Android OS Forum banner
1 - 20 of 109 Posts

·
Android Dev
Joined
·
61 Posts
As I am still waiting for my Touchpad to arrive, I decided to be as useful as I can without actually having access to a device, so I am currently working on a kernel very specifically for the Touchpad with manufacturer drivers for any known hardware component on the Touchpad. I am also removing components within the reference drivers that are not present on the Touchpad, such as a physical keypad. and tweaking the video framebuffer specs to the physical specs of the Touchpad (1024x768x16).
If anyone has any information that I don't have in this doc or has any corrections for me I would appreciate it.
Thanks,
TecKnight

Update:
[Wednesday 8/31 at 1:30 PM PST]
This is a work in progress intended to assist developers working on porting Android to the HP Touchpad. As HP has thus far not disclosed any interface level details on the Touchpad, the information presented here may be speculative.
Where relevant, I have indicated the sources of information that support my conclusions. This information will be updated or corrected as the facts become evident.
I am now in the process of building an Android kernel based on the current gingerbread source and the msm8660_surf profile from the codeaurora github.
I am removing items present in the msm8660_surf build that do not exist on the touchpad, such as the physical keypad and I am adding the hardware devices listed below.
I am also changing the video geometry to match the Touchpad's maximum video resolution (1024x768x16). I have given this kernel the codename "KRYPTONITE".
I will post the complete source and binaries once the kernel is built. Unfortunately HP is taking their sweet time shipping me my Touchpad, so I will be working with any developers with access to a touchpad once it has been built.
I expect to have my first successful build sometime Wednesday (8/31) or Thursday(9/1). At that point I will add a link to this document and post something on rootzwiki as well.
Any developers that would like to work with me on this, especially if you have access to a Touchpad, please feel free to message TecKnight at rootzwiki.com forums or email me: [email protected]

KRYPTONITE-Hardware Subsystems HP Touchpad

My HP Touchpad Devs Folder
 

·
Android Apprentice
Joined
·
66 Posts
TecKnight said:
As I am still waiting for my Touchpad to arrive, I decided to be as useful as I can without actually having access to a device, so I am currently working on a kernel very specifically for the Touchpad with manufacturer drivers for any known hardware component on the Touchpad. I am also removing components within the reference drivers that are not present on the Touchpad, such as a physical keypad. and tweaking the video framebuffer specs to the physical specs of the Touchpad (1024x768x16).
If anyone has any information that I don't have in this doc or has any corrections for me I would appreciate it.
Thanks,
TecKnight

Hardware Subsystems HP Touchpad

My HP Touchpad Devs Folder
I didn't know these touchpads were only 16bit color?
 

·
Android Dev
Joined
·
61 Posts
Discussion Starter · #4 ·
Yes, twiddler
Android's video framebuffer interfaces are all implemented at 16 bit color depth even if the underlying system supports > 16 bit
 

·
Android Dev
Joined
·
61 Posts
Discussion Starter · #5 ·
Thanks Adam.
If you look at my document, you will see that I do reference that document for several of the identified components.
Definitely useful for our purposes, which of course is to get Android running on this baby.
TecKnight
 

·
Android Dev
Joined
·
61 Posts
The reference msm8660_surf device is a developer board called a DragonBoard. The DragonBoard was created by Qualcomm to show off the APQ8060 processor and to allow hardware developers to test various devices with the new processor. The Dragonboard has a physical keypad (see image)
View attachment 1790
I am simply removing the reference to this hardware. This will have no effect on touch screen based keyboards, USB keyboards or Bluetooth keyboards. They will all function normally.
The reason I am using this as the reference build for KRYPTONITE, is that the DragonBoard is currently the only other released device using the Qualcomm APQ8060 processor and since it is a developer product, Qualcomm has full source code freely available.
TecKnight
 

Attachments

·
Android Apprentice
Joined
·
57 Posts
bmtbandit said:
I see in your write up the presence of a GPS chip. I was under the impression the TP did not have GPS.

SO there is a chip, and webOS just is not utilizing it?
The 3G version of the TouchPad did/does have a GPS built-in...but the non-3G (aka - the WiFi version most people have...especially those who bought their TouchPad via the "firesale") do not have GPS built in.

There are rumors of people either getting or working to get an external GPS unit (usually a bluetooth GPS unit) to work with their TouchPad...but those claims are unsubstantiated from my research.

I hope this helps! :)
 

·
Android Beginner
Joined
·
4 Posts
I did not want to cross-post this everywhere, but I think TecKnight is providing the most open platform for development and sharing. Kudos.

This was from a tip (Avatar26) in another thread, the leaked HoneyComb ROM from HTC Puccini which also has Qualcomm MSM8660 chip. Rest of internals are unknown (as far as I could tell), but it also has a 10" screen so there's a slight chance of same Cypress touchscreen? The HTC Lead (4.3" phone, same chip) also has a dump floating around apparently but I couldn't find it.

http://forum.xda-developers.com/showthread.php?t=1240772 dev thread porting to HTC Flyer

http://www.megaupload.com/?d=ZYBZL0ZP dump link

Keep up the good work TecKnight. I wish I could help more but I know nothing of anything.

EDIT: nevermind about the touchscreen drivers. It seems that the Puccini is packing N-trig touchscreen based off the driver found in /bin/
 

·
Android Lover
Joined
·
144 Posts
I'd also like to add my kudos for TechKnight for being so transparent.

I personnaly think that all this cloak and dagger, secret society, here's a video to prove we are good nonsense is [email protected]#$ - There, I've said it - it took me a while, but I've caved. I'm not going to donate to a bounty, I'm not going to go after a bounty. I'm going to focus on the bootloader and how to de-brick if you totally fubar the iNAND and any information I find out, you'll know about here immediately. Thats what an Open Source Community should be about

That being said, I think the everyone working on getting Android running on TouchPad are making amazing progress and I wish the best to whoever wins the race. I finally get to unbox by TouchPad on Sunday and I'll freely and willingly help anyone and everyone (provided my TouchPad doesn't get bricked in the process)

Hey, speaking of which - When you install Ubuntu on the TouchPad, what touch screen drivers are being used?
 

·
Android Beginner
Joined
·
12 Posts
calris said:
I'd also like to add my kudos for TechKnight for being so transparent.

Hey, speaking of which - When you install Ubuntu on the TouchPad, what touch screen drivers are being used?
It's not actually installed on the device. It's a chroot environment with its window system pointed at a local X Server.
 

·
Android Beginner
Joined
·
16 Posts
He told me he's not much in to twitter, chatted with him a bit, and I think this guy has his head on straight. Good luck, and I hope you get your TP soon.
 
1 - 20 of 109 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top