[NucMed]

(There seems to be the right post for it: https://www.a5oc.com/threads/mmi-3g...ently-2023-europe.176144/page-38#post-1628844)

It seems that the link there for RoW leads nowhere now

 

[mj131]

It seems that the link there for RoW leads nowhere now

Yes,
here is the map link (thanks Byront for that)

17.26 GB file on MEGA

mega.nz

And here is prepared fixes:
ANZ 3G+ - 412.3 KB file on MEGA
ME 3G+ (untested yet) 412.4 KB file on MEGA
SA 3GHigh - 412.4 KB file on MEGA
SA 3G+ - 412.4 KB file on MEGA

Install the map, use the activator from very first post and then use the fix provided here.
Enjoy your new map.

Fixes for other parts of the map will be provided on demand

Here is the post you are looking for

 

[NucMed]

Here is the post you are looking for

Hi, thank you. I note Congo is talking about "fixes" for the maps, is that something that I need to d/l too as I notice you mention not to install any "activators/fixes/HDD reformating scripts or the like"?

Cheers, all the best, Peter

 

[mj131]

Hi, thank you. I note Congo is talking about "fixes" for the maps, is that something that I need to d/l too as I notice you mention not to install any "activators/fixes/HDD reformating scripts or the like"?

Cheers, all the best, Peter

No fixes are needed. Just the maps themselves.

 

[NucMed]

No fixes are needed. Just the maps themselves.

Thank you. As an aside, I've PM'd you my scan done with VCDS in November just before coming O/S.

 

[DrGER]

Hi, thank you. I note Congo is talking about "fixes" for the maps, is that something that I need to d/l too as I notice you mention not to install any "activators/fixes/HDD reformating scripts or the like"?
...

This is likely related to the the work we did on your HNav system last year to fix the missing acios_db.ini file for the MMI3G AN region navdb. Depending on mj131's implementation, you may need to re-run the nav unblocker script after installing the MMI3GP AN navdb. --g

 

[NucMed]

This is likely related to the the work we did on your HNav system last year to fix the missing acios_db.ini file for the MMI3G AN region navdb. Depending on mj131's implementation, you may need to re-run the nav unblocker script after installing the MMI3GP AN navdb. --g

Thanks for the heads up DrGER, I might, if I may, copy you in using your mmi3ginfo3-231230 script when I do the install, it may give you more of an insight into what is going on with the implementation.

Cheers, Peter

 

[TJ001]

As promised a few more pictures.

Mj has sorted most ofvthe little niggles with only the rear parking graphics glitch which is being worked on.

Can't believe how great the mmi looks now.

I'm now looking into how to play videos from the SD card format etc and play about with my new updated mmi.

Thanks again to Mj for this, it's transformed my car.

 

[NucMed]

Hi TJ001, just wondering about the screen showing Audi Drive Select. Is your car equipped with it? I guess that screen replaces (at least on my 2011 A6 C6/4FH allroad) the circular red/black dial with each setting. Does the car depicted represent your model, or is it just a generic car? So, for mine, would it display the appropriate A6 allroad? Cheers & congratulations with being the first ...

 

[TJ001]

Hi,

I dont have ADS as standard I activated by obd11.

It's a generic car but I don't know if it might change depending on what model is set in the green menu.

 

[NucMed]

Hi,

I dont have ADS as standard I activated by obd11.

It's a generic car but I don't know if it might change depending on what model is set in the green menu.

Ah, ok, thanks for the clarification.

 

[mj131]

This is likely related to the the work we did on your HNav system last year to fix the missing acios_db.ini file for the MMI3G AN region navdb. Depending on mj131's implementation, you may need to re-run the nav unblocker script after installing the MMI3GP AN navdb. --g

The activators/unblockers, while super convenient, are based on a really bad idea.
Stopping the vdev-logvolmgr (like most activators do) has many side effects, such as disabled background database file verification & more.
My build does not have (or need) any of such brute 'hacks' and installing them would only worsen the operation of the unit.

Thanks for the heads up DrGER, I might, if I may, copy you in using your mmi3ginfo3-231230 script when I do the install, it may give you more of an insight into what is going on with the implementation.

Cheers, Peter

Please do not run any scripts or share any information/files generated by them. I ask this as a way to respect my work and effort to make this possible.
While I do provide this on here now for free as a goodwill to the community, I do not want my builds to become another "solution" that is being shared and sold for-profit by others.

 

[NucMed]

Please do not run any scripts or share any information/files generated by them. I ask this as a way to respect my work and effort to make this possible.
While I do provide this on here now for free as a goodwill to the community, I do not want my builds to become another "solution" that is being shared and sold for-profit by others.

OK, understood. My concern regarding changing the system was related to the installation of maps last year bought from an "official" vendor that borked my system & DrGER was good enough to rescue it for me ... see this link

AS DrGER is skilled in this area, perhaps you could help each other out from time to time when/if problems arise?

 

[DrGER]

The activators/unblockers, while super convenient, are based on a really bad idea.
Stopping the vdev-logvolmgr (like most activators do) has many side effects, such as disabled background database file verification & more.
My build does not have (or need) any of such brute 'hacks' and installing them would only worsen the operation of the unit.
...

The work-around described by Keldo in early 2016 to effectively disable the H-B navdb activation process has been a lucky exploit of H-B's weak FSC file-based navdb activation scheme. Apart from it's dodgy implementation (IMO) initially (that is, inside new shell script mme-becker.sh), the exploit has worked well for many MMI3G/3GP users for 8+ years. Sure, terminating vdev-logvolmgr at the right time has consequences for the end-user (e.g., requiring User-defined mode to update the navdb), but they seem (very) minor to me for the benefit gained (that is, removing the activation related block to the navdb). That said, if the MMI3G > MMI3GP conversion process offered here also solves the problem of navdb activation without the need for a proper FSC file, that's great. For the rest of us, well, that's another matter. --g

 

[JohnS4]

Hi,

I dont have ADS as standard I activated by obd11.

It's a generic car but I don't know if it might change depending on what model is set in the green menu.

It should change. Mine shows an A4 Avant in the display.

 

[TJ001]

Another update,

With help from Mj maps are now working perfectly.

Had a lot of 140 errors when installing and just hit retry and the install continued we also had to tweak a few bits and pieces and at one point Mj pointed put my car was 400 feet below ground 🤣 but finally success and so far the 3GP nav software is working.

Mj has been incredible and he's looking at a bug where the rear parking sensors graphics only flas up briefly.

As far as I can see everything works as intended, only thing i cant see is the battery level which i enabled pre update, and so far no luck converting video clips to play off the SD card but I'm so, so happy I did the update and am so thankful to Mj for the support, advice and patience he has shown.

 

[NucMed]

With help from Mj maps are now working perfectly.

Thanks for the update. Just looking back over your part of the thread, the main glitches (to me) appear to have been with the maps installation (and other items/systems that you modified prior), rather than any problem with the install of the firmware/software modification from mj131, would that be a correct assessment? Cheers.

 

[TJ001]

Prwtty much, only problems were things id added via OBD11 .

Footwell lights
Battery level
ADS
Heater controls displaying on screen

The nav was fine once I added a section I'd missed in the update.

The actual firmware update from Mj was pretty simple and with only a few tweaks after.

Hopefully my cockups will help Mj in future development. 🤣

 

[NucMed]

only problems were things id added via OBD11 .

Great to know, as mine is otherwise stock standard (apart from FW update & maps update), it augurs well for @mj131 's development of the 3 High to 3+ FW/software. Cheers

 

[mj131]

Prwtty much, only problems were things id added via OBD11 .

Footwell lights
Battery level
ADS
Heater controls displaying on screen

The nav was fine once I added a section I'd missed in the update.

The actual firmware update from Mj was pretty simple and with only a few tweaks after.

Hopefully my cockups will help Mj in future development. 🤣

The battery level is a feature that never made it to the original 3g+ units.
I might bring back this feature for all cars (including A6 A7 A8), but it is not of high priority (since it was never available as a stock factory feature on 3g+).

The rest of the options (if some additional things were retrofitted, such as footwell lights) is a matter of selecting/unselecting options in the green menu.


Visual display for parking sensors (if not originally fitted/coded from factory but enabled by manually coding the modules) is an issue with certain old gateways and parking modules, and only if the car has a manual transmission and has no front parking sensors (only rear).
This would also happen if you were to retrofit a real 3g+ unit in the car, however, thanks to TJ001, I was able to record what the parking module is sending and there will be a fix for this very specific nuance soon.