I just thought I should mention don't do it!
If you really need to keep your cache tidy, especially on Marshmallow, do it from Recovery. I have tried cleaning the cache from both CCleaner apk and ASC Mobile Security apk and they cause app optimization to malfunction and the device to freeze and then bootloop. I'm not sure if this is CM 13-based specifics but if it is its a bug that needs addressing. Cleaning the cache from one of these apps causes a bootloop, of which is correctable by:
Power phone OFF
Hold down VOLUME DOWN and press POWER
Select RECOVERY MODE by selecting it from the blue box using the VOLUME UP and VOLUME DOWN buttons and pressing POWER when you see RECOVERY MODE .
Follow the instructions for your custom recovery ( Philz, TWRP, CWM, etc. ) to clean the cache and dalvik cache partitions.
Reboot to system.
When done, you should see Optimizing app x of xxx and you should be able to resume use without losing your data. Immediately uninstall any automatic cache cleaners and resume normal operation. Don't repeat the same mistake.
I either do it manually, by deleting it in root explorer and rebooting or I use the SD Maid app. never ever an issue. and BTW, its not an issue with stock or aosp, using apps to clear cache. that sounds like a user issue or a cm issue.
Related
Anyone know how to clear the dalvik cache on a hero without Root access? Tried via ADB and will not remount without root. Any help would be most appreciated. Thanks Everyone
turn off your phone press home plus power you'll see a phone press home plus power again. choose cleaar cache
Many thanks!
Dalvik / Cache
So I'm a tad confused between dalvik and cache. Are they the same thing? I've seen people refer to clearing "dalvik cache" and both individually. Also, when you do a factory reset from the recovery menu (home + pwr), does that wipe the data and clear the "dalvik"?
I'm curious cause I would like to completely wipe everything off of my phone and start a new and I'm not quite sure the best steps to take
Thanks!
Stephen
This is mostly for anyone who runs kifno's rocksteady ROM, along with his scripts. Essentially, I am not sure how to install both of them together properly. It seems the instructions kind of overlap? And I do not want to wipe anything at the improper time. So if someone could edit these instructions so I could follow them in sequence, I would be grateful. If it makes a difference, I will be flashing the uncapped kernel (768mhz).
P.S. - I've been running xda roms for about a year now, and just wanted to say thank you for all your hard work and contributions to the open-source community. To ALL developers
ROM INSTRUCTIONS
Instructions:
1. Backup EVERYTHING (SD Card, Titanium Backup, Nandroid)
2. Wipe EVERYTHING (Data/Factory Rest, Wipe Cache, Format Boot, System, Cache, and Data, Wipe Dalvik)
3. Download and Copy RockSteady & Gapps to your sdcard
Get Rock Steady Here
Get Gapps Here
4. Flash RockSteady and Gapps and Reboot
5. Skips gapps setup and reboot into recovery and wipe data, cache, and dalvik again
6. reboot into system
7. After setting up gapps, in the menu > sense settings > ui setting > check tink ab and make the scale factor 1 instead of 7
8. Long press home screen and create a custom widget with phone as the activity. Then click the phone icon and us es file explorer or gallery and use the transparent.png I provided for you on the root of your SD card. Okay the custom widget and the drag and drop it over the phone button. Do the same for right sense dock button (choose a custom activity of your choice)
9. Add the sense clock by using the fancy widget widget i provided for you.
10. Choose a new wallpaper if you wish by picking one of the sense wallpapers I provided for you on your sdcard's root directory.
11. Please see here about widgetlocker. Please purchase this app from the market to use as the sense lockscreen. I REALLY RECOMMEND IT. And you can easily disable the default lockscreen once you start using this app by going into the cyanogenmod settings > tablet settings > and checking disable lockscreen.
SCRIPT INSTRUCTIONS
Installing Instructions (Recovery Menu):
Difficulty: Easy
Download the Kifno Tweak's Universal Script v1.5 from below:
Get the Capped 691mhz Build Here
Get the Uncapped 768mhz Build Here
Charge phone to 100% and leave on the charger during this process
Put the .zip on the root of your sd card
Reboot into recovery
Backup Everything (Apps, SD Card, etc) & Wipe Everything (Data, Sd-Ext, Cache, System, Boot, Dalvik-Cache)
Flash Rom
Fix permissions if using clockwork recovery
Flash your capped or uncapped build
Delete data, cache, and dalvik
Reboot
Reboot Recovery
Delete data, cache, and dalvik
Unplug Charger and do not plug back in until your phone dies.
Reboot into recovery once it is dead by connecting charger.
Wipe battery stats
Charge to 100% and repeat the discharging, wiping, and charging process about 3-5 times
Enjoy the battery life and performance
The red is the confusing part. Thanks!
Ill post instructions in about an hour or two. Glad to see you're using my work though and sorry for the confusion.
Sent from my HERO200 using XDA Premium App
The Muiu Camera Doesnt Work :[
backup everything
wipe everything
flash rom
flash gapps
flash v1.5 stable
reboot into rom
skip gapps and reboot recovery
wipe data,cache, and dalvik
reboot into rom
then follow my set up instructions for my rom after that process
enjoy
also miui camera works on 4-21-11 it does. are you using the latest version?
Yes I amm
Sent from my HERO200 using XDA App
Jurellz said:
Yes I amm
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Oh sorry didn't see your reply but try the latest one now
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 ?
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.
Hello guys,
My Huawei Mate 20 lite has just updated to latest firmware (SNE-LX1 8.2.0.138(C432))
Now all application notifications are gone from the drawer and the lock screen. I have tried enabling all possible settings, including ignoring battery saver, allowing to draw over other apps, etc.
All messengers get just a dot on the icon - no banner, no lockscreen notification.
Spotify and Poweramp have no drawer and no lockscreen control as well - to skip a song, I need to unlock the phone and open the actual application.
I did honestly try to google, disabled smart lock (no face unlock present) and smart cover - no luck.
I have tried re-installing Spotify - no result.
Any ideas?
Worked just fine up until the firmware update.
This can be caused by a bad configuration in settings or an application that affects notifications.
If you really tried everything and nothing worked, I recommend you factory reset the phone from the Recovery mode. You have to enter the recovery mode and factory reset the phone, then clean the cache (Wipe Data / factory reset & Wipe cache partition).
This can be an operating system error that occurred when updating the phone. Resetting the phone and cleaning the cache eliminates the logs and settings. It also makes the system start properly correcting any system error.
Obviously this removes everything you have on the phone. I recommend it if absolutely nothing works.
CamoAndres said:
This can be caused by a bad configuration in settings or an application that affects notifications.
If you really tried everything and nothing worked, I recommend you factory reset the phone from the Recovery mode. You have to enter the recovery mode and factory reset the phone, then clean the cache (Wipe Data / factory reset & Wipe cache partition).
This can be an operating system error that occurred when updating the phone. Resetting the phone and cleaning the cache eliminates the logs and settings. It also makes the system start properly correcting any system error.
Obviously this removes everything you have on the phone. I recommend it if absolutely nothing works.
Click to expand...
Click to collapse
Thanks for suggestion, but I couldn't say it's a fix. I'm rather trying to check if anyone else is having the same issue with the latest firmware and if there is an actual solution (ok, selling this phone and buying a normal one is another considerable option)