Voters 0
0
Vlinker MC-Android option not showing in the bluetooth connections list
- Closed
- Subscribe
 |
Hakan Akcalar |
Hi there,
My setup:
Hyundai Kona 64kWh 2021
Vgate Vlinker MC+
Samsung Note20 Android 12
This setup works with EVnotify can find and connect to vLinker MC-Android
However ABRP cannot find vLinker MC-Android option, (even if I press the connect button on the OBD dongle and/or wait a long time, plug-out & plug-in, etc), only lists vLinker MC-IOS option and if I select vLinker MC-IOS it connects and shows the current SOC only once, but never updates it again, thus useless.
It looks like ABRP cannot detect Vlinker MC-Android, is there anything I can do about it ?
Best regards,
Hakan
Activity Newest / Oldest
Katya_ABRP
Status changed to: Closed
Jesus Ruiperez
I can confirm what Hakan commented here. Connecting the ODB Vlinker MC+ is a really erratic and laborious process and I hope that wich follows will help to find the solution.
DATA:
VolksWagen e-up! 2020 (alpha)
ABRP: Android 4.2.0 (881).
ODB Vlinker MC+.
Phone: Xiaomi MI Mix 2S. Android 10 con MIUI 12.0.3
FACTS:
1.- The Vlinker MC-Android NEVER appears on the Bluetooth connection selection screen (in spite of the fact that it has been previously configured as Bluetooth connection and CarScanner has no problem on using it and coneccting successfully). Either the search continues without showing anything, or only Vlinker MC-IOS appears.
2.- The surprising thing is that Vlinker-iOS appears even though this connection has not been configured in phone Bluettoth connections.
3.- Once the only available option (vlinker-iOS) has been selected, the connection is made sometimes (rarely) or gives an error (more frequent)
4.- The "final trick" is to forget about the error, continue using the application and continue traveling without connection and then frequently, after a few minutes, it is detected that the connection has occurred and ODB data is already available in real time. Otherwise you must go back to point 3 and repeat the process again.
I hope to continue to be of help and I offer to gladly do all the tests that are necessary.
Hakan Akcalar
Hi Jruip,
I just wanted to let you know that, my setup just worked fine with the ABRP v4.2.0 (881). Maybe some updates coming to my Note20 might also have helped, idk. Best luck,
Hakan
Samuel_ABRP
Hi, could you get it to work in the meantime?
Hakan Akcalar
Strangely enough, I could not get it to work on my Samsung Note20 phone, but it worked on a Samsung J7 Prime phone, even though the latter is an older/lesser phone. No idea why :/
Samuel_ABRP
Once it is paired we store the BLE ID and also try to copnnect from other phones if we find that dongle. So can you please check, if the connection mechanism works on the other phone now? Setup is a bit more strict to not let pass any not working connections, but once it is known as working we will just try to connect to the dongle. Would be interesting to see, if the connection from your other phone works as well now that setup was successful.
Hakan Akcalar
I surely did try this, but with no success. I think my Note20 is not happy with the IOS named connection and needs to connect to Android named connection. As far as I know, both connections to the vLinker MC is BLE connections, but the Android one is not visible on ABRP. Similar thing happened with other apps, they struggled to find the Android option where the IOS option is immediately available. On these other OBD apps, I tried to use IOS option but was not successful, then pressing the connect button on the vLinker MC, some waiting etc, I could finally see the Android option pop up, then everything worked fine.
How my samsung J7 phone can work with IOS option I do not know, but my Note20 is not happy with IOS option and needs to connect to vLinker MC-Android option, if you can make it show-up on ABRP.
Hakan Akcalar
Hi Samuel,
Thank you for the advice,
I will try
Samuel_ABRP
Status changed to: User Feedback
Samuel_ABRP
You need to use the iOS named connection, as that is the BLE connection. We do not support classic BT connection right now.
Did you try to restart the app after setup? There might be something wrong with the transition from setup to normal usage. So please try again and check if a restart of the ap works after setup.