Feature Request: Background-free option

[Civilian-No-001]

After using adb authorization, or after the phone restart, authorization is invalid, I cannot know the running status of scoop. And will scoop support Shizuku or wireless debugging? Thanks

[TacoTheDank]

After using adb authorization, or after the phone restart, authorization is invalid, I cannot know the running status of scoop.

Sorry, I don't quite understand what you mean. Could you clarify, please? Are you saying that you don't know whether Scoop is running when you boot up / restart your phone?

Will scoop support Shizuku

This isn't likely at the moment, unless someone would like to open a pull request to add Shizuku support and can verify that it works successfully. I lack the technical knowledge for adding Shizuku support; maintaining such support after it is added, however, wouldn't be very difficult.

or wireless debugging?

As far as I can tell from the official docs, nothing code-wise needs to be done as the ADB stuff itself is the same, just the mode of connection is different (Wi-Fi, as opposed to a cable). So I think it's safe to say that Scoop already does support wireless debugging.

Thanks for opening an issue! :)

[Civilian-No-001]

@TacoTheDank Sorry for not expressing clearly.

1. Scoop does not indicate the permission status of read logs. So it is impossible to know whether it is authorized in the application, need to go to other applications to check the authorization status. For example, FindMyDevice

2. There is no control option for the background of the program. Scoop needs to run in the background to capture the crashs, and have a informtion to keep-alive; now opening the main program will keep the background by default, and it is not possible to only view the history without turning on the monitoring. For example, GeometricWeather

So, I suggest adding two options in the setting, automatic startup(follow system start), start monitoring(follow program start) and an adb permission indicator(red/green).

Regarding wireless debugging, I mean turning on wireless debugging and pairing without connecting to the computer. I no longer request this feature because it will take up too much of your time and complicate the application. Now I use the app manager to authorize scoop and wait for the app manager to update the wireless debugging.

[TacoTheDank]

1. Scoop does not indicate the permission status of read logs. So it is impossible to know whether it is authorized in the application, need to go to other applications to check the authorization status.

Actually, Scoop does, although I suppose it's not very apparent. A different screen shows according to the status of READ_LOGS.

2. There is no control option for the background of the program. Scoop needs to run in the background to capture the crashs, and have a informtion to keep-alive; now opening the main program will keep the background by default, and it is not possible to only view the history without turning on the monitoring.

You can always just stop it from the notifications, though I suppose I could add a setting for this.

So, I suggest adding two options in the setting, automatic startup(follow system start)

An issue for this is already open here.

start monitoring(follow program start)

Not quite sure what you're referring to by this.

and an adb permission indicator(red/green).

Already exists, although I suppose I can make it more apparent.

Regarding wireless debugging, I mean turning on wireless debugging and pairing without connecting to the computer. I no longer request this feature because it will take up too much of your time and complicate the application. Now I use the app manager to authorize scoop and wait for the app manager to update the wireless debugging.

Unless I misunderstood, I've already stated that the app supports wireless debugging, as that is dealt with by the Android OS itself (at least according to the docs I can find), not by apps.

[Civilian-No-001]

Thank you

start monitoring(follow program start)

Not quite sure what you're referring to by this

I mean, opening scoop now automatically turns on monitoring for crashes, but sometimes I just want to turn on scoop to view past crashes, and I don’t need to turn on monitoring. You have already told me that I can turn off in the notification, and also consider adding option in the settings.

Regarding wireless debugging, I mean turning on wireless debugging and pairing without connecting to the computer. I no longer request this feature because it will take up too much of your time and complicate the application. Now I use the app manager to authorize scoop and wait for the app manager to update the wireless debugging.

Unless I misunderstood, I've already stated that the app supports wireless debugging, as that is dealt with by the Android OS itself (at least according to the docs I can find), not by apps.

Yes, wireless debugging is a system function. I don’t know how to express split screen operation, but you can try this Shizuku

Scoop is already perfect, and thanks for considering these features, I will close this issue later.

[TacoTheDank]

Let's leave this open for

Opening scoop now automatically turns on monitoring for crashes, but sometimes I just want to turn on scoop to view past crashes, and I don’t need to turn on monitoring.

I'll try to add this as a feature.

[Civilian-No-001]

Thanks

[TacoTheDank]

@Civilian-No-001 Scoop will now indicate the status of READ_LOGS in a setting https://github.com/TacoTheDank/Scoop/commit/86a3c7cd99bd337ff573ead8aa32c468afa4b56c