I enrolled to beta programa like 3 weeks ago and everything was just fine, but yesterday after some apps updated the phone started freezing a lot, all the apps started crashing especially WhatsApp and Instagram, when I unlock the phone it takes like 5 seconds, also a lot of times when I go to the home screen after writing something, the keyboard stays on screen and it doesnt hides, I dont know what is happening, if someone could help me I would thank it a lot.
Juandos23 said:
I enrolled to beta programa like 3 weeks ago and everything was just fine, but yesterday after some apps updated the phone started freezing a lot, all the apps started crashing especially WhatsApp and Instagram, when I unlock the phone it takes like 5 seconds, also a lot of times when I go to the home screen after writing something, the keyboard stays on screen and it doesnt hides, I dont know what is happening, if someone could help me I would thank it a lot.
Click to expand...
Click to collapse
Don't mean to scare you, but that is exactly what was happening to me right before going into an unrecoverable bootloop. Nothing I tried revived the device, although there have been some that have been able to. I ended up RMA'ing my device as nothing I did brought it back to life. You might be in a different situation but just giving you a heads up.
*Bump*
Stock 7.1.1 and rooted here. I've been on the official 7.1.1 release for our 6P's since early December, and for the past week or so, I've been experiencing freezing as well. I'd be in the middle of typing in Hangouts, streaming music in the car via bluetooth and Spotify, or just waking the phone up from sleep. For the past few days, I've been getting 3-4 freezes per day.
On rare occasions, I've left the phone alone to settle, and it returns to normal, but more times than not, a hard reset is the only 'fix'; until the next freeze.
I reluctantly wiped the phone, unrooted, flashed stock 7.1.1 and re-rooted all via NRT last night. The phone froze again this morning coming off the charger...
Granted, it decided to restore 528mb's worth of WhatsApp history as soon as I unplugged it (why it didn't restore on charger overnight is beyond me though). Will update if it freezes again.
The phone runs butter smooth with zero issues other than these freezing occurrences though. MO, the 6P is the best all-rounded phone currently available, even if it's a year old already.
Appreciate any help or suggestions!!
That's odd try ex kernel and over clock or try HEBF manager on play store
Quick update. Couldn't bear the multiple freezes per day, so I called Google to ask for help. Apparently I've done everything I can on my end (including a factory reset and updating to the latest firmware), so they sent out a replacement 6P to me free of charge. They'll also be covering the courier/shipping costs for my old 6P too. Fantastic customer service. Kudos to them!! I called them Tuesday morning (20th Dec) Australian time, and received my replacement 6P Friday afternoon (23rd Dec). Very quick indeed
Half a day after setting up my replacement 6P, including updating to 7.1.1, I started getting the same symptoms as my old 6P. Freezing, unresponsiveness, etc. Persisted for another day and had enough. I've since done a full wipe and downgraded back to the final 6.0.1 release, and it's been stable as a rock for 3 days now. No freezes, lagginess, nothing.
So I deduce it might actually be a software issue with 7.1.1, and not a hardware problem. It appears a growing number of Pixel and Pixel XL users are also experiencing random freezes on their new phones running 7.1.1 too...
Looks like I'll stick with 6.0.1 until Google makes a formal announcement and something is done about 7.1.1. I've missed Xposed and GravityBox too, so 6.0.1 is all good. Most importantly, it's stable
Had you ever tried booting into safe mode to see if maybe an app was causing the issue? Maybe a compatibility issue between an installed app(s) and 7.1.1
redduc900 said:
Had you ever tried booting into safe mode to see if maybe an app was causing the issue? Maybe a compatibility issue between an installed app(s) and 7.1.1
Click to expand...
Click to collapse
Thanks for the pro tip. I did consider doing that with the replacement 6P, but the only apps that I had installed were the stock Google ones that came with 7.1.1, WhatsApp, Facebook, Twitter, Instagram and SwiftKey. I just assumed if such popular apps were the cause, a lot more people would have pinpointed them as the problem?
I did however read a few users claiming SwiftKey to be the culprit prior to RMA'ing my old device, but even after uninstalling that from my old phone, I was still getting the freezing issues.
Related
I got a replacement device with stock rom recently and it suddenly started to experience stutters, lags and freezes frequently. For example, I'd be typing on the keyboard and suddenly everything stops responding. It happens in Chrome, randomly whenever I'm using the keyboard, and basically throughout the rom.
One solution is for me to wait 2 minutes and it might suddenly start responding. But the only sure solution that always works is for me to lock and unlock the device a few times (using the power button) and everything goes back to normal for two minutes until it lags and freezes again.
Thoughts anyone?
I had all the same previous apps on my previous Nexus 4 and had no problems....
RMA karma.......
........
These are tough to troubleshoot, but to narrow it down to hardware vs. software, I'd do a Factory Reset, and test, before signing into your Google Account and d/l'ing all your apps. If it works fine for a time/day, THEN sign in and only add a few apps (set Market auto update/restore off for the time being). Naturally do the apps your require daily first, and check stability for some time before adding back your 'fluff' apps. Often a poor app can be the culprit.
This happened to my nexus 7. I had it for about a month and i noiced that it started lagging really bad. Watching a video was just horrible and the responsiveness of it was bad. I just thought that it was a app or the custom rom i was running. I factory restored it and locked the bootloader and it still lagged. I just RMA'd it and i got a new one that was much better.
wideasleep1 said:
These are tough to troubleshoot, but to narrow it down to hardware vs. software, I'd do a Factory Reset, and test, before signing into your Google Account and d/l'ing all your apps. If it works fine for a time/day, THEN sign in and only add a few apps (set Market auto update/restore off for the time being). Naturally do the apps your require daily first, and check stability for some time before adding back your 'fluff' apps. Often a poor app can be the culprit.
Click to expand...
Click to collapse
Actually the keyboard is screwed up too. In gesture typing it randomly draws lower on the keyboard than I'm actually drawing. I'm guessing that it is a hardware or touchscreen sensor problem. I did an RMA and Fido Asurion promised to have a replacement to me by July 3rd. The only problem is that they only seem to send out refurbished phones for RMA's.
montrealguy said:
Actually the keyboard is screwed up too. In gesture typing it randomly draws lower on the keyboard than I'm actually drawing. I'm guessing that it is a hardware or touchscreen sensor problem. I did an RMA and Fido Asurion promised to have a replacement to me by July 3rd. The only problem is that they only seem to send out refurbished phones for RMA's.
Click to expand...
Click to collapse
Yeah..if it's acting up after a Factory Reset, then no amount of fiddling will solve it. Sorry man!
Hello everyone, I did some searching on what I'm going to ask but it seems as though all I've read were due to rooting and pertained to logins.
I have a new Moto XPE running the stock Sept. 1st Patch. I can log into Snapchat just fine, my issue lies after I'm using the app. Messages won't load in Snapchat and stories become stock on loading as well. On some Snapchat stories that are loading, after looking at a few images, the screen goes black and is again stuck on loading. Eventually the app crashes and sometimes the phone will crash as well to the point where other apps like YouTube just won't open up and the phone will either reboot on its own or require one from myself manually. Has anyone with a Moto XPE or Moto X Play experienced any of the issues I've described?
Thank you.
Holy crap, I thought it was just me, or that I was just going crazy.
Weird thing is I only started noticing any problems at all when I flashed from stock to a few of the various Nougat builds (CM14, then AICP, back & forth a couple times, then RR) which all have camera driver issues. I noticed half the time the camera wouldn't load upon starting snapchat, or if it did, it would take ~10 full seconds to change from the blank black screen, and sometimes if I would flip it to the front camera or vice versa, it'd just hang indefinitely.
That's the primary reason I switched back to stock a few days ago - I use snapchat A LOT and nougat just doesn't have enough cool features to justify one of my most-used apps basically being crippled to the point of not working the majority of the time. But once I restored my stock backup (not the September security update, the one before it) the camera started up fine in SC but I started getting EXACTLY all the problems you described.
The general consensus seems to be that SC is a super poorly-coded app on Android to begin with, but this must be a recent thing as it makes it downright unusable. I'm actually in the process of going back to 7.1.1 because that still works better than what the app's been doing lately. I wonder if it's happening on devices other than the MXPE?
jDally987 said:
Holy crap, I thought it was just me, or that I was just going crazy.
Weird thing is I only started noticing any problems at all when I flashed from stock to a few of the various Nougat builds (CM14, then AICP, back & forth a couple times, then RR) which all have camera driver issues. I noticed half the time the camera wouldn't load upon starting snapchat, or if it did, it would take ~10 full seconds to change from the blank black screen, and sometimes if I would flip it to the front camera or vice versa, it'd just hang indefinitely.
That's the primary reason I switched back to stock a few days ago - I use snapchat A LOT and nougat just doesn't have enough cool features to justify one of my most-used apps basically being crippled to the point of not working the majority of the time. But once I restored my stock backup (not the September security update, the one before it) the camera started up fine in SC but I started getting EXACTLY all the problems you described.
The general consensus seems to be that SC is a super poorly-coded app on Android to begin with, but this must be a recent thing as it makes it downright unusable. I'm actually in the process of going back to 7.1.1 because that still works better than what the app's been doing lately. I wonder if it's happening on devices other than the MXPE?
Click to expand...
Click to collapse
It happened on my BlackBerry Priv too. I just switched over from that device a few days ago
I'm on stock 6.0.1 and I don't have any big issues with snapchat, the only one is that sometimes camera is very dark at start and I have to go to messages and back to camera to fix that
iks8 said:
I'm on stock 6.0.1 and I don't have any big issues with snapchat, the only one is that sometimes camera is very dark at start and I have to go to messages and back to camera to fix that
Click to expand...
Click to collapse
Yeah same here, it can get a little laggy sometimes for me but I just log out and back in and it works fine.
This might not be here nor there for this specific issue, but if you use Xposed/Snapprefs/rooted etc etc...One thing I noticed that REALLY causes a lot of lag with snapchat is overlays. Especially the FB Messenger app. If you have those chat heads on your screen with Snapchat open as well, things are basically unusable until you get back to the home screen and force close both apps. Could be happening without Xposed as well. Just a thought.
On a side note about Snapchat in general- it has always run like crap on every phone I've owned.
Snapchat kept screwing up, even tried the beta. Decided to try Casper and so far it's working great
Hi folks
I received my OP2 in July 2016, and this issue has been a mild periodic annoyance. As I approach the end of my warranty, I want to be 100% confident that this issue is software rather than hardware... (so rather than a fix, my highest priority is confirming that I do not have a hardware defect)
The issue is that the screen rotation will stop working for most, but not all apps (OnePlus Camera is the sole exception, it seems). It will rotate normally for a couple weeks and then I'll notice in some app, usually YouTube or Facebook first, that the screen orientation won't rotate anymore. Once I notice it in any app, no other app rotates either except the stock camera. I have been experiencing this symptom on-and-off for most of the time I've had the device, spanning multiple OOS releases (currently 3.5.8 and still happening).
A reboot fixes the condition, then it works fine for a week or two and comes back. OnePlus support suggested a factory reset, which I've done pursuing this issue before, and it didn't help (it immediately helped, obviously, but the issue did return on the same schedule as before).
I had my OP2 rooted, but still using the stock ROM otherwise, for several months (to be able to use Adblock). I reverted to 100% stock configuration pursuing this issue, it happened the same before/during/after the time it was rooted.
I have checked out the accelerometer with the app "Test Your Android" and watched the graph in the "gravity sensor" test. When the phone is in its non-rotating state and I rotate the phone, the graph lines cross but the app stays in portrait. This makes me think the phone knows it has rotated. I reboot the phone, redo the same test, and the graph looks similar except the app now rotates as well (ironic, really).
Is there a background service for "screen orientation" similar to how Play Services provides GPS information to other apps? If so, am I right in suspecting that the service responsible for answering the question, "what way is the device oriented currently?" is either not answering, or answering incorrectly?
I would prefer not to go to a third party ROM just to test this as I'm very happy with the current config of my device, other than this issue popping up from time to time. Any input is appreciated.
Thanks!
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
utkarsh102 said:
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
Click to expand...
Click to collapse
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
k1shy said:
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
Click to expand...
Click to collapse
In case you want suggestions, try these:
Bliss
Halogen
Validus
Lineage 13
Well, I have the same issue on my OP2 intermittently and it does not matter which rom I am using. In addition to OOS, I have had this issue on Marshmallow Cyanogenmod / Nougat Lineage based roms. Sooner or later it always returns. It seems to happen after longer uptime periods. E.g. with OOS3 I had an uptime stretch of 40+ days (without a reboot), so during this time I experienced the autorotation issue multiple times. It seems to get fixed by itself, but then comes back again. A reboot fixes it usually for longer period of time. As I am now on a custom rom, which is updated quite often, at least once of twice a week, the uptime stretches are not that long and I do not experience this issue often. I have noticed that the step counting sensors also stop working intermittently.
On rooted lineage based rom you can manually restart the sensors with following terminal commands:
su
stop sensors
start sensors
Don't know if this works on OOS. I made a tasker task shortcut for this on my homescreen.
Interesting...I have had the problem on-and-off I'd say, sometimes it follows this ~2 week pattern, sometimes it'll go longer than a month with no issues that I've noticed. Of course, it's also fairly rare that I watch videos on my phone and this is the main time that I realize it won't rotate.
Of course, with the current trend being to make all videos square with unnecessary obnoxious text in the letterbox black space, I suppose I'll never need to rotate my phone again </sarcasm>.
Prior to utkarsh102's suggestions I had already flashed AOSPExtended so I'm going to try rolling with this for a short time, if any issues surface (unrelated to my rotation issue) I'll try another ROM. Given that I'm trying to diagnose this issue before my warranty runs out (yeah, shoulda done it sooner, I know) I'll need to have a usable solution that can run stable for weeks uninterrupted to catch this again, if it's going to happen again.
FYI OnePlus support was entirely unhelpful about this issue. They completely disregarded the fact that it is intermittent and was not currently happening when I reported it to them. They were not able to suggest any diagnostic effort I could take to narrow down the issue further. Viewing the accelerometer readings was my own idea, not theirs. That suggestion absolutely should have come from them.
I do know I'm/we're not isolated in having this issue as there are other forum posts on various sites complaining of it.
I'll keep this thread updated with my findings, in the meantime anyone who has experienced this issue please chime in. It would be helpful to present to OnePlus, though I get the impression they won't care as they seem to have classified the 2 as a legacy product at this point. It's not like we're trying to get parts for a dot-matrix printer here.
Edit, October 2017, to provide an update without bumping the thread:
I've been using AOSPExtended on a constant basis since my last update to this thread and while I have experienced a variety of other issues, this particular one with the screen rotation has not affected me. My uptime has never been super long, but long enough at times that I should have seen this issue if it were going to happen following the same pattern as before.
Is there any way to figure out what's causing a random reboot?
I'm rooted, running A-O Rom, which is almost stock Android 8.
I got a random reboot when I used the camera the other day (it took about 5 pics and then rebooted).
Today I got a random reboot in the middle of playing "Words With Friends."
I've never had any issues with these apps before. Since it was today and 3 weeks ago, I doubt it will happen again soon, but I don't want it to happen again at all, especially since I'll be going on vacation soon and needing it for pics/alarm clock/phone/etc.
Any suggestions?
baldybill said:
Is there any way to figure out what's causing a random reboot?
I'm rooted, running A-O Rom, which is almost stock Android 8.
I got a random reboot when I used the camera the other day (it took about 5 pics and then rebooted).
Today I got a random reboot in the middle of playing "Words With Friends."
I've never had any issues with these apps before. Since it was today and 3 weeks ago, I doubt it will happen again soon, but I don't want it to happen again at all, especially since I'll be going on vacation soon and needing it for pics/alarm clock/phone/etc.
Any suggestions?
Click to expand...
Click to collapse
Could be just Oreo. Im on stock temp root and get random reboots, way more then nougat.
I ran A-O's 8.0 for almost a year without any reboots...
Any other ideas from anyone on how to diagnose this? or fix this?
I have an Australian bought Pixel 4, build: QQ1B.200205.002, Security patch level 5 Feb 2020, stock factory firmware, not rooted. Bought it on the first week of release, so had it for a while now.
Since about a week ago my phone stopped responding to the "ok-google" hotword in sleep and locked modes. Restarting the phone temporarily fixes it, but it stops again after a while. Especially if I don’t use the phone for an hour or so.
It used to work quite reliably before. Voice match is enabled, also retrained the voice model but that didn’t help. Haven’t installed any new apps recently, nor recall changing any settings. I only have a handful of very popular 3rd party apps like Waze, Tunein, Skype, Outlook, Viber, Whatsapp a couple of banking apps etc., but no games or optimiser apps of any sort.
Any ideas?
Thanks.
I had similar issue. I had to disable battery optimisation for the Google app. Seems to have cure it
Thanks for the reply, I tried changing battery optimizer settings for Google app, failing that I even did a factory reset. Still nothing. Looks like I’m not alone with this particular problem: https://support.google.com/pixelphone/thread/27204195?hl=en
Check your case, small cutouts affected my microphones on my Galaxy Note8 two years ago.
Received the march update, but the problem still exists.
vonDubenshire said:
Check your case, small cutouts affected my microphones on my Galaxy Note8 two years ago.
Click to expand...
Click to collapse
Pretty sure the case has nothing to do with it, because it used to work fine with the same case till a month ago, it works for a while soon after the phone is restarted, and there are many others experiencing the same problem as noted in the above google community thread.