Closed Werve closed 1 month ago
Did you enable logging debug info in Matlog? It appears that it didn't take any debug logs. I've only found the following error but not any debug info which should've been printed before this:
java.io.IOException: java.io.IOException: Could not create session
at io.github.muntashirakon.AppManager.servermanager.LocalServer.checkConnect(LocalServer.java:116)
at io.github.muntashirakon.AppManager.servermanager.LocalServer.<init>(LocalServer.java:90)
at io.github.muntashirakon.AppManager.servermanager.LocalServer.getInstance(LocalServer.java:48)
at io.github.muntashirakon.AppManager.servermanager.LocalServer.restart(LocalServer.java:179)
at io.github.muntashirakon.AppManager.settings.Ops.autoDetectRootSystemOrAdbAndPersist(Ops.java:357)
at io.github.muntashirakon.AppManager.settings.Ops.init(Ops.java:221)
at io.github.muntashirakon.AppManager.settings.MainPreferencesViewModel.lambda$setModeOfOps$4$io-github-muntashirakon-AppManager-settings-MainPreferencesViewModel(MainPreferencesViewModel.java:126)
at io.github.muntashirakon.AppManager.settings.MainPreferencesViewModel$$ExternalSyntheticLambda12.run(Unknown Source:2)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
Caused by: java.io.IOException: Could not create session
at io.github.muntashirakon.AppManager.servermanager.LocalServerManager.getSession(LocalServerManager.java:88)
at io.github.muntashirakon.AppManager.servermanager.LocalServerManager.start(LocalServerManager.java:124)
at io.github.muntashirakon.AppManager.servermanager.LocalServer.checkConnect(LocalServer.java:111)
... 12 more
Caused by: java.lang.Exception: Server wasn't started.
at io.github.muntashirakon.AppManager.servermanager.LocalServerManager.useAdbStartServer(LocalServerManager.java:225)
at io.github.muntashirakon.AppManager.servermanager.LocalServerManager.startServer(LocalServerManager.java:254)
at io.github.muntashirakon.AppManager.servermanager.LocalServerManager.getSession(LocalServerManager.java:86)
... 14 more
I had left it with the default setting, which is verbose so they should be included:
I will try to recapture
I had left it with the default setting, which is verbose so they should be included:
I will try to recapture
I tried filtering all the log entries with D/
and found nothing.
I set only Debug in Matlog and captured two more times. 2024-02-23-09-47-47.zip
I set only Debug in Matlog and captured two more times. 2024-02-23-09-47-47.zip
Still no debug logs. No idea what's going on with it. Can you extract this file? /sdcard/Android/data/io.github.muntashirakon.AppManager.debug/cache/am.log
I set only Debug in Matlog and captured two more times. 2024-02-23-09-47-47.zip
Still no debug logs. No idea what's going on with it. Can you extract this file?
/sdcard/Android/data/io.github.muntashirakon.AppManager.debug/cache/am.log
Yes, but not via adb, apparently there are limitations in the new Fire TV 4K Max to adb permissions. I was able to extract it via Mixplorer launched from the device and granting the folder read permissions appeared. am.log
Yes, but not via adb, apparently there are limitations in the new Fire TV 4K Max to adb permissions.
This might actually be the issue.
The response for the following command
sh /storage/emulated/0/Android/data/io.github.muntashirakon.AppManager.debug/cache/run_server.sh 60001 b5cc1db213132f4f67c728d4814eb9a9
was
sh: /storage/emulated/0/Android/data/io.github.muntashirakon.AppManager.debug/cache/run_server.sh: Permission denied
This means either it couldn't access run_server.sh
via ADB or run_server.sh
does not have the execution permission.
Yes according to this article https://www.aftvnews.com/missing-storage-access-permission-in-fire-os-8-on-2nd-gen-fire-tv-stick-4k-4k-max-is-causing-issues-with-media-player-and-file-manager-apps/ that adb can no longer access "/sdcard/Android/data/" and "/sdcard/Android/obb/"
This also explains the message in Shizuku's first screenshot
Yes according to this article https://www.aftvnews.com/missing-storage-access-permission-in-fire-os-8-on-2nd-gen-fire-tv-stick-4k-4k-max-is-causing-issues-with-media-player-and-file-manager-apps/ that adb can no longer access "/sdcard/Android/data/" and "/sdcard/Android/obb/"
This also explains the message in Shizuku's first screenshot
I guess, we need to do this for App Manager as well (an unrelated but interesting issue: #948).
Latest update, I believe, has disabled access from localhost altogether.
We need a starter script that can also be run from another device. This is the only solution that may work after the latest update.
Should be fixed in 4f97928e97fd9da5a93c7ea1af40c682462b4e33
I've tried the latest debug build 4.0.0 beta01 (436) but it remains in no root mode. I've also tried to run the Custom commands described via adb shell with shizuku (aShell app) but both return Permission denied. The second command via normal shell returns file not found.
Logs?
Logs?
From Matlog DEBUG info: logs-2024-04-29-09-29-22.zip
From /sdcard/Android/data/io.github.muntashirakon.AppManager.debug/cache/am.log
am.zip
Note: After choosing the automatic mode of AppManager the RSA signature confirmation window for ADB (of Fire TV) appears and I set accept always.
I ran the two Custom Commands reported in AppManager in shell with aShell, then via Shizuku, and both returned Permission Denied.
Please check before submitting an issue
Describe the bug
I tried AppManager v3.1.4 Stable with Fire TV 4K Max 2 Gen (Android 11) but both auto mode and ADB on TCP fall back to no-root.
Shizuku after two tries with the 5555 option it connected.
Instead, with the Fire TV 4K Max 1 Gen (Android 9) AppManager worked properly.
To Reproduce
No response
Expected behavior
No response
Screenshots
No response
Logs
Logs using AppManager_v4.0.0-alpha02-DEBUG#2645: logs-2024-02-22-22-49-46.zip
Device info
Additional context
No response