So a weird thing just happened:
My phone was on and running fine. (I'm on Mack 3.5 with LK8). A few minutes pass and I pick my phone up and it's completely shut off. Wouldn't start up with the power button, I had to pull the battery. It loaded up fine and the only thing I notice that changed was the inverted google play store I had installed reverted back to white. Any thoughts on this?
Maybe play store updated?
Update: New one finally received.
Sent from my SPH-L900 using Tapatalk 2
Sounds like sleep of death, goes into deep sleep and ends up in a coma. Are you undervolted at all? If you are try raising you min clockspeed voltage back to normal.
☆SoA: Son's of Android™☆
I like to break stuff!
Related
I think this is an ec05 thing. I never noticed out until ec05. What happens is, after talking on the phone for 30 minutes or so, if anything wakes the screen like another call or like today a low battery warning, the phone will freeze. Sometimes I can still talk and other times the call will drop.. I have noticed that sometimes when I hang up it will freeze and I will have to pull the battery and reboot. usually it is plugged into a charger, but also does this just by itself. It is not the wake from sleep thing, as I have had that and this is different.. Like the thing is getting to hot or something.. I am currently running a stock rooted only ec05. I have re ch lashed and all and I still have this problem here and there. It isn't every call and I can't reproduce it over and over.. Any ideas or things to try to narrow this down...
Thanks.
I've noticed this as well, both on bone stock, and on SRF 1.1.1.
Are your overclocked or undervolted? This could be causing funky cpu frequency jumps you otherwise normally don't see and causing your phone to freeze or even reboot.
Sent from my SPH-D700 using XDA App
Stock rooted phone with no modifications, no over or under.. Not sure what is going on..
Take that droid over to Mos Eisley and get the memory flushed.
Sent from Bonsai 7.1.1.1
Oh how I wish it was that easy!!
Is anybody else having issues with their ET going to sleep and you have to pull the battery to get it come back up? I thought it might have been my setcpu settings. So I cleared them and uninstalled it. I tried the midnight rom and the starburst rom. I tried the stable and exp LosKernel. None of these got rid of this issue for me. Randomly through out the day I can try to wake the phone up to use it and nothing happens. After a minute or two I have to pull the battery. I am currently testing the stock kernel.
Thats weird, the only time that happened to me was when i had setcpu, and i tried putting "screen off" value to 200/200.
You should install setcpu again, and make screen off value 500/500, and if you dont have the issue, then try making the value 200/500, if you dont have the issue at this value, then leave it as is.
Sent from my SPH-D710 using xda premium
I agree it is weird and I am not sure why it is happening. If it stays okay with the stock kernel then I may wipe and try the viperrom.
Yep happened twice the other day... Im on stock rom with lost kernel..roooted i put setcpu to 200/1200 after waking my screen for a minute used google came back 3 min later and phone was either off or wouldnt wake .. I had to pull battery twice.
I setcpu up to 1200/1200 never happened again.
This is a nice phone but very touchy.. Seems alot weird things goin on for some Et users.
Worst of all for this phone is Los or just weak /radio signal in general ..which is a samsung issue.
Sent from my SPH-D710 using XDA Premium App
Why people still insist on screen off profiles amazes me. When you hit the power button to wake it - the phone is stuck at 200MHz, you do realize this? If snything else is going on while it's stuck at 200 or SetCPU doesn't sample the phones state fast enough, it never gets out of 200MHz and locks up. Just like any other processor does when you overload it.
All the background processes going on even when the screen is off and somebody thinks setting the CPU max to 200MHz is a good idea? That's just asking for it. Not to mention the screen off profile is known to cause this issue. Notice how Virtuous, Viper, Cyanogen, and many other developers don't use one in their native OC daemons? There's a reason why. The phone sleeps just fine without it, just let it do it's thing.
Don't use offscreen profiles (the kernel is smart enough) and avoid using task killers, as those are likely to be the second leading issue.
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
ElAguila said:
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
Click to expand...
Click to collapse
Just wanted to throw this out there: beware mislabeling this problem. The setcpu issue causing the phone the permanently lock up and require a bat pull is one issue, yes; slow screen wake up is a different issue. Sometimes if you hit the power button, the screen will not wake up on the first try. If you wait a few seconds and push in the button again for a second or so, the screen almost always will come after. Coming from a mo-pho, I actually had the stupid no-wake problem requiring bat pulls, so I'm extremely paranoid about by e4gt doing this -- but it really has been good about eventually waking up every single time...just try my instructions and see if it works for you, too.
Again, though -- setcpu issues may be a different problem entirely.
did you reinstall a rom and try it again or did you simply just unistall setcpu and try it. I say this because I had an issue when testing setcpu and my system still kept my cpu setting even after I unistalled the app. I had to reinstall the rom after wiping to get it to run properly again.
I think I have found the issue. I did a factory reset and installed the rom but I am getting an error now that is basically saying it can't read the internal storage card. So I think there are some actual hardware issues going on that need to be looked at by sprint.
how often has the sod been happening? I think i got it yesterday, but not sure.
Do you use setcpu?
Sent from my SPH-D710 using Tapatalk
This thread seems a little slow- has there been a solution found or are we isolated cases?
I reflashed the phone back to rooted stock and then flashed Blazer 4.1.
Got 2 SODs in the past week- one just a few minutes ago.
I tried calling the phone from another line, it rings but the screen is black and thus I couldn't answer it.
Power button and vol buttons work fine.
I had to powerdown and reboot.
Getting kinda frustating.
I've recently started to have CPU Usage problems. Things are running at 4 percent idle, things like messages, reader, etc... Things that shouldn't be. I woke up at 2 AM only to discover the side of my face burning after turning over in my sleep onto my phone. The phone was burning hot. It even had the case on. I quickly went to Task Manager and CPU usage for Maps and Navigation was at ~46 percent each. What is happening? This has never happened before (except with Spotify). I am running everything completely vanilla stock, besides Sprint carrier updates.
RootTheWorld said:
I've recently started to have CPU Usage problems. Things are running at 4 percent idle, things like messages, reader, etc... Things that shouldn't be. I woke up at 2 AM only to discover the side of my face burning after turning over in my sleep onto my phone. The phone was burning hot. It even had the case on. I quickly went to Task Manager and CPU usage for Maps and Navigation was at ~46 percent each. What is happening? This has never happened before (except with Spotify). I am running everything completely vanilla stock, besides Sprint carrier updates.
Click to expand...
Click to collapse
Exactly why I deleted Maps and I reinstall it as needed. It sounds like processes are running on their own. Search in XDA for BetterBatteryStats. It will give you a more detailed breakdown of what's happening
Sent from my SPH-D710 using xda premium
it is probably an app causing it when your phone gets hot check the task manager and check cpu and if an app is yellow or red that's probavbly what's causing it. hope this helped.
I loaded it up and used it for about 3 mins or so (gpu force is on). I could feel the phone starting to get hot and about that time my screen went black (which has done this before) so I pulled the battery out which usually fixed previous issues. Well this time everything would boot up and once the launcher loaded my GPS icon appeared in the status bar and the device would crash and reboot again. After numerous battery pulls and booting into safe mode and everything else I could think of the problem never corrected, doing the same thing everytime. Eventually had to restore with factory image.
Just wanted to know if anyone else has experienced this? Also, it doesn't help that in new to android and was completely uneducated on a fix besides what I did and was a little turned off to the OS at that point.
On the other hand I love my Galaxy Nexus lol
Sent from my Galaxy Nexus using xda premium
i play around with it here & there but have never had that happen. also, i have gps/location turned off(always that way) so not sure if that has anything to do with it.
I'm playing around with it aswell and up to 30-40 min straight without it ever even getting tempered.. with gps location turned on and over wifi..
Sent from my Galaxy Nexus using xda premium
no issues here with earth over wifi. gps off. didn't get too hot either. also loaded faster and with less lag than my transformer.
I've also used it for more than 15 minutes without problems. It does heat up, but nowhere near the ungodly temperatures it reaches while playing games.
gps seems to heat up more when charging it seems. with any phone. but i wouldn't sweat it too much unless your phone is rebooting or melting.
crookone10 said:
Just wanted to know if anyone else has experienced this? Also, it doesn't help that in new to android and was completely uneducated on a fix besides what I did and was a little turned off to the OS at that point.
Click to expand...
Click to collapse
I had a few freezes (mostly in google maps) but they were resolved with a battery pull. Your expereince could have been just very bad luck.
Try this App to check your phones hardware: https://market.android.com/details?id=com.into.stability&feature=order_history
I had no problem running it for 20 min, no errors occurred. Phone gets really warm to the right of the camera when the App is active, which is to be expected.
Both mine loaded fine.
My phone locks up 2-3 times a day when sleeping. When it locks up, the "SAMSUNG" splash screen briefly flashes, and the phone vibrates. If left alone, it gets warm. I have to hold the power button or pull the battery to restart it. I have been unable to adb into the phone to get logcat or dmesg after it locks up. Also, this never occurs while the phone is plugged in. I have tried Darkside v8 with both Venom and Faux 008 kernels, as well as Jedi Mind Trick 8/18 with Faux 009. With Darkside, I tried changing the screen-off governor with System Tuner to ondemand as mentioned at http://forum.xda-developers.com/showpost.php?p=29559002&postcount=8633, but it didn't help. Is there anything I may have done wrong, or any way to fix this? Thanks!
What happens if you don't touch the governor?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
What happens if you don't touch the governor?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
With conservative governor and screen-off set to no governor change, it crashed this morning. Running Mind Trick 8/18 with Faux 009.
MadMax3947 said:
With conservative governor and screen-off set to no governor change, it crashed this morning. Running Mind Trick 8/18 with Faux 009.
Click to expand...
Click to collapse
Try on demand .
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
Try on demand .
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I set the governor to ondemand and rebooted. Phone locked up within 10 minutes. Also, if it helps, I had Venom clocked at 384/1512 and Faux at 384/1728 (since I can't lower the max because of DVFS). Darkside v8 ran fine for about a week before the crashes began.
MadMax3947 said:
I set the governor to ondemand and rebooted. Phone locked up within 10 minutes. Also, if it helps, I had Venom clocked at 384/1512 and Faux at 384/1728 (since I can't lower the max because of DVFS). Darkside v8 ran fine for about a week before the crashes began.
Click to expand...
Click to collapse
When you say lock up you're talking about sleep of death correct? Have you logcat afterwards?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
When you say lock up you're talking about sleep of death correct? Have you logcat afterwards?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
It only locks up when the screen is off, and never when plugged in. I tried Streamline kernel a while ago and got sleep of death basically every time the screen turned off (and I went back to stock immediately), but this seems different (in that it doesn't just not wake up like Streamline, the phone vibrates and displays the SAMSUNG splash before it won't wake up). I tried to get a logcat with adb when it last crashed, but the phone didn't even show on my computer's USB bus. I restarted it and took a logcat and dmesg until it booted, which I can send you if you wish.
I tried flashing Gideon's stock OC/UV script (http://forum.xda-developers.com/showpost.php?p=20946429&postcount=574), thinking that my phone may just be unable to handle the default UV with Venom and Faux, but this caused it to SOD (without the SAMSUNG splash) almost immediately. I went back to my Nandroid of Darkside v8 (since Mind Trick didn't help things), and flashed Faux 009 with the undervolt set with System Tuner to -12.5mv below stock for all stock frequencies. If this doesn't help, is there a possibility that my phone is faulty? I have had it since December. Also, could this be related to the GPU or L2 overclocks in Venom and Faux (but if so, why wouldn't it crash when the phone is awake)? Thank you for your time.
If it still crashes, I have a flashable zip of the stock ICS kernel and its modules that I can try, or if extremely necessary I can ODIN back to stock.
EDIT: manual Faux UV did not help, just flashed stock.
EDIT2: It just crashed with stock kernel as well (still using Darkside v8 ROM). Since it doesn't seem to be ROM or kernel related, I'm worried it may be the phone (perhaps whatever passes for a PSU in a smartphone? It'd explain why it doesn't crash on battery power). I'll probably try flashing AOKP ICS next in case it's a TouchWiz problem. Is there anything I'm missing here, or should I ask for a warranty exchange if AOKP or stock ODIN still crashes?
EDIT3: Uninstalled System Tuner to be completely sure nothing's affecting the governor/voltage/clock/etc. (still Darkside v8 ROM, stock UVLE1 kernel), crashed within 15 minutes of restart.
MadMax3947 said:
It only locks up when the screen is off, and never when plugged in. I tried Streamline kernel a while ago and got sleep of death basically every time the screen turned off (and I went back to stock immediately), but this seems different (in that it doesn't just not wake up like Streamline, the phone vibrates and displays the SAMSUNG splash before it won't wake up). I tried to get a logcat with adb when it last crashed, but the phone didn't even show on my computer's USB bus. I restarted it and took a logcat and dmesg until it booted, which I can send you if you wish.
Click to expand...
Click to collapse
I would put stock ROM back on it take it to a t mobile store and show them what's happening. If you have warranty they should replace it. Your CPU is shot. It won't go into deep sleep. And when running stock, it's not a software issue. It's hardware.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
I would put stock ROM back on it take it to a t mobile store and show them what's happening. If you have warranty they should replace it. Your CPU is shot. It won't go into deep sleep. And when running stock, it's not a software issue. It's hardware.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I was worried about this. I will ODIN back to stock tonight, but I won't be able to take it to a t-mobile store for a couple of days. Thank you for your help.
EDIT: I have been running stock UVLE1 (kernel and ROM) without root for almost a day now, and it has not locked up. According to CPU spy, the phone is able to enter deep sleep. Could there be something in the custom boot scripts used by Darkside and Mind Trick that my phone doesn't like? It's about the only thing I could think of that would not be fixed by the stock kernel. I might try re-rooting and/or flashing AOKP ICS in a few days if my phone holds up.