[Android Head-Units] Scopesys:
Well, I said it was working well -- I didn't say it was Perfect ;)

Quote:

Originally Posted by okij

2. 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.

DO not get that.. If I am displaying the Player widget, as in my Video, and it is displaying the current LOGO & RDS for the selected station, if I use the Steering wheel button to go forwards or backwards between stations, it works fine. There is a delay, after a new station is selected in the RDS Info.

You are probably getting the Station name through RDS (in Europe), Here in the USA, the RDS Station name is often not the station name, so I have my Station names manually entered, a benefit being, they show up the instant the station is selected.

3. 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).

Yes, selecting navradio+ the first time to switch to it (in my case its the 4th player) sometimes does not select correctly.

Also, if the 4th player is another Player, selecting Navradio+ sometimes takes a few presses to get it to lock in as the 4th player, but once it does, it is fine.

5. 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.

Yes, I have just learnt to be patient and wait. It could be better, but it is not a deal breaker.

6. 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.)

Again, yes.. I get that as well, but currently accept it.

My may area of concentration on Navradio+ has been helping the developer sort out the RDS issues that are peculiar to the USA, as well as the USA radio stations sending content information in the Station name field, that screws up identifying the Station Name. - as well as making a decent LOGO/ARTWORK set for USA Maryland.

That as the main objective of the Video to show the result of a SCAN and Station name editing, and then how it displayed in FCC.

I did not want to confuse that with the FCC integration issues, so FULL DISCLOSURE, I did EDIT OUT those pieces of the Video, where FCC & navradio+ were not updating as expected.

So there are CUT in the video, which I did not really try to hide, as I made the Audio fade in/out on those cuts :)

Both developers have been very quite this past week. maybe they are taking a well earned break - maybe they are too busy working on fixes and improvements..

Time will tell ... Patience is a Virtue :fingers-crossed: