Linaro-android August 2015

linaro-android@lists.linaro.org

11 participants
7 discussions

by Shawn Guo

Hi Guys, I need help on a Lollipop booting issue. I'm trying to boot Android 5.1.1 on a customer SoC which integrates Cortex-A9 MP and Mali 400. It's quite close to get into the launcher, but it fails to due to an ANR in SystemUI. The full logcat is attached, and some highlights of the log are as below. 1. There are quite some messages from Choreographer like this: I/Choreographer( 1220): Skipped 391 frames! The application may be doing too much work on its main thread. 2. There a number of window freeze timeout messages in the log. W/WindowManager( 1220): Window freeze timeout expired. W/WindowManager( 1220): Force clearing orientation change: Window{xxxxxxxxxxxxxx} 3. I see "Boot is finished", but right before it, there is a "BOOT TIMEOUT". W/WindowManager( 1220): ***** BOOT TIMEOUT: forcing display enabled I/SurfaceFlinger( 874): Boot is finished (88437 ms) I'm a bit new to Android, and running out of idea what is happening here. So any suggestions or comments about where to look at or how to debug such issue is highly appreciated. Shawn

8 years, 9 months

Re: [ANN] Round 2 (and 3) of Gerrit upgrade

by Paul Sokolovsky

Hello, https://dev-private-review.linaro.org/ has been upgraded to Gerrit 2.10.6. Upgrade went smooth, the only issue is that handful open reviews there are now in "Merge Conflict" state, as discussed below. However, I tried to merge a test review with such status and it went OK. If that won't work, a change need to be rebased and re-pushed from command line. To remind, the biggest change in 2.10.x is a new change summary screen. Every user will be notified about it via popup on first access, linking to detailed documentation: https://dev-private-review.linaro.org/Documentation/user-review-ui.html and offering choice to switch back to classic screen (support for which is dropped in 2.11, so use your judgement when you want to learn the new screen - now or later). Please let me know of any issues seen. If nothing big pops up, we'll finish 2.10.6 migration next weekend, upgrading https://review.linaro.org and https://lhg-review.linaro.org as discussed below. Thanks, Paul On Fri, 21 Aug 2015 16:25:58 +0300 Paul Sokolovsky <Paul.Sokolovsky(a)linaro.org> wrote: > Hello, > > As was announced previously, Linaro Systems team is working to upgrade > Gerrit version used on our hosts from 1-year old 2.8 to recent and > supported 2.10. Two weeks ago, we upgraded > https://android-review.linaro.org as a pilot. The upgrade went largely > OK, though as full disclosure, following issues were faced: > > 1. Upgrade uncovered issues with duplicate accounts. This issue is > mostly specific to android-review.linaro.org - it's the oldest Gerrit > system in Linaro which accumulated number of accounts from different > authentication services we used as well as community accounts. Other > systems are unlikely to be affected at all, and even on > android-review.linaro.org only few active users were affected and > issues were resolved proactively. > > 2. 2.10 exposed an AJAX caching issues we experienced intermittently > before - just to allow to nail them down and resolve consistently for > all servers. So, this is off the list. > > 3. The "biggest" issue we saw is that after the upgrade, all pending > open changes in Gerrit were changed to "Merge Conflict" state, > which was not resolvable from UI, with Gerrit suggesting to rebase and > re-push change from command line. Having done that, a reviewed worked > without a problem. We even received a report that this issue may be > related to the new review UI, switching to old screen allowed to > rebase a change via UI button. > > > With this in mind, we think we're ready for the next round of upgrade. > Based on previous discussions, this would be > https://dev-private-review.linaro.org , slated to upgrade next > weekend. We'd like to confirm that this plan works well for them. > > Otherwise, we'd plan to finish Gerrit upgrade (and do any needed > follow-up tweaks) before Connect, so there was productive work there > (and we can consult people on new UI/features they may want to use). > So, if everything goes smooth with dev-private-review.linaro.org, a > weekend after next (Sep, 5) we'd plan to upgrade 2 remaining systems: > https://review.linaro.org and https://lhg-review.linaro.org . Again, > we'd like to be sure that their stakeholders are OK with this. > > > > 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 -- Best Regards, 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

9 years, 11 months

Could Android source code build on ARM64 boards?

by Xinliang Liu

I am wonder is that possible to build android source code on ARM64 boards? Currently, it seems the android build system doesn't support arm64 arch as a host. If we want to support this native build, then what are the work should be do? Do you have ever try this? This is import that if we want to deploy ARM64 boards in the build cloud center. Usually, the build cloud should support Android build.

10 years

Using ADB boot options for Android Devices

by Sandeep Chawla

Hello Linaro Android Champions, Thanks for your efforts in making Lava a great automation platform for Android. I use Nexus10 fastboot driver on my devices, which flashes the boot image on the device. This leads to a problem that whenever the dispatcher issues 'adb reboot' command, the device reboot instead of being the fastboot mode as with the regular fastboot driver. Is there an option in the device.conf file to specify a different boot command ? If we could change the command from 'adb reboot' to 'adb reboot-bootloader' , the dispatcher would be able to work fine. Please let me know if you have any further questions. Thanks Sandeep

10 years

Duplicate user accounts on android-review.linaro.org

by Paul Sokolovsky

Hello, We recently upgraded Gerrit on android-review.linaro.org (former review.android.git.linaro.org) to 2.10.6, and it uncovered issue with duplicate accounts (not sure how it happened, there were some account table migrations, maybe it exposed inconsistencies which were latent before). The full list of dup accounts is below. Some folks are no longer with Linaro, other likely not use android-review.linaro.org actively, other are community accounts. And there's no easy way to see which of dup accounts is the right one. So, this mail is cc:ed to few folks I know may use this server, and if you see yourself in the list below, please respond too. So, what we need from you is: 1. Log in to https://android-review.linaro.org 2. Check that your group memberships look as expected at https://android-review.linaro.org/#/settings/group-memberships 3. Look up your numeric account ID at https://android-review.linaro.org/#/settings/ 4. Reply to this mail with the info above (whether your groups are ok, and account ID). Please let some time for resolution (I'm on vacation next week), if you're blocked by dup account issue, please ping Andy Doan or Matt Hart. Thanks, Paul full_name | preferred_email | count ----------------------+--------------------------------------+------ Tony Mansson | tony.mansson(a)linaro.org | 2 Omar Ramirez Luna | omar.luna(a)linaro.org | 2 tinoj antony | tinojantony(a)gmail.com | 2 Georgy Redkozubov | Georgy.Redkozubov(a)linaro.org | 2 Alan Bennett | alan.bennett(a)linaro.org | 2 Paul Beeler | sparksco(a)gmail.com | 2 Yusuf Burmawala | burmawala.yusuf(a)gmail.com | 2 Fahad Kunnathadi | fahad.k(a)linaro.org | 2 Ramesh Chandrasekaran | ramesh.chandrasekaran(a)stericsson.com | 2 Hongbo Zhang | hongbo.zhang(a)linaro.org | 2 Harigopal Gollamudi | harigopal.gollamudi(a)linaro.org | 2 Soumya Basak | soumya.basak(a)linaro.org | 2 Naresh Kamboju | naresh.kamboju(a)linaro.org | 2 Tyler Baker | tyler.baker(a)linaro.org | 2 Angus Ainslie | angus.ainslie(a)linaro.org | 2 Botao Sun | botao.sun(a)linaro.org | 2 Stefan Ekenberg | stefan.ekenberg(a)linaro.org | 2 Anil Kumar Koli | anil.koli.kumar(a)gmail.com | 2 ??Abhishek Paliwal | abhishek.23dec(a)gmail.com | 2 Romain Perier | romain.perier(a)gmail.com | 2 Rajagopal Venkat | rajagopal.venkat(a)linaro.org | 2 David Zinman | david.zinman(a)linaro.org | 2 Amit Khare | amit.khare(a)linaro.org | 2 Bintian Wang | bintian.wang(a)linaro.org | 3 Mathieu Poirier | mathieu.poirier(a)linaro.org | 2 Milosz Wasilewski | milosz.wasilewski(a)linaro.org | 2 -- Best Regards, 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

Gerrit 2.10.6 upgrade: All changes are stuck in "Cannot Merge due to Path Conflict" state

by Paul Sokolovsky

Hello, It was just just brought to my attention by Yongqin that after upgrade, all open changes appear to be stuck at "Merge Conflict" state, which is easily visible in the summary table: https://android-review.linaro.org/#/q/status:open Checking any single change, e.g. https://android-review.linaro.org/#/c/15987/ it says "Cannot Merge", and tooltip says "due to a path conflict". There's no "Rebase" button, tooltip says that rebasing should happen locally, and new version uploaded. Yongqin tried that with https://android-review.linaro.org/#/c/15996/ , and it cleared state and change was merged successfully after that. So, there's nothing fatal, but of course it's quite a chore to rebase all patches manually. My googling for what could be the cause of such problem after an upgrade, unfortunately didn't turn up much so far. But there're a lot of older (circa 2010) discussions of Gerrit behavior when harmless, not really conflicting concurrent commits to a repo threw changes into such state. They all relate to the times when Gerrit didn't support automatic conflict resolution or it was conservatively disabled. But on android-review.linaro.org, we exactly have those conservative "off" settings of circa-2.4 times. So, my hypothesis is that's what played role in such situation with upgrade, and i propose to have more process-friendly settings. Specifically, currently we have: Submit Type: Merge if necessary Automatically resolve conflicts: FALSE Require Change-Id in commit message: FALSE I propose to change it to: Submit Type: Rebase if necessary Automatically resolve conflicts: TRUE Require Change-Id in commit message: TRUE Let me know if there're any concerns. Not that these are "avoid problems in the future" changes, current conflicting changes will need to be re-uploaded by their authors manually. -- Best Regards, 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

Re: RFC: Gerrit version upgrade on Linaro hosts

by Paul Sokolovsky

Hello, With Vishal's approval below, and checking whether one of these days in the beginning of month is better/worse than another, https://android-review.linaro.org is finally upgraded today. The upgrade largely went OK, but there're at least few known issues: 1. There're duplicate user accounts exposed (same name/same email), with a known effect that such user can't be added as a reviewer/member of a group. 2. There're visible caching issues with Chrome. This is again a known issues, which was tackled with different degrees of success on different Gerrit hosts. The new version just exposes this issue very deterministically (e.g. new comments don't appear in Chrome until after delay). I'll be tackling these issues tomorrow. Let me know if you're affected by the above or see any other issue - there may be help required to collect info from different cases/verify fixes. Thanks! On Wed, 29 Jul 2015 15:52:47 +0530 Vishal Bhoj <vishal.bhoj(a)linaro.org> wrote: > +1. Sounds good to me. > > On 29 July 2015 at 15:51, Paul Sokolovsky <paul.sokolovsky(a)linaro.org> > wrote: > > > Hello Vishal, > > > > What do you think about Gerrit version upgrade on > > android-review.linaro.org , per the email below? > > > > Thanks. > > > > > > On Thu, 23 Jul 2015 17:27:19 +0300 > > Paul Sokolovsky <Paul.Sokolovsky(a)linaro.org> wrote: > > > > > Hello, > > > > > > All Linaro Gerrit services (4 of them) currently run Gerrit > > > 2.8.6.1, the latest of 2.8 branch, which is now 1 year old, and 3 > > > major releases behind the latest, 2.11. > > > > > > We (Systems) regularly get requests regarding features available > > > in newer Gerrit versions, and regularly face issues, which are > > > not even reportable upstream, as we run a pretty old version. > > > > > > With all the improvements we did to Gerrit management across > > > different installs lately, we're now ready to raise the question > > > of the version upgrade. Here're basic facts about recent Gerrit > > > versions: > > > > > > 1. Major change in 2.9 is introduction of new change summary > > > screen. It's pretty different by both looks and feel and it's > > > fair to say taht one needs to relearn Gerrit a bit with its > > > introduction. It's still possible to use old screen, until it's > > > removed in further versions. > > > > > > 2. 2.11 does remove support for old change summary screen. > > > > > > 3. 2.10 and 2.11 are actively supported and maintained (e.g. > > > 2.10.6 released Jun 29, 2.11.2 - Jul, 14). > > > > > > Based on this, we would like to propose upgrade to 2.10, to let > > > people some leeway to learn the new change screen, and be able to > > > switch back to the old screen in the meantime. > > > > > > As usual, we'd like to select single server for pilot upgrade > > > first, and among 4 we have, Linaro Android Gerrit, > > > https://android-review.linaro.org seems like a good candidate, as > > > it's used just by subset of Linaro teams, and at the same time, > > > used regularly to call it "tested" after the pilot period. > > > > > > > > > Things you can do/help with in the meantime: > > > > > > 1. Provide feedback on the general idea of the upgrade. > > > 2. Let us know if you'd like a server you regularly use to be > > > upgraded sooner rather than later. We in particular would like to > > > know whether Android Team (and other stakeholders) agree to pilot > > > new version on https://android-review.linaro.org > > > 3. Get feedback from any stakeholders which may be affected, > > > first of all, from Builds&Baselines, who run CI with Gerrit > > > integration. 4. Get acquainted with new change screen > > > "extramurally", by reviewing documentation with extensive > > > screenshots: > > > > > https://gerrit-documentation.storage.googleapis.com/Documentation/2.9/user-… > > > > > > > > > > > > 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 > > > > > > > > -- > > Best Regards, > > 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 > > -- Best Regards, 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-android August 2015