[MysticMan]

Originally Posted by grey78

For me it works better than A12. GPS off problem with Maps solved, smoother and faster apps to load and clearer images. It seems like a worsening of the audio system to me, I preferred the sound of Spotify and Netflix with the A12. Torque works in BT with ELM327 OBD. I think I'll stick with A13 at the moment.

I'm still getting No location access message on A13 sometimes.

[grey78]

Originally Posted by MysticMan

I'm still getting No location access message on A13 sometimes.

I'm using Ksw-T-M600_OS_v1.5.8-ota e no GPS problem like A12 on WAZE, Maps, Life360, all apps work fine. I didn't do a factory reset, just update the software.

[georgiee]

Hello!
Is there any way to fix android head unit with snapdragon 662 which is stuck on boot?

https://f30.bimmerpost.com/forums/sh...postcount=4180
I disassembled the device following Kri's instructions in his post and finally saw that it was for the snapdragon 625.

PS: You try with SD card it didn't work
Thanks in advanced!

[Muzamil]

Originally Posted by car_fings

Hi all,
I am still on A12 (Ksw-S-M600_OS_v1.5.6NEXAI-ota.zip) on my M600 , is A13 now stable ?
A few months ago it was said that A13 had bluetooth and other issues. I a, just wondering how stable that is now ?

Thanks

I bought a 662 in February that came with A13 preinstalled, running version 1.44 (i think) and it worked flawlessly. I mainly use it to stream Tunein Radio from my Samsung Phone thru Android Auto. Yesterday I updated to v1.58 and so far all is good. The one thing I noticed immediately was that the sound quality improved with Android auto on Zlink. The high frequencies improved noticeably. There was a shimmer I never heard before.

Zlink (wired) launched faster too

[stu_c]

Hi all, is it possible to stop the music from switching off when I go into the original BMW menu and also activate the arrows on the standard radio unit to skip songs etc?

I have currently connected it to my car via the AUX USB in the car using a Jack to AUX adapter

Would be far easier if I could connect the screen via Bluetooth to my Bluetooth audio in my car but the screen for some silly reason doesn't allow you to do a Bluetooth search :rolling_eyes:

Screen: M600
RAM: 8GB
Memory: 128
Android 13

[KevinCorsius]

Hello all, I've recently installed a RoadTop 10.25" HU in my F31. 662 M600 model. Since installing, everytime I start driving, I get a chassis stabilization error. When I stop briefly and take off again, it dissappears and stays away for the rest of the ride. Could anyone tell me what is causing this? I presume something CAN related?

[luckerNo1]

Originally Posted by Shamanix

Guys, meet qualcomm 685 at Hifimax for BMW

Thanks for the information! Seems to only be a tiny upgrade over the snapdragon 662 however. Yes, it has a much smaller manufacturing node (11nm vs 6nm) - so it's more efficient, but since a car isn't a phone, in practice that shouldnt matter much. Heat isn't an issue in a car. So when it comes down to performance, the newer chip clocks quite a bit higher, but it has the same gpu and basically the same specs apart from the higher clock. Disappointing for a "pro" device tbh. They should have gone for at least an 8 gen 1.

Check it out on notebookcheck:
https://www.notebookcheck.net/Processor-Comparison-Head-2-Head.247596.0.html

I'm still looking for which android box to order..

[chumpy]

Originally Posted by luckerNo1

Thanks for the information! Seems to only be a tiny upgrade over the snapdragon 662 however. Yes, it has a much smaller manufacturing node (11nm vs 6nm) - so it's more efficient, but since a car isn't a phone, in practice that shouldnt matter much. Heat isn't an issue in a car. .

I have had issues in summer with performance like stuttering music. I have the 662 and live in Australia.

[car_fings]

A couple of days ago I was driving with the blazing sun facing me, and the back of the head unit, the warning like "your phone is getting too hot" popped up. Has anyone had this issue?
My journey finished within 10 of that, so it didn't progress and continued to work after the message during the journey, it is working OK afterwards too.
I couldn't locate the message in notifications so couldn't screenshot it.