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
Related
Well I've been running gingervolt on my phone and it has been running fine until now. Today my softkeys won't light up anymore unless I go to settings and click on the screen brightness that's when they come on but once it times out and goes black they won't come back on when I unlock it. Also when I received a call and slide the screen up for some reason I can't hear anything and the phone hangs up. Does anyone know what can I do to fix this issue? Thanks. Version 2.3.4 running gingervolt 1.3
Sent from my VS910 4G using XDA App
robledjl said:
Well I've been running gingervolt on my phone and it has been running fine until now. Today my softkeys won't light up anymore unless I go to settings and click on the screen brightness that's when they come on but once it times out and goes black they won't come back on when I unlock it. Also when I received a call and slide the screen up for some reason I can't hear anything and the phone hangs up. Does anyone know what can I do to fix this issue? Thanks. Version 2.3.4 running gingervolt 1.3
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
This happened to me the first night gv 1.3 was released. It went away the next day though. Re-flash?
Ok. I will reflash and hopefully that would fix it
Sent from my AT100 using Tapatalk
This happens on my phone once in a while. I just open up adjbrightness and problem solved.
Sent from my VS910 4G using XDA App
This will sound weird but what I do when this happens (usually a restart of device) is bring the phone's screen to my laptop screen momentarily, or just hit it with a beam of light from my 700 lumen flashlight It's quick and easy
adrenaline_rush said:
This will sound weird but what I do when this happens (usually a restart of device) is bring the phone's screen to my laptop screen momentarily, or just hit it with a beam of light from my 700 lumen flashlight It's quick and easy
Click to expand...
Click to collapse
haha, very MacGyver...Going into Settings > Display and toggling auto brightness on/off would probably accomplish the same thing.
jamrwoo said:
haha, very macgyver...going into settings > display and toggling auto brightness on/off would probably accomplish the same thing. :d
Click to expand...
Click to collapse
no it won't jamrwoo !!!!!!
Alright guys I reflashed it And it fixed the soft key issues but im still having problems answering the phone. When I slide it up to answer i can't hear anything... Timer keeps going but I have to hang up and call them back... Sometimes it just hangs up when I try answering. Does anyone have any other suggestions? Thanks a lot for reading my post.
Sent from my AT100 using Tapatalk
robledjl said:
Alright guys I reflashed it And it fixed the soft key issues but im still having problems answering the phone. When I slide it up to answer i can't hear anything... Timer keeps going but I have to hang up and call them back... Sometimes it just hangs up when I try answering. Does anyone have any other suggestions? Thanks a lot for reading my post.
Sent from my AT100 using Tapatalk
Click to expand...
Click to collapse
With everything that you've tried, it's starting to sound like it might be a hardware issue. If that's the case, you might have to send it in to get it fixed.
So should i restore to stock and see if that fixes the problem? I guess either way I need to restore to stock if I need to send it off to get fixed right?
Sent from my AT100 using Tapatalk
robledjl said:
So should i restore to stock and see if that fixes the problem? I guess either way I need to restore to stock if I need to send it off to get fixed right?
Sent from my AT100 using Tapatalk
Click to expand...
Click to collapse
Couldn't hurt. I would do it if nothing else has worked.
Sent from my VS910 4G using Tapatalk
As stated, screen will not go off via timeout or power button tap. Power button is recognized and will bring up shut down menu like normal.
Device is rooted (thanks DG) and had been running well for over a week. Defrosted all apps from tibu in case I got over zealous but no better. A factory reset has not cleared it up either. Hoping the oneclick from the root package will correct the issue, but thats not until I get home later this evening.
Has anyone experienced / recovered from this issue?
Smart stay is turned off
I've had noticeable lag like a few seconds and sometimes I wonder if it's going to shut off but it always does. Better set a dark lock screen wallpaper to conserve your battery
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I know this is kind of basic, but what is your setting here:
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!
3496255310
papashex said:
Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!
Click to expand...
Click to collapse
I'm having the same problem, I rooted through vroot.... what do you mean one click fixed it little my incite would be helpful....
thank you
Mine just did this, scared the hell out of me It also didn't go into deep sleep before it started. (Not rooted).
Pulled the battery, waited 30 seconds, plugged it back in.... same thing. Waited a few minutes, seems to have sorted itself out.
Scary....
This is definitely a software bug and it is related to the Headphone detection bug that people are having too (it's actually the same bug causing both issues). This happens to me quite often after I restart my phone. It's kind of like the phone hangs during the startup process. I've also noticed that the wifi/bluetooth status that was present before restarting the phone (i.e. whether they on/off) doesn't get applied until the bug sorts itself out.
For me sometimes this works: open an app like Chrome and then hit the home button to get back to your launcher. This works 95% of the time for me. I'm wondering if it has something to do with not having Touchwiz set as the default launcher.
I'm experiencing this same problem. If I don't manually turn the screen off by tapping the power button, the screen will not timeout.
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.
Hello and Happy Turkeyday to all. I have an issue with my wife's note. When she gets any notifications they turn the screen on and it doesn't turn off. I feel pretty knowledgeable about the android O.S. in a whole, I have my S5 rooted and running AICP. I just can't figure out why the notifications cause the screen to stay on. Has anyone else had this problem maybe you could help shed some light on my issue. Thanks in advance.
Is the phone rooted?
Sent from my SM-N910T using Xparent Pink Tapatalk 2
No she won't let me root her phone.
Same problem
I have the exact same problem on my Note 4 (N910F).
My phone is rooted and I have had the problem from the start.
I am also running a custom kernel now but the problem persists.
Any ideas on why this is happening anyone? I've got it to not turn the screen on for a notification but now it won't turn off when plugged in.
Turn off the lock screen notifications, or everything you can on the lock screen settings, most likely something is causing the screen to wake lock. My bet is the weather widget.
Sent from my SM-N910T using XDA Free mobile app
I just searched for the same problem on the Galaxy s5 and someone said to download wakelock-detector to see if it's an app.
Will keep you updated if it helps.
Bullet_King1996 said:
I just searched for the same problem on the Galaxy s5 and someone said to download wakelock-detector to see if it's an app.
Will keep you updated if it helps.
Click to expand...
Click to collapse
So a little update, so far, my problem seems to be fixed.
After the app told me that Dsploit was causing a lot of screen-on time, I disabled the app.
Haven't had it happen so far today so I hope this helps you too.
Bullet_King1996 said:
So a little update, so far, my problem seems to be fixed.
After the app told me that Dsploit was causing a lot of screen-on time, I disabled the app.
Haven't had it happen so far today so I hope this helps you too.
Click to expand...
Click to collapse
Can anyone else have other fix? I have new note 4 with rom stock and very few apps (5-8 apps)
the "Wakelock Detector-Save Battery" app requird root this not my phone so I can't root for now.
If you have very few apps installed, uninstall those apps one by one to see which one is potentially keeping the screen on. Otherwise, do a factory reset, clear cache; also ensure power button is sticky and is fully functional.
u1988 said:
Can anyone else have other fix? I have new note 4 with rom stock and very few apps (5-8 apps)
the "Wakelock Detector-Save Battery" app requird root this not my phone so I can't root for now.
Click to expand...
Click to collapse
arjun90 said:
If you have very few apps installed, uninstall those apps one by one to see which one is potentially keeping the screen on. Otherwise, do a factory reset, clear cache; also ensure power button is sticky and is fully functional.
Click to expand...
Click to collapse
Thx, What I did in the end is disble a few stock apps (I add a pic)
And set the Screen time to 30 sec and shut down the deivce got the battery out turn on, set the Screen time to 1 min and shut down...
a few times in the end got it back to the time I want, all of this fore "soft" reset the database of the settings
..now for about a week+ the problems won't show again :highfive:
Boot into recovery and clear cache
or factory reset like everyone said
Great to hear all is well. Please tell me that you're going to root.
u1988 said:
Thx, What I did in the end is disble a few stock apps (I add a pic)
And set the Screen time to 30 sec and shut down the deivce got the battery out turn on, set the Screen time to 1 min and shut down...
a few times in the end got it back to the time I want, all of this fore "soft" reset the database of the settings
..now for about a week+ the problems won't show again :highfive:
Click to expand...
Click to collapse
arjun90 said:
Great to hear all is well. Please tell me that you're going to root.
Click to expand...
Click to collapse
It's not my phone, so for now no need to root .
btort1 said:
Boot into recovery and clear cache
or factory reset like everyone said
Click to expand...
Click to collapse
I gave you Another solution.
Has anyone else noticed a reduced ability of the voice to text capability, that it can no longer translate long phrases? I've also noticed that it often connects on the first try during a search, but quickly cancels itself, needing a second try to get it right.
That happened before the update to me it SUCKED.. TRY resetting voice cleaning cache and rebooting once or twice
ganggreen30 said:
That happened before the update to me it SUCKED.. TRY resetting voice cleaning cache and rebooting once or twice
Click to expand...
Click to collapse
Ok, crud, not finding the specific app. What the heck am I supposed to look for?!?
Sent from my XT1254 using XDA Free mobile app
Update, I was gonna do a factory reset after an update/backup, and the Turbo went through the app updating thing like when switching to ART. When I took LP, it did it, but I guess not 100%. As right now, all searches go through on the first try. I WAS thinking of re-ARTing the Turbo in the first place, but had no knowledge how to force it. If someone knows how, PLZ post!
Ok, looks like the was some kind of conflict with Better Keyboard 8's voice-to-text. A quick round trip to safe mode seems to have ironed things out for now.
Sent from my XT1254 using XDA Free mobile app