recently I've acquired a problem with the volume of the headphone jack of my defy, it's about 1/3 of what it previously was.
my problem started out when I restored an old nandroid to do the 3.6.360 update (it had been complaining at me to update, but I had removed some bloat-ware) after the update the volume problem kicked in so I decided to restore my old nandroid at which point I got stuck in a boot-loop. up to this point I had not realized you were supposed to do a wipe in custom recovery before restoring a nandroid. I panicked and flashed Chinese 2.2 which made the phone actually brick, had to use the mcgyver hack, then I Flashed orange froyo which I had heard worked on bricked phones. now I'm running orange Froyo deblur with my old system intact. I tried the nandroid that comes along with orange deblur, but neither did that fix my problem or work with any 3g fix so I switched back over.
If anyone knows how to fix this issue I would greatly appreciate it.
Send it to motorola? i don't think if you can fix hardware problems...also note that there are loads of bugs in the latest kernel (2.6.x) so also mention that if you've upgraded to the latest kernel?
Problem is, it should be t-mobile us, if I send it in I'm not too sure they'll be happy to fimd Orange on it. Also I am in fact running the 2.6 kernel.
I have this problem too, and would be very happy to hear about a solution. Just wondered the first time if my old ears are getting worse... I'm running on the 3.4.2-145 2.6 kernel.
My touch screen seems to work fine on 4.2.2 (specifically the rom at: http://forum.xda-developers.com/showthread.php?t=2719411) but when I flash a 4.4.2 rom, it does not seem to track my finger well. Half way through a swipe it will just stop reacting to my finger, and no matter how hard I press or move it around it will not detect my finger again until I lift it and place it again.
This is very bothersome as it makes the tablet almost unusable. Any help is very appreciated.
This is ANY 4.4.2, stock based, or AOSP I have tried multiple roms from aosp, and ive tried both the A and B roms at http://forum.xda-developers.com/showthread.php?t=2707363
Update
So I went back to a 10a 4.2.2 base stock. Like usual the touch screen behaved normally here, Then I flashed the latest Mahdi and it once again stopped tracking my finger.
I then flashed the discontinued dyn kernel (gpeish works too) and it started tracking normally. I wanted to use the AIC kernel for AOSP, but unfortunately it does not correct the issue. So what I did was, flash dyn to get it working correctly, then flashed AIC over top of that. It seemed to do the trick. I don't have the issue now. Though I am not sure what this means, or if other people have this problem.
zetorung said:
So I went back to a 10a 4.2.2 base stock. Like usual the touch screen behaved normally here, Then I flashed the latest Mahdi and it once again stopped tracking my finger.
I then flashed the discontinued dyn kernel (gpeish works too) and it started tracking normally. I wanted to use the AIC kernel for AOSP, but unfortunately it does not correct the issue. So what I did was, flash dyn to get it working correctly, then flashed AIC over top of that. It seemed to do the trick. I don't have the issue now. Though I am not sure what this means, or if other people have this problem.
Click to expand...
Click to collapse
Thank you so much, I thought that I got a defective PAD, I have
I know that this is a veeery old post, so to clarify and be sure about what you did
Flashed stock 10a 4.2.2
Flashed DYN Kernel
Flashed AIC
Have you figured out any way to resolve the issue with 4.4.2?
thank you
Orochikun said:
Thank you so much, I thought that I got a defective PAD, I have
I know that this is a veeery old post, so to clarify and be sure about what you did
Flashed stock 10a 4.2.2
Flashed DYN Kernel
Flashed AIC
Have you figured out any way to resolve the issue with 4.4.2?
thank you
Click to expand...
Click to collapse
Unfortunately no. I ended up selling it after a year or so to buy a nexus 9. Sorry I cant be of more help.
zetorung said:
Unfortunately no. I ended up selling it after a year or so to buy a nexus 9. Sorry I cant be of more help.
Click to expand...
Click to collapse
Thank you for the reply
Well I just keep flashing till it works like it should lol
I have the same issue ! For a moment there I thought the G Pad had a non-sensitive area like the iPads have xD
The strange thing is, this problem also appears on Lollipop roms...
Is there any solution available? Still having this issue with AOSP 6...
Hello everyone. Since the Title has character limit im gonna have to explain myself here better.
Ive had my HTC One M8 for 4 years now. Pretty much since it came out in 2013. I installed ARHD back in 2014 and its been working just fine ever since. A couple of months ago i decided to go back to 45.0. Everything went smooth and everything works just fine.
But a week ago the phone decided to just go woopdido and it wouldnt open up any apps in Playstore although i could still see them. So i tried to restart it and when i did it got stuck at the HTC Logo. I tried to restart it a few times but it kept getting stuck. I was super confused due to the reason that i havent really done anything with my phone besides since the day i installed ARHD 45.0. I got desperate so i reinstalled it but this time with 53.1 and that went fine too except for one fishy thing and that was that i remember before when installing ARHD, when it got 30% it wouldnt take 2-3 minutes for it to finally start installing the ROM. It would take a couple of seconds for it to start right away and be done.
After installing 53.1 phone worked just as fine except for the fact that it was slower than it has ever been before. Which was also weird. Either way. After a couple of hours of it working, setting up every app i needed i restarted it and again it was stuck at the HTC Logo. Welp i guess..
So after that crap i went back to 45.0 again. It went good and all except it keeps getting stuck at 30% for a while but whatever. Going back to 45.0 though didnt help. Keeps repeating the same crap after a while. After a restart when having the phone doing nothing for hours gets it stuck at HTC Logo again. I literally cannot do anything with it atm and i have no clue how to go further from here as i have not had this before.
The HTC One M8 is rooted. S-Off everything you really need. The current TWRP version i have is 3.1.1.0.
Your firmware may be outdated. I would think it would be, as you said you haven't installed anything to the phone since 2014.
This (old firmware) alone would play havoc with the current ROMs. And also not play well with current TWRP, which may explain why going back to ARHD 45 is still resulting in problems.
What goes it day for OS number on the bootloader screen? If blank, what are the hboot and radio numbers?
The original issue could have just be due to some damage or corruption to the OS. It happens.
Also, the phone was released in 2014, not 2013.
redpoint73 said:
Your firmware may be outdated. I would think it would be, as you said you haven't installed anything to the phone since 2014.
This (old firmware) alone would play havoc with the current ROMs. And also not play well with current TWRP, which may explain why going back to ARHD 45 is still resulting in problems.
What goes it day for OS number on the bootloader screen? If blank, what are the hboot and radio numbers?
The original issue could have just be due to some damage or corruption to the OS. It happens.
Also, the phone was released in 2014, not 2013.
Click to expand...
Click to collapse
It was released in 2014? Welp why did i think it was 2013? Either way.
You missunderstood me but its all good because its on me. I was meant to say that i havent touched anything since i installed 45.0 a couple of months ago right. The firmware is fine and all for the current version i have. It was for 53.1 too.
And out of the blue it just got stuck on the HTC Logo. I tried something and it was updating the SuperSU which actually was the reason why it got stuck on the HTC Logo. I installed 2.79 and now it boots just fine and the phone is back on speed again. Apparently 2.82 has issues which is the version i assume it tried to update to through both TWRP and Playstore.
sp3tan said:
You missunderstood me but its all good because its on me. I was meant to say that i havent touched anything since i installed 45.0 a couple of months ago right .
Click to expand...
Click to collapse
Ah, I do see now that you stated you installed ARDH 45 a couple months ago. There is a lot of info there, so I missed that part.
Glad to hear you sorted it out. It's unusual to see a simple SuperSU update cause such a chain of event; but s#it happens I suppose.
redpoint73 said:
Ah, I do see now that you stated you installed ARDH 45 a couple months ago. There is a lot of info there, so I missed that part.
Glad to hear you sorted it out. It's unusual to see a simple SuperSU update cause such a chain of event; but s#it happens I suppose.
Click to expand...
Click to collapse
Yeah it does. I also forgot to mention that my microphone went to sh*t also. But its not because of this event. Although after this last reinstall i did the microphone picks up my voice better than it did before it went crap. But people cant still hear me when they call me
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.