You might read a few threads with the hashtag apn to learn more about previous advice given. Please note however that the APN system changed for AOSP very late 2025, so try to become (a little) aware of the 2026 change. [1]
For APN first step is to know Tracfone’s published APN and try to set them exactly by the technique of Add APN rather than Edit existing APN.
When this is “too difficult” you should “simply” ask for an APN reset. This happens OTA (maybe by a technician rather than the call handler). This may require persuasion, but they are taking your money.
IMS registration
A more advanced concept. Note especially the second part of this advice found in both Pixel 8 Pro husky and Pixel 4XL coral install page:
Warning: Make sure that you can send and receive SMS and place and receive calls (also via WiFi and LTE, if available), otherwise it will not work on /e/OS as well. Additionally, some devices require that VoLTE/VoWiFi be utilized once on stock to provision IMS.
IMS registration check on device
I suggest trying to keep this simple with your carrier to start with … try to deal with APN but also ask if your phone is currently correctly IMS registered with them.
Edited: If Tracphone expresses reservations in your particular case you might consider taking further your experience of rolling back to Stock Android …
Sorry you have effectively tried this, so perhaps a more advanced conversation with the carrier to see if they are prepared to try to identify the difference.
Did it make a change?
If yes will the correct performance now persist to /e/OS if you reinstall? Yes it did.
- I do not think that “Rollback to fix IMS” has been recommended on the forum before (and, edit, you have effectively tried this) but please keep us informed as I have a sense that some current similar user problems might stem from this or similar as carriers have at least two different ways of fundamental IMS registration.
Returning to APN
[1] Advanced … the change is explained here migrate configuration data to carrier_ids
Note that “simple” APN config difficulties can arise if Tracfone is incorrectly registered or missing update in AOSP at Google latest carrier_id/carrier_list.textpb.
Under TracFone I find
carrier_id {
canonical_id: 2022
carrier_name: "TracFone"
carrier_attribute {
mccmnc_tuple: "310240"
mccmnc_tuple: "310260"
mccmnc_tuple: "310280"
mccmnc_tuple: "310410"
mccmnc_tuple: "310950"
mccmnc_tuple: "311180"
gid1: "DDFF"
}
carrier_attribute {
mccmnc_tuple: "310410"
mccmnc_tuple: "310280"
mccmnc_tuple: "310240"
mccmnc_tuple: "310260"
mccmnc_tuple: "311180"
mccmnc_tuple: "330110"
gid1: "DEFF"
}
carrier_attribute {
mccmnc_tuple: "310260"
gid1: "534D"
}
carrier_attribute {
mccmnc_tuple: "310260"
gid1: "4D4B"
}
carrier_attribute {
mccmnc_tuple: "310590"
mccmnc_tuple: "310591"
mccmnc_tuple: "310592"
mccmnc_tuple: "310593"
mccmnc_tuple: "310594"
mccmnc_tuple: "310595"
mccmnc_tuple: "310596"
mccmnc_tuple: "310597"
mccmnc_tuple: "310598"
mccmnc_tuple: "310599"
mccmnc_tuple: "311480"
gid1: "BA01270000000000"
}
}
Also exist “Tracfone-ATT” | “Tracfone-TMO” | “Tracfone-VZW” if you are taking this further here please can you confirm if you are on the “plain” TracFone and we can rule out these other three. Further room for error, idk, is how Google allow these settings to cascade down Android versions.
Good luck.