Database Users

Recent issues?

Hey everyone
I got a nexus 5 and using a Galaxy gear live.
I think there was an update the other day to google services and I think since then the watch has been having issues.
I get notifications and everything fine
But when I try to say text my friend Justin
I go OK google. Text Justin mobile. Say my text. It transcript it fine but then says I didn't catch that. And does that every time. I will say hey what's up. It will show that fine in the screen but then all of a sudden it will say didn't catch that
Anyone else having that issue at all?

At least it's not just me then! Same thing started a couple of days ago for me too. Using the LG G Watch R, it now won't "show me my steps", "set a timer for 50 minutes" or acknowledge what I want to say in a message even though it's got it up on the screen. Must be a software bug as I've reset the watch and reinstalled Android Wear on my phone. Still gets my notifications through so it's just a matter of waiting for a patch I suppose.
Weirdly enough, I can't reply to texts (I use Hangouts) but I can dictate replies to Whatsapp messages so it must be a google thing.

I suspect it's a server-side issue as it suddenly happened to a lot of us (though seemingly not all) around the same time. It's similar to how voice dictation of location-based reminders stopped working for some people for a few days a couple of months ago. I do find it alarming, though, that the primary and intended method of interacting with the watch can simply go offline for days on end without a word for Google.
Sent from my Nexus 7 using Tapatalk

Ya. Seems to be working again fine without issues now. Was odd

c_86 said:
Ya. Seems to be working again fine without issues now. Was odd
Click to expand...
Click to collapse
Unfortunately it still doesn't work for me. Really frustrating

Yesterday's Android Wear app update has solved the "show me my steps" issue but texting is still out of action.

[Q] Push notifications only work on wifi

I have a sprint galaxy s5. Ive had this problem for about a month and the only thing i havent tried is coming here. The push notifications are not coming through on any app unless the phone is on wifi or i leave an app running on the screen while im away. Ive check all the settings, had sprint look on their side, factory reset, took it to a sprint store, and than had it replaced with another S5. After the first day with the new phone it worked fine until i went to sleep and it updated to 4.4.4 over night. The following day the same problem, no push notifications on data. I went to a samsung video chat and they said it was a bug and wait for the 5.0 update. Well......its here and im still waiting for my friends test email and facebook message to come through.
Any thoughts would be very much appreciated.

Bump

If you're rooted maybe this app https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer
could fix your issues. There is an app for non rooted devices too, but I doubt that it works as good.

I'm not rooted and tried the other app you recommended with no luck. I decided since the 5.0 update came through to factory reset the phone. I sent a test to my gmail and installed whatsapp to see if notifications would come through and I've had no luck. Looks like another trip to the sprint store for another phone.

NoahMayes said:
I'm not rooted and tried the other app you recommended with no luck. I decided since the 5.0 update came through to factory reset the phone. I sent a test to my gmail and installed whatsapp to see if notifications would come through and I've had no luck. Looks like another trip to the sprint store for another phone.
Click to expand...
Click to collapse
Maybe you have Restrict Background Data checked. It wont give any notifications on Sim network till the app is open. Did you check this out? Push notifications are coming easy on the WiFi and not on mobile data.

I have tried the restrict background data, toggling it on and off and I also checked data usage for apps and none are restricted. Everything is fine on wifi but not on data, app has to be running on the screen to update if i'm not connected to a wifi. I've looked through different forums and many reported the issue fixed because the APN needed changed, but Sprint will not let me configure it. I've been through their tech team and everything seem right on their end.

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

Bricked Nokia 6 after February update, anyone else?

Hi,
I updated my Nokia 6 early yesterday morning, February 21st. The update was 1,7GB in total, don't know what it consisted of. The update came to my phone through standard automated update check, I got a notification to connect to WiFi, I did, the update downloaded and installed.
Apparently, it was the Android Pie update, though I didn't look that closely.
So, 100% stock ROM, no mods, fully official update method. No tricks. Connected to wall, 100% battery.
After the update the phone booted and asked to reboot to install operator updates. I'm not quite sure the exact wording of the message pop-up, but that's what it asked as far as I can remember. I agreed to reboot, the phone shut down, and never came back to life again.
It won't respond to any key presses. It's completely bricked.
I'm going to get it fixed in a shop, where it'll go to have its display changed anyway. I'm writing this here to ask, has anyone else had troubles with the update? It was rolled out in Finland apparently February 21st or 20th, or then I haven't reacted to the notification before. I'm quite unhappy with the state of the matters, since it seems to be the official update that bricked my phone.
So, anyone had any troubles with Android Pie update?

Mine bricked 2 days ago after the same Android pie update, 1.7 GB. I have tried flashing to no avail. Currently looking for ways to restore a bricked Nokia 6 TA-1021.

rwaithera said:
Mine bricked 2 days ago after the same Android pie update, 1.7 GB. I have tried flashing to no avail. Currently looking for ways to restore a bricked Nokia 6 TA-1021.
Click to expand...
Click to collapse
According to the service personnel, a small wonder happened when they plugged in my TA-1021 - the device started right up. It's quite extraordinary claim, since my phone was connected to my charger when it shut down, and it was showing 100% battery.
I have no reason for this, only speculation. The only explanation I can come up with outside of some divine intervention is, that the phone did not shut down after all. Instead, it was stuck on some loop with screen off and buttons inoperative. When it finally ran out of battery, it responded right away when it received more power.
I did not try and flash my phone myself. Nor did they flash it in the shop. It wasn't necessary, the phone is now fully functional.
Maybe try to plug it in briefly and see what happens. If nothing, then just unplug it again and try another time tomorrow. Btw. HMD Global's chat support was very responsive, so I highly recommend contacting them if you suspect that your case was caused by the updater itself.

Mine didn't get bricked, but it started having issues with Google accounts. After the update, all apps which use my Google account to login had login errors & I couldn't add Google accounts onto the device. I manually synced the account, removed the account & tried to add it again (shows a "sorry something went wrong" message everytime I try to add an account), wiped the cache, even factory reset it, but nothing helped. I finally had to spend some time learning how to downgrade it & was able to add accounts on the device again. But after I updated my device with Android 9 (V6.12) again, the issue came back.

my all google apps arent working on TA-1000

mine is completely bricked. wont turn on at all. TA-1033.
Is there anyway to fix this?

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.