yashsingh1/xdaforums huggingface dataset:
[MTCD Software Development] KoTiX2:
Ok a new version 1.71 is coming soon:

(Already in 1.70)

Added beep on click of various functions

Added confirm. dialog to Clear List

Save and restore station list now can use "-" character and name can be very long

Added button "Copy Logo Name" in "edit" and "add station" window

Added find logo by Frequency for USA stations

Changed, PTY metadata is sent on receiving pty

(Added in 1.71)

Added Various US states logos new packages with Pi codes included in the name for automatic logo assignement: Pennsylvania,Puerto Rico,Rhode Island,South Carolina,South Dakota,Tennessee,Texas,Utah,Vermont,Virginia,Virgin Island,West Virginia,Washington,Washington DC,Winsconsin (more will come...)

Added timer to logo preview in popups

Added new functions to BACK button in settings:

1. Single click to close NR+

2. Double click to close NR+

3. Single click to exit to Launcher, LongClick to close NR+

Added support for service to start in background (It's a first try to help FCC switch player from widget)
[MTCD Software Development] Drunkenninja:
Navradio+ sometimes closes when hitting the home button, using FCC.

Hope this is fixed soon, just want it to stay open in the background.
[MTCD Software Development] okij:
Thanks, I was excited to see your announcement and that version 1.71 is already in Play Store, so I just installed and tried it.

Unfortunately 1.71 always force closes, no matter if I open it with via the FCC player widget (using today's latest version 3.385 from Play Store) or by opening it by tapping on the NavRadio+ app icon. :(

Please try if you can reproduce this issue.

If you need logs, I can take them for you - just not right now (it's dinner time with family. :))
[MTCD Software Development] KoTiX2:
Yes please send me the log whenever you can

EDIT nevermind I got it. The fix will come out asap.

Sorry about it
[MTCD Software Development] KoTiX2:
It was missing a permission for Android 9.

V1.72 is coming on playstore

EDIT: for FCC users, there are still some issues when switching between players and NavRadio but I'm making some little progresses even if they are still not noticable yet. So expect some other v1.7* coming out tomorrow. I don't guarantee that I'll making it working but I'll spend some time on it for sure ;)
[MTCD Software Development] Scopesys:
It's now working 100% reliably on my Unit (even with FM radio enabled, and both FM Radio & NavRadio+ set as FCC QuickPlayers) ---

Does not bother me if initially they start up in the Foreground, as they soon go into Background and all works well,

I think the key to getting it to work for me, was a FCC setting in the Quickplayer part of the FCC widget, to force FM radio to start up in Foreground, to fix some issue with Steering wheel controls.

Now I can sleep nights without obsessing on why it was not working :good:
[MTCD Software Development] KoTiX2:
I released version 1.73 with just a couple of fixes for service in background and notifications.

It seem to me that is working good enough to release it to public.

So I'd like to have a confirmation from beta testers that there are no major issues with it so everybody can enjoy All the new features and fixes since v1.70.
[MTCD Software Development] emre33:
notification: No Frequency (1.73). It was in previous versions (<1.73).
[MTCD Software Development] Scopesys:
[MENTION=2734955]KoTiX2[/MENTION]

Version 1.73

(1) BIG THANK you for the Back Button update

Now that navradio+ is not being re-started (by hitting back button) so often, the Issue with Turning on/off Notifications is a lot more obvious.

It looks like any changes to Display Notifications, does not take effect unit navradio+ is re-started

or

Any change to Notifications, does not take until notifications are changed again.

ie

(1) Turn ON Notification -- does not take effect

(2) Turn OFF Notificatons, and now the previous Turn ON Notifications takes effect

etc.

This has the effect of making it seem that the Turn On Notifications is Backwards, until you re-start navradio+

It's not as if you are turning them ON/ OFF that often, probably just any time NavRadio+ is re-installed,(Beta Testing) and needs to be set up, and chances are, navradio+ will close and need to be restarted after that, so the Change Notification ON/OFF then takes effect, but it is Unexpected behavior... all other changes in navradio+ take effect without a re-start. (I think)
[MTCD Software Development] okij:
I'm sorry to say that, but the issues that I reported on the FCC thread a couple of times are still there, including double sound (FM + other media player) and missing media info updates. I assume that these are caused by NavRadio+ 1.73 still crashing, which I observed.

I will be able to get a log for you in 2-3 hours, don't have time right now.
[MTCD Software Development] KoTiX2:
Are you talking about "Notification toast" or "StatusBar notifications" or metadata?

EDIT: It's important that after changing a settings, you exit the settings screen going back to NavRadio main screen to apply the new setting.

This because many settings need a restart of the app to take effect and exiting the settings screen i force the recreation of the app.

If after changing a setting you press the home button, then probably you have to restart navradio to make it take effect.
[MTCD Software Development] KoTiX2:
V1.74 is coming with this fixed
[MTCD Software Development] KoTiX2:
I haven't noticed crashes after 1.73
[MTCD Software Development] Scopesys:
Talking about the Notification Text that pops up on the screen, for a few seconds, when the radio Station is changed.

OK, now I know it needs a Restart for the Notification change to take effect, BY DESIGN, all is OK :)
[MTCD Software Development] okij:
Feedback for NavRadio+ 1.73 and 1.74

I've attached a logcat of the tests I did with NavRadio+ 1.73 (timestamp 13:43 - 13:50) and NavRadio+ 1.74 (timestamp 15:37 - 16:01), both with the latest FCC Launcher 3.385.

With both NavRadio+ versions I noticed the following issues:

It still takes about 5 seconds when switching from a different player to NavRadio+ via the FCC player widget. (Other media players don't have this issue when being controlled via the FCC player widget.)

It even takes about 5 seconds to resume playback when I press on the pause / play button of the FCC player widget. (Other media players don't have this issue when being controlled via the FCC player widget.)

It's not possible yet to switch to NavRadio+ in background, so the NavRadio+ screen is shown for about a second.

Could you please comment on these, i.e. what's the reason for this 5 seconds delay and can you fix it in NavRadio+ or does SpeedFire- have to look after this in FCC Launcher? Is it normal that NavRadio+ doesn't start in background yet (I guess so) and are you still working on this?

With version 1.73 I still had these issues:

The player widget randomly stopped updating station name, logo and RDS info.

One or two times I had to press the player widget button that I have assigned NavRadio+ to 2-3 times to switch to NavRadio+.

NavRadio+ once kept playing in background after switching to a different media player.

I guess that these have to do with the following crashes that I recorded:

06-27 13:48:12.693 4882 4882 E AndroidRuntime: FATAL EXCEPTION: main
06-27 13:48:12.693 4882 4882 E AndroidRuntime: Process: com.navimods.radio, PID: 4882
...

06-27 13:48:53.886 5533 5533 E AndroidRuntime: FATAL EXCEPTION: main
06-27 13:48:53.886 5533 5533 E AndroidRuntime: Process: com.navimods.radio, PID: 5533
...

Version 1.74 worked better for me, even though I tested it about 3x as long as 1.73. :good:

But I had the following issue with version 1.74:

After I sent the head unit to standby and woke it again, FCC started NavRadio+ again because it was the last player before standby. NavRadio+ started playing for only a second and then crashed.

This crash is here in the catlog:

06-27 15:58:02.259 11122 11122 E AndroidRuntime: FATAL EXCEPTION: main
06-27 15:58:02.259 11122 11122 E AndroidRuntime: Process: com.navimods.radio, PID: 11122
...

Thanks for your improvements in the 1.7x releases! It's definitely getting better, although some issues still need to be fixed. :)

Edit: Sorry, I just saw that attaching the logcat didn't work out when I wrote this post, so I attached it now again.
[MTCD Software Development] Scopesys:
When all the LOG says is FATAL EXCEPTION: main

Does that mean there are no Exception handlers to handle that Exception, or if there is a handler, it does not Log any information about the Exception.

If that is the case, might help to add a little more detail to the Log during exceptions ?
[MTCD Software Development] KoTiX2:
Ok I have looked some more on this and there is not an easy solution, the handling of Play/Pause commands simply won't work in the way it's made now NavRadio using mediasession buttons.

It's not just a matter of starting NavRadio service, it's more complicated than that.

So you will have to be more patience until i find time to implement a new mediabuttons receiver or i find some other way to solve it.

1. If NavRadio is running, then it sends metadatas everytime an element change so or NavRadio has crashed or the problem is on FCC side.

2. the FCC widget buttons are not handled by NavRadio so i have no idea

3. I have no idea...

They are not related to the crash..

I've seen this crash many times already with FCC/NavRadio working togheter and it happen when somehow FCC take control of everything on the headunit making other apps to do wierd stuff..

I'll try to block this crash in someway.

Generally speaking... I will try to dedicate some time to fix the FCC widget issues but I have many other things to take care that are not FCC related and i have a very limited time.

I'm going to release this v1.74 to public as it seem stable enough for standard users and FCC ones.
[MTCD Software Development] okij:
Thanks for your reply!

I'm quite sure that NavRadio has crashed, since also Ubiquity Music Widget - which I have installed for comparison - didn't get updated anymore.

Thanks a lot for your dedication on this! :)

Yes, please do so. The current version 1.74 is much better than the versions from some days ago.

And please don't take my bug reports as critizism, I just want to help you to iron out the last bugs with my reports and logs. ;)
[MTCD Software Development] Scopesys:
[MENTION=2734955]KoTiX2[/MENTION]

Question: 100% Navradio+ ( 0% FCC)

Logo Files.

It seems when I do a new install of Navradio+, making folder RadioLogos empty, and then copy my own Maryland.zip there and extract it into Maryland, NavRadio+ does not seem to be able to find the logo files.

What I have to do is remove the ones I put there manually, tell NavRadio+ to download the Maryland.zip from you, and extract it.

Then go back in and delete your Maryland.zip & Maryland folder, and then put mine there.

Then Navradio+ can see the logos.

Does this seem right to you, and if this is really how it should be working ... ? I though the user could side-load their own Logos

ie Is there something when I download from you and extract, does that put something into NavRadio+ so it knows to look in that particular folder ??
[MTCD Software Development] KoTiX2:
Which app do you use to browse for the logos?

When you hit the select logo button do you still use totalcommander or what?
[MTCD Software Development] Scopesys:
I am not talking about selecting a logo when the station is 1st created.. I appreciate that for that, I need to use Total Commander (and not Gallery), -- but do not really understand why.

I am talking about editing a station, where gallery does work

But only if I download the zip from you first, extract it.. then I can replace it with my zip & folder.

Are you telling me that if I use Total Commander, a new Install navRadio+ will find my logos (when editing stations), even if I have not downloaded yours first, and then replaced them.

If I download say 20 states zip files (and extract them) then I assume Navradio+ will look in ALL those folders for a Sid or Frequency match ?

Should Frequency match currently be working. ?

Currently I have NavRadio+ installed and set up, and working very well (even with FCC), -- after installing many versions, and reinstalling and setting up many many many times, so at the moment is very much a case of "If it ain't broke, don't fix it "
[MTCD Software Development] KoTiX2:
When you press the "select logo", android use the default file browser available in your unit.

On MTC device normally it use the Google Gallery to browse for the logos.

The Google Gallery don't know by itself that there are new files in a folder, it need somebody that tell it that there are new files. This because it's not a real file browser but consider it more a database of the links of the files andother informations .

When NavRadio extract the files from the zip, for each file it tells the Gallery that a new file has been added to the gallery database.

If you put your files manually in the unit and you want to use Gallery, you have to refresh it to make it find them (Normally cicling between folders do the trick) otherwise they will not be found.

Using TotalCommander all this is not necessary because it's a file browser, not a gallery database and what you see it's really what you have.

A slightly different story is happen If you want to be able to use the automatic assignement.

Automatic assignement look only for the files located in the folder named with same name of the zip file downloaded from the LOGO settings screen.

It won't look in all folders available because it will take forever looking for the right file but knowing the logo Nation that the user have selected, we also know the name of the zip.

So in your case, after fresh install, you just need to select the Maryland in the Nation selection, you don't need to download or extract the standard files, just select the nation and put your files in a folder /RadioLogos/Maryland

I have a small quetion for you now....

For the rest of the world i made the Logo nationality being automatically set according to the android locales (language) set in android settings. For the USA it would be en_US

Is there a way to know also the State from some other setting? so it can be automatically set too?
[MTCD Software Development] KoTiX2:
Sorry, you are right somehow i still have an old code in the AddStation window

Uhm... I'll think about it...

I'm making up the logo sets for all the US states in this format: FREQNUM_CALLSIGN_SLOGAN_SID

You are free to keep using your own package but i have something different in mind and i already have made a lot of scraping and renaming (you know it) for many states that i won't change it again.

My idea is to create a new field in the Station button beside the small freq number to show the callsign (Just for the USA and maybe Australian users)

The callsign will be assigned automatically when setting the logo (manually or automatically) copying it from the logo name.

The slogan sometimes include the name of the station, sometimes the town or the area so it's up to the user what to set in the name part.

The result will be a button like:

[pic] The Tiger

WTGE 100.70 MHz

Tnx for the tip, i'll think about it ;)
[MTCD Software Development] Scopesys:
Good -- I am not going Crazy :)

Sounds great .. I'll try it/test it when you have it ready.

(As you say, I can always go back to my Logos and its .json if I want, but your system will be more convenient for the whole USA)

Not that most over here in the USA are doing much traveling these days, with the alarming rise in new Covid-19 cases we are experiencing :(
[MTCD Software Development] dj.shauny.g:
Can not get this to install on my device whatever i try
[MTCD Software Development] Scopesys:
OK, I think we can assume "THIS" = Navradio+ but "MY DEVICE" is what, a Commodore 64, a IBM mainframe, an Abacus ??? (or even a Samsung 9 Smartphone ??)

It's a given that the APP will not install on those devices....

And what is "Whatever I try" ?? Did you try Praying and making an offering to the "Great Android Spirit" ??? (or even try Purchasing the APP )
[MTCD Software Development] armgenio:
You have the logo of the Radios of Brazil. I bought your app on Playstore, but I can not download the logos of Brazil.
[MTCD Software Development] KoTiX2:
Can you select Brazil from the Logo Nation list in logo settings?

Which radio region did you set in factory settings?
[MTCD Software Development] KoTiX2:
Version 1.75 for Testers is coming up:

Fixed Crash when switching player in FCC widget

Initial support for USA CallSign in station buttons

Updated various USA logo packages

FCC users please confirm that at least it doesn't crash anymore ;)
[MTCD Software Development] Scopesys:
Does not seem to Crash for me - ran for about 45 Minutes.

I assume the Frequency match when there is no SID is not yet implemented.

(if it is, it did not seem to work for me)

I can see the USA format.. It seems to change to USA format when the Filename is Copied.

I would very much prefer if the Old Format, or USA format was a option, rather than a forced mode when filename is copied.

Please also consider changing the USA format, or adding 3rd format.

REASON:-

In the Station Preset, to the right of the ICON, there is not much room.. Especially for a slogan of more than about 8-9 characters.

Would it not make more senses in a USA Format to have the fixed 9-10 character max of the CALLSIGN and FREQ to the right of the Logo, and then the much longer FULL 2nd line for the Slogan

ie

[ LOGO ] WBAC 120.4

Baltimore's Newest Rock & Roll Station

So, maybe a Format Option

O Non USA

O USA/AU 1

X USA/AU 2

etc as needed

Amazing Job in getting all those USA Logos and filenames !!! I know that was a LOT of WORK !!!

Here is a Video, or what it looks like with the navradio+ Logos, and resulting current USA Format.

Also, for comparison, what I created with 1.74 and my Logos, with manual editing of the Station names, ( edited to Optimize for Navradio+ Station Button, NavRadio Above Station Buttons text, and Display with FCC.)

The Automatic generation comes close to the Manually Edited and optimized version, which is pretty amazing, as the Automatic system works for every radio station in the USA !!!

VIDEO: NavRadio+ 1.75

BTW: FYI: Here in the USA, radio stations changes their programming Format and Slogans, about as often as one changes Underwear, as they try to find a format that maximizes PROFIT.

So really, the Slogan ,PTY, or even their Format based "Friendly name" can change very often, so it becomes almost non-relevant.

The Important thing that does NOT changes is the Frequency & Callsign, so in the USA, that is really the most reliable way to identify with any given Station.
[MTCD Software Development] Scopesys:
1.75 Logo saves correctly from Create Station Page :) Tnks
[MTCD Software Development] KoTiX2:
Ok, tnx for all the infos :)

I'll see what I can do for the buttons layouts
[MTCD Software Development] okij:
Thanks for this new test version. :)

After trying it for about 2 x 20 minutes, I can confirm that the fatal exceptions which I reported here are fixed, because I didn't see any in the catlogs that I took today. :good:

I also didn't observe double sound (FM + other player) anymore, so this issue seems to have been caused by the crashes. :good:

Most of the other issues that I reported are still valid. The current state is:

The FCC player widget randomly stops updating station name, logo and RDS info. (I assumed that this gets fixed when there are no more crashes, but there must be another reason for it, either in NavRadio+ or in FCC Launcher.)

It still happens that I have to press the FCC player widget button more than one time to switch to NavRadio+. (Also here I assumed that this gets fixed when there are no more crashes, but there must be another reason for it.)

It still happens that after waking the head unit from standby or fully restarting the head unit, FCC starts NavRadio+ again because it was the last player before standby/reboot (as it is supposed to do), but stops playing after about a second. (Again I assumed that this gets fixed when there are no more crashes, but there must be another reason for it.)

It still takes about 5 seconds when switching from a different player to NavRadio+ via the FCC player widget. (Other media players don't have this issue when being controlled via the FCC player widget.)

It even takes about 5 seconds to resume playback when I press on the pause / play button of the FCC player widget. (Other media players don't have this issue when being controlled via the FCC player widget.)

It's not possible yet to switch to NavRadio+ in background, so the NavRadio+ screen is shown for about a second.

I have attached two logcats from this morning for your and [MENTION=4292729]SpeedFire-[/MENTION]'s evaluation. The second catlog starts after fully restarting the unit, after which issue #3 happened.

P.S.: I used NavRadio+ 1.75 and FCC Launcher 3.390 for doing these tests today.
[MTCD Software Development] dape16:
I understand that there are other priorities right now, but do you have any plans to integrate NavRadio+ with the mediaplayer widget in Waze? It's very convenient to control music with the widget when navigating.
[MTCD Software Development] KoTiX2:
Uhm.. i didn't even know that Waze have a mediaplayer.

Tnx for the suggestion, I write it down in the to-do list.
[MTCD Software Development] dape16:
Thanks for your answer! Sounds good. Waze supports about 20 mediaplayers right now.

BTW, version 1.75 in Play Store is much more stable when using FCC. Thanks for the update.
[MTCD Software Development] dj.shauny.g:
My device is a PX5

Aa for "trying" i have deleted my original radio app to try and install this and nothing. I have altered setting in the factory's settings and nothing. Whatever i try and do to get this app onto my device it says "app not installed" it must not be compatible. I would purchase the app, money is not the issue here.
[MTCD Software Development] AdekP:
@ KoTiX2

Everything has been great since several versions back. Thank you.

I have a small request that in the notification options you can add the option of displaying in launchers also the name of the radio channel without the frequency, which navradio automatically adds before the channel name. The frequency is not important for everyone, and since a person reads from left to right, then if we want to see what channel is currently playing, we first see the frequency ;)
[MTCD Software Development] KoTiX2:
Are you sure that you have an MTC device?

Can you send me a picture of the system information screen showing the MCU number?
[MTCD Software Development] Scopesys:
[MENTION=2734955]KoTiX2[/MENTION]

Are you doing something intentionally in NavRadio+ to prevent a user from Exporting the APP, and then being able to re-install that exported version, (if it is not the current version on Playstore.) ?

Every other APP I have tried to do this with, purchased or free, it has worked, but it would seem that NavRadio+ cannot be re-installed from an exported backup of a prior version. :(

I believe that most Apps allow this, and then once installed, will check with Playstore, to see if it is purchased, and if so, will turn on the Purchased features.
[MTCD Software Development] KoTiX2:
Nope, I haven't added anything like that.
[MTCD Software Development] dj.shauny.g:
Unsure how to add pictures on here so uploaded to dropbox, here is the link....

https://www.dropbox.com/s/pxujcog5lf1qpj7/20200702_063913.jpg?dl=0
[MTCD Software Development] KoTiX2:
You have an MTC device that is perfectly compatible with NavRadio+ but you are running android 6.0 and it could be the problem.

I set the compatibilty untill android 6 but i have never tested it.

I suggest you to upgrade your unit to androi 8 at least or even 9, there are tons of threads about firmware upgrade, you can use a the sdcard method or the USB method with Hal9k Mod Installer.

It's an easy step to have a newer headunit more compatible with today software.