Random Reboot in 2.3.3, not in a call. - Nexus S General

I have a non-rooted stock NS on 2.3.3 and the phone was just sitting on my desk doing nothing when I felt it vibrate. I picked it up to check for a text or email, but the phone was instead rebooting.
Has this happened to anyone else on this build? I have had the phone reboot while in call before, but never just sitting there in standby.

This happens to me in 2.3.2. I will have the phone just sitting there and it will randomly just be rebooting. Its not frequently enough to bother me yet but it happens on and off.
Sent from my Nexus S using XDA Premium App

same here on 2.3.2.... thats why I wanted 2.3.3. Ill wait patiently for the nightlies to include it.

happened to me many many times on 2.3.2, but not 2.3.3. knock on wood

Happened to me...2 times already...never on 2.3.2...im rooted though
Sent from my Nexus S using XDA App

This happened to me like 2x a day with 2.3.2.
Hasnt happened once yet with 2.3.3.

I never got reboots in-call, though I did get them a couple times when I overloaded the phone's RAM.

Mine just rebooted in 2.3.3. I'm also getting "Can't connect to camera" anytime I use the Amazon barcode app which worked perfectly in 2.3.2.

Haven't tried the new update yet
Sent from my Nexus S using XDA App

I never had the in call rebooting, just overloading reboots on my nexus s. I have yet to have one since the update, but it has only been a little over 24 hours. Then again this has been happening to me since updating my nexus one be it stock, rooted, or CM6 FRF91 and FRG83D or any form of gingerbread I've used on it. The only thing I can say it it started in froyo for me.
Sent from my Nexus S using XDA App

on the new update havent had any issues.

I had the random reboot in 2.3. 2 and thought the update had fixed it.
Unfortunately it did not - i noticed the phone rebooting yesterday.
The camera has crashed twice so far, requiring a battery pull.
I am stock, non-rooted.
I also get random failed downloads and failed market updates.
Starting to get frustrating.
Sent from my Nexus S using XDA App

MacGuy2006 said:
I had the random reboot in 2.3. 2 and thought the update had fixed it.
Unfortunately it did not - i noticed the phone rebooting yesterday.
The camera has crashed twice so far, requiring a battery pull.
I am stock, non-rooted.
I also get random failed downloads and failed market updates.
Starting to get frustrating.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
With all the problems you stated, it is obvious that ur rom is corrupt. I suggest you to back up all your settings, wipe everything and then reinstall a rom .

He's not rooted dude. Btw I get a reboot on every call. On cm nightly, no matter what I try/flash
Sent from my Nexus S using XDA Premium App

I just had reboot one time with 2.3.3 but I was running all processes 72 hours, without stopping and it suffered a lot !!!

deeren said:
With all the problems you stated, it is obvious that ur rom is corrupt. I suggest you to back up all your settings, wipe everything and then reinstall a rom .
Click to expand...
Click to collapse
Nope.
It happens to 2 Nexus S, both stock, not even rooted. One barely has additional apps, too.
I think a lot of people don't notice the reboot, because it is silent, so if you are not looking at your phone exactly at the particular time it reboots, you wouldn't know it.
The inability to dial at times is much more annoying, IMO: you punch in a number, the phone tries to dial, then hangs up. At the same time, there are 3-4 signal bars. When it happens, it normally takes several tries to get it to work.
The crashing camera also doesn't happen every time, but it is definitely a new bug in 2.3.3.

Just had my first random reboot on 2.3.3 while phone was sat on my keyboard while at my PC.
Rooted detoxed Rom stock

My 2.3.3 phone went into the weird "Dim Screen Reboot Screen" reboot at some point during the night last night. I was late for work because the alarm clock didn't go off (I know, I know...don't depend on a cell phone alarm clock)
I'm about done with this phone. And Android. Anyone wanna buy my NS? Dead serious.

fchipm said:
My 2.3.3 phone went into the weird "Dim Screen Reboot Screen" reboot at some point during the night last night. I was late for work because the alarm clock didn't go off (I know, I know...don't depend on a cell phone alarm clock)
I'm about done with this phone. And Android. Anyone wanna buy my NS? Dead serious.
Click to expand...
Click to collapse
This dim reboot screen thing used to happen quite a bit on my g2 in its early days, got it launch day. OTA fixed it.
Sent from my Nexus S using Tapatalk

fchipm said:
My 2.3.3 phone went into the weird "Dim Screen Reboot Screen" reboot at some point during the night last night. I was late for work because the alarm clock didn't go off (I know, I know...don't depend on a cell phone alarm clock)
I'm about done with this phone. And Android. Anyone wanna buy my NS? Dead serious.
Click to expand...
Click to collapse
I am still hopeful, but I am losing some patience with Android.
The platform seems to be all about selling the newest hardware, but the user experience is definitely below that of the iPhone. I keep hoping that the next Android OS upgrade will close the gap, but....
The iPhone 5 will have 4" screen, with Apple's better screen aspect ratio. If it only did Flash....
Anyway, the Nexus S is really the best user experience Android has to offer, and it's overall fine. Except when it acts like WM6.

Related

so much for the 2.3.3 reboot fix

simply said. my phone still reboots
using cm7 2.3.3 #12 and this bastard still reboots.
anyone else?
no.. wrong section
try wiping dalvik/cache/factory
No reboots over here.
Sent from my Nexus S
dudeimgeorge said:
simply said. my phone still reboots
using cm7 2.3.3 #12 and this bastard still reboots.
anyone else?
Click to expand...
Click to collapse
what kernel? And if you're going to ***** about problems with 2.3.3 you should run fully stock to make sure some customization is causing the issue.
Never once had a random reboot related to a call. Why do people tend to only pay attention to half of a bugfix and never specify whether their "problem" is related to it and then post it the completely wrong section about the problem without searching for the older threads relating to their issue?
I encountered this problem too, just 3 hours ago; the first after upgrading to 2.3.3 since Thursday.
Stock (but deodexed) 2.3.3, rooted, dalvik,cache-wiped.
EDIT: And oh, it's not a reboot bug -- it was a shutdown bug for me. Wasn't on a call, phone was just on stand by in my pocket, while my wife and I watched Voyage de la Vie. After the show, phone was dead, power button not working. I had to remove the batteries to jack it up again.
I guess I would be wiping my phone again, oh man that sucks.
But in the end, I still love my Nexus S.
kenvan19 said:
Never once had a random reboot related to a call. Why do people tend to only pay attention to half of a bugfix and never specify whether their "problem" is related to it and then post it the completely wrong section about the problem without searching for the older threads relating to their issue?
Click to expand...
Click to collapse
People don't understand. They just see "reboot bug" and anytime they get a reboot it's "that bug".
Highland3r said:
People don't understand. They just see "reboot bug" and anytime they get a reboot it's "that bug".
Click to expand...
Click to collapse
My G2 (pure stock) rebooted once in a while. In fact I watched it happen while i was in a meeting there day before I got the nexus s. It must be the same bug!
nexus s has not reboot once, though ill give it time its only been three days.
Sent from my Nexus S using Tapatalk
On CM7 build 12 with netarchy 1.2.7... it rebooted once sitting on the desk doing nothing lol. Haven't had a reboot since but it's only been a day. Battery life seems pretty good but 3D performance took a hit on 2.3.3 =\
dinan said:
On CM7 build 12 with netarchy 1.2.7... it rebooted once sitting on the desk doing nothing lol. Haven't had a reboot since but it's only been a day. Battery life seems pretty good but 3D performance took a hit on 2.3.3 =\
Click to expand...
Click to collapse
is this from benchmarks or are you seeing real world performance decrease? I am not trusting benchmarks as my g2 performed better in quadrant, yet real world the ns feels much faster.
Sent from my Nexus S using Tapatalk
Both. Benchmarks are lower and also when playing games like dungeon defenders its noticeably slower than before.
Sent from my Nexus S using XDA App
dinan said:
Both. Benchmarks are lower and also when playing games like dungeon defenders its noticeably slower than before.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That's strange, the ns has a good gpu..
Sent from my Nexus S using Tapatalk
I'm not saying it's bad, I'm saying the performance is worse than when I was on a 2.3.2 CM7 with the SAME PHONE. Not sure what comparing GPU's has to do with this.
Anyway, just had a reboot while trying to do the pattern unlock to wake my phone. It booted with a little "Safe Mode" thing at the bottom left, never seen that before. Then shortly after that it promptly rebooted itself again and it's back to normal CM7, but all my widgets mysteriously vanished from my home screen... great.
[hfm] said:
That's strange, the ns has a good gpu..
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
dinan said:
I'm not saying it's bad, I'm saying the performance is worse than when I was on a 2.3.2 CM7 with the SAME PHONE. Not sure what comparing GPU's has to do with this.
Click to expand...
Click to collapse
True, that was just my impression switching phones. I suppose it was a stability/compatability play as I hope they wouldn't unknowingly release a build with an unknown gross performance deficiency in the display driver.
Sent from my Nexus S using Tapatalk
prior to 2.3.3 my phone rebooted while in stand by on a daily basis and just once while on a call. i haven't noticed it after 2.3.3, but i'm not holding my breath just yet. i hope it's fixed.
cygnum said:
I encountered this problem too, just 3 hours ago; the first after upgrading to 2.3.3 since Thursday.
Stock (but deodexed) 2.3.3, rooted, dalvik,cache-wiped.
EDIT: And oh, it's not a reboot bug -- it was a shutdown bug for me. Wasn't on a call, phone was just on stand by in my pocket, while my wife and I watched Voyage de la Vie. After the show, phone was dead, power button not working. I had to remove the batteries to jack it up again.
I guess I would be wiping my phone again, oh man that sucks.
But in the end, I still love my Nexus S.
Click to expand...
Click to collapse
My phone is doing the exact same thing.
On 2.3.2, CM7 nightly 2.3.3, and stock 2.3.3.
Wiped or not. Rooted or not. Same damn reboot/shutoff.
It just reboot/shutoff with screen off, and hangs dead there sometimes with LED lights on. Have to remove battery to boot. Sometimes takes a dozen time battery removal to get it pass bootloader.
I am fed up. Now I am using wiped non-root 2.3.3 with a broken CMR, and still reboots!
I am going to flash the stock Recovery back and lock the bootloader before sending back to Samsung for replacement.
But seriously, what would you recommend as my next phone. I am thinking about Tbolt or Atrix.
rocketragz said:
prior to 2.3.3 my phone rebooted while in stand by on a daily basis and just once while on a call. i haven't noticed it after 2.3.3, but i'm not holding my breath just yet. i hope it's fixed.
Click to expand...
Click to collapse
It's not.
I have 2 Nexus S, both of them have spontaneously rebooted on 2.3.3.
It was much worse on 2.3.2, though.
Both are stock, not even rooted. Even most of the apps are different (my wife uses very few).
delete....
dudeimgeorge said:
simply said. my phone still reboots
using cm7 2.3.3 #12 and this bastard still reboots.
anyone else?
Click to expand...
Click to collapse
You do realize the "reboot" bug has nothing to do with just rebooting right? It has to do with rebooting while DURING a call. Also You're running CM7, so any random reboots is an issue with CM7 itself. It's still buggy as heck.
And ummm actually for me. Build 11/12 has been strong, not a single reboot. Used to have random soft-reboots, soft-reboot loops, and can't unwake the phone. All needing battery pulls. Haven't had a single random reboot with CM7 build 12.
nxt said:
You do realize the "reboot" bug has nothing to do with just rebooting right? It has to do with rebooting while DURING a call....
Click to expand...
Click to collapse
Except that it's happening to way too many of us, NOT during a call. I call that a "reboot" bug.
My phones are stock.

EVO keeps force rebooting

For some reason my EVO keeps restarting randomly on me, and all the time too.
I'm running CM7 7.0.3.1 and savaged zen 2.2.0, and I have an extended battery and I rum juicedefender.
Now I don't think its the battery because I've had it for month
Its most like savagedzen 2.2.0 but idk maybe its CM7 too.
I think this started after I started playing words with friends. Doesn't seem like a memory intense app and I never had this happen but lately its been rebooting randomly, like I'm download from the market. Internet, and even posting this thread!
Basically I'm thinking of switching to either virusrom or Mik, which is better?
Sent from my dope fly fresh EVO
my chick is having the same issue. hers just reboots at random after starting to use her pandora app about a week ago.
her evo is running:
Mod version: CyanogenMod-7.0.3.1-Supersonic
Kernel version: [email protected]#1
Ditto
I have same problem, and have tried various ROM's, most recently a complete wipe as per Mikroms instructions. Only pattern I can make out is it tends to start when the CPU is stretched a little, such as running Tango over 3G, or even Angry Birds for over ten minutes. Once it starts though, it reboots several times before it finally quits.
There was another thread on this, but no solutions, instead it turned into an argument over whether it is CM7 fault; not very constructive. I have tried different batteries and changed up CPU speeds, still to no benefit.
Like I said, if I don't tax the system I have no problems, and that so far has been my only solution, but a disappointing experience with my Evo.
My dad's kept rebooting too even after the gingerbread OTA. He is running a bone stock phone(not even rooted)
Wife is having the same issue on her stock EVO with the new OTA
same issue here, playing WWF,stupid zombies or surfing the web. on decks rom and on the gingerbread 2.3 stock.
Apparently, this is a common problem with the EVO. Mine started as soon as I accepted the recent OTA update. There is an XDA thread somewhere. Just do a Google search.
Same here & 2 of my other friends. I am on my 3 or 4 EVO (lost count) & everyone does it. This is only one I rooted as well. I noticed it does it less (once every few weeks to a month) with a custom non cm rom. Also restart your phone at least every couple of days (usually I did every day). It works out pretty well. What I tell my friends don't hesitate to tell sprint you have a issue so it gets documented. So you have proof to fall back on when you had enough. It's not like you pulling one over on them. They see if you have all these issues for so long why just now saying so. I have found that for some reason phone resets in middle of calls multiple times same day with certain Bluetooths. I drive truck for living so I on phone alot with customers/work/friends/family/etc. Always Bluetooth, and did up to 5 times a day. Then bought one top of line (jawbone icon &now Bose) and doesn't do it like that anymore. Hope this helps any of you. & again any issues you get tell sprint. Last time I got a new EVO in box, & they let me keep my old one. So gave it to my mother. Then had it replaced under her #.
Sent from my EVO using Tapatalk
Mine started out with a reboot
every so often. It finally got so bad it would reboot over and over until I pulled the battery for a few. Somewhere in the process, my GPS crapped out as well. It would work for a few minutes and then freeze. Not a good thing when you are not from Boston and trying to navigate 8am traffic to get somewhere.
I got a refurb as a replacement. It was in perfect shape and only had like 111 minutes of talk time. No telling why it was sent back but I've had no issues with it.
Mine is doing this too.. its annoying Ive restored backups and it just keeps rebooting, i dont know whats wrong. Im on avaFroyo 2.2
I don't remember where but there is a thread about this very topic. From what I read this was attributed to a corrupt data partition. My gf phone is starting to have this problem. Only fix I have read so far is to reroot phone and take it to sprint. I am waiting til they can root the ota. Then I will unroot her phone and get a new one.
Tim
Sent from my PC36100 using Tapatalk

[Q] Stock Nexus S Randomly rebooting

I've had my nexus s for almost a year and it's randomly rebooting. While in android 2.3 it rebooted once or twice a week. I thought that ICS would fix it, but it didn't, and now the phone is still rebooting, but only once or twice a month. I wasn't able to notice any thing or app that could cause the phone to reboot. Sometimes it's during a call, sometimes during a game, sometimes while i'm staring at the homescreen. I've looked at some logs and the problem seems to be the OS, because it say something like "critical android error, rebooting" before it reboots. The phone isn't rooted or any thing like that, and now it's in 4.0.3, updated OTA. Any ideas??
alexfiorani said:
I've had my nexus s for almost a year and it's randomly rebooting. While in android 2.3 it rebooted once or twice a week. I thought that ICS would fix it, but it didn't, and now the phone is still rebooting, but only once or twice a month. I wasn't able to notice any thing or app that could cause the phone to reboot. Sometimes it's during a call, sometimes during a game, sometimes while i'm staring at the homescreen. I've looked at some logs and the problem seems to be the OS, because it say something like "critical android error, rebooting" before it reboots. The phone isn't rooted or any thing like that, and now it's in 4.0.3, updated OTA. Any ideas??
Click to expand...
Click to collapse
Root and install a custom ICS rom .
Sent from my Crespo using xda premium
thegtfusion said:
Root and install a custom ICS rom .
Sent from my Crespo using xda premium
Click to expand...
Click to collapse
If its doing it on stock I doubt that will fix it. Random reboots once or twice a month doesn't seem like a huge deal really. I've had just about every high end android phone under the sun and if I only got one or two reboots a month on any of them I'd be happy.
Sent from my Nexus S 4G using Tapatalk
Once or twice a month is not bad at all...
A reboot once or twice a month isn't really bad, that's true, but I was curious to know what was causing the phone to reboot. Thanks anyway.
I'm on stock 4.0.3 (i9023), was on stock 2.3.6. Had maybe one random reboot since I bought the phone (wich was about 3 or 4 months ago) and I think it was on Gingerbread (not sure though)... Not bad since I had more of them when using custom roms on my tiny X8 I had before.
I've done a full wipe and a full update when updating to ICS.
Hey guys, I have similar problem. I bought my Nexus S second-handed half a year ago. I had 2.3.6 at that time, and it used to reboot itself like once a day. But as the time passed by, the ammount of restarts increased to 3-5 per day. When the ICS was released, I rooted and manually updated ICS (I have european i9023 version, I'm from Czech Republic), with stock ICS rom and CWM recovery 5.0.2.0. I thought it would stop, but i was wrong. Then I read it was caused by some widgets (like Beautiful Widgets, bought, not cracked). It worked for some time after unistalling, reboots decreased, but now I am on the old level with 5 restarts a day. I tried everything, even full wipe, formated USB storage, didn't help. Do you think another kernel and custom rom could help, or is it some kind of HW problem? Thanks for any advice.

[POLL] How often do you reboot?

I know, it's not Windows, but is it a good idea from time to time to reboot manually? Would we have any benefit from doing this?
Personally, I reboot only when I really have to, for making backup, or when I install anything on system level that requires rebooting. My system is solid and stable and if anything hangs, simple selective app killing solved everything so far.
I was on CM7, and Neutrino earlier and was very satisfied with both of them, but then I bought lapdock so I switched to Nottachtrix. I had no need to reboot manually with any of them. Maybe your mileage varies, and I'd like to hear your opinions.
Does shutting your phone off at night count? There's no need IMO to have a phone on 24/7. Take a break from it.
Sent from my MB860 using xda app-developers app
Over 10 times a day, hardware problems causing random shutdowns all the day xD
Well, im running Th3Bill's MIUI 2.8.17 and i have to reboot the phone at least one time in the day because for random reasons, it loses internet acces, and i have to reboot it to get everything working again. Also when the camera goes crazy and when i open the app, says that can't connect to the camera. A reboot fixes that issue.
i'm using jokers CM9 and its been stable as a stable thing tied down to a really heavy stable object.
but i do reboot it 2 or 3 times a week - usually because i forget to put it on charge overnight and the battery dies
andrew.cambridge said:
Does shutting your phone off at night count? There's no need IMO to have a phone on 24/7. Take a break from it.
Click to expand...
Click to collapse
I have it automated to go to airplane mode in 11PM and it resumes in 7AM, that's about turning it off. I have it next to my bed, and sometimes I use it as a flashlight during the night. I love this flashlight app.
Fast Crash said:
Over 10 times a day, hardware problems causing random shutdowns all the day xD
Click to expand...
Click to collapse
I should have included "Randomly. It reboots by itself." option in poll.
djluis48 said:
Well, im running Th3Bill's MIUI 2.8.17 and i have to reboot the phone at least one time in the day because for random reasons, it loses internet acces, and i have to reboot it to get everything working again. Also when the camera goes crazy and when i open the app, says that can't connect to the camera. A reboot fixes that issue.
Click to expand...
Click to collapse
I remember stuck camera problem when I tested ... some of ROMs (can't remember which ones) and it was a deal breaker. You shuold reconsider your ROM-radio-kernel choice. I had best experience with Neutrino, regarding battery life, speed and stability. With Blur based Nottachtrix I lost CM goodies (which I really miss), some speed and battery life, but I gained Webtop functionality. However, Nottachtrix has proven to be stable and reliable.
I always reboot once a day regardless of its needed or not. My wife use to never reboot her inspire and she kept having freeze ups so I told her reboot once a day now hers seams to be doing a lot better.
Sent from my SAMSUNG-SGH-I747 using xda premium
Well my touchscreen is broken so i need to pull the battery to hang up a phone call... going to replace it soon though.
andrew.cambridge said:
Does shutting your phone off at night count? There's no need IMO to have a phone on 24/7. Take a break from it.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Exactly !
Dont know why people want their phones on 24/7 you're no president of your country
plus it might help i better battery and overall life of device
I reboot every morning after full charge. Clears up the RAM.
Sent from my MB860 using xda app-developers app
Whatever happends, even if I run stock or any custom ROM, my data connection gets lost with time. Impossible to get it back without a reboot. So I reboot quite a LOT !
I reset almost every day since almost every day I'm flashing a new ROM, or returning a Nandroid. But many times, connection problems, or freezing apps, I managed to solve restart.
Basically never. =) never have any problems on thebills miui
Sent from my MB860 using Tapatalk 2
I reboot about once or twice a day but not because I want to, the dreaded random reboots have returned
Sent from my MB860 using xda app-developers app
I reboot mainly when I f**k up an system file (last one was when I froze the blur launcher... it kept showing FC one after another..... adios battery! Hello bootscreen!
maajstor said:
I know, it's not Windows, but is it a good idea from time to time to reboot manually? Would we have any benefit from doing this?
Personally, I reboot only when I really have to, for making backup, or when I install anything on system level that requires rebooting. My system is solid and stable and if anything hangs, simple selective app killing solved everything so far.
I was on CM7, and Neutrino earlier and was very satisfied with both of them, but then I bought lapdock so I switched to Nottachtrix. I had no need to reboot manually with any of them. Maybe your mileage varies, and I'd like to hear your opinions.
Click to expand...
Click to collapse
once a day
My intention is not to reboot ever .. but being on a beta ROM has its side-effects ..
Sent from my MB860 using xda app-developers app
andrew.cambridge said:
Does shutting your phone off at night count? There's no need IMO to have a phone on 24/7. Take a break from it.
Click to expand...
Click to collapse
I stopped thinking this way after 9/11. On 9/10, I went out drinking with friends and went to bed without shutting off my phone like I normally did. That morning my roommate and I were woken up by a call from a friend purely because of my mistake. Since then, I treat my phone like a landline.
Every Tuesday before I check for ICS update.
Sent from my MB860 on CM10
everyday about 6~7 times.
yea it's not a windows but
reboot is not bad way to manage devices
Sent from my MB860 using xda app-developers app

[S4 Active]- So my phone started freezing up on me yesterday...

My experience with my S4A has been amazingly flawless up until yesterday, when it started experiencing one of the issues that killed my experience with the HTC One- random freezes. And what's strange about it is that they are the same type of freezes that my One experienced, only when browsing the web or using an internet based app like Pulse. It has happened 3 times since yesterday and is so bad that I've had to pull the battery to even get it to reboot. Which brings me to one of my suspicions...
The only thing that has changed between me getting the phone set up originally and when the freezes began was the fact that I started swapping batteries instead of charging the phone. Now, phone batteries nowadays are not just like your average AA cell, it has circuitry in it and NFC stuff... is it possible that a defective battery could be the culprit of my woes? I just put in my original battery and am gonna just wait and see if it happens. The other battery that I've been using is a Samsung OEM battery and not a cheap one. I did root and freeze a bunch of stuff, but nothing exotic, and it was fine until yesterday. I doubt anything I did caused this.
Has anyone else experienced any freezes like this? Help me solve this, I really want to keep this phone (at least until the next latest and greatest comes out). TIA
_MetalHead_ said:
My experience with my S4A has been amazingly flawless up until yesterday, when it started experiencing one of the issues that killed my experience with the HTC One- random freezes. And what's strange about it is that they are the same type of freezes that my One experienced, only when browsing the web or using an internet based app like Pulse. It has happened 3 times since yesterday and is so bad that I've had to pull the battery to even get it to reboot. Which brings me to one of my suspicions...
The only thing that has changed between me getting the phone set up originally and when the freezes began was the fact that I started swapping batteries instead of charging the phone. Now, phone batteries nowadays are not just like your average AA cell, it has circuitry in it and NFC stuff... is it possible that a defective battery could be the culprit of my woes? I just put in my original battery and am gonna just wait and see if it happens. The other battery that I've been using is a Samsung OEM battery and not a cheap one. I did root and freeze a bunch of stuff, but nothing exotic, and it was fine until yesterday. I doubt anything I did caused this.
Has anyone else experienced any freezes like this? Help me solve this, I really want to keep this phone (at least until the next latest and greatest comes out). TIA
Click to expand...
Click to collapse
Mine started Sunday. All it would do is hang at the ATT logo on reboot. I ended up doing a factory reset and it hasn't happened since. Certainly made me suspect the rooting I did...
kbmapper said:
Mine started Sunday. All it would do is hang at the ATT logo on reboot. I ended up doing a factory reset and it hasn't happened since. Certainly made me suspect the rooting I did...
Click to expand...
Click to collapse
What did you do to your phone after rooting?
A couple of times now my active has become unresponsive. The power button doesn't seem to work and the home key doesn't do anything. The led is flashing blue and the battery is still about 35%. The only thing I can do is pull the battery.
Not sure if this is related to your question but I'm going to try to get it replaced...
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Didn't really do anything drastic- Titanium Backup and froze some att crap. Nothing even remotely close to system apps.
dinglayne said:
A couple of times now my active has become unresponsive. The power button doesn't seem to work and the home key doesn't do anything. The led is flashing blue and the battery is still about 35%. The only thing I can do is pull the battery.
Not sure if this is related to your question but I'm going to try to get it replaced...
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Click to expand...
Click to collapse
My LED never starts flashing but like yours, none of the buttons respond and I have to do a battery pull. I really don't want to have to get it replaced, and I really don't want to wipe and start over, just don't have the time right now to do either. Did you do anything to yours? Root?
kbmapper said:
Didn't really do anything drastic- Titanium Backup and froze some att crap. Nothing even remotely close to system apps.
Click to expand...
Click to collapse
Same here. Nothing I froze should have any affect on system stability.
I Haven't had any issues since I've had the phone, going on 3 weeks. I've been rooted and have froze apps in TB with no problems since geohot gave us root. Also have done some other root mods, and have not experienced any issues.
Sounds like just some bad hardware circulating.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
I've modded mine a good amount and haven't had any lock ups. I have just about every root app out there. Xposed with nottach, dark phone and contact apk, and cm10.1 messaging app. Froze a lot of bloat too
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4 Beta
Man I REALLY hope it's not a hardware issue. I'm so tired of doing the repeated exchange thing. I went through 5 One X's before I found a suitable one, saw that pattern emerging with the One (had 2, both with same issues) and was really hoping the S4A was going to be the answer to my woes. I really love this phone but if it ends up being a hardware thing, I will be incredibly disheartened.
Sent from my SAMSUNG-SGH-I537 using xda premium
Any way to tell the build dates of our phones? Maybe we could narrow it down to a certain production date.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
echonc said:
Any way to tell the build dates of our phones? Maybe we could narrow it down to a certain production date.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Click to expand...
Click to collapse
I dunno... My box is in another state so I won't be able to check it for a few weeks. I bought it on the very first day it was available if that helps any. On a side note, I put my original battery in last night and it hasn't locked up on me since. We'll see what happens by the end of the day.
Sent from my SAMSUNG-SGH-I537 using xda premium
I am rooted but that's pretty much it.
The only thing I know I was doing at the time was watching a YouTube video then pressed pause.
Next thing you know I picked it up hit the power... Nothing. Hit menu... Nothing. The blue LED was just the normal notification indicator, so I knew it hadn't powered off... Resulted in a battery pull.
I also know that I didn't get any messages or new notifications while the screen was off.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
I ALWAYS have issues restoring from titanium backup, esp going from one phone to another. My suggestion is to factory reset and start with a clean slate, cas only then can u verify a hardware issue.
_MetalHead_ said:
I dunno... My box is in another state so I won't be able to check it for a few weeks. I bought it on the very first day it was available if that helps any. On a side note, I put my original battery in last night and it hasn't locked up on me since. We'll see what happens by the end of the day.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
I know on the Captivate the Build Number could be found under the battery (can be found there on the S4A as well) and it was the year/month that the phone was built, or so they say. My S4A Build number is 1306 so I'm guessing it was built the beginning of June...
_MetalHead_ said:
I dunno... My box is in another state so I won't be able to check it for a few weeks. I bought it on the very first day it was available if that helps any. On a side note, I put my original battery in last night and it hasn't locked up on me since. We'll see what happens by the end of the day.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
I would like to know if you have had any more problems since you put your original battery back in? If you could give a update I would really appreciate it. I really think the active is a great phone and I truly like it but if people are having a lot of issues with it, I'll just return it and get something else to save myself a headache down the road. I have a week left on my return date so that's why I was wanting to know.
Sent from my SAMSUNG-SGH-I537 using xda premium
gf has had similar issues; heres what fixed it.
battery pull
factory reset/restore
reboot
battery pull
reboot
root/etc/restore from there. check to make sure you dont have custom CPU voltage/speed mods enabled; i believe this was the initial culprit, though even after resetting them to stock it would still lock up. it only did it 3 times, and usually right after a new mod, but ONLY if CPU values were changed. after the above procedure, she redid all her cpu values but only AFTER all mods were installed, rebooted, and everything works great again.
tmease1 said:
I would like to know if you have had any more problems since you put your original battery back in? If you could give a update I would really appreciate it. I really think the active is a great phone and I truly like it but if people are having a lot of issues with it, I'll just return it and get something else to save myself a headache down the road. I have a week left on my return date so that's why I was wanting to know.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
The only "issue" I've had with mine is that it's too bright when the brightness is set to max
tmease1 said:
I would like to know if you have had any more problems since you put your original battery back in? If you could give a update I would really appreciate it. I really think the active is a great phone and I truly like it but if people are having a lot of issues with it, I'll just return it and get something else to save myself a headache down the road. I have a week left on my return date so that's why I was wanting to know.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
Same problems no matter which battery. It seems to happen most when I'm using Chrome so I deleted the updates but it's still doing it. It happened while playing a game today which it's never done before. Next step is to freeze Chrome and see if that helps. If not, then I'm gonna factory reset and if that doesn't work, I'm gonna have to exchange it. I really did not want to have to deal with this. With my ridiculous work schedule I don't have the time or the energy. I might just start looking for a different phone because I'm sick of having issues like this.
Sent from my SAMSUNG-SGH-I537 using xda premium
_MetalHead_ said:
Same problems no matter which battery. It seems to happen most when I'm using Chrome so I deleted the updates but it's still doing it. It happened while playing a game today which it's never done before. Next step is to freeze Chrome and see if that helps. If not, then I'm gonna factory reset and if that doesn't work, I'm gonna have to exchange it. I really did not want to have to deal with this. With my ridiculous work schedule I don't have the time or the energy. I might just start looking for a different phone because I'm sick of having issues like this.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
I would say if the factory reset does not work than it is the phone itself. I had issues like this in the past with my old infuse and I did a factory reset and it took care of it. Hopefully that will help you out so you can keep your phone. Thanks for replying.
Sent from my SAMSUNG-SGH-I537 using xda premium
tmease1 said:
I would say if the factory reset does not work than it is the phone itself. I had issues like this in the past with my old infuse and I did a factory reset and it took care of it. Hopefully that will help you out so you can keep your phone. Thanks for replying.
Sent from my SAMSUNG-SGH-I537 using xda premium
Click to expand...
Click to collapse
Yeah bud, I really hope a reset works. I might do it tomorrow, I should have enough time. I'm just frustrated that I'm having identical issues with the S4A that I had on my One. I was really hoping to find a phone that just works. I don't think I've had a problem free phone since my Epic 4G Touch. My One X had issues (though my 5th one was near perfect), my iPhone 5 was horrible, both my Ones had problems, and now this. I'm just venting now but I'm seriously tired of it. I've got my eye on that new Sony i1 that's coming out in a couple months, I really love their current design choices and I've never tried a Sony before. Or maybe the next Nexus. Who knows. I just don't want to deal with this crap anymore.
/rant
Sent from my SAMSUNG-SGH-I537 using xda premium

Categories

Resources