Hello, has anyone had problems with the watch notifications?
The problem I have is that the notifications do not appear on the clock screen, nor do they vibrate, nor do they sound; only until I swipe from bottom to top I see that there are notifications.
I already spoke to Huawei support and they ask me to activate special notification permissions that I cannot find in the settings.
I hope someone can help me.
Have you already attempted to enable any available permissions from the app details under Apps in Settings?
Hello, thank you very much for answering.
I have already managed to get the notifications to work for a few hours, but after a few hours the same thing happens again. I have activated all accesses of the Health application, such as access to notifications (In the menu "special access to apps"), permissions to contacts, phone, etc. The Health app is also out of battery optimization.
Huawei's support asks me to activate this:
Settings> Privacy> Management> Special app permissions> Notifications> Huawei Health.
I hope I have explained myself well.
If it consistently seems to work until the phone is idle for a couple hours, you should check all of the different settings for battery and background data throughout the phone and see if one of them is to blame. There are quite a few different settings for this, including some also in Developer Options if you enabled those.
Hi.
When it worked for a while and then no longer, it was the first thing I thought. Something is killing some service or task and that's why they stop coming. But it is nothing like that, the notifications do reach the clock, but it does not vibrate or sound. I already put the application without battery optimization, which starts automatically, blocked in tasks, application services the same. I can not think of anything else.
Thanks for the help.
After doing more research, I came to a huawei forum in Chinese and found the answer. The watch can detect that it is not being used, that you are not wearing it and tattoos can make the watch think that it is not being used. I have my entire left arm tattooed, change the wristwatch and it works perfectly. But I don't know how this leaves me a little unsatisfied, I don't know.
It doesn't have a way to disable that? Might want to suggest it to them. Usually features like that aren't hardcoded because such situations exist.
No, the GT2 series has a sensor dedicated specifically to that. I can only return it, change the hand to the one that is not tattooed or erase the tattoo.
Related
After what I've read about Lollipop so far I'm getting kind of ambivalent about updating. Here are two of my concerns in regards to notifications:
1) Heads-up notifications. Apparently developers are the ones that are now in control of whether notifications are important enough to completely blot out a piece of the top of the screen, including the ability to access the notification tray, until the notification is handled. So whereas before I could remain completely immersed in whatever app and wait until I decide I'm ready to pull down the shade, now I am forcibly blocked from accessing part of the app and user interface until I first interact with the notification. As far as I can tell users are unable to do anything about this intrusion.
2) Silent mode - it sounds like a lot of users are really upset already about this screw-up. The old silent mode allowed alarms through which was just perfect for the use case of alarms. You go to bed and you want your phone to shut up completely until the alarm that is supposed to wake you up. Now apparently the only real silent mode also silences alarms. "Priority mode", the feature that is used for so-called quiet hours, still lets through all sorts of vibrations from apps that many users cannot sleep through.
Are these accurate descriptions of the current state of affairs in Lollipop? If so I think it'll drive me nuts and I won't be able to switch until I can take control of these flaws. And with Xposed unavailable for the foreseeable future it means having to figure out how else to hammer a broken OS into respecting the functionality that used to "just work". Does this bother anyone enough that they'll just avoid upgrading for now?
I don't think so at all, it takes some getting used to because the system is alot more iphone-Esq in nature but it definitely works well. There is alot of few features that just bring the whole system up to date, feels very very modern now. Like when you plug the phone into the charger it tells you how much time is remaining until the phone is full, for instance my phone says 47 minutes until full right now in the charger. It can predict how much battery life remains based on typical usage. Having notifications on the lock screen so you don't have to go through the lock screen and then the pull down menu to see whats going on is very convenient. As far as silent mode goes, there is plenty of settings that allow alarms and events to still work even though calls and messages are silent, I like how they ditched the stereotypical "vibrate" or "silent" modes and went with "all" priority and "none". There are always going to be people that are very resistant to change and claim that its awful, but I feel this was a much needed update to the android system.
Nonetheless if I'm given only the choice now between either intrusive or useless notifications, it's not very appealing.
Sent from my Nexus 5 using Tapatalk
but you are given a choice
Spawne32 said:
but you are given a choice
Click to expand...
Click to collapse
The choice I am looking for is:
1) Completely disable heads-up notifications and keep them all in the notification tray, because if I'm doing something on my device I damn well want to stay in what I'm doing instead of other apps getting to choose if they can block part of my screen.
Can I do this on Lollipop?
2) At night, silence everything, *never* vibrate for anything ever, but allow alarms (and possibly voice calls) to ring.
Can priority mode do this?
From what I am reading, people are complaining that vibrate notifications are still leaking through in priority mode.
Can't say I've noticed any vibrations from apps.
cmstlist said:
The choice I am looking for is:
1) Completely disable heads-up notifications and keep them all in the notification tray, because if I'm doing something on my device I damn well want to stay in what I'm doing instead of other apps getting to choose if they can block part of my screen.
Can I do this on Lollipop?
2) At night, silence everything, *never* vibrate for anything ever, but allow alarms (and possibly voice calls) to ring.
Can priority mode do this?
From what I am reading, people are complaining that vibrate notifications are still leaking through in priority mode.
Click to expand...
Click to collapse
I use 'None' at night and it stops everything, as designed, but I've not tried an alarm as I have a clock for that. Turning on 'Priority' alerts, but turning calls/messages/Events off, should only allow alarms through but, again, I've not tried this.
As for notifications, I've been watching videos on YouTube full screen and the notification hasn't popped up unless I drag down to view the bar so doesn't seem to be an issue
Best thing to do? Back up your phone, flash 5.0 and if you don't like it go back to 4.4.4 and restore your backup
cmstlist said:
CUT
2) At night, silence everything, *never* vibrate for anything ever, but allow alarms (and possibly voice calls) to ring.
Can priority mode do this?
From what I am reading, people are complaining that vibrate notifications are still leaking through in priority mode.
Click to expand...
Click to collapse
THIS.
Audio management is just a pain in the ass. I got the same need, when I go sleep I don't want ANY sounds from the phone except wake up alarm and calls coming from a whitelist.
Actually this is not possible. If I set interruption mode, it doesn't silence any other sounds (eg: try to put the charger in and you'll hear the sound/vibration), and If I set the completely silent mode it doesn't allow interruptions.
I used to use a third party app named Nights Keeper, it was perfect running on KitKat, but now it is not on Lollipop, as it can't set the phone on totally silent mode except calls from whitelist.
Dunno if it's a bug or a "feature", the fact is that i'm not satisfied with this, and i can't "fix" it with 3rd party apps.
I always recommend that one: https://play.google.com/store/apps/details?id=com.antonc.phone_schedule
Works like charm for the father of 2 year old - mute from 21 to 6:40 am, all alarms always on proper volume.
unster said:
I always recommend that one: https://play.google.com/store/apps/details?id=com.antonc.phone_schedule
Works like charm for the father of 2 year old - mute from 21 to 6:40 am, all alarms always on proper volume.
Click to expand...
Click to collapse
does it work properly on Lollipop?
'cause this app https://play.google.com/store/apps/details?id=com.nightskeeper&hl=en is supposed to do the same, but it actually doesn't works with L
I think so. Just tested it briefly and seems to work on me.
just to say that i've created a new Enhancement request here: if this means something for you here having the same needs of me, please partecipate.
https://code.google.com/p/android/issues/detail?id=79334&colspec=ID Type Status Owner Summary Stars
I've noticed some issues with notifications in lollipop aswell.
Most disturbing is that notifications just pop up as icon in the status bar, except the app is heads up supported (like hangouts) than you get the heads up notification of course.
Before you had at least something like a banner. Even if it was only one line, at least you knew from whom your eg. message or email was and the subject or the first words.
It's seriously just the icon now
That devs have to implement things like buttons or a textbox is obvious, but just the text???
Come on google...
In regards to that app - I have read that when pre Lollipop apps try to put the device into Silent mode, instead it goes into Priority mode. Including Tasker. This may explain observations noted upthread.
Sent from my Nexus 5 using Tapatalk
With HeadsOff lollipop heads-up notifications can now be disabled!
No root needed.
You can also restore the ticker text in the statusbar!
Give it a try:
Download from Playstore
XDA thread
I'm having a very, VERY difficult time getting this phone comfortably paired with my new Huawei watch. Irony of ironies, my Asus zenwatch 2 performed flawlessly for many months with the device, but since a factory reset, I can not get this to consistently stay paired with EITHER watch, leading me to believe it's an issue with the software, or the phone itself. I've got Android wear set to run with screen off, and ignoring battery optimizations, but still, many many times notifications I see received on my phone won't push to the watch, unless I open the Android wear app on my phone, at which point they forward immediately to the watch. Obviously, this is less than ideal to have to repeatedly do.
I've called Googles service number, and after very little troubleshooting they forwarded me to Huawei, who said I have to talk to the Chinese headquarters because Huawei USA doesn't service international devices. They don't have an international phone number that I've been able to find yet (Huawei USA has a wrong number listed for them.) And they haven't responded to my emails.
I've gone through many, many trial and errors trying to fix it on my own. I'd flash a custom rom if I was sure that would help, but I'm not versed in those ways, and I'd like to exhaust every other possibility before risking bricking.
I'm desperately trying to find a particular settings menu, for notification access, that emotion ui has squirrel away somewhere. I can tell it's a Huawei setting and not an android wear setting based on the aesthetics of the screen, but the only time I'm able to see this setting is when installing Android wear for the first time.
I'd like to check this setting WITHOUT having to unpair my watch and reinstall Android wear, but no amount of digging through the settings menu of emotion ui has shown me where to find it. It isn't in the notification menu, nor in permissions. Any gurus of this Android skin know where to find the notifications access settings page?
I have screenshots of the settings menu to show what I'm trying to find, but due to my post count I can't share links to them in this post, but I can pm them if that is helpful.
As an update to my situation, I discovered a slightly inelegant solution to accessing the notification access menu : I've started using an app called feel the wear to emphasize the notification vibrations, since the Huawei watch, particularly with a metal link band, is a little weak on the vibration motor. By uninstalling and reinstalling the app, it sends me to the notification access page again. The bad news, is that when my problem manifested again (after a phone restart, an event that consistently seems to be the catalyst for this) I reinstalled feel the wear, and Android wear was still enabled to have notification access.
So, to summarize, I've eliminated the following possibilities through troubleshooting that might cause the notifications to stop pushing to the watch unless I open the Android wear app on my phone (which immediately pushes the notifications to my watch.)
-notification access for Android wear
-doze settings (battery optimization is disabled for Android wear)
-Android wear has full permissions (trusted app)
-Android wear is set to auto launch, and is permitted to continue running after screen off.
Now, while I was in the notification access menu after reinstalling feel the wear, I did disable and then re-enable notification access for Android wear. This caused the watch to restart, notifications haven't delayed since that yet, but it hasn't lasted long enough for me to be comfortable that this remedies the issue.
Unpairing and repairing the watch every time this occurs isn't acceptable, is there any light to be shed on what could still be causing my problem?
Finally, if it could be any help, I'm a Tasker user, so if there is a profile I could write with a trigger when receiving a notification that might help, I have access to that utility. I tried writing one already, that, when my screen was off, would automatically open the Android wear app when receiving a notification from my three main apps that I monitor, but while the app was indeed open when I received notifications from one of those apps, it appeared that until the app was open with the screen ON, the notifications wouldn't push through, so it didn't solve my problem. Don't know if there's any action I can put in a profile that might "wake up" Android wear when I get a notification. (I hope my diligence in these Tasker pursuits illustrates the effort I've put into making this work, I adore this phone, and love Android wear, and really want them to play nicely together.)
Came across this thread while Googling for the same problem. I found a solution that while still inelegant, is better than the one you have here. I downloaded More Shortcuts. Which allows access to various settings activities that Huawei seems to hide, including Notification Access. Some of the android default stuff is there but then not functional. For example, I went to Data Usage which took me to a screen with black text on a black background, though also included a toggle and a dropdown that brings stuff up...
I tried downloading this app, but it doesn't seem to work with Nova Launcher. I'm curious to see what else I can modify
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Good morning. Please, i deactivate all possible energy saving but some other thing must be persistent and the gmail notifications, the bank notifications and many other push notifications don't arrive. I gave all permission but there is not thing to do for me. I think this is impossible and perhaps i am wrong something. can anyone tell me step by step what permissions have i to do for be sure that all permissions are given?
when i unlock from standby and wake the screen the notifications appear all at once!!
i read many problems like this but i didn't find a solution.
can anyone help?
thanks
myabc said:
Good morning. Please, i deactivate all possible energy saving but some other thing must be persistent and the gmail notifications, the bank notifications and many other push notifications don't arrive. I gave all permission but there is not thing to do for me. I think this is impossible and perhaps i am wrong something. can anyone tell me step by step what permissions have i to do for be sure that all permissions are given?
when i unlock from standby and wake the screen the notifications appear all at once!!
i read many problems like this but i didn't find a solution.
can anyone help?
thanks
Click to expand...
Click to collapse
Same. No e-mail, Snapchat, Twitter etc notifications.
But on the other hand, messenger and instagram ones work just fine.
OneUI 1.1, Android 9, September update, Exynos. Xposed, Magisk
Could be the sleeping apps function turned on. If so the phone shuts apps down when they haven't been used in a while.
Data saver can also stop apps using data in the background even if they're still running.
I have both turned off and standby power drain is still minimal. WhatsApp is probably the worst consumer next to Gmail. Need both.
this problem is present in many and many samsung galaxy devices and i wonder why yet didn't solve it.... all the sleeping functions are deactivated and so for data saver and battery saver.... nothing to do, but random, not always
Is it just me or this phone (or at least the CN RMX2071 roms) are super aggressive in closing apps? I know it's a general theme with "custom" (non aosp) based ROMs and most vendor UI takes, but it feels really really broken in these phones.
I have to keep the phone in "high performance" mode and even then i have to re-run some apps every other day (Nova launcher's google companion app) and even re-add widgets (Google Calendar) for them to continue to function, presumably because the power management system keeps shutting them down.
I have every single app to OFF in the App Freeze screen, every app is allowed to run in background (not the smart option, plain always-let-this-run option) and allowed to launch other apps (otherwise more things are broken) and it still feels like things are quirky due to how aggressive the power management is.
Am i missing something? are there more options that i missed? is it better in the EU/IN ROMs?
The eu rom fixes this problem
So a trade off of functionality vs latest security patches etc. Might be worth a try of switching over and at least trying it for a short little bit to determine.
Does anyone know if there's a differnce in behavior for Android Auto between CN and EU ROMs? (though i imagine its also related to power management at the least)
[DELETED]
I am on EU ROM here in the UK (A.28) and ever since I got this phone. It loves to close apps in the background. Facebook used 1400mah when it was just running in the background. Disabled it running in background, notifications work but now it only uses 234mah roughly. There system is messed up. Other apps that I like to use in the background include Google Clock and Skip Track Settings.
These I have a Tasker to launch both apps, with a little pause between launch. I have "Exclude from recent apps" enabled and then after they've launched. I get it to go home automatically. Then with my usage, I have this task running on boot, 5am (whilst I'm asleep) and on secondary app open. I don't notice it, other than when it boots and you just gotta let it run. My clock then works 100% of the time for my alarms and works all day.
One thing to note is, if you click "clear all" in recents, you have to run the task (I do this with the secondary app) to reopen the apps. Thankfyully, with Tasker with auto start-up enabled, it just works and is obviously in realme's don't close in background list.
Thankfully, with Android 11, a promising change to the rules for OEMs is that they can't have list of preferable apps and have to give all app developers an equal chance to running and not being killed. So hopefully, with Android 11, realme will have to stop this annoying practise.
Hope I've explained that well enough and you can use Tasker as a bootleg option
- Josh
Are you saying the power issues are still prevalent in the EU rom as well? If i got you right, You have some kind of a Tasker config to keep launching all the apps that the OS kills on various stages? Because i don't see how that would exclude them from being killed/blocked by the Realme UI service. Again, Unless there IS a difference in the EU rom.
In my case, I gave up on using Google Clock because the alarms never trigger and Android Auto is insanely hard to get running because it keeps killing SOME part of it or one of the apps im trying to use in Auto (Waze, Maps, Youtube Music, etc)
ransagy said:
Are you saying the power issues are still prevalent in the EU rom as well? If i got you right, You have some kind of a Tasker config to keep launching all the apps that the OS kills on various stages? Because i don't see how that would exclude them from being killed/blocked by the Realme UI service. Again, Unless there IS a difference in the EU rom.
In my case, I gave up on using Google Clock because the alarms never trigger and Android Auto is insanely hard to get running because it keeps killing SOME part of it or one of the apps im trying to use in Auto (Waze, Maps, Youtube Music, etc)
Click to expand...
Click to collapse
Yes, apps that realme likes to kill in the background. I have them opened by Tasker whilst I'm sleeping and on boot as realme doesn't close Tasker in the background and then the apps work fine all day. I don't notice it open them other than on boot as otherwise my phone is in standby.
Alarms never triggered for me as realme killed Google Clock, that's why now when it just opens in the background as I sleep it isn't killed.
I don't use my phone intensely and because Tasker opens them as apps, realme can't close them because they're still technically open, even though they don't show in recents. That's why when you clear all apps in recents, you need to then reopen them (that's what my secondary Tasker app does).
As for Android Auto, I haven't had any issue with it. When I use it, my car isn't technical so it uses the screen. I plug my phone in, turn the car engine on and phone begins to charge. Then with a bluetooth to FM adapter, my phone auto connects to bluetooth, and as soon as my phone connects, Android Auto automatically opens (as I have it enabled in Auto's settings) and I get it to play music automatically.
For someone using the actual plug in display to the car, I don't know. Android Auto came pre-installed and all I had to do was install the version for "phone screens".
If you need help with Tasker, my insta is below. Feel free to reply to this or message me on there.
Hope this helps
- Josh
It does help, Thanks!
ransagy said:
Are you saying the power issues are still prevalent in the EU rom as well? If i got you right, You have some kind of a Tasker config to keep launching all the apps that the OS kills on various stages? Because i don't see how that would exclude them from being killed/blocked by the Realme UI service. Again, Unless there IS a difference in the EU rom.
In my case, I gave up on using Google Clock because the alarms never trigger and Android Auto is insanely hard to get running because it keeps killing SOME part of it or one of the apps im trying to use in Auto (Waze, Maps, Youtube Music, etc)
Click to expand...
Click to collapse
Due to a similar issue I had in my corporate Outlook e-mail app, I searched for a solution for the error I got there like "Your organization has removed its data associated with this app" and I found an article from Microsoft proposing a resolution (url not include in this post because it is not allowed, however it is quite easy to find it).
I followed that resolution proposed and it worked for Google Clock app. The alarm finally rang this morning!
Basically, you should go to app list, choose Google Clock (or even any clock app) and configure it as follows:
-in "Power Saver", choose ""Run in Background"
-Set "Allow Notifications" to on
-Set "Auto Startup" to on
-Set "Allow other Apps or Services to Launch" to on
Hope it helps
Yeah, I pretty much did that to every single app on the phone (Besides "Auto Startup" where the OS only allows you 5 outside the whitelisted apps it knows like whatsapp, discord, etc) and i still had interminent issues here and there. Thanks for the heads up either way!
Wpbarreto said:
Due to a similar issue I had in my corporate Outlook e-mail app, I searched for a solution for the error I got there like "Your organization has removed its data associated with this app" and I found an article from Microsoft proposing a resolution (url not include in this post because it is not allowed, however it is quite easy to find it).
I followed that resolution proposed and it worked for Google Clock app. The alarm finally rang this morning!
Basically, you should go to app list, choose Google Clock (or even any clock app) and configure it as follows:
-in "Power Saver", choose ""Run in Background"
-Set "Allow Notifications" to on
-Set "Auto Startup" to on
-Set "Allow other Apps or Services to Launch" to on
Hope it helps
Click to expand...
Click to collapse
ransagy said:
Yeah, I pretty much did that to every single app on the phone (Besides "Auto Startup" where the OS only allows you 5 outside the whitelisted apps it knows like whatsapp, discord, etc) and i still had interminent issues here and there. Thanks for the heads up either way!
Click to expand...
Click to collapse
I also enabled all of these settings (other than last one, can't find it) and had some days it worked, some days it didn't. So for the sake of my actual work, I used my Tasker method and works 100% of the time. Ultimately, realme kinda screwed us over. Ultimately, Android 11 should fix this with it's new guidelines so let's just work around it in the mean time.
Yeah, I'm yet to try your Tasker method, i definitely will though, it's basically the last ditch effort here. I just finished switching to the EU rom as well.
ransagy said:
Yeah, I'm yet to try your Tasker method, i definitely will though, it's basically the last ditch effort here. I just finished switching to the EU rom as well.
Click to expand...
Click to collapse
ransagy said:
Yeah, I pretty much did that to every single app on the phone (Besides "Auto Startup" where the OS only allows you 5 outside the whitelisted apps it knows like whatsapp, discord, etc) and i still had interminent issues here and there. Thanks for the heads up either way!
Click to expand...
Click to collapse
On Startup Manager, for me on EU ROM A.30, and since I first got the phone. The limit on Startup Manager was and still is 20 not recommended startup apps. This is, in realme's words, "to ensure the hone will run smoothly", like bollocks. My old phone had 3GB of RAM and has the exact same apps and ran fine (other than only allowing 3 backgrounds apps to run before memory ran out). But with 8GB and SD865, it's just their way of saying, oh look we have this amount of screen on time. Judging by the list on A.30, the Google Clock is now recommended (I don't think it was before). Either way, realme is gonna get shunned with Android 11's new guidelines and it'll be a fair playing field.
Android Authority - Google Fighting Unfair Power Management Article (Just an interesting read):
www. androidauthority. com/ android-11-background-apps-1136794/
- Josh
Yeah, EU rom (A.20 as its the only one compatible with the chinese model right now) seems to have saner behavior, 20 startup apps instead of 5 and i don't think it has that "allow others to launch" option at all, so not blocking it even? We'll know soon. App Freeze doesn't seem to be automatically enabling on apps, either, also good.
Google Clock worked for me this morning (i duplicated the "system" clock alarms, just a couple mins later to be sure something triggers)
I'll check Android Auto today as well.
I AM always on High Performance mode though.
The thing is about Android 11's changes, that they seem to be worded a little on the easy side in the Google language - makes it seem to me that Google is just asking the vendors to be a little clearer on what they do when informing the users, not that they absolutely can't kill background apps. Here's hoping though.
ransagy said:
Yeah, EU rom (A.20 as its the only one compatible with the chinese model right now) seems to have saner behavior, 20 startup apps instead of 5 and i don't think it has that "allow others to launch" option at all, so not blocking it even? We'll know soon. App Freeze doesn't seem to be automatically enabling on apps, either, also good.
Google Clock worked for me this morning (i duplicated the "system" clock alarms, just a couple mins later to be sure something triggers)
I'll check Android Auto today as well.
I AM always on High Performance mode though.
The thing is about Android 11's changes, that they seem to be worded a little on the easy side in the Google language - makes it seem to me that Google is just asking the vendors to be a little clearer on what they do when informing the users, not that they absolutely can't kill background apps. Here's hoping though.
Click to expand...
Click to collapse
I keep my settings to standard and never do high performance stuff. I also use 60hz as although I love 90hz, I also love battery life and it isn't enough for me to justify the battery usage.
Yeah, I dropped down to normal and had no issues so far, without tasker of anything, just the EU A.20 ROM.
I am on 90Hz all the time though - As someone who is used to 144Hz monitors and gaming, i can sorely tell the difference between 60 and 90 and to me the battery life difference is somewhat negligible.
I haven't tried Android Auto, but we'll see soon enough. Android 11 also brings wireless Auto to everyone, so that might help there as well.
When I use facial recognition to unlock and app, after my face is recognized, before I can go into the app, I get a screen that is showing a message: "Verified. Tap confirm to continue". I am trying to get rid of that message and avoid the unnecessary extra step to press the confirm button before I can access the app. I am told by an app manufactured that it is a setting on my Samsung S22 Ultra with Android 12. But I am coming from an old Pixel phone and cannot find this setting on my new 22Ultra. Can someone direct me to the setting to turn off that extra step after facial recognition works? Thanks!
Sounds like you've installed some 3rd party app that does this. The default S22 behaviour doesn't show this message.
I can see you asked on other fourms, and they suggested things I was going to say. But it seems like some third party app is either doing this, or enforcing it.
the_scotsman said:
Sounds like you've installed some 3rd party app that does this. The default S22 behaviour doesn't show this message.
I can see you asked on other fourms, and they suggested things I was going to say. But it seems like some third party app is either doing this, or enforcing it.
Click to expand...
Click to collapse
Yes I posted on another forum but no solution there yet, just a few good suggestions that don't work. I don't have any other apps that enforce this behavior though. And I pressed support at RoboForm pretty hard about it and they insist it is not something in their app even though RoboForm is an app that it happens in. I am thinking it is when certain 3rd party apps are opened using face recognition, the Android system does not acknowledge those apps for some reason and pops up the message to do a 2nd confirmation before it will allow the apps to open. Thanks for the reply.
Have you tried unistalling Roboform to test if that fixes it?
I have found a few other apps that call up the exact same message so it is not just Roboform. I did uninstall and reinstall Roboform today for another reason and called up a health record app that does the same thing. It happened in the health app even with Roboform uninstalled.
I think we have determined that it is a system message. An app may call it up or trigger it when using face recognition but it is not generated by the app itself. If we knew what it was called then it would be easier to track it down. within Android or the Samsung settings. if it is even in the settings somewhere.
Yea, it's likely going to be a system message, that is called by certain apps in certain circumstances. But the only way you'll find it is to remove apps a few at a time until it stops appearing.
I get the same message and have looked everywhere for a setting. It doesn't exist. Pretty stupid behavior for sure.
Is there a solution? I have the same thing with Microsoft apps. So stupid..
Try: Settings, Biometrics and Security, Face Recognition, And untick: Stay on lockscreen until swipe.
For me, double tapping the screen or using the power button to wake the phone, triggers the face unlock which then quickly unlocks the phone with no other input.
Is this just one app, or all apps?