Related
I have a ATT TP2/Stock Radio and have been flashing ROMs for a long time... I recently flashed to the latest ENERGY rom and after a day or so the weather for "My location" quit updating?
I figured it was a bug so I flashed to another one of his ROMs. (I always have used his ROMs from my 1st flash) The phone will not find a GPS signal to update my location. I went back to a tried and true oldler version of Energy, which worked in the past and still no "My location" weather?
Google maps cannot locate any satilites either?
I flashed back to 1st ATT stock ROM loaded google map, searched my location and it worked... So they phone is still working properly.
Flashed back to ENERGY ROM and back again to no "My location" weather or google map GPS?
I have tried everything I can think of please help...
Perhaps you have already done it, but have you performed a task 29? If not try that, then flash your rom.
Both the My Location and GPS issues are discussed (with possible solutions) in the Energy ROM FAQs, Post 6 (of the Energy ROM thread) Section 3 "Solutions to Issues":
http://forum.xda-developers.com/showpost.php?p=4579513&postcount=6
"My Location" is derived from cell tower information, not GPS. Issues with My Location may be a function of the cell tower at your local area, either low signal strength, or just not passing the proper info to your phone. If you travel to a location a few miles away (or farther) do you still get no location?
I have the ATT Tilt2, same as you, and have flashed Energy ROM many times (including most recently Oct. 8), and have never had an issue with either My Location or GPS. There are some ATT-specific solutions you can try, listed in the FAQ. Also, updating to the newer radio (one shown in my signature) may help.
Will do...
I do perform Task 29- Thanks for the reply
I will read more about the it from the Energy thread. Thanks for the reply...
That is the ROM I started having issues with.
OCT.8 Cookie Rom- Flashed and just like normal everything was fine. Drove out on a job for work and everything was good, later got back to my shop in and looked at the phone and it was stuck on the other city,kinda like it hadnt updated since. Tried to update and it just would time out? So I Hard reset the phone and it never loaded the My Location... Full signal indoors and out.
One of the guys I work with has a TP2 as well and he asked me if google was working. I tried to locate me on the map and it says "Your location is temporary not avial." When I try to update the weather from the tab it says "No updates are avail."
I dont know? Im downloading the new ATT ROM now and will, see what it does.
I was told that it will update my radio.
Ive never flashed my radio, and dont know much about it or what exactly it does to upgrade it. I am going to try to read more tonight when I get off work.
Thanks, If your have any inputs/questions I will get back ASAP...
Dont know?
Well the new ATT ROM is on the phone working fine...? As soon as it booted the weather on the Sense popped up with my city... I cant figure out why other roms arent working.
Im going to flash again to Energy soon... Maybe tonight or tomarrow; Battery is dead and have to let it charge. Besides Ive flashed some many times im tired of messing with it.
If anyone has any ideas on what my issue may be please help.
Thanks-
JColorado said:
Well the new ATT ROM is on the phone working fine...? As soon as it booted the weather on the Sense popped up with my city... I cant figure out why other roms arent working.
Im going to flash again to Energy soon... Maybe tonight or tomarrow; Battery is dead and have to let it charge. Besides Ive flashed some many times im tired of messing with it.
If anyone has any ideas on what my issue may be please help.
Thanks-
Click to expand...
Click to collapse
The stock ROM works fine because it does all the work for you. It preforms a task29 as part of the process. If you don't know what that is, it's a tool that erases and formats the internal memory of the device. It also flashes the radio and the ROM in the same program. Basically, all of the things you needed to do on a custom ROM, it does for you on the stock ROM.
BEFORE putting another ROM on your device, preform a task29 (search for it in the Rhodium ROM dev section), then flash the ROM. After that, read the FAQ in post #6 of the Energy thread. If that doesn't answer your question, then ask about it in that thread.
BEFORE posting a question in the Energy thread, be sure to read the FAQ. There is a correct way to ask for help there.
IDK, This is wierd
I do know about task29 and perform it before every flash.
So Stock ROM V.2 was working on "My Location" and Google Map... So I was looking around for .Cabs to clean the Stock ROM up and noticed that ENERGY had posted some new ROMS and I downloaded one. I Task29'd and flashed to the new Energy ROM, No fix on Google and weather "My Location" still unable to update or even find my location...?
Task29'd and went back to Stock ROM V.2 and now I'm having the same issue with the stocker?
Does anyone know what could possibly causing this issue? I don't ever get into the Registry or anything. I just flash and go adding the basic .Cabs
I'm at a loss... I would really hate to replace the phone due to this. Everything else works fine it just seems to be a GPS issue...
Any help would be greatly apperciated.
Thanks in advance-- I hope
JColorado said:
OCT.8 Cookie Rom- Flashed and just like normal everything was fine. Drove out on a job for work and everything was good, later got back to my shop in and looked at the phone and it was stuck on the other city,kinda like it hadnt updated since. Tried to update and it just would time out?
Click to expand...
Click to collapse
This to me would seem to indicate that it might be an issue with the cell towers and not your phone, if it works in some locations and not others. Its a pretty common issue, that's why its on the FAQs. For months, my phone would not retrieve the location information from the cell tower near my office, despite 4 bars of reception. But it works fine almost anywhere else. Next time you are driving to other locations, experiment and see if it works better in other towns.
The time out message for weather just means it can't get the weather info over the data connection, it doesn't refer to My Location. The HTC weather server has issues from time to time, so this may have nothing to do with your phone.
JColorado said:
I do know about task29 and perform it before every flash.
So Stock ROM V.2 was working on "My Location" and Google Map... So I was looking around for .Cabs to clean the Stock ROM up and noticed that ENERGY had posted some new ROMS and I downloaded one. I Task29'd and flashed to the new Energy ROM, No fix on Google and weather "My Location" still unable to update or even find my location...?
Task29'd and went back to Stock ROM V.2 and now I'm having the same issue with the stocker?
Does anyone know what could possibly causing this issue? I don't ever get into the Registry or anything. I just flash and go adding the basic .Cabs
I'm at a loss... I would really hate to replace the phone due to this. Everything else works fine it just seems to be a GPS issue...
Any help would be greatly apperciated.
Thanks in advance-- I hope
Click to expand...
Click to collapse
If you are running Energy ROM, then the solution to your My Location problem is listed in post #6 of that thread. The easiest solution is to simply disable 3G. My Location is determined from the Cell Towers, not the device. If this solution doesn't work for you, then that narrows the problem down to something you've installed on the device. Try the solutions listed first. If that doesn't work, install a program like Sprite Backup to create an image of your device so you don't loose anything. After backing up, flash the stock ROM and see if, without installing or changing anything, you have the same problem. If it's working like this, then install things one-by-one until you find the culprit.
JColorado said:
Ive never flashed my radio, and dont know much about it or what exactly it does to upgrade it. I am going to try to read more tonight when I get off work.
Click to expand...
Click to collapse
Flashing the radio is super easy. If you've already flashed ROM, flashing the radio is basically the same process, except it only takes a several seconds. It updates the software on your phone that allows it to connect with the cell network. It resides on a separate part of the memory than the OS, so it usually is not affected by ROM flashes (and vice versa, flashing the radio does not affect the ROM). The newer official ATT ROM is an exception, where they packed the radio in with the ROM. So now your radio is updated to the newest ATT radio. Flashing custom Rhodium GSM ROMs from XDA won't affect the radio, unless specifically indicated otherwise (and I haven't seen any custom ROMs that do that).
redpoint73 said:
Flashing the radio is super easy. If you've already flashed ROM, flashing the radio is basically the same process, except it only takes a several seconds. It updates the software on your phone that allows it to connect with the cell network. It resides on a separate part of the memory than the OS, so it usually is not affected by ROM flashes (and vice versa, flashing the radio does not affect the ROM). The newer official ATT ROM is an exception, where they packed the radio in with the ROM. So now your radio is updated to the newest ATT radio. Flashing custom Rhodium GSM ROMs from XDA won't affect the radio, unless specifically indicated otherwise (and I haven't seen any custom ROMs that do that).
Click to expand...
Click to collapse
There are a couple of custom ROMs that flash radio as well. I don't recall which, but be sure and look before flashing!
stevedebi said:
There are a couple of custom ROMs that flash radio as well. I don't recall which, but be sure and look before flashing!
Click to expand...
Click to collapse
Thanks, good to know. Of course, we always read the ROM instructions thoroughly before flashing!
Narrowed Down...
Thanks to all that have helped so far...
Ok after reading the last few post I have somewhat narrowed down the issue.
Okay, Yesterday I flashed the New ATT ROM so I have the upgraded radio-
Discouraged after I lost the "My Location" with the stock ROM and its differences between Energy(I guess I got spoiled by it) I flashed back to a later version of Energy.
CajunFlavoredbob- Thanks for recommeneding me to try disabling 3G and see if it works. Well it did, I dropped to the Edge network full signal and it picked up pretty quick both on "My Location" Weather and Google... Switched back to 3G and issue came back.
So I read post#6 from the Energy forum and one user says for him he used
"FF ATT Nokia aGPS Settings" I am using something I think is similar to that it is "FF Google aGPS Settings Generic" but I guess its not work aswell as it should or at all? So I am going to try to find this other .Cab and install it and see if this works.
Somewhat narrowed down, with the issue but feel like I am getting somewhere
Thanks to all for help so far! I will keep you guys updated...
No luck...
Okay well I got 3 .Cabs from I believe Fone Fanatic and another one from this guy I work with and no luck?
Any other ideas on what I can do?
Yesterday my gps wasnt working at all. It would not lock on no matter what I did. I was on a custom rom and I tried wiping my data/cache, reinstalling maps (just for giggles), and a multitude apps from the market that help deal with gps problems (gps fix, gps status, toolbox, etc).
When all this didn't work I decided to odin back to the last official JB update and still no gps. On a whim I decided to odin back to an ICS firmware and that made my gps work. I have no idea but it did. I then odin to UVDLJC, installed TWRP's most recent and restored my backup of the custom rom I was using in the first place and gps now worked.
While I'm happy as heck that my gps is now working and that it was not a hardware issue I'm extremely curious what happened.
I have flashed many roms lately and I cannot think what a custom rom can do to gps to hose it or if it was just one of those things. I would of thought that when I originally did an odin to UVDLJC that would fix the issue but that didn't. Whatever the flash to ICS did fixed it but what in the heck could that of been?
I figure if I can find out or get an idea what happened then I can steer away from flashing certain roms, or just be prepared that flashing any roms at all can make this happen again.
Same here.
Hello, ddcoh.
I am currently having the same issue you had with GPS not working. I've tried everything from trying tedious Play store apps to trying many different roms and kernels (clean installing every time) to completely reverting back to stock including using TriangleAway in case that did any help. Nothing worked. I have been thinking about going back to ICS to see if that worked but the last time I tried to downgrade from 4.1.1 to 4.0.4 I ended up soft bricking my phone even though I followed the steps word for word.
Can you tell how you went about downgrading to ICS and then back to JB, please? I use my GPS a lot and I would hate to find out it's a hardware issue.
Typically, it's been when people are going from 4.2 to 4.1.
Zza1989 said:
Hello, ddcoh.
I am currently having the same issue you had with GPS not working. I've tried everything from trying tedious Play store apps to trying many different roms and kernels (clean installing every time) to completely reverting back to stock including using TriangleAway in case that did any help. Nothing worked. I have been thinking about going back to ICS to see if that worked but the last time I tried to downgrade from 4.1.1 to 4.0.4 I ended up soft bricking my phone even though I followed the steps word for word.
Can you tell how you went about downgrading to ICS and then back to JB, please? I use my GPS a lot and I would hate to find out it's a hardware issue.
Click to expand...
Click to collapse
Well I used odin to flash an T999_UVALEM which was a prerooted ICS rom. After booting it up I checked to see if GPS was working and it was.
I then used odin again to flash T999_UVDLJA which is a JB rom and booted it up also and saw that gps was working. Then I just restored a backup of a room I had been using and GPS still worked.
I've been out of town and noticed that after flashing a few roms that gps wasn't working so instead of doing all the above stuff I just flashed a cm10 rom. I believe I either used a cm10 nightly (or maybe 10.1, memory is hazy) or LiquidRom and that got the GPS working by just doing that. Not sure if that will work for you but you could always backup your setup using TWRP's latest and then flashing a cm10 rom and seeing if gps is working and if that fixes it then you could then just reboot and restore the rom you are currently on and that might fix your gps for you.
http://forum.xda-developers.com/showthread.php?t=1949687
Hi Guys really need help on this one.
As a brief background on the problem, from stock I have flashed a few custom roms mainly paranoid android, carbon, android revolution hd. Flashing was always successful. No problem with odin flash as well. My concern is this. I noticed that I was getting SODs after flashing a few custom roms. So in order to fix it, I tried to flash stock rom. No problem with flashing however SODs continue to exits. Have tried flashing quite a few stock roms but basically SOD problem still exists. By the way when flashing through ODIN I always just flashed with the PDA option never with the others. Getting really frustrated about this. I can get rid of the SODs temporarily by using SoftLocker. However, I wish to get back to a stable rom base before I try any new customizations. Hope you can help me. Thanks.
On an added note, when I connect my phone to the PC the phone is not automatically detected. I still have to input *#7284# change modem to pda in order for it to be detected. I think this is somehow related because this happened during my encounters with SODs.
Your help would be greatly appreciated.
By the way, I have already checked for the SDS chip and happily my phone doesn't use the insane chip.
Just wondering about this SOD thing.
Should it be enough that I flash into stock (PDA only) to get factory stock?
Should mention that original ROM of phone did NOT have SODs.
So I'm guessing the culprit is flashing the customized ROMs.
However, I cant get stability back even when flashing back to stock.
I can still see some residual effects of previous roms in my current stock rom (like the usb connection not detected).
Just looking for some clues and glad if someone could help.
t3kn1ks said:
By the way, I have already checked for the SDS chip and happily my phone doesn't use the insane chip.
Just wondering about this SOD thing.
Should it be enough that I flash into stock (PDA only) to get factory stock?
Should mention that original ROM of phone did NOT have SODs.
So I'm guessing the culprit is flashing the customized ROMs.
However, I cant get stability back even when flashing back to stock.
I can still see some residual effects of previous roms in my current stock rom (like the usb connection not detected).
Just looking for some clues and glad if someone could help.
Click to expand...
Click to collapse
HI Guys,
Just an update on this, in case someone is experiencing the same problems, it seems I got the SOD fix. I found it out by switching back to an AOKP rom. Suddenly, no more SOD. After a bit more experimenting, I found out that it had something to do with the kernel (stock kernel even!). My basic fix is this: install a stock rom then switch kernel to Note2Core. It seems certain "configuration updates" within the kernel prevents the device from going into sleep of death. (Note that my device now can "sleep" properly ... saw this using cpu spy ... deep sleep is still attained with NO SOD). Hope this helps people out there with the frustrating SOD problem.
Incidentally, if someone could point out how the kernel change fixed the SOD problem it would be a great help.
By the way, usb connection is still not detected by default but fixed by doing *#7248" and then choosing pda for usb.
Fixed! and Solved!
t3kn1ks said:
HI Guys,
Just an update on this, in case someone is experiencing the same problems, it seems I got the SOD fix. I found it out by switching back to an AOKP rom. Suddenly, no more SOD. After a bit more experimenting, I found out that it had something to do with the kernel (stock kernel even!). My basic fix is this: install a stock rom then switch kernel to Note2Core. It seems certain "configuration updates" within the kernel prevents the device from going into sleep of death. (Note that my device now can "sleep" properly ... saw this using cpu spy ... deep sleep is still attained with NO SOD). Hope this helps people out there with the frustrating SOD problem.
Incidentally, if someone could point out how the kernel change fixed the SOD problem it would be a great help.
By the way, usb connection is still not detected by default but fixed by doing *#7248" and then choosing pda for usb.
Click to expand...
Click to collapse
As an end note, I was able to bring back the ROM to stable state.
I believe my mistake was that I accidentally flashed an S3 ROM to my Note 2.
Probably corrupted some files.
The fix seems to be this:
Flash N7100_OXA_N7100XXDLJ2.
It will fail at sboot.bin.
Flash another stable rom (I did it with stock rom Stock_Deodex_Rooted_N7100XXDMC3_N7100OLBDMD1_N7100DXDLK5_THL)
Finish up.
Test for SODs.
CPU spy is the best way to check for it.
If deep sleep occurs without SOD then your phone is back to stable state.
USB connection is working properly as well as bluetooth (which I failed to notice was defective as well).
Hope this helps someone as it took me almost 5 months to get the phone stable. Cheers.
t3kn1ks said:
As an end note, I was able to bring back the ROM to stable state.
I believe my mistake was that I accidentally flashed an S3 ROM to my Note 2.
Probably corrupted some files.
The fix seems to be this:
Flash N7100_OXA_N7100XXDLJ2.
It will fail at sboot.bin.
Flash another stable rom (I did it with stock rom Stock_Deodex_Rooted_N7100XXDMC3_N7100OLBDMD1_N7100DXDLK5_THL)
Finish up.
Test for SODs.
CPU spy is the best way to check for it.
If deep sleep occurs without SOD then your phone is back to stable state.
USB connection is working properly as well as bluetooth (which I failed to notice was defective as well).
Hope this helps someone as it took me almost 5 months to get the phone stable. Cheers.
Click to expand...
Click to collapse
Thanks man i thumbs up ur account....i was changing my dead screen to a new one and i thought it was the new screen that kept turning off even after trying stock kernels and even pegasus but because of ur note2core recommendation and worked like a charm ....thanks man
It used to work but just noticed today it isn't any more. GPS will still find me, but it won't travel along with me in google maps and none of the satellites lock on using GPS toolbox. It shows 20 or more satellites available but none lock. If I do a search for nearby places it gets it right every time but it won't lock on to any satellites. I am rooted, I tried changing the rom and even loading a fully stock one and it still isn't working. I don't get how some of this stuff will work but I can't get any full lock.
Is this likely a device issue or something that I can fix?
I am also having this issue with my Pixel (non XL). Next weekend I will try and reset the device but I have had this issue for a few months now. I am not sure if it's software or a hardware problem.
JAYNO20 said:
It used to work but just noticed today it isn't any more. GPS will still find me, but it won't travel along with me in google maps and none of the satellites lock on using GPS toolbox. It shows 20 or more satellites available but none lock. If I do a search for nearby places it gets it right every time but it won't lock on to any satellites. I am rooted, I tried changing the rom and even loading a fully stock one and it still isn't working. I don't get how some of this stuff will work but I can't get any full lock.
Is this likely a device issue or something that I can fix?
Click to expand...
Click to collapse
Did you change kernels as well.
Way back in the day I had an issue like you described and the only way to resolve was to restore backup in which gps worked.
Then fire up phone confirm GPS lock. Then do all the flashing.
The only solution I ever knew to this issue was to restore a backup or start over from factory images.
parakleet said:
Did you change kernels as well.
Way back in the day I had an issue like you described and the only way to resolve was to restore backup in which gps worked.
Then fire up phone confirm GPS lock. Then do all the flashing.
The only solution I ever knew to this issue was to restore a backup or start over from factory images.
Click to expand...
Click to collapse
Yeah I changed the kernel. I tried completely unrooting and flashing a fully stock roms (March and April ROM) then reflashing the rooted rom I'm on (pure nexus) and even a non stock kernel (ElementalX) and it still won't lock.
JAYNO20 said:
Yeah I changed the kernel. I tried completely unrooting and flashing a fully stock roms (March and April ROM) then reflashing the rooted rom I'm on (pure nexus) and even a non stock kernel (ElementalX) and it still won't lock.
Click to expand...
Click to collapse
I assuming no back up then if you didnt restore that.
In my experience i dont recall flashing the stock rom alone enough to undo the change to the kernel that screwed up GPS.
It wouldnt lock on stock rom?
try flashing stock kernel by itself maybe?
parakleet said:
I assuming no back up then if you didnt restore that.
In my experience i dont recall flashing the stock rom alone enough to undo the change to the kernel that screwed up GPS.
It wouldnt lock on stock rom?
try flashing stock kernel by itself maybe?
Click to expand...
Click to collapse
Hey,
Flashing stock firmware actually includes the stock Kernel by the way. :good:
Cheers...
It didn't lock on any of the stock roms I flashed (which as user 5.1 stated included the stock kernel) but it used to work fine before on stock roms and even on pure nexus at one time. Not sure what happened or why it just stopped locking onto satellites.
JAYNO20 said:
It didn't lock on any of the stock roms I flashed (which as user 5.1 stated included the stock kernel) but it used to work fine before on stock roms and even on pure nexus at one time. Not sure what happened or why it just stopped locking onto satellites.
Click to expand...
Click to collapse
Hey,
I don't think it will fix it, since several ROMs didn't... But did you try reverting to an older version which used to work. You likely did it already. Just in case you didn't...
Otherwise you may try contacting Google or whom you bought your device, report your issue and see if they are already aware of the situation with others users maybe? As it sounds like a hardware issue...
Looks like you are far of being alone here: https://www.google.fr/search?q=goog...j0l2.8956j0j4&sourceid=chrome-mobile&ie=UTF-8
Good luck...
5.1 said:
Hey,
I don't think it will fix it, since several ROMs didn't... But did you try reverting to an older version which used to work. You likely did it already. Just in case you didn't...
Otherwise you may try contacting Google or whom you bought your device, report your issue and see if they are already aware of the situation with others users maybe? As it sounds like a hardware issue...
Looks like you are far of being alone here: https://www.google.fr/search?q=goog...j0l2.8956j0j4&sourceid=chrome-mobile&ie=UTF-8
Good luck...
Click to expand...
Click to collapse
Yup I did try that already. I am ordering a replacement tonight.
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.