[MOD ROOT] Enable native call recording on S8 Nougat - Samsung Galaxy S8 Themes, Apps, and Mods

You have to be rooted, with a root explorer add this line to system/omc/"your csc folder"/cscfeature.xml :
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
For example if you have an Italian csc you will have: system/omc/ITV/cscfeature.xml
Save and reboot.

Put root in the topic.

Would this work in any GS nougat device? Thank you...

BarbasanAB said:
Would this work in any GS nougat device? Thank you...
Click to expand...
Click to collapse
maybe, I don't know, tested only on my S8, bye.

Thank you! Working!

You might want to take/put note that not all S8 model has "omc" directory,
example, G950FD in some country using "system/csc/" directly instead, just like my country use "system/csc/XID"
but the rest of the steps or tricks is 99% similar,
files which needed to be modded are same files

I tried but stuck at "Custom binary locked by FAP Lock" when I reboot... I don't know what is my mistake

diego1810 said:
maybe, I don't know, tested only on my S8, bye.
Click to expand...
Click to collapse
on my s8 don't work...

This definitely works but there is a small typo in the OP. The code to use is:
Code:
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
Also remember to paste it inside the [FeatureSet] [/Featureset] brackets.

This doesn't work as it comes up with an error after the call saying, "Failed to save recording"

windowsdan4216 said:
This doesn't work as it comes up with an error after the call saying, "Failed to save recording"
Click to expand...
Click to collapse
I have used the code on multiple Samsung devices for several years now. Have you deleted the stock voice recorder app by any chance?
https://play.google.com/store/apps/details?id=com.sec.android.app.voicenote

windowsdan4216 said:
This doesn't work as it comes up with an error after the call saying, "Failed to save recording"
Click to expand...
Click to collapse
I have the exact same issue. I have also used this method successfully for years too. I can't figure out what's wrong.... The feature is enabled in the dialer and in settings...it appears the call is being recorded, but then when the call ends it says "failed to save recording. " Stock voice recorder is installed. Problem persists no matter which rom or kernel or csc is used.
I am using a UK version phone in USA on AT&T.....csc is BTU. I wonder if yours is the same?
Sent from my SM-G955F using Tapatalk

Thank you

RuggedHunter said:
I have the exact same issue. I have also used this method successfully for years too. I can't figure out what's wrong.... The feature is enabled in the dialer and in settings...it appears the call is being recorded, but then when the call ends it says "failed to save recording. " Stock voice recorder is installed. Problem persists no matter which rom or kernel or csc is used.
I am using a UK version phone in USA on AT&T.....csc is BTU. I wonder if yours is the same?
Click to expand...
Click to collapse
I am in UK using EVR (EE) CSC which is stock with stock ROM and stock kernal.
I get this problem and can't figure it out either. There are screenshots added to show the error I get ... However I can see that when you empty the /sdcard/calls folder and start a new call recording, you get a temp .voicecall file appear (which is a hidden file) but then it fails to save when the call is ended.

windowsdan4216 said:
I am in UK using EVR (EE) CSC which is stock with stock ROM and stock kernal.
I get this problem and can't figure it out either. There are screenshots added to show the error I get ... However I can see that when you empty the /sdcard/calls folder and start a new call recording, you get a temp .voicecall file appear (which is a hidden file) but then it fails to save when the call is ended.
Click to expand...
Click to collapse
Yes, that is exactly what I see too. I'll add that the Tasker actions to record calls also do not work and throw complaints about the source.
Sent from my SM-G955F using Tapatalk

Remember to set folder authorization with root explorer to 755 and file xml to 644

In my hunt to enable download Booster I found the activity for this setting in Nova launcher widget activity under phone. Called "auto record calls". You can enable it to record all calls, calls from numbers not saved, or specific numbees. No root required to enable. Not sure if enabling this will help turn something on for you guys. Just wanted you to know, if you didn't already, that it is there.

RuggedHunter said:
Yes, that is exactly what I see too. I'll add that the Tasker actions to record calls also do not work and throw complaints about the source.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
All of a sudden mine is saving the recordings properly?? I'm not sure how? But now it is.
I opened the voice recording app -> started a recording -> allowed permissions -> opened the csc folder in /system and made the permissions to my cscfeature.xml 644 and rebooted but not sure what caused it to start working but now it is!

windowsdan4216 said:
All of a sudden mine is saving the recordings properly?? I'm not sure how? But now it is.
I opened the voice recording app -> started a recording -> allowed permissions -> opened the csc folder in /system and made the permissions to my cscfeature.xml 644 and rebooted but not sure what caused it to start working but now it is!
Click to expand...
Click to collapse
Strange. Still no joy here. I have all three permissions granted for voice recorder and of course permissions are correct for the xml file... no idea what I'm missing.
Sent from my SM-G955F using Tapatalk

Peace of cake man ..thanks a lot . Working great on my 955fd .

Related

SMS enabler for MZ602, MZ616 Rooted Devices

Guys,
Since SMS / USSD Mod can be done successfully on XOOM 3G, MZ601 Devices, I thought to ask if you guys need to test this on MZ602, MZ616 Rooted Devices.
For that, I need testers with the following devices:
1) MZ602, Some 4G LTE devices are thought to not be able to have SMS enabled because of carrier blocking... We will check about that..
2) MZ616,
I will also give a script for roll-back procedure in case the MOD doesn't work...
wesamothman said:
Guys,
Since SMS / USSD Mod can be done successfully on XOOM 3G, MZ601 Devices, I thought to ask if you guys need to test this on MZ602, MZ616 Rooted Devices.
For that, I need testers with the following devices:
1) MZ602, Some 4G LTE devices are thought to not be able to have SMS enabled because of carrier blocking... We will check about that..
2) MZ616,
I will also give a script for roll-back procedure in case the MOD doesn't work...
Click to expand...
Click to collapse
Shoot it this way my friend - I will test
I know that sms mods work wonders for non US GSM Xoom devices,
would love to see it work on US CDMA/LTE Xoom.
Im down to test as well. My xoom is on a granfathered plan that has unlimited data and texting.
BTW my xoom is the lte model
Great. Thank you guys...
So plz send me your framework-res.apk and your location/carrier.
Sent from my MZ601 using Tapatalk 2
Still seeking?
wesamothman said:
Guys,
Since SMS / USSD Mod can be done successfully on XOOM 3G, MZ601 Devices, I thought to ask if you guys need to test this on MZ602, MZ616 Rooted Devices.
For that, I need testers with the following devices:
1) MZ602, Some 4G LTE devices are thought to not be able to have SMS enabled because of carrier blocking... We will check about that..
2) MZ616,
I will also give a script for roll-back procedure in case the MOD doesn't work...
Click to expand...
Click to collapse
If you are still looking for testers, I'm willing to do.
I have a 77.1.128.MZ616.Retail.en.EU with Android 4.0.4
Carrier is e+ in Germany
leicksta said:
If you are still looking for testers, I'm willing to do.
I have a 77.1.128.MZ616.Retail.en.EU with Android 4.0.4
Carrier is e+ in Germany
Click to expand...
Click to collapse
Yup, why not. Send me your framework-res.apk. it is in /system/framework/
I assume you are rooted.
I've attached it.
And yes 'm rooted.
leicksta said:
I've attached it.
And yes 'm rooted.
Click to expand...
Click to collapse
Here is the MOD
SMS-USSD enabler for MZ616: http://www.mediafire.com/download.php?oacihj4kniap2qn
Rollback in case it doesn't work: http://www.mediafire.com/download.php?bqo75tl6k7nata2
How to install:
1) download both files to your XOOM SD CARD
2) reboot into recovery and flash the mod (enabler)
3) reboot to system
4) make sure you have your SIM mounted for 3G.
5) open the messaging app (will be installed by the mod) and send an sms to another number; or better if you use gosms pro from the market. and send from another number to the one in your XOOM (send/receive tests)
6) open phone and dial a ussd code *#1234#; the number is different from provide to provider.
7) test and report back.
8) upon failure, nothing works, flash the rollback zip from recovery to go back to your original framework.
Hi, I tested your framework-res.apk but had to install (and recover) it with adb and busybox, because I don't have a custom recovery. Afaik I can't install one at the MZ616 due to the locked boot rom. If you know a way to custom recovery like twrp, I would give it a try
The result of swapping the framework-res.apk was the tablet was hanging in the startup with the "waving" Motorola logo.
One thing I noticed was the size of the new file: with 4881 kb it was very small compared to the 8254 kb of the original one.
Is there anything I may have missed, or any other clues?
Lothar
Sent from my XOOM 2 using xda app-developers app
leicksta said:
Hi, I tested your framework-res.apk but had to install (and recover) it with adb and busybox, because I don't have a custom recovery. Afaik I can't install one at the MZ616 due to the locked boot rom. If you know a way to custom recovery like twrp, I would give it a try
The result of swapping the framework-res.apk was the tablet was hanging in the startup with the "waving" Motorola logo.
One thing I noticed was the size of the new file: with 4881 kb it was very small compared to the 8254 kb of the original one.
Is there anything I may have missed, or any other clues?
Lothar
Sent from my XOOM 2 using xda app-developers app
Click to expand...
Click to collapse
Aha, I thought you are rooted which to me should mean you have unlocked boot loader with custom recovery installed. Didn't know you don't have that sort of recovery not installed... you got a boot loop maybe because you used the stock recovery .
Don't worry about the size of file, it is just a matter of compression level during building the apk...
Unfortunately, I don't own mz616 and I yet don't know a way to get twrp on it. Please lease with runandhide05 who might be able to get twrp up and running on your device first.
I'm working with runandhide05 on custom recovery.
But I also made some progress with your framework-res.apk and mms.apk: I installed them again (just to be sure) over adb shell with busybox, and now it worked and my xoom 2 rebooted fine. Now I can receive SMS, but only one time to read with SMSPopup. Sending does not function (I'm using Go SMS). I don't see any other SMS app, but the phone app shown up. If I try to open phone, I only get the message that contacts won't responding. If I open contacts, everything shows up ok, only the phone links don't work. I get the message thart com.android.phone is not responding.
Hope that helps yuo investigating further.
Best regards Lothar
Sent from my XOOM 2 using xda app-developers app
leicksta said:
I'm working with runandhide05 on custom recovery.
But I also made some progress with your framework-res.apk and mms.apk: I installed them again (just to be sure) over adb shell with busybox, and now it worked and my xoom 2 rebooted fine. Now I can receive SMS, but only one time to read with SMSPopup. Sending does not function (I'm using Go SMS). I don't see any other SMS app, but the phone app shown up. If I try to open phone, I only get the message that contacts won't responding. If I open contacts, everything shows up ok, only the phone links don't work. I get the message thart com.android.phone is not responding.
Hope that helps yuo investigating further.
Best regards Lothar
Sent from my XOOM 2 using xda app-developers app
Click to expand...
Click to collapse
On your ROM, stock one, do you have phoe.apk? Or MMS.apk without installing my mod?
I mean before you install my mod, can you check /system/app and see if you have MMS.apk there? If so, please send them to me. I am afraid the ones I included are for xoom1 family, not Xoom 2
wesamothman said:
On your ROM, stock one, do you have phoe.apk? Or MMS.apk without installing my mod?
I mean before you install my mod, can you check /system/app and see if you have MMS.apk there? If so, please send them to me. I am afraid the ones I included are for xoom1 family, not Xoom 2
Click to expand...
Click to collapse
I had before in /system/app: Phone.apk, PhoneAddons.apk, SmscSettings.apk, SMSPopum.apk and Contacts.apk
I only found and installe Mms.apk in your mod. Before the mod I only see Contacts as an App and after the mod also Phone shown up. But I don't see Mms in the apps.
I've attached the original (stock) apks.
leicksta said:
I had before in /system/app: Phone.apk, PhoneAddons.apk, SmscSettings.apk, SMSPopum.apk and Contacts.apk
I only found and installe Mms.apk in your mod. Before the mod I only see Contacts as an App and after the mod also Phone shown up. But I don't see Mms in the apps.
I've attached the original (stock) apks.
Click to expand...
Click to collapse
Oh, OK. Let me see if I can find compatible MMS.apk for your Xoom 2
leicksta said:
I had before in /system/app: Phone.apk, PhoneAddons.apk, SmscSettings.apk, SMSPopum.apk and Contacts.apk
I only found and installe Mms.apk in your mod. Before the mod I only see Contacts as an App and after the mod also Phone shown up. But I don't see Mms in the apps.
I've attached the original (stock) apks.
Click to expand...
Click to collapse
Alright,
I did some modifications to your framework-res.apk;
Indeed, there was this config defined in your framework
"config_text_sms_receive" but there was no send config
What I did is that I added send configuration "config_text_sms_send" and complied it. Also, changed the MMS.apk to a generic one that works across devices. I decompiled the compiled APK and I can see it persists in bools.xml and in public.xml; therefore, the reference was created successfully.
From SmscSettings.apk that you sent, I can see the option that your device can set the SMS Center number. You may wanna try to check that and put the SMS center number the same as the one of your phone "of course from the same service provider". And then try. I hope this works for you know; I can't test it cuz I don't have MZ616 device.
Here is the link; download it and flash it. http://www.mediafire.com/download.php?2b317ejrp7my9ew
In case you need to rollback, couple of posts earlier I included the rollback to original framework.
Good luck and let me know how it goes.
NOTE: I also enabled SIP capabilities for you; so I think you will be able to use your device as a SIP hub and SIP phone over IMS (IP Multimedia Subsystem).
Hi, this is really good news. It is a shame that this function is left out of the deveices ...
Is there any chance for getting that running on the MZ608, ICS4.0.4 ?
koerc said:
Hi, this is really good news. It is a shame that this function is left out of the deveices ...
Is there any chance for getting that running on the MZ608, ICS4.0.4 ?
Click to expand...
Click to collapse
Xoom mz608 is 3g media edition , I don't have it to test. Upload your build.prop and framework-res.apk for me to check and for you to test
wesamothman said:
Alright,
I did some modifications to your framework-res.apk;
Indeed, there was this config defined in your framework
"config_text_sms_receive" but there was no send config
What I did is that I added send configuration "config_text_sms_send" and complied it. Also, changed the MMS.apk to a generic one that works across devices. I decompiled the compiled APK and I can see it persists in bools.xml and in public.xml; therefore, the reference was created successfully.
From SmscSettings.apk that you sent, I can see the option that your device can set the SMS Center number. You may wanna try to check that and put the SMS center number the same as the one of your phone "of course from the same service provider". And then try. I hope this works for you know; I can't test it cuz I don't have MZ616 device.
Here is the link; download it and flash it. http://www.mediafire.com/download.php?2b317ejrp7my9ew
In case you need to rollback, couple of posts earlier I included the rollback to original framework.
Good luck and let me know how it goes.
NOTE: I also enabled SIP capabilities for you; so I think you will be able to use your device as a SIP hub and SIP phone over IMS (IP Multimedia Subsystem).
Click to expand...
Click to collapse
Hi, sorry for the late feedback. I checked your new framework and mms and the new mms shown up as an app and could be started. But there is no change with sending SMS and also old received SMS are not seen by the apps (mms and go sms). Only the sms popup app is showing an incoming sms just one time. If I try to send a sms with mms, I get the message that mms is not responding. The other messages or behavior has not changed to the previous test. Could it be that one app is blocking access to the sim card?
Regards Lothar
wesamothman said:
Xoom mz608 is 3g media edition , I don't have it to test. Upload your build.prop and framework-res.apk for me to check and for you to test
Click to expand...
Click to collapse
Hi, sorry to intrude, but I'm interested in these features. Here are the requested files.
Thanks
jyoshinari said:
Hi, sorry to intrude, but I'm interested in these features. Here are the requested files.
Thanks
Click to expand...
Click to collapse
Any news guys?

VoLTE - i9505 International for Jio - Easy way.

I am not a developer but a HW guy.
This applies only to i9505 international version with Qualcomm processor as tested.
Please note that whoever tries the following, upon failure and/or ending up with bricked phone(s), incurring any loss, implied or direct, resulting from the application of what is described in this post, including but not limited to time, warranty, update from Samsung including security updates, resources, financial or otherwise,etc., does not point a finger in my direction but, does so at his/her own risk.
(Hope I scared a few).
The unit that I used originally had XXUHPK2 - XST firmware.
Whatever given below are personally experienced after quite a bit of searching, testing and few near misses including SIM not being detected or infinite loops when searching for network to register due to my own experimentation with Modem and NON-HLOS files.
But I never once lost my IMEI as the method is fairly straightforward. Always God "ODIN" is there to the rescue.
This applies to those who do not want an "always on" Jio4GVoice app and prefer to stay with stock recovery. Of course custom recovery can always be installed.
I have used PI1_VOLTE_JIO FW available on this forum but had faced few issues related to calling out at times, more so when I travel long distance. If I stay put at certain places it always worked.
Now to the works:
1. Using ODIN install I9505XXUPOL1_I9505PHNPOL1_PHN FW. - Search to download FW.
Nordic version of FW with PI1 modem "may" be used but I found network search for registering yields less number of networks. I have not tried using the Nordic FW.
2. Root the device using CF-Auto-Root.
3. Search for "Volte fix.zip" and download. Easiest way to get links to download is YouTube. In the zip file I used all files have 07-11-2016 as creation date. I found VoLTEFiles zip too with the same dates but did not try it so far.
4. Watch the YouTube, say, at "watch?v=MlkaziK6AkY" or any other relevant VoLTE zip file installation video to get the gist of the method before attempting.
5. The zip contains an Apks folder and a Files folder. Extract APK, csc folder, CSCVersion.txt and SW_Confgiuration.xml to a known folder preferably in ext-sd if available.
6. Install root explorer. It is under extracted Apks folder. Allow for installation of app from unknown sources.
7. Open Root Explorer browse to /system directory. Rename existing csc folder, CscVersion.txt and SW_Configuration.xml with some leading characters as fall back. The csc folder and the files can optionally be deleted as well.
Root Explorer will require the patition to be mounted as RW saying it is Read Only. Say OK to proceed.
8. Copy and paste the above folder and files obtained from zip to /system.
9. Change permissions via Root Explorer as below:
Touch the folder or file under Root Explorer. Once selected touch 3 dots on top right and select permissions. Given numbers can be directly entered using Octal button.
csc folder - 755 octal
CscVersion.txt - 644 octal
SW_Configuration.xml - 644 octal
10. Exit Root Explorer and Reboot. And wait patiently for a while until the two way sign appears on status bar. It really takes a while.
Call Settings - "Outgoing voice call settings" automatically shows "Use VoLTE when available".
Factory reset does not restore VoLTE icon on status bar and calling is not possible as well. Wait for a while for the phone to complete all processes after setting up. Reboot to get VoLTE back.
It seems to take a while and the Sammy phone will show a report being sent when connected to WiFi... to inform you later when you select "Software Update" that the phone has modified in an un-authorized way, etc.
Calling and messaging works even with WiFi ON.
I have not provided any link as the credit should go where it belongs.
See screenshots in the attached thumbnails.
ODIN Version used 3.12.7
CF-Auto-Root available on this forum.
And most importantly thanks to the developer who created the VoLTE fix files. And a special thanks to @dhiru1602 with his PI1-VOLTE-JIO ROM as it was instrumental in making me search and test.
Does this work on other S4 not for JIO and on other networks?
treysis said:
Does this work on other S4 not for JIO and on other networks?
Click to expand...
Click to collapse
Sorry for the belated reply. I was using it on Jio only as no other nw providers were offering VoLTE at that time. Now the unit is with someone else in another country. I learnt VoLTE is available in that country and will request to get it checked. Will revert with results.
hey, no problem and thanks for the help! Have you heard back from your friend yet?
treysis said:
hey, no problem and thanks for the help! Have you heard back from your friend yet?
Click to expand...
Click to collapse
Yes and a No - On one network it does not show the icon. He is not sure if the ISP actually implemented VoLTE though announced last year. On the other he has not tested as yet. Says needs to get the 4G SIM. Will wait for some more time and revert again.
Ok. I know for sure that my network and my SIM support VoLTE, cause I am using it on another Samsung handset and it's working fine. But on the S4 no luck yet.
Btw. I just put a Malaysian SIM and this enabled VoWiFi in the settings. But couldn't try it as the card is not fully active anymore.

[VIDEO] How google blocks 5G for unlisted countries (explained)

I made a video explaining how google blocks 5G in the software by default for unlisted countries.
I also tried posting this on reddit at r/googlepixel but mods deleted it.
I think this information should be spread to the wider general public because it affects just about every one of us here, having to root our phones to enable 5G, when this should just be enabled out of the box with absolutely no tinkering required.
If a phone is advertised as "5G ready", we should expect to be able to connect to our carrier's 5G network out of the box, regardless of being in a "supported country" or not.
This video shows that carrier-google certification is not necessary to connect to your carrier's 5G network.
I wonder if it's possible to file a class action lawsuit because blocking 5G in the software clearly has to be some sort of "misleading" or "false advertising" in terms of the phone being "5G" ready.
@elong7681
In reply to your other question. (proton rom thread may not be the best thread to discuss this)
carrier_policy.xml file is located inside the carrier mbn file.
To extract the mbn file, you need:
Efs Tools https://github.com/JohnBel/EfsTools/releases
dotnet-core https://dotnet.microsoft.com/download/dotnet-core/3.1
dotnet https://dotnet.microsoft.com/download/dotnet/5.0
1. Install dotnet-core and dotnet
2. Copy mbn file into the efstools folder
3. Run in command prompt: EfsTools.exe extractMbn -i mcfg_sw.mbn -p mcfg
4. New folder (mcfg) will be created and mbn file will be extracted inside.
Carrier_policy.xml is inside the "policyman" folder.
This video will also explain how the mbn files are used to enable or disable 5G.
swangjang said:
@elong7681
In reply to your other question. (proton rom thread may not be the best thread to discuss this)
carrier_policy.xml file is located inside the carrier mbn file.
To extract the mbn file, you need:
Efs Tools https://github.com/JohnBel/EfsTools/releases/tag/0.13
dotnet-core https://dotnet.microsoft.com/download/dotnet-core/3.1
dotnet https://dotnet.microsoft.com/download/dotnet/5.0
1. Install dotnet-core and dotnet
2. Copy mbn file into the efstools folder
3. Run in command prompt: EfsTools.exe extractMbn -i mcfg_sw.mbn -p mcfg
4. New folder (mcfg) will be created and mbn file will be extracted inside.
Carrier_policy.xml is inside the "policyman" folder.
This video will also explain how the mbn files are used to enable or disable 5G.
Click to expand...
Click to collapse
Thanks, I agree making this thread was a good idea.
I managed to pull the modem.img from the device.
To find which partition has what installed:
su
ls -la /dev/block/bootdevice/by-name
To pull the modem partition:
su
dd if=dev/block/sda12 of=/sdcard/modem_a.img
dd if=dev/block/sda13 of=/sdcard/modem_b.img
Unfortunately, it's not organised in folders to something like mcfg_sw/generic/*
but instead, it's all labeled in numbers.
They also can't be extracted using the method in post #2.
5G now working on my P5 with Free Mobile in France. Thanks for this post
swangjang said:
I managed to pull the modem.img from the device.
To find which partition has what installed:
su
ls -la /dev/block/bootdevice/by-name
To pull the modem partition:
su
dd if=dev/block/sda12 of=/sdcard/modem_a.img
dd if=dev/block/sda13 of=/sdcard/modem_b.img
Unfortunately, it's not organised in folders to something like mcfg_sw/generic/*
but instead, it's all labeled in numbers.
They also can't be extracted using the method in post #2.
Click to expand...
Click to collapse
@swangjang I have a quick question for you, before I rooted and started flashing roms and kernels but after I unlocked my bootloader I had the ability to record phones calls through the Google phone app but I only used it once so I stopped paying attention to the phone app while I was using it but I just recently noticed that I can no longer record phone calls, the record button is no longer present when I'm using the phone. I live in the US and that option is available for us but I no longer have the option, is there any chance you could help me get that option back ?
elong7681 said:
@swangjang I have a quick question for you, before I rooted and started flashing roms and kernels but after I unlocked my bootloader I had the ability to record phones calls through the Google phone app but I only used it once so I stopped paying attention to the phone app while I was using it but I just recently noticed that I can no longer record phone calls, the record button is no longer present when I'm using the phone. I live in the US and that option is available for us but I no longer have the option, is there any chance you could help me get that option back ?
Click to expand...
Click to collapse
I don't know much about it either lol. As far as I know, phone call recording was supposed to be removed from Google Phone app due to recording laws. Maybe you somehow had the beta version of the app and it got updated?
I use skvalex's recording app. You have to pay for premium after a free trial and it's quite costly for an app but I don't regret paying for it. It records both sides internally so bluetooth calls are also recorded both sides.
Something that might be worth considering if you can't find a way to get it back.
swangjang said:
I don't know much about it either lol. As far as I know, phone call recording was supposed to be removed from Google Phone app due to recording laws. Maybe you somehow had the beta version of the app and it got updated?
I use skvalex's recording app. You have to pay for premium after a free trial and it's quite costly for an app but I don't regret paying for it. It records both sides internally so bluetooth calls are also recorded both sides.
Something that might be worth considering if you can't find a way to get it back.
Click to expand...
Click to collapse
Thanks for your quick reply and the app reference
swangjang said:
@elong7681
In reply to your other question. (proton rom thread may not be the best thread to discuss this)
carrier_policy.xml file is located inside the carrier mbn file.
To extract the mbn file, you need:
Efs Tools https://github.com/JohnBel/EfsTools/releases/tag/0.13
dotnet-core https://dotnet.microsoft.com/download/dotnet-core/3.1
dotnet https://dotnet.microsoft.com/download/dotnet/5.0
1. Install dotnet-core and dotnet
2. Copy mbn file into the efstools folder
3. Run in command prompt: EfsTools.exe extractMbn -i mcfg_sw.mbn -p mcfg
4. New folder (mcfg) will be created and mbn file will be extracted inside.
Carrier_policy.xml is inside the "policyman" folder.
This video will also explain how the mbn files are used to enable or disable 5G.
Click to expand...
Click to collapse
Hi, this is helpful, but it would be great if you could give further detailed instructions as to how to enable 5G for unsupported carriers. In other words, what needs to be done after step #4 above (editing and copying of files)?
Also, would this process work is a dual sim configuration?
Thanks for your expose!
nsiti said:
Hi, this is helpful, but it would be great if you could give further detailed instructions as to how to enable 5G for unsupported carriers. In other words, what needs to be done after step #4 above (editing and copying of files)?
Also, would this process work is a dual sim configuration?
Thanks for your expose!
Click to expand...
Click to collapse
There are tutorials in other threads in this forum on how to do that. But if written guides are difficult to follow (not judging, the guides assume you have some PC knowledge and it took me a while to understand them too), I can make a video showing step by step process this weekend.
I'm not sure about dual sim 5G. 5G DSDS (Dual Sim Dual Standby) was only just implemented in March update and I don't have a 5G esim to test it.
swangjang said:
There are tutorials in other threads in this forum on how to do that. But if written guides are difficult to follow (not judging, the guides assume you have some PC knowledge and it took me a while to understand them too), I can make a video showing step by step process this weekend.
I'm not sure about dual sim 5G. 5G DSDS (Dual Sim Dual Standby) was only just implemented in March update and I don't have a 5G esim to test it.
Click to expand...
Click to collapse
@swangjang that would be awesome
elong7681 said:
@swangjang that would be awesome
Click to expand...
Click to collapse
Seems it's not necessary any more.
Finally , One Module-unlock 5G-Volte-VoWIFI
Hello,, After a long term of tries and workarounds. Finally found some module by ender-zhao :love::love::love::love::love::love: Thanks for him so much. Simply one module to enable 5G and Volte ,vowifi... install it from magisk , restart and...
forum.xda-developers.com
I haven't tried it yet but it seems promising.
swangjang said:
Seems it's not necessary any more.
Finally , One Module-unlock 5G-Volte-VoWIFI
Hello,, After a long term of tries and workarounds. Finally found some module by ender-zhao :love::love::love::love::love::love: Thanks for him so much. Simply one module to enable 5G and Volte ,vowifi... install it from magisk , restart and...
forum.xda-developers.com
I haven't tried it yet but it seems promising.
Click to expand...
Click to collapse
@swangjang if it isn't too much trouble and you have the time I personally think it would still benefit the community if you did that video tutorial because being able to do it manually would teach people how to do it versus using a simple magisk module either way thank you for your help and work thus far.
@swangjang is it possible to flash the Google and Qualcomm binaries and if so can you point me in the right direction?
elong7681 said:
@swangjang is it possible to flash the Google and Qualcomm binaries and if so can you point me in the right direction?
Click to expand...
Click to collapse
Sorry, I'm not sure what you mean by that...
swangjang said:
Sorry, I'm not sure what you mean by that...
Click to expand...
Click to collapse
They are located here https://developers.google.com/android/drivers Maybe this will help explain my question
elong7681 said:
They are located here https://developers.google.com/android/drivers Maybe this will help explain my question
Click to expand...
Click to collapse
Oh. I have no idea lol.
swangjang said:
Oh. I have no idea lol.
Click to expand...
Click to collapse
Ok I appreciate your response, besides the XDA Developers website is there any other websites like this one that you can recommend ?
elong7681 said:
Ok I appreciate your response, besides the XDA Developers website is there any other websites like this one that you can recommend ?
Click to expand...
Click to collapse
To my knowledge, I don't there are any other alternatives that's English based.
I still dont understand, do I need to root my device to do this?

S8+ (G955F) Native Call Recording Code CSCFeature.XML no longer working - Help

Hi guys
Got the Australian variant which is the G955F. Ended up doing a complete reflash of stock ROM due to SMS messages not coming through which after clearing the data and cache from seemed to destroy it. But thats another story.
I have the Vodafone version and downloaded from SAMMOBILE the latest which came with 5 files. Though I was a bit confused because there were 2 for CSC. Home & just CSC. I flashed it with Home CSC.
Have managed to Re root the phone using Magisk which has all worked out fine according to root check.
I cannot do what I was able to do before though.
That is to add some text to the end line of CSCFeature.XML to enable native call recording.
I even backed up my old CSCFeature.xml and copied and replaced it in the same dir but I am not seeing the 'Call Record' feature during phone calls like I could before.
Any ideas why?
Could this be because I flashed Home CSC instead of just the CSC file? If that is the reason then is it possible to flash just the CSC file on Odin without having to do any data wipes or formatting etc?
Update: Went through the XML file to find a load of text had made its way above the whole set of coding.. Since removing it it is now fully functional.

Question features missing

how do i get the samsung screen recorder and secure folder on my a226b and or any other samsung ad i dont have them for some reason and i would like to know if theres any universal twrp or odin thing to flash that would gove them back or maybe secret setting to enable or apk to install
Win_7 said:
how do i get the samsung screen recorder and secure folder on my a226b and or any other samsung ad i dont have them for some reason and i would like to know if theres any universal twrp or odin thing to flash that would gove them back or maybe secret setting to enable or apk to install
Click to expand...
Click to collapse
There Isn't a screen recorder or secure folder on the SM-A226B you can use calculator+ and flash a android 13 GSI to use the screen recorder.
You can enable screenrecorder by modifiying some lines in /system/etc/floating_feature.xml
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
<SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>-pip</SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>
Without spaces. If there is already the value simply change to this. I'm working on a way to enable secure folder in my free time. First tests were successful however there are still some problems. I'm extracting files from A13 5G (SM-A136B) because it has the same chipset as A22 5G and has secure folder
fede2782 said:
You can enable screenrecorder by modifiying some lines in /system/etc/floating_feature.xml
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
<SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>-pip</SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>
Without spaces. If there is already the value simply change to this. I'm working on a way to enable secure folder in my free time. First tests were successful however there are still some problems. I'm extracting files from A13 5G (SM-A136B) because it has the same chipset as A22 5G and has secure folder
Click to expand...
Click to collapse
thanks!!!! will this work on any other phone other than a226b?
and do you know of any file manager app that can actually edit system files (i have a good one called filemanager+ but it can only read even if i do mount -o remount,rw /
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (https://www.apkmirror.com/apk/samsu.../samsung-capture-5-4-22-android-apk-download/) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
fede2782 said:
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (Here's where you can download latest apk) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
Click to expand...
Click to collapse
eh thats ok i used adb and accepted root on device
my phone didnt have the file is that ok if i just create it?
also you made a mistake on the url can you send a working one?
fede2782 said:
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (Here's where you can download latest apk) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
Click to expand...
Click to collapse
um how can i fix "system partition doesnt have enough free space" when trying to convert newer samsung capture to system app
You don't need to convert. Just update with apk when phone on. Like every app. I made a mistake in the link. I fixed it. The file should exist on every Samsung one ui device.
fede2782 said:
You don't need to convert. Just update with apk when phone on. Like every app. I made a mistake in the link. I fixed it. The file should exist on every Samsung one ui device.
Click to expand...
Click to collapse
oh bruh i deleted system app and reinstalled
An apk of Samsung capture must remain in the /system partition in order to get priv-app permissions
I recommend you to reinstall original firmware (One UI 5.1 if it is available in your region) then modify floating_feature.xml.
This file is placed in every samsung device in /system/etc/floating_feature.xml
You do not have to create nothing. Just modify it add that lines. In my firmware (official one UI 5.1) the second line is already placed in the file. So I simply added:
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
in the middle of the file
fede2782 said:
An apk of Samsung capture must remain in the /system partition in order to get priv-app permissions
I recommend you to reinstall original firmware (One UI 5.1 if it is available in your region) then modify floating_feature.xml.
This file is placed in every samsung device in /system/etc/floating_feature.xml
You do not have to create nothing. Just modify it add that lines. In my firmware (official one UI 5.1) the second line is already placed in the file. So I simply added:
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
in the middle of the file
Click to expand...
Click to collapse
i still didnt have the file i made it and updated capture but didnt get screen recorder even after reboot :/ am on android 11 and im not updating especially as theres bootloader update
For me it is working. The file floating_feature.xml needs to exist. if it doesn't exist this means your firmware version is old and it doesn't have modern one UI. I don't know how I can help you more
fede2782 said:
For me it is working. The file floating_feature.xml needs to exist. if it doesn't exist this means your firmware version is old and it doesn't have modern one UI. I don't know how I can help you more
Click to expand...
Click to collapse
i have a70 with screenrecorder its on android 10
my a22 is on oneui 3.1
I don't know.
fede2782 said:
I don't know.
Click to expand...
Click to collapse
alright then sorry for bothgering you
Win_7 said:
alright then sorry for bothgering you
Click to expand...
Click to collapse
Don't worry
Image clipper wip being prepared! Object Eraser! deCorizer - Add missing One UI features to A22 5G
You can flash this Magisk module AT YOUR OWN RISK. I AM NOT RESPONSIBLE for lost warranty, bootloops, lost data or any other damage to your device. THE SOFTWARE IS PROVIDED “AS IS” This module tries to add as many One UI features as possible to...
forum.xda-developers.com
fede2782 said:
Image clipper wip being prepared! Object Eraser! deCorizer - Add missing One UI features to A22 5G
You can flash this Magisk module AT YOUR OWN RISK. I AM NOT RESPONSIBLE for lost warranty, bootloops, lost data or any other damage to your device. THE SOFTWARE IS PROVIDED “AS IS” This module tries to add as many One UI features as possible to...
forum.xda-developers.com
Click to expand...
Click to collapse
it didnt work
it just said system is root and a couple other things then i rebooted nthing
Win_7 said:
it didnt work
it just said system is root and a couple other things then i rebooted nthing
Click to expand...
Click to collapse
At the moment is only for DWC1 OXM
I'll try to download your file from AVA1 as soon as I can and I'll patch it
fede2782 said:
At the moment is only for DWC1 OXM
I'll try to download your file from AVA1 as soon as I can and I'll patch it
Click to expand...
Click to collapse
i have AVA6 not 1

Categories

Resources