[REQUEST] Correct working of MIN and MAX Value recognition in some situations #174

Is your feature request related to a problem? Please describe.
Two features.

1 - Can't get AATorque working in background in the head unit. At the moment i'm using AATorque via AAwireless with developer mode. When i select the AATorque app in head unit, it works in "real time". But when, in example, i switch to Waze app or Spotify app, AATorque stops the data recording.
Example: I set the MAX value indicator in RPM. Suppose i'm cruising at costant 2000RPM with AATorque opened. But if i switch to Waze, and then accelerate to 4000RPM, when i return to AATorque he keeps showing 2000RPM as MAX RPM value.

2 - I would see the correct MINIMUM value in the AFR (c) and AFR (m) PIDs. The problem is: when i open AATorque for just one second it shows "00,0", then receives the value from TorquePro and shows the correct value (14,7). But the MIN Value keeps stucked as "00,0" because it remembers of that value showed at start.

Describe the solution you'd like

1 - I would like the app keeps recording data also if isn't the main app showed (like when i'm using Waze, or Spotify).

2 - I would like the app had a button that "restarts" the MIN / MAX Values recognition. So i can start the value recognition when TorquePro is completely operative.

Describe alternatives you've considered

Additional context

Thanks in advance