[Android Head-Units] Scopesys:
Many thanks ... it seems to be back working as it was when it was first added, and will, under the right circumstances, show the Connected device name.

I played with it a bit tonight, and while I don;t think I am 100% understanding the conditions under which it works and does not work, there does seem to be a pattern/rules to make it work.

Basically, The phone should not be trying to make a connection with the head unit, until both the head unit has booted, and FCC is up and fully running,

Then it correctly shows "disconnected". and when one tell the Phone to connect with the head unit, with both CALL and MEDIA, then it will display the phone's name, and change to the correct Connected Icon & color.

You can then go on to tell the phone to disconnect, and either reconnect again, or connect with a different phone, and all display correctly.

If However, when starting the head Unit, you rush and tell the phone to Bluetooth connect (or it does it automatically) BEFORE FCC has finished loading, then the Device name will never appear, even if you disconnect the phone & try to connect it again.

In this case, the only way to recover, is to disconnect the phone, re-boot the head unit, wait for FCC to load, and then tell the phone to BlueTooth connect.

While this may not be idea for those that has set up automatic head Unit detection with their phone, to get the phone to automatically Bluetooth connect -- as FCC is not yet running when the connection is made, and thus no Device name .. its not such an issue for me personally, because of the way I use my phone.

Typically, I have the Phone in Low Power mode, and in this mode Bluetooth is off.

My older Samsung J3 phone does not support the auto detection of the head unit and the automatic Bluetooth connect.

So, when I go to the car, I need to do the following.

(1) get Phone out of Power saver/low power mode.

(2) Turn on Ignition, and let head unit boot, and FCC start and be fully running.

(3) While head unit is starting up, set the Phone to be a wifi Hotspot.

(4) Disconnect the head unit from the house wi-fi, and re-connect to the phone wifi.. ( check that WiFi widget not shows Phone name)

(5) Only then, turn on the Phone's Bluetooth, and tell it to connect to the head unit, and that Call & media data are ON.

(6) Then I can check that the FCC Bluetooth Widget shows the Connected BLUE color, and is displaying the phone's name.

(7) Finally start the car, and pull out of the garage.

The whole process takes about 1 minute, including the Bluetooth startup, which is not too bad.

It takes considerably longer if I rush & mess up, and have to shut down the head unit, and start all over again...

The 1 minute is not wasted, I also use this time to select what Music player and playlist I want to listen to, check the TPMS to make sure tires are OK etc etc.

Not quite complex enough to need an Airplane type Cockpit Check list -- but getting there :P

Bottom line -- Thanks [MENTION=4292729]SpeedFire-[/MENTION] for getting it this good .. it is certainly quite useable, and I am delighted that it works this well :)

Video << crude Video, showing it working (and not working)

Comment: the Disable, Not Connected Icons are fine .. My misunderstanding while recording.

I did not show any Video of it NOT working, but if I HAD connected the bluetooth to the head unit while it was booting, before FCC had loaded, that seem to Lock out the correct operation of both the Icon Color, and the Device name, even after subsequent FCC reboots

What is strange though is that it does connect and shows the Connect Icon, but in white !! (not blue) with no device name.

The white (not Blue) color for Connected Icon is unexpected ??? -