Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2024-02-28T17:37:09Zhttps://gitlab.e.foundation/e/backlog/-/issues/7488GS290 completely unstable & unusable after upgrade to 1.152024-02-28T17:37:09ZJonathan RTGS290 completely unstable & unusable after upgrade to 1.15- /e/ version: 1.15
- Device model(s): GS290
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: no
## Summary
After upgrading to 1.15 2 days ago, first everything was still usable, even when the system was qu...- /e/ version: 1.15
- Device model(s): GS290
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: no
## Summary
After upgrading to 1.15 2 days ago, first everything was still usable, even when the system was quite slow in comparison to version 1.14 with android 11. Only thing I recognized was that the typeset and visuals where a bit off because everything was huge. Then first issues began after around 1 additional day with 1.15 when synchonisation apps stopped working. Also the filemanager app startet viewing errors when trying to create folders.
So I decided to restart the phone. After this, nothing was usable anymore. The login process with sim and biometrical unlock was way slower and with high latency than ever before. After the unlock noting started up and only the message screen was able to be opened up from the top. Over this I was able to open the settings but in most cases, everything I open up via the settings menu, an empty window opens and nothing happens anymore. Somehow I managed to switch my launcher from ruthless back to bliss (default) but thats it. Even in safe-mode I am not able to open any app. Even the Upgrade-View (first in settings menu) isn't accessible.
My phone isn't usable like this anymore. I never ever had this happen since I used the GS290 with eOS. And I upgraded multiple times now.
## The problem
**Steps to reproduce**
Upgrading from 1.14 (Android 11) to 1.15 (Android 12) and restart the phone once after you upgraded successfully.
Maybe its corresponding with using Ruthless-Launcher as app launcher but not sure, because problems persist even after switching back to bliss.
**What is the current behavior?**
Phone can be started but not used beside app launcher and accessing settings because no apps can be opened and viewed anymore.
Nether the deinstallation of any apps is possible.
**What is the expected correct behavior?**
Seemless opening and usage of apps and windows
## Technical informations
**Relevant logs (`adb logcat`)**
Can't create logs nor acess files
**Relevant screenshots**
Can't create Screenshots nor acess files
## Solutions
**Workaround**
Nothing known yet
**Possible fixes**
Nothing known yethttps://gitlab.e.foundation/e/backlog/-/issues/6838Murena One screen does not turn on when fingerprint is touched2024-02-28T17:26:40ZShenol MustafovMurena One screen does not turn on when fingerprint is touched- /e/ version: 1.9
- Device model(s): Murena One
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Seemingly randomly, Murena One screen does not turn on, and the phone does not unlock, when th...- /e/ version: 1.9
- Device model(s): Murena One
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Seemingly randomly, Murena One screen does not turn on, and the phone does not unlock, when the fingerprint scanner is touched. It works 80% of the time, but in 20% it does not show anything, and I need to first press the power button, to turn the screen on, then scan the finger.
## The problem
**Steps to reproduce**
It just does not work some times.
**What is the current behavior?**
Screen stays black, no sign of scanning/unlocking.
**What is the expected correct behavior?**
Phone should unlock and turn on the screen.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/7576Sensors do not work2024-02-28T17:16:42ZDmitriSensors do not work- /e/ version:
- Device model(s): Fairphone 4
- Developer mode enabled: yes
- Device rooted: yes
- Trackers blocker enabled: yes
## Summary
I downloaded FP4-TP1V-factory.zip on October 5 and installed it on my new fp4.
As I began using...- /e/ version:
- Device model(s): Fairphone 4
- Developer mode enabled: yes
- Device rooted: yes
- Trackers blocker enabled: yes
## Summary
I downloaded FP4-TP1V-factory.zip on October 5 and installed it on my new fp4.
As I began using the phone I started noticing that none of my sensors worked. The phone does not turn of the screen when I'm calling. Pictures are not rotated even though I turned it on in the app settings. My bubble level did not work.
## The problem
None of the sensors work. If I run phyphox it says with every test that the sensor is not available.
Strange thing is that google maps does seem to measure changes in luminosity because the app turns to dark mode when I drive through a tunnel.
**Steps to reproduce**
Take a new FP4 and install FP4-TP1V-factory?
<What actually happens>
Sensors do not work except apparently for a google app (maps)
**What is the expected correct behavior?**
the phone should register changes in motion, luminosity, etc
<What you should see instead>
The phone (except for google maps) does not register any changes in motion, luminosity, etc/
## Technical informations
Fairphone 4 with /e/os FP4-TP1V-factory
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
/system/bin/sh: adb: inaccessible or not found
**Relevant screenshots**
![photo_2023-11-27_18-30-55](/uploads/41fff97a898c659926726073011eb0ac/photo_2023-11-27_18-30-55.jpg)
![photo_2023-11-27_18-30-55__2_](/uploads/374b4ca00db42ccdfdd0def5cd857add/photo_2023-11-27_18-30-55__2_.jpg)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/5660Updater does not support patch number2024-02-28T17:11:48ZNicolas GelotUpdater does not support patch number- /e/ version: v1.0.2
- Device model(s): ~"FP3/FP3+"
## Summary
We cannot publish version with patch number like `v1.0.2` where `2` is the patch number because the ~"/e/OS Updates" crashes.
## The problem
**Steps to reproduce**
H...- /e/ version: v1.0.2
- Device model(s): ~"FP3/FP3+"
## Summary
We cannot publish version with patch number like `v1.0.2` where `2` is the patch number because the ~"/e/OS Updates" crashes.
## The problem
**Steps to reproduce**
Have a build with a patch number and tap on the refresh button of the updater.
**What is the current behavior?**
The ~"/e/OS Updates" crashes.
**What is the expected correct behavior?**
The ~"/e/OS Updates" supports patch number.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
--------- beginning of crash
06-21 08:52:06.536 5517 5517 E AndroidRuntime: FATAL EXCEPTION: main
06-21 08:52:06.536 5517 5517 E AndroidRuntime: Process: org.lineageos.updater, PID: 5517
06-21 08:52:06.536 5517 5517 E AndroidRuntime: java.lang.NumberFormatException: multiple points
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1914)
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at sun.misc.FloatingDecimal.parseFloat(FloatingDecimal.java:122)
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at java.lang.Float.parseFloat(Float.java:451)
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at org.lineageos.updater.misc.Utils.checkForNewUpdates(Utils.java:279)
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at org.lineageos.updater.UpdatesActivity.processNewJson(UpdatesActivity.java:326)
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at org.lineageos.updater.UpdatesActivity.access$600(UpdatesActivity.java:75)
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at org.lineageos.updater.UpdatesActivity$6.lambda$onSuccess$1$UpdatesActivity$6(UpdatesActivity.java:365)
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at org.lineageos.updater.-$$Lambda$UpdatesActivity$6$N0a8nQdJ_byRZOxzn1AfTWoQm-s.run(Unknown Source:8)
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:883)
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:100)
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7356)
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
06-21 08:52:06.536 5517 5517 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
06-21 08:52:12.356 5517 5531 W System : A resource failed to call close.
```
cc @rhunault/e/OS v1.6-rc.4Alexandre RouxAlexandre Rouxhttps://gitlab.e.foundation/e/backlog/-/issues/7258Fairphone 4 camera shows lens 3 (which does not exist)2024-02-28T17:09:56ZShenol MustafovFairphone 4 camera shows lens 3 (which does not exist)- /e/ version: 1.14
- Device model(s): FP4
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: no
## Summary
Fairphone 4 camera shows lens 3 after the OS update. Previously there was only lens 1 (normal) and le...- /e/ version: 1.14
- Device model(s): FP4
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: no
## Summary
Fairphone 4 camera shows lens 3 after the OS update. Previously there was only lens 1 (normal) and lens 2 (wide).
## The problem
**Steps to reproduce**
Open the camera app, click on lens 1, then again on lens 2. Lens 3 seems to be lens 1.
**What is the current behavior?**
Showing lens 3, which does not exist
**What is the expected correct behavior?**
no lens 3
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![image](/uploads/324c241625a49593aa55dd64d03df14d/image.png)
## Solutions
**Workaround**
Just switch again to lens 1.
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/7084"Whitelist" Microsoft SSO domain in Advanced Privacy2024-02-28T16:51:06ZAude M"Whitelist" Microsoft SSO domain in Advanced Privacy## Summary
<Summarize the improvement briefly and precisely>
Microsoft SSO domain is detected as a tracker by Exodus and blocked by ~"Advanced Privacy" which causes issues. After an [analysis](https://gitlab.e.foundation/e/backlog/-/is...## Summary
<Summarize the improvement briefly and precisely>
Microsoft SSO domain is detected as a tracker by Exodus and blocked by ~"Advanced Privacy" which causes issues. After an [analysis](https://gitlab.e.foundation/e/backlog/-/issues/6936), we've decided to stop consider it as a tracker.
## Description
**What is the current behavior?**
<What actually happens>
Microsoft SSO domain login.microsoftonline.com is considered as a tracker.
**What is the improved behavior?**
<What you should see instead>
Microsoft SSO domain login.microsoftonline.com is not considered as a tracker even if in Exodus's analysis.
**What does it bring?**
<Why this improvement is needed>
Better usability of apps using Microsoft SSO.
## Mock-ups
<Provide a mock-up of how it would look with the improvement>
## Examples
<Give the example of what users will be able to accomplish with the improvement>
## Validation
<List test case that will be run to validate that the issue is working as expected>
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>
/cc @jacquarg @rhunault/e/OS v1.14-betaGuillaume JacquartGuillaume Jacquarthttps://gitlab.e.foundation/e/backlog/-/issues/7134Microsoft Intune Company Portal not working2024-02-28T16:50:08ZShenol MustafovMicrosoft Intune Company Portal not working- /e/ version: 1.12.3
- Device model(s): FP3+
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
After update to 1.12.3 Microsoft Intune Company Portal connection is not working anymo...- /e/ version: 1.12.3
- Device model(s): FP3+
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
After update to 1.12.3 Microsoft Intune Company Portal connection is not working anymore, reporting no connection.
Seems like this is related to Advanced Privacy, but even with tracker for Intune and other Microsoft apps disabled, the connection is not working. When tracker control is totally disabled, the connection works.
## The problem
**Steps to reproduce**
install Intune Company Portal , try to use the app.
**What is the current behavior?**
no connection
**What is the expected correct behavior?**
app should work
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![image](/uploads/fe87379155ac5d4ef59f6dd123e672b4/image.png)
![image](/uploads/dafd7315d94bda06160bfdbfc72213cb/image.png)
## Solutions
**Workaround**
Disabling "apps tracker control" on phone level, makes the app work.
**Possible fixes**
Could there be another tracker, which is not Microsoft app or Intune portal related, which affects the connection?
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/7738[Fairphone 5] settings for double tap on lock screen to wake-up2024-02-28T16:41:35ZErwan Georgete.i9dnw@passmail.net[Fairphone 5] settings for double tap on lock screen to wake-up- /e/ version: 1.19
- Device model(s): FP5
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
There are no settings to configure double tape on lock screen to wake-up. Setting exist in Fairphon...- /e/ version: 1.19
- Device model(s): FP5
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
There are no settings to configure double tape on lock screen to wake-up. Setting exist in Fairphone 5 with stock Android.
## The problem
Open settings -> Display -> Other display parameters -> no option for double tape to wake up (but double tape on status bar to sleep device exist)
**Relevant screenshots**
![Screenshot_20240205-124602_Paramètres](/uploads/9448299227828c9571d6211480c60edf/Screenshot_20240205-124602_Paramètres.png)
## Solutions
**Possible fixes**
Add this setting from stock android example.
Related to #7539 (yes, I copied most of the text :innocent:)https://gitlab.e.foundation/e/backlog/-/issues/7697[Devices] 2024-01-23 Grooming2024-02-28T16:27:17ZRomain Hunault[Devices] 2024-01-23 Grooming1. Issues without a weight: https://gitlab.e.foundation/groups/e/-/issues/?sort=updated_desc&state=opened&iteration_id=284&weight=None&first_page_size=100
2. Roadmap
- Murena 3: more details? no
- End of A11: end of support?
...1. Issues without a weight: https://gitlab.e.foundation/groups/e/-/issues/?sort=updated_desc&state=opened&iteration_id=284&weight=None&first_page_size=100
2. Roadmap
- Murena 3: more details? no
- End of A11: end of support?
- End of A12 for Q3? Probably a bit early?https://gitlab.e.foundation/e/backlog/-/issues/7640Teracube 2e (zirconia) installation instructions needs correction2024-02-28T14:43:40ZShenol MustafovTeracube 2e (zirconia) installation instructions needs correction- /e/ version: 1.18
- Device model(s): zirconia
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
<Summarize the bug encountered briefly and precisely>
## The problem
**Steps to re...- /e/ version: 1.18
- Device model(s): zirconia
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
<Summarize the bug encountered briefly and precisely>
## The problem
**Steps to reproduce**
Install /e/ OS on the Teracube 2e (2020) according to the instructions at https://doc.e.foundation/devices/zirconia/install.
After the last command "fastboot reboot" the screen went black.
The smartphone can no longer be started at all, not even in recovery or fastboot mode.
Comparing the commands mentioned in the instructions above with the files in the installation ZIP, several files were NOT mentioned in the list of "fastboot flash ..." commands, although they were included in the ZIP file.
Downloading various installation ZIPs from the dev and stable branches and compared the files they contained: There were always (different) files included that were not mentioned in the instructions.
Most likely instructions at https://doc.e.foundation/devices/zirconia/install are out of date and that the file "dtbo.img", for example, which is not mentioned there but is present in the ZIP file, should also have been flashed.
The smartphone can no longer be booted after following the instructions. Cannot flash the missing files afterwards.
**What is the current behavior?**
Wrong instructions. Phone bricked.
**What is the expected correct behavior?**
Right instructions
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
/label ~"type::Bug"
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>/e/OS v1.20-betaSahil SonarSahil Sonarhttps://gitlab.e.foundation/e/backlog/-/issues/7066Brightness issues FP42024-02-28T14:43:00ZHaydee ElizondoBrightness issues FP4- /e/ version: 1.11
- Device model(s): Fairphone 4
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: no
## Summary
<Summarize the bug encountered briefly and precisely>
Without using the automatic brightness...- /e/ version: 1.11
- Device model(s): Fairphone 4
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: no
## Summary
<Summarize the bug encountered briefly and precisely>
Without using the automatic brightness option, but chosen manually, sometimes the brightness suddenly drops quite a lot (30-40% or so?) and it is no longer possible to get the full brightness at that point, even if you manually set the slider to maximum. Some time later, suddenly, the brightness returns to the previous level.
**Steps to reproduce**
<How one can reproduce the issue>
**What is the current behavior?**
<What actually happens>
**What is the expected correct behavior?**
<What you should see instead>
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
Similar errors were identified at,
- https://forum.fairphone.com/t/random-screen-dimming-while-brightness-slider-stays-at-100-after-a12-update/93195
- https://community.e.foundation/t/maximum-brightness-changes/50243
I would like to identify if these bugs with similarities can give a better picture of the issue and if it is something that needs to be fixed from Fairphone or if there is something that can be done from Murena.
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>/e/OS v1.20-betahttps://gitlab.e.foundation/e/backlog/-/issues/7109Network connectivity loss on Fairphone 42024-02-28T14:42:54ZShenol MustafovNetwork connectivity loss on Fairphone 4- /e/ version: 1.11
- Device model(s): FP4
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
Often (but not always) the phone cannot connect to the network. An explanation mark appe...- /e/ version: 1.11
- Device model(s): FP4
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
Often (but not always) the phone cannot connect to the network. An explanation mark appears in the GSM-icon on the top of the screen, for both e-SIM and normal SIM.
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
**What is the current behavior?**
Network settings reset does not help. SIM card change does not help.
**What is the expected correct behavior?**
<What you should see instead>
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![image](/uploads/8fb25d9637ff64e6827a6a9082afb2bd/image.png)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>/e/OS v1.20-betaAlexandre RouxAlexandre Rouxhttps://gitlab.e.foundation/e/backlog/-/issues/7560night light turns off for 1-2 seconds, causing flashes2024-02-28T14:42:48ZShenol Mustafovnight light turns off for 1-2 seconds, causing flashes- /e/ version: 1.15-1.17
- Device model(s): Murena One
- Developer mode enabled: yes/no
- Device rooted: no
- Trackers blocker enabled: yes/no
## Summary
Seems there is a bug in the night light mode. When night light is enabled, someti...- /e/ version: 1.15-1.17
- Device model(s): Murena One
- Developer mode enabled: yes/no
- Device rooted: no
- Trackers blocker enabled: yes/no
## Summary
Seems there is a bug in the night light mode. When night light is enabled, sometimes it turns off and on erratically.
## The problem
**Steps to reproduce**
Turn on "night light" , use the phone. The issue happens rarely, but seems like happens more often, when the phone is downloading files from internet. The screen becomes white, then red again in a short time. Showing the notifications (drop down from top, to see the download progress), might trigger it. I was able to reproduce randomly during the download, then the same issue happened when the phone is on main screen. It is hard to reproduce on demand, but it happens.
**What is the current behavior?**
Phone disables night light for 1-2 seconds
**What is the expected correct behavior?**
No change
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![signal-2023-11-22-222734](/uploads/53b54dd931458cde4f89b5015c007a13/signal-2023-11-22-222734.mp4)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>/e/OS v1.20-betaRohit R Sekharmerothh@e.emailRohit R Sekharmerothh@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/7597Sound level too low on call after /e/ OS update on GS2902024-02-28T14:41:10ZShenol MustafovSound level too low on call after /e/ OS update on GS290- /e/ version: 1.17
- Device model(s): GS290
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
After /e/ OS update, probably 1.15??? , the sound level of the phone drops too much (in...- /e/ version: 1.17
- Device model(s): GS290
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
After /e/ OS update, probably 1.15??? , the sound level of the phone drops too much (in normal mode, not in speakerphone mode)
## The problem
**Steps to reproduce**
Maybe updating to to 1.15 etc. causes a bug in sound levels.
**What is the current behavior?**
Sound too low
**What is the expected correct behavior?**
normal sound
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![image](/uploads/fc428e7788c4e951ea0620e4cf945574/image.png)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>/e/OS v1.20-betahttps://gitlab.e.foundation/e/backlog/-/issues/7325Apply /e/OS' icon and /e/OS' app name for Maps notification2024-02-28T14:40:29ZRaj Khemanirajk@murena.ioApply /e/OS' icon and /e/OS' app name for Maps notification- /e/ version: 1.16-beta
- Device model(s): ~FP4 ~one
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
The ~"/e/OS Maps"' icon and name are not being used in Maps' notifications.
[Referenc...- /e/ version: 1.16-beta
- Device model(s): ~FP4 ~one
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
The ~"/e/OS Maps"' icon and name are not being used in Maps' notifications.
[Reference issue](https://gitlab.e.foundation/e/backlog/-/issues/5732#note_445572)
## The problem
**Steps to reproduce**
\-Start navigation with maps
\- check the notification
**What is the current behavior?**
Maps' notification not using ~"/e/OS Maps"' icon and name.
**What is the expected correct behavior?**
Maps' notification should use ~"/e/OS Maps"' icon and name.
[Here](https://www.figma.com/file/CSCHqZyZioMyV2I2rAMBjc/Icons?type=design&node-id=302-3669&mode=design&t=aPMKoW57qYd2EQtB-4) is the icon which should be used, in our accent colour.
![image](/uploads/2c7e0895950f4caac00e0954a84bb129/image.png)
## Technical informations
**Relevant screenshots**
| T | S |
|---|---|
| ![image.png](https://gitlab.e.foundation/e/backlog/uploads/876f81c2dc5293fb016190242d71f16d/image.png){width=404 height=520} | ![image.png](https://gitlab.e.foundation/e/backlog/uploads/65a46a86a72d94cd6d7287a72262fc3f/image.png){width=384 height=482} |
| ![image.png](https://gitlab.e.foundation/e/backlog/uploads/c2d4f8817d9d4030469555232fe8eea5/image.png){width=403 height=410} | ![image.png](https://gitlab.e.foundation/e/backlog/uploads/81dd7b3c7427cce5489519bf18889ee9/image.png){width=403 height=410} |
## Solutions
**Workaround**
**Possible fixes**/e/OS v1.20-betaNishith KhannaNishith Khannahttps://gitlab.e.foundation/e/backlog/-/issues/7222sms bug after sending mms2024-02-28T14:40:18ZFlorent VINCENTsms bug after sending mms- /e/ version:1.13
- Device model(s): murena s8
- Developer mode enabled: yes
- Device rooted: yes/no
- Trackers blocker enabled: yes
## Summary
after sending a mms (image + text) if i send a sms to same recipient without leaving conve...- /e/ version:1.13
- Device model(s): murena s8
- Developer mode enabled: yes
- Device rooted: yes/no
- Trackers blocker enabled: yes
## Summary
after sending a mms (image + text) if i send a sms to same recipient without leaving conversation, there is a flickering image of the previous image sent, each time i hit a letter to send this next sms
video more explicit than text explanation
![bug-mms-sms](/uploads/321eaa5d19ae46879ae38a84ab51a38a/bug-mms-sms.webm)
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
**What is the current behavior?**
flickering image on each letter i write
**What is the expected correct behavior?**
no flickering image
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>/e/OS v1.20-betaAbhishek AggarwalAbhishek Aggarwalhttps://gitlab.e.foundation/e/backlog/-/issues/6760Murena One picture quality2024-02-28T14:38:25ZShenol MustafovMurena One picture quality- /e/ version: 1.9 (but the issue may have started earlier)
- Device model(s): Murena One
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Pictures taken with Murena One have low quality with ...- /e/ version: 1.9 (but the issue may have started earlier)
- Device model(s): Murena One
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Pictures taken with Murena One have low quality with a lot of noise/distortion.
## The problem
**Steps to reproduce**
Take pictures with Murena One. Change to different resolutions. Zoom into the picture. On all resolutions, the quality is far from ideal, and there is noise.
**What is the current behavior?**
There is noise
**What is the expected correct behavior?**
High quality pictures.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![d-une-photo-de-48MP-avec-reduction-du-bruit_IMG_20230120_131104](/uploads/f78b93a530f9945c42fab6e507b3cb88/d-une-photo-de-48MP-avec-reduction-du-bruit_IMG_20230120_131104.jpg)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>/e/OS v1.20-betaMohammed Althaf ThayyilMohammed Althaf Thayyilhttps://gitlab.e.foundation/e/backlog/-/issues/6465FP4 does not take a picture as long as the camera is moving (slow camera)2024-02-28T14:38:10ZShenol MustafovFP4 does not take a picture as long as the camera is moving (slow camera)- /e/ version: 1.6
- Device model(s): FP4
- Device rooted: no
## Summary
FP4 never takes a picture as long as the phone is moving (no fixed focus). This is likely caused by Open Camera: https://sourceforge.net/p/opencamera/tickets/615/...- /e/ version: 1.6
- Device model(s): FP4
- Device rooted: no
## Summary
FP4 never takes a picture as long as the phone is moving (no fixed focus). This is likely caused by Open Camera: https://sourceforge.net/p/opencamera/tickets/615/
## The problem
**Steps to reproduce**
Click the take picture button in Camera and start moving FP4, the camera does not take a picture until you stop moving the phone.
**What is the current behavior?**
Does not take a picture
**What is the expected correct behavior?**
Should take a picture immediately
## Solutions
**Workaround**
Click the third button on top (flash icon) > under photo mode, choose locked or infinity or MF (manual focus)
**Possible fixes**
This Open Camera issue: https://sourceforge.net/p/opencamera/tickets/615/
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>/e/OS v1.20-betaMohammed Althaf ThayyilMohammed Althaf Thayyilhttps://gitlab.e.foundation/e/backlog/-/issues/7696Searching the calendar crashes the app2024-02-28T14:37:38ZMatthieu RomanSearching the calendar crashes the app- /e/ version: 1.19.1-s stable
- Device model(s): FP4
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Searching the native calendar app crashes the app.
## The problem
**Steps to reproduce...- /e/ version: 1.19.1-s stable
- Device model(s): FP4
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Searching the native calendar app crashes the app.
## The problem
**Steps to reproduce**
Open Calendar, then three dot menu on the right, tap Search.
**What is the current behavior?**
The app crashes.
**What is the expected correct behavior?**
You should have the possibility to search through Calendar events.
## Technical informations
**Relevant logs (`adb logcat`)**
Logs copied from the [corresponding forum post](https://community.e.foundation/t/searching-the-calendar-crashes-the-app/53377) with a Pixel 3xl:
```
[11-12 19:48:58.554 1723:6232 I/ActivityTaskManager]
START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=foundation.e.calendar/com.android.calendar.AllInOneActivity bnds=[271,403][495,771]} from uid 10207
[11-12 19:48:58.813 1723:1866 I/ActivityTaskManager]
Displayed foundation.e.calendar/com.android.calendar.AllInOneActivity: +255ms
[11-12 19:48:58.840 11034:11034 I/GoogleInputMethodService]
GoogleInputMethodService.onStartInput():1883 onStartInput(EditorInfo{EditorInfo{packageName=foundation.e.calendar, inputType=0, inputTypeString=NULL, enableLearning=false, autoCorrection=false, autoComplete=false, imeOptions=0, privateImeOptions=null, actionName=UNSPECIFIED, actionLabel=null, initialSelStart=-1, initialSelEnd=-1, initialCapsMode=0, label=null, fieldId=16908298, fieldName=null, extras=null, hintText=null, hintLocales=}}, false)
[11-12 19:48:59.182 1723:30788 W/InputManager-JNI]
Input channel object ‘d1ce775 Splash Screen foundation.e.calendar (client)’ was disposed without first being removed with the input manager!
[11-12 19:49:01.906 15266:15690 E/AndroidRuntime]
FATAL EXCEPTION: Filter
Process: foundation.e.calendar, PID: 15266
java.lang.IllegalAccessError: Field ‘androidx.cursoradapter.widget.CursorAdapter.mContext’ is inaccessible to class ‘androidx.appcompat.widget.SuggestionsAdapter’ (declaration of ‘androidx.appcompat.widget.SuggestionsAdapter’ appears in Etar.apk)
at androidx.appcompat.widget.SuggestionsAdapter.getSearchManagerSuggestions(SuggestionsAdapter.java:776)
at androidx.appcompat.widget.SuggestionsAdapter.runQueryOnBackgroundThread(SuggestionsAdapter.java:156)
at androidx.cursoradapter.widget.CursorFilter.performFiltering(CursorFilter.java:50)
at android.widget.Filter$RequestHandler.handleMessage(Filter.java:236)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.os.HandlerThread.run(HandlerThread.java:67)
[11-12 19:49:01.911 1723:30788 W/ActivityTaskManager]
Force finishing activity foundation.e.calendar/com.android.calendar.AllInOneActivity
[11-12 19:49:01.929 1723:3445 W/ActivityTaskManager]
enqueueAssistContext failed: caller ActivityRecord{2d81a80 u0 foundation.e.calendar/com.android.calendar.AllInOneActivity t2225 f}} is not current top ActivityRecord{9da9948 u0 amirz.shade/.ShadeLauncher t1843}
[11-12 19:49:01.929 1723:3445 W/AutofillSession]
failed to request autofill data for Token{acc8fb2 ActivityRecord{2d81a80 u0 foundation.e.calendar/com.android.calendar.AllInOneActivity t2225 f}}}
[11-12 19:49:01.946 1723:30788 D/AutofillSession]
handling death of Token{acc8fb2 ActivityRecord{2d81a80 u0 foundation.e.calendar/com.android.calendar.AllInOneActivity t2225 f}}} when saving=false
[11-12 19:49:01.946 1723:2227 I/WindowManager]
WIN DEATH: Window{875cf12 u0 foundation.e.calendar/com.android.calendar.AllInOneActivity}
[11-12 19:49:01.946 1723:5649 I/ActivityManager]
Process foundation.e.calendar (pid 15266) has died: fg TOP
[11-12 19:49:01.946 1723:2227 W/InputManager-JNI]
Input channel object ‘875cf12 foundation.e.calendar/com.android.calendar.AllInOneActivity (client)’ was disposed without first being removed with the input manager!
[11-12 19:49:01.996 1723:1870 W/WindowManager]
Failed to deliver inset state change to w=Window{875cf12 u0 foundation.e.calendar/com.android.calendar.AllInOneActivity EXITING}
android.os.DeadObjectException
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(BinderProxy.java:571)
at android.view.IWindow$Stub$Proxy.insetsControlChanged(IWindow.java:687)
at com.android.server.wm.WindowState.notifyInsetsControlChanged(WindowState.java:4045)
at com.android.server.wm.InsetsStateController.lambda$notifyPendingInsetsControlChanged$6$InsetsStateController(InsetsStateController.java:552)
at com.android.server.wm.InsetsStateController$$ExternalSyntheticLambda1.run(Unknown Source:2)
at com.android.server.wm.WindowAnimator.executeAfterPrepareSurfacesRunnables(WindowAnimator.java:345)
at com.android.server.wm.RootWindowContainer.performSurfacePlacementNoTrace(RootWindowContainer.java:887)
at com.android.server.wm.RootWindowContainer.performSurfacePlacement(RootWindowContainer.java:824)
at com.android.server.wm.WindowSurfacePlacer.performSurfacePlacementLoop(WindowSurfacePlacer.java:177)
at com.android.server.wm.WindowSurfacePlacer.performSurfacePlacement(WindowSurfacePlacer.java:126)
at com.android.server.wm.WindowSurfacePlacer.performSurfacePlacement(WindowSurfacePlacer.java:115)
at com.android.server.wm.WindowSurfacePlacer$Traverser.run(WindowSurfacePlacer.java:57)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.os.HandlerThread.run(HandlerThread.java:67)
at com.android.server.ServiceThread.run(ServiceThread.java:44)
[11-12 19:49:02.412 1723:1869 W/ActivityTaskManager]
Activity top resumed state loss timeout for ActivityRecord{2d81a80 u0 foundation.e.calendar/com.android.calendar.AllInOneActivity t-1 f}}
[11-12 19:49:03.345 1723:2623 I/ActivityTaskManager]
START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10300000 cmp=foundation.e.calendar/com.android.calendar.AllInOneActivity} from uid 10207
[11-12 19:49:03.367 1723:1878 I/ActivityManager]
Start proc 15697:foundation.e.calendar/u0a119 for pre-top-activity {foundation.e.calendar/com.android.calendar.AllInOneActivity}
[11-12 19:49:03.397 15697:15697 V/GraphicsEnvironment]
ANGLE Developer option for ‘foundation.e.calendar’ set to: ‘default’
[11-12 19:49:03.398 15697:15697 V/GraphicsEnvironment]
ANGLE GameManagerService for foundation.e.calendar: false
[11-12 19:49:03.602 1723:1866 I/ActivityTaskManager]
Displayed foundation.e.calendar/com.android.calendar.AllInOneActivity: +253ms
[11-12 19:49:03.789 11034:11034 I/GoogleInputMethodService]
GoogleInputMethodService.onStartInput():1883 onStartInput(EditorInfo{EditorInfo{packageName=foundation.e.calendar, inputType=0, inputTypeString=NULL, enableLearning=false, autoCorrection=false, autoComplete=false, imeOptions=0, privateImeOptions=null, actionName=UNSPECIFIED, actionLabel=null, initialSelStart=-1, initialSelEnd=-1, initialCapsMode=0, label=null, fieldId=16908298, fieldName=null, extras=null, hintText=null, hintLocales=}}, false)
[11-12 19:49:03.980 1723:3445 W/InputManager-JNI]
Input channel object ‘929250b Splash Screen foundation.e.calendar (client)’ was disposed without first being removed with the input manager!
```
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
/label ~"type::Bug"
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>/e/OS v1.20-rcFahim Salam Chowdhuryfahim@e.emailFahim Salam Chowdhuryfahim@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/7578eDrive doesn't always show the quota warning notification2024-02-28T14:36:12ZRomain HunaulteDrive doesn't always show the quota warning notification- /e/ version:
- Device model(s):
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
<Summarize the bug encountered briefly and precisely>
For the same account, I do not see the quot...- /e/ version:
- Device model(s):
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
<Summarize the bug encountered briefly and precisely>
For the same account, I do not see the quota warning on all my device
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
I setup my Murena cloud account on 3 devices.
My Murena cloud account is nearly full
![image](/uploads/da94b7bf6c88d680f70c08c77dbf8b75/image.png)
**What is the current behavior?**
<What actually happens>
On the older on (~starlte ~r, configured 3 years back), I see the notification "cloud storage full"
On the Pixel 4a (~sunfish ~t, configured last August) and Murena Two (~two ~t, configured during the weekend), I do not see the notification
**What is the expected correct behavior?**
Having the notification displayed, doesn't matter the device.
<What you should see instead>
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
/cc @aude @vincent @fahim44
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>/e/OS v1.20-rcFahim Salam Chowdhuryfahim@e.emailFahim Salam Chowdhuryfahim@e.email