- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jan 12 2024
Uhm. This already works.
Jan 7 2024
Jan 6 2024
Thanks Luca asd
Dec 31 2023
Dec 23 2023
Dec 21 2023
sha256 9dc81af68d2bd8e5ac9664d981ea214189450450f5046358d742d81f4aea9715
sha256 488f040a278fa2f602b52040f9002813cc7281c573c789924cca76cecc03ab2e
.
Sorry asd
The changelogs should be:
Fix crash on Android 14 with MaTO live positions Small improvements with GTFS positions
Ok non ho spiegato bene il problema evidentemente.
Declined for T1221: Install OpenJDK 17 for LibreBusTO builder
Tested visiting the Map, and I still see bus navigating around, like silly machines.
Done with:
Dec 20 2023
docker run -ti --user 1004:1004 -v /opt/reyboz/android:/opt/reyboz/android -v /home/phabricator-android-builder:/home/phabricator-android-builder -v $(pwd):$(pwd) -w $(pwd) debian-fdroid-builder:latest
Dec 14 2023
Veramente serve il permesso per le sveglie per usare MQTT? asd
Dec 12 2023
- si chiede il permesso di mettere Sveglie (Alarms) all'utente
Dec 8 2023
Dec 3 2023
Done. Late.
Nov 28 2023
Nov 21 2023
Thanks, tested
Nov 20 2023
Also this can be followed upstream:
We can follow this upstream:
- Each alert has "id" so when downloaded again it can be easily identified.
- Each informed_entity is either a line or a stop. This could be translated in "a bell like" notification, that is displayed when the arrivals are shown with the stop (Or the line)
- The description_text can be put in a nice dialog that shows when the bell icon is touched
- We should account for the possibility of multiple alerts on a single stop, or line