Teracube VoLTE problem on AT&T in USA

Not sure if these will help but…

Loss of LTE after latest S/W update to 1.12.3 - Teracube 2e - Teracube Community

Advisory - [US] Issues related to AT&T / Cricket (or other ATT based MVNOs) - April 2022 - Announcements - Teracube Community

Although the latter thread closed in October there might be a tip or two to try.

2 Likes

Great link from @marcdw btw … in addition, and having read that …

  1. My experience is that good online access is required any time you want to adjust / edit / create new APN. My experience is that APN settings do not save unless the user provides the full, verifiable, set of APN – these seem to be verified to exist or else they fail to save. If correct, this means a user probably cannot save an APN file incrementally, it should be saved “complete”.

  2. As an alternative to Edit APN are you able to use + at the very top of the APN page, to Add a new set.

Same experience here, after update VolLTE is non-functional. I’m using AT&T .
Data (internet, video calls, etc) works fine.
I looked at @marcdw first posts , after a reset still same behavior.

In APN settings there is a default profile that cannot be edited or deleted.
In order to be able to SAVE a new APN setting I need to be in airplane mode and then select it strangely it would go into modifying/ rewrite itself to deliver the same behavior.

Can I rollback the update?

I’m also having the same problem starting today I just finished posting it here: phone-calls-not-working-teracube 2e e/OS/ 1.12

I see on the teracube forums that last year Sharad stated "Going ahead, we are removing AT&T as a supported carrier " Link

Sure enough, in the current FAQ on teracube’s website all the carriers are T-mobile based.

Does this mean all of us teracube owners where T-mobile is not an option are now the owners of very expensive bricks?

Thanks for the bit of information. Didn’t know that!
I see this going forward with no further troubleshooting or support of the AT&T network and its resellers. Now that’s Teracube firmware, /e/ is a different spinoff. That announcement was last year, since then /e/'s VolLTE support has been working fine for me.

I have been able to save the APN in the past, but this time, it will not save. I cannot edit one, either. Oddly, an extra default shows up called mht. I cannot edit this one, or the one called internet. The setting buttons don’t respond to touch. A new entry will not save, either.
I have reset network settings, factory refresh, removing then adding the sim, to no avail. I’m thinking I might have to revert to e OS 1.10, which was the last one to work. I managed to skip 1.11.

tried most of the same steps to no avail. With exception of network reset (did a full reset instead) and yeah didn’t help.

I reverted to e OS 1.10, and successfully added the necessary access point with no issue. I’m back in business.

EDIT: I wonder if this issue occurs with 1.11. I managed to skip that one.
EDIT: Doesn’t matter, 1.11 is no longer available to download.

1 Like

I recall the release notes for 1.11 expressly stated that it had problems on the 2e and was not released to them.

It’s good to hear there is hope. Thanks all.

To revert to 1.10, did you download a fresh rom and install from scratch? I assume not a dirty install.

Aight! Did the same and worked out right away without additional settings.
@Brado I used the teracube 2e firmware flasher and then used the /e/ os easy installer. Not a single command was misspelled!

Yes, I downloaded 1.10 and did a manual install. https://doc.e.foundation/devices/emerald/install
Funny, the “fastboot format md_udc” command did not work, but it still turned out okay. Nice of linux to tell you how to install things like fastboot and adb, and so forth, right there by the command line.

Not necessarily related to the AT&T stuff but for those who had issues with 1.12.3, a new 1.12.5 is now available for stable. Dev will follow shortly.
Supposedly fixes recent issues.

I guess I’d better skip this one, then.

EDIT: On the contrary, this update does solve my AT&T issue. The access point I added carried over from 1.10, and I can make calls.

1 Like

Thanks to all for sharing.

Last week I tried what @eqw21759 did, but
could not make the easy installer work. My linux machine is running mint, which seems not to play well with the qt libraries required for easy installer. In windows the installer kept stalling part way through - I suspect a driver issue that I was not able to chase down using the /e/ support docs.

So I did a manual install of 1.10 using adb and now can make calls again. Whew.

@davking, your latest post seems to say you upgraded to 1.12.5 and everything works, is that right? You used the updater? I can’t find release notes anywhere for 1.12.5

It sure would be nice to be able to roll back without reinstalling and having to redo all the installed apps and settings. It would also be nice to have a recovery like twrp so we could create full image copies. Maybe I’m missing something.

Thanks again everybody.

It was announced here Week 27, 2023: Development and Testing Updates

Update 4 July v1.12.5 has been released for Teracube emerald and zirconia (2e) stable users. They should be able to see it in their updater app. This has the fix for the calls not connecting issue. Will update when fix goes on dev.

It seems dev users are still waiting for such notification.

That was helpful @aibd, thanks. The update ran flawlessly from 1.10 to 1.12.5 and calls work fine.

Having trouble again, cannot edit or save an APN on e v1.20 Internet is very slow in some areas, even though I have a decent antenna.

Same goes for v1.21, cannot edit an existing APN or add a new one. I need to set an APN for Patriot Mobile, which uses AT&T.

Of course usually the easiest thing is to ask the carrier to send the APN over the air to your device. Is there some difficulty doing that ?

So it is possible that the main apns-config.xml has the error and it is being fed to your device with every update. It is a very big file (~3,866 lines) the file is found here https://gitlab.e.foundation/e/os/android_vendor_lineage/-/blob/v1-r/prebuilt/common/etc/apns-conf.xml?ref_type=heads

I searched and linked v1-r (you should search the Android version you are using). I started by searching for cricket as it was mentioned further up the thread, but as I posted this I see you now are on Patriot. I did not find a match for Patriot.

I suggest that you should first search for an existing issue and could consider to add to or start new Issue as Report an issue giving the correct information.