[Android Head-Units] okij:
@SpeedFire- Thanks a lot for your latest version 3.501 which runs very stable and without any issues on my head unit. :)

There's just one thing left that's not working well yet and bugging me: Even with the latest NavRadio+ v2.28 from @KoTiX2's beta channel on Play Store the FCC Player widget doesn't stably update the incoming station and RDS text updates from the NavRadio+ notification.

Today I've recorded a video and Logcat which I already sent to @KoTiX2, but currently we're a bit out of clue if this misfunction is something that can be fixed in NavRadio+ or needs to be fixed in FCC. Therefore I'm now posting the video, my comments about it and the Logcat here too for you to have a look.

I hope that you can receive RDS text in Russia, so hopefully you can reproduce the issues on one of your devices (mine is a MTCE PX6), which should help you to find the root cause. Please use the latest NavRadio+ v2.28 from the beta channel, enable the usage of notifications/metadata in the settings (if not already enabled) and set Field 1 = RDS text and Field 2 = Station name. This is important, so Artist = Station name and Title = RDS text, which is the same as e.g. also DAB-Z uses the text fields.

Here are my findings that I posted to @KoTiX2 today:

"The good thing is that when the RDS text is first received after switching to NavRadio+ or after switching stations, now in about 50% of the time it is then also immediately shown in the FCC Player widget. This is better than on v2.27, because then it always needed the second RDS update until the RDS text was displayed in the Player widget.

The bad thing is that it still doesn't work reliably and that furthermore with v2.28 now other unexpected things happen that didn't happen before, like the Player widget not updating anymore (but only when NavRadio+ is active, as my other players still are shown fine in the Player widget). I took a video to demonstrate some of this, with often showing the NavRadio+ notification before showing the result in the Player widget:

At 00:11 the RDS text is correctly shown in Player widget after the first RDS update came in (= expected behavour).

At 00:24 the RDS text is correctly shown in Player widget after the first RDS update came in (= expected behavour).

At 00:43 the RDS text is not shown in the Player after the first RDS update came in (= buggy).

At 01:01 the RDS text is not shown in the Player after the first RDS update came in (= buggy).

At 01:40 the RDS text is not shown in the Player after the first RDS update came in (= buggy).

At 01:44 the RDS text is then shortly shown when switching to a different station (= this is very interesting, as it shows that the RDS text is processed too late by the FCC Player widget).

At 02:01 the RDS text is not shown in the Player after the first RDS update came in (= buggy).

From 02:08 to 02:13 the Station name etc. is not updated anymore in the Player widget after switching stations ...

at 02:14 ... although the notification is correctly updated (= somehow the Player widget got stuck displaying any infos from the NavRadio+ notifications).

From 02:20 to 02:44 it's till the same behaviour. AFAIR I got it working again by manually restarting the FCC Launcher, but some time later it happened again.

I also attached a Logcat from this morning in case you want to take a look at it.

Especially the oddity that happened at 01:44 and the not updating Player widget that can be seen from 02:08 to 02:44 make me think that something still needs to be fixed in FCC. On the other hand, my other players work 100% of the time correctly with the FCC player widget, so it could well be that something about the notification and metadata is still not compatible with the way FCC needs or interprets it."

@KoTiX2 won't have time to further look into this until Monday. He also wrote to me that NavRadio+ is still not acting as a mediaplayer (i.e. there are no Play/Pause and Next/Prev buttons in the notification yet), so maybe there is still something that needs to be fixed by him.

From my testings I think that the reasons for the described bugs could be:

NavRadio+ is using a notification and sending metadata at the same time. I'm not sure if this is what you asked for, so maybe those two interfere with each other because the Player widget tries to react to both of them. Maybe this also leads to the Player widget freezing = not being updated anymore.

Maybe it's just a matter of timing. I have the feeling that the Player widget reacts to the first notification update after e.g. switching stations, but that if there's another update very soon after it (e.g. by an incoming RDS text), this second update gets ignored.

So please take a look, I hope that you find something that needs to be fixed in either FCC or NavRadio+.🤞Please let me know if you need any more infos or testing.