Related
Good evening all,
I have a friend who possesses a T Mobile Galaxy S4. He purchased this phone while he was on onsite assignment in USA.
Now he's come back to India and he's using this phone here.
The issue with his phone is, whenever he tries to download regional apps (Indian apps like Tata Sky, mIndicator etc.), play store does not allow him to download and he receives the same message that everyone else who try to download US specific apps from non US locations.
Could anyone let me know whether the issue is with hardware or Google Account?
If the issue is with Google Account, could you please tell me how to get rid of this issue?
PS: He is also planning to flash CM11 and asked me for help. Do I need to unlock the bootloader of TMo GS4 before flashing CM11 or Paranoid Android?
satish0101 said:
Good evening all,
I have a friend who possesses a T Mobile Galaxy S4. He purchased this phone while he was on onsite assignment in USA.
Now he's come back to India and he's using this phone here.
The issue with his phone is, whenever he tries to download regional apps (Indian apps like Tata Sky, mIndicator etc.), play store does not allow him to download and he receives the same message that everyone else who try to download US specific apps from non US locations.
Could anyone let me know whether the issue is with hardware or Google Account?
If the issue is with Google Account, could you please tell me how to get rid of this issue?
PS: He is also planning to flash CM11 and asked me for help. Do I need to unlock the bootloader of TMo GS4 before flashing CM11 or Paranoid Android?
Click to expand...
Click to collapse
I can't help you on the regional apps, but as the bootloader goes; it isn't locked in the first place regardless of what Android version you're on.
lordcheeto03 said:
I can't help you on the regional apps, but as the bootloader goes; it isn't locked in the first place regardless of what Android version you're on.
Click to expand...
Click to collapse
Thanks.
The issue is similar to what non US users face when they try to download US specific apps. Just in reverse.
Is there any option in Google Account details that needs changing?
Hey folks,
I bought an S7 Active from eBay and I'm using it in Ireland. Everything is working fine that I need, but my carrier recently introduced WiFi Calling and upon trying to set it up from the setting menu where it reads
"wifi calling lets you make and receive calls over wifi with your at&t accoumt. when you use wifi calling, information about the country where the wifi connection is made will be sent to your carrier. Learn more about wifi calling (link).
GET STARTED"
I get the following error:
"Wifi Calling activation not successful, try again later"
I rang support for my carrier and they think it's something to do with the handset. They support the S7 and the S7 Edge but as the S7 Active is an AT&T exclusive and appears to have custom AT&T software, it seems like it might be trying to connect to AT&T and it can't?
Also, when I check for software updates, it says AT&T Software Update at the top of the screen, now this doesn't give any errors and it says software up to date, so I'm not sure if this is correct or if there's new software out that it can't connect to update?
Is there any way around this? I know maybe it's possible to ROOT and install a new ROM, but I'd rather avoid that hassle..
Any feedback would be great
I am in the same situation. S7 Active unlocked from EBAY, and using it in Czech Republic with Vodafone sim. Is here chance to get OTA Nougat update?
I'm using one in Canada and flashed the updates described in another thread in this phone's forum. They will reset your phone to factory, but you will have 7.0 nougat and security patches into April, 2017. I doubt any kind of OTA will be forthcoming unless you have an ATT SIM, but I'm not an expert in this at all. I plan on keeping good backups and flashing the updates as they become available. Aside from that, it's a great phone. If they make the s8 active global, then I'll look into getting one some time down the road.
Thanks for the replies. Does the S8 have an active version? I hadn't heard anything on it yet?
so when you flash nougat 7, does it completely wipe and install a new ROM on your phone, or it just updates the AT&T rom, so even with the update, you're still bound to the AT&T settings for updates/wifi calling etc?
Yes, it wipes out the phone completely, you'll have to set it up again. Everything else is same, such as AT&T bloats, wifi calling etc.
Ok thanks for letting me know. So no point I guess if it doesn't solve the issue
I live in Czech Republic. In situation, when I will buy prepaid sim card from AT T, and I will use it in my unlocked S7 Active, it is possible to get OTA Nougat update?
That's not a bad idea, would possibly work for the OTA update, but maybe not if it's not actually connected to AT&T?
It wouldn't work for the wifi calling though I'm sure?
faronium said:
I'm using one in Canada and flashed the updates described in another thread in this phone's forum. They will reset your phone to factory, but you will have 7.0 nougat and security patches into April, 2017. I doubt any kind of OTA will be forthcoming unless you have an ATT SIM, but I'm not an expert in this at all. I plan on keeping good backups and flashing the updates as they become available. Aside from that, it's a great phone. If they make the s8 active global, then I'll look into getting one some time down the road.
Click to expand...
Click to collapse
I'm in Edmonton AB, Yes, there will be nothing for updates or WiFi calling if you are not on the ATT network with their SIM.
Which ROM did you update to, the QD4, or past it?
Keep it rolling
I'd love to know more about using the S7 Active internationally from anyone who has been down that road already. In the UK and considering getting one from Ebay but I would immediately want to update it to Nougat and I'm unsure if this will be possible? I have a Mac laptop in the house and would hope to use that to apply any upgrades. Really appreciate any info you guys have!
mmmbient said:
I'd love to know more about using the S7 Active internationally from anyone who has been down that road already. In the UK and considering getting one from Ebay but I would immediately want to update it to Nougat and I'm unsure if this will be possible? I have a Mac laptop in the house and would hope to use that to apply any upgrades. Really appreciate any info you guys have!
Click to expand...
Click to collapse
ODIN is only available for Windows (Vista/7/8/10). You will have to run Wine for just the Odin program or Boot Camp for the full Windows OS in a partition.
Wine is the easiest solution, start there and install the program, USB drivers.
UnableToResetOldProfile said:
ODIN is only available for Windows (Vista/7/8/10). You will have to run Wine for just the Odin program or Boot Camp for the full Windows OS in a partition.
Wine is the easiest solution, start there and install the program, USB drivers.
Click to expand...
Click to collapse
I to am in the UK and purchased a S7 Active from Ebay. The phone came in a sealed box and worked fine. No AT&T logo at startup or bloatware. However when I rebooted the phone after switching of, an integrity error came up which forced me to wipe/erase the phone. I thought maybe a first time glitch but it did it again and all was lost. Had my old S4 Active so persevered and read info on this post to reflash firmware to QB2 using ODIN. Now note this is the first time i have ever attempted anything like this so complete newbie. However all went well and I now have a phone on Nougat. It reboots without error now. But it is now back to AT&T with logo at Startup and US voice for google navigation etc... Google pay now does work though. I am pleased with my results but would love to have firmware that makes it non AT&T specific for use in the UK, any ideas would be greatly appreciated.
Hello fellas(and ladies)
I have a Samsung Galaxy S9, from t-mobile, dark blue. I've locked myself out of the device, and I have a friend that is going to help me get it back working. In order for him to be able to help me, he needs to know the model number. I know it's a SM-G960.. but how do I determine the exact model (i.e. sm-g960f, sm-g960e, etc). I'm unable to login to the phone so I cant check it like that, and the back cover is sealed on there as you know unless you have the tools to remove the cover (which I don't). Is there another way to find out which model it is, like download mode or recovery mode or something? Thanks for taking the time to read this, and for your advice.
Edit- US Model
KooKlique said:
Hello fellas(and ladies)
I have a Samsung Galaxy S9, from t-mobile, dark blue. I've locked myself out of the device, and I have a friend that is going to help me get it back working. In order for him to be able to help me, he needs to know the model number. I know it's a SM-G960.. but how do I determine the exact model (i.e. sm-g960f, sm-g960e, etc). I'm unable to login to the phone so I cant check it like that, and the back cover is sealed on there as you know unless you have the tools to remove the cover (which I don't). Is there another way to find out which model it is, like download mode or recovery mode or something? Thanks for taking the time to read this, and for your advice.
Edit- US Model
Click to expand...
Click to collapse
Your box will tell you. But its a u model. ALL US CARRIER PHONES ARE A U MODEL, there is no difference between any of them.
kekistaneerefugee said:
Your box will tell you. But its a u model. ALL US CARRIER PHONES ARE A U MODEL, there is no difference between any of them.
Click to expand...
Click to collapse
Thank you for taking the time to answer, I appreciate it.
KooKlique said:
Thank you for taking the time to answer, I appreciate it.
Click to expand...
Click to collapse
You just keep locking yourself out of devices don't you....
https://forum.xda-developers.com/galaxy-j7/help/galaxy-j7-g-oogle-verification-issue-t3852720/
Well one thing you can do is reset your Google password on a computer then try to login again after 24 hours. Surely you have a recovery email address which you can use?
This is Samsung's instructions on what to do:
If you already reset your device, but don't remember your Google username and/or password, the device can't be used. In that case, you can do one of these:
If you know your Google username but can't remember the password, you can reset your password on the device, or at www.google.com. It can take up to 24 hours for a new password to sync with all registered devices. After 24 hours, you can try logging in to your phone with the new password.
If you have multiple Google Accounts, and you can't remember which Google Account you set up on your device, visit https://www.google.com/android/devicemanager.
Log in with your Google username and password and check the list of devices registered to the account. If you don't see the device listed on the account, it means the device is registered to a different account. Use the same process to check for devices linked to your other Google Accounts. When you find the registered account, use it to log in to your device.
If you can't remember any of your Google Account information, you can send your device, along with proof of purchase, to an authorized Samsung Service Center. Samsung has special tools to reset the phone to factory defaults with no protection enabled.
Click to expand...
Click to collapse
Source: https://www.samsung.com/us/support/frp/
Furthermore:
It seems dodgy to me that you posted a topic pretty much asking the same thing about a month ago regarding a totally different phone here - https://forum.xda-developers.com/galaxy-j7/help/galaxy-j7-g-oogle-verification-issue-t3852720/
FRP is there to prevent lost/stolen phones from being used, if you've bought a phone that is FRP locked you should take it up with the seller. Not try to break the lock yourself!
Thread closed.
I have a Singapore variant of the tab S4 it makes and receives calls just fine over 3G but wont make them over LTE is VoLTE even possible on this? I travel the country and have ran into a few instances where I have LTE coverage but not 3G
It looks bad
Samsung has disabled VoLTE in every tablet that supports it, tab s3, s4, s6 and s7. It won't comment on this. I suggest contacting Samsung and asking for an update to address this issue. I understand there is a complex hack to accomplish this, but it involves editing a binary file.
If Samsung won't do it, maybe the carrier firmware can enable VoLTE?
AT&T says its Tab S4 variant will continue to work after their 3G shutdown.
Tab S4 (SM-T837A) is listed in their compatible devices:
https://www.att.com/idpassets/images/support/wireless/Devices-Working-on-ATT-Network.pdf
Maybe this means VoLTE is enabled for calling? Or they might mean it will keep working but only for data LTE.
There is no carrier tab s4 that will work for calls, and I don't think sms either! The carriers have a system in which you can have data/talk/text on a samsung Tab 3,4,5,6,7,8 if you also have a samsung phone.
Samsung also has a setting you can enable to make calls on your tablet if you also have a phone, if both devices are logged into your Samsung account. No security flaw there! Not sure if the phone must be Samsung too, but it would seem so!
I'm not going to say what I think about a manufacturer going out of its way to reverse a setting, intentionally crippling its flagship products, so customers need to purchase more stuff to obtain the expected functionality!
I did write to the CEO of Samsung Electronics, Co., Ltd.. I asked for a firmware update to enable VoLTE in the Tab S series beginning with the S3.
Earlier Tab S don't have compatible hardware. If you clear your browser data, so no one can tell you're a hacker, and google 'Samsung investor relations', you can find his name and address.
I'm not going to dox him here. But if anyone wants to write him, please be very civil, clean, upright, and simply ask for an update, followed by, "I only ask for Samsung to live up to its reputation! I think my request is more than reasonable! Thank you for taking your valuable time to read my message. Best Regards, name"
Don't use spinglish--words and phrases that mean one thing implied to mean something else. And example in reverse is when Dell dubbed one of its laptops exploding into flames, 'a thermal event'!
Just be direct, brief, polite and honest.
Samsung chat says:
Hi, thank you for contacting Samsung Care. I’m D-- ....
... It will be updated in coming update. You will receive a notification on your tablet once it got updated.
8:36 PM When do you think the update will be?
8:37 PM Profile SEA Digital Messaging We don't have the exact information. Hope it will update will release in couple of weeks.
8:38 PM This is due to the 3G shutdown? That will work then, with the update I'll be able to download a phone app from the app store?
Thank you
8:38 PM Profile SEA Digital Messaging It is not about the 3G shutdown, the feature is not available on the tablet. Carrier have not permitted to use this feature on Samsung tablet. You can use caling feature on third party applications like WhatsApp ETC.
8:41 PM ok yes. Then I will wait for the update. Is this official it will be updated?
the tablet will be updated to download a phone app?
8:42 PM Profile SEA Digital Messaging Yes it will be official once the Update released you will get notification on your screen.
Once you get the Update it will update automatically to make the calls.
8:44 PM ok thank you D
Click to expand...
Click to collapse
So maybe it'll be soon I'm hoping to use VoLTE for my tablet soon. Otherwise Singapore firmware might allow VoLTE calls currently? Why is that? I can't download or install or side-load any phone app currently.
edit update: I flashed to t-mobile using odin and that lets me send and receive texts just fine using messenger app. I use tello so I can place outbound calls over wifi too, so I can just use google voice for any other phone call inbound. I've heard other versions outside usa might be able to place calls though?? Suppose we'll get an update here soon anyway hopefully.
-Cat_F
There will be convoluted ways to get data/talk/text on the Tab S models without adding VoLTE compatibility.
awesome14 said:
There will be convoluted ways to get data/talk/text on the Tab S models without adding VoLTE compatibility.
Click to expand...
Click to collapse
?
Cat_F said:
?
Click to expand...
Click to collapse
Like calling on other devices, if both a phone and tablet are logged in to your Samsung account, you can use your tablet for Data/talk/txt, because it's actually using the phone.
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.