Related
I'm getting a crashed UI when checking notifications by swiping the top left corner downward.
I'll get an email or hangout and when I go to check it via the notification area it just blacks out the screen, then has a slight panic attack and switches between the home screen and the lock screen once or twice but this takes 5-10 seconds and it is obvious there is some sort of crash. However there are no crash notifications from android. Then my notifications seem to work find for a little bit.
It is similar or possibly the exact same thing as what is described here http://forum.xda-developers.com/showthread.php?t=2743255
Does anyone know of a fix for the UI / Notification Bar crashes that are happening? I'm seriously considering getting a new tablet and using this as a good excuse.
Apparently clearing the davlik, cache, and doing a factory reset doesn't seem to help.
I'm running CM 11 M6 EMMC on my Nook HD+
_Boondock_ said:
I'm getting a crashed UI when checking notifications by swiping the top left corner downward.
I'll get an email or hangout and when I go to check it via the notification area it just blacks out the screen, then has a slight panic attack and switches between the home screen and the lock screen once or twice but this takes 5-10 seconds and it is obvious there is some sort of crash. However there are no crash notifications from android. Then my notifications seem to work find for a little bit.
It is similar or possibly the exact same thing as what is described here http://forum.xda-developers.com/showthread.php?t=2743255
Does anyone know of a fix for the UI / Notification Bar crashes that are happening? I'm seriously considering getting a new tablet and using this as a good excuse.
Apparently clearing the davlik, cache, and doing a factory reset doesn't seem to help.
I'm running CM 11 M6 EMMC on my Nook HD+
Click to expand...
Click to collapse
How did you install it? Can you describe the process or link to the tutorial you used?
Did you do the factory reset before or after the install?
deleted
I can confirm the same problem. It is reproducible. Which does not mean it happens every time but over the course of using the tablet for 5 hours it happend around 3 times. Very very annoying!
Something similar happend when I heavily used Firefox without using the notification bar. Maybe it is also an issue when all memory is taken?! Should hopefully be fairly easy to fix since it was introduced somewhere between M4 and M6.
sirbender42 said:
How did you install it? Can you describe the process or link to the tutorial you used?
Did you do the factory reset before or after the install?
Click to expand...
Click to collapse
I've installed it flashing in CWM
I've tried doing the factory reset before and after the install.
Same issue here.
I am running CM 11 internal and have the same issue...
According to this post, this bug is due to be fixed in the next nightly.
ejstubbs said:
According to this post, this bug is due to be fixed in the next nightly.
Click to expand...
Click to collapse
I posted this. The bug report I posted sounds like the notification bug we see. According to the changelog the bugfix should be in starting with the cm-11-20140513-NIGHTLY-ovation.zip
You can download here: http://download.cyanogenmod.org/?type=nightly&device=ovation
Please let people know if this fixed it.
Still an issues (running 0515-nightly)
I flashed the nightly from 20140515 and am still having the resetting issue... Anyone else?
Does anyone know how to fix an issue where the screen never locks? It just shows the last app when the phone wakes up about half the time.
I have a Galaxy S5 unrooted and stock.
Haven't run into that but I'm having issues with random sleep of death and random reboots. Stock unrooted here as well. I've already done a cache clear and that seemed to work for about 24 hours but I just had another SOD.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
lathamc said:
Does anyone know how to fix an issue where the screen never locks? It just shows the last app when the phone wakes up about half the time.
I have a Galaxy S5 unrooted and stock.
Click to expand...
Click to collapse
I been having the same problem
lathamc said:
Does anyone know how to fix an issue where the screen never locks? It just shows the last app when the phone wakes up about half the time.
I have a Galaxy S5 unrooted and stock.
Click to expand...
Click to collapse
mcnaught82 said:
I been having the same problem
Click to expand...
Click to collapse
In settings, go to lockscreen > Secured Lock Time > Instantly. Thats how I fixed it.
amazingasian said:
In settings, go to lockscreen > Secured Lock Time > Instantly. Thats how I fixed it.
Click to expand...
Click to collapse
That doesn't fix the problem. I adjusted that setting as soon as I did the upgrade. It's a lollipop issue.
mcnaught82 said:
That doesn't fix the problem. I adjusted that setting as soon as I did the upgrade. It's a lollipop issue.
Click to expand...
Click to collapse
Was this listed under 'Lock screen'? I checked where the amazingasian stated, and couldn't find the option. That being said, it doesn't seem to be consistent enough to be a setting.
lathamc said:
Was this listed under 'Lock screen'? I checked where the amazingasian stated, and couldn't find the option. That being said, it doesn't seem to be consistent enough to be a setting.
Click to expand...
Click to collapse
Yes it's under lockscreen. To be able to see the setting, 1st u must select a lock screen type, not the regular swype screen. Then go back to the lock screen setting and the option will be available. But lime I said, doing that doesn't fix this issue. Yesterday I turned my screen on and off 3 times just to get it to lock.
mcnaught82 said:
Yes it's under lockscreen. To be able to see the setting, 1st u must select a lock screen type, not the regular swype screen. Then go back to the lock screen setting and the option will be available. But lime I said, doing that doesn't fix this issue. Yesterday I turned my screen on and off 3 times just to get it to lock.
Click to expand...
Click to collapse
Have you tried a lock screen from Play Store? That might solve the problem. I'm using Hi Locker currently, with no problems at all.
cmerlyn said:
Have you tried a lock screen from Play Store? That might solve the problem. I'm using Hi Locker currently, with no problems at all.
Click to expand...
Click to collapse
I haven't tried it, mostly because I actually like the look of the lock screen and its integration with the rest of the OS. I think it is more of a problem with the OS not recognizing that the screen has been turned off. Therefore, I think it is a problem that would affect all lock screens.
Could it be an issue with Smart Lock? I do have a smart device set up (the Sync system in my car), but the locking isn't being consistent in my car.
I am having an issue where the Samsung Keyboard crashes when used with some apps. Notably Facebook messenger. Anyone else notice this? Also, on occasion when opening the stock SMS app after unlocking the device, it automatically opens the bottom most conversation. I've cleared both data and caches for the apps. I am fresh install rooted lollipop the day it came out.
CAG-man said:
I am having an issue where the Samsung Keyboard crashes when used with some apps. Notably Facebook messenger. Anyone else notice this? Also, on occasion when opening the stock SMS app after unlocking the device, it automatically opens the bottom most conversation. I've cleared both data and caches for the apps. I am fresh install rooted lollipop the day it came out.
Click to expand...
Click to collapse
Try my new revised rooted 5.0 process which uses FlashFire. Much more accurate in regard to permissions and contexts.
muniz_ri said:
Try my new revised rooted 5.0 process which uses FlashFire. Much more accurate in regard to permissions and contexts.
Click to expand...
Click to collapse
Will do, I have been so busy lately, I did not even notice. Thank you.
my lollipop problems
Stock s5 with lollipop AT&T. Since update and even after cache clearing, I am suffering from extremely slow charging, too fast battery drain. Occasional sluggishness, and occasionally notifications don't work until phone unlocked.
I used muniz_ri's flash fire method keeping root which installs fresh and lollipop works flawlessly with no bugs, nothing broken. After install, google reinstalls your apps which many rediscover their stored settings on the internal sd. Most lollipop issues seem to be related to the stock update method or manual tibu restore... muniz fresh install lollipop is solid.
SoCalHTCFuze said:
I used muniz_ri's flash fire method keeping root which installs fresh and lollipop works flawlessly with no bugs, nothing broken. After install, google reinstalls your apps which many rediscover their stored settings on the internal sd. Most lollipop issues seem to be related to the stock update method or manual tibu restore... muniz fresh install lollipop is solid.
Click to expand...
Click to collapse
This makes me wonder then, because I was a fresh install with the original method Muniz had up. I only TiBu restored a few apps (none affected by my keyboard issue) and let everything else stay fresh. I am going to try the new method for the reasons Muniz pointed out to my prior post that listed the issues I had.
SoCalHTCFuze said:
I used muniz_ri's flash fire method keeping root which installs fresh and lollipop works flawlessly with no bugs, nothing broken. After install, google reinstalls your apps which many rediscover their stored settings on the internal sd. Most lollipop issues seem to be related to the stock update method or manual tibu restore... muniz fresh install lollipop is solid.
Click to expand...
Click to collapse
Totally agree. I also used the FF method and I have no problems what so ever with my phone. @muniz_ri came through again. Thanks.
Sent from my SAMSUNG-SM-G900A
Solution:
Go to Settings (if you're stuck in an app, use the button in your notification panel)
Go to 'System' (try tapping above the broken screen area)
Go to 'About this phone'
That should be all that has to be done! Do note: this fix isn't permanent. Let's hope Nokia fixes this.
Old thread:
Hello all!
When i woke up today and unlocked my phone (while an app is open) the bottom part (starting just above the nav-buttons) of my touchscreen just stops working.
I've had this problem a couple times (at most once per day) since updating from Oreo.
The solution to this problem seems to just to reboot the phone.. (This won't fix it permanently, sadly)
I'm asking if anyone else has this same problem, because i don't know the source of this problem.. (Maybe its because of the app not being P compatible?)
Thanks!
Hi, I have the same problem after the last update (september). Android Pie beta. Almost every morning i have to restart ..
Before the update was enough to just torn off/on the screen .
i don't have this problem on TA-1046 with Pie DP2-DP4.1 or Pie stable... maybe some incompatible apps? you use some for changing NavBar/Gesture area?
although i use XDA NavigationGesture what replace NavBar/Gesture with own, still not having problem, maybe you can try too this replacement, have many more function/settings that stock Pie gesture
for u its bottom touch screen is not working , but for me top of my touch screen isnt working .. and iam facing some serious problems after updating to pie . my phone restarts all of a sudden while charging , app crashes and more , hope hmd fixes this kind of issues in upcoming oct security patch update .
k3dar7 said:
i don't have this problem on TA-1046 with Pie DP2-DP4.1 or Pie stable... maybe some incompatible apps? you use some for changing NavBar/Gesture area?
although i use XDA NavigationGesture what replace NavBar/Gesture with own, still not having problem, maybe you can try too this replacement, have many more function/settings that stock Pie gesture
Click to expand...
Click to collapse
The app i left open last when it happened was "Boost For Reddit"
I'm using the old navbar layout (so no swipe)
dexterboon said:
for u its bottom touch screen is not working , but for me top of my touch screen isnt working .. and iam facing some serious problems after updating to pie . my phone restarts all of a sudden while charging , app crashes and more , hope hmd fixes this kind of issues in upcoming oct security patch update .
Click to expand...
Click to collapse
That's soo weird! I really hope HMD will release a patch soon.. I don't want to downgrade back to oreo
Issue with charging
I am having a charging issue. My phone usb and adapter is working fine with other phones. But when I connect my Nokia 7 Plus below 50%,My phone shows charging And when I tap the screen it doesn't charge. It occurs couple of time. And then It becomes normal and shows rapid charge after 55%. My charging port is fine when I connect it with my Pc usb port. some how the rapid charge doesn't respond. Does anyone have this problem?
Rahul Deshmukh21 said:
I am having a charging issue. [...]
Click to expand...
Click to collapse
What is real time for charge? Rapidcharging is disabled while you activated LCD
Yeah I'm facing similar issues, or did... I'm not sure... but it's been a non-issue for the past ~36 hours now. Here's to hoping it's not an issue any longer. I speculated it might be adaptive battery related somehow, so I tried rebooting my phone just before going to bed Sunday night, but my navbar still worked Monday morning, and this Tuesday it's still working in fact. I did this to test if it stopped working based on time since last reboot, or because some background process being killed due to adaptive battery/doze putting the phone to sleep. But based on my recent experience I think my hypothesis can be rejected. And I'm still not sure what caused it.
STcraft said:
Hello all!
When i woke up today and unlocked my phone (while an app is open) the bottom part (starting just above the nav-buttons) of my touchscreen just stops working.
I've had this problem a couple times (at most once per day) since updating from Oreo.
The solution to this problem seems to just to reboot the phone.. (This won't fix it permanently, sadly)
I'm asking if anyone else has this same problem, because i don't know the source of this problem.. (Maybe its because of the app not being P compatible?)
Thanks!
Click to expand...
Click to collapse
Same for me ta-1046, happened to me twice now. bottom part of screen stops reacting to touch. reboot fixes it.
Hmm... After playing around in the settings while having this problem active, for some reason, going to the phone info section just fixed it... I'm not sure if going there actually did that. needs more testing, I suppose.
+1 I use navigation gestures
STcraft said:
Hmm... After playing around in the settings while having this problem active, for some reason, going to the phone info section just fixed it... I'm not sure if going there actually did that. needs more testing, I suppose.
Click to expand...
Click to collapse
Huh, I'll be damned. When my nav bar was frozen this morning I went into the "about phone" section in the menu, and, lo and behold, my nav bar sprang back to life instantly. Now it might still just be a coincident of course, but it's certainly interesting, and could potentially be a fix where you don't have to reboot.
silverphoenix87 said:
Huh, I'll be damned. When my nav bar was frozen this morning I went into the "about phone" section in the menu, and, lo and behold, my nav bar sprang back to life instantly. Now it might still just be a coincident of course, but it's certainly interesting, and could potentially be a fix where you don't have to reboot.
Click to expand...
Click to collapse
surprised me as well that it worked. He could be a good beta tester. lol
Capture of
I managed to capture a video of the bounds of the touch-registration when the bottom 1,5 centimeter of the screen stops registering.
https://imgur.com/xrRB906
Same problem for me after upgrading a couple of days ago. Bottom of the screen (navbar and a bit more) is not accessible. Always happens after a night charging.
Going to the "About phone" menu fixes it. Thanks!
I have seen reports of people with other phones saying this is due to the setup wizard being active and preventing using the navigation bar. Tried some suggested adb commands without success. I will still try to disable the setup wizard app and report back.
IT ACTUALLY WORKS!!
AssKiRK said:
surprised me as well that it worked. He could be a good beta tester. lol
Click to expand...
Click to collapse
oh thank you! XD
Updated the OP
Please put a comment here as well: https://community.phones.nokia.com/support/discussions/topics/7000036457?page=1
This might help getting a quicker fix from Nokia.
Looks like the recent October patch still has this issue.
Would be nice if i can get a logcat this issue, but given this issue gets triggered after hours of inactivity, it would take a looong time to sift through the log.
Maybe there's a way to trigger it without waiting?
I can try logging when i do the "about phone" fix, will come back to this.
same isue here.. after chsrging at night nav bar bottom inch not responsive.. will try the phone info thing in the morning... is this software related ? will there be a patch??
At some point after upgrading to Android 9 I started having the following issue where if the screen turns off due to inactivity and I turn it back on by pressing the power button, I see whatever screen I had open before it went to sleep but it's frozen. Scrolling touching etc still perform (invisible) actions but the screen is frozen until I either press the app switch button or perform some action that would change the current application. While the screen is frozen the drawer from the top works just fine. Also when the app that gets frozen is the desktop (I'm using the default launcher), I can see the background scrolling if I swipe left or right but the widgets don't change, they are frozen.
Does anyone else have the same problem? Any ideas what could be causing it?
Tritonio_GR said:
At some point after upgrading to Android 9 I started having the following issue where if the screen turns off due to inactivity and I turn it back on by pressing the power button, I see whatever screen I had open before it went to sleep but it's frozen. Scrolling touching etc still perform (invisible) actions but the screen is frozen until I either press the app switch button or perform some action that would change the current application. While the screen is frozen the drawer from the top works just fine. Also when the app that gets frozen is the desktop (I'm using the default launcher), I can see the background scrolling if I swipe left or right but the widgets don't change, they are frozen.
Does anyone else have the same problem? Any ideas what could be causing it?
Click to expand...
Click to collapse
FWIW I have not really solved the problem but I am circumventing it by having the screen lock immediately instead of waiting 5 minutes. That way I have to unlock with a fingerprint every time the screen is off, and unlocking refreshes the screen which "fixes" the problem.
Tritonio_GR said:
FWIW I have not really solved the problem but I am circumventing it by having the screen lock immediately instead of waiting 5 minutes. That way I have to unlock with a fingerprint every time the screen is off, and unlocking refreshes the screen which "fixes" the problem.
Click to expand...
Click to collapse
There were lot of reports of glitchy phones after the Pie update.
The cure was a factory reset or software repair with Xperia Companion
Use Xperia Transfer to back up your calls/contacts/texts before you reset the phone
Didgesteve said:
There were lot of reports of glitchy phones after the Pie update.
The cure was a factory reset
Click to expand...
Click to collapse
Can you please link a thread, where users told, that problem is solved after reset?
I have the same frozen display (since Android Pie), when turning display off and on again.
Don´t wish to reset and install all again, if that does not help.
bye,
Ralf
thegrobi said:
Can you please link a thread, where users told, that problem is solved after reset?
I have the same frozen display (since Android Pie), when turning display off and on again.
Don´t wish to reset and install all again, if that does not help.
bye,
Ralf
Click to expand...
Click to collapse
Hi Ralf,
the phone will always work better with a reset after a major update, all the Oreo applications are trying to work under Pie. Sometimes it works, sometimes it doesn't. Oreo apps aren't made to work under Pie and they can error.
here, is one example, or another, but I didn't jump to Pie because of all the negative feedback and the scores of people trying to downgrade.
A reset will fix your problem and if you use Xperia transfer then the amount of personal information lost will be minimal.
Thanks for the links.
Didgesteve said:
all the Oreo applications are trying to work under Pie. Sometimes it works, sometimes it doesn't. Oreo apps aren't made to work under Pie and they can error.
Click to expand...
Click to collapse
This sounds to me, the combination of "old" Navi-apps with Pie is the problem. May be only with Pie on some Sonys.
I'm afraid, a reset will not change the frozen display.
All other apps till now do not freeze after display-on except MagicEarth and Osmand+
This 2 apps i deinstalled (+ deleting the data) and installed again.
A reset will fix your problem and if you use Xperia transfer then the amount of personal information lost will be minimal.
Click to expand...
Click to collapse
Xperia transfer shows me only 2 apps for backup.
I'll probably try a reset in the next few days anyway.
bye,
Ralf
thegrobi said:
Thanks for the links.
This sounds to me, the combination of "old" Navi-apps with Pie is the problem. May be only with Pie on some Sonys.
I'm afraid, a reset will not change the frozen display.
All other apps till now do not freeze after display-on except MagicEarth and Osmand+
This 2 apps i deinstalled (+ deleting the data) and installed again.
Xperia transfer shows me only 2 apps for backup.
I'll probably try a reset in the next few days anyway.
bye,
Ralf
Click to expand...
Click to collapse
Looks like there is know issue with the Osmand+, the date of the post is may last year, but it may just be a 'feature'
When backing up with Xperia transfer, make sure you select all the boxes that are optional. It's things like text messages/contacts/phone history that are useful after a reset. Some apps can't be moved and have to be downloaded directly from the playstore, but Google should give you that option, after you log back in to the wiped phone.
Edit: I can recomend Sygic, free maps for one country, works without data.
In the meantime, I found more users with this problem and a little solution that another user describes:
I can confirm I have the exact same issue since Android 9 with my Xperia xz1 compact.
I normally have no lockscreen options set. So when I wakeup the Phone, it sometimes kind of 'locks' the screen. Widgets do not respond, I cannot switch home screens. The time on the status bar remains correct. If I then click on an app and go back, everythning behaves normally.
So I'm quite sure this must be a software issue, as other people have this problem to.
My workaround for now is to have a lockscreen option aktive. But I would rather have not, for conveniance.
I tested this also with safe mode and complete factory reset of the phone. The 'bug' is still there.
Click to expand...
Click to collapse
If I disable lockscreen, then apps stop when it is switched on again. However, I always have to enter pin or use fingerprint sensor, or smart lock.
This often does not work when cycling and is dangerous when cardriving.
On Android 8, the lockscreen did not need to be active.
So the problem is not Osmand and MagicEarth.
It is a Sony 9 bug with Android 9.
bye,
Ralf
Found in an other forum an easy method to reproduce the problem.
disable the screen lock (it must be set to "None");
lock the phone and then unlock it;
lock and unlock it again.
Click to expand...
Click to collapse
bye,
Ralf
---------- Post added at 01:50 PM ---------- Previous post was at 01:20 PM ----------
Because I believe that Sony will not fix the error, I could imagine a solution:
An app (possibly tasker), which puts a selectable running app from foreground while pressing the power button in the background and immediately brings it back to the foreground.
Does anyone know such a tool?
bye,
Ralf
[/COLOR]Because I believe that Sony will not fix the error, I could imagine a solution:
An app (possibly tasker), which puts a selectable running app from foreground while pressing the power button in the background and immediately brings it back to the foreground.
Does anyone know such a tool?
bye,
Ralf[/QUOTE]
So, did you ever find a solution?
I've got the 8gb/128gb version of the phone the last weekend. I'm having this issue where the phone is not responsive to the touch for about 1~2 seconds after I wake it up (either by double-tapping the screen or pressing the power button).
This happens after the screen is off for a few minutes (even if playing music in Soundcloud/Youtube Vanced). It'd turn on the screen but I can't interact with the screen right away.
I used to have a similar problem with my Razer Phone 1 and it happened whenever I tried to hide the navigation bar or use a different navbar/gestures. I have gestures enabled in the ROG 2, but not sure if it's related. Also, I think it came with WW ROM, I don't know if that'd matter.
I'd really appreciate any input from you guys on how to solve this. Thanks
el4nimal said:
I've got the 8gb/128gb version of the phone the last weekend. I'm having this issue where the phone is not responsive to the touch for about 1~2 seconds after I wake it up (either by double-tapping the screen or pressing the power button).
This happens after the screen is off for a few minutes (even if playing music in Soundcloud/Youtube Vanced). It'd turn on the screen but I can't interact with the screen right away.
I used to have a similar problem with my Razer Phone 1 and it happened whenever I tried to hide the navigation bar or use a different navbar/gestures. I have gestures enabled in the ROG 2, but not sure if it's related. Also, I think it came with WW ROM, I don't know if that'd matter.
I'd really appreciate any input from you guys on how to solve this. Thanks
Click to expand...
Click to collapse
I've got same phone on the latest ww rom (there's an update, might help) and haven't seen this yet. So you use double tap to wake? Any screen off gestures? Would be interesting to figure out which feature is misbehaving
xxBrun0xx said:
I've got same phone on the latest ww rom (there's an update, might help) and haven't seen this yet. So you use double tap to wake? Any screen off gestures? Would be interesting to figure out which feature is misbehaving
Click to expand...
Click to collapse
It doesn't show any new update when I check. I believe it's because I dont have the CN ROM. Yes I do use double tap to wake. I will disable it and use it during a day to see if it change. If not, I'll try using the navbar instead of gestures. I haven't set up any screen off gesture. I'll report back if I find something
el4nimal said:
It doesn't show any new update when I check. I believe it's because I dont have the CN ROM. Yes I do use double tap to wake. I will disable it and use it during a day to see if it change. If not, I'll try using the navbar instead of gestures. I haven't set up any screen off gesture. I'll report back if I find something
Click to expand...
Click to collapse
This also happened to me when I converted to WW ROM, and to many others as well. It affected my gaming experience so much so I converted back to CN ROM. I will be using the CN ROM until this problem is fixed.
Guys can u tell me where to set the double tap to wake the phone? Thanks
Found it. Dang all this time I didn't know this exist
Nb I tried using it and my phone is working great and fast. I'm using ten cent version.
It has nothing to do with what I mentioned. I think I'll reset my phone or convert it to the CN Rom
I have the same issue unfortunately - A 1 second delay when I tap to wake (screen kinda just freezes for a split second then turns responsive again).
Not a big deal, but wondering what is the issue.
Enigmatic331 said:
I have the same issue unfortunately - A 1 second delay when I tap to wake (screen kinda just freezes for a split second then turns responsive again).
Not a big deal, but wondering what is the issue.
Click to expand...
Click to collapse
I still have the same issue. I went from WW rom to CN rom, but it did not fix that issue. Most of the time does not happen, but sometimes it can freeze up to 5 seconds, which can get quite annoying
el4nimal said:
I still have the same issue. I went from WW rom to CN rom, but it did not fix that issue. Most of the time does not happen, but sometimes it can freeze up to 5 seconds, which can get quite annoying
Click to expand...
Click to collapse
Mmm. Hey, I am currently on Android 10, and the problem seemingly is gone (actually it kinda looks like there's a split second animation which makes the delay unnoticeable) - Give that a try to see if it helps?
5 seconds is horrible!
Enigmatic331 said:
Mmm. Hey, I am currently on Android 10, and the problem seemingly is gone (actually it kinda looks like there's a split second animation which makes the delay unnoticeable) - Give that a try to see if it helps?
5 seconds is horrible!
Click to expand...
Click to collapse
Im not sure about going to Android 10, is it still a beta right? The issue disappeared for me the first days when I changed to CN rom, but it came back a couple of days later :/
To update - Am on Beta 6 - So far so good. The problem hasn't come back yet. Only catch is double tapping is a slight bit less sensitive than before.
Once the official Android 10 release is out, hopefully that would sort you out for good!