Android System Programming Activity
Brought to you by:
shugaoye
Activity for Android System Programming
-
Android System Programming released /glmark2/glmark20171019.apk
-
Roger Ye posted a comment on discussion Chapter 11
There is one commit is missing. Please pull the latest code from my GitHub. The issue should be resolved.
-
Give me sometime. I will test it again.
-
Nanik posted a comment on discussion Chapter 11
It is using android-x86 branch
-
Even when the Android code is checked out from android-7.1.1_r4_ch11_aosp branch the same error happens The fbtest project is relying on header files that probably need to be included or need to be specified explicitly
-
Please checkout branch "android-x86". I need to check whether I mentioned this or not in the book.
-
Got issue when following step in Chapter 11 for compiling fbtest I/media/AOSPDrive/AndroidEmbeddedSystemChapter/bionic/libc/arch-x86/include -I/media/AOSPDrive/AndroidEmbeddedSystemChapter/bionic/libc/include -I/media/AOSPDrive/AndroidEmbeddedSystemChapter/bionic/libc/kernel/uapi -I/media/AOSPDrive/AndroidEmbeddedSystemChapter/bionic/libc/kernel/uapi/asm-x86 -o iplan2.o iplan2.c /media/AOSPDrive/AndroidEmbeddedSystemChapter/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.9/bin/x86_64-linux-android-gcc...
-
Fixed this issue due to some kind of permission issues. The solution is to copy the whole product/ directory from the Android /out folder to another drive or directory
-
What I mean is are you able to verify that NFS path "10.0.2.2:/AOSPDrive/AndroidEmbeddedSystemChapter/out/target/product" can work? If I want to verify it, I will install an ubuntu with NAT network connection only. Inside Ubuntu, I will test it using NFS mount like: $ sudo mount -t nfs 10.0.2.2:/AOSPDrive/AndroidEmbeddedSystemChapter/out/target/product /mnt/test If this can work, it means the NFS share setup has not problem in the host. Another difference is that, if there is only NAT connection,...
-
What I mean is are you able to verify that NFS path "10.0.2.2:/AOSPDrive/AndroidEmbeddedSystemChapter/out/target/product" can work? If I want to verify it, I will install an ubuntu with NAT network connection only. Inside Ubuntu, I will test it using NFS mount like: $ sudo mount -t nfs 10.0.2.2:/AOSPDrive/AndroidEmbeddedSystemChapter/out/target/product /mnt/test If this can work, it means the NFS share setup has not problem in the host. Another difference is that, if there is only NAT connection,...
-
Sorry what you mean by Set the NFS IP to 10.0.2.2
-
Create a new vm inside virtualbox and tried ROOT=10.0.2.2:/AOSPDrive/AndroidEmbeddedSystemChapter/out/target/product and event ROOT=10.0.2.15:/AOSPDrive/AndroidEmbeddedSystemChapter/out/target/product as the IP 10.0.2.15 is reported as the IP from DHCP by the kernel log below [ 10.060720] rtc_cmos rtc_cmos: setting system clock to 2017-05-17 01:08:58 UTC (1494983338) [ 10.382107] Sending DHCP requests ., OK [ 10.445036] IP-Config: Got DHCP answer from 10.0.2.2, my address is 10.0.2.15 [ 10.591700]...
-
Let's try to use NAT only. Can you help to verify two things? 1. Set the NFS IP to 10.0.2.2 2. Will you be able to on another virtual machine and try to mount NFS share 10.0.2.2::/media/AOSPDrive/AndroidEmbeddedSystemChapter/out/target/product If both are ok, we can debug further. Below is my configuration. label 4. NFS Installation - x86vbox menu x86vbox_install kernel x86vbox/kernel append ip=dhcp initrd=x86vbox/initrd.img root=/dev/nfs rw androidboot.hardware=x86vbox INSTALL=1 SRC=/x86vbox ROOT=10.0.2.2:/home/sgye/vol1/android-vbox/out/target/product...
-
Following content of pxelinux.cfg prompt 1 default menu.c32 timeout 100 label 1. NFS Installation (serial port) - x86vbox menu x86vbox_install_serial kernel kernel append ip=dhcp console=ttyS3,115200 initrd=initrd.img root=/dev/nfs rw androidboot.hardware=x86vbox INSTALL=1 DEBUG=2 SRC=/x86vbox ROOT=192.168.56.1:/AOSPDrive/AndroidEmbeddedSystemChapter/out/target/product nfsroot=192.168.56.1:/AOSPDrive/AndroidEmbeddedSystemChapter/out/target/product label 2. x86vbox (ROOT=/dev/sda1, serial port) menu...
-
Checked out android-7.1.1_r4_x86vbox_ch08_r1 from the github and able to start up Virtualbox and was able to boot up kernel but when it tried to get into Android it is stuck in the following line Detecting Android-x86...................................... seems like it cannot find the root for some reason. Following are the /etc/exports content nanik : /media/AOSPDrive/AndroidEmbeddedSystemChapter$ sudo exportfs /media/AOSPDrive/AndroidEmbeddedSystemChapter/out/target/product <world> nanik : /media/AOSPDrive/AndroidEmbeddedSystemChapter$...
-
Anonymous posted a comment on discussion Chapter 9
In section 'Booting to Recovery' there is a configuration label 5. x86vbox recovery (ROOT=/dev/sda2) menu x86vbox_recovery kernel x86vbox/kernel append ip=dhcp console=ttyS3,115200 initrd=x86vbox/ramdisk-recovery.img androidboot.hardware=x86vbox DEBUG=2 SRC=/android-x86vbox ROOT=/dev/sda2 however the ramdisk-recovery.img does not get produced during make process. Is there a separate make task that need to be executed as it's not mentioned in the chapter.
-
To make ramdisk-recovery.img, there are two ways to do it. You can simply remove $OUT/ramdisk-recovery.img and $OUT/recovery. After that, you build again. If you just want to do a quick test by modifyin the content $OUT/reocovery, you can generate ramdisk-recovery.img using the below command. ramdisk: $ $(MKBOOTFS) -d ${OUT}/system ${OUT}/recovery/root | minigzip > ${OUT}/ramdisk-recovery.img You can refer to this Makefile that I use to build individual targets. https://github.com/shugaoye/x86vb...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1
