yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] mariodantas:
Really I don't know, is a simlink, will try to mount tonight to see if it is possible to backup, the will be back to you with (or without) results !
[FYT Android Head Units] gergenam@gmail.com:
Hi guys! I have a device EKIY T900 4/64

I previously connected the SD card module (Part1, Part2)

There is such a problem: after exiting from sleep mode, the SD card module is sometimes not detected.

Does anyone have any ideas? Please help me to solve this problem if possible.
[FYT Android Head Units] j-5:
I would just use the WiFi on that unit.
[FYT Android Head Units] sagipael:
Hi,

I have tried it today, but i still got the same error. (see attached)

Any ideas how to make it work?

Thanks,

Sagi
[FYT Android Head Units] surfer63:
Strange. I tried it on my old sc9853i, which is exactly the same CPU, just a bit older, and there it works (although I can't use the allappupdate.bin on that machine).

Can you try in a terminal what the command "more /proc/cpuinfo" does?
[FYT Android Head Units] matt205gti:
So, I've found a DAC that outputs 4 analog channels from the optical out on the Navifly and can be powered by USB, so all good there.

I think the only issue blocking me putting it in the car now is that the USB HDMI capture device i use tends to drop off the OTG interface and requires removing and reconnecting before it can be used.

On my PX5 unit, this never happens :(

Really anything USB seems flakey on these, had it for nearly a year and still can't get it working properly.
[FYT Android Head Units] hzn942:
I have mekede M600s, everything works great except carlink, I use carplay all the time, but I cannot find a way to turn carplay into dark node when headlight turned on, this is really annoying when driving during the night. any idea of how to fix it?
[FYT Android Head Units] sagipael:
Hi,

See attached.
[FYT Android Head Units] surfer63:
This is not what I had expected. It fails to detect the name for the processor family and so on.

I am lost here as well.
[FYT Android Head Units] kangyoon20:
Hi guys,

i just bought a new 7862s (no brand) and connect to an active subwoofer via green rca out,

but having these issue

- Bass Setting in Equalizer doest not make any changes to my subwoofer

- Bass Filter for front speaker also filter out subwoofer frequency

- If i put Fader all the way to Rear only, the subwoofer together with front speaker had no sound

I read through the forum for hours and saw some mentioned the Equalizer for Bass is broken,

and someone mentioned the latest Joying firmware had fixed that.

So is there any solution currently for my model Equalizer bass setting problem?

my main objective is to adjust front speaker and subwoofer separately,

currently the front mid cant handle the low end freq well

Below i attached my player info, HWget_info zip and the equalizer

these subwoofer setting in equalizer make no changes to my subwoofer sound

i wanted to cut out <50hz freq to my front mid, but it also cut them for my sub
[FYT Android Head Units] Specy01:
Days ago I downloaded from the site of Mekede, the latest firmware related to my Navifly M700S UIS7862 9 "8-128GB, this has the IDmanufacturer identical to mine ie 116. Sunday morning I installed it but, as some of you know I continue to have the problem of LED daytime running lights that randomly turn on / off during the day. Today checking the updatecfg file.txt I realized that it has the command twipe data, so I wanted to change that command with twipe all with Notepad++. I reinstalled the firmware with this new file and I end up with a problem. The first thing I wanted to do was to delete the floating icon of the "Digital Wellbeing" app By clicking on it, the app does not open but opens the air conditioning app, as in the picture. I tried to delete the app from the settings from the App item but I can only force the stop and disable but despite this the icon remains on the screen and makes me see the air conditioning. Any ideas? Where am I wrong?
[FYT Android Head Units] surfer63:
It is not the wellbeing app, it is the softtouch app having the hand with the finger pointing up.

You do not click the icon, you go to apps and click that softtouch app and uncheck all options.
[FYT Android Head Units] Specy01:
Thanks surfer. Later I get back in the car and do it.

As for twipe data and twipe all, I didn't see any difference, except that in the NavRadio + installation I lost the settings. Before installing the firmware I had removed the USB drive and after putting it back navradio+ I did not find my settings saved I think on the USB drive. Can you tell me why? Maybe @KoTiX2 know something
[FYT Android Head Units] KoTiX2:
NavRadio settings are saved on internal memory not on USB, maybe that's why you don't find them.
[FYT Android Head Units] surfer63:
For the uis7862 there is no difference anymore between twipe_all and twipe_date with the super partition scheme.

twipe_date wiped the /data partition, but not the /oem partition

twipe_all wipes the /data, the /oem partition and the /sdcard, which is actually the internal memory and not some USB-card..

However, since the use of the super partition, the /oem partition is always wiped as it is part of the super partition which is read-only.

And as most apks store their config in /data/data/<app name>, the settings of the NavRadio are also wiped if you use twipe_data.

In that case you should use the backup/restore option from NavRadio. You will get a NavRadio_Preferences json file in the root of your internal memory (or a NavRadioFree_preferences in case you do not supprt @KoTiX2 for his nice app).

(That NavRadio_Preferences json file is also handy if you want to manually add frequencies and then import it back)
[FYT Android Head Units] gordgelin:
probably there is difference - twipe_all also wipes completely /sdcard while twipe_data - not, if i'm not wrong
[FYT Android Head Units] Specy01:
I had imagined it, so I had previously removed the USB drives. Thanks
[FYT Android Head Units] gordgelin:
/sdcard is not usb but internal memory in these devices
[FYT Android Head Units] Specy01:
I thought they were saved on the usb. Tip, excuse me if I may: it would be a great thing if you could save it on the usb. Maybe with an option so that the user can make the choice of where to save.
[FYT Android Head Units] Specy01:
I understand, sorry I took a mistake. Thank you for specifying it
[FYT Android Head Units] KoTiX2:
Yes I'd really like to add this feature but it's not an easy task because on each android version change 9-10-11-12 Google changed the rights and methods to handle the user datas so it's just a pain for me.

It's not one of my priorities but I'll see what I can do. ;)
[FYT Android Head Units] surfer63:
Sorry. You are completely right. Thanks for the correction. I will also correct the post.
[FYT Android Head Units] Specy01:
Despite following your suggestions, the app icon reappears when you restart. What else can I do?
[FYT Android Head Units] surfer63:
Sorry, but this is really the right and only way. Is really every checkbox unchecked?
[FYT Android Head Units] Specy01:
Yes I have disabled all app options
[FYT Android Head Units] Specy01:
I made a video hoping you can see well

New video by Giuseppe Lavalle

photos.app.goo.gl
[FYT Android Head Units] Matt Devo:
you're misunderstanding. Open the Touch Assistant app. uncheck all the options therein. There is nothing in the Settings app to disable the HVAC control overlay
[FYT Android Head Units] surfer63:
When I say go to the apps, I do not mean in the Settings, but in the App drawer.
[FYT Android Head Units] Specy01:
Damn me, it was so simple 🙄 and I've done it other times, thanks. An OT question, is the first time I publish a link to a video of my drive, can I have privacy problems, that is, from that link someone can trace other files of my drive in addition to the video of the link? I don't think so, but I want to have you to confirm it. Surfer, sorry for the OT
[FYT Android Head Units] Matt Devo:
no, the generated link does not expose any information about the path or owner
[FYT Android Head Units] Specy01:
Tank you @Matt Devo
[FYT Android Head Units] prokiller1199:
anyone?
[FYT Android Head Units] matrixx1:
So apparently this issue happens only to my device an no one else?
[FYT Android Head Units] surfer63:
Have you set carlink to autoconnect?

Did you try without autoconnect but start from sleep? Settings -> User -> Application Setting ( which applications you want to auto-start when you start your car and unit )

And what I say almost every time: Why do you buy a full fledged fully functional Android unit and use it as an AA emulator? You could have done the same with a special unit < 99 euros.
[FYT Android Head Units] Clandaries:
That is the one million dollar question :) I think the same everytime someone is havin problems with Android Auto on a Android device where you can install nearly all Android apps.

Maybe someone can clarify this question.

Why use AA on a head unit with Android OS?
[FYT Android Head Units] marchnz:
Agree. Also, these Chinese knockoffs are not AA, its essentially emulated and causes no end of problems, resulting in daily membership here for support.

Want AA, why not buy a Google sanctioned headunit

Android Auto Compatibility | Android

Android Auto works with hundreds of vehicles and aftermarket stereos. Check your compatibility here.

www.android.com

Don't see your Chinese knock off listed above- its not AA :)
[FYT Android Head Units] surfer63:
True.

But when you buy such an expensive unit of at least 800 up to 2000 euros, I consider it even dummer to use it as an AA emulator ;)
[FYT Android Head Units] matrixx1:
Hi yes it's on autoconnect as I would like to have it connected automatically. As to your question why I did buy such a device for AA only. Well, it was still much cheaper than a JVC Kenwood Pioneer Sony etc device, and came in a package (with fascia, canbus, etc which are extra for branded devices), has a bigger better resolution and bc of Android I can add a lot of extra functions. But the UI of AA is the best imho for driving
[FYT Android Head Units] surfer63:
Perhaps yes, but in that case I would have bought an Mekede 200S, Mekede 300S or Mekede 400S (at maximum) for example. That is enough for AA and cheaper.

And in case of the 200S (only 2GB) on the unit in the Apps section disable a few apps.
[FYT Android Head Units] jsensation:
Hello I write from Spain.

I have one Android Head, Coho, with the uis7862. I don't know if it is FTY or TS10.

Could someone clarify for me?Thank you
[FYT Android Head Units] Ahto Simakuutio:
I have a 2015 Citroen Berlingo which electrical architecture is close to your car. I have the type C display on dashboard. I also have the Raise CANbus adapter. I can adjust the car original clock with the button panel in attached screenshot. The screen buttons mimic the buttons lost with the original RD4 radio.

I suggest you to try through different Peugeot/Citroen car models in the "original car agreement" (or such) menu in "Factory" menu. I found "Peugeot Tepee" to be correct one for my particular car.

The steering wheel stereo stalk buttons worked initially correctly. I remapped some of those with @seb21 Modded syu.ms.apk.
[FYT Android Head Units] surfer63:
You should have photographed the top notification bar as well.

But it is a FYT.
[FYT Android Head Units] jsensation:
Does this photo help you?

It's that I have a problem. I can't connect an odb bluetooth to the android unit. I don't know how to fix it.

I imagine that they have already discussed it, but I do not handle English well and I use Google translate.

Thank you
[FYT Android Head Units] matrixx1:
Well it is really nice of you to be worried indirectly about my financial situation but I can assure you I could afford it, was ca 400 usd. I am too much into gadgets not to choose the best available, it's one of my weak spots. Anyhow I enjoy the HU very much and am happy I went with the best available:)
[FYT Android Head Units] matrixx1:
It's not possible to connect to obd via Bluetooth on this device unfortunately. You can go with usb or WiFi version, not with BT
[FYT Android Head Units] Clandaries:
OBD adapters mostly uses 1234 as password. Try to set it in the Bluetooth app.

The Ekiy T7 and my CC3 can connect to OBD snd phone.
[FYT Android Head Units] surfer63:
Not true. It is limited but it can be done with the right BT dongle.

See bullet #28 of post #2 of the "Q&A, tips, info Roll-up (Joying) FYT SC9853i". No matter that it is a sc9853i or a uis7862. It is a FYT and it is 100% the same.

The second option is to change "sys.fyt.bluetooth_type=1" to "sys.fyt.bluetooth_type=0" in your config.txt and flash that one. That might help as well.
[FYT Android Head Units] Matt Devo:
could have fooled me
[FYT Android Head Units] jsensation:
Thank you all.

I have tried with the code 1234 and it has not worked.

I will try to flash the modified txt.I will try to flash the modified txt.
[FYT Android Head Units] 03hdfatboy:
ATOTO AC-4450 Bluetooth OBDII, uses torque app.​

I have one, works great.​
[FYT Android Head Units] kangyoon20:
Last try for any solution/suggestion before i get an small amplifier with crossover 😁
[FYT Android Head Units] old.splatterhand:
Bluetooth Connection is indeed very tricky.

I have a cheap OBD adapter from ebay which i tried to connect in Joying settings and in stock Android settings. I doesn't show connected in both, but Torque app does and receives the data from it.

But the OBD connection killed my Bluetooth Hotspot connection which is more important to me, so i skip the OBD part in the future.
[FYT Android Head Units] darudon:
Thank you for your answer!

I haven't tried every Peugeot/Citroen model, not even the Tepe, but quite a few. (307, 408, 407, etc.) I found the panel shown in the picture several times, but it did not respond to any button, on any model. I'll try the non-numeric types as well.
[FYT Android Head Units] matrixx1:
Well good for you. On MEKEDE m6pro plus it doesn't work. I didn't try the hack posted above as those are from 3-4 years ago and since then th manufacturer did some changes to the firmware. So on my device I cannot get it to work
[FYT Android Head Units] jsensation:
I was able to connect the obd modify the config.txt
[FYT Android Head Units] surfer63:
# deleted. Not worth the time #
[FYT Android Head Units] j0hn83:
It does.

You can only use those Bluetooth options (the default android Bluetooth menu) if you set Bluetooth type 0 in your config.txt.

odb adapters almost always work here in my experience with type 0 set.

The M6 Pro comes with Bluetooth type 7 in the config.txt so you need to use the provided Bluetooth app that you pair your phone to.

It's hit or miss whether the odb will connect in there depending on the odb adapter used.

My odb works on my Mekede m500s with both Bluetooth type 1 and 0
[FYT Android Head Units] surfer63:
# Deleted as well as it was a reaction on several posts #
[FYT Android Head Units] Matt Devo:
I'm using the same device. "I can't get it to work" is not the same as "it doesn't work / not possible"
[FYT Android Head Units] matrixx1:
So my statement was not untrue. It doesn't work. Of course if you do some hacking you might be able to get it work but that's above "normal" operation. So if I ask you nicely would you be willing to share with me how you were able to make it work? Do you use some kind of special BT OBD2 or you flashed the config file change the value of the BT settings from 7 (supposedly) to 0? (supposedly).
[FYT Android Head Units] Matt Devo:
I didn't do anything special. I used MD's Settings Shortcuts app to ensure that BT was enabled in the stock Android Settings. I disconnected my phone from the HU. Then I opened the OBD Eleven app and clicked connect. No pairing necessary or changing of BT type via config (it's set to 7)
[FYT Android Head Units] matrixx1:
Ok to be honest I havent tried it with my phone disconencted. Also because phone is connected to BT1 and OBD2 should be connected to BT2 according to my understanding. using MD's Settings shortcut, I also can get to the BT menu but i only see devices called noName, nothing else, ever (see picture in my above post). But it is also true I dont have a 120-140 USD worth of OBD2 adapter with dedicated app, just a plain and simple one.
[FYT Android Head Units] Lakis_dj:
Mekede m500s - Torque Pro OBD 2 & Car - for Toyota corolla 1.6 M.MT.
[FYT Android Head Units] matrixx1:
Ok I really don't understand how some people can make obd2 dongle to work via BT on a MEKEDE fyt device. Mine as stated above couple of times sees the BT devices as noName. Apparently somehow yours doesn't. But I have no clue why this is the case and as I see people like to show off that 9ts working but cannot share how or why it is working. Of course maybe they are lucky and have a dongle which works with dedicated SW or BC of other reason and people also don't know why it's working for them
[FYT Android Head Units] Lakis_dj:
which program works with obd ? thanks !
[FYT Android Head Units] j0hn83:
Your understanding is incorrect for your device. I've only ever seen that advice on Atotos website.

BT2 should only be used if you have set Bluetooth to 0 in the config.txt

BT2 doesn't work otherwise

It isn't because Matt has an expensive ODBII with app either.

I have a £5 ELM327 unbranded, generic ODBII off of Amazon and it works perfectly through the BT1 app without any changes or tweaks to my device. I didn't even need to change the Bluetooth PIN to 1234 to match my ODBII.

For those that can't get ODBII working through BT1 (and there are many who can't, not just you) then the advice is to change Bluetooth type to 0 and then it will work.
[FYT Android Head Units] jsensation:
I have a hybrid Toyota, that program is Hybrid assistant.

To connect the obd modify the config.txt changing the bluetooth value from 1 to 0 (or vice versa) as they put in another answer.
[FYT Android Head Units] Ahto Simakuutio:
I got a generic BT dongle working with following instructions. Kudos to @surfer63

The key point was first to remove phone pairing. And I was lucky in that my dongle identity starts with "OBD".
[FYT Android Head Units] Ahto Simakuutio:
Oh. In that case you may be out of luck with Raise. Lets hope the XP adapter works better if you ordered one already.
[FYT Android Head Units] Syntaxer:
Hello, have anyone tried JamesDSP?

Does it work with the already included DSP and is it even worth it?
[FYT Android Head Units] jsensation:
hello i have a problem

I tried to install the Mario firmware and the radio did not work, it restarted, the canbus did not work...

I tried to install a Mekede firmware and the radio does not start. The Android symbol or the recovery robot does not appear.

Thx...
[FYT Android Head Units] Clandaries:
I used Rootless JDSP, but i just used it to make the head unit louder.

But now i have a external amplifier so i deinstalled it.

Cant really say something about it.
[FYT Android Head Units] surfer63:
Did you try really everything as explained in post #2 section IX ?
[FYT Android Head Units] jsensation:
The problem is that the logo does not appear.

I press the reset button, it restarts but the screen stays black.

The only thing that occurs to me is to connect to a computer to see if I can enter the recovery to install from there.The only thing that occurs to me is to connect to a computer to see if I can enter the recovery to install from there.
[FYT Android Head Units] surfer63:
Do you have a special screen that requires a special LCD config?

What's more: was there an lcdconfig in that firmware that you flashed?

Do you still have a photo of the System info screen where it mentions the panel. I just helped a user who also had a black screen without anything appearing, not even the boot logo, and with only flashing the correct lcdconfig it worked again.
[FYT Android Head Units] jsensation:
I have the screen that came with the HU.

I flash the firmware Mario

dantas, 1.4gb.

This is the information I have
[FYT Android Head Units] surfer63:
No, you flashed mario Dantas' software.

and then you flashed "some" Mekede firmware. Which one? A standard 7862 version? Or a 7862 pro version with different config.sys and didfferent lcdconfig?

Show us a listing what was in that Mekede firmware.

Secondly: With the panel I mean something like this (which I quickly copied from another post).

This photo is terribly unclear but it was the one I found first. photographed images are wrong. Use the builtin screenshot option.

If you have that panel identifier from your original firmware we might simply "unbrick" your unit with only the correct lcdconfig file and the lsec7862update binary.
[FYT Android Head Units] jsensation:
I do not have the information you are asking for from the panel.

Flash The firmware Mario on top of the oem of the year 2021.

Since it didn't work, I flashed the medeke uis7862 9"10" vertical firmware because the normal one was not on the web. Modify the config.txt so that the screen instead of 180 was at 90°. in the middle of the flash The radio turned off and it didn't turn back on.

I copied all the files that came out of the .zip from the web page.
[FYT Android Head Units] labkos:
I downloaded the firmware for the Joying UIS7862 System Car Stereo. Can I install it on my own?
[FYT Android Head Units] gordgelin:
it seems you have FarCar device, their devices are often incompatible with generic firmwares in some parts
[FYT Android Head Units] labkos:
It is fyt device
[FYT Android Head Units] gordgelin:
of course it is fyt platform, but device manufacturer seems to be farcar, they often have different boards, mcu and android firmwares so usually listed in separate forum threads, but you may try if you have your original firmware
[FYT Android Head Units] labkos:
Thanks.I will try it
[FYT Android Head Units] matrixx1:
I tried this with my BT OBD2 dongle with its name OBDII and did as described but for me it didn't work unfortunately
[FYT Android Head Units] labkos:
If I am upgrading with this firmware will the applications be lost
[FYT Android Head Units] maciej.kubiak:
Q12 from Q@A

I have some problems with additional microphone.

When I plug in extended microphone to minijack 3,5mm works 2 microphones - included and extended. I have unit 8581 so I haven't in options microfon choose.

I tried to method with isolate 2 pins on wires to microphone in unit, but if i did this, I haven't signal input from microphone in minijack 3,5mm and in unit. So I think problem is with impedance in circuit od microphone in this unit. Anyone can help?

I can do method with original wire and microphone OEM with amp (power +/- 5V and signal with 1kOhm on signal from microphone) but I don't know it will work.

Is possible to change software, to get in fabric options Microfon choose?
[FYT Android Head Units] surfer63:
Don't cross-post.

This is an hardware option. Your unit would have the setting if it was enabled in the hardware.

If you now put a brand-new firmware on your unit, the option might indeed be in the Settings, but it will still not function.
[FYT Android Head Units] maciej.kubiak:
I thought this thread is for 8581 units. I have unit with this CPU and in Q&A is in 12 point about microphones. If it will be hardware problem - the isolate of pins from mic should work, but isn't. Ok, software not solve the problem. Any ideas how to disable one of mic ?
[FYT Android Head Units] surfer63:
Yes, that is correct, but you also asked in the "Medeke/Navifly 7862" thread. That is cross posting. And that thread is especially for 7862 units by the way. That is why I answered here and mentioned the cross posting.
[FYT Android Head Units] maciej.kubiak:
Ohhh yes, i know what you mena now. I double post here and there, because i thought there are two different threads. Here is link to Medeke thread in step#2 to solve the problem. Here can't help, maybe there someone has the same problem with disabling the mic. If there two threads about unit and microphone what's wrong i asked in 2 places the same time? Maybe people from mekede thread doesn't read here? I thought it rise effects.
[FYT Android Head Units] j0hn83:
It's called cross posting and it's against the rules.

Choose the thread that you think is most relevant and post there.