Trying to help my dad out with his Pixel C. He was complaining about constant bootlooping after Android Nougat was installed on his tablet. I did some remote trouble shooting with him, and nothing seemed to help. I instructed how to do a factory reset. He did this, reinstalled his apps, and a few days later the bootloops started happening again. He ended up getting an RMA from Google.
New device came today. I added his account, all was fine. Restored his apps. Again, all is fine. used some random apps, again, all is fine. Opened Chrome. Bootloop. Cannot get it to stop bootlooping unless I turn off wifi BEFORE it connects to wifi. Sometimes you don't have a chance, it connects before you disable it. If i disable wifi, I can use the tablet and it is fine (well as much as you can do on a non internet connected device). As soon as wifi connects, it bootloops. I have removed his google account, disabled all syncing, removed almost every single app, yet the problem remains.
Does anyone have any idea what else I can do?
I want to grab a trace of whatever is causing the crash, but not sure of the best way/app that will let me do that.
Try disabling chrome
I tried uninstalling it as well as uninstalling every other program.
I'm trying to flash the latest factory image, and it keeps dying trying to flash the system partition.
Related
Has anyone else had trouble accessing Google Talk over 3G? If I don't use WiFi, it constantly tells me "unable to access server." If I do turn on WiFi, and then shut it off, GTalk shows everything grayed out. If I don't sign in to GTalk, I can't use the market. What's going on here? I was able to use GTalk on 3G *once* today. Not anymore.
My googletalk hasn't been able to sign in for the past 2 days.
It will randomly not be able to connect but then later connect for a few minutes and sign out.
I'm connected to wifi and its working now however.
posted from a EPIC4G.
Just had this problem on my girlfriend's Epic. It has to do with the Market, they're linked to your account and you can't have on without the other (from experience). I tried rebooting, clearing market and gtalk cache and the new update that came out a few days ago but nothing seemed to work. I finally did a factory reset and everything worked like it should.
Sent from my SPH-D700 using XDA App
It's just plain stupid that this is necessary. Android is starting to really grate on my nerves lately.
Hmmm, my GTalk works when on wifi or 3G. Now when I change connections from one to the other it takes some time to reconnect sometimes. That I do notice.
Forgive My Brevity. To Be Or Not To Be...
I had to hard-reset the damn thing. Adding Google accounts was giving me the stupid "Could not establish a reliable connection to the server" bullcrap. Of course, everything works *wonderfully* now (minus GPS, of course), and the phone is nice and fast again. What is this, Windows Mobile?!
Edit: GAH! It's happening again! "Could not connect to server. Will retry shortly" when on 3G! WTF, Google. I just wasted 2 hours reinstalling apps after a hard reset just to get this crap all over again.
So is this for sure a problem on googles side?? Cuz only few people seem to confirm this issue. I'm still within my 30 days, so I can exchange my phone if its a specific phone related problem..
I don't know. Some rocket surgeon over at Google decided that it was best to allow multiple Google accounts on the phone and sync everything, but not let you change Gtalk accounts. Their response to the bug? They try to throw the Gtalk team under the bus and close the bug report.
Okay, and now it's working again. I moved around to another Sprint tower and everything worked again. This actually happened yesterday. Now I'm back to my original location where the bug showed itself the first time, and things still seem to be working. I'm going to avoid reboots for now...
I am having the same problem
APOLAUF said:
Has anyone else had trouble accessing Google Talk over 3G? If I don't use WiFi, it constantly tells me "unable to access server." If I do turn on WiFi, and then shut it off, GTalk shows everything grayed out. If I don't sign in to GTalk, I can't use the market. What's going on here? I was able to use GTalk on 3G *once* today. Not anymore.
Click to expand...
Click to collapse
I am also having the same problem with my Galaxy S2. Has anyone resolve this without resetting it to factory setting?
Hi,
I've been searching for solutions now for a few hours and finally it dawned on me that maybe I should try connecting via hotspot from my cell. Now the download starts normally. But when I switch back to my normal wireless router, it comes back again.
I have done all the "tricks" one can find online: clearing cache, deleting my account, removing updates from g-play. Also I have no firewall on in my router. everything else works well. On top of this, the downloads worked like two weeks ago and I have not touched anything since...
Please tell me that someone here has an idea what is wrong?
[Q] Very unusual WiFi problem. I can not "search" or "sign in" to Google Services
As titles states; This is not rom related, though it first happened while flashing a nightly build of CM. On the screen to sign in to my Google account, it was hanging. I let it go for about 5 minutes then disabled WiFi and retried with success. I thought it was a isolated issue so I didn't think much of it. I then turned WiFi back on and continued to setup the rom. When I got to the stage of downloading an app from Play Store I continued to getting "Connection timed out" - This went on for several attempts until I disabled WiFi.
The last problem I have is when I search in Google it fails to load any results unless I disable WiFi. What is even stranger is I can use WiFi ONLY when I type in a complete URL in the address bar "www.xda.com" for example. It is almost as if WiFi is failing to communicate with Google Services? - I have flashed a few other modem packages and completely formatted internal SD and sideloaded another roms to no success. I am about to go back to stock firm to see if it resolves it but thought I would ask here just in case someone has had a similar issue
uppon2 said:
As titles states; This is not rom related, though it first happened while flashing a nightly build of CM. On the screen to sign in to my Google account, it was hanging. I let it go for about 5 minutes then disabled WiFi and retried with success. I thought it was a isolated issue so I didn't think much of it. I then turned WiFi back on and continued to setup the rom. When I got to the stage of downloading an app from Play Store I continued to getting "Connection timed out" - This went on for several attempts until I disabled WiFi.
The last problem I have is when I search in Google it fails to load any results unless I disable WiFi. What is even stranger is I can use WiFi ONLY when I type in a complete URL in the address bar "www.xda.com" for example. It is almost as if WiFi is failing to communicate with Google Services? - I have flashed a few other modem packages and completely formatted internal SD and sideloaded another roms to no success. I am about to go back to stock firm to see if it resolves it but thought I would ask here just in case someone has had a similar issue
Click to expand...
Click to collapse
Problem was resolved only after going back to complete stock 1.2.1
I attempted to download an app from Google Play yesterday and noticed the download was running very slow so i stopped it and re-tried it a few times. It then stalled and would not download at all so I closed Google Play store and went back into it, now I get 'No Connection' in the center of the screen and Google Play will not work. I have since tried my stock Android browser and I get 'Web page not available' and also Youtube and Amazon app store have similar issues. However, what doesn't make sense is that some Internet based apps work fine and Dolphin browser works fine too. If I switch off Wi-Fi and connect to 3G everything works fine so the issue lies with the Wi-Fi connection. My wife who has the same phone can connect and use the Wi-Fi fine without any issues and any other Internet device I have is still working as it should be. It appears it is only my phone with the issue.
I have tried checking date/time which is correct.
I have reset cache and cleared data for both the browser, Youtube and Google Play
I have rebooted my phone and my broadband router
I have tried changing the security settings to from WPA2-PSK (AES) to WPA/WPA2-PSK (Mixed Mode)
All to no avail.
I have rooted Android 4.3 but it has been working fine for over a year before now. I would want to avoid doing a factory reset at all costs as I have some important apps that can't be backed up with the likes of Helium and some other forums have shown that a factory reset has not resolved the issue.
Any help on this matter would be much appreciated.
After a day of trying to resolve this issue I have finally managed to fix it. This may be useful for anyone else having the same issue:
I went into my Wi-Fi settings and looked for my router in the list and did a long tap on the name and chose 'Forget Network' so it removes my router. I then did a re-scan so it picked it back up. When tapping it, this time I was able to re-enter my Wi-Fi password and connect. After doing this everything started working again.
I've no idea why all of a sudden the network failed to work correctly but at least it is now sorted. I just don't understand why some Internet access worked and others did not. I guess I shall never know!
Hey guys. I'm having a very weird WiFi issue on my A520F.
Today the WiFi froze. It wouldn't turn off when I switched it off. After I while it turned off but took ages to turn it on again.
I factory reseted the device because I thought it was a software issue. It didn't work - after the first boot it was the same.
After a while after this, the WiFi started working again, but only for a period of time, then it would just freeze again for apparently no reason. Switching it off and on solves the issue for a while, then it freezes again saying that my WiFi is limited.
I can't take any logs since I'm not rooted (and don't have a PC to use ADB), and this is really scaring me since it happened out of nowhere. An hour before this started happening WiFi was working just fine.
I haven't installed anything unusual today, just connected for the first time on a new, but trusted, WiFi.
I've also reseted my WiFi router to its factory settings, thinking that it could be the issue, but the problem persisted. My Chromecast works just fine on the very same network.
Did this happened to anyone before? I've tried to root my phone a while back and, since it didn't worked out, I gave up and flashed the latest firmware from my country. This phone originally came with German firmware in it and I flashed it to a Brazilian one, which is the one I'm using and had no issues so far.
Can this be a hardware issue?
Thanks in advance!
So I guess I'll end up solving this on the weirdest way I can imagine.
After I posted I logged into my modem's settings and took a log at its logs. Seems that the moment this issue started to happen was near the time that the DNS server my modem was using started to fail.
I never thought that such a simple thing could mess this things like this. I mean, the DNS server is essential, but how that could freeze my phone's WiFi? Either way, I changed the DNS to Google's DNS and since then I haven't had any freeze or disconnetion. I'll test a bit more to see if the problem is gone.
Well, I do believe that I found the root of the problem.
As some of you may know, modems tend to stay on for a very long period of time (no one wants to lose internet connection, so we rarely reboot then), and for reasons I don't know (and as a tech support guy I've seen this happen A LOT) they freeze sometimes and only work again after being completely turned off and on.
Since the issue started again when I was messing with the modem settings (trying to change the DNS again to see if the problem would return), I decided to give my modem a few minutes of rest.
After that, I've powered it on again and went through the initial setup (my ISP provides an simple wizard when you first connect to the WiFi) and up until now I'm not having issues.
I'll wait a few more hours to report again, but so far so good.
So it seems that giving those things a few minutes rest every month or so isn't a bad thing at all.