help with inverted touch screen issue

[XiaoTao Liu]

Hi,

I am trying to install the android 8.1 to my teclast x98 air 3G(Intel Bay Trail-T Z3736F). Everything appears to be cool except that the 

touch screen has some mirror or inverted problem, meaning when I touch left, it is actually right. I touch upside and it is actually downside. 

 I checked driver in win10, it has some name of Goodix. Anyone know how to fix it?

[Felix lau]

在 2020年1月15日星期三 UTC+8下午10:12:55，XiaoTao Liu写道：

i've got dis issue too. so far i wanna know how to port the windows driver to android x86 to make it work but cn't find anyways to know how  

[Juuso Pikkarainen]

Hey. Good that someone brings up goodix touchscreen issues. I have issues with Android 6 and 7 on My HP Stream 7. I dont know how it is called, but almost everytime when i touch something on screen, it keeps pressing it like im holding my finger on the screen. Even im not. I rather use those builds because Android 8 is slow. Oh. And i have issues with camera not existing and it doesnt wake from sleep when power button is pressed. Android 8 solves those, expect that camera issue. But it is painfully slow. Android 9 has that touch issue, camera issue and hibernate issue.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/b17ffc5f-c897-43d9-8142-2aeb06168081%40googlegroups.com.

[Daniel Cheung]

Probably same problem I had with my Teclast X98 Plus (A5C6). You need to modify the init.sh file because the initialization script doesn't understand what kind of device it is. At least for my X98 Plus, Teclast didn't bother writing any unique values to the DMI on the BIOS so every time I try a new Android X86 version, I have to modify the file again or modify it before I compile a custom disk image. The Goodix driver is included and it works, the problem is it doesn't know what the correct orientation is. See this thread for solution for screen rotation.

https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!searchin/android-x86/auto$20rotation%7Csort:date/android-x86/MW0rE7Gkpqw/aQgxNboUCgAJ

As for sleep and camera, I don't think you will find any solutions to them yet. There are a lot of camera sensors available in the kernel configuration file to support building custom image but I'm not sure which are supported in the default image file that you download. Furthermore, sleep is something that has been an issue and only recently seem to be working better in Android 9. Not working 100% but at least it doesn't black screen when you try to wake up the device. Since the Stream 7 only has 1GB of RAM, I'm not sure if you can even run any version beyond 7 even with animation disabled. You can ask the dev team and see if they are interested in keeping 7 around as a long term support version. It would definitely help the older devices.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/CADqGsX4AB3RJxfOYnshZW7H4Kvc1Kh7-N%2Bnf7%2B3nLNfNtvoHsg%40mail.gmail.com.

[XiaoTao Liu]

Your reply helped me making some progress. 

I didn't mention the auto rotation not working issue in my first post, and now the code on the thread you sent fix that.

However, the inverted touch remains the same. Do you know how to fix that?

As for the auto rotation, the first 3 lines of code in that thread does make the auto rotation work. But it also works in the inverted way(180 degree). When I add the 4th line of code, it works 90 degree deviation, meaning when I put the tablet portrait, it shows landscape. 

On Thursday, January 16, 2020 at 4:57:19 AM UTC+8, BrokenE39 wrote:

Probably same problem I had with my Teclast X98 Plus (A5C6). You need to modify the init.sh file because the initialization script doesn't understand what kind of device it is. At least for my X98 Plus, Teclast didn't bother writing any unique values to the DMI on the BIOS so every time I try a new Android X86 version, I have to modify the file again or modify it before I compile a custom disk image. The Goodix driver is included and it works, the problem is it doesn't know what the correct orientation is. See this thread for solution for screen rotation.

https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!searchin/android-x86/auto$20rotation%7Csort:date/android-x86/MW0rE7Gkpqw/aQgxNboUCgAJ

As for sleep and camera, I don't think you will find any solutions to them yet. There are a lot of camera sensors available in the kernel configuration file to support building custom image but I'm not sure which are supported in the default image file that you download. Furthermore, sleep is something that has been an issue and only recently seem to be working better in Android 9. Not working 100% but at least it doesn't black screen when you try to wake up the device. Since the Stream 7 only has 1GB of RAM, I'm not sure if you can even run any version beyond 7 even with animation disabled. You can ask the dev team and see if they are interested in keeping 7 around as a long term support version. It would definitely help the older devices.

On Wed, Jan 15, 2020 at 6:55 AM Juuso Pikkarainen <juudo...@gmail.com> wrote:

Hey. Good that someone brings up goodix touchscreen issues. I have issues with Android 6 and 7 on My HP Stream 7. I dont know how it is called, but almost everytime when i touch something on screen, it keeps pressing it like im holding my finger on the screen. Even im not. I rather use those builds because Android 8 is slow. Oh. And i have issues with camera not existing and it doesnt wake from sleep when power button is pressed. Android 8 solves those, expect that camera issue. But it is painfully slow. Android 9 has that touch issue, camera issue and hibernate issue.

ke 15. tammik. 2020 klo 16.13 XiaoTao Liu <kevin...@gmail.com> kirjoitti:

Hi,

I am trying to install the android 8.1 to my teclast x98 air 3G(Intel Bay Trail-T Z3736F). Everything appears to be cool except that the 

touch screen has some mirror or inverted problem, meaning when I touch left, it is actually right. I touch upside and it is actually downside. 

 I checked driver in win10, it has some name of Goodix. Anyone know how to fix it?

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.

To unsubscribe from this group and stop receiving emails from it, send an email to andro...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/b17ffc5f-c897-43d9-8142-2aeb06168081%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.

To unsubscribe from this group and stop receiving emails from it, send an email to andro...@googlegroups.com.

[Daniel Cheung]

To be honest, I don't know how the value of 102 is determined. The closest information I could find is this commit:

https://osdn.net/projects/android-x86/scm/git/hardware-libsensors/commits/76cd154fcd4ccde8d211183120668d9480b0bfb2

setprop hal.sensors.axis.order "1,0,2" # for Y,X,Z

So I guess you have to play with the number like 012, 021, 102, 120, 210, 201 and see which one works. 

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/33353367-90b6-4bb7-9b4d-f31cc90a8291%40googlegroups.com.

[Chih-Wei Huang]

Daniel Cheung <dwt.c...@gmail.com> 於 2020年1月16日 週四 上午7:49寫道：

>
> To be honest, I don't know how the value of 102 is determined. The closest information I could find is this commit:
> https://osdn.net/projects/android-x86/scm/git/hardware-libsensors/commits/76cd154fcd4ccde8d211183120668d9480b0bfb2
>> setprop hal.sensors.axis.order "1,0,2" # for Y,X,Z

Note this commit is for sensors of hdaps type.
All of you are using iio sensors, I guess.
So the above properties don't apply.

> So I guess you have to play with the number like 012, 021, 102, 120, 210, 201 and see which one works.
>
> On Wed, Jan 15, 2020 at 2:57 PM XiaoTao Liu <kevin....@gmail.com> wrote:
>>
>> Your reply helped me making some progress.
>> I didn't mention the auto rotation not working issue in my first post, and now the code on the thread you sent fix that.
>>
>> However, the inverted touch remains the same. Do you know how to fix that?
>>
>> As for the auto rotation, the first 3 lines of code in that thread does make the auto rotation work. But it also works in the inverted way(180 degree). When I add the 4th line of code, it works 90 degree deviation, meaning when I put the tablet portrait, it shows landscape.

If your axis is inverted instead of exchanged,
you should add

set_property ro.iio.accel.x.opt_scale -1
set_property ro.iio.accel.y.opt_scale -1
set_property ro.iio.accel.z.opt_scale -1

Use one or more of them, depends on which axes are inverted.

About the original question, you may need to calibrate the touchscreen.
See the post for how to do it:
https://groups.google.com/d/msg/android-x86/sUPPAg3rZU0/To9daLBGCgAJ



--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[XiaoTao Liu]

Thank you Chih-Wei. I read this thread before and tried those code in terminal, but the inverted touch screen remained the same.By inverted I mean when I touch the upperleft corner, the tablet shows that I actually touch the lower right corner.It feels like the touch screen rotated 180 degree around the center.
Is there other ways I can try to fix this?

[Chih-Wei Huang]

XiaoTao Liu <kevin....@gmail.com> 於 2020年1月16日 週四 下午1:37寫道：

>
> Thank you Chih-Wei. I read this thread before and tried those code in terminal, but the inverted touch screen remained the same.By inverted I mean when I touch the upperleft corner, the tablet shows that I actually touch the lower right corner.It feels like the touch screen rotated 180 degree around the center.
> Is there other ways I can try to fix this?

The calibration would fix it.
Make sure you have done it correctly.

Check the content of /data/misc/tscal/pointercal,
it should contain 7 integers.
And check logcat to see if it contains
the line "pointercal loaded ok"

[kevin.Liu]

Great, finally I got gravity working by adding 

set_property ro.iio.accel.y.opt_scale -1

and delete the line of 102. Still, I dont know what the line of 102 means.

Now leaves the touch screen issue. I noticed in the init.sh file has already the same code as in the thread you provide.

---

发自我的iPhone

------------------ Original ------------------

From: Chih-Wei Huang <cwh...@android-x86.org>

Date: Thu,Jan 16,2020 10:39 AM

To: Android-x86 <andro...@googlegroups.com>

Subject: Re: help with inverted touch screen issue

-- 
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/CAKc24n20wtcNTWJkkxz%2B28U431SOWbDh8hvg-5W6KfBFAWp_MQ%40mail.gmail.com.

[XiaoTao Liu]

Somehow this time it works. Thanks a lot!

On Thursday, January 16, 2020 at 3:05:46 PM UTC+8, Chih-Wei Huang wrote:

XiaoTao Liu <kevin...@gmail.com> 於 2020年1月16日 週四 下午1:37寫道：

[Chih-Wei Huang]

kevin.Liu <kevin....@gmail.com> 於 2020年1月16日 週四 下午7:33寫道：

>
> Great, finally I got gravity working by adding
>
> set_property ro.iio.accel.y.opt_scale -1

Fine. You may provide your DMI info. I'll add it.

> and delete the line of 102. Still, I dont know what the line of 102 means.

x=0, y=1, z=2, 102 means x and y are exchanged. easy?

> Now leaves the touch screen issue. I noticed in the init.sh file has already the same code as in the thread you provide.

Yes, but that is only executed for specific devices.
You should add yours.

Another way is to modify the driver directly.
That requires you have the knowledge to read, change
and compile the kernel. See the patch as an example:

https://osdn.net/projects/android-x86/scm/git/kernel/commits/69d201a837884f67401e2e0046817b5ede78ca7f

[kevin.Liu]

I don't know how to copy paste DMI info, so I took a photo.

After trying 8.1 for a while, I found it crash from time to time. So I installed cm14.1 r3 instead. I did the same mod as I did in 8.1, and the auto rotation got fixed again, but calibration didn't work. I found the pointercal became a folder instead of a file. Do you know how to fix it?

---

发自我的iPhone

------------------ Original ------------------

From: Chih-Wei Huang <cwh...@android-x86.org>

Date: Fri,Jan 17,2020 10:49 AM

To: Android-x86 <andro...@googlegroups.com>

Subject: Re: help with inverted touch screen issue

-- 
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/CAKc24n2uMfdOAVOjyivqJSZMXCqRDpSoiZ_vjEZ%2Bx7AQcXL%3DJg%40mail.gmail.com.