Linaro-android January 2012

linaro-android@lists.linaro.org

36 participants
65 discussions

by Zach Pfeffer

So our current naming scheme is awful. staging- landing- tracking- ick ick ick We'd like to make this better, here's the idea: old new staging-vexpress-a9 ics-armlt-stable-gcc46-vexpress-a9 tracking-panda ics-tilt-tracking-gcc46-panda aosp-panda ics-aosp-stable-gcc44-panda staging-imx53 ics-freescalelt-stable-gcc46-imx53 panda-4.4 ics-tilt-upstream-gcc46-panda landing-snowball ics-igloo-stable-gcc46-panda landing-panda ics-omapzoom-stable-gcc46-panda, keep staging-panda ics-tilt-stable-gcc46-panda staging-origen ics-samsunglt-stable-gcc46-origen panda ics-kwg-upstream-gcc46-panda panda-4.4 ics-aosp-stable-gcc44-panda Its basically, <type of Android>-<kernel source>-<kernel type>-<toolchain version>-<target> Hopefully this will allow people to figure out what's what. Comments, questions, concerns? -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams 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

13 years, 12 months

What our customers want from Android

by Zach Pfeffer

So I've been talking to our customers (10 at last count) and they really like what we're doing. There are three things that are getting in their way: linaro-android-media-create GCC4.6 frequent kernel upgrades They love our builds, but they'd really like it if they could get stock AOSP builds for their boards on stable kernels that they can work with using fastboot that have been CI tested and QA'd. I'm not advocating for the wholesale destruction of our current way of life, tip kernels, tip toolchains, linaro-android-media-create, but I would like to move in a direction that gives our users what they want. -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams 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

14 years, 1 month

ics with armhf build

by Guruswamy, Senthilvadivu

Hi, Has anyone succeeded in -mhard-float build for ICS ? I am interested in benchmarking the performances w.r.t soft and hard float builds. If armhf provides positive results on performance, then we could try to have this as default for future OMAP SW releases. I could build u-boot and kernel with hard-float options, but not knowing where to start for the android Filesystem. I used the android toolchain 4.6.2 (the gold pointed by Bero) I could find armhf ubuntu prebuilt images but not ICS. Regards, Senthil

14 years, 1 month

Please fill in Weekly status.

by Tony Mansson

Hello guys. There was an issue with our meeting pages resulting from the recent remake of our Team "home page" but that has been fixed now. Please go to https://wiki.linaro.org/Platform/Android/Meetings/2012-02-01 and report the past weeks accomplishments and next weeks plans. I very much appreciate to have the bug number included if you talk about bugs. BR, Tony

14 years, 1 month

Initial list of Blueprints for 12.02, from the Developer Platform Team and Android Team

by Zach Pfeffer

Actually including linaro-android and modifying the subject a little... On 30 January 2012 22:24, Zach Pfeffer <zach.pfeffer(a)linaro.org> wrote: > Linaro Android 12.02 is also ready to roll: > > https://launchpad.net/linaro-android/+milestone/12.02 > > We're generally working through the issues from the last cycle listed > in the 12.01 spreadsheet entry with a distinct Snowball bent this > cycle - since we're trying and get Google Hangouts working on it. For > the future, we'll generally put a heavy emphasis on working to make > all features green. > > The test sheets are here: > > Versatile Express A9 > https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AnpUtxWjZbP9dENmW… > > iMX53 > https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadHlNN… > > Panda > https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadHFPb… > > Snowball > https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadHJoV… > > Origen > https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadHJXV… > > booya > > On 30 January 2012 21:21, Ricardo Salveti <ricardo.salveti(a)linaro.org> wrote: >> Hi guys, >> >> As we're almost done with 12.02 planning, I'd like to share the >> current blueprints we intend to work during the 12.02 cycle: >> https://launchpad.net/linaro-dev-platform/+milestone/12.02 >> >> I know this is a quite short cycle, as we'll have the Linaro Connect, >> Android Builders and ELC, but I really hope to get most of the >> blueprints done during Connect's hacking sessions. >> >> Some interesting topics we'll cover this month: >> * Adding the USB-Host enablement test cases at LAVA >> * Start testing and validating the daily Linaro Native and Cross GCC packages >> * Enable ARMHF Precise based builds >> * Update XBMC to the latest 11.0 Beta release (currently Beta 2) >> * Sysroot build automation >> * Backporting of Unity 5, bringing the latest development from the GWG >> * Finalizing the Cross Buildd with Multi-Arch support >> >> And a few other bug fixes :-) >> >> Hope you enjoy ;-) >> >> Cheers, >> -- >> Ricardo Salveti de Araujo >> >> _______________________________________________ >> linaro-dev mailing list >> linaro-dev(a)lists.linaro.org >> http://lists.linaro.org/mailman/listinfo/linaro-dev > > > > -- > Zach Pfeffer > Android Platform Team Lead, Linaro Platform Teams > 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 -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams 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

14 years, 1 month

Re: Touch screen problem

by Bharathi Subramanian

Hi, If the interrupt count is incrementing, you should get the touch event in GetEvent command output. Did you changes the already existing touchscreen settings or wrote a separate driver for the SPI? Bye :) -- Bharathi Subramanian

14 years, 1 month

Can anyone think of a workaround for deleting a built-in app in Android?

by Tony Mansson

Hi, Can anyone think of a workaround for deleting a built-in app in Android? All the apps in our builds get the status of "built-in" as opposed to "downloaded". This makes them impossible to uninstall. If we want to debug one of our apps with DS-5 CE, we must allow it to be uploaded and installed by DS-5. That's how this tool works. You can't install the same app twice and you can't delete a built-in app. So we need to remove the app to be debugged from the build which is inconvenient. You may have to mount /system/app writeable (which I think is OK for a developer edition like Linaro Android, it could be a build option?) and muck around in the database yourself since neither adb uninstall or the Settings app is keen on removing a built-in app. Can it be done? /Tony

14 years, 1 month

Inbjudan: Post Mortem with Android Team and contributors @ fre 2012-01-27 14:00 - 14:30 (linaro-android@lists.linaro.org)

by Tony Mansson

Du har blivit inbjuden till följande händelse. Titel: Post Mortem with Android Team and contributors Hi. let's meet up for a quick flashback on the 12.01 cycle and sum up all the good and bad things. Drop me a mail if you want to discuss anything specific and I'll put it on the agenda here: https://docs.google.com/a/linaro.org/document/d/1qYQX4FSc8oaIbKmVmFZJL9HoQI… När: fre 2012-01-27 14:00 – 14:30 Stockholm Var: Mumble Kalender: linaro-android(a)lists.linaro.org Vem: * tony.mansson(a)linaro.xn--org-4n0a organisatör * linaro-android(a)lists.linaro.org * Andy Doan Händelseuppgifter: https://www.google.com/calendar/event?action=VIEW&eid=aXIzdjg5cWtmZzk0cGtjc… Inbjudan från Google Kalender: https://www.google.com/calendar/ Detta e-postmeddelande har skickats till kontot linaro-android(a)lists.linaro.org eftersom du är deltagare vid denna händelse. Om du inte vill få notiser om denna händelse i framtiden kan du avvisa denna händelse. Du kan även registrera dig för att få ett Google-konto på https://www.google.com/calendar/ och kontrollera notisinställningarna för hela kalendern.

14 years, 1 month

Touch screen problem

by Francesco Sarasini

Hi all, I have got the board Chipsee BeagleBoard-XM Expansion V2. It mounts ads7846 touchscreen. In dmesg I have: ads7846 spi3.0: no device detected, test read results was 0x00000000 ... regulator_init_complete: vads7846: incomplete constraints, leaving on and the touchscreen doesn't work. Any suggestions? Thanks Francesco

14 years, 1 month

[ANN] New universal seed ("uniseed") is ready to be used for build

by Paul Sokolovsky

Hello, An updated seed for Android platform is available as http://android-build.linaro.org/seed/uniseed.tar.gz . The requirement when preparing this seed was to make one which includes all repositories used by our manifest. Unfortunately, with such approach we just had swing of pendulum from one extreme to another. The old seed tarball was based only on (now pretty dated) pandaboard manifest, so other boards had to fetch increasingly more source with it. The new seed became not only comprehensive, but also very big and thus sluggish to download: its size 14Gb which is 4+ times increase over the previous one. So, it's clear that we'll need other iteration(s) to find good compromise, but in the meantime the new seed fixes issues we had with older one: increasing rate git fetch failures and overall fetch times. With new seed, totals source preparation time is ~10mins. With the old one, we had ~9mins in the best cases. For the worst, I specifically did some statistic analysis and plotted graphs: https://wiki.linaro.org/Platform/Android/SeededBuilds#Benchmarks_and_Statis… As they show, there were builds were source preparation took almost half an hour. They also show that besides background slowly increasing checkout times, it big time increases happen in jumps (apparently when big repository, like kernel, being added/changed). To use the new seed, REPO_SEED_URL should be set to the URL provided: REPO_SEED_URL=http://android-build.linaro.org/seed/uniseed.tar.gz I made a number of builds using new seed (~pfalcon/*-uniseed) which didn't show any issues (I don't expect any "what actually gets built" concerns - we've done with those during initial seed builds leveraging). So, I would like to propose switching to the new seed once release is done, for example, this Saturday, to have results by Monday. Please let me know if this sounds ok. 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

14 years, 1 month

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-android January 2012