Greetings.
Since today I haven't been able to download apps I purchase in the Market. It all started with a message relating to the change over from Google Checkout to Google Wallet and I believe I had to accept a new agreement, which I did.
After trying to purchase the game I received a message about an error with the purchase using Google Wallet and I would receive an email updating me on the purchase.
Now the game is in a constant state of 'Starting download', and force kill and wiping cache and changing/checking credit card haven't solved the issue.
I wrote many more details about it in another thread started by someone with similar issues, only he posted in a Droid forum:
http://forum.xda-developers.com/showthread.php?t=1465777
Also there was something different about all the other receipts I usually get back from the Market:
http://forum.xda-developers.com/showpost.php?p=21865779&postcount=21
I'm inclined to think it's an issue relating to that Checkout to Wallet transition and possibly because I'm in Canada? Could it also be related to the fact I used a VPN to sign up for Google Music, would that have messed up the country location for my Google account?
Just a few more quick details in case you don't visit the above link... free apps will download, as well as paid ones that I uninstall and reinstall. It seems that all new apps won't download but it let me refund another one I attempted to purchase after it wouldn't begin the download.
Thanks for the feedback,
rAy
Wipe data from Market and Google Framework Services, reboot, and give it another shot...
I seem to recall the Google message saying something about the Market having to reset, so you may have jumped the gun a little...
Well my issue seems to be resolved. It was most likely a Wallet issue, and I believe that deleting and re-entering my credit card fixed it, only it took some time (I'm assuming they tried to charge it again overnight because I woke up with the game already installed successfully this morning and was also able to buy another app. I'm thinking the info got mixed up when they changed me over from Checkout to Wallet.
Give that a try if you get the same issue!
rAy
Sent from my Galaxy Nexus using xda premium
Will google wallet work at checkout if your data is turned off?
Yes, Google Wallet will work at checkout if your data is turned off.
Thanks, got a lot of weird looks though using my phone to pay
Next time someone gives you a look just tell them, "You still carry a wallet? That's old school."
Nice, i told told them welcome to the future
I'm replacing the Shift with a GS3 today, we are buying from a private seller and verifying the ESN is clean at the local Sprint Store.
Is there a way to verify that Google Wallet/NFC is fully functional at that time?
I'm not sure how it works on Samsung, but it is possible to brick the NFC chip when flashing between ROM's if you don't clear the Google Wallet data first. If the phone isn't rooted, then it's a non issue most likely.
This will be my first Samsung phones, so some things are a bit different from HTC.
I have not heard of any issues with Google Wallet after the first week or so.
Logging into Google on the phone, then launch wallet, it should load your data from your account.
Bielinsk said:
I have not heard of any issues with Google Wallet after the first week or so.
Logging into Google on the phone, then launch wallet, it should load your data from your account.
Click to expand...
Click to collapse
Good to know, thanks.
I had a sudden Google Wallet issue this morning. Not sure why.
My phone is stock S3 with root, super user is UNchecked. Has been.
It took a while to get Wallet up and running. Once it was, I have had no problems with it until today. I have used Google Wallet several times a day since I got it up and running. More than 50 purchases already without issue. I have made NO changes to my phone.
Today I tried to use it and it said "unfortunately Google Wallet is not supported............yadda yadda yadda....."
I have not tried anything to fix it. My build.prop is set to the original ATT settings. I thought about resetting Google Wallet, but I decided to check with you guys before I did anything so I don't mess it up.
Any ideas?
ericu571 said:
I had a sudden Google Wallet issue this morning. Not sure why.
My phone is stock S3 with root, super user is UNchecked. Has been.
It took a while to get Wallet up and running. Once it was, I have had no problems with it until today. I have used Google Wallet several times a day since I got it up and running. More than 50 purchases already without issue. I have made NO changes to my phone.
Today I tried to use it and it said "unfortunately Google Wallet is not supported............yadda yadda yadda....."
I have not tried anything to fix it. My build.prop is set to the original ATT settings. I thought about resetting Google Wallet, but I decided to check with you guys before I did anything so I don't mess it up.
Any ideas?
Click to expand...
Click to collapse
Clearing it's cache/data might be a option. Although, it's a shot in the dark as I don't use it myself.
you didnt turn off update in google play market and the app was updated.
the modified version has those checks removed
After having it for a day, my Pixel C is already getting replaced under warranty.
Whenever I try to make a purchase of a paid app on it, I just get an error message "Error retrieving information from server [RPC:S-7:AEC-0]". Purchases work fine on my Nexus6P so the issue seems specific to the tablet. Downloading updates, pre-purchased apps or new Free apps works fine, error only happens when trying to make a purchase.
Have tried all the troubleshooting steps I can find online, clearing data from Play Store and Google Framework Services, no effect. Have removed my Google account from the device, rebooted and then re-added the account, no effect. Done a complete factory reset but still the same issue when I go to the Play Store and try to make a purchase of any paid for app.
I had several payment methods on my account, one of which was expired, but I've removed that and still the same error. I've got over £11 of credit on my Google account anyway and was only trying to purchase something that costs less than £3, so payment cards shouldn't have come into it.
Contacted Google Support and they called me back, said they're going to send a link for me to order a brand new device and instructions on returning the old one.
On the one hand, it doesn't seem like something that would be caused by a hardware issue. But on the other hand, it doesn't seem like an account issue since it's specific to just this one device. Looking around it seems this is a relatively common error, but just removing and re-adding the Google Account should normally fix it.
I'm not running a custom ROM or anything, not even rooted, just running the tablet as it comes (with updates installed)
I've not had any issues like that on either of my Pixel Cs (replaced one under warranty due to the lockscreen pattern bug) so I'd imagine a replacement should sort your issue.
Very strange though... Fingers crossed it gets sorted for you.
Someone has mentioned to me that it could be an issue with the hardware storage of the root certificates that's the problem, which makes sense since the error occurs after the Permissions prompt, at the stage where the Play Store attempts to access the payment information on my account.
Received my replacement Pixel C and still got exactly the same issue.
Whenever I try to purchase an app that costs money, I get an error,
"Error while retrieving information from server.
[RPC:S-7:AEC-0 ELVS-P3QO-E625O]"
(Everything after the AEC-0 is different every time)
This is immediately after turning on the tablet for the very first time and going through the setup process.
Worried that something is wrong with my Google account and that I'm going to have exactly the same issue even if I return it and got a different tablet. But it still works fine on my 6P phone is the thing.
1. In our Android terminal, we go to the Settings
2. Then to Applications
3. Here locate the following FRAMEWORK OF GOOGLE SERVICES:
4. We select Google Services Framework, stop the service, and then delete the data.
5. Then, we locate the service also Google Play, and do the same operation, stop and delete data.
6. After doing this with the two services, reniciamos our Android terminal and will try to download an application from Google Play, we see that already operate normally. Disculpame by Google translation.
chinimen said:
1. In our Android terminal, we go to the Settings
2. Then to Applications
3. Here locate the following FRAMEWORK OF GOOGLE SERVICES:
4. We select Google Services Framework, stop the service, and then delete the data.
5. Then, we locate the service also Google Play, and do the same operation, stop and delete data.
6. After doing this with the two services, reniciamos our Android terminal and will try to download an application from Google Play, we see that already operate normally. Disculpame by Google translation.
Click to expand...
Click to collapse
Did all that on a call from a Google troubleshooter, but still the same error.
Definitely looking to be an issue with my account from some further testing though.
Just created a new account and added my card as a payment method. Tried to make a purchase and it goes through fine.
The only difference with my regular account and the new account is that my regular account has some Google Play Store credit on it from the Opinion Rewards app, and has a fair few devices registered against it.
I'm wondering if it's possible that my account just has 'too many' devices against it, but I can't see any way to actually remove an old device from my account (My old S3 phone seems to be on there 3 times and I now have two Pixel C tablets registered against it)
Removed the new account from the tablet and re-added my original account. If I go to the "My Account" section of the Play Store on the tablet, I get the same error message when it tries to retrieve/display my payment methods. But again, only with my primary account on a new device. My old devices that were already registered can do this no problem. So the issue seems to be that new devices aren't correctly registering against my account, or something along those lines.
https://security.google.com/settings/security/activity?pli=1
chinimen said:
https://security.google.com/settings/security/activity?pli=1
Click to expand...
Click to collapse
I can see my current devices on there, but not the older ones. But I can see the older ones on my Play Store devices list strangely enough.
The device I'm having trouble with is listed on there and doesn't state as having any problems.
I had another callback from Google and the issue is being escalated, so we'll see how it goes.
El goog don't advertise this, and might be reticent at first, but you can get them to delete all your devices (not the same as you account) from 'registered' and then you begin again. Usually you only have a number (4?) you may disconnect every year from the total of 10 (I think).
In your case, I've no doubt they'll do it.
Had this problem too on my Sony Android TV. In my case the problem was a voucher code (and trying to pay with it, paying normally worked fine), I've activated over the chromecast offers page. The google support wasn't able to delete it, but the unredeemable voucher disappeared after a few months.
Hm, will see if I can get Google to remove some devices from my account. There's 8 showing on there at the moment when I go to Settings on the Google Play Web store, 4 of which need to be removed (3 old phones and the first Pixel C tablet), though these don't appear in the Android Device Manager.
I'm also wondering if the issue lies with the Google Credit I have on my account, all of which was earned through the Opinion Rewards app. I'm tempted to try just spending all of it via another device to clear it from the account and see if that sorts things. Even if it doesn't it's only about £8 worth, and it's not like I paid anything for it.
Cracked it.
It was something weird with my account, but also something I could fix.
I downloaded the Firefox browser onto my Pixel C and accessed the Play Store webpage through there, going to the My Account section where my Payment Methods are listed. I noticed that there's a payment method for my mobile carrier that I set up on my old Sony Z2, but was also available on my Nexus 6P. I removed that payment method, then on the Pixel I cleared the Data/Cache for Google Play Framework and Google Play Store apps, then restarted. After that, my Pixel C Play Store app can now access my payment information and make purchases.
No idea if it was removing the carrier payment method that did it since that method was causing some kind of conflict on a non 3G tablet, or if it was accessing the Play Store via a third party browser app which kicked some kind of authentication into gear.
Either way, a very weird issue thankfully solved! I've responded to my Google Support ticket with the update as well, so hopefully they can become aware of a possible issue.