I've got two Moto G 2014 phones, one of them being a new one I got a week ago. I'm in the UK and the 5.0.2 Lollipop OTA update arrived a couple of days ago. Today I updated both phones to Lollipop which worked perfectly.
Motorola Migrate only migrates the data, so I tried to use the new Tap & Go feature to migrate all my apps etc to the new phone, effectively to clone it, but Tap & Go seems to be missing. I don't get the option to pair the new phone with an existing phone at first boot after a factory reset and if I add my Google account, it goes through the normal setup wizard except that the Tap & Go setup part is missing from it.
I've spent a lot of time trying to get this to work this evening including the obligatory googling for it, but come up with nothing, including on XDA, therefore I hope someone here can confirm if Tap and Go has been disabled for this model and perhaps why. If it's actually supposed to work, then I'll be grateful for any troubleshooting tips to help make it work.
Tap & Go only works with NFC (Near Field Communication), for which our devices lack the chip.
And there's me thinking that NFC was a generic name for Bluetooth which works at short distances, lol.
Looking it up on Wikipedia, I can see that Bluetooth costs $5 for the tag (which we have) while NFC is a mere 10c and yet it doesn't have it. Shame, this important new feature could have easily been implemented to work over Wi-Fi and should have been, in my book.
en.wikipedia.org/wiki/Near_field_communication#Comparison_with_Bluetooth
Have you tried migrate?
Yes first thing I did with both phones on KitKat. It copied over all the data perfectly, but I did notice that there weren't any options to copy the apps, settings and screen configs. Hence I was disappointed, but not surprised when it didn't copy these things.
I then saw that Lollipop had this cloning function (Tap & Go) which was just what I wanted, got confused over the meaning of NFC, upgraded both phones to Lollipop and discovered that I couldn't use T&P. Very frustrating, especially as this functionality can easily be implemented over Bluetooth or Wi-Fi. I'll bet when Lollipop was being developed, the beta testers suggested this functionality and were quite annoyed that this wasn't done when there's no technical reason for not doing so.
Related
Hello guys,
For a couple of months I have been testing several top roms for Galaxy S GT-I9000. The problem is that when I found the most stable and faster one (for my requirements), I have the same problem over and over again, being unable to find the cause. Everything is related to GPS tracking.
To start with the begining, I bought the phone as a present for my wife a while ago. Because of the fact that I wanted to be able to keep up with ALL new applications from Google Store, I have flashed Jellybean [X-bean 2 ROM] (finding it runing considerably faster than the actual third version).
However, after installing all the applications that we were using, I found out that after a couple of GPS (or network) tracking uses, the tracking part just stops working until reboot.
For example, in Viber you have the option to send location when writing a message. After a period of using it, it either keeps giving a past location (which sounds like getting stuck on a specific location fix) or even an error that is unable to locate or something like that.
We also considered funny to track when needed where each of us is (on our way) when we want to meet somewhere in the city after jobs. For that we have used "Where are you sweetie" application. After a few uses, it gives you a location updated dozens of minutes ago, or even "Unable to locate phone" message.
Additionally, for security purposes, I had installed Cerberus. As a test, I wanted to see if that fails too at the same chapter and of course, I got the same result. Either an old location (unless I force it to refresh by activating GPS real-time tracking) or even a "cannot communicate to the phone" sometimes.
The funny part is that after a restart it all works perfect for some time.
And I want to mention that this happened for all jellybean custom roms that I have tested.
I am sure that I am not the only one having the same problem, so even though this is not something that we couldn't have lived without, I was just curious if either of you guys have heard of this or of a fix for this issue.
I'm having some problems with NFC. Prior to Friday evening, my NFC was working great with Android Beam, Google Wallet, etc.
Friday afternoon I was playing around with Tasker and the NFC Locale plugin to create some tasks when a specific NFC tag was read. I made just a simple "turn on flashlight" task and was wowing myself with the magic of the tag. I also installed the Xposed module that lets you use NFC with the screen off. After playing with it for awhile I put my phone in airplane mode (I was in a poor service area). A few hours later (still in airplane mode but with NFC turned on) I resumed play with NFC and Tasker to make some more interesting tasks but noticed my phone wasn't responding to my previously used tag or any other (unused) tags. I thought maybe since I didn't cell signal that is why it wasn't working (stupid thought, I know) and decided to wait till I had service to resume the tinkering.
Fast forward to tonight, I still can't get my phone to respond to any NFC tags or any tap to pay terminals (for use with Google Wallet) or Android Beam with my SO's Moto X and I can't think of what else to try before I do a factory reset.
So far I have:
1) frozen/hibernated every NFC using app individually to test each one to see if any of them would work on their own
2) uninstalled every app and Xposed module that uses NFC except Google Wallet
3) rebooted my phone multiple times ensuring NFC is on
4) ran a logcat to make sure NFC is actually turning on/off and from what I can tell it is (I can post the logcat if need be)
Factory resets are such a PIA and I'd like to avoid it at all costs but I am thinking that is the way I need to go unless anyone has any other ideas for me. Googling around it seems like a lot of NFC issues tend to be hardware related...I am definitely hoping that is not the case.
Thanks in advance for any advice or input!
Hi all. I did a search but couldn't find a clear answer to this particular question. If it's out there I would appreciate if you could throw me a link.
I just received a replacement Moto X for my current unit which has a bad camera. Both were created using Motomaker if that makes a difference.
I've got the new phone activated and used Migrate to move the basic stuff, but I can't seem to find a way to move the majority of my apps to the new phone (I've used Titanium Backup previously but I guess that's not an option here as both have 4.4.2) and I've got quite a few programs that contain settings and data that I really don't want to lose or have to recreate from scratch.
Is there a program that would allow me to move the bulk of my current apps and the related data to the new phone relatively easily or should I just start the copy/paste bucket brigade via USB and my computer?
Edit: I'm also open to using adb and a nandroid backup if that's a possibility, but I would appreciate pointers to instructions if they exist. Thanks.
Does Google back up work, when I switched from my HTC to my MotoX, everything went across including wifi locations.
It should be in your menu, you are actually backing up your Google account and it restores data on any device that you sign in on.
Tapatalked from my G PAD 8.3
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
younger06 said:
Does Google back up work, when I switched from my HTC to my MotoX, everything went across including wifi locations.
It should be in your menu, you are actually backing up your Google account and it restores data on any device that you sign in on.
Tapatalked from my G PAD 8.3
Click to expand...
Click to collapse
It doesn't appear to be working as advertised. I've installed the same apps that were on my original phone and none of them had the same configuration or data on the new phone. I've even tried removing apps from the new phone and forcing a sync on the old phone, then reinstalling on the new phone about a half hour later to see if that might help but have had no better results.
nhizzat said:
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
Click to expand...
Click to collapse
Is it working properly with the Moto X now? I've seen quite a few reports of it failing on Motorola phones and the Play description itself mentions that it's not available to Motorola devices.
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
So i recently switched from sprinit to verizon and at the sametime updated my phone with the new system update. Since then my gps randomly stops keeping track of my location in a trip. I downloaded a gps tool from the app store and when it happens i use the app to reset my gps and it works. But then later if I use google maps again it randomly gives me the same issue. Its a easy enough fix but its annoying to have to keep doing that.
Was hoping there was some kind of fix or am I just unlucky and the gps is starting to go out.
Any help would be appreciated.
Thanks
Check here...settings, connections, mobile network. Make sure u r on lte/cdma for Verizon
Sent from my SM-N950U using Tapatalk
chefjl said:
Check here...settings, connections, mobile network. Make sure u r on lte/cdma for Verizon
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
Ya it was set to global. Hopefully it fixes it. Will test it out later when i need to leave work.
Having the same issue. I believe it started occurring after software update: N950USQU7DSL5 which was pushed out early February for me.
sjsuguy83 said:
Having the same issue. I believe it started occurring after software update: N950USQU7DSL5 which was pushed out early February for me.
Click to expand...
Click to collapse
Ya I switched over from global to lte/cmda like chefji suggested and it helped were its not occuring as much but I still have the issue. Hopefully it gets fixed. If not i may have to try to revert back to an older update.
I just saw this thread after posting my questio above. Same issue and I'm on Verizon too. Mine has always been a Verizon phone. I dont recall exactly when the problem started but definitely within last 2 months. Never had issues before. For me, the workaround seems to be to use an app called GPS Fix/Optimizer and on the home page of that app, click on the button that says System off on bottom left and turn it to System on. I hate having to do these extra steps and never had a problem with any other Android phone doing this.
Try wiping the Cache Partition. If that doesn't help, backup your device and perform a Hard Factory reset.
iceepyon said:
Try wiping the Cache Partition. If that doesn't help, backup your device and perform a Hard Factory reset.
Click to expand...
Click to collapse
Wipe cache partition but there is no reason to do a hard factory reset. This is a GPS problem and not a software issue. It is not isolated to Note 8 phones but seems to affect S9, S9+, Note 9, Note 10, and possibly a few others. It also started early Feb after Note 8's received a security update and the others received the Android 10 update. Samsung, Google, and especially Verizon are all pointing fingers at each other for blame instead of working together to try and come up with a fix. One thing I have found is that unlike the countless Android phones I have had in the past, there is absolutely no way to control the GPS. There no longer is an on/off switch. The best available choice is to search deep in settings to find Location but the only thing it controls is on/off switches for Wifi Scanning or bluetooth scanning. Turning both of those on now is considered High Accuracy. The only thing that has worked for me is using an app called GPS Fix/Optimizer in conjunction with an app called GPS Status. By using both of those apps before using Waze or Google maps, allows me to successfully navigate and it can find my exact position. I have also discovered that besides Waze and G Maps, many are reporting the same kind of problem with other location based apps such as Uber and Lyft. This needs to be fixed and I could care less which company is at fault but one of them needs to step up or all need to come together and figure out the problem...
mikeyk101 said:
Wipe cache partition but there is no reason to do a hard factory reset. This is a GPS problem and not a software issue. It is not isolated to Note 8 phones but seems to affect S9, S9+, Note 9, Note 10, and possibly a few others. It also started early Feb after Note 8's received a security update and the others received the Android 10 update. Samsung, Google, and especially Verizon are all pointing fingers at each other for blame instead of working together to try and come up with a fix. One thing I have found is that unlike the countless Android phones I have had in the past, there is absolutely no way to control the GPS. There no longer is an on/off switch. The best available choice is to search deep in settings to find Location but the only thing it controls is on/off switches for Wifi Scanning or bluetooth scanning. Turning both of those on now is considered High Accuracy. The only thing that has worked for me is using an app called GPS Fix/Optimizer in conjunction with an app called GPS Status. By using both of those apps before using Waze or Google maps, allows me to successfully navigate and it can find my exact position. I have also discovered that besides Waze and G Maps, many are reporting the same kind of problem with other location based apps such as Uber and Lyft. This needs to be fixed and I could care less which company is at fault but one of them needs to step up or all need to come together and figure out the problem...
Click to expand...
Click to collapse
Hello, I am having the same problem. I have a Galaxy Note 8 from AT&T, this problem started end of February, workaround is to switch the location OFF and then back ON but is annoying. I reset network, clear cache and nothing fixed the problem so I thought was a problem in the phone itself so I submitted a claim to Asurion, got the brand new replacement phone and the following day exact same problem appeared.
Now reading this thread I am fully convinced that is a bug. I hope it gets solved ASAP.
I posted about this on another thread and what I have stumbled on:
https://forum.xda-developers.com/showpost.php?p=82337821&postcount=18
I have seemed to narrow it down to it only happening when I connect my Note 8 to my 2016 Chevy Silverado and use Waze or Google maps on my radio via Android Auto. I made a few changes that I mentioned in the above thread to the battery settings for a couple apps. Because of the VID, I haven't been driving as much so I haven't done a lot of testing but this has seemed to help.
Well I thought it was fixed but it doesnt seem to be and it really seems to be an Android Auto glitch. Just yesterday, I had to run a couple errands and had phone plugged in for Android Auto. First couple trips, it worked just fine. Then one more trip, all I saw was the floating blue dot in Waze. While still plugged in to my Chevy, I went to GPS Fix and clicked to turn system on. I then went to GPS Status and it couldnt get a location fix. In GPS Status, I also selected Manage A-GPS State. First I tried reset and no fix. Then I did download and again, no fix. I gave it a little bit of time to see if it would work but it didnt. So next I unplugged my phone from my Chevy and again checked in GPS Status and no fix. I again went into Manage A-GPS State, reset, no fix, then download, and it fixed on my location right away. So for me, this is really pointing to an Android Auto issue. Hopefully a fix will come along soon...
Just to add, Waze had already been started once I fired up the Android Auto on the My Link Chevy radio as I had started a route. Waze was still running in the background when I disconnected from my Chevy radio so that kind of eliminates Waze as the problem, at least for me. Especially when GPS Status couldnt get a fix while I still had Android Auto running on my Chevy but as soon as I disconnected and ran through the GPS Status reset and download, I had a fix and Waze worked fine again.
Has this been resolved yet? Any fixes found?
Not completely resolved yet but the annoying workaround gets it working again. It should just work on it's own without all the extra steps. And I was able to get semi confirmation after creating a thread in the Google Support sub forum for Android Auto. I am being told that when plugging in the phone to use Android Auto that Android Auto attempts to also connect to the gps in my Chevy. It's kind of confusing and dont quite understand exactly what is happening. My vehicle does not have a dedicated gps system but I am being told that there could be some kind of GPS in the vehicle anyway and that could be causing the problem. I call BS on this info but I also didnt have any part of creating Android Auto. If this is what is happening, it pretty much says that Android Auto is probably the cause of the issue. I dont need military precision on my gps location and my phone inside my house will give me an accuracy of around 10 feet. No reason to be more accurate than that and this shouldn't even be a part of the Android Auto app.
https://support.google.com/androidauto/thread/45792804?hl=en
I posted this in the other thread but I'll add it here for completeness. I'm having the same issue on an unbranded note 8. But I'm not using android auto. I can use gps tools and it holds a lock fine. But if additional programs are launched, waze, maps, jbv1 I lose lock.
My Note 8 has the problem, I am not using WAZE, I am using The FitBit App with my VERSA 2, My Husband has the Note 9 and is using the FitBit App with his VERSA 2. His resulting miles walked and my resulting miles walked should be almost identical. They are not. I am consistently showing less miles than he does. When looking at the exercise map, generated by the GPS data, His walk path follows the streets we walked accurately, while mine cuts the corners, has me walking in drunken path across the properties located near the road and in some instances cutting across non walkable terrain. Giving me less mileage than my husband. Thankfully, my steps are accurately accounted for. I want this problem fixed. I don't like being cheated of my exercise miles.
Any update here? Note8 on Verizon. Having the same problem with Endomondo (fitness app) and Google Maps. Hard reset phone, and it's still problematic. For me, it might start out working fine, then midway thru a run it will stop. Usually resetting the app will make it work again.
I use T-mobile, and I tried just about everything and almost gave up. Today I was thinking that mayve its the wifi and bluetooth settings helping the GPS so I went to location and turned off the wifi and bluetooth improve accuracy settings and problem is fixed for me! So much headache gone. I was about to buy a new phone.
Dominicgage1994 said:
I use T-mobile, and I tried just about everything and almost gave up. Today I was thinking that mayve its the wifi and bluetooth settings helping the GPS so I went to location and turned off the wifi and bluetooth improve accuracy settings and problem is fixed for me! So much headache gone. I was about to buy a new phone.
Click to expand...
Click to collapse
Keep us updated if this continues to work. I will try this as well to see if it helps on mine too.
Dominicgage1994 said:
I use T-mobile, and I tried just about everything and almost gave up. Today I was thinking that mayve its the wifi and bluetooth settings helping the GPS so I went to location and turned off the wifi and bluetooth improve accuracy settings and problem is fixed for me! So much headache gone. I was about to buy a new phone.
Click to expand...
Click to collapse
I just tried this and it failed location fix right away after opening Waze in Android Auto on my Chevy. So still searching for a real fix...
Well it looks like the Android Auto developers are starting to listen. After creating a thread on their google community page months ago, and numerous others posting same issue, they said they were going to reach out to several posters by email with directions on creating a bug report to forward to them. They claim they have been unable to recreate the problem and wanted bug reports from several having the problem so they could take a look. I had another failure today on a trip so I created a bug file and forwarded it. We shall see what they find...