I've an "insider" in MB Portugal, who told me that MB decided to ignore this "small issue" (they're words) in order to allocate all resources in the new mbux etc etc
so... they will not, almost for sure, fix this..
this weekend i will order the box
It is all bs as after the FUP3 update which changes the system to apilevel/ntg6/081 - there is a change to allow Baidu Carlife in China regions to use the whole resolution from using 1280x720 resolution to the custom 1600 x 600.
They even sell adapters around 400CNY to convert Baidu Carlife to Apple Carplay keeping full-screen conversion as well on the native system. I have tried to enable CarLife capable on HU6 System Activation - the menu option doesn't even appear in licenses after coding.
I have tried many different coding options in DTS but it is based on the same system activation as AA/Carplay so requires Device Key to provided by MB to be manually activated or for MB to remotely activate with certificates. Someone probably knows the device key generation algorithm...
I wonder if asking MB if I purchased the smartphone integration package, surely I should be able to have Carlife as well. I did try the Carlife app on my iPhone and the car doesn't detect this mode.
I did try changing remote ui parameters in HU6 to China but the car fails to accept the coding with an NRC22 error - there's also a parameter for TEST_CARPLAY but unsure if this is just a pre-development feature of maybe the Carplay navigation/media feature transfer to IC cluster or if this is a widescreen mode in some beta.