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 John,
[ + linaro-android ML ]
I have two questions for working on AOSP Hikey:
- When use "adb shell" to execute commands, then it will return back
the execution value and error code. Usually we will get back the new
line character as "\r\n", but I found for AOSP releasing it will
only return back "\n" for new line.
So is this decided by system's booting script or decided by shell's
building? I want to change back to use "\r\n" for the format.
- Second question is related with adb's permission. On my pc I need
add "sudo" or change to root "sudo -s" for adb commands, otherwise
it will report "insufficient permission".
This is okay when I manually send adb commands, but when use python
script to execute adb commands it also need add "sudo" for add adb
related commands.
So want to check if there have more convienent method so can let
normal user to use adb command?
Thanks,
Leo Yan
