Release Notes Archive

Enhancements

The following items are newly-implemented features intended to increase end-user productivity throughout TrackIt.

TrackIt Android has been updated to be compatible with the new version of ISE eFleetSuite. Because of some recent changes to the ISE eFleetSuite application, TrackIt Android would behave unexpectedly during login and logout.

The Location Disclosure message for TrackIt Android has been updated to read: "TrackIt collects location data in the background even while not in use, to enable auto-statusing and real-time map visibility for dispatch." To accept the disclosure and continue to the app, tap OK.

Corrected behavior:

The DVIR card for VisTracks customers now functions as intended to alter Pre- and Post-Trip Certifications and trigger DVIR Pre-Trip or DVIR Post-Trip alerts.

Previous behavior:

The DVIR card for customers with VisTracks did not change properly for the Pre- and Post-Trip Certification. This caused the alerts function associated with DVIR alerts to function incorrectly.

Enhancements

The following items are newly-implemented features intended to increase end-user productivity throughout TrackIt.

Water Allowed and Water Extra fields have been added to the Load Properties card for trucks with the TrackIt Delivery Cycle Monitoring assembly.

Corrected behavior:

Engine data updated through Custom Events will be updated on the Engine Signal report.

Previous behavior:

The Engine Signal report was not updating engine data that is updated through Custom Events.

Enhancements

The following items are newly-implemented features intended to increase end-user productivity throughout TrackIt.

The COMMANDassurance APK will now send its version information to the TrackIt Web Console. The APK version will be displayed in the Tracking Device screen in Settings > Tracking Device > Tracking Device. Additionally, the probe firmware versions can be viewed in the Edit Equipment dialog screen found in Settings > Equipment > Equipment. Customers must have COMMANDassurance version 5.5.12+ to view versions in the TrackIt Web Console.

A new Change Wifi State setting was added to the Settings menu in TrackIt Android. The setting allows users to turn on the device's Wi-Fi without requiring them to exit out of the MDM lock screen.

The Dutch translation for the Load Properties card has been updated based on feedback from a customer in the Netherlands.

Enhancements

The following items are newly-implemented features intended to increase end-user productivity throughout TrackIt.

Registration for TrackIt Android devices has been adjusted for recent changes to Android OS 10. Any device running OS 10 and TrackIt Android 14.4.54 or above will not accept IMEI numbers as the TRACKIT DEVICE ID. Instead, the device's 10-digit phone number will be used to identify the device. Device registration with devices running OS 9 or previous operating systems will continue to use either the device IMEI or phone number as before. BYOD customers can refer to these instructions for device installation and registration.

To register an OS 10 device with TrackIt Android

PREREQUISITE: Data and all Enterprise Mobility Management solutions must be enabled and given full permissions. This includes: Android Enterprise, SureMDM, and SureLock.

1. On your OS 10 device, launch the TrackIt Android app.
2. On the Location Disclosure screen, tap OK to allow TrackIt to collect vital location data.
3. Tap the Existing tab. The device phone number should appear in the TRACKIT DEVICE ID field.
4. Tap SAVE to finish registering the device. The app then redirects you to the login page.
5. Enter an employee and vehicle number before tapping LOGIN to begin using TrackIt Android as needed.

Enhancements

The following items are newly-implemented features intended to increase end-user productivity throughout TrackIt.

A Location Disclosure dialog now appears in TrackIt Android upon initial start up. As Google now requires, the dialog informs users that TrackIt collects location data while running in the device background. Users can navigate away from the dialog by tapping OK below the message.

The Display Over Permission for OS10 devices is now a Suggested permission instead of a Critical permission. Because the permission is set as Suggested, drivers will not receive an urgent notification if the permission is disabled. However, the permission is still required for TrackIt Android to function properly in the device foreground.

TrackIt Android no longer redirect drivers to enable Critical Permissions when drivers log in to the app. Red Bar Alerts are now used to remind TrackIt Android users when permissions need to be enabled. Additionally, missing Critical Permissions are displayed in the System Health Summary report.

Enhancements

The following items are newly-implemented features intended to increase end-user productivity throughout TrackIt.

The Current Volume and Current W/C Ratio (Water/Cement ratio) values were added to the Load Properties card for users of the TrackIt Delivery Cycle Monitoring. This change will give drivers access to more real-time information from the TrackIt Delivery Cycle Monitoring system.

The Display Over permission for OS10 devices has been changed to a suggested permission instead of a critical permission. Previously, drivers would get stuck on the login page because of the permission was set as critical.

Enhancements

The following items are newly-implemented features intended to increase end-user productivity throughout TrackIt.

Drivers will now be able to log in to VisTracks and run ELD successfully even if VisTracks servers are unavailable for sync. Previously, drivers could not log in to VisTracks if its servers were unavailable.

The previous TrackIt Android v14.4.49 release caused the TrackIt Android application to stop responding in some instances. With this update to the release, the application will be fully responsive.

TrackIt Android will now always send the most accurate and recent odometer values to VisTracks. Previously, some situations occurred in which the odometer values sent to VisTracks were significantly different than the actual odometer values.

Enhancements

The following items are newly-implemented features intended to increase end-user productivity throughout TrackIt.

The Load Properties card was updated to display details about drum revolutions received from the TrackIt Delivery Cycle Monitoring. Charging and Discharging Revolutions fields were added. These new fields and the Total Revolutions field will be reset to zero when a new ticket is assigned.

To support TrackIt Android functionality with Android OS 10, TrackIt GPS coordinates will be sent even if TrackIt Android is running in the background for an extended period of time. Previously, battery optimization for Android OS 10 would interfere with GPS coordinate transmission when TrackIt Android was running in the background.

TrackIt Android will no longer report a communication error with COMMANDassurance unnecessarily. No error will be reported when a driver clocks out or when a brief loss of communication occurs between TrackIt Android and the COMMANDassurance app. Only lengthy communication losses will be reported.

In some cases previously, TrackIt would report a COMMANDassurance communication error when a driver clocked out of TrackIt Android. This scenario would cause the System Health Summary and System Health History reports to display inaccurate data.

Enhancements

The following items are newly-implemented features intended to increase end-user productivity throughout TrackIt.

The No Sensor Signal health state was added to the DRS Health Aspect in the System Health Summary and System Health History reports. This state will display when a vehicle with the TrackIt Delivery Cycle Monitoring system is not receiving signals from the sensor.

Truck Ahead and Truck Behind cards have been enhanced to display truck statuses accurately even if the trucks are assigned different status types.

TrackIt Android's connection with Mobile Ticket has been modified, and DNS resolution logic was changed.

The Water Added value on the Load Properties card was adjusted to provide a more consistent display. With the change, the value on the card will match the value displayed on both the Load Properties report in the TrackIt Web Console and the COMMANDassurance display installed on a truck.

With this enhancement, the map locations associated with the Truck Ahead and Truck Behind cards will now be updated more frequently in real time. Previously, the map locations associated with these cards would sometimes update at longer intervals than preferred by customers.

A new processing icon will display on the Load Properties card when data is being transmitted from COMMANDassurance and cannot yet display. Previously, "N/A" was displayed on the card in this scenario, but will now only display when the drum is not loaded.

Corrected behavior:

TrackIt Android will process all status changes sent from the COMMANDassurance even if the app is running in the background.

Previous behavior:

In some cases, TrackIt Android would ignore the status changes triggered by the Probe. This happened in cases where TrackIt was in the background when the status change triggered.

A new DVIR Post-Trip alert has been added to the Web Console for VisTracks users. This alert will trigger when a driver attempts to enter the Clock Out status or Log Out of TrackIt Android without first completing a Post-trip DVIR. Administrators have the option to prevent drivers from clocking out until the Post-trip DVIR is complete.

A new DVIR Pre-Trip alert was created for TrackIt and VisTracks users. If a driver starts their vehicle without completing a Pre-trip DVIR, this alert can be set to trigger.

Tickets received by TrackIt from a ticketing system will now automatically update VisTracks. This means that shipment information present on a ticket in TrackIt will create an Hours of Service Shipment in VisTracks. With this update, drivers can more easily stay compliant with the ELD mandate.

A new status card for DVIR users has been created. This card allows VisTracks users to see from the TrackIt app whether their Pre-Trip and Post-Trip DVIRs have been certified during a session. By tapping on the card, this launches the VisTracks app and allows the user to begin their DVIR.

When the DVIR has been completed, this is reflected via the DVIR card.

A new algorithm for the Loading status has been created for Drum Rotation Sensor (DRS) customers.

A new screen has been added to the TrackIt app to allow for the manual enabling of feature permissions. This screen will typically display upon initially launching the TrackIt app if specific permissions have not yet been enabled. Once the Phone Calls, Device Location, and Files permissions are enabled for the device, then the screen no longer displays when the app is launched. However, this screen may still be accessed by navigating to the Settings screen.

TrackIt has been updated to send the probe health aspects to the server. The TrackIt app now reports whether or not TrackIt is connected to the COMMANDassurance Probe solution.

Corrected behavior:

TrackIt will not fail to log in a driver if VisTracks cannot initialize the app or sync with the VisTracks server.

Previous behavior:

TrackIt failed to log in a driver when it could not initialize the VisTracks app or sync with the VisTracks server.

Updated reports to show (DRS) as the change type any time a status change is made by the Drum Rotation Sensors (DRS).

Adjusted logic for the Load Properties card to show the drum as Stopped instead of N/A if the application is not detecting a charging or discharging direction from DRS.

Added logic to to change a truck's status to Washing based on logic associated with the Drum Rotation Sensors.

Corrected behavior:

The GPS Health Aspect now reports No GPS - Permission, when TrackIt cannot capture the GPS due to insufficient Android permissions.

To address this, support staff (or the driver, for 3P) will then need to adjust tablet permissions.

Previous behavior:

In the GPS Health Aspect report, it showed the GPS as Good because Location Services was turned on, but TrackIt was unable to capture GPS due to insufficient Android permission (i.e., background location).

Various changes have been made to the TrackIt Android application's security and permissions functionality as part of ongoing Android 10 support efforts.

Corrected behavior:

EDCs now configure correctly on tablets using iOS v9.

Previous behavior:

EDCs would not configure consistently with tablets using iOS v9.

Corrected behavior:

The Truck Ahead and Truck Behind status cards now update in real time as expected.

Previous behavior:

The Truck Ahead and Truck Behind status cards were not updating in real time, sometimes lagging upward of 15 to 20 minutes behind.

Corrected behavior:

If a driver re-centers the map on the Truck Ahead/Truck Behind cards, the pin will remain displayed.

Previous behavior:

When using the Truck Ahead/Truck Behind card, if a driver re-centered the map the pin would disappear.

Corrected behavior:

Pressing the Home button on the TrackIt app will no longer cause the application to close.

Previous behavior:

If a user pressed the Home button on the TrackIt app, the application would occasionally crash.

Updated TrackIt app to immediately update the software version in TrackIt Web once an update is installed on a tablet.

Updated the communication method between ESM and TrackIt on the tablet to better conform to the methods compatible with Android v9+.

The battery power levels on the Probe have been updated to use the numbers 1 through 4. Previously, the values -1 through 3 were used. As a result, the Load Properties card on the TrackIt Android app showed the wrong status based on the previous numbering.

The TrackIt app Load Properties card has been improved to show the correct battery power status based on the 1 - 4 numbering.

To see the battery status, tap on the Load Properties card to see the full screen detail view.

When the Probe is reset, it will send data to TrackIt with values of zero (0). The zero value data is meant merely as a "reset" dataset and is not accurate with regard to the status of the load or the Probe battery. As a result, the zero value was causing a Low Probe Battery alert to trigger when it shouldn't.

The TrackIt app and Web Console have been improved to ignore the dataset that is sent from the Probe when the device initially resets. As a result, the Low Probe Battery alert will not accidentally trigger on a Probe reset anymore.

Due to changes with Android 9+, instructions must be made for whether an app requires a foreground or background service to run correctly. To address this, both TrackIt Android and Event Services Manager have been bound. Both apps, which are required for engine data, will always run together.

TrackIt now updates the Returning Navigation card on a tablet to reflect any new location when a delivery address changes. Previous to this, if only the latitude or longitude changed, the card was not updated.

Corrected behavior:

TrackIt messages will attempt to deliver until the Android application successfully receives the message.

Previous behavior:

TrackIt messages would not deliver to the tablet device if the Android app crashed while the message was being delivered.

Corrected behavior:

After logging in on TrackIt Android, the Diagnostics screen will not be available if the vehicle does not have a Probe license assigned.

Previous behavior:

After logging in on TrackIt Android, users could still navigate to the Diagnostics screen despite the vehicle not having a Probe license assigned.

The Load Properties Card details screen was showing a significant amount of data that drivers did not understand or care about. That data has now been moved to the Settings screens section of the app. To see this troubleshooting information, navigate to Settings > Probe > Diagnostics. The same information will display as before.

The Load Properties detail screen (from tapping the Load Properties card) now shows more fields of data that are applicable to what the driver wants to know regarding a load.

Android 5 (Lollipop) is no longer supported with TrackIt Android v14.4.34+. If a user tries to load this version or newer on an Android 5 tablet, the install will fail and give an error about being unable to parse the installer.

Logic was added to turn off the tablet's Wi-Fi when TrackIt identifies that the tablet is connecting to the EDC's wireless connection. This allows the tablet to still use the device's cellular connection and maintain TrackIt's functionality, although engine data will not be available. This prevents previous behaviors in the field where a tablet would connect to the EDC's wireless connection and require the driver to manually forget the network.

The new 30-turn countdown label on the Load Properties card has been relabeled from Revolutions to Remixed to Remixing. This way, it will not run off the edge of the card on smaller screens.

Corrected behavior:

When a value is set for Engine Hours Offset while editing equipment, the value is now sent to ISE eFleetSuite for both DVIR and HOS tracking purposes.

Previous behavior:

When a value is set for Engine Hours Offset while editing equipment, the value was not sent to ISE eFleetSuite.

A counter was added to the Load Properties cart that allows truck drivers to monitor rotation counts when water is added to the truck load via the waterflow meter. When water is added on a load, the Load Properties card displays a Revolutions to Remixed counter that begins tracking rotations needed to reach a fully-mixed state. Once the revolutions has fully counted down from 30, this counter disappears.

When the Probe is malfunctioning, this enhancement forces the TrackIt Load Properties card to display no information. This was done because when the probe is not working right, the data on the card can be misleading. So in order to avoid any inaccurate data, the Load Properties card for Android devices will show nothing.

The Load Properties card will also display a message indicating what problem the Probe is having. This allows the driver to take action to fix the problem or notify the appropriate people to get the Probe repaired.

The TrackIt app now displays a new Probe Setup Screen which allows the Probe installer to enter the required setup information without having to login on the TrackIt Web Console. The setup screen will capture the I/O Box Mac Address, Probe MAC address, Sensor Serial Number, and Flow Meter Volume Per Pulse.

This can be done without logging into the TrackIt Web Console, and one tablet can complete the setup for any vehicle by simply typing in the vehicle number.

Functionality has been added for VisTracks to use Engine Hours Offset from the TrackIt Web Console for ELD.

The GPS Disabled alert has been added to TrackIt's alerts setup. This alert monitors devices and will notify administrators when GPS or Location Services are disabled on a device.

When viewing the Load Properties card, if the Ordered Slump value was not present, it displayed the value of not_available instead of NA. This was caused by some incorrect logic in dealing with the translation file.

From now on, the Ordered Slump field will display NA if no value has been provided for a ticket.

Corrected behavior:

When Custom Event alerts are triggered on the TrackIt Android application, the red bar alert will now properly display on the device screen.

Previous behavior:

When custom engine events were triggered on the TrackIt Android application, the red bar alert was not displaying reliably.

Corrected behavior:

The route a vehicle is following when speeding is viewable from the Speed Alert Breakdown report. Simply select the information icon next to the speeding occurrence, and this will display a map of the GPS fixes that includes the coordinates of the vehicle while it was speeding. This also includes the actual speed of the driver when they started and stopped speeding.

Previous behavior:

When viewing the Speed Alert Breakdown report, the starting and ending records for a speeding occurrence indicated a speed of zero (0). The route of a vehicle was likewise not viewable from the report.

The Load Properties card for COMMANDassurance now displays the current drum rotation speed (RPM) as well as the current rotation count (revolutions).

A new message is now delivered to the probe when a vehicle has received a new ticket. This allows the probe to anticipate a new load and identify what the expected volume is. The probe can then use this to better determine when a load is fully mixed and switch to the Fully Mixed state. This is intended as an additional measure to ensure the probe can gauge a load's mix state and avoid overmixing.

Corrected behavior:

Tablets connecting to an EDC will not encounter a loss of cellular connectivity.

Previous behavior:

Tablets connecting to an EDC's wireless connection occasionally caused the tablet to lose all cellular connectivity. Fixing this required a reboot or re-enabling the network settings on the tablet.

Corrected behavior:

Previously sent and received messages will appear on the Messages screen.

Previous behavior:

In Android v14.4.28, when viewing the Messages screen, previous messages sent and received would not appear on the screen. While drivers could still send messages, they saw the text "No recent messages" on the screen.

A notification bar now displays along the top of the driver tablet when a connection is lost and no data may be retrieved from the TrackIt server. When no connection can be made, a red notification bar appears to indicate the problem.

When a connection is re-established, a green notification bar appears to indicate the successful connection.

This notification is intended to indicate when a connection with TrackIt's servers is or is not available on the device, which ultimately affects the TrackIt Android app's ability to send or receive data. The notification is not indicative of the device's cellular signal quality.

Originally, when drivers sent messages, TrackIt immediately indicated that the message was sent. This did not factor in delays to a message's delivery due to reasons like poor cellular signals. Messages will now display a "Sending..." status until the message has successfully delivered to dispatch.

If the device's Webview or Chrome version is below v54, an error message appears now appears on the device screen. This message instructs the driver to update the Webview or Chrome version to v54+.

For additional information, please view the system requirements for BYOD setups here.

Corrected behavior:

The login screen has been updated to prevent the copyright text from moving to other locations of the screen where it might otherwise block screen text or buttons.

Previous behavior:

When using the TrackIt Android app on smaller tablet screens, the copyright text was pushed up from its set location and appeared on top of the login fields or buttons.

Corrected behavior:

The EDC health check will only report the device's connection as "healthy" if properly connected to the TrackIt Android app.

Previous behavior:

Configurations using the EDC reported a "healthy" connection with the TrackIt Android app even when the device was not connected.

Corrected behavior:

When configuring the TrackIt Android app for use with the EDC, if the firmware version cannot be obtained from the TrackIt server, this will not prevent the configuration process from completing.

Previous behavior:

When configuring the TrackIt Android app for use with the EDC, the app would sometimes fail to retrieve the firmware version. During such occurrences, this prevented users from completing the configuration process with EDC devices.

Corrected behavior:

Driver devices will not connect to the EDC's wireless signal if the infrastructure mode is left on.

Previous behavior:

When upgrading TrackIt Android, an unexpected behavior occurred that would leave infrastructure mode on and allow the tablet to connect to the EDC's wireless signal.

TrackIt will now download the latest EDC firmware to the tablet if no firmware has been downloaded previously. This is intended to help keep BYOD customers updated with the latest EDC firmware application by default.

Webview has been tested and minimum requirements established based on Android OS version. The requirements are as follows:

• Android 6.X: Webview 54+
• Android 7.X: Chrome 58+ (Android 7.0+ uses Chrome, not Webview)
• Android 8.X: Pre-loaded with the necessary version of Chrome

Corrected behavior:

The font size used for status names has been increased to a larger size to accommodate greater ease of reading.

Previous behavior:

The font size used for status names was reduced in TrackIt Android v14.4.18 to a smaller size.

Corrected behavior:

When a driver swaps from one vehicle to another with an EDC configuration, the tablet will update to track the engine diagnostic data for the new truck.

Previous behavior:

When performing a truck swap with an EDC configuration, the TrackIt Android app continued to track engine data for the previous vehicle's EDC instead of the new one.

Additional work was performed to increase EDC reliability when using WiFi Direct. This ensures that data flow between the device and tablet continues to be as accurate and secure as possible.

Corrected behavior:

The logic governing the functionality of the Posted Speed Limit alert has been improved to more accurately identify the road the vehicle is traveling on. This allows TrackIt to always compare the vehicle's current speed to the correct posted speed limit.

Previous behavior:

The logic pertaining to the Posted Speed Limit alert sometimes used the speed limit for a nearby road that the vehicle was not traveling on. This triggered false speeding alerts.

Corrected behavior:

Secure connections between an EDC device and tablet with AT&T cellular service successfully occur without throwing any SSL errors.

Previous behavior:

After attempting a secure connection with an EDC device, SSL errors were returned.

Corrected behavior:

When viewing the Health Check screen on the TrackIt Android app, the mileage shown for the vehicle's odometer will accurately convert to kilometers or miles depending on the company's settings.

Previous behavior:

The vehicle mileage shown on the Health Check screen of the TrackIt Android app inaccurately converted mileage between kilometers and miles.

Corrected behavior:

The TrackIt Android app accurately determines whether the connection with the EDC device is a wireless or cellular network and correctly configures the connection for device communication.

Previous behavior:

When connecting to the EDC, the TrackIt Android app would misinterpret the wireless signal as a cellular connection. As a result, the devices would not successfully connect.

In an effort to more reliably determine the ignition state in vehicles, the Ignition Status Switch is now included in the logic for the ignition state web service call to the EDC. This enhancement is also meant to aid communication with eFleetSuite and prevent missed odometer readings that occur when TrackIt Android has not properly determined the vehicle's ignition state.

The Health Check in Wifi Direct has been enhanced to compile information from all possible connection points with the EDC and return appropriate messages to TrackIt Android.

Additional logic was implemented to assist with automatically troubleshooting connectivity problems with the EDC device. If the hardware cannot connect or send engine data, the new behavior prompts the device to automatically reboot. Upon successfully booting, the EDC attempts once more to establish a connection.

Corrected behavior:

The refresh time of the screen in the TrackIt Android application was changed to a five second interval to enable the application with an EDC and ED configuration to properly display Engine Hours on the Engine Data screen.

Previous behavior:

Sometimes, in vehicles with an EDC and ED configuration, the engine data would not display Engine Hours on the Engine Data screen in the TrackIt Android application even though all the engine data was being properly reported in the TrackIt Web Console. This would most often happen while drivers were initially configuring an EDC with a device and the TrackIt Web Console.

Corrected behavior:

The EDC now checks for the need to upgrade it's firmware more than once to prevent a login from interrupting the configuration process.

Previous behavior:

Logging into TrackIt Android caused EDC configuration to stop.

Corrected behavior:

Failed firmware updates will not prompt a wireless connection with EDC devices or affect cellular data to the tablet.

Previous behavior:

When a failed firmware update was encountered, the driver's tablet would connect to the EDC via wireless and then shut off all cellular data to the tablet.

Corrected behavior:

In the TrackIt Android app, when an EDC device is disconnected, it will disappear from the Select Device screen. This list of accessible devices is updated every 20 seconds.

Previous behavior:

When an EDC was disconnected, the EDC did not disappear from the Select Device screen in the TrackIt Android application.

Improved support now exists for using the TrackIt Android app in portrait mode. While it could be used previously, some screens and features did not function or display correctly. Screen display optimization allows for consistent layout, reliable user experience, and reduced performance incidents.

To assist with encouraging safe driving habits, a new alert is available to combat driver speeding. Each time a vehicle exceeds the posted speed by a predefined amount, this may trigger a Posted Speed Limit alert.

When a driver exceeds the posted speed limit and the alert's threshold, drivers will see a message at the bottom of their screen. It disappears only when the vehicle decelerates to below the posted speed limit.

TrackIt Android now supports Android 8.0+ operating systems. This improves TrackIt performance and ensures compatibility with the latest system features.

After configuring an EDC device with your tablet, a new card displays with engine data to verify a successful connection with the device. This data consists of odometer readings and engine hours. If the connection between tablet and EDC was not successful, these fields will not populate with data values.

To view engine data for a configured EDC, navigate to Settings > Devices and then tap on the desired EDC. This will display a screen divided into two cards, one with the EDC's information and a CONFIGURE button, and the other with any detected engine data to verify the connection.

Dispatchers and fleet managers need to know when and how long speed violations occur with a driver. As part of the new Speed Alert Breakdown report, both the start and end times of speeding incidents are recorded. This information is used to identify chronic speeding and separate shorter occurrences from more prolonged and problem behaviors.

The TrackIt server uses speed data only from GPS fixes rather than engine readings for the purposes of Posted Speed Limit alerts. This is done to avoid inaccurate readouts caused by delays in data reporting from vehicle engine data controllers (EDCs) or on-board computers (OBCs).

This ultimately impacts when speed violation alerts display on the device's screen.

Corrected behavior:

TrackIt Android is considered a "foreground service" and reports GPS fixes regularly, even if the tablet is focused on another application or service.

Previous behavior:

Devices using Android 8.0+ encountered an operating system behavior that would constrain GPS fixes to report only once every 10 minutes while the TrackIt Android app was not running in the foreground. For example, when a driver used a navigation app or ISE eFleetSuite, TrackIt would only report the vehicle's GPS fix in 10-minute intervals rather than the usual one-minute interval.

Corrected behavior:

When running an Engine Events report, each reported occurrence is only recorded and reported once.

Previous behavior:

When some companies ran an Engine Events report, duplicate entries appeared on the generated results. This was caused when engine events intermittently reported twice to TrackIt, even though a single event had occurred.

Corrected behavior:

The Phone ID field is now labeled as the TRACKIT DEVICE ID and allows users to pick between data types to register the device. When registering a new tablet device with the TrackIt Android app, device users may choose from radio button options to use the device's associated Phone #, IMEI #, or the Other data type.

When the phone or IMEI options are selected, TrackIt auto-populates the field with the associated values detected for the device. The Other option allows users to manually enter a different desired value.

Previous behavior:

When an administrator attempted to register a new tablet device with the TrackIt Android app, the device's phone number or IMEI number was automatically detected and populated into the Phone ID field. However, the data pulled to this field was not always the desired type.

Corrected behavior:

When drivers enter a status with the Returning Navigation card, the map automatically centers on the destination location's pin.

Previous behavior:

As a driver entered a status for returning to their plant, the Return Navigation card appeared on the tablet, but the map wasn't centering on the destination. Instead, it displayed a different geographic location and required the driver to tap the Recenter Map button to focus on the destination's pin.

Corrected behavior:

When GPS speed is reported with a triggered custom engine event, the value is accurate and consistent with all other reported GPS speeds.

Previous behavior:

When a custom engine event was triggered, the GPS speed reported with the custom event was different from the GPS speed actually recorded. Any other GPS speeds reported were accurate, yet the speed sent with the engine event recorded a different value.

Corrected behavior:

When GPS speed is reported with a triggered custom engine event, the value is accurate and consistent with all other reported GPS speeds.

Previous behavior:

When a custom engine event was triggered, the GPS speed reported with the custom event was different from the GPS speed actually recorded. Any other GPS speeds reported were accurate, yet the speed sent with the engine event recorded a different value.

Improved support now exists for using the TrackIt Android app in portrait mode. While it could be used previously, some screens and features did not function or display correctly. Screen display optimization allows for consistent layout, reliable user experience, and reduced performance incidents.

To assist with encouraging safe driving habits, a new alert is available to combat driver speeding. Each time a vehicle exceeds the posted speed by a predefined amount, this may trigger a Posted Speed Limit alert.

When a driver exceeds the posted speed limit and the alert's threshold, drivers will see a message at the bottom of their screen. It disappears only when the vehicle decelerates to below the posted speed limit.

TrackIt Android now supports Android 8.0+ operating systems. This improves TrackIt performance and ensures compatibility with the latest system features.

After configuring an EDC device with your tablet, a new card displays with engine data to verify a successful connection with the device. This data consists of odometer readings and engine hours. If the connection between tablet and EDC was not successful, these fields will not populate with data values.

To view engine data for a configured EDC, navigate to Settings > Devices and then tap on the desired EDC. This will display a screen divided into two cards, one with the EDC's information and a CONFIGURE button, and the other with any detected engine data to verify the connection.

Corrected behavior:

TrackIt Android is considered a "foreground service" and reports GPS fixes regularly, even if the tablet is focused on another application or service.

Previous behavior:

Devices using Android 8.0+ encountered an operating system behavior that would constrain GPS fixes to report only once every 10 minutes while the TrackIt Android app was not running in the foreground. For example, when a driver used a navigation app or ISE eFleetSuite, TrackIt would only report the vehicle's GPS fix in 10-minute intervals rather than the usual one-minute interval.

Corrected behavior:

When running an Engine Events report, each reported occurrence is only recorded and reported once.

Previous behavior:

When some companies ran an Engine Events report, duplicate entries appeared on the generated results. This was caused when engine events intermittently reported twice to TrackIt, even though a single event had occurred.

Corrected behavior:

The Phone ID field is now labeled as the TRACKIT DEVICE ID and allows users to pick between data types to register the device. When registering a new tablet device with the TrackIt Android app, device users may choose from radio button options to use the device's associated Phone #, IMEI #, or the Other data type.

When the phone or IMEI options are selected, TrackIt auto-populates the field with the associated values detected for the device. The Other option allows users to manually enter a different desired value.

Previous behavior:

When an administrator attempted to register a new tablet device with the TrackIt Android app, the device's phone number or IMEI number was automatically detected and populated into the Phone ID field. However, the data pulled to this field was not always the desired type.

Corrected behavior:

When drivers enter a status with the Returning Navigation card, the map automatically centers on the destination location's pin.

Previous behavior:

As a driver entered a status for returning to their plant, the Return Navigation card appeared on the tablet, but the map wasn't centering on the destination. Instead, it displayed a different geographic location and required the driver to tap the Recenter Map button to focus on the destination's pin.

Third-party applications on a driver's tablet may now request the vehicle number of the logged-in user via the TrackIt Android app. The inclusion of a new intent API on TrackIt Android facilitates external requests and returns for truck numbers. This is intended to ensure consistency between application services used by your company and reduce the risk of entering an incorrect truck number.

A previously-implemented enhancement added TrackIt to the list of "Home" launcher apps in Android settings. For some mobile device management (MDM) systems, this caused configuration issues. Due to such reported problems, this feature is now removed and TrackIt will not show up as a Home screen app option in Android.

Corrected behavior:

When the TrackIt Android app can't connect to the TrackIt server, the following message displays: Cannot connect to TrackIt.

This message will appear whenever the tablet lacks a cellular connection, or for any other reason that prevents the app from communicating with the TrackIt server.

Previous behavior:

When the TrackIt Android app couldn't connect to the TrackIt server, drivers received the following inaccurate error message: Couldn’t connect to any Wifi hotspot. Please turn your device off and then on (not reboot).

This message caused significant confusion for companies using cellular-enabled tablets rather than an OBC hotspot and wireless-only tablet setup.

Corrected behavior:

All cards in TrackIt Android that contain a map display properly.

Previous behavior:

When using the TrackIt Android app, some users found they could not view any cards containing a map. In these instances, the map itself appeared as blank even when the driver tapped the card and brought up GPS navigation.

Corrected behavior:

If the default navigation app set from the TrackIt Web Console is unavailable on a device, an error appears.

Previous behavior:

When attempting to use the server-defined default navigation app, some device users experienced errors indicating that the application could not load. However, this error occurred under the wrong conditions, as these devices had the server-designated app correctly installed.