gingerbread-x86 on Pegatron Lucid tablets (WeTab, ExoPC)

[Nicolas]

Hello,

first of all, I am posting from Google Groups, so apologies for any
misformatting. Also, great work.

Gingerbread is working fine so far on the Pegatron Lucid tablet;
specifically, I am using a WeTab. After creating a new device with the
defconfig scrambled together from tegav2, viewpad10 and the original
WeTab kernel config, I am now left with a correctly booting Android
2.3.

Issues (mostly things I do not understand):

a) Multitouch (hid-multitouch) is working, but not really. Clicks are
impossible, it seems the curser is in drag mode all the time. The
module is loaded from _info via EXTMOD. The eGestured service should
be loaded on boot, but this does not seem to happen. Manually starting
it does not fix the problem.

b) The resolution seems off as soon as the "android" logo disappears,
it seems to be default 800x600. I set UVESA_MODE in the _info file,
but specified FB0DEV=i915. What is the correct way to specify the
device resolution, and how do you set the graphics adapter module? (Or
ould this be a DPI issue? The correct dpi value for this device is
135, which I set in system.prop.)

c) The device powers off after about 1 minute. It seems to go to stand-
by and just freeze. How can I investigate this?

If anyone could drop me a small hint, I would be very grateful.

Nicolas

[Arobase40]

1) Gingerbread does not have mesa nor drm support (or at least very
limited support as stated by Chih Wei in an older thread).
2) Cursor mode is either not supported as default (make a seach in
google group to get the patches).
3) I recently posted an explanation about Suspend/Resume issue with
includes Power Off and Reboot.

[Nicolas]

Thanks for your reply.

On 27 Apr., 08:24, Arobase40 <arobas...@gmail.com> wrote:
> 1) Gingerbread does not have mesa nor drm support (or at least very
> limited support as stated by Chih Wei in an older thread).

The problem persists also in froyo. It is not even a problem, rather a
question of ignorance: I simply would like to know the /Right Way/ to
setup the graphics adapter.

> 3) I recently posted an explanation about Suspend/Resume issue with
> includes Power Off and Reboot.

Ok, so this is a general issue? (Note that the Viewsonic-provided
froyo image does not suffer from it.)

Nicolas

[Arobase40]

What are the Gfx cards used these tablets ?

Can you tell me which froyo and which kernel version is provided by
Viewsonic ? ^^

Mesa is affected by an auto-detect mechanism bug with lattest version
(FRG83G) with some Intel subsets of gfx card.

About Suspend/Resume, may be Viewsonic found an issue or they just
commented out the XHCI module just as I mentioned in a previous
thread : I guess viewsonic tablets don't have USB3 ports, right ? ;-)

[Arobase40]

I haven't found out the Viewsonic source code for their x86 version,
but just got the patches they used for the ARM version, and they
commented out the XHCI module just as I suggested in my previous
thread ! ^^ ;-)

Here is the link :

http://www.viewsonic.com/gtablet/news.htm

Upper right of the page... :-)

On 27 avr, 11:47, Nicolas <n.tess...@gmail.com> wrote:

[Nicolas]

Ok, of the initial issues, only the graphics one is still relevant.

It seems the hid-multitouch driver cannot work properly with the
eGalax touchscreen, but using the eGestured service solves this issue.

Removing XHCI solved the crashing.

Thank you for the input. Now what to do with this device specs? Is
there a way to submit it?

[Arobase40]

If your don't anwer the question how could I respond to you ??? ^^

[Nicolas]

I am sorry. I did not realize there are two messages.

The graphics are standard N45X, so I think it would be the GMA 3150.

Viewsonic uses a 35-7 kernel, but that is kind of irrelevant, since I
got most of it working for the 38 kernel.

[Arobase40]

So you're out of luck !

You didn't say much about your display with the lastest froyo
version...

Unless Chih Wei pushed a new debugged version I'm not aware of, FRG83G
ID (latest Froyo version) should have mesa issue with this chipset, as
explained above.
So you have to downgrade mesa with the older version.

The howto is here :

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

At first, no need to downgrade the kernel. See if that solve your
problem with graphical issue.

Then downgrade the kernel to 2.6.35 and get my tar ball for the aspire
1000s serie to get the multitouch drivers and test if that solve your
touch panel issue.

But don't forget to backup your whole tree before applying any
change !!!

Tell me how it works after that...

[Nicolas]

The latest Froyo version, checked out today, kernel .38, works fine.
The display works, and so does the Touchsceen by loading both the hid-
multitouch module and the eGestured service (tslib on eGestured).

I will test Gingerbread as soon as possible with my current config.

[Arobase40]

Lucky guy ! ;-)

[Nicolas]

I am still wondering why the hid-multitouch module makes the
touchscreen so "sticky". The button-up event is ignored. Could this be
a configuration issue?

[shadow2000]

May you give me a short instruction which branch and which target config is working best on your exopc?

[Nicolas]

I used the froyo-x86 branch with my custom target, which I will share
in a new post.