bblovers.net

BlackBerry prabayar di Singapura dengan Starhub

Kristian — Thu, 25 Feb 2010 11:40:06 +0000

Bayangkan saat berada di luar negeri tapi BBLovers butuh layanan BlackBerry. Tentunya itu bukan masalah besar, sampai akhirnya tagihan datang. Biaya roaming BIS ternyata cukup mahal. Saya hanya sempat mengecek XL yang membandrol Rp 50 ribu per hari.
Salah satu cara untuk menyiasati hal itu adalah dengan membeli kartu perdana dari operator yang menyediakan layanan BlackBerry prabayar.
Saya menulis artikel ini dari BlackBerry, memanfaatkan layanan prabayar BlackBerry dari StarHub, di Singapore. Untuk tarif, jelas lebih ekonomis dibandingkan roaming. Untuk berlangganan 3 hari (paket individual), dikenai tarif SGD$10, 7 hari SGD$18, dan 30 hari SGD$25. Perbedaan dengan paket di Indonesia terletak pada limit penggunaan data yang dibatasi.
Jika kita bandingkan dengan tarif roaming BB XL, yang 7 hari menyedot biaya sampai Rp 350 ribu, beda harganya amat kontras.
Jadi pilih yang mana nih???

Layanan BlackBery Tri, Termurah di Indonesia

Kristian — Mon, 22 Feb 2010 06:01:24 +0000

Satu lagi operator Indonesia yang menyediakan layanan Blackberry. 3 (dibaca Tri) menyusul empat operator lain yang telah menyajikan layanan serupa, yakni Indosat, XL, Axis, dan Telkomsel.
Kelebihan layanan BeBe Tri terletak pada tarifnya yang amat kompetitif, bahkan yang paling murah dibandingkan keempat “kakak”nya.
Ada tiga pilihan paket, berdasarkan masa penggunaan:
1. Harian Rp 3,500
Ketik REG(spasi)BB kirim ke 234
2. Mingguan Rp 19,000
Ketik REG(spasi)BB1 kirim ke 234
3. Bulanan Rp 88,000
Ketik REG(spasi)BB2 kirim ke 234

Paket layanan tersebut sudah mencakup browsing, push email, BBM, IM, dan social networking. Tertarik?

15 Orang Pertama Pencoba Aplikasi Twitter For BlackBerry

Beatrix — Fri, 12 Feb 2010 06:49:14 +0000

BBLovers berkesempatan untuk menjadi salah satu dari 15 orang pertama yang mendapat invitation code untuk mendownload aplikasi Twitter for BlackBerry di Indonesia. Wow…rasanya gimanaaa geto ya. Tapi kesan pertama tidak begitu mengecewakan…Interfacenya menarik, dan yang paling penting fontnya itu. Guedee…ya betterlah daripada Ubertwitter dan lainnya. Tapi karena masih versi beta, memang masih agak tersendat. Cuma ada satu yang masih berusaha kami oprek….masih agak kesulitan untuk bisa retweet nih. Be right back with more update…Stay Tune…

Chatting sepuasnya dengan BlackBerry XL cuma Rp 2000/hari

Kristian — Mon, 01 Feb 2010 16:48:55 +0000

XL meluncurkan varian baru dari layanan BlackBerry One, dengan nama BlackBerry Gaul. Tarifnya cukup fantastis, hanya Rp 2000/hari. Jadi BBLovers yang hanya membutuhkan layanan untuk chatting (Yahoo Messenger, MSN Live Messenger, dan Google Talk) serta MySpace dan Facebook, tak perlu membayar sampai ratusan ribu per bulan. Bahkan, biaya langganan bulanan hanya dikenakan Rp 50 ribu/bulan. Perlu diingat, fitur layanan Browsing dan EMail tidak bisa digunakan selama BBLovers berlangganan paket ini.

Cara pengaktifan BlackBerry Gaul cukup mudah. Cukup tekan *123# lalu tekan Yes/OK. Selanjutnya, pilih menu untuk mengaktifkan layanan BlackBerry Gaul. Untuk aktifasi menggunakan SMS, BBLovers dapat lansgun mengirim SMS dengan format: BB(spasi)Gaul ==> tarif harian, atau: BB(spasi)Gaul(spasi)Bulan ==> tarif bulanan, lalu kirimkan ke nomor 568.

Bagi yang sudah memanfaatkan layanan ini, ditunggu curhatnya ya!!

BES On Demand pertama di dunia dari Indosat

Kristian — Mon, 18 Jan 2010 03:05:39 +0000

Satu lagi prestasi manis diukir oleh operator Indonesia. PT Indosat Tbk. berhasil menjadi operator pertama di dunia yang menyediakan layanan BlackBerry Enterprise Service (BES) on Demand. BESoD sendiri merupakan layanan data BlackBerry untuk tingkat korporasi, dengan fasilitas pengendalian akses data dan email, yang amat krusial bagi sebuah perusahaan.

BES On Demand dapat dinikmati pelanggan pascabayar (Matrix) dan prabayar (Mentari dan IM3). BBLovers cukup mengirim SMS bertuliskan “BES Bulanan” ke 899 untuk mendaftar. Harga yang ditawarkan cukup bersaing, hanya sekitar Rp 160 ribu per bulan.

Indonesia sendiri memang cukup inovatif dalam menggelontorkan berbagai layanan BlackBerry. Bahkan layanan BIS on demand untuk individu, dengan pilihan langganan harian, mingguan, dan bulanan, juga pertama kali diperkenalkan oleh operator-operator Indonesia. Hebat kan?

Sumber

Perfectly Bold; Slimmer & Faster

Beatrix — Fri, 15 Jan 2010 10:19:17 +0000

BlackBerry Bold 9700 atau yang akrab disebut dengan panggilan Onyx, akhirnya resmi juga di Indonesia. Sekilas memang tidak ada yang istimewa tentang anggota baru keluarga BlackBerry ini. Tetapi begitu sekali mencobanya, kami langsung ketagihan. Secara keseluruhan, BlackBerry Bold 9700 ini mengemas banyak peningkatan kecil yang penting atas BlackBerry Bold. Penggabungan antara desain yang elegan bersanding serasi dengan kemampuan yang mumpuni. Kami tidak akan mengulasnya secara habis-habisan kali ini, mengingat ini hanyalah versi update dari BlackBerry Bold 9000 yang diandalkan banyak BBLovers. Lihat dulu di bawah ini untuk spesifikasi lengkap Bold 9700:

Desain ramping dengan ukuran 4.29″ x 2.36″ x 0.56″ (109 mm x 60 mm x 14.1 mm) dan berat hanya 122 grams
Display berukuran 2.44-inch yang tajam dengan resolusi 480 x 360 dengan 245 ppi)
Full-QWERTY keyboard yang sangat taktis – dengan tombol-tombol yang dibuat dengan teknik tinggi dan dilapisi warna krom – untuk pengetikan yang akurat dan cepat
Trackpad peka sentuhan inovatif yang memungkinkan navigasi secara intuitif dn responsif
Built-in Wi-Fi (802.11 b/g) untuk browsing web yang lebih cepat dan penambahan konektifitas data
Kamera 3.2 MP dengan variabel zoom, autofocus, flash dan video recording
BlackBerry® OS 5.0 menawarkan pengguna pengelolaan email, kalender* serta pengalaman browsing yang lebih baik dengan proses JavaScript dan CSS yang lebih cepat.
Built-in GPS untuk peta dan aplikasi berbasis lokasi lain serta photo geotagging
Media player untuk video, foto dan musik ( dapat digunakan untuk memainkan musik hingga 38 jam), plus dukungan untuk BlackBerry® Desktop Manager untuk PC dan Mac, serta BlackBerry® Media Sync untuk kemudahan sinkronisasi iTunes® dan Windows Media® Player dengan smartphone**
3.5 mm stereo headset jack, dedicated volume controls, tombol Lock dan Mute keys pada bagian atas handset
Slot kartu memori microSD/SDHD yang mendukung hingga 16 GB saat ini dan diharapkan mendukung kartu memori 32 GB dan 2 GB jika telah tersedia.
256 MB Flash memory
Akses ke BlackBerry App World™yang menyajikan katalog aplikasi mobile yang dikembangkan khusus untuk smartphone BlackBerry<http://www.blackberry.com> . Apalikasi tersebut dibagi-bagi berdasarkan kategorinya: games, hiburan, IM dan social networking, berita, cuaca, produktivitas dan lainnya.
Fitur-fitur kelas atas dan mudah digunakan, teknologi yang mampu meminimalkan noise dan speaker berkualitas tinggi
Bluetooth® (2.1) dengan dukungan untuk Secure Simple Pairing, hands-free headsets, stereo headsets, car kits dan peripheral Bluetooth lain
Dukungan untuk layanan BlackBerrytermasuk akses ke 10 email accounts ( termasuk dari provider terkemuka seperti Yahoo!®, Windows Live™ Hotmail®, AOL® and Gmail™); dan Dukungan BlackBerry® Enterprise Server, yang menghadirkan keamanan terbaik dan administrasi TI untuk perusahaan
Diproduksi dua versi untuk mendukung berbagai kombinasi frekuensi jaringan 3G operator :
o UMTS/HSDPA 2100/1900/850/800 MHz dan quad-band EDGE/GPRS/GSM
o UMTS/HSDPA 2100/1700/900 MHz dan quad-band EDGE/GPRS/GSM

Baterai 1500 mAhr yang mudah dilepas dan diisi ulang dengan talk time 6 jam dan Standby hingga 17 hari pada 3g mode

Saya sempat mencobanya selama beberapa waktu, dan jika BBLovers saat ini sedang menggunakan BlackBerry Bold 9000, akan sangat menghargai peningkatan kualitas layar yang lebih tajam dan penggunaan optical trackpad yang responsif dan tidak rewel seperti trackball tradisional. Kinerja juga terasa lebih cepat, berkat paduan prosesor yang lebih handal dan sistem operasi BlackBerry OS 5.0 yang lebih efisien. Perlu dicatat, Bold 9700 merupakan BlackBerry pertama yang telah memakai sistem operasi tersebut dari paketnya.
Namun penyempurnaan yang membuatnya wajib dimiliki pengguna setia BlackBerry adalah kapasitas baterainya yang jauh lebih bandel alias tahan lama. Jika dulu rata-rata kurang dari 24 jam, kini Bold 9700 mampu bertahan lebih dari 24 jam, bahkan untuk pemakaian yang kurang “aktif”, bisa mencapai 48 jam. Jadi BBLovers bisa bernapas lega karena tak perlu lagi mengantungi charger atau baterai cadangan jika ingin membawanya seharian.

Dengan segala fitur dan peningkatannya, maka tak berlebihan jika saya menyebut BlackBerry Bold 9700 sebagai BlackBerry terbaik saat ini, setidaknya sampai keluar lagi penggantinya. Bagi BBLovers yang sudah menggunakannya, ditunggu ya komentarnya!!!

Presentasi lebih praktis dengan BlackBerry Presenter

Kristian — Sun, 10 Jan 2010 18:42:00 +0000

Bertepatan dengan Consumer Electronics Show atau CES 2010, RIM mengumumkan perangkat terbarunya yang ditujukan untuk meningkatkan fungsionalitas ponsel pintarnya, yaitu BlackBerry Presenter. Dengan aksesoris baru ini, BBLovers dapat melakukan presentasi Microsoft PowerPoint, PDF, atau file gambar lain secara wireless dari smartphone BlackBerry. Keren kan? Boleh dibilang, alat ini memberikan solusi jika BBLovers malas membawa laptop atau file presentasi dikirim secara darurat ke BlackBerry.

Tersedia mode loop untuk mengatur waktu antara satu slide dengan yang lain, mirip seperti presentasi biasa. Juga ada mode Freeze, yang akan menghentikan slide di layar saat BBLovers sedang mencari halaman yang diinginkan di smartphone. Presenter ini mendukung berbagai efek PowerPoint, koneksi Bluetooth, dan mendukung sistem video NTSC dan PAL.

BBLovers dapat menghubungkannya dengan perangkat lain yang memiliki kabel VGA atau S-Video. Untuk saat ini, BlackBerry Presenter tidak bisa dipakai untuk seri Curve 8300 dan Pearl Flip. Firmware Presenter juga bisa diupgrade, menggunakan PC Intel yang menjalankan MS Windows serta BlackBerry Device Software v4.6 atau lebih baru.

Berikut spesifikasinya:

Ukuran: 3.4 x 2.4 x 0.9 inches (86 x 60 x 23 mm)
Bahasa: Inggris, Prancis, Italia, Jerman, Spanyol
Kabel video: S-Video, VGA
Koneksi daya: USB
Dukungan resolusi: 640×480 (VGA), 800×600 (SVGA), or 1024×768 (XGA)
Bluetooth: Versi 2.0 + EDR, Class 1.5
Carrying Case: Synthetic Leather

Sumber

UberTwitter Beta 6: Banyak fitur baru

Kristian — Fri, 08 Jan 2010 03:32:13 +0000

UberTwitter yang cukup populer di berbagai platform ini telah dirilis versi betanya untuk smartphone BlackBerry. UberTwitter Beta 6 yang baru ini mengemas cukup banyak peningkatan baru.

Berikut daftar update fitur dan kemampuannya:
* List – BBLovers bisa menciptakan, menghapus, berlangganan, serta menambah & melihat member.
* Find People – menemukan orang, persis seperti link “Find People” di homepage Twitter.
* Icon yang baru
* Uber Bar – Terdapat di atas layar, dengan dukungan penambahan tab, seperti Firefox, yang dapat menampilkan berbagai data seperti timeline, list, dan sebagainya.
* Retweet
* Update Twitter Profile – update profil dari BlackBerry.
* Report Spam – melaporkan tweet sebagai spam.
* Twitter Geo-Tagging – Anda bisa menggunakan myloc.me URL, Twitter Geo-Tagging, atau keduanya!
* Friend Picker – Ketik “@” dan daftar teman akan muncul
* Avatar lebih besar – klik di foto profil dan versi besar gambarnya akan muncul
* TwitLonger – kirim tweet yang lebih panjang, berkat teman-teman di TwitLonger.com. Kemampuan ini telah diintegrasikan baik untuk mengirim atau menerima tweet ekstra panjang.
* What’s the Trent? – kerjasama dengan WhatTheTrend.com dapat menampilkan penjelasan topik yang sedang tren, dan BBLovers juga bisa menjelaskan mengapa sebuah topik menjadi tren
* Pilihan layout timeline – pilih antara layout “bubble” atau “bar”

Jujur saja, saya bukan pengguna berat Twitter, tapi setidaknya dengan fitur-fitur baru ini, UberTwitter Beta 6 mungkin akan menarik perhatian para pengguna kasual Twitter untuk lebih aktif ‘tweeting’.

BBLovers dapat mendownload UberTwitter Beta 6 di sini.

JVM Error Code

Beatrix — Tue, 05 Jan 2010 11:23:09 +0000

Pernah atau lagi mengalami kejadian BeBe error? Pastinya bingunglah ya…Termasuk saya waktu pertama kali BeBe error, nge-hang dan muncul kata2 JVM Error 5xx. Apaan lagi itu kan… Nah, supaya gak bingung. Coba liat aja tabel dibawah ini supaya lebih tahu error JVM (Java Virtual Machine, yang pertama kali saya kira JUM)yang menimpa BeBe kamu.

Value	Error	Description
101	Previous startup failed	The device was reset during the JVM boot process. The JVM found the boot in progress flag was set on startup. The screen is intended to break continuous reset loops so that corrective action can be taken.
102	Invalid code in filesystem	The system checked the COD files in the device for modification and determined that a problem exists with one or more COD files.If all loads fail, a build process error might occur (a problem exists with signing the COD files). If a user action on the device resulted in this problem, the reset cycle is continuous because the code in the filesystem has been corrupted. The only recovery method is to wipe the device and restore a new system.
103	Cannot find starting address	The starting address for the boot COD file cannot be found. This might indicate that a boot COD file has not been installed on the device or that its format is invalid or corrupt.
104	Uncaught:	An uncaught Java exception was thrown by the Java code and diagnosed by the JVM. Execution can continue, or the device can be attached to a debugger on a desktop computer. The Microsoft® Windows® Event Viewer log should contain the traceback of the thrown exception.
105	Example, DbRecSize( %d ) -> %d	The file system application programming interface (API) has returned an error status for a specific operation. This might indicate a corrupt filesystem or an error in the JVM.
106	Graphics system error	An error was detected in the graphics system on the device.
107	operator new() called	A C++ class in the JVM was coded incorrectly to inherit from VMRamObject that has the correct override for operator new. Extract the current (post-reset) BUGDISP.
108	operator delete() called	A C++ class in the JVM has was coded incorrectly to inherit from VMRamObject that has the correct override for operator delete. Extract the current (post-reset) BUGDISP.
109	PriorityMessageCount error:	The value returned by RimPriorityMessageCount is negative. It should always be greater than, or equal to, zero. This indicates an error in the operating system code. Extract the current (post-reset) BUGDISP and EVENTLOG.
110	Non-idle event downtime error:	A problem was detected in the accumulation of JVM down time, which represents how long the JVM has been idle. This usually indicates an error in the device firmware or the JVM. This could also occur if the tick count rolls over after 400 or more days of device time.
111	Font engine error	An error was detected in the font engine system on the device. Extract the current (post-reset) BUGDISP and EVENTLOG.
112	Java Native Assertion Failure	An error was detected in the Java native code. Extract the current (post-reset) BUGDISP and EVENTLOG.
200	Application manager threw an uncaught exception	The application manager event thread threw an uncaught exception and cannot continue execution.
201	Crypto initialization code failed	The initialization of the crypto system failed and the device cannot continue execution.
202	An attack on the key store has been detected	An attack has been detected and execution cannot continue.
203	Console process died	The application manager console process (usually the Ribbon) has died. This is likely due to an uncaught exception during execution.
204	Persistent Content Exception	An application tried to commit a plaintext object to the Persistent Store. This will only happen if Content Protection is on and a process tries to save something in the PersistentStore that is marked as plaintext. Since this exception was not handled, the persistent store is in a bad state. You should reset to roll back to the last good commit point.Note: This is not a JVM erro; the JVM is simply diagnosing the problem. The eventlog contains information about the erroneous Java code.
501	VM_THREAD_SWITCHED: Internal Error	This is an error return used internally in the VM. It should never be reported as a device error.
502	VM_PROCESS_DEATH: All processes exited	The last Java process has terminated. There is nothing left to execute.
503	VM_THREAD_DEATH: Internal Error	This is an error return used internally in the VM. It should never be reported as a device error.
504	VM_THREAD_SWITCH: Internal Error	This is an error return used internally in the VM. It should never be reported as a device error.
505	VM_BAD_CODE: Bad Byte Code	An error has occurred in the JIT compiler.
506	Uncaught Exception	An uncaught Java exception was thrown in the initial VM Java thread, thus ending the only live thread in the system. The eventlog contains the traceback for the exception.
507	Unsatisfied Link	A dependency on a COD file could not be satisfied because the COD file is missing.
508	Invalid object	A problem has been detected with a debugger command to the VM.
509	VM_PPO_INFINITE_LOOP: infinite loop in PPO phase of GC	The maximum iteration count for the PPO phase of a GC must be the maximum number of file handles in the system. This error indicates that the iteration count exceeds the maximum. Hence, a flaw exists in the PPO loop or a corrupted file system. The extra hex integer in the error string is the flash id of the current record where the infinite loop was detected.
510	Deadlock	All threads are waiting on objects, resulting in deadlock. The system cannot recover from this state because no thread can release a lock.
511	Debug connection died	A problem has occurred while debugging that may be caused by a VM problem or an incorrect debugging command being sent to the VM.
512	GC Aborted	An idle garbage collection has been interrupted by a user event (for instance, a key was pressed or the trackwheel was used).
513	needs running	An opcode requires that a class execute before it can continue execution.
514	needs running	A new instance of a class has been allocated and it must be initialized by the default constructor before it can be used.
515	Object group too big	The reachable objects form a group that cannot be represented properly by the JVM because either there are too many objects or the total size of the objects is too large.
516	Persistent ids exhausted	When committing a persistent object, the JVM found that the persistent store id counter reached its limit. The object was not committed and a critical error was reported. This error should not occur unless a device is heavily used for years.
517	Filesystem corrupt	An inconsistency was detected in the JVM persistent object store.
518	Unexpected longjmp	A garbage collection marking phase was terminated via a longjmp. This indicates that the marking phase was interrupted when it should have completed without interruption. This error should not occur because these actions are executed when the device is not idle, and GCs can only be interrupted when the device is idle.
519	Internal Error	The JVM host is missing or has been disabled.
520	Internal Return	This is an internal state that indicates a Java method return needs to be executed.
521	Dangerous Wait	An Object.wait() was executed by a thread that holds a lock on another object.
522	Interlaced synchronization	A thread acquired two locks on objects in an order that doesn’t match the order in which a lock on the two types were previously acquired. This indicates a future potential deadlock situation and is reported. The check is only available in the simulator under the control of the JvmDebugLocks application switch.
523	System process died	A critical Java process has terminated, and the device cannot continue to operate in a normal manner.
524	LMM error	An object has been marked as recovered by the Low Memory Manager, but it was not freed during a garbage collection.
525	Bad persistent object	An auto-commit operation during a garbage collection detected a non-persistent object reachable from the persistent store root. The type of the object was output into the eventlog.
526	java.lang.Object not found	The class definition for java.lang.Object cannot be found.
527	java.lang.String not found	The class definition for java.lang.String cannot be found.
528	Corrupt filesystem. Unrecoverable. All data will be lost	All data will be lost when execution continues. The error message screen contains a number representing an internal reason for the corruption. This error is not diagnosed if a COD file was removed because the JVM must delete objects that were defined in the removed COD file. Thus, this error is not expected in normal device operation. Refer to the following reason codes: Root array reference is not a valid array reference Root array type is not Object[] Root array size < 1 (i.e., Object[0]) Contents of root[0] is not a valid ref Type of root[0] is not a LongIntHashtable Persistent segmented array header contains an invalid reference An entry in a persistent Object[] contains an invalid reference An Object’s type refers to an unknown codfile An Object’s type description in the codfile doesn’t match the size in the store A reference type field in an Object has an invalid reference in it A reference type field in an object points to an object of the wrong type A persistent Object[] is missing its descriptor Object in persistent store is not marked as persistable Root array is segmented and one of the segments is invalid
529	Corrupt filesystem. About to attempt recovery. Some data may be lost	Some data will be lost when execution continues. The error message screen contains a number representing an internal reason for the corruption. This error is not diagnosed if a COD file WAS removed because the VM must delete objects that were defined in the removed COD file. Thus, this error is not expected in normal device operation. Refer to the following reason codes: Root array reference is not a valid array reference Root array type is not Object[] Root array size < 1 (i.e., Object[0]) Contents of root[0] is not a valid ref Type of root[0] is not a LongIntHashtable Persistent segmented array header contains an invalid reference An entry in a persistent Object[] contains an invalid reference An Object’s type refers to an unknown codfile An Object’s type description in the codfile doesn’t match the size in the store A reference type field in an Object has an invalid reference in it A reference type field in an object points to an object of the wrong type A persistent Object[] is missing its descriptor Object in persistent store is not marked as persistable Root array is segmented and one of the segments is invalid
530	VM_PREVENT_GC_OVERFLOW: _preventGC overflow	A fixed number of native objects can be protected from garbage collection. This error indicates that a native has exceeded the fixed limit of objects that can be protected. If the device is reset or thread tracebacks are logged, the name of the actual native can be extracted.
531	Flash exhausted	There are certain operations where the JVM cannot withstand running out of flash space. In these circumstances, this error will be reported if the JVM cannot allocate a required amount of flash space.
532	VM_ASSERTION_FAILED: Assertion failed	Normally this JVM error should not be reported since the device is not shipped with assertions enabled. The simulator may report this error in debug mode indicating a VM assertion was violated. Try typing BKPT to activate the debugger and dump the native call stack for forwarding to the VM team.
533	VM_RUN_METHOD: needs running	This is used internally for ECMAScript to call Java methods.
534	VM_FAST_RESET_DISABLED: Fast Reset Disabled	This is used internally to indicate that fast reset capability is not available. Often used in platform-specific code.
535	VM_UNUSED_535: Unused	This is an unused VM error.
536	VM_FAST_RESET_BAD_INSTANCE: VM Instance Check Failed	This is used internally to indicate that the VM structure passed in is at the wrong address or has been corrupted.
537	VM_FAST_RESET_BAD_HEAP: Heap Check Failed	This is used internally to indicate that the VM heap has been corrupted or pointers into the heap have been corrupted.
538	VM_FAST_RESET_BAD_IRAM: IRAM Check Failed	This is used internally to indicate that the VM IRAM checks have detected corruption of VM data structures (threads and local stacks) that reside in IRAM.
539	VM_FAST_RESET_NOT_IDLE: Not Idle	This is used internally to indicate that the VM was not idle when the reset occurred and, as such, cannot continue with a fast reset.
540	VM_FAST_RESET_MULTIPLE_RESETS: Multiple Resets	This is used internally to indicate that the time since the last fast reset is less than a minimum time. By disallowing multiple fast resets in a short amount of time, this should prevent fast reset loops.
541	VM_HEAP_COMPACT_INFINITE_LOOP: infinite loop detected in heap compaction	The VM detected a problem in its RAM heap that indicates its RAM was corrupted. The problem was detected by identifying a possible infinite loop during RAM heap compaction. A bugdisp log and eventlog should be extracted quickly when the device is in this condition. If possible, images of RAM should be saved.
542	Transient memory leak	The JVM detected that some memory was not freed, indicating that a memory leak has occurred. This condition is detected as early as possible to improve chances of isolating the cause.
543	VM_FS_MISMATCH: Incompatible Java filesystem installed	The VM detected that the operating system binary is different from the operating system binary used to create the Java file system. This means that the Java native methods may not be linked properly and as such, the integrity of the system cannot be guaranteed. The system can be recovered by using the VM DLFX and DLPS commands to delete the fixups and persistent store. This will clear all data and fixups and let the filesystem re-link to match the new operating system binary.Note: The recovery order is: Delete fixups Delete persistent store Reset device
544	VM_SECTION_MAP_OVERFLOW: a module references more than 255 other modules	The VM detected that a module is trying to reference more than 255 other modules. Extract the filesystem immediately when this error is detected.
545	VM_INCOMPATIBLE_FILESYS: an incompatible or corrupt filesystem was found	The VM detected an incompatible or corrupt filesystem. Extract the filesystem immediately when this error is detected.
546	VM_UNUSED_546: unused	The VM detected that the RAM image of its filesystem is corrupted (failed CRC check). Better to reset than to duplicate the corruption into flash.
547	VM_UNUSED_547: unused	This is an unused VM error.
548	VM_UNUSED_548: unused	This is an unused VM error.
549	VM_UNUSED_549: unused	This is an unused VM error.

Theme Animasi Tranquil Garden

Beatrix — Tue, 05 Jan 2010 02:38:28 +0000

Bagi yang sudah mendownload aplikasi App World, coba cek kedalamnya. Barangkali ada aplikasi baru yang ditawarkan. Apalagi untuk Indonesia, masih banyak banget aplikasi gratisan yang bisa di download. Aplikasi yang ditawarkan itu belum tentu gratis di negara lain. Contohnya theme yang satu ini. Tranquil garden adalah theme yang menampilkan sebuah kebun yang asri lengkap dengan animasi kupu-kupu yang beterbangan. Theme ini bisa didownload langsung dari aplikasi App World yang sudah kamu download di BeBe. BBLovers menganjurkan theme ini, karena setelah mencobanya terbukti theme ini tidak terlalu berat dan suasana kebun dan air terjun yang asri buat suasana hati kita jadi lebih sejuk. Hehehe…. Tampilan menunya juga oke, didominasi warna hijau dan icon menu berubah jadi transparan. Buruan di download, mumpung gratis….Kalau diliat dari situs App World, theme ini berbayar loh…$5.99, lumayan kan…