[whitewidow]

Originally Posted by PGH_X5

Just saw that Mr. 12 Volt is now offering an NBT MMI. Audi and Porsche folks recommend them often.

https://www.mr12volt.com/collections...ts/p2000-nbtmm

Apparently does not work with ID6. This would be ideal for me as it is lossless audio.

[hagncola]

Originally Posted by Nath4n

pacstealer Not sure what is unclear. When you switch between car's infotainment and MMI the control knob and steering wheel buttons are supposed control only the system which is displayed on the screen. At least that's how it should behave.
After I updated from 21.6.7.116 (which was working as intended) to 23.1.12.117, both the knob as well as steering wheel buttons control both systems at the same time, so e.g. when I move up in the car's infotainment, it moves up in the MMI GUI as well, when I want to check my tire pressure it also stops a music played via MMI, etc.

Did you disconnect the negative terminal of the battery for 5 minutes to check if it help ?

[dws199]

Originally Posted by hagncola

Try without connect the Phone to the car bluetooth and check if it´s working.

Thanks, yes if I disconnect the cars Bluetooth then the issue goes away but obviously I can't then use the cars Bluetooth for calls. Is there any work around?

[hagncola]

Originally Posted by dws199

Thanks, yes if I disconnect the cars Bluetooth then the issue goes away but obviously I can't then use the cars Bluetooth for calls. Is there any work around?

As far as i know, no. It seems the bluetooth connection of the OEM iDrive "steals" the voice button. You can use "hey siri / hey google" or long press the idrive controller. Maybe you give a try for calls with the mmi box and use the auto calibrate option during a call (ex. mailbox) and use a litte bit louder volume. Change the volume -/+ as long as the result from the auto calibrate is 100 %.

Works for me without issue (no echo) since weeks, never used OEM bluetooth again.

The only point, you can not use the shortcuts 1 to 8 for phone numbers and some phone functions on the cluser.

[PGH_X5]

Originally Posted by whitewidow

What would be the benefit of this over the other MMI devices in this post? Is this compatible with a 2018 f36 with ID6?

I would guess firmware implement and support plus better audio. Mr12V has a good reputation.

[muniz_ri]

Originally Posted by 3zmac

I have a pixel and while my stretch doesn't seem as bad as yours (F25 x3), I haven't found a solution yet. I've been just using it stretched, which bothers me less than having blank areas on the left and right of the screen from the scrap adjustment.

Android Auto SHOULD support any size screen, just like CarPlay does. From the threads linked below, it looks like Android relies on the car manufacturer to tell the phone what size display it should use. Otherwise the phone will use it's best guess, which may either not fill the screen, or may appear stretched. Our MMI devices must not be communicating screen resolution back to the phone the way it expects (it may not be their fault- who knows if the car allows them to detect the resolution first place!), so the phone standardizes the Android Auto resolution as close as it can estimate. I'm not sure how CarPlay gets around this, but Apple has a history of using their own non-standard methods to figure these things out.

https://www.reddit.com/r/AndroidAuto...id_auto_fully/

https://support.google.com/androidau...r-screen?hl=en

There may be a way to mess with it in developer settings, but I'm not seeing an AndroidAuto setting in my developer settings. Next time I'm in my car I will connect and see if I AndroidAuto customizations pop up in developer settings.

Again, this is all a guess- I could be way off in how all of these thigns work so don't necessarily take my word for it.

You are correct. The mmi sends the resolution/aspect ratio and dpi ("density") values to the phone. The problem with all of the mmi's, except Bimmertech's, is that they are sending the same resolution value for both 8.8" and 10.2" screen, i.e. 1280x480. This is why the display appears stretched on 10.2" screens. Bimmertech's mmi sends a resolution of 1280x480 for the 8.8" screen and 1440x540 for the 10.2" screen.

As a side note, the dpi values change the size of the screen elements and they also trigger changes in the layout. For example, in the attached pic the eta bar at the bottom is displayed much smaller than usual after increasing the dpi on my Carlinkit unit.

[dws199]

Originally Posted by muniz_ri

You are correct. The mmi sends the resolution/aspect ratio and dpi ("density") values to the phone. The problem with all of the mmi's, except Bimmertech's, is that they are sending the same resolution value for both 8.8" and 10.2" screen, i.e. 1280x480. This is why the display appears stretched on 10.2" screens. Bimmertech's mmi sends a resolution of 1280x480 for the 8.8" screen and 1440x540 for the 10.2" screen.

As a side note, the dpi values change the size of the screen elements and they also trigger changes in the layout. For example, in the attached pic the eta bar at the bottom is displayed much smaller than usual after increasing the dpi on my Carlinkit unit.

Hi

Is there anyway to change the DPI setting for the Roadtop MMI? I assume you've repackaged your own firmware for your Carlinkit version?

[whitewidow]

Originally Posted by muniz_ri

You are correct. The mmi sends the resolution/aspect ratio and dpi ("density") values to the phone. The problem with all of the mmi's, except Bimmertech's, is that they are sending the same resolution value for both 8.8" and 10.2" screen, i.e. 1280x480. This is why the display appears stretched on 10.2" screens. Bimmertech's mmi sends a resolution of 1280x480 for the 8.8" screen and 1440x540 for the 10.2" screen.

As a side note, the dpi values change the size of the screen elements and they also trigger changes in the layout. For example, in the attached pic the eta bar at the bottom is displayed much smaller than usual after increasing the dpi on my Carlinkit unit.

What carlinkit device are you using? All i want Is Android auto. I have factory carplay but from what I gather the carlinkit needs carplay over USB and apparently my 2018 f36 can only do wireless carplay?

[Chris567]

Originally Posted by hagncola

If you using AUX, on MMI menu exist audio settings (general, music, navigation, voice (siri) . If you using fully bluetooth (phone and "music") it will not work to have different levels (as far as i know).
More infos about your system, firmware would help.

I also have a problem with the volume over BT. Music volume is fine when playing by itself. Speech (eg driving directions) are fine when playing by themselves. But when music is on and speech is on both play at a low volume. In AUX it works fine -- the music becomes faint and speech plays at regular volume when both happen; but this isn't happening with BT. I emailed Roadtop and they were researching it.

[ADHD]

Originally Posted by pacstealer

in my case i didnt need to connect any cable; just connect the BT of the phone to the car and then to the MMI box, switch mode to AUX in the car and that's it

Ya bluetooth is connected to Carplay and bmw31??? and the Wifi is connected to the Carplay. I set the CD/MULTIMEDIA setting to aux and it does NOTHING>> If I plug in the phone on the usb (charger) and go back in the settings and set it to IPHONE on USB the volume works...

i transfered the green Fiber optic cables to the quadlock that goes in the back of the HU but the ROADTOP harness has a AUX plug that there Directions say needs to be plugged into the armrest Aux?

After a little research I Think having a HU_CIC on the NBT setup The Quadlock doesnt have an aux built in.. I dropped the aux wire behind the unit and to the side ran it under the trim to the middle armrest and up through the aux/usb block so its completly hidden except the plug itself plugging into the aux.... It works flawless now every startup..

[ToniCipriani]

Originally Posted by MMcoding

You need to change the settings in MMI box

Go to SETUP -> CarPlay/Android auto -> Auto dark mode set it to ON

This didn't seem to work for me. For my box it seems like there is dark mode for Carplay but not for Android Auto. I tried toggling that option my maps are still daylight bright.

EDIT: So apparently it DOES work. However, it fails to detect if it's at night and the headlights are already on. I have to switch off and on my headlights (I usually leave mine at on), then it detects it correctly.

[dws199]

Originally Posted by hagncola

As far as i know, no. It seems the bluetooth connection of the OEM iDrive "steals" the voice button. You can use "hey siri / hey google" or long press the idrive controller. Maybe you give a try for calls with the mmi box and use the auto calibrate option during a call (ex. mailbox) and use a litte bit louder volume. Change the volume -/+ as long as the result from the auto calibrate is 100 %.

Works for me without issue (no echo) since weeks, never used OEM bluetooth again.

The only point, you can not use the shortcuts 1 to 8 for phone numbers and some phone functions on the cluser.

Thanks for your response, I didn't realise that I could long press the idrive controller instead, I have tried that and it works fine! So I think I'll still with that option, many thanks

[Migz71]

Originally Posted by Nath4n

Anybody has FW update v1.7.x for Android B2?



Here you go:
https://mega.nz/file/61IQTDqJ#cJ_ESk...fCQypaHzBSineY

But to be honest, after I updated the MCU with this, my car controls both the MMI as well as car's system at the same time no matter what is on the screen, soooo...

This is not version 1.7x update its just a mcu update. Is there a 1.7x update out for the Andream mmi's yet? Cheers

[hagncola]

Originally Posted by Chris567

I also have a problem with the volume over BT. Music volume is fine when playing by itself. Speech (eg driving directions) are fine when playing by themselves. But when music is on and speech is on both play at a low volume. In AUX it works fine -- the music becomes faint and speech plays at regular volume when both happen; but this isn't happening with BT. I emailed Roadtop and they were researching it.

If you on the OEM interface with full bluetooth connecten and do the same direct on the phone (music with navigation) i think you have the same audio issue ?

For my opinion, if full bluetooth is used, the mmi interface shows only the picture and does not take care on any sound because it´s connected to OEM. I think there is no possibility to change.

[hagncola]

Originally Posted by muniz_ri

You are correct. The mmi sends the resolution/aspect ratio and dpi ("density") values to the phone. The problem with all of the mmi's, except Bimmertech's, is that they are sending the same resolution value for both 8.8" and 10.2" screen, i.e. 1280x480. This is why the display appears stretched on 10.2" screens. Bimmertech's mmi sends a resolution of 1280x480 for the 8.8" screen and 1440x540 for the 10.2" screen.

As a side note, the dpi values change the size of the screen elements and they also trigger changes in the layout. For example, in the attached pic the eta bar at the bottom is displayed much smaller than usual after increasing the dpi on my Carlinkit unit.

Maybe dip switch 1,2,3 and 4 are needed


6.5 inch:
11000000
8.8/10.25 inch:
11100000
tip:
If the installed car model screen is 10.25inch, please use dip switch code 1111
0000 first

[ToniCipriani]

Originally Posted by LOLMEE

Road Top unit cant connect again Android Auto it appears a message saying .

Android Auto cannot connect right now
When its safe to do so
Please check Android Phone

It worked last days but now its dosnt connect to it. Wireless and bluethoot works

I get the same message on one of my phones, one running Android 11. Another running Android 14 connects fine most of the time. Sometimes it gets stuck on the waiting on device screen, I have to cycle my ignition, then it starts working.

Trying to get this sorted out with the Aliexpress seller but not proving too helpful, and Road Top themselves won't help me (via the WhatsApp number).

[ToniCipriani]

Originally Posted by sbrook02

The dark/light mode switching of the maps is not based on day light, but on the car headlight status. If the headlight is on, the maps will be displayed in dark mode even if it's during the day. If you car's headlight mode is automatic, then the map switching is automatic as well.

This didn't seem to work for me. I drove one night and the screen dazzled me with a daytime map. Is there a setting for this on the box?

The closest I found was an "Auto Carplay Light/Dark Mode", but I'm using Android Auto.

[ToniCipriani]

Originally Posted by ToniCipriani

So I just finished installing the Road Top box on my car with HU_ENTRY, got the "CIC High 6-pin" variant, which turns out to be just the NBT version.

So far everything seems to work out of the box, audio passthrough works through the quadlock and didn't need to use the Aux Cable, even microphone seems to all work (I couldn't confirm whether it was pulling audio from the phone or the car's mic, though).

I'm primarily using this for Wireless Android Auto, however connectivity seems a bit finnicky. Android Auto starts fine on my primary phone (Motorola ThinkPhone with Android 14), but refuses to start on my backup (Motorola One Hyper with Android 11). It connects to Bluetooth and Wi-Fi, but when Android tries to start, either I get stuck on the waiting for device to connect screen or I get "failed to recognize device". Haven't tried wired Android Auto though. Phone tries to reconnect via Bluetooth and Wi-Fi and seems to keep looping on that.

Furthermore, I'm noticing if I don't start the car and just the radio, Android Auto doesn't seem to want to connect either. When I start Android Auto when the car is off it prompts me to stop YouTube (the app on the box, not my phone), but then I also get stuck on the waiting on device screen when this happens.

Anyone seen something similar?

So after some more testing, It's still not working perfectly, but I'm finding ways to workaround this:

- If the car's ignition is on and it doesn't connect, opening the YouTube or Autolink app to force Android Auto to quit, then re-opening Android Auto seems to fix it. This seem to happen if the MMI box only recently disconnected your phone, e.g. if you just stopped the car to go into a store to buy something and get back into the car.
- In "low power mode" (i.e. if the car is completely off and you press the radio knob to turn on), Bluetooth doesn't seem to want to stay connected. Holding the Back button would reboot the box usually fixes it. Also in this mode, for whatever reason, the YouTube app seems to auto start.

[ToniCipriani]

Originally Posted by fe7565

My Carlinkit did that. My Road Top (Pangolin brand offshoot) does not. Must be a firmware issue. Just to make sure, may want to go through the pain of completely erasing the Bluetooth setup in the OEM head unit and in the MMI and redo them again.

Question: is your phone with you when you are out of the car for a short time? Ad if yes, are you far enough from the car to break the bluetooth and/or wifi connection?

Edit: I think the reason it reconnects fine after a longer time is because the car goes to sleep and powers down the MMI as well...breaking all connections. When you enter the car again, it reboots from scratch and connects OK according to the designed MMI protocol sequence.

But, when you only leave for a short time but far enough to break the bluetooth and wifi connections while the MMI still stays powered up...the MMI's internal software protocol may not connect back to the bluetooth and/or wifi automatically. That's because the Chinese clowns that designed the software did not properly test for all situations. And they did not make the source code available in an open source format so people can fix it. Quality is not the #1 priority when you have enough dumbasses (like me) to buy their half-ass products.

One thing that could be done is to do some tests to confirm if the bluetooth and/or the wifi loss leads to a "no-reconnect" problem in all cases. Since we cannot get into the MMI firmware (I think Firefly1337 managed to hack it in the early versions) to fix the crap MMI coding, instead could use an Arduino or else to detect when the bluetooth and/or the wifi is disconnected from the MMI and then force a reboot of the MMI which will also fire up the re-connect-protocol next time it detects your phone in range.

This is the exact problem I'm having with mine right now, ironically mine is a RoadTop box.

I'm having a hard time explaining this to the seller though.

[fe7565]

Originally Posted by ToniCipriani

This is the exact problem I'm having with mine right now, ironically mine is a RoadTop box.

I'm having a hard time explaining this to the seller though.

Try the latest CUST Version 176 that was posted here some 20 pages back. It seems to re-start (sort of) CarPlay when losing the binding. It's not rebooting MMI, just CarPLay.

[ToniCipriani]

Originally Posted by fe7565

Try the latest CUST Version 176 that was posted here some 20 pages back. It seems to re-start (sort of) CarPlay when losing the binding. It's not rebooting MMI, just CarPLay.

Mine currently says BR504... seems like I have different hardware?

The MCU version does match the one mentioned a few times here.

[fe7565]

Originally Posted by ToniCipriani

Mine currently says BR504... seems like I have different hardware?

The MCU version does match the one mentioned a few times here.

Yes, I don’t recognize that firmware. If you install Road Top firmware it will probably brick it.