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
Hi,
My name is Javier Romero and live in Buenos Aires, Argentina.
I'm an electronic technician and teach Android OS in an IT institute, also
work as a Linux Sysadmin.
Would like to know if there is something where I can help with, on the Linaro
Mobile Group.
I appreciate your kind attention.
With my Best regards,
*Javier Romero*
*E-mail: xavinux(a)gmail.com <xavinux(a)gmail.com>*
*Skype: xavinux*
Hello,
The latest Jenkins LTS release, 1.625, requires Java7 to run (to give
some context, Java9 is in beta now, Java7 is many years old). As
learned with some pain on ci.linaro.org, which already upgraded, this
requirement applies not just to a Jenkins master, but also to build
slaves, just to run slave agent to be connected to a master.
We install both Java6 and Java7 on android-build.linaro.org slaves, but
the default is still Java6, "for compatibility with older Android
versions", as a comment says.
Is Java6 being a default still relevant? The easiest way to accommodate
the upcoming upgrade is just to switch default to Java7. If there're
issues expected with that, we can follow an alternative way of adding
adhoc version overrides for slave startup.
--
Best Regards,
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
On Sun, Nov 1, 2015 at 10:07 PM, YongQin Liu <yongqin.liu(a)linaro.org> wrote:
> On 2 November 2015 at 11:59, John Stultz <john.stultz(a)linaro.org> wrote:
>>
>> You can try to objdump -d the files and diff the output.. That might
>> help narrow down where things are different.
>
> Sorry, I can not find out anything from the output.
>
> Not able to read the objdump output:(
>
> Attached the binaries and objdump output files here, in case if someone
> likes to check the binary file.
Sorry. Yea, objdump isn't super useful after the symbols have been
stripped out. Might try to build w/ symbols and try again?
thanks
-john
They're now accepting pre-orders for the Nexus 5X, saying it'll leave their
warehouse on November 9 -- so if the past is any indication, we'll see
6.0.0_r2 or 6.0.1_r1 next week to match what's actually on there.
Still no sign of the 6P...
ttyl
bero