Related
I have a Tmobile G2 that I just got a week ago. I played around with it for a couple days before deciding to root it, but finally pulled the trigger. Two days after rooting it a very strange thing happened. In the middle of the evening some of my Google applications stopped syncing. Gmail, Voice, and Contacts stopped. Drive still worked. Hangouts still worked... It was just weird. I clicked around for awhile and hit the interwebs to find the solution or to see if there was some widespread google outage again, but nothing.
I did everything I could think of, and then I finally clicked the option to take the phone back to stock. I know it wasn't going to take away my root, but at this point I wasn't thinking root was the problem. I just thought maybe I installed something that messed up the phone or something. Anyway, I took it back to normal and now the problem was weirder. It wouldn't even let me connect my Google account (or any google account) to the phone. It kept saying there was some sort of server error. I called TMO support and they couldn't figure it out either. They gave me a number to call Google support to let them fix it. They said that this was a 'known issue' and google support would be the one to fix it.
I kind of got nervous that they were going to creep into my phone or something and void my warranty. If my phone was broken and wouldn't connect to Google anymore then I at least wanted to be able to return it to the store and get a new one. I kinda like this device. So I un-rooted it and took it way back to stock. That fixed the problem. I don't know why, but it did. It left SU on the phone, so I'll have to get that off if it has issues again, but for now it is working fine.
Any idea why it would have just suddenly stopped connecting to Google? It connected to Drive just fine and several other apps, but the important ones wouldn't work. Unrooting it did the trick, but that would suck if you have a really great setup built. Oh well... The price you pay for being a hacker I guess.
ocdetails said:
I have a Tmobile G2 that I just got a week ago. I played around with it for a couple days before deciding to root it, but finally pulled the trigger. Two days after rooting it a very strange thing happened. In the middle of the evening some of my Google applications stopped syncing. Gmail, Voice, and Contacts stopped. Drive still worked. Hangouts still worked... It was just weird. I clicked around for awhile and hit the interwebs to find the solution or to see if there was some widespread google outage again, but nothing.
I did everything I could think of, and then I finally clicked the option to take the phone back to stock. I know it wasn't going to take away my root, but at this point I wasn't thinking root was the problem. I just thought maybe I installed something that messed up the phone or something. Anyway, I took it back to normal and now the problem was weirder. It wouldn't even let me connect my Google account (or any google account) to the phone. It kept saying there was some sort of server error. I called TMO support and they couldn't figure it out either. They gave me a number to call Google support to let them fix it. They said that this was a 'known issue' and google support would be the one to fix it.
I kind of got nervous that they were going to creep into my phone or something and void my warranty. If my phone was broken and wouldn't connect to Google anymore then I at least wanted to be able to return it to the store and get a new one. I kinda like this device. So I un-rooted it and took it way back to stock. That fixed the problem. I don't know why, but it did. It left SU on the phone, so I'll have to get that off if it has issues again, but for now it is working fine.
Any idea why it would have just suddenly stopped connecting to Google? It connected to Drive just fine and several other apps, but the important ones wouldn't work. Unrooting it did the trick, but that would suck if you have a really great setup built. Oh well... The price you pay for being a hacker I guess.
Click to expand...
Click to collapse
Google had problems with their servers, many services were unavailable... had most probably nothing to do with you rooting...
You just picked the right time to do that.
Google from time to time have some problems. But not related to rooting.
PAGOT said:
Google had problems with their servers, many services were unavailable... had most probably nothing to do with you rooting...
You just picked the right time to do that.
Google from time to time have some problems. But not related to rooting.
Click to expand...
Click to collapse
That's kind of what I thought, but it was miraculously healed when I unrooted it. It could have just been strange timing, but there was nothing on the web about anybody else having this issue. I'll root it again and see what happens. There are some definite advantages to root access that I don't want to lose, but getting my email and texts are pretty important too, so....
ocdetails said:
That's kind of what I thought, but it was miraculously healed when I unrooted it. It could have just been strange timing, but there was nothing on the web about anybody else having this issue. I'll root it again and see what happens. There are some definite advantages to root access that I don't want to lose, but getting my email and texts are pretty important too, so....
Click to expand...
Click to collapse
Seriously??? The web was full of it ...
read here for example http://techcrunch.com/2014/01/24/gm...mails-to-be-sent-to-one-mans-hotmail-account/
http://techcrunch.com/2014/01/24/gmail-goes-down-across-the-world/
PAGOT said:
Seriously??? The web was full of it ...
read here for example http://techcrunch.com/2014/01/24/gm...mails-to-be-sent-to-one-mans-hotmail-account/
http://techcrunch.com/2014/01/24/gmail-goes-down-across-the-world/
Click to expand...
Click to collapse
I'm talking about this past Saturday morning, though. February 1st. I know about the google issue a week or two ago, but this was only affecting my mobile apps and wasn't the same thing. I was able to access gmail on the computer just fine. I could even access it from the phone's browser fine, but connecting the Google account to the phone was not possible. All I kept getting was 'cannot make a reliable connection to the server' error, so that is why I took the phone back to stock and then all the way back to unrooted. Unrooting it solved it, so I don't think it was just a google server issue which only affected me between the hours of 7:30 on Friday night till Saturday afternoon when I finally gave up and unrooted. It could have been connected, but I doubt it.
Which rooting guide did you follow?
Sent from my LG-D802 using Tapatalk
ocdetails said:
I'm talking about this past Saturday morning, though. February 1st. I know about the google issue a week or two ago, but this was only affecting my mobile apps and wasn't the same thing. I was able to access gmail on the computer just fine. I could even access it from the phone's browser fine, but connecting the Google account to the phone was not possible. All I kept getting was 'cannot make a reliable connection to the server' error, so that is why I took the phone back to stock and then all the way back to unrooted. Unrooting it solved it, so I don't think it was just a google server issue which only affected me between the hours of 7:30 on Friday night till Saturday afternoon when I finally gave up and unrooted. It could have been connected, but I doubt it.
Click to expand...
Click to collapse
I'm having the same problem. I deleted my account and recreated it. But auto-sync does not work. This has nothing to do with syncing. That works - but I have to sync manually. If I manually sync it from either the app or from the accounts option in settings it works fine. But it won't sync again. I deleted the account, restarted the phone and added the account again. Still doesn't work. If you root it and run into the same problem, please post again. I'll unroot too then.
I know this used to work at some point. I don't know when it stopped working. But it's not been working for days now.
mrm43 said:
Which rooting guide did you follow?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I don't recall. The root part worked fine. I was able to use several of my apps which require root access and they all worked fine for a couple days. It just seems really random that this would all stop working one day.
So here is the timeline.....
Monday 1/27/14 - phone arrives
Wednesday - Rooted
Friday evening - Strange sync issues
Saturday morning - restored to stock while keeping root (did not solve problem and now I cannot connect any google account)
Saturday afternoon - unrooted and restored device (solved problem and google account synced fine after)
That was all in the same week. I've only had the phone since last Monday. It is worth saying that my HTC G2 and my wife's HTC G2 didn't have any issues with google syncing during this time. Totally different products, but I really tried to find anything to link the problem to something systemic and not just a device issue.
I haven't rooted it again just yet. I need to do it before I go too nuts re-installing the apks on my machine anyway. I'll definitely post again if I have problems again, but I really want to believe it was just something left over from whatever bug plagued Google a couple weeks ago.
Wi-Fi Calling is not working at all on my stock s7. Is anyone else experiencing this? Getting enablement error. Spoke with sprint tech support who is stumped and now escalating up to higher level team.
Rest of phone (including wifi and hotspot/tethering) working as it should.
Saw one post about disabling Bluetooth and BT share. tried that with no improvement.
-Josh
What kind of testing would help?
I have never used this before, so keep it simple, lol
I have the same problem. . They told me, after escalating, that it was am account code error. . I am trying now to enable. . Update it works now after whatever account coding they updated
cwb1231 said:
I have the same problem. . They told me, after escalating, that it was am account code error. . I am trying now to enable. . Update it works now after whatever account coding they updated
Click to expand...
Click to collapse
That sounds promising.They have called me three times to keep escalating. Any chance you would PM me your #. I can ask them to look at your acct to figure out how to fix mine.
Also if you have air rave try turning that off
cwb1231 said:
Also if you have air rave try turning that off
Click to expand...
Click to collapse
I didn't have any problem with the Airrave and my S5 using Wi-Fi calling.
I think I had to do that sometimes because the phone was trying to use both or maybe just to eliminate that possibility
Anyone have a solution for broken Wifi calling. I tried everything I could find including calling Sprint. Running the latest Sprint S7 update, was working before the phone updated. Really not looking forward to do a hard reset.
It's a problem with the data code on your account.Will need tech suport to fix. They are having issues with s7 not carrying code over correctly.
Thanks for the feedback, do you mean my Data plan is not correctly assigned to my phone. Ill probably have to hold the Sprint tech supports hand to get it going.
No its the actual billing codes for your account and how wifi is coded on it.
No luck, was on the phone with Sprint for almost an hour. They made a Ticket, said said I needed to take my phone to a repair center
I have to tell you after the security update it reset my pattern lock and i ended up with factory reset because the Samsung website unlock feature isn't set up for the s7. Had to use Google website and my Google account to restet. Good luck
cwb1231 said:
I have to tell you after the security update it reset my pattern lock and i ended up with factory reset because the Samsung website unlock feature isn't set up for the s7. Had to use Google website and my Google account to restet. Good luck
Click to expand...
Click to collapse
I know what you mean. Luckily I had fingerprint unlock working cause my pin unlock broke after the update. Hoping for a work around cause I got my phone setup just right. Is there a backup I can do that will restore everything exactly the way I have it now (except Wifi calling of course)? I had titanium backup years ago but it was a pain back then.
WiFi Calling
I have the same issue with my S7 with the enablement error. I have been on the phone with Sprint for over 1 hr with no help - they state it is a Samsung software issue. I went back to Best Buy where I got the phone and exchanged it but still the same problem. I took it to the Samsung reps who were there and they also were stumped. I reached out to "advanced tech Sprint support" who stated its a Samsung issue and will not be fixed until they release a patch. I reached out to Samsung and they stated they were not aware of any issues and to send the phone to their repair center - which made no sense. I see online that some have no issues doing wifi calling so it may be luck of the draw. I think that Sprint will blame Samsung who in return will say no issue. I am going to try to exchange the phone again and hope the third time works!
Did you try a hard reset?
Check wifi calling doesn't support messaging at this time..
Chetski said:
I know what you mean. Luckily I had fingerprint unlock working cause my pin unlock broke after the update. Hoping for a work around cause I got my phone setup just right. Is there a backup I can do that will restore everything exactly the way I have it now (except Wifi calling of course)? I had titanium backup years ago but it was a pain back then.
Click to expand...
Click to collapse
It only recognized my fingerprint a couple times then after power off it wouldn't. Also found out find my mobile isn't set up by Samsung for s7 yet, if ever. . I use nova launcher which allows you to save your homescreen and widget and folder setup. I use helium to back up apps and data. Restore was only really annoying not horrifically annoying. Don't forget to back up your Samsung account settings and take your sd card before you go the Google reset route. . The most help I got was the Samsung rep at best buy
Sent from my SM-T330NU using XDA-Developers mobile app
Thank you, that's a lot of great information.
I had 4 reps tell me to bring it to store for repair, did hard reset etc.... got up to advanced tech support before guy called me and said "fixed the problem, go ahead and try"and worked fine after that.
I have been using Kevo on my samsung phones going back a couple of models. I got the S7 Edge and it worked fine until yesterday. Door doesn't respond to the phone. The app said it needed to update, but timed out of updates whether on wifi or 4G. The app itself said it was for lollipop- it just stopped working. I uninstalled and then reinstalled, the update button is now gone, it works, and still shows for lollipop. Anyone have similar experience?
sefar said:
I have been using Kevo on my samsung phones going back a couple of models. I got the S7 Edge and it worked fine until yesterday. Door doesn't respond to the phone. The app said it needed to update, but timed out of updates whether on wifi or 4G. The app itself said it was for lollipop- it just stopped working. I uninstalled and then reinstalled, the update button is now gone, it works, and still shows for lollipop. Anyone have similar experience?
Click to expand...
Click to collapse
I just installed my Kevo on Easter. I didn't have any problems with it at all...until I tried to enable android wear. When I did that, I got an alert that it needed an update. That was an endless process of back and forth, enable and disable it on the app, but finally I got an update button that said keep phone w/in 20 feet while it processed the download. I just sat my phone on the floor and did some other stuff. Came back and I had an all update finished and "tap here to restart kevo app". I did that and tried the lock out with my phone, fab, and keys...all okay. When I tried my watch (moto 360), I got the "no keys" error followed by "unexpectedly stopped" message.
I shot an email off to Kevo/Kwikset about it and yesterday got a reply back. Their support stated they do not support the S7 or S7edge with no eta that they will in the future. I asked why, but haven't received an answer yet. Then I saw on reddit that someone said it was because Kevo only supports Android-L; however, now that more devices are getting updates to M, a lot more people are having trouble. They officially state that Kevo supports the S6...what's going to happen when an S6 updates to M? Wonder if they'll put out an update?
They have been notoriously slow, but my app is working again, despite the OS issue they mentioned. Weird, and it still doesn't work with the GearS2, contrary to all the publicity when the watch was released last year that it was working!
Wondering if anyone else has encountered this incredibly annoying issue. Using a T-Mobile S8 and ever since the last update I've been getting prompts to log in to my Samsung account. The window will always interrupt whatever you're doing when it decides to pop up, and is always waiting when you unlock the phone in the morning. I don't have a Samsung account, nor do I want one. I just want to be able to stop this from happening. Any thoughts?
The same thing has been happening to me since my last update. I've just been ignoring it, but I'm on the same page as you. I refuse to get a Samsung account. Google already knows everything there is to know about me. I doubt there is anything to prevent that pop-up from appearing for now, but at least it's not any more intrusive than it already is.
Ardrid said:
Wondering if anyone else has encountered this incredibly annoying issue. Using a T-Mobile S8 and ever since the last update I've been getting prompts to log in to my Samsung account. The window will always interrupt whatever you're doing when it decides to pop up, and is always waiting when you unlock the phone in the morning. I don't have a Samsung account, nor do I want one. I just want to be able to stop this from happening. Any thoughts?
Click to expand...
Click to collapse
I have Samsung account, so I don't have any annoying popup regarding that, but I have used my phone without signing in to the account for at least a week and haven't seen any popups either. I am using US Unlocked S8
Ardrid said:
Wondering if anyone else has encountered this incredibly annoying issue. Using a T-Mobile S8 and ever since the last update I've been getting prompts to log in to my Samsung account. The window will always interrupt whatever you're doing when it decides to pop up, and is always waiting when you unlock the phone in the morning. I don't have a Samsung account, nor do I want one. I just want to be able to stop this from happening. Any thoughts?
Click to expand...
Click to collapse
I was starting to think I was the only one. Google is no help, who's surprised. I used the 'contact samsung' field in the popup a few dozen times. First few times they told me to disable the app in settings, so I knew they wouldn't be any help. After a lot more emails they said to bring the phone to a samsung service center. There isn't one within 100 miles, and I'm not going to send it to one, so, another dead end. When 99.9 percent of sheeple are dying to sign up, samsung isn't going to accommodate the few who still remember privacy and free will. If I didn't require a smartphone for work I would use this thing for skeet practice. The 30 year old phone that is screwed to my kitchen wall still works fine.
Here's how
This is how I fixed it. Go to Settings/ Accounts/ accounts (again)/ Samsung Account/ About/ App Info/ Notifications/ uncheck. You're welcome
Many thanks for your solution friend.
It's back and can't be disabled in Oreo
I'll second that, updated to Oreo this morning, Samsung account nag is back and haven't found a solution to disable it yet.
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.