-
-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to connect to a 2017 VW Jetta #52
Comments
Hi, |
Based on the log file of the VW Jetta it seems that your adaptor breaks the Bluetooth connection on the ATZ (reset) command. I have seen this happen with several adaptors already. I would suggest to disable the ATZ command in the AndrOBD settings: This should eliminate the device reset and allow the bluetooth connection to stay alive. Please let me know the results |
This trick worked for my SEAT IBIZA ST FR 1.2 TSI 105 thanks |
@fr3ts0n thanks. Unfortunately, I don't have access to the Jetta right now, but I guess this has nothing to do with the car but rather with the adapter, right? So I should see the same issue with other cars and I guess that same trick would solve this problem. |
@oroce : regarding my answer you should try. As it worked with my SEAT it shall work for any recent VW group car |
@oroce: Yes you are right. |
@fr3ts0n it seems to be a recurrent problem. What about disabling this command in the default settings ? |
@Fraifrai This setting stays consistent with your installation for all following app usage. |
maybe a comment about it in the settings should avoid such issues opening. |
I've added this subject to the FAQ Wiki page |
I just wanted to confirm that disabling ATZ command resolved the issue for me, too. thanks @fr3ts0n |
Hey, I tried to connect to a 2017 (february) VW Jetta. After I select the bluetooth adapter the label goes online and immediately goes back to offline. the notification on the bottom says:
Device connection was lost.
Torque lite and premium works without any problem.
In Torque I was able to connect to the car with turned off timing. As it can be seen in the log I tried with all the timing options.
AndrOBD.log.1vwjetta.txt
Android:
App version:
The text was updated successfully, but these errors were encountered: