X Logcat Manager APK

<p><i>XLogcatManager</i> is an Android app to improve <a href='https://cs.android.com/android/platform/superproject/+/android-13.0.0_r3:frameworks/base/services/core/java/com/android/server/logcat' target='_blank' rel='nofollow noopener'><code>LogcatManager</code></a> added in Android 13 using Xposed hooks. The app requires a <b>rooted device</b> to work.</p><p>Android 13 added <a href='https://cs.android.com/android/platform/superproject/+/android-13.0.0_r3:frameworks/base/services/core/java/com/android/server/logcat' target='_blank' rel='nofollow noopener'><code>LogcatManager</code></a> which shows a dialog when an app runs logcat command that has READ_LOGS permission before it is allowed to read system wide logs and access is only allowed for the next 60s, after which approval is required again. Access dialog will only be shown if the app is on the top, even if it has a foreground service, and access will be denied for all other background apps automatically. On previous android versions, the app only needed to be granted <code>READ_LOGS</code> permission once with <code>adb</code> or <code>root</code> and then could read logs whenever it wanted.</p><p>The <i>XLogcatManager</i> xposed module was created to allow rooted users to not have to grant <code>adb</code> or <code>root</code> access to apps that shouldn't require it just to read logs by solving <code>LogcatManager</code> design issues and some bugs.</p><p><br><b>Features</b></p><ul><li>Allows access till next reboot to the app if users selects allow button in the allow access dialog instead of just for the next 60s.</li><li>No 60s timeout to reshow dialog if access was (accidentally) denied by user.</li><li>The dialog will also show for apps with foreground service instead of just top apps.</li><li>Fixes the bugs mentioned in the <a href='https://issuetracker.google.com/issues/243904932' target='_blank' rel='nofollow noopener'>issuetracker issue</a> based on the solutions provided, but implementation is slightly different in some cases due to method hooking limitations.</li></ul>