Develop Bugs

[Q] Internet keeps hanging even with full 3g signal (Three UK)???

OK, Firstly, does anyone else have the Defy on the Three network and is it working alright for you??
I'm just trying to figure out whether this is a phone problem or a network issue. Basically I'll unlock the phone, go onto google, search for something and that's when the wait starts, it's really weird, I'll have full 3G signal, and neither of the little traffic arrows will do anything, which makes me think it's not a network issue. Absolutely all network traffic locks up, including gmail, market etc
But then if I make a phone call and hang up it will start working again fine. All I can think is that it's just a little software glitch in my phone. Does anyone know if Motorola will send me a ROM update/repair tool for the phone because I'm guessing it's something to do with that, or even try rolling back to Eclair 2.1 to try that. And yes, before you ask, I've tried many times doing a full wipe/factory reset and it makes no difference.
I've quadruple checked all my APN settings for Three which don't even have usernames or passwords and even checked the settings were correct in the secret service menu. Also when I had the problems I ran a ping test (in the secret menu *#*#4636#*#*) and they all returned "failed could not find ip"
It's just so weird how random it is, I can't work it out. Maybe the defy really isn't compatible with three.
If anyone's got any ideas please please please leave info below.
One other thing I forgot to mention is that the defy was previously locked to Tmobile(uk) and was unlocked using a simple unlock code, no hacking or modding involved

Hi mate,
I've been using my defy on 3 UK with no problems since Jan. I've been on eclair the whole time. Currently the 2.51 stock.
Olly

[Q] T-989 - No data network. Mobile Network State: Disconnected

Hi there. I own an unlocked, rooted t 989 Samsung Galaxy SII which I bought in the US. I recently moved to the Netherlands, and got a new simcard with Vodafone. The problem: I can't get my data to work.
I have tried (almost) everything, so prepare for a read. Here's the list:
- Sim card is fine, I tried it in a old phone and 3G pops up instantly
- Rebooted, pulled battery, turned mobile connections on/off, handpicked network, etc, etc, all the basics.
- Got the APN settings from Vodafone. Tried them manually, resetted them, automatically, turned it on, turned it off.
- Going online through Wifi works.
- Under settings-Status it reads under Mobile Network State: Disconnected. But I know that the phone detects the network correctly. It can distinguish between UMTS and GPRS here.
- So there seems to be no trouble with the phone being incompatible with the network. I read online that other people had NO trouble using their T989 in Europe.
- I tried inserting my old American pre paid T mobile sim card and turn roaming on. No luck.
- A lot of other people with the same problem tried to link it to Easy Battery Saver. I tried updating, uninstalling and going into its settings to find out what it could be, but nothing.
The last thing I can still try is to factory reset, unroot and try to get the phone to its most original state and see what it does. But before I triple wipe all my contacts, pictures, apps, etc, I want to make sure I did absolutely everything to try and fix this beforehand. Being a noob here, I can't post any links but I trust you I tried.
The people at Vodafone are of no help whatsoever. I hope you geniuses could help me any further.
[Edit] And sorry for posting this in General Chat. If a mod could move my question to Q&A I'd be most thankful..!

I am having the exact same damn problem! it started with being unable to send a simple text message yet having data. now it says it is searching forever

thijsr said:
Hi there. I own an unlocked, rooted t 989 Samsung Galaxy SII which I bought in the US. I recently moved to the Netherlands, and got a new simcard with Vodafone. The problem: I can't get my data to work.
I have tried (almost) everything, so prepare for a read. Here's the list:
- Sim card is fine, I tried it in a old phone and 3G pops up instantly
- Rebooted, pulled battery, turned mobile connections on/off, handpicked network, etc, etc, all the basics.
- Got the APN settings from Vodafone. Tried them manually, resetted them, automatically, turned it on, turned it off.
- Going online through Wifi works.
- Under settings-Status it reads under Mobile Network State: Disconnected. But I know that the phone detects the network correctly. It can distinguish between UMTS and GPRS here.
- So there seems to be no trouble with the phone being incompatible with the network. I read online that other people had NO trouble using their T989 in Europe.
- I tried inserting my old American pre paid T mobile sim card and turn roaming on. No luck.
- A lot of other people with the same problem tried to link it to Easy Battery Saver. I tried updating, uninstalling and going into its settings to find out what it could be, but nothing.
The last thing I can still try is to factory reset, unroot and try to get the phone to its most original state and see what it does. But before I triple wipe all my contacts, pictures, apps, etc, I want to make sure I did absolutely everything to try and fix this beforehand. Being a noob here, I can't post any links but I trust you I tried.
The people at Vodafone are of no help whatsoever. I hope you geniuses could help me any further.
[Edit] And sorry for posting this in General Chat. If a mod could move my question to Q&A I'd be most thankful..!
Click to expand...
Click to collapse
Try flashing a different radio/modem then an american one?

@decko5 Nice to see I'm not the only one, but that doesn't help us yet .
@doug36 Besides the fact that I'm running a stock ROM that should be compatible with no issues, I'm not sure how I'd do that. I can flash a separate part of the kernel? That sounds like a very tricky thing to do.

thijsr said:
@decko5 Nice to see I'm not the only one, but that doesn't help us yet .
@doug36 Besides the fact that I'm running a stock ROM that should be compatible with no issues, I'm not sure how I'd do that. I can flash a separate part of the kernel? That sounds like a very tricky thing to do.
Click to expand...
Click to collapse
It's actually pretty easy. You can flash most radios via ClockworkMod Recovery. I couldn't find any threads with a list of Galaxy S-II radios here on XDA, but I found one over at RootzWiki for you. http://rootzwiki.com/topic/2725-radio-samsung-galaxy-s-ii-radios-updatezip-updated-20-aug-2011/
Just find the corresponding one to your geographical location and carrier (Google is your friend) and follow the steps.
Good luck and hope it helps!
(p.s. you should definitely look to see which radio you currently have so that you can download a backup of it before you go flashing radios.)

Thanks for that very helpful post! I've raped and butchered Google, but I'm still having trouble finding out which modem I should download. There seem to be so many and the post on RootzWiki gives no guidance to which is which. Any wisdom on this? I'm in the Netherlands, so Western Europe, on a Vodafone network.
By the way. I fully wiped my phone and installed Team Kang's Juggernaut 5.. No luck, same problem. What I found really, really weird is that it was instantly in Dutch. (Which is ok, I speak Dutch) But I don't remember ever selecting a language. How does it know? Besides, I'd rather have it in English .
What I did find out is that I'm still using a old firmware, UVKID, instead of UVKL1. So I'm restoring back to my previous ROM and trying to update. I'll see what happens. If that doesn't work, I'm going to restore my phone to stockest of the unrooted stocks and try and update.
If that doesn't work, I'll have no option but to send the phone to T-mobile.
I'll try the modem update as soon as I understand what I'm doing . But it does sound promising. Thank you so much for your help, it's greatly appreciated!

Hi guys,
I've updated my firmware to UVKL1, still no luck. Anybody who can tell me which radio I should try on this Vodafone network in the Netherlands?

I am from India and had faced this similer issue with many of my android phones specially with captivate and infuse.......Here what i always did to connect data network.
Just uncheck the use packet data network box in mobile network settings and try to move out from that area (say u are in ur office and going back home) and check the data in settings.
This thing has worked for me always, I don't knw if its related to the OS or to the network provider but this has helped.
Have u tried any other network sim card on ur phone ?

An update for other people that might be looking for a solution in the future. It turns out to be a clear Vodafone problem. I tried a different simcard from a different network (both T-mobile Netherlands and KPN), and they instantly worked without any trouble.
I went back to a different Vodafone store in Amsterdam, and they were much more helpful than the first one. The sales guy told me he had seen the same problem with AT&T iPhones on the Vodafone network.
I called Vodafone, and they have been very nice to me. But they haven't found a solution yet and are looking into it. They see me registering to the network, granting me access, but still my data doesn't work. They've also told me that they will let me cancel my contract for no cost if they don't find a solution.
So problem remains unsolved, but at least there's some light at the end of the tunnel. I was close to buying a new 500 dollar phone... Americans going to Europe: Beware with getting a Vodafone simcard. Sorry to the Vodafone guys, but as for now, that's the status.

So to give closure to this issue (I always hate it when people fix their problem without telling the interwebs..)
IT WORKS!
After an initial terrible experience at the Vodafone counter, the headquarter tech guys have really been great to me. So it is indeed a Vodafone problem. American phones always give them a headache. They don't know what causes the problem exactly, but they do have a fix. It turns out that when logging on to the data network, American phones (AT&T iPhones, my T989 SGsII, and some other Android devices) sent some gibberish along that make the Vodafone server go cuckoo.
The solution was, miraculously, to sign me up (for free!) to the WiFi hotspot service that Vodafone provides, and then logging on to a different APN, being: office.vodafone.nl in my case.
Hope this helps anyone who's having similar issues.

T-989 network solution SOLVED ?
thijsr said:
So to give closure to this issue (I always hate it when people fix their problem without telling the interwebs..)
IT WORKS!
After an initial terrible experience at the Vodafone counter, the headquarter tech guys have really been great to me. So it is indeed a Vodafone problem. American phones always give them a headache. They don't know what causes the problem exactly, but they do have a fix. It turns out that when logging on to the data network, American phones (AT&T iPhones, my T989 SGsII, and some other Android devices) sent some gibberish along that make the Vodafone server go cuckoo.
The solution was, miraculously, to sign me up (for free!) to the WiFi hotspot service that Vodafone provides, and then logging on to a different APN, being: office.vodafone.nl in my case.
Hope this helps anyone who's having similar issues.
Click to expand...
Click to collapse
ok the issue here is that some of the t989 are vodafone and some are USA network , now the other solution is that you flash with command prompt which there is a link to that tool im going to upload from the link i got it from . its also a clockrecoverymod , but this 1 asks you for deleting data user on the device and also resets the network includes USA/overseas though if your not customed roms
or any hacked roms , after flashing this device your basically removing any unwanted apps and cache that are hidden during network searching will be fixed bugs , put the simcard in slot but make sure that is a 3G/4G accounts, than its going to reboot the device automatically , it should be searching for service and also will be a circle with a slash on it where the service bar usually is , just wait about 1/2 hour to an hour maximum time let it do its thing , ok whats happening now to the phone is that is thinking with android network with usa and overseas market apps comparing both carriers network also gets the proper address for the custom rom or original kernel, froyo either 1 will get the correct network address and / VPN / and also will be adding both T-mobile/AT&T choose T-mobile dont go for AT&T cause it will research network configuration plus the phone its not unlocked for both its just a network passby to get correct WPN/VPN/clockworkrecoverymod .

Where is an fix?
Sent from my SGH-T989 using xda premium

@#11 That reads like gibberish to me
@#12 I think I posted a fairly extensive report on how I fixed this...?

[Q] HTC ONE X phone number unreadable after upgrade to 4.2.2

Hi everyone,
I seem to be facing a problem that I haven't found discussed here with my phone.
Following a successful upgrade to Slimbean 4.2.2 build 6 OFFICIAL, everything seems to be working correctly with my Tmobile UK SIM card and I can make or receive calls and texts, I can read the IMEI reference but for some reason my phone number is not displayed anymore in the "about phone" section in Settings or if I use an app like "SIM Card" to read the details of the SIM. I get instead the message "unknown number"
I am not sure if this is a problem or not, so I would like to know if anyone can think of any potential limitation due to this issue.
On top of this, I am about to move abroad and was going to request a code from Tmobile to unlock the phone as I assumed the phone was locked to their network, but when I tried a THREE SIM card, the card was actually accepted and I connected to that network but again the phone number is not displayed in the settings section...
Has anybody seen or heard a similar issue?
I installed a fresh Slimbean ROM from scratch as I was previously running a completely different ROM and I assume it was successful as everything seems to be working.
The only issues I could find in the forum were related to not being able to retrieve the IMEI number after the upgrade, but nothing about the phone number itself.
I would be very grateful if anyone could offer any help or suggestion.
Thank you in advance.
David.

I have noticed the same thing on the official CM 10.1 builds (with both Three UK and giffgaff SIMs), I suspect it is an issue but it's not a real bother to me all it means that any app that auto detects your phone number (eg hangouts) will just ask for it during initial setup instead.
Again the same for the IMEI sometimes this doesn't show up but it does most of the time.

hydo1 said:
I have noticed the same thing on the official CM 10.1 builds (with both Three UK and giffgaff SIMs), I suspect it is an issue but it's not a real bother to me all it means that any app that auto detects your phone number (eg hangouts) will just ask for it during initial setup instead.
Again the same for the IMEI sometimes this doesn't show up but it does most of the time.
Click to expand...
Click to collapse
Thanks Hydo1,
I have found a couple of things yesterday.
First, I have been able to add the number manually through the settings menu in the dial pad and it now shows in the "about" section.
Second, I have found out that although my voicemail is setup and active when I call the Tmobile services, it doesn't actually work anymore and I can only guess it is due to this issue as it was working before...
I'll try again once I have switched to a new network abroad...

WIFI Authentication Issues

Hello,
I'm a happy G3 owner, D855, 3Gb/32GB International version. I rooted using IOroot successfully and have done 2 OTA updates since then, currently on 10g, root still on.
I'm having major issues when trying to connect to WIFI routers in cafes/restaurants/hotels, public places in general, whereas my wife's phone and my smartwatch (believe it or not, with its mini antenna in the wrist bands (Omate Truesmart)) connects from the first try.
On the G3, I get "Authentication error" almost always, but it is working properly at my home, my parents house etc.. Only in public places or rather in places where there are a lot of people connected usually.
Does anybody have an idea what to do to solve this issue?
Many thanks for any help/tips
Chris

I do not have same issue but very simillar. Everytime wanna connect to public wifi LG G3 Android 5.0 show up screen with "login into network". Nothing more. Web browser won´t open page with login name and password even own web browser is not openning anyway. It works before Lollipop arrived...

I have the same problem, do you solve it?

You could disable "Show passwords" (Settings / Security) and try again. For some people this appears to work :good:

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.