Feedback for v3.1.1

  • Vendor Name : Samsung
  • Device name : S10+
  • Device CodeName : beyond2lte
  • Version of /e/OS or Stock which existed previously : 3.0.4
  • Is the device Rooted / Not rooted : rooted

I had a similar issue than another member on a S10e which is that the update process was stuck at “95%”.
I restarted the phone (power + vol up) and voilà
All is working fine except the everlasting bugs known on /e/os for this device

“SIM1 not allowed”
@RVzapd It’s worth going into the Settings > Internet > (Select your SIM having problems) and check the IMEI displayed there, it’s likely that you’ll see the same IMEI as me. [004400152020000]

The error “SIM X not allowed” always indicates that the Carrier allows registration of the device in their network, but not the SIM card itself and it’s information (read phone functionality or mobile internet).


@aibd Rebooted again and the issue still exists, IMEI codes are the same (004400152020000)

Happy to provide any logging if needed, just need some guidance on how to obtain them.
As mentioned the observation is that the bootloader still displays the correct IMEI (at least for SIM1; SIM2 is not displayed)

All fine on Pixel 5 redfin after update from 3.0.4 to 3.1.1 official.

I suspect the camera app to still not work, I deleted it and switched to an GCam port long ago since the e/OS camera app is not able to make pictures, they are blurry in any setting.

As usual there were problems with App Lounge not updating apps during the last months/versions, that is not a problem right now but I guess it could reappear anytime, so fingers crossed.

Hate to point the finger but since Murena was so eager to talk about how they value fast security updates and how they want to shorten the update cycle I have to say that since then it has actually prolonged, I was on June’s Security Patch level until today and I’m still running Android 13 on an officially supported device, so yeah, it’s the plan for the future, I know, so Godspeed and all…

Anyhow, many thanks to the team!

  • Vendor: Murena
  • Device: Murena Two
  • Previous version: 3.0.4
  • Not rooted

Update to 3.1.2 went smoothly, no issues found yet. The update process took even more time than the last updates, about 2 hours until I could finally restart.
3.1.1 never appeared on the updater page.

Clearing the storage of SliderSwitchHandler fixes the slider until the next boot for me.

IMEIs also show the same thing for me, but Calls and SMS work for me.

2 Likes

I’ve rebooted 7 times already (because that is first fix I try in such a scenarios) and latest was after your message. Does not help at all to the situation. So my situation is exactly same as @Raxay . I am also happy to provide any log or information as needed, but I don’t know where to get them.

P.S. I needed to wait with my reply, because of the slow mode at the forum. So if more realtime responses benefit, maybe some realtime chat is good idea?

EDIT 12:53 GMT+0:
Did reset the mobile network settings and one of my two sim started to work. eSIM does not work, but physical sim got the connection. IMEI didn’t change, so I am surprised that physical SIM started to work

EDIT 13:04 GMT+0:
It worked like 10 minutes and now stopped working. So that wasn’t working solution at the end.

FP6 SIM / IMEI failing on e-3.1.2

This is an understandable problematic issue. I wiil try to DM you … however

I have no knowledge of the actual problem but I would be inclined to do

Settings > System > Reset options > Reset mobile network settings.

Missed your first post in the rush :slight_smile: But yes, I have the exact same problems, did all the same checks and tricks. Let’s wait and see.

Did today. Installed and working great. Thank you.

FP6 SIM / IMEI failing on e-3.1.2

I tried a DM to @satse (because of new user timeout) he says (paraphrase).

The resetting mobile network did open the physical sim card, but it didn’t open the eSIM card.
It stopped working after about 10min. So the solution wasn’t really working, as the ISP rejected it after a little time, even if it initially worked. IMEI didn’t restore.

I would be inclined to do

Settings > System > Reset options > Reset mobile network settings.

Just tried that, unfortunately no dice still showing the incorrect IMEI numbers.
Like I wouldn’t even mind doing a factory reset, if the issue is fixed thereafter but reinstalling everything just to have the same issue doesn’t seem worth it and I doubt it would help with the IMEI codes.

EDIT #1: Related thread was opened for this problem specficially: Sim 1 Not allowed in e/os 3.1.2 ?!?

1 Like

Vendor: FP
Device name: FP5
Previous version:3.0.4-t-20250709 507786-offical-FP5
Not rooted.
All is well. Android v remains A13.
Patience pays off for the OTA! Great work by the team.

For me the factory reset (via Settings->System->Reset->Erase all data (factory reset) did not help with this issue.

*sees update finally released*
Three dot one dot TWO?
*checks forum*
I think I’m gonna skip this one guys

6 Likes

please, which version ? A13 or A15 ?
Arnaud

What’s your question?

because we are waiting A15 for pixel5 and online there is only A13.

Vendor Name: Oneplus

Device name: 9 pro

Device CodeName: Lemonadep

Version of /e/OS or Stock which existed previously: 3.0.4 A14

Is the device Rooted / Not rooted: Not rooted

Updated to 3.1.1 A14. Update sucesfull. Everything working ok so far. Thank you for your hard work!

Also experiencing the SIM card issue with v3.1.2.

My second day on /e/OS (FP6, bought from Murena’s webshop) and I’m seriously looking into re-googling the phone and installing Android. However, I’m afraid I would mess it up even worse (or make the warranty void…?) by doing that.

For those with SIM card issues … did you leave the SIM card in the phone while upgrading? Or did you first remove it and then got issues when re-installing it?