seamless permissions [Feature Request]

[applesoff]

With integration of shizuku, is it possible to have the app run the terminal commands to add these permissions without the need for a third party app or pc?

[Sathvik-Rao]

Hi @applesoff,

I will look into integrating Shizuku into the ClipCascade Android app. I want to note here that once the commands are executed in the terminal, they remain valid until the app is uninstalled. Tested on Android 14, the app will not lose permissions when updated or restarted, only when uninstalled. To install an updated version of the app, avoid uninstalling the old version; it will automatically override the existing installation.

[applesoff]

I guess I have more issues with the app staying connected too. After a few days it seems like the app stops persisting and need to be reopened and connected.

Additionally, when copying passwords the app opens in the background and inserts itself into the recently used apps, is there a way to make it not show up in recent app switcher if it's just from a copy action?

[Sathvik-Rao]

Hi @applesoff, are you using the latest version of the app and server? I’ll try to implement a feature to remove the app from recents when copying in an upcoming release.

[Sathvik-Rao]

Hi @applesoff

New Release

With integration of shizuku, is it possible to have the app run the terminal commands to add these permissions without the need for a third party app or pc?

The app is a combination of Kotlin and React Native, and integrating Shizuku would require considerable effort. The adb permissions only need to be granted once and will persist until the app is uninstalled. Moreover, app updates will not revoke these permissions.

---

I guess I have more issues with the app staying connected too. After a few days it seems like the app stops persisting and need to be reopened and connected.

The foreground service is generally terminated only during system restarts or under battery stress. Restarts can happen automatically or randomly during inactivity or at night. Occasionally, Android may also terminate foreground services under low battery conditions. While these situations are not major issues, Android does impose restrictions that prevent an app from starting a foreground service directly from the background. Apps can only perform tasks like data processing or displaying notifications in such cases. However, some exceptions exist, such as during system restarts.

With the latest release, the app automatically starts the service after a system reboot. However, do not enable this feature if you're using the ADB workaround, as clicking "Start" will trigger a popup requesting permission to READ_LOGS. When the service starts automatically after a restart, this popup is bypassed, and automatic background monitoring will not function.

To mitigate this, the app checks every 15 minutes to ensure the foreground service is running. If it detects that the service has been terminated, it sends a notification. Even if you accidentally clear the notification, it will reappear until the app is re-opened, or you can click the notification to auto-start the service.

---

Additionally, when copying passwords the app opens in the background and inserts itself into the recently used apps, is there a way to make it not show up in recent app switcher if it's just from a copy action?

The app has been updated to exclude itself from the recent apps list when copying text.