Linaro-android April 2014

linaro-android@lists.linaro.org

13 participants
17 discussions

Optimizing OVERLAY handling on android-build

by Paul Sokolovsky

Hello, There were increasing Android build times during last month again (going over 3.5hrs). Yesterday, I re-created the seed, but that didn't improve times match. I did more stats on builds and it turns out that we spend almost 1.5hrs in copying ever-growing overlay collection to the slaves via sluggish CopyToSlave Jenkins plugin. That's issues known for at least half-year, and was in queue for being reworked. I didn't work on android-build closely for few months, but now that I'm back on maintenance, I'd like to start with fixing this long-overdue issue. The idea was to pull all the needed overlay, straight to a slave. The complication here was handling of license protected files. ci.linaro.org had the same issue, and used a script to handle automatic downloads for some time. However, as of now, it was switched to other process and the script git bitrotted with recent linaro-license-protection codebase changes. I took a look at revamping it, but then though that it may be a good idea to use simpler and more explicit process, following closely click-thru usage. So, if you want to use a license-protected binaries in a build, you'd need to specify: ACCEPT_LICENSE=<license_id> Where <license_id> is id under which license is registered in linaro-license-protection. One good way to figure it out is to read the license page at all (well, as HTML source, the id is included in some links). Wording of variable name (as well as of commands in underlying implementation) is also explicit to point that its usage construes license acceptance. I prototypes these changes using https://android-build.linaro.org/builds/~pfalcon/panda-jb-gcc47-tilt-tracki… which is down to 2h10m build time. I'm ready to migrate all builds tomorrow, while we're early in cycle start. Please let me know if there're any issues with approach or proposed migration timeframe, otherwise let's make android-build rock again. Thanks, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

10 years, 7 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

10 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

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

10 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

10 years, 10 months

No display via HDMI using Linaro Android 14.03 on Samsung Arndale Board

by Mohammad Merajul Islam Molla

Hello, I downloaded and built Linaro Android 14.03 from source (replica build using pinned manifest) on Ubuntu 13.04 (64-bit) machine. After flashing it booted successfully on my Samsung Arndale Board with Exynos 5250 (Cortex A15). But there is no display on my HDMI monitor. It just remains black. It looks like its not getting any signal from board at all. What am I missing here? Thanks in advance. -- -Meraj

10 years, 10 months

Re: linaro-android Digest, Vol 29, Issue 9

by gmail

https://validation.linaro.org/static/docs/nexus-deploy.html i have read this url .i want to connect the i9250(galaxy nexus) to the lava , so i want to know if the 5V/1A adapter may be used as the power supply ,for i do not have a 4V/2A one . On 2014/4/22 20:00, 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. No display via HDMI using Linaro Android 14.03 on Samsung > Arndale Board (Mohammad Merajul Islam Molla) > 2. Building a smaller android for Arndale Board > (Mohammad Merajul Islam Molla) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 21 Apr 2014 21:33:28 +0600 > From: Mohammad Merajul Islam Molla <meraj.enigma(a)gmail.com> > To: linaro-android(a)lists.linaro.org > Subject: No display via HDMI using Linaro Android 14.03 on Samsung > Arndale Board > Message-ID: > <CAHu9=sPAR30zG-SyrRGP1oHBv2iVqPKZnPb=gUmSLjzxENL8qQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello, > > I downloaded and built Linaro Android 14.03 from source (replica build > using pinned manifest) on Ubuntu 13.04 (64-bit) machine. After flashing it > booted successfully on my Samsung Arndale Board with Exynos 5250 (Cortex > A15). > > But there is no display on my HDMI monitor. It just remains black. It looks > like its not getting any signal from board at all. > > What am I missing here? > > Thanks in advance. > > > > -- > -Meraj >

10 years, 10 months

Building a smaller android for Arndale Board

by Mohammad Merajul Islam Molla

Hello, I would like to build a smaller version of android by excluding some built in apps and some external programs (inside .../external/...). I could exclude the apps by modifying - .../build/target/product/sdk.mk and .../build/target/product/generic_no_telephony.mk files. Build was successful for Arndale board using Linaro Android 14.03 replica build and it reduces system.tar.bz2 size by about 15MB. But I can't seem to find any document or reference on the web on how I can exclude building some programs in 'external' directory. Which makefiles do I need to modify for this? What's the process? -- Thanks, -Meraj

10 years, 10 months

Fwd: [LNG] Re: error while cloning the linaro android kitkat 4.4

by Vincent Hsu

forward to linaro android list ---------- Forwarded message ---------- From: <pandaboard111(a)gmail.com> Date: Wed, Apr 16, 2014 at 10:09 PM Subject: [LNG] Re: error while cloning the linaro android kitkat 4.4 To: linaro-networking(a)linaro.org Cc: rajkumar.thavti(a)sibridgetech.com can you tell me what's the solution of the problem, I face the same problem as you . thanks a lot ! 在 2014年3月7日星期五UTC+8下午1时20分34秒，rajkuma...(a)sibridgetech.xn--com:-7z8fk634a > Hi All, > > I want to build android kitkat on pandaboard...i have downloaded linaro > android build script from > > http://releases.linaro.org/13.11/android/panda and when i run the script > i got cloning error after few hours of fetching the tags and branches... > > the script throws the following message... > Traceback (most recent call last): > File "/home/rajkumar/linaro-android-kitkat/.repo/repo/main.py", line > 408, in <module> > _Main(sys.argv[1:]) > File "/home/rajkumar/linaro-android-kitkat/.repo/repo/main.py", line > 384, in _Main > result = repo._Run(argv) or 0 > File "/home/rajkumar/linaro-android-kitkat/.repo/repo/main.py", line > 143, in _Run > result = cmd.Execute(copts, cargs) > File "/home/rajkumar/linaro-android-kitkat/.repo/repo/subcmds/sync.py", > line 650, in Execute > fetched = self._Fetch(to_fetch, opt) > File "/home/rajkumar/linaro-android-kitkat/.repo/repo/subcmds/sync.py", > line 319, in _Fetch > archive=self.manifest.IsArchive): > File "/home/rajkumar/linaro-android-kitkat/.repo/repo/project.py", line > 1087, in Sync_NetworkHalf > self._InitMRef() > File "/home/rajkumar/linaro-android-kitkat/.repo/repo/project.py", line > 2085, in _InitMRef > self._InitAnyMRef(R_M + self.manifest.branch) > File "/home/rajkumar/linaro-android-kitkat/.repo/repo/project.py", line > 2097, in _InitAnyMRef > self.bare_git.UpdateRef(ref, dst, message = msg, detach = True) > File "/home/rajkumar/linaro-android-kitkat/.repo/repo/project.py", line > 2306, in UpdateRef > self.update_ref(*cmdv) > File "/home/rajkumar/linaro-android-kitkat/.repo/repo/project.py", line > 2383, in runner > p.stderr)) > error.GitError: platform/packages/inputmethods/LatinIME update-ref: > fatal: 1d90d66fd637398868c98ba66480d17250bf1233^0: not a valid SHA1 > > so i want to as you guys what might be the possible root cause and > solution for this if possible... > > > -- You received this message because you are subscribed to the Google Groups "Linaro Networking" group. To unsubscribe from this group and stop receiving emails from it, send an email to linaro-networking+unsubscribe(a)linaro.org. To post to this group, send email to linaro-networking(a)linaro.org. To view this discussion on the web visit https://groups.google.com/a/linaro.org/d/msgid/linaro-networking/165b3898-b…<https://groups.google.com/a/linaro.org/d/msgid/linaro-networking/165b3898-b…> . -- Regards, Vincent Hsu

10 years, 10 months

Re: Re:Re: Linaro android start in Fastmodel--But mouse can't display in CLCD

by Jon Medhurst (Tixy)

On Wed, 2014-04-09 at 10:25 +0800, dcv wrote: > Before I press the Left Ctrl and Left Alt keys, I have selected CLCD > window. But when I select CLCD and grap mouse in it,I cannot find > mouse in it . The mouse pointer will be drawn by the Android system being run by the 'Fast Model'. Despite having the name 'fast', the emulation of the ARM system is a lot slower than real hardware, and for the first few minutes after boot the Android system tends to be very busy doing various background task and doesn't have much emulated cycles for updating the display. However, I see from you screen shots that the emulator has been running for 20 minutes, which should be enough time. I also see from the screenshots that you are running a model with one emulated CPU. Can you say which fast model you are running? Is it one of the pre-built ones that ARM supplies? And which Linaro Android build/release are you working with? I want to see if I can reproduce the problem. Regards -- Tixy

10 years, 10 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-android April 2014