@ Ammyt. my nitdroid also is slow. not that slow but slow. any game hangs like fruit ninja and others. cant play lane splitter as the accelerometer always shifted to the right. any fix for these problems to make it fast and fix accelometer. i overclocked it to 900 via set cpu. install N12 via ur auto installer.kernel rc 5
@ Ammyt. my nitdroid also is slow. not that slow but slow. any game hangs like fruit ninja and others. cant play lane splitter as the accelerometer always shifted to the right. any fix for these problems to make it fast and fix accelometer. i overclocked it to 900 via set cpu. install N12 via ur auto installer.kernel rc 5
Hello, I am not Ammyt but might be able to help
try the dalvik.vm.heapsize=32m tip, the explanation is many pages before, it requires changing a config file, give it a look
I have been using NITDroid since two months. did NOT face any problems during installation.
Now all of sudden (without any modification). It shows guru meditation error when NITDroid is chosen at bootscreen.
Code:
Mounting root device mmcblk0p2 failed
And there are NO issues with Maemo. kernels: omap, powerl48, 49
at 805MHz. Android really needs more RAM to run smoothly. 512MB would be nice. 256MB of RAM results in excessive process killing in the background.
On a side note, if calls worked, N12 would be usable daily. The app you're using doesn't FC, like older versions for NITDroid.
BTW, is N14 moving to u-boot? I heard that it no longer uses a ramdisk. That would be really nice -- multiboot sometimes fails to properly flash the kernel, and I need to connect it to flasher to upload a good kernel again.
I have been using NITDroid since two months. did NOT face any problems during installation.
Now all of sudden (without any modification). It shows guru meditation error when NITDroid is chosen at bootscreen.
{..}
And there are NO issues with Maemo. kernels: omap, powerl48, 49
..you never know. Do a fresh install. Start from scratch, follow every command to the hilt..
@ammyt:
I may be on to solving this issue with multiboot, backupmenu, NIT & KP49 all intact. If i do, i'll let you know what i did so that you can add a note to your Easy Install on eMMC - Wiki.
On a side note, if calls worked, N12 would be usable daily. The app you're using doesn't FC, like older versions for NITDroid.
BTW, is N14 moving to u-boot? I heard that it no longer uses a ramdisk. That would be really nice -- multiboot sometimes fails to properly flash the kernel, and I need to connect it to flasher to upload a good kernel again.
Hi..!
Is there really an issue with multiboot that fails to load the kernel..? I mean, is it a bug in the 'multiboot' application, or is it something more basic like a limitation of the device itself which multiboot can't overcome..? I ask because multiboot itself looks great.. and IT PERFORMS with BackupMenu (which is an awesome tool).
For anyone having issues with "Force close" errors in a lot of apps in Nitrdoid (OOME usually), the following fix should help:
1. Boot into Maemo
2. Open X-Term (Ctrl+X)
3. Run 'vi /home/system/build.prop'
4. Press i to change to edit/insert mode
5. At the end of the file, add the following line:
dalvik.vm.heapsize=32m
6. Press 'esc', write ':wq'
7. Boot back into Nitdroid and you should be sweet
- Where the HELL is that file..?!?! I wish to be sweet too, very actually.
..let no one say otherwise.
