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

For me, V3.200 is working well, and there is really nothing that I now feel is in urgent need to be fixed or corrected. If this was the final version of FCC was 3.200, I would be more than content to live with that, and find it more than satisfactory. (but obviously, any additions or refinements to FCC would be most welcome as well)

That being said, there are still a number of things in FCC's operation, that I have mentioned this year, that not being critical, understandably did not get addressed. So I am going to re-list those all together, in this post, so that you can consider their importance to you at this time, to address.

(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.

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

(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.

(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.

(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

(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.

(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.

(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.

(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.

(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)

(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)

None of the above are CRITICAL needs, but you might like to consider addressing some of them, if that fits in with your overall design and development plans for FCC.