yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] HatManSan:
I have only "just" noticed the OBD widget. It offers some great info. However I cannot get it working. I have the official XTRONS obd dongle that works fine with Torque. None of the OBD protocols produce results. Am I missing something? Cheers
[Android Head-Units] okij:
Thanks for these infos! :) I just notified its dev @KoTiX2 here on the NavRadio+ thread and asked him to add the station logos to the notifications.
[Android Head-Units] okij:
Thanks for test109. I now had some time to try it and am glad to confirm that I now also didn't have any issues with GMMP. (y)

Switching between DAB-Z, NavRadio+ and GMMP Classic worked as intended for about 10 minutes of switching forth and back, so in my point of view this should be fixed now, which is great.

So the only issue left is the NavRadio+ station logo which most, but unfortunately not all of the time is displayed. I hope that @KoTiX2 will add the station logo to the notification, as you asked for.
[Android Head-Units] SpeedFire-:
Great! Thanks for testing!
[Android Head-Units] 2ndjobmoney:
I use split screen a lot.

Since version 102, I can't select split screen from the home menu.

Does it no longer support split screen?
[Android Head-Units] SpeedFire-:
Please check that this checkbox is enabled (if available):

Fcc Settings - System - Use split screen (the first option at the top)
[Android Head-Units] 2ndjobmoney:
My Unit is Android 8.1 and Not show split screen checkbox in System option
[Android Head-Units] HatManSan:
t109. Running Poweramp ONLY today, no NavRadio etc. All was fine on boot apart from the usual letter M, but in trying to get BT to work with the Xtrons dongle (it used to be fine) to experiment with the OBD widgets, I changed the BT type. I forget which one it was on. :( My iPhone 12Pro was invincible to the radio as well. Anyway I now have no idea what BT module is in my PQS1039BL (If anyone knows please let me know). So on reboot I ended up with wrapped text and although PA was running and playing the widget didnt follow suite, even after about 3 mins waiting. I have included a LC this time. Thank you

Screenshot

LogCat
[Android Head-Units] SpeedFire-:
Thanks. Here is a fix - fcclauncher-3.442_test110.apk
[Android Head-Units] okij:
Happy New Year @SpeedFire- and all users of FCC Launcher! 🍾🥂
[Android Head-Units] mariodantas:
Yes @SpeedFire- You deserve it from the FCC community
[Android Head-Units] KoTiX2:
I tested this last FCC build on Allwinner, MTC and UIS7862 units and the results are different on each on them.

Results are also inconsistent on the same unit but let's say that the station logo is shown for most of the times.

The metadata that NavRadio have always sent are:

METADATA_KEY_TITLE, METADATA_KEY_ARTIST,

METADATA_KEY_ALBUM,

METADATA_KEY_ART

I'll add the METADATA_KEY_ALBUM_ART in the next release but this is not the problem IMO.

I'm pretty sure it was working ok in previous versions of FCC even with KEY_ART only and i haven't made any changes in the metadata code since a long time.

Happy new year to everybody :)
[Android Head-Units] SpeedFire-:
Hi

Please note that we are talking not about broadcasts sent by NavRadio+ but about player Media Notification (which is shown when you scroll down the status bar).

Currently there is no album art shown there. Could you please consider adding it?

Here is an article which can also help.

Playing nicely with media controls

News and insights on the Android platform, developer tools, and events.

android-developers.googleblog.com

The most important part:
[Android Head-Units] okij:
Happy New Year to you too! :)

Does this mean that the station logo will be shown in the notification in the next release of NavRadio+? I'm asking because FCC fetches it from the notification.

Edit: I just saw that @SpeedFire- was faster than me. ;)
[Android Head-Units] KoTiX2:
Yes, I'm talking of player metadata not broadcasts.

As i said NavRadio always sent the bitmap: MediaMetadata.METADATA_KEY_ART because a new bitmap is created in runtime to add a black background for some transparent logos and it was working fine.

logos are 255*255 pixels max.

For sure it doesn't send the uri MediaMetadata.METADATA_KEY_ALBUM_ART_URI , i never used this key.

I'll see if I can handle the uri instead of the bitmap and add all the keys if this is the problem...
[Android Head-Units] SpeedFire-:
I think that METADATA_KEY_ALBUM_ART_URI and METADATA_KEY_ALBUM_ART can be used interchangeably. So no need to use METADATA_KEY_ALBUM_ART_URI particularly. I think the major task is to see the Album Art in the notifications which isn't the case currently. I can't make a screenshot at the moment but I hope @okij can show this.
[Android Head-Units] KoTiX2:
Ok, to be shown in the notifications i also need to add the "mediastyle" part i guess, which is not there now.
[Android Head-Units] SpeedFire-:
Good point. This can probably fix the issue.
[Android Head-Units] SpeedFire-:
Happy New Year everyone!

You are what drives the app development and motivates to change it.

I am really excited about our community!

You are the best! Happy New Year! :love:🥳🎉
[Android Head-Units] rigattoni:
Happy New Year to everyone in this thread.

This community is really exciting. :love:
[Android Head-Units] HatManSan:
Happy and Prosperous New Year to all!
[Android Head-Units] mariodantas:
Great, two big developpers together: @SpeedFire- and @KoTiX2 (FCC and NavRadio)

By together I mean in the same forum tharead LoL
[Android Head-Units] SpeedFire-:
Guys, please test fcclauncher-3.442_test111.apk

- Brightness widget is slightly fixed again

- Auto-brightness should work for those who had issues

Please test that brightness and auto-brightness work fine now.
[Android Head-Units] dgeffe:
Hallo

Funktioniert das Radio mit FCC?

Hello is the YT5760B radio supported?
[Android Head-Units] hoffeck01:
Is there a way to make the light frame around the map dark at night?

View attachment 5498633
[Android Head-Units] SpeedFire-:
Is this a test version?
[Android Head-Units] hoffeck01:
Yes. It is the 111.
[Android Head-Units] SpeedFire-:
OK. What is the name of this map theme?
[Android Head-Units] hoffeck01:
This is the Google Map. The theme is the last of the selectable themes.

View attachment 5498717
[Android Head-Units] SpeedFire-:
I mean in the Map Settings you have fields like "Day Theme" and "Night Theme" where you can select different color themes for google maps. What theme is selected?
[Android Head-Units] hoffeck01:
OK I understand. It is automatic.

The map is dark but the frame is light.

During the day, the map is bright and so is the frame.
[Android Head-Units] cillerbee:
Hi, I was wondering if FCC Launcher works on UIS 7862 FYT Models? I have the EKIY 6GB 128GB Model

Thanks
[Android Head-Units] mariodantas:
Yes it does
[Android Head-Units] schloram:
Hi @SpeedFire- ,

I have a M.I.C AV8V6 with Stock OS. The radio comes with a preinstalled App called "Vehicle". Inside this app I can see some information about my car (see screenshot). This somehow works without the need of an separate OBD Dongle. Don't know how.

Now I have an OBD Dongle from my car manufacturer. This Dongle only works with a dedicated app (Skoda Connect Lite) and gathers information about fuelling and the travelled routes to display it in nice statistics.

Since I don't really want to switch the dongle because I like the Skoda App too much, my question is: Is it possible that the FCC launcher could make use of the data shown in the photo below without OBD? I mean the data is already present without an OBD Dongle so it shouldn't be too hard for FCC to fetch this info. Or is it?

Thanks for your time.
[Android Head-Units] rigattoni:
These information shown in your picture are from your Comfort Can, which is connected to your unit. These information are available for all VW-group cars since a long time because they are used in the OEM radios too.

You don´t need any OBD dongle for these information.

I don´t know if this can be activated. You need to search for it in FCC (Add App to screen). If you don´t find it, you may be able to get it working by Tasker. Needs to be evaluated.
[Android Head-Units] Joscj:
Hi,

I have a Joying JY-UQD80N4G unit, and I’m having trouble getting phone calls through FCC to work. I’ve managed to get my iPhone connected to FCC via Bluetooth, but I’m not able to set FCC as the standard phone app. When I try to set up FCC as the default phone app from within the FCC settings, it just takes me to a Google search for “call John Smith”. When I open Android settings to change default apps, phone app does not show up as an option. If I install google phone it will show up as the default phone app, but I’m not able to change it. Is anyone else having this problem, or am I doing something wrong?
[Android Head-Units] SpeedFire-:
I can't reproduce this issue on my device with standard night theme.

Please check what night theme is selected here.
[Android Head-Units] SpeedFire-:
This really depends on the head unit and its software. Sometimes this data is easily accessible (if it is broadcasted to the system, therefore to third party apps like Fcc Launcher). But in most cases this data is not / hardly accessible and is contained inside the particular app.

Overall this is what I call "deep integration". It is required to have at least apks and LogCat logs at minimum. You can try to record LogCat logs (see the first post).
[Android Head-Units] hoffeck01:
@SpeedFire-

I'll see tomorrow. However, I have not changed anything.

I still found out that if I switch from "automatic" to "night" then the bright frame disappears.
[Android Head-Units] SpeedFire-:
You're right. Google updated its Google Assistant several months ago so no calls via third party apps (like Fcc Launcher) are allowed now. I should probably delete this feature or mark it as unavailable.
[Android Head-Units] Joscj:
I see. That sucks, the Joying app isn’t great. Thanks for replying, though. And Thanks for an amazing launcher, it totally transformed my HU👌🏼👌🏼
[Android Head-Units] SpeedFire-:
New test version is out: fcclauncher-3.442_test113.apk

- Volume and NaviLink widgets are rewritten to the new widget type

- Some small bugs are fixed.
[Android Head-Units] daemondee:
I use Car Radio app for listening my favourite local radio stations. It can send a logo to launchers but it not appear correctly in FCC player widget. You can see that at attached image 1. I tried the same thing in android emulator and there the station logo is displayed as it should (see attached image 2). @SpeedFire- could you please take a look if the problem is only on my CSN2 head unit or is this happening on the other units as well? Thank you.
[Android Head-Units] SpeedFire-:
Do you mean it is fit incorrectly?

Can you give me a link to the app?
[Android Head-Units] daemondee:
Sorry for bad information. Yes it is fit incorrectly. If the station logo is symmetrical, it is fit correctly, but if it is longer in width than in height, it is fit incorrectly.

Here is a link to the app.
[Android Head-Units] SpeedFire-:
I can confirm that it is displayed correctly in Android Emulator.

The player layout includes this parameter:

android:scaleType="fitCenter"

This parameter should fit album art properly.

I can't tell why your CSN2 unit ignores it (probably).
[Android Head-Units] daemondee:
Will it help you if I record a logcat?
[Android Head-Units] SpeedFire-:
No
[Android Head-Units] daemondee:
Ok, thank you anyway.
[Android Head-Units] daemondee:
I tried this now on my phone (Galaxy A5 2017, android 8), clean installed test113, set up new player widget and it is the same as on my head unit. The logo is not fit correctly.
[Android Head-Units] SpeedFire-:
Thanks! I reproduced this on my Samsung device as well. I will investigate this.
[Android Head-Units] SpeedFire-:
Here is a fixed version: fcclauncher-3.442_test114.apk

It turned out that album art was cropped to square by default.

Now I've added an option to the Player widget settings (crop is now disabled by default)
[Android Head-Units] daemondee:
Thank you @SpeedFire- ! 🙂 I just tried it on my Samsung phone and it works perfect.

Thank you for such a quick fix. 🙂

Edit:

Also works on my HU. Thanks! :)
[Android Head-Units] kill_one:
hello @SpeedFire-

could you put an on-screen lock option in widgets? So that they cannot be mobilized by mistake if enabled? Thanks a lot for all :)
[Android Head-Units] SpeedFire-:
It is available. You need to long click on an empty part of your home screen and then click on a lock icon in the bottom right corner.
[Android Head-Units] okij:
@KoTiX2 Today I've noticed that besides the album art there's one more thing missing in the NavRadio+ notification:

In the 1st attached screenshot you can see the RDS text on the main screen of NavRadio+ (in this case it's the currently playing title "Lewis Capaldi - Before You Go").

But as you can see in the 2nd screenshot, this information is missing in the NavRadio+ notification, instead only "[2] 99.20 MHz" is shown.

Because of this also the FCC Player widget only shows "[2] 99.20 MHz" instead of the RDS text, as you can see in the 3rd screenshot.

Therefore I'd like to ask you to not only add the album art to the NavRadio+ notification in your next release, but also show the current RDS text in the notification (or did I miss an option which already enables this?) The notification should only show the generic "[station number] xxx.xx MHz" when there's no RDS text available. Thanks in advance. :)
[Android Head-Units] KoTiX2:
Ok let's explain what kind of notifications NavRadio can show/send (since the beginning..)

There are 4 different type of notifications:

1. Toast (timed) message

2. Status bar icon

3. Drop-down "quick settings" panel notifications (or whatever it's called)

4. Mediaplayer metadatas

The 1st one show the logo, the station name and frequency. You can select in settings the time duration and position on the screen.

The 2nd one show only the white NavRadio icon on status bar

The 3rd. Is the one you are talking about and because NavRadio wasn't born as a mediaplayer it actually show only those things you see.

The commons mediaplayers can show other things using a different approach with "mediastyled" notifications. I will try to move to this approach after that the porting to FYT units is done.

The 4th one is used to send the logo and rds infos to Agama, FCC etc.. to be shown in their player widgets. In NavRadio settings you can choose the order of the name,text or pty because each launcher use a different sequence.

If i understand, FCC use the 3rd option to create a kind of mediaplayer widget in home screen but my app right now cannot send all the infos it needs and actually it never did.

What I don't understand is why everybody need all this now when it wasn't necessary a few months ago...
[Android Head-Units] okij:
AFAIK @SpeedFire- switched from using mediaplayer metadatas to using drop-down notifications when rewriting the Player widget some months ago. He found this to be the more reliable way.

@SpeedFire-: Please correct me if I'm wrong and if possible give some more details to @KoTiX2.
[Android Head-Units] SpeedFire-:
Correct. This way proved to be more reliable for the launcher to communicate with players. As far as I know other car launchers (like Agama) do not work with several media players and do not allow to switch quickly among them. Therefore this is an easier task for them to control "the only one" selected player and get a data from it.

Fcc Launcher, on the contrary, needs to identify correctly which player is currently playing, which media data is required to be saved / displayed and which should be ignored. For example some players send their media data with "paused" state AFTER the other player is already playing, so this is a much more complicated task than just to show the latest media data received from the Android system.

Things become even more complicated when custom mods (like Hal9k) are installed. These mods often want to send their own media data in parallel with built-in FM radio or NavRadio+.

Some of the updates from all of these media apps include large album arts (which should be saved), some include low quality arts (which should be ignored), some do not contain them at all (and here you need to decide - do you need to show the default art or to find a saved high quality art. If you decide to show high quality art - are you sure it belongs to the same song / radio station? What if the artist/song name was slightly changed?). For example I noticed that NavRadio+ sends the default FM radio freq first and then a second update with the assigned radio station name.

Therefore from the Fcc Launcher's point of view the "simple" task to display current media data is a really difficult one. The launcher receives multiple updates from different media players / radio apps / mods - sometimes 10+ per second and needs to get the correct data from all of them.

This is only a part of all the difficulties the multi-player launcher has to work with :)

If I would decide to account for broadcasts (like in your 4th option) things become excessively complicated unfortunately. Therefore the only option for me is to use media notifications.

I understand you more than others :)

Honestly, I don't think this is something urgent. Fcc Launcher shows the data more or less correctly for NavRadio+, except for album arts (which depends on the order of media updates received from NavRadio+ and Hal9k) and RDS data (as @okij mentioned).

I would suggest you to complete your current task (FYT integration) and then get back to this feature request when you have time.
[Android Head-Units] okij:
@SpeedFire- Thanks for this in-depth explanation from a dev's point of view. It was a very interesting reading for me too, as I could only guess how complex the implementation of the Player widget is.

I fully agree with what you said to @KoTiX2. All the basic stuff is working, so my request is not really urgent.

Thank you both for your commitment in the software development for our head units, it's great to have skilled devs like you! :)
[Android Head-Units] jeff leggett:
Been out of the loop for a while messing around with my pixel 6 but I'm back. Downloaded one of the latest versions and it is getting close to perfect. If I remember correctly you're one of the few launchers that shows the titles of music I'm playing over bluetooth. Huge for me. Plus the amount of customization is crazy and crazy easy to do. One thing I think would be sweet is a visualizer bar. Right now I use muvis but I'd like something built in. Anyway keep up the good work and happy new year everyone.
[Android Head-Units] Big_11:
Sorry for launching this "old" Thread, but i'm new in this Launcher and would give them a Try..

I installed it and my first try, was to show Station and RDS Information at the Center Widget (maybe with Channel logos)

So my question: ist this option only available in the paid version ? or could i try it in the standard version ?

and how??

i read such a lot articles and threads, but found no really answer..

information

own an Rockchip Car-Radio (Erisin) with FMRadio App which display Station Information and RDS

Android 10

Thank you for hints...
[Android Head-Units] SpeedFire-:
If you don't see RDS data in the free version you will not get it on Premium.

In paid version you can assign your custom station names and logos to radio stations.

You can also try NavRadio+ app for example.
[Android Head-Units] Big_11:
I will See RDS Info at my Radio App but how could it be shown at FCC Launchers widget? I choosed it at tapping at this widget..
[Android Head-Units] SpeedFire-:
Seeing some data at the Radio App doesn't mean it could be transferred to third party app like Fcc Launcher.

Most device producers make it difficult or impossible to get RDS data from their devices.

Each app works in its own sandbox and doesn't share its data with other apps.

In those cases where possible I tried to get and show this data in the player widget. But such deep integrations are not always possible/successful.
[Android Head-Units] kill_one:
Thanks! Can the single widget also be blocked?
[Android Head-Units] Sathiyakumar3:
same thing here. I still havent been able to do the same.
[Android Head-Units] HatManSan:
Haven't been out for a few days. Loaded t114 yesterday. Rebooted and bingo.

It has never been this random before. Player widget gone entirely. Sat number icon gone, TPMS text off screen. The dreaded and all too frequent "M" now bigger and the player controls have shifted upwards.

View attachment 5506523

LogCAT Hopefully this Log has some good debug data in it. If you need anything else I will try to collect it for you. Cheers
[Android Head-Units] SpeedFire-:
When you restart the launcher everything returns to normal?

Can you send me your backup file please?
[Android Head-Units] SpeedFire-:
New test version - fcclauncher-3.442_test115.apk

- Route widget (with navigation arrow) is rewritten

- TPMS widget is rewritten

Please test both. I couldn't verify that both of them work correctly.
[Android Head-Units] HatManSan:
I will make a new backup tomorrow. Cheers.

Yes it does reset to normal but the player never display NavRadio data and i keep getting the letter M everytime. I have cleared system cache.
[Android Head-Units] HatManSan:
Ok t115 loaded. No Artist and Song data from NavRadio has not returned. Just made a backup for you to look at. Cheers. FCC BU
[Android Head-Units] kill_one:
Hello @SpeedFire-

I always have the same problem whatever version I install, could you take a look at the log to understand why the launcher closes when I click on the button to program a steering wheel button?

Thanks so much
[Android Head-Units] kill_one:
here is the log ...
[Android Head-Units] Armydad10:
Hey all, I just bought an Atoto A6 Karkit, new model. It will not let me give FCC access to notifications so no album covers. Is there a fix or way around this? Thx! Best launcher out there!
[Android Head-Units] electrico.clax:
@speedfire, my device is Alwinner, Why when i use tpms widget, after 3-5 Second the number of tyre pressure is gone. Like Just can not to update periodically. Please what version of tpms apk n fcc launcher apk must i install to get tpms widget stable. This is a great car launcher for me.
[Android Head-Units] _Trolk_:
Hello,

I cannot see RDS radio text on uis7862.
[Android Head-Units] rigattoni:
RDS is an system software, internal used information which is not provided to outside the radio app itself. So it is basically normal that you don´t get RDS in Fcc.... and no other launcher independent to the chipset.
[Android Head-Units] _Trolk_:
Ok, I'm asking because it worked on Allwinner and it does not display on uis7862 M300S.
[Android Head-Units] _Trolk_:
Interestingly, after installing the navradio application, the RDS text appeared from this application but it turns off when working with the FCC.
[Android Head-Units] okij:
This will be fixed when the dev of NavRadio+ @KoTiX2 has added the RDS text and the station logo to its notification, because FCC gets its data from the player's notification.

You can read about this issue starting from post #8,449 and the following 3 posts.
[Android Head-Units] _Trolk_:
Ok, thanks for the clarification