Related
I know I'm not alone with this and I think it's getting ignored because most people don't have the problem.
Even after the MR, I'm still having 100% Awake problems.
Yesterday I did the following.
1. Flashed back to stock rom.
2. Allowed the phone to perform the OTA MR update
3. Updated PRL and Profile.
4. Rooted phone using asroot2 process.
5. Installed Optimized/Zipaligned Apps found in this forum.
I then installed a random selection of my preferred apps. I did not log into any of the social networks on the phone itself. Facebook, Twidroid, Peep, Seemic are all on the phone but either not logged into or not set to update automatically. GPS is on, bt and wifi are not.
The only widgets I'm running is the normal clock/weather, big calendar, music player, and gps/wifi/bt toggles. Everything else is shortcuts and such. I'm using Gmail app for my mail, the stock messaging app for sms, and the stock browser. I'm syncing with Google for mail, contacts, and calendar. I have no other email accounts set up.
This was the 3rd time going through this process. The phone lasts roughly 24 hours with great low awake times, then suddenly starts climbing. A reboot will of course reset it so it shows 100% awake.
Things I've tried.
Installed Spare Parts and sorted by all sorts of things. Android System seems to be the biggest offender. Real vague.
Installed the Terminal app and tried to run top. Nothing seems to be taking up an abnormal amount of CPU but I don't know how accurate this thing is.
Obviously I've tried this 3 times and attempted to keep all widgets and other things that constantly update away from use but it doesn't stop.
I have shied away from task killers seeing how that's the normal reaction in this forum, that they're bad and I'm not sure they are a good idea.
My buddy has the exact same phone, way more widgets and things running, and his has been running for days without ever going over 25% Awake. We've went through all of our setting and installed apps and widgets etc, and cannot find a good reason for this.
I'm hoping to get some recognition for the problem. Maybe if others have the problem, we can try to see if we can come up with a fix.
Suggestions
Check the apps you have installed, some of the ones i liked say they 'keep the phone from sleeping' during installing. Just because you aren't running an app doesn't mean it's not running in the background. I would suggest you uninstall ALL external apps and test your phone for 24 hours after a full charge and see if that is the problem.
Another problem i had was i never gave my battery the proper charge when i bought the phone. I got much better performance from my batter by running it down to where it would not turn on then completely charged it without interruption. I repeated this 3 times in a row and my battery lasts much longer now.
I would also suggest to flash your phone with the fresh ROM .6b After doing this my phone was amazingly fast and excellent sleep times.
Currently Pulled Status:
After 48:15:00 Up Time Only Awake Time 13:01:00 (27%)
I'm aware of that app thing but I will say that I haven't installed any apps to speak of today. The only thing I installed today was a widget for turning the ringer off but I uninstalled that. Of course, that *could* be the problem.
Other than that, I haven't installed any apps today so you'd think that anything that would cause 100% Awake would have happened yesterday as well. Granted, that's an assumption and something best proven so tonight I will flash to stock + the OTA MR and leave it alone. We'll see if the phone with zero apps installed in basically stock form flips to 100% awake tomorrow or not.
I tried Fresh yesterday and it made no difference. Granted, I put it on top of a phone that already was at 100% Awake but still. I also don't care for what's installed/removed on the rom either. I would love to have my stock rom + rooted + removed apps + optimized apps and call it a day. I can hope right?
I was having the same problem as you...
I did a factory data reset after I applied the MR.
Then rooted
Then installed fresh .6
my phone has been sleeping like a baby ever since (over 1 week now).
Hope that helps...
andybars said:
I was having the same problem as you...
I did a factory data reset after I applied the MR.
Then rooted
Then installed fresh .6
my phone has been sleeping like a baby ever since (over 1 week now).
Hope that helps...
Click to expand...
Click to collapse
I tried Fresh .6b but it didn't help. Granted, I applied it after the 100% awake problem hit. I don't really care for Fresh though.. but I might try it after I do a few experiments.
Bah.. I gave up on the experiment idea and went ahead and did this.
Flashed to stock
OTA MR upgrade
Rooted
Flashed Fresh .06 ROM
Flashed Optimized/Zipaligned apps
Only apps installed are Seesmic, SMS Backup & Restore, and Call Logs Backup & Restore.
I will leave it at that for now. It will get a full charge tonight and hopefully I'll see more than a 24 hour run of good idle time.
I can say that sms problem is also persists.
And i found out that i have SMS problem only when there is 0 in incoming number. If sender have number without ZERO - it works just fine.
Nice fix from sprint -) I think they do not test it at all
kajama said:
I can say that sms problem is also persists.
And i found out that i have SMS problem only when there is 0 in incoming number. If sender have number without ZERO - it works just fine.
Nice fix from sprint -) I think they do not test it at all
Click to expand...
Click to collapse
I am running the MR + rooted, and have *NO* issues whatsoever with texting... and I have sent and received plenty of messages to/from people with a zero in their phone number.
x99percent said:
I am running the MR + rooted, and have *NO* issues whatsoever with texting... and I have sent and received plenty of messages to/from people with a zero in their phone number.
Click to expand...
Click to collapse
Could be a total coincidence but I was texting someone with a zero in their number when my awake time started climbing. But I had also been texting all morning with another person with a zero in their number and it waited until around 3:30 to start acting up.
sph33r said:
I will leave it at that for now. It will get a full charge tonight and hopefully I'll see more than a 24 hour run of good idle time.
Click to expand...
Click to collapse
make sure you look for the following
settings>applications>deveolopment
(uncheck stay awake)
if this is checked, your phone WILL NOT SLEEP when plugged in.
to avoid any silliness make you check the awake time when it is NOT plugged in.
...Just sayin
x99percent said:
I am running the MR + rooted, and have *NO* issues whatsoever with texting... and I have sent and received plenty of messages to/from people with a zero in their phone number.
Click to expand...
Click to collapse
I have this problem on 2 updated Hero.
kajama said:
I have this problem on 2 updated Hero.
Click to expand...
Click to collapse
What problem? I said I had no problems..?
x99percent said:
What problem? I said I had no problems..?
Click to expand...
Click to collapse
I understood your message, but i STILL have SMS problem on 2 HERO after MR update. Thats a pitty
Well folks, I thought I had the problem licked but last night it came back. On Monday morning, I did the following:
1) RUU back to stock
2) applied voice mail and MR update
3) rooted phone and applied optimized apk & clear screen mod
It was working so well until last night when I was playing with the wireless and wired tether apps. After I *uninstalled* those apps, the phone would not go back to sleep. I'm getting sick of this but will not be resetting my phone. Hopefully an update will come out soon to resolve this.
Yesterday I decided I didn't care for the Fresh .6 rom and went back to my experiment idea.
I flashed the stock RUU back onto it, let it do the OTA update for the firmware, and then installed only Handcent and Seesmic to keep from using the stock SMS/twitter clients just in case.
I signed into Google for my Gmail, contacts, and calendar and left all the update settings alone. I turned on GPS satellites, and I signed into the Facebook integration on the phone so I could get the photos/bdays/status updates in People.
That's all I did. No rooting, no additions, nothing. I removed all widgets except for the clock/weather and the big calendar. Everything else was deleted, I only have the 6 shortcuts on the first home screen.
I went to bed with between 1:15-1:30 awake time. I woke to 4:45 wake time and climbing. Sometime around 5am it stopped being idle and is now climbing steadily toward 100% awake time. Obviously I wasn't using the phone, I received no phone calls or text messages, and it was charging.
This is frustrating.
sph33r said:
Yesterday I decided I didn't care for the Fresh .6 rom and went back to my experiment idea.
I flashed the stock RUU back onto it, let it do the OTA update for the firmware, and then installed only Handcent and Seesmic to keep from using the stock SMS/twitter clients just in case.
I signed into Google for my Gmail, contacts, and calendar and left all the update settings alone. I turned on GPS satellites, and I signed into the Facebook integration on the phone so I could get the photos/bdays/status updates in People.
That's all I did. No rooting, no additions, nothing. I removed all widgets except for the clock/weather and the big calendar. Everything else was deleted, I only have the 6 shortcuts on the first home screen.
I went to bed with between 1:15-1:30 awake time. I woke to 4:45 wake time and climbing. Sometime around 5am it stopped being idle and is now climbing steadily toward 100% awake time. Obviously I wasn't using the phone, I received no phone calls or text messages, and it was charging.
This is frustrating.
Click to expand...
Click to collapse
did you just totally ignore my post or what?
johnsongrantr said:
did you just totally ignore my post or what?
Click to expand...
Click to collapse
Yes I ignored it because it did not pertain to the issue at hand. If you had read my entire post, you would see that it had, on all previous times, went from idle to 100% awake while off the charger. Last night was the first time it ever went awake in the middle of the night and it only happened 3 hours before I woke up meaning that it had been on the charger for 5 hours previous without being awake.
Also, that option isn't even checked by default. The only way it would be checked is if you were too stupid to read the text next to it. Needless to say, mine is not checked.
So no, never once in the time of having his phone has that setting been turned on. This issue is not related to your post in the least.
sph33r said:
Yes I ignored it because it did not pertain to the issue at hand. If you had read my entire post, you would see that it had, on all previous times, went from idle to 100% awake while off the charger. Last night was the first time it ever went awake in the middle of the night and it only happened 3 hours before I woke up meaning that it had been on the charger for 5 hours previous without being awake.
Also, that option isn't even checked by default. The only way it would be checked is if you were too stupid to read the text next to it. Needless to say, mine is not checked.
So no, never once in the time of having his phone has that setting been turned on. This issue is not related to your post in the least.
Click to expand...
Click to collapse
well just for ****s and grins.... retest with it not being plugged in. just to rule out even the remote possibility of that being the issue.
EDIT: also if you are really hard set on figureing out what is causeing it do a stock RUU, then update it.... then don't touch it... at all, no market apps, no enableing anything.... then test
if good, then add a variable.... use scientific method of figureing out what is wrong. Don't just test with a random set of variables and hoping someone might guess at what might be the issue.
from the information you gave.... my money is on the charger causeing it. I may be just totally wrong, but my track record is being right most of the time with this type of troubleshooting.... but if you want a second opinoin... by all means... and a tip of the hat to you sir
johnsongrantr said:
from the information you gave.... my money is on the charger causeing it. I may be just totally wrong, but my track record is being right most of the time with this type of troubleshooting.... but if you want a second opinoin... by all means... and a tip of the hat to you sir
Click to expand...
Click to collapse
I'd say you're wrong because I'm not experiencing the issue at all.
Since the OP's phone and my own are similarly modded, I'm thinking that it has something to do with his own personal info (contacts, calendar, etc.)... because I have NO issues.
I use HTC Peep to update/view Twitter.
I use Handcent for SMS/MMS.
In contrast to the OP's phone, my phone has a ton of stuff installed (25 free apps from the Market, last I checked)... yet my awake times are consistently <30%.
johnsongrantr said:
well just for ****s and grins.... retest with it not being plugged in. just to rule out even the remote possibility of that being the issue.
EDIT: also if you are really hard set on figureing out what is causeing it do a stock RUU, then update it.... then don't touch it... at all, no market apps, no enableing anything.... then test
if good, then add a variable.... use scientific method of figureing out what is wrong. Don't just test with a random set of variables and hoping someone might guess at what might be the issue.
from the information you gave.... my money is on the charger causeing it. I may be just totally wrong, but my track record is being right most of the time with this type of troubleshooting.... but if you want a second opinoin... by all means... and a tip of the hat to you sir
Click to expand...
Click to collapse
Except, again.. of the 4 times I've reloaded this and had the 100% awake time, only once has it happened on the charger. So I find that theory a bit weak. I suppose it could be, but still.. seems a bit odd that, for instance, it would wait until 3:30 in the afternoon (7 + hours after coming off the charger) to act up.
I'm currently stock + 2 apps which should eliminate the supposed leak with the SMS that some people still claim is happening. But I will flash the stock RUU and then the OTA MR and leave it alone. I'm still going to use the functions of the phone though. I see no reason why syncing with Google or facebook or using peep should matter since those are on the phone from the get-go and intended to be used. I'm sure everyone on here who has no problems at all has a lot more things turned on than I do right now.
For instance, X99Percent and I have compared settings. He has WAY more widgets running, WAY more programs installed, and is signed into all the social networks. Yet he can use his phone for days with normal idle time. I might make it 24 hours, or in the case of yesterday, about 14 hours, before going to 100% awake.
I'm convinced it has a lot more to do with something wrong with the phone itself or a software bug than anything else. And if you notice, I'm not alone in this problem, there's others complaining about it on here and on PPCGeeks.
What the heck? I had at least 600+ txt messages from all different people, and now they're all gone?!?! I sent a txt message (stock, not rooted, using google's Messaging app), put my phone into sleep mode, woke up my phone a few minutes later to send another msg, and was greeted by an empty thread (with a bud's phone number there but none of the prev. messages), and there were no messages/threads anymore
The exact same thing has happened to me twice so far...
Yep. This happens ALL THE TIME with me. I've been having MyBackup Pro run nightly backups so I don't lose important information. This is a serious bug for me and it's cost me some info that could not be recovered before that I really needed.
I've never had a smartphone that has done this but the Nexus does it about once a week. Now I only lose a few messages when it happens since I back up every night, but the fact the issue is there at all and it just happens randomly is really disheartening. Rooting and using a custom ROM has not helped.
Have all of you tried disabling auto delete?
Yeah, that's not related to this issue. You can have auto-purge off and it will still happen after a while. Just randomly erases everything.
That's odd, this is the first time im hearing of this. I've never had my phone delete anything i didn't want it to.
Maybe it's something to do with the ROM you're using or some tweaks you've done.
Try using a stock rom for a while or something and see if the problem persists
I've heard this happening many times now, and every time it was when using the built in messaging app. So I've used hand cent from day 1.
interesting. this happened to me also. only one time though so far..*knocks on wood.
never had it happen to me (knock on wood) thats a very weird problem :\
This has happened top me once on my Nexus in three months.
It's on the buglist here - http://code.google.com/p/android/issues/detail?id=5669 where they are asking for logs to help identify the issue.
There are already a couple of threads about this. It's not just the Nexus - it seems to be 2.x
see here
http://forum.xda-developers.com/showthread.php?t=667800
PhantomRampage said:
Maybe it's something to do with the ROM you're using or some tweaks you've done.
Try using a stock rom for a while or something and see if the problem persists
Click to expand...
Click to collapse
For the record, while it only happened to me once, it did happen to me and I've never rooted or installed any custom ROMs (I even waited for the official OTA for update 1 to hit me in due order).
Luckily I had a 2-week old backup of SMS to restore and I've since set a nightly backup schedule for SMS/MMS and call log via MyBackupPro.
One thing that may contribute is that I am a pack rat and so have every message that I've gotten since I got my G1 in 10/08 (ignoring that one purge due to this bug and the time when I forgot to turn off auto-deletes and didn't notice until a couple of weeks later). I have threads with several hundred messages in them for the friends I text most...
It does seem to happen to us pack rats, and not very often to those who don't hoard messages. I read somewhere that it was suspected to be an overflow error of some sort, and that people had managed to prevent it by keeping the auto-delete function active.
I am not prepared to do that however. I don't want to deliberately delete my messages that I have worked so hard to collect. I would rather google fixed it.
Hopefully froyo will bring a solution to our problem.
WTH is going on!? The last 2 weeks Market has been flaky at best. I click to update/download something and it just hangs. Come back to it hours later and the program I clicked on 3 hours ago is finally installed.
I'm on stock, rooted with 1 click. Anyone else seeing this problem?
I posed this earlier in IRC. what I do is sign in and out of Google Talk. Seems to clear it up.
Google talk is pre-installed on your phone. The app is called talk.
Quicksand Jesus said:
I posed this earlier in IRC. what I do is sign in and out of Google Talk. Seems to clear it up.
Google talk is pre-installed on your phone. The app is called talk.
Click to expand...
Click to collapse
I can sign out of Google talk but I can sign back in. I reboot the phone and still have the same issue. I've been having this issue for the past week so something makes me thing it's the market/sprint.
blazinazn said:
WTH is going on!? The last 2 weeks Market has been flaky at best. I click to update/download something and it just hangs. Come back to it hours later and the program I clicked on 3 hours ago is finally installed.
I'm on stock, rooted with 1 click. Anyone else seeing this problem?
Click to expand...
Click to collapse
Ok, to me, you just confirmed that it's a Sprint/Google connection issue. A few people in the Evo forum are having the same problems. Some people weren't even rooted and were having the same problems.
It seems to affect all google apps including Market, Gtalk, Gmail, etc. The apps seem to hang or give me a server error. My problems just started last night and I too am rooted. Luckily, like I said before, it seems to affect rooted and unrooted users.
I called up Sprint and they wanted me to do a hard reset (of course), but I refuse to since these seem like bigger problems, and they probably can't be solved on the phone level, but rather on the network level.
Hopefully they can find the problem soon!
Great, now I can't login to talk or use the market.
I rebooted a couple times and it worked for a couple mins, then stopped again. I'm gonna go with this is a Google problem, doesn't work when I use wifi either.
Fix for Wifi issues with Samsung Epic
So ever since I rooted my phone I've had issues with wifi for use with anything such as the market, web browser, sms, you name it.
Found that there is a file that is easily corruptible and can easily be fixed thankfully with a free app from the market called Android Mate.
You'll have to have your phone rooted and then navigate to the phones base directory then go here: /data/wifi/ and delete this file: bcm_supp.conf
Android Mate seems to have issues with navigating the base folder (root directory) so for me I went to the data folder and had to manually type in /wifi and it pulled up the bcm_Supp.comf file and I deleted it and rebooted my phone and presto no more issues.
Hope this helps a few people
I am unrooted and am having the exact same problem. Both with market and gmail. I can't even get emails half the time or hardly ever even see the apps I've downloaded in market! Very frustrating!
Sent from my SPH-D700 using XDA App
Someone at Howard Forums reported they can't even get to sites like google.com and Gmail from their laptop when connected to the internet via their Sprint data card.
Today, Google Talk FC's for me every time I try to start it.
Over the last couple of days my messages have been acting weird.
I'll send a message, and then when someone replies it will show that I received their message before I sent mine.
Has anyone else had this happen?
I'm using a stock dhd with gingerbread
Sent from my Desire HD using XDA App
I think there may be a problem with the HTC time servers. My phone is currently 12 mins ahead of the rest of the world!!
I have seen posts on the vodafone forum concerning time errors.
rider5512 said:
I think there may be a problem with the HTC time servers. My phone is currently 12 mins ahead of the rest of the world!!
I have seen posts on the vodafone forum concerning time errors.
Click to expand...
Click to collapse
Okay, thanks for the info.
Also my weather hasn't been updating for the last 2 days , so i'm guessing that's related to their servers aswell.
i had this i fixed by disabling auto time update then set manually then switched back to auto then set manually again before finally selecting auto (rebooting phone after each change)
this fixed it for me, might not for you, yours might only need changing once but worth a try
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.