Related
Hey!
I looked everywhere to find a solution to my GPS that's not working and ended up with this thread, where crypted offers a scripted solution, including the agps solution, using the NTP servers.
I selected the Google Build and after a Restart, the GPS locked and I was happy!
But unfortunately, it locked 260km away from my position :-/
I know that some users already experienced similar problems, but I couldn't find any solution yet.
Did I miss something?
try reading this :
http://forum.xda-developers.com/showthread.php?t=1447593
and also try this one :
http://forum.xda-developers.com/showthread.php?t=1392466
b02 said:
try reading this :
http://forum.xda-developers.com/showthread.php?t=1447593
and also try this one :
http://forum.xda-developers.com/showthread.php?t=1392466
Click to expand...
Click to collapse
Hey!
These are two of the solutions I tried, first the scripted one (I actually wanted to post this link but I accidentally took an other ^^) and then the other one.
There was no change, I also think, that both describe a similar way to solve it.
Right now, I saw, that there are two gps.conf files, one in /etc/gps.conf and one in /system/etc/gps.conf, but I don't think that this is the problem..
BTW: Heres the GPS Status - there are no Satellites showing up, is this normal?
Saftpackl said:
Hey!
These are two of the solutions I tried, first the scripted one (I actually wanted to post this link but I accidentally took an other ^^) and then the other one.
There was no change, I also think, that both describe a similar way to solve it.
Right now, I saw, that there are two gps.conf files, one in /etc/gps.conf and one in /system/etc/gps.conf, but I don't think that this is the problem..
BTW: Heres the GPS Status - there are no Satellites showing up, is this normal?
Click to expand...
Click to collapse
well, try with this too :
4. This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
9. CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
11. Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
the 11 one may get it to work ... ?
b02 said:
well, try with this too :
4. This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
9. CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
11. Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
the 11 one may get it to work ... ?
Click to expand...
Click to collapse
I tried that already (also tried different config layouts), but unfortunately, it changed nothing.
Isn't the aGPS just for finding the nearest satellites faster? So, it seems, that aGPS is finding the wrong position (maybe because of some NTP servers?) and that the normal gps still isn't even working (because I tried to get GPS running since I flashed CM7)..
Hmmm..
Saftpackl said:
I tried that already (also tried different config layouts), but unfortunately, it changed nothing.
Isn't the aGPS just for finding the nearest satellites faster? So, it seems, that aGPS is finding the wrong position (maybe because of some NTP servers?) and that the normal gps still isn't even working (because I tried to get GPS running since I flashed CM7)..
Hmmm..
Click to expand...
Click to collapse
i guess it's not working, somehow, since you can't find ANY satellite
did you try any other rom, and did gps work when u were stock ?
^^
Yes, it worked on stock rom, and i believe it also did on another (maybe Mindhaxors ROM)
But I like CM very much and would prefer not having to change, these are like two worlds for me since I tried it out ;-)
I had the same issue, using CM7 nightly. I applied the patch and GPS was showing a fixed location far away from actual location. Then I tried a combination of using another app (GPS test instead of GPS status), calibration of compass (rotating in all three axes a cuple of times) and removal of AGPS data and GPS started to work in gps test as well as on google maps. After reboot however I was not able to reproduce it. Now I don't have any fix..I'll try it tomorrow, maybe I'll have more luck.
make nand backup and try full factory reset clean dalvik cache and stuff, and reflash... try it even with new sd card or just some clean one...
p.s. flash latest nightly, or 14th january one, since it's tested ;-)
Sent from my HTC Wildfire using xda premium
I have the same issue:
CM72, GPS fix various methods tried out as in the topics linked, get "too" fast fix within minuted but around 400km away ;-( Any idea what else could be done???
Yes. Wait for sat locks and position update the first time and try not to get bored and quit. It well find you eventually and subsequent location updates will be faster...Might take 10 min or so.
Sent from my cm7.2 Wildfire S
I also have the same kind of prolem.
I tried every solution adviced but my gps is stuck to 46°59.999N and 3°59.999E.
i am with cm 7.2 and my gps workswhen i install a stock rom.
thank u in advance
img851.imageshack.us/img851/1448/screenshot1329031958236.png
I think I might be having the same problem, in my case after applying GPS patches the location returned by GPS was constant (and far away from my actual location). I am yet to understand and fix it, but I think I'm getting closer
UPDATE @estantor - yep I'm having the same issue, the GPS is either stuck at exactly the same coordinates, or lately it stopped locking on to the satellites
those are the exact coordinates where my CM72 GPS is also stuck, in the middle of nowhere in France.
Really strange, I wonder if flashing a more recent CM72 update might help?
UPDATE: DId a new flash with CM72 RC0, applied the fix and now its fast and correct ;-)!!!
playagiron said:
those are the exact coordinates where my CM72 GPS is also stuck, in the middle of nowhere in France.
Really strange, I wonder if flashing a more recent CM72 update might help?
UPDATE: DId a new flash with CM72 RC0, applied the fix and now its fast and correct ;-)!!!
Click to expand...
Click to collapse
did you install the latest nighly build? i'm still stuck :-/
which fix exactly did you apply?
Edit: GPS is working after I installed m1ndh4x0rs ROM where it worked before and reverting to my previous backup (CM7) it still shows the wrong location, though, when GPS has a weak or no signal
Ok so ever since I updated to any of the 4.4.2 rom (i.e. Cm11, Cyanfox, SlimKat and Carbon Rom) my accelerometer won't work correctly.
At first I thought it was a GPS issue but after looking into it more the GPS locks fine. It's only the direct in google maps or any other GPS like app that is messed up. For instance, when I'm using google maps and I'm facing north it will show me facing east, then when I change directions it can't figure out which direction I'm facing and spins around in circles and maps will crash. Same thing happens when I use GPS Status, the app will say I'm facing the wrong direction and when I move direction it starts to spin out of control.
I defiantly don't think its a hardware issue since everything was working fine with the touchwiz rom and 4.3 roms. If anyone has any clue on how to fix this I would greatly appreciate it. This is pretty much the only thing that is wrong for me with any kitkat roms.
I have a tmobile galaxy s3 and current running SlimKat build 3. :crying:
Try FasterFix app
Perseus71 said:
Try FasterFix app
Click to expand...
Click to collapse
I gave it a shot but no luck. I have also used GPS status and FasterGPS but like I said before I don't think its a GPS issue because it does lock on to my location fine. It's just my compass doesn't work correctly.
I believe CM has a Advanced Option to Re-Calibrate Accelarometer. Settings > Advanced is where the option is I think. I use Slim Bean so I don't have CM details.
Oh yeah I forgot about that but it still didn't work. I appreciate all the ideas though.
You may want to go back to Stock and then try. Just to rule out any hardware issues. It will also wipe any corrupt firmware.
Perseus71 said:
You may want to go back to Stock and then try. Just to rule out any hardware issues. It will also wipe any corrupt firmware.
Click to expand...
Click to collapse
Do you mean odin to stock or just flash a stock rom? If it's odin I'll definitely try it when I get home. The thing I find weird is that when I flashed the S3Rx rom, everything was working fine.
I'd do Odin before trying anything else.
So I odin back to stock and like before everything was working properly. Then when I flashed back to carbon rom, is back to pointing in the wrong direction and spinning out of control.
I'm surprised that I'm one of the only if not the only one with this problem. Is there an app that I can manually calibrate which direction I'm pointing?
I'm out of ideas...
Can you flash a different kernel on top of Carbon ?
Perseus71 said:
Can you flash a different kernel on top of Carbon ?
Click to expand...
Click to collapse
I flashed KT kernel, BMS, Harkness and DKP. For a little while it seemed like BMS had fixed it but then went back to the same ol' sad story. :crying:
Try Another Rom please. Not just Carbon. This time try a 4.3 rather than Kitkat.
I have tried other roms and I stated that this didn't happen till I started using Kitkat roms. When I was on carbon 4.3.1 there weren't any problems as well as on S3Rx 4.3 rom. Not sure why this only happens on Kitkat roms and what seems like only to me. I'll continue to look for solutions cause I really like the look and feel of Kitkat.
So after searching and searching I finally found a fix! I was about to give up hope but decided to try one last kernel, Quantum kernel. At first it seemed like it wasn't working but I had to calibrate my accelerometer with GPS Status. After that everything was gravy! I hope this helps others that have the same problem I did!
I had a perfectly working Galaxy Nexus running CM10.x, which I updated to a CM11 nightly. This worked great for a week or so and then the camera and gallery started FCing. After several resets, restores, newer/older nightly installs, nothing changed. Tried all possible combinations of new/old Gapps, but still no luck. I tried different ROMs - PA, stock 4.3 and some others, but nope. I even tried Ubuntu Touch and even that couldn't access the camera. This is when I was pretty convinced that the camera module itself must have died.
My questions:
What killed the camera? Is it possible that a bad ROM could have done it?
Is it possible to fix this via software?
I can try and get it repaired locally, but I just want to know if anything can be done at home.
Thanks.
aalaap said:
I had a perfectly working Galaxy Nexus running CM10.x, which I updated to a CM11 nightly. This worked great for a week or so and then the camera and gallery started FCing. After several resets, restores, newer/older nightly installs, nothing changed. Tried all possible combinations of new/old Gapps, but still no luck. I tried different ROMs - PA, stock 4.3 and some others, but nope. I even tried Ubuntu Touch and even that couldn't access the camera. This is when I was pretty convinced that the camera module itself must have died.
My questions:
1) What killed the camera? Is it possible that a bad ROM could have done it?
2) Is it possible to fix this via software? I can try and get it repaired locally, but I just want to know if anything can be done at home.
Thanks.
Click to expand...
Click to collapse
A ROM wouldnt just kill the camera over time. It would have not worked right after the ROM was installed. So I doubt it was a ROM. I would do a full reset. Not just a normal factory reset but flash the factory image and see if it fixes it. If it doesn't then most likely it's a hardware issue.
jsgraphicart said:
A ROM wouldnt just kill the camera over time. It would have not worked right after the ROM was installed. So I doubt it was a ROM. I would do a full reset. Not just a normal factory reset but flash the factory image and see if it fixes it. If it doesn't then most likely it's a hardware issue.
Click to expand...
Click to collapse
I've used the phone for over a year without any issues with several kernels and ROMs before and the camera worked just fine.
Yes, I've done a complete clean up - I wiped the whole phone and memory (using the fastboot -w option) and installed different ROMs and even a different OS (Ubuntu Touch), but the camera issue persists.
I believe it's hardware issue, but I just wanted to know if anyone's faced a similar problem.
aalaap said:
I've used the phone for over a year without any issues with several kernels and ROMs before and the camera worked just fine.
Yes, I've done a complete clean up - I wiped the whole phone and memory (using the fastboot -w option) and installed different ROMs and even a different OS (Ubuntu Touch), but the camera issue persists.
I believe it's hardware issue, but I just wanted to know if anyone's faced a similar problem.
Click to expand...
Click to collapse
So you went through this process?
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895
jsgraphicart said:
So you went through this process?
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895
Click to expand...
Click to collapse
Yup. I believe that's the exact post I referred to when I did it.
It even lost root during this process (of course) and I had to do it again - something I hadn't done in almost two years.
Since it was a spare phone, there wasn't any useful data on it. I backed up a few pictures and completely wiped it clean. No luck.
I'll add that the issue is only with the camera. Some apps FC, some apps (such as Camera+) give a message saying it was unable to connect to the camera or something. I believe the Gallery also FCs because it uses the camera at some point. All other apps work perfectly fine.
aalaap said:
Yup. I believe that's the exact post I referred to when I did it.
It even lost root during this process (of course) and I had to do it again - something I hadn't done in almost two years.
Since it was a spare phone, there wasn't any useful data on it. I backed up a few pictures and completely wiped it clean. No luck.
I'll add that the issue is only with the camera. Some apps FC, some apps (such as Camera+) give a message saying it was unable to connect to the camera or something. I believe the Gallery also FCs because it uses the camera at some point. All other apps work perfectly fine.
Click to expand...
Click to collapse
Usually if the phone has any issues at all, that process fixes them. And if it doesn't, then there is usually something wrong with the hardware. I wouldn't think the problem was brought on by installing a ROM or kernel though.
I think it's related to the kernel that you're using
......
i think yes but if you change the rom it will work
some roms the camera has some bugs big bugs colors are broken and stuff
I've been having ongoing problems with my GPS for awhile now. At first I thought it was due to a problem with the Lineage OS ROM. Now, having gone back to various stock ROMs, I've found that it's occurring with them as well.
The problem is this: the GPS works great the first 24 hours or so after a boot. After that, the GPS seems to die, showing no satellites in GPS Test or similar apps. HOWEVER, after a reboot, it works great again. Given that it works great after a fresh boot, I'm inclined to think this is a software problem, not hardware - and I'd like to hear from you as to whether you agree with this thinking.
If it is a software issue, the question is what else I can try other than what I've already done (flashing stock and other ROMs). Maybe there's some software that isn't being wiped/overwritten when flashing these stock ROMs with Odin? I tried using KIES, but it doesn't allow me to initialize the device (I'm assuming because Knox shows I've already installed a custom ROM onto it at some point).
Any wisdom appreciated - even if it's just a suggestion of where else to ask 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.