hp slate 500 wifi and touch screen support?

[kipperstieva]

i have my slate setup to dual-boot windows 8 DP and android x86. I
started with the Tega 3.2 RC2 because that seems like it's the closest
hardware to slate, processor wise, and it works, but no touch input
and no wifi. I read that the new ICS kernel should support n-trig, so
i installed the 4.0 test build and I get "Unfortunately, Setup Wizard
Has Stopped" after it boots. Am I wasting my time trying to make this
work or are there similar devices out there with similar hardware that
have touchscreen or wifi working running Androidx86?

[Jan Van Winkel]

Hi,

I started of from generic-x86 ICS and disabled the wl module
(CONFIG_WL) as it seems the wifi does not work with this module and it
is the first choose by the automatic module loader. Once you disabled
the module the auto selction will fall back to bcrmmac. Problem is
that you need to have the broadcom firmware installed in /system/lib/
firmware/brcm for this driver. I toke the firmware (/lib/firmware/brcm/
bcm43xx_hdr-0.fw & /lib/firmware/brcm/bcm43xx-0.fw) from my ubuntu
machine and placed it in this directory bcm43xx-0.fw.

Further I had to disable the psb module (GA500 driver) else my
graphics where screwed, I had a diagonal flickering. By disabling this
module you will fallback to uvesafb, problem is that the default
resolution is 800x600 instead of 1024x600 (I'm currently working on
that).

For the touchscreen there is no problem, the ntrig driver gets
automatically loaded and it works out of the box including multitouch.

The next problem that I have is the audio but I hope it is just a
matter of finding the correct module.

Regards,
Jan

[Chih-Wei Huang]

2012/1/7 Jan Van Winkel <vanwin...@gmail.com>:

> I started of from generic-x86 ICS and disabled the wl module
> (CONFIG_WL) as it seems the wifi does not work with this module and it
> is the first choose by the automatic module loader. Once you disabled
> the module the auto selction will fall back to bcrmmac. Problem is
> that you need to have the broadcom firmware installed in /system/lib/
> firmware/brcm for this driver. I toke the firmware (/lib/firmware/brcm/
> bcm43xx_hdr-0.fw & /lib/firmware/brcm/bcm43xx-0.fw) from my ubuntu
> machine and placed it in this directory bcm43xx-0.fw.

Interesting finding.
Do you mean the bcrmmac driver works for you?
What's your broadcom chip?

> Further I had to disable the psb module (GA500 driver) else my
> graphics where screwed, I had a diagonal flickering. By disabling this
> module you will fallback to uvesafb, problem is that the default
> resolution is 800x600 instead of 1024x600 (I'm currently working on
> that).

There is no solution yet.
One possible hope is the gma500_gfx driver
in linux-next branch.
But it's still buggy to display android gui
as last time I tried.

[Jan Van Winkel]

@Chih-Wei Huang

First a small correction the driver that I got working, by accident,
is the bcmsmac and this for the 4313 bcm chip set.
I was expecting to see it working with the b43 driver and tried
multiple kernel builds with no success but this could be due to the
fact that that wl module was still there.

But the real root cause is that the wl kernel module does not play
nicely with ICS wpa_supplicat and I was just lucky that the bcmsmac
( + wpa_supplicat) worked out of the box after copying the firmware
from ubuntu 11.10.
See post:
http://groups.google.com/group/android-x86/browse_thread/thread/55487ab6325cf1cd/475ded615b837d5f

Concerning the graphics I don't mind uvesafb and manged the set the
correct resolution (1024x600) through UVESA_MODE.
But this brings me to the point that I have a question, how do you
patch a more resent kernel with the android stuff as I would give the
module a try my self?
Is there a patch set available?
Apologies if it was already posted but I could not find it and I
bumped into a post where you mentioned that you tried 3.2-rc4 so I was
wondering how (feel free to make a new post out of this).

@kipperstieva

Maybe the ntrig touchescreen kernel module got not automatically
loaded but was loaded in my cases as I started to add a device target
for the slate and in the slate_info file I added hid-ntrig to EXTMOD.


On Jan 8, 10:29 am, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> 2012/1/7 Jan Van Winkel <vanwinkel...@gmail.com>:

[Chih-Wei Huang]

2012/1/9 Jan Van Winkel <vanwin...@gmail.com>:

> Concerning the graphics I don't mind uvesafb and  manged the set the
> correct resolution (1024x600)  through UVESA_MODE.
> But this brings me to the point that I have a question, how do you
> patch a more resent kernel with the android stuff as I would give the
> module a try my self?
> Is there a patch set available?

All patches are in the git repository.
You may try to merge it with a newer kernel branch.

But I usually start from what others have done.
In this case I use the Linaro kernel, which
is based on 3.2-rc6 at this moment.
git://android.git.linaro.org/kernel/linaro-android
Then I merge the linux-next branch which
contains gma500_gfx driver from Alan Cox.
This is the simple way to get a more recent
kernel with drivers you want. Remember
git is very powerful, once you get familiar with it.

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

[Stefan Matthäus]

Hello,

there is a little group of peoples running the Tegav2 images of AndroidX86 on their WeTabs and ExoPCs. They have made some changes to the Tegav2 image to get more compatible to that tablet PC. I give you my experiences with it and the links to the modifications.

The target  of this email is to sensiblize you on the needs of the users of WeTab/ExoPC and other Pegatron Lucid based Atom Tablet PCs, so that in the future the Tegav2 images could also run on these without any changes.

Mostly these peoples at the wetab-community.com forum are using a modified 3.2.2 image based on the Tegav2 image on androidx86.org. They also tryed the 4.0x version but found that it is still too unstable to use it, most testers report that at least 10 minutes it hangs up. The 3.2.2 image is much more stable, I could use it more than 3 hours per session before it hangs up.

First I report you the modifications which have been done to the Android X86 3.2 Tegav2 image to support the Pegatron Lucid platform:

1. Currently the mod is based on: http://android-x86.googlecode.com/files/android-x86-3.2-RC2-tegav2.iso

2. Changes:
2a: WLAN sometimes does not get a DHCP adress after connect, this solves it:
  
chmod 777 /system/etc/dhcpd/*

2b: The touchscreen is detected as a mouse, the follwoing changes this:

cd /system/usr/idc
cp Vendor_03eb_Product_201c.idc Vendor_0eef_Product_72a1.idc

2c: The screen light can only be adjusted after after replacing a file:

cd /system/lib/hw
rm lights.tegav2.so
wget http://www.steckbecken.at/wp-content/uploads/lights.tegav2.so

Note that this change is not compatible to the original Tegav2 platform, so maybe there must be some modifications to this file to be able to support both Tegav2 and Lucid with one file. Would this be possible?

2d: To be able to use a real SD card beside a fake-SD:

cd /system/etc
mv vold.fstab vold.fstab.bak

2e: To make GPS useable on the Lucid platfrom with the GPS/3G-module:

cd /system/lib/hw
rm gps.tegav2.so
wget http://www.steckbecken.at/wp-content/uploads/gps.tegav2.so

Alos this one should not be compatible to the original Tegav2 platform, so maybe a solution could be found to support both with one file?

2f: The webcam can be made useable when replacing two other files:

cd /system/lib
rm libcamera.so
rm libcameraservice.so
wget http://www.steckbecken.at/wp-content/uploads/libcamera.so
wget http://www.steckbecken.at/wp-content/uploads/libcameraservice.so

Also these files should not be compatible to the original Tegav2 platform anymore. Maybe it is possible to change also this in a way that it can suppot both plattforms, Lucid and Tegav2?

2g: The following mod makes the following functions functional, but it still has two negative issues. The negative issues are that the screen light gets a bit darker and on some users WeTab it influences the CPU fan negative, it might not run anymore what is fatal as the tablet is no more cooled. They currently think that this mod is checking the hardware management controller too often, so that it might get overloaded and hangs up. On my own WeTab the fan control still works with this change.

The following files are required, as for the issues in the forum they are marked as experimental:

- http://www.wetab-community.com/index.php?app=core&module=attach&section=attach&attach_id=6072 ( asus-laptop.ko.gz )
- http://www.wetab-community.com/index.php?app=core&module=attach&section=attach&attach_id=6073 ( sensors.tegav2.so.gz )

Then run these commands:

cp asus-laptop.ko /system/lib/modules/3.0.1-android-x86-tegav2+/kernel/drivers/platform/x86
cp sensors.tegav2.so /system/lib/hw

boot with DEBUG=1
exit
depmod -a
exit

2f: The internal 3G modem still does not work well, it is detected, but it seems to hang up after detecting the available networks. The problem has not been solved yet. Further details can be found here: http://www.wetab-community.com/index.php?/topic/17917-android-322-komplett-rc2-image/page__st__320__p__247284#entry247284 and following messages (in german).

From Windows Devicemanager, Huawei Mobile Connect 3G Modem:
- USB/VID_12D1&PID_1404&REV_0000&MI_00

2g: For the Atheros Bluetooth module no driver yet.
From Windows Devicemanager:
- USB\VID_13D3&PID_3304&REV_0001

2h: This summary is based on the following german threads in the WeTab community forum:
I. http://www.wetab-community.com/index.php?/topic/17948-zusammenfassung-der-zwei-android-threads/ (list of changes)
II. http://www.wetab-community.com/index.php?/topic/17917-android-322-komplett-rc2-image/page__st__220__p__245469#entry245469 (322 rc2 image discussion)

3. A fully modified image runable on the Lucid/WeTab/ExoPC/... can be downloaded from message No. 1 of this thread, it is always updated with the newest changes:

http://www.wetab-community.com/index.php?/topic/17917-android-322-komplett-rc2-image/

The instruction of this messaqe in the forum shows how to boot this image out of a Windows 7 / 8 partition using NeoGrub and BCDEdit. This is very interesting for those who own an ExoPC which comes by default with Windows 7. Or for those who have deleted WeTabOS and replaced by Win 7.

I hope that one of the Android X86 group will have a close look in this message and helps to improve the developement of Android X86 to support more platforms. If you have any questions or you need help, just contact me or the user Halver of the wetab-community forum as the responsible for the most of the changes at the 3.2.RC2 image.

Thank you all,

Stefan

[stefan]

Hello,

this email is specially for the maintainer of the Tegav2 tree.

There is a little group of peoples running the Tegav2 images of

AndroidX86 on their WeTabs and ExoPCs. They have made some changes to
the Tegav2 image to get more compatible to that tablet PC. I give you
my experiences with it and the links to the modifications.

The target of this email is to sensiblize you on the needs of the
users of WeTab/ExoPC and other Pegatron Lucid based Atom Tablet PCs,
so that in the future the Tegav2 images could also run on these

without any changes and with full hardware support.

2h: The Android kernal is compiled without himem option, so even if
the tablet PC has 2 GB of memory, it can only use 1 GB.

2i: There is no support in the Tegav2 build for the Broadcom video
accelerator which is built into the WeTab 3G. Broadcom Crystal HD
Video Decoder, PCI\VEN_14E4Tegav2 image on WeTab/ExoPC and other
Pegatron Lucid tablets1615&SUBSYS_161514E&REV_00

2j: Also no support for the Chronotel Videoswitch of the WeTab/ExoPC
to enable HDMI-out to mirror the internal display to an external one.

2k: This summary is based on the following german threads in the WeTab

community forum:
I. http://www.wetab-community.com/index.php?/topic/17948-zusammenfassung-der-zwei-android-threads/
(list of changes)
II. http://www.wetab-community.com/index.php?/topic/17917-android-322-komplett-rc2-image/page__st__220__p__245469#entry245469
(322 rc2 image discussion)

III. Own experiences and researches.

3. A fully modified image runable on the Lucid/WeTab/ExoPC/... can be
downloaded from message No. 1 of this thread, it is always updated
with the newest changes:

http://www.wetab-community.com/index.php?/topic/17917-android-322-komplett-rc2-image/

The instruction of this messaqe in the forum shows how to boot this
image out of a Windows 7 / 8 partition using NeoGrub and BCDEdit. This
is very interesting for those who own an ExoPC which comes by default
with Windows 7. Or for those who have deleted WeTabOS and replaced by
Win 7.

I hope that one of the Android X86 group will have a close look in
this message and helps to improve the developement of Android X86 to
support more platforms. If you have any questions or you need help,
just contact me or the user Halver of the wetab-community forum as the
responsible for the most of the changes at the 3.2.RC2 image.

Thank you for providing the Tegav2 image and hope that it will support
the Lucid platform soon fully,

Stefan

Ps: If this message appears several times, then sorry, I might have
problems with Thunderbird and the Google account. Still checking
that...

[Jan Van Winkel]

For those that are interested you can find a preliminary device target
for the hp slate at the following link:
https://docs.google.com/open?id=0Bxw1kTqfiG57NmM4M2I0YTMtODk5NS00OTJlLTgxMDEtN2U5ZWI4ZDc2ZjIy

Note that the broadcom firmware (bcm43xx-0.fw bcm43xx_hdr-0.fw) is
missing.
So you will need to find a copy of the firmware and place it in the
directory device/hp/slate/fw/brcm .

Once everything is in place you can set TARGET_PRODUCT=hp_slate to
make a build.

On Jan 9, 5:09 am, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> 2012/1/9 Jan Van Winkel <vanwinkel...@gmail.com>:

[kipperstieva]

Hi Jan -

I think my problem is that I can't get any of the generic-x86 ICS
builds to install so I've been installed targeted builds for other
devices that do not have the correct settings/firmware/drivers. I'm a
windows dev, so this stuff is new to me, but I just installed GIT Bash
on my windows 7 box and pulled down the bcm firmware files.

Also, how do I "disabled the wl module (CONFIG_WL)" and the GA500
driver? Or better yet, do you have a list of files and paths that
needed to be changed after installing a generic build to get the slate
wifi and touch screen working?

thanks,

kipper

On Jan 8, 3:37 pm, Jan Van Winkel <vanwinkel...@gmail.com> wrote:
> @Chih-Wei Huang
>
> First a small correction the driver that I got working, by accident,
> is the bcmsmac and this for the 4313 bcm chip set.
> I was expecting to see it working with the b43 driver and tried
> multiple kernel builds with no success but this could be due to the
> fact that that wl module was still there.
>
> But the real root  cause is that the wl kernel module does not play
> nicely with ICS wpa_supplicat and I was just lucky that the bcmsmac
> ( + wpa_supplicat) worked out of the box after copying the firmware
> from ubuntu 11.10.

> See post:http://groups.google.com/group/android-x86/browse_thread/thread/55487...

[RedHanded97]

Any update on this build? I haven't tried it myself as I am a bit of
an Android newbie but am interested in what other people have found...

On Jan 15, 10:41 pm, Jan Van Winkel <vanwinkel...@gmail.com> wrote:
> For those that are interested you can find a preliminary device target

> for thehpslateat the following link:https://docs.google.com/open?id=0Bxw1kTqfiG57NmM4M2I0YTMtODk5NS00OTJl...

[greg]

Jan, thank you for that - I was able to use your target-files and create an ISO for the hp slate 500 based on android-x86 repo as of end of Feb. 

So far it seems fine, tho' I did not test much yet.  Wifi works, n-trig touchscreen works (not sure about multitouch), etc.  Am just booting/running off a USB so far.

greg

[greg]

Further to this - wifi and touch seem to work pretty well, including
pinch/zoom. Camera works (rear) but slow/jerky. Sound does not seem
to work, nor does screen auto rotate. Did not instal, still booting
off the usb so did not try installing any other apps.

If anyone interested I can make this iso available... its just a
compile, no changes other than bcom wifi and ntrig stuff. Would stil
like to figure out sound - would make this pretty reasonable.

Greg

On Mar 2, 6:36 pm, greg <gkn...@gmail.com> wrote:
> Jan, thank you for that - I was able to use your target-files and create an
> ISO for the hp slate 500 based on android-x86 repo as of end of Feb.
>
> So far it seems fine, tho' I did not test much yet.  Wifi works, n-trig
> touchscreen works (not sure about multitouch), etc.  Am just
> booting/running off a USB so far.
>
> greg
>
>
>
>
>
>
>
> On Sunday, January 15, 2012 6:41:01 AM UTC-5, Jan Van Winkel wrote:
>
> > For those that are interested you can find a preliminary device target
> > for the hp slate at the following link:
>

> >https://docs.google.com/open?id=0Bxw1kTqfiG57NmM4M2I0YTMtODk5NS00OTJl...

[Misseri Xavier]

Hi,

Is that possible to share the iso file ?

Thank you very much.
Xavier

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

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.

[dtdave]

I would love to get that iso as well! Any luck on the sound?

[MHeathK]

I'd like to give it a try on my slate.

On Mar 3, 7:42 am, greg <gkn...@gmail.com> wrote:

[Gerson Lopez]

Hi Greg,

Yeah I would definitely be interested in your ISO. I am using HP slate 2 and everything works fine except for wifi and sound. I wuld really like to learn how to do this my self, any ideas or good source for tutorials? Thanks in advance. 

[Dekkar]

Would like an ISO to try on my Latitude ST.... they have similar hardware.

Thanks,

Dekkar

[Gurs]

Yes I would definitely give it a try and post any findings. Thank You.

[CruciasNZ]

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

Hp Slat 500 (1 not 2) everything working except sound, hardware accel,
auto-rotate and of course, it can't install

[Gurs]

Thanks CruciasNZ but that is the build that I am using on my HP Slate 2. Oh well I will keep trying other builds and post back if I find anything. Thank You.

[David Martínez]

Do you know how to resume/restart the slate after screen timeout? If i use power button the screen only vcontins garbage.

[David Martínez]

Maybe i'm wrong but after resume/restarting the slate, the screen only
contains garbage and a reboot is necessary. Any hint about hot to
solve the issue?

[Joshua Hovis]

Just installed the 4-1 on my Slate. Sound isn't working correct. all
sounds get stuck in a continous loop.

Great work though, happy just to have it running at all, keep up the
good work!

Thansk,

Josh

On Apr 1, 3:15 pm, tabletsx86 <rbg.tablets...@gmail.com> wrote:
> your slate image is updated...didn't realize it didn't boot...normally
> check but
> must have slipped through...very slow booting maybe my non slate
> hardware I checked it on...
>
> hacked up a quick sound fix to try till you get sound working because
> someone said
> no sound.....
>
>    http://tabletsx86.org/CYNEW-UPDATED-BUILDS.htm

[Gurs]

Hey Jan,

Thanks for all the hard work tried your hp slate build on my hp slate 2 and loved it. Everything seems to work fine but the the wi-fi and sound. I even tried the tabletx86 updated hp lsate build 20120401 and would not boot. Is there any way you can add hp slate 2 wi-fi drivers to your hp slate build. Let me know if I can be of any assistance. Thanks again.

[CruciasNZ]

How did you guys get the sound working? Can you link to the steps or
post here?

[aaronb1138]

I'm having the same sound loop problem on an HP Slate 500. Sound
loops. Sounds like some kind of PCI bus issue. I had sound working
exactly one time, after booting from the USB flash method. USB flash
drive and internal installs consistently have the sound loop.

Also, although it is generally against the AOSP and Android x86 goals,
is there any chance we can get a build for the Slate using Intel's
latest EMGD drivers. They claim full hardware acceleration of OpenGL
2.0 / ES 2.0 on Android Gingerbread with their binaries for the E6xx
processors, so there should be a window to move those binaries over to
the Zxxx processors on ICS.

Please see the bottom of the support matrix here:
http://download.intel.com/embedded/software/EMGD/324002.pdf?iid=5048

On Apr 2, 4:04 pm, tabletsx86 <rbg.tablets...@gmail.com> wrote:
> stuck in a loop???
>
> did the hack and ran jetboy to verify sound worked...it worked fine...
>
> don't have a clue about any loop...???
>
> further explanation/more info needed...
>
> or just wait til maintainer fixes sound correctly..

[Kyle Meyer]

Was the image just pulled?  I don't see it up on the site.

On Sunday, April 1, 2012 1:15:56 PM UTC-6, tabletsx86 wrote:

your slate image is updated...didn't realize it didn't boot...normally
check but
must have slipped through...very slow booting maybe my non slate
hardware I checked it on...

hacked up a quick sound fix to try till you get sound working because
someone said
no sound.....

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



On Mar 26, 11:35 pm, CruciasNZ <chris.pa...@gmail.com> wrote: