yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
I did not understand what you meant, but now I do. I will remove the OK button. It is a standard dialog, but I will change it to the same dialogs as for the long-running actions (The zip function and backup function), which do not have a button.

The popup should actually stay there until the "green" flash message appears.
[FYT Android Head Units] wipika1:
Attached translation to Greek. Thanks again for all the work!
[FYT Android Head Units] surfer63:
Thank you.
[FYT Android Head Units] Gscipione:
Attached translation to Italian. Thanks again for all the work!
[FYT Android Head Units] Moldeb:
Ok - so I thought I'm too impatient and tried again: Did the test again and didn't hit OK at the first pop-up (info), just waited longer for the second pop-up (start flash) to show - but it doesn't. It only comes up e.g. after a reboot but once it comes up the flashing works ok.

Maybe this is due to the fact that I have two external memories on that unit (MicroSD and USB-Stick)?

Interestingly, I stumbled over another issue on my second unit: In that unit, I had no external memory when I tried to edit config.txt. I got no errors but when it rebooted to flash, it didn't - only showed a fastboot logo briefly then booted into the system. The FET log showed successful copies to external memory (which was however not present as mentioned). I then inserted an empty USB stick, tried the edit again et voilà, flashing worked.

Or maybe have FET check for external memory (or verify the copying) - just in case others are as stupid as me or have a corrupted external memory ;)
[FYT Android Head Units] surfer63:
The mechanism is that I write to External Storage, which is actually the internal memory (INTERNAL in the standard FYT file manager ->32GB/64GB/128GB/256GB and then of course what is left after 2~5 GB of firmware). When the writing has finished, I stop the USB bus and restart the USB bus. This triggers the RKUpdate service which then checks all mass-storage for an lsec6315update (or lsec6316update) and thereby triggers the flash. The lsec script does it work and then removes the lsec631Xupdate binary.

As simple as that and already used on the Sofia's and PX5 units.

What kind of unit is that? Don't you see INTERNAL memory when you open the FYT file manager?

In that case I really have to check. I never anticpated a unit without memory.
[FYT Android Head Units] Moldeb:
Some Joying 7862 - it has and shows plenty of free internal memory. But without sdcard / USB stick the flash attempt looked like the attached (it's a Smart car boot logo then briefly a fastboot droid then dark then Smart car boot logo again - I've cut off the system boot that followed). Back in the system, it would offer the flash again but it would fail again (circular). The circle only stopped when I added external memory and tried again.

View attachment 6072147

Edit: The fastboot droid is visible in only one frame or so before it gets dark - and next to it there's text "No command". Only spotted that using the slider in the video.

Frame exported for ease of reference:

View attachment 6072156
[FYT Android Head Units] surfer63:
Yes, I saw it. So somehow it is detected that there is an lsec6315update, which I write to external storage, but it doesn't see the lsec7862 script, or it is not there. It mentions the "no command" prompt (whih is also displayed when there is FYT layer in /oem and the zygote process can't continue).
[FYT Android Head Units] honda2015:
I managed to install the newest version of this apk from thread 1 but it couldn't be opened. An error like app can't open popped up.
[FYT Android Head Units] surfer63:
Please uninstall and try to reinstall.

I install (test) version after (test) version and never encountered this. Today I installed 3 versions without problem.

Edit: Just to be sure I used the 1.2.0 version and installed it again. It simply opens and functions. Then the new test version and it also opens and functions.

What kind of unit do you have?
[FYT Android Head Units] honda2015:
I have tried it again using v1.2.0 but to no avail. The fyt extra tool keeps stopping it says.

I have a mekede mk6pro 8+128.
[FYT Android Head Units] surfer63:
On your internal memory there is a folder FET_logs. Can you check if it exists and if it contains log files? If so, can you zip them and attach it to a post?
[FYT Android Head Units] honda2015:
Sure, here you go.
[FYT Android Head Units] surfer63:
It seems to stop after the magisk check and your unit is not rooted. That is when I disable the rooted buttons.

I will check tomorrow.
[FYT Android Head Units] hal752:
Not sure if this is user error (myself) or a change in the overall file structure used by dudu.

Anyway the app can't find the config folder. Will do some digging to see where they have relocated it.

View attachment 6072801
[FYT Android Head Units] surfer63:
Can you use my HWGetInfo apk?

I am curious to see the differences in partitions, file structures, locations, additional or removed properties, etcetera.
[FYT Android Head Units] hal752:
Looks like it can. Attached svreens of what it made. View attachment 6072808View attachment 6072809View attachment 6072810
[FYT Android Head Units] surfer63:
Thanks, but you should have a HWGetinfo.zip and a folder HWGetinfo with the unzipped files on your internal memory. Can you please share the zip?
[FYT Android Head Units] surfer63:
That's what I expected. A set of new properties:

Spoiler content hidden.

And the config.txt is actually a symlink from /oem/dudu to /product/ls/config.txt.

That's why my FET app can't open it.

With a good file manager, like Total Commander or Amaze or another, you could look at the contents of config.txt in /product/ls and copy it to internal memory or a USB-stick or so to checkl it. And a symlink in modifiable "/oem" can always be overwritten by a "real" config.txt.

In theory I could check for some "dudu" property and if it exists get the config.txt from /product/ls, overwite the symlink in /oem/dudu and then save the config.txt there.

I won't do that though. I do not know enough of DuDuOS right now.

And it comes with a number of modded apps and a number of new dudu apps.

But actually it is still 95% FYT.

(And I did not look at the dudu 6315_1.zip yet. That takes time and I had other things to do)
[FYT Android Head Units] surfer63:
Version 1.2.1 released

Correct layout locksceen (buttons were not evenly distributed)

Fix crash: handling of rooted buttons on unrooted unit

Updated EN/DE/IT/NL translations

Add new Greek translation (thanks @wipika1)

Before a "system flash: Change the "OK-dialog" to a "no buttons" alert dialog

(Settings Tab; root requiring function) Add option to enable adb over wifi and enable USB debugging

Still ToDo: Give users option to select where to store temporary data (files, scripts) before "system flash"

I will not do these requests. I do not expect many 7862 and 8581 kernels to be relased anymore now that the M7s are released which can also be used with DuDuOS. And PeaceOS is a random, generated link from Yandex. It would require me to release a new version of my app in case a new PeaceOS is released.
[FYT Android Head Units] Aran:
Great work.
[FYT Android Head Units] surfer63:
This is still not correctly working. It doesn't crash anymore on unrooted units (and I still have no idea what disabling buttons in a tabbed layout has to do with rooted or unrooted), but the buttons are not disabled. You can simply tap them and depending on the function, the application doesn't do anything (edit config.txt) or crashes (day/night mode device).
[FYT Android Head Units] ByBossX:
Hello, the Turkish translation is attached.
[FYT Android Head Units] surfer63:
Thank you. I quickly compiled a new (test) version which I did send to you in a PM.

Also with two new strings not in your file yet.
[FYT Android Head Units] Gscipione:
Update Italian version
[FYT Android Head Units] WarSpaz:
swedish translation
[FYT Android Head Units] surfer63:
Thanks.
[FYT Android Head Units] surfer63:
Version 1.2.2 released

Make check on rooting (both on SuperSu and on Magisk) more robust and display a dialog when choosing a rooted function on an unrooted unit

IT translation updated.

add Turkish translation (thanks @ByBossX )

add Swedish translation (thanks @WarSpaz )
[FYT Android Head Units] surfer63:
Version 1.2.3 released

autoclose of app on non-FYT devices didn't work. Part of code had simply "disappeared" (my fault of course). Now added again.

Polish translation updated.
[FYT Android Head Units] Bettman66:
I just wanted to test the lock screen and found that the tool doesn't start on the new medeke 7870 devices.

Not an FYT device.
[FYT Android Head Units] surfer63:
Your device is of course a FYT device, but my tool is currently only for uis7862 (ums512) and uis8581 (sc9863).

Next to that: I have no clue yet about the "internals" of the 7870.

I could not find the energy yet to dive into it :)
[FYT Android Head Units] surfer63:
What could work:

General: Collect system info, display config.txt (modified for 7870)

Bluetooth: Open default Bluetooth Settings

Settings: All

Lockscreen: All

Triple dot top-left menu: All

Maybe (and only maybe) I will have a look next weekend.
[FYT Android Head Units] Bettman66:
To this day I still don't understand why all firmware manufacturers don't support a lock screen.
[FYT Android Head Units] surfer63:
Yes, that is indeed strange. Most standard builtin car units do have a "valet" mode enabling you to lock your unit. And some even allow you to access your unit, in valet mode, via your phone.

Anyway: Can you run my HWGetInfo apk (from my signature) and share the results?
[FYT Android Head Units] Bettman66:
I've already done that and will make the files available after work.
[FYT Android Head Units] surfer63:
Version 1.2.4 released

Implement "multi-window" functionality. That is: make it compatible for split-screen.

I realized this morning that my own app did not support split-screen. And it is so easy: 3 lines of (the same) code in every Activity.

(click for full size image; here displayed function: Edit config.txt)

View attachment 6076921

FYT needs to recreate some layouts, but if they spend an hour (max.) on every "old-fashioned" app (music, dvd, BT, radio, some others) they are ready.
[FYT Android Head Units] surfer63:
Version 1.2.5 released

First implementation of M7 7870 functionality

renamed apk to internal app name being xyz.hvdw.fytextratool.apk

Implementing the 7870 functionality was less work than expected. Of course the functionality is limited as we do not have rooted units on the 7870.
[FYT Android Head Units] Bettman66:
The tool starts correctly.

I can set the pin in the lookscreen menu and lock/unlock the device.

At the top of the status bar, all buttons work, as does the message center with all quick settings except for the back button.

Maybe I misunderstood the lookscreen and only the tool is blocked?
[FYT Android Head Units] surfer63:
I might completely remove the lockscreen.

The lockscreen does not work with "physical" buttons on your unit as that is outside Android and directly handled by the MCU.

I did not realize that the statusbar also overrules the lockscreen. I will test tonight.
[FYT Android Head Units] Specy01:
Congrats on your app @surfer63 . I still have to try it thoroughly, but I already find it fantastic and well made.

I just tried "Lock my unit" but it doesn't seem to work for me. I have no physical button. My HU is a Navifly M700S with Mekede firmware and is not rooted. I only have touch keys on the left of the screen. Does this mean that "Physical button" also includes touch buttons?

Also a suggestion: in the first tab, the first button is: "zyp fyt apps to AllAppupdate.bin" with the Italian translation (and in english linguage) it is not clear that clicking on it takes the backup of the AllAppUpdate.bin, or at least, This wording doesn't seem very intuitive to me, wouldn't it be better to add the word "backup" in order to better understand what it's used for backing up?
[FYT Android Head Units] surfer63:
Yes, all buttons not part of the Android screen itself are physical buttons controlled by the MCU and forwarded to com.syu.ms.

Fine with me. If that makes it clearer for users we will change it. I updated the translatable files in post #1.
[FYT Android Head Units] Bettman66:
Medeke 10.36 '' 12GB/256GB

I have no "physical" buttons.
[FYT Android Head Units] j0hn83:
The lockscreen has never worked correctly, with or without buttons. It is just much easier to bypass with buttons.

Some buttons on the steering wheel even bypass the lock.

You also had a brand new platform that this app was not made for. It was only tweaked to work on 7870 yesterday.

That it does not work has been mentioned lots of times in this thread and others. @surfer63 left the lockscreen in the app trying to be helpful in case it might work for some people or incase someone else fixes it themselves.

If you need a working lockscreen you will need to modify the heavily obfuscated com.syu.ms.apk file
[FYT Android Head Units] newuzer1:
personally, i have very little trust in the security/privacy of these chinese units and for that reason use a throwaway 'car' google account and def do not link/sync personal data. there's nothing in my unit that i have a need to lock but had i felt the need to lock it, i'd be pursuing a solution via tasker (or similar automation app) although the same shortcomings may be there as well. Or depending how frequently i intended to lock it - a hidden kill switch.
[FYT Android Head Units] surfer63:
Tasker or any other app has the same limitations and more, as those buttons in the screen bezels are not controlled by Android, but by the MCU. Which means that Tasker or any other Android app can't control them either.

And note that Tasker and Tasker-alikes use the Android KeyboardGuard. FYT, like all those other car head unit manufacturers, removed the KeyboardGuard. This means that Tasker or any other Android app even have less options to protect your unit.

That's why Mario and I used an external library that does this without using the KeyboardGuard. But alas: then come those "annoying" buttons on the side/bottom of the screens.

The only option is to either modify the com.syu.ms directly, or use Magisk + LSPosed framework + Xposed module to hook the code inside com.syu.ms that reacts on the MCU.

That's the only reason I upgraded Magisk to v27.0 in my kernels. To be able to use LSPosed and Xposed modules. For the rest Magisk V23.0 also did an excellent job and everything you actually need in a "normal" rooted device.

But I have more plans than free time and my programming skills are really limited.
[FYT Android Head Units] Bettman66:
That's not a big problem, the "Fully Single App Kiosk" app can do everything, switching it off is a bit tricky but you only need it if you want to change something in the settings.
[FYT Android Head Units] surfer63:
Does that one block the home key next to/below the screen? I certainly do not mean the home key and back key in the status bar. I really mean the hard/soft button next to the screen or below the screen.

And if you reset the unit (simple needle tap in RST hole), will it boot in standard Android or again in the kiosk app?

If it doesn't do that it is just as useless.

But if it does it might be a good replacement.
[FYT Android Head Units] Bettman66:
I can test that.

The app is set as the launcher and another app is set as the primary app. I chose the FCC Launcher as the primary app, but you can't select the default launcher. You select the apps you want to start like Dab-Z etc. and the rest is blocked, including the settings.

edit: The Fully kiosk app survives the reset and is still the launcher.

Fully Single Kiosk App
[FYT Android Head Units] comiflor:
Hello! I encountered a problem. I have two apps that I would like to set to the "dark mode". Google maps and Scoober (Just eat delivery). I had rooted my unit with the universal tool from here and installed the FET app, updated Magisk and granted superuser rights to FET app but after the reboot nothing happens. Are there other options to set those two apps to "dark mode"? Thank you for all your help and work.
[FYT Android Head Units] surfer63:
Why?

For google maps see here: https://www.howtogeek.com/772860/how-to-enable-dark-mode-in-google-maps-on-android/
[FYT Android Head Units] comiflor:
Thank you man. Really appreciate the patience. The problem is that the other app Scoober has some buttons that don't appear on the display of the HU from where I could change it. On any other Android phone they are displayed but on the HU not. It is a bit annoying when driving in the evening because the hole screen gets white and it is not so pleasant for my eyes. Again many thanks for the help and the patience. I do not have the time now but I will add some screenshots later to this post for you to see what I mean.
[FYT Android Head Units] surfer63:
Version 1.2.6 released

Add top-right menu entry to display used Open Source tools

Add first (and maybe final) implementation of fytcanbusmonitor (based on: github ; XDA)

It also comes with a number of new translatable strings.

I added a new tab called "System" (translatable. Android makes tab names always uppercase), currently only containing one button.

(click the image for full-size version)

View attachment 6078084

When you press the button you first get a selection popup allowing you to restrict what is being read to prevent a total overload of information.

View attachment 6078085

You can read that I mention "maybe final". That is because CANbuses are a total mess as car manufacturers do not (have to) comply to a standard at all. Every car manufacturer uses different codes and these codes are even different for newer and more luxuruous cars (expansion from simple mechanic air-conditioning to mulit-segment automatic climate control, etcetera).

So actually I am pretty disappointed.

And with regard to the "Main: No Canbus needed". This is actually what the com.syu.ms can directly access, either from Android or via the MCU.

But even there I can't find the codes and their "translation" inside the com.syu.ms. @fagner already indicated that code 114 is the Car battery voltage. This seems to be correct as my OBD dongle says more or less the same, but always slightly higher (is this terminal voltage versus source voltage?).

I do appreciate users mentioning what code corresponds to which value. Anyone that can help "translating" the codes to values like "114 -> Battery Voltage" can download a free version of the FET tool ;).

And mentioning OBD: OBD is a worldwide standard that all cars should follow. It might also be the reason that DuDuOS also implements OBD widgets in their launcher/OS. TPMS, car voltage, speed, fuel consumption, etcetera is always the same. It might be easier to write an OBD interface as there are many Open Source apps as well (AndrOBD) for example.

This is not something I will do. There are many good apps available, better than I can make.
[FYT Android Head Units] Gscipione:
translation in Italian of the last version of FET.
[FYT Android Head Units] Moldeb:
...and here come the German strings
[FYT Android Head Units] surfer63:
Version 1.2.7 released

- Italian and German translation updated

- FYTCanbusMonitor: code 114 (battery voltage) and code 101 (speed) translated. Rest not.

It is just the continueos updated row of codes that passes by when choosing (only) Main.
[FYT Android Head Units] aiui:
Thanks @surfer63 , you've done a great job, I feel like I already owe you another beer, just one question, will we be able to see the voltage in the taskbar?
[FYT Android Head Units] surfer63:
Yes, but not via my FET app.

After approximately September 2023, FYT added Voltage in the statusbar for some units (but that has nothing to do with the fytcanbusmonitor or my app). Next to that some more features were added for the M6 and other models.

@LLIyT_HuK and I discussed what we could find in the SystemUI, and what we could use.

Inside the SystemUI there are many statusbar_<type>_<brand> xml files, and sometimes per resolution or horizontal/vertical.

In the (smali) code (inside com/syu/cfg) are a number of config files, each with a fytmanufacturerid like Config_001.smali, Config_095.smali, Config_116.smali (etcetera).

So, the SystemUI statusbar can be configured almost per unit/brand.

LLIyT_HuK already made a SystemUI with Voltage in the statusbar based on the M6Pro systemUI, but it needs some more fine-tuning.

As LLIyT_Huk is the expert, I leave it to him to do the mods.

So just be patient.
[FYT Android Head Units] marjanoos:
Today I've checked this canbus data display and no matter which option I choose, I'm seeing all the data (not much though)

View attachment 6080208
[FYT Android Head Units] surfer63:
I will check this weekend.

One question though: Do you have a canbus?

Edit: If you do not have a CANbus, you will only see Main, whatever you select.

And Main is not much. The Canbus options show a lot of data esepcially when the motor is running and you are driving.

Note also: all data is written to csv files. CAN<timestamp>.csv in Interal memory. I did not change that from the original code.
[FYT Android Head Units] marjanoos:
Yes, I have a canbus (I mean data bus by that, but I also have a decoder).
[FYT Android Head Units] Adamados:
This sound interesting to me,

My car is a VW Golf 7 and because of a DIY user i own VCDS OBD interface and their software.

I think via VCDS i could read Canbus data and if our FYT could read them too then i suppose i could match
[FYT Android Head Units] surfer63:
Perhaps, but like explained above: It is different for each car and Canbus-decoder. So your Golf 7 is different from a Peugeot or Toyota, etcetera.

Your code 1017 is not the same as on another car.

For OBD this is standardized.
[FYT Android Head Units] surfer63:
You are completely right.

Only when using Main, you skip the CANbus, but as long as one of the CANbus options is selected, you simply get everything that flows through the CANbus.

The four "calls" (main, canbus, sound,canup) are actually only two calls: a non-canbus (main) and a common "show everything" canbus call.

I though that the library gave me a choice :)

Maybe it is best to only mention Main and (general) CANbus.
[FYT Android Head Units] fabiodedo:
ITALIAN translation of FET version 1.2.7
[FYT Android Head Units] surfer63:
Thank you, but did you compare with @Gscipione's translation from post #123?

I do see differences, but how do I know which is the best Italian translation. Did you use his translation (from the translation ip) and improved it?

Note also that in Gscipione's translation the strings are correctly "escaped".

<string name="app_theme_dark">Imposta il tema scuro dell\'app</string>

In your translation they are not.

<string name="app_theme_dark">Imposta il tema Scuro dell'app</string>

The "dell'app" should be "dell\'app".

I do not understand where your translation is based on.
[FYT Android Head Units] fabiodedo:
I had seen that in the English version there were more strings than the Italian one (I think because the English one is updated to 1.2.7).

I improved the translation compared to that of Google Translate.

I corrected the file, now the strings are correctly "escaped".

I had also translated Mario's FMC.

PS: what exactly do you mean by the "Canup" option of the fyt canbus monitor?