Here it is in a nutshell: Error 927 on ANY download, any app, any game, be it paid or free, on my Nexus 7 (2013) FHD. I've done the following:
- Cleared the data and cache for the Google Play Store, Download Manager, and Google Services Framework.
- Uninstalled updates for the Google Play Store and Google Services Framework.
- Deleted and re-added my Google account.
- Rebooted.
- Hard reset.
- Downgraded to 4.3 and re-upgraded to 4.4.2.
- Tried to download the apps and games from the Google Play website, and get "An unexpected error has occured. Please try again later."
- Changed the filter and proxy settings on my Cisco router.
- Switched to LTE, and... same thing.
- Created another Google account, and it worked, but I will NOT be forced to re-purchase the apps I've spent nearly $80.00 on over the years, or upload my music collection to Google Music again.
- Reached out to Google for help, and... crickets.
I'm at the end of my rope. If this isn't resolved soon, I'm returning the Nexus to Wal-Mart. I've NEVER had this sort of issue before, even with my first-generation Nexus 7. I've had Android tablets since my Motorola Xoom awhile back. I've ALWAYS had Android tablets. I'd hate to have to abandon Android because of this idiocy, but I may have to do so. I don't want to have to go with Apple for both my smartphone and tablet, but it's starting to look that way.
If anyone has any suggestions that aren't listed above, please, help me out. I love my Nexus 7, but without apps and games, it's pretty worthless.
Thanks in advance.
Normally deleting and adding back the Google account is a solution for Play Store problems, but as you said, you tried that. Some have reported that error 927 is because of a network connection error. How is web browsing? YouTube?
abarax said:
- Downgraded to 4.3 and re-upgraded to 4.4.2.
Click to expand...
Click to collapse
How did you do that? Did you download the 4.3 ROM to flash it? Did you unlock and flash a custom recovery?
When all else fails, flash the stock ROM, especially with your downgrading and upgrading. Google's files include a "flash-all.bat" within that will wipe everything and flash the stock ROM and recovery.
https://developers.google.com/android/nexus/images#razor
Pandae said:
Normally deleting and adding back the Google account is a solution for Play Store problems, but as you said, you tried that. Some have reported that error 927 is because of a network connection error. How is web browsing? YouTube?
All web browsing and pre-installed apps work just fine. Just any attempts to update those apps, or install any other apps from Google Play, fail with error 927.
How did you do that? Did you download the 4.3 ROM to flash it? Did you unlock and flash a custom recovery?
When all else fails, flash the stock ROM, especially with your downgrading and upgrading. Google's files include a "flash-all.bat" within that will wipe everything and flash the stock ROM and recovery.
https://developers.google.com/android/nexus/images#razor
Click to expand...
Click to collapse
I actually have flashed the stock ROMs, from the original 4.3 to 4.4.2, with the exact same results. I've also made certain not to unlock the bootloader and to not root as to recreate the OOB experience as well. At this point, my options are exhausted.
abarax said:
I actually have flashed the stock ROMs, from the original 4.3 to 4.4.2, with the exact same results. I've also made certain not to unlock the bootloader and to not root as to recreate the OOB experience as well. At this point, my options are exhausted.
Click to expand...
Click to collapse
Are you able to install apps on another device with the same account? If not it may be a problem with your account...
Dexxon said:
Are you able to install apps on another device with the same account? If not it may be a problem with your account...
Click to expand...
Click to collapse
I know his pain I have flashed reflashed installed stock and im using a atrix 2 with ics 4.0.4
im hoping its a google server problem and it will be fixed
I was having the same problem for the last two days and I went to settings/Google account and noticed there was a sync error with sound search for Google play and I manually synced it and now apps download .
Sent from my Nexus 5 using Tapatalk
I went into my account removed my devices from it on the web and signed in on my phone now it works
Sent from my MB865 using Tapatalk
I've been having the exact same issue for 4 days. Regardless of rom, phone, or gmail account I use. I've done every wipe format imaginable even Odin as I have a Samsung phone same issue. Now I cant even get any Google apps to connect at all. Such as Google plus play store YouTube etc...Google says never heard of it before sorry.
dawiseguy77 said:
I've been having the exact same issue for 4 days. Regardless of rom, phone, or gmail account I use. I've done every wipe format imaginable even Odin as I have a Samsung phone same issue. Now I cant even get any Google apps to connect at all. Such as Google plus play store YouTube etc...Google says never heard of it before sorry.
Click to expand...
Click to collapse
I'm having the exact same problem now for a few days. I called Google support and they are aware of the problem and had no resolution. I was told too bad basically.
Out of curiosity, for those having this issue, did you upgrade to a 4.4.2 ROM?
I updated to stock rooted 4.3 galaxy note 2 Verizon and it happens on all of my gmail accounts too
Sent from my SCH-I605 using Tapatalk
I have the same problem. Ran across this thread doing a search for the error 927. Running a Verizon HTC One and an LG G Pad 8.3. Both have the same problems, and i too have called Google several times. Their answer was to call HTC. I was livid. I changed my password, but was only a temporary fix until I made a purchase from the Play store. Then the error came back. I realize i am in the Nexus 7 forums but wanted to chime in since the problem is happening to me too. Hopefully Google comes up with a fix. Too much money tied up to just create new account, which does work by the way.
Creating a new account shouldn't even be an option what it the issue happens on the new account? Google just needs to fix it.
Sent from my SCH-I605 using Tapatalk
dawiseguy77 said:
Creating a new account shouldn't even be an option what it the issue happens on the new account? Google just needs to fix it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
I agree...I would be ok if they just said we're working on a fix, but just to ignore me and say call the manufacturer pizzed me off.
Sent from my HTC6500LVW using Tapatalk
planedoc said:
I agree...I would be ok if they just said we're working on a fix, but just to ignore me and say call the manufacturer pizzed me off.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Yeah Google making me mad too
Sent from my SCH-I605 using Tapatalk
Same boat. I did everything the original poster did as well. Called into play store support and eventually got passed off to tier 2 support. Haven't heard anything in over a week.
The issue affects every device I log into with my account. Originally showed rpc:s-7 error, now 927.
Anyone with this problem find a solution? Again, I've done everything the op posted. In the past I've been able to correct the problem. But this time, no go.
Have the same problem... In every device I'm using with my account... 3 tablets, 2 cell phones. Spent more than 400 dollars in apps.. Can't download, nor even update. Always error 927. Changed password and problem persists.. It's obviously a problem with my account.. Wonder what could I do.
Have you tried installing apps from Google Play on a computer?
Hello, just an update...
My problem has gone... Seems it was from google side.
Too bad I had to flash my cel 3 times before I realized it was happening to all my devices.
Don't know if the password change had anything to do with the fix since, at least, it didn't work immediately.
If you encounter the same problem don't panic... give it a little time, hopefully it fixes on its own.
Thank you very much.
Hello, I am running a Note II with jedi master x2 4.3 and purchased a Gear 2 neo, running latest firmware version.
http://forum.xda-developers.com/show....php?t=2568537
I cannot remember if I uninstalled S-Voice or it is not included, either way after trying to get it to work I donwloaded and installed an APK for the s4's s voice, it starts up and seems to work on the phone, but the watch is not recognizing it (and I did restart the watch, at which point it asked me (again) to accept the terms and conditions for S-Voice and again told me it needed to be installed.
Any thoughts? And thanks for taking the time to read this!
Edit: I fixed it using these instructions as if my phone was a non samsung
I have looked at many forums about the S Voice not connecting with the Gear 2 Neo but none of them have been able to fix my problem. A lot of people say they were missing the saproviders.apk but I have that and I have uninstalled and reinstalled the Gear app which installs it and still nothing.
When I try to connect it says connection failed. When I go in to my apps in the gear menu, I can't get in to the setup for S Voice. Everything else seems to work just fine. I get my messages, phone calls and other notification. I just can't get S Voice to connect. It works fine on my Note 4, so I know the app itself is working.
I have a Note 4 running 5.1.1. It is not rooted. It was connected to a Gear Fit before I got the Gear 2 Neo.
Does anyone have any ideas. I have been search for days to find out a solution.
Thanks in advance.
dsireme said:
I have looked at many forums about the S Voice not connecting with the Gear 2 Neo but none of them have been able to fix my problem. A lot of people say they were missing the saproviders.apk but I have that and I have uninstalled and reinstalled the Gear app which installs it and still nothing.
When I try to connect it says connection failed. When I go in to my apps in the gear menu, I can't get in to the setup for S Voice. Everything else seems to work just fine. I get my messages, phone calls and other notification. I just can't get S Voice to connect. It works fine on my Note 4, so I know the app itself is working.
I have a Note 4 running 5.1.1. It is not rooted. It was connected to a Gear Fit before I got the Gear 2 Neo.
Does anyone have any ideas. I have been search for days to find out a solution.
Thanks in advance.
Click to expand...
Click to collapse
Sorry, when I first looked I didn't get a Gear forum. I will ask in there instead. Thanks
I am currently on an HTC 10 running the latest version of LeeDroid, rooted. Ever since I flashed the new ROM, my Gear S2 Classic was unable to connect, but I left it like that as it still showed the time. After getting frustrated with not receiving notifications, I reset the watch and uninstalled everything related to the Gear off of my phone (Samsung Accessory Service, Gear S Manager, Gear S Plugin) and reinstalled everything. I attempted to connect to my watch for setup afterward, but every single time it prompts me to connect to my watch, the app crashes and the whole process has to restart. I can confirm that the watch can connect to my Note 5. Is this an issue with root?
Since a couple of the gear app updates the download of the depending software failes.
I was also on leedroid but I have had to rollback to stock to make everything work properly with my S3 frontier. Sh.. t happens. I rooted my device by myself
I had this info from Lee directly.
So we aspect the hTC N update next week... Hopefully.
Sent from my HTC 10 using XDA-Developers Legacy app
---------- Post added at 04:38 PM ---------- Previous post was at 04:37 PM ----------
estuardoman said:
I am currently on an HTC 10 running the latest version of LeeDroid, rooted. Ever since I flashed the new ROM, my Gear S2 Classic was unable to connect, but I left it like that as it still showed the time. After getting frustrated with not receiving notifications, I reset the watch and uninstalled everything related to the Gear off of my phone (Samsung Accessory Service, Gear S Manager, Gear S Plugin) and reinstalled everything. I attempted to connect to my watch for setup afterward, but every single time it prompts me to connect to my watch, the app crashes and the whole process has to restart. I can confirm that the watch can connect to my Note 5. Is this an issue with root?
Click to expand...
Click to collapse
Since a couple of the gear app updates the download of the depending software failes.
I was also on leedroid but I have had to rollback to stock to make everything work properly with my S3 frontier. Sh.. t happens. I rooted my device by myself
I had this info from Lee directly.
So we aspect the hTC N update next week... Hopefully.
Sent from my HTC 10 using XDA-Developers Legacy app
Do you think installing LeeDroid unrooted would work? If not then I guess I will have to go back to stock ?
Hello, i use the Gear S App with the Gear S Plugin App from the Playstore with my HTC 10 and my Gear S3 Classic works fine with them..
So i will think, its a Problem with the Rom.
Did all Services for the Gear S App was installed, or was they removed by the Dev?
Nice Greets
Custom roms have a problem with the Samsung gear S plugin. Maybe it's because they are all deodexed? The only rom working for me is the nougat port for Verizon from santod040
Sent from my HTC6545LVW using Tapatalk
Anyone figure this out?
I read somewhere on another forum that the issue is some rom ID or device ID. Samsung Gear App or Plugin reads this ID and depending on the ID does this or that (checking if the device supports "something" - can't now remember what). Problem is that custom ROMs have IDs which this app doesn't recognize and gets into a piece of code which crashes. There was a patch to be applied to the Samsung App or Plugin to ignore the ID check which made it work OK, but it was a patching process one would have to repeat each time a new version of the app comes up.
Good morning,
Has anyone else had issues with setting up Android Pay on their watch with the 2XL? I have an LG Watch Sport that worked great with my Nexus 6P, but when I try to set it up on with my Pixel 2 XL, it tells me it cannot be set up because it's rooted, has an unlocked bootloader, or a custom ROM. Both are stock, but both are on the Beta Program, but I didn't have that issue when the Nexus was on beta. I've tried resetting the watch with no luck. Any ideas?
Thanks!
ferdeenand said:
Good morning,
Has anyone else had issues with setting up Android Pay on their watch with the 2XL? I have an LG Watch Sport that worked great with my Nexus 6P, but when I try to set it up on with my Pixel 2 XL, it tells me it cannot be set up because it's rooted, has an unlocked bootloader, or a custom ROM. Both are stock, but both are on the Beta Program, but I didn't have that issue when the Nexus was on beta. I've tried resetting the watch with no luck. Any ideas?
Thanks!
Click to expand...
Click to collapse
it doesn't work in my country so i can't test
BUT root brake android pay from 2016 i believe
you have to use the hide function in magisk
hide alllllllll the apps that don't need root
then reboot then clear data from android pay/google service/ play store
then try again
After digging around online through the Android Beta Google+ page, it seems that it doesn't work on the Wear beta, but since it was already active with the 6P, it continued to be active. Pairing with the Pixel reset the watch and that's what stops it from working. I'm leaving the beta and will downgrade the OS when I get home to a charger.