lun_admin/NeoLaunch_From_Kvaesitso
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Docs

Browse Source
This commit is contained in:
MM20 2023-05-25 19:18:30 +02:00
parent b4d7aa16af
commit fdbb2d1609
No known key found for this signature in database
GPG Key ID: 0B61A8F2DEAFA389
2 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docs/developer-guide/integrations/icon-packs.md
View File

@ -107,7 +107,7 @@ month (`calendar_1`, `calendar_2`, etc. up to `calendar_31`).
:::note :::note
Single digit days must not be zero-padded (e.g. `calendar_1` is correct but `calendar_01` is not). Single digit days must not be zero-padded (e.g. `calendar_1` is correct but `calendar_01` is not).
Make sure all 31 drawables are present, or the launcher will reject the icon. Make sure that all 31 drawables are present, or the launcher will reject the icon.
::: :::
#### Clock icons #### Clock icons

15
docs/docs/user-guide/troubleshooting/granted-permissions.md Normal file
View File

@ -0,0 +1,15 @@
# Permission Requests for Already Granted Permissions
On some devices, the launcher might keeps asking for the notification permission even after you have
already granted it. This usually occurs a few minutes to hours after you have granted the
permission.
The problem is caused because some OEMs have too aggressive battery "optimization" in place which
terminate
the launcher's notification listener service prematurely. The launcher then notices that it can no
longer receive notifications and asks for the permission again.
The steps to fix that are different for each OEM but it usually involves disabling battery
optimization
for Kvaesitso. This website has a list of guides for different OEMs:
https://dontkillmyapp.com/