Got my official OTA update this morning and it's been nothing but problems since.
First, the phone wouldn't boot. Got the 'droid' sound effect, and phone froze on the eye. Fixed itself after a battery pull.
Now, contacts won't load, one of my email accounts won't sync, phone is not as smooth or stable, keep getting FCs (Sense FC, 'Process System is not responding') from which the phone won't recover.
Never got around to rooting, so it was stock rom -> OTA.
Anyone else? Ideas?
jaangunnar said:
Got my official OTA update this morning and it's been nothing but problems since.
First, the phone wouldn't boot. Got the 'droid' sound effect, and phone froze on the eye. Fixed itself after a battery pull.
Now, contacts won't load, one of my email accounts won't sync, phone is not as smooth or stable, keep getting FCs (Sense FC, 'Process System is not responding') from which the phone won't recover.
Never got around to rooting, so it was stock rom -> OTA.
Anyone else? Ideas?
Click to expand...
Click to collapse
Your phone wasnt frozen, it was loading. After a OTA update or new rom install, then your phone will take longer to boot and appear its stuck. You made a mistake by doing a battery pull and might of messed up something. I would only pull the battery if it was stuck for like 15 minutes+
I would take your phone to VZW and get a replacement.
I did wait for half an hour before the initial battery pull.
But you're probably right, shouldn't have pulled.
Did a factory reset and everything is smooth now. Annoying to have to get all my apps back, but so it goes.
Related
Well, I say it did. In my patient, impatience, I rooted my Vibrant two days ago (then later that day T-Mo announced they would roll out the OTA Update).
I rooted with RyanZA's One Click from the Market and applied the lagfix (V2.1+). This morning, when I woke up, I had the OTA Update waiting for me. So I uninstalled the OneClickLagFix, uninstalled EXT2 Tools and left the phone rooted. I took the OTA Update and everything was FINE for most of the day. I did a couple of reboots, played with some things, and went about my day.
Earlier this evening I was getting some directions via Google Navigation when it took me back to the "old days". The phone froze, gave me a black screen, and hung out like a worthless welfare recipient looking for a free 40. I did a battery pull, the phone rebooted, the OS loaded, swiped in my pattern and it froze, no black screen, but froze. After about 5 minutes, and yanked the battery, rinse, repeat, same result.
After that, it would hit the Galaxy S Splash screen and then go dark. I waited as long as 25 minutes in one instance. After literally 10 attempts, I booted into the recovery console and wiped everything. The phone came back and all was well. I reinstalled apps (still had root) and went about my way.
At some point, randomly, before reinstalling the lagfix, Haptic Feedback went dead. Well, scratch that, the entire vibrate function went dead. No Vib, anywhere. So where do I go from here? I'm thinking it has to be a software glitch. Frankly, I don't want to wipe the thing again. I referenced a thread here entitled "Is your samsung vibrant not vibrating when it should??" (I'm to new to post a link here), but none of those options worked.
Has anyone else experienced this problem yet?
Do I have any other options?
Thanks for the input!
I've got same problem
Well I see a lot of people are having problems with the update... I'm not sure if I should install it when it pops up on my phone....
Sent from my SGH-T959 using XDA App
the lagfix 2.1 causes all vibration to die in the latests updates, JI5 and 6 it's a known issue use version 1+ if you want lagfix with vibration
yeah its the 2.1 lagfix. The 1.0 version work fine.
Yes, I just installed the lagfix and my vibration went away... What's the difference between version 2.1 and 1.0?
I updated my phone manually through Mini Kies.
Before the update with or without OCLF applied, the phone would never freeze. Since I've applied the update the day before yesterday, the phone has locked up three times. Basically what happens is, the screen will, well, freeze, and my button presses do absolutely nothing, I hit the back button- phone vibrates, does nothing, same with home button. To power it off I either hold the power button for 5-10 seconds, I have not yet had to pull the battery. HOWEVER. This last time it froze, I powered down the device but the phone would not turn back on. I pulled the battery from the phone and inserted it back in and after doing so my phone powered back on with no problem. It's a bit concerning though. Probably the worst thing about all of this is the fact that my phone runs great! Fast and responsive, GPS seems to be spot on. Except about once a day since the update, it freezes.
Any ideas? I have no experience with modding/flashing anything so I get really nervous with things like installing custom roms. I was thinking I could roll back the update and then re-do the update. I doubt I'd get the update OTA though, I updated my girls device OTA and she has had no problems so far.
I was even considering flashing Bionix, but again, very nervous to do so. I even had trouble just creating a nandroid backup! I couldn't get into clockwork recovery to do so.
Can anyone just baby me with this? Tell me where to start?
Thanks :/
I would suggest you flash back to stock firmware using Odin.
Go into the Development section and look at the directory sticky. There is a link in there for a thread on how to go back to stock firmware.
Once you flashed back to stock, i suggest using it on stock for a day or two to make sure the phone work correctly. Once you verified the phone working then try to update to JI6 again via Kies mini.
Other than that you can start to mess around with flashing different custom firmware and mods. It hard to brick the phone since you can always go into download mode and odin back to stock.
Be adventurous! Good luck!
would you suggest that I go back to stock before trying to flash bionix?
Wearespacepeople said:
would you suggest that I go back to stock before trying to flash bionix?
Click to expand...
Click to collapse
You should go to JFD then to JI6. Freezing isn't normal, I don't have any freezing. If it was randomly freezing there would have been a 10 page thread on it already.
I've also had it freeze twice on me. Went from rooted Stock to JI6 using Odin. /shrug
Same issue after applying JI6 OTA. I unrooted before applying the OTA, but have now reapplied OCLF with stock.
Same issue. Frozen hard twice. Browser exits randomly. Battery drains about twice as fast as before JI6.
I went from fresh Stock to JI6 via Odin. I don't know if I can wait for Froyo. I may just go back to stock again, even with the broken GPS.
I bet the OP has a bunch of apps installed.
A lot of people are blaming the update, but I'm almost sure there are many rogue apps in the marketplace, because last night I was getting freezes and after I uninstalled all the apps I don't actually need (or use very frequently) all of the freezing just stopped. The phone runs smoothly now. And removing those apps + removing the Task Manager widget from one of my screens increased my battery life by ~200%.
I installed BioNix 1.9.1 (with JI6) and I'm still getting occasional freezes, but I'm wondering if they are due to Angry Birds which I installed at the same time as my original JI6 OTA update. I'm seeing some reports (forum.androidcentral.com/motorola-droid/38906-freezes-weird-stuff-angry-birds.html) , but I have no idea if this is a valid idea.
Anyone else seeing freezes with JI6, but not angry birds?
I've also been having freezing problems, and I think they're GPS related.
The last time was last Friday. I was driving down to Washington DC using my phone for turn-by-turn navigation, and it froze about 1/3 of the way there. I had to pull the battery out to restart. When I got to my destination, I was using Maps and then the browser, and while the GPS icon was on the notification bar, telling me it was trying to find my position, my phone froze again. Again, I had to pull the battery out. Both happened within around a 1.5-2 hour period. I realized it may be due to the GPS, so I turned off GPS right away. It's now Monday afternoon and my phone hasn't frozen since.
My G2 is rebooting itself every 5 seconds.. it won't load or get past the G2 screen...
i tried holding the power down but thats not doing anything.. I guess I'll just pull the battery.
this is the first time this has happened. usually it randomly reboots, but it loads but this one has been rebooting for 10 minutes now.
will my rebooted while I was in the gmail app.
it won't finish boot so I pulled the battery.
it did restart this time but my phone lost all it's apps and settings!
it reverted back to stock but I've not rooted or modded my phone in any way.
argh, going back to my old phone...
never had an android phone reboot so much and now forgetful.
N4Spd said:
will my rebooted while I was in the gmail app.
it won't finish boot so I pulled the battery.
it did restart this time but my phone lost all it's apps and settings!
it reverted back to stock but I've not rooted or modded my phone in any way.
argh, going back to my old phone...
never had an android phone reboot so much and now forgetful.
Click to expand...
Click to collapse
It seems you have a defective unit.
I'm not exactly sure what happened, but when I first rooted, installed safestrap, and then Jelly Beans 106 on my Note 3, my phone would start up fine but then restart constantly. I would get my home screen, then immediately get notifications that various apps had crashed, and then the phone would reboot, but not fully though, it wouldn't go directly to the Jelly Beans boot animation, not through the full boot from the beginning with the samsung logo. From start up to reboot varies, but usually whatever app i was using would crash within a minute, and my phone would crash/lockup/reboot maybe 30 seconds to a minute later. It did not matter what app i as using or what I was doing. Actually I just noticed it somehow lost all my email settings, none of the accounts are there anymore.
If I booted into the stock rom from safe strap it seemed stable, but never with Jelly Bean. I had tried clearing the caches, wiping the phone, and a bunch of other fixes and nothing worked. In a last ditch effort I tried the process again, from the very beginning, I retooted my phone, reinstalled everything, and it worked, until three days ago when it started rebooting again. I had about three months of my phone being perfect, and then it just started rebooting randomly on it's own. The only thing that I can think that I did was decline some usage rights for the my magazine samsung app, that was the last thing I did before my phone went crazy.
I can't even get the stock rom to be stable anymore, it will do the same thing, whats' going on? I don't get why my phone was so stable, and then it went all haywire again. anybody have any idea of what I can do?
Hey, I had been stuck with the issues as mentioned shortly after I upgraded to Nougat via ODIN (SM-G935F/probably Netherlands, Unlocked, no root, no mods). The phone would work fine and then suddenly start overheating and resultant bootloops and black screens when in certain standard apps like Google photos and Facebook. This would happen with no fixed pattern, sometimes everyday, sometimes once a month). I did cache clears and full resets but the problem would reappear. Phone stopped getting OTAs as well, although it got a few in the beginning. Security patches. Recovery typically showed updating and didn't progress.
Finally I decided to flash another latest stock ROM via ODIN. Now a few days have gone by without a sign of the previous troubles (God, I hope it stays like this).
My question after this long story, is this possibly a hardware problem, in which case I'll sell it off before it reappears. Or could it just be a software glitch solved by the new ROM, in which case I'd like to keep the phone. Which is more likely, I really want to keep the phone as the S8 upgrade is not worth the money for me, in my opinion.
waqar747 said:
Hey, I had been stuck with the issues as mentioned shortly after I upgraded to Nougat via ODIN (SM-G935F/probably Netherlands, Unlocked, no root, no mods). The phone would work fine and then suddenly start overheating and resultant bootloops and black screens when in certain standard apps like Google photos and Facebook. This would happen with no fixed pattern, sometimes everyday, sometimes once a month). I did cache clears and full resets but the problem would reappear. Phone stopped getting OTAs as well, although it got a few in the beginning. Security patches. Recovery typically showed updating and didn't progress.
Finally I decided to flash another latest stock ROM via ODIN. Now a few days have gone by without a sign of the previous troubles (God, I hope it stays like this).
My question after this long story, is this possibly a hardware problem, in which case I'll sell it off before it reappears. Or could it just be a software glitch solved by the new ROM, in which case I'd like to keep the phone. Which is more likely, I really want to keep the phone as the S8 upgrade is not worth the money for me, in my opinion.
Click to expand...
Click to collapse
Sounds like a bad flash. The new flash removed the issues, so you're good to go.
Guess what guys, the problem returned after about 3-4 weeks. Appeared randomly while using FB. Phone went into bootloop and overheating again, and even when it restarted properly, it would go into the same cycle when I started using apps like messaging, whatsapp and facebook.
I booted in recovery and cleared the cache after about 25 reboots. One thing I noted was that recovery initially showed an update running, which got stuck first, and then completed after another reboot and entering into recovery. Has been stable for the past 24 hours now, like it never happened. I can't figure out what the issue could be, since now I can do whatever I want and it won't overheat like before or reboot.
Feels like a software issue since it disappears like it was never there. Hardware rarely does that. Is there a possibility that storage of some sort is bad at some point, and when data is written over that point, the problem appears. I'm shooting in the dark but can't figure it out otherwise.
Yup.
Seems you have memory issues.
Go to Samsung service and replace memory chip.