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/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
Hello, I am student In KOREA..
I want Install NEXUS7 2012 images on my NEXUS7 device.
I have downloaded 4 image files, boot.img, system.img, userdata.img, recovery.img
on http://snapshots.linaro.org/android/~linaro-android/nexus7-2012-linaro/last…
and I tried porting these files on my device using fastboot like this command that "fastboot flash boot boot.img"...
but my device is blocked and the logcat error message tell "couldn't find an OpenGL ES implementation"..
I can't solve this problem, can you give some solutions? and i attached logcat file with this mail.
and if I use linaro_android_build_cmds.sh..., How can I install?? I read the guide but there is only way install on sd card...
so I don't know make image files without sd card...
Thank U!!!
Hi, linaro,
I have found some of ECM patch for android jellybean in
"-- For bug #1042239 ECM doesn't work on Android Jelly Bean."
Could you send me the whole ECM patch by mail or
tell me where to download?
Thanks in advance !
*Jason Mei
mobile phone :18221120718
*
Hi there,
android-build.linaro.org is displaying "Could not load lava-job-info: Server error: 404". It looks like it started on the 21st of Feb.
Hope this is helpful.
Best,
Brendan
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
Hi guys,
One of my active research tasks at the moment is to characterize and
understand the endurance issues related to the eMMC products in Android
environment. So that's why I need to profile eMMC protocol on active
working system under some circumstances. I tried first to do it with
Android Emulator from Android SDK but unfortunately eMMC here is only used
by the SD Card emulation at that point, while for the internal disk images
NAND is used. And I need to see how Android works exactly with its internal
eMMC storage and not external. So my questions are:
1) Does Android Linaro provides the possibility to emulate internal disk
images with eMMC?
2) And if does, what is the situation with running Android Linaro in
virtual environment (let's say QEMU for example) ?
Hope to get any answers or hints from you. Thanks a lot!
--
Best Regards,
Dima Kostenich
I was going through this patch of ours "gralloc: Use FBIOPAN_DISPLAY
instead of FBIOPUT_VSCREENINFO to refresh display"
http://android.git.linaro.org/gitweb?p=platform/hardware/libhardware.git;a=…
and was wondering if we need to update this patch. The rationale
behind this patch is that the PUT_VSCREENINFO implementation of iMX53
Fb driver was broken at that time
https://bugs.launchpad.net/linaro-android/+bug/824506 so we switched
to PAN_DISPLAY.
Here is an old but relevant discussion on this topic on
android-porting list
https://groups.google.com/d/msg/android-porting/6Tn36GpVWJI which say
that the correct way to go forward is PAN_DISPLAY and put
PUT_VSCREENINFO as a fallback option. Which sounds about right.
The only thing which is confusing here is that the fb kernel
documentation suggest to use PAN_DISPLAY if we want to pan the screen
only (i.e. only xoffset and/or yoffset are modified) and use
PUT_VSCREENINFO otherwise. And in this particular case we modify other
screen info variables as well (e.g. activate), should we still be
doing PAN_DISPLAY then?
Regards,
Amit Pundir
On 14 February 2014 10:26, Cao Gao <caogao(a)umich.edu> wrote:
> Hi,
> Amit, thanks for the info!
> I got it switched to software OpenGL. But unfortunately, the Origen Quad
> (running ICS) keeps complaining about "System UI has stopped" and "Launcher
> has stopped" and cannot boot successfully; other boards running JB just
> cannot boot.
Try this http://android.git.linaro.org/gitweb?p=platform/frameworks/base.git;a=commi…
> Is it because these apps are using hardware rendering by default? Is there a
> way I can turn that to software rendering? Or is it because of other issues?
>
> Thanks a lot,
> Cao
>
>
> On Thu, Feb 13, 2014 at 4:06 AM, Amit Pundir <amit.pundir(a)linaro.org> wrote:
>>
>>
>> On 13 February 2014 02:15, Cao Gao <caogao(a)umich.edu> wrote:
>>>
>>> Hi,
>>> I'm trying to get software rendering instead of hardware rendering
>>> working on development boards.
>>> I found this (dated) post:
>>> https://groups.google.com/forum/#!topic/android-building/xtvBj2oekPo
>>> which enables software rendering on ICS for pandaboard.
>>> I have applied this patch to several boards, namely the Origen Quad
>>> running ICS, Odroid running JB, and Arndale Octa with Jelly Bean. None of
>>> them worked: I cannot even compile the source after changing the code.
>>> I'm wondering if anyone have some updates or other way to do that. Any
>>> help would be greatly appreciated.
>>
>>
>> Set "ro.nohardwaregfx=true" in your device config file and try this
>> http://android.git.linaro.org/gitweb?p=platform/frameworks/native.git;a=com…
>>
>>>
>>>
>>> Thanks,
>>> Cao
>>>
>>> _______________________________________________
>>> linaro-android mailing list
>>> linaro-android(a)lists.linaro.org
>>> http://lists.linaro.org/mailman/listinfo/linaro-android
>>>
>>
>
