yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] danilaur:
Now it is ok, i unistall and reinstall
[FYT Android Head Units] marioti:
hi. Is there any chance to make it fit to nonFYT based HU, like this:

[General Discussion] QF001 (ROCO K706) Head Units with UIS 7862s (not FYT based) [read first post first]

Hello all, it seems that there are some QF001 owners out there but not much informations. So i will try to collect everything and put it at one place. The original manufactor is shenzhen jitu technology co. ltd. These units are sold from...

xdaforums.com

There is nothing so annoying like stock FM radio app in those HU
[FYT Android Head Units] KoTiX2:
I bought a qf001 unit to start working on it.

I just need to find time to work on it.

It will takes some months anyway....
[FYT Android Head Units] marioti:
Thank you, i'll wait for any progress on it
[FYT Android Head Units] r_dmitry:
через huawei app gallery, но оно там сейчас недоступно
[FYT Android Head Units] x X x:
Hello. So I bought the full version of the NavRadio and I have a really anyoning problem with searching for new FM stations using arrows. When I set the arrows to find nearest frequency with available FM station - every press on the arrow almost always stops at every one of tenth frequency, e.g. start frequency: 99,0 > single key press > frequency 99,1 > signle key press > frequency 99,2. Rarely the differences are greater (eg. 0,2, 0,3 between key presses).

There are three options to choose from in the General settings for the arrow key press:

1. Frequency small step +/-

2. Preset Station +/-

3. Search Next/Previous Station

The 2nd option works as expected (switching between saved stations) but 1st and 3rd acts as the 1st option.

I have trying to set the slider of the Manual adjustment of reception sensitivity for FM stations to randomized values (0, 99, 50, 20, etc.) without any effect.

This situation happens on the free and paid version of NavRadio.

In my stock radio app searching works as expected.
[FYT Android Head Units] KoTiX2:
..and what kind of unti do you have?

Form which country are you from?
[FYT Android Head Units] x X x:
I am from Poland. Device is Joying unit, model and version attached:
[FYT Android Head Units] KoTiX2:
Ok

I believe that you have set a wrong radio sensitivity or you have a reception problem. It's too sensible.

Which values did you set?

Try also using DX instead of LOC function when seeking
[FYT Android Head Units] x X x:
Right now I disabled the manual adjustments setting under Radio menu, the DX, AF and Stereo are on.

I set the arrows to single press to seek for the stations.

I am on the saved, worked frequency (great quality, stereo signal, 107,90 freq.).

Now after some additional testing I found that sometimes single press moves the frequency to the 107,80 (or 107,70), sometimes it moves to further frequency but stops on te frequency without any signal, sometimes it goes to the good quality frequency. It is not consistent at all. I will post the video of how this is working on my unit.
[FYT Android Head Units] KoTiX2:
Disable the AF that doesn't work on FYT units.

Set to manual the sensitivity settings and raise it up to maximum. When you seek for a station it shouldn't stop at all.
[FYT Android Head Units] x X x:
I have attached the video in my previous post.

For the following settings (AF disabled, sensitivity of FM set to 100) it is still seeking the frequencies witch are not existing (no signal), in low steps (mainly 0,10, sometimes greater), especially just after the good frequency was found. Video attached. As you can see the 89,50 freq is found when seeking forward but skipped when seeking backward.

Btw. what about this toast notification? Can we disable this? It is showing when the seeking is performed (it's duplicating the message on the app itself) and it's stacking every button press, so when single toast message is showing for e.g. 10 seconds, 10 presses on the seeking buttons forcing to show the toast message for 10 x 10 seconds.
[FYT Android Head Units] danilaur:
set auto scan,sensitivity of FM set to 1
[FYT Android Head Units] x X x:
No matter if I set it to autoscan or manual (by pressing the buttons) it is still working as on my videos.

Any other suggestions @KoTiX2 ? Maybe it is an issue?
[FYT Android Head Units] kolarov:
Hi @KoTiX2 ,

After updating to the latest version (2.85d) I noticed two problems:

- When the radio is started, the sound starts and immediately stops. In order for it to start playing, I need to change the station. I tried uninstalling and reinstalling the app, but the problem remained.

- The speedometer does not show how fast you are moving - it does not count at all.
[FYT Android Head Units] KoTiX2:
Please tell me which launcher are you using?
[FYT Android Head Units] kolarov:
I don't use launcher. The standard ones offered by my multimedia - No 10.

For the moment I use NavRadio+ as a launcher ;)
[FYT Android Head Units] danilaur:
KoTiX2 all new version cant update ok, tried to unistall and reinstall app, please fix this for beta testers, it is very frustrating !
[FYT Android Head Units] KoTiX2:
What do you mean by can't update ok??

Tomorrow I'll releasing a new standard version.
[FYT Android Head Units] danilaur:
all versions must be uninstalled and reinstalled, the application cracks after each update and lose all settings
[FYT Android Head Units] j0hn83:
I've done a dozen updates of this app without uninstalling and never once had an issue or lost any settings.
[FYT Android Head Units] danilaur:
Because you are not beta tester, all beta version, not stable!
[FYT Android Head Units] flaviocc:
Hi OP tks for the app....I have a problem:

I installed the vivid version to test (I want to test before I buy) and now I need to uninstall to make other tests....but I have an error and the app wont uninstall (package error).

Can you point what I need to do to remove the app? Tks.

My test is to use the FCC Launcher with original software radio (naviradio force close every time).

Tks.
[FYT Android Head Units] KoTiX2:
Why are you using the vivid version if you use FCC??

Vivid version of NavRadio is incompatible with FCC.

I have no idea why you cannot uninstall the app probably it's an FCC problem?

Try to uninstall it from the android settings instead of doing it from the launcher...
[FYT Android Head Units] flaviocc:
Bcs I tried Vivid first. That's the reason.

I tried from the system and get the same package error. I changed the launcher to Nova launcher (btw the version works) and same result.

Edit: cleaned cache, data etc and the app is there.
[FYT Android Head Units] KoTiX2:
Man i have no idea except do a factory reset or if you have root access delete manually the folder data/data/com.navimods.radio_free
[FYT Android Head Units] flaviocc:
ok. dont have root access, I will figure out what I can do here. Tks.
[FYT Android Head Units] surfer63:
Did you already try to reinstall the same version? and if that is successful, then uninstall it again?
[FYT Android Head Units] flaviocc:
Not yet.

I did not return to the car yesterday. I’ll try later. Tks for your suggestion.
[FYT Android Head Units] loz.misha:
have the same issue.
[FYT Android Head Units] KoTiX2:
Please post a picture of the system information screen showing the MCU number.
[FYT Android Head Units] KoTiX2:
Please post a picture of the system information screen showing the MCU number.

Thx.
[FYT Android Head Units] louforgiveno:
Sorry to hijack......hoping you could help me identify my unit (confirm i can use fyt mods etc)

Thank you

(Bought new on ebay, listing said mekede, thought it might be the M200s or a Winca?)

Baseband Version

FM_Base_18B_W21.12.3|sc9873A_modem|03-24-21 03:14:08

MARLIN3E_TRUNK_W21.13.3|uwe5623_marlin3E_usbhub|03-31-21 01:19:48

Build Number

QP1A.190711.020 release-keys

System Info

App 1280x720 2021-11-10 09:57:06

CPU Info

CPU:UIS8581A Octa-Core 1.6GHZ@2.0 GB(Memory) + 32GB(Storage)

MCU Version

2021.10.09 10:12:29 YIN_53_L6315_G23P48F64_E60_V:1.0

Bluetooth Version

BLINK_2161_RELEASE/2021:09:14:19:38:05_blink
[FYT Android Head Units] KoTiX2:
Yes, it's a fyt unit with 8581 cpu
[FYT Android Head Units] louforgiveno:
Thank you!

And "Yin_53" is the reseller id? Does that imply where i would find the factory software? I've got a lot to learn, 1st thing I'd like to do is create a full backup or at least find the factory software before i start tinkering, but the Ebay seller is just a re-reseller so they don't have it.

Maybe things will get clearer as i dive in, but if you have any insights it is greatly appreciated.

Thanks again
[FYT Android Head Units] loz.misha:
Here, sorry for bad quality, but should be readable.
[FYT Android Head Units] x X x:
Here you go.

Btw did you saw my videos attached earlier?
[FYT Android Head Units] surfer63:
https://xdaforums.com/t/general-fyt...q-a-mods-tips-firmware.4396339/#post-86349167
[FYT Android Head Units] KoTiX2:
yep, i saw it.

can you make a video using this free version, please:

Dropbox - File Deleted - Simplify your life

www.dropbox.com

I only improved the messaging to better understand when start and stop the seeking.

It looks like both of you guys have a joying MCU while i have a NOR.

Maybe something change in the handling of sensitivity...
[FYT Android Head Units] loz.misha:
Recorded small clip, please check
[FYT Android Head Units] x X x:
The toast works better than before, even for multiple pressing the seek buttons. Still I think that while you displaying the message about seeking in the GUI directly there is no need to duplicate it in toast. Imho it should be removed (the toast for seeking) or customizable in settings.

As you can see on longer video the seeking function works better now - it is related to place where I am atm, there are more good quality stations with strong signal. But still the behaviour of seeking buttons is strange - when the proper station is found - next press on the seeking button almost always causing the frequency to move 0.10 step instead of seeking for another good quality frequency. Second press is needed to seek for another good quality frequency. The seeking tuning option is disabled on these videos.
[FYT Android Head Units] KoTiX2:
Why are you modifying the basic version??
[FYT Android Head Units] x X x:
What do you mean? The green screen is your apk file from post #910, the purple one is the NavRadio+. I've attached the videos from both versions to show the differences in displaying the toast messages.

The seeking works exactly the same on both versions.
[FYT Android Head Units] KoTiX2:
i was just wondering why do you see the stations logos on the free version??

Anyway, which radio region do you use?
[FYT Android Head Units] x X x:
Ou :D No, I was not modified anything. The stations list was created in NavRadio+ then imported to the Basic version (the attached apk). So it looks like some kind of issue ;)

I am on Europe region. I am from Poland.
[FYT Android Head Units] KoTiX2:
Oh ok that's explain it :)

In the next days 'll send you guys some free versions to test before release the full version.

Thx for your help ;)
[FYT Android Head Units] KoTiX2:
Hi, please try this version:

Dropbox

www.dropbox.com

i fixed some stuff here and there...
[FYT Android Head Units] x X x:
Thank you! I see toast are gone, nice :) It is a big game changer for me!

About the seeking I've attached three videos:

1. Fresh install, default settings, manual tuning is turned off.

2. App memory cleaned, default settings, manual tuning is turned on with default settings (30 for FM).

3. Stock Radio app for comparison. The seeking is performed by press and hold the button(s). It is sometimes stops at the frequency with no signal at all, but overall it works better.
[FYT Android Head Units] KoTiX2:
Uhm... Looking at original app it doesn't work good either so i believe it could be something related to hardware or firmware.

On my unit the seek function work much better than that with NavRadio and original app too.

I cannot reproduce the problem as it doesn't happen on my unit and honestly i can't think of anything that can help fixing it.

I'll see if I can add a delay somewhere but i can't guarantee anything..
[FYT Android Head Units] x X x:
I will made some more testing tomorrow and post the results. I am on the center of the city right now and the results could be differ (videos were recorded in the country side). I know that the original app is not great at all but I feel it responses better anyway. In some points of the video the behaviour of the pressing and holding could be incorrectly discovered by the ui because I was looking directly to the phone screen while recording so there could be some miss-press&holds ;)
[FYT Android Head Units] KoTiX2:
In the original app if you set the maximum sensitivity level ( means that it should receive only station with very high signal) does it stop anyway?
[FYT Android Head Units] x X x:
As far as I remember there is no such option. I will check this today evening (no access to car atm).
[FYT Android Head Units] KoTiX2:
In the original app you can set the sensitivity too.

I'm 100% sure of it because I copied it from there.

Set it to manual and rise it up to maximum ad see what happen..
[FYT Android Head Units] x X x:
You have right, the sensitivity option is present (the scale is different) and when I set it to maximum 255 value no stations have been found.

For the opposite side this option in NavRadio seems to not working at all, or the scale is to short (is this percentage presentation of the 0-255 range? Or still a byte but trimmed to 100?). I have attaching two videos: one with manual turned on and raised high up, one with manual disabled. The scanning looks almost the same if not the same.

And yes, for both apps and some stations seeking stops just after 0.10 so it could be hardware related.
[FYT Android Head Units] KoTiX2:
Can you send me the original radio apk that you have in your unit?

If you have used my tool to remove the original app it should have made a copy in a backup folder on usb.

Indeed the problem is the sensitivity value scale!

In the original app i have the default value for AM and FM is 22.

What are the default values in your original app?
[FYT Android Head Units] x X x:
Default values are:

- FM: 182

- AM: 168

.apk attached :)
[FYT Android Head Units] KoTiX2:
Please i also need the build.prop file from your firmware
[FYT Android Head Units] x X x:
Where to get it?
[FYT Android Head Units] KoTiX2:
nevermind...

Please try this version:

Dropbox - File Deleted - Simplify your life

www.dropbox.com

I haven't tested it yet but you should see in navradio settings the manual sliders set up to 255.

Then when you do a seek it will show up a popup with some infos that i need:

persist.fyt:

SensMax:

Sens_Default:

ro.fyt.fmsens:

please report me back what it show and how it goes ;)
[FYT Android Head Units] x X x:
Hi! I've installed this version and mentioned slider is not here, just the regular AM and FM with 0-100 scale (by default set to 30 for FM and 40 for AM).

About the info from the toast:

persist.fyt: 182 140 255 168 140 255

SensMax: 100

Sens_Default: 22

ro.fyt.fmsens: 0

For both seeking forward / backward.
[FYT Android Head Units] KoTiX2:
ok i'm almost there...

persist.fyt.fm.default: 182 140 255 168 140 255 means:

FM default 182, min 140, max 255

AM default 168, min 140, max 255

try this:

Dropbox - File Deleted - Simplify your life

www.dropbox.com

you should have the settings range between 140 and 255 so you should be able to set 182.

I'm still fighting a little setting the default values programmatically...
[FYT Android Head Units] x X x:
Good evening.

With this version the setting for manual tuning is turned off by default and showing the same default values as earlier (30 for FM and 40 for AM) but sliders for both are placed at the beginning of the scale.

After turning manual on I was able to move the FM value to the 255 as a last one, so for testing purposes I set it to max and check the seeking. It was not working as it should (no stops at any frequency) but the seeking seems less sensitive for bad signal freq. When I went back to the manual adjusting the slider went back to the left side of scale and shows 100 value for FM and still 40 for AM. I have set maximum values for both FM and AM this time (the 30 for FM is not available - 100 is the first value), check seeking, went back to setting and again - both sliders are on theirs left position with value 100 (AM too).

We are on the proper way to adjust it to my device ;) Good job!

Sorry, no video for today. I hope everything given above is clear enough for you.
[FYT Android Head Units] marjanoos:
I have Mekede M6 Pro with Vivid Launcher (special version for NavRadio+). My default radio app is disabled (changed name, added .bak). @mariodantas kernel installed.

I have NavRadio+ latest beta from Google Play

I have also radio fascia with dedicated climate control panel (canbox is inside that) and hardware buttons with "FM" button and "Menu" button. The first one triggers FM radio app obviously and the second one triggers the main screen.

I experience no sound for a short period of time:

1. I'm on the main screen and radio is turned on, playing OR I have radio app is on the main screen and I click "Menu" button

2. I click "FM" button OR touch the screen on the widget with radio player

3. There's no sound for about 3 seconds and then radio is playing again

here's video

navradio

New item added to shared album

photos.app.goo.gl

I know that AF don't work on FYT devices but what happens when this option is turned in NavRadio+? While being in my city (Warsaw), sometimes I have heard static noise for a second. Now I'm in Germany and instead of static noise I can hear some other station for a second if AF is marked on.

Also I've notice that when I was driving through Poland to the Germany, I started my ride using FM Radio, then changed to Spotify. And twice NavRadio was turning itself on again and Spotify music was stopping.
[FYT Android Head Units] AviationPhotographer:
Hello! I purchased the full paid version today, what a great app. So much better than the stock one, I'm going to try and disable the stock app with your USB drive files later today. One thing I noticed is that the track/artist information for what's playing seems to truncate and not show the entire thing or scroll. Is there a trick to getting this to work? I can see part of it, but only a few characters no matter what station I tune in to.
[FYT Android Head Units] KoTiX2:
That depend on the quality of the signal and onwhat the station broadcast.

If l

You live in the USA you can enable the "Concatenate RDS text" option.
[FYT Android Head Units] KoTiX2:
I hope this will be the final version:

Dropbox - File Deleted - Simplify your life

www.dropbox.com

let me know ;)
[FYT Android Head Units] danilaur:
KoTiX2 i whant to ask you whant to make a video player ?
[FYT Android Head Units] marjanoos:
Excuse me but what for? There are many many video players in the market and it would be better that @KoTiX2 would focus on radio app, which is rather niche app.
[FYT Android Head Units] danilaur:
yes
[FYT Android Head Units] marjanoos:
Another bug related to Vivid launcher: if I open phone app and use dialer (radio stops playing) and after phone call radio doesn’t come back neither doesn’t if I leave dialer without a call.
[FYT Android Head Units] danilaur:
use this launcher DoFunAutoUI-V7.6.6 (many themes)
[FYT Android Head Units] KoTiX2:
I'm sorry but i found a small bug in test3 version.

Here is the fixed one to test:

Dropbox - File Deleted - Simplify your life

www.dropbox.com

The sensitivity settings should go from 140 to 255 byt i couldn't get the minimum value to apply correctly so the range is 0-255.

Default value for FM is 182 and for AM is 168

Activating LOC it increase the sensitivity level by 25 only for FM, so it's like if you set 182+25= 207

I don't know if 25 is a good number, i'll need a reply from you guys if you need more or less for the LOC/DX function.

Of course I'm talking only of those Joying units that use this sensitivity range.

All other models use the usual 0-100 range with default values FM:30 and AM:40

There are other default values in the code of the original app but i will not cover every single FYT model because i cannot test them all. Anyway setting 22 or 18 or 30 doesn't really change much.

I'll have 2 days off now so other fixes or the fixed full version will come during weekend.

Ciao ;)

Edit: to answer the question about making other apps... I really don't have enough time for anything else beside NavRadio.

I'm not even a real programmer. I'm just an old kid who like to play with code in his spare time :D
[FYT Android Head Units] WarSpaz:
I must say, KoTiX2 really seems service minded and should have praise for that :)

I dont even have the bought app yet since im waiting for my FYT unit, but as soon as i get it i will disable the stock radio and buy this one!
[FYT Android Head Units] danilaur:
"Anyway setting 22 or 18 or 30 doesn't really change much."

if i set 1 for fm and 1 for am it is ok ?
[FYT Android Head Units] KoTiX2:
No, it's not ok. It will stop the search at every low signal.

If you want thatbthe search stop only at good quality stations you need to set the correct value for your unit.

Ok my unit that have range 0-100 a value of 30 is ok.

On joying units that have range 140-255 the default value is 182 so anything around that is good.

Read the previous posts about all this matter
[FYT Android Head Units] KoTiX2:
Correct me if I'm wrong but that happen with original radio app too.

Isn't it?
[FYT Android Head Units] danilaur:
ok, and set all other than AF for best signal outside the city 20-30 km?

mine is like you 0-100
[FYT Android Head Units] x X x:
I've tested both. The scale is indeed from 140 to 255 for FM and AM, and saves the value which I set. But imho changing the value doesn't affecting the sensitivity at all. The 140, 182 and 255 works exactly the same - receiving the stations in similar way as in my default app.
[FYT Android Head Units] KoTiX2:
The purpose of all this work was to make NavRadio work at least like the original app.

Can you confirm me that this has been achieved?

At this point all i need to know is if NavRadio act exactly in the same way of the original app or not.

If setting 255 in the original app (or in NavRadio) the seek function still stop to bad stations (stations with low signals), then the problem is also in MCU or radio chip and it's out of my control.

Please be sure to test both apps in the same way and i the same contest/area.

One small note that i just thought about and could cause a bug right now: don't set 255 and enable LOC in the same time otherwise it will go out of range and it will force load the default sensitivity value.
[FYT Android Head Units] KoTiX2:
AF doesn't work!!!

Don't enable it.
[FYT Android Head Units] marjanoos:
Haven’t tried with original app. But only on Vivid launcher.
[FYT Android Head Units] x X x:
I've tested again the FYT4 version and found where the issue with 255 value is coming from. The behaviour of switch to enable/disable manual tuning is inverted. When option is on set up value would not affect scanning sensibility. But if you set the value to e.g. 255 and turn the option off (to force it act with default value), the sat up value will affect seeking sensitivity and for e.g. 255 value - stations won't be found. If you change the value to the lowest one - 140 - and turn the option off again - stations will be found.

I've recorded a complete video presenting this issue.
[FYT Android Head Units] AviationPhotographer:
I tried running your original radio app renamer with a fat32 USB. I set the files and folders exactly how it was mentioned and plugged it into my Toyota Prius. The system said 'installing external storage', but I never got a 'start' button. I tried restarting the head unit, but same thing. No start button. Any ideas?
[FYT Android Head Units] louforgiveno:
Have you ran the DocumentsUi file (it allows data to be written to external devices) i assume this process requires that.
[FYT Android Head Units] AviationPhotographer:
Forgive my newb-ness, but how does one go about doing that? Is that an apk to install/run?