Open DevelLevel opened 1 year ago
DevelLevel
commented
1 year ago (Accidentally closed the issue...) HCI Snoop log files from the android device trying to connect: Bluetooth_starting.log Car_Scanner-working.log AndrOBD-not_working-with_ATZ.log AndrOBD-not_working-without_ATZ.log
fr3ts0n
commented
1 year ago I do have a similar / equal adapter available (also reports ELM V1.5), but unfortunately I can not reproduce the problem with this.
The only obvious thing I could find in the HCI Snoop files is some difference in the signal timing:
There is a chance that the adapter needs some preparation time when it can not take any command too early after connection is established. I will create a test version which includes a delay like this ...
fr3ts0n
commented
1 year ago Test version V2.6.4 is available here: https://t.me/AndrOBD_dev/251
DevelLevel
commented
1 year ago Test version V2.6.4 is available here: https://t.me/AndrOBD_dev/251
Thanks for the update, unfortunately it does not seem to work. Maybe even worse? (The adapter does not return "ELM327 v1.5") Here are some new HCI Snoop logs if they might help: AndrOBD_2.6.4-not_working-with_ATZ.log AndrOBD_2.6.4-not_working-without_ATZ.log Car_Scanner-working(2).log Torque-working.log
I haven't worked with Snoop logs before but from what I can see there seems to be a differences between AndrOBD and CS/TQ. The frame the phone sends right after the adapter responds with "ELM327" includes ATE0. (Frame 191 in Torque-working.log & 286 in Car_Scanner-working(2).log) Car Scanner even seems to be sending ATE0 before receiving the "ELM327" response... (Frame 282 in Car_Scanner-working(2).log) Could this have something to do with it?
fr3ts0n
commented
1 year ago You can.open hci logs with wireshark for Analysis.We are much earlier than sending ATE command. It seems to happen before the First command is sent.
Describe the bug
After connecting to the adapter in Android Bluetooth settings successfully and pressing on connect in the top right corner of AndrOBD a toast comes up saying something like "Connected to OBD II", instantly followed by another toast saying something like "Device disconnected". This is the same behavior as in issue 64, though it can't be resolved with disabling the ATZ command...
To Reproduce
Steps to reproduce the behavior:
Expected behavior
AndrOBD Debug log files
Log without the ATZ command disabled
Log when disabling various commands such as ATZ
Log detail level
INFO/FINER
Important details on your environment:
Tested on
Additional context
The adapter seems to be a
v2.1v1.5 clonethat after my research seems to be capable of BLE, which could be a problem if it is not backward compatible?It was bought on CDON. But the seller does not provide a lot of information.The device is though very similar to this one which specifies that "make sure to select in settings, "Connection type": Bluetooth 4.0 (LE)".As mentioned by @fr3ts0n in the telegram group this might require a "BLE specific comms module". I am thinking a command to enable BT version 1.x, 2.x or 3.x mode of some sort might also work...After connecting to the device in Bluetooth settings it does not show up as connected but instead you can see the scanner and it's MAC address in "Previously connected devices". Though it works without any issues on the other apps this way...Any ideas?
Update 1. After some further testing with other apps like "Car Scanner" and "Torque" it seems like the device is not a BLE/Bluetooth 4.x device. In "Car Scanner" you can choose between BLE/Bluetooth 4.x or traditional BT and the device is only visible using the traditional BT setting. It is also possible to observe the OBD2 adapter blink once on AndrOBD original settings, but when disabling ATZ, ATLP and ATI it blinks a couple of times.