Now there are issues on HOME_APP_ADJ and HOME_APP_MEM properties...
On 8 Apr, 01:54, Yi Sun <[email protected]> wrote:
> If you are seeing some messages like load libgl.so failed bla bla
> bla.... It is harmless and most likely you are still hitting on the 1
>
> On Tue, 2009-04-07 at 15:49 -0700, Luca Belluccini wrote:
> > Confirm the 2nd ... I think there's also some issue with opengl lib
>
> > On 7 Apr, 14:42, Chen Yang <[email protected]> wrote:
> > > hi,you may reference this thread for more information on the issues
> > > with current most updated
> > > source:http://groups.google.com/group/android-porting/browse_thread/thread/6...
>
> > > basically, i guess there are some issues like:
> > > 1) battery service with incorrect path information
> > > 2) preloaded-classes reference non-exist class for build for x86
> > > --
> > > Chen
>
> > > On Tue, Apr 7, 2009 at 6:43 PM, Luca Belluccini
>
> > > <[email protected]> wrote:
>
> > > > I am not able to boot correctly android using 2nd april codebase.
> > > > I fixed some build errors (they removed ext2fs and mountd from build
> > > > process).
> > > > I get the installer image, install it but after executing init.rc's
> > > > files i get a console, but no graphical user interface.
> > > > Executing ps, i see zygote and all the other processes running.
> > > > Using a "february" codebase, it works.
>
> > > > On 5 Apr, 16:53, Luca Belluccini <[email protected]> wrote:
> > > >> We all know from previous posts that it is possible to make android
> > > >> run on EEEpc 701.
> > > >> We are able to:
> > > >> [video] works with framebuffer (no h/w support)
> > > >> [audio] works??? maybe compiling modules and adding uses ALSA
> > > >> [wifi] works by using its module
> > > >> [lan] works by using l2 module
>
> > > >> Is it ok?
>
>
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
