General Medeke/Navifly 7862

[j0hn83]

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.

 

[Johnny#C#]

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.

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...

 

[j0hn83]

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.

 

[marjanoos]

On the older FYT devices without a dedicated mic port, the internal and external mic are always on.

By "older FYT devices" you mean old revisions which were produced before mid 2022 or all devices which aren't M6Pro?

 

[j0hn83]

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.

 

[marjanoos]

Thanks. I wish at least one chinese company would put an effort to make device without such irritating bugs and really refined. I would pay more, but there's no choice.

 

[surfer63]

Thanks. I wish at least one chinese company would put an effort to make device without such irritating bugs and really refined. I would pay more, but there's no choice.

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

 

[evilution.dk]

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.

 

[DexterMorganNL]

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?

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.

 

[evilution.dk]

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.

 

[evilution.dk]

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.

Just to notify anyone subscribing to the thread that I managed to find a solution for this

 

[marchnz]

Just to notify anyone subscribing to the thread that I managed to find a solution for this

Which was

 

[Moon2]

Which was

Its in his original post as an edit (3 posts above his latest post).

https://xdaforums.com/t/medeke-navifly-7862.4248969/post-88290735

 

[marjanoos]

The second problem is that the loading of the camera application takes too long. From the moment of shifting into reverse it takes 3-4 seconds, and in my opinion it should take 1 second

Did you manage to deal with that delay?
I hope you will come back to the forums and reply me

@DexterMorganNL you wrote that delay is inevitable but actually it's not. I had MTCE device previously and reverse image was instant (and I know that's different device). Here it's about 3-4 second which makes the reverse camera useless.

 

[DexterMorganNL]

Did you manage to deal with that delay?
I hope you will come back to the forums and reply me

@DexterMorganNL you wrote that delay is inevitable but actually it's not. I had MTCE device previously and reverse image was instant (and I know that's different device). Here it's about 3-4 second which makes the reverse camera useless.

Yes a delay, while starting the engine: not while the engine is running, than there is no delay between going into reserve and the camera. The delay is because the headunit needs to wake from sleep.

 

[marjanoos]

There's no difference in my case. When I put the reverse with engine running, 3 seconds between reverse screen is showing.

Also was anybody able to install updates for those integrated app store apps? Like canbus, protocol etc.? When I try to install them, I get "app wasn't installed".

 

[DexterMorganNL]

There's no difference in my case. When I put the reverse with engine running, 3 seconds between reverse screen is showing.

Also was anybody able to install updates for those integrated app store apps? Like canbus, protocol etc.? When I try to install them, I get "app wasn't installed".

Only the Carlink, the others I didn't try to install and no that app store show some error. So it's not working somehow.

 

[Lakis_dj]

Which was

 

[marchnz]

The correct answer was: First post updated with details to resolve the issue.

 

[marjanoos]

There's no difference in my case. When I put the reverse with engine running, 3 seconds between reverse screen is showing.

For the record: I was dumb I assumed that if there's no camera attached, head unit would go into reverse mode as quick as if camera was attached (but with black screen only).

So when I thought "well, let's try to connect the camera" and I've found that image is showing instantly.