Related
Hi everyone,
Posting this here because this is my first post. I started to experience s o d or my nook won't wake up around the time the .32 kernals came out. 1 of which when I was playing with the screen on screen, screen off animations. the backlight would turn on but the nook was unresponsive, I did a hard reset and everything was okay. I don't know if it was a coincidence or not but ever since I unchecked " screen on animation" I have not had a sod. Just my 2 cents it seems to be a working for me maybe someone else to confirm this. Please respond using the following format.1. SODS yes or no. 2.screen on animation yes or no. 3. lockscreen yes or no
Sent from my ADR6300 using XDA App
JT75 said:
Hi everyone,
Posting this here because this is my first post. I started to experience s o d or my nook won't wake up around the time the .32 kernals came out. 1 of which when I was playing with the screen on screen, screen off animations. the backlight would turn on but the nook was unresponsive, I did a hard reset and everything was okay. I don't know if it was a coincidence or not but ever since I unchecked " screen on animation" I have not had a sod. Just my 2 cents it seems to be a working for me maybe someone else to confirm this.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
While I've never had a sod, I've found that unchecking screen on animation ensures a smooth, error free wake.
I'm curious to hear from people that have a lot of sods to see if they have screen on animation checked
Sent from my ADR6300 using XDA App
I had SODs when I first upgraded from a .29 kernal build. Wiping personal data has stopped the problem for me.
DeathsArrow said:
I had SODs when I first upgraded from a .29 kernal build. Wiping personal data has stopped the problem for me.
Click to expand...
Click to collapse
What personal data?
Sent from my ADR6300 using XDA App
I see they removed the screen on animation from the next nightly maybe I was on to something after all.
Took my nook from cm7#87 to 3.1 after flashing the stock ROM, wiping and installing all apps manually. overkill but I've been getting SoD, PBD and the SoD+PBD.
maybe on to something or there's something more that had to removed(?) cause I had animation off and had two SoD just this morning.
Check this out guys....
http://forum.xda-developers.com/showthread.php?t=1108964
Running: nightly-87, 1.2Ghz 5/23 OC kernel. Stable as a rock, and running significantly faster than nightly 60-something I came from. my system would not deep sleep at all, didn't have any battery problems.
The method of enabling on/off screen animations, then hard rebooting fixed it right up. No SOD's yet. Even though it will probably end up being fixed in the next couple nightlies, thanks for the tip.
Sent from my Nook color using Tapatalk
I've never had Power On Animation on, and I only recently turned on Power Off Animation. Neither appear to have any affect on SOD.
I was plagued with SoD - would need hard reset even after 3mins of screen turning off.
Unchecking 'screen-on animation' solved it 100%.
I repeat....100%......very happy camper here
Thank you to whoever suggested it - post now buried deep in one of the CM7 dev threads.
kevvyboy
The reason I suggested this is because when I flashed Dal's .32 beta I was thinking how cool the animations were. I sat in my chair for like 2 minutes watching the screen turn on and off, then once when i tried turning it on I got no animation. The back light turned on but no homescreen. I waited nothing happened, so I held down the power button then the back light turned off, then I hit power and it turned back on. So I figured something got hung up with the screen on animation so I unchecked it but still use the screen off animation.
Has anyone had this issue?
I have tried a few different ROM's and have had this problem on all, the phone will work but sometimes when the phone is locked and asleep you cannot get the screen back.
If you ring the phone it will ring but you can't wake the phone up (the screen is off).
If I then pull the battery and reboot all is well until the next time, which is random.
I will remove all my programs to see if there is one of them causing the issue, I don't believe it is the rom as it has happened on a few of them.
Have you wiped your phone when flashing the different roms? I've had it sometimes, i think it could be a ram management issue...
Talon26 said:
Have you wiped your phone when flashing the different roms? I've had it sometimes, i think it could be a ram management issue...
Click to expand...
Click to collapse
Yeh, I always do a factory/wipe, dalvik cache wipe.
I think it might have been TW4.5, I did some research and installed TW4 Manager I then updated TW4.5 to the latest Version. So far it hasn't happened yet but i'll give it a couple more days.
Thanks.
Yh ive been reading and TW4 generally accelerates the issue (because its a ram hog? not sure i dont use it) Im currently using Golauncher with system tweaks, but was told that nemus launcher and system tweaks was a better combination... Seems to be working, ive had less force closes or issues of that type
it's the proximity sensor. needs replaced.
pch.radu said:
it's the proximity sensor. needs replaced.
Click to expand...
Click to collapse
I don't think so...
The proximity sensor is only used when your in a call. It should not have any effect when he tries to wake it from his pocket after a while...
Well i am on 2.3.5 and using golauncher and never had any problems. Still my best guess is the damn sensor. On samsung apps there is an app called sensors i think and that app tells u what is working inside the phone.
Sent from my GT-I9000 using XDA App
If I recall correctly yeah I had this issue once on JVR and once on JVS and now on JVT I got it a few hours ago
---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------
pch.radu said:
Well i am on 2.3.5 and using golauncher and never had any problems. Still my best guess is the damn sensor. On samsung apps there is an app called sensors i think and that app tells u what is working inside the phone.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Sounds like a great app but seeing as the screen doesn't turn on that app might as well be useless in this case
No screen turns on, its just when it turns off it wont come back on...
I have the same issue with my SGS. Running stock version of JVT.
Wake up in the morning to phone alarm but screen is black. Pushing home button or any other button does nothing. Had this happen a few times now and only solution is to pull the battery
In order to help you we need to know what you are running currently and what you have tried to resolve the issue so far, can please make as detailed account as possible
It's seems that everybody have this same issue. I have exactly this same - phone is working - buttons are lit, but the screen is blank. I'm on 2.3.5 stock firmware.
Trying to solve this I already did wipe and even formatted the internal storage.
What's more interesting is that this same happens to my wife's Galaxy Mini (S5570) !!.
I can remember though that when my phone was on v2.2 about a year ago it was working ok.
small tip:
What you can do instead of pulling the battery out is to press the power button for about 10 seconds ( phone will turn off) release and the press it again for few seconds to start again.
You don`t need to press power again, just keep it pressed until you see the samsung bootlogo.
Mine has started to blackout too, maybe it`s related to some installed software. It worked ok still few months ago. My galaxy mini is working ok tho, has only few market apps installed.
Sent from my GT-I9000 using Tapatalk
poyda69 said:
Has anyone had this issue?
I have tried a few different ROM's and have had this problem on all, the phone will work but sometimes when the phone is locked and asleep you cannot get the screen back.
If you ring the phone it will ring but you can't wake the phone up (the screen is off).
If I then pull the battery and reboot all is well until the next time, which is random.
I will remove all my programs to see if there is one of them causing the issue, I don't believe it is the rom as it has happened on a few of them.
Click to expand...
Click to collapse
The bug is called SOD (Sleep of Death). Apparently a Gingerbread only bug (I think deep sleep was introduced in Gingerbread).
Your phone is going into deep sleep, and can't be woken agian.
I don't know if there is a fix for it, but you could try search for SOD on these forum pages.
Herman76 said:
The bug is called SOD (Sleep of Death). Apparently a Gingerbread only bug (I think deep sleep was introduced in Gingerbread).
Your phone is going into deep sleep, and can't be woken agian.
I don't know if there is a fix for it, but you could try search for SOD on these forum pages.
Click to expand...
Click to collapse
i had this issue on cm7 with neo kernel, but sometimes it responded after some time
i think its black magic made by apple and will kill our cats
As Herman76 said, this is the SOD, I used to get them quite frequently. I created a thread with a possible workaround. So far haven't got any new SODs.
I can't put my finger on this issue I've been having with my Note.
Don't get me wrong, this device is a godsend!
The problem I've been having is that sometimes when I take my Note out of my pocket and try to press the unlock or menu button it doesn't show anything on the screen. I've read about people having issues with delay before it pops up, but it doesn't pop up even after 10 seconds or a minute, it feels like the device 'hangs' or doesn't want to wake up. The only way I can turn the phone on again is by pressing the unlock button for like 10 seconds and the phone reboots.
I thought it was a problem with Green Power, I thought it maybe had issues turning off the wifi or data when the screen was locked and that the service would cause the OS to crash or 'hang'. When I look at my battery history after the reboot it shows that I lost a significant amount of battery (5-15%, depending on how long it took for me to 'discover' the crash) and there's a 'jump' in the graph.
Things I've tried:
Stock rom - problem persists
Different kernels - tried all the kernels available in the market including stock, problem persists
Add a bit of paper between back-cover and battery (to make sure it doesn't lose contact)
Checked if there was dust between battery connections
Tried different sim card
Tried disabling wifi and data all day (mysteriously persists)
DIfferent governors (ondemand and interactive) (the phone reverts to default governor after the forced reboot, normal? i have my phone set to interactive on boot, but somehow it skips that after the forced reboot)
I've attached a picture of the battery graph. According to the stats there's a 25 minute gap where the phone was 'stuck' and you can see that the screen was on and active for that duration.
There are NO funny apps running in the background, this is is a clean install with some standard Samsung apps frozen.
tl;dr version: phone randomly won't wake up; battery loss after forced reboot;
I might have found the issue myself. Now when I come to think of it, I think it always occurs after I've been in my car for like a 30 min drive... Maybe the phone is having trouble switching networks? Anyone know what might be causing this?
Or better yet, how can I research this issue? Can I enable some logging somewhere to track this?
I had the note for about 10 days and today, about 1 hour ago it happened to me for the first time. I tried the home button to wake the screen but nothing, tried the power , nothing and holding the power but nothing happened. I had to pull the battery.
I had this problem in the beginning, but no more.
It's one of two things, in my case. Restoring apps (with data) from Titaium backup, or SetCPU or both. Do a factory reset, reinstall apps without data. If using setCPU, disable it for a while to see if it happens again. It's been over a week and the problem is gone.
tamarian said:
I had this problem in the beginning, but no more.
It's one of two things, in my case. Restoring apps (with data) from Titaium backup, or SetCPU or both. Do a factory reset, reinstall apps without data. If using setCPU, disable it for a while to see if it happens again. It's been over a week and the problem is gone.
Click to expand...
Click to collapse
I was using System Tuner instead of SetCPU to freeze apps and change governor, maybe I've just been using the wrong app? I deleted it just in case. Will see if the problem persists, thanks!
The nasty thing about it is that it seems to happen randomly (but it most likely doesn't) and is pretty rare (happens once every 3 days).
Still, I don't like the fact of not being available for X amount of time, even if it's 30 minutes.
I'm on stock room and unrooted. Like I said first time it's happened.
i've had the GNote since 4 days now , and yesterday same thing happened as the device was in my pocket and i couldnt wake it up at all , battery pull solved it.
im on stock , non rooted
I can't believe that we are the only ones with this issue. Anyone else? OR better yet, how did you resolve it?
Dont know if this is the same issue as the streak had, but with the streak if you kept it your pocket with the screen facing your body this would sometimes happen. Flipping it so that it that the screen doesnt face your body in your pocket solved this issue.
kirkla79 said:
Dont know if this is the same issue as the streak had, but with the streak if you kept it your pocket with the screen facing your body this would sometimes happen. Flipping it so that it that the screen doesnt face your body in your pocket solved this issue.
Click to expand...
Click to collapse
Thanks for your reply. I did some research, and apparently it had to do with static being built up in the screen from wearing it towards your body in your pocket.
This issue was that you couldn't swipe the lockscreen cause the touch screen wouldn't respond. The problem we are having is that the screen won't even turn on and that the system locks up.
Same issue here with my 2 days old Galaxy Note, that's how I found this forum. In my case it went from not waking up occasionally to every time WIFI was ON (I did some experimenting with settings to see which one could be the one causing the problem). But then...occasionally it would not wake up even with WIFI OFF: very annoying. And this is my first Android, so I didn't have any custom anything, pretty much same as out of the box when I got it The only solution was to reset the handset. And definitely has nothing to do with having it in my pocket as I don't carry it in my pocket. Rang Samsung, they told me it was faulty, I returned it. Now I'm concern the next one is going to have screen issues? As so many people complain in this forum? we'll see.
My issues have been resolved after flashing AbyssNote 1.4 and when I stopped using System Tuner. I've started using Voltage Control instead and now I'm not even having problem @ 100Mhz undervolted 50mV from stock.
Same problem with my wife's Gnote, totally stock, just a small handful of apps installed. Happened twice, about a week apart.
She does a lot of travelling, maybe you're right about that. But it happens after she gets home when it's still OK.
Had the same same issue twice in two days and had to do a battery pull, just did a master reset and re -installed the applications manually, so far so go.
YOu guys think its a hardware or a software issue?
Hmm.. Happened to me too about three times in the last two weeks. I am on stock rom but rooted, and running Green Power. Hopefully samsung will fix it in the next updates. Seems like a software bug to me. Maybe not enough juice when in deep sleep?
metus666 said:
I was using System Tuner instead of SetCPU to freeze apps and change governor, maybe I've just been using the wrong app? I deleted it just in case. Will see if the problem persists, thanks!
The nasty thing about it is that it seems to happen randomly (but it most likely doesn't) and is pretty rare (happens once every 3 days).
Still, I don't like the fact of not being available for X amount of time, even if it's 30 minutes.
Click to expand...
Click to collapse
Hello
its the problem of your kernel. try Abyys 1.4 and use XDA Superpower to adjust the CPU-Frequency automatically
neunzehn77 said:
Hello
its the problem of your kernel. try Abyys 1.4 and use XDA Superpower to adjust the CPU-Frequency automatically
Click to expand...
Click to collapse
problem is it also happens on stock rom.
mfractal said:
problem is it also happens on stock rom.
Click to expand...
Click to collapse
It's very well possible that the stock kernel has faulty settings for the CPU. Haven't had the problem again with AbyssNote 1.4 and Voltage Control (even with custom cpu frequencies)
I just got my note today.
Battery in, turnt it on a few mins playing around.... the problem started
and hasnt since stopped...
Anyone tried contacting samsung about this?
software fix or hardware issue ??
qazkamakazi said:
I just got my note today.
Battery in, turnt it on a few mins playing around.... the problem started
and hasnt since stopped...
Anyone tried contacting samsung about this?
software fix or hardware issue ??
Click to expand...
Click to collapse
at this point we're just guessing, there haven't been any official confirmations of the problem as far as i know.
But if it's so accute that it keeps happening all the time you must have a faulty device.. call samsung ?
I'll try to keep this brief. Earlier tonight I downloaded the Nova Launcher on the google play store. It worked fine, I set it up how I wanted, etc etc. Well I went to looking for an app to replace the circles app on stock ICS. I found an app called "Fancy Widgets" and downloaded it. Practically as soon as it finished downloading my phone rebooted. I thought, maybe, it just needed to reboot for the app to take effect. I had to do that with a previous phone.
But no, Now my phone is just in a constant loop of boot and load to the home screen, wait 10-20 seconds and reboot. It just keeps going through this over and over so basically my phone is useless at the moment.
Does anyone know how to help this? I'm lost. If I can't get it figured out I'm going to have to stay up all night trying to figure it out because my phone is my alarm clock and I'll oversleep otherwise. So.. Please help!! Thanks!
Parham112 said:
I'll try to keep this brief. Earlier tonight I downloaded the Nova Launcher on the google play store. It worked fine, I set it up how I wanted, etc etc. Well I went to looking for an app to replace the circles app on stock ICS. I found an app called "Fancy Widgets" and downloaded it. Practically as soon as it finished downloading my phone rebooted. I thought, maybe, it just needed to reboot for the app to take effect. I had to do that with a previous phone.
But no, Now my phone is just in a constant loop of boot and load to the home screen, wait 10-20 seconds and reboot. It just keeps going through this over and over so basically my phone is useless at the moment.
Does anyone know how to help this? I'm lost. If I can't get it figured out I'm going to have to stay up all night trying to figure it out because my phone is my alarm clock and I'll oversleep otherwise. So.. Please help!! Thanks!
Click to expand...
Click to collapse
Already tried power and volume down button (6 sec)?
Good news is the att sound works as a good alarm. I found out when mine did that. Restart in safe mode by holding down power and volume rocker then do a factory reset.
Sent from my MB886 using xda app-developers app
funny, I've had nova launcher working with fancy widgets when i updated my phone and it went into a reboot loop. it only happened to me when i updated the phone though
My first Atrix HD rebooted itself daily, sometimes bootlooping and causing me a lot of grief. The phone was fine for the first two days. After that, it went haywire. I would run logcats to try to determine the causes of the bootloops. I always found an error with some random app. I'd uninstall it and the phone would be fine for awhile. Eventually, I came to the conclusion that a problem with the wifi radio was the underlying cause. If not, the wifi problem and reboots were co-morbid, so to speak, and related to the same problem. I was pretty sure the real problem had to do with faulty hardware. I exchanged the phone for another. I've had this one for three days now and it just rebooted itself about 15 minutes ago. That bugs me.
I like the phone, but I think there may be an unusually high number of defective units out there. That's based solely on anecdotal information, but I believe it to be true. If anyone has any additional theories or has an explanation for these reboots, that would be a great help to me.
McEwen.
McEwen said:
My first Atrix HD rebooted itself daily, sometimes bootlooping and causing me a lot of grief. The phone was fine for the first two days. After that, it went haywire. I would run logcats to try to determine the causes of the bootloops. I always found an error with some random app. I'd uninstall it and the phone would be fine for awhile. Eventually, I came to the conclusion that a problem with the wifi radio was the underlying cause. If not, the wifi problem and reboots were co-morbid, so to speak, and related to the same problem. I was pretty sure the real problem had to do with faulty hardware. I exchanged the phone for another. I've had this one for three days now and it just rebooted itself about 15 minutes ago. That bugs me.
I like the phone, but I think there may be an unusually high number of defective units out there. That's based solely on anecdotal information, but I believe it to be true. If anyone has any additional theories or has an explanation for these reboots, that would be a great help to me.
McEwen.
Click to expand...
Click to collapse
Yeah, I wish someone knew what the problem was. After I posted this originally at the beginning of October, I deleted Fancy Widgets and didn't have any more problems with boot loop until this week. I blamed it on my two newest apps and un-installed them, but the problem is there somewhere and I randomly reboot after installing Nova back.
This really bothers me. I had just gotten used to how I had everything set up in Nova. The stock launcher is disappointing in comparison now that I've experienced something better.
Parham112 said:
Yeah, I wish someone knew what the problem was. After I posted this originally at the beginning of October, I deleted Fancy Widgets and didn't have any more problems with boot loop until this week. I blamed it on my two newest apps and un-installed them, but the problem is there somewhere and I randomly reboot after installing Nova back.
This really bothers me. I had just gotten used to how I had everything set up in Nova. The stock launcher is disappointing in comparison now that I've experienced something better.
Click to expand...
Click to collapse
Replying to myself, but yeah..
It now looks like my issue has something to do with DoubleTwist music player. Nova worked until I tried to put a DoubleTwist widget on my homescreen and it IMMEDIATELY went into boot loop.
So I've had my S3 mini for over 10 months now and I've been flashing ROMs on it (mainly Maclaw's ROMs). Then one day, suddenly while I was playing music the phone just shut off. When I turned it back on, all these green squares were flickering in the boot screen and whenever I tried to play music again, there would be like audio crackling or some kind of static and then crash, turn off and perform a bootloop. I took battery and turned it on and whenever I opened an app, it would load the app and after 5-10 seconds it would just close.
So I decided to flash the stock firmware via odin. After flashing it worked normally for like 30 minutes or so, then the problem started. Although the green screen flickers on the boot animation were gone, the audio problem and app crashes and random reboots are still happening.
I don't know if this is a hardware problem or a software problem. If it is a software problem, can anyone help me?