You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Android's Developer's settings there's an option to select the bug reporting manager. I csn imagine that having the right flags and asking for right permission would get Scoop into that list, solving the permission's problem (root/adb usage) and maybe save battery for users.
Unfortunately I still didn't have time to do enough research, so for now it's just an idea or suggestion.
The text was updated successfully, but these errors were encountered:
Interesting, I had never even thought of that 🤔. I did some preliminary searching around for information, but I couldn't really find anything that would indicate how I could get Scoop into that list.
Hi @TacoTheDank, I've been requested to investigate if this exact feature can also be added in App Manager (it can't right now). However, it might be possible for Scoop to have this feature. Looking at the framework source for Shell (here's a starting point for you), it appears that bug report handler relies on a system protected broadcast receiver com.android.internal.intent.action.BUGREPORT_REQUESTED (might vary among Android versions) which is sent to the selected bug report handler when triggered. Everything is good on that part (you can copy the exact behaviour from Shell, I think). The primary issue for Scoop would be to become the default bug report handler. The selection activity is available in settings or can be set directly via Global settings table. But it wouldn't work even if you select Scoop as the default bug report handler because you'd need your app to be whitelisted under bugreport-whitelisted (which you can do systemless-ly using Magisk or may get ActivityManager to return you package name using Xposed).
If you're really interested in this feature, I suggest first try whitelisting and selecting Scoop as a bug report handler and check if the broadcast receiver is actually called by the system and then proceed further. Good luck 😉
In Android's Developer's settings there's an option to select the bug reporting manager. I csn imagine that having the right flags and asking for right permission would get Scoop into that list, solving the permission's problem (root/adb usage) and maybe save battery for users.
Unfortunately I still didn't have time to do enough research, so for now it's just an idea or suggestion.
The text was updated successfully, but these errors were encountered: