Related
Running stock DK28 with no real problems till now, as of yesterday none of my accounts (gmail, hotmail, yahoo) will send or receive messages in the Email app. The Gmail app still works fine and obviously the webmail in the browser works - but the email app just doesn't do anything. When I set it to sync it just spins forever and sent messages stay in the Outbox indefinitely.
Any idea why this may be happening? I've been running DK28 for about a month and never had the problem before.
Me too!
Odined my phone last week back to DI18 and everything was going fine until monday when I noticed that my email wouldn't sync anymore when I told it do. Even setting it back to automatic, it still wouldn't sync. Another odd thing I noticed was that the screen orientation would get stock and not respond.
I dont know what caused your problems but considering that I didnt have these problems before I blame it on me and my apparent lack of flashing my phone properly lol. So tonight I'm going to flash again and be a little more meticulous
I suggest you do the same.
I have a Canadian Rogers Galaxy Note 3 (SM-N900W8) running the latest software update (as of last night).
Any time I dial someone's number, there is a full 10 to 15 seconds delay/lag before the phone 'reacts' and starts to actually make the call. This lag/delay happens regardless if I am:
using speed dial (though it is especially obvious then)
manually dialling a number
sliding to the right on a person's contact (quick dial)
pressing and holding on a contact's number to dial
I've tried adjusting the Google Sync settings, turning on/off the "Sync People details" as well as my Samsung account's "Sync contacts". I've disabled Facebook/Linked In "Sync Contacts", based on my theory that there was some sort of hiccup being caused by these apps' attempts to pull data on the contact immediately upon me placing the call.
The other issue is that Contact photos/names are also severely delayed when receiving an incoming call, for example when my phone starts ringing, all that I can see is their phone number at the top of the screen (almost as if it's the 'raw' cellular data), and not their name or picture (as normally would immediately appear on say my Galaxy S 3).
I've searched all over but have yet to see this issue pop up. This seems really strange. Any ideas or solutions?? Thanks!
Edit: I tried a second battery pull and hard restart and this seems to have fixed the issue for now. Weird!
If it's any consolation, it's not just your Rogers Note 3. I'm having the same issue with the Note 3 made for T-Mobile USA. I'm going to try the battery pull like you suggested and see if that resolves the issue, as well as some alternate dialers. I'll post my luck once I've tried this.
kamandor said:
Edit: I tried a second battery pull and hard restart and this seems to have fixed the issue for now. Weird!
Click to expand...
Click to collapse
I have found this problem (delay dialing) for 2 weeks.
When I connect to internet, by wifi or mobile data, it is corrected. But whenever the internet connection is disconnected , it apears.
I'm disappointed from Note 3 because of lots of bugs that has got especially after update to kitkat
-delay dialing
-not working any auto call recording app.
-not working properly it's sensors.
And etc
Same bug here. 4.2.1. Phone was fine, never used to do it. randomly started doing this around the same time as I started getting multiple duplicate sms messages. Dialing delay goes away when wifi is on.
Very annoying. I'm open to suggestions!
Shaunuss said:
Same bug here. 4.2.1. Phone was fine, never used to do it. randomly started doing this around the same time as I started getting multiple duplicate sms messages. Dialing delay goes away when wifi is on.
Very annoying. I'm open to suggestions!
Click to expand...
Click to collapse
At least 150MB of phone memory should be free..
Else, it'll lag..
I removed a few apps and now am having 200MB of free space on my Phone Memory (internal), and there are no lags..
Phone is running smooth..
StaticBlaze said:
Atleast 150MB of phone memory should be free..
Else, it'll lag..
I removed a few apps and now am having 200MB of free space on my Phone Memory (internal), and there are no lags..
Phone.is running smooth.
Click to expand...
Click to collapse
Thanks for your reply! I have 1.1gb RAM free pretty much all the time, 1.18GB ROM free, and 20.99GB internal SD free.
Not sure this is the problem.
I got the same problem and i realized after i read this post that it doesnt happen if im connected with wifi. There should be a way to fix this, its a 500euro phone there shouldnt be such problems...
Had the same problem with a Samsung Relay, after a few updates. Had a chat with Samsung, after a hard cache clearing left me with the option to factory reset. Which I'm not very interested in. Uninstalled a lot of applications, then by chance connected to the wifi and sent an email. After that, it seems to be working now.
Didn't fix the problem for more than a few hours. Actually I believe hooking on wi-fi did it, because I connecting again this morning solved the problem again.
I installed a firewall and denied permission for all apps, let's see if this works...
No, the firewall doesn't work.
After connecting on wireless it works for about 3-4 hours. Then again bull**** happens. Don't know why, but this relation is interesting. There is no actual traffic sent form the device, since the firewall blocks a lot of the system bull**** apps from communicating, but after enabling it it works.
I see that enabling wireless even for a short while (3sec) is enough to get it back on track. Why might this be so?...
Prey
Factory reset, reinstall everything, then encryption. 4 hours. Tested during the procedure to see if it dials fast. It dialed, until the end, when it started to have the same problem again.
Then I got the wonderful idea from above to check if there is something wrong with Prey. A software to block your phone if it's stolen. And guess what, as long as it's not connected to the Internet, it hangs and won't open. Maybe this was creating the problem? Don't know, but for now I uninstalled it and it seems to be working. I remember it did an update before the problem occurred, maybe the update is the problem? Will write again if the problems persists.
Cross-referencing this thread on Prey:
https :// help.preyproject.com/topics/ android-call-delay-caused-by-prey
(sorry, as a new user I can't post outside links, so you must correct the URL above)
Seems I'm having the same issue on two of my Prey-enabled devices (HTC One X+ and HTC One X) after upgrading to latest version. Happens with Data-off.
norenendur said:
Factory reset, reinstall everything, then encryption. 4 hours. Tested during the procedure to see if it dials fast. It dialed, until the end, when it started to have the same problem again.
Then I got the wonderful idea from above to check if there is something wrong with Prey. A software to block your phone if it's stolen. And guess what, as long as it's not connected to the Internet, it hangs and won't open. Maybe this was creating the problem? Don't know, but for now I uninstalled it and it seems to be working. I remember it did an update before the problem occurred, maybe the update is the problem? Will write again if the problems persists.
Click to expand...
Click to collapse
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.
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...
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.