This is awesome, how would I go about adding custom apps or ones from app stores?
Thanks for sharing Andrew, This looks like a very interesting project.Can you elaborate further on how you were able to boot the Android 4.2.2 image on the BBB. From what I've been reading the arowboat guys have not yet got it working on the BBB.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/Yc8CdtU5MEs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Will you let us know when the instructions will be out? Was it hard to create? Overall it runs well, glad that Android can be supported on the black! Thanks
Thanks for the tutorial! I had one problem:When I started up the Bone, it went to a screen that said 'Automatically Logging In' with the beagleboard logo in the right handside. Android didn't boot up, and I don't know why. Did I do something wrong, or should I just wait?
OK I'll see if I can find the time this evening to run up your image on my board with the LCD4 installed and see what happens :)
Will report back once I've given it a go.
I realized that I didn't use step 8, so I did that. However, nothing happened. None of the User LEDs turned on, and I am not sure what is going on
btw: for 'some' of the capes to work fully, you need the patched
device-tree-compiler 'dtc', since I didn't see this mentioned in your
directions, i figured i'd better point it out, just in case..
Here's a quick script to build the patched dtc, till the '@' option
hits mainline dtc:
https://github.com/RobertCNelson/tools/blob/master/pkgs/dtc.sh
wget -c https://raw.github.com/RobertCNelson/tools/master/pkgs/dtc.sh
chmod +x dtc.sh
./dtc.sh
--
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...@googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/Yc8CdtU5MEs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
Sounds to me like the boot button works, otherwise pressing or not pressing the button would get you the same result. Have you looked at the sd socket to make sure all the pins are making contact? Have you tried booting anything else from sd? Have tried to see if you can mount the sd from uboot or at least see if it is visible? Have you formatted sd like the BBB wiki states?
I know that these are a lot of questions but they should help to isolate the problem.
-Wil
--
Hey Roy,
Can you create a backup .img of you sd and provide a download link. I would love to test that image on my BBB with several sd cards to see if it works.
-Wil
--
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/Yc8CdtU5MEs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
Okay, I've had a second go at it. I've tried every combinations of the following:
- 2 microSD cards: SanDisk 4GB HC Speed 2, and Kingston 8GB HC Speed 4
- 2 power supplies: 5V @ 2amps
- 2 BeagloneBone Blacks rev A5B
I flashed the image on the microSD cards using Win8 64bit w/ DiskImager per the instruction of the wiki: http://circuitco.com/support/index.php?title=AndroidI tried unplugging all other connections (USB, Ethernet, LCD Capes etc.) and many different combinations. I did notice that the ethernet port LEDS blink rapidly. Though the 4 user LEDS did not become solid and nothing happened.Unfortunately, after all this I was not able to boot the Android image by Andrew. I believe the issue lies in the Android image itself.
--
If/when you look at the LCD7?, can you take a picture and put it on
here? I want to see how it looks...
--
Thanks man. Resolution looks decent according to your video, so I'll probably get this screen.Are you planning to do any SD card partitioning so Android can recognize SD card space, as well as the Wifi tutorial soon?
--
ö<0>ð<0><0><0><0><0><0><0>
U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
mmc_send_cmd : timeout: No status update
reading u-boot.img
reading u-boot.img
U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)
I2C: ready
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net: <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot: 0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
micro SD card found
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
534 bytes read in 4 ms (129.9 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
Running uenvcmd ...
reading zImage
3320040 bytes read in 403 ms (7.9 MiB/s)
reading am335x-boneblack.dtb
24129 bytes read in 9 ms (2.6 MiB/s)
## Flattened Device Tree blob at 815f0000
Booting using the fdt blob at 0x815f0000
Using Device Tree in place at 815f0000, end 815f8e40
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.8.13-bone22 (notroot@ubuntu) (gcc version 4.7.3 20130328 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.04-20130415 - Linaro GCC 2013.04) ) #1 SMP Thu Jun 20 22:32:44 UTC 2013
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: Generic AM33XX (Flattened Device Tree), model: TI AM335x BeagleBone
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] AM335X ES1.0 (neon )
[ 0.000000] PERCPU: Embedded 9 pages/cpu @c0e2c000 s14080 r8192 d14592 u36864
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129792
[ 0.000000] Kernel command line: consoleblank=0 console=ttyO0,115200n8 androidboot.console=ttyO0 mem=512M root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait init=/init ip=off video=720x480-16@60 qemu=1 vt.global_cursor_default=0
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] __ex_table already sorted, skipping sort
[ 0.000000] allocated 1048576 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] Memory: 511MB = 511MB total
[ 0.000000] Memory: 507256k/507256k available, 17032k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc08d6580 (9018 kB)
[ 0.000000] .init : 0xc08d7000 - 0xc0920700 ( 294 kB)
[ 0.000000] .data : 0xc0922000 - 0xc09a4e00 ( 524 kB)
[ 0.000000] .bss : 0xc09a4e00 - 0xc0a1c180 ( 477 kB)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[ 0.000000] Total of 128 interrupts on 1 active controller
[ 0.000000] OMAP clockevent source: GPTIMER1 at 24000000 Hz
[ 0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[ 0.000000] OMAP clocksource: GPTIMER2 at 24000000 Hz
[ 0.000000] Console: colour dummy device 80x30
[ 0.000380] Calibrating delay loop... 363.67 BogoMIPS (lpj=354304)
[ 0.017385] pid_max: default: 32768 minimum: 301
[ 0.017636] Security Framework initialized
[ 0.017735] Mount-cache hash table entries: 512
[ 0.027617] Initializing cgroup subsys cpuacct
[ 0.027655] Initializing cgroup subsys memory
[ 0.027722] Initializing cgroup subsys blkio
[ 0.027875] CPU: Testing write buffer coherency: ok
[ 0.028468] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[ 0.028549] Setting up static identity map for 0x806166f0 - 0x80616748
[ 0.030251] Brought up 1 CPUs
[ 0.030278] SMP: Total of 1 processors activated (363.67 BogoMIPS).
[ 0.031699] devtmpfs: initialized
[ 0.097407] pinctrl core: initialized pinctrl subsystem
[ 0.097703] rstctl core: initialized rstctl subsystem
[ 0.098218] regulator-dummy: no parameters
[ 0.098762] NET: Registered protocol family 16
[ 0.099925] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.110117] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[ 0.110894] platform 49000000.edma: alias fck already exists
[ 0.110925] platform 49000000.edma: alias fck already exists
[ 0.110950] platform 49000000.edma: alias fck already exists
[ 0.112340] OMAP GPIO hardware version 0.1
[ 0.117160] gpio-rctrl rstctl.3: loaded OK
[ 0.122361] hw-breakpoint: debug architecture 0x4 unsupported.
[ 0.124517] cpsw.0: No hwaddr in dt. Using c8:a0:30:c4:c4:19 from efuse
[ 0.124550] cpsw.1: No hwaddr in dt. Using c8:a0:30:c4:c4:1b from efuse
[ 0.139272] bio: create slab <bio-0> at 0
[ 0.150945] edma-dma-enginstered
[ 0.518284] io scheduler cfq registered (default)
[ 0.520435] tps65217-bl tps65217-bl: no platform data provided
[ 0.520481] tps65217-bl: probe of tps65217-bl failed with error -22
[ 0.521332] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.524096] omap_uart 44e09000.serial: did not get pins for uart0 error: -19
[ 0.524437] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0
[ 1.249582] console [ttyO0] enabled
[ 1.254414] [drm] Initialized drm 1.1.0 20060810
[ 1.272866] brd: module loaded
[ 1.283117] loop: module loaded
[ 1.286586] at24 0-0050: 32768 byte 24c256 EEPROM, writable, 1 bytes/write
[ 1.293879] at24 1-0054: 32768 byte 24c256 EEPROM, writable, 1 bytes/write
[ 1.301156] at24 1-0055: 32768 byte 24c256 EEPROM, writable, 1 bytes/write
[ 1.308434] at24 1-0056: 32768 byte 24c256 EEPROM, writable, 1 bytes/write
[ 1.315709] at24 1-0057: 32768 byte 24c256 EEPROM, writable, 1 bytes/write
[ 1.329971] bone-capemgr bone_capemgr.8: Baseboard: 'A335BNLT,0A5A,1913BBBK2213'
[ 1.337763] bone-capemgr bone_capemgr.8: compatible-baseboard=ti,beaglebone-black
[ 1.376939] bone-capemgr bone_capemgr.8: slot #0: No cape found
[ 1.414047] bone-capemgr bone_capemgr.8: slot #1: No cape found
[ 1.451155] bone-capemgr bone_capemgr.8: slot #2: No cape found
[ 1.488265] bone-capemgr bone_capemgr.8: slot #3: No cape found
[ 1.494515] bone-capemgr bone_capemgr.8: slot #4: specific override
[ 1.501115] bone-capemgr bone_capemgr.8: bone: Using override eeprom data at slot 4
[ 1.509147] bone-capemgr bone_capemgr.8: slot #4: 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G'
[ 1.519286] bone-capemgr bone_capemgr.8: slot #5: specific override
[ 1.525882] bone-capemgr bone_capemgr.8: bone: Using override eeprom data at slot 5
[ 1.533918] bone-capemgr bone_capemgr.8: slot #5: 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI'
[ 1.543965] bone-capemgr bone_capemgr.8: slot #6: specific overri[ 67.712532] warning: `zygote' uses 32-bit capabilities (legacy support in use)
[ 100.036647] net eth0: initializing cpsw version 1.12 (0)
[ 100.044738] net eth0: phy found : id is : 0x7c0f1
[ 100.049753] libphy: PHY 4a101000.mdio:01 not found
[ 100.054792] net eth0: phy 4a101000.mdio:01 not found on slave 1
[ 100.068821] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 150.519662] init: sys_prop: permission denied uid:1003 name:service.bootanim.exit
[ 153.566758] binder: release 713:939 transaction 9916 out, still active
[ 153.910763] binder: 509:525 transaction failed 29189, size 300-0
[ 164.146733] binder: 823:942 transaction failed 29189, size 144-8
[ 164.153115] binder: send failed reply for transaction 9916, target dead
Hello all. I posted this information over at the Google+ group for BeagleBoard.org, but I wanted to post it here as well. I have Android running on the BBB using the Jellybean (4.2.2) source from arowboat.org and the Linux 3.8.13 kernel from my BeagleSNES project (www.beaglesnes.org). I just added the Android drivers (Drivers -> Staging Drivers -> Android) into the same kernel configuration that I use for BeagleSNES. This kernel is really just a stripped down configuration (a 1.9 meg zImage) using Robert Nelson's 3.8.x kernel source tree. Instead of using the GCC cross-compiler that comes in Rowboat's current prebuilt tools, I use the 3.7 GCC that comes with Robert's kernel tree to build the entire system. I also updated the u-boot to v2013.04.
Here is a video of it running: https://www.youtube.com/watch?v=yeSt1Y7FhEs
Here is the download of a working Android image that can be written onto a 4GB microSD card using "dd": http://icculus.org/~hendersa/BBB_JB_Android_3_8_13.img.bz2
There is no hardware accelerated video in this version, since SGX support isn't ready for the 3.8 kernel. To shut off hardware accelerated video, I pass "qemu=1" as a kernel command line argument in uEnv.txt and I add "debug.egl.hw=0" to the /system/build.prop file in the root file system. To get rid of that blinking cursor on the framebuffer (which I accidentally left on in the image that I made), add this to the uEnv.txt kernel command line arguments: "vt.global_cursor_default=0"
This build will be of interest to Android experimenters who want to use HDMI for audio and video output (rather than using an LCD cape) and who want to experiment with using the device tree. My kernel is pretty stripped down, so feel free to fetch Robert's latest kernel source for the 3.8.x branch and rebuild your own kernel to drop into the image that I have supplied. That way, you can include whatever drivers you would like in your kernel. Use a USB mouse (and a keyboard, too, if you want) to interact with the system.
Thanks, and enjoy!
Andrew
1. Android doesn't ask to be Google-activated. When I got my Android
phone, I couldn't use it until I signed in with my Google account. No
big deal, I don't really intend to lug it around. However...
2. I did manage to side-load the Google Play app, along with the GMail
app.
The real problem with this build is that it doesn't seem to support ADBdebugging. I've tried starting adbd from init.rc, but it looks like the miniUSB port is not detected at all. I will try to see if there are any hintsin the console log, but any ideas? The 'vanilla' rowboat build doessupport adbd, so it is definitely doable.
--
Andrew, thanks for this image, got it working after fiddling with the
video resolution. More precisely, I could *see* that it was working
when I found the right res. Here's what I found:
1. Android doesn't ask to be Google-activated. When I got my Android
phone, I couldn't use it until I signed in with my Google account. No
big deal, I don't really intend to lug it around. However...
2. I did manage to side-load the Google Play app, along with the GMail
app. They won't run however, probably because I hadn't activated the
device. (I'm supposed to supply a one-time device-specific password
but couldn't find anything in the Settings. I tried the Accounts item
under Settings, got email and one other that I don't remember at the
moment. I entered my Google credentials, and Android told me that I
needed a device-specific password (or something like that).
3. The browser hangs now and then and asks me whether I want to wait
or force-close.
4. The entire environment is slow, my mouse laggy. Wondering if my
monitor has anything to do with it. I've posted a photo of the back of
my monitor in another thread, but for your reference: dick smith LCT
TV with DVD Player, MODEL: GE6607. Other markings: DSE11080793, N19
GE6607, for whatever they may be worth. I don't remember at the moment
what res I entered in uEnv.txt
5. Again, I don't know if it's my monitor and/or its resolution, but I
don't get sound off the HDMI cable. For whatever it may be worth, I
don't get sound either from my ThinkPad running FreeBSD 9.x. Never did
have the chance to test it with Windows (Vista Home Basic).
6. Just for reference, I tried it with a lower res (480x???) and parts
of the output didn't make it to the screen. E.g., I don't see the
Back+Home+Task button at the bottom of the screen. Changing it to a
higher res fixed that some. And now it occurs to me that maybe I can
see the hidden parts of the output by scrolling?
adb over usb and Android Composite Gadget probably needs some additional kernel patches to be picked from the google android kernel tree.
--
Great work Andrew! In other good news, I was able to boot your latest image w/ LCD3 by flashing it with Win8 and a 8gb microSD card after trying several times. For some reason it automatically boots without needing to press the boot button while applying power as mentioned in the instructions. This is where I was tripping up on before.Next I am planning to get your image working with the following 7inch LCD cape from chipsee: http://www.chipsee.com/product/evm/beagle/bbb-exp-c.html?___store=english&___from_store=defaultIt looks like they include their own android image and source. Do you have any pointers on getting your image to work with this cape?
On Wednesday, July 3, 2013 3:17:43 PM UTC+9, Vishveshwar wrote:adb over usb and Android Composite Gadget probably needs some additional kernel patches to be picked from the google android kernel tree.Thanks. Adding the gadget driver seems to enable it, but getting a bunch of USBerrors on the host:
Hey Roy,
Can you create a backup .img of you sd and provide a download link. I would love to test that image on my BBB with several sd cards to see if it works.
-Wil
On Jun 25, 2013 6:47 AM, <rhkr...@gmail.com> wrote:Trying to get caught up with all the posts...thanks everybody:o On did I check the SD socket. I checked for bent pins, poor solder joints, etc. Nothing showed up under a lighted magnifier. In fact I could see scratch marks on the SD card where the pins on the socket made contact. All of the scratches were about in the middle of the fingers on the SD card so I don't think there is anything wrong there. Solder joints looked good.o On booting something else from the SD card. Well, the first time I tried the board I followed the Getting Started guide and updated to the latest Angstrom. That worked as far as I can tell. Curiously, I also got Android to boot once or twice without the button pressed which Charles explained. That was the first night. I have tried multiple cards, multiple images etc. with the same result.,.hold the button apply power, nothing happens,.no LEDs lit.o Have I tried mounting the card from UBoot? No...I don't have a USB-Serial cable...yet to check and I don't get far enough to bring up the virtual serial port.o Have I formatted the SD card according to the BBB Wiki. I think so. I also tried writing the image from Linux and Windows w/ the same result. Partition-wise there are three partitions...boot, usrdata and rootfs. SD card mounts in both Windows and Ubuntu so I think it's formatted right.o On powering through the mains and not the USB. Tried both. Mains power w/ a 5V@1A wall wart that has worked on similar systems in the past.So, I've concluded that this seems like a hardware problem with this board. As somebody pointed out the button is hard to press and hold down so I wonder whether I flexed the board and an internal trace or solder joint is damaged. Requested an RMA from Mouser...after a few exchanges they said OK. Now I'll need to get a new board and use the same SD card...I'll post again when I have results.Roy
On Monday, June 24, 2013 6:42:07 PM UTC-7, Daniel Escasa wrote:Elsewhere in this group is a similar thread (maybe this one <g>), and a solution was to power the 'bone through the mains, not through the USB port.I've been having the same problems, tried an AC/DC adapter and still didn't get anywhere. Had the adapter tested, and it was defective. Still haven't had the time to get a new one, but I'm hoping that a new adapter will get me booting from the uSD
On Monday, June 24, 2013 10:59:19 AM UTC+8, rhkr...@gmail.com wrote:The board boots to Angstrom from the eMMC with no problems.But, still no luck w/ booting from the uSD card. I tried using a Kingston 8GB SDHC card; downloaded the image again, used 7Zip to decompress it wrote the .img file to the SD card using WIn32 Disk imager, all just like the instructions said. Mounted the card under Ubuntu and it recognized 3 partitions, boot, rootfs and usrdata. boot and rootfs had what I expected. usr data was empty except for lost+found.Same thing, though, when I installed the card and tried to boot to Android. Held button down, applied power, continued to hold button down for about 10 seconds. Nothing - no LEDs lit, no Android boot. don't hold the button and apply power and Angstrom starts up. Is there any way to tell what's happening during booting? I can't figure out how to get the console working - until the system partially boots COM3: (the com port assigned to the BBB) is not recognized.
--
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...@googlegroups.com.
I saw the post on the LCD3 and removed just the video=720x480-16@60 part of that line in uenv.txt. That left the qemu=1 and the vt.global_cursor_default=0 portion of the line. Is that correct?The reason I ask is that with an LCD on my (now sucessfully booting Android new BBB) I can see the clock in the right corner and it looks like it's scaled correctly for the display, but I don't see the rest of the desktop and the panel seems unresponsive to touch.
No luck with the merged Android gadget driver, but it mostly works using theFunction Filesystem driver as described below. The only problem I have isthat the serial number shows as '????????????' which Eclipse doesn't like.
I wanted to let everyone know that I uploaded a new copy of the Android image. I took some measurements during the build process so that I could document the total time required to build Android from source (about 6 hours) and the hard drive space needed (about 35 GB). The download link for the image is still the same: http://icculus.org/~hendersa/BBB_JB_Android_3_8_13.img.bz2In this image, I built Robert Nelson's kernel without disabling anything, which should allow people with supported cape boards and USB/Bluetooth peripherals to use them with Android. I got rid of that blinking framebuffer cursor with the proper setting in uEnv.txt. I also copied all of the built kernel modules and firmware into the Android filesystem. My previous build had no modules or firmware in it, so any capes that were dependent upon firmware definitely wouldn't work.This image is a "first run" image, meaning that it will be like turning your Android system on for the first time. It will take about 2.5 minutes to start up and get to the "welcome to your device" screen. On subsequent runs, it will only take about a minute or so to get started.I used this build as a test of my build instructions from scratch, and I did find a few trivial details that I neglected to mention. These items have been addressed and added into my instructions at: http://icculus.org/~hendersa/androidAndrew
I apologize in advance for being a complete newbie to Linux, but I read the instructions provided, and does this mean that if we just use the pre-built image at the link below, we don't have to follow the rest of the instructions on the page for building Android yourself? Thanks : )
On Friday, June 21, 2013 12:36:00 PM UTC-4, Andrew Henderson wrote:I wanted to let everyone know that I uploaded a new copy of the Android image. I took some measurements during the build process so that I could document the total time required to build Android from source (about 6 hours) and the hard drive space needed (about 35 GB). The download link for the image is still the same: http://icculus.org/~hendersa/BBB_JB_Android_3_8_13.img.bz2
On Tue, Jun 18, 2013 at 12:42 PM, Ryan Ramchandar <ryan...@gmail.com> wrote:
> Thanks for sharing Andrew, This looks like a very interesting project.
>
> Can you elaborate further on how you were able to boot the Android 4.2.2
> image on the BBB. From what I've been reading the arowboat guys have not yet
> got it working on the BBB.
It's actually pretty cool what Andrew just did.. So in the last few
kernel releases there has been renewed interest in merging the android
kernel stuff in mainline.. So Andrew took the kernel source we are
using for Angstrom/Ubuntu and rebuilt it with more of the Android
config options enabled.. Essentially ignoring the 'arowboat' kernel..
Tweaked a few things, and bam, Android works. ;)
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
Hi Nelson ,Thanks for all your efforts in adding support for BBB.I ported your Android Image On My BBB which i used for Device driver Testing.But with this build my mini usb is not detected with lsusb command thus i not able to use adb on usb.Can you please help me out finding way to enable Mini Usb on BBB.ThanksAmit
Hello all. I posted this information over at the Google+ group for BeagleBoard.org, but I wanted to post it here as well. I have Android running on the BBB using the Jellybean (4.2.2) source from arowboat.org and the Linux 3.8.13 kernel from my BeagleSNES project (www.beaglesnes.org). I just added the Android drivers (Drivers -> Staging Drivers -> Android) into the same kernel configuration that I use for BeagleSNES. This kernel is really just a stripped down configuration (a 1.9 meg zImage) using Robert Nelson's 3.8.x kernel source tree. Instead of using the GCC cross-compiler that comes in Rowboat's current prebuilt tools, I use the 3.7 GCC that comes with Robert's kernel tree to build the entire system. I also updated the u-boot to v2013.04.
Here is a video of it running: https://www.youtube.com/watch?v=yeSt1Y7FhEs
Here is the download of a working Android image that can be written onto a 4GB microSD card using "dd": http://icculus.org/~hendersa/BBB_JB_Android_3_8_13.img.bz2
There is no hardware accelerated video in this version, since SGX support isn't ready for the 3.8 kernel. To shut off hardware accelerated video, I pass "qemu=1" as a kernel command line argument in uEnv.txt and I add "debug.egl.hw=0" to the /system/build.prop file in the root file system. To get rid of that blinking cursor on the framebuffer (which I accidentally left on in the image that I made), add this to the uEnv.txt kernel command line arguments: "vt.global_cursor_default=0"
This build will be of interest to Android experimenters who want to use HDMI for audio and video output (rather than using an LCD cape) and who want to experiment with using the device tree. My kernel is pretty stripped down, so feel free to fetch Robert's latest kernel source for the 3.8.x branch and rebuild your own kernel to drop into the image that I have supplied. That way, you can include whatever drivers you would like in your kernel. Use a USB mouse (and a keyboard, too, if you want) to interact with the system.
Thanks, and enjoy!
Andrew
I'm also having problems starting adbd with kernel 3.8 and I think I found the problem. I tried to load the kernel module using this command:
CONFIG_USB_FUNCTIONFS=y
but when i write ./adb devices
my device not appear in the list
however i check the usb debugging in my BBB.
Best Regards,
Sultan
Andrew:Thank you for this post. I have this image working on my BBB using 4D Systems 4DCAPE-43T Cape by editing the uEnv.txt as: video=48...@56 . I am able to SSH to the device using Android SSH Server on the device and putty on my PC. However, I need to know the root password for this image. I like to avoid using 'adb shell' to get to the root. I really want to root this device. I use Xamarin as a development tool and it works well. However, when I try to access, via code, the "/sys/class/leds/beaglebone:green:usr0"
--
[...]
Try testing it out with a USB mouse and making sure that it looks and acts like what you would expect. If you move the mouse and don't see the cursor, then let us know. [...]Andrew
Strangely, I've been unable to make touchscreen work with "andrews jb" on 4D systems 4DCAPE_70TI've tried with the prebuilt image, and also tried building from source, using the instructions on Andrews webpage, using latest 3.8.x kernel sources.Touch screen works fine on TI_Android_JB_4.2.2_DevKit_4.1.1 image, so it's definitely not an hardware issue.I'm currently baffled, since its reported that LCD7 works, and the 4DCAPE_70T should be similar, it appears.Any help/suggestions highly appriciated - maybe there's some patches available i need?