Add docs to enable restricted settings on Android 13
This commit is contained in:
parent
ed3bcb6334
commit
df93f0260a
32
docs/docs/user-guide/troubleshooting/notification-access.mdx
Normal file
32
docs/docs/user-guide/troubleshooting/notification-access.mdx
Normal file
@ -0,0 +1,32 @@
|
|||||||
|
import MoreVertRoundedIcon from '@mui/icons-material/MoreVertRounded'
|
||||||
|
|
||||||
|
# Notification Access on Android 13+
|
||||||
|
|
||||||
|
Starting with Android 13, notification access is restricted for sideloaded apps. If you sideloaded
|
||||||
|
the APK, you might need to perform some extra steps to enable notification access (which is required for the music widget and for notification badges):
|
||||||
|
|
||||||
|
1. Try to grant the notification access permission as you would normally do. If you sideloaded the APK, all the controls are disabled:
|
||||||
|
|
||||||
|
<img src="/img/notification-access-1.png" width="300"/>
|
||||||
|
|
||||||
|
2. Tap on the disabled toggle “Allow notification access”. This dialog will show up:
|
||||||
|
|
||||||
|
<img src="/img/notification-access-2.png" width="300"/>
|
||||||
|
|
||||||
|
3. Tap “OK” to close the dialog.
|
||||||
|
|
||||||
|
4. Tap on the app icon. It leads to the app info screen.
|
||||||
|
|
||||||
|
<img src="/img/notification-access-3.png" width="300"/>
|
||||||
|
|
||||||
|
5. Tap on the 3-dot-menu (<MoreVertRoundedIcon/>) in the top-right corner.
|
||||||
|
|
||||||
|
:::info
|
||||||
|
This menu only shows up if you have tried to enable a restricted setting before. **Step 2 is crucial for this to work.**
|
||||||
|
:::
|
||||||
|
|
||||||
|
6. Tap on “Allow restricted settings”
|
||||||
|
|
||||||
|
<img src="/img/notification-access-4.png" width="300"/>
|
||||||
|
|
||||||
|
7. Go back to the previous screen. The controls are no longer disabled, and you can allow notification access.
|
||||||
@ -8,6 +8,11 @@ However there are a few things you might want to know:
|
|||||||
|
|
||||||
Per default, only media sessions from "music apps" are shown in the music widget. An app qualifies as "music app" if it has an activity that has either the `android.intent.action.MUSIC_PLAYER` action or the `android.intent.action.MAIN` action and the `android.intent.category.APP_MUSIC` category. Some media apps don't declare these in their manifests so the launcher won't recognize them as music apps. You can disable this filter in Settings > Widgets > Music > Restrict to music apps. With this setting disabled, the music widget will show media sessions from all apps, including non-music apps like browsers, video player apps and video streaming apps.
|
Per default, only media sessions from "music apps" are shown in the music widget. An app qualifies as "music app" if it has an activity that has either the `android.intent.action.MUSIC_PLAYER` action or the `android.intent.action.MAIN` action and the `android.intent.category.APP_MUSIC` category. Some media apps don't declare these in their manifests so the launcher won't recognize them as music apps. You can disable this filter in Settings > Widgets > Music > Restrict to music apps. With this setting disabled, the music widget will show media sessions from all apps, including non-music apps like browsers, video player apps and video streaming apps.
|
||||||
|
|
||||||
|
## I can't grant notification access permission!
|
||||||
|
|
||||||
|
Please refer to [notification access on Android 13+](/docs/user-guide/troubleshooting/notification-access)
|
||||||
|
|
||||||
## Why do I need to grant access to my notifications just to control some stupid media session?
|
## Why do I need to grant access to my notifications just to control some stupid media session?
|
||||||
|
|
||||||
That's a very good question. I don't know. Ask Google, why they make so [nonsensical decisions](https://www.reddit.com/r/mAndroidDev/comments/gn6ckb/man_im_so_happy_no_malicious_app_can_get_access/). The only way for third party apps to control media sessions is to read notifications and extract the media sessions from there. Sadly, the more privacy-friendly alternative is restricted to system apps only, ["due to privacy of media consumption"](https://developer.android.com/reference/android/Manifest.permission#MEDIA_CONTENT_CONTROL). Yep, that makes sense. Thank you, Google.
|
That's a very good question. I don't know. Ask Google, why they make so [nonsensical decisions](https://www.reddit.com/r/mAndroidDev/comments/gn6ckb/man_im_so_happy_no_malicious_app_can_get_access/). The only way for third party apps to control media sessions is to read notifications and extract the media sessions from there. Sadly, the more privacy-friendly alternative is restricted to system apps only, ["due to privacy of media consumption"](https://developer.android.com/reference/android/Manifest.permission#MEDIA_CONTENT_CONTROL). Yep, that makes sense. Thank you, Google.
|
||||||
|
|
||||||
|
|||||||
BIN
docs/static/img/notification-access-1.png
vendored
Normal file
BIN
docs/static/img/notification-access-1.png
vendored
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 126 KiB |
BIN
docs/static/img/notification-access-2.png
vendored
Normal file
BIN
docs/static/img/notification-access-2.png
vendored
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 126 KiB |
BIN
docs/static/img/notification-access-3.png
vendored
Normal file
BIN
docs/static/img/notification-access-3.png
vendored
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 110 KiB |
BIN
docs/static/img/notification-access-4.png
vendored
Normal file
BIN
docs/static/img/notification-access-4.png
vendored
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 123 KiB |
Loading…
x
Reference in New Issue
Block a user