[Android Head-Units] SpeedFire-:
Thank you for your suggestions. I will quickly comment on them:

(1) Saving FCC settings. While editing the save name, their is a "Historic" ? option on that screen, to save to SD. ( before save to Google drive was added ?) But then after the edit, you are presented with a screen to select to save to SD or Google. It might be clearer to remove that "historic" option to save to SD, when editing the the saved name.

This is not a bug. Saving to SD is a working option and I use it quite frequently. So this is kept there for purpose.

(2) When the volume is changed, the Player WIdget scrolling text gets re-set to the start of the scroll.

I was able to reproduce this but the reason is not clear to me. My assumption is - when the volume bar appears it receives system's focus. This is important because text in the widget is scrolling only when it gets focus (I set a <request focus> command in xml file on the text). But I am not sure that the reason is in this.

(3) Pro Version options. Sometimes they are referred to as PRO options, and sometimes as PREMIUM options. Making the name of the Paid for version consistent would be better.

Can you please show such cases? I launched a full search by the word "pro" and it was found only in some translations (not in the meaning of "premium" as far as I can tell).

(4) Some widgets have had the UP/Down buttons added to there Slider controls, that makes them a lot easier to set to precise values. But not all sliders, Suggestion is to standardize on the Slider controls, and make them all have UP/Down buttons.

Agreed. I was almost sure that I changed it everywhere. Can you show an example?

(5) Eliminate loosing the selected 4th player in the Player widget, when quickplayers 1, 2 or 3 are selected. 4th player seems to survive a reset or re-boot, but gets removed when quickplayer 1, 2 or 3 are selected.

ie Only replace the 4th player with a newly selected 4th quickplayer

The idea here was to keep 3 quick players for user selection and show the 4th only when it plays. Your use case is also understandable, maybe we need a one more checkbox for this.

(6) BT widget . Connection name. Is that really an issue for all Android version, or can the versions that support it, update the name as new devices connect & disconnect.

No good news here. BT APIs are bad on all android versions. I did an extensive research on StackOverflow for a possible solution with no good results. If you could find any third party widget which identifies BT devices reliably please give me a link.

(7) BT & Wifi Widget. There is options of Connected and Unconnected TEXT color, but only one option for icon color, Can the ICON color also have 2 colors, one for connected and one for not-connected.

Good suggestion. I will add it.

(8) Adding a away to add USER Defined OBD2 Pids, either a fixed number in the FCC OBD2 menu, or from reading a user edited OBD2 config file.

There area lot of useful PIDS that are car specific, so while FCC cannot be expected to know all these, at least the owner can, if so motivated, add their own specific ones for their car.

This may be difficult. But I will try.

(9) When Widgets are drawing (re-drawing), often they draw with one configuration, and then later, after other widgets have loaded, those first widgets change and update with their final configuration settings. Could that be fixed.. maybe the configuration parameters could be sorted so that for a given widget, they are all processed with that widget, before the next widget is drawn/redrawn.

With this, some sort of ICON OVERLAY ( bottom right corned) to Indicate that widgets are still loading, (maybe on other screens), so maybe wait before touching screen.

Please can you show this on video?

(10) Adding a FCC "Compass WIdget" with options to configure in various typical FCC widget ways. ( Maybe both TEXT and Grapgic). This would be a GPS Compass widget. Currently none of the Playstore GPS Compass APPs support having a WIdget. (apart from Torque Widgets, that seems to clash with FCC widgets, and cause the whole system to reduce to a crawl)

Hm. Probably I can't do this right now. Please remind me about this. Btw, do you have a good example of such text / graphics in some compass app?

(11) For those more recent Head Units that support SPLIT SCREEN, FCC is very limited in how small it's size of the split screen can be reduced to. (On my system, about 80%), leaving not much room for the other App's screen. Maybe this is just unavoidable, but if there was a way for FCC to allow the other apps screen to be a little bigger, that would make Split Screen with FCC more of an attractive option. (Even if the user would need to create some specific FCC screens that are basically of a different size, to run in split screen mode)

Not possible unfortunately. It also drove me crazy but it turns out that split screen is designed this way in Android. Your default launcher (a Home app) can have a minimum of 75-ish% of the screen. If you select another launcher as a default one - then FCC Launcher can have a 50% portion of the screen. Please test. I don't really get this idea of Android developers.

Moreover, third party app developer (like me) can't even initiate a split screen mode. This should be done manually by a user. No API here at all.

Overall, split screen mode looks like a half-baked feature to me... as if Android developers inserted it in a rush.