SAP will be updating the released version of the Afaria Android client available for download from Google Play. The list below includes the planned changes and is subject to change by the time of posting to Google Play. The final list will be included in the Google Play description.
What's New?
No new features are introduced in this version.
What's Fixed?
The following items are resolved and currently planned for inclusion.
- After Android 4.3 devices, installed with Afaria clients version 6.60.6406 (from Play Store), are upgraded to Android 4.4.2, the "Connecting… Connected… Failed." error messages occurred on Samsung Galaxy S4 devices.
- On a Samsung Galaxy S4 running Android 4.4.2 all subsequent Afaria Client connections fail once the MMEP has been installed.
- Unable to control device access on Exchange 365 for Motorola TC55
- Calls do not appear in the ConnLog which appears to be truncated
- Afaria fails to retrieve IMEI from Motorola TC55 (pre-production device)
- Calls/SMS made on an Android device are not showing in the connlog sent back to the server, this is possibly due to a corrupted SQLite database being rebuilt on the device
- When running an Android Configuration Policy containing Seed Data, after the initial update of configuration, every time the policy is subsequently run, the notification 'Afaria seed data Update complete' is raised, despite no further configuration changes having been made
- There is no list for "Data (3G network usage)" in Activity list to all of samsung android device.
- Afaria Client 6.60.6406 on Android 4.4.2 devices crashes when TEM is enabled and switching from WiFi to 3G
- Afaria seed file is not consumed by Android 6.60.6406 Client on Samsung Galaxy Tab 3 devices and a NullPointerException exception is seen in device log.
- The Afaria client crashes when running its schedules.
- Cancelled incoming calls logged as incoming calls with a non-zero time span call duration in Device Activity Data.