I don't suppose you can get the existing versions for Pre3 and TouchPad released? There are some changes that I would like to be able to make.

tl; dr: Recompile everything with FP set to hard instead of soft.

softfp was a compromise for a number of years but since we are mostly in the age of Cortex now for mobile/tablet markets, it should be possible to recompile the entire toolchain, kernel and apps for a significant speedup anywhere FP is used: 3D, OpenGL, OpenSSL etc.. However, binary only blobs such as 3D drivers need to be recompiled.

The title is incorrect. This doesn't make device faster. Original title: "Ubuntu/ARM rebuilt with hardfp float-abi".

Call it Milamber.js

Points for guessing the reference.

Guessing http://en.wikipedia.org/wiki/Pug_(fictional_character) :P

Correct. =)

The inverse is more useful.

webOS running with an interface to the Android market and ability to run Android apps. It should not be that hard to get that working if people pitch in to help.

- Dalvik needs to work under webOS which should be a recompile and some changes. There's also Alien.

- Android apps need to have a generic wrapper to put them into webOS cards.

- Some other interface issues to clean up.

So, who wants to help do this?

PS: FWIW, webOS essentially uses an Android kernel already.

megaduck, you can already dive into parts (well the non-compiled bits) by taking the webOS doctor apart (it's just a jar).

The WebOS Internals team is happy to accept any patches which are then made available to users with Preware.

So you don't have to wait to get started and we would love more hackers joining the effort. We are also usually available on #wosi-dev on IRC.

muffle is broken until I have time to make a new patch. Probably not till this weekend.

The Pre actually had decent hardware except for being light on mem. The OMAP chip was particularly overclock friendly and once overclocked along with some additional tweaks was nice and fast.

The problem was the earlier webOS versions had no GPU acceleration at all and ended seeming sluggish sometimes.

It needs a bigger form factor in slicker package - CPU/GPU matter but not as much as form factor for the Pre atm. Having the tiny Pre screen does little justice to webOS.

If they could get a SGS2 or Atrix type device out with GPU accelerated webOS UI and may be ship Android compatibility until webOS apps catch up - it would become a really credible player.

Yes, I should have been more precise. I've never liked the form factor and packaging of the WebOS devices. TouchPad looks like it might be up to scratch, but still nothing that looks good to me on the horizon in terms of the handset.

I have an old Sprint Pre and a Pre2. Even with the it clocked to 1.1GHz and an increase in the compcache the difference is quite noticeable. The Pre2 absolutely trounces it in performance. That extra 256MB makes a big difference.

webOS 2.1 can be installed on the Pre if you make use of the Meta-Doctor.

Some additional hoops to jump through but it's entirely doable along with overclocking, you end up with a pretty snappy device.

http://www.webos-internals.org/wiki/WebOS_2_Upgrade

You want to be working on current-gen hardware if you're baselining future development efforts at 2.x going forward.

What you don't want to be using as your sole dev/test unit is a two year-old device using an unofficial workaround to get an OS version installed that was never intended to be used on it.

It's fine if you want to support those people that decided to use the workaround by having one of these franken-units around as a secondary edge-case device to test on, but it should never be the only device you use to develop and test with. I have a 1Ghz overclocked Sprint Pre at 1.4.5 as my "daily driver" and another Sprint Pre I've upgraded to 2.0 for testing such cases.