[Android Head-Units] donaldta:
Alright, it looks like WinCa.service that starts up and loads the phone app but that's it.

I/ActivityManager( 1279): Start proc [COLOR="Red"]com.winca.service[/COLOR] for added application com.winca.service: pid=[COLOR="Red"]1421[/COLOR] uid=1000 gids={3002, 3001, 1015, 3003}
E/PhonePolicy( [COLOR="Red"]1421[/COLOR]): Could not preload class for phone policy: com.android.internal.policy.impl.PhoneWindow$ContextMenuCallback
D/dalvikvm( [COLOR="Red"]1421[/COLOR]): GC_FOR_ALLOC freed 162K, 3% free 7523K/7751K, paused 54ms
I/dalvikvm-heap( [COLOR="Red"]1421[/COLOR]): Grow heap (frag case) to 8.670MB for 1344016-byte allocation
D/dalvikvm( [COLOR="Red"]1421[/COLOR]): GC_FOR_ALLOC freed <1K, 3% free 8835K/9095K, paused 5ms
D/dalvikvm( [COLOR="Red"]1421[/COLOR]): GC_CONCURRENT freed 1K, 3% free 8833K/9095K, paused 1ms+1ms
D/dalvikvm( [COLOR="Red"]1421[/COLOR]): GC_FOR_ALLOC freed <1K, 3% free 8834K/9095K, paused 25ms
I/dalvikvm-heap( [COLOR="Red"]1421[/COLOR]): Grow heap (frag case) to 11.552MB for 3024016-byte allocation
D/dalvikvm( [COLOR="Red"]1421[/COLOR]): GC_FOR_ALLOC freed 0K, 3% free 11787K/12103K, paused 28ms
I/BootReceiver( [COLOR="Red"]1421[/COLOR]): ------------------------------BootReceiver action:android.intent.action.BOOT_COMPLETED

There were lots of apps that responded to the "Boot Complete" broadcast; however, the package I created wasn't one of them. :( It wasn't even listed anywhere in the logcat.

Actually, eStrongs altered their File Explorer a little bit. It no longer automagically remounts the file systems as needed. Now when you want to make any changes to the system file system you must hold down on the root explorer title option then select "Mount R/W" from the popup that appears when you let it go.

It sounds like to me that their OnKey listener(s) checks for both scancodes and keycodes. You're probably right with that theory of the double functions. We'll probably have to find single use scancodes in order to get it working appropriately.

---------- Post added at 05:53 PM ---------- Previous post was at 05:28 PM ----------

It might just be as well. By the looks of the logcat messages, the file names I provided are for the touchscreen. I don't believe that will work. They should probably be labeled, "mcu-keypad.kl" and "Vendor_0000_Product_0000.kl" respectively.

I/InputManager( 1279): Initializing input manager
I/InputManager( 1279): Starting input manager
D/EventHub( 1279): No input device configuration file found for device 'mcu-keypad'.
I/EventHub( 1279): New device: id=1, fd=90, path='/dev/input/event1', name='mcu-keypad', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=true
I/EventHub( 1279): New device: id=2, fd=97, path='/dev/input/event0', name='s3c_ts', classes=0x4, configuration='/system/usr/idc/s3c_ts.idc', keyLayout='', keyCharacterMap='', builtinKeyboard=false
E/EventHub( 1279): could not get driver version for /dev/input/mouse0, Not a typewriter
I/SystemServer( 1279): Input Method Service
W/InputManagerService( 1279): Couldn't create dir.: /data/system/inputmethod
E/EventHub( 1279): could not get driver version for /dev/input/mice, Not a typewriter
I/InputReader( 1279): Touch device 's3c_ts' could not query the properties of its associated display 0. The device will be inoperable until the display size becomes available.
I/InputReader( 1279): Device added: id=2, name='s3c_ts', sources=0x00001002
I/InputReader( 1279): Device added: id=0, name='mcu-keypad', sources=0x00000101
I/InputReader( 1279): Reconfiguring input devices. changes=0x00000004
I/InputReader( 1279): Device reconfigured: id=2, name='s3c_ts', surface size is now 800x480, mode is 1