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
Hi, Bero
Any idea why the size of the binaries compiled from the same source files
are different between the flounder version and the flo version?
10:29:01 liuyq: marshmallow$ ll
out/target/product/{flo,flounder}/system/bin/libstagefright_mp3dec_test
-rwxrwxr-x 1 liuyq liuyq 231360 Nov 2 10:29
out/target/product/flo/system/bin/libstagefright_mp3dec_test*
-rwxrwxr-x 1 liuyq liuyq 124684 Nov 2 10:28
out/target/product/flounder/system/bin/libstagefright_mp3dec_test*
10:29:39 liuyq: marshmallow$
The binaries are 32bit static linked version compiled with the attached
Android.mk
And the size of libc.so files are different as well.
10:37:13 liuyq: marshmallow$ ll
out/target/product/{flo,flounder}/system/lib/libc.so -h
-rwxrwxr-x 1 liuyq liuyq 659K Oct 29 15:34
out/target/product/flo/system/lib/libc.so*
-rwxrwxr-x 1 liuyq liuyq 540K Oct 19 18:32
out/target/product/flounder/system/lib/libc.so*
10:37:21 liuyq: marshmallow$
Some features are not compiled into the libc.so on the flounder platform?
--
Best Regards,
Yongqin Liu
---------------------------------------------------------------
#mailing list
linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org>
http://lists.linaro.org/mailman/listinfo/linaro-android
Hello,
We upgraded from Gerrit 2.8 to 2.10 in the beginning of September, and
it went pretty smooth and let us overcome few annoying issues and enjoy
few new features and better integration with other apps.
Unfortunately, 3 months later, 2.10 also feels old, with 2.12 having
been released in the interim. With various Linaro groups continuing to
leverage advanced Gerrit features and integrations with other apps
(Jenkins, Bugzilla), Systems team faces various bugs and issues. None
of these issues are too grave, but they're quite convoluted and take
much time to be researched and understood. And then we find out that
it's a known issue in 2.10, which was fixed in later versions.
Jenkins' Gerrit integration already requires 2.12 for full
functionality and warns about our version being too old and some
features not supported. Which in turns brings concerns that every
time it doesn't work as expected, it may be because Gerrit plugin is
no longer tested with 2.10 and hits some issue pertaining to it.
With that in mind, Systems team would like to start planning for
next Gerrit upgrade, and move straight to the latest, 2.12.
To remind, the reason we didn't upgrade to 2.11 last time, was because
2.10 was the last version which included old-style change review
screen, and we wanted to provide smoother transition and let people to
try the new screen at their own pace. So, if you still use the old
design, please go to https://review.linaro.org/#/settings/preferences ,
and in "Change View:" dropdown, select "New Screen", and give it a
chance with the help of this doc:
https://review.linaro.org/Documentation/user-review-ui.html
And if you have any concerns regarding the upgrade, please speak up now.
Otherwise, we can do it in one of the following timeframes:
1. Upgrade in January.
2. Upgrade a bit later, but still before the Connect.
3. Discuss and plan upgrade at the Connect.
Systems team votes for the choice 1, upgrade next month (apparently, by
the end of), as that will allows us to deliver smoother Gerrit
experience to other teams, instead of firefighting older version issues.
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
