After latest update my phone thinks I'm trying to enter split screen or something and draws the blue sparkly line when I'm just trying to do something ordinary.
I haven't found a way to completely disable knuckles gestures even though it's off in the accessibility settings.
Halp!
Same issue here, even after stop it.
Same issue I that I have, I try to disable it from accessibility options, but it doesn't work
Same ****. Also thought that after the update this setting got reset but it's disabled...
Me too! It is really annoying and I've been trying to find a way to stop it from coming up! It keep messing up my gameplay! lol
Same issue here
Performed the steps from Huawei support and no success.
I've done clean cash and settings reset
On the end they confirmed that this is emui 10.1 issue.
Interesting that the guy from support team has the same phone as mine and had no problems after update.
The final suggestion was to roll back to 10.0 or wait for the update from Huawei.
Ok, I've found a temporary solution, but you need to use appAssistant.
For any apps that are giving you issues with the knuckle gesture, add them to appAssistant, and allow appAssistant to run. Then make sure you select the option in appAssistant to disable knuckle gesture.
Hope the fix comes out soon. But for now, this is good enough.
Any updates on this?
So after phone reset I ended up with rolling back to 10.0 and disable auto update.
I'll wait for the patch from Huawei
Thanks
Looks to be bugged in EMUI 10.1 and Huawei is aware of the issue... hopefully able to solve it soon. It's quite irritating.
https://consumer.huawei.com/uk/community/details/Knuckle-gesture-stuck-on-emui-101/topicId_32937/
They are simply not going to fix this. Back to Samsung guys.
noelho said:
Ok, I've found a temporary solution, but you need to use appAssistant.
For any apps that are giving you issues with the knuckle gesture, add them to appAssistant, and allow appAssistant to run. Then make sure you select the option in appAssistant to disable knuckle gesture.
Hope the fix comes out soon. But for now, this is good enough.
Click to expand...
Click to collapse
This is So far the best solution/temp fix
Jonkki said:
After latest update my phone thinks I'm trying to enter split screen or something and draws the blue sparkly line when I'm just trying to do something ordinary.
I haven't found a way to completely disable knuckles gestures even though it's off in the accessibility settings.
Halp!
Click to expand...
Click to collapse
Like this?
leet8845 said:
Back to Samsung guys.
Click to expand...
Click to collapse
crazy...
Latest
Related
This just happened to my phone for whatever reason. The bottom portion of my screen (where navigation is located) will not work any longer. I know the touchscreen is still working, because i can scroll down a website and it still will recognize touch but not if I am trying to use the navigation buttons. I have tried gesture, 2/3 button but none of them work. I even flash a stock image (didn't do a full wipe just unrooted it) to see if this would fix. If anyone has a fix for this please let me know.
Thanks!
pimp11774 said:
This just happened to my phone for whatever reason. The bottom portion of my screen (where navigation is located) will not work any longer. I know the touchscreen is still working, because i can scroll down a website and it still will recognize touch but not if I am trying to use the navigation buttons. I have tried gesture, 2/3 button but none of them work. I even flash a stock image (didn't do a full wipe just unrooted it) to see if this would fix. If anyone has a fix for this please let me know.
Thanks!
Click to expand...
Click to collapse
I came here to see if anyone else was having the same issue! Yes, i have to hit the docked icons several times before they open. wasn't an issue a day or two ago......
Sucks but glad to see i'm not alone. must've been some kind of play services update or something that broke it.
hochoch said:
I came here to see if anyone else was having the same issue! Yes, i have to hit the docked icons several times before they open. wasn't an issue a day or two ago......
Sucks but glad to see i'm not alone. must've been some kind of play services update or something that broke it.
Click to expand...
Click to collapse
It's very annoying. I figured something happened with my root, but i unrooted and problem still persists. Basically unusable as i have to go back through apps instead of going home .
hochoch said:
I came here to see if anyone else was having the same issue! Yes, i have to hit the docked icons several times before they open. wasn't an issue a day or two ago......
Sucks but glad to see i'm not alone. must've been some kind of play services update or something that broke it.
Click to expand...
Click to collapse
Yep having the same issue. The dock icons aren't always working, but the screen does because I can still scroll everywhere.
I also noticed that not all of my screen is being used. I black bar bezels on the sides of my screen. Looks like a full reset is inbound when I get home.
Ok, i was on plays services 19.4.20 and updated to the beta and now this is fixed!
Here is the beta version from apk mirror: https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-19-5-28-release/google-play-services-19-5-28-120400-273329419-android-apk-download/
you can install this app to quickly check your version. it used to link right to apk mirror but they took the functionality out unfortunately: https://play.google.com/store/apps/details?id=com.weberdo.apps.serviceinfo
whew - glad that was an easy fix! hopefully it doesn't auto-update and break it again or something.
This has been going on with me since a mid september update. JUNK PHONE this pixel 3!!! First phone by google that I really hate. Contacted google about that, they asked me to clear all cache from the UI, play, etc... I still have the same issue...
I have stock, no root.
karikian said:
This has been going on with me since a mid september update. JUNK PHONE this pixel 3!!! First phone by google that I really hate. Contacted google about that, they asked me to clear all cache from the UI, play, etc... I still have the same issue...
I have stock, no root.
Click to expand...
Click to collapse
Personally first big issues that I have had with the phone. I just full restored and am restoring everything from the built in backup now. It fixed the issue though so at least i don't have to buy a new phone lol.
hochoch said:
Ok, i was on plays services 19.4.20 and updated to the beta and now this is fixed!
Here is the beta version from apk mirror: https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-19-5-28-release/google-play-services-19-5-28-120400-273329419-android-apk-download/
you can install this app to quickly check your version. it used to link right to apk mirror but they took the functionality out unfortunately: https://play.google.com/store/apps/details?id=com.weberdo.apps.serviceinfo
whew - glad that was an easy fix! hopefully it doesn't auto-update and break it again or something.
Click to expand...
Click to collapse
I tried this and no dice. Had to full wipe and restore. Oh well. Glad it worked for you however!!!!
I just updated to EMUI 10 last week which has been great, but today it updated again to 10.0.0.188 and now I keep getting a notification about my full screen gestures app (I use it along with the system full screen gestures) which I can't disable. It says "If you don't want" this feature I can disable it, but I DO want it. All I can do is put it on 'gentle notification' so it only sits in my notification bar but it's just taking up space for no reason. There's got to be a way to disable this notification.
Vicxx said:
I just updated to EMUI 10 last week which has been great, but today it updated again to 10.0.0.188 and now I keep getting a notification about my full screen gestures app (I use it along with the system full screen gestures) which I can't disable. It says "If you don't want" this feature I can disable it, but I DO want it. All I can do is put it on 'gentle notification' so it only sits in my notification bar but it's just taking up space for no reason. There's got to be a way to disable this notification.
Click to expand...
Click to collapse
Maybe cannot be removed
PhoneTechShop said:
Maybe cannot be removed
Click to expand...
Click to collapse
Thank you for taking time out of your day just to say maybe, I'll definitely come to you in future when I need more maybes, what an amazing contribution.
Have you tried disabling that feature, then rebooting your phone and going into settings an enabling it again once it's booted back up?
Toggling on/off rebooting, etc. That's all I can think of.
Also, since you just updated, have you considered resetting the phone? I know it's a major pain, but it might help. Last resort of course. I had to reset after my most recent update before the one I got today. I'm hoping I don't have to reset this time.
Vicxx said:
Thank you for taking time out of your day just to say maybe, I'll definitely come to you in future when I need more maybes, what an amazing contribution.
Click to expand...
Click to collapse
You are welcome
Hi everybody,
I'm running the Android 11 public beta and to be honest I've been doing so pretty much since I bought the 3a XL, so I can't remember if this was an issue beforehand. I am having absolutely no issues elsewhere.
Basically when a text, WhatsApp, Gmail or anything like that comes through I get the sound but the screen doesn't light up.
I don't have AoD activated (can't stand using them) but I do have the toggle for lighting up for new notifications activated. I have no power saving modes or do not disturb settings switched on and all notification settings for my apps seem to be fine. I don't want to reset my phone and start all over again as I really can't be bothered just for this one thing, and it would also use up my last slot with YouTube Premium so I'd have to call them to clear my device list again.
Please can someone think what might be happening here. Is this a bug with 11? Or can anyone think of anything else to try.
Many thanks
Maybe check lockscreen settings and see if you're not allowing the notifications there.
41rw4lk said:
Maybe check lockscreen settings and see if you're not allowing the notifications there.
Click to expand...
Click to collapse
Show all notifications etc are on. When I tap the screen the notification is there so it's not hiding it or anything - it just doesn't light the screen up.
Double check all settings in Display > Lock screen display. I think all the action is there. I'm sorry if this is menial or redundant. Just offering up ideas, it could be a bug but I can't verify it since I'm not on 11.
41rw4lk said:
Double check all settings in Display > Lock screen display. I think all the action is there. I'm sorry if this is menial or redundant. Just offering up ideas, it could be a bug but I can't verify it since I'm not on 11.
Click to expand...
Click to collapse
Yeah sadly I've been through all the settings and I really can't find anything that would be causing this. I thought maybe it could even be a faulty proximity sensor or something but that's working fine too.
I was hoping that it was a known bug because then at least I know it'll get fixed, although this issue has survived the most recent beta update.
leoni1980 said:
Yeah sadly I've been through all the settings and I really can't find anything that would be causing this. I thought maybe it could even be a faulty proximity sensor or something but that's working fine too.
I was hoping that it was a known bug because then at least I know it'll get fixed, although this issue has survived the most recent beta update.
Click to expand...
Click to collapse
Here's a screenshot of my settings, not sure how much will match with yours but I can't imagine much difference. Either way I get notifications the way you want with these settings. If you don't you might file a bug report.
https://imgur.com/a/DGqXkIR
It's happening on my phone also. Maybe a bug in Android 11
After yesterday's update to Tizen 5.5.0.1. When you turn your hand, the screen lights up. What was not before in the do not disturb mode. Active Watch 2. Tired of looking for a solution how to make sure that the screen does not turn on? Thanks in advance.
Sorry for bad english, google translate
If you have wake up gesture activated on your watch, deactivate it and activate again. It worked for me.
can I delete and skip this update version? My watch is working great since previous ecg/fall detection update.
Grootoy said:
If you have wake up gesture activated on your watch, deactivate it and activate again. It worked for me.
Click to expand...
Click to collapse
Thanks for the answer, but it didn't work
Did you do this in wearable app also?
Sorry for stupid question, but sometimes **** happens.
Grootoy said:
Did you do this in wearable app also?
Sorry for stupid question, but sometimes **** happens.
Click to expand...
Click to collapse
Good afternoon, yes, I did it in wearable and on the clock. I even did a factory reset, it seems to me that the Samsung just removed this option from the clock, now the screen always turns on in the do not disturb mode. I don't know what to do anymore.
valmar said:
Good afternoon, yes, I did it in wearable and on the clock. I even did a factory reset, it seems to me that the Samsung just removed this option from the clock, now the screen always turns on in the do not disturb mode. I don't know what to do anymore.
Click to expand...
Click to collapse
It's strange situation. I see several of us have the same watch active 2, but after last update the same watches have different problems.
May be you need to reinstall OS. Just use tizen 5.5.0.1 again. I hope it helps to solve the problem.
Grootoy said:
It's strange situation. I see several of us have the same watch active 2, but after last update the same watches have different problems.
May be you need to reinstall OS. Just use tizen 5.5.0.1 again. I hope it helps to solve the problem.
Click to expand...
Click to collapse
Thanks for the advice, I have already resigned myself, changed the wake-up of the clock with a touch and probably will leave it that way. Good luck!
+1 same problem
Hi, this is not a bug but an intended change of Samsung. DND mode means no notifications. But you should be able to just look at the time when you lift your wrist. Before the update that was disabled and now they enabled it in DND mode. The only way to disable it is disable wake up gestures in general.
S21fe updated to UI5.
Couple of issues.... Fingerprint reader sometimes doesn't work when phone hasn't been used for some time. When it happens I need to double tap the screen to wake it up and then scan my fingerprint again.
Also "back" gesture (where I swipe up from the right bottom of the screen) sometimes instead of going back brings up the list of background apps.
Both issues very annoying.
Anyone else experienced anything similar?
Try clearing the system cache. Double check all settings. If that flaws things get more complicated...
A factory reset may be needed, but hard to say if it will resolve the issues. Someone will need to try the latter if the former doesn't work. A global reset of settings is a less drastic option but it may not be enough and still take a lot of time.
This is one reason why I spurn upgrades on a platform that's fulfilling its mission. Lol, I'm still using UI 1.5, no glaring issues.
Unfortunately with latter versions an upgrade may resolve flaws in earlier post >1.5 variants. Tough choice once you are on Android 11 as there's no roll back on stock Samsung's for that. I wasn't locked into using 11 on my N10+'s and never will load it. 12 is even worse.
Roll back is an option for you if bootloader wasn't upgraded too. Eventually Samsung will fix it if it's a firmware/software glitch but don't hold your breath for that
blackhawk said:
Try clearing the system cache
Click to expand...
Click to collapse
With each major update, I always clean the system cache from the recovery !
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
That may not be enough if going from 11 to 12, etc.
Rule #1 - if the OS is fast, stable and fulfilling its mission let it be! You have little to gain and a lot to lose. Although there was a big security hole in 12, not sure if it was patched already or if the patch is in what you just install. Oddly that hole isn't in 9-11.
Gookill is a mess...
I have the same problem with fingerprint unlocking. It simply doesn't work (if I press the side button, it works). Some hours ago I wiped the system cache and after that, I didn't notice the described problem. I will see in the next few hours.
Now I changed "Fingerprints -> Show icon when screen is off" to "Tap to show" instead of "On always on display" which was the default after the upgrade to Android 13.
UPDATE: The phone still has the same problem. Sometimes it simply doesn't allow it to unlock with a fingerprint. The screen is locked as hell. Only the side button unlocks it.
If you go to Lock screen>Always On Display>Show always, does that solve your problem? Mine was set to "show for new notifications" only and the fingerprint icon would disapperar after locking it.
Mine was set to "Show for new notifications". As you suggested, I changed it to "Show always" and we will see, how it works. In my opinion, it is better to show display only when something happens. But something changed and problems occurred.
Report: it didn't help. I have found out that the issue appears if the phone is locked for a while and then a notification comes. This is the reason why this problem exists also while using Android Auto. It creates a notification when it connects ... and then the phone can be unlocked with a fingerprint until the side button is pressed. I'm sure this is a bug that didn't exist before the upgrade to Android 13.
no such issues here with the eu version. definitely an upgrade in every way.
After 3 days with Android 13 on snapdragon variant, only two minor issues found here : slow charging (2h20 from 0 to 100, less than 2h before) and an "unauthorized action due to modified device" screen when rebooting, disappearing by touching "OK" button. Don't know what is unauthorized but... well. I was rooted before, now stock unrooted and relocked bootloader. It doesn't seems to lock something, everything I use is working.
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
d0j0m0j0 said:
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
Click to expand...
Click to collapse
The recent update with the December security patch seens to have resolved this issue for me.
Edit: scratch that, still not fixed...
Edit2: turning off lock scrern mods in Galaxy MaxHz seems to help.
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
How does one do that?
xda-eh said:
How does one do that?
Click to expand...
Click to collapse
It's on the boot menu on Samsung's.
blackhawk said:
It's on the boot menu on Samsung's.
Click to expand...
Click to collapse
You're referring to accessing the recovery mode as explained here?
xda-eh said:
You're referring to accessing the recovery mode as explained here?
Click to expand...
Click to collapse
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
blackhawk said:
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
Click to expand...
Click to collapse
The link I provided and the one you did refer to the same thing. Only difference is my link also provides a way to do it via ADB. In any event, thanks for your response.