Related
Where is the setting that sets the lockscreen timeout to 15 seconds? I still have a huge issue with pocket dialing and would love to adjust it down to 2 seconds (improve battery life as well). I know that it's not in the apk since the default android timeout is the same with the htclockscreen deleted.
Is this a kernel issue that can't be addressed until the source is released?
Thanks for your time.
tstack77 said:
Where is the setting that sets the lockscreen timeout to 15 seconds? I still have a huge issue with pocket dialing and would love to adjust it down to 2 seconds (improve battery life as well). I know that it's not in the apk since the default android timeout is the same with the htclockscreen deleted.
Is this a kernel issue that can't be addressed until the source is released?
Thanks for your time.
Click to expand...
Click to collapse
The timeout should be in the display section of settings.
It actually most likely is part of the apk. HTC modified the settings apk to add the scenes feature in there. Most likely they either modified that part too or, even more likely, they just read the settings for the lock screen in their lock screen apk. Either way, this is what would need to be modified to allow for adjusting of the timeout. Now, that said, there may be a plethor of other places that need to be modified to allow for this change to actually work. Right now this would be a lower priority.
There is already a 15sec lockout option. Go Menu>Sound & Display>Screen Timeout (will be at the bottom of the page).
chuckhriczko said:
The timeout should be in the display section of settings.
It actually most likely is part of the apk. HTC modified the settings apk to add the scenes feature in there. Most likely they either modified that part too or, even more likely, they just read the settings for the lock screen in their lock screen apk. Either way, this is what would need to be modified to allow for adjusting of the timeout. Now, that said, there may be a plethor of other places that need to be modified to allow for this change to actually work. Right now this would be a lower priority.
Click to expand...
Click to collapse
So you're saying that on a vanilla build of android there is a setting for the lockscreen timeout, and that the default android lockscreen is part of the settings.apk?
There is already a 15sec lockout option. Go Menu>Sound & Display>Screen Timeout (will be at the bottom of the page).
Click to expand...
Click to collapse
Not the screen timeout, the lockscreen timeout. In my pocket the menu button can be pressed, then pressed again within a 15 second window to wake the device and magically start dialing. I would like to cut that 15 seconds down to a realistic 2-3 seconds.
That's a good idea and I'm interested to hear if it's possible.
tstack77 said:
Not the screen timeout, the lockscreen timeout. In my pocket the menu button can be pressed, then pressed again within a 15 second window to wake the device and magically start dialing. I would like to cut that 15 seconds down to a realistic 2-3 seconds.
Click to expand...
Click to collapse
Why not just setup a unlock pattern?
gu1dry said:
Why not just setup a unlock pattern?
Click to expand...
Click to collapse
Have you actually tried using one for even just a day...what a giant PITA
tstack77 said:
Have you actually tried using one for even just a day...what a giant PITA
Click to expand...
Click to collapse
I've used the unlock pattern since I purchased the phone, which I got my phone 9 Oct 09...
gu1dry said:
I've used the unlock pattern since I purchased the phone, which I got my phone 9 Oct 09...
Click to expand...
Click to collapse
I commend you then, I didn't last an hour inputting the damn thing every few minutes just to read a text message...but of course I don't need my phone to be that secure so the annoyance > necessity
That said, the lockscreen should be able to accommodate the both of us, and I'm just looking for a solution that works for me.
tstack77 said:
I commend you then, I didn't last an hour inputting the damn thing every few minutes just to read a text message...but of course I don't need my phone to be that secure so the annoyance > necessity
That said, the lockscreen should be able to accommodate the both of us, and I'm just looking for a solution that works for me.
Click to expand...
Click to collapse
And I was simply suggestion a possible solution. Also I have my lockscreen timeout set to 1min.
My personal recommendation: follow the directions in the thread on deleting unwanted apps to root your Hero, remount the filesystem so you can delete HtcLockScreen.apk, then buy LockbotPro & install it instead. The current version is a little buggy in the way it handles reboots (after you reboot, the Android non-HTC lockscreen becomes re-enabled and "first in line"), but it's not too hard to fix when it happens, and it works wonderfully the rest of the time.
To fix it after rebooting, you basically swat away the default Android lockscreen (menu-menu), launch Lockbot, launch its settings menu, un-check "enable lockbot", return to home, relaunch Lockbot, launch its settings menu, re-check "enable lockbot", and you're done. Looking at the changelog, it appears that the bug I just described is a fairly recent new bug, and it looks like the author is releasing updates every couple of days trying to fix it.
Note that Lockbot will "kind of" work if you don't root & delete HTC's lockscreen... but it won't work well because HTC's lockscreen is pretty aggressive about defending its turf. It's a night & day difference. (Sorry if I sound like a broken record, but as they say... there's no zealot like the reformed sinner. If I'd known how easy it would be to fix the #1 thing I hated about my Hero, I'd have done it the afternoon the first "how to root the CDMA Hero" hit the net
I can definitely say that my overall happiness & satisfaction increased dramatically after I did it. It sounds petty, but HTC's dysfunctional/useless lock screen (backed up by Android1.5's annoying & tedious default) really did annoy me to the point where I was starting to dislike my Hero. Rooting & replacing them with Lockbot really made a difference.
Thanks for the recommendation, nice to see I'm not the only one annoyed with the default lockscreen issue.
I tried out LockBot all day yesterday but it still has one major flaw, any/every button will wake the device (not just 'menu' and 'power'). Each time I pulled the phone out of my pocket the screen was on, pretty sure it's the trackball constantly getting tapped in my pocket.
Had to delete it due to battery drain. Still looking for a solution
Is there any secret to making this work better to wake up the phone. I cannot seem to hit it right to get it to unlock. Sensitivity adjust?
I like the phone otherwise.
Tap the screen quickly and firmly in the same spot two times. I have no problems with it using that method.
Train wreck for me. Double tap is horrible! I started a return through Amazon, wondering if I should try a replacement first though. I have huge lag issues too on this phone.
I am having the problem with tap to open too. There are many reviews on Amazon detailing the same thing. I sent an email to Alcatel support asking if they would be addressing this issue. I am still deciding if I want to keep the phone.
Last couple of days I have had more instances of misses with this than I had the first couple of days. But still I feel I have had better luck with the double-tap.... than many others over here so far. Usually a firm tap, with your fingers bent and the fingernails almost hitting the glass, works pretty well. But at times, even a firm tap will not work, and I have noticed that un-setting the option ( in Settings -> Gestures ) and then setting it back again gets it going again. This and the lag with loading apps may be related , and I hope Alcatel release a 5.1 update soon.
I've only had an issue with this once and a reboot fixed it. I think in some cases people are not hitting the screen firmly and quickly. Also the may not be hitting the same spot as well. I have seen other phones that use the knock unlock gesture but with a knock code and maybe some people thought they could hit the screen where ever they wanted between the 2 knocks. I'm just guessing here.
steavis00 said:
Is there any secret to making this work better to wake up the phone. I cannot seem to hit it right to get it to unlock. Sensitivity adjust?
I like the phone otherwise.
Click to expand...
Click to collapse
what i did was disable the two incoming call option in gesture, now doubletap with no problem.
Turning off "Turn Over to Mute" seems to help with tapping to wake screen, but not tap to shut off screen.
Borghi said:
Turning off "Turn Over to Mute" seems to help with tapping to wake screen, but not tap to shut off screen.
Click to expand...
Click to collapse
in my phone wake and shut off works perfectly fine,and i have turn off mute and the alarm.
goseup said:
in my phone wake and shut off works perfectly fine,and i have turn off mute and the alarm.
Click to expand...
Click to collapse
I believe I have found the root cause of the problem. Right after I got the phone I installed Nova Launcher. I started playing around and tried switching back to the stock launcher. Immediately the double tap feature started to work consistently. Hopefully it will STAY working and Nova will update their launcher to support the double tap feature fully.
Borghi said:
I believe I have found the root cause of the problem. Right after I got the phone I installed Nova Launcher. I started playing around and tried switching back to the stock launcher. Immediately the double tap feature started to work consistently. Hopefully it will STAY working and Nova will update their launcher to support the double tap feature fully.
Click to expand...
Click to collapse
I doubt if the launcher is the issue. When the screen is off the launcher is not in control of the phone, the OS is in control. Also, I use Nova Prime and have only had 1 problem with Double Tap To Wake in the past 8 days.
Shodan5150 said:
I doubt if the launcher is the issue. When the screen is off the launcher is not in control of the phone, the OS is in control. Also, I use Nova Prime and have only had 1 problem with Double Tap To Wake in the past 8 days.
Click to expand...
Click to collapse
I partly agree with your statement. As I understand Nova Prime includes support for double tap. The free app does not. Using the free app I can double tap to wake the phone, but not to sleep. Using the stock launcher, both functions work perfectly. I tried installing the Google Now launcher and it was the same as the free Nova launcher. No double tap to sleep.
I am new to Xda (or forums in general), but I had tons of issues with the double tap to wake feature not working. This was a shame because everything else I loved about this phone (only other thing I would change is a slight processor boost; a Snappy 801 would be perfect). Anyways, I finally got around the issue by performing these steps:
1-In Settings, navigate to Gestures and make sure 'Turn over to mute' is unchecked and 'Turn over to activate' is disabled.
2-Don't know if this is mandatory, but I also disabled the Func shortcuts in the Lock Screen Settings as well.
3-Reboot the device and don't touch these settings again
For some reason, I think Alcatel's software was not appropriately tested with all of these functions enabled. I am not sure, I just know I am having much higher hit rates (works almost every time) after performing the above steps.
Hope it works for you guys.
Lastly, if the double tap starts having issues again, just run a reboot and it should fix it (I just had to reboot after 30+ hours of standby).
goseup said:
what i did was disable the two incoming call option in gesture, now doubletap with no problem.
Click to expand...
Click to collapse
YAY, THIS THING WORKS FOR ME, NOW IT DOESN'T LAG, D2W AND D2S, USING STOCK LAUNCHER, tried using other premium launchers, problem is smart lock doesn't work
THANKS
---------- Post added at 09:50 PM ---------- Previous post was at 09:43 PM ----------
works well now, the only thing we need is ROOT, unlocked bootloader is easy to achieved on this phone.
Borghi said:
I believe I have found the root cause of the problem. Right after I got the phone I installed Nova Launcher. I started playing around and tried switching back to the stock launcher. Immediately the double tap feature started to work consistently. Hopefully it will STAY working and Nova will update their launcher to support the double tap feature fully.
Click to expand...
Click to collapse
Nova has it's own double tap gesture. If you want it to turn off the screen then you will have to have it call a program like "screen off" to accomplish that. DT to wake is still handled by the lockscreen.
believe me i been looking for a way to make this double tap in look screen to work better, by accident i find out that tapping very lightly wake the phone all the time.
Double-tap not working for me. Running all stock, stock launcher.
Same here I can't get the double tap to work for anything, I tried turning off the features and func but nothing, my phone has its days where it works fine and other days where it just doesn't.
Sent from my 6045I using XDA Free mobile app
My original suggestion to fix the double tap was to reboot, but I found a much quicker way. Go under gestures and turn it off and on again. Seems to work every time it gets wonky.
i notice that D2W work almost perfect while the phone on charger ...so it may be power saving mode that make the digitizer off after several minutes???!!!
Maybe it's a common issue but I haven't found any info when searching about it.
I have a P11 Pro, and since I got it, I have always been having the same issue with the tablet waking up on its own quite often, randomly, or even sometime refusing to go back to sleep.
I disabled any setting that might waking it up (tap to wake, move to wake...), and disabled several apps, but it changes nothing.
It's especially annoying since when I don't use a screen lock, with the 5 minutes stay on time I set, it keeps waking and empty the battery quite fast.
Using a screen lock reduce the issue as the tablet goes back to sleep quickly, but still doesn't solve the problem. And I don't want to use screen lock when I use the tablet at home.
Does any you know that issue, or how to fix it?
Thanks in advance!
Do you have a keyboard attached or some Bluetooth devices like mice?
Does it have a built in sensor for lid close and open when used with the original keyboardcover? That might be causing the issue then.
Did you try a factory reset?
Is the latest system update installed?
hashtowent said:
Do you have a keyboard attached or some Bluetooth devices like mice?
Does it have a built in sensor for lid close and open when used with the original keyboardcover? That might be causing the issue then.
Did you try a factory reset?
Is the latest system update installed?
Click to expand...
Click to collapse
Nothing connected.
Yeah the lid has a sensor, but it does it even when I remove the cover completely or when I leave it closed and not moving.
Yes I did several factory reset, update of the firmware, and yes I'm on the latest one.
As far I can understand, a process on the tab itself is waking up the tab randomly, I just can't put my finger on which app/function does it.
Stremon said:
Nothing connected.
Yeah the lid has a sensor, but it does it even when I remove the cover completely or when I leave it closed and not moving.
Yes I did several factory reset, update of the firmware, and yes I'm on the latest one.
As far I can understand, a process on the tab itself is waking up the tab randomly, I just can't put my finger on which app/function does it.
Click to expand...
Click to collapse
Look for battery usage details it should tell, after having show system services ensbled
hashtowent said:
Look for battery usage details it should tell, after having show system services ensbled
Click to expand...
Click to collapse
Nothing visible there either, the app that keeps waking up the tab isn't necessarily taking any battery.
I didn't mention as it is very visible from my profile, but I'm not a beginner with android, very far from it, if I'm asking here it's because I already tried all the obvious things
I am asking if anybody has the same issue and/or was able to fix it. If not, I guess it's just my unit.
You might try this
The command like this:
adb shell dumpsys batterystats --checkin
provides a statistic for wakeups, including the reasons.
Mine wakes up. Can't figure out why either but then I'm not by any means an Android ace. I turn the screen off then after some period of time it'll turn back on. Nothing in the notifications bar the screen just turns back on for no apparent reason. So yes, it is happening to someone else but no answer as to why.
hashtowent said:
Do you have a keyboard attached or some Bluetooth devices like mice?
Does it have a built in sensor for lid close and open when used with the original keyboardcover? That might be causing the issue then.
Did you try a factory reset?
Is the latest system update installed?
Click to expand...
Click to collapse
I'm sad to say that you were right, the magnetic cover was at least partially to blame for the wake events. That's a huge bummer, since I guess there is no way to fix the issue
I had this issue.
I said that notifications must not wake up the tablet and it did not appear anymore.
I know there was no notification, but it worked for me.
(in fact, sometimes, I had the impression that a notification appeared for a very short time)
LeNouveau said:
I had this issue.
I said that notifications must not wake up the tablet and it did not appear anymore.
I know there was no notification, but it worked for me.
(in fact, sometimes, I had the impression that a notification appeared for a very short time)
Click to expand...
Click to collapse
Interesting, I'll try that too, thanks
I have the plus not the pro but check if near to wake up is on under the AI Experience Center in settings.
hungmung said:
I have the plus not the pro but check if near to wake up is on under the AI Experience Center in settings.
Click to expand...
Click to collapse
Everything is disabled there.
But I am quite convinced it comes from the smartcover, as since I enterily removed it, I don't have the issues anymore and the battery lasts weeks (with light usage) instead of 2 days like before.
Issue is that there is no way to disable the smart cover magnet...
Stremon said:
Everything is disabled there.
But I am quite convinced it comes from the smartcover, as since I enterily removed it, I don't have the issues anymore and the battery lasts weeks (with light usage) instead of 2 days like before.
Issue is that there is no way to disable the smart cover magnet...
Click to expand...
Click to collapse
That is probably it. I just thought I'd offer I had similar happen and had accidentally turned that on so it was turning on every time anything moved near it.
hungmung said:
That is probably it. I just thought I'd offer I had similar happen and had accidentally turned that on so it was turning on every time anything moved near it.
Click to expand...
Click to collapse
Thanks, that indeed makes sense.
And I really wish it was just that.
I'll try again with the smart cover to see if I can do anything about it.
It's the official magnetic cover so it's a huge bummer that it causes issues...
Stremon said:
Interesting, I'll try that too, thanks
Click to expand...
Click to collapse
Hi, I was looking for a solution to the waking up of the screen. In the ¨AI Experience Center¨ there is an option called ¨automatically screen light-up¨. I turned this off, because it said that if sensor detects a face, the screen lights up, and also "other" objects can trigger this screen light up. I suppose the cover is detected while closed. Other object in the range of 0.5m can also trigger this light up. Also deactivated the notifications icons in the status bar, if not doing this, it continues to light up the screen in my P11.
Mine does the same thing...just sitting there and all of a sudden the screen lights up.
Solution:
Settings -> Display -> Lock Screen -> When to show
Turn "new notification" off
Has anyone else got this bug? After locking the phone, the screen will stay active (even though the display is off) for around a second.
I've noticed the fingerprint icon flashes once after a second at the same time.
It's quite annoying if like me, you lock it and immediately shove it into your pocket within a second, as I sometimes unlock it to find I'm in an email or an app I didn't remember being in.
jonnyguitar said:
Has anyone else got this bug? After locking the phone, the screen will stay active (even though the display is off) for around a second.
I've noticed the fingerprint icon flashes once after a second at the same time.
It's quite annoying if like me, you lock it and immediately shove it into your pocket within a second, as I sometimes unlock it to find I'm in an email or an app I didn't remember being in.
Click to expand...
Click to collapse
I have seen other people report this as well.
jonnyguitar said:
Has anyone else got this bug? After locking the phone, the screen will stay active (even though the display is off) for around a second.
I've noticed the fingerprint icon flashes once after a second at the same time.
It's quite annoying if like me, you lock it and immediately shove it into your pocket within a second, as I sometimes unlock it to find I'm in an email or an app I didn't remember being in.
Click to expand...
Click to collapse
Yeah, but you need to be quite quick to trigger something on the screen. I tried to do it on purpose and I can replicate the issue 9 out of 10 times )).
Hoping for a fix in the next update.
This is getting worse. Screen stays active around 3 seconds after locking it. I can see there is a quick refresh of the lock screen when it's really locked. It's really annoying now as I feel like I need to wait for this until I can safely put it in my pocket.
this doesn't happen when using nova launcher's gestures (double tap => lock screen). maybe works with an 3rd party app from playstore too, or custom kernel with double tap to sleep or some magisk mod?
seadersn said:
this doesn't happen when using nova launcher's gestures (double tap => lock screen). maybe works with an 3rd party app from playstore too, or custom kernel with double tap to sleep or some magisk mod?
Click to expand...
Click to collapse
What lock method do you use in Nova? Accessibility, Device Admin, or root?
ouch, now you got me... I think it was accessibility. I took the one which enabled fingerprint usage after locking via nova gesture. I think it was accessibility, jep
edit: had time to look at phone now, it's accessibility
seadersn said:
ouch, now you got me... I think it was accessibility. I took the one which enabled fingerprint usage after locking via nova gesture. I think it was accessibility, jep
edit: had time to look at phone now, it's accessibility
Click to expand...
Click to collapse
Okay. accessibility or root. I still get that delay after locking, even with Nova double tap. It's just one blink a couple seconds after locking. I notice the clock blink once. Honestly, I wouldn't have even noticed it had it not been posted here..
seadersn said:
this doesn't happen when using nova launcher's gestures (double tap => lock screen). maybe works with an 3rd party app from playstore too, or custom kernel with double tap to sleep or some magisk mod?
Click to expand...
Click to collapse
Yep, I uses Nova double tap to sleep/Accessibility and do not have this issue
+1 on using Nova Launcher. I cannot produce this problem if i tried.
I need some advice on troubleshooting this one.
Brand new P7P, turned on Tap to Wake and "Always show time and info" on the lockscreen. It only ever works after a reboot *before* I log in the first time. Once I log in,that's it,screen is black when I lock it and it won't tap to wake.
I've removed the screen protector in case it was messing with the proximity sensor. I ran the phone in safemode and both *do* work in safemode,so I suspect it's an app on startup causing this.
What I need help with is how can I whittle down the culprit without removing all the apps one by one? Is there an app that will allow me to stop apps starting up at boot time and add them one by one?
dunetails said:
I need some advice on troubleshooting this one.
Brand new P7P, turned on Tap to Wake and "Always show time and info" on the lockscreen. It only ever works after a reboot *before* I log in the first time. Once I log in,that's it,screen is black when I lock it and it won't tap to wake.
I've removed the screen protector in case it was messing with the proximity sensor. I ran the phone in safemode and both *do* work in safemode,so I suspect it's an app on startup causing this.
What I need help with is how can I whittle down the culprit without removing all the apps one by one? Is there an app that will allow me to stop apps starting up at boot time and add them one by one?
Click to expand...
Click to collapse
@zetsumeikuro wait,I don't get what's so funny?
Mine works on every part of my lock screen.
Any chance you're using lift to wake? Besides that, I have everything else on the same as you.
Edit: Just reread your post. Do you have a lot of apps? You could force stop every single one of them and test to see what happens to be sure that it's an app.
Curiousn00b said:
Mine works on every part of my lock screen.
Any chance you're using lift to wake? Besides that, I have everything else on the same as you.
Edit: Just reread your post. Do you have a lot of apps? You could force stop every single one of them and test to see what happens to be sure that it's an app.
Click to expand...
Click to collapse
Yeah I have quite a few,but I think I'd rather try this first than start uninstalling and reinstalling the lot.
Not fixed,but getting somewhere. This is related to Bluetooth in some way.
If I turn off Bluetooth and reboot the phone,AOD works. I unlock the phone,it still works.
If I turn on Bluetooth AOD immediately breaks again until I turn off Bluetooth AND reboot.
I thought it might be my fitness band so disconnected and uninstalled the app, but the problem persisted. I have no other devices permanently using Bluetooth, so I'm starting to think this is a Bluetooth bug rather than a specific app now
dunetails said:
Not fixed,but getting somewhere. This is related to Bluetooth in some way.
If I turn off Bluetooth and reboot the phone,AOD works. I unlock the phone,it still works.
If I turn on Bluetooth AOD immediately breaks again until I turn off Bluetooth AND reboot.
I thought it might be my fitness band so disconnected and uninstalled the app, but the problem persisted. I have no other devices permanently using Bluetooth, so I'm starting to think this is a Bluetooth bug rather than a specific app now
Click to expand...
Click to collapse
If the fitness band allows you to take pictures remotely, it is possible that it recognizes it as a keyboard and that this interferes due to some bugs
PaulBW said:
If the fitness band allows you to take pictures remotely, it is possible that it recognizes it as a keyboard and that this interferes due to some bugs
Click to expand...
Click to collapse
Good point. This is why I tried to uninstall the app and disconnect the fitness band entirely,just to rule it out. Unfortunately,even once uninstalled,after a reboot with BT off AOD worked,but the moment I turned BT on AOD broke.
I can't think of any other apps using the BT at the moment but having a think. Will post more info if/when I get it.
Finally figured it out thanks to the hint by LaNy_6. This *is* down to Android Auto, but it’s not immediately obvious how or why.
To fix I went to Settings > Apps
Select See All Apps
From the top right overflow menu select Show System
Scroll Down to Android System
Select Notifications
Ensure Car Mode is selected
When I did this, I saw LaNy_6’s screenshot for the Android System notification that says “Driving App is running – tap to exit driving app” in my notification shade.
After doing this, AOD/tap to wake/lift to wake all suddenly work as expected.
Please note that upon rebooting the Driving App notification shows again and you have to tap it to go away. Again,no idea why.
I have no idea why, but I’m guessing every reboot the phone was put in to driving mode. I have never connected it to a car, there’s no reason for this to happen, but because I didn’t see the notification it never got exited from it seems. There’s no other indicators that it’s in driving mode, the phone works as normal other than the AOD problem.