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
Related
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.
Ok this has happened to me twice now, after turning off my phone and switching batteries every applications except for stock ones will continually force close. I am using Voodoo lagfix on JM1 official so unsure if this is causing it. I am able to fix applications by running titanium backup and restoring the apps but this becomes tedious with the free version and I'm having issues with paypal donating for the paid version.
Has this happened to anyone else? I'm thinking maybe the issue is that I pull the battery out a second too soon and it somehow corrupts the data.
Same problem here with a i9000b 2.2.1 Kernel 2.6.32.9
When I switch between the original and spare batteries, the first confg screen comes out (language and first options). Most not-stock apps forcing close and google maps also not working.
I've had to the factory reset twice, so i decided to do experiences. I switched many times, with and without "no stock apps" installed; after 1 munute off; just after the screen out and without switching off at all. The funny thing is that I had no problems these times, except the config screen coming when I didn't switch off before switching (but apps didn't force closing).
It seams to me that the bug happens when memory is quite full or you have made some more configurations. I will try to continue my normal use and see what happens if I switch spare-original battery again.
this same thing happened to me, but i use launcher pro so can't do anything and clockworkmod is not in the recovery anymore so i can't restore to a previous configuration. WTF? anybody have a fix for this?
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
I recently moved to HellyBean. It has behaved fabulously on my Captivate. But I'm not sure I want to stay here because of one issue - without killing it (by hand or automatically), the media scanner runs continuously now (continuous 100% cpu usage). This takes the battery down really, really fast. When I have the process killed, battery life is extraordinary!
But I'd like to solve this if possible. Is there a chance it isn't HellyBean or JellyBean related (the way the multiple copies of music was an ICS issue)? The fact that no one else reports anything similar would make me think it's possible. If so, can anyone suggest what might be the issue.
Or what might be the other problems I might anticipate with the media scanner off. It sees my music, and seems to play everything. Camera works fine.
I did a scandisk of my removable SD, and it found no errors, and still gives the same issue on scanning - never stops.
This happened to me on GB with Corn Kernel 7.06a. I booted into recovery, cleared both dalvik cache and system cache, then booted and media scanner went through its startup normally.
you orobably know this:
it takes a long time to boot the first time after clearing caches. just wait for it to finish.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Thanks for the idea. Thought I had probably tried it before, but it was worth another shot. Unfortunately, it didn't work. CPU usage still pegs out at 100% until I shut her down.
maybe try freezing media storage app with TiBu or system tuner then reboot. Then you can troubleshoot without cpu tied up?
have you booted with external sd card removed?
if you can't freeze it due to cpu tied up, then boot into recovery, turn off init.d, syscontrl tweaks, oc, and whatever else to see if it helps.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
laughingT said:
have you booted with external sd card removed?
if you can't freeze it due to cpu tied up, then boot into recovery, turn off init.d, syscontrl tweaks, oc, and whatever else to see if it helps.
Click to expand...
Click to collapse
Two good ideas. The external sd was fine. But I had some crap in the init.d (I don't know how, I thought I had cleared it on the flash) that wasn't decipherable. Deleted that, booted up, and it's fine now. Mega thanks.
Problem is cleared - thread can be closed now, moderator.
I have this same issue on a Galaxy Nexus and Galaxy S II:
http://forum.xda-developers.com/showthread.php?t=1884381
http://forum.xda-developers.com/showthread.php?t=1889331
So I was running eXistenZ 4.0 and I had enabled Ram swap. I was having the most smooth experience I have ever had with this POS phone. One day though, the notification/charging LED stops working. After desperately trying and failing to find a fix, I flashed a stock FTF and restored a previous Nandroid backup and VOILÀ! , My phone was back to normal. Oblivious as to what caused the problem, I enabled Ram swap again. Everything worked fine for a few weeks but then something happened again. This time the stamina mode stopped working. I was extremely pissed. So I set out to find out what happened and try to fix the problem. I failed in my attempt to fix the problem so I ended up restoring a nand backup but I did end up finding out what was causing the problems. It turns out, while using apps that were very RAM intensive, Sony services were being moved to the swap file. During the first time, the "Light Effects Service" was moved among a few others and during the second time the "Eco Mode Controller Service" was moved. They were moved back automatically, But they never really started up again. After figuring this out, I tried to manually recreate this incident. I clean flashed a ROM and made sure all the services were working. Then, I installed Greenify and greenified the two services mentioned above. After I degreenified both the services, I restarted the phone to check if the services automatically started up. They didn't. Therefore, I have come to XDA to share my findings.
I have made this post for two reasons .
1) To ask all the good people of xda about a possible solution to my problem. Is there any way to use swap and prevent this from happening?. Can I lock the Sony services in primary Ram and prevent them from being transferred to the virtual (SWAP) Ram. Or do I have to give up using SWAP?.
2) To warn people about the possible complications that are sure to arise when they use SWAP on our XPERIA SP and possibly other Xperia smartphones.