Skip to content

Colota - Android GPS Location tracker

Fix docs: permission note formatting, stale reference, remove duplicate section

Max Dietrichc1f284057170
diff --git a/apps/docs/docs/configuration/server-settings.md b/apps/docs/docs/configuration/server-settings.md
index d6284576..3dedd5bd 100644
--- a/apps/docs/docs/configuration/server-settings.md
+++ b/apps/docs/docs/configuration/server-settings.md
@@ -23,7 +23,7 @@ Your server endpoint must accept HTTPS requests (POST or GET depending on your H
- `100.64.x.x – 100.127.x.x` (CGNAT)
- `169.254.x.x` (link-local)
-On **Android 17+**, connecting to another device on the local network (everything above except `localhost`) requires the **Nearby Wi-Fi Devices** permission. Colota requests this when you use **Test Connection**. See [Permissions](/docs/development/permissions#local-network-nearby-wi-fi-devices) for details.
+On **Android 17+**, connecting to another device on the local network (everything above except `localhost`) requires the **ACCESS_LOCAL_NETWORK** permission. Colota requests this when you use **Test Connection**. See [Permissions](/docs/development/permissions#local-network-access) for details.
Use the **Test Connection** button in settings to verify your server is reachable.
diff --git a/apps/docs/docs/development/permissions.md b/apps/docs/docs/development/permissions.md
index 7c75aacd..924bb469 100644
--- a/apps/docs/docs/development/permissions.md
+++ b/apps/docs/docs/development/permissions.md
@@ -88,7 +88,11 @@ android.permission.ACCESS_LOCAL_NETWORK
Starting with Android 17, apps need this permission to connect to devices on the local network. Colota requests it when you use **Test Connection** with a private/local IP endpoint (e.g. `192.168.x.x`, `10.x.x.x`, `172.16-31.x.x`, or `100.64.x.x`). Loopback addresses (`localhost` / `127.0.0.1`) do not require this permission. If your server is a public HTTPS endpoint, this permission is never requested.
-:::note Android 16 On some Android 16 devices, local network access may be enforced early via security patches. In this case, Android uses the **Nearby Wi-Fi Devices** (`NEARBY_WIFI_DEVICES`) permission instead. If your local server is unreachable on Android 16, go to **Android Settings > Apps > Colota > Permissions** and enable **Nearby devices** manually. :::
+:::note[Android 16]
+
+On some Android 16 devices, local network access may be enforced early via security patches. In this case, Android uses the **Nearby Wi-Fi Devices** (`NEARBY_WIFI_DEVICES`) permission instead. If your local server is unreachable on Android 16, go to **Android Settings > Apps > Colota > Permissions** and enable **Nearby devices** manually.
+
+:::
### Battery Optimization
diff --git a/apps/docs/docs/integrations/custom-backend.md b/apps/docs/docs/integrations/custom-backend.md
index 121e66e1..2aabe961 100644
--- a/apps/docs/docs/integrations/custom-backend.md
+++ b/apps/docs/docs/integrations/custom-backend.md
@@ -98,22 +98,6 @@ your-domain.com {
}
```
-## Compatible Backends
-
-Colota works with any service that accepts HTTP POST or GET requests. Built-in templates are available for:
-
-- **[Dawarich](/docs/integrations/dawarich)** - Self-hosted location history
-- **[OwnTracks](/docs/integrations/owntracks)** - Self-hosted presence tracking
-- **[PhoneTrack](/docs/integrations/phonetrack)** - Nextcloud location tracking
-- **[Reitti](/docs/integrations/reitti)** - Self-hosted location tracking
-- **[Traccar](/docs/integrations/traccar)** - GPS tracking platform (HTTP GET)
-
-Also works with:
-
-- **Home Assistant** - via webhook or REST API
-- **Node-RED** - flow-based automation
-- **Any HTTP server** - that accepts POST (JSON) or GET (query params)
-
## Configuration
1. Go to **Settings > API Settings**