yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] okij:
[MENTION=9325785]Scopesys[/MENTION]: Also NavRadio+ is still in development, so IMHO it would be a good idea to post this feedback on [MENTION=2734955]KoTiX2[/MENTION]'s thread which you can find here.

I assume that you informed yourself about the different layout options (horizontal and vertical) and the available station logos beforhand, so while it's OK that you wish improvements in this matter, it shouldn't have surprised you that there are no station logos for Maryland yet.

If JPG logos make the app crash, then it's definitively a bug that should be fixed.

As you said, other users may think differently. What I personally like about NavRadio+ in comparison to the stock radio app is:

I like the pre-defined layouts (the stock radio app has just one fixed layout), as well as the possibility to choose one of the pre-defined colour themes and to set my own colours. There are enough possibilities for my taste.

The station scan IMHO works much better than on the stock radio app.

The integration of station logos is better and more flexible than on the stock radio app with FCC's logo support, as well as on the radio app of the Hal9k Mod which also supports station logos since version 4.0.2.

RDS text is handled and displayed better than on the stock radio app and is sent via media broadcast (so that also the FCC media player widget will be able to display it when it has been fixed by [MENTION=4292729]SpeedFire-[/MENTION].)

RDS AF (alternative frequencies of the same station) are handled better than on the stock radio app.

NavRadio+ is in active development and being steadily improved, just like FCC Launcher is.

I just wanted to show you my different point of view. [MENTION=4292729]SpeedFire-[/MENTION]: Sorry if this got a bit off-topic. :)
[Android Head-Units] Scopesys:
But maybe it's right on Topic. ? A healthy discussion and critique of NavRadio+ is useful information for anyone considering using it with FCC, and discussions about it's Pro & Con's, especially integrated into FCC is good.

At the moment, as far as my head unit is concerned, the fact that NavRadio+ seems to be crashing, and FCC reverting to the OEM's Radio App, is not great, but i will keep it installed, and keep re-testing it as FCC develops (and maybe NavRadio+ develops), and will report my findings to other FCC users, here in the FCC forum.

I certainly would not want to run it in Split screen with FCC, but if the APP can work stably with the FCC Player widget doing the information displaying, it would be no more or no less that I am getting from the OEM radio App. However, as a Widget display, most of the option in NavRadio+ become irrelevant in the widget depiction.

---------- Post added at 19:36 ---------- Previous post was at 19:31 ----------

That really needs to be 100% Confirmed. My 500 x 500 jpg images I made for FCC, do make it crash. maybe its a jpg/png issue, or a size issue.

I should really try one of my Jpg images, converted to png to see what is may be causing the crashes.
[Android Head-Units] tonimontoia:
my friend yourself you told me not to criticize the developers, you criticized an application like navradio + without any sense, if you do not know its potential do not defame its author, you are the only person who spoke badly about this application and its developer , I would say that you should make an apology, hello
[Android Head-Units] KoTiX2:
1. I can't comment this because it's just your personal point of view

2. Please send me the Maryland logos archive so I can add it to my repository.

The USA logos has been provided by NavRadio users if you have more please just send them to me.

3. Jpg files don't have transparency and 500*500 image is just too big at takes more resources.

250*250 are enough.

I'm not an FCC user and talking about fresh air I really understand you because I have exactly the same feeling when I got back from this launcher to "my normality" but I don't want criticize it.

As SpeedFire said many times, it's not for everybody, some like it and some not. Just like everything else in the world.

People asked me to make some changes to my app to make it work with FCC and I did it.

It doesn't work?

It crash because FCC handle the original radio app by his own?

Maybe next time try using NavRadio without FCC to check the difference.

I already tried to contact [MENTION=4292729]SpeedFire-[/MENTION] but I had no reply.

I'm sorry but i can't do more on my side to make the apps work togheter.
[Android Head-Units] AdekP:
I wrote about it in the Navradio thread, FCC causes errors in the operation of NavRadio. No other launcher does just FCC.

PS NavRadio is the best application to operate the built-in FM receiver. Other developers of the launcher claimed that it was not possible to extract RDS data to be displayed on the launcher, and KoTiX2 showed that it could be.

[MENTION=1349777]Scopes[/MENTION]: Has the FCC loaded radio station logos with you? Because as far as I remember, adjusting it is a torment: enter the frequency, enter the name of the radio station, load the logo ... 30 times anyway. And you complain that jpeg doesn't support you?
[Android Head-Units] matrixx1:
Hi everybody, dear [MENTION=4292729]SpeedFire-[/MENTION]

I wanted to give a quick feedback regarding v16 and split screen mode. If the screen has widgets it works in 50% but cannot change to 75% or 25%. If however there are icons on the screens not widgets, in split screen the icons become huge and the FCC launcher is not really usable. please see picture to understand better the problem

https://ibb.co/NSSvtmD

https://ibb.co/p3tz8Xh
[Android Head-Units] KoTiX2:
Don't worry about transparency, it's used and showed only in my app.

NavRadio+ add automatically a black background to the logo before sending it as a metadata.

So the result image in FCC, Agama or whatever receiver is a 255*255 image with black background.
[Android Head-Units] variosteph:
if you disable the radio app in system settings, there´s no jumping back to the "old" radio app

works for me
[Android Head-Units] SpeedFire-:
Hi,

Thanks for changes. I will look into the integration with NavRadio soon. This clearly should be done on my side now.

I was busy doing some other urgent fixes.
[Android Head-Units] SpeedFire-:
Please try the betas. This bug is already fixed (long time ago actually).
[Android Head-Units] SpeedFire-:
This beta is mostly for those who use Yandex as a MiniMap provider but it fixes some bugs too.

FCC 3.365 v21:

- Yandex API is updated to the latest release. This also allowed to add many new MiniMap styles from Google Maps.

- Fixed a crash when album art is changed (happened on some devices).

- Volume widget's icons can change color. You can also change a "side margin" for a more compact look.
[Android Head-Units] SpeedFire-:
Here is quick fix for NavRadio.

FCC 3.365 v22:

- FM Radio does not overtake control over NavRadio in this version. However, it seems that NavRadio does not react to the Launcher next/previous commands. Need more investigation.

I've also noticed ANR (Activity Not Responding) error in NavRadio broadcast receiver for some reason:
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

Found an issue that the picture widget is broken.

The square is shown on long click, but no picture. Tried some other pics and had to return to v16.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Ref: Volume widget's icons can change color. You can also change a "side margin" for a more compact look. (Nice :) )

If you are working in that area, could you please consider adding the property to the volume controls, to have have an ACTIVE "Pressed" color when the "+" or "-" icons are pressed .. like, for example, the "Player Play/Pause/Next/Previous" Player WIdget.

see Video

https://drive.google.com/file/d/14hRR-e-ecLdVL23cWf9A7htsTEa0nQWb/view?usp=sharing
[Android Head-Units] SpeedFire-:
Thanks! Image widget fixed: FCC 3.365 v23
[Android Head-Units] rigattoni:
Verified OK!

Thanks for fixing. :highfive:
[Android Head-Units] okij:
Thanks a lot for starting on the NavRadio+ integration and for this first test version! :)

After testing it a bit I can confirm that the control over NavRadio is not working well yet, i.e. the switching between different players and NavRadio isn't always working and sometimes the FM sound keeps playing after switching to a different player, so there's double sound. Also the auto-resume after standby isn't working reliably yet, it starts playing but stops again after some seconds (the NavRadio screen is shortly shown then).

As you already said, the next/prev keys of the player widget don't work yet for switching channels. However, the canbus steering wheel keys are working for this on my PX5. BTW, I have the stock radio app disabled (frozen via Titanium Backup), so it cannot interfere with NavRadio.

What is already working well in v22/v23 is the display of NavRadio's broadcast intents of the station name, logo and RDS info in FCC's player widget. :good:

Also [MENTION=2734955]KoTiX2[/MENTION] for information.
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION],

may I ask you to implement another radio app too? :confused:

Would be really appreciated... :good:

This is from my current new Klyde unit with another new firmware and PX6.

View attachment 5027195

What I could see in logcat is, that the station name is sent by RDS and the PTY. I managed to get a toast on each change of the station name.

The radio app is available by FCC in the widget, but nothing shown (station name).

I can toggle between the player and FM, but that´s all.

The log entry is:

[ 05-25 18:14:47.406 1849: 1849 I/Radio.MainActivity ] mRadioPSName = ENERGY

The radio app is attached. If you need anything else, please ping me.
[Android Head-Units] SpeedFire-:
FCC 3.365 v24:

- AutoBrightness bug fixed (hopefully) when brightness sometimes changed to maximum for 1 minute on the edges of time ranges.

- Fixed an old bug when some built-in FCC icons didn't work from All Apps drawer (such as a device Reboot button).
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Is the design goal with FCC and split screen, to be able to edit a FCC screen when it is in Split mode, or will all editing need to be done in Full screen, in the hope it will automatically scale correctly from Full to split.

Currently when I try to edit a FCC screen when in Split mode, (ie Font size), most widgets I have tried do not respond correctly to font size changes when in split screen mode.

As you have probably realized by now, I am pushing for the ability/option to have screens that can be designed either as Full or Split, and if they are split screen, they will always automatically display in split mode, when they are called (by swipe, or the Page select widget)

Also, if designed to be a split screen, to have a specified default App that runs with that screen, as well as a page Widgets that can call a full , or a split screen with a specified app associated with that screen.

This should give the option of completely eliminating the need to manually split a screen (especially when driving), and to easily select a specified split screen, with associated application, as a press of a page Widget button, as swipe, or a steering wheel button.

This may actually make the code for Editing split screens easier, because if the screen is originally created as a Full or Split screen, then editing is being done in the specified format that that screen was created in . -- as opposed to trying to edit a Full screen that has been scaled to be a split screen, and trying to edit that scaled down screen.
[Android Head-Units] ntldr:
I just installed the latest NavRadio+ which is supposed to work with FCC Car Launcher, but it's not working properly.

I uploaded a video showing what's the problem

https://youtu.be/-YNmmFV2ITY
[Android Head-Units] Scopesys:
It looks to be working in a similar way to how it works on my Px5 head Unit.

You do not seem to have any LOGOs installed for the radio Station you were selected, so, as in my case, you get a default, which looks like part of the Tuning scale.

In your case, it flashes up and then goes away. In mine, it stays displaying (I think) -- I have NavRadio+ logos installed, and they do display correctly (most of the time) (but do not look good, blown up to fit the Player Widget's Artwork window.

So what for YOU is "not working properly" -- It was not clear to me watching the Video, what the issue really is ??

( A little audio voice commentary on these posted video would maybe help)

It also seemed intermittent as to FCC switching to navRadio+ full screen, when you pressed the artwork. Then later, that seemed to work ok.
[Android Head-Units] KoTiX2:
Is the widget configured to have NavRadio+ as player?

I don't see any player configured in middle widget.

Or am I missunderstanding how FCC work?
[Android Head-Units] Scopesys:
I think he must have 4th Player enabled, so the Player widget will use the last player (except players 1, 2 3) as the 4th player, until another new player is started.

He also seems to have the option set for Players to run full screen when the artwork is touched.

Maybe he only has 4th player set up ??

So what is the issue, apart from not having any Logos set for this Navradio+ stations ?

Anyway, this is what NavRadio+ currently looks like when running in the FCC Player widget on my head unit

https://youtu.be/YHF7i-y7Uhw

Note: I do NOT have correct logos loaded for my local radio stations, so the LOGO (FM Freq) will not match the Real radio frequency, as displayed in the FCC Player WIdget's Artist & Song windows. (What does display there is correct for the actual radio station selected)
[Android Head-Units] SpeedFire-:
FCC 3.365 v25:

- Launcher restarts are fixed!!! (I really hope so)
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Just installed this update over top of previous. (v24)

"Can display overlay" permission keeps being requested now to all FCC pop-up notifications.

Did a settings backup. Uninstalled FCC. Re-Booted system. Installed 3.365 v25 as fresh install, and then restored myy FCC settings.

Note:

(1) Install never asked permission to enable "Can display overlay" Permissions, and I am still not getting Notifications, but instead, getting the "Can display overlay" permission not granted popup

(2) This was not an issue when I previously updated to v24

While there may be a way to Manually force to give that permission now, a FRESH Install should have taken care of this automatically ?

( How do I manually give FCC the required permission) ?
[Android Head-Units] jrobbom5:
It's different for different versions of Android, but this should get you in the right place:

Go to Settings->Apps and Permissions. Scroll down to where is says "See all XX Apps", select FCC from the list

Now scroll down and select Advanced (it's not under Permissions for some reason), and then make sure that "Draw over other apps" is set to "Allowed".
[Android Head-Units] ntldr:
Hi there [MENTION=2734955]KoTiX2[/MENTION],

I configured the widgets to use 2 players: NavRadio+ and Spotify. The problem here is that, after selecting the radio station, when I press the Home button, FCC tries to use the default Radio App, which I disabled in Factory settings. Before disabling the default Radio App, FCC was trying to go back it all the time. I saw that [MENTION=4292729]SpeedFire-[/MENTION] just released an update to FCC, let me install that as well and try again.

---------- Post added at 04:06 AM ---------- Previous post was at 03:57 AM ----------

I only use two players. Previously they were the default Radio App and Spotify and yes, the widget is set to go to the currently playing app in full screen when touched, never had issues with that.

The problem is that, once I select a radio station and press Home button to go back to FCC home screen, the radio stops playing a few seconds later.
[Android Head-Units] Scopesys:
‘You little ripper’ That fixed it :) Thanks

[MENTION=4292729]SpeedFire-[/MENTION]

Still a bug, in that"set overlay Permission" should have been set when the V25 was Installed fresh, and installing Version 25 over 24 should not have turned off that permission, that was enabled OK in V24.

One additional bug with NavRadio+ in the FCC Player widget. (Should be a simple one to fix ) :)

When selecting NavRadio+ from a player that has a Song Progress Bar running, the Progress Bar continues to run for NavRadio+ (in the FCC Player Widget) from where it was in the previous player, rather than stop displaying as it should do (and does for say the Default Radio)
[Android Head-Units] Scopesys:
OK.. Thanks .. FYI I do not get that happening with my setup. It may have done that a few versions ago (Cannot remember, so much was wrong back then), but now it works really well.

I just converted my custom FCC radio Logos (For the Baltimore, MD area) into smaller PNG files, and have set those up in NavRadio+. making the ones I have Logos for FAVORITES.

Works really well, and since I can easily change those radio station with the Steering Wheel control, I am Happy.

NavRadio+ does seem to be sending it's own Notification when stations are changed -- don't need that in FCC, so hopefully there is a way to turn that off in NavRadio+

(see Video)

So this is what NavRadio+ now looks like (for me) in FCC, running as a Quickplayer in the Player Widget, and also here is my Maryland(Baltimore Area) Logo set for NavRadio+

https://drive.google.com/file/d/16-yt8NLrPjKBnOjQUrya3QJpDYosCFXG/view?usp=sharing
[Android Head-Units] ric69:
Good job :good: px30 reboots well thanks for this
[Android Head-Units] tonimontoia:
hi friend, if you can post me your backup do you think it can work on mine? thanks
[Android Head-Units] okij:
FCC needs the notifications too for displaying the station name, logo and RDS info in its player widget, so it wouldn't be a good idea to turn them off.

On my setup, I can turn off those notifications in the Mod settings of the Hal9k 4.0.2 ROM (Mod settings -> Radio and Media Player -> Radio -> Show pop-up notifications), so you could look there.

Also FCC itself has its own setting for this (FCC settings -> display -> notifications -> show music-player notifications), which I have turned off in my setup too.

BTW, please tag [MENTION=2734955]KoTiX2[/MENTION] when you post something about NavRadio+ here (like the station logos you created), so he can take notice. I don't know if he's now generally following the FCC thread because of the ongoing NavRadio+ integration.

Thanks a lot, looks good so far! :)

I have one request for the GPS widget: Please make the icon resizeable. Since the last 1-2 versions, it partially covers the satellite count number when I have at a primary text size of 26 pt, which worked before and which I use for all widgets.

Alternatively (and preferably) , you could make the GPS icon smaller and put the text below it, so it fits the layout of e.g. the icons of the combined trip widget.
[Android Head-Units] AdekP:
Hi

I have a question, can I change the FCC logo that is displayed when launching the launcher to my own (e.g. car logo)?
[Android Head-Units] AdekP:
In addition to one of the biggest advantages that NavRadio can send RDS data to the launcher and are covered by this crime;)
[Android Head-Units] Scopesys:
[MENTION=2734955]KoTiX2[/MENTION] [MENTION=4292729]SpeedFire-[/MENTION]

I was not clear ... NavRadio+ has the option to put it's own NOTIFICATION TEXT up on the screen. Its that that I wanted to turn off, and found that that display on/off was an option in navradio+.

The issue is that any changes to that setup in Navradio+ seems to be one change behind (out of sync), so effectively, to turn it off, you have to turn it off, and then turn it back on, and then it will do the 2nd to last thing you told it, ie Turn it off.

-- But there is also an issue with FCC's Popup Notification for Radio, when using NavRadio+

Navradio+ appears to have a lot of information to send as a Notification message to FCC, and FCC seems to be processing that one word at a time, and popping up multiple FCC Radio Notification Pop-Up, as it processes each word, and then it just repeats and repeats.

see VIDEO https://drive.google.com/file/d/166Mc0DkznurgVYYlK6gMt3ijE7A_yZOu/view?usp=sharing

+1 .. Noticed this as well. maybe, like other widgets, both text & Icon can be controlled (on/Off) and with size, as well as the Format property ( ie Text + Icon , Icon + text, just Text, just Icon etc -- like other widgets)

This is another step forward to making FCC widgets have a consistent set of Editable properties.

Some of the newer widgets seems to have got added in a basic form, and got working, but then all their normal Widget Editable Properties were not added.

The Bluetooth & Wifi widgets also fall into this list.
[Android Head-Units] Scopesys:
SPLIT SCREEN -- anyone ??

Has anyone been able to have FCC split their screen when starting an APP from the Icon widget ?

Does not seem to split the screen on my Px5 Oreo 8 Unit, and splitting the screen using Android setting is not really practical when driving.

I did find an App call "Split Screen Shortcut", that allow the screen to be split by various Triggers, or a Floating Button, but it does need Accessibility turned on for that App :(

Somewhat of a PAIN, but at least one only has do it it once per Head unit startup.

Maybe I am making it too difficult and missing something ? Any suggestions of feedback anyone ??
[Android Head-Units] KoTiX2:
I don't have permission to your gdrive to watch the video, please enable the permisssions.
[Android Head-Units] nimslo:
[MENTION=4292729]SpeedFire-[/MENTION]: Thanks for your quick response. But, unfortunately, the bug is still not fixed (Android 6.01). I updated FCC to 3.365.v24, deleted and reinstalled the Route Widget. While the widget works fine with Sygic, it shows no direction arrow with Google Maps, as you can see on attached pictures. It would be great, if you were able to fix this!

By the way, 3.365.v24 has an additional bug: Pressing the "Home" button leads to the main home screen page in any case, no matter what you have choosen in the settings. "Return to the last seen home screen page" does not work any more.
[Android Head-Units] rigattoni:
Use Tasker for such things... I don´t know why you are scared about using root and Tasker, but it´s the master-tool to automate nearly anything in a safe way.