43

[ROM][10.0][UNOFFICIAL] LineageOS 17.1 for Unihertz Atom L and XL [Alpha] [2022-...

 2 years ago
source link: https://forum.xda-developers.com/t/rom-10-0-unofficial-lineageos-17-1-for-unihertz-atom-l-and-xl-alpha-2022-01-31.4171407/page-12#post-86400509
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
It looks like there's no easy solution: This looks odly familiar to the things PeterCxy did with ims in his old build I based mine on.
I think ims seems not to be working at all in my builds therefore the correct settings cannot be supplied to the system.
Sadly even if I tried to implement something myself I don't have a contract to properly test VoLTE and everything connected with it.

Sorry.
Wonder if I'm out of luck with Lineage entirely on this carrier, regardless of phone. I'd considered getting something with mainstream Lineage support (a Pixel most likely) for compatibility reasons, but now I fear that would be a waste of money.

I don't fully understand what this documentation means, but it sounds as if it is a problem at the AOSP level. If this is the case, I might as well suck it up and just use the stock ROM on the phone I already own.
Wonder if I'm out of luck with Lineage entirely on this carrier, regardless of phone. I'd considered getting something with mainstream Lineage support (a Pixel most likely) for compatibility reasons, but now I fear that would be a waste of money.
The Pixel has good community support. Also the kernel is opensource which helps a lot. The Unihertz devices (along with all mediatek devices I guess) have more of an "enthusiastic" support. I do this entierly in my free time.
I think as Verizon is not such a small company that it will work on the Pixel.
I don't fully understand what this documentation means, but it sounds as if it is a problem at the AOSP level. If this is the case, I might as well suck it up and just use the stock ROM on the phone I already own.
It's about a change in the approach of serving the required settings of the telephony subsystem to the system(-apps). It started in Android 6 and seems to have gain broad acceptance around A8 or A9. The apns-conf.xml is prior to that and only serves as a fallback.
If I understand this correctly the sim card (of Verizon at least) seems to have signature to it that forces the system to use the new approach and the fallback to mcc/mnc seems to be not compatible.

The next logical approach for me would be to consume all my holiday leave, buy a plane ticket, travel to your (remote) area, get a Verizon contract and start debugging the device. Or find someone who is capable to do that.
I do this entierly in my free time.
And I'm quite grateful. Thank you for all of your time and effort.

I think I'm going to look into other carriers. Lineage had mobile data on T-Mo previously, and given that I can physically see Verizon broadcasting here, that might be an option as well.

report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK