Related
Hi,
I bought my Note 2 about 2 weeks ago and kept it to OTA Updates, until recently updated via ODIN and CWM to a few different Original Custom FWs (PA3, RootBox, Carbon, ETC)
Thing is, i like charging my phone overnight, and it just freezes right when i plug it into the charger if the phone is turned off, even if it's on the power block that came with the phone box or via any usb port in my computer.
I've read that it's the kernel, but i've tried many kernels (perseus, limaro, neak, etc) and it always freezes. Also tried different base (official stock roms from sammobile, but i confess i haven't tried charging with stock because i always root it, and cwm it and custom rom it right away, i have no plans on coming back to stock)
I know this is no dealbreaker, but i'd like to be able to do it, since i only like to charge the phone once in a day, and it's when i'm sleeping.
Appreciate any help, thanks in advance.
Bump!
Factory reset.
this is XXXDDDAAA
Try to Charge with any other power adopter. QUOTE=Sojiryu;39628968]Hi,
I bought my Note 2 about 2 weeks ago and kept it to OTA Updates, until recently updated via ODIN and CWM to a few different Original Custom FWs (PA3, RootBox, Carbon, ETC)
Thing is, i like charging my phone overnight, and it just freezes right when i plug it into the charger if the phone is turned off, even if it's on the power block that came with the phone box or via any usb port in my computer.
I've read that it's the kernel, but i've tried many kernels (perseus, limaro, neak, etc) and it always freezes. Also tried different base (official stock roms from sammobile, but i confess i haven't tried charging with stock because i always root it, and cwm it and custom rom it right away, i have no plans on coming back to stock)
I know this is no dealbreaker, but i'd like to be able to do it, since i only like to charge the phone once in a day, and it's when i'm sleeping.
Appreciate any help, thanks in advance.[/QUOTE]
UtkarshGupta said:
Factory reset.
this is XXXDDDAAA
Click to expand...
Click to collapse
I did, CWM Fatory Data/Cache Wipe and didn't work, not sure if it's the same from the rom factory reset option, willing to try (and reinstall everything from scratch) if you or anyone confirms this.
Thanks.
jdomadia said:
Try to Charge with any other power adopter.
Click to expand...
Click to collapse
I did, Doesn't work with the original, or with any other, or USB to PC, just freezes, however it works on stock rom, just not any custom rom.
Thanks.
Try a super wipe and flash back stock rom. We need to cross out custom roms.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
Try a super wipe and flash back stock rom. We need to cross out custom roms.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
It charges while off on Stock ROM just fine, Just not on ANY CUSTOM 4.1.2/4.2.2 AOSP/AOKP, went to stock and came back to, say Carbon, or Rootbox with no luck, Still unable to charge while off,
Try not to undervolt it...when you try to undervolt too much there will be freezes when you lock the screen.. i had the same problem..
Thats my advice..
Make full wipe and install a custom rom..at the very first boot..try to access to stweak...grant it root pernission...and overvolt every cpu frequency step by+50mV.
Give it a try...i hope i helped you...ifbyes ..plz hit the thanks button..
If you have further question...feel free to pm me..or start a new thread.
Sent from my GT-N7100 using xda premium
It just started happening to me a few days ago on Jedi Master ROM... was working fine for about a month... if the screen stays off for a while or if it's charging for awhile it locks up... have to pull the battery
Have the same problem on slimbean 4.2.2 rom
Wysłane z mojego GT-N7100 za pomocą Tapatalk 4
Similar problem here, whenever screen is off for more than 8 seconds it will not wake up... Any ideas? I am trying stock roms and others, no solution so far...
Same problem with my GT-N7100.
I've tried both CWM & TWRP. It happens after flashing stock ROM to any of 4.3 AOSP based (CM10.2, ReVolt, Carbon, AOKP). When I'm trying to charge in power-off state, empty battery with white circle on center appears and freezes. Device doesn't charge and the only way to boot something (recovery/bootloader/system) is to reinsert the battery.
Changing build-in kernel to N.E.A.K. didn't help either.
I'm out of options. Please help :crying:
Happened here exactly after downgrading from 4.3 custom back to stock Samsung ROM. Of course lost IMEI but I managed to fix it and after applying ARIZA patch all worked well, however I flashed another stock, bit never and freezing started... Out of options so far as well. I will keep trying.
EDIT: Tried suggested in another thread RECOVERY software, however ODIN fails on sboot.bin every time...
My guess - trouble is in AOSP kernel. For example, if you install any AOSP based ROM and then install N.E.A.K. v2.2x SAMSUNG FW kernel (for TouchWiz) - problem goes away. You can't start ROM after that, but that's not the point.
I think we should post our issue in some kernel development discussion, like N.E.A.K. and hope they find solution.
btw 4.2 and 4.3 ROMs both has that issue.
mellax said:
My guess - trouble is in AOSP kernel. For example, if you install any AOSP based ROM and then install N.E.A.K. v2.2x SAMSUNG FW kernel (for TouchWiz) - problem goes away. You can't start ROM after that, but that's not the point.
I think we should post our issue in some kernel development discussion, like N.E.A.K. and hope they find solution.
btw 4.2 and 4.3 ROMs both has that issue.
Click to expand...
Click to collapse
---------------------------------------------------------
Just installed Omnirom 4.4.2 on my Note 10.1 (2012) and am having the same issue. As soon as I dock it / charge it when locked, can't unlock and it appears to crash. I did not have this issue with stock.
Any further progress?
Thanks in advance.
Anybody ever found a solution for this? My note 2, N7100 hangs if charged when switched off.
Only when switched off, I shows the battery with the white circle and that's it.
AOSB KK 1.3.6, 4.4.4, krn 3.0.64-CM, latest modem, TWRP etc.
Brammieman said:
Anybody ever found a solution for this? My note 2, N7100 hangs if charged when switched off.
Only when switched off, I shows the battery with the white circle and that's it.
AOSB KK 1.3.6, 4.4.4, krn 3.0.64-CM, latest modem, TWRP etc.
Click to expand...
Click to collapse
Try Resurrection Remix 4.4.2 KitKat v5.1.5 They fixed it somehow.
plz help
I have note 2 its all fine
but when i turn the screen off for a while the phone freeze and not turning on unless i unplug and replug the battery
this thing happens even in the charger i tried replacing the battery but the same thing
any ideas
Tab s t705 singapore updated to hong kong lolipop 5.0.2.
Been using it for a month without problems till suddenly started freezing in certain situations.till now i think its isolated to charging!
Device rooted supersu/twrp.
Ive read about it on internet couldnt find aolution and happened to other tab s (800..700..etc) no solution found and some said linked to lollipop but ive used it a while before anything happened.
What i did and did NOT work.
1.with without sim/
2. Delete cashe/dalvik and wipe to factory
3, restore a previous backup twrp where the issue want there
4. Installed other rom ..blissrom
5.flashed seperal kernels and updated twrp to latest for tab s
6.using other charger
Can be hardware? What can go wrong? Maybe from a drop something happened?
It keeps freezing with wtever last on screen. Lockscreen/app opened/home screen..mostly on lockscreen as it seems to happen a while after starting charging.
Please help this problem is driving me crazy since i lose all my work when it happens and im on stock rooted lolipop rom
Anyone ??
No1
8.4 models have been known to have problems with the battery connector which causes issues. There is a video on YouTube for the fix.
i think its solved !
rolled back to stock 4.4.2 od3 that came with the tab s. rooted backup.
i dont know what app/update/root/kernel might cause it but seems it was actually from lollipop and confirmed now !
AND SEEMS TO WORK BACK NORMALLY NOW !
I doubt it's lollipop itself but more a rogue app if that is the case.
I would make a backup of your current system with flashfire then reinstall lollipop and see if it happens again.
If it does restore your flashfire backup.
A fair number of unlucky LG G3 owners using AOSP/CM-based ROMs, myself included, have a major problem with the issue where a reboot/power-on cycle results in the phone getting stuck at the LG or boot splash screen ad infinitum.
The only way around it is to do a battery pull, sometimes several times, before the phone eventually recovers, but not until after it's gone thru its "Optimizing" or "Upgrading" apps, which takes 5-10 extremely annoying minutes.
I'm using a D851 and have this issue with every ROM I've used (Xenon, Exodus, AICP, to name a few).
This is not a battery issue as I've had the same problem using batteries from 3 different manufacturers. I've also had the same problem when plugged in.
If anyone knows of a fix - would be greatly appreciated (please don't say factory reset or root back to stock - I've already done this and it doesn't fix this issue).
I also have this problem with aosp and cm roms, i also get bsod sometimes. I think that maby the battery is broken, but im not sure since i dont got any problems on stock. When i get money for a new battery i will reply here with results.
I got my new battery today and it bootet up instantly
I had this issue on my d852 running cm12.1. It turns out using autorec is what caused it for me. I fixed it by flashing a kitkat tot then installing twrp using flashify. Once I had twrp installed I flashed the modem.bin from a lollipop d852 kdz. I haven't had a shutdown/reboot hang in a week now.
I have the same problem D851, it happens on latest builds of exodus and aicp. candy and blisspop works fine without any issues. I have changed the battery but the problem persist on exodus and aicp
Hi. I just updated the nightly build. After that, phone start to reboot randomly but i didnt think it is a big problem. But now, my battery is %5 and its not charging. I connect the cable, there is the lightning on the battery icon but when i go battery settings it says "%5 not charging". What should i do? How can flash stock rom with that battery level? Please help.
Sent from my iPad using Tapatalk
Same problem here. Revert back to the old CM13, it'll work. As for the 5%, just keep charging it while you downgrade it to the old CM, it won't charge the battery, but it will also stay at 5%.
filbertmang said:
Same problem here. Revert back to the old CM13, it'll work. As for the 5%, just keep charging it while you downgrade it to the old CM, it won't charge the battery, but it will also stay at 5%.
Click to expand...
Click to collapse
What version of CM13 u install to get it back to work? I try to install RR ROM but still don't charge. But when I turn off my phone (I don't know why) then my phone is charging. Any idea?
I had the same problem, it didn't charge more than %18, but i guess it was because of dirty flash, after wiping everything and flasging the new one, problem was solved
I had this problems. You can turn off your phone and it will charge.
If you want to keep CM 13 install 777 kernel that the charging bug will be fixed. At least it worked for me and some other users.
☝ yes, a different kernel fixed the issue, as it is a kernel issue from the new cm kernel that was recently implemented.
777 kernel is great!
Thank you all, I couldn't answer earlier.
filbertmang said:
Same problem here. Revert back to the old CM13, it'll work. As for the 5%, just keep charging it while you downgrade it to the old CM, it won't charge the battery, but it will also stay at 5%.
Click to expand...
Click to collapse
Your method has worked, thanks. As you say it remained same while flashing.
Ryudo0 said:
I had this problems. You can turn off your phone and it will charge.
If you want to keep CM 13 install 777 kernel that the charging bug will be fixed. At least it worked for me and some other users.
Click to expand...
Click to collapse
It wasn't also charging when it's turned off. But thanks for answer.
Sent from my LG-D855 using Tapatalk
Yes i had the same problem and 777 kernel fixed the issue
The kernel wasn't stable at the beginning i had some lags but after clearing cache and dalvik everything is working great now.
BTW Did anyone fixed the issue of "Invalid number" after ending calls???
M_ashmawii said:
Yes i had the same problem and 777 kernel fixed the issue
The kernel wasn't stable at the beginning i had some lags but after clearing cache and dalvik everything is working great now.
BTW Did anyone fixed the issue of "Invalid number" after ending calls???
Click to expand...
Click to collapse
I think this bug come with update CM13 to Android 6.0.1 and they don't know how to fix it or they just don't want to fix it. This bug is on all softwere with number 6.0.1 (on 6.0 never had this) - i think so.
xVeenix said:
I think this bug come with update CM13 to Android 6.0.1 and they don't know how to fix it or they just don't want to fix it. This bug is on all softwere with number 6.0.1 (on 6.0 never had this) - i think so.
Click to expand...
Click to collapse
Do you know what's the last cm 13 update with android 6.0?
I had this problem few times, restart always helped.
Cancled..
Nightly Released 12/22/2015 Fixed Charging Issue
xVeenix said:
What version of CM13 u install to get it back to work? I try to install RR ROM but still don't charge. But when I turn off my phone (I don't know why) then my phone is charging. Any idea?
Click to expand...
Click to collapse
I walked my d855 (LG G3) back through the nightly releases until I found the latest one that did not have the charging issues for me. I ended up with the 12/22/2015 Nightly Build that doesn't seem to have any of the charging issues. I was not able to download the 12/23/2015 Nightly for some reason, I think I just got a 404 error when trying to download the file.
I saw some people talking about the 777 kernel being a solution to this issue and I downloaded the zip file for that kernel but I wanted to see if one of the nightly releases fixed the issue before I started messing around with the kernel. I may end up installing that one if one of the Nightlies doesn't fix this issue sometime in the near future.
For the record, my phone would charge for a short while and then would stop charging the battery. The percentage at which it stopped seemed to be random, it was not the same percentage every time. Every once in a while I could get it to charge up to 100% again but not usually. Most of the time it would stop charging within a couple of minutes of plugging it in or setting it on the wireless charger. It did seem to take a charge if it was turned off. I could only test that with the wired charger since the wireless charger boots the phone up before starting to charge the phone again. Whenever it stopped charging, my 3c toolbox battery manager would say that it was plugged in (or on the wireless) but that it was either at 0mA coming in or sometimes it would actually drop into the negative (discharging).
Around the same time that I started having the charging issues I also ran into a problem where the phone would shut itself off whenever I had Google Play Music running through my Bluetooth headphones for a few minutes. It didn't just shut down all of the sudden with no warning, it would throw up the message box that it was shutting down, just like if I had told it to shut down myself.
I will keep an eye on the 12/22/2015 Nightly release and see if all of the issues I was having with the more recent Nightlies have stayed away. I will post again if I do run into these problems again.
*** EDIT ***
I went ahead and installed the 777 kernel and then updated to the most recent nightly release. I still ran into the same battery issue the first time I tried to plug the phone in. So, in my case at least, the 777 kernel did not do anything to help out the charging problems related to the nightly updates past the 12/22/2015 nightly release.
I am currently restoring my image to the 12/22/2015 nightly release with the updated 777 kernel so that I can charge my phone again. I will continue to check out the 777 kernel but I am going to have to hold off on the nightly releases/updates until they fix this problem. I can't leave my phone off every time it needs to charge. I did order two more batteries with an A/C charger so that I can swap out batteries for full ones if I need to. I originally ordered those when I first came upon the charging problem, mistakenly thinking my battery was going bad.
At any rate, hopefully someone will figure out something for this charging issue soon. I hope I maybe saved someone a little time with this post anyway....
I have the same issue with LG G3 Rogers/Bell (852). Reverted to Dec 22 nightly and battery is now charging OK. Anything past Dec 22 seems to have this battery charging issue for me.
Can confirm that flashing an alternate kernel does in fact fix the charging bug!
AssasinPenguins said:
Can confirm that flashing an alternate kernel does in fact fix the charging bug!
Click to expand...
Click to collapse
tried flashing 777kernel and phone was stuck on boot screen, have any idea why??
svismobo_66 said:
tried flashing 777kernel and phone was stuck on boot screen, have any idea why??
Click to expand...
Click to collapse
Hello
I'm using the latest update CM13 (30-12-2015) and the problem of charge apparently has solved. I have managed to charge my cell phone to 100%. In the only previous version it loaded up to 50%.
someone more that has tested?
Updated to latest nightly Dec 30 2015 and confirm that charging is working again for me. Thanks.
I also updated to December 30 and it is now fixed.
Sent from my LG-D852 using Tapatalk
I still have this issue, tried the 777 kernel and got stuck on boot.
Been trying to systematically update ever since...
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.