Releases: RADAR-base/radar-commons-android
Releases · RADAR-base/radar-commons-android
radar-commons-android version 0.6.1
Changes since version 0.6:
- Added Android 8 notification channels support
- Check for malformed float and double data being submitted by plugins
- More precise login failure messages
- Less intrusive Bluetooth and permission handling.
- Do not try to login when there is no internet.
- Fixed crash on missing auth state
radar-commons-android version 0.6
Changes since version 0.5.2:
- Updated DataCache API to match new radar-commons RestSender API
- More graceful recovery on Device registration conflict with measures to prevent such conflict
- Do not crash on wrong device providers, but log an exception instead.
radar-commons-android version 0.5.2
Changes since 0.5.1:
- dependency publication fixes
- fix for empty device filter #39
radar-commons-android version 0.5.1
radar-commons-android version 0.5.1
Changes since version 0.5:
- updated Gradle and Android versions
- fixed javadoc generation
- Use Crashlytics logging
- Update current AppAuthState after
loginSucceeded
radar-commons-android version 0.5
radar-commons-android version 0.5
Changes since version 0.4:
- Fixed settings propagation on reset/restart
- Added authentication to connection checks
radar-commons-android version 0.4
radar-commons-android version 0.4.
Changes since version 0.3.4:
- Interoperable with RADAR Management Portal 0.3.x
- Fixed Management Portal data propagation
radar-commons-android version 0.3.4
radar-commons-android version 0.3.4
Changes since version 0.3.3:
- Use
START_STICKYto restart service if closed - Fixed ManagementPortal device registration
- Fixed server status propagation
RADAR-Commons-Android version 0.3.3
RADAR-Commons-Android version 0.3.3
Changes since version 0.3.2:
- Set sources on providers' initialization
Changes since version 0.3.1:
- Fixed a ConcurrentModificationException and a NullPointerException on application start
Changes since version 0.3:
- Hotfix: Fixed requesting of app usage and location tracking permissions
Changes since version 0.2.1:
- Simplified registration of topics
- Reconfiguration of service providers
- Moved most of the logic into RadarService
- Moved OfflineProcessor from Phone plugin
- Allow creation of services which don't require Bluetooth connection
- Added disk space checker
- Added integration with Management Portal
- Added login managers
- New caching mechanism
- Updated radar-commons and radar-schemas-commons versions
- Lots of small fixes and improvements
- Updated documentation
Changes since version 0.2:
Hotfix: also propagate Strings in RadarConfiguration
Changes since version 0.1:
- Use minimum Android API level 21 and target API level 25
- Went from RADAR-Commons 0.2 to 0.4
- Fixed bug that the app would hang after close
- Added more parameters
- Use shared ExecutorService in caches
- Do not crash on invalid radar configuration
- Added Network and Battery level broadcastreceiver utilities
- Send data only with WiFi (configurable) and reduce messages when battery levels are low
- Send data at a reduced rate, unless a record batch is full
- Deprecated PersistentStorage in favour of SharedPreferences
- Set a maximum QueueFile size
- If QueueFile addition fails because the queue is full, do not invalidate previous additions.
RADAR-Commons-Android version 0.3.2
RADAR-Commons-Android version 0.3.2
Changes since version 0.3.1:
- Fixed a ConcurrentModificationException and a NullPointerException on application start
Changes since version 0.3:
- Hotfix: Fixed requesting of app usage and location tracking permissions
Changes since version 0.2.1:
- Simplified registration of topics
- Reconfiguration of service providers
- Moved most of the logic into RadarService
- Moved OfflineProcessor from Phone plugin
- Allow creation of services which don't require Bluetooth connection
- Added disk space checker
- Added integration with Management Portal
- Added login managers
- New caching mechanism
- Updated radar-commons and radar-schemas-commons versions
- Lots of small fixes and improvements
- Updated documentation
Changes since version 0.2:
Hotfix: also propagate Strings in RadarConfiguration
Changes since version 0.1:
- Use minimum Android API level 21 and target API level 25
- Went from RADAR-Commons 0.2 to 0.4
- Fixed bug that the app would hang after close
- Added more parameters
- Use shared ExecutorService in caches
- Do not crash on invalid radar configuration
- Added Network and Battery level broadcastreceiver utilities
- Send data only with WiFi (configurable) and reduce messages when battery levels are low
- Send data at a reduced rate, unless a record batch is full
- Deprecated PersistentStorage in favour of SharedPreferences
- Set a maximum QueueFile size
- If QueueFile addition fails because the queue is full, do not invalidate previous additions.
RADAR-Commons-Android version 0.3.1
RADAR-Commons-Android version 0.3.1
Changes since version 0.3:
- Hotfix: Fixed requesting of app usage and location tracking permissions
Changes since version 0.2.1:
- Simplified registration of topics
- Reconfiguration of service providers
- Moved most of the logic into RadarService
- Moved OfflineProcessor from Phone plugin
- Allow creation of services which don't require Bluetooth connection
- Added disk space checker
- Added integration with Management Portal
- Added login managers
- New caching mechanism
- Updated radar-commons and radar-schemas-commons versions
- Lots of small fixes and improvements
- Updated documentation
Changes since version 0.2:
Hotfix: also propagate Strings in RadarConfiguration
Changes since version 0.1:
- Use minimum Android API level 21 and target API level 25
- Went from RADAR-Commons 0.2 to 0.4
- Fixed bug that the app would hang after close
- Added more parameters
- Use shared ExecutorService in caches
- Do not crash on invalid radar configuration
- Added Network and Battery level broadcastreceiver utilities
- Send data only with WiFi (configurable) and reduce messages when battery levels are low
- Send data at a reduced rate, unless a record batch is full
- Deprecated PersistentStorage in favour of SharedPreferences
- Set a maximum QueueFile size
- If QueueFile addition fails because the queue is full, do not invalidate previous additions.