Timeline for android keeps on restarting with optimizing apps
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2020 at 13:47 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jan 16, 2018 at 10:09 | vote | accept | PareekSandeep | ||
| Jan 13, 2018 at 20:22 | comment | added | Izzy | \o/ Glad I hit the nail with my hammer :) Summed up everything in an answer as requested. Enjoy the revival :) // @acejavelin if it were a corrupted Dalvik/ART cache, the "optimizing apps" should have fixed that: doesn't that rebuild the very same cache? But definitely the backup idea is a good reminder :) And your hint of "being prepared" does not only apply to custom ROMs: being on such one often has another "backdoor" (thanks to root) a "common stock user" does not have … | |
| Jan 13, 2018 at 20:17 | answer | added | Izzy | timeline score: 1 | |
| Jan 13, 2018 at 17:13 | comment | added | PareekSandeep |
Thanks @Izzy. I was able to resolve the issue by using your suggestion. I tried some extra steps. I flashed "Aroma file manager" because that was not installed in my Phill Z recovery. One thing to note was that Aroma File Manager had to be flashed twice(using zip install from external memory); thus it allowed me access to /data/tombstones as well as /data/data/<Package_name>. I not only removed problematic packages, but also removed some clutter folders which were lying there unused. Viola! I would want to make this as answer If @Izzy can post this comment as answer. Thanks!
|
|
| Jan 12, 2018 at 21:32 | comment | added | acejavelin | On rare instances, this could be corruption of the Dalvik/ART cache, possibly even a defective eMMC storage chip. Honestly at this point I would backup any data that is important and clean install (wipe everything). Once of the things anyone on a custom ROM should be prepared to do at any time is wipe all data and reinstall, kind of goes with the whole "custom rom" way of life, so to speak. | |
| Jan 12, 2018 at 18:32 | comment | added | Izzy |
adb shell, then cd /data/tombstones. ls lists the contents. Viewing those files on-device would obviously be a bit tricky for you, so the easiest would be pulling them to your computer: adb pull /data/tombstones tombstones would pull the entire folder and place it onto your PC. Then investigate with the tools you're familiar with. Having found the culprit, from adb shell (as root) rm -rf /data/data/<culprits-package-name>. To exit from adb shell type, well, exit :)
|
|
| Jan 12, 2018 at 18:16 | comment | added | PareekSandeep |
@Izzy Seems a good suggestion. Unfortunately, I am not that of an expert and my aroma file manager is not working right now. It says no cwm/aromafm/aromafm.zip in path'. Any help on getting that installed would be awesome. I do have adb and fastboot access but I am not that expert there either.
|
|
| Jan 12, 2018 at 17:54 | comment | added | Izzy | Note that mean you will lose that app's data as well! // Please let us know if that worked out. | |
| Jan 12, 2018 at 17:53 | comment | added | Izzy |
That usually means it has trouble with one app. The cyanogenmod tag lets me assume you've got a custom recovery on the device. Boot into that. Hopefully you have either ADB capabilities there, or the recovery includes a file manager (e.g. Aroma; twrp has both). Navigate to the tombstone folder (usually /data/tombstones) and check the "trace" block of the latest files. I suspect it always mentions the same app/package-name. If so, delete that app's data directory (/data/data/<package_name>). Next boot should succeed. // Had that recently myself …
|
|
| Jan 12, 2018 at 17:36 | history | asked | PareekSandeep | CC BY-SA 3.0 |