Hi,
I have the following problem with my Xperia Neo (hallon):
My touch screen crashed some time ago, so I bought a new one and replaced it. Since then the touch screen works in most parts of the screen just fine. Only in the range around the navigation bar the touch screen does not work. I tracked my finger with the "pointer location" option so I can see that touches are recognized from 0x0 to 478x731 pixels. Beyond that "731 pixel line" the touch screen does not work, so the lower part of my screen does not react because its resolution is 480 x 854 pixels.
My assumption is that the touch screen resolution is too low for the new touch screen so I tried to increase it. I created a "/system/usr/idc/Vendor_0000_Product_0000.idc" file and set it according to the input device configuration guidelines and added a "build.scr" to my sdcard folder but nothing changed.
Any idea what my mistake is?
Regards
Hello
I just replaced the touch screen of my generic 9inch Android Tablet running on Jelly Bean. I couldn’t get the genuine one so I just bought a compatible one: The screen works BUT it doesn’t properly map the co-ordinates on the Display. Bottom and the sides are OK but the top (about 1 inch in landscape mode) has no response. The screen is all working : The bottom matches fine but as you swipe upwards you can see that your finger touches a higher point which matches a slightly lower point on the display. When your finger reaches the top …the matching map becomes about 1inch bellow on the display.
I need help to fix this issue: I think there would be a file inside my android where there would be values to match the Display Screen mapping with the Touch Screen (digitizer)
Thank you in advance……
I changed the digitizer and display in my phone. The digitizer seems to think its resolution is larger (1080x1920) than the real display resolution (720x1280), so my touch is misplaced. I know how to change the display (physical) resolution using wm size, but that scales the digitizer resolution proportionally.
How do I change the digitizer resolution?
Output of dumpsys SurfaceFlinger: pastebin.com/gXnfxJKv
Output of dumpsys display: pastebin.com/bwkjXHxH
(The phone is Lenovo A7000, but that shouldn't matter. The error persists after upgrading firmware, rebooting etc. I haven't flashed/rooted - yet.)
After using adb shell wm size ----x---, did you try adb shell wm density ---? Density is basically the dpi of which the device will utilise
Good luck.
ramiabouzahra said:
After using adb shell wm size ----x---, did you try adb shell wm density ---? Density is basically the dpi of which the device will utilise
Good luck.
Click to expand...
Click to collapse
Thanks, but yeah, I tried and it doesn't affect the digitizer resolution either, none of the wm options do anything worthwhile.
It seems I need something like a way to change sizes of SurfaceFlinger layers.
Xellos0 said:
Thanks, but yeah, I tried and it doesn't affect the digitizer resolution either, none of the wm options do anything worthwhile.
It seems I need something like a way to change sizes of SurfaceFlinger layers.
Click to expand...
Click to collapse
SurfaceFlinger is integrated into the GPU if I am correct, so good luck with changed that
Other than that, at the time of writing, I can't come up with a solution.
Wish you best of luck
Just going to add that I have a similar yet different problem to you.
The similar part is I too also need means to change digitizer resolution but instead of going from 1080p(FHD) down to 720p(HD). My scenario needs to go from 1080p(HD) up to 2160p(UHD)
So I'm just adding more traffic in hopes people know of commands specific to the digitizer or a method to locate & modify files which report the device as only 1080p to most apps
See I've tried Shell/ABD commands but unlike most phones giving my phone a command to report itself as 4K to apps is creating an issue because seemingly even though the device knows it's 4K it reports to itself/apps as 1080p so my the digitizer is running itself as 1080p even though the hardware is sending a 4K signal to light the screen even if most times what's displayed is simply 400% 1080p
If anyone knows what files to get to (as well as how) I as well as OP can manually add the appropriate values to use the correct amount of our screens whilst utilizing the correct resolution, because like he said the PDI stuff isn't related to digitizer only display scale, we need digitizer scaling
OJKLLC said:
Just going to add that I have a similar yet different problem to you.
The similar part is I too also need means to change digitizer resolution but instead of going from 1080p(FHD) down to 720p(HD). My scenario needs to go from 1080p(HD) up to 2160p(UHD)
So I'm just adding more traffic in hopes people know of commands specific to the digitizer or a method to locate & modify files which report the device as only 1080p to most apps
See I've tried Shell/ABD commands but unlike most phones giving my phone a command to report itself as 4K to apps is creating an issue because seemingly even though the device knows it's 4K it reports to itself/apps as 1080p so my the digitizer is running itself as 1080p even though the hardware is sending a 4K signal to light the screen even if most times what's displayed is simply 400% 1080p
If anyone knows what files to get to (as well as how) I as well as OP can manually add the appropriate values to use the correct amount of our screens whilst utilizing the correct resolution, because like he said the PDI stuff isn't related to digitizer only display scale, we need digitizer scaling
Click to expand...
Click to collapse
& to clarify when in 4K all the time mode with the ABD/Shell command it's not like I can use the whole screen to touch but it'll scale that touch to 1960 by 1080, not the touch for my case is 100% accurate to where I place my finger, issue is that its only sampling 1960 by 1080 of the pixels aka just 1 corner so only useable quarter of the touchscreen with the other 75% completely dead
So I noticed that the in display button's sensitivity was too high for some reason.
I changed to 5/5 pressure needed - the lowest sensitivity.
It is now still high.
I was wondering if there is an option to change it manually (I have root installed already).
Please help. :crying:
Hello Good People
I have Galaxy s10 lite snapdragon version. Pretty expensive one. I love my phone.
Sadly, there are ghost touches at the middle of Screen as yellow circle. No warranty period. I tried apps to disable that portion of screen by overscan but no way.
Is there any way to disable that portion by changing screen resolution like this:
"adb shell wm overscan left,top,right,bottom where left, top, right and bottom are the coordinates upto which screen works.
For example, phone resolution of 480px × 854px, would have had this problem, adb shell wm overscan 0,0,0,839 to disable 15px at the bottom of the screen.
Or adb shell wm size 480x839
"
i got this code from net. It disables at bottom but i need the disabled portion placed at the middle of Screen, which i don't know. Would you please help me with correct code or any other way so that i can use the screen without being bothered by ghost touches. Please please. Help a little.
Minimum width 400 dp
Size6.7 inches, 107.8 cm2 (~87.8% screen-to-body ratio)Resolution1080 x 2400 pixels, 20:9 ratio (~394 ppi density)
Run diagnostics. Is it really a hardware issue?
Clear system cache, hard reboot, and try in safe mode.
No factory reset... not yet.
blackhawk said:
Run diagnostics. Is it really a hardware issue?
Clear system cache, hard reboot, and try in safe mode.
No factory reset... not yet.
Click to expand...
Click to collapse
Done but no way out.