[Q] CM Rom Force Close - Fascinate Q&A, Help & Troubleshooting

Hello Community,!
I have been using CM since the nighties unitl the early 30's before Kernel got hacked I have stopped using CM around that time and switch back to near stock rom (TSM Resurrection) due to force close on every single applications. Now that CM is official, I hope the problem is gone but it is still there. I can use the phone for couple hours and then force close everywhere.
I have tried the following with that I can find on the forums:
1. Fix Permissions.
2. Fix Permissions and then reflashing CM.
3. Wipe data and reflashing.
4. Went back to stock (with atlas and all that) and then back to CM.
5. Rebooting/pulling battery out does not fix it either.
I read that it would be running out of memory causing it, but closing apps did not help.
Could it be rogue app(s) causing it or something entirely different?
Thank You!

Hyper_Warp said:
Hello Community,!
I have been using CM since the nighties unitl the early 30's before Kernel got hacked I have stopped using CM around that time and switch back to near stock rom (TSM Resurrection) due to force close on every single applications. Now that CM is official, I hope the problem is gone but it is still there. I can use the phone for couple hours and then force close everywhere.
I have tried the following with that I can find on the forums:
1. Fix Permissions.
2. Fix Permissions and then reflashing CM.
3. Wipe data and reflashing.
4. Went back to stock (with atlas and all that) and then back to CM.
5. Rebooting/pulling battery out does not fix it either.
I read that it would be running out of memory causing it, but closing apps did not help.
Could it be rogue app(s) causing it or something entirely different?
Thank You!
Click to expand...
Click to collapse
just went thru this the other night with another member...try going back to dl09 and reformat your sd card. worked for him

I have not tried in addition to reformatting my sd card whild doing the whole DL09 restoring. I will give that a go.
It would probably also be a good idea to redownload the apps fresh from the the market instead restoring them from titanium backup?

Hyper_Warp said:
I have not tried in addition to reformatting my sd card whild doing the whole DL09 restoring. I will give that a go.
It would probably also be a good idea to redownload the apps fresh from the the market instead restoring them from titanium backup?
Click to expand...
Click to collapse
with tibu just make sure to restore app only w/ out data. Should be no different than redownloading the app from market.

Your solution seems to work so far, I did however redownload fresh copies of apps from the market and just restore the data from titanium backup just incase any full restore are corrupted. I do get random phantom keys from time to time.
ty

Related

[Q] CM7 RC1 upgrade issues and questions

I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
kabell4 said:
I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
Click to expand...
Click to collapse
Regarding your nightly question, they are full ROMs...the difference between them is the code that was committed within the previous 24 hours. Of course that also means that, in theory, some of the nightlies could be 100% the same...anyway, the nightlies can be a beautiful thing or a disasterous thing...usually if there's an issue with a nightly it is quickly found by those who flash each nightly and it is brought up around 3.2 million times and it is typically fixed by the next nightly.
Partitioning usually does mean a wipe of data on the SD. Careful!
When I upgraded to a 32GB flash from the stock 2GB from my Aria, I backed up the entire contents and restored on the new one. Apparently there is volume information stored somewhere (not sure where) and the phone couldn't recognize the card and asked me to partition it.
Because I had a backup, I decided to do so, but instead of partitioning for the entire size of the chip, it partitioned only 2GB!
So I had to stick it into a reader and repartition it manually and then selectively restore music, etc back on the card.
After that it worked just fine. So short version: yes it does.
kabell4 said:
I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
Click to expand...
Click to collapse
You will need to creaate an sd-ext partition to fix the issue of installing (larger) apps with CM7.
The best way would be through ROM Manager.
wifi
Installed the RC2 and can't connect to a hidden SSID wifi network.
That is a known issue with the wifi driver on cm7 thus far. Not sure if it will be corrected though. Anyone else know if it is in the works?
"Do you mind if I turn up the AC?"
I believe if you flash to nightly 14 all will be good, not 100% sure though.
TheFurnace said:
That is a known issue with the wifi driver on cm7 thus far. Not sure if it will be corrected though. Anyone else know if it is in the works?
"Do you mind if I turn up the AC?"
Click to expand...
Click to collapse
As far as I know there are no plans to change it. But then again we weren't supposed to get fm radio working either...
Sent from my cm7 Aria using XDA App
Too true. Never know what is coming down the pipeline!
"Do you mind if I turn up the AC?"
stellarhopper said:
You will need to creaate an sd-ext partition to fix the issue of installing (larger) apps with CM7.
The best way would be through ROM Manager.
Click to expand...
Click to collapse
Great input from everyone. Thanks! Following up on the sd-card partitioning... I have a new 8g card and want to more to CM7. If I partition it, what happens when I restore the backed up app using My Backup Root? And, what is the best partition configuration, why, and what info get store in each section (ext)?
Thanks...
kabell4 said:
Great input from everyone. Thanks! Following up on the sd-card partitioning... I have a new 8g card and want to more to CM7. If I partition it, what happens when I restore the backed up app using My Backup Root? And, what is the best partition configuration, why, and what info get store in each section (ext)?
Thanks...
Click to expand...
Click to collapse
The easiest way to partition is using your ROM manager.
Just select the max size for SD-EXT (I think it would got to 512MB), and none for swap.
I'm not sure if this would have any effect on your backup - I myself started out from scratch and got my apps from the market even though I had made an Astro backup...
You will store all your stuff - music, pictures etc in the normal partition. The SD-EXT will be automatically handled by the phone.
Tried flashing Nightly 22 on my Aria from 17. I spent a lot of time customizing 17. Is there a way to keep all of the old home screens? Also, GPS lock isn't working for me. Using MyBackup Root for Apps, but it seems to duplicate the apps?
kabell4 said:
Tried flashing Nightly 22 on my Aria from 17. I spent a lot of time customizing 17. Is there a way to keep all of the old home screens? Also, GPS lock isn't working for me. Using MyBackup Root for Apps, but it seems to duplicate the apps?
Click to expand...
Click to collapse
You should be able to flash each new nightly without losing any of your settings/customizations/homescreens and apps.
While upgrading from ROM manager, just check the backup option, don't check wipe data and cache.
I can confirm this works transitioning from 14 to 22 because I just did it yesterday night
As for the GPS problem, thats a known issue - the workaround is to make a nandroid backup of your current cm7, then do a complete phone reset, then do a nandroid restore of cm6 or 6.1 (hope you have one), do another factory reset, and restore your cm7 from the backup you took in the 1st step
stellarhopper said:
You should be able to flash each new nightly without losing any of your settings/customizations/homescreens and apps.
While upgrading from ROM manager, just check the backup option, don't check wipe data and cache.
I can confirm this works transitioning from 14 to 22 because I just did it yesterday night
As for the GPS problem, thats a known issue - the workaround is to make a nandroid backup of your current cm7, then do a complete phone reset, then do a nandroid restore of cm6 or 6.1 (hope you have one), do another factory reset, and restore your cm7 from the backup you took in the 1st step
Click to expand...
Click to collapse
first of all, i would never suggest using rom manager for things such as that. historically it has only caused problems and has been more of an inconvenience than anything. second of all, when you boot into CWM and do it the right way, don't wipe data, it's suggested but not necessary that you wipe cache and dalvik, then flash the rom and you'll be good.
Thanks to both of you. Big help and not deleting the data did the trick. Looks like I'm good to go and GPS is working well again. Is there a way to ensure I don't have duplicate apps taking up space on the card and phone? I'm getting errors on moving some apps to the sd card.
kabell4 said:
Thanks to both of you. Big help and not deleting the data did the trick. Looks like I'm good to go and GPS is working well again. Is there a way to ensure I don't have duplicate apps taking up space on the card and phone? I'm getting errors on moving some apps to the sd card.
Click to expand...
Click to collapse
Not all apps can be moved to the FAT32 partition on the SD card. Widgets also, won't work properly if moved to the SD FAT32.
If you need more memory, look into (read up) partitioning your sd card with a ext3 partition and installing S2E or Dark Tremor a2sd (DT a2sd).
zervic said:
first of all, i would never suggest using rom manager for things such as that. historically it has only caused problems and has been more of an inconvenience than anything. second of all, when you boot into CWM and do it the right way, don't wipe data, it's suggested but not necessary that you wipe cache and dalvik, then flash the rom and you'll be good.
Click to expand...
Click to collapse
Oh, I had no idea about that, thanks for the info.
I've been using ROM manager without any problems so far, apart from one lately, that when I reboot to recovery, I always get an error screen - exclamation mark in triangle...but I just pull the battery and reboot into recovery manually and it starts whatever command I had given it (backup/new rom) automatically...

[Q] Need help, cannot install apps or recovery backuped ones

In a world of trouble now. been on sd 1.9.0 (initially on 318 official), everything was great for some time, then, after a month or two, phone started acting funny (frequent random reboots, hangs, could not start for hour or two when got into dell logo loop...), so i decided to do factory reset. did it and after that could not install any app or recover any titanium backuped apps. when installing any app, install process will continue endlessly, with progress bar always on start (but not freezed, bar is moving, but there is no progress). same thing with titanium backups - could not make any restore - also it starts, but no progress.
later tried new rom flash (sd 1.9.0), then 1.8.1, then 318, then simplestreak 1.2, then again 1.9.0, all with factory resets - could not fix my problem - could not install or make recovery.
hardware-wise all seems without malfunctions. been thinking that maybe internal sd is defective, made check from engineering menu and all seems ok with it.
got no more remedies, made around 50 reflash attempts today, no luck.
another idea that buggs me: could it be that app folder on internal memory is somehow not writable? what are normal permissions on internal memory folder structure?
looking forhelp - solutions or ideas. do you think that is hardware or software defective?
got some kind of warranty, but i'm not sure that i could enforce it...
Can you install apps normally though the market or sideloaded?
It could be that your backups are bad if you can install other stuff
Need a little clarification. Does your ROM after the flash run OK? If it no longer reboots on its own or hangup, doubt you have a problem with your internal SD.
I would recommend scrapping Titanium, I quit using it and started using MyBackUp Pro and haven't had any issues since when I recover apps.
You could do one of several things...
1)Use the QDL tool to get back to a stock ROM, then flash StreakMod and then StreakDroid 1.9.0 and see what happens.
2)Try replacing the internal SD with a 4GB class 10 which will improve performance and do away with the trouble if that were the problem
3)Use the QDL tool to get back to stock ROM and send it in for warranty if all else fails
TheManii said:
Can you install apps normally though the market or sideloaded?
It could be that your backups are bad if you can install other stuff
Click to expand...
Click to collapse
No, i can't install via market. When i connect to market, it instantly start to download updates (Gmail, Maps etc.) and, when downloaded, it will start installing, and progress will endlessly be stuck on start...so basically same thing like manual install or Titanium recovery.
dmandic said:
No, i can't install via market. When i connect to market, it instantly start to download updates (Gmail, Maps etc.) and, when downloaded, it will start installing, and progress will endlessly be stuck on start...so basically same thing like manual install or Titanium recovery.
Click to expand...
Click to collapse
Ok, you do understand that if you are allowing the market to install all the updates you had on your phone before, it could take a considerable amount of time, and may seem to get stuck. It doesn't download and install one by one, it begins downloading everything you had in your market account (something I hate about the market), so it may be trying to install 20 or 30 or 40 apps and updating others that are part of Android ALL at the same time. It could easily take an hour if you have a hundred apps or so on your phone.
Just a comment, not sure if you have taken that into consideration.
But I doubt you internal SD is bad, if it were, you wouldn't get as far as you get without some force closes, or maybe not even boot.
Your issue is software related in my opinion. But I could be wrong.
cdzo72 said:
Need a little clarification. Does your ROM after the flash run OK? If it no longer reboots on its own or hangup, doubt you have a problem with your internal SD.
I would recommend scrapping Titanium, I quit using it and started using MyBackUp Pro and haven't had any issues since when I recover apps.
You could do one of several things...
1)Use the QDL tool to get back to a stock ROM, then flash StreakMod and then StreakDroid 1.9.0 and see what happens.
2)Try replacing the internal SD with a 4GB class 10 which will improve performance and do away with the trouble if that were the problem
3)Use the QDL tool to get back to stock ROM and send it in for warranty if all else fails
Click to expand...
Click to collapse
ROM(s) working (relatively) OK. Have some FCs on some ROMs, no frequent hangups and only some reboots. Didn't have any of them for a long time because i was trying to find some solution for apps install because without ability to install smartphone is useless.
I heard some bad things of Tutanium, but i was happy with it so far, and i think that it is not his fault.
1) tried that (318 and 351 stock), and others combinations, and always ended with same problem
2) and 3) if i try to replace internal sd, then i will void my warranty
if anything else fails, i'll try my warranty, but i don't know if i'll succedd, but i'll like it better to fix it on my own, if it is software problem, not hardware
Breaking News!
Interesting turn of events: out of pure despair, i tried to flash Streakdroid 2.0 (Gingerstreak).
Out of blue, i could again install apps! I played a little, and tried to flash SD 1.9, hoping that it would be "fixed" now. But, sadly, it isn't! I still cannot install apps on SD 1.9.0! I flashed SD 2.0 again, and found that on SD 2.0 i CAN again install apps (Titanium also works, although it is basically useless because most of backuped apps and settings don't work on GB).
Here is summary:
- on Froyo builds (318, 351 stock; SimpleStreak 1.2; 1.8.1, 1.9.0 SD) i CANNOT install apps (endless install loop) and restore Titanium backups
- on GB build (SD 2.0) i CAN install apps and restore Titanium backups
This is completely puzzling to me. I though that is probably hardware fault (internal sd or something else), but if on SD 2.0 everything works, and on Froyo builds not, it seems that is some kind of software error?
I suspect on some kind of folder permissions error. Does anybody know right permissions for internal system folder etc.?

[Q] Titanium Backups Batch function not working

I have always used ROM Manager to do everything, but seeing that might not be the best way to do things..I have been having some other problems with restoring, and talked about it on another forum, but can't post the link here yet.
So, my nightlys said it is time to upgrade, so I am going to completely back everything up with TB, and fire it all up to dropbox. All of my system settings are 100% the way I want them... I also clicked the beta migration option in the preferences, hoping that would help me.
Step 1 - Backup all user apps + system Data
Step 2 - Sync to Dropbox
Step 3 - Boot into Clockwork Mod Recovery, and do everything manually, not through ROM Manager
Step 4 - Clear cache and Dalvik
Step 5 - Run zip from SD Card
This time, it seemed like everything went as planned. When I started the phone back up, all the apps were in the same spot, and wallpaper was the same. Although, the first time, when the screen timed out, I couldn't turn it back on. Pulled the battery, and all is working fine now.
Step 6- went into TB and did a batch restore of all apps and data, but only clicked the green items. From reading somewhere else, it is only wise to do the green items, not the red, so that is what I did. Then reboot for all to take effect.
This is where I am confused. None of my data is restored. For example, I use K-9 Mail, and the settings aren't restored by the batch. But, if I go to that app, and hit the restore data, then it restores it fine. So, for me to do all my apps, the batch function isn't working, I have to go through and do 15-20 apps manually.
So, what am I doing wrong here? Why isn't the batch operation working properly for me?
Edit - Something else I noticed that didn't restore properly was any of my ring tones. Not a huge deal, but I thought might be worth mentioning in this dilemma.
So I assume you are on CM7 as you refer to nightlies.
You say that you wipe cache/dalvick cache and install. Then when you reboot all your apps are in the right place?
Then why on earth would you want restore your apps on top of the existing apps with TB? Maybe that is causing the problem. AFAIK upgrading with a nightly shouldn't touch your installed apps.
Did you check the app settings before restoring with TB?
As for the ringtones, I always had that problem when using CM7, just got used to fixing them after installing each nightly.
Hope this helps.
What version of TB are you using? I was having a similar problem doing restores on v3.9.0.1 and was having problems doing batch recovery with my SGS2. The status bar would come up but wouldn't successfully finish. I then upgraded to 4.0.0.0 and everything seems to work.. might give that a try if you're using an older version.
killall said:
So I assume you are on CM7 as you refer to nightlies.
You say that you wipe cache/dalvick cache and install. Then when you reboot all your apps are in the right place?
Then why on earth would you want restore your apps on top of the existing apps with TB? Maybe that is causing the problem. AFAIK upgrading with a nightly shouldn't touch your installed apps.
Did you check the app settings before restoring with TB?
As for the ringtones, I always had that problem when using CM7, just got used to fixing them after installing each nightly.
Hope this helps.
Click to expand...
Click to collapse
Yes, sorry, I am running CM7, but using the nighties.
As far as the apps, that's why I think I am doing something wrong. Last time was the first time everything was there, every other update, it was like I was starting off with a new phone. No app, no data, nothing. A brand new fresh start.
I will try it again in a few minutes and hope for the best..
Thanks for helping out with this one..
bringit8 said:
What version of TB are you using? I was having a similar problem doing restores on v3.9.0.1 and was having problems doing batch recovery with my SGS2. The status bar would come up but wouldn't successfully finish. I then upgraded to 4.0.0.0 and everything seems to work.. might give that a try if you're using an older version.
Click to expand...
Click to collapse
I am currently using the Pro, 4.0.2. It just seems that I have to refresh all the data for each app by themselves, but all at once won't work.
Upgrading my nightly now, so keeping my fingers crossed that it will work.

edit

delete
I am experiencing the same issues. I assume you have this problem with ICS roms, because that's where I get those problems. I am currently running WEUI and half my apps are not at all working. I have also flashed back to stock, tried ICS Slim and MIUI v4, but no luck. I am also getting issues, while listening to music, where the song will keep on playing, but the app will ask me if I want to FC or wait. This has only happened recently. I really do not feel like going back to 2.2 or 2.3. Any help is greatly appreciated
Have you guys tried fixing the permissions?
That usually fixes most force close problems.
Xenoism said:
Have you guys tried fixing the permissions?
That usually fixes most force close problems.
Click to expand...
Click to collapse
Tried it, but no luck. Only option now is to flash a different ics rom, and see if that works. If all else fails I can always go back to bionix.
2 questions:
1 Can you see your internalSD with a file explorer?
2 Did you try wiping /cache and /dalvik-cache and rebooting?
I find a good wipe cure many things wrong (with my phone too )
Woodrube said:
2 questions:
1 Can you see your internalSD with a file explorer?
2 Did you try wiping /cache and /dalvik-cache and rebooting?
I find a good wipe cure many things wrong (with my phone too )
Click to expand...
Click to collapse
1. Yes
2. Yes, usually before I flash a different rom/reflash rom to try and fix this I wipe data and wipe cache patition and dalvik cache.
OK. The first question was to make sure you still had access to your internal and not sole sort of veiled encryption error.
Let me think about somethings and ill get back to you. I am wondering if it wouldn't be a bad idea to format /data and /system to make sure that you don't have any ghosts lurking. If you do, make sure you back up SDs contents to PC just in case.
Woodrube said:
OK. The first question was to make sure you still had access to your internal and not sole sort of veiled encryption error.
Let me think about somethings and ill get back to you. I am wondering if it wouldn't be a bad idea to format /data and /system to make sure that you don't have any ghosts lurking. If you do, make sure you back up SDs contents to PC just in case.
Click to expand...
Click to collapse
All those apps are still force closing on 2.2. Could it be, because I'm restoring them from titanium backup?
I'll try to backup SD onto my Computer and then format sd. It's probably some ghost file that is causing my phone to have errors. It probably is a file that has to do with MIUI since I flashed that as it happened.
Btw thanks for trying to help
Edit: I formatted sd card, put all the files back onto sd card, restored apps with tiatnium backup, but still no luck. I even factory reset,wiped cache and dalvik cache after formatting sd, but still no luck.
Thanks everyone for trying to help. I figued out the problem. Titanium backup was causing all those apps to have issues. I uninstalled all user apps via tb and download them from the market. I am getting no force close what so ever, with dl apps from market.
Usually when that happens from TB, it is from restoring system files (they show in red in the TB list of apps).
I use it to restore user apps + data every time I flash a new ROM, but I never use it to restore system apps, and I don't have any problems with it.
Since you've already restored from the market, you could try running TB and deleting it's backup data and then running a new batch backup of user apps (and no system apps) to have the freshest copy of your apps from a working system. That should allow you to restore in the future, hopefully without issue.
Sent from my SGH-T959 using xda premium
This could be a problem with using TB. TB gives you the option of restoring apps+data. If you're coming from a 2.2 rom to 4.0, you don't want to keep the data from a 2.2 rom. What you can do is restore apps without the data. That should solve your problem.

[Q] flush-179:0 eating CPU (and battery)

Hi,
My EVO 4G LTE is S-OFF. I've been running FreshROM 5.3.1 since it was released without issue. Last Thursday I started getting a lot of backround app crashes. Not a big deal, I wiped, reloaded the ROM, then restored everything via Titanium Backup pro. All was well for a couple of days.
Yesterday, my battery died within about 3 hours. Normally, I go over 16 hours. After some investigation and I found a process 'flush-179:0' eating CPU (and battery). I've wiped, flashed again, even flashed different ROMs. It's still there; every time.
I found one post on XDA where someone said it was caused by a performance tweak app (http://forum.xda-developers.com/showthread.php?t=2016993). Their fix was to flash stock, radios, etc. then root again. I haven't used any apps to tweak anything. So, if it's a similar cause...data/config corruption?
Has anyone else seen this? Does anyone know of a fix?
Thanks!
I'm not familiar with this specific issue but you mentioned that you restored everything using titanium backup. If you are experiencing problems I would strongly recommend NOT restoring all data as you may be restoring that very same issue. If you don't want to have to start all over then at least only restore just apps and data. Never system data.
Sent from my EVO using Tapatalk 2
eddy0090 said:
I'm not familiar with this specific issue but you mentioned that you restored everything using titanium backup. If you are experiencing problems I would strongly recommend NOT restoring all data as you may be restoring that very same issue. If you don't want to have to start all over then at least only restore just apps and data. Never system data.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Of course, the problem is that it's there when I wipe and flash a new ROM (Fresh, Rejuvenated, etc.). Even before I load my data via TB.
zisix said:
Hi,
My EVO 4G LTE is S-OFF. I've been running FreshROM 5.3.1 since it was released without issue. Last Thursday I started getting a lot of backround app crashes. Not a big deal, I wiped, reloaded the ROM, then restored everything via Titanium Backup pro. All was well for a couple of days.
Yesterday, my battery died within about 3 hours. Normally, I go over 16 hours. After some investigation and I found a process 'flush-179:0' eating CPU (and battery). I've wiped, flashed again, even flashed different ROMs. It's still there; every time.
I found one post on XDA where someone said it was caused by a performance tweak app (http://forum.xda-developers.com/showthread.php?t=2016993). Their fix was to flash stock, radios, etc. then root again. I haven't used any apps to tweak anything. So, if it's a similar cause...data/config corruption?
Has anyone else seen this? Does anyone know of a fix?
Thanks!
Click to expand...
Click to collapse
u should try mean rom 6.5 ICS.. if your still on the old base.. or flash new firmwear and radio in bootloader then flash a new jelly bean rom if u want to try the new base out
evo401 said:
u should try mean rom 6.5 ICS.. if your still on the old base.. or flash new firmwear and radio in bootloader then flash a new jelly bean rom if u want to try the new base out
Click to expand...
Click to collapse
I think I will; this seems to fit with the latest info I just figured out.
I flashed Fresh again, and suddenly started getting the warning about the SD card being damaged and to format it (as we know, that's not the external SD card). No matter how many times I format it, the error comes back. From some other searching, the 'flush-179:0' process seems to have something to do with storage, maybe because it can't read that partition it's causing issues.
I updated the firmware and radio, still no luck.
So I tried loading another ROM (I went with Mean Bean). That fixed the issue with the SD Card partition being unreadable/unformatable. Maybe that was caused by multiple flashes
But, the flush-179:0 process is still eating CPU and battery.
zisix said:
I updated the firmware and radio, still no luck.
So I tried loading another ROM (I went with Mean Bean). That fixed the issue with the SD Card partition being unreadable/unformatable. Maybe that was caused by multiple flashes
But, the flush-179:0 process is still eating CPU and battery.
Click to expand...
Click to collapse
?? i never heard of that flush-197:0?? could it be an app u downloaded maybe.. if u flash meanbean over abd dont install any app does is that flush-179 still there or it it there after u install yoir apps?
evo401 said:
?? i never heard of that flush-197:0?? could it be an app u downloaded maybe.. if u flash meanbean over abd dont install any app does is that flush-179 still there or it it there after u install yoir apps?
Click to expand...
Click to collapse
As far as I can tell, it's part of Fresh 5.3.1 and other ROMs I had on my SDCard that are based on the old OTA. The latest Mean Bean doesn't have the same issue after wipe & flash.
I emailed flipz (the Fresh dev), though who knows if/when he'll get back to me. For now, I'm thinking about running MeanBean for a while.
You really can't go wrong with mikeyxda and his mean series of ROM's. That man consistently puts out quality work. No doubt about it.
zisix said:
I flashed Fresh again, and suddenly started getting the warning about the SD card being damaged and to format it (as we know, that's not the external SD card). No matter how many times I format it, the error comes back. From some other searching, the 'flush-179:0' process seems to have something to do with storage, maybe because it can't read that partition it's causing issues.
Click to expand...
Click to collapse
You nailed it. I was having issues with the flush-179 system process taking up 100% of my CM10's (JB) CPU time. It got so bad that I couldn't even reboot or shutdown without pulling the battery, which of course caused other problems. Initially I thought the "System" process was just out in the weeds, but by using OS Monitor and unchecking "Hide System Process", I was able to find the flush-179 culprit.
My first clue that it might be SD card-related was obtained after opening a terminal window and typing 'mount'. The line for /mnt/sdcard showed (paraphrased):
# mount
...
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,...
...
Realizing that a "flush" process probably had something to do with filesystem caching and seeing the "179" in the mount output, I focused on my SD card. After pulling the card, backing it up, formatting, and restoring it in Windows, I am happy to report that my little Android has been fast, snappy, and problem-free for several days now.
- Dave

Categories

Resources