Related
Hi ppl. I recently encountered this problem and Hv searched a lot but couldn't find a proper solution.
I pulled my Ph out of my pocket and had the pocket sensor app installed back then and the phone was getting locked and unlocked but I couldn't bypass the lock screen since the touch screen wouldn't respond. I could see everything else on the notification bar working like the gprs arrows and I even got a call when this happened but couldn't pick the call up too. The only way I could get out of it was to take the battery out. Now its been happening often and I heard the emmc chip gets fried if u keep taking the battery out when the Ph is on. Anyone else facing a similar problem??
I am rooted on 2.3.5
Sent from my HTC Incredible S using XDA
FCArsenal said:
Hi ppl. I recently encountered this problem and Hv searched a lot but couldn't find a proper solution.
I pulled my Ph out of my pocket and had the pocket sensor app installed back then and the phone was getting locked and unlocked but I couldn't bypass the lock screen since the touch screen wouldn't respond. I could see everything else on the notification bar working like the gprs arrows and I even got a call when this happened but couldn't pick the call up too. The only way I could get out of it was to take the battery out. Now its been happening often and I heard the emmc chip gets fried if u keep taking the battery out when the Ph is on. Anyone else facing a similar problem??
I am rooted on 2.3.5
Sent from my HTC Incredible S using XDA
Click to expand...
Click to collapse
Did u try to lock n unlock it via the on/off button on top when it not responding?..
Sent from my HTC Incredible S using xda premium
I had major problems when I was on 2.3.3 stock unrooted.
I had a lot of crap on it so maybe that was the problem.
Are you on a custom rom? If youre not, I would probably try a gingerbread custom rom and see if it still happens.
Also if you are scared of taking the battery out, you can hold power+vol down+vol up at the same time for a few seconds, and it will reboot
Try not to use that apps. See whether the same thing happen again or not.
Sent from my HTC Incredible S
Yes McIero. I tried the power button but it doesn't help. TX anyway
Sent from my HTC Incredible S using XDA
FCArsenal said:
Yes McIero. I tried the power button but it doesn't help. TX anyway
@marcj338 yeah am on the rooted 2.3.3 rom. Did u Hv similar problems with this rom?? It happens sometimes but when it does it really gets annoying grrr. Am waiting for ics to come out n hopefully it will fix it.
Sent from my HTC Incredible S using XDA
Click to expand...
Click to collapse
Sent from my HTC Incredible S using XDA
FCArsenal said:
Sent from my HTC Incredible S using XDA
Click to expand...
Click to collapse
Have you tried a factory reset?
I had it on unrooted stock optus rom.
I would change to a more optimised rom like ARHD or something
@nonverbose
I don't think it is that big of an issue for a factory reset but it happened again today and was fine after a few mins. Would you come to know what is causing this if I sent some kind of an error log or something. If yes pl tell me what I need to send. @marcj338
Does ARHD have internet pass through? I use my office network to download big games,etc so I need the feature. Hows ARHD better than the stock anyway?
Sent from my HTC Incredible S using XDA
FCArsenal said:
Does ARHD have internet pass through? I use my office network to download big games,etc so I need the feature. Hows ARHD better than the stock anyway?
Click to expand...
Click to collapse
Not sure about the internet pass through because I have never tried to use it so I dont know if its there
It is much smoother, Ive played with stock 3.0 and it lags and is a bit choppy
When I used ARHD, I found it a LOT smoother than stock, it has better battery life, and it more optimised. Even with OC is lasts longer. I would have kept it, but I didn't like the look of stock 3.0 compared to runnymede ports
FCArsenal said:
@nonverbose
I don't think it is that big of an issue for a factory reset but it happened again today and was fine after a few mins. Would you come to know what is causing this if I sent some kind of an error log or something. If yes pl tell me what I need to send. @marcj338
Does ARHD have internet pass through? I use my office network to download big games,etc so I need the feature. Hows ARHD better than the stock anyway?
Sent from my HTC Incredible S using XDA
Click to expand...
Click to collapse
The reason I suggested a factory reset is because I think you're experiencing major lag spikes, possibly due to background running tasks. Does it always happen when you have this pocket sensor app activated?
@markj338
I wanted to try out ARHD for a while but was unimpressed by CM so I thought of sticking to stock but later when I checked my friends Ph and saw the difference I wanted to go for it but now I think am gonna wait for ics cos I heard it's very stable. TX for ur time though! Appreciate it ..
@nonverbose
I think it's the pocket sensor but am not sure. I try out various combinations to get outta it. Sometimes I think its the go locker but I noticed 1 thing for sure ....it happens when it's really hot outside and the battery heats up too. Am trying to give as much info as possible!!
Sent from my HTC Incredible S using XDA
Wow.....everytime I try to determine the problem as to why this is happening I come up with random ideas since noting used to work. Now on my way to work the same thing happened again. It is still not responding and am posting this from my office computer. I could unlock the go lock screen by the vol button which I had configured. I could see the internet pages loading up since I was browsing when it happened suddenly. The auto rotation also works and all buttons like home, menu, search are responding but it just doesnt seem to respond when I touch the screen. I googled it and found there is something called a touch input which might be and issue. I cant do anything to stop and restart the service since the touch doesnt work. Any suggestions?
Uninstall pocket sensor and go locker.
Really ...y do you think they are the problem.
Sent from my HTC Incredible S using XDA
FCArsenal said:
Really ...y do you think they are the problem.
Sent from my HTC Incredible S using XDA
Click to expand...
Click to collapse
You asked for suggestions. Its a process of elimination.
FCArsenal said:
Really ...y do you think they are the problem.
Sent from my HTC Incredible S using XDA
Click to expand...
Click to collapse
Check where exactly is the proximity sensor and make sure nothing is blocking it (dirt) and/or is still exactly where it should be (if you drop a phone it might get dislocated). This would explain sudden unresponsiveness since phone might think it is in call mode (proximity sensor detects presence of your head and disables the screen while you are dialling).
I had go launcher n pocket sensor way before this started happening. I don't think that's the problem. Its something to do with the touch input but can't figure out the cause.
N yeah I remember dropping it once. My SD card is almost full since I got a lotta media n apps. Would buying a new high capacity SD card do the trick? I remember my laptop lagging due to an almost full hard disk ...
Sent from my HTC Incredible S using XDA
It happened again today. I received some bluetooth files and its not responding now. Menu buttons work but the touch is being a *****. It happens so randomly n it not even funny. grrrr
Im having an annoying issue with my Vivid where when im trying to play a video in the youtube app, and in landscape mode (full screen) my screen ALWAYS dims and its annoying since the video sometimes cant be seen clearly because of it. I flip it back to portrait and it goes full brightness.again. Anyone else have this issue? Or is there some fix?
Btw, i dont have auto brightness on, full brightness on my end. I also tried to uninstall updates and no luck. Im on stock 4.0.3 unrooted
Sent from my HTC PH39100 using Tapatalk 2
mike21pr said:
Im having an annoying issue with my Vivid where when im trying to play a video in the youtube app, and in landscape mode (full screen) my screen ALWAYS dims and its annoying since the video sometimes cant be seen clearly because of it. I flip it back to portrait and it goes full brightness.again. Anyone else have this issue? Or is there some fix?
Btw, i dont have auto brightness on, full brightness on my end. I also tried to uninstall updates and no luck. Im on stock 4.0.3 unrooted
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
I haven't experienced this problem. Have you cleared the app cache and data? Im on deodexed stock ics rooted.
lmftmf said:
I haven't experienced this problem. Have you cleared the app cache and data? Im on deodexed stock ics rooted.
Click to expand...
Click to collapse
Just did. No luck. I updated OTA from stock GB. Did not want to go this far, but im gonna try a factory reset to see if starting clean helps since i kept my GB data when I updated
Sent from my HTC PH39100 using Tapatalk 2
mike21pr said:
Just did. No luck. I updated OTA from stock GB. Did not want to go this far, but im gonna try a factory reset to see if starting clean helps since i kept my GB data when I updated
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Sometimes thats the only option i would run the RUU to be completely certain something didnt get borked during the OTA upgrade.
I have this problem too! I'm running stock ICS
Sent from my HTC PH39100 using XDA
Just finished setting everything up again. Factory reset seems to have done the trick. Ill update if it happens again
Sent from my HTC PH39100 using Tapatalk 2
It friggin did it again!!!! Im outta ideas....
Edit: I think I figured it out... Sensor still working even if auto brightness is off, I have a pen with an integrated flashlight, and after pointing the light to the sensor in the phone while playing the video, sure enough brightness went back up. Same issue (or feature) that the capacitive buttons have, annoying nevertheless
Sent from my HTC PH39100 using Tapatalk 2
mike21pr said:
It friggin did it again!!!! Im outta ideas....
Edit: I think I figured it out... Sensor still working even if auto brightness is off, I have a pen with an integrated flashlight, and after pointing the light to the sensor in the phone while playing the video, sure enough brightness went back up. Same issue (or feature) that the capacitive buttons have, annoying nevertheless
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Could be an issue with your ambient light sensor?
lmftmf said:
Could be an issue with your ambient light sensor?
Click to expand...
Click to collapse
Maybe... Because I noticed that the same time the issue is ocurring, when I switch with auto brightness from full brightness, the screen stays the same till after i shut off the screen and wake it back up which is where the sensor kicks in
Sent from my HTC PH39100 using Tapatalk 2
Hi,
I'm having the exact same issue as you. It happens regardless of how high the screen brightness is, and whether autobrightness is on or off.
It's nice and bright on vertical view, then as soon as you rotate it to fullscreen, the screen dims and it's almost impossible to see the video.
I'm running stock 4.0.3 on a Sensation XE, and I've done multiple full factory resets on my device, no joy.
Any ideas?
Has anyone had any power button issues? Or heard of anything similar.
Suddenly found that the power button was completely unresponsive, in that it wouldn't wake the sleeping device, fortunately I'd enabled volume buttons to wake, once device was awake, power button still did nothing, so I couldn't get to access reboot menu, so installed Franco's reboot application, rebooted, and it's working absolutely fine again? As if nothing was ever wrong, makes me suspect a software rather than hardware related problem.
Strange? Familiar? Can anyone relate?
I've had many previous, non nexus devices which suffered from dead power button, but nothing of late, plus the device is only weeks old.
I'm running latest Chroma build (as per sig) so asop.
Sent from my Nexus 6
Not exactly experiencing the same problem, but I've been having this odd power-button issue since today. If I leave my phone locked/screen off for about 5 minutes, it does not respond to a press of the power button. The weird thing is, it does respond after exactly 3 presses, every time. It's a non-issue when Smart Unlock is engaged on my home wifi-network. On 5.0.1. Chroma, haven't updated it in a week or two.
Aruarian said:
Not exactly experiencing the same problem, but I've been having this odd power-button issue since today. If I leave my phone locked/screen off for about 5 minutes, it does not respond to a press of the power button. The weird thing is, it does respond after exactly 3 presses, every time. It's a non-issue when Smart Unlock is engaged on my home wifi-network. On 5.0.1. Chroma, haven't updated it in a week or two.
Click to expand...
Click to collapse
Sounds like a different issue.
Mine was a complete one of, switch made me suspect software asop issue.
Monitoring.....
Sent from my Nexus 6
Happened again, dead power button, woke by volume buttons, reboot, works fine again.
So this isn't intermittent, in that when it fails it won't work again until restart, which says to me software.
I'm now using this thread as log. To see if RMA necessary.
Chroma 5.1 22/03/2015
Sent from my Nexus 6
Happened again later in the day.
Sent from my Nexus 6
ben_pyett said:
Has anyone had any power button issues? Or heard of anything similar.
Suddenly found that the power button was completely unresponsive, in that it wouldn't wake the sleeping device, fortunately I'd enabled volume buttons to wake, once device was awake, power button still did nothing, so I couldn't get to access reboot menu, so installed Franco's reboot application, rebooted, and it's working absolutely fine again? As if nothing was ever wrong, makes me suspect a software rather than hardware related problem.
Strange? Familiar? Can anyone relate?
I've had many previous, non nexus devices which suffered from dead power button, but nothing of late, plus the device is only weeks old.
I'm running latest Chroma build (as per sig) so asop.
Sent from my Nexus 6
Click to expand...
Click to collapse
Do you have a screen protector covering the sensor? If so that's probably the issue, disable ambient display and see if you can reproduce the problem.
Sent from my Nexus 6 using XDA Free mobile app
No screen cover, just a ringke slim cover. But I don't think that covers the sensors.
Sent from my Nexus 6
ben_pyett said:
No screen cover, just a ringke slim cover. But I don't think that covers the sensors.
Sent from my Nexus 6
Click to expand...
Click to collapse
No that wouldn't, still try turning off ambient display and see if the issue persists.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
No that wouldn't, still try turning off ambient display and see if the issue persists.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Feature is disabled. ?
Sent from my Nexus 6
ben_pyett said:
Feature is disabled. ?
Sent from my Nexus 6
Click to expand...
Click to collapse
It was already disabled when you were having the problem?
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
It was already disabled when you were having the problem?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry, yes, looks like the option has always been disabled.
Sent from my Nexus 6
ben_pyett said:
Sorry, yes, looks like the option has always been disabled.
Sent from my Nexus 6
Click to expand...
Click to collapse
Then short of backing up and doing a clean install I am out of ideas, sorry.
Sent from my Nexus 6 using XDA Free mobile app
Cheers. Literally only just did that for stable Chroma 22/03 version... Will wait until further versions come out and will consider doing that. Cheers anyway
Sent from my Nexus 6
26/03/2015 Happened about four times today. Rebooted once, another time out went away after a bit... So sounding like could be hardware for first time... Hmmm
Sent from my Nexus 6
happened to me today, like it was in a deep sleep and took ages for the power button to work.
Im on stock 5.1
Happened once 31/01 soft reboot resolved it
Still believe this is software.
ben_pyett said:
26/03/2015 Happened about four times today. Rebooted once, another time out went away after a bit... So sounding like could be hardware for first time... Hmmm
Sent from my Nexus 6
Click to expand...
Click to collapse
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
mgear356 said:
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
Click to expand...
Click to collapse
I would get this issue on Chroma if I had enabled the option Display--Ambient Display--Overwrite Value.
See if thats enabled, and if so, try with it disabled for awhile.
mgear356 said:
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
Click to expand...
Click to collapse
I was clean install on 5.1 but not since, although did import apps and data from TB not that it should impact it at all. Only ever run Chroma, jumped straight to it after initial unlock.
Fortunately volume keys always wake - so far.
Let me know how you get on - in this thread.
If I find it continues to happen then I'll consider clean install and then maybe even a replacement device.
Everything was fine after last reboot.
Immediately after plug in into charger, the power button stop working. First time experiencing this. Able to try this to guys?
Edit: I toggled 2 things.. Enabled / disabled ambient display overwrite defaults and screen on when plug / unplug charger..
Power button is working again without any restart.. @githyanki @ben_pyett
So I just got my midnight black oneplus 3T. Love the phone, battery life everything. However, during calls, mainly on 7.1.1 my screen turns on and I press buttons with my face by accident, it's seriously annoying and because of it I've had the phone in a box for the past 5 days. I currently have an iPhone 7 plus and I reeeallly want to give the phone a chance but this is seriously annoying!
Does anyone have any tips for me at all?
Cheers
Jonny:crying:
Jonnyn93 said:
So I just got my midnight black oneplus 3T. Love the phone, battery life everything. However, during calls, mainly on 7.1.1 my screen turns on and I press buttons with my face by accident, it's seriously annoying and because of it I've had the phone in a box for the past 5 days. I currently have an iPhone 7 plus and I reeeallly want to give the phone a chance but this is seriously annoying!
Does anyone have any tips for me at all?
Cheers
Jonny:crying:
Click to expand...
Click to collapse
Are you keeping the top part of phone a bit away? Maybe that could be the reason or simply the proximity sensor is faulty. You could try a reset and if the problem is still there get it checked form OnePlus.
Sent from my OnePlus3T using XDA Labs
I have this bug too on 7.1.1/4.1.3. Proximity sensor is tested to be working.
I read somewhere that it's a bug in the oneplus dialer, and sideloading the goggle pixel dialer fixes the issue, but I could not test it with the Magisk module, because I ran into a different bug, and lost networking until I reinstalled Magisk from scratch...
Try it at your own risk.
fricy81 said:
I have this bug too on 7.1.1/4.1.3. Proximity sensor is tested to be working.
I read somewhere that it's a bug in the oneplus dialer, and sideloading the goggle pixel dialer fixes the issue, but I could not test it with the Magisk module, because I ran into a different bug, and lost networking until I reinstalled Magisk from scratch...
Try it at your own risk.
Click to expand...
Click to collapse
This sounds good I'll try it later. Thank you sir!
fricy81 said:
I have this bug too on 7.1.1/4.1.3. Proximity sensor is tested to be working.
I read somewhere that it's a bug in the oneplus dialer, and sideloading the goggle pixel dialer fixes the issue, but I could not test it with the Magisk module, because I ran into a different bug, and lost networking until I reinstalled Magisk from scratch...
Try it at your own risk.
Click to expand...
Click to collapse
This sounds good I'll try it later. Thank you sir!
bonham1988 said:
Are you keeping the top part of phone a bit away? Maybe that could be the reason or simply the proximity sensor is faulty. You could try a reset and if the problem is still there get it checked form OnePlus.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Definitely not keeping the phone away from my face at all. Another user said its a software bug. I might just have to try lineage OS for a bit.
Thanks for the tip! ^_^
It happens to me, too.
Sent from my ONEPLUS A3003 using Tapatalk
Hello after i updated my phone to oreo it lags sometimes. I assume that it is kind of a Glance problem cause when i turn off glance there is no lag at all(pretty strange i know). I contacted support about this 2 times and they said restart the phone and clear the chace of the app that causes the issue. Neither of them work. Does anyone else facing this issue?
Toedwarrior said:
Hello after i updated my phone to oreo it lags sometimes. I assume that it is kind of a Glance problem cause when i turn off glance there is no lag at all(pretty strange i know). I contacted support about this 2 times and they said restart the phone and clear the chace of the app that causes the issue. Neither of them work. Does anyone else facing this issue?
Click to expand...
Click to collapse
I do not have this problem, everything works well and works noticeably better than the beta
Sent from my Nokia 8 using Tapatalk
The only lag I have is with the fingerprint senzor. If I doubletap the screen and then I press the fingerprint, it unlocks instantly. If I press the fingerprint with the screen off, it takes a while before the screens turns on (~1.5sec). Maybe this is how it is on the Nokia 8, but on the HTC 10 was lightning fast.
I will reset the phone if the problem presist s i will send the phone to service
Sent from my Nokia 8 using XDA Labs
stuffynet said:
The only lag I have is with the fingerprint senzor. If I doubletap the screen and then I press the fingerprint, it unlocks instantly. If I press the fingerprint with the screen off, it takes a while before the screens turns on (~1.5sec). Maybe this is how it is on the Nokia 8, but on the HTC 10 was lightning fast.
Click to expand...
Click to collapse
Had a 10 as well as don't really notice that much difference. What I will say is that battery performance trounces the 10 so I'd imagine it's pulling the Nokia from deep sleep that causes the minor lag.
always restart wherever it lags. it lags with the amount of oreo update.
Did you tryed a factory reset? I did it and it is more responsive then before. But safe needed data first. Backup before factory reset!
Powered by Nokia 8
2WildFirE said:
Did you tryed a factory reset? I did it and it is more responsive then before. But safe needed data first. Backup before factory reset!
Powered by Nokia 8
Click to expand...
Click to collapse
Yeah i am going to do that
Sent from my Nokia 8 using XDA Labs
stuffynet said:
The only lag I have is with the fingerprint senzor. If I doubletap the screen and then I press the fingerprint, it unlocks instantly. If I press the fingerprint with the screen off, it takes a while before the screens turns on (~1.5sec). Maybe this is how it is on the Nokia 8, but on the HTC 10 was lightning fast.
Click to expand...
Click to collapse
I think it is so the phone isnt getting false attempts to unlock it, only my opinion though, i am not saying that is deffo the reason.
I just have the same problems with my Nokia 8 since 2 days.
Fingerprint or power-button unlock is sometimes painfully slow. Maybe up to 5 seconds.
I have the Android 8.1 Oreo update installed since some months already and also the newest security patch.
I have read, it's a general problem of the 8.1 version, that unlocking gets slowed down.
Anyone has a solution so far? Factory reset doesn't seem to help always (I didnt try), but maybe downgrading to Android 8?
nokia 8 unlock delay fixed
I have same issue with my nokia 8 after trying so many methodes. I have found a solution which is working for me
Go to Setting -display settings- advance- turn off Glance feature
this work for me give it try hopfully it will work Inshallah
Naveedahsan said:
I have same issue with my nokia 8 after trying so many methodes. I have found a solution which is working for me
Go to Setting -display settings- advance- turn off Glance feature
this work for me give it try hopfully it will work Inshallah
Click to expand...
Click to collapse
No, this didn't work for me at all.
I think it's related to deep sleep / doze feature. Try to restore factory settings and wipe clean data + cache of the phone and see if it will help. There's so many things that can cause this that we're not able to help any of you.
KonikoO said:
I think it's related to deep sleep / doze feature. Try to restore factory settings and wipe clean data + cache of the phone and see if it will help. There's so many things that can cause this that we're not able to help any of you.
Click to expand...
Click to collapse
Thanks, I know, but that also didn't help me. Currently I am following this bug report at Google:
https://issuetracker.google.com/issues/109710373
It seems to be an issue witht he June Android Security Patch... a lot of Pixels are having the same problem.
I don't thinks it's the June 2018 update problem. If u look at the dates on this thread, the problem started after the oreo 8.0 update back in November 2017. Hopefully it'll be fixed in the android 9 update coming soon. I updated straight to 8.1 after unboxing so I don't know if this problem was around during nougat
Same here
I have the same error.