E
E
Evgeny Dolbanovsky2019-03-20 16:34:10
linux
Evgeny Dolbanovsky, 2019-03-20 16:34:10

Where are the touchscreen drivers in android firmware???

There is OnePlus One 16gb, it broke the screen, then changed it to a new one complete with a touchscreen.
BUT
The touchscreen on any firmware goes crazy, a huge number of phantom clicks, it's impossible to use the OS at all. I found the firmware cm-12.0-YNG1TAS17L in which there are fixes for the touchscreen, the touchscreen behaves as it should, there are no clicks, but there is another jamb, but that's another story.
I want to pull out the touchscreen driver, and slip it instead of the stock driver in other firmware.
For example, slip it into cm-12.1 to put Kali without dancing with a tambourine.
Tell me, is this idea generally real with a driver change?
At what stage is the touchscreen driver loaded?
Where are the drivers for the touchscreen?
Can I just replace the files?
If you can’t just do it, write a simple algorithm how to do it, I really want to get confused)))
+ there is another interesting symptom, the touchscreen is furious in TWRP, if I think correctly, then the driver is loaded from boot.img ???

Answer the question

In order to leave comments, you need to log in

3 answer(s)
V
ValdikSS, 2019-04-03
@ValdikSS

The touchscreen driver is usually compiled into the kernel (not assembled by a module). So the answer is in the core.

T
TyzhSysAdmin, 2019-03-20
@POS_troi

Don't thank
https://www.xda-developers.com/

R
rPman, 2019-03-20
@rPman

Try to find calibration tools for your touchscreen, maybe it is already in your firmware (although in cm it seems that everything is cut out, including the engineering menu)
In the vast majority of cases, drivers in Linux are strongly tied to the kernel version (and therefore to a specific firmware) , they are either compiled into the kernel, or assembled as a module and lie in the initrd image side by side or in the firmware file system.
In general, just transferring files will not work. But in the case of a touchscreen, in theory, the problem is not in the driver, but in the calibration, i.e. accompanying configuration files that this driver uses. True, in each individual case, you need to study the issue, because vendors are sawing and they almost always do not want to share source codes and documentation.
here is an example of x86 android calibration of its universal driver blog.inelsis.ru/?p=318 but by itself the instruction will not help here, just the idea itself in this
ps if you find it, please share with the world

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question