Database Users

[HELP] Group messaging (MMS) issues

I want to start off by saying I have 1 or 2 group messages that go on throughout the whole day, every day. When I first got the Verizon S7 edge, I had zero issues for the first three days. All of the sudden, at least once a day, there is an issue receiving and sending group messages. I can't link it to anything specific besides it happening most when the group chat is most active. 11 people in the chat are sending multiple messages at a time and then I'll send a message at the same time and i realize mine is not sending and then I stop receiving everyone else's messages. If I go to the individual participants chat in my texting app, there will be a bunch of messages that are downloading. This has happened to me in the past with other phones, but its usually linked to having bad service at a certain time and simply turning mobile data on and off will fix the issue. I cant link it to anything this time, it happens randomly. It doesn't matter where I am, if I have 1 bar or 4 bars, if wifi is on/off, bluetooth is on/off. The messages eventually start coming in, but I dont know what causes that to happen either. I could restart the phone 4 times before it helps. The only thing I can say is it happens most often when the group chat is most active. I'll also mention that this wasn't an issue in the first 3-5 days of using the phone. Below are the steps I've already taken to try and resolve the issue.
1. Wifi on/off
2. Mobile data on/off
3. Restarting the phone
4. Tried 4 different texting apps - Hangouts, google messenger, samsung messenger, verizon messenger
5. Factory reset
6. New SIM card
7. Swapped the phone out for a brand new one. Issue started again with the new one after 3-5 days.
8. Enabled every app that was disabled
9. Activated/deactivated advanced calling
10. Called Verizon tech support - We replicated the issue and thought it was due to "delete old messages" being turned on in the settings. Tech support thought the phone was trying to delete old messages at the same time I was receiving a bunch of texts and everything would get stuck. Everything seemed fine after changing that, but it happened again a few hours later.
11. I've run out of options
I had the Note 5 before this and had zero issues with that phone and I've never had an Iphone.
Please help

Use textra app from play store
Follow me on Twitter @bash_array

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??

Factory reset my X727, now Google Services arent working correctly?

I received my phone a few days ago brand new, updated the firmware to 21s, and experienced an overheating issue so I thought doing a factory reset may help before trying to return it possibly for a new one.
However, once I reset the phone, I cant seem to get my google account to sync properly anymore.
The play store doesnt show any of my installed apps and doesnt show that any of my apps need updates either, though if I manually search for the app in the store, it will allow me to update it that way. Syncing my google apps like mail etc seem to be very slow, and I usually have to manually refresh to get new mail.
The biggest issue though is the play store is trying to charge me for every app Ive ever purchased. If I go into settings then purchase history in the play store app, I can see the list of all the apps Ive ever purchased and what I paid for them. When I click the view link which takes me to that app, its showing full price and tries to get me to pay for it. The only workaround I have found is going to the website store, and choosing to manually download the paid app to the phone which seems to work.
Ive tried everything I can think of to fix this. I made sure the google play store and google play services had the latest version. Ive gone into all the google apps and cleared the data and rebooted. Ive tried removing my google account from the phone settings and Ive factory reset my phone three more times and the issue persists.
I have contacted Google support multiple times over 4 -5 hours yesterday which was a nightmare and the reps are extremely unhelpful trying to tell me I must be doing something wrong like logging in with a different account or that the problem lies with the developers of the apps and I need to contact them directly (like I need to contact 100 different app developers to see why theyre trying to charge me for apps again...?) Ive tried telling them I can still access all my paid apps on my old phone and the web browser shows all my purchases as well.
The only thing I can think of is some Google config file or something is remaining on the phone between factory resets which is causing the phone not to connect fully with Google services. The phone isnt rooted, I didnt want to do that in case I had to return the phone due to the overheat issue I had.
Anyone have any possible idea what is causing this? Prior to doing the first factory reset, all my google services worked fine. It was only after doing the first reset I ran into this issue and Google has no clue whats going on and it doesnt help the reps that contact me usually reply with general troubleshooting that has nothing to do with my issue

The paid apps now showing up as paid was definitely a bug i encountered when I first got the phone. I don't quite remember how I solved it. I think I may have just uninstalled/reinstalled google play services and rebooted a few times. After a few hours, every app was showing up properly. I wouldn't bother contacting the app devs or google again, it's definitely something that can be solved by messing with the phone.

I believe the cause of this was the version of the Google play store. It happened to me the first time I set the phone up. I've sideloaded a newer version of the play store and then it behaves like normal.

Notifications are cut short / completely broken on some apps.

First time poster here, I recently bought a Galaxy S8 after I became tired of my iPhone and boy, do I love this phone. I have never had so much fun with a mobile device.
My phone is only a week old and was working perfectly until a couple of days ago - one evening, I was messaging a friend on Discord when suddenly the notifications started getting cut short and not showing up in the AOD/notification centre. My notification sound would only play for like a split second, the Discord logo would appear in the status bar for a split second, and then the sound would suddenly stop and the notification was not able to be found in my notification centre. Discord had not received an update, and I had not (knowingly) changed any settings, so I had no idea what had caused it.
Now, I get this with Google Allo as well. And Telegram. And my Twitter DM notifications have straight up stopped working, they don't even make a sound or appear for a split second. I have no idea what has caused this, I've tried reinstalling all of these apps, force stopping them, ensuring that they are not put to sleep in the device manager, etc...but nothing seems to be working. It seems to be getting worse and worse, as initially I only encountered this issue with Discord, but now it's with all of these apps - Snapchat, WhatsApp and Messages are now the only apps on which I receive notifications reliably (for now).
I posted a thread on the /r/galaxys8 subreddit discussing this and found that other users shared the same issue, and even found another thread posted by somebody having the same issues with Google Allo, but nobody has a solution. Is there anything that you guys can recommend? I'm willing to try anything, I'm just extremely hesitant to factory reset my phone as I've finally got it set up how I want it and I really don't want to have to start over.
Thanks!

Android 10 Share Crash

I just got the OTA update from AT&T for my V35 to Android 10. Now, whenever I try to Share from an app and the system Share panel is invoked, the Share panel starts to populate and then crashes and often takes the app with it. The only app that I can Share from now appears to be Firefox, but that doesn't appear to use the system Share but has its own.
Any ideas what could be going on? This is happening for my and my wife's phones (both V35). I contacted AT&T chat support and all they gave me was canned answers and then ended the chat; useless.
UPDATE 1: I found the problem with both phones is GroupMe. On the one phone I was able to get things working again by clearing the cache and data for GroupMe, uninstalling it, reinstalling it, and logging back in. For the other phone, this didn't work. I can Share when GroupMe isn't logged in, but once I log in, the Share crashes while populating. The only difference between the working phone and broken phone is that the working phone has a GroupMe account linked with Microsoft and the non-working phone has its GroupMe account linked with Google. So, it appears that a Google-account-GroupMe + Android 10 + Share is the broken combination. Now I'm really at a loss here.
UPDATE 2: Apparently I'm not the only one: https://www.reddit.com/r/AndroidQue...e_causing_android_system_share_menu_to_crash/
UPDATE 3: While GroupMe logged in with Microsoft was allowing Share to work on my phone for a while, Share has since stopped working while I'm logged into GroupMe. When I delete the data for GroupMe, I can share again. I've emailed GroupMe support about this matter and will report back. I'm currently running the latest version of GroupMe from the Play store: 5.47.4, released May 19, 2020
UPDATE 4: I've chatted with AT&T support a few more times. The first time was with Oliver, and that didn't go very well. I did manage to get a case number though. I was told that update V350AWM20i would be pushed to my phone in the next 24 hours which would fix the issue; I already have V350AWM30c, which is newer. I then spoke with Mike in a second chat session (which I started because Oliver hung up on me) and was told that my case has been escalated and I should at least hear back from AT&T in 24 hours. I'll keep updating this.
For sure GroupMe shouldn't be causing Android to crash, but Android shouldn't crash because of a bad app. IMO, both parties are at fault here.
UPDATE 5: I contacted AT&T today (they didn't contact me as they said they would) and they now say that I'll have a resolution by the 27th. GroupMe hasn't returned my request for support.
UPDATE 6: I contacted AT&T yesterday, the 26th, and they said that an update that would be pushed to my phone to fix the problem. They didn't know the version of the update that would be pushed. The update never came. Today, the 27th, I contacted AT&T again and they said that my case was closed and the the update was pushed. They said they pushed the latest version of Android Pie to my phone. So, here we go again. They decided they would re-open the case and would investigate my issue. For some reason they were under the impression that I opened a support ticket to get an update to Android 10. No one that I spoke with today could even tell me what my issue was, even after they read this post. I was transferred to another support agent where I sat for about an hour before quitting the chat. I only saw "Agent is typing..." and "Agent stopped typing" once, after about 45 minutes, but no actual interaction from the agent.
In other news, GroupMe has started replying to my request for support and apparently they can't open x265-encoded videos of a screen recording I took of the problem that they requested. I've sent them an x264-encoded screen recording to see where this goes.
UPDATE 7: I ended up calling AT&T support (866-344-6217) and spoke with a very helpful person who was able to correctly identify the problem and is escalating it to others, possibly LG, to see if the problem can be addressed. A remote control session was done with my phone where the problem was clearly reproduced. Such was the case even after clearing various cache and data for the app, web view, and system. I was informed that the problem will likely be solved by a hard reset of my phone. Apart from the obvious reason why I don't want to do that, the fact that this affects two of my phones the same indicates that it is an endemic software problem that should be addressed less this roll-out causes more problems for others. Since my phone has such a reliable reproduction and I need to schedule time to reset my phone, I'm holding off on doing this until I hear back about the escalations that AT&T is taking, which I'm expecting today, the 28th based on our conversation.
If anyone knows how to contact LG on this matter, or even AOSP, I'm all ears. It still should never be the case that a logged-in app should be able to crash the Share function in Android.
UPDATE 8: I just (8:49 am CST, May 28th) received a text message from AT&T saying that they were closing my "Urgent Case"; I was never called to inquire if my issue was resolved. Hopefully I'll still get the phone call I was promised later today.
UPDATE 9: I heard back from AT&T and they continue to work the issue. For reference, the model of my device is LM-V350AWM and it is SIM unlocked.
UPDATE 10: Microsoft GroupMe released an update to version 5.47.5 today which resolved the problem on my wife's phone. Thus, there are two solutions to this problem: 1) the comment below about turning off and on "Direct Share", and 2) installing the update for GroupMe. The reason why any installed app could cause the Android system to crash is still beyond me and hopefully is something that AT&T, Google, and LG can work out.

This happened to me last nite. I'm still on 9. Drove me cray untill I rebooted. Now I have some random app stop pop-ups, but sharing is fine.
Sent from my LM-V350ULM using Tapatalk

I had a similar issue. I had to disable the "direct share" and "nearby devices" under settings > network > sharing panel.
Oddly enough after verifying this fixed my issue I was able to re-enable them and sharing was still working.

wizardofwoz said:
I had a similar issue. I had to disable the "direct share" and "nearby devices" under settings > network > sharing panel.
Oddly enough after verifying this fixed my issue I was able to re-enable them and sharing was still working.
Click to expand...
Click to collapse
This absolutely worked. I'll continue watching to see if the problem returns as GroupMe contacts work their way back into my Direct Share list. I do find it strange this came up after the upgrade. It seems that the upgrade process didn't reset/flush something related to the list of contacts related to GroupMe.