Touchscreen not working on any Android x86 OS

Touchscreen not working on any Android x86 OS

TechTablets Forums Cube Forums Cube Mix Plus Touchscreen not working on any Android x86 OS

Tagged: 

This topic contains 18 replies, has 4 voices, and was last updated by  akasection 2 months, 1 week ago.

Viewing 4 posts - 16 through 19 (of 19 total)
  • Author
    Posts
  • #143273

    virgo
    Participant
    • Posts: 156

    Fast start-up is relate to file system trace, no thing to do with firmware

    For example you can not mount a NTFS partition as Read/Write if fsck failed on that partition.

    Something wrong in your assumption

    P/S after reading your long procedure. I think, the “WORK-AROUND”, you describe need SUSPEND function of Android.

    This may relate to File System trace as you say with FASTBOOT.

    That is the only possible explanation of Windows affect in this case

    There is nothing to do with touchscreen firmware.

    Windows does, in fact affect other dual boot system in term of peripheral firmware download.

    Like I said as observed in dual boot Hackintosh/Linux with Windows machine, when Bluetooth firmware is downloaded to the board,

    then a hot-reboot to Hacckintosh/Linux make it work.

    So it is obvious that different version of Windows has different version of firmware!

    All Linux/Hackintosh gurus of the Linux/Hackintosh community know this.

    End!


    If you found my answer helpful, you may donate to me at my signature above!

    #143284

    akasection
    Participant
    • Posts: 8

    yeah, I rephrased it wrong, actually I’m not implying that touchscreen driver failed because of windows, but the ‘hack’ one.

    Now I think I’ve explained the real problem, is there any way to fix that behaviour? It’s kinda hassle that I need to “suspend” first everytime I want to use the touchscreen.

    #143524

    Mario Ray Mahardhika
    Participant
    • Posts: 2

    I use PhoenixOS 2.6.4, touchscreen works from the beginning but the desktop is upside down. Easily fixed by installing rotation control app and turn on its start on boot functionality (another way would be to tinker with init.sh, but I’m too lazy to do that). The difference, probably, is that I install from the .img instead of .exe. There might be differences in result between the two install methods. I just want it natively, no Windows interference at all.

    #143786

    akasection
    Participant
    • Posts: 8

    Hmm.. interesting experience…

    or maybe it because I disabled C-power state on BIOS?

     

Viewing 4 posts - 16 through 19 (of 19 total)

You must be logged in to reply to this topic.

Lost Password