Samsung Note 3, SM-N9005, hlte: Bliss Launcher v1.18.0
Samsung TAB A7, SM-T500, gta4lwifi: Bliss Launcher v3.0.1-beta
Both updatet from v1.21, not rooted
Same here for the TAB A7
Samsung Note 3, SM-N9005, hlte: Bliss Launcher v1.18.0
Samsung TAB A7, SM-T500, gta4lwifi: Bliss Launcher v3.0.1-beta
Both updatet from v1.21, not rooted
Same here for the TAB A7
Updated to V2.0 on Oneplus 7t pro
Bliss Launcher v3.0.1_beta
Updatet from v1.21, not rooted
One small issue:
Failed to start camera preview:
And then the app hangs with:
Serious camera error
Isn’t dev and stable the same just different ‘bulid keys’?
@mihi, changes in stable are delayed compared to dev (to be tested by more users than just the test team)
i also think this.
Clean installation went smooth with no problems.
Using Ruthless Launcher for the moment. I’ll have a play with Bliss when I have some free time.
Thanks to the entire team for your time and effort
Edit- Bliss Launcher is awesome. Spent time setting up various folders and widgets. Second day in and I think Ill keep it. Great job team. Thanks
Update went well although slowly as usually (no complaints!.. just an observation). Didn’t have time to test well enough but seems to work well.
Only problem spotted so far is that the system navigation (System → Gestures → System Navigation) if set on 2-button navigation it doesn’t work (properly). 3-button navigation has no problems.
2-button navigation seems to work similar (?) to gesture navigation. I cannot say for sure as I dislike very much gesture navigation so I don’t use it.
I use 2-button navigation so the problem was obvious.
I was not able to spot any difference in the camera app behavior; only its icon has changed. Unfortunately still no support for all (2) cameras on the back which I really hoped would “magically” happen. I thought /E/ would switch to (LineageOS) Aperture when the announcement about the new camera app was made.
Thank you very much to the developers for their efforts and to Murena for making this ROM possible!
I’m looking forward for the update to 2.0 for my daily driver as of now (S9+).
Device: POCO X3 NFC, NO ROOT, Updated through updater, using Trebuchet as default launcher
Haven’t found problem so far other than…
Painfully slow download as I kept getting disconnected almost every 3 ~ 5 minutes.
It also happened with manual download that I had to use some sort of download managers (doesn’t happen like that with downloads from other places).
Therefore, please let the updater automatically resume upon disconnect (this way, we won’t have to tap “resume” every 3 ~ 5 minutes)
2-button navigation, for some reason, is misbehaving after the update. So I’ve changed to 3-button (as someone else already mentioned about it)
Thank you for your work.
Vendor Name: Motorola
Device name: Moto G 5G
Device CodeName: kiev
Version of /e/OS which existed previously: e-1.21-t-20240325389105-dev-kiev
Version of /Recovery which existed previously: recovery-e-1.21-t-20240325389105-dev-kiev
The device is Not rooted
OTA update with reasonably fast ROM download.
The new BlissLouncher v3.0.1-beta with new wallpaper is integrated.
Samsung
Galaxy S7 (SM-G930F)
herolte
before: 1.21-r-20240322388914-stable-herolte
now: 2.0-r-20240506399551-stable-herolte
Not Rooted
… no issues …
Thanks a lot for keeping that hardware alive!
But with regards to all the hype about 2.0 … I must say there’s absolutely no (or very little maybe somewhere?) change in look+feel from what I’ve seen so far …maybe I am missing something here… or maybe R is just kept as it is…(?)
edit: found it - it´s a pity:
Updater says: “No new updates found”
Don’t panic !
Same here but this is a staggered release so the update will appear in time.
Vendor Name: LG
Device name: G5 (International)
Device CodeName: h850
Version of /e/OS which existed previously: e-1.7-Q-20230112251029-dev-h850
Version of Recovery which existed previously: recovery-e-1.7-Q-20230112251029-dev-h850
The device is Not rooted
Manual upgrade form /e/OS-Q ~ T’ without data loss.
The new BlissLouncher v3.0.1-beta with new wallpaper is integrated.
Vendor Name: LG
Device name: G3 (International)
Device CodeName: d855
Version of /e/OS which existed previously: e-1.21-r-20240323388943-dev-d855
Version of Recovery which existed previously: recovery-e-1.21-r-20240323388943-dev-d855
The device is Not rooted
OTA-Update
BlissLouncher v1.18.0
Triggered the update from System settings, the phone rebooted, and now it only boots into Fastboot. System is unusable.
Vendor Name: Xiaomi
Device name: Redmi Note 8T
Device CodeName: ginkgo/willow
Version of /e/OS or Stock which existed previously: 1.21
Is the device Rooted: no
EDIT: I was able to restore the system to the previous version by dirty flashing the 1.21 recovery, then wiping cache, finally flashing 1.21 from recovery, and then resetting network settings once booted into the system to make WiFi work again. At least the phone is usable again, but this was a one hour command line enterprise and far from something a non-technical user would be able to solve, and I’m still on the old version.
OK for my Pixel5 (purchased in /e/-shop) not rooted.
It was upgraded with 2.0-t stable release (updated from 1.21.1 to 2.0 (1.20-t-20240506399547-stable-redfin) with e_redfin-user 13 TQ3A.230901.001 eng.root.20240506.184053).
To be noted : upgrade to e-2.0-t-stable locked at “reboot preparation” at 50% during 40mn for a total time about 1h30.
Also, 2 reboots were needed before internet access can work correctly (wifi or data). Some applications could access it while others (Firefox) could not. Few pbms with GPS and apps that need to use the Advanced Privacy (IP and position) buttons from not used to used.
The camera pbm (described here or there ) is still here : when I take a picture with lens1 the final picture is blurry when I’m not in “auto” mode.
A pbm more : the bliss weather does not work. It remains unconfigured with no wifi nor data access.
In fact, to configure Bliss Weather we need to use manual update instead of 15mn default between updates.
Vendor Name: Goodle
Device name: Pixel 4a
Device CodeName: sunfish
Version of /e/OS or Stock which existed previously: v1.2-t-dev
Is the device Rooted: no
No issues so far. Looking forward for the actual release notes, I don’t see alot of changes but surley for people using Bliss Launcher it will be great.
Vendor Name: Murena
Device name: FP5
Device CodeName: FP5
Version of /e/OS or Stock which existed previously:
e/OS 1.21 stable
The device is not rooted
Installation went well,
no problems after 5 Minutes of use.
Great thanks to the dev und the hole team.
Vendor Name - Xiaomi
Device name - Mi 10T Lite 5G
Device CodeName - gauguin
Version eOS which existed previously - e-1.21-t
Not Rooted
Updating without problems.
Camera: freezes when recording video (Aperture works).
Trebuchet (version 13 launcher3): i can install but it doesn’t work (NeoLauncher works)
Important: eDrive works (syncro) again.
Vendor Name: Murena
Device name: Teracube 2E
Device CodeName: Emerald
Version of /e/OS previously: 1.21.1 stable
The device is: Not rooted
Update went smooth and fine. Everything seems to work. Nice icons, interface snappy, no drain.
Improvement in this update: battery use details are working (first time on my device).
Thanks to the dev team!
Vendor Name: Fairphone
Device name: FP3
Device CodeName: FP3
Version of /e/OS previously: 1.21 t stable
The device is: Not rooted
Updated to /e/OS 2.0-t
All seems to be working well
Now waiting for an update to my FP4 (s)