linaro-android January 2016

linaro-android@lists.linaro.org

5 participants
4 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

Re: [Linaro-validation] lava-android-test development state

by Milosz Wasilewski

Petr, On 19 January 2016 at 18:34, Petr Vorel <petr.vorel(a)gmail.com> wrote: > Hi there, > > what is the development state of lava-android-test? > * last development happen year ago, last tag 2014.01 > * not in Linaro's patchwork (https://patches.linaro.org/) > * no Debian package (there is empty git repo pkg/lava-android-test.git) > * last build isn't in PyPi (well other packages seems to be even pulled from > PyPi). > > Is it considered as done, or just abandoned? (if yes, why?) It's not used any more. The main reason (from my perspective) was inability of matching the test results to executed tests. The test that were important to us were migrated to lava-test-shell. Second reason for dropping support for lava-android-test was increasing difficulty in maintaining lava-android-test dependencies on LAVA servers deployed in our LAB. This solution didn't scale well and was abandoned. We have legacy support for lava-android-test in multi node environment if someone still wants to use this code. However my personal recommendation is to move to lava-test-shell. milosz > > I'm considering to use it for testing Android firmware builds, it looks nice... > > Thanks for info. > > Kind regards, > Petr > > PS: I'm sorry to posting to both lists, not sure which one is the right one. > _______________________________________________ > linaro-validation mailing list > linaro-validation(a)lists.linaro.org > https://lists.linaro.org/mailman/listinfo/linaro-validation

8 years, 9 months

lava-android-test development state

by Petr Vorel

Hi there, what is the development state of lava-android-test? * last development happen year ago, last tag 2014.01 * not in Linaro's patchwork (https://patches.linaro.org/) * no Debian package (there is empty git repo pkg/lava-android-test.git) * last build isn't in PyPi (well other packages seems to be even pulled from PyPi). Is it considered as done, or just abandoned? (if yes, why?) I'm considering to use it for testing Android firmware builds, it looks nice... Thanks for info. Kind regards, Petr PS: I'm sorry to posting to both lists here and linaro-validation) as I'm not sure which one is the right one.

8 years, 9 months

Blur vs. Block on icon highlighting

by Shawn Guo

Hi, I'm running into a problem on Android 5.1 when using keyboard to move input focus among different application icons. It seems that the problem may be related to how application icon is highlighted when it gets input focus. On customer's system, the application icon will be highlighted with a blur effect around it. As a comparison on hikey, I found that the icons gets highlighted with a square block around them. The attached pictures demonstrate the differences there. I guess that such input focus highlighting effect should be done by GPU. But the customer's system runs a same version Mali DDK as Hikey. So I'm wondering if this different behavior is caused by Android level of configuration. That's why I'm asking help from Android mail list. Any comment or hint about how this different behavior comes will be much appreciated. Thanks. Regards, Shawn

8 years, 10 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-android January 2016