Page Comparison

• Migrating BlackBerry builds from Good Dynamics to Blackberry Dynamics, aligning GD App ID with Android App ID, extending full_backup_content.xml with exclusion gdstartupContinuum
• Upgrade of several build environment components (buildToolsVersion, JDK generation, ...)

• Korrektur GDApplicationID

• Signing APK with SHA-256 now

• Separating GDApplicationIDs to allow distribution of different build variants in one BES environment
• Raising version to reflect end of 2.x beta phase

• Raising target Androids to 5.0-8.0
• Making texts smaller, hence UI usable on modern smartphones
• Optimizing decimal number editing to be usable with buggy onscreen keyboard of Samsung XCover 3
• Support for operation in BB UEM jail using GD Library for HTTP(S) connections
• Support to use IMEI, Android_ID, Phone. Nr. as dynamic device ID

1.2.1 (1401)

• HTTP(S) requests to server now come with extended User-Agent header and additional X-MDA-* headers, to collect information about client's software version and track rollouts
• Workaround to avoid uncritical Exception MDAAPK-

• 20, which occured when the Server Sync Acitivity re-runs and fails while the device is still busy waking up

1.2.0 (1371)

• Introduces concept of configurable scanType, and 2 scanTypesa new scanType:
  • Beta support for barcode/RFID scanners in keyboard wedge mode (primarily for Pidion BIP-6000 Series)Experimental support for RFID scanners in NFC mode (primarily for Pidion BIP-6000 Series)
• Fixed MDAAPK-16: If suspended tours fail to get written to the storage completely, starting any tour became impossible. Now those damaged files are "migrated" into a failure report, getting them uploaded to the server for eventual manual "recovery" of measurement data already entered.
• To reduce occurences of MDAAPK-16 situations, specified and implemented MDAAPK-17, optimizing writing of tour xml files by a factor of 10:
  • Only the youngest "former measurement" is carried along, reducing the size of those xml files by up to roughly 49%
  • Tour files are written with a more efficient XML creation approach, and buffered
• Workaround for MDAAPK-18, a NPE for which I have no idea how it could have happened
• In case of an unexpected Exception (like MDAAPK-18), the UncaughtException report is now , speeding up the process and saving battery considerablyaccompanied by logcat output, which might include hints on the exact situation
• Fixed MDAAPK-19, wrong refusal of inserting digits in decimal value after comma but before the end

1.1.3 (978)

• Proposal for next measurement point to read now proposes the next un-finished measurement point, not the first un-finished measurement point
• Employee selection page shows Tour name and system date, to make visible which tour had been selected
• Extended recognition of allegro's left orange function key as back button

• After sync error message is confirmed, client now goes to main screen, making it clear that there are no automatic retries
• MDA Admin proposes Backend and Update URIs to allow faster initial configuration
• MDA Admin connection test 
  
  • now works in background (making it compatible with newer Android versions), and gives back more information in case of an error
  • now requests new connectionTest servlet instead of employee list
• Fixed missing recalculation of calculated values after using back button within complex measurement profiles
• Fine tuned display of download and upload progress
• Barcode variant of "fast mode"
• Easy way to go back to most recently saved measurement
• Server sync now starts with connection test to clearly distinct from tour XML problems
• Server sync checks difference between android system time and server time, and prints a warning if the difference is larger than 5 minutes

•  2 final UI enhancements