Using adb command to have access to clipboard in Android 10

[jshir8]

Clipboard pro is an Excellent application👍🏻 But I have one suggestion. Currently the app cannot have direct access to clipboard in Andriod 10, which is a little complicated. There is another application named Clip Stack. This app uses adb command to have access to the clipboard in Android 10. I suggest you also try this method. Thanks!

使用 FastHub 从我的 Mate 20 Pro 发送

[atrashler]

We are investigating this feature as an alternative working solution to bypass the restrictions of Android Q.

[GitAlexToTheGreek]

Hi,

Is this the reason that my copies in the Android app aren't being saved/recorded? (Tracking is enabled, ClipTo works correctly on Windows).

I'm familiar with the adb/clip stack workaround, and also request that it's an option here as well.

[atrashler]

Yes, it will be added after some investigation

[atrashler]

Hi,

Is this the reason that my copies in the Android app aren't being saved/recorded? (Tracking is enabled, ClipTo works correctly on Windows).

I'm familiar with the adb/clip stack workaround, and also request that it's an option here as well.

Yes. It is the reason. Now in the app we have implemented alternative solutions with global context action ‘Clipto...’ and action ‘Paste’ in the notification. After some research we will add some more convenient solution.

[atrashler]

@shihuajie1998 , @GitAlexToTheGreek and everyone who could help:

I have pre-releases new build with support of this feature. I need help to test it because on different custom shells of Android Q this behaviour can work or not (who know:).

Please check if it works on your devices and let me know here.

Here the build - https://github.com/clipto-pro/Android/releases/tag/v2.41.0

[GitAlexToTheGreek]

@shihuajie1998 , @GitAlexToTheGreek and everyone who could help:

I have pre-releases new build with support of this feature. I need help to test it because on different custom shells of Android Q this behaviour can work or not (who know:).

Please check if it works on your devices and let me know here.

Here the build - https://github.com/clipto-pro/Android/releases/tag/v2.41.0

Hi Alex,

Thanks for your efforts...

Here's what I get when submitting the command...

[d0x360]

Works on my note 10+ running Android 10 with Feb update.

[GitAlexToTheGreek]

Works on my note 10+ running Android 10 with Feb update.

My phone's updated to the latest available and its only the December patch so maybe that's a factor?

[atrashler]

@shihuajie1998 , @GitAlexToTheGreek and everyone who could help: I have pre-releases new build with support of this feature. I need help to test it because on different custom shells of Android Q this behaviour can work or not (who know:). Please check if it works on your devices and let me know here. Here the build - https://github.com/clipto-pro/Android/releases/tag/v2.41.0

Hi Alex,

Thanks for your efforts...

Here's what I get when submitting the command...

Could you try to run this commands one-by-one? Each line in the instruction is a separate command, so be careful and run each line independently.

[jshir8]

@atrashler I tried and it worked properly. Thanks a lot for the efforts!

[GitAlexToTheGreek]

Could you try to run this commands one-by-one? Each line in the instruction is a separate command, so be careful and run each line independently.

Oh!

So don't copy/paste the entire...

"adb -d shell pm grant com.wb.clipboard.pro android.permission.READ_LOGS; adb -d shell appops set com.wb.clipboard.pro SYSTEM_ALERT_WINDOW allow; adb -d shell am force-stop com.wb.clipboard.pro;"

...as one command? Got it. I'll update soon...

[GitAlexToTheGreek]

😐 Update:

[atrashler]

Could you try to run this commands one-by-one? Each line in the instruction is a separate command, so be careful and run each line independently.

Oh!

So don't copy/paste the entire...

"adb -d shell pm grant com.wb.clipboard.pro android.permission.READ_LOGS; adb -d shell appops set com.wb.clipboard.pro SYSTEM_ALERT_WINDOW allow; adb -d shell am force-stop com.wb.clipboard.pro;"

...as one command? Got it. I'll update soon...

No. Three commands:

1) adb -d shell pm grant com.wb.clipboard.pro android.permission.READ_LOGS

2) adb -d shell appops set com.wb.clipboard.pro SYSTEM_ALERT_WINDOW allow

3) adb -d shell am force-stop com.wb.clipboard.pro

[GitAlexToTheGreek]

Could you try to run this commands one-by-one? Each line in the instruction is a separate command, so be careful and run each line independently.

Oh! So don't copy/paste the entire... "adb -d shell pm grant com.wb.clipboard.pro android.permission.READ_LOGS; adb -d shell appops set com.wb.clipboard.pro SYSTEM_ALERT_WINDOW allow; adb -d shell am force-stop com.wb.clipboard.pro;" ...as one command? Got it. I'll update soon...

No. Three commands:

1. adb -d shell pm grant com.wb.clipboard.pro android.permission.READ_LOGS
2. adb -d shell appops set com.wb.clipboard.pro SYSTEM_ALERT_WINDOW allow
3. adb -d shell am force-stop com.wb.clipboard.pro

And press enter after each command, correct?

Doing so lead to these errors:

(Plus the 3rd command doesn't even initiate a response).

[atrashler]

Could you try to run this commands one-by-one? Each line in the instruction is a separate command, so be careful and run each line independently.

Oh! So don't copy/paste the entire... "adb -d shell pm grant com.wb.clipboard.pro android.permission.READ_LOGS; adb -d shell appops set com.wb.clipboard.pro SYSTEM_ALERT_WINDOW allow; adb -d shell am force-stop com.wb.clipboard.pro;" ...as one command? Got it. I'll update soon...

No. Three commands:

1. adb -d shell pm grant com.wb.clipboard.pro android.permission.READ_LOGS
2. adb -d shell appops set com.wb.clipboard.pro SYSTEM_ALERT_WINDOW allow
3. adb -d shell am force-stop com.wb.clipboard.pro

And press enter after each command, correct?

Doing so lead to these errors:

(Plus the 3rd command doesn't even initiate a response).

Almost correctly:) 1) Could you try to input the first command manually (now it seems like you copy it and the copied string contains ‘new line’ symbol

2) and the second one

3) the third one is correct. all commands should not inform you with any message

[GitAlexToTheGreek]

Working 😀👍👌

[atrashler]

Great! Marked as closed. Thanks!

[GitAlexToTheGreek]

Uh oh 🙁

So my keyboards started going haywire earlier...

Imgur

The only (temporary) solution was to restart the phone, at which point the keyboard would return to normal, for a few minutes or so, and then back to the bug.

I went to Running Services and started force-stopping various apps, all of which didn't affect the bug, until I stopped ClipTo.

I then uninstalled it and the bug hasn't returned since. Could it be a coincidence? Does it make any logical sense that updating a clipboard manager would impact keyboard stability?

Anyway, I'm wondering if you can make sense of this and hopefully get CT working normally again.

[atrashler]

Uh oh 🙁

So my keyboards started going haywire earlier...

Imgur

The only (temporary) solution was to restart the phone, at which point the keyboard would return to normal, for a few minutes or so, and then back to the bug.

I went to Running Services and started force-stopping various apps, all of which didn't affect the bug, until I stopped ClipTo.

I then uninstalled it and the bug hasn't returned since. Could it be a coincidence? Does it make any logical sense that updating a clipboard manager would impact keyboard stability?

Anyway, I'm wondering if you can make sense of this and hopefully get CT working normally again.

Please install the latest version from Google Play (2.41.2). Have solved several related issues in it. If the problem will not gone - let me know so I can investigate it. Thanks!

[atrashler]

Uh oh 🙁

So my keyboards started going haywire earlier...

Imgur

The only (temporary) solution was to restart the phone, at which point the keyboard would return to normal, for a few minutes or so, and then back to the bug.

I went to Running Services and started force-stopping various apps, all of which didn't affect the bug, until I stopped ClipTo.

I then uninstalled it and the bug hasn't returned since. Could it be a coincidence? Does it make any logical sense that updating a clipboard manager would impact keyboard stability?

Anyway, I'm wondering if you can make sense of this and hopefully get CT working normally again.

Have checked on the latest version (2.41.2). The issue is reproducible if you click on any action in the notification area. Will fix it ASAP.

Thanks!

[atrashler]

Uh oh 🙁

So my keyboards started going haywire earlier...

Imgur

The only (temporary) solution was to restart the phone, at which point the keyboard would return to normal, for a few minutes or so, and then back to the bug.

I went to Running Services and started force-stopping various apps, all of which didn't affect the bug, until I stopped ClipTo.

I then uninstalled it and the bug hasn't returned since. Could it be a coincidence? Does it make any logical sense that updating a clipboard manager would impact keyboard stability?

Anyway, I'm wondering if you can make sense of this and hopefully get CT working normally again.

Could you please check this build (https://github.com/clipto-pro/Android/releases/tag/v2.41.3). It should work now. Thanks!

[GitAlexToTheGreek]

😉

On Sun, Feb 23, 2020, 11:00 AM Alex Trashler notifications@github.com wrote:

Uh oh 🙁

So my keyboards started going haywire earlier...

Imgur https://i.imgur.com/XjFWP4e.mp4

The only (temporary) solution was to restart the phone, at which point the keyboard would return to normal, for a few minutes or so, and then back to the bug.

I went to Running Services and started force-stopping various apps, all of which didn't affect the bug, until I stopped ClipTo.

I then uninstalled it and the bug hasn't returned since. Could it be a coincidence? Does it make any logical sense that updating a clipboard manager would impact keyboard stability?

Anyway, I'm wondering if you can make sense of this and hopefully get CT working normally again.

Have checked on the latest version (2.41.2). The issue is reproducible if you click on any action in the notification area. Will fix it ASAP.

Thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/clipto-pro/Android/issues/11?email_source=notifications&email_token=AOIEUYMBY52WU3QRUGUNP53RELBVDA5CNFSM4JXWLXTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMWEKOY#issuecomment-590103867, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOIEUYNLBNODZZ2CZZMLANTRELBVDANCNFSM4JXWLXTA .

[d0x360]

Works on my note 10+ running Android 10 with Feb update.

My phone's updated to the latest available and its only the December patch so maybe that's a factor?

That's possible. The Feb update on my note 10+ said there were bug fixes as well but it didn't specify if they were fixes by Google and part of AOSP or custom fixes by Samsung.

[atrashler]

Works on my note 10+ running Android 10 with Feb update.

My phone's updated to the latest available and its only the December patch so maybe that's a factor?

That's possible. The Feb update on my note 10+ said there were bug fixes as well but it didn't specify if they were fixes by Google and part of AOSP or custom fixes by Samsung.

Technical implementation uses core android functionality that should work in the same way on all devices. Now the only problem could be is in my implementation of this logic with some not critical changes for every specific platform. @GitAlexToTheGreek has found some issue in the version 2.41.2. That is why in Beta-channel I have published yet another build (2.41.3) that should work correctly on all devices.

[d0x360]

It's the beta build that I'm using so that must be it.

On Mon, Feb 24, 2020, 5:00 PM Alex Trashler notifications@github.com wrote:

Works on my note 10+ running Android 10 with Feb update.

My phone's updated to the latest available and its only the December patch so maybe that's a factor?

That's possible. The Feb update on my note 10+ said there were bug fixes as well but it didn't specify if they were fixes by Google and part of AOSP or custom fixes by Samsung.

Technical implementation uses core android functionality that should work in the same way on all devices. Now the only problem could me in the my implementation of this logic with some not critical changes for every specific platform. @GitAlexToTheGreek https://github.com/GitAlexToTheGreek has found some issue in the version 2.41.2. That is why in Beta-channel I have published yet another build (2.41.3) that should work correctly on all devices.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/clipto-pro/Android/issues/11?email_source=notifications&email_token=ADLH3GI3GKHKZ4ZWKNLIYQTREQ7OFA5CNFSM4JXWLXTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMZWHJY#issuecomment-590570407, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADLH3GL22KXHDUB2V5J5WELREQ7OFANCNFSM4JXWLXTA .

[GitAlexToTheGreek]

Technical implementation uses core android functionality that should work in the same way on all devices. Now the only problem could be is in my implementation of this logic with some not critical changes for every specific platform. @GitAlexToTheGreek has found some issue in the version 2.41.2. That is why in Beta-channel I have published yet another build (2.41.3) that should work correctly on all devices.

Ok...

1) Running v2.41.3

2) Adb commands worked again and normal copying function working 😎😎😎

3) Will report back after an extended time using the device, hopefully all goes well 🤞

[GitAlexToTheGreek]

1) So far so good! 😀

2) Hey Alex is there a way to search for and remove 'duplicates'?

And/or perhaps a method to prevent CT from creating a new entry if it recognizes the copied text is identical to a previous copy in a future release?

[sirius16]

Yes, hi, is anyone else having the problem of their keyboard disappearing altogether under the 2.41.3 version with the adb unlock? The keyboard for mine straight up disappears and it's almost like it's being suppressed because it's not until I kill the app that I get my keyboard back.

Addenum: I did manage to somehow fix the permanently suppressed keyboard problem, so now all that remains is the original problem of the repeatedly collapsing keyboard (not my phone, but it's the exact same phenomenon)

But the clipboard monitoring and copying still works, just the keyboard is the issue now

[GitAlexToTheGreek]

Hi Sirius 🙂

Strange that 2.41.2 caused the keyboard shenanigans on my phone and everything's now working with .3 and it's the other way around on your side 🤔

Which device and OS release are you using? (Wish I could be more helpful.)

[atrashler]

Yes, hi, is anyone else having the problem of their keyboard disappearing altogether under the 2.41.3 version with the adb unlock? The keyboard for mine straight up disappears and it's almost like it's being suppressed because it's not until I kill the app that I get my keyboard back.

Addenum: I did manage to somehow fix the permanently suppressed keyboard problem, so now all that remains is the original problem of the repeatedly collapsing keyboard (not my phone, but it's the exact same phenomenon)

But the clipboard monitoring and copying still works, just the keyboard is the issue now

Are you sure that you are using the version 2.41.3 ? Because this issue should be prior this version.

[sirius16]

Yes, hi, is anyone else having the problem of their keyboard disappearing altogether under the 2.41.3 version with the adb unlock? The keyboard for mine straight up disappears and it's almost like it's being suppressed because it's not until I kill the app that I get my keyboard back. Addenum: I did manage to somehow fix the permanently suppressed keyboard problem, so now all that remains is the original problem of the repeatedly collapsing keyboard (not my phone, but it's the exact same phenomenon) But the clipboard monitoring and copying still works, just the keyboard is the issue now

Are you sure that you are using the version 2.41.3 ? Because this issue should be prior this version.

I'm sure, yeah Although, if other people don't seem to be having this problem it might be my phone but I have no idea what would cause that

[atrashler]

Yes, hi, is anyone else having the problem of their keyboard disappearing altogether under the 2.41.3 version with the adb unlock? The keyboard for mine straight up disappears and it's almost like it's being suppressed because it's not until I kill the app that I get my keyboard back. Addenum: I did manage to somehow fix the permanently suppressed keyboard problem, so now all that remains is the original problem of the repeatedly collapsing keyboard (not my phone, but it's the exact same phenomenon) But the clipboard monitoring and copying still works, just the keyboard is the issue now

Are you sure that you are using the version 2.41.3 ? Because this issue should be prior this version.

I'm sure, yeah Although, if other people don't seem to be having this problem it might be my phone but I have no idea what would cause that

Will check it. Now I know only about the problem on OnePlus devices. Could you please write your phone info?

[sirius16]

Yes, hi, is anyone else having the problem of their keyboard disappearing altogether under the 2.41.3 version with the adb unlock? The keyboard for mine straight up disappears and it's almost like it's being suppressed because it's not until I kill the app that I get my keyboard back. Addenum: I did manage to somehow fix the permanently suppressed keyboard problem, so now all that remains is the original problem of the repeatedly collapsing keyboard (not my phone, but it's the exact same phenomenon) But the clipboard monitoring and copying still works, just the keyboard is the issue now

Are you sure that you are using the version 2.41.3 ? Because this issue should be prior this version.

I'm sure, yeah Although, if other people don't seem to be having this problem it might be my phone but I have no idea what would cause that

Will check it. Now I know only about the problem on OnePlus devices. Could you please write your phone info?

Yeah, it's a OnePlus 7T Pro 5G McLaren with Android 10 (January 2020 update). Any other info you need?

[atrashler]

No. It’s enough:) Thanks!

[GitAlexToTheGreek]

...it's a OnePlus 7T Pro 5G McLaren with Android 10 (January 2020 update)...

Assuming you're in the US with a T-Mobile device? I've only been able to update to the Dec patch...

...wondering if TM os updates differ based on region? Can you share which part of the country you're in, Sirius? (going to inquire with T-Mobile chat support)

[GitAlexToTheGreek]

Also Sirius, can you remember approximately when you received that January patch update?

[sirius16]

Sorry, it was the December patch, not January. I read something wrong

I'm in the America, the Mid-Atlantic

[d0x360]

Patches can differ slightly by region but they generally are identical when it comes to Android itself. It's usually things like apps that might get added in one region but not another so it shouldn't be an issue.

You can disable (really disable and often delete) these apps through ADB. Just Google the commands.

Samsung phones have massive amounts of bloat and almost all phones have a service called DMAT which is basically spyware. I always remove that and on a Samsung device I get rid of roughly 100 apps and services. It's insane.

On Thu, Feb 27, 2020, 9:44 PM GitAlexToTheGreek notifications@github.com wrote:

...it's a OnePlus 7T Pro 5G McLaren with Android 10 (January 2020 update)...

Assuming you're in the US with a T-Mobile device? I've only been able to update to the Dec patch...

[image: Screenshot_20200227-183839] https://user-images.githubusercontent.com/59787873/75505690-c7c59980-5990-11ea-8e84-958065226e65.jpg ...wondering if TM os updates differ based on region? Can you share which part of the country you're in, Sirius? (going to inquire with T-Mobile chat support)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/clipto-pro/Android/issues/11?email_source=notifications&email_token=ADLH3GIKTJKO5S6XYOXJSC3RFB27JA5CNFSM4JXWLXTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENGYPRQ#issuecomment-592283590, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADLH3GLM6IR6EAAXNVOBINLRFB27JANCNFSM4JXWLXTA .

[atrashler]

@GitAlexToTheGreek @d0x360 @sirius16 could you please check the new release how it works on your devices (have added possible fix of the problem with OnePlus devices but need to be checked)

Here the latest build: https://github.com/clipto-pro/Android/releases/tag/v2.42.0

Thanks in advance!

[GitAlexToTheGreek]

1) "Sorry, it was the December patch, not January. I read something wrong"

Ah, no worries 😉

T-Mobile actually did something unprecedented the other day and did an Ota with the current security patch. That's never happened in nearly 10 years of using them as my carrier 🎉

2) Thanks for the feedback d0x360 🙂

"You can disable (really disable and often delete) these apps through Adb"

-> Can you clarify which apps you're referring to?

3) @atrashler, will do 😉 Thanks as always for your efforts.

Btw, any consideration given to a previous question above..."is there a way to search for and remove 'duplicates'?

And/or perhaps a method to prevent CT from creating a new entry if it recognizes the copied text is identical to a previous copy in a future release?"

[atrashler]

"Sorry, it was the December patch, not January. I read something wrong"

Ah, no worries 😉

T-Mobile actually did something unprecedented the other day and did an Ota with the current security patch. That's never happened in nearly 10 years of using them as my carrier 🎉

Thanks for the feedback d0x360 🙂

"You can disable (really disable and often delete) these apps through Adb"

-> Can you clarify which apps you're referring to?

@atrashler, will do 😉 Thanks as always for your efforts.

Btw, any consideration given to a previous question above..."is there a way to search for and remove 'duplicates'?

And/or perhaps a method to prevent CT from creating a new entry if it recognizes the copied text is identical to a previous copy in a future release?"

The app should not create duplicates by default. If you are trying to create some existing note than the app should merge the attributes of the new one (tags and title) with the existing one. If you import notes than the app will not import notes that already exists. So it should not be possible to create duplicates. Could you send some examples if you have duplicates?

[sirius16]

@GitAlexToTheGreek @d0x360 @sirius16 could you please check the new release how it works on your devices (have added possible fix of the problem with OnePlus devices but need to be checked)

Here the latest build: https://github.com/clipto-pro/Android/releases/tag/v2.42.0

Thanks in advance!

So far, so good!!! I can copy without the keyboard doing the weird rapid collapse and/or straight disappearing. I'll keep using it and let know if I find anything, but so far, so good!!! Really, thanks a lot (now if I could only figure out how to pin the notification to the top… or a floating bubble)

[GitAlexToTheGreek]

Could you send some examples if you have duplicates?

Some previous examples:

To be fair though, I've tried copying and recopying this again and again...

2.42.2-release (2420200)

And it's not making any extra copies. So maybe it's fixed? (using 2.42.2).

Also good to hear that it doesn't create extra copies when importing. 😎

[atrashler]

Could you send some examples if you have duplicates?

Some previous examples:

To be fair though, I've tried copying and recopying this again and again...

2.42.2-release (2420200)

And it's not making any extra copies. So maybe it's fixed? (using 2.42.2).

Also good to hear that it doesn't create extra copies when importing. 😎

Strange behaviour. It should not happen. But it is possible if you have used one of Beta-versions of the app:) Anyway the core logic of the app - no duplicates. No matter you import your notes from several different backups with possible duplicates or you create notes manually - the app always checks for possible duplicates and does not let to create the same note twice.

[atrashler]

Have published new release with bugfix (https://github.com/clipto-pro/Android/releases/tag/v.2.42.4).

In few hours the same build will be available in Beta channel on Google Play.

[GitAlexToTheGreek]

Hi Alex,

More peculiar behavior to report:

-> Copies aren't always reflected in CT in real time (instantaneously).

And it's unclear if my method to 'wake it up' is just a remarkable coincidence or if it's the thing that's actually causing it to activate again...

Example:

I made a copy at 2:20pm...

...and for a brief period of time, CT was not updating with the same copy. Even after force-stopping, clearing cache, etc.

Last time this happened, I opened Clip Stack, which I keep enabled as a backup and indeed the 2:20pm copy was present (as shown above).

I then go back to CT, and there it is!

It should be noted that once CT displayed the copy, it did correctly show the original time stamp (2:20) instead of the time that it started displaying entries again (a minute or two afterwards). So does that imply that CT was still sniffing in real time just not displaying in real time (for whatever reason)?

Btw, CS doesn't copy each time either, and that's the whole reason I looked for an alternative from CS in the 1st place. Furthermore, even after waiting and/or tinkering with the app, it still doesn't display the missing copy/ies the way CT appears to, they're just unaccounted for.

Obviously I can't say for sure there's a correlation between the two apps, nor can I explain why CT stops displaying copies in real time...wondering if you have any suggestions?

(On version 2.42.4-release, although I just noticed the update to .5 - I'll update the app and update in this thread if I notice the behavior start up again or not).

[atrashler]

If Clipto is activated via adb it should monitor and take notes from every update in the clipboard. If it is not so please send me scenario.

But be aware not to use Clipto and Clip Stack at the same time. Both apps use the same source of knowledge about changes in the clipboard and it is possible that Clip Stack ‘clears’ this source every time it is acknowledged about the next change. I can not check it but it is possible and it is better not to use the similar working apps together. Try to check if the behaviour is not correct when only Clipto is running.

[GitAlexToTheGreek]

Would keeping it installed but turning off the "listening" function be sufficient...

...or best to uninstall it altogether?

[atrashler]

Just make sure that it is not running.

[dijiugeweiba]

when I run the first adb command on windows10, it shows below, how can I solve this problem? `platform-tools_r29.0.6-windows\platform-tools>adb -d shell pm grant com.wb.clipboard.pro android.permission.READ_LOGS Security exception: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.

java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS. at android.app.ContextImpl.enforce(ContextImpl.java:1951) at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1979) at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:2153) at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:130) at com.android.server.pm.permission.PermissionManagerService$PermissionManagerServiceInternalImpl.grantRuntimePermission(PermissionManagerService.java:3190) at com.android.server.pm.PackageManagerService.grantRuntimePermission(PackageManagerService.java:6590) at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:2015) at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:234) at android.os.ShellCommand.exec(ShellCommand.java:104) at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:23868) at android.os.Binder.shellCommand(Binder.java:881) at android.os.Binder.onTransact(Binder.java:765) at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:5100) at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4763) at com.android.server.pm.OppoPackageManagerService.onTransact(OppoPackageManagerService.java:83) at android.os.Binder.execTransactInternal(Binder.java:1021) at android.os.Binder.execTransact(Binder.java:994)`