Related
My phone keeps on randomly rebooting. Is anyone having the same problem?
Sent from my T-Mobile G2 using XDA App
I am experiencing this problem too.
It rebooted once when I was using the Camera (Youtube HD Video mode)
Once When Trying to open Gallery.
And once while just sitting here on my desk at work.
I want to love this phone so bad! I really like it so far though, and the keyboard issue is def. not a problem for me, and I think it's probably a design flaw rather than a manufacturing "defect" considering there are no springs. It is very hard to recreate the hinge problem while holding it naturally, including at a 45 degree angle in bed.
I also have had a few reboots and also media server force closes while running other apps. Never had these issues with my N1. Luckily I still have it. I'll give it a few more days and probably end up returning this G2 and going back to the N1.
Sent from my T-Mobile G2 using XDA App
I have been waiting for a good QWERTY phone with a fast CPU and a WVGA, passed on the nexus one and kept my G1. After running CM6 on my G1 (usable but sloooow) there is no going back for me after using the G2.
I sure hope this is something fixable in a firmware update
Does it reboot all the way to the white htc screen or the grey tmo g2 screen? Mine does it to the tmo screen and seems to only happen when the phone has been sitting for awhile and I pass through an area with no reception and when I hit reception again is when it happens. Almost like its turning itself off but stays on enough to look for signal and then turns back on. I only say this because on my drive I know the spots where I lose service and the phone does the reboot in those spots. Anyone else?
Sent from my T-Mobile G2 using XDA App
Yea I had this happen today when roaming in nw ohio I think it may have started after taking pics of my niece. I also have a problem with the memory card it says it mounted read only and none of my pics or anything show up in the gallery.
The incredible used to randomly reboot. I believe that was due to when there was low signal. It was fixed with an ota.
Sent from my Incredible using XDA App
brentcizek said:
Does it reboot all the way to the white htc screen or the grey tmo g2 screen?
Click to expand...
Click to collapse
It goes to the G2 logo screen.
I have also had two occurrences of it being stuck at that screen and the power button not responding to long press or anything, only solution was to remove battery.
Lcsglvr said:
The incredible used to randomly reboot. I believe that was due to when there was low signal. It was fixed with an ota.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
That would make a lot of sense, I'm at work right now and my signal is very weak here, goes in and out all the time.
What about others who are experiencing this problem?
Also, I am using a Class 6 A-Data 8gb microsd partitioned for ext3/swap/fat (not the included card), and so far each time it has rebooted the USB cable was plugged into a PC (for charging only, no debug or mass storage)
I wonder if any of this matches up with others who are having issues?
Mines always happened not plugged in and has never gotten stuck.
Sent from my T-Mobile G2 using XDA App
g2 reboot and mulitple force closes
i am getting the reboot issue also, it seems to be random when i am opening an app or going in to basically anything. also i am getting multiple force closes in basically all apps. i did a master reset and going to reload all apps and such and see if that fixes anything.
Could be something you have installed too I remember some people having this problem when nexus first came out and they built a list and narrowed it down
Sent from my T-Mobile G2 using XDA App
There's a thread on Tmo forums about this issue, the guy fixed it by transferring his number to the new sim card that came with the phone. If you haven't tried it, give it a try.
I updated my sim and haven't had any reboots yet
Sent from my T-Mobile G2 using XDA App
For what its worth, my N1 reboots occasionally, randomly when I may be doing something. Happening ever since I got it. Maybe sone kind of exception happening in Android?
Sent from my Nexus One using XDA App
I have transferred my sim also and am still having this problem. It was after going through a no signal zone, which sucks because I am in hotels and places where I have no signal all the time.
Victor
gjvah said:
There's a thread on Tmo forums about this issue, the guy fixed it by transferring his number to the new sim card that came with the phone. If you haven't tried it, give it a try.
Click to expand...
Click to collapse
Thanks for this tidbit. I called Tech Support and had my phone number moved to the SIM that came with the phone. Probably a long-shot, but what the hell...
Well, after 2 hours on a fresh charge, I sat my phone down for 15 minutes. When I picked it up it was dead (black screen). Had to pull the battery.
Seemed to be a weird fluke. Did have another reboot, though it felt Android related versus hardware.
-oldsk00lz
So it rebooted on me this morning in a spot with perfect reception. I was trying to open the xda app but it wasn't opening...almost like I didn't have any data. Fishy fishy..
Sent from my T-Mobile G2 using XDA App
Mine actually rebooted twice on me, both at random times.
1st occurence - I was listening to pandora, skipped a song while the loading circle was going on, I tried to go back to the home screen and it did take me there but than rebooted all of a sudden - It went straight to the G2 gray screen with the T-mo logo
2nd occurence - again I was listening to iheartradio app, trying to switch to a different but it rebooted back to the t-mobile gray screen ----- i think iheartradio is not tailored for android 2.2 yet, so i thought it could be the culprit.. since it only supports upto 2.1 in the market.
but yea nothing else as of now... hopefully it wont happen again.
This happened to me for the first time today. I was on the web, pressed the home button and scrolled thru the screens to get to my widget and it froze on me and rebooted to the t-mo g2 launch screen.. it actually stayed there for a good 2 mins so I pulled the battery and rebooted after and it was fine.. is this an on going problem that'll be fixed soon? i hope?
AND THEN, when the phone restarts it has more than 50 % battery.
WTF.
Is this happening to anyone else?
Are you running stock, di18, eb13, eco5? More details please!
Sent from my SPH-D700 using XDA App
sorry, was just wondering if anyone else had this happen, running eb13 viper rom.
This has happened to me, at the
time I had syndicate 1.0.2. It did a soft reboot and didn't actually hang up till my phone finished rebooting. The whole time well it was on the booting video the call still worked. Then it booted to the lockscreen and the call ended.
Reminds me of my palm pre.
Sent from my SPH-D700 using XDA App
Hey, they called this phone the "Epic" for a reason, it only does things in epic proportions.
I've had that problem on the EB13 Syndicate, then today one the EC05 Syndicate... I fixed it last time, but can't remember how. I just wiped battery stats and did calibration, so I will let you know if that did it.
this happens to me whenever i get a phone call and i have less than 15% battery. it has happened on EVERY rom i have used
Sent from my SPH-D700 using XDA App
ydoucare said:
Hey, they called this phone the "Epic" for a reason, it only does things in epic proportions.
Click to expand...
Click to collapse
Truth LOL
Sent from my SPH-D700 using Tapatalk
I made a post about this a few weeks ago. I remember it happening on dk28 and everything since, multiple roms. Right now I am using eb13 with ec05 modem but haven't had a call yet whan my battery was that low. I can't believe not very many people have complained about this.
Sent from an Epic failure of a phone.
Are you STILL here trolling the Epic forums J3ff?
Sent from my Froyo'd Epic using XDA App
nerdtaco said:
Are you STILL here trolling the Epic forums J3ff?
Sent from my Froyo'd Epic using XDA App
Click to expand...
Click to collapse
I wouldn't call it trolling if it's the truth.
It just happened to me again.
15% beep, DROPPED CALL, phone reboots, 22% battery on restart.
I can't wait till a new cool phone comes out on sprint.
Mee too, just don't get the same one I get ok?
Sent from my Froyo'd Epic using XDA App
Still happens on EC05 with SRF and Rodricks kernal.
well even after loading a new kernal and rom, still happens. I just bought a 3500mah battery, FML
Can't wait to get rid of the epic. Had the issue since EB13. I guess it's not bad as iphone dropping calls all the time, but still unacceptable!
NoSoMo said:
Can't wait to get rid of the epic. Had the issue since EB13. I guess it's not bad as iphone dropping calls all the time, but still unacceptable!
Click to expand...
Click to collapse
yup. It's annoying as F - I have to cut the person off and say "My battery is dead I'll call you back" as fast as possible.
Then the phone reboots and it has 30+ % battery.
Seriously stupid.
J3ff said:
yup. It's annoying as F - I have to cut the person off and say "My battery is dead I'll call you back" as fast as possible.
Then the phone reboots and it has 30+ % battery.
Seriously stupid.
Click to expand...
Click to collapse
Are you running SetCPU or an Undervolt settings? When a battery gets to a low percentage, the voltage is lower so any undervolt settings will actually be even lower and the phone will crap out. At 40% my phone would not wake and totally black out, needed to pull battery. Found out I had undervolted 200 Mhz by 100 mV. Pushed that back to zero and no more problems.
It could also be a bad battery, especially with the varying percentage from reboots like that.
no undervolt. Just whatever the rom+ kernal settings are is what I run.
I should get the new battery this week. Hopefully that'll fix the problems
J3ff said:
no undervolt. Just whatever the rom+ kernal settings are is what I run.
I should get the new battery this week. Hopefully that'll fix the problems
Click to expand...
Click to collapse
You are running the kernel supplied with Syndicate or something else?
Do you BONSAI?
Yes blame the phone for everything when running a custom rom
The first time this happened to me I figured it was a fluke. Now I've had a third time where in mid phone call my Epic has "thought" it's battery was drained to 0 and hung up my call then proceeded to shut down. The first time was in a busy train station in Chicago, don't remember the situation the second, and today was when I got another call beeping in while I was on the line. Each time when I booted the phone back up it showed plenty of life left on the battery.
Has anyone else experienced this or could it be my phone? I wish I could remember specifics from the first two occurrences, but I believe it could have been a call waiting situation as well.
FWIW, I'm on the MTD CleanGB 1.0.3 rom.
Does it go through a shut down or is it just off? If it is just off may be loose battery connections. Oh you said it shut down on the call....maybe it was a modem crash. Try reflashing a modem.
Sent from my SPH-D700 using XDA App
Mine actually did this last night while I was on the phone
kennyglass123 said:
Does it go through a shut down or is it just off? If it is just off may be loose battery connections. Oh you said it shut down on the call....maybe it was a modem crash. Try reflashing a modem.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
It actually goes through the shutdown. Does the low battery double beep and pop up, then says shutting phone down.
Might need to wipe the battery stats then re-calibrate the battery. Mine has done this before, but I'm pretty sure it was from throwing the battery at my wall.
theduce102 said:
Might need to wipe the battery stats then re-calibrate the battery. Mine has done this before, but I'm pretty sure it was from throwing the battery at my wall.
Click to expand...
Click to collapse
Quite possible. I think I didn't bother calibrating the last couple of times I've flashed a ROM. Going to go ahead and do that and hopefully it doesn't happen again.
CapsLockKey said:
Quite possible. I think I didn't bother calibrating the last couple of times I've flashed a ROM. Going to go ahead and do that and hopefully it doesn't happen again.
Click to expand...
Click to collapse
Ya I've had the same issue I would have like 14% and while I'm in a call it would shut down
Just wipe status and calibrate it and it should be fine
Sent from my SPH-D700 using XDA App
I've had this happen, only on cm7 though.
Doesn't happen often so I've not been worried about it
Sent from my SPH-D700 using xda premium
This used to happen to me ALL the time. It was so frustrating, as soon as it hit 15% if I was talking it'd shut right down. Thankfully flashing the new GB roms seems to have fixed the problem. I sure hope it doesn't happen in CM7
I have this issue regardless of rom. Happens when on a call and low battery alert sounds.
Well, just did it to me again. I calibrated the battery after upgrading to the latest MTD cleanGB yesterday. I was in a building that had poor signal granted, but same thing dropped call, low battery popped up and it shutdown. I had 60% battery left.
This is my first nook. I did some trading to get it. It had cm9 on it when I got it but it a tad laggy so I put mirages cm7 on it using from manager. It has been running great ever since and today I put it on the counter(battery was around 60%) I took it to my room a little later to charge since I have to work tonight but before I plugged it in I tried to wake it up but the screen would not come on. It will not do anything at all. Never owning one I have no idea how to diagnose it.
Sent from my Galaxy Nexus using xda premium
Welcome to the Sleep of Death - I have this happen occasionally too.
Hold the power button for ~10 secs, the screen will get noticeably darker when it actually turns off. Let go and press for another ~8 secs to cause it to reboot - you'll get that distinctive flash from the back-light.
I find this happens more often when I leave the wifi on and it goes to sleep, so I'm pretty obsessive about turning that off before sleeping the nook.
What ROM are you running? Stock CM7 or Phiremod / Mirage / etc.?
HumanXv2 said:
This is my first nook. I did some trading to get it. It had cm9 on it when I got it but it a tad laggy so I put mirages cm7 on it using from manager. It has been running great ever since and today I put it on the counter(battery was around 60%) I took it to my room a little later to charge since I have to work tonight but before I plugged it in I tried to wake it up but the screen would not come on. It will not do anything at all. Never owning one I have no idea how to diagnose it.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That was probably Sleep of Death (SOD). Read about it in my tips thread in my signature link.
Sent from my Nook Color running ICS and Tapatalk
Worked like a charm, thanks a lot. I'm running mirage now and sometimes back to miui. Debating on going back to cm9.
Sent from my Galaxy Nexus using xda premium
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