Rogers Wireless has a feature that supports "Name ID" it shows you the name of the person who is calling if they are not in your contact (usually, it's from the public phone book records, so it works for businesses, Landlines and VoIP customers)
This feature works natively on iphones and blackberries and most older android devices. However, with 6.0 marshmellow (nexus 5x), mine doesn't work, even if I turn off "Caller ID by Google" reverse lookups in the settings.
I'm wondering if other people have the same symptoms. It's hard for me to test because many providers do not support this "CNAP" feature
does it work on non rogers phones? (unlocked phones not available thru rogers)
reason i ask is Rogers doesnt sell the 5X, so Rogers specific features, ie VoLTE, etc dont work on it.
Edit: I'm with Rogers, I've never even heard of this.. it doesnt work on my 5X, also i dont believe it worked on my 6P it worked on my 6P until my google account synced. then the name changed to what i had in my contacts for that number.. I think this is something like i mentioned above, non rogers phones not working with the Rogers features.
I don't have access to a nano-sim adapter at the moment, but I figure it probably worked on my non-rogers Nexus 4 back in 4.x
Its a very old issue with Android, not just Marshmallow, but since way before it, going back to Froyo.
It does not work on any Android AOSP or Cyanogenmod AFAIK unless that ROM is provided by the Cellular provider. If you update your ROM from any other source, it is guaranteed not to work. Do a google search, its a well known issue and its a problem with AOSP Dialer+Contacts+Framework that they never bothered implementing for GSM users. However as mentioned before, if the ROM comes from your provider, they will have the code in the App+Framework to make it work.
cloneman1 said:
I don't have access to a nano-sim adapter at the moment, but I figure it probably worked on my non-rogers Nexus 4 back in 4.x
Click to expand...
Click to collapse
Related
Hi,
my provider (free.fr) activated one very good feature on his internet boxes => wifi secure
this way, each mobile client who are at the same company could connect to freewifi network without needing to give a pin or a password...
So if i'm at a friends house, and have NO 3G signal, i simply start wifi and it connects to his internet box with a specific IP adress (so the ISP can know if it was the user or a mobile user who did something in case of abuse)
that's for the cool part, this all works with EAP-SIM (so the simcard does the authentification)
that's the cool part
the less cool part => this feature does not seams to be in the actual high end nexus ?!?
whereas ihpones, blackberry or some other android devices (galaxy S) does this...
there is an issue request here and some guy told that this is a RIL problem...
now question:
is this really a RIL problem ? or does a specific ROM have the EAP-SIP option in the 802.1x EAP security menu ?
it is really a shame that the galaxy nexus who is newer and better than the galaxy S, does not have that kind of feature....
I think what you are looking for was originally called UMA (Unlicensed Mobile Access) and now called GAN (Generic Access Network). It allows you to make and receive calls using your normal mobile number, but over Wifi. I have not looked for any phone or apps that support the technology, but I think that is what you want to look for.
clobber said:
I think what you are looking for was originally called UMA (Unlicensed Mobile Access) and now called GAN (Generic Access Network). It allows you to make and receive calls using your normal mobile number, but over Wifi. I have not looked for any phone or apps that support the technology, but I think that is what you want to look for.
Click to expand...
Click to collapse
Nope, he's actually talking about EAP-SIM, which is an oft-requested feature on the Android Issue Tracker. Some phones implement it (the GSII does), and it's unclear to me what's needed from the RIL/baseband to enable it. IIRC there are a few mods to enable EAP-SIM on phones which had it disabled, it might be worth looking into that and see if a dev could chime in on the issue.
I think that this link could interests you:
code.google.com/p/seek-for-android/wiki/EapSimAka
The devs need to add this to their roms...
Add a star here to make the things move faster:
code.google.com/p/android/issues/detail?id=9329
G0belet said:
Nope, he's actually talking about EAP-SIM, which is an oft-requested feature on the Android Issue Tracker. Some phones implement it (the GSII does), and it's unclear to me what's needed from the RIL/baseband to enable it. IIRC there are a few mods to enable EAP-SIM on phones which had it disabled, it might be worth looking into that and see if a dev could chime in on the issue.
Click to expand...
Click to collapse
My point is that EAP-SIM (and EAP-AKA for 3G) are used in UMA/GAN.
EAP-SIM on Galaxy Nexus
I would expect the high end Galaxy Nexus that is sold directly by Google not to have any RIL problem to communicate with the SIM, as it should be really UNLOCKED as advertised and even support different mobile networks.
I will get one and try the solution as reported on code.google.com/p/seek-for-android/wiki/EapSimAka
If as witnessed by the lack of response at code.google.com/p/android/issues/detail?id=9329 this is not a technical problem, but a marketing and/or strategic one I will complain with Google for advertising as UNLOCKED something that it is not, and request my money back.
evelasco said:
I will get one and try the solution as reported on code.google.com/p/seek-for-android/wiki/EapSimAka
Click to expand...
Click to collapse
I tried this patch on my rom oxygen on my htc desire but it didn't work. Can you tell us if you success or not ? Thanks.
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
如下图：
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.
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.
Has anyone else experienced the same problem? Is there any way to get them to reactivate it?
I had an an XT1955-5 that was fully functional on the AT&T network, including voice over LTE. I bought this phone because XT1955-5 was on their list of approved phones. I even checked the sim status to verify that it didn't kick down to 3g/H+ when I made a call, and it had the HD symbol on the call screen.
Despite this, AT&T disabled it because they were shutting down the 3g network. I got them to reactivate it and it worked again for several months. Then, when they sent me the cheap replacement phone and sim card, they deactivated my old phone and I couldn't get it to work again. I tried calling them and talking to their technical support to explain the situation that VoLTE was fully functional on it. They didn't seem to know much other than "the computer says this phone isn't compatible." They said they would try changing my provisions, but they ended up making it much worse so mobile data wouldn't even work anymore.
Do they just go by an IMEI whitelist that can't be overridden? My best guess is that they seem to be shutting down all phones that weren't AT&T branded, so this one gets the axe because it was unlocked from another carrier. This is very disappointing because I really liked this phone for a combination of several factors that I can't seem to find in any others.
Unless I'm misreading the list, this is a whitelisted device on the AT&T network.
Correct, the model number is on their whitelist. That's why I chose this phone and why it's so frustrating that it was deactivated. I guess there's a subset of whitelisted IMEIs within that list, but isn't published. This particular one must not have been on their whitelisted IMEI list because it was unlocked from a nother carrier. Do you know if there's any way to get ATT to add it of am I SOL?
They say nothing about IMEI number limitations.
As long as it's not blacklisted there shouldn't be an issue. This list was just revised so your phone may not have been previously whitelisted.
There's quit a bit of confusion is what I gathered.
Some of the AT&T features like vid calling won't work without the AT&T software maybe firmware. Guess we'll both find out on the 22nd.
Call AT&T advance tech support as this is the game that moves as you play it.
I have a development:
I flashed back to stock/RetUS ROM from LineageOS 18.1 to try to fix wifi calling on T-Mobile since I was trying to switch to them due to this hassle. While I was at it, I read a post on a forum for another phone, where the person said they reflashed stock to reprovision the sim. I figured it's worth a try, so I popped in my AT&T sim card while on stock ROM and to my surprise, it fixed it. The LTE network is fully functional, at least for now. I didn't think Lineage did anything to change the radio firmware or whatever it is that controls how it interacts with the cell carrier. I guess I was wrong.
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
MotoMan1955-5 said:
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
Click to expand...
Click to collapse
AT&T isn't witch hunting. As long as it's firmware is compatible with their protocols it will work.
I have no clue what those protocols are though.
(deleted, mistook carrier)
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
MotoMan1955-5 said:
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
Click to expand...
Click to collapse
If these apply to you try:
Clear system cache
Clear Sim Toolkit data
Reset network setting
Get a new sim card from AT&T, handle like a stick of ram as they can be damaged by ESD.
From what is described, it does sound like a provisioning issue, and calling to get it fixed would probably be the correct solution. But why is it flagged as incompatible? Why would that status be persistent for that line? It's weird.
FWIW, AT&T kicked me off for switching from a OnePlus 6 (not a 5g phone) to a OnePlus N10 (5G phone). They were nice enough to disable my account on a Friday night when I switched sims, and was without cell service all weekend since they apparently don't want to do customer service outside banker's hours. Couldn't use the old one either (on 4G), I was completely blacklisted.
T-Mobile happily accepted my porting on Monday .
I'll save my unkind thoughts past "maybe consider firing them" as I don't want to sound like a loonie.
Man, I wish I could switch. I actually tried switching to a T-Mobile MVNO. They provisioned my SIM correctly, but unfortunately their coverage was insufficient in my rural area. I considered sticking with them and using wifi calling at home if that would work, but that feature was broken on lineage and I thought I got this to work correctly with AT&T.
I did get it working by flashing stock again, calling ATT to have them correctly provision it, then flashing LineageOS again. It has been working properly for about a week so with any luck I'll get to continue using the phone.
The 22nd came and went. I'm noticing some vids pause occasionally. May be just a random glitch otherwise no change. I may eventually try a network reset and have AT&T do it on their end.
Long live 4G LTE