yashsingh1/xdaforums huggingface dataset:
[General Topics] hkjo:
/optics/configs/carriers/<3-letter-csc>/conf/cscfeature.xml

Decode the XML with OmcTextDecoder. No need to reencode before using it back on the phone.

I copied all the files from that directory, modified the XML, and overridden the original directory with a basic Magisk module.

It's there on my XXU 1BUC3 (CAC), inside Developer Options.

1BUC3 and Magisk 22.1 here.

Not sure how the retail models correlate with firmware versions, but you already have the phone so probably just mind the firmware version.

I think the 2nd letter after the base model is color (B/K/W = black/red/ white?).
[General Topics] F308:
I did but it was in other thread.

https://xdaforums.com/t/magisk-module-universal-safetynet-

fix-1-1-0.4217823/page-34#post-84835899
[General Topics] F308:
Easy said.

This action I would do first time then questions come in bunches.

Search results are not clear enough for me.

There's no such thing like "Basic" Magisk module then I understand it was just term you used telling that you used Magisk itself to do it.

How exactly?

Did you create zip containing this directory and installed it with help of Magisk?

Did you modify boot.img?

Did you use REPLACE= feature somewehere?

If yes - where? Where you located modified directory?

I see Magisk tree like:

/sbin/.magisk/

|---block

|---busybox

|---mirror - (many dirs here)

|---modules

|---3c

|---hosts

|---MagiskHidePropsConf

|--- rootdir - (many dirs here)

Hints would be very appreciated.

For now, before you answer, I probably replace file directly but the knowledge would be very useful in future.

I would revert direct modification.
[General Topics] hkjo:
Yeah, I meant the word literally. See attached for what I'm using on a "CAC" CSC. I've replaced the "conf" directory on Magisk's post-fs-data.sh stage. Not sure if that's the ideal but it works.

Install from the Magisk app like any module.

CSC settings changed:

Camera_ShutterSoundMenu =

true

Common_DisablePhoneNumberFormatting =

false

(

show phone numbers with dashes; too bad it still ignores dashes you write manually in contact numbers)

Contact_SupportDuoVideoCall =

false

(don't integrate Duo into the normal dialer)

Setting_SupportRealTimeNetworkSpeed =

true

(shows transfer speed in status bar; stupidly, the toggle is available in the settings only when connected)

VoiceCall_ConfigRecording =

RecordingAllowed

---

By the way, there's Android 11 with OneUI 3 rolling out now.

Not sure how it affects the CSC features enabled above.

Besides that, as usual, Samsung take a step forward and at the same time a step back. OneUI 3 degrades some GUI and features, just like OneUI 2.x ruined other things (like the battery graph). I'm thinking, best hold off for now, or even avoid it entirely.
[General Topics] F308:
Thank you.

Will try bit later.

In the meantime I loaded modified cscfeature.xml directly to it's place, added only one line which was mentioned in thread.

Tried Magisk Skvaler recording module but it is paid and I won't buy it at this moment.

Bad luck. It expired for me today as I tried it once in the past.

External recorder, Cube ACR, recorded only my voice.

AFAIK Android 11 won't have recording limitation, then maybe efforts will not be necessary but HowTo knowledge is always worth it's value.

For my country it is not published yet.

Hope TopJohnWu will adopt Magisk quickly to use it if such necessity occurrs.

Maybe not.

All the best for you.
[General Topics] Bagoreng:
I would like to report that for some reason OEM Unlock option has reappeared in Developer Options, it happened after I first connected to the internet and installed some other apps such as DNS66, Firefox, OpenCamera etc. I don't remember doing anything special through adb or flipping any settings in the last minutes of the initial configuration process. So it's kinda weird.

With the basic setup done I have now returned the phone to the relative and hopefully they don't mess anything up, but if I need to see/configure anything more I can ask them at will, I might continue fidding with it through the months perhaps bringing some feedback to the community where I can. DNS66 is quite a bit crashy here and I'm not sure what could it be, if it's something I removed too much, but I managed to make it work by editing the default hosts file that's cached locally and blocking the update URL so it'll stay how I'd like it, because the thing crashes when I try to add new filter or edit the default one, pretty much stuck and unusable otherwise.

Thanks for your report, tho you did upgrade from an already installed Magisk previously right? (or does it need reinstall after upgrade?)

Yeah it's black, but no idea, haven't found anything more on this.
[General Topics] hkjo:
No, I didn't have Magisk on the older firmware.

I OTA-upgraded to 1BUC3, Magisk-patched the same firmware, flashed with Odin. Needed to install the Magisk APK afterwards, since I flashed CSC_*.tar.md5 rather than HOME_CSC (which presumably leaves the user data intact). Not sure if that's required, but that's what I did.
[General Topics] F308:
Did you have root access and Magisk at this moment?

If so - OEM Unlock is visible this way, but it is not certain what it means.

Important is that you have root.

Later Magisk modules may behave in weird way sometimes, that we have to be aware of.

Once you have root you are at home.

Even flashing modified ROM second time or doing factory reset doesn't remove it.

If app complains hide magisk for it.

Added later:

I installed ACR phone, agreed for everything it required, still recorded only myself.

Maybe really it depends of country?

In mine recording is allowed if remote person know that he is being recorded.

hkjo:​

1. I created my zip following your example.

2. What do you use to record calls?

3. Weird thing:

While my ROM is OPV - in Settings->About phone-> Software info > I see Service Provider SW ver. like XEO/XEO,XEO/EUX/XEO.

What the hell that supposes to mean?

Maybe I should load modified cscfeature.xml to those directories instead of POV?

Added later:

Sorry, you wrote already:

I enabled something but recorded only myself.

Need make second try.
[General Topics] hkjo:
The native call recorder, which is a button in the stock dialer:

https://preview.redd.it/k1qsxx3pd83...bp&s=978e2657fa54a2e568adebc9939724a805f78ba0

That wasn't me. ACR didn't work correctly here.

4 slash codes? Only 3 here (one is the comma separated dual-SIM item), and that's also what I recall seeing on the web.

Try changing inside XEO.

EUX seems to be Germany. Most codes are under /configs/carriers/, but EUX is of the few that are under /configs/carriers/single/. Maybe something special about it.
[General Topics] Bagoreng:
No, I was not attempting anything custom at all. I was still proceeding with plan to configure the phone without root or anything custom, just ADB debugging. And didn't bother unlocking the bootlader. I wasn't trying to root from the beginning, when I saw lack of Lineage OS and TWRP, too risky in this case. I might attempt it somewhere in the future tho. Relatives got really stubborn about "so many days" without the phone.

I tried to configure the phone with ATH2 build. It ended up being mostly learning experience. Throughout I found some side effects and bugs and other inconveniences lefover by the months of phone usage since it's purchase. I ended up doing a factory reset. Then I updated the FW using the phone it self, over Wi-Fi, the official way. And another factory reset. After that OEM Unlock was nowhere, I even searched the whole settings for it and nothing. I proceeded with the ADB only plan to debloat the phone. I was regularly in Dev Options setting other things and did infact periodically check for the OEM Unlock option and I never saw it. And then when I was almost finished, literally, then I see it, and I can't remember what exactly could have caused it because about 1-2 hours of connecting to the internet with WiFi, installing 3rd-party-apps, inserting SIM card and connecting with Cellular was all there. One of those actions may have triggered something else to trip and so on. Who knows. This may be a bug or it may be intentional.
[General Topics] F308:
Banzaiii!!!

That I tried and it works.

Solution so far may be in one of two points.

Either it was XEO where change was necessary or it was matter of button which initially was not visible.

I had "add other caller" instead of "record call".

I made changes in both, XEO and POV, added as well your line related to CscFeature_Camera thinking that you added it for a reason:

<!-- === Mod1 === --> <CscFeature_Camera_ShutterSoundMenu>TRUE</CscFeature_Camera_ShutterSoundMenu>

<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>

<!-- === Mod2 === -->

(Only those two lines were added).

Voila!!!

Bow of respect and thanks for help.

BTW:

Right now in place of "+" button I have recorder button.

Do you eventually have an idea how to add "+" to screen again?

It adds another person to call, now it is not possible while sometimes useful.
[General Topics] hkjo:
You can use instead the menu's "Add Call".

I don't know if it's possible to configure which buttons appear in the dialer's main screen.

Well, yeah. To be able to have the camera silent without muting globally. :)
[General Topics] F308:
1. Somehow recording button replaced "+", but it is not that important now.

Maybe it is embedded in dialing application?

2. Well. Then this had nothing to do with recording.

I wondered if eventually camera had shared function which might be used in recording as it records sound.

Nevermind.

Feels good to win the battle, allies like you should be appreciated, too.

You are part of the success.
[General Topics] hkjo:
Yes, but the Add Call function is still available in the menu. Maybe Add Call would be more useful as a button than Bluetooth, but it's not a big deal.

Next things to fix (not me :)): get 60fps video recording to work somehow, get some GCam to work, have the Bluetooth icon show in the status bar, better battery graph (like in older OneUI)...
[General Topics] F308:
I remember that with video there were problems in the past.

HQ video didn't work well with stabilization, sometimes phone simply didn't connect to camera and reboot was the only solution.

I didn't fight with it too much.

4K video simply consumed megabytes of space in nulltime.

For myself I met in the past graph which displayed realtime network traffic on status bar.

Digits are displayed by many apk's but they are not readable without magnifying glass, graph was marvellous.

BTW:

Did you use BetterBatteryStats?

It was giving much information.

Following conclusions from those data I had nightly battery usage in range 0.1-0.3%/hour, sometimes 0.5-0.8.
[General Topics] hkjo:
Didn't try, nor any other battery apps. I almost always prefer stock features/apps, especially for low-level features. Better compatibility, potentially lower power, lower privacy risks...
[General Topics] F308:
Sure, but you loose nothing trying.

BTW:

Recording works like AK-47.

Was very useful the second day after I succeed get it acting.
[General Topics] hkjo:
Now we just need to get video recording working like an M16 (or better, M4? :)).
[General Topics] F308:
I found this:

https://xdaforums.com/nexus-6p/themes-apps/mod-camera-nx-v4-google-camera-zsl-hdr-t3494435

Didn't read.

Myself I seek a word about Daily Job Scheduler.

At least working command line which would give me pattern to compose my own one.
[General Topics] Akhil99:
Hi there!

I could help in bringing up TWRP and start some ROM development.

DM/Message me :)
[General Topics] hkjo:
If I got it right, it appears most GCam versions/mods don't work on Mediatek SoCs, like in the A41. The Nexus 5X is Snapdragon.

I tried a few of the suggested versions in the site below, none worked.

Google Camera Ports Download

Modified Google Camera ports (Pixel Camera) by BSG, Arnova8G2, BigKaka, Shamim, and others. Download hub for GCam ports.

www.celsoazevedo.com
[General Topics] F308:
Hence we keep nearly all A41 related information here I can tell that while ago I upgraded Android to version 11 which appeared 1-2 days ago on sammobile.com.

No problems at all.

I modified AP_* by the book, downloaded it to phone and voila!

Not even lost apps, personal settings, call history, contacts etc.

I feared I will have coming night sleepless but bit of luck is worth more than tons of hard work sometimes.

One thing:

Magisk fails when I want it to hide it but it hides itself from applications and while my bank apk works IDGAS.

Akhil99:​

Anything what you will bring to the table will be appreciated.

Myself I am not on level which allows me to work on things like you mentioned, but I'd enjoy seeing TWRP, yes.
[General Topics] Akhil99:
I would need someone to test the TWRP I build. We can chat on telegram with group chat or personal chat. here's my telegram @cha0scl0wn.
[General Topics] hkjo:
@F308

I think I read Android 11 breaks video recording with screen off?

(Like with this app.)

And while Samsung's OneUI 3 may have some improvements, it seems there are also downgrades. Has the full QuickSettings screen become 3 lines instead of 4, or app drawer folders 3 icons in a line instead of 4?
[General Topics] F308:
Well.

Bit of weird to record video with screen off.

Anyway I am not much interested in recordings.

I don't know exactly what you mean with QuickSettings.

If I've seen image would be helpful.

Concerning icons on screen I don't know, I had 6x5 icons on screen and it remained this way after upgrade then I don't know how initial setup looks like.

There is native call recording but having Magisk module which you provided to me I don't know how it works.

Will check one day after disabling module.

Right now I am checking what is different comparing to Android 10.

It would be good to have list of Samsung Android 11 bloatware to freeze.
[General Topics] claudito77:
I confirm quicksettings screen is now on 3 lines
[General Topics] F308:
For the records:

I finally passed through SafetyNet check.

Switching off debugging was final change which helped.

I missed this point earlier.
[General Topics] F308:
Hello again.

Do you remember this discussion?

I wanted help a friend and activate recording on his Galaxy S9+.

First - there was no such path like above.

I found cscfeature.xml file under /odm/etc/omc/XEO/conf, modified it following former method which was working on my phone, but it does not work.

I attach this directory zipped and final stuff, if you would do me a favor and have a look I would be grateful.

Maybe you will discover something what I missed?

Maybe variable allowing recording differs from A41?

This is the point.

I checked presence of modified cscfeature.xml in place where it should be, that means mounting module directory by Magisk worked.

Thank you in advance.

Have a nice day.
[General Topics] hkjo:
I think it's somewhere else. Maybe like this one:

https://xdaforums.com/t/enable-call-recording-editing-csc.3866537/

The CSC setting name is probably the same.

Best continue under the S9/+ forum... :)
[General Topics] F308:
Thank you.

I was there however have still lot to read.

Looks like despite the same Android version behavior differs, necessary actions follow.

Surely I will try.
[General Topics] F308:
Sorry for late reply.

I came to the idea that I could try while I am not busy what recently was the case.

I don't use telegram but for a while we can communicate here via private messages if not in posts.
[General Topics] F308:
Again after certain delay, new related question.

Is there a way to override only one file, not directory?

One cannot "mount --bind filename" and duplicate big directory where only one file differs from original may be troublesome.
[General Topics] psychowood:
Hi, can someone confirm that there's no CSC with call recorder enabled out of the box yet? AFAIK with an official CSC it should be possible to flash with Odin keeping knot & so on... I'll root it sooner than later but this phone is not for me and I'd like to keep it stock for a while if possibile (OTA stopping is the deal breaker here).

TIA
[General Topics] hkjo:
BTW, still no A41 subforum on XDA. The admins must have something against this model. :)

Not sure. Try asking under the big unwieldy Magisk thread:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/page-2409

But why not copy and override the whole directory? Unless you mean it's many MBs.

I haven't looked in recent months, but AFAIK the model wasn't officially released in countries where Samsung enables call recording.

It's a 2020 model, so probably no more variants since then, but check the firmware sites to see if you spot any suitable countries. There's a list of candidates, I don't know if complete, here:

https://xdaforums.com/t/enabling-native-call-recorder-through-csc.3962224/
[General Topics] F308:
Yes, this was always a solution however mounting /system/etc would interfere with hosts module which is there thanks to Magisk.

I could overwrite one action by another.

I wanted change /system/etc/gps_psds.conf.

There is line: NTP_SERVER= ...

which points to North America, guess for all worldwide ROM-s.

I preferred to point it nearer, to my country NTP server.

In the meantime I kinda cheated.

I loaded modified gps_psds.conf to Magisk hosts module directory, /data/adb/modules/hosts/system/etc/ and it worked using "coleague's" functionality.

Not sure how hosts file is mounted under /system/etc, though.

This module is likely embedded since some time and doesn't work alone.

I loaded there my own hosts file, too.
[General Topics] hkjo:
If I'm not mistaken, just place your file in the module ZIP under:

/system/etc/gps_psds.conf.
[General Topics] F308:
Thank you.

In the meantime I found that 'mount --bind' works with files if target file exists.

I didn't know it until now.
[General Topics] Akhil99:
Hello to everyone looking for support for the Galaxy A41.

I am pleased to inform that I and Aya have been able to unlock bootloader, patch vbmeta and get basic TWRP booted on the SM-A415F Mediatek.

{Mod edit}
[General Topics] F308:
I am in, but I don't see much there.

Would you give me some hints?

Eventually via PM.
[General Topics] Oswald Boelcke:
@Akhil99

As an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads. These conditions obviously don't apply to your post, you or this thread. For this reason I've removed the reference to Telegram. Please refrain from sharing of social media links or attempts to drag members to them in future. Thanks for your cooperation!

Regards

Oswald Boelcke

Senior Moderator
[General Topics] F308:
Do you remember me?

I have a question.

Partially related to thread.

Hence you knew how to enable native call recording maybe you know how to enable native screen recording in Android 11.

I was looking around, but didn't find anything interesting.
[General Topics] hkjo:
@F308

Yes, I still remember. :)

No idea about the screen recorder.

But aren't there tools in the store?
[General Topics] F308:
Well.

In the meantime I came to the same conclusion.

Still would prefer native to avoid overkill but anything working will be ok.

Thank you for quick reply.
[General Topics] mesteri7:
Dear all, here is the way to Unlock the bootloader, in details that are comprehensible even for a complete beginner, as myself :) This surely worked perfectly for me.

Unlocking Bootloader of Galaxy A41

1. First you Enable developer options in Settings/About phone/Software information by tapping 7 times on the build number.

Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some circumstances.

2. Allow bootloader unlocking in Developer options → OEM unlocking

2.1. Reboot to download mode by doing this: power off your device and press the download mode key combo VOL UP+VOL DOWN, connect to PC while pressing the buttons. Warning will come about custom OS. (Usually to continue to Odin mode, you Press Vol up but here: )

2.2. to continue> Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot. Press VOL UP to confirm

2.3. Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.

Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. If grayed out option is not there, get it back with method which you find if you search for „How to Fix Missing OEM Unlock in Developer Options on Samsung Phones” (the one which says to change date/time and disable some automatic actions the phone does, etc. ).

Your bootloader now accepts unofficial images in download mode

3. Go to download mode > pres VOL UP+VOL DOWN simulataneously and while holding, connect phone to PC

to continue: VOL UP

to simply exit download mode, press VOL DOWN+power button for 7 sec

Check if the bootloader is unlocked. At this point your oem lock shall be indicating> OEM LOCK: OFF (U) (If it is still locked, it will say OEM LOCK: ON (U).
[General Topics] mesteri7:
The good news is that basic TWRP for A41 was already created by @Akhil99 . -Cheers to Akhil!!- Who can help create the final stable version? The phone could enter and fully use TWRP but one could not launch Android from it. We got stuck trying to modify/exchange fstab in the boot.img. I have the phone, Akhil has the knowledge! :) However maybe the simple issue of Odin version described in next message could help solve it all? @F308 @hkjo @Minuz
[General Topics] mesteri7:
At this point I try to root the phone. I applied the methods described here earlier to Android 11 and had no success. I use Odin v3.14.4. and Magisk v.23.0, patching the full 5Gb AP from the newest samsung stock software. Also tried patching only the boot.img.

Maybe I should do it all using Android 10 like @F308 described and after the root upgrade to Android 11... Any tip would be much appreciated.

However, maybe the problem for not being able to finish creating stable TWRP and rooting the phone is because of Odin? @Zirila said that all versions 3.14.4 are fake... Made me think... Has anyone a link to a "not fake" version of Odin?
[General Topics] F308:
Well.

I used Odin v3.14.4 all the time, don't remember from where.

To identify it I provide MD5SUM:

50860de40988969f3ea3f308c6143e1d Odin3_v3.14.4.exe
[General Topics] A2HX:
I may could help developing for this device but I need a partner

So, if there is someone out there to help me with it

then I'll try to make something for it
[General Topics] mesteri7:
Thanks a lot, @F308 . I found out that the one I used had different parameters! Maybe that was causing my problems! Now I downloaded another Odin and made sure it is the same as you used. I will repeat all my previous efforts but now using "your version" of Odin. :)
[General Topics] mesteri7:
I tried to root my A41 so I wanted to do it the exact way you did, to be able to root it.

I downloaded the same samsung sowftware (Android 10) you used first, I obtained the same Odin version you used but still cannot successfully flash the patched AP.

I flashed all: BL + complete AP patched by the latest Magisk app from Play store + CP+ CSC. Which version of Magisk did you use? Did you flash all categories or only the patched AP?
[General Topics] F308:
I followed instructions from:

Installation

The Magic Mask for Android

topjohnwu.github.io

There is said that you flash everything.

At this moment I used Magisk 22 and I had Android 10.

Pretty soon version magisk 23 and Android 11 appeared.

I patched the same way AP from Android 11 and flashed everything except CSC again.

Instead CSC I flashed CSC_HOME to keep my data on phone.

So far so good.