Anyone heard of an issue where apps in internal storage just start fc'ing then are essentially deleted? I am running cm6 rc2 which I flashed about 6 weeks ago. I haven't had too many issues outside of the bugginess of the ads launcher which I replaced with launcher pro. This afternoon, I try to start up dogcatcher and it immediately force closes, I tried to access the podcast I was looking for through music mod and that fails as well. I thought I might need to reboot, but when I get back into the system two more apps fail as well as the original failed apps not working. Curious, I look in my application list and the apps are mostly gone except for a few apps that show the generic market app icon, which I take to mean corrupted apps. I was able to go into titanium and restore some of the apps to work again, but I have had a pop up stating mytracks has stopped working, but I haven't even started mytracks since the reboot. I guess what I am worried about is If my phone's internal storage is failing? Is it even possible? Any suggestions?
Sent from my Nexus One using XDA App
I had the same thing happen, everytime I rebooted more apps would become corrupt, I was worried that my internal storage was failing, so I wiped everything and started again from scratch, and haven't had a problem since.
When you say start from scratch are you talking about reflashing cm6? I had been holding out since I have been reading about a lot of issues with the 6 stable version.
I formatted the phone, deleting cache and dalvic cache, and then reinstalled. I was using CM6 at the time so reflashed it, did everything by the book to be sure and it has been smooth sailing since.
Only time I have ever had this issue, on the N1 or G1 was after flashing a ROM and not wiping. Sometimes I could get away with it, sometimes not. Wipe and reflash is what I would do.
Hey Thanks guys.
I went ahead and wiped everything and started fresh with cm6 stable.
I am not sure what was going on . I had done a complete wipe and install from stock to rc2 and it worked great for 4-5 weeks. The only thing I could think of was possibly an issue with K-9 mail. One of things I saw happen fairly regularly (3-4 times a week) after rc2 was installed was that K-9 would suddenly just fc. That in and of itself wasn't too weird, but every time it would fc I would get a low space notification right after, where I kew I had 40-50 mbs of space free. Memory leak or something? Dunno.
All weirdness aside, so far CM6 stable is running great...
I've seen this happen when my the /cache filesystem was full. ('App not installed' , FCs etc). Run a 'df' command in a shell to check.
Clearing the cache would be a temporary solution. Moving the /cache to the sd card using DarkTremor Apps2SD is a permanent solution.
I currently have 178 apps.
Related
Let's start with some basic information. I am running not rooted stock Froyo 2.2.1, Baseband version I9000XXJPY, Kernel version 2.6.32.9 [email protected] #1, Build number FROYO.XXJPY. Using stock TW Launcher.
In the morning I've moved couple of apps to SD card. Few hours later my battery went flat and the phone turned off. I've replaced the battery with a fully charged one and the phone was booting quite a while and when it finished it started with locale setting screen. At the same time several apps started to force close unexpectedly. When I went through all the initial settings the wallpaper was the same, icons and widget layout was the same. There were many apps missing (I reckon all of them were installed on the SD card). Many apps that remained were either force closing just after starting or had the settings reverted to defaults.
Some examples:
- Android Agenda widget was in its place but settings missing.
- I've reinstalled TwittCaster and moved to Phone - although it looks like the data/settings are being wiped after every phone restart and I need to put my login details every time.
It looks like many of the apps are reverting settings to default every time I restart the phone.
Both my external and internal cards seems fine, I can access and open files (e.g. photos and music) on them.
When I was trying to install some apps from the Market I was getting error messages that the app cannot be installed in the chosen destination, or there is not enough space. But after few tries I've managed to install them. As far as I know there should be quite a lot of available space.
I've tried to unmount/mount external card, take it out and in again. I've formatted cache partition from recovery mode. I've tried to clear RAM with Task Manager.
I would be grateful if someone could help me to diagnose the reason behind all this, help me to fix it and prevent it from happening in future. I really want to understand the problem and the trigger so I can avoid similar problems in the future
I will appreciate any help.
Thanks!
Sorry to bump, but this is really driving me mad.
It appears that I need to reinstall every app as they all closing unexpectedly on starting. after I reinstall them they loosing settings every time I restart the phone. Is it an external or internal card issue or maybe internal memory? Please help!
I have also noticed that Android Market is quite slow on me. Muc, much slower then before it ask happened.
Sent from my GT-I9000 using XDA App
sounds like hardware failure to me. Its back to factory and exhibiting problems. Why not take it back and have it replaced/fixed?
Sent from my GT-I9000M using XDA App
Strange problem this...
I guess format, reflash and clean install of apps would be a better option... instead of just re-installing apps...
I just wish to avoid sending it for a repair. This is a new replacement I get several days ago from Samsung, for which I was fighting for 4 months.
Anyway I will try to format and reset everything and build everything up from scratch. But if only I could understand how and why it happened maybe I would be able to prevent it from happening in the future.
Is there a special way I can format sd cards before installing and moving apis there?
Sent from my GT-I9000 using XDA App
I am on SGS #2 atm and im trying to stress test it using the HD video method. I have noticed random apps starting to FC. I guess my real question is, Are there certain apps that are more likely to FC compared to others? I noticed the phone gets REALLY slow at loading as it reaches the drive capacity, however, once i delete all the junk videos, the speed returns to normal. Ive also noticed the FC happens when i open too man apps.
Are there any other clear indicators?
Thanks!
Yes,
It's about to go.
Fair well~
Mine did that not too long ago. I was playing Game Dev Story and it got all laggy. So i reboot and i started getting loads of force closes. COuldnt even boot because LauncherPro kept fc. so i reset to factory and speed came back and no fc so far ( maybe one per day..) Strangely , this came right after flash from ODIN for the first time. Although i only flashed a new KERNEL which is speedmod. I NEVER had any problems before that and had my phone since OCT. Anyways, updated to K12O and still on a stock - rooted JL2. Lets pray for the better!
Yep.
Mine started to force close on my email app. Then when I got it working, I tried to attach a photo to an email when the email and picture gallery crashed. Restarted the phone and I kept getting all kinds of FC's on different apps every 1 minute or so. Reinserted the battery, turned it on and it was all over.
I just want the damn thing to die so i can send it in for a new one from samsung...
sleeplessfreek said:
I just want the damn thing to die so i can send it in for a new one from samsung...
Click to expand...
Click to collapse
Well the last thing that did it for me was I had backed up all my apps with myroot then formatted the internal card. Loaded all my apps back to my phone, then I did a mass update on all the apps at the same time. That's when my phone was unresponsive and FC's occurred consistently until the entire phone crashed.
I was pretty happy with Nookie Froyo last night; it seemed to be working well enough & the market was going fine. I had one point where I had to open Rom Manager and set permissions, and it seemed to go on its way & be happy.
Today on the commute in, it fell apart. MortPlayer barfed on a directory, and wouldnt open, continually force closing as soon as it starts. Going into settings & hitting clear data and clear cache didnt do anything: the amount of KB used for both remained exactly the same. I opened Rom Manager, and it force closed immediately. I tried going into settings for it and doing clear data / clear cache, but again the amount of KB used for both remained exactly the same.
How can I fix this? What are likely causes for clear data / clear cache not having any effect? I've seen this last problem quite frequently on my various android devices-- Rom Manager seemed like the perfect fix (only found it last night) but now Rom Manager itself is borked. Help please.
For reference, I have plenty of experience with command lines, and have su, terminal, and adb all working fine. I just dont know what I need to do. And-- on my previous distro-- I found some mounts werent happy about remounting rw.
also, are there logs on these application crashes?
I had the same problem. Are you using a patriot card? Was the wifi on?
I reboot and leave the wifi off. Turn off time automatic update.
Not sure if that what fix it for me. Would not hurt to try.
Using an ADATA "class 10" card (pshaw! 6mb/s does not class ten make!). I was in Airplane mode on the commute. I'll try turning of automatic update.
Let me know. I would like to find out what is happening.
this is interesting i get these force closes on both my centon and kingmax cards cm7 and nookie froyo respectively. The force closes then go into an epidemic with framework services fc every app launch. it makes the nook unusable until reboot then it happens all over again. i use the nook praying the browser doesnt crash then force close hell ensues. I hope there's a fix
based on the lack of responses in this thread i assume this is a known issue. I'll continue to Google a cure
Guys my Nook is freezing sometimes.
I have to shut down manually with the power button .
I am running right now nightlies 102 with OC 18/06.
But I had this problem and with Phiremod test Rom.
I have install the rom to my internal emmc.
any suggestion?
Isolate the machine..by this run without the OC kernel..or try running a different version of cm..many time on my machine with the nightly updates it does also freeze..I always to back to one that does not freeze..remember you are flashing test builds and they must be treated as such. Also..what speeds are you using...are you running setcpu with at boot option on..which you should not do. It WILL lock up..have you deleted any of the .apk files? Did you clear the cache and dalvic?
life64x said:
Isolate the machine..by this run without the OC kernel..or try running a different version of cm..many time on my machine with the nightly updates it does also freeze..I always to back to one that does not freeze..remember you are flashing test builds and they must be treated as such. Also..what speeds are you using...are you running setcpu with at boot option on..which you should not do. It WILL lock up..have you deleted any of the .apk files? Did you clear the cache and dalvic?
Click to expand...
Click to collapse
I will try to clear the cashe adn dalvin. No I dont use setcpu I know that it will crach with the preinstalled performance settings.
Try a complete flash with a differently nightly..what I mean is wipe all 3 (dalvic, data and cache and try just to boot) some times the nightlife are not very friendly... Build 110 comes to mind...it froze up..had to do a complete restore..frankly...I am getting tired of always flashing theses...my favorite is build 64 with the 1.3 sped kernel. For me this was running just right. I am going to flash 112 later tonight and I want to write a guide to which apks to remove safely for new flashers..I been meaning to write one for awhile..
life64x said:
Try a complete flash with a differently nightly..what I mean is wipe all 3 (dalvic, data and cache and try just to boot) some times the nightlife are not very friendly... Build 110 comes to mind...it froze up..had to do a complete restore..frankly...I am getting tired of always flashing theses...my favorite is build 64 with the 1.3 sped kernel. For me this was running just right. I am going to flash 112 later tonight and I want to write a guide to which apks to remove safely for new flashers..I been meaning to write one for awhile..
Click to expand...
Click to collapse
maybe I will try a new build tonight.
I will report back.
cool......
searius said:
Guys my Nook is freezing sometimes.
I have to shut down manually with the power button .
I am running right now nightlies 102 with OC 18/06.
But I had this problem and with Phiremod test Rom.
I have install the rom to my internal emmc.
any suggestion?
Click to expand...
Click to collapse
Try the new CM7.1 RC release. I always do a clean install whenever i have freezing issues or i feel that nook is running slow.
http://download.cyanogenmod.com/?type=RC&device=encore
To many freezes,
Oh how dare you mock me so.
Power off again.
sounds like SOD...
SOD: http://forum.xda-developers.com/show....php?t=1108964
I have put nightlies 112 now.
For the moment I had not any freeze only one time SOD.
But I have not use too much the Nook those days. I have exams
It doesn't look like Sleep of Death. My NC is not sleeping. Just when I'm in some application (for example, Angry Birds) it becomes extraordinary slow.
I exit the application and it is slow in launcher screen. Looks like frozen, then after several seconds it starts reacting on previous gestures. Then long delay again. Have to power off or reboot Nook.
I saw it yesterday for first time. My Nook was turned off for ~2 weeks. Then I turned it on and updated some apps in market. I noticed Netflix app was in memory. I don't think it loaded automatically at start up before.
I have CM7.0.2 stable, with normal kernel at 925MHz. I installed more than 100 apps, maybe one of them is the reason. It happens quite often, maybe once in half an hour. It can also happen in market during update. Nook is unusable right now.
But my friend has CM7.0.3 and he didn't install that many, I believe he has the same problem.
Will try to wipe stuff and to prevent unnecessary apps from starting with autostarts. Will see how it goes.
With that many apps...make sure you clean out the cache frequently...there are a few apps that do that free on the market....when got got my first android device...a evo I would load everything I could under the sun and delete and installed like crazy....now I have a few trusty apps and I clean out my cache everyday....browsing along will fill up the cache like crazy...
searius said:
I have put nightlies 112 now.
For the moment I had not any freeze only one time SOD.
But I have not use too much the Nook those days. I have exams
Click to expand...
Click to collapse
Glad to see you up and running.....
life64x said:
With that many apps...make sure you clean out the cache frequently...there are a few apps that do that free on the market....when got got my first android device...a evo I would load everything I could under the sun and delete and installed like crazy....now I have a few trusty apps and I clean out my cache everyday....browsing along will fill up the cache like crazy...
Click to expand...
Click to collapse
The only reason to do this kind of nonsense is if you need more space in /data, which is unlikely a problem on the Nook Color.
khaytsus said:
The only reason to do this kind of nonsense is if you need more space in /data, which is unlikely a problem on the Nook Color.
Click to expand...
Click to collapse
I have to disagree...I use firefox on the nook and after a few hours of surfing..it will slow down dramatically...clear my data cache and speed goes up...Also...the more apps loaded the more processess and services runningcin the background which results in overall slowdown...I really don't know why you call it nonesense when it is simple math..the more you have and use the more it is caches and or memory is gutted down with more crap running on it in the background and or swapping in and from cache.
I wiped cache partition and Dalvik cache using CWM recovery. NC looks better now. Didn't freeze so far, but I need to test more.
Thanks
PS. I rarely use browser. It froze while playing some game, or immediately after exiting game, in Zeam launcher.
micksh said:
I wiped cache partition and Dalvik cache using CWM recovery. NC looks better now. Didn't freeze so far, but I need to test more.
Thanks
PS. I rarely use browser. It froze while playing some game, or immediately after exiting game, in Zeam launcher.
Click to expand...
Click to collapse
I don't do the dalvic cache...I am talking about the general cache...currently using 'cache cleaner' from marketplace and works like a charm.
my nook has been freezing a lot lately too. randomly. it doesn't slow down or anything, it just freezes and I have to hard reboot. at least 3 times a day. I am on nightly 116, this has been happening since beta 3.1. using 6/18 kernel. overclocked to 1175.
sometimes it will even freeze right after the bootanimation as soon as it gets to the main screen. Any ideas on what I can do? I have changed the kernel from conservative to ondemand and that didn't help. I lowered the overclock from 1200 to 1175 and that didn't help.
edit: as I was typing this it froze while clicking on the dropbox app. I restarted and it froze as soon as it got to the homescreen. also just cleaned the cache. freed up a lot of memory but it didn't help.
Slow clock down to stock..or flash another build...also just use cm for over clocking if you are using setcpu..uninstall it..I don't know if you are. Try interactive...if still freezing..with setcpu..yes..reinstall..basically try different combos...when you find one that is stable...backup and use that as your daily driver and then experiment with different build.
I cleaned program cache too, with Android Assistant. I guess it's the same. Nook froze badly today. Played Angry Birds, froze completely. Pressed "n" button, exited to launcher, but could not do much in it. Only long-press power button helped.
The thing is it worked well two weeks ago. Then I didn't use it, then I downloaded few free apps from Amazon and ran out of space on eMMC. Then I moved some apps to microSD (I don't think I moved Angry Birds but it looks like it is on SD for some reasons). And my microSD has bad random access times. Can this be the reason?
People in this thread http://forum.xda-developers.com/showthread.php?t=1005633 reported problems when booting OS from slow cards. It probably applies to apps on SD too. I bought Sandisk card now, but it will take time to deliver.
I'm running cm7.1 stable, running off emmc, and every now and then my beautiful NC just locks up, I have it OC to 1.2ghz, I did a search and only end up with results from older nightly threads. Is this a common issue or just me?
PS... I have reflashed and cleared, data,cache, etc..
Thanks
Sent from my NookColor using XDA
Have you always had the issue or did it start recently? I would look at uninstalling any new apps you downloaded prior to the issue starting. There is a good chance you might find a bad app to be your problem.
It wasnt happening before, I tried cm9 with opengl, after I reverted back to cm7(fresh install not nandroid) it started happening, the apps I am running were the same apps I was running before trying cm9(and the freezing problem wasn't happening)
Sent from my HTC Sensation 4G using XDA
Since you are going for a clean install anyway and there is no issue with the CM7 install script did you try the factory reset option or was it just the caches that you cleared? Have you confirmed that you have a good download of the CM7 zip?
Also you might want to try flashing your latest nandroid and make sure that is still running the same as when you created it. If so and you still want to install fresh try it coming off of that one instead of from CM9.
JP
I've had trouble with both Beautiful Widgets and Google Currents locking up my CM7. Got rid of those and I essentially never get lockups any more.
511pf said:
I've had trouble with both Beautiful Widgets and Google Currents locking up my CM7. Got rid of those and I essentially never get lockups any more.
Click to expand...
Click to collapse
I do have beautiful widgets installed, let me remove it and see if it helps
Sent from my HTC Sensation 4G using XDA
So did removing BW resolve the random freeze? My wife's NC is doing the exact same thing and she has BW too. But I just installed CM7 on hers last night so not sure if BW is the culprit or not yet.
I've been running CM 7.2.0 RC1 from SD card about a month now, and I've experienced a number of freezes. On April 5, I had two freezes within a few hours, and I started keeping track of the freezes, hoping a pattern would emerge.
From April 5 through April 17, there were a total of eight freezes. I don't know what the uptime was when the first freeze occurred on April 5, but all subsequent freezes occurred with less than two days uptime. During those 13 days, uptime got above two days on two occasions; both times a "Sleep of Death" occurred before uptime reached three days.
Was there a pattern? Yes! Every single freeze occurred while I was using Opera Mobile browser, and browsing these forums at forum.xda-developers.com.
On April 18 I started using Dolphin to browse the xda forums, and there has not been a single freeze so far. (I still use Opera Mobile for other browsing.) Uptime had reached five days when I voluntarily rebooted this morning.
I realize this may not be relevant to the rest of the discussion in this thread, which seems to deal with CM 7.1. Then again, maybe it is. This seemed the logical place to report the observation.
Update: Opera Mobile has updated to version 12.00.ADR-1204201824 on April 25. I'll revert to using Opera Mobile on the xda forums, to see if it still freezes.
My freezing problem was resolved by moving a bunch of apps from SD back to phone. I left on the SD partition apps I don't use often, and I made sure all apps on my launcher page in ADW were on phone.
threebeers said:
My freezing problem was resolved by moving a bunch of apps from SD back to phone. I left on the SD partition apps I don't use often, and I made sure all apps on my launcher page in ADW were on phone.
Click to expand...
Click to collapse
You really don't gain much and lose a lot by running apps installed to sd. Since everything is automatically on 'sd' with an sd install, those that say they are installed to phone are really still on sd (in /data, which is also on sd). The only reason to install apps to sdcard is if you have so many installed that you have no more room in /data. And with sd installs, usually the /data is made of a generous size. Installing apps to sd slows your system since it has more system overhead to work through.
I know it sounds confusing, but with sd installs, installing to phone means installed to /data which is a partition of your sd. If it says installed to sd, it means it is installed to sdcard, which is another partition of your sd. So no matter where you tell it, it is all on sd and /data is faster because of less system overhead.
For anyone else having this problem, I found that if it was overclocked for me, it would freeze a lot more frequently. But, that may have just been bad luck on my part!
pink401k said:
For anyone else having this problem, I found that if it was overclocked for me, it would freeze a lot more frequently. But, that may have just been bad luck on my part!
Click to expand...
Click to collapse
Came to post the same thing. My nook color will run max OC 1200 but often it will freeze for no reason. After many attempts of uninstalling the many different apps I thought were causing it I started moving the OC lower in small increments and running for a long as possible without a freeze. Finally got down to 975 and haven't had a freeze in days.
Kinda disappointed though since someone got it at 1600 and most run at 1200 and all I can get is less than 1000. I'm probably moving to a Asus Transformer Infinity soon anyways though.
It has been known since the early days of Dalingrin's overclocking kernels that many of the NC's have issues with anything above 1100 MHz and undervolting can create a great deal of instability.
My recommendations are to try 1100 MHz max... and lower voltage .05 mV at each step. I personally never have issues with these settings...
You can then try lowering voltage .05 mV at a time until you start having issues... then increase it back to the last one you had no issues with.
I just leave mine at 1100 and .05 mV lower than the reported "Stock Voltage"