Error 505 when updating Amazon apps - Droid Turbo 2 Q&A, Help & Troubleshooting

Since updating to Marshmallow, the Amazon, Kindle, and Amazon Music apps will not update on my Turbo 2. I get an Error 505 message when attempting to do so. I have tried clearing the data for each and disabling then enabling, but nothing has worked. Has anyone else had this problem and/or know of a fix?

g0thm0g said:
Since updating to Marshmallow, the Amazon, Kindle, and Amazon Music apps will not update on my Turbo 2. I get an Error 505 message when attempting to do so. I have tried clearing the data for each and disabling then enabling, but nothing has worked. Has anyone else had this problem and/or know of a fix?
Click to expand...
Click to collapse
https://forums.lenovo.com/t5/DROID-...Amazon-apps-after-MM-update/m-p/3283077#M3925
Take a look at what fixed this. It's from the Motorola Turbo 2 forums and is what I used to fix my same issue.

Related

Google Now gives error "Network error. Check your network connections and try again."

Google Now gives error "Network error. Check your network connections and try again."
UPDATE: FIXED, check comment below!
So, you may have heard of this error before, I got it randomly today for no reason while trying to use Google Now on Tap, so I tried uninstalling updates for Google Play Services etc. and it just resulted in me having to re-enable Google Now Cards blah blah blah, which wouldn't work and kept saying the error and doing nothing.
After spamming to opt-in to Google Now (after a fresh reset of the phone), it eventually let me, and I spammed refresh in the Google App and it eventually refreshed, but 9/10 times it will just fail with that error.
What do I do? This is seriously annoying and I use Google Now for so much crap nowadays, it's hard to live without now...
I've tried resetting, it seems to be an account related issue from the research I've done so far, reading up about other people's attempts to fix it etc.
Thanks in advance guys, I appreciate it.
I'm on a Nexus 6P running Android 6.0.1 and it's not rooted.
-Andrew
12 hours later and it fixed itself...
Such a weird error.
Oh well!

Play Store - Waiting for Network

I've got the A2017U with the stock Nougat update. Unlocked bootloader, but not rooted. I got through the Verizon quirks, and seem to have voice and data connected again. Doesn't look like I'm connected to LTE though. Phone information only shows CDMA/EVDO information, and Voice Network is 1xRTT.
I can get by with that for now. My main concern is that I'm having trouble in the Play Store. Background app updates seem to be working, but when I manually try to update, or install a new application, I get Waiting for Network.
I tried clearing data and cache from the Play Store and Download Manager applications. That didn't help. I disabled the Play Store, and it reverts back to what they call the "factory version". I can then quickly update or get an application before the Play Store updates itself which gives me that error again.
I saw a thread on this on a Sprint message board from a few years ago, but the solution was to wait for an update sent from Sprint.
Anyone else see this issue?
Thanks,
Paul
I just started seeing this today. No idea what caused it. I tried installing a new app over 4G and it got stuck on "Waiting for network" even though I was connected to the internet with browsing, Inbox, Hangouts and Whatsapp all working fine. I connected to wifi and same issue. Cleared cache and data, rebooted and same issue on both 4G/wifi.
Thanks for your suggestion about disabling and enabling as I now have my new app installed and other apps updated.
Recently I've noticed some bugs with the 7.1.1 update relating to mobile data. Stops working randomly and the signal icon keeps losing the "4G LTE" portion even if I'm connected.
jimmygoska said:
I just started seeing this today. No idea what caused it. I tried installing a new app over 4G and it got stuck on "Waiting for network" even though I was connected to the internet with browsing, Inbox, Hangouts and Whatsapp all working fine. I connected to wifi and same issue. Cleared cache and data, rebooted and same issue on both 4G/wifi.
Thanks for your suggestion about disabling and enabling as I now have my new app installed and other apps updated.
Recently I've noticed some bugs with the 7.1.1 update relating to mobile data. Stops working randomly and the signal icon keeps losing the "4G LTE" portion even if I'm connected.
Click to expand...
Click to collapse
I have the same problem which I noticed this morning. Tried all suggestion about clearing data, cache, etc. but nothing worked. Hoping someone has a fix.
I am having this problem as well. Thought it had to do with me switching carriers today but apparently not. Hopefully a fix is released soon.
I'm also having this issue today. I'm on Verizon. Everything else seems to work. But, even on WiFi I can't get anything from the play store.
Edit:. Disabling the play store and then renabling it (reverting back to previous version) fixed the issue for now.
I just came here to post the same question?? Just noticed it about 30 minutes ago.
[EDIT] I disabled and rolled back to the previous version, still didn't work for me. I also updated to the newest one (from March 6th) I found here on XDA, still didn't work.
Disabling and reverting the Play Store worked for me. Stock install on Cricket running 7.1.1 in the USA.
It started working again about an hour ago?
[UPDATE]
Woke up this morning, not working again.
I've rolled back, tried other versions, nothing works for me.
still same on me. tried wipe data, deactivate and activate bla bla. still same.
Go on your mobile to apps and then google play store, then choose uninstall updates, it will revert back to the old app store, and then it should work again.
Been having this SAME as exact problem since Nougat. My phone is completely STOCK though.
Everything I've tried is just a temporary fix. after play store updates automatically the problem happens again and I can't download anything. Updates happen randomly when my phone is sleep.
Very annoying
Got the same problem here in Thailand with the G model.
Revert the play market to inițial version and all will be ok. This problem îs from Google
danct2005 said:
Revert the play market to inițial version and all will be ok. This problem îs from Google
Click to expand...
Click to collapse
That worked for a while, but trying again this morning has no effect.
Me 2 I'm running 7.1.1 on Chinese version A2017. And today the same problem showed.
emmecinque said:
That worked for a while, but trying again this morning has no effect.
Click to expand...
Click to collapse
Also the problem is not happening on other phones in my same local network. The problem is specific to the Axon 7 (well I guess possibly others too, but not other phones I have.)
---------- Post added at 08:32 AM ---------- Previous post was at 07:45 AM ----------
emmecinque said:
Also the problem is not happening on other phones in my same local network. The problem is specific to the Axon 7 (well I guess possibly others too, but not other phones I have.)
Click to expand...
Click to collapse
OK based on some information in a similar thread on the ZTE forums, I think the deal is this: going (via Settings - Apps) to the Google Play app, and then clicking the upper-right "three dot" menu to get the "Uninstall Updates" option allows you to revert back to an older revision (7.2.13). That revision works.
The problem is that, in the background, something really wants to keep the Play app up to date. If you're not quick enough to get it open and start downloading, you'll be back to the bad update.
Same issue "Waiting for network" hit my A7 last night out of the blue. On AT&T network. All other Android devices in house use GP Store with no issues. Been on Nougat since day one with pretty much no issues.
No idea why this happened. Quite frustrating.
Have you tried going to Settings/Apps, select Google Play Store, go to Storage (or similar, I have a non-english phone) and clear the cache there? This solved the same issue on my phone. It's strange that clearing the cache didn't help in other instances.
I started running into this last night with my Azon 7, too. Stock 7.1.1, T-Mobile, also tried on wifi. Clearing the Play store cache didn't help. Uninstalling updates for the Play store works briefly, then I get the same error (presumably because the updates to the store have reinstalled), and I have to uninstall Play store updates again to update again.
I've tried the cache trick, the uninstall tricks, nothing works long term. I'm stumped as to why we all started seeing this happen around the same time. What changed to trigger it??

Asus Zenpad 8.0 Z380M Android Issue

Hey everyone,
This is actually my parents tablet so I'm not entirely sure what happened. They told me it was updated and it looks like a factory reset was performed. It prompts for the account associated with the tablet and I used my mom's email/pass and it says "There is an unexpected error. Try again in 24 hours". I've waited multiple days multiple times and still get the same error. When I try a different login, it says I need to use the account that was previously being used. I tested my mom's credentials elsewhere and they were fine.
It's out of warranty from Asus now and I couldn't find much info online.
Am I SOL? Can I load a new ROM on to it to fix this issue?
Any advice would be greatly appreciated.
Thanks!
drakore said:
Hey everyone,
This is actually my parents tablet so I'm not entirely sure what happened. They told me it was updated and it looks like a factory reset was performed. It prompts for the account associated with the tablet and I used my mom's email/pass and it says "There is an unexpected error. Try again in 24 hours". I've waited multiple days multiple times and still get the same error. When I try a different login, it says I need to use the account that was previously being used. I tested my mom's credentials elsewhere and they were fine.
It's out of warranty from Asus now and I couldn't find much info online.
Am I SOL? Can I load a new ROM on to it to fix this issue?
Any advice would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
This sounds like an error with GOOGLE NOT THE OS. There must be something about errors like this on other devices.
P.S. sorry about the capitals, it just makes the most important part easily readable

Strange Sync/Download Issues on Multiple OP 6T Handsets

Hello all.
I ordered a OnePlus 6T (non-T-Mobile, 128 GB, 8 GB RAM) on launch day, which I received last week.
Once I logged in with my Google account and started trying to download apps, I noticed that it was taking forever to even start the download from the play store (it says "downloading" but the progress bar does not appear, and then maybe 45-60 seconds later it starts downloading the app). Once the actual download starts, the speed seems about normal. It also takes it forever to load images within the play store and to sync my Gmail account. Push notifications are also delayed for gmail and hangouts, if they ever appear at all.
I did multiple factory resets and OP tech support remotely flashed a fresh factory rom for me, but this didn't help the problem. I returned the device and ordered another, which I just got today. I'm having the same exact problems, which seem bizarre to me since I haven't been able to find anything online suggesting this is a common bug, even though I've now experienced it on two handsets.
A related little glitch I noticed, I'm on T-Mobile, and when I have VoLTE and WiFi calling enabled, Hangouts crashes whenever I enter any text in a message field.
It seems to me the phone is having some issue syncing/connecting with Google's play services/servers. I've tried restarting and clearing the cache on both Google Play Services and the Play Store, both of which I've also verified are up to date. My OS is up to date as well. I have recreated the problem on multiple Wi-Fi networks as well as over cellular data.
Does anyone have any insight into what might be causing this? I really like the phone aside from this major issue...

System Phone App broken after T-Mob OTA 9.0.2?

Is anyone else with a T-Mob 6T have an issue with dialing out calls? Phone got a small OTA and updated the SYSTEM Phone app from the play store and then just broke. Can't swipe to contacts from inside the app, causes it to crash and crash and force stop. Thank God have Google contacts on as a backup. But even from dialing out from Google contacts it takes up to 7 tries to get a call to actually dial. Typically I need to do a full power down and up to get a call to go out. I have no mods yet on the phone, just unlocked from T-Mob I didn't even flash my unlock token yet since this began. Was going to this past weekend until this happened and I wanted to make sure I had no issues before going forward with twrp and magisk. First time poster been waiting a long time to finally get my feet wet here, probably won't answer until am EST since I have work early.
Thank you and hope this post wasn't a big ramble.
It's fixed. No OTA update from T-Mobile. Guessing it was on Google's end. Clear Play Store cache/data. I can confirm now through SafetyNet Test, the 6T passed. Yesterday it did not, and clearing the cache/data did not work. Today it does. I'm getting app updates now as I type.
JDM9499 said:
It's fixed. No OTA update from T-Mobile. Guessing it was on Google's end. Clear Play Store cache/data. I can confirm now through SafetyNet Test, the 6T passed. Yesterday it did not, and clearing the cache/data did not work. Today it does. I'm getting app updates now as I type.
Click to expand...
Click to collapse
Ok well calling is working so far but still crashes when I swipe to contacts. Tried clearing all caches also. Weird stuff and my phone passes safetynet. Will update if I can find a work around or a way to make it work again.
Try uninstalling the built-in Visual Voicemail app and installing the one from the Play Store. Someone reported that cured their phone app crash issue.

Categories

Resources