yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Pyteck:
Thanks.

I have just installed Radioproxy 1.2 with the free version of Navradio.

I find that my steering control buttons which takes me from the home screen - bluetooth device - music player - telephone calls no longer work with Radio Proxy 1.2 installed. When this is removed, it works fine. With radio proxy installed I only get one toggle from the homescreen to Navradio and not to other apps, bluetooth etc. Can this be fixed? The button which stiched between stations and vol up and down still works just fine.

The other good part - I had a noise issue which sounds in the background of my headunit when started from cold or hot. The sound is not directly from the car speakers but from the speakers supplied with the headunit. The sound was almost like the OEM radio app is preset/tuned into a station that isnt broadcasting on boot but has white noise in it and was low and intermitent...hissing lowly, cutting and starting again. Even though radio isnt set to start on boot, it still appears that somehow, it does and tuned into this hissing frequency. I thought it was my head unit and grounding issues but it sounded more like a radio frequency reception issue. The good part is that installing Navradio seemed to have solved this issue with the noise as not Navradio seemed to have overridden the default radio and tuned into a clear station but no noise still or that Navradio has disabled the default radio so that this noise doesnt happen anymore. So thank you to the developer.

Will let you know if this changes but so far so good look to be fine. Now just fixing the toggle button between apps. This is disabled by Radio Proxy.

Will be buying the full version once this issue is fixed. Unless its fixed with the paid version.

Thanks
[FYT Android Head Units] KoTiX2:
Radioproxy replace the original radio app with a shortcut to NavRadio, so that original app never start.

The fix isn't done by NavRadio but by radioproxy.

You could accomplish the same removing the original radio app with my remover tool.

I'll investigate why radioproxy interfere with your mode button.
[FYT Android Head Units] heavyhms:
Same issue I have pm to you some days ago with my "Source" steering wheel button. Is not a big problem but if it where possibile to restore the button's original behaviour it would be a good thing.

After installing RadioProxy (same with 1.1 and 1.2) at the first button pression there a dialog box asking associate the function with Navradio+ or RadioProxy. Both options have the effect of taking directly to the Navradio+ main screen
[FYT Android Head Units] KoTiX2:
Could you try to raise up the sensitivity in NavRadio settings so it find only good stations and not the noisy ones?

Even without installing radioproxy 1.2, try to do some manual stations seeking to check if it stop to good stations.

Ones you set the right sensitivity the proxy should work ok.
[FYT Android Head Units] Asmund:
I have the exact same problem! Its very very annoying.

As stated, it doesn't help turning off AF, coz it is still "SEEKING for an alternative frequency" - and doing a really bad job.

After trying for several over an hour, I had to just turn off the radio.
[FYT Android Head Units] KoTiX2:
Ok. Remove radioproxy for now. Read the 2nd post about it.

Could you also try to adjust the sensitivity as written in my previous post?
[FYT Android Head Units] Asmund:
I'll try to remove radioproxy for now!

Which post is "Read the 2nd post about it." - What number?
[FYT Android Head Units] Lahoyaa16:
Bende de aynı sorun var: (cihaz, UIS7862,) Sürüm 3.10 sadece ses odağındaki ses eksikliğine çözümdü, yenilikler var ama aynı zamanda eksiklikler ve hatalar da var.

Mod translation: I have the same problem: (device, UIS7862,) Version 3.10 was only a solution to the lack of sound in the audio focus, there are innovations but also shortcomings and bugs.
[FYT Android Head Units] KoTiX2:
To REMOVE RadioProxy follow these steps:

Settings - Device - Applications - RadioProxy - Three dots in the upper right corner - Delete updates
[FYT Android Head Units] KoTiX2:
Remove radioproxy 1.2 and you will not have any bug.

P.s. it's mandatory to write in English on this forum
[FYT Android Head Units] Asmund:
Was a bit "tricky" removing the app, since it was called Radio and not RadioProxy.

Other than that it is working again.
[FYT Android Head Units] KoTiX2:
Can you tell me which value is set the sensitivity in your NavRadio settings?
[FYT Android Head Units] Asmund:
18
[FYT Android Head Units] KoTiX2:
Does the manual seek work ok with 18?

Does it stop on empty stations?

Could you try again using RP1.2 with sensitivity much higher like 40?
[FYT Android Head Units] Asmund:
I tried installing RP1.2 again, and set the sensitivity to 40, and also tried 50.

It made things a lot better. Its not so "aggressive" in "seeking for an alternative frequency".

One problem/annoyance is that when NavRadio seeks for af, it does sometimes takes quite a long time - sometimes about 2-3 minutes - its like it is scanning the entire FM band, and it stops for a moment at wrong stations or/and at a frequency where no signal is.

And the most annoying thing is you can't turn off AF. Even if you turn in off in the settings, its still "seeking for an alternative frequency" when signal is too weak.
[FYT Android Head Units] surfer63:
If you have a CANbus, did you set in the FYT Settings -> Factory -> Antenna normally On ( Most new cars need constant 12V on the Antenna to get a good signal, especially when you have a sharkfin antenna on your roof and connected via the CAN bus => Then set to On).

Without that I had "reasonable" reception in my home town (close to a radio tower), but also constant seeking when getting further away from the radio tower. With it set to ON, I have crystal clear reception and no more endless frequency scanning. Make sure you have this switched to ON with a CANbus and a sharkfin antenna on your roof.

Also: Apart from bugs that should be fixed of course (assuming you have paid and use NavRadio+, otherwise you can only kindly request ;)), I do not understand the complaint. Seeking the alternate frequencies is a one time job that might take long the first time. And after that you should never have to do it again (backup your settings!). But again: take a look at my first point.

But also: I have 9 stations I want to store where actually only the first 4 are of importance. For those 4 stations I added the first 3 alternative frequencies in/close by my region by hand and for the other 5 stations the first 2 frequencies by hand.

And based on that and the SID/pi-code of these stations with their frequencies, the rest gets scanned when on the road.

Edit: Or simply add the frequencies in the app and while driving it will nicely switch to another frequency when necessary.

This is the first functioning AF radio app for the FYTs, and in this case the first version. Be a bit patient please.

Edit: Updated first line to set it to FYT settings, to make clear that it is not part of the NavRadio settings.
[FYT Android Head Units] Droyka:
After updating to the latest version on my UIS7862 unit the app boots for a second and then crashes. Not sure what to do. Maybe reinstalling?
[FYT Android Head Units] KoTiX2:
Thx for your tests, indeed if sensitivity is not well adjusted it will cause to stop the seek at every small interference.

The fact that it stop and restart is exactly what it's supposed to do. I use the manual seek function to search for the next frequency and when it's found I wait for a picode for a couple of seconds. If the picode is not the same as the starting one then seek again for next freq.

Anyway I can confirm that there are various bugs in this first release of the AF seek function and I probably should have waited a bit more before releasing it but I'm already working on some fixes:

1. Indeed it never stops even if I wanted it to loop only one time through all frequencies.

2. I forgot to block the methods that look for logos and names causing the seek slower and more messy.

3. When a new frequency is found can happen different things:

- if there are no stations with same picodes just change frequency

- if exist a station with same picode add this frequency to the AF list of the station

- if exist 2 stations with same picode merge them together keeping the AF list of both of them

I already fixed the first 2 bugs, I'm working on the 3rd and I also added one more option in settings to enable/disable the AFseek function

I'm not sure if it's necessary also a confirmation dialog to start the AFseek whenever radioproxy advise that the signal is too low.

what do you guys think?
[FYT Android Head Units] fra_dta:
I would rather prefer no confirmation dialog

I would like to ask for another "issue", maybe it is not an issue, and there is way to do it.. I set manually some favorites and display them in the 2 lines at bottom, today I add other ones, try to put the new at the end manually, to have them displayed only if I shift to the lef. When done, they always put themselves in an other order, frequency. Is there a way to keep them as I like?
[FYT Android Head Units] KoTiX2:
You are not the first one asking me this.

The FAV list is generated from the combination of FM and AM.

Right now if you want to reorder them you need to reorder the stations in the FM list so they will be reordered in FAV list too.

I haven't found/thought of a good way to handle the problem so it's on hold for now...
[FYT Android Head Units] heavyhms:
I'm agree... better avoid a confirmation popup for AF.
[FYT Android Head Units] fra_dta:
I have another question, on boot..

I set start on boot Radioproxy (1.1) Navradio+ (3.10) and a Navigator.

Navradio+ autostart from its config is set to off

What happen is; I see Navradio starting, no sound, immediately after starts the Nav, still no sound, and after Navradio starts again, this time with sound. This is why I use both radio Proxy and navradio set on autostart.

If I try only Navradio it starts, immediately after starts the nav, no sound. So is it imperative to use them both or there is another way I haven't tried yet?
[FYT Android Head Units] Droyka:
Next day it seems fine. Just a one off kind of glitch I guess.
[FYT Android Head Units] KoTiX2:
NavRadio config most of the times is bypassed by the firmware of the unit, so don't even consider it...

What kind of launcher are you using? and which Navigator?

The startup is set in the launcher or in unit settings?

If with RadioProxy everything is fine means that somehow the original app is trying to start or something make it start.

You should try to understand which one is doing what...

NavRadio takes some seconds to playsound the first time on fyt units i don't know if the navigator takes over the audiofocus and then it give it back.
[FYT Android Head Units] KoTiX2:
Comin up v3.11

- Fixed crash introduced in version 3.10 (sorry...)

- (FYT) Fixed infinite loop of AF seeking

- (FYT) Added option in settings to disable AF seek

- Merge of frequencies now merge the AF lists too! (@surfer63 This is what you were waiting for :D )

- Improved autoseek and find logos codes

I had to release this update quickly because of a stupid error I introduced in the previous one that was causing a crash on all other platforms.

More fine tuning of the AF will come in the next week but it seem much better now :D
[FYT Android Head Units] fra_dta:
1 Ok, I don't use it

2 Native unit android launcher, Sygic

3 unit settings
[FYT Android Head Units] KoTiX2:
Please take a video of the problem so I can try to reproduce it.
[FYT Android Head Units] fra_dta:
I don't want to have You loose time, I think that the video could tell You very little, it is only a sort of three apps that start one after the other. I think that your "NavRadio takes some seconds to playsound the first time on fyt units i don't know if the navigator takes over the audiofocus and then it give it back." should be investigated better, so I'll try to change Nav and see if something change.
[FYT Android Head Units] surfer63:
I think this is exactly what happens. When Sygic starts, I assume it takes audio focus and after a few seconds releases it again.

Can you change the start up sequence: First Sygic, then NavRadio+?

And there is no need to start RadioProxy, NavRadio will take care of that.

The only reason I can think off to also start RadioProxy, is that when you start Sygic, then RadioProxy, then NavRadio, you will have slightly more time for Sygic to return audio focus.
[FYT Android Head Units] fra_dta:
1 No, actually, because I use native settings M300s autostart, from android, and I simply set the three apps on yes.

2 I am aware of that, but with only one of them one instance of Navradio starts but no sound, then starts the sygic and remain there in full screen, without sound.

Maybe could it be different if I started navradio and sygic using your FYT-Starter_1.01.1907081605.apk?

3 I begin to think it is so.

I'm using this native launcher,

I really can't care less of the time and music gadgets, the annoying thing is that I set Sygic as default in the pip, and this prevent me to use split screen with navradio and sygic, because if set in the pip as default starting nav that app won't work in split mode. I'm considering your launcher 34, for now I'm using nav at full screen and Navradio circolar widget
[FYT Android Head Units] surfer63:
Sorry, Off-topic.

This is not to tell you about my preferred programs or exchange them with others (I don't like that ;)), but just to give you another option for split-screen. I am using Nova launcher (but any non-PIP window launcher will do) together with "Split Screen Launcher", which is an app, not a launcher (you might need to side-load if play store doesn't allow you to install). Split Screen Launcher gives you the option to place shortcuts on your home screen that will start two programs simultaneously in split-screen.

I don't want anything to start on boot. I start an app, tap a widget or I start via the shortcut 2 apps.

See below the screenshot with the red rectangle. Click to enlarge (I used to have a clean screen with a bottom icon row and two widgets on the right side).

For this example I have in the in the red rectangle a 2x3 icon row:

Maps + media player, Maps + RadioDroid, Maps + NavRadio+.

Magic Earth + media player, Magic Earth + RadioDroid, Magic Earth + NavRadio+.

Simply tap one of them and both apps are started in split-screen. For me this is ideal.

For normal trips I always use Google Maps.

For my trips with my caravan I always use Magic Earth as it has a truck/caravan/camper profile (same for Cygic?).

So normally it is a "bit" cleaner as I only add the Magic Earth icon row for a vacation trip, as I can add them again within 1~2 minutes.

(and the "extra" Media player icon in the center is for my wife ;))
[FYT Android Head Units] fra_dta:
Ok. I'll check it

Sorry for the off-topic ;)
[FYT Android Head Units] DrumVlado:
This app is amazing, thank you so much!

I just hate the look of the stock FYT firmware apps and I wish they could be replaced in the same way you replace the radio.

I wonder how difficult would be to replace the a/c controls, the player etc...?
[FYT Android Head Units] KoTiX2:
Modify an app changing the graphic is not that hard, there are tons of tutorials on XDA or on the web about it.

Changing the code need higher skills.

Anyway NavRadio is not a modified app.

It's a totally different app from the original. It only use some parts of the original one to take control of the MCU and radio chip.
[FYT Android Head Units] Closerm6b:
Hi

Radioproxy new version realised or not yet?
[FYT Android Head Units] KoTiX2:
There are no updates for radioproxy.

The problems were only in NavRadio.

You just need radioproxy1.2 and NavRadio 3.11
[FYT Android Head Units] Closerm6b:
Thanks for reply

I need radioproxy 1.2
[FYT Android Head Units] Pyteck:
How about the mode switching issues discussed earlier in the thread that the car button, when radioproxy is installed, does not allow the switching between bluetooth, radio, home screen, and phone?

Thanks
[FYT Android Head Units] Closerm6b:
Thanks for reply

I need radioproxy 1.2 apk
[FYT Android Head Units] surfer63:
post #1311.

@KoTiX2 : Please update post #1. It has radioproxy 1.1 but currently only announces 1.2.
[FYT Android Head Units] aiui:
It's actually a good idea, but I take very short trips each time I get in the car and I always have to touch the main unit, but I wonder if it wouldn't be possible for someone to make a launcher with an application on each side, just like that. split launcher on one side the map, and on the other the navradio+, but place a list of 4 or 6 favorites at the bottom of each window so that we can quickly, for example, exchange the navradio+ for the music player and leave the map as it was, this way whenever I start the car I will have the last two applications used as well as if I load it at home I will go to these two applications. I'm suggesting that, but I don't know if it's feasible to do something like that and I apologize if I'm giving a stupid idea but it seems like a good idea and I'd be willing to pay for it.
[FYT Android Head Units] surfer63:
That's the modded Launcher34. I removed the side pane, but you can just as well make it 50:50.

And @LLIyT_HuK already did the same for his PeaceOS launcher here. That one can also be made 50:50.

But's what is the use? You will again get a rigid launcher if you only allow 2 apps. And Maps will run in PIP mode with reduced functionality and reduced displayed info.

If you use Maps in a PIP window, you should never start with Maps. You need to start Maps full-screen BEFORE it has run in a PIP-window, or it will only work in PIP mode.
[FYT Android Head Units] aiui:
yes the map in pip mode is limited but it is not in split launcher, and if it works and in this way we either change the navradio+ for the music player on one side or the maps for the Magic world on the other, of course we would be stuck with just two applications but they would be the ones I wanted, and of course, we could open any application in full screen. I think it would be very useful but I don't even know if it would be viable, of course your solution also works but we have to interact with the head unit every time we get into the car and that becomes impractical over time and I travel a lot in big cities and use Wase to see the traffic situation and find out about speed cameras.
[FYT Android Head Units] surfer63:
This is completely off-topic here. There are multiple ways to do this. but too much to discuss here.
[FYT Android Head Units] marchnz:
You made sense of that waffle, well done :)
[FYT Android Head Units] KoTiX2:
Going back on topic... :D

I'd like to have some feedback of the new AF seek function form anybody who can test it on the road, please ;)
[FYT Android Head Units] Specy01:
I've updated RadioNav+ to ver. 3.11 from the play store (before I had the version prior to 3.07 if I'm not mistaken). So I installed RadioProxy 1.2. When I restarted NavRadio+ it also asked me if I wanted to uninstall the original radio. Unfortunately, I pressed on "not asking for it anymore".

Previously I had already manually memorized the alternative frequencies for my favorite radios
[FYT Android Head Units] KoTiX2:
Are you sure it didn't asked to "Replace the original radio" instead of "remove"?
[FYT Android Head Units] Specy01:
Honestly I can't say the right wording, I removed it too quickly (I was in a bit of a hurry), I'm sorry I can't be more precise 😞
[FYT Android Head Units] Closerm6b:
After installing radio proxy 1.2 ,on every startup its begin Seeking for Af and stop only it return to the same station
[FYT Android Head Units] ludditefornow:
Split screen issue is also fixed. Thanks.

I did notice a new bug. On start up of the FYT unit, I open NaviRadio and Google Maps (Maps is linked to the NAVI option).

Radio starts correctly. Switching stations with steering wheel controls does not work until I manually bring the NaviRadio app back into focus.

Not a big issue, but I just want to let you know. I will look to see if I can change the order of apps opening with the FYT firmware. If it was DOS or CMD batch file I would just add a timer for 1500ms in between launch commands. But i am still trying to get my head around Android.
[FYT Android Head Units] KoTiX2:
Your unit has a sc9853i CPU.

It means that is the older type of FYT unit that is not compatible with my app.

Only the newer FYT units with uis7862 and sc9863a CPU are compatible.

I don't know what atoto S8 version it correspond.
[FYT Android Head Units] surfer63:
He has an Atoto S8 Gen 1, which is indeed a sc9853i.

The Atoto S8 Gen 2 is a uis7862.

I have no idea why Atoto uses these totally misleading names. That might be common in car brands/models, but not in these kind of units.
[FYT Android Head Units] spludgey:
Another bug (not sure if it has been mentioned):

When I have a number of stations in my favourite and it switches from AM to FM or vice versa, it will not play the first FM station, it will continue playing the AM station. If you change the channel again, it will play the second FM station.
[FYT Android Head Units] KoTiX2:
Isn't this be solved with free version 2.19 ?

https://xdaforums.com/t/dev-new-navradio-ported-to-uis7862-fyt-devices.4387965/post-86346517

The full version will get this fix in its next v2.22 release.
[FYT Android Head Units] spludgey:
I download the one you linked a page back, but I didn't uninstall first (said it installed successfully).

I'll check the version tomorrow, but I thought I was running 2.19.
[FYT Android Head Units] ludditefornow:
The updated app fixed the issue for me. I did needd to uninstall the old first. I couldn't just run the new installer over the old app. It failed.

I also made a backup of my channel lists before I uninstalled.

@KoTiX2, I am seeing an obscure bug that sometimes when opening the app, the station defaults to 89.5 on the FM dial and not a previously used station or any other of my saved stations. 89.5 is not a channel in my region and is not saved as a station.

Have not yet figured out how to replicate this and it is not an issue to me. If a way to replicate the issue is found, I will let you know in case it helps in some way. It was only noticed because I am trialing a lot of different methods for launching apps so there is a lot of opening and closing.
[FYT Android Head Units] j-5:
I think that might be the original radio hardware kicking on, or the radio firmware defaulting to that station. Mine did the same thing randomly on boot. I added NavRadio+ to autostart to correct that, but your situation might be different.

(also, NavRadio+ seems to start twice now, I click my home screen at initial start, and it flips back to NavRadio+ after a minute)
[FYT Android Head Units] vonny571:
Bummer. Thanks for the response though. Good luck with the app.
[FYT Android Head Units] Gaugamela:
Atoto makes a mess with their naming scheme.
[FYT Android Head Units] KoTiX2:
Never say never!

i did a quick test with surfer63 and with surprise of both of us everything seem to be working just fine even on your type of unit.

Please confirm that is ok on your Atoto S1 too with this:

DOWNLOAD NAVRADIO FREE v2.20 from GDrive

or

DOWNLOAD NAVRADIO FREE v2.20 from Dropbox

Tomorrow a new v2.23 version of NavRadio+ will come out on Playstore:

- removed temp for not MTC devices

- fixed fonts in settings screens

- on TopWay units the app now close on audiofocus lost

- unified dropdown notifications and metadatas

- added verification of installed Hal9k ModService and prevented its interference

- added FYT units with sprd9853i ed sprd9863a(UIS8581) cpu to supported list
[FYT Android Head Units] vonny571:
Sweet! I'll check it out after I get off work.
[FYT Android Head Units] surfer63:
Note that the new low-end FYT units sc7731 (uis8141e) are 100% compatible with the sc9853i units on java level (AllApp.pkg) and hardware level (not android CPU/system). Now that your app also works on sc9853i, it should also work on these sc7731 (uis8141e) units.

I don't know anyone with such a unit though.

EDIT: These units mostly have cheap FM chips without RDS.