Apps
FewDo
This app helps you with IF-THEN automations on your Android phone: when something happens (IF), FewDo runs the actions you chose (THEN).
Overview
FewDo is offline-first. Automations live on the device. There is no FewDo account and no cloud sync. Network use happens only when you configure an HTTPS webhook action. No ads. No analytics.
The model is simple: one or more IF conditions (AND/OR) → one or more actions. You can enable or disable each automation, test actions with Run now, and review a local execution history.
What the app does
- Create, edit, copy, reorder, enable, and delete local automations.
- Combine up to five IF conditions with AND/OR connectors and an ordered list of actions.
- Trigger on Bluetooth, time schedules, notifications, device state, and more.
- Run actions for notifications, volume/display, waits, webhooks, apps/Settings, device controls, and more.
- Optionally reverse selected actions when the IF ends (same AND/OR rules as the IF list).
- Show per-flow readiness warnings when permissions or special access are missing.
- Export/import automations as JSON (HTTP secrets are never exported), view history, copy a redacted engine log, and more.
IF conditions (triggers)
Triggers include:
- Bluetooth - a paired device connects or disconnects, or is currently connected (any device or a specific one).
- Time - approximate time or time period on selected weekdays or every day. Schedules are intentionally inexact and can be delayed by battery saving.
- Notification - a chosen app posts or removes a notification; optional local title/text matching. Needs Notification Access.
- Device state - Wi-Fi, charging, headphones, Android Auto, NFC tag, place, foreground app, and more (many of these need PrivBridge running).
...and more, as shown in the editor.
THEN actions
Actions run in order. Examples:
- Show a notification; set media or ring volume; change brightness, timeout, or orientation; Do Not Disturb; torch; vibrate.
- Wait a number of seconds, or wait until Bluetooth / USB headphones / Android Auto (and related wait-until targets).
- Timer or alarm (background runs may open via a tap notification).
- HTTPS webhook (GET/POST/PUT/PATCH/DELETE) with Keystore-protected secret headers.
- Open a URL, app, or Android Settings screen (some automatic runs may require tapping a handoff notification).
- With PrivBridge: Wi-Fi/Bluetooth/NFC/mobile data toggles, connect/disconnect Bluetooth, VPN on/off for a chosen VPN app, play/pause media, navigation keys, app launch/force-stop, screen lock (never unlock), and more.
...and more, as shown in the editor.
PrivBridge
PrivBridge is a shell bridge (UID 2000, not root). It pairs with Android Wireless debugging so device IFs and THENs that need it can run. It does not unlock the device.
- Home shows PrivBridge: On / Off. Automations that need it warn when it is Off and offer Set up PrivBridge.
- Easy pairing: Developer options → Wireless debugging → Pair with code → reply to the FewDo notification with the 6-digit code → confirm UID 2000.
- USB debugging is not required by Android for Wireless debugging, but some Samsung devices need USB debugging on briefly if Connect fails.
- After PrivBridge reports On, on Samsung prefer turning USB debugging off so PC plug/unplug does not kill the bridge. Leave Wireless debugging on if you want auto-recovery.
- A reboot ends the shell process. Enable Wireless debugging again and tap Connect and start PrivBridge.
- Stop PrivBridge stays stopped until you start it again.
Do not expect PrivBridge to survive every OEM debugging toggle or USB cable event. Behaviour varies by device.
Good to know
- Force-stopping FewDo pauses automatic triggers until you open the app again.
- Exact-to-the-second schedules need granted exact-alarm access; otherwise timing is approximate.
- Locked devices stay locked. FewDo does not request unlock or full-screen intent bypass.
- Permissions (Nearby devices, notifications, Notification Access, Modify system settings, and others) are requested only when a feature needs them.