Guest brookergray Posted January 22, 2012 Report Posted January 22, 2012 Make sure that you mounted system in "mounts and storage" otherwise it's not going anywhere. And DO NOT WIPE dalvik. It's the most idiotic thing one can do and recommend. Everyone who does it is an idiot whose phone should be confiscated and given to people with brains. Just sayin'.
Guest flshg Posted January 22, 2012 Report Posted January 22, 2012 Make sure that you mounted system in "mounts and storage" otherwise it's not going anywhere. And DO NOT WIPE dalvik. It's the most idiotic thing one can do and recommend. Everyone who does it is an idiot whose phone should be confiscated and given to people with brains. Just sayin'. Would be useful for you to explain how wiping the dalvik cache is idiotic, as it sounds like it could have a major impact on what everyone does in future.
Guest brookergray Posted January 22, 2012 Report Posted January 22, 2012 (edited) Would be useful for you to explain how wiping the dalvik cache is idiotic, as it sounds like it could have a major impact on what everyone does in future. Every time the system starts it checks if the apk or the jar files that the dalvik file caches is still the same. If it's changed than it's deleted and a correct one is recreated. You can watch this happen in logcat during boot. If this didn't convince you than check inside the framework-res.apk. There is no classes.dex file in there thus there's nothing cached in dalvik-cache. I can dig up a more technical explanation if you want. RELATED When you're flashing a rom you're wiping not because of dalvik but because of the possibility that some framework stuff has incompatible databases/files in data that they would try to load and thus cause errors. Edited January 22, 2012 by brookergray
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now