Linaro-android

linaro-android@lists.linaro.org

1073 discussions

by Botao Sun

Hi Vishal, A question about USB mass storage feature on Linaro Android images. I would say there are 2 different ways: 1. Using Android device as a host: In this way, by plugging in a USB mass storage device, a USB stick for example, there should be a pop-up window shows up on screen to say a USB mass storage device has been plugged in, similar as you do it on your PC. The current status is after plugged in the USB stick, some manual procedures need to be done to access the device, as indicated in test case USB Host ( https://wiki.linaro.org/Platform/QA/TestCases/Android#USB_Host), and no any UI notification shows. My question here is that is this an expected behaviour? 2. Using Android device as a client: In this way, by plugging it to a host PC, there should be a notification shows on screen to let user to choose among different options, USB mass storage is one of them. I remember we now only has the ADB debug notification (If USB debugging is enabled in developer options), USB mass storage option never shows. We already have a bug there: https://bugs.launchpad.net/linaro-android/+bug/897549 My question here is do we support this feature? Thanks. Best Regards Botao Sun

11 years, 9 months

Re: linaro-android Digest, Vol 30, Issue 3

by gmail

Now the "repo sync" is ok. I think the reason is that my Internet connection is not stable. thanks On 05/09/2014 08:00 AM, linaro-android-request(a)lists.linaro.org wrote: > Send linaro-android mailing list submissions to > linaro-android(a)lists.linaro.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.linaro.org/mailman/listinfo/linaro-android > or, via email, send a message with subject or body 'help' to > linaro-android-request(a)lists.linaro.org > > You can reach the person managing the list at > linaro-android-owner(a)lists.linaro.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of linaro-android digest..." > > > Today's Topics: > > 1. Linaro Android on cubieboard? (Vyacheslav Evgrafov) > 2. repo sync stops at the 99% (410/414) (gmail) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 8 May 2014 22:58:54 -0700 > From: Vyacheslav Evgrafov <slava.evgrafov(a)gmail.com> > To: linaro-android(a)lists.linaro.org > Subject: Linaro Android on cubieboard? > Message-ID: > <CAAncmEcnWjLqJdvrQZk8CTDKY04Hkk0T2w1fMRsunbbPR7fxvw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Congrads on partership with Allwinner. > > Are you guys planning Android release for Cubieboard anytime soon? >

11 years, 9 months

Detect UIFreeze and Blank screen

by $rik＠nth

Hi Linaro/Android/Dev's , I am running few Graphics benchmark tests on a Pandaboard. Recently after few changes in Overlay layer i am seeing UI is getting freeze randomly and sometime it is showing black screen even though shell is able to access. If i launch any activity through am, UI is not getting updated and it needs a hard reboot. It is very hard to debug the root cause. How to stop any test/benchmark if the UI freeze or a blank screen. Is there any way to do it from kernel or userspace. Any available tool that detects similar issue. -- Thanks & Regards, M.Srikanth Kumar.

11 years, 9 months

repo sync stops at the 99% (410/414)

by gmail

i have tried some times， but all stop at 99% Fetching project platform/external/linaro-android-tools Fetching project platform/hardware/samsung/origen/gralloc_ump Fetching project platform/frameworks/compile/libbcc Fetching projects: 98% (406/414) Fetching project platform/external/chromium_org/third_party/skia/gyp Fetching project platform/hardware/invensense Fetching project platform/external/ipsec-tools Fetching project device/samsung/proprietary-open Fetching projects: 99% (410/414) Fetching project platform/packages/wallpapers/Basic

11 years, 9 months

Linaro Android on cubieboard?

by Vyacheslav Evgrafov

Congrads on partership with Allwinner. Are you guys planning Android release for Cubieboard anytime soon?

11 years, 9 months

how to update the source after the environment MANIFEST_BRANCH have been changed ?

by gmail

I have downloaded the source a month ago , at that time the MANIFEST_BRANCH was "MANIFEST_BRANCH=linaro_android_4.4". Now, i found that the environment is "MANIFEST_BRANCH=linaro_android_4.4.2" how can i update my source code ? i follow this page https://android-build.linaro.org/builds/~linaro-android-member-ti/panda-lin… thang you !

11 years, 9 months

Problems building Linaro Android on Ubuntu 10.04 for Versatile Express

by Dious, Kevin

To whom it may concern, My name is Kevin Dious and I am writing because I am trying to use the linaro_android_build_cmds.sh script to build Linaro Android for the Versatile Express. Specifically, I am trying to build the following: https://android-build.linaro.org/builds/~linaro-android/vexpress-linaro-14.… Script link: http://snapshots.linaro.org/android/~linaro-android/vexpress-linaro-14.04-r… When I run the script, I get the following error initially (highlighted in yellow): Package acpica-tools is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package acpica-tools has no installation candidate kdious@eco-build1:/local/mnt/workspace/vexpress-linaro-build-309$ I noticed that the acpica-tools package is only available for Ubuntu 14.04 (Trusty Tahr). However, the script mentioned that it can be used for Ubunuu versions as old as 10.04 (see yellow heighted portion below). The acpica-tools package is part of the list of packages that the script tries to download (see below highlighted line below): UBUNTU=`cat /etc/issue.net | cut -d' ' -f2` HOST_ARCH=`uname -m` if [ ${HOST_ARCH} == "x86_64" ] ; then PKGS='gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z1-dev libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc uboot-mkimage openjdk-6-jdk openjdk-6-jre vim-common python-parted python-yaml wget uuid-dev acpica-tools' else echo "ERROR: Only 64bit Host(Build) machines are supported at the moment." exit 1 fi if [[ ${UBUNTU} =~ "13." || ${UBUNTU} =~ "12.10" ]]; then #Install basic dev package missing in chrooted environments sudo apt-get install software-properties-common sudo dpkg --add-architecture i386 PKGS+=' libstdc++6:i386 git-core' elif [[ ${UBUNTU} =~ "12.04" || ${UBUNTU} =~ "10.04" ]] ; then #Install basic dev package missing in chrooted environments sudo apt-get install python-software-properties if [[ ${UBUNTU} =~ "12.04" ]]; then PKGS+=' libstdc++6:i386 git-core' else PKGS+=' ia32-libs libssl-dev libcurl4-gnutls-dev libexpat1-dev gettext' fi else echo "ERROR: Only Ubuntu 10.04, 12.* and 13.04 versions are supported." exit 1 fi If I remove the reference to the acpica-tools package (the blue highlighted section above), the script does progress further but the following error is hit (See green highlighted error message below): Your Name [Kevin Dious]: Your Email [kdious(a)eco-build1.qualcomm.com]: kdious(a)quicinc.com Your identity is: Kevin Dious <kdious(a)quicinc.com> is this correct [y/N]? y repo has been initialized in /local/mnt/workspace/vexpress-linaro-build-309/git-1.7.9.5/android cp: missing destination file operand after `.repo/manifest.xml' Try `cp --help' for more information. kdious@eco-build1:/local/mnt/workspace/vexpress-linaro-build-309$ >From looking at the script, it seems as if the following line is failing (See green highlighted line below): # download the android code ./repo init -u ${MANIFEST_REPO} -b ${MANIFEST_BRANCH} -m ${MANIFEST_FILENAME} --repo-url=git://android.git.linaro.org/tools/repo -g common,vexpress if [ ${EXACT} -eq 1 ] ; then rm .repo/manifest.xml cp $MANIFEST .repo/manifest.xml fi So I have a few questions: a) Is the acpica-tools package truly necessary in order to build Linaro Android? If so, how are you able to build it on versions of Ubuntu older than 14.04? b) IS there some workaround that we can use to get around the cp error referenced above? Any help that you can provide would be greatly appreciated. Thank you. Regards, Kevin Dious Qualcomm Innovation Center, Inc. 5755 Morehouse Drive San Diego, CA 92121-1714 (858) 651-2014 (Phone) (858) 845-7478 (Fax) kdious(a)quicinc.com

11 years, 9 months

a question about juice project: how did you deal with the iptables component in 32 android/64 kernel mode.

by Panshilin (Peter)

Hi all concerned: there will have some problems about the external software components like iptables when they are running in kernel 64 . because these components interactive by netlink and share structures between the usrer space and kernel space. How the juice team work to meet these problems? whether the juice team have noticed and verify these android external components. Best Regards Peter

11 years, 10 months

Test Result Summary of Linaro Android 14.04 Release.

by Soumya Basak

Linaro Android 14.04 Release (Calender week 17): Here is the test result summary for 14.04 Release Linaro Android image on following boards: 1) TI Panda 4460; 2) TI Panda 4430; 3) Samsung Arndale; 4) Galaxy Nexus; 5) ARM Versatile Express A9; 6) ARM Versatile Express TC2; 7) ARM Versatile Express TC2 LSK; 1. TI Panda 4460 + Linux Linaro Android (Column: R) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… 2. TI Panda 4430 + Linux Linaro Android (Column: R) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… 3. Samsung Arndale + Linux Linaro Android (Column: P) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AuNOCeo15fRHdDFaR… 4. Galaxy Nexus + Linux Linaro Android (Column: N) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AuNOCeo15fRHdFhhe… 5. ARM Versatile Express A9 + Linux Linaro Android (Column: R) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… 6. ARM Versatile Express TC2 + Linux Linaro Android (Column: W) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… 7. ARM Versatile Express TC2 LSK + Linux Linaro Android (Column: X) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… Consolidated test result spreadsheet for Linaro Android 14.04 release, please visit the link below: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdDZxQ… -- Thank You. Best Regards -Soumya Basak.

11 years, 10 months

Linaro Android 14.03 Custom Built Kernel Crashes and Erases SD Card Data

by Mohammad Merajul Islam Molla

Hello, I am seeing this strange issue on my Samsung Arndale board with Linaro Android 14.03 Build. I downloaded the code and did a replica build using pinned manifest here - http://releases.linaro.org/14.03/android/arndale/pinned-manifest.xml This booted successfully on Samsung Arndale Board with Exynos 5250. After that I did a custom build of the kernel source included in the download. I used the config file from - http://releases.linaro.org/14.03/android/arndale/kernel_config . The only option I changed is - CONFIG_GPIO_SYSFS=y set so that /sys/class/gpio shows up. With this kernel it also booted successfully and /sys/class/gpio was there too. The problem I am facing is after about 10 minutes, the kernel panics with below trace - =================================================================================== root@arndale:/ # 6PM: suspend entry 1970-01-01 00:01:09.575420657 UTC [ 69.580000] PM: suspend entry 1970-01-01 00:01:09.575420657 UTC 6PM: Syncing filesystems ... [ 69.590000] PM: Syncing filesystems ... done. done. 6mmc0: card 0001 removed [ 80.590000] mmc0: card 0001 removed 6mmc1: card b368 removed [ 80.600000] mmc1: card b368 removed 2EXT4-fs error (device mmcblk1p6): ext4_find_dest_de:1657: inode #67: block 4443: comm PackageManager: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=0, name_len=0 [ 85.250000] EXT4-fs error (device mmcblk1p6): ext4_find_dest_de:1657: inode #67: block 4443: comm PackageManager: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=0, name_len=0 3Aborting journal on device mmcblk1p6-8. 3Buffer I/O error on device mmcblk1p6, lo mmcblk1p6-8. gical block 139265 4lost page write due to I/O error on mmcblk1p6 3JBD2: Erro block 139265 r -5 detected when updating journal superblock for mmcblk1p6-8. 0Kernel panic - not syncing: EXT4-fs (device mm on mmcblk1p6 cblk1p6): panic forced after error [<c0015450>] (unwind_backtrace+0x0/0x100) from [<c03f6bfc>] (panic+0xb8/0x23 mmcblk1p6-8. 8) [<c03f6bfc>] (panic+0xb8/0x238) from [<c015449c>] (ext4_handle_error.part.45+0x60/0xa4) [<c015449c> 85.300000] ] (ext4_handle_error.part.45+0x60/0xa4) from [<c01546e8>] (ext4_error_inode+0xc8/0x11c) [<c01546e8>] (ext4_error_inode+0xc8/0x11c) from [<c013fdb4>] (__ext4_check_dir_enc+0xb8/0x238) try+0x180/0x1a4) [<c013fdb4>] (__ext4_check_dir_entry+0x180/0x1a4) from [<c014f8a8>] (ext4_find_dest_de+0xc45+0x60/0xa4) 8/0x170) [<c014f8a8>] (ext4_find_dest_de+0xc8/0x170) from [<c014fb9c>] (add_dirent_to_buf+0x198/0x1bc) [<c014e+0xc8/0x11c) fb9c>] (add_dirent_to_buf+0x198/0x1bc) from [<c014fcf8>] (ext4_add_entry+0x138/0xb1c) [<c014fcf8>] (ext4_add_entry+0x138/0xb1c) from [<c01506f0>] (ext4_add_nondir+0x14/0x64) [<c01506f0>+0x180/0x1a4) ] (ext4_add_nondir+0x14/0x64) from [<c0150994>] (ext4_create+0xf4/0x164) [<c0150994>] (ext4_create+0xf4/0x164) from [<c00cad98>] (vfs_create+0x80/0xc0) [<c00cad98>] (vfs_cree+0xc8/0x170) ate+0x80/0xc0) from [<c00cd30c>] (do_last.isra.54+0x770/0xb94) [<c00cd30c>] (do_last.isra.54+0x770/0xb94) from [<c00cd7e4>] (path_openat.isra.55+0xb4/0x488) [+0x198/0x1bc) <c00cd7e4>] (path_openat.isra.55+0xb4/0x488) from [<c00ce798>] (do_filp_open+0x30/0x84) [<c00ce798>] (do_filp_open+0x30/0x84) from [<c00c0354>] (do_sys_open+0xe4/0x17c) [<c00c0354>]+0x138/0xb1c) (do_sys_open+0xe4/0x17c) from [<c000e100>] (ret_fast_syscall+0x0/0x30) [ 85.360000] [<c014fcf8>] (ext4_add_entry+0x138/0xb1c) from [<c01506f0>] (ext4_add_nonir+0x14/0x64) 2CPU1: stopping [<c0015450>] (unwind_backtrace+0x0/0x100) from [<c0013ae4>] (handle_IPI+0x194/0x1c8) [<c0013ae4>] (handle_IPI+0x194/0x1c8) from [<c00085d0>] (gic_handle_irq+0x60/0x6c) [<c00085d0>] (gic_handle_irq+0x60/0x6c) from [<c000dd00>] (__irq_svc+0x40/0x70) Exception stack(0xe80d7e48 to 0xe80d7e90) 7e40: 00000000 00000004 e80d7e28 00000000 00000004 00000067 7e60: 00007738 00000000 60070013 000076d0 00000002 c05ca448 00000000 e80d7e90 7e80: c03fd414 c0022a80 60070013 ffffffff [<c000dd00>] (__irq_svc+0x40/0x70) from [<c0022a80>] (console_unlock+0x478/0x4f4) [<c0022a80>] (console_unlock+0x478/0x4f4) from [<c0038a50>] (process_one_work+0x108/0x380) [<c0038a50>] (process_one_work+0x108/0x380) from [<c0039864>] (worker_thread+0x16c/0x468) [<c0039864>] (worker_thread+0x16c/0x468) from [<c003e11c>] (kthread+0xb8/0xc4) [<c003e11c>] (kthread+0xb8/0xc4) from [<c000e198>] (ret_from_fork+0x14/0x3c) 4------------[ cut here ]------------ 4WARNING: at kernel/workqueue.c:752 wq_worker_waking_up+0x6c/0x84() dModules linked in: [<c0015450>] (unwind_backtrace+0x0/0x100) from [<c00209bc>] (warn_slowpath_common+0x54/0x70) [<c00209bc>] (warn_slowpath_common+0x54/0x70) from [<c0020a74>] (warn_slowpath_null+0x1c/0x24) [<c0020a74>] (warn_slowpath_null+0x1c/0x24) from [<c0039bcc>] (wq_worker_waking_up+0x6c/0x84) [<c0039bcc>] (wq_worker_waking_up+0x6c/0x84) from [<c0048594>] (ttwu_do_activate.constprop.76+0x4c/0x64) [<c0048594>] (ttwu_do_activate.constprop.76+0x4c/0x64) from [<c004aaa8>] (try_to_wake_up+0x1d8/0x2d0) [<c004aaa8>] (try_to_wake_up+0x1d8/0x2d0) from [<c003edf4>] (autoremove_wake_function+0xc/0x34) [<c003edf4>] (autoremove_wake_function+0xc/0x34) from [<c0046254>] (__wake_up_common+0x50/0x84) [<c0046254>] (__wake_up_common+0x50/0x84) from [<c0046470>] (__wake_up+0x3c/0x50) [<c0046470>] (__wake_up+0x3c/0x50) from [<c02d9120>] (i2c_s3c_irq_nextbyte+0x16c/0x440) [<c02d9120>] (i2c_s3c_irq_nextbyte+0x16c/0x440) from [<c02d944c>] (s3c24xx_i2c_irq+0x58/0x78) [<c02d944c>] (s3c24xx_i2c_irq+0x58/0x78) from [<c006ef9c>] (handle_irq_event_percpu+0x7c/0x1b4) [<c006ef9c>] (handle_irq_event_percpu+0x7c/0x1b4) from [<c006f110>] (handle_irq_event+0x3c/0x5c) [<c006f110>] (handle_irq_event+0x3c/0x5c) from [<c0071fdc>] (handle_fasteoi_irq+0x88/0x118) [<c0071fdc>] (handle_fasteoi_irq+0x88/0x118) from [<c006e838>] (generic_handle_irq+0x20/0x30) [<c006e838>] (generic_handle_irq+0x20/0x30) from [<c000f054>] (handle_IRQ+0x48/0xb4) [<c000f054>] (handle_IRQ+0x48/0xb4) from [<c00085a4>] (gic_handle_irq+0x34/0x6c) [<c00085a4>] (gic_handle_irq+0x34/0x6c) from [<c000dd00>] (__irq_svc+0x40/0x70) Exception stack(0xe84efb10 to 0xe84efb58) fb00: 00000000 00000000 003f6e90 00000000 fb20: e84efb5c 7a68ab86 00005dbf 000000c8 00000001 c05c2098 c05c209c 00000020 fb40: 00000000 e84efb58 c0014300 c01bfe30 60010013 ffffffff [<c000dd00>] (__irq_svc+0x40/0x70) from [<c01bfe30>] (__timer_delay+0x38/0x50) [<c01bfe30>] (__timer_delay+0x38/0x50) from [<c03f6d3c>] (panic+0x1f8/0x238) [<c03f6d3c>] (panic+0x1f8/0x238) from [<c015449c>] (ext4_handle_error.part.45+0x60/0xa4) [<c015449c>] (ext4_handle_error.part.45+0x60/0xa4) from [<c01546e8>] (ext4_error_inode+0xc8/0x11c) [<c01546e8>] (ext4_error_inode+0xc8/0x11c) from [<c013fdb4>] (__ext4_check_dir_entry+0x180/0x1a4) [<c013fdb4>] (__ext4_check_dir_entry+0x180/0x1a4) from [<c014f8a8>] (ext4_find_dest_de+0xc8/0x170) [<c014f8a8>] (ext4_find_dest_de+0xc8/0x170) from [<c014fb9c>] (add_dirent_to_buf+0x198/0x1bc) [<c014fb9c>] (add_dirent_to_buf+0x198/0x1bc) from [<c014fcf8>] (ext4_add_entry+0x138/0xb1c) [<c014fcf8>] (ext4_add_entry+0x138/0xb1c) from [<c01506f0>] (ext4_add_nondir+0x14/0x64) [<c01506f0>] (ext4_add_nondir+0x14/0x64) from [<c0150994>] (ext4_create+0xf4/0x164) [<c0150994>] (ext4_create+0xf4/0x164) from [<c00cad98>] (vfs_create+0x80/0xc0) [<c00cad98>] (vfs_create+0x80/0xc0) from [<c00cd30c>] (do_last.isra.54+0x770/0xb94) [<c00cd30c>] (do_last.isra.54+0x770/0xb94) from [<c00cd7e4>] (path_openat.isra.55+0xb4/0x488) [<c00cd7e4>] (path_openat.isra.55+0xb4/0x488) from [<c00ce798>] (do_filp_open+0x30/0x84) [<c00ce798>] (do_filp_open+0x30/0x84) from [<c00c0354>] (do_sys_open+0xe4/0x17c) [<c00c0354>] (do_sys_open+0xe4/0x17c) from [<c000e100>] (ret_fast_syscall+0x0/0x30) 4---[ end trace b18da9d87686dd90 ]--- ==================================================================================== Is this a new bug? -- Thanks, -Meraj

11 years, 10 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-android