yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Thanks for fixing the Text on the Square Artwork in the Player widget :)

Progress bar is still too thin on the Square Artwork.

Ideal would be that it ran on a solid (black) background, and was about 3 times thicker, with a narrow baclground between the Artwork bottom, and the Progress bar.

See attached Screenshot & the Photoshoped suggest updated version.

===

Minor issue .. not high priority, but it is frustrating ...

Spotify Shortcuts

These get added to the "Home Screen", but that Home screen is always screen 2, and not the FCC user defined Home Screen.

Ideally, could it add these shortcuts to a User Defined Screen number ? (Fcc setting ?)

In my case , it would be a screen I have dedicated to Spotify Shortcuts.

At the Moment, it adds the shortcuts to screen 2 (not my home screen which is screen 3), and then I have to move them to my Spotify Shortcut screen.

This is now further complicated if the Screens are LOCKED.

The ideal solution would be "user defined screen", where Spotify shortcuts gets added to (which in my case would be screen # 10)

BTW: An issue with Spotify shortcuts t would appear to be that if the Version of Spotify is updated, those shortcuts generated with an earlier version, no longer work, giving an error about unknown application. (so every time Spotify updates, all existing Spotify shortcuts no longer work)

Are shortcuts calling both Spotify & version ? If so, could they be made to work with any version ?? -- or whatever it takes to fix this issue (if it is something that FCC can do)

EDIT:

Added Video I made yesterday but did not add when I first wrote this post.

Basically shows what I have written about in the above text, mainly about the Quickplayer selection.

In hindsight, comparing the Current MiniMap styles with a Google map style, the current styles are pretty good.

(For some reason, the Google Map Style looks a lot better/different on my PC, and not so good on the Android head Unit -- strange - may be a Gamma Issue ?)

https://drive.google.com/file/d/1EWxOlMnmW9lpebBvpqk4A7V0fVazliUR/view?usp=sharing
[Android Head-Units] SpeedFire-:
Yes. Premium will work on any version.
[Android Head-Units] parisisal:
Bug - daily total park time

Hi [MENTION=4292729]SpeedFire-[/MENTION]

i noticed a bug on a FCC Car Launcher widget.

The "daily total park time" does not reset! It coninues to grow up day after day! (last widget on the right - 35:32)

See the picture:

I was in car about a minute ago.

- 0.04 : total trip time daily -> working

- 1:11 : park time in a single trip -> working

- 35:32 : daily total park time (park time in a single day) -> NOT WORKING (i was in car a minute ago, it count already 35 minutes).

Now, the widget counts more that 1h when i get my car in the morning! I suppose that every day the "daily total park time" have to starts from 0:00.

I tried to reset trip data, all the widget starts from 0, but the "daily total park time" don't!

Can you fix it ?

I've also a request : Can you add a widget that sums : "total trip time daily + daily total park time" (and call it something like "total trip/parking time").

Best Regards,

Salvo
[Android Head-Units] Scopesys:
Ref: Spotify Shortcuts

Updated Spotify today ( did not note old and new versions number), but after update, the Spotify Shortcuts made with the earlier version of Spotify, still worked with the new (lastest) version.

In past months, many times, the Old shortcut no longer worked with a Spotify Update.

SO, GOOD news !!
[Android Head-Units] Scopesys:
Happy Thanksgiving 2019!

and to SpeedFire- for the creation and continued development

of "FCC CAR LAUNCHER"
[Android Head-Units] SpeedFire-:
Good news. How does the latest alpha work overall? Do you experience any restarts or other annoying bugs?
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

On Px5 (Eonon) Unit, restarts are very few. - big improvement in latest alpha

The Allwinner unit, restarts on most Home press, or player changes (don't play with the Allwinner unit that much, just use it to play music at work !!)

Switching between players is still an issue, and actually seems worse and more unstable in the latest Alpha.

Still a lot of jumping back and forth between players when one of the other 3 players are selected, and initially, artwork and text may not always update.

After a few changes, it gets better, but is still not 100%

The impression I get, and from what i recall you have said in the past, FCC is trying to keep track of what all the players are doing, but often this information seems to be out of date, or not available. My thoughts are that OLD, Incorrect data is far worse than no data at all.

The Current Alpha is Usable, but is still very unstable as far as displaying the correct Artwork & text, or even switching and staying with the selected Quickplayer.

I would suggest that FCC should only switch players if the user actually selects a different player, and when they do, then that IMMEDIATELY becomes the displayed selected player-- and does not change. The artwork and text should show DEFAULT, and then FCC should try to get the CURRENT data for that player.

Most players cannot pick up from exactly where they were in a playlist, after a reset or re-boot, so keeping the and displaying the old Historic information, in most cases, in wrong, and should not be the norm.

Unfortunately, this may require some considerable work to correct, and get to what may be a simpler, less Fudged design. All those 'work arounds" that were added may well not be needed anymore, now that the memory leaks and Database bugs have been fixed.

I can make another Video, but basically it will only show again what my past 2-3 videos show, FCC switching back and forth between players when one of the existing Quickplayers is selected, and not displaying the correct information for that player .. (often very old, historic data)
[Android Head-Units] SpeedFire-:
[MENTION=9325785]Scopesys[/MENTION] OK, thank you for the feedback!
[Android Head-Units] okij:
[MENTION=9325785]Scopesys[/MENTION]: Heaving read many of your recent posts, I want to thank you for your clear and detailled observations and descriptions of the known bugs and your videos! They surely are helpful for [MENTION=4292729]SpeedFire-[/MENTION] for tackling the bugs.

I agree with you that making the backend of the player widget less complex should help to improve things.

BTW, one bug that I regularly observe on the player widget is that the artist and the title displays switch their position erratically. Did you observe this too? I couldn't find out what triggets it, only that switching between different players sometimes cures it.
[Android Head-Units] Scopesys:
Thanks... I also find that making a video is far clearer than trying to explain what is happening, and risking putting a biased interpretation on what I see happening.

I don't recall ever observing on the player widget, the artist and the title displays switching their position erratically.

Most of the time I am using PlackPlayer EX, and have taken the trouble to clean up the meta statement in the Mp3 files, and standardize on the Artwork, to 400 x 400.

I also run all the Mp3s through a couple of Mp3 tag diagnostic programs, so I am pretty sure that all my Mp3s on the CF card are 100% valid and do not have any strange additional tags.

Out of interest, when you see them swap over, is that repeatable ?? .. ie, if its playing something that can be re-played (Mp3 or some other play list), does it swap over every time on the same song, EVERY time that song is played ? Maybe the swapping over is really due to the source's tags actually being incorrect on some tracks ??

"Mp3Checker" & "Mp3 Diag" are the two Windows diagnostic program that I use to make sure all my Mp3 files are valid , and "Mp3tag" to make sure all my tags and artwork are good.

I also finally use "Drivesort.exe" to sort all folders and files alphabetically on the CF card -- not that that is needed for most players, (except simple file players that do not have their own sort ability)
[Android Head-Units] ab1702:
[MENTION=4292729]SpeedFire-[/MENTION] I too see more problems with player widget in these more recent alphas. A few days ago I was listening to dab-z and then it just switched over to Apple Music by itself after about 5 minutes.

Today the unit had been on for a minute and dab-z had started when the unit came on. After the minute I switched to Apple Music which started playing, the artist and track info was from the last time I used Apple music(which wasn’t the song I was currently listening to) and the album art was from the radio station I was listening to the last time I used dab-z.

On other occasions when I’ve been in the car say maybe 15 minutes I’ll switch to Apple Music but the track info and/or album art doesn’t change from dab-z so I have to go back to dab-z and then back to Apple Music again and then it will update correctly.

I would say this has been like this for the last few weeks on and off, before that for me it was working reliably I’d say for a few month.
[Android Head-Units] okij:
Actually I listen to radio (and not MP3s) most of the time and I observed the artist/title swapping with the DAB-Z app and AFAIR the Radio app (FM). In DAB-Z the artist display shows the name of the station and the title display shows the info that the radio station currently airs (like "artist - name of song" or e.g. some short news). These get swapped at times and I haven't found out yet how to trigger this behaviour. In the Radio app, the artist display shows the FM frequency and the title display shows the name of the radio station that I've set in FCC.

If it occurs again when DAB-Z is playing, I will check if the artist and the title display are also swapped in the Radio app and in my MP3 media player (I use the GoneMAD Music Player). If only DAB-Z is affected, I will report this bug on the DAB-Z thread. If the Radio and/or media player app is also affected, I will report this again here, because it would be a bug of FCC.

Edit: I did some more testings and now am quite sure that this bug is caused by DAB-Z and not by FCC, therefore I just posted it here with some more details on the DAB-Z thread.
[Android Head-Units] Timsche2210:
Hey guys,

Installed yesterday the PX5 in my SLK R171, and found todays this awesome launcher.

It’s really great to see, that someone work on such an amazing software.

I got one problem, if I want to use the call-somebuddy widget it told me to install google contacts. If I installed it, contacts want to sign in with the google account. If I fill out the sign in window, the failure „your account already exists on this device“ (in German, so may the 1:1 spelling is different) and I cannot login.

Think this is just a small problem, but I don’t find a solution...

Regards

Timo
[Android Head-Units] Scopesys:
You can use bigger (readable) fonts for both items, and have them BOTH able to scroll, if the text in either (or both) gets too long to fit in your assigned windows space.

see Video below :)

https://drive.google.com/file/d/1YMezj2jZBleflTgwqnifANU-skcVIuPq/view?usp=sharing
[Android Head-Units] SpeedFire-:
I'm still resting from a Player Widget modifications, so do not expect any improvement in this part (yet).

FCC Launcher 3.328:

- Some bugs related to initial Launcher setup were fixed (there was an extra screen with a widget sometimes, screensaver screen had incorrect properties).

- Screensaver screen's properties (a dark screen with a black wallpaper) are now associated with a unique screen id and not just a page number. So now you can reorder your screensaver screen and it will keep that properties.

- Fixed different crashes which were reported automatically.
[Android Head-Units] realzoulou:
Another update after [MENTION=4292729]SpeedFire-[/MENTION] has provided me to dowload the Premium version at no cost (Thanks!)

I tested: FCC 3.220 (current Play Store version), DAB-Z 1.5.65 (OMRI mode), PX5 Android 8 Hal9K ROM, Suspend to RAM disabled, instead OFF after 30 sec, DAB-Z is configured as (only) auto start app (Premium feature), all other settings in FCC and DAB-Z are on default values

I repeated following steps 5 times on a bench setup: DAB-Z is playing in background, FCC shows main screen. Then ignition OFF, wait until device is OFF. Then ignition ON, wait until DAB-Z continues to play.

Result: In all 5 of 5 tests, DAB-Z was successfully started.
[Android Head-Units] SpeedFire-:
Thanks!

Can you please also test this on the latest alpha?
[Android Head-Units] realzoulou:
Tested with FCC alpha 3.328 with the same test procedure as before: In all 5 of 5 tests, DAB-Z was started successfully.
[Android Head-Units] SpeedFire-:
Perfect! Thank you!
[Android Head-Units] ab1702:
This isn’t the problem in question though.

The problem is when in FCC settings you select ‘autostart last player used’. If Dab-z is the last player used before the unit is turned off, fcc will not start it again automatically when the unit is switched back on. This is when the dab-z setting of ‘automatic start upon usb detection’ is turned off.
[Android Head-Units] okij:
+1.

This summarizes it very well.
[Android Head-Units] realzoulou:
Finally someone that describes the problem properly! Thanks [MENTION=8476598]ab1702[/MENTION] !!

Yes, I can reproduce this, too. Used the same device and app versions as in my previous post

[MENTION=4292729]SpeedFire-[/MENTION] Find a logcat of the cold boot attached. DAB-Z was the last media player before ignition off.

View attachment 4891591

Maybe important to know for you [MENTION=4292729]SpeedFire-[/MENTION] : DAB-Z cannot be started by MediaController.TransportControls.play(). The MediaBrowserService within DAB-Z requires that the Player activity configures the DabService first. But I also do not see that FCC attempted to start DAB-Z with the normal LAUNCHER intent.
[Android Head-Units] parisisal:
Hi [MENTION=4292729]SpeedFire-[/MENTION]

In this version in the trip combined widget the altitude widget shows always " " (no value).

Could you fix?

The standalone altitude widget works.

EDIT: Fixed deleting and rebuilding the widget.

Salvo
[Android Head-Units] rigattoni:
May be I´m a nerd regarding GPS data, but FCC just shows the not corrected altitude from GPS.

I saw this issue long time ago, but in respect to other important issues I did not post it... Is a nice to have feature I think.

All GPS data do not take the geoid undulation of the real earth in account for showing the altitude on the display. https://en.wikipedia.org/wiki/Geoid

This undulation depends on the location where you live, as example for Germany it´s around -47m in difference to the GPS altitude.

May be this would be some kind of feature to take the undulation in account. To be able to put it in as personal value in the settings of the widget would be nice.

In this case the user would be able to get the more accurate altitude.

To verify the real altitude just use this web site: https://www.unavco.org/software/geo...eight-calculator/geoid-height-calculator.html
[Android Head-Units] realzoulou:
[MENTION=4292729]SpeedFire-[/MENTION] User [MENTION=4916555]okij[/MENTION] reported an issue with FCC in the DAB-Z thread in this post. The post contains a logcat.

The issue is about track and artist being swapped in a Player Widget. See the pictures in the post. Expected is Artist = DAB station name = "WDR 2 Rhein-Ruhr" and Track = DAB DLS text = "Rehab - Amy Winehouse".

DAB-Z sends out the Notification, which FCC receives correctly as

10:51:04.367 6051 6051 D FCC_Service: NOTIF_ACTION RECEIVED MSG_UPDATE_TRACK_ARTIST_ALBUMART pkg = com.zoulou.dab, track = Rehab - Amy Winehouse, artist = WDR 2 Rhein-Ruhr, playstate = 3

FCC gives out several log messages, not sure if I interpret them correctly. What I can see is that something inside FCC prints shortly before FCC receives the Notification

10:51:04.295 6051 6051 D AchievementNotification: showAchievementNotificationWithDrawable. type = music, title = Rehab - Amy Winehouse | WDR 2 Rhein-Ruhr, drawable size = 72

and after the Notification track and artist are swapped

10:51:04.388 6051 6051 D AchievementNotification: showAchievementNotificationWithDrawable. type = music, title = WDR 2 Rhein-Ruhr | Rehab - Amy Winehouse, drawable size = 72

Hope this helps to find the root cause.
[Android Head-Units] Timsche2210:
[MENTION=1633144]speedfire[/MENTION]

Do you know the problem with the google contacts?

Regards
[Android Head-Units] Scopesys:
As one nerd to another -- Interesting indeed.

Here in Maryland , USA (East Coast), it is:

Geoid height: -50.283 (meters)

Orthometric height (height above EGM96 geoid which approximates mean sea level): 50.283 (meters)

(Note: orthometric height = GPS ellipsoidal height - geoid height)
[Android Head-Units] rigattoni:
Yup, to show the real altitude there should be any adjustment in FCC, either manually by input of the local difference, or by using the formula to calculate the difference automatically. To reduce CPU load I would prefer the manual way as there is no big jump in the undulation around 500km of your local area.
[Android Head-Units] Scopesys:
Sounds good to me -- although I personally have no need to know my EXACT altitude. +/- 50 meters is good enough for me

However, I when I am at sea level, looking out across an Ocean, It would be nice to see the GPS reading nearer to zero feet :)

Getting even more Nerdy, does all this take into account the rise in the ocean sea levels due to global warming ??
[Android Head-Units] tlyonstlyons:
It's rising 1/8" per year. Maybe you can add it in your head? but remember a usual GPS is +/-30 feet or more. How surprising that you are floating your car on the ocean.
[Android Head-Units] Scopesys:
No, just doing wheelies on the beach at low tide !!
[Android Head-Units] parisisal:
Hi [MENTION=4292729]SpeedFire-[/MENTION],

the main issues on FCC Launcher 3.328 version that i found are :

- The Player widget sometime changes source. I have the FM Radio and myTuner Pro. I was listening radio FM -> the i make a phone call -> when I hang up i found that the current player has changed to myTuner Pro. Why ?

- The total park daily time is still NOT WORKING. It grows up day by day! Does not reset every day. Why ? When I turn on the radio in the morning i start from 1h and 45min of parking time. Why ?

- The minimap returns always automatically to the current position. It is annoyng! Before in order to return to the current position I have to click on the "target" icon.

Is there a better way to notice bugs ? Or we have to write down here ?

Regards,

Salvo
[Android Head-Units] rigattoni:
Another change request upcoming:

As a lot user just now buying units with CSN2 MCU I would like to have an adaption for the Auto brightness settings.

Just now, auto brightness does not work.

If I use Tasker to set a brightness, this works fine, so I would expect that the current implementation does not use the Android standard. [MENTION=4292729]SpeedFire-[/MENTION], would you be able to get this working on these CSN2 units too?
[Android Head-Units] parisisal:
Someone uses TuneIn or myTuner?

Using myTuner i have the current station/logo in the player widget.

TuneIn seems not integrated?

Do you know why?
[Android Head-Units] bossman4:
I just got back in action after a long trip and installed 3.328. There was no issue with the install on the Eonon unit and I did not have any troubles with the widgets moving on startup (thanks Speedfire!).

Today, in the garage, I was trying to use the app as a normal person rather than a tester.

I had previously setup the Quickplayer (Radio, Blackplayer and my Podcast player) on the main FCC screen and Amazon Music, Black Player and the podcast player on a second Quickplayer screen.

All the music apps seemed to work, but there was a second button push needed to set the titles and graphics the first time I switched.

There were no FCC restarts that I could see. I will have more time to play with it tomorrow while driving, while using the phone and Google maps.

The break was good. Coming back to see FCC app set up and do its job was very rewarding.

Thanks a bunch Speedfire!
[Android Head-Units] Scopesys:
Christmas is almost here, so I am putting in my FCC Christmas "Wish List" (because I have been "NICE" ? )

Some "FUN" stuff to program and add for a Merry Christmas :-

(1) Compass option to display on Speedometer widget

(2) Thicker Progress bar on Bottom square Player Widget Artwork.

(3) Spotify Shortcut to save to a user specified page (Not only the Home page)

(4) Standard Google Map style for Mini-Map.

Then maybe in 2020, an opportunity to get back to finalizing the Quickplayer issues
[Android Head-Units] SpeedFire-:
FCC Launcher Beta 3.332:

- I was really busy optimizing the resource consumption and performance of the Launcher. A lot has been done. As a result CPU usage on a screen without miniMap should look something like this:

(this beta is sent to a beta channel in Play Store)
[Android Head-Units] okij:
[MENTION=4292729]SpeedFire-[/MENTION]: Thanks a lot for the new beta release, much appreciated! :) I will install it instantly and see how it works.

My wish list for Christmas is short: please finalize the Quickplayer issues. :fingers-crossed: IMHO it is most important to fix existing bugs before implementing new options and features. Currently, most of the negative comments on Play Store are about bugs and not about missing features. For sure FCC already is by far the best launcher for Android head units feature-wise, but to get a wider acceptance and recognition amongst users, it's crucial to make it stable and bug free.

As I reported here, the artist and the title are sometimes in the wrong order. This week I testet if the Player Widget option to manually swap artist and title has an influence on this bug, but it hasn't: Either way, the title and the artist display is sometimes in the opposite order than it should be after starting the HU from standby, which gets fixed by switching to a different player and back to DAB-Z then. Please have a look at [MENTION=7838245]realzoulou[/MENTION]'s detailed report with background information from my logcat. I hope that you can find the root cause and fix this bug soon.

[MENTION=9325785]Scopesys[/MENTION]: Please don't get me wrong, your "fun stuff" feature requests all make sense. And for sure you - as one of the most active members on this thread - are more in a position than me to ask for new features. Nevertheless I think that [MENTION=4292729]SpeedFire-[/MENTION] should focus on fixing the bugs, since the last official "stable" version on Play Store was released almost 9 months ago and IMO a new really stable version should be released as soon as possible.

About your 2nd wish (2) Thicker Progress bar on Bottom square Player Widget Artwork.: I personally like the thin progress line, because it doesn't cover much of the artwork and is thick enough to be seen on my 1024x600 screen. Nevertheless I support your feature request, but setting a thicker progress bar should be optional, maybe by being able to set the height in pixels.