You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The car is a 2014 F10, with a factory NBT with an Apps option/FSC coded in. It connects to my AAIdrive dedicated Android 7 running Galaxy S6 Edge with no issue, but as soon as I try connecting my S22 the Apps connection takes a few seconds to initialize, and as soon as it is estabilished the NBT reboots itself. Tried with MyBMW and a few versions of the Connected Drive apps with no improvement. Is there something that can be done for this or should I stick to the S6 until the battery completely dies?
The text was updated successfully, but these errors were encountered:
MyBMW is flaky with USB support, and your Android 7 version is the last version to support USB audio with the car. I'd recommend sticking with it as long as you can.
I've seen this rebooting problem if multiple BMW apps are installed and trying to talk to the car at the same time. Make sure only one of them is installed.
At first I tried running only ConnectedDrive 6.4. Since it did not work out I tried the other stuff. But the S6 has no storage expansion, and when I tried Tidal on it it stuttered on losless tracks so sooner or later I have to think of something.
The car is a 2014 F10, with a factory NBT with an Apps option/FSC coded in. It connects to my AAIdrive dedicated Android 7 running Galaxy S6 Edge with no issue, but as soon as I try connecting my S22 the Apps connection takes a few seconds to initialize, and as soon as it is estabilished the NBT reboots itself. Tried with MyBMW and a few versions of the Connected Drive apps with no improvement. Is there something that can be done for this or should I stick to the S6 until the battery completely dies?
The text was updated successfully, but these errors were encountered: