I just compiled and booted the new codes/binaries on my Treo 650, unfortunately it's still in a loop and no-go.
Could someone enlighten me on the debug process...? On Nov 22, 3:35 pm, koba <[email protected]> wrote: > FYI, > > > After the zygote process is running, the runtime process must be > > launched. I don't see an executable file for runtime, so I am > > guessing it gets created dynamically. > > Actually, following processes are 'folk'ed from zygote and changed > process name by native method android.os.Process#setArgV0(String). > That's why you don't see such executable files. > > On 11月22日, 午前11:56, NickDG <[email protected]> wrote: > > > The following processes look like they have started and are running > > normally.. > > > /System/bin/servicemanager > > /System/bin/mountd > > /System/bin/debuggerd > > /System/bin/rild > > /System/bin/mediaserver > > /System/bin/installd > > > The next step in the boot sequence is launching the zygote process. > > The executable is /system/bin/app_process > > > After the zygote process is running, the runtime process must be > > launched. I don't see an executable file for runtime, so I am > > guessing it gets created dynamically. > > > The runtime process then starts the servicemanager process. > > > The zygote process (app_process) then launches DalvikVM. > > > This is where I believe we are getting stuck. When I manually try and > > launch the app_process executable, nothing happens. No errors or > > anything. > > > I am trying a few things to see what I can do with it. > > > Cheers! > > > - Nick > > > On Nov 17, 3:20 pm, NickDG <[email protected]> wrote: > > > > An AID assists the system for acceleration. Usually an AID is not > > > required. I'm not 100% on this. > > > > I have read all over the internet that the screen resolution is > > > variable. Question is, does it auto detect or must we specify it in > > > the source? > > > > If Android only supports rectangular screens, we would probably end up > > > with black bars on the top and bottom of the Treo/Centro screen. > > > (320x240) The TX would be ok though. > > > > - Nick > > > > On Nov 16, 10:50 pm, Lo Yuk Fai <[email protected]> wrote: > > > > > What's AID...? > > > > > Using the method mentioned by john b to disable the boot animation, > > > > and strace to print its output to console. I got some messages, > > > > presumably just before the loop began... > > > > >http://ifile.it/34oy2wb > > > > > Unfortunately it's too fast for me to see what's really shown... Again > > > > showing a lack of solid debugging setup on our part... Anyway, is it > > > > possible to disable the splash screen altogether, not just the > > > > animation...? > > > > > BTW, I remember reading somewhere before that Android expects a > > > > rectangular screen...? Is this requirement changed and square screen > > > > works as well...? > > > > > Cheers! > > > > > On Nov 17, 9:28 am, NickDG <[email protected]> wrote: > > > > > > In the source, pmem is enabled for GPU acceleration. Since this > > > > > device isn't showing up on the Palm OS devices, I am guessing it > > > > > doesn't exist. > > > > > > We need to build from source again with the pmem disabled/turned off. > > > > > Can we ask the Android team how to disable this? According to the > > > > > source pmem is an AID. Not sure if it is required. > > > > > > - Nick > > > > > > On Nov 16, 10:48 am, Lo Yuk Fai <[email protected]> wrote: > > > > > > > Got console back as instructed by Alex. But that's it, no other > > > > > > progress. > > > > > > > If it's SurfaceFlinger, could it be something related to the frame > > > > > > buffer...? > > > > > > > Cheers. > > > > > > > On Nov 14, 3:15 pm, woodbook <[email protected]> wrote: > > > > > > > > There are 3 definitions for loglevel in system/core/init/init.h. > > > > > > > > #define ERROR(x...) log_write(3, "<3>init: " x) > > > > > > > #define NOTICE(x...) log_write(5, "<5>init: " x) > > > > > > > #define INFO(x...) log_write(6, "<6>init: " x) > > > > > > > > Normally it's set as 3 so it only outputs ERROR level. > > > > > > > > Have fun! > > > > > > > > On Nov 14, 1:01 pm, Lo Yuk Fai <[email protected]> wrote: > > > > > > > > > Just wonder... Will the log has more detail if loglevel in > > > > > > > > init.rc is > > > > > > > > set to a higher value... Say, 6? > > > > > > > > > Cheers. > > > > > > > > > On Nov 13, 6:54 am, NickDG <[email protected]> wrote: > > > > > > > > > > Boot log is great! Thanks for the work. > > > > > > > > > > Surface flinger was the first service to die before they all > > > > > > > > > went > > > > > > > > > down. > > > > > > > > > > This section has some errors that maybe caused it to die? > > > > > > > > > > SurfaceFlinger > > > > > > > > > SurfaceFlinger is starting > > > > > > > > > MemoryHeapBase > > > > > > > > > error opening /dev/pmem: No such file or directory > > > > > > > > > SurfaceFlinger > > > > > > > > > SurfaceFlinger's main thread ready to run. Initializing > > > > > > > > > graphics H/ > > > > > > > > > W... > > > > > > > > > SurfaceFlinger > > > > > > > > > Couldn't open /sys/android_power/wait_for_fb_sleep or /sys/ > > > > > > > > > android_power/wait_for_fb_wake > > > > > > > > > GLLogger > > > > > > > > > couldn't load <libhgl.so> library (Cannot find library) > > > > > > > > > SurfaceFlinger > > > > > > > > > EGL informations: > > > > > > > > > SurfaceFlinger > > > > > > > > > # of configs : 4 > > > > > > > > > SurfaceFlinger > > > > > > > > > vendor : Android > > > > > > > > > SurfaceFlinger > > > > > > > > > version : 1.2 Android META-EGL > > > > > > > > > SurfaceFlinger > > > > > > > > > extensions: EGL_ANDROID_query_string_config > > > > > > > > > EGL_ANDROID_swap_rectangle > > > > > > > > > SurfaceFlinger > > > > > > > > > ext/config: EGL_ANDROID_swap_rectangle > > > > > > > > > SurfaceFlinger > > > > > > > > > Client API: OpenGL ES > > > > > > > > > EGLDisplaySurface > > > > > > > > > using (fd=21) > > > > > > > > > id = PXA > > > > > > > > > xres = 320 px > > > > > > > > > yres = 320 px > > > > > > > > > xres_virtual = 320 px > > > > > > > > > yres_virtual = 640 px > > > > > > > > > bpp = 16 > > > > > > > > > r = 11:5 > > > > > > > > > g = 5:6 > > > > > > > > > b = 0:5 > > > > > > > > > EGLDisplaySurface > > > > > > > > > width = 51 mm (159.372543 dpi) > > > > > > > > > height = 38 mm (213.894730 dpi) > > > > > > > > > refresh rate = 57.78 Hz > > > > > > > > > SurfaceFlinger > > > > > > > > > OpenGL informations: > > > > > > > > > SurfaceFlinger > > > > > > > > > vendor : Android > > > > > > > > > SurfaceFlinger > > > > > > > > > renderer : Android PixelFlinger 1.0 > > > > > > > > > SurfaceFlinger > > > > > > > > > version : OpenGL ES-CM 1.0 > > > > > > > > > SurfaceFlinger > > > > > > > > > extensions: GL_OES_byte_coordinates GL_OES_fixed_point > > > > > > > > > GL_OES_single_precision GL_OES_read_format > > > > > > > > > GL_OES_compressed_paletted_texture GL_OES_draw_texture > > > > > > > > > GL_OES_matrix_get GL_OES_query_matrix > > > > > > > > > GL_ARB_texture_compression > > > > > > > > > GL_ARB_texture_non_power_of_two GL_ANDROID_direct_texture > > > > > > > > > GL_ANDROID_user_clip_plane GL_ANDROID_vertex_buffer_object > > > > > > > > > GL_ANDROID_generate_mipmap > > > > > > > > > > We are seeing pmem pop up again. Trying to access memory > > > > > > > > > that doesn't > > > > > > > > > exist on the system maybe? Can we rem it out in the source? > > > > > > > > > > - Nick > > > > > > > > > > On Nov 12, 10:29 am, Strags <[email protected]> wrote: > > > > > > > > > > > I'm using the debian/lenny rootfs > > > > > > > > > > fromhttp://hackndev.com/node/212. > > > > > > > > > > > I've built android, and copied the root filesystem into > > > > > > > > > > /android_root > > > > > > > > > > on /. > > > > > > > > > > > I boot debian, ssh in (over USB), and then: > > > > > > > > > > > chroot android_root ./init > > > > > > > > > > > This brings up the same messages that you're getting, and > > > > > > > > > > then the > > > > > > > > > > flashing robot. At this point, I can (using another shell), > > > > > > > > > > go into / > > > > > > > > > > android_root/dev/log, and look at a bunch of interesting > > > > > > > > > > log messages. > > > > > > > > > > > strings main > > > > > > > > > > > Unfortunately, the boot process seems to be continually > > > > > > > > > > dying and > > > > > > > > > > restarting: > > > > > > > > > > >http://codepuppies.com/~ben/treo/bootlog.txt > > > > > > > > > > > On Nov 12, 1:37 am, NickDG <[email protected]> > > > > > > > > > > wrote: > > > > > > > > > > > > Update: Now I am getting this error. > > > > > > > > > > > > A N D R O I D init: Unable to open persistent property > > > > > > > > > > > directory /data/ > > > > > > > > > > > property errno: 2 > > > > > > > > > > > init: cannot find `/system/bin/playmp3` disabling > > > > > > > > > > > `bootsound` > > > > > > > > > > > sh: can't access tty; job control turned off > > > > > > > > > > > # warning `rild` uses 32-bit capabilities (legacy support > > > > > > > > > > > in use) > > > > > > > > > > > > On Nov 11, 10:33 pm, NickDG <[email protected]> > > > > > > > > > > > wrote: > > > > > > > > > > > > > Hey Alex, > > > > > > > > > > > > > Thanks for the kernel. I tried and successfully got it > > > > > > > > > > > > to boot. > > > > > > > > > > > > > It worked with 1944. I used the following settings > > > > > > > > > > > > > root=/dev/mmcblk0p2 mem=64m rootdelay=1 init=/init > > > > > > > > > > > > > I get a kernel panic when it tried to execute init. > > > > > > > > > > > > Permissions look > > > > > > > > > > > > right. hmmm... > > > > > > > > > > > > > I've been keeping my eye on the Centro topic at > > > > > > > > > > > > Hackndev. Sorry I > > > > > > > > > > > > haven't posted in there yet! > > > > > > > > > > > > > - Nick > > > > > > > > > > > > > On Nov 11, 4:05 pm, Alex Osborne <[email protected]> wrote: > > > > > > > > > > > > > > NickDG wrote: > > > > > > > > > > > > > > Trying to get the Centro to the boot screen too. > > > > > > > > > > > > > > It needs to catchup > > > > > > > > > > > > > > to our progress with the 650. :) > > > > > > > > > > > > > > Nick, have you tried my kernel build with Centro > > > > > > > > > > > > > support compiled in? > > > > > > > > > > > > > Here's an android patched kernel that should work on > > > > > > > > > > > > > the 650, 680, > > > > > > > > > > > > > Centro and may work to some extent on the LifeDrive, > > > > > > > > > > > > > TX, T|T5, T|C and > > > > > > > > > > > > > Zire 72 machines as well. I've only tested it on the > > > > > > > > > > > > > 650 and 680 though. > > ... > > read more >> --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
