yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] cryptyk:
I can definitely modify the firmware and re-flash it, but that's much harder.

I was hoping for an easier way like using 7862lsec.sh to copy a single modified file. Do you think that's impossible?
[FYT Android Head Units] mariodantas:
Look at elable inside (below)
[FYT Android Head Units] mariodantas:
I think that if you create your *lsec.sh file with something like cp -r <yourstuff> /oem/app [or] /oem/priv-app it will work fine
[FYT Android Head Units] cryptyk:
I've tried that. It doesn't work.

The /oem folder that's mounted at flash time is mmcblk0p42

/dev/block/mmcblk0p42 on /oem type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc)

But then when the system is booted, that block device is mounted to /fem (which is mostly ignored)

/dev/block/mmcblk0p42 on /fem type ext4 (ro,seclabel,nosuid,nodev,noatime,noauto_da_alloc)

At runtime, the /oem directory is just linked to /elable.

lrw-r--r-- 1 root root 13 2008-12-31 16:00 oem -> /dev/oem_link
lrwxrwxrwx 1 root root 7 1969-12-31 16:00 oem_link -> /elable

The problem is I don't see any way to mount /elable at flash time to modify it.

When the system is running, /elable is mounted to /deb/block/dm-3, but that isn't available at flashing time.

/elable is mounted as ro as a first_stage_mount in the fstab:

system /system ext4 ro,barrier=1 wait,logical,first_stage_mount
vendor /vendor ext4 ro,barrier=1 wait,logical,first_stage_mount
product /product ext4 ro,barrier=1 wait,logical,first_stage_mount
elable /elable ext4 ro,barrier=1 wait,logical,first_stage_mount
[FYT Android Head Units] mariodantas:
I see, I'm not really guru in the TEYES structure, I think that here around this thread you must find someone who knows TEYES strusture better than me.
[FYT Android Head Units] cryptyk:
Sounds good. Also, thanks for everything you've done for the community. I've just started playing with these headunits and all of the work you (and surfer and seb and others) have done are a huge benefit to everyone.
[FYT Android Head Units] mariodantas:
Well fellow, welcome to the FYT world, we all count on you to join our group, with fresh ideas, improvements, we all together try to deliver better experiences and customization possibilities to these firmwares !

Now we have to stay in the main thread subject "Modded com.syu.ms"
[FYT Android Head Units] seb21:
I will make changes to the UI to fit your resolution.
[FYT Android Head Units] seb21:
@Disturbed21

Could you post a photo of this issue ? I checked it in emulator with that resolution and the app is full screen, just the down is outside the screen. What is your dpi ?
[FYT Android Head Units] NoUsrNameSry:
Hey, any updates on this mod for T'Eyes CC3. I'm having the same issue everyone else seems to be having. My factory buttons work with their OEM functions, but the SWC app will not work for remapping. I feel so limited; only Vol, Track, and Mode work from the defaults and I want to use your solution. However, I see that it is only for Joying and Mekede. Anyone have any luck getting this to work on their CC3?
[FYT Android Head Units] mariodantas:
@seb21 is surely working in new stuff, be patient !
[FYT Android Head Units] seb21:
How are you flashed this file. If you used the lsec method then it will not work. Look few post above there was discussion about TEYES. The Joying version as the newest should work on all units. Teyes ms.apk has nothing special in it.
[FYT Android Head Units] cryptyk:
You'll need to use FYT Firmware Tools (from this forum) to unpack the firmware, replace the syu.ms.apk file, then repack and flash the modified firmware. This won't factory reset your device (assuming you use the October Teyes CC3 firmware as your baseline)
[FYT Android Head Units] NoUsrNameSry:
What tools are you referring to? I've looked through this whole thread and see a few attachments, but am unclear which specifically I have to do first. If I'm not mistaken, I need the firmware tools before I can install and do the Post #15 method? Sorry if these are all stupid questions. I am very much new to code and modding android so I need things explained to me like a child. I don't want to do anything that might brick my new $500 toy.
[FYT Android Head Units] cryptyk:
Replacing files in the firmware isn't a good idea unless your really know what you're doing. You're unlikely to brick it, but it's possible.

There FYT Firmware Tools are in this forum... Not in this thread.

Edit:. Here. https://xdaforums.com/t/tool-fyt-firmware-workbench-2-0.4444267/
[FYT Android Head Units] NoUsrNameSry:
Thank you for linking me to the tools. So, is this workbench an alternative to the post #15 method? Do I have to unZip this to a USB and plug it into the CC3? I'm unclear if I need to download the zip file in Isec post or the Joying apk from the 1st post? What happens if I just download and install the Joying apk raw just like the Mod Config app from the main post?

Please describe the steps I need to do in order specifically for the CC3. If the workbench needs values configured, I'll be completely lost, so please describe the process carefully.
[FYT Android Head Units] mariodantas:
Yes, use it only iof you are sure what you will do inside the firmware
[FYT Android Head Units] mariodantas:
Note that CC3 firmware stores OEM apps and priv-apps inside elable partition, also config files.

Never used FFW in T'eyes 6315_1.zip for CC3
[FYT Android Head Units] mariodantas:
This thread is about modded com.syu.ms powered by @seb21 and not about FFW
[FYT Android Head Units] mariodantas:
Hi @seb21

Still found it in app/aj.smali

public static void h(String str) {
ActivityManager n = ae.n();
try {
if (str.startsWith(":")) {
str = str.substring(0, str.indexOf(":"));
}
if (!p.a(str)) {
k(str);
n.forceStopPackage(str);
a.o.c.a(str);
}
} catch (Exception e2) {
e2.printStackTrace();
}
}
[FYT Android Head Units] marchnz:
. Deleted.
[FYT Android Head Units] marchnz:
This isn't how xda works.

put some effort in, post in the correct thread, and create / feedback instructions to your level.
[FYT Android Head Units] mariodantas:
I saw the deleted post, the user has nothing to do here I think 💬
[FYT Android Head Units] seb21:
Hi. Yes the method you posted is used to killing apps. It is used when unit goes to sleep (you can disable that in my mod), and the code calls it from different places . I'm not sure if it good idea to disable it at all, but if you wish I can add this as switchable option. If you think it is killing something important then you can add that package to protected_app.txt.

The line in this code :

if(!p.a(str))

Checks if the package to kill is in mentioned property file, and kill's it only when the package is not "protected".

Also I have seen you post in your firmware thread and i don't see a connection between ms.apk and accessibility .
[FYT Android Head Units] mariodantas:
Ok @seb21 many thanks for your explanation !
[FYT Android Head Units] seb21:
Hi everyone.

New versions available . Updated first post.
[FYT Android Head Units] marchnz:
Recover from junk posts
[FYT Android Head Units] Moldeb:
Great piece of work! Re-assigned my VW SWC and use this together with @mariodantas MD Edition kernel (no Mainservice) - works really well!
[FYT Android Head Units] barnesk9:
hey @seb21 awesome work with the update. I had a couple of questions for you.

1. Is there any way to map a button to the Track forward/hang up and Track back/answer phone button like the joying software does it if I only have CANBUS controls? Or

2. Do you have any idea how to get the intents from Android auto? I'm on a Joying unit and Carlink 2.0 but buttons like play/pause don't work
[FYT Android Head Units] marchnz:
Up.
[FYT Android Head Units] mariodantas:
Thanks @seb21 , now FMC detects your MS and will allow (in upcoming release) to handle properties manually or automatically (i.e.: If user installs a player app, FMC will search for that payer apk package name into payer_app.txt file, if not found then will add to list as well as remove from list if user uninstalls the apk, same for navigation apps).
[FYT Android Head Units] PaY87:
Hi! I tried the latest FW and also clean cache storage for FMC. It now asks for SU when pressing lock device. Then FMC seems to close and i can see for few seconds a red lock in the taskbar which got a disabled line in thr icon. Besides that the device don't seems locked.
[FYT Android Head Units] mariodantas:
Wrong thread, please go to This thread
[FYT Android Head Units] PaY87:
You are right sorry! And ignore my post the issue was that Opera had an account too. I had to remove Opera too before activate lock.
[FYT Android Head Units] seb21:
Hi. First sorry for not responding early to your post.

1. No. But i will try to add this in few days.

2. I searched up Carlink app for intents receivers - there are plenty of them. The curious thing is that Carlink App has implemented key PLAY/PAUSE (key code: 85) , but it is not working.

I have updated the ms.apk in the first post with key event inject function . This allow to send any key code as system key event. If you have time you can test various codes. Maybe Carlink app will respond . Detailed info about this is in user manual.txt

I also uploaded a test version. This version allow user to assign touch actions to steering wheel buttons. If in Carlink app PLAY/PAUSE button is all time visible this can work. Detailed info is in text file inside the test version.zip file
[FYT Android Head Units] barnesk9:
Thanks! I've been trying to find solutions for this for a while. Just today I created an app using Tasker app factory to try and make the play pause work and it still doesn't. I'll try your test version and update you on what I find.
[FYT Android Head Units] barnesk9:
@seb21 I just used the test app and it works great! The only issue I've seen is that when you assign a special action to a button you can't do a long press or double press if the special action is the single press action
[FYT Android Head Units] onkel-adi:
Hello to all,

but is this apk vendor specific or can it be used on all chinese HU? I've got an Junsun and I'm interested in some features of your apk but try to avoid bricking my device.

thx
[FYT Android Head Units] surfer63:
It is manufacturer specific. It needs to be a FYT uis7862 unit.

Your Junsun is not that and is not supported.
[FYT Android Head Units] onkel-adi:
Thanks mate for the fast reply. All clear. I try to find out if there is a similar apk in my device. How difficult was it to decompile the apk? Did you work on smali or was it quite simple to gain the java source code files. Did our chinese friends obfuscate the source code with some tools?
[FYT Android Head Units] seb21:
I tested this on my unit and it work normal, no matter how the combination is all three functions on a button are working as expected.
[FYT Android Head Units] seb21:
Decompiling code to smali of most apps is easy. You can even decompile to java but only for lookup purpose,there is small chance that decompiled java code will be compilable. So it looks like this : browse the decompiled java code for finding spot of your interest, then you must find the same spot in decompiled smali.

All changes must be done in smali. There is one limitation : as the ms.apk is system apk (at least on FYT based units) you can not change the signature therefore no changes to Android Manifest.

And for the obfuscation . Few years ago the code was not obfuscated, then someone from this forum has invited people from Joying customer help to look up on this forum to see what problems do users have. And the solution from our "chinese friends" was obfuscating the code. I don't know how it looks on Junsun.

If you want to try to modify your unit and have some questions just ask.
[FYT Android Head Units] marchnz:
@seb21 do you have any hopes of Analogue steering wheel modification being implemented, or perhaps that requires MCU code change as MCU handles analogue buttons?
[FYT Android Head Units] onkel-adi:
Thanks man, yes I don't want to re-invent the wheel so I will ask if I'm in doubt of something. It would be great to have a virtual machine to test the stuff I do but I don't think that would be quite easy because of the mcu and bootloader (I think). So it will stay on good old old-fashioned open hearth surgery...
[FYT Android Head Units] seb21:
The analogue buttons are handled in MCU and ms.apk. MCU reads the analogue value of pressed button and send it to ms.apk as learned key code. The problem is that in Ms APK are only three places where key codes are handled (can, unit and analogue ?) , But it is not working.

I must add to my unit analogue button ( at least one) to look closer to this problem.
[FYT Android Head Units] seb21:
Yeah, testing can be very frustrating - make changes -> go to car and check if it is working -> go back to home and the circle starts from the begining. For luck it is hard to brick these units, just don't touch android system files .
[FYT Android Head Units] snnail:
hi I installed it on a joying unit useing method from #15 but cannot find the setting? or the app itself, Am i missing somthing? TIA
[FYT Android Head Units] seb21:
Hi. The syu.ms.apk is not visible in launcher, it's a system app that is working all time in background.

The setting app you must download from this thread and install it like every other android APK.
[FYT Android Head Units] snnail:
thanks for the quick reply, and I just did that, thanks a lot for the awesome work!
[FYT Android Head Units] suwind:
Hello, excuse me, my Toyota will update the dashboard time when it starts up, which will be updated every minute. The ms.apk before 2022/04 will not update the dashboard time, is there any way to block the dashboard time update? My English is not good, please forgive me.
[FYT Android Head Units] seb21:
Hi.If you are using my mod then yes,there is a possibility to do that. It requires the knowledge of values that are sent to CAN . These values can be taken from ms.apk. Sen me your car model, year and the type of can-box or a photo of Can setting page from FYT Settings App. Maybe i will be able to fint those values.
[FYT Android Head Units] dishe2:
Will this work on an Atoto unit that uses resistive swc wires?

I want to set a button to launch an app and the built in config screen doesn't have that option.
[FYT Android Head Units] seb21:
As i was informed by some users

the analog SWC (resistive) is not working right now.
[FYT Android Head Units] dark_knight_007:
Hi,

The long and double press are not working for me. My SWC is working with CAN box.

Could you update the modified ms.apk in newer version. This is my ms.apk in attachment.
[FYT Android Head Units] seb21:
Hi.

How the config app behave when you press button on your swc and hold it ? The background of "Car button" turns green and stay green as long as you keep the button pressed or turns green only for a moment ? If it is the second option then there is no way to fix it - your car is reporting button presses as press and release.

And for the newer ms.apk i will look into it.
[FYT Android Head Units] fahrenhayt46:
@seb21

Thanks for this great app,

I took the risk and installed it on a fyt-based device whose manufacturer I do not know ( sc9853, android 8.1).

Only the "mode" button on the steering wheel can be assigned, even that is enough for me.

However, the bottom side of the application is not visible on the 1024x600 resolution screen (160dpi). I added the picture. How can I fix this?

I have one more question for you.

I can't assign the "google assistant GO" app to a long press of the Mode key. Because this application does not appear in the application list.

How can I assign the "google assistant GO" application to a long press of the Mode button? Is it possible to do it with "intent"?

(The "google assistant" app is not making phone calls, so I have to use the "google assistant Go" app.)

Can you help me with this?
[FYT Android Head Units] seb21:
Hi.

As the Config app is based on android "density pixels" the only solution is to lower your dpi, around 100 dpi should be enough. I''m currently rewriting the app but it is long road before me - so no other solution from my side right now.

This app is visible as "Assistant" (not "Assistant go")in system, and should be visible on apk list in Config app. I have checked that in emulator.

Let me know if you still can't see it.

And for the risk installing any ms.apk on any FYT device : there is no risk, if it will not work properly or it will crash you can always install back your "good version" .
[FYT Android Head Units] fahrenhayt46:
Thank you for the answer.

The app I'm talking about is not the regular "google assistant" app.

"google assistant GO" application.

"google assistant GO" app does not appear in the list.

Can I run it with "intent" even though it doesn't appear in the list? How can I do.

edit:

app link: google-assistant-go
[FYT Android Head Units] seb21:
My bad. I have searched for the assistant go and play store was installing regular assistant. And it looks like i have no devices compatible with this app. There is for sure an intent to launch this app, but i don't know the activity to launch.

Tommorow i will think something off.
[FYT Android Head Units] DexterMorganNL:
Who has experience with this? I see no point to enable NOKILL, when it would cause the unit to shutdown instead. I though first I would have to select apps and add them to the NOKILL. But instead all apps that are opened, won't be killed? I replaced the ms.apk with the Modded version, but I'm planning to flash it in the coming days.
[FYT Android Head Units] DexterMorganNL:
Okay NO-KILL seems to work fine: I especially like it for this reason, so that you can make use of the splitscreen and after the unit wakes from sleep. It easily reverts back to this state.

I'm using it in combination with @mariodantas project. Both projects combined, offer a major improvement to the headunit: why should my apps be killed? This unit has plenty of power, to handle a few apps in sleep mode.
[FYT Android Head Units] seb21:
Just added version of my mod based on 18-02-2023 syu.ms.apk.
[FYT Android Head Units] hop3l3ss1990:
Hi @seb21,

First, your mod is amazing :-)

I'm using an Ekiy T7 in my Volvo S60 and had the issue that my canbox has mapped the previous and next song actions to the actual buttons, to the up and down wheel, the menu wheel... Well one of those wheels is a bit shaky and so a song was skipped randomly... (this is horrible when you try to follow an audio book).

Because of this I had the canbus box completely disabled (selected none)... But thanks to your mod I mapped the "Previous" and "Next" to "N1" (what ever this is) and now the songs are not skipping anymore. :-)

Now I would have two feature requests:

It would be very nice to have a simple "disable" option instead of mapping it to "N1"

Please find a way to also disable the volume actions

In the thread you say it is not possible to remap the volume actions (except of adding additional actions to the default). Is this a "sanity" restriction or so deeply that it just can not be changed?

Reason: My car has a pretty complicated audio system and the HU is connected to some receiver via a simple aux cable (Volvo's optical bus can not be used -_-). Now I have the problem that the volume keys change the volume of the audio system and of the HU. But I don't want that the volume of the HU changes. I configured in the HU settings that it starts with max audio out. It would be perfect if there is an option to ignore the Volume keys, disable the volume actions and keep the volume control at the orginal audio system.

Currently I change the volume and have then to "slide" the volume on the screen to max to only control the audio system.
[FYT Android Head Units] seb21:
Hi.

Here you have a modified version of ms.apk that allow to "block" volume keys. For now to disable volume key assign its main action to "N1" as you did with your broken button.

The reason that volume buttons can not change it functions is because they have it's own logic : holding volume key pressed changes the volume continuously as long it is pressed.

And for the disabling a button - i will add that possibility to the next version.
[FYT Android Head Units] hop3l3ss1990:
Thanks a lot! Is this based on the 18.02.2023 one (this is what I currently use)?

I will give it a try and report back tomorrow morning :-)
[FYT Android Head Units] seb21:
yes
[FYT Android Head Units] hop3l3ss1990:
I tried the changes and they work as described :cool:

Maybe this would be also a good option in the preferences? A way to just disable the volume actions is a huge improvement for everyone using an simple aux cable. :-)

Another question: Instead of mapping the "mapped" actions of the can bus decoder, do you also get the raw events? Like if two buttons are mapped to one action e.g. "next" can you distinguish which one of them was clicked and we can map using the raw events "id" in case of duplication?

Thanks
[FYT Android Head Units] suwind:
This is my CAN&2021 toyota rav4 , asking for help to stop ms.apk from updating the dashboard of the car.

thank you

thank you
[Google Pixel 6] mohamed_emad10:
After I updated pixel 6 to android 13,​

phone doesn't work became bricked and I can't fix it because when I plug it into my computer and see the device manager in windows,​

but it is not detected by `adb devices` or `fastboot devices`.​

I see it detected in seconds and disappear by watching device manager as a " USB serial port device (COM 3)" in windows 11​

​

in windows 7 & ubuntu detected as pixel CDC- ACM (Pixel ROM Recovery )device because devices manager in win7 can't find any driver compatible so it detected as itself in "Other devices"​

​

in VM box :

​

while I hold down the power button so I can't fix it,​

how to restore my phone and flash it in this mode I think this mode is EDL​

I tried to boot in bootloader by pressing press power + volume down and power + volume up and all together but nothing work , the phone is dead​

I have tried to fix by this post but unfortunately it doesn't work https://xdaforums.com/t/guide-unbrick-pixel-6-oriele-or-pixel-6-pro-raven.4441245/​

I have escalated this issue in google tracker since 2 months but i got NO ANSWER and NO HELP :confused: https://issuetracker.google.com/issues/243636259​

is anyone have any idea to fix my ? i will appreciate any try 😊 PLZ help me
[Google Pixel 6] tom1807:
Very likely you can't.

From your description, when you flashed it, A13 was updated only on one slot with the new bootloader, while the second slot is still stuck with the previous bootloader. During the flashing (how did you flash?), something went wrong, so the Pixel wanted to boot from the second slot with the "old" bootloader and the "Anti-Roll-Back" kicked in.

RMA and hopefully get an exchange

Cheers
[Google Pixel 6] J0nhy:
Follow this steps and let us know if it worked for you

1. Unplug the cable from your phone

2. Press and hold for at least 15 seconds the power button then release

3. Connect a cable from your pc to your phone but you need to press volume up and hold it until you connect the cable, once connected release the button your phone shall turn on fastboot mode, it it worked just proceeded and flash a13 again, just download it from it's official source

14. Profit
[Google Pixel 6] mohamed_emad10:
i have flashed using fastboot commands and that was on both-solts

Do you have idea how manufacturing put the Rom on devices? OR about

cdc-acm connection?
[Google Pixel 6] mohamed_emad10:
i have tried but nothing work
[Google Pixel 6] wooly909:
Hi i got the very same issue with my Pixel 6 Pro, where you ended up with your issue?
[Google Pixel 6] XdekHckr:
nah, it doesn't work
[General Questions and Answers] Privacydroid:
So i'f installed an app on my lineageos device, the app included google analytics and google firebase, for example: com.google.firebase.analytics.

The app is now uninstalled and i want to find out if there are any remainings of google still hidden somewhere, and if so how do you get rid of them?

I'f heare that for example if you install gmail and uninstall it, that some part of the app will remain active on the device even when the app has been uninstalled.
[General Questions and Answers] xXx yYy:
Run SD Maid Pro app