Generic tablet's touchscreen not working on any version or build

[stewartie4]

Hi I bought my generic tablet here:
http://www.dhgate.com/new-arrival-9-7-inch-thin-tablet-pc-capacitive/p-ff8080812f006b56012f028c374d70aa.html
which came with windows 7 and android x86
it has 2gb of RAM, bluetooth and a 1.66ghz intel atom n455 processor
with a capacitive touchscreen. this tablet came with android x86 froyo
and the touchscreen and g sensor worked great, after that i decided to
upgrade to ice cream sandwich and stupidly formatted the android
partition. now i have no way of knowing which build was compatible
with my tablet.
since then I have downloaded every build of ice cream sandwich and
froyo and tried them, in all of them the touchscreen still doesn't
work
what should I do?
I can provide any logs and details needed
thanks for the hard work, help and patience.

[Stefan]

Hello,

as you also have a running Windows 7 on your tablet, the best first step
would be to find out what kind of touch-screen hardware your tablet has.
This can be done that way:

Start Windows and login
Press Start
Select System control panel
Open the system icon (you also can use the Windows+Pause key on a
hardware keyboard to open this.)
Open the device manager
Open the HID tree (human interface device)
Select the touch screen device
Note it's device name into your answer to this group
Double click it to open it
Go to the Details tab
From the list, select "hardware IDs"
Copy the shown value into your answer to this group

You also should be able to find these informations under /dev in an
Linux/Android environement.

Then, somebody might have a look if there are Linux / Android drivers
available and he might integrate them into the device tree (maybe the
Tegav2 would be the best to fit?)

Stefan

[stewartie4]

Thanks for the reply
I followed your instructions but the device manager just lists the
generic name "hid-compliant device"
The device ids are:
HID\VID_03EB&PID_201C&REV_45:1
HID\VID_03EB&PID_201C
HID_DEVICE_UP:000D_U:0004
HID_DEVICE
Though I doubt these will do you much good.
Thanks

> >http://www.dhgate.com/new-arrival-9-7-inch-thin-tablet-pc-capacitive/...

> > which came with windows 7 and android x86
> > it has 2gb of RAM, bluetooth and a 1.66ghz intel atom n455 processor
> > with a capacitive touchscreen. this tablet came with android x86 froyo
> > and the touchscreen and g sensor worked great, after that i decided to
> > upgrade to ice cream sandwich and stupidly formatted the android
> > partition. now i have no way of knowing which build was compatible
> > with my tablet.
> > since then I have downloaded every build of ice cream sandwich and
> > froyo and tried them, in all of them the touchscreen still doesn't
> > work
> > what should I do?
> > I can provide any logs and details needed

> > thanks for the hard work, help and patience.- Hide quoted text -
>
> - Show quoted text -

[Stefan]

Hello,

unfortunately this hardware ID does not tell much, except of that the
touch screen device is controlled by an Amtel AT90USB162 microprocessor,
which communicates via USB with the motherboard.

In Windows, did you had to install special drivers to support that
touchscreen, or was it autodetected from Windows with no need of special
drivers? If you have Windows drivers, could you send me them for
analyzing off-list? Maybe I can find out the manufacturer by that way,
and then somebody else might know where to find the driver.

Stefan

Am 06.04.2012 16:00, schrieb stewartie4:
> Hi I did what you said thanks for the reply. The touchscreen doesn't
> have a name as such just a generic "hid-compliant device"
> The hardware ids are:

> HID\VID_03EB&PID_201C&REV_45:1
> HID\VID_03EB&PID_201C
> HID_DEVICE_UP:000D_U:0004
> HID_DEVICE

> Although I can't say they'll make much sense!thanks

>
>
> On Apr 5, 9:16 pm, Stefan<matthaeus.ste...@googlemail.com> wrote:

>>> http://www.dhgate.com/new-arrival-9-7-inch-thin-tablet-pc-capacitive/...

[stewartie4]

Hello, thanks for the reply,

No there were no special drivers installed, windows simply knew it was a touchscreen.

I also installed a clean version of windows8 consumer preview and again, it was automatically detected.

So I assume the answer lies with the default windows windows drivers?

The tablet came with a program that controls brightness auto rotation etc. Would uploading that help?

Thanks

[stewartie4]

[uMP2k]

hi,

I have the same tablet and suffered the same fate as you. loaded a
different x86 install and lost my touchscreen. i also posted on this
and managed to get a bit of info.

Windows device manager tells me that it is a usb touchsceen with a
hardware id as follows: USB\VID_03EB&PID_201C&REV_45:1
USB\VID_03EB&PID_201C

i did get a response from somebody with the original install on his
tablet. his info was that the Android 2.2 originally on our tablet
used 2.6.35.7 kernel and loads a driver module named hid_cdt_mt.ko. i
have a copy of this and some other files if it might help.

[Alteran]

It has come out from the horses mouth and all the followers, you can only get a good copy of ICS working with a custom build or a very very pop tablet. if you have a off brand it simple will not be supported and don't look forward for it to be. Android maybe on multi systems now, but it has fallen in to the apple trap. If you a normal everyday person who don't know how to edit a iso, you are SOL. Since the 2.3 to the New 4.0 and on going they are not going to make a open range android. So for all the people looking, if your tablet or computer is very pop then you maybe in luck, if you computer is not, you will either build your own iso or you SOL.

 

If you own a jumper jk0-tt I have a full custom ISO. Stipped down only for this tablet. Atom N455, no other support, rt2860 wifi driver only.

 

I was open to the x86 build till I found  out how close minded the people behind the build was. It was based off of linux, but it is not linux. After many debates of why they can't support multi drivers in builds it will never happen. So never expect a install to just work all the way around, this won't happen. So if you want x86 buy a very pop tablet.

 

As of for me, I will stick with the ARM for android. Atleast microsoft's new windows8 supports all x86 and 95% of ARM devices.

[stewartie4]

Thanks for the reply,

Yes, that seems to be the exact same tablet I have! Tanks very much, the files would be much appreciated! Then maybe I can find out how to build a ics build with those drivers.

Thanks!

[stewartie4]

Of course I know how to edit an iso I just don't know what files to edit/replace lol

[Stefan]

Hello,

my opinion is that you think too simple. You think, you have your device
working, so you are happy and don't care on others. This is not my
opinion, even if I can be quite happy with my WeTab and Corvus's work.

In the message just below of yours, from tabletx86, there are a few
links which look quite promising. Why not just integrate these things
into the tegav2 device tree and see what happens?

Stefan

> --
> You received this message because you are subscribed to the Google
> Groups "Android-x86" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/android-x86/-/257TQp_Ce0AJ.
> 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.

[stewartie4]

Yeah, I'm not paying double for the same specs just because It's branded.... it I wanted to do something like that i'd buy a mac....

I was thinking about ARM but Microsoft have said conclusively you will not be able to run x86 exes on ARM meaning every single program on windows now will be incompatible

On Sunday, April 8, 2012 6:32:40 PM UTC+1, Alteran wrote:

[uMP2k]

I have sent you an email with the files and some other info that I have been able to discover.  Hope it helps...

[stewartie4]

hello I have received nothing as of yet try sending to ryanste...@live.co.uk thanks

On Sunday, April 8, 2012 3:31:01 PM UTC+1, uMP2k wrote:

[uMP2k]

Email re-sent. Let me know if it gets to you. Hope info and files help.

[stewartie4]

got it thanks. did you ever get it fixed?

[uMP2k]

Nope! All got too complicated for me. Would love Ro see it working though.

My main hope is that once Windows 8 comes out it will be a perfect fit on this tablet.

[Nihilist]

You probably all know this but I'm just going to throw it out there.
Try the eeepc build.

Load with debug, when the prompt appears type modprobe multi-touch.
See if it loads your screen. type exit. and then type exit again..

[stewartie4]

i'm actually running windows 8 now its fantastic, would never go back to 7. Still a bit rough around the edges though. I'm going to try and see if I can work this out and i'll get back to you.

Thanks for the help

[stewartie4]

thanks i'll try that and post the results here

[Ooop Yooo]

2012/4/8 Stefan <matthaeu...@googlemail.com>

Hello,

my opinion is that you think too simple. You think, you have your device working, so you are happy and don't care on others. This is not my opinion, even if I can be quite happy with my WeTab and Corvus's work.

I share most Alteran's opinions. It's not a matter of his being happy and don't care on others as I had to explain him how to build a custom Tegav2 iso with a wireless driver compatible with his chipset, after his was waiting some weeks for someone to do this little change.

Unfortunatly most users aren't able to setup a dev environment and compile their own build... ^^

 

In the message just below of yours, from tabletx86, there are a few links which look quite promising. Why not just integrate these things into the tegav2 device tree and see what happens?

Yes, why not ??? ^^ lol

But why the Tegav2 target (or any other targets) holder or the "official" Android-x86 devs don't do the changes such as adding some more wireless, ethernet, touchscreen drivers, etc... ???

 

If they don't do these changes, who will then ??? ^^

Ooop

Stefan

Am 08.04.2012 19:32, schrieb Alteran:

It has come out from the horses mouth and all the followers, you can only get a good copy of ICS working with a custom build or a very very pop tablet. if you have a off brand it simple will not be supported and don't look forward for it to be. Android maybe on multi systems now, but it has fallen in to the apple trap. If you a normal everyday person who don't know how to edit a iso, you are SOL. Since the 2.3 to the New 4.0 and on going they are not going to make a open range android. So for all the people looking, if your tablet or computer is very pop then you maybe in luck, if you computer is not, you will either build your own iso or you SOL.
If you own a jumper jk0-tt I have a full custom ISO. Stipped down only for this tablet. Atom N455, no other support, rt2860 wifi driver only.
I was open to the x86 build till I found  out how close minded the people behind the build was. It was based off of linux, but it is not linux. After many debates of why they can't support multi drivers in builds it will never happen. So never expect a install to just work all the way around, this won't happen. So if you want x86 buy a very pop tablet.
As of for me, I will stick with the ARM for android. Atleast microsoft's new windows8 supports all x86 and 95% of ARM devices.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To view this discussion on the web visit https://groups.google.com/d/msg/android-x86/-/257TQp_Ce0AJ.
To post to this group, send email to andro...@googlegroups.com.

To unsubscribe from this group, send email to android-x86+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

--
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+unsubscribe@googlegroups.com.

[Chih-Wei Huang]

2012/4/15 Ooop Yooo <ooop...@gmail.com>:

> Yes, why not ??? ^^ lol
>
> But why the Tegav2 target (or any other targets) holder or the "official"
> Android-x86 devs don't do the changes such as adding some more wireless,
> ethernet, touchscreen drivers, etc... ???

Have you told us which driver you need?

[Ooop Yooo]

Oh me bad, I missed your question....

2012/4/17 Chih-Wei Huang <cwh...@android-x86.org>

Me personnaly ? No, as I don't need any... BUT at least Alteran asked for wireless RT 2860 since march 26th as far as I can remember, but many others asked also for other wireless support, but you may be too busy to read them all...

I helped Alteran to solve his problem, but all the others users are not capable to compile their own build.

But the most common requests is Ethernet support but there are too many to name them all. 

So maybe you could add an "official" Ethernet support with a best quality build than what Tabletx86 can supply ???

Someone else asked also for ts calibrate as his touchscreen seems to need one.

Should I have to assume a spokesperson position in between the end-users and you ?

I don't mind to collect their requests, find the correct drivers name (this will save you some of your precious time) with the concerned builds and raise these requests to you if you do care...

What do you think ?

--
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.

[Chih-Wei Huang]

2012/4/24 Ooop Yooo <ooop...@gmail.com>:

> Oh me bad, I missed your question....
> 2012/4/17 Chih-Wei Huang <cwh...@android-x86.org>
>>
>> 2012/4/15 Ooop Yooo <ooop...@gmail.com>:
>> > Yes, why not ??? ^^ lol
>> >
>> > But why the Tegav2 target (or any other targets) holder or the
>> > "official"
>> > Android-x86 devs don't do the changes such as adding some more wireless,
>> > ethernet, touchscreen drivers, etc... ???
>>
>> Have you told us which driver you need
>

> Me personnaly ? No, as I don't need any... BUT at least Alteran asked for
> wireless RT 2860 since march 26th as far as I can remember, but many others
> asked also for other wireless support, but you may be too busy to read them
> all...

Indeed it is. I still have over 40 pending unread mails.

For 2860, I assume you talked about tegav2.
Actually I have added it to my tree, but
forgot to push it. Will do soon.

> I helped Alteran to solve his problem, but all the others users are not
> capable to compile their own build.
>
> But the most common requests is Ethernet support but there are too many to
> name them all.
>
> So maybe you could add an "official" Ethernet support with a best quality
> build than what Tabletx86 can supply ???

This has been explained.

> Someone else asked also for ts calibrate as his touchscreen seems to need
> one.

I've also explained how to enable tslib for a target.

> Should I have to assume a spokesperson position in between the end-users and
> you ?
>
> I don't mind to collect their requests, find the correct drivers name (this
> will save you some of your precious time) with the concerned builds and
> raise these requests to you if you do care...
> What do you think ?

Thank you.

The best approach is you can provide patches
so they can be merged directly.
The second best practice is tell me (us)
which target needs what drivers.
But that needs more time and efforts to handle.

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

[Ooop Yooo]

2012/4/24 Chih-Wei Huang <cwh...@android-x86.org>

2012/4/24 Ooop Yooo <ooop...@gmail.com>:

> Oh me bad, I missed your question....
> 2012/4/17 Chih-Wei Huang <cwh...@android-x86.org>
>>
>> 2012/4/15 Ooop Yooo <ooop...@gmail.com>:
>> > Yes, why not ??? ^^ lol
>> >
>> > But why the Tegav2 target (or any other targets) holder or the
>> > "official"
>> > Android-x86 devs don't do the changes such as adding some more wireless,
>> > ethernet, touchscreen drivers, etc... ???
>>
>> Have you told us which driver you need
>

> Me personnaly ? No, as I don't need any... BUT at least Alteran asked for
> wireless RT 2860 since march 26th as far as I can remember, but many others
> asked also for other wireless support, but you may be too busy to read them
> all...

Indeed it is. I still have over 40 pending unread mails.

For 2860, I assume you talked about tegav2.
Actually I have added it to my tree, but
forgot to push it. Will do soon.

I guess you missunderstood what I was talking about : nonetheless, if one change takes so long time, what about more changes... ^^ 

I was mainly talking about the binaries builds with more wireless cards support and such other stuffs with all official builds : Tegav2, EeePC, Asus_laptop, AMD Brazos, etc...

> I helped Alteran to solve his problem, but all the others users are not
> capable to compile their own build.
>
> But the most common requests is Ethernet support but there are too many to
> name them all.
>
> So maybe you could add an "official" Ethernet support with a best quality
> build than what Tabletx86 can supply ???

This has been explained.

I probably missed this part ???

What's wrong with Ethernet patch when it's working with all users capable to apply this patch and compile their own builds ???

 

> Someone else asked also for ts calibrate as his touchscreen seems to need
> one.

I've also explained how to enable tslib for a target.

Yeah, this was only usefull for those being able to compile their builds, not to the end-users...

Sounds like, you always forget them and think all users can compile a build, am I wrong ?

 

> Should I have to assume a spokesperson position in between the end-users and
> you ?
>
> I don't mind to collect their requests, find the correct drivers name (this
> will save you some of your precious time) with the concerned builds and
> raise these requests to you if you do care...
> What do you think ?

Thank you.

The best approach is you can provide patches

Which patches ??? Most of the requests are just a matter of adding already existing drivers, so very minor changes in the defconfig files...

 

so they can be merged directly.

N/A

 

The second best practice is tell me (us)

Who tells who ???

When users post a request or a question on this forum, ain't they telling you the "official" devs or yourself ? ;-)

 

which target needs what drivers.

Ditto

 

But that needs more time and efforts to handle.

Can't you delegate this task to someone that have more spare time than you ?

As if everyone is waiting after your spare time this can take some months before any changes come... ^^

 

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

[Chih-Wei Huang]

I'm happy to delegate tasks to others.
But who would like to take it? Will you?

Well, you said you'd like to collect their requests, find the correct
drivers name
with the concerned builds and raise these requests to me.
Are you serious or just kidding?

If you are serious, I'm happy to delegate the task to you.
Please provide me patches on end-users requests.
Thanks a lot!

2012/4/25 Ooop Yooo <ooop...@gmail.com>:

[Ooop Yooo]

2012/4/25 Chih-Wei Huang <cwh...@android-x86.org>

I'm happy to delegate tasks to others.
But who would like to take it? Will you?

Since this is limited to change the x_defconfig, x_info files and such in targets sources, why not ?

 

The Ethernet patch is another story, as I don't know what is the problem with it... I still don't have any answer from you.

For the rest, I'm not willing to change anything else in the system, as this will endeed need too much time and more expertise...

 

You do have more skill than me for high level changes and I don't want you get unemployed from your own project. lol

Well, you said you'd like to collect their requests, find the correct
drivers name
with the concerned builds and raise these requests to me.
Are you serious or just kidding?

I am quite serious !

 

If you are serious, I'm happy to delegate the task to you.
Please provide me patches on end-users requests.

Yeah, I already deleted most of them from my mail box as I though they would never be treated, but I could do a research from the web version of the google android-x86 group. So you see how serious I am.

To whom should I send these (directly to you ?) and what will be the delay for the changes to be applied and the binaries be delivered ? 

If that could be done in a short term, everyone will be happy : the end-users and yourself as this project is your baby... ^^ ;-)

If this takes months, no need to go any further...

Thanks a lot!

You're welcome.

 

2012/4/25 Ooop Yooo <ooop...@gmail.com>:

[Chih-Wei Huang]

2012/4/25 Ooop Yooo <ooop...@gmail.com>:

> 2012/4/25 Chih-Wei Huang <cwh...@android-x86.org>
>>
>> I'm happy to delegate tasks to others.
>> But who would like to take it? Will you?
>
> Since this is limited to change the x_defconfig, x_info files and such in
> targets sources, why not ?
>
> The Ethernet patch is another story, as I don't know what is the problem
> with it... I still don't have any answer from you.

This is a design decision, as explained several times.
The current patch touches framework too much.
That's ugly and hard to maintain.
As I've pointed out, we want a hal solution.

> For the rest, I'm not willing to change anything else in the system, as this
> will endeed need too much time and more expertise...
>
> You do have more skill than me for high level changes and I don't want you
> get unemployed from your own project. lol
>
>> Well, you said you'd like to collect their requests, find the correct
>> drivers name
>> with the concerned builds and raise these requests to me.
>> Are you serious or just kidding?
>
>
> I am quite serious !
>
>> If you are serious, I'm happy to delegate the task to you.
>> Please provide me patches on end-users requests.
>
> Yeah, I already deleted most of them from my mail box as I though they would
> never be treated, but I could do a research from the web version of the
> google android-x86 group. So you see how serious I am.
>
> To whom should I send these (directly to you ?) and what will be the delay
> for the changes to be applied and the binaries be delivered ?

Send patches to the list for review.

> If that could be done in a short term, everyone will be happy : the
> end-users and yourself as this project is your baby... ^^ ;-)

That depends.

If you show you are good at the task by providing
high quality patches, I can even give you developer
account so you can push patches directly.

[Gernot Hillier]

Hi there!

If I might misuse this thread for a technical question... ;-)

On 2012-04-24, Chih-Wei Huang wrote:
> 2012/4/24 Ooop Yooo<ooop...@gmail.com>:

>> 2012/4/17 Chih-Wei Huang<cwh...@android-x86.org>
>>>
>>> 2012/4/15 Ooop Yooo<ooop...@gmail.com>:

>> Someone else asked also for ts calibrate as his touchscreen seems to need
>> one.
>
> I've also explained how to enable tslib for a target.

I guess this refers to
http://groups.google.com/group/android-x86/browse_thread/thread/48cac33f841c8f4c
("Touchscreen calibration for ics-x86"), right?

So I did was described there, added a small workaround in tslib so that
ts_calibrate also accepted BTN_MOUSE/BTN_LEFT (will send a patch later
if things work) and ran ts_calibrate from the serial console after
Android was up.

After touching crosshairs, it gave me a number of calibration values
which I first tried to write to /system/etc/pointercal with seemingly no
effect and then to /data/system/tslib/pointercal.

The latter, however, made my touchscreen completely ignore any input - I
can't even see the circle visualizing the touchpoint anywhere. Probably
my values are bad?

uid=0 gid=1007@machine:/ # cat /data/system/tslib/pointercal

12653 178 343852 45 7156 1692836 65536 800 480 480

When doing that, I also had severe difficulties using ts_calibrate -
most of the time, probably due to high jitter and a detected drag event,
Android redraws the screen so that I can't see the ts_calibrate
crosshairs any more. Probably I got wrong values therefore?

Now, before starting digging through the code in the Android base
framework, I wanted to ask whether the described procedure was correct
and/or if you have some suggestions how to understand what's going on
w/o debugging the Android core.

Btw, what's the intended effect of "BOARD_USES_TSLIB=true" in the initrd
script?

--
Gernot Hillier
Siemens AG, Corporate Technology, CT T, Program "Open Source Platforms"

[Gernot Hillier]

Hi!

On 2012-04-27, Gernot Hillier wrote:
> http://groups.google.com/group/android-x86/browse_thread/thread/48cac33f841c8f4c
> ("Touchscreen calibration for ics-x86"), right?

[...]

>
> The latter, however, made my touchscreen completely ignore any input - I
> can't even see the circle visualizing the touchpoint anywhere. Probably
> my values are bad?

[...]

>
> Btw, what's the intended effect of "BOARD_USES_TSLIB=true" in the initrd
> script?

Ok, forget my request. My last question was the key to my problem. My
device init script was defective and didn't set this variable. So
/scripts/3-tslib didn't kick in.

After fixing that, the calibration screen showed up automatically upon
reboot and calibration data was automatically stored and applied. Thanks
to all who made tslib calibration work for ics-x86!

--
With kind regards,

Gernot Hillier
Siemens AG, CT T, Program "Open Source Platforms"

[Jon Izarzugaza]

Hi! I'm new here, just joined to see if I have a bit of luck. I own a EEEPC T91, which has a touch fippable screen that can basically be used as a tablet (you can fold the screen looking upwards, to make it a bulky tablet).
The touchscreen device ID is HID\VIC_1CB6&PID_6680. After googling a bit, it seems to be a "IdeaCom HID Touch Screen" . When I boot ICS, I get to the touchscreen calibration. And I can get to calibrate it, as it takes the touch events. But once I'm on ICS, it won't properly recognize the touches. However I noticed this: If I move the mouse using the touchpad, if I then use the touchscreen, the mouse fades away to hide. It RECOGNIZES there was a touch, but the interface won't react. No icon can be touched, no homescreen can be moved...nothing.

I don't know if you guys could help me or give me directions, but I would greatly appreciate it!

Cheers,
Jon

[Chih-Wei Huang]

T91 support has been added to the source tree
(thanks to Edward Peek's patches)

You may build it from source, or
wait next release.

2012/5/6 Jon Izarzugaza <tim...@gmail.com>:

[Jon Izarzugaza]

This is great! Thank you so much indeed! I'm not sure if i can compile it myself, I'll give it a shot. When do you think the next version might be released?

[Jon Izarzugaza]

Thank you very much! I'm downloading the "android-x86-4.0-eth0-eeepc-20120426.iso", is it this one?
I've been encountering several problems to enter tabletsx86.org, both Chrome and Firefox seem to have problems to reach the page with "too many redirections". Reconq finally loaded the page effortlessly. I'll try also the Asus and generic isos if this one doesn't load. Thank you!

On Mon, May 7, 2012 at 12:02 PM, tabletsx86 <rbg.tab...@gmail.com> wrote:

that was added Apr 6

    http://git.android-x86.org/?p=device/asus.git;a=commit;h=f266de37d4b0e3b6f5262b557f8b7d2a8d2f42d0

there is a build here, based on Apr. 24 repo that you could try while
waiting...

   http://tabletsx86.org/x86-UPDATED-BUILDS.htm

On May 6, 11:30 pm, Jon Izarzugaza <timo...@gmail.com> wrote:
> This is great! Thank you so much indeed! I'm not sure if i can compile it
> myself, I'll give it a shot. When do you think the next version might be
> released?

> On May 6, 2012 10:44 PM, "Chih-Wei Huang" <cwhu...@android-x86.org> wrote:
>
>
>
>
>
>
>
> > T91 support has been added to the source tree
> > (thanks to Edward Peek's patches)
>
> > You may build it from source, or
> > wait next release.
>

> > 2012/5/6 Jon Izarzugaza <timo...@gmail.com>:

[Jon Izarzugaza]

Great!! Eeepc works like a charm! Well, since it's a resistive touch screen, I actually have to press hard to make a swipe (otherwise it will take it as a random click somewhere), but it's still very cool. Thank you!

Now I'll have to figure out the way to increase the resolution to the native 1024x600, as it seems to be working at 800x600. I'll try to check if there's some documentation on that :)