Hi
Perhaps this is an unusual question: can be dalvik cache be manually built without rebooting?
I explain:
I have a "critical" link2sd usage (many more apps linked respect to internal memory capacity).
I have some problems with my terminal, which is unstable (sometimes freezes after boot, see this thread); due to this I safety boot without SD inserted; then I insert SD, in link2sd i relink app files, it does correctly, but apps obviously still do not work due to dalvik cache is not built (but symlinks are present).
Just to try, which is the command that makes dalvik cache building at boot, and after an apk installation(something like dexopt...)?
Can I try to apply it when device is in use?
If I reboot when I suffer this instability problems both /data partition could be filled by .dex files and the device could freeze after boot.
Thanks (and tell me if this is bull****)
Related
I read in a lot of threads where people recommend wiping "cache and Dalvik-cache" to fix a variety of problems. I know apps have their own cache but does the Eris have a cache other than Dalvik? I'm using GSB 3.8 and I don't see another cache, but maybe I'm not looking in the right place.
Dalvik-cache files are split up into two different locations. The dex files for your system apps are in /cache/dalvik-cache and the dex files for your installed apps are in /data/dalvik-cache. The popular cache2cache script moves the files from data/dalvik-cache to the cache partition to provide more space on the data partition.
Besides dalvik-cache files, the /cache partition is also where market apps are temporarily downloaded before being installed.
Hope that helps.
OK, I use Zach's C2C script so clearing one dalvik location clears both and I was aware of the temp download location also. I guess I'm not missing anything, but I wanted to be sure. Thanks.
Hi,
I am using CM9 beta 8 by maclaw and team with a 32gb ext card formatted as follows using CWM 5
4gb sd-ext
1gb swap.
I also am using the d2sd script by ungaze.
I have about 500mb worth of files in sd-ext.
Sometimes when my phone is on for too long or when i open and close too many apps it will reboot randomly, and if i decide to turn it off, wipe cache and dalvik, it will just boot to a black screen and even after 2 hours its not booting..
Can anyone help me?
EDIT:i found out that the cam wipe dalvik removes the link to the dalvik as well, so when the kernel boots it loads the dalvik from the preset location in the NAND, and when it cannot find it, (due to the init.rc not running to link it, init.rc loads AFTER this process), it will not boot.
I had to do a nandroid restore and used adb to manually cd into the dalvik-cache and rm * then it finally booted.
But sometimes even after clearing the dalvik, the phone will reboot randomly into the CM screen and back again.
Any ideas?
How much of the ritual of rom management is actually necessary and how much is just passed on wisdom based ultimately on nothing? Is there really any benefit to wiping a partition more than once, fo example? Some people suggest all sorts of voodoo to make sure a rom gets installed right and everyone is quick to blame a failure to follow the ritual perfectly for any shortcomings of the rom.
Just curious. Either way - it is interesting to have these flashing rituals. The ritual is different for each device.
Steps to flashing ROM -
1. Wipe all partitions ONCE (but make sure you wipe them all).
2. Flash ROM first, flash gapps if not included, then flash any other zips of apps/mods/whatever else that you need.
3. Done.
A lot of the tips that people give are misleading. You DO NOT need to wipe more than once. When you format a flash drive on your computer, do you format it 2-3 times just 'to make sure everything is wiped' or do you just format it once? Same thing for the NAND flash memory of phones/tablets. One format of the partitions will wipe them clean.
There's no such thing as a wait time for 'letting the ROM settle in'. You flash a ROM, reboot, wait for dalvik cache to rebuild, wait a minute or two after boot for all the auto-start apps to load (especially if you have a single core phone with low RAM) and use away.
You don't have to wipe cache+dalvik cache each time you flash an update of your ROM. Android automatically detects which apks have changed and rebuilds the dalvik cache only for them, rather than unnecessarily deleting the whole dalvik cache and rebuilding the same stuff again. Google 'android auto dexopt-ing' for more info.
You don't have to wipe cache+dalvik after flashing a new kernel, because those are for apps and aren't related to kernel.
The correct wiping order is -
1. Format /boot
2. Format /system
3. Format /data
4. Format /cache
Some devices have additional partitions so you would need to format them too if necessary, but for most devices these are the standard partitions to wipe. Some recoveries have a 'format all partitions (except SD card)' option which does all this at once, most recoveries require you to format them manually. In most recoveries, the option for formatting data is called 'Format data/Factory Reset'. This does the same thing as running Factory Reset in the phone settings, i.e. it formats /data and /cache. So depending on your recovery, you might not need to format /cache after formatting /data. Many people advise to format dalvik cache after formatting data. This is completely unnecessary. Dalvik cache is just a folder in /data and in /cache, so when you format /data and /cache or do a factory reset, it is wiped too. If you wipe dalvik cache after formatting those partitions already, you're doing nothing other than deleting a non-existent folder.
You don't need to 'calibrate' the battery after a new ROM flash. Battery calibration as it is called does nothing but delete a system file called batterystats.bin which contains info about the running apps, percent of battery they use and the battery history. This file is anyway reset whenever you charge the device fully, so you're essentially 'calibrating' your device each time you fully charge it.
https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT
Last one, you don't need to fix permissions each time you flash a ROM/ROM update. Only run it if you're getting a lot of app FCs.
Sent from my Desire HD using xda premium
I agree with Sashank, use the order but personally (again my own personal preference) I boot the ROM first after flashing ROM /or GApps then I reboot back into recovery to flash anything that needs to be flashed. Also when using 4EXT Recovery (preferred/best recovery for our Desire HD) there's an option to wipe all partitions except for SD Crad, I usually use that 3 time to make sure my device is as clean as possible
Hey friends,
I Flashed again gingerdx31b(mimmi) after creating a ext partition through CWM and I activated the DC2SD after that I install couple of apps and rebooted my phone and suddenly FC errors are pop up and only black screen, I did it again wiping all but it still happens so I decided to Flash again wiping all active A2SD and there are no errors with it.
Can some one help me to activate DC2SD without that errors! I need it because I saw some one telling its save more system memory more than A2SD!
Rockmins said:
Hey friends,
I Flashed again gingerdx31b(mimmi) after creating a ext partition through CWM and I activated the DC2SD after that I install couple of apps and rebooted my phone and suddenly FC errors are pop up and only black screen, I did it again wiping all but it still happens so I decided to Flash again wiping all active A2SD and there are no errors with it.
Can some one help me to activate DC2SD without that errors! I need it because I saw some one telling its save more system memory more than A2SD!
Click to expand...
Click to collapse
#Ap2sd moves installed apps from data partition to sdcard & data partition is located at root/data
#Dc2sd moves dalvik-cache from data partition to sdcard & dalvik is located at root/data/dalvik-cache*
#system partition is where rom installs & it's located at root/system
1-data partition size is ~200 mb
2-data partition is not using system partition(they are separated)
3-dalvik-cache uses at MAX 30 mb of your data partition
4-dc2sd makes phone,app start-ups slower... phone will be less responsible & strange fc errors appear ...
5-it's better to wipe cache instead of moving dalvik to sd
6- use android's native app2sd (no partitions needed, move from settings /app manager / tap on any app & press on "move to sdcard " option)
*not 100% sure about info
Sent for xda via tapatalk
# always wear your seat belt as it saved my life...:beer:
# sorry for English
I'm running Marshmallow and have a 64GB internal microSD card mounted as "adopted storage". When I tell TWRP (3.0.2-0) to clear the Dalvik cache, only a few apps (about 9) get regenerated ("optimized") on the next reboot. The remaining 100+ apps are not optimized on the next reboot. I've tried deleting the /data/dalvik-cache folder myself and get the same results. So, I assume that the oak/etc. files for the other 100+ apps are stored "somewhere else". Any idea where?
Thanks.
(PS: Yes, I know Marshmallow is an Art system, not a Dalvik system. The term "dalvik cache" is used in many places as a generic term to refer to the place where Android keeps optimized apps. Marshmallow still uses the /data/dalvik-cache folder for this purpose. Marshmallow's obviously just not as ... consistent about using it as earlier versions of Android.)