Updated very smoothly. That was nice. The only small issue I noticed is the App Lounge settings reverted to default so I had to change them back to my preferences.
Vendor Name Teracube
Device name 2e
Device CodeName emerald
Version of /e/OS existed previously 1.13-r-20230724313393
Not rooted
Hi, i think itâs a problem with the qualcomm aptX codec.
Go to headphones bluetouth settings and turn it off.
The phone change to another codec.
This works for me as a workaround, till they fix it.
I have a Teracube 2e the first one about two or three updates ago VoWifi started and I was very happy. I am on Mintmobile so VoWifi is supported by the carrier. I know per the store this device does not support it but I know it works on stock Android and LineageOS and it worked on like two or three previous builds of /e/. It is possible to for VoWifi to work. Anyways on this update VoWifi stopped working and I am hopping it will make a comeback or get official support.
Vendor: Murena
Device Name: Teracube_2e
Version of /e/OS 1.14.2-s-20230825321008-stable-zirconia
Version of /e/OS or Stock which existed previously : v1.13
The device isnât rooted
Updater was crashing, so I needed to clear updater storage. Now itâs working, but I donât have 1.13 anymore (I usually like to keep at least one older version)
Vendor name : Fairphone
Device name : FP3
Device CodeName : FP3
Version of /e/OS or Stock which existed previously : v1.13
The device isnât rooted
Since the last update, Iâve got 2 different issues :
1 - Canât create a connection share (it worked perfectly before)
2 - Very important lags when playing the Merge Dragon game (difficulty for scrolling or double touching). It worked also perfectly before
previous /e/OS version was 1.13, but I have no idea what version of Android was present when I rooted it
Same here, on my FP4 with /e/os 1.14
If âAudio HD : Qualcomm aptX audioâ is enabled, then no sound comes out of my bluetooth headset (Plantronics Backbeat Pro 2)
If disabled, it works perfectly
I was making a video recording with my FP4 and a message came in, but instead of e/os muting the sound of the message and just give the notification in the screen. The sound of the message is now recorded in the videoâŚ
Very annoying as it is a very loud sound and can be very clearly heared when playing back the video.
My FP3 running 1.14-s-20230815320616 (lang: DE, EN) is barely usable after upgrading.
Previous version: 1.13
The software navigation bar / buttons do not work properly. The home button does sometimes return to the home screen / app launcher. The square does not work most of the time. Taping on it does not open the application history, the configured longpress action is also not triggered. Removing configured action from the settings does not solve the problem.
The bugs typically appear after using the phone for less than 15 minutes. The only workaround i found is restarting the phone. I am not able to close apps as usually which results in a much higher battery drain.
The home button error was present in previous versions, but did only occur ~once a month.
I am not sure if this is a bug in android 12 or in the build here but I use Signal and customize my notifications for it, and more often than not it uses default sound. I would guess it is a notifications bug, since it certainly has changed how you get into settings for applicationâs notifications.
I do not have any other 3rd party apps that I would duplicate with.
Battery life is noticeably shorter.
Everything else seems to be working just fine, the update was flawless.
Fairphone FP3
Version of /e/OS previously: 1.13-S-dev
The device rooted
Neither the system nor the updater show the version number (only âAndroid 12â).
The change log link goes to a not existing page because in the URL the version is missing, too.
The updater shows a toast that there was no internet connection but it is. So no search for further updates is possible.
Trebuchet keeps crashing frequently as soon as another Launcher is installed. Sometimes Trebuchet doesnât restart so that recent apps doesnât work any more. A system reboot is necessary.