Android image and some instructions

andrzej zaborowski balrogg at
Thu Nov 6 15:38:24 CET 2008

2008/11/6 Sean McNeil <sean at>:
> andrzej zaborowski wrote:
>> 2008/11/5 Álvaro Lopes <alvieboy at>:
>>>> This will take time to get down right, but hopefully now you will all be
>>>> able to begin playing with Android.
>>> Hi Sean, hi all,
>>> I has finally able to boot it and have something on the screen in my
>>> GTA02. Pretty much impressive. :) Thanks a lot for your work there. Took
>>> quite a few boots
>>> for me to be able to see anything on the screen, don't know exactly why.
>>> I do have some notes about it:
>>>       * Took me quite a while to figure out that in "ADBHOST=neo", "neo"
>>> was indeed the IP address of the freerunner :) Should have been smarter.
>>> Anyway, I think you
>>> can easily clarify that on your page.
>>>       * Do you have those needed kernel patches around ? Although I don't
>>> have a debug board I think I might have some spare time to try "fixing" the
>>> resume issue,
>>> even if it means merging other people (Andy,...) patches.
>>>       * There seems to be no display acceleration. Can the community help
>>> in anything here ?
>> Yes, the acceleration features done in Xglamo can be added to whatever
>> manages the screen in Android or better yet to the framebuffer driver
>> in the kernel.  This would allow both Android and Xfbdev and even
>> mplayer to use the same driver code.
>> I don't know what graphics accel features the T-mobile G1 has, but if
>> we're lucky they're implemented on the framebuffer side so the
>> interface is transparent to Andorid itself.
>> I wonder if anyone has tried to install a standard X server on the G1
>> yet?  Or a whole openmoko or qtopia distro?
> Android doesn't use an X server at all.

Yup, that's why it would be interesting :)

> It uses its own Java window manager
> that sits on top of the frame buffer. The G1 has accelerated openGL support
> and video/audio codecs used through the Packet Video OpenCore technology.

Do you know if the userspace accesses the hw directly or rather makes
an ioctl() on the framebuffer, when it wants to make an opengl call or
blit part of the screen?


More information about the devel mailing list