[Touch Viva, MDA Basic ROM Development] MusikMonk:
Just thought I'll let you guys know where we stand right now.

Touchscreen is still not working :( I'm asking for help and ideas everywhere I can.

Buttons, however, are now working after some small modifications. So it's possible now to move around Android a bit.

If you want to try it yourself, obviously at your own risk, you'll need to be able to SSH to your phone (I'll provide an alternative way when I find out how to disable touchscreen calibration).

Here are the steps:

Download and install wing-linux-0.4pre3-rootfs.cab and wing-linux-0.4pre3-herald.cab from https://sourceforge.net/projects/wing-linux/files/Wing Linux Development/ , make sure to install to storage card not to main device.

Download the attached zImage.zip and extract it.

Replace the zImage under \storage card\linux with the one you just extracted.

Run haret from the previous folder or Wing-Linux from programs under start menu.

Click on run.

When prompted to enter partition sizes you can either leave it till it times out or click the centre button. Both ways will use default values.

Keep waiting till you get to the touchscreen calibration.

Connect the device to your computer via usb and connect via SSH (step 10 here: https://sourceforge.net/apps/trac/wing-linux/wiki/PartitionInstallation)

Through SSH, run startAndroid.

You can now disconnect the connection and wait till Android finishes booting.

When done reset the device to go back to windows.

If you did do that, please post about your experience.

You'll also need to know the keymapping:

DPAD works normally: Up, Down, Left, Right and Enter.

Volume up is mapped to menu button.

Volume down is mapped to cancel/back.

Green/Red buttons are mapped normally (notice that, by default, Red button puts the device in standby and that's not implemented yet. Press any key to get back to Android).

This is the status at the moment:

GSM is, to a good extent, working:

I can call out successfully and the mic seems to be working well.

When calling in, the call is directly disconnected but appears in the log.

I couldn't find a way to send a message (as I don't have an input method).

Receiving SMS was successful.

Haven't tried GPRS (same problem as sending SMS, no input to set up APN).

Bluetooth:

Won't turn on. Tried having it on from WM before running, the only thing that changed was that the blue led was still flashing on and off normally, Android still considers it off and scanning for bluetooth device from my laptop yields nothing.

Backlight:

It's on, but changing brightness from settings does nothing.

Buttons:

After the small modification to the code, except for the power button, everything is working.

LED:

Green led is flashig normally when device is on, and it stop when device enters standby.

Yellow led (events, charging) doesn't seem to work. Nothing changes when connected to pc or power and when havig unread SMS.

Blue led, as noted before, worked when bluetooth was turned on from WM before booting.

USB:

I can connect and SSH successfully, so yes it does work.

SD Card:

I can access my sd under /media/windows (via SSH), does this count as working? Under Android's settings, the SD card supposedly has 242MB of total space, with 156MB available (note that I'm using a 2GB card).

Real Time Clock:

Seems to be functional.

Framebuffer/Rotation:

I didn't know how to test this. The only option concerning rotation that I found was the "Switch orientation automatically when rotating phone" and the Opal doesn't have the hardware for that. However, I remember booting into a landscape Android one time during my initial testing, so I guess it might be considered as working?

Vibration:

Again, I'm not sure how to test this. Under settings all I found was "Vibrate phone for incoming calls" and that's obviously not gonna help, if checking that is supposed to make the device vibrate on messages as well, then it's not working.

Battery, WIFI, Camera, Audio:

Not implemented yet.