LiMo, MeeGo, or other mobile Linux on the Blade

[Guest fonix232]

I was thinking today about running another type of Linux on the Blade.

After looking through a few of the OS', I made this list (most possible on top):

- LiMo

- MeeGo

- Maemo

- TuxMobil

I know, this will be hard, but LiMo is very similar to the Android system (just it's totally native) and relatively should be easy to boot.

So, my question is, should we try porting any of these?

[Guest rayraven]

^Frankly, none of them are as polished as android, nor do they have the needed apps.

Meego is showing promise, but i think we should wait till they actually make a phone that someone sells B)

IMHO, we need MIUI/Gingerbread before these :unsure:

[Guest Phoenix Silver]

why not :unsure:

after all i have installed rockbox in my ipod video and i'm very very happy with it

is this the way to rid of java ?

Edited January 1, 2011 by Phoenix Silver

[Guest rayraven]

OFFTOPIC:

^There's a rockbox app in development for android.

http://www.rockbox.org/wiki/AndroidPort

[Guest That-Guy]

Think we should stick to getting a solid 2.2 and 2.3 :unsure:

Android is a great platform!

[Guest Meizirkki]

MeeGo is definitely interesting, but targets the armv7 instruction set, while Blade is older armv6. Porting is of course possible, but probably not worth it because MeeGo user interface needs graphics acceleration, which, according to MeeGo wiki, will not work with Android libraries.

[Guest domenico lamberti]

i would love to have any of these on my blade, yes i agree a strong 2.2/2.3 build would be more beneficial first , but if we could try to do it , and get a successful boot on tthere , some people want to do it to show that they can , not for any other reason

[Guest fonix232]

MeeGo is definitely interesting, but targets the armv7 instruction set, while Blade is older armv6. Porting is of course possible, but probably not worth it because MeeGo user interface needs graphics acceleration, which, according to MeeGo wiki, will not work with Android libraries.

But there is no need for Android libraries, as the whole system gets ported, not just the UI.

[Guest rayraven]

^more offtopic, but, how's the MIUI port going?

Cant wait to test :unsure:

[Guest Tom G]

Meego is showing promise, but i think we should wait till they actually make a phone that someone sells :unsure:

Nokia N900?

[Guest rayraven]

^Which came with Meamo & got beta builds of Meego.

What i meant was, once they release a new phone with Meego on it, ergo, a stable & complete build of Meego :unsure:

[Guest Meizirkki]

But there is no need for Android libraries, as the whole system gets ported, not just the UI.

libEGL and libGLESv2

As we know vanilla X and software GLES works but we need hardware libEGL and libGLESv2 for better performance.

I pulled libEGL.so, libGLESv2.so and libGLESv1_CM.so from my Nexus /system/lib along with the supporting /system/lib/egl files lib***_adreno200.so as the system/lib files are just stubs into the lib/egl files.

After booting .xsession_errors reported liblog.so not found when loading mcompositor. pulled that from Nexus.

libcutils.so was not found next then 'libc.so ELF version does not match current version' was reported. The libc.so in /usr/lib was a pointer to /lib so I just copied the /lib file to /usr/lib.

Now libutils.so and libz.so were not found and were pulled from the nexus.

Now here is the kicker, 'undefined Symbol __sF' in libc.

This is because the Android libs I pulled have been built with Bionic libc and I cannot use that as that would break the rest of MeeGo.

So the question is can we arrange for bionic and glibc to coexist or is this the end of the road?

After talking to a few guys on xda I think this avenue is closed - unless you know better. http://forum.xda-developers.com/showthread...4255&page=6

This was the case for Nexus One. ZTE Blade graphics drivers are not open source AFAIK, so we'll end up with the same problem. Please correct me if I'm wrong.

Source:

http://wiki.meego.com/ARM/MSMQSD

Edited January 2, 2011 by Meizirkki

[Guest Mixu]

MeeGo is definitely interesting, but targets the armv7 instruction set, while Blade is older armv6. Porting is of course possible, but probably not worth it because MeeGo user interface needs graphics acceleration, which, according to MeeGo wiki, will not work with Android libraries.

To my understanding MeeGo doesn't need graphics acceleration but of course it makes UI smoother. If I remember right, N900 was running quite long time without acceleration and it was working ok (but I haven't followed N900 discussion that closely since I don't own one so maybe the MeeGo really needs the acceleration nowadays).

There is already a tutorial about getting the MeeGo to run on N8x0 (armv6 and no graphics acceleration) [Tutorial] Meego on N8x0 @talk.maemo.org. If they can get MeeGo usable on N8x0, then shouldn't it be also usable on Blade if we think about hardware capability? Yes, it probably won't be easy but as you said, it would be interesting.