I have a FP4 that I purchased from Murena, the update showed up in the automatic update. It is 2.6.3, official, u
edit:
2.6.3-u-20241217455359-official-FP4
2 Likes
An issue with upstream Lineage OS 21 based on Android 14 matches the problem with e/OS U (Android 14): media apps like Spotify etc. used from the work profile (using āShelterā) in my case, will cause the launcher (Bliss or Trebuchet) to enter a lock screen / black / lock screen cycle. It canāt be stopped without restarting the phone.
Here is one link to the LineageOS issue: Work profile apps with media playback notifications make phone unusable (#7630) Ā· Issues Ā· LineageOS / issues / android Ā· GitLab however attempting to add additional information there for the developers caused the thread (and many other threads I attempted to link together since they are about the same issue) to be closed.
I believe this issue may be across many devices, so if other users report problems using a work profile (āShelterā or other) and having apps creating notifications causing display crash loops, then this is likely related.
In fact, if anyone already in 2.6.3-U can report successful use of Shelter media apps it would be helpful. I have not found any confirmation that work profile notification apps such as media players will NOT cause this issue, making it unusable.
1 Like
After making the update, my new Murena Fairphone 4 has a mobile network state of āDisconnectedā. My SIM card worked previously, and I can still text and make calls. However, my mobile data does not work, and I can only connect to the Internet using WiFi. In the top toolbar, the network icon appears, but there is no 5G icon.
- Fairphone
- FP4
- FP 4
- Version of /e/OS which existed previously: Unsure. I bought the phone new less than a month ago from Murena, but it was fully updated on the official version before I was prompted to update to this new version.
- Not rooted
Additional details:
- Iām using a Tello SIM physical SIM card (part of the T-Mobile network in the USA).
- I took the SIM card out and reinserted it. I restarted the device multiple times.
- The SIM card is enabled; mobile data is on. I changed the preferred network type from 5G to 4G to 3G (no change).
- I tried resetting the APNs to default as well as the network settings.
- I didnāt notice it immediately because Iām almost always on my home WiFi.
Iām hesitant to reach out to my SIM provider, Tello, since the service partially works, and it worked perfectly for weeks before I updated this brand-new Fairphone 4.
Any advice on how to proceed would be appreciated. This is a very new device, and Iām new to the community. Iām also not sure if Murena Support or Fairphone Support would be the best contact for further technical support. I really love the phone so far but would like to resolve this so I can use my phone outside of my home!
Thank you!
You could try to check APN settings 
2 Likes
Hi @Manoj
There seems to be an issue with Samsung devices. It would be great if you point the developers to the potential problem. It seems that most users have the problem that the bliss launcher does not start.
Sharing with the developers. What is the specific Samsung device code name where issues with Bliss Launcher are being reported.
One issue reported on:
Device name: Galaxy S5e
Device CodeName: gts4lvwifi
What are the other device codenames
Murena
pixel 5
redfin
/e/OS 2.5
Not Rooted
Xiaomi
Redmi Note 9S
Miatoll
/e/OS 2.5
Not Rooted
Xiaomi
Redmi Note 10 Pro
Sweet
/e/OS 2.5
Not Rooted
All working ok, Thanks.
I have now upgraded my three devices
a) Samsung Tab S6 Lite āgta4xlwifiā
b) Samsung Tab S5e āgts4lvwifiā
c) Samsung Galaxy S10e ābeyond0lteā
to /e/OS 2.6.3 U aka Android 14
The S5e upgrade worked by booting into the existing recovery (2.5) and applying the upgrade with adb sideload (aka known as dirty upgrade). Everything survived the upgrade.
For the S6 and S10e it was necessary to first update the recovery (using heimdal) and wiping the device (in the recovery). The adb sideload afterwards complained about signature check failing (which is simply to be ignored) and printed a few errors about some sort on incompatible partitions. But it worked. The devices booted into clean /e/OS 2.6.3 U.
I reinstalled on the S6 with the included Seedvault backup which I made from the S5e (which is my daily used tab). Most of the apps and their settings have been flawlessly reinstalled from the backup. Only Firefox gave me a problem as I didnāt found a way to move the bookmarks (which is the most important data in Firefox for me).
Other apps like K9 Mail or Wireguard have been restored without their settings but luckily those have their own backup option (mostly manually in their settings).
The reinstalling of the S10e, which is my daily used phone, from the Seedvault backup worked also mostly flawless. For some reason a few minor important apps have not been reinstalled.
Only WhatsApp and Signal needed some extra effort. For WhatsApp a manual copy of the Android/media/com.whatsapp folder to a SD card and restoring this folder before opeing WhatApp the first time worked. The backup has been detected and everything was just as on the old version.
For Signal it was easy as Signal offers its own backup which is done to my Nextcloud. The restoration worked without problems.
I identified the following issues with 2.6.3 U:
- On the tablets the character selector popup (when long pressing a key on the keyboard) is a bit misaligned. But it is still usable.
- UnifiedPush is not working for me. I have the ntfy app installed and it receives the topics I subscribed to. But Element X is not able to register to my own ntfy server. If I enable UnifiedPush in /e/OS settings, it connects to ntfy.sh. I havenāt found a way to convince Element X to choose the ntfy app with my own server as provider.
But not having this is not a big problem for me currently.
Iād like to see UnifiedPush be fully integrated into /e/OS. At the moment, itās not usable.
Iād also like to see SeedVault backup be supported by more apps to backup their settings.
Having said that, Iām happy with the new /e/OS version and as always when a new version for my devices is available and working a donation is on its way.
Many thanks to the developers and the whole /e/ team.
1 Like
As others mentioned (@ccgauvin94 here and @Melinoe here eSIM Activation Error - Murena Mobile) I also canāt use my second SIM (eSIM).
Answering @aibd summarizing in the thread above:
- I donāt own a Murena FP4
- The problem isnāt here with the last v. 2.5-t.
- Now Iām on 2.6.3-u-20241217455359-official-FP4.
- My italian carrier is VeryMobile (virtual, based on Wind 3)
- My phisical SIM works
1 Like
That fixed it! Thanks so much @mihi!
The problem was that there werenāt any APN settings. When I went into those settings, I got the message about there arenāt any APN settings associated with this account.
I manually added the APN settings for my service provider Tello in both the name and APN fields. Then, the mobile data status changed to āConnectedā and the 5G icon appeared next to the network icon in the top tray.
This is the first time I needed to add the APN settings manually. Typically, the physical SIM card would do this automatically as is what happened with my previous device and the Fairphone 4 before the update. My best guess is that the operating system upgrade reset it.
Iām not sure if solving this has any relevance to the e-SIM issue, but Iām glad I posted here.
3 Likes
That is probably correct.
The APN set by /e/OS in Android 13 (T) should come from apns-conf.xml where the carrier Tello is āNot foundā.
Fritz!App Fon V2.12.4: The app does not respond to incoming calls.
Fairphone 3+ (FP3), Bootloader locked, not rooted.
Current Version: 2.6.3-t-20241217455358-official-FP3
Murena needs to pull this update immediately for FP4 users, it is critically broken and will seriously disrupt their lives if they are using an eSIM.
I currently cannot make or receive phone calls, texts, or use data outside of WiFi. In addition to the obvious ramifications of not being able to be contacted/contact people (such as my wife and kids), I also cannot:
- Log into my bank account (2 factor SMS)
- Log into my work email (Duo OTP requires SMS)
- Call anyone to help resolve those things
Basically my whole life is disrupted until a physical SIM shows up in the mail 3-5 business days from now, at which point I have no evidence, only hope, that it will work.
Unacceptable for an OTA update for a $500 phone purchased from Murena directly.
1 Like
Can confirm, adb sideload worked also for me. Took quite a while so be patient
one question jabsu, can you move the icons at the bottom of the screen? i tried it and it doesnāt work on my pixel 7a. thanks slim
I can, it works as expected. No problem to report from me.
Did you check if your APN settings are correct? A user above on a FP4 found they had been removed, and after manually reading them their network worked again
Unfortunately, canāt access APN settings until there is a valid SIM.
- Vendor Name: Google
- Device name: Pixel 4
- Device CodeName: Flame
- Version of /e/OS or Stock which existed previously: 2.5t
- Not rooted
OTA update failed / unavailable
Performed āDirty-Upgradeā as outlined by @piero (no issues, all data retained)
All seems fine, file transfers via USB still works (Mac)
1 Like
Teracube_2e
e_emerald-user 12 SQ3A.220705.004 eng.root.20241217.030444