I have it working on my 2013.
larger Nexus 6p or Pixel XL displays great w/ AMOLED screens with high resolution and I have a swank RAM mount and ball affixed up on dash that holds it for this app as well as Topo maps ...fwiwWhat are folks using to monitor with? Double dins or tablets? I am looking for a small tablet or double
Dimm but I Habe a beef stereo so don't want to fuck it up. Is there anyway to enxoirporste innovative wideband into the datalogging. Thanks.
Sent from my iPhone using Tapatalk
Apple one leaves a bit of a sour taste in your mouth as you use it Ok, all the joking aside - the platform in which the application runs should have no impact on performance. OS and functionality are two separate things.I noticed that you can get the torque app on the apple now. Has anyone tried it and notice any difference between Android and Apple?
I am re-assessing my setup and re-doing it anew;mine works perfectly for my 2012. granted I have a manual but all other readings work well.
I haven't really updated my app in a long time because it's always worked for me in the limited capacity I needed it. I can look into it this week and get back to you. I picked up the app 5 or 6 years ago... I also have Pro and used it primarily for DTCs. I used it as a primary gauge cluster for an LS swap on another vehicle, but it still read the JKU just fine when I had it plugged in.I am re-assessing my setup and re-doing it anew;
I actually may have had TorquePro working for such a long time - so long it predates the upgrade where the TorqueScanner app plugin came about - I do not recall ever having installed the Scanner plugin for it. I wonder if someone like myself who has had it prior to that, you may recall that was not always a requirement to attain the Extended PID option; I realized whatever OS update blew my configuration of the app away also simply defaulted the thing and must now require these plug ins for certain premium functions (I own the Pro version ) .
I went back to review all of my install setup and config notes and nothing about plug-ins was mentioned and I would recall installing something separate. whatever
I am reinstalling and seeing if it made a difference but until then I ordered one of the B&M dial gauges so I can have an analog temp-gauge that is there if this digital scanning goes south.
thanks, btw; I appreciate your verifying for me. :jeep2:
thatd be cool and I appreciate it. I haven't tested yet after reinstalling so please feel free to share your findings as wil I :jeep2:I haven't really updated my app in a long time because it's always worked for me in the limited capacity I needed it. I can look into it this week and get back to you. I picked up the app 5 or 6 years ago... I also have Pro and used it primarily for DTCs. I used it as a primary gauge cluster for an LS swap on another vehicle, but it still read the JKU just fine when I had it plugged in.
Small update I found while working on this with my 2011.
It seems like if you send the 3E01 code to a 2011, and then later the 1092 code, it causes the issue where the abs and brake light start blinking. If you have tried the 3E01 code you need to disconnect everything and start over. Then the 1092 wakeup works great.
07-10 - 3E01 wakeup
11 - 1092 wakeup
>11 - unknown
I tested the temperature I was getting from Torque vs my Flashpaq and they match up. This makes me pretty confident that the reading is accurate.