Related
Hi fellow blackers,
My optimus black was on Nova Rom 2.2 v8:
http://forum.xda-developers.com/showthread.php?t=1161015
And I flashed it to v20n:
http://forum.xda-developers.com/showthread.php?t=1441901
I followed the instructions specifically these two before proceeding with the zip install.
1. Wipe Data/Cache (if not wiped, might cause problem)
2. Advanced > Wipe Dalvik Cache (same as data/cache, might cause problem)
After flashing, I can't seem to install any app from Market. It says that I have insufficient space on device.
So did some searching (google and here on XDA):
Here are their suggestions:
1. Install Marketfix - unfortunately, I can't install this because it is already saying I have insufficient space.
2. Clear market cache - after clearing (cache and data), I still says insufficient space
3. Uninstall market update - Going to settings - Application - manage application then selecting Market, I don't see any uninstall button. Just Force close, cancel and clear cache, clear data..
4. Finally I saw knzo's supposedly fix for this: Something to do with file system (nova is on EXT4 while stock is on EXT3)
http://forum.xda-developers.com/showthread.php?t=1212370&highlight=insufficient
I wasn't able to try option 1 because the file was removed on all file sharing sites.
Options 2 and 3 - restore factory settings isn't working. The phone is not doing anything after I click Erase everything. It just hangs
Any other suggestions?
Try reflash ROM with wipe all data and cache in CWM including dalvik cash and formating partitions in "mounts&storage".
Or this!
Try wipe cache and dalvik cache...worked for me
hmm pardon me, but how do I boot into recovery? I tried powering the device on while holding volume down (also tried up and G button) but it didnt reboot into recovery.
Artyomperec said:
Try reflash ROM with wipe all data and cache in CWM including dalvik cash and formating partitions in "mounts&storage".
Or this!
Click to expand...
Click to collapse
Since I can;t install anything (rom manager etc.), I think I needed to do what you advised.
I was able to flash the stock then started up from there
Since I can;t install anything (rom manager etc.), I think I needed to do what you advised.
I was able to flash the stock then started up from there
Click to expand...
Click to collapse
Have you tried flash this MOD for enter in recovery from power off phone pushing "G" button, not pressed and hold, but pushing every time when boot, work for me!
just try this
dsokua said:
Hi fellow blackers,
My optimus black was on Nova Rom 2.2 v8:
http://forum.xda-developers.com/showthread.php?t=1161015
And I flashed it to v20n:
http://forum.xda-developers.com/showthread.php?t=1441901
I followed the instructions specifically these two before proceeding with the zip install.
1. Wipe Data/Cache (if not wiped, might cause problem)
2. Advanced > Wipe Dalvik Cache (same as data/cache, might cause problem)
After flashing, I can't seem to install any app from Market. It says that I have insufficient space on device.
So did some searching (google and here on XDA):
Here are their suggestions:
1. Install Marketfix - unfortunately, I can't install this because it is already saying I have insufficient space.
2. Clear market cache - after clearing (cache and data), I still says insufficient space
3. Uninstall market update - Going to settings - Application - manage application then selecting Market, I don't see any uninstall button. Just Force close, cancel and clear cache, clear data..
4. Finally I saw knzo's supposedly fix for this: Something to do with file system (nova is on EXT4 while stock is on EXT3)
http://forum.xda-developers.com/showthread.php?t=1212370&highlight=insufficient
I wasn't able to try option 1 because the file was removed on all file sharing sites.
Options 2 and 3 - restore factory settings isn't working. The phone is not doing anything after I click Erase everything. It just hangs
Any other suggestions?
Click to expand...
Click to collapse
2 days ago I got this problem too, but SOLVED when I upgrade to CWM 5.0.2.6 (from CWM 4.0.1.5) then re-flashing with redy2006 V20N
what version CWM u have?
dsokua said:
hmm pardon me, but how do I boot into recovery? I tried powering the device on while holding volume down (also tried up and G button) but it didnt reboot into recovery.
Click to expand...
Click to collapse
just try adb reboot recovery from your PC to go to CWM
Just for be able to post new thread. Sorry.
kingtawon said:
2 days ago I got this problem too, but SOLVED when I upgrade to CWM 5.0.2.6 (from CWM 4.0.1.5) then re-flashing with redy2006 V20N
what version CWM u have?
just try adb reboot recovery from your PC to go to CWM
Click to expand...
Click to collapse
Ooh, I didn't update my CWM so I think it was on 4.x.x.x, Was able to flash and install apps in 5.0.2.6
Anyway, Im on temasek kangs build now
dsokua said:
Ooh, I didn't update my CWM so I think it was on 4.x.x.x, Was able to flash and install apps in 5.0.2.6
Anyway, Im on temasek kangs build now
Click to expand...
Click to collapse
so, still got same issue ?
The purpose of this thread is to host a location and continue support for a really neat ext4 mod.
IMPORTANT: If you flash the no data limit mod you need to do it after every update or your data, which won't be lost will be hidden by the contents of the data data partition.
I'm going to keep this brief. The original thread was closed so I wanted to have a new location where everyone can find the files. But this is a new thread for Jermaine151's and my EXT4all mod.
Below is the original thread which already has a lot of useful information:
http://forum.xda-developers.com/showthread.php?t=1315372
Here is where you can find most of if not all the EXT4All files:
http://dinc.does-it.net/EXT4_Mods/
Sorry this thread isn't too organized but I threw one together so people could post on it with their comments.
This mod should work on all AOSP ROMs including ICS ROMs and MIUI. It's been confirmed on CM7 and MIUI but I've also tested on CM9. It should also work on all Sense ROMs and does work on every Sense ROM I've tested. Be sure to flash a newer version of the gingertiny kernel if you use a Sense ROM as the kernel version flashed to add ext4 compatibility is out of date.
V2 Mods with TWRP 2.3+ support and proper support for filesystem tweaks for ROMs that are already set to use ext4 found below:
V2 EXT4All Mods
FAQ
Q. How do I know if the ext4 mod(s) worked?
A. The best way is to do the following from terminal:
su
mount | grep /data
It should show a line with /data and ext4 and, if it has the no data limit, also a line with /data/data and ext4. If you're on an ICS/JB ROM it will show ext4 anyways. The best way to tell with the new version of the mod is to see if noauto_da_alloc shows in the results of the above commands.
Hey tiny, thanks for opening this btw. Wasn't sure if I should post here or on ur kernal thread but my girls dinc was having the data limit problem so I wiped cache and dalvic, flashed ext4 no data limit normal dalvic then flashed ur newest kernal (3/11 date). And I have been having the hardest time keeping her phone stable. I've tried every governor sav2, interactivex, ondemand, even sa, tried deadline, sio schedulers, even tried raising the voltages to a post u had on ur kernal thread, page 85 or something (wasn't sure if I should set the min and max of the voltages for the same thing, but that's wat I did). But she still says its very unstable. She's running stock+ 3.01 and she DOES have a cheap ebay battery in her phone, not quite sure how much that plays a role in the problem. She's at work right now so I can't pull any logs, but I know ull probably need a logcat? Or I dunno. If u could gimme directions on anything I should post to assist u. And I'm not overclocking at all for the record. On stock kernal she never had any stability issues, uptime of 200 hours+. But urs is definitely snappier and that damned data limit is the main reason y I even switched her over to begin with. Thanks tiny in advanced for everything u do!!!
Sent from my ADR6400L using xda premium
I'd prefer the kernel thread.
And I'll need a last_kmsg. Just copy /proc/last_kmsg with root explorer or another file explorer and attach it to a post on the kernel thread. Since you most likely eliminated undervolting by using the voltages on page 85 of the kernel thread, then it's possible the battery has an effect. I've heard that poorly made batteries can cause issues that stock batteries don't have so further deviation from stock may have an influence. Either way, I'll look at that log once you get it. Make sure not to battery pull until you can copy that log and try to do it within 24 hours of the last reboot to be safe.
the following thread contains very simple and plain english directions for using this MOD. it helped me, and it was my first time rooting. Thanks also to tiny4579 for posting this new thread.
http://forum.xda-developers.com/showthread.php?t=1488351
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
funkpod said:
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
Click to expand...
Click to collapse
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
I've been running various ICS roms and switched back to Warm rev 58. Upon installing the latest kernel and the Ext4 mod. I am unable to install apps. Any idea what may be causing this. I wasn't sure if it was the rom or not do I did an update with SVN and installed that with the same results. I have a nandroid with just the rom and all the apps I want, but would like to overclock and the stock kernel won't allow. And would also like to be able to install a new app should one arise.
Sent from my HTC Droid Incredible using xda premium
tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks, how do I generate the logcat?
Sent from my Incredible.
Aw yeah.
Ok. It's not the kernel. Installed the most recent and everything is fine. Installed the ext4 with dalvik moved before that and rebooted and apps were missing and it wouldn't let me install new apps and some of my previously installed apps were missing. When I tried to install them it said it was going to replace an existing app and then said app not installed.
Any ideas???
Sent from my HTC Droid Incredible using xda premium
tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
funkpod said:
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
Click to expand...
Click to collapse
Sorry I just dont have time tonight to explain. Maybe tomorrow.
Sent from my Galaxy Nexus using Tapatalk 2
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
funkpod said:
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
Click to expand...
Click to collapse
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
funkpod said:
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
Click to expand...
Click to collapse
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Sirknifealot said:
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Click to expand...
Click to collapse
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
funkpod said:
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
Click to expand...
Click to collapse
If you're wiping I don't see the point of fix permissions as it will fix it back to what it already probably is. I haven't fixed permissions in a while flashing ROMs and I've been ok. Force closes that I got that made me try fix permissions then weren't fixable with fix permissions anyway.
I would wipe, flash ROM, flash kernel if desired, then mod. Though if it's a sense ROM I would switch the order of kernel and mod flashing. So really you can do: ROM, ext4all mod, kernel after a wipe if you choose to wipe to fix your issue.
hey, flashed over to RC3! so far so good, slowly adding things back! will let everyone know how it goes!
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
omniatic said:
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
Click to expand...
Click to collapse
No, if you actually format the device like when the system runs the format command the filesystem will be ext4. However in your example of CM9 the ramdisk mounts data and cache as ext4. This will actually have a minor improvement over ext3. It'd still be an ext3 filesystem but loaded as ext4 so there's minimal performance gains.
In reality any time you flash a ROM or a boot.img type kernel (not any of mine) you will use the ramdisk of the ROM and reverse part of the effects. But since ROMs like CM9 and newer CM7 versions mount as ext4 you'll still see data and cache showing as ext4. Make sense? I never really did explain it properly before I think.
Hey guys,
I've had CM 7.2 Stable for a couple weeks on my phone. It was
working great until a few days ago when I tried to tweak the CPU
settings a little. Right now i'm using
Governor Smartass V2- Min 352 MHz, Max- 691 MHz
What CPU settings are you all using with CM 7.2???
Since I tweaked it from the default cpu settings I've been
experiencing screen freezes. Sometimes the trackball will work
sometimes it won't. It primarly happens when my phone has been
sitting idle for some time. I'll try to get it out of the lock screen
but it won't respond to my touch. I've tried rebooting, battery pull,
I've also tried lowering and raising the min and max settings. It'll
work periodically and then it will just freeze. Funny thing is I
don't know what the "default cpu settings" were set at. I've been
looking around a lot but couldn't find much.
Thanks!
I have never seen an issue here with 691. My experience though is that smartass 1 or 2 do not work as well as ondemand.
691/352 ondemand
Sent from my HERO200 using Tapatalk 2
kjjjjshab said:
I have never seen an issue here with 691. My experience though is that smartass 1 or 2 do not work as well as ondemand.
691/352 ondemand
Sent from my HERO200 using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot for the input. I'll try to go back to On Demand. If that doesn't work then maybe I'll just re-flash the ROM.
Tell me do you have any other overclocking apps installed?? Or any kind of app that effects the lock screen??
#Root-Hack_Mod*Always\=LTE
laie1472 said:
Tell me do you have any other overclocking apps installed?? Or any kind of app that effects the lock screen??
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
Hi-
I looked at my list of apps to be sure and no extra overclocking app installed. I'm using the default "CyanogenMod Settings" to get to "Performance" and setting the cpu from there. I have not installed any extra lock screen apps or 'lock screen security app' other than what comes preinstalled on CM 7.2. I don't believe I have any app that effects the lock screen. All of the apps I have are fairly simple, mostly developed by google inc. and nothing that tweaks or alters the device (I have Maps, a Speedometer, Navigation.) I try to keep them all closed though with the Task Killer app I downloaded.
I have switched back to OnDemand. So far nothing has changed and it's still stalling up (even though it's only been about an hour.)
Thanks a lot.
Uninstall the task killer. Reboot to recovery. Wipe cache, and davlik cache. See if that helps at all.
#Root-Hack_Mod*Always\=LTE
Update
laie1472 said:
Uninstall the task killer. Reboot to recovery. Wipe cache, and davlik cache. See if that helps at all.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
So I tried raising the minimum CPU And my phone would not respond at all in the lock screen the next morning. So I had to do a manual recovery and wiped the davlik cache and cache like you suggested (thank you Laie1472). Rebooted. Was able to navigate through my phone for about one minute and it froze again.
So I did a full wipe in recovery ( thanks to senior member SleepyEDB)
I re flashed cm 7.2 and so far it's running 'better' it still freezes every now and then in the lock screen and other places when I wake it up, but not as often. We'll see how it works tomorrow. Ive been searching through a couple other forums and one guy with a similar problem took his phone apart and found it was a hardware problem. Maybe I should send it back (BestBuy refurbished).
SleepyEDB said-
Doing a full wipe in recovery
Do the following steps in Recovery to perform a full wipe:
Wipe Data/Factory Reset
Wipe Cache Partition
Mounts and Storage -> Format /system
Mounts and Storage -> Format /boot
Advanced -> Wipe Dalvik Cache
To do a 'dirty wipe', only wipe the Cache Partition and Dalvik Cache, steps 2 and 5.
That worked for ONE day
brentmxt said:
So I tried raising the minimum CPU And my phone would not respond at all in the lock screen the next morning. So I had to do a manual recovery and wiped the davlik cache and cache like you suggested (thank you Laie1472). Rebooted. Was able to navigate through my phone for about one minute and it froze again.
So I did a full wipe in recovery ( thanks to senior member SleepyEDB)
I re flashed cm 7.2 and so far it's running 'better' it still freezes every now and then in the lock screen and other places when I wake it up, but not as often. We'll see how it works tomorrow. Ive been searching through a couple other forums and one guy with a similar problem took his phone apart and found it was a hardware problem. Maybe I should send it back (BestBuy refurbished).
SleepyEDB said-
Doing a full wipe in recovery
Do the following steps in Recovery to perform a full wipe:
Wipe Data/Factory Reset
Wipe Cache Partition
Mounts and Storage -> Format /system
Mounts and Storage -> Format /boot
Advanced -> Wipe Dalvik Cache
To do a 'dirty wipe', only wipe the Cache Partition and Dalvik Cache, steps 2 and 5.
Click to expand...
Click to collapse
So that was short lived. Once I did the Full wipe around noon it worked almost perfectly until for about 12 hours. I think it froze right before I went to bed. I woke up and it was completely frozen at lock screen again. I did another full wipe and reinstalled cm 7.2 and it froze again. So I did a second full wipe and it is now working. I really hope it will accept my nandroid backup if it freezes again because it's A LOT quicker. Than doing a full wipe.
Hope this helps anybody who goes through the same thing.
hepl me s5830 3g problems rom 4.1.2
kauhai92 said:
hepl me s5830 3g problems rom 4.1.2
Click to expand...
Click to collapse
Please state your problem clearly..
sax0406 said:
Please state your problem clearly..
Click to expand...
Click to collapse
I used the rom 4.1.2 3g unstable and was restarted
I've found the rom you've probably installed
http://forum.xda-developers.com/showthread.php?t=2011671
From the thread i read:
sdcard with ext4 partition is required. /data partition is mounted to sdcard ext4 partition. NO ANY link2sd scripts are needed in this build!
Click to expand...
Click to collapse
Maybe you forgot to create a ext4 partition. Try with this.
If after this the rom continue to restart, try another rom.
TheDevil000 said:
I've found the rom you've probably installed
http://forum.xda-developers.com/showthread.php?t=2011671
From the thread i read:
Maybe you forgot to create a ext4 partition. Try with this.
If after this the rom continue to restart, try another rom.
Click to expand...
Click to collapse
you to install test no ,:laugh: it has more than version 4.1.2
you test this yet http://forum.xda-developers.com/showthread.php?t=2141770
This rom is very good, you shouldn't have reboot problems like this.
Maybe you have installed this rom in a wrong way.
Try this procedure:
- Restart in clockworkmod
- Do a full reset (wipe data, wipe cache and other things), wipe dalvik cache,
- Format /system
- Install the rom
This must be the correct procedure. After install wait some minutes (usually not more than 10 minutes).
TheDevil000 said:
This rom is very good, you shouldn't have reboot problems like this.
Maybe you have installed this rom in a wrong way.
Try this procedure:
- Restart in clockworkmod
- Do a full reset (wipe data, wipe cache and other things), wipe dalvik cache,
- Format /system
- Install the rom
This must be the correct procedure. After install wait some minutes (usually not more than 10 minutes).
Click to expand...
Click to collapse
thank you
why I increased cpu machine runs slow lag
English slightly less
It's normal. OC principle.
If you increase a lot the max frequency, the cpu can't handle at this rate.
High OC increase temperature of the cpu, so oc with cautions.
For example, I use 825mhz when I need to start high-load apps (like angry birds series)
TheDevil000 said:
It's normal. OC principle.
If you increase a lot the max frequency, the cpu can't handle at this rate.
High OC increase temperature of the cpu, so oc with cautions.
For example, I use 825mhz when I need to start high-load apps (like angry birds series)
Click to expand...
Click to collapse
thanks I have followed your instructions and my s5830 not lag
I asked the command line for app terminal
English slightly less
This is to at least avoid the need to boot into CWM recovery every time
Reason:
I immediately flashed my brand new Nook HD+ with the emmc CM 10.1 three weeks ago
The vanilla CM booted in 90 seconds but that was 350 app installs ago and many uninstalls and app updates as well
If I power on the HD+ seem to always get stuck in the boot loop of the CM Logo; I wait up to 10 minutes
It seems booting into CWM recovery via N button on Power on and choosing wipe dalvik-cache allows a rebuild of dalvik-cache for the 350 apps followed by normal boot into CM 10.2
Besides the long delay is there any harm in wiping Dalvik-Cache every time I reboot or poweron?
I believe only this method and CM safe mode are the only way I know to avoid bootloops
Do I need to modify Dalvik-Cache settings/properties to fix bootloops? If not can I automate/ default into the Dalvik-Cache wipe for each poweron / reboot
BTW reason I rebooted a few times is I am still trying to struggling getting USB OTG / USB host mode working
Should I turn off USB debugging if I can not use USB OTG and I also do not use ADB?
TIA
Dave
What is CM safe mode?
The dalvik cache is split into two places. The system app dalvik cache is stored in /cache/dalvik-cache. The installed apps dalvik cache is stored in /data/dalvik-cache. It does no harm to clear those caches periodically. It just takes a while when you reboot for the operating system to rebuild them from the apks.
So you should be able to manually delete the /data/dalvik-cache folder with your file manager just before you reboot. I am assuming that is the one giving you problems. If not it, try the one in /cache.
If you know how to write scripts you can automate it.
Edit: if it turns out to be the dalvik-cache in /cache causing the problem, I have a build.prop setting to move the /cache dalvik to /data.
Sent from my Nook HD+ running CM10.1 on emmc.
Help with automating the Dalvik-Cache wipe
Thanks for the reply Leapinlar!
When I am booting into in CWM recovery and choose the Dalvik-Cache wipe is it wiping out both /data/dalvik-cache and /cache/dalvik-cache?
How long do I realistically need to wait before I can determine I am in a bootloop situation? I do wait 10 minutes but maybe less time?
Does CM 10.1 boot time dramatically increase over time or does adding apps also increase the boot time ?
I found a script on: http://smanager.wikidot.com/scripts:power-scripts[/U "Superclean and reboot "
As a newbie I would like to know which file or directory to put a subset of this script so that it automaticly runs when I poweroff or reboot via the power button even better would be how to add a popup question box asking me if I want to wipe out dalvik-cache as part of the shutdown.
TIA
Dave
leapinlar said:
What is CM safe mode?
The dalvik cache is split into two places. The system app dalvik cache is stored in /cache/dalvik-cache. The installed apps dalvik cache is stored in /data/dalvik-cache. It does no harm to clear those caches periodically. It just takes a while when you reboot for the operating system to rebuild them from the apks.
So you should be able to manually delete the /data/dalvik-cache folder with your file manager just before you reboot. I am assuming that is the one giving you problems. If not it, try the one in /cache.
If you know how to write scripts you can automate it.
Edit: if it turns out to be the dalvik-cache in /cache causing the problem, I have a build.prop setting to move the /cache dalvik to /data.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
The CWM dalvik wipe wipes both of them.
Yes, adding apps increases boot time. The operating system has to verify that the dalvik cache files match the apks. The more apks installed, the longer the boot. If they do not match, it rebuilds them. If they are missing (like after a wipe) it starts rebuilding immediately without checking. 350 apps sounds very high. Do you really need that many?
Some have said that the ability to read emmc decreases with use (kind of akin to defrag on a PC). That is what that trim controversy is all about. There is a process where that can be cleaned up with the trim app, but it has been known to brick certain Samsung memory chips (and some HD+s have them).
I don't know anything about that script or where to put it to execute on power off. You put it either in /system/etc/init.d or /data/local/userinit.d to execute on startup.
And you have still not told me what CM safe mode is.
Sent from my Nook HD+ running CM10.1 on emmc.
safe mode on CM 10.1
safe mode on CM 10.1
Press power button and then press and hold reboot option..
Phone / Tablet will ask you to boot in safe mode or normal mode..
I did this twice in the past
So the apps folder upon reboot is much smaller as most APKs are not loaded in this safe mode
I am kind of a newbie with CM but it is very nice
TIA
Dave
leapinlar said:
The CWM dalvik wipe wipes both of them.
Yes, adding apps increases boot time. The operating system has to verify that the dalvik cache files match the apks. The more apks installed, the longer the boot. If they do not match, it rebuilds them. If they are missing (like after a wipe) it starts rebuilding immediately without checking. 350 apps sounds very high. Do you really need that many?
Some have said that the ability to read emmc decreases with use (kind of akin to defrag on a PC). That is what that trim controversy is all about. There is a process where that can be cleaned up with the trim app, but it has been known to brick certain Samsung memory chips (and some HD+s have them).
I don't know anything about that script or where to put it to execute on power off. You put it either in /system/etc/init.d or /data/local/userinit.d to execute on startup.
And you have still not told me what CM safe mode is.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
[email protected] said:
safe mode on CM 10.1
Press power button and then press and hold reboot option..
Phone / Tablet will ask you to boot in safe mode or normal mode..
I did this twice in the past
So the apps folder upon reboot is much smaller as most APKs are not loaded in this safe mode
I am kind of a newbie with CM but it is very nice
TIA
Dave
Click to expand...
Click to collapse
Huh! That is a new one for me. LOL. Thanks.
If it boots faster in that mode, that tells me you have too many apps.
Sent from my Nook HD+ running CM10.1 on emmc.
Your boot loop sounds similar to the one I had for a while. It just sits at the Cyanogen Mod circle for EVER. The fix for me was to go in and disable 'quick render' in the launcher settings. (Remove the checkmark)
Will try disable 'quick render' in the launcher settings.
Aaron thanks for the info * I will see if helps my bootloop issue
I went to Trebuchet settings to uncheck 'quick render' in the Homescreen panel
TIA
Dave
Solution: quick & dirty automating the Dalvik-Cache wipe
Thanks to Leapinlar for great explanations and patience and
Kudos to Bartito for his Shutdown APK!
Just tested the instructions below on HD+ CM 10.1
Leapinlar can you please verify the commands before other users try this as I am still a Newbie to CM
after following these instructions I powered on the HD+ and the dalvik-cache rebuilt 268 APKs without needing to boot into CWM recovery
This will continue for every poweron and reboot until the script /system/etc/shut.d/rmdalvikdata is removed
The boot process is obviously delayed significantly but hopefully no more bootloops!
1) launch terminal emulator app and type these commands from the terminal:
su
mount -o rw,remount /system
mkdir /system/etc/shut.d
chmod 755 /system/etc/shut.d
echo "rm /data/dalvik-cache/*" > /system/etc/shut.d/rmdalvikdata
chmod 777 /system/etc/shut.d/rmdalvikdata
ln -s /system/etc/shut.d /system/etc/shutdown
exit
exit
2) please, download the "SystemScriptsExecutor-cwminstaller.zip"
from: http://forum.xda-developers.com/showthread.php?t=1387692
Note: I saved it the zip file to the MicroSdXc card
3)install SystemScriptsExecutor-cwminstaller.zip from CWM recovery on Nook HD Plus.
Note: I actually used vi on term with a USB keyboard to create /system/etc/shut.d/rmdalvikdata
and I am not sure the symlink is necessary
It looks correct. And I would leave the symlink in. The Executer may need it.
Sent from my Nook HD+ running CM10.1 on emmc.
I saw the same problem on cm-10.1.3-RC2-ovation: "wallpaper quick render" enabled causes bootup to stall on the animated logo. Clearing cache was the only way to complete with it enabled. Disabling restores the ability to boot and reboot normally.
It's a devious bug as you might only run into it days after enabling the feature. In my case, it was a few days after a fresh CM installation, having setup and installed everything the way I wanted. adb logcat didn't show anything obvious within the boot loop. I spent a while building the installation back from scratch with incremental nandroid backups attempting to find the point where things broke. Glad I found this thread instead!
It'd be nice to have it fixed as quick render makes scrolling between home pages noticeably smoother.
Aaron Camp said:
Your boot loop sounds similar to the one I had for a while. It just sits at the Cyanogen Mod circle for EVER. The fix for me was to go in and disable 'quick render' in the launcher settings. (Remove the checkmark)
Click to expand...
Click to collapse
Thank you sir! I have struggled with this and your suggestion seems to have cured the problem. I have spread the word in 2 other threads.
Wish the developer would see this. Then, perhaps, a fix might be in the future.