Software

[DarkRedFlame]

CyanogenMod - Currently 60% - 70% done to a working port (Doesn't mean final)

What currently works:
COMPLETE Booting into Android
COMPLETE ADB commands via ADB
COMPLETE Touchscreen support (Multi-touch, 10 fingers)
COMPLETE Power, back/home and volume button layout
COMPLETE Bluetooth ( Fixed 9/24)
COMPLETE Softkeys
COMPLETE Sound
COMPLETE Accelerometer
COMPLETE LED (Confirmed in IRC)
COMPLETE Backlight (Confirmed in IRC)
90% Complete Wifi ( Still needs to be fixed for reconnecting to wifi, needs to be verified)
Partially Compass (Bugs need to be worked out)
Partially CPU/GPU Acceleration ( Both cores are enabled) (Video drivers need to be worked on)

What does not currently work:
Blank for now

Whats currently being worked on:
Light Sensor (Works in kernel, needs an interface written for android)
Fake SD card Mount
Power Management (Needs to be adapted to a supported android interface, having trouble with sleep)
Camera (Has video feedback VIA overlay, can't capture to disk) ( Work started 9/23)
Vibration (Needs to be adapted to a supported android interface)

Issues:
Sleep Issues for Wifi and Magnetometer
Airplane mode stays on once turned on, happens because the touchpad doesn't have a real radio interface layer.
Magnet (Touchstone Support) (Works and charges, but no event is raised to show you it's charging)


TouchDroid - Currently DEAD (More or less)

What currently works:
Booting into Android
ADB commands via ADB
Touchscreen support (Multi-touch, 10 fingers)
Power button and volume button layout

What does not currently work:
Camera
Bluetooth
Compass/Mag
Home button
Power Management (USB Charge Only)
Sound
Vibration
Being able to run Metal Gear Solid, the best PSX game ever made.

Whats currently being worked on:
Wifi


IRC Logs:
<@fattire> you can use it (wifi), but something called "combo scan" needs to be added to it to get it to rescan/reconnect if it drops.. also I think there may be some kernel issue w/it at the moment..

<@ciwrl> touchpad build may fu-bar usb partition
<@ciwrl> the lvm resize has the possibility of overwriting/corrupting the usb partition
(In response to the above)
<@FatTire> okay so basically, if I'm not mistaken the touchdroid instructions for resizing the partitions/logical volumes had you basically shrink the media one and then create a bunch of new android ones using the space left over.
<@FatTire> jonpry (or maybe it was rwhitby) observed that it's a much better practice to first resize the media vfat filesystem inside that logical volume BEFORE you resize the logical volume itself.
<@FatTire> so the order would be... (actually first shut off cryptfs which I don't think they did either)... then... resize the interior vfat file system for media, THEN shrink the media logical volume that surrounds it.
<@FatTire> otherwise you have a filesystem that thinks its larger than it is, basically.

<@ciwrl> they are already focusing on delivery mechanisms (ease of install)
<@ciwrl> we'll be doing the dual boot as well

<@dalingrin> the vibrator driver works but we need to adapt it to an interface that Android likes (needs a timed_gpio interface to work with Android)
<@dalingrin> same for the battery

[ReverendKJR]

That is the best "Not Working" list ever!

[xiVFINISHERVix]

Anything new? It's been a few days

[DarkRedFlame]

Anything new? It's been a few days

Just updated it with some new information I have received.