Will it be possible to make the app of Native Clipboard Manager work on Android Q well?

[AndroidDeveloperLB]

For now, I've found out that it's possible to get the clipboard data in the background, but only if the app is in the foreground with an on-top view .
Example here . Un-comment the part in the onStartCommand function, and you will see it will write to the log each time something gets copied, even if you leave the app.

But, what I miss on your app is to paste the clipboard data, which doesn't work and I don't know how it is working in code.

I know that clipboard apps got to be much worse on Android Q (here), but maybe there is still a way around it?

[Fabian42]

There is a "Clipboard whitelist" Magisk module that fixes this issue.

[AndroidDeveloperLB]

Is the app "Native Clipboard Manager" available somewhere with its code?

[Fabian42]

That is this repository, but it is outdated. I restored a newer version from a backup, there are also various websites that have it, no idea how trustworthy they are.
If you meant "Clipboard wishlist", then yes, here: https://github.com/Kr328/Riru-ClipboardWhitelist

[AndroidDeveloperLB]

No, I mean this app:

https://play.google.com/store/apps/details?id=com.dhm47.nativeclipboard

https://apkpure.net/native-clipboard-manager/com.dhm47.nativeclipboard

https://www.apkmirror.com/apk/dhm47/native-clipboard/

It uses accessibility to allow to past clipboard history easily.

[Fabian42]

That is exactly where you are already commenting, it is this repository right here.

[AndroidDeveloperLB]

That can't be correct, because if you download it, and search for "AccessibilityService", you won't find even one file with it.
There are also no configurations that are set for it to work, and it never used Magisk at all. Worked without root.

Also the dates don't seem correct.

[Fabian42]

Maybe that is caused by the old state, no idea. But the developer name matches.

[AndroidDeveloperLB]

Old state? What do you mean?
Only thing that seems to match is the package name.
The version is different. On Play Store, it's 4.8.1, and here it's 3.3.
I can't even find 3.3 on the history.

Ever since I've tried it, it always had accessibility and didn't require Exposed, or root, or Magisk or anything special.

[Fabian42]

So you mean this cannot be the same developer? That is very weird. I would suggest contacting one of them, but I think both projects are abandoned.

[AndroidDeveloperLB]

I thought I'm doing it here...
Also pretty sure I tried via email.
I tried now again.

[tp0]

This is the correct repo but it is just outdated and apparently was abandoned even before the dev stopped development (hence newer versions on Play Store).

[AndroidDeveloperLB]

Too bad