[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

From what I experience with 3.314, FCC is having an issue determining which player to run after a Re-Boot, or even a FCC restart (Forced by the FCC Restart widget).

The seemingly random switching between Players by FCC at restart or re-boot, over an extended time (minutes) , would seem to be a BUG that should now be addressed.

--------------------------------------------------------

DETAILS and a fuller description of the perceived issue:-

FCC's behavior appears to be that it has not remembered (Stored) what player was playing, or when it comes time to start again, does not correctly use that stored information.

To me, this would seem to be the Most important, and overriding thing to get right as soon as the unit is re-starting, or re-booting, is that the QUickPlayer Player name widget, should immediately display that state when it first draws after the re-boot or reset.

It is not doing that, but instead seems to be trying to determine what is the current player by other indirect methods (ie looking at notification ? etc).

IT appears that FCC is trying to be smart, and remember other things, like the Artwork and Text for players, which may have benefits, but after re-start, and especially after a re-boot, that historic information is most likely obsolete and not relevant, and it might be better to display NO Information, rather than incorrect information.

Then if FCC is displaying NO Information, it can have a priority task to try to get that CURRENT information for the currently selected (and remembered + displaying as selected) Player.

BEFORE recent updates, there would appear to have been some Database storage bugs and memory leaks, that further complicated things, as well as when the user was switching players.

Now these have been fixed, FCC seems quite stable in selecting different Players and displaying the correct information, but ONLY AFTER players have been selected a number of times in rotation, and FCC has had the opportunity to "sort itself out", and get updated with players and their information.

So that leaves the underlining issue that has always been present, but maybe masked by the above now fixed Memory & Database bugs.

Based on what I have seen when testing, and some thinking about what is really desirable, ESPECIALLY after a Re-Boot (or the Unit re-starting after being off for some time), is that ALL Historically saved Artwork and Player text is most likely Obsolete, and it would be far better to start off with them Blank/Default, rather than show incorrect information.

The only really IMPORTANT information, is what player was last Selected, it's Play/Pause state, and if any player has been set to be the one to play at startup in FCC's settings.

It is that Player that should Immediately "Show" as Selected and be set as the "Current" Player, and the widgets should NEVER at any time display anything else.

Note: There is a special case when FCC setting has been set to start a specific player at startup, and that player is NOT one of the 3 configure QUickplayers, and is also not the 4th Quickplayer. In that case , if 4th player has been enabled, it should become the 4th player (before the 4 player selection is first displayed).

If the Option for 4th layer has not been selected, that poses a deleama, and probably the cleanest way around that is for FCC to itself detect this, and Enable the 4th player, setting that startup player as the 4th player.

If more than one player that is not defined in settings to be 1,2,or 3 Quicklayer, then only one can be added as the 4th player, but all those players selected to start, should be started in a paused state, with only one of them set to the 4th player and set to be selected (and to play or be paused)

But no matter how it is finally designed to work, the current issue in 3.314 (to me) as far as the Player Widget is concerned are:

(a) The indecision as to what is the correct selected and displaying as selected Player.

(b) The elimination of FCC switching between Players by itself, as it comes out of Re-Boot, or re-start, and for what may be many minutes, seeming to randomly switch between Players, as it sorts itself out, and makes additional guesses about what the current player should be.

(c) It is appreciated that getting the current information for the CORRECTLY selected player may require some time after-boot or even re-start.

Factors such as MP3 players not being able to access their files on the Head unit media, while the OS does a CheckDisk etc, or streaming Players having to re-establish connections and request fresh data etc ... but during this time, it might be far better for FCC to just consistently show the correct selected player, and Blank/default data, until such time that it is sure it is getting correct, current data to display.