Feedback for v3.1.1

/e/OS Smartphone Operating System Build Feedback
147

Sim card was in phone - I’ve never removed sim card during update on any phone in more than 10 years of flashing phones on android.

148

I left sim in. Especially with eSIM it is bigger job to remove it and the reinstall and I need to contact my ISP to register the new eSIM. Physical SIM is easier to remove, but I don’t think that is helping if the problem is with IMEI as it seems to be.

149

Instead of only rebooting the phone, for those of you who have SIM issues … try taking the SIM card out (if not an e-SIM), reboot phone without SIM card, then turn off phone, reinstall SIM card and turn on phone.

1 Like
150

I left the SIM in while upgrading. I had tried booting the phone without the SIM and had no effect.

I now tested this exact sequence and no effect.

151

Unfortunately doing this had no effect on the issue.

152 
Vendor Name: Fairphone

Device name: The Fairphone (6th gen.)

Device CodeName: FP6

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

Device Not rooted

Version 3.1.2: Same issue as other FP6 users, physical SIM rejected. IMEI code 004400152020000, which is wrong. Carrier Telia Dot (Finland).

Tried:

  1. Several reboots: no effect
  2. resetting mobile network settings: no effect.
  3. Power off, sim card out, restart without SIM, reset mobile network settings, power off, sim card back, restart: no effect.

Has anybody opened an issue in Gitlab for this?

1 Like
153

Vendor Name: Xiaomi

Device Name: Redmi K20 / Mi 9T

Code Name: davinci

Version of /e/OS which existed previously: e-3.0.4-t-20250710507811-community-davinci

Device Not rooted

Vendor Name: Oneplus

Device Name: 7 Pro

Code Name: guacamole

Version of /e/OS which existed previously: e-3.0.4-a14-20250709507533-community-guacamole

Device Not rooted

Vendor Name: Samsung

Device Name: Galaxy S8

Code Name: dreamlte

Version of /e/OS which existed previously: e-3.0.4-s-20250711508139-official-dreamlte

Device Not rooted

As always, all devices work perfectly. :slight_smile:

Installation without error. :+1:

a big thanks to the development team for the hard and excellent work. :ok_hand: :slight_smile:

155

Haven’t opened one yet, I don’t know which project that’d fall under [I’m quite new to all of this], but I pulled logs via syslog from the phone that I could provide.

I honestly don’t really know what I’m looking at, the only thing that stood out to me was this in the modem logs:

Excerpt:

09-04 17:53:30.669 D/NRM-C-1 ( 3392): onRequestNetworkRegistrationInfoComplete result: 0, info: NetworkRegistrationInfo{ domain=PS transportType=WWAN registrationState=DENIED networkRegistrationState=DENIED roamingType=NOT_ROAMING accessNetworkTechnology=NR rejectCause=0 emergencyEnabled=false availableServices=[] cellIdentity=CellIdentityNr:{ mPci = 2147483647 mTac = 2147483647 mNrArfcn = 2147483647 mBands = [] mMcc = 244 mMnc = 91 mNci = [REDACTED] mAlphaLong = Telia FI mAlphaShort = Telia mAdditionalPlmns = {} } voiceSpecificInfo=null dataSpecificInfo=android.telephony.DataSpecificRegistrationInfo :{ maxDataCalls = 16 isDcNrRestricted = false isNrAvailable = false isEnDcAvailable = false mLteAttachResultType = 0 mLteAttachExtraInfo = 0 NrVopsSupportInfo :  mVopsSupport = 0 mEmcSupport = 0 mEmfSupport = 0 } nrState=**** rRplmn=24491 isUsingCarrierAggregation=false isNonTerrestrialNetwork=TERRESTRIAL}

Based on the latest in this thread it seens like it wasn’t supposed to roll out.

EDIT: Was confirmed that the 3.1.2 is not supposed to be in the stable channel here: Install e/OS on Fairphone 6 - #82 by mihi

I’m hoping that there is a workaround to restore functionality soon™, I really don’t wanna go back to googlefied Android. :slight_smile:

EDIT: It also seems that specifically Telia blocks the access with that IMEI. My carrier is Telia FI

1 Like
156

Not just Telia, DNA blocks too, interestingly Elisa doesn’t though.

1 Like
157 
Vendor Name : FairPhone
Device name : FP6
Version : 3.1.2-a15-20250828521531-official-FP6
Device Not rooted

When the phone starts up, SliderSwitchHandler app crashes

158

I had the same issue on my S10e beyond0lte and was starting to panic, thank you so much, worked like a charm after that :pray:

159

There seems to be v.3.1.3-beta created on gitlab. Hopefully it solves this issue.

2 Likes
160

FP5 official, upgraded to v3.1.1, without any issues and nothing missing, so far.

Good to hear, that further progress is in the making:

1 Like
161
  • Vendor Name:
    Google
    Device Name:
    Pixel 7
    Device CodeName:
    panther
  • 13

3.1.1-t-20250828521480-official-panther

e_panther-user 13 TQ3A.230901.001 eng.root.20250828.120404

  • Not rooted

OK

162

I had the exact same issues with App Lounge on my Xiaomi Poco X3. See my post #92 and #99.
I’m quite sure that it is not related to the device, but a problem on the server side which seems sot block some ip adresses or location. I found a workaround: using a VPN and connecting via the Andora country, App Lounge could connect and install/update apps.
FYI, yesterday ip adresses from Belgium or Germany were rejected for some reason. A the time of writing this post, my App Lounge work normally without need to pass through a VPN. I guess that the problem is solved on the server side… or that Belgian ip adresses are now reallowed for some reasons…

163

Many thanks.

I was just exactly in the same case with the same device.

164

Man, I waited for over 1 month to finally setup my new FP6 and relock the bootloader, and now v3.1.2 is not a stable version?? I also have wrong IMEI 1 and 2 but phone calls and sms seem to work so far. However battery seems to drain faster than on v3.0.4. Still need to test a bit more though.

165

Just updated from OTA. I quickly checked the camera app to test some of FP6 specific issues:

  • Zoom not working for pictures. (Zooming is possible, but after zooming in and out for a bit the app crashes)
  • Low microphone while recording videos. (Although this is fixed on the camera app, third party apps still have a lower volume, although not as bad as before.)
  • No option for 50 MP pictures. (You can set the setting to take pictures at 50MP, but as soon as the app is closed the setting is reseted back to 12MP, which is not really usable.)

I really hope these issues can be ironed out on the next release…

1 Like
166

Regarding v3.1.2 being supposedly a testing release that slipped into the stable branch, does it mean it was signed with a testing key? If yes, does this mean we’ll need to restart from scratch and reset the phone in order to install the next stable release?

167

Good news A15 official for FP5

Thank you