[MANUP456]

Looking foward to a full working product.

[wyrm]

Hi androidezx,

I am looking at your code and I have some comments:

1. android-a1200-pcap.patch replace all ezx_pcap_write register writes with just a 0 write to REG_INT_SEL. Writing values to registers without knowing their meaning is bad and can harm your phone (seriouslly!). I marked this Alex Zhang contributions long ago when he contributed this code to us with the /* wrong */ comments and there was a good reason for that.

2. android-touchscreen.patch Also not a good idea. You cant just enforce the raw TS samples to the range accepted by android. You have to do filtering and calibration. You can write an userspace daemon for this (or use tslib, altough i dont know if you can use it with android), that outputs to a Uinput device file, so android can read correct data from /dev/input/whatever.

3. Consider updating your OpenEZX patchset to our git latest version. A lot of stuff have changed latelly, and this is the code which will be submitted to mainline linux. (not to mention some cool new features).

4. the BP stuff. The trick here is that once put on flash mode (when you enter the bootloader) you cant put BP to work again without a power cycle. So, to get BP working, you have to flash a secondary bootloader on your phone, look for gen-blob on my people.openezx.org home page. You will have to flash it to the kernel partition on your phone, and everything will be much easier

[jorgesmm]

I got Android running on my a780!

Thanks to androidezx for his help .

I've tested Android with:
- androidezx patchset and rootfs.
- e680 and a780 kernels/modules.
- configuring a780 keycodes.
- Adding ApiDemos.apk (you can see for example OpenGL demos ).

@androidezx. I don't know why, but the red ciclon only appears on screen if I telnet into the phone and write something with my PC keyboard. It sounds very strange but I've done many tests and if I don't telnet into the phone and don't press some keys, then the red ciclon doesn't show up or it lasts many seconds.

I've also tested it with gen_boot (many thanks to wyrm) but my phone is switched off after a minute. I have the same problem with other kernels and rootfs like Openmoko or Qtopia.
@wyrm: do you know why? If I do the same thing with boot_usb everything goes fine (as you can see in the video).

@wyrm, For your info, I've installed dual boot, and the second "kernel" is flashed with gen_boot, so this way, I can start 2.4 kernel without transflah card.

I agree with wyrm, it good be nice to use latest patches.

@androidezx I can try to help you with a780 although I don't have enough C/Linux skills to make patches

I've uploaded a video on YouTube:

[ame="http://www.youtube.com/watch?v=ntycTJosBHA"]YouTube - Android on a780[/ame]

[wyrm]

Originally Posted by jorgesmm

I've also tested it with gen_boot (many thanks to wyrm) but my phone is switched off after a minute. I have the same problem with other kernels and rootfs like Openmoko or Qtopia.
@wyrm: do you know why? If I do the same thing with boot_usb everything goes fine (as you can see in the video).

The phone switch off is a good signal it means that BP was waiting for AP to start communication, as AP doesnt, BP asked the power-off. Sort of a watchdog.

With boot_usb the bootloader puts the BP on flashmode, in this case the watchdog is not active.

To stop the watchdog, simply open() all /dev/mux* devices early at boot (before loading android). This is enough to keep the phone on. (and to talk with bp; cat /dev/mux<i> and you will see some nice modem messages).

Originally Posted by jorgesmm

@wyrm, For your info, I've installed dual boot, and the second "kernel" is flashed with gen_boot, so this way, I can start 2.4 kernel without transflah card.

Good idea, altough it propably slows down a lot the sartup of your phone.

I will change gen-blob to load the default kernel from flash instead of the mmc to allow use without a card. Thanks for the idea.

[jorgesmm]

@wyrm

I've done some tests but still happens the same.
I've executed cat /dev/mux*& and this is the only thing Ive seen:

+MBAN: Copyright 2000-2002 Motorola, Inc.
+CIEV: 1,0

I've also tested with OpenMoko and Qtopia (altough both rootfs use ezxd and I think it opens all /dev/mux, ins't it?).

What else can I do?

[honking]

Can anybody port android on rokr E2?

[androidezx]

Originally Posted by wyrm

Hi androidezx,

I am looking at your code and I have some comments:

1. android-a1200-pcap.patch replace all ezx_pcap_write register writes with just a 0 write to REG_INT_SEL. Writing values to registers without knowing their meaning is bad and can harm your phone (seriouslly!). I marked this Alex Zhang contributions long ago when he contributed this code to us with the /* wrong */ comments and there was a good reason for that.

Wyrm: Thanks for your advise! I will avoid it as the following code change.

2. android-touchscreen.patch Also not a good idea. You cant just enforce the raw TS samples to the range accepted by android. You have to do filtering and calibration. You can write an userspace daemon for this (or use tslib, altough i dont know if you can use it with android), that outputs to a Uinput device file, so android can read correct data from /dev/input/whatever.

Wyrm: You are right. The right way is that filtering/calibration should be done before writing touch drive datat to /dev/input/event1. But Android file system reads raw x/y coordination info and pressure info from /dev/input/event1. There is some difficulty in calibration. Hope that someone finish this task. Here I just do rough calibration for demo purpose.

3. Consider updating your OpenEZX patchset to our git latest version. A lot of stuff have changed latelly, and this is the code which will be submitted to mainline linux. (not to mention some cool new features).

Wyrm: Could you tell me where I can get this latest git version patchset? Thanks!

4. the BP stuff. The trick here is that once put on flash mode (when you enter the bootloader) you cant put BP to work again without a power cycle. So, to get BP working, you have to flash a secondary bootloader on your phone, look for gen-blob on my people.openezx.org home page. You will have to flash it to the kernel partition on your phone, and everything will be much easier

Wrym: I saw there was one gen2bp.patch under people.openezx.org/wrym. I want to know whether it is the source of gen-blob (including A1200) which was located in people.openezx.org/wrym/gen-blob. Thanks

[wyrm]

no, it is not.
gen-blob is on svn.openezx.org/trunk/src/blob/gen-blob.

The latest git patchset is on git://git.openezx.org/openezx.git please note that some patches are still not on this version, this is the case with ts0710mux driver, so you will have to port it from the svn.openezx.org patchset.

[androidezx]

Finally, let keypad work on Android (tested with A1200) fully. Original a1200 keypad matrix code swapped unexpected. Now I transform this keypad code matric from 6*5 to 5*6 and keypad interrupt can be received and keycode event can be sent to /dev/input/event1 correctly.

Another infor for your reference: Android uses /system/usr/keylayout/qwerty.kl to map raw keypad event to internal android key event. You can get internal android key event code from Emulator. Here is what I got from emulator.

Home key: 0x66 (102)
Menu key: 0xE5 (229)
Back key: 0x9E (15

Five direction navigation key:
Up key: 0x67 (103)
Down key: 0x6C (10
Left key: 0x69 (105)
Right key: 0x6A (106)
Center key: 0xE8 (232)

Call (Send) key: 0xE7 (231)
Hangup(End) key: 0x6B(107)

Certainly, we cannot send these key event to android application. Instead, we should send raw key event to android application from keypad driver, then android application received these raw key events and mapped them using qwerty.kl. For example, if we want to specify one key (like Camera key of A1200) as Call (Send) key, we can get this keyevent code of Camera (in my testing, I assigned 231 to Camera key). Then do mapping in qwerty.kl via specifying "key 231 CALL WAKE_DROPPED" is ok. In other words, we must map our keyevent code to internal android keyevent name (like CALL in this example).

The below is the mapping between keyevent name used in qwerty.kl and real keyevent android required:

Keyevent Name in qwerty.kl Android key
HOME Home key
SOFT_LEFT Menu

DPAD_UP Up key:
DPAD_DOWN Down key
DPAD_LEFT Left key
DPAD_RIGHT Right key
DPAD_CENTER Center key

CALL Call (Send) key
ENDCALL Hangup(End) key

[androidezx]

Audio still not work on A1200 Android. (I have no more time to focus on it. Currently, busy working on A1200 BP bring-up).

Wyrm,
Does audio work on A1200 with latest openezx git patch?

Thanks!
Androidezx