[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[andrexice]

Hi Andrew thanks for all your hard work can you assist me to add a new 
4dcape-70ct cbl 
works with 4dcape-70t but not with the new 4dcape-70ct cbl 

Regards
Andre
 
On Sunday, 28 September 2014 17:14:24 UTC+2, 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/56d25eeb-4852-436a-a544-a84c3fedb9f4%40googlegroups.com.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[baytechits]

Hi,

I need to build AOSP kikat 4.4 for beaglebone black and linux kernel is 4.1 
for my BLE integration. 
Do you have any reference build for guide to do such build

regards
venkat
baytech


On Tuesday, March 1, 2016 at 6:42:10 AM UTC+5:30, dariush.ab...@gmail.com 
wrote:
>
>
>
> On Sunday, September 28, 2014 at 6:44:24 PM UTC+3: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
>>
>
> Hi Andrew.
> Thanks a lot for your great work.
> I'm trying to flash BBBAndroid to eMMC but using fastboot.
> the problem is it does not boot with kernel 3.8, just boots with kernel 
> 3.2.
> I'm using the u-boot with fastboot support "U-Boot SPL 
> 2013.01.01-bbb-fb-2-gf7d94e6 ".
> It complains about not supported machin ID.
> Any suggestion? 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/b6c80549-d415-4d00-9b5f-574ab2e8b312%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[dariush . abbasinezhad]

On Sunday, September 28, 2014 at 6:44:24 PM UTC+3: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
>

Hi Andrew.
Thanks a lot for your great work.
I'm trying to flash BBBAndroid to eMMC but using fastboot.
the problem is it does not boot with kernel 3.8, just boots with kernel 3.2.
I'm using the u-boot with fastboot support "U-Boot SPL 
2013.01.01-bbb-fb-2-gf7d94e6 ".
It complains about not supported machin ID.
Any suggestion? 

-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[gassa0617]

I recently followed the instruction to build my own image(Android 4.4.4 + 
kernel 3.8.13), the ADB doesn't work no matter whether I replaced the three 
file you upload in the response.
Any suggestions.

Thanks 

-yin

在 2014年9月28日星期日 UTC-4上午11:14:24，Andrew Henderson写道：
>
> 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.

Re: [beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[simhans9]

Hi,

Can any body help me out to automount(mmc or usb) supports to BBB or not 
with android kitkat 4.4.4. If it supports can help me how to add support. 

Thanks & Regards,
Narasimha.
On Saturday, April 18, 2015 at 1:13:53 AM UTC+5:30, cam...@gmail.com wrote:
>
> Seems to work now.  I made sure udev had the correct entries and I was 
> able to boot into Android and toggle an LED once I modified a few pertinent 
> files.
>
> Thanks!
>
> On Thursday, April 9, 2015 at 5:43:00 PM UTC-4, Keith Conger wrote:
>>
>> I can confirm it works fine with MacOSX, my guess its a configuration 
>> issue on the Linux desktop side. 
>>
>> Keith 
>>
>> On Thu, Apr 9, 2015 at 11:02 AM,   wrote: 
>> > Was this ever resolved?  I am experiencing a similar issue. 
>> > 
>> > 
>> > On Tuesday, March 31, 2015 at 2:06:14 PM UTC-4, jimmy...@gmail.com 
>> wrote: 
>> >> 
>> >> Hi Andrew, 
>> >> 
>> >> Please you help me with the USB ADB. 
>> >> I downloaded bbbandroid_111514.img.xz image, and I wrote this image to 
>> my 
>> >> Beaglebone Black. 
>> >> I use Ubuntu 14.04, I have made /etc/udev/rules.d file with content: 
>> >> #adb protocol on BeagleBone Black (BBB 1) 
>> >> SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666" 
>> >> #adb protocol on BeagleBone Black (BBB 2) 
>> >> SUBSYSTEM=="usb", ATTR{idVendor}=="0451", MODE="0666" 
>> >> and I grant permission: 
>> >> chmod a+r /etc/udev/rules.d/51-android.rules 
>> >> and: adb kill-server, adb start-server 
>> >> But when I give command "adb devices", I only see "List of devices 
>> >> attached", my BBB can't attach. 
>> >> So I decide to replace three files that you have attached to my BBB. 
>> >> But now my BBB can't start into Android OS, I only see 'ANDROID' on 
>> screen 
>> >> forever. 
>> >> What's happen here? 
>> >> Please you help me for USB ADB. 
>> >> 
>> >> Best regards 
>> >> Jimmy Trinh 
>> >> 
>> >> 
>> >> On Tuesday, October 7, 2014 at 8:10:50 AM UTC+7, Andrew Henderson 
>> wrote: 
>> >>> 
>> >>> I have not made a new premade image with USB ADB, but I have it 
>> working. 
>> >>> In your current BBBAndroid image, replace your uEnv.txt (/boot 
>> partition) 
>> >>> with the one I have attached.  Replace your two 
>> init.genericam33xx*.rc files 
>> >>> (/rootfs partition) with the two I have attached.  In addition to 
>> getting 
>> >>> USB ADB up and running, the main .rc file also changes some 
>> permissions to 
>> >>> make them more relaxed.  Now, i2c-tools work without superuser 
>> privileges 
>> >>> and it "wakes up" all four GPIO banks in case you need to mmap() the 
>> GPIO 
>> >>> registers. 
>> >>> 
>> >>> If you watch the FTDI output from the BBB (when the USB is plugged in 
>> at 
>> >>> boot), you'll see something like the following: 
>> >>> 
>> >>> [5.784087] CAUTION: musb: Babble Interrupt Occurred 
>> >>> [5.854604] CAUTION: musb: Babble Interrupt Occurred 
>> >>> [6.048723] CAUTION: musb: Babble Interrupt Occurred 
>> >>> [6.119724] CAUTION: musb: Babble Interrupt Occurred 
>> >>> [6.341756]  gadget: high-speed config #1: FunctionFS 
>> >>> 
>> >>> On your dev system side, use ADB to list the devices: 
>> >>> 
>> >>> $ adb devices 
>> >>> List of devices attached 
>> >>> BBBANDROID  device 
>> >>> 
>> >>> $ adb logcat 
>> >>> ... 
>> >>> D/AlarmScheduler(  917): No events found starting within 1 week. 
>> >>> I/ActivityManager(  592): Waited long enough for: 
>> ServiceRecord{a5fb0900 
>> >>> u0 com.android.calendar/.alerts.InitAlarmsService} 
>> >>> D/InitAlarmsService(  917): Clearing and rescheduling alarms. 
>> >>> D/ConnectivityService(  592): Sampling interval elapsed, updating 
>> >>> statistics .. 
>> >>> D/ConnectivityService(  592): Done. 
>> >>> D/ConnectivityService(  592): Setting timer for 720seconds 
>> >>> 
>> >>> 
>> >>> On Sunday, October 5, 2014 5:24:27 PM UTC, Andrew Henderson wrote: 
>>  
>>  USB ADB is currently being worked on.  The image I provided builds 
>> in 
>>  FunctionFS support, but I have not yet made the modifications to the 
>> .rc 
>>  files to point ADB to FunctionFS.  I'm currently working on a few 
>>  modifications to the .rc files to make the image a bit more "BBB 
>> friendly" 
>>  for those interested in using it for Android hardware interfacing 
>> practice. 
>>  
>>  On Sunday, October 5, 2014 12:31:33 PM UTC-4, Lei Wang wrote: 
>> > 
>> > May I ask if ADB over USB is supported in this release? Thanks very 
>> > much! -lei 
>> > 
>> > -- 
>> > 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/tHXTzJhH_Qc/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/d/optout. 

Re: [beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[camisir]

Seems to work now.  I made sure udev had the correct entries and I was able 
to boot into Android and toggle an LED once I modified a few pertinent 
files.

Thanks!

On Thursday, April 9, 2015 at 5:43:00 PM UTC-4, Keith Conger wrote:

 I can confirm it works fine with MacOSX, my guess its a configuration 
 issue on the Linux desktop side. 

 Keith 

 On Thu, Apr 9, 2015 at 11:02 AM,  cam...@gmail.com javascript: wrote: 
  Was this ever resolved?  I am experiencing a similar issue. 
  
  
  On Tuesday, March 31, 2015 at 2:06:14 PM UTC-4, jimmy...@gmail.com 
 wrote: 
  
  Hi Andrew, 
  
  Please you help me with the USB ADB. 
  I downloaded bbbandroid_111514.img.xz image, and I wrote this image to 
 my 
  Beaglebone Black. 
  I use Ubuntu 14.04, I have made /etc/udev/rules.d file with content: 
  #adb protocol on BeagleBone Black (BBB 1) 
  SUBSYSTEM==usb, ATTR{idVendor}==18d1, MODE=0666 
  #adb protocol on BeagleBone Black (BBB 2) 
  SUBSYSTEM==usb, ATTR{idVendor}==0451, MODE=0666 
  and I grant permission: 
  chmod a+r /etc/udev/rules.d/51-android.rules 
  and: adb kill-server, adb start-server 
  But when I give command adb devices, I only see List of devices 
  attached, my BBB can't attach. 
  So I decide to replace three files that you have attached to my BBB. 
  But now my BBB can't start into Android OS, I only see 'ANDROID' on 
 screen 
  forever. 
  What's happen here? 
  Please you help me for USB ADB. 
  
  Best regards 
  Jimmy Trinh 
  
  
  On Tuesday, October 7, 2014 at 8:10:50 AM UTC+7, Andrew Henderson 
 wrote: 
  
  I have not made a new premade image with USB ADB, but I have it 
 working. 
  In your current BBBAndroid image, replace your uEnv.txt (/boot 
 partition) 
  with the one I have attached.  Replace your two init.genericam33xx*.rc 
 files 
  (/rootfs partition) with the two I have attached.  In addition to 
 getting 
  USB ADB up and running, the main .rc file also changes some 
 permissions to 
  make them more relaxed.  Now, i2c-tools work without superuser 
 privileges 
  and it wakes up all four GPIO banks in case you need to mmap() the 
 GPIO 
  registers. 
  
  If you watch the FTDI output from the BBB (when the USB is plugged in 
 at 
  boot), you'll see something like the following: 
  
  [5.784087] CAUTION: musb: Babble Interrupt Occurred 
  [5.854604] CAUTION: musb: Babble Interrupt Occurred 
  [6.048723] CAUTION: musb: Babble Interrupt Occurred 
  [6.119724] CAUTION: musb: Babble Interrupt Occurred 
  [6.341756]  gadget: high-speed config #1: FunctionFS 
  
  On your dev system side, use ADB to list the devices: 
  
  $ adb devices 
  List of devices attached 
  BBBANDROID  device 
  
  $ adb logcat 
  ... 
  D/AlarmScheduler(  917): No events found starting within 1 week. 
  I/ActivityManager(  592): Waited long enough for: 
 ServiceRecord{a5fb0900 
  u0 com.android.calendar/.alerts.InitAlarmsService} 
  D/InitAlarmsService(  917): Clearing and rescheduling alarms. 
  D/ConnectivityService(  592): Sampling interval elapsed, updating 
  statistics .. 
  D/ConnectivityService(  592): Done. 
  D/ConnectivityService(  592): Setting timer for 720seconds 
  
  
  On Sunday, October 5, 2014 5:24:27 PM UTC, Andrew Henderson wrote: 
  
  USB ADB is currently being worked on.  The image I provided builds in 
  FunctionFS support, but I have not yet made the modifications to the 
 .rc 
  files to point ADB to FunctionFS.  I'm currently working on a few 
  modifications to the .rc files to make the image a bit more BBB 
 friendly 
  for those interested in using it for Android hardware interfacing 
 practice. 
  
  On Sunday, October 5, 2014 12:31:33 PM UTC-4, Lei Wang wrote: 
  
  May I ask if ADB over USB is supported in this release? Thanks very 
  much! -lei 
  
  -- 
  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/tHXTzJhH_Qc/unsubscribe. 
  To unsubscribe from this group and all its topics, send an email to 
  beagleboard...@googlegroups.com javascript:. 
  For more options, visit https://groups.google.com/d/optout. 



 -- 
 Keith Conger 
 keith DOT conger AT gmail DOT com 
 http://thecongers.org 


-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[camisir]

Was this ever resolved?  I am experiencing a similar issue.

On Tuesday, March 31, 2015 at 2:06:14 PM UTC-4, jimmy...@gmail.com wrote:

 Hi Andrew,

 Please you help me with the USB ADB.
 I downloaded bbbandroid_111514.img.xz image, and I wrote this image to my 
 Beaglebone Black.
 I use Ubuntu 14.04, I have made /etc/udev/rules.d file with content:
 #adb protocol on BeagleBone Black (BBB 1)
 SUBSYSTEM==usb, ATTR{idVendor}==18d1, MODE=0666
 #adb protocol on BeagleBone Black (BBB 2)
 SUBSYSTEM==usb, ATTR{idVendor}==0451, MODE=0666
 and I grant permission: 
 chmod a+r /etc/udev/rules.d/51-android.rules
 and: adb kill-server, adb start-server
 But when I give command adb devices, I only see List of devices 
 attached, my BBB can't attach.
 So I decide to replace three files that you have attached to my BBB.
 But now my BBB can't start into Android OS, I only see 'ANDROID' on screen 
 forever.
 What's happen here?
 Please you help me for USB ADB.

 Best regards
 Jimmy Trinh


 On Tuesday, October 7, 2014 at 8:10:50 AM UTC+7, Andrew Henderson wrote:

 I have not made a new premade image with USB ADB, but I have it working.  
 In your current BBBAndroid image, replace your uEnv.txt (/boot partition) 
 with the one I have attached.  Replace your two init.genericam33xx*.rc 
 files (/rootfs partition) with the two I have attached.  In addition to 
 getting USB ADB up and running, the main .rc file also changes some 
 permissions to make them more relaxed.  Now, i2c-tools work without 
 superuser privileges and it wakes up all four GPIO banks in case you need 
 to mmap() the GPIO registers.

 If you watch the FTDI output from the BBB (when the USB is plugged in at 
 boot), you'll see something like the following:

 [5.784087] CAUTION: musb: Babble Interrupt Occurred
 [5.854604] CAUTION: musb: Babble Interrupt Occurred
 [6.048723] CAUTION: musb: Babble Interrupt Occurred
 [6.119724] CAUTION: musb: Babble Interrupt Occurred
 [6.341756]  gadget: high-speed config #1: FunctionFS

 On your dev system side, use ADB to list the devices:

 $ adb devices
 List of devices attached
 BBBANDROID  device

 $ adb logcat
 ...
 D/AlarmScheduler(  917): No events found starting within 1 week.
 I/ActivityManager(  592): Waited long enough for: ServiceRecord{a5fb0900 
 u0 com.android.calendar/.alerts.InitAlarmsService}
 D/InitAlarmsService(  917): Clearing and rescheduling alarms.
 D/ConnectivityService(  592): Sampling interval elapsed, updating 
 statistics ..
 D/ConnectivityService(  592): Done.
 D/ConnectivityService(  592): Setting timer for 720seconds


 On Sunday, October 5, 2014 5:24:27 PM UTC, Andrew Henderson wrote:

 USB ADB is currently being worked on.  The image I provided builds in 
 FunctionFS support, but I have not yet made the modifications to the .rc 
 files to point ADB to FunctionFS.  I'm currently working on a few 
 modifications to the .rc files to make the image a bit more BBB friendly 
 for those interested in using it for Android hardware interfacing practice.

 On Sunday, October 5, 2014 12:31:33 PM UTC-4, Lei Wang wrote:

 May I ask if ADB over USB is supported in this release? Thanks very 
 much! -lei



-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[jimmy . tayho]

Hi Andrew,

Please you help me with the USB ADB.
I downloaded bbbandroid_111514.img.xz image, and I wrote this image to my 
Beaglebone Black.
I use Ubuntu 14.04, I have made /etc/udev/rules.d file with content:
#adb protocol on BeagleBone Black (BBB 1)
SUBSYSTEM==usb, ATTR{idVendor}==18d1, MODE=0666
#adb protocol on BeagleBone Black (BBB 2)
SUBSYSTEM==usb, ATTR{idVendor}==0451, MODE=0666
and I grant permission: 
chmod a+r /etc/udev/rules.d/51-android.rules
and: adb kill-server, adb start-server
But when I give command adb devices, I only see List of devices 
attached, my BBB can't attach.
So I decide to replace three files that you have attached to my BBB.
But now my BBB can't start into Android OS, I only see 'ANDROID' on screen 
forever.
What's happen here?
Please you help me for USB ADB.

Best regards
Jimmy Trinh


On Tuesday, October 7, 2014 at 8:10:50 AM UTC+7, Andrew Henderson wrote:

 I have not made a new premade image with USB ADB, but I have it working.  
 In your current BBBAndroid image, replace your uEnv.txt (/boot partition) 
 with the one I have attached.  Replace your two init.genericam33xx*.rc 
 files (/rootfs partition) with the two I have attached.  In addition to 
 getting USB ADB up and running, the main .rc file also changes some 
 permissions to make them more relaxed.  Now, i2c-tools work without 
 superuser privileges and it wakes up all four GPIO banks in case you need 
 to mmap() the GPIO registers.

 If you watch the FTDI output from the BBB (when the USB is plugged in at 
 boot), you'll see something like the following:

 [5.784087] CAUTION: musb: Babble Interrupt Occurred
 [5.854604] CAUTION: musb: Babble Interrupt Occurred
 [6.048723] CAUTION: musb: Babble Interrupt Occurred
 [6.119724] CAUTION: musb: Babble Interrupt Occurred
 [6.341756]  gadget: high-speed config #1: FunctionFS

 On your dev system side, use ADB to list the devices:

 $ adb devices
 List of devices attached
 BBBANDROID  device

 $ adb logcat
 ...
 D/AlarmScheduler(  917): No events found starting within 1 week.
 I/ActivityManager(  592): Waited long enough for: ServiceRecord{a5fb0900 
 u0 com.android.calendar/.alerts.InitAlarmsService}
 D/InitAlarmsService(  917): Clearing and rescheduling alarms.
 D/ConnectivityService(  592): Sampling interval elapsed, updating 
 statistics ..
 D/ConnectivityService(  592): Done.
 D/ConnectivityService(  592): Setting timer for 720seconds


 On Sunday, October 5, 2014 5:24:27 PM UTC, Andrew Henderson wrote:

 USB ADB is currently being worked on.  The image I provided builds in 
 FunctionFS support, but I have not yet made the modifications to the .rc 
 files to point ADB to FunctionFS.  I'm currently working on a few 
 modifications to the .rc files to make the image a bit more BBB friendly 
 for those interested in using it for Android hardware interfacing practice.

 On Sunday, October 5, 2014 12:31:33 PM UTC-4, Lei Wang wrote:

 May I ask if ADB over USB is supported in this release? Thanks very 
 much! -lei



-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Keith Conger]

Since this took me a few days to figure out, I figured I'd post how I got 
Wifi working in bbbandroid.  Hope this saves a few days of your life :) 
 Obviously swap the kernel modules with the ones appropriate for your 
device.

# Add to device/ti/beagleboneblack/init.genericam33xx_flatteneddevicetr.rc:
# under on post-fs-data
# wifi
mkdir /data/misc/wifi/sockets 0770 wifi wifi
insmod 
/system/vendor/lib/modules/3.8.13+/kernel/net/wireless/cfg80211.ko
insmod 
/system/vendor/lib/modules/3.8.13+/kernel/net/mac80211/mac80211.ko
insmod 
/system/vendor/lib/modules/3.8.13+/kernel/drivers/net/wireless/rtl8192cu/8192cu.ko

# At the bottom
service wpa_supplicant /system/bin/wpa_supplicant \
   -iwlan0 -Dwext -c/data/misc/wifi/wpa_supplicant.conf \
   -e/data/misc/wifi/entropy.bin -g@android:wpa_wlan0
   class main
   socket wpa_wlan0 dgram 660 wifi wifi
   disabled
   oneshot

service dhcpcd_wlan0 /system/bin/dhcpcd -ABKL
   class main
   disabled
   oneshot

service iprenew_wlan0 /system/bin/dhcpcd -n
   class main
   disabled
   oneshot


# Add to following tags in file 
device/ti/beagleboneblack/overlay/frameworks/base/core/res/res/values/config.xml:
string-array translatable=false name=networkAttributes
itemwifi,1,1,1,-1,true/item
…
/string-array

# And
string-array translatable=false name=radioAttributes
item1,1/item
…
/string-array

# Add to device/ti/beagleboneblack/BoardConfig.mk:
BOARD_WPA_SUPPLICANT_DRIVER  := WEXT
BOARD_HOSTAPD_DRIVER := WEXT
WPA_SUPPLICANT_VERSION   := VER_0_8_X
BOARD_WLAN_DEVICE:= wlan0

# Add file device/ti/beagleboneblack/wpa_supplicant.conf with the following 
contents:
ctrl_interface=wlan0
update_config=1

# Add to device/ti/beagleboneblack/device.mk:
PRODUCT_COPY_FILES += \

frameworks/native/data/etc/android.hardware.wifi.xml:system/etc/permissions/android.hardware.wifi.xml
 
\

device/ti/beagleboneblack/wpa_supplicant.conf:system/etc/wifi/wpa_supplicant.conf

PRODUCT_PROPERTY_OVERRIDES += \
   wifi.interface=wlan0 \
   wlan.driver.status=ok


On Sunday, October 12, 2014 at 10:55:58 AM UTC-6, Adam Singer wrote:

 The suggested Wifi support would be awesome, its a common stack that 
 people can get their hands on easily. ADB over USB would also be greatly 
 appreciated when you publish a new image :) 


-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Michael Gobbers]

Hey Andrew,

I'm able to boot the 3.14 kernel now with usb and proper hdmi support.
I then started to include the bluetooth modules. The modules seem to load
fine.
However, now when I'm seeing the boot animation and finally enter to
homescreen a crash happens and the boot animation appears again.

This is the output after the crash:

binder: 8841: binder_alloc_buf, no vma

binder: 8841: binder_alloc_buf, no vma

[  658.943483] binder: 9034:9191 transaction failed 29201, size 248-4

[  658.951002] alarm_release: clear alarm, pending 0

[  658.958173] binder: 8841: binder_alloc_buf, no vma

[  658.963237] binder: 9034:9191 transaction failed 29201, size 188-4

[  658.971025] binder: release 8841:9028 transaction 60843 in, still active

[  658.978173] binder: send failed reply for transaction 60843 to 8968:8968

[  658.985315] binder: undelivered transaction 61599

[  658.990261] binder: undelivered transaction 61605

[  658.995234] binder: undelivered transaction 61606

[  659.000672] binder: undelivered transaction 61592

[  659.005677] binder: send failed reply for transaction 61593 to 9265:9265

[  659.012739] binder: send failed reply for transaction 61607 to 9281:9308

[  659.019834] binder: send failed reply for transaction 61618 to 9296:9296

[  659.029835] binder: 8968:8968 transaction failed 29189, size 208-0

[  659.065614] binder: 9265:9265 transaction failed 29189, size 240-0

[  659.251928] init: untracked pid 9296 exited

[  659.394084] init: untracked pid 8998 exited

[  659.398895] init: untracked pid 9116 exited

[  659.454135] init: untracked pid 9281 exited

[  659.464443] init: untracked pid 8927 exited

[  659.495386] init: untracked pid 9265 exited

[  662.203936] init: untracked pid 8985 exited

[  662.220119] init: untracked pid 8968 exited
I was thinking that the vmalloc size was not big enough. However, It's
already at 486MB

I do always see the alarm release in the output. Maybe that has something
to do with it?

Cheers,
Michael



2015-03-18 17:20 GMT+01:00 Michael Gobbers mgobb...@orcasolutions.be:

 Hey Andrew,

 I wasn't able to solve either one of my problems.
 Disabling FunctionFS led to a kernel panic.

 Changing the resolutions definitely works but the flickering is still
 there.

 I'm pretty much out of options here I guess so I think the next step is
 backporting the required kernel modules required for the BLE to 3.8 as I'm
 getting nowhere with the 3.14 kernel.

 Cheers,
 Michael

 2015-03-18 14:23 GMT+01:00 Andrew Henderson hende...@icculus.org:

 OK, this is starting to make more sense. 1920x1080 at 60 Hz is not a
 supported mode for the BBB. I've seen screen shearing on 1920x1080 at 24 Hz
 before with OpenGL ES on 3.14 with single buffering before. My suggestion
 is to use the video= parameter to set a supported resolution lower than
 1920x1080 and see how well that works for you. Here is a list of the
 supported modes: http://elinux.org/Beagleboard:BeagleBoneBlack_HDMI

 Maybe try 1280x720-16@60, instead.

 On Wednesday, March 18, 2015 at 7:02:29 AM UTC-4, Michael Gobbers wrote:

 For the video issue I tried changing the video parameter to
 1920x1080-16@60 the native resoltion of my display. However, when I
 did, I did not see anything on the display.

 Here is a small video of the display so you get what I mean with
 flicker. It seems that some video buffer isn't emptied or something as I'm
 seeing old screens between the one that I should see
 https://youtu.be/me1_O4iaHB8




 --
 Michael Gobbers   http://be.linkedin.com/in/michaelgobbers


 Desguinlei 6 - 2018 Antwerpen




-- 
Michael Gobbers   http://be.linkedin.com/in/michaelgobbers


Desguinlei 6 - 2018 Antwerpen

-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Michael Gobbers]

Hi Andrew,

I retried the 3.14 kernel.

I'm getting the following error:

 WARNING: CPU: 0 PID: 110 at drivers/usb/gadget/f_fs.c:2595
ffs_ep0_write+0x44d/0x474()

[  149.939235] Modules linked in:

[  149.942448] CPU: 0 PID: 110 Comm: adbd Tainted: GW3.14.35+ #6

[  149.949616] [c00119c5] (unwind_backtrace) from [c000f63b]
(show_stack+0xb/0xc)

[  149.957570] [c000f63b] (show_stack) from [c05005ab]
(dump_stack+0x4f/0x64)

[  149.965181] [c05005ab] (dump_stack) from [c0030b4f]
(warn_slowpath_common+0x4b/0x68)

[  149.973686] [c0030b4f] (warn_slowpath_common) from [c0030b7d]
(warn_slowpath_null+0x11/0x14)

[  149.982940] [c0030b7d] (warn_slowpath_null) from [c036f70d]
(ffs_ep0_write+0x44d/0x474)

[  149.991729] [c036f70d] (ffs_ep0_write) from [c00cafb1]
(vfs_write+0x6d/0x130)

[  149.999599] [c00cafb1] (vfs_write) from [c00cb2c9]
(SyS_write+0x2d/0x64)

[  150.006994] [c00cb2c9] (SyS_write) from [c000cc81]
(ret_fast_syscall+0x1/0x46)

[  150.014950] ---[ end trace 3555ece349f08477 ]---

[  151.039009] read descriptors

[  151.042065] read strings
I believe it has to do with the FunctionFS. What is it used for? Can I
disable it? I believe it is only used so that ADB would work right?

To provide you with some extra info, I had to build the kernel with the
folowing modifications to the defconfig:

I commented:
# CONFIG_USB_G_NOKIA=m  //This led to an inconsistent state

I included this:
CONFIG_DMA_OMAP=y //This was a required dependency

Cheers,
Michael



2015-03-18 2:39 GMT+01:00 Andrew Henderson hende...@icculus.org:

 Are you using an LCD cape? I have seen flickering similar to what you
 described with the 3.8 kernel when I forced a video resolution via the
 video= kernel command line option (in uEnv.txt in the boot partition) for
 the LCD3/4/7 CircuitCo capes and the 4DCAPE-43T/70T capes from 4D Systems.
 For those display capes, the resolution is pulled from the device tree
 overlay for the cape automatically, so you should not specify a video
 resolution. If you are using HDMI, you may not be getting the proper EDID
 resolution information from your display. In that case, the TILCDC driver
 will default to 1024x768, which your display (if it is an HDMI display) may
 not properly support. Either way, I have seen that refresh problem when the
 logical resolution that the TILCDC driver expects mismatches the physical
 resolution of your display device.

 I have not seen that particular USB error before, but I also have not
 worked with the 3.10 kernel on the BBB. I've gone straight from 3.8 to
 3.13/14.

 Andrew

 On Tuesday, March 17, 2015 at 4:45:42 PM UTC-4, Michael Gobbers wrote:

 Hi Andrew,

 Thanks for the reply. Indeed Keith Conger supplied me with the patches.
 I have gotten a bit further now as I'm getting the hand of configuring
 and building the kernel for the beaglebone black. I'm now able to boot all
 the way to the android home screen.

 However, I have major graphical glitches. It seems that the boot
 animation is being displayed together with the home screen. Their also
 seemed to be a lot of flickering on the screen. So there is something
 seriously wrong there.

 The biggest issue for me that I came across was the fact that my usb host
 port didn't seem to work. So no mouse available there.
 Today I tried the 3.10 kernel and there I do not have the graphical
 glitches. However, again there is no host port available.

 from the ftdi output I did find the following while booting the kernel:

 [2.725494] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with 
 status -517

 [2.733755] platform musb-hdrc.0.auto: Driver musb-hdrc requests probe 
 deferral

 Have you ever come across this error?




-- 
Michael Gobbers   http://be.linkedin.com/in/michaelgobbers
+32477188592


Desguinlei 6 - 2018 Antwerpen

-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Michael Gobbers]

For the video issue I tried changing the video parameter to 1920x1080-16@60
the native resoltion of my display. However, when I did, I did not see
anything on the display.

Here is a small video of the display so you get what I mean with flicker.
It seems that some video buffer isn't emptied or something as I'm seeing
old screens between the one that I should see
https://youtu.be/me1_O4iaHB8

2015-03-18 11:50 GMT+01:00 Michael Gobbers mgobb...@orcasolutions.be:

 Hi Andrew,

 I retried the 3.14 kernel.

 I'm getting the following error:

  WARNING: CPU: 0 PID: 110 at drivers/usb/gadget/f_fs.c:2595
 ffs_ep0_write+0x44d/0x474()

 [  149.939235] Modules linked in:

 [  149.942448] CPU: 0 PID: 110 Comm: adbd Tainted: GW3.14.35+
 #6

 [  149.949616] [c00119c5] (unwind_backtrace) from [c000f63b]
 (show_stack+0xb/0xc)

 [  149.957570] [c000f63b] (show_stack) from [c05005ab]
 (dump_stack+0x4f/0x64)

 [  149.965181] [c05005ab] (dump_stack) from [c0030b4f]
 (warn_slowpath_common+0x4b/0x68)

 [  149.973686] [c0030b4f] (warn_slowpath_common) from [c0030b7d]
 (warn_slowpath_null+0x11/0x14)

 [  149.982940] [c0030b7d] (warn_slowpath_null) from [c036f70d]
 (ffs_ep0_write+0x44d/0x474)

 [  149.991729] [c036f70d] (ffs_ep0_write) from [c00cafb1]
 (vfs_write+0x6d/0x130)

 [  149.999599] [c00cafb1] (vfs_write) from [c00cb2c9]
 (SyS_write+0x2d/0x64)

 [  150.006994] [c00cb2c9] (SyS_write) from [c000cc81]
 (ret_fast_syscall+0x1/0x46)

 [  150.014950] ---[ end trace 3555ece349f08477 ]---

 [  151.039009] read descriptors

 [  151.042065] read strings
 I believe it has to do with the FunctionFS. What is it used for? Can I
 disable it? I believe it is only used so that ADB would work right?

 To provide you with some extra info, I had to build the kernel with the
 folowing modifications to the defconfig:

 I commented:
 # CONFIG_USB_G_NOKIA=m  //This led to an inconsistent state

 I included this:
 CONFIG_DMA_OMAP=y //This was a required dependency

 Cheers,
 Michael



 2015-03-18 2:39 GMT+01:00 Andrew Henderson hende...@icculus.org:

 Are you using an LCD cape? I have seen flickering similar to what you
 described with the 3.8 kernel when I forced a video resolution via the
 video= kernel command line option (in uEnv.txt in the boot partition) for
 the LCD3/4/7 CircuitCo capes and the 4DCAPE-43T/70T capes from 4D Systems.
 For those display capes, the resolution is pulled from the device tree
 overlay for the cape automatically, so you should not specify a video
 resolution. If you are using HDMI, you may not be getting the proper EDID
 resolution information from your display. In that case, the TILCDC driver
 will default to 1024x768, which your display (if it is an HDMI display) may
 not properly support. Either way, I have seen that refresh problem when the
 logical resolution that the TILCDC driver expects mismatches the physical
 resolution of your display device.

 I have not seen that particular USB error before, but I also have not
 worked with the 3.10 kernel on the BBB. I've gone straight from 3.8 to
 3.13/14.

 Andrew

 On Tuesday, March 17, 2015 at 4:45:42 PM UTC-4, Michael Gobbers wrote:

 Hi Andrew,

 Thanks for the reply. Indeed Keith Conger supplied me with the patches.
 I have gotten a bit further now as I'm getting the hand of configuring
 and building the kernel for the beaglebone black. I'm now able to boot all
 the way to the android home screen.

 However, I have major graphical glitches. It seems that the boot
 animation is being displayed together with the home screen. Their also
 seemed to be a lot of flickering on the screen. So there is something
 seriously wrong there.

 The biggest issue for me that I came across was the fact that my usb
 host port didn't seem to work. So no mouse available there.
 Today I tried the 3.10 kernel and there I do not have the graphical
 glitches. However, again there is no host port available.

 from the ftdi output I did find the following while booting the kernel:

 [2.725494] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with 
 status -517

 [2.733755] platform musb-hdrc.0.auto: Driver musb-hdrc requests probe 
 deferral

 Have you ever come across this error?




 --
 Michael Gobbers   http://be.linkedin.com/in/michaelgobbers
 +32477188592


 Desguinlei 6 - 2018 Antwerpen




-- 
Michael Gobbers   http://be.linkedin.com/in/michaelgobbers
+32477188592


Desguinlei 6 - 2018 Antwerpen

-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

OK, this is starting to make more sense. 1920x1080 at 60 Hz is not a 
supported mode for the BBB. I've seen screen shearing on 1920x1080 at 24 Hz 
before with OpenGL ES on 3.14 with single buffering before. My suggestion 
is to use the video= parameter to set a supported resolution lower than 
1920x1080 and see how well that works for you. Here is a list of the 
supported modes: http://elinux.org/Beagleboard:BeagleBoneBlack_HDMI

Maybe try 1280x720-16@60, instead.

On Wednesday, March 18, 2015 at 7:02:29 AM UTC-4, Michael Gobbers wrote:

 For the video issue I tried changing the video parameter to 
 1920x1080-16@60 the native resoltion of my display. However, when I did, I 
 did not see anything on the display.

 Here is a small video of the display so you get what I mean with flicker. 
 It seems that some video buffer isn't emptied or something as I'm seeing 
 old screens between the one that I should see
 https://youtu.be/me1_O4iaHB8


-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

I have not yet tried FunctionFS under 3.14. The only reason it was in the 
3.8 kernel was to support ADB, so you can remove it if you wish. I am 
unfamiliar with that particular error.

On Wednesday, March 18, 2015 at 6:51:03 AM UTC-4, Michael Gobbers wrote:

 Hi Andrew,

 I retried the 3.14 kernel.

 I'm getting the following error:

  WARNING: CPU: 0 PID: 110 at drivers/usb/gadget/f_fs.c:2595 
 ffs_ep0_write+0x44d/0x474()

 [  149.939235] Modules linked in:

 [  149.942448] CPU: 0 PID: 110 Comm: adbd Tainted: GW3.14.35+ 
 #6

 [  149.949616] [c00119c5] (unwind_backtrace) from [c000f63b] 
 (show_stack+0xb/0xc)

 [  149.957570] [c000f63b] (show_stack) from [c05005ab] 
 (dump_stack+0x4f/0x64)

 [  149.965181] [c05005ab] (dump_stack) from [c0030b4f] 
 (warn_slowpath_common+0x4b/0x68)

 [  149.973686] [c0030b4f] (warn_slowpath_common) from [c0030b7d] 
 (warn_slowpath_null+0x11/0x14)

 [  149.982940] [c0030b7d] (warn_slowpath_null) from [c036f70d] 
 (ffs_ep0_write+0x44d/0x474)

 [  149.991729] [c036f70d] (ffs_ep0_write) from [c00cafb1] 
 (vfs_write+0x6d/0x130)

 [  149.999599] [c00cafb1] (vfs_write) from [c00cb2c9] 
 (SyS_write+0x2d/0x64)

 [  150.006994] [c00cb2c9] (SyS_write) from [c000cc81] 
 (ret_fast_syscall+0x1/0x46)

 [  150.014950] ---[ end trace 3555ece349f08477 ]---

 [  151.039009] read descriptors

 [  151.042065] read strings
 I believe it has to do with the FunctionFS. What is it used for? Can I 
 disable it? I believe it is only used so that ADB would work right?

 To provide you with some extra info, I had to build the kernel with the 
 folowing modifications to the defconfig:

 I commented:
 # CONFIG_USB_G_NOKIA=m  //This led to an inconsistent state

 I included this:
 CONFIG_DMA_OMAP=y //This was a required dependency

 Cheers,
 Michael



 2015-03-18 2:39 GMT+01:00 Andrew Henderson hend...@icculus.org 
 javascript::

 Are you using an LCD cape? I have seen flickering similar to what you 
 described with the 3.8 kernel when I forced a video resolution via the 
 video= kernel command line option (in uEnv.txt in the boot partition) for 
 the LCD3/4/7 CircuitCo capes and the 4DCAPE-43T/70T capes from 4D Systems. 
 For those display capes, the resolution is pulled from the device tree 
 overlay for the cape automatically, so you should not specify a video 
 resolution. If you are using HDMI, you may not be getting the proper EDID 
 resolution information from your display. In that case, the TILCDC driver 
 will default to 1024x768, which your display (if it is an HDMI display) may 
 not properly support. Either way, I have seen that refresh problem when the 
 logical resolution that the TILCDC driver expects mismatches the physical 
 resolution of your display device.

 I have not seen that particular USB error before, but I also have not 
 worked with the 3.10 kernel on the BBB. I've gone straight from 3.8 to 
 3.13/14.

 Andrew 

 On Tuesday, March 17, 2015 at 4:45:42 PM UTC-4, Michael Gobbers wrote:

 Hi Andrew,

 Thanks for the reply. Indeed Keith Conger supplied me with the patches. 
 I have gotten a bit further now as I'm getting the hand of configuring 
 and building the kernel for the beaglebone black. I'm now able to boot all 
 the way to the android home screen.

 However, I have major graphical glitches. It seems that the boot 
 animation is being displayed together with the home screen. Their also 
 seemed to be a lot of flickering on the screen. So there is something 
 seriously wrong there.

 The biggest issue for me that I came across was the fact that my usb 
 host port didn't seem to work. So no mouse available there.
 Today I tried the 3.10 kernel and there I do not have the graphical 
 glitches. However, again there is no host port available.

 from the ftdi output I did find the following while booting the kernel:

 [2.725494] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with 
 status -517

 [2.733755] platform musb-hdrc.0.auto: Driver musb-hdrc requests probe 
 deferral

 Have you ever come across this error?




 -- 
 Michael Gobbers   http://be.linkedin.com/in/michaelgobbers
 +32477188592


 Desguinlei 6 - 2018 Antwerpen
  

-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

Hello Michael. I believe that Keith Conger supplied you with the 3.18 
backport drivers for Bluetooth, right? I have Keith's patches sitting in my 
review queue, but I haven't yet created a branch with them. The problem 
that I'm running into is that the 3.8 kernel has the capemgr in it, but the 
later kernels do not. So, Bluetooth drivers in the newer kernels aren't 
readily available for BBBAndroid without a lot of screwing around. The 
drivers that you need are available in the 3.14 kernel, but the 3.14 kernel 
does not have support for dynamic loading of device tree overlays in it. 
Only 3.8 has this feature, which is why I am sticking with 3.8 for 
BBBAndroid. I want to make it easy for people to try different hardware 
configurations and easily prototype Android interfacing code, though some 
features requiring the drivers from newer kernels (like Bluetooth drivers) 
aren't available because of this. 

You could try just dropping the 3.14 kernel into the BBBAndroid build 
process as you are doing, but you must make sure that the device tree 
(.dtb) in the boot partition matches the kernel. The FTDI serial output 
will tell you of any issues with the bootloader and help you diagnose these 
sorts of problems. If all of the lights are on, you are having a problem 
very early in the boot process. My guess is that it is a mismatch of some 
sort among the bootloader, uEnv.txt file, the device tree .dtb, and the 
kernel. You probably haven't gotten far enough along in the build process 
to worry about having the correct kernel modules installed in the root file 
system, but that shouldn't be a problem if you are using my makefile.  My 
makefile installs the modules into place for you.

Also, make sure that you have the Android staging drivers (binder, 
anonymous shared memory, low memory killer, etc.) enabled in you kernel 
configuration for the 3.14 kernel. You were asked about all of those 
options when you built the kernel because you were using a kernel 
configuration file for the 3.8 kernel with your 3.14 kernel. There are a 
number of mismatches in the options between the two kernels, so the kernel 
Kconfig system was asking you to sort out the differences.

Andrew


On Wednesday, March 11, 2015 at 3:00:40 PM UTC-4, mgob...@orcasolutions.be 
wrote:

 Hi Andrew, 

 Thanks for the great job you've doing on the beagleboard. 
 For the project I'm currently working on I included bluetooth support to 
 the build. However, it seems that the le functionality isn't working 
 because it relies on some modules not available in the 3.8 kernel. 

 Some people pointed out the I should upgrade to kernel 3.14. However, I'm 
 kind of I'm the dark here and I don't really know what I'm doing wrong. 

 Would it be possible to point me in the right direction? 

 Currently I modidified the repo manifest to fetch the beaglebone 3.14 
 kernel and replace it with the original bbbkernel in the manifest. I ran 
 the make oldconfig on the kernel to merge the 3.4 config with the new 3.14 
 config. However, after running the build I tried to boot it on the BBB and 
 it failed to boot. The 4 userleds seem to stay lit. 

 After doing the make oldconfig I had to enter a lot of new options. I'm 
 not really sure what I was doing there... 

 Cheers, 
 Michael 





-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[nventawi...@gmail.com]

Thank you so much Andrew,
you are really kind.  I will keep this extra packets for now.. I also
have to include the libs you used in your book to handle spi devices..
will keep in touch.

Gianmaria
Italy
On mar, 2015-03-17 at 13:20 -0700, Andrew Henderson wrote:
 Hello Gianmaria. Sorry for the delay in getting back to you on this.
 The .img files for the various Android partitions are generated as
 part of the BBBAndroid build process.  But, the makefile installs the
 kernel, firmware, and modules into the file system after the .img
 files are generated. I stay away from installing Android into the eMMC
 because I don't want to limit the size of the partitions to fit within
 the 2GB/4GB eMMC. That is why I target the microSD card for the
 BBBAndroid build scripts. You can use the .img files that are
 generated during the BBBAndroid build process and use fastboot to
 place the images onto the eMMC (as Chris's instructions show in the
 link that you mentioned). But, you may have to shrink the size of the
 images because I include a few extra packages (such as the i2ctools)
 that aren't in the usual AOSP packages.  Because of this, my images
 are bigger than normal and may not fit onto a 4GB eMMC as-is.
 
 
 
 
 On Monday, March 2, 2015 at 1:04:39 PM UTC-5, nvent...@gmail.com
 wrote:
 
 
 Hi Andrew,
 
 i found your git very usefull. Can you give me some
 information on how to create .img files and boot android
 copletly from eMMC? Something like 2net.co does here: 
 
 
 
 https://github.com/csimmonds/bbb-android-device-files/tree/kk4.4-fastboot
 
 
 
 Thank you in advance. 
 
 
 Regards,
 Gianmaria
 
 Il giorno giovedì 15 gennaio 2015 05:01:32 UTC+1, Andrew
 Henderson ha scritto:
 
 I don't have the various cape .dtbo overlay files
 copied into the image (aside from those statically
 built into the am335x-boneblack.dtb file in the dtbs
 directory of the boot (first) partition.  To add any
 overlays to your system, copy the necessary .dtbo
 files into /system/vendor/firmware directory of the
 rootfs (second) partition.  You can automatically load
 the overlay on boot by adding the appropriate commands
 to the init.{ro.hardware}.rc file in the root
 directory of the rootfs partition.  Just look in that
 file for the BBBAndroid comments and read them to
 see how to do this.
 
 
 
 After the overlay loading command, you can add
 commands to chmod the permissions on the appropriate
 files in the /dev filesystem to relax the permissions
 on the UART tty files to allow apps to access them.
  Just look in the init.{ro.hardware}.rc file for some
 examples (I chmod /dev/spidev* and the /dev/i2c*
 devices, for example). Ideally, you'd have a manager
 access such hardware resources on your behalf via the
 Android HAL.  But, for prototyping, it isn't a big
 deal to open these devices up and let apps talk to
 them directly via JNI.
 
 
 This is probably a good time to mention that I've
 recently put together a book which covers all the
 details involved in creating Android apps that talk
 directly to hardware.  It is Android Hardware
 Interfacing with the BeagleBone Black from Packt
 Publishing, and it is scheduled to go to print next
 month: 
 https://www.packtpub.com/hardware-and-creative/android-hardware-interfacing-beaglebone-black
 
 
 So, if you're still fighting with the details a few
 weeks from now, there will actually be a reference
 book to help you out (using BBBAndroid, too!).
 
 On Tuesday, January 13, 2015 at 4:29:20 PM UTC-5,
 ti...@emailbx.com wrote:
 
 Thanks a lot for creating this.
 
 I have got this image and the BBB now is
 running using a 4DLcd 7. 
 For my experiments, i'm trying to use UART4
 (as it's available in the headers of the LCD)
 so i installed an apk for serial
 testing 
 http://code.google.com/p/android-serialport-api/ but when I try to send some 
 info  I get the error You do not have read/write permission to the serial 
 port
 

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

Are you using an LCD cape? I have seen flickering similar to what you 
described with the 3.8 kernel when I forced a video resolution via the 
video= kernel command line option (in uEnv.txt in the boot partition) for 
the LCD3/4/7 CircuitCo capes and the 4DCAPE-43T/70T capes from 4D Systems. 
For those display capes, the resolution is pulled from the device tree 
overlay for the cape automatically, so you should not specify a video 
resolution. If you are using HDMI, you may not be getting the proper EDID 
resolution information from your display. In that case, the TILCDC driver 
will default to 1024x768, which your display (if it is an HDMI display) may 
not properly support. Either way, I have seen that refresh problem when the 
logical resolution that the TILCDC driver expects mismatches the physical 
resolution of your display device.

I have not seen that particular USB error before, but I also have not 
worked with the 3.10 kernel on the BBB. I've gone straight from 3.8 to 
3.13/14.

Andrew 

On Tuesday, March 17, 2015 at 4:45:42 PM UTC-4, Michael Gobbers wrote:

 Hi Andrew,

 Thanks for the reply. Indeed Keith Conger supplied me with the patches. 
 I have gotten a bit further now as I'm getting the hand of configuring and 
 building the kernel for the beaglebone black. I'm now able to boot all the 
 way to the android home screen.

 However, I have major graphical glitches. It seems that the boot animation 
 is being displayed together with the home screen. Their also seemed to be a 
 lot of flickering on the screen. So there is something seriously wrong 
 there.

 The biggest issue for me that I came across was the fact that my usb host 
 port didn't seem to work. So no mouse available there.
 Today I tried the 3.10 kernel and there I do not have the graphical 
 glitches. However, again there is no host port available.

 from the ftdi output I did find the following while booting the kernel:

 [2.725494] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with 
 status -517

 [2.733755] platform musb-hdrc.0.auto: Driver musb-hdrc requests probe 
 deferral

 Have you ever come across this error?


-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Michael Gobbers]

Hi Andrew,

Thanks for the reply. Indeed Keith Conger supplied me with the patches.
I have gotten a bit further now as I'm getting the hand of configuring and
building the kernel for the beaglebone black. I'm now able to boot all the
way to the android home screen.

However, I have major graphical glitches. It seems that the boot animation
is being displayed together with the home screen. Their also seemed to be a
lot of flickering on the screen. So there is something seriously wrong
there.

The biggest issue for me that I came across was the fact that my usb host
port didn't seem to work. So no mouse available there.
Today I tried the 3.10 kernel and there I do not have the graphical
glitches. However, again there is no host port available.

from the ftdi output I did find the following while booting the kernel:

[2.725494] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed
with status -517

[2.733755] platform musb-hdrc.0.auto: Driver musb-hdrc requests
probe deferral

Have you ever come across this error?




2015-03-17 21:32 GMT+01:00 Andrew Henderson hende...@icculus.org:

 Hello Michael. I believe that Keith Conger supplied you with the 3.18
 backport drivers for Bluetooth, right? I have Keith's patches sitting in my
 review queue, but I haven't yet created a branch with them. The problem
 that I'm running into is that the 3.8 kernel has the capemgr in it, but the
 later kernels do not. So, Bluetooth drivers in the newer kernels aren't
 readily available for BBBAndroid without a lot of screwing around. The
 drivers that you need are available in the 3.14 kernel, but the 3.14 kernel
 does not have support for dynamic loading of device tree overlays in it.
 Only 3.8 has this feature, which is why I am sticking with 3.8 for
 BBBAndroid. I want to make it easy for people to try different hardware
 configurations and easily prototype Android interfacing code, though some
 features requiring the drivers from newer kernels (like Bluetooth drivers)
 aren't available because of this.

 You could try just dropping the 3.14 kernel into the BBBAndroid build
 process as you are doing, but you must make sure that the device tree
 (.dtb) in the boot partition matches the kernel. The FTDI serial output
 will tell you of any issues with the bootloader and help you diagnose these
 sorts of problems. If all of the lights are on, you are having a problem
 very early in the boot process. My guess is that it is a mismatch of some
 sort among the bootloader, uEnv.txt file, the device tree .dtb, and the
 kernel. You probably haven't gotten far enough along in the build process
 to worry about having the correct kernel modules installed in the root file
 system, but that shouldn't be a problem if you are using my makefile.  My
 makefile installs the modules into place for you.

 Also, make sure that you have the Android staging drivers (binder,
 anonymous shared memory, low memory killer, etc.) enabled in you kernel
 configuration for the 3.14 kernel. You were asked about all of those
 options when you built the kernel because you were using a kernel
 configuration file for the 3.8 kernel with your 3.14 kernel. There are a
 number of mismatches in the options between the two kernels, so the kernel
 Kconfig system was asking you to sort out the differences.

 Andrew


 On Wednesday, March 11, 2015 at 3:00:40 PM UTC-4, mgob...@orcasolutions.be
 wrote:

 Hi Andrew,

 Thanks for the great job you've doing on the beagleboard.
 For the project I'm currently working on I included bluetooth support to
 the build. However, it seems that the le functionality isn't working
 because it relies on some modules not available in the 3.8 kernel.

 Some people pointed out the I should upgrade to kernel 3.14. However, I'm
 kind of I'm the dark here and I don't really know what I'm doing wrong.

 Would it be possible to point me in the right direction?

 Currently I modidified the repo manifest to fetch the beaglebone 3.14
 kernel and replace it with the original bbbkernel in the manifest. I ran
 the make oldconfig on the kernel to merge the 3.4 config with the new 3.14
 config. However, after running the build I tried to boot it on the BBB and
 it failed to boot. The 4 userleds seem to stay lit.

 After doing the make oldconfig I had to enter a lot of new options. I'm
 not really sure what I was doing there...

 Cheers,
 Michael






-- 
Michael Gobbers   http://be.linkedin.com/in/michaelgobbers
+32477188592


Desguinlei 6 - 2018 Antwerpen

-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

Hello Gianmaria. Sorry for the delay in getting back to you on this. The 
.img files for the various Android partitions are generated as part of the 
BBBAndroid build process.  But, the makefile installs the kernel, firmware, 
and modules into the file system after the .img files are generated. I stay 
away from installing Android into the eMMC because I don't want to limit 
the size of the partitions to fit within the 2GB/4GB eMMC. That is why I 
target the microSD card for the BBBAndroid build scripts. You can use the 
.img files that are generated during the BBBAndroid build process and use 
fastboot to place the images onto the eMMC (as Chris's instructions show in 
the link that you mentioned). But, you may have to shrink the size of the 
images because I include a few extra packages (such as the i2ctools) that 
aren't in the usual AOSP packages.  Because of this, my images are bigger 
than normal and may not fit onto a 4GB eMMC as-is.


On Monday, March 2, 2015 at 1:04:39 PM UTC-5, nvent...@gmail.com wrote:


 Hi Andrew,
 i found your git very usefull. Can you give me some information on how to 
 create .img files and boot android copletly from eMMC? Something like 
 2net.co does here: 

 https://github.com/csimmonds/bbb-android-device-files/tree/kk4.4-fastboot

 Thank you in advance. 

 Regards,
 Gianmaria

 Il giorno giovedì 15 gennaio 2015 05:01:32 UTC+1, Andrew Henderson ha 
 scritto:

 I don't have the various cape .dtbo overlay files copied into the image 
 (aside from those statically built into the am335x-boneblack.dtb file in 
 the dtbs directory of the boot (first) partition.  To add any overlays to 
 your system, copy the necessary .dtbo files into /system/vendor/firmware 
 directory of the rootfs (second) partition.  You can automatically load the 
 overlay on boot by adding the appropriate commands to the 
 init.{ro.hardware}.rc file in the root directory of the rootfs partition. 
  Just look in that file for the BBBAndroid comments and read them to see 
 how to do this.

 After the overlay loading command, you can add commands to chmod the 
 permissions on the appropriate files in the /dev filesystem to relax the 
 permissions on the UART tty files to allow apps to access them.  Just look 
 in the init.{ro.hardware}.rc file for some examples (I chmod /dev/spidev* 
 and the /dev/i2c* devices, for example). Ideally, you'd have a manager 
 access such hardware resources on your behalf via the Android HAL.  But, 
 for prototyping, it isn't a big deal to open these devices up and let apps 
 talk to them directly via JNI.

 This is probably a good time to mention that I've recently put together a 
 book which covers all the details involved in creating Android apps that 
 talk directly to hardware.  It is Android Hardware Interfacing with the 
 BeagleBone Black from Packt Publishing, and it is scheduled to go to print 
 next month: 
 https://www.packtpub.com/hardware-and-creative/android-hardware-interfacing-beaglebone-black

 So, if you're still fighting with the details a few weeks from now, there 
 will actually be a reference book to help you out (using BBBAndroid, too!).

 On Tuesday, January 13, 2015 at 4:29:20 PM UTC-5, ti...@emailbx.com 
 wrote:

 Thanks a lot for creating this.
 I have got this image and the BBB now is running using a 4DLcd 7. 
 For my experiments, i'm trying to use UART4 (as it's available in the 
 headers of the LCD) so i installed an apk for serial testing 
 http://code.google.com/p/android-serialport-api/ but when I try to send 
 some info  I get the error You do not have read/write permission to the 
 serial port

 I read that i have to enable muxing on the pins to enable uart4. How can 
 I do that in you image?

 Any info is appreciated.

 Thx

 On Saturday, November 15, 2014 at 3:25:58 PM UTC-6, Andrew Henderson 
 wrote:

 I have built a new microSD card image for BBBAndroid 
 (bbbandroid_111514.img), and it is now available for download.  Just 
 follow 
 the link at bbbandroid.org to download it.

 In this build, USB ADB support is working just fine.  I've been able to 
 connect with the BBB using both command-line ADB and ADB through the 
 Eclipse ADT under both Windows and Linux.  You can push/pull files, 
 install/reinstall apps, get logcat output, shell, etc. using the USB cable 
 that came with your BBB board.  If you want a root shell on Android, the 
 ADB shell is the way to go.

 I changed the USB ID to 18D1:4E23 for the BBB device when BBBAndroid is 
 being used.  These are the same USB vendor and device IDs as a Google 
 Nexus 
 S.  The reason that I changed this is to make life much easier for the 
 Windows users.  Each phone vendor provides their own drivers for USB ADB, 
 and it was difficult for the Windows users to get the drivers set up 
 properly.  This should make things much easier for them.  Linux users 
 never 
 had a problem with it, since their USB ADB worked right out of the box.

 I also shrunk the image to 7.6 GB to accommodate 

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

Hello Grayver.  Actually, USB cameras on the BBB are not something that I 
have any experience with. I do have support for V4L2 enabled in the kernel, 
and I have enabled USB camera support in the device/ti/BoardConfig.mk file 
for the Android build. But, I haven't given it a try to see how well it 
works. You may very well have the camera working, but without OpenGL ES to 
scale the captured video to the full screen size, it may not actually work 
in any standard camera app. If you have a USB camera that is known to work 
under Linux, you can give it a try and see how well it works out for you. 

My general rule is that if some device is supported under a Linux system 
with the 3.8 kernel on the BBB then it is supported under BBBAndroid with 
the 3.8 kernel. That doesn't mean that the Android apps will always play 
nice with your hardware, but the userspace interface to the device that is 
exposed by the kernel will be the same under Linux as it is under Android. 
 One of these days, I'm going to have to work with a USB camera under 
Android. But, until then, I can't give you any concrete recommendations. 
 Sorry. Your best bet is to check out what cameras people are using with 
OpenCV and then stick with one of those. If you need special modules loaded 
for a particular camera, you can place an insmod for the module or 
modules inside of the init.{ro.hardware}.rc file in the root file system of 
the BBBAndroid image.

Andrew

On Monday, March 16, 2015 at 1:50:21 PM UTC-4, grayv...@gmail.com wrote:

 Hi Andrew*,*

 I am trying to use the BBB for basic picture analysis with OpenCV over 
 Android OS.

 I was wondering, does this release support any basic usb cameras (are 
 there any drivers for known products)?

 So far i have found this 
 http://www.radiumboards.com/HD_Camera_Cape_for_BeagleBone_Black.php which 
 is a bit pricy.

 thank you very much,

 Grayver


-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[grayver110]

Hi Andrew*,*

I am trying to use the BBB for basic picture analysis with OpenCV over 
Android OS.

I was wondering, does this release support any basic usb cameras (are there 
any drivers for known products)?

So far i have found this 
http://www.radiumboards.com/HD_Camera_Cape_for_BeagleBone_Black.php which 
is a bit pricy.

thank you very much,

Grayver

On Sunday, September 28, 2014 at 6:14:24 PM UTC+3, 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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[mgobbers]

Hi Andrew,

Thanks for the great job you've doing on the beagleboard.
For the project I'm currently working on I included bluetooth support to the 
build. However, it seems that the le functionality isn't working because it 
relies on some modules not available in the 3.8 kernel.

Some people pointed out the I should upgrade to kernel 3.14. However, I'm kind 
of I'm the dark here and I don't really know what I'm doing wrong.

Would it be possible to point me in the right direction?

Currently I modidified the repo manifest to fetch the beaglebone 3.14 kernel 
and replace it with the original bbbkernel in the manifest. I ran the make 
oldconfig on the kernel to merge the 3.4 config with the new 3.14 config. 
However, after running the build I tried to boot it on the BBB and it failed to 
boot. The 4 userleds seem to stay lit.

After doing the make oldconfig I had to enter a lot of new options. I'm not 
really sure what I was doing there...

Cheers,
Michael



-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[nventawires]

Hi Andrew,
i found your git very usefull. Can you give me some information on how to 
create .img files and boot android copletly from eMMC? Something like 
2net.co does here: 

https://github.com/csimmonds/bbb-android-device-files/tree/kk4.4-fastboot

Thank you in advance. 

Regards,
Gianmaria

Il giorno giovedì 15 gennaio 2015 05:01:32 UTC+1, Andrew Henderson ha 
scritto:

 I don't have the various cape .dtbo overlay files copied into the image 
 (aside from those statically built into the am335x-boneblack.dtb file in 
 the dtbs directory of the boot (first) partition.  To add any overlays to 
 your system, copy the necessary .dtbo files into /system/vendor/firmware 
 directory of the rootfs (second) partition.  You can automatically load the 
 overlay on boot by adding the appropriate commands to the 
 init.{ro.hardware}.rc file in the root directory of the rootfs partition. 
  Just look in that file for the BBBAndroid comments and read them to see 
 how to do this.

 After the overlay loading command, you can add commands to chmod the 
 permissions on the appropriate files in the /dev filesystem to relax the 
 permissions on the UART tty files to allow apps to access them.  Just look 
 in the init.{ro.hardware}.rc file for some examples (I chmod /dev/spidev* 
 and the /dev/i2c* devices, for example). Ideally, you'd have a manager 
 access such hardware resources on your behalf via the Android HAL.  But, 
 for prototyping, it isn't a big deal to open these devices up and let apps 
 talk to them directly via JNI.

 This is probably a good time to mention that I've recently put together a 
 book which covers all the details involved in creating Android apps that 
 talk directly to hardware.  It is Android Hardware Interfacing with the 
 BeagleBone Black from Packt Publishing, and it is scheduled to go to print 
 next month: 
 https://www.packtpub.com/hardware-and-creative/android-hardware-interfacing-beaglebone-black

 So, if you're still fighting with the details a few weeks from now, there 
 will actually be a reference book to help you out (using BBBAndroid, too!).

 On Tuesday, January 13, 2015 at 4:29:20 PM UTC-5, ti...@emailbx.com wrote:

 Thanks a lot for creating this.
 I have got this image and the BBB now is running using a 4DLcd 7. 
 For my experiments, i'm trying to use UART4 (as it's available in the 
 headers of the LCD) so i installed an apk for serial testing 
 http://code.google.com/p/android-serialport-api/ but when I try to send 
 some info  I get the error You do not have read/write permission to the 
 serial port

 I read that i have to enable muxing on the pins to enable uart4. How can 
 I do that in you image?

 Any info is appreciated.

 Thx

 On Saturday, November 15, 2014 at 3:25:58 PM UTC-6, Andrew Henderson 
 wrote:

 I have built a new microSD card image for BBBAndroid 
 (bbbandroid_111514.img), and it is now available for download.  Just follow 
 the link at bbbandroid.org to download it.

 In this build, USB ADB support is working just fine.  I've been able to 
 connect with the BBB using both command-line ADB and ADB through the 
 Eclipse ADT under both Windows and Linux.  You can push/pull files, 
 install/reinstall apps, get logcat output, shell, etc. using the USB cable 
 that came with your BBB board.  If you want a root shell on Android, the 
 ADB shell is the way to go.

 I changed the USB ID to 18D1:4E23 for the BBB device when BBBAndroid is 
 being used.  These are the same USB vendor and device IDs as a Google Nexus 
 S.  The reason that I changed this is to make life much easier for the 
 Windows users.  Each phone vendor provides their own drivers for USB ADB, 
 and it was difficult for the Windows users to get the drivers set up 
 properly.  This should make things much easier for them.  Linux users never 
 had a problem with it, since their USB ADB worked right out of the box.

 I also shrunk the image to 7.6 GB to accommodate everyone that was 
 having difficulty writing the 8 GB image to their microSD cards that were 
 actually a little bit smaller than 8 GB.

 Andrew


 On Sunday, September 28, 2014 11:14:24 AM UTC-4, 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: 

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

I don't have the various cape .dtbo overlay files copied into the image 
(aside from those statically built into the am335x-boneblack.dtb file in 
the dtbs directory of the boot (first) partition.  To add any overlays to 
your system, copy the necessary .dtbo files into /system/vendor/firmware 
directory of the rootfs (second) partition.  You can automatically load the 
overlay on boot by adding the appropriate commands to the 
init.{ro.hardware}.rc file in the root directory of the rootfs partition. 
 Just look in that file for the BBBAndroid comments and read them to see 
how to do this.

After the overlay loading command, you can add commands to chmod the 
permissions on the appropriate files in the /dev filesystem to relax the 
permissions on the UART tty files to allow apps to access them.  Just look 
in the init.{ro.hardware}.rc file for some examples (I chmod /dev/spidev* 
and the /dev/i2c* devices, for example). Ideally, you'd have a manager 
access such hardware resources on your behalf via the Android HAL.  But, 
for prototyping, it isn't a big deal to open these devices up and let apps 
talk to them directly via JNI.

This is probably a good time to mention that I've recently put together a 
book which covers all the details involved in creating Android apps that 
talk directly to hardware.  It is Android Hardware Interfacing with the 
BeagleBone Black from Packt Publishing, and it is scheduled to go to print 
next 
month: 
https://www.packtpub.com/hardware-and-creative/android-hardware-interfacing-beaglebone-black

So, if you're still fighting with the details a few weeks from now, there 
will actually be a reference book to help you out (using BBBAndroid, too!).

On Tuesday, January 13, 2015 at 4:29:20 PM UTC-5, ti...@emailbx.com wrote:

 Thanks a lot for creating this.
 I have got this image and the BBB now is running using a 4DLcd 7. 
 For my experiments, i'm trying to use UART4 (as it's available in the 
 headers of the LCD) so i installed an apk for serial testing 
 http://code.google.com/p/android-serialport-api/ but when I try to send 
 some info  I get the error You do not have read/write permission to the 
 serial port

 I read that i have to enable muxing on the pins to enable uart4. How can I 
 do that in you image?

 Any info is appreciated.

 Thx

 On Saturday, November 15, 2014 at 3:25:58 PM UTC-6, Andrew Henderson wrote:

 I have built a new microSD card image for BBBAndroid 
 (bbbandroid_111514.img), and it is now available for download.  Just follow 
 the link at bbbandroid.org to download it.

 In this build, USB ADB support is working just fine.  I've been able to 
 connect with the BBB using both command-line ADB and ADB through the 
 Eclipse ADT under both Windows and Linux.  You can push/pull files, 
 install/reinstall apps, get logcat output, shell, etc. using the USB cable 
 that came with your BBB board.  If you want a root shell on Android, the 
 ADB shell is the way to go.

 I changed the USB ID to 18D1:4E23 for the BBB device when BBBAndroid is 
 being used.  These are the same USB vendor and device IDs as a Google Nexus 
 S.  The reason that I changed this is to make life much easier for the 
 Windows users.  Each phone vendor provides their own drivers for USB ADB, 
 and it was difficult for the Windows users to get the drivers set up 
 properly.  This should make things much easier for them.  Linux users never 
 had a problem with it, since their USB ADB worked right out of the box.

 I also shrunk the image to 7.6 GB to accommodate everyone that was having 
 difficulty writing the 8 GB image to their microSD cards that were actually 
 a little bit smaller than 8 GB.

 Andrew


 On Sunday, September 28, 2014 11:14:24 AM UTC-4, 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 

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[timo]

Thanks a lot for creating this.
I have got this image and the BBB now is running using a 4DLcd 7. 
For my experiments, i'm trying to use UART4 (as it's available in the 
headers of the LCD) so i installed an apk for serial 
testing http://code.google.com/p/android-serialport-api/ but when I try to 
send some info  I get the error You do not have read/write permission to 
the serial port

I read that i have to enable muxing on the pins to enable uart4. How can I 
do that in you image?

Any info is appreciated.

Thx

On Saturday, November 15, 2014 at 3:25:58 PM UTC-6, Andrew Henderson wrote:

 I have built a new microSD card image for BBBAndroid 
 (bbbandroid_111514.img), and it is now available for download.  Just follow 
 the link at bbbandroid.org to download it.

 In this build, USB ADB support is working just fine.  I've been able to 
 connect with the BBB using both command-line ADB and ADB through the 
 Eclipse ADT under both Windows and Linux.  You can push/pull files, 
 install/reinstall apps, get logcat output, shell, etc. using the USB cable 
 that came with your BBB board.  If you want a root shell on Android, the 
 ADB shell is the way to go.

 I changed the USB ID to 18D1:4E23 for the BBB device when BBBAndroid is 
 being used.  These are the same USB vendor and device IDs as a Google Nexus 
 S.  The reason that I changed this is to make life much easier for the 
 Windows users.  Each phone vendor provides their own drivers for USB ADB, 
 and it was difficult for the Windows users to get the drivers set up 
 properly.  This should make things much easier for them.  Linux users never 
 had a problem with it, since their USB ADB worked right out of the box.

 I also shrunk the image to 7.6 GB to accommodate everyone that was having 
 difficulty writing the 8 GB image to their microSD cards that were actually 
 a little bit smaller than 8 GB.

 Andrew


 On Sunday, September 28, 2014 11:14:24 AM UTC-4, 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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[idoprv]

Hi Andrew,
Maybe you can help me,I'm trying to use beaglebone black with a custom 
touch screen, so i tough that Android O.S would do the job in the best way. 
I've downloaded the prebuild Android 4.4.4 image but it didn't support the 
touch of the screen.
I Contact the company who made the screen and they told me i have to insert 
their driver into the Android kernel inorder it will support the touch in 
the screen.
So I've follow the link in http://2net.co.uk/ and got to the guide 
 https://github.com/csimmonds/bbb-android-device-files/tree/kk4.4-sdcard
and has they guid I'm willing to download the AOSP first and then the 
specific bbb device files, but after few days of trying to download the 
AOSP files (and in between increasing again  again my virtual machine) i 
got this last screen which I'm pretty frustrated about because I cant 
understand if the download is already over or not. and as I understand 
redownload means to start over the download again.
I'll be glad if someone could help me what do I do with the next screen? 
and do I even going the right way with the above steps?

Thnks,
Ido


On Sunday, September 28, 2014 6:14:24 PM UTC+3, 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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[idoprv]

Hi Andrew,
I'm not sure if I send it already but to make sure I send it again.
I'm trying to connect BBB to custom touch screen, I've tried with the 
custom O.S and it didn't work.
I though the best way to achive such a connection would be with Android 
O.S, so i've download the AOSP 4.4.4 prebuild image 
from http://2net.co.uk/tutorial/android-4.4-beaglebone and plugged it to 
the beaglebone black but it didn't work (I can see the image but the touch 
functionality doesn't work).
I've contact the screen manufacturer and they told me that I have to insert 
the driver into the Android kernel first and then build it and just then it 
suppose to work.

So I've tried to download the source of the AOSP as the guide 
in https://github.com/csimmonds/bbb-android-device-files/tree/kk4.4-sdcard 
says but then I just got stuck in the following attached imaged, its been 
like that for the last 55 hours, and I've not idea if it end already or it 
isn't but it seems that the download is stuck (as in the following image).

https://lh4.googleusercontent.com/-lA3FuyyTFN0/VKgiunL1CbI/AJA/rszWqRBwk_U/s1600/android%2Brepository%2Bisnt%2Bfinished.png


as I understood if i'll type the following command again:

repo sync -c

it will start the download all over again and it is pretty long download.
I'd like to know what can I do now? and do I in the right direction?

Thanks,
Ido

On Sunday, September 28, 2014 6:14:24 PM UTC+3, 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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

1. Your repo command for fetching the AOSP code is hanging up, which can be 
caused by a few different things.  Review the Source sync issues section 
of https://source.android.com/source/known-issues.html.  Also, ensure that 
you are using the latest version of git.  This does not mean that you 
apt-get git, this means that you check the version that you have, see if 
that is the latest version available from source, and the download the 
latest git source and get it built and running on your system.

2. The guide that you linked outlines the process for building KitKat 4.4.4 
with a 3.2 Linux kernel.  This is quite a different kernel than the 3.8 
kernel provided in BBBAndroid. 3.8 uses DRM and supports the BBB's capemgr, 
which is a very different approach than 3.2 uses.  If you need a guide to 
build KitKat with a 3.8 kernel, follow the guide on the bbbandroid.org 
website: http://bbbandroid.sourceforge.net/build.html.  If you are using a 
3.2 kernel with your Android, I can't help you troubleshoot drivers and 
such because I don't work with the older kernel versions.  The nice folks 
at https://code.google.com/p/rowboat/ are a better resource for 
troubleshooting 3.2 kernel issues.

3. What is the display? Who is the manufacturer? Can you provide a link to 
it?  How does the display connect to the BBB (cape, HDMI connector, other)? 
 What version of the kernel does the manufacturer supply drivers for? Does 
the manufacturer supply a device tree node for the display?  Did the 
display work with the BBBAndroid image, but without the touchscreen?  I 
have no idea what your display is and how it works, so I can't help you get 
it working.

Andrew

On Saturday, January 3, 2015 11:50:53 AM UTC-5, ido...@gmail.com wrote:

 Hi Andrew,
 Maybe you can help me,I'm trying to use beaglebone black with a custom 
 touch screen, so i tough that Android O.S would do the job in the best way. 
 I've downloaded the prebuild Android 4.4.4 image but it didn't support the 
 touch of the screen.
 I Contact the company who made the screen and they told me i have to 
 insert their driver into the Android kernel inorder it will support the 
 touch in the screen.
 So I've follow the link in http://2net.co.uk/ and got to the guide  
 https://github.com/csimmonds/bbb-android-device-files/tree/kk4.4-sdcard
 and has they guid I'm willing to download the AOSP first and then the 
 specific bbb device files, but after few days of trying to download the 
 AOSP files (and in between increasing again  again my virtual machine) i 
 got this last screen which I'm pretty frustrated about because I cant 
 understand if the download is already over or not. and as I understand 
 redownload means to start over the download again.
 I'll be glad if someone could help me what do I do with the next screen? 
 and do I even going the right way with the above steps?

 Thnks,
 Ido


-- 
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.

Re: [beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[William Hermans]

I realize I am kind of lurking on this thread,but could you posting large
console output please post these console outputs to a pastebin ?


I am interrested in debug information, but pastebin is surely better for
this sort of output.

On Mon, Dec 22, 2014 at 7:19 AM, Andrew Henderson hende...@icculus.org
wrote:

 Using the HDMI cable to connect the BBB to your DVI/HDMI display should
 work without an issue.  You do not need HDMI audio to use the Android
 image.  I have used it without an issue with the various LCD capes without
 audio, for example.  Using the ethernet LAN connection and USB mouse are
 also supported.

 I will need more information before I am able to help you.

 Can you supply a complete FTDI output from bootloader boot through to
 about 60 seconds?  The reason that I ask for this is because I need to see
 where the video resolution is being set in the TILCDC framebuffer driver.
 While there are a number of failed services in the logcat output that you
 provided in your other post, I need to see the results of the kernel
 booting output first before I can move on to helping you troubleshoot any
 user space issues.  The logcat output shows that you are well into the boot
 process of user space.  If anything is failing in kernel space, I need to
 know that first.

 Are you not seeing anything on your display?  One of the most common
 problems is the EDID block not being sent from your monitor to the BBB.
 When this happens, the TILCDC kernel driver will default to a resolution of
 1024x768 (which may not be supported by your monitor).  This results in a
 blank screen.  My first guess is that this is your problem (especially if
 you see it for both the old and new Android images).

 Are you stuck at the screen with the Android animation on it?  You
 should not be, from what I can see of your logcat output.


 On Friday, December 19, 2014 3:33:01 AM UTC-5, kiran...@gmail.com wrote:

 Hi andrew! i tried you images (old and new) for beagle bone black. But i
 am not getting booted into it.

 Is it required to connect Display, LAN, and USB mouse.
 If I use HDMI CABLE (sony erricsion) to connect my PC monitor, will it
 drive.

 the FTDI output:
 [6.038794] g_ffs: read descriptors
 [6.042738] g_ffs: read strings
 [6.060551]  gadget: g_ffs ready
 [6.064563] musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver
 [6.072874] musb-hdrc musb-hdrc.0.auto: new USB bus registered,
 assigned bus number 2
 [6.081893] usb usb2: New USB device found, idVendor=1d6b,
 idProduct=0002
 [6.089055] usb usb2: New USB device strings: Mfr=3, Product=2,
 SerialNumber=1
 [6.096608] usb usb2: Product: MUSB HDRC host driver
 [6.101795] usb usb2: Manufacturer: Linux 3.8.13+ musb-hcd
 [6.107524] usb usb2: SerialNumber: musb-hdrc.0.auto
 [6.114174] hub 2-0:1.0: USB hub found
 [6.118361] hub 2-0:1.0: 1 port detected
 shell@beagleboneblack:/ $ [6.293332] CAUTION: musb: Babble Interrupt
 Occurred
 [6.391168] CAUTION: musb: Babble Interrupt Occurred
 [   27.787048] warning: `zygote' uses 32-bit capabilities (legacy support
 in use)
 [   43.804027] healthd: battery l=0 v=0 t=0.0 h=1 st=1 chg=
 [   46.763599] net eth0: initializing cpsw version 1.12 (0)
 [   46.772805] net eth0: phy found : id is : 0x7c0f1
 [   46.789857] libphy: PHY 4a101000.mdio:01 not found
 [   46.794916] net eth0: phy 4a101000.mdio:01 not found on slave 1
 [   46.817629] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
 [   68.388050] init: sys_prop: permission denied uid:1003
  name:service.bootanim.exit

  --
 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.


-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[kiranvarma3]

Hi andrew! i tried you images (old and new) for beagle bone black. But i am 
not getting booted into it.

Is it required to connect Display, LAN, and USB mouse. 
If I use HDMI CABLE (sony erricsion) to connect my PC monitor, will it 
drive.

the FTDI output:
[6.038794] g_ffs: read descriptors
[6.042738] g_ffs: read strings
[6.060551]  gadget: g_ffs ready
[6.064563] musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver
[6.072874] musb-hdrc musb-hdrc.0.auto: new USB bus registered, assigned 
bus number 2
[6.081893] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[6.089055] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[6.096608] usb usb2: Product: MUSB HDRC host driver
[6.101795] usb usb2: Manufacturer: Linux 3.8.13+ musb-hcd
[6.107524] usb usb2: SerialNumber: musb-hdrc.0.auto
[6.114174] hub 2-0:1.0: USB hub found
[6.118361] hub 2-0:1.0: 1 port detected
shell@beagleboneblack:/ $ [6.293332] CAUTION: musb: Babble Interrupt 
Occurred
[6.391168] CAUTION: musb: Babble Interrupt Occurred
[   27.787048] warning: `zygote' uses 32-bit capabilities (legacy support 
in use)
[   43.804027] healthd: battery l=0 v=0 t=0.0 h=1 st=1 chg=
[   46.763599] net eth0: initializing cpsw version 1.12 (0)
[   46.772805] net eth0: phy found : id is : 0x7c0f1
[   46.789857] libphy: PHY 4a101000.mdio:01 not found
[   46.794916] net eth0: phy 4a101000.mdio:01 not found on slave 1
[   46.817629] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   68.388050] init: sys_prop: permission denied uid:1003 
 name:service.bootanim.exit

-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[kiranvarma3]

(  583): Initializing input manager, mUseDevInputEventForAudioJack=false
I/SystemServer(  583): Window Manager
I/WindowManager(  583): No existing display settings 
/data/system/display_settings.xml; starting empty
I/WindowManager(  583): No keyguard interface!
I/InputManager(  583): Starting input manager
I/SystemServer(  583): No Bluetooh Service (emulator)
I/SystemServer(  583): Input Method Service
E/EventHub(  583): could not get driver version for /dev/input/mice, Not a 
typewriter
W/InputMethodManagerService(  583): Couldn't create dir.: 
/data/system/inputmethod
D/EventHub(  583): No input device configuration file found for device 
'tps65217_pwr_but'.
W/EventHub(  583): Unable to disable kernel key repeat for 
/dev/input/event0: Function not implemented
I/EventHub(  583): New device: id=1, fd=87, path='/dev/input/event0', 
name='tps65217_pwr_but', classes=0x1, configuration='', 
keyLayout='/system/usr/keylayout/Generic.kl', 
keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, 
usingSuspendBlockIoctl=false, usingClockIoctl=true
I/InputReader(  583): Device added: id=-1, name='Virtual', 
sources=0x0301
I/InputReader(  583): Device added: id=1, name='tps65217_pwr_but', 
sources=0x0101
W/ResourceType(  583): Failure getting entry for 0x7f06 (t=5 e=0) in 
package 0 (error -75)
I/SystemServer(  583): Accessibility Manager
I/ActivityManager(  583): Config changes=1df8 {1.0 ?mcc?mnc en_US ldltr 
sw768dp w1024dp h768dp 160dpi xlrg land ?uimode ?night -touch -keyb/v/h 
-nav/h s.2}
I/InputReader(  583): Reconfiguring input devices.  changes=0x0004
I/ActivityManager(  583): Config changes=400 {1.0 ?mcc?mnc en_US ldltr 
sw768dp w1024dp h695dp 160dpi xlrg land ?uimode ?night -touch -keyb/v/h 
-nav/h s.3}
I/SystemServer(  583): Mount Service
D/MountService(  583): got storage path: /storage/sdcard0 description: 
Internal storage primary: true removable: false emulated: true mtpReserve: 
100 allowMassStorage: false maxFileSize: 0
D/MountService(  583): addVolumeLocked() StorageVolume:
D/MountService(  583): mStorageId=65537 mPath=/storage/emulated/0 
mDescriptionId=17040663
D/MountService(  583): mPrimary=true mRemovable=false mEmulated=true 
mMtpReserveSpace=100
D/MountService(  583): mAllowMassStorage=false mMaxFileSize=0 
mOwner=UserHandle{0} mUuid=null
D/MountService(  583): mUserLabel=null mState=null
D/MountService(  583): got storage path: /storage/sdcard1 description: SD 
card primary: false removable: true emulated: false mtpReserve: 0 
allowMassStorage: false maxFileSize: 0
D/MountService(  583): addVolumeLocked() StorageVolume:
D/MountService(  583): mStorageId=0 mPath=/storage/sdcard1 
mDescriptionId=17040664 mPrimary=false
D/MountService(  583): mRemovable=true mEmulated=false 
mMtpReserveSpace=0 mAllowMassStorage=false
D/MountService(  583): mMaxFileSize=0 mOwner=null mUuid=null 
mUserLabel=null mState=null
D/MountService(  583): got storage path: /storage/usb1 description: USB 
storage primary: false removable: true emulated: false mtpReserve: 0 
allowMassStorage: false maxFileSize: 0
D/MountService(  583): addVolumeLocked() StorageVolume:
D/MountService(  583): mStorageId=0 mPath=/storage/usb1 
mDescriptionId=17040665 mPrimary=false
D/MountService(  583): mRemovable=true mEmulated=false 
mMtpReserveSpace=0 mAllowMassStorage=false
D/MountService(  583): mMaxFileSize=0 mOwner=null mUuid=null 
mUserLabel=null mState=null
I/SystemServer(  583): LockSettingsService
I/SystemServer(  583): Device Policy
I/SystemServer(  583): Status Bar
I/SystemServer(  583): Clipboard Service
I/SystemServer(  583): NetworkManagement Service
I/SystemServer(  583): Text Service Manager Service
I/PackageManager(  583): No secure containers on sdcard
D/dalvikvm(  583): GC_CONCURRENT freed 253K, 8% free 4222K/4552K, paused 
4ms+53ms, total 310ms
D/dalvikvm(  583): WAIT_FOR_CONCURRENT_GC blocked 20ms
D/dalvikvm(  583): WAIT_FOR_CONCURRENT_GC blocked 8ms
D/dalvikvm(  583): WAIT_FOR_CONCURRENT_GC blocked 11ms
W/PackageManager(  583): Not granting permission 
android.permission.GLOBAL_SEARCH to package com.android.quicksearchbox 
(protectionLevel=18 flags=0x8be45)
I/SystemServer(  583): NetworkStats Service
W/PackageManager(  583): Unknown permission 
com.google.android.gallery3d.permission.GALLERY_PROVIDER in package 
com.android.bluetooth
W/PackageManager(  583): Unknown permission 
android.permission.MMS_SEND_OUTBOX_MSG in package com.android.bluetooth
W/PackageManager(  583): Unknown permission 
com.google.android.googleapps.permission.GOOGLE_AUTH in package 
com.android.providers.calendar
W/PackageManager(  583): Unknown permission 
com.google.android.googleapps.permission.GOOGLE_AUTH.cl in package 
com.android.providers.calendar
W/PackageManager(  583): Unknown permission 
com.google.android.googleapps.permission.GOOGLE_AUTH.mail in package 
com.android.calendar
W/PackageManager(  583): Not granting permission 

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

Using the HDMI cable to connect the BBB to your DVI/HDMI display should 
work without an issue.  You do not need HDMI audio to use the Android 
image.  I have used it without an issue with the various LCD capes without 
audio, for example.  Using the ethernet LAN connection and USB mouse are 
also supported.

I will need more information before I am able to help you.

Can you supply a complete FTDI output from bootloader boot through to about 
60 seconds?  The reason that I ask for this is because I need to see where 
the video resolution is being set in the TILCDC framebuffer driver.  While 
there are a number of failed services in the logcat output that you 
provided in your other post, I need to see the results of the kernel 
booting output first before I can move on to helping you troubleshoot any 
user space issues.  The logcat output shows that you are well into the boot 
process of user space.  If anything is failing in kernel space, I need to 
know that first.

Are you not seeing anything on your display?  One of the most common 
problems is the EDID block not being sent from your monitor to the BBB. 
 When this happens, the TILCDC kernel driver will default to a resolution 
of 1024x768 (which may not be supported by your monitor).  This results in 
a blank screen.  My first guess is that this is your problem (especially if 
you see it for both the old and new Android images).

Are you stuck at the screen with the Android animation on it?  You should 
not be, from what I can see of your logcat output.

On Friday, December 19, 2014 3:33:01 AM UTC-5, kiran...@gmail.com wrote:

 Hi andrew! i tried you images (old and new) for beagle bone black. But i 
 am not getting booted into it.

 Is it required to connect Display, LAN, and USB mouse. 
 If I use HDMI CABLE (sony erricsion) to connect my PC monitor, will it 
 drive.

 the FTDI output:
 [6.038794] g_ffs: read descriptors
 [6.042738] g_ffs: read strings
 [6.060551]  gadget: g_ffs ready
 [6.064563] musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver
 [6.072874] musb-hdrc musb-hdrc.0.auto: new USB bus registered, 
 assigned bus number 2
 [6.081893] usb usb2: New USB device found, idVendor=1d6b, 
 idProduct=0002
 [6.089055] usb usb2: New USB device strings: Mfr=3, Product=2, 
 SerialNumber=1
 [6.096608] usb usb2: Product: MUSB HDRC host driver
 [6.101795] usb usb2: Manufacturer: Linux 3.8.13+ musb-hcd
 [6.107524] usb usb2: SerialNumber: musb-hdrc.0.auto
 [6.114174] hub 2-0:1.0: USB hub found
 [6.118361] hub 2-0:1.0: 1 port detected
 shell@beagleboneblack:/ $ [6.293332] CAUTION: musb: Babble Interrupt 
 Occurred
 [6.391168] CAUTION: musb: Babble Interrupt Occurred
 [   27.787048] warning: `zygote' uses 32-bit capabilities (legacy support 
 in use)
 [   43.804027] healthd: battery l=0 v=0 t=0.0 h=1 st=1 chg=
 [   46.763599] net eth0: initializing cpsw version 1.12 (0)
 [   46.772805] net eth0: phy found : id is : 0x7c0f1
 [   46.789857] libphy: PHY 4a101000.mdio:01 not found
 [   46.794916] net eth0: phy 4a101000.mdio:01 not found on slave 1
 [   46.817629] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
 [   68.388050] init: sys_prop: permission denied uid:1003 
  name:service.bootanim.exit


-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[liku50]

Hi Andrew.

Could you please tell me how can i add dropbear support for android 4.4 
running on linux 3.2 kernel.

Looking for a quick response from your end..

On Sunday, 16 November 2014 02:55:58 UTC+5:30, Andrew Henderson wrote:

 I have built a new microSD card image for BBBAndroid 
 (bbbandroid_111514.img), and it is now available for download.  Just follow 
 the link at bbbandroid.org to download it.

 In this build, USB ADB support is working just fine.  I've been able to 
 connect with the BBB using both command-line ADB and ADB through the 
 Eclipse ADT under both Windows and Linux.  You can push/pull files, 
 install/reinstall apps, get logcat output, shell, etc. using the USB cable 
 that came with your BBB board.  If you want a root shell on Android, the 
 ADB shell is the way to go.

 I changed the USB ID to 18D1:4E23 for the BBB device when BBBAndroid is 
 being used.  These are the same USB vendor and device IDs as a Google Nexus 
 S.  The reason that I changed this is to make life much easier for the 
 Windows users.  Each phone vendor provides their own drivers for USB ADB, 
 and it was difficult for the Windows users to get the drivers set up 
 properly.  This should make things much easier for them.  Linux users never 
 had a problem with it, since their USB ADB worked right out of the box.

 I also shrunk the image to 7.6 GB to accommodate everyone that was having 
 difficulty writing the 8 GB image to their microSD cards that were actually 
 a little bit smaller than 8 GB.

 Andrew


 On Sunday, September 28, 2014 11:14:24 AM UTC-4, 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.

Re: [beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Adam Singer]

Excellent!

-- 
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.

Re: [beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[nishikantanayak1]

 Hi Robert,

  Thanks for the help ..

 Finally, I am Successful in booting the u-boot with the blank EEPROM . but 
now the kernel booting stopped at certain point, it hangs trying to mount 
the rootfs (/dev/mmcblk0p2). 

 *Waiting for root device /dev/mmcblk0p2...*

 after this print it got stuck over there.

I have already tried with BBB (without EEPROM) using the same build images 
and it also hangs at the same place. 

Any help in solving this will be appreciated

On Friday, October 31, 2014 7:36:21 PM UTC+5:30, RobertCNelson wrote:

 On Thu, Oct 30, 2014 at 10:50 PM,  nishikan...@gmail.com javascript: 
 wrote: 
  Hi Andrew, 
  
  Now we are using one customized board based on Beaglebone Black Design. 
 In 
  case of BBB TI is writing some board type configuration in the EEPROM, 
 so 
  during the Initial booting process it reads those information and 
 configures 
  the board accordingly. 
  
  As we are using one fresh board we don't have anything written into 
 the 
  EEPROM,  because of which it is failing at the U-boot every time with 
 some 
  errors like: 
  
  U-Boot SPL 2013.01.01-00129-g6d40c2a-dirty (Oct 30 2014 - 09:58:22) 
  Incorrect magic number (0x) in EEPROM 
  
  I have tried to skip the read_eeprom () in the u-boot  which reads the 
  EEPROM header for board type, also done the Pin muxing in 
  board/ti/am335x/mux.c but didn't get any better result out of this. 
  
  As per my knowledge if we will write the same Configuration into the 
 EEPROM 
  as BBB then the board will boot properly. but we want to avoid that 
  procedure. so could you please tell me is there any other method to 
 solve 
  this issue. 
  
  Looking for a quick response from your end .. 

 See this patch for reference (yes it's v2014.10) 

 It is what CircuitCo uses to boot blank eeprom boards. 


 https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2014.10/0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch
  

 Regards, 

 -- 
 Robert Nelson 
 http://www.rcn-ee.com/ 


-- 
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.

Re: [beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[nishikantanayak1]

In addition to my previous comment (posted on 03/11/2014)

I have also tested with v2014.10 and got the same output as before :

U-Boot SPL 2014.10 (Nov 03 2014 - 15:40:04)
Incorrect magic number (0x) in EEPROM
Could not get board ID.
Incorrect magic number (0x) in EEPROM
Could not get board ID.
Unknown board: assuming BeagleBone Black.Incorrect magic number 
(0x) in EEPROM
Could not get board ID.

I am getting these logs in every 1 minute(approx) in my FTDI Output.

On Friday, October 31, 2014 7:36:21 PM UTC+5:30, RobertCNelson wrote:

 On Thu, Oct 30, 2014 at 10:50 PM,  nishikan...@gmail.com javascript: 
 wrote: 
  Hi Andrew, 
  
  Now we are using one customized board based on Beaglebone Black Design. 
 In 
  case of BBB TI is writing some board type configuration in the EEPROM, 
 so 
  during the Initial booting process it reads those information and 
 configures 
  the board accordingly. 
  
  As we are using one fresh board we don't have anything written into 
 the 
  EEPROM,  because of which it is failing at the U-boot every time with 
 some 
  errors like: 
  
  U-Boot SPL 2013.01.01-00129-g6d40c2a-dirty (Oct 30 2014 - 09:58:22) 
  Incorrect magic number (0x) in EEPROM 
  
  I have tried to skip the read_eeprom () in the u-boot  which reads the 
  EEPROM header for board type, also done the Pin muxing in 
  board/ti/am335x/mux.c but didn't get any better result out of this. 
  
  As per my knowledge if we will write the same Configuration into the 
 EEPROM 
  as BBB then the board will boot properly. but we want to avoid that 
  procedure. so could you please tell me is there any other method to 
 solve 
  this issue. 
  
  Looking for a quick response from your end .. 

 See this patch for reference (yes it's v2014.10) 

 It is what CircuitCo uses to boot blank eeprom boards. 


 https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2014.10/0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch
  

 Regards, 

 -- 
 Robert Nelson 
 http://www.rcn-ee.com/ 


-- 
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.

Re: [beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[nishikantanayak1]

Thanks for the help Robert

I have done all the changes, whatever you have mentioned in the Patch file, 
but still the board is not booting up. I think only the *s_init() function 
(file:board/ti/am335x/board.c)* is keep on executing repeatedly, as i can 
see only this log i.e.* **Unknown board: assuming BeagleBone Black.* (*file: 
**board/ti/am335x/mux.c.) *in every 1 minute(approx.)

FYI:
As the u-boot source files what you are using and what i am using are not 
completely same so i did all the changes manually (instead of applying the 
patch directly).
e.g. --- /home/original/am335x_evm.h2014-11-03 09:49:54.061434173 +0530
+++ include/configs/am335x_evm.h2014-11-03 10:11:11.869458684 +0530
@@ -142,6 +142,8 @@
 run ramargs;  \
 bootm ${loadaddr}\0 \
 findfdt=\
+setenv fdtfile am335x-boneblack.dtb; \
+setenv fdtbase am335x-boneblack; \
 if test $board_name = A335BONE; then  \
 setenv fdtfile am335x-bone.dtb; fi;  \
 if test $board_name = A33515BB; then  \

so could you please help me out for solving this issue..

On Friday, October 31, 2014 7:36:21 PM UTC+5:30, RobertCNelson wrote:

 On Thu, Oct 30, 2014 at 10:50 PM,  nishikan...@gmail.com javascript: 
 wrote: 
  Hi Andrew, 
  
  Now we are using one customized board based on Beaglebone Black Design. 
 In 
  case of BBB TI is writing some board type configuration in the EEPROM, 
 so 
  during the Initial booting process it reads those information and 
 configures 
  the board accordingly. 
  
  As we are using one fresh board we don't have anything written into 
 the 
  EEPROM,  because of which it is failing at the U-boot every time with 
 some 
  errors like: 
  
  U-Boot SPL 2013.01.01-00129-g6d40c2a-dirty (Oct 30 2014 - 09:58:22) 
  Incorrect magic number (0x) in EEPROM 
  
  I have tried to skip the read_eeprom () in the u-boot  which reads the 
  EEPROM header for board type, also done the Pin muxing in 
  board/ti/am335x/mux.c but didn't get any better result out of this. 
  
  As per my knowledge if we will write the same Configuration into the 
 EEPROM 
  as BBB then the board will boot properly. but we want to avoid that 
  procedure. so could you please tell me is there any other method to 
 solve 
  this issue. 
  
  Looking for a quick response from your end .. 

 See this patch for reference (yes it's v2014.10) 

 It is what CircuitCo uses to boot blank eeprom boards. 


 https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2014.10/0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch
  

 Regards, 

 -- 
 Robert Nelson 
 http://www.rcn-ee.com/ 


-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[nishikantanayak1]

Hi Andrew,

Now we are using one customized board based on Beaglebone Black Design. In 
case of BBB TI is writing some board type configuration in the EEPROM, so 
during the Initial booting process it reads those information and 
configures the board accordingly.

As we are using one fresh board we don't have anything written into the 
EEPROM,  because of which it is failing at the U-boot every time with some 
errors like:

U-Boot SPL 2013.01.01-00129-g6d40c2a-dirty (Oct 30 2014 - 09:58:22)
Incorrect magic number (0x) in EEPROM

I have tried to skip the read_eeprom () in the u-boot  which reads the 
EEPROM header for board type, also done the Pin muxing in  
board/ti/am335x/mux.c 
but didn't get any better result out of this.

As per my knowledge if we will write the same Configuration into the EEPROM 
as BBB then the board will boot properly. but we want to avoid that 
procedure. so could you please tell me is there any other method to solve 
this issue.

Looking for a quick response from your end ..

On Sunday, September 28, 2014 8:44:24 PM 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.

Re: [beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Robert Nelson]

On Thu, Oct 30, 2014 at 10:50 PM,  nishikantanay...@gmail.com wrote:
 Hi Andrew,

 Now we are using one customized board based on Beaglebone Black Design. In
 case of BBB TI is writing some board type configuration in the EEPROM, so
 during the Initial booting process it reads those information and configures
 the board accordingly.

 As we are using one fresh board we don't have anything written into the
 EEPROM,  because of which it is failing at the U-boot every time with some
 errors like:

 U-Boot SPL 2013.01.01-00129-g6d40c2a-dirty (Oct 30 2014 - 09:58:22)
 Incorrect magic number (0x) in EEPROM

 I have tried to skip the read_eeprom () in the u-boot  which reads the
 EEPROM header for board type, also done the Pin muxing in
 board/ti/am335x/mux.c but didn't get any better result out of this.

 As per my knowledge if we will write the same Configuration into the EEPROM
 as BBB then the board will boot properly. but we want to avoid that
 procedure. so could you please tell me is there any other method to solve
 this issue.

 Looking for a quick response from your end ..

See this patch for reference (yes it's v2014.10)

It is what CircuitCo uses to boot blank eeprom boards.

https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2014.10/0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[liku50]

Hi Andrew,

Thanks for the reply.

The only log for zygote that i can see in my FTDI output is: 

[   23.539523] warning: `zygote' uses 32-bit capabilities (legacy support 
in use)

Then some other logs like:

[   44.074598] init: sys_prop: permission denied uid:1003  
name:service.bootanim.exit

Is this the expected output??

On Tuesday, 21 October 2014 06:49:52 UTC+5:30, Andrew Henderson wrote:

 I don't see any errors that are out of the ordinary in your FTDI output. 
  How long did you wait before giving up?  If there is a failure on the 
 first boot, you should see some sort of failure beyond that in the log. 
  You can also run logcat from the FTDI shell to get some more details.  If 
 you see that zygote is started in your log, you're well on your way.  It 
 takes several minutes on the first boot before the top level screen comes 
 up.  Until then, you just see the Android animation on the screen.

 The FTDI shell belong to the shell user and group, not root.  If you'd 
 like to use root, plug in your USB cable and use ADB to shell in to the 
 system.

 Andrew


 On Monday, October 20, 2014 3:26:22 AM UTC-4, lik...@gmail.com wrote:


 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
 

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

Yes, that is the expected output.  You're through most of the boot process 
if zygote is started.  Therefore, you aren't experiencing bootloader or 
kernel problems.

Can you describe the problem that you are seeing in more detail?  Do you 
see anything on the screen at all?  You should see the Android animation 
screen while the system is starting up.  If you aren't seeing anything at 
all on the screen, then you might be having HDMI issues (like a bad cable 
that isn't reporting EDID information fro your display to the BBB). Look 
back through your FTDI log and look for any messages regarding tilcdc.  If 
you see something like this:

[3.680634] tilcdc 4830e000.lcdc: found TDA19988
[3.686131] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[3.693072] [drm] No driver support for vblank timestamp query.
[3.699640] tilcdc 4830e000.lcdc: No connectors reported connected with 
modes
[3.707162] [drm] Cannot find any crtc or sizes - going 1024x768
[3.722056] Console: switching to colour frame buffer device 128x48
[3.733792] tilcdc 4830e000.lcdc: fb0:  frame buffer device

... then you are experiencing a cable problem.

If you can see the Android animation screen and that screen never exits, 
then let me know and we can troubleshoot from there.  But this:

[   44.074598] init: sys_prop: permission denied uid:1003  
name:service.bootanim.exit

... tells me that your animation screen finished and that the system booted 
up properly.

Andrew


On Tuesday, October 21, 2014 12:48:59 AM UTC-4, lik...@gmail.com wrote:

 Hi Andrew,

 Thanks for the reply.

 The only log for zygote that i can see in my FTDI output is: 

 [   23.539523] warning: `zygote' uses 32-bit capabilities (legacy support 
 in use)

 Then some other logs like:

 [   44.074598] init: sys_prop: permission denied uid:1003  
 name:service.bootanim.exit

 Is this the expected output??

 On Tuesday, 21 October 2014 06:49:52 UTC+5:30, Andrew Henderson wrote:

 I don't see any errors that are out of the ordinary in your FTDI output. 
  How long did you wait before giving up?  If there is a failure on the 
 first boot, you should see some sort of failure beyond that in the log. 
  You can also run logcat from the FTDI shell to get some more details.  If 
 you see that zygote is started in your log, you're well on your way.  It 
 takes several minutes on the first boot before the top level screen comes 
 up.  Until then, you just see the Android animation on the screen.

 The FTDI shell belong to the shell user and group, not root.  If you'd 
 like to use root, plug in your USB cable and use ADB to shell in to the 
 system.

 Andrew


 On Monday, October 20, 2014 3:26:22 AM UTC-4, lik...@gmail.com wrote:


 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: 

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[liku50]

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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

I don't see any errors that are out of the ordinary in your FTDI output. 
 How long did you wait before giving up?  If there is a failure on the 
first boot, you should see some sort of failure beyond that in the log. 
 You can also run logcat from the FTDI shell to get some more details.  If 
you see that zygote is started in your log, you're well on your way.  It 
takes several minutes on the first boot before the top level screen comes 
up.  Until then, you just see the Android animation on the screen.

The FTDI shell belong to the shell user and group, not root.  If you'd 
like to use root, plug in your USB cable and use ADB to shell in to the 
system.

Andrew


On Monday, October 20, 2014 3:26:22 AM UTC-4, lik...@gmail.com wrote:


 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 

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Lei Wang]

Andrew,

Thanks very much for the very detailed explanation on the character of the 
init.generic*.rc files pushing.

In regarding to the navigation bar, I am using an element14 BBB with 
Circuito LCD4. So I don't have leisure to change the resolution. However I 
can using the LCD panel on-board buttons to navigate back. So it is not a 
big deal at this moment.

As Adam Singer mentioned, I am really looking forward to the kernel 
3.10/3.14 version with SGX support. Because kernel 3.10 adds much improved 
robustness to the USB driver.

Thanks again!

Lei



On Sunday, October 12, 2014 10:41:47 PM UTC-4, Andrew Henderson wrote:

 One thing that I should note is that if you use ADB to push files over to 
 the BBB, you must be sure that the permissions of the file that you pushed 
 are set correctly after the transfer.  If you are pushing the 
 init.generic*.rc files over, you must do something like:

 $ adb shell
 root@beagleboneblack:/ # chmod 750 init.genericam33xx\(flatteneddevicetr.rc

 If the permissions are too permissive, the import command in init.rc 
 will refuse to include the init.generic*.rc file because it is a security 
 risk.  If the init.generic*.rc file isn't included, then ADB won't start, 
 and you are effectively prevented from using ADB at that point.  You'll 
 have to mount the EXT4 partition under Linux to fix the permissions.  Be 
 careful!

 Andrew

 On Sunday, October 12, 2014 9:50:55 PM UTC-4, Andrew Henderson wrote:

 The rootfs filesystem (the / filesystem) is set to read-only once you 
 reach the post-fs phase of boot.  This is why you can't ADB push to it.  
 I've been on the fence as to whether I should remount this as read-write, 
 and I suppose that I probably should.  Since I'm trying to open up this 
 Android a bit to make it easier for people to experiment with, it is 
 reasonable to do so.  It also allows the Windows people who can't easily 
 mount EXT4 to make changes to their Android system via ADB.

 Look at your init.genericam33xx(flatteneddevicetr.rc file at around line 
 36:

 # we will remap this as /storage/sdcard0 with the sdcard fuse tool
 mkdir /data/media 0770 media_rw media_rw
 chown media_rw media_rw /data/media

 # Set indication (checked by vold) that we have finished this action
 setprop vold.post_fs_data_done 1

 Right before that # Set indication ... line, add these two lines:

 # BBBAndroid: Remount the rootfs as rw for ADB push of files to /
 mount rootfs rootfs / rw remount

 This will remount / as read-write.  The original remount to read-only 
 occurs in init.rc, but you generally don't want to change the standard .rc 
 files, so I override all of the defaults in the platform-specific .rc 
 files.  I just pushed this change up to the repo: 
 https://github.com/hendersa/bbbandroid-vendor-ti-beagleboneblack-aosp

 I have not checked into the nav bar issue, but I know that I have seen it 
 in some resolutions and not in others.  Maybe try a different resolution?  
 I'll see it at 720x480, for example, when using HDMI.  But I won't see it 
 at the much higher resolutions (1920x1080, I think).  

 Andrew


 On Monday, October 13, 2014 1:13:44 AM UTC, Lei Wang wrote:

 Hi Andrew,

 I rebuild the BBBAndroid and created my own image. The ADB USB does work 
 after I replaced those (3) files you attached earlier. It is a very good 
 news. 
 But I did find out that I couldn't push file thru the ADB push. I tried 
 both the eclipse ADT and command line. Neither works. I've got some 
 information like,

 E:\Program Files\Android\android-sdk\platform-toolsadb push 
 init.genericam33xx
 (flatteneddevicetr.rc /init.genericam33xx(flatteneddevicetr.rc
 failed to copy 'init.genericam33xx(flatteneddevicetr.rc' to 
 '/init.genericam33xx
 (flatteneddevicetr.rc': Read-only file system

 Another minor issue is that the navigation bar is not shown in the 
 interface. I double checked the images you attached. I couldn't find 
 navigation bar either. I had same issue with TI's stock image (Kernel 3.2 
 based). I added a line to the  
 init.am335xevm.rc: setprop lcd.landscape true, which fixed the problem 
 (
 https://gitorious.org/rowboat/vendor-ti-am335xevm/commit/53391ade1b440e94c73db59444bf72529ce9ff32).
  
 I did the same to the init.generic*.rc file. However it didn't work this 
 time. I wonder if you know how to bring the navigation bar back.



 Thanks a lot!

 Lei


 On Sunday, October 12, 2014 1:03:54 PM UTC-4, Andrew Henderson wrote:

 I'll have to make the next pre-made image a little smaller than the 
 full capacity of my microSD cards because so many of the manufacturers are 
 being very liberal on exactly how many bytes they consider 8GB to be...

 I have a Realtek RTL8188CUS USB wifi dongle sitting here (an Edimax 
 EW-7811 of some sort, I believe), so I'll check into getting it set up for 
 you when I have a few minutes.  The kernel modules are actually already 
 sitting in the image, so you should be able to insmod them from 

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Altaf]

Hello, 
Great work appreciate. 
It would be awesome if you can add USB WiFi Support for Atheros AR9271  or 
Realtek RTL8188CUS Based Device

-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Adam Singer]

The suggested Wifi support would be awesome, its a common stack that people 
can get their hands on easily. ADB over USB would also be greatly 
appreciated when you publish a new image :) 

-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

I'll have to make the next pre-made image a little smaller than the full 
capacity of my microSD cards because so many of the manufacturers are being 
very liberal on exactly how many bytes they consider 8GB to be...

I have a Realtek RTL8188CUS USB wifi dongle sitting here (an Edimax EW-7811 
of some sort, I believe), so I'll check into getting it set up for you when 
I have a few minutes.  The kernel modules are actually already sitting in 
the image, so you should be able to insmod them from within the 
init.{ro.hardware}.rc file.

Andrew

On Sunday, October 12, 2014 12:45:54 PM UTC-4, Altaf wrote:

 Hello, 
 Great work appreciate. 
 It would be awesome if you can add USB WiFi Support for Atheros AR9271  
 or Realtek RTL8188CUS Based Device


-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Lei Wang]

Hi Andrew,

I rebuild the BBBAndroid and created my own image. The ADB USB does work 
after I replaced those (3) files you attached earlier. It is a very good 
news. 
But I did find out that I couldn't push file thru the ADB push. I tried 
both the eclipse ADT and command line. Neither works. I've got some 
information like,

E:\Program Files\Android\android-sdk\platform-toolsadb push 
init.genericam33xx
(flatteneddevicetr.rc /init.genericam33xx(flatteneddevicetr.rc
failed to copy 'init.genericam33xx(flatteneddevicetr.rc' to 
'/init.genericam33xx
(flatteneddevicetr.rc': Read-only file system

Another minor issue is that the navigation bar is not shown in the 
interface. I double checked the images you attached. I couldn't find 
navigation bar either. I had same issue with TI's stock image (Kernel 3.2 
based). I added a line to the  
init.am335xevm.rc: setprop lcd.landscape true, which fixed the problem 
(https://gitorious.org/rowboat/vendor-ti-am335xevm/commit/53391ade1b440e94c73db59444bf72529ce9ff32).
 
I did the same to the init.generic*.rc file. However it didn't work this 
time. I wonder if you know how to bring the navigation bar back.



Thanks a lot!

Lei


On Sunday, October 12, 2014 1:03:54 PM UTC-4, Andrew Henderson wrote:

 I'll have to make the next pre-made image a little smaller than the full 
 capacity of my microSD cards because so many of the manufacturers are being 
 very liberal on exactly how many bytes they consider 8GB to be...

 I have a Realtek RTL8188CUS USB wifi dongle sitting here (an Edimax 
 EW-7811 of some sort, I believe), so I'll check into getting it set up for 
 you when I have a few minutes.  The kernel modules are actually already 
 sitting in the image, so you should be able to insmod them from within the 
 init.{ro.hardware}.rc file.

 Andrew

 On Sunday, October 12, 2014 12:45:54 PM UTC-4, Altaf wrote:

 Hello, 
 Great work appreciate. 
 It would be awesome if you can add USB WiFi Support for Atheros AR9271  
 or Realtek RTL8188CUS Based Device



-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

The rootfs filesystem (the / filesystem) is set to read-only once you 
reach the post-fs phase of boot.  This is why you can't ADB push to it.  
I've been on the fence as to whether I should remount this as read-write, 
and I suppose that I probably should.  Since I'm trying to open up this 
Android a bit to make it easier for people to experiment with, it is 
reasonable to do so.  It also allows the Windows people who can't easily 
mount EXT4 to make changes to their Android system via ADB.

Look at your init.genericam33xx(flatteneddevicetr.rc file at around line 36:

# we will remap this as /storage/sdcard0 with the sdcard fuse tool
mkdir /data/media 0770 media_rw media_rw
chown media_rw media_rw /data/media

# Set indication (checked by vold) that we have finished this action
setprop vold.post_fs_data_done 1

Right before that # Set indication ... line, add these two lines:

# BBBAndroid: Remount the rootfs as rw for ADB push of files to /
mount rootfs rootfs / rw remount

This will remount / as read-write.  The original remount to read-only 
occurs in init.rc, but you generally don't want to change the standard .rc 
files, so I override all of the defaults in the platform-specific .rc 
files.  I just pushed this change up to the repo: 
https://github.com/hendersa/bbbandroid-vendor-ti-beagleboneblack-aosp

I have not checked into the nav bar issue, but I know that I have seen it 
in some resolutions and not in others.  Maybe try a different resolution?  
I'll see it at 720x480, for example, when using HDMI.  But I won't see it 
at the much higher resolutions (1920x1080, I think).  

Andrew


On Monday, October 13, 2014 1:13:44 AM UTC, Lei Wang wrote:

 Hi Andrew,

 I rebuild the BBBAndroid and created my own image. The ADB USB does work 
 after I replaced those (3) files you attached earlier. It is a very good 
 news. 
 But I did find out that I couldn't push file thru the ADB push. I tried 
 both the eclipse ADT and command line. Neither works. I've got some 
 information like,

 E:\Program Files\Android\android-sdk\platform-toolsadb push 
 init.genericam33xx
 (flatteneddevicetr.rc /init.genericam33xx(flatteneddevicetr.rc
 failed to copy 'init.genericam33xx(flatteneddevicetr.rc' to 
 '/init.genericam33xx
 (flatteneddevicetr.rc': Read-only file system

 Another minor issue is that the navigation bar is not shown in the 
 interface. I double checked the images you attached. I couldn't find 
 navigation bar either. I had same issue with TI's stock image (Kernel 3.2 
 based). I added a line to the  
 init.am335xevm.rc: setprop lcd.landscape true, which fixed the problem (
 https://gitorious.org/rowboat/vendor-ti-am335xevm/commit/53391ade1b440e94c73db59444bf72529ce9ff32).
  
 I did the same to the init.generic*.rc file. However it didn't work this 
 time. I wonder if you know how to bring the navigation bar back.



 Thanks a lot!

 Lei


 On Sunday, October 12, 2014 1:03:54 PM UTC-4, Andrew Henderson wrote:

 I'll have to make the next pre-made image a little smaller than the full 
 capacity of my microSD cards because so many of the manufacturers are being 
 very liberal on exactly how many bytes they consider 8GB to be...

 I have a Realtek RTL8188CUS USB wifi dongle sitting here (an Edimax 
 EW-7811 of some sort, I believe), so I'll check into getting it set up for 
 you when I have a few minutes.  The kernel modules are actually already 
 sitting in the image, so you should be able to insmod them from within the 
 init.{ro.hardware}.rc file.

 Andrew

 On Sunday, October 12, 2014 12:45:54 PM UTC-4, Altaf wrote:

 Hello, 
 Great work appreciate. 
 It would be awesome if you can add USB WiFi Support for Atheros AR9271  
 or Realtek RTL8188CUS Based Device



-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Lei Wang]

Andrew,

It seems that the pre-built image size (8,018,460,672 bytes) is slightly 
larger than a 8G uSD card size (7,939,784,704 bytes Sandisk HC). I had 
difficulty to write the image to the SD. 

Win32DiskImager (under Win7) complains; Image Writer (Ubuntu 12.04) also 
complains. dd command does not report error. However the BBB did not boot. 

Unfortunately I don't have 16G uSD on hand. 
I am in a process creating another virtual machine so I can build from 
source and remove some packages. 

I wonder if I am on the right path and there is some easier way out.

Thanks,

Lei

On Friday, October 10, 2014 8:47:46 AM UTC-4, Andrew Henderson wrote:

 Right now, I don't have any plans to flash the eMMC.  BBBAndroid is 
 currently intended to be a prototyping platform, so I'd prefer to make the 
 entire OS easily removable in case you need to mount it on a different 
 machine and fix any changes that you made to .rc, .dtbo, or .ko files in 
 the rootfs file system.  SGX support is planned, as soon as the 3.14/3.17 
 kernels move a little further along.  I plan on moving all of my projects 
 to the newer kernels once all of the features that I need are there.

 On Friday, October 10, 2014 12:10:18 AM UTC-4, Adam Singer wrote:

 Wow great job Andrew! Just ran with this image with ease. Is there 
 anything built in that can be used to flash to eMMC? Any plans to integrate 
 with the SGX drivers for better graphics drivers?



-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

Right now, I don't have any plans to flash the eMMC.  BBBAndroid is 
currently intended to be a prototyping platform, so I'd prefer to make the 
entire OS easily removable in case you need to mount it on a different 
machine and fix any changes that you made to .rc, .dtbo, or .ko files in 
the rootfs file system.  SGX support is planned, as soon as the 3.14/3.17 
kernels move a little further along.  I plan on moving all of my projects 
to the newer kernels once all of the features that I need are there.

On Friday, October 10, 2014 12:10:18 AM UTC-4, Adam Singer wrote:

 Wow great job Andrew! Just ran with this image with ease. Is there 
 anything built in that can be used to flash to eMMC? Any plans to integrate 
 with the SGX drivers for better graphics drivers?


-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Adam Singer]

Wow great job Andrew! Just ran with this image with ease. Is there anything 
built in that can be used to flash to eMMC? Any plans to integrate with the 
SGX drivers for better graphics drivers?

-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Lei Wang]

Hi Andrew, I will test it out and let you know the result. Thanks! -lei

On Monday, October 6, 2014 9:14:09 PM UTC-4, Andrew Henderson wrote:

 I accidentally attached an incorrect .rc file with some additional testing 
 material in it.  I'm attaching the proper one now.

 On Tuesday, October 7, 2014 1:10:50 AM UTC, Andrew Henderson wrote:

 I have not made a new premade image with USB ADB, but I have it working.  
 In your current BBBAndroid image, replace your uEnv.txt (/boot partition) 
 with the one I have attached.  Replace your two init.genericam33xx*.rc 
 files (/rootfs partition) with the two I have attached.  In addition to 
 getting USB ADB up and running, the main .rc file also changes some 
 permissions to make them more relaxed.  Now, i2c-tools work without 
 superuser privileges and it wakes up all four GPIO banks in case you need 
 to mmap() the GPIO registers.

 If you watch the FTDI output from the BBB (when the USB is plugged in at 
 boot), you'll see something like the following:

 [5.784087] CAUTION: musb: Babble Interrupt Occurred
 [5.854604] CAUTION: musb: Babble Interrupt Occurred
 [6.048723] CAUTION: musb: Babble Interrupt Occurred
 [6.119724] CAUTION: musb: Babble Interrupt Occurred
 [6.341756]  gadget: high-speed config #1: FunctionFS

 On your dev system side, use ADB to list the devices:

 $ adb devices
 List of devices attached
 BBBANDROID  device

 $ adb logcat
 ...
 D/AlarmScheduler(  917): No events found starting within 1 week.
 I/ActivityManager(  592): Waited long enough for: ServiceRecord{a5fb0900 
 u0 com.android.calendar/.alerts.InitAlarmsService}
 D/InitAlarmsService(  917): Clearing and rescheduling alarms.
 D/ConnectivityService(  592): Sampling interval elapsed, updating 
 statistics ..
 D/ConnectivityService(  592): Done.
 D/ConnectivityService(  592): Setting timer for 720seconds


 On Sunday, October 5, 2014 5:24:27 PM UTC, Andrew Henderson wrote:

 USB ADB is currently being worked on.  The image I provided builds in 
 FunctionFS support, but I have not yet made the modifications to the .rc 
 files to point ADB to FunctionFS.  I'm currently working on a few 
 modifications to the .rc files to make the image a bit more BBB friendly 
 for those interested in using it for Android hardware interfacing practice.

 On Sunday, October 5, 2014 12:31:33 PM UTC-4, Lei Wang wrote:

 May I ask if ADB over USB is supported in this release? Thanks very 
 much! -lei



-- 
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.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

I have not made a new premade image with USB ADB, but I have it working.  
In your current BBBAndroid image, replace your uEnv.txt (/boot partition) 
with the one I have attached.  Replace your two init.genericam33xx*.rc 
files (/rootfs partition) with the two I have attached.  In addition to 
getting USB ADB up and running, the main .rc file also changes some 
permissions to make them more relaxed.  Now, i2c-tools work without 
superuser privileges and it wakes up all four GPIO banks in case you need 
to mmap() the GPIO registers.

If you watch the FTDI output from the BBB (when the USB is plugged in at 
boot), you'll see something like the following:

[5.784087] CAUTION: musb: Babble Interrupt Occurred
[5.854604] CAUTION: musb: Babble Interrupt Occurred
[6.048723] CAUTION: musb: Babble Interrupt Occurred
[6.119724] CAUTION: musb: Babble Interrupt Occurred
[6.341756]  gadget: high-speed config #1: FunctionFS

On your dev system side, use ADB to list the devices:

$ adb devices
List of devices attached
BBBANDROID  device

$ adb logcat
...
D/AlarmScheduler(  917): No events found starting within 1 week.
I/ActivityManager(  592): Waited long enough for: ServiceRecord{a5fb0900 u0 
com.android.calendar/.alerts.InitAlarmsService}
D/InitAlarmsService(  917): Clearing and rescheduling alarms.
D/ConnectivityService(  592): Sampling interval elapsed, updating 
statistics ..
D/ConnectivityService(  592): Done.
D/ConnectivityService(  592): Setting timer for 720seconds


On Sunday, October 5, 2014 5:24:27 PM UTC, Andrew Henderson wrote:

 USB ADB is currently being worked on.  The image I provided builds in 
 FunctionFS support, but I have not yet made the modifications to the .rc 
 files to point ADB to FunctionFS.  I'm currently working on a few 
 modifications to the .rc files to make the image a bit more BBB friendly 
 for those interested in using it for Android hardware interfacing practice.

 On Sunday, October 5, 2014 12:31:33 PM UTC-4, Lei Wang wrote:

 May I ask if ADB over USB is supported in this release? Thanks very much! 
 -lei



-- 
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.
kernel_file=zImage

console=ttyO0,115200n8
#video_res=video=720x480-16@60
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext4 rootwait fixrtc
 
loadkernel=load mmc ${mmcdev}:${mmcpart} 0x8020 ${kernel_file}
loadfdt=load mmc ${mmcdev}:${mmcpart} 0x815f /dtbs/${fdtfile}
 
boot_ftd=run loadkernel; run loadfdt

mmcargs=setenv bootargs consoleblank=0 androidboot.console=ttyO0 mem=512M 
acpi=noirq vt.global_cursor_default=0 mpurate=1000 ${video_res} qemu=1 
console=${console} root=${mmcroot} rootfstype=${mmcrootfstype} init=/init 
ip=off g_ffs.idVendor=0x18d1 g_ffs.idProduct=0x4e26 
g_ffs.iSerialNumber=BBBANDROID

uenvcmd=run boot_ftd; run mmcargs; bootz 0x8020 - 0x815f



init.genericam33xx(flatteneddevicetr.rc
Description: Binary data


init.genericam33xx(flatteneddevicetr.usb.rc
Description: Binary data

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

I accidentally attached an incorrect .rc file with some additional testing 
material in it.  I'm attaching the proper one now.

On Tuesday, October 7, 2014 1:10:50 AM UTC, Andrew Henderson wrote:

 I have not made a new premade image with USB ADB, but I have it working.  
 In your current BBBAndroid image, replace your uEnv.txt (/boot partition) 
 with the one I have attached.  Replace your two init.genericam33xx*.rc 
 files (/rootfs partition) with the two I have attached.  In addition to 
 getting USB ADB up and running, the main .rc file also changes some 
 permissions to make them more relaxed.  Now, i2c-tools work without 
 superuser privileges and it wakes up all four GPIO banks in case you need 
 to mmap() the GPIO registers.

 If you watch the FTDI output from the BBB (when the USB is plugged in at 
 boot), you'll see something like the following:

 [5.784087] CAUTION: musb: Babble Interrupt Occurred
 [5.854604] CAUTION: musb: Babble Interrupt Occurred
 [6.048723] CAUTION: musb: Babble Interrupt Occurred
 [6.119724] CAUTION: musb: Babble Interrupt Occurred
 [6.341756]  gadget: high-speed config #1: FunctionFS

 On your dev system side, use ADB to list the devices:

 $ adb devices
 List of devices attached
 BBBANDROID  device

 $ adb logcat
 ...
 D/AlarmScheduler(  917): No events found starting within 1 week.
 I/ActivityManager(  592): Waited long enough for: ServiceRecord{a5fb0900 
 u0 com.android.calendar/.alerts.InitAlarmsService}
 D/InitAlarmsService(  917): Clearing and rescheduling alarms.
 D/ConnectivityService(  592): Sampling interval elapsed, updating 
 statistics ..
 D/ConnectivityService(  592): Done.
 D/ConnectivityService(  592): Setting timer for 720seconds


 On Sunday, October 5, 2014 5:24:27 PM UTC, Andrew Henderson wrote:

 USB ADB is currently being worked on.  The image I provided builds in 
 FunctionFS support, but I have not yet made the modifications to the .rc 
 files to point ADB to FunctionFS.  I'm currently working on a few 
 modifications to the .rc files to make the image a bit more BBB friendly 
 for those interested in using it for Android hardware interfacing practice.

 On Sunday, October 5, 2014 12:31:33 PM UTC-4, Lei Wang wrote:

 May I ask if ADB over USB is supported in this release? Thanks very 
 much! -lei



-- 
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.


init.genericam33xx(flatteneddevicetr.rc
Description: Binary data

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[Andrew Henderson]

USB ADB is currently being worked on.  The image I provided builds in 
FunctionFS support, but I have not yet made the modifications to the .rc 
files to point ADB to FunctionFS.  I'm currently working on a few 
modifications to the .rc files to make the image a bit more BBB friendly 
for those interested in using it for Android hardware interfacing practice.

On Sunday, October 5, 2014 12:31:33 PM UTC-4, Lei Wang wrote:

 May I ask if ADB over USB is supported in this release? Thanks very much! 
 -lei

-- 
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.