[FYT Android Head Units] dishe2:
Interesting, on the Atoto the standard stack is not crippled at all, and they make a big deal about advertising that in their literature, website and manual so I thought it was exclusive to their model. Especially after I heard that other users couldn't get non-branded equipment to pair if unsupported.

If you can access the original AOSP stack from elsewhere in the system, that's a major find imo. It makes sense, I believe the standard SoC relies on a BT/Wifi component, so I always sort of figured there IS an original AOSP bluetooth stack that they masked into a custom app. Atoto just owned up to it and gave access to it directly from the menu and settings.

Here's the thing- even within Atoto's line of devices they aren't the same, so how can it be the same across other devices?

Let's back up a moment- my original concern was that the Atoto units would only reconnect to the LAST device used, not any one else who might have driven the car before and paired. For example, if I drove last, my wife will get in the car and it won't connect to her phone. It will be stuck looking for mine. Can we confirm whether or not other units have this issue? Because it sounds like @marchnz said his does reconnect:

Although it isn't clear if he understood what I was asking. Mine also always reconnected to my phone consistently, as long as no one else ever uses another phone in between. Essentially, you can't share the unit between drivers automatically.

When I explained to Atoto that this is a major problem sharing the car with family members ( even their cheap linux based Atoto F7 can support multiple paired devices), they agreed and said they would need to engineer a solution.

On my S8 (7862), the BT1 app (which I guess is Blink for everyone else?) has its own button under the settings screen to upgrade firmware for the BT chip. This is next to the reset bluetooth button, and that is what was used to change the behavior on that device and make it work the way I wanted. Atoto sent me a fix that gets flashed there. There was no lsec or config file update AT ALL on that model, and if it were a simple config file change they would have just done that.

When I wanted to hard reset everything, including my storage and paired BT units so it was completely like new, they explained to me how to use the twipe command in an otherwise empty update, so it's not like they don't know how that works.

The cheaper A6 PF (8581 chip) does not have the button to upgrade firmware in the BT1 app. Out of the box, it had the same problem as my S8 regarding not reconnecting to other paired devices, so I reached out to the support team that had made the S8 fix for me and asked if it could just be applied there too.

They responded that since the A6 uses a totally different BT system, their engineers would need some more time to make an update that would fix it.

Within about 2 weeks, they released an update for me to flash and that fixed it. THIS one was a full lsec etc update. The S8 was not.

If you want to say it all comes down to the config files, I have to say that can't be true. These systems don't work the same way even across their own brand of fyt devices.

In fact, when I was purchasing my S8 Ultra initially, they told me this and one other model have a better BT chip that is capable of better noise suppression (my car has a convertible top so there is a lot of wind noise), which is different from the other S8 models. Of course, those were the 2 most expensive models so it might have been marketing hype but based on what I'm seeing here, I think there's something to it. I really think the Bluetooth units aren't the same across FYT devices.