Quick Settings causing FCs - Droid Incredible Q&A, Help & Troubleshooting

I just flashed the Quick Settings for Official GB OTA (4.06.605.2).
http://forum.xda-developers.com/showthread.php?t=1239820
Now I'm getting the following error every couple seconds. "The process android.process.acore has stopped unexpectedly." I have cleared the cache and the dalvik cache. Is there anything I can do short of factory reset or restoring a backup to get rid of this error?

Not likely since you flashed something over top of your rom set up. Just bite the bullet and revert to a backup or reflash the rom.

I flashed this earlier today and I haven't had that FC issue. Any other mods installed?
Sent from my ADR6300 using XDA Premium App

I backed up everything with Titanium and did a factory reset. That seemed to fix the problem but after I restored my apps I started to get FCs again. I just wiped everything and flashed McSense v1.2 and the Quick Settings on top of that. Rebooted and everything works good. I'm going to re install everything from market rather than restore from backup.

Also, it helps to backup only user apps and some data. Avoid system days if you were restoring any.

Related

[Q] Cyanogenmod Failed to restore an app :/

So i recently backed up my beautiful widgets app to titanium back up, and when cyanogenmod tries to install it / restore it, the ROM just reboots everytime. Has anyone had any problems similar to this?
Originally Posted by supergadgetman
Just loaded the new RC after a clean wipe and now I am trying to restore my user apps from titanium backup. My evo just reboots before any app even gets installed. Everytime I click run in the batch restore I get a reboot. This is after I wiped again, reflashed, reinstalled Titanium backup, but same results. This is with the stock kernel. Anyone having this problem?
bumppppppp

Com.sprint.ce.updater force close?

I am so confused! I recently started getting a sprint installer (Com.sprint.ce.updater) force close upon rebooting of the phone. It doesn't appear to be causing any adverse effects of the phone, but it is annoying. Any ideas?
Normally, I use clockworkmod as my recovery of choice, but I was using Amon Ra to wipe cache and dalvik cache and then flash SBC 4.2.2. Unfortunately, I accidentally wiped data instead of cache. Not a big deal, I have several clockworkmod backups.
Reflashed clockworkmod and attempted to restore data. Data restored, but started to get this Com.sprint.ce.updater force close. Tried other data restores, and still force close. Even attempted to do a complete data/system wipe. System wipe resolved issue until data restore occurred. Tried a complete restore using a clockworkmod backup that I know works. Still Com.sprint.ce.updater force close!
I really don't want to have to start all over again with a clean rom. Help?
Sent from my PC36100 using Tapatalk
something seems like its not compatible or was backed up wrong. thats why i dont use clockwork, but i may be wrong. Next time, post in Q&A. thaats the updater for OTA's i believe, and i'm guessing your running sense and not aosp. so possibly somethings corrupted.

[Q] App Force Close Error In Custom ROM

OK so here's my problem.. I have backups in both nandroid and Titanium Backup. I flash a ROM wait for it to do its business. After everything boots up, I try to restore everything through titanium backup but I get a force close error. I also try to open Rom Manager to see if it works and I get the same error but for Rom Manager. So the error isn't in Titanium Backup, but I do not know where it is. Any ideas?? I enjoy having custom Roms, but not if I do not have all of my stuff on the Rom.
Well I was going to attach a picture but it will not allow me because I am " New".
The error message reads as this.
! Sorry!
The application Titanium Backup (process com.keramidas.TitaniumBackup) has stopped unexpectedly. Please try again.
(Force Close) <---- button
It also does it with other applications such as the Facebook Launcher.
Once you flash your ROM, run Fix Permissions preferably from recovery, else use the version(s) in either Rom Manager, or Titanium.
Once that completes, reboot device. When you restore things from Titanium, just restore apps, preferably one-by-one, and only the app, not the data.
Do not at all recommend restoring apps+data+system data from Titanium. Why?
The system data backup residing in Titanium was for the last ROM, or the last time the backup was completed. As such, if you flash a different ROM, you are overwriting the system data of the new ROM with the system data from the old ROM - that spells odd behavior, mass force closes. etc. etc.
Well I tried this solution smtom, and it was to no avail. Any other suggestions?
When flashing a ROM, are you clearing cache/dalvik and doing the factory reset on the device? What version of Rom Manager & CWM are you using?
The latest version of CWM is giving people issues.
Absent all that, try not restoring apps or data (anything really) from TB when you flash the new ROM, after having wiped data/caches/user data.
Yes I'm clearing cache and data. The CWM version is 3.0.0.5, which is the latest recovery.
What does clearing the dalvik do and how do I factory reset the device?
I figured it out, with tmtom's help of course! I had to do a factory reset and then flashed the rom and everything worked. Thanks for the advice!!
I have the same error so I'm going to try the solutions provided in this thread. I do have one question though. Kalebskalicky mentioned that he finally fixed it by doing factory reset and then flashing the rom.
Just to be clear; factory reset is the same as wiping data/factory reset? Or I need to do a factory reset from the phone settings?
Another thing. I have noticed that the FC issues have something to do with gapps, acore, and/or framework processes. When I get any of these force closes, all the other apps start to crash, but all the issues start with any of those 3 processes crashing.
However, there are 2 apps that force close from the start, even before any of these 3 processes crash. These 2 apps are voxer and waze.
Is there like a way to delete the folder where they are installed? maybe it's a problem of installation? I have no idea and haven't been able to fix it.
Any suggestions, would be inmensely appreciated.
Thank you very much.
UPDATE:
Just wanted to mention that I always wipe data/factory, wipe cache, and wipe dalvik cache, and then flash the new rom. Is this ok to do? Or am I deleting stuff I shouldn't?
Thanks again.
I also had this issue.
I had tried wiping the cache and the dalvik cache. Fixing permissions. didn't wont to format as everything was set-up how I wanted it and couldn't be bothered going through it again.
After some digging around I had to uninstall titanium backup first then delete the folder
/sdcard/external_sd/data/com.keramidas.TitaniumBackup
(there may also be /sdcard/data/com.keramidas.TitaniumBackup to Delete)
Reinstalling titanium backup after deleting this folder, worked like a charm.
Apparently its to do with a corrupt database upgrade???
I hope this helps any one.

[Q] Backup not working with new custom ROM

Hello
last night I tried installing the carbon rom for my Note 2 N7100. (v1.8 Release stable build)
Everything wen't fine but I used titanium backup to backup my files and I also have a backup with CWM. I cleared all data/factory reset and wipe cache plus I installed the 4.2.2 gapps. The OS worked completely fine but when I used titanium backup to restore all apps and system data, It asks to restart which I did and when I restarted my phone the startup time took 25 minutes+ so I knew something wen't wrong. I rebooted into recovery and wiped cache and data reset again but I'm still having issues. I forgot to mention I tried using titanium backup and just restoring system data and not the apps.
I decided to do a restore completely using the CWM backup then I flashed 4.3 gapps to get it back up to date. However, when I tried to startup my phone, gapps isn't working properly and keeps popping up com.process.gapps or something like that has stopped. Usually this means the wrong version of gapps is installed but I've tried reflashing it incase I had a bad flash but that didn't work either.
I'm now using carbon rom without any of my previous system data or apps.
What can I do?
Thanks

Com.processes.gapps! What is this!?!?

Hey all, never posted on here before because I've had good luck with ROMS in the past but here goes.
Haven't rooted since the 4.3 update. Rooted the other day with cfautoroot. Everything went fine. Decided to try slimrom, so I installed TWRP 2.7.0, made a backup, ect. Went to install the ROM and it gave me errors. So I restored my backup. I had a hell of a time getting past the at&t screen but I finally got it to boot. The minute I unlocked, I was bombarded by "com.processes.gapps has unexpectedly quit" among every other app telling me it failed. So I got to the backup and restore and did a factory restore. Everything seemed to be normal. So I looked online for some information on the errors. Found a forum that indicated I was using a TWRP version that was too new. So I installed 2.6.1. Because I apparently enjoy being aggravated, I did the whole process over again. The same result happened. After more research I discovered that TWRP may have been the culprit along with ROM manager. So I installed Clockwork and did the whole process AGAIN! I got slimrom to install without problems. I was able to make a backup of slimrom as well. Just to be sure, I went and did a wipe in clockwork and tried to restore the backup I made of stock. Restarted, same error messages. Every second. Did a factory restore and everything was fine. So then I did a backup again and restored my backup of slimrom. It works fine! If I try to restore the backup of stock, I get errors. What's going on here!?
What I tried:
Clearing caches and data of the apps that were throwing errors
Stopping download manager and restarting it.
Clearing cache and delvik cache in CWM
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Categories

Resources