8
10
Fork
You've already forked documentation
22

add explaination about background usage to FAQ #49

Merged
s1m merged 1 commit from Nickname/documentation:background-usage into dev 2026年03月24日 17:28:17 +01:00
Contributor
Copy link

Added a section about background permission requirements, as you suggested in Matrix.
Optionally Conversation could be noted as an example for apps requiring unrestricted access, but I dont want to bloat this.

Added a section about background permission requirements, as you suggested in Matrix. Optionally Conversation could be noted as an example for apps requiring unrestricted access, but I dont want to bloat this.
add explaination about background usage in FAQ
Some checks are pending
ci/woodpecker/pr/main Pipeline is pending approval
ci/woodpecker/pull_request_metadata/main Pipeline is pending approval
ci/woodpecker/pull_request_closed/main Pipeline is pending approval
aa57cd5d82 
Added a section about background permission requirements, as you suggested in Matrix. 
Optionally Conversation could be noted as an example for apps requiring unrestricted access, but I dont want to bloat this.
Owner
Copy link

Thanks for the contribution !

I think it is important for Conversations, because it works as a distributor the other apps can use, like Sunup or ntfy.

I will edit a little to talk about the default permission before UnifiedPush need 👍

Thanks for the contribution ! I think it is important for Conversations, because it works as a distributor the other apps can use, like Sunup or ntfy. I will edit a little to talk about the default permission before UnifiedPush need 👍
@ -54,1 +54,4 @@
## Q: Do Apps need permission to run in the background with UnifiedPush?
The app must have permission to run in the background for UnifiedPush to work. Apps are by default allowed to run in the background with optimizations("Optimized"). Most apps should work with that setting, although some apps might require the permission to run in the background without restrictions("Unrestricted"). This should not have a negative impact on your battery usage.
Owner
Copy link
- The app must have permission to run in the background for UnifiedPush to work. Apps are by default allowed to run in the background with optimizations("Optimized"). Most apps should work with that setting, although some apps might require the permission to run in the background without restrictions("Unrestricted"). This should not have a negative impact on your battery usage.
+ By default, applications have the permission to run in the background. And you can't deny background usage to the applications to use UnifiedPush. It should work with the default settings, although if are using Conversations as a distributor, some apps might require the permission to run in the background *without restrictions*. It should not increase the application battery consumption.
```diff - The app must have permission to run in the background for UnifiedPush to work. Apps are by default allowed to run in the background with optimizations("Optimized"). Most apps should work with that setting, although some apps might require the permission to run in the background without restrictions("Unrestricted"). This should not have a negative impact on your battery usage. + By default, applications have the permission to run in the background. And you can't deny background usage to the applications to use UnifiedPush. It should work with the default settings, although if are using Conversations as a distributor, some apps might require the permission to run in the background *without restrictions*. It should not increase the application battery consumption. ```
s1m changed target branch from main to dev 2026年03月24日 17:28:10 +01:00
Sign in to join this conversation.
No reviewers
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
UnifiedPush/documentation!49
Reference in a new issue
UnifiedPush/documentation
No description provided.
Delete branch "Nickname/documentation:background-usage"

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?