[ooati]

Just wanted to give info on my install I completed early last week in my F10. I did get the 12.3" version from Kanor.

I completed what I call my phase 1 complete install. Unit works as advertised and expected. Having done a lot of research prior and thanks to all the information and answers shared here, I knew what to expect in terms of both install and functionality.

I followed the video install on YouTube (007Serge's and NYST8FMIND's).

One variation in my install was using an InStock GPS210 splitter to split the OEM GPS signal between the OEM and Android HUs. Works perfectly (see picture attached).

Here are links to the Fakra to Coax connectors I used:
2x Female Fakra to Male Coax
1x Male Fakra to Male Coax

The goal, in addition to sharing the GPS signal, is to prevent the Android HU from sending DC power which could damage the OEM GPS equipment.

Basic functionality works, WiFi, maps, music, bluetooth, Android Auto and other apps.

As I've read here in the forum, audio integration seems to be some peoples' main gripe. However, it works fine for me in terms of using the OEM mic and speakers.

While there are a few options of playing music, I have settled to use the Amazon Prime app on the Android HU as the primary means to playing music. I did test playing music from my phone via bluetooth connection with the Android HU. Playing music using the Android music player is definitely going to be the least (and probably never) used option.

Looks like I am also able to use the OEM mic with Google Maps.

Right now, I only have my phone connected via bluetooth to the OEM unit for calls. As such when calls come in or go out, they still use the OEM mic and speakers.

I also have my phone as a hotspot for the Android HU.

I have heads-up display and OEM 360 camera in my car. The OEM 360 camera still works fine when I put the car into reverse.

Wireless Android Auto was initially one of my most wanted features. However, I think I have settled to use apps natively on the Android HU instead. I still need to do more testing. At the very least, I know wired AA works as expected. The one caveat is that the USB connection to the Android HU doesn't seem to be powerful enough to charge my phone. As it stands, AA will only be useful for getting email and messaging from my phone.

For anyone interested - here is my experience testing with wireless AA. It works as it should with my S9+. In addition to the dependency on the android phone supporting wireless AA, what I discovered from my testing is that the phone needs to be paired via bluetooth for calls with the Android HU, otherwise wireless AA won't work. I tried enabling the paired connection for audio only but wireless AA wouldn't work because my phone and the android HU wouldn't stay paired. As an FYI, the way AA auto works is that it starts a hotspot on the compatible HU, in the case the android HU, and then forces the phone to connect to the hotspot. As long as the phone stays connected to the hotspot, AA keeps working. In my tests, once my phone connects via bluetooth with the android HU (and enabled for calls) AA begins to look for new car connections and one just needs to start Zlink for the wireless AA connection to complete.

In addition, my tests show that Head Unit Reloaded (HUR) also works as excepted when connected to my phone's hotspot. I just have to set AA on my phone to "Start head unit server" and then have HUR connect via WiFi.

Phase 2 will be incorporating a USB DAC and installing OEM single USB and USB/AUX-IN sockets in the glove box. Right now, I have the USB cables run into the glove box via the cutout for the USB socket. Everything works as it should now, just want to improve sound quality and give the OEM look in the glove box.

I have the wires with male and female 3.5mm ends as well as the 4-pin socket harness I got from ECS.

Frankly30 Do you or anyone know the AUX socket 4-pin connection mapping to the 3-pin left, right and ground 3.5mm AUX connectors?

[carlosdelajonquera]

Originally Posted by carlosdelajonquera

Hello
i have a problem to connect my phone on the ANDROID HU.
I can connect it but after 1 sec it's deconnected.
I try to install another firmware 2.3.6 bu same problem.
I think the state of bluetooth doesn't work and the programme close.
Do you have any solution??

Problem solved with re installation of factory_config.xml and conexion to wifi.
My phone is well connected now

[RedErik]

Originally Posted by ooati

Frankly30 Do you or anyone know the 4-pin connection mapping to the 3-pin left, right and ground 3.5mm connectors.

4 pin AUX connector is:
1 - shield
2 - GND
3 - AUX R
4 - AUX L

[serge858]

Originally Posted by ooati

Just wanted to give info on my install I completed early last week. I did get the 12.3" version from Kanor.

I completed what I call my phase 1 complete install. Unit works as advertised and expected. Having done a lot of research prior and thanks to all the information and answers shared here, I knew what to expect in terms of both install and functionality.

I followed the video install on YouTube (007Serge's and NYST8FMIND's).

I have also received 12.3 HU for F01 from Kanor, installed it recently.
Video is below.

Just wanted to share my first impressions. Frameless BIG display looks great! My 10.25 in comparison looks so small after 12.3)
Works fast as expected.

This is my first screen with the Blue Ray option as Chinese sellers call it. In reality it is violet anti-glare film on the screen that prevents reflections BUT makes an image a bit blurry and negatively affect on view angles.

Definitely much better is anti-glare coating that goes on 10.25 HD GS screens.

In general, 12.3 looks fresh and natural in F01, should be the same in F10 but in E70, E84 IMO for extreme users only))

[serge858]

Originally Posted by RedErik

4 pin AUX connector is:
1 - shield
2 - GND
3 - AUX R
4 - AUX L

Here how it is visually:

[meloh]

I'm trying to figure out if this player supports DAB+

KANOR
https://www.alibaba.com/product-deta...103825615.html

Or do they all support this?

[RedErik]

Originally Posted by meloh

I'm trying to figure out if this player supports DAB+

KANOR
https://www.alibaba.com/product-deta...103825615.html

Or do they all support this?

None of them does. You need to get a DAB+ antenna with USB for Android and then you can download any DAB radio app.

[engelj13]

Originally Posted by serge858

I have also received 12.3 HU for F01 from Kanor, installed it recently.
Will post a video soon on Youtube)
Just wanted to share my first impressions. Frameless BIG display looks great! My 10.25 in comparison looks so small after 12.3)
Works fast as expected.

This is my first screen with the Blue Ray option as Chinese sellers call it. In reality it is violet anti-glare film on the screen that prevents reflections BUT makes an image a bit blurry and negatively affect on view angles.

Definitely much better is anti-glare coating that goes on 10.25 HD GS screens.

In general, 12.3 looks fresh and natural in F01, should be the same in F10 but in E70, E84 IMO for extreme users only))

Where did you obtain that M Screen?

[serge858]

Originally Posted by engelj13

Where did you obtain that M Screen?

This is boot logo animation made by RedErik, available here in the thread or here:
https://mega.nz/folder/m4F03TaS#k7jsBqvPW8_u_W15FeirKg

[RedErik]

Originally Posted by engelj13

Where did you obtain that M Screen?

More info here:
https://f30.bimmerpost.com/forums/sh....php?t=1719625

[sickF30]

this thread is insane. lol

anyone have a link to a reputable seller for an android 10 unit?

[serge858]

Originally Posted by sickF30

this thread is insane. lol

anyone have a link to a reputable seller for an android 10 unit?

Search for Ebilaen on Aliexpress or Kanor on Alibaba. Both are dealing with GS brand HUs and have a good service and of course good prices.

[Kri]

I checked the update in comparison to 2.7.9, this version 2.8.3 is from 9th April 2021.

Update can be found here:
https://mega.nz/folder/kIB3CSZD#wnqmCQnF8i7VW1yIEvz66g

ro.build.display.id=Ksw-Q-Userdebug_OS_v2.8.3
ro.build.version.incremental=eng.zhanji.20210409.223546
ro.system.build.date=Fri Apr  9 22:35:22 CST 2021
ro.system.build.fingerprint=qti/msm8953_64/msm8953_64:10/QKQ1.191008.001/zhanjianquan04092235:userdebug/test-keys

Finally a Update that seems to be worth to install again
This Update has alot of changes due to the ZLINK-HICAR implementation, so maybe we missed some other changes at the code.

The behavior of Memory Killer has been updated, apps will now be killed when there is only 20% of RAM free anymore, before it was at 40%.
At normal usage this should be set fair enough to not trigger the app killing feature anymore, so i call it fixed.
If you still face app killing issues, please check with a RAM Usage tool like "RAM Monitor -Floating Widget" which app does consume so much memory, its then proably more a memoryleak issue of that specific app.
However there will soon be a mod available to disable Memorykiller at all, but this requires a deeper changes, is always locked to one specific OTA file and will be used at your own risk

Now the changelog of this update:

• Bugfix: Memory Killer Issue resolved, Threshold lowered from 40% to 20%, Apps will be not killed at normal usage as fast as before anymore !
• Feature: Added Huawei ZLINK-HICar 2.0.2 (Android Auto alternative)
• Feature: Added thai and greek language strings to some of the apps
• Feature: Zlink Touchpointer support ?!?!?
• Update: Zlink updated to version 4.0.7 - sourcecode has been encrypted now, no changelog/analyzing possible anymore !
• Update: Found specific code changes which seems to lead to a preperation for Android 11.
• Update: LTE-Baseband specific behavior for MSM8917 (SD425) headunits has been added
• Update: Audio Drivers, as always changes/fixes unknown

I also made a new set of factory_config.xml files, as some things are new:

• Added Yanosik to supported Navi Apps
• Added "com.ankai.ardvr" to supported "SupportedDVRAppList"
• Added samples of GUI-Name renaming support, GUI`s can now have custom names
• Added Can Protocol "BC_Protocol_type_3.0" for Mercedes
• Added: Zlink-HICar switch

Factory_config_BMW_A10_283.zip
Factory_config_Audi_A10_283.zip
Factory_config_Mercedes_A10_283.zip

A Noticeable change is that Factory Settings do now support changing GUI Names to whatever you want
This is probably more useful for company use to Change GUI Names to reflect their BRAND, or to remove Car Manufacturer Names due to legal issues

This is how the Line does look alike

<Item id="5" name = "BMW_EVO_ID7" display = "FANCY NEW INTERFACE" />

Kri

[rodriguezstyle]

Cool News!!!

KswRedirect works with 2.8.3 ?

[EvntHrzn]

Hi Kri,

There are a couple of random ´ in the <SupportUIList> section in your Factory_config_BMW_A10_283.zip, and they are outside of the comment tags.

I haven't tried this build yet so I don't know if this will have any negative impact on the functionality of the units as it pertains to those lines of code (Best case scenario, they will just be ignored, I don't know).

I deleted them from my own file, but I figured I'd point this out in case they do end up causing issues for anyone. (You have PM turned off so I couldn't message you privately).

Thanks for all your work!

[Viresh87]

My aftermarket rear camera has not been working properly. Sometimes the camera works and sometimes it doesn't. I will then see this message.

How can I fix this?

[Serg B.]

Originally Posted by EvntHrzn

Hi Kri,

There are a couple of random ´ in the <SupportUIList> section in your Factory_config_BMW_A10_283.zip, and they are outside of the comment tags.

I haven't tried this build yet so I don't know if this will have any negative impact on the functionality of the units as it pertains to those lines of code (Best case scenario, they will just be ignored, I don't know).

I deleted them from my own file, but I figured I'd point this out in case they do end up causing issues for anyone. (You have PM turned off so I couldn't message you privately).

Thanks for all your work!

The same "´" is also found in Factory_config_BMW_A10_263. Everything works without problems.

[EvntHrzn]

Originally Posted by Serg B.

The same "´" is also found in Factory_config_BMW_A10_263. Everything works without problems.

Ah ok, thanks for the heads up. I had not looked at any files since 2.3.6 came out due to not wanting to deal with memorykiller in its previous iteration.

[engelj13]

Originally Posted by RedErik

More info here:
https://f30.bimmerpost.com/forums/sh....php?t=1719625

I tried the tool and have some struggles...any advice?

[RedErik]

Originally Posted by engelj13

I tried the tool and have some struggles...any advice?

Sorry, what tool? What struggles?

[sickF30]

Originally Posted by serge858

Search for Ebilaen on Aliexpress or Kanor on Alibaba. Both are dealing with GS brand HUs and have a good service and of course good prices.

Just ordered from Kanor, thanks!

[sickF30]

Originally Posted by ooati

One variation in my install was using an InStock GPS210 splitter to split the OEM GPS signal between the OEM and Android HUs. Works perfectly (see picture attached).

Here are links to the Fakra to Coax connectors I used:
Female Fakra to Male Coax
Male Fakra to Male Coax

Just bought my unit and I'm going to copy your GPS solution. Can you double check your links though?

It looks like you have 2x Female Fakra to Male Coax (link points to the splitter) and 1x Male Fakra to Male Coax (not pictured, but assuming it connects to the top of the splitter?)