[park]

Originally Posted by serge858

If the issue persists after the SW has been upgraded then it is highly likely the hardware issue, perhaps some screen micro-controller is out of order. Maybe it would be reasonable to return that defective HU and purchase another one.

It only occurs during booting, is it a hw problem, not a sw?

[serge858]

Originally Posted by park

It only occurs during booting, is it a hw problem, not a sw?

I tend to consider that HW issue anyway. But that is only IMHO of course)

[EvntHrzn]

Originally Posted by park

Why is the first boot screen like this?
It occurs randomly and is the same even though the MCU was updated as suggested by the seller.
The APP is also updated to 2.5.8

https://youtu.be/mQZp__VzGl0

This is the issue that I had that took almost a month to resolve. In the end, the seller could not figure out what was going on, and I had to replace it. The second unit had the same issue. I then waited until the seller supposedly looked into it. After a few weeks, they assured me that they had new units on hand that did not have this boot corruption.

They were unable to tell me what the issue had been, but since I had 2 units that were both like that, and we tried a mind-numbing amount of software fixes that didn't work, it's very likely it was hardware related. In which case, you will just need to get it replaced.

Feel free to look back at my posts, as there are many that I made in trying to get the community's help with this, but the short version is that the only fix is to replace it and hope you get a good unit, unfortunately. Otherwise, you will drive yourself mad applying all the software fixes that your seller tells you to, which will do nothing.

Mine was the AVIN 12.3" Popout HU for my F10. The one that I have now (the 3rd replacement), is working like a charm and has been for over a month now. I wish you luck!

(I am curious to know if you have any sim card inserted into your unit? Just a pet theory of mine that may not lead anywhere, but I would like to know if you don't mind)

[pierreye]

Originally Posted by serge858

I didn't like the image quality of CVBS camera on HD screen (it was blurry), though it was just fine on my previous SD screen, also some annoying camera delay appeared. So then I swapped it to AHD camera which solved both issues.

So if I swap both front and rear camera to AHD, will that work? My camera is integrated into the trunk handle and so far can't find any AHD camera that will fit like OEM.

[pierreye]

Originally Posted by park

It only occurs during booting, is it a hw problem, not a sw?

What brand did you get? Just to understand if it only affect certain brand/model. As per my understanding, there's slight different between Mekede/Navifly vs AvinUSA.

[serge858]

Originally Posted by pierreye

So if I swap both front and rear camera to AHD, will that work? My camera is integrated into the trunk handle and so far can't find any AHD camera that will fit like OEM.

I tried to connect both AHD cams just for tests but without success. Not sure what was wrong, but F_cam wasn't active by some reason.

You can change your handle for OEM one without the camera and then use universal AHD camera https://ali.onl/1Gat

But don't use AHD rear and CVBS front they won't work together. AHD is getting noisy (or even No Signal) after switching to CVBS.

[pierreye]

Manage to install the head unit. My rear cam is activated when put in reverse but when I change gear to D, it still display rear camera. I connect both front and rear camera red power cable to the +12v output from HU. Or should I use 360 camera wire?

Also, how do I increase the width for the parking line? It’s a bit too narrow for my camera.

Current MCU Ver: 023055dGS-NBT-GTH-DC-200922
APP Ver: Ksw-Q-Userdebug_OS_v2.3.0

Should I upgrade to v.2.3.6 image attached in the first post? I wouldn't try the latest v2.5.8 due to Memory Kill function

[Aquastevae]

Sorry, but I've gone completely through this thread from the OP, I see info about avoiding buying fake units, and how to upgrade the Android versions. But what I don't see is anything about what are the trusted companies to buy Android HU's for specific model BMW's. For example, my car is a E92, and my space looks different than any I saw on Ali Express. Also, I'm looking for a unit that replaces my Idrive screen, not that goes on top of my AC unit. Any information anyone can provide me, is very much appreciated.

[serge858]

Originally Posted by pierreye

Manage to install the head unit. My rear cam is activated when put in reverse but when I change gear to D, it still display rear camera. I connect both front and rear camera red power cable to the +12v output from HU. Or should I use 360 camera wire?

Also, how do I increase the width for the parking line? It’s a bit too narrow for my camera.

Current MCU Ver: 023055dGS-NBT-GTH-DC-200922
APP Ver: Ksw-Q-Userdebug_OS_v2.3.0

Should I upgrade to v.2.3.6 image attached in the first post? I wouldn't try the latest v2.5.8 due to Memory Kill function

Never tried 360 camera wire, you may try. Also I think the rose Camera DET wire supposed to work with 360 camera.

You cannot change the parking lines width. I think it is software issue that these lines are too narrow on HD screen due to high resolution.

There's no much sense to update 2.3.0 FW but you may try.

[serge858]

Originally Posted by Aquastevae

Sorry, but I've gone completely through this thread from the OP, I see info about avoiding buying fake units, and how to upgrade the Android versions. But what I don't see is anything about what are the trusted companies to buy Android HU's for specific model BMW's. For example, my car is a E92, and my space looks different than any I saw on Ali Express. Also, I'm looking for a unit that replaces my Idrive screen, not that goes on top of my AC unit. Any information anyone can provide me, is very much appreciated.

Can you post your dash picture with the screen you want to replace please. Tnx

[pierreye]

Originally Posted by serge858

Never tried 360 camera wire, you may try. Also I think the rose Camera DET wire supposed to work with 360 camera.

You cannot change the parking lines width. I think it is software issue that these lines are too narrow on HD screen due to high resolution.

There's no much sense to update 2.3.0 FW but you may try.

Thanks for the reply. I'll try to troubleshoot my front camera issue. If this doesn't work, I might try out car camera video converter that will automatically switch between rear and front camera. Hopefully this box also work with AHD camera.

https://www.aliexpress.com/item/3225...4%2316062%2321

[serge858]

Originally Posted by pierreye

Thanks for the reply. I'll try to troubleshoot my front camera issue. If this doesn't work, I might try out car camera video converter that will automatically switch between rear and front camera. Hopefully this box also work with AHD camera.

https://www.aliexpress.com/item/3225...4%2316062%2321

I tried similar controller box with AHD cameras and mix AHD/CVBS, without success, though it worked fine with CVBS cams.

[pierreye]

Originally Posted by serge858

I tried similar controller box with AHD cameras and mix AHD/CVBS, without success, though it worked fine with CVBS cams.

I also asked the seller GreenYi regarding AHD camera using the controller box and confirm no go. Also I think the reason the camera never switch to front camera is the rear camera is still active from the +12v supply although switch to D mode. As long as distance control is active, the rear camera will get the +12v power and will activate. I'll try to disconnect the rear camera to check if that will switch to front camera. If this work, then I need to tap a relay from the reverse light that will cut the power from the rear camera when switch to D.

[Mortenmyre]

Originally Posted by Kri

I checked the update in comparison to 2.3.6 (and 2.5.4) , this version 2.5.8 is from 27th November 2020.

As update 2.5.4 interim update to the new gui, i didn`t do a seperate changelog


The update can be found here:
https://mega.nz/file/9QYx1QJQ#fGCpdA...FjHTvDEHh2pwKA

ro.build.display.id=Ksw-Q-Userdebug_OS_v2.5.8
ro.build.version.incremental=eng.zlx.20201211.173029
ro.system.build.date=Fri Dec 11 17:30:12 CST 2020
ro.system.build.fingerprint=qti/msm8953_64/msm8953_64:10/QKQ1.191008.001/zlx12111730:userdebug/test-keys

ro.build.display.id=Ksw-Q-Userdebug_OS_v2.5.4
ro.build.version.incremental=eng.zlx.20201203.161435
ro.system.build.date=Thu Dec  3 16:14:18 CST 2020
ro.system.build.fingerprint=qti/msm8953_64/msm8953_64:10/QKQ1.191008.001/zlx12031614:userdebug/test-keys

I found no changes regarding memorykiller, so if you have no issue with your actual 2.3.6 is see no reason to update so far.

• Feature: New GUI ID7_ALS, inluding Music/Video player and Settings page all in a blue design
• Feature: Speedplay now setup able via Factory config file , but unknown which license is requires.
• Update: Centerservice updates to target Hicar and Speedplay
• Update: EasyConnected update targeting better Scaling

Attachment 2485211
Attachment 2485212
Attachment 2485213
Attachment 2485207

Speedplay apk:
Attachment 2485220
Attachment 2485221
Attachment 2485222

Factory Config file 2.5.8:

• Added: Gui ID7_ALS
• Added: GUI ALFA Romeo
• added maps support list for Igo map Israel & luna, T map (south korea)
• added: ZLink /Speedlink app switch

Download:
Attachment 2485215
Attachment 2485216

Kri

What is speedplay!? A app like zlink? Is it better

And what about the update is it better than 2.5.3
Because I got issues with auto Bluetooth connection and idrive control in android auto

[Sjaakkoni]

Just a question for the experts.

I bought a HU 10.25 with Android 10 through navifly.

However, I don't have a display from the original unit. The car is an F21 from 11-2016. I believe an ID5 (prof nav) without a touchscreen.

Obviously everything checked three times and the cabling is good

MCU ver: 023055dGS-NBT-GTH-DC-201117
App ver Ksw-Q-Userdebug_OS_v2.5.3

[03]NBT_F30/F20/F15/F22/F48(8.8",10.25")

Do you know if this combination would work?
My Chinese friend is having to wait a little longer with answers ..

Thanks

[Gold007]

Hi there.
I need a little help. I upgraded to 2.5.8 onto everything going except ID5 and ID6 don't work, only ID7.
does anyone know what the problem might be?
Thanks for the help.

[serge858]

Originally Posted by Sjaakkoni

Just a question for the experts.

I bought a HU 10.25 with Android 10 through navifly.

However, I don't have a display from the original unit. The car is an F21 from 11-2016. I believe an ID5 (prof nav) without a touchscreen.

Obviously everything checked three times and the cabling is good

MCU ver: 023055dGS-NBT-GTH-DC-201117
App ver Ksw-Q-Userdebug_OS_v2.5.3

[03]NBT_F30/F20/F15/F22/F48(8.8",10.25")

Do you know if this combination would work?
My Chinese friend is having to wait a little longer with answers ..

Thanks

Would work for what? If your question is about Display settings for OEM menu then I suppose you need to choose Car without OEM display, you will have only a clock on OEM menu.

[Sjaakkoni]

Originally Posted by serge858

Would work for what? If your question is about Display settings for OEM menu then I suppose you need to choose Car without OEM display, you will have only a clock on OEM menu.

What I mean is I get "no signal" on display. The android works well and so does the idrive.
However, no signal from the original unit.

edit:
I found out I have a NBT/EVO system. Will that work anyway?

[DiegoXSnake]

Hi, I bought an android 10.25 screen for my F30, it lasted about 2 months and now it looks like this:

I only have the iDrive enabled perfectly, but the android disappeared and only throws this image, the touch does not work either.

There is a button on the back of the screen but it does nothing more than turn the screen off and on, I have pressed it for a few seconds and it does nothing.

Please help.

Does anyone know how to perform a recovery or a hard reset to recover the android or how it was originally?
Thanks a lot!

[EvntHrzn]

Originally Posted by DiegoXSnake

Hi, I bought an android 10.25 screen for my F30, it lasted about 2 months and now it looks like this:Attachment 2491390

I only have the iDrive enabled perfectly, but the android disappeared and only throws this image, the touch does not work either.

There is a button on the back of the screen but it does nothing more than turn the screen off and on, I have pressed it for a few seconds and it does nothing.
Attachment 2491391
Please help.

Does anyone know how to perform a recovery or a hard reset to recover the android or how it was originally?
Thanks a lot!

Take a look at the first page, first post, and scroll down to SD 625 OTA Recovery installation. That should give you all the information you need to restore your unit to the firmware you want. However, it is no guarantee it will resolve the specific issue you are having.

If after doing that, you still have the issue, then more knowledgeable members than myself may be able to help you. Good luck.

Also, a quick search, or taking a look at the first post of this thread, would have given you this information. Just an FYI for the future. Loads of useful info there.

[DiegoXSnake]

Originally Posted by EvntHrzn

Take a look at the first page, first post, and scroll down to SD 625 OTA Recovery installation. That should give you all the information you need to restore your unit to the firmware you want. However, it is no guarantee it will resolve the specific issue you are having.

If after doing that, you still have the issue, then more knowledgeable members than myself may be able to help you. Good luck.

Also, a quick search, or taking a look at the first post of this thread, would have given you this information. Just an FYI for the future. Loads of useful info there.

Thanks for answering. But there it talks about restarting the system, how do I restart the system if I can't see anything on the screen?

[EvntHrzn]

Originally Posted by DiegoXSnake

Thanks for answering. But there it talks about restarting the system, how do I restart the system if I can't see anything on the screen?

You said in your post that there is a button on the back of the screen that turns it off and on? Typically this is the reset button which you can use to restart the system.

If you followed the instructions on page one correctly, when your system restarts, it should see the recovery file (make sure both the file and the USB drive are named properly as per the instructions). If you know that your system is restarting, and you know for sure the Recovery procedure was followed correctly, but it's still not working, you may have a dead unit.

But perhaps someone else can chime in.