I tried to enable Smart Lock and have run into a couple issues which no amount of searching gave way to results. I'm on a stock unrooted device.
Is there a way to make this feature work based on location? Seems to not work in locations where I set it to. I tried uninstalling and reinstalling google play services to no avail. Rebooting does nothing to fix.
Sometimes when I try to view the Smart Lock settings, after entering the pin/pattern nothing appears in the menu at all. Very buggy. Does this feature just plain suck or something? I'd rather not use face unlock, but this might force me to.
SOCOM-HERO said:
I tried to enable Smart Lock and have run into a couple issues which no amount of searching gave way to results. I'm on a stock unrooted device.
Is there a way to make this feature work based on location? Seems to not work in locations where I set it to. I tried uninstalling and reinstalling google play services to no avail. Rebooting does nothing to fix.
Sometimes when I try to view the Smart Lock settings, after entering the pin/pattern nothing appears in the menu at all. Very buggy. Does this feature just plain suck or something? I'd rather not use face unlock, but this might force me to.
Click to expand...
Click to collapse
I have issues like this. Supposedly, smart Lock not working by location is a bug from Google not op. It is very hit or miss
thejase said:
I have issues like this. Supposedly, smart Lock not working by location is a bug from Google not op. It is very hit or miss
Click to expand...
Click to collapse
I wonder if this is an Oreo issue and if it will be fixed in P. Very annoying. I may just drop security all together. I didn't have it on my last phone for over 3 years. I like the idea of it, but not being able to unlock the phone while driving and at "trusted" places is pretty useless.
SOCOM-HERO said:
I wonder if this is an Oreo issue and if it will be fixed in P. Very annoying. I may just drop security all together. I didn't have it on my last phone for over 3 years. I like the idea of it, but not being able to unlock the phone while driving and at "trusted" places is pretty useless.
Click to expand...
Click to collapse
Agreed
And the fingerprint unlock not fast enough for you. I do it in one motion. Pick up phone and unlock just like that
nujackk said:
And the fingerprint unlock not fast enough for you. I do it in one motion. Pick up phone and unlock just like that
Click to expand...
Click to collapse
It has nothing to do with speed and everything to do with convenience. Let's not forget that GOOGLE is the one who added the feature. Oreo has been out, in general, for a while. It should just plain work. If I'm at home, why should there be a lock on my device? When I'm out however, it just makes sense to be locked down. Adding a feature that actually doesn't work or works some of the time, is something you'd think they'd have caught during Oreo testing at Google; particularly, as it's an issue with Android, not manufacturers. Even my wife's Galaxy S9+ has this issue.
@thejase
I get that but I don't use it as I'm the opposite phone should be locked when not in my hand never know what will happen,who may come over to visit I have lots of nieces and nephews. One who grabs any phone he can.
But I meant it to be fast enough that it's as if it's not locked.
If you want to stick with
Smart lock have you tried use the voice feature it may work.
Also look into Tasker I seem to remember someone using it to unlock the device based on location. I use it to turn on and off my Wi-Fi based on location. Auto start my music when in my truck.
thejase said:
It has nothing to do with speed and everything to do with convenience. Let's not forget that GOOGLE is the one who added the feature. Oreo has been out, in general, for a while. It should just plain work. If I'm at home, why should there be a lock on my device? When I'm out however, it just makes sense to be locked down. Adding a feature that actually doesn't work or works some of the time, is something you'd think they'd have caught during Oreo testing at Google; particularly, as it's an issue with Android, not manufacturers. Even my wife's Galaxy S9+ has this issue.
Click to expand...
Click to collapse
Seems to be working better today. Disabled the "smart lock" in trust agents setting under fingerprint and security, then booted to the stock recovery and wiped the cache only. (I'm not rooted yet, but TWRP would work for this as well). Seems to have led to a fix, but it could be temporary. As for usefulness of smart lock, I am not worried about others in my own home taking my device and combing through it for all I care. If you have kids or are concerned about content on your phone being messed with, just don't use the feature. For a lot of people, it is a useful feature to have.
This issue has returned and requires a cache wipe almost every day. Beyond annoyed. I am considering deleting my fingerprints or any security. Pretty stupid feature that makes the phone require a password every single time I want to use it, when this feature could have alleviated that in so many places where I know my phone is safe (home, work, car).
Oneplus 6 - Phone unlocks with smart lock off on Android P
I don't use smart lock option in my phone but after upgrading to Android P, even when the smart lock option is off, my phone screen opens when picked immediately as it is supposed to show the screen is locked. Any suggestions please
Related
Hi, I searched the forum but had no luck:
Completely new Nexus 5, White 16GB, and I have this issue:
When i receive and miss a call, as soon as the ringer stops the phone automatically shows the unlocked homescreen and it just stays there, instead of locking itself normally. This is really weird, and happens even if the phone is in my pocket (so it's not sensor-related like whatsapp pop-ups for example). Also not really safe i'd say. If I select another lockscreen method, it behaves normally (showing, for example, unlock pattern for a certain amount of time before turning the monitor off again.)
Anyone experiencing the same issue?
http://www.reddit.com/r/Nexus5/comments/1q04f7/nexus_5_unlocks_itself_after_a_missed_call/
This is the only other reporting I found on the web. Can anyone test this? It's really fast and easy, and I think this could be a pretty serious issue.
My phone (pin locked) doesn't do that. Phone stays locked. Is your phone kept unlocked?
jj14 said:
My phone (pin locked) doesn't do that. Phone stays locked. Is your phone kept unlocked?
Click to expand...
Click to collapse
Yes. I don't really like the pin/passcode unlock (also don't really need it). Classic slide is simple and fast enough, but it's crazy that it stays unlocked after a missed call.
Also, I noticed that it automatically enters the last application that was open the last time you locked it, creating even more concerns (last online on messaging applications, online status in facebook, ecc.)
Just imagine you boss calling you, with no luck, and founding out a second later you're online in Facebook. Just because you were ignoring your phone, while driving for example.
themcfly said:
Yes. I don't really like the pin/passcode unlock (also don't really need it). Classic slide is simple and fast enough, but it's crazy that it stays unlocked after a missed call.
Also, I noticed that it automatically enters the last application that was open the last time you locked it, creating even more concerns (last online on messaging applications, online status in facebook, ecc.)
Just imagine you boss calling you, with no luck, and founding out a second later you're online in Facebook. Just because you were ignoring your phone, while driving for example.
Click to expand...
Click to collapse
I agree - that should not be the expected behavior
nexus5 32gb here, exactly the same behavior.. I had to enable a pin/password unlock method because every missed call would unlock my phone, even in my pocket..
I have the same issue.
Maybe it is because of the app Light Flow Lite ?
mr_smith1 said:
I have the same issue.
Maybe it is because of the app Light Flow Lite ?
Click to expand...
Click to collapse
I thought this as well, but then I tried it on my friends N5 and had the same behavior, without light flow. I think many of us actually discovered this trying notifications in Light Flow (i bought the pro version) but it's not related to that.
kowloon12 said:
nexus5 32gb here, exactly the same behavior.. I had to enable a pin/password unlock method because every missed call would unlock my phone, even in my pocket..
Click to expand...
Click to collapse
Me too, but I hate it because I can't swipe down from the top to quickly see my notification without unlocking the device first.
Let me know if you guys have any advice on this issue, also report it in this thread to keep it bumped and see if anyone is reporting any solution.
themcfly said:
Me too, but I hate it because I can't swipe down from the top to quickly see my notification without unlocking the device first.
Click to expand...
Click to collapse
exactly this, it was so useful to just throw a glance to the notifications to decide if open them or simply clean them away
Yes same here, this looks to be a bug surely?
Sent from my Nexus 5 using xda app-developers app
OK thanks,
I reported the problem on google discussion (I copy/paste our first topic because you explained the problem very well ^^).
the URL:
"https://productforums.google.com/forum/#!category-topic/nexus/nexus-5/KML5nWW9q6o"
mr_smith1 said:
OK thanks,
I reported the problem on google discussion (I copy/paste our first topic because you explained the problem very well ^^).
the URL:
"https://productforums.google.com/forum/#!category-topic/nexus/nexus-5/KML5nWW9q6o"
Click to expand...
Click to collapse
Nice one, I have posted in that discussion as well. Hopefully we will get a response.
Others have the same problem, do you know how to report a problem to google ?
I just tried it on my phone, called from my desk number, missed call. It did open the phone all the way, but the screen turned back off in 5 seconds, per my settings.
My phones is currently stock, have not rooted or unlocked the bootloader yet. Only UI modification apps are Widgetzoid and Dashclock, I wanted to stay stock for a bit.
Sorry, that you are having issues. Unfortunately sometimes the easiest way to figure out what is causing the problems is to do a factory reset, and re-dowload your apps one by one, to see what is causing the problem.
Ok, but a several people have the same issue ...
Anyway, I think I will tri not to miss a call whenever the phone is in my pocket !
Zandeer said:
I just tried it on my phone, called from my desk number, missed call. It did open the phone all the way, but the screen turned back off in 5 seconds, per my settings.
Click to expand...
Click to collapse
I don't like setting the screen timeout so short, many thimes i just place the phone on my desk while messaging and I want the screen to stay on, for at least 2 minutes.
And when I lock my phone to keep it in my pocket, it's supposed to stay locked and ignore any unintended touches as soon as i slide to unlock, which was originally introduced to prevent an unlock by accident. Yes, I could lower my screen timeout to 5 seconds, but that does not solve the problem because still unintended touches can occur in that time frame.
themcfly said:
I don't like setting the screen timeout so short, many thimes i just place the phone on my desk while messaging and I want the screen to stay on, for at least 2 minutes.
And when I lock my phone to keep it in my pocket, it's supposed to stay locked and ignore any unintended touches as soon as i slide to unlock, which was originally introduced to prevent an unlock by accident. Yes, I could lower my screen timeout to 5 seconds, but that does not solve the problem because still unintended touches can occur in that time frame.
Click to expand...
Click to collapse
I wasn't sing o set your screen lock time to what I have it set at, I was just saying that it did re-lock. However, you are right, IMO it should not completely unlock the screen when the phone is ringing.
Though I have never not had a passcode on my phone, so not sure if that is how it always behaves. Was just trying to test and be helpful.
I sent a message to the google team, let's wait and see.
here is a link to see the bug :"http://www.youtube.com/watch?v=SSTq8Xhe6Kc&"
Zandeer said:
I wasn't sing o set your screen lock time to what I have it set at, I was just saying that it did re-lock. However, you are right, IMO it should not completely unlock the screen when the phone is ringing.
Though I have never not had a passcode on my phone, so not sure if that is how it always behaves. Was just trying to test and be helpful.
Click to expand...
Click to collapse
Thanks for testing, I was wondering if this could have been related to root / unlocked bootloader somehow but you have confirmed this is not the case as it happens on a totally stock phone.
good catch there. same issue here.
at least a Google employee has responded to the topic created HERE. Maybe that will expedite then pushing out an update ASAP.
Upgraded my N5 to its Lollipop Factory Image, and setup Smart Lock to work with my Moto 360. I'm noticing that my N5 will still prompt me for a passcode half the time, even though my moto 360 shows it's still connected (I can even PROVE it's connected, by doing an "Ok Google" voice search). I even set up face unlock to give it another unlock method, and that didn't seem to increase the success rate for Smart Unlock. It seems that no matter what, smart unlock doesn't work for me a lot of the time. To be more specific, it seems like it doesn't work if I haven't used the phone in awhile. Once I put my passcode in, smart lock seems to work just fine for awhile, but eventually it will stop working again, forcing me to enter my passcode to jumpstart it again.
Anyone else experiencing this?
Yes, this seems to be what I'm experiencing as well.
Same here... really want this to work. I assumed it might be because I dirty flashed, are you running a clean install?
same here...
Same here with a nexus 9. Tried connecting it to a moto and to my nexus 5. The units ARE connected to the nexus9 but in smartlock they have status "not connected". After setting up it works until the units are out of reach for the first time....after that it is back to pincode
jt3 said:
Upgraded my N5 to its Lollipop Factory Image, and setup Smart Lock to work with my Moto 360. I'm noticing that my N5 will still prompt me for a passcode half the time, even though my moto 360 shows it's still connected (I can even PROVE it's connected, by doing an "Ok Google" voice search). I even set up face unlock to give it another unlock method, and that didn't seem to increase the success rate for Smart Unlock. It seems that no matter what, smart unlock doesn't work for me a lot of the time. To be more specific, it seems like it doesn't work if I haven't used the phone in awhile. Once I put my passcode in, smart lock seems to work just fine for awhile, but eventually it will stop working again, forcing me to enter my passcode to jumpstart it again.
Anyone else experiencing this?
Click to expand...
Click to collapse
got no problem at all since N5 is paired with my LG G watch.
Got problems making NFC tag work. I have a NFC sticker at home, i use it with this app https://play.google.com/store/apps/details?id=com.jwsoft.nfcactionlauncher&hl=en making toggle wifi when i enter home (wifi on) and when i walk out (wifi off). I tried to use the same tag for smart unlock, but it simply doesn't works. Tag writing seems to be ok but still have to enter the pin when i pass my phone over it. Should i use another tag?
Mine works but RARELY
Sent from my Nexus 5 using XDA Premium 4 mobile app
Well, I figured out my issue anyway. It seems it's Gravity Screen. I use it to turn off my screen when I put the phone in my pocket (and turn it back on when I take it out). Because of this, I rarely touch the power button anymore. Apparently, when Gravity Screen locks the device, it REALLY locks it, making it so that Smart Lock can't unlock it, and forcing you to enter a passcode. I've left a note in the dev's thread, asking for a fix, but for now, I had to disable that feature.
Now, Smart Lock is working almost all of the time. I still have the occasional need to enter a passcode (like after rebooting), but for the most part, this fixed my issue.
I guess the tl;dr of all this is to make sure you don't have any apps running that lock or power-off your screen. They may be interfering.
jt3 said:
Well, I figured out my issue anyway. It seems it's Gravity Screen. I use it to turn off my screen when I put the phone in my pocket (and turn it back on when I take it out). Because of this, I rarely touch the power button anymore. Apparently, when Gravity Screen locks the device, it REALLY locks it, making it so that Smart Lock can't unlock it, and forcing you to enter a passcode. I've left a note in the dev's thread, asking for a fix, but for now, I had to disable that feature.
Now, Smart Lock is working almost all of the time. I still have the occasional need to enter a passcode (like after rebooting), but for the most part, this fixed my issue.
I guess the tl;dr of all this is to make sure you don't have any apps running that lock or power-off your screen. They may be interfering.
Click to expand...
Click to collapse
I don't use Gravity Screen, but have it installed. Could that cause the problem? I'm currently on 5.1 Cataclysm on my Nexus 5.
I have added Moto 360 as a trusted device. The moment I add it i'm able to unlock without PIN. However, after a few minutes, although the watch is connected, smart lock doesn't seem to work. I had this issue on stock Android 5.0 (no root or bootloader unlock) also with a Sony bluetooth headphones!
My smart lock "trusted places" is not working. I am assuming it is associated with the recent update to the Google Play Services for the "on body detection."
My Google Play Services has been sucking up my battery usage when location services is on. Other users have been experiencing the same issues. Some fixes suggest turning the smart features off then back and another is reinstalling the Google play services (revert then update again.)
I side loaded my Google Play Services but it didn't fix the problem. I am still looking for a fix so trusted places will work.
Sent from my Nexus 5 using Tapatalk
chrisinsocalif said:
My smart lock "trusted places" is not working. I am assuming it is associated with the recent update to the Google Play Services for the "on body detection."
My Google Play Services has been sucking up my battery usage when location services is on. Other users have been experiencing the same issues. Some fixes suggest turning the smart features off then back and another is reinstalling the Google play services (revert then update again.)
I side loaded my Google Play Services but it didn't fix the problem. I am still looking for a fix so trusted places will work.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Having absolutely the same problem. The "on body detection" feature works perfectly, howeve, the "trusted places" - almost never. I find myself entering my PIN at home every time I want to unlock the device, except for the times I slide it out of my pocket. If Google fixes these problems, Smart Lock would be my favourite feature!
I've pretty much given up on Smart Location Unlock. It's been broken for weeks now. I'm on CM12 and made profiles to disable pin/password/pattern when connected to my home Wi-Fi.
I'm hoping someone else is having this same issue since the MM update.
When I first got the Note 5 on lollipop, I set up a smart lock with my home location so I didn't have to use my fingerprint when I was at home. I also set up the s view case to automatically unlock the phone when opened. On lollipop this worked pretty much flawlessly.
Since the update though, both are somewhat finicky. Sometimes it works just fine while other times it's smart lock that still wants my fingerprint. At other times, smart lock is fine, I only need to swipe to unlock, but the s view case doesn't unlock the screen when opened. I'm hoping it's just an overlooked bug in the first MM software and will be corrected with future updates.
I have factory reset the phone and done everything I can think of to fix it. It's not a big deal as it doesn't hurt functionality at all, it's just a bug I've noticed. Also, I think a good option under the smart lock settings would be "when connected to a certain Wi-Fi access point" but it's not an option.
Has anyone else noticed this and fixed the issue? Thanks
Same issue. Set up paired with my Zenwatch and it seems to be about 50/50 whether I can slide to unlock or have to use fingerprint.
Same thing here. Its def a bug. I have tried clearing out my google settings, location settings, location cache, everything other than a master reset for the most part.
Honestly it never works right since the mm update. Wouldnt even give it a 50/50..
BUT
What i have noticed is if i simply press the home screen twice, one to wake, then again but lightly pressing, it unlocks automatically. The finger print scanner reads the print so quick it gets you straight to the home screen.. shouldnt have to do this. but it works pretty well to unlock quickly. Plus, dont have to slide anymore and get prints/smudge on the screen.
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
computerslayer said:
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
Click to expand...
Click to collapse
Do you have the navbar hidden by any chance
crixley said:
Do you have the navbar hidden by any chance
Click to expand...
Click to collapse
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
computerslayer said:
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
Click to expand...
Click to collapse
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
crixley said:
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
Click to expand...
Click to collapse
We're talking about the back button and the new pill gesture button, right? If so, then no I haven't installed anything to hide those: they are always visible.
Well, after 24 hours, I had the issue resurface. Unfortunately, the logging app I was using (matlog) froze up with the phone and produced a blank text file. While rebooting restored normal function of the phone, I can't produce a log as a result.
It occurs to me that while I am not disabling the navbar, I do use a function of the Cerberus anti-theft app to disable the notification bar while locked. Could this be the source of my issue? If so, is there any way to confirm this?
In the meantime, I've disabled that function and will see if the lock-up occurs again.
I'm curious where you were going with the question about the navbar. Could you tell me more about what you were thinking it might have been?
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
computerslayer said:
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
Click to expand...
Click to collapse
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
crixley said:
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
Click to expand...
Click to collapse
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
computerslayer said:
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
Click to expand...
Click to collapse
I'm glad to hear it's fixed for you!
I try to help as much possible, I remember how good it was to have people help me when I needed it and sometimes I need a hand as well.
Hi all. In this Video the reviewer states that he isn't getting any notifications with the screen off. Also it is a problem for one of our members. Is anyone else having these hassles? Do you get incoming text, email AUDIO notifications without waking the phone?
Hi
I have no issue with notification at all..
Even when screen is off ..
U do have to active notification from each app setting and alow all permissins...
Also keep in maind to keep app running remove battery restriction from app setting also..
All will work normal
Working for me but I did need to grant WhatsApp and Trurcaller lots of permissions.
I even got True Edge installed for a visual way to get notified and that works brilliantly with the device asleep with screen off.
I was a bit surprised at the extra level of permissions needed. It's all gravy now, but I could see why a reviewer or somebody unaware would get caught out
But yes, I am getting notifications with the screen off in sound and visually, without having to wake the phone.
Indeed at first I wasn't getting any notifications but then I discovered you need to go into the app info and give permission for notifications and turn off battery saver.. now it works perfect and only for the apps I want
The video the OP posted is exactly whats happening to me. I have all the settings as described. Battery saver turned off and even when into each apps settings and allowed ALL permissions just to see if it would work. As the video says, notifications come, but you have to wake the device to see them, there is no sound or anything on screen until the device is woke. Exactly as the video describes. I do hope its fixed soon, I am back to using my Note 5 whilst my beautiful 10 Ultra sits in its box.
Burginthorn said:
The video the OP posted is exactly whats happening to me. I have all the settings as described. Battery saver turned off and even when into each apps settings and allowed ALL permissions just to see if it would work. As the video says, notifications come, but you have to wake the device to see them, there is no sound or anything on screen until the device is woke. Exactly as the video describes. I do hope its fixed soon, I am back to using my Note 5 whilst my beautiful 10 Ultra sits in its box.
Click to expand...
Click to collapse
Have you undone your earlier modifications to the phone (copying files from phone to phone etc)?
You have two problems and the one to ignore for now is louder notifications. It's notifications at all.
It isn't something to fix from Xiaomi's view and it is always worth learning the software. I don't like it myself... It can be cloying etc.
But the default behaviour is to opt in to notifications. It's working as intended. That said look where we are, it's just your problems are a special case. No biggie, let's fix this!
You have an outstanding issue clouding this where you are trying to use unexplained files on the device (like seriously what format are they? Does it work in Music or anything? Have you tried removing them?)
Took a while but I get all my notifications now when screen is off, see 2vattached screen shots
Thanks all for answering my question! I think this is my last question before buying from Liaow.com, if the syncing isn't a constant problem. Does anyone have a major syncing problem as explained in this review? Once or twice a day I can deal with. I check the calendar throughout the day like most people. However if I get busy and forget, missing calendar events/alarms wouldn't work for me. I'd be forced to use my work iPhone<shudder> for calendar events lol.
Sathelp said:
Took a while but I get all my notifications now when screen is off, see 2vattached screen shots
Click to expand...
Click to collapse
How did you get the icons to show on the lock screen?
Mine doesn't. Quite annoying.
Also sometimes the lockscreen doesn't show me notifications even tho they are there.. :s
I have no issues with icons displaying while locked. You do need to enable them and ensure they start automatically and power control is turned off for the app. It has been much easier in the EU ROM for some reason.
Solution!
Here is the thing that helped me with the same notification issue! Just google "xiaomi mi 10 ultra notifications" and in the top 5 links you'll probably find an article from: theunpopulartraveller. It explains the settings, and they need to be accessed by pressing and holding the app icon ^ app info.
Don't give up, try and you'll get the sounds from needed apps back. And ye, actually now I find the way Xiaomi did it much more convenient: I just turned on notifications for 2 apps, and all the rest are silent, while previously I had to turn off all the rest of the apps (much more than 2, definitely) not to get disturbed by all the bull****.
EU Rom doesn't have the "importance" option at 30/31
Well after trying to update to 12.1.1 and seeing what a buggy heap of junk it was, I factory reset, installed 12.0.15, and formatted data. But now notifications don't work when the screen is off whatsoever, absolutely no notifications. Beautiful. I'm so sick of the software issues with this phone, I'm definitely never buying another Xiaomi phone at this point.
AerationCheese said:
Well after trying to update to 12.1.1 and seeing what a buggy heap of junk it was, I factory reset, installed 12.0.15, and formatted data. But now notifications don't work when the screen is off whatsoever, absolutely no notifications. Beautiful. I'm so sick of the software issues with this phone, I'm definitely never buying another Xiaomi phone at this point.
Click to expand...
Click to collapse
Disable adaptive notifications from setting. I dont know what google thinking when creating such feature.
it basically interrupt the whole notification process. Using so called Ai to decide, when to give you notifications or when not to. But most of the time it pick wrong decision and delay our notification altogether.
This is android feature since Q thus also causing problem on Pixel phone. On xiaomi seems like it suddenly got worse on Android 11
AerationCheese said:
Well after trying to update to 12.1.1 and seeing what a buggy heap of junk it was, I factory reset, installed 12.0.15, and formatted data. But now notifications don't work when the screen is off whatsoever, absolutely no notifications. Beautiful. I'm so sick of the software issues with this phone, I'm definitely never buying another Xiaomi phone at this point.
Click to expand...
Click to collapse
How did u manage to roll back to 12.0.15?
Get over to the EU ROM version. Lock screen notifications work fine.
Have you checked each notification that it has no battery optimisation set, also, check in notifications that each one has access to the lock screen. Since A11, notifications have been a pain but for some reason they do work much better on the EU ROM.
Sathelp said:
Get over to the EU ROM version. Lock screen notifications work fine.
Have you checked each notification that it has no battery optimisation set, also, check in notifications that each one has access to the lock screen. Since A11, notifications have been a pain but for some reason they do work much better on the EU ROM.
Click to expand...
Click to collapse
There are issues for Gpay and some banking / local safetynet apps for EU ROM which i do not wish to live with.
Somehow the props file in the eu rom causes those issues.
i am probably going to rollback to 12.0.15... now is the excruciating 160 hours wait for unlock.
You obviously don't follow the EU forums. GPay works, safeynet works and my UK bank works. But you also get everything plus more than the Chinese stock and all updates are based on both weekly and stable stock ROMs respectively.
Sathelp said:
You obviously don't follow the EU forums. GPay works, safeynet works and my UK bank works. But you also get everything plus more than the Chinese stock and all updates are based on both weekly and stable stock ROMs respectively.
Click to expand...
Click to collapse
i don't follow it to the tee, but i've seen some reports of some users not able to use gpay out of the stable roms.
that's why.. too much trouble.. i'll see what i can do when the unlock timer is up..