Related
Hi,
I have a rooted GT-i9000m (bell Galaxy S Vibrant). I used the one click lag fix to root my phone and it works fine.
A few days ago out of no where all the apps started auto closing as soon as i opened them and then both the menu and back touch buttons lit up and the screen went black. I held the power down till it rebooted only to get and error with com.android.calendar even tho I never use the app. When it finish's booting none of my installed apps are showing.
The first time it happened with com.android.app and I did a full wipe and factory reset and just reinstalled everything.
Ideally I don't want to system reset to factory settings again and lose all my files and notes that i copied back on to the phone 2days ago...
Please note I have tried clearing the data for the calendar app in settings -> apps and i cleared the calendar back up. My problem is that none of my installed apps are showing...
(Update) I also cant reinstall or update apps due to a Installation error - Insufficient storage. But there's room on both SD cards. I also set 850mb for apps when i did the one click lag fix and i don't have 850mb of apps installed.
(Update 2) I did a factory reset again this time i didn't format the internal and external SD cards. (It works like new again) Thus I got to keep all my personal files and ring tones ect. The only thing that was deleted that I didn't back up is my Notes. This leads me to my new question whats best for backing up apps on a rooted SGS (bell Vibrant)?
If anyone has answers they would be much appreciated.
i had the same problem
install rom manager from the market place
there is a option in there "Fix Permissions" just run that and it will fix it up for you
only takes 1-2min to run
Tried what you said but i cant install anything... I get Installation Error - Insufficient storage available.
I now understand the cause of the problem. I change my battery once and some times twice a day. At first I would wait for the long shut down (untill the screen goes totaly black) and then take off the back and swap out the battery. At least 3 times the phone would boot up and ask me for the network unlock code (I bought the unlock code directly from bell for 75$). I found this rather annoying so i tried just taking the battery out wile it was on (idle) and it appeared to work flawlessly at least 20-30 times before the phone would start to do an endless force close loop cycle. This kept forcing me to do a factory reset on the phone. I can only assume the one click lag fix and my disregard for the need of the shutdown before removing the battery must be all the cause of my problems.
I will try and see if my phone is more stable with out the one click lag fix.
nope that is not the cause of the problem
but it sounds like you are another victim of the lag fixes that is killing your internal SD card.
not the fault of the lag fix, it just make the problem apear sooner than later
I have been having a similar issue and I'm using Voodoo lagfix. I think it's because I took the battery out before it had completely shut down.
read this
http://forum.xda-developers.com/showthread.php?t=793404
Well the phone bit the dust today. I opened up google maps to look up an address and it crashed with the usual error. So i rebooted the phone and now it stays stuck at the boot logo. (the glowing S with both touch keys staying lit) So i did the recovery thing again but this time I had to do the Vol-up + home + power in order to get the phone working some what. IDK but it wont let me log into my google account to sync my contacts. My APN settings are correct and working and I even tried off my Wifi at home. I'll just hope its a google problem and not my phone acting up. Thanks for the pointer to the bad internal SD. That may be the problem kinda hard to prove it to Samy thoe...
I get force close errors after about 4-7 days of use. Now its gotten worse. A few days ago I was looking up an address and my phone crashed and rebooted it self. It then hug at the S boot logo for 20mins. I got to my friends apartment building to find my phone still stuck at this boot logo. I couldn't remember his apartment number or buzzer code... Normally i just check my contacts list and buzz the code. I was standing out side in the Canadian fall cold wind trying to get this phone to work... OMG i almost just smashed it on the spot. Anyways I remembered about something i had read on this forum about the recovery mode ( i had used it to root ) so i tried that out got the little menu and tried every option before having to do the dreaded factory reset. Well nothing work with the exception of the factory reset it got my phone working in about 5mins... LOL
Anyways I thought I might try upgrading the firmware when I got home. What a mistake... I cant control my phones MP3 player via my bluetooth car stereo any longer. Tried everything even a factory reset and formatting the internal and external SD's. I tried running it with out rooting it again and with out the lag fix in hopes that I wouldn't get a force close error. Wouldn't you know it about 5 hours after the factory reset un-rooted just after i finish coping over all my music. I get a force close error! So I tried again and this time the phone ran for about 30hours before it started giving me force close errors about the email now...
Sigh I've tried just about everything in my power to make this phone work. So I assumed it must be the phone... I called Samsung up to get a RMA going... Wouldn't you know it they tell me that I have to call my carrier to get it RMA/repaired. I try to explain that I bought the phone with out a contract and bought the unlock code from Bell so I could use it on Fido. They tell me to call Fido... ROFL Fido wouldn't even give me their APN settings when i got this phone so knew they would be of no help. They don't even have one android phone in their line up i tell the sammy rep. So they tell me I should go back to the Bell store I bought it from to get it repaired/RMA'ed.
I doubt Bell will be of much help but here's hoping.
Do you think my phone is broken, bad flash, buggy memory, ect and needs to be RMA'ed?
Update...
I got my phone back from repairs 2 weeks ago. They flat out replaced the phone for a new one. This was a huge headache for me because the new one wasn't unlocked. Took Bell 2 hours to get the new one unlocked wile my wife waited out side double parked downtown! (I thought it would be a quick pick up and I would be out) The blue-tooth works flawlessly again!!
Much to my dismay the replacement phone has started acting up much like my first one did. It gets several force close errors a day and has gotten to the point where it no longer can send or receive text messages (using Handcent). The stock Music Player app also force closes at random with more frequently. It looks like I got another Lemon. This time around I did NOT root, lag-fix, or flash firmware. I will be sending it for repairs as soon as I can afford to buy another phone to use wile this one is off at repairs. My back up phone is a 3~ year old Iphone3g that my son has made his... (cracked screen, vol rockers dont work, power button is jammed in, the LCD screen it self is bleeding on the top edge)
The Vibrant never let me down other than as a phone. As a divx player or using all-share it rocks! I use these features A LOT to play my 720p divx movies on any TV or the projector in the bedroom .
with that being said I might keep the phone just as a portable movie player to bring from place to place and put my sim in something more stable.
TL;DR: My phone is experiencing a very similar problem to the broken internal SD after Froyo update, except on eclair and is fixed (apparently temporarily) with a factory reset. I'm on Telus, bought the phone from somebody off craigslist and have a return receipt. What should I do?
So for the second time in a few days my Samsung Galaxy S (I9000M from bell, bought on craigslist running on telus) was having problems opening an app so I restarted it. (The first time Market would force close whenever I tried to open it, the second time it was Browser). After the app force closed a few times I did a restart. The first time I restarted it (when Market froze) it went to the lock screen, with the default background (it looked like my data was all wiped). After unlocking the screen, I got a perpetual series of force close messages. This happened each time. I had to do a factory reset and lost all my settings, photos, messages and everything (No backups, of course. Facepalm). Then today I pretty much had it back to the way it was before the reset, and Browser force closes repeatedly on opening. I restart the phone again and this time it only gets to the 'S' animation then goes black/restarts after the animation stops. The capacitive buttons sometimes light up. Similar to the issues from the Froyo update I think, except I didn't update to Froyo. I can get to the 3-button recovery screen and do system reset as well which seems to not help the froyo issue, I think. It's currently working but I'm not sure how long that will last. I'm not pleased about having a phone I have to re-setup every few days. (I'm actually pretty angry...)
Anyway, I have a "Mobile Device Repair and Return Receipt" from the seller from craigslist. It's still under warranty. Anybody else experience this? Can I take it to bell and have it fixed with the documentation I have? What would you suggest I do here?
I was just getting over the initial buyers remorse phase for my galaxy (or in my case, flashers remorse, even though I run stock JPY and it's fine, I have this urge to re-exchange it for a SLOWER stock Vodaphone Australia 2.2 version that's probably more buggy, but at least truly stock), when I drained my battery to 1% to test battery life, and shut it off manually.
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) left right and center then went straight back into default first-boot menu, like the very day I received the phone, or after a hard reset. The funny thing was, instead of having default values selected, it had the ones I had already put in. I thought it would be fine after that. Wrong.
I tried rebooting it again to see if it fixed itself, and it does the same with the forced closes. I uninstall my background and re-install it, and save some settings. When it boots it restores the live background back to it's stock settings (the live wallpaper I chose is still there, but the settings for it are not).
At this point I'm scratching my head so I uninstall all apps. This time on boot it doesn't throw up "force close" errors, but instead force-closes a single app or service for me on boot, with the one buzz, then three quick buzzes. Sigh... I have to factory reset my phone. One thing that particularly annoyed me was the fact I moved all my apps (AngryBirds ) to my external SD card, yet miraculously, after the reset my phone doesn't seem to think it's there anymore! Another thing I'm pondering is that if I didn't reset my phone like this, would this still have occurred?
Runs perfectly fine after the factory reset, with no errors or anything on boot as of yet. I have been compulsively rebooting it ever since just to find out, LOL!
Is this a 'normal' sort of thing to happen on the SGS, or is just through shear coincidence the combination of me restarting the phone in it's booting phase + the low battery life screwed up some boot settings while the phone was writing to it, or is it some hardware error? I can see this as particularly annoying if it were to happen every month or so. Coming from an old brick phone with something like 8000 messages on it, it'd be inconvenient to say the least to start deleting everything periodically... I guess I can use apps to back-up data when this occurs, but some apps don't even work after it's been erroring out on me. *Pulls hair out*
TL;DR:
Reset my phone while it was booting (still on the GT-I9000 screen) on a low (1%) battery and it broke my phone settings. Forced closes unknown app/service on boot with no 3rd party apps installed, but still boots to home. Force closes 3rd party apps frequently if they're installed. Factory Reset/Wipe. Problem Solved. Annoyed. RAGE.
next time something like this happens use adb logcat to figure out what is actually going wrong
exclamationmark said:
...
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) ...
Click to expand...
Click to collapse
you are not alone . after draining battery , starting it accidently up (drained) in middle of booting , killed it for me, well not killed but wouldnt boot for me and I had to the the factory reset. oh and since the nice bzz ... bzz bzz bzz I hear more often I would like to ( here was I ignored crying about it http://forum.xda-developers.com/showthread.php?t=937938 )
Yeah I'll definitely boot up logcat if it happens again. I'm just hoping this isn't a regular occurrence . As long as I don't do anything stupid like this again, I'm thinking it should be fine.
The third time this happens, it's going back to the service center, so it's got two chances left! Another thing I failed to mention was that it was chewing up like 200mb~ ram with level 1+2 ram cleared, without loading back into the homescreen, before the factory reset. Probably the stupid forced close app/service leaking >.>
Pagot, if that were me and continual factory resets were the only way to fix it (or didn't fix it) I'd flash it back to stock (or just remove root) and return it to the service center if that's an option. Sounds like something got corrupted or didn't get flashed properly. Either way I'd let THEM waste their time sorting it out because no amount of flashing is going to solve a hardware issue if it turns out to be one.
exclamationmark:
(had stock, so just root removing) but I know how our service centers work (and I would have to bring it even to our carrier) they wouldnt even talk to me if I didnt do the factory reset and the first thing they would do "reflash and factory reset"
right now I am not playing on the phone so much anymore. no lust or time so no idae if my apps are still fcing so often . And I installed speedmod and made a backup so I can revert back if something happens. So will see.
Wanted to just write about the battery down +(or) not full boot = corruption
Hello All,
I received the Lollipop OTA about a week ago and since then my phone has been randomly restarting on its own and then proceeding to perform some sort of process once it starts.
It says something along the lines of "Optimizing Apps 1of 119" and this process takes a while. I have tried clearing the cache but it doesn't seem to help.
Any ideas of whats happening, solutions ?
Thanks,
Pete
I can confirm the problem. Having the same issue where apps are optimized on every power on.
When my nexus 7 updated to 5.0 it did this a few times. Then mysteriously stopped doing it after a week or two.
Whenever Android boots and starts with "Optimizing App # of #" it usually means your ART cache got wiped for whatever reason (corrupted maybe). This is the same effect as if you wiped the caches in TWRP. It takes a long time because ART caches are substantially larger than Dalvik caches.
Try to plug the cable off before turning on the phone. Looks like a serious bug but that helped in my case.
I performed a factory reset last night seems to be much better so far, I will report if the issue starts up again !!
Pete
Which lollipop update did u do, i mean the brazil retail one or the europe one??
Cos i faced this issue a lot in brazil retail update, yet to try europe update....
had the GB OTA update and can attest to the annoying android updating with each phone restart, fortunately I have not had any random rebooting issues as reported by others
Jim
jfran said:
had the GB OTA update and can attest to the annoying android updating with each phone restart, fortunately I have not had any random rebooting issues as reported by others
Jim
Click to expand...
Click to collapse
But you do have annoying apps update at each restart right??
Yes i have the annoying android updating with each restart
I have experienced these random reboots and I have also noticed that I get an error when taking screenshots where it says that either the storage is full or the app doesn't allow it. I have at least 3gb left and I have tried it across the system and it doesn't work. I am on the retail US version for XT1053
Sent from my SHIELD Tablet using Tapatalk
I have also some optimising situations on the restarts. Someone know what can fix or raise this situation?
Sent from my XT1052 using XDA Free mobile app
the android updating stopped, not sure if it was clearing the gallery data (2GB) the helped, or booting it safe mode, anyway boot time is now back to normal
Mine only gets into the process of optimizing apps when it's connected to the power source (PC via usb or directly to the power outlet). I just have to remember to unplug before switching off the phone.
It doesn't restart on its own.
Apart from missing lots of features after the Lollipop update, I also have the optimizing problem, it takes 30min and is extremely annoying, happened 5 times already, one time was a random reboot.
Any idea how to fix it? I do not consider a factory reset a solution. Motorola has spend much time and effort in upgrading while keeping all existing settings and app configs and app data. If I knew I would need a reset I would not have "upgraded" (def would have stayed with 4.4.4 had I known some pratical features are missing, the change log and all tech sites are waay to optimistic about the Lollipop updates!).
same here.
unrooted stock Rogers/Fido version
pasta1234 said:
I performed a factory reset last night seems to be much better so far, I will report if the issue starts up again !!
Pete
Click to expand...
Click to collapse
My sister in law had the same experience.. After the 5.1 update on her XT1053 Dev Edition, she kept getting the "optimizing app xx of yy" on reboot... After a factory reset, and setting up from scratch, she is back to working fine.
Friend of mine had the same experience with his XT1053... factory reset and setup from scratch fixed it.
I received the OTA two weeks ago (retail.en.gb), after some days i had a reboot and the optimization of 130apps
So i decided to do a factory reset and install just few application.
Tonight i forgot to put the phone on charge and this morning i had again reboot and optimizaion, just 80 apps bat took 10minutes!
I hope someone found a fix for this annoing issue
worst phone ever, it is very frustrating,should i upgrade to android M ?
Try encrypting then factory reset.
Hi,
I've owned my VERIZON Samsung Galaxy Note 5 since early December and have not rooted the device. Today while taking notes in lecture, the device began displaying notices for crashed background apps (Gmail has crashed, Nova launcher has crashed, etc.) The problem persisted for another hour, even after booting into safe mode. I wiped the cache and factory reset the device, however during setup, Samsung keyboard would crash along with other apps running in the background during setup (One time I got "Samsung Galaxy has stopped working"). The phone started increasingly randomly rebooting since the phone first began to malfunction.
Since the factory reset didn't seem to actually reflash the firmware, I downloaded OJ3 stock ROM and flashed successfully using Odin, however the phone began acting even more erratically and failed to boot 4 out of every 5 boot loops. I tried flashing OGJ, which failed to boot worse than OJ3. I just flashed OJ2, which seems to be more stable than the other flashes I tried, however I'm still getting sluggish performance, random reboots and crashes of background apps immediately after booting.
At this point I believe it is defective hardware and I should call in the warranty for a new phone.
Has anyone experienced similar issues? Any speculation on the source of the issue? What should I know going into attempting to exchange for a new phone?
Note 5 crash
Yep, have the same problem, but I have not attempted to Flash the Phone yet...
Did multiple factory resets, clear caches... but to no avail. There is no structure or pattern in crash rate. Although it is getting more often day by day...
Found no working sollution, but it feels like there is a bad memory segment or something. Everytime it randomly uses that segment... crash!
Really don't know. Will try to get warrenty fix.
Let me know if you found a sollution on your side?
Cheers,
Wim
kbiscu1t said:
Hi,
I've owned my VERIZON Samsung Galaxy Note 5 since early December and have not rooted the device. Today while taking notes in lecture, the device began displaying notices for crashed background apps (Gmail has crashed, Nova launcher has crashed, etc.) The problem persisted for another hour, even after booting into safe mode. I wiped the cache and factory reset the device, however during setup, Samsung keyboard would crash along with other apps running in the background during setup (One time I got "Samsung Galaxy has stopped working"). The phone started increasingly randomly rebooting since the phone first began to malfunction.
Since the factory reset didn't seem to actually reflash the firmware, I downloaded OJ3 stock ROM and flashed successfully using Odin, however the phone began acting even more erratically and failed to boot 4 out of every 5 boot loops. I tried flashing OGJ, which failed to boot worse than OJ3. I just flashed OJ2, which seems to be more stable than the other flashes I tried, however I'm still getting sluggish performance, random reboots and crashes of background apps immediately after booting.
At this point I believe it is defective hardware and I should call in the warranty for a new phone.
Has anyone experienced similar issues? Any speculation on the source of the issue? What should I know going into attempting to exchange for a new phone?
Click to expand...
Click to collapse
OP here. Made a warranty claim, they seem to have replaced the motherboard as the solution. Complete repair experience from warranty claim to package back at my doorstep was less than two weeks, which is impressive for what I've heard about Samsung's support. Good luck!