Related
Hi,
I recently bought a HTC Touch HD, and I think that the "shutdown-screen-when-you-answer-a-call" function of phones like Diamonds, Touch Pro and HD is the dumbest way to prevent accidental presses on the touch screen.
Our devices have a light sensor, that could be used to switch off the screen if the phone is near the ear (like the phone using an "i" word ) and keep it on when you answer with loudspeaker for example.
The "problem" with this function is that when you're already in a "no-light" environment, the screen lock function doesn't work.
To resolve this issue, I think we could use the G-Sensor. Indeed, if the place has no light, then, the phone cannot detect the proximity of a ear. But when you put the phone next to the ear, you hold it a the vertical...
To make it short, the app should do :
Do nothing in normal use.
When a call arrives :
- it monitors the ambient light
If there's light :
- when you answer the call, if there's light then no more (you stick the phone next to the ear), it switches off the screen and continue to monitor.
- while in call, if there's light again (you want to see some info on the screen for example), it switches on the screen and continue to monitor.
- and so on until you end the call
If there's no light :
- when you answer the call, but let it at the horizontal (you let it on the desk for example), it does nothing
- if you take the phone on the vertical position (you stick the phone next to the ear), it switches the screen off.
- if the phone, during a call, goes from vertical to horizontal of horizontal to vertical, the screen is switches on/of
- and so on until you end the call
Obviously, you could replace the "switch on/off screen" with "lock/unlock screen".
What do you think about ?
UPDATE :
After playing a bit with the HD, it appears that HTC DOES use the light sensor for turning the screen off during a call.
Let's do a test :
In a place with plenty light :
- put your mobile with the face up
- call a number (always face up) : the screen will not be switched off until the light sensor detects a loss of luminosity or a timeout set in the registry.
So, my conclusion is that HTC already use the light sensor to switch the screen off during a call, but they do it in an absurd way :
- they poll the sensor just to shut down the screen, not to switch it on.
- once the screen has been switched off, they do not longer poll at all.
Do you think it could be a way to "hack" their system to do what we want to do ?
no one has an opinion on this idea ? if there's nobody that want / have the time to develop a soft, I understand, but at least please, give me just your opinion
I agree with your idea for such an application. I must admit that I am very used to just pushing the power button when I answer a call (from Polaris use) to ensure I am not going into other programmes as I rub the phone against my ear. On the other hand I am trying to get used to the Touch HD's modern automatic method but I can't help not feeling relaxed that it has worked and keep trying to look at the screen in the corner of my eye to see if it did go off or not.
If it does not come now I am sure there will be such an app very soon just as you describe especially as all the latest models now have it.
i'd use the half of it that doesn't require the G-sensor as i don't have a diamond or HD...
but i'm certainly sick and tired of my ear operating my touch screen while i'm speaking.
I've written a prototype to do exactly what you are talking about although the one crucial part I am missing is the lock code. Every example or suggestion for locking the screen is very hacky and never feels like a good approach. If anyone has a good solution for locking the screen (especially in managed code) I would be happy to complete what I have started and release it with source so it could be improved upon.
So far, the best locking utility I have seen is PocketShield although I'm not sure what approach was used for locking in that case. It almost feels like a form that captures all windows events but I'm not sure exactly.
fireweed said:
I've written a prototype to do exactly what you are talking about although the one crucial part I am missing is the lock code. Every example or suggestion for locking the screen is very hacky and never feels like a good approach. If anyone has a good solution for locking the screen (especially in managed code) I would be happy to complete what I have started and release it with source so it could be improved upon.
So far, the best locking utility I have seen is PocketShield although I'm not sure what approach was used for locking in that case. It almost feels like a form that captures all windows events but I'm not sure exactly.
Click to expand...
Click to collapse
Maybe the simpliest way to "protect" the screen is to switch it off. I suppose it must be some API to do that ?
Concerning the "locking", I think the simpliest way is to put on focus an empty window (transparent if it can be ).
I'm really happy to know that you're working on an app like that
lpaso said:
Hi,
I recently bought a HTC Touch HD, and I think that the "shutdown-screen-when-you-answer-a-call" function of phones like Diamonds, Touch Pro and HD is the dumbest way to prevent accidental presses on the touch screen.
Our devices have a light sensor, that could be used to switch off the screen if the phone is near the ear (like the phone using an "i" word ) and keep it on when you answer with loudspeaker for example.
The "problem" with this function is that when you're already in a "no-light" environment, the screen lock function doesn't work.
To resolve this issue, I think we could use the G-Sensor. Indeed, if the place has no light, then, the phone cannot detect the proximity of a ear. But when you put the phone next to the ear, you hold it a the vertical...
To make it short, the app should do :
Do nothing in normal use.
When a call arrives :
- it monitors the ambient light
If there's light :
- when you answer the call, if there's light then no more (you stick the phone next to the ear), it switches off the screen and continue to monitor.
- while in call, if there's light again (you want to see some info on the screen for example), it switches on the screen and continue to monitor.
- and so on until you end the call
If there's no light :
- when you answer the call, but let it at the horizontal (you let it on the desk for example), it does nothing
- if you take the phone on the vertical position (you stick the phone next to the ear), it switches the screen off.
- if the phone, during a call, goes from vertical to horizontal of horizontal to vertical, the screen is switches on/of
- and so on until you end the call
Indeed, you could replace the "switch on/off screen" with "lock/unlock screen".
What do you think about ?
I searched the forum for an existing app that could do this, but I didn't find anything.
If there's already an app that do this stuff, I'm truely sorry for this post.
Click to expand...
Click to collapse
I'm looking for this.. If you find a solution send me a PM, I will do the same
Thanks!
We need this app, how does the iphone acheive this?
I think the 'easiest' way to make this app would be to keep the phone doing what it does currently (put the phone on standby when answering a call) then have the light sensor take the phone out of standby when it receives light, (taking it away from your ear)?
Obviously if its dark then we would have to use the power butten as we currently do now or have the Gsensor do it with a twisting motion (vertical to horizontal).
If anyone has an idea how to program this i'm willing to help in any way, the current systems seems so crude on such tech devices!
DB
lpaso said:
Hi,
I searched the forum for an existing app that could do this, but I didn't find anything.
Click to expand...
Click to collapse
There a program, that can help you. Not full, but it can switch off screen, using g-sensor. However its using not vertical aligment of the phone. There are using changing orientation of the phone to decide when phone near the ear.
http://forum.xda-developers.com/showpost.php?p=2622590&postcount=45
I have always wondered why our WM phones don't do what the iphone does...
For the SE Xperia X1, the light sensor is right near the earpiece (along with the little front facing camera), so it would go to virtually 100% darkness when near the ear. I would presume unless you are using the phone also in 100% darkness (which should be pretty rare I would guess) then it would work like the iphone.
I have also been quite annoyed by the fact that after a phonecall, sometimes I found i'm in a note taking program or weather program or something else. It just seems dumb, considering our phone HAVE these lightsensors?!
I think it's a fantastic idea to solve a VERY FRUSTRATING PROBLEM
lpaso said:
no one has an opinion on this idea ? if there's nobody that want / have the time to develop a soft, I understand, but at least please, give me just your opinion
Click to expand...
Click to collapse
I would rank myself this way:
Not a newbie who's just gotten a touchscreen phone and is now discovering the quirks when holding screen to ear,
and not a developer,
but a power-user. I have installed all sorts of XDA-developed features/enhancements for my phone.
But now I have 4 years experience -- starting with the T-Mobile MDA, and its successor, the T-Mobile WING. And despite all of the advancements expected in that time, STILL, I inadvertently end a call, or put it on hold accidentally, ALL THE TIME. Between that and trying to retrieve the phone from my pocket just to answer the damn ringing phone, I would say I have, on the average, a 20% success rate -- and 80% of the time the call is disrupted. And at least once a day my ohone, in my pocket, even when using s2u2, manages to REDIAL my latest conversation, so mcuh so that all my friends say "why don;t you get rid of that phone. It does all these whiz bang things but still can't reliably manage a basic phone call.
My most recent experiment was to call someone, then when they answered, press the s2U2 key to lock the phone screen. Only I came to find out from A_C that this is no good: S2u2 does not have recognition that you're ending the call, thus, since it's in lock-mode, the "END CALL" or Hang-Up hard key does not work.
So by all means, I would even pay for an app that once and for all handles the baseline problems of simply making a phone call. Thanks for making this request.
fireweed, have you contacted A_C, author of s2u2 ?
There may just be perfect synergy between the two of you. His "best of breed" screen-lock app is widely used -- and other developers, like supbro, for example, author of iDialer, have collaborated on small code-bits from A_C to solve some integration problems.
If for any reason you are unfamiliar with A_C, go to his website: www.ac-s2.com -- where his apps are explained, and all link back to XDA.
He's even managed to make the screen lock work, yet, have it selectively overridden when you insert headphone jack -- such that his s2p (slide to play) app opens and allows you to switch music tracks etc while otherwise the screen and buttons are all fully locked...
fireweed said:
I've written a prototype to do exactly what you are talking about although the one crucial part I am missing is the lock code. Every example or suggestion for locking the screen is very hacky and never feels like a good approach. If anyone has a good solution for locking the screen (especially in managed code) I would be happy to complete what I have started and release it with source so it could be improved upon.
So far, the best locking utility I have seen is PocketShield although I'm not sure what approach was used for locking in that case. It almost feels like a form that captures all windows events but I'm not sure exactly.
Click to expand...
Click to collapse
Hi,
After playing a bit with the HD, it appears that HTC DOES use the light sensor for turning the screen off during a call.
Let's do a test :
In a place with plenty light :
- put your mobile with the face up
- call a number (always face up) : the screen will not be switched off until the light sensor detects a loss of luminosity or the timeout set in the registry expires.
So, my conclusion is that HTC already use the light sensor to switch the screen off during a call, but they do it in an absurd way :
- they poll the sensor just to shut down the screen, not to switch it on.
- once the screen has been switched off, they do not longer poll at all.
Do you think it could be a way to "hack" their system to do what we want to do ?
I think HTC does not only switch off the display but goes to standby (phone works independent if you didn't know yet). Your idea is a lot different in terms of programming.
I don't know if it goes to standby : when the screen is switched off during a call, a press on any button switch it on again. In the registry, the key controlling the timeout before the screen is shut off is named "LightSensorToScreenOff" so I think it is just switching off the screen...
lpaso said:
I don't know if it goes to standby : when the screen is switched off during a call, a press on any button switch it on again. In the registry, the key controlling the timeout before the screen is shut off is named "LightSensorToScreenOff" so I think it is just switching off the screen...
Click to expand...
Click to collapse
Well if thats the case, its HALF of what the iphone does... it turns off the screen based on the light sensor going dark suddenly (next to ear) but then fails to turn the screen back on after you move the phone away from your ear...
Anyone know how to enable this?
Interested in having this feature too. Isn't it possible to have the G-Sensor determine when the phone is vertical and shut the screen and then when it is lying flat to turn the screen back on again. Believe that the Iphone does it this way, not with the light sensor.
Hmm... I never had my ear 'navigating' my phone during in-call before....
I never allowed the screen to touch my face anyway, and the speaker is facing the ear canal, when I receive or make calls...
But i do understand that s2u2 can do what you guys might need, it locks the screen during in call.
Hennyb said:
Interested in having this feature too. Isn't it possible to have the G-Sensor determine when the phone is vertical and shut the screen and then when it is lying flat to turn the screen back on again. Believe that the Iphone does it this way, not with the light sensor.
Click to expand...
Click to collapse
I think the Iphone has something called proximity sensor, which senses the distance from the ear to the phone, hence when the phone rest on the outer ear, the phone screen shut off.
Or am I wrong?
Section9 said:
I think the Iphone has something called proximity sensor, which senses the distance from the ear to the phone, hence when the phone rest on the outer ear, the phone screen shut off.
Or am I wrong?
Click to expand...
Click to collapse
No, you're right. It uses an iR sensor to know if there's something near the phone.
I'm using an Adonit Jot style stylus on a Android phone (ZTE V5 Max on Android 4.4.4, but I experience similar problems with other devices), which generates less signal on the capacitive touch screen than a finger. The phone's software appears to be configured with only hand touch in mind, and drawing with the stylus results in broken lines a lot.
On the pointer location debug display the minimum pressure I can get for a touch point to register is 0.09, and with this stylus I get 0.10~0.11 most of the time, so the head room is really low. With a finger the pressure level is usually above 0.15. This makes me wonder if I can tweak the threshold for a signal to be registered as touch to make inking with the stylus more stable.
I'm aware of some Build.prop configs suggested here and there. However after playing with several versions and reading some of the documentation I believe those values only change the touch behavior after a touch point has been registered. The actual threshold for a signal to be recognized as touch is not changed, and my problem remains.
I've also came across this thread which appears to be very relevant, unfortunately the mentioned file system paths are not found on my 4.4 ROM.
Is there anything I can play with to change such a threshold? (I have root access.) Or is it hard-coded in device-specific drivers?
My G4 just died, should I get the VZW version of the Pixel 2?
I just want to swap in the nano sim and keep going.
I want to use a custom rom so I need to unlock the bootloader, is this possible?
Swapppa has some reasonable offerings........
LG was a bad experience, want simplicity at its android best.
spyknee said:
I want to use a custom rom so I need to unlock the bootloader, is this possible?
Click to expand...
Click to collapse
Not if you buy the Verizon version
Sent from my Pixel 2 using Tapatalk
ok and then
can I use my current nano sim for puppywireless, a verizon mvno, with the unlocked google edition pixel 2? Verizon wants cdma phones......................
You can buy the unlocked version from Google and use it on Verizon.
>Do I want a Pixel?
Depends on if you do or not.
Jokes aside, you can unlock a Verizon P2 if it hasn't taken the Jan update yet. Visit in store and ask to see a P2 in box, no SIM or wifi please. The box will indicate the factory software. Once you find a winner (hurry, they're fading from inventory) just carefully apply the unlock steps and enjoy.
Go Ahead
Yes, you should, Pixel mobiles are the best mobiles according to my friend's opinion, I'm also going to buy it next week but first I have to write my assignment.
So, I now own a new Pixel 2 Google Edition.
1st Pros:
Luv that its already stripped down and lean in the stock OS. @8.1.0 ver.
1st Cons:
Device does not report battery lvl correctly in notifications tab, always states 100%, icon always shows full.
WiFi icon appears to show only on, no signal strength at all.
Totally dislike notifications tab period! Too much redundancy! To much access points to the same stuff.
Decided that it should be a central home screen. A group of 5, home at center. Now that leaves 4 sides or edges.
1 edge for calling and texting, swipe left edge
1 edge for social media outlet of choice, swipe edge right
1 edge for camera and video, swipe edge down
1 edge for video and music playback, swipe edge up
Or could be other choices instead. Point being all the different access methods, repeat the same things so lets get simple.......................
Its about personalized customization of actual use. right now we just customize the presentation of gui's, color, form. There is nothing intuitive about OS use tho!. Things like smart bullitain are really useless and forced on us, seriously, wonder around with a live feed always going.......no.
spyknee said:
So, I now own a new Pixel 2 Google Edition.
1st Pros:
Luv that its already stripped down and lean in the stock OS. @8.1.0 ver.
1st Cons:
Device does not report battery lvl correctly in notifications tab, always states 100%, icon always shows full.
WiFi icon appears to show only on, no signal strength at all.
Totally dislike notifications tab period! Too much redundancy! To much access points to the same stuff.
Click to expand...
Click to collapse
Interesting: on 8.0 the Pixel 2 battery meter stuck at 100% charge for a long time (not permanently), but that was fixed by updates. Should not be a problem with 8.1.
And the WiFi icon works just as expected, i.e. shows signal strength (though no "activity arrows" if you were used to those). So this sounds like something is wrong.
I'm not sure what you are saying about the notifications. Can you give some examples?
Things like smart bullitain are really useless and forced on us, seriously, wonder around with a live feed always going.......no.
Click to expand...
Click to collapse
I don't have anything forced on me - I just turned off (or didn't turn on) anything that didn't interest me (with Google's launcher being one of the first things to go). There are always alternatives.
So I have discovered that enabling the ui demo mode was the problem with the status bar and battery level reporting, enabling this bad.
I have learned of and enabled the system ui tuner. This ended all the phone functions, status reporting, very sweet. Now the status bar just reflects certain running services.
I also installed the Android P theme launcher, I like it. Has a sidebar option, the ability to hide the status bar, the ability to alter dock settings. So I essentially dumped some cpu reporting cycles, so to speak, let see how bat life responds.
Without root, I have gotten closer to what I want. Need to get TWRP installed and a nandroid made.
Next thing,
Ambient- Always On Display, many internet posts for disabling. Do Not Disable!
Affects the screen saver display and wake up, touch screen. The touch screen seems to need this enabled for better response. I decided to enable the edges as well. Turned it to full squeeze. Do not wish the assistant but it seems that disabling it, and the rest really upsets touch screen.
spyknee said:
Next thing,
Ambient- Always On Display, many internet posts for disabling. Do Not Disable!
Affects the screen saver display and wake up, touch screen. The touch screen seems to need this enabled for better response. I decided to enable the edges as well. Turned it to full squeeze. Do not wish the assistant but it seems that disabling it, and the rest really upsets touch screen.
Click to expand...
Click to collapse
Ehm, AOD is just a additional option that is included so you can check the clock and whatnot without the need of turning on your screen.
The touch response in the screen is controlled at the kernel driver level and is only affected (in a negative way) by yourself and your fingers and how dirty the screen is.
spyknee said:
Next thing,
Ambient- Always On Display, many internet posts for disabling. Do Not Disable!
Affects the screen saver display and wake up, touch screen. The touch screen seems to need this enabled for better response. I decided to enable the edges as well. Turned it to full squeeze. Do not wish the assistant but it seems that disabling it, and the rest really upsets touch screen.
Click to expand...
Click to collapse
I might be the only one but I disabled aod with no ill effect that I am aware of. I don't care for it.
Also, enabling the up-down arrows on wifi-data is a simple mod.
aod affects pick up wake, double tap wake. touch responsesivness is very finicky as is, worse with aod off.
spyknee said:
aod affects pick up wake, double tap wake. touch responsesivness is very finicky as is, worse with aod off.
Click to expand...
Click to collapse
You are just experiencing some placebo side effects, mate. AOD have NOTHING to do with the screen sensitivity.
The screen- and touch response is controlled at the kernel driver level. Not at software/application(s) level.
AOD
My issue was this, if I left the phone idle and untouched for awhile and then came to it and double tapped the screen, it would not wake up. I would have to use the side button to open. Sometimes the action of lifting would allow the double tap to work, but inconsistant. Doing the squeeze for the assistant was inconsistant as well.
The touch screen acts inconsistantly. If you do a horizontal movement, it interferes with a vertical swipe, I mean things seem to get canceled out. I have to initiate action multiple times to win.
heres the deal, i do not give a flying bleep whether its a hardware or software issue, I would like smart answers that give a solution, not assign a blame or fault. Or tell me I am somehow misinterpreting what I percieved.
So here is my take. The dam phone is overloaded with redundant crap, that steps on each other, interfering with it self. IMO everything in this phone should be disabled at purchase. The consumer should then enable those things it wants! Possibly eliminating over extended, overlapping services and hardware.
Now I say this because it appears that in fact to much was being asked of the phone and it was flipping out basically.
I dumped some google software, pretty much what it would let me.
I disabled the screen saver function, my belief is this was why i would not wake up. Screen saver or no, it times out going to the aod clock display, which I like. Now the phone responds to a lift and double tap everytime......................................................................................
I was using a single home screen, with the android p launcher sidebar. My issue was using swipes to navigate web sites, read stuff, sift thru pages. The swipes were not responding properly, PITA. It seems that by using a single home screen, it stilts the screen edge, makes a dead zone, interferes. Not to mention the right side slider swipe icon is useless as presented. It seems that enabling a 2nd home screen helps with that dead zone. Its not 100% when swiping thru pages but response has gotten more tolerable.
IMO
Thanks to fakebook, everyone should understand what these devices are truly about, DATA MINING.
Google
Verizon
LG,HTC,Samsung,Hauweii
Each and every phone has at minimum, 3 different forms of active data harvesting going on. manufacturers, carriers, media apps. The greatest performance killer of all, not to mention...........................................I have come to despise predictive search algos, targeted marketing adds, basically digital junk mail inundation.
So,
Been using the pix 2 awhile now. Really hated Oreo so I went into beta play to get pistachio. Used ver 3, now 4.
I really liked the initial ver 3 update cuz it removed so much bloat from carrier crap. Less google crap too it seems.
Now I like the responsiveness much better with ver 4. I still have everything I can disabled, disabled or removed. No AOD, active edges, tap to life, no music, movies, tv. No auto pay, auto track, auto search, google talk, nada.
Its a com device, an internet search device, thats it! Bat life is good, real good.
These devices are overburdened with non-sensical, redundancies, that create huge performance impacts. Seriously, how many ways are there to access a smartphone, on all at once.
Now I lift the phone, touch the physical button and walla, works every dam time.
Yep, flexible to meet millions of users needs...
Just dropping this here: https://forum.xda-developers.com/pixel-2/help/worth-buying-pixel-2-june-2018-t3803197
It might also give anyone also in a similar situation additional information to help deciding.
I don't know if anybody else here has suffered this, but I've read several times when googling, that many XZP devices came with input lag out of the box. My device has always suffered with this, and flashing custom ROMs didn't seem to make a difference.
Input lag means that sometimes, keystrokes/touches are completely missed and sometimes scrolling misses too.
I unlocked my bootloader really early on, so I never wanted to send it back as I'm sure this voids my warranty.
I tested for a faulty digitizer using various screen input test apps from playstore, and they usually don't show any areas of the screen as faulty. This has always made me believe that it was most probably a software issue.
Today I discovered that yes indeed, my issue is definitely a software issue.
THE FIX:
Changing the screen resolution to 4k (3840x2160), and DPI to 821.
I've tried this before but never noted the difference in touch input. Perhaps because I wasn't looking for it.
Today I tried it again and much to my surprise, this time I noticed a HUGE improvement to input sensitivity and for now has 100% alleviated the problem. Typing, tapping and scrolling works perfect now.
This is most likely caused by the screen having to rescale pixels from 1080p to 2160p, making extra work for the CPU, but I'm no expert so I might be wrong. But it works for me.
I'll also note that I'm using Turbo ROM p75B now, and the input delay was still there until changing the resolution.
I'd like it if somebody who has suffered the same issue could provide feedback, I really hope this helps you too, as this was the only real issue that have me buyers regret, and it now works wonderfully.
Cheers.
Edit: I do believe this topic might be better recognised in the guides and discussions category. If so, could a mod please move it there.
Luckily I haven't had this input lag issue. However, I do get input lag if I have stamina mode turned on, and set to battery time preferred.
Just so you know, you do know that you're only emulating 4k, right? The only way to set the display to 4k is on AOSP.
@iKlutz I can't seem to find the resolution settings lol
Yes I understand that it's only "emulating" 4k and that it's not native 4k. It also uses more battery, which would suggest higher CPU usage, which in part contradicts my theory about rescaling causing input lag.
Perhaps it is something to do with the "touch map" (I can't think of the term), the software/grid that maps out the touchable area to the digitizer, having to resize from 1080p to 2160p, making the grid inaccurate? But it wouldn't make sense as to why it only affects some devices.
Also, I do not have stamina mode enabled as it's almost pointless in today's phones. I believe limiting processing speed only makes process queus take longer to finish, which means that CPU takes longer to idle. It only saves a negligible amount of battery unless your phone screen is off for 80% of the day. Almost as pointless as closing applications and cleaning RAM, as your phone will just use more battery rebuilding caches and restarting processes.
In any case this has completely alleviated the issue for me, so I hope someone on Google ends up here and this may be a solution for them too.
gavster26 said:
@iKlutz I can't seem to find the resolution settings lol
Click to expand...
Click to collapse
There are some threads here that explain various methods to change the VM resolution and scaling. If you're unfamiliar with ADB, I suggest you read very carefully and take precautions, as setting the resolution wrong could make it really difficult to reverse the procedure and we currently don't have a way to make TWRP backups.
i noticed this too.. but i enabled glove mode and things sorted by it self..
this kinda works, it happens very much less frequently but it does still happen
I finally picked up a U12 after Amazon had a 20% off sale on Warehouse Deals versions. It was basically new and I initially liked it. However, I'm likely returning it because the Motion launch gestures are extremely unreliable, especially when taking it out of my pocket. It seems that the proximity sensor doesn't immediately register that it's not in a pocket anymore. That, or it has to be more forcefully lifted UP, like you must do to activate the Ambient Display. I tried this with the Ambient display in both "always on" mode and "lift to check" mode. Same results. A majority of the time, I take my phone out of my pocket and go to double-tap on the screen and nothing happens. If I keep doing it, it works after a while. If I leave it lying on a table, it will pretty much always work, which is why I think it's a proximity/light sensor issue.
I have experienced this behavior before with other phones with double-tap-to-wake. In fact, LG and OnePlus seem to be the only ones that are 100% reliable for me.
Before anyone suggests it, NO, fingerprint wake-up is not an option. I interact with my lockscreen notifications almost exclusively throughout the day. I just want the screen to turn on when I tap on it twice, like it's supposed to and that's not happening. I also don't use power buttons. At all. I use my phone left-handed anyway, so that's not ideal. I'm not looking for a suggested work-around. I'm just seeing if anyone else experiences this and/or if there's something I'm missing. The phone is great otherwise, but this is a huge deal-breaker for me.