yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] KoTiX2:
If sensitivity is set to 40 or more the search will find only stations with higher signal. This mean that the search will not stop on stations with noise but only on very good stations.

Lower is the number more noisy stations you'll get.

In Poland I know that RDS is not well implemented for the RDS text for example. In many stations the text is transmitted in the Station Name field and not in the proper text field.

I added the LiveRDS option in settings specificatelly because of the request of a Polish user.

Anyway i just wanted to be sure you were not from USA, Canada or other countries with different system.

I don't know about the picode... I beleive it's ok

Stock head units use 2 different circuits (PLL) to find the alternative station. One circuit keep the current frequency, while the second one search on background another frequency that transmit the same picode. When the second circuit find the new frequency, it is passed to the first circuit.

You don't hear or see nothing happening during the AF search because of these 2 circuits.

The code in my app instead start a manual search of the next good frequency, wait 3 seconds for RadioProxy to send the picode and if it matches the original station it stops, otherwise it keep searching.

I'm still trying to improve the function.. it willtake a while..
[FYT Android Head Units] surfer63:
Picking the right sensitivity can make a big difference. Increasing the range from 20 to 30 for example, can already make all the difference. Increasing it to 35 can make it find the stations you want. Increasing it to 40 can result in hardly any station being found because almost none of the stations is strong enough.

You have to listen on which sensitiviy you get good reception.

I did some experimenting myself and for my radio 35~37 seems optimal.

But of course that depends on your own antenna and amplifying circuit. I assume it is different per car brand and maybe model. But that's a guess of course.
[FYT Android Head Units] danilaur:
i use 30 for fm
[FYT Android Head Units] Moldeb:
Any recommendations as starting point for the 255 scale? My second unit has that scale, I'm trying around 165 for FM (disabled AM) but it seems a bit arbitrary. Also has the bad habit to miss stations by 0.05 (in Germany all stations are on the 0.1 pattern) or add e.g. 97.45 as AF for a station that is on 97.4 which is never true and just prolongs the scan... On that one, would it be possible to add a rule for AF that an AF must be at least 0.1 MHz (better 0.5 MHz) away from the other? Everything narrower is definitely ghosting...
[FYT Android Head Units] KoTiX2:
I'm sorry but I have only a 0-100 scale unit, I can't tell the right number on the 255 scale. You can do your own tests with manual seeks and remember that also the LOC/DX function change the sensitivity. Only after you setup your sensitivity with manual seek you can try and fine tune it with AF.

In Europe the frequency steps are 0.05Mhz for FM, there is no need to change it.

I'm adding now a better way to handle the AF, switching first all saved Alternative Frequencies and only if nothing is found on these ones start seeking for a new one.

It seem to work pretty well so far...

I'll probably release it next week ;)
[FYT Android Head Units] giobengi:
Excellent Kotix, although it would be really nice if it could work with background search, as you wrote above, while you listen to a frequency it searches for an alternative frequency underneath.

Yesterday I took a long trip and I tried navradio well but I missed most of the Sinner tennis match on RaiRadio1 because it was always looking for the alternative frequency but I must say that now I have this function on my car radio, before I couldn't follow a station for the entire journey.

I hope you will improve it.
[FYT Android Head Units] Moldeb:
Yes I use that of course (Loc to skip noisy stations)

I know but I've found it faster and less erratic to set it to South America (0.1 MHz)...
[FYT Android Head Units] marjanoos:
Now I think you misunderstood me. I don’t have MTCE hu anymore. I have this issue on my M6 Pro.

Today it showed up again. I started using Spotify and after a while radio started to look for alternate frequency and my spotify music stopped. And TA function is disabled.
[FYT Android Head Units] Pyteck:
Thank you both.

Would be a happy volunteer to test when the fix is implemented.
[FYT Android Head Units] KoTiX2:
I can say that today I fixed the MODE button with a new version of RadioProxy and of NavRadio+

Both will be out tomorrow or the next day. Here is the full changelog:

- Fixed AF toggle for AFseek

- Added AF frequency switch before seeking

- (FYT) Fixed MODE button using RadioProxy 1.3

- (FYT) Added mute during il afseek
[FYT Android Head Units] pedja8791:
I recently got this unit, the app is working great but I had no rds info, I also didn't had it on the default radio app.

Radio chip tda 7780 supports rds as far as I have been able to find info on it.

I found out that it doesn't opens same options under extra settings, depending on the code you type.

I have tried with 8888 but I was not able to find rds option, only to change region under radio option.

After some research I typed 123456 and more options appeared, under config info there was rds which was unticked, after I tickted YEEEY, it's now working,even in default app.

Hope that this will be helpful to someone like me.

BTW great work, now I'm purchasing the full version.

Any updates when Serbia will get logos?
[FYT Android Head Units] KoTiX2:
Serbia already have logos..
[FYT Android Head Units] IgorYa:
Hello! My stereo mode (ST) icon never lights up. It turned on once after installing the application, when I switched from my native radio to this one, and no longer appears. What could be the reason?
[FYT Android Head Units] KoTiX2:
Is ST mode enabled? what kind of model do you have?
[FYT Android Head Units] IgorYa:
Yes, sure. XIMA XV6 Pro, uis7862, 4x64
[FYT Android Head Units] KoTiX2:
Is this a FYT device?

MCU number?
[FYT Android Head Units] Warlord721:
I actually have noticed this started from a couple versions ago, and meant to post a message here to @KoTiX2 about it. I have found that when I start NavRadio (using paid version) the ST icon is not working and the signal is not in STEREO. BUT if I enable TA and let it scan then when it stops then when I select other channels then ST will light up and I believe the signal is in STEREO again as it sounds better.
[FYT Android Head Units] IgorYa:
FYT1
[FYT Android Head Units] IgorYa:
I confirm, I tried it now, it’s the same for me
[FYT Android Head Units] KoTiX2:
I can confirm that there is a problem with Stereo mode.

I'll try to fix it during this week.

Sorry about it..
[FYT Android Head Units] KoTiX2:
Coming up on next version 3.12:

- Fixed AF toggle for AFseek (it was inconsistent)

- Added AF frequency switch before seeking (First scan through the saved alternatavi frequencies, then seek if nothing is found)

- (FYT) Fixed MODE button using RadioProxy 1.3

- (FYT) Added mute during AFseek

- (FYT) Fixed Stereo mode

To fix the MODE button it is mandatory to install RadioProxy 1.3:

RadioProxyFYT_1.3
[FYT Android Head Units] rockman18:
Hello @KoTiX2, little question, just to be sure... When you launch an AF seeking, do you save all aternative frequencies even for other found stations or only for the current looking station ?
[FYT Android Head Units] KoTiX2:
Only for the current station.

It save all frequencies that send the same picode of the current station.
[FYT Android Head Units] rockman18:
As you receive the picode and you know the list of stations, is it possible to fill the other stations Alternative Frequencies at the same time ? it will improve the current AF frequencies database in one shot. (will stop when found the looking station but some stations will benefit of this seeking)

Edit : imagine i'm leaving a region and losting all my radio station at the same time, in one seek to retrieve my current station, the seek will pass through other stations and when my station will be found, i can switch to another station that perhaps has been found during the check and i'll go directly on the detected AF.

Edit2 : Perhaps the last detected AF station can become the main frequency for this station ?

exemple : I save my radio station with picode Radio1 in City1 on 100.00MHz, I move to city2, now for this picode 105.00MHz is the AF. But I stay in City2 for months so 105.00MHz can become my main frequency for the moment. When I will move back to City1 100.00MHz is in my known alternative frequencies so it will switch quickly and it will replace the main frequency for this station.

@KoTiX2 all of this are only ideas for a potential roadmap
[FYT Android Head Units] KoTiX2:
It's a nice idea but you should have a very good signal to avoid receiving the wrong pi-code, otherwise it will be a mess...

I'll think about it and I'll make some tests. I cannot guarantee anything anyway....
[FYT Android Head Units] rockman18:
I have added an edit2 to my previous message i don't know if you see it.
[FYT Android Head Units] Moldeb:
So in case this is of interest to anybody: On my second unit (255 scale) I need to go to around 220 to avoid mere noise or ghost stations to be stored as "stations". The 255 scale becomes less sensitive with higher numbers.

On Navradio+ 3.12 and RadioProxy 1.3, I still see the issue that AF stores a x.y5 MHz variation of a x.y0 station as AF for that station which is never true. Example: Station is on 87.6 MHz, AF stores 87.65 MHz as alternative frequency for the same station - this is never true and always just a ghost / tuner failure and always gives a noisy signal. For now I still use the Latin frequency scheme in order to not have to delete the x.y5 MHz stored frequencies. A rule or minimum frequency gap between AFs for the same station would be great!
[FYT Android Head Units] KoTiX2:
Edit2: it's already like that for the current station: everytime a new frequency is found or it switch one of the saved ones, it become the main one.
[FYT Android Head Units] KoTiX2:
This is not very clear to me...

If you do a manual seek, does it stop at frequencies with 0.05 MHz ?

If it does that manually then you need to raise up more the sensitivity or there is something wrong with your reception...
[FYT Android Head Units] Moldeb:
Yes manual seek. First it stops at the correct frequency for the station (say 0.1 MHz). Upon next seek up, it often stops at the same station (plus 0.05 MHz) which is just wrongly tuned for the same station. Happens with strong local stations. I'll test more on the sensitivity, seems to be a fine line (if at all) between avoiding the above and skipping real but weaker stations.

I don't care about the issue in manual seek, the real usability issue is that AF does the same and stores useless AFs but I understand it's due to sensitivity and I need to solve it for manual scan first.
[FYT Android Head Units] surfer63:
You should indeed raise the sensitivity. If it gets stuck on not completely correct frequencies, it is because the sensitivity is for example 20. If you raise it to 30 (for example), this not so good reception quality of this not entirely correct frequency will simply be skipped.

And of course you need to fine-tune here. If you raise the sensitiviy too high, it will skip almost all stations.
[FYT Android Head Units] KoTiX2:
I'll see if I can set a 0.10mhz step during seek function but I'm very doubt that is possible.

I'll let you know ;)
[FYT Android Head Units] Moldeb:
Clear but for strong local stations 0.05 MHz off may still be stronger than weaker "real" stations. I understand the concept though and will continue to try and find the right threshold.
[FYT Android Head Units] Lahoyaa16:
Thanks for the update, but with this update, errors started to occur on FYT devices. When we enter the notifications and logo menus, the application crashes and closes, and RDS texts, especially station names, appear with incorrect characters and corrupted characters.
[FYT Android Head Units] KoTiX2:
Please try to uninstall and re-install
[FYT Android Head Units] marioti:
Hi KoTiX2​

About NR+

Is there a way to make more fit the elements in split screen. Look at the pic. The station name is small, and the stations windows below have (to me) too much free space from below (maybe bigger windowses?)
[FYT Android Head Units] KoTiX2:
Ok. I will fix the text sizes but I'm not about filling up the empty spaces.

Which resolution is your display?
[FYT Android Head Units] marioti:
1200x2000
[FYT Android Head Units] IgorYa:
Will version 3.12 be posted on the Huawei appgallery?
[FYT Android Head Units] KoTiX2:
Yes but there are a few bugs to fix first so it probably will come 3.13 straight away
[FYT Android Head Units] Closerm6b:
Congrat the app Just around the corner to be perfect
[FYT Android Head Units] rockman18:
Hello @KoTiX2, I experience a strange bug on the last version (I think it was already there on the previous version).

I'm listening Spotify, but when I enter in an underground parking the sound starts to cut off at fix rate and it seems to be because of the AF seeking running in background even if Navradio doesn't have the sound focus. And if I open Navradio the AF seeking is running but not in mute. (otherwise, the mute seeking works)
[FYT Android Head Units] KoTiX2:
Thx for reporting this.

Indeed the NavRadio AFseek is running even when the app is on background and not playing.

It will be fixed in next release ;)
[FYT Android Head Units] Ahto Simakuutio:
Good news. Upgrading 3.08 to 3.12 fixed the issue I reported earlier this year.

I had found a way to reproduce it 100% and even a workararound for it, but checked the last version still before reporting. Good that I did, I assume the audio focus / mode fixes have eliminated the problem. Good work 👍
[FYT Android Head Units] Krt0245:
Hello, do you have a plan to put the app compatible with mt6183 cpu and mt6225l radio chip? My stock radio app is quite bad at their job to decode the fm signal.
[FYT Android Head Units] KoTiX2:
no, sorry but i can't work on every single model
[FYT Android Head Units] KoTiX2:
Coming up on next v3.13:

- (FYT) Fixed issue with MODE button and launcher icon

- (FYT) AFSeek is now disabled if another player is playing

- (FYT) Fixed some more afseek bugs

- Increased text sizes in Split Screen

- Fixed another bug while merging stations
[FYT Android Head Units] rockman18:
Hello, I've updated this morning on 3.13 but still have AFseek starting in background when listening another app (YouTube, Spotify)

Edit : I've not start Navradio on my head unit. The AFseek start even if Navradio is not launched.

If it could help, here is my method. I start my car but not start Navradio at startup. I open YouTube or Spotify, I lost radio signal so AFseek is starting, I open Navradio+ and I have the splash screen as it's the first start. The AFseek is running.
[FYT Android Head Units] KoTiX2:
If you never open NavRadio then it's not the AFseek code I wrote in NavRadio but it's the original AF that is scanning for frequencies.

I have no control over it.
[FYT Android Head Units] rockman18:
Oh so that could mean that original AF is really working? 😳 Is it possible to deactivate it (deactivate hardware AF in Navradio) and activate only software AF in the app ?

The strange thing is that the bug wasn't there before last week. Can't it be a RadioProxy behavior?
[FYT Android Head Units] KoTiX2:
Original Hardware AF is still working but you know that on FYT units it does something totally wrong.

You can turn it off from NavRadio or the original app but I still need it ON to catch the moment when it start looking for a new frequency so I can start my own AFseek function instead.

If you disable the hardware AF, the SW one will never work.

Please make some more tests, uninstalling NavRadio and radioproxy, disabling AF, etc... just to be sure that it's not caused by my software.

Let me know ;)
[FYT Android Head Units] marioti:
After last update i've noticed a bug or something. When I edit station (I just add alternative frequency) then I can't edit it anymore or even change the station for other. App need to be reboot
[FYT Android Head Units] KoTiX2:
Ok, I'll check it but remember that you can also edit it from the bottombar/stations/edit station
[FYT Android Head Units] marioti:
ok. thank you.

I like bigger font for station name in split screen :)

So you say, there's nothing possible to do with making a bigger window with station logo/name in this view as on my latest video?
[FYT Android Head Units] giobengi:
Hello to all radio listeners, with the latest version the AF for our Fyt 8692 finally works quite decently but I continue to have the bug that when I stop even for a short time, when I turn the machine back on I have Igo running, I hear the audio of the radio that is in the background but I can't control it with the steering wheel controls unless I bring it

running first and then I can put it back in the backgroud.

Then I wanted to ask you Kothix, before you send me to hell, with the original radio if I gave the voice command saying: "HEY TOP - FM 90.80" the radio would start on this frequency (Virgin radio), with Navradio/Radio proxi ora the radio starts but not on the called frequency. For me this was very convenient and did not distract me from driving, can this be implemented or does it depend on the Toppal voice app?

Thanks, if you want you can send me to hell :)
[FYT Android Head Units] KoTiX2:
I'll have to implement the voice recognition commands into NavRadio.

Right now these commands are totally missing.

Anyway I don't understand why the radio start at boot if you didn't started it and if you didn't set it to start at boot.

When you say "for a short time", do you mean during sleep mode? Or after a cold boot?
[FYT Android Head Units] giobengi:
Yes, I set the automatic start of Navradio, Whatsupp and Igo as navigation apps, then I set the sleepy mod. With the cold start everything works fine but if I stop even for a short while and get out of the car (for example to get coffee) when I get back in I have the navigation in the foreground, I can hear the radio but I can't control it unless I first remove it from the background and put it in the foreground for a moment.

So you will implement voice commands in the future I hope. Thank you
[FYT Android Head Units] j0hn83:
I have the same with Navradio+ but I think it has always been this way.

I'm usually listening to Navradio when i turn the car off. When I start the car and the head unit wakes from deep sleep Navradio will resume playing music but the steering wheel buttons don't change stations. I need to open Navradio (bring it to the foreground) in order for the buttons to work again, then I can safely minimise Navradio and the buttons continue to work.

This only happens after the car has been turned off and the head unit wakes from sleep mode. I have the same behaviour with the original radio app uninstalled and with radioproxy installed.

It isn't a big issue for me.
[FYT Android Head Units] KoTiX2:
Are you guys sure that when the unit wake up and the radio play NavRadio is on background?

When you open NavRadio after sleep, do you see the NavRadio splahscreen or do you see the NR home screen?
[FYT Android Head Units] surfer63:
I think this is the 8 year old "feature" that when you use the default property "ro.build.go_lasttop=true", the last media player will be started, which can also be the radio. As the radio module itself is a piece of hardware controlled by the MCU and not by the Android level, it will simply start playing without any app to control it. That was already on the Sofia-3GR units in 2015/2016.

This property "ro.build.go_lasttop=true" is a "FYT default" and not even in the config.txt.

As I don't want any music starting when I start the car, all my config.txt's contain the line "ro.build.go_lasttop=false" (one of the scripts in post #4 of my "all-in-one" thread.

I prefer to switch on the (Nav)Radio or a mediaplayer, when I am "ready for it".

However, when you restart the car within 3~4 minutes, so before the "deep-sleep" really has set in, it will still play.
[FYT Android Head Units] giobengi:
No I don't think this happened with the old radio and in any case it only happens in suspension, with the first start everything is ok. In fact, I notice it immediately as I don't see the navradio popup on the navigator and yet I can hear the audio below.
[FYT Android Head Units] surfer63:
What you describe in your earlier post is exactly the "feature" I am describing. And please note that in 2015/2016 there was no NavRadio. That came in 2022 or 2023. So before that time you had that behavior with the original radio.

You can't "fix" this behavior untill FYT "fixes" it and they won't do that and can't do that because the radio starts earlier than the Android control level.

(And another thing: Why Whatsapp? Never type messages during driving. That causes accidents, and please don't tell me you only want to read what others are sending you, that is also very distracting. We used to have a lady living in our close neighborhood that got killed in an accident, because some moron was chatting on his phone during driving.)
[FYT Android Head Units] giobengi:
Yes Surfer, I don't use Anroidauto and on AA whatsupp is there anyway and I try to use it only with voice messages but I realize that it is dangerous just like in AA.

Returning to the sleepy problem, I don't remember that this happened with the original radio and I don't think I remember it wrong.
[FYT Android Head Units] Droyka:
Hey KoTiX2,

I have a suggestion for the grid view. Right now there are 2 style options. Show logo, name and fequency and the other option is just the logo. Could you add the option to show logo and name? It could allow for a slightly larger font and logo in the grids :)
[FYT Android Head Units] Alphanewb:
Thanks for this app, I hate the atoto style and lack of options, and how the atoto app has such limited space for stations, and even pretends to have a second page but it just clones the first page...

I am a paid customer of navradio, so I shall complain that it has possibly the most unreliable swiping I have ever experienced, a notable accomplishment! Thankfully carosel mode works fairly smoothly and looks good!
[FYT Android Head Units] marioti:
i have the same user experience. I use carousel mode, because two other just running away when i slide them. I guess it would be better to change it for card swiping just like in a phones main screen is (i don't know how to translate it)
[FYT Android Head Units] KoTiX2:
Ok. I'll see.what I can do about it..
[FYT Android Head Units] Alphanewb:
A disable smooth scrolling option would be the simplest I guess? Or maybe some ghosted rasterization of the random radio station logos?
[FYT Android Head Units] KoTiX2:
Can you post a video of the problem on your unit?

So we are sure that we are talking about the same thing?
[FYT Android Head Units] miruim:
I have a file with almost 200 png files of the radio stations in Portugal.

what is the best way to add the logo in a automatic way , because i created a new folder inside radiologos folder but it doesnt find it . i have to put it manually.

in the zip file i have downloaded in the radio app, some radio logos have numbers. what that numbers means Pi Code?

if yes , where i can find them ?

regards

Sorry.. already found it, and creating an entiry list
[FYT Android Head Units] KoTiX2:
If you wish I can add your logos to my package so they will be available for other people too.

Just send me them or upload them somewhere. Thx ;)
[FYT Android Head Units] miruim:
Sure, no problem.. I will add the radio stations with logo and pi code, and send to you.
[FYT Android Head Units] giobengi:
Out of curiosity, where did you find the pi codes?
[FYT Android Head Units] marioti:
...and all logo stations, too.

I was searching them for my country but no luck.