[Dodgeboy 1969]

Have you joined the google group? if so, make sure that play store account is on the same email. What is the problem?

https://play.google.com/store/apps/details?id=com.mariusrdv.jeepaa

URL not found on server

 

[AZJeeper]

Well, @mariuslt has been busy! I noticed a JeepAA update pop up on my phone so I went out to see what was new. A lot!

It looks like you figured out how to display all of the modes. They are all decoded ("Auto", "Sport", etc.) except for Rock Mode. That would be Mode 2 in the picture. Also, E-Locker: 1 means it's locked, 0 = unlocked. You nailed the AWD status! Sorry I couldn't be more help in getting you the data but at least now you have something to build on.

Regarding that "feature creep" idea I had about showing brakes on this page, perhaps there's an easier way. Why not just incorporate the Group: "Difference in Wheel speeds" into Driveline? That way one could tell if a wheel changes speed. The screenshot below is static, but it works well when, for example, turning a corner. I'm sure it would give a hint at least if BLD is being applied.

Also noticed a new menu item - "Display in fps" I believe. Not sure why that's there.

Again, many, MANY thanks for doing this! It's going from being "interesting" to a "must have"! At least for me.

 

[mariuslt]

Glad to hear , fps basically mean how many pids responses are received in a second. Request pid -> get response -> redraw all screen. Just interesting to my self how fast is communication. Because if too many pid request in one screen may slow down update rate. And thanks for rock mode and locker raw values, will map those in next build.

 

[AZJeeper]

@mariuslt, found another bug in the Imperial/Metric conversion. Pictures are worth 1000's of words...

Metric:

Imperial:

Believe that 1st gauge should be engine oil temperature.

Also curious that the outside temp is different between the gauge and what's on Uconnect. 28C is 82.4F so the gauges are consistent between Metric and Imperial. What's on Uconnect must come from a different place. What's weird is on my JKU, the outside temp on the display is about 1.5F lower than if I read it on the OBD2 port, so FCA must use different probes for display vs internal ambient temps.

 

[mariuslt]

@mariuslt, found another bug in the Imperial/Metric conversion. Pictures are worth 1000's of words...

Metric:

View attachment 234069

Imperial:

View attachment 234068

Believe that 1st gauge should be engine oil temperature.

Also curious that the outside temp is different between the gauge and what's on Uconnect. 28C is 82.4F so the gauges are consistent between Metric and Imperial. What's on Uconnect must come from a different place. What's weird is on my JKU, the outside temp on the display is about 1.5F lower than if I read it on the OBD2 port, so FCA must use different probes for display vs internal ambient temps.

uhhhhh yep imperial gauge "Engine oil Temperature" is missing his description. will fix it in 1.1.3 version maybe next week. atm 1.1.2 is stuck in google review, not sure why( whats new, mapped awd missing values and added wheel speed differences in driveline screen. More red wheel view border value, means it is running faster than others).
Also cant remember, but i think outside temperature value I have confirmed with alfaobd. so uconnect maybe use some math rounding

 

[AZJeeper]

uhhhhh yep imperial gauge "Engine oil Temperature" is missing his description. will fix it in 1.1.3 version maybe next week. atm 1.1.2 is stuck in google review, not sure why( whats new, mapped awd missing values and added wheel speed differences in driveline screen. More red wheel view border value, means it is running faster than others).
Also cant remember, but i think outside temperature value I have confirmed with alfaobd. so uconnect maybe use some math rounding

Ran version 1.1.2 through my extensive testing process Here's my assessment.

Close. Really close! The locker status is backward (i.e. shows "Locked" when unlocked and visa versa). I like the wheel speed differences on the driveline screen, but it's really hard to tell the red vs orange especially when bouncing around. Not sure what colors you can choose from but something with more contrast would be helpful. I confirmed the ambient temp with Alfaobd too and it's spot-on with your gauge, so Uconnect must have some rounding or something. I know in my JK the outside temp on my dash is disabled below about 20 mph. I can watch the ambient on my OBD gauge go up rapidly when I slow to a crawl so I'm sure there's some masking of temps so people don't freak out.

Today was the first time I paid close attention to the driveline screen as I drove around town. I'm quite surprised how much of the time the KL spends in 2wd mode!

Many thanks!

P.S. Remember how much I helped when you make your first million Euros on this app!

 

[Gary Kline]

Should work on any android auto headunit. But yours is android tablet itself and thats the problem I guess. My app is coded specifically for "android auto car screen", screen what you see is just normal application screen to grant bluetooth permissions (and yes shows up as location). After you plug device to usb cable, you should see android auto screen started. Double check if Google Pixel has android auto installed.

Hey @mariuslt ,

Is there any way to compile a build that doesn't check if it's running on Android Auto to see if it would work on a straight Android Tablet or do you think it just won't work (e.g. technically the architecture is too different).

As I posted in my earlier post, no matter whether I try to run the app on the android tablet head or my Google Pixel phone (in order to use AndroidAuto), the app just hangs on the permissions page. :-(

 

[mariuslt]

Hey @mariuslt ,

Is there any way to compile a build that doesn't check if it's running on Android Auto to see if it would work on a straight Android Tablet or do you think it just won't work (e.g. technically the architecture is too different).

As I posted in my earlier post, no matter whether I try to run the app on the android tablet head or my Google Pixel phone (in order to use AndroidAuto), the app just hangs on the permissions page. :-(

Everything will work for sure. Just need to develop/migrate android auto screens UI and for normal android device. But in your case, best scenario would be to drop out "middle man - bluetooth adapter" and use somehow a CAN bus request straight from your infotainment device, as I understand atm it can control climate, reacts to steering wheel buttons etc ?(just a thought)
I will think about "normal" android device solution.
Wait a second, did you installed JeepAA app on your android phone or straight to T'EYES CC3 device ? App should be installed on your mobile phone.

 

[mariuslt]

empty

 

[sb3251]

All these posts have been intriguing so I went ahead and purchased a vgate vlink mc+ and had the app up and running in 5 minutes. This is very cool! As another who is still a bit peeved that off road pages never came to the 2019s, I say thank you for doing this! Only have played with it for a few minutes and love what I'm seeing so far! If there is one wish I could add, not sure even if possible, but the ability to swipe left or right to switch between the groups as opposed to having to select from the menu would be incredibly helpful

 

[mariuslt]

All these posts have been intriguing so I went ahead and purchased a vgate vlink mc+ and had the app up and running in 5 minutes. This is very cool! As another who is still a bit peeved that off road pages never came to the 2019s, I say thank you for doing this! Only have played with it for a few minutes and love what I'm seeing so far! If there is one wish I could add, not sure even if possible, but the ability to swipe left or right to switch between the groups as opposed to having to select from the menu would be incredibly helpful

Google has so many restrictions regarding android auto apps, swiping or other interactions with screen I think is impossible at the moment or I dont know how . But yeh I see what you mean and would be much better interface.

 

[Gary Kline]

Everything will work for sure. Just need to develop/migrate android auto screens UI and for normal android device. But in your case, best scenario would be to drop out "middle man - bluetooth adapter" and use somehow a CAN bus request straight from your infotainment device, as I understand atm it can control climate, reacts to steering wheel buttons etc ?(just a thought)
I will think about "normal" android device solution.
Wait a second, did you installed JeepAA app on your android phone or straight to T'EYES CC3 device ? App should be installed on your mobile phone.

I tried JeepAA on both my Android Phone AND the T'EYES CC3 android tablet head in the dash. Both exhibited the same issue. When the app went to ask for permissions, I said yes but then the screen just hung on "All permissions are granted". There was no way to continue on/move forward etc. I had to shut the app and each time I went back in, it kept asking for permissions and would hang on the permissions screen.

I can use my vLinker OBD2 adapter with other OBD2 apps installed on both my Andoid (Pixel) phone and the CC3.

Thoughts?

ps: So in short, it looks like it installed correctly but when I go to launch the app and it asks for permissions, it never makes it past the permissioning screen.

 

[mariuslt]

I tried JeepAA on both my Android Phone AND the T'EYES CC3 android tablet head in the dash. Both exhibited the same issue. When the app went to ask for permissions, I said yes but then the screen just hung on "All permissions are granted". There was no way to continue on/move forward etc. I had to shut the app and each time I went back in, it kept asking for permissions and would hang on the permissions screen.

I can use my vLinker OBD2 adapter with other OBD2 apps installed on both my Andoid (Pixel) phone and the CC3.

Thoughts?

ps: So in short, it looks like it installed correctly but when I go to launch the app and it asks for permissions, it never makes it past the permissioning screen.

View attachment 234216

This screen looks ok, just not sure if yours head unit supports "real" android auto mirroring?

 

[AZJeeper]

@Gary Kline, If you open JeepAA on your phone, that white screen is all you will get. It would appear, as @mariuslt said, that your T'EYES CC3 is acting like an android tablet, not running Android Auto. That's why you get the white screen there too.

There are two different operating environments, native Android and Android Auto. Here's a quick test. Can you watch videos on your T'EYES CC3? If you can, that is NOT the Android Auto environment! Android Auto has strict restrictions that prevents any videos - even weather radar - from playing. Yes, there are hacks to get around it, but Google believes videos on AA are a safety issue.

I checked the T-EYES website and they say the CC3 has Android Auto but other models don't. I also saw some forum posts that says Android Auto CC3 needs the T'EYES Carlink app to work.

Good luck!

 

[sb3251]

Google has so many restrictions regarding android auto apps, swiping or other interactions with screen I think is impossible at the moment or I dont know how . But yeh I see what you mean and would be much better interface.

I figured there would be that restriction as there are no other AA apps that have swipe capabilities that I know of. But if you find a way...

 

[Gary Kline]

@Gary Kline, If you open JeepAA on your phone, that white screen is all you will get. It would appear, as @mariuslt said, that your T'EYES CC3 is acting like an android tablet, not running Android Auto. That's why you get the white screen there too.

There are two different operating environments, native Android and Android Auto. Here's a quick test. Can you watch videos on your T'EYES CC3? If you can, that is NOT the Android Auto environment! Android Auto has strict restrictions that prevents any videos - even weather radar - from playing. Yes, there are hacks to get around it, but Google believes videos on AA are a safety issue.

I checked the T-EYES website and they say the CC3 has Android Auto but other models don't. I also saw some forum posts that says Android Auto CC3 needs the T'EYES Carlink app to work.

Good luck!

Thanks @AZJeeper. The CC3 is a full Android head meaning I can (with nothing else connected) insert a SIM card in it (or connect via. WiFI), open the Google Play store and download and use almost any app there like an Android tablet. I have YouTube downloaded as well as the Google Maps app for example.

It also has Android Auto/Car Play meaning that if I connect my Google Pixel Phone (or an iPhone) and click the "CarLink" app, my phone displays on the head unit looking like Android Auto (or CP if I hook an iPhone up). So I believe I have both (though I use it almost exclusively in native Android mode all the time since there's really nothing extra I get by mirroring my phone through AA/CP.) Here's some screens I get natively with no phone or other connection:

YT app

Google Maps app

 

[AZJeeper]

It also has Android Auto/Car Play meaning that if I connect my Google Pixel Phone (or an iPhone) and click the "CarLink" app, my phone displays on the head unit looking like Android Auto (or CP if I hook an iPhone up).

Do you still get the JeepAA white screen when Carlink is active and T'EYES is in Android Auto mode?

 

[AZJeeper]

@mariuslt, had a quick look at 1.1.3. I didn't know there was an update until I noticed the Elocker showed off when I was in Auto mode! Didn't do all of the pages, just the driveline page. Wheel speed differences are really easy to notice now. BUT (always that "but"), the wheel speed data seems to blink off in the middle of a turn for a bit, then comes back. Maybe a fps issue? Wouldn't worry about fixing it yet - might be an OBD adapter issue. I'll do some more testing next time I get a chance.

Thanks again!

 

[AZJeeper]

@mariuslt - I took some data on AlfaOBD for the four wheel speeds. The data was recorded in approx 150ms intervals. I plotted the data and noticed it was quite noisy - a lot of high-frequency spikes, but relatively low amplitude. There is a lot of data crossing in the spikes. I'm pretty sure that's what is causing the blinking in the wheel speeds.

Depending on how ambitious you are, there are a couple of ways to smooth out the data. The first would be a x-period average. For example, you could average the current reading with the last 3 samples for a 4-period average. It will add a bit of lag to the data, but we are still talking only a few milliseconds. A better but more complex way would be to do a "simple" low-pass first-order filter. That probably is more work than it's worth unless you are well-versed in filter design!

I did a couple of plots of unfiltered vs a 4-period average filter. You can see some crossing in the unfiltered that is eliminated with the simple averaging.

Unfiltered:

4-period average:

Of course, you may have a better idea.

Let me know if I'm getting too deep into this. You have already done a lot and JeepAA is a great app. I know your time is valuable, so I guess it's how much you like your "hobby"!

 

[UN4GTBL]

I will move this comment here

This is very cool. I only tried it out in my Garage as I have a meeting to do shortly, but I like it!

Constructive feedback:

• Would it be possible to make it easier to switch groups? (Whether it's by swiping the screen left/right, or adding a "Groups" button at the top of the screen somewhere?)
• Could we change the Jeep JK picture to a KL?
• The "Connected & Group" box in the top left of the screen is kind of cut off from the driver's seat for me on my Pixel 7. Could it be moved to the right by half a cm or so?

Thank you!!