Vendor Name: Fairphone
Device Nem: Fairphone 3
Device Code Name: FP3
Previously version: 1.14
The microphone shutdowns without reason, when I send an audio via whatsapp there is no sound. To re activate the microphone i need to make a call and activate the mic.
I kinda stopped coming here because I have fewer and fewer issues. It does not seem quite fair for the devs! 
I did […] → 1.11-s → 1.13-s → 1.15-s and those versions were OK on my /e/-bought FP3+ (which will soon be three years old I think). Thanks for your work.
I just have Camera has focus problems after update to eOS v1.15 now but nothing too annoying.
1 Like
Issues #1 and #3 seem to be related to Android in general as they are listed on the fairphone 4 issue tracker..
I am also experiencing issue #3 and it has gone worse since the latest update to 1.15 
I need to use earphones now to be sure I get heard.
Vendor name: Fairphone
Device name: Fairphone 3 (original camera module)
Version of /e/OS previously: 1.14-s stable
Version of /e/OS now: 1.15-s stable
No custom recovery
Nova launcher
I believe it is since 1.15 (maybe since 1.14, but not earlier) that in Telegram when I watch a video in panorama mode (phone on the side) and full screen that the three virtual buttons (back, home, minimized apps) keep sliding in and out on the right side at high frequency. When I adjust the volume and the volume bar shows on the right side, it also moves back and forth with the three buttons at the same high frequency. Extremely annoying. Any Telegram users have the same issue?
Hey, I updated to v1.15 on my Murena Teracube 2e (zircona), presumably on the “stable” channel, but now it’s listed as “dev” What gives?
I am having horrible problems with my text messaging on stock QKSMS (from F-droid). I am not using the built-in message app. Sporadically, it will just fail to send, and nothing will work, in or out, until I reboot the phone.
Vendor: Murena
Device Name: Teracube 2e
Codename: Zirconia
previous \e\OS: IMG-e-1.14.2-s-20230825321008-stable-zirconia.zip
current v1.15 \e\OS: [IMG-e-1.15-s-20230913330639-stable-zirconia.zip] (there is no longer a link!)
Device is not currently rooted
Please refer to this guide to find out what you are running currently … [HOWTO] Give complete /e/OS version info easily for support, answers, comparison etc
1 Like
Well, yes – there was no link, so I copied it from my phone. What I reported is the version that shows on my phone under “/e/OS version”
Part of what I’m asking about is that I installed it as “stable”, but a very similar version now appears in “dev” that appears to have been released four days later. So where does that leave the (now absent) stable version on my phone? @Manoj ? Should I roll it back to stable v1.14? Or try dev v1.16? I usually avoid dev versions because I use it as my “daily driver” phone.
Galaxy S9
Vendor Name: Samsung
Device name: Galaxy S9
Device CodeName: starlte
Version of /e/OS or Stock which existed previously: /e/OS 1.14
Is the device is: Not rooted
Problems:
- The launcher has slowed down: when swiping away an app / returning to the home screen, it always takes a second before app icons appear. I use no wallpaper, just a blank unicolour background.
- The sharing menu is very slow: No matter if I’m trying to share a photo from the Gallery app or a text from the Notes app, it takes up to 15 seconds before the sharing menu has loaded suggested contacts and app icons. Strange thing is, when I switch off the screen once the sharing menu is loaded, and then switch it back on, the menu needs to reload contacts and app icons and that takes just as long again.
Pinging @Manoj instead. Why is build 1.15-s-20230913330639-stable-zirconia not offered anymore? Was it retracted?
There is no easy rollback in recent Android once there are different security patch levels involved across the respective OS versions.
This would amount to a new install, wiping your data by default (at least it would be safer to assume so).
Switching from stable to dev would amount to a new install, too, wiping your data by default (at least it would be safer to assume so).
dev is a different release channel/ build type … https://doc.e.foundation/build-status … it isn’t offered instead of a certain stable version, but in parallel for itself.
For what it’s worth …
The stable build for zirconia should come with the next iteration - v1.16 . Will check and update if there is any change in the plan.
- Vendor Name: Fairphone
- Device name: Fairphone 4
- Device CodeName: FP4
- Version of /e/OS or Stock which existed previously: /e/OS v1.14
- Is the device Rooted / Not rooted: not rooted
Bliss Launcher issues
Seeing a couple of weird Bliss Launcher display glitches. This isn’t necessarily new to v1.15; that’s just when I started to be systematic about investigating and screenshotting.
Dynamic icon shape inconsistencies and glitches
Summary: Bliss Launcher doesn’t respect the user’s choice of dynamic icon shape, except when creating shortcuts. The current shapes gets baked into shortcuts at creation time, even if the user subsequently changes it.
OK, so Bliss Launcher does not respect Settings → Display → Icon Shape for normal app icons. Instead, it always uses “Rounded Rectangle”. I wish it used the setting and allowed you to change the icon shape: squircles are slightly nicer!
When shortcuts are created, though, the shape configured in that setting is respected, but in a weird way. It is hard-baked into the shortcut’s icon for its entire lifetime, then cropped additionally by Bliss’s “rounded rectangle”.
This can make shortcuts display with grey corners, since “Device Default” is “round”, apparently. See the shortcuts created by Shelter in How to make Advanced Privacy work with work profiles using Shelter - #3 by achadwick, and compare them with their equivalents below. I honestly thought that this was how Bliss marked shortcuts, back then, but it turns out it’s just a glitch.
Workaround: If you want consistency between shortcuts and apps, change Settings → Display → Icon Shape to “Rounded Rectangle” before (re)creating the shortcuts
Icon size and layout fluctuations
BlissLauncher’s layout fluctuates over time. Basically, even if the icons stay in the same place and the names don’t change, the layout changes over periods of a few hours or days, and the icons seem to draw unpredictably at different sizes. This misdrawing can (seemingly) compound and make folders display with odd grey bottom and right borders (last screenshot).
It’s kind of bistable in that the layout algorithm seems to pick one of two sizes for the icons, but the main area and the 4 quick access icons at the bottom stabilize at different times. Which is a bit odd; I wonder if the two zones are influencing each other by adopting different sizes? The screenshots above are ordered chronologically, but aren’t necessarily that close in time (this is over 6 days)
- Main area:
- state M1: screenshots 1 and 4 (nice fill, this looks good)
- state M2: screenshots 2 and 3 (not as nice looking, cant’ really put anything in the gap)
- Quick access strip:
- state Q1: screenshots 1 and 3 (consistent with M1)
- state Q2: screenshots 2 and 4 (small icons like M2)
This glitch affects 3-button, 2-button, and gesture navigation all the same way. The extra space from gesture navigation doesn’t allow the algorithm to make better choices (or more accurately, more consistent and more stable ones)
- Vendor Name:
OnePlus. - Device name:
OnePlus 8 Pro. - Device CodeName:
instantnoodlep. - Version of /e/OS or Stock which existed previously:
R worked previously. - Is the device Rooted / Not rooted:
Not rooted. Fresh install.
The touchscreen does not work when S or T is installed. This is regardless of which OOS version it is flashed over (whether Android 11, 12 or 13). For both, I even tried extracting the recovery, vbmeta and boot images and flashed them first (as those are not available for download next to the T version).
Same Phone, same software,
exactly the same issues
gigaset
GS-290
Previous version v1.14
Not rooted
Since installing v1.15-s-2023091333063-stable-GS290, cannot send any SMS messages. Tried numerous workarounds suggested, none work.
I have a Fairphone 3+ on version 1.15-s-20230913330639-stable-FP3 and le location provider does not work. Actually, I have the problem for a moment (since 1.12, if I remember well), and I cannot any extra location provider.
I tryed to install the Mozilla Stumbler to improve precision, but I don’t understand if it works because it does something and gets no error, but the Mozilla location provider is still lost.
Yes, but the stable version of 1.14 for zirconia is also Android 12 (S), so I wouldn’t have to deal with that rollback issue, correct? @Manoj , could I roll back to 1.14 stable without loss of data? I know I can’t do it OTA, but I’ve done many command line installs. How long until v1.16, do you think?
Even if the underlying Android version is the same, rollback protection is still about the security patch level (I’ve seen this in practice myself).
1.14 has an older security patch level than 1.15.
Since the update to /e/OS 1.15 my USB DAC the Hidzizs S9 Pro is not anymore recognized by my GS290. What to do?
Vendor Name Gigaset
Device name GS290
Device CodeName
Version /e/OS 1.15 or 1.16. Now I have 1.17-s-20231109350748-stable-GS290
Not Rooted