My Z3 sometimes does "stealthy" auto reboots when not in use. The system crashes and does an auto reboot but not a full one because the phone won't ask for the sim pin code, it will reboot to the lockscreen so unless you're looking at the phone while it happens you won't notice. If you're lucky enough to catch the reboot, you'll notice the screen suddenly lighting up, and the boot animation will play, then the phone will go back to the lock screen where you left it. My phone does this a couple of times a week, most of the times I don't catch it but there's a way to tell: go to Settings → About Phone → Diagnostics → SYSTEM INCIDENTS
If it shows 0 this means you haven't had a reboot in the past 10 days. Right now on mine it shows 1 which happened during the night (so I didn't catch it happening). I always have 1 or 2 in there, I'm not sure if it always happened, but I started noticing it after Lollipop, and factory reset didn't help.
Please let me know if you have any "system incidents".
MarkMRL said:
My Z3 sometimes does "stealthy" auto reboots when not in use. The system crashes and does an auto reboot but not a full one because the phone won't ask for the sim pin code, it will reboot to the lockscreen so unless you're looking at the phone while it happens you won't notice. If you're lucky enough to catch the reboot, you'll notice the screen suddenly lighting up, and the boot animation will play, then the phone will go back to the lock screen where you left it. My phone does this a couple of times a week, most of the times I don't catch it but there's a way to tell: go to Settings → About Phone → Diagnostics → SYSTEM INCIDENTS
If it shows 0 this means you haven't had a reboot in the past 10 days. Right now on mine it shows 1 which happened during the night (so I didn't catch it happening). I always have 1 or 2 in there, I'm not sure if it always happened, but I started noticing it after Lollipop, and factory reset didn't help.
Please let me know if you have any "system incidents".
Click to expand...
Click to collapse
Hi Mark
I know this phenomenon on custom Roms or when using a custom kernel.
I think this is called a hot - reboot, kinda, because it's not a full reboot.
If you're using w custom kernel this might be the reason, or the settings of the kernel.
I can't check what you requested because I'm using the concept rom atm.
But I'm quite sure I don't have this issue, as I remember from kk days that the notifications are gone afterwards and I think this would go for lp too, and I didn't notice so far (on this rom).
But I did have had random reboots many times at different set ups of course. It can also occur on certain stock kernel settings or root apps I assume.
Gesendet von meinem D6603 mit Tapatalk
Aronuser said:
Hi Mark
I know this phenomenon on custom Roms or when using a custom kernel.
I think this is called a hot - reboot, kinda, because it's not a full reboot.
If you're using w custom kernel this might be the reason, or the settings of the kernel.
I can't check what you requested because I'm using the concept rom atm.
But I'm quite sure I don't have this issue, as I remember from kk days that the notifications are gone afterwards and I think this would go for lp too, and I didn't notice so far (on this rom).
But I did have had random reboots many times at different set ups of course. It can also occur on certain stock kernel settings or root apps I assume.
Gesendet von meinem D6603 mit Tapatalk
Click to expand...
Click to collapse
My phone is completely stock and I still have these weird reboots. Before I do another factory reset I'm trying to understand if other people have them (and then not bother with a factory reset because that would mean it's a firmware issue) or if I'm the only unlucky one who keeps getting them. Anyway, I was considering getting my phone serviced, I noticed the glass is a bit misaligned and I have a dead pixel, I called the service center and they said both issues are covered by the warranty. Might as well add random reboots to the list, maybe they'll get me a refurbished phone, mine has a few marks on it.
I factory reseted my phone and then sent it in for repairs, most likely got a refurb too since this one looks brand new, and I still have those "system incidents" happening early in the morning when the phone is just resting on my table.
I don't like begging for replies but please if you stumble upon this thread just drop a line saying if you have them or not. At this point I can't be the only one.
Also I'd like to know if there is any way to consult a log or something that would tell me why it happened.
I used to have them on kk, but they stopped. Mine would only happen at work, which led me to believe it was network related somehow... As if a spotty signal was heating up the phone or something. They stopped as randomly as they started.
Sent from my SM-T700 using XDA Premium HD app
I factory reseted my phone again after messing with the concept rom, and guess what, not even one day passes and the piece of crap reboots out of nowhere like always. I'm so mad right now, I only have 3 thirdparty apps installed, poweramp, the app from my mobile data provider and waze. I will start to try and get rid of this phone now, this is absolutely ridiculous.
I have exactly the same problem. Started after installing LP. Had someone found a solution?
Sam
Wait, is this happening on the Concept ROM? Because if so, you do know that's an unfinished ROM, right? Not meant to be a daily driver?
Clean flash the latest stock LP and go from there.
robogo1982 said:
Wait, is this happening on the Concept ROM? Because if so, you do know that's an unfinished ROM, right? Not meant to be a daily driver?
Clean flash the latest stock LP and go from there.
Click to expand...
Click to collapse
Dude, read the post again. It's happening on stock lollipop with literally no mods installed. I kept the concept rom for 5 days and it was absolutely stable for those 5 days. Stock lollipop reboots at least once every 10 days, but usually twice.
Here's a recap: I had the phone for quite a while now, I don't remember if I had reboots on KitKat, but I definitely have had them for the past 2 months or so. Meanwhile I got my phone refurbished because I had a dead pixel, it was already rebooting when I sent it in, got it back factory reseted and hardware refurbished and the reboots continued once I started installing all my stuff. Now I installed the concept rom to check it out, went back to stock lollipop with a full factory reset via PCC and after a day with pretty much nothing installed I had another reboot. The only thing that was kept during all this time is my 16Gb Class 3 SanDisk SD Card and my WIND (IT) nano sim card. I've decided to buy another SD Card anticipating the Android M memory unification feature, so I bought a Class 10 uhs3 32Gb SD Card from Kingston (which by the way isn't reaching anywhere near the declared speeds of 80/90mb/s, it only reads and writes at around 35 on the phone, I made a thread about it, maybe the phone itself can't read that fast), and I've been using it for a day now. I had no reboots yet but I had some weird app incidents under diagnostics, one from photo analyzer service and one from backup and restore (I hope they happened when I was still messing with the memory card in and out, because I didn't use any of those apps).
Here's a thread I made on the official forum:
https://talk.sonymobile.com/t5/Xper...oubleshoot/m-p/1057964/highlight/false#M26160
By the way, I still don't know if these reboots are rare or if everyone has them. Too few people have commented on whether they have them or not, while this thread has 447 views. If even 10 people commented saying if they had reboots or not I'd be able to rule out glitchy firmware. A friend of mine has the Z3C and he said he has no system incidents and his phone never rebooted.
Still getting soft/stealthy reboots
After doing a complete repair via pcc, I did not put a SD card back in my phone and only installed my google account and apps... No 3rd party apps. It goes for a couple days and then starts doing a reboot usually once every charge and mostly in the morning. The battery usage graph shows a pretty significant gap as if the phone was off but not completely off. Then I find system incidents in the diagnostic app but it only gives me the date and time of when it happens. No other information. Kind of useless if you ask me. This has all started after updating the official LP build . 200 firmware. Sony needs to investigate this became it's happening more and more for people on 5.1.1
I have a locked bootloader, stock kernel, rooted, xposed, dual recovery, tricked out rxz experience ROM with 85 apps (it includes 17-19 xposed add-ons) in addition to 102 system apps, no random reboots at all. I keep an eye on phone diagnostics, system status (temperatures, etc.) like a hawk.
So guys if this happens at you at stock rom , my suggestion is ask the service for replacement maybe.
Sent from my D6603 using Tapatalk
I am currently doing a test after repairing via pcc, installing a new Google acc, only important updates to apps I use that come pre-installed. So far it's been 5 days and no soft boots or incidents in diagnostics. Although it means nothing because usually after about a week or so is when the issues come back after doing a full repair or factory reset. I guess time will tell. Otherwise everything seems to be working great, especially battery life.
Related
I've been through 2 G2x's , both have had the same problems...
Random reboots
Random freezes
Random shutdowns
Crazy inconsistencies in battery life
I've also gone the route of rooting and trying CyanogenMod with the same results.
With the battery issues, I did the following test 3 nights in a row.
Phone wiped, 100% battery charge, signed into Google and let the apps download, rebooted phone, data connection turned off (airplane mode), unplugged the phone and set in the exact same spot in the same room 3 nights in a row at 11PM.
Come 8AM when I woke here's the results:
Day 1: 30% battery remaining
Day 2: 80% battery remaining
Day 3: 0% remaining - battery was stone cold dead - wouldn't boot until I plugged in.
Phone was fine when I started typing this post, but just now while typing this message I reached over to check my phone for text messages (I keep the alerts volume all the way down while at work) and it's locked up again...
Guess I'll be returning the phone for a refund and borrowing an old flip phone for a month until the Sensation comes out.
Sorry LG - when it works, it works AWESOME, but I need something a bit more reliable considering that work needs to contact me on the phone and I am on call 24/7 !
In the 2 weeks I've had it I've only had 2 random freezes and no other issues at all. This is my first android phone and the thing i see that's screwed up with android is it leaves applications open, there is no exit buttons on apps. I've been using juice defender and uninstalling any apps that keep popping back up after ending task on them.
Sorry to hear about your problems. You're doing the right thing by returning it and getting another phone. I don't understand why people have loyalties to corporations who could give 2 craps about you. Buy what works for you and makes you happy.
For me, the occassional reboot on the G2X is a pain but the promise of a stable CM release and an official gingerbread release on this hardware has me sticking it out. Can't wait
I haven't had any issues with my phone except battery life. Buy my battery life isn't as bad as yours. It used to be horrible but I got a new sim and that seemed to make it better.
Regarding the reboots, some apps are causing the phone to reboot. Either the apps aren't optimized for the phone or the other way around. I had one reboot and after I removed the offending app, never happened again.
Sent from my LG-P999 using XDA App
kangxi said:
I haven't had any issues with my phone except battery life. Buy my battery life isn't as bad as yours. It used to be horrible but I got a new sim and that seemed to make it better.
Regarding the reboots, some apps are causing the phone to reboot. Either the apps aren't optimized for the phone or the other way around. I had one reboot and after I removed the offending app, never happened again.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Actually, when I bought the phone I had them put a brand new SIM card as mine was getting to be a little long in the tooth - if getting a new one helps the situation I'd hate to see how it was with my old one :-D
Removing an offending app would prove to be a real problem for me though, as everything that I install has a legitimate work-related function.
im returning mine today for a newer batch one. its may 4 so i expect one that has the date of 4/24 and up as stated in other threads. mine reboots and freezes during random functions.
I ordered mine on the 20th so the day the phone was out in the store. I had to order mine online since i am a T-Mobile RSA. I have alittle screen bleed but not much. I will be doing exchanges until i get one with no bleed. Other wise i have had no problems at all. No reboots, lock ups, data problems, nothing the phone is rock solid. I love the phone. Every person that has come into my store with problems i have told them that T-Mobile is going to exchange this for you under the lifetime warranty if you have it for the life of you having the phone. So you have nothing to worry about. The phone is a great phone to have. Do the exchanges until you get a working one. I know i would do it until i did. Even if it meant doing it 100 times.
JWhipple said:
I've been through 2 G2x's , both have had the same problems...
Random reboots
Random freezes
Random shutdowns
Crazy inconsistencies in battery life
I've also gone the route of rooting and trying CyanogenMod with the same results.
With the battery issues, I did the following test 3 nights in a row.
Phone wiped, 100% battery charge, signed into Google and let the apps download, rebooted phone, data connection turned off (airplane mode), unplugged the phone and set in the exact same spot in the same room 3 nights in a row at 11PM.
Come 8AM when I woke here's the results:
Day 1: 30% battery remaining
Day 2: 80% battery remaining
Day 3: 0% remaining - battery was stone cold dead - wouldn't boot until I plugged in.
Phone was fine when I started typing this post, but just now while typing this message I reached over to check my phone for text messages (I keep the alerts volume all the way down while at work) and it's locked up again...
Guess I'll be returning the phone for a refund and borrowing an old flip phone for a month until the Sensation comes out.
Sorry LG - when it works, it works AWESOME, but I need something a bit more reliable considering that work needs to contact me on the phone and I am on call 24/7 !
Click to expand...
Click to collapse
A better test would have been to not install any apps. Then you could truly test your phone and not some rogue app, that you keep installing.
I'm about to do a complete wipe again and use a secondary Gmail account I have so to eliminate any apps from auto-installing and test throughout the day since I have my work PC handy.
or just skip the Gmail sign in process at first and add your Gmail account later from Settings. This will prevent it downloading your apps on first boot.
Also to the New Android User: Back closes apps, Home leaves them open. It isn't the OS's fault if you don't know how to use it.
To the OP: Have you rooted and flashed the Pre-Dexopt Patch from Paul?
http://forum.xda-developers.com/showthread.php?t=1051616
LG left the phone in Dev mode and doesn't dexopt the phone on initial bootup. This is why our phones boot so quickly. The downfall is after a few hours, it starts to lag out and lock up/reboot.
Sounds exactly like the problem you are having.
This patch is required for stock and EaglesBlood Roms excluding CM7. This should be fixed in the upcoming Gingerbread update. I also believe EaglesBlood and future roms will start coming with this patch included.
So do yourself a favor and patch it.
Basically, it's an awesome phone and many, if not all, of the issues should be resolved with software updates. Gingerbread is already in the works.
Sent from my LG-P999 using XDA App
player911 said:
or just skip the Gmail sign in process at first and add your Gmail account later from Settings. This will prevent it downloading your apps on first boot.
Also to the New Android User: Back closes apps, Home leaves them open. It isn't the OS's fault if you don't know how to use it.
To the OP: Have you rooted and flashed the Pre-Dexopt Patch from Paul?
http://forum.xda-developers.com/showthread.php?t=1051616
LG left the phone in Dev mode and doesn't dexopt the phone on initial bootup. This is why our phones boot so quickly. The downfall is after a few hours, it starts to lag out and lock up/reboot.
Sounds exactly like the problem you are having.
This patch is required for stock and EaglesBlood Roms excluding CM7. This should be fixed in the upcoming Gingerbread update. I also believe EaglesBlood and future roms will start coming with this patch included.
So do yourself a favor and patch it.
Click to expand...
Click to collapse
Yep, have tried without the patch initially and then with it.
I have signed in with the secondary Gmail account - only thing I imported from the original was my contacts, so, it's 100% stock with the exception of Paul's patch and recovery.
I'll be damned...
In an attempt to preemptively find out what I would need to return the accessories I ordered for the phone just in case I took the plunge and returned the phone, I was on hold with T-Mobile...
And while on hold, I grabbed my phone - and SURE ENOUGH - LOCKED UP HARD!
So, I guess this just made up my mind for me - I'll be returning this phone to point of purchase. Just need to use NAND to restore the stock backup , reflash stock recovery and unroot...
I am planing to return this phone too..
It seems the phone shut down completely for no reason, sometimes the screen doesn't wake up even tho phone is running in background.
So far i have tried to run completely stock with no apps installed no sync nothing and i was getting battery like 6-7 hrs.
I guess that was not acceptable for me.
I might have to wait till HTC Sensation comes out. What you think guys ?
Mine works fine, no problems at all, yes the screen bleeds a bit, but I can deal with that.
awesome phone, much better than my atrix
Sent from my LG-P999 using XDA Premium App
Slappy00 said:
Mine works fine, no problems at all, yes the screen bleeds a bit, but I can deal with that.
awesome phone, much better than my atrix
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
+1 Mine also works amazing... and a lotttt better than atrix....
ikm19 said:
I am planing to return this phone too..
It seems the phone shut down completely for no reason, sometimes the screen doesn't wake up even tho phone is running in background.
So far i have tried to run completely stock with no apps installed no sync nothing and i was getting battery like 6-7 hrs.
I guess that was not acceptable for me.
I might have to wait till HTC Sensation comes out. What you think guys ?
Click to expand...
Click to collapse
That's where my money is going...
my understanding is the sensation is locked down that's why cyan isn't going to get it. Which also means no dev support.
The MyTouch 4G and G2 were locked down too... Unless they are going to lock the bootloader?
ikm19 said:
I might have to wait till HTC Sensation comes out. What you think guys ?
Click to expand...
Click to collapse
HTC announced an update to the Sensation in Q3 that will include a NFC chip to match the features of the SGS2. I'm also guessing they'll increase the amount of RAM in the phone to make it more competitive. If the 2.3.3 update makes the G2X stable I may keep it until later in the year. If the Sensation comes out before they update the G2X I'll get Sensation. I need a phone that's consistently dependable and in that regard the G2X is a mess. I can't do custom ROMs because I travel globally and everyone I've ever used has always given me problems registering on foreign networks so CM7 is no silver bullet for me. It's a shame too because the G2X hardware (bleeding screen excepted) is pretty slick and it's really fast when the planets line up and everything works. Sigh.
I've been searching the interwebs and XDA for days regarding the random reboots that the Nexus S is cursed with and I was wondering if there are any confirmed solutions? (Phone randomly reboots, and gets stuck at a bootloop with a very dark screen until battery pull).
I've read reports where an OTA was supposed to have fixed the problem and read other reports that stated that if the reboots persist after the OTA then the phone has a hardware issue and needs to be replaced.
Mine has been doing it at the most random times, which is a major inconvenience for me if I rely on the alarm clock to wake me up in the morning.
I've run factory wiped, flashed stock, Cyanogen, and NSCollab and they all have had the problem. Can anyone provide me with some help?
If I can't figure out how to get rid of them I think I'm going to try my luck with a refund or exchange before the warranty runs out.
I just got an AT&T version for my wife during the "free upgrade" promotion. I have not rooted or installed any roms and this phone is having some issues. Reboots at completely random times, goes into boot loops, and even locks on a black screen with the buttons lit. I have been searching for about 2 hours without any real answers. I have been through Aria, Captivate and now NS. Flashing roms and dealing with android quirks is usually not an issue, but I want to retain my ability to return this phone if it is faulty.
What I have tried:
1. Uninstalled questionable user apps
2. Switched SIM cards (used my SIM)
3. Factory Reset
Model: GT-I9020A
Ver: 2.3.4
Base: I9020AUCKE1
Build: GTJ61
Some help/suggestions from some experienced Nexus S owners would be appreciated. Thinking tomorrow will be a return to Best Buy.
andythefan said:
I've read reports where an OTA was supposed to have fixed the problem and read other reports that stated that if the reboots persist after the OTA then the phone has a hardware issue and needs to be replaced.
If I can't figure out how to get rid of them I think I'm going to try my luck with a refund or exchange before the warranty runs out.
Click to expand...
Click to collapse
I ended up doing an exchange at BB today and the problem is gone. I would definitely attribute your problem to a hardware issue. The new NS that I have is running smoothly and has not had one freeze or reboot yet. Get yours traded in before it is too late.
I would like to add that it seems there is a lot less support/community advice in the NS section than some of the other sections I visit. Strange...
I get the same thing, and frequently woke up (late) to bootlooping...
This is far from a fix or diagnosis.. but this is how I manage:
1. Buy a cheap alarm clock
2. when the phone is bootlooping, I plug in the usb (to computer), open dos prompt and type adb reboot or adb reboot recovery (then fix permissions). If you have the android sdk installed on your computer, of course.
I have a case.. and it's a pita pulling the battery out.
However, before i go to sleep, I've been turning off auto-sync (gmail, contacts, etc, all of them), and it hasn't bootlooped overnight since.
Something to try.. but good luck My signature has my phone version and setup.
Thanks for replying everyone. I went ahead and arranged to have it replaced. In my area only one Best Buy had Nexus S's in stock and they were sold out online. There was an armed robbery in the area near the Best Buy, but I went anyways!
I've got the last Nexus they had and just nandroid restored. Everything seems fine so far!
Not even a week into having a replacement Nexus S the reboots have started happening again. It's happened twice today. This leads me to think, is this a software issue?
Try a different kernel.
Wipe cache & dalvik.
Fix permissions.
So Im a little new to this, and hopefully I won't be asking things that can be easily found, since i did try looking for answers..after having my verizon s3 for over a month now (still stock), im having a few different issues/annoyances, and can't figure out how best to resolve them.
1) Whenever i restart my phone, i get voicemail notifications, even though I have no new notifications.Ive seen a few different solutions for it, namely leaving yourself a voicemail, then deleting it and it should make it go away...but it doesnt. i can only get a temporary fix, which is to go and force stop the Phone application, but next time my phone restarts the same issue happens again.
2) a few times my phone will hotboot..or atleast thats what i think its called. basically the phone will freeze, then after a minute or two it will go back to the lock screen..but if i leave it alone, or if i try to run anything, it will again freeze and go to the lock screen. this even happens when i restart my phone. the way around it i found is to unlock the phone, then immediately turn off the screen. after 15-20 seconds, i can turn the screen on again and it will work fine. i read some topics on this but they seem to be random occurrences, and i didnt really see anyone saying it happens on every startup..
3) android_system/gsiff_daemon killing me battery- so over the last week ive seen that this is really killing my battery. it always takes up about 50% of my battery, no matter what i do.it also seems to cause the phone to get really hot. the topic i read below, it seems like a root cause isn't found yet, and the only way to resolve it without rooting is to restart your phone, but for me it seems so always come back at the top..
http://forum.xda-developers.com/showthread.php?t=1755180
i'm wondering if rooting and unlocking the bootloader will help at all. the last time i rooted a phone was like 2-3 years ago with my incredible, so im a little cautious about doing it and accidently bricking my phone. i was going to follow section 2 of this guide, there shouldnt be too much of a risk of it going wrong right? http://forum.xda-developers.com/showthread.php?t=1762709
y2jasper said:
So Im a little new to this, and hopefully I won't be asking things that can be easily found, since i did try looking for answers..after having my verizon s3 for over a month now (still stock), im having a few different issues/annoyances, and can't figure out how best to resolve them.
1) Whenever i restart my phone, i get voicemail notifications, even though I have no new notifications.Ive seen a few different solutions for it, namely leaving yourself a voicemail, then deleting it and it should make it go away...but it doesnt. i can only get a temporary fix, which is to go and force stop the Phone application, but next time my phone restarts the same issue happens again.
2) a few times my phone will hotboot..or atleast thats what i think its called. basically the phone will freeze, then after a minute or two it will go back to the lock screen..but if i leave it alone, or if i try to run anything, it will again freeze and go to the lock screen. this even happens when i restart my phone. the way around it i found is to unlock the phone, then immediately turn off the screen. after 15-20 seconds, i can turn the screen on again and it will work fine. i read some topics on this but they seem to be random occurrences, and i didnt really see anyone saying it happens on every startup..
3) android_system/gsiff_daemon killing me battery- so over the last week ive seen that this is really killing my battery. it always takes up about 50% of my battery, no matter what i do.it also seems to cause the phone to get really hot. the topic i read below, it seems like a root cause isn't found yet, and the only way to resolve it without rooting is to restart your phone, but for me it seems so always come back at the top..
http://forum.xda-developers.com/showthread.php?t=1755180
i'm wondering if rooting and unlocking the bootloader will help at all. the last time i rooted a phone was like 2-3 years ago with my incredible, so im a little cautious about doing it and accidently bricking my phone. i was going to follow section 2 of this guide, there shouldnt be too much of a risk of it going wrong right? http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I would start with a factory reset and see if that solves your problems. keep in mind it will erase your apps and settings. VOL+/HOME/POWER
i was hoping to avoid factory reset since i didnt want to reset up my screens and apps, and also for the voicemail and gsif_daemon issue from what i read it keeps coming back. but if thats the best option i guess i have to suck it up and do it then
Root and unlock BL won't fix problems. That will only allow you to modify your phone more. I think you have to bite the bullet on this one. Test it out good before you install all your apps if you reset.
Sent from my SCH-I535 using xda app-developers app
You could just have some rogue apps. Many apps fail miserably just going from ICS to JB. I hated TouchWiz. Rooting and Unlocking Bootloader was the best thing that has happened to my S3. Rooting is very safe and its very easy to got back to stock. My battery was terrible on stock. 4G is going to eat your battery up quickly as opposed to just Wifi. All the alternative launchers can backup you home screen (Apex/Nova etc) and all your apps should be backed up in Googles cloud should quickly get pulled back down after a factory reset or ROM install
kanc3r said:
You could just have some rogue apps. Many apps fail miserably just going from ICS to JB. I hated TouchWiz. Rooting and Unlocking Bootloader was the best thing that has happened to my S3. Rooting is very safe and its very easy to got back to stock. My battery was terrible on stock. 4G is going to eat your battery up quickly as opposed to just Wifi. All the alternative launchers can backup you home screen (Apex/Nova etc) and all your apps should be backed up in Googles cloud should quickly get pulled back down after a factory reset or ROM install
Click to expand...
Click to collapse
hm ok. 4g isn't really the cause. in the area where my apartment is, 4g isn't even available yet, i only get a chance to use 4g on weekends when i come visit family/friends. otherwise i use the "phone info" app to turn 4g off. also my voicemail issue is resolved now, i messed around a bit more between voicemail and google voice and finally found the rogue message that was left. i'm thinking if i root and unlock, i can at the very least install a different kernal to improve battery life, to possible negate the gsiff_daemon issue.
s3 turning off randomly requiring battery pull to restart. here is the breakdown to date problem occured,verizon tech sent replacement phone, that phone did it so sent it back and kept original phone, replaced sims card, problem still there, replaced battery, problem still there replaced phone again, still there, replaced sims card and battery again,guess what phone is still shutting off randomly, stock rom,factory mode (no apps)nothing not even email linked all software ota up to date. all is documented by verizon and and sumsung but everytime i talk to them all i get is the same old we can send you a like new phone after all the resets and ect., i dont want another s3 that is reman wich i know does they same thing and i didnt really want to exchange what i thought was the best for a droid wich verizon wants to do and sammy wants to send reman. i have already had two other reman phones that do the same thing. now here is the kicker i own 3 total s3's and now guess what one of the other is doing it now too. is there anybody else having this problem? is there a way to track what is running when it shuts down?would a different kerrnel help? would a different rom help? could this be my account with verizon? any help at all i dont know what to do?
more info
i am starting to think this is a problem with the screen not waking up and staying dark and not necessarly shutting down. any ideas on ways to check this?
coop245 said:
i am starting to think this is a problem with the screen not waking up and staying dark and not necessarly shutting down. any ideas on ways to check this?
Click to expand...
Click to collapse
Try another rom although it sounds like an app. Can't be the phone on that many of them. You only one reporting this problem so has to be something you are putting on phone.
prdog1 said:
Try another rom although it sounds like an app. Can't be the phone on that many of them. You only one reporting this problem so has to be something you are putting on phone.
Click to expand...
Click to collapse
both phones are doing this on stock. no apps installed
My friend had 8 replacements through verizon before he got a good one. So try a couple more times maybe. I know it is really inconvenient but honestly the GS3 is the best Android on Verizon right now (arguably atleast) and they probably won't let you trade up to a Razr HD Maxx which is the only one I would recommend.
I'm having the same problem apparently. I just bought this phone used and activated it monday night. That night, i plugged the phone into the charger while i slept and the phone shut off overnight. Phone wouldnt turn on with the power button - required a battery pull to restart.
Going through tuesday, the phone worked fine. However, in the evening, the phone was idle for a few hours, and when I went to check it before going to bed I found it had powered off again! Required another battery pull to restart...plugged it into the charger, and went to sleep. When I woke up, I again found (for the third time) that the phone had powered down, and required another battery pull to restart.
Going into wednesday, phone is working fine. Then I leave it idle in the afternoon for a few hours during work, and when I get ready to drive home, I find it is again powered down, requiring a battery pull to restart (fourth time in less than 2 days).
Now I go to visit verizon, and the rep tells me (after I think he was looking through some company forums for answers) that I should try clearing the cache from every app, since maybe the data was corrupted during my OTA update to JB (which i installed monday night), and some app was causing this problem. So I do that, and the same thing happens again overnight...battery pull etc...
I'm figuring next I'm going to do a factory data reset, possibly tonight. This is supposed to be my sister's christmas gift! Hah...trying to work the bugs out before tuesday. Any thoughts?
Starting a post with I'm not crazy sound like something a crazy person would say.... just saying.... But I agree with the earlier post that it could be app or rom based and only effecting the screen. These are the options I see you having:
1. Try freezing any apps you've installed one at a time and see if it stops
2. Make nandriod and try another rom and then come back if that doesnt fix it
3. Try this thread to clear everything and upgrade http://forum.xda-developers.com/showthread.php?t=1984436
-This method formats internal and external sd card AND bumps you up to rooted JB in the process. Use VRBLK3.
4. Get a replacement phone
KjK89 said:
Starting a post with I'm not crazy sound like something a crazy person would say.... just saying.... But I agree with the earlier post that it could be app or rom based and only effecting the screen. These are the options I see you having:
1. Try freezing any apps you've installed one at a time and see if it stops
2. Make nandriod and try another rom and then come back if that doesnt fix it
3. Try this thread to clear everything and upgrade http://forum.xda-developers.com/showthread.php?t=1984436
-This method formats internal and external sd card AND bumps you up to rooted JB in the process. Use VRBLK3.
4. Get a replacement phone
Click to expand...
Click to collapse
These options might work for the OP, but only #4 could work for me since i'm not rooting this phone (its for my sister). If I find a fix for my issue, i'll post here.
Are you guys using an sd card? If so it might be a corrupt file that the system goes over and gets stuck on, messing the cell up. Did you try making a backup on pc, formating your card (fat32) and putting you stuff back on it? Or take the card out and see if you get the same problem without it. If you're going thru all the replacements then its gotta be something that you use in common with all of em. GL!
Hey guys,
I need help. Badly. My trusty SCH-I535 has pretty much gone to pot over the last three days. It started with the lockscreen/power button becoming so loose and sensitive, that the screen was perpetually turning on and off. However, my warranty expired last Thursday. Aside from that, the software was functioning beautiful (Carbon ROM, unknown August 4.3 nightly). Today however, the phone decided to freak out. Suddenly, it began displaying the incorrect time, wouldn't show me new messages, and applications were incredibly unstable. In an attempt to fix the issue, I decided to re-flash the ROM. This however, made no change. Therefore, I made the decision to finally update to the most recent stable version. After doing this, the phone wouldn't boot past the carbon boot animation. I rolled back to an older build, and had the same issue.
Here's where it gets sucky. After rolling back didn't do anything, I was in the process of re-flashing 1.8. During install process, TWRP crashed. This left me without a bootable system partition. As the night has worn on, it's become worse and worse. Now, TWRP is crashing often before the splash screen, at the "Samsung Galaxy SIII" screen. Occasionally it will load, but always locks up and crashes before finishing the install process. Same deal with CWM. I have tried several versions of both recoveries and none have made a single bit of difference. I've scoured the forums, and can't seem to find an identical problem/working fix. I've tried everything I can find, and so far, nothing productive has happened. It's 3:25AM over here, and I'm exhausted. I'm at my wits end. Any input would be fantastic.
Thanks so much,
The_Unofficial
Did you try to flash via ODIN? Maybe it will help you to boot it to normal.
The_Unofficial said:
Hey guys,
I need help. Badly. My trusty SCH-I535 has pretty much gone to pot over the last three days. It started with the lockscreen/power button becoming so loose and sensitive, that the screen was perpetually turning on and off. However, my warranty expired last Thursday. Aside from that, the software was functioning beautiful (Carbon ROM, unknown August 4.3 nightly). Today however, the phone decided to freak out. Suddenly, it began displaying the incorrect time, wouldn't show me new messages, and applications were incredibly unstable. In an attempt to fix the issue, I decided to re-flash the ROM. This however, made no change. Therefore, I made the decision to finally update to the most recent stable version. After doing this, the phone wouldn't boot past the carbon boot animation. I rolled back to an older build, and had the same issue.
Here's where it gets sucky. After rolling back didn't do anything, I was in the process of re-flashing 1.8. During install process, TWRP crashed. This left me without a bootable system partition. As the night has worn on, it's become worse and worse. Now, TWRP is crashing often before the splash screen, at the "Samsung Galaxy SIII" screen. Occasionally it will load, but always locks up and crashes before finishing the install process. Same deal with CWM. I have tried several versions of both recoveries and none have made a single bit of difference. I've scoured the forums, and can't seem to find an identical problem/working fix. I've tried everything I can find, and so far, nothing productive has happened. It's 3:25AM over here, and I'm exhausted. I'm at my wits end. Any input would be fantastic.
Thanks so much,
The_Unofficial
Click to expand...
Click to collapse
Your broken power button is probably the issue. The reason your recoveries are crashing is likely because the power button is triggered and it's making the phone turn off in the middle of the process.
It's unfortunate your warranty just expired, but you can get it fixed through a website, then you should be good from there. Also I would try to call up Samsung and tell them what you think the problem is, they might give you a break and fix your phone anyway since it's only a week after warranty.
Sent from my SCH-I535 using Tapatalk 2
Details...
Alright guys. More details. Sorry it took so long to reply. Apparently I had Gmail set to send XDA emails to spam. Silly me.
The more times I attempt to boot to recovery, the earlier TWRP will freeze.
TWRP rarely makes it beyond the "Installing System" process
TWRP NEVER makes it beyond the "Creating Symlinks" phase
I'm using TWRP 2.6.3.0
If I let the phone sit, it gets farther in the installation process before hanging
Bad Username, I tried contacting Samsung and Verizon. Neither one of them would replace , or fix it for me. Have any specific resources for repairing the button? That would be excellent. I just ordered a cheap $3 case on Amazon to see if that would help fix the problem. I don't, however believe this is causing the problem. TWRP has a lockscreen. It never goes to the lockscreen, it just hangs, then eventually force reboots. Almost as if some temporary RAM storage is being filled up. It's quite strange.
skyss07 I would REALLY prefer not to flash to stalk. Like, REALLY. This would mean losing all my files and pictures. I'm not too keen on that. I'm saving that as a final resort only.
The_Unofficial said:
Alright guys. More details. Sorry it took so long to reply. Apparently I had Gmail set to send XDA emails to spam. Silly me.
The more times I attempt to boot to recovery, the earlier TWRP will freeze.
TWRP rarely makes it beyond the "Installing System" process
TWRP NEVER makes it beyond the "Creating Symlinks" phase
I'm using TWRP 2.6.3.0
If I let the phone sit, it gets farther in the installation process before hanging
Bad Username, I tried contacting Samsung and Verizon. Neither one of them would replace , or fix it for me. Have any specific resources for repairing the button? That would be excellent. I just ordered a cheap $3 case on Amazon to see if that would help fix the problem. I don't, however believe this is causing the problem. TWRP has a lockscreen. It never goes to the lockscreen, it just hangs, then eventually force reboots. Almost as if some temporary RAM storage is being filled up. It's quite strange.
skyss07 I would REALLY prefer not to flash to stalk. Like, REALLY. This would mean losing all my files and pictures. I'm not too keen on that. I'm saving that as a final resort only.
Click to expand...
Click to collapse
Mobile tech videos would do it, not sure what the cost would be, I'd try contacting them.
Sent from my SCH-I535 using Tapatalk 2