Hello everyone,
today, I installed the official update 3.1.2-t-20250903523043-official-two for my Mureno Two smartphone. Since then, I have been unable to make or receive calls. Unfortunately, restarting the device did not resolve the issue. I hope there will be a bug fix soon. Would a downgrade with minimal risk be possible here? If so, how?
Thank you.
I found a solution to my problem. I set the APNs to default and then configured them manually according to the provider’s specifications! Nevertheless, it could have been caused by the update!
Who is your service provider and can you message me the APN settings. I can pass it to the team to check.
The problem has reappeared since the update to version 3.2, but this time the workaround no longer work
you’ll have to probably file this with a two label to the backlog, give your mcc / mnc ids (carrier).
There’s no apn / telephony issue yet (for sms, but that seemed more carrier related than device related).
One way to resolution is adding your exact mcc / mnc settigns to the apn xml config shipped with the build. For an example how this looks like see this thread. Your settings will be wrapped in a xml line and added.
Though why you can’t save apn settings, maybe someone else can chip in who’s seen that behaviour
This thread (where carrier specifics were given) Murena Teraube 2s doesn't work with USmobile? (warp) includes interesting images showing that APN are impossible to change due, apparently, to the phone not being on Verizon “List of devices” … or … “within their network”.
The problem with the calls is getting more and more absurd.
I have a new workaround. I have to swap the SIM card for any other card, and then it works again. But simply switching off the phone or removing the SIM card doesn’t work.
Can anyone make sense of this?
Sorry, not at present from the information given. In the thread I just linked we did try to apply a little “science” so that the OP could eventually find a solution. Would you be prepared to share your carrier name and an idea of your geographic region?
Something of an edge case, but FYI, if your carrier has changed APN and the publishers of the “AOSP APN presets” are not aware, it is possible that each update might cause an APN fail.
| DE | sim.de | uses 1&1-network |
|---|
new ex drillisch / “5g” 1und1 sim? those have a mcc mnc 262 / 23 and made it to the a15 branch of the apns-conf.xml.
/e/OS needs to backport to v1-t too for a13 devices like the two.
Can you force choose smartmobil entries? same settings, those are in a13.
I have no technical insight why you can’t save the apn settings. mcc / mnc mismatch? did you use 262 / 23?
fyi @aibd: there was a repo shift this week on apns - lineage moved apn conf xml from a big xml in the vendor prebuilts into a sliced-per-country dedicated vendor repo. At the very least it makes merge requests to the repo more approachable. It’s backported to all active lineage versions