KitKat Pi?

[RoelVB]

I'm wondering the same thing.
It seems KitKat has a better change of running stable on the Pi than ICS (or JB).

[carsonuh]

I was wondering the same exact thing. Since it is tailored to work with lower end devices (that have 512mb ram) then in theory it should be able to run on Raspberry Pi. This could be a game changer if does

[ojdon]

Since when was the issue of Android on the Pi a memory limitation?

The reason why Android is an issue on the Pi is because of Broadcom's proprietary hardware... Kitkat doesn't change a thing and Google's statement about lower memory requirement was for OEMs who were still shipping new devices running Android 2.3 Gingerbread.

[ShiftPlusOne]

Why do you need broadcom to write the driver? Why can't the folks interested in Android on the pi write a graphics driver using the available API?

[redhawk]

What API??

As far as I'm aware all the low level hardware stuff is only known to Broadcom therefore if you want working drivers for Android only Broadcom can write them.
Furthermore the Pi is powered by an old slow ARMv6 processor I see no benefits from running Android over what Linux or RiscOS already has to offer.

Richard S.

[ShiftPlusOne]

Well, there's OpenGL ES and OpenVG. Looking at my phone, I don't see it doing anything graphically that couldn't be done without low level access to the hardware on the pi.

This is an honest question by the way. I assume you folks are right and Broadcom would need to be involved, I am just wondering why.

[jamesh]

There's also dispmanx.

But the problem is that Google keep changing the way Android works and making it need more and more low level connection to the GPU. It's a right PITA.

[demetry14]

Thats why you should just do a WebOS build. There is a company that has android apps working on WebOS... Then you have the masterpiece of WebOS with the lag of to many apps to choose from.

[MoosePi]

Where is the download link for a fully working WebOS .IMG ??

[redhawk]

I think you're missing the point Android on the Pi isn't the issue here but the lack of driver support from Broadcom, WebOS would be no better off.

Richard S.

[jamesh]

And since webOS is really on the decline, it would be an odd decision to port it...

[demetry14]

I think you're missing the point Android on the Pi isn't the issue here but the lack of driver support from Broadcom, WebOS would be no better off.

Richard S.

WebOS is already better off because it is in a layer above the Linux system which fully supports the hardware on the Raspberry Pi as seen with Raspbian and all other Linux systems currently available for the RPi. WebOS is not on a decline, it has declined completely to only be for those of us who remember how to build and use it and write apps for it. It is not impossible to get this going, but it would take someone without a full time job a few days to get the base system and GUI running.

[demetry14]

Where is the download link for a fully working WebOS .IMG ??

No img, but they hold your hand. Build away.

https://github.com/webOS-ports/meta-raspberrypi

[demetry14]

Here is a great base to work from prebuilt OpenEmbedded build.

http://www.gentoogeek.org/steves_world/ ... image_html

[2549]

http://webos-ports.org/wiki/Raspberry_Pi

http://pivotce.com/2014/09/01/official- ... t-updates/

[DirkS]

http://webos-ports.org/wiki/Raspberry_Pi

http://pivotce.com/2014/09/01/official- ... t-updates/

And the reason for digging up this corpse is?

[mimi123]

There is a build with buggy mouse support (but working keyboard).
There is model A support coming (800x480)
Info at #razdroid

[Joe Schmoe]

And the reason for digging up this corpse is?

Well, it is almost Halloween, you know…