[Android Head-Units] bossman4:
I copied the behavior of 3.318 that I previously posted with my setup, since it did not change significantly with 3.320.

1) I think most of the testers seem to have quickplayer on their main screen, so they do not get the bouncing to the main screen that happens to me as described below...….

2) the initial picking of the (2) Blackplayer results in the wrong graphics only for the first toggling as described below

3) I would say that 3.320 seems faster in the toggling between players.

I have the Eonon unit (Rockchip) in this test. I am in Florida, so it is warm.

The very good news is that in the configuration that I have, the 3.318 version is very predictable. This was not the case in recent versions. It allowed me to reproduce certain behavior over and over again. The configuration for testing this time for the quickplayer is

1) FM Radio

2) BlackPlayer

2) FM Player (podcast player)

I have the standard FCC template for the main screen and I have moved the quick player to second screen all by itself. All the players and radio are running in the background and audio switch is instantaneous

First, If I have player 2) or 3) on the quick player screen during startup, when I pick FM Radio, it picks the right audio feed and rolls to the main FCC screen and displays the correct text and graphics. If I roll to the second Quickplayer screen, the FM Radio audio stays correct and the graphics and test are correct for the FM radio. This behavior happens every time I push 1) FM Radio on the quick player screen that has 2) or 3) playing and is very very predictable. I personally would have expected the Quickplayer screen to stay on the screen and the text and graphics depict the FM Radio. Maybe it is my configuration with the two screens (Main and Quickplayer Screen)

Second, If I pick 3) FM Player (Podcast) it correctly picks the right audio stream and correctly picks the correct text and graphic. I don't think it ever makes a mistake with this application on this button position. Works wonderfully!

Third, If I am on 3) FM Player and I think 1) FM radio (after I rolled back to the separate quick player screen) and then I pick 2) Blackplayer, the audio changes correctly but the text and the graphic says on 3) FM Player. The second time I hit the 2) Black player button, the text and graphic correctly catch up to the audio. This behavior only occurs the first time after restart or reboot. Once it correctly displays the correct text and graphics, the toggling between 2) and 3) will display the correct text and graphic. Every once in awhile, it will stumble and eventually find the right text and graphic on 2), but most of the time it is spot on.

So my assessment is that the FM radio behavior (switching to the main screen when 1) FM Radio is pushed) is the situation that Speedfire eluded to in his notes.

The second behavior where I need two button pushes for 2) Blackplayer to display correct text and graphics seems to be a coding quirk. Just as reminder, I only see this behavior when the unit starts up and the 2) Blackplayer is picked for the first time after another player is running. Subsequent single button pushes while toggling results in correct player, text and graphics. A normal car radio operator may think they did not hit the choice button correctly the first time, but in reality, the audio changes correctly. Again, this behavior only occurs when the unit is fired up, not later in the test session.

The FCC software seems to be very stable in this section of code and now allows the fine tuning of the "preferred" behavior. Almost there for the simple audio applications.

Amazon Music will have to wait.

Getting very close Speedfire!!!!!