I pushed the murena image via “adb” to the root folder of the internal storage, another time to the “Download” folder, but in both cases only the “adb” option appeared to “Apply Updates”. So, I did not download the image because my wifi was not working, but I think the way the image is obtained is not relevant.
1 Like
System update files might be downloaded to a different partition which doesn’t have enough remaining space.
This is just a guess, you might try to check the Updater if there are still old updates which can be deleted.
Old system update files will remain if updates are not deleted after the installation, see Updater settings (‘Updates nach Installation löschen’):
1 Like
even if you downloaded the file on the phone ?
this is expected displayed in the terminal
Vendor Name: Fairphone
Device name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: v1.20-s-stable to v1.21-t-stable
Is the device Rooted / Not rooted not rooted
Some Apps, e.g. DAVx5 or DWD Warnwetter shows me multiple times, that they have no network connection. After two days a lot of notifications come on my phone and all Apps work fine…
Hi, somehow the upgrade to T is not showing up in my Murena Fairphone 3+. Any ideas why?
EDIT: Solution was to first update to v.1.20 - then the upgrade to 1.21 immediately showed up. Thanks for the hint @mihi
Upgrade went smoithly! Thanks a lot to the /e/ Team!
Vendor Name: Fairphone
Device name: Fairphone 3+
Device CodeName: FP3+
Version of /e/OS or Stock which existed previously: v1.19-s-stable to v1.21-t-stable
Is the device Rooted / Not rooted not rooted
Thanks for any suggestion!
Update 4 April: The team will be releasing a v1.21.2 build for the Murena one which will have a patch for the no wifi issue. Will share the ETA for this release.
The build specific for the Murena one has been released. Read the complete details here
4 Likes
The reason might be that it is only offered when on v1.20…
Atleast when you check the other users with FP3, their previous version was v1.20.
I guess OTA Upgrade is developed for a certain base version
3 Likes
Vendor Name: Fairphone
Device name: FP3
Device CodeName: FP3
Previous Version of /e/OS: 1.20-s (stable)
Rooted: No
OTA Version Upgrade to 1.21-t.
I can send SMS messages, but not receive them anymore
Edit: I am using dual sim, but after popping the secondary one I am still not receiving texts (that should arrive on the primary one)
UPDATE: After waiting for a while, the messages came through and now new messages appear immediately. Not sure what happened but all seems fine now.
No problem sending and receiving sms on my FP3.
Vendor Name : Fairphone
Device name : FP3
Device CodeName
Version of /e/OS or Stock which existed previously : 1.20-s
Is the device Rooted / Not rooted : not rooted
After two days of update, an old bug appear : “Unable to open the camera. Still use by another app? ID:0”
- Vendor Name - Google
- Device name - Pixel 6 Pro
- Device CodeName- Raven
- Version of /e/OS or Stock which existed previously - GrapheneOS
- Is the device Rooted/Not rooted - Not rooted
All appears to be working well. Thank you team for your hard work as always.
Today I saw that an e/os upgrade to 1.21 (I think) was available for my Teracube 2e Zirconia. Unfortunately after download and (trying to) reboot I got stuck on a menu from which I choose Recovery. This led me to:
Bootloader, Please connect your computer and use fastboot to interface with the device. Visit https://bit.ly/3t9tbFV for more information.
From that site I downloaded Platform tools on my Linux (Xubuntu 22.04) computer, connected the Teracube and tried to run Fastboot. Nothing doing, Fastboot does not start (permission to run as program OK). (Tried two computers.) So far I did not find a solution here. So I am stuck.
Any tips? Thank you!
First … https://doc.e.foundation/pages/install-adb
after that … we no longer seem to see the link containing:
" Ubuntu Linux: Set up the following:" in: https://developer.android.com/studio/run/device
Ubuntu is slightly different from Debian ofc … you might try (the equivalent of) https://packages.debian.org/bookworm/android-sdk-common.
/e/ documentation has another take https://doc.e.foundation/pages/insufficient-permissions
Vendor Name: murena
Device name: Fairphone 4
Device CodeName: FP4
Previous Version of /e/OS: 1.20-s (stable)
Rooted: No
OTA Version Upgrade to v1.21.1-s
I keep seeing the icon for “no voice connectivity” (as I undererstand it - never had this before) in the status line, though voice calls work fine incoming and outgoing
also the settings for voice calls and sms are greyed out:
neither can I select cellular networks manually:
I’m using a 5G eSIM from O2 Germany
besides this, nearly everything seems to work fine - I only have one more issue (but already since some releases): open camera nearly all the time shows a red square after tapping for AF worth lense 1 and sometimes really doesn’t focus well - other apps focusing fine with lense1, ooencamera works fine with lense 2
thanks for any hints… BR
Norbert
Thank you very much. Not very straightforward for my limited knowledge of these matters. I’ll study it again tomorrow.
But in the meantime: as the Teracube is not yet my first phone, I could do a clean install of e/os without losing much. But for that I would have to do something to the Teracube in bootloader mode to be able to use the e/os Easy installer again. If that is more simple I would prefer to do that.
Vendor Name: Samsung
Device name: Galaxy Tab A7 10.4 2020 (LTE) SM-T505
Device CodeName: gta4l
Version of /e/OS which existed previously: e-1.20-T
Version of Recovery which existed previously: e-1.20-T
The device is Not rooted
The OTA update 1.21-t went smoothly. The e-Recovery was also updated from version 1.20-t to 1.21-t as requested.
This would be a good solution … once you were sure all Search – “open” and “closed” issues were resolved.
We are yet to see (I think) a report from (in progress) – Easy Installer v0.21 (beta).
Meanwhile we see a CLI install from https://doc.e.foundation/devices/zirconia/official – back to Post #2
I am rather lost, but I tried to sideload v1.21 using the relevant file for Teracube 2e Zirconia from this page. However I stumbled on this error:
e/os failed to find update binary META/INF/com/google/android/update-binary
Enough for today. Will have another look tomorrow, but it is getting a bit frustrating.
Vendor name: TeraCube
Device name: 2e (2021)
Device CodeName: Emerald
Previous Version of /e/OS: v1.20.0
Rooted: no
I have too many LTE icons on the status bar.
This was not “the relevant file” for sideload … check out this post Murena One : v.1.21.2 release : with fix for wifi and bluetooth functionality - #5 by aibd regarding the “leading IMG” in the filename.
You will find a sideload ROM at
https://ota.ecloud.global/api/v1/zirconia/dev/ or
https://ota.ecloud.global/api/v1/zirconia/stable/
… depending on your build type.
1 Like