ubuntu-phone team mailing list archive

["leon lee" <llrraa@xxxxxx>]

hi folks. I have good news and very bad news.
Good news is that I have fixed the adbd and /system issue.

1. to fix /system issue, Specify fstype when mounting /system in ramdisk.img\scripts\touch
    mount /dev/mtdblock0 /system
=>      mount -t yaffs2 /dev/mtdblock0 /system   

2. To fix adbd, just delete /ubuntu/var/lib/lxc/android/pre-start.d/10-no-adbd in the sdcard.img
phablet@ubuntu-phablet:/var/lib/lxc/android/pre-start.d$ ls -l
total 16
-rwxr-xr-x 1 root root 213 Sep 17 19:05 10-no-adbd
-rwxr-xr-x 1 root root 145 Sep 12 21:05 15-no-uchroot
-rwxr-xr-x 1 root root  75 Sep 12 21:05 25-process-overrides
-rwxr-xr-x 1 root root 156 Sep 12 21:05 30-no-surface-flinger
phablet@ubuntu-phablet:/var/lib/lxc/android/pre-start.d$ cat 10-no-adbd
#!/bin/sh

# Make sure adbd is not started automatically
#sed -i 's/setprop persist.sys.usb.config adb$/setprop persist.sys.usb.config ""/
#' $LXC_ROOTFS_PATH/init.rc

# Disable adbd
rm $LXC_ROOTFS_PATH/sbin/adbd

very bad news:
After fixing the issue, I try direct_sf_test, and get the same bad result:
root@android:/system/bin # ./direct_sf_test                                    
Could not acquire surface control object during surface creationProblem creating surface ... aborting now.

I think the code is also not clean, which leads to the surfaceflinger issue. We need to look for some clean code to fix this.
The attached is the log for your reference.

Attachment: flipped-system adbd ok sf not ok-131006.log
Description: Binary data