# Fixing simpleperf broken records

DevFeed: [Fixing simpleperf broken records](<https://devfeed.tech/articles/fixing-simpleperf-broken-records-25623.md>)

Original publisher: [Read original article](<https://blog.p-y.wtf/fixing-simpleperf-broken-records>)

Author: Pierre-Yves Ricau

Published: 2022-01-21T18:13:19Z

Content type: tutorial

Language: en

Sources: [Py's blog](<https://devfeed.tech/sources/py-s-blog.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [code](<https://devfeed.tech/tags/code.md>), [developer](<https://devfeed.tech/tags/developer.md>), [performance](<https://devfeed.tech/tags/performance.md>), [profiling](<https://devfeed.tech/tags/profiling.md>)

## AI overview

This tutorial explains how to diagnose and work around unusable simpleperf traces on Android when truncated callchain roots create breaks in the main-thread call tree. It also describes simpleperf's relationship to Android Studio's callstack sampling features.

## Source excerpt

Summary This blog shows how to fix simpleperf traces which are otherwise unusable because they include samples with truncated callchain roots. Read on to learn more about what these crazy words mean! Profiling Android apps As an Android developer, I ...