Please post a picture of the system information screen of your unit
showing the MCU number.
Please post a picture of the system information screen of your unit
showing the MCU number.
He has a uis8141E. Does your navradio apk support that?Ok. Please post a picture of the content of the root of USB disk.
Possibly, if you have it, post a link to the firmware for your unit.
The app itself works wonderfully! All features appear to work great on it. It tunes to different stations, I can preset everything, etc. AM and FM both work, and the logos work great after downloading.
The contents of the thumbdrive are exact as you specified in the second post.Ok. Please post a picture of the content of the root of USB disk.
Possibly, if you have it, post a link to the firmware for your unit.
If this is the root of USB and it's not a the content of a folder, then i need a copy of your firmware.The app itself works wonderfully! All features appear to work great on it. It tunes to different stations, I can preset everything, etc. AM and FM both work, and the logos work great after downloading.
The contents of the thumbdrive are exact as you specified in the second post.
View attachment 5914035
It is in the root directory. I'll work on getting the firmware for you tomorrow (it's late here in California). Thanks!If this is the root of USB and it's not a the content of a folder, then i need a copy of your firmware.
Unless ZHAN have changed something in the firmware (like Teyes have done in its 2022 firmwares), there is no reason to not starting the update script.
I beleive this is the last Test: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.
Thank you. Indeed it works as expected nowI beleive this is the last Test:
Dropbox - File Deleted - Simplify your life
www.dropbox.com
(The Automatic sensitivity switch was inverted)
Please let me know if it's all ok now![]()
Tomorrow will come out the full version with the fix.
I've also want to thank you and I've really appreciate that you immediately working on the user suggestions, fixing the issues and making your great app better for all of usTomorrow will come out the full version with the fix.
Thx for your help man. I really appreciate it
![]()
For "Full version" i mean the paid PlayStore one. So yesI've also want to thank you and I've really appreciate that you immediately working on the user suggestions, fixing the issues and making your great app better for all of us
Will the fix be available also for the paid version from the Google Play?
I have an additional question about this scale. Earlier one user used to name the 0-100 scale as a "km scale" - is this "function" really represents the amount of the kilometers (+/-) of the signal sensitivity? Or was this simply misnamed?
I have an idea to unifying the scale to reflect reality more and be clearer (more understandable) for the user. Right now the values range 140-255 looks more like the remnant of the back-end work than the final front-end representation. Unifying the scale may be more user friendly I think (eg. 0 - super sensitivity, 100 - lowest sensitivity, or better vice versa, with greater steps like 5 or 10). That's is just my thinking because I am a half-manual half-automated software tester so that's my everyday think-view from the end-user side on the back-end codeFor "Full version" i mean the paid PlayStore one. So yes
km?? Absolutely no!
It's just a value that the MCU use to set the sensitivity in the radio chip.
In the code of the original app i can see that depending on various models and radio chips, this value can be 50, 100 (for my unit) or in your case 255.
The original radio app is still the same since the very first fyt model, then they added code to support the new models from "Sofia" units to latest UIS7862 ones.
This is the main reason of the confusion in the code.
Well, now that i understand correctly how it work for my and your model i could make it in anyway i like.I have an idea to unifying the scale to reflect reality more and be clearer (more understandable) for the user. Right now the values range 140-255 looks more like the remnant of the back-end work than the final front-end representation. Unifying the scale may be more user friendly I think (eg. 0 - super sensitivity, 100 - lowest sensitivity, or better vice versa, with greater steps like 5 or 10). That's is just my thinking because I am a half-manual half-automated software tester so that's my everyday think-view from the end-user side on the back-end code
This is just a suggestion of course.
Hello. Why don't you try this thread apk? "NavRadio+" is pretty awesome. Just install it from playstore. Your unit has to be a FYT model (UIS7862 or sc9853i).hello colleagues, please if anyone has the original radio software, I deleted the original software and I don't have it anymore...backup_radio_apk please...
No, you can't go back.I haven't had a chance yet to download the firmware, but I updated the app this morning (I saw there was an update in Google Play), and now I'm having major issues with the app. It started with the app crashing when I would use the steering wheel buttons to switch between my favorite stations. Then, as the day went on, the app now crashes completely when I load it. The radio will start playing, and immediately the app crashes. I have sent a crash report to google (which I assume you get as well?). Is there a way to go back to the previous version?
If you own a Joying, try selecting Waze in the settings-general-Navi app. Additionally, turn on the GPS Mix in settings-general.For the past week or so, the NavRadio+ sound cuts off whit Waze. For example when I go over speed limit, some notification from Waze etc.
But when Spotify in the background playing, no such issue. It goes a bit quieter I hear the Waze and then everything is back to normal. Used to work same with NavRadio+.
Maybe I have changed some setting in head unit but I think not. So is this a bug from NavRadio or Waze or?
That was praise for you
Sorry guys, RadioProxy was a quick mod of MusicProxy and in this first release I left by default to run only the full version of NavRadio+.Hello @KoTiX2,
I've tried your FYT_RadioProxy with the Free version of NavRadio but it doesn't seems to work as shown in my video.
I will try with the paid version today but my dad has exactly the same car and HU as mine and he will not pay for an application as good as it can be (old people doesn't think as us).
View attachment 5993413
Thanks sir @surfer63 ! Actually the source you provided me kind of evidences what I was suspecting of ..