[Q] Wierd problem when turning screen off and on - One (M7) Q&A, Help & Troubleshooting

Hey guys, im having a bit of a problem. My phone is shuting off on itself.
Everytime i turn it on, it boots up no problem, but when i hit the power button to turn the screen off, when i want to turn the screen on again by pressing the power button, the screen just goes deep blue, and turns off.
I haven't change anything on it for quite a few months now, so i'm not sure why this is happening. Im on Viper 3.5 i think or 3.7, using faux123 kernel, dont remember which version, but an old one with which i never had any troubles... rooted, s-on
Any ideas?
Thanks!
Coldsun15
PD: Logcat in the .rar file...was too big for .txt

Really?? No one??
Well, just for further info... my phone appeared to fix itself, since it stopped doing that weird thing for a couple of days, but now is back... nothing ever changed, no new apps, or settings or anything...
Any ideas welcome
Edit: Attaching new logcats...

coldsun15 said:
Well, just for further info... my phone appeared to fix itself, since it stopped doing that weird thing for a couple of days, but now is back... nothing ever changed, no new apps, or settings or anything...
Click to expand...
Click to collapse
I think your power button is broken (or you may have a related hardware issue). Nothing but a root app can reboot the phone, and I've never seen that happen by accident.

fenstre said:
I think your power button is broken (or you may have a related hardware issue). Nothing but a root app can reboot the phone, and I've never seen that happen by accident.
Click to expand...
Click to collapse
Yeah, i thought about it being hardware but something is off... i mean, if it where the power button, then i shouldnt be able to turn it on easily, or it wouldnt turn off the screen properly, nor would it just start working alright for a couple of days... plus, it didnt recieve any hits or anything during, before or after the problem.
I also thought it could be the screen, but when its on, it works perfectly, as on the first day...
But yeah, I'm not taking hardware problem out of the table...just seems unlikely to me...
Thanks for your answer!
Coldsun15
Edit: also, I just found out it doesnt actually restart...screen just turns dark blue, then it powers the screen off and it wont turn on when pressing power... but i know its on, because i can still hear notification sounds of incoming messages...
Edit2: Just tried same but instead of using power button, i used logo2sleep and home2wake kernel options, and did the on/off with them, and same result...dark blue screen then off and not turning on... so it cant be power button

Related

Power Button- slow?

i noticed recently that if i press the power button, it sometimes takes a really long time to turn the screen on. i know the hardware works because the backlight in the soft buttons turns on immediately, but the screen remains black for up to 10 seconds. this happens rarely. however, im fairly sure it isnt a software problem because ive wiped completely and installed a fresh rom and the problem seems to persist. perhaps i just recently noticed, and the problem was always there? does anyone else have this problem?
three threads above yours.
http://forum.xda-developers.com/showthread.php?t=681723
could be a hardware issue.
Mine does this every few days.. I am still on the stock 2.1 rom.
Mine also does this, I only noticed it after flashing Cyanogenmod 5.0.6. so I thought it might have been a bug. I also assumed it was a bug because the phone seems to act strangely when you are touching the screen and try to hit the power button.
Hopefully this isn't a hardware issue, I've had the phone since release.
Is anyone else experiencing similar issues?
It happens to me as well, but very infrequently. Maybe every few days... so it doesn't bother me enough to worry about it.
I'm on stock ROM btw.
I am leaning towards thinking this may be software related. A few minutes ago I was at the lock screen and tried about 50 times (yes I waited long enough after each press) and simply could not get the screen to turn off. I then tried long pressing the power button and, sure enough, each time it would bring up the shutdown menu (yes, over the lock screen). Must be a bug right?
Hmm, my problem's slightly different. Around half of the time, I have to press the power button twice to turn the screen on. Sometimes, pressing it the first time doesn't turn the screen on, had to press the power button firmly again.
This started only recently. On stock n1 and bought it during feb.
that means that your power button is dying, like many others' (including mine)
this is the first time, it takes 2 clicks to work....than it will increase.
Expect a repair soon...
Well i am having the issue other way around. i am not been able to put my phone in stand by mode by clicking on it and it is do a hard press then i get options to shut off the phone
any suggestions what might be causing it ?
I'm happy I haven't received this problem yet
-------------------------------------
i want my yogurt lol froyo time
negroplasty said:
Mine also does this, I only noticed it after flashing Cyanogenmod 5.0.6. so I thought it might have been a bug. I also assumed it was a bug because the phone seems to act strangely when you are touching the screen and try to hit the power button.
Hopefully this isn't a hardware issue, I've had the phone since release.
Is anyone else experiencing similar issues?
Click to expand...
Click to collapse
I am having the same issue and i wonder if you were able to find the cause for it. I have the same rom as you do on your phone
negroplasty said:
I am leaning towards thinking this may be software related. A few minutes ago I was at the lock screen and tried about 50 times (yes I waited long enough after each press) and simply could not get the screen to turn off. I then tried long pressing the power button and, sure enough, each time it would bring up the shutdown menu (yes, over the lock screen). Must be a bug right?
Click to expand...
Click to collapse
I have a similar problem. When I unplug the N1 from the charger, the screen comes on showing the lock screen, and I can't get it to turn off. If I unlock the phone, however, then the power button works normally. I don't think it was doing this until recently (I bought it in January the first day it was offered and am running the stock update1 ROM).
So here is my theory if the power button is a problem then it needs to act up both ways and not only one way. right now i can put the phone in sleep mode but i can wake it up. i will post the issues on the development forum and might be able to find an asnswer to it
So seems like the issues is because of Cyanogenmod 5.0.6 because since i have flashed another rom it is working just fine. i will be doing some more testing before i can be certain
Another problem I am experiencing is when I long press the power button, it pulls up the phone options menu but also turns off the screen. It's extremely frustrating as it does this quite frequently; right after I power on the screen again and unlock the device it works properly every time - so much so that I am convinced this is a software issue.
I am now running froyo, rooted with Cyan's minor root patch. I can also say for sure I experienced the same problem on CM 5.0.6, but it definitely occurred less frequently.
Am I alone here?
di2356 said:
i noticed recently that if i press the power button, it sometimes takes a really long time to turn the screen on. i know the hardware works because the backlight in the soft buttons turns on immediately, but the screen remains black for up to 10 seconds. this happens rarely. however, im fairly sure it isnt a software problem because ive wiped completely and installed a fresh rom and the problem seems to persist. perhaps i just recently noticed, and the problem was always there? does anyone else have this problem?
Click to expand...
Click to collapse
I just started having this problem after upgrading to 2.2.
I have this every so often. But sometimes wonder if it is flyscreen doing it
You guys should all just be running the app no lock to take the power autumn out of the equation.
Ahhhhh! I just need trackball wakeup!
I have a similar issue where my screen will turn on but will be unresponsive. When i turn it on and off, the backlight jut comes and goes. If it times out it won't turn back on for a bit(the backlight will come on still).
I just wiped my phone, hoping that'll fix it since it only started happening on a regular basis since I updated to Froyo

G1 Black screen, Cannot get to bootloader

Hey, I have been given a phone off a friend to fix but it wont turn on. Booting normally, I get a vibration and then the backlight comes on but i cannot see anything. When i try to boot into the bootloader by holding the camera button and powering it on, the backlight comes on but nothing else. I cannot see the bootloader. Under both circumstances, I cannot turn the phone off. I have to pull the battery to turn it off.
Does anyone have any suggestions about a possible fix? Thanks
Havie you tried send when trying to enter bootloader? If it resets then you can still get to bootloader. If not, your friend has soft bricked and only way is to JTAG which takes strong hardware knowledge and steady hands.
-------------------------------------
Sent via the XDA Tapatalk App
ok im having the exact same problem. actually i thought it was a battery problem so i spent 77$ on a 3700 mAh new batter i guess tripple life... and got it yesterday booted gave same problems. black screen where T-Mobile should be yet the rom loads with scribble screen meaning u see part but it looks like the pixels are messed up. so actually decided to resort to what someone told me a Factory Reset so Pressing Camera + Power i got a Black Backlight screen yet wont show... and I cant turn it off without Taking out the Battery this has become a issue after installing cyanogen 5.0.7 T5... since then i Re-rom'd to superbad 1.2.5 same problem screen scribbles and stops im thinking did I fry it i dont even know how to google my problem because its pretty unique it isnt a battery issue its something in the hardware ... or am I wrong please send us some feedback... ill keep this thread in mind
Sorry, what do you mean by 'send'. I am a complete noob when it comes to G1's. I have worked out i can shut off the phone by holding call + menu + end but thats it. I still cannot see anything at all on the screen. I still only get a vibration on boot. How would I know if the boot has been sucessful but i simply cannot see?
Could the flex ribbon cable be nackered?

Nexus one not waking

okay so when my n1 is in sleep, it takes like 3 tries to wake it up. The first time I press the unlock button the unlock screen comes and then goes back to sleep instantly. The second time the lights for the back menu home and search light up and that's it. the third time it works. I'm on froyo. anyone else with this problem?
I have a similar issue.
Sometimes just the capacitive buttons light up and not the screen. I have to make 2 or 3 tries to get it to turn on. Its rare, but its there. It only happened on 2.2.
ok good, me too!
was just looking for this topic.
mine doesnt always turn anything on at all. sometimes the light go on, others nothing. Also trying to turn off the phone is hard as it sleeps straight away with out opening up the power menu.
I have a stock N1, which recently updated to Froyo, with the same problem.
any ideas would be great!
cheers,
lorin.bute said:
I have a similar issue.
Sometimes just the capacitive buttons light up and not the screen. I have to make 2 or 3 tries to get it to turn on. Its rare, but its there. It only happened on 2.2.
Click to expand...
Click to collapse
Also happens on CM 5.0.7.1.
i think it may be a hardware button issue.
I have tried turning mine off (had to pull the battery out) and then to turn it on.
It should turn on readily as it has nothing to do with the OS at that point.
any ideas?
No HW button issue described. HW button works - if it didn't, lights wouldn't go on. It's a wrong reaction on the button, at least that's what OP describes (and me too).
Your N1's power button is dying, it's a known HARDWARE issue. I experienced all of that what you may think a software bug, nut dear friends, prepare to meet HTC or Google for warranty. My N1's power button is dead, I couldn't swap for a new one because I bought it in my country where no official distributor for N1 yet. Sad!
ps: you may try to search for "N1 power button" and see there are more and more reports about this problem.
I've read more than one or two threads on power button issues, and I know what I'm talking about. My power button DOES power up the phone when the battery is taken off the first shot, it DOES wake the phone from standby, it DOES register long presses - there was even one time when a second press was long, and suddenly the screen woke up with power menu, while the first press left it dark with touch button light going on.
Doesn't look even a bit like HW to me. HW would leave the phone dead, non-responsive to touches, or create a loose touch which would translate into several touches - none of those would EVER turn into a phone being on with screen off, and suddenly snapping back to screen on when the SCREEN is touched several times.
Could be your cpu was too busy to accept any inputs.
I have a thread about it here:
http://forum.xda-developers.com/showthread.php?t=692874
Take your time! As for me, I'm using my N1 for 3 months now for the power button to completely dead with everyday use (I didn't use any app to trackball-wake).
As I said, all the things you are yelling I have been through. And I, too, thought it was software problem.
I tried both MCR and Cya with no hope.
Good luck!
ps: One of my friend just told me about his N1's power button issue right after hearing me telling about mine.
This sucks
anyone know where i can buy a new button??
Corrupt SD Card
I had the same issue. I'd press the power button, the bottom four buttons would light up but no screen wake. Only way to get out of it was to pull the battery. It would happen maybe 30-40% of the time. (Nexus One Froyo FRF72)
I think it was due to a corrupt MicroSD card. I recently installed a 32gb card and put some music on it using songbird and possibly didn't safely remove. That's when I started getting issues. Removed the SD card completely and it worked fine. Changed back to the old card and no issues. Then formatted the 32gb and tried again, worked fine. Then I tried to transfer more music, there was an error and I got the same problem. (Cheap ebay card from Hong Kong, that'll teach me).
Anyway, I'd be interested to know if that solved anyone else's problem, because all I see on forums are that it's a faulty power button, but that didn't seem to be the case in my situation.
Cheers,
Dylan
-Witty esoteric statement about science/technology.
Mine is doing kinda the same weird thing but a little different.
When I push the power button the screen comes on but is unresponsive to touch. If I press the power button again the screen dims and then turns off, the home keys light up and then the trackball glows white. The phone then does not respond to the power button for around 10 secs and repeats this behavior 4 or 5 times until it actually starts working correctly and I can swipe my finger to get to the home screen.
It usually does this after being inactive for a period of time, like after sitting overnight.
FRF91
LancherPro Beta 0.6.7.2(maybe the problem?)
jimbobalu said:
Mine is doing kinda the same weird thing but a little different.
When I push the power button the screen comes on but is unresponsive to touch. If I press the power button again the screen dims and then turns off, the home keys light up and then the trackball glows white. The phone then does not respond to the power button for around 10 secs and repeats this behavior 4 or 5 times until it actually starts working correctly and I can swipe my finger to get to the home screen.
It usually does this after being inactive for a period of time, like after sitting overnight.
FRF91
LancherPro Beta 0.6.7.2(maybe the problem?)
Click to expand...
Click to collapse
i have almost the same issue, although mine happened twice when i was on EPE54B but it's been far more common on FRF91
the only difference is my power will continue to turn the back light on and off no matter if the screen has already timed out or not
kobecamp2009 said:
okay so when my n1 is in sleep, it takes like 3 tries to wake it up. The first time I press the unlock button the unlock screen comes and then goes back to sleep instantly. The second time the lights for the back menu home and search light up and that's it. the third time it works. I'm on froyo. anyone else with this problem?
Click to expand...
Click to collapse
I have exactly the same issue. Over in the general forum, there's another thread on this issue. Many, myself included, are reporting that this problem started after the FRF91 update. Can you confirm?
rtx101 said:
Your N1's power button is dying, it's a known HARDWARE issue. I experienced all of that what you may think a software bug, nut dear friends, prepare to meet HTC or Google for warranty. My N1's power button is dead, I couldn't swap for a new one because I bought it in my country where no official distributor for N1 yet. Sad!
ps: you may try to search for "N1 power button" and see there are more and more reports about this problem.
Click to expand...
Click to collapse
Read again carefully. Are you sure your hardware problem was identical to what the OP described? I've noticed a lot of people with obvious hardware problems (i.e., the power button is completely unresponsive) posting on threads like this when they actually have a different problem. It's very confusing.
britoso said:
Could be your cpu was too busy to accept any inputs.
I have a thread about it here:
http://forum.xda-developers.com/showthread.php?t=692874
Click to expand...
Click to collapse
This sounds VERY promising -- thank you britoso!
PS: Are you guys getting the unresponsive unlock slider like britoso describes?
I had this problem when I first flashed CM6 yesterday. Even after wiping and reflashing it was the same. Only way to get out of the black screen was to do a soft reset, power + vol down + trackball. I finally found out that my SD card malfunctioned and was corrupt. I tried reformatting the sd card in an microsd card reader but windows said it could not be reformatted. I finally switched back to another microsd card that was working, wipe and reflashed cm6 and the problem went away. Try backing up all the data on your microsd onto your computer then reformat it and wipe then reflash to see if it works
Edit: ughhhh it just happened again, but not as bad as before, turns back on after second try... maybe i didnt press the trackball hard enough

[Q] Samsung Galaxy S GT-I9000 won't work if not plugged on external power source

Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !
Marc_B_ said:
Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !
Click to expand...
Click to collapse
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?
timberman4444 said:
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?
Click to expand...
Click to collapse
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?
Marc_B_ said:
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?
Click to expand...
Click to collapse
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.
Hi again, try to play a song and turn the screen off to see what happens.
Sent from my GT-I9000 using xda app-developers app
timberman4444 said:
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.
Click to expand...
Click to collapse
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress
Marc_B_ said:
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress
Click to expand...
Click to collapse
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then
timberman4444 said:
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then
Click to expand...
Click to collapse
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?
Marc_B_ said:
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?
Click to expand...
Click to collapse
you tried to install the rom on the recovery instead of odin?
timberman4444 said:
you tried to install the rom on the recovery instead of odin?
Click to expand...
Click to collapse
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive
Marc_B_ said:
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive
Click to expand...
Click to collapse
so, you can`t install any rom at the moment?
timberman4444 said:
so, you can`t install any rom at the moment?
Click to expand...
Click to collapse
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...
Marc_B_ said:
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...
Click to expand...
Click to collapse
Pretty bad signals there.. i think you should go to a repair shop or buy another device
timberman4444 said:
Pretty bad signals there.. i think you should go to a repair shop or buy another device
Click to expand...
Click to collapse
Sadly, yes... thanks for helping however !

Nexus 6 Screen Won't Turn On, Rest of Phone still on

Figured I see if anyone else has had this issue. I went for a walk with the dog yesterday, and was listening to music on my Nexus 6 the whole time, and when I got home I couldn't get the screen to turn on. Music was still playing, it was still connected to my G watch, and holding the power button triggered a vibrate when the power menu opens--but the screen was completely black and unlit the whole time.
Had no prior issues, just wondering if anyone else has had this issue. Figuring I'll probably call Motorola as this seems like a hardware issue...
Any suggestions would be well received!
Try holding the power and volume down buttons together and see if the screen will come on when it reboots to the boot loader. Alteratively you could try to power cycle it by holding the power button down for 30 seconds. Hopefully Motorola will also be able to help you.
me too
same exact thing happed to me music pulled out headphones the phone still works but the screen is dead. I can pull to use phone and **** and have the same vibration. holding power for 20 seconds is a no go. tried tons of holding combinations it seems like I can get it to shut off and on may be but it's just not doing a reset that I can tell that reboots the screen.
joshsunfresh said:
same exact thing happed to me music pulled out headphones the phone still works but the screen is dead. I can pull to use phone and **** and have the same vibration. holding power for 20 seconds is a no go. tried tons of holding combinations it seems like I can get it to shut off and on may be but it's just not doing a reset that I can tell that reboots the screen.
Click to expand...
Click to collapse
you had an sod(sleep of death). it sounds much worse than it actually is. its a rather common issue as well(no fix). try using a custom kernel.
ok crap
simms22 said:
you had an sod(sleep of death). it sounds much worse than it actually is. its a rather common issue as well(no fix). try using a custom kernel.
Click to expand...
Click to collapse
so stupid question how do I do that? I've only tried to root a phone once and it was a g1. please provide a link or something i'm pretty techy but am rather upset right now.
Ambient display fault?
Hey, I had the same issue, i switched off the ambient display and after that the problem is solved. Give it a try, it might help. Go to Settings, Display, and turn off the ambient display .
same problem

Categories

Resources