Hello everyone.
I've been using my s21 ultra for more than a month, and the Smart Lock feature hasn't really been working, whether it is trusted places, trusted devices etc..
I especially need it to keep the phone unlocked via Bluetooth trusted device when running android auto in my car (Skoda superb 2017).
To make things worse, since the latest may firmare update, not only the BT connections doesn't keep it unlocked, but each time I unlock the screen manually, android auto disconnects, which is driving me crazy.
Any idea why this is happening? Is there a high level of security in the Samsung galaxy devices I should unlock?
Thanks for any tip.
Any other settings you have ON?
Smart Lock works great with my FIt2 watch.
maybe you should turn off for android auto in settings- apps- special access- optimize battery usage or check keep open in task manager. I had a similar problem with mi band and after enabling both options it works normally
Related
Is there a way to enable NFC when screen is off ?
Xposed had some modules that did this but could not find another solution
aalupatti said:
Is there a way to enable NFC when screen is off ?
Xposed had some modules that did this but could not find another solution
Click to expand...
Click to collapse
+1
A dev should be able to whip something up sooner or later.
No.
aalupatti said:
Is there a way to enable NFC when screen is off ?
Xposed had some modules that did this but could not find another solution
Click to expand...
Click to collapse
Unfortunately:cyclops:, they consider that a security issue. So unless you use a hack, you are SOOL.
I suppose it is a bit of a risk but the range of NFC is so limited. Too small to penetrate one's pocket or read from a distance. The only thing I used it for was in the car to toggle WiFi and Bluetooth which kicked off a chain reaction to start/stop Pandora streaming. Now I have to wakeup the phone first to scan NFC and connect BT. Not that big an inconvenience but I did like the option.
Sent from my Nexus 6 using Tapatalk
I guess its only a matter of time before a Dev figures this out.
Sent from my Nexus 6 using Tapatalk
Or someone fixes xposed for art.
Sent from my Nexus 6 using Tapatalk
vvveith said:
Unfortunately:cyclops:, they consider that a security issue. So unless you use a hack, you are SOOL.
Click to expand...
Click to collapse
It's no more a security risk than being able to enable "Ok Google" when the screen is locked. Not being able to to use NFC when the screen is locked has always annoyed me and was glad Xposed allowed me to do it with KitKat, alas no more. Even my work Blackberry, any current BB10 model and supposedly the most secure of the OSes, allows me to enable NFC when not locked.
Lost in translation?
Taomyn said:
It's no more a security risk than being able to enable "Ok Google" when the screen is locked. Not being able to to use NFC when the screen is unlocked has always annoyed me and was glad Xposed allowed me to do it with KitKat, alas no more. Even my work Blackberry, any current BB10 model and supposedly the most secure of the OSes, allows me to enable NFC when not locked.
Click to expand...
Click to collapse
We are not talking about being able to enable NFC when the screen is not locked. We are talking about having NFC enabled, and the device is sleeping with screen off, not being able to have NFC detect tags or what not without first turning screen on then also unlocking the device. I think you know this but just must of typed it wrong. If not, NFC works great with screen on once past the lock screen. I never disable NFC, I use it the same as the previous post. Getting in car, turns on bluetooth and then launches Pandora and GPS.
With the new Android Auto app and a supporting head unit, all you have to do when you get in your car is plug your phone into a USB port and everything else is automatic. Yeah, one great thing about Nexus 6 and mobile hands free tech.
vvveith said:
We are not talking about being able to enable NFC when the screen is not locked. We are talking about having NFC enabled, and the device is sleeping with screen off, not being able to have NFC detect tags or what not without first turning screen on then also unlocking the device. I think you know this but just must of typed it wrong. If not, NFC works great with screen on once past the lock screen. I never disable NFC, I use it the same as the previous post. Getting in car, turns on bluetooth and then launches Pandora and GPS.
Click to expand...
Click to collapse
You're correct, it's a miss-type and I wrote "unlocked" instead of "locked" - corrected.
I too also always keep NFC enabled, but having to unlock the phone is a real nuisance, thankfully as I also keep Bluetooth on now I can set my in-car to be a trusted device that disables the lock, so once the the connection is made I know I can just tap the phone without worrying. But now I don't even do that as I get Tasker to detect the connection and do it for me
I'm bumping the hell outa this thread. Just bought 20 of my first NFC tags to use various places just to find out NFC is disabled when the screen is off!? Mega-fail.
Anyone find any way to do this or is there a ROM that supports this yet that anyone knows of?
HixVAC said:
I'm bumping the hell outa this thread. Just bought 20 of my first NFC tags to use various places just to find out NFC is disabled when the screen is off!? Mega-fail.
Anyone find any way to do this or is there a ROM that supports this yet that anyone knows of?
Click to expand...
Click to collapse
i just wake up the device with s2w and then use NFC for various actions including unlocking the screen ( i use a pw due to exchange enforcement )
+1
Anyone have any luck getting this working?
I've tried the Xposed module and can't seem to get screen off detection working.
I'm on 5.1.1 (LMY48I)...
Im in the same boat as Jazic... any updates here?
no way?
You would think this functionality would be natively inherent...
This should be at least a quasi-option.
Like you should be able to enable NFC while screen is asleep to a white-listed tag, and be able to set it to wake up screen or not, and be able to unlock phone or not.
So long as a white-list is required it's not a security risk.
It would also be cool to be able to set up app specific UI macros to initiate from NFC.
Hi all, I updated to android-M (completely wipe then installed stock rom). Since then, all the ways of smartlock do not work at all. I checked location access all the apps have it, including system apps (in app permissions). Please help. Has anyone sucesfully gotten Smartlock to work with android-M?
Worked fine for me on stock m and pure nexus
Works fine for me with my BT headset and Android Wear Watch. I've never tried it with a location.
Works with my smartwatch, my location , and my bluetooth stereo adapter thing for my house.
No problems here using MM Pure Nexus using my Android Wear for smart unlock.
Smart Unlock works fine for me with Bluetooth devices...but the location version does seem broken. I even have two location "circles" for my home, to cover a greater area, and I keep having to unlock it manually. This was not an issue for me on 5.1.1.
Location smart lock does not work well for me at all. 5.1.1 it worked great. Bluetooth smart lock is on point.
Location smart lock has been working fine for me the past couple weeks on 6.0. I did run into an issue initially where it seemed like it was stuck thinking I was always at a location to stay unlocked. That was right after I flashed and a reboot solved it.
Location is also broken for me, only works if I manually open Maps and let it settle my location for a bit, then the device stays unlocked for a couple of minutes only. Changing location accuracy has no effect on it.
I'm surprised more people aren't complaining about this...do most people not use location Smart Unlock?
Mine was working flawlessly on 5.1.1 after I upgraded to 6.0 was hit and miss bit I durty flashed the update-after performing factory reset it works fine again
Do you have an exchange account installed? If yes, switch to 'Nine' and it uses app-level encryption rather than device-level. That's the only time it didn't work for me.
Running stock latest image. No tweaks/root.
Sent from my Nexus 6 using Tapatalk
Location unlock is a bit messy for me as well. I thought only I had it.
Location unlock occasionally doesn't work for me (first thing in the morning, usually, or if the phone has been locked/screen off for an extended period of time), but it works most of the time; and the BT unlock works 100% of the time in my car (stupid Toyota not having Android music controls to browse albums...)
liquidzoo said:
Location unlock occasionally doesn't work for me (first thing in the morning, usually, or if the phone has been locked/screen off for an extended period of time), but it works most of the time; and the BT unlock works 100% of the time in my car (stupid Toyota not having Android music controls to browse albums...)
Click to expand...
Click to collapse
Even when Smart Unlock (Location) is working, it will still lock after an extended period of time untouched. It's just a built in safety feature.
Ok so consensus seems to be that location at least IS broken for a lot of people...I'm not sure why though, at least it's not just me.
Same here
Running Google nexus 5 and stock marshmallow, unrooted. Have had same problem since upgrade to marshmallow. Location worked beautifully on lollipop. Bluetooth still fine. Basically sometimes I'm lucky and it unlocks with smart lock, but mostly it's a manual unlock. Noticed that it does sometimes eventually unlock smartly when one waits a while on lock screen and screen on. Keep tapping it to keep active. Very frustrating, adding a feature in past which you get used to and then breaks in future.
It would seem that if a trusted location has an address, it does not work so well, if at all.
Moving the trusted location pin around so that the trusted location uses gps coordinates instead of an address seems to work more consistently. No recent problems with smart lock trusted locations.
The location smart lock never worked for me even in lollipop. The only way I got it to work is by dropping something like 20-30 pins to blanket my county to ever get it to say it unlocked for location. And in google's location history thing it looks all good with points dropped frequently at my house.
Me too, my cellphone don't unlock in my house.
He work well on 5.0.2, now I'm in 6.0 and don't work. I go to do downgrade
I would like to test the new AA split screen functionality on my aftermarket AA headunit, with RRS 7 inch screen. I do have the latest AA installed, an unrooted S10+, with wireless connection; everything working just fine -but I cannot find a way to force AA into the split screen mode.
Is there a way to do this (force split screen mode in this setup), WITHOUT rooting my phone (company mail account gives troubles)?
Installation of extra apps, if needed, is no problem at all.
Only way I've been able to force it is by using AAGateway. HUR lets you adjust DPI settings which will force the dual screen mode youre talking about. I went to Walmart and bought a cheap phone (seriously like, 30 bucks) deleted everything off it that wouldn't break it (though ADB) and installed AAGateway. Its got a dpi switch that will let you force widescreen, and will also add wireless AA to your car. Some phones work with AAGateway, (your s10 will be the master) and some dont. I can 100% confirm that the $29 simple mobile LG Journey 2 works, and can 100% tell you that the $49 Simple Mobile Moto E does not. Its not that it cant run the app, but the way its firmware is set, the app cannot toggle the phones hotspot, which is necessary for the whole thing to be automated. The Journey is cheaper and works right out of the box.
I have two OP's now, an 8T and 10 Pro, both on Android 12. While the 10 Pro came with 12, the 8T was just recently upgraded.
Neither of them will start Android Auto without me first unlocking the phone. This problem only started on the 8T after the 12 upgrade and then the minor update that followed.
I noticed when I unlock my phones the popup to specify what type of USB connection pops up, (charge only, file transfer, etc) - so wondering if this is part of the problem? I tried setting the default to file transfer which is the option for Android Auto, but I still have to unlock the phone every single time I connect to my car.
Did something change between 11 and 12 that would make this happen? Is this a bug?
Does anyone else have this issue, or a resolution idea?
TYIA
Try disabling the screensaver on your phone. I had similar issues on my OnePlus 7Pro, though not on Android 12. After I disabled the screensaver, it connected fine.
gocoogs said:
Try disabling the screensaver on your phone. I had similar issues on my OnePlus 7Pro, though not on Android 12. After I disabled the screensaver, it connected fine.
Click to expand...
Click to collapse
Thanks but I'm not sure what you mean by screensaver? Oxygen OS, at least, doesn't have anything like that in settings. We have a "lock screen" but I need security on my phone so I can't disable that.
I did find a "trusted devices" section where your phone will remain unlocked when it detects things like a location or connected device. I added my car to this, but it still doesn't work. "Trusted Devices" still requires you to unlock phone once before it works properly once connected, just like my Android Auto is doing
I went into developer options and set the default USB configuration to charging/Android Auto. It still shows when you plug it in but my phone still works with the screen off. Also, check the settings in AA as there is one which you have to toggle for starting Android Auto when the phone is locked.
Hi guys, I recently switched from a samsung s8 to a Pixel 7 and I wanted to be able to carry some "automations" with me with an NFC Tag.
The automatism is simple: I return home -> the wifi is activated and the ringtone becomes silent. I leave the house -> the wifi is deactivated and the ringtone returns to normal.
With the S8 I've never had any problems.. with the Pixel, when I get home, the ringtone goes silent, but Do Not Disturb is also activated. And there is no way to separate Quiet from Do Not Disturb! Both activate.
I tried with two different programs to modify the nfc tags: a very old version of "Trigger" and the most recent "NFC Tools". But both give the same result: if you activate Silent, you also activate Do Not Disturb! Obviously if I change the ringing mode by hand this doesn't happen.
Advice?! Has anyone encountered this problem?
DerekZool said:
Hi guys, I recently switched from a samsung s8 to a Pixel 7 and I wanted to be able to carry some "automations" with me with an NFC Tag.
The automatism is simple: I return home -> the wifi is activated and the ringtone becomes silent. I leave the house -> the wifi is deactivated and the ringtone returns to normal.
With the S8 I've never had any problems.. with the Pixel, when I get home, the ringtone goes silent, but Do Not Disturb is also activated. And there is no way to separate Quiet from Do Not Disturb! Both activate.
I tried with two different programs to modify the nfc tags: a very old version of "Trigger" and the most recent "NFC Tools". But both give the same result: if you activate Silent, you also activate Do Not Disturb! Obviously if I change the ringing mode by hand this doesn't happen.
Advice?! Has anyone encountered this problem?
Click to expand...
Click to collapse
Before "Trigger" and "NFC Tools", what app were you using?
If anything, I suggest you use -- if you were not using originally anyway -- MacroDroid. It seems to be capable of achieving what your goal is, although I wasn't able to get the NFC tool to set up myself (but that might just be my phone). Although I'm unsure if you really need to use NFC protocol to achieve this versus using geolocation/GPS; you could probably achieve the same thing with a gps trigger...And i'm sure there are other clever ways you can achieve the same goal using the very diverse program.
Worse comes to worst, you could possibly use Tasker -- although that app hasn't really been in active development in a while, I've seen around the forum that people still use it so at the very least it still functioning...
I used to use Trigger... but once it was set up I never used it again (except in the background). But that was 4 years ago.
I think I will try to use MacroDroid. I already use it to enable/disable rotation only on some programs.
Any advice on any modules?