Skip to content

Commit 8c95326

Browse files
committed
permissions: remove wake lock
which was used on api levels lower than 23
1 parent c74b603 commit 8c95326

File tree

2 files changed

+1
-2
lines changed

2 files changed

+1
-2
lines changed

app/src/main/AndroidManifest.xml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,6 @@
1515
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
1616
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
1717
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
18-
<uses-permission android:name="android.permission.WAKE_LOCK" />
1918
<uses-permission android:name="android.permission.READ_SYNC_SETTINGS" />
2019
<uses-permission android:name="android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS"/>
2120
<!-- ACCESS_COARSE_LOCATION is required to get WiFi's SSID on 8.1 -->

wiki/Info-on-battery-optimization-and-settings-affecting-battery-usage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
First things first:
22
* Syncthing-Fork requires to be exempted from doze which is asked during the welcome wizard. The app will cease to function if the permission is revoked.
3-
* The app doesn't require the permission to "waste" your battery and the app doesn't use it to set wakelocks. It does run a reliable so called "Android foreground service".
3+
* The app doesn't require the permission to "waste" your battery. It does run a reliable so called "Android foreground service".
44
* Technically speaking, it's required to avoid database corruption in case Android can't communicate with the SyncthingNative before putting the app and SyncthingNative in suspend.
55

66
Here is how you can reduce battery usage even further by optimizing Syncthing's settings:

0 commit comments

Comments
 (0)