Skip to content
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

Closed
oroce opened this issue Apr 2, 2018 · 11 comments
Closed

Failed to connect to a 2017 VW Jetta #52

oroce opened this issue Apr 2, 2018 · 11 comments

Comments

@oroce
Copy link

oroce commented Apr 2, 2018

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:
screenshot_20180402-180151

App version:
screenshot_20180402-180230

@oroce oroce changed the title Failed to connec to a 2017 VW Jetta Failed to connect to a 2017 VW Jetta Apr 2, 2018
@Fraifrai
Copy link

Fraifrai commented Apr 3, 2018

Hi,
same problem with SEAT IBIZA 2013

@fr3ts0n
Copy link
Owner

fr3ts0n commented Apr 3, 2018

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:
Settings -> Development options -> Disabled ELM commands -> check "ATZ"

This should eliminate the device reset and allow the bluetooth connection to stay alive.

Please let me know the results

@Fraifrai
Copy link

Fraifrai commented Apr 4, 2018

This trick worked for my SEAT IBIZA ST FR 1.2 TSI 105

thanks

@oroce
Copy link
Author

oroce commented Apr 4, 2018

@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.

@Fraifrai
Copy link

Fraifrai commented Apr 4, 2018

@oroce : regarding my answer you should try. As it worked with my SEAT it shall work for any recent VW group car

@fr3ts0n
Copy link
Owner

fr3ts0n commented Apr 4, 2018

@oroce: Yes you are right.
It is an issue of the combination of adapter- and mobile device.
You will face the same situation on other cars as well, but the setting of ATZ command disabled should fix that situation for all vehicles.

@Fraifrai
Copy link

@fr3ts0n it seems to be a recurrent problem. What about disabling this command in the default settings ?

@fr3ts0n
Copy link
Owner

fr3ts0n commented Apr 18, 2018

@Fraifrai This setting stays consistent with your installation for all following app usage.
This is only reset to default values if you de- and re-install the app, so I don't really see the necessity of changing the workaround into the default settings.
The ATZ command is handled by most adapters without any problems in BT communication ...

@Fraifrai
Copy link

maybe a comment about it in the settings should avoid such issues opening.

@fr3ts0n
Copy link
Owner

fr3ts0n commented May 8, 2018

I've added this subject to the FAQ Wiki page

@fr3ts0n fr3ts0n closed this as completed May 8, 2018
@oroce
Copy link
Author

oroce commented May 13, 2018

I just wanted to confirm that disabling ATZ command resolved the issue for me, too. thanks @fr3ts0n

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants