A20 building android and some issues

[dpenev]

Hello,

I am very new to Android.

I have A20-MICRO-4GB and trying to make it working with my 19'' LCD using HDMI interface

1. I decided to test using the Olimex original Android my board arrived with.
   After some resets and playing with the Search Home buttons on the board I got the Android lock desktop on my LCD. But If I drag the lock icon some application icons blink quickly on the screen and my LCD become dark. I have to reset the board to get the Android lock desktop again. Apparently something is not OK. I have reflashed the board with Olimex A20_android_422_TS_USB_UART_I2C_WIFI_LAN_HDMI_LCD_1024x600_release_3.img - same behavior. I have hooked terminal to UART0 for someone to refer:

-------------------
...
Starting kernel ...

[    3.466746] init: width = 1024
[    3.470199] init: height = 600
[    3.473607] init: s.st_size = 1536000
[    3.477707] init: logo match failed!fbsize = 2457600
[    3.738404] init: do_umount: /data
[    4.226058] init: do_umount: /cache
[    4.317670] init: dont need format /dev/block/UDISK
[    4.338051] init: do_umount: /databk
[    5.115678] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
[    5.779830] i2c i2c-1: Invalid 7-bit I2C address 0x00
[    6.016355] android_usb: already disabled
[    6.021540] init: using deprecated syntax for specifying property 'sys.usb.config', use ${name} instead
[    6.050935] init: using deprecated syntax for specifying property 'sys.usb.config', use ${name} instead
[   10.721061] init: sys_prop: permission denied uid:1003  name:service.bootanim.exit

ls
acct
cache
config
d
data
default.prop
dev
etc
init
init.goldfish.rc
init.rc
init.sun7i.rc
init.sun7i.usb.rc
init.trace.rc
init.usb.rc
initlogo.rle
mnt
nand.ko
proc
root
sbin
sdcard
sys
system
ueventd.goldfish.rc
ueventd.rc
ueventd.sun7i.rc
vendor
-------------------


2. I have read somewhere that I probably have to configure the display settings in the file script.bin. Do you think this will help? I have adb working. Where is the script.bin I have to modify?
         
3. I have decided to build the Android kernel and image.
I got under lichee bImage  u-boot.bin  uImage  zImage. So I think uboot and the kernel are OK. How can I put them on A20-MICRO-4GB?
For the Android image I got ./android4.2/out/target/product/olinuxino-a20/system.img. Is this the image I can load with Phoenix Suite?

Thanks in advance
Dimitar

[dpenev]

I got another thing which may be relevant to my "LCD gets dark issue"

I got logcat at the moment I am trying to unlock my Android board.
Anyone hitting V/TAG     ( 1697): bug 7643792: fitSystemWindows([0,19][0,0]) ?

I/SurfaceFlinger( 1125): GraphicBufferAlloc::createGraphicBuffer
I/SurfaceFlinger( 1125): GraphicBufferAlloc::createGraphicBuffer
D/audio_hw_primary( 1128): start_output_stream AUDIO_DEVICE_OUT_AUX_DIGITAL
D/audio_hw_primary( 1128): start_output_stream: card:1, port:0, rate:44100
V/alsa_pcm( 1128): pcm_open_req, playback card: 1, device: 0, req_rate: 44100
V/alsa_pcm( 1128): pcm_open_req try rate: 44100
V/alsa_pcm( 1128): pcm_open_req OK config->rate: 44100
D/PhoneStatusBar( 1781): disable: < expand icons alerts ticker system_info BACK HOME recent* CLOCK search >
D/PhoneStatusBar( 1781): disable: < expand icons alerts ticker system_info back* home* recent clock* search >
W/AudioFlinger( 1128): write blocked for 375 msecs, 1 delayed writes, thread 0x41792108
V/TAG     ( 1697): bug 7643792: fitSystemWindows([0,19][0,0])
D/dalvikvm( 1697): GC_FOR_ALLOC freed 625K, 16% free 7015K/8332K, paused 148ms, total 150ms
D/dalvikvm( 1697): GC_FOR_ALLOC freed 401K, 16% free 7007K/8332K, paused 114ms, total 115ms

Dimitar

[dave-at-axon]

To edit the script.bin file you need to mount the nanda partition.

adb shell mkdir /mnt/sdcard/kernel

adb shell mount - the vfat /mnt/block/nanda /mnt/sdcard/kernel

You'll need the sunxi tools fex2bin and bin2fex to convert them.


For the build if you run extract-bsp from the android4.2 this will copy the image files to the correct place for pack. Run pack from the android4.2 directory. Most likely though it will fail as the board directory in the tools/pack under lichee directory is missing. The name used is in the packages directory.

I am working on a Web page for this to go up this week. It's not complete as the build still crashes in surfaceflinger but it will help to document what I have found so far.

[dpenev]

Thanks dave-at-axon,

I have A20-MICRO-4GB and I don't use sdcard.
Do you happen to know the location of script.bin in the nand flash?

dimitar

[dave-at-axon]

I believe that the partitions should still be the same on the SDCARD.

Try mounting the NANDA partition as I have shown before.

By the way, another user on the forum and myself have been struggling to get SCRIPT.BIN changes to take effect. As of now we can modify the file and save it back to the partition and then reboot but for some strange reason, none of the changes are being detected. We've tried both NAND and SD and both do the same.

Hope this can work for you?

[dave-at-axon]

Actually, the boot partition on SD should be named sdc1.

[tonsal]

Hi.

I found this on the forum. It seems that the script.bin is in /dev/nanb.
I don't know if this is correct, but I hope it helps.
https://www.olimex.com/forum/index.php?topic=1809.msg8249#msg8249

I hope you get it working and create the "tutorial" for rest of us. Eagerly waiting.

[dave-at-axon]

It could well be but nandb is a raw format partition so you can't mount or change it.

[dave-at-axon]

I've posted what I found here along with instructions on how to build Android for the A20 even though it does not work once the image is loaded

http://axonjakarta.wordpress.com

[dpenev]

Hello,

I confirm that it seems the update of screen resolution in script.bin seems to not affect my display issue.

adb shell mkdir /boot
adb shell mount -t vfat /dev/block/nanda /boot
adb pull /boot/script.bin
fexc -I bin -O fex script.bin script.fex

modify script.fex

fexc -I fex -O bin script.fex script-new.bin
adb push script-new.bin /boot/script.bin
adb shell sync
adb shell umount /boot

I am thinking to get LCD monitor or display.

Olimex sale:

A20-LCD15.6 - No touch screen?
Is the standard Android image from Olimex support this LCD out of a box?

A13-LCD10TS
Is this sported by A20-OLinuXino-MICRO-4GB board and is it working with the Olimex Android image?

Dimitar

[olimex]

Dimitar in the wiki there are only 7" and 10" LCD images for Android
it may or may not be possible to make image for the 15.6" so better use HDMI TV if you want bigger sizes displays under Android

15.6" LCD have no touchscreen

[dpenev]

Hi Olimex,

If I decide that 10'' is OK for me can I go with A13-LCD10TS ?
Is it supported by your Android image A20_android_422_TS_USB_UART_I2C_WIFI_LAN_HDMI_LCD_1024x600_release_3.7z
And will it run OK on A20-OLinuXino-MICRO-4GB hardware?

Will the touchscreen panel also functioning on that platform?

Thanks
Dimitar