yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] szarlama:
Thanks to all of you. Yes, it was a tragic period for me and my family. Writing here a few months ago, I hoped that there might be someone among you who had private contact with my brother. Unfortunately, the worst-case scenario has been confirmed, and my brother is no longer with us, and no one knows what happened.
[FYT Android Head Units] seb21:
The intents will be almost fully configurable,that meant : Activity,Service and Broadcast with full range of Extras.

And for clarity : Your SWC (analog) are now fully configurable and working ?
[FYT Android Head Units] seb21:
At what ZIP are you referring ? I have provided not a single ZIP. For the installation read post #15 in this thread.
[FYT Android Head Units] leo06:
From post #15. Can the ms.apk be installed from the file manager? The mod config apk can.
[FYT Android Head Units] ludditefornow:
@seb21 My SWC is CAN driven and it is now fully working. I can now assign long press and double press to multiple buttons. In the initial version, I could only assign double and long press to a single button.
[FYT Android Head Units] mariodantas:
Useful also to sort them
[FYT Android Head Units] seb21:
No. syu.ms.apk is a system apk. It can be only istalled using the lsec method.
[FYT Android Head Units] leo06:
Then I guess is not installed but I can change buttons function with the mod config app

Any idea why can’t be installed? After installation do you see any message in the screen or the no command with android robot is normal?

In the 7862isec.sh I see this

cp -rf /storage/sdcard1/190000000_com.syu.ms_modded.apk

but there is no sdcard in my unit, only usb
[FYT Android Head Units] daviddosa:
In my post you find a bunch of explanation on what each line does under a Spoiler tag.

That line is not complete and it should have an additional argument at the end. It's trying to copy the said file to nowhere as there's no copy-to path given.

The file should contain exactly this:

#!/system/bin/sh

#backup original
cp -rf /oem/app/190000000_com.syu.ms/190000000_com.syu.ms.apk /storage/sdcard1/backup/190000000_com.syu.ms.apk

#replace original with modded one
cp -rf /storage/sdcard1/190000000_com.syu.ms_modded.apk /oem/app/190000000_com.syu.ms/190000000_com.syu.ms.apk
chown -R 0.0 /oem/app/190000000_com.syu.ms/190000000_com.syu.ms.apk
chmod 0755 /oem/app/190000000_com.syu.ms
chmod 0644 /oem/app/190000000_com.syu.ms/190000000_com.syu.ms.apk

Unfortunately I don't know what the USB storage on your system is named as. In my case it's named as "sdcard1", but I also have a USB DVR camera installed which is probably mounted first as "sdcard0".

Should I update the installer zip file with this version?
[FYT Android Head Units] seb21:
Not yet. I don't have clear answer if analog SWC is working.

Sdcard0 is always built-in memory. Mine is sdcard1 and I have no more devices attached
[FYT Android Head Units] leo06:
Ok, maybe the problem is that I plug the usb to a usb hub and under file manager shows as usb6, I also have a usb dvr and shows as usb4. I try will try directly to usb port of headunit after disconnect the dvr camera.

Have you check the can protocol version?

thanks for the zip file
[FYT Android Head Units] rs200z:
Tried this 'new' version but analog SWC still doesn't work unfortunately.

Another issue I encountered is when I press the Back or Home button on my head unit, sometimes I get a double beep (key tone) instead of the usual single beep.

Funny thing is that it is not consistent. I tried pressing multiple times (with pause in between so as not to trigger the double press function) and i can be getting single beep for few press and then out of the blue a double beep sounded. Not sure if anyone else is facing this issue.
[FYT Android Head Units] barnesk9:
@seb21 Thank you SO MUCH!!! I just bought a new car that's CANBUS controlled and only 2 of my 7 buttons worked and even those were backwards. This solved my problem!

2 questions for you though.

1. Do you have a donate link? I'd love to support your efforts and

2. I've noticed that when using the car link app some of the controls don't work (play/pause, voice input, others too but those are one I know for certain) Do you have any ideas as to why?

​
[FYT Android Head Units] seb21:
Hi.

1.If you want to, here you have. PayPal .But it's not necessary.Thanks anyway.

2. I can not help you with this problem. Ask at the forum, maybe someone can help you.
[FYT Android Head Units] mariodantas:
{Mod edit: Quoted post has been deleted. Oswald Boelcke}

Project seems to be giant, I don't think that the project is ready, but I think that @seb21 will update the 1st post of the thread with the upcoming releases
[FYT Android Head Units] barnesk9:
I updated to the new version of the Joying Firmware for the 1920 x 1200 unit hoping to fix my problem with carlink and now the modded apk won't install I tried the apk from the first post and the zip from post 15 and I can't downgrade the firmware

@seb21 would it be possible to update the script for the new version or could you tell me what is required to do it?
[FYT Android Head Units] mariodantas:
Hello, this is maybe calm due to Christmas month ?
[FYT Android Head Units] zinemahk:
Excuse my english.

Instalation was ok, but I have a Navifly TS model with portrait screen. It makes the Mod Config app useless, because I only can see/use part of the menus.

Any solution? Thanks.
[FYT Android Head Units] seb21:
Sorry for that. I'm new to this typical android stuff like layouts and dealing with different screen resolutions. I will however learn something new and make the UI work on different screen orientations.
[FYT Android Head Units] Specy01:
Hi @seb21, i haven't installed your app yet, but i hope to be able to do so soon. Reading the varius post in this treath, i read about long pressure and double pressure of the steering wheel controls.

I have a Peugeot 308, and my steering wheel controls don't accept long pressure and/or double pressure; if i installed your app, my steering wheel controls will accept it? Also with the original radio, the simultaneous pressing of Vol+ and Vol- paused the music, with your app is it possible to achieve this?

Thanks you for the work you do.
[FYT Android Head Units] seb21:
Hi.

If your car controls handles the buttons normal way (button state is sent only on button physically state change) then yes it should work.

It looks like pressing simultaneous Vol+ and Vol- sends another code : MUTE .

Just try it . If my mod will not work or you don't want to use it ,you can always go back to standard syu.ms.apk .
[FYT Android Head Units] daviddosa:
I'm using it on a Peugeot 308 too. As @seb21 said in his last post, the Vol + and Vol - buttons will send a Mute command. With the standard Raise decoder, the command works, with the extra SimpleSoft XP decoder, I couldn't get it to work properly and neither with the new RaiseTech decoder.

Double and Long press buttons will work as I'm using it on mine, but you can't set it to pause or play with any of the buttons for some reason. I tried configuring the Band / Mode button to be Play/Pause either on normal press, double press or long press but doesn't work. Tried Play only, tried Pause only, nothing. The only way you can silence the radio is to set it to Mute but that doesn't stop the currently playing music in Apple CarPlay.
[FYT Android Head Units] seb21:
Play / Pause works, I'm using it on Spotify and tried it on YouTube . The problem you describe is with CarPlay. If you know what signal or sets of signals works with CarPlay then i can add a special action to my mod. And maybe intents will be solution to you problem.

Probably i will put new version (with intents) about a week.
[FYT Android Head Units] daviddosa:
I'll try to figure something out. There might be something in the Carlink app which needs to be checked.
[FYT Android Head Units] Specy01:
It's really strange. When I had the canbus Raise the mute did not fonziova, while now that I have the Simple Soft XP works fine. But I suppose it's due to the setting I did in the "car info" app of the canbus.
[FYT Android Head Units] daviddosa:
What are your selections in the CANBUS settings menu, which model of car did you choose?
[FYT Android Head Units] Specy01:
Now I don't remember, but tomorrow morning I'll check and I'll let you know
[FYT Android Head Units] daviddosa:
@seb21 You were right. Play/Pause works when I'm using a different player than CarPlay. I looked in the Carlink app but I couldn't figure out which part handles the inputs.
[FYT Android Head Units] s14kouki:
Just wanted to say thank you all involved for this great tool - I can finally configure my SWC!

My only limitation is my GOLF 7 has very limited programmable buttons thus I'd like to add more.

I have tried to install a third party controller by wiring the Key 1 and Key 2 to add more buttons but I can't seem to get it working.

I tried programming through the Headunit control app - nothing registers. I also tried changing Seb21 config app to look for Key1/2, again nothing registers.

Is this because my current SW keys are through CANBUS? is it possible to run both?

Or faulty aftermarket SWC Box?
[FYT Android Head Units] barnesk9:
It's definitely something with the Carlink app. I have the same problem with android auto, when I use the default media player play and pause work fine but in Carlink they don't do anything
[FYT Android Head Units] daviddosa:
Might not be the answer you're looking for but you can also try adding different actions to double press and long press for the existing buttons. You can add 2 extra actions for every button.
[FYT Android Head Units] s14kouki:
Many thanks for your input, that's what I'm currently doing - it can get confusing so ideally would prefer separate button box attached to the steering wheel.
[FYT Android Head Units] daviddosa:
@seb21

I might have found the part within the CarLink app which is responsible for the button press handling.

I used the Jadx-Gui program on Windows to open and decompile the app I extraced from the AllAppUpdate.bin file.

After decompiling the file can be found in f/a.class.

Spoiler content hidden.

I also noticed something what might be interesting, another file

Spoiler content hidden.

There's a keycode for next, previous, mute, but there's no separate keycode for pause. Could this be the cause?
[FYT Android Head Units] Specy01:
Sorry for the delay. My car is a 308 eHDI of 2012, but if I set the 308 some steering wheel controls do not work. Now I have set the 4008 of 2017 and all the steering wheel controls work and I also have the mute with the simultaneous pressure of the Vol + and Vol-.
[FYT Android Head Units] seb21:
But there are keycodes for play,pause and play/pause.

Look at this . It is taken from older carlink apk :

Spoiler content hidden.

I don't see this definitions in new versions but i doubt that they are changed.

In f/a.class you have

Spoiler content hidden.
[FYT Android Head Units] Specy01:
@daviddosa

I forgot to point out. The only problem I have with this setting is that from time to time, randomly, I turn on the maintenance light (the key) and the opening of the doors is indicated incorrectly. But today I should get another canbus and we'll see if it will be the right one
[FYT Android Head Units] s14kouki:
I just updated my canbus files via the Teyes update app, now the patch no longer works.

I've also tried to reflash the mod with no luck. The config app doesn't register any of my SW buttons like it did before.

During the update process I had to download 4 files and install in sequence, I'm pretty sure one of them was titled MS.apk. Could this another case of Teyes locking out mods after update?

Help! This mod was so good, I wish I never updated the canbus :cry:
[FYT Android Head Units] seb21:
Send me the updated ms.apk.
[FYT Android Head Units] seb21:
If anyone wants to update their translation i updated the strings.xml file in first post.

New versions of Config App and syu.ms i will post tomorrow .
[FYT Android Head Units] s14kouki:
Thanks so much for your help.

Attached is the file downloaded when I click the update ms.apk button.
[FYT Android Head Units] seb21:
I have updated first post and the files.

@zinemahk Config app now support vertical screens

@rs200z new version is here. And if you get the ""downgrade" error then use lsecXXXXupdate binary from new firmware. Update script stays the same.
[FYT Android Head Units] seb21:
I compared your file and the new form joying. Your ms.apk is standard one and should be replaceable with modded version.

Try the new one from 04.11.22
[FYT Android Head Units] surfer63:
Thanks @seb21 for your improvements to our units.

I see you have one apk for Joying and one for Mekede. When examining the last few firmwares of Mekede and Joying, I noticed that in the fyt.prop (when you unpack the AllAppUpdate.bin), you have the well known ro.build.fytmanufacturer, but now also the ro.fyt.uiid.

It might be something new that FYT put in there to make it harder for modders to adapt their firmware.

Joying has a value of ro.fyt.uiid=4, Mekede is ro.fyt.uiid=2.

I did not search in a decompiled com.syu.ms.apk for this value to see if this property is checked and somewhere hard-coded to 2 or 4 for both brands/resellers.

If you flash a system with a firmware from one of those, you need to change the ro.build.fytmanufacturer to prevent issues with the MCU firmware.

And if you leave the rest as is, the apks will also function fine.

But if you take one apk from one firmware and flash it onto another, you might now need to take this ro.fyt.uiid into account, or really stick to the version for your firmware (like you now do with the two apks)

It might be something to examine in both com.syu.apks, but currently I don't want to and I suppose you know those apks now quite well. ;)

Edit: the UIID property is a unique identifier for your "phone". Maybe FYT is copying this for their own needs.
[FYT Android Head Units] s14kouki:
Hi Seb

I tried the 04.11.22 version with no luck still.

I should also mention in the canbus update I had to update 3 other files which are:

- protocolupdate.apk

- syu.canbus.apk

- syu.us.apk

along with the syu.ms.apk which I attached in my previous post.

Could updating the other files impact the functionality of the modded syu.ms.apk file?

I'm considering doing a fresh install of my current firmware in the hope it will restore my previous canbus files, do you think this will work?
[FYT Android Head Units] mariodantas:
ro.fyt.uiid in here
[FYT Android Head Units] seb21:
Yes, you are right . The ms.apk is checking for ro.fyt.uiid property and compares it to 2,4 and 1. And this values are the same in joying,mekede and even in teyes. But from i could see ro.fyt.uiid property is only used to some minor config : sound (subwoofer),image and canbus. It looks like there are 3 or 4 basic hardware platforms that are provided by FYT.

I have local reseller unit fytmanufacturer =124 my uiid =1 and i have used ms.apk from joying and mekede without any problems. The only way the blocking can be done is within the system itself by checking version,checksum or signature.

As i see if you replace ms.apk with another for example my modded version and it is not working there can be only one explanation : system for some reason (different signature ???)has not updated Dalvik Cache- therefore it still using old app.

Do you know a way (without root)to force the system to clear/rebuild Dalvik ?
[FYT Android Head Units] surfer63:
Yes, I just explained that in another post if you flash a single app.

See post #1250 from the "General FYT based Spreadtrum uis7862 etcetera" thread.

For the com.syu.ms it should be

# Remove the current app data/program cache/cache
rm -rf /data/dalvik-cache/profiles/com.syu.ms
rm -rf /data/data/com.syu.ms
rm -rf /data/dalvik-cache/arm64/*com.syu.ms*

Edit:

The relevant dalvik files are actually:

/data/dalvik-cache/arm64/oem@app@190000000_com.syu.ms@190000000_com.syu.ms.apk@classes.dex
/data/dalvik-cache/arm64/oem@app@190000000_com.syu.ms@190000000_com.syu.ms.apk@classes.vdex

A lot of users know my HWGetinfo.apk by now, but personally I use a flashable lsec script to do this as it gives much more info. I will add some informational text to it and share it in "my" thread.
[FYT Android Head Units] s14kouki:
I reinstalled my firmware with full wipe, now works fine again.

Thank the heavens! (And @seb21 )
[FYT Android Head Units] surfer63:
I just added that getinfo script to the bottom of my first post of my "General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware" thread.
[FYT Android Head Units] zinemahk:
Hi, the ModConf app works perfect in portrait mode.

I think everything is well installed and configurated in my HU but still can´t manage Key1-key2 buttons. SWC manager is working as usual, but I can't use the double/long press.

My Unit is a Navifly/Mekede TS3 (FYT 7862) with last firmware.

For investigating purposes I configured google assistant as one of the buttons, and if I keep pressing it the app executes BEFORE release the button. Maybe that will help... who knows.

Excuse my poor english, and Thank you very much.
[FYT Android Head Units] nagibo77:
Thank you very much for your work. It is very useful 👍

At last I can configuration my SWC bottoms with canbus.

Thanks again.
[FYT Android Head Units] seb21:
Hi.

In Config app when you press a button, background for "Car button" is turning to green. Can you tell me how it behave when you press a button and hold it : green as long you press a button or shortly turn green and then back to normal ?
[FYT Android Head Units] zinemahk:
Not in my car so I can't confirm it, but I think it keeps green as long I press the button.

In other hand, if I set one of the buttons as "Next", short press makes radio go to the next memorized channel, and with a long press the radio starts seeking up, while I set it like "Prev" in your modconfig app. I haven't tried with other apps or buttons yet because my HU has just a couple of weeks.

I will do more tests tomorrow. Hope it helps.
[FYT Android Head Units] daviddosa:
I have updated the installer to include the new ModConfigApp and newer versions of modded syu.ms.apk.

Find it in post #15.
[FYT Android Head Units] Jpw0917:
Does anyone know what the Honda Lanewatch Button is called in the Car Buttons menu/ if it’s assignable
[FYT Android Head Units] daviddosa:
If you open up the app and have the modified MS app installed, then when you press it, it'll show you it's purpose within the list. If it's not coming when you press the button, it won't be a configurable button as of now.
[FYT Android Head Units] Jpw0917:
When I press it it activates a function from the default system CAN BUS
[FYT Android Head Units] daviddosa:
That means you either didn't install the modded syu.ms.apk (not the ModConfigApp) or you haven't enabled the default method blocking in the ModConfigApp. This can be done with opening the ModConfigApp, go to Misc and then turn on "Block some write Write_To_MCU". You don't need to configure anything inside -at least it's working like that for me- just turn it on, then close the app. Open it and try again.

If this isn't working still, make sure you replaced the modded syu.ms.apk properly.
[FYT Android Head Units] KoTiX2:
Hi seb21, i just found out a small issue with your modded service and my app NavRadio+.

It took me almost 1 day to understand that wasn't my code causing this issue but because it doesn't happen in the basic version i looke all over to find it out.

The problem is that Navradio+ become silent for a few seconds when resuming from background.

To reproduce the problem, simply start NavRadio+, press home button to go to launcher and then open again NavRadio+. At this point the service think that NR is a new package starting and it initialize the sound again even if it was already playing.

As I said on the Basic version this doesn't happen and infact i can see that the "radio_free" package is not present in the code your modded service.

Replacing modded service with original one, everything work as expected :)

please let me know if you need something from my side to be modified.

Cheers;)
[FYT Android Head Units] seb21:
Hi

I'm aware of the problem with NavRadio, you are not the only one. And for the record i tested this in my unit and i don't have this issue.

I need some more info from you.

1. Which button do you use to switch to the radio : unit or swc (if swc - analog or canbus) ?

2. How do you have set the button function : Radio or User Apk ?

And about the NavRadio+ package. I do not have hardcoded any packages in my mod. You probably referring to property files inside ms.apk. You can edit them by yourself , you only need a archive program that can open zip files and text editor.
[FYT Android Head Units] seb21:
I Don't see how this should work. Block Write_To_Mcu with no arguments should do nothing. If the blocking without argument was working then you would not able to use your head unit - the MCU controls the whole device : buttons,sound etc. And ms.apk would not able to set anything.

Moreover this is one way blockade ms -> mcu.

If you want to prevent the ms.apk to send anything to canbus you pass to that function only one argument : 227
[FYT Android Head Units] daviddosa:
Okay, that then explains some weirdness what was happening with mine.

What should we put into the argument parts then?
[FYT Android Head Units] seb21:
I really doubt that is a button signal (yeah, i know physically it is a button) . I suspect that pressing this button send a signal through the canbus like for example opened doors. And that why it is not manageable.
[FYT Android Head Units] seb21:
That you must take for yourself from the ms.apk code.

227 - is the canbus - it is universal for all cars and canboxes.

227,167 - in my car it is compass on multi function display.

As for the canbus the the values are depending for car,model and canbox model.

If you want to block something i suggest you to look up in old (not obfuscated ) ms.apk code to give you some insights about the actual values.

But honestly speaking i don't see any sense for just blocking , unless you want send your own values.

Example : Setting clock in Golf 7 with Simple Soft canbox

ToolkitDev.writeMcu(227, 166, 7, (byte) (t.year - 2000), (byte) (t.month + 1), (byte) t.monthDay, (byte) (((format << 7) | t.hour) & 255), (byte) t.minute, (byte) t.second, 1);

227- canbus

166 - clock subsystem

7- length of the message (7 bytes)
[FYT Android Head Units] KoTiX2:
Thx for replying me.

I use the home button on the panel to put NavRadio on background and go to launcher.

Then i use the NavRadio icon to bring it foreground. I don't use any radio button to open NavRadio.

I didn't mean that you have included a NavRadio package inside the service apk, i mean that is found "com.navimods.radio" package name in the code of your modified apk but not the "com.navimods.radio_free" package name in it.

P.s. i know perfectly how to decompile or jadx an apk to look to the inside code. ;)
[FYT Android Head Units] seb21:
Let me clarify a thing. In my mod i don't hardcoded any packages names. That what you found is "com.navimods.radio" in player_app.txt property file. It's a list of multimedia players. You don't need to decompile apk to change that file. Open the ms.apk as ZIP. Go to assets/property/ unpak the player_app.txt. Edit it and copy it back. The whole process takes 2 min.
[FYT Android Head Units] KoTiX2:
I was referring to this intent but propably has nothing to do with the issue.
[FYT Android Head Units] seb21:
I forgot this. It is a leftover . I used it to get Navradio frequency for my multifunction display. It is just broadcast receiver.
[FYT Android Head Units] Gunde:
Very intriguing tool. Anybody try it on Teyes CC3, or is there any reason I shouldn't? :)
[FYT Android Head Units] mariodantas:
CC3 have another method of flashing (they put the /oem/* apks into a partition named "elable") I don't know if you can use the normal flash method for com.suy.ms file, maybe someone here know how to do it ?
[FYT Android Head Units] mariodantas:
Everything inside this mountpoint has been extracted from elable