Messages

1

Android / Porting M5rc14 To Real Hardware

« on: February 21, 2008, 10:12:46 pm »

Did you create a new kernel with latest Google patches applied?
If not, then don't bother to try, it won't work on the kernel used in the previous release, since they made some major changes.

Ya. I've updated to newest kernel. Google do minor modify on new kernel. The major change is the binder driver.

2

Android / Porting M5rc14 To Real Hardware

« on: February 21, 2008, 10:04:20 pm »

I've tried copy a binary to /dev/graphics/fb0, and it can work. My framebuffer driver works well
But Android still not print something on the screem. It semms google make some  modification on
SufaceFlinger serives.
As I trace the system bootup, it uses mmap to map /dev/graphics/fb0 to memory.

how did you copy it?

you need to do "cp -prd /dev/XXX /dev/graphics/" to copy the device, or, better yet, use "mknod" instead!

I use android's original init, and it creates device node automatically; /dev/graphics/fb0 (29, 0) is alreadly there
when system boot-up.
I mean I copy a binary image into the fb device, and there's something shown on screen
And I also use mmap() to map the fb device, write something, and it works.
My framebuffer driver seems works fine.

3

Android / Porting M5rc14 To Real Hardware

« on: February 21, 2008, 04:15:09 am »

2). There's nothing appear on the screen. (screen is turned to black,
it doesn't happen on previous version, too)

Same for Angstrom Zaurus. Just blank screen, nothing displayed.

I don't think this would work though, give a try to copy /dev/fb0 to /dev/graphics/fb0 and chmod 666. The emulator is working like that.

Android Zaurus: Confusing issue of Android m5_rc14
http://androidzaurus.seesaa.net/article/84934031.html

I've tried copy a binary to /dev/graphics/fb0, and it can work. My framebuffer driver works well
But Android still not print something on the screem. It semms google make some  modification on
SufaceFlinger serives.
As I trace the system bootup, it uses mmap to map /dev/graphics/fb0 to memory.

BTW, the boot very slow problem is solved, it's because my flash driver I/O thread's priority is too low.
Now system can boot successfully, but still have nothing on screen

4

Android / Porting M5rc14 To Real Hardware

« on: February 18, 2008, 10:38:28 pm »

Hi everyone:
Does anyone can help me? Thanks in advance.
I'm now working on porting m5rc14 to our platform.
I meet 2 problems:

1) when system starts, console seem almost hangs. and process
system_server
occupies 99% of CPU time.

This is my logcat:
W/AudioFlinger(  557): Using stubbed audio hardware. No sound will be
produced.
I/AudioFlinger(  557): AudioFlinger's main thread ready to run.
I/ServiceManager(  539): ServiceManager: addService(AudioFlinger,
0x133f8)
I/sysproc (  557): System server: starting Android runtime.
I/sysproc (  557): System server: starting Android services.
I/SystemServer(  557): Entered the Android system server!
I/sysproc (  557): System server: entering thread pool.
D/TouchDex(  557): TouchDex parent waiting for pid=580 (timeout=36.4s)
I/ServiceManager(  539): ServiceManager: unable to find service
activity
I/runtime (  539): Still waiting for activity manager...
I/ServiceManager(  539): ServiceManager: waiting for service activity
D/AudioFlinger(  557): Audio hardware entering standby
I/ServiceManager(  539): ServiceManager: unable to find service
activity
I/runtime (  539): Still waiting for activity manager...
I/ServiceManager(  539): ServiceManager: waiting for service activity
I/ServiceManager(  539): ServiceManager: unable to find service
activity
I/runtime (  539): Still waiting for activity manager...
I/ServiceManager(  539): ServiceManager: waiting for service activity
I/ServiceManager(  539): ServiceManager: unable to find service
activity
I/runtime (  539): Still waiting for activity manager...
I/ServiceManager(  539): ServiceManager: waiting for service activity
I/ServiceManager(  539): ServiceManager: unable to find service
activity
I/runtime (  539): Still waiting for activity manager...
I/ServiceManager(  539): ServiceManager: waiting for service activity
I/ServiceManager(  539): ServiceManager: unable to find service
activity
I/runtime (  539): Still waiting for activity manager...
I/ServiceManager(  539): ServiceManager: waiting for service activity
I/ServiceManager(  539): ServiceManager: unable to find service
activity
I/runtime (  539): Still waiting for activity manager...
I/ServiceManager(  539): ServiceManager: waiting for service activity
E/TouchDex(  557): timed out waiting for 580; kill(0) returns 0

It seems services don't respond to SeviceManager, it doesn't happen on
previous version

2). There's nothing appear on the screen. (screen is turned to black,
it doesn't happen on previous version, too)

m3rc37 system runs well on our platform with new released kernel.