I had everything working perfectly. Just finished restoring all 382 of my apps through titanium backup pro, then I tried switching to ART on CM11 Nightly. So naturally, I ran out of space during app optimisation (at around the 250th app)
Now it's extremely laggy, and I can't open up any apps besides settings menu. (because the Google Now launcher keeps crashing)
If I switch back to dalvik, will it restore the memory?
Or should I just wipe, and reflash the ROM?
EDIT:
I switched it back to dalvik, and for anyone wanting to know the answer, it does restore the memory. But not all of it.
Before switching from dalvik to ART, I had 1.5GB free, when switching back, I now have 429MB.
ldAbl said:
I had everything working perfectly. Just finished restoring all 382 of my apps through titanium backup pro, then I tried switching to ART on CM11 Nightly. So naturally, I ran out of space during app optimisation (at around the 250th app)
Now it's extremely laggy, and I can't open up any apps besides settings menu. (because the Google Now launcher keeps crashing)
If I switch back to dalvik, will it restore the memory?
Or should I just wipe, and reflash the ROM?
EDIT:
I switched it back to dalvik, and for anyone wanting to know the answer, it does restore the memory. But not all of it.
Before switching from dalvik to ART, I had 1.5GB free, when switching back, I now have 429MB.
Click to expand...
Click to collapse
I just suggest you do a full wipe :/
Press thanks if I helped!
Related
So I flashed the latest CM7 nightly on Sunday, installed from zip. Since then some of my apps have been force closing. Some are google apps like maps, and voice which I need day to day, others like facebook twitter, multiple browsers and engadget. I tried clearing cache, and battery stats as I use different batteries, and fixing permissions. Since then I have flashed CM7 RC 1 and two different MIUI builds, and have had the same problems with those. I haven't installed from titanium backup, just from the market. Any help would be greatly appreciated. EDIT: Now even XDA is force closing
I randomly started experiencing a similar problem recently with CM7 RC1... a lot of my apps were randomly force closing including the android core process...
Just now, I decided to wipe and reflash... now I'm having a new issue - the phone is not recognizing the radio.. it says "Baseband version: Unknown"
I can't activate the phone because the second I hit SEND, android.process.acore force closes.
Anyone have any insight?
EDIT: Just wiped and flashed CM7 Nightly build #8 - NO RADIO ISSUES OR FORCE CLOSES SO FAR
I am having similar issues. I am running CM 6.1.0, ClockworkMod 3.0.0.5, and radio 2.15.00.07.28.
I think just about every process has forced close at some point. Frequent offenders are messaging, youtube, and google framework.
Which caches and/or application data should I try clearing?
I am thinking of upgrading to CM7 RC1 but if the corrupted data remains cached will these problems follow me?
Did you wipe dalvik cache? Or possibly try different kernal.
It's back to working at %100 today after flashing CM7 which made my home button not work, then a sense rom.
I have an update on force closes as it pertains to my installation of CM7.
We need to follow the instructions accordingly. What I mean is we need to wipe everything that is suggested in the thread introducing the new ROM.
I couldn't load the new ROM from ROM manager. That is when all the force closes kept happening.
We must go into recovery and format the system, cache, and data from the Mounts and Storage Menu. Then, wipe Dalvik cache, battery stats, cache partition, and data/factory reset. Then install the new .zip from the root of your SD card (Both ROM and Gapps).
This is what worked for me. I have had no force closes since doing things this way.
Also, restore data only from Titanium Backup; else apps revert back to the previous ROM settings.
This may not be exactly the way things are intended by the wonderful developers here but it is what I have found to work.
Oldtymehockey said:
I have an update on force closes as it pertains to my installation of CM7.
We need to follow the instructions accordingly. What I mean is we need to wipe everything that is suggested in the thread introducing the new ROM.
I couldn't load the new ROM from ROM manager. That is when all the force closes kept happening.
We must go into recovery and format the system, cache, and data from the Mounts and Storage Menu. Then, wipe Dalvik cache, battery stats, cache partition, and data/factory reset. Then install the new .zip from the root of your SD card (Both ROM and Gapps).
This is what worked for me. I have had no force closes since doing things this way.
Also, restore data only from Titanium Backup; else apps revert back to the previous ROM settings.
This may not be exactly the way things are intended by the wonderful developers here but it is what I have found to work.
Click to expand...
Click to collapse
I read on cyanogen mod forums (thread here: http://forum.cyanogenmod.com/topic/15898-app-force-close-on-cm7-rc1/ )
And it was noted that its a known issue, and that re-installing the app worked, or running fix_permissions in terminal.
I installed fresh CM7 RC1, installed a few apps from market, ran fix_permissions and no force closes so far. Might try out the nightly
So... after flashing MikG v3.0 and trying it out for a day (not that this is related to mikg rom), I went back to Synergy RLS1. EVO FC's android processes now. Media, Market vendor, or Mail. Just whichever it feels like FCing.
I've wiped all data, cleared my SD card of ghost folders, Flashed and reflashed. Still doing it. Also, I notice that my gallery and music apps take forever to load the mp3s and pics now possibly an SD read error? I've been running Synergy since June and not had this problem before.
Any ideas?
I don't know of any other options, unless it is an app that is causing all this (which I have no new apps that I haven't had in the last month(s))
Has this happened before to anyone >_>?
VERY Annoying. Can't use the phone for constant !FORCE CLOSE! windows
Did u restore any app data from backing up between roms?
-EViL-KoNCEPTz- said:
Did u restore any app data from backing up between roms?
Click to expand...
Click to collapse
Thank you for your reply!
Nope. Not unless it has done it natively. Though, all my apps do download automatically after flashing Synergy.
How might I clear this?
I have Titatnium back up, though I don't use it. And astro, but I don't use the backup features on it either.
In titanium when u choose batch restore select app only, try reflashing fresh don't restore from Google restore apps only thru tibu and see if you still get the FC issue, I'm not 100% sure but I think Google adds app data with the backup and some apps data cause issues between roms I've had issues both from sense to sense and from sense to aosp or vice versa from app data causing errors in processes and force closing random apps or processes
Hi,
I thought that to install wiui stable (2.2.3) all i had to do was go to recovery and install from zip to install wiui. I'm coming from CM7.2 quarx, but i didn't think that'd be a problem.
After the first install, it went fine, except there were tons of Force Closes (first for launcher) so i couldn't even use the phone. I then flashed the launcher pro for wiui .zip and then it booted up, but had different FCs (android.media process, and a couple others, i can't remember)
So after, i decided to reflsh to cm7.2, and it's fine. all my contacts are gone, and homescreensetups, etc. but it looks like all my apps are there, mms, call hstory, etc.
I then tried to reinstall wiui again, and now it's stuck in boot loop. I've tried wiping cache and dalvik, i just don't know what else to do.
If anyone can spare the time to help, i'd greatly appreciate it.
thank you
simple method..
flash CM7.2 again..backup all ur apps with the help of titanium backup...
go to recovery...wipe data..then flash wiui..wipe cache and delvik cache...reboot...
install titanium backup..restore all ur apps..
Advice for future..to avoid force closes, always wipe date before shifting to other ROMs!
Ye thanks, i did that. but when i restored my apps i got the FCs again. maybe something in my data is incompatible w/ wiui? oh well, I've gone back to CM7.2 again. but now i had to use sync[ix app to get all the pics back to my contacts. not sure why it didn't work like it did before.
The times I've done that, I've shut down the phone and restart because a simple reboot didn't do the job. Also, I run ROM Manager and fix permissions. I can't tell you the last time I had an FC.
tronjojo said:
Ye thanks, i did that. but when i restored my apps i got the FCs again. maybe something in my data is incompatible w/ wiui? oh well, I've gone back to CM7.2 again. but now i had to use sync[ix app to get all the pics back to my contacts. not sure why it didn't work like it did before.
Click to expand...
Click to collapse
Just restore the apps and not the app data, this is a problem I had when moving from CM7 to WIUI.
First run of WIUI I had loads of FC's. I wiped data, installed zip, wiped cache and dalvic again, then when going through Titanium backup I didnt restore the app data.
I have had no problems since then.
hope that helps, WIUI is really nice
So, today I turned my phone off because I had a class and it didn't turn on again.
Everything worked properly yesterday before switching to ART, so I think that ART caused my bootloop.
I've tried everything I could (without wiping anything), but it still didn't boot properly
I made a nandroid now, and I clean flashed a new ROM
It's not the bootloop that bothers me, but the fact that I don't have a recent backup of the only game I play
So here's my question: is there a way to switch back to dalvik without actually doing it from Developer Settings? Some kind of adb command maybe?
If not, how can I restore app's data from my nandroid? I've tried both Titanium Backup and Nandroid Manager, but the app force closes when I try to open it
ROM: ShinyROM
GApps: PA stock package
Kernel: ALKKX and the one that comes with ShinyROM (didn't boot with both of them)
I don't think that it can help but the game is Geometry Dash
I was like #20 in the global score with more than 1k stars, I don't want to start it over ughhh
I've used sultanxda's cm 13 rom since it's inception and only stayed there because of xposed. Since the official xposed was released, I decided to upgrade and have had nothing but problems.
To start with, I upgraded with TWRP by wiping (system/cache), flashing new fw by sultan, flashing the new sultanxda cm14 rom, flashed gapps, flashed magisk, wiped cache, and booted. After it booted it up, a lot of FC and apps staying on their splash window and closing.
So I tried RR and they fared well, but after a while it started doing the same. I could be not using my phone for a few hours, load whats app, and it would FC.
Backed up data (using TB), did a full wipe (system/data/cache), flashed fw, flashed rom, flashed gapp, magisk, xposed, and flashed the update.zip I created with TB. After boot and restore it did the same thing.
Thinking maybe it's the data, I did the above, but this time I didn't restore the data by TB's update.zip. I did a clean install, booted, waited for google play to restore by downloading all apps, then restored only the data using TB. This seemed to be having the best result and I used it all day with minor issues like whatsapp would not update until I launched it. So if people were sending me messages, I didn't know until I launched whatsapp.
Went to bed and woke up, same deal as the original problems. Lots of apps: Whatsapp, Web video broadcaster, whisper, signal, ring, sc, firetv app, and many more would either give FC or not launch. Only way I figured to fix it is restore the app only using TB.
I even tried reflashing the FW and Open beta FW again, but that did not help.
What is about my phone and nougat that's causing me to have these problems? I had no issue using MM with all of these apps. If they were not compatible, google would have not downloaded them after a clean install.
Anyone else having these issues or know what might be going on? I'm very tempted to go back to my MM backup and update the data for all apps if I cant fix this.
ahb83 said:
I've used sultanxda's cm 13 rom since it's inception and only stayed there because of xposed. Since the official xposed was released, I decided to upgrade and have had nothing but problems.
To start with, I upgraded with TWRP by wiping (system/cache), flashing new fw by sultan, flashing the new sultanxda cm14 rom, flashed gapps, flashed magisk, wiped cache, and booted. After it booted it up, a lot of FC and apps staying on their splash window and closing.
So I tried RR and they fared well, but after a while it started doing the same. I could be not using my phone for a few hours, load whats app, and it would FC.
Backed up data (using TB), did a full wipe (system/data/cache), flashed fw, flashed rom, flashed gapp, magisk, xposed, and flashed the update.zip I created with TB. After boot and restore it did the same thing.
Thinking maybe it's the data, I did the above, but this time I didn't restore the data by TB's update.zip. I did a clean install, booted, waited for google play to restore by downloading all apps, then restored only the data using TB. This seemed to be having the best result and I used it all day with minor issues like whatsapp would not update until I launched it. So if people were sending me messages, I didn't know until I launched whatsapp.
Went to bed and woke up, same deal as the original problems. Lots of apps: Whatsapp, Web video broadcaster, whisper, signal, ring, sc, firetv app, and many more would either give FC or not launch. Only way I figured to fix it is restore the app only using TB.
I even tried reflashing the FW and Open beta FW again, but that did not help.
What is about my phone and nougat that's causing me to have these problems? I had no issue using MM with all of these apps. If they were not compatible, google would have not downloaded them after a clean install.
Anyone else having these issues or know what might be going on? I'm very tempted to go back to my MM backup and update the data for all apps if I cant fix this.
Click to expand...
Click to collapse
/using TB is known to brek google push messaging service. Alos when going from something that was on android m to android n, always do a clean flash (formatting both caches, system and data) When backing up, make sure to only back up and restore user data. Not a single piece of system info should ever be restored.
zelendel said:
/using TB is known to brek google push messaging service. Alos when going from something that was on android m to android n, always do a clean flash (formatting both caches, system and data) When backing up, make sure to only back up and restore user data. Not a single piece of system info should ever be restored.
Click to expand...
Click to collapse
right, that's what I did this last time I reflashed everything. backed up all important apps, flashed everything, let google restore the apps, and restore only the data to the non-system apps.
would that have an effect of every other app though? I could not use web video caster even thought it was a fresh install, no restored data, because it would just FC.
ahb83 said:
right, that's what I did this last time I reflashed everything. backed up all important apps, flashed everything, let google restore the apps, and restore only the data to the non-system apps.
would that have an effect of every other app though? I could not use web video caster even thought it was a fresh install, no restored data, because it would just FC.
Click to expand...
Click to collapse
The best thing you can do is grab matlog from the play store and run a logcat. The post it in the roms thread.