My next mobile phone will be whatever linuxmce has the best support for -there's talk of developing for both android and the iphone. I'm willing to contribute $40 to one of these, but I prefer to wait to see which makes greater strides.

Just to give my 2 cents, I would contribute to an android orbiter. I do not have either a android phone nor a iphone, but it would make more sense to have an orbiter for the android phones considering that only AT&T has the iphone. Android phones will be available on cdma and gsm networks such as verizon, sprint, AT&T, and t-mobile, making android a better choice for linuxmce. The bigger the pool of users, the bigger the pool of people who would contribute for development now and for future versions of an orbiter. :=)

Just to give my 2 cents, I would contribute to an android orbiter. I do not have either a android phone nor a iphone, but it would make more sense to have an orbiter for the android phones considering that only AT&T has the iphone. Android phones will be available on cdma and gsm networks such as verizon, sprint, AT&T, and t-mobile, making android a better choice for linuxmce. The bigger the pool of users, the bigger the pool of people who would contribute for development now and for future versions of an orbiter. :=)

I think both would be great additions...but it has to be said that currently there are more users with iPhones than Android based phones. This could change over time as more phone manufacturers build products around Android...but for now thats the case.

It would be really cool if a android orbiter was integrated with androids UI (using its menu button to bring up the computing, sleep menu, power, more, etc buttons), so the tilt function, and maybe even a widget view just whats playing (and maybe some other things).Is it posible to get the information out of linuxmce so it can be rendered in the orbiter (in this case the android handset)?If true, then I'm intrested in take part in this project.

They recieve images of fully rendered screens from the core over RFCOMM,they send back keypresses and screen touches over RFCOMM,they send back bluetooth location information.

In the end, we would make a touch screen UI variation, which would take advantage of the phone's screen, and build a UI for it, but due to the nature of how Orbiter works, making one with a "native" UI would be exceedingly difficult