Desktop and phone
Troubleshooting
The things that most often go wrong, and what to check first.
AI
Open the same URL in a browser. Ollama should answer at
http://<host>:11434/api/tags. If the browser cannot reach it either, the problem is the server or the firewall. From a phone, remember that localhost means the phone, so use your computer's LAN address.Reminders and notifications
Two settings decide this. Grant the exact-alarm permission, and accept the battery-optimisation exemption when offered. Both are on Settings ▸ Notifications. Android deliberately delays alarms for apps it has put to sleep.
Notes and the editor
Expected on a very large note the first time. Both editors virtualise their rendering, so scrolling stays smooth once it is open.
Data
Two things stop it deliberately. An archive written by a newer version of the app is refused rather than half-imported, and a restore aborts if the pre-restore safety snapshot cannot be written. Free some space and try again.
Still stuck?
The project keeps an open defect ledger in BUGS.md in the repository, recording for each entry whether it was reproduced in a running app, read from the source, or only inferred. If your problem is in there, it is known.