Im getting this error
D/AndroidRuntime( 902): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 902): CheckJNI is OFF
E/dalvikvm( 902): Can't open dex cache '/data/dalvik-cache/[email protected]@core[email protected]': No such file or directory
I/dalvikvm( 902): Unable to open or create cache for /system/framework/core.jar
D/dalvikvm( 902): Failed on '/system/framework/core.jar' (boot=1)
D/dalvikvm( 902): VM cleaning up
D/dalvikvm( 902): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 902): JNI_CreateJavaVM failed
E/AndroidRuntime( 902): JNI_CreateJavaVM failed
from the logcat dnt kno what to do.....it keeps freezeing on me...
I've been searching for a solution all over the place for this one but haven't had any luck.
This has happened a couple of times since flashing 4.0.4, and I have tried all the fixes I can find but none help me.
So here is what happens:
I flash 4.0.4, and then partition my SD card (Kingston 8GB class 4) with the sdparted script (I've tried but ext4 and ext2 with the same results). Next I flash the AeroBlack theme (I've also had the problem without the theme).
At this point everything seems to be working fine, and I start installing apps. Then for some reason, that I haven't been able to isolate yet, after a reboot it will pop up with the "SD Card Removed" message, yet I haven't touched the SD card. After that my apps are gone, but I am able to get them back normally with another reboot. I may have had to do a "repair ext" from the recovery console once or twice.
After I get the phone reading the SD card again, all of my apps reappear and are shown as installed in the market. However, when I try and run any of them, they will either force close or error out in some other way (i.e. pandora says it cannot connect and exits). fix_permissions doesn't help. If I uninstall/reinstall each app, they start working again, but that will be a cumbersome process if this continues to happen, plus I lose all of my app settings.
So I am at a loss for what else to try. I would really like to find a solution to this as I love how much better the mod works, but I've reflashed my phone several times a day over the past week trying to get to a stable load.
Frequently Asked Questions said:1. Do I have to wipe?
You shouldn't have to wipe if coming from a JF ADP-based ROM, otherwise, probably. If weird things are happening, try wiping. You can also try the permission fixer script linked above. If you are coming from an HTC-based ROM like Hero or Sapphire, you are going to have to wipe.
2. Will you include the HTC Dialer/HTC Mail?
No, because I won't be shipping the full HTC-modified Android core (it's not open source), which these apps depend on. I do include the "Work Email" application which is the HTC Exchange client.
3. Will this work on the Magic?
It will work on Dream (G1) or Magic 32B (myTouch). I plan to support 32A devices soon.
4. How do I set up apps-to-sd?
You need to create a second partition on your SD card in the ext2/ext3/ext4 format. Search the forums if you don't know how to do this. Once created, the ROM will move your apps automatically and new apps will be installed to the SD by default.
5. How do I install MyFaves?
Look here: http://forum.xda-developers.com/showthread.php?t=542267
6. Will you include feature X, Y, or Z?
Maybe, ask me about it.
7. How do I convert to Ext3?
Reboot into recovery (home + power), drop to a console (Alt+x), and enter: "upgrade_fs". Reboot and you will be at ext3. This requires my recovery image listed above.
8. Can I use Ext4?
Yes, the kernel supports it (with delayed allocation fixes) and the required tools are there. You'll need to do the conversion manually, though.
9. How do I enable the HTC_IME?
Go into settings->Locale & text and disable "Android Keyboard" and enable "Touch Input".
10. Can I tether with this?
Yes. I recommend using Wifi Tether for Root Users
11. I want to switch back to ext2.
Reboot into recovery (my recovery image), drop to a console (Alt+X). Remove the journal with "tune2fs -O ^has_journal /dev/block/mmcblk0p2". You should then fsck with "e2fsck /dev/block/mmcblk0p2".
12. Will you include feature XXX from Hero?
No. Most of the HTC apps in Hero require the heavily modified closed-source Android core which I won't be including.
13. My /system/sd is read only and/or didn't upgrade to ext3!
Your filesystem is probably corrupt. Boot into Recovery 1.2+ and run a filesystem check from the menu. If it tells you to run it manually, drop to a console (alt+x) and run "e2fsck /dev/block/mmcblk0p2".
14. Is ext3/ext4 safe for my SD card?
Probably, unless your card is very old and does not support wear leveling. Use Google and decide for yourself.
15. I have problems with force closes of paid apps and have to reinstall my them after a no-wipe upgrade!
Run the "permission fixer" script. It is included in this build as well as Recovery 1.2+. Just execute "fix_permissions" from a terminal or the recovery console and reboot.
16. Can I use your work in my own ROM?
Of course, I am all about sharing! Just give credit where credit is due.
17. It's taking forever to boot!
The first boot will take longer than normal because dexopt needs to run. If you are nervous, connect USB and run "adb logcat" to watch the progress.
18. My phone rebooted by itself!
Possible kernel panic or oops. Please get me the output of "cat /proc/last_msg" when you reboot so it can be debugged.
19. My camera is black and white only!
You have settings left over from the old Android camera. Just go into the Camera, hit menu, settings, then "reset to defaults".
20. My auto-rotate/accelerometer isn't working!
Not really the fault of the ROM, but here's how to fix it: Go into recovery, drop to console, "mount /data", then "rm /data/misc/akmd* /data/misc/rild*" and reboot.
21. What about swap space?
As of 4.0, Compcache is activated by default unless a userinit.sh script is present. Search the forums for information on how to create a userinit.sh to activate swap.
22. Will you include the Flash Player from Hero?
No, because it's tightly coupled to the Hero Browser, which is tightly coupled to the Hero Framework. It's not easily portable at this point. Run Hero if you want it. Otherwise, we will have to wait for something more compatible.