Related
Ever since upgrading to Lollipop 5.1 on my Moto X (2013), I get the message: "vnd.android.nfc://ext/motorola.com:xring", every time that the screen unlocks with the Motorola NFC Skip. Is there a way to prevent the message from showing?
Thanks
Pat
I get that message as well, the Skip doesn't really work consistently for me anymore though. Maybe the first day I set it up it kind of worked, now it doesn't do a damn thing. Anyone on 5.1 with 2013 able to get it to work reliably? I may do a factory reset if so.
If i remember correctly, Motorola posted that skip wont work anymore with 5.1
Called them up to get suggestions.
I uninstalled and reinstalled the Skip app on the play store. Then I re-added the Skip to NFC security settings. Seems to be working reliably now.
ohmimpotence said:
Called them up to get suggestions.
I uninstalled and reinstalled the Skip app on the play store. Then I re-added the Skip to NFC security settings. Seems to be working reliably now.
Click to expand...
Click to collapse
Does it still give the message or is it gone now?
Still gives the message if I do it with the screen on. From the lock screen it doesn't seem to. I haven't tested if it's still working today because I'd have to remove like the 4 trusted locations I have for my home but even with trusted location on, my phone will lock itself after not using it for a certain amount of time and I'm not using on body detection. When it did that this morning, I was not able to unlock it using the Skip.
ohmimpotence said:
Still gives the message if I do it with the screen on. From the lock screen it doesn't seem to. I haven't tested if it's still working today because I'd have to remove like the 4 trusted locations I have for my home but even with trusted location on, my phone will lock itself after not using it for a certain amount of time and I'm not using on body detection. When it did that this morning, I was not able to unlock it using the Skip.
Click to expand...
Click to collapse
I think that it has to do with SmartLock locks up the phone after 4 hours of inactivity.
The weird thing is it doesn't unlock with the Skip if it's locked due to inactivity.
Anyone ever get any satisfaction here? I just got the 5.1 update for me Verizon moto x, it's made my NFC ring practically unbearable. It unlocks the phone fine, but then it continually scans my ring and pops up every time the ring moves out of range and back in range of the NFC reader.
Sent from my XT1060 using XDA Free mobile app
So I got the upgrade but now I am unable to use the voice command Ok Google from watch face as before. I can only get it working by holding power button and even then it seems just laggy.
Anyone else having this issue activating it by voice?
Thanks!
Having that same issue. Not only does not "Ok Google" work, even after enabling it in the watch's settings, even when pressing down the crown, the whole thing is extremely slow. Furthermore, for sending a message, the "Ok" doesn't time out after a couple of seconds in order to send the message automatically. It requires me to tap the screen.
All in all, its looking more like a downgrade for me. The whole system feels sluggish and incoherent from a usability standpoint of view.
Edit: Didn't factory reset the watch after update
I have an another problem. Google Assistant isn't launched in Czechia yet and there isn't Google Now in Android Wear 2. So, I lost any speech control.
I've too had issues with "OK Google" after Android Wear 2.0 install. I did get it sort of working after a device reset and reconnect to my phone. (Samsung Note 5). Its slow!! and now for sending text messages you have to confirm with a tap. All in all the functionality went down....
Anyone know how to revert back to the old rom?
Mr.Caution said:
I've too had issues with "OK Google" after Android Wear 2.0 install. I did get it sort of working after a device reset and reconnect to my phone. (Samsung Note 5). Its slow!! and now for sending text messages you have to confirm with a tap. All in all the functionality went down....
Anyone know how to revert back to the old rom?
Click to expand...
Click to collapse
So another issue is that even after going to the stupid settings where you actually have to enable Ok Google from any screen on your watch, it STILL wont work. I can only get it to work by using the power button which has a huge delay and then only when I am connected on Wifi. For some reason it no longer works when on my normal cellphone connection.
The phone is super laggy, battery dies fast...its a MESS.
Basically my watch is useless now for all the things I need it to do daily
Mine only works if i go and disable Bluetooth and enable WiFi else it complains it can't contact Google. Play store is the same too. Slow lagging assistant is not good especially sending txts with no auto send
Sent from my Moto G (4) using Tapatalk
Same issue here. "OK Google" is the most important feature...
You need to give permissions for the OK Google to work. Didn't notice about it until I read this thread (I think most particularly Phone access)
shaolin95 said:
So I got the upgrade but now I am unable to use the voice command Ok Google from watch face as before. I can only get it working by holding power button and even then it seems just laggy.
Anyone else having this issue activating it by voice?
Thanks!
Click to expand...
Click to collapse
Yes , it is the same on my watch - it is laggy ! I am looking for a way to downgrade back to old android wear.
venzislav said:
Yes , it is the same on my watch - it is laggy ! I am looking for a way to downgrade back to old android wear.
Click to expand...
Click to collapse
I just got the ROM from this post and used the flash steps he listed and it worked fine.
https://forum.xda-developers.com/showpost.php?p=71823043&postcount=3
shaolin95 said:
I just got the ROM from this post and used the flash steps he listed and it worked fine.
https://forum.xda-developers.com/showpost.php?p=71823043&postcount=3
Click to expand...
Click to collapse
Is it possible after downgrade to stop watch from upgrading again to 2.0 ?
venzislav said:
Is it possible after downgrade to stop watch from upgrading again to 2.0 ?
Click to expand...
Click to collapse
I want to find out as its annoying to see the upgrade message over and over
shaolin95 said:
I want to find out as its annoying to see the upgrade message over and over
Click to expand...
Click to collapse
Pfff this 2.0 is a big s**t !!!
Doesn't lag on mine using the 2 core or 4 core kernel
almostthere said:
Doesn't lag on mine using the 2 core or 4 core kernel
Click to expand...
Click to collapse
Does OK Google work with voice commands and when not connected to Wifi???
shaolin95 said:
Does OK Google work with voice commands and when not connected to Wifi???
Click to expand...
Click to collapse
Yup mine works perfectly without wifi (have been testing it outdoors since 2 days ago). Fix is to go to apps, system apps, google, permissions, enable permission to phone (maybe others too since IDGAF and ticked all)
almostthere said:
Yup mine works perfectly without wifi (have been testing it outdoors since 2 days ago). Fix is to go to apps, system apps, google, permissions, enable permission to phone (maybe others too since IDGAF and ticked all)
Click to expand...
Click to collapse
Would you look at that! It works but WTH is google making it so complicated now for users? Most people dont hang around XDA to know these things. Like for instance apps now need to be downloaded on the phone as its not autmotically done, etc.
Really weird approach.
Thanks for the tip!
After a factory reset and being extremely patient, I was able to get Ok google to work. You have to go to the store on the app and update all of the apps and then enable, OK google in the settings. Problem is the response time is horrible. I'm going to stick with 2.0 and hope that they roll out updates to make it faster.
Isham.padron said:
After a factory reset and being extremely patient, I was able to get Ok google to work. You have to go to the store on the app and update all of the apps and then enable, OK google in the settings. Problem is the response time is horrible. I'm going to stick with 2.0 and hope that they roll out updates to make it faster.
Click to expand...
Click to collapse
Responses time is horrible on the initial due to it running on single core at lower clock speeds and on conservative core governor.
Therefore you'll have to give it sometime for it to settle down or if you can't deal with it, you'll have to unlock the bootloader and flash in the dual or quad core enabled kernel file
Running in quad core kernel, battery life seems decent and response real snappy
Well that's just stupid because it worked fine on the previous android wear build. This is dumb on LG's part.
I've got google assistant set up with trusted voice etc so that I can issue commands to my locked Note8 while driving etc, one thing I've noticed that I'm not a fan of is if I issue a simple command like 'what time is it' for example, google completes the request without ever leaving the AOD but after the request is complete my phone is still off but it stays unlocked. Is there a way to make my phone automatically re-lock after a voice command with Google assistant?
dicko101 said:
I've got google assistant set up with trusted voice etc so that I can issue commands to my locked Note8 while driving etc, one thing I've noticed that I'm not a fan of is if I issue a simple command like 'what time is it' for example, google completes the request without ever leaving the AOD but after the request is complete my phone is still off but it stays unlocked. Is there a way to make my phone automatically re-lock after a voice command with Google assistant?
Click to expand...
Click to collapse
Say "Hi Bixby, lock screen" when you're done.
harveydent said:
Say "Hi Bixby, lock screen" when you're done.
Click to expand...
Click to collapse
Yeah I know, it would just be better if it relocked itself.
dicko101 said:
Yeah I know, it would just be better if it relocked itself.
Click to expand...
Click to collapse
Why not just set your lock to 30 seconds or whatever. Assistant commands unlock your phone.
Sent from my SM-N950W using Tapatalk
milan187 said:
Why not just set your lock to 30 seconds or whatever. Assistant commands unlock your phone.
Sent from my SM-N950W using Tapatalk
Click to expand...
Click to collapse
My lock does time out, it's just annoying, it seems logical that your device should just re-lock after a voice command, a lot of voice commands don't need to unlock, like the example I gave, they don't even leave the AOD, it just seems like something that should have been obvious and would have been easy to implement.
dicko101 said:
My lock does time out, it's just annoying, it seems logical that your device should just re-lock after a voice command, a lot of voice commands don't need to unlock, like the example I gave, they don't even leave the AOD, it just seems like something that should have been obvious and would have been easy to implement.
Click to expand...
Click to collapse
Most commands require access to something therefore can't work in a locked encrypted system. Can google work around it? Probably. This is the first time I've seen a complaint about this.
Sent from my SM-N950W using Tapatalk
Hi guys,
Strange one this is, most of my recent apps (except the odd 4 or 5) started auto closing themselves *overnight* after the Pie update, everything is fine during day time.
This is still true after disabling Auto Optimization and Auto Restart, and locking all recent apps.
Needless to say, never had a problem in Android 8.0.
Cheers.
Same with me also
I can only imagine this would be the same for everybody -- or am I missing a magic switch somewhere??
this is normal. you have to turn off sleeping apps, or remove from that list as well as adaptive batery which is new to pie.
The more I read about this pie, the less I want it.
Fixed mine.
Setting->Device Care->Battery-> 3dot menu settings
Turn off Put unused apps to sleep.
Thanks. Will try myself.
Sadly still the same for me...
Opened apps auto closed overnight, note just overnight, day time all is fine.
Sadly still the same for me...
Apps auto closed overnight, daytime is fine.
It's the device optimisation set to run automatically every night? It is on mine
Sent from my SM-T820 using Tapatalk
pizza_pablo said:
The more I read about this pie, the less I want it.
Click to expand...
Click to collapse
Ha trust me it's so childish, and so dull.. Everything is like iphoney kind of feel! Big childish icons! They have simplified it too much! it don’t feel good, it feels way to simplified plus they have removed so much it really sucks!
When you do get the update, let us know if you’re going to stick to it or not! As i went back to Oreo day 2 man Oreo is awesome!
device optimisation is off, so is auto restart.
is this normal behaviour for adaptive battery? in which case, it would be rather stupid design -- I want my apps (especially those locked) to stay on ready to be used anytime!
yzs1002 said:
Sadly still the same for me...
Opened apps auto closed overnight, note just overnight, day time all is fine.
Click to expand...
Click to collapse
See screenshots below,
Mine is set to default 0300, to close/optimize. I set it to off.
willcor said:
See screenshots below,
Mine is set to default 0300, to close/optimize. I set it to off.
Click to expand...
Click to collapse
thanks -- mine had always been off.
N1NJATH3ORY said:
When you do get the update, let us know if you’re going to stick to it or not! As i went back to Oreo day 2 man Oreo is awesome!
Click to expand...
Click to collapse
I don't even want to take the update.
What county and provider are you and how did you downgrade to Oreo?
pizza_pablo said:
I don't even want to take the update.
What county and provider are you and how did you downgrade to Oreo?
Click to expand...
Click to collapse
UK Purchased Note 9 direct from Samsung UK.. i used SAMFIRM.EXE and Odin3_v3.13.1_3B_PatcheD to downgrade to Oreo 8.1.l it's so easy to downgrade walk in the park easy
N1NJATH3ORY said:
UK Purchased Note 9 direct from Samsung UK.. i used SAMFIRM.EXE and Odin3_v3.13.1_3B_PatcheD to downgrade to Oreo 8.1.l it's so easy to downgrade walk in the park easy
Click to expand...
Click to collapse
Hopefully, I'm able to pull that off with this locked down Verizon Note 9, if the need arises.
How do you keep it from wanting to update to Pie?
pizza_pablo said:
Hopefully, I'm able to pull that off with this locked down Verizon Note 9, if the need arises.
How do you keep it from wanting to update to Pie?
Click to expand...
Click to collapse
Just disable auto updates from software updates menu! Also don't check for updates, as you will not be able to get rid of that annoying update notification, unless you factory reset it! It’s that simple!
pizza_pablo said:
Hopefully, I'm able to pull that off with this locked down Verizon Note 9, if the need arises.
How do you keep it from wanting to update to Pie?
Click to expand...
Click to collapse
Disable both Software Update .apks via ADB/AdHell3/Package Disabler app of your choice.
KOLIOSIS said:
Disable both Software Update .apks via ADB/AdHell3/Package Disabler app of your choice.
Click to expand...
Click to collapse
I've read a lot about those, in the other threads, but none seemed reliable any more.
Maybe I'll see if I can hold off the update with AUTO UPDATES turned off in DEFROST OPTIONS and if that doesn't work, downgrade back to Oreo and then adb/Package disable.
Anyone else? P4xl
Only works after I've opened the app
Occasionally when I unlock my phone after being asleep it won't respond to ok Google...
Battery opt is off
Cleared cache with no luck
virtyx said:
Anyone else? P4xl
Only works after I've opened the app
Occasionally when I unlock my phone after being asleep it won't respond to ok Google...
Battery opt is off
Cleared cache with no luck
Click to expand...
Click to collapse
A few reports of the same on Aussie Whirlpool. I wonder if it's language setting bug.
Mine is fine so far, but I'm still stuck on the old Assistant due to having a GSuite account on the P4XL.
xdatastic said:
A few reports of the same on Aussie Whirlpool. I wonder if it's language setting bug.
Mine is fine so far, but I'm still stuck on the old Assistant due to having a GSuite account on the P4XL.
Click to expand...
Click to collapse
Noticed it since moving onto the new assistant
I have the same issue. need to open open first before it works. i think it started to happen on dec build for me
Same here since running custom roms...
Any known fix? Pretty annoying not being able to use a feature properly
Weird, I have the opposite problem. It's overly sensitive for me, it'll just randomly go off in my pocket when I'm having a conversation
Sent from my Pixel 4 XL using Tapatalk