Releases: owntracks/android
Releases · owntracks/android
v2.4.3-beta2
Updated changelog
v2.4.3-beta1
Disable paho auto-reconnect, because it's really really really buggy
v2.4.2
Changelog
Version 2.4.2
New features
- The ongoing notification should now not wake up the lock screen if the content changes.
Bug fixes
- Fix crash on startup where shared preferences has some invalid values
- Fix crash on being prompted to enable device location because of a callback not being initialized properly
- Fix crash due to a race when reverse geocoding the contacts
- Fix crash due to Android SDK bug throwing unexpected error when fetching current connection details
v2.4.1
v2.4.0
Changelog
Version 2.4.0
New features
- The welcome screen is now swipey!
- Dark theme! (thanks to all who suggested, closes #787 #788 and #789)
- On Android API>=30, when the service is started in the background (e.g. after a boot or upgrade), it'll now notify the user that locations won't be received unless the app has been explicitly interacted with (via the activity, or changing the monitoring mode etc). This is because of the new Android background location limits. (See #976, #969, #967)
- Polish translation (thanks Robert!)
- You should now be able to exit the app by sending an intent (e.g. from other apps like Tasker etc.). Sending a "startservice" intent with
org.owntracks.android.EXIT
should stop the service as well as quit the app. Closes #982. - Split the app into two Android flavors - OSS and GMS. GMS is what will continue to be published to the play store, but the OSS will now be published on the GitHub releases as well. The OSS version looks to remove dependencies on Google's Play Services and closed-source maps libraries. Ultmiate aim is to have a version we can distribute via F-Droid, giving users the option for a version that's more open.
- Log screen will now only display actual application logs, rather than just a dump from
adb logcat
which wasn't that useful. - Exported configurations are now pretty printed (thanks @nycex)
- The outgoing message queue is now persisted to device storage, so it should survive both app and device restars (closes #994)
- Contact bottom sheet now includes details about their battery, speed, altitude, and bearing
- Location messages now also include the BSSID and SSID if available. Closes #871
- The Geocoder error notification can now be enabled/disabled in the preferences
- Added topic key to HTTP messages. Closes #1047
- [Experimental] Added the ability to use OpenStreetMap instead of Google Maps as a mapping layer. Can be enabled by adding
useOSMMap
to theexperimentalFeatures
config key. - [Experimental] Added the ability to use a pure AOSP location provider instead of the Google Play Services
FusedLocationProviderClient
. Can be enabled by addinguseAospLocationProvider
to theexperimentalFeatures
config key. - [Experimental] Have the contact peek bearing arrow rotate depending on the current devices orientation
Bug fixes
- Lower notification priority of geocoder error notifications to make them a bit less present / shouty
- If location is disabled on-device, OT will now prompt the user to enable on startup.
- Fix crash on opening contact list where there's a card for a user but no location yet (#984)
- Map view will now start on a recognizable map location (Paris) rather than at 0,0
- Clicking "back" with a contact sheet open will now close the sheet rather than minimize the activity
- Retry backoff for messages now goes up to 2 minutes
- Messagecards are cached, so if a contact is cleared and then re-appears on the broker, the image and name are correct
- If the username is not specified, the topic username is correctly set to be "user"
v2.4.0-beta4
Prevent crash when outgoingQueueIdlingResource is idle on message deq…
v2.4.0-beta3
Use a Google Material edittext instead of an Edittext because of bett…
v2.4.0-beta2
Beta / prod releases should build APKs with the right version code in
v2.4.0-beta1
Capture logcat on build failure
Android-v.2.3.0
Changelog
Version 2.3.0
New features
- Config can now be loaded by the app using an
owntracks:///
URI, either pointing at a remote config location or encoded inline in base64. - Multiple MQTT topics (space-delimited) are now supported under the
subTopic
preference - Message sending is now retried on failure up to 10 times, or 10,000 times for location messages to be better resilient against transient failures, but to also not block the queue for messages that upstream can't handle. (#936)
- Geocoder will now handle errors from the Geocoding service more gracefully, showing a notification and respecting rate-limiting / backing off. (#942)
- Minor UI changes separating the About screen from the rest of the preferences
- HTTP Useragent changed from "Owntracks/" to "Owntracks-Android/" to better indicate to servers which OT client it is
- Catalan language support (thanks Rafroset!)
Bug fixes
- Fix bug relating to geocoding handling where the displayed value was not correctly updated.
- Geocoder now only considers first 4dp of location lat/lng to prevent too many requests resulting from tiny location drift
- Background location permission no longer needed, so removed
- Fix for regression introduced in 2.2 where self-signed certificates supplied as the CA were doing more restrictive hostname checking (#896). Hostnames are no longer matched if the CA cert is the same as the MQTT leaf cert.
- Geocoder preference should now work properly on API<24
- Initial location fix should now also work better on API<24
- Fix an issue where trying to exit the app wouldn't work if there were outstanding messages queued to be sent (#954)