ASUS EEEPC T101MT - Android x86 - Touchscreen not working.

[ET]

I have read threw the forums and tried every solution to get the
touchscreen to work.

Touchscreen calibration appears upon boot and reacts on touch, but
once the system is up, it is no longer responding to the touchscreen.

Please give a detail description I have seen the linux fix for the
touchscreen which is
sudo rmmod usbhid
sudo rmmod hid
sudo modprobe hid
sudo modprobe usbhid quirks=0x0486:0x0186:0x0040

How would this work with android if possible please give me detailed
how-to can I run these commands in the Terminal Emulator?

Tried both of these:

http://groups.google.com/group/android-x86/browse_thread/thread/c1e0d17cb549f38d/f4b3d36a237f66bb?lnk=gst&q=t101mt#f4b3d36a237f66bb

http://groups.google.com/group/android-x86/browse_thread/thread/96c208ad977c116c/ffef0f80ddc6018e

Replaced the kernel with the attached ones from the post above
numerous times and still no luck.

Also I cannot access the nightly build server….

Please help I have been fighting with this issue for a while now with
no success.

[Mnauel bbasd]

Hi
I build this last version 2.2.2 and touchscreen work but with modifications. But wireless is NOT working. The first time that I connect with WIFI, is completely OK, But when I reboot the computer I can not connet again. WIFI error. NO networks... The command dmesg in console: ath9k unload...

I build always the last gingerbread-x86 version. The compilation is OK. But Android no run, Black screen when I star the system.
 Previous version of gingerbread work fine, bul the screen very slow. like reported previosly by people.

Regards
mabo

2011/4/20 ET <et...@hotmail.com>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Chih-Wei Huang]

I've pushed the touchscreen driver for T91MT/T101MT.
Multi-touch works well on my tested T91MT and T101MT.
Special thanks to Benjamin from Enac who
provided the driver.

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

[Mnauel bbasd]

Hi

On my T101MT the touchscreen NOT WORK with new multitouch driver. When I start Android, the calibration screen does NOT appear, this is not important since with some old versions neither it appeared and the touch screen work fine whitout the calibration. I have had to enable again the egalax driver in the kernel (this have been disabled) . With egalax the touch screen work fine on my T101MT.

If I can do any test to help, I will be delighted in making it.

The other problem is the WIFI. This not work, only first time, but later when I reboot the computer WIFI does not work any more...

Regards
mabo

2011/4/22 Chih-Wei Huang <cwh...@android-x86.org>

[Chih-Wei Huang]

It is said there are two types touchscreen
used in T101MT.
One used hid-mozart, now works
fine with the new hid-multitouch driver.
Another used hid-egalax, which is also
merged to hid-multitouch.
But I have no chance to test it.

Please provide the pci id of your touchscreen.
I'll see if possible to correct it.

2011/4/22 Mnauel bbasd <mabo6...@gmail.com>:

> On my T101MT the touchscreen NOT WORK with new multitouch driver. When I
> start Android, the calibration screen does NOT appear, this is not important
> since with some old versions neither it appeared and the touch screen work
> fine whitout the calibration. I have had to enable again the egalax driver
> in the kernel (this have been disabled) . With egalax the touch screen work
> fine on my T101MT.
>
> If I can do any test to help, I will be delighted in making it.

--

[Mnauel bbasd]

Please, clould you tell me what is the command (ubuntu or Android) to get the pci id information that you really need?

Thanks
mabo

2011/4/22 Chih-Wei Huang <cwh...@android-x86.org>

It is said there are two types touchscreen

[Arobase40]

Chih Wei,

Some touchscreens and specifically those with a resistive panels need
a little patch, even with the hid-multitouch module !

Look at my tarball I sent you some times ago. There were comments
about this in the test for the 1420P* and 1820P*.

This should be something like :

echo 3 $VendorID $ProductID 0 > /sys/module/hid_multitouch/drivers/hid
\:hid-multitouch/new_id

May be not the 0 parameters after $ProductID, but should be very
close... ^^

if unsure, ask Benjamin Tissoires and Stephane Chatty to clarify.

On 22 avr, 08:35, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> It is said there are two types touchscreen
> used in T101MT.
> One used hid-mozart, now works
> fine with the new hid-multitouch driver.
> Another used hid-egalax, which is also
> merged to hid-multitouch.
> But I have no chance to test it.
>
> Please provide the pci id of your touchscreen.
> I'll see if possible to correct it.
>

> 2011/4/22 Mnauel bbasd <mabo666...@gmail.com>:

[Mnauel bbasd]

This is the info from ubuntu:

cat /proc/bus/input/devices:
I: Bus=0003 Vendor=0eef Product=480d Version=0100
N: Name="eGalax Inc. USB TouchController"
P: Phys=usb-0000:00:1d.1-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input5
U: Uniq=
H: Handlers=mouse0 event5
B: PROP=0
B: EV=b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=6608000 1000003

lsusb:
Bus 003 Device 002: ID 0eef:480d D-WAV Scientific Co., Ltd


Regards
mabo

2011/4/22 Arobase40 <arob...@gmail.com>

[Arobase40]

Is your touch panel not working at all with hid-multitouch or is it
"only" a multitouch issue ???

On 22 avr, 09:41, Mnauel bbasd <mabo666...@gmail.com> wrote:
> This is the info from ubuntu:
>
> cat /proc/bus/input/devices:
> I: Bus=0003 Vendor=0eef Product=480d Version=0100
> N: Name="eGalax Inc. USB TouchController"
> P: Phys=usb-0000:00:1d.1-2/input0
> S: Sysfs=/devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input5
> U: Uniq=
> H: Handlers=mouse0 event5
> B: PROP=0
> B: EV=b
> B: KEY=400 0 0 0 0 0 0 0 0 0 0
> B: ABS=6608000 1000003
>
> lsusb:
> Bus 003 Device 002: ID 0eef:480d D-WAV Scientific Co., Ltd
>
> Regards
> mabo
>

> 2011/4/22 Arobase40 <arobas...@gmail.com>

[Mnauel bbasd]

Hi

My touch panel not working at all with hid-multitouch.
But work fine with hid-egalax module.

Regards
mabo

2011/4/22 Arobase40 <arob...@gmail.com>

Is your touch panel not working at all with hid-multitouch or is it

[Arobase40]

Ok, I guess "someone" will get in touch with you for this
problem... ;)

One "big guruuuu". :-)

On 22 avr, 17:47, Mnauel bbasd <mabo666...@gmail.com> wrote:
> Hi
>
> My touch panel not working at all with hid-multitouch.
> But work fine with hid-egalax module.
>
> Regards
> mabo
>

> 2011/4/22 Arobase40 <arobas...@gmail.com>

[Mnauel bbasd]

I dont need one "big guruuuu", only people that like to work in this project, not as you.

Regards
mabo

2011/4/22 Arobase40 <arob...@gmail.com>

Ok, I guess "someone" will get in touch with you for this

[Arobase40]

What do you mean with : "not as you." ??? ;-)

I'm far from being a guru in any way, but there may be only a few
persons (may be 2) able to solve your problem, and if you don't want
them to help you...

Up to you ! :-)

On 22 avr, 18:36, Mnauel bbasd <mabo666...@gmail.com> wrote:
> I dont need one "big guruuuu", only people that like to work in this
> project, not as you.
>
> Regards
> mabo
>

> 2011/4/22 Arobase40 <arobas...@gmail.com>

[ET]

I have tried the most recent nightly build eeepc-201100426.iso and the
touchscreen for my T101MT does not work.

Is there something I am missing? Do I need enter some command some
where to get the touchscreen driver?

I see on the nightly build server there is an eeepc_info file with the
T101MT referenced. Am I suppose to do something with that file?

Please help and Thank you in advance.

[Mnauel bbasd]

Hi ET

I have tried nightly build eeepc-201100426.iso and WORK FINE. This iso are not using the hid-multitouch driver, are using the hid-egalax and the touch screen work fine with this driver.

Regards
Mabo

2011/4/26 ET <et...@hotmail.com>

[ady080808]

You should use viewpad image.Because eeepc image didnt support touchscreen.
----- Orig. e-mail -----

[ET]

Tried both the nightly viewpad from last night, and the main 2.2
viewpad on the download page and still no touchscreen.

[Chih-Wei Huang]

2011/4/26 ady080808 <ady0...@gmail.com>:

> You should use viewpad image.Because eeepc image didnt support touchscreen.

Don't mislead others.
Of course eeepc target supports all touchscreen
series of Eee PC, including T91, T91MT, T101MT...

What we discussed here is a driver issue
in the recent changes of android-2.6.38 kernel.

[Chih-Wei Huang]

It's very strange that the nightly iso still uses hid-egalax driver.

If it uses the latest kernel, there is even no hid-egalax driver.
It is replaced by hid-multitouch and is removed.
The eeepc target has been updated to use hid-multitouch.

I doubt his source tree is not updated daily.

[Mnauel bbasd]

Hi Chih

Yes very strange always for me. But I can confirm that this latest use hid-egalax and not hid-multitouch.

Regards
Mabo

2011/4/26 Chih-Wei Huang <cwh...@android-x86.org>

[Arobase40]

in fact, all "ancient" drivers still exist in the 2.6.38 kernel and
are defined as modules in android-x86_defconfig.

So unless the "auto-detect" mechanism (if any) goes wrong and revert
to hid-egalax, or "someone" else set the the hid-egalax driver in the
eeepc target ??? ^^

On 26 avr, 13:39, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> It's very strange that the nightly iso still uses hid-egalax driver.
>
> If it uses the latest kernel, there is even no hid-egalax driver.
> It is replaced by hid-multitouch and is removed.
> The eeepc target has been updated to use hid-multitouch.
>
> I doubt his source tree is not updated daily.
>

[Mnauel bbasd]

Yes,

but the hid-egalax has been disable from the makefile. Then this module in not compile directly and never generated. You have to modify the makefile and others files to use the hid-egalax with 2.6.38 kernel and Android 2.2.2

Regards
Mabo

2011/4/26 Arobase40 <arob...@gmail.com>

[Arobase40]

I guess you didn't understand what I meant... ^^

AGAIN : hid-egalax driver is defined as module in android-
x86_defconfig, so if you use EXTMOD="$EXTMOD hid-egalax" or modprobe
hid-egalax in your target and modify eeepc-defconfig accordingly, it
will get compiled and loaded with your build.

So even though the build id and the kernel could be the newest, but if
the eeepc target is still an old one, this may be the problem... ^^

On 26 avr, 20:17, Mnauel bbasd <mabo666...@gmail.com> wrote:
> Yes,
>
> but the hid-egalax has been disable from the makefile. Then this module in
> not compile directly and never generated. You have to modify the makefile
> and others files to use the hid-egalax with 2.6.38 kernel and Android 2.2.2
>
> Regards
> Mabo
>

> 2011/4/26 Arobase40 <arobas...@gmail.com>

[Mnauel bbasd]

Sorry for not understand you,

but when i compiled the 2.6.38 with android and enabled hid-egalax, I had to modify eeepc_defconfig, eeep_info and the MAKEFILE in the hid directory, because if not the module will not be generated.
Maybe I was wrong. Maybe the makefile is generated automatically by some way, I am not sure...

Mabo

2011/4/26 Arobase40 <arob...@gmail.com>

[Arobase40]

You do not have to modify the Makefile file, as it is not used.

Only the above stated files are needed.

If you still have problem, then your problem is somewhere else : may
be a typo in one of your definition files ???

On 26 avr, 20:42, Mnauel bbasd <mabo666...@gmail.com> wrote:
> Sorry for not understand you,
>
> but when i compiled the 2.6.38 with android and enabled hid-egalax, I had to
> modify eeepc_defconfig, eeep_info and the MAKEFILE in the hid directory,
> because if not the module will not be generated.
> Maybe I was wrong. Maybe the makefile is generated automatically by some
> way, I am not sure...
>
> Mabo
>

> 2011/4/26 Arobase40 <arobas...@gmail.com>

[Mnauel bbasd]

Ok

Thanks
Mabo

2011/4/26 Arobase40 <arob...@gmail.com>

[ET]

Can someone please post attach the correct file or kernel for me to
use? Tried the nightly again with no luck touch screen still does not
work for me

When android boots it says

TBLIB calibration utility
touch crosshair to calibrate
Press enter to skip

.... The touchscreen responds when calibrating but once finished it
boot into the android OS and the touchscreen stops working.

Is there some code anyone wants me to try? I am going on now 2 weeks
trying to get the touchscreen to work for android on my eee pc T101MT.

I ran the code :

cat /proc/bus/input/devices

I: Bus=0003 Vendor=0eef Product=480d Version=0100

N: Name="AsusTek, Inc. Multitouch(YFO)"

P: Phys=usb-0000:00:1d.1-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/
input5
U: Uniq=
H: Handlers=mouse0 event5

B: EV=1b
I don't see the "eGalax Inc. USB TouchContorller" do I have a
different device?

[Arobase40]

This touch panel is already under investigation by experts, so be
patient, please.

The weird thing is that it works a for a while... ??? ^^

If you know how to use console (AFT F1), type "lsmod | more" (without
quote) and watch if you can see hid-multitouch or hid-egalax.

If none of them exist try modprobe hid-mutitouch and back to ui with
ALT F7 to see if you get some responses

if not, back to console, then modprobe hid-egalax, and again check if
that work.

If not we could try something else, later...

[ET]

There is only a hid-egalax there is no hid-multitouch

I run the command modprobe hid-egalax and it accepts the command but
when I return with ALT F7 the touchscreen does not work still.

[Chih-Wei Huang]

Oh, I'm really confused what you talked.
I even doubt if I forgot to commit and push something.
I double checked and confirmed I didn't miss something.

So let me emphasis again. In the latest
froyo-x86/gingerbread-x86 tree, the facts are:

* kernel is 2.6.38, the hid-multitouch driver is merged
to replace other multitouch drivers, including
hid-egalax, hid-hanvon, hid-cando, hid-penmount, ...
All the old drivers are REMOVED from the source tree,
including the source, Kconfig and Makefile.
* All the targets I maintained including eeepc, tegav2 and asus_laptop
are updated to use the new hid-multitouch driver.

So what Arobase40 said is wrong.

What Mabo said is partially correct, however,
it's not possible to use hid-egalax unless
you manually added back hid-egalax.c.

To verify, the HEAD commit in kernel dir should be 616fce5,
while the HEAD commit in device/asus/eeepc is 3139a8a.
If your tree doesn't have the same commits as mime,
you have to repo sync again.
Note repo sync may fail to update your tree probably due to
you have modify something that conflict with the upstream.
If so, you need to resolve it and sync again.
(hint: use git stash to save your local changes
and git stash pop to apply them again)

--

[Mnauel bbasd]

Hi Chih

Yout are right, the current repo does not contain the source code of hid-egalax.cpp. But when i try hid-multitouch firts time some time ago, that is,The first time you post that changed to the new hid-multitouch, at that time the source code of hid-egalax was into the hid directory. This is while i could compile hid-egalax module manually...


Regards
mabo

2011/4/27 Chih-Wei Huang <cwh...@android-x86.org>

--

[Arobase40]

On 27 avr, 03:52, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> Oh, I'm really confused what you talked.
> I even doubt if I forgot to commit and push something.
> I double checked and confirmed I didn't miss something.
>
> So let me emphasis again. In the latest
> froyo-x86/gingerbread-x86 tree, the facts are:
>
> * kernel is 2.6.38, the hid-multitouch driver is merged
>   to replace other multitouch drivers, including
>   hid-egalax, hid-hanvon, hid-cando, hid-penmount, ...
>   All the old drivers are REMOVED from the source tree,
>   including the source, Kconfig and Makefile.
> * All the targets I maintained including eeepc, tegav2 and asus_laptop
>   are updated to use the new hid-multitouch driver.
>
> So what Arobase40 said is wrong.
>

Chih Wei, If I'm wrong, how does it come I still have all the
mentioned drivers in the backup tar ball I made from FRG83G ID with
2.6.38 kernel ?!?!?!?!
I kept this tree, as I'm still trying to debug and resolve the mesa
auto-detect mechanism. I can't send it back to you as the tar ball is
too big with my slow internet connexion.

So unless I have a ghost and alien version retrieved/downloaded from
nowhere, please don't state I'm wrong !!!

I have spent many hours to download it twice and to check there was
REALLY a mesa issue when you issued doubts about this problem before.

[Chih-Wei Huang]

I don't know why you so insist your point.
I don't care what your source tree is --
apparently you didn't update your tree.

What I said is the fact on the android-x86
git repository, the common code base
all our developers use.

If you have spent a minute to check the
git server, you will know why you were wrong.

2011/4/27 Arobase40 <arob...@gmail.com>:

[ET]

What are the commands I need to run to repo sync? How do I update my
source tree?

Thank Chih you da man

[Chih-Wei Huang]

$ repo sync

在 2011年4月27日下午9:39，ET <et...@hotmail.com> 寫道：
> What are the commands I need to run to repo sync? How do I update my
> source tree?

--

[Arobase40]

If I do so insist it's because technically I was NOT wrong !

My source tree does contain all the mentioned drivers ! If you changed
everything afterward, is just another aspect you should have
mentioned.

That's all. ;-)

On 27 avr, 09:48, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> I don't know why you so insist your point.
> I don't care what your source tree is --
> apparently you didn't update your tree.
>
> What I said is the fact on the android-x86
> git repository, the common code base
> all our developers use.
>
> If you have spent a minute to check the
> git server, you will know why you were wrong.
>

> 2011/4/27 Arobase40 <arobas...@gmail.com>:

[Arobase40]

Well I didn't even realize you felt concerned and attacked by my
previous post, and I was surprised by your answer :

"So unless the "auto-detect" mechanism (if any) goes wrong and revert
to hid-egalax, or "someone" else set the the hid-egalax driver in the
eeepc target ??? ^^ "

By using the word "someone" I didn't mentioned YOU were in cause, but
suggested someone else.
Just as you were yourself also surprised the nightly build contains
the hid-egalax module... ^^

As a reminder, I quote back your answer :

"It's very strange that the nightly iso still uses hid-egalax driver.

If it uses the latest kernel, there is even no hid-egalax driver.
It is replaced by hid-multitouch and is removed.
The eeepc target has been updated to use hid-multitouch.

I doubt his source tree is not updated daily. "

:-)

On 27 avr, 03:52, Chih-Wei Huang <cwhu...@android-x86.org> wrote:

[Nicolas]

For my eGalax device, the only working solution is to use the
eGestured service (see sparta device).

N.

[ET]

I searched and could only find this post

http://groups.google.com/group/android-x86/browse_thread/thread/f6c439db8963a028/50e3694aec80bfe7?lnk=gst&q=eGestured+service#50e3694aec80bfe7

What commands did you run to get the eGestured server on the sparta
device?

Please write it out for so a one year old newb can read it. Thanks

[ET]

Ran repo sync and still nothing still shows the touch screen driver as
AsusTek, Inc. Multitouch(YFO)

If someone thinks they know what files I might need or which kernel
could help me with this mess, you please attach them to this post

Thank you

[Arobase40]

I thought the answer was clearly stated above in my previous post ???

I don't know much about eGestured server , as this sounds unlikeky not
"natural" to "my point of view"...

I'm not willing to hurt anyone and don't want the author of this
feature to feel upset in any way, right ? ;-)

[ET]

Sorry ment eGestured service

On Apr 28, 10:57 am, ET <et...@hotmail.com> wrote:
> I searched and could only find this post
>

> http://groups.google.com/group/android-x86/browse_thread/thread/f6c43...

[Nicolas]

> Chih Wei, If I'm wrong, how does it come I still have all the
> mentioned drivers in the backup tar ball I made from FRG83G ID with
> 2.6.38 kernel ?!?!?!?!

I had the same question, but I think it is just that the out folder is
not automatically cleaned.

[ET]

Ok no luck with the repo sync. What can I do? Are you working on
this issue in the next release?

I only bought this eee pc to use with android and still cant get the
touch screen working please anybody who might think they can help me
please post the commands for me to run.

Help I need somebody.......

Thanks

On Apr 27, 10:46 am, Chih-Wei Huang <cwhu...@android-x86.org> wrote:

[Arobase40]

I don't know if that may help you, but you could try to downgrade the
kernel to 2.6.35, then get my target which contains a tar ball with
all the touch drivers (including hid-multitouch). Then read the
aspire1000s_info file which also contains a trick for unsupported
touch panels (try with and without this "trick")... ^^

If hid-multitouch doesn't work, try hid-egalax drivers (or hid-
mosart).

You may also have to set CONFIG_HID=y and CONFIG_USB_HID=y as well (if
not already set) in kernel/arch/x86/configs/android-x86_defconfig.

No guarantee this works though... ^^

[Silverio Cortez]

I tried alot of fixed on in articles here and none seem to work
only thing i got is when i went to debug mode it said Asustek Inc
Multi Touch (TTI) unsure if you guys have any support for this i
googled it and ended up in a ubuntu forum i might be missing something
if anyone could be of assistance i would greatly appreciate it. I do
not know how to compile what i do know is i installed Ubuntu Natty
beta 2 and everything worked out of box so is there a way to port all
the drivers from ubuntu to androidx86.

[Arobase40]

I don't know much about Ubuntu Natty Beta 2 version, but for what I
have noticed in the Natty final version is that the hid-multitouch
module is broken and is not working anymore. At least with my Cando
panel Panel in the Acer 1825ptz...
So it is hid-cando which is loaded as default, and so as single
touchscreen.

I tried to unload hid-cando and load hid-multitouch instead, but the
touchscreen is not recognosized anymore and won't work at all.

Stephane Chatty, from the Enac is unreachable at the moment, so we
won't get support from him for about a week or by about 10 days.

But for what I know, or we use have to use an older kernel than 2.6.38
or we have to go directly to 2.6.39.

[Silverio Cortez]

any way i can download multiple kernals with different hid like
multitouch cando and mosart or will i have to learn how to compile to
do so.

[Arobase40]

To compile and create the Asus_laptop target should not be so
difficult as there are many tutorials on Android-x86 web site or on
other places such as Samiux's Blog, and as the target has already been
created.

The "hardest" task will be to create your linux (Ubuntu) environment
for building and to download the source code.

What you'll need also to do is to downgrade the kernel to 2.6.35 or
upgrade it to 2.6.39 (RC versions though)... ^^

You may need to watch at the older posts as I can't remember the git
commands to do so... :-)

I'm kind of a "rebel" guy about repo or git commands. lol ;-)

[Silverio Cortez]

uhm ill see if i can, if i cant i will just have to wait till
bluestacks comes out or hopefully ice cream sandwich can work,

Just a though could transformer source code be compiled to work on a
touch eee pad.
If yes then it might motivate me into booting into ubuntu and start
learning.

[Arobase40]

Transformer source code is ARM (Tegra 2) kernel source code... ^^

But may be you could have a watch at the hid drivers section.

Should be common to any architecture... Hopefully...

[albert_ap]

I have the same problem as ET, and installed almost all versions and
does not work the touchscreen and wifi works occasionally. If anyone
has another version or know where to find it please tell me where.
Thanks.

[Silverio Cortez]

well im going to wait for Bluestacks alpha testing started i already
signed up, viewpad pro 10 has bluestacks already installed and some
videos and it seems very fluid.