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.
Related
Hey guys, my nookcolor has been randomly rebooting since i rooted it. Never while i was using it, i just sometimes hear the bootup sound, and look to find that my book is now on.
Im just concerned this will affect my battery, and i also don't want it rebooting while im using it.
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Divine_Madcat said:
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Click to expand...
Click to collapse
I still want to use the B&N stuff. Any rom that emits them, I will not be installing.
I think it likely that there are NC users in both camps-
Those who want the B&N stuff and those who don't.
I am one of those who don't; the Nook for Android software does better for reading ePub, imo and I am rarely near a B&N store.
Right now we have root and Market plus B&N and I would guess (could easily be wrong) that the first custom roms will be pure Android with no B&N.
We will probably end up with an option to set while flashing: retain B&N customizations or straight Android.
I base this guess on what I have seen in the other roms for various devices (mainly Droid) I have looked at.
Same here. If I want to read B&N books, I could still use their Android app on a custom ROM.
After switching to Cyanogen on my phone, it's been quite relaxing to not have to worry about provider updates bricking the thing or otherwise screwing up the rooted customizations (or just randomly resetting the thing back to factory defaults because I started up one of their apps and it got confused). Not to mention that the CM team does a far better job supporting the device than the manufacturer and my service provider does.
And yes, like other Android devices, there will probably be ROMs in both categories: completely built from scratch with no B&N portions at all, and improvements on the B&N system to add more functionality.
Fair enough for those that are interested in the reader portions - i have to admit, i bought this as a tablet, with literally 0% in it as an e-reader; i already have a Sony 505 for that. I may use it on occasion, but only as an afterthought.
However, this topic is really drifting - perhaps we should just bring it back to the rebooting issue?
Yeah, I installed the Uptime Widget on my NC today and picked it up a few ago and its uptime was 1:30; max 15h (from before it rebooted 90 minutes ago). I'll keep running it.
What we need to do is get a logcat when it happens.. So maybe overnight I'll leave it running or something. It just rebooted on me and I was semi-watching it, didn't even notice but Uptime Widget was reset to 7m up, 15:30 max..
I have started up a logcat and I'm going to leave it running while I get ready to go out for the day.. Although I just installed and fiddled with Google Earth, which failed badly, so I wonder if it caused some problem. Also saw it happen after playing with Google Maps, so I wonder about Location stuff maybe doing it.. Dunno. I just launched Maps a few ago and it's been up since. Hopefully a logcat will capture some info.
I have noticed that I've seen some crashes that don't show the Crash dialog.... TweetDeck is particularly bad about crashing viewing some Facebook posts, and in this case it just goes black for half a second then back to the list of posts. A logcat shows it crashed. But I don't know the two are related (not having the crash dialog stuff and the reboots that is).
I had it reboot on me twice last night, one time I didn't know about it until I picked it up later and noticed the uptime widget was down to some 30 minutes, and another time right before bed I hit the power button and about 10s later I saw the boot up text and a reboot happen.
Still haven't caught it on logcat.
My doesn't reboot spontaneously, but it does "lock up" and won't turn on with the power button from standby occasionally. If I remember to use the Nook Button to wake from standby, I don't seem to have this issue. If I use the power button, and it won't wake, I need to hold it down for ~15 seconds and it reboots.
AFIAK, it has done this since I purchased it (I rooted after about 1 hour with the NC in my hands).
Mine has never reboot WHILE I'm using it, it's sneaky about it. But I suppose I'd much prefer it reboot while I'm not using it than while I'm using it; I have yet to have it do a full reboot while using it.
Trying to set up a Delicious account.. yeah, that rebooted the Java VM. But only time I've made it reboot at all.
Hahah, damnit, it just rebooted after it went to sleep. I seriously think it has something to do with going to sleep. I've been sleeping it and waking it repeatedly on adb logcat and it won't crash. Figures.
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
isolated_epidemic said:
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
Click to expand...
Click to collapse
Actually not using any of those on mine.. I have Beautiful Widgets in ADW and Beautiful Widgets + Note Widget in WidgetLocker.. Not adjusting the backlight at all either, in fact I don't think I have at all since getting it now that I think about it.
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
mastroiani said:
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
Click to expand...
Click to collapse
I suspect it's a software thing, as it doesn't randomly reboot in use, it ONLY seems to happen going into standby, and I have YET to make it happen connected USB for adb.
You know actually, I think alogcat can log automatically now, maybe I should try that.. but it'd have to run for a day or so, as I only see this happen like twice a day at most.
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
wvcachi said:
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
Click to expand...
Click to collapse
I myself had not played with SetCPU at all. So had you in the past and set it to conservative, and switched it back, or you switched it from its defaults? Reminds me, per my observation that it never has rebooted while on AC or USB, was there a default profile when plugged in that it's set to ondemand vs conservative? This could start making some weird kind of sense. I'll try it, but using something called CPU Tuner since it's free..
EDIT: I looked on USB and on Battery, both times was conservative, so looks like that's the default... Does the Nook have an automatic switching utility like cpuspeed in it? Hmm.. /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor is the file if anyone else wants to look.
BTW, has anyone on 1.0.1 auto-nooted etc not seen these random sneaky ninja power-off reboots? I swear mine waits until I'm not looking and reboots. I've only SEEN it do it once or twice, but in the last 5 or so days it's rebooted at least 10 times while powered off. Again NEVER while I'm using it, so I'm at least thankful for that. If it were rebooting while using it that would not be acceptable.
I have the Uptime Widget, kinda wished I had an uptime graph to see if there is a pattern.. I'm about 99% sure it never happens when plugged in AC or USB.
EDIT2: IT IS CLEARLY MOCKING ME. It just rebooted after I peeked at the governor files and let it idle to sleep.
I have the same random reboot problem since I upgraded to 1.0.1 and used auto-nooter. I only see it when it goes to sleep...or so I thought. This morning I heard it reboot and i hadn't touched it since last night. FYI, it was not plugged in when it happened. Thankfully it never reboots while in use.
Oh...ad i havent used any CPU clocking tools. Also...never saw this on 1.0. So weird but I am sure someone smarter than I will figure it out.
UPDATE- Just got out of the shower and while getting dresses...heard the Book reboot twice within a minute or two.
Wondering if its an app that is causing a fatal crash when it tries to update.
Sent from my Nooxus One using Tapatalk
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
rckymtnrfc said:
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
Click to expand...
Click to collapse
I've had one unexpected reboot today that I know of, I think this has helped, although I keep finding my Wifi turned off, even though this program I installed is only set to turn it off when the battery is extremely low. So I changed that profile and it hasn't turned itself off since, so seems to me maybe the battery reporting is a little wonky sometimes.
I've been watching, and I'll keep an eye out, but I think wvcachi is onto something.
BTW, the Nook has been primarily idle for the last 5 hours, just popped it on a few times to read an email, check on something, or see if it reboots so I haven't used it a bunch but it's lost a whopping 2% battery in that time. I also disabled the Phone stuff too, per this thread:
http://forum.xda-developers.com/showthread.php?t=883908
I am at 6.5 hours now....no rebooting so far.
Sent from my Nooxus One using Tapatalk
Hi, with stock 2.2.1, I experience phone having blackscreen. How it happen. I press on the wake button, nothing happen. Press again, the phone wake, and sleep... lol. I have no problem in auto reboot and shut down, only this problem...
Anyone face this too?
Sent from my LG-P990 using XDA Premium App
Isn't this the BSOD everyone always goes on about?
Apparently it happens to a lot of people.
Meltus said:
Isn't this the BSOD everyone always goes on about?
Apparently it happens to a lot of people.
Click to expand...
Click to collapse
Is it? i thought everybody was experiencing reboot and shut down...
xxdoggyxx said:
Hi, with stock 2.2.1, I experience phone having blackscreen. How it happen. I press on the wake button, nothing happen. Press again, the phone wake, and sleep... lol. I have no problem in auto reboot and shut down, only this problem...
Anyone face this too?
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
i also had this problem with Stock ROM when i bought my phone, 2 hrs later i flashed MCR ROM - no problem anymore
How come you have 2.2.1??? update to 2.2.2...
Sent from my LG-P990 using XDA App
xmoo said:
How come you have 2.2.1??? update to 2.2.2...
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
No idea... I bought my phone at the earlier earlier batch, where it is pack in bubblewrap... LOL!
Anyway, at 2.2.2, still same problem. Doesn't want to get custom rom, as after my exam, i'm going down to LG and get some servicing or shyt out from them...
The problem exist especially when you are charging. It occur also when you put your phone to sleep while running on GPS. Very fedup with it.
It is categorized in Freeze and Reboot Problem
It's the first stage of that problem, if you continue using it, you will suffer the reboot problem
xxdoggyxx said:
Hi, with stock 2.2.1, I experience phone having blackscreen. How it happen. I press on the wake button, nothing happen. Press again, the phone wake, and sleep... lol. I have no problem in auto reboot and shut down, only this problem...
Anyone face this too?
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
Sorry to hear that for you but, it happens to a lot of us the Freeze called BSOD (Black screen of Death)
Welcome to the happy LG owners club called BSOD...
also known as sleep of death
Welcome to join BSOD.
Sent from my LG-P990 using XDA App
Oh. BSOD. Haha
Maybe you just can change the rom and wait LG update.
Sent from my LG-P990 using XDA App
black screen on wake up after sleep... lcd display hardware fault
i have two optimus 2x
one works perfectly ,The second has this problem ..when the light goes out and pressed the power button to wake up screen is black... can see only light
i open both and i change motherboard between them
the problem remained at the same display whit the other motherboard from the one who work perfectly
conclusion...i ordered another lcd
ali_alex said:
i have two optimus 2x
one works perfectly ,The second has this problem ..when the light goes out and pressed the power button to wake up screen is black... can see only light
i open both and i change motherboard between them
the problem remained at the same display whit the other motherboard from the one who work perfectly
conclusion...i ordered another lcd
Click to expand...
Click to collapse
Damn you crazy!
I had this issues once. Never after.
xmoo said:
Damn you crazy!
I had this issues once. Never after.
Click to expand...
Click to collapse
i had this issue after flashed mcr rc17 never before,in the first time i belive that this rom has the issue but ...flased back to stock and the problem remain the same,tried different 11 stock rom and no way !
after i make the change !
i have still the original dual and have all of the reportet problems.
Reboot, Shut down and Black screen
net
solution to some bsod models. Tested, working!
Many p990 bsod models have faulty soldering of some sort. A solution which have worked for many is to simply plug in your charger. When your phone goes to sleep and doesnt wake up when you hit the power button, just leave it be for 12+ hours. Place your phone on something soft as well, like your bed. This will heat up the device and fix the faulty soldering. If it does not work, try longer period of charging. Good luck. (I will take no responsibility if this does not work as planned)
This was tried on a bsod model which went to unresponsive sleep every 5-30 minutes. After this procedure it was faultless
killacan said:
Many p990 bsod models have faulty soldering of some sort. A solution which have worked for many is to simply plug in your charger. When your phone goes to sleep and doesnt wake up when you hit the power button, just leave it be for 12+ hours. Place your phone on something soft as well, like your bed. This will heat up the device and fix the faulty soldering. If it does not work, try longer period of charging. Good luck. (I will take no responsibility if this does not work as planned)
This was tried on a bsod model which went to unresponsive sleep every 5-30 minutes. After this procedure it was faultless
Click to expand...
Click to collapse
Lol... Solder have melting point of at least 90℃. I don't wanna melt my phone..
Sent from my Optimus 2X using XDA Premium App
have u tried not to sleep your device when charge?? settings->applications->development->stay awake
I've had my LG for quite some time now and I still trying to figure it out. So, if you're patient enough, please, just bare with me for a while as I explain what I've tried so far what what were the results.
A lot of people complains about this phone... unstable, crashes, reboots, BSOD, etc...
The first problem I had, came with the stock ROM... after a while the Wi-Fi just stopped working and it would display "Error..." as a message. The only solution was to reboot. 3 or 4 days after I had bought it, this was already killing me... so I started trying other ROMs but all seemed to suffer from some sort of problem except for one (see phone info below), which I've been running since June and I find it impeccably stable I can basically keep my phone running for as long as I want, as long as the battery doesn't run out (obviously), which brings me to a second point... battery drain!!
The battery drain was the only problem I didn't manage to find a solution for... and after a certain while, even though my phone was stable, having to charge my phone every single day was becoming very annoying.
Since I live in a different country than my GSM operator, it doesn't come as a news flash that network look-up has a big impact on the battery life, specially because I live close enough to the border to be able to keep the signal but in some parts of my house the signal is lost forcing the phone to search for a new network, which sometimes it finds (roaming) and sometimes it comes back to the original network and so on... However, what I find, unarguably, to have the biggest impact on the battery is having the Wi-fi enabled when there's no available network, it's just huge, it can suck up the battery in a few hours...
So, I decided to try some of those power management apps such as Locale, Green Power and some other, in order to minimize these problems, but curiously, they all caused the same problem... BSOD within a matter of minutes. I installed the app, configured it, waited for the phone to go into sleep and puff... it was gone. The only way out of it was removing the battery. I uninstalled the app, and the phone was stable again... this happened with every single app of the kind, that I have tried.
At the moment my phone is as stable as it gets but if I don't pay it enough attention, the battery dies in a blink of an eye.
Model number: LG-P990
Android version: 2.2.2
Baseband version: 1035.21_20110614
Kernel version: 2.6.32.28-mck-r14-ocuv
Build number: FRG83G
LGE version: 19/5-11 MoDaCo FR17 Fear Edition 10
Any suggestions will be more than welcome.
Cheers!
Hey guys,
ever since I used CM7 on my Galaxy it puts the WIFI in sleep mode as soon as i turn the screen off. I've set the sleep policy to never but yet it slows the datarate down first and then some seconds later it is stuck at 0 kb/s. That's very annoying especially if you download some bigger files. Is that a known bug on CM7 or is it just me?
Come on, i am the only one with that problem? :/
I don't have this problem, download continues even if the screen is locked...
Sent from my GT-I9000 using XDA Premium App
When I was using CM7 a while back I had this same issue. Had to make sure screen was on all the time. This and some other small issues made me switch back to Darky's ROM which lags like crazy, but at least has good battery life and is stable.
Are you sure? Even same speed as with screen turned on? How in the blue does it work for you? I've had this issue on every nightly so far
Ever tried another modem/kernel?
Sent from my GT-I9000 using XDA Premium App
Try this:
https://market.android.com/details?id=com.shantz.wifikeepalive&feature=search_result
I've tried several modems. Currently i'm on JVQ... As kernel I only tried Fugumod so far... but i seems like it works for others :/
@mobidzid
I've tried this and other apps who keep connection alive, but they have no effect at all for me :/
I have the opposite for MIUI rom.
The MIUI rom by default set the WIFI in sleep mode as soon as the screen is turned off. However, from the battery history, the WIFI never go to sleep. Is this a problem with MIUI rom or there are other setting required?
Nothing new on this? It really drives me crazy here
Please delete, I wrote into the wrong thread... :O
worly said:
Hey guys,
ever since I used CM7 on my Galaxy it puts the WIFI in sleep mode as soon as i turn the screen off. I've set the sleep policy to never but yet it slows the datarate down first and then some seconds later it is stuck at 0 kb/s. That's very annoying especially if you download some bigger files. Is that a known bug on CM7 or is it just me?
Click to expand...
Click to collapse
I have same problem?! If anyone solved problem?
Have anyone other than me experienced that the phone suddenly is turned of? It's not the BSOD or reboot, but just turned off and can be turned on right away..
I've saw it yesterday when it was in my pocket, and this morning when i woke up.
I'm using the CM7 RC1 ROM straight from the box.
Yes. I get this to... (With every build of CM that is)
Same happens to me also with the latest CM7.
Me and my brother also get this, started with cm7 57 I think
Sent from my Optimus 2X using Tapatalk
Does anyone know how to use ADB to log? Then we could maybe capture some logs when this happens and post to aremcee to see if he can help us..
The same thing has happend to me 2 times in the week a have had this replacement device. It's worse than the one I traded this one for
But I'm on stock havn't rooted or anything.
Just had a BSOD aswell.. Gotta hate this phone. It's works on stock so I can't send it to my dealer and get my money back
Install a Froyo Rom
Profit.
My findings on the CM7 sod (sleep of death) issue (I post this here, as I don't have enough posts to post it to dev area):
I've been using CM7 occasionally since the first nightly. About 2 months ago I suddenly had 3 sods in 2 days. This was after I bought JuiceDefender Ultimate. In JD I had sync enabled once per hour, and JD set to first try to connect to wifi and then mobile data. In Android wifi settings I had wifi sleep policy set to "when screen turns off".
After I set JD to use only mobile data on sync events, and turned wifi sleep policy to "never", I haven't had a single sod since. If I remember correctly, I once managed to induce a sod by turning wifi on or off (can't remember which) through the power control widget, and immediately after that I turned the screen off normally by pressing the power button (while wifi was "dimmed" in the power control widget meaning it was changing it's state).
So I strongly believe that my sods were caused by the combination of turning wifi on or off (either through widget or JD doing it) and turning the screen off at the same time. I didn't experiment any more, since I found my solution above.
I wrote this here, because people try hard to hunt down what's causing the sods, and I wanted to share my thoughts. If it is of no help, then sorry.
it happens sometime... don't trust your phone's alarm to wake up. you could have bad surprise (just had the experience 2 days ago) :'(
i am running cm7 no. 165. and vork kernel clocked to 1504 no reboots or black out issues. i also have green power managing my network data only... good luck all... just remember that cm7 is still nightly and is not considered stable.
Hi, I'm about to get one LG, but I've had the same issue with an Orange Boston mobile with a 2.3.5 CM7. I disabled Wi-Fi sleep too and it seems to help.
Before the scren weirdly shut down and the phone rebooted.
Hmm might try this out and see if it works.
I can't seem to get this issues myself. I will try and test this later on my other phone.
That is the reason why I don`t use CM7 anymore ...
Moderator Message
Extensive discussion going on here >
http://forum.xda-developers.com/showthread.php?t=997705
THREAD CLOSED
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.