My settings force close and have went through cleared cash, closed apps recent, even went to safe mode and still forces close. Any ideas besides the ones you can dig offline?
I think a simple factory reset and clearing cache partitions will do. Try clearing only cache partitions first see if it works alone if not then factor reset (from recovery menu)
sarsary said:
I think a simple factory reset and clearing cache partitions will do. Try clearing only cache partitions first see if it works alone if not then factor reset (from recovery menu)[/QUOTE.
Found out at one point recently i had applied substratum theme and did a theme. Caused conflicts so i uninstalled but apps it added sometime later caused issues and locked me out. So downloadd a ram booster which let me scan for running apps and seen android symbol by the apps and removed. Walla. Thanks for help. Hate starting phone fresh after swipe or factory reset. There is an answer if ya look. Just couldnt find till now.
So note to any users clean out unused apps and attached files. They can cause issues down road!
Click to expand...
Click to collapse
Related
I have 2 Incredibles, mine, and my daughter's. I had hers initially, then gave her that one when mine showed up. On mine, I immediately flashed it to the first leak and 2.05 Radio OTA per instructions here, and it worked great.
On hers, I forgot to do a erase all before flashing it, so it still had all of my old data and apps on it. After flashing, I expected to see the screens revert back to their default state, but they didn't. My custom icon placements were still in place on the home screens. The icons for 3rd party downloaded apps were generic android icons. Opening any 3rd party app would cause a force quit. I did an erase everything, didn't fix it. If I went to the market, apps would show as not being loaded, so I loaded them, same results. I then uninstalled and reinstalled, and the apps all worked again.
So, last night, I reverted both phones. Mine went smooth as butter. Hers did the exact same thing as before. So, I went through all the actions, and got it all working again, no problem. Lastly, she went to change the desktop pattern to a picture, and rebooted the phone (not sure why), but it hung on the first "HTC Incredible" boot screen. Pulled the battery and put it back in, no change. Pulled it, let it sit for about a minute, put it on A/C and put the battery back in, and it came back up as expected. When it booted though, it has gone nuts again. All changes since the flashback were lost, icons were generic, I had to uninstall and reinstall everything.
The thing to note here is that once I get it all set up, it works fine, no problems. All I can figure is the fact that I didn't clear everything before the first flash has caused something in memory to become corrupt, and and isn't getting purged when I do an erase all.
So, does anyone have any suggestions?
Thanks,
Doc
did you do a hard reset?
Sent from my Incredible using XDA App
sounds like you need to clear the davlick cache too. just selecting full wipe isn't always enough.
jdkoreclipse said:
did you do a hard reset?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Ok, what's a "hard reset" as opposed to clearing everything via the Settings -> Privacy -> factory data reset?
seanhassars said:
sounds like you need to clear the davlick cache too. just selecting full wipe isn't always enough.
Click to expand...
Click to collapse
And how does one go about clearing the davlick cache?
Thanks!
Doc
I did the same thing when I flashed mine. I just went back into clockwork and did a format on every choice including the cache and did a reinstall and everything was stock.
Thanks, I'll give it a try!
I'd still like to hear from seanhassars and jdkoreclipse on how to perform the options they suggested.
Thanks,
Doc
Hard reset is the clear storage option in the bootloader.
And you clear dalvik cache in the advanced menu in recovery.
Sent from my ADR6300 using XDA App
I'll be redoing the phone tonight so will take all of this into account.
Thanks a lot to all!
Doc
Hello. I have a stock 4.5.91 At&t Atrix, unrooted, and with a locked bootloader. When I booted up today, some applications that are in my Media Area had disappeared. In the Manage Apps section, it lists them in com. form. For example, Tank Hero is named com.clapfootgames.tankhero. When I try to move these apps back to the phone or clear their data, the system says they don't exist. Rebooting doesn't help, and I don't want to factory reset, as I have 90+ downloaded apps.
I'd try clearing the dalvik cache and cache partition. Not sure how to without cwm. Faced the same issue couple of times...
Sent from my cherried-trix using Tapatalk
Upon rebooting, the apps were restored, but I know this problem will persist. I'll live with it until I root (which I'm very tempted to do). Thank you for the reply!
Turned on my A500 just now and the Android Is Updating popup flashed... then the counting of updated processes... all the version numbers seem to be the same... anyone else get this or have an idea what they updated?
If it's any consolation, it isn't an update. I have no idea what the issue is. But my tablet does the same thing every so often. It's as if I cleared my cache or something...
...odd
The only time I've seen that was on a reboot after a major update. Oh well, no worries.
That occurs when the Dalvik Cache has been cleared. Before ICS you would just see the boot animation the whole time that was happening, in ICS they decided to show you the process. Don't know why your Dalvik is clearing when you power down though.
cruise350 said:
That occurs when the Dalvik Cache has been cleared. Before ICS you would just see the boot animation the whole time that was happening, in ICS they decided to show you the process. Don't know why your Dalvik is clearing when you power down though.
Click to expand...
Click to collapse
Perhaps the OP should format /cache and wipe the dalvik-cache using recovery? Perhaps the permissions are messed up or the partition has gone awry.
Some odd things happened yesterday- All media on the storage card acted like the card was first plugged in. Everything had to index all over again. Then other little things that pretty much confirms some cache was cleared somehow. No idea... I'm probably going to back things up and do a hard reset.
Hi,
Hopefully someone has a solution for me.
This morning I switched on my TF101 and when I tried to go home from Gmail the button lit up but did nothing. I was convinced it didn't work. So I treid a few reboots and still nothing. I tried some other launchers and still nothing.
On further inspection I realised that when turning on slide unlock that also didn't work. Changing to pin, pattern or password still shows no unlock.
Are you running stock or a custom ROM?
Are you running stock recovery or a custom one?
I'd try to wipe the cache and dalvik, it fixes lots of weird software issues.
Lethe6 said:
Are you running stock or a custom ROM?
Are you running stock recovery or a custom one?
I'd try to wipe the cache and dalvik, it fixes lots of weird software issues.
Click to expand...
Click to collapse
It's the stock ROM rooted with debugfs.
I know how to wipe the cache but how do I wipe the dalvik. I remember doing it once a couple of years ago on another device but for the life of me now can't remember.
I was going to try clearing the davlik with Terminal Emulator and typed "su" followed by "ls" and all it showed is "recovery". Does this mean it's somehow landed in recovery mode? If so, how do I get out of it?
I managed to clear dalvik through terminal emulator. Optimised apps and rebooted but the problem persists.
Sent from my Transformer TF101 using Tapatalk 2
Reaper1242 said:
It's the stock ROM rooted with debugfs.
I know how to wipe the cache but how do I wipe the dalvik. I remember doing it once a couple of years ago on another device but for the life of me now can't remember.
I was going to try clearing the davlik with Terminal Emulator and typed "su" followed by "ls" and all it showed is "recovery". Does this mean it's somehow landed in recovery mode? If so, how do I get out of it?
Click to expand...
Click to collapse
If you have CWM, go to advanced, wipe Davlik.
frederuco said:
If you have CWM, go to advanced, wipe Davlik.
Click to expand...
Click to collapse
Thanks, now I remember I used CWM.
I thought I'd report back on this in case the information might help someone else down the line.
I tried the cache/davlik clear method and that did nothing for me. I stuck with it for a few days and eventually resorted to button saviour. I also realised that not only was the home button and any lock screen not working, but when using the ASUS quick settings in notifications it didn't show all settings.
This lead me to believe something in the system itself had gotten warped.
Today I did a Titanium backup, factory reset and restored all apps, data and system data. Initially it was fixed but on restart the problem casme back. I knew I'd restored whatever had caused the issue. My next step was to do another factory reset. Since it takes minutes to manually get the system back I only restored apps and data.
This time, after restore the issue was gone. So clearly the issue was in a system setting.
So for anyone else having this issue. Backup with Titanium, factory reset and only restore apps+data.
I have got this issue since I wiped the dalvik cache on Android 4.2.2 to fix a Play Store issue which I should of deleted that dalvik cache file with Titanium Backup or use Lucky Patcher to remove that left over file in /data/app/ but also wiping the cache somehow broke the APN API not allowing me to add the wiped APNs and such.
Since then I had to reflash EVERYTHING using the Nexus Stock Image flasher from Google Developers, since then I had no issues until a recent Android 4.3 update which caused the dalvik cache issue to arise since it wiped the dalvik cache.
I also do not have root because of the update but the su binary and SuperSU is still there so I cannot fix the issues manually.
When I come back on holiday I will root the device to see if I can fix the issue
but if that does not help then I can use the root to backup ALL the user apps, backup ALL the internal SD contents and reflash also rooting it.
Because I paid for the TB licence I can just restore my stuff in a touch of a "button".
I have removed apps which I don't use and the ones which I suspect is causing the issue but that does not help.
It seems that wiping the cache partition now does not break anything.
The dialog box says in the title "Android is upgrading..." and it says below "Starting apps..." and then gets off in a second.
I have seen forums of people having this strange issue but there are no replies.
I am getting back from holiday on the 31/8/13.
I really want this haunting issue to stop so please help so others can fix this issue without going though annoyance caused by this issue.
andyabc said:
I have got this issue since I wiped the dalvik cache on Android 4.2.2 to fix a Play Store issue which I should of deleted that dalvik cache file with Titanium Backup or use Lucky Patcher to remove that left over file in /data/app/ but also wiping the cache somehow broke the APN API not allowing me to add the wiped APNs and such.
Since then I had to reflash EVERYTHING using the Nexus Stock Image flasher from Google Developers, since then I had no issues until a recent Android 4.3 update which caused the dalvik cache issue to arise since it wiped the dalvik cache.
I also do not have root because of the update but the su binary and SuperSU is still there so I cannot fix the issues manually.
When I come back on holiday I will root the device to see if I can fix the issue
but if that does not help then I can use the root to backup ALL the user apps, backup ALL the internal SD contents and reflash also rooting it.
Because I paid for the TB licence I can just restore my stuff in a touch of a "button".
I have removed apps which I don't use and the ones which I suspect is causing the issue but that does not help.
It seems that wiping the cache partition now does not break anything.
The dialog box says in the title "Android is upgrading..." and it says below "Starting apps..." and then gets off in a second.
I have seen forums of people having this strange issue but there are no replies.
I am getting back from holiday on the 31/8/13.
I really want this haunting issue to stop so please help so others can fix this issue without going though annoyance caused by this issue.
Click to expand...
Click to collapse
that android is upgrading dialog box is the dalvik getting rebuilt, it get rebuilt after you wipe it, it is SUPPOSED to happen when you wipe your dalvik. it isnt an issue. if not, you wouldnt have a bootable or usable phone. the real issue here is you using lucky patcher. we all know what it is used for, and is disrespectable to the developers that hang out on xda.
simms22 said:
that android is upgrading dialog box is the dalvik getting rebuilt, it get rebuilt after you wipe it, it is SUPPOSED to happen when you wipe your dalvik. it isnt an issue. if not, you wouldnt have a bootable or usable phone. the real issue here is you using lucky patcher. we all know what it is used for, and is disrespectable to the developers that hang out on xda.
Click to expand...
Click to collapse
I only use Lucky Patcher for important stuff and not really for what you think so that is NOT the issue what so ever and misleading to this thread and plus, other people use it.
I mean that in EVERY boot it says that it is starting apps, nothing to do with building at all.
Sent from my Nexus 4 using Tapatalk 4 Beta
andyabc said:
I only use Lucky Patcher for important stuff and not really for what you think so that is NOT the issue what so ever and misleading to this thread and plus, other people use it.
I mean that in EVERY boot it says that it is starting apps, nothing to do with building at all.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Late reply, but Lucky Patcher did this to my phone just now and I don't know what to do, other than reflash. Which sucks because I spent all night modding out my phone and was stupid enough to not to a nandoid backup.
Edit: The first boot it upgraded everything then everything force closed, 2nd boot everything upgraded, but seems to be working fine. Woo. Was scared for a moment.
evilpig said:
Late reply, but Lucky Patcher did this to my phone just now and I don't know what to do, other than reflash. Which sucks because I spent all night modding out my phone and was stupid enough to not to a nandoid backup.
Edit: The first boot it upgraded everything then everything force closed, 2nd boot everything upgraded, but seems to be working fine. Woo. Was scared for a moment.
Click to expand...
Click to collapse
Well you was LUCKY (pun alert!).
Anyway it seems that the stock rom was always the issue, even reflashing does not fix this issue when you wipe the dalvik cache.
I am on ParanoidAndroid 3.98 at the moment and I am not getting any issues just by wiping the dalvik cache and/or the cache partition.
Sent from my Nexus 4 using Tapatalk 4
I have found fix for this error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click that Toolbox then select 4th last option i.e Remove all odex files.Thats it android will reboot on itself and vola no android is upgrading. .
Check out attached image for help.
:good:Hits Thanks If I helped u:good:
Garu8 said:
I have found fix for this error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click that Toolbox then select 4th last option i.e Remove all odex files.Thats it android will reboot on itself and vola no android is upgrading. .
Check out attached image for help.
:good:Hits Thanks If I helped u:good:
Click to expand...
Click to collapse
I just removed the odex files and worked great. Thank you.