yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] spludgey:
Can you change the font size in the widget to something more reasonable, in the full version? If so, I'll buy it.
[FYT Android Head Units] vonny571:
I haven't had a lot of time to mess with it, but so far it is working well. Thanks for the support.
[FYT Android Head Units] honeker64@gmail.com:
it turns out pretty slowly step by step .... after turning on why is it like looking for a dream? sometimes I only have a voice when I start the factory radio and then the navradio
[FYT Android Head Units] KoTiX2:
What FYT model do you have?

How much RAM?
[FYT Android Head Units] honeker64@gmail.com:
Atoto s8 2gen 3G+32G
[FYT Android Head Units] DrumVlado:
Hey, how do you stop the radio? I use FCC launcher at the moment, and the media widget is very buggy, but can I stop the radio in the NavRadio+ app itself?
[FYT Android Head Units] Closerm6b:
Only tap the station that i listen for
[FYT Android Head Units] surfer63:
Yes, tap the widget. The app will open. Tap the "Back" key.

Unfortunately there is no Pause/Play and/or Stop button in the widget and neither in the app itself.

On some of the commercial stations when the commercials start, I would like to "Pause" and start again after x minutes.

But pressing back to exit (widget tap, back tap) and tap the icon again after a few minutes are the same number of actions as pause/play (widget one tap extra), so it actually doesn't make a difference. It only comes down to "user experience".
[FYT Android Head Units] KoTiX2:
Ok. You need to raise up the radio sensitivity in NavRadio settings/radio.

Set it about 40-50% of the slider.

If it still doesn't work you can always disable the AFseek in settings/radio but it means that you have a very bad reception on your unit.
[FYT Android Head Units] KoTiX2:
Actually there is a PAUSE function that need to be enabled in settings/general "Single click in the middle of the screen to Pause the radio player" but it work only with NavRadio open in foreground.
[FYT Android Head Units] surfer63:
I added a "Q29: My radio reception is bad. AF (Alternative Frequency) seeking in the NavRadio app doesn't finish or continuously restarts." to the Q&A section of "General FYT based Spreadtrum uis7862(s) (unisoc ums512) & uis8581a (sc9863) - Q&A, Mods, tips, firmware" for all those users that do not use the 12V power on their antenna and have a bad signal.

But it might be good to add that as well to post #2 Some Tips and Guides under AF or somewhere else. You will get this question many times again ;)
[FYT Android Head Units] CitricC:
I have an issue in combination with using CarPlay on my unit and the Sophe One+ (Bluetooth device + app) on my phone. The situation is like that.

I start the Navradio+ app (proxy installed), followed by the CarPlay app. Using / through CarPlay I use google maps and in the background the radio (on the unit) is running. The moment I receive a notification from my phone / the Sophe app (alert is audible through the speakers, Sophe app is always running automatically), the navradio playback is gone. I have to reopen the Navradio app and it’s working again.

*just bought the app to support your awesome work!
[FYT Android Head Units] heavyhms:
Actually I have same problem (a couple of days ago there are no problems) after the latest upgrade of tomtom go and latest version of Navradio+ (radioproxy 1.2): radio playback does not fade during tomtom notification, but stops completely and need do be resumed manually. This problem does not occurs with Google maps navigation (audio correctly fade and resume after notification). Today I'll test if the same issue is present also with Dab-Z 2.x to verify if is a Tomtom specific issue or is related to tomtom-Navradio+ interaction.

Tomtom go and maps are installed on radio, not used via carplay in my case.
[FYT Android Head Units] heavyhms:
Update after some test:

There seems to be a problem interacting with TomTomGo.

When NavRadio+(0.3.11 with RadioProxy 1.2) audio is playing, the latest version of TomTomtGo (3.6.235) fails to fade the radio and overlay alerts (no audio is heard from the navigator). If you manually force playback, once the warning is over, navradio cannot automatically resume playback unless you reopen the application. The audio fade of Tomtom notifications works perfectly with MX player and Dab-Z 2.0, just as the interaction between NavRadio+ and Google maps (navigation) and Sygic Navigator works perfectly.

@KoTiX2 if you need more info you can send me a PM in italian (my english is not exactly "fluent")
[FYT Android Head Units] 3PI:
That audio problem that you mention, not only happens with the tomtomGO application, it also happens with all types of third-party applications, such as Waze, radardroid, etc. If NavRadio+(0.3.11 with RadioProxy 1.2) is active and running, the audio from other applications is muted. If you turn off "NavRadio+", then they do appear. It's as if NavRadio+ app takes over the audio.

Curiously, with GoogleMaps, the audio, and warnings work well. Obviously, I have the GPS audio mix configured correctly. I have done many tests

It seems that it is not a problem that only affects tomtomGo. But also to other applications that need to sound mixed with NavRadio+
[FYT Android Head Units] heavyhms:
except also Sygic Navigator (this one works well with Navradio+, tested with last today update of Sygic)
[FYT Android Head Units] Droyka:
Hey KoTiX2, I have this function enabled and the button I have for play/pause works for pausing, but not for playing again. I have to use the touchscreen again to continue playing. Do you think you can fix this?
[FYT Android Head Units] Moldeb:
I know it's off topic and you don't like it - but I'm still grateful you've mentioned this as it solves various issues I had with PiP launchers. I'm now back on good old Nova as well.

Get better soon!

And back on topic: Thanks much @KoTiX2 for making AF work! Actually I'm now looking at NavRadio+ and will probably buy it. Had not used it before (just used DAB or streams given the original FM radio is so bad...).

Edit: Have bought it now :)
[FYT Android Head Units] KoTiX2:
I'm aware of these issues, all them are related to "audio focus" problem that on almost on all these Chinese units but particularly on FYT devices is handled half by system service and half by the app.

If you have noted on my recent changelogs i'm struggling trying to fix on the problem. If I fix the audio switch with radars/navy apps then it brake up the audio focus on boot.

A while ago I wrote that if you enable the test mode it will enable a special patch for the radars issue, maybe it can fix the tomtom problem too.

So please guys try to enable "test mode" going to settings/about NR, double click on the NR icon until "TestMODE" show up.

Please report me back if it solve something.
[FYT Android Head Units] KoTiX2:
When I added the play/pause function I couldn't get it to work.

When NavRadio is not playing, it stop listening to the buttons.

Honestly I don't know if I can fix this...
[FYT Android Head Units] Droyka:
Haha okay ;p

Thanks for trying nonetheless!
[FYT Android Head Units] andi_n:
Hello,

at first I would like to say thank you for your great work.

Last Sunday I did a first short test, drove about 100 km, the AF is working quit good.

And at the moment it looks like the app has stopped scanning all stations after start all times.

But Saturday / Sunday I will drive from Croatia to Amsterdam for a show.

This will be a real praxis test through different countries.

I will report.

In the older versions the app didn't changed the station names when found a new station on a frequenz which have been already in the list.

Is this still so?

If is possible that the stations on the favorite list will be not deleted upon deletion the station list?

After a while, driving through 2 - 3 countries the station list endless.

Cheers
[FYT Android Head Units] KoTiX2:
The older version (3.10) was buggy. The 3.11 may still have something not perfect but should work much better.

I recommend you to save your station list before doing anything from "Manage lists" or make a backup of the settings.

If you have the "Merge" frequencies function anabled it should do all the work for you keeping the station name and logo. If the reception is good any new station found will have an ID assigned and if this station already exist, the new frequency will be added to its AF list, keeping the station name.

Please let me know how it will be your trip with the new AF ;)
[FYT Android Head Units] heavyhms:
Hi, test mode does not solve issue with TomTom
[FYT Android Head Units] giobengi:
However, at the moment the AF function is annoying or rather it should be improved because if a stored station does not have a good signal, navradio starts searching for the alternative frequency but never stops searching and does not even return to the original frequency if it does not find it. This search should be much faster.

I have updated with the latest version of navradio and with radio proxi 1.2, I also have good reception with the antenna powered by my Fyt settings and with radio level at 45.

I hope for good future work from Kiotis.
[FYT Android Head Units] aiui:
In my humble opinion, I think that the search for an alternative frequency should firstly look for alternative frequencies already stored in the memory itself, and secondly, after going around the frequencies completely, it should go back to the original frequency. Of course this is easier said than done, but the truth is that at least AF already works.
[FYT Android Head Units] KoTiX2:
The search should stops after one full round even if a frequency is not found and will set again the starting frequency.

This is happening on all my tests but maybe on the road something different can always happen. I will investigate further..

The search cannot be faster because to find another frequency of the same station it's needed to receive the picode. The picode can be received in 1-2 seconds so at each seek stop it will wait up to 2 seconds if picode is not found.

I'll try to improve this AF function but as you can see there are some limitations.
[FYT Android Head Units] Moldeb:
Drove through half of Germany today and it worked pretty well:

- if the AF was stored it just switched almost seamlessly.

- if it was not stored it searched but fairly quickly.

- if there was no AF available, it went back to the original frequency after a round.

I'd still have some proposals for your consideration:

- the full round can mean many stations to be scanned and getting about a second sound for say 60 stations is tedious. I'd prefer a silent scan and only unmute once the scan is over.

- now that I'm travelling my stations list is full of regional senders from another region and while I want to keep them for when I'm back, here stations seem to get shuffled a bit (e.g. new logo old name) since other local senders are on the same frequency. Guess it'll sort via RDS info when I listen to a station longer. Is there maybe a way to correct the name faster, e.g. together with assignment of the new logo?

And one question, in case I've done something wrong: Do I have to start Navradio+ via the radioproxy or does it not matter? Also, every now and then Navradio proposes to remove the original radio app - but I thought that's not required anymore as we now have Radioproxy. Or does the proposal come up when Radioproxy is not running (direct start of Navradio)?
[FYT Android Head Units] giobengi:
No Kotix, for me it continuously scans over and over again without returning to the origin station, I also tried to empty the cache but I think it doesn't work properly on my navifly.
[FYT Android Head Units] Closerm6b:
When AF searches and does not find any strong waves, it returns to the first one. Isn’t it possible, when passing, to record the strongest waves for all the recorded channels, as in the original radio?
[FYT Android Head Units] KoTiX2:
Did you update to 3.11?

Did you increase the sensitivity to 40-50?
[FYT Android Head Units] KoTiX2:
Please explain better
[FYT Android Head Units] surfer63:
Early this week I also had to drive through multiple "frequency regions".

Maybe it is indeed better to first use the frequencies that have already been stored. I have 9 stations stored (with only 4 important ones). The one with the least frequencies has only 3 frequencies, the one with the most has 6 frequencies. It is much faster to scan one of the stored 3 (or even 6) frequencies, than scan the whole frequency range. I think that a total frequency scan, could then be the second step.

Or make this a Setting, something like: First use stored frequencies (On) and then start full frequency scan (Off)" (or checkbox: Always do full scan instead of using stored frequencies first). Most users that used NavRadio before the AF capabilities will have those frequencies stored anyway. And new users also want there favorite stations first, so when they start they will first put in the frequencies of their favorite stations, and do not do a full scan getting 24 stations they do not want anyway.

And for the same "lazy" user, who only has the first frequency stored for his home location, to have an On/Off setting: "NavRadio can use your stored frequencies (Off) or scan the whole range (On) which might take up to 2~3 minutes.

(Oh, those design decisions ;))

1. Agree :), or put the volume to 30~50% or so.
[FYT Android Head Units] Specy01:
Ditto for me, so much so that after a few days, yesterday, I preferred to deactivate AF and do the search again, after which I manually memorized the respective alternative frequencies in the various radio stations. Now for a few days I'll try to turn AF back on to check what it does. To be precise, I did various tests setting the sensitivity between 40 and 50 with intermediate values. He always did a search for me starting from 91 up to 107 MHz and went around several times without success. My reception is quite good and I also did the tests by varying the antenna power supply as well
[FYT Android Head Units] KoTiX2:
Please try to remove radioproxy 1.2 and use the original radio app instead.

It does the same thing of NavRadio: no voice from tomtom but Radio get lowered or muted according to gps mix.

Does this happen to you too?

thx;)
[FYT Android Head Units] KoTiX2:
Ok, the mute sound is an easy job but for the rest i'll need some brain storming.. it will take a while..
[FYT Android Head Units] ionutlup:
Hello.It is possible a new free version for testing ,maybe the last one 3.11.The transmission is interrupted for 1-2 seconds after a short time and this phenomenon is constantly repeated. I own a Roco K706. I also tried with RadioproxyFYT 1.2 and it doesn't work. I can't buy the application until it works perfectly for me.Thanks
[FYT Android Head Units] KoTiX2:
Radioproxy is only for FYT devices not for rocok706.

I'm aware of the 2 seconds audio mute problem and units now I haven't found a way to fix it because it's something due to the Bluetooth audio and system service.

The only thing you can do is to press the reset button in the Bluetooth screen.

That normally stop the audio issue.
[FYT Android Head Units] ionutlup:
Already tried that and is unchanged isue!
[FYT Android Head Units] 3PI:
Thanks for your genius.

Unfortunately, I can no longer test with the original application. When I installed NavRadio+ application, I deleted the original radio application, because it was horrible.

I'm going to try what you tell me, deleting radioproxy1.2

thx
[FYT Android Head Units] giobengi:
Yes Kotix I have already written about that I updated to version 3.11 and radioproxi to 2.1 and the radio search level to 45. Today it worked well sometimes but most of the time it scans continuously without stopping and if it does not find the alternative frequency it doesn't go back to the original.

Then I agree with what is written about it being better to disable the audio when doing the search and if it were faster it would be excellent.
[FYT Android Head Units] KoTiX2:
I asked you to remove radioproxy to let the original app to start but if you don't have it there is no need to remove it
[FYT Android Head Units] KoTiX2:
The sensitivity range on your unit is 0-100 or 0-255?

Whenever you stop the search pressing an arrow or changing station it should go back to original frequency.

For a full loop I mean that if you are on 102.5 the search goes to 108, then 87.50 and keep searching until it goes over 102.5. So it will end at next station found after reaching again 102.50. Then if nothing is found it set back the original frequency.
[FYT Android Head Units] KoTiX2:
It's working fine here.

My problem was that I used the RCA out of my unit and the audio from navi is not correctly directed to this output.

Then I connected the amplified/normal audio output to my speaker and everything is working fine now.

Do you use an external amp on your car?
[FYT Android Head Units] giobengi:
I don't understand this sensitivity, where can I find it? I'm talking about the sensitivity of Navradio with FM which I set to 43.

I understood the search cycle but it doesn't stop for me and the search continues for more and more cycles and it is also difficult to stop it even if I use the arrows or click on another station.
[FYT Android Head Units] KoTiX2:
Yes, the sensitivity in NavRadio settings can be 0-100 or 0-255 depending on the fyt model. What range do you see there?
[FYT Android Head Units] giobengi:
Ok I'm sorry, so for me it's from 0 to 100 and I set 43 FM and 7 AM.
[FYT Android Head Units] giobengi:
ok so for me it's from 0 to 100 and I set 43 FM and 7 AM
[FYT Android Head Units] giobengi:
This is the video that Kiotix are request. I hope it is ok.
[FYT Android Head Units] KoTiX2:
uhm.. .this is a bit weird...

please post a picture of the edit window showing SID number and AF list, like this:
[FYT Android Head Units] surfer63:
Completely off-topic, but this video showed me the possibility of the semi-transparent carroussel option for the stations. Stunningly beautiful!

Mille grazie.
[FYT Android Head Units] giobengi:
Here is the photo requested.

Too beautiful right Surfer? and with the background that I adapted to it everything is even more beautiful.
[FYT Android Head Units] surfer63:
The background is "too much" for me :). I have a very simple non-distractive background.
[FYT Android Head Units] surfer63:
Coming back on the "AF seeking with AF switched off".

For me AF in general functions fine, also this weekend (Sunday). On the way out, 2 stations switched automatically to the new frequency. On the way back I had the radio switched off (I listened to other music). And for that reason those 2 stations were still on that other regions frequency.

This morning I had a short trip. I started NavRadio and immediately I switched off AF (as I did not want to listen to 1~2 minutes of incorrect stations or "crackling noise"). Those 2 stations on that other frequency of another region, was not the active station.

So I tapped the desired station and wanted to start double-tapping to get to the correct frequency. But before I could do that, Navradio+ started to search for an alternate frequency (and displays that message), but as mentioned: I had AF switched off ( and I checked that immediately again of course).

I stopped the app and then restarted it. Then it did not start searching again. Does this AF on/off require a restart of the app?

This all on the 0.3.11.
[FYT Android Head Units] KoTiX2:
uhm... i'll check it. it's probably another bug :(
[FYT Android Head Units] heavyhms:
@KoTiX2 , after the update of Google app released yesterday the TomTom audio notifications are received correctly, fading the radio playback, but after some channel change via steering wheel button navradio+ seems to lose again audio focus (and also cannot change channel via steering wheel buttons. A device restart restored the complete functionality (and also tomtom notifications remains functional)
[FYT Android Head Units] Pyteck:
Hi @KoTiX2

Thanks for your work. Just a friendly reminder about the mode button not working after radioproxy 1.2 is installed.

Not sure if you still have this in mind, have fixed it or still working on it?

Thanks
[FYT Android Head Units] j0hn83:
I noticed this last night when trying RadioProxy.

My steering wheel mode button usually cycles between radio/Bluetooth audio/video player/navi app

With the stock radio app uninstalled the mode button simply skips the radio on the cycle and continues to work.

With radio proxy installed the mode button simply launches navradio on each press and no longer cycles through the various apps.
[FYT Android Head Units] Pyteck:
Thanks. This was exactly my experience.

Hopefully the developer has this in scope especially with all the other requests.

Radioproxy seem to solve a noise problem i seem to have with my head unit. Happy to wait for a fix if there would be one.
[FYT Android Head Units] surfer63:
We discussed this on Nov 5th. I think it t might be because the cycle carroussel checks for the package name and an activity in the original radio app. An activity the current radioproxy doesn't have. Maybe that breaks the cycle. But the com.syu.ms code is currently difficult to read.

I could be wrong.
[FYT Android Head Units] KoTiX2:
I looked at the code inside com.syu.ms and it check if the current foreground app is com.syu.radio it switch to next app.

Radio proxy package name is com.syu.radio but it's moved to background to bring up NavRadio.

NavRadio is not it list of the apps of Mode button so it never switch to next one.

What we need is to modify com.syu.ms adding NavRadio package name as an alternative to default radio app.

I'll ask to seb21 to add it ;)
[FYT Android Head Units] surfer63:
There are many apps in this cycle like the com.syu.dvd. There is not one single 7862 or 8581 that still has a DVD. The DVD app is not even packaged anymore in the firmware.

So what if you make an alias to com.syu.dvd in NavRadio, like I do with all those FYT apps in my FyrHWOneKey?

The only thing that could happen is that users on the first start have to chose on "Which app to start" -> Once/Always)
[FYT Android Head Units] KoTiX2:
Uhm... But the problem is not how to get into NavRadio... It's how to get out of it.

I'll try anyway your suggestion

Thx ;)
[FYT Android Head Units] surfer63:
No, I know that too :), but if com.syu.ms thinks it is com.syu.dvd it might continue the cycle.
[FYT Android Head Units] marjanoos:
@KoTiX2 I don't understand the sensitivity bar in settings. I have the 0-100 range and I have to have 20-30 set which seem to be low signal strength issue? But those stations which are found have good sound quality and RDS is found quickly. But using AF there's a constant station search.

Also I have experienced an issue which I have experienced on MTCE - with AF turned on and using Spotify, NavRadio turns automatically when new frequency is found and stops playing music from Spotify.
[FYT Android Head Units] KoTiX2:
The AF stop when it receive the the station id number, listening well doesn't mean that the signal is good enough to receive the picode.

Where are you from? Maybe in your country the RDS is not fully implemented...

On MTCE is not the AF that wake up the radio, it's the TA function. Disable the TA function.
[FYT Android Head Units] marjanoos:
But should it look for another frequency? I mean that I have one station which I use. Signal should be good enough. If sensitivity is set to something under 30, I can hear the station well. In case sensitivity set to 40-50 I get only noise. That's why I don't understand how it works. And I think it's not explained enough in the app.

I'm from Poland and RDS is implemented well here, I mean RDS and RDS-AF are working well in stock head units.