Database Info

[Q] Screen won't stay off!

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

[Bug Reports]

MODS : Please move to GENERAL SECTION. Thanks.
Hi, starting this thread to roll up on bugs reporting. Will compile all your reports, verify them and inform Samsung about it and hopeful for a fix.
Sent from my GT-P6200 using XDA App
1) Sleep of Death (two users)
2) Floating Dialer popped up without being asked for... (two user + myself)

sleep of death. Its rare for me but still annoying when it happens. Plus, sometimes when I have the browser set to quick menu when you drag from off screen for the toolbar. The right side will bring up the dial for a second and disappear. Other than that awesome tab!

I get randon reboots and shutdowns, at least one of each everyday, usually right after I first turn it on for the day. It also sometimes is a bugger to wake up, sleep of death? I thought it might be powersaver mode causing me problems but they persist after I turned it off.

kzoodroid said:
I get randon reboots and shutdowns, at least one of each everyday, usually right after I first turn it on for the day. It also sometimes is a bugger to wake up, sleep of death? I thought it might be powersaver mode causing me problems but they persist after I turned it off.
Click to expand...
Click to collapse
I do not have this issue at all.
Try to flash the original firmware and hard reset. Do not root or install apps. Run it for a couple of days and see the result.
But I do believe it can be related to the motherboard.
Example, my original P1000 tablet was superb, no hangs or SODs... but I bricked it (excessive tinkering) and Samsung changed the motherboard. Since then, I started to experience hangs and a few SODs... sold it off...

PandaHandz said:
sleep of death. Its rare for me but still annoying when it happens. Plus, sometimes when I have the browser set to quick menu when you drag from off screen for the toolbar. The right side will bring up the dial for a second and disappear. Other than that awesome tab!
Click to expand...
Click to collapse
happens a couple times a day to me.. I am getting tired of it for sure..

Not trying to be mean, but not development related. Should be just Q&A
Sent from my Insanity powered SGS2

I've been fortunate so far also but if I start to get SOD then I would root grab set cpu and raise your minimum to 400
Sent from my Nexus S using xda premium

sorry for not posting sooner, removed the Micro SD card and reinstalled everything, that was a week ago, not one single SOD or reboot.
Not sure what it means, but it could be looking for the SD to index or update files and not reading the card causing the reboot?
What do I know, it just could be luck, but worth a try.
Let me know how it works for you.

[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?

Nexus 5 randomly turns on

I haven't been able to find this problem documented anywhere so I thought I'd ask.
It seems that my Nexus 5 has suddenly began turning on when being held at a certain angle. I believe that the proximity sensor has something to do with it. It started to happen after I was on the phone for a couple of hours. I've tried restarting, and switching from Art to Dalvik.
Is anyone else familiar with this problem or a solution? It's driving me nuts!
Thanks

onewaylife4all said:
I haven't been able to find this problem documented anywhere so I thought I'd ask.
It seems that my Nexus 5 has suddenly began turning on when being held at a certain angle. I believe that the proximity sensor has something to do with it. It started to happen after I was on the phone for a couple of hours. I've tried restarting, and switching from Art to Dalvik.
Is anyone else familiar with this problem or a solution? It's driving me nuts!
Thanks
Click to expand...
Click to collapse
Are you using a case? it might be pressing the power button.

I have using a case, but there is an oversized cutout around the power button. I am almost certain that this is related to a bug with the proximity sensor.

Mine, when using stock kernel would sometimes turn on by itself after pulling it from my shirt pocket..
Hasn't happened since I stopped using stock kernel.
Doesn't seem too common another poster, think whozilla saw this behavior as well.
No biggie.just odd.
WR
Sent from my Nexus 5

onewaylife4all said:
I have using a case, but there is an oversized cutout around the power button. I am almost certain that this is related to a bug with the proximity sensor.
Click to expand...
Click to collapse
does it turn ON after you power the phone OFF
or you mean that it wakes up from sleep state randomly?

GUGUITOMTG4 said:
does it turn ON after you power the phone OFF
or you mean that it wakes up from sleep state randomly?
Click to expand...
Click to collapse
No, it won't turn on if the phone if OFF. I'm referring to it "waking up". It will wake up simply by holding the phone at a certain angle and distance away from the body.

onewaylife4all said:
No, it won't turn on if the phone if OFF. I'm referring to it "waking up". It will wake up simply by holding the phone at a certain angle and distance away from the body.
Click to expand...
Click to collapse
Are you using a custom Rom/kernel? if so, try installing a new Rom
If that happens to be a hardware problem, It could be more related to the power button than the P.sensor
Most common issues related to the sensor is that screen stays off. Eventually, a screen protector can produce that, but not in your case.
The proximity sensor won't notice the angle you tilt the phone at (compass sensor does). It needs to detect something in front of it closer than +-1 inch to act up and should
turn off the screen when in a phone call. There's no much reason to turn on screen because it is not its function and much less if not phone call is happening.
Maybe the USB port is dirty and thinks you plugged a charger
or power ribbon/connector is loose inside, if any.

Power Button won't wake up screen sometimes.

Hello!
After locking the phone, it happens that sometimes the power button won't turn on the display.
The button is still working, because it is possible to start the Flashlight (long press power button) or open the camera app (double tap power button, can hear the sound).
I'm using the latest lineageos 14.1 version.
Does anybody how to fix this?

AwildPikachu said:
Hello!
After locking the phone, it happens that sometimes the power button won't turn on the display.
The button is still working, because it is possible to start the Flashlight (long press power button) or open the camera app (double tap power button, can hear the sound).
I'm using the latest lineageos 14.1 version.
Does anybody how to fix this?
Click to expand...
Click to collapse
rajat.arora said:
same thing happen with me from last 3 days. don't know what is the problem. but it wake in 1-2 minutes. .i can listen screen unlock sound. and lock sound but display is black.
Click to expand...
Click to collapse
Faulty display.

Not faulty display. Happened to me with oreo roms, nougat roms are ok.
Also with some themes applied too

rajat.arora said:
same thing happen with me from last 3 days. don't know what is the problem. but it wake in 1-2 minutes. .i can listen screen unlock sound. and lock sound but display is black.
Click to expand...
Click to collapse
I installed the official Oxygen OS and still have the same problem.
Mr.Ak said:
Faulty display.
Click to expand...
Click to collapse
I don't think so, because my display got replaced.

Destrocamil said:
Not faulty display. Happened to me with oreo roms, nougat roms are ok.
Also with some themes applied too
Click to expand...
Click to collapse
You ever thought why everyone else is using Oreo roms without display issues and you can't? Hmm,I see faulty display.
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
AwildPikachu said:
I don't think so, because my display got replaced.
Click to expand...
Click to collapse
I'm afraid it is a faulty replacement then.

AwildPikachu said:
Hello!
After locking the phone, it happens that sometimes the power button won't turn on the display.
The button is still working, because it is possible to start the Flashlight (long press power button) or open the camera app (double tap power button, can hear the sound).
I'm using the latest lineageos 14.1 version.
Does anybody how to fix this?
Click to expand...
Click to collapse
As ridiculous as that may sound i think it's a problem with your button, you will have to desolder this and resolder a new one. I used to have the same problem, button didn't work like 2/10 at first, and that rate kept increasing. With use and tear it kept worsening. I bought soldering iron and replaced the button, it now works freakin' great.
Europe link: https ://www. ebay. com /itm/For-OnePlus-One-Replacement-Power-Button-Flex-Cable-OEM/152114356352?epid=685628822&hash=item236ab8e080:g:C20AAOSwLF1YB02h
just remove the spaces and you're ready to go!
If this was any helpful to you please make sure to click the thanks button .

filippos96 said:
As ridiculous as that may sound i think it's a problem with your button, you will have to desolder this and resolder a new one. I used to have the same problem, button didn't work like 2/10 at first, and that rate kept increasing. With use and tear it kept worsening. I bought soldering iron and replaced the button, it now works freakin' great.
Europe link: https ://www. ebay. com /itm/For-OnePlus-One-Replacement-Power-Button-Flex-Cable-OEM/152114356352?epid=685628822&hash=item236ab8e080:g:C20AAOSwLF1YB02h
just remove the spaces and you're ready to go!
If this was any helpful to you please make sure to click the thanks button .
Click to expand...
Click to collapse
Okay that sounds strange. I can give it a try.

Now that i see this Thread again, it's far more likely that your lcd just died or partially did. Although if it turns on sometimes like your state, "that sometimes the power button won't turn on the display" it may be a bad teared down soldering on either the power button on the lcd pcb. Get it to a repair shop and ask for a check, if you don't mine you cant open your back cover and remove the screws so you let the motherboard pcb exposed, with a high quality picture we should be able to see if the power button is the problem or not.

filippos96 said:
Now that i see this Thread again, it's far more likely that your lcd just died or partially did. Although if it turns on sometimes like your state, "that sometimes the power button won't turn on the display" it may be a bad teared down soldering on either the power button on the lcd pcb. Get it to a repair shop and ask for a check, if you don't mine you cant open your back cover and remove the screws so you let the motherboard pcb exposed, with a high quality picture we should be able to see if the power button is the problem or not.
Click to expand...
Click to collapse
The whole display part was replaced in a repair shop.

AwildPikachu said:
The whole display part was replaced in a repair shop.
Click to expand...
Click to collapse
aye, and? Mine was the same, it worsen upon the replacement, and within some days of usage, the flex cable had gotten damaged for good, the oneplus one replacement displays out there are crappy, mostly used, not well maintained, cheap ones, and they are not to be trusted.

filippos96 said:
aye, and? Mine was the same, it worsen upon the replacement, and within some days of usage, the flex cable had gotten damaged for good, the oneplus one replacement displays out there are crappy, mostly used, not well maintained, cheap ones, and they are not to be trusted.
Click to expand...
Click to collapse
I'm using a cheap replacement from ebay that I replaced myself,and I'm yet to see any issues with it.

most lcd have the problem. i got a lcd thrice now from different manufacturers had the same problem for some extent
digitizer works fine but lcd doesn't have good connection

My Nexus was also sometimes not waking with the power button. A custom ROM flash (Nexus4Ever) worked well, but still had the same problem. Probably related to this I would notice that when the phone did wake it was sometimes taking a few seconds to do it.
After some searching I found a solution under the lineageos forums -- search for BUGBASH-230 (can't post url here because this is a guest reply). Basically, you have to copy (copy them, don't move them) all tzapps files found in system/etc to system/vendor. It worked for me. There's no more delay in waking up and the problem has been gone for a week now. Before the fix it was occurring at least once a day. Try it.

I have same problem with you and this occcurd after change os nougat to Oreo 8.1 on my j7 prime

It's not the display
I have the same issue on my Nexus 7 with 14.1 installed. The mockingbird replies about it being a faulty display or power button are unfounded considering rebooting the device fixes the issue. Only seems to occur when it's been on for a while or has less than 30% battery.

Did anyone ever fix this? I see this on a few versions of Lineage. Disabling the lock screen in System Profiles settings avoids the issue, but then there's no lock screen!

Not The Display, exactly...
Just thought I would throw in my 2 cent observations. I have a Samsung Relay 4G (t699/apexqtmo). It worked flawlessly with its stock software / and official upgrade (I.C.S. & J.B). Once I upgraded to KitKat or Lollipop, the screen backlight would never turn on after waking the device on a single button push. The difference between these versions of android as it relates to waking the device can be found in changes to power management / wake locks code. I am not good enough to figure the ins and outs of this type of programming, but maybe this will give some hacker an idea of how to patch or work around this particular part of the firmware. Thanks!

Just upgraded form stock to LineageOS rooted and all....display wake up worked fine b 4 now i have this problem also it will sometimes eventually wake up but takes forever and many button presses

So, if anyone is till wondering about this, here is the information i believe to fix this bug, that is if anyone can integrate the change into CM KitKat and beyond for our sad old Relay. github.com/TeamApexQ/apexq/issues/24. Any chance this could be implemented through an apk?

Because I really don't want to shell out $$$ for an F(x)tec Pro