[RetSurfer]

Originally Posted by TurtleBoy

If doing it while driving, you should be letting go of the button as soon as it shuts off. That means the reboot is starting and the screen should come back on during it. When not driving, you should be letting go of the button as soon as you hear anything.

Great, I'll try that

Thank you

[aaaaaaaaaz]

So if I already have an earlier version of id8.5 2023/07.33 then i won’t expect to get a OTA update prompt this time right?

[apw2607]

Its takes about 70 seconds in total from the time you first press the volume button in and release it to initiate the reboot.

If you keep the button pushed in, when the screen does come back on it will just reboot again.

[TurtleBoy]

Originally Posted by apw2607

Its takes about 70 seconds in total from the time you first press the volume button in and release it to initiate the reboot.

If you keep the button pushed in, when the screen does come back on it will just reboot again.

Shouldn't take anywhere near that long, 30 seconds is the mark. Or are you saying the reboot process takes 70 seconds?



https://faq.bmwusa.com/s/article/BMW...language=en_US

[TurtleBoy]

Originally Posted by alanzyy

So if I already have an earlier version of id8.5 2023/07.33 then i won’t expect to get a OTA update prompt this time right?

No, not at all. You will be updated to .53. Still waiting on data but it looks like all of those that have received the OTA so far went from an earlier version of 8.5 to .53.

[aaaaaaaaaz]

Originally Posted by TurtleBoy

No, not at all. You will be updated to .53. Still waiting on data but it looks like all of those that have received the OTA so far went from an earlier version of 8.5 to .53.

Ty

[apw2607]

I can confirm for BMWs point of view. .530 (I-Level) is the fix for CarPlay connectivity issues per SIB 65 27 23

[Boardmember]

Someone call someone and tell them that I have .33 and will go a day where CarPlay connects every time and I’ll have a day where it won’t connect after getting in/out (re-starting) 4-5 times. If this is the fix, hit me. Ugh.

[TurtleBoy]

Originally Posted by Boardmember

Someone call someone and tell them that I have .33 and will go a day where CarPlay connects every time and I’ll have a day where it won’t connect after getting in/out (re-starting) 4-5 times. If this is the fix, hit me. Ugh.

Not following at all. You have .33 and the fix is .53 or higher. Now that the SIB has been issued then you can take it to the dealer and have it updated without waiting for the OTA. This can also be used by folks with 8 to get updated to 8.5.

[aaaaaaaaaz]

Originally Posted by Heavyd

Since I upgraded to 07/2023.53 I have frequent and multiple carplay issues. Phone even doesn’t connect with the car. I had months no issues with the previous software version under 8.5.

Originally Posted by TurtleBoy

Not following at all. You have .33 and the fix is .53 or higher. Now that the SIB has been issued then you can take it to the dealer and have it updated without waiting for the OTA. This can also be used by folks with 8 to get updated to 8.5.

I think he was referring to Heavyd's experience here - he had .33 which did not have carplay issue but upgraded to .53 for some reason and start to see carplay issue. I think this is currently the only case we see like that.

[TurtleBoy]

Originally Posted by alanzyy

I think he was referring to Heavyd's experience here - he had .33 which did not have carplay issue but upgraded to .53 for some reason and start to see carplay issue. I think this is currently the only case we see like that.

I don't think that is what he was referring to but maybe. Heavyd has been the only person reporting a problem with .53 so likely an issue with his phone and not the software.

[aaaaaaaaaz]

Any words US 🇺🇸 OTA starts to roll out?

[TurtleBoy]

I think I see what he is referring to. I should have looked at the SIB rather than apw2607's description. The SIB says the fix is on .30 not .53. When BMW refers to the iLevel using the YY-MM-vvv notation the 5 is dropped to get the sub version. So in the case of this SIB, using 23-07-530 means 07/2023.30 in iDrive version speak.

[Boardmember]

Yea I understand a confused response to my post.

I’m 90 min away from my dealer, the point being that’s three hours in a day that I infrequently have.

If I can get the OTA and that fixed it, that’s awesome and would soon cause me to forget my frustration with this. (I’ve spent many years with CarPlay and have become dependent apparently)

I called Genius. The nice lady told me rebooting wasn’t good for my car, then told me to long boot by holding the button continuously for three successive cycles, which I’ve not done before. Of course CP appeared, as it will after a single reboot.

I’ll see. And will report. But im confident a dealership visit will be imminent. 3800 miles. Too soon for any ancillary service.

[nZtiZia]

the long reboot for three cycles is a telematics reboot (compared to one cycle for an iDrive reboot). it won’t address/fix the CP connection issue; it’s helpful regaining vehicle communication with the cloud server:
- fixes non-updating vehicle status in the MyBMW app
- refreshes and installs iDrive apps