Uhm. This already works.

Thanks Luca asd

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:

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

Veramente serve il permesso per le sveglie per usare MQTT? asd

1. si chiede il permesso di mettere Sveglie (Alarms) all'utente

Done. Late.

Thanks, tested

Also this can be followed upstream:

We can follow this upstream:

1. Each alert has "id" so when downloaded again it can be easily identified.
2. 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)
3. The description_text can be put in a nice dialog that shows when the bell icon is touched
4. We should account for the possibility of multiple alerts on a single stop, or line