I have read in some cases the external one is being interfered by the internal microphone. Have you tried to disable it?
General General FYT based Spreadtrum uis7862(s) (unisoc ums512) & uis8581a (sc9863) - Q&A, Mods, tips, firmware
- Thread starter surfer63
- Start date
Yes, thanks.
Tried this using both methods - software and disconnecting internal mic, both unsuccessful.
It does have interference but not in the way that the external mic doesn't work anymore. It simply doesn't improve and gets slightly worse, but that is something else than not functioning at all.
Or FYT has introduced a new bug
Thank you all for the input. Here is my plan
- Quadruple check the physical connection and ensure physical click
- Test the eternal physical mic (3.5mm jack -> harness -> HU) to another device to see if it works
- Try to find a known working external mic, and test this
- Quadruple check that internal mic is disabled (i did this in software in the factory setting, no change, but it sounds like I need to see the manufacture date to see if was made before August, and then I might have to open the unit)
Thank you. I’m sure I read a post on 4pda that someone had an issue with the external not working until they disabled the onboard mic. But I do agree with you. It shouldn’tIt does have interference but not in the way that the external mic doesn't work anymore. It simply doesn't improve and gets slightly worse, but that is something else than not functioning at all.
Or FYT has introduced a new bug
I was going to suggest checking the wiring harness to ensure it has a good connection in the connector.
Ok, I've torn up my dash again. thank you to everyone who gave me suggestions on the mic. Here are the results of my testing. Device details again for reference: iDoing FYT unit UIS7862 MCU 2021.04.26 15:40:55 PSTAR_53_L6315_G23P48F64_V:1.0
Any advice?
- Validated External Mic by removing the 3.5mm jack and plugging it into the 3.5mm jack on both a microsoft surface tablet and an old Moto Z play
- On the moto Z play, the phone was able to register voice via google assistance. The phone is on its last legs and died, so I switched to the surface
- On the surface, I made a test call to a friend in discord, changed from the surface internal mic to the iDoing external mic during the call; friend could hear me and noticed the audio change. I also made 2 recordings, one with the iDoing external mic and one with the Surface internal mic. They sounded different but I could hear both
- fully disconnected the harness from the back of the iDoing head unit and downloaded a voice recorder app directly to the head unit (phone was not paired)
- Recording 1: Internal mic, "back MIC switch" in Factory menu set to "OFF - Front Mic"
- Recording 2: internal mic, "back MIC switch in Factory menu set to "ON - back Mic"
- firmly plugged in the harness in the correct spot (it was fully seated) and re-connected the external mic
- Recording 3: external mic, "back MIC switch" in Factory menu set to "OFF - Front Mic"
- Recording 4: external mic, "back MIC switch in Factory menu set to "ON - back Mic"
- zero of the recordings picked up any sounds.
Any advice?
Attachments
Interested in this too.
I tried with a USB Jabra conference device which didn't work but I suspect needed more power.
Ok, so low-power options. Got it. I'm going to grab a cheap USB mic that I have laying around, and then if that fails, look for other options that are specific to Android. Seeing a lot of "lapel" mics designed to record to a phone, so that's promising. May also test with a USB A-C adapter on my phone. Will update in about 10hrs. If anyone has any recommendations, please share
No no, the photos are a bit grainy, but I guarantee you that everything is connected in a workmanlike manner. I will post you a good more detailed photos with the respective data of the mcu and all the rest. The isec 6521 update was working 2 years ago. But now when I repeat the reset, it completes the procedure and the screen keeps flashing and it won't let me set the resolution to 1280x480 pixels anymore. It is currently set to 1280x600. And I think some application has tampered with the resolution. Another mistake I made was not turning off automatic updates.
Attachments
j0hn83
Senior Member
FYT have crippled Bluetooth and USB on these devices.
I would not be surprised if a USB mic didn't work.
Ack. I did get bluetooth to work on mine, and wired Android Auto via USB. Can you give me some more details on what I should try to give me the best chance of getting this to work?
I tried a random USB mic that I had lying around; no dice. Will try around with lesser audio app that was recommended to me in another thread, and maybe look for an android-specific USB app
Fully suspecting a software issue on the head Unit at this point. Any other ideas?
Fully suspecting a software issue on the head Unit at this point. Any other ideas?
You already tried a lot, but did you contact Idoing and did you ask them? They are the first to contact but you don't mention that.
If your microphone connection is really defective you should contact them.
You are correct. I did reach out to Idoing first. They gave me basic troubleshooting steps which I've already tried, said "this should work", then asked for the wiring diagram for my stock head unit, so they could try to make a harness for the stock mic. Then said they'd get back to me in Feb.
Given this troubleshooting, I don't think this is a hardware issue
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2
You can't find them because they don't exist for you. There aren't anywhere on your unit.
Those are files for the FYT 7862 platform.
You have a TS10 (Topway) 7862 device. Same 7862 SoC/processor but the platform/firmware/MCU all differ a lot. There's nothing in this FYT Android Head Units section of the forum that is applicable to your unit.22
Yes, but your device is not a FYT, so not compatible with all firmware/mods/etcetera mentioned here.
You have a K706. Head over to the Android Head Units sub-forum for support.2
Z-link is for other platforms.
We use the carlink app on our FYT devices for carplay and Android auto.
Our devices used to have z-link libraries inside but they are no longer present in newer firmware.
No idea if it ever worked.2@sofakng please stop diluting this thread, it's already a lot of work to digest its on topic parts. Post #1 clearly states
and you seem pretty ignorant right now.
Thanks also to others who do not answer you here. -
58Last revised: 19 February 2024
This thread tries to be a "one fits all" thread about FYT based Spreadtrum Unisoc uis7862(s) (Unisoc ums512) and uis8581a (sc9863) head units and its software, modded or not. The first few posts will be "collection" posts for all kind of info but will also link to other useful information that might be added later or in other threads.
Part of the tips, mods, etcetera are also valid for FYT based sc9853i head units, and even for the older PX5 and Sofia-3GR.
DISCLAIMER: Every action you do on your unit is on your own responsibility. I will help where I can (and probably a lot of other users as well), but I am never responsible.
This thread is meant for:
- Discussing firmwares (see post #2), modded firmwares, mods and rooting (not advised).
- Tips, tricks, mods to improve the general usability of your unit.
- Try to solve design errors/flaws where we expect that these Chinese resellers/suppliers will not do it.
- buyers advice (is this one better than that one?)
- 4G providers, DAB+ modules or DAB+ software (see here for DAB-Z by @realzoulou), Navradio+ (see NavRadio+ ported to UIS7862-FYT devices by @KoTiX2 , sub-woofers, OEM cameras, OBD devices, TPMS or other peripheral devices.
- ABSOLUTELY NOT for posts about "what is/are your favorite app(s)?"
- Questions about repairs, warranty and the like. That is between you and the reseller. Questions about interchangeabilty of hardware are OK.
General unit information
Q&A - Questions & Answers
This section has been moved to post #3 as this post #1 got too big and started giving errors on editing.
FYT Settings explained
Safety & Security - Your Google account
All these Chinese and non-Chinese units are unprotected and fully unlocked. Like you leave your phone unprotected, off course in this case in a locked car.
Your Google account may contain:
- all your Contacts and Gmail - It would be terrible if others could lay their hands on it and use it for phishing, ask money from people who trust you, etc.
- your Google Drive - This might contain confidential documents like family documents, documents from your notary, life insurance, mortgage, etcetera.
- your photos - All those precious and maybe intimite family moments
- Less important (perhaps): Google Maps (where have you been, which places do you visit regularly), Calendar.
So, (My) Rule no. 1: Create a second account and use that in your car.
Disclaimer: Google accounts get hacked every day due to lame passwords or other reasons, but so far I have not heard of anyone's account being hacked in an unprotected car head unit.
If your Google Play purchases, like NavRadio+ or your media player, are in your family library (all my purchases are, apart from one which is useless in the car anyway), you simply invite your second account into your family library.
And you can always give your first Google account read or write access to (a folder) on the Google drive of your second "car" account to be able to exchange files and other data (or settings).
Mods, useful software, tweaks for your system, etcetera.
- Backup the firmware of your unit (see post #4). Useful if you do not have a firmware yet for your unit.
- Disable or (re-)enable the mediaplayer at startup/wakeup.
- Change Fytmanufacturer script to correct the fytmanufacturer id after a flash with another resellers AllAppUpdate.bin bullet #3). Note: You can still use this script but you can also add the ro.build.fytmanufacturer to the config.txt of your firmware and flash that config.txt.
- DocumentsUI for Android 10. Without it you can't write to an external USB drive with other file managers. That is because the documentsUI is missing. Install it, open it once and afterwards your file managers can use it to get access.
- Android Shortcut Settings: This program by Mario Dantas gives you access to some hidden settings in the (FYT) head units.
- Mario Dantas (@mariodantas ) created/build the website "uis7862 FYT Factory":
- A great and very extensive collection of launchers for FYT models and also a collection of (un)rooted kernels for your unit. (Read post #2 section III "The 6315_1.zip" for more info on kernels and how universal they are.)
- He now also created a new firmware (MD-edition) that after flashing gives you some very handy and essentials options for on-the-fly rooting and root access for selected apps, starting apps from boot, make firmware backups, save your /data/data partition, etc.
- @seb21 made a modded combination of the com_syu_ms.apk and a Config.apk. This combi allows you to change the "hard-coded" steering wheel buttons in case you have/use a CANbus and add "no kill" functionality. See Modded syu.ms.apk.
- getinfo script. This is in fact an extension of my HWGetInfo.apk, but as an lsec script. It gives more info than the HWGetInfo.apk as it runs as a flashable script thereby having full access to the system.
- Disable airconditions app on Tesla style uis7862/8581a units (see post #1781)
- Modded Launcher 34 (see thread "Modded Launcher 34 for uis7862(s) and uis8581a (and probably uis8514a)")
- A completely modded firmware (AllAppUpdate) with uniform theming. See the PeaceOS thread.
- Rooting your unit: See @gordgelin's universal root script or from his own website.
47Last revised: 12 July 2023.
More about Firmware(s)
This post is valid for FYT uis7862(s) (ums512) and uis8581a (sc9863) units running Android 10 or fake Android 11 or 12.
Contents of a firmware zip:
Note that the firmwares for the uis7862 and the uis8581a only differ on the flashing binary and the kernel zip. Configuration files are the same. Some resellers deliver a firmware that contain two kernel zips and two flashing binaries, as the flashing binary will only work on the hardware it is intended for flashing the correct kernel zip.
- Kernel:
- 6315_1.zip: the kernel zip for the uis7862(s).
- 6316_1.zip: the kernel zip for the uis8581a.
- The 6315_1.zip or 6316_1.zip zip file contains all "standard" Android software, drivers and apks. It also contains the the boot.img; the system/vendor/oem partitions and a few other things. This 6315_1.zip for the uis7862 "should" be interchangeable between all 800x480, 1024x600 and 1280x720 models. The same for the 6316_1.zip for the uis8581a. Special resolutions come with specific lcdconfig.txt files.
- The binaries that do the flashing of the firmware:
- lsec6315update for the uis7862(s)
- lsec6316update for the uis8581a.
- These are the binaries that do the flashing of the firmware, optionally install a boot image or boot animation, optionally run scrips from the lsec_update folder after the flashing process itself has finished. These binaries can also be used to only flash a boot image, boot animation, or run scripts.
- AllAppUpdate.bin: Special zip file that contains all FYT apps (This can be (un)packed with any (un)zipper, but I prefer 7-zip). This file also contains special files with reseller specific configs. This one is only interchangeable between the same reseller-id, unless you change that reseller-id or use the scripts from post #3, bullet #4.
- config.txt: file comparible to the build.prop which can contain additional properties.
- oem: (OPTIONAL) Folder containing some additional apps. These are not automatically installed, but can be found in folder /oem/oem in your internal memory (internal SC card called USB) via the internal FYT file manager. Do not confuse this with the oem partition itself where the AllAppUpdate.bin will be installed to. So it is a folder oem inside the /oem partition, therefore: /oem/oem. I use this folder upon flashing to add some of my preferred apps that I want to have available, but not directly installed.
- vital-app (OPTIONAL): apks that are inside the vital-app folder inside the AllAppUpdate.bin are treated as apks to be installed AFTER the normal flash. So if a flash has been executed, and your system reboots, it will perform an "update". That is that it will at that moment install the apks in the folder vital-app.
- updatecfg.txt: Contains instructions for the flashing process
- Stm32ud.bin: (OPTIONAL) binary to flash the MCU
- GD32_E230_64K_Flash.Hex: (OPTIONAL) the hex file that contains the MCU firmware itself. These are very limited cross-compatible. do not flash these if your do not know exactly what you are doing.
I. (Factory) Firmwares
Some commands that can be put inside updatecfg.txt
Code:twipe_all # Wipe entire system. twipe_data # Will wipe data partition (but not /sdcard, internal memory). Wiping the /data partition will wipe all config, all 3rd party apps and updates of system apps. This is the same as a "reset to factory defaults" twipe_cache # Will wipe the cache of the apps thereby removing the temporary files that are stored for those programs. twipe_sd # Will wipe internal memory /sdcard (but not the data partition) dellapp # Remove all 3rd party apps make_updates # Make an upgrade U-disk boot file test # test unit and firmware before flash
Some properties that can be put inside config.txt. Say you live in Brazil and you want your locale settings immediately on Brazil, you can add that. As a second example we take a "Tesla style" unit which is actually a rotated horizontal unit. You see that we specify 0 from the rotation. This is because android is normally for portrait like screens. Our landscape models have a value ro.sf.swrotation=90 decrees as they are actually 90 degrees rotated. A Tesla style unit therefore is again 0 degrees and sometimes 180 degrees.
Or you want to improve the microphone function a little, you can add or modify the following lines:Code:ro.product.locale = pt_BR ro.sf.swrotation=0
If you decide to download a 4pda Russian modded firmware, make sure you remove the settings from this config.txt file that makes this a Russian firmware (unless you are Russian, but in that case you probably would not be here).Code:persist.sys.zlink.mic.vol=9.9 persist.audio.mic.senstivity=1 persist.btmic.gain=10 persist.btspk.gain=7
28-05-2023: I added two scripts in post #3 under bullet #4 to let you flash any AllAppUpdate.bin to your uis7862(s) or uis8581a unit.
II. AllAppUpdate.bin
III. The 6315_1.zip or 6316_1.zip
Again: the 6315_1.zip is the kernel for the uis7862. The 6316_1.zip is the kernel for the uis8581a.
(Inside also "III-a. More details about the files inside the 6315_1.zip/6316_1.zip and how to decompress and unpack/"open" them" and "III-b. Recompress uncompressed images from the 6315_1.zip/6316_1.zip to squashfs format for small (!) and easy access. (Not for flashing.)")
IV. Some info on partitions
V. The lsec_updatesh folder, lsec6315update/lsec6316update binary and 7862lsec.sh/8581lsec.sh script (and what about "universal" scripts)
VI. Compatibilty between uis7862 (ums512) Firmwares
VII. FYT firmware types over the different CPU configurations
VIII. Flashing a Full firmware, an AllAppUpdate.bin or a new system/kernel/core from another reseller
IX. If everything goes wrong and your unit ends up in a boot loop or doesn't get past the boot logo.
34Backup the application data of your uis78672 (ums512) unit (or your sc9863a (uis8581a) unit).
This is especially useful if you do not have an official firmware from your supplier yet. The kernel/cores are universal on these FYT uis7862/uis8581a units, but the AppUpdate is not.
This works on both the uis7862 and the uis8581a. I don't have this ui8581a unit but it is actually the same for these two types of FYT units.
It will actually also make a backup of your sc9853i unit, but there it requires some extra follow up steps. Next to that: There are already many firmwares that can simply be downloaded.
Changelog:
21 November 2023: Changed back to 7zip and took some more time to study the myriad of options.
15 October 2023: Changed 7zip to zip. Added options to:
- zip symbolic links as links and not try to follow the link (inaccessible system partition files. 7zip does not have this option)
- Do extensive verbose output
- Copy output to log file (AllAppUpdate.bin.log)
This script will create a directly flashable backup!
appBackup-V1.2 script
- Unzip the contents of this zip onto a clean usb-stick.
- Insert it into your unit and let it reboot.
- It will make a backup of the specific firmware part into folder BACKUP onto the USB-stick (which should therefore have >1GB free space).
- After the script is ready, you will get a green increasing counter telling you to remove the usb-stick. Do this after 4~5 seconds (or later). The system will automatically reboot.
- When it is done and after removal of the usb-stick, you will have four (4) files in this BACKUP folder on your USB-stick: AllAppUpdate.bin, config.txt, lsec6315update or lsec6316update, and updatecfg.txt
- If you copy these four files to a clean usb-disk and also copy an 6315_1.zip (for uis7862) or a 6316_1.zip (for a uis8581), you can always restore your unit to its factory settings.
After running the backup script:
Do check after the backup on errors. Do read the "AllAppUpdate.bin.log" inside the BACKUP folder. You might not understand everything, but if there is a line wth "ERROR" or "WARNING", you can copy it and report back.
Restore option I:
For a uis7862: Copy the AllAppUpdate.bin, config.txt, lsec6315update, updatecfg.txt from the BACKUP folder onto a clean USB-stick. Insert that one in your unit and let it flash your unit.
For a uis8581: Copy the AllAppUpdate.bin, config.txt, lsec6316update, updatecfg.txt from the BACKUP folder onto a clean USB-stick. Insert that one in your unit and let it flash your unit.
Restore option II:
In case option I still gives you an unstable system, you need to do a complete flash. For that you also need to flash a new kernel/core.
- Download whatever FYT firmware (but not T'eyes) for a 7862 and take out the universal kernel/core 6315_1.zip . (For a uis8581 copy out the 6316_1.zip)
- Only copy that 6315_1.zip (or 6316_1.zip for a uis8581) to the same USB-stick which you used in "option I". This means that this content will be added to the USB-stick. It will not replace the content.
- Insert that one in your unit and let it flash your unit.
27Mods and Tweaks
==================================================================================
1. disable or (re-)enable the mediaplayer at startup/wakeup.
FYT mimics the behaviour of many builtin car units that it continues with the player or radio or BT connected phone player, that was active during "switch off". These 2 scripts can disable that behaviour (I want silence when I start my car) or enable it again (default FYT behaviour). This is a shameless copy of @gordgelin scripts with a slight modification where @gordgelin adds the command at the 16th line whereas most standard firmwares have max 8 lines or so. My script simply adds the line to 4th line of config.txt. Works on uis7862 (ums512), sc9863a (uis8581a) and sc9853i (could easily be ported to other FYT units as well).
Note: When you restart the car within 3~4 minutes, so before the "deep-sleep" really has set in, it will still play.
==================================================================================
2. Correct the fytmanufacturer id of your unit/MCU in the fyt.prop
Do this in case you get a big yellow bar with red letters in the top of screen saying "UI and MCU does not match". It means that the property fytmanufacturer id (ro.build.fytmanufacturer= XY) is incorrect. (See also Q13/A in post 1 and section II. and vI. in post 2.
Option 2a.
Take the config.txt from your firmware. Add the correct ro.build.fytmanufacturer to the config.txt. Only flash this config.txt with a lsec6315update/lsec6316update to your unit.
Option 2b:
If you still know the original id, you can use below linked script to correct that entry again without completely reflashing your unit.
Read the README.txt carefully !!
You can download this script: ChangeFytmanufacturer
==================================================================================
3. Script to correct the screen orientation of your unit.
Probably you are here because you did not read the Forum well enough (especially "VIII. Flashing a Full firmware, an AllAppUpdate.bin or a new system/kernel/core from another reseller" in post #2 and flashed a firmware to your FYT with a different screen orientation.
What does this script do?
It can set the correct orientation for your screen. This is set by a property called "ro.sf.swrotation=xy", where xy is a value of 0, 90, 180 or 270 . Use the value from YOUR ORIGINAL firmware in the config.txt.
You will find a config.txt with this script that contains the default value for most units being ro.sf.swrotation=90
In case you have no longer your original firmware you simply need to experiment with the above values until you have the right one.
You can download this script: ro.sf.swrotation
==================================================================================
4. Two scripts to flash any FYT AllAppUpdate.bin to your unit.
EDIT: Some of the new Mekede M6Pro models and comparables from other resellers come with an lcdconfig for their 2000x1200 K screens. My scripts below do not take those files into account. I "think" that when you encounter an lcdconfig on the new downloaded firmware, you have to remove it and stick to the one installed on your unit.
What do these scripts do and how to use them
These scripts are for both the uis7862 (ums512) and for the UIS8581a (sc9863a).
The AllAppUpdate.bin, that contains the FYT application layer, is for both CPUs the same.
The scripts make a copy of your current config and use that to flash your unit using that config of your unit.
Some information to start with
FYT units do have an MCU and based on the type of manufacturer you can have a different MCU firmware. This MCU firmware is totally different from the normal downloadable firmware that you can get for your unit having new functionality, bugfixes, etcetera..
The Android layer is universal on FYTs but works slighly different for different MCUs.
How this Android layer should act on the underlaying MCU is determined by a property called ro.build.fytmanufacturer which can have several values.
A second and third property are the:
- sys.fyt.bluetooth_type property which is normally 0 or 1, but on the new M6Pro/M6Plus models anything up to 7
- ro.sf.swrotation. This property defines the screen orientation and is in 95% of the cases 90 (degrees), for Joyings often 270 and for Tesla screens (0 or 180).
Important
BEFORE YOU FLASH ANYTHING TO YOUR UNIT, YOU FIRST NEED TO RUN THE "PRE-FLASH" SCRIPT !!
Steps to perform
- Take a clean FAT32 formatted USB-stick (or a (micro-)SD-card in some USB reader/writer).
- Copy the contents inside the "pre-flash" folder onto the USB-stick (not the pre-flash folder with contents, but the contents inside the pre-flash folder).
- Insert it into your unit, let it reboot and go into recovery mode, and wait until the green message tells you that you can remove it again.
- Delete the "lsec_updatesh" folder including contents on your USB-stick !
- Make sure to keep the "myconfiguration" folder and check its contents: It must contain a config.txt and a fyt.prop. If correct: copy this myconfiguration also to a save place. You never know when you need a backup. If the folder does not contain those files or one of them, then don't continue but ask in the forum.
- Copy the AllAppUpdate.bin that you downloaded somewhere onto the USB-stick.
- Also flashing the 6315_1.zip or 6316_1.zip?
- UIS7862: If you want to flash the kernel as well, copy the 6315_1.zip onto the USB-stick.
- UIS8581a: If you want to flash the kernel as well, copy the 6316_1.zip onto the USB-stick.
- Now copy the contents of the "flash" folder onto the USB-stick.
- Check your "lsec_updatesh" folder. Do you now also have a "lsec_updatesh (1)" folder, or inside the "lsec_updatesh" folder something like a "7862 (1).sh"? It means that you did not delete the "lsec_updatesh" folder on the USB-stick, or that your file manager does not overwrite on copying. In this case: Redo step 4.
- Copy (not move) the config.txt inside the "myconfiguration" folder into the root of the USB-stick.
- You can now flash your unit using this USB-stick.
Remarks
- If you are thinking of using this in combination with @mariodantas' kernel, you need to know what you do. Mario's kernel comes with its own scripts and fmc app. Of course you can combine this if you know what you do, but do not simply copy everything on top of each other on this USB-stick. Please keep it separate.
- You can also combine it with PeaceOS, but also in this case @LLIyT_HuK's version comes with it's own scripts. So know what you do.
- The flashing script uses "twipe_data" in its "updatecfg.txt". This will clear your settings and all 3rd party apps which you downloaded from the Play Store or sideloaded from other locations. You can disable that by putting a # in front of the twipe_data line, but that is your own responsibility.
- Most newer firmwares nowadays come with an lsec script and a fyt_build.prop. This fyt_build.prop comes with a fake property to set Android to 11 or 12. I refuse to go with that absolutely incorrect and despicable behavior and I will not copy it.
- Once you have made your pre-flash copy of your config, you can also use the flash script to copy any modified fyt.prop or config.txt to your unit without using an AllAppUpdate.bin.
You can download both scripts in one zip: flash_any_AllAppUpdate.zip13I created a new thread for "FET". See here https://xdaforums.com/t/fet-fyt-extra-tool.4653315/
Hi guys and girls,
As fmc is not around anymore, and being ill this entire week giving me a 1~2 hours a day that I am not exhausted, I decided to pick up an anbandoned "piece of work", being my FET programme (Fyt Extra Tool).
This is a very basic, "ugly" tool. If nobody is interested I most probably stop again.
If users are interested ....
Anyway some screenshots inside the spoiler (Click images to see fullscreen)
Buttons with "the android with root on its chest" require root access.
The 3rd screen is a "Dutch" screen. I started to make translations, but that took too much time. For some languages I can almost do it completely myself, for others I do not have a clue. If you want it in your language, you do the translation.
Dear translators (whoever): Please take the strings from the attached zip. DO NOT use the strings from a decompile apk. It contains a lot of garbages from the other libraries built in.
See attached the current languages, but only very partially translated (using https://www.deepl.com/translator).
And attached the apk. Simply install it as any other apk (no lsec script, just plain install)
EDIT: Latest apk version in post #3707.
Edit: Note that the first ZIP option is only for non-Teyes FYT devices, but no system/error checking yet.
Edit2: You first have to set a pincode before you can lock the screen. No error checking there either.
