Voters 1
1
Wrong Live SOC With ODB BTLE
- Done
 |
Andrew Van Til |
I recently upgraded to Premium to try out live data integration on a road trip. Among the issues we encountered the SOC displayed in the app was wildly wrong at times (see photo). When I was able to look at the data directly (via Car Scanner) the number was right (i.e. what I see in the car's display), ABRP was just wrong. Dongle is an ODBLink CX.
Activity Newest / Oldest
Samuel_ABRP
Status changed to: Done
Samuel_ABRP
Things fixed so far:
- background gps on Samsung (mentioned somewhere below)
- disabled battery optimization
Andrew, as this issue was originally opened for OBD issues can we close this as it seems to work now? If there is anything else left you can just open new issues, feel free to open as many as you want (but hopefully don't need ;)).
Andrew Van Til
Works for me. Should I open a request for the bug icon not displaying in AA? It would be much easier to provide the logs if it was present there. I can't always fiddle with the phone while driving.
Samuel_ABRP
Please try that again with 4.2.10 as i changed the init sequence a little, if it does not show up with that version you can open a report.
Samuel_ABRP
Btw which phone do you use. Some seem to have problems when AA is running without the app being active on the phone. Maybe this has an effect on BT as well.
Andrew Van Til
Samsung S21 Ultra
Samuel_ABRP
So from what I understood is that this does not happen as long as the phone is active? Could you please just leave the screen on (stays automatically on when navigating in ABRP) and check if the soc is correct then?
Andrew Van Til
Last night I observed that the SOC % displayed in AA corrected when I picked up the phone and launched the app. I didn't do enough testing to see what happened if I drove around with it on/active or off/inactive.
Samuel_ABRP
Ok please check it on your next trip and let me know if that works. Maybe we also need some special background BT logic for some phones.
Samuel_ABRP
Status changed to: In progress
Samuel_ABRP
Hi,
Live data is unrelated to premium, you can also use it in the free version.
Which car is it, that you are trying to connect to? Did You verify that the connection worked before (did it show the values on the car detail page?).
Andrew Van Til
Sorry, I should have been clearer. I upgraded to Premium so I could use ABRP with live data via Android Auto on our road trip. Yes, the BTLE connection was valid. I believe the image also indicates this with the BT icon, when I didn't establish a connection (or it wasn't working properly*) this was a red mobile data icon.
* in one case I had to force stop ABRP on the phone to get it to connect to the BTLE dongle about an hour after it connected properly.
The car is a Ford Mach-E. It did work at times, it wasn't always wrong. Sometimes it would be fine at the beginning, then drift wrong. Other times it would be fine the whole time. Others, wildly off like what is displayed here. I have more photos of it not working if that would be useful.
Samuel_ABRP
No, what would be more helpful is a bug report, as soon as this happens. We can either provide you the tester role, then a bug report button appears on AA and you can quickly report if the connection drifts away again and we can have a look at the reported data, or if this happens quite often anyways and is easy to reproduce, you can also just report a bug in settings -> contact & feedback -> report bug, click yes when it asks to send logging data and send the mail that is generated to samuel@iternio.com. It's up to you, which do you prefer?
Samuel_ABRP
Forgot to mention... the bug report needs to be done immediately when you see the problem, else the logging is cleared.
Andrew Van Til
Which can I do from the AA app? It would be inconvenient to stop driving to report bugs, and unsafe to pull out my phone to do it while driving.
On second thought, maybe the tester role would be better. I noticed (and had my passenger photograph) several issues that we encountered (unresponsive app, map disappearing, duplicate navigation lines, loss of state when switching apps, etc) on the trip. I'm happy to report them when they pop as long as I can do so in a safe/convenient way.
Samuel_ABRP
Thats definitely the one with the tester role, its more or less two clicks on the AA interface. Please send me a mail to samuel@iternio.com with your account mail so i can add it and provide instructions.
Andrew Van Til
Emailed. Will also have a look on our EV6 to see if I can reproduce.
Robby Van Mieghem
Can I also have the tester role ? Since my SOC value is also not ok . Car was charged to 80% this morning, showed that one on my dash also, abrp says its 82% for example. Also I tried the API integration and at first it was showing correct values from my bmw... But this morning I used abrp via carplay, and saw the value was not updated. If I close the app and reopen, it is. I drive a bmw i4 m50 & using carplay & Vgate vLinker MC+
Samuel_ABRP
BMW i4 is not supported yet via OBD. Please open your own issue, I think this is not related.
Robby Van Mieghem
done
Andrew Van Til
This is similar to what I see in our Kia EV6 (did a little testing last night). AA version of ABRP shows a number (generally a few % higher than actual) until I open the ABRP app on the phone, then it gets the right value. I didn't get a chance to drive around long enough to see if it stays in sync from that point on wards.