Hi, after using my droid 3 for less than a week, I turned it on one time, and it bypassed the lock screen. I see it for a split second, then it goes away w/out me doing anything. This is not good, like if it turns on in my pocket, I'll be doing who know what on my phone... please help as soon as you can. Thanks!
Same issue with mine. I can generally get it to bypass the lockscreen on purpose if I do something weird, like unlock it right after I open the keyboard or play with the volume buttons.
Mine did this so I did a factory reset and I've not had that issue again since. Its been a week.
Sent from my DROID3 using XDA App
spacecasespiff said:
Mine did this so I did a factory reset and I've not had that issue again since. Its been a week.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Does anyone know how to fix w/out a factory reset?
I fixed the problem by changing the value of the Security Lock Timer in Settings > Location & Security
Hi all, randomly when trying to exit apps or close them my back and home button do not respond. It takes five minutes and randomly repairs itself. Anyone know a fix as I want to throw this phone!
htconem7max said:
Hi all, randomly when trying to exit apps or close them my back and home button do not respond. It takes five minutes and randomly repairs itself. Anyone know a fix as I want to throw this phone!
Click to expand...
Click to collapse
This is a calibration issue. Others have confirmed to fix this by navigating to Settings>Language & Keyboard>HTC Sense Input>Advanced>Calibration Tool/Reset.
Try resetting it first, then calibrating.
--
Say thanks if I was of help!
Sent from my HTCONE using xda app-developers app
aarongillion63 said:
This is a calibration issue. Others have confirmed to fix this by navigating to Settings>Language & Keyboard>HTC Sense Input>Advanced>Calibration Tool/Reset.
Try resetting it first, then calibrating.
--
Say thanks if I was of help!
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Sadly this hasn't helped. I'm going to update to sense 6.0 and see if it works.
When I click the power button to turn on the screen, only in the immediate moment following does the screen recognize my touch. Sometimes, this means I can unlock the device, pull open settings, or open an app (that has a lock-screen widget). Once there, I can do nothing, until the screen turns off (if plugged in, nothing). If I hold the first click (like going in circles on the lock-screen without letting go or unlocking), I can prolong the sensitivity for the duration of contact. All physical buttons are confirmed working. AT&T Torch working. Software is up-to-date and restored via ODIN to 4.3, then OTA to 4.4.2, so practically stock. It's the AT&T model.
Thoughts or comments?
(note, I plan to go to at&t or best buy (Samsung Rep) asap, but am not sure when I will be able to. I tried searching for something both in this forum and google for similar issues, so I apologize if this is a repeat thread- I really tried to avoid it, if so).
http://forum.xda-developers.com/showthread.php?t=2653149
Lots of people had screen issues, after the OTA 4.4 update, myself included.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Thanks for the link, After having a live chat where the at&t support agent was unable to fix the problem, she informed me I was still under warranty and sent out for a replacement device.
help me
captaincado said:
http://forum.xda-developers.com/showthread.php?t=2653149
Lots of people had screen issues, after the OTA 4.4 update, myself included.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
im in 4.3 but i think with bootloader cn9 if i upgrade to 4.4.2 touch wont work, in 4.3 no sound no mic. help
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
If you look at the bottom of the screenshot, it is not there even though it was there hours ago.
Edit: screenshot did not get attached, so linking to it here.
https://imgur.com/a/mseib7F
I had the same thing happen to me. I also use goodluck for the screenshot button, and it was still there. After a restart it came back and has not vanished again. Maybe just a fluke?
Sent from my Samsung SM-N960U1 using XDA Labs
nuclearrage said:
I had the same thing happen to me. I also use goodluck for the screenshot button, and it was still there. After a restart it came back and has not vanished again. Maybe just a fluke?
Sent from my Samsung SM-N960U1 using XDA Labs
Click to expand...
Click to collapse
Your tip fixed the problem with one caveate: After the phone booted up, after I unlocked the screen, the phone rebooted by itself. This repeated 5 times before stopping. WEIRD
I think I figured out what is causing it. If I go into the secure folder, and then let the screen timeout, when I unlock the screen again it makes the buttons disappear. I think it might be a bug in Pie and OneUI
Sent from my Samsung SM-N960U1 using XDA Labs