Carplay TSB hopeful at least
#1
AudiWorld Newcomer
Thread Starter
Join Date: May 2017
Location: Arlington, VA
Posts: 8
Likes: 0
Received 0 Likes
on
0 Posts
Carplay TSB hopeful at least
(I did a quick scan of messages, but didn't see posting of this fix, apologies if it is known already.) Note: I haven't tested this yet, but I have hopes. I just had my car in for the first service (1 year, only 7,000 miles.) I brought up about Carplay and the reverse problem. They explained that there were Technical Service Bulletins (TSBs) about it. Here's a copy of what was put on the work order of what they did related to that.
"B APPLE CAR PLAY WILL SHUT OFF WHEN FIRST STARTING UP AND PUTTING IN REVERSE. HAPPENS EVERY TIME. MUST UNPLUG PHONE AND PLUG BACK IN TO WORK. CAUSE: PERFORMED TSB 2046294/3 91960199 CHECKING 3G MMI SOFTWARE 6752 W 1.05 0.10 280 1400 14.00 14.00 01500000 GFF/GUIDED FUNCTIONS 6752 W 0.00 1.00 2800 14000 140.00 140.00 FC: 919639 002 PART#: COUNT: 0 0 TPARTS CLAIM TYPE: 710 AUTH CODE: 919601 3080 15400 TLABOR VERSION 1 (EMP# 6752,20MAR18 11:53): 7005 found tsb- 2046294/3 scan system and no faults store in the system, found tsb - 2046294/3- These are known software concerns which only exists with 2017 A4 vehicles which were built with the base MMI system that does not have navigation nor an internal jukebox hard drive. This MMI system is called MIB2 High Scale (or MMI Radio Plus). The concern was resolved in vehicles built after CW22/16 with SW0110 or service SW0118 or higher. connected battery charger and sd card and updated 5f module to latest software version. after completion perform svm code input test plan, and updated the 5f module to latest software version. completed diagnosis VERSION 2 (EMP# 6752,20MAR18 12:05): 7005 found tsb- 2046294/3- method 2 scan system and no faults store in the system, found tsb - 2046294/3- These are known software concerns which only exists with 2017 A4 vehicles which were built with the base MMI system that does not have navigation nor an internal jukebox hard drive. This MMI system is called MIB2 High Scale (or MMI Radio Plus). The concern was resolved in vehicles built after CW22/16 with SW0110 or service SW0118 or higher. connected battery charger and sd card and updated 5f module to latest software version. after completion perform svm code input test plan, and updated the 5f module to latest software version. completed diagnosis"
I'll try and check how it is doing over the next few weeks, but wanted to share this, since I know other people have also been frustrated.
Greg
2017 Audi A4
(and previously 2004 Audi A4)
"B APPLE CAR PLAY WILL SHUT OFF WHEN FIRST STARTING UP AND PUTTING IN REVERSE. HAPPENS EVERY TIME. MUST UNPLUG PHONE AND PLUG BACK IN TO WORK. CAUSE: PERFORMED TSB 2046294/3 91960199 CHECKING 3G MMI SOFTWARE 6752 W 1.05 0.10 280 1400 14.00 14.00 01500000 GFF/GUIDED FUNCTIONS 6752 W 0.00 1.00 2800 14000 140.00 140.00 FC: 919639 002 PART#: COUNT: 0 0 TPARTS CLAIM TYPE: 710 AUTH CODE: 919601 3080 15400 TLABOR VERSION 1 (EMP# 6752,20MAR18 11:53): 7005 found tsb- 2046294/3 scan system and no faults store in the system, found tsb - 2046294/3- These are known software concerns which only exists with 2017 A4 vehicles which were built with the base MMI system that does not have navigation nor an internal jukebox hard drive. This MMI system is called MIB2 High Scale (or MMI Radio Plus). The concern was resolved in vehicles built after CW22/16 with SW0110 or service SW0118 or higher. connected battery charger and sd card and updated 5f module to latest software version. after completion perform svm code input test plan, and updated the 5f module to latest software version. completed diagnosis VERSION 2 (EMP# 6752,20MAR18 12:05): 7005 found tsb- 2046294/3- method 2 scan system and no faults store in the system, found tsb - 2046294/3- These are known software concerns which only exists with 2017 A4 vehicles which were built with the base MMI system that does not have navigation nor an internal jukebox hard drive. This MMI system is called MIB2 High Scale (or MMI Radio Plus). The concern was resolved in vehicles built after CW22/16 with SW0110 or service SW0118 or higher. connected battery charger and sd card and updated 5f module to latest software version. after completion perform svm code input test plan, and updated the 5f module to latest software version. completed diagnosis"
I'll try and check how it is doing over the next few weeks, but wanted to share this, since I know other people have also been frustrated.
Greg
2017 Audi A4
(and previously 2004 Audi A4)
#2
AudiWorld Member
CarPlay now works properly for us with iOS 11.3. Which is interesting, because there is nothing in the release notes that suggests any CarPlay fixes.
2018 Allroad Prestige, MMI firmware: 1118
2017 A4 Prestige, MMI firmware: 0918
iPhone 8, iOS 11.3 (15E216)
2018 Allroad Prestige, MMI firmware: 1118
2017 A4 Prestige, MMI firmware: 0918
iPhone 8, iOS 11.3 (15E216)
#3
Interesting. I've def. been having this carplay issue. Downloaded 11.3 and will report back tomorrow if this update resolved the issue. Fingers crossed.
#4
AudiWorld Member
#6
Audiworld Junior Member
In case this helps others diagnose this issue further...
iOS 11.3 on my iPhone X fixed the "CarPlay-disconnects-after-Audi-camera-screen-appears" issues on my 2017 A4 allroad Prestige (MMI 0918).
A few months ago, I took my car to the dealer with the same complaint posted at the top of this thread. At that time, my dealer reported that there is no TSB on this issue, or any MMI firmware update designed to fix this issue. They also were unable to reproduce the issue using their own iPhones; it was only happening for them with my iPhone X. I don't know what iPhones or iOS version they tested with.
iOS 11.3 on my iPhone X fixed the "CarPlay-disconnects-after-Audi-camera-screen-appears" issues on my 2017 A4 allroad Prestige (MMI 0918).
A few months ago, I took my car to the dealer with the same complaint posted at the top of this thread. At that time, my dealer reported that there is no TSB on this issue, or any MMI firmware update designed to fix this issue. They also were unable to reproduce the issue using their own iPhones; it was only happening for them with my iPhone X. I don't know what iPhones or iOS version they tested with.