Like the title says, on every 5.1 ROM I keep getting random reboots. They happen indiscriminately, with no clear reason at all. Other people report no issues at all. On 5.0.2 I have no issues at all. I have no idea what causes it could be or no knowledge on how to diagnose it...I want to use 5.1, but if this keeps happening I don't think I can ?.
I've not had any issues with random reboots, been running euphoria rom (updating with each new build) and glitch kernel for weeks with no issues.
Assuming you're doing clean flashes, with no extra mods, and not restoring system data, yes? Its even possible that restoring app data from backups can cause weird things to occur at times. If you haven't yet, wipe everything and clean flash, restore apps only from play store, and see if it still happens.
Otherwise, maybe a specific app is causing problems? You could try and grab some logs to narrow down the cause, but I know that's very tough to do if the issue is intermittent and seemingly random. Still it is the only way to tell for sure what's happening.
Here's a guide on how to grab the different logs if that helps at all: http://forum.xda-developers.com/showthread.php?t=1520508 .
LucentBirch said:
Like the title says, on every 5.1 ROM I keep getting random reboots. They happen indiscriminately, with no clear reason at all. Other people report no issues at all. On 5.0.2 I have no issues at all. I have no idea what causes it could be or no knowledge on how to diagnose it...I want to use 5.1, but if this keeps happening I don't think I can ?.
Click to expand...
Click to collapse
The random reboots are caused by outdated 5.0.2 binaries, if you update to 5.1 it should mend it random reboots. Also if your ROM developer might or will update the ROM to 5.1 with the updated binaries!
Killah1994 said:
The random reboots are caused by outdated 5.0.2 binaries, if you update to 5.1 it should mend it random reboots. Also if your ROM developer might or will update the ROM to 5.1 with the updated binaries!
Click to expand...
Click to collapse
Well I know for a while that some 5.1 roms were using the 5. 0. 2 binaries because the 5.1 weren't released yet... And they never really said whether or not they updated the binaries or if they were even released...I updated my tablet to a 5.1 R_5 this morning and it hasn't rebooted all day...so maybe they have?
LucentBirch said:
Well I know for a while that some 5.1 roms were using the 5. 0. 2 binaries because the 5.1 weren't released yet... And they never really said whether or not they updated the binaries or if they were even released...I updated my tablet to a 5.1 R_5 this morning and it hasn't rebooted all day...so maybe they have?
Click to expand...
Click to collapse
5.1 binaries and factory image for this device were just rolled out today. This may indeed resolve your issues, but give the custom rom devs some time to catch up, they'll need to grab the latest source and post new builds for the latest binaries to be included.
Same thing here
I excitedly loaded up the 5.1 build on my 2013 wireless today. SAME ISSUE. I can't do anything .
I didn't wipe the device when I upgraded. I was rooted - unrooted / flashed / rooted using the Nexus Root Tooklit as I have since Jelly Bean. I used the option to use NO WIPE MODE to try and keep my apps intact.
Any help appreciated.
mrdrumsc said:
I excitedly loaded up the 5.1 build on my 2013 wireless today. SAME ISSUE. I can't do anything .
I didn't wipe the device when I upgraded. I was rooted - unrooted / flashed / rooted using the Nexus Root Tooklit as I have since Jelly Bean. I used the option to use NO WIPE MODE to try and keep my apps intact.
Any help appreciated.
Click to expand...
Click to collapse
in that case you should try wiping then flash the 5.1 factory image and see if it works.
PrizmaticSmoke said:
5.1 binaries and factory image for this device were just rolled out today. This may indeed resolve your issues, but give the custom rom devs some time to catch up, they'll need to grab the latest source and post new builds for the latest binaries to be included.
Click to expand...
Click to collapse
cm12.1. rebooted once today while using chrome.
Reboots better!
I concur with the messages I've been seeing. After several app updates over the weekend, culminating in some Chrome updates, the tablet seems stable. I haven't re-rooted it yet.
I wonder if something has to do with the "notification crash" error listed in the changelog for 5.1.1.
Either way, looking forward to 5.1.1!
Hello, I think I have a really strange problem. I'm running Exodus 6.0 (and I made a full and fully functional backup that worked without issues) and yesterday I wanted to install AICP 12.0 (Android 7.0).
So I did a clean flash, but the SIM card detection didn't work and baseband showed up as "unknown" (according to the AICP members, I am the only one with such an issue).
So I tried several times but no success. They told me that it could be a problem of the 20G modem and bootloader. So I decided to revert back and since then I only have problems.
This is what I've done: Firstly, I flashed the 20D kdz. The phone booted fine. So I tried to install TWRP through ADB. (The phone was recognized and I was able to perform ADB commands). So I booted to bootloader, typed in the commands, but....nothing. TWRP didn't boot and I couldn't install it, no matter what I've tried. No I was on stock Rom without root and custom recovery, so I decided to revert back to Lollipop. I flashed the 10c kdz, flashed the rooted system image, wanted to flash TWRP (3.0.2-1) via Flashify, no success. Not until I tried TWRP 3.0.2-0, I had success and TWRP has been flashed. So ok, all fine now I thought, so I flashed the complete 20D stock Rom via TWRP, booted it up, worked. Now I wanted to give AICP a try again. So again installed, again no SIM card detection. With the CM 14 nightly 10/21 flashed afterwards (always clean flashed), success! SIM card was detected fine. So, again AICP tried and surprise, SIM card was detected as well. But now I had new problems: When I flashed SuperSU, SIM card wasnt't detected again.
Without SuperSU and stock AICP kernel, I suffered random reboots while setting up the WiFi connection in setup wizzard. Without SuperSU and Llama Sweet R7 kernel, I suffered a system crash and got a green screen saying something like "App F1Q: XPU Error!". So after some time I gave up and wanted to clean flash Exodus again, again no success, because the setup wizzard stopped (unfortunately:laugh:).
So ok, last rescue: My full backup. So I restored it (Exodus 6.0 10/22 nightly, opengapps pico 10/23, SuperSU SR1 2.78 in systemless mode, systemless xposed v86.2) and seemed to work fine. Today, I wanted to run SafetyNet Helper, and the phone suddenly rebooted. I wanted to run Pokémon Go, the phone suddenly rebooted. Nova Launcher can't get permissions for showing up unread labels correctly (though I have Nova Prime and all permissions are granted for sure!), other apps seem to work correctly. But all in all it's very strange because I have the feeling that somethink went completly wrong. So I don't know what I've done wrong, what do you think about this?
I've been having this issue where the touchscreen on my OP 5T will be working just fine but the next second just turn unresponsive to any touch, and no amount of rebooting fixes it.
So far, I've tried using the unbricking tool and restored it to OOS 5.1.3, wiped everything off the phone and tried the latest OOS 9.0.1, and even some custom ROMs like Pixel Experience, both the official Oreo version and some unofficial Pie versions.
I even tried installing custom kernels like the blu-spark kernel and the π kernel.
But here's the thing, all of these work right after making the change but the touchscreen stops working a day later. I'm still on the fence if this is a hardware or a software issue, because (do please correct me if I am wrong) a hardware issue would be if it was totally unresponsive and not work fine after installing a new ROM/kernel, which is not the case here, leading me to assume it has to be something in the software related?
gasburger said:
I've been having this issue where the touchscreen on my OP 5T will be working just fine but the next second just turn unresponsive to any touch, and no amount of rebooting fixes it.
So far, I've tried using the unbricking tool and restored it to OOS 5.1.3, wiped everything off the phone and tried the latest OOS 9.0.1, and even some custom ROMs like Pixel Experience, both the official Oreo version and some unofficial Pie versions.
I even tried installing custom kernels like the blu-spark kernel and the π kernel.
But here's the thing, all of these work right after making the change but the touchscreen stops working a day later. I'm still on the fence if this is a hardware or a software issue, because (do please correct me if I am wrong) a hardware issue would be if it was totally unresponsive and not work fine after installing a new ROM/kernel, which is not the case here, leading me to assume it has to be something in the software related?
Click to expand...
Click to collapse
Same problem. Did you solve this problem?
Has anyone found a permanent solution to this? Or at least a reason? My op 5t also stops responding randomly to the touch. This is really bad.
I also have this problem as well. It seems that many users have this issue. OnePlus should take a close look at it
I have been having this issue for more than 6 months. The problem came after one update during android Oreo if not mistaken (Which update i can't remember)
For my phone, the screen will be unresponsive during the below occasions:
1. After rebooting the phone, touchscreen is unresponsive for up to a minute
2. When browsing pictures in gallery
3. When taking picture using portrait mode
4. When google play is updating apps
5. When google photo is backing up photos.
I am also doubting if is a hardware or software issue, because it only happened in some occasion previously for my case. Tried wipe and install stable/open beta a few times, same thing.
After the latest open beta update, it got even worst, other than the above occasions, the screen start to stop working randomly (be it watching a youtube video or using chrome), its getting annoying as i need to restart my phone a few times a day.
I saw alot of people having this issue, but has yet to raise concern of OnePlus.
I've recently had the same problem, I was still running Lineage 15.1 and had not updated my firmware in months because the official builds switched to 16, then suddenly 2 weeks ago the touch screen stops responding while I was actually using it. Reboots didn't help, clearing cache and flashing lineage didn't help. In the end I somehow got it to work again by flashing the last open beta - but even then it didn't work right after flashing it, I had to leave it over night then it mysteriously started responding again in the morning.
I've just had it happen again and I have tried removing the screen protector and completely discharging the battery as some people on the oneplus forum have reported this helps, but it did not work for me. I really can't be bothered going through the whole process of re-flashing open beta then flashing back to lineage and installing all my apps an restoring my data again, but the only other option at this point is to try take it apart to check the screen is still connected to the motherboard properly....
solution
I also faced this problem, then i tried to degrade it to android oreo, and somehow i never faced touch issue, i think this is a bug in android pie,
karyy said:
I also faced this problem, then i tried to degrade it to android oreo, and somehow i never faced touch issue, i think this is a bug in android pie,
Click to expand...
Click to collapse
I'm not sure about that, the first time I had the issue appear I was still running oreo, as I mentioned, I hadn't updated anything in months due to the lineage nightlies switching to Pie.... That said, certainly seems like most people who have reported it mentioned upgrading to Pie
Facing same issue..
I have a similar issue too..
It started several months ago, when the screen used to randomly stop working, a quick hard reboot usually solved the issue.
But about a month ago, the screen stopped responding altogether and any amount of reboot did not work. So too the device to Oneplus service, there they flashed it to 9.0.7, and the screen started working again, and continued working for a few more hours, until it stopped responding again.
Tried flashing several times using the unbricking tool, but all efforts in vain.
Finally after a month or so, I bought a new phone, and today I just wanted to see if anything has changed on OP5T, and to my surprise, the touch screen started working again.
So this time I enabled USB Debugging, permanently enabled OTG, so that even if the screen stops working, I can use an external keyboard/mouse.
But OP5T is no longer my primary device, and hence I have moved on to a different manufacturer, as I saw absolutely no point in buying another Oneplus and god knows what will happen a year down the line...
Has anyone found a solution to this? I am facing the same problem with my oneplus 5T.
chandle-stick said:
Has anyone found a solution to this? I am facing the same problem with my oneplus 5T.
Click to expand...
Click to collapse
I had the problem. Had to send it back to OnePlus. They replaced the cpu under warrenty. Call 0neplus.
i have this problem on LineageOS 16, in stock is good
k-ninja said:
I'm not sure about that, the first time I had the issue appear I was still running oreo, as I mentioned, I hadn't updated anything in months due to the lineage nightlies switching to Pie.... That said, certainly seems like most people who have reported it mentioned upgrading to Pie
Click to expand...
Click to collapse
I was just searching this issue online. I'm currently facing it as well.
Rebooting the phone makes it go away. I face this issue while charging the phone via official dash charger.
I'm running stock Oxygen OS 5.1.7 running Oreo 8.1.0. I faced this issue 6-8 months ago as well. I cleared 7gb free space in my phone then it started working fine then. My device is 64GB variant. I never updated to Android Pie.
This is a major problem in OnePlus 5 and 5t. I've seen many posts on both XDA and official oneplus forums but found no guaranteed solution so far. I was thinking of flashing custom kernel but then saw here that people are still facing this issue in custom ROMs.
I thought I had solved the problem by installing the RenderZenith kernel, which someone on the oneplus forums recommended in the thread there dealing with this issue... but it has resurfaced after a couple of months without issue. Rebooting does not fix the issue for me, I have to flash a stock firmware, and sometimes reboot a few times, before the touchscreen starts working again. I tried installing CarbonROM instead of Lineage to see if that made a difference but it lasted about a day before the problem reoccurred. I am now going to try a Q-based ROM (probably Carbon) to see if that makes any difference, but I am not hopeful. I have even had the issue occur once while I was still running stock 9.0.9 and had not yet got to reflashing a custom ROM, had to do a full wipe and reinstall the stock ROM again to get it working.
I'm about ready to throw this phone in the bin and buy something new - only problem is I don't know what. Certainly not going to waste money on another oneplus after this debacle but there aren't many other options that are good for custom ROMs. Too bad OOS is such insecure trash and Oneplus as a company cant be trusted, otherwise I might at least see how I go running stock for a while.
k-ninja said:
I thought I had solved the problem by installing the RenderZenith kernel, which someone on the oneplus forums recommended in the thread there dealing with this issue... but it has resurfaced after a couple of months without issue. Rebooting does not fix the issue for me, I have to flash a stock firmware, and sometimes reboot a few times, before the touchscreen starts working again. I tried installing CarbonROM instead of Lineage to see if that made a difference but it lasted about a day before the problem reoccurred. I am now going to try a Q-based ROM (probably Carbon) to see if that makes any difference, but I am not hopeful. I have even had the issue occur once while I was still running stock 9.0.9 and had not yet got to reflashing a custom ROM, had to do a full wipe and reinstall the stock ROM again to get it working.
I'm about ready to throw this phone in the bin and buy something new - only problem is I don't know what. Certainly not going to waste money on another oneplus after this debacle but there aren't many other options that are good for custom ROMs. Too bad OOS is such insecure trash and Oneplus as a company cant be trusted, otherwise I might at least see how I go running stock for a while.
Click to expand...
Click to collapse
Have you tried Affinity kernel? Saw a post here. But it is for OnePlus 5
https://forum.xda-developers.com/showpost.php?p=79256461&postcount=95
archz2 said:
Have you tried Affinity kernel? Saw a post here. But it is for OnePlus 5
https://forum.xda-developers.com/showpost.php?p=79256461&postcount=95
Click to expand...
Click to collapse
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
k-ninja said:
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
Click to expand...
Click to collapse
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
---------- Post added at 08:23 PM ---------- Previous post was at 07:57 PM ----------
k-ninja said:
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
Click to expand...
Click to collapse
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
archz2 said:
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
---------- Post added at 08:23 PM ---------- Previous post was at 07:57 PM ----------
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I'm not running OOS now, but I have had the issue occur while I was. I am just re-flashing OOS to get the touchscreen to work again, but actually I can't even get the setup wizard to work once the phone boots (hangs on the "just a sec" screen), so I am usually flashing another custom ROM once the screen works again. I managed to get to about 6 hours of normal usage last night before the screen stopped responding again - after fighting with the phone all day and most times not getting much past installing magisk modules.
I am starting to think the problem is related to either Magisk, or the riru kernel hooking modules necessary for Xprivacylua (which is mandatory to install IMO) - I had been using the YAHFA module mostly but yesterday I tried Sandhook to see if it made any difference - that was when I managed to get to 6 hours instead of 30 minutes, but it was also when I went back to Magisk 19.3 instead of installing 20.2. Now that I think back, I am wondering if it was upgrading Magisk from 19.x to 20.x that made the issue resurface after a couple of months without it.... Can't remember for certain, but it seems like the most plausible explanation. I tried flashing Magisk uninstaller this time when the screen stopped, but it didn't help - only reflashing back to stock works (sometimes it even takes a few goes). Whatever the problem is, it seems like it is tripping some hardware related switch which only gets reset when installing stock FW.
the other thought I had was that perhaps the hooking framework is getting in the way - like it intercepts the screen touches before they are processed, but it bugs out for some reason and they never get passed on to the OS. I don't know enough about how it works honestly, or any idea how to go about debugging such a weird problem, so no way to look into it.
Anyway, to answer you other question - I never had the problem with OOS 5.1.7, I have never run stock OOS on my phone, but the first time I had the problem was with Lineage 15.1 Oreo 8.1.0. I can't remember if at that time I was running stock xposed or edxposed.
I'm close to my wits end here. IF the problem turns out to be magisk related, it's pretty much new phone time - I doubt even if I logged a bug report it will get looked at any time soon much less resovled, and I simply refuse to run an android phone without xprivacylua.
k-ninja said:
Anyway, to answer you other question - I never had the problem with OOS 5.1.7, I have never run stock OOS on my phone, but the first time I had the problem was with Lineage 15.1 Oreo 8.1.0. I can't remember if at that time I was running stock xposed or edxposed.
Click to expand...
Click to collapse
Edexposed is for Pie ROMS as there's been no development for Pie from official developer for xposed. Chances are you were running xposed only on Oreo 8.1.0.
Today I flashed Franco Kernel on my phone, been running smooth so far. I used to get non-responsiveness while dash charging specifically. Let's see how it goes. Will keep you updated.
Bugger it... I managed to get to 4 days or so after flashing back to LOS 16.1 / Magisk 19.3 / Edxposed YAFHA / Franco kernel, but it has just crapped out on me again.
This time I has tried a slowly-slowly approach, at first running just the stock OS and apps for a few hours, then gradually started installing magisk, riru, edexposed, then finally xprivacylua - Didn't have any problems up to there. Then I installed pico gapps, and used the Play store to do a fresh install of Mobius Final Fantasy instead of restoring from Titanium backup (this game is actually the only real reason I need gapps at all :-/). Mobius is a PITA because its like a 5Gb download, so it takes a long time to reinstall rather than restore from TB. Anyway it seemed like it was working ok for a few days after the fresh install but I just picked up the phone as couldn't unlock it. I have noticed that often the problem does occur while I am playing the game and I have wondered if there is something about it which makes it more likely to trigger, but it can't be the only thing as it happens even during the setup wizard sometimes.... bloody infuriating.
Anyway... not sure what to do now. Really CBF going through the back-to-stock dance again. Meh.