yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
I know that post (I regularly read 4pda) and I did not respond to it as I do not speak/type Russian (I never respond in 4pda although I sometimes very much want/like to). There is indeed a watchdog in the MCU. It checks for the correct recovery in place. If that is not the case, FYT writes the backup (/system/etc/recovery-resource.dat) to the recovery partition again so that it is 100% correct again. It does that on reboot (/system/bin/install-recovery.sh) and it checks regularly and then goes into reboot to fix it, but I do not know about the length of that timer.

If you speak/type Russian, then feel free to add that as reply :)

And with regard to backing up: I tested it and backing up to internal memory is indeed faster. But what good is a backup on internal memory? You need to copy it "somewhere else" anyway, otherwise your backup might be worthless on a crashed/boot-looping unit. And first saving it to internal memory and then to SD-card is much slower (and it makes the scripts more complicated). So I backup to the used flash drive (SD-card/USB-stick) so that if the user takes it out of the unit, he/she immediately has his/her separate backup.

Edit: I did not test the TWRP recovery image from 4pda. That also means that I did not test whether the original recovery is written back after reboot.

I did not check that as I can make backups anytime (now also via the app), and restore them anytime without needing the TWRP.
[FYT Android Head Units] xadamadax:
Ok, Allapp.pkg question, I'm having inconsistent issues and trying to isolate. I have 12 apk's i'm trying to load into an allapp.pkg. I am wondering what would cause checksum errors during the flash.

I put all 12 APK in got a checksum error when flashing. So i started with 1 of the 12, then 2 and so on until i got the error.

Here is where it gets strange. If i then create an allapp.pkg with apps that were working previously I get the same error... i have tried different combinations and can't figure it out.

I have tried 3 flash drives and both USB ports on the radio.

Any help is appreciated, i'm pulling my hair out. I'm doing this all on a test bench (not in the car), in case power has something to do with it, but my bench is 12v.

At it's peak, these were the APK's i was trying to put in the pkg

nova-launcher-6-2-10.apk

Screen Recorder Video Recorder XRecorder_v1.3.0.4_apkpure.com.apk

Speedtest by Ookla_v4.5.9_apkpure.com.apk

Split Screen Launcher_v2.3_apkpure.com.apk

spotify-8-5-51-941.apk

TeamViewer QuickSupport_v15.5.76_apkpure.com.apk

TeamViewerQS.apk

Waze GPS Maps Traffic Alerts Live Navigation_v4.61.0.3_apkpure.com.apk

1Weather Forecasts Widgets Snow Alerts Radar_v4.9.3.1_apkpure.com.apk

AParted Sd card Partition_vBaklayon_apkpure.com.apk

ECU Connect_v3.11.1_apkpure.com.apk

ES File Explorer File Manager_v4.2.2.5.1_apkpure.com.apk

Fulscrn Free_v5_apkpure.com.apk

Google Drive_v2.20.201.03.45_apkpure.com.apk

KWGT Kustom Widget Maker_v3.46b14609_apkpure.com.apk

thanks guys
[FYT Android Head Units] surfer63:
I don't know but what I see is

As far as I know they are the same and therefore have the same package name.

When you get the flash errors, are these two both in the Allapp? Trying to flash the same app (package name) twice, having different size and/or SHA1/md5sum checks might indeed give a checksum error.

Edit: I prefer apkmirror by the way, as it gives you SHA1/mds checksums under the "verified safe to install (read more)" link, which youcan check after downloading.

Maybe a bit paranoid, but that makes it more secure that you really get what you think you are downloading.
[FYT Android Head Units] xadamadax:
quick support and qs are different, QS is an addon for AOSP1 so that teamviewer will work

in fact those those two by themselves- when done alone in the allapp.pkg or when installed manually work totally fine. I have also tried without them entirely, no dice

thanks for the thought though!
[FYT Android Head Units] surfer63:
FYT_SC9853i_Extender beta-3

Hi,

for the time being this will be the last.

Some are packed with the jre, which is the "java runtime environment".

You can find them on my github.

"Open" the Assets under the text.

FYT_SC9853i_Extender.jar : This is just the full jar. It needs java V11 or better.

FYT_SC9853i_Extender-exe-beta3.zip : This is the windows executable packed with the jre.

FYT_SC9853i_Extender-beta3-Linux-x86_64.AppImage : This is an appImage for Linux. Download it, make it executable with `chmod +x FYT_SC9853i_Extender-beta3-Linux-x86_64.AppImage`, and run it from the command line or double click it from your file manager. It should run on any 64-bit Linux (I tested 5 distro's )

FYT_SC9853i_Extender-beta3-MacOS-x86_64_with_jre.zip : This is the jar with a shell script to start it and packaged with the MacOS V11 jre (This is not a bundle!)
[FYT Android Head Units] Hammerhand.17:
Hi, [MENTION=2550900]surfer63[/MENTION], I have a vertical fyt compatible unit. I've modified it with your software, and even achieved root, but there are two things I can't get, hope you can give me some help.

1. I've changed ringtone, but now when I receive a call I get no sound.

2. I've tried to avoid killing background apps, so I modified skipkillapp including the name of the apps I want to keep, but it doesn't work.

Then I've tried to use your jet software to use nokill mod, but it appears blank. I think it is because it's build dependent, and mine doesn't match with none of fyt (2019.10, if I remember well).

I don't even know if, being it a vertical unit, I could use one of the official firmwares, but I wish I could, at least, use the nokill mod.

I attach my hwget info for you to see.

Thanks.View attachment HWget_info.zip
[FYT Android Head Units] tchleb:
Upload your com.syu.ms.apk and I can modify it with the nokill Feature.

The apk is located at oem partition.
[FYT Android Head Units] surfer63:
Do you mean you have no ringtone, or don't you have sound during the call?

The skipkillapp did work in the 2019 March and April firmware, but then it seems FYT changed "something" as it indeed doesn't work anymore.

That could be an options as well, but you can also extract it from the Allapp.pkg in your firmware.

Coming to that: Do you have a firmware copy? And is your firmware one of the following? (copied from the Joying blog)

Those are from the joying blog but the latest firmware is from 2019-9-17.

And yours is 2019.10? I can't find that on the blog.
[FYT Android Head Units] Hammerhand.17:
Ok, attached it is.

I have no ringtone. It was a mp3 file.

Ok, so I better left the untouched one?

I don't have a firmware copy, seller didn't provide (and we didn't end in good terms, due to a sloooow shipping, more than 100 days).

I have a raw backup from your software. You can see the data of my firmware in the screenshots attached

This is why I attached hwget info in previous post, because I think this is not a compatible unit (it's a 1024x768 10.1 vertical unit), but some of your mods are working fine; I don't think I can use the joying firmware, but would thank you if you take a look.

Ok, seems like images didn't upload well: https://imgur.com/a/Uft9WqU
[FYT Android Head Units] tchleb:
But both files on the root of an USB Stick and flash the mod.

I also packed the stock com.sys.ms to an update .pkg for easy restoring to stock.

Enjoy:laugh:

BTW i would also create a raw backup of the oem partition.

You can add this line to surfers63 backup script.
[FYT Android Head Units] surfer63:
I did not add that, as it was a "we don't need that as we have an allapp.pkg".

So if you have a firmware, you can simply copy the lsec6521update and the Allap.pkg to a USB-stick and flash it. And your original oem partition will be back.

If you do not have a firmware, it is indeed better to make a backup of the oem partition as [MENTION=8637033]tchleb[/MENTION] advises. :good: Thanks. Good addition. I never realized that for my backup system script.
[FYT Android Head Units] Hammerhand.17:
Ok, thanks a lot, will tray as soon as posible and report back.
[FYT Android Head Units] mdepcz:
I have a problem with the size of the radio application, can it be adapted to the screen size?

The model of my radio is jy-hos02n4gs-2 10.25 inch

can you adjust the resolution of radio mod to 1280 * 480?

I will be grateful for any help.
[FYT Android Head Units] surfer63:
Not without putting a lot of time and effort into it. SYU/FYT has a dramatically bad way of building "the screens" for their applications. Instead of using the flexible auto-sizing options Android offers you, they build a screen for a specific resolution/ratio. And not only for the radio app, but for almost all of their apps. This also means they need to build and compile their apps for the several screen ratios. (102x600 and 800x480 ~ 16:9; 1280*480 = 24:9)

So sorry, but no. I will not do that. Also because I already switched to DAB+ and do not use the builtin radio anymore.
[FYT Android Head Units] mdepcz:
:płacz:Do you have mod org with this resolution to return to the initial state unfortunately I have no experience in such things, thank you for the answer
[FYT Android Head Units] Hammerhand.17:
Ok, works perfectly. I hope you guys can help me with my other questions (ringtone gone and compatibility of firmware)
[FYT Android Head Units] surfer63:
Like I mentioned a couple of posts earlier: Copy the Allapp.pkg from your firmware and the lsec6521update to a clean USB-stick and flash it. It will restore all your original Joying apps, without clearing the settings.
[FYT Android Head Units] gamer765:
Oh yeah, wanted to say that the Teyes launcher will not work on any other unit since it has built in activation and will show a gray bar on the screen. I removed the activation bits but it sucks that it's built for 1024*600 screens.
[FYT Android Head Units] tchleb:
Can you please post the moded teyes launcher. How you removed the activation screen?
[FYT Android Head Units] gamer765:
I havent tested, but here you go. -REMOVED-

If it works, I can optimize it so it uses less CPU cycles. I removed the activation by simply making the activation method return void instead of it carrying out the activation stuff. In Java, the method is of type void, so the calling method/class is not expecting any response. The way I patched it is a bit dirty since the activation method still gets called and gets accessed but since it returns void it's just a wasted CPU cycle. Best way is to just remove the calls completely.
[FYT Android Head Units] thierry34:
only with this file ,simcard icon on the notification bar will desapear ? :RÉ:RÉ
[FYT Android Head Units] surfer63:
I thought so, but maybe not. It definitely (!) was on the PX5 and the Sofia. And on 4pda a user mentioned this as well to another user for the 9853i. But I used it myself and the the "no simcard" icon (simcard with question mark) is still in my notification bar.

But it this case it can also mean that the kernel/system is only using WiFi, but the hardware "simply" detects a missing SIM card.

As I do not have a sim card for it, I can't test whether in that case it only uses Wifi.

Also on these Sofia/PX5 units we had the

don
fapklogon

in the crruptoff where we thought that "don" was "debug on". We never found out about the "fapklogon".
[FYT Android Head Units] thierry34:
if we'll find the file of the simcard icon ,and delete it , will it be ok or there wiil be another bug ? :):)
[FYT Android Head Units] surfer63:
Most probably it will be inside the SystemUI.apk. No use trying to remove that.

I'm used to it now and don't care anymore.
[FYT Android Head Units] Guyzer73:
[MENTION=2550900]surfer63[/MENTION],

Thanks for all the help and setting up this thread. I've read your response to my questions on the main thread and have tried to use your FYT HW Onekey app and have limited success.

Firstly, my HU does not have any HW keys and is the full touch screen HU with 1280x480 resolution, unrooted, running August firmware. So before implementing your app, when pressing the 'mode' button on the SW I would cycle through the media apps as follows; Radio>BT Phone>BTMedia>Media Player> Video Player>Navigation. However, once I configured FYT HW Onekey both Video Player and Navigation disappeared.

I followed your instructions on your Github repository so I'm at a slight loss as to why I lose video and navigation on the scroll function...:confused:

Do you have any idea why this is? Have I c**ked up somewhere along the line?

I do note in your app that under the "Configure the options for the MODE carousel HW..." there are only 4 configurable options 6 that I mentioned above. I assume radio and nav are default to the system so you've not made them configurable, understandably. But I don't understand why I've lost video and navigation when I cycle through on the MODE button...:confused:

Idea ideas how I can trouble shoot this? I'm quite happy to try things out if they help others as I'll update the firmware once I have solutions to all my configuration challenges, or not as the case may be...

Cheers, and thanks for all the hard work you're putting in :good:

Guy

PS Hows the Custom ROM looking??
[FYT Android Head Units] surfer63:
I do not know why this happened.

In the fyt.prop in everey Allapp.pkg in every firmware, you find:

ro.fyt.def.sb.radio=6
ro.fyt.def.sb.dvd=5
ro.fyt.def.sb.btphone=5
ro.fyt.def.sb.btav=3
ro.fyt.def.sb.ipod=5
ro.fyt.def.sb.aux=4
ro.fyt.def.sb.player=5
ro.fyt.def.sb.navi=5
ro.fyt.def.sb.tv=5

It rotates through these options in the MOD/SRC (1) button, but only if the app or hardware is available (like DVD, ipod, auxilliary).

When you go into Settings->Apps->All apps and select the FytHWOnekey app, you can under the "standard open" app setting, remove the current assignments. Then it should work as before.

I stopped that. I thought that based on the fact that you can create your own signed 6521_1.zip (for the rooted boot image), you could also do that for the system.new.dat.br (which requires quite a lot of steps only for unpacking and repacking, and that's without all the modifying steps) inside that 6521_1.zip, but I guess there is something like a CRC/sha1/md5sum check as well that prevents this.

I did quite some attempts. When flashing the ROM everything works fine except the flashing of /system based on the system.new.dat.br. It varies from simply stopping and "erroring out" on the system.new.dat.br to twice a soft-brick when it started flashing the /system, by first formatting it and then stopping, resulting in an empty system partition.

And like mentioned here: I'm actually really happy with my unit and have no reason/motivation anymore to change "something".

(1): I did not try or test test this yet. Again lack of motivation (and time).

Based on the fact that you can now create your own Allapp.pkg on these units, and thereby your own fyt.prop (see post #2), you "might be able" to change this cycle and replace with your own.
[FYT Android Head Units] Guyzer73:
[MENTION=2550900]surfer63[/MENTION], thanks for the response and the tips on how to resolve this.

I think firstly I shall trouble shoot your FYTHWOnekey app by applying individual links for the SWC MODE key and see where the failure comes. If you don't mind I'll report that back to you and see if it helps any.

Otherwise, I shall try and resolve this using [MENTION=575209]bambapin[/MENTION]'s app as well as changing the SkipKillApp.Prop, I shan't try to mess with the FYT.prop for the moment as I think that's currently beyond me, and like you I have little time to do trial and error...

Thanks again :good:
[FYT Android Head Units] thierry34:
i tested to add tasker app to the skipkillapp.prop files with value -10.

when unit turn on, tasker is always open but i have this message "no profil active" . if i turn off one profil ,and turn on immediatly , this profil work.

why, when i turn on unit, no profil started ? an idea ?
[FYT Android Head Units] mclaudio:
hi there

i tried to root with developer.rtf from other post but found the same problem as other user: black screen and have to install rom again...

since that is not possuble, what kind of mods can be installed with this method?

only moded radio apps?

what are "server_mods"?

thanks
[FYT Android Head Units] surfer63:
The <some_prefix>_com.syu.ms.apk is the "main server" apk. It is THE central apk that controls everything. It is the "bridge" between many apks and the MCU binary. It grabs all hardware key-presses from the screen and from resistance based SWC controls. It captures all key-presses sent forward by the CANbus apk in case of CANbus Steering Wheel Controls. It als gets the airconditioning and open/closed doors (and sometimes more) from the CAN bus application. Upon "ignition on" the broadcast ACC_ON is sent by the MCU, and upon "ignition off" the broadcast ACC_OFF is sent by the MCU. The com.syu.ms "does a lot of things" based on these broadcasts.

And with regard to the "main server mods":

The com.syu.ms has internally a navi_app.txt containing the names of navi apps that can interrupt all media for a navigation instruction, also if it has not been assigned the navi app. It does contain a lot of Chinese/Asian apps, but further only Google Maps, Waze and iGo. So I added 26 "Western" navi apps including a number of those traffic-light/speedcam/traffic jam apps. The com.syu.ms checks if one of these apps is running and whether it generates some output.

Next to that it contains a function (method in android java) that kills all apps when going into "deep sleep" (the mentioned ACC_OFF broadcast), apart from the apps mentioned in the "skipkillapp.prop". I modded that com.syu.ms to a "no-kill" version that simply skips this function/method when going into deep sleep (note that I myself do not use that mod). The first mod was made by Gustden already for the Sofia. The second for the PX5 my [MENTION=7838245]realzoulou[/MENTION]. Then I continued it and put it forward on the (obfuscated) SC9853i version.
[FYT Android Head Units] surfer63:
I had hoped some Tasker expert would reply as I am not a Tasker user at all. I only know (for quite some time already) that if Tasker is started in the background, the profiles get not activated. Maybe that is what is happening.
[FYT Android Head Units] mclaudio:
humm may that be the cause that i cannot program SWC despite they work? or due to Key1 and Key2 wires not connected?
[FYT Android Head Units] Guyzer73:
[MENTION=2550900]surfer63[/MENTION]

I'm bench testing both your FYT HW Onekey.apk and [MENTION=575209]bambapin[/MENTION] 's FYTStarter on my HU (whilst my motor gets new head gaskets/ cylinder heads:( ) and am getting somewhere with my desired set-up, especially using FYTStarter to launch Tasker to kill all apps that Android seems to open when waking from deep sleep.

However, I have three questions that I hope you may be able to help with:

1: If I use the Skipkillapp.prop to kill the radio apk, will the hardware still launch the radio via the MCU, and just not launch the radio app in android? This would be desirable for a clean wake from deep sleep.

2: You have mentioned that the radio is 'always on' and that it is only muted when other media plays. Is there a way to get this to 'auto-switch'? What I mean is if I'm playing media via Google Music and pause the music, can I get the radio sound (not the app) to play over the speakers without selecting the radio app? I had this with my old head unit and it was a great feature...

3; Is there a way to play radio (not TuneIn or similar) whilst running Android Auto in the foreground using Head Unit Reloaded? Again my old HU default played the terrestrial FM radio if HUR/AA was not playing media.

I'll continue playing around with some trial and error, including using Tasker App , but, any pointers to make this 'less painful' would be great. Oh the HU is not rooted and I have no plans to do so.

Thanks

Guy
[FYT Android Head Units] surfer63:
1. I do not know. Given the fact that the unit remembers the state of the radio when it goes to deep sleep and thereby restarting it out of deep sleep, might mean that giving a positive value to com.syu.radio in the skipkillap.prop to kill it might help. The "killallbutsome" function cleanly closes apps. That would mean that the radio app is also cleanly closed, thereby muting the radio channel. It might work. I simply do not know.

2. By current functionality: No. Of course it can be programmed, but you would need a service for that. That is increasingly hard to program on 8.x for non-system apps or without root. The simplest thing would be to ask Joying to have a setting that will allow this (as a setting, as I personally do not want it). But looking at how things go between the resellers (Joying, FunRover, Zhan, etc) and the MCU/Android builder FYT, this might never see the light.

3. I do not know for sure. On the PX5, which Joying also asked me to test 1-2 years ago, I think I did this once to test. I think I started the radio and then switched to AA. But personally I never use AA when having full functionality available and have not tocuhed it (yet) on the sc9853i.

Maybe other users can answer 3. (and the rest btw) better than I can.
[FYT Android Head Units] thierry34:
i wanted to update allpagg file. i put this file and lsec6521update file on a usb key (FAT32) but it doesn't work. i'll try with add updatecfg file but what do i write on this file to not erase all on the unit and reinstall all ?

thanks
[FYT Android Head Units] surfer63:
There is no need for the updatecfg at all.

What is in the Allapp.pkg? And did you pay attention to the uppercase A in Allapp.pkg? (That is quite obvious for a Unix/Linux guy, but maybe not a Windows guy)
[FYT Android Head Units] thierry34:
i added app in the skipkillapp file to test if app added run . (torque,cpu monitor, tpms..)

i repack Allapp.pkg and put it on the usb key with lsec6521update file. unit watch the update, boot on the logo and i can see android robot. but reboot immediatly .

if i put all the files of firmware on the usb key , update works perfectly.
[FYT Android Head Units] surfer63:
Did you put all the apks from the Allapp.pkg and the torque,cpu monitor, tpms?

or

did you create a "clean" Allapp.pkg ONLY containing torque,cpu monitor, tpms?

You should not do the first.

You should do the 2nd. In that case you only need the lsec6521update.

If you use a full Allapp.pkg, the flash software expects a full firmware.
[FYT Android Head Units] thierry34:
i add all name apk (torque,cpu monitor, tpm) to the skipkillapp file original.

if i understand what to say, i'll must delete all in the skipkillapp file original, add the app i would add , and repack Allapp.pkg .

put the 2 files (Allapp and lsec6521update) on the usb key ,and when i'll flash , it'll add the app of the skipkillapp i created in the original skipkillappin unit ?
[FYT Android Head Units] mclaudio:
Hello to all

i use Macrodroid app, altought after comming from deepsplee it always disable the acessibility from on to off, that is needed to run.

i have searched google and apparently this is a problem of android when going to deep sleep.

how can i add this app to the nokill so that it is not kicked off from acessibility options?

Macrodroid is like tasker but easier app

thanks
[FYT Android Head Units] tchleb:
Thank you. I will try it and give you an feedback.
[FYT Android Head Units] gamer765:
Any feedback?
[FYT Android Head Units] tchleb:
I see that I come to test this week
[FYT Android Head Units] surfer63:
Sorry for my late reply. I am currently busy with a restart of one of my other projects which has nothing to do with cars or head units.

Your unit is 100% compatible. It's manufacturer id=1. It's sys.fyt.bluetooth_type=0.

That means that if you want to flash your unit with a Joying firmware or a T'eyes SSPRO firmware, you need to modify these 2 settings before flashing.

If you used my system backup script, you are already good, be it that you need to backup the oem partition as well as [MENTION=8637033]tchleb[/MENTION] mentioned.

As I'm now spending my time on other things, i will not modify my java app or existing scripts in the coming days (sorry).

W.r.t. the ringtone: You can create a new ringtone in .mp3 format. Use my FYT_SC9853i_Extender to copy it on a usb-stick and flash it.