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
Hey Guys
I have been recently facing this issue on my Nexus 4 from the past 2 week.It happens once in every week.
The issue is that, when I am on a certain app, such as the camera it automatically shuts and another opens. Along with that issue, the phone automatically goes to home screen, opens different apps etc. The only solution i have found is that to leave the phone off for a while (15 min) and then switch it on again.
Could some one please help me out with this issue?
Hello, I'm facing this bug since some time ago (don't remember if this started with the pie update or not).
When scrolling an app (Twitter, Reddit, etc) sometimes it gets stuck and there's nothing I can do for it to become responsible again, the only thing that brings it back is pressing menu button and multitask to another app or to the same app that got frost and everything goes back to normal. It's weird. I think I has something to do with the screen shut down time because those freezes occurs when I stop scrolling for some seconds and when I want to scroll again it gets stuck as explained, probably approaching the time limit that the screen is set to shut down for inactivity... Also, when u try to scroll and realize it's stuck, when you multitask and get back to the app that got frost, you see that it actually scrolled it was just the screen/image that was stuck.
If there's anyone facing this bug or knows a fix?
Cheers.
when I want to open one of my apps via the "recent apps-menu", it takes a few seconds until it works. it does not react instantly. the issue occurs quite often and since Android 10
Barracuda79 said:
when I want to open one of my apps via the "recent apps-menu", it takes a few seconds until it works. it does not react instantly. the issue occurs quite often and since Android 10
Click to expand...
Click to collapse
I just noticed that, too. Started happening for no apparent reason. There was no delay yesterday, but today I can definitely see the issue. No reboots, updates, etc. Weird...
Restored a rooted G5 Plus back to stock firmware (re-locked bootloader). After restoring a number of apps the phone now freezes for 10 to 30 seconds after clearing the lock screen to access the device then every 20 to 40 minutes the same issue crops up again. Is there any way to figure out which app is the cause without going through another lenghty process of restoring to stock and reloading apps one at a time? Like a way to view some sort of log files that show which app is freezing or consuming all phone resources? Or an app that will do the same?
A few times I've had calls disconnect, listening to music freezes for short periods of time, and the System UI or what ever app is open will also freeze because of this.
And a second issue cropped up as well post restore to stock, getting a "Updating Bluetooth Context" notification that pops up briefly and disappears from time to time. Searching doesn't seem to indicate a solid root cause to this (like an app) but seems to be something some have had crop up.