As I currently understand the Toyota TPMS on Torque app situation, the existing incompatibility can be distilled to bluetooth obd adapter selection.
More specifically, most available adapters - including mine - use cloned ELM327 chips that in some (read Toyota) cases can't access a subset of the ISO14230-4 (KWP2000) protocol data due to a bus initiation error caused by limited timing settings. Apparently, later versions of genuine ELM327 chips were updated to handle additional ISO14230 baud rates and initiation (first in v1.4 firmware which certainly predated the original post, then further in v2.0), whereas clones are stuck on older, pirated firmware ("v1.5" which was never an ELM Electronics version number, and is actually based on ELM327 v1.0). Unfortunately, genuine chip adapters are more expensive, and not readily available - particularly from US-based retail sources.
[Aside: The latest ELM327 firmware is v2.2. One can check the version number of an adapter's firmware using Torque by selecting "Adapter Status" on the start screen and scrolling to "Adapter Version", but bear in mind some "v1.5" clones supposedly spoof v2.1.]
Furthermore, there is another set of adapters that utilize a different chip based on the STN11xx architechure. These chips support the ELM327 command set, in addition to being faster, more secure, and allowing post-manufacture, user-initiated firmware upgrades. Scantool's bluetooth OBDLink adapters use STN11xx chips. At present, the Scantool firmware also exhibits the bus initiation timing error, but Scantool has promised an imminent firmware update to resolve it (they claim an ELM327 v2.0 timing solution is already in their unreleased source code).
So, options I know of for making Toyota TPMS work on Torque are: either procuring a recent, genuine ELM327 chip-based, bluetooth obd adapter now (probably from Romania); or purchasing a Scantool OBDLink bluetooth adapter if and when the firmware for the various models is upgraded with the relevant code. Then, the appropriate PID settings must be decoded - fortunately the Scanguage (not to be confused with the aforementioned Scantool) people appear to have already completed much of that work, see
https://www.scangauge.com/x-gauge-commands/toyota-lexus-scion-tpms/.
At least, I hope the above information is functionally correct. If it is, a ~$50 bluetooth adapter will eliminate the need for a Scanguage, thereby saving the associated extra expense, wire routing, and mounting of a low-resolution, additional display.
