asellus

This is not normal on my MY17. My headlight switch has off, auto, running lights, and headlights as switch positions, and the headlights only come on in automatic when there isn't sufficient light to trip the sensor, or when in the headlight position.

I believe you can code various parameters around the DRLs, so someone may have popped in there with a PIWIS or equivalent?

I assume that "off" is one of the switch positions tested that still has the headlights on.

Worst case, perhaps there's a short in a relay somewhere, the DRLs are tripping the headlight circuit? Seems fishy to me, given that a lot of modern cars are module-driven for this. Not sure on the 911.

very cool, that's a good piece of information -- @enzotcat this is why our map FEC differs, I guess!

rainer

So, I‘m one step further on the light issue: the light switch does not seem to be recognized. No part #, no serial #, just empty fields.
I compared it to 2 other Macans, both show proper ECU information.

it‘s either not plugged in or defect i guess. The Front BCM just switches headlights on when ignition is on, but does not get any setting infos like „auto“ or „off“.

my buddy ordered a new switch, that should fix it.

enzotcat

Well, I've tried pretty much everything I can think of - leaving the car with it overnight, using @asellus FEC list for my own, adding in more FECs, etc. - yes, I made doubly sure that I didn't have a space in my parameter list (it was a copy-and-paste error for the message), I looked at the bytes of the generated FecContainer to make sure it had all of the FEC codes, I tried running the adaptation before I flashed the FS, I tried it after, I tried leaving the FS as-is and leaving that overnight and then changing just the FecContainer. Still nothing. It's as though it's just completely ignoring it. Normally I'd expect, when connected via Bluetooth, that my phone would pop up a message saying "Android Auto is available", but I get nothing at all. No message, no indication that the MIB2 has done anything useful. It says "USB device connected" when I connect the phone, as it always has.

I think I'm gonna give up on this for a while again.

rainer

AA will not work with bluetooth, only w/ USB.

I got the message immediately after patching and connecting the phone w/ USB.

enzotcat

Yup, I know - I plugged it in. But all my other cars give a message when your phone is connected to the car by Bluetooth that says "Android Auto is available. To connect, plug in your device".

When I plug it in, all I get is the USB Device connected" message, nothing else.

@rainer - how did you do the ExceptionList.txt route - did you just add a file with the FEC exceptions?

enzotcat

@rainer and @asellus - what is the version of the firmware on your unit? I wonder if that has something to do with it.

asellus

S/W: MHI_US_POG11_K3300 0809
H/W: 051

Phone driver version listed as 10.468.116

enzotcat

Hmm.

My S/W is MHI2_US_POG11_P3300 0809
H/W is the same as yours at 051
Media driver version is CLU6_MMX2_PAG_NAR_G11_073PROD-1
Phone driver is the same at 10.468.116


[Edit] I suspect you really meant MHI2 and that was a typo. Seems like the K vs P is "dealer installed" vs "factory installed" version; otherwise they're identical.

enzotcat

Eureka!

So I decided to do some more research and try things again. My premise was simply that the MIB was not rebooting properly even though I left it overnight, turned the car off, etc. etc. etc. So I found a nice little place that has some MIB hacking tools (from an earlier post in this thread, but see here - M.I.B. - More. Incredible. Bash. Anyway, I groveled through the code a little bit and found that they do it a little differently - they use ExceptionList.txt and hack MIBRoot to disable the checksum/encryption check for both FecContainer.fec and ExceptionList.txt; anyway, I didn't do that, but it did lead me to the little key that seems to have done the magic for me - a command to reboot the device - on -f rcc /usr/apps/mib2_ioc_flash reboot executed on the RCC. That set of code is a treasure trove of MIB patches and scripts for having a lot of, errm, "fun" with your MIB2. Anyway, the first time I did it, I was running an FecContainer.fec with a bunch of extra FECs, and upon reboot my nav was suddenly gone, so I looked and finally found a real InvalidFecContainer.fec that was significant. So, next I replaced the container with the original FecContainer.fec and saw my nav magically appear after a couple of seconds - that was very encouraging.

Finally, I took my 1st modified FecContainer that just added the FEC for AA, and copied that over. For good measure, I rebooted via the command above, and as they say, voila! Magic happened! (And yes, the seat heater is on because it's 18 degrees F outside and snowing and my garage is unheated).

Thanks to all the help from @asellus without whom I would never have gotten this done. And thanks to @chris2 even though he's actively ignoring this thread for putting the original guide together.

Let's hope that nothing cray-cray goes wrong due to the hack (I doubt it, because I disassembled the code and looked at what it was doing so I'm pretty confident that nothing bad will occur, which is why I was moderately insistent to myself at least of doing this myself - I don't exactly like letting anyone monkey with my software toys), but it's definitely not for the faint-hearted.




Home Screen!!

Android Auto link!!

enzotcat

Some more thoughts to record things for posterity. You definitely have to do an "adaptation" - doesn't matter if it's via PIWIS or via command line on the MIB2 device.It looks like you need to ensure that 3 things are set correctly - (a) Apple CarPlay must be enabled (should be, since it comes from the factory like that), (b) Android Auto must be enabled, and (c) USB device mode must be set correctly (again, should be since it comes from the factory like that). In any event, if you're doing it via PIWIS or some other tool, follow those guides. If, however, you're doing it via command line, it's something like the following. It seems like setting these values both before you flash and after you flash may be useful, and I suspect - based upon a hunch and knowledge of how some dummies write code that relies upon a read to change cached values - that you want to read the values back again after setting them. It goes something like this:

Also note that after the initial reboot, it takes some time for the home screen to load - the Porsche logo appears, the outline of your car appears, and then if you do not go to a home screen loading image and instead go to something like the last screen you were on before rebooting, press the "Home" button to go home. This should then take several seconds to show, and in the interim it will show a "Loading Home" page. If it does not do this, this is your clue that the unit has not completely rebooted and therefore none of your changes have gone into effect. In that case, see the previous post about rebooting the unit (in brief, execute on -f rcc /usr/apps/mib2_ioc_flash reboot when logged into the RCC or MMX).

rainer

(have to change thread due to update):

I had connection problems w/ AA and it did not work after patching - just got the update that it works now, the cable was the issue!

RadonHD

Did anyone tried Sport Chrono?
I tried to make screenshots (with Developer Mode enabled) but didn't find a key to make a screenshot. Long pressing Home, Media etc. did not work for me...

enzotcat

What do you mean w.r.t SC - do you mean trying to enable it? I’ve got SC already, so haven’t tried it.

asellus

Yeah, AA can be real finnicky with USB cables. A while back I switched to "pursun" brand cables with fully metal, 90 degree angle ends on them and haven't had a single issue since.

googleg

Hello all,
I have been reading this post with a lot of curiosity and interest. I find it crazy that a much wanted feature such as Android Auto is there, waiting to be activated... I'm tempted to do the flip on my 2017 Macan.

If I understood correctly the tool "MIB - More Incredible Bash" pretty much automates most of the tasks once you have gained access to the system. One question though: is it mandatory to flash a patched image or copying the patched FEC and EL is enough ?

Also, the MIB readme says it is not recommended to flash the unit while the engine is running. I've seen on this thread someone crashing the PCM because it went on sleep mode half way through the process. What is the safest way to proceed if you don't have an external power source?

Thank you for your help.