On occasion, usually once a day, I press the power button to wake my phone and I get nothing. This started happening pretty randomly all of a sudden one day. I have to hold power and reboot the phone when this happens. I've tried several cm10 nightlies and aokp, and both do this. I have not flashed a Samsung build nor have I tried cm9. The odd thing is that I can unlock the phone even with the black screen, I can feel the haptic feedback bur the screen will never come on till I reboot. Any thoughts?
What is the minimum CPU speed you have set? And what versions of the ROM are you using. Also are you on stock kernel?
Sent from my SAMSUNG-SGH-I747 using xda premium
Oogy said:
On occasion, usually once a day, I press the power button to wake my phone and I get nothing. This started happening pretty randomly all of a sudden one day. I have to hold power and reboot the phone when this happens. I've tried several cm10 nightlies and aokp, and both do this. I have not flashed a Samsung build nor have I tried cm9. The odd thing is that I can unlock the phone even with the black screen, I can feel the haptic feedback bur the screen will never come on till I reboot. Any thoughts?
Click to expand...
Click to collapse
This sounds a lot like an SOD. I have not had one on CM10 10/9 or 10/10.
z34370z said:
What is the minimum CPU speed you have set? And what versions of the ROM are you using. Also are you on stock kernel?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Min cpu is 384.. Going to up it to see if this stops.. But have used both stock cm kernel and the ktoonsez one
Right now I'm on the 10/5 Aokp ktoonsez task650
I've not had this issue since cm9 but if you want to avoid it don't flash a third party kernel.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Related
Anyone else have this problem? I just got this phone like not even a week ago and it just stopped working. It will work like 10-15% of the time. Should I send it in or what should I do? would it be a software problem Like the rom I installed? I doubt it but I installed the AokP with franco kernal would that be it?
I have aokp 28 with Franco kernel and I've never experienced this problem. If your power button is giving you issues go to settings in rom control and use volume wake with this feature I never use my power button.
Sent from my Galaxy Nexus using xda premium
beiker44 said:
Anyone else have this problem? I just got this phone like not even a week ago and it just stopped working. It will work like 10-15% of the time. Should I send it in or what should I do? would it be a software problem Like the rom I installed? I doubt it but I installed the AokP with franco kernal would that be it?
Click to expand...
Click to collapse
1) Flash another ROM. Still broken?
a) No?: It was your ROM
b) Yes?: Go to #2
2) Restore to stock. Still broken?
a) No?: Custom ROMs borked it.
b) Yes?: Go to #3
3) Return the phone / warranty claim.
Had this issue. A little different since it was the volume rocker giving me a headache. Volume up suddenly was hit or miss. Then became totally unusable. Brought it back to the store, showed the problem, went home with a brane new Gnex.
Sent from my Galaxy Nexus using Tapatalk
I was wondering if anyone else experiences this issue.
I have flashed about a handful of JB ROMs. A couple AOKP releases, CM10 and also CNA. I have noticed that every JB ROM I flash I don't get sound (touch screen,ringtone any sounds at all) for the first 5 or 10 mins after signing into the phone.
I do a clean wipe and install, wait 10mins, reboot and then sign in and setup my phone, but during the first 5 to 10mins of setup I don't hear anything even when the volume is turned all the way up. I can even disable sound and then re-enable and the same thing. Then all of a sudden it just kicks in and starts to work.
Very strange, wondering what would cause this? Since this has happened on every JB ROM could it be gapps related? Suggestions?
After a while it does work and I don't have sound issues afterward, but I just can't figure out why it happens. Thanks.
I'll have to pay more attention on the next awesome rom I'm going to flash tonight
But I did notice that I never get a sound when connecting usb.
Sent from my SAMSUNG-SGH-T989 using xda premium
many people have been experiencing this issue, adjusting the volume keys during a call or while using gnow seems to do the trick for me..
Old school trick was to turn volume down all the way and then back up all the way
Sent from my SGH-T989 using xda app-developers app
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
joooe said:
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
Click to expand...
Click to collapse
It is a common issue with custom kernels right now. It is due to a bug in the source. We have to wait for Google to fix it. For the meantime use a stock kernel or anything close to stock like 007 kernel
Sent from my Galaxy Nexus using Tapatalk 2
joooe said:
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
Click to expand...
Click to collapse
deeren said:
It is a common issue with custom kernels right now. It is due to a bug in the source. We have to wait for Google to fix it. For the meantime use a stock kernel or anything close to stock like 007 kernel
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
the same issue with stock kernels too(unrooted and rooted).
btw, its not called bsod, its called sod(sleep oif death)
It's probably not kernel related. Did you turn your animations off in developer settings? Try turning them to .5. Helped me and several others. Running mmuzzy with tiny kernel.
klobkelosh said:
It's probably not kernel related. Did you turn your animations off in developer settings? Try turning them to .5. Helped me and several others. Running mmuzzy with tiny kernel.
Click to expand...
Click to collapse
Will try that.
Thanks everyone.
I have the same BSOD/SOD issue... will try the 0.5 animation trick and report back. I would hate to go back to 4.1 roms.
I found new love for my SGN with the 4.2.1 smoothness.
Did it help?
I am experiencing SOD / BSOD on my Nexus 4 + latest CM10.1 nightly from time to time... (stock kernel).
In developer settings there are actually three settings regarding animations - are all to be set to .5?
Best regards,
ww
For me it did, yes.
No more BSOD.
I put them all to x.5
I've been diagnosing this for some time and I feel fairly confident that it is only the animation duration setting that triggers the sod. I have the other two settings set to 0 and duration set to 1 and no sod. But, it will not turn off that pesky crt animation.
who in here looked at logcat/dmesg when that happens?
do you have daydream ON? do you use an adblocker?
i've had one on 4.2.1, WITH AN ADBLOCKER installed. no adblocker, no bsod. full stock (rooted, unrooted, tried them both, doesn't matter), default settings (only enabled usb debugging)
just had another SOD / BSOD: I connected the charger and realized after 15 minutes, that the clock was unchanged (still 15 Min prior) - I tried to open an app and got a timeout. After I switch the screen off and on again I just saw a black screen (a little bit lighter than actually off) - but no homescreen anymore... damned.
Hi guys,
So i upgraded my T989D from Koodo stock 4.1.2 to PAC-MAN v23.0.0 from this thread: http://forum.xda-developers.com/showthread.php?t=2332229 .
Everything was running fine for the first 2 days (besides having to set the governor to samsung, as default interactive would severely lag the phone). However, yesterday the phone froze and would not turn on properly (would get stuck on CM boot screen). Eventually after a few battery pulls it loaded up, but I cannot put the phone into vibrate mode. It goes from silent to sound and skips vibrate. All options within Settings > Sound relating to vibrate have disappeared. I tried rebooting multiple times with no success. Also tried searching google/xda but nothing similar popped up.
Any ideas on how to fix this issue would be highly appreciated!
Just make sure you have the kernel where it sits right with out lag so you can use the rom right also for the vib reboot the phone once ,twice its a known issue but should work :thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
krazierokz said:
Just make sure you have the kernel where it sits right with out lag so you can use the rom right also for the vib reboot the phone once ,twice its a known issue but should work :thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
By kernel are you referring to the performance control? If yes, than I have already set the governor to "Samsung" and it does not lag at all.
I have restarted multiple times (it does freeze during boot quite often, requiring more restarts), but I can never get the vibration function back.
Try another ROM and see it it happens there
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Ended up installing a new kernel: http://forum.xda-developers.com/showthread.php?t=2230064
Vibrate option is back. However the phone still gets stuck on the boot screen. Have to do multiple battery pulls before it loads up properly.
Hey guys,
Was wondering if anyone has experienced their Tab 3 8'' not waking up from sleep at random times.
This happens to be about once every day or two where i have to hold the power button to reset the tab because it won't wake.
I'm on the latest stock firmware.
Sent from my GT-I9100 using XDA-Developers mobile app
I had this happen before, but not as often as you experienced this. I am not sure what happens, but holding the power button to reset always fixes it, even though it is a pain to always have to do that. Also, I am running the latest CM13 rom, but I have experienced it on other roms as well.
Rawb0Ss said:
I had this happen before, but not as often as you experienced this. I am not sure what happens, but holding the power button to reset always fixes it, even though it is a pain to always have to do that. Also, I am running the latest CM13 rom, but I have experienced it on other roms as well.
Click to expand...
Click to collapse
Thanks for the reply. It's interesting it happens on CM13 too. I played around with different governors and schedulers but it doesn't change anything unfortunately.
I thought it might have something to do with leandroid toggling WiFi off for me at certain times as well, but I disabled that and it still goes into a sleep of death.
Sent from my GT-I9100 using XDA-Developers mobile app
44hats said:
Thanks for the reply. It's interesting it happens on CM13 too. I played around with different governors and schedulers but it doesn't change anything unfortunately.
I thought it might have something to do with leandroid toggling WiFi off for me at certain times as well, but I disabled that and it still goes into a sleep of death.
Click to expand...
Click to collapse
This problem is common maybe,it's because of your kernel is buggy or something