yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] LunaEros:
You can use Surfer's HWGetInfo apk and it will create a zip file with all of your units pertinent info. Post that up here for him and everyone.

---------- Post added at 10:24 AM ---------- Previous post was at 10:21 AM ----------

Well I can use any launcher now but they stay on the left of the clock since they don't get rid of it.

Can I rename that file still considering I already took the root off and flashed my stock boot image back to fix my system?

If it breaks something would I be able to rename it back to fix it?
[FYT Android Head Units] xadamadax:
TY - I'll get the HWGetInfo file uploaded today
[FYT Android Head Units] surfer63:
See attached two lsec.sh scripts.

You might need to make one of your 3rd party installed launchers as default launcher before you use the scripts.

I can't test them myself, but I guess they work fine. If they do work fine, other users having this launcher+window apk combi and being sick of it can use it as well.
[FYT Android Head Units] LunaEros:
Thanks, Surfer! I'll give them a try a little later when it cools down. :D
[FYT Android Head Units] xadamadax:
HWget_info YEE T R, generic sc9583i, FYT, 768x1024, portrait

Attached, thanks again
[FYT Android Head Units] surfer63:
Well, you already knew that you had a FYT.

From the properties.txt you can find all used fyt and syu properties which are specific for the unit.

If you want to flash a Joying firmware or T'eyes SPRO firmware, there are a number of properties that need to be changed.

Your manufacturer id is 1 ([ro.build.fytmanufacturer]: [1]). => fyt.prop; needs to be altered in the Allapp.pkg

Your bluetooth type is 0 ([sys.fyt.bluetooth_type]: [0]), just like the Joyings. => in the config,txt

The default fyt user id is 2 ([ro.fyt.uiid]: [2]), where it is 6 for the Joyings (also in fyt.prop). As such that is not important if you would flash a Joying firmware (or T'eyes SPRO firmware) onto your unit.
[FYT Android Head Units] LunaEros:
You are awesome Surfer!! The disable window script got rid of that damn clock so now I can use the entire screen! WOOHOO!

It's too bad they didn't have the foresight to make that clock swipeable to where you could just swipe it on and off the screen as you needed it. Because it's not a bad looking clock but it just takes up too much space.

Unfortunately I don't think the ringtone replacement worked. I don't have any way to test call my phone while connected to the HU to tell so I'm not 100% sure that it didn't but when the script wrote everything, one of the lines was in red that said something like it failed on writing the blink_ring.mp3
[FYT Android Head Units] surfer63:
I just realised (realised as in British English ;)) last night that the new SC9853i models have a blink_ring.mp3 in /oem and a softlink in /system (blink_ring.mp3 -> /oem/blink_ring.mp3). So FYT deviated from the standard they used in all their previous models.

Sorry.

Attached a corrected script.
[FYT Android Head Units] tchleb:
Does the MCU firmware also have to be changed?

BTW do you know if the stm32 / gd32 is locked (read / write over SWD).
[FYT Android Head Units] LunaEros:
Still don't think it worked. Getting the same message.

P{retty sure this is the line that's in red that says "fail!!" After it.

cp /storage/sdcard1/lsec_updatesh/blink_ring.mp3 /oem/blink_ring.mp3

Would it be easier for you to figure out with the results of that new deeper scan script you made. FYT Get Info?
[FYT Android Head Units] surfer63:
I used that info.

But first:

What are the contents of your USB-stick? Did you copy your own blink_ring.mp3 into the lsec_updatesh folder?

I just tried my own script and it works great. I do not get an error message and it simply does what it has to do (be it the wrong action).

Guessing that you're a windows user: on linux (underlaying system of Android) and on Android itself, there is a difference between uppercase and lowercase letters. It has to be blink_ring.mp3: all lowercase!

Anyway: that is still not correct.

I never felt the need to change the ringtone, but on the Sofia and the PX5 the folder was /system/media/audio/ringtones, like it has to be on Android, containing fyt.ogg. That is also how my JET app worked. I copied that to the SC9853i, but was corrected by two users mentioning that is should be /system/blink_ring.mp3. Although I could hardly believe that, but I changed my JET app and they said "it was now correct".

That is absolutely not correct.

But it is not /system/media/audio/ringtones/fyt.ogg either. I already tried that. The strange thing is that the fyt.ogg is indeed the "ring....ring...ring" sound. But changing that one (and I checked it) does not work.

When looking at the properties I find:

[ro.config.ringtone]: [Ring_Synth_04.ogg]
[ro.config.ringtone0]: [Ring_Synth_04.ogg]
[ro.config.ringtone1]: [Ring_Synth_02.ogg]

But that is complete nonsense. It is not used at all. No idea why that is in there.

Edit: like mentioned above: I really don't care about the ringtone. I will have a look at it, but it is low on my list.
[FYT Android Head Units] LunaEros:
Damn! Maybe that's what I did wrong. I don't think I had the ringtone in the folder. I had it in the root of the asb. I'll try it again. I can be a dimwit with Android. smh. Sorry.
[FYT Android Head Units] surfer63:
Not necessary. It does not give the desired result anyway.
[FYT Android Head Units] LunaEros:
It doesn't?

The ringtone I want to get rid of is this annoying loud kinda syth/orchestra type melody. I wanna replace it with one I made that's just a woman's voice saying "Incoming Call"

---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------

And yeah. I use Windows. But I did name it just like you had it in lower case as "blink_ring.mp3" I realize unix/linux based file systems are case sensitive.
[FYT Android Head Units] xadamadax:
Ok, so new question, lets say I wanted to include a navbar hider (immersive mode) app in the allapp.pkg. Take navbar hider for example (https://play.google.com/store/apps/details?id=in.tsdo.elw&hl=en_US).

If you were to just download the app from the playstore you would have to run an adb command to enable proper keyboard usage.

My question, is there a way to include this adb command (or, rather, set this permission) in the config.txt or lsec.sh script? I am assuming yes. I have to go to my car to open the app to get the exact ADB command, I can add that shortly.

This way i could include the app in my allapp.pkg and the app would work correctly from the get go.

thanks in advance
[FYT Android Head Units] surfer63:
This requires either root access or adb on a "debug" system. Our SC9853i systems are built as "release" systems. That means that adb does not get root access ("adbd cannot run as root in production builds"). You can activate adb but it will still not allow to set immersive settings. (Not for nothing it is call Android "Debug" Bridge)

But you do indeed have the option to use an lsec.sh script. You could write an apk that asks the user for a clean flash drive. Write the appropriate script that enables/disables the navigation_bar/status_bar/both. The unit will detect it and ask for a reboot: done.

You could use the same way to disable specific apps from using immersive mode.

I have been thinking of such an apk, just like my JET apk, but something like "SC9853i_FYT.apk" (a really catchy name, I think ;)). I have now written a number of scripts. It would be much easier to simply do that from one apk.

Next to that: I already wrote earlier that it would be quite simple to extend my HWGet_info apk to get the necessary data from the current "original" firmware and write that as a "zipped" script. Copy any FYT compatible firmware (Joying, T'eyes, Funrover, Zhan, Whitson) to a clean flash drive. Unzip that zipped script to the same flash drive, and flash it to your FYT compatible unit. That way you can test which firmware you like most.

But currently I am lazy as my unit does what I want it to do (apart from Google voice calling). So I have no idea when or even if ever I will start this apk.
[FYT Android Head Units] xadamadax:
well, i definitely love the apk name :D Surfer, thanks again
[FYT Android Head Units] LunaEros:
Hey Surfer!! Don't get rid of that ringtone script you made for me. It actually does work. I was out this morning and got a call and realized after a couple rings that it wasn't that godforsaken synth ringtone anymore it was the "incoming call" voice I made and put in with the script. Awesome! Little by little I think people will be able to crack these newer FYT Android units to be like we all want like the old ones were.
[FYT Android Head Units] xman75:
Hello,

Can I use these mods for the VO101N4GS and VO101N4GS-R, sorry if this has been answered elsewhere but I haven't seen an answer in the forum search.

VO101N4GS-R

Intel Airmont eight-core 1.8GHz SC9853i (9.7" 1024x768)

4GB/64GB
[FYT Android Head Units] LunaEros:
You'll have to wait for someone like Surfer or Tchleb to show up for a definite answer to that. But I would think it's not out of the realm of possibility since I've heard you can put the firmware from other brands HUs such as Teyes and others because they are compatible with Joying's FYT units. I think it's primarily depends on exactly what unit you have. And if it's close enough to the units the particular mod you want to use was made for.

Surfer will have to know exactly which unit you have to be able to tell 100%.

Grab the HWGetInfo. apk out if his signature line in one of his posts, install and run it. It will create a zip file with all the specific HW and SW info he'll need to tell and post it on the board for him.
[FYT Android Head Units] surfer63:
That is a Joying FYT with the 9.7" screen and a 1024x768 resolution. Your firmware has only a few modifications like the setting "com.android.systemui.is.switch=true".

The mods from post 228 will all work and I guess the others as well.

There might be one exception being the radio because your resolution and screen ratio is different. 1280x720 and 1024x600 and 800X480 are all approx. 16:9. Your screen ratio is 4:3
[FYT Android Head Units] tchleb:
Yes this mods can be used for both joying head units.
[FYT Android Head Units] xman75:
Thank you! You are correct, I can change the radio apk, however the image is cut in half once I rotate the screen. i will apply other apks and settings to see compatibility with the 9.7" rotating screen. Thank you all for contributing to this thread, this is a great resource.
[FYT Android Head Units] gamer765:
[MENTION=2550900]surfer63[/MENTION], you think it'd be fine flashing a Teyes rom onto a Joying FYT unit? I'm kinda tired of the look of the Joying UI. All I've gotta do is modify the config.txt right?
[FYT Android Head Units] surfer63:
Post has been edited. Read again.

Yes, you can do that. Another user already did that (@lucasmm) although he doesn't have a Joying but a FYT compatible. I have also been thinking of doing it myself. It is not only the config.txt though that you need to modify. You also need to modify the fyt.prop inside the Allapp.pkg for the correct manaufacturer.

And I would do a clean install.

In config.txt remove

ro.product.locale.language=ru
ro.product.locale.country=RU
persist.sys.language=ru
persist.sys.country=RU

You don't need to alter the sys.fyt.bluetooth_type=1

In the fyt.prop you need to alter the id.

Joyings id =43, T'eyes' id is 95

So set it to:

ro.build.fytmanufacturer=43

(Some units also have "sys.fyt.mcu_cus_id=43" or whatever the id is of that reseller.)

Below has been edited

And to prevent errors I would do a clean install, thereby wiping everything.

Create an updatecfg.txt and add the lines "test" and "twipe_all" (copied from the first post of this thread)

test # test unit and firmware before flash
twipe_all # Wipe entire system

Remove the remarks with/after the hash tag. (I do not even know whether remarks are allowed.)

You need to do a "twipe_all". A lot of the apps are of course 100% the same but do have a different name. That would give conflicts as the old one would still be in place in its own folder and the new one would be put next to it in its folder. That would give 2 apps with the same package name. That is not allowed.
[FYT Android Head Units] surfer63:
I edited above post. Please read again.
[FYT Android Head Units] gamer765:
thank you, already figured as much regarding the updatecfg.txt. Already made my own SPRO firmware with the mediaserver mods. The CC2 version looks awesome, might look into that if the SPRO flashing goes well.
[FYT Android Head Units] surfer63:
He means the main server mods, like the extended one and the nokill one.

Yes, they have more or less the same bugs. That also stopped me from "migrating" so far.

I do have DAB radio, so I am totally happy. If I hadn't I would be interested in the radio mod that some dev(s) made and which shows station logos for the several stations (and you could easily use downloadable DAB logos for that).

It is location based and they use a lookup table, but only for Russia. It is relatively easy to modify that for other countries in the world, but time wise it's a huge amount of work. It is relatively simple: If you are in Zwolle on FM 102.3 you are on on Radio538 so show that logo. And then if your are in Paris on 102.3 you are on the ABCD station so show that logo, and in Berlin on 102.3 you are on the WXYZ station ..., .... and so on, and so on. But only for the Netherlands that would already be a huge task.
[FYT Android Head Units] mastrv:
This shows some of the customizations possible in CWG. Repeating images of themes from the http://carwebguru.ru/ site:
[FYT Android Head Units] Bronchi:
Hello, first of all thank you all for creating great tutorial and mods.

I have fyt compatabile model.

I installed radio mod from GitHub repo using tutorial from fist page (version 8.1, soiski71 folder). I changed apk name etc. and it's working ok.

However I still don't have RDS, I mean original app didn't show rds info either, but I thought that modded one will. Or I am wrong?

Any tips?

Somehow I can't upload hwget.zip but tell me and I will copy paste certain sections.

EDIT: OK, my bad I feel stupid.. I didn't turn on rds in radio settings...
[FYT Android Head Units] PaulBorges:
Hello again.

After the root sucess, thanks for the magisk solution. I need help with a volume knob. The sofia joying model i used the 1din front model of my car to make a DIY. I use the knob volume and a usb to send the volume up, down and mute. I changed the generic.kl file with sucess.

Now with this intel unit from joying this doesn't work. Some help be appreciated.

Thanks
[FYT Android Head Units] surfer63:
New pc app for SC9853i: FSE

Despite my words that I didn't want to spend more time on creating software, I started again

It is a java programme to make it cross-platform. It runs on Linux/Windows/MacOS/Chromebook (in Linux window), and probably any platform that runs java.

It makes a flashable USB-stick/SD-card for you for your FYT SC9853i.

It is is to do more or less the same stuff as the JET apk, but on the PC and you don't need a rooted unit.

See a 2min 22s screen capture video on Youtube. I ran screencapture software on Windows and on Linux.

Linux is my platform of choice, but as most users will be on Windows I also made a recording on Windows: the video starts with it.

It is just in very early state, but the current buttons work.

It contains "properties" files containing the strings being used in the program, so it can be translated.

But if nobody's interested, I stop here.
[FYT Android Head Units] LunaEros:
Very cool, Surfer! I see you DID see my reply about the ringtone script you wrote for me working.

Where is this new one? Is it that One Key app link you have at Github or where the Jet tools are?
[FYT Android Head Units] surfer63:
Not yet downloadable and not on github yet.
[FYT Android Head Units] LunaEros:
Ok. I can wait. :)
[FYT Android Head Units] xadamadax:
You know I'm interested dude! Thanks for putting in the effort, always appreciated
[FYT Android Head Units] surfer63:
First beta FYT_SC9853i_Extender

Hi,

A first beta of the app.

As said: it is a java application to make it cross-platform. It needs java 11 or newer (java-8 is already long time out of support).

For the Windows users I simply packaged it inside an exe and "delivered" the java 11 jre (java runtime environment) with it (see attached exe_plus_jre.png 2nd image).

Users on Linux and MacOS can simply install java-11 on their systems via the package managers or download it from adaptopenjdk.net. Simply select the version 11 jre (or newer) for your platform. Maybe later I might create a MacOS bundle and/or a Linux AppImage or .deb.

Windows users can find the zipped exe plus jre as "FYT_SC9853i_Extender-exe-beta.zip" from this Google drive link.

Linux and MacOS users can download the jar from this Google drive link. Simply start it with "java -jar FYT_SC9853i_Extender.jar".

If I continue I will put everything again on Github.

I added a progress message and an "indeterminate" progress bar on downloading bigger content (3rd image).

Currently in English and Dutch (obviously), but texts are quite rudimentary at the moment.
[FYT Android Head Units] surfer63:
Sorry. Beginners mistake. Google sharing was set to "only for invited", instead of "everyone with this link"
[FYT Android Head Units] seb21:
Hi.

Please set the permission on the windows version to download for everyone. For now we can only see, but not download.

Linux version is fine.
[FYT Android Head Units] LunaEros:
I downloaded it but the .jar doesn't seem to want to run. I have the latest Java on my system but I don't know enough about it to figure what's wrong. (shrug)
[FYT Android Head Units] surfer63:
Link was exactly shared in the same way as the jar, but it was indeed not working when using another id to download.

I removed it and uploaded it again. Above link should now be good, or use this one.

What do you get if you do a "java -version" on your system?

That .jar works fine on my Win10 laptop, on my Linux laptop and on my Chromebook in the "Linux beta" client.

Edit: I will start with the Github setup.
[FYT Android Head Units] LunaEros:
According to the About window it says Version 8 Update 251 (build 1.8.0_251-b08)
[FYT Android Head Units] surfer63:
That is not by far the latest version. That is the old Version 8 that is outdated and not supported anymore.

I already mentioned you need version 11 or newer.

If you want to use this jar, you can copy the jar into the folder containing the exe and the jre folder, or otherwise: create a new folder and copy the folder jre and the jar in that new folder.

Then you create a "FYT_SC9853i_Extender.bat" file, using below statements, and make sure to copy it in the same folder as the jar and the jre folder.

@echo off
set CURRENT_PATH=%cd%
set JAVA_HOME=%CURRENT_PATH%\jre
set PATH=%JAVA_HOME%\bin;%PATH%;.
java -jar FYT_SC9853i_Extender.jar

Then you can start the jar with the bat file and it will use the local V11 jre, and not your system wide antique version 8.
[FYT Android Head Units] LunaEros:
I guess I'll have to try that. Hope I can figure it out. I'm still on Win7 and Java is reporting that it's running the latest when I made it check for updates.

---------- Post added at 02:07 PM ---------- Previous post was at 01:56 PM ----------

Ok. The only folder I see with Java.exe is under this path..... C:\Program Files\Java\jre1.8.0_251\bin

But there is no JRE folder under that path. In fact the only folder I see with JRE i it is jre1.8.0_251 which is just under the Java folder which itself is under Program Files.
[FYT Android Head Units] surfer63:
Why don't you simply download the exe? I mentionted in the first post: "Windows users can find the zipped exe plus jre as "FYT_SC9853i_Extender-exe-beta.zip" from this Google drive link." And remember, as always, to extract with paths.

Why messing around with the jar?
[FYT Android Head Units] LunaEros:
Ugh. (smh) Becaaaause. Like I told you before, you're dealing with an idiot, Surf. I didn't see that link. My bad. (Walks away sheepishly)
[FYT Android Head Units] xadamadax:
Bang up job Surfer, thanks
[FYT Android Head Units] surfer63:
beta 2 FYT_SC9853i_Extender

Hi,

I expanded it a little.

Windows exe: here.

Universal jar: here. Note that you need java version 11 or newer in your path or environment.

Changelog:

- added radio mods

- split Other tab and add backup/restore tab. The restore is disabled as I did not finish that (but I'm done right now).

- add "get system info" on backup/restore tab. This does actually the same as my HW_Getinfo apk but due to the fact that the script is executed with root rights, I can collect more info.

Still from Google drive as github does not allow releases (downloadable files) bigger than 10MB. The "exe with jre" is 46MB. I have to find something about that.

Edit: And in case you see "weird" English texts, let me know. I'm not a native speaker (and I might mix up British English and US English: analyse vs analyze, etc.)
[FYT Android Head Units] LunaEros:
Very cool, Surf! Don't worry about the English. You do fine and Americans can read British English just fine anyway.

What do the radio mods do though?
[FYT Android Head Units] surfer63:
Nothing more than changing the look & feel: a skin. See attached.

Being a little bit creative and a little bit technical can do wonders.

See also older "skins" for several mods here: https://hvdwolf.github.io/Joying-RootAssistant/OtherMods-examples.html

See also older "skins" for (older) radio mods here: https://hvdwolf.github.io/Joying-RootAssistant/RadioMods-examples.html
[FYT Android Head Units] LunaEros:
Cool! And those work on the stock radio? What about those other stock apps in the first link?
[FYT Android Head Units] surfer63:
They are all old mods for the Sofia3GR. On the PX5 hardly any mods have been developed. Same for the sc9853i: Only my BW-RDS mod and Soisky's mod.
[FYT Android Head Units] mastrv:
Surfer63, thanks for all your hard work. Hopefully, I'll be able to use it on my head unit as well.

FYI, I remember reading something about backing up and restoring on 4pda. There was something about a timer / watchdog thread that automatically rebooted the unit after 5 minutes and 30 seconds or 6 minutes and 30 seconds...something like that. I think it's meant to handle cases where the unit hangs so that it can be recovered from. I'll try to find it and post back.

I'll also try to find some other radio mods that look good.

---------- Post added at 05:18 PM ---------- Previous post was at 05:05 PM ----------

Found the post. It was about loading TWRP into recovery. It sounded like it rebooted after 6.5 minutes. They recommended to backup to internal memory as it would be faster. Doesn't sound like they are sure about it, but something to watch out for.

Link: http://4pda.ru/forum/index.php?showtopic=936715&view=findpost&p=95352560