Manoel Aranda Neto

cc @bruno-garcia

example: https://github.com/getsentry/sentry-java/blob/main/sentry-android-fragment/src/main/java/io/sentry/android/fragment/SentryFragmentLifecycleCallbacks.kt#L134-L140

Android now recommends improving for 90fps, which means ~11ms per frame instead of 60fps/~16ms, maybe we can consider this when working on the Mobile vitals and how we define slow/frozen...

That's what it'd look like.

Ideally, the file format would match with the radiography on iOS, so Sentry UI could prettify and offer features like collapsing, etc...

it'd be possible ootb only via bytecode manipulation or executing `logcat params...` and writing the output to a file or parsing the text, of course. I'm not sure if it's...

We can execute `Runtime.getRuntime().exec("logcat -v time");` and listen the buffer in a while loop. https://github.com/pedrovgs/Lynx/blob/master/lynx/src/main/java/com/github/pedrovgs/lynx/model/Logcat.java

> Sounds great! Will it require extra permission or slow down the app - inside release app builds? It does, but not for all versions apparently. https://github.com/pedrovgs/Lynx/blob/7b1f25172f2bd3f4563076dcd58ec532aebfb9f1/sample/src/main/AndroidManifest.xml#L20-L21 Well, ideally this...

https://developer.android.com/studio/preview/features#logcat Not sure if the logcat output has changed or the IDE is parsing it, but worth checking it when working on this issue, worst case we have to parse...

I suspect we can reuse this logcat parser from the Android framework itself https://cs.android.com/android/platform/superproject/+/master:development/tools/bugreport/src/com/android/bugreport/logcat/LogcatParser.java