Related
Hiya folks,
Just wondering if anybody has been experiencing random reboots on the OP3. Have been experiencing em on 3.2.1 and 3.2.2 about twice a day since I got the phone four days ago. Tried a cache wipe/hard reset but to no avail. Haven't been able to reproduce the reboots. Just happen at completely random times, while writing an email, making a call, or connecting to the car Bluetooth. Phone is perfectly responsive and stable otherwise!
Have asked Amazon for a replacement, but I'm wondering if this is something that's been noticed by anybody else. No mods done, completely stock. Running dual sims (Vodafone and Jio VoLTE).
Attaching a screenshot of how the battery page shows the reboots.
Yeah, they happen for me periodically. Not nearly as often as yours though. Mine is maybe once or twice a week max. But yes, slightly annoying.
Phone is completely stock, locked, unrooted. Running 3.2.2.
mrhohoha said:
Hiya folks,
Just wondering if anybody has been experiencing random reboots on the OP3. Have been experiencing em on 3.2.1 and 3.2.2 about twice a day since I got the phone four days ago. Tried a cache wipe/hard reset but to no avail. Haven't been able to reproduce the reboots. Just happen at completely random times, while writing an email, making a call, or connecting to the car Bluetooth. Phone is perfectly responsive and stable otherwise!
Have asked Amazon for a replacement, but I'm wondering if this is something that's been noticed by anybody else. No mods done, completely stock. Running dual sims (Vodafone and Jio VoLTE).
Attaching a screenshot of how the battery page shows the reboots.
Click to expand...
Click to collapse
Haven't had a single random reboot yet, had the phone for about a month now. Started with 3.1.3, then 3.2.1, now 3.2.2, rooted, running xposed (not a lot of modules).
What are you doing when the reboots happen (an app issue)?
Hw4ng3r said:
Haven't had a single random reboot yet, had the phone for about a month now. Started with 3.1.3, then 3.2.1, now 3.2.2, rooted, running xposed (not a lot of modules).
What are you doing when the reboots happen (an app issue)?
Click to expand...
Click to collapse
It's been all over the place, but often when the screen was actually off! The way I would know would be I'd pick up the phone and see that it asks for the PIN post reboot. If it helps, I've enabled encryption. I also have a work (exchange) email account set up as a device admin
I know there's ways of investigating this with logcats and last_kmsg, but I've had the phone 4 days and I cant imagine why it's spontaneously rebooting while doing literally nothing. Seeing as hardly anybody has had similar reboots (on XDA/OnePlus forums), could this be a hardware issue at all? I could possibly try reflashing the entire phone, but that would essentially be the same as a wiping data/cache, right?
Here's an idea - my LTE data/VoLTE is extremely spotty (on Reliance Jio which is in a beta test stage) - disconnects and connects VERY frequently, could that be triggering reboots at the baseband level? Now throwing ideas at the wall!
mrhohoha said:
Hiya folks,
Just wondering if anybody has been experiencing random reboots on the OP3. Have been experiencing em on 3.2.1 and 3.2.2 about twice a day since I got the phone four days ago. Tried a cache wipe/hard reset but to no avail. Haven't been able to reproduce the reboots. Just happen at completely random times, while writing an email, making a call, or connecting to the car Bluetooth. Phone is perfectly responsive and stable otherwise!
Have asked Amazon for a replacement, but I'm wondering if this is something that's been noticed by anybody else. No mods done, completely stock. Running dual sims (Vodafone and Jio VoLTE).
Attaching a screenshot of how the battery page shows the reboots.
Click to expand...
Click to collapse
Mine had random reboot issues recently on a trip. It only seemed to happen when I was using Google navigation combined with listening to music on my bluetooth headphones. I haven't tried that combination since the trip and haven't had any reboots since then.
Here's an idea - my LTE data/VoLTE is extremely spotty (on Reliance Jio which is in a beta test stage) - disconnects and connects VERY frequently, could that be triggering reboots at the baseband level? Now throwing ideas at the wall!
same issue
the reboots are random, and i could only know that the phone has rebooted itself if it ask for a pin upon scanning finger, went to service center and has OS flashed, but the problem still persist, for me some time when the phone hangs, some kind of pixels form on the screen, attaching a sample photo for reference, anybody experiencing this issue or am i the only one, and today the phone has completely stopped working, it is not switching on.
sbzrsd said:
the reboots are random, and i could only know that the phone has rebooted itself if it ask for a pin upon scanning finger, went to service center and has OS flashed, but the problem still persist, for me some time when the phone hangs, some kind of pixels form on the screen, attaching a sample photo for reference, anybody experiencing this issue or am i the only one, and today the phone has completely stopped working, it is not switching on.
Click to expand...
Click to collapse
Wow that is substantially worrying, and almost certainly not just a software issue I reckon. Try getting a replacement maybe? - or atleast ask the service folks for a mainboard replacement. Anybody else with reboot issues?
Doesn't really seem to be an OS bug, unless it happens in very niche use cases which I don't have anyway! Getting the replacement on Tuesday, fingers crossed for that one!
My friend and I both got a one plus 3. He does not have this problem but I have.
The reboot is random but usually happens during charging. Sometimes it even turns off.
I have tried to ask for a replacement but they rejected me. Still communicating with the support staffs
mrhohoha said:
Wow that is substantially worrying, and almost certainly not just a software issue I reckon. Try getting a replacement maybe? - or atleast ask the service folks for a mainboard replacement. Anybody else with reboot issues?
Doesn't really seem to be an OS bug, unless it happens in very niche use cases which I don't have anyway! Getting the replacement on Tuesday, fingers crossed for that one!
Click to expand...
Click to collapse
Went to service center in Gurgaon, getting a replacement for motherboard, as oneplus policy doesn't give replacement handset, have to SETTLE for this, i dont know how many days this whole process is going to take, will update you guys about it when i get the phone back.
I have the same issue, random reboots usually when screen is off.
3.2.1, root + xposed... for me it started with 3.2.0 update
marleyfan61 said:
Mine had random reboot issues recently on a trip. It only seemed to happen when I was using Google navigation combined with listening to music on my bluetooth headphones. I haven't tried that combination since the trip and haven't had any reboots since then.
Click to expand...
Click to collapse
I experienced a similar scenario twice, only seems to happen on long trips, 3+ hours. I was using Waze with Plex streaming audio over car Bluetooth. I have not had this on shorter trips, 1-2 hours. I'm typically plugged into the dash car charger. Otherwise, haven't had issues. Never rooted 3.2.2.
Situation Update
Got the replacement OP3 on August 9. Have now seen 2 random reboots since. Once while paired to the car Bluetooth, once after finishing a call.
I have till August 19 to decide whether to keep this device or ask for replacement number two! Overall, the reboot situation is a lot better on this device, but I can't help wonder - why any at all?
Seems at this point to either be a bug with the Bluetooth implementation AND/OR with the dual SIM functionality where repeated switching between SIMs for every call. (I use one SIM for calls and texts, another for data)
Can anyone confirm the situation on a custom ROM as opposed to stock? I'm running stock 3.2.2
Aaaaand now we have an ota claiming to fix 'auto-reboot issues' - 3.2.4 :laugh:
The reboots were so sparsely documented compared to the other stuff that I ended up getting a replacement for a s/w issue!
Anyway - you folks reboot free now? Post results with 3.2.4 please
I had three back to back random reboots while using Google Maps and Amazon Kindle in the background. Weird.
I've yet to have a random reboot on 3.2.4
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Got my very first reboot :crying:
I'm on 3.2.4 with bl unlocked, rooted, Xposed, twrp
Had several reboots while driving and navigating on google maps one after the other. Maybe it is to do with the GPS sensor but its annoying coz you need it most when u r navigating turn by turn
jonynoname said:
Had several reboots while driving and navigating on google maps one after the other. Maybe it is to do with the GPS sensor but its annoying coz you need it most when u r navigating turn by turn
Click to expand...
Click to collapse
Agree. It happens only when I drive with gmaps running on background. When the screen times out, the phone, instead of shutting down the display, goes to hard reboot.
I've never had this issue until I moved to the latest update. Weird. Annoying.
I had my first reboot a few hours ago (with 3.2.4). I was connected to Bluetooth in my Car. Noticed it, as my car told me that mein Phone is now connected. No gmaps or something with GPS runinng.
Looks like Bluetooth is the Problem.
Nexus 5X 32GB - stock Android 7.1.2
Fact 1: The device presented the usual bootloop issue a couple months ago. I sent it to LG support for repair, where they replaced the entire PCB. For about a week after the repair the device behaved normally, then the freezing issue started.
Fact 2: After some factory resets and experimentation with installing/uninstalling apps I suspected might cause the issue, I unlocked the bootloader, flashed the latest stock Android 7.1.2 image (wiped user data/cache etc.), relocked the bootloader and kept using it normally.
Fact 3: A few days later from the flashing, the freezing issue came back.
Behavior: What happens is that the device randomly freezes when interacting with it (be it texting on a messaging app, scrolling through Chrome, expanding the notification bar etc.). When this happens, most of the times the device will stay frozen for a couple of minutes and then take me back to the lockscreen where I need to enter my PIN again to unlock it. Sometimes it will just reboot. And less frequently, it will give me an error message that "Google App has crashed". All of the times, when the device remains frozen, the back of the phone will get hot (but not extremely hot).
As you understand, I haven't yet managed to find the root cause of this issue, whether software or hardware induced. Nevertheless, the phone is rendered unusable that way and I want to investigate my options.
Any ideas? Your help is much appreciated.
I would see if your are still covered under the warranty and get it replaced with a unit that doesn't have the hardware issue.
Sent from my Nexus 5X using Tapatalk
I'm noticing similar behaviors on mine too. I have the latest Android 6 room installed instead of 7.
It started happening about 2 weeks ago. Was there an update on Google apps or the core platform recently that could be affecting the ROMs?
I have exactly the same problem! Except I haven't flashed anything. Mine has been stock all the time. So I don't think it is because of flashing.
They also replaced my phone's motherboard after bootloop. And now I have this random freezing at least once a day. Also I haven't been rooted or unlocked bootloader.
Mine is still under warranty.
Does anyone have an update?
I also saw this start happening on a stock 5x with no bootloop issues and no replacement hardware, roughly mid-May. Usually multiple freezes per day. Have not observed freezing for the last 5 days or so, though -- operating like normal again.
Just an update: Lately the issue happens a lot less frequently, but it's still there.
I suspect it has nothing to do with the ubiquitous bootloop issue (as mine has been repaired before the freezing issue appears, while @biff-torkington experiences freezes without having the bootloop issue).
Still no idea what can be done to remedy this situation.
No freezing at all in my 16 month old bullhead currently on stock rooted 7.1.2 with phasma kernel, no previous bootloops or hardware repair. I have never updated ota however and have run a custom ROM the majority of the time since I've had it, no idea if that would make a difference or not
The answer is simple:
2GB Ram + badly written ram hungry apps like messenger.
Best solution is to get another phone.Oh well...
I took delivery of a Tesla Model 3 on March 30 of this year. At the time, it was running Tesla's software 2019.5.15, but within a day it had upgraded to 2019.8.4, then 2019.8.5, then 2019.12.1 a couple of days ago, and finally to 2019.12.1.1 today. Through all of this, I've had no problems with Bluetooth connections to my OnePlus 5t phone for media streaming; however, I have had problems with placing and receiving phone calls, and the problem has gotten worse with Tesla's 2019.12.1 or 2019.12.1.1 (I'm not sure which).
I never tried making phone calls in the day or so I had Tesla's 2019.5.15, but I did with 2019.8.x, with about a 50% success rate. Sometimes it would work fine, but other times I'd get very stuttery sound, as if the connection was cutting in and out about ten times per second. Initially, I was running LineageOS 15.1; however, in part because I hoped to resolve this problem, I updated my phone to LineageOS 16 about two weeks ago. That update did not fix the problem, unfortunately, but it also did not make it any worse.
Since my car has updated to 2019.12.1 or 2019.12.1.1, though, the problem has gotten worse: Now, when I try to place a call, at best I'll hear a brief click, short series of clicks, or beep, and then I get silence. When receiving a call, the phone rings, I hear a ring tone over the Tesla's audio system, and the Tesla's screen shows an incoming call. I can answer the call via the Tesla's screen, but again, I get no audio. Worse than all of this, sometimes, on both incoming and outgoing calls, the Tesla's screen has gone completely blank a few times. This isn't guaranteed to happen, but it's happened at least four times to me today as I've been testing things.
Some of what I've tried, with no success:
Adjusting volume settings on both the car and the phone
De-pairing the phone and the car, rebooting both, and then re-pairing them
Updating the phone to the very latest LineageOS build (lineage-16.0-20190428-nightly-dumpling-signed.zip)
Using "developer mode" Android options to adjust every Bluetooth option I could find (AVRCP version, audio codec, audio sample rate, bits per sample, channel mode [stereo vs. mono], LDAC codec)
Testing with both incoming and outgoing calls
This same phone works fine with a Bluetooth headset. On my previous car (a 2017 Chevy Volt), I had few problems, although on about 5% of the calls, I did experience the stuttering audio problem that kicked up to 50% frequency with the Tesla before it stopped working altogether.
I've gone to Tesla's Web site and used their "contact us" link to file a bug report (although there was no "bug report" option, so it may not get routed correctly).
Does anybody here have any other ideas of what I could do, short of replacing my phone or installing another Android version? (I'm really trying to avoid the pain of setting everything up again!)
srs5694 said:
I took delivery of a Tesla Model 3 on March 30 of this year. At the time, it was running Tesla's software 2019.5.15, but within a day it had upgraded to 2019.8.4, then 2019.8.5, then 2019.12.1 a couple of days ago, and finally to 2019.12.1.1 today. Through all of this, I've had no problems with Bluetooth connections to my OnePlus 5t phone for media streaming; however, I have had problems with placing and receiving phone calls, and the problem has gotten worse with Tesla's 2019.12.1 or 2019.12.1.1 (I'm not sure which).
I never tried making phone calls in the day or so I had Tesla's 2019.5.15, but I did with 2019.8.x, with about a 50% success rate. Sometimes it would work fine, but other times I'd get very stuttery sound, as if the connection was cutting in and out about ten times per second. Initially, I was running LineageOS 15.1; however, in part because I hoped to resolve this problem, I updated my phone to LineageOS 16 about two weeks ago. That update did not fix the problem, unfortunately, but it also did not make it any worse.
Since my car has updated to 2019.12.1 or 2019.12.1.1, though, the problem has gotten worse: Now, when I try to place a call, at best I'll hear a brief click, short series of clicks, or beep, and then I get silence. When receiving a call, the phone rings, I hear a ring tone over the Tesla's audio system, and the Tesla's screen shows an incoming call. I can answer the call via the Tesla's screen, but again, I get no audio. Worse than all of this, sometimes, on both incoming and outgoing calls, the Tesla's screen has gone completely blank a few times. This isn't guaranteed to happen, but it's happened at least four times to me today as I've been testing things.
Some of what I've tried, with no success:
Adjusting volume settings on both the car and the phone
De-pairing the phone and the car, rebooting both, and then re-pairing them
Updating the phone to the very latest LineageOS build (lineage-16.0-20190428-nightly-dumpling-signed.zip)
Using "developer mode" Android options to adjust every Bluetooth option I could find (AVRCP version, audio codec, audio sample rate, bits per sample, channel mode [stereo vs. mono], LDAC codec)
Testing with both incoming and outgoing calls
This same phone works fine with a Bluetooth headset. On my previous car (a 2017 Chevy Volt), I had few problems, although on about 5% of the calls, I did experience the stuttering audio problem that kicked up to 50% frequency with the Tesla before it stopped working altogether.
I've gone to Tesla's Web site and used their "contact us" link to file a bug report (although there was no "bug report" option, so it may not get routed correctly).
Does anybody here have any other ideas of what I could do, short of replacing my phone or installing another Android version? (I'm really trying to avoid the pain of setting everything up again!)
Click to expand...
Click to collapse
Hello again from TMF (turok3000) . Can confirm I see exactly the same as you (lineage 16.0 + tesla 2019.12.1.1).
I would say you're best off posting here: https://forum.xda-developers.com/oneplus-5t/development/rom-lineageos-16-0-pie-oneplus-5t-t3843026
Do you happen to have tried with latest stock oxygenos ? I'm guessing not since you mention not wanting setup hassle (I'm in a similar situation).
Thanks for the suggestion of posting in another thread. I've done so, with a few updates.
I did back up the phone and tried installing stock OxygenOS as a test; however, the installation went badly -- it hung with a spinning logo on first boot. Thus, I restored my (mostly) working configuration. I may give it another try later, but there's only so much time I can invest in this sort of thing each day.
Any luck with this? I also have a Tesla Model 3 and the same exact problem as you. I'm using crDroid but it is largely based on LineageOS.
Maybe there is something I can try? I messed with all the dev options for bluetooth.
I've worked around it by re-installing OnePlus's OxygenOS. I'd prefer LineageOS or something else more open, but for the moment, switching to OxygenOS seems like the only solution. A caveat: I haven't tried any recent build (from the last month or so). It's conceivable it's been fixed and I just don't know it yet. Also, some others, using OnePlus phones other than the 5t (IIRC, the OnePlus 6 and/or 3) report that reverting to OxygenOS does not help them. If you've got a 5t, though, reverting to OxygenOS, although a nuisance, may be worth trying. There's a thread tracking the problem on a Tesla forum here:
https://teslamotorsclub.com/tmc/threads/bluetooth-problems-on-phone-calls-only.150774/
The problem is common on LineageOS for multiple phones, but it also occurs on some other phones, even including some iPhones. At least one unofficial LineageOS build is not affected; but that build may have been tweaked or rely on proprietary drivers. Overall, then, it looks like more of a Tesla problem than a phone problem, but it's hard to be sure without digging into the code and running diagnostics that I'm not competent to do.
srs5694 said:
I've worked around it by re-installing OnePlus's OxygenOS. I'd prefer LineageOS or something else more open, but for the moment, switching to OxygenOS seems like the only solution. A caveat: I haven't tried any recent build (from the last month or so). It's conceivable it's been fixed and I just don't know it yet. Also, some others, using OnePlus phones other than the 5t (IIRC, the OnePlus 6 and/or 3) report that reverting to OxygenOS does not help them. If you've got a 5t, though, reverting to OxygenOS, although a nuisance, may be worth trying. There's a thread tracking the problem on a Tesla forum here:
https://teslamotorsclub.com/tmc/threads/bluetooth-problems-on-phone-calls-only.150774/
The problem is common on LineageOS for multiple phones, but it also occurs on some other phones, even including some iPhones. At least one unofficial LineageOS build is not affected; but that build may have been tweaked or rely on proprietary drivers. Overall, then, it looks like more of a Tesla problem than a phone problem, but it's hard to be sure without digging into the code and running diagnostics that I'm not competent to do.
Click to expand...
Click to collapse
Ah well thanks for getting back. That is disheartening, as I had been using OOS since I got the phone on release day & finally thought I should try something different. It sounds like I'm gonna have to go through all the efforts to revert back to OOS.
For reference, it did not work for me using crDroid builds from 6/23/19 and 6/30/19.
I'll use Tesla's feedback system to put my "vote" in towards fixing these bluetooth issues.
My Model 3 received an update yesterday to 2019.24.4 and the Bluetooth calling works! Just thought you should know. I'll cross post on TMC.
Hello all,
Is anybody having issues with their Pixel XL or Pixel after they updated to the Android 10 October Patch in regards to random rebooting, flickering while charging or unplugging from charger, irrecoverable soft reboots, major lag when locking the phone (taking 20 seconds to actually lock and if you try to use it before it fully locks it will freeze in a state showing both the lock screen and the screen you were on previously) or navbar colours not updating. These issues have been persistent throughout ROMs and Stock Firmware even on Android 9 making me believe this is a hardware issue with the phone. I want to know if anybody else here has had these issues, i have seen them been reported elsewhere but not on xda yet.
Thanks
Nothing here, my Pixel XL does not exhibit the said problems (and I hope it remains that way ). It is indeed scary to see quite a number of people saying the final update from Google caused their phones to be bricked (on reddit that is). Nearly had a heart attack when it took longer than usual to restart the phone after accepting the OTA update.
No problems with mine either.
I have a constant reoccurring problem where the mic stops working. At first, I thought it was a hardware problem, but every time it has happened, it has been temporarily remedied by a reboot. After rebooting, it works fine, but then it will stop working again at an unexpected time. It is clear to me that this is a software issue. This makes taking calls and using Assistant virtually impossible.
I was planning on flashing a custom ROM on the device to see if it fixes the issue, but I found out that I have the Verizon boot-loader locked model. I did go onto Google's developer site and flashed the latest OTA but to no avail.
I need help. I have seen not a single other person with the same problem as me. This makes the phone completely useless AS A PHONE. I have been recently using a Galaxy Note 8 as a replacement, but TouchWiz doesn't cut it for me, as well as being a version behind.
It is a hardware issue, all pixels made before 02/2017 might develop that issue.