-
-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App manager doesn't run if you relaunch it. #1355
Comments
having this issue too. samsung a13 5g. February Samsung ota security update is possibly related because after installing it i could no longer view appdata in mixplorer. only after mixplorer added shizuku to beta features could i manage other apps appdatas, after updating to that February security update. |
i didnt have am stable installed so i installed the latest and i was able to launch am 3.1.6 adb mode after pairing. still took ages to let me switch modes or choose pair etc. but it works. OP. maybe try that. i mostly use the snapshot version. the snapshot is the one that's having the issue, i dont remember it happening on 2 or 3.x but I'll share if it does. if i had to guess this is an indicator i need to reflash stock rom because having it at 0-1% free space corrupted files or whatever it does when you fill it up and stuff never seems to work fully normally thereafter. |
@vordx: Can you take some logs when you try to launch it from background using the debug build? According to your video, it launched fine, but it didn't list any apps. @ascendbeing: Please create a new issue with everything you have on the issue. Make sure to explain it in a step by step manner so that I can follow you. Please refrain from indicating what may went wrong other than the ones you're sure about (e.g., February updates, etc.). This creates a bias which makes it difficult to find out the actual issue. |
@MuntashirAkon although I am not the person who you asked for logs, here, I have some for you. This is what I see in logcat after I've previously ran AM and it worked, and this log is triggered either when trying to relaunch it (when it tries to go adb but fails) or when I got it on non root mode since that didn't work and am trying to change it to "auto" while wireless debugging is currently enabled in either case;
EDIT btw this is latest pre release (4.3.1?). but when this problem is active, no matter which AM app I attempt to launch (I have debug build installed and 4.3.x latest preview release, happens with latest stable too), none of them are able to claim adb. and this is galaxy a136u February 2024 security update. Linux localhost 4.14.186-27210951 #1 SMP PREEMPT Fri Feb 16 15:09:50 KST 2024 armv8l Android``` |
This part looks interesting. You need to be more thorough about your report. Instead of saying everything in one complex line, try to write it in an ordered list. This way I can understand the situation better and figure out what may go wrong. ADB is all about interacting with the |
Please check before submitting an issue
Describe the bug
App manager gets stuck when relaunching it from the background
To Reproduce
Screen_Recording_20240420_134426_AM.Debug.mp4
Expected behavior
Launch fine?
Screenshots
Shared a video above
Logs
No response
Device info
Additional context
No response
The text was updated successfully, but these errors were encountered: