[AndroidBall]

Ok guys we got it. Lots of stuff to see here.

Here it is

This dump contains .img files that you mount. Thats why they are so small. Once you mount it you will have access to the files. If you don't know how to mount it you shouldn't even be trying so don task.

NO ONE MAY POST THIS ANYWHERE OUTSIDE OF ROOTZWIKI WITHOUT PERMISSION FROM ME OR jiwanish. DO NOT DOWNLOAD AND REDISTRIBUTE AS YOUR COPY. Thank you​

THIS IS NOT A ROM YET GUYS STOP ASKING HOW TO FLASH IT!

Jiwanish's Twitter: http://twitter.com/#!/ShahzebJiwani

2.2 Froyo Android image for HP Touchpad.

Full image dump.

For the Android community at large. Released as soon as we had it.

 

[b16]

Keep it civil, this is awesome news. This is a progressive place, we enjoy having you all here!

 

[b16]

Relax, I don't think he meant it in a bad way. Lets move on, we got more dumps coming today.

 

[bmtbandit]

i just realized this might be a problem and had to register and ask! would running android render the touchstone useless? I've been contemplating buying one, if android does kill it then I'll be able to save some monayy

I don't see how it would. The Touchstone works off Magnets, and is hardware based. There are also threads about making other devices use Touchstone, by modding the hardware.

 

[ReverendKJR]

After taking a look at the build.prop of this dump, it appears that this android build is meant for a device that has both HDMI output and GPS. I wish the Touchpad had that. Obviously, these pieces will be removed from our build to eliminate clutter.

 

[ReverendKJR]

Looking further into this build, i notice that a preliminary build is going to be a bare bones system, meaning that it will run Android.... and thats it. Drivers are going to be needed that are not part of this default build. It will struggle with basic functions such as getting wifi activated and possibly sound. I think that a good bit of patience will be required before we start dumping this on everyone's devices.

 

[mythamp]

This build should have all the correct drivers installed.....in the video we saw Jiwanish surf the web through wifi and also had bluetooth on. Sound and Camera ran perfectly based on singhaldallas's video on youtube

. Not sure how you came to that conclusion, maybe i need to learn a bit too..i am still a noob at this.

 

[Joenathan]

Looking further into this build, i notice that a preliminary build is going to be a bare bones system, meaning that it will run Android.... and thats it. Drivers are going to be needed that are not part of this default build. It will struggle with basic functions such as getting wifi activated and possibly sound. I think that a good bit of patience will be required before we start dumping this on everyone's devices.

The youtube videos show that wifi already works and furthermore since this is a Qualcomm dev build and it's their SOC running the touchpad, I'd imagine it has all the drivers.

 

[Joenathan]

Guys, not to alarm you but this will more than likely take at least a couple months for an alpha version then another couple for a RC. I know it's exciting but we are building from the ground up here. Getting this hardware to work with Android will be tough but not impossible. It will take longer because there are no current Android tablets running the same hardware configurations, these guys probably had to choose the device that had the MOST similarities and then work with that. That being said, many many things will not work or work well when the initial alpha is released. Also, were going to need Honeycomb source if were going to get that working, but that's like 6 months+ down the road I'm guessing. My times could be off a bit but the issues are the same. Have patience and be grateful, help if you can, if you want. I will. If there is one good thing that comes out of this I would say it is that because this device is WiFi only then a lot of the work normally associated with doing this will be removed because these guys won't have to work on any kind of radio hardware. I just hope there are enough similarities between the chosen devices build and the Touchpad that this operation can go as swiftly and smoothly as possible.

Dude, it already runs android... It'll be much easier with this dump, I'd imagine they could have Gingerbread booting in a day.

With this dump they have a kernel and they have drivers which are arguably the hardest part of porting Android.

 

[cypis]

Guys, not to alarm you but this will more than likely take at least a couple months for an alpha version then another couple for a RC. I know it's exciting but we are building from the ground up here. Getting this hardware to work with Android will be tough but not impossible. It will take longer because there are no current Android tablets running the same hardware configurations, these guys probably had to choose the device that had the MOST similarities and then work with that. That being said, many many things will not work or work well when the initial alpha is released. Also, were going to need Honeycomb source if were going to get that working, but that's like 6 months+ down the road I'm guessing. My times could be off a bit but the issues are the same. Have patience and be grateful, help if you can, if you want. I will. If there is one good thing that comes out of this, I would say it is that because this device is WiFi only then a lot of the work normally associated with porting will be removed because these guys won't have to work on any kind of radio hardware. I just hope there are enough similarities between the chosen devices build and the Touchpad that this operation can go as swiftly and smoothly as possible.

There is few devices based on same hardware Like sensation or evo 3d. HTC puccini should be almost the same to Touchpad.

 

[seibertjd]

Is it possible to take the open source kernel from WebOS which has the drivers in it and modify it to work with Froyo for an early release?

 

[rothnic]

Is it possible to take the open source kernel from WebOS which has the drivers in it and modify it to work with Froyo for an early release?

Yeah, I'm just not sure how much differences there would be compared to an android kernel. So there might be some level of porting required, and porting as the kernel version required for each new android release changes. This was a small issue going from froyo to gingerbread, but a larger issue going from gingerbread to HC.

 

[Joenathan]

This does mean they have compiled drivers, but still no one has the driver source. So, that kernel(which has drivers statically compiled in) is a black box that has to be worked around until we have kernel source. Generally, we can complain to the vendor that they must release the source code because they are shipping a product with GPL'd code in it. However, I'm not sure if this arguement extends to their actual kernel they ship with the tablet.

In other words, to be able to move with android as it progresses, we still need kernel source.

Most drivers are proprietary and their source code is never released, whereas when using the Linux kernel companies are forced to abide by the GPL license and release the source code.

Having said that, the source code for the kernel would be nice to have and would give the devs greater access to the hardware but isn't at all necessary to progress.

 

[rothnic]

Most drivers are proprietary and their source code is never released, whereas when using the Linux kernel companies are forced to abide by the GPL license and release the source code.

Having said that, the source code for the kernel would be nice to have and would give the devs greater access to the hardware but isn't at all necessary to progress.

It absolutely is necessary to progress. Look at the Viewsonic Gtablet and other Tegra2 tablets that are stuck without a totally working honeycomb port because Nvidia never released a honeycomb compatible kernel for it.

 

[Joenathan]

It absolutely is necessary to progress. Look at the Viewsonic Gtablet and other Tegra2 tablets that are stuck without a totally working honeycomb port because Nvidia never released a honeycomb compatible kernel for it.

This is starting to get off topic, but, the only reason there are no good Honeycomb ports is because we don't have the source code for Honeycomb and no other reason than that.

 

[yarly]

Most drivers are proprietary and their source code is never released, whereas when using the Linux kernel companies are forced to abide by the GPL license and release the source code.

Having said that, the source code for the kernel would be nice to have and would give the devs greater access to the hardware but isn't at all necessary to progress.

The kernel to the touchpad is open because it's linux. The rest of the code is not.

Just because a kernel is GPL however, does not mean all the drivers (which reside in the kernel) are open sourced. Kernels can be GPL and have binary blobs in them. Examples: every linux kernel for android until the Galaxy S2 had binary blobs in it (most namely the GPS).

 

[rhcp011235]

We are working as hard as possible to bring you android guys. I and many other team members dont even have a TP yet.

 

[bmtbandit]

Can someone please provide instructions how to convert the various .img files into actual files.

 

[yarly]

Easiest way would be mounting them from within linux

 

[bmtbandit]

Easiest way would be mounting them from within linux

How do you handle the multipart files or is each file its own directory? Ie. would I:
mount - o loop 1.img /mnt/1
mount - o loop 2.img /mnt/2
...