Related
I was having problems with every custom ROM on my captivate randomly shutting down, I had to use Captivate Keepalive to keep it running. I was using AXURA before, then a friend referred me to PR 3.5 and I switched. My shutdowns actually increased! I was thinking that I was going to have to go back to vanilla when I saw a post mentioning similar problems, and though that it might help me too. I installed the kernel, and I haven't had a shutdown in 4 days so far! So for me, Phoenix Rising 3.5 + Glitterballs' kernel is rock-solid.
I was pointed Here.
As strange as it sounds different kernels give me different results too. Some make my phone do Random Shutdowns and others are stable as can be.
I noticed that to, different rom/kernels would effect random shutdowns it seems. Then I spent 10 minutes on the phone with att (literally 10 minutes) and they sent me a new phone next day for $2 and I can run anything I want with zero shutdowns.
Sent from my SAMSUNG-SGH-I897
Then this and the fact that AT&T are replacing certain build and batch of phone with the shut down issue seems to point to bad RAMs. With different ROMs and Kernals, managing different apps and services and loading different parts of kernel and page swap of the RAM probably caused the shutdown. Sort of like the BSOD for windows when things go wrong with stuff in the memory. So it sounds like the AT&T shut down replacement are replacing a bad batch of RAMs. Just a thought.
overkillthemighty said:
I was having problems with every custom ROM on my captivate randomly shutting down, I had to use Captivate Keepalive to keep it running. I was using AXURA before, then a friend referred me to PR 3.5 and I switched. My shutdowns actually increased! I was thinking that I was going to have to go back to vanilla when I saw a post mentioning similar problems, and though that it might help me too. I installed the kernel, and I haven't had a shutdown in 4 days so far! So for me, Phoenix Rising 3.5 + Glitterballs' kernel is rock-solid.
I was pointed Here.
Click to expand...
Click to collapse
The official fix is sending it in to Samsung and having them replace the TIB board on your Captivate. Flashing various ROMs is YMMV and definitely not a real fix.
I cant bare this any more
my phone shut down randomly at least 3 times a day. I almost missed my class today. I am not charging it, battery is 60% full. fu-ck Samsung and att.
pobinghun said:
my phone shut down randomly at least 3 times a day. I almost missed my class today. I am not charging it, battery is 60% full. fu-ck Samsung and att.
Click to expand...
Click to collapse
Speedmod K12O kernel works wonders! No more shutdowns!
alled samsung today and requested manager, this did not help. I asked about random shut downs and was told they know nothing about this issue.
I was asked to send in phone to be be checked but told these ingnorant people that this will not work. Who is going to pay for service which i am not using during downtime. Class Action , this is what we need.
a2gtinut said:
alled samsung today and requested manager, this did not help. I asked about random shut downs and was told they know nothing about this issue.
I was asked to send in phone to be be checked but told these ingnorant people that this will not work. Who is going to pay for service which i am not using during downtime. Class Action , this is what we need.
Click to expand...
Click to collapse
it amazes me that there isn't already a class action law suit against Samsung.. I don't understand how they can keep producing all these phones with faulty hardware.. first there was the GPS not working then the Vibrants on Bell had faulty RAM.. now the Captivates are randomly shutting down and even the Nexus S has random reboots.. is it too much to ask to make a phone that actually works as expected?
My Captivate's random shut down "sleep of death" also disappeared.
There is no shut down with GB kernels (12.28 or 01.04 #47 kernel)
and there was also no automatic shutdown with Speedmod K12 kernels (500MHz)
I was on Darky's 7xx nd 8x ROMS.
I'm using Hamsters 6.3 ROM with Speedmod K12O 500MHz Warm kernel and ZMKP1 modem. There is no shutdows so far. Battery life is excellent.
I must have missed this thread earlier when I posted elsewhere, but I also found that Phoenix 3.0 seems to have fixed my issues.
pezx44 said:
I must have missed this thread earlier when I posted elsewhere, but I also found that Phoenix 3.0 seems to have fixed my issues.
Click to expand...
Click to collapse
I am wondering, would it resolve random shutdowns? Currently im using FF3.0, have random shutdowns.
Only true resolution is to get replacement from Samsung/Att
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
mpencexda said:
Only true resolution is to get replacement from Samsung/Att
Click to expand...
Click to collapse
Yep. My third phone has been shutdown free for over 2 months.
I downloaded load monitor and it hasnt shut down in 5 months, I was shutting down 20 times a day before i downloaded it.
what is monitor can you explaint me i have same shutting down 20 times a day only on miui i don't have such problem
I've had my G2X for about a month, and have been experiencing the common issue where my phone randomly shuts off and the only way to get it to turn back on is to pull the battery.
I've installed the GB update, that didn't fix it. Factory reset didn't help either.
Has anyone successfully fixed this issue on their phone? If so, what'd you do? Is there any chance that rooting my phone would correct the problem?
Sorry if there was a post about this, I couldn't find anything talking about if anyone's been able to fix the problem.
Thanks
yes... the onlyhh way to fix the problem is to root! nvflash clock work mod recovery, then flash eagle blood 2.3.3 rom and it is perfect...
Thanks, this did indeed seems to do the trick. Not a single reboot so far after 2.5 days.
Sent from my LG-P999 using XDA App
My G2X actually restarted on its own today. It was the first time since the first few days I had the phone over a month-month and a half ago. Wasn't really a big deal, lol. It comes back on.
Have been playing with this phone for 3 days now and haven't had any issues (I did install xboarder's stock rooted version). Minor screen bleed is the only issue.
Sent from my LG-P999 using XDA Premium App
Finally, someone (dmaniscool) who can say they switched to an xda dev'ed ROM and got rid of the lock ups. I've posted many times asking if anybody ACTUALLY FIXED a problem (specifically the battery pull lock up); I got no responses, and someone finally stated it. Great. Next time my wife's G2x locks up, I'm rooting and putting a ROM on it.
Thank you dmaniscool
-Bob
so, PLEASE dmaniscool, occasionally update this thread with your lack of lock-ups, or if you get a lock-up. PLEASE!!!
Thanks,
-Bob
namklak said:
so, PLEASE dmaniscool, occasionally update this thread with your lack of lock-ups, or if you get a lock-up. PLEASE!!!
Thanks,
-Bob
Click to expand...
Click to collapse
Will do, so far so good! I had no experience with rooting, and was able to figure it out looking at the guides available on the forum. It kind of looks intimidating, but it's not actually very difficult.
By restart does everyone mean just shuts down? Mine never restarts, it will just shut off.
Sent from my LG-P999 using XDA App
RZJZA80 said:
By restart does everyone mean just shuts down? Mine never restarts, it will just shut off.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Mine did both actually, shut down and restarts. But mostly just shut downs, which required a battery pull to power back on.
My 2 will do both - but I think the "shut-off" is a lock up, because the longer I leave it locked up, the less battery I'll have after I do a battery pull.
8 days of both phones not locking up by doing one restart per day per phone.
Since I raised the minimum CPU speed to 389 from 216, I have far fewer sleeps of death
You don't wanna know where this was sent from.
I've tried every ROM and kernel combination possible and nothing actually fixes these problems for me.
Wow this post was scary at first, I had a thunderbolt and no matter what. RUU, Different ROMS, Stock, Kernels, Radios. Changing all that didn't matter it still turns off constantly and doesn't turn back on till I do it meaning no text or calls, basically same as having a phone on silent all the time without even having the luck chance of pulling it out while ringing.....
I am on miui x.26 (whatever kernal that comes with it) and have over 40 hours of uptime. I haven't had a crash yet, I just manually restart every couple of days because I'm weird like that.
Sent from my LG-P999
Well 6 days into it and I've had a total of 2 shutdowns. I don't know if it was a coincidence, but both times were after being outside when it was ~90 degrees out.
This is still much improved, I used to get 3-4 per day on average.
I'm using Eaglesblood 2.3.3. I'm thinking of trying MIUI because it's so nice looking.
For me I did a battery replacement the first time directly from T-Mobile and the phone continued restarting on me. I was just about to request a replacement phone from T-Mobile until I recently purchased a different brand of battery containing the same specs as the stock battery and to my surprise no overheating and definitely no restarts. I feel that the restarts and lockups are due to faulty batteries shipped out with the phones. I'm suprised no one has mentioned this.
Sent from my LG-P999 using Tapatalk
Do you mind sharing what brand battery you purchased?
Sent from my LG-P999 using XDA App
Wow, I told the CostCo kiosk girl I was having lock up problems and I had my grandkids with me. She took my phone and pulled the battery - at the same time my grandson stated he had to go to the bathroom NOW. She either looked at the battery or something on the phone under the battery. I didn't have time to ask. She didn't really comment and gave me my phone back.
Hmmmmmm........
-Bob
ok so do they know what exactly is causing the shut downs or reboot on this phone? i just got mine today and it was pre installed with gingerbread and idk if there is root for the gingerbread build yet. i just want root but no custom rom for me. i love the stock rom. it kicked the crap out of my sensation 4g as far as speed goes in everyday use.
Has anyone else came across the screen of death (random shutdown when idle and requires long pressing power to turn back on) with their Galaxy Tab 7+? I have this problem everyday and it seems like other Samsung phones had similiar problems like this one.
Does anyone know if there is a way to fix this? Supposively it may be a problem with the Wifi or reading the SD card when idle.
Sent from my GT-P6210 using xda premium
I Did a factory rest and haven't had one in two Weeks.
I did a factory reset last night and still have the same problem. Did you do a factory reset under "Settings > Privacy > Factory Reset"?
Didn't change a thing for me.
Sent from my GT-P6210 using xda premium
I occasionally get reboots, I can hear the sound when its in my pocket. Likely due to set cpu. My min is 500. I hear its related to on demand setting. I may uninstall if it persists.
the SOD issues is a known issue on some units.
While some units have it very frequently others don't.
The one i got from Fry's (and returned) had it.
The 3G version one i got from ipmart.com doesn't have it.
It seems like it may have something to do with the SD card reading. I removed mine and haven't had a problem since.
Sent from my GT-P6210 using xda premium
I take that back, just got SoD again. I'm really considering exchanging this for another one
Sent from my GT-P6210 using xda premium
charmartist said:
I did a factory reset last night and still have the same problem. Did you do a factory reset under "Settings > Privacy > Factory Reset"?
Didn't change a thing for me.
Sent from my GT-P6210 using xda premium
Click to expand...
Click to collapse
No I did mine from recovery. Power and the volume button closest to power. Select factory reset. I believe they are slightly different, but I am not positive of that. If that doesn't help, I'd return it if possible and get a different one. Here in the states most return periods have been extended Into January. Good luck.
Another thing you can try is using Odin to flash the retail ROM for the 6210 that is posted in the development section. I have had to do that several times trying to get cwm sorted, that may have fixed it. That's a good way of reloading the code, because I did get the sod several time prior to my first brick. After reloading the code, I forgot the problem even existed. Again good luck
charmartist said:
Has anyone else came across the screen of death (random shutdown when idle and requires long pressing power to turn back on) with their Galaxy Tab 7+? I have this problem everyday and it seems like other Samsung phones had similiar problems like this one.
Does anyone know if there is a way to fix this? Supposively it may be a problem with the Wifi or reading the SD card when idle.
Sent from my GT-P6210 using xda premium
Click to expand...
Click to collapse
I have had two Tab 7+ from Amazon. Both had the SOD problem. I returned both and now I will either wait until there is a fix from Samsung or will look for another tab.
I got them 2-3 times per day on my first unit...I exchanged it once Best Buy got another in stock and haven't had any issues at all. So yeah...if you're getting the SODs, exchange it if you can.
I had this too! I immediately asked for it to be returned. I didn't spend so much money on a device that randomly shuts down. Sending it back today..
I have only had one random reboot (that I know of). I have, however, had some apps like Marketplace crash on me at least a couple dozen times. I always have to manually reboot to fix it.
Quick update guys, I exchanged it today at Best Buy and just got done updating the firmware through Samsung Kies. We'll see how this one goes; I'll keep everyone posted.
Just wanted to let everyone know that I havent had a SoD since I exchanged it and the battery lasts longer also. So far so good, I'm glad I didnt keep the other one.
Sent from my GT-P6210 using xda premium
Well, i guess i spoke too soon. I updated the firmware tonight. Since then Ive had 2 random reboots.
GaresTaylan said:
Well, i guess i spoke too soon. I updated the firmware tonight. Since then Ive had 2 random reboots.
Click to expand...
Click to collapse
If you can, go for an exchange. Don't keep a defective item unless you have to. Samsung has warranty on it though I believe.
Sent from my GT-P6210 using xda premium
Im chalking my random reboots up to setcpu. Had 2 in 10 minutes. Removed set cpu none since. PROBABLY need a custom kernel.
chrisrotolo said:
Im chalking my random reboots up to setcpu. Had 2 in 10 minutes. Removed set cpu none since. PROBABLY need a custom kernel.
Click to expand...
Click to collapse
What were your SetCPU settings?
Any screen-off profile with a maximum limit less than 800 MHz WILL cause SoDs until the kernel can get patched.
removed all profiles. just 500 min 1.1 max
Finally gave up and returned mine. I had just updated to the latest firmware, did a factory reset and 4 hours later got 2 back to back SOD's. This was the last day I could return it to Best Buy and luckily they had 1 left. Charging the new one right now.
Starting today, my phone has been giving me notifications about a sign in error to my Google account. It's happened about 5 times so far, all just today. My phone is completely stock. Is anyone else experiencing this issue? Are Google servers having some issues?
I think Google was having problems this morning. Maybe they still are.
Sent from my ADR6300 using xda app-developers app
Okay thank you
Same here. I just flashed the latest Cyanogen mod nightly so I thought it was the ROM.
Sent from my SCH-I535 using xda app-developers app
Been getting that error like crazy today. I'm guessing it's cleared up though? Haven't seen it in a minute..
Just started getting it a few hours ago, completely stock.
I wonder if they're just making system wide changes in waves, you guys are getting the errors much later than me, I haven't gotten one in hours now
I am getting as well yesterday and today with 2 different ROMs so I believe its a Google issue
Confirming as well, just got one to be exact
I've been getting the log in error periodically for over a day now
It's been happening to me since last night, and I'm on a completely different phone. In searching for a solution that DIDN'T involve starting from scratch by reflashing a ROM (literally hours of work to retweak and restore everything, titanium backup and all) I found another thread regarding this issue on a totally different phone forum of xda.
I myself am running Now for ICS on my One S running Viper Rom. From this thread, with no details given I can only assume most of you are using Verizon galaxy S 3s?
But anyways. In the other thread it seemed the consensus that the issues were related to Google now. Some users reported some success from logging out of their Google plus then logging back in again. That resolution has provided me no dice so far.
Most users reporting the issue said that their google now was even not working at all. Have any of you tried google now while encountering these issues? Does it work or does it seem to be malfunctioning? Mine (along with the rest of my google apps) all seem to be working fine still. =L
Is anyone on here using a phone other than the Verizon GS3? what roms are involved? Anyone encountering this issue NOT have google now installed to their phone?
Hoping to narrow the details down in the interest of gaining a little more knowledge about this specific occurrence.
This happened to me a couple months ago, and I was running GNow for ICS back then too. Can't remember but I'm fairly certain the issue worked itself out. But its obnoxious ass all hell. Been getting the notification once every 5 minutes whenever I dismiss it, and its been prevalent since last night! It's starting to severely irritate me lol.
Sent from my HTC One S using xda premium
I'm on an HTC Amaze running a custom Speed Rom. My battery ran out during the error message and my phone wouldn't turn on again. Luckily I had a nandroid from earlier in the month, but I still lost 3 weeks of data on my phone, not the end of the world, but certainly a nuisance. I also recall having this happen a few months ago and the issue resolved itself so my guess is that it's an issue on Google's side. I am, however, disappointed that it's taking so long. A few hours is fine, but over a day and counting?
FIXED!!! (for me at least)
boojay said:
I'm on an HTC Amaze running a custom Speed Rom. My battery ran out during the error message and my phone wouldn't turn on again. Luckily I had a nandroid from earlier in the month, but I still lost 3 weeks of data on my phone, not the end of the world, but certainly a nuisance. I also recall having this happen a few months ago and the issue resolved itself so my guess is that it's an issue on Google's side. I am, however, disappointed that it's taking so long. A few hours is fine, but over a day and counting?
Click to expand...
Click to collapse
Tell me about it. Im seriously starting to lose my sanity over this.
A couple users said to disable Google Account manager (via settings > apps) as a temporary solution, but for me doing so disabled all of my g apps entirely so that's definitely not a good work around.
I spotted a thread in the amaze forum involving a speedrom issue (http://forum.xda-developers.com/showthread.php?t=1968141) and he seemed to think it was related to his Rom. Seemed that doing what he did resolved it, but given the prevalence of this issue accross as many devices as it has and as many roms as it has, I'm inclined to think that the issue coincidentally resolved itself while he was busy flashing lol
Regardless... I'm so desperate to stop being pestered by this issue that imma bout to wipe cache and dalvik cache and see I'd that doesn't fix the issue for me as well. I'll report back when I know one way or the other.
Edit - cache and dalvik cache wiped. Crossing my fingers. Only time will tell... Or not. Got the error whilst I was writing this paragraph lol. No dice
Edit 2 - interesting. I've had the sports card running for a couple days now. It kinda updated but didnt seem to be working 100%. Whether its related or not, im not sure but simultaneous to this behavior I noticed that the search function didn't work. Didn't open chrome up at all so I'd simply have to type my search into chrome directly. I just disabled the sports card and my search function is working again all of a sudden. Haven't gotten the error yet, if this pans out that might have been the source of my problem. Keeping my fingers crossed.
Edit 3 FIXED!!!!! (for me at least). It's now been an hour and 35 minutes since I disabled the sports card. My now search has been working for the first time in days since the instant I disabled it and the error free hour and 35 minutes is by far the longest span of time I've achieved in the last 24 hours (was getting the error within 5-10 minutes of each time I dismissed it previously). Anyone else encountering this issue have the Sports card enabled? Try it, see if it solves the issue for you as well and share with the class =)
Edit 4 - I guess it was a passing moment nonetheless. Got more errors.in the last 15 minutes after about 2 and 1/2 hours of not seeing it at all. Damn this is effing ridiculous
Sent from my HTC One S using xda premium
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Yeah AndroidAutobot, still issues here. It's really starting to get on my nerves. Kinda wish there was a way to disable specific notifications because it's not really hindering my usage. My only concern right now is draining my battery.
Swyped from my Android/iPhone Killer
boojay said:
Yeah AndroidAutobot, still issues here. It's really starting to get on my nerves. Kinda wish there was a way to disable specific notifications because it's not really hindering my usage. My only concern right now is draining my battery.
Swyped from my Android/iPhone Killer
Click to expand...
Click to collapse
Yeah. I gave up on it last night and figure with it being as prevalent as it is, it absolutely has to be server related and can't be anything Rom/system related by any means. On a positive note Im pretty sure I havent seen it in 3-4 hours so maybe they've finally fixed it. This is day 3 for me so I sure hope they did
Sent from my HTC One S using xda premium
I just went into the phone settings then account. Removed my gmail account then resign in and I have got the error all night
Sent from my SCH-I535 using xda premium
AndroidAutobot said:
Yeah. I gave up on it last night and figure with it being as prevalent as it is, it absolutely has to be server related and can't be anything Rom/system related by any means. On a positive note Im pretty sure I havent seen it in 3-4 hours so maybe they've finally fixed it. This is day 3 for me so I sure hope they did
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ditto, it's been a couple of hours since I've received the error. I think we have it beat!
Swyped from my Android/iPhone Killer
boojay said:
Ditto, it's been a couple of hours since I've received the error. I think we have it beat!
Swyped from my Android/iPhone Killer
Click to expand...
Click to collapse
Yep. It's been gone all day for me. At least it was persistently annoying enough this time around to actually remember that it.resolved.itself.I'd.there's ever a next time this comes up. Knocking on wood that It won't ever again of course =)
Sent from my HTC One S using xda premium
I'm running on Stock 4.4 rooted and Franco's kernel, starting tonight, out of no where my phone keeps waking up on its own. At first I thought it may be an app so I rebooted the phone and its still doing it. Any ideas? I didn't install anything in the last 24 hours and i just noticed it 10 minutes ago.
bilago said:
I'm running on Stock 4.4 rooted and Franco's kernel, starting tonight, out of no where my phone keeps waking up on its own. At first I thought it may be an app so I rebooted the phone and its still doing it. Any ideas? I didn't install anything in the last 24 hours and i just noticed it 10 minutes ago.
Click to expand...
Click to collapse
I have the same thing. Doesn't happen an awful lot, but when it does, it happens a few times within a short time frame.
I started a thread about this a few days ago and no one had any input. I'm rooted, but still on stock.
velveteen71 said:
I have the same thing. Doesn't happen an awful lot, but when it does, it happens a few times within a short time frame.
I started a thread about this a few days ago and no one had any input. I'm rooted, but still on stock.
Click to expand...
Click to collapse
I did a quick search before i posted and I didn't come across your post or I would have just wrote in that thread. Are you using stock kernel as well ?
bilago said:
I did a quick search before i posted and I didn't come across your post or I would have just wrote in that thread. Are you using stock kernel as well ?
Click to expand...
Click to collapse
Yep.