Menu
▾
▴
Tree [c6cc8d] pie-x86 android-x86-9.0-r1 android-x86-9.0-r2 / boottime_tools / bootanalyze / History
| File | Date | Author | Commit |
|---|---|---|---|
| stressfs | 2018-03-23 |
Wei Wang
|
[bbf73e] Move boottime tools to system folder |
| Android.mk | 2018-03-23 |
Wei Wang
|
[bbf73e] Move boottime tools to system folder |
| README.md | 2018-03-23 |
Wei Wang
|
[bbf73e] Move boottime tools to system folder |
| bootanalyze.py | 2018-03-23 |
Wei Wang
|
[bbf73e] Move boottime tools to system folder |
| bugreport_anayze.py | 2018-03-23 |
Wei Wang
|
[bbf73e] Move boottime tools to system folder |
| config.yaml | 2018-03-23 |
Wei Wang
|
[bbf73e] Move boottime tools to system folder |
Read Me
bootanalyze
The bootanalyze tool helps to profile boot timing.
Per specific product modify config.yaml file to include
events you are looking for. Config should look like:
stop_event: <logcat log message which will terminate log collection after reboot>
events:
event1_name: <pattern that matches log message>
event2_.....
On some devise clock is showing incorrect time for first couple of seconds after boot.
To ensure correct adjustment of time, one has to include event in config that will
be present in dmesg log after clock correction.
