Colorspace / component ordering? (RGBA vs ARGB vs RGB vs BGR)

The texture image looks fine it just doesn't draw to the screen. That can't be a Colorspace/component ordering issue, right?, unless if it's in the wrong mode it won't draw?. liar/krnlyng might have said it renders improperly, but the boot animation that's in the trace looks fine.

ps. I have no idea how it works.

i traced the texture from where it originates in the android bootanimation up until to the renderer app and it was transfered correctly byte by byte and RGBA component ordering was used everywhere

Well although somewhat "in a gray area" we could try installing the aliendalvik rpm dumped from someone's Jolla phone Also I just found a dump of it and will try making it work on my Nexus5 (file system dump, not rpm dump, don't know how complete it is or what scripts are run from the rpm)

theres a specific kernel module thats required for this. so I don't think it can be done.

the kernel module isn't the biggest issue (i think earlier versions of aliendalvik didn't use the mysatroker kernel module), there is more like gralloc, hwcomposer and so on...

on webos there is a similar project, what do they do: they have the chroot render into a secondary framebuffer (on webos there are two), and display its contents later

now... :0 on sfos (at least on the jolla phone):
there are two framebuffers! /dev/fb0 and /dev/fb1
then, does aliendalvik use the second fb? doesn't seem like it, if we can trust fuser/lsof

There's a new, similar project that might be of use to you called Shashlik. You might have already heard of it but I don't think anyone's mentioned it yet here on TMO. There's a talk about it on Sunday.

Looks promising! They're even trying to use normal Linux kernel rather than an Android one.

Does this work out of the box on Harmattan yet?