Status Update
No update yet.
Comments
lb...@gmail.com
To show how needed this permission is, you can see how many apps and downloads for them are used for clipboard manager:
https://play.google.com/store/search?q=clipboard%20manager&c=apps
Removing the ability to monitor the clipboard in the background will ruin those and apps, the developers' jobs , and will cause users to be more frustrated over apps that used to work well and fit their needs.
Removing the ability to monitor the clipboard in the background will ruin those and apps, the developers' jobs , and will cause users to be more frustrated over apps that used to work well and fit their needs.
ad...@google.com
ad...@google.com
We have passed this to the development team and will update this issue with more information as it becomes available.
al...@gmail.com
The need to make clipboard access a permission was raised over a year ago with hundreds of people starring and commenting in agreement:
https://issuetracker.google.com/issues/123461156
Description
It is said:
"Unless your app is the default input method editor (IME) or is the app that currently has focus, your app cannot access clipboard data."
I suggest to have a new permission for accessing the clipboard in the background.
This is how it could work:
1. For backward compatibility and for maximum privacy handling, when any app that doesn't have the permission declared in the manifest (especially those that target old Android versions) tries to access the clipboard in the background, the OS could temporarily freeze this app, and ask the user if it's ok to grant it this permission.
2. For apps that can access the Android Q API , we could have a new permission that the app could request like any other special permission. It will also be able to check if the permission is granted, of course, to show the user an indication if it's working as expected or not.