Releases: owntracks/android
Releases · owntracks/android
Android-v.2.3.0-beta1
Protect against notification channel being empty
Android-v.2.2.2
Changelog
Version 2.2.2
Breaking changes
- TLS hostname verification now no longer considers the CN field in the server certificate. This is in line with the deprecation of using CN for host verification as of RFC2818 (2000) and RFC6125 (2011). Instead, hostnames will be validated against the list of subjectAltNames (SANs) in the server certificate. If you were previously relying on the CN field in your certificate and didn't have any SANs listed, or the SAN list doesn't contain the hostname you're connecting to, TLS connections may now fail. The suggested course of action is to regenerate the cert ensuring that the SAN list is correct.
Bug fixes
Android-v.2.2.1
Changelog
Version 2.2.1
New features
- Russian translation!
- TLSv1.3 support
- Location messages now include the batteryStatus in line with iOS (#841)
- Added explicit remote configuration preference toggle
- Reverted the
tst
field of location/waypoint/transition messages to mean the time that the event occurred. Added a newcreated_at
field to these types with the timestamp of the message creation.
Bug fixes
- Prevent crash when a user inputs an invalid MQTT URL (#852)
- Fix an issue related to remoteCommands not being received or handled correctly (#842)
- Config import no longer crashes when waypoints are absent (#818)
- Map now correctly updates the blue dot when in foreground
- Configuration management screen now shows waypoints that will be exported
- Monitoring mode button should now be correct when Map activity is resumed
Android-v.2.2.0
Changelog
Version 2.2.0
New features
- Created a changelog!
- Logs now viewable and shareable from within the application (Status -> View Logs)
- Debug logs are now toggleable from the logs viewer UI
- Migrated preferences to androidx library
- MQTT errors are now displayed more clearly on the connection status.
- Locator intervals are now user-configurable, and differentiated between significant changes and move modes.
- Clearing a contact sends a zero-length payload rather than a JSON message for type
MessageClear
, in line with the iOS app and booklet - Users can specify the MQTT client ID explicitly
- Removed confusion around MQTT auth (no username vs anonymous). Now, not supplying a username = anonymous auth
- Added French translations
Bug fixes
- MQTT processor should be more stable at re-connecting when disconnected
- Improved reliability of internal message queue / backoff mechanism when unable to send a message
- Fixed some issues on the welcome screens on older (API<=24) devices
- Fixed race conditions in usage of the MQTT client
- Fixed input weirdness when trying to edit latlngs in the region UI
- Fixed some bugs in the configuration import / export handling
- Fixed a bug where MQTT tried to connect without a valid configuration
- Fixed a bug preventing users from putting the mode into low power mode
- Stale incoming locations are only discarded if the preference is set
- All messages have the current time populated into the
tst
field, as opposed to the time of the last location fix - Better reliability in reading from mis-typed preferences.
- Few general lint / stability fixes
Android-v.2.1.3
Build 21301
- [FIX] wrong long press label of report button
- [FIX] crash on invalid http headers
- [FIX] http connection not closed correctly on errors
- [FIX] location request not setup again on locator parameter change
- [FIX] include
debugLog
configuration key in export and editor - [FIX] some translations
- [NEW]
dontReuseHttpClient
config key to create a new HTTP client on every request. Can fix stuck queue on certain devives (see #656) - [NEW] removed locator interval and displacement UI settings because they were misunderstood causing too much confusion for many users
- [NEW] made locator accuracy configurable in signifficant mode with
locatorPriority
configuration key - [NEW] Improve display of error conditions
- [CHANGE] improved log handling
- [CHANGE] updated dependencies
Build 21302
- [FIX] Downgraded MQTT library to fix several issues
- [FIX] Back buttons and arrows in preferences
- [FIX] Monitoring mode not saved/restored correctly
- [FIX] Removed test location listener that could crash the background service
- [NEW] Remote reportLocation command triggers new location fix (thanks to @grheard)
- [NEW] Added debug log toggle in preferences
- [NEW] Removed region place picker because API was retiered by Google
Android-v.2.1.2
Build 21201
- [FIX] Crash in VersionFragment when no suitable browser is installed
- [FIX] Wrong wtst unit in waypoint messages (#631)
- [FIX] Crash when setting illegal username in HTTP mode
- [FIX] Crash when setting invalid geofence parameter
- [NEW] Debug logger that can export application logs to a HTML file. See our booklet for more details.
Owntracks has no influence on the notification size. To return to the old unobstrusive notification, manually set the priority to low by following the steps outlined in #633
Android-v.2.1.1
Bugfix release for Android-v.2.1.0
Build 21101
- [FIX] waypoint transitions were sent in quiet mode
- [FIX] reportLocation command was ignored in MQTT mode (#627)
- [FIX] wrong data types for alt, vel attributes in location message (#629)
- [FIX] crashes in WelcomeActivity
- [FIX] crash during EncryptionProvider initialization
- [FIX] crash when receiving waypoint message without radius
Build 21102
- [FIX] Setup screen got stuck on restrictions page
- [FIX] Improved error reporting (#567)
Android-v.2.1.0
- [NEW] Foreground/Background mode replaced by monitoring modes (quiet => No automatic location reports/passive location gathering, manual => Only automatic region location reports/passive location gathering, significant => automatic location reports/active location gathering based on Wifi/Cell location, move => frequent location reports/active location gathering based on GPS). Significant changes mode corresponds to the old behavior.
- [NEW] Locator displacement and interval only influence significant location monitoring mode
- [NEW] Monitoring modes displayed in notification when endpoint state is idle or connected
- [NEW] Prefilling new region with current location
- [NEW] Added estimated distance to contacts in details view
- [NEW] Moved background jobs to Android Work Manager. Reconnect/Ping jobs now have a minimum interval of 15 minutes.
- [NEW] Spanish translation. Thanks to @Kaysera.
- [NEW] Improved dependency handling and fixed several bugs
- [FIX] Waypoint import not working probperly
- [FIX] Config import not displayed correctly
- [FIX] Crash on first launch
- [FIX] Locations not correctly requested
- [CHANGE] Removed copy mode
- [CHANGE] Removed GUI to configure unauthenticated connections. auth preferences key can still be set via configuration editor if unauthenticated connections are really required
Special thanks to @growse for his various contributions
Android-v.2.0.0
First public release of version 2.0 optimized for modern Android versions.
Warning, this release drops support for bluetooth beacons
Changes
- Removed support for bluetooth beacons because that feature accounted for over 90% of all crashes
- Removed support for shared waypoints. Waypoints are now always treated as shared
- Removed support for our hosted public MQTT platform
- Added
ping
functionality that will trigger a location report periodically - Added support for Opencage Geocoder as alternative to Google
- Rewrote backend service from the ground up to work more reliable on modern Android versions that prevent many actions whe nthe app is in the background.
- Added custom useragent to HTTP mode to better identify the app in logs
- Added altitude to extended data publishes
- New algorithm for region detection that is assisted by location publishes
- Added support for inregions element of location publishes
- Fixed encryption issues with HTTP mode
A big thanks to @growse for his contributed code and all beta testers that identified possible issues.
Android-v.1.2.7
[FIX] #501 map not loaded correctly
[FIX] several crashes