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
Related
I have had the payed version of Lock 2.0 since there was an option to buy but since I got my Nexus One it has now become pretty much unusable. The sad part is that it is better than the lock button that is on the top of the phone cause it lets you bring up the lock screen by pressing your track ball. I love all the different back grounds and sounds you can download and how they stay in a folder and not in your app draw (which is really annoying). Now the thing I don't like is that when you press the volume buttons when the phone is locked you can and will turn down or up the volume on accident and this is why this app is now unusable. Can it really be that hard to add an option to disable these buttons? I have emailed Android Apps and they say the reason the volume button does that is for when you are listening to music and thats great but whats the use if when you get a call or text and you can't hear it cause you turned the volume down to 0 on accident. I emailed them today again and asked if they could update their app and I hope they do. The reason I started this thread is so anybody could comment on this problem with I have to say is probably my second favorite app on the market. I will also email them a link to this thread so they can see what everybody thinks. One more thing on another lock app LockBot when you press the volume button the sound does not get turned down but I don't want to really pay for two apps that can do the same thing. Edit: OK they fixed it but their is a new problem with the home button.
isjr said:
I have had the payed version of Lock 2.0 since there was an option to buy but since I got my Nexus One it has now become pretty much unusable. The sad part is that it is better than the lock button that is on the top of the phone cause it lets you bring up the lock screen by pressing your track ball. I love all the different back grounds and sounds you can download and how they stay in a folder and not in your app draw (which is really annoying). Now the thing I don't like is that when you press the volume buttons when the phone is locked you can and will turn down or up the volume on accident and this is why this app is now unusable. Can it really be that hard to add an option to disable these buttons? I have emailed Android Apps and they say the reason the volume button does that is for when you are listening to music and thats great but whats the use if when you get a call or text and you can't hear it cause you turned the volume down to 0 on accident. I emailed them today again and asked if they could update their app and I hope they do. The reason I started this thread is so anybody could comment on this problem with I have to say is probably my second favorite app on the market. I will also email them a link to this thread so they can see what everybody thinks. One more thing on another lock app LockBot when you press the volume button the sound does not get turned down but I don't want to really pay for two apps that can do the same thing.
Click to expand...
Click to collapse
What rom are you using?
Cyanogens latest has an option for trackball wake-up (and of course that mod can be applied to other roms as well) if that is indeed the biggest thing about it you like. I personally never saw the need to change my lockscreen from stock, but can understand why some people do.
I am using the stock rom, I didn't want to root this phone since you void your warranty and mine is pretty messed up I should get a replacement this week. Also I am glad Cyanogen added that and that tells you it is a problem in the stock or he wouldn't have had to improve on it. So people like me only have the option of downloading an app to get the same results. Also I have used a rooted phone before, I had been using my Google Ion rooted for about 6 months before I got my Nexus One.
Ok I just got an email from the developer and they have disabled the volume buttons by default on the new version that was fast. Now there is a weird problem where even after you set the Launcher as the default for your home button it still keeps opening Lock 2.0, its really annoying but I already told them so I'm sure they will fix it. Now if only Google would respond like this for their "Support Forums" on fixing the 3G and Touchscreen problems the world would be a better place.
I understand the issue with the volume keys. I don't listen to music so i installed the app (ringer mode locker) by kaa from the market. It overrides the system setting and locks on your choose of settings: vibrate, ringer silent etc. If you volume up or down it stays on you set point. I like if because it is not a background app using extra battery trying to monitor a set point.
isjr said:
Ok I just got an email from the developer and they have disabled the volume buttons by default on the new version that was fast. Now there is a weird problem where even after you set the Launcher as the default for your home button it still keeps opening Lock 2.0, its really annoying but I already told them so I'm sure they will fix it. Now if only Google would respond like this for their "Support Forums" on fixing the 3G and Touchscreen problems the world would be a better place.
Click to expand...
Click to collapse
Please don't critisize Google like this, 3G issues and Touchscreen problems are not simple applications in which code can be modified to turn off the "Volume" buttons.. I've noticed the employees on their forums try to solve things to the best of their abilities - but Google can not just correct everything as if it takes a small flick of the wrist, or click of a mouse...
Honestly I don't see how they will fix any 3G issue entierly without modifiying the insides of the phone.. guess I dont know enough about phones to make such a conclusion anyways.
isjr said:
Now there is a weird problem where even after you set the Launcher as the default for your home button it still keeps opening Lock 2.0, its really annoying but I already told them so I'm sure they will fix it.
Click to expand...
Click to collapse
I emailed them about this a couple of weeks ago. I told them exactly that and I got a "Steve Jobs-like" response lol..
"Something is wrong with your phone."
I even posted about it a couple of times in the Q&A section but got no responses. I'm glad to see someone on a stock ROM is experiencing the same issue because I thought it was due to using CM. Are you using an auto task-killer?
!!
I want to get rid of my lockscreen! its anoying having to press the power button then unlock the screen!
frankzua77 said:
I want to get rid of my lockscreen! its anoying having to press the power button then unlock the screen!
Click to expand...
Click to collapse
Get "KeyGuard disabler" from the market. It costs 1.49 but does exactly what you want. I'm sure there are free versions of similar software too but this is only one i've ever tried.
!!
gIMpSTa said:
Get "KeyGuard disabler" from the market. It costs 1.49 but does exactly what you want. I'm sure there are free versions of similar software too but this is only one i've ever tried.
Click to expand...
Click to collapse
________________
wow dude just tried it! works perfect! thanks man!
Meh....
After installing and trying to use it, I finally gave up. It has the potential to be by far one of the best android apps. The developer has designed programs that mesh with android so natively that I am jealous of his understanding. But even after a few reinstallations, this program never delivered. A replacement lockscreen must be more than just pretty. It wasn't sized right for the Nexus One screen and constantly froze "Updating List", even when I was just trying to unlock. The "Updating List" freeze causes a loop that just recalled the freeze when I hit home. There is no escape short of hitting menu, more, home, then selecting my home screen program. I would consider that a lock screen fail if I have to navigate a menu to select a home screen instead of sliding the sexy little slider over. I hate taking refunds from the market, but Lock 2.0 needs more work. If I see anyone saying it has been adjusted for the N1 screen and the home bug has been fixed, I'll buy it again, but until then, I'll stick with the just weather and toggle widgets.
I hear that Lock 2.0 disables notifications on the Nexus One. Does anybody know of any apps thats just as attractive as Lock 2.0 that doesn't disable notifications or freeze.. etc.. (something iphone-ish i guess)
Any news about the home button bug bypassing the lock screen in Lock 2.0?
As far as a can tell its been working good and the dev added the option to clear the home screen default if it does it again. Its pretty sad that he left it messed up for months until I sent him the link to this thread.
Sent from my Nexus One
isjr said:
As far as a can tell its been working good and the dev added the option to clear the home screen default if it does it again. Its pretty sad that he left it messed up for months until I sent him the link to this thread.
Sent from my Nexus One
Click to expand...
Click to collapse
Thanks, but I was referring to another bug (unless I'm totally mistaken):
When you turn on your nexus and you're still on Lock 2.0 lock screen, if you press the home button, it unlocks the phone without having to use the slider.
Hope this was clear...
HTC Sensation: Possible solution of "phone doesn't sleep" and "power button" problem
Hi every body,
I was getting irritated and extremely fed up of basically two problems of my htc sensation:
1- The phone didn't automatically turn the screen off. The screen would remain ON and wouldn't automatically lock itself. For example, i use the phone and then i will place it at a side expecting that first screen will be dimmed and then phone will automatically lock itself. It wasn't happening since a very long time (I don't remember the beginning of problem), even when screen timeout setting was enabled. I also observed that if at one time i set the brightness level of display to be automatic, next time i check it and brightness level was always set to be at maximum level.
2- When i pressed the power button to lock the phone, the phone often doesn't go dark. It went dark for a second and then became ON again. I had to press it a number of times until it goes dark. Similarly when i wanted to unlock the phone, i had to press the power button multiple number of times, until it gets unlocked.
Basically i was trying to solve the 1st problem. I went into settings -> applications -> manage application. I checked for each installed application whether it has following in the permissions:
System tools: prevent phone from sleeping
Following applications had above mentioned permission, so i removed them:
xda
ebay
mobile voip
daily motion
sports tracker
Calorie Counter - MyFitnessPal
imdb
Photo Editor
speedtest.net
whatsapp
yahoo messenger
Surprisingly after removing those apps, both issues 1 & 2 were totally gone. The phone was automatically locking it self (it still is). So for me problem number 1 is totally gone now.
However, regarding second problem, i tested it like 100 times locking and unlocking the screen by pressing power button. The behavior was absolutely normal. Then i checked the brightness level of phone, it was set to maximum, i set it to automatic. As soon as i set the brightness level to be automatic, the 2nd problem somehow reappeared.
Now if i set the brightness level manually, the 2nd issue doesnt reappear, but when i set the brightness level to be automatic, power button issues reappears.
Sorry for such a long post but I hope may be this post helps someone, also i would like to ask the experts the justification of such behavior of phone.
I am using stock rom and android version 2.3.4, sense version 3.0 and software number 1.50.206.1
This definitely needs a bump!
I was thinking of possible solutions as well, but this one makes sense. Maybe it is a flaw in how that permission is handled? I don't know how to program, but if any of you clever rom hackers are around, maybe you can try tweaking this? I was thinking that it was maybe something to do with the hardware button itself, sending off multiple signals to the phone telling it to lock and unlock right after due to the shoddy power button design.
My main issue with the fix in the original post is that I use a lot of apps that require this permission, and apps are kinda what define how useful your phone is (aside from making phone calls, that is). If there was a way to fix this issue by either tweaking the "prevent phone from sleeping" permission, or maybe just trying to add an input delay that doesn't register any power button presses until half a second has passed or something.
Like I said, I don't know what is possible to tweak with android since I don't know how to program so I might just be talking out of my butt, however, I do like this phone, it just has this one major power button flaw that really annoys me!
#2 doesn't occur in ICS Roms. I'm always on auto brightness.
Some ROMS added some apps may let your phone awake automatically when you close the screen,so it is the right way to move some apps. Using ARHD ICS and Insection ICS ROMS ,#1#2problems never happend.
Basically i would like to stick to original stock rom. I know i can avoid these problems if i use custom roms.
@Tekuno
Let me tell you, i didn't delete all of those apps which were using that permission "prevent system from sleeping". I only deleted those which i mentioned in my 1st post. Among those, i installed "yahoo messenger" again and 1st problem started happening again. I removed that app, problem gone. For me it's the case of hit and trial. I can't definitely point out one specific app which cause the problems.
I think there is really a flaw in the way this permission is handled by operating system of the phone.
I would also like to keep with the stock rom if possible. I figured it would only be a few apps that would be causing the lock screen issues, I am currently too lazy to go through all of the apps and figure out which ones are causing it.
I'll wait patiently for the ICS and Sense 3.6 update and see if that helps.
i have both problems too. About no 2, i always tot it happens after using the stock camera app which forces the brightness to go maximum and sometimes after exiting, there is some bug that doesnt return setting to automatic. Just a hunch but not sure :s
Do you have "Extended quick settings" installed ? and on a custom ROM, if so then i guess you need to check the "Screen On" option in the extended quick settings dropdown window.
You must have accidentally pressed it and activated it instead.
I am running Dman's rooted stock UCLB3 with Entropy's DD and Voodoo Lagfix. I love the setup but one this is really bothering me: I can't set the screen security time. I like the screen to go off in 15 - 30 seconds, but I want to be able to decide how long it will be until I have to use the security unlock. Now, there used to be a setting for this under Location and Security, but for some reason it is no longer there. Is it this ROM or is this missing from all 2.3.6 builds (i.e. stock)?
In case you aren't following me, I am attaching two screenshots, one from Samsung's website, the other from my phone. As you can see there is no "Timeout" menu on my phone. Was this somehow stripped from Dman's ROM (not impossible since the android.policy.jar file - the one that I believe is related to this menu - sometimes encounters issues from deodexing) or is this feature just gone from the phone? If it was stripped, how might I go about getting it back?
This is driving me mad right now, so I'd love to hear a definitive answer.
The setting that you are looking for can be found under Settings / Display. It wasn't stripped, you're just not in the correct menu.
No, that is a different setting. You'll notice that the display setting is to determine when the display will go to sleep (when it will automatically turn off), the setting I am talking about determines when the screen will lock after the screen turns off.
There are two programs with similar functions: Delayed Lock and JuiceDefender Ultimate. However, I suspect that the phone setting is still partially alive somewhere because both programs seem to wreak havoc with whatever settings are now default.
Oh, okay, now I understand. That feature isn't available in stock UCLB3, and there were no issues when deodexing.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Thanks. That's basically the answer I wanted. I've been poking through the guts of both the stock and rooted builds trying to find out what happened. It is really irritating that it's not there (well, for me it is!) because the security screen seems to have a mind of its own, particularly if you introduce alternative lockers into the mix.
For anyone who may be interested, you may be able to set the timeout by editing values in the android.policy.jar file in framework folder. Search around, you'll find instructions. I haven't tried this.
The two apps I have found that enable this functionality are Delayed Lock and Juice Defender Ultimate. However, neither app works well with 3rd party security locks such as Go Locker. The lock delay apps trigger the system security screen lock so you may have to go through as many as 3 screens before you get to your home screen.
Sorry, there is one other app: Password Delay. I did not try this because I want to use a pattern lock. PD does not work with patterns.
Yeah, join the club lol. I just learned to deal with it after a while. But I hear you. Tried looking for some alternative ideas... and I just kept unlocking everytime.
Sent from my A500 using Tapatalk 2
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Yes, this is me too exactly. Same thing with the dev option too. Not sure if I should wait for 8.1 or if it's hardware and RMA it. Frustrating because I like this phone.
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
I have definitely noticed this as well, happy to know it wasn't just me
cb474 said:
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
Click to expand...
Click to collapse
I tried a reset but the issue still showed up. In fact it happened twice on the first time setup stuff afterwards. I called Google and we went through the motions and reset it from recovery mode but it was still there when I was testing it the next couple hours. Anyway, we're doing the RMA thing. I'll let you guys know how it works out when I get my new phone.
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
I find that it occurs when I'm in a small room with the heat turned up. The sensitivity of the touch screen seems to depend a lot on moisture. If I keep my fingers moist (or wear a touch sensitive glove) it works a heck of a lot better.
ritzack said:
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
Click to expand...
Click to collapse
That's good and bad news I guess, hopefully just needs a software update. I have a replacement coming Monday, but I kind of expect no improvement and that this is just a common thing that a lot of people aren't noticing
I noticed that for a while in Google Play Books, in which I tap the screen frequently to turn pages. I tried a factory reset, which didn't help. I tried running in safe mode and testing on Maps and still had a problem, although less frequently (a higher percentage of taps worked). Then it started to work better. We'll see if that lasts.
I tried flicking as opposed to tapping and flicking always works.
I'd suggest posting on the Pixel product forum or calling support, so that Google becomes more aware of the issue. There are some threads on the subject on reddit and the product forum.
Out of interest are you noticing it any particular parts of the screen?
I've noticed it a few times but it's been on areas of the screen near the edges.
I assumed it was some sort of palm rejection thing going on it the background with it thinking I'm accidently mashing the display.
With me it was the right edge toward the middle, as that's where you tap to turn the page in Play Books.
I get it on the back button frequently, but it happened just now in the middle of the screen when I typed the text input box to start writing this
I think this is the whole OS hanging/freezing briefly actually, not a touchscreen input issue
- Pressing the hardware unlock button can get ignored (both locking/unlocking)
- Scrolling from a quick flick + release can suddenly stop (no additional inputs)
So most likely this is a software issue, hopefully fixed in an upcoming update? It's kinda annoying
Did you change the DPI or font size? I go back to default and it seems that everything is good now.
---
update: no it happens again…
nonexistent said:
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Click to expand...
Click to collapse
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting any m.reddit thread in chrome and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
nonexistent said:
Haven't changed the DPI or font size
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
So, I replicated what you told me, 3x. I didn't miss any taps, and no system hang/missed input..
hmm
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
nonexistent said:
Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
Yeah, sometimes I see a tap register visually on the screen, but the intended action doesn't happen.
redandblack1287 said:
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
Click to expand...
Click to collapse
It's funny. I had the issue. Did a factory reset. Felt like it was better. But now that I'm thinking about it more I notice it a lot. So I can't tell if it's really different. Before I figured I'd made a mistake. Now I think it's the phone. Damn you phone!
Anyway, I notice that the issue tends to happen more or less randomly, at any position on the screen. Also, sometimes the same tap fails to register twice in a row, but once it's starts working all subsequent taps that come in a row work (say I'm clicking through a lot of menu items in some settings). So maybe that lends some credence to the idea that there is a system for registering the taps that is not waking up and once it does it works fine.
Perhaps related, I have my ambient display set to wake on double tap. Before the Nov update it hardly worked. Now it seems to be working reliably.
I am so used to my OnePlus 9's AOD that I'm kind of surprised how terribly it seems to be implemented here and I'm hoping it's just being buggy...
First off, the AOD doesn't seem to work at all if I don't choose to have it displayed all the time (which is the first hint that this may be a bug as even the preview for tap or lift seems to suggest that the AOD should be popping up, not the lock screen as is happening right now).
Second, if I do have it displayed all the time, incoming notifications bring up the lock screen. My OnePlus shows a preview of that one specific notification while still on the AOD screen and it seems silly that Google isn't utilizing something similar. It is extremely handy to have a text come in, say with a 2FA code, and have the entire screen black besides a large preview that shows you that code. The way that it is working now, it wakes the lock screen, which is fine, except the message gets truncated so it often requires me to interact with the device even further to be able to see the full message.
I also tried turning off wake the screen for notifications to see if that triggers the AOD and... it just adds an icon to the AOD...
This is a huge downgrade in user experience if this is the normal expected behavior. I could have sworn my 3 XL handled it better than this but I haven't used it for awhile and I'm not at home where I could check it. Maybe I'll have to look into third party options.
Im not quite sure and your whole post. I as well had the Oneplus 9 pro. My Pixel 7 pro AOD works just fine. I double tap screen and goes directly to the AOD, which displays the Date(top left corner), the time that is big, the fingerprint icon and battery percentage. a tap of the screen brings up the lock screen. Face unlock and pin works directly to the home screen. Now I do have to say im using Nova Launcher as i can't stand that the dat and google search bar can't be removed.
schmeggy929 said:
Im not quite sure and your whole post. I as well had the Oneplus 9 pro. My Pixel 7 pro AOD works just fine. I double tap screen and goes directly to the AOD, which displays the Date(top left corner), the time that is big, the fingerprint icon and battery percentage. a tap of the screen brings up the lock screen. Face unlock and pin works directly to the home screen. Now I do have to say im using Nova Launcher as i can't stand that the dat and google search bar can't be removed.
Click to expand...
Click to collapse
Thanks. Sounds like I have a bug after all right now.
When you get a text or something, does it show an AOD notification with a preview like the OnePlus did or does it just show the lock screen?
I turned off screen on with new notification, I will have to check
Without screen on with new notification, I still get the notification and AOD stays on. Lock screen does not come on. So in other words, AOD works as it should.
EtherealRemnant said:
Second, if I do have it displayed all the time, incoming notifications bring up the lock screen. My OnePlus shows a preview of that one specific notification while still on the AOD screen and it seems silly that Google isn't utilizing something similar. It is extremely handy to have a text come in, say with a 2FA code, and have the entire screen black besides a large preview that shows you that code. The way that it is working now, it wakes the lock screen, which is fine, except the message gets truncated so it often requires me to interact with the device even further to be able to see the full message.
Click to expand...
Click to collapse
The AOD on my Pixel 4a works just like you describe the OnePlus AOD, it stays on the AOD but displays the message at the center for a few seconds, sounds like a bug (unless this changed on the 7 and 7 pro for some reason).
Interesting. Thanks to both of you. Hopefully it gets resolved at some point. I'm in no mood to factory reset and set everything up again so I'll just deal with it for now.
EtherealRemnant said:
Interesting. Thanks to both of you. Hopefully it gets resolved at some point. I'm in no mood to factory reset and set everything up again so I'll just deal with it for now.
Click to expand...
Click to collapse
Yeah Im trying to adjust to not having Recent Apps, home and Back buttons on the screen! lol
schmeggy929 said:
Yeah Im trying to adjust to not having Recent Apps, home and Back buttons on the screen! lol
Click to expand...
Click to collapse
You can get those back if you want. Settings > System > Gestures > System navigation and change back to 3-button.
Do you have the wake screen setting toggled? It's possible that's why
EtherealRemnant said:
You can get those back if you want. Settings > System > Gestures > System navigation and change back to 3-button.
Click to expand...
Click to collapse
Thanks, I literally just found it as I was getting your reply notification!
bosox284 said:
Do you have the wake screen setting toggled? It's possible that's why
Click to expand...
Click to collapse
I have tried messing with all four settings in all sorts of configurations to see if I can get it to work properly and have been totally unsuccessful. It seems I have just stumbled on some kind of bug.
EtherealRemnant said:
I have tried messing with all four settings in all sorts of configurations to see if I can get it to work properly and have been totally unsuccessful. It seems I have just stumbled on some kind of bug.
Click to expand...
Click to collapse
Hey, I do have the same bug. Did you manage to fix it ?
I am rooted + I use Kirisakura kernel
I don't think this would be the cause but we never know ...
Repear88 said:
Hey, I do have the same bug. Did you manage to fix it ?
I am rooted + I use Kirisakura kernel
I don't think this would be the cause but we never know ...
Click to expand...
Click to collapse
It was resolved after I did a factory reset and restored only SMS and apps (but not settings) from my Google backup.
EtherealRemnant said:
It was resolved after I did a factory reset and restored only SMS and apps (but not settings) from my Google backup.
Click to expand...
Click to collapse
Thx ! Damn it ...
I didn't restore anything ... I'll try before resetting (it's been only 2 days I have it ready XD)
schmeggy929 said:
Im not quite sure and your whole post. I as well had the Oneplus 9 pro. My Pixel 7 pro AOD works just fine. I double tap screen and goes directly to the AOD, which displays the Date(top left corner), the time that is big, the fingerprint icon and battery percentage. a tap of the screen brings up the lock screen. Face unlock and pin works directly to the home screen. Now I do have to say im using Nova Launcher as i can't stand that the dat and google search bar can't be removed.
Click to expand...
Click to collapse
Don't know if I understand you correctly. Do you have enabled AOD all the time (always show time and info)? If not, you double tap to show AOD and it's working fine? Do you have any other settings enabled (tap to check phone, etc)?
I have disabled AOD (always show time and info) and when I tap, it goes straight to lockscreen. Not sure but that change may have been introduced in one of the latest updates.
@EtherealRemnant same question to you
In my case as it works right now:
When I enable AOD (always show time and info), it is showing all the time. When I disable that, it's not. When I tap on the screen (when AOD is disabled), it goes straight into lockscreen. When I receive a notification, AOD shows for a short moment.
What I would like to achieve (dunno if that's possible) would be to have tap to show AOD instead of lockscreen (with AOD not showing all the time).
I understand what you would like to do( tap the screen to have AOD appear first. I cannot find anything like( temp AOD) in settings. The show time and info toggle is basically the master AOD switch. Either AOD all the time or disabled completely, nothing in between.
Same for me, after reading topics on reddit, I was thinking I wasn't a bug and I might misunderstood what op was saying.
@trawel to add to your statement, if you move slightly your phone, like lifting one side, the AOD should come, most of the time (sometimes screen stays black)
But yeah I also would like to be able to "tap to show AOD" so it won't unnecessarily unlock when it sees my face.
AOD = Always On Display...it's in the name...ALWAYS ON. I understand what you're looking for but then it would NOT be called AOD, but SOD = sometimes on display.
jaseman said:
AOD = Always On Display...it's in the name...ALWAYS ON. I understand what you're looking for but then it would NOT be called AOD, but SOD = sometimes on display.
Click to expand...
Click to collapse
We get the semantics but the point is that the AOD used to function differently. You used to be able to tap to get the AOD to come on and lifting the device used to always go to AOD FIRST. When I made this thread, I was not seeing the AOD at all most of the time. A factory reset has set it to such that if the phone gets barely moved, the AOD comes up, but tapping or picking it up quickly will almost always go to the lock screen (but then sometimes it will go to the AOD too when picking it up quickly) so it's clearly bugged somehow as the behavior is inconsistent, whichever way that Google intended for it to actually be.
Going beyond that, the AOD is pretty useless anyway. Any incoming notifications light up the lock screen. Why can't they just make it like my OnePlus where the notification shows up on a black screen with a full preview when AOD is enabled? This is so much more useful, not to mention battery friendly.