MIDDLE part of one plus has become unresponsive after update lollipop ROM . tried many different solutions . none of them worked . please help how to get the touchscreen back again
The lower part of my screen (last inch or so) is often unresponsive so if I type, I'll miss a bunch of spaces.....
theMoiz94 said:
MIDDLE part of one plus has become unresponsive after update lollipop ROM . tried many different solutions . none of them worked . please help how to get the touchscreen back again
Click to expand...
Click to collapse
Test your touchscreen using this app https://play.google.com/store/apps/details?id=com.rn.yamtt
If there are issues with multi touch, only thing I can suggest is to switch to other ROM if you are rooted and bootloader unlocked
I had read that CM has fixed touchscreen issue in their latest CM12.1 nightlies
If you are not rooted, a factory reset may work (hopefully) else call the customer service for RMA if they do it for you so easily
I was facing such issue on CMOS12 and also on all lollipop ROMs so I downgraded to XNPH05Q
Hey folks, first of all, sorry but I couldn't find anything that helped.
I have a Galaxy Note 4 (SM-N910F (international Version); Codename: "trltexx") and had flashed an unofficial version of Cyanogenmod 14.1. Except for a few bugs, it was running fine.
I've then changed to Lineage OS 14.1, obviously unofficial as well. This was running fine too and had less bugs (i.e. camera was working unlike with CM).
Well, then, after about a week or so, the phone became unstable and just won't recover from it since then - at least two weeks.
System and Play Store apps/services began to crash (sometimes several at once), the device restarts/turns off randomly or keeps displaying the boot animation and won't turn on till I take the battery out and put it back in.
The weird thing is, these problems sometimes don't occur at all and everything runs nice and smooth and later, everything starts again and is even worse. It feels like the phone is destroying and recovering itself over and over again.
Right now, I'm running the latest version of Ressurrection Remix OS (V5.8.1./Android 7.1.1).
Well, I'd like to thank you in advance for your answers.
User422 said:
Hey folks, first of all, sorry but I couldn't find anything that helped.
I have a Galaxy Note 4 (SM-N910F (international Version); Codename: "trltexx") and had flashed an unofficial version of Cyanogenmod 14.1. Except for a few bugs, it was running fine.
I've then changed to Lineage OS 14.1, obviously unofficial as well. This was running fine too and had less bugs (i.e. camera was working unlike with CM).
Well, then, after about a week or so, the phone became unstable and just won't recover from it since then - at least two weeks.
System and Play Store apps/services began to crash (sometimes several at once), the device restarts/turns off randomly or keeps displaying the boot animation and won't turn on till I take the battery out and put it back in.
The weird thing is, these problems sometimes don't occur at all and everything runs nice and smooth and later, everything starts again and is even worse. It feels like the phone is destroying and recovering itself over and over again.
Right now, I'm running the latest version of Ressurrection Remix OS (V5.8.1./Android 7.1.1).
Well, I'd like to thank you in advance for your answers.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried asking in the rom threads to see if anyone else is having the same issues ? Unfortunately using cm/lineage based roms can have bugs as they are not based on samsung firmware
Regards
Sawdoctor
Hi, thanks for the answer. I wanted to say that I went down to resurrection remix Rom which is based on Android 6 (Marshmallow).
It's fine now.
Now I'm just looking to find a way to hide my root. Can't use my banking app anymore since I've rooted my device.
Update 2: The phone problems I have described reoccur over and over again. A factory reset via TWRP fixes that and then the phone slowly goes back to the old problems.
I don't know what to do anymore except for doing this over and over again.
Hello All,
How can I downgrade to Android 10 without unlocking bootloader or rooting the device. I am asking that because Android 11 is plagued with issues on Pixel 4a. When I tested beta on my 3a it was stable and good.
bloodhound42 said:
Hello All,
How can I downgrade to Android 10 without unlocking bootloader or rooting the device. I am asking that because Android 11 is plagued with issues on Pixel 4a. When I tested beta on my 3a it was stable and good.
Click to expand...
Click to collapse
I don't think you can. You'd need to flash a full system image of Android 10, not a OTA, and a full wipe.
A wipe alone might cure your issues.
What issues you have?
The issues are only with android auto. When the phone is connected to android auto with usb cable and playing music through spotify. After few minutes the audio plays through phone speaker even though the phone remains connected to android auto. Only workaround fix for this issue is disabling the location. What's the use of android auto if location is disabled as we use android auto for navigation or maps
Tulsadiver said:
I don't think you can. You'd need to flash a full system image of Android 10, not a OTA, and a full wipe.
A wipe alone might cure your issues.
Click to expand...
Click to collapse
LOL!! I did factory reset and the issue persists. I believe it's google play services which is causing these issue which i mentioned above.
My friend is having same issue with his 3a and he didn't update to android 11. That's how I came to conclusion that Google Play services are causing these
I thought AA had serious issues on A11 natively? I don't think it is Play Services. Sorry no link. I think I read it on Android Police or maybe Phone Arena.
Hi there,
Yesterday i decided it would be time to upgrade my old Syberia 3.9 + microg install.
I thought it would be best to start with a fresh OOS installation, so I used the MSM tool to install OSS 10.3.7 and updated it to 10.3.12 OTA.
After successfully booting Syberia 4.9 I discovered that my Wifi periodically reconnected every second or so which made Wifi completely unusable.
I thought it may be a Syberia issue so I went back to OOS 10 and the issue was gone. So I switched to dotOS 5.2.1 and after that to Havoc OS 4.12 but couldn't get Wifi to work properly.
Rn I'm on OOS 11 which again works without any problem.
What am I missing? How do i fix this issue? I really don't want to use OOS + gapps....
I'm on LineageOS since a month (A11), and I've been experiencing the same thing. Every week or so, this issue occurs. A reboot resolves it, but it's still annoying. Never had anything like it on OOS though.
had this device all of a week (barely), seemed to work great out of the box, have left it stock intentionally.
take the April security update, reboot.
Have completely lost pinch zoom / multitouch and it seems as though the screen's settings, software or combination are completely misaligned / out of whack regarding touch input.
It's the kind of behavior you get when you have a droplet on your screen and the phone screen is getting erratic input... like it's compromised or fragmented somehow.... I've increased sensitivity which made the phone more usable, but I can barely use the bottom row of my home screeen. If I switch to left hand and try my L thumb, it better detects the input (if I aim WAY LOW). Almost like the calibration for the screen touch has been completely FUBAR.
Hoping custom software and lack of OTA updates fixes this? Has this community seen this issue and are custom ROMs a way out of the mess, or is this a hardware issue that absolutely requires the device to be returned and replaced? Seems odd the change happened with no physical change to the phone.
Same issue here when updating. Complete factory reset fixed mine
@beflythis hey did you figure the fix out? I have a similar issue. Factory reset didn't help me
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
anshuuu03 said:
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
Click to expand...
Click to collapse
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
This is definetly an issue with what seems to be the software, not sure exactly what is wrong though (I dont know too much about kernel driver code),
anshuuu03 said:
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Click to expand...
Click to collapse
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Do let me know if it works. It would be a life saver
fbievan said:
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
Click to expand...
Click to collapse
I think downgrading to Android 10 has worked for almost everyone facing this problem
vovapolischuk said:
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
Click to expand...
Click to collapse
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Now that i know that im now going crazy, and atleast one other person has very very similar story to mine, there needs to be a proper fix. I do know that android 10 and android 11 do have different touchscreen drivers. Downgrading then upgrading back wont work, atleast to my knowledge. I've done plenty of looking, and just don't know whats wrong. If any kernel devs that know their way around touchscreen drivers, and pixel 4as. Would be a life saver. But I have little idea of whats actaully going wrong.
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Yep, downgrading again to Android 10 alllows multittouch to work
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
fbievan said:
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
Click to expand...
Click to collapse
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
fbievan said:
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
Click to expand...
Click to collapse
Make sure to test, test, and test
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
Can I ask: has that worked for you?
fbievan said:
Can I ask: has that worked for you?
Click to expand...
Click to collapse
I think I will try and do the 10 > 11 > 12 > 13 in a few days. I am stuck with some work and cannot afford to keep resetting my phone atm. But I will update here whatever is the update on that