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

I can do that...

Android Version I am running on my Head Unit is same as in the emulator. 8.0 and Android Studio Device is the Pixel 3. ( Hardware device is an Eonon P5X)

(Pixel 3 is the closest to my Head Unit, with Play Store included in the image - I tried making a closer CLONE match, but had issues with Play Store not being included, and it was a Pain to try to add it, if it was not already in the original image)

I can also make a Video to show the Artwork NOT changing, but that is all it will show ... ie The Artwork not updating, which I have described already,

If only a single Player is ever run after a restart, then things are a lot more stable.

If selections are made between QuickPlayers, then that is really when things start to go wrong, artwork does starts to not update, and many times, FCC switches back to a previous player, by itself, with no user interaction.

There seems to be a lot going on when the unit re-boots, with FCC switching between what it remembered (stored) when the unit shut down, and what state the Head unit is in when it is re-booting.

ie FCC switching between Players by itself, and a lot going on for quite a few minutes (unit running slowly), until it finally settles down and starts playing consistently.

I believe this is the behavior you need to see happening at your end in Android Studio, either with the emulator, or when debugging on an actual Head Unit.

Strange you do not already see this .. maybe this is a function of the FCC screens I have set up ? I can send you a Backup copy of my FCC configuration.

If I make a Video, it should probably be taken in Android Studio, by capturing the whole screen, showing the LogCat running and a small image of the Device above in the corner.

That way you can can see what is going wrong on the Device, at the same time as seeing the log. I can also send you the log in a text file.

I can work on this over the next few days, if this is exactly what you need.

Another approach, (

One I would recommend

) may be to temporarily ignore these issues, and concentrate on fixing the high number of Exception errors, and warnings, and then re-evaluate the actual operation of FCC, after they have been addressed.

They should probably be fixed sooner or later -- maybe sooner is the best path.

To date, all I have done is to run the same version of FCC , with the same FCC Configuration, in Android Studio, and notice the high number of warnings & exceptions in the LogCat

Since the APK is obfuscated and without source code, that is practically all I can realistically do, and it is not my intention to get into the internals of FCC - far too complex --- I am quite happy to Test, while you diagnose & fix.

I am open to do and send you whatever you want, so based on the above, if you tell me specifically what you want, I will do my best to supply it to you.

Finally, the Artwork update issues, are really only a big issue when switching between players, and when the unit first starts up. When the present themselves, then a combination of Restarting FCC, or Re-booting the Head unit, will normally restore correct artwork updates (until another player is selected), so it is something that one can live with, as frustrating as it is.

ON a positive note, the Speed Alarm system is now working Flawlessly in the latest Alpha ... :)

Attached: My FCC Configuration Backup