0% found this document useful (0 votes)
18 views

Logcat

The log entries record system events like launching an activity, binding to a service, garbage collection, and timing information for an app. It shows the app launching a splash screen activity, then returning to the main activity. It also captures profiling data being saved to disk and notices of the app going into the background.

Uploaded by

tarabanegorik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
18 views

Logcat

The log entries record system events like launching an activity, binding to a service, garbage collection, and timing information for an app. It shows the app launching a splash screen activity, then returning to the main activity. It also captures profiling data being saved to disk and notices of the app going into the background.

Uploaded by

tarabanegorik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

--------- beginning of system

12-27 12:19:59.993 24621 24621 I ContentProviderMonitor: PerfMonitor


installContentProviders : before publish content providers
12-27 12:20:00.265 24621 24621 W Looper : PerfMonitor looperActivity :
package=com.uamobile.game/com.uamobile.launcher.activity.SplashActivity time=260ms
latency=508ms running=118ms procState=2
ClientTransaction{ callbacks=[android.app.servertransaction.LaunchActivityItem]
lifecycleRequest=android.app.servertransaction.ResumeActivityItem }
historyMsgCount=2 (msgIndex=2 wall=506ms seq=2 running=155ms runnable=44ms io=156ms
late=4ms h=android.app.ActivityThread$H w=110)
12-27 12:20:00.266 24621 24621 W Looper : PerfMonitor looperActivity :
package=com.uamobile.game/com.uamobile.launcher.activity.SplashActivity time=0ms
latency=769ms running=0ms procState=2
ClientTransaction{ callbacks=[android.app.servertransaction.TopResumedActivityChang
eItem] } historyMsgCount=3 (msgIndex=2 wall=506ms seq=2 running=155ms runnable=44ms
io=156ms late=4ms h=android.app.ActivityThread$H w=110) (msgIndex=3 wall=260ms
seq=3 running=118ms runnable=26ms io=19ms late=508ms h=android.app.ActivityThread$H
w=159)
12-27 12:20:00.965 24621 24768 W BpBinder: PerfMonitor binderTransact : time=293ms
interface=com.google.android.gms.measurement.internal.IMeasurementService code=11
12-27 12:20:02.726 24621 24621 I Timeline: Timeline: Activity_launch_request
time:79409758
12-27 12:20:02.745 24621 24621 W Activity: Slow Operation: Activity
com.uamobile.game/com.uamobile.launcher.activity.SplashActivity onActivityResult
took 165ms
--------- beginning of main
12-27 12:20:04.234 24621 24621 W MirrorManager: this model don't Support
12-27 12:20:04.426 24621 24621 I Timeline: Timeline: Activity_launch_request
time:79411459
12-27 12:20:07.646 24621 24672 I m.uamobile.gam: ProcessProfilingInfo
new_methods=4925 is saved saved_to_disk=1 resolve_classes_delay=8000
12-27 12:20:10.683 24621 24768 I FA : Application backgrounded at:
timestamp_millis: 1703676008640
12-27 12:20:47.677 24621 24672 I m.uamobile.gam: Waiting for a blocking GC
ProfileSaver
12-27 12:20:47.686 24621 24672 I m.uamobile.gam: WaitForGcToComplete blocked
ProfileSaver on HeapTrim for 9.462ms
12-27 12:23:36.964 24621 26685 I FA : Application backgrounded at:
timestamp_millis: 1703676214929
12-27 12:24:31.298 24621 24621 W Choreographer: Frame time is 0.14015199 ms in the
future! Check that graphics HAL is generating vsync timestamps using the correct
timebase.

You might also like