yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
You can still find out if NavRadio+ is supported on your particular head out, and try out the evaluation version, If it does not tune your radio, then there is not point waiting for any fixes, as your radio may not be compatible in any case.

Also, if you want to see it working, there are plenty of Videos on here,showing it working with FCC :)

If the evaluation version does work, then there has been major fixes in the past few weeks to the paid version, and for most users, it is now working more than acceptably with FCC, because both developers were dedicated to getting together and getting any compatibility issues fixed.

When it comes to purchasing Apps, FCC is by far the best "Bang for your Buck" of just about ALL Play-store Apps, and NavRadio+ comes in not far behind.
[Android Head-Units] roydestroy:
Yeah thanks for the suggestions. I already have both apps paid but I am not using their beta versions. As far as I know the two apps work well only in their betas. If I am mistaken please inform me.
[Android Head-Units] Scopesys:
I believe that BOTH apps now have their latest beta Version published as the latest Play_Store version up on Playstore. and both those version work very well together.

@ 6/5/2020

FCC FCC 3.370 is actually on Play Store in the beta channel, but there was a link for it in a previous post by Speedfire- (See link in Next Post after this one)

Navradio+ was just release as latest Version on Playstore Current Version 0.1.63 (Do not use 0.1.62 - previous song steering wheel button bug)

I am running these 2 version together, and they are running great -- Best Yet
[Android Head-Units] Smess1210:
Just to let you know [MENTION=1633144]speedfire[/MENTION] my minimap issues are solved, they may have been since the other alpha but I haven't been using the vehicle so can't be sure.

Thank you and keep up the great work....
[Android Head-Units] nokian95ita:
Good afternoon

I installed the penultimate version of the lancher on my 8227l and unfortunately after a first period of functioning, now every time I press the home button or back it restarts. Tomorrow I install version 3.370 and try, however, I wanted to report this problem Thanks
[Android Head-Units] mclellan83:
Wondering if I should update to the latest version? GPS seems to stop responding and kind of gets fuzzy. Main problem for me is that the always going north doesn't seem to turn off or on when I click on it

View attachment 5034615
[Android Head-Units] bajoseph04:
On my unit, though pressing home button is fine, there's issue when you do multitasking and click close all apps. When you press the multitasking button, you can always see FCC in the recent apps. When you press close all apps, FCC closes too. And starts again when you press the home button. This issue didn't exist in the previous store beta.
[Android Head-Units] Scopesys:
Here is a copy of PART of a post I just made on the

Navradio+ forum

.

The information it contains might be of interest to anyone running FCC, whether they are also using NavRadio+ or Not.

It is specifically targets towards the USA users, as it deals specifically with USA FM & AM Radio Stations

99% of the time I listen to a Mp3 collection on the head units SD card, but it was an interesting exercise to learn about R(B)DS and its implementation here in the USA, as to be part of the Beta Team testing the NavRadio+/FCC integration.

Once again ( I cannot say this enough times) THANK YOU to both APP developers for working together to get BOTH Apps working so well together.
[Android Head-Units] Scopesys:
Video Comparison between FCC/NavRadio+ "change station" widget responses, Today, vs a few days/version ago.

Current versions seem to be a step backwards to how well it was working a few days ago.

Having Videos of both, makes it far easier to see the difference, rather than a mass of TEXT description of the difference.

Video: A few days ago, (older versions) working well

Video: Today, (latest versions) NOT working nearly so well
[Android Head-Units] SpeedFire-:
There was no any release of FCC in these days. Which versions do you compare?

Maybe NavRadio app was updated?
[Android Head-Units] Scopesys:
Lesson learnt, and not to be lazy .. always show APP version at start of Video.

Both Videos running Navradio+ as the Radio Player

1st (older Video) June 3

FCC v29

NavRadio 1.51 (Then current latest Version)

2nd (newer Video) June 6

FCC v29 (same as June 3)

NavRadio 1.63 (now current latest version)

So same FCC but different NavRadio+ versions

In hindsight, it can be seen that FCCwidgets are still quite responsive to Station changes, but the navradio+ widgets are slower.

Maybe any apparent slow down of the FCC widgets is a function changes made to NavRadio+ , as it is NavRadio+ that is the running APP
[Android Head-Units] KoTiX2:
I have changed some code in NavRadio widgets that was causing a bad crash at startup so I guess the difference is there.

I will look at it.

Then regarding the PTY information show in NavRadio widget I could make it send that info as music GENRE metadata but I need to know if FCC can show that info in the widget.

[MENTION=4292729]SpeedFire-[/MENTION]

Right now NavRadio send the artwork, title and Artist data, what else can FCC display?
[Android Head-Units] SpeedFire-:
I think I can use the GENRE field.
[Android Head-Units] Scopesys:
Great ..... does that also mean that if the FCC Player widgets is made to be able to display the GENRE meta data, that it might also be able to display that information from Mp3 players, if they send that info ( and of course if that meta datat is on the Mp3 file)
[Android Head-Units] nokian95ita:
[MENTION=9483956]bajoseph04[/MENTION]

thanks for the reply but I don't go for multitasking and I don't press the button close everything. this simply happens if I open another app and go back to the home via the home button or via the back button and it also happens when I go back from the reversing camera

Inviato dal mio Mi 9T utilizzando Tapatalk
[Android Head-Units] bajoseph04:
I believe the dev is busy working on new features.. Split screen, navradio integration etc. Hopefully once people are happy with it, we may expect stability improvements
[Android Head-Units] Scopesys:
(Deleted by Poster)
[Android Head-Units] jrobbom5:
I finally got around to trying the split-screen feature using the beta version from the play store, and noticed a few problems. To start, I just set Google Maps to start in split-screen mode.

1) When in split screen, the status bar is displayed. I have it turned off in the FCC settings. It is only shown on the launcher half of the screen, not on the maps side.

2) When I press the maps icon, the screens split and maps is shown correctly, but the launcher only displays the skin. Icons and widgets are not displayed. Once I press the Home button, the launcher finishes loading correctly

3) When I try exit split screen, by dragging the little bar in the centre either left or right, then maps is shown in full screen, regardless of which way I swipe. I need to then press the home key to return to FCC in full screen.

All in all though, really great feature and one that I will find very useful. Thanks [MENTION=4292729]SpeedFire-[/MENTION] for all of your hard work on this.
[Android Head-Units] WizzardMaker:
Volume controls and screen brightness no longer working

I have an Allwinner T8 Android 8.0.1 system

Both audio and screen brightness worked before but now it stopped working. I joined the beta program, but I don't know if it stopped working because of that or before that

My device is rooted and I am ready to give you everything you need
[Android Head-Units] SpeedFire-:
Please check that AllWinner type of device is selected. FCC Settings - System - Advanced - Device type.
[Android Head-Units] WizzardMaker:
Yes, Allwinner is selected
[Android Head-Units] KaraSSi:
Hello. In My case automatic brightness and calling is not working. What kind unit i have and is it supporting?

HU info screenshot

https://ibb.co/CHqZGqv
[Android Head-Units] NabeelYAF:
cant get bluetooth or radio to work with widgets

Hello,

i cant get my bluetooth or radio to work with the homescreen widgets

the apps are preinstalled in the headunit called BTMusic and FM Radio

the headunit is somewhat locked since i cant access any bluetooth settings and if it wasn't for the launcher i wouldn't have been able to access Developer settings

android settings showing android version 9.0 while its 7.1.1

Device info

Manufacturer: Allwinner

Model: QUAD-CORE T3 k2001-nwd

APPVER: K2001n-NWD_20190823.13502218.N0026.01

PlatfromVER: K20n-2019/08/06

MCUVER:v3.0-FF01-20190218-A02-CAN0000-00-00-DVD000000000-00

BTVER: GOC_XR829_4.0/2019/07/26

am i having hardware compatibility issues ?

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

If you do implement this, will it be similar to the Song, Artist un the Player widgets, and able to be turned on/off, size & color, and able to be displayed separately, or displayed on top of the artwork ?

On the subject of displaying text on Artwork, this has always seemed to me to have issues. While FCC has the ability to select the colour of that text on the artwork, this is the one case in FCC (apart from speed in the map), that text is placed on a background, whose color could be anything.

So there will some background where, whatever color you choose for text, the text will not be visible on the Artwork background.

Artwork MASK provides a crude way to improve this, but degrade the Artwork image, and with only fixed masks, cannot cater for every text selections.

There is however a very easy, PERFECT solution. "Text Stroke & Fill" which I believe can be made a controllable Text Property.

EG: For example, if the Text color to be placed on the Artwork is WHITE, and an Artwork, that is primarily white is selected, the text will still show up.

The amount of stroke can be adjustable to produce more "surround" background.

So, if artwork was mainly BLACK, and SONG/Tile is "Hello World is also Black, you would be able to see the Black text on the Black background

(see attached File below)
[Android Head-Units] kramttocs:
Just found out about this launcher yesterday and purchased the pro since it's so much better than the one I had.

I am using an Atoto A6Y Pro.

Most things work great but I can't figure out the voice call.

When I go through the 'wizard' to make fcc the default it opens a search window for 'Call John Smith'. There aren't 3 dots to click anywhere. I've never tried voice calling on this device but would really like to use it.

What am I missing?

Thanks in advance.
[Android Head-Units] okij:
[MENTION=4292729]SpeedFire-[/MENTION]:

As I posted here and here, there are some remaining NavRadio+ integration issues.

For some of those issues I'm not sure if they might have to be fixed in NavRadio+ or if they have to be fixed in FCC Launcher, so I just posted here on the NavRadio+ thread and asked [MENTION=2734955]KoTiX2[/MENTION] to also have a look into these and give some feedback. Those issues are:

The remaining two issues that I already reported are some malfunctions of the DAB+ integration, which was working perfectly before, but since your latest changes has those bugs:

Will you fix those DAB-Z related issues or should [MENTION=7838245]realzoulou[/MENTION] also have a look into these, because your new method to access media players (as I understood it) is better than the old method and should be adopted in DAB-Z too?

[MENTION=7838245]realzoulou[/MENTION]: If you have some time, it would be great if you could get the latest FCC version 3.370 that [MENTION=4292729]SpeedFire-[/MENTION] posted here and give us some feedback after having a look into this.

Thanks in advance for looking after this. :)
[Android Head-Units] Scopesys:
I have a POSSESSED Head Unit ???
[Android Head-Units] okij:
[MENTION=9325785]Scopesys[/MENTION]:

If you possess your head unit, of course it's a possessed head unit. ;)
[Android Head-Units] pug304_:
yesterday i tried to change somd apps/widgets on my HU, newest "official" (no beta) FCC version from google play, especially i tried to get Sygic icon im main screen. Not sure what happened but a popup appeared "if like to get to icin back go to FCC settings.. Since that my Sygic icon is hidden (not deactivated!), but Sygic is working due to i has assigned it to Nav button on the HU.

I doublechecked everything twice, but i didn't found the proper place to unhide the icon? Ideas?

HU is a pumpkin PX6, running on Hal9k 4.0.2
[Android Head-Units] rigattoni:
FCC-Settings --> System --> Advanced --> Hidden Apps
[Android Head-Units] kramttocs:
Spent the last couple hours customizing this launcher. Really impressed.

Few things:

1. Chrome as a widget shortcut won't stay open. It restarts. Due to it treating it like a player?

2. On the media widget (center piece) I changed the Player Default icon to see what it did but I can't change it back to the blue/grey checkered wave. Clicking Default doesn't work.

3. Since I am hiding the status bar as I figure most are it would be really nice to have a widget that shows the phone connection status symbols like signal and battery

4. Nice if the WiFi widget would show traffic arrows if possible

Let me know if there is a better place for feedback
[Android Head-Units] Scopesys:
For NavRadio+ FCC users.

If you are using FCC, and you modify the Options in NavRadio+, to alter what RDS information gets sent as Song, Artist, Album - then it looks like you will need to Re-Start FCC for the changes to take effect. in FCC.

(At least, that is what I am finding in practice, at the moment -- Not a big deal - you probably will not be changing those navRadio+ options at all, once you have set them to what you want (or left them as the default)

[MENTION=4292729]SpeedFire-[/MENTION]

For other Players, hopefully the adding of this 3rd Item , will mean that the FCC Player widget will now support 3 Text fields, Song, Artist, and now the addition of Album ?
[Android Head-Units] kramttocs:
Is there something I need to do to get the Atoto default FM Radio working in the quickplayer? In the options just 'Radio' isn't available and the FM Radio choice doesn't seem to apply to the Atoto radio. When it is selected in the quickplayer and I click the widget to open it I get a Play Store window that says not found.
[Android Head-Units] pug304_:
embarrassing, sometimes you're just incapable :angel: Thx for the trick!
[Android Head-Units] okij:
[MENTION=4292729]SpeedFire-[/MENTION]: I hope that you are well, because lately it has become a bit quiet on this thread. There hasn't been a test release within the last ten days, which seems unusual and which we're not used to. ;)

Today I tested [MENTION=2734955]KoTiX2[/MENTION]'s latest NavRadio+ 1.69 with the current FCC 3.370. All of the remaining integration issues which initially I posted on 3rd and 4th of June and then summarized in post #6331 are still existent. Please tell us when we can expect a new test version, since after ten days of waiting I'm now a bit frustrated that I didn't even get a feedback about my bug reports. :(

I talked with [MENTION=7838245]realzoulou[/MENTION] about issues #4 and #7 (which affect your DAB-Z integration) and he told me that the Intent Extra which keeps DAB-Z in the background when launching it currently is not sent by FCC, so you have to add it again to fix those two issues.

The latest NavRadio+ 1.69 now sends PTY information via Metadata ALBUM field, so we hope that you will add an option to display a third text field in the FCC player widget to be able to display album respectively PTY information. :fingers-crossed:
[Android Head-Units] rigattoni:
I have the same issues on my units.

Because I am just now working on my RL7AC_ head unit, I can´t say anything about NAvRadio+.
[Android Head-Units] kramttocs:
Looks like the display brightness settings aren't working on the atoto S8 either.
[Android Head-Units] Scopesys:
Hi Guys .. how are things back in June ?? I'm posting this and a Video from the Future, From the USA at the end of November 2020, so sit back, relax and enjoy (

and don't take me too seriously

)

You might find it interesting to see FCC & NavRadio+ in a few months time.... assuming this video does not cause a Time Paradox, and things turn out differently..

Video: Sent back in time from Nov 2020
[Android Head-Units] rigattoni:
But... this is only one radio app, used by a handful of user in this thread.

There are other important fixes to do too, even if you guys really want it.

CSN2 units are not fully implemented and the amount of CSN2 and CSN2_D are raising from different supplier.

I asked for integration of at least the factory radio app for my new RL7Ac unit from Klyde. Unfortunately I even did not get an answer on it.

..and yes, I really appreciate the hard work [MENTION=4292729]SpeedFire-[/MENTION] is doing in the background to give us this really great launcher.

May be [MENTION=4292729]SpeedFire-[/MENTION] you have some time to answer these questions:

What is planned to get CSN2 units implemented?

What is from our side needed to help?

What is needed to get some most used features implemented in RL7Ac units, as FM radio, volume settings, backlight settings?

I can provide any needed software to help out. I would be able to test it if you would provide any test builds....
[Android Head-Units] kramttocs:
I am new to FCC but I agree. Not to sound ungrateful - more so that FCC is so nice that I'd like to see more people be able to take advantage of it.

I would really like to use that radio app but it isn't compatible with my headunit. I don't know enough about the different mcu's and whatnot to know if I am in the minority or majority that can't use it.

Like rigattoni, it would be nice to see FCC work with all of the factory radio apps as well as the core functionality (like brightness) working across the board.

That said, if the focus of FCC is only for certain units/mcu's than that is Speedfire's choice and can be respected. I just really think this launcher is the best out there (even with some of the things not working with all units).

I am also happy to test and provide anything needed.
[Android Head-Units] rigattoni:
There is another most important thing to keep in mind...

MTCD and MTCE units will die out in the nearer future. The new standart will be CSN2 units with PX5 and PX6 and bigger units usable in portrait and landscape mode (Tesla style) with RL7Ac MCU...
[Android Head-Units] okij:
But that is not the point.

[MENTION=4292729]SpeedFire-[/MENTION] made a great success in implementing NavRadio+ support about two weeks ago and then all of a sudden stopped to release any new test version, be it with the needed remaining fixes or other stuff. Also he participated on this thread much less then usual, that's why I think that he is busy with other things in life at the moment. Just a guess.

As it is now, not only the NavRadio+ support still needs some bugs to be fixed, but also the DAB-Z support which was perfectly working is broken in the latest test versions from about two weeks ago and needs to be fixed.

[MENTION=2534110]rigattoni[/MENTION] please be fair and let other users also ask their needs and have their wishes implemented, as you do too. At the beginning of this year, I acknowledged that [MENTION=4292729]SpeedFire-[/MENTION] was busy working on your request for improving CSN2 support, so I waited with asking him for looking into other things until CSN2 support was sorted, as you can read in my post from 12th January:
[Android Head-Units] Scopesys:
I know I am stating the obvious -- but :-

That's the nature of the beast -- in development, one thing can get fixed, and another stops working. Past events have shown that Speedfire will end up getting it sorted, but it may take some time .. Summer Holidays-- A life - Work- Remember FCC is just his "Hobby"

If you are beta testing new beta Version, just make sure you have your setting backed up, and you can always uninstall, and go back to a previous version, if you think that will temporarily serve you better,

The FCC settings "Backup" & "Restore" is working well, and is a WONDERFUL THING :)

I think we got really SPOILT last year when Speedfire went on Holiday, and ended up working on FCC almost every day of his Holiday. I am sure he needs a break..
[Android Head-Units] Drunkenninja:
Is there a way to reset the Phone Call settings in FCC, I have trouble making calls using the in built FCC settings (I receive them fine), Google asked me the first time if I wanted to use MTC Dialer or FCC to make calls and I chose FCC and have had this problem since, is there a way to go back to MTC Dialer?

Also, does anyone know how to remove Beta updates, I want to try the latest stable version just to compare functionality and stability.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Hi .. everything OK at your end ? maybe you are on vacation, and if so .. GREAT -- relax and recharge.

Many of us on the forum are getting a little concerned, with not see you here for quite a time, and obviously, things like the Corona Virus are on everyone's mind.

So I hope everything is going well for you, and maybe a quick "Hello. Hi Guys . I'm OK" would put a lot of caring minds at rest
[Android Head-Units] kramttocs:
I can't help on the phone as I can't seem to get FCC to own that part but for the beta you should be able to leave it from the play store. First I would backup your settings so you can uninstall and reinstall in case it doesn't automatically push the latest to your device.

[MENTION=9325785]Scopesys[/MENTION] If it helps add a little peace - I'd emailed him the other day asking if this thread was the best place to report issues and he responded fairly quickly confirming that it was
[Android Head-Units] VladimiroCampus:
FCC Carluncher pro & Navradio+ issues

Hi everyone,

I have an Android MTCE unit with Android 9, Rom Hal9k 4.02 and FCC Car Luncer pro version.

I currently have FCC 3.370 and Navradio + 1.69.

In the system section I set the app to start automatically like this:

10 sec wait, 3 seconds between one app and another.

1) Waze

2) None

3) Navradio +

4) Home screen.

After activating Navradio + the app works if it is displayed in the foreground and as soon as you return to the home (and therefore it is put in the background) it stops working.

It happens to you too ??? I don't know what to invent in advanced settings anymore ...

My homesceen uses the minimap....

Thanks in advance...

Bye.
[Android Head-Units] pug304_:
it stops working in terms of app get in back and sound stops? Same happend to me. When i changed almost all settings in Navradio and also FCC regarding showing popup informations the issue gone nearly complete. It's same from time to time, but rare. BTW bringing Navradio in front by pressing FCC shortcut it seems to be way more stable.

No waze, no minimap on my system! IMHO an issue FCC/Navradio. Please don't ask in detail which change i've done ;)
[Android Head-Units] kramttocs:
I feel like Speedfire is getting bombarded with things right now :)

A few more things I am running into:

1. When not set to full screen view (so the Status Bar is visible) the app drawer doesn't respect that area. The top row of apps are partially underneath the status bar

2. Can the status bar be hidden from the Screensaver screen?

3. I don't know that I intend to use the Left Panel but I am not seeing it working or else am not configuring it correctly. The space is allocated but it's blank.
[Android Head-Units] rigattoni:
I am far away from beeing unfair. I just wanted to mention that there are still major issues in the implementation.

...and yes you are right, you gave me time to get at least the rudimental things working on CSN2 units. But a lot of things are untouched yet.

I just asked him for answers on my questions. Nothing else. ;)

I never wanted to be understood as I wanted to blame or push. I really appreciate all the work [MENTION=4292729]SpeedFire-[/MENTION] did for us and especially also for my units.

To say it once again: This is by far the best Car Launcher in the market!