Paid App get no connection (2025)

Torque main forum

6 Posts

2 Users

0 Reactions

19 Views

RSS

(@mi28havoc)

Posts: 9

Active Member

Topic starter

Hey,

I write that some time before, but to this moment, no bugfix is released 🙁 (and my older post was deleted?!)

I have a Volvo V40 from 1998 and a cheap ebay adapter. When I had paid for the app, everything works find. But then with the update with the new "start screen" the paid app cannot connect to the ECU anymore. The free app works without problems!

I get the info:

- checking protocol
- multible ECU detectet
- checking model... and there it freezes...

the free app jumps over this and say

- checking protocol
- multible ECU detectet

and then it connects...

Please say what to do (send debug logs etc.) 🙁

-------
Tony

P.S. Sorry for my bad english oO

(@admin)

Posts: 6632

Member Admin

Hi Tony

The latest version 1.4.46 contains the debugging code that I need to get this problem fixed for you

If you could start the program, go to the "Realtime" screen, wait for it to try to connect for about 2 minutes(this is important to gather enough information). Then press 'Menu' click 'More...' and use the "Send Comms Debug Logs" option.

Enter a short description (so I know who the debug is from - just your forum name will do) and I will then be able to see what is going on for you

Thanks

Ian

(@mi28havoc)

Posts: 9

Active Member

Topic starter

Hi Ian,

done (send it twice, so i'll be sure that you got the logs) 🙂 thanks in advance 😉

Tony

(@admin)

Posts: 6632

Member Admin

Hi thanks for the logs

It looks like your adapter may be faulty - from the log responses there are a lot of '?' responses from the adapter - this is an error response from the adapter meaning that it did not understand the command torque sent to it (from the logs the command was correct)

If you go to the "Adapter Status" activity and scroll down to the "Adapter Error Rate" you will see it will be above '0' if the app has been trying to connect for some time. A snippet from communication with the adapter looks like:

1303397803881 {-- ATI
1303397803911 --} ELM327 v1.4
1303397803912 {-- ATH0
1303397803964 --} OK
1303397804074 {-- ATAT0
Fast 'Poking' interface due to no response
1303397808252 {--
1303397808280 --} ?
1303397808282 {-- ATAT0
1303397808333 --} ?
1303397808333 {-- ATAT0
1303397808533 {-- ATAT0
1303397808576 --} ?

- The '?'s should not be there.

Can you confirm you only have one active bluetooth connection with the adapter and no other pairings, and also that you are using an original ROM image with the handset

The free version works (and only just) because it does not use the responses from the adapter it just blindly sends data, but you hardly get any features for that. The full version needs the adapter to work correctly for the features it provides.

Thanks

(@mi28havoc)

Posts: 9

Active Member

Topic starter

Oh, that doesn't sounds good :/

Maybe my original Nexus One Bluetooth Car Adapter had an open connection, but i don't think so...

The OBD Adapter works with every other App, even on my Laptop with some programs, and has no Problems :/

I'm not sure if I should buy a new one, i don't think that this fix the Problem...

The Volvo V40 has two ECUs, a "light" ECU, that is the real one for the engine, and a "transmission" ECU for the automatic transmission, maybe the paid version did not find the "right" ECU, because it is named "light"?

My Nexus one has the stock 2.3.3 Android without any modifications/root etc.

(@mi28havoc)

Posts: 9

Active Member

Topic starter

OK, now tested with a Mazda Premacy, same problem 🙁

I sent you the logs, anyway, maybe you can see more than in the Volvo...

When I look at the "Adapter Error Count" there is "0", not more...

Do you think i should buy another eBay OBD Bluetooth Interface, and if yes, which? :-/

Or maybe u can do a "only send" mode in the paid app, so it works like the free app? The free app shows everything I want, so I have no problems with "less" functions, but the advertisment sucks :-/

Previous Topic

Next Topic