Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2024-02-22T13:47:45Zhttps://gitlab.e.foundation/e/backlog/-/issues/2795GS290 missing the FM App in /e/ ROM2024-02-22T13:47:45ZManoj NairGS290 missing the FM App in /e/ ROM- /e/ version: Q
- Device model(s): ~GS290
## Summary
FM Radio app is missing on /e/ ROM's
## The problem
**Steps to reproduce**
Install and Run the GS290 /e/ ROM
**What is the current behavior?**
FM Radio is missing
**What is...- /e/ version: Q
- Device model(s): ~GS290
## Summary
FM Radio app is missing on /e/ ROM's
## The problem
**Steps to reproduce**
Install and Run the GS290 /e/ ROM
**What is the current behavior?**
FM Radio is missing
**What is the expected correct behavior?**
The FM Radio seems to be working on the Stock ROM
## Technical informations
Issue raised based on [user requests from forum](https://community.e.foundation/t/fm-radio-on-gigaset-gs290/29207)
**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>https://gitlab.e.foundation/e/backlog/-/issues/1780PWA and shortcust have different appearance depending on the browser used2024-01-14T02:03:31ZAlexis NoetingerPWA and shortcust have different appearance depending on the browser used- /e/ version: 0.10-2020081067149 stable
- Device model: Samsung S9+
- When it started to occur:
- Reproducible with the last /e/ version: yes
- Reproducible with LineageOS:
## Summary
PWA or website shortcut save on the home screen do...- /e/ version: 0.10-2020081067149 stable
- Device model: Samsung S9+
- When it started to occur:
- Reproducible with the last /e/ version: yes
- Reproducible with LineageOS:
## Summary
PWA or website shortcut save on the home screen doesn't have a valid icon when saved with the /e/ browser. In comparison, PWAs and website shortcuts saved via Firefox always have an icon similar to the Android app.
<Please tick one of the following sentences if relevent>
- [ ] The device is unusable
- [ ] The bug is the source of a data loss or a big waste of time
- [x] The bug concerns a third-party application
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
go to https://community.e.foundation from the /e/ browser
Open the hamburger menu of the /e/ browser
Select 'Add to Home Screen'
Icon is hard to recognize
When trying the same steps with banking apps, the icon for the shortcut has only one capital letter
**What is the current behavior?**
Icon of the shortcut either doesn't have the right graphical elements as the Android app or shows a capital letter instead of a graphical icon.
**What is the expected correct behavior?**
Icons for shortcuts should be at least as good as the ones saved via Firefox and if possible as relevant as the icon of the original app
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
See example:
![498-1024-max](/uploads/1de701f5fae8265c4e200469f7acc7c6/498-1024-max.png)
First 2 rows are saved vie the /e/ browser
3rd and 4th rows are saved from Firefox
Shortcuts are:
https://community.e.foundation
https://tan.fr
https://mabanque.bnpparibas/fr/connexion
https://www.lachainemeteo.com/meteo-france/ville-306/previsions-meteo-nantes-aujourdhui
https://m.blablacar.fr
https://m.uber.com
https://m.twitter.com
https://particuliers.societegenerale.fr/com/icd-web/cbo/index.html
## 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>https://gitlab.e.foundation/e/backlog/-/issues/1270Update takes verly long time if the screen is off on A/B devices2023-12-01T06:15:11ZMCUpdate takes verly long time if the screen is off on A/B devices- /e/ version: FP3 alpha
- Device model: FP3
- When it started to occur: From the alpha test
- Reproducible with the last /e/ version: I dont know
- Reproducible with LineageOS:
## Summary
<Summarize the bug encountered briefly and pre...- /e/ version: FP3 alpha
- Device model: FP3
- When it started to occur: From the alpha test
- Reproducible with the last /e/ version: I dont know
- Reproducible with LineageOS:
## Summary
<Summarize the bug encountered briefly and precisely>
In the alpha test from april to may, each FP3 update took a very long time (up to two hours) when the screen was off. Whenever the screen was tapped and not turned off, it took less than 15 minutes.
<Please tick one of the following sentences if relevant>
- [ ] The device is unusable
- [x] The bug is the source of a data loss or a big waste of time
- [ ] The bug concerns a third party app
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
<How one can reproduce the issue>
Install FP3 test or alpha
<What actually happens>
Update takes hours when screen is off
<What you should see instead>
After download press install, put the phone on the table and drink a coffee, after then the phone should be updated.
## 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>https://gitlab.e.foundation/e/backlog/-/issues/779Network Cell Info lite(com.wilysis.cellinfolite): crashes at startup2023-11-19T02:03:26ZGaël DuvalNetwork Cell Info lite(com.wilysis.cellinfolite): crashes at startup- <details><summary>Third party app icon</summary>![icon](/uploads/36868d7622081d7cfaafbf582f3c7864/icon.png)</details>
App com.wilysis.cellinfo crashes at startup.
According the log this is a GMS support issue:
```01-24 15:11:54.786 ...- <details><summary>Third party app icon</summary>![icon](/uploads/36868d7622081d7cfaafbf582f3c7864/icon.png)</details>
App com.wilysis.cellinfo crashes at startup.
According the log this is a GMS support issue:
```01-24 15:11:54.786 17209 17238 W DynamiteModule: IDynamite loader version < 2, falling back to getModuleVersion2
01-24 15:11:54.786 17209 17238 D GmsDynamiteLoaderImpl: unimplemented Method: getModuleVersion for com.google.android.gms.measurement.dynamite
01-24 15:11:54.786 17209 17224 W Ads : #007 Could not call remote method. @4
01-24 15:11:54.786 17209 17224 W Ads : com.google.android.gms.internal.ads.jp: com.google.android.gms.dynamite.DynamiteModule$a: Failed to instantiate module class: com.google.android.gms.ads.measurement.DynamiteMeasurementManager
01-24 15:11:54.786 17209 17224 W Ads : at com.google.android.gms.internal.ads.hp.a(SourceFile:2)
01-24 15:11:54.786 17209 17224 W Ads : at com.google.android.gms.internal.ads.nb.b(SourceFile:11)
01-24 15:11:54.786 17209 17224 W Ads : at com.google.android.gms.internal.ads.ob.run(Unknown Source:4)
01-24 15:11:54.786 17209 17224 W Ads : at java.lang.Thread.run(Thread.java:764)
01-24 15:11:54.786 17209 17224 W Ads : Caused by: com.google.android.gms.dynamite.DynamiteModule$a: Failed to instantiate module class: com.google.android.gms.ads.measurement.DynamiteMeasurementManager
01-24 15:11:54.786 17209 17224 W Ads : at com.google.android.gms.dynamite.DynamiteModule.a(SourceFile:130)
01-24 15:11:54.786 17209 17224 W Ads : at com.google.android.gms.internal.ads.hp.a(SourceFile:1)
01-24 15:11:54.786 17209 17224 W Ads : ... 3 more
01-24 15:11:54.786 17209 17224 W Ads : Caused by: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gms.ads.measurement.DynamiteMeasurementManager" on path: DexPathList[[zip file "/data/app/com.wilysis.cellinfolite-b4lnrd_CAge-64-ho2-FBw==/base.apk"],nativeLibraryDirectories=[/data/app/com.wilysis.cellinfolite-b4lnrd_CAge-64-ho2-FBw==/lib/arm64, /system/lib64, /vendor/lib64]]
01-24 15:11:54.786 17209 17224 W Ads : at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:125)
01-24 15:11:54.786 17209 17224 W Ads : at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
01-24 15:11:54.786 17209 17224 W Ads : at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
01-24 15:11:54.786 17209 17224 W Ads : at com.google.android.gms.dynamite.DynamiteModule.a(SourceFile:128)
01-24 15:11:54.786 17209 17224 W Ads : ... 4 more
01-24 15:11:54.825 1074 4882 I WifiService: isScanAlwaysAvailable uid=10076
01-24 15:11:54.825 17209 17252 I Ads : App measurement is starting up, version: 16250
01-24 15:11:54.825 1074 4882 I WifiService: getSupportedFeatures uid=10076https://gitlab.e.foundation/e/backlog/-/issues/503Echo in calls with speaker2023-11-16T11:06:42ZAnthony ScemamaEcho in calls with speaker**Issue details**
Some Galaxy S7 users have complained of an echo at the call receiver’s end. The caller would not be aware of the issue unless the person on the other side of the call complains.
Some of these devices were purchased f...**Issue details**
Some Galaxy S7 users have complained of an echo at the call receiver’s end. The caller would not be aware of the issue unless the person on the other side of the call complains.
Some of these devices were purchased from the Murena Store.
**Investigation**
The development team did a detailed analysis of the issue and has arrived at the following conclusions.
- The issue is due to incompatibility between the hardware and the software which assists in the noise cancellation.
- This problem does not impact all users of this phone.
- The Galaxy S7 devices in question are from 2016 and have stopped receiving firmware updates by the vendor since 2019… This effectively means there will be no vendor patches for the device any longer.
**Solutions tried**:
- Debugging: No positive results to report despite exhaustive efforts.
- OS upgrade: The S7 was released with Android 7 (also called Nougat) and thanks to the /e/OS developers was upgraded to /e/OS based on Android 10 (also called Q). Unfortunately, this has not resolved the echo issue.
- Use different firmware version: no result
- Play with audio configuration: no result
**Action to be taken**
- Based on these findings, the development team has concluded that it would not be possible to resolve the echo related issue in the affected Galaxy S7 devices.
- The echo issue related bugs in GitLab raised for this hardware will be closed with these findings.
**Learning from this exercise**
- The Murena store has stopped sourcing and selling this model
- Testing of builds and newer devices includes test cases to check for echo on receiver side.
- Testing teams to include volunteers spread across different regions and service providers
**Remedial Step(s)**
Use of headphone has been reported by some users as a possible solution to this problem
Linked to the following community announcement: https://community.e.foundation/t/issue-with-echo-heard-by-call-receivers-on-some-galaxy-s7-devices/47965
<details><summary>Initial issue description</summary>
If I use the speaker of the phone when making a call, the other person hears an echo of her voice.
Samsung Galaxy S7 sold by /e/
SM-G930F
Version 0.7-2019062814891
</details>https://gitlab.e.foundation/e/backlog/-/issues/1860Files app changes date-time fingerprint when moving files (it especially mess...2023-10-25T07:49:12ZŽroutíkFiles app changes date-time fingerprint when moving files (it especially messes up the Timeline for images in the Gallery app)
## Summary
Files app changes date-time fingerprint when moving files (it especially messes up the Timeline for images in the Gallery app)
## The problem
**Steps to reproduce**
Move an older image (photo or screenshot) to a new folde...
## Summary
Files app changes date-time fingerprint when moving files (it especially messes up the Timeline for images in the Gallery app)
## The problem
**Steps to reproduce**
Move an older image (photo or screenshot) to a new folder using the Files app.
* Check the Details for the file moved
* Check the Gallery's Timeline
**What is the current behavior?**
* The Details of the moved file/image read a recent date and time
* The moved image is displays as first in the Timeline in the Gallery.
**What is the expected correct behavior?**
The date and time shall not be updated to the moved files and images. It is an unorthodox behavior across many OS.
The moved image shall not be showed as first in the Timeline. It was not created or manipulated recently. It was only assigned a different location within the filesystem.
The date that should be taken into account for a picture in ~"/e/OS Gallery" and ~"/e/OS File manager" is the one set in `Taken on` and not the one set in `Last modified on`;\
![Screenshot_20221101-124517_Files](/uploads/24bf067c1832ca300ad94e72c658f037/Screenshot_20221101-124517_Files.png)
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
None to my knowledge
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>/e/OS v1.16-rcAbhishek AggarwalAbhishek Aggarwalhttps://gitlab.e.foundation/e/backlog/-/issues/548Factory reset do not remove pictures2023-10-20T09:59:56ZVincent BourgmayerFactory reset do not remove pictures# Factory reset do not remove pictures
## Summary
When performing a factory reset, after the reboot, Images were still present
## Steps to reproduce
1- take photos
2- Go into Settings to perform a factory reset.
3- wait for the phone t...# Factory reset do not remove pictures
## Summary
When performing a factory reset, after the reboot, Images were still present
## Steps to reproduce
1- take photos
2- Go into Settings to perform a factory reset.
3- wait for the phone to reboot.
4- Check your gallery.
## What is the current behavior?
After the reboot due to factory reset, if you check you gallery you'll see that your photos are still there.
## What is the expected correct behavior?
All photos should have been removed too.
## Relevant logs and/or screenshots
None.
## Possible fixes
No idea at the momenthttps://gitlab.e.foundation/e/backlog/-/issues/925Deletion of paused system updated is not intuitive2023-10-06T15:19:40ZMarkusDeletion of paused system updated is not intuitiveIn order to delete a paused update the user has to long-press on the paused update, which is not very intuitive.
To trigger this issue:
1. Start to download a system update
2. Pause the download before it is finished
3. Wait until the n...In order to delete a paused update the user has to long-press on the paused update, which is not very intuitive.
To trigger this issue:
1. Start to download a system update
2. Pause the download before it is finished
3. Wait until the next system update is available
4. Download and install the new system update
![Screenshot_20181013-085731](/uploads/68c142bd206116926d89a57b05bb6ed9/Screenshot_20181013-085731.png)
Pressing the "Resume" button just opens a notification:
![Screenshot_20181013-092306](/uploads/7b29e59fdf51306d5156b92bcd0e6cc5/Screenshot_20181013-092306.png)
When a newer update is installed I would expect that the "Resume" button is replaced by a "Delete" button, since the "Resume" button has no functionality in this case.https://gitlab.e.foundation/e/backlog/-/issues/808weather source crashes app2023-07-25T10:54:02ZXavier Griffinweather source crashes appwhenever I choose the weather source, it crashes the app. Please help.whenever I choose the weather source, it crashes the app. Please help.https://gitlab.e.foundation/e/backlog/-/issues/2513Bad display of the update search frequency in the Updater settings2023-05-31T01:03:26ZAnonymeBad display of the update search frequency in the Updater settings- /e/ version: all
- Device model(s): all (here on the GS290, latest stable)
## Summary
<Summarize the bug encountered briefly and precisely>
The "Auto updates check" string in Updater's preferences is partially hidden. So both in Eng...- /e/ version: all
- Device model(s): all (here on the GS290, latest stable)
## Summary
<Summarize the bug encountered briefly and precisely>
The "Auto updates check" string in Updater's preferences is partially hidden. So both in English and in French, we can't know if it's set to Once a day, a week or a month unless we go into landscape mode, or unless we select again the option we want.
## The problem
**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>
We should be able to directly see what is the selected behavior.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
![Screenshot_20210206-092718_Updater](/uploads/3b6099a04d6d1c541e4e198d7eb59bbd/Screenshot_20210206-092718_Updater.png)
![Screenshot_20210206-092746_Gestionnaire_de_mise_à_jour](/uploads/a169f65eead5ea160739a5c5310468b5/Screenshot_20210206-092746_Gestionnaire_de_mise_à_jour.png)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
Put the device in lanscape mode
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
Replace the current string from > to:
ENGLISH
- Once a day > Daily ([Weblate](https://i18n.e.foundation/translate/e/android_packages_apps_updater/en/?checksum=b717b4e28a8e80fd))
- Once a week > Weekly ([Weblate](https://i18n.e.foundation/translate/e/android_packages_apps_updater/en/?checksum=9a76db7253dc1085))
- Once a month > Monthly ([Weblate](https://i18n.e.foundation/translate/e/android_packages_apps_updater/en/?checksum=d5bf83fca7f21b24))
FRENCH
- Une fois par jour > Quotidiennement ([Weblate](https://i18n.e.foundation/translate/e/android_packages_apps_updater/fr/?checksum=b717b4e28a8e80fd))
- Une fois par semaine > Hebdomadaire ([Weblate](https://i18n.e.foundation/translate/e/android_packages_apps_updater/fr/?checksum=9a76db7253dc1085))
- Une fois par mois > Mensuel ([Weblate](https://i18n.e.foundation/translate/e/android_packages_apps_updater/fr/?checksum=d5bf83fca7f21b24))
(I already modified and saved the modification in French)https://gitlab.e.foundation/e/backlog/-/issues/3792The colour of the update download progress bar in Notifications is not consis...2023-04-24T01:03:30ZŽroutíkThe colour of the update download progress bar in Notifications is not consistent (is darker) with the style colour- /e/ version: 0.18-q
- Device model(s): ~h850
- Device rooted: no
## Summary
The colour of the update download progress bar in Notifications is not consistent (is darker) with the style colour. The colour shall match the chosen colour...- /e/ version: 0.18-q
- Device model(s): ~h850
- Device rooted: no
## Summary
The colour of the update download progress bar in Notifications is not consistent (is darker) with the style colour. The colour shall match the chosen colour style.
## The problem
**Steps to reproduce**
Check the colour of the download progress bar in Notification at downloading OS release. Compare with the colour of the download progress bar else, in the appropriate section in Settings.
**What is the current behavior?**
I'm not sure yet in the default colour (blue-greenish), but the chosen pink is darker in the progress bar definitely
**What is the expected correct behavior?**
The colour of the progress bar matches the OS style.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
Colour in Settings matches the OS style.
![Screenshot_20210908-202223_Updater](/uploads/1716c479bc1247e9a4164491cde3d4c2/Screenshot_20210908-202223_Updater.png)
Colour in Notification is darker.
![Screenshot_20210908-202209_Browser](/uploads/7d9098f6993538fc698f4d6142f17d09/Screenshot_20210908-202209_Browser.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>https://gitlab.e.foundation/e/backlog/-/issues/4058Dialer app - dark mode -2023-04-15T01:03:37ZJannesDialer app - dark mode -- /e/ version: pie
- Device model(s):mido,x00td
- Device rooted: no
## Summary
calling accounts and accesibility menu points still appear in white
## The problem
**Steps to reproduce**
on pie open dialer app go to settings open cal...- /e/ version: pie
- Device model(s):mido,x00td
- Device rooted: no
## Summary
calling accounts and accesibility menu points still appear in white
## The problem
**Steps to reproduce**
on pie open dialer app go to settings open calling accounts or accesibility menupoints
**What is the current behavior?**
When dark mode is applied the menu points remain light
**What is the expected correct behavior?**
those menu points should turn dark when applying dark mode
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![Screenshot_20211026-132257_Phone_Services](/uploads/58534e4b4e395c99da1be013084734db/Screenshot_20211026-132257_Phone_Services.png)![Screenshot_20211026-132304_Phone_Services](/uploads/e33c09bfa916276ee9f214431f8b95b5/Screenshot_20211026-132304_Phone_Services.png)
<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>https://gitlab.e.foundation/e/backlog/-/issues/586Battery notification sounds played at Ring volume2023-04-04T05:32:28ZSylvain Manceausylvain@murena.ioBattery notification sounds played at Ring volume## Summary
<Summarize the improvement briefly and precisely>
Charging notification volume doesn't follow the appropriate value.
## Description
**What is the current behavior?**
Ensure **Settings** > **Sounds** > **Advanced** > **Cha...## Summary
<Summarize the improvement briefly and precisely>
Charging notification volume doesn't follow the appropriate value.
## Description
**What is the current behavior?**
Ensure **Settings** > **Sounds** > **Advanced** > **Charging Sounds** is enabled
Change Notification volume, plug and unplug the device. It doesn't change anything
Change Ring volume, plug and unplug the device. This time you realize that Charging notification follow the ring volume
**What is the improved behavior?**
<What you should see instead>
Charging notification volume follow the notification volume.
**What does it bring?**
<Why this improvement is needed>
It looks more appropriate.
## 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>https://gitlab.e.foundation/e/backlog/-/issues/1519New Icon - size inconsistency in settings2023-04-03T01:03:27ZGaël DuvalNew Icon - size inconsistency in settings- /e/ version: 0.9-20200701 (stable)
- Device model: FP3
- When it started to occur: latest stable
- Reproducible with the last /e/ version: 0.9-20200701 (stable)
- Reproducible with LineageOS:
## Summary
Icon size is different in sub ...- /e/ version: 0.9-20200701 (stable)
- Device model: FP3
- When it started to occur: latest stable
- Reproducible with the last /e/ version: 0.9-20200701 (stable)
- Reproducible with LineageOS:
## Summary
Icon size is different in sub categories than in main settings view
**This improvement concerns** <Tick at least one of the following choices>
- [x] UI
- [ ] Behavior
- [ ] Privacy
## Description
**What is the current behavior?**
Icon size is different in sub categories than in main settings view
![size](/uploads/52d2509b05ef32056462aebf38338009/size.png)
**What is the improved behavior?**
!(Icon size is different in sub categories than in main settings view)
**What does it bring?**
UI consistency
## 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>https://gitlab.e.foundation/e/backlog/-/issues/2147additional system languages with strange names proposed by the system2023-03-31T01:03:32ZRalph Böhlkeadditional system languages with strange names proposed by the system- /e/ version: e-0.12-pie-20201029
- Device model(s): Santoni
## Summary
When adding another language to the system in most cases 2 languages are suggested with strange names (could be some Chinese and English/Chinese). No obvious reas...- /e/ version: e-0.12-pie-20201029
- Device model(s): Santoni
## Summary
When adding another language to the system in most cases 2 languages are suggested with strange names (could be some Chinese and English/Chinese). No obvious reasons why those ones are being proposed
The same behavior appeared as well with other devices (Pie)
[179_strange-lng-logcat_11-21-2020_23-52-06.txt](/uploads/2b42924ef82d9a3319536bf58b5b3e67/179_strange-lng-logcat_11-21-2020_23-52-06.txt)
![178_strange-lng](/uploads/e47271537ffc28d4c8cbeecfe042266e/178_strange-lng.jpg)https://gitlab.e.foundation/e/backlog/-/issues/862Setting "showPicturesEnum" should default to NEVER2023-03-26T01:03:22ZAxel NapolitanoSetting "showPicturesEnum" should default to NEVERShowing images in E-Mails may violate privacy of users. Remote access to resources like images may be recorded, analyzed and abused to monitor activity of the user. Avoiding the loading of those images would improve privacy of a user.
C...Showing images in E-Mails may violate privacy of users. Remote access to resources like images may be recorded, analyzed and abused to monitor activity of the user. Avoiding the loading of those images would improve privacy of a user.
Currently the default setting is "ALWAYS" which means, that resources will be always loaded, which may violate privacy of the user if not manually changed. The default setting should be changed to "NEVER" which denies loading of remote resources like images by default - users may then individually decide to load those resources anyway by simply pressing the according button in the mail view. This improves privacy and gives back control to user.
**Affected files:**
* k9mail/src/main/java/io/eelo/mail/preferences/AccountSettings.java
* k9mail/src/main/java/io/eelo/mail/Account.java
**Proposed changes:**
In: k9mail/src/main/java/io/eelo/mail/preferences/AccountSettings.java
Change:
```java
s.put("showPicturesEnum", Settings.versions(
new Settings.V(1, new Settings.EnumSetting<>(Account.ShowPictures.class, Account.ShowPictures.ALWAYS))
));
```
To:
```java
s.put("showPicturesEnum", Settings.versions(
new Settings.V(1, new Settings.EnumSetting<>(Account.ShowPictures.class, Account.ShowPictures.NEVER))
));
```
In: k9mail/src/main/java/io/eelo/mail/Account.java
Change:
```java
showPictures = ShowPictures.ALWAYS;
```
To:
```java
showPictures = ShowPictures.NEVER;
```
AND
Change:
```java
showPictures = Preferences.getEnumStringPref(storage, accountUuid + ".showPicturesEnum", ShowPictures.ALWAYS);
```
To:
```java
showPictures = Preferences.getEnumStringPref(storage, accountUuid + ".showPicturesEnum", ShowPictures.NEVER);
```
**Additional todos:**
Test cases should be added.
Patch:
[0001-Set-default-preference-for-ShowPicture-to-NEVER.patch](/uploads/3b6a39abf2cec6d990da2e50880cc1dd/0001-Set-default-preference-for-ShowPicture-to-NEVER.patch)Quitohttps://gitlab.e.foundation/e/backlog/-/issues/1213Clock ask for permission2023-03-20T02:03:23ZRomain HunaultClock ask for permission- /e/ version: pie
- Device model: all pie
- Reproducible with the last /e/ version: yes
- Reproducible with LineageOS:
## Summary
<Summarize the improvement briefly and precisely>
At first start, Clock app ask for a permission
**Thi...- /e/ version: pie
- Device model: all pie
- Reproducible with the last /e/ version: yes
- Reproducible with LineageOS:
## Summary
<Summarize the improvement briefly and precisely>
At first start, Clock app ask for a permission
**This improvement concerns** <Tick at least one of the following choices>
- [ ] UI
- [ ] Behavior
- [ ] Privacy
## Description
**What is the current behavior?**
<What actually happens>
On a fresh install, Clock ask for `Set and clear the alarm which will wake up device from the power off state` permission.
**What is the improved behavior?**
<What you should see instead>
Clock doesn't ask for any permission, which are all given by default for default apps.
**What does it bring?**
<Why this improvement is needed>
Less confusion for users
## 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>https://gitlab.e.foundation/e/backlog/-/issues/4049"Apps" app not deleting app update packages2023-03-12T02:21:37ZRaphaël Ochsenbein"Apps" app not deleting app update packages- /e/ version: 0.10
- Device model(s): Galaxy A3 (2017)
- Device rooted: yes/no ??
## Summary
I noticed that “Apps” store was taking up a lot of space, almost 6GB today (after ~half a year of /e/ usage) and I wasn’t sure if you can del...- /e/ version: 0.10
- Device model(s): Galaxy A3 (2017)
- Device rooted: yes/no ??
## Summary
I noticed that “Apps” store was taking up a lot of space, almost 6GB today (after ~half a year of /e/ usage) and I wasn’t sure if you can delete that, or if it’s being used by other apps. I didn’t find information on this. I turns out you can - it seems those 6GB of data were app-update packages, that you obviously don’t need any more after updating.
Settings > Storage > Internal shared storage > Other apps > Apps > Clear storage.
## The problem
User tcecyk from the e community forum analyzed the problem some more:
> Space usage comes from former install folders listing its sub-apks within “XAPK Installer-release/temp/..” at
>
> /storage/emulated/0/Android/data/foundation.e.apps/files
>
> I guess the code doesn’t handle yet the cleanup after installing from those extracted XAPKs. The entries get created within installSplitApks() in app/src/main/java/foundation/e/apps/xapk/XApkInstallUtils.kt · fe80a4c9 · e / apps / Apps · GitLab 1
>
> (Cleaning up after regular .apk installs was done in Some APK are still available in Download (#1634) · Issues · e / Backlog · GitLab 2)https://gitlab.e.foundation/e/backlog/-/issues/838Vertical stack view of recents apps after removing Launcher32023-03-10T02:03:24ZAmit Kumaramitkma@e.emailVertical stack view of recents apps after removing Launcher3## Summary
After removing Launcher3, the recent apps view converted to default vertical stack instead of much sophisticated horizontal side by side view.
## Steps to reproduce
Remove the Launcher3 apk, the recent apps view has been cha...## Summary
After removing Launcher3, the recent apps view converted to default vertical stack instead of much sophisticated horizontal side by side view.
## Steps to reproduce
Remove the Launcher3 apk, the recent apps view has been changed to default.
## Expected Behaviour
Horizontal side by side view should be shown for recent apps.
## Possible Fixes
Import `quickstep` module from Launcher3 package and make it compatible with BlissLauncherhttps://gitlab.e.foundation/e/backlog/-/issues/636Bad sound when using loudspeaker2023-03-08T02:03:21ZDieudonnéBad sound when using loudspeakerWhen using loudspeaker when making a phone call, the person called hears his own voice distorted and very unpleasant.When using loudspeaker when making a phone call, the person called hears his own voice distorted and very unpleasant.