Re: [android-porting] Kernel panic - not syncing: Attempted to kill init!

2010-06-27 Thread Ashwin Bihari
You want "init=/init" in your bootargs..and you can use "rootwait" instead of "rootdelay=3".. Regards -- Ashwin On Sun, Jun 27, 2010 at 2:54 AM, Ranganath s wrote: > Hi, >   I got it my previous kernel panic problem solved. Now i am able to mount > till rootfs but after that i am again running

[android-porting] Absolute pointing HID device on Android-x86

2010-06-27 Thread Henk Kok
Dear group, I am part of a team that is developing a pointing device which we want to get to work on Android-x86. Actually, Android seems to be the first linux flavour that will allow our full-blown version to function. We happen to have a rather elaborate HID descriptor, which under Windows will

[android-porting] Porting to device without Back and Menu Button

2010-06-27 Thread xift
Hi, I am currently porting Eclair to a device without Back and Menu button. Android 1.5 was running on that device before. The vendor had some pretty neat software replacement for these buttons. How to Implement such a replacement? I already searched this group but appearently every Android device

Re: [android-porting] Kernel panic - not syncing: Attempted to kill init!

2010-06-27 Thread Subramani Venkatesh
Hi Ranganath, There are some changes required when yuou try SD/MMC card as file system 1. copy entire out/target/product//root to your sd card 2. copy entire out/target/product//system your sd card /system directory created by root 3. Modify your init.rc file to avoid mounting again system by yaff

Re: [android-porting] Absolute pointing HID device on Android-x86

2010-06-27 Thread Subramani Venkatesh
Hi, On Android platform, keyinput events are read by EventHub.cpp code which opens new input device and record's keyevents into a queue. you might have to check the code in the path given below for more information, there are so much define.. framework/base/core/libs/ui/Eventhub.cpp framework/base/

Re: [android-porting] Absolute pointing HID device on Android-x86

2010-06-27 Thread Dianne Hackborn
Also "absolute device that needs a pointer" is not a concept the Android platform understands. It assumes that an absolute device is a touch screen, and interprets it appropriately. You will need to modify the window manager's low-level input code in KeyInputQueue.java to interpret your devices c

[android-porting] Re: froyo weird timeouts?

2010-06-27 Thread Alexey Roslyakov
Hello, we've fixed problem. For people found this in search: Subject: [PATCH] Fix for race condition in MountService and NativeDaemonConnector. NativeDaemonConnector calls onDaemonConnected() callback function. In case of MountService callback function calls mConnector.doListCommand, and excepti