Related
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??
I just wanted to mention an issue that my S8 started having after i upgraded to Oreo. I was unable to make or receive any calls. As soon as i tried to make a call, it immediately ended the call and any incoming call would go straight to voicemail. After playing around with settings, i disabled the Enhanced LTE option and i was able to start making calls again. This setting is only for HD Voice so its not a huge loss. I'm not sure if anyone else has run into this issue but I wanted to mention it to the community. I had tried to reset Network settings and cleared cache to not avail.
I should note, i have not tried to do a factory reset because i was hoping that would be a last resort so its possible that would fix the problem all together but I talked to the tech at the AT&T store and he said he wasn't aware of this issue. If anyone else runs into this issue, feel free to comment.
Matt
lewbrah said:
I just wanted to mention an issue that my S8 started having after i upgraded to Oreo. I was unable to make or receive any calls. As soon as i tried to make a call, it immediately ended the call and any incoming call would go straight to voicemail. After playing around with settings, i disabled the Enhanced LTE option and i was able to start making calls again. This setting is only for HD Voice so its not a huge loss. I'm not sure if anyone else has run into this issue but I wanted to mention it to the community. I had tried to reset Network settings and cleared cache to not avail.
I should note, i have not tried to do a factory reset because i was hoping that would be a last resort so its possible that would fix the problem all together but I talked to the tech at the AT&T store and he said he wasn't aware of this issue. If anyone else runs into this issue, feel free to comment.
Matt
Click to expand...
Click to collapse
I'm in the same boat. Any chance you figured it out? I completed a reset and still have the issue.
Thanks, James
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.
I have this issue where I cannot receive mms messages! Anyone else experience this or have a fix
had the same problem. My APN Settings were not correct. Check & fix these
I reset my APN Settings and have wiped storage / cache for all messaging apps. Anything else I can try?
OP6T on Verizon. I had no issues with texts until Android 10 beta. I did a clean install of the Stable release of Android 10 and still having the same issue receiving mms texts.
My OP6T on Verizon was working fine with Android 9 and Google Messages. I updated to Android 10 during the initial release (before the pause). After that nothing worked for MMS or group SMS until I did a full wipe and reinstall of everything. Now I can get MMS and group SMS, but only with the OnePlus Messages app. Every other messaging app fails to download messages.
I found a fix!
After getting no help from Google or OnePlus, I went back to Verizon and had them get me a brand new SIM card. I'm not sure what changed, the APN settings all look identical to my old one, but it fixed the issue. I can receive MMS on any apps now without any issues. (on 10.0.1 anyway)
Bandalo76 said:
I found a fix!
After getting no help from Google or OnePlus, I went back to Verizon and had them get me a brand new SIM card. I'm not sure what changed, the APN settings all look identical to my old one, but it fixed the issue. I can receive MMS on any apps now without any issues. (on 10.0.1 anyway)
Click to expand...
Click to collapse
Very interesting! I had thought about doing this but kept talking myself out of it.
Going to request a new one now!
THANK YOU! New SIM installed and everything is back to normal! So glad to have Google Messages back!
Glad it worked for you! I just wish I could figure out exactly what the problem was so OnePlus and Google could stop finger pointing at each other.
Well, updated to 10.3.0 this morning, and this issue has returned. Looks like it's back to the OnePlus messaging app.
New sim fixed it for me
Bandalo76 said:
Well, updated to 10.3.0 this morning, and this issue has returned. Looks like it's back to the OnePlus messaging app.
Click to expand...
Click to collapse
I updated to 10.3.0 and MMS stopped working for me as well. I went to Verizon, got a new sim and it started back working. I have a T-mobile converted to International.
emimbs said:
I updated to 10.3.0 and MMS stopped working for me as well. I went to Verizon, got a new sim and it started back working. I have a T-mobile converted to International.
Click to expand...
Click to collapse
I've already replaced this SIM once. I can't go buying a new SIM every time OnePlus updates their software. It bugs me that OnePlus and Google both just point fingers at each other over this problem.
Bandalo76 said:
I've already replaced this SIM once. I can't go buying a new SIM every time OnePlus updates their software. It bugs me that OnePlus and Google both just point fingers at each other over this problem.
Click to expand...
Click to collapse
I had this same issue and had done the same thing to get it working again (got a new SIM from Verizon). After this 10.3.0 update, it came back. I sent a message in to OnePlus yesterday and today I heard back. They asked if I could try clearing system cache. I did, then reinstalled Google Messages, and the issue seems to be resolved. I'm not sure if it's a permanent fix or not, but I'll keep testing it for the time being. I'm interested to see if the issue returns after the next OOS update in January, as clearing the system cache once a month is a workaround, not a fix.
If anyone else tries clearing the system cache, please let me know whether or not it works for you and I'll send on to OP. Here are the directions from the OP rep with a little clarification:
Power off the device
Press and hold volume down + volume up + power buttons
The device will boot into recovery mode or into Fast Boot mode
If it boots into Fast Boot, tap Recovery Mode or use the volume up/down buttons to scroll to Recovery Mode and use the power button to select
If a keyboard pops up, enter your device's PIN/password
Select language
Select Wipe data and cache > Wipe cache
Tap Yes when asked "Cache will be wiped, continue?"
Now Reboot system from "Reboot" option
mason-johnson said:
I had this same issue and had done the same thing to get it working again (got a new SIM from Verizon). After this 10.3.0 update, it came back. I sent a message in to OnePlus yesterday and today I heard back. They asked if I could try clearing system cache. I did, then reinstalled Google Messages, and the issue seems to be resolved. I'm not sure if it's a permanent fix or not, but I'll keep testing it for the time being. I'm interested to see if the issue returns after the next OOS update in January, as clearing the system cache once a month is a workaround, not a fix.
Click to expand...
Click to collapse
Unfortunately, this didn't fix my issue. Uninstalled Messages, rebooted, cleared the cache, rebooted again, then reinstalled Messages, and still can't receive MMS.
Works just fine with OnePlus' messaging app though.
I'm about done with this. A used Pixel 3 XL may be calling my name here soon.
Bandalo76 said:
Unfortunately, this didn't fix my issue. Uninstalled Messages, rebooted, cleared the cache, rebooted again, then reinstalled Messages, and still can't receive MMS.
Works just fine with OnePlus' messaging app though.
I'm about done with this. A used Pixel 3 XL may be calling my name here soon.
Click to expand...
Click to collapse
Just make sure it's a used pixel from google or you will be dealing with a locked bootloader. I myself just switched from a vzw pixel 3xl to the OnePlus 6t. At least I now have the option to try to fix any issues.
mason-johnson said:
I had this same issue and had done the same thing to get it working again (got a new SIM from Verizon). After this 10.3.0 update, it came back. I sent a message in to OnePlus yesterday and today I heard back. They asked if I could try clearing system cache. I did, then reinstalled Google Messages, and the issue seems to be resolved. I'm not sure if it's a permanent fix or not, but I'll keep testing it for the time being. I'm interested to see if the issue returns after the next OOS update in January, as clearing the system cache once a month is a workaround, not a fix.
If anyone else tries clearing the system cache, please let me know whether or not it works for you and I'll send on to OP. Here are the directions from the OP rep with a little clarification:
Power off the device
Press and hold volume down + volume up + power buttons
The device will boot into recovery mode or into Fast Boot mode
If it boots into Fast Boot, tap Recovery Mode or use the volume up/down buttons to scroll to Recovery Mode and use the power button to select
If a keyboard pops up, enter your device's PIN/password
Select language
Select Wipe data and cache > Wipe cache
Tap Yes when asked "Cache will be wiped, continue?"
Now Reboot system from "Reboot" option
Click to expand...
Click to collapse
No luck
Furious this update ****ed things up again. The last thing I want to do is fight the mall and a Verizon store for a new sim, but it appears I have no choice.
Same issues here too after the update to 10.3.0. Worked very well with Android 9. What changed??? I have tried all this as well as adding information for MMS to the APN settings where the MMS data was missing. Nothing has worked. I am headed to Verizon this afternoon to get a new SIM and try that. Both my wife's and my phones are in the same boat. No joy here! Good to know that I am far from the only one. I love my phone though, but annoyed at the lack of support for this so far.
mrmuhles said:
Same issues here too after the update to 10.3.0. Worked very well with Android 9. What changed??? I have tried all this as well as adding information for MMS to the APN settings where the MMS data was missing. Nothing has worked. I am headed to Verizon this afternoon to get a new SIM and try that. Both my wife's and my phones are in the same boat. No joy here! Good to know that I am far from the only one. I love my phone though, but annoyed at the lack of support for this so far.
Click to expand...
Click to collapse
Mine corrected the issue on its own. I'm not sure but messages from Google is working for me. I'm on TMO converted.
New sim and all is well again. Pathetic "fix" but thankfully they're free.
All of a suddennim not getting mms messages in OnePlus messaging app now..
Now what do I do
i fixed this on multiple 7 pros by editing apn from internet to internet.fi
fi because my carrier is finnish.
i myself dont have this issue on my 6t
Hi there,
since the beginning of December I am unable to playback the WhatsApp voice messages I send, not only I cannot play them but the receivers cannot play my messages either.
It was working perfectly before, but suddenly it stopped. I could not find a reason, so I factory reset my phone, reinstalled WhatsApp from scratch, but no go.
When I hit the Play button, it just stays there, the cursor does no move anywhere. I am pretty sure the phone records the messages, but nobody is able to listen to them. The audio settings are correct as well as permissions.
Am I the only one experiencing this issue?
I can only think this is due to an update from WhatsApp that has generated a software conflict with this phone, which is why I would like to know if anybody else is experiencing this problem.
Thank you!
Alex
Anybody?
kwajongen said:
Hi there,
since the beginning of December I am unable to playback the WhatsApp voice messages I send, not only I cannot play them but the receivers cannot play my messages either.
It was working perfectly before, but suddenly it stopped. I could not find a reason, so I factory reset my phone, reinstalled WhatsApp from scratch, but no go.
When I hit the Play button, it just stays there, the cursor does no move anywhere. I am pretty sure the phone records the messages, but nobody is able to listen to them. The audio settings are correct as well as permissions.
Am I the only one experiencing this issue?
I can only think this is due to an update from WhatsApp that has generated a software conflict with this phone, which is why I would like to know if anybody else is experiencing this problem.
Thank you!
Alex
Click to expand...
Click to collapse
My uncle is facing the same issue you mentioned. Tried resetting the phone but no solution so far. Looking for solution.
I spoke to the 'so called' WhatsApp customer support, they are aware of the issue and they said it will be fixed in the future. Mind, this was 6 weeks ago.
I asked for an ETA, they said they have none.
Obviously they do not care about the few Nokia phones around, therefore they will never fix this.
Very disappointing, but there is nothing we can do if their app sucks.
I am facing the same issue. tried clearing the cache, resetting the app, changing to a new phone number, and at the end resetting the whole phone. It just refused. I think it might have something to do with the version of Android. it has Android 9 so I might try to see if there is a good rom with android 11 or 12 and see if that helps.
Any solution? I have this problem fow months. Is possible change the android to another version to fix?