Database Info

[Q] All Nexus 5 sensors mysteriously non-functional?

Update: Sorry about the title, it should be "[Q] All Nexus 5 SENSORS mysteriously non-functional?"
Well, I usually don't post under Q&A, Help & Troubleshooting unless I'm stumped...
I was flashing an OMNI-hammerhead update a couple days ago on my N5 and noticed something funny, the orientation sensor on my phone didn't seem to work, and I couldn't tilt my phone anymore. I quickly googled the problem expecting somebody with a similar problem but I haven't found one yet... I figured it was just a bad build, so I opened up TWRP and reflashed the zip for my original working OMNI install. The orientation sensor still didn't work... So I booted back into recovery and did a systen-data-cache-dalvik wipe and reflashed OMNI. Still, the sensor wouldn't work. I installed Android Sensor Box and opened it up and it said the only available sensor was the sound sensor. Furthermore, when I was taking a look through the sysfs none of the usual device firmware directories were showing up. `lsmod` seems to show that all of the kernel modules are loaded for my phone, and re-flashing my phone to stock android didn't help either. Finally, today I decided to back up my /data/media folder and reflash everything, including the radio and bootloader using the Unified Android Toolkit. Still, after all of that, the only sensor that shows up is the sound sensor. No compass, no accelerometer, nothing. What should I do? What should I try?

joshumax said:
Update: Sorry about the title, it should be "[Q] All Nexus 5 SENSORS mysteriously non-functional?"
Well, I usually don't post under Q&A, Help & Troubleshooting unless I'm stumped...
I was flashing an OMNI-hammerhead update a couple days ago on my N5 and noticed something funny, the orientation sensor on my phone didn't seem to work, and I couldn't tilt my phone anymore. I quickly googled the problem expecting somebody with a similar problem but I haven't found one yet... I figured it was just a bad build, so I opened up TWRP and reflashed the zip for my original working OMNI install. The orientation sensor still didn't work... So I booted back into recovery and did a systen-data-cache-dalvik wipe and reflashed OMNI. Still, the sensor wouldn't work. I installed Android Sensor Box and opened it up and it said the only available sensor was the sound sensor. Furthermore, when I was taking a look through the sysfs none of the usual device firmware directories were showing up. `lsmod` seems to show that all of the kernel modules are loaded for my phone, and re-flashing my phone to stock android didn't help either. Finally, today I decided to back up my /data/media folder and reflash everything, including the radio and bootloader using the Unified Android Toolkit. Still, after all of that, the only sensor that shows up is the sound sensor. No compass, no accelerometer, nothing. What should I do? What should I try?
Click to expand...
Click to collapse
Here you go.
http://forum.xda-developers.com/google-nexus-5/general/sensors-fix-nexus-5-t2704915

wolfu11 said:
Here you go.
http://forum.xda-developers.com/google-nexus-5/general/sensors-fix-nexus-5-t2704915
Click to expand...
Click to collapse
Hmm, it was really that simple?
Huh, who'da thought...
Thanks!

3 different OPO´s

I owned 3 OnePlus (1 white and 2 blacks). The last purchased was the sandstone version, and i bought it 2 days ago. My Question is simple: the first 2 OPO are running without any problems (sensor, touch, disply). But the third one (the newer one) from the start the proximity sensor doesnt work, the auto brightness is very strange (lowering and rising the brightness its not smooth, it´s like it´s choking). After many roms, i´ve succed in find a fix for the proximity sensor, but i have to flash it everytime i install a rom. I do not understand, what is so different with this model?
BTW: when i opened for the first time, it had version of 4.4.4, that i didnt saw it before 11.0-XNPH28R! And with that rom i had to manually upgrade to cm12, because the update system was telling me that is up to date.

SoRiNuS said:
I owned 3 OnePlus (1 white and 2 blacks). The last purchased was the sandstone version, and i bought it 2 days ago. My Question is simple: the first 2 OPO are running without any problems (sensor, touch, disply). But the third one (the newer one) from the start the proximity sensor doesnt work, the auto brightness is very strange (lowering and rising the brightness its not smooth, it´s like it´s choking). After many roms, i´ve succed in find a fix for the proximity sensor, but i have to flash it everytime i install a rom. I do not understand, what is so different with this model?
BTW: when i opened for the first time, it had version of 4.4.4, that i didnt saw it before 11.0-XNPH28R! And with that rom i had to manually upgrade to cm12, because the update system was telling me that is up to date.
Click to expand...
Click to collapse
Sounds like a firmware issue to me. When you say you upgraded to CM12 do you mean the nightlies or the stock ROM (Cyanogen OS 12)? And what method did you use to upgrade? By flashing the stock images with fastboot? Or flashing a ROM zip with recovery?

Heisenberg said:
Sounds like a firmware issue to me. When you say you upgraded to CM12 do you mean the nightlies or the stock ROM (Cyanogen OS 12)? And what method did you use to upgrade? By flashing the stock images with fastboot? Or flashing a ROM zip with recovery?
Click to expand...
Click to collapse
I´ve updated to Cyanogen OS 12 YNG1TASI3 using TWRP, but i´ve flashed the firmware with fastboot (this after i say that i have problems). But it´s the same. The only fix for proximity that work is the one from here: http://forum.xda-developers.com/one...es-mmwolverines-opo-mods-tips-tricks-t3027926
BTW: i´ve flashed EUPHORIA Rom, and the same, the problems persist (and i think that on this rom, the autobrightness issues is bigger, the brightness changing choking is more visible).

SoRiNuS said:
I´ve updated to Cyanogen OS 12 YNG1TASI3 using TWRP, but i´ve flashed the firmware with fastboot (this after i say that i have problems). But it´s the same. The only fix for proximity that work is the one from here: http://forum.xda-developers.com/one...es-mmwolverines-opo-mods-tips-tricks-t3027926
BTW: i´ve flashed EUPHORIA Rom, and the same, the problems persist (and i think that on this rom, the autobrightness issues is bigger, the brightness changing choking is more visible).
Click to expand...
Click to collapse
I think your best bet is to wipe your slate clean and start fresh. Go to my guide thread and use the instructions in section 8 to flash the stock images to your device with fastboot (don't worry about flashing the userdata.img as it'll only wipe your internal storage which is unnecessary, and don't worry about flashing the recovery.img as you'll need TWRP again anyway). You can grab the latest stock images from here. Once you've flashed the stock images flash whatever ROM you want and you should have no more issues (hopefully).

Heisenberg said:
I think your best bet is to wipe your slate clean and start fresh. Go to my guide thread and use the instructions in section 8 to flash the stock images to your device with fastboot (don't worry about flashing the userdata.img as it'll only wipe your internal storage which is unnecessary, and don't worry about flashing the recovery.img as you'll need TWRP again anyway). You can grab the latest stock images from here. Once you've flashed the stock images flash whatever ROM you want and you should have no more issues (hopefully).
Click to expand...
Click to collapse
Holly, thanks man! It finally worked, NO MORE proximity sensor issues, i guess after all it was a firmware issue. Thanks!

SoRiNuS said:
Holly, thanks man! It finally worked, NO MORE proximity sensor issues, i guess after all it was a firmware issue. Thanks!
Click to expand...
Click to collapse
No problems, glad to help.

Proximity & Light sensors broken?

Hi guys, looking for some suggestions.
My Proximity & Light Sensors have stopped working - and not sure what else to try. I have tried the following:
Flashed CM11S
Flashed CMOS12 & CMOS12.1
Flashed Modems individually (for relavent rom) - and tried Oxygen
If I try this app - it tells me there's no sensor available on my phone.
Looking for any other suggestions really. How likely is it that the sensors have just failed?
I've also emailed Oneplus support - but don't hold out much hope for a prompt or useful reply (looking at other peoples experiences!)
Thanks in advance.

Bump..

gneville said:
Hi guys, looking for some suggestions.
My Proximity & Light Sensors have stopped working - and not sure what else to try. I have tried the following:
Flashed CM11S
Flashed CMOS12 & CMOS12.1
Flashed Modems individually (for relavent rom) - and tried Oxygen
If I try this app - it tells me there's no sensor available on my phone.
Looking for any other suggestions really. How likely is it that the sensors have just failed?
I've also emailed Oneplus support - but don't hold out much hope for a prompt or useful reply (looking at other peoples experiences!)
Thanks in advance.
Click to expand...
Click to collapse
When you say you've flashed CMOS12 & CMOS12.1, that means the nightlies right? Flashing OxygenOS or any of the CM nightlies should've flashed their respective firmwares. I'm afraid that it is a hardware problem if that's the case.

gneville said:
Hi guys, looking for some suggestions.
My Proximity & Light Sensors have stopped working - and not sure what else to try. I have tried the following:
Flashed CM11S
Flashed CMOS12 & CMOS12.1
Flashed Modems individually (for relavent rom) - and tried Oxygen
If I try this app - it tells me there's no sensor available on my phone.
Looking for any other suggestions really. How likely is it that the sensors have just failed?
I've also emailed Oneplus support - but don't hold out much hope for a prompt or useful reply (looking at other peoples experiences!)
Thanks in advance.
Click to expand...
Click to collapse
Hi, i've the same problem. Lightsensor + Proximitysensor are not working. I also think it's a hardware issue. Today i tried a lot of modem firmware versions since there is an issue with the proximity sensor and modem firmware. No luck.
Did you found a solution? My device is still in warranty but i would like to avoid this procedure.
Regards

@dr0bz if you want to be sure it isn't an hardware issue I suggest to flash completely back to stock and see if the proximity sensor works then, if not with all the default software then I am afraid it is defect and has to be replaced

@wulsic, than i fear this is a hardware case to 100%. I've tried yesterday a complete stock OPO cm 13.2 found here on xda. Ok, than a warranty repair is not avoidable.
thx

dr0bz said:
@wulsic, than i fear this is a hardware case to 100%. I've tried yesterday a complete stock OPO cm 13.2 found here on xda. Ok, than a warranty repair is not avoidable.
thx
Click to expand...
Click to collapse
Well goodluck with sending it to warranty then and don't forget to backup ur data:good:

I've just made a whatsapp call and the app is properly using the sensor. The display is properly switching off near the ear. Funny, ideas?

dr0bz said:
I've just made a whatsapp call and the app is properly using the sensor. The display is properly switching off near the ear. Funny, ideas?
Click to expand...
Click to collapse
Lol, the proximity sensor is working in phone app as well. Perhaps there was an ota update and i just didn't noticed the new state. The weird thing naturally is that i've already returned everything to stock before.

Phone powers off after flashing CAF based ROMS no boot.

Hi guy,
I have been trying to figure this out for a while now and can't seam to figure it out. Everytime I flash a CAF based ROM after clicking reboot the phone turns off. During this time it is very hard to get the phone to turn back on. Holding the power button does not seam to do anything. I have to hold the power+volup+voldown for around 30 seconds let go and do it again in order to get back into recovery. I am not getting any errors at all when flashing. I really have no clue what it could be. I have tried every CAF based ROM I have come across here and they all do it. The only thing I can come up with is my phone has had the screen, camera, and battery replaced. Could one of these parts or another part be causing a problem that doesn't allow CAF based ROMS to work? I know its a long shot but thats all I can think of at the moment.
Right now I am working on trying to flash CyanogenMod from this thread. I have tried both version 13 and version 14 both have the same problem. This is what I have tried.
Flash HammerheadCAF reboot back into recovery
Flash bootloader&radio_HHZ20h+2.30.zip reboot to recovery
Flash cm-13.0-20161029-UNOFFICIAL-hammerheadcaf.zip
Flash opengapps
Flash SuperSu
Reboot
Black screen of death
What is wrong with this process? I have also tried the same process with cm-14.0-20161029-UNOFFICIAL-hammerheadcaf.zip. I am now going to try this same process with cm-14.1-20161029-UNOFFICIAL-hammerheadcaf.zip. I don't expect any difference though. Anyone have any suggestions?
Thanks,
Rocky
*****Update*****
I have tracked the problem down to CAF TWRP. I have formatted the phone which has removed everything except CAF TWRP and I am still getting the black screen of death situation. When the phone reboots it completely turns off. It will not respond unless I hold down power+volup+voldown for around 30 or 40 seconds. Then the phone will finally enter the bootloader. Are there any other recoveries that will flash CAF based ROMs? I don't know what else to do =(

Maybe don't flash supersu? Cm comes prerooted?

audit13 said:
Maybe don't flash supersu? Cm comes prerooted?
Click to expand...
Click to collapse
Thanks for your reply and time. I also tried flashing without SuperSU and it did the same thing. When I tapped reboot the phone would not turn on. I also tried just flashing the ROM and rebooting. The problem is with TWRP CAF because I have even formatted the phone so there was no ROM just TRWP CAF and when I tapped on reboot to recovery the phone just turned off. The power button wouldn't do anything. It would not even turn the phone on. The only thing I could do was hold the power+voldown+volup for 30 sec let go and press them again and go into bootloader.

Hey guys anyone else have any suggestions? I have tried sending a support ticket to twrp over a week ago. I haven't heard a word from them. I really want to use CAF ROMs

Hi!
I'm facing the same problem. I've been trying everything I can think of, and everything ended with a black screen when trying to boot:
Flashing stock again and then TWRP and CAF.
Flashing a lower version of TWRP (2.8.7.0) and then flashing CAF.
Flashing an AOSP version of CM, then TWRP for CAF and finally CAF.
Fixing permissions.
Changing filesystems to F2FS.
I tried to logcat, but adb logcat keeps waiting for the phone and it doesnt find anything.
Anybody has another idea of what could be happening or how to solve it?
Thanks!

I can flash caf, aswell as noncaf roms on my N5 just fine.
I used the CM14 darkrom CAF. Excellent performance, great battery life
i wiped the device in TWRP caf (Latest) (system,data,cache,dalvik0
Then i flashed the rom and the Darkrom gapps (use only those, as rom comes withouth a launcher. Pixwl launcher embeded into gapps package)
Wipe cahce/dalvik & reboot
It looped like: GOOGLElogo ,bootanimation ,self restart and it works perfectly fine since then
---------- Post added at 18:54 ---------- Previous post was at 18:53 ----------
I should also mention, that i use the european D821 model

I was beginning to wonder if it was just me. I felt like an ass for posting for help because I felt like it was my fault. I still have not gotten any response at all from twrp support. I really want to use car based Roms. I use to be able to when I first got the phone. Now I don't have a clue what the problem is. I am using the 820 USA model.
After doing a Google search for CAF TWRP no boot black screen and other combinations I have found posts around the web from people with the same issue. The only resolution was to revert to stock. I have sent TWRP support another email linking to this topic as well as contacted them on g+ hopefully we can get a resolution.

since i dont own the device.... no logs= we cant help you

Funny thing is twrp caf and non-caf are identical, the ONLY difference is that they are looking for a different device name when flashing. So I'd suggest to use the non-caf one, download any caf rom, edit the updater-script and replace every "hammerheadcaf" with "hammerhead" and it will flash just fine. If it really is just a twrp issue that will work. But I don't know why, I feel it's bound to be more than that...

I'm having this problem too, I can flash any non-CAF ROM and it will bootup fine, but any CAF rom will leave me in a black screen. Did you found any solution yet?

I have not been able to find a solution to the problem. TWERP tech support seams to be non existent. I have emailed them numerous times. They don't even take the time to say they will look into it =(

Dark_Eyes_ said:
Funny thing is twrp caf and non-caf are identical, the ONLY difference is that they are looking for a different device name when flashing. So I'd suggest to use the non-caf one, download any caf rom, edit the updater-script and replace every "hammerheadcaf" with "hammerhead" and it will flash just fine. If it really is just a twrp issue that will work. But I don't know why, I feel it's bound to be more than that...
Click to expand...
Click to collapse
What else could it be if we are able to flash absolutely anything else we want to flash except for a CAFE ROM?
I have never tried editting the updater script. Could you please explain how to do the things you described?

Ok I got an update. Today just for ****s and giggles I tried to flash the latest TWRP twrp-3.0.2-0-hammerhead.img on top of itself from inside TWRP using the image flashing process. I got the black screen I been getting that we are discussing here. Therefore, that tells me that the problem is not with TWRP CAF but with flash recovery's in TWRP. For some reason TWRP does not like that. Therefore, I am manually flashing the fallowing files the old fashion way by hand using the android sdk and adb.
1.) TWRP CAF
2.) The latest bootloader directly from the latest google factory image
3.) The latest radio directly from the latest google factory image
4.) Install the latest build of Dark ROM
I will report back with my findings.
Findings are epic fail. No boot, black screen of death.:crying: After holding down volup+voldown+power I am able to get back into recovery just like with flashing all the files through recovery when I first started. However, I can't get the damn thing to boot the ROM. I don't know what to think anymore. I think we just have to come to the conclusion that CAF based ROMs are out of the question for us :crying: :crying: :crying: When my son gets home and can hold the tablet while I operate the Nexus 5 maybe I will try to make a video of the problem. Hopefully this will help lead to a resolution.

Let me guess. All your phones have been repaired or are second-hand devices, aren't they?

experience7 said:
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
Click to expand...
Click to collapse
will a repaired device not work, mine has had the screen replaced. Nothing else just the screen.

experience7 said:
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
Click to expand...
Click to collapse
Yup, I have replaced the screen, why is that? Is it too much different than the original, shouldn't it work normally?

Not sure what's wrong with the hardware. No CAF for you guys, I'm sorry.

experience7 said:
Not sure what's wrong with the hardware. No CAF for you guys, I'm sorry.
Click to expand...
Click to collapse
Wait seriously? because i fixed my screen i am not able to use a caf rom on my device? That seems ridiculous, what would cause that to even be a thing? is there some sort of security flag it checks for?

Yeah I replaced the screen on mine too. Not sure how that plays a role. The only thing I can think of is unless there is a missing driver or something like that because our screens are different.
There's gotta be a way to fix this problem. I wish I knew how to build ROMs, kernels, and recoveries. I don't think anyone will go out of their way to fix a problem that doesn't directly affect them. So for me it is stock, rooted, with ElementalX till this pos croaks.

Not sure what the problem is. Fact is that your screen somehow differs from the 'original' one which causes CAF ROMs to blackscreen.
If you really, really want your phone to run CAF you have to provide a lot more information. You could try to get a running system and fetch some hardware information. Pretty sure there are apps on the Play Store that print hardware brands/model names, etc. Report your results and I'll use the same method to get mine. We should compare. Furthermore we'll need logs. Try to boot CAF. Of course it will blackscreen again but you can reboot to recovery and pull some logs. Maybe last_kmsg and dmesg where the latter one should be even more interesting.
And last but not least I'd like to tag @myfluxi here. Perhaps that's interesting for you...

[DEV] I extracted the updated touchscreen firmware from MIUI Nougat kernel

Haven't managed to test if it fixes the bug because I had to sleep lol.
https://github.com/Demon000/libra/commit/b5067833797cd1eb207cd976bf2419c58ca8c7ed
If anyone can test if it works, I would be very thankful.
How I did it?
Get a hex file editor.
Compile kernel with old touchscreen firmware.
Open the synaptics_biel_sharp_update.fw or synaptic_biel_auo_update.fw that have been generated in firmware/ folder in the hex editor.
Get the MIUI kernel, split it, uncompress it.
In the .fw files, the first four hex groups are magic numbers(a hex group looks like "3F"), and after that there are some common hex groups in sharp and auo firmware.
Use the hex editor to search for the common groups in the MIUI kernel, and also find the magic number before the common groups.
Use the "csplitb" program to split the the kernel binary at the newly found magic number + common groups, and strip the result to 12661 lines.
Repeat this for every common group found.
Then use the objcopy program inside the toolchain to convert the binary files to .ihex, and replace the ihex files in the firmware folder.
Done.
It is complicated, but once you get the first steps it will be easy to understand.
Although I don't know if I did a good job at explaining.

Cozmy, you are magic. Lot of thanx, Man.

Many thanks. :good:

How does one flash this?

danbrown162 said:
How does one flash this?
Click to expand...
Click to collapse
You cannot, devs that make custom roms can use it to build rom with fixed display firmware.

danbrown162 said:
How does one flash this?
Click to expand...
Click to collapse
I can post a kernel build with it later, not tested as currently I'm working on lineage os using all the vendor binaries and blobs from the nougat release.

Harrynowl said:
I can post a kernel build with it later, not tested as currently I'm working on lineage os using all the vendor binaries and blobs from the nougat release.
Click to expand...
Click to collapse
I couldn't get it to update the firmware because I was not using Xiaomi touchscreen drivers in my kernel, but the firmware itself should be working fine.
I don't want to bloat my CAF touchscreen driver so it will take me longer until I find where it fails.
Please keep us updated.

https://drive.google.com/open?id=0B9WMSJf5LSatdG5WM24zNnJPaEk
Kernel image which fixes the touchscreen problem.
PS. This kernel may use more battery, just because I didn't spend time optimizing the kernel, but rather optimizing the source-code quality, lol.
You can try flashing your original kernel to see if the fix remains.
Tested on Resurrection Remix Nougat.
EDIT: I haven't tested it on any AUO panels, as my phone has a Sharp one.
EDIT2: Flashed back the Resurrection Remix kernel and touchscreen is still fixed. Success!
Guide: backup your kernel, flash the kernel I provided, restore your old kernel.
Proof as attachment.

Cozzmy13 said:
https://drive.google.com/open?id=0B9WMSJf5LSatdG5WM24zNnJPaEk
Kernel image which fixes the touchscreen problem.
PS. This kernel may use more battery, just because I didn't spend time optimizing the kernel, but rather optimizing the source-code quality, lol.
You can try flashing your original kernel to see if the fix remains.
Tested on Resurrection Remix Nougat.
EDIT: I haven't tested it on any AUO panels, as my phone has a Sharp one.
EDIT2: Flashed back the Resurrection Remix kernel and touchscreen is still fixed. Success!
Guide: backup your kernel, flash the kernel I provided, restore your old kernel.
Proof as attachment.
Click to expand...
Click to collapse
I hope this gets implemented on next releases of our roms

solis_f said:
I hope this gets implemented on next releases of our roms
Click to expand...
Click to collapse
Just give the ROM maintainers a link to this, they will surely add it to the ROM.

Holy **** You're a hero Cozzmy13, thank you!
I just tried the image on my AUO Mi4c, and I couldn't boot TS CM13 with the kernel. The fix didn't stick after restoring the original boot partition, but I have a feeling we're very close here
I'll try flashing RR later and see what I get, I have a Nandroid backup somewhere.

Phlogistol said:
Holy **** You're a hero Cozzmy13, thank you!
I just tried the image on my AUO Mi4c, and I couldn't boot TS CM13 with the kernel. The fix didn't stick after restoring the original boot partition, but I have a feeling we're very close here
I'll try flashing RR later and see what I get, I have a Nandroid backup somewhere.
Click to expand...
Click to collapse
It's my fault, I compiled the image with RR ramdisk. It definitely works on RR Nougat, that's for sure. I have since switched to Lineage OS and the fix sticked.

I have problem . Ive installed the fix on AICP 12.1 the phone doesent boot. Returned the old kernel from backup. My phone boots but now i have problem with my hardware buttons, sometimes take 3-4 to respond to the touch. I also deleted and flashed system partititon but problem stil presist.

bankov said:
I have problem . Ive installed the fix on AICP 12.1 the phone doesent boot. Returned the old kernel from backup. My phone boots but now i have problem with my hardware buttons, sometimes take 3-4 to respond to the touch. I also deleted and flashed system partititon but problem stil presist.
Click to expand...
Click to collapse
Is the touchscreen problem fixed? If it's not then this is not my fault. If it is fixed then it's XIAOMI's fault. I will test on my device and report back. Use on-screen buttons until I do some research.

The problem was not in your update. It was from the last AICP update 23.01.2017 i installed 19.01.2017 and buttons are fine now. The touchscreen seems to be fixed iven with full wipe, going back to miui and restoring 19.01.2017 AICP.

Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?

Phlogistol said:
Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?
Click to expand...
Click to collapse
Can you explain the problem a bit more?
Did it get fixed after restoring?

Phlogistol said:
Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?
Click to expand...
Click to collapse
Mine is AUO. My touchscreen was like yours but it was from AICP update.
Basicly im not 100% shure it is fixed but i remember it couldnt register touch on the left bezel if somhere else is toched on the screen. And now is fine.

For anyone applying this from now on, the process is not reversible, because of the way the driver checks if firmware can be updated, it only wants to do upgrades, not downgrades.
Also, for anyone having problems that go away after a clean flash, they are probably not because of my fix.
If they don't go away, there is probably an updated firmware version somewhere that fixes it. I'll extract them again from the newest Nougat version.

Cozzmy13 said:
Can you explain the problem a bit more?
Did it get fixed after restoring?
Click to expand...
Click to collapse
Sure, I was a bit pressed for time yesterday
The touchscreen was inconsistent, for lack of a better word. Touches on a specific point on the screen didn't register on that location, but on some other one. It wasn't random because I could reliably reproduce this. There were also some points on the screen I couldn't reach at all. The capacitive buttons also didn't work. I'd have taken logs, but I couldn't get into developer options
I don't know exactly how this works, but the touchscreen got reversed to its original state when I managed to restore a backup of my earlier TS CM13.1 system from TWRP (I restored all available partitions). It took a few tries because of the weirdness though When I say original state, I mean it still suffers from the multitouch bug, so nothing got fixed.
Hope this is useful, but I'm stumped. Could we have different digitizers?