yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
You are right. I had some blackout I think.

Off course your kernel from 28 June is newer that the foreign from 17 June.

Of course the domestic one from 24 July is the latest, but I drag the Google stuff from the foreign 17 June into the domestic.

The Google stuff is important for our units to function, but the date is not extremely important. The Play Store apk and Google Maps, etcetera are built into the product partition, but if newer versions are available in the Play Store, they are downloaded anyway. And for some of those Google apks, you get almost every week new versions, so it is impossible to keep track.

For me the most important part are security fixes and android base layer upgrades in the kernel.

Even creating a kernel based on the domestic kernel only containing the Google Play Store would be sufficient as you can then download everything from the Play Store, but it would indeed require a lot of downloading.

With full kernels you do not have to do anything. Everything works and due to the fact that you can flash without a "twipe_data" or "twipe_cache" means that it functions like a normal Android phone update: Everything will comntinue to work (A flash with fmc or modeed com.syu.ms will require a "tweak_cache").
[FYT Android Head Units] prokiller1199:
Thanks I found my "Ver" file but for the kernel I think just don't bother to touch it because it seems a bit complicated.
[FYT Android Head Units] Chrizzydizz:
Been trying to make a backup of my HU but doesnt seem to work.

Copied the content from the backup.zip to a usb and I get a prompt in the HU about firmware update and I clock okey and it reboots and then shows this message and then reboots. No backup is made...

Included my HWget_info.zip
[FYT Android Head Units] prokiller1199:
Time based is it will dim your screen when sunset time.

Small light control is depends on your headlamp switch, when you turn on your headlamps then it will dim your screen
[FYT Android Head Units] InElement:
Ahh, so this isn't for the LEDs on the side then, but rather for the backlight on the screen.

Will probably just use headlight mode, but when is the sunset/sunrise time configured when in time-based mode?
[FYT Android Head Units] prokiller1199:
yeah... I think the side capacitive touch button couldn't be configure at all, only the color.

I think depends on area, here in Asia (Malaysia) it dim my screen follow the internet sunset time I guess... at around 7:30pm
[FYT Android Head Units] sawixso81:
Thanks for the upload...with some tinkering got it running on my joying 7862...only issue I have is the Bluetooth app won't ask permissions for my contacts so they don't show...I did notice that the new Bluetooth app has a 2000×1080(something like that) my unit is a 1280×800...would that be the issue. Also in order for all the launchers to work I had to flash it with my units kernel for it to work
[FYT Android Head Units] Fbocsa:
Greetings All,

I did a test again with the appbackup script.

I disassembled the HU and realized the Dash camera is connected to USB 1 that is why it gets the sdcard1 and the usbstick is sdcard2. So I have disconnected the dash cam and the script run but with failure. I found only config.txt, Isec6316update and updatecfg.txt in backup folder.

I have tested several times and started to read the posts again.

I have found the script I have used was from the post#225 so I have downloaded the zip from post#4 and it worked well.

My HU is an uis8581a2h10 4gb/64gb

Many thanks for the script and for all other app and information!
[FYT Android Head Units] arca114@gmail.com:
You can only use the same as your screen if changing this can have serious problems...
[FYT Android Head Units] surfer63:
Thanks for your reply. I removed the script from post #225.
[FYT Android Head Units] valerio.tosti:
Hey Guys any way to uninstall Spotify apk from my Headunit without root? Uis7862
[FYT Android Head Units] surfer63:
Just like any other 3rd party apk. Long-tap the apk or do it from Settngs->Apps
[FYT Android Head Units] valerio.tosti:
Its installed as system app, can't uninstall
[FYT Android Head Units] surfer63:
T'eyes unit? -> Then you can't remove it.

Other FYT unit -> via an lsec script
[FYT Android Head Units] valerio.tosti:
Have other Fyt.

Can you help me with that?

I am not that good at this.
[FYT Android Head Units] surfer63:
Copy an lsec6315update to a clean USB-stick.

Create a folder lsec_updatesh on that USB-stick

Inside that lsec_updatesh folder, create a 7862lsec.sh file (As you don't mention it, I think you are a windows user, so make sure stupid Windows does not add a .txt behind that)

Inside that file 7862lsec.sh file insert:

#!/system/bin/sh

rm -rf /data/dalvik-cache/profiles/*com.spotify.music*
rm -rf /data/dalvik-cache/arm/*com.spotify.music*
rm -rf /data/dalvik-cache/arm64/*com.spotify.music*
rm -rf /oem/app/*spotify*
rm -rf /oem/priv-app/*spotify*

As I do not exactly know how spotify is installed, i do a "brute-force" delete.
[FYT Android Head Units] surfer63:
For what it is worth (maybe to start a new discussion;)?).

I added "Q27: SOC or SOM? What is the difference?" to the first post "Q&A".
[FYT Android Head Units] Fredday:
Hello InElement, congrats on your unit. To answer these 3 things you mention:

Floating button can be turned off through your apps -> touch screen -> open it and turn it off or adjust it to your liking.

The lines of the backup camera I can turn off when I go into my hdr settings app, you can however adjust them a little bit but it will never be like a built in back-up camera from the factory.

The radio app that's built in is sh** and you'll have to get used to it. I also installed DAB+ with my unit so I am using the dab-z app or whatever app you want and make my unit start up with this instead of the regular radio. However if you search the forums for navradio+ topic, there you can find how to "uninstall" the regular radio app.

Hoped this helped you a little bit.
[FYT Android Head Units] Fredday:
@surfer63 as a fellow countryman, maybe you can help me out as I see you seem to be very familiar with the headunits.

How can I change the default google maps navigation which shows on my launcher to another one of my liking? (no, not waze, i'd like to use Flitsmeister)

I have been looking around on the forums but I can't seem to find the solution.
[FYT Android Head Units] surfer63:
Although deprecated as the Launchers now handle it themselves, you can still try the T'eyes Frontapp: https://play.google.com/store/apps/details?id=ru.fytmods.frontapp
[FYT Android Head Units] Ahto Simakuutio:
Pictures look the same as on my Mekede, so I reply based on my knowledge.

It can be removed. The option is buried somewhere in the menus.

Same as above, I think this setting is inside the Factory > Reverse parking line. If you cannot find it, you can still adjust the lines to outside of visible screen.

As replied already, but one anecdote: On my system both screen dim and side buttons illumination are controlled by that above setting.

Yes, the original radio app is hopeless. I guess Chinese don't use RDS so they cannot relate how it should be utilized. I suggest you to try Navradio.

Possibly. You need to find its signal in the car wiring, attach a 3.5mm plug on it, and hope the OEM mic gain is at applicable level for the headunit.
[FYT Android Head Units] Ahto Simakuutio:
Setting Max Reversing angle: How this works?

I have dynamic reversing lines on camera view. The lines sway based on steering wheel rotation. The information is got via CAN adapter.

I'd expect that the max reversing angle would scale how much the lines sway, but the setting does not seem to have any effect on the lines graphics when I have tried altering it. Is my expectation incorrect?
[FYT Android Head Units] Fredday:
Hey Surfer thanks for the reply however I have the mekede m6 pro plus with your ok-kernel and the md-edition. So I guess this doesn't work for it or is it a general app although it says it's for t-eyes?
[FYT Android Head Units] surfer63:
Even thought of looking in Post #1: FYT Settings explained?

In that case you would not ask all these questions.

Search the forum!

And with regard to the dynamic lines. That is indeed how it "should" work. I do not know why it doesn't for you. If I rotate my steering wheel a little and then change the setting, I see the lines sway back and forth.
[FYT Android Head Units] Ahto Simakuutio:
Thank you @surfer63 for your effort and help on this forum. I honestly don't know how should I have phrased my question otherwise. Yes, I have read post #1 many times and this complete thread through, as it contains very valuable information. I am also willing to contribute to the community 🙏

This confirms that the setting actually works on some applications and is not just a Chinese decoration. And there should not be any special trick to know, it just is not working in my case. Not a biggie, would be nice to have it but I can manage with the default.
[FYT Android Head Units] spacebutler5:
I installed CH-9863-FYT sold as EKIY X7.

Using the default radio app it see it will randomly start a scan of the fm band? Ie I am listening to fm band 91 and suddenly it is sweeping the full fm band (no noise is coming out of the speakers during the scan) it's not a phantom steering wheel keypress as I only have volume up and down programed, and track skip up and down which switch between the programmed channels. If use the touch screen I can interrupt the scan and go back to one of my programmed channels, but it will start the scan again after 30 seconds or so. Once I let it do a full scan it seems like I can finish my drive without it doing it again.
[FYT Android Head Units] prokiller1199:
Hey @surfer63 do you know what's the difference between sys.fyt.bluetooth_type=0 and 7? Because my unit came with 7 and it is damn buggy and unstable basically unusable. After switching to 0, it is so damn stable and works like charm, but I did notice I lose some of the features. For example, the only one is HD audio streaming (aptX HD) is enabled on type 7 but only AAC on type 0.

update: Also tried type 1, not working at all showing "activation error"
[FYT Android Head Units] Clandaries:
This is what a config says.

# Bluetooth types

# 0 - built-in trash

# 1 - realtek

# 7 - qualcomm
[FYT Android Head Units] surfer63:
Disclaimer ;):This is an "educated" guess.

There are at least 5-8 suppliers of bluetooth chips, where RealTek and Qualcom are two of them.

I simply think that they used RealTek BT 5.0 chips in the older 7862/8581a models, and that they use Qualcom BT 5.2 chips in the 7862S SOCs/motherboards.

And just like you have a fytmanufacturer id, I assume you also have this "sys.fyt.bluetooth_type" id to to get the most out of the chip.

I assume 0 is the "general purpose" AOSP bluetooth driver stack. (AOSP = Android Open Source Project, but that should be basic knowledge).

1 is then the Realtek driver optimization

7 is the qualcomm driver optimization.

Note that as of BT 5.2 HD audio streaming is added to BLE.

The BT version in the uis8581a/uis7862 is BT 5.0 or BT 5.1

I assume that is the difference.

As FYT always cripples the BT drivers/stack, I assume they still have some bugs to fix on the M6Pro models.

But again: It is an "educated guess".
[FYT Android Head Units] prokiller1199:
My unit have BT 5.1 as written in the spec list. They say they using QCC3031, some place say it's BT 5.0 some says it's BT 5.1... LOL

7 is the Qualcomm optimized driver? to me it's more like not optimized at all.
[FYT Android Head Units] surfer63:
Thanks for the QCC3031 mentioning.

The qualcomm specification sheet mentions that it is BT 5.1/5.2, whatever that means.

The (complete) BLE HD specification is a requirement for 5.2, but probably already part of that functionality might be built in into lower version chips.

Just like OpenGL 2.x and 3.x are GPU displaying standards, but some mali or other GPUs already supported and support some of the functionality in chips with lower OpenGL versions, simply because at that time they do not comply with all the requirements.

And as I started my reply: "This is an educated guess".

If I am wrong then please let someone correct me.
[FYT Android Head Units] prokiller1199:
Cool explanation. Thanks

I guess I'll have to wait for Mekede to fix this type "7" bug or wait for it to become more matured in future then I will flash back. Will use type 0 temporary.
[FYT Android Head Units] gordgelin:
this is not educated guess )) this is what my config.txt says ))) there are also other types but they were never found in these devices

i decided to add this info instead of that unreadable comments it usually has

wrong bt type == completely non working bluetooth

also i know there are 9863 devices with bluetooth type 8 but for now i do not know what chip it stands for

1 - realtek

Spoiler content hidden.

7 - qualcomm

Spoiler content hidden.

0 - built-in bluetooth, part of SOC/SOB, you can switch to this type even if you have dedicated chip 1,7 or whatever

Spoiler content hidden.
[FYT Android Head Units] gordgelin:
yes, for now there are much more complaints about QC bluetooth then there ever were for old realtek devices,

new Teyes CC3 boards with QC chips also often reported for bt problems, they even shared some firmware updates for QC chip itself
[FYT Android Head Units] InElement:
General question as I'm getting acclimate to my unit: Some of these custom launchers are really heavy-handed. I don't want too much on my homescreen — just an analog clock, the usual app launcher button, and maybe a few shortcuts to things like the radio app, carlink, and settings on my homescreen.

What's everyone going with for this kind of setup? It seems like Nova is the go-to? Any particular widget recommendations or collections of ideas anywhere? A show-and-tell thread would be nice, if one exists anywhere?
[FYT Android Head Units] Fredday:
There's a vid on YT from saabunleashed who talks about different launchers and shows them in his vid. Might want to look at that if you want a custom setup.
[FYT Android Head Units] laoyang88:
Not guessing. Chinese is marked in the config file
[FYT Android Head Units] laoyang88:
0 internal bluetooth written in Chinese
[FYT Android Head Units] prokiller1199:
not on mekede's config file.
[FYT Android Head Units] laoyang88:
#test

sys.fyt.bluetooth_type=1

persist.sys.ahd = 1

# 高清倒车 1开 0关

# 配置蓝牙类型

# 0：内置蓝牙；

# 1：RDA；

# 2：IVT；

# 3：WQRDA；

# 4: WQBC5

persist.syu.camera360 =1

# 0不带360 1带360
[FYT Android Head Units] gordgelin:
i know ))

but for most users it often looks like this in many text editors/viewers and it does not list 7 and 8 anyway
[FYT Android Head Units] laoyang88:
select GB2312 in word
[FYT Android Head Units] laoyang88:
The sound of the mic is small and there is noise, can the settings fix it?
[FYT Android Head Units] Moldeb:
See the general discussion thread, in particular FAQ and the description of config.txt. In my UIS7862 Joying unit (which doesn't have an internal mic, only external), it also makes a difference whether I use BT module 0 or 1, interestingly (as it shouldn't) - on 0 the mic is much clearer/louder, on 1 callers complain about distant/quiet/difficult to understand. Have to use 0 anyway to get my OBD dongle working so stopped thinking about it.
[FYT Android Head Units] laoyang88:
thanks. I have a problem with my external mic. changed one. ok
[FYT Android Head Units] laoyang88:
I don't know whether the volume of btphone is 0 or 1.on my px6 it is 1.usually use external bt
[FYT Android Head Units] Moldeb:
PX6? Wrong forum.

To clarify: 0 and 1 refer to the BT module (not volume) set in config.txt as also discussed further above: sys.fyt.bluetooth_type=1 or sys.fyt.bluetooth_type=0
[FYT Android Head Units] laoyang88:
sorry. another px6
[FYT Android Head Units] laoyang88:
two bt different volume settings
[FYT Android Head Units] Moldeb:
Not relevant here, don't transfer anything from PX6 to UIS7862. Read everything on microphone in posts #1-4 of this thread, it gives you settings you can try in config.txt, tells you how to disable the internal mic, etc.
[FYT Android Head Units] laoyang88:
Maybe it can help to understand the working status of internal and external bt
[FYT Android Head Units] Moldeb:
There is no external BT though.
[FYT Android Head Units] laoyang88:
Maybe set 4 to see the effect.Might be able to drive it too.maybe louder
[FYT Android Head Units] Moldeb:
You will only get an error if you chose a wrong driver for a module.
[FYT Android Head Units] Fredday:
Hello Moldeb, I have the same issue with my obd dongle.. it doesn't show on my unit's bt but neither on my phone yet it is connected and showing the lights. I do have obd on within the unit's settings. Did you have the same issue it didn't show on neither?
[FYT Android Head Units] j0hn83:
Try some of the launchers on marios FYT site.

Specifically the 2 launchers labelled

19001120com.android.launcher8 26 ALL UNITS

or

19001120 com.android.launcher6 26 ALL UNITS

7862/8581 FYT Factory by Mario Dantas
[FYT Android Head Units] hzn942:
Question: is there a way to configure the factory password before flash the firmware?

I have Mekede M600s, recently I flashed joying's newest firmware(04/07/2022), everything works fine except that I cannot enter the factory setting/developer settings. I've tried the password mentioned in Q&A section but nothing worked for me.

would you please give some help on this issue?
[FYT Android Head Units] hanichl:
Doing some tests with several firmware files from Joying. Each time, a new firmware is processed, all settings and installed oem apps are removed.

I removed the entry "twipe_all" in updatecfg.txt , same behaviour, very strange: some apps are missing, some are present ... some settings are present, some are gone ....

Any hints, tricks to get a real "update" , without removing / formatting / anything ? I know, that there also my bi issues when doing that, but nevertheless .......... KR !!
[FYT Android Head Units] sagipael:
Seem that the cpu family is aarch64
[FYT Android Head Units] surfer63:
Please check the original script.

You mention that the command failed

/storage/sdcard1/7zzs........ failed

But is this really the entire error?

And is there an AllAppUpdate.bin created?
[FYT Android Head Units] martindagun:
I have the Ekiy KK3 unit and have two minor issues:

- The side button backlights seem to turn off after a short period. Is there somewhere I can change this as I can't see them at night time.

- I can't seem to get my phone connected via Carlink. It used to work with my phone but not my partners. Now it's changed where it allows for my partners phone to be connected but not mine. Btw I'm not trying to have both of them connected at once. I can connect via bluetooth but not carlink.

Thanks
[FYT Android Head Units] mariodantas:
Yes it show fail but AllAppUpdate.bin is created and I checked it, is good, /oem/Ver file does not exist
[FYT Android Head Units] Ming12309:
Tôi có ***g câu hỏi với bạn

Mod translation via GT: I have the same question as you
[FYT Android Head Units] mariodantas:
Thanks for using my tool !
[FYT Android Head Units] AxesofEvil:
Is there any way to know whether I have the latest firmware? I have a brand new M500s, which has build #: 'QP1A.190711.020 release-keys'. I am wondering if the links posted in post #1 are more recent or not.

(Edit: I used HWGetInfo and found that my build date was:

[ro.system.build.date]: [Mon Jan 17 09:25:02 CST 2022]

...But I don't know where to find the equialent info in the downloaded firmware before installing it)

Also, is there any way to backup the existing firmware? I already ran the backup procedure as per post #4, but this does not capture an equivalent 6315_1.zip file. I am wondering whether there is a way to create this file from my unit before upgrading the firmware.

I have seen a few reboots while using the unit, and am wondering whether a new firmware will address this.
[FYT Android Head Units] surfer63:
You don't need a 6315_1.zip file. For the 7862 FYTs they are all 100% identical. That's why my script doesn't make a backup of it.

Of course it makes a difference to flash a newer one compared to an old one.

However, I found literally no differences so far from older ones to newer ones. The Chinese builders are lazy.

To get the build date you really need to unpack the 6315 to the deepest level being the system partition where you will find the build.prop.

I described that in post 2: III. The 6315_1.zip
[FYT Android Head Units] mariodantas:
I have also a tool for that (linux) which uncompress the 6315_1 and creates the mount points for each partition

https://xdaforums.com/t/tool-fyt-firmware-workbench.4444267/
[FYT Android Head Units] AxesofEvil:
Can you clarify these 2 statements? if the 6315_1 has the build date then it is clearly not 100% identical (since my build date is newer)

But what I really wnat to know is that I can revert back to how my unit was if I try a different firmware. if I do not flash the 6315_1, and only flash the AllAppUpdate.bin, I guess that may be good enough. Is there any version information in the AllAppUpdate.bin?

Thanks, this makes things a little easier
[FYT Android Head Units] AxesofEvil:
Has anyone done any reverse-engineering on the Canbus module interface to the head unit?

I have a Volkswagen MkVI GTI with Dynaudio, and get no sound out of the radio due to the amp being controlled via CanBus commands. I talked to Navifly, but they just said:

This is definitely not true for my vehicle. I was able to reverse-engineer the AMP commands far enough to be able to send canbus commands to tun on/off the amplifier (canbus identifier 0x6c7). I'm building a small arduino module (mini pro + MCP2515) that will use the amp-power wire to send the proper commands. That will be enough to get things working, but the Amp supports additional per-channel balance commands as well, and I'm wondering whether I could just replace the 'Raise' module altogether to get more functionality
[FYT Android Head Units] dbmgreen:
Question:

How do I identify my joying model.

Whenever I ask joying, they just send me an update file. Its an android 10 device, only had it about 6 weeks. It is still the old UI, and I would like the new UI. The last file they sent me, was the wrong screen orientation. :) grrrrr

Its a 10.1inch screen.

If I have the model, I'm assuming I can download firmware for my model with new UI?

They always ask for this screen attached.

Can anyone help?

Just for clarity, the SKU doesn't seem to match the model number? Not sure why?

I purchased this image below my screen grab.

SKU: JY-TQ155N4G-B

Ship From: Chinese Warehouse

CPU: UIS7862 12nm Dual ARM Cortex-A75 + Six ARM A55

Ram: LPDDR4 8GB Rom:EMMC 128GB

Support Bluetooth, WiFi, DVR, OBD2, Back-Up Camera
[FYT Android Head Units] Petarkco:
Looks like Joying have released another update. No changelog again.

I wish there was a way to find out what has changed because it's a pain having everything wiped when there is no noticeable difference.
[FYT Android Head Units] stediste:
I have a question, my headunit is FYT 31 and i noticed it interfere with DAB+ signal. I would like to know if someone else have noticed it. I want to buy another headunit, but don' t want the same problem.
[FYT Android Head Units] surfer63:
I was not precise enough in my statement. They are not bitwise identical of course.

A specific type of phone has its own system firmware for cpu and installed hardware and the like.

Those FYT uis7862 units are all exactly the same (exactly the same "phone") and if you download a firmware fom Joying or Mekede or T'eyes, they might pack it with their own programs and "tweaks" inside the AllAppUpdate.bin, but the system part (6315_1.zip) is for all units identical.

Some minor variations like a better or worse radio chip, or better or worse audio chip are covered by builtin "drivers".

And yes: you can only flash the AllAppUpdate.bin without touching the core of your system.