Develop Bugs

Samsung Smart Call

I've got unlocked Note 10+ and I flashed the U firmware because of video calling that's missing on U1. Now I found that on T Mobile version there is no Smart Call and it is replaced by T Mobile NameID, which I consider inferior and I'd have to pay for full functionality.
Anybody knows if there is any way how to get the stock Samsung dialer with Smart Call back? I'd hate to flash the U1 ROM and go through the restore process again. Even with Samsung cloud, Google and SD backups it took me almost half day to get it set as I had it before.

Stank0 said:
I've got unlocked Note 10+ and I flashed the U firmware because of video calling that's missing on U1. Now I found that on T Mobile version there is no Smart Call and it is replaced by T Mobile NameID, which I consider inferior and I'd have to pay for full functionality.
Anybody knows if there is any way how to get the stock Samsung dialer with Smart Call back? I'd hate to flash the U1 ROM and go through the restore process again. Even with Samsung cloud, Google and SD backups it took me almost half day to get it set as I had it before.
Click to expand...
Click to collapse
My past experience with Samsung Smart Call, was that i found that even though, its baked into Samsung Firmware, it is Service Provider depended. to "activate /work".
I might be wrong, but i personally believe so, based on my experience.
Just to recap, my experiences with my old Note 8 and my Note 9 (both devices not rooted)
I also flashed Stock Samsung firmware .. different CSC onto these devices.
I found on both occasions i lost the function of th Smart Call.
( Hiya services), also Volte function etc etc.
I could see the Smart Call settings in firmware, but it was greyed out.
Could not enable it at all.
When i flashed my old Samsung Firmware (Service Provider CSC) Smart Call (Hiya services), was enabled again and working.
I'm sure in your case, you'll will find it's Service Provider depended.
Good luck.

willcor said:
My past experience with Samsung Smart Call, was that i found that even though, its baked into Samsung Firmware, it is Service Provider depended. to "activate /work".
I might be wrong, but i personally believe so, based on my experience.
I'm sure in your case, you'll will find it's Service Provider depended.
Good luck.
Click to expand...
Click to collapse
The thing is, after I purchased and set up the phone on stock Samsung firmware, VoLTE and Smart Call worked perfectly fine. But stupid me wanted to try the video calling. I found that the video calling is not different than Google Duo and I will NEVER use RTT texts. I see no real advantage from using T Mo firmware in comparison with stock Samsung (provisioned for T Mo of course)
Actually quite the opposite. For me, the signal strength and battery life is practically the same on both and again, FOR ME Smart Call is much more useful than video call and RTT.
If anyone knows any benefits from keeping T Mo firmware over stock, please enlighten me. I really don't want to go through the flashing the whole thing and restoring dance again, but I'm afraid I will have to.

Stank0 said:
The thing is, after I purchased and set up the phone on stock Samsung firmware, VoLTE and Smart Call worked perfectly fine. But stupid me wanted to try the video calling. I found that the video calling is not different than Google Duo and I will NEVER use RTT texts. I see no real advantage from using T Mo firmware in comparison with stock Samsung (provisioned for T Mo of course)
Actually quite the opposite. For me, the signal strength and battery life is practically the same on both and again, FOR ME Smart Call is much more useful than video call and RTT.
If anyone knows any benefits from keeping T Mo firmware over stock, please enlighten me. I really don't want to go through the flashing the whole thing and restoring dance again, but I'm afraid I will have to.
Click to expand...
Click to collapse
Ha, your post reminds me,
that when i flashed
my branded Samsung Firmware ( Voda CSC) with the Samsung unbranded Firmware,
The reason, was also to get video calling working.
As my branded device did not have video calling option on dialer.
I could only activate video, if someone else, video called me... only then the video option, would appear.!
I then afterwards, realized that i lost my Smart Call functions. and flashed back to the branded software.
This was on my Note 9.
So i had no video call option on dialer ,but Smart Call.
Now...
again, with my branded( Voda CSC) Note 10 +,
i see that my device has video calling on dial pad.....!
So, the Service Providers, chop and changed.
A year back, they disabled video calling option, from dial pad.
Now video calling is back on the dial pad plus Smart Calls is working fine.
Good luck

So.... I bit the bullet and flashed back the U1 firmware. The only thing I lost is the video calling. I still have RTT button on my dialer. Whether it works or not I haven't tried yet. I know it wasn't there on the original dialer when I purchased the phone. Maybe because I didn't flash USERDATA? Who knows.
I'm happy I've got Smart Call back.

CSC N975U
Good afternoon, I have the n975u model, my question is what firmware should I install, to get the smart call and video calls by duo?. Or is csc the one that has these functions active?
Thanks!!
excuse my english, google translator.

I have a Verizon Note10+ running Android 11 (3.1) I paid my cell off 4 mo ago. Verizon confirmed for me that my cell is carrier unlocked. I've tried everything to get the Smart Call app on my phone to work. The only thing I haven't tried is rooting it cause I don't know how. I have 3 versions of the apk and can't make them work. Can anyone help?

Generally, does international firmware version have an approach enable most features?

Hi All,
My decision to stay QSB 30.121-12 or TROIKA_RETAIL_10_QSBS30.62-17-2 will depend if permission is allowed for some function in the particular channel firmware.
“In some countries in some phones, some feature as call recording of Android 10 is disabled…” I’m aware features may be blocked also from a service provider or disable from firmware point of view.
In an international firmware compared to a country based (example Canada), does features are more likely enable or disable?
Generally, does international firmware version have an approach enable most features and let’s the country’s service provider to block them ?
Reference:
https://forum.xda-developers.com/on...oid-10-rom-t4039817/post82290937#post82290937
Reference:
https://www.boldbeast.com/forum/topic1877-android-10-call-recording.html
Root needed
In some countries in some phones, the call recording feature of Android 10 is disabled, and Boldbeast Recorder can't bypass the limits to enable the feature again. Your own voice is good but the caller's voice is very weak in recordings. In this case all recorders don't work either for sure, you can test and confirm the fact yourself. To fix the problem root is the ONLY way to go. If you don't root the phone there will be no solution in the whole market without doubt unfortunately. If you root the phone Boldbeast Recorder can fix it perfectly.
Thanks

ATT Port to Verizon S20 G981V Questions

I switched jobs and my work let me keep the S20 5G G981V that was assigned to me. I got it SIM unlocked and ported over to my family's Verizon account. At my new job, the entire warehouse is a cell deadzone but wifi is amazing. I have noticed that wifi calling is not even available for me to use. From what I gather, that's because I'm using the ATT image on the Verizon network. Is flashing the Verizon firmware through ODIN my best bet to getting wifi calling back, or should I go the root and custom ROM route? I've been rooting phones for over 10 years so I'm not new to the process. I went to the Verizon store and they told me I was ****e out of luck. Thanks!!!

pogibry said:
I switched jobs and my work let me keep the S20 5G G981V that was assigned to me. I got it SIM unlocked and ported over to my family's Verizon account. At my new job, the entire warehouse is a cell deadzone but wifi is amazing. I have noticed that wifi calling is not even available for me to use. From what I gather, that's because I'm using the ATT image on the Verizon network. Is flashing the Verizon firmware through ODIN my best bet to getting wifi calling back, or should I go the root and custom ROM route? I've been rooting phones for over 10 years so I'm not new to the process. I went to the Verizon store and they told me I was ****e out of luck. Thanks!!!
Click to expand...
Click to collapse
I have a similar situation: I'm trying to get VZW Wi-Fi calling to work on an unlocked international S20+ (SM-G986B). Verizon told me they allow WI-Fi calling on BYOD equipment and that my account is properly provisioned. However:
There is no evidence of any Wi-Fi calling settings anywhere in the phone's UI.
System logs (e.g., logcat | grep -e UNWFC -e EPDG) show lots of info about not being registered for Wi-Fi calling.
IMS Settings show that VoLTE is provisioned, but not HD Voice. VoLTE clearly works.
Samsung's Wi-Fi calling stack is supposed to be pretty universal these days, and to a large extent, it delivers: when I put in a T-Mobile SIM, Wi-Fi calling comes up right away. So it seems that the Wi-Fi calling stack on my phone isn't completely out to lunch. But Verizon's Wi-Fi calling implementation appears to not be so cut and dry.
Last night I popped open a SM-G986U (supposedly universal carrier-unlocked US Snapdragon S20+) firmware image in an attempt to understand what Verizon is doing for their Wi-Fi calling, and it appears I opened a can of worms.. I found a whole lot of Verizon-specific content in there that I don't have.
Spoiler: system.img find output
Code:
{tuxomatic /mnt/G986USQS1BTJ2_OYN1BTJ2/AP} # find system -type f | grep -iP 'vz|verizon'
system/etc/permissions/com.verizon.os.xml
system/etc/permissions/com.verizon.phone.xml
system/etc/permissions/com.verizon.provider.xml
system/etc/permissions/privapp-permissions-com.customermobile.preload.vzw.xml
system/etc/permissions/privapp-permissions-com.securityandprivacy.android.verizon.vms.xml
system/etc/permissions/privapp-permissions-com.verizon.llkagent.xml
system/etc/permissions/privapp-permissions-com.verizon.loginengine.unbranded.xml
system/etc/permissions/privapp-permissions-com.vzw.apnservice.xml
system/etc/permissions/privapp-permissions-com.vzw.ecid.xml
system/etc/permissions/verizon_net_sip_library.xml
system/etc/permissions/vzwapnlib.xml
system/etc/init/vzsysprop.rc
system/carrier/VZW/permissions/ecid-hiddenapi-package-whitelist.xml
system/carrier/VZW/permissions/snp-hiddenapi-package-whitelist.xml
system/carrier/VZW/permissions/mvm-hiddenapi-package-whitelist.xml
system/carrier/VZW/permissions/privapp-permissions-com.verizon.obdm.xml
system/carrier/VZW/permissions/privapp-permissions-com.verizon.mips.services.xml
system/carrier/VZW/permissions/vzcloud-hiddenapi-package-whitelist.xml
system/carrier/VZW/permissions/privapp-permissions-com.verizon.onetalk.dialer.xml
system/carrier/VZW/permissions/privapp-permissions-com.samsung.advancedcalling.xml
system/carrier/VZW/permissions/whitelist_com.LogiaGroup.LogiaDeck.xml
system/carrier/VZW/permissions/vla-hiddenapi-package-whitelist.xml
system/carrier/VZW/permissions/privapp-permissions-com.vzw.hss.myverizon.xml
system/carrier/VZW/permissions/mvs-hiddenapi-package-whitelist.xml
system/carrier/VZW/permissions/privapp-permissions-com.telecomsys.directedsms.android.SCG.xml
system/carrier/VZW/dummy.txt
system/carrier/VZW/priv-app/HuxExtension/HuxExtension.apk
system/carrier/VZW/priv-app/com.customermobile.preload.vzw/com.customermobile.preload.vzw.apk
system/carrier/VZW/priv-app/MyVerizonService/MyVerizonService.apk
system/carrier/VZW/priv-app/IgniteVerizon/IgniteVerizon.apk
system/carrier/VZW/priv-app/MyVerizonMobile/MyVerizonMobile.apk
system/carrier/VZW/priv-app/LocationAgent/LocationAgent.apk
system/carrier/VZW/priv-app/AdvancedCalling/AdvancedCalling.apk
system/carrier/VZW/priv-app/SNP_stub/SNP_stub.apk
system/carrier/VZW/priv-app/OneTalkDialer/OneTalkDialer.apk
system/carrier/VZW/priv-app/VzwImsApiService/VzwImsApiService.apk
system/carrier/VZW/priv-app/canid_stub/canid_stub.apk
system/carrier/VZW/priv-app/LLKAgent/LLKAgent.apk
system/bin/vzsysprop
system/priv-app/VZWAPNService_sku/VZWAPNService_sku.apk
system/priv-app/VzCloud/VzCloud.apk
system/framework/VZWAPNLib_VZW.apk
system/framework/com.verizon.os.jar
system/framework/com.verizon.phone.jar
system/framework/com.verizon.provider.jar
system/framework/oat/arm/com.verizon.os.odex
system/framework/oat/arm/com.verizon.os.vdex
system/framework/oat/arm/com.verizon.phone.odex
system/framework/oat/arm/com.verizon.phone.vdex
system/framework/oat/arm/verizon.net.sip.odex
system/framework/oat/arm/verizon.net.sip.vdex
system/framework/oat/arm64/com.verizon.os.odex
system/framework/oat/arm64/com.verizon.os.vdex
system/framework/oat/arm64/com.verizon.phone.odex
system/framework/oat/arm64/com.verizon.phone.vdex
system/framework/oat/arm64/verizon.net.sip.odex
system/framework/oat/arm64/verizon.net.sip.vdex
system/framework/verizon.net.sip.jar
Spoiler: optics.img find output
Code:
{tuxomatic /mnt/G986USQS1BTJ2_OYN1BTJ2/CSC } # find optics/configs/carriers/single/VZW -type f
optics/configs/carriers/single/VZW/conf/cscfeature.xml
optics/configs/carriers/single/VZW/conf/cscfeature_network.xml
optics/configs/carriers/single/VZW/conf/customer.xml
optics/configs/carriers/single/VZW/conf/omc.info
Spoiler: prism.img find output
Code:
{tuxomatic /mnt/G986USQS1BTJ2_OYN1BTJ2/CSC # find prism/etc/carriers/single/VZW -type f
etc/carriers/single/VZW/userdatacfg.xml
etc/carriers/single/VZW/enforcedeletepackage.txt
etc/carriers/single/VZW/oathpartnerid.conf
etc/carriers/single/VZW/contents.db
etc/carriers/single/VZW/sales_code.dat
etc/carriers/single/VZW/VZW_keystrings.dat
etc/carriers/single/VZW/csc_ringtones_list.txt
etc/carriers/single/VZW/imsupdate.json
etc/carriers/single/VZW/default_workspace_easy.xml
etc/carriers/single/VZW/default_apps.xml
etc/carriers/single/VZW/default_apps_upsm.xml
etc/carriers/single/VZW/enforceskippingpackages.txt
etc/carriers/single/VZW/default_workspace.xml
etc/carriers/single/VZW/unique_text.xml
etc/carriers/single/VZW/hidden_apks_list.txt
etc/carriers/single/VZW/default_application_order.xml
Just based on their names, a quick glance at the packages baked into system.img suggests the following are reasonably likely to be associated with Wi-Fi calling:
VZWAPNLib_VZW.apk
VZWAPNService_sku.ap
VzwImsApiService.apk
AdvancedCalling.apk
The big question is AdvancedCalling.apk?! Is this some sort of proprietary implementation of Wi-Fi calling and VoLTE?! Is it possible that Wi-Fi calling on Verizon isn't possible using the Samsung Unified Wi-Fi Calling app? And is there special APN config that needs to get pushed to my phone to enable EPDG connectivity required for Wi-Fi calling?
There's a whole lot in the CSC images (optics.img and prism.img) too. Of particular note, prism.img's imsupdate.json seems to define some sort of E911 IMS configuration. I wouldn't be suprised if that was a prerequiste for WI-Fi calling.
I also find interesting the declaration of packages allowed during power saving and emergency modes (suggesting these packages are necessary for core functionality like calling):
Spoiler: packages allowed during power saving mode
Code:
{tuxomatic /mnt/G986USQS1BTJ2_OYN1BTJ2/CSC } # grep -Po '<.*?PowerSaving.*>\K.*?(?=<.*?>)' optics/configs/carriers/single/VZW/conf/cscfeature.xml.out | tr ',' '\n'
com.sec.android.app.cmas
com.sec.imsservice
com.samsung.sdm
com.samsung.syncmlservice
com.samsung.syncmlphonedataservice
com.samsung.sdm.sdmviewer
com.vcast.mediamanager
com.vzw.apnservice
com.verizon.vzwavs
com.motricity.verizon.ssodownloadable
com.vzw.hss.myverizon
com.verizon.mips.services
com.cequint.ecid
com.samsung.vvm
com.LogiaGroup.LogiaDeck
com.vzw.hss.myverizontabletlte
com.vzw.ecid
com.telecomsys.directedsms.android.SCG
com.asurion.android.verizon.vms
com.samsung.unifiedsettingsservice
com.samsung.unifiedtp
com.verizon.messaging.vzmsgs
com.sec.android.app.setupwizard
com.samsung.advancedcalling
com.securityandprivacy.android.verizon.vms
com.samsung.usbyod
com.verizon.onetalk.dialer
Spoiler: packages allowed during emergency mode
Code:
{tuxomatic /mnt/G986USQS1BTJ2_OYN1BTJ2/CSC } # grep -Po '<.*?EmergencyMode.*>\K.*?(?=<.*?>)' optics/configs/carriers/single/VZW/conf/cscfeature.xml.out | tr ',' '\n'
com.sec.android.app.cmas
com.samsung.sdm
com.samsung.syncmlservice
com.ipsec.service
com.sec.android.providers.iwlansettings
com.sec.android.providers.mapcon
com.sec.providers.assisteddialing
com.sec.vowifispg
com.vzw.apnservice
com.motricity.verizon.ssodownloadable
com.vzw.hss.myverizon
com.verizon.mips.services
com.sec.unifiedwfc
com.samsung.vzwapiservice
com.samsung.advancedcalling
Interestingly, I see references to the packages I called out above. The also are likely involved too:
com.ipsec.service
com.sec.vowifispg
Even the Samsung Unified WiFI calling app made the list.
Ideally, we need some input here from someone that has VZW Wi-Fi calling up and running on a rooted device (and who is willing to do a bit of experimentation!) that can help us understand what components are involved/required. I don't know if there is anything to block you from installing the universal or VZW-specific firmware on your device, though based on what I remember from past reading on the topic it seems likely to be a large step in the right direction; please confirm for yourslef. I'm in a bit tougher spot than you because flashing the VZW firmware simply isn't an option on my Exynos device. I also don't want any unneeded extra VZW bloat on my system, but based on what I've seen it looks like I'll have to merge at least part of the VZW CSC into my ROM image.
Speaking of rooting and custom ROMs, have you managed to get the bootloader unlocked? As I understand, this is a nontrivial effort for US-based Snapdragon models and currently only available as a commercial unlocking service. The feedback seems pretty good but it appears that the service is limited to a handful of models running particular bootloader revisions.

Wow that's a lot of info! Thank you for that I tried installing the U firmware but it kept failing in Odin; I'm going to try the V tonight and see if it will work.
For unlocking the bootloader, I haven't done that yet. If I do, I will go all the way and load a custom ROM; I'm trying to avoid that for now UNLESS we know that wifi calling works on those custom ROMs, like Lineage or AOSP, etc...

pogibry said:
Wow that's a lot of info! Thank you for that I tried installing the U firmware but it kept failing in Odin; I'm going to try the V tonight and see if it will work.
For unlocking the bootloader, I haven't done that yet. If I do, I will go all the way and load a custom ROM; I'm trying to avoid that for now UNLESS we know that wifi calling works on those custom ROMs, like Lineage or AOSP, etc...
Click to expand...
Click to collapse
I guess it's not surprising they block installation of the universal firmware on a carrier locked model. Though that being the case, flashing Verizon firmware on an AT&T branded phone doesn't sound much more promising. How did that go?
My expectation is that going towards the likes of Lineage or even AOSP are going to take you further from a working Wi-Fi calling setup on a network with a non-standard implementation like Verizon.
BTW, do you by chance know what package is used to make the ipsec connection to the EPDG? I'm getting the impression that com.ipsec.service is an obsolete component that no longer exists on our phones. Interestingly though, my phone has /system/bin/charon and a handful of supporting libraries; these are components of the excellent, industrial-strength package strongSwan and could be responsible for that connection, though if that's the case, I still don't understand how it gets configured.

I wasn't able to get the link for the other firmware to work last night; I'm going to try again today.
For the EPDG, that part is over my head. I like rooting phones but I've never developed and made my own ROM's before.

Just got it downloaded, tried through ODIN and it failed. Is it because my bootloader isn't locked? I've never used ODIN with a phone that wasn't already unlocked.

pogibry said:
I wasn't able to get the link for the other firmware to work last night; I'm going to try again today.
For the EPDG, that part is over my head. I like rooting phones but I've never developed and made my own ROM's before.
Click to expand...
Click to collapse
In LTE, voice communication is carried over IP using trusted transport formed over the carrier's LTE network. Wi-Fi calling uses an analogous scheme, but since you are using a direct internet connection rather than the carrier's own trusted network connection, an IPsec VPN tunnel is instead used to create the trusted transport. The ePDG (evolved packet data gateway) is the device that terminates that VPN connection on the carrier end, and acts as the entry point into the carrier network for Wi-Fi calling; here is a nice little primer on ePDGs and IPsec. If your phone is unable to establish the requisite VPN tunnel, for example because the VPN software is not installed on your phone, there is precisely zero chance of Wi-Fi calling working. That's why I'm so interested in understanding what package is used to form the VPN connection. It's not clear to me what all the strongSwan instance I found in the ROM image is used for: it could be used for one or more of (a) the built in VPN client available on the Connections page, (b) the KNOX VPN client, or (c) Wi-Fi calling.
This is my first attempt at making a ROM. The quality and selection of custom ROMs seems to have been steadily decreasing in recent years, and I've never been able to find exactly what I was looking for out of the box anyway. Moreover, most ROM developers aggressively upgrade the base image of their ROMs which is exactly the opposite of the approach I'm looking for: I'd much rather stay on Android 10 for the foreseeable future rather than deal with 11 or (very soon) 12 and deal with compatibility issues with Magisk and all my favorite modules.
Overall, it's been a painful experience. Between the low quality of the tools and Samsung's countless security measures, it has resulted in a lot of hair pulling; I even ended up rolling my own kitchen. And now there's this Wi-Fi calling problem. I see plenty of posts complaining about difficulties with the feature on Verizon, but no one explaining how they solved it.
pogibry said:
Just got it downloaded, tried through ODIN and it failed. Is it because my bootloader isn't locked? I've never used ODIN with a phone that wasn't already unlocked.
Click to expand...
Click to collapse
I have pretty much no experience with the locked bootloader phones, but it sure wouldn't surprise me if carrier issued devices are keyed in such a way so that they won't accept the universal firmware or firmware of another carrier.

Bumping this thread. Verizon can't flash their software for me. They referred me to Geek Squad and they said they can't. From what I've read online about ODIN, it can work, but you legit need to crack the combination of things to get it to work. Since my bootloader is locked, I'm pretty sure I need the patched version of ODIN (?). I tried the bootloader version that matches mine but with the Verizon firmware and it fails, giving an error message of a modem mismatch. I grabbed the CP file from the ATT version and used that with instead of the Verizon CP file and this time I got a re-partition error message, which I don't get because I don't have the "ReParition" box selected within ODIN. There has got to be a way to get the Verizon firmware on this phone without having to unlock my bootloader (I did try and apparently my phone isn't able to be unlocked yet).

Did you ever get Wi-Fi calling working or at least get your bootloader unlocked? I finally got Wi-Fi calling working on my unlocked SM-G986B, and if you're able to bootloader unlock/root, I'd imagine you could do something similar.

Question Will this work on the zfold3?

Enable native call recording on SAMSUNG Galaxy S22 by changing the CSC region using SamKEY without rooting the phone
Enable native call recording on SAMSUNG Galaxy S22 by changing the CSC region using SamKEY without rooting the phone
www.artushfoto.eu

Yes, along as the region you change the CSC too, supports call recording, should work like normal

boomdox said:
Yes, along as the region you change the CSC too, supports call recording, should work like normal
Click to expand...
Click to collapse
Is there any downsides to this besides losing some Samsung apps?

You shouldn't loose anything as far as I'm aware, it's baked into the firmware, but the CSC either allows it or doesn't based on local laws, so you shouldnt loose any apps, unless for whatever reason they don't have them in those regions. Just research which firmware or region has the software that closest matches your needs

Question Manually edit CSC of S22/E (for verizon USA)

Mostly for built in call recording.
I had a S22/U1, I like the formfactor but it has no recording, so then I got a S22/E (snapdragon, india) version which works in the USA on verizon but sometimes signal just drops, and sometimes texts don't go through among other issues (recording is flawless).
I was looking into it and apparently the 'best' solution for S22 with recording (that works in USA) is to somehow get a rooted S22/U1 (USA version) and with root access you can manually edit the CSC file to turn on recording. But the challenge is getting a rooted U1, which can only be done with a paid service like sam PWND (as far as I know) and they are on pause now anyways....
So then I was thinking if all it takes is editing CSC then can I instead somehow load some files to my S22/E and make it have access to /U1 features (so calls don't drop etc.), and then take advantage of the root (which /E has with unlocked bootloader) to subsequently edit the CSC and turn recording back on?
Does anyone have any ideas or thoughts? I read that the modem is the same so in principle this can work?