hi, >Why come the other Android own hardware-services without this? since its mokoid demo library, no other app or service required/loaded it.
a library should be loaded (either prelinked or run time when needed) when a process is running., so as to use library calls. for eg, take mediaserver launched during bootup,. it already got preloaded libraries, but further overlay/omx libraries will be loaded while video/audio is playing., PS. log /mnt/sdcard/v/1080i # /mnt/sdcard/v/1080i # ps | grep mediaserver 1406 1013 0:00 /system/bin/mediaserver 1741 0 0:00 grep mediaserver /mnt/sdcard/v/1080i # /mnt/sdcard/v/1080i # cat /proc/1406/maps 00008000-00009000 r-xp 00000000 b3:12 56729 /system/bin/mediaserver 00009000-0000a000 rwxp 00001000 b3:12 56729 /system/bin/mediaserver 0000a000-00046000 rwxp 00000000 00:00 0 [heap] 10000000-10001000 ---p 00000000 00:00 0 10001000-10100000 rwxp 00000000 00:00 0 40000000-40008000 r-xs 00000000 00:04 2209 /dev/ashmem/system_properties (deleted) 40008000-40009000 r-xp 00000000 00:00 0 40009000-40107000 r-xp 00000000 00:0d 2073 /dev/binder 40107000-40108000 ---p 00000000 00:00 0 [SNIP removed] afa00000-afa03000 r-xp 00000000 b3:12 18549 /system/lib/liblog.so afa03000-afa04000 rwxp 00003000 b3:12 18549 /system/lib/liblog.so afb00000-afb16000 r-xp 00000000 b3:12 18525 /system/lib/libm.so afb16000-afb17000 rwxp 00016000 b3:12 18525 /system/lib/libm.so afc00000-afc01000 r-xp 00000000 b3:12 18491 /system/lib/libstdc++.so afc01000-afc02000 rwxp 00001000 b3:12 18491 /system/lib/libstdc++.so afd00000-afd41000 r-xp 00000000 b3:12 18532 /system/lib/libc.so afd41000-afd44000 rwxp 00041000 b3:12 18532 /system/lib/libc.so afd44000-afd4f000 rwxp 00000000 00:00 0 b0001000-b000c000 r-xp 00001000 b3:12 56758 /system/bin/linker b000c000-b000d000 rwxp 0000c000 b3:12 56758 /system/bin/linker b000d000-b0016000 rwxp 00000000 00:00 0 be8c7000-be8e8000 rwxp 00000000 00:00 0 [stack] /mnt/sdcard/v/1080i # Also check #MYDROID/build/core/prelink-linux-arm.map for prelinked system wide libraries to avoid loading time., > Which is the offical way to integrate new Hardware into the HAL? no guidleines as such., the blog explains neat steps. you can refer "platform/hardware/**" under android projects. sample HAL layers - http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git;a=tree;h=refs/heads/gingerbread (got HAL layer implementation for camera/alsa/overlay/BT/etc) On Tue, Jan 18, 2011 at 6:18 PM, Dudero <[email protected]> wrote: > Hallo, > > I found a tutorial which explains the Android HAL by an LED-example: > (found on: http://blog.csdn.net/hongtao_liu/archive/2010/12/07/6060734.aspx) > > LED-Manager->LED-Service->LED-HAL->LED-Kernel-Driver > > My question is now: > > why does the java-service load this shared library: > > static{ > System.load("/system/lib/libmokoid_runtime.so"); > } > > Why come the other Android own hardware-services without this? > Which is the offical way to integrate new Hardware into the HAL? > > > Greetz dudero > > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-porting > -- Regards, Deva www.bittoggler.com -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
