ATT Port to Verizon S20 G981V Questions - Samsung Galaxy S20 / S20+ / S20 Ultra 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.

Related

[Q] Verizon phone user in China

Courtesy of a very good deal while I was in the USA, I was able to pick up an HTC One M8 for $100. Seemed like a great deal for my first Android phone running 4.4.2. Talked with their support people, to guarantee it wasn't locked, confirmed that with a couple of web sites, then bit the bullet. Now I am back in China, using China Telecom, which is compatible with respect to data transmission, and both voice and SMS works fine.
But data, with a 4G SIM, doesn't work at all. Nor does 3G, or 2G. Oh yes, we have no chickens (G in Mandarin sounds like 'ji', which means chicken). Investigating things, it seems that this is because in trying to configure the phone APN for China Telecom, there is a required field which Verizon doesn't display: PPP. Without a way to set up PPP field to #777, there is no way to get the phone to talk China Telecom's network. Additionally, even when I try to save the APN information, it resets fields like MNC (CT requires 03) back to the Verizon value of 11. WTF? Obviously, it is time for me to venture into the world of a custom ROM, since that might make all the things I need visible. Decided to go with Android Revolution ROM.
I rooted my device with Weaksauce, downloaded all the required files, and was looking into custom recovery when Verizon pushed to me that an upgrade for my phone was available (4.4.3). Decided WTH, maybe that will expose the PPP entry that I need.
Nope, Weaksauce no longer works (and I didn't get to the point of S_off before that happened). the APN menu is now completely locked (with no ability to change anything or create new APN entries), and now I am concerned that Verizon has hosed my ability to get this phone working in China as anything other than a wi-fi capable data machine.
As a first timer delving into this world, I would appreciate some quick pointers to make sure I am going in the right direction.
Thanks in advance.
If you can read Chinese, the settings are supposed to be as follows for the APN:
名称:中国电信互联网设置CTNET (也可以用自己喜欢的)
APN:ctnet
代理:(未设置)
端口:(未设置)
用户名:[email protected]
密码:vnet.mobi
服务器:(未设置)
MCC:460
MNC:03
身份验证类型:PAP或CHAP
APN类型:default
PPP拨叫号码:#777
如下图:

Connects to Guest Networks

Hello,
I have a Samsung Galaxy Note 2, SGH-M317i (Bell Mobility) and recently installed Cyanogenmod 12.1 (Lollipop 5.1.1). All is running well, the device actually seems to be running much faster...probably due to the lack of bloatware that originally came with it. Sure, I miss some of the "cool" features that the manufacturer had added (ie. hand swipe for screen capture), but overall I am extremely happy with the decision to flash the ROM. Although it does self-identify as a SGH-N7105 now. (About Phone > Device model)
Anyway, I have noticed that when I have my guest networks enabled on my home router (an ASUS RT-N66U running the latest Merlin firmware), my phone insists on connecting to the Guest networks (a2.4 and 5 GHz) instead of my full, "regular" network (hidden SSID, but a "Saved" network in the phone). Even if I go into the WiFi settings and tell the phone to forget those entries, it will still try to connect...even going so far as to say "connected" even though I know it does not have the proper credentials. I have no idea what is causing this as the problem was not present on the stock 4.4.2 KitKat that I had previously.
Sure, I could give it the credentials for those guest networks (all are WPA-Personal protected) but I have restricted those from accessing the intranet as they are primarily for guests who come by, so that is not really a viable option.
Does anyone have any suggestions? It seems strange that it attempts to connect and save these networks, so technically, I shouldn't have to do anything to keep the phone from connecting. However, since it insists, I had thought that Android would have a native (not requiring an app) method of blacklisting these networks. I have looked at apps such as WiFi Ruler, but again would've thought that there is a manual way of doing this. (I don't know if this is obvious by virtue of the fact that I am running a custom ROM, but the phone is rooted.)
Thanks!
used this code and off your wifi power saving mode and try *#0011# select wifi..u may need need press the botom left button to select wifi
Very odd. It seems that since installing CM12.1, my device no longer accepts or recognizes USSD codes. I guess I hadn't noticed since I had rooted and unlocked it prior to flashing Cyanogenmod over the stock ROM. I did some reading and I found that there is a patch to enable those codes (and SMS) on CDMA models of the Note 2. However, mine is LTE and does SMS, MMS, and it uses LTE without issue.
Here is a link to that page:
http://forum.cyanogenmod.org/topic/112400-solution-to-sms-and-ussd-code-on-cm121-cm12-cm11-cm10/
Is this something anyone else has experienced? Should I follow the instructions on that page and install the patch?
Again, my phone is a Samsung Galaxy Note 2, SGH-i317M but since the installation of CM12.1 the About Phone > Device model reports it as being a GT-N7105 with a Baseband Version I317MVLUDNH2.
I'd really like to try the solution to my WiFi problem, so if anyone else has had experience with the USSD codes not working please let me know if there is a solution.
Thanks!
To update my last post:
Some USSD codes do work, I watched the pop ups more closely this time and there is one before the "...invalid MMI code" that says "USSD code running". The main one that find interesting no longer works is the one I had used to unlock my phone *#197328640#. I had figured that it would not have disappeared simply by installing Cyanogenmod. Further, I also followed that thread I had posted the link to a little further, and I'm not comfortable flashing the "patch" it leads to as I cannot confirm it's original source and it does sound like it may be another full ROM.

S7 Active for use outside the US (WiFi Calling and Software Updates?)

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.

VoLTE and WiFi calling

Hi
I am trying to enable VoLTE and WiFi calling on my Nexus 5x. My carrier supports these features, and as far as I know, Nexus 5x is capable of supporting them as well. My phone is rooted, and runs Pixel 2 ROM which I found on xda (https://forum.xda-developers.com/nexus-5x/development/rom-pixelmod-lg-nexus-5x-t3486862). I have Magisk flashed and I just enabled the "VoEnabler" module so that I get the necessary toggles in Settings. They appear, but unfortunately, they do not work. When I check IMS registration in ##4636## (##INFO##) it still says "Not registered". I have learnt that I need to enable a certain "profile" for the Qualcomm radio chip as well, so I downloaded QPST_2.7.460 and managed to see the phone in PDC.exe after installing the correct Qualcomm drivers on my PC, and setting the DIAG PORT to on for the phone by issuing the command 'su; setprop sys.usb.config diag,adb' in a Terminal emulator on the phone. Where I am stuck now, is in PDC, because it only shows me 3 profiles: HW_DEFAULT, SW_DEFAULT and ROW_Generic_3GPP. I read that Vodafone_India, or Telefonica UK, or Telia Finland would be profiles that may work with my carrier and allow my phone to register with IMS, but unfortunately I do not have those in the list. So, my question is, does someone have more experience with this, can I load MBN files for this profiles using the "Load" button in PDC? If so, do files coming from other Nexus 5x, or even other phones work? If anyone has any experience with this, any help would be grately appreciated.
A little update: I tried with some of the mcfg_sw.bin files from the stock ROM, unfortunately, it just cannot activate for Sub0 and switches back to ROW_Generic_3GPP. Furthermore, I downloaded an LG G4 firmware, as that phone uses the same chipset, and tried to see the files extracted from the KDZ file usig 7zip, yet none of the "mcfg_sw.bin" files actually appear in PDC so I cannot "activate" it on the phone. Would really appreciate someone with a bit of experience to guide me on this one.
Thank you very much.
PS. Sorry if this is the wrong section, feel free to move it wherever it belongs to.
Your carrier needs to have enabled these features in their network for your phone model, too.
I've found that support for VoLTE is very spotty among custom ROMs. Some don't seem to pay any attention to it, some say they "support" it but it doesn't seem to work. That may be a per-carrier issue. FWIW I'm on Verizon in the USA and CandyROM is one of the few I've found that "supports" VoLTE, *and* it actually works for me, *and* the ROM is actively maintained. So maybe try that one if you're not too attached to PixelROM. I wish this feature was paid more attention by developers, it really makes a big difference in call quality.
The carrier supports it, of course. Do you have the same phone (5x) and run CandyROM on it? Have you got a link for it? I don't see how ROMs really have to do anything special, since they do not touch the radio partition, which is still the one from stock. You just have to add the toggles to the Settings app by editing build.prop, I guess. But I will take a look anyway, maybe it actually works, although my carrier does not support this actual model, I was hoping I couod change the modem config on it and force it to work with WiFi calling and VoLTE.
https://forum.xda-developers.com/nexus-5x/development/rom-candy8-1-beta-t3749484/page9
Yes, I have a 5X, run this ROM, and VoLTE works.
Jacquestrapp said:
https://forum.xda-developers.com/nexus-5x/development/rom-candy8-1-beta-t3749484/page9
Yes, I have a 5X, run this ROM, and VoLTE works.
Click to expand...
Click to collapse
Maybe I'll try it, although I am pretty sure it won't work by default on my carrier, since it has the same default radio which lacks the proper config for my network. That's what I am trying to get, a proper config that will work with my phone, by switching it with Qualcomm PDC.
For Verizon, the necessary config is already in the radio image, of course, and probably gets picked up automatically when the device signs into the network. For Europe, all I see is EE UK...
In the UK the operator EE does support VoLTE for many phones but not for the N5X, even if you've "provisioned" it in your ROM.

Anyone w/S7 Active on Red Pocket? Mobile hotspot & tethering just broke

Hello all,
I was warned of an impending "update" a few nights ago. Since it hit, my mobile hotspot no longer works.
Does anyone else have an S7 Active on Red Pocket who has a working hotspot? If so, could you share the APN settings you are using, and the Android version you are on?
I think they rolled me back to January 2018. G891AUCU2BRB5
Would rather not factory reset or root, but getting very close to doing so. Neither RP or AT&T are helpful here.
Thank you,
Bob
Red Pocket Mobile Hotspot problem solved - stock Oreo 8.0 fixed it
Well, for anyone who might encounter this, I finally resolved it.
Pulled the SIM card and did a factory reset. Then it recognized the Oreo update over Wifi. Had to load an intermediate update first.
I put it Red Pocket's AP settings.
First time I tried Mobile Hotspot, it still didn't work.
Restarted the phone.
Still didn't work.
Then I remembered one rep saying to switch MVNO type to "IMSI".
3rd times a charm. Hotspot and USB tether now both working.
After ten hours of wading through poor advice, I'm back to where I was four days ago.
With one exception: I learned how to turn on Developer Mode (tap Build Number 7 times in Software Info)
AND SHUT OFF THE AUTOMATIC UPDATES UNDER DEVELOPER MODE SO IT WON'T HAPPEN AGAIN!!!
I have a stock S7 Active/G891A that I bought unlocked on eBay in March of 2018. It's currently running Oreo 8.0.0, build G891AUCS4CSA3. I just now disabled OTA updates thanks to you.
I've been trying to get Mobile Hotspot to work on this phone ever since I switched Consumer Cellular several months ago. Whenever I tried to enable hotspotting the phone screen would display a popup:
Please wait while verifying
Which was a normal message on the AT&T network, but now (using AT&T's network through Consumer Cellular), after 5-10 seconds a different window would appear:
Tethering/Mobile AP is unavailable.
A network issue may be preventing use of your Mobile Hotspot. Please call Customer Care at 611.
[excessive hard-coded line breaks omitted]
Over the course of several weeks in January I literally spent hours on the phone with several Consumer Cellular 1st and 2nd tier support techs trying to get past that error. Tier 2 support gave me new APN settings, had me do a network reset, and suggested that I do a factory reset. Which I did later, but that didn't work, either. Then CC tier 2 support gave up and bumped my ticket to tier 3. Tier 3 support then transmitted their version of an APN definition to my phone, but still no love. At the end of the 2nd week of phone tag, a Tier 2 tech told me that "it <Mobile Hotspot> just doesn't work with some phones not sold by us".
Maybe hotspotting won't work with my old Motorola Razor, but I was pretty sure that I'd eventually strike gold with my trusty G891A.
Because my S7 Active has version 4 of the boot loader (thank you, latest and final OTA), I haven't been able to find anything that resembles a working root. I even paid OneClickRoot to do it via remote desktop session, hoping that they had some good mojo that I hadn't yet discovered. But their support tech hit a wall, too, and ended up flashing my phone back to stock Oreo 8.0.0. They also refunded my purchase almost immediately which made me sort of happy but still sad that I had no Hotspot abilities.
While searching for possible workarounds (ROMS, root, mystical incantations) tonight I came across your posts:
bobcpdx said:
[snip]
Then I remembered one rep saying to switch MVNO type to "IMSI".
[snip]
Click to expand...
Click to collapse
So I followed your tip. I created a new APN definition and copied in all of the values from the CC Tier 3 definition . I then set Mobile virtual network operator type to imsi . This value was set to None in all in all of the other APN definitions on my phone.
I didn't even need to reboot the phone. I selected my new APN definition and enabled Mobile Hotspot. The first message about verifying came up. But then the phone didn't direct me to dial 611. Mobile Hotspot simply started working.
Thanks every so much for sharing this insight.
bobcpdx said:
Well, for anyone who might encounter this, I finally resolved it.
…..
Then I remembered one rep saying to switch MVNO type to "IMSI".
3rd times a charm. Hotspot and USB tether now both working.
….
Click to expand...
Click to collapse
WOW! Thanks so much for posting this. I've been struggling for a couple of months to find a way to hotspot my two unlocked LG's (G6 and a G7) on Cricket and Consumer Cellular. This trick enabled hotspot/tether quickly and easily.
My apologies to Cricket and CC, for my unflattering thoughts about them. I assumed it was their issue! Not sure why these unlocked LG's are fidgety like this. We got a Moto X4 (Android One flavor) in the family, and it can hotspot with no tweaking.
BTW - I have a similar issue with call forwarding on the LG's. Can't enable it, get an error. But the Moto X4 has no problem on either of these AT&T MVNO's. Anyone have an easy answer for that? Thanks.
This doesn't answer the call forwarding question. I'm not sure who pushes OTA updates, but soon after my last post I got a notification that an my phone needed to be rebooted for an update to finish. This was after I (at least thought that I had) disabled automatic updates. After the update the hotspot feature no longer worked. I checked APN settings and found that the update had reset the APN MVNO type to NONE . I manually changed it back to imsi and it's been working ever since. I also made sure (twice with reboot in between) that automatic OTA Updates are disabled.
Although enabling/disabling these features seems to be problematic with AT&T MVNOs, what I find more curious is that techs at Consumer Cellular claim not to know how to fix them. Maybe that's true, or maybe that's what they are told to say.
Was it coincidence that I received an OTA update within days of making this change, or is the Big Brother with the Blue Death Star logo watching us so closely?

Categories

Resources