2014+ Jeep Cherokee Forums banner

Android auto metrics app (off road pages)

1 reading
13K views 99 replies 13 participants last post by  Fraddles  
#1 · (Edited)
Hi,

I have released my app in google play store, but it is in early access(closed testing). To access app, you need just to join google group jeepaa - Google Groups. and then you should be able to access (same account email) https://play.google.com/store/apps/details?id=com.mariusrdv.jeepaa
  • Tested only with Jeep Cherokee 2019 Limited, 2.0L turbo, ZF9 gearbox, Uconnect 8.4
  • Bluetooth device: Vgate vLinker MC+ (should be ok and cheap ELM327 1.5)
  • Android device: Xiaomi Note 10 pro (Android 13). App supports Android 9 and up

Atm application has bugs, so don't shout on me :). I will try to work on improvements from time to time.

Couple of screens:
 
#66 ·
I dont think so sorry. I do know Flutter language, I can write android/ios app with one code base, but only simple/usual ones. In this case we have bluetooth part and android auto/car play, those parts requires native coding and ios is not my thing :)

For the boost value I used standard pid 010B - Intake manifold absolute pressure , and conversion to Bar is (A/100)-1,
for psi (A / 100) - 1) * 14.5038. Not sure if alfa has real turbo pressure value.

I was on vacation trip and only now saw a big activity in this thread :), thanks guys. Also, I will check what I can do for others suggestions/changes.
 
#63 ·
@mariuslt, I'll jump on this "improvement" bandwagon. For the turbo, the Boost looks like it's giving both vacuum and boost. That makes it hard to see actual boost unless you are paying attention to the "-" in front of the number. Perhaps it would be best to filter out negative numbers and just show actual turbo boost? Just a thought. Also, what are you using to calculate boost? Is it Boost Pressure = Absolute Pressure (in manifold) - Atmospheric Pressure? Thanks for considering!
 
#72 ·
I did a quick test of 1.1.4. It looks very good with the Cherokee vs the Wrangler, and I like switching screens much better!

I got a vLinker MS for free to evaluate. Tried it with JeepAA. It is noticeably faster to connect and the data seems a bit smoother on JeepAA (but it might be my imagination!). For sure the MS is much faster than the MC+ on AlfaOBD. I don't have my OBDLink MX+ to compare to, but offhand I'd say the MS is comparable.

Now, about that boost gauge... ;)
 
#73 ·
now I am lost a bit :) regarding boost formula. To calculate real boost I need just to subtract barometric pressure(0133) from MAP(010B). Basically and what I do now with pid 010B - (A / 100) - 1, for bar value. 1 is a constant for sea level barometric pressure and as I understand this is the main problem atm.

Core sentence from AZJeeper article - "To determine the Manifold Relative Pressure, also known as boost, we would take the value displayed as Absolute pressure and subtract the Atmosphere to make it "relative." "

Final formula would be 010B - 0133 = boost. In my area I still will get negative pressure because barometric pressure returned 1.00 bar today. I will incorporate and 33 pid in the next build.
 
#76 ·
@mariuslt, quick question. What is the difference between Battery Voltage and Voltage Sense? I noticed the Battery Voltage deteriorates after the car shuts down, so it's not a direct measure of the actual battery. I assume that's what Voltage Sense is?

Just curious.
 
#77 ·
@mariuslt, quick question. What is the difference between Battery Voltage and Voltage Sense? I noticed the Battery Voltage deteriorates after the car shuts down, so it's not a direct measure of the actual battery. I assume that's what Voltage Sense is?

Just curious.
I believe that voltage sense could be a voltage of engine ECU or some other sensor, to monitor all electrical system status. But I am not sure. Could not find and in alfa what for this value exactly stands for.
 
#88 ·
@mariuslt hasn't been on this forum since November 2024. Maybe he got tired of turning his hobby experiment into a free product. I know I sure pressured him a lot on getting features, and I appreciate all of his time to make this available to us.

In any case, thanks for all of the work you put in! Hope to see you back on the forum sometime!
 
#90 ·
I'd pay for the android auto version :cool: need to market past this forum to get your proper dues :)
 
#91 ·
Does this work for pre-2019's?

I see Gary in here, but he could not get it to work?

I would potentially be interested in a version that works with standard Android, on a 2018 KL...

I don't have a (suitable) OBD reader yet, but I do have a small Samsung tablet that would work nicely as a secondary display, or an older phone or two... Just need to find somewhere to mount it.

I do have an MSD Dashhawk from my Mazda 6 MPS... but it does not want to talk to my Jeep. :cry: Probably because it's last update was a few years before the first KL appeared.

Cheers.
 
#92 ·
Does this work for pre-2019's?

I see Gary in here, but he could not get it to work?

I would potentially be interested in a version that works with standard Android, on a 2018 KL...

I don't have a (suitable) OBD reader yet, but I do have a small Samsung tablet that would work nicely as a secondary display, or an older phone or two... Just need to find somewhere to mount it.

I do have an MSD Dashhawk from my Mazda 6 MPS... but it does not want to talk to my Jeep. :cry: Probably because it's last update was a few years before the first KL appeared.

Cheers.
Issue I had is that I could not get the TEYES to find my OBD2 adapter (either vLinker MC+ or OBDLink MX+) so even if I were to get @mariuslt's software to work on a bare android tablet, I have no way for the tablet to connect to the OBD2 port. I'm not sure if this is a limitation on just my TEYES or all android tablets. I use my phone for AlfaOBD to see the same information so having it on the android tablet (TEYES) isn't critical for me. I heard it might be possible using a USB OBD2 adapter with the TEYES but need to confirm that.