Has anyone used the torque app on a fast tablet?

[hansj3]

So I bought torque pro and use it occasionally on my phone but its kind of really slow. Has anyone here used it on a faster tablet or phone? One of my coworkers just bought an mdmaxgo from Matco, and its nothing more than a fancy tablet with a Bluetooth dongle and some good software. It even has Google play. All for the low low price of $2500, but its a fluid professional experience wrapped in a water/shock/sand/whatever proof case and both scans, sims a oscilloscope, and has a tech help program to help point techs to the problem

If torque on a faster tablet would net me at least 75% of the same experience, I'd be thrilled. My old kyocera torque is painfully slow at torque,and my $40 black Friday tablet doesn't have Bluetooth plus its a great excuse to buy a new tablet

On that note I wish they had a more "professional mode" that would flip to codes,live data, freeze frame, and mode$06. Super bonus if it break it down into modules.

 

[michaelluscher]

The app itself is zippier on better hardware, but a older non CANBUS vehicle just isn't gonna serve up live data as fast as a newer one

Also, a OBDLink MX is hand's down the best ELM327 you can get

Keep CarGauge Pro on hand for GM products, and FORScan for the FML products

 

[bowlofturtle]

^agreed.

My Note4 is pretty quick and on torque pro it works nicely. But it still takes like a full minute or 2 to do a scan or clear faults.

how fast is the matco version?

Any handheld scanner i've used will pull faults rather quickly VS torque.

 

[Vikas]

It is NOT the hardware but the protocol aka wire speed. Anything before 2007 is going to be slow unless you can find the factory scanner.

 

[hansj3]

Originally Posted By: Vikas
It is NOT the hardware but the protocol aka wire speed. Anything before 2007 is going to be slow unless you can find the factory scanner.


Not true his scanner, my c reader, and the shops solus are all fast. None of em are factory scanners.


His scanner is faster than the snap on solus. I think because the software is more polished, and the dongle is permanently paired, but

 

[Vikas]

are you comparing apples to apples? heck, even professional like ScnnerDanner or EricO when using his fancy Snap On scanner shows how to cut down on the number of PIDs when he is doing the live data scan on older vehicles.

Are you talking about user interface and screen painting speed etc? Because the protocol itself is limited by its slow baud rate (eg ISO 9141 used in Japanese cars before 2007).

Now there are different ways a device could handle this to make the user experience more tolerable. For example, on my cod readers/scanners, the unit first tries all other protocols before trying ISO 9141; so it takes a while before it even establishes communication with the car. A better approach would be to remember the last successful protocol and start from there or give the ability to change the order etc but that involves employing software engineers and usability engineers on the project.