Hi Andrew,

Thanks very much for the great work.

Now i am trying to port AOSP 4.4.4 (KitKat) for the BBB by using your repo 
manifest XML file. I built the U-boot, Kernel Successfully and also created 
the Filesystem.  But the problem is after putting all the built images into 
the microSD card, while booting i am getting some errors. i think it is not 
booting upto the android level, as it is getting stuck somewhere else. 
please take a look at the errors: 

[    2.847248]   #0: TI BeagleBone Black
[    3.559459] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data 
mode. Opts: (null)
[    3.568018] VFS: Mounted root (ext4 filesystem) on device 179:2.
[    3.575446] devtmpfs: mounted
[    3.578863] Freeing init memory: 244K
[    4.602721] init (1): /proc/1/oom_adj is deprecated, please use 
/proc/1/oom_score_adj instead.
[    4.705862] init: /dev/hw_random not found
[    4.710863] init: cannot open '/initlogo.rle'
[    4.823625] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data 
mode. Opts: nomblk_io_submit,errors=panic
[    4.862816] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    4.886477] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    4.893231] init: /dev/hw_random not found
[    4.923083] init: cannot find '/system/bin/sgx/rc.pvr', disabling 'pvr'
[    4.934643] init: cannot find '/system/bin/rild', disabling 'ril-daemon'
[    4.948132] healthd: wakealarm_init: timerfd_create failed
[    4.958423] healthd: No charger supplies found
[    4.967361] init: cannot find '/system/etc/install-recovery.sh', 
disabling 'flash_recovery'
[    4.979856] healthd: BatteryStatusPath not found
[    4.989605] healthd: BatteryHealthPath not found
[    4.998759] init: property 'sys.powerctl' doesn't exist while expanding 
'${sys.powerctl}'
[    5.012524] healthd: BatteryPresentPath not found
[    5.018248] healthd: BatteryCapacityPath not found
[    5.023926] init: powerctl: cannot expand '${sys.powerctl}'
[    5.030486] healthd: BatteryVoltagePath not found
[    5.035933] init: property 'sys.sysctl.extra_free_kbytes' doesn't exist 
while expanding '${sys.sysctl.extra_free_kbytes}'
[    5.047582] healthd: BatteryTemperaturePath not found
[    5.053002] healthd: BatteryTechnologyPath not found
[    5.058308] init: cannot expand '${sys.sysctl.extra_free_kbytes}' while 
writing to '/proc/sys/vm/extra_free_kbytes'
[    5.069792] binder: 91:91 transaction failed 29189, size 0-0
[    5.076145] init: property 'sys.sysctl.tcp_def_init_rwnd' doesn't exist 
while expanding '${sys.sysctl.tcp_def_init_rwnd}'
[    5.088106] init: cannot expand '${sys.sysctl.tcp_def_init_rwnd}' while 
writing to '/proc/sys/net/ipv4/tcp_default_init_rwnd'
*shell@beagleboneblack:/ $*

I am expecting *root@android* over here, whereas i am getting 
*shell@beagleboneblack* in this case

Could you please help me out on this. Expecting a quick response from your 
end..


After 
On Sunday, 28 September 2014 20:44:24 UTC+5:30, Andrew Henderson wrote:
>
> Hello all. I have released a new port of Android for the BBB.  This 
> version uses AOSP 4.4.4 (KitKat) and the 3.8 Linux kernel. I have made 
> build instructions and a pre-made image available at 
> http://www.bbbandroid.org.  I use a combination of AOSP repos and Rowboat 
> build scripts, and I have a few custom repos for the kernel, bootloader, 
> and additional "external" tools (such as i2c-tools).  You can view the repo 
> manifest XML file for the project here:
>
>
> https://github.com/hendersa/bbbandroid-manifest/blob/master/bbbandroid-aosp-4.4.4_r1-3.8.xml
>
> Because this Android image uses the 3.8 kernel, you should be able to just 
> plug in your capes and go without any hassle:
>
> Built-in HDMI cape:
> http://i.imgur.com/q4AZQ95.jpg
>
> 4D Systems LCD capes:
> 4DCAPE-43T: http://i.imgur.com/6qHmgqX.jpg
> 4DCAPE-70T: http://i.imgur.com/UZLG7Or.jpg
>
> CircuitCo LCD capes:
> LCD3: http://i.imgur.com/LC7SrBB.jpg 
> LCD4: http://i.imgur.com/1xBQ8R6.jpg
> LCD7: http://i.imgur.com/vxoqROE.jpg
>
> Andrew
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to