Arti dari kode Error Java Virtual Machine BB anda

List dari kode error yang bisa saja terjadi di Java Virtual Machine (JVM) BlackBerry anda:

• 101 Internal JVM error.
• 102 Invalid code in file system. The .cod files in the handheld have been checked for modification and it has been determined that there is a problem with one or more .cod files.
• 103 The starting address for the boot .cod file cannot be found. This might mean that a boot .cod file has not been installed on the handheld, or that its format is invalid or corrupt.
• 104 An uncaught Java exception was thrown in the Java code and diagnosed by the JVM. Execution can be continued or the handheld can be attached to a debugger on a desktop through a serial or USB cable. The event log should contain the traceback of the thrown exception.
• 105 An OS file system API returned an error status for a certain operation. This can indicate a corrupt file system or an error in the JVM.
• 106 An error has been detected in the graphics system of the handheld.
• 107 Internal JVM error.
• 108 Internal JVM error.
• 109 Internal OS error.
• 110 Non-idle event downtime error. A problem has been detected in the accumulation of JVM down time that represents how long the JVM has been idle. This indicates an error in either the OS code or the JVM code.
• 200 Application manager threw an uncaught exception. The application manager event thread threw an uncaught exception and so cannot continue running.
• 201 Initialization of the cryptographic system failed and the handheld cannot continue to operate.
• 202 An attack on the key store has been detected, and the handheld cannot continue to operate.
• 203 The application manager console process, usually the Home screen ribbon, has failed, like due to an uncaught exception.
• 501 Internal error.
• 502 All processes exited. The last Java process has terminated, and there is nothing left to execute.
• 503 Internal error.
• 504 Internal error.
• 505 Internal error.
• 506 An uncaught Java exception was thrown in the initial VM Java thread thus killing the only live thread in the system. The event log contains the traceback for the exception.
• 507 A dependency on a .cod file could not be satisfied due to a missing .cod file. Load the missing .cod file onto the handheld.
• 508 Invalid object. A problem has been detected with a debugger command to the VM.
• 516 Error occurred during garbage collection, which might indicate a corrupted file system.
• 510 All threads are waiting on objects, which results in a deadlock. The system cannot recover from this state since no thread can release a lock.
• 511 A problem has occurred during debugging.
• 515 The reachable objects form a group that cannot be represented properly by the VM because there are too many objects or the total size of the objects is too large.
• 516 When committing a persistent object, the VM found that the persistent store id counter has reached its limit. The object was not committed.
• 517 An inconsistency has been detected in the VM persistent object store.
• 518 Internal error.
• 519 Internal error.
• 520 Internal error.
• 521 Indicates that Object.wait() has been executed by a thread that holds a lock on another object; occurs only in simulator if the JvmDebugWaits application switch.
• 522 A thread has acquired two locks on objects in an order that doesn’t match the order that previous locks for the two types were acquired, which indicates a future potential deadlock situation; reported only in the simulator when the JvmDebugLocks application switch is set.
• 523 A critical Java process has died and the device cannot continue to operate normally.
• 524 An object has been marked as recovered by the Low Memory Manager but it was not freed during a garbage collection. This is only checked in the simulator under the control of the JvmDebugLMM application switch.
• 525 Bad persistent object. An auto-commit operation during a garbage collection has detected a non-persistent object reachable from the persistent store root. The type of the object has been output into the event log.
• 526 The class definition for java.lang.Object cannot be found.
• 527 The class definition for java.lang.String cannot be found.
• 528 The file system is corrupted. Data on the handheld is unrecoverable.
• 529 The file system is corrupted. An attempt is going to be made to recover data, but some data might be lost.
• 530 Internal JVM error.
• 531 Flash memory has been exhausted.
• 532 A JVM assertion has been violated. This error can occur only in the simulator, not on an actual handheld.

BlackBerry on Demand (BoD)

BoD adalah BIS yang dapat di aktivasi/non-aktivasikan melalui SMS. BoD ini pertama kali diluncurkan di Indonesia dan oleh Telkomsel lalu disusul oleh operator-operator lainnya.

Layanan ini begitu mudah digunakan sehingga menjadi pilihan favorite bagi pengguna BlackBerry pemula yang masih ingin mencoba-coba layanan operator maupun bagi pengguna yang memiliki beberapa handheld BlackBerry karena lebih mudah untuk berganti-ganti layanan (aktivasi dan non-aktivasi tanpa perlu ke galeri operator). Waktu aktivasi layanan ini pun sangat cepat, yang berani dijanjikan operator adalah dalam 24 jam akan aktif tetapi kebanyakan sudah aktif dalam 1-2 jam. BoD dapat digunakan untuk SIM pre-paid maupun post-paid

Layanan BIS pre-paid ini sama dengan BIS post-paid dalam hal unlimited data selama menggunakan APN BlackBerry dan juga diberikan 10 account emails.

Berikut ini adalah cara serta harga yang ditetapkan setiap operator untuk layanan BODnya:

Telkomsel

Registrasi BoD Bulanan (Rp. 180,000.-/bulan): SMS “BB<spasi>REG” (contoh: BB REG) ke 333

Biaya: Rp. 180,000.-/bulan

Stop BoD: SMS “BB<spasi>UNREG” ke 333

Indosat

Registrasi BoD Mingguan (Rp. 50,000.-/minggu): SMS “BIS1<spasi>Merek<spasi>Tipe” (contoh: BIS1 BB 8900) ke 889

Registrasi BoD Bulanan (Rp. 160,000.-/bulan, Matrix Rp. 175,000.-): SMS “BIS2<spasi>Merek<spasi>Tipe” (contoh: BIS1 NOKIA E90) ke 889

Bagi pelanggan Indosat yang menggunakan Mentari dan BlackBerry 8300 dapat menggunakan paket BIS Bonus Pulsa dengan registrasi SMS “BIS2BONUS BB 8300″ ke 889.

Untuk keterangan lebih lanjut mengenai paket BIS Indosat dapat menuju ke link berikut: http://www.indosat.com/Matrix_BlackBerry/BlackBerryR_from_Matrix_Up_Date/BlackBerry_On_Demand

Stop BoD: SMS “UNREG” ke 889

XL

Registrasi BoD One Harian (Rp. 5,000.-/hari): SMS “BB<spasi>ON” ke 568

Registrasi BoD One Bulanan (Rp. 150,000.-/bulan): SMS “BB<spasi>Bulan” ke 568

Untuk keterangan lebih lanjut mengenai paket BIS XL dapat menuju ke link berikut: http://www.nyambungterus.com/index.php?xl=Nyambung.layanan-bb

Stop BoD: SMS “BB<spasi>OFF ke 568

Cara Backup 3rd Party Application

Backup 3rd Party Applications untuk Desktop Manager 4.7

1. Sambungkan Blackberry, kemudian nyalakan Desktop Manager >Device Switch Wizard
2. DSW> Blackberry devices
3. Pastikan HANYA 3rd Party Application yang dipilih, kemudian NEXT.
4. Desktop Manager akan mem-backup seluruh 3rd Party Apps, setelah selesai, JANGAN pilih Next / Cancel.
5. Cari file dan folder di PC anda (pastikan cari hidden files and folder serta folder system dalam pencarian). Cari sebuah Folder yang namanya sama seperti PIN BB anda, dan sebuah file .alx
6. Pindahkan kedua file tersebut ke folder lain (cth. Desktop)
7. Kembali ke Desktop Manager dan Cancel proses backup tadi.

RESTORE Process

1. Sambungkan Blackberry > jalankan Desktop Manager
2. Pilih App Loader > Add/Remove Applications
3. Pilih Add
4. Buka folder PIN anda tadi (proses backup no.6)
5. Pilih file .alx tadi dan Pilih Open > Next

Semoga membantu.

Sumber : Crucial_Xtreme, Crackberry
Translation: red.angelz

Join the forum discussion on this post - (1) Posts

Cara Upgrade / Downgrade Blackberry

Udah gatel nih mau cobain firmware2 yang ada di gudang? Ga usah repot2 bawa ke toko untuk upgrade, caranya cukup mudah koq. Kita coba ajarin step-by-step caranya, biar kamu bisa langsung update sendiri. Yang dibutuhkan adalah: sebuah Blackberry (ya iya lahhh), kabel USB, PC dan Laptop serta sambungan internet (buat buka page ini donk :D)

Ada 2 Cara untuk mengupgrade firmware (OS) Blackberry kamu, yaitu..

Basic

1. Download dulu OS terbaru buat device kamu (Pastikan OS itu untuk tipe Blackberry kamu)
2. Backup dulu data kamu pake Desktop Manager.
3. Install OS yang tadi kamu download di No.1 (.exe file)
4. Hapus file “vendor.xml” (C:\Program Files\Common Files\Research In Motion\AppLoader)
5. Install OS yang baru tadi dengan cara sambungin BB kamu ke PC pake Desktop Manager.

Advance

1. Download dulu OS terbaru buat device kamu dari gudang commberry atau darimana aja.(Pastikan OS itu untuk tipe Blackberry kamu)
2. Backup dulu data kamu pake Desktop Manager
3. Backup aplikasi-aplikasi yang kamu sudah install sebelumnya
4. Kalau kamu dulu pernah mengupdate firmware sebelumnya, uninstall dulu dari komputer kamu (Control Panel > Add/Remove Program > Uninstall OS yg lama dari list)
5. Install OS yang tadi kamu download di No.1 (.exe file)
6. Hapus file “vendor.xml” (C:\Program Files\Common Files\Research In Motion\AppLoader)
7. Wipe Blackberry kamu menggunakan JL_cmdr
8. Install OS yang baru tadi dengan cara sambungin BB kamu ke PC pake Desktop Manager > App Loader.
9. Restore applikasi pihak ketiga kamu (click here to see how)
10. Restore dari Backup data yang tadi dibuat di No.2

————————————————————————————————————–

Wiping your Blackberry using JL_cmdr:

1. Sambungkan BB dengan PC menggunakan USB
2. Setelah BB terhubung, pilih opsi no.4 - Wipe Handheld
3. ketik “blackberry” (tanpa tanda petik) untuk menghapus seluruh system blackberry.

Setelah ini, Blackberry akan reboot, akan ada tampilan layar putih dengan tulisan ‘507′ error. Jangan panic, memang demikian, karena OSnya ga ada. Kemudian silahkan melanjutkan menginstall OS yang baru.

Note: Ada beberapa forum yang menambahkan proses Memory Optimization, namun menurut saya gak perlu karena OS kamu sudah di delete habis pada proses Wipe Blackberry. Proses itu boleh saja dilakukan kalau kamu memang mau.

Selama melakukan proses ini, gunakan sambungan USB langsung ke USB PORT. JANGAN sambung menggunakan USB HUB. Ada kalanya Blackberry tidak ter-detect oleh PC/Desktop Manager/JL_cmdr, jangan panik, coba lepas dan sambung kembali kabel USB, terkadang bisa sampai 5 kali copot-sambung baru terdeteksi.

Bila terjadi hal-hal aneh (semoga enggak), jangan panik dan stress, coba jelaskan permasalahannya kesini, nanti kita bantu semaksimal mungkin.

Advance step ini ditujukan agar OS yang diinstall lebih ‘fresh’ tanpa meninggalkan file-file system lama yang mungkin ditinggalkan OS lama pada saat proses upgrade/downgrade.

Happy upgrading!

Join the forum discussion on this post - (9) Posts