Well, I'm facing this issue since long time. My proximity sensor stops working after 5 minutes of turning on the phone. That is screen doesn't turns off while calling. I need to press power Button in order to turn off the display.
I tried most of the famous ROMs but all have this issue, but the cataclysm. With this ROM, issue happened but only once in a month or so. I used it since last 12 months or so. It should be noted that I have checked and verified that it's not an hardware's issue. Because it stops working exactly after 5-6 minutes.
After some research, I found that this can be related to radio files. Radio files means kernel? Not sure. I tried to find out but unable to identify which one to install. I'm using lineage is 14.1 for nexus 5. Can somebody please suggest me which version should be installed?
Does this happen on a stock ROM?
i have the same issue as OP said, and i think it's not hardware related problem. but i haven't tried going back to stock ROM atm
I know the proximity sensor has failed on a couple of phones I repaired after they were knocked, dropped, or had a screen replacement.
If it still does it on a completely unrooted stock ROM, I think it would be a hardware issue.
but the weird thing is the sensor is working fine after reboot and a couple of minutes afterwards. and then i lock the phone and put my phone, then i unlock my phone again it's not working anymore. could that be hardware issue or maybe battery issue? i have old battery and i think it needs a replacement
also i read this https://forum.xda-developers.com/google-nexus-5/general/sensors-fix-nexus-5-t2704915 and try the method and still not working
Does this happen on a stock ROM too? If it does, this leads me to conclude it is a hardware issue.
I have run custom ROMs on phones and the ROMs may work fine from a few minutes to a few days. Suddenly, things start to lock up or stop working and a reboot fixes the issues until a short time later.
audit13 said:
Does this happen on a stock ROM too? If it does, this leads me to conclude it is a hardware issue.
I have run custom ROMs on phones and the ROMs may work fine from a few minutes to a few days. Suddenly, things start to lock up or stop working and a reboot fixes the issues until a short time later.
Click to expand...
Click to collapse
Yes. Any ROM including stock ROM. The only ROM with which sensor works as expected is cataclysm. It works totally fine with this which means there’s no hardware issue.
Related
Found some threads mentioning digitizers causing issues with this on other models of hardware, but doesn't sound the same.
Been holding off on rooting my Note that I've had for a week to wait for stock recovery, kernel, etc. to be out in case I had issues.
Rooted no issues, went back to stock just to make sure I could, then rerooted.
Not sure if coincidence, but now if I let the screen time out or manually do it, then wake it up.. my touch screen stops working. I can hard reset and it works until I do the same thing, then stops working again.
Anyone else seen this?
Reseil said:
Found some threads mentioning digitizers causing issues with this on other models of hardware, but doesn't sound the same.
Been holding off on rooting my Note that I've had for a week to wait for stock recovery, kernel, etc. to be out in case I had issues.
Rooted no issues, went back to stock just to make sure I could, then rerooted.
Not sure if coincidence, but now if I let the screen time out or manually do it, then wake it up.. my touch screen stops working. I can hard reset and it works until I do the same thing, then stops working again.
Anyone else seen this?
Click to expand...
Click to collapse
multiple threads:
http://forum.xda-developers.com/showthread.php?t=1849618
http://forum.xda-developers.com/showthread.php?t=1851387
http://forum.xda-developers.com/showthread.php?t=1854665
http://forum.xda-developers.com/showthread.php?t=1848261
http://forum.xda-developers.com/showthread.php?t=1847054
i was not rooted so I returned mine. sounds like some people have been able to get it working again
Okay so this is ROM independent, and has been happening over the course of 2-3 months (with varied roms and many wipes). What will happen is that when I unlock the phone, rarely, (I'd say 1 in 100 times, maybe more) the touchscreen won't work. Usually if I leave it alone for a while, when I go to unlock it, it works again. But usually, I'll have to force reset the phone and then it'll work. It is nearly imposible to recreate this problem, it just randomly happens. My phone doesn't have water damage, and only has some nicks on the cornes from small drops. Anyone know what is happening?
This is a known bug with s2w, some reports also say underclocking/overclocking/undervolting is causing the issue too. Either way, it's well known and there's no fix at this time except for disabling those features or going back to stock kernel.
Ah thanks, had no idea
Sent from my One X using xda app-developers app
Hi guys,
I have a problem that I've never seen or heard of before. So here is the situation:
Power button didn't work, so RMA'd phone. Got different phone back and instantly rooted/installed custom rom. Didn't notice anything until a month later. My phone would randomly just lag out and the wifi would stop. It would still show connected and that there was uploading activity, but that is all. When I clicked it to disable, nothing would happened. I would have to restart the phone, disable it for a while then re-enable it. I though it was the rom so I switched. Noticed the same thing is happening. I decided to play around with my sim, so I took it out and then put it back in, and it somehow fixed the problem. So I was assuming it was the sim causing the problem. Worked perfect for a week then started happening again. I did the thing with the sim and it didn't work this time. I still have the problem now.
Basically, my wifi would just stop working, when I click on it the phone lags out and freezes. I have to restart the phone and it will work. Sometimes Itll work for a full day then all of a sudden just stop. Sometimes it happens just a few minutes after restarting. I mostly find that it happens when the battery is less than 20%. Right now I am running stock LP, locked bootloader. I was supposed to send it in but they wouldn't accept it because I was 6 days over my warranty. So I'm not sure if I was send a faulty phone and now I'm stuck with it?
LG said I would be charged $150 flat rate for them to fix it which sucks. I'd rather just get a new phone and stay away from LG in the future.
Any suggestions? Also this was happening on KK at first then I tried LP Roms and same thing. I have never flashed any radio since I got the phone, could this be a possible solution?
s.hack said:
I was supposed to send it in but they wouldn't accept it because I was 6 days over my warranty. So I'm not sure if I was send a faulty phone and now I'm stuck with it?
LG said I would be charged $150 flat rate for them to fix it which sucks. I'd rather just get a new phone and stay away from LG in the future.
Click to expand...
Click to collapse
You would get the same reply from pretty much any company, once it is over the warranty period then it is over the warranty period, this is no reason to "stay away from LG". Most charge a flat rate since they're likely to simply do a motherboard/whatever board swap if the fault is to do with internal components, as it is much easier/cheaper for them to do this compared to diagnosing and repairing/replacing things individually.
s.hack said:
Any suggestions? Also this was happening on KK at first then I tried LP Roms and same thing. I have never flashed any radio since I got the phone, could this be a possible solution?
Click to expand...
Click to collapse
Try a different radio version. If it doesn't change anything then you have a hardware problem.
Elluel said:
You would get the same reply from pretty much any company, once it is over the warranty period then it is over the warranty period, this is no reason to "stay away from LG". Most charge a flat rate since they're likely to simply do a motherboard/whatever board swap if the fault is to do with internal components, as it is much easier/cheaper for them to do this compared to diagnosing and repairing/replacing things individually.
Try a different radio version. If it doesn't change anything then you have a hardware problem.
Click to expand...
Click to collapse
The only reason I said I would stay away is because it seems that I sent in my phone with a problem only to receive another one with a different problem. I'll try the radios tonight, hopefully it works.
Thanks, I'll keep you guys posted.
s.hack said:
The only reason I said I would stay away is because it seems that I sent in my phone with a problem only to receive another one with a different problem. I'll try the radios tonight, hopefully it works.
Thanks, I'll keep you guys posted.
Click to expand...
Click to collapse
You mentioned that you only ran into issues after a month. During that month a hardware issue could have possibly developed and the device was fine when you initially received it.
Known LP bug.. Thats why i still stay with kk
Sent from my Nexus 5 using XDA Free mobile app
Hi guys i am having a problem where my phone soft reboots after my screen is off.It happens on every rom.It stopped happening when i installed turbo rom for 2 days and then it came back.plz help
Arpan22 said:
Guys this has been a frustrating issue.When I turn my screen off my phone soft reboots.It happens on every rom.When i install the first 6.0.1 stock rom it freezes after every 5 minutes and reboots.Plz help me.This phone has turned useless,i am using aicp 12 and i have to keep my screen on and it doesnt last 5 hours.
Click to expand...
Click to collapse
Assuming you are flashing correctly, then this is a hardware problem...
Have you ever replaced your display panel? Bootlooping on Marshmallow and sometimes odd behavior on Lollipop that is display related could be because of a cheap or non-OEM display, we have definitely seen it before. If you are sure this is the original display then this is not the issue.
I would go back to the flashing process and make sure you are doing it correctly... including the factory reset in stock recovery before flashing.
acejavelin said:
Assuming you are flashing correctly, then this is a hardware problem...
Have you ever replaced your display panel? Bootlooping on Marshmallow and sometimes odd behavior on Lollipop that is display related could be because of a cheap or non-OEM display, we have definitely seen it before. If you are sure this is the original display then this is not the issue.
I would go back to the flashing process and make sure you are doing it correctly... including the factory reset in stock recovery before flashing.
Click to expand...
Click to collapse
I have not replaced my panel.I checked my battery health and it shows good.What hardware problem could cause it.Listen i was using cm13 for almost 6 months and i used a sound mod where my earpiece would work as a speaker.One day it stopped working and another day it just started rebooting aftet every 2 minutes.I dunno what happened
Arpan22 said:
I have not replaced my panel.I checked my battery health and it shows good.What hardware problem could cause it.Listen i was using cm13 for almost 6 months and i used a sound mod where my earpiece would work as a speaker.One day it stopped working and another day it just started rebooting aftet every 2 minutes.I dunno what happened
Click to expand...
Click to collapse
If you haven't replaced the display panel and you purchased the device new, then that isn't the problem.
The sound mod probably blew out the speaker or amp/dsp, likely not related to to the rebooting issue but possible.
Does it reboot in safe mode when turning off the screen?
I'll reply here. I am betting a very non clean install and would like to see you wipe advanced: dalvik, data, system, and cache, and flash only rom, gapps, and supersu if you want, but no additions, kernels, themes, mods, apps, fixes, or anything, and test in that state.
I have a very weird issue with my HTC U11 plus:
When the screen is off (the device is asleep, not turned off), pressing the power button or using the fingerprint sensor turns it on, but there is a random delay, between 5 and 20 seconds, where the screen stays blank.
Additionaly, the Edge Sense is absolutely unreliable: there is again a delay of between 5 seconds and 35 seconds.
It has started doing that last week.
I tried factory resetting it today, but I get the same result. I have opened a ticket at HTC, but as it is out of warranty, I don't think they'll be able to help me...
Has anyone ever seen such an issue?
Did you solve this？
I have this problem too and my camera also have delay when i open.
I tried flash the stock RUU,but it's no use.?
No, unfortunately not. HTC support said they could repair it but as it was out of warranty they gave me a quote for several part replacement they might have to do, and it cost the price of a new handset (500 euros for a motherboard replacement) so in the end I went with a new handset
It's so unfortunately.?
I have the exact same issue and from the last weekish or so, and no luck fixing it or finding out what is causing it. Also tried factory reset, safe mode doesn't help. Randomly its ok at times but typically 5 seconds to wake from sleep mode. Ive done no system updates. And yes camera is affected, almost feels like CPU tied up doing something.
running android 9
software 2.20.709.2
kernel 4.4.153
It must be an APP issue causing this, does someone have the issue on a rooted device to see what's using the CPU. Once its out of sleep mode for a bit its all ok and runs normal.
---------- Post added at 02:42 PM ---------- Previous post was at 02:11 PM ----------
Hi edzilla,
Did you try another ROM, or does anyone with the HTC u11+ not have this issue and if so what ROM/stock version are you on?
I believe I was on the latest update when it happened, and that that there wasn't any update before it started happening.
ill try rooting/aftermarket rom later to confirm if its hardware.
i downgraded back to android 8 RUU and the issue is still there. i have not tried non stock rom yet but this seems like a hardware issue with the screen or CPU once its in full sleep mode. is anyone running a decent alternative rom i can try?
Anybody found a solution? Like with a different ROM? Or confirmed it is hardware?
I have the same. Came out of the blue. First it was draining the battery. That has stopped now. But since a couple weeks, huge delay when starting. Up to 25sec.
Thought it was an app. So did a hard reset, wiped everything. But even without any apps installed, still the same delay when starting from standby.
Android 9
software 2.19.401.2
kernel 4.4.153
Is it worth putting a different ROM? Don't want to waste a weekend...
So maybe better directly getting a new phone? Any thoughts?
Thank you!
ForSH-3719 said:
Anybody found a solution? Like with a different ROM? Or confirmed it is hardware?
I have the same. Came out of the blue. First it was draining the battery. That has stopped now. But since a couple weeks, huge delay when starting. Up to 25sec.
Thought it was an app. So did a hard reset, wiped everything. But even without any apps installed, still the same delay when starting from standby.
Android 9
software 2.19.401.2
kernel 4.4.153
Is it worth putting a different ROM? Don't want to waste a weekend...
So maybe better directly getting a new phone? Any thoughts?
Thank you!
Click to expand...
Click to collapse
I couldn't find a good rom to try and never found a fix for the slow wake issues.. still happens in safe mode so not an app. Most likely hardware.. gave to my daughter who can deal with the issue better than me.
jaya21 said:
I couldn't find a good rom to try and never found a fix for the slow wake issues.. still happens in safe mode so not an app. Most likely hardware.. gave to my daughter who can deal with the issue better than me.
Click to expand...
Click to collapse
Then won't spend time - served me well for 3+ years.
Will get a new phone...
Thanks a lot for letting me know.