I didn’t see TorqueScan mentioned in the changelog. I hope that in the next version the TorqueScan results can be saved or sent via email.

Thank you.

Quote from admin on November 28, 2017
Changes in 1.10.112 (Current beta, November 2019)
===========================
* Fix issue with fault log theme
* Updates to distance to empty calculation
* Improvements to Trip View activity to replace a missing function
* USB has been updated to be more ‘plug and play’
* Fix a couple of theme issues with black text on a dark background
* All displays updated to show ‘not ready’ when the ECU reports a sensor is not ready
* Fix a problem in logging
* Fix Infinity ‘max’ in Trip View

Changes in 1.10.107
=================
* Fix for trip uploading not uploading user units if a ‘%’ was one of the units
* New trips website (part of the app update due to changes also needed in the app) – maps fixed, graphs work with user added and app added sensors, faster server. ‘id’ login will be retired at this point in favour of email based user logins (the ID system isn’t as secure), plus use of SSL.
* Rewrite of permissions requests (API changes required in Android 9 onwards)
* Updated launcher icon that follows googles new ‘adaptive icons’ gudelines
* Updates for API26+ handling for third party plugins
* Improvements to rendering speed of gauges and also small bugfix causing rendering speed to slow down on some ART configurations
# Due to the way in Android O+ limits background services, third party PID plugins will need to update to take this into account on newer platforms – mainly any AIDL service should be started with startForegroundService where possible (I will release an updated example plugin in a couple of days with the relevant changes)
* Refreshed trips activity to use the new google maps API

Changes in current version
=======================

* Small bugfix in profile loading seen on some devices
* Change for Google API updates in the Google Play Developer console

Changes in 1.8.202
================
* Workaround for small issue in older android 6 handsets due to OS bug
* Improve the Vechicle profile screen a bit so it is easier to parse
* Can override fuel level pid
* Improved poll rate for user defined PIDs
* Fix a theme issue with dials using the long pid format (0x7ffffffe)

Changes in 1.8.199
===============================
* Fixed issue saving fault code lists
* Added Android device battery level pid
* Added link to PID editor from dashboard screen in display configuration when the display is linked to a user created PID
* J1939 support for large vehicles (Busses, Boats, Plant equipment, etc) – Select the protocol from the vehicle profile settings to use it
* Update to fix some non-obd compliant nissan ECUs as well as others ECUs that may cause to report \’No PIDs available\’
* Totaliser (and averaging, etc) equations now have the ability to save their \’learned\’ data as part of the PID definition
* Fix difficult to reproduce hang in profile activity when exiting and the handset has a problematic bluetooth driver
* Added IEEE-754 float functions – 4 byte FLOAT32(A:B:C:D) and 8 byte FLOAT64(A:B:C:D:E:F:G:H)
* Added 16 & 32bit unsigned int function – INT16(A:B) and INT32(A:B:C:D) – INT16(A:B) can be used in place of (A*255)+B
* {A:1} bitwise operator notation deprecated and replaced with BIT(A:1) function
* PID editor now keeps the screen on when editing (and more importantly, when using the the ‘test’ button)
* Added LOOKUP() and CLOSEST() functions (documentation to appear in wiki shortly)
* Fixed a crash in the graphing activity when used with android versions less than 3
* Added INT24(A:B:C) function (in next beta update)
* Update tile server with fresh maps (map widget)
* Scale map widget graphic up on high dpi handsets
* Fix temperature notification message not resetting
* Fix ANR when power-disconnected received (in-dashboard settings)
* Change to point at new theme server
* Add support for generic BLE serial connections
* Add new extended information activity to adapter information screen
* Fix a centering problem with text on a few screens
* Added MAX(x:y) and MIN(x:y) functions. Max returns the greater of x or y, and min returns the smaller of x or y
* Fix titles in O2 graph display showing wrong title (stuck on sensor one) when in fact it was showing a different sensor
* Update the ‘choose bluetooth device’ dialog to be more intuitive and easier to see when you have a lot of bluetooth devices paired (or BLE devices in range)
* Equation editor no longer shows the error popup over the currently editing area if the equation is multi-line
* ‘Add Display’ menu now uses more decimal places for some PIDs(sensors) when previewing to avoid rounding
* Updated status icons in starting screen
* Add drag coefficient to vehicle profile settings (advanced)
* Add vehicle ‘type’ to vehicle profile settings
* Add different icons for trucks, minivans, bikes, boats, plant, etc
* Update adapter benchmark activity with new options and graphs
* Fix a timeout issue with the new BLE code
* UI updates to the vehicle profile

Changes in 1.8.178
=================
* Updated bluetooth adapter selection process to prevent a hang
* Fix for hang on screen resume
* Workaround for KiwiBLE device scan hanging in the app settings on some devices
* Trip reset no longer resets long term mpg average
* Fix Twitter logging support
* Fix issue where app would incorrectly warn no bluetooth device was paired when a WiFi, USB, or TTY device was being used
* No longer allows auto scanning for dtcs when using the Ford bugged ECU workaround option in the settings to prevent triggering the ECU bug in a small number of year 2001 F1/250s
* Added M3D ECU extended PIDs to PID editor

Quote from admin on November 28, 2017
Changes in 1.10.112 (Current beta, November 2019)
===========================
* Fix issue with fault log theme
* Updates to distance to empty calculation
* Improvements to Trip View activity to replace a missing function
* USB has been updated to be more ‘plug and play’
* Fix a couple of theme issues with black text on a dark background
* All displays updated to show ‘not ready’ when the ECU reports a sensor is not ready
* Fix a problem in logging
* Fix Infinity ‘max’ in Trip View

Changes in 1.10.107
=================
* Fix for trip uploading not uploading user units if a ‘%’ was one of the units
* New trips website (part of the app update due to changes also needed in the app) – maps fixed, graphs work with user added and app added sensors, faster server. ‘id’ login will be retired at this point in favour of email based user logins (the ID system isn’t as secure), plus use of SSL.
* Rewrite of permissions requests (API changes required in Android 9 onwards)
* Updated launcher icon that follows googles new ‘adaptive icons’ gudelines
* Updates for API26+ handling for third party plugins
* Improvements to rendering speed of gauges and also small bugfix causing rendering speed to slow down on some ART configurations
# Due to the way in Android O+ limits background services, third party PID plugins will need to update to take this into account on newer platforms – mainly any AIDL service should be started with startForegroundService where possible (I will release an updated example plugin in a couple of days with the relevant changes)
* Refreshed trips activity to use the new google maps API

Changes in current version
=======================

* Small bugfix in profile loading seen on some devices
* Change for Google API updates in the Google Play Developer console

Changes in 1.8.202
================
* Workaround for small issue in older android 6 handsets due to OS bug
* Improve the Vechicle profile screen a bit so it is easier to parse
* Can override fuel level pid
* Improved poll rate for user defined PIDs
* Fix a theme issue with dials using the long pid format (0x7ffffffe)

Changes in 1.8.199
===============================
* Fixed issue saving fault code lists
* Added Android device battery level pid
* Added link to PID editor from dashboard screen in display configuration when the display is linked to a user created PID
* J1939 support for large vehicles (Busses, Boats, Plant equipment, etc) – Select the protocol from the vehicle profile settings to use it
* Update to fix some non-obd compliant nissan ECUs as well as others ECUs that may cause to report \’No PIDs available\’
* Totaliser (and averaging, etc) equations now have the ability to save their \’learned\’ data as part of the PID definition
* Fix difficult to reproduce hang in profile activity when exiting and the handset has a problematic bluetooth driver
* Added IEEE-754 float functions – 4 byte FLOAT32(A:B:C:D) and 8 byte FLOAT64(A:B:C:D:E:F:G:H)
* Added 16 & 32bit unsigned int function – INT16(A:B) and INT32(A:B:C:D) – INT16(A:B) can be used in place of (A*255)+B
* {A:1} bitwise operator notation deprecated and replaced with BIT(A:1) function
* PID editor now keeps the screen on when editing (and more importantly, when using the the ‘test’ button)
* Added LOOKUP() and CLOSEST() functions (documentation to appear in wiki shortly)
* Fixed a crash in the graphing activity when used with android versions less than 3
* Added INT24(A:B:C) function (in next beta update)
* Update tile server with fresh maps (map widget)
* Scale map widget graphic up on high dpi handsets
* Fix temperature notification message not resetting
* Fix ANR when power-disconnected received (in-dashboard settings)
* Change to point at new theme server
* Add support for generic BLE serial connections
* Add new extended information activity to adapter information screen
* Fix a centering problem with text on a few screens
* Added MAX(x:y) and MIN(x:y) functions. Max returns the greater of x or y, and min returns the smaller of x or y
* Fix titles in O2 graph display showing wrong title (stuck on sensor one) when in fact it was showing a different sensor
* Update the ‘choose bluetooth device’ dialog to be more intuitive and easier to see when you have a lot of bluetooth devices paired (or BLE devices in range)
* Equation editor no longer shows the error popup over the currently editing area if the equation is multi-line
* ‘Add Display’ menu now uses more decimal places for some PIDs(sensors) when previewing to avoid rounding
* Updated status icons in starting screen
* Add drag coefficient to vehicle profile settings (advanced)
* Add vehicle ‘type’ to vehicle profile settings
* Add different icons for trucks, minivans, bikes, boats, plant, etc
* Update adapter benchmark activity with new options and graphs
* Fix a timeout issue with the new BLE code
* UI updates to the vehicle profile

Changes in 1.8.178
=================
* Updated bluetooth adapter selection process to prevent a hang
* Fix for hang on screen resume
* Workaround for KiwiBLE device scan hanging in the app settings on some devices
* Trip reset no longer resets long term mpg average
* Fix Twitter logging support
* Fix issue where app would incorrectly warn no bluetooth device was paired when a WiFi, USB, or TTY device was being used
* No longer allows auto scanning for dtcs when using the Ford bugged ECU workaround option in the settings to prevent triggering the ECU bug in a small number of year 2001 F1/250s
* Added M3D ECU extended PIDs to PID editor

Hi
Phone just done a software update to Android 10 and app no
Longer supported?
Will this ever be fixed?

Quote from cintakc on December 4, 2017
It’s bad that you deleted the list of changes made earlier,
I often turned to him to remember all the possibilities of the program

Quote from Martinrick1976 on September 18, 2018

Quote from Fabarker on August 27, 2018
How do update my pro version to the latest ver
.?

Buenas tardes como hago para actualizar el sotware

Hi, no updates or communication that I can find for almost a year now. Is this still being developed and supported?

Just a heads up, the 1.8.52 version of the apk works on android 11. After lots of digging I started trying older versions on aptoide. I can confirm it does not force close on android 11.

My current Torque Pro version on kindle fire HD 8 7th gen is 1.10.120.
Dont see the change list for this in the thread.
If not maintained here, pls post link to changelog

The map view bug is doing my head in, when viewing logged data in the app the route is incorrectly over layed on the map, when is this going to get fixed? its been an issue for a long time and there is no excuse as to why its not been fixed, the developer knows about it and chooses to do nothing, they popped up when android 11 was released and updated the app, asked about any problems then total silence, even joined the beta program thinking development was going to start,big mistake, think will leave the beta program so my one star review will show in play store, not impressed at all.
This app might as well be Abandonware