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.
Related
As the title states, the camera on my Nexus 5x is completely unusable. My bootloader is unlocked and I'm running MHC19J. This issues happens on MHC19J and on Android N 90% of the time. When it does work, both cameras works fine. I'm am currently on MHC19J with no applications installed and the phone crashed and rebooted. After the reboot the camera works but I have no confidence it's going to stay this way. I have noticed another user on this has the same (or at least similar issue) which was caused by ditry-flashing MHC19J however, I have flashed the factory image from Google.
This issue started a few days ago. I think the issue started after flashing elementalX (eas preview version) on a stock rooted MHC19J.
If you think it's related to the kernel grab logs and post them in the kernel thread since you clean flashed to begin with. I'm sure flar would like to see them if it is the cause. I'm using the same kernel on Omni without that issue.
You can also return to stock (and potentially to a different version) completely and see if it occurs again.
Keithn said:
If you think it's related to the kernel grab logs and post them in the kernel thread since you clean flashed to begin with. I'm sure flar would like to see them if it is the cause. I'm using the same kernel on Omni without that issue.
You can also return to stock (and potentially to a different version) completely and see if it occurs again.
Click to expand...
Click to collapse
Thank you for the reply. I cannot get the logs becuase I have since flashed many different factory images. However, even on completely stock, the issue still occurs.
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage. But none of these roms allow the T800 boot to get beyond the initial splash logo screen. I am using latest TWRP, 3.1.1 to wipe and install rom. I am not getting any install errors. Boot loader is confirmed as CPK2.
FYI, I am able to get back to the samsung rom by reflashing it with Odin.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
mach281 said:
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
Click to expand...
Click to collapse
My wife has the US Cellular 10.5 variant (T807R4). It was freezing so frequently it had become almost unusable for anything but watching videos. Rooting and disabling most of the Samsung apps did not fix the problem. I wiped the system with TWRP only to discover that none of the custom ROMs would work on this model. I downloaded and flashed the stock Samsung MM firmware (and it sat on the opening splash screen for at least 15 minutes before it finally booted up) and for the hour I used it after setting it up, I had no problems. I had previously cleared the cache with Titanium Backup and that also seemed to be a temporary fix. My conclusion is that something is happening when the cache fills up that causes the freezes but I'll need more data to say that for sure.
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
mach281 said:
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
Click to expand...
Click to collapse
Please explain the steps to install 7.1.2 (and which ROM you used) and update on the freezing issue. Most of the freezing issues I have read about seem to be on LTE variants (SM-T807x) so I was about to buy a wifi only (T800) tablet, thinking that would be a solution to the problem. If that's not the case, then I shouldn't waste my money.
The instructions for installing a non-stock ROM are on the dev's host page in Tab s forums. I first tried Resurrection Remix and now am on LineageOS. It was only after I wiped the internal storage area that I was able to get past the 7.x.x boot screens.
I found the stock rom 6.0.1 freezing issue persistent. I believe the problems started for me with XAR H4 and really picked up with K2 (roms supplied by sammobile). The tablet would frequently just freeze while working in an app: the screen and hardware buttons would not respond at all. Never had that problem with Android 5. The only thing I was able to do to unfreeze it was to reboot into download mode then restart the OS from there. I sometimes found that if I left it frozen overnight it would unfreeze itself by morning.
Hi guys,
I updated my op3 to latest beta 28 but I got random reboots when I'm not using it;
in fact, usually it reboots when charging or when it's in standby, and other moments like that.. I really don't know why!
I checked the MD5 of the zip, I flashed with the latest bluspark 8.54 and I did a full wipe;
I also reflashed with a dirty flash the ROM(and other ROMs based on Oxy).
Nothing changed.. it appears 2-3 times per day.
Anyone of you got the same error? which could be a solution?
I had exactly the same problem, but flash rom via adb fixed that.
not experiencing any.. stock non rooted...
Kshysiek said:
I had exactly the same problem, but flash rom via adb fixed that.
Click to expand...
Click to collapse
Sounds interesting.. will try! Thx in advance
Morning! You're not the onlyone having troubles with OB28, I'm facing similar issues aswell. Decided to wipe all and perform another clean install (not via adb as suggested above) yesterday afternoon and no issues so far. Will keep you updated
Running ExperienceOS by Jamal btw, which is based on stock OB28
I have had this as well. Just keeps rebooting randomly.
Dirty flashing the rom ob28 helps and keeps it stable. But then it reappears after some time randomly. It could be after a few hours or a day or two as well. Yesterday it just started rebooting while it was lying on the desk.
I suspect it could be because of a custom kernel. I have moved from custom to stock (rooted) for now. Lets see
Having same with ob28 also with 5.0. Sometimes it starts rebooting when charging, sometimes while just laying on the desk. 2 times I had it rebooted to recovery. I have even missed an alarm. I found a phone rebooted to recovery in the morning.
Yesterday clean installed 5.0. Rebooted 10 minutes ago. Dirty flashed ob28, retooting also.
Sent from my ONEPLUS A3003 using Tapatalk
In another thread, someone suggested rooting with SuperSU instead of Magisk. Tried that and now stable of over 2 days. You might give it a try
It has something to do with magisk or bluspark twrp in combination with something. Tried installing Supersu. Rebooting stopped, but dm-verity message appeared when booting. Decided to format everything. Flashed original recovery, but it could not decrypt file system. Tapped on forgot my password and it wiped everything. Sideloaded OOS 5.0, rebooted, then flashed twrp via fastboot. Flashed magisk 14.5. Stable for 2 days.
Sent from my ONEPLUS A3003 using Tapatalk
I have 2 oneplus 3 (one for me and my wife). I installed on both the latest beta Hydrogen OS (basically the same version as OB28).
On both devices, magisk 14.5 is installed.
And yes, I received random reboots maybe 1-2 days one time. And once rebooted, sometimes it will reboot again few seconds after that for few times.
Usually to stop that, after the reboot done, I will reboot the phone manually as fast as possible. And it will be okay for another 1-2 days.
So far I can live with this. But I might downgrade my wife's phone to something else stable
creezalird said:
I have 2 oneplus 3 (one for me and my wife). I installed on both the latest beta Hydrogen OS (basically the same version as OB28).
On both devices, magisk 14.5 is installed.
And yes, I received random reboots maybe 1-2 days one time. And once rebooted, sometimes it will reboot again few seconds after that for few times.
Usually to stop that, after the reboot done, I will reboot the phone manually as fast as possible. And it will be okay for another 1-2 days.
So far I can live with this. But I might downgrade my wife's phone to something else stable
Click to expand...
Click to collapse
Same behaviour here on OxygenOS 5.0 with Magisk 14.5 and Boeffla kernel. I usually wipe cache and dalvik in TWRP 3.2 and then it's fine for a couple of hours (or days, if I'm lucky).
Quick update from my side. It's been 6 days since I replaced Magisk and rooted with SuperSU and it definitely solved my issues. No reboots or whatsoever.
basvanasperdt said:
Quick update from my side. It's been 6 days since I replaced Magisk and rooted with SuperSU and it definitely solved my issues. No reboots or whatsoever.
Click to expand...
Click to collapse
Same here
Been in SuperSU for 3 days. No issues so far
Op3 ob28
I had random reboots on Freedom OS 3.1 after about two weeks of use with stock kernel and Magisk 14 (no issues before that). Flashed Blu Spark 207, didn't help. Flashed FOS 3.2: neither. Somebody suggested aggressive dose to be the culprit. It wasn't as I didn't had it enabled for starters. I Flashed official OB28 + magisk and stock kernel... And after one day, reboot. Flashed Blu Spark 208, reboot. But after a couple more reboots last week, they seem to have gone by themselves:
$ uptime
02:00:49 up 4 days, 6:48, load average: 2.98, 2.01, 2.24
*I had not tried using super su instead.
What can we do to debug this issue? Seems like everybody is trying to guess in the dark...
---------- Post added at 09:31 AM ---------- Previous post was at 09:10 AM ----------
If I may suggest, there seems to be a sort of "environmental" origin for this... I've noticed some "correlated incidence of reboots" between unrelated devices, regardless of specific OB variant (OB, FOS, EOS), kernel (stock, Blu), and root method, based on number of complaints and reports of generically unsuccessful attempts to solve the issue in the respective ROM threads, and here too.
Besides, I've not been able to identify any usage related trigger: this has happened to me while phone is idle, while browsing this thread, while driving thru unknown and dangerous streets guided by Waze, while commuting on the subway and only listening music...
Some more rigurous analysis of the prevalence of these reboots as a function of time might prove useful...
Also, there seems to be a growing incidence between users. There seems to be also a "incubation time" for most of us (but not for everybody). Are we sure we are not talking about some disease?
Just had another reboot. No Magisk log created...
But on every reboot I seem to lose some settings (in the settings app). Which setting is lost, seems completely random: battery optimization setting, LED notification setting, configured sounds,...
Aaand..... Two reboots lastima friday, and about 5 today...
This Is turning into a real deal breaker...
Experiencing back to back reboots form morning on stable Oreo op3. Imma switch back to 7.1 til the time its solved
I also have problems with reboots, but they have given way. Now I have a problem with the phone's sudden heating and battery drain this.
simpele said:
Just had another reboot. No Magisk log created...
But on every reboot I seem to lose some settings (in the settings app). Which setting is lost, seems completely random: battery optimization setting, LED notification setting, configured sounds,...
Click to expand...
Click to collapse
strange1712 said:
Aaand..... Two reboots lastima friday, and about 5 today...
This Is turning into a real deal breaker...
Click to expand...
Click to collapse
abhibnl said:
Experiencing back to back reboots form morning on stable Oreo op3. Imma switch back to 7.1 til the time its solved
Click to expand...
Click to collapse
Kshysiek said:
I also have problems with reboots, but they have given way. Now I have a problem with the phone's sudden heating and battery drain this.
Click to expand...
Click to collapse
Those experiencing reboots .. pls specify if it's with or without magisk. And if it's with, which version. And if it's without, what other modding have you done.
Will be helpful to establish the common thing in the setup causing the reboots
candiesdoodle said:
Those experiencing reboots .. pls specify if it's with or without magisk. And if it's with, which version. And if it's without, what other modding have you done.
Will be helpful to establish the common thing in the setup causing the reboots
Click to expand...
Click to collapse
With magisk 14.0 and later magisk 14.5. Now I'm testing without root at all, as it seems to be magisk related, it is also reported on the magisk thread.
Can say definitively that 3.0.2-0 is the last full working version of TWRP recovery 99% without issue for the M919. Yesterday I spent the day installing different versions of TWRP since 3.0.2-0, installing the same Lineage 14.1 nightly, installing apps and testing wifi, ODINing back to factory, and installing the next version.
Originally I was on 3.2.1 and noticed crazy WiFi disconnect issues and system slowness and general bugginess. Read all the problems other people with other models of S4s were having with later builds of TWRP on later builds as well. I don't know what changed, but everything after 3.0.2-0 caused all the issues people hate to see with custom ROMs for this phone.
I have no WiFi drops, no lagginess, no issues with cell network, no random reboots. I say 99% because I'm sure there's something that might crop up that I haven't found, but if you're looking to get a brand new life out of your S4, stick with 3.0.2-0, and Lineage 14.1 works great.
Wonder if that's why I've been having dropped calls and a occasional freezes/reboots...
Overall the S4 has been working well, but its not 100% reliable. On my daily commute there's a couple spots I will always drop calls. I also noticed randomly I will lose all bars for no reason and it will come back a few seconds later. Last I've noticed that my phone will randomly freeze. All of these faults are occasional but its enough for me that it can lead to problems. These problems have shifted between ROMs as well, optimized lineage, standard lineage, etc.
Can you tell me if I need to reinstall my ROM too, or can I just flash the twrp you mention here?
I just flashed twrp-3.1.1-0-jfltexx with the latest nightly, wifi worked fine the past two days. Not sure about calls, haven't talked long. It's the version lineage suggests to use in their instructions.
I did notice that the CPU heats up in TWRP though, have to hold phone under a fan if backing up or flashing.
How would recovery would affect the wifi and calls though? I would think it would depend on the last firmware you had (I guess modem etc) and lineage itself...?
This is interesting. I just did my m919 with the new lineage 15.1 os and used twrp 3.2.2 and I havent noticed any issues so far. Maybe the latest 3.2.2 fixed the issues you described?
doom3crazy said:
This is interesting. I just did my m919 with the new lineage 15.1 os and used twrp 3.2.2 and I havent noticed any issues so far. Maybe the latest 3.2.2 fixed the issues you described?
Click to expand...
Click to collapse
Perhaps, I'm still rocking 14.1 as we just use the phone as our "house phone" and as a baby monitor (call myself via Hangouts from this phone, put it in kid's room) so I'm not sure about going through the whole upgrade/update process. If I get an itch for punishment I'll set aside some time on a weekend to try
How did you find 15 thought this only had 14.1
WangChung81 said:
Can say definitively that 3.0.2-0 is the last full working version of TWRP recovery 99% without issue for the M919. Yesterday I spent the day installing different versions of TWRP since 3.0.2-0, installing the same Lineage 14.1 nightly, installing apps and testing wifi, ODINing back to factory, and installing the next version.
Originally I was on 3.2.1 and noticed crazy WiFi disconnect issues and system slowness and general bugginess. Read all the problems other people with other models of S4s were having with later builds of TWRP on later builds as well. I don't know what changed, but everything after 3.0.2-0 caused all the issues people hate to see with custom ROMs for this phone.
I have no WiFi drops, no lagginess, no issues with cell network, no random reboots. I say 99% because I'm sure there's something that might crop up that I haven't found, but if you're looking to get a brand new life out of your S4, stick with 3.0.2-0, and Lineage 14.1 works great.
Click to expand...
Click to collapse
I had the same problem you did but found this custom TWRP 3.3..0.0 worked great if you want to try roms above 14.1
---------- Post added at 08:01 PM ---------- Previous post was at 08:00 PM ----------
yoshkapundrick said:
I had the same problem you did but found this custom TWRP 3.3..0.0 worked great if you want to try roms above 14.1
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...p/jdcteam-twrp-3-3-0-0-custom-builds-t3925619
Hi,
Since I got the latest Oxygen OS update (I'm on Oxygen OS 9.0.4) . My Phone App has started crashing if I make a outgoing call or get one. First the Phone App crashes and then the system UI Crashes. The Phone was working fine till this update.
Thinking this is an issue with the Oneplus Oxygen OS update, i tried to move to Pixel Experience OS. The version I installed worked well but again when i did a OTA upgrade the same issues started recurring. There I also faced crashes if I used the camera app.
Frustrated I moved back to the Stock Rom.. But the Problem of the Calling app still exists. I"ve tried installing alternate diallers but its the same effect. I'm attaching my log file here : https://drive.google.com/file/d/1nLldKekVd_ZLWRghbPeJP94cdimQpsf6/view?usp=sharing
Can you guys help figure out whats happening ?
coolparth said:
Hi,
Since I got the latest Oxygen OS update (I'm on Oxygen OS 9.0.4) . My Phone App has started crashing if I make a outgoing call or get one. First the Phone App crashes and then the system UI Crashes. The Phone was working fine till this update.
Thinking this is an issue with the Oneplus Oxygen OS update, i tried to move to Pixel Experience OS. The version I installed worked well but again when i did a OTA upgrade the same issues started recurring. There I also faced crashes if I used the camera app.
Frustrated I moved back to the Stock Rom.. But the Problem of the Calling app still exists. I"ve tried installing alternate diallers but its the same effect. I'm attaching my log file here : https://drive.google.com/file/d/1nLldKekVd_ZLWRghbPeJP94cdimQpsf6/view?usp=sharing
Can you guys help figure out whats happening ?
Click to expand...
Click to collapse
try clean flash any beta version of oos , or use unbrick tool to restore all firmware to factory setting.
Hi
Would this be the unbrick tool ? https://www.google.com/amp/s/forum....5t-unbricking-tool-confirmation-t3733012/amp/
Seems like a very old version ?
Hello
I tried doing the clean flash to the latest Beta.. But still getting the crashes. Will try un bricking now.. However is there a chance its related to the hardware ?
coolparth said:
Hello
I tried doing the clean flash to the latest Beta.. But still getting the crashes. Will try un bricking now.. However is there a chance its related to the hardware ?
Click to expand...
Click to collapse
no, perhaps its related to software. are u using any mod or theming?
Hi,
Currently none. The phone was on Stock Oxygen till 3 odd months ago and was working fine. After one of the OTA Updates, this problem started happening. Since I could not find any consistent users reporting the same issue on Oxygen, I decided at that point to try using a different ROM and switched to Pixel experience. The phone worked ok for 2 weeks or so post that. Again after a new OTA came and I upgraded it started crashing again.
In the team time i saw another update to Oxygen had come so it thought i'd try going back to stock.. But not avail. Its still crashing.. Its only the Phone App that acts up. Everything else works fine. However the first time this issue came video playback was also freezing.
The logs that i have posted show these crashes but I dont have enough knowledge as yet to understand the reason.
After the above response to try clean flashing the latest Beta. But the issue persists..
Try see if the phone app is set as standard app for handling phone calls.
Hi
Tried that ..it is set as default.. The latest trial I did is cleanflashed an older version official ROM v5x of Oxygen OS... Problem is still the same..
Infact worse.. now I've got the settings app crashing and random reboots in addition to the phone app crashing !
I'd thought if this issue is due to post 9.02 upgrades this would solve it . But it's made it worse..
Parth