I got .76 today and I am unable to connect at all. I’m assuming that’s what you are working on in .77? I did send you a debug.

Quote from Steffe2 on February 14, 2022
Just got .77. Going to test it tomorrow and see if it connects properly.
As the last week or so, it has had problems connecting to the car, forcing removal of the device and restarting BT-pairing.
Before that, it worked properly as long as I weren’t too far from the car when unlocking (which I guess wakes the device).

Answering myself, first start today worked flawlessly (fastest connection so far). Testing again in about 9h, after work

bibubip84: You’ll probably want to update to .78 for some additional fixes

Re: the slow update – There is now an automatic refresh applied to PIDs (so if the PID does not change in value, then it doesn’t get refreshed as often (to a lower limit) and this allows other PIDs whose values are changing to get faster updates. As soon as it changes, it will immediately be polled fast again

Wow. It’s very cool and useful feature! I noticed display pulse changes depend of changing incoming data, i used to think it was a bug or my eyes problem

Hi!

jermydean: Apologies – I have your debug, thanks. I had missed the AUTO use of headers from my test (it’s now fixed in the .79 update). I’m hopeful that this is now most of the issues caused by the major changes in the beta, fixed

The changes improve several parts of the adapter handling (and fix 2 long standing issues) so we’re now in a bugfix phase where everything will now be made stable and I won’t need to touch the OBD code now for a while (except for minor bugs now)

Just got .79. New refresh algorithm works smooth and steady. No issues yet.

Hi

Unfortunately because I have not seen original connection issues you were experiencing on the multitude of adapters and devices I have here. This means that if there is an issue, it might not have shown up in testing here beforehand

However, if you do have a problem, and report it (with a debug now that is added) I can usually see what is going on and fix it (or at least take an educated guess where the issue is, or improve that area in an attempt to workaround an OS bug, Adapter issue, or fix an app bug)

It is not my intention to ever release a version which has issues, though, and rely on feedback from people who have a multitude of different ECU/vehicle/Adapter/Phone configurations to shout if there is an issue in a beta before it gets to full release (If there was only one signalling standard for OBD2, and Android didn’t have historically so many bluetooth bugs in various manufacturer’s handsets, and every adapter worked properly then the testing would be simple to do – as it happens I have 10 protocols * 3 different main ECU configurations vehicles can have * about 5 adapters (one type works flawlessly, and the other 4 are varying degrees of broken). All of which makes for a complicated testing regime)

One of the biggest (required) changes was moving to support Android 12 which was required by Google Play (which affected all the public/shared app storage for every developer if they made use of it)

Fortunately though I am nearing the end of all the OBD changes which significantly improve the app in terms of dealing with problematic adapters and more efficiently getting data from the ECU – I’m just waiting for feedback now all the main changes are done and catching any small bugs in the beta before the next main update.

Probably a silly question, but how do I get the beta?

i try to use onOBDConnected function in script. Seems doesn’t work.

For test i wrote

onOBDConnected = function() {
logInfo(“test”);
};

No “test” in script log on connected to obd and ecu, or am i doing something wrong?

Hi!

redfoxy – thanks for the feedback!

bibubip84 – you’re not doing anything wrong – you’ll want the .81 update which will be out tomorrow where that’s all linked together now (there was an issue with speed and that method slowing things down and causing issues) – it’s all fixed in .81 and the upshot is that if you now have a script that pops up something like a blocking message or sleep(forever) that it should no longer slow things down or cause issues for other scripts

Small note: the onSensorRead function can get called a *lot* of times quickly (basically for every sensor) – if you don’t need it then don’t define the method (so the app will skip calling it and optimises)