what I forgot to write, the Bluetooth works and the connection is stable, I tried a few other diagnostic apps to test, everything works fine.
unfortunately not with Torque at the moment.

it is the current 1.12.32. all permissions are allowed, nothing else is coupled with the MC+ adapter. As I said, the constellation is exactly the same as before the major update

How can I do that? The one from the playstote is on 12.1.32

Thanks, I’ll test the new version later and report back here

Thanks for the reply!!!!!

These are the gauges that stay frozen at >512

The complete names are:

Miles Per Gallon(instant)
Miles Per Gallon(Long Term Average)
Fuel Remaining(calculated from vehicle profile)

Also, any luck in changing the Fuel Remaining % to Gallons Remaining?

Hi!

Can you do the following:

Make sure you’re on the latest version (1.12.46 or .48) released today

Re-select the bluetooth adapter in the settings (even if its already selected, unselect it and reselect it)

Go into the settings->special settings->enable debugging

Quit and restart the app

Let Torque try to connect to the adapter for about 60 seconds -if it hasn’t connected in that time (and there are no other apps connected to the adapter as this will block the connection) then go to the ‘realtime information’ screen (without quitting Torque) and press the gear icon/menu->send debugging information.

Write your forum name in there(so I can find the debug) and then press send which will send me the debugging information. let me know here and then I’ll know to look at the debug when you’ve sent it

The adapters only allow one connection at a time so if another app is still connected, it will block Torque from being able to connect

Hello, I have now followed your instructions and done everything, but I was unsuccessful. I have now sent the debugging information with the nickname Panter. I hope you can solve it.

That’s going in the changelog when I’ve done it as exactly that

Panter:
1644062683124 *** class java.lang.SecurityException:UID 10431 / PID 9057 lacks permissions ***

You need to give the app nearby devices/bluetooth permission (basically all the permissions it asks for) it hasn’t got one or more permissions which is why it can’t connect

Android will only let the app ask for permissions twice and then will ignore any further requests by the app for permissions – at that point you’ll need to go into the android settings->app settings to allow permissions

Hi!

Thanks – that means it the issue can only be broken permissions on that handset (your device vendor has broken something)

Good news is that I may be able to workaround it (it may require 2 attmepts, this is the first).

There will be version 1.12.56 on Google Play Beta (once Google have approved it) – this version has the workaround that might get you up and running

Please try it when google make it available (should be about an hour) and let me know if it worked or didn’t work – if it didn’t work another debug would be extremely helpful! Thanks!

Thank you very much, now everything is working fine again as usual. the last update fixed everything