BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

[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

[Lei Wang]

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

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

[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

[Andrew Henderson]

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

[Lei Wang]

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

[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?

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

[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

[Altaf]

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

[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 :) 

[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

[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-tools>adb 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

[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

[Andrew Henderson]

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

[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

[lik...@gmail.com]

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

[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

[lik...@gmail.com]

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

[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

[nishikan...@gmail.com]

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 (0xffffffff) 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 ..

[Robert Nelson]

On Thu, Oct 30, 2014 at 10:50 PM, <nishikan...@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 (0xffffffff) 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/

[nishikan...@gmail.com]

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.h    2014-11-03 09:49:54.061434173 +0530
+++ include/configs/am335x_evm.h    2014-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..

[nishikan...@gmail.com]

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 (0xffffffff) in EEPROM

Could not get board ID.

Incorrect magic number (0xffffffff) in EEPROM

Could not get board ID.
Unknown board: assuming BeagleBone Black.Incorrect magic number (0xffffffff) 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:

[nishikan...@gmail.com]

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:

[Andrew Henderson]

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

[Adam Singer]

Excellent! 

[lik...@gmail.com]

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

[Andrew Henderson]

Adding additional packages to your Android build is independent of the kernel that you use.  So, whether you use a 3.2, 3.8, 3.14+ kernel on your BBB with Android, it is still the same.  After you clone the Android source repos and you have the complete Android source on your machine, look inside the "device" directory of the Android source and locate the directory for your device.  In my Android builds, this is the device/ti/beagleboneblack directory.  Open the device.mk file in this directory and look at it.  A variety of packages will be added to your device-specific build using lines like this:

PRODUCT_PACKAGES += \

    librs_jni \

    com.android.future.usb.accessory

You just need to add the following at the end of your file, but before any $(call ...) lines at the end of the file:

PRODUCT_PACKAGES += dropbear

Now that you've added the dropbear package to the build, you need to add the source code for dropbear.  All of the extra external packages like dropbear are in the "external" directory of the Android source tree.  If you don't have an "external/dropbear" directory there, you can fetch the dropbear git repo from AOSP.  When the dropbear package has been added and you've modified device.mk to include the dropbear package, run your lunch command again and rebuild the system.  It will now include the dropbear binaries.  Make sure that an Android.mk file exists in your external/dropbear directory, since this is the makefile used by the Android build system to build each Android component.  If you don't have an Android.mk file, you downloaded dropbear from somewhere on the internet, rather than pulling it from AOSP.

You'll need to create your SSL keys, copy all of the dropbear files over to your Android system, and modify the init.rc file to launch the dropbear daemon at the appropriate time.  Just google a bit and you'll see many people that are installing dropbear to their rooted Android systems.  I am not going to walk you through these steps because it varies from Android system to system and there are plenty of examples out there to help you.

Andrew

[kiran...@gmail.com]

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

[kiran...@gmail.com]

(  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=0x00000301

I/InputReader(  583): Device added: id=1, name='tps65217_pwr_but', sources=0x00000101

W/ResourceType(  583): Failure getting entry for 0x7f060000 (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=0x00000004

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 android.permission.ACCESS_DOWNLOAD_MANAGER to package com.android.browser (protectionLevel=18 flags=0x9be45)

W/PackageManager(  583): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.browser (protectionLevel=2 flags=0x9be45)

W/PackageManager(  583): Not granting permission android.permission.BIND_WALLPAPER to package com.android.camera2 (protectionLevel=18 flags=0x58bc45)

W/PackageManager(  583): Unknown permission com.google.android.gallery3d.permission.PICASA_STORE in package com.android.dreams.phototable

W/PackageManager(  583): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.settings

I/SystemServer(  583): NetworkPolicy Service

I/SystemServer(  583): Wi-Fi P2pService

W/PackageManager(  583): Unknown permission com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD in package com.android.development

W/PackageManager(  583): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.development

W/PackageManager(  583): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES in package com.android.development

W/PackageManager(  583): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.YouTubeUser in package com.android.development

W/PackageManager(  583): Not granting permission android.permission.DELETE_PACKAGES to package com.svox.pico (protectionLevel=18 flags=0x8be45)

W/PackageManager(  583): Not granting permission android.permission.DEVICE_POWER to package com.android.deskclock (protectionLevel=2 flags=0x48be45)

I/SystemServer(  583): Wi-Fi Service

D/WifiController(  583): isAirplaneModeOn = false, isWifiEnabled = false, isScanningAvailable = false

I/SystemServer(  583): Connectivity Service

D/ConnectivityService(  583): ConnectivityService starting up

D/ConnectivityService(  583): wifiOnly=false

E/ConnectivityService(  583): Ignoring protectedNetwork 10

E/ConnectivityService(  583): Ignoring protectedNetwork 11

E/ConnectivityService(  583): Ignoring protectedNetwork 12

E/ConnectivityService(  583): Ignoring protectedNetwork 14

D/CommandListener(   92): Setting iface cfg

D/CommandListener(   92): Trying to bring up eth0

D/dalvikvm(  583): GC_CONCURRENT freed 314K, 9% free 4357K/4752K, paused 4ms+66ms, total 243ms

I/WifiService(  583): WifiService starting up with Wi-Fi disabled

D/WifiWatchdogStateMachine(  583): Disabling poor network avoidance for wi-fi only device

I/SystemServer(  583): Network Service Discovery Service

D/NsdService(  583): Network service discovery enabled true

I/SystemServer(  583): UpdateLock Service

I/SystemServer(  583): Notification Manager

I/SystemServer(  583): Device Storage Monitor

I/SystemServer(  583): Location Manager

I/SystemServer(  583): Country Detector

I/SystemServer(  583): Search Service

I/SystemServer(  583): DropBox Service

I/SystemServer(  583): Wallpaper Service

I/SystemServer(  583): Audio Service

I/MediaFocusControl(  583):   Remote Control   registerMediaButtonIntent() for PendingIntent{a5d8f7a0: PendingIntentRecord{a5eca0a8 android broadcastIntent}}

I/SystemServer(  583): Dock Observer

W/DockObserver(  583): This kernel does not have dock station support

I/SystemServer(  583): Wired Accessory Manager

W/WiredAccessoryManager(  583): This kernel does not have wired headset support

W/WiredAccessoryManager(  583): This kernel does not have usb audio support

W/WiredAccessoryManager(  583): This kernel does not have HDMI audio support

I/SystemServer(  583): USB Service

D/dalvikvm(  583): GC_CONCURRENT freed 293K, 8% free 4512K/4884K, paused 4ms+3ms, total 155ms

I/SystemServer(  583): Serial Service

I/SystemServer(  583): Twilight Service

I/SystemServer(  583): UI Mode Manager Service

I/SystemServer(  583): Backup Service

V/BackupManagerService(  583): Initializing package tracking

V/BackupManagerService(  583): No ancestral data

V/BackupManagerService(  583): addPackageParticipantsLocked: all

I/BackupManagerService(  583): Scheduling backup for new app com.android.calendar

D/BackupManagerService(  583): Now staging backup of com.android.calendar

I/BackupManagerService(  583): Scheduling backup for new app com.android.browser

D/BackupManagerService(  583): Now staging backup of com.android.browser

I/BackupManagerService(  583): Scheduling backup for new app com.android.providers.userdictionary

D/BackupManagerService(  583): Now staging backup of com.android.providers.userdictionary

I/BackupManagerService(  583): Scheduling backup for new app com.android.sharedstoragebackup

D/BackupManagerService(  583): Now staging backup of com.android.sharedstoragebackup

I/BackupManagerService(  583): Scheduling backup for new app android

D/BackupManagerService(  583): Now staging backup of android

I/BackupManagerService(  583): Scheduling backup for new app com.android.providers.settings

D/BackupManagerService(  583): Now staging backup of com.android.providers.settings

V/BackupManagerService(  583): Starting with transport android/com.android.internal.backup.LocalTransport

V/BackupManagerService(  583): Found transports: 1

I/BackupManagerService(  583): Binding to transport host ComponentInfo{android/com.android.internal.backup.LocalTransportService}

I/BackupManagerService(  583): Found stale backup journal, scheduling

I/BackupManagerService(  583):   com.android.calendar

I/BackupManagerService(  583):   com.android.browser

I/BackupManagerService(  583):   com.android.providers.userdictionary

I/BackupManagerService(  583):   com.android.sharedstoragebackup

I/BackupManagerService(  583):   android

I/BackupManagerService(  583):   com.android.providers.settings

I/BackupManagerService(  583): Backup enabled => false

I/BackupManagerService(  583): Opting out of backup

I/SystemServer(  583): AppWidget Service

I/SystemServer(  583): Recognition Service

I/SystemServer(  583): DiskStats Service

I/SystemServer(  583): SamplingProfiler Service

I/SystemServer(  583): NetworkTimeUpdateService

I/SystemServer(  583): CommonTimeManagementService

I/SystemServer(  583): CertBlacklister

I/SystemServer(  583): Dreams Service

I/SystemServer(  583): Assets Atlas Service

I/SystemServer(  583): IdleMaintenanceService

I/SystemServer(  583): Print Service

I/SystemServer(  583): Media Router Service

I/WindowManager(  583): SAFE MODE not enabled

D/dalvikvm(  583): JIT started for system_server

D/Atlas   (  583): Loaded configuration: SliceMinArea (768x768) flags=0x2 count=25

W/AssetAtlasService(  583): Could not find EGL configuration

D/Atlas   (  583): Rendered atlas in 46.91ms (42.41+4.50ms)

I/Zygote  (  583): Process: zygote socket opened

I/ActivityManager(  583): Start proc com.android.systemui for service com.android.keyguard/.KeyguardService: pid=644 uid=10010 gids={50010, 1028, 1015, 1035, 3002, 3001}

V/KeyguardServiceDelegate(  583): *** Keyguard started

V/KeyguardServiceDelegate(  583): onSystemReady() called before keyguard service was ready

W/SystemServer(  583): ***********************************************

E/lights  (  583): write_int failed to open /sys/class/backlight/pwm-backlight/brightness

F/SystemServer(  583): BOOT FAILURE making Package Manager Service ready

F/SystemServer(  583): java.lang.SecurityException: Unable to find app for caller android.app.ActivityThread$ApplicationThread@a5e5f818 (pid=583) when registering receiver android.app.LoadedApk$ReceiverDispatcher$InnerReceiver@a5e600c0

F/SystemServer(  583):  at com.android.server.am.ActivityManagerService.registerReceiver(ActivityManagerService.java:13021)

F/SystemServer(  583):  at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1450)

F/SystemServer(  583):  at android.app.ContextImpl.registerReceiverAsUser(ContextImpl.java:1425)

F/SystemServer(  583):  at com.android.internal.content.PackageMonitor.register(PackageMonitor.java:84)

F/SystemServer(  583):  at com.android.server.pm.UserManagerService.systemReady(UserManagerService.java:237)

F/SystemServer(  583):  at com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:10476)

F/SystemServer(  583):  at com.android.server.ServerThread.initAndLoop(SystemServer.java:893)

F/SystemServer(  583):  at com.android.server.SystemServer.main(SystemServer.java:1179)

F/SystemServer(  583):  at java.lang.reflect.Method.invokeNative(Native Method)

F/SystemServer(  583):  at java.lang.reflect.Method.invoke(Method.java:515)

F/SystemServer(  583):  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785)

F/SystemServer(  583):  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601)

F/SystemServer(  583):  at dalvik.system.NativeStart.main(Native Method)

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/AppOps  (  583): Pruning old package media/1013: new uid=-1

I/ActivityManager(  583): System now ready

I/SystemServer(  583): Making services ready

E/MountService(  583): Boot-time mount failed (-1)

E/MountService(  583): Boot-time mount failed (-1)

D/NetworkManagementService(  583): not enabling bandwidth control

W/MountService(  583): Duplicate state transition (mounted -> mounted) for /storage/emulated/0

I/iptables(   92): iptables terminated by exit(3)

E/Netd    (   92): exec() res=0, status=768 for /system/bin/iptables -F fw_INPUT

I/ip6tables(   92): ip6tables terminated by exit(3)

E/Netd    (   92): exec() res=0, status=768 for /system/bin/ip6tables -F fw_INPUT

I/iptables(   92): iptables terminated by exit(3)

E/Netd    (   92): exec() res=0, status=768 for /system/bin/iptables -F fw_OUTPUT

I/ip6tables(   92): ip6tables terminated by exit(3)

E/Netd    (   92): exec() res=0, status=768 for /system/bin/ip6tables -F fw_OUTPUT

I/iptables(   92): iptables terminated by exit(3)

E/Netd    (   92): exec() res=0, status=768 for /system/bin/iptables -F fw_FORWARD

I/ip6tables(   92): ip6tables terminated by exit(3)

E/Netd    (   92): exec() res=0, status=768 for /system/bin/ip6tables -F fw_FORWARD

W/SystemServer(  583): ***********************************************

F/SystemServer(  583): BOOT FAILURE making Network Managment Service ready

F/SystemServer(  583): java.lang.IllegalStateException: command '5 firewall disable' failed with '400 5 Firewall command failed'

F/SystemServer(  583):  at com.android.server.NetworkManagementService.setFirewallEnabled(NetworkManagementService.java:1617)

F/SystemServer(  583):  at com.android.server.NetworkManagementService.prepareNativeDaemon(NetworkManagementService.java:401)

F/SystemServer(  583):  at com.android.server.NetworkManagementService.systemReady(NetworkManagementService.java:224)

F/SystemServer(  583):  at com.android.server.ServerThread$2.run(SystemServer.java:961)

F/SystemServer(  583):  at com.android.server.am.ActivityManagerService.systemReady(ActivityManagerService.java:9368)

F/SystemServer(  583):  at com.android.server.ServerThread.initAndLoop(SystemServer.java:938)

F/SystemServer(  583):  at com.android.server.SystemServer.main(SystemServer.java:1179)

F/SystemServer(  583):  at java.lang.reflect.Method.invokeNative(Native Method)

F/SystemServer(  583):  at java.lang.reflect.Method.invoke(Method.java:515)

F/SystemServer(  583):  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785)

F/SystemServer(  583):  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601)

F/SystemServer(  583):  at dalvik.system.NativeStart.main(Native Method)

F/SystemServer(  583): Caused by: com.android.server.NativeDaemonConnector$NativeDaemonFailureException: command '5 firewall disable' failed with '400 5 Firewall command failed'

F/SystemServer(  583):  at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:391)

F/SystemServer(  583):  at com.android.server.NativeDaemonConnector.executeForList(NativeDaemonConnector.java:327)

F/SystemServer(  583):  at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:292)

F/SystemServer(  583):  at com.android.server.NetworkManagementService.setFirewallEnabled(NetworkManagementService.java:1614)

F/SystemServer(  583):  ... 11 more

W/NetworkStats(  583): bandwidth controls disabled, unable to track stats

W/NetworkPolicy(  583): bandwidth controls disabled, unable to enforce policy

I/iptables(   92): iptables terminated by exit(3)

E/Netd    (   92): exec() res=0, status=768 for /system/bin/iptables -F fw_INPUT

I/ip6tables(   92): ip6tables terminated by exit(3)

E/Netd    (   92): exec() res=0, status=768 for /system/bin/ip6tables -F fw_INPUT

I/iptables(   92): iptables terminated by exit(3)

E/Netd    (   92): exec() res=0, status=768 for /system/bin/iptables -F fw_OUTPUT

I/ip6tables(   92): ip6tables terminated by exit(3)

E/Netd    (   92): exec() res=0, status=768 for /system/bin/ip6tables -F fw_OUTPUT

I/iptables(   92): iptables terminated by exit(3)

E/Netd    (   92): exec() res=0, status=768 for /system/bin/iptables -F fw_FORWARD

I/ip6tables(   92): ip6tables terminated by exit(3)

E/Netd    (   92): exec() res=0, status=768 for /system/bin/ip6tables -F fw_FORWARD

W/SystemServer(  583): ***********************************************

F/SystemServer(  583): BOOT FAILURE making Connectivity Service ready

F/SystemServer(  583): java.lang.IllegalStateException: command '6 firewall disable' failed with '400 6 Firewall command failed'

F/SystemServer(  583):  at com.android.server.NetworkManagementService.setFirewallEnabled(NetworkManagementService.java:1617)

F/SystemServer(  583):  at com.android.server.ConnectivityService.setLockdownTracker(ConnectivityService.java:3966)

F/SystemServer(  583):  at com.android.server.ConnectivityService.updateLockdownVpn(ConnectivityService.java:3941)

F/SystemServer(  583):  at com.android.server.ConnectivityService.systemReady(ConnectivityService.java:2285)

F/SystemServer(  583):  at com.android.server.ServerThread$2.run(SystemServer.java:976)

F/SystemServer(  583):  at com.android.server.am.ActivityManagerService.systemReady(ActivityManagerService.java:9368)

F/SystemServer(  583):  at com.android.server.ServerThread.initAndLoop(SystemServer.java:938)

F/SystemServer(  583):  at com.android.server.SystemServer.main(SystemServer.java:1179)

F/SystemServer(  583):  at java.lang.reflect.Method.invokeNative(Native Method)

F/SystemServer(  583):  at java.lang.reflect.Method.invoke(Method.java:515)

F/SystemServer(  583):  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785)

F/SystemServer(  583):  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601)

F/SystemServer(  583):  at dalvik.system.NativeStart.main(Native Method)

F/SystemServer(  583): Caused by: com.android.server.NativeDaemonConnector$NativeDaemonFailureException: command '6 firewall disable' failed with '400 6 Firewall command failed'

F/SystemServer(  583):  at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:391)

F/SystemServer(  583):  at com.android.server.NativeDaemonConnector.executeForList(NativeDaemonConnector.java:327)

F/SystemServer(  583):  at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:292)

F/SystemServer(  583):  at com.android.server.NetworkManagementService.setFirewallEnabled(NetworkManagementService.java:1614)

F/SystemServer(  583):  ... 12 more

D/dalvikvm(  583): GC_CONCURRENT freed 305K, 8% free 4720K/5100K, paused 4ms+4ms, total 367ms

D/dalvikvm(  583): WAIT_FOR_CONCURRENT_GC blocked 51ms

D/dalvikvm(  583): WAIT_FOR_CONCURRENT_GC blocked 32ms

I/ActivityManager(  583): Config changes=200 {1.0 ?mcc?mnc en_US ldltr sw768dp w1024dp h695dp 160dpi xlrg land -touch -keyb/v/h -nav/h s.4}

W/RecognitionManagerService(  583): no available voice recognition services found for user 0

W/InputMethodManagerService(  583): Ignoring setImeWindowStatus of uid 1000 token: null

V/KeyguardService(  644): onCreate()

E/WVMExtractor(   97): Failed to open libwvm.so

W/ResourceType(  583): Failure getting entry for 0x7f060000 (t=5 e=0) in package 0 (error -75)

I/ActivityManager(  583): Start proc com.android.inputmethod.latin for service com.android.inputmethod.latin/.LatinIME: pid=687 uid=10040 gids={50040, 1028, 1015}

V/InputMethodManagerService(  583): Adding window token: android.os.Binder@a5ef0ac8

E/cutils-trace(   97): Error opening trace file: Permission denied (13)

W/GpsLocationProvider(  583): Could not open GPS configuration file /etc/gps.conf

W/LocationManagerService(  583): no network location provider found

D/SystemUIService(  644): loading: class com.android.systemui.recent.Recents

D/SystemUIService(  644): running: com.android.systemui.recent.Recents@a5cf2ad0

D/SystemUIService(  644): loading: class com.android.systemui.statusbar.SystemBars

D/SystemUIService(  644): running: com.android.systemui.statusbar.SystemBars@a5cf30b8

E/LocationManagerService(  583): no geocoder provider found

D/SystemUIService(  644): loading: class com.android.systemui.usb.StorageNotification

D/SystemUIService(  644): running: com.android.systemui.usb.StorageNotification@a5cf4e78

D/SystemUIService(  644): loading: class com.android.systemui.power.PowerUI

D/SystemUIService(  644): running: com.android.systemui.power.PowerUI@a5cf64d8

D/SystemUIService(  644): loading: class com.android.systemui.media.RingtonePlayer

D/SystemUIService(  644): running: com.android.systemui.media.RingtonePlayer@a5cf71d8

D/SystemUIService(  644): loading: class com.android.systemui.settings.SettingsUI

E/FlpHardwareProvider(  583): Error hw_get_module 'flp': -2

E/LocationManagerService(  583): No FusedProvider found.

E/FlpHardwareProvider(  583): Error hw_get_module 'flp': -2

E/LocationManagerService(  583): no geofence provider found

D/SystemUIService(  644): running: com.android.systemui.settings.SettingsUI@a5cf8580

I/ActivityManager(  583): Start proc com.android.settings for broadcast com.android.settings/.widget.SettingsAppWidgetProvider: pid=705 uid=1000 gids={41000, 1028, 1015, 3002, 3001, 3003}

I/CommonTimeManagementService(  583): No common time service detected on this platform.  Common time services will be unavailable.

I/InputReader(  583): Reconfiguring input devices.  changes=0x00000020

I/InputReader(  583): Reconfiguring input devices.  changes=0x00000010

I/ActivityManager(  583): Start proc com.android.phone for added application com.android.phone: pid=719 uid=1001 gids={41001, 3002, 3001, 3003, 1028, 1015}

I/ActivityManager(  583): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.android.launcher/com.android.launcher2.Launcher} from pid 0

I/ActivityManager(  583): Start proc com.android.launcher for activity com.android.launcher/com.android.launcher2.Launcher: pid=738 uid=10009 gids={50009}

I/StatusBarManagerService(  583): registerStatusBar bar=com.android.internal.statusbar.IStatusBar$Stub$Proxy@a5f16d10

I/Choreographer(  583): Skipped 118 frames!  The application may be doing too much work on its main thread.

D/PhoneStatusBar(  644): mSettingsPanelGravity = 8388661

W/InputMethodManagerService(  583): Focus gain on non-focused client android.view.inputmethod.InputMethodManager$1@a5ed0d10 (uid=1000 pid=583)

V/KeyguardServiceDelegate(  583): *** Keyguard connected (yay!)

I/LatinIME(  687): Hardware accelerated drawing: true

W/ResourceType(  583): Failure getting entry for 0x7f060000 (t=5 e=0) in package 0 (error -75)

D/dalvikvm(  583): GC_CONCURRENT freed 285K, 7% free 4876K/5240K, paused 57ms+100ms, total 352ms

I/ActivityManager(  583): Start proc com.android.printspooler for service com.android.printspooler/.PrintSpoolerService: pid=755 uid=10032 gids={50032}

D/dalvikvm(  644): GC_CONCURRENT freed 147K, 7% free 2983K/3200K, paused 10ms+3ms, total 93ms

D/dalvikvm(  644): GC_CONCURRENT freed 21K, 6% free 3374K/3560K, paused 3ms+2ms, total 29ms

D/dalvikvm(  644): WAIT_FOR_CONCURRENT_GC blocked 16ms

W/InputAttributes(  687): No editor info for this field. Bug?

I/MediaFocusControl(  583):   Remote Control   registerMediaButtonIntent() for PendingIntent{a5f21318: PendingIntentRecord{a5eca0a8 android broadcastIntent}}

I/ResourceUtils(  687): Found default value: resource=keypress_vibration_durations build=[HARDWARE=genericam33xx(flatteneddevicetr MODEL=BeagleBone Black BRAND=Android MANUFACTURER=Texas_Instruments_Inc] default=-1

I/ResourceUtils(  687): Found default value: resource=keypress_volumes build=[HARDWARE=genericam33xx(flatteneddevicetr MODEL=BeagleBone Black BRAND=Android MANUFACTURER=Texas_Instruments_Inc] default=-1.0f

V/BackupManagerService(  583): Connected to transport ComponentInfo{android/com.android.internal.backup.LocalTransportService}

V/BackupManagerService(  583): Registering transport android/com.android.internal.backup.LocalTransportService::android/com.android.internal.backup.LocalTransport = com.android.internal.backup.LocalTransport@a5f164b8

I/ActivityManager(  583): Start proc android.process.acore for content provider com.android.providers.userdictionary/.UserDictionaryProvider: pid=776 uid=10001 gids={50001, 3003, 1028, 1015}

V/PhoneStatusBar/NavigationBarView(  644): touchEnabled:false

I/LatinIME:LogUtils(  687): Dictionary info: dictionary = userunigram.en_US.dict ; version = ? ; date = ?

I/PrintSpoolerService(  755): No existing print spooler state.

E/BluetoothAdapter(  644): Bluetooth binder is null

E/BluetoothAdapter(  644): Bluetooth binder is null

D/dalvikvm(  687): GC_CONCURRENT freed 184K, 8% free 2927K/3180K, paused 4ms+61ms, total 332ms

E/BluetoothAdapter(  644): Bluetooth binder is null

I/ActivityManager(  583): Start proc com.android.smspush for service com.android.smspush/.WapPushManager: pid=794 uid=10022 gids={50022}

I/LatinIME:LogUtils(  687): Dictionary info: dictionary = main:en ; version = 42 ; date = 1381226429

D/dalvikvm(  644): GC_CONCURRENT freed 112K, 5% free 3670K/3844K, paused 3ms+3ms, total 172ms

D/dalvikvm(  776): GC_CONCURRENT freed 207K, 9% free 2944K/3220K, paused 4ms+2ms, total 100ms

D/dalvikvm(  738): GC_CONCURRENT freed 193K, 9% free 2971K/3232K, paused 14ms+52ms, total 240ms

E/BluetoothAdapter(  719): Bluetooth binder is null

E/BluetoothAdapter(  644): Bluetooth binder is null

I/LatinIME:LogUtils(  687): Dictionary info: dictionary = UserHistoryDictionary.en_US.dic ; version = ? ; date = 946685064

I/LatinIME:LogUtils(  687): Dictionary info: dictionary = personalization.en_US.dict ; version = ? ; date = 946685064

I/LatinIME:LogUtils(  687): Dictionary info: dictionary = PersonalizationPredictionDictio ; version = ? ; date = 946685064

E/BluetoothAdapter(  719): Bluetooth binder is null

D/CallNotifier(  719): CallNotifier: mSignalInfoToneGenerator created when toneplay

E/BluetoothAdapter(  719): Bluetooth binder is null

D/dalvikvm(  719): GC_CONCURRENT freed 140K, 7% free 2977K/3188K, paused 9ms+65ms, total 233ms

D/PhoneStatusBar(  644): disable: < expand icons alerts ticker system_info back home recent clock search >

E/BluetoothAdapter(  705): Bluetooth binder is null

I/FusedLocation(  583): engine stopped (com.android.location.fused)

I/FusedLocation(  583): engine started (com.android.location.fused)

I/FusedLocation(  583): engine started (com.android.location.fused)

D/TelephonyDebugService(  719): TelephonyDebugService()

W/CallNotifier(  719): Got onMwiChanged() on non-voice-capable device! Ignoring...

I/ActivityManager(  583): Start proc com.android.music for broadcast com.android.music/.MediaButtonIntentReceiver: pid=826 uid=10030 gids={50030, 3003, 1028, 1015}

D/dalvikvm(   95): GC_EXPLICIT freed 37K, 4% free 2721K/2828K, paused 2ms+6ms, total 58ms

D/dalvikvm(   95): GC_EXPLICIT freed <1K, 4% free 2721K/2828K, paused 3ms+9ms, total 57ms

D/dalvikvm(   95): GC_EXPLICIT freed <1K, 4% free 2721K/2828K, paused 2ms+2ms, total 57ms

D/dalvikvm(  644): GC_CONCURRENT freed 96K, 4% free 3994K/4160K, paused 63ms+6ms, total 298ms

D/dalvikvm(  738): GC_FOR_ALLOC freed 49K, 4% free 3155K/3272K, paused 35ms, total 41ms

I/dalvikvm-heap(  738): Grow heap (frag case) to 3.755MB for 640016-byte allocation

E/BluetoothAdapter(  644): Bluetooth binder is null

I/dalvikvm(  826): CheckJNI enabled: not enabling JNI app bug workarounds.

D/PhoneStatusBar(  644): heads up is disabled

W/SchedPolicy(  583): add_tid_to_cgroup failed to write '826' (Permission denied); policy=0

W/ActivityManager(  583): Failed setting process group of 826 to 0

V/KeyguardServiceDelegate(  583): **** SHOWN CALLED ****

W/System.err(  583): java.lang.SecurityException: No permission to set to given group

W/System.err(  583):    at android.os.Process.setProcessGroup(Native Method)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.applyOomAdjLocked(ActivityManagerService.java:15284)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15528)

W/System.err(  583):    at com.android.server.am.BroadcastQueue.processCurBroadcastLocked(BroadcastQueue.java:225)

W/System.err(  583):    at com.android.server.am.BroadcastQueue.sendPendingBroadcastsLocked(BroadcastQueue.java:260)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.sendPendingBroadcastsLocked(ActivityManagerService.java:13006)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplicationLocked(ActivityManagerService.java:5023)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplication(ActivityManagerService.java:5063)

W/System.err(  583):    at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:394)

D/dalvikvm(  738): GC_CONCURRENT freed 11K, 4% free 3769K/3900K, paused 13ms+33ms, total 268ms

D/dalvikvm(  738): WAIT_FOR_CONCURRENT_GC blocked 114ms

W/System.err(  583):    at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2071)

W/System.err(  583):    at android.os.Binder.execTransact(Binder.java:404)

W/System.err(  583):    at dalvik.system.NativeStart.run(Native Method)

I/MediaFocusControl(  583):   Remote Control   registerMediaButtonIntent() for PendingIntent{a5f4c9b8: PendingIntentRecord{a5f4c4b8 com.android.music broadcastIntent}}

D/dalvikvm(  644): GC_FOR_ALLOC freed 19K, 4% free 3996K/4160K, paused 227ms, total 232ms

I/ActivityManager(  583): Start proc android.process.media for content provider com.android.providers.media/.MediaProvider: pid=840 uid=10000 gids={50000, 1028, 1015, 1023, 1024, 2001, 3003, 3007}

I/dalvikvm-heap(  644): Grow heap (frag case) to 13.341MB for 9830416-byte allocation

D/dalvikvm(  644): GC_CONCURRENT freed <1K, 2% free 13596K/13764K, paused 85ms+20ms, total 288ms

D/dalvikvm(  644): WAIT_FOR_CONCURRENT_GC blocked 150ms

W/SchedPolicy(  583): add_tid_to_cgroup failed to write '840' (Permission denied); policy=0

W/System.err(  583): java.lang.SecurityException: No permission to set to given group

W/ActivityManager(  583): Failed setting process group of 840 to 0

W/System.err(  583):    at android.os.Process.setProcessGroup(Native Method)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.applyOomAdjLocked(ActivityManagerService.java:15284)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15528)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplicationLocked(ActivityManagerService.java:5052)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplication(ActivityManagerService.java:5063)

W/System.err(  583):    at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:394)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2071)

W/System.err(  583):    at android.os.Binder.execTransact(Binder.java:404)

W/System.err(  583):    at dalvik.system.NativeStart.run(Native Method)

D/dalvikvm(  583): GC_CONCURRENT freed 345K, 8% free 4973K/5392K, paused 4ms+26ms, total 467ms

E/BluetoothAdapter(  705): Bluetooth binder is null

W/System.err(  583): java.lang.SecurityException: No permission to set to given group

W/SchedPolicy(  583): add_tid_to_cgroup failed to write '755' (Permission denied); policy=0

W/ActivityManager(  583): Failed setting process group of 755 to 0

W/System.err(  583):    at android.os.Process.setProcessGroup(Native Method)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.applyOomAdjLocked(ActivityManagerService.java:15284)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15370)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15395)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15379)

W/System.err(  583):    at com.android.server.am.ActiveServices.removeConnectionLocked(ActiveServices.java:1708)

W/System.err(  583):    at com.android.server.am.ActiveServices.unbindServiceLocked(ActiveServices.java:860)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.unbindService(ActivityManagerService.java:12776)

W/System.err(  583):    at android.app.ContextImpl.unbindService(ContextImpl.java:1606)

W/System.err(  583):    at com.android.server.print.RemotePrintSpooler.unbindLocked(RemotePrintSpooler.java:400)

W/System.err(  583):    at com.android.server.print.RemotePrintSpooler.onAllPrintJobsHandled(RemotePrintSpooler.java:339)

W/System.err(  583):    at com.android.server.print.RemotePrintSpooler.access$700(RemotePrintSpooler.java:52)

W/System.err(  583):    at com.android.server.print.RemotePrintSpooler$PrintSpoolerClient.onAllPrintJobsHandled(RemotePrintSpooler.java:614)

W/System.err(  583):    at android.print.IPrintSpoolerClient$Stub.onTransact(IPrintSpoolerClient.java:79)

W/System.err(  583):    at android.os.Binder.execTransact(Binder.java:404)

W/System.err(  583):    at dalvik.system.NativeStart.run(Native Method)

D/dalvikvm(  738): GC_FOR_ALLOC freed 104K, 5% free 3956K/4132K, paused 194ms, total 202ms

I/dalvikvm-heap(  738): Grow heap (frag case) to 6.739MB for 2949136-byte allocation

D/dalvikvm(  738): GC_CONCURRENT freed 11K, 3% free 6825K/7016K, paused 6ms+9ms, total 95ms

D/dalvikvm(  738): WAIT_FOR_CONCURRENT_GC blocked 88ms

D/dalvikvm(  644): GC_FOR_ALLOC freed 9601K, 4% free 3998K/4160K, paused 242ms, total 242ms

D/dalvikvm(  738): GC_FOR_ALLOC freed <1K, 3% free 6825K/7016K, paused 67ms, total 67ms

I/dalvikvm-heap(  738): Grow heap (frag case) to 9.541MB for 2949136-byte allocation

I/dalvikvm-heap(  644): Grow heap (frag case) to 13.342MB for 9830416-byte allocation

D/dalvikvm(  644): GC_FOR_ALLOC freed <1K, 2% free 13598K/13764K, paused 86ms, total 86ms

D/dalvikvm(  738): GC_CONCURRENT freed 0K, 2% free 9705K/9900K, paused 3ms+19ms, total 105ms

D/dalvikvm(  738): WAIT_FOR_CONCURRENT_GC blocked 101ms

D/dalvikvm(  644): GC_CONCURRENT freed <1K, 2% free 13598K/13764K, paused 3ms+3ms, total 77ms

D/dalvikvm(  738): WAIT_FOR_CONCURRENT_GC blocked 415ms

I/ActivityManager(  583): Displayed com.android.launcher/com.android.launcher2.Launcher: +11s184ms

W/WindowManager(  583): Window freeze timeout expired.

W/WindowManager(  583): Force clearing orientation change: Window{a5ef5d28 u0 com.android.systemui.ImageWallpaper}

I/Choreographer(  738): Skipped 127 frames!  The application may be doing too much work on its main thread.

I/SurfaceFlinger(   94): Boot is finished (57600 ms)

I/Choreographer(  644): Skipped 524 frames!  The application may be doing too much work on its main thread.

E/BluetoothAdapter(  583): Bluetooth binder is null

E/BluetoothAdapter(  583): Bluetooth binder is null

V/WiredAccessoryManager(  583): init()

I/PowerManagerService(  583): Boot animation finished.

I/RecoverySystem(  583): No recovery log file

I/ActivityManager(  583): Start proc com.android.onetimeinitializer for broadcast com.android.onetimeinitializer/.OneTimeInitializerReceiver: pid=868 uid=10002 gids={50002}

D/dalvikvm(  644): GC_FOR_ALLOC freed 9669K, 71% free 4117K/13856K, paused 145ms, total 150ms

I/dalvikvm-heap(  644): Grow heap (frag case) to 13.459MB for 9830416-byte allocation

D/dalvikvm(  738): GC_FOR_ALLOC freed 5773K, 60% free 4033K/9944K, paused 574ms, total 580ms

I/dalvikvm-heap(  738): Grow heap (frag case) to 6.717MB for 2846736-byte allocation

D/dalvikvm(  644): GC_CONCURRENT freed 1K, 2% free 13716K/13856K, paused 3ms+11ms, total 86ms

D/dalvikvm(  738): GC_CONCURRENT freed <1K, 32% free 6813K/9944K, paused 3ms+11ms, total 65ms

D/dalvikvm(  738): WAIT_FOR_CONCURRENT_GC blocked 60ms

D/dalvikvm(  738): GC_FOR_ALLOC freed <1K, 32% free 6813K/9944K, paused 38ms, total 38ms

I/dalvikvm-heap(  738): Grow heap (frag case) to 9.431MB for 2846736-byte allocation

D/dalvikvm(  738): GC_CONCURRENT freed <1K, 4% free 9593K/9944K, paused 3ms+3ms, total 51ms

D/dalvikvm(  738): WAIT_FOR_CONCURRENT_GC blocked 46ms

I/Choreographer(  644): Skipped 96 frames!  The application may be doing too much work on its main thread.

W/SchedPolicy(  583): add_tid_to_cgroup failed to write '868' (Permission denied); policy=0

W/ActivityManager(  583): Failed setting process group of 868 to 0

W/System.err(  583): java.lang.SecurityException: No permission to set to given group

W/System.err(  583):    at android.os.Process.setProcessGroup(Native Method)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.applyOomAdjLocked(ActivityManagerService.java:15284)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15528)

W/System.err(  583):    at com.android.server.am.BroadcastQueue.processCurBroadcastLocked(BroadcastQueue.java:225)

W/System.err(  583):    at com.android.server.am.BroadcastQueue.sendPendingBroadcastsLocked(BroadcastQueue.java:260)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.sendPendingBroadcastsLocked(ActivityManagerService.java:13006)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplicationLocked(ActivityManagerService.java:5023)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplication(ActivityManagerService.java:5063)

W/System.err(  583):    at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:394)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2071)

W/System.err(  583):    at android.os.Binder.execTransact(Binder.java:404)

W/System.err(  583):    at dalvik.system.NativeStart.run(Native Method)

I/BootReceiver(  583): Copying audit failures to DropBox

I/BootReceiver(  583): Checking for fsck errors

W/SchedPolicy(  583): add_tid_to_cgroup failed to write '840' (Permission denied); policy=1

W/ActivityManager(  583): Failed setting process group of 840 to -1

W/System.err(  583): java.lang.SecurityException: No permission to set to given group

W/System.err(  583):    at android.os.Process.setProcessGroup(Native Method)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.applyOomAdjLocked(ActivityManagerService.java:15284)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15370)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15395)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15379)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.getContentProviderImpl(ActivityManagerService.java:7578)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.getContentProvider(ActivityManagerService.java:7804)

W/System.err(  583):    at android.app.ActivityThread.acquireProvider(ActivityThread.java:4399)

W/System.err(  583):    at android.app.ContextImpl$ApplicationContentResolver.acquireProvider(ContextImpl.java:2185)

W/System.err(  583):    at android.content.ContentResolver.acquireProvider(ContentResolver.java:1378)

W/System.err(  583):    at android.content.ContentResolver.delete(ContentResolver.java:1276)

W/System.err(  583):    at android.provider.Downloads.removeAllDownloadsByPackage(Downloads.java:805)

W/System.err(  583):    at com.android.server.BootReceiver.removeOldUpdatePackages(BootReceiver.java:93)

W/System.err(  583):    at com.android.server.BootReceiver.access$100(BootReceiver.java:42)

W/System.err(  583):    at com.android.server.BootReceiver$1.run(BootReceiver.java:82)

V/OneTimeInitializerRece(  868): OneTimeInitializerReceiver.onReceive

I/ActivityManager(  583): Delay finish: com.android.onetimeinitializer/.OneTimeInitializerReceiver

I/ActivityManager(  583): Resuming delayed broadcast

W/System.err(  583): java.lang.SecurityException: No permission to set to given group

W/SchedPolicy(  583): add_tid_to_cgroup failed to write '840' (Permission denied); policy=0

W/ActivityManager(  583): Failed setting process group of 840 to 0

W/System.err(  583):    at android.os.Process.setProcessGroup(Native Method)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.applyOomAdjLocked(ActivityManagerService.java:15284)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15528)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.removeContentProvider(ActivityManagerService.java:7840)

W/System.err(  583):    at android.app.ActivityThread.completeRemoveProvider(ActivityThread.java:4638)

W/System.err(  583):    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1351)

W/System.err(  583):    at android.os.Handler.dispatchMessage(Handler.java:102)

W/System.err(  583):    at android.os.Looper.loop(Looper.java:136)

W/System.err(  583):    at com.android.server.ServerThread.initAndLoop(SystemServer.java:1093)

W/System.err(  583):    at com.android.server.SystemServer.main(SystemServer.java:1179)

W/System.err(  583):    at java.lang.reflect.Method.invokeNative(Native Method)

W/System.err(  583):    at java.lang.reflect.Method.invoke(Method.java:515)

W/System.err(  583):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785)

W/System.err(  583):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601)

W/System.err(  583):    at dalvik.system.NativeStart.main(Native Method)

I/ActivityManager(  583): Start proc com.android.providers.calendar for broadcast com.android.providers.calendar/.CalendarReceiver: pid=898 uid=10007 gids={50007, 3003, 1028, 1015}

W/SchedPolicy(  583): add_tid_to_cgroup failed to write '898' (Permission denied); policy=0

W/ActivityManager(  583): Failed setting process group of 898 to 0

W/System.err(  583): java.lang.SecurityException: No permission to set to given group

W/System.err(  583):    at android.os.Process.setProcessGroup(Native Method)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.applyOomAdjLocked(ActivityManagerService.java:15284)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15528)

W/System.err(  583):    at com.android.server.am.BroadcastQueue.processCurBroadcastLocked(BroadcastQueue.java:225)

W/System.err(  583):    at com.android.server.am.BroadcastQueue.sendPendingBroadcastsLocked(BroadcastQueue.java:260)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.sendPendingBroadcastsLocked(ActivityManagerService.java:13006)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplicationLocked(ActivityManagerService.java:5023)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplication(ActivityManagerService.java:5063)

W/System.err(  583):    at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:394)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2071)

W/System.err(  583):    at android.os.Binder.execTransact(Binder.java:404)

W/System.err(  583):    at dalvik.system.NativeStart.run(Native Method)

I/CalendarProvider2(  898): Created com.android.providers.calendar.CalendarAlarmManager@a5cf5a08(com.android.providers.calendar.CalendarProvider2@a5ced668)

I/ActivityManager(  583): Start proc com.android.email for broadcast com.android.email/.service.EmailBroadcastReceiver: pid=925 uid=10027 gids={50027, 3003, 1028, 1015}

W/System.err(  583): java.lang.SecurityException: No permission to set to given group

W/System.err(  583):    at android.os.Process.setProcessGroup(Native Method)

W/SchedPolicy(  583): add_tid_to_cgroup failed to write '925' (Permission denied); policy=0

W/ActivityManager(  583): Failed setting process group of 925 to 0

W/System.err(  583):    at com.android.server.am.ActivityManagerService.applyOomAdjLocked(ActivityManagerService.java:15284)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15528)

W/System.err(  583):    at com.android.server.am.BroadcastQueue.processCurBroadcastLocked(BroadcastQueue.java:225)

W/System.err(  583):    at com.android.server.am.BroadcastQueue.sendPendingBroadcastsLocked(BroadcastQueue.java:260)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.sendPendingBroadcastsLocked(ActivityManagerService.java:13006)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplicationLocked(ActivityManagerService.java:5023)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplication(ActivityManagerService.java:5063)

W/System.err(  583):    at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:394)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2071)

W/System.err(  583):    at android.os.Binder.execTransact(Binder.java:404)

W/System.err(  583):    at dalvik.system.NativeStart.run(Native Method)

I/CalendarProvider2(  898): Sending notification intent: Intent { act=android.intent.action.PROVIDER_CHANGED dat=content://com.android.calendar }

W/ContentResolver(  898): Failed to get type for: content://com.android.calendar (Unknown URL content://com.android.calendar)

I/ActivityManager(  583): Start proc com.android.calendar for broadcast com.android.calendar/.alerts.AlertReceiver: pid=941 uid=10031 gids={50031, 3003}

W/System.err(  583): java.lang.SecurityException: No permission to set to given group

W/SchedPolicy(  583): add_tid_to_cgroup failed to write '941' (Permission denied); policy=0

W/ActivityManager(  583): Failed setting process group of 941 to 0

W/System.err(  583):    at android.os.Process.setProcessGroup(Native Method)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.applyOomAdjLocked(ActivityManagerService.java:15284)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15528)

W/System.err(  583):    at com.android.server.am.BroadcastQueue.processCurBroadcastLocked(BroadcastQueue.java:225)

W/System.err(  583):    at com.android.server.am.BroadcastQueue.sendPendingBroadcastsLocked(BroadcastQueue.java:260)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.sendPendingBroadcastsLocked(ActivityManagerService.java:13006)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplicationLocked(ActivityManagerService.java:5023)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplication(ActivityManagerService.java:5063)

W/System.err(  583):    at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:394)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2071)

W/System.err(  583):    at android.os.Binder.execTransact(Binder.java:404)

W/System.err(  583):    at dalvik.system.NativeStart.run(Native Method)

D/dalvikvm(  925): GC_CONCURRENT freed 232K, 10% free 2874K/3180K, paused 4ms+3ms, total 31ms

D/ExtensionsFactory(  941): No custom extensions.

D/AlertReceiver(  941): onReceive: a=android.intent.action.BOOT_COMPLETED Intent { act=android.intent.action.BOOT_COMPLETED flg=0x8000010 cmp=com.android.calendar/.alerts.AlertReceiver (has extras) }

I/ActivityManager(  583): Delay finish: com.android.calendar/.alerts.AlertReceiver

D/AlertService(  941): 0 Action = android.intent.action.BOOT_COMPLETED

D/AlertService(  941): Scheduling next alarm with AlarmScheduler. sEventReminderReceived: null

D/AlarmScheduler(  941): No events found starting within 1 week.

I/ContactLocale(  776): AddressBook Labels [en_US]: [, A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z, ?, ?, G, ?, ?, ?, ?, T, ?, ?, ?, ?, ?, ?, ?, ?, ?, S, ?, ?, F, ?, ?, O, , ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, , ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, , ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, , ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, , ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, , ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, #, ]

D/dalvikvm(  840): GC_CONCURRENT freed 215K, 10% free 2896K/3184K, paused 4ms+5ms, total 33ms

D/dalvikvm(  840): GC_CONCURRENT freed 241K, 10% free 3043K/3356K, paused 4ms+5ms, total 31ms

W/MediaScanner(  840): Error opening directory '/storage/sdcard1/', skipping: Permission denied.

V/MediaScanner(  840): pruneDeadThumbnailFiles... android.database.sqlite.SQLiteCursor@a5cfa2f0

V/MediaScanner(  840): /pruneDeadThumbnailFiles... android.database.sqlite.SQLiteCursor@a5cfa2f0

I/ActivityManager(  583): Delaying start of: ServiceRecord{a5f71338 u0 com.android.exchange/.service.EmailSyncAdapterService}

I/ActivityManager(  583): Start proc com.android.exchange for service com.android.exchange/.service.EmailSyncAdapterService: pid=964 uid=10047 gids={50047, 3003, 1028, 1015}

W/SchedPolicy(  583): add_tid_to_cgroup failed to write '964' (Permission denied); policy=0

W/System.err(  583): java.lang.SecurityException: No permission to set to given group

W/System.err(  583):    at android.os.Process.setProcessGroup(Native Method)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.applyOomAdjLocked(ActivityManagerService.java:15284)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15528)

W/ActivityManager(  583): Failed setting process group of 964 to 0

W/System.err(  583):    at com.android.server.am.ActiveServices.realStartServiceLocked(ActiveServices.java:1395)

W/System.err(  583):    at com.android.server.am.ActiveServices.attachApplicationLocked(ActiveServices.java:1874)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplicationLocked(ActivityManagerService.java:5014)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplication(ActivityManagerService.java:5063)

W/System.err(  583):    at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:394)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2071)

W/System.err(  583):    at android.os.Binder.execTransact(Binder.java:404)

W/System.err(  583):    at dalvik.system.NativeStart.run(Native Method)

W/ActivityManager(  583): Unable to start service Intent { cmp=com.android.email/.service.AttachmentDownloadService } U=0: not found

D/dalvikvm(  583): GC_CONCURRENT freed 375K, 9% free 5053K/5508K, paused 16ms+6ms, total 210ms

I/Email   (  925): Observing account changes for notifications

W/SchedPolicy(  583): add_tid_to_cgroup failed to write '776' (Permission denied); policy=0

W/System.err(  583): java.lang.SecurityException: No permission to set to given group

W/ActivityManager(  583): Failed setting process group of 776 to 0

W/System.err(  583):    at android.os.Process.setProcessGroup(Native Method)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.applyOomAdjLocked(ActivityManagerService.java:15284)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15528)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.removeContentProvider(ActivityManagerService.java:7840)

W/System.err(  583):    at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:773)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2071)

W/System.err(  583):    at android.os.Binder.execTransact(Binder.java:404)

W/System.err(  583):    at dalvik.system.NativeStart.run(Native Method)

I/ActivityManager(  583): Resuming delayed broadcast

I/ActivityManager(  583): Start proc com.android.deskclock for broadcast com.android.deskclock/.AlarmInitReceiver: pid=980 uid=10035 gids={50035, 1028}

W/SchedPolicy(  583): add_tid_to_cgroup failed to write '980' (Permission denied); policy=0

W/ActivityManager(  583): Failed setting process group of 980 to 0

W/System.err(  583): java.lang.SecurityException: No permission to set to given group

W/System.err(  583):    at android.os.Process.setProcessGroup(Native Method)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.applyOomAdjLocked(ActivityManagerService.java:15284)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15528)

W/System.err(  583):    at com.android.server.am.BroadcastQueue.processCurBroadcastLocked(BroadcastQueue.java:225)

W/System.err(  583):    at com.android.server.am.BroadcastQueue.sendPendingBroadcastsLocked(BroadcastQueue.java:260)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.sendPendingBroadcastsLocked(ActivityManagerService.java:13006)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplicationLocked(ActivityManagerService.java:5023)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplication(ActivityManagerService.java:5063)

W/System.err(  583):    at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:394)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2071)

W/System.err(  583):    at android.os.Binder.execTransact(Binder.java:404)

W/System.err(  583):    at dalvik.system.NativeStart.run(Native Method)

I/ActivityManager(  583): Waited long enough for: ServiceRecord{a5f4b3c8 u0 com.android.music/.MediaPlaybackService}

V/AlarmClock(  980): AlarmInitReceiver android.intent.action.BOOT_COMPLETED

D/NetUtils(  583): dhcp_do_request failed : eth0 (new)

E/Ethernet(  583): DHCP request error:Timed out waiting for DHCP to finish

D/NetUtils(  583): dhcp_do_request failed : eth0 (new)

E/Ethernet(  583): DHCP request error:Timed out waiting for DHCP to finish

V/AlarmClock(  980): AlarmInitReceiver - Reset timers and clear stopwatch data

I/AlarmClock(  980): Displaying next alarm time: ''

I/LauncherIconVisibilityManager(  687): Boot has been completed

I/LauncherIconVisibilityManager(  687): Activity has already been disabled: ComponentInfo{com.android.inputmethod.latin/com.android.inputmethod.latin.setup.SetupActivity}

V/AlarmClock(  980): AlarmInitReceiver finished

D/AlertReceiver(  941): onReceive: a=android.intent.action.PROVIDER_CHANGED Intent { act=android.intent.action.PROVIDER_CHANGED dat=content://com.android.calendar flg=0x10 cmp=com.android.calendar/.alerts.AlertReceiver }

D/AlertService(  941): 0 Action = android.intent.action.PROVIDER_CHANGED

I/ActivityManager(  583): Delay finish: com.android.providers.calendar/.CalendarProviderBroadcastReceiver

I/ActivityManager(  583): Resuming delayed broadcast

I/GlobalDismissManager(  941): no sender configured

D/AlertService(  941): Beginning updateAlertNotification

D/AlertService(  941): No fired or scheduled alerts

D/AlertService(  941): Scheduling next alarm with AlarmScheduler. sEventReminderReceived: null

D/AlarmScheduler(  941): No events found starting within 1 week.

I/ActivityManager(  583): Waited long enough for: ServiceRecord{a5f6d000 u0 com.android.calendar/.alerts.InitAlarmsService}

D/InitAlarmsService(  941): Clearing and rescheduling alarms.

D/ConnectivityService(  583): Sampling interval elapsed, updating statistics ..

D/ConnectivityService(  583): Done.

D/ConnectivityService(  583): Setting timer for 720seconds

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/lights  (  583): write_int failed to open

I/lights  (  583):       /sys/class/backlight/pwm-backlight/brightness and /sys/class/backlight/tps65217-bl/brightness

I/MediaFocusControl(  583):  AudioFocus  abandonAudioFocus() from android.media...@a5cea8b8com.android.music.MediaPlaybackService$3@a5ce9738

I/ActivityManager(  583): Start proc com.android.musicfx for broadcast com.android.musicfx/.ControlPanelReceiver: pid=1007 uid=10003 gids={50003, 3003, 3002}

W/SchedPolicy(  583): add_tid_to_cgroup failed to write '1007' (Permission denied); policy=0

W/System.err(  583): java.lang.SecurityException: No permission to set to given group

W/ActivityManager(  583): Failed setting process group of 1007 to 0

W/System.err(  583):    at android.os.Process.setProcessGroup(Native Method)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.applyOomAdjLocked(ActivityManagerService.java:15284)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15528)

W/System.err(  583):    at com.android.server.am.BroadcastQueue.processCurBroadcastLocked(BroadcastQueue.java:225)

W/System.err(  583):    at com.android.server.am.BroadcastQueue.sendPendingBroadcastsLocked(BroadcastQueue.java:260)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.sendPendingBroadcastsLocked(ActivityManagerService.java:13006)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplicationLocked(ActivityManagerService.java:5023)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.attachApplication(ActivityManagerService.java:5063)

W/System.err(  583):    at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:394)

W/System.err(  583):    at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2071)

W/System.err(  583):    at android.os.Binder.execTransact(Binder.java:404)

W/System.err(  583):    at dalvik.system.NativeStart.run(Native Method)

V/MusicFXControlPanelReceiver( 1007): onReceive

V/MusicFXControlPanelReceiver( 1007): Action: android.media.action.CLOSE_AUDIO_EFFECT_CONTROL_SESSION

V/MusicFXControlPanelReceiver( 1007): Package name: com.android.music

V/MusicFXControlPanelReceiver( 1007): Audio session: 4

V/MusicFXControlPanelEffect( 1007): closeSession(android.app.ReceiverRestrictedContext@a5ce5dd8, com.android.music, 4)

W/SocketClient(   92): write error (Broken pipe)

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

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

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

[ido...@gmail.com]

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

[ido...@gmail.com]

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

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,

[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

[ti...@emailbx.com]

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

[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!).

[nvent...@gmail.com]

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

[mgob...@orcasolutions.be]

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

[grayv...@gmail.com]

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

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

[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

[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

[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?

 

--

Michael Gobbers  

+32477188592

Desguinlei 6 - 2018 Antwerpen

[nvent...@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

[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,

[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: G        W    3.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

[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

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

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

[Michael Gobbers]

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

--

Michael Gobbers  

[cdcar...@gmail.com]

Hello Andrew,

just a question, I'm continuing to work with your bbbandroid using a 4gb microSD card. This will not the same if I use eMMC onboard? this is also 4 gb.  Next.. what packets i can easly remove without damages? and how to do it?

Ciao,

gianmaria

[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

[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">

        <item>"wifi,1,1,1,-1,true"</item>

        …

</string-array>

# And

<string-array translatable="false" name="radioAttributes">

        <item>"1,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 :) 

[jimmy...@gmail.com]

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

[cam...@gmail.com]

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

[Keith Conger]

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

Keith

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

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

[cam...@gmail.com]

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!

[simh...@gmail.com]

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.

[gass...@gmail.com]

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写道：

[dariush.ab...@gmail.com]

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-00002-gf7d94e6 ".

It complains about not supported machin ID.

Any suggestion? 

[bayte...@gmail.com]

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

[andr...@gmail.com]

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