General Medeke/Navifly 7862
- Thread starter wmccann2
- Start date
it can be replaced with the same one on the left, but you have to uninstall the old one
Hi,
I had the same issue once I tried to wipe config.txt with a script in lsec_updatesh. After that I just did a new update/installation without that script and it fixed.
I think the radio is in apps in AllAppUpdate.bin, you have to replace it with another before installation
So, if I manage to change the ribbon and cut off the internal microphone, will it work? I am not familiar with hardware changes like that. But the question is why with the previous update I had from 2021 it was working? I remember I always had both microphones listening, but with the software switch on, the external microphone was louder, so I could use them without problems. If I could find somehow the setting or configuration that made the previous update to work, maybe I could use it here too, without any hardware hack
On the older FYT devices without a dedicated mic port, the internal and external mic are always on. It is hard wired this way and it cannot be changed with software.
That's why many users modify the units to disable the internal mic.
The software switch for changing front/back mic does NOTHING at all for devices that don't have the newer dedicated mic port on the rear.
It doesn't turn anything off or make anything louder.
If you think it was louder before with the switch then it is probably just confirmation bias. The brain believes what it expects.
On 4PDA ( Just Google 4PDA UIS7862 ) there are modified versions of the original radio app available, which even include logos. But its on your own risk.
Thanks, I put the highlight ......NavRadio !!!
Attachments
Last edited:
Thanks for the answer. It was louder, really. I was using microphone since 2021 for calls all the time, google search, maps, a few assistants, etc. After the last update (Aug 2022 and Nov 2022, I have tried) none of those works with microphone. In BT calls it listens nothing and in other apps it is very weak...
The settings containing the external/internal (back/front) microphone switch was not released until August 2022.
There's no way you could have been using that option since 2021.
Your microphone may have been louder before you performed an update but it was not because of the software microphone switch. It does nothing on units without the relevant hardware.
By "older FYT devices" you mean old revisions which were produced before mid 2022 or all devices which aren't M6Pro?
I mean all devices that aren't the M6Pro and the new Teyes CC3 2k.
These newer devices have a separate, dedicated mic port on the rear.
On devices like the Mekede M500s, M600s and the Teyes CC3 there is no dedicated mic port on the rear. It doesn't matter when they were produced, they didn't revise them in mid 2022.
On all of these devices, no matter the manufacture date, the internal mic is always on. The external mic is always on (if connected).
The setting labelled "Back Mic Switch (Front Mic / Back Mic) only works on these newer models with the dedicated mic port.
You might call it a bug. I call it a design flaw which they fortunately now (6 months ago) fixed. That is is not backwards compatible is because it is hardware.
You can also request a new motherboard. That was more common some years ago, but if you request it they might send you a new one. Of course it will cost money
Hi all. Has anyone experienced poor audio quality when streaming from phone via the bluetooth app? It sounds very compressed. I have an M600s with the latest firmware from the Mekede website. I have searched extensively but have not yet found a solution for my device. Could it really be that the module is of such poor quality?
EDIT:
Through 4PDA I was able to learn that you can switch to using the internal BT module by setting 'sys.fyt.bluetooth_type=0' in config.txt. This allows for use of the AAC codec which can be set under developer settings which solved my problem.
Now, it seems that the BT app cannot see devices but you can pair up from phone side. Also, other codecs such as LDAC or aptX do not seem to be supported.
I have not observed any issues from switching module so I am curious as to why they added a second module in the first place.
Anyway, I hope this can possibly help others in the future.
EDIT:
Through 4PDA I was able to learn that you can switch to using the internal BT module by setting 'sys.fyt.bluetooth_type=0' in config.txt. This allows for use of the AAC codec which can be set under developer settings which solved my problem.
Now, it seems that the BT app cannot see devices but you can pair up from phone side. Also, other codecs such as LDAC or aptX do not seem to be supported.
I have not observed any issues from switching module so I am curious as to why they added a second module in the first place.
Anyway, I hope this can possibly help others in the future.
Last edited:
No, but why not stream directly from the headunit? I have used that feature in Bluetooth one time, and it works just fine. But the volume is partly controlled by your phone.
Thanks for the response. Streaming through the unit indeed does work good but I know my girlfriend would prefer to use the BT audio feature. I just did not imagine that compression would be the challenge here.
Just to notify anyone subscribing to the thread that I managed to find a solution for this
Which wasJust to notify anyone subscribing to the thread that I managed to find a solution for this
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3Yay! I did a thing!
With a bit of dutch courage, I had a go at the modification & although it was a right bugger to do, I got there in the end. I made a video for others to see, I've set it as unlisted on youtube for now because I noticed an error I appear to have made twice. I said earlier that the spacializer didn't work & I was wrong. I only noticed when I watched the video I made that when I tested the HDMI I used the "surround" option in the mixer. For the other apps I used the "field "option. I must have made the same mistake when I tested on my workbench, because I've been & checked & when using the "field" option it works fine. So, mod works 100% as far as I know.
Here's the vid for those who are interested:2
Nice you fixed it.
However, being Dutch I always feel slightly insulted when someone mentions "Dutch courage".
So here a little history why Dutch courage is actually "English calm down and reduce fear for".
https://en.wikipedia.org/wiki/Dutch_courage (the short, more positive version)
And why the English should be thankful for their gin.2
Maybe you have some battery issue. START STOP often stops working when battery voltage drops under 60% or lower, depend from a car. I'm guessing you spent quite a bit of time in a car with not running engine while you were installing and testing the radio. If the voltage drops below a certain level, the car starts to turn off the consumers of electricity, but the car continues to start normally. I assume you have an AGM or EFB battery in your car. At least it should have it according to the START STOP function.22
Thanks for the responses. I was getting around .08 Mbps down, .5 up. I ended up doing a reset on the headunit and it works much better now. -
65
As well as connecting the fan to the harness you also have to switch it on in the UI. In Settings go to Device/Sound/Amp OnOff set to On to have the fan on. Looks like there isn't proper integration for the fan so they just use the switchable amp power output to drive the fan.5
It is definitely suggested especially if you live in (sub-)tropical areas. The fan is really quite and keeps the temperature about 20 degrees lower (in my case).
And with regard to "UI looks different": I just created a modded firmware based on the latest Mekede in combination with the latest core/kernel I could find, that contains all 11 launchers that are available for the several FYTs around. I currently use Nova Launcher. My current Mekede firmware (build date 18 September 2021) contains 3 launchers: 2 of them look very nice, but that is only eye candy. Real functionality is not so great. I will simply test all 11 and might get back to Nova again. I will also test if my modded firmware is "sharable". I know simply how to overcome issues, so I want to test first.
I also use something else than the "twipe_all" or "twipe_data", that removes everything (all) or all data including your 3rd party installed apps including their settings. And only because FYT still doesn't have a good update protocol for their own apps after 6+ years.
My "post upgrade" action is only removing all FYT related data/cache/profiles.
But first test if that really works4
Hello there. I've already test it. Me and my girlfriend usually travel together so I have to choose between her phone and mine (FYT unit only connects to 1 phone at a time). So she's connected and all her contacts appear (and I store it) and as soon as I connect my phone the list is swapped and I cannot see her list anymore.
It's a good thing. And other fact is that the unit first pairing is always to the last paired phone during switch off (assuming that that phone bluetooth is enabled).3I finally received my Mekede uis7862 unit for my Octavia 2015, but it doesn't fit correctly. It needs to be pushed in and "click" tight. That is the system VW/Skoda/Seat/Audi use after 2013. That doesn't work and therefore it can easily fall out of the dashboard.
I did a test drive this afternoon and as such the unit functions fine, but the fact that it is completely loose and can fall out of the dash is an extreme annoyance after having waited so long.
EDIT: And the 5GHz WiFi reception is a big deception. I have to park my car almost inside my nearest WiFi Mesh AP, while I have a perfect MESH WiFi network.
