Hi, well, that problems are the same I had before the switch to Tizen, buuut... now ATN Manager is no option anymore. Many ppl here and even more in the Gear 2 forums say that the most recent Gear Manger (The one from 3 days ago) should do the trick and pass notifications to the Gear (2/NEO). Well.... No? I am on a Note 1 (GT-N7000) with CM11 FW and have some nice problems. Not only the fact that phone calls are silent for me and the one calling me, nope. Notifications are never sent over to the phone. Yes, I activated the Security setting and yes, I selected app and removed the limitation in the Gear manager Settings. Anyone an idea? Did ANYONE get that really work and if so, how?
ATN Manager has bluetooth hooks for android, not tizen...
Out of nowhere on phone reboot it managed to pass ONE notification. Now it's silent again. Strange thing that...
So I've got a new Samsung Gear Live from the Play Store. I'm attempting to pair the device to a Nexus 5 running stock 4.4.4.
When I turn on the Gear Live I'm prompted with selecting a language. I choose English US. Then i'm taken to the "Install Android Wear on your phone" Screen
At first this screen would show me the text "Gear Live 4AFV" (or something along those lines). However 9/10 (after rebooting or resetting the watch) it will simply show me "Gear Live" no 4 digit name.
Without the 4 digits showing the phone will not detect the bluetooth device to connect. On the off chance that it does show up and the phone is able to detect the watch, the pairing process can either work, or stall leaving both devices sitting at a "wait a moment while pairing" screen that never ends.
Lastly, if everything works and i'm able to pair the watch and phone. it will randomly disconnect and nothing I do will make it reconnect to one another.
Other things to note. Bluetooth has no issues on my phone with any other device.
I've reset the watch numerous times,
I've uninstalled the Android Wear app as well as any other watchfaces or launchers.
I've factory reset the phone.
Suffice it to say i'm almost certain there is a problem with the watch, the question is has anyone else experience this or anything similar with a Reset hasn't fixed the problem and is there possibly a solution to this problem that isn't a replacement.
Google has offered to replace the watch but I want to ensure I"m not missing something here.
thanks for any assistance in advance.
gear live 5.0 lollipop connection issues
jay slasher said:
So I've got a new Samsung Gear Live from the Play Store. I'm attempting to pair the device to a Nexus 5 running stock 4.4.4.
When I turn on the Gear Live I'm prompted with selecting a language. I choose English US. Then i'm taken to the "Install Android Wear on your phone" Screen
At first this screen would show me the text "Gear Live 4AFV" (or something along those lines). However 9/10 (after rebooting or resetting the watch) it will simply show me "Gear Live" no 4 digit name.
Without the 4 digits showing the phone will not detect the bluetooth device to connect. On the off chance that it does show up and the phone is able to detect the watch, the pairing process can either work, or stall leaving both devices sitting at a "wait a moment while pairing" screen that never ends.
Lastly, if everything works and i'm able to pair the watch and phone. it will randomly disconnect and nothing I do will make it reconnect to one another.
Other things to note. Bluetooth has no issues on my phone with any other device.
I've reset the watch numerous times,
I've uninstalled the Android Wear app as well as any other watchfaces or launchers.
I've factory reset the phone.
Suffice it to say i'm almost certain there is a problem with the watch, the question is has anyone else experience this or anything similar with a Reset hasn't fixed the problem and is there possibly a solution to this problem that isn't a replacement.
Google has offered to replace the watch but I want to ensure I"m not missing something here.
thanks for any assistance in advance.
Click to expand...
Click to collapse
I have the same connection issue but not until I updated it to Android version 5.0 that I started to get connection issues and the gear live was constantly doing a sync loop and it would not stay connected or send SMS messages.
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've noticed something odd the last few days.
I tend to use Smart Lock to have my phone unlocked while I'm at home and that tend to work decently. Sometimes it doesn't unlock if the phone can't get a good enough locations but overall it's been doing it's job.
These last few days I've noticed something odd however.
The phone doesn't lock. At all. Wherever I am. Kind of annoying.
Sure, there are other ways to solve this, but still. It's a built in function and it'd be nice if it was working as intended.
Running stock 7.1.1, feb's OTA without root so I'm not quite sure what would be the culprit behind this. I'm running beta versions of Google Maps though so that could be it. Maybe something broke in the latest update.
Has anyone else noticed this behavior?
I've seen the same thing recently. My setup sounds similar - stock 7.1.1 from February, not rooted, locked bootloader. I have Smart Lock set to stay unlocked at home but locked everywhere else. I'm at work right now where it should be locked but it's opening on a swipe up without prompting for my pin.
I suspect that this has something to do with a new version of Google Play Services or something getting pushed in the background.
I rebooted my phone and the issue went away. Now prompted for my pin every time I swipe up on the lockscreen.
Yep -both my wife's Pixel and mine fail to use trusted places and devices correctly (we don't use the other smart locks). Started after the Play Services 10.2.98 update on the 10th Feb.
Both trusts seem to only check on phone start, e.g. if restarting at a trusted place the phone remains unlocked when you leave that location.
I've sent feedback and reported it to Pixel support who seemed completely uninterested.
Cheers guys. It's not just me then.
I have the same problem. Trusted places is not recognizing the location. I'm on stock 7 with October security patch. Trusted device though works, Bluetooth in my Jeep.
Sent from my Nexus 6 using XDA Free mobile app
I have an update.
Here is the short version. Trusted places is working again. On Friday I received my first OTA security update. I'm now on NBD92D. After installing the patch there was no change until Sunday when there was a pop up explaining how trusted places functions. Since then it's functioning correctly.
Sent from my Nexus 6 using XDA Free mobile app
I'm on N6F26U and I just noticed this today. It's supposed to stay unlocked at home and when connected to the BT transmitter in the vehicle, but it was unlocked at the DMV today. Definitely not trusted.
Same problem here... Smart unlock bluetooth will not list any devices, at all. Period. Can't peer, can't use. Latest version. Thanks Google!
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