yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
Luckily, I made a Video of my whole backup/restore/update session. ;)

Seems there might have been an issue with 3.318, that looks like it is fixed in 3.319, BUT the VOLUME Widget in 3.319 is messed up (as you will see in the video).

Had to restore twice, 1st time many widgets had incorrect parameters.

I'll let you analyze the video, and draw your own conclusions, rather than type a whole complex account of my interpretations..

Video is long, but a text description would have been even longer !!!

NOTE: Volume Widget got messed up as soon as 3.319 was loaded (Missed that during the recording).. Nothing to do with backups or restores.. it is messed up in 3.319

Included below are

(a) Video (link)

(b) Backup made under 3.318, ( Volume Widget OK)

(c) Backup made under 3.319 (Volume Widget broken)]

https://drive.google.com/file/d/1DDeXhHxDJwMMUPGIdcQE4EgDcuk6N4yq/view?usp=sharing
[Android Head-Units] SpeedFire-:
Thank you. Volume widget was broken because I optimized widget layouts (simplified then) so the drawing speed can increase.

In this alpha I fixed volume widget:

FCC Alpha 3.320
[Android Head-Units] okij:
House numbers in Offline Mapbox map

This weekend I changed my MiniMap from Google Maps to Offline Mapbox, using free OpenStreetMap vector tiles.

Interestingly, the day and the night mode of the Mapbox map differ not only in their coulour schemes, but also in the content that is displayed: While in day mode there are no house numbers on the map, there are house numbers in the night mode. Actually I find them quite distracting.

[MENTION=4292729]SpeedFire-[/MENTION]: Is this intended behaviour? (I guess not!?) Since I didn't find a toggle to switch off the house numbers in night mode, is there some other way to switch them off, maybe a configuration file? And last but not least: Could you disable the house numbers in the next version or add a toggle so that the users can decide if they want to see them? Thanks in advance! :)
[Android Head-Units] ab1702:
[MENTION=4292729]SpeedFire-[/MENTION] In these last couple of alpha versions I have still lost the album art in player widget for a couple of stations on dab-z.

They are still in the dab-z app but FCC will not display them anymore and nothing has changed.

It happened when you changed the resolution for the album art somewhere around 3.317 or 3.318. I get all the station and song info etc but it doesn’t show the station logo anymore. However when I change to the next station in my list the logo for that one appears in FCC. It’s just 2 stations that I use where fcc doesn’t show the artwork for it anymore.
[Android Head-Units] SpeedFire-:
This is easy to fix

Here you can change night theme to "Night (no house numbers)":

FCC Alpha 3.320 v2
[Android Head-Units] SpeedFire-:
Were they of low quality? I've added an additional check to not show album arts with too low resolution (less than 100x100).
[Android Head-Units] ab1702:
Ok thanks, that must be what it is then.

Zoulou has some logos built into the app and the rest of the logos I got from the Volkswagen website. The logos I now can’t see are ones that came built into the dab-z app so I don’t know the resolution of them.

It shouldn’t really be a problem though as I should be able to find some new logos online if that is the problem.
[Android Head-Units] Scopesys:
Looking real good ... Volume control back, and widgets seem to load a lot faster !!!

Switching between players seems a lot more stable & predictable as well.

One thing I think I have learnt. Sometimes I use APPKILLER to clean up historic run apps etc... Frees up memory etc..

IF I do, I need to RESTART FCC, and then get the Players running again, or else switching between players is messed up.. probably because APPKILLER has unloaded those players behind FCC's Back, and FCC is now confused.

A FCC Reset fixes all that :)

NEW BUG ( think it has always been in FCC ) - (to me a low priority !! )

Progress indicator in Player Widget does not seem to always work correctly, or update correctly when players are switched, or one opens a player and moves the play point withing the app.

Its almost a if FCC calculates the progress bar rate at the start of a song, and then just runs on that calculation, without ever checking the actual position within the song as it plays.

I thought I saw in the LOG, FCC constantly getting position updates ??

I do not normally display the progress bar , especially as I use Square Artwork, so the Circular Progress bar is often difficult to see ON TOP OF the artwork.

A simple LINE progress bar below the Artwork would be nice for non Circular displays. ;)

OVERALL 3.320 is the BEST so far !!!! Thanks SpeedFire- for all the fixes this week.

====================================================

BTW: Some time ago I asked if you would consider adding a COMPASS widget.

So, thinking more about this, maybe the IDEAL way to do this is to add it as an Option to the SPEED Widget.

(I cannot find a decent GPS Direction Compass Widget on Playstore, and in any case, adding it to the SPEED widget would be a good use of space to display a compass)

A Circular ring around the SPEED (Like on the Overspeed widget), with a Background Ring Color, and a Forground color for a small Part of the Outer Circle, in a position on that Ring representing the GPS Compass (Direction of Travel)

The SPEED widget is already accessing the GPS, to get the speed, so maybe its not too much more to get the Direction as well, and display it on the same widget ??

ie
[Android Head-Units] okij:
Thanks for the quick fix! I just tested it and it's working. :)
[Android Head-Units] SpeedFire-:
FCC Launcher Alpha 3.321:

- A very important bug is fixed related to widgets update.

Sometimes when a command to update widget was received, the app updated not only the particular widget (the update of which was requested) but ALL the widgets of this type. In some cases (for example after restore from backup) this led to a massive excessive widgets updates in geometrical progression. Now it should be fixed.

Please check if you see any visible effect from this fix.
[Android Head-Units] Scopesys:
VERY BIG visible effect -- FCC is no longer doing random Re-starts.

In fact, it does not seem to do any unexpected re-starts at all now, even if one switches between Players as fast as one can make selections on the Screen.

One remaining bug. Only on 4th Quickplayer, no matter what player is selected to be the 4th.

Selecting the 4th player when another player is selected, correctly switches to 4th player, and it is Highlighted. But pressing 4th player again, turns off Highlighting, so it looks as if no player is selected. Everything else is OK, 4th player keeps playing, but none of the players are now showing as selected.

Selecting 1,2 or 3 player, selects that player, and one of the 1, 2,3 players can be pressed as many times as you like, and still remains selected.

But pressing 4th player while 1,2 or 3 player is running, correctly selects 4th player, but pressing 4th player again, then de-selects it being highlighted.

But GREAT Progress, in stopping all the FCC frequent re-starts.

Seems only one slight issue with selection of 4th player still to fix.

Still the progress bar issue, but this I think has only very recently been highlighted, and is now probably far more fixable, now that Player selection is working so well.
[Android Head-Units] RocketSled:
Not so much a bug as "unexpected behavior" maybe. I use SiriusXM streaming almost exclusively. That's player #1. But my HU doesn't have it's own network connection, it has to hotspot to my phone, which takes it a minute or so worst case, but always 30 seconds or more. FCC comes up much sooner than the network, and when it does, it tries to start the SiriusXM player. But the player doesn't actually start. It actually sort of just hangs at its startup screen waiting for an internet connection (it will eventually time out if none is forthcoming). I can't tell if the player exits and FCC restarts it, or the screen just switches to the player when FCC tries to command it, but I will see the SiriusXM player pop up a few times, for just a second, before the display reverts back to FCC. Then that behavior stops, FCC is in the foreground and it thinks the player is playing but it isn't. Once the network connection comes up, if I toggle the play/pause button a couple of times the player will start playing.

Any way to delay FCC's attempting to start a player until after there's a valid network connection? (I know I can sort of fix this with Tasker)
[Android Head-Units] tonimontoia:
good morning I can no longer see the fcc notifications possible cause? thanks
[Android Head-Units] Scopesys:
If you installed a video recorder, like "DU Recorder", you could capture a video off your Head Unit as you operated it with the issues you have.

This might be far clear to view and understand, than a long text description.

It does not need to be a "Steven Spielberg" production, just a simple capture of what is happening. Remember, after the bug is fixed, the video then becomes redundant, so no point in spending a lot of time making it fancy -- (unless you want to play !!)

Personally, I seem to have had far better success submitting videos to SpeedFire-, than long text posts.

The Video allows the developer to actually SEE what you see, and he stands a far better chance of reproducing what he sees on the Video, at his end, than trying to interpret a complex text explanation.

And some verbal commentary explaining what you are doing, no matter how rough and broken, is far better than silence !!

:good:

---------- Post added at 08:21 ---------- Previous post was at 08:11 ----------

FCC Notifications are working correctly for me, right up to current latest FCC version 3.321.

I typically have them turned off, but every time I turn them on, they have worked, ever since they were introduced.

Certainly working with 3.321 -- just checked ( at least with my Px5).

I did initially have Notification display issues with my Allwinner unit, when I first installed FCC on it, some 9 months ago, until I changed one of the system default developer setting to do with animation.

---------- Post added at 08:35 ---------- Previous post was at 08:21 ----------

I tried the SiriusXM streaming APP about 6 months ago, when I had a trial XMSiriusXM offer. It's a very poorly written APP, and is very inferior to the non-streaming, Built into Head Unit XM Radio receivers.

Maybe if you have not seen the native Radio XMSirus running, you may not realize just how bad the Android streaming app is. (Apple version is a little better)

I even talked to SiriusXM, and got to talk to the app developer ( that was surprising !!) Basically, he was Clueless -- I am surprised he even got the streaming app to work at all.

Needless to say, I never subscribed to SIrusXM after the trial - mainly because of the Content, and the high frequency it keeps repeating (YAWN)
[Android Head-Units] tonimontoia:
? thanks
[Android Head-Units] bossman4:
I agree with Scopesys, the 4th player still seems to cause problems. I turned it on by accident when I put Quickplayer on the main screen.

When Quickplayer is placed on main screen, the FM Radio pick works correctly, because the main screen is already the choice. If you put the Quickplayer on any other FCC page, picking the FM Radio results in rolling to the FCC main page rather than staying on the page where the Quickplayer is located. As I mentioned before, most folks used Quickplayer on the main screen, so that behavior was not seen by others.

Amazon Music (with downloaded music) on Quickplayer Menu

I have figured out the abnormal behavior of Amazon Music in displaying the album art. Here is the "hodge podge" sequence to display Amazon Music album art on the FCC Quickplayer.

There are several main screens that Amazon Music application displays within the application

1) List of artists, albums, genres, playlists?. These pages allow you to pick various albums, etc. If you want to play an album, you make your choice here and it will play whole album in sequence. If you jump home to the FCC main menu after starting the album, the Quickplayer does not show the Amazon Music album graphic, possibly because the last screen shown within Amazon Music is the list of album screens.

2) Album picture menu in Amazon Music. This page shows the large album cover along with player controls and songs within Amazon Music. If you start an album on the "list screen" of Amazon Music and then pick the "large album screen" to show the large cover within Amazon Music, it must be placing the correct album cover art in a memory location that Speedfire is expecting Quickplayer to grab album art. If you switch to Quickplayer after displaying the "large album screen", it shows album art correctly on FCC Quickplayer. The Amazon Music album art continues to show correctly as you toggle between the various players (my case is Blackplayer, FM Tuner (podcast app) and Amazon Music in FCC Quickplayer.

So in summary with the latest alpha version of FCC, Amazon Music (downloaded) album art will display correctly in FCC Quickplayer, if you have the "large album screen" menu (with listed songs) opened within Amazon Music before you go into FCC Quickplayer. If you do not do that, the album art won't show up correctly in FCC Quickmenu.

My next test with Amazon Music is to arrange a playlist with several songs from different albums. I would start the playlist from within Amazon Music and then try to switch to album view within Amazon Music. I would then move to FCC Quickplayer and see if the album art changes when the next Amazon Music song comes along.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Version: 3.321

Px5 -- all those frequent FCC resets seems to have stopped :)

Allwinner -- still has a high frequency of FCC Resets , especially when changing players, or returning to the Home screen.
[Android Head-Units] bossman4:
Scopesys suggested that I try "DU Recorder". I loaded it up and it wanted to get me to subscribe for a year and then another "video recorder" tried to jump in. I could not easily get the hang of it, even though I did think I recorded a segment video. I just deleted the screen app since there always seems to be stragglers with these free apps. I am needing to get comfortable with this kind of application on a small radio screen.

What I have noticed before and have now replicated what I think is a real bug.

When I have the FCC app locked from editing and I am in the app browser screen (screen with all apps shown in a grid) and I "long press" an App button, FCC places the App on the FCC Main Screen. I would have thought that by having FCC locked, it would have prevented me from placing a new App (it called it a widget) on the FCC menu. I have repeated this behavior multiple times on purpose, after accidentally editing the main FCC menu screen and trying to figure out what the heck happened.
[Android Head-Units] SpeedFire-:
FCC Launcher Alpha 3.323:

- Progress bar fixed!

- 4th player selection bug fixed.

- Horizontal progress bar is added to the "square" player widget style (you need to select this specific style not just disable round album arts - it's the third style in the list)

- Option added to start FM radio foreground each time (this is for some devices on which background switching to FM radio doesn't work or does not allow to control FM radio via wheel buttons).
[Android Head-Units] Scopesys:
My apologies -- when I downloaded it some 9 months ago, it did not ask me to subscribe. Maybe the subscription was for a Premium version ?

I am reasonably sure I did not pay any subscription for mine.
[Android Head-Units] okij:
Thanks a lot, I will try it tomorrow.

Why did the APK increase by ~20 MB?

Today I tested the Mapbox map a bit more. There are two problems / bugs that I encountered and should be fixed:

It's not possible to lock the map to northern direction. Pressing the compass symbol does this just for a short moment, then the map spins to the driving direction again.

When the car stops, the map keeps spinning back and forward instead of keeping arranged to the driving direction. It's like the unit would have a built-in magnetic compass that isn't calibrated. Actually the map must use the GPS info for turning the map, but of course the GPS signal is not fully accurate and jumps around by a few meters. Mapbox reacts quite nervous to this, whereas Google Maps keeps the direction when the car is stopped.
[Android Head-Units] Scopesys:
That was quick -- Many Thanks :)

Unfortunatly, the Horizontal Progress bar is very very thin, and cannot be easily seen,

see Video

Maybe you could add a Thickness control, so users can make it as thick as they need it to be so it is easily visible on their particular head unit.

Also, I did not notice it while I was recording, but after I had done the quick sequence of Player Changes, ending up with Blackplayer selected, the 4th Player which WAS JetAudio but somehow that had got changed to the FM Radio !!!

The 4th Player changing to the FM Radio was most unexpected !!!

Maybe a little unrealistic to do all those changes so quickly, as when the changes are done at a more reasonable rate, it works very well. -- but it is the Job of a beta tester to try to BREAK IT :)

It changed at 3:36, as FM Radio was being selected during a quick sequence of player changes.

Maybe a Program Logic rule should be that the 4th player can never be changed to be the same player as any of the other 3 quickplayers

https://drive.google.com/file/d/1DhUSuVt_d3S_qtRHJjbSXV8M8DqruKEG/view?usp=sharing

EDITED: I have NEVER AGAIN been able to reproduce the 4th players changing when making rapid player selections, so it would appear to be a very rare occurrence - I just happened to catch one of those rare occurrences in the Video
[Android Head-Units] bossman4:
Works good for a three player system (Radio, BlackPlayer, Player FM), once I cycle through the choices once. Each media player (Blackplayer, Player FM) requires a second repeat button push for the correct album to show up when I first start toggling choices on QuickMenu after a complete purposeful Android bootup. During this startup sequence, the audio switches correctly. just the artwork needs a second nudge.

After the first button toggling hesitation scenario, subsequent button pushes result in very quick audio and graphic switching between the players and radio.

Not sure why..
[Android Head-Units] tonimontoia:
hello, there is a method to start viper automatically without opening the whole screen thanks
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

3.312

Recently added Square Style Artwork, that has bottom progress bar option.

None of the Artwork Overlays are visible, ie Controls, Song/artist Text.

It is as if the Artwork is the TOP layer, and covers everything else up ??
[Android Head-Units] kruszynsky:
Other FM Radio player

[MENTION=4292729]SpeedFire-[/MENTION]

Can You add function to change default fm player? Because in my android station fm app is not is not detected and i can't choose it
[Android Head-Units] SoberXDA:
Hello!

Can you please disable the automatic restarts of a 4th player?

See the recording for yourself:

https://youtu.be/OLN6JtngCts

It is most annoying. While FCC is doing it's restart thingies, I'm not able to do anything.

PS: Funny thing is I did not even enable a fourth player in the settings...
[Android Head-Units] riccardone1:
I tried the 3.323 version and found these flaws:

1) when launching the launcher the background of the minimap is white and not with custom colors. Only by entering and leaving the setting does it work properly.

2) sometimes to make Spotify go I have to select the radio and then again Spotify ...

Thank you for the work you are doing
[Android Head-Units] Scopesys:
I have always found the color selections for the Mini-Map to be less than optimum, with some options giving large areas of light backgrounds, where other background areas are dark.

That, and because IMHO, the Google map has a far better color scheme , and is a lot clearer and easier to read while driving, is why I never use the Mini-map.

If there was a way to better customize the colors, (or at least an option to select a color scheme that closely matched that of Google Map), I might be more inclined to use it.

I appreciate that a lot of work (and a lot of RAM) has been dedicated to the Mini-Map, and for some, it might be a good solution for navigation, but here in the USA, to me, Google Map is a far better choice, if only for its clarity of display.

BTW: The Light background area are NOT water.. in fact, knowing the area, it is difficult to determine WHY some areas have a lighter background.
[Android Head-Units] SpeedFire-:
You can find or customize map color scheme here https://snazzymaps.com/ and send a json to me.
[Android Head-Units] Scopesys:
How about just adding the DEFAULT Google map style (from https://snazzymaps.com/ )-- that looks good to me and it is what many are already use to.

If you had a mind to make it more customization, how about have an option to select "User Style", which would access a Json file that the user could create from that website, and import into FCC (like the Radio station Logos etc)

Personally, I would be more than happy with the Google map style, but others might like to do their own customization.
[Android Head-Units] realzoulou:
[MENTION=4916555]okij[/MENTION] asked me for feedback regarding FCC not able to start DAB-Z: I tested with FCC alpha 3.318 and DAB-Z 1.5.61 and DAB-Z was always started after a suspend/resume on a PX5 (Hal9k, Android 8). On device restart it was never started, but the root cause is not in DAB-Z as far as I see. Not sure if it is important: I don't have the FCC premium version.
[Android Head-Units] SpeedFire-:
FCC Launcher Alpha 3.326:

- Tried to further fix Launcher restarts. Please test.

- A red "Delete" button is added to all FCC widgets' settings which will help to delete them easily.

- TPMS widget crash fixed

- When home screen is locked now you can't put an app on it accidentally
[Android Head-Units] mclaudio:
I have Premium if i install Alpha premium will be enabled?

Enviado do meu SM-N960F através do Tapatalk