Hello all;
I was fortunate enough to get my sons Moto and have been trying to get it connected with no luck.
I'm not 100% certain if its the rom or the kernel (both custom), but I thought I would try asking here first. My gapps is the latest so I don't think that would be the issue.
The second I install Android Wear from the Play store I get immediate Google Play services failures. I've done much of the normal troubleshooting and it narrows down to; if I disable WearableService in Google Play services, I lose the error, however it also loses connectivity. If I delete the app, it immediately corrects the issue.
Before I ask in the kernel/rom forums, has anyone else had this issue?
Thanks!
Related
Hey all,
I finally made the jump to the One M8 from my iPhone a few weeks ago, and I quickly unlocked, S-OFF'd, rooted, and flashed MaximusHD. I had to switch back to my iPhone for a couple of weeks for work reasons, and yesterday decided to switch back to the One. When I booted it up, I saw that an OTA was available for MaximusHD 7.1, so I installed it and realized that I was missing LTE and stuck on HSPA. A quick phone call to AT&T resolved my issue when I realized that it was simply a provisioning problem (since the 4S I had been using is LTE-less). Now for the strange part - after being on WiFi all day at home, I come to work and try to fire up the Google search app (while connected to LTE), no dice. The app throws a "Can't reach Google at the moment." So I fire up Chrome, and try google.com - after a painstaking few seconds, I get "Timed out". I navigated to a different site (CNN), just to test connectivity and voila! - the page loads immediately. I retried google.com, and the site still times out. Also, the Play Store has no connectivity over LTE, also throwing "Connection timed out." All other apps (Instagram, Speedtest, even GMaps/G-mail) work while on LTE. If I force the phone to drop to HSPA (by choosing GSM/WCDMA only in Mobile Network settings), then magically all the forementioned apps and google.com work properly. It seems that all the Google services are "blocked" while connected to LTE. So far I've tried:
- Airplane mode on/off
- Rebooting
- Clearing defaults and wiping all the application caches (as well as the Play frameworks)
- Factory resetting/Wipe Cache
- Flashing a different ROM (VenomOne) and starting fresh
- Confirmed that APN settings are correct (other sites other than google.com work fine)
- Deauthorized my phone in my Google account settings
- Created a new Google account
None of these worked. I also tethered my MacBook to the phone, and was able to access google.com via Safari perfectly fine while the phone was sharing it's LTE connection. I installed Firefox on the phone, and strangely google.com works fine as well. It seems as though any Google services that rely on my login fail to work on LTE, but work perfectly fine over HSPA. Google searches work, the GSearch app works fine, and the Play store loads immediately. Switch back to LTE, all other apps and sites load properly, Google services fail again (now including Sync).
Sorry for the lengthy post guys, but I'm out of ideas. I'm going to (unfortunately) flash the phone back to stock and see if that works, and if it doesn't, I'll drop by the AT&T store tomorrow and see if a new device makes a difference. It doesn't quite add up, unless its a weird provisioning problem. Hopefully you guys can help or might have an idea? Thanks!
Hey man, I'm jumping on board with you on this issue. I've been battling this same exact issue for the last month or so. I've literally tried everything in the book and can't seem to figure it out. Not hijacking your thread, but I was going to create a thread here as well since I'm out of ideas. Here's my experience, hopefully we can knock something out here to fix this plague of a problem.
I've flashed multiple different versions of firmware, multiple different ROMs, cleared every kind of cache you could imagine, etc. Often I can get the issue to disappear for a short while, but it always returns.
I did restore the phone to stock using the factory RUU. That actually did work for a short period of time, but then I started receiving a message that said "Restricted Access Changed - Data Service is Blocked".
That message led me to this site: Nexus 5 Restricted Access Changed Issue - Solved
After being 100% stock, I uninstalled updates for Google Play Services. That worked for 3 days. After 3 days, I connected to wifi for the first time, after I turned wifi off - no connection to the Play Store again.
That was last night. Flashed newest firmware (2.22.401.5) and Insert Coin 4.0.9 this morning... still no good. Google Search and the Play Store time out with "No Connection" messages.
The one thing I believe differs from me to you, is that HSPA+ (GSM/WCDMA) does not work either. I believe you said that worked for you?
Certain little things seem to randomly make it work for a short period of time. Once I flashed cache/dalvik and did a fastboot erase cache - magically worked after that. Though, that only lasted for a day or two.
Think I'm going to jump on Support Chat with AT&T to see if they can provide any help, though I doubt it. I'll update here as I go along so hopefully we can get this figured out. Sorry for the lengthy response.
Same issue, also from CT
Just responding to the OP, I am having the EXACT same issue as you with my Google Services not always connecting while I am on LTE. I wonder if it's a geographic thing as I am in Southeast CT Groton to be exactly although I have also had the same issues in Niantic at work. I also have AT&T service but my device is a HTC One M8 Developer edition. I sometimes can connect to Google services over LTE but it seems to be hit or miss. Services that I have been having trouble with include gouge search accessed through chrome, google now/voice search, Play store and Wallet. I have not had any issues streaming music over Google Play music, even when my other services were not functional over LTE for some reason. I have tried all the suggested trouble shooting steps such as uninstalling Google updates, clearing google play services cache and app data, verifying my date and time setting, etc. I even unlocked and rooted just to delete the hosts.txt file as was suggested in the system/etc folder. So far nothing I have done has completely fixed my LTE issue, it was the exact same behavior on kk 4.4.3 and after I applied the kk 4.4.4 OTA update. I have not tried S-off or installing any custom ROMs. As I type this my Google services ARE working over LTE but I'm not expecting that to remain constant based on past experiences.
trailrunnerx said:
Just responding to the OP, I am having the EXACT same issue as you with my Google Services not always connecting while I am on LTE. I wonder if it's a geographic thing as I am in Southeast CT Groton to be exactly although I have also had the same issues in Niantic at work. I also have AT&T service but my device is a HTC One M8 Developer edition. I sometimes can connect to Google services over LTE but it seems to be hit or miss. Services that I have been having trouble with include gouge search accessed through chrome, google now/voice search, Play store and Wallet. I have not had any issues streaming music over Google Play music, even when my other services were not functional over LTE for some reason. I have tried all the suggested trouble shooting steps such as uninstalling Google updates, clearing google play services cache and app data, verifying my date and time setting, etc. I even unlocked and rooted just to delete the hosts.txt file as was suggested in the system/etc folder. So far nothing I have done has completely fixed my LTE issue, it was the exact same behavior on kk 4.4.3 and after I applied the kk 4.4.4 OTA update. I have not tried S-off or installing any custom ROMs. As I type this my Google services ARE working over LTE but I'm not expecting that to remain constant based on past experiences.
Click to expand...
Click to collapse
Did you contacted your carrier about this LTE and Google services issues? Cause I can use all Google services on LTE. Its kinda a bummer that you cant use something that you are paying for tho.
Poslano z mojega HTC One_M8 z uporabo Tapatalk
This guy has the same issue: http://forum.xda-developers.com/att-htc-one-m8/help/lte-connection-issues-3-28-401-7-t2913168
He thought it was caused by flashing firmware. But based on your experience, it might just be a carrier issue.
I just got my new unlocked Fire Phone about a week ago, and after a week of use, I love this phone but do have a couple of questions to help out my experience.
1)I find the need to use Google Play for a couple of apps... Tried downloading the google play store useing a video o a different post found, only to find that a "Google Play Services stooped" error rendered my phone useless. I uninstalled all the google apps and my phone worked fine, but still need gale play.. How can I fix this??
2) I currently have Fire OS 3.6.8 but read that there is a new Fire OS 4.6, but my phone wouldn't update it. What can I do to fix this??
mcadenas45 said:
I just got my new unlocked Fire Phone about a week ago, and after a week of use, I love this phone but do have a couple of questions to help out my experience.
1)I find the need to use Google Play for a couple of apps... Tried downloading the google play store useing a video o a different post found, only to find that a "Google Play Services stooped" error rendered my phone useless. I uninstalled all the google apps and my phone worked fine, but still need gale play.. How can I fix this??
2) I currently have Fire OS 3.6.8 but read that there is a new Fire OS 4.6, but my phone wouldn't update it. What can I do to fix this??
Click to expand...
Click to collapse
I hate this phone right now because Google updated its play services to 7.8.3.
1. You probably installed Play services 4.4.x, but it then updated it automatically to 7.8.3. That has been breaking everything google on this pone.
2. check the general forum and you'll see them.
I can't wait until I get the LG G4.
Thorin78 said:
I hate this phone right now because Google updated its play services to 7.8.3.
1. You probably installed Play services 4.4.x, but it then updated it automatically to 7.8.3. That has been breaking everything google on this pone.
2. check the general forum and you'll see them.
I can't wait until I get the LG G4.
Click to expand...
Click to collapse
Actually, update your phone first. I had the same issue with the google play store, so I completely removed it from the phone. After the most recent update to FireOS, everything works smashingly. Uninstall google play services, update your phone, then put everything google back. Bada bing, bada boom, all better.
mstrblueskys said:
Actually, update your phone first. I had the same issue with the google play store, so I completely removed it from the phone. After the most recent update to FireOS, everything works smashingly. Uninstall google play services, update your phone, then put everything google back. Bada bing, bada boom, all better.
Click to expand...
Click to collapse
Agreed. After updating to 4.x it's been great. Even the overlapping font on google maps is gone. I can change my keyboard easily.
But I'm still going to get the LG G4.
Is anyone else having issues getting a GPS lock on the fire phone? I recently was gifted one after the fire sale and I have been having issues ever since. When it actually works, the GPS has significant drift, and it often has trouble catching up with me when I am walking around. It also takes forever to acquire a GPS lock, if it can at all. I have waited 10 minutes, inside an open park with no trees within 50 meters of me for a lock with no luck. I can't even get a lock inside my own home after trying to acquire a GPS lock for well over a half hour. Sometimes it acquires a lock after 5 minutes, most of the time it doesn't--draining my battery significantly in the process
This has been happening with Ingress, Google Maps, Chrome, the Silk Browser, the built in Maps app, and Waze, so I doubt it is an issue with a specific app not being compatible with the FireOS. I am running stock, unrooted FireOS 4.6.4 with Google services framework, Google play store, Google play services, as well as the Google account manager installed (I need it for Maps, hangouts, and ingress). I am also wondering if the Google Play services apps are somehow interfering with GPS services, but I am very reluctant to uninstall them as I would have to reinstall the delicate setup of old Google apps that allow vital apps like Hangouts, Google Account manager, and Ingress to function in at least a usable state. However, it is with noting that I have tried to see if uninstalling Google Maps would help to no effect.
Does anyone experience issues like this? Is this a common issue? If not, does anyone have any advice on how to resolve the issue? Because if not, I am probably just going to buy a new phone.
GPS works fine on mine with stock 4.6.3 (rooted), try a GPS tester (GPS Test is one) and see if it gets an accurate lock.
GPS disconnects for like 30 second every 2 minutes on mine. 4.6.3 rooted. No Google services. It was previously on AT&T 4.6.4.
Happens on the stock Maps app, Waze, and SatStat.
EDIT:
I tried flashing 4.6.5 and leaving it unrooted. Re-enabled almost all the Amazon apps and its still giving me issues. Maps just says "Searching for GPS..." all the time while trying to navigate to an address. I think this might be hardware issue. Trying to troubleshoot with Mayday.
UPDATE:
In case anyone lands here looking for answers...
After a couple weeks of dealing with Amazon's tech support, they decided to give me a new phone. The new phone's GPS works as expected! It's an AT&T model on 4.6.5 not rooted.
It was suggested I come over here and see what's going on. I've got a 5t with Oxygen.
I've never been able to get Android Auto to load, once. It always says "Something went wrong - Google Play services doesn't' seem to be working right now."
I can't Force Stop the Google Play services, or deactivate it. I've cleared my cache. I don't have a Android Device Management App installed either.
I enrolled and updated to the Google Play services Beta, but haven't still can't force stop it either.
Where do I go from here?
I don't know about this issue.
But I can say I use Android auto daily in my car and have no issues.
I have a Volkswagen caddy 2017 and use ob3
I sideloaded the app because it is not officially released in my country. I use version 3.0.
@dashbarron,
I have the exact same problem . I've also gone the play services beta route with no joy. I've tried literally every possible solution I've come across on the web, still no joy. I can't get past this.
Did you ever get AA to work? How?
Thanks!
-Warren
dashbarron said:
It was suggested I come over here and see what's going on. I've got a 5t with Oxygen.
I've never been able to get Android Auto to load, once. It always says "Something went wrong - Google Play services doesn't' seem to be working right now."
I can't Force Stop the Google Play services, or deactivate it. I've cleared my cache. I don't have a Android Device Management App installed either.
I enrolled and updated to the Google Play services Beta, but haven't still can't force stop it either.
Where do I go from here?
Click to expand...
Click to collapse
I don't know if you have used Android auto before, so maybe you really like it and my advise maybe of no use to you. But while it is good to use, I soon reverted back to using split screen, top half for nav and bottom half to easily switch between music or radio or whatever else you want, even set up a YouTube video before you get going if it's something that doesn't require your focus on it, with gestures it's safer than messing around with the complicated controls in my car! And I have the plug in version of Android auto built into the car, I literally only plug it in when I have my daughter's on board so they can call out ok Google for whatever tune they want on. Anyway that's how I roll when driving and I'm driving all day everyday, hope maybe I saved u some time getting it working
I'm hoping someone can help me with this issue. I have an x80 Pro the CN version. I unlocked the bootloader and rooted it with Magisk. After a few days my Google Play Services stopped working. I reset my phone and again it works a few days then stops. I finally found a video where it shows how to setup everything on Magisk so that your SafetyNet doesn't detect the unlocked bootloader. I did all that, passed all the tests, it worked a few days then the same thing. When I run a SafetyNet checker it just says can't access Google Play Services. Anything that uses Google Play Services doesn't work or is delayed. Here's the weird part.. If I connect my phone through USB to my car or my computer, the play services work well but the minute I unplug it, back to not working again. So something is making this happen and I am not sure what.. If anyone has any experience with this and could help, it would be greatly appreciated.
Go to settings/Account and sync.
Open Google Service and deactivate this. Wait a Moment and activate. Working.
morpheus620 said:
Go to settings/Account and sync.
Open Google Service and deactivate this. Wait a Moment and activate. Working.
Click to expand...
Click to collapse
I just tried. Same thing unfortunately. I have no idea why it's doing this.
Music&Art said:
I'm hoping someone can help me with this issue. I have an x80 Pro the CN version. I unlocked the bootloader and rooted it with Magisk. After a few days my Google Play Services stopped working. I reset my phone and again it works a few days then stops. I finally found a video where it shows how to setup everything on Magisk so that your SafetyNet doesn't detect the unlocked bootloader. I did all that, passed all the tests, it worked a few days then the same thing. When I run a SafetyNet checker it just says can't access Google Play Services. Anything that uses Google Play Services doesn't work or is delayed. Here's the weird part.. If I connect my phone through USB to my car or my computer, the play services work well but the minute I unplug it, back to not working again. So something is making this happen and I am not sure what.. If anyone has any experience with this and could help, it would be greatly appreciated.
Click to expand...
Click to collapse
Have you turned on "Google Basic Services" in settings? Most resellers turn this on for you and install the Google Play store before shipping the device, but it is turned off by default. If you have done a factory reset then it would be off. Turning it on is essential to maintaining permanent Google Play services.
frcraig said:
Have you turned on "Google Basic Services" in settings? Most resellers turn this on for you and install the Google Play store before shipping the device, but it is turned off by default. If you have done a factory reset then it would be off. Turning it on is essential to maintaining permanent Google Play services.
Click to expand...
Click to collapse
Yeah. I turned it off then back on to make sure. But same thing would happen. What I did now is I downgraded it to a previous firmware version and then did the whole safety net process again. It seems to be okay now. Honestly I think it started happening after I would go into the clear cache mode where it wipes the phone cache but not the data on your phone. I haven't done that since I did this and it seems to be okay now. I don't know why clearing the cache would cause this to happen since I like doing that every once in a while. It was very weird because I would connect my phone to USB and the services would come back. Unplug it, they would be gone. Something was triggering it to do that and I have no idea what.
If you have removed com.vivo.pem every firmware update is a problem with google authentication.
Restore com.vivo.pem and you get rid of the issue.
maxant69 said:
If you have removed com.vivo.pem every firmware update is a problem with google authentication.
Restore com.vivo.pem and you get rid of the issue.
Click to expand...
Click to collapse
Well, not only after the update the Google services turn off. In my case every third day they just turn off. There exist more frustration issues, because they can be turned on again easily. But still... It's annoying.