02-06-2023, 03:28 PM | #1 |
New Member
5
Rep 6
Posts |
Return Of Experience, Android 12, ID8, snapdragon 662 on BMW series 5
Hello,
I post here as most of the android discussions are there, even if this is on a 5 series. If not acceptable, let me know, I'll move it to the 5 forum. As promised, here is a REX on my android HU installation, I’ve solved some issues but some remain (for the time being). Car: I have a BMW Series 5 M550d, 2016, big screen, Bang & Olufsen audio, GPS, Bluetooth call and music, navi…all of that is under NBT connectivity. HU: On aliexpress, I’ve bought a Navifly, Android 12, ID8, 12.3 Qualcomm 662 Android 12 256G blue screen, touchscreen. GPS cable: On aliexpress, I’ve also bought a Fakra GPS “Y” cable with a diode to protect android HU (from what I’ve understood) to be able to connect both android HU and OEM unit GPS. Installation: Nothing really difficult, lot of tuto there and there, but still some note:
Snapdragon issue: As I have read there seems to be a lot of fake units, even if Navifly was a recommended vendor, I checked everything with CPU-Z. The Android version was ok, the only difference was that I had a snapdragon 665 and not a 662 as advised. Not a big deal in terms of performance (thanks for the help on this forum) but sufficient for me to claim a discount, which was accepted for 100€. Audio: This is what was scaring me the most, audio quality for the B&O system. I was ready to potentially use a DAC, but fortunately, I think thanks to the NBT config and thanks to that aux connection into the wiring, Audio is as good as before, no change at all. Clearly don’t understand why as I’m still going through AUX OEM… Mic: As for everyone, the internal headunit microphone is bad. I tried to modify MIC gain without any success, I tried a chip external microphone which was bad also, I tried a better one still bad, I also tried to cut the internal microphone without any improvement and I finally discovered THE solution. Here is the video: https://www.youtube.com/watch?v=fyEPYYKNLLc Roadtop are selling MMI box and provide with these units a “Y” cable to connect the OEM microphone to the android Head Unit in addition to the OEM unit. I asked them if they were ok to sell it apart from the MMI box, they accepted for 30€ port included. I installed it per the video, and I must say that results are above my expectation, voice messages on whatsapp or other stuff are just perfect, and I don't even need to increase MIC gain. Android auto: For the time being I don’t use android auto for the following reason:
Zlink remains usable by launching the app. Tasker: For the moment I’m using tasker to launch phone hotspot, for wifi sharing to get data on the HU. Several guides are available for that. Calls: This is the last remaining part for which I’m not fully satisfied with the use. Like everyone I’m using the OEM calls system but there are still some issues that prevent me from being satisfied, and I don’t desperate to use android calls. Not in the order because I don’t know how to organize my idea:
Here it is, I think I’ve explained everything, I hope it could help as I spent a lot of time on all your forums to find solutions. If you have any question feel free. |
02-06-2023, 07:19 PM | #2 |
Private First Class
140
Rep 160
Posts |
Hello Mils31,
could you elaborate further on that "Y" Splitter cable they supplied to you, like did the cable come with extra circuitry, resistors or some kind? I was considering of achieving something similar, if it were just a dumb Y-Splitter. The Mic is actually wired on the Quadlock itself on NBT, so I wonder what there is that stopped the Android HU devs from just taking Microphone from the Quadlock. |
Appreciate
0
|
02-06-2023, 07:47 PM | #3 | |||
Lieutenant
136
Rep 401
Posts |
Quote:
Quote:
Quote:
Last edited by Mjam; 02-07-2023 at 12:55 AM.. |
|||
Appreciate
0
|
02-07-2023, 03:25 AM | #4 | |
New Member
5
Rep 6
Posts |
Quote:
On top of that even if in my case, there is a 3 pin connector, my OEM mic had only 2 pins inside the connector. I don't understand neither why Android HU dev didn't provide it....and I'm quite surprised to have found this solution working as easy... |
|
Appreciate
0
|
02-07-2023, 03:27 AM | #5 |
New Member
5
Rep 6
Posts |
|
Appreciate
0
|
02-07-2023, 08:41 AM | #6 | |
Private First Class
140
Rep 160
Posts |
Quote:
https://aliexpress.com/item/1005004122915335.html - The Splitter https://aliexpress.com/item/1005003563725244.html - AUX Connector If you don't have the telematic communication box, you could probably even extract those same wires from quadlock adapter without needing to route extra wires through your A-pilar. |
|
Appreciate
0
|
04-29-2023, 07:21 AM | #7 | |
Enlisted Member
7
Rep 35
Posts |
Quote:
Also, the Equalizer app has no effect on sound. Can you verify? If your sound drops when you switch to OEM menu use KSW-Tookit to fix. |
|
Appreciate
0
|
10-25-2023, 12:41 AM | #8 |
Enlisted Member
0
Rep 48
Posts |
hello.
I have the same problem with the microphone, they hear me terribly. Could you give me the exact link for the cable? I can't find it on the roadtop website. Greetings and thanks in advance |
Appreciate
0
|
03-05-2024, 04:52 AM | #9 |
Registered
0
Rep 1
Posts |
Upgrade OEM screen with limited/no changes in wiring
Hi all,
Many thanks for your respective feedbacks, and a particular thanks to Mils31 for all these details. I will also share some experience with my F11 2012 with a CIC system : 1) in 2023 : I installed an MMI box in order to bring Carplay - I had to install the additional wire in order to connect the MMI box with the OEM mic, as shown in the Roadtop video - I had to connect the AUX cable to the OEM AUX plug under the armrest => Carplay works, but screen was not touch sensitive. And the sound was quit horrible. On top of that, the system was freezing sometimes. Hence I decided to replace that MMI and OEM screen by a 10"25 inch screen powered by Linux 2) in 2024 : I replaced the MMI box and old OEM screen with a 10"25 integrated screen powered by Linux and a Sunplus chipset. Installation was really easy : only the harness wire + USB cable. No other cables needed : neither AUX nor Jack for OEM mic ! => And I can tell you : result is really good. 3) Now, I would like to switch to a 12"3 screen, but I am really cautious with the product to choose : I don't want any additional AUX cable, no jack cable for the OEM mic (nor external mic). After some investigation, I understand that : - for screens powered by Linux : no need any AUX cable, no additional mic. All OEM - for screens powered by Android : a. if MTK chipset, then you need to wire AUX b. if Snapdragon, then no need to wire AUX, according to the seller on aliexpress What's your views ? I hope it will be helpful for those who are considering for an upgrade of their OEM screens. |
Appreciate
0
|
Post Reply |
Bookmarks |
|
|