MuntashirAkon/AppManager

AppManager initialisation

Open

#1829 opened on Nov 20, 2025

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Java (3,673 stars) (236 forks)batch import
Help Wanted

Description

Describe the existing feature/documentation

No response

Describe your problem(s)

Hi, I'm coming for some help in a chain of issues I experience, issues that end up with AppManager. Long story long:

All begins with starting the app that hangs on splash screen with initialisation message. It would hang forever, but I have to go quick setting tiles and tap wireless debugging. It's always disabled even when all debugging is enabled in dev options - which is weird. That's most probably my ROM issue, the ROM cannot be changed - let's assume - forever. Realme disabled bootloader unlocking year ago for non china devices. I'm using Shizuku too. It doesn't work with "disable permission monitoring" TOGGLED OFF in dev options. On the other hand - USB-C pendrive doesn't work with "disable permission monitoring" TOGGLED ON. Bit confusing, huh? If you're not lost yet - what I need to do is to clean up the mess for fluent workflow. I always forget that "disable permission monitoring" TOGGLED ON breaks pendrive connection. It's seen on the system but not mounted. I always hang at AppManager or Shizuku start because quick settings tile goes always off after some period of time (ROM issue - that's message from Shizuku). Needless to say: going to dev options and switching toggles every time is not very comfy and takes time.

I understand it all starts in device's ROM but it's impossible to change them both ATM. Btw I'm using wireless debugging and want it that way.

Any easier way to manage that all, mainly AppManager start but permission monitoring too?

Additional context

No response

Contributor guide

Tech stack
androidjava
Domain
mobile
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Android developmentAppManager codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
The issue is a support request about device specific initialization hangs. To address, first reproduce the hang in a similar environment. Examine the AppManager initialization code, particularly the splash screen logic and wireless debugging detection. Investigate interactions with Shizuku and the 'disable permission monitoring' toggle. Review comments on this issue for any suggested workarounds. Consider adding documentation or a troubleshooting guide for users with custom ROMs.