Hi All,
I tried to run logcat in my platform, it shows
# logcat
Unable to open log device '/dev/log/main': No such file or directory
Seems that it can't find the correct device node. I tried to trace the
source code of logcat and the logger driver.
I found the logcat try to open /dev/log/main as
It is most likely that you do not have the Android device drivers
enabled in your kernel. You really need them to be present. Another
possibility is you are using a newer kernel which places devices in a
different location in the /sys tree. In that case, you'll need to add an
option to your .c
Hi Rupesh,
I have downloaded the android file system & uImage released by you from the
following link.
http://embdroid.homeftp.net/ANDROID.tar.bz2
So i want to know Is this sufficient to see android running on this board ??
My doubt is when we build android on host system (Ubuntu Desktop ) we
i
Thanks Anders,
this was actually a near-hardware issue. Now, we were able to show off
Sean's and the others great work to Mike Jennings from the Android
team right now mentioning the FreeRunner port it in his talk on
Android @Oredev!
Keep it up!
/peter
http://www.oredev.se - Be there or be gone
http://blog.jayway.com/2008/11/21/android-on-the-freerunner/
/peter
http://www.oredev.se - Be there or be gone.
GTalk:neubauer.peter
Skypepeter.neubauer
ICQ18762544
Phone +46704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter http://twitter.c
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
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#s
