yashsingh1/xdaforums huggingface dataset:
[Redmi 9C Guides, News, & Discussion] help_me_pls:
how to unbrick redmi 9c ? please xda forums make a 2024 version tutorial
[Android Q&A, Help & Troubleshooting] donotprikel231:
I have TWRP which i flashed to the phone without problem with flashfire, but the fact is that the bootloader is locked and says the recovery is not authorized by AT&T. I want to know can i sign the TWRP recovery firmware to the manufacturer or as the official firmware so it can mimic the official one and work. I doubt that is possible but it could be possible because of how outdated the secruity patch it but i just want a complete awnser.

Im using the Samsung galaxy S5 SM G900A AT&T on rooted android 5.1.1 lollipop.
[Xiaomi Poco X3 Pro] darksafferHK:
Greetings,I am a x3p user recently i flash crdroid 10 a14. I flashed it successfuly but I cannot disable the force encryption. i have tried all the dfe file and the universal once too but it didn't work just bootloop.So what's the reason in here is it about a14 or something doing wrong here.I am want know how to dfe android 14 crdroid thanks!!
[Android Q&A, Help & Troubleshooting] DJ_Steve:
hello all,

got a question i cant seem to find an obvious solution to and its not specific to a device so i thought best to post in here.

ive got a Samsung Galaxy Tab S6 Lite LTE (exynos) that i have repurposed and mounted into the dash of my car replacing the head unit.

this works really quite well and i am using macrodroid to power on and off the display and radios based on charger status but here is the problem i am having:-

im using a usb c hub which supports usb power input to pass through power to the tablet and also has a inbuilt audio and hdmi(future plans) output - this all works fine and tablet even sees usb drives connected to the hub. but once power is removed (when i turn off the car) the tablet switches to powering the hub from the tabs battery, this is rapidly draining the battery in the tablet in probably under 12 hours.

im wondering if anyone knows a way of disabling this reverse power mode somehow as if i change the usb settings to disable charging the audio stops working via the hub.

tablets running a custom build of lineage 20(to enable/disable some bluetooth profiles and audio routing changes) if it matters.
[FYT Android Head Units] Moldeb:
Thanks much, will try! Two questions, as I'm coming from an older FMC version (w/o mainservice) and also use @seb21's swc tool - and would replace FMC with FET now:

Would the FMC functionality to restart apps from suspend on the basis of the various text file catalogues be lost? I assume so, not sure how relevant this is to me.

@seb21's tool would remain unaffected, correct? That one is more important to me, as I have canbus SWC and remapped keys.

Thanks for your time!

Edit: Attached updated strings.xml for DE_DE, if you have use for it.
[FYT Android Head Units] surfer63:
FMC and @seb21 swc tool are completely independent.

"Would the FMC functionality to restart apps from suspend on the basis of the various text file catalogues be lost? "

Currently yes. If FMC is still functioning for you then please do not uninstall.

And again the question: Does the lockscreen work in FMC? If you tab the physical home key or Back key on the side/bottom of the unit. Does it stay locked or will it go back to the unlocked home screen.

Und danke für die deutsche Übersetzung.
[FYT Android Head Units] surfer63:
Apart from Atoto, where I understood this is limited, you can add apps to the "start on boot completed" file yourself via

Settings -> User - > Application Setting ( which applications you want to auto-start when you start your car and unit )

You don't need FMC for that. FMC had it before FYT had added it to the Settings apk.
[FYT Android Head Units] Moldeb:
Can test the first one only as my unit has no physical buttons. Have never used the lock function as the radio runs it's own Google account (family, locked down pretty much)...
[FYT Android Head Units] Gscipione:
Hi @surfer63, I complete translations in Italian. You made a great job and thanks for all that you are donig for this Units.
[FYT Android Head Units] surfer63:
I now understand that you mean the application that should be started at BOOT_COMPLETED and should be "whitelisted" in /oem/app/pwctl_config.xml.

However, the last 3 7862 firmwares (kernel date 20231226; apps date 20230104) and the last 2 9863 firmwares (kernel 20231208; apps 20240103 ), no longer have this pwctl_config.xml.

As if FYT/Mekede is changing their approach. Or as if FYT/Mekede made a big mistake by forgetting to package these files in their latest app layers (7862 and 9863 are identical)

I started working on the "enable apps from boot", but I first want to wait on newer firmwares. This is a lot of work and I don't want to do it for nothing if FYT changed their setup.

Spoiler content hidden.
[FYT Android Head Units] Moldeb:
This is absolutely not urgent for me. Next thing I need to find out is how to uninstall FMC app, it doesn't work anymore but is a system app. Superuser is gone, FMC is still there...
[FYT Android Head Units] surfer63:
Simply create a 7862lsec.sh (or 8581lsec.sh) script containing

#!/system/bin/sh
# remove FMC
rm -rf /data/dalvik-cache/profiles/com.mariodantas.fytmanagementcenter*
rm -rf /data/dalvik-cache/arm64/*com.mariodantas.fytmanagementcenter*
rm -rf /oem/priv-app/com.mariodantas.fytmanagementcenter*

I already used it
[FYT Android Head Units] Moldeb:
Thanks again, this has worked beautifully!
[FYT Android Head Units] marjanoos:
@surfer63 please find attached polish translation
[FYT Android Head Units] surfer63:
Thank you. I will apply them tonight.

You might have already seen that some translations have already been prepared but not used yet in the app.
[FYT Android Head Units] leo989:
Great. May I suggest you find a way to set dark mode without root & reboot needed, because Tasker and also SystemUI tuner can do it with non-root devices and doesn't need a reboot. Tks.
[FYT Android Head Units] surfer63:
As of Android 10 there is a standard function to do this, but that is only allowed for system apks. I do sign my apk with the system platform keys, but I don't want to push my apk into /oem/app as well and whitelist it it.

I have no idea how Tasker and SystemUI tune can do this without being a system app. Google very clearly mentions that this is a necessesity as it is against design policies and therefore not allowed for "any" app.

I will have a look anyway.

Edit: to expand a little on this (using the Android 10 option):

On Android 10 and later versions, you can use the UiModeManager class to set the system-wide dark mode programmatically. Note that this approach requires the WRITE_SECURE_SETTINGS permission, which is a system-level permission. It's generally not recommended to request this permission unless you are developing a system app or have a specific use case that requires it. Android apps should follow the user's preferences and the system-wide dark mode setting, and requesting this permission may result in your app being rejected from the Google Play Store.

I do have a specific use case and of course I don't care at all about the last sentence. Like said: I don't want my app to be a system app and whitelisted. That would require to make changes to the kernel (like Mario does for his fmc in his MD-Edition kernels) and then push my app via an lsec script to /oem/app or /oem/priv-app. I

want my app to be able to run on any FYT, be it that you need root mode if you want to use this specific functionality. Maybe Tasker got "permission" from Google, I don't know.

Edit2: I just checked fmc and fmc uses the exact same rooted approach even though fmc is pushed as system app and whitelisted in ther MD-Edtion???
[FYT Android Head Units] leo989:
you are right, Tasker and SystemUI tuner required "write secure settings" permission and do not need root, I enabled it via ADB shell when I installed them.
[FYT Android Head Units] surfer63:
Released a 1.0.4.

No big changes but a number of small fixes/changes and two new translations (Polish by @marjanoos and Vietnamese by @paypal@telegram)
[FYT Android Head Units] surfer63:
Released a 1.0.5.

This is the one I actually wanted to release, but I ran into all kind of stupid issues Yesterday and got fed up with it.

I added a button "Edit config.txt" which allows you to edit the config.txt on the unit. It will then be flashed immediately after saving. This requires a rooted unit.

See image below. Click for full size

View attachment 6063916

After saving you will see a short popup warning you, and then the below "flash" popup.

View attachment 6063911

Changelog:

- Added the "Edit config.txt" button/functionality

- Added a check that will disable the two rooted buttons if you do not have a rooted unit.

- And some new untranslated strings (apart from Dutch of course ;) )
[FYT Android Head Units] surfer63:
Hi @Gscipione. I completely overlooked your post. I am really, really sorry.

Thanks for your contribution.

Recompiled and released a version 1.0.6 with Italian translation.
[FYT Android Head Units] Gscipione:
I translate last version of your app 1.0.5 in italian so you can release it in the version 1.0.6.
[FYT Android Head Units] surfer63:
New release 1.0.7

- Add new functionality to add the default Android Bluetooth Settings to the FYT Settings (thanks to @brymbrym for the idea)

- Added a number of error checks.

- Updated translations (Italian, Polish, Dutch)

Spoiler content hidden.

Edit: immediate change to 1.0.7b. I forgot to add a check that the button for this rooted function will be disabled when your unit is not rooted.
[FYT Android Head Units] surfer63:
What kind of unit? How did your root your unit with which method/root option?

And is root working with other apps?
[FYT Android Head Units] Aleksandr_B:
Fyt 1. Root received your kernel from a neighboring topic. Magisk 27 from there. Total commander received root.
[FYT Android Head Units] surfer63:
Really strange.

OK, but 7862, 8581? And which brand, if any?
[FYT Android Head Units] Aleksandr_B:
7862 Lehx
[FYT Android Head Units] DrumVlado:
Hi. I couldn’t find an answer to my problem, so I am writing. After I initiated a config edit, I get the “install new firmware” dialogue on each restart. Should I delete some file somwhere?

Thanks
[FYT Android Head Units] Gscipione:
Nice job @surfer63. Looks great in Italian.😍😍
[FYT Android Head Units] bautrupp:
Nice work indeed!

But could you please put the version number in the file name?
[FYT Android Head Units] surfer63:
I am currently restructuring the app to clean up the screen and add two menu's top-right..

What is the resolution of your unit? It does not display correct, but I do use "auto-res".
[FYT Android Head Units] surfer63:
Yes, fine with me.

Next one will have it.
[FYT Android Head Units] Gscipione:
My resolution is 1280x720. My unit is m6pro mekede with the last Firmware of January
[FYT Android Head Units] surfer63:
I really don't understand that. My M500S is also 1280x720. The screenshots I post are all made on my own unit.

Anyway: I will move to 2 columns with a few "buttons" in the most top-right menu ":" and the lockscreen in a menu "lockscreen" left from it.
[FYT Android Head Units] Gscipione:
It is very strange because I have same resolution and same kernel of your unit but the format of the column is different. The first 2 are bigger and the last one is smaller.

What could be the issue?
[FYT Android Head Units] surfer63:
Version 1.0.8

Restructure of the app to clean up the main screen. Added two "option menu's" in the top-right

Removed currently untranslated strings for Spanish, French and Portuguese.

Translators:

More logical renaming of strings.

A few added strings.

All strings have been alphabetically sorted.

The "pin code disclaimer" (Pin: Read me!") has been enlarged and therefore set back to English.

You have seen quite some releases from me in the past 1½ week. I will now slow down considerably, so you will most likely not see new functionality on short term.

If I receive updated/new translations, I will recompile another version and release that immediately. That is easy work.

Spoiler content hidden.
[FYT Android Head Units] surfer63:
Please check the new version 1.0.8.
[FYT Android Head Units] Gscipione:
I will try it now and tell you. It attach you find new translation for version 1.0.8.
[FYT Android Head Units] Gscipione:
With new version
[FYT Android Head Units] surfer63:
Did you attach the correct one? It is 100% identical to the one already in 1.0.8
[FYT Android Head Units] Gscipione:
Sorry I did not save the file now is correct.
[FYT Android Head Units] marjanoos:
I think that's because of the length of buttons. They are dynamic depending on how much text is on them. The longest description describes how wide will the column be.

For example in my case right column is shorter than left one. Because my translations are much shorter than italian or english.

I also have one suggestion, to change the english translation of Buttons with \"the android with root on its chest\" require root access.

I'm a young man and I can see the android robot on the buttons, but I definitely can't see what text is on its chest.

My suggestion is something like:

Buttons with green Android icon require root access.

I will also make another improvement of my translations as I installed the app today and some of them need to be refined.
[FYT Android Head Units] surfer63:
You are completely right. I use the standard settings "wrap_content" which indeed auto-scales to the longest content on a button or in a menu.

I fully agree. I will change it in the English and (my) Dutch strings.
[FYT Android Head Units] Gscipione:
also for the Italian version I full agree with the changes that @marjanoos suggest
[FYT Android Head Units] surfer63:
I just checked German, which I can translate myself for 90%. German is really a "long language".
[FYT Android Head Units] Moldeb:
Could try to shorten the terms, might then be a less accurate translation but would still get the meaning ;)
[FYT Android Head Units] mcvive:
...and many words for one and the same term
[FYT Android Head Units] Moldeb:
New DE version attached, tried to shorten text ;)

Also for DE I changed this string

<string name="firmware_upgrade_txt">In a few seconds you will see the popup with Start/Cancel for a \"firmware upgrade\". This is necessary to apply the changes.</string>

slightly to become

<string name="firmware_upgrade_txt">In a few seconds you will see the popup with Start/Cancel for a \"firmware upgrade\". \"Start\" is necessary to apply the changes.</string>

as otherwise in DE you would think the popup is necessary. Also now treated device/unit/headunit as synonyms now (system is different). Other than that I tried to stay coherent - but some text could get even shorter if I could use e.g. on/off for enabled/disabled ;)
[FYT Android Head Units] surfer63:
This will still be a popup and the length of the text is not an issue here.

I made it a popup to warn the users.

Otherwise some less experienced users might get startled if they suddenly see that the unit will do a "firmware upgrade".

The popup will be killed anyway after ~2 seconds (unless you press cancel for that firmware upgrade)
[FYT Android Head Units] Moldeb:
Sure, I haven't shortened that - just replaced "this" with "Start" to tell people they shouldn't press Cancel in that popup ;)
[FYT Android Head Units] surfer63:
Now I understand what you mean. That is indeed a good suggestion and will make it a bit more clear.
[FYT Android Head Units] surfer63:
release 1.0.8b

Only an update of Italian, German, Dutch and original English translation.
[FYT Android Head Units] Gscipione:
New version 1.0.8b
[FYT Android Head Units] marjanoos:
"Localisation" doesn't have to be direct translation. :) End user just must be able to understand the meaning.
[FYT Android Head Units] Moldeb:
German version 1.08b looks like this - if this is still too long then I've further shortened the two longest terms in the attached strings.xml. Meaning should still be ok in particular the app has an explanation for the Add standard BT settings to FYT settings button...

View attachment 6066253
[FYT Android Head Units] surfer63:
Version 1.0.9:

change bluetooth 0 name to ro.lsec.btname=Bluetooth builtin chip id=0;

update some translations

So still another release.
[FYT Android Head Units] surfer63:
That doesn't help though. And depending on the selected language on the unit, the name of BT settings entry in the FYT settings app changes. Strange.
[FYT Android Head Units] Aran:
Hi @surfer63 , really nice tool you are building. You asked for requests. Don't know if this is possible but:

-Is it possible to create script/button/link to download and install the latest modified kernel?

-Maybe same for latest updates on the firmware of adjusted interface from peace is

-possible to adjust the gain on the mic, and maybe other frequently used tweaks

These will really make tweaking more easy for many users.
[FYT Android Head Units] surfer63:
As such that's all possible.

kernel: I release all kernels with the "yyyymmdd" system build date in it, and when it is a uis8581/sc9863, I also add 9863 in the name. So yes, I could check the [ro.system.build.date] property of the unit, check the [ro.fyt.platform] or [ro.board.platform] for the type of unit, and see if a newer kernel is available.

peaceos: Theoretically this could be a yes, but the download link is "some random generated" link from yandex. I have currently no idea how to check for an updated version.

I was thinking of a screen with "tweaks" for the config.sys with checkboxes to activate/deactivate:

Disable or (re-)enable the mediaplayer at startup/wakeup.

Alter fytmanufacturer, maybe from a dropdown with the ~20 id's I know from the ~40 suppliers I know. But if the user doesn't know, that makes no sense. I could change the fyt.prop as well, but the config.txt is always parsed as last file. (and remove the stupid android 11, 12 or 13 from the fyt_build.prop)

Add/Remove the standard Bluetooth settings to the FYT settings for the builtin BT chip.

Tweak the microphone.

Having said (typed) this: I have no idea when I will do this. I already mentioned that I will slow down.

I also discovered that there is a "libsu" from topjohnwu's Magisk, which simplifies my root commands substantially and is made to work with Magisk.

That is now my first point of attention, together with the ToDo from post #1: Creating the AllAppUpdate.bin zip and "Collect system info" are currently "blocking UI actions" and that is how I want it to be (be patient), but the app doesn't show a progress dialog from start to finish. I made multiple apps where I did this, but it is still not working for FET.

Anyway: thanks for your suggestions. I appreciate it when users think along (although it is extra work for me ;) )
[FYT Android Head Units] surfer63:
And it works nicely. To be continued.
[FYT Android Head Units] newuzer1:
Another suggestion, enable ADB Wifi - haven't gotten to testing the code/modification myself yet.
[FYT Android Head Units] surfer63:
Enabling the adb wifi is one thing. But I can't enable the usb debugging in the developer settings (as far as I know). That should be a user action.
[FYT Android Head Units] surfer63:
Version 1.1.1 - 20240211

Finally managed to get a popup to display before the long(er) running "Zip FYT apps to AllAppUpdate.bin" and "Collect system Info" methods.

Translators: Changed string "dialog_start_collect_system_info" and "dialog_start_zip". Please compare with original English strings. (Note: I changed German and Italian myself. Polish, Russian and Vietnamese are too different to even recognize.)

Version 1.1.0 (not released, intermediate build)

Switch to topjohnwu's libsu that is part of Magisk (libsu: "An Android library providing a complete solution for apps using root permissions.")

(Yes, another release. Despite what I said.)

Click image for full size.

View attachment 6067035

View attachment 6067044
[FYT Android Head Units] Adamados:
Thank you, it worked for me too.

One more question, in my occasion i have some Manufacturer's Apps that i don't want (NEXAI+ , NEXAI Voice etc..)

As my unit is rooted with your kernel and i have Magisk installed, is there any way to remove this apps through any application or only via 7862lsec.sh script?
[FYT Android Head Units] surfer63:
You need a 7862lsec script for this.
[FYT Android Head Units] surfer63:
Working on a "tab" structure. It makes it much easier to structure, add extra screens ("fragments") and put long texts on buttons for more clarity.

I still have to flatten out a few bugs and some quircks.

Note that it is a simple, fixed non-gliding tab frame-layout structure. So no gliding/swiping in case of 85 tabs ;).

And I integrated/converted it into the "Main Activity" which is not as should be done when freshly designed, but any programmer having criticism: please improve my work. It is open source.

Spoiler content hidden.

I have a alternating week ahead: very busy, couple of days out of town, very busy again.

So probably close to next weekend I think to release it.
[FYT Android Head Units] Specy01:
@surfer63, In the third tab "lockscreen" the first option "set a pincode" really allows me to set a pincode even if the HU is "original", i.e. if i don't have the Mariodantes firmware installed or yours with Magix?
[FYT Android Head Units] surfer63:
This tabbed version is "work in progress" and has not been released yet. The current version is not tabbed and had the lockscreen option as a top-right menu.

Android uses the "keyguard" to lock the screens. This "keyguard" has been disabled on our unit (on every android head unit from every supplier for that matter).

This is a replacement functionality and lets you define your own pincode.
[FYT Android Head Units] Adamados:
So i suppose to remove this apk

View attachment 6067482

i need to run this script

#!/system/bin/sh
# remove FMC
rm -rf /data/dalvik-cache/profiles/com.txznet.aipal*
rm -rf /data/dalvik-cache/arm64/*com.txznet.aipal*
rm -rf /oem/priv-app/com.txznet.aipal*

did i understand it correct?
[FYT Android Head Units] surfer63:
Almost.

The last line needs to be "rm -rf /oem/app/com.txznet.aipal*"

app, not priv-app.

and the comment should not be "# remove FMC" ;)
[FYT Android Head Units] Moldeb:
Now got around to test a bit and found that when you use functions that require flash (edit config.txt, add standard BT to FYT settings) the pop up informing about the flash pop up shows but if you hit OK nothing seems to happen (flash pop up doesn't come up). It then came up though either after a manual reboot (BT settings add) or leaving the screen (edit config.txt -> save -> 1st pop up hit OK -> flash pop up doesn't show, instead I'm back in the edit window, had saved earlier so this time hit Cancel -> voilà flash pop up shows ;)

So in the end both functions worked but there was some hiccup in triggering the flash pop up.

I do like being able to edit config.txt on the fly, great work!

I don't know what caused the hiccups, once I briefly saw a Magisk message that FET failed on root rights - but it has root rights...
[FYT Android Head Units] marchnz:
Surfer is an xda legend, straight shooter and of a very small number that actually share what they know and answer questions to members of all tenure.

Hat tip to surfer63.
[FYT Android Head Units] surfer63:
I released a version 1.2.0.

Migrate to tabbed frame layout structure

Changed "android root icon" to "root prompt" (Translators: this might require a change in the string for these functions)

No further functional changes

Spoiler content hidden.

And this took much longer than "promised", but I had two sad occurrences in 2 weeks in the family. Focus was elsewhere. A bit typing in the forum is not so difficult.

There is now a Bluetooth Tab only containing 2 entries as I wanted to have a button displaying the bonded* devices for both Bluetooth Adapters, but somehow I could not make this work. And as said: focus was elsewhere.

So actually this is only a "cosmetic" change.

*: In case of questions: See BLE Pairing and Bonding
[FYT Android Head Units] WarSpaz:
Family first :)
[FYT Android Head Units] Moldeb:
DE translation attached.

Best wishes for your family!