XLogcatManager

dev.agnosticapollo.xlogcatmanager
by Zapstore _@zapstore.dev

Republished from GitHub / F-Droid by the Zapstore main account.

XLogcatManager is an Android app to improve [`LogcatManager`](https://cs.android.com/android/platform/superproject/+/android-13.0.0_r3:frameworks/base/services/core/java/com/android/server/logcat) added in Android 13 using Xposed hooks. The app requires a **rooted device** to work.

First release: Jan 28, 2024, 1 total release.

Most recent release: Jan 28, 2024.

Repo

Appears in 0 app stacks.

0 sats / 0 zaps received in the past year.

Sats Received

Underlying data available via MCP: app_zaps, app_releases.

Zap Count

Underlying data available via MCP: app_zaps, app_releases.

Releases

  • Jan 28, 2024 0.2.0
    # Changelog ## [v0.2.0] - 2024-01-28 00.25 ### Changed - Bump `compileSdkVersion` and `targetSdkVersion` to `34`. ([`eb600e3a`](https://github.com/agnostic-apollo/XLogcatManager/commit/eb600e3a)) ### Fixed
    More…
    - Fix hooking for Android 13 newer revisions - The static final int fields were being optimized out during build time and references were replaced with literal value. This caused the `NoSuchFieldError` exception to be thrown when getting the field values with `XposedHelpers.getIntField()`. To fix this, ported over static values directly into `XLogcatManagerService` class instead of getting them dynamically, the field values haven't still been changed in Android 14, so not an issue for now. - The `LogcatManagerService$LogcatManagerServiceInternal` class has been replaced with `LogcatManagerService$$LogAccessDialogCallback` in AOSP, which caused the `ClassNotFoundError` to be thrown. To fix this, we first attempt to get `LogcatManagerServiceInternal` and if that fails, then we use `LogAccessDialogCallback`. https://cs.android.com/android/_/android/platform/frameworks/base/+/db1ed6fa670ad261b81d1886cb947f235e3ce802 - The `LogAccessDialogActivity` class has been moved from system server to system UI package, which caused the `ClassNotFoundError` to be thrown. To fix this, we now hook the `com.android.systemui` package as well and we attempt to hook for both `android` and `com.android.systemui` packages, and if `com.android.server.logcat.LogAccessDialogActivity` class is found, we hook its methods and if `com.android.systemui.logcat.LogAccessDialogActivity` class is found, we hook its methods instead. **Users who are updating the app instead of a new install will need to manually enable `System UI` in (LSPosed) module scope for `XLogcatManager`.**. https://cs.android.com/android/_/android/platform/frameworks/base/+/fc13cb1d680d57ea6401e2d45dfb1e46bf046fc7 Closes [#2](https://github.com/agnostic-apollo/XLogcatManager/issues/2) ([`cdace1a6`](https://github.com/agnostic-apollo/XLogcatManager/commit/cdace1a6)) ## [v0.2.0]: https://github.com/agnostic-apollo/XLogcatManager/compare/v0.1.0...v0.2.0