You wait until the one without RC is available 
That’s a catch22: I did wait until 1.16 was available - without RC - and truely answered the question which one I installed on.
This IMHO does not qualify as information on or link to a RC.
I personally don’t mind at all, but the motivation behind this restriction is given in the post from which I cited, and I can understand it, it’s potentially confusing for users who don’t see this rc and therefore see no new version until the staggered release reaches their device.
And apart from that, do we know whether rc.4 was the final rc before official release and even if so, whether the official release is a 1:1 match of rc.4, or were there still changes?
As it stands, we don’t know what rc.4 functioning well anywhere is really worth, although it sounds better than possible issues with it, of course 
.
You are right in any aspect, and there is still the question remaining unsolved, HOW I can answer this topic without mentioning the release candidate, because I installed on it, and that is one of the answers to be given.
Or should I put it “mysterious” or “unnameable”?
Pl stop putting information about test builds on the forum.
The v1.16 release has been postponed to 24th October and be spread up to 7th Nov.
Thread will be opened when we start the release.
3 Likes
Fairphone 4 has now a better sound quality in speakerphone mode
Happy to read that 
1 Like
SM-A310F from /e/OS v1.15_q to /e/OS v1.16_q
Vendor Name: Samsung
Device name: Galaxy A3 (2016) - variant SM-A310F
Device CodeName: a3xelte
The device was and is not rooted
Upgrade via sideload:
Everything works as before!
Thanks!
PS
MicroG Services Core on the upgraded system was kept on v0.2.27.223616 regarding the problems reported with https://gitlab.e.foundation/e/backlog/-/issues/7064 (which - as usual - hasn’t been touched by the team so far …). (As long as the microG team itself still considers v0.2.27.223616 to be the stable version I will also still stick with it …)
- Sony
- Xperia XZ2 Compact
- xz2c
- Stock ROM
- bootloader unlocked
Just installed /e OS 1.16 T on stock ROM for a Sony XZ2C… everything seems to be working great, even the camera.
Thank you team !
- Oneplus
- 5
- cheeseburger
- /e/OS 1.15 T
- bootloader unlocked
Unfortunately update fails. I have made 2 times the download and after restarting there’s a blue line for completion that starts “filling”; after a small time an error Update failed apears and I only have the reboot now option. Phone completely boots on 1.15 T previously installed.
Is there any explanation for this behavior? The blue line is something new. I suppose it tries something with the firmware/partitions?
As a remark on the text before the update the name it’s LineageOS and not /e OS; a small omision I believe.
- Sony
- Xperia XZ2 Compact
- xz2c
- 1.15T
- Not rooted
Experience seems basically the same as 1.15T. I’ve just noticed that call volume seems to be stuck at a fairly loud volume. Adjusting the call volume doesn’t appear to work.
With my own xz2c I’ve noticed that since installing 1.15T (and continuing with 1.16T) that the call volume setting doesn’t appear to work. Call volume is stuck at a constant (and for me fairly loud) volume. Is that also your experience, @Cooler?
KB2003 from /e/OS v1.15_t to /e/OS v1.16_t
Vendor Name: OnePlus
Device name: 8T - variant KB2003
Device CodeName: kebab
The system was, but is now no longer Magisk-rooted (please refer to https://gitlab.e.foundation/e/backlog/-/issues/7124 , which - as usual - hasn’t been touched by the team so far …)
Upgrade via a bootloader/fastbootd procedure:
Everything works as before!
Thanks!
PS
MicroG Services Core on the upgraded system was kept on v0.2.27.223616 regarding the problems reported with https://gitlab.e.foundation/e/backlog/-/issues/7064 (which - as usual - hasn’t been touched by the team so far …). (As long as the microG team itself still considers v0.2.27.223616 to be the stable version I will also still stick with it …)
Now available (dev – stable is not there yet) for FP3. 
Fairphone | FP3+ | FP3 | previously on /e/OS 1.15-s-20230916331435-dev-FP3 | not rooted
All five stages combined took 32 minutes on my FP3+.
2 Likes
Google Pixel 4a (Sunfish)
Vendor Name: Google
Device name: Pixel 4a
Device CodeName: Sunfish
Version of /e/OS which existed previously: e-1.15-t-20230918331436-dev-sunfish
the device is Rooted
OTA-Update to e-1.16-t-20231019342574-dev-sunfish went smoothly.
Everything works fine.
THX for your great work!
Hello,
Updated my:
Xiaomi Mi8
dipper
previous version: 1.16-beta-t
installed one: 1.16-t-20231018342574-dev (via sideload)
not rooted
No bug yet. Runs smoothly.
Thx again to all the Team!
Samsung S10+
previous version 1.15s
installed: 1.16s
not rooted
OTA upgrade
It upgraded without any issues (really fast, actually).
I’ve been using the new version for 24h now, and have not encountered any bug or issue, yet.
Vendor Name: Xiaomi
Device name: Pocophone F!
Device CodeName: Beryllium
Version of /e/OS which existed previously: e-1.15-S-dev
My home screen setup has been completely broken. Find below the first three home screen pages. From page three onwards, all apps appear in alphabetical order.
Otherwise, update seems working.
