18 replies to this topic

[Eusibius]

Might be app specific, then.. but triggering a similar effect.

FWIW - I have Angry Birds on my SD card.  Still no mass FC's.

kmbear, on 09 December 2011 - 03:05 AM, said:

Another vote towards Angry Birds being installed on SD card instead of internal memory being one of the culprits for this problem.  Just uninstalled it and my problems are gone.

[Paul600k5]

I've been having this issue of cascading, or mass FC's since about the first week of running 7.1 Final. Never, ever before that. Never. Not once. Not maybe that one time that I thought was something else but could be related. Never. Did I mention never? Except now, almost weekly, everything crashes. Nothing opens, things that open (settings is really the only thing that will) immediately crash. Text messages come in and are displayed on the notification bar but when I try to view them, handcent fc's and they are lost. After a while, I gave up on 7.1 final.

That brings us to now. It's been a week since I threw up the one finger salute to 7.1F and flashed back to my Nand of 7.1RC1. For most of that week, I had whiplash. The phone was so fast and so smooth that my eyes couldn't keep up. It was invigorating! Last night, before bed, I had 26% battery left... after 21 hours! I should mention that I run InvisibleK No.28 which helps explain the performance. Today though, uh oh, goodbye functionality.

So there I was, innocently opening up Dolphin Mini to look something up for my girlfriend, when it unexpectedly crashes. Huh, I thought. Maybe I should just restart it and try again. Same thing, I get to the site, scroll down, start reading, BOOM! It crashes. "Blast you dolphin mini!" I cry. Oh well, Opera works. Oh wait, no it doesn't. Another FC. Now I'm nervous. I do a power button reboot. Waiting... waiting... order lunch... waiting... waiting... appetizers arrive... waiting... Lockscreen finally shows up. I unlock it. There were so many FC's that I think "Hopes and Dreams" FC'ed. "Your Future" has experienced an unexpected error and must shut down. So I try a battery-pull restart. Same thing. Reboot into recovery then restart system. Same thing. It's a "pretty brick." It boots but won't run anything. I'm out of options.

Did I mention that this is now happening after a full wipe and restore of a system image which functioned perfectly for several months? To say the least, I'm pissed.

[MrAb3z]

Hey Paul600k5, I had all the same problems you experienced, as well as everyone else here I think, when I upgraded to 7.1.0 Stable. Like everyone else, was amazed with the the changes and stuff. Within hours though, the FC and everything else that could go wrong went wrong. There came a point where I could even receive text messages nor send them anymore, attempting to do so would force close the text messaging app/service. I gave up on it and reflashed back to 7.1.0 RC1 hoping it would resolve the issues. It did kind of at first, but my phone was still experiencing a few FC here and there. After about a week later and a few reboots, the phone was back to normal. Now it only acts up once in a blue moon, but other than that its pretty good. So I guess wait it out and just reboot your phone for a few days, see what happens.

What's kind of upsetting about this is that the RC1 never gave me problems before I upgraded to the stable version. And I mean never, it ran smooth since day 1. But since my run in with the stable version from hell, I feel like its left my phone a little sluggish, and for lack of a better term, somewhat corrupted RC1 (I emphasize "lack of a better term", I'm not implying the stable version actually corrupted the RC1). It's almost like the stable version gave my Incredible the phone-herps: I can manage the symptoms but it still has flare ups every now and then.

What's more upsetting is that no one in the CM team seems to be really doing anything about it. Now hear me out, I know they are busy working on CM9, and I know they probably have a shitload of other **** to do. But this seems to be a very common problem amongst various phones with this version. At least give a heads up, let people know "hey we're aware of the problem and are working on it" or "hey guys we know something is fucked up with 7.1.0 right now but were a little busy with other things at the moment, we'll get back to you." Some form of communication or acknowledgement would go a very long way at this point. I don't know, maybe its just me but I would really like to see what 7.1.0 is capable of if not at least bring my phone back up to full speed before everything kinda went down the poophole.

[jbcode42]

Just want to quickly clarify some things people seem to be missing.

1) The CM team is not working on this issue.
This is just plain incorrect. CUViper even has changes that helps alleviate the issue in the more recent nighties. The problem is the base android design and the HTC incredible design. I would go so far as to say this is a design flaw with the HTC incredible. As CUViper said, "It's not really a software problem that CM can fix, or I would have done it." Unless you are a developer and think you have a solution, assume that CM team is/has worked on this issue.

2) The phone will say out of memory or out of space.
This is not what it says. You will not "see that warning" unless you are running a nightly with CUVipers fix (as far as I understand the fix, please correct me if I am wrong). However the bigest indication that this is the problem without running df -h to check your /data/data size, is to read what the force close is. If it is an IOException or a lot of SQLite exceptions, it probably is the issue in this thread.

3) Downgrading or switching back to stock fixes it.
This is not true either. All the versions have the exact same amount of space. In my experience I actually had worse issues with stock due to the Dialer Storage. It is important to note that switching may cause the *illusion* of fixing the issues, but really all it does is when you reinstall your apps, your cache is clear, and it fills up again over time.

4) It is hard to identify the worst culprits.
I have successfully identified the worst culprits by using a command I think someone posted earlier, "du -sk /data/data/* | sort -nr | head"
Yes, it is a mess to type on the terminal (note you should probably su before trying it), but it will list the biggest abusers of space. Some, such as com.groupon, have a cache folder that you can safely delete the contents of. Some, like firefox, may be large due to the size of the native libraries it uses and may be harder to clean, if not possible at all. If one of the top apps is not one you use, you may want to consider uninstalling it completely!

5) Rebooting the is the best course of action when this starts.
I have found its easier to nip this on the bud by not rebooting and fighting through the FCs, even if that means I have to temporarily uninstall an app until I clean stuff out.

6) Anything with a bunch of FCs is defiantly this issue.
Note that this can also be caused by a faulty flash memory that /data/data is mounted on. Although this situation is not likely, it is worth noting that it is possible for there to be other things that cause similar symptoms.

I just wanted to clear out a couple of possible points of contention to the best of my understanding. If I am wrong on any of these, (particularly what CUViper's fix does), please correct me.

[mach]

"3) Downgrading or switching back to stock fixes it.
This is not true either. All the versions have the exact same amount of space. In my experience I actually had worse issues with stock due to the Dialer Storage. It is important to note that switching may cause the *illusion* of fixing the issues, but really all it does is when you reinstall your apps, your cache is clear, and it fills up again over time."

I really have to disagree with you.  I never had any problems with FCs or rebooting until I switched to CM7.1.  Never.  Then I flashed CM7.1 and the problems began.  And not just minor problems, I'm talking about boot-loops that could only be stopped by battery pulls, and rampant FCs

If you go back through the thread, you can see that I went back to stock on November 16th.  All of the problems that began when I flashed CM7.1 have been gone since that time.

I don't see how you can attribute this to an "illusion".  Almost a year and a half of running a stock ROM, with no problems, and then switching to CM7.1 for a month and having so many issues that I wanted to launch the phone out the window, then going back to stock and having no problems.  This is no illusion.

[Paul600k5]

Agreed with Mach. These issues were not present for me on stock 2.2, any of the sense-based roms I've run, MIUI, or any CM7-series roms up until 7.1 Final. After the probably began, I did full wipe reflashes, changing kernals, format sd-card and even flash back to older versions. The problem I'm having now is that it randomly starts the FC-flood and my phone becomes a fancy pocket clock until some period of time has elapsed and it starts working again. I have over 100 apps, most of which I've had for months and never gave me problems before.

[markybob]

i found that manually formatting /system in recovery and reinstalling CM from scratch fixed the contact fc's.  "full wipe" does *not* format /system, so you need to do it manually.

[AcumenProbitas]

This issue has come and gone for me over the past few months.  I believe I was dealing with two separate issues.

I compulsively moved apps to the SD card to avoid filling up /data/data to 100% because I would experience the cascading force closes.  When I updated to 7.1, I started to experience the freezing issue.  The freezing issue went away after an SD card reformat... until the $0.10 app sale.  I bought some big apps (20-30mb), and .android_secure on the SD card was approaching 1GB. I started to experience the freezing issue again.  I wiped/restored with TitaniumBackup, freezing starts again when I install my big new purchases.  Even without the new apps, it still took 3-5 minutes to load the apps from my SD card after a reboot.  Also, every time the phone booted and attempted to load apps from the SD card, ADWLauncher would freeze and need to force close.  If I missed the prompt asking me to force close ADWLauncher, the phone would freeze up completely.  I decided moved the smallest apps back on to my phone (anything 2mb or less in .android_secure) and now there is almost no delay loading apps from the SD card, and no freezing issue.  I am not sure if it was an issue with the number of apps on the card, or with the size of the folder, but it's better now.  /data/data is still okay too, since most of the apps I moved were small.

[spadesluck]

I created an account just to put my thoughts in.

When I was running 7.1 RC1 I never had one problem with my phone the 7 months I was deplyed with it. The day I switched over to 7.1 stable I had nothing but a crap ton of problems, Force Closing everything. I have since then moved to the nightly build 258 and am back to having no problems what so ever. No force closing anything. There is something really wrong with the stable build. I thought is was just my phone but as it turns out it is not.

[Tothinator]

I had a lot of similar problems to those above. I've been stable for a few days now since
1. cleaning out some apps that showed up as having a lot in /data/data
2. Switching over to nightly 258

Not sure what the real root cause is, but just thought I'd add my results too

[RoninX]

Hello,
I was going to take the plunge on CM 7.1 stable (first time ever modding) until I read this thread.  Now I want to try out nightly 258, but when I go to http://download.cyan...e=RC&device=inc , I'm getting a "Website Offline, No Cached Version Available" CloudFlare error.

Are there mirrors available elsewhere or when will this problem be fixed?

Thanks!

[RoninX]

Well it's back online!   I just needed more patience, I guess.
Flashed to 258, running great so far.

I know the Incredible's an old phone, not even supported by HTC anymore, but is development on this still continuing? (nightly 258 seems to be the latest which was 11/16/11)

Edited by RoninX, 06 February 2012 - 07:08 PM.

[CUViper]

The good thing about CyanogenMod is that most development applies to all supported devices.  The nightly build server just had some issues, and I think decided not to bother rebuilding it for CM7.  So yes, new stuff has been added in the meantime.  There will eventually be a 7.2, and you can get a preview with one of the KANG builds floating around on XDA or RootzWiki.

[RoninX]

Thanks, I'll check those out also.  Loving CM 7.1...wish I tried this out sooner.

You guys are doing an amazing job!

Edited by RoninX, 07 February 2012 - 09:28 PM.

[bwanamarko]

CUViper, on 01 November 2011 - 04:55 PM, said:

Garaxiel, that logcat show sqlite IO exceptions, which probably means your /data/data is full, a common issue.  I'm working on getting this handled better, but in the mean time you should try a cache cleaner to free up some space manually.

@CUViper - do you know if this has an issue associated with it on google code? searching the issues I could not find any mention of it. Also how would I know which app in my /data/data folder is too full without checking every folder? use the --recursive option and --size (I can't remember the adb/busyBox options)? Could I just wipe the entire /data/data folder and then restore user data from Titanium?

[bwanamarko]

CUViper, on 16 November 2011 - 06:41 PM, said:

FYI, nightlies starting from 256 should manage cache cleanups automatically now.  It's still a problem if you have too much genuine data though.  You can see each app's usage with a command like "du -d1 /data/data | sort -n" to find the biggest offenders.  Maybe you can also compare that from your time at 69% to 90% to see what grew so much.

@CUViper my version of BusyBox doesn't have the -d1 option (although I'm using teminal emulator from CM7.1) maybe this is only available from adb shell?

[CUViper]

bwanamarko, on 08 February 2012 - 06:36 PM, said:

@CUViper my version of BusyBox doesn't have the -d1 option (although I'm using teminal emulator from CM7.1) maybe this is only available from adb shell?

Hmm, CM actually comes with BusyBox and other utilities already.  The version in /system/xbin/du should support -d1, I just tried it.

You can get a similar result like this: "du -s /data/data/* | sort -n"

[bwanamarko]

@CUViper my bad, "du -d1 ..." work fine. I was misreading the --help, and didn't interpret the -d N directions well. Thanks for the response, and sorry for being such a n00b.

[funkpod]

hey, i am brand new to rooting.  literally.  less than a week old.  however, i rooted initially to fix the low storage space issue on my Incredible.  


I used this mod...
"Convert2Ext4_no_data_limit_normal_dalvik.zip"

http://forum.xda-dev....php?t=1315372r

based off of these directions...

http://forum.xda-dev...d.php?t=1488351



and, it works!  it moves everything in the /data/data partition into the 750mb of internal storage, so now there is a lot of room!

and i think that this mod works on Cyanogenmod.

would this Mod fix these force close problems?  

Susan, did you ever find a solution to this problem?  is it still happening, everyone?  I am very very very curious about trying CM7.1..... but maybe I should try an earlier release?  which one would be more stable?

thanks, and hope this Mod i mentioned helps.