yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] whitewolf8111:
[MENTION=4292729]SpeedFire-[/MENTION] the little bits that I've been able to try, it seems to be running much faster and smoother... However, Setup Wizard/Restore is still rather broken. I can not get past the setup wizard no matter what I try. At first the wizard didn't run after install (complete uninstall and delete of the 2 FCC backup folders) and I went right to the settings to restore my backup settings, then restart the unit and when it comes back up, it just keept looping the setup wizard. I get all the way to where it asks me to place a widget on the desktop but before I can press and hold one long enough, it restarts the launcher and then pops up with the "Something went wrong. Let's try to setup again" and it would just keep repeating the same behaviour over and over again.

So I uninstalled and cleared it all again, and made sure to wait for the prompt for the widget permissions before trying to restore my backup. It still took quite a few tries and restarts to get it to finally restore my backup.

I will report back with other findings once I play around with it for a little while. I did notice in the last version the amount of FCC restarts was reduced by quite a bit... Not sure if I even saw a single one actually!

Getting better and better:good:
[Android Head-Units] SpeedFire-:
This looks like a critical issue. I will try to reproduce it. Thanks!
[Android Head-Units] riccardone1:
I haven't tried version 3.332 yet, but if you often see the mini map (open and close) it remains hidden and there is no way to display it anymore.
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

As others reported, no resets seen within the last updates on my different units: now 3 units with PX5 (MTCD and MTDE), 1 PX5 (CSN2) and 1 Joying (SC9853 with Intel X86)

To be mentioned that only on MTCx units the following features are working:

Automatic brightness

FM radio in all widgets

Bluetooth

As these units are not that rare in the market (Klyde switched completely to CSN2 for all seller), so Pumpkin does not deliver any MTCE unit anymore if the unit is not really car specific and manufactured by other suppliers than Klyde.

From customer point of view the missing features are reported as bugs even if insider know that the implementation for these units is missing.

The market switches in the moment and it seems that CSN2 and Intel units come up more and more, and for this you should make sure that the support for these units is working at least for the most common functionality, before adding new features.... ;)
[Android Head-Units] SpeedFire-:
CSN2 will be integrated probably (however I don't know yet if it has the same interfaces across all manufacturers or everything is custom).

But first we need to make a new release (the last one was in March 2019!). So performance improvements and bug fixes are the top priorities now.

Integrations and feature requests will be implemented after the release.

It would be nice if someone could compare the current release version (3.220) with the latest alphas/betas. I want to make sure that the newer version is better in every aspect.
[Android Head-Units] Scopesys:
Just to be clear, you are seeking a comparison between Current Release version 3.220 and the last alpha/beta you released FCC Launcher 3.328 ?

Specifically, what features and potential bug fixes are you looking to be compared between these two versions.

One factor that seems to be very significant, is on what head Unit these tests are done.

My primary In car unit is an Eonon Px5. I also have an Allwinner that I play about with on the bench.

There is far more differences between these two unit, on any given version of FCC, than between the two versions above, so expect different bug reports from different users having different head units.

FYI: Unless otherwise stated, all my Bug reports will only be for the Eonon Px5.

ie 3.328 has all but eliminated random FCC restarts, compared with 3.220 on the Px5 unit, while they are still very frequent on the Allwinner unit.

However, overall, I find that 3.328 is far more stable than 3.220, with 3.328 starting far quicker after a re-start than the older 3.220

3.328 still has issues when switching players, either with being able to update the artwork and text, and with it often displaying very Historic information (artwork & text), associated with that player the last time it was used, even if that was hours or days ago.

ie it is still putting up very old data, rather than first displaying the default Player screen, and blank text, and then getting the current data from the player.

Instead, it seems to be getting that data form some old, out-of-date cache ??

And there are still times,(in latest 3.328) when after the user has selected another player, FCC then after a short time, switches back to the original Quickplayer, or one of the other Quickplayers.
[Android Head-Units] riccardone1:
same problem on version 3.332
[Android Head-Units] SpeedFire-:
Yes! The idea here is to find out if it is better to push a release now (if 3.332 is better than 3.220) and then fix some remaining bugs like with a quickplayer.

Does it work better on 3.220?
[Android Head-Units] Scopesys:
For me, it seems to be more stable & predictable with the later 3.332.

Would you like to comment or give a brief description of the apparent caching of data for players, and how long that cache remains active.

Is this something that is being changed between versions ??

To me, it seems that FCC is trying to be a little too clever, as far as caching is concerned, and then often put up really out of date data, rather than putting up some default, and then going and getting the current data. I would say that "No data", or a delaying in displaying correct data is better than "Incorrect Data".
[Android Head-Units] bossman4:
I just picked up this 3.332 off the Alpha site

I used it in the garage with my Eonon PX5 unit that I have been using for testing. I had a slight problem during installation where my quick pick for my podcast player on the first menu would not work and my Amazon quick pick did not work on the second quick menu. There was a quick fix by dropping into the Quickplayer setup and repicking the same players.

I rebooted the whole unit after backing it up, both on the SD card and Google Drive. That seemed to work fine, although I have not restored the menus in awhile.

I let the unit start up in the garage with the internet active.

The app seemed very responsive (a lot quicker than before). If I picked between radio, podcast app or Blackplayer EX, the artwork would change correctly; except for the first time Blackplayer EX is chosen ( requires two button pushes for the artwork to change even though the music changes with one button push). This first button push issue after startup seems to be a common hiccup for the past alpha versions. Nothing serious, but annoying.

Amazon art is still a problem (in Speedfire's defense, it has not been worked on), but the music plays fine and the text changes.

I am getting ready for a long car ride and I am very optimistic that the FCC player is going to be performing very well, given the reduction in resource needs with 3.332. Pretty snappy right now.

Just a warning to folks. Speedfire has made some new options available, so sit down and check all the option screens to be sure you are taking advantage of the newer features.
[Android Head-Units] rigattoni:
I also still see major issues with the player widgets, but the over all experience is a lot better than the 3.220. No automatic restarts of FCC in the last Betas so far.

I added a new video, taken on my current Joying SC 9853 on my bench. View attachment 4895343

Info:

There are 4 player widgets on my desktop:

Artist/Station and Songinfo on top

Cover picture in the middle

Player FM-Radio and Online Radio left bottom

DAB-Z and Poweramp right bottom

View attachment 4895339
[Android Head-Units] Scopesys:
I also see the same issue with Amazon art, but it seems to be Amazon specific, so I have concentrated on bugs that are more widespread and common to all players.

Once they are fixed, then might be the time to address specific players and their own unique issues.

Personally, when not beta testing, in the car when driving, I mostly (99% if the time), just use BlackPlayer Mp3 player, with my own music collection on a USB stick.

(Local FM radios station content sucks !!)
[Android Head-Units] rigattoni:
Yes, I know that the American always use the compass. In some cars automatically shown in the mirror too.

In Germany it´s not really useful as you don´t have streets named with directions.
[Android Head-Units] bossman4:
I just got back from a long drive with my EONON PX5. The FCC app is very responsive and I did not get any resets while I was driving. The switching of the music between applications seemed to be smooth, but art is challenged on startup.

Here are some nuances that I don't quite have a grip on......

I had been starting the car up in the garage which has wifi service. This allows the various Quicklauncher applications to touch base on the internet before they go into offline mode. I noticed different behavior of these applications, when I started the car away from the wifi.

I have not been using my cell phone as a hotspot on the road, so the "EONON" cannot link up to the internet while I am driving or starting up the unit away from internet. It appears that sometimes the various "audio" players get hung up (after car start away from WiFi) looking for an initial internet connection. The problem can be fixed by diving into the applications themselves to hit the play button. When I got back, I turned my hot spot on and I will try it with constant internet connection as I start and stop later on today.

These are all startup quirks, that go away after everything is fired up.

With everything "fired up", I can page through two Quickplayer screens quickly. The first main quick player screen (main) has radio, Blackplayer and podcast player. The second Quickplayer page has Amazon, Blackplayer and podcast player. I can switch back and forth between the two pages and pick different players on different screens. The music and text seem to follow the button pushes except for the previously mentioned Amazon Music (future effort).

Like I said before, figuring out the other applications running under FCC with internet service and no internet service probably is the next effort.

If everything works in the future, I expect to have just one Quickplayer screen with the 4 players...…

I think this version is very stable, quick and usable!.

I need to do some more testing with a hotspot and not a hotspot to see how that affects the performance of FCC as it tries to deal with all underlying applications.
[Android Head-Units] okij:
Since I have my head unit (a Witson PX5) for only about a month now, I haven't used version 3.220 for long (I switched to the previous alphas soon) and cannot really compare.

From using version 3.332 for today, I can confirm what other users already wrote: For me it's the most stable and snappiest version so far, also restarting FCC ist very fast now. Switching between the three players that I use (DAB-Z, FM Radio and GoneMAD Music Player) seems to work more stable than on previous alpha versions. :good:

The bug with the swapped artist and title information when using DAB-Z on the FCC player widget happened again this evening. It didn't happen all day, so I was already hoping that you fixed it, but just before leaving my car it caught me again. :p

There was one new bug that I encountered this afternoon with version 3.332: I switched the MiniMap from Google Map to Offline Mapbox display (which worked well on one of the alpha versions about 1-2 weeks ago) and - during the map display tried to build up - got a force close of FCC. I tried to restart it for two more times, which resulted in force closes as well. Then I managed to switch back to Google Map display, which is perfectly working for me. I took a logcat for you (see attachment), so you can have a look what might have caused this bug. It happened somewhere between ~ 17:40 and ~ 17:50 o'clock.
[Android Head-Units] Scopesys:
Growing up without GPS, knowing what direction you generally want to go, and what direction you are actually going was important, to not getting lost.

These days with GPS "Map" you can see your direction, but that means having the map up taking up a lot of screen.

For the past few months I have been driving around with a Torque GPS compass on my dash mounted Phone, and it has made me a lot more aware of where I was going, especially if I do not have a GPS map displaying.

Looked a lot, and cannot find any GPS compass widgets, to use with FCC.

Even if there were, they would take up significant space on the screen.

The FCC SPEED widget seems a natural & convenient item to also have the option to have a Compass rose display, and then it could be used as just a speed widget, a Speed and Compass Widget, or even just a Compass widget (by setting speed font low and same color as background to hide the speed).

[MENTION=1633144]speedfire[/MENTION] Would also be a fun addition to program, when taking a break from working on the Player Widget :)
[Android Head-Units] liamstears:
Depending where you are located I could send you a CSN2 motherboard for testing purposes, I upgraded my motherboard to the DSP version so I could send a non DSP version if it means more features and reliability could be added, this could be my donation to you for your great work...
[Android Head-Units] SharkysRacing:
Just installed this launcher. Got everything all setup was all excited. Open the radio tab and nothing but static. Closed the launcher and opened the factory launcher opened Radio. Perfect. No static. Changed back to Agama. Selected Radio. STATIC!. What gives.
[Android Head-Units] Scopesys:
Are you using the head Unit that you have talked about in other Forums ?

ie

If so, sound like lots of things do not work on that unit, whatever Launcher you are using. !!

Others seem to have issues with this unit, nothing to do with FCC..

see

https://xdaforums.com/android-auto/android-head-units/problem-8227l-head-unit-yt9217b-t3935834

and many other posts in other forums about this unit.

In particular : ref your YT8217 device
[Android Head-Units] rigattoni:
As far as I know, the one and only manufacture of these CSN2 and CSN2-D (with DSP) is Klyde.
[Android Head-Units] SharkysRacing:
I bought 2 different units. Which came in last week and figured i would try something different. These are the following:

YT3518CL_00008_V008_20190529( All Netcom L) _HIFI

System: Android 6.0 Marshmallow Car Edition

Kenel: 3.18.19

No Cambus

DDR: 1G

Flash: 16G

CPU: A53 1.53GHz x4

Capacitance: 10000

Amplifier: AC7315 Mos Bile Duct 46w x4

Display: 1024*600

MCU1: HW3518-3.3-SWO-3.9
[Android Head-Units] Scopesys:
This one ?

https://bingfantech.en.alibaba.com/product/62151636448-814994452/9_inch_4G_LTE_Car_GPS_Navigation_1_16G_Android_Auto_Hifi_Stereo_System_Car_Radio.html

If [MENTION=4292729]SpeedFire-[/MENTION] is told exactly what you have, he should be able to tell you if it is supported by FCC (in particular, the AM/FM Radio), that you seem to be having an issue with when using FCC.

With the cheaper units( sub $100) from little known China Manufacturers (ie Manufacturer: Bingfan Technology), you typically only get what you pay for :(

If there is an option in factory setting ?, make sure your AM & FM radios are set your Country's frequency & channel spacing etc.

If they are still set by default to an Asian setting, then the Radio may well not work correctly.

---------- Post added at 17:10 ---------- Previous post was at 16:42 ----------

Yes -- I can see it jumping between Song & Artist -- strange.

While not a fix, may I suggest what I did on a similar page..

If you move your CLOCK down slightly, you will gain room to have the artist and the song across the whole of the top of screen.

If you do them as separate widgets. one on left, one on right, with each one only have one line. (turn off send line) and on second widget swap song/artist.

This will both give you more horizontal room for the text, but BOTH will scroll as needed...

ie see video

https://drive.google.com/open?id=1YMezj2jZBleflTgwqnifANU-skcVIuPq
[Android Head-Units] SharkysRacing:
One like it. Slight differences. But again. Ive paid $55. And ive paid $300. All the same. Missing internals. Non working features. I dont mind paying $500 if i knew 100% i would get what im suppose to have.
[Android Head-Units] Scopesys:
Agreed -- its a gamble when buying these units... there is always a catch associated with many of them !!!
[Android Head-Units] SharkysRacing:
Believe it or not. This recent unit plays am/fm more clear when set to China Region, instead of US Region.
[Android Head-Units] SpeedFire-:
FCC Launcher Beta 3.333:

- Some more optimizations

- Progress bar in square player widget is larger
[Android Head-Units] mclaudio:
Not available on the play store

Enviado do meu SM-N975F através do Tapatalk
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Optimizations look good -- in that seems even more stable than previous versions.

Switching between players is best so far .. sometimes artwork switches back and forth an extra time before settling down to the correct artwork.

Also, sometimes Amazon & Google artwork stops updating, but can typically be started again, by selecting a different playlist from those streaming sources.

Square Artwork Progress bar -- WIDER -- Thank you (now I can see what is happening with it more clearly)

FM radio - No progress bar -- as expected

BlackPlayer: progress bar runs and appears to always be correct, setting back to zero at start of a new song.

On Amazon & Google, progress bar seems to not behave as expected, and does not reset at start of a new song.. maybe that is right, and in fact, a progress bar when playing a given stream from these players does not make any sense, and in fact, there should be no progress bar ???

However, if in fact these streaming players are sending Progress Position data, it seems to not be being displayed corrected, wrt the start of new songs on these players. or wrt a given play list .

I started to make a Video, but it seemed very random as to what the progress bar was doing with Amazon & Google Players -- could not determine a pattern, and video was getting far to long( and boring !!)

So, does a progress bar for Amazon & Google music make senses? or should it in fact not be showing a progress bar ???

If it should, then it seems to be defective, and I will try again to make a video to show what it is doing...

But overall it looks very good .. I would say the best so far-- and probably worth considering for a Play Store release, if others do not find anything that is drastically broken.

---------- Post added at 21:43 ---------- Previous post was at 21:38 ----------

也许你已经转移到中国了？
[Android Head-Units] okij:
As always, thanks! :)

Did you already look into the bug that I reported (artist and title are sometimes shown in the wrong order when playing DAB-Z)? Any insight or progress yet?
[Android Head-Units] rigattoni:
It´s not about the jumping alone, but about switching player itself.

You can see my touches on the screen and the reaction of FCC is that the player is switched back and forth some times... not always.

Hmmm... this is exactly what I don´t want. ;)

I want to keep audio completely in the middle of the screen. Tastes are different :)
[Android Head-Units] okij:
:laugh:
[Android Head-Units] SpeedFire-:
I haven't received my DAB+ receiver from China yet.
[Android Head-Units] okij:
Ah, I see.

But - since you don't have DAB+ stations in your area and therefore won't receive artist and title information - I think that even when you have got your DAB+ receiver, you have to work with [MENTION=7838245]realzoulou[/MENTION]'s detailed report with background information from my logcat that I posted here.

So I'm not sure if you need your DAB+ receiver to fix this particular bug, maybe analyzing my logcat already gives you some hints how to fix it.

I don't really know since I'm not a developer. Maybe [MENTION=7838245]realzoulou[/MENTION] could post his opinion on this?
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

Did some testing on bench with my:

10.1 Pumpkin

PX5 CSN2

Android 9

Switching between the player seem more stable here. (FM-Radio as expected still not available in the player drop down list)

Progress bar for all music-player (mp3, ogg...)and on DAB-z is working fine.

...but some fine tuning necessary...

The app Radioplayer which does not send a real art work is a bit strange.

As you can see in the attached video, There is a progress bar which is wrong. On top, each time the "album art" changes, the progress bar jumps back to the middle and will never reach the end:

https://xdaforums.com/attachment.php?attachmentid=4896691&d=1575807011

...and the artist and station information is toggled. That seems to be related to the app itself.

Another issue in the player widget found:

If the online radio is playing and I use long click on the widget, the information shown on the widget is from another player which is paused in background. See attached video: https://xdaforums.com/attachment.php?attachmentid=4896753&stc=1&d=1575809949

Over all, I would see this version 3.333 as the next official release.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Ref: 3.333 & Progress bar ( Eonon Px5 Head Unit)

(Thanks for making this progress bar wider)

After doing a little more investigation as to what apps kept a progress bar , I made a 3rd attempt at a video, showing the progress bar issues with the FCC Player widget progress bar.

The video shows what happened when I switches between Players that have a progress bar, and ones that obviously do not (ie FM Radio), and shows how the progress bar displayed in the FCC widget.

While correct Progress bar indications must be a low priority, it is a symptom of something wrong with the Player widget, and the Progress bar not updating correctly, which might also be associated with the artwork etc not updating correctly, (that is more important)

Suggestion: When a different Quickplayer is selected, FCC is now setting the text blank, and the Artwork to default, as soon as the new player is selected, and then later attempts to get the new correct data from the newly selected player.

Maybe, at the same time the the text is set to blank, and the artwork to default, the Progress bar should be CLEARED to zero.

While doing this should only be cosmetic, and won't fix the incorrect display of a false progress bar position, it would be a step in the right direction, and make the transitions between players more consistent visually.

The video attached is a sample of what I experienced running FCC, with an attempt to explain what I was doing, and what appears not to be working as expected.

Ver 3.333 Progress-Bar Video:-

https://drive.google.com/open?id=1Fa8D78WLCE3MKpusZOXlfTDvy3ciZVKe
[Android Head-Units] jukk:
Just a curious question. Do you people in other countries with FM radio have station names and programming available through RDS?

At least in my country (Finland), just like a stock car FM receiver, my Eonon unit radio app shows station name, and if the station sends it, it also lists the title of the current program broadcasted. (Unfortunately, something in the chain from FM receiver to the Android radio app apparently doesn't handle unicode, so any umlaut in station name or program title is turned into garbage).

From that point of view, it feels a bit awkward to have to enter station names manually in FCC.

Example:

[IMG="image"]https://www.dropbox.com/s/m15nd5zkpjz65h6/FMradio.jpg?raw=1[/IMG]