Develop Bugs

Sleep of death

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.

lockup during sleep

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.

Galaxy Nexus Occasionally Freezes and Reboots?

This just happened to me today. First time it happened was early in the afternoon when I was playing Mini Motor Racing and I turned off the screen for a while. When I turned it on and unlocked my phone, the game screen was black. When I pressed the home button, it froze on me, then it rebooted. Second time, it was the same situation. Then the third time, when I was downloading a game from via my browser, it froze and restarted on me and now, I tried to transfer an obb file from a game to my phone and when it was half way done, it restarts on me. Anyone know what's going on?
Sent from my Galaxy Nexus using xda app-developers app

mini motor does that to me as well. not the gnex's fault. it just doesn't resume so well.

svtfmook said:
mini motor does that to me as well. not the gnex's fault. it just doesn't resume so well.
Click to expand...
Click to collapse
So could it be mini motor racing that's causing the reboots?

I forgot to mention that it makes a popping noise when it freezes and restarts
Sent from my Galaxy Nexus using xda app-developers app

More than likely it is mini motor. I've had apps that froze my phone that required battery pull. Deleted the app and all was fine.

Sounds pretty typical of overheating, or overclocking/undervolting. Maybe try keeping a fan on it when doing anything intense. Or you might try a kernel that lets you raise the voltages a bit. Some phones are more stable that way.

I dont know about volting. How much should I overvolt? I'm using AOKP w/ Franco kernel. My max clock speed is 1305 (previously 1420) and my min clock speed is 920.
Sent from my Galaxy Nexus using xda app-developers app

I'd try furst uninstalling the app just to see it after the pone runs properly or it keeps rebooting. The OC/UV issue is hard (at least for me) and have never given to me no good experiencies. I tried once to UV and had the same problems you're having, only solving theme by retoring setting to default.

If you're rooted, get the Trickster Mod app from the Play Store and disable Smart Reflex (all three switches) and see if the reboots stopped.
Cause apparently, that seems to be the case foe my phone (I use Faux's kernel v 21 with no smart reflex... the basic basic kernel)
sent from my mini tractor

question useless
Most kernel use Smartreflex, and if he had do this answer , i dont think it's going to undervolt under stable value for his phone
If you could provide more info about your phone specs its better, if you use OC kernel like Glados with 2 ghz, it's pretty normal, ever cpu is different
using CM10 nights can cause ( never ) bug like this, but if your phone freeze in infinite bootloop with metallic sound under is surely voltage value.
try to use your ROM's stock kernel , ( you might reflash without wipe anything your ROM and ( if needed ) GAPPS )

Well... if your post was directed to me, in that case, I'm using the non smart reflex version of the kernel. The stock kernel also uses smart reflex.
Strangely, I have to use the kernel without smart reflex... cause if I get another kernel which has the provision for smart reflex, and manually turn it off, it doesn't seem to help (or stick).
Of course, if your list wasn't targeted to me, then feel free to ignore this post
sent from my mini tractor

Music skipping/freezing when screen is off

I notice that whenever I play music (Pandora or Google Music) with the screen off and a bunch of recent applications, the sound will skip and stutter. This only happens when the screen is off AND when I have a bunch of recent applications open. It sounds like an issue with how JB is handling RAM, but I have 80-90% ram usage at most when it happens; or perhaps is an issue with the wakelock under heavy RAM usage. If I clear all the recent applications by holding the home button down and clicking the trash icon, this problem goes away.
Phone Info:
- Teshxx's stock T-889 rom odexed (03-05-13) 4.1.2
- Baseband T889UVALK8
- Model: GT-N7105 (I could rename to T-889 but I believe this is relevant to the issue)
Attempts to resolve:
- Wiped dalvik cache and regular cache
- Installing newer versions of Teshxx's stock odexed rom
- Wiped app data from Google Music and Pandora
Potentially related:
- I deleted the stock music player and musicFX app
- I deleted some other miscellaneous apps
- I have some tasker profiles that address both Pandora and Google Music (one is a trigger to open Pandora, the other is to increase volume of Google Music)
- I have not tried and would like to avoid doing a full system wipe

Im completely stock and listen to pandora several hours a day. Usually while driving to and from work.
No issues for me.
Could be an issue with your ROM.

IAmSixNine said:
Im completely stock and listen to pandora several hours a day. Usually while driving to and from work.
No issues for me.
Could be an issue with your ROM.
Click to expand...
Click to collapse
Do you usually have the screen off and have a bunch of recent apps?

Same happens to me with LG O3D in every music player (only while screen off). Even If I Use only 70 % of ram
Sent from my LG-P920 using xda app-developers app

Jinra321 said:
Do you usually have the screen off and have a bunch of recent apps?
Click to expand...
Click to collapse
Screen is off when im driving.
Ive gone days with out rebooting my phone, and i dont go in and stop them. So yes recent apps has what ever has been opened in between reboots.

Probably a ROM issue. I am back onto stock with my gs3 (Waiting on note 2) and have never had those issues. O have had them on different ROMS though.
I can have tons of apps open and screen off and no issues on stock. Shouldn't be a RAM issue either as 2G is plenty.
Sent from a galaxy far away!

I encountered a simular problem on my Samsung infuse tracked it down to cpu throttling I'd check governer and scheduler may be some screen off power save bias built in to rom maybe
Sent from my SGH-T889 using xda app-developers app

SIGMAxB said:
I encountered a simular problem on my Samsung infuse tracked it down to cpu throttling I'd check governer and scheduler may be some screen off power save bias built in to rom maybe
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I do believe it may be related to CPU throttling as well. I do not have powersaving enabled and also do not have have any governing apps. I have better battery stats to track my CPU speeds and battery stuff, but I'm not sure how to set governing without an app.

Jinra321 said:
I do believe it may be related to CPU throttling as well. I do not have powersaving enabled and also do not have have any governing apps. I have better battery stats to track my CPU speeds and battery stuff, but I'm not sure how to set governing without an app.
Click to expand...
Click to collapse
With a script
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Are you using voodoo sound?

Could be ROM, kernel, CPU settings, etc. This happened to me last week with the CM nightlies. I installed an update & my music started stuttering like crazy when the screen was off. Turns out I had the CPU settings customized for a special kernel but hadn't reinstalled that kernel, so the phone was trying to manage the stock CM kernel with settings for the custom kernel.

This used to happen to me before I switched to Perseus kernel. Since then I don't have the issue. Could you try that?
Sent from my SGH-T889 using xda app-developers app

I tried doing a full wipe and installed teshxx's N7105 t-mo rom (4/09/13) and did not use any throttling apps (everything else stock). The music was still skipping with the screen off, but I tried setting my minimum CPU speed to 400mhz (from 200mhz) and the skipping stopped (300mhz still skips). So I'm positive it's a problem with CPU throttling now. Since it's a full wipe and I'm still having this issue, I feel that it's a hardware issue. Perhaps I should just warranty my phone.

Changed governor to on demand and all is good.

Music skipping when screen turns off
Hey guys, I didn't realize how many other people were having this problem too....
My phone is rooted and I used ROM Toolbox Pro to turn up the min CPU value from 200mhz to 400mhz and it seems to work so far. So if you can find any type of app that can up your minimum value on your CPU it might do the trick. Because that stutter is super annoying....
I will keep you guys up to date if this doesn't work. But so far so good.

I noticed the same thing on my note 10.1 tab. Fully stock, first day i got it it did that with Google play music. Only noticed it that one time though. I'll report back if it happens again.

<Solved> Need help. CPU usage maxed out constantly.

Not sure if this is the best place to ask, but here goes...
Google Pixel 2 XL (Google variant)
TWRP 3.2.1-2
ElementalX kernel
Rooted with Magisk
TL;DR - Need something to view app CPU usage
Today (and a few times before this) my system UI started crashing every 20 to 45 seconds. The few times this happened before, I just assumed it had something to do with Substratum or app updates and I've uninstalled all theme overlays and updated the system to the latest factory image. So, today, I uninstalled theme overlays, uninstalled Substratum, updated to May image and rebooted back to the system. The system UI still crashes without root, Substratum and custom kernel. This time, I noticed that the phone was getting a little hotter than it normally does. So, in between system UI crashes, I determined that all 8 CPU cores are staying maxed out. I haven't found an app or any setting that allows me to monitor what apps are using the CPU (or rather, what apps are hogging the CPU). Does anyone have any ideas where to start with this kind of issue?
BTW, the phone was running fine a couple of hours earlier. I was out driving around (for work) and this just started.
Any help would be greatly appreciated....
Thank you

Got it fixed.
Thanks for listening

Inane65 said:
Got it fixed.
Thanks for listening
Click to expand...
Click to collapse
What was the culprit?
Sent from my Pixel 2 XL using Tapatalk

soopermarkus said:
What was the culprit?
Click to expand...
Click to collapse
Sorry. Never got a notification for this question.
It was an app called volume locker. Apparently, it changed the volume from a Tasker profile and when it changed back to the default it kept trying to go back and forth constantly. Caused the CPU to max out. Reboot wouldn't fix it. Had to uninstall and reinstall it.