yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

You are already probably looking into this : navRadio+ comes with two NavRadio+ widgets.

These seem to work reliably, even when placed on a FCC Screen, and used there -- so that seems to indicate that navRadio+ "CAN" be controlled reliably by a Widget.

The $64,000 questions would seem to be

(1) Are those NavRadio+ widget control "Android Standard"

(2) IF it is not standard, does navradio+ change to be standard, or does FCC make a special case, and control NavRadio+ with the same methods as navradio+'s current widgets. (whatever that is)

Also,

It seem that if BOTH navradio+ and the default app are used at the same time, then there is an issue where navradio+ loosed control, and starts to display incorrect screens.

But while navradio+ might be in some "locked up" state, the Default Radio seems able to take back control and run correctly. (without re-boots etc.. it just takes over and the radio responds correctly)

If the Default radio App can regain control, then maybe Navradio+ should be able to, or be made able to, do the same.

There seem to be no technical reason why both apps should not be able to co-exist, and the user switch between them (if that's what they want), without just ONE of the Apps locking up,

It's similar to having two USB Mp3 players. If one runs and accesses the Mp3s on that USB stick, it should not prevent another Mp3 payer from being selected, and be expected to work.

There is no question of only being able to have ONE Mp3 player installed on the head unit, because more than one with make them CRASH or Lock-Up each other.

I get the impression from some of your comments, that this may be what you are currently looking into. ?
[Android Head-Units] SpeedFire-:
FCC 3.365 v27:

- Another attempt to integrate with NavRadio+. It doesn't work perfectly but it works better.

Please note that the way to control all players using MediaSession interface has changed so please check that this version works fine with all your other external players.
[Android Head-Units] okij:
Thanks a lot for the new test version. :)

I just tested it for some minutes during my lunch break and can confirm that it works better than v27:

(+) Changing the NavRadio+ stations now works fine with the player widget's previous/next buttons.

(+) I've also tried the other two other players that I use regularly (DAB-Z and GoneMAD Music Player) and changing stations respectively tracks works fine as before, so the new way to control the players using MediaSession interface seems to be compatible with those players.

Those things still didn't work well in v27:

(-) When switching from a different player to NavRadio+, it takes a couple of seconds before the playback starts. This was working instantly with the stock radio app, although I assume that the delay I experience now is caused by the time that NavRadio+ needs to load!? It would be fine if this delay could be minimized though.

(-) The NavRadio+ screen is shown for a second when switching from a different player to NavRadio+. It would be great if this could happen in background, similar to the way that FCC starts DAB-Z in background.

(-) When switching from NavRadio+ to a different player, it still happens that the FM sound keeps playing along with the other player's sound, i.e. the audio focus sometimes isn't properly switched.

(-) During my short test it happened that I still could switch the NavRadio+ stations, but the display of the player widget (station name, logo and RDS info) didn't update anymore.

That's my feedback after doing a short test, maybe [MENTION=9325785]Scopesys[/MENTION] can do some more detailled testing.

So it's definitely an improvement over v26, although some things still need to be fixed and improved. :good:

Also [MENTION=2734955]KoTiX2[/MENTION] for information.

Please keep up the great work, guys!

[MENTION=4292729]SpeedFire-[/MENTION]: When you released v26, I asked why the apk size increased from 52 to 71 MBytes, but didn't get a response yet. In v27, the apk size still is at 71 MBytes, so I would like to ask this question again.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Thanks...

Please could you give a very brief description of what is changing here, especially with respect to NavRadio+, to get the two Apps to work together.

(a) Is navradio+ getting changed to make it more "Standard" Android Widget compatible.

(b) If FCC being changed to make it more "Standard" Android Widget compatible.

or a combination of both. ?

Your comment "Please note that the way to control all players using MediaSession interface has changed" would suggest that FCC is changing in some way to this end.

My reason for asking is that those of us testing and trying to see if all this work, are essentially testing TWO Apps at the same time -- FCC & NavRadio+, and potentially BOTH Apps are being updated by their developers, at the same time, or at different times.

It would help when testing to know if FCC is being changed to better Interface to Navradio+ in an Android Standardized way, or Navradio+ is being changed to be more Android WIdget standardized.
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Forgetting about NavRadio+, this new version of FCC seems to have introduced a new Bug, (nothing to do with NavRadio+ )

(a) It does seem to be more stable when controlling navradio+

but

(b) It has introduced an issue where if the Player is changed to Default RADIO, and say the Station is then changed by the Steering wheel, on the 2nd change, FCC jumps back t the former player. If after switching to Radio, one enters Radio full screen and does a operation like change station, then back in FCC, then using the steering wheel button does NOT make FCC revert back to the previous player.

see Video, that shows

(a) navradio+ working reasonably well,(once it starts to run correctly) unless one causes the Default radio to run. !!

(b) MORE IMPORTANTLY, new Bug introduced, where FCC switches Player when it should not. (caused by control of "current ??" player)

VIDEO: -- FCC V27 -New Bug - Reverts back to previous player

BTW: I make these recordings, and typically do not edit them, or even watch them till I have uploaded them with a post... then I watch them for the 1st time after reading the post, just like you would - then occasionally I will go back and change the text in the post
[Android Head-Units] rigattoni:
[MENTION=4292729]SpeedFire-[/MENTION]

Sorry to say but I found another issue in v26.

(Didn´t try the v27, because NavRadio+ is not of any interest for me , because it´s not working on my units. So I did not update my unit to it.)

Workflow:

Choose any not-FCC-widget and place it somewhere on the screen

Long press on widget and choose icon

Put in a new name for it

Press OK button

Let FCC restart

Observed behavior:

Icon and name are not overtaken after restart of FCC.

The behavior is the same even if you just change icon or name.

Expected behavior:

Icon and name are overtaken as changed in settings.
[Android Head-Units] SpeedFire-:
I can't confirm this bug. For me it works.
[Android Head-Units] SpeedFire-:
FCC 3.365 v28:

- Small fixes with NavRadio integration
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Please can you tell us What Fixes -- what should we be looking at that had changed -- got improved / fixed.

Currently, there are many issues, some of which are very unstable / intermittent. Its like a HAYSTACK of things that do not work correctly.

When you talk about "some small fixes" that's like a NEEDLE.

So now we are looking for a NEEDLE in a HAYSTACK, and

we don't eve know what the needle looks like

. :confused:

This makes it difficult, if not impossible, to report back on whatever changes you made, are actually doing better or worse.

I GREATLY appreciate all the work you put into FCC, and all the time you spend on fixing and improving it .. must be MANY hours for each update.

Maybe you could spend a few minutes of that time, passing on to those who are beta testing, a more precise description of what has been changed, why, and what we should be looking at to report back on those specific changes :)

------------

I spent 3 hours testing v28 this evening, and concluded it was not working as well as v27. major issues with updating navradio+ artwork, intermittent update.

So I went back to V27 , only to find that the issue I had found in v28, was still back in v27 -- but I had not noticed it there when I was running v27.

Before I had every Radio station with a logo, so this bug did not show up.

The FLICKERING in V28 every approx 10 seconds IS new to V28, no matter what player, and went away when I went back to V27

So it now feels like 3 hours wasted :(

Video - NOTE - the NavRadio+ artwork update issue was still back in v27
[Android Head-Units] bajoseph04:
Please consider option to disable split screen as a feature request and not a complaint. Thanks
[Android Head-Units] SpeedFire-:
Thank you for testing!

This is not always possible. Sometimes (like in this case) I try to improve something inside (intents, communication interfaces) to reach better stability. Therefore there are no visible changes for user which can be described. Often I don't know for sure if these stability changes are really positive or not. So it's as hard to find out the final results for me as for you. That's why a feedback from the testers is really important here.

This is interesting...
[Android Head-Units] SpeedFire-:
Split screen feature doesn't have any side effects. Especially after Launcher restarts are fixed now.

You probably want something else to be fixed (thinking this is caused by split screen). So please show these bugs.
[Android Head-Units] okij:
I still had launcher restarts some days ago (with the version had the restart fixes in changelog), that's why I also asked for this.

However, with v27 I didn't have launcher restarts yet. I will keep a eye on it and try to get a logcat if I see a restart again.

I will skip v28 for the reasons that [MENTION=9325785]Scopesys[/MENTION] posted.
[Android Head-Units] SpeedFire-:
FCC 3.365 v29:

- This version is tested with the Beta NavRadio+ (which is not publicly available yet)

- Standard FM Radio app is killed when you change to NavRadio

- NavRadio is killed when you change to Standard FM Radio (so both apps can work reliably with FCC widget)

- Better (I hope) processing of artist/track data from notifications. For me it works better when changing between 3 test players: Standard FM, AIMP and NavRadio
[Android Head-Units] jrobbom5:
If it's up for the vote, I vote for the split screen feature, I think it's a fantastic idea.
[Android Head-Units] bajoseph04:
Yep.. it's a fantastic idea agree. But that shouldn't affect the overall performance of the launcher since most people won't be using it or the feature won't work on few units. These guys shouldn't sacrifice the performance of the launcher (assuming most headunits have 2gb RAM and mediocre processors) because of a cosmetic feature like split screen that is not going to be of much use on a car head unit. That was the major concern of most of us.

Now that [MENTION=1633144]speedfire[/MENTION] has confirmed that the split screen has nothing to do with the performance of the launcher or the launcher restart issues are not related to the split screen, I have no concerns with the further improvement of this feature. But if at all this will impact the the launcher in a minimal way due to the extra coding, few guys request for a switch to turn off this feature. As simple as that. For those who enjoy the split screen, we have no regret.
[Android Head-Units] okij:
Feedback for FCC 3.365 v29 with NavRadio+ 1.60

Thanks for the new test version. :)

First a short feedback for v28, which nevertheless I tested for some minutes before I read about v29 and installed it:

With v28 I didn't experience the problems that [MENTION=9325785]Scopesys[/MENTION] described, there was no flickering and such. For me it worked the same or a bit better than v27, for which I gave you my feedback in post #6274. I don't know what's different on [MENTION=9325785]Scopesys[/MENTION]'s setup, maybe he didn't use the latest 1.5.9 beta version of NavRadio+?

Now my feedback for v29 after testing it with the latest version 1.60 of NavRadio+ 1.60 for some minutes:

(+) When switching from NavRadio+ to a different player, now the FM sound seems to be stopped reliably, so there is no double sound anymore.

(-) Edit: The player widget still randomly stops updating station name, logo and RDS info, so even when changing stations, the widget display is stuck until changing back and forth between different players and/or fully closing NavRadio+ before starting it again.

(-) Quite often I have to press the player widget button that I have assigned NavRadio+ to 2-3 times to switch to NavRadio+. This should work with only one press, like it's correctly working with the other players (DAB-Z and GoneMAD Music Player in my case).

(-) When switching to DAB-Z via the player widget, now the DAB-Z app stays open and doesn't go back to home screen automatically after switching. I'm not sure if this bug was already introduced inn v27, because you changed the way that the playing apps are accessed in v27, but it needs to be fixed.

(-) When switching from a different player to NavRadio+, it takes about 6 seconds before even the NavRadio+ screen is shown and shortly after this the playback starts. IMHO there is something wrong, this delay cannot be caused by the time that NavRadio+ needs to load (it's an app of just 2-3 MBytes in size). [MENTION=2734955]KoTiX2[/MENTION]: Please also have a look at this, i.e. do some test with FCC v29, to see what might be wrong and how it can be improved. Edit: I now did some tests with NavRadio+'s own widget and (when pressing on it), NavRadio+ starts instantly. So this 6 second long delay is something that needs to be fixed on FCC's side or in the way that NavRadio+ is controlled respectively activated.

(-) The NavRadio+ screen is shown for about a second when switching from a different player to NavRadio+. It would be great if this could happen in background, similar to the way that FCC starts DAB-Z in background. (Side note: This currently doesn't work reliably in DAB-Z too, please see #4 above, and might be caused by the way that FCC accesses the player apps.)

So in summary, it's getting better with each version of FCC Launcher and NavRadio+, but still some issues are to be fixed. :)

Edit: Also thanks for reducing the apk size to ~50 MBytes again!
[Android Head-Units] nimslo:
[MENTION=4292729]SpeedFire-[/MENTION]

1.)

I recently (again) pointed out, that the "Route Widget" does not work correctly in connection with Google Maps (last tested with Play Store version 3.362 as well as Alpha/Beta version 3.365.v24). Instead of a changing direction arrow, only the logo (triangular arrowhead) is displayed on my Android 6.0.1 device. Pictures in post #6237. You may have no intention of working on this issue, nevertheless, in any case, it would be nice if I could get a response.

2.)

I want to replace the GPS-Speedo widget, which responds too slowly in my opinion, by the OBD widget.

a.)

Unfortunately with the OBD-Speedo the unit (km/h) is shown in the same line and size as the value. Is it possible to put the unit (km/h) in small letters on the second line (as with the GPS-Speedo) or, if not possible, to switch off displaying the unit?

b.)

It would be great if you could introduce an editable multiplication factor (e.g. x 1.05) for the OBD-Speedo to enable individual fine-tuning of the displayed value. However, the value should still be displayed as a rounded integer only, without decimals.

c.)

Another note on a bug in the OBD widget (3.362, I have not tried this with betas): It does not work if the widget setup window is closed by pressing "OK". Apparently this clears the ticks set one level earlier for the possible OBD values to be read out. Then displayed are no values or just the frozen value that was current at the time the OK button was pressed. However, if you do not close the setup window by the "OK" specified by the app, but pressing ESC/Back, the widget works.

Please, don't let me feel being ignored, any response would be highly appreciated.:crying:
[Android Head-Units] rigattoni:
Just tried it once again and here is a video: https://drive.google.com/file/d/1ICEwVvXVtOmK1PFStgQlEzKTK6Y7uq8G/view?usp=sharing
[Android Head-Units] Scopesys:
GREAT News,,, hopefully the beta NavRadio+ will be available soon to try it with.

I like the KILLING !!!!:good: and the expected improvement in switching between Quickplayers (which has been an issue for a long time)

Will test v29 this evening after work :)
[Android Head-Units] liamstears:
@ SpeedFire-

First quickly I just wanted to say thank you for the continued support in trying to get NavRadio+ up and working properly, I really am looking forward to getting this flawless.

Secondly I'm after some help with the TPMS integration. I have 2 issues.

First one is there seems to be no way of stopping an alert of a low pressure tyre? At the moment I am having to correct the tyre pressure and then restart FCC to get the sound/warning to stop. Can this be looked into? It would be nice to have a feature to either snooze the alarm for a time period, or snooze till fixed or stop it completely or something?

Second problem is that on my headunit if I do a full reboot both FCC and the TPMS widget load correctly, however if I just wake the unit from sleep as you would normally day to day the TPMS widget refuses to load. I have to go into the settings of my device and go into apps/tpms widget and kill it. Then I can go back to FCC, click the widget and it will load again. This seconds one seems really odd to me and I didn't face this problem on my old headunit so not to sure exactly what's causing it or how to fix it or if there is a workaround? What would cause it not to load the pressures when waking from sleep? The process seems to be running still? Or maybe I need to kill the process and wake it when my device resumes from sleep? This would seem an easy workaround using Tasker secondary app and the built in software startup loading of my headunit? Really appreciate your input on this and any information you can give

Thanks again @ SpeedFire- FCC is amazing!
[Android Head-Units] tonimontoia:
good evening, who can help me with each ignition starts automatically tomtom nds, I have tried everything even applications that hibernates nothing I can't thanks
[Android Head-Units] SpeedFire-:
First issue - tap on the warning (not swipe it) and the warning will be snoozed for 30 minutes.

Second issue - this is a really odd issue. I don't even know why this may happen. Tasker workaround seems like a good option for now.
[Android Head-Units] liamstears:
Thanks for the speedy response

I'll try the tasker workaround see if I can get it to work and let you know

When you say tap the warning do you mean the pop up or the notification? Could you maybe add a button in the TPMS screen itself to do this also?

Also even after correcting the pressure the alarm was still going off, so if this works for 30minutes will it sound again after? Because at the moment if I correct it I still get the sound and notification...
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

Works GREAT ... ( with lastest available navradio+)

Switching between any QUickplayers is greatly improved.

navRadio+ works well ( except the PLAY button in the FCC Player widget)

Switching between default Radio & navRadio+ is very much better.

No more FCC reloads

No more navradio+ reloads

I don't think this combination is Killing each other (yet), so when one does switch, it seems one had to enter the APP, to gain Re-Focus ? But that's not a big deal, and maybe will not be needed when they Kill each other ?

VIDEO: FCC working well with NavRadio+
[Android Head-Units] SpeedFire-:
The latest version under the name FCC 3.370 is uploaded to the beta channel in Play Store
[Android Head-Units] okij:
[MENTION=4292729]SpeedFire-[/MENTION]: Additionally to my feedback for v29 from yesterday there is another new issue:

7. (-) After ending a phonecall, the DAB-Z screen is shown instead of the FCC homescreen. (Of course before making or receiving the call, DAB-Z was not in full-screen mode, but the FCC homescreen was shown.) This could be related to issue #4 (see above).

Please have a look into this issue too. :)

---------- Post added at 12:01 PM ---------- Previous post was at 11:59 AM ----------

Thanks! :)

What's the changelog? Did you fix some of the issues that I've reported yesterday?
[Android Head-Units] SpeedFire-:
Not yet
[Android Head-Units] Scopesys:
[MENTION=4292729]SpeedFire-[/MENTION]

QUick Video, showing FCC widgets & NavRadio+ widgets on the same page.

Comparison of their operation & control. Working VERY WELL :)

Comparing the widgets does raise a Request

The NavRadio+ widget is able to get & display the Station Genre. ie News, Weather, Educational, culture, Music, or None etc etc

This is typically sent by the Station often, so is one of the 1st pieces of RDS info available. It is also Informative.

Would it be possible for the Player Widget to be able to display this Information, maybe as an optional Overlay on the Artwork ?

Ideally at the Top Center, on a Contrasting background, ( Top Center would work for both Circular and Square Artwork)

VIDEO: FFC & NavRadio+ widget test & comparison (+ Request)
[Android Head-Units] roydestroy:
Hello, is there a way to display RDS info on the Artist and song label of the FCC widget?
[Android Head-Units] Scopesys:
Doesn't it t already do that with NavRadio+

As far as the Default Radio Player is concerned, I don't think most of them, even if they can display RDS information in their APP, make it available to other Apps/Widgets

I assumed that was what the "+" is Navradio+ is all about -- Its far better than the default AM/FM radio

Here in the USA, even if the Station has R(B)DS equipment, what they choose to send out on it varies enormously..

Some only send out their Station name, other send out a whole stream of updating information, Song Playing, name of radio show etc etc.

It's totally inconsistent between Stations and seems to be whatever they feel like doing (or NOT doing).

If some new song comes on I do not know, I have a Google Song Search button on my Screen, which will , in most cases, Identify the Song & Artist, and then will even take "My Passengerr" to the Text Lyrics !! -- NO - I do NOT read they Lyrics while driving !!!
[Android Head-Units] roydestroy:
Well I do not know if NavRadio+ does this because I do not have the beta versions of either FCC or NavRadio+ in order to see this. Still waiting for a stable version. Also, I never implied anything in my question regarding NavRadio+ so I do not understand where you are basing this comment saying "Doesn't it already do it with NavRadio+".
[Android Head-Units] Scopesys:
OK, so RDS from what source are you talking about, if not the radio ??

I was giving navradio+ as an EXAMPLE of a APP that had RDS, and whose RDS information, FCC is able to display in the Player Widget, in the Song & Artist fields of the FCC Player widget
[Android Head-Units] roydestroy:
I WAS talking about the radio. But not NavRadio. I was talking about the stock Radio app. Anyway, as far as I understand this can only be done through NavRadio so I'll have to wait till problems are fixed. Thanks anyway.