Vendor Name: Murena
Device name: Murena 2
Device CodeName: Murena 2
Version of /e/OS: 2.0 T Stable 2
Is the device Rooted: No
Since the update I can no longer make calls, nobody understands me or can’t hear me at all.
Sim card removed and reinserted. Smartphone switched off. And tested the Fossify phone app, same problem. I own a second Murena 2 and will test it with it later. I hope there will be a patch soon.
Any other Murean 2 users here with the same problem?
Thank you!
I have updated my FP2 from 1.21-r → 2.0-r successfully too and so far I’m not seeing any issues.
As for the security date, the Android security update is still reported as February 2024, but that is to be expected since Google has stopped doing security updates for Android 11 (R).
If you stack two app icons together you get a drawer, or do you mean something different?
Hello,
tried lawnchair14 and it is already gone away from my device, lol.
Better for me the launcher you suggested or, it is similar, simple launcher from fdroid.
If anyone interested, the pic is showing my home, e os t v2.0.
I mean something different. An app drawer is a certain area separate from the home screens (usually accessable if you swipe up from your home screen) which shows all installed apps, lets you search for apps, group them, pin to home screen, etc. See: What Is an App Drawer in Android and How to Use It Optimally
Thanks for asking. How are we suppose now, by removing function on the button, to access the app list to permit to edit screen’s icon ? I di have accees via parameter to all apps installed, but it is not possible from there to create shortcut on the screen. Any known work around ? Will the ream patch this issue ?
I have a Fairphone 5 on Version 1.21, when i start the update installation the Updater app stops working. I tried clearing cache and storage of the updater app, but that doesnt change anything.
Thanks for the hint. I will have a look at your recommendation of Lawnchair 14 fork by Gooler: I don’t like BLISS neither, as I miss the widget possibilities etc.
I wrote:
if 2.0 for the FP2 did not receive any security updates and apparently also no (functional) updates of apps […]
I stand corrected. Thanks to @mihi who informed me that the button was meant which previously only switched between video recording and snapshot and now implements a third option (QR scanning), I believe that the topics and issues mentioned in the v2.0r release notes indeed also apply to the FP2.
Kind regards
Ingolf
Hello,
about security, i think screenshots are comprehensive and eloquent enough, that’s fine with me.
Being old or not updated doesn’ t necessarily mean not safe, at least not always 
In this case, it is just a simple launcher, able to do its job.
Yes, I’ve tried Simple Launcher as well.
It was quite good though had some performance (occasional lag) issue on my device.
I would say whichever is fine (other than I can’t get used of Bliss Launcher LOL).
Right, you have a point.
My logic is if the device is anonymous, the less targeted the device is by attacks; therefore latest security update isn’t 1st priority (contrary to what most of “cyber security experts” says)
Example: On G-bloat ROM, people get latest security update while privacy is compromised because of G-bloat tracking 24/7 with wifi-triangulation, G ID & matching of device finger print etc.
Meanwhile on Degoogled, none of these happen while security update is slower.
though I understand that people have different priorities.
Vendor Name: Asus
Device name: Zenfone 8
Device CodeName: sake
Version of /e/OS or Stock which existed previously: e-1.19.1-s dev
Is the device Rooted : no
Major update from A12 to A13 using recovery method did go without any difficulties. So far, with the T Build, /e 2.0 everything works fine, no issues.
I like the new Bliss launcher with the improved smooth animations as well the standard icons look more modern. Nice!
Also moving icons around for reposition is much better now, no aggressive screen cycling anymore.
I will be transferring candies to /e.foundation - keep up the good work!
Vendor Name: Fairphone
Device name: FP3+
Device CodeName: FP3
Version of /e/OS previously: 1.21 t stable
The device is: Not rooted
The update went fine and in general, I did not run into any issues, other than …
This is the only issue I found so far as well. I also use 2-button navigation, and with 2.0 the gestures became useless.
If I switch from 4 x 6 to 4 × 5 icons, I seem to lose a few icons (and groups). Most notably the Settings app’s icon 
…
Since the upgrade to V2.0 (OnePlus 6) I notice that the battery seems to drain a lot faster then the previous build.
Battery usage shows Android System draining the most.
I managed to fix this by clearing Bliss Launcher’s cache and data storage in Settings ↦ Applications.
Hi Luja,
I tried for you: I downloaded version 2.O in 4G for my moto G5 cedric and after it installed correctly. The wifi works again!!! Wonderfull.
The photo app is even faster!
The only weird thing is the disappearance of the native /e/OS application for navigation. I put Osmand instead.
The latest update to v2.0 is failing on my Moto G7 (Not play or plus), when I need to restart the device it simply remains with the screen off and never turns on again. I’ve waited for over 3 hours and it did not work, I have to force shutdown it and when I turn it on again it’s still in v1.21.
This is the same no matter how I try to update. I’ve tried the OTA update, importing the update zip from SD in the updates interface, loading from SD under /e/ recovery and adb sideloading on /e/ recovery and all of them end up the same.
If someone knows a way to extract logs during this time or know what could be the problem I’d appreciate.
There is an Issue with river build and has been already reported. The team is checking on this. Have requested them to withdraw the build from the servers. Will update if there are any inputs.
Requesting users of Moto G7 river if you have reverted to v1.21 pl can you do the following
adb root
adb pull /cache/recovery/last_log
or
logs just after the reboot for the update with
adb logcat
Attach the log files to the issue created here