One thing is, I can't find the essential runtime process in the emulator neither.
When I start the emulator and run $./adb shell $ps I can see following active processes My question now is: Which process is the one to start up Android? On Nov 30, 3:15 pm, Stefan <sgo...@dh-electronics.de> wrote: > Hi alltogether, > > I use a 2.6.33 Kernel for a i.mx cpu. I've patched the files and > drivers described > in :http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Porting... > > Afterwards I set the kernel config as recommended > inhttp://android.git.kernel.org/?p=kernel/common.git;a=blob_plain;f=Doc... > > Then I got the system.img, ramdisk.img and userdata.img as described > here:http://elinux.org/Android_on_OMAPfrom the emulator > > Now I want get Android started but some files are missing: > > device/system/bin/dbus-daemon is missung > device/system/bin/runtime is missing > device/system/bin/logd is missing > > and last but not least > > device/system/bin/usbd is missing. > > When I tried to follow the instructions formhttp://elinux.org/Android_on_OMAP > the problem is: dbus-daemon and runtime is unknown. > > Now my question: > May I use the dbus-daemon from my standart system? > Where do I get / How can I build the runtime routine? > > These questions may seem for you experienced developers > maybe a bit stupid but I hope some of you can help me. > > With best regards, > > Stefan -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
