I would like to use Quicksupport (Teamviewer) to control my device remotely. But I can' get it to work. If I try to connect with my computer there is a popup that asks for "special permisson" and when I tap the button to go there, nothing happens.
With my Lenovo Tab4 I don't have this problem, the app only asked for a special addon.
Does anybody have got this to work??
When running
Code:
adb shell dumpsys package com.teamviewer.quicksupport.market
I get below list.(# is my symbol to verify requested vs granted)
Code:
requested permissions:
#android.permission.VIBRATE
android.permission.SYSTEM_ALERT_WINDOW
#android.permission.REQUEST_DELETE_PACKAGES
android.permission.REQUEST_INSTALL_PACKAGES
android.permission.INJECT_EVENTS
android.permission.CAPTURE_SECURE_VIDEO_OUTPUT
android.permission.CAPTURE_VIDEO_OUTPUT
#com.teamviewer.incomingremotecontrolsamsunglib.SAMSUNG_SUPPORT_PERMISSION
com.samsung.android.knox.permission.KNOX_REMOTE_CONTROL
com.sonymobile.permission.ENTERPRISE_API
com.android.remotecontrolservice.REMOTE_CONTROL
#android.permission.ACCESS_WIFI_STATE
#android.permission.CHANGE_WIFI_STATE
#android.permission.FOREGROUND_SERVICE
#android.permission.BLUETOOTH
#android.permission.GET_PACKAGE_SIZE
#android.permission.KILL_BACKGROUND_PROCESSES
android.permission.ACCESS_FINE_LOCATION
#android.permission.READ_EXTERNAL_STORAGE
#android.permission.WRITE_EXTERNAL_STORAGE
#android.permission.INTERNET
#android.permission.WAKE_LOCK
#android.permission.ACCESS_NETWORK_STATE
install permissions:
android.permission.FOREGROUND_SERVICE: granted=true
android.permission.BLUETOOTH: granted=true
android.permission.INTERNET: granted=true
android.permission.GET_PACKAGE_SIZE: granted=true
android.permission.CHANGE_WIFI_STATE: granted=true
android.permission.ACCESS_NETWORK_STATE: granted=true
com.teamviewer.incomingremotecontrolsamsunglib.SAMSUNG_SUPPORT_PERMISSION: granted=true
android.permission.KILL_BACKGROUND_PROCESSES: granted=true
android.permission.REQUEST_DELETE_PACKAGES: granted=true
android.permission.VIBRATE: granted=true
android.permission.ACCESS_WIFI_STATE: granted=true
android.permission.WAKE_LOCK: granted=true
runtime permissions:
android.permission.READ_EXTERNAL_STORAGE: granted=true
android.permission.WRITE_EXTERNAL_STORAGE: granted=true
I noticed not all permissions were granted (those without #) but that's what the plugin does I believe. Anyways I was able to grant access to some of them ('adb shell pm grant com.teamviewer.quicksupport.market <permissionname>') but 4 - got error 'is not changable permission type'
Code:
android.permission.REQUEST_INSTALL_PACKAGES
android.permission.INJECT_EVENTS
android.permission.CAPTURE_SECURE_VIDEO_OUTPUT
android.permission.CAPTURE_VIDEO_OUTPUT
and another two are not there (checked with 'adb shell pm list permissions')
Code:
com.sonymobile.permission.ENTERPRISE_API
com.android.remotecontrolservice.REMOTE_CONTROL
Maybe someone with root can try granting those 4 access and checking for those missing 2. My phone is not rooted so I can't
Related
Hello,
Im using MIUI 10 android 9 non rooted.
When i want activate agressive doze via adb [ adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS ], i get this error message:
D:\ANDROID\TOOLS\ADB-FASTBOOT>adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS
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:1822)
at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1850)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1391)
at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:89)
at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.grantRuntimePermission(PermissionManagerService.java:2118)
at com.android.server.pm.PackageManagerService.grantRuntimePermission(PackageManagerService.java:5604)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:1730)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:217)
at android.os.ShellCommand.exec(ShellCommand.java:103)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:21860)
at android.os.Binder.shellCommand(Binder.java:629)
at android.os.Binder.onTransact(Binder.java:527)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2809)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4014)
at android.os.Binder.execTransact(Binder.java:728)
D:\ANDROID\TOOLS\ADB-FASTBOOT>
I read tutorial here https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
Any help would be appreciated
exodius48 said:
Hello,
Im using MIUI 10 android 9 non rooted.
When i want activate agressive doze via adb [ adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS ], i get this error message:
D:\ANDROID\TOOLS\ADB-FASTBOOT>adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS
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:1822)
at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1850)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1391)
at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:89)
at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.grantRuntimePermission(PermissionManagerService.java:2118)
at com.android.server.pm.PackageManagerService.grantRuntimePermission(PackageManagerService.java:5604)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:1730)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:217)
at android.os.ShellCommand.exec(ShellCommand.java:103)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:21860)
at android.os.Binder.shellCommand(Binder.java:629)
at android.os.Binder.onTransact(Binder.java:527)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2809)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4014)
at android.os.Binder.execTransact(Binder.java:728)
D:\ANDROID\TOOLS\ADB-FASTBOOT>
I read tutorial here https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
Any help would be appreciated
Click to expand...
Click to collapse
Most likely your ROM is incompatible. If you are keen on Greenify, switch to a custom ROM and check.
tnsmani said:
Most likely your ROM is incompatible. If you are keen on Greenify, switch to a custom ROM and check.
Click to expand...
Click to collapse
Custom rom? So i need to unlock bootloader my device , install twrp etc etc.? OK thanks.
I dont want to do it, so better to uninstall greenify.
exodius48 said:
Custom rom? So i need to unlock bootloader my device , install twrp etc etc.? OK thanks.
I dont want to do it, so better to uninstall greenify.
Click to expand...
Click to collapse
Good plan. Greenify really isn't needed on your device/rom.
When you run ADB on the computer make sure the CMD (the black window) is running As Administrator.
It really is worth it to run these ADB commands on a Non-Rooted device, Greenify works great.
I have an OPPO K5 - China domestic version. When I tried to grant permission to GSAM I also had the same long error message. Then I discovered further down the Developer Options menu, there's a tab called "Disable Permission Monitoring", I switched it on and the adb command worked without the long error message. Not sure if MIUI has a similar tab though.
exodius48 said:
I read tutorial here https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
Click to expand...
Click to collapse
Hi.
Link is broken. Any tutorial copy to post here?
Regards.
I have an Android(7) phone and a Linux pc. By enabling USB debugging and using the terminal of my pc, I am able to read the notifications of my phone using the command:
Code:
adb shell dumpsys notification --noredact
Now, there are some notifications in android in which we can interact with the app directly from the notification. For example, in a Whatsapp notification, there are usually two buttons: Reply & Mark as read. In YouTube, there are options like Play, Turn off, Watch later. In the output of the above command, these options are visible in the following form:
actions={
[0] "Reply" -> PendingIntent{6becf48: PendingIntentRecord{87b8050 com.whatsapp startService (whitelist: +30s0ms)}}
[1] "Mark as read" -> PendingIntent{c1661e1: PendingIntentRecord{b8e3249 com.whatsapp startService (whitelist: +30s0ms)}}
}
Click to expand...
Click to collapse
I have two questions:
Can we interact with these options from adb shell? For example, is there any command like
Code:
adb shell <SOME COMMAND> 'Message to be sent in whatsapp with reply option'
which will send the text as a reply in whatsapp without opening the app?
Is it possible to swipe the notifications using any adb command? (Not the
Code:
adb shell input swipe x0 y0 x1 y1
, it requires to unlock the phone each time)
Some comments:
Here is what I found that may be relevant to this question.
I think that I have to somehow launch the specific intent linked to the mentioned PendingIntent id (in this case 6becf48 or 87b8050)
Using the command
Code:
adb shell dumpsys activity intents > output.txt
and then searching for 87b8050 in output.txt, I found the name of the intent. It was as follows:
* PendingIntentRecord{87b8050 com.whatsapp startService (whitelist: +30s0ms)}
uid=10104 packageName=com.whatsapp type=startService flags=0x0
requestIntent=act=com.whatsapp.intent.action.DIRECT_REPLY_FROM_MESSAGE dat=content://com.whatsapp.provider.contact/contacts/2256 cmp=com.whatsapp/.notification.DirectReplyService (has extras)
whitelistDuration=+30s0ms
Click to expand...
Click to collapse
Now I think that it may be possible to launch the intent
Code:
com.whatsapp.intent.action.DIRECT_REPLY_FROM_MESSAGE
using adb shell am command, and passing the intent id and message as some parameters.
(Just like we can launch Whatsapp from adb with am command, it should be possible to launch the pendingIntent also.)
I'm searching for something similar.. Did you figure this out or still exploring?
bump !
I'm trying to enable certain features of my custom app that require "dangerous" permissions. Is it possible to force the permissions instead of asking the user for the permissions? We are selling a prepackaged device and don't want to force the users to have to accept the permissions manually. Anything is in the realm of access; the devices are rooted and using adb, side loaded apps, etc are all acceptable solutions.
root permission is the ultimate permission as far as I know.
kouseralamin said:
root permission is the ultimate permission as far as I know.
Click to expand...
Click to collapse
The device is rooted, but the application is not running as "root".
bennycatalyst said:
I'm trying to enable certain features of my custom app that require "dangerous" permissions. Is it possible to force the permissions instead of asking the user for the permissions? We are selling a prepackaged device and don't want to force the users to have to accept the permissions manually. Anything is in the realm of access; the devices are rooted and using adb, side loaded apps, etc are all acceptable solutions.
Click to expand...
Click to collapse
Typically an app will send a notification to ask for permission to use features on user's phone, which user can Allow or Deny. And that for good reason. . Wondering why you want to bypass this mechanism?
From the user's point of view there are the following high risk ( dangerous ) permissions:
Make phone calls
Send SMS or MMS
Read sensitive logs
Display system-level alerts
Kill background processes
Process outgoing calls
Write secure settings
Authenticate Accounts
Read email attachments
Add system service
Read instant messages (IM)
Full list of permissons here.
An app's permissions must be defined in app's Manifest.xml. Only optional permissions the app has declared can be granted and/or revoked. If Android is rooted then granting and/ or revoking an app's optional permissions is done by PM.
ADB Examples:
Code:
adb devices
adb shell "su -c 'pm grant <packageName> <permissionName >.READ_PROFILE'"
and/or
Code:
adb devices
adb shell "su -c 'pm revoke <packageName> <permissionName >.READ_PROFILE'"
Setting section crashed after grant permission
adb -d shell pm grant com.oasisfeng.greenify android.permission.DUMP
Android 11
Setting section returne normale after revoke permissions
Any idea ?
I updated to Android 11 today, and got the same issue.
I found this:
[BETA] Greenify 4.7.5, 10.11.2019
10.11.2019 new beta 4.7.5 released on Play Store. See change log on Play Store https://play.google.com/store/apps/details?id=com.oasisfeng.greenify NOTE: YOU MUST REGISTER FOR GREENIFY BETA to install the Beta versions. See the Greenify...
forum.xda-developers.com
Seems it's not working properly under Android 11 and people think it's outdated
I got the same bug with Anroid 11
Hope that they will fix it soon
0utc0ntr0l2020 said:
Setting section crashed after grant permission
adb -d shell pm grant com.oasisfeng.greenify android.permission.DUMP
Android 11
Setting section returne normale after revoke permissions
Any idea ?
Click to expand...
Click to collapse
Same here :/
~Same problem here too.
Same problem here
I have the very same problem. I have another question and pleased to be answered; how to degrant a permission from greenify for example?
If it's like this
to grant:
adb -d shell pm grant com.oasisfeng.greenify android.permission.DUMP
to degrant:
adb -d shell pm degrant com.oasisfeng.greenify android.permission.DUMP
?
Same. And the app is not working as well as before the OS 11.1.1.1 update. Eg. Instagram is constantly waking up despite being Greenfied, along with various other apps.
OP6TNewb said:
Same. And the app is not working as well as before the OS 11.1.1.1 update. Eg. Instagram is constantly waking up despite being Greenfied, along with various other apps.
Click to expand...
Click to collapse
It's also the case for me. I think it (Instagram App) is persistent.
Hello
sorry if i write to Oppo Find X5... i not see theard Oppo Finx X6 Pro
My problem is more locale 2 - not working pm grant to change locale in other language
Can help... ??
I try:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell pm grant jp.co.c_lis.ccl.morelocale android.permission.CHANGE_CONFIGURATION
Exception occurred while executing 'grant':
java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
at android.app.ContextImpl.enforce(ContextImpl.java:2253)
at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:2281)
at com.android.server.pm.permission.PermissionManagerServiceImpl.grantRuntimePermissionInternal(PermissionManagerServiceImpl.java:1364)
at com.android.server.pm.permission.PermissionManagerServiceImpl.grantRuntimePermission(PermissionManagerServiceImpl.java:1346)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:553)
at android.permission.PermissionManager.grantRuntimePermission(PermissionManager.java:597)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:2591)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:302)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onShellCommand(PackageManagerService.java:6351)
at android.os.Binder.shellCommand(Binder.java:1073)
at android.os.Binder.onTransact(Binder.java:901)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4313)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onTransact(PackageManagerService.java:6335)
at android.os.Binder.execTransactInternal(Binder.java:1331)
at android.os.Binder.execTransact(Binder.java:1268)
Please help