Hi folks
I wonder if any of you is encountering the horrendous issue of slowness in opening websites with Chrome, Firefox and stock browser unless I reboot the phone.
It's really weird because the web address is found and opened immediately, but the page stays white and loading almost 90 % for about a minute before it finishes loading and showing the site entirely.
But as soon as I reboot the device all browsers load fast and open websites immediately.
I have no idea what app causes this or how long time passes before the slowness begin.
-Cache deletion doesn't help.
-Uninstalling and reinstalling doesn't help either.
I appreciate your feedback on this.
Related
Anyone have the same bug? It happens on some sites, the site loads but when scrolling it just returns to my home screen without a notification why....so no forceclose i guess?
I only have this when I use (install) flash, so I stay away from it untill 3.1 and wil test again.
I have the same issue sometimes. It happened once today, actually. It's really very rare for me so it isn't that big of a deal and I'm sure that whatever is causing it will be addressed in an update soon. Just wish that update would arrive sooner than later. =/
ibila said:
Anyone have the same bug? It happens on some sites, the site loads but when scrolling it just returns to my home screen without a notification why....so no forceclose i guess?
Click to expand...
Click to collapse
I have had it a few times with www.nu.nl.
Scrolling is not even neccessary, it justs closes to the home screen after a few seconds. Have had it a few times now.
Robin
Has happened exactly twice for me, that's less often than Firefox 4 crashes on my desktop so I'm not worried
I'm using a case with a magnet in it to automatically turn the screen off/on but have been having issues with the device rebooting after closing the case. I would close the case, the screen would turn off and when I'd look at it next I would see that it had rebooted as I am displaying the system uptime on the lock screen.
I've found that this only happens if I have been using Chrome to browse. If I go back to the home screen leaving Chrome in the background and close the case it will reboot every time. If I go back to the home screen open up the last used apps list, swipe chrome out then close the case it never reboots. It seems like a software issue.
I need to see if it makes any difference if I use the on/off button rather than the case and if it will reboot if the screen shuts off automatically. I also need to see if it matters if Chrome is in the foreground or background. Either way, the reboots only occur if I have been using Chrome.*
Anyone else having the same problem?
Running unrooted stock JSS15Q.
Chrome triggers my random reboots whether using case or not. Switched to dolphin, random reboots gone.
I am not saying chrome is the trigger for random reboots for everyone as I believe there are multiple causes.
I use a smart case and with neither Chrome nor the AOSP brower was I having reboots.
Just my $.02.
Chrome is likely to cause some reboots. Simply freeze or uninstall the app with eg. TB and the problem is solved. I never had any random reboots since I´ve got rid of some Google junk apps right after having rooted the device :laugh:
I prefer Firefox since you can use the Adobe Flash with it without any problems. It may be a bit slow but in the end it doesn´t matter if you wait one second more or less, as long as you can watch every desktop homepage available..
The GPU doesn't suspend properly resulting in an auto-reboot. The bug should be fixed soon:
https://code.google.com/p/chromium/issues/detail?id=286378
(There is a kernel bug triggered by Chrome; a Chrome workaround will be released first.)
tni.andro said:
The GPU doesn't suspend properly resulting in an auto-reboot. The bug should be fixed soon:
(There is a kernel bug triggered by Chrome; a Chrome workaround will be released first.)
Click to expand...
Click to collapse
My understanding is that this bug is triggered by Chrome 30 beta only-- normal Chrome is fine. Google already has a fix in the works.
That may be the case for the specific bug being referenced, but there are likely multiple issues causing reboots as I have consistently triggered reboots using stock production chrome.
The thing is "reboot" is a very non-descriptive way of describing a bug (from the standpoint of understanding the real issue). Of course it is what the end-user encounters so they will lump all reboots together.
Did the unit reboot because of kernel panic, was it in driver triggered by user space apps usage of different features, was the reboot caused by android not not pinging watchdog because it became non-responsive, was there an issue with the WiFi driver or did shutting off WiFi just hide a bug in network log rotation, was there issues with elpida ddr3 memory not retraining properly causing memory corruption.
All these and many more could be responsible for a percentage of what the end-users have lumped together as the random reboot problem.
Yes, I've had reboots not linked to using Chrome beta also, but they are fairly rare (for me, anyway).
The chrome beta reboot is 100% reproducible-- start chrome beta, then put the tablet to sleep and it'll reboot under a minute later.
All of my reboots have been while in chrome. In fact, if I catch chrome being unresponsive and close it in time, I can avoid the reboot. A brief chrome freeze is the catalyst for my reboots every single time. If this thing didnt reboot so fast Id be really irritated about it. Ive been up a total of 3 days now, versus 3 reboots per day, ever since switching over to lightning.
Chrome Beta started causing my Nexus 4 to randomly reboot starting sometime last week I'd say. Regular Chrome doesn't cause any issues that I've noticed.
I suppose this is why they call it "beta" and hide it unless you have the link!
Weird, I have rebooted just by browsing this thread on tapatalk. No chrome installed whatsoever. Sigh..
I switched to CM 10.2 nightlies and my reboots are now gone.
rodalpho said:
My understanding is that this bug is triggered by Chrome 30 beta only-- normal Chrome is fine. Google already has a fix in the works.
Click to expand...
Click to collapse
+1
The non beta version works fine. I use it daily with no reboots ever.
Sent from my Nexus 7 using xda app-developers app
Helll everyone there is something weird going with my phone and all Google services.
I currently use dorimanx kernel and Cloudy stock
Ok my problem now. As I surf the Web Chrome beta starts not to connect to anything apart from Google displaying errors like err_name_not_resolved or something about the dns, and play store times out in just one second whilst uc browser or dolphin keeps going on and loading the same pages that give the errors to Chrome. Also cannot access Google drive while these errors appear. After rebooting nothing happens but when I press "forget" on wifi network and reconnect everything goes normal. What is going on with my g2?
Anyone can help?
Thanks for your time.
I have a Nexus 6P running a custom ROM and kernel (Purenexus & Elemental X) and 6.0.1 is its current version. My problem is that most of the time I try to access a Web page via Chrome or any other browser it doesn't loads, the loading bar gets sort of stuck about 1/4 of the barbar, I hit refresh and nothing, my WiFi is pretty fast and this happens to me with every WiFi I use and even with my own data connection LTE. I found a way to get out of the being stuck by hitting the recent apps button and accessing again to the browser and it loads the page FAST, but I can't deny it's annoying that I have to that everytime single time that I get stuck. Like I said, my connection is pretty good but even though my Web pages don't load and remain blank.
Hi folks,
I let my phone (6T, international version, completely stock never rooted), update to Android 11 this morning.
One thing is bugging me so far: at random times, I'll get brief flashes of some other window popping up momentarily (too fast for me to see what it is), and then it goes away. But it throws games into pause mode and takes me out of the flow.
What's causing this and how do I turn it off?
Welll this is not a normal behavior, so noone know why and how. Seems android 11 is not yet stable for us. I rolled back to android 10 on my 6T mclaren
Progress update: this problem seems to have resolved itself. I think it may have had to do with each app gradually settling in. A few reboots and some hours later the phone seems stable, though I'm having a few smaller issues like my phone icon left my home screen, I've now got TWO "Contacts" apps, and other minor stuff.
More update... the popups are back. I think they happen frequently after a reboot then settle down over time. I will keep an eye on it and report back anything I find in case it helps others.
Partial solution: I filmed what was going on in slow motion and despite my hand being in the way I saw the popup said "Gallery kee" presumably "Gallery Keeps Closing" or something like that. I don't use the Gallery app so I disabled it in Settings\Apps. Let's see if the problem keeps up. Maybe other apps are also contributing, and I'll have to address them one by one.
After a full day and another reboot for unrelated reasons, I can confirm that disabling the Gallery app fixed the problem. Not a single popup since I disabled it. Since I never use Gallery, only Google Photos, for me it's no loss. Probably a cache wipe would have sufficed as well. I did a a full cache wipe today to address a Gmail issue, and at some point I'll re-enable Gallery and see if the problem recurs despite the cache wipe.