mirror of
https://github.com/tytydraco/LADB.git
synced 2026-04-27 00:15:59 +03:00
[GH-ISSUE #66] Can't executing grant permission command #51
Labels
No labels
bug
documentation
enhancement
enhancement
good first issue
help wanted
pull-request
question
question
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/LADB#51
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gplcn on GitHub (Apr 2, 2022).
Original GitHub issue: https://github.com/tytydraco/LADB/issues/66
When i submit command
adb shell pm grant com.arumcomm.crashlogviewer android.permission.PACKAGE_USAGE_STATS,the result is :@Rozia13 commented on GitHub (Apr 10, 2022):
@Kashifrazabb commented on GitHub (Apr 12, 2022):
Same. Have you got the solution?
@N-X-T commented on GitHub (Apr 14, 2022):
LADB auto jump to shell, try sending "pm grant com.arumcomm.crashlogviewer android.permission.PACKAGE_USAGE_STATS"
@gplcn commented on GitHub (Apr 14, 2022):
No
| |
sdgaopeilei
|
|
@.***
|
---- 回复的原邮件 ----
| 发件人 | @.> |
| 日期 | 2022年04月13日 04:14 |
| 收件人 | @.> |
| 抄送至 | @.@.> |
| 主题 | Re: [tytydraco/LADB] Can't executing grant permission command (Issue #66) |
Same. Have you got the solution?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
@gplcn commented on GitHub (Apr 14, 2022):
Tried it before, but it didn't work.
| |
sdgaopeilei
|
|
@.***
|
---- 回复的原邮件 ----
| 发件人 | @.> |
| 日期 | 2022年04月14日 19:19 |
| 收件人 | @.> |
| 抄送至 | @.@.> |
| 主题 | Re: [tytydraco/LADB] Can't executing grant permission command (Issue #66) |
LADB auto jump to shell, try sending "pm grant com.arumcomm.crashlogviewer android.permission.PACKAGE_USAGE_STATS"
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
@mirh commented on GitHub (Jun 10, 2022):
The "adb shell" part is already assumed by LADB.
You have just to enter
pm grant com.arumcomm.crashlogviewer android.permission.PACKAGE_USAGE_STATS@teou1 commented on GitHub (Oct 14, 2022):
And type everything manually, that error indicates wrong permission name, if you are copy pasting it from somewhere you might have caught a space with it.
@mirh commented on GitHub (Oct 15, 2022):
Spaces shouldn't cause any issue in a cli.. and copy pasting is usually more robust to errors.
@teou1 commented on GitHub (Oct 15, 2022):
In a nomal desktop OS yes, and if someone pastes the wrong type of quote or hyphen or nonenglish encoding the shell says so....but android adb throws weird and not understandable errors like this, so it is worth trying. Just my experience, it happened to me. Maybe i am wrong.
@mirh commented on GitHub (Oct 15, 2022):
I reckon unicode handling may be odd yes, especially if you are going from a CP 850 cmd.exe to the native unix shell.
But I don't think I have ever seen anything bad with spaces.
@tytydraco commented on GitHub (Oct 15, 2022):
I have a feeling that either the permission name you're entering is wrong (android.permission.PACKAGE_USAGE_STATS) or maybe, which OEM do you have? If it's like Xiaomi or something it might be removed in the OS.
@Luisdeugarza commented on GitHub (Jun 21, 2024):
I have a Xiaomi and I have this problem, what I can do?
@talhacomak commented on GitHub (Jun 19, 2025):
In some Xiaomi devices, the WRITE_SECURE_SETTINGS not given to the ladb app, so it can not give the WRITE_SECURE_SETTINGS or any secure permissions to any app.
Maybe this information would be added to the README