[Q] Screen won't stay off! - Nexus S Q&A, Help & Troubleshooting

I can't turn my screen off. When I press the power button it goes off for 0.5 to 3 seconds and comes back on. I was using Axura when it first happened, but then I restored an older CM rom and I'm having the same issue. Has anyone else had this problem? I'm sure I don't have to add that it isn't ideal for battery life ..

cavved said:
I can't turn my screen off. When I press the power button it goes off for 0.5 to 3 seconds and comes back on. I was using Axura when it first happened, but then I restored an older CM rom and I'm having the same issue. Has anyone else had this problem? I'm sure I don't have to add that it isn't ideal for battery life ..
Click to expand...
Click to collapse
Are you plugged in when it is happening? If so, have you tried to turn off the "Always stay on" setting?

I had this happen to me. It turns out it was a faulty power button. Its a hardware issue. I had to return my phone because I was still in the 30 day window, if you're outside of that you need to send it in to samsung.
Sent from my Nexus S using XDA Premium App

Thanks for the replies.
Strangely enough the issue disappeared as quickly as it appeared about 6 hours after it began! I tend to agree that it's a hardware problem, but as long as it's not happening constantly I'm going to live with it (due to the fact that as an Australian living in Spain with a NS from the US I don't imagine a warranty claim would be easy).

A hardware problem wouldn't be my first assumption if I was on a custom ROM and/or had lots of apps installed.
If it happens again, I'd get a logcat recorder app or adb logcat session running on the phone and see what exactly it says goes on just before the screen wakes each time.

Oh ok. I tend to assume it's a hardware problem due to the fact that it happened on completely different roms. But the way that bug causing "artifacts" are sometimes left behind when changing roms doesn't give me confidence in that assumption. I really don't understand it.
I'll definitely give the logcat a go if it comes back. Thanks.

hi,
i am bringing back this thread from a few months back because it was the only one i found that showed the same problem.
i installed alogcat and attached a log file here. can anyone see if there's anything in the log that would be a software reason as to why it's waking itself? also, it doesn't shut itself off while this is happening. the screen will stay on indefinitely. i've had the phone for 6 months and this has become a new problem i would say in the last 3 weeks. i don't want to have to send it to samsung for a few weeks.
thanks for any assistance

Related

Take pic with camera using flash: phone goes dead?

Hi - I just got my Sensation a few days ago and I love it. But I have now found an annoying bug (?). When I take a picture and it involves the flash going off, 8 times out of ten the phone will just go dead immediately - screen off, no response. Sometimes a battery pull required to get it to reboot. Anyone experienced this?
Seems to happen indoors when the subject is fairly close, darker conditions.
Not sure if this is a hardware or software problem - I really don't want to return it
Try turning off geotagging.
Thanks, I tried that, then turning off gps, then turning off location, same problem every time.
I find that turning off mobile data, and even leaving all of the above on, stops the problem. Or, leaving data on but turning off the flash. Data + flash = crash...!
Still not sure if this is software related? I guess so?
dazz29 said:
Thanks, I tried that, then turning off gps, then turning off location, same problem every time.
I find that turning off mobile data, and even leaving all of the above on, stops the problem. Or, leaving data on but turning off the flash. Data + flash = crash...!
Still not sure if this is software related? I guess so?
Click to expand...
Click to collapse
Hmm. Since it's correlated with the flash, and few if any others have complained about this I'd guess HW, but who knows. I'd probably do a factory reset, and if that didn't fix it get a replacement.
Has anyone found a solution to this problem? Same thing happens to my phone.
This was posted when the phone first came out. Probably in the early threads. That was one of the first things I checked when I got my Sensation. I don't know if there was a solution other than swapping - but do a search in the forum because it was covered. Hope there was a solution for you.
Same thing happens here, Revo HD.
MEETOO
At first I just waited and it would restart THEN...
Had to pull battery and it would restart THEN...
When it restarted only a speckled screen followed by home screen THEN...
Only speckled screen THEN...
Nothing but the vibration when trying to restart THEN...
A replacement is being shipped after a trip to the T-Mobile store.
Initially I called T-Mobile and they told me the UPDATE would solve my problem but as the day progressed it was all down hill.
During the course of the sales person ordering me a new phone they automatically added a protection plan without my knowledge.
YIPPEE HUH?

Phone keeps randomly powering off!

Hi, been away from the forum, as i have just got back from holiday
i am having a prblem with my desire.. i went to florida, left my phone at the theme parks, desire s, zte blade, ipod touch in the car for 8 hours in around 30-40 degrees. since then, my desire s has been faulty.
my touch, and zte work fine, but my desire has a major problem now. it works normal in use, but when i lock it and put it into sleep mode, when i try to unlock it , it will start up the whole phone again. basically, it powers off on its on randomly in sleep mode.
The problem is really annoying. it is also very common on the desire hd..
http://www.google.co.uk/search?sour...360GB360&q=htc+desire+hd+randomly+turning+off
Im running leedroid port from dhd. i thought the rom was the problem, but it isnt. i flashed other roms, hydrogen, but the problem still exists. shoud i test the stock unrooted ROM?
i dont think it is a software fault anyweay. the phone was working fine for 2 weeks running leedroid, then suddenly i have the problem now.
i have emailed htc, and awating a reply now. so will i need to get it repaired? or replaced as a faulty unit?
Hmm.....does sound like the heat has done it in....damn!
Although there are plenty of other countries where the temp is close to this all the time, you would have thought....
Try installing close to stock ROM with no apps installed, (Yes perform wipe). I'd suggest installing battery moniotr widget and get iot to log full details (including apps), force log in sleep mode so that you can at least see when it dies and what temp it's at when it does and what apps are running at the time.
Although does sound like warranty return issue (at least this way you get a new motherboard and possibly even a new device)...(you might want to check the recommended running temp levels in the warranty book first - just so that you get your story straight)
Positive note: at least its still functioning so that you can re-install RUU etc and mask S-OFF before returning it?
ps
Mines done this a couple of time over the last few months...although I always figured that I've hit the buttons in my pocket?
ben_pyett said:
Hmm.....does sound like the heat has done it in....damn!
Although there are plenty of other countries where the temp is close to this all the time, you would have thought....
Try installing close to stock ROM with no apps installed, (Yes perform wipe). I'd suggest installing battery moniotr widget and get iot to log full details (including apps), force log in sleep mode so that you can at least see when it dies and what temp it's at when it does and what apps are running at the time.
Although does sound like warranty return issue (at least this way you get a new motherboard and possibly even a new device)...(you might want to check the recommended running temp levels in the warranty book first - just so that you get your story straight)
Positive note: at least its still functioning so that you can re-install RUU etc and mask S-OFF before returning it?
ps
Mines done this a couple of time over the last few months...although I always figured that I've hit the buttons in my pocket?
Click to expand...
Click to collapse
Cheers Ben! Love how your always here to help!
I'll try installing battery monitor widget , and go back to stock, s-on
So do you think it was the heat that damaged the phone? My ipod touch and zte blade were left in the car, but they work 100% fine
I've checked the warranty thingy, it says do not expose battery to 60 degrees or higher.
But to be honest, I dot really know how hot it could get in the car... Florida is very hot!
I'm just waiting for a reply from HTC now
The phone works fine everywhere else, its just this problem.. I tried cooling the phone by switching it off and taking the battery out, and leaving it for an hour.
The thing with this problem, is that it is entirely random! It sometimes last ages in standby before the problems occur, or within 10 minutes.
How can I prove it to HTC??
I wouldn't worry too much about your phone doing the same once in a few months or so
Mine is happening at least 6 times a day!!
I'll try to keep the thread updated to how it all goes
Cheers Ben
Sent from my HTC Desire S using XDA Premium App
olyloh6696 said:
Cheers Ben! Love how your always here to help!
I'll try installing battery monitor widget , and go back to stock, s-on
So do you think it was the heat that damaged the phone? My ipod touch and zte blade were left in the car, but they work 100% fine
I've checked the warranty thingy, it says do not expose battery to 60 degrees or higher.
But to be honest, I dot really know how hot it could get in the car... Florida is very hot!
I'm just waiting for a reply from HTC now
The phone works fine everywhere else, its just this problem.. I tried cooling the phone by switching it off and taking the battery out, and leaving it for an hour.
The thing with this problem, is that it is entirely random! It sometimes last ages in standby before the problems occur, or within 10 minutes.
How can I prove it to HTC??
I wouldn't worry too much about your phone doing the same once in a few months or so
Mine is happening at least 6 times a day!!
I'll try to keep the thread updated to how it all goes
Cheers Ben
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
Hello,
Could have been the heat, but could simply be a faulty motherboard....either way a new device might be a good thing, 1/2 way through your warranty period.
Don't know how hot it gets in cars in Florida....but I know that it can kill pets let alone phones!
Cheers, not worried about my phone, just trying to relate that's all
You're just going to be have to forcefull in your email and exaggerate...even
best of luck
ben_pyett said:
Hello,
Could have been the heat, but could simply be a faulty motherboard....either way a new device might be a good thing, 1/2 way through your warranty period.
Don't know how hot it gets in cars in Florida....but I know that it can kill pets let alone phones!
Cheers, not worried about my phone, just trying to relate that's all
You're just going to be have to forcefull in your email and exaggerate...even
best of luck
Click to expand...
Click to collapse
Yeh thanks I think it must be the heat that damaged the phone; it was working perfectly before for the last 3weeks!
My phone is just a month old now
Hopefully they just send me a new phone
I tried to act pleading in the email, but I did not mention anythig about leavig it in heat or the car. I just said it keeps crashing on me...
Hopefully I get a reply soon tommorow!
Sent from my HTC Desire S using XDA Premium App
Though my phone was not left anywhere where temp was extreme, mine is also doing this since this week,, Also a few months old and I blame the apps installed . I ahd battery monitor and suspected just that prog..
I have not yet gone to a clean rom yet but selectively remove apps till I find improvement....
Meaning there are others with the same problem !
olyloh6696 said:
Hi, been away from the forum, as i have just got back from holiday
i am having a prblem with my desire.. i went to florida, left my phone at the theme parks, desire s, zte blade, ipod touch in the car for 8 hours in around 30-40 degrees. since then, my desire s has been faulty.
my touch, and zte work fine, but my desire has a major problem now. it works normal in use, but when i lock it and put it into sleep mode, when i try to unlock it , it will start up the whole phone again. basically, it powers off on its on randomly in sleep mode.
The problem is really annoying. it is also very common on the desire hd..
http://www.google.co.uk/search?sour...360GB360&q=htc+desire+hd+randomly+turning+off
Im running leedroid port from dhd. i thought the rom was the problem, but it isnt. i flashed other roms, hydrogen, but the problem still exists. shoud i test the stock unrooted ROM?
i dont think it is a software fault anyweay. the phone was working fine for 2 weeks running leedroid, then suddenly i have the problem now.
i have emailed htc, and awating a reply now. so will i need to get it repaired? or replaced as a faulty unit?
Click to expand...
Click to collapse
A2Z said:
Though my phone was not left anywhere where temp was extreme, mine is also doing this since this week,, Also a few months old and I blame the apps installed . I ahd battery monitor and suspected just that prog..
I have not yet gone to a clean rom yet but selectively remove apps till I find improvement....
Meaning there are others with the same problem !
Click to expand...
Click to collapse
Yeh, some of them have the same problem after a couple if weeks old (not exposed to heat or anything) what causes this problem?
How often do u have this problem??
My old Nokia 5230 has the same problem
Mine has the same problem and has never been exposed to extreme heat. I think the power button is faulty and after some use it get stuck some times and closes the phone down. I started pressing the button with less force and the random power downs stopped happening.
What happened? I have not found a relationship yet. It seems random too me so far. If it happens once more i will go to factory default plain htc stock rom (i have not fiddled with the device or rom)
If it then happens as well i know enough. I will see and report me experience in due time.
Btw its android 2.3.3 build 1.47.401.4
Sent from my HTC Desire S using XDA App
A2Z said:
What happened? I have not found a relationship yet. It seems random too me so far. If it happens once more i will go to factory default plain htc stock rom (i have not fiddled with the device or rom)
If it then happens as well i know enough. I will see and report me experience in due time.
Btw its android 2.3.3 build 1.47.401.4
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
To be honest, I think its more of a hardware problem!
My phone was running fine on stock and custom roms for 3 weeks, then it just started last week when I left my phone in the car
A lot if desire hd users had the same issue as us!
I'm awaiting a reply from HTC now
Will update on what they say.
the heat probably was the culprit
my phone reaches around 45c at times due to the high outside temperature here,but i don't have any problems so i guess yours was heated more
but if you can, try changing the battery it may help
Random shutdown
I also suffered from this. A new Radio + ROM + cleaning some apps has solved the problem.
Thanks for the replies everyone!
I received the following e-mail of HTC today:
Dear Oliver Loh,
Thank you for contacting HTC regarding your HTC Device.
I understand that you are currently experiencing difficulties with rebooting and random restarts.
I believe that the reason for this is because of a hardware issue.
In order to rectify this I would like you to perform the following actions:
) Make sure your device is fully up to date:
Menu - settings - about phone - system software update - tick box - check now.
) If possible test the device with or without a (new) battery, SIM, SD card.
To assist you further I have attached links to the HTC Support Site which will enable you to work through the above step by step:
http://www.htc.com/uk/support.aspx
Once the above has been completed you may be required to do a factory reset, for your convenience I have detailed the steps below:
) Restarting or factory resetting your phone:
Restarting your phone (soft reset):
If your phone is running slower than normal, an application is not performing properly, or your phone becomes unresponsive, try restarting your phone and see if that helps solve the problem.
Please remove the battery, wait for a few seconds, reinsert the battery, and then turn the phone on.
Performing a factory reset (hard reset):
Note: Factory reset will not remove the data and files that are in your phone’s microSD card.
Factory reset is not a step to be taken lightly. It will permanently delete all your data and customized settings, and will also remove any applications you've downloaded and installed. Be sure to back up any data and files you want to keep before you do a factory reset.
Performing a factory reset via settings
Performing a factory reset using phone buttons:
If you cannot turn on your phone or access the phone settings, you can still perform a factory reset by using the buttons on the phone.
1. With the phone turned off, press and hold the VOLUME DOWN button, and then briefly press the POWER button.
2. Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button..
3. Press VOLUME DOWN to select CLEAR STORAGE or (Factory Reset), and then press POWER.
4. Press VOLUME UP to start the factory reset.
Should the above solution not resolve your query please can you confirm the following and reply to me:
1) Has the device been recently updated/upgraded or changed:?
2) Has a new application been recently downloaded:?
3) Please can you turn off all applications and UN-install any which are unessential, As they may be causing issues:?
4) What have you already done/tried to troubleshoot your issue/s:?
5) When did your issue/s occur or re occur:?
6) Is you device or applications fully up to date:?
Should the above fail to restore your device to full working order, the device (MAY) need to be sent for repair.
I hope that this information meets with your requirements, should you have any further questions please do not hesitate to contact us again.
If this response has resolved your query, and you have no further questions please close this ticket by following the link below. Upon closure of the ticket you will be invited to complete our Customer Satisfaction Survey which should take no more than 1 minute to complete.
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number xxxxxxxxxxxxxxxxxxx.
Sincerely,
Robert
HTC
Want to see what others are saying? Have a question to ask other HTC fans?
Become a fan of HTC facebook.com/htc
Follow us on Twitter twitter.com/htc
Subscribe to our YouTube Channel youtube.com/htc
Explore our development resources developer.htc.com
We are unable to receive replies to this email account. Please visit us at htc.com if you have any questions or need further assistance.CONFIDENTIALITY NOTE : The information in this e-mail is confidential and privileged; it is intended for use solely by the individual or entity named as the recipient hereof. Disclosure, copying, distribution, or use of the contents of this e-mail by persons other than the intended recipient is strictly prohibited and may violate applicable laws. If you have received this e-mail in error, please delete the original message and notify us by return email or collect call immediately. Thank you. HTC Corporation
Click to expand...
Click to collapse
And today i can confirm the problem has occured 8 times today. Now it can do the problem up to 3 times in a row, when the device is in use.
It happened this morning 3 times, 2 in the afternoon, and as i am typing now, i just booted into recovery and the phone crashed on me twice at the recovery screen.
I will reply to HTC and tell them i have the stock rom etc, and will s-on my device and send it for repair soon hopefully
So what's your uptime since you changed??
rotem said:
I also suffered from this. A new Radio + ROM + cleaning some apps has solved the problem.
Click to expand...
Click to collapse
If the problem persists through multiple ROMs, it definitely sounds like a hardware problem. I'd return it to stock and have it sent in for repair under warranty.
Haven't read all replies... but this is a well-known battery fault (and isn't necessarily triggered by either heat or humidity... it is most commonly a manufacturing defect).
My very first HTC Desire S handset had almost exactly the same issue, only the battery from that handset would power off the phone only when the GSM picked up a signal (I.E.... you get reception, but the phone kills itself instantly. No reception, phone ran fine).
O2 replaced the entire thing under warranty (but I sneakily kept the battery to prove my theory). I placed that battery into my replacement handset, and behold.... EXACTLY the same thing!
Put the new battery in, everything works perfectly.
Bottom line: don't replace the phone, just replace the battery!
LaKraven said:
Haven't read all replies... but this is a well-known battery fault (and isn't necessarily triggered by either heat or humidity... it is most commonly a manufacturing defect).
My very first HTC Desire S handset had almost exactly the same issue, only the battery from that handset would power off the phone only when the GSM picked up a signal (I.E.... you get reception, but the phone kills itself instantly. No reception, phone ran fine).
O2 replaced the entire thing under warranty (but I sneakily kept the battery to prove my theory). I placed that battery into my replacement handset, and behold.... EXACTLY the same thing!
Put the new battery in, everything works perfectly.
Bottom line: don't replace the phone, just replace the battery!
Click to expand...
Click to collapse
Hmm.. it does make a bit more sense that the heat could have affected the battery rather than the phone itself.
The battery is probably unable to run under low power that is used when put in sleep mode so it just cuts itself out altogether.
My hypothesis...
i have the exact problem!!
i thought i was the only one... mine turns off at least 3-4 times a day for no apparent reason.
at first, i thought it was the heat during the summer.. but now that the temperature is getting milder i dont really think thats the cause.
sometimes when i place it on the desk and i tap it or just bump it hard enough it'll turn off.
i think its more of a hardware problem then software.
Julzx said:
i have the exact problem!!
i thought i was the only one... mine turns off at least 3-4 times a day for no apparent reason.
at first, i thought it was the heat during the summer.. but now that the temperature is getting milder i dont really think thats the cause.
sometimes when i place it on the desk and i tap it or just bump it hard enough it'll turn off.
i think its more of a hardware problem then software.
Click to expand...
Click to collapse
That's sounds like a bad battery connection, I'd take it back under warranty {if possible} as the chance of a fried eMMC chip must be high!

Random Reboots.. any new info?

Hi everyone.. I searched a bit but couldn't come up with any more answers so I'm wondering if I missed something.
I've had my TF since like May, and for as long as I've had it, I've had this issue.
No matter what kernel or Rom or anything, my TF always randomly reboots ONLY when my screen is shut off and the wireless is left on. It doesn't reboot if I'm using it, and the only way to make it not happen is to turn on airplane mode when I'm done with it.
Its not a big deal, but it is annoying, especially if I leave it in the living room and forget airplane mode. Then whoever is in there gets to watch my TV constantly and randomly reboot every few minutes.
Its just more annoying than anything. Id love to just keep wifi active so it automatically connects when I turn the screen on.
Other than this, my TF has been flawless for like 6 months
Thanks if anyone has any information!
I've suffered through the same issue with my 16gb TF. By any chance do you have your pattern lockscreen turned on? Can't quite remember where, but I read that having it stops the reboots.
I tried it on mine and haven't had one since...but it's only been a day or 2. Can anyone confirm if the lockscreen stops or limits the issue?
avlon said:
I've suffered through the same issue with my 16gb TF. By any chance do you have your pattern lockscreen turned on? Can't quite remember where, but I read that having it stops the reboots.
I tried it on mine and haven't had one since...but it's only been a day or 2. Can anyone confirm if the lockscreen stops or limits the issue?
Click to expand...
Click to collapse
Wow, ill have to give this a try. I've never used the pattern lockscreen.
random reboots
I get this after about an hour of use. If I sitch it off via the button then when I press it again it reboots. If I just let th TF switch itself off (after 5 mins) it switches on normally when I press the start button.
I also had similar problems with my wife's TF, it rebooted randomly just about anytime (not just with screen off), apps crashing randomly. When I returned it to the store where I bought it, they immediately replaced it with a new one that doesn't suffer any of those problems.
If you have such problems, I'd recommend taking it back to the store for repair, because that is definitely not the expected behavior.
unfortunately the lock screen thing didn't work
Can't really take the thing back, I've had it for months.... fortunately this is the only issue I have... I can live with it. Its purely an annoyance that doesn't affect me when using it...

[Q]SOLVED! Big problem on all 4.2 roms can't make or receive calls!

Hi. I have been running pacman v22.0.1 for quite some time now and I could quite easily make and receive calls with no problems, the rom was fast and battery life was great. But quite recently, I received a call and answered it spoke but when it came to ending it, I couldn't get the screen to turn on and all that happened was the button backlights were flashing like mad! So I left it for a while and came back to the phone which had dropped from 84% battery to 41% and it was running very slow. Later when I tried making a call, I couldn't hear anything and I couldn't end the call which led to a charge of £5 which isn't too much money I'm not too fussed with that. But I switched to another rom then wiped everything and flashed pacman again but still had the same problem. Is there anybody who is facing the same problem or has a solution? I have tried on 4 different 4.2 roms now and have experienced the same problem with all.
Just uploaded a very, very long log cat if you are a dev or have knowledge of logs, please read!
Problem solved, it was my screen protector which was covering my proximity sensor and jelly beans behaviour with the proximity sensor caused it to stay off. When buying a screen protector always make sure it has a hole or gap of some sort for the proximity sensor. The bug in the log cat was something else which was fixed by a build.prop tweak.
My radio is 3831.19.00.110
ifti786 said:
I couldn't get the screen to turn on and all that happened was the button backlights were flashing like mad! So I left it for a while and came back to the phone which had dropped from 84% battery to 41% and it was running very slow. Later when I tried making a call, I couldn't hear anything and I couldn't end the call which led to a charge of £5 which isn't too much money I'm not too fussed with that.
Click to expand...
Click to collapse
Were you rapidly pressing the power button? Occasionally, I find my phone lags when turning the screen on, I press the power button once and the buttons light up, then I don't press it again and wait for the screen to turn on. If it is pressed a second time, it means "turn the screen off again", so you never see it turn on.
paulie-uk said:
Were you rapidly pressing the power button? Occasionally, I find my phone lags when turning the screen on, I press the power button once and the buttons light up, then I don't press it again and wait for the screen to turn on. If it is pressed a second time, it means "turn the screen off again", so you never see it turn on.
Click to expand...
Click to collapse
That could just be it: the reason for my problem is my impatience! Still need to check though...
No, that didn't fix it. I think it might have something to do with my proximity sensor because on vipersaga, it used to turn the screen on when I moved my phone from my ear but now it doesn't so I have to press the power button.
Also have the same problem on jelly bean fire
Sent from my HTC Desire S
Please help because I really want Jelly Bean 4.2 but at the current moment, it looks like my desire s is incapable of running it!
I flashed the ROM this morning and everything is well except of GPS (or is it just invisible?) and no weather on the cLock widget (btw any ideas here anybody?). I had issues of the screen keeping black with backlightes hardware buttons (and some others) with v21. But I never tried to use the phone for calling somebody with that, cause it was merely a stage facing the best ROM for me.
Did you do full wipe and Dalvik cache wipe? I found it is very useful to do so, cause it eliminates uncertainties the kind of "where does this come from?".
sanilii said:
I flashed the ROM this morning and everything is well except of GPS (or is it just invisible?) and no weather on the cLock widget (btw any ideas here anybody?). I had issues of the screen keeping black with backlightes hardware buttons (and some others) with v21. But I never tried to use the phone for calling somebody with that, cause it was merely a stage facing the best ROM for me.
Did you do full wipe and Dalvik cache wipe? I found it is very useful to do so, cause it eliminates uncertainties the kind of "where does this come from?".
Click to expand...
Click to collapse
Wipe all partitions except sd card AMD done this on pacman v22.0.1, JellyFireBean, JellyTime, flinny cm10.1 and AOKP redefined. I have just flashed a new radio and will check if that fixed it
Flashing a new radio did not fix the problem please somebody help!
ifti786 said:
Flashing a new radio did not fix the problem please somebody help!
Click to expand...
Click to collapse
I've got the same problem. My screen won't turn on after I move the phone away from my head after a call, altho I can turn it on with the powerbutton somehow. Happens on all JB ROMs for me aswell.
I tried Proximity Sensor Finder app from play store and it says 9cm when theres nothing infront of the sensor, then goes to 0cm when there is something, but doesn't go back to 9cm when the sensor is free again. It only goes back to 0cm when I restart the app.
I don't know whats the problem, but I think its software related.
Is the s2w turned on? If so, it could be the problem. BTW, the problem with black screen but capacitive button lights turned on, also have I. I see it, when I turn off the screen and try to turn it on after 5-10 seconds. But waiting a little helps.
Running Pacman 22.0.1
NVardan said:
Is the s2w turned on? If so, it could be the problem. BTW, the problem with black screen but capacitive button lights turned on, also have I. I see it, when I turn off the screen and try to turn it on after 5-10 seconds. But waiting a little helps.
Running Pacman 22.0.1
Click to expand...
Click to collapse
S2w is off, tried waiting too and that didn't help. I took a log cat of what happened and can upload it if wanted. My friend is taking a look at it for me to see whether there's a bug. It could have something to do with the build.prop.
ifti786 said:
S2w is off, tried waiting too and that didn't help. I took a log cat of what happened and can upload it if wanted. My friend is taking a look at it for me to see whether there's a bug. It could have something to do with the build.prop.
Click to expand...
Click to collapse
Maybe you should upload the logcat in the PACman thread.
Ok will do that now
Sent from my HTC Desire S
NVardan said:
Maybe you should upload the logcat in the PACman thread.
Click to expand...
Click to collapse
The log cat is waaaaaaay too long, I've sent you a message, anybody else who wants the log cat, ill pm you.
ifti786 said:
The log cat is waaaaaaay too long, I've sent you a message, anybody else who wants the log cat, ill pm you.
Click to expand...
Click to collapse
Unfortunately I am NOT a developer so I can't help you.
You must copy-paste your logcat in a .txt file and upload it in the PACman thread.
Sent from my Desire S using Tapatalk 2
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
sarcome said:
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
Click to expand...
Click to collapse
Right, I've just had a look through the logcat and i've found a bug. I'm going to try some build.prop tweaks and see what the results are. I will let you know but please bear in mind that it might take some time as I am having some very important exams coming up so I'm going to be revising in most of my free time.
sarcome said:
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
Click to expand...
Click to collapse
Do you have a screen protector on your phone by any chance?

Busted phone for a Dev if you want it

Alright guys, I had a conversation in Ax's "Run ROMs on different Carriers" thread, but I really want to get to the bottom of my issue, whether it be a hardware issue, ROM related, OR user related.
I've been having an issue with my phone the past few days. Started out it would read "invalid sim, need to reboot" or something along that. Anyways this was after flashing a nightly and I figured, OK, it's a nightly i'll live with it. Eventually my phone just started to power off/reboot all by itself; not real consistent but it was happening more than I would like. Today, the S*&% really hit the fan. I flashed a nightly Wednesday night(i'm not going to say which one, because i'm not sure if it was from the ROM itself or if this was a hardware issue). Anyways, Friday at about noon or so, I open a game to play on my lunch break, I get distracted so I lock my phone to attend to something else. I go back to my phone and it is powered off, now totally unresponsive to anything. I pull battery and try to restart, when I place the battery back in the phone it automatically reboots(WITHOUT ANY BUTTON PRESS) I thought to myself ok this is kind of weird. I try rebooting by using power+vol up...absolutely nothing, it's just a brick. Well, I pull the battery again, hold vol up thinking it will go into recovery...nope, it will boot for a sec or two, just enough to get the blue lettering on the top left of the screen then shuts off again. OK, let's put this b*&*h into download mode and see what happens. it goes into DL mode, all the way to the point of where it says " do not turn target off" then shuts down. I did both of these multiple times, with different batteries as well, plugged in and not. It won't stay on for a computer to recognize it. Someone suggested a stuck power button, I don't think so; it feels the same as it always has.
I was fortunate enough to be able to get another S4 with a busted screen so I switched out motherboards. I have a working phone again...which is all I was worried about. I've flashed quite a few ROMs, I follow procedure to the T when flashing... What do you guys think...hardware issue...user issue...ROM issue? I'm very curious to know because I don't want this happening again, obviously. I would even send the phone out to someone to play with(mind you, the screen doesn't work and the silver bezel is crappy because I just used my original one).
I would say stay away from whatever ROM you flashed. This could also be a hardware issue. I had my old note just randomly shut off on me and was unresponsive as well. Finally got it to boot and reset it. But in your case I would stay away from that ROM and maybe find something more stable. So as this is unknown to what happened I would not blame either. Sorry to hear about your bad experience.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Soup_Nazi said:
Alright guys, I had a conversation in Ax's "Run ROMs on different Carriers" thread, but I really want to get to the bottom of my issue, whether it be a hardware issue, ROM related, OR user related.
I've been having an issue with my phone the past few days. Started out it would read "invalid sim, need to reboot" or something along that. Anyways this was after flashing a nightly and I figured, OK, it's a nightly i'll live with it. Eventually my phone just started to power off/reboot all by itself; not real consistent but it was happening more than I would like. Today, the S*&% really hit the fan. I flashed a nightly Wednesday night(i'm not going to say which one, because i'm not sure if it was from the ROM itself or if this was a hardware issue). Anyways, Friday at about noon or so, I open a game to play on my lunch break, I get distracted so I lock my phone to attend to something else. I go back to my phone and it is powered off, now totally unresponsive to anything. I pull battery and try to restart, when I place the battery back in the phone it automatically reboots(WITHOUT ANY BUTTON PRESS) I thought to myself ok this is kind of weird. I try rebooting by using power+vol up...absolutely nothing, it's just a brick. Well, I pull the battery again, hold vol up thinking it will go into recovery...nope, it will boot for a sec or two, just enough to get the blue lettering on the top left of the screen then shuts off again. OK, let's put this b*&*h into download mode and see what happens. it goes into DL mode, all the way to the point of where it says " do not turn target off" then shuts down. I did both of these multiple times, with different batteries as well, plugged in and not. It won't stay on for a computer to recognize it. Someone suggested a stuck power button, I don't think so; it feels the same as it always has.
I was fortunate enough to be able to get another S4 with a busted screen so I switched out motherboards. I have a working phone again...which is all I was worried about. I've flashed quite a few ROMs, I follow procedure to the T when flashing... What do you guys think...hardware issue...user issue...ROM issue? I'm very curious to know because I don't want this happening again, obviously. I would even send the phone out to someone to play with(mind you, the screen doesn't work and the silver bezel is crappy because I just used my original one).
Click to expand...
Click to collapse
Im saying nothing for sure, but a stuck power button feels just like normal. I had this issue on two separate samsung phones (they are known for this issue). I thought it was just bs, but i decided to tear it down and check. I used a q-tip and everclear and got plenty in there, wiggled and pressed the button for around five minutes. Re assembled, put the battery in and sure enough, the problem was gone. You cant always feel the button sticking. But hey, if you are offering the remains up, ill take em! I would gladly pay $200 for a replacement screen for it to test on.
Sent from my Nexus 7 using XDA Premium 4 mobile app
rebel1699 said:
Im saying nothing for sure, but a stuck power button feels just like normal. I had this issue on two separate samsung phones (they are known for this issue). I thought it was just bs, but i decided to tear it down and check. I used a q-tip and everclear and got plenty in there, wiggled and pressed the button for around five minutes. Re assembled, put the battery in and sure enough, the problem was gone. You cant always feel the button sticking. But hey, if you are offering the remains up, ill take em! I would gladly pay $200 for a replacement screen for it to test on.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Someone beat you to it, Rebel, sorry...just took the first poster or PM that I got. I got the message overnight otherwise I would have posted in here.
I kinda played with the power button when it was tore down, however I didn't use any alcohol on it but that is a good idea.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Edit: Used some IPA on the power button this morning, soaked it pretty well, pressed the button many many times with varying pressure, with a hard pointy object etc. etc., jiggled side to side, tried every option I could to get it unstuck (if that's what it is) and still doing the exact same thing.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Mods, I'd like to politely request this thread to be closed...no use for it now. Thanks.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Categories

Resources