0.45.0

Description of bug:


1/ When trying to connect none of the dongles are showing as active - I have good Internet and Bluetooth.

so I do the following
1) Tried using both legacy and next gen dongle but both are showing as active on the dongle but the screen shows not availiable
2) I removed both dongles from my list and then tried again - still no luck
3) My Bluetooth connection is showing connected to my car (as it always is) so I turn the radio off
Now when I try and connect I get the error Make sure ignition is turned on, I try again not difference
I try Continue and I get the list of cars in my garage so I select my car and now connect.
4) Having connected i look at control unit 17 and get error message Communication error with control unit
5) Go back to control unit list and try again and it seems to be working

Not done any coding yet but ran a scan

Logged off and back on again and this time it connects to the car but I get the error message MAKE SURE IGNITION IS TURNED ON
The only way I can connect to the car is by using the Continue and select my car.

I cleared error messages on the scan and when I tried to email scan results no default email address is populated
History file shows nothing for the Clears that i have done
History file is showing confused results, I have 20 control units with a number of Faults before the clear and 1 fault after the clear.
The faults items are showing a mixture of before and after so not sure what they are supposed to be showing me

Android software version 9.0
Phone Sony Experia
Dongle variant - offline so not relevant
Car Cupra Formentor
App profile cupra280.co.uk

Agreed and i have reported directly as well but I use this section to let others know there is a bug as OBD11 are not very good at letting us know there is an issue that they are (hopefully) working on.

I also experienced the same issue with the new 0.45.0.
Almost impossible to connect, and when connected will not communicate with any control units.
Android 11 on Samsung Galaxy S10.
Vehicle is a 2021 VW Tiguan SEL P R-line.

Have sent several messages to the tech team for 2 days with no response.

Bob.

This is on a NextGen dongle, user email is [email protected]

Thanks for the confirmation.
Is there any way (safe) to revert back to the previous version?

Appreciate your post...

Bob.

I'm assuming you're talking about "sideloading"?
I don't think I'm in huge hurry (being a retired Software Engineer, I know how stressful "forced" updates are).
I'll patiently wait until they put it (the fixed "new" version) back out on the Play Store.

Thanks!

Bob.

This morning I received the following message from the Dev Team:

"Hello,

could you re-install the application and try again now?"

I have a couple of questions about this.

1) If I uninstall and re-stall the app, will I lose my Pro license and my stored credits?
and
2) If the answer to 1 is no, what good does uninstalling and re-installing a known "broken" app do?
and
3) Are they somehow saying that there is something about a fresh install VS an update that fixes this issue?

Bob.

I felt the same, they are trying to buy time.
Thank you for clarifying the license/credit situation.
Although it makes me feel much better knowing that those are safe, I don't think I will try to do what they are asking.

As mentioned previously, I am a retired Software Engineer myself. Embedded systems coding, but nothing to do with phones.
That said, I am trying to understand what differences, if any, happen during a clean install vs an update. My guess, little to none.

Your update was from 0.44.0 to 0.45.0? Mine failed from 0.43.0 to 0.45.0, and I only had the unit a handful of days. Somehow I missed the 44 update.
They update software THAT often? Must be stressful to work on their Dev team.

I think I'll pass on their suggestion and wait for 0.46.0 to be released.

Bob.

If no one posts after you, but you do, it merges with your last post?
Weird.

On mine I removed the software, installed 0.40 which worked fine.
This morning after i saw the IOS Thread I did the update to 0.45 and all the old issues came back.

The ios issue was different it was related to the fact that you could not code at all, the Long Coding and Adaptation processes were not working.
According to one user that is now fixed so its a different problem.

Took a shower and then decided to follow their request.
Here is the email I just sent the Dev Team:

"Hello and Thank You for the reply.
I did as requested and can report the following:

Installed dongle and turned on the ignition (but did not start the vehicle).
Hit CONNECT and almost immediately got the "Make sure the Ignition is on CONTINUE TRY AGAIN" message.
Try again did nothing.
I hit CONTINUE and it brings up a list of sorts with my CAR (a picture) in the middle.
When I hit the CAR it connected within 30 seconds.
I next went to the Car and chose Control Units.
I chose AIR CONDITIONING and surprisingly it got into the control data.
I did not try to do any changes (LONG CODING, ADAPTATIONS or APPS).
I then "arrowed" back until I got to where I could disconnect and disconnected.
Pulled the dongle and turned the ignition off.

While this is MUCH better than previous, I still find the CONNECTION sequence ODD.
Why does it want me to turn on the ignition when it is clearly already on.
Why does TRY AGAIN do nothing?
Why does CONTINUE bring up the list and allow the CONNECTION to complete?

Is this going to be the new NORMAL way to CONNECT?

Please advise.

Bob."

Do you find the "Make sure the Ignition is on    CONTINUE    TRY AGAIN" message odd?
I wouldn't mind if it went straight to the list, but what happens now makes ZERO sense to me....

Bob.

Sounds like an easy fix (to me, anyway)....
Hopefully they'll get it sorted.

Appreciate your bug thoughts

Bob.

I got pinged by OBDEleven over at the VWVortex forum.
They are "happy" that things are working now???
I asked a few questions that didn't get answered, and he said if I needed anything else to hit up [email protected]
Is this the end of this issue?

Confused.

Bob.

This version is very broken after chatting with the support guys

The 1st gen dongle just didn't want to connect or dropped quickly,

When it did connect it might read the modules but nothing else.