Ho. Mobile italy uses vodafobe network works fine
When I do a little web searching, I find the same news everywhere. Samsung uses proprietary VoLTE implementation, which is hard to reverse engineer. There seems to be no one planning to fix this:
https://www.reddit.com/r/LineageOS/comments/t5v2dw/helpvolte_support_on_lineage_os_181_samsung_s10/
Although that might change as 3G is getting shutdown in Europe these years. It looks like at the latest, 2025 there will be no country that has it. And hence Samsung phones will be nonfunctional if they have a custom ROM.
https://blog.telegeography.com/3gs-sun-is-setting-in-europe
I feel new potential e/os users would appreciate a warning before investing a lot of time and money in a phone that might now work now and definitely won’t soon.
What phone do you use?
If you have a Samsung phone and the VoLTE works. Please share more. You might have the solution many people need!
I’m sorry you had to go through all this. What a freaking hassle. I almost got a Samsung while they still sold them for the US market in the /e/OS online store. I’m glad I delayed my purchase and ended up with a phone without this issue. I barely lucked out.
I hope you get your situation worked out one way or the other. I hope your life is good besides your phone issue!
Thanks for your concern.
Everything worked out for me. No hard feelings. I’m still very grateful for the work being done here. It’s very important to have a opensource ROM that is user friendly, and this is the closest I’ve seen to it. I suspect there is enormous amount of work going on to make it happen.
Fortunately for me I’m only out $2 USD for some tracefone SIM cards. All the weeks I spent working on this are not a complete waste. I now know how to install e/os and reinstall the original firmware. I also know how I like to configure my custom ROM best. When I get the right phone, next time everything will be much smoother as a result of all this work. So in the end, the mistake was actually valuable.
But this might not be the attitude for others, hence the reason I am attempting to get the developers to make a clear warning for the Samsung phones. Unfortunately, I haven’t yet been successful.
Some of you may or may not have come across this issue and I can only speak to Motorola phones but if your phone has never been on a given carrier before you install /e/ or any alternative, de-Googled OS WITHOUT INSTALLING THE GOOGLE PLAYSTORE, you will not be able to get on the network - I have to assume that this is some sort of agreement between Google and the major carriers. The workaround is to install the stock OS onto your phone or a different OS that allows you to install GAPPS (never had any luck installing GAPPS with /e/), connect to your carrier, make and receive a few phone calls / make and receive some texts, connect to carrier data and make sure everything is working, then install /e/. I had this issue with a new Motorola cellphone when I installed /e/ before I had installed the sim card and I just had that issue again when switching my phone from AT&T to Verizon. In both cases, the issue was resolved by using the Motorola recovery software to install the stock ROM, putting the phone on the network and reinstalling /e/.
Regain your privacy! Adopt /e/ the unGoogled mobile OS and online services
I’m aware of this problem, but my experience is different than yours - and, it’s not a general problem with /e/OS or other deGoogled custom ROMs, but depends solely on the 4G LTE frequencies supported by the device and carrier, and the carriers’ network and APN settings. You do not need a stock Android with Google Mobile Services, Play Store and other GApps to set it correctly.
LineageOS contributors mentioned it too, placing a call in stockrom somehow enabled VoLTE with the non-stockrom (if the device is generally able to do so). The technical details evade me, but there are a few identifiers you send on IMS registration that a provider can use to filter
I fall into that “screwed by Samsung VoLTE” due to proprietary nonsense category. I presently have a Samsung S9 Dual Sim International SM-G960F running on LineageOS 17.1. I was using LineageOS just fine until AT&T dumped me (via MVNO Red Pocket Mobile) last year in spring. After that I was forced to T-Mobile as my effort to convert to Verizon failed. T mobile covered has lots of holes if you aren’t super urban and my service quality sucks to the point where I’m compelled to change.
Back in 2022, after a very disruptive and lengthy service interruption, and despite me scouring the internet forums, it was unclear that there was this Samsung / VoLTE relationship. Since then, I mistakenly bought another Samsung (loving the form factor) S10e and started the bootloader unlock and the like only to discover that the SM-970U or U1 aka G970U didn’t work with VoLTE. I found that there was an unofficial build with the US versions (which is a Qualcom Snapdragon processor), but it was reported to have the VoLTE limitation. My workaround was going to be to try to find another dual sim Samsung phone (like I did in the past with my international Dual Sim Galaxy S9), until I FORTUNATELY found THIS THREAD. I have read another thread that suggests that this VoLTE nonsense is a matter of Qualcom (Snapdragon processor manufacturer) wants X number of dollars or cents for licensing but somebody didn’t want to pay (so we’re subsequently screwed as hardware owners). I have since decided to try the Pixel 4a (maybe 5G version) and/or the Moto G7 Power. I intuitively hate Google for all of their privacy violation and bad political influence and techocrisy but now it seems I have a reason to start hating Samsung as well. Ironically the harder they squeeze it seems the more determined it makes me to want to be free of their BS. Although I think the carriers also have quite a bit to do with this micromanagement and planned obsolescence as well. So yes, please put big big big warning labels for us dumb and lazy and entitled Americans that think that we have a right to have custom Samsung ROMS.
I can’t say that I have a solution but I’ve been running LineageOS 17.1 on a Samsung S9 Dual Sim international model 960-F on T-Mobile’s network through Red Pocket after AT&T gave me the boot. The interesting thing is that under “Mobile Network” there is NOT a menu option for VoLTE, but rather it defaults to “Preferred network type LTE (recommended)”. I perceive that T-mobile may have engineered a workaround, maybe being the underdog of the big boys as far as carriers are concerned. After all, it’s still 4G LTE tech. As I understand (or infer or perceive) this VoLTE is more or less a matter of coms protocol and the carriers have some latitude to manage these at the network level. Xmodem, Ymodem, or Zmodem. It’s all 1’s and 0’s and a bunch of crap. Give me my C64 again. The Delorian was probably much better of stuck in 1985, 1955, or maybe even 1885. The fate of all mankind, it seems, is in the hands of fools.
I live in the countryside. So many holes in the T-Mobile network. I wish I could use them.
After all the hassle, I’ve decided to shelf this project for now. I’ll be back in a year or two. I’m only interested in switching if I can have quality hardware that just works. This will be my only phone. I cannot mess around with service interruption.
I hoping either the Samsung issue gets sorted out or even better we get some ROM developers in the US, who make this happen.
Motorola is having a sale on the 2022 Edge which has a Lineage OS and, I think, an /e/ ROM as well.
Speaking of service interruption, I am closely considering switching my Pixel 5 over to an ATT MVNO
I know, I know. But I was sort of locked to Mint due to my use of a Tercube 2e. Now that I have moved on, I really would like the better cell coverage ATT offers here. Mint/T-Mobile really is routinely terrible for us.
Is Cricket ok for pixel and e/ os users? What is the process like switching a phone with an e-sim?
I would recommend Patriot Mobile MVNO. Not only do they support all major carriers but dual-sim phones can use their multi-carrier service; where, whichever carrier has the better signal, that’s the one your phone will use. Their customer service is, literally, the best in the industry - they spent hours on the phone with me to help me get my /e/ ROM’ed phone on the network while I was using their AT&T service. They are only slightly more expensive then most other MVNOs (a lot more expensive then the $10-per-line XFinity offering) but, for me, it’s worth it to have a de-Googled phone.
A gentleman I know who roots and mods phones for a living told me that he has a much easier time getting his phones on the Verizon network then AT&T so I am using Patriot Mobile’s Verizon service right now, and he’s right - a de-Googled phone gets picked up on the Verizon network, no problem.
Having seen the issue first-hand, I must agree with him that AT&T and Google have some sort of agreement going on which, apparently, Verizon isn’t a part of.
All, please keep the discussion away from politics. This is a list which has important information.
I am editing the tables to add Verizon and US Mobile (both their Verizon and their T-Mobile SIMs) for the USA as “working” and removing Verizon from the “doesn’t work” list. Verizon’s CDMA network has been retired a few years, their LTE network has no issues with /e/ or any Android-based ROM.
keep in mind beyond the carrier letting the device onto its network, feature-compatibility can be device-dependent - the [LIST] Features list for devices - VoLTE/VoWifi/Wificall per-device carrier compatability list goes into the details.
Excuse me, but PeteFoth’s note should also be flagged and for the same reason.
Edited the first post to update the list of carriers that work in Japan. FWIW I’ve created a topic about how /e/OS works on FP4 in the country: