Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Galaxy S22 ultra causes my NBT unit to reboot. #793

Open
TBGR opened this issue Jun 20, 2024 · 2 comments
Open

Galaxy S22 ultra causes my NBT unit to reboot. #793

TBGR opened this issue Jun 20, 2024 · 2 comments

Comments

@TBGR
Copy link

TBGR commented Jun 20, 2024

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?

@hufman
Copy link
Collaborator

hufman commented Jun 24, 2024

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.

@TBGR
Copy link
Author

TBGR commented Jun 24, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants