Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2022-05-30T22:11:42Zhttps://gitlab.e.foundation/e/backlog/-/issues/2049Unexpected "Event notifications" every 6min that disappears after 1s2022-05-30T22:11:42ZIngoUnexpected "Event notifications" every 6min that disappears after 1s- /e/ version: e-0.12-q-2020110282350-dev-FP3
- Device model(s): FP3
## Summary
Every 6min there is a notification with text "Event notifications" and a calendar icon that automatically disappears after 1s.
I don't have any events in m...- /e/ version: e-0.12-q-2020110282350-dev-FP3
- Device model(s): FP3
## Summary
Every 6min there is a notification with text "Event notifications" and a calendar icon that automatically disappears after 1s.
I don't have any events in my calendar that would trigger a notification.
## The problem
**Steps to reproduce**
Simply wait (so far 6min)
**What is the current behavior?**
A notification comes up and disappears after a second.
**What is the expected correct behavior?**
That notification should not appear.
## Technical informations
**Relevant logs (`adb logcat`)**
**Relevant screenshots**
![Event_notification](/uploads/3db3dbf2f3e3b889f092fbfc2244300a/Event_notification.jpg)
## Solutions
**Workaround**
I haven't found a way to suppress that notification.
**Possible fixes**/e/OS Alicante betaNishith KhannaNishith Khannahttps://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/3738Swipe gestures doesn't work with any other launcher than Bliss2022-09-30T12:39:48ZMika LatvalaSwipe gestures doesn't work with any other launcher than Bliss- /e/ version: 0.18Q (27th august 2021)
- Device model(s): Redmi Note 8T
- Device rooted: yes (with magisk, no root privileged for apps [magisk hide needed for banking apps])
## Summary
With any other launcher than Bliss, only back ges...- /e/ version: 0.18Q (27th august 2021)
- Device model(s): Redmi Note 8T
- Device rooted: yes (with magisk, no root privileged for apps [magisk hide needed for banking apps])
## Summary
With any other launcher than Bliss, only back gesture from swipe gestures can be used. Gestures from bottom won't work. No access to homescreen or switching between apps.
Edit: Switched to 3-button mode, installed Lawnchair, enabled gestures. Now seems to work fine like this, not sure how long thought.
## The problem
**Steps to reproduce**
- Turn on Android swipe gestures
- Install some other launcher which is supposewd to work with swipe gestures
- Run launcher and test gestures, especially from bottom.
**What is the current behavior?**
Described in summary
**What is the expected correct behavior?**
All swipe gestures should work.
## 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/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/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/995contact import via vcf file to e.drive doesn't work2021-01-25T04:46:12ZJoJocontact import via vcf file to e.drive doesn't work# <Issue title>
## Summary
I have exported 780 contacts from my Huawei P10 phone via vcf export. Than I have tried to import this vcf file to my e.drive contacts. But nothing happens.
I have tried the following steps:
1. imported the v...# <Issue title>
## Summary
I have exported 780 contacts from my Huawei P10 phone via vcf export. Than I have tried to import this vcf file to my e.drive contacts. But nothing happens.
I have tried the following steps:
1. imported the vcf file to my Evolution address book on my ubuntu laptop. All 780 contacts are imported.
2. Exporting the contacts from evolution into a new vcf file
3. try to import the new vcf file on e.drive -- only 80 Contacts are imported
Than I have tried this on my own nextcloud 14 server
1. Import of the original vcf file --- failed
2. Import the new vcf file from evolution --- 779 contacts are imported -- 1 gets lost
3. Exporting the 779 contacts from my own Nextcloud server into a third vcf file
4. Importing the third vcf file into e.drive ---- 228 contacts where imported
From another user from telegram group I know, that he have had the same problem. He have tried to import 200 contacts but only 100 where really imported.https://gitlab.e.foundation/e/backlog/-/issues/708Installed apps not updated to latest version from /e/ Apps store2020-08-04T12:26:21ZMarcusInstalled apps not updated to latest version from /e/ Apps storeSeveral apps in the /e/ app store could be updated with newer versions available for a while in f-droid. However the /e/ Apps store does not suggest an update.
e.g. 30 Sep:
| App | /e/ Apps store | F-droid | Installed |
| --- | --- | -...Several apps in the /e/ app store could be updated with newer versions available for a while in f-droid. However the /e/ Apps store does not suggest an update.
e.g. 30 Sep:
| App | /e/ Apps store | F-droid | Installed |
| --- | --- | --- |---|
| Nextcloud | 3.8.0 - 24 Sep | 3.8.0 - 19 Sep | 3.7.0 |
| Riot | 0.8.28a - 27 April | 0.9.4 - 5 Sep | 0.8.28a |
| Tutanota | 3.59.14 - 27 Sep | 3.59.16 - 28 Sep | 3.59.5 |
It seems there are two separate cases:
1. The app in the /e/ App store is simply not up to date. e.g. Riot
2. The app in the /e/ App store is more up to date than the installed version but the new version is not suggested for update. e.g. Nextcloud
My phone:
- Nexus 5 - 0.7-2019092524859
- All apps mentioned installed with /e/ Apps storehttps://gitlab.e.foundation/e/backlog/-/issues/698Revolut is unusable and need urgent update2020-05-01T14:56:48ZbeletteRevolut is unusable and need urgent update![df7db84b9ff3efb4bf2efb737ce8ca08f5f8e1e5](/uploads/0716fc82111ae1daa1c25e9155b21afb/df7db84b9ff3efb4bf2efb737ce8ca08f5f8e1e5.png)
Version on /e/ store : 5.29 (502900501) Updated on 2019-08-09
Version on playstore : 6.19.2 Updated on ...![df7db84b9ff3efb4bf2efb737ce8ca08f5f8e1e5](/uploads/0716fc82111ae1daa1c25e9155b21afb/df7db84b9ff3efb4bf2efb737ce8ca08f5f8e1e5.png)
Version on /e/ store : 5.29 (502900501) Updated on 2019-08-09
Version on playstore : 6.19.2 Updated on 2019-12-03 (today)
Please update as there is no way to use Revolut outside their applicationNivesh Krishnanivesh@e.emailNivesh Krishnanivesh@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/641Redmi Note 7 Pro In Call Volume unresponsive2021-12-14T16:08:45ZjayRedmi Note 7 Pro In Call Volume unresponsive- /e/ version: 0.7-2019123035874
- Device model:Xiaomi Redmi Note 7 Pro
- When it started to occur: Since installation in November 2019
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: Not tried
## Summary
I...- /e/ version: 0.7-2019123035874
- Device model:Xiaomi Redmi Note 7 Pro
- When it started to occur: Since installation in November 2019
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: Not tried
## Summary
In Call Volume unresponsive
<Please tick one of the following sentences if relevent>
- [ 1] The device is unusable
- [ ] The bug is the source of a data loss or a big waste of time
- [ ] The bug concerns a third-party application
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
Make a call
**What is the current behavior?**
Once the call starts the volume is loud. Pressing the volume buttons produces no discernable change. There is much in call noise (interference?)
**What is the expected correct behavior?**
Volume buttons should work. In call noise should be minimal
## 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/198Unable to save birthdays for contacts on local phone account2020-05-12T19:19:11ZMarkusUnable to save birthdays for contacts on local phone account## Summary
When I try to save a contact on the Local phone account, then I am unable to specify the birthday.
This problem does not appear when I select a "/e/ Address book" or a nextcloud powered "WebDAV Address book" for storing the c...## Summary
When I try to save a contact on the Local phone account, then I am unable to specify the birthday.
This problem does not appear when I select a "/e/ Address book" or a nextcloud powered "WebDAV Address book" for storing the contact.
## Steps to reproduce
1. Start the contacts app
2. Click on the "create new contact"-icon
3. Click on "Saving to"
4. Select "Local phone account"
5. Click on "More fields"
## What is the current behavior?
There does not appear an entry field for the birthday.
## What is the expected correct behavior?
I would expect that I am able to specify a birthday for a contact.Jalon-JabugoSumit PundirSumit Pundirhttps://gitlab.e.foundation/e/backlog/-/issues/3833sync http endpoints unavailability should not pop up error messages to the fr...2022-09-23T01:04:07Ztcecyksync http endpoints unavailability should not pop up error messages to the front screen- /e/ version: 0.18
- Device model(s): any
## Summary
when cal/card/webdav sync endpoints are unavailable, Accountmanager pops the error message to the front screen.
The error message is hard for users to understand nor as with notifi...- /e/ version: 0.18
- Device model(s): any
## Summary
when cal/card/webdav sync endpoints are unavailable, Accountmanager pops the error message to the front screen.
The error message is hard for users to understand nor as with notifications easy to suppress. Unavailability is not "actionable" and not at all times relevant to the user.
## The problem
**Steps to reproduce**
1. make webdav sync endpoints unavailable in a sandbox
**What is the current behavior?**
2. accountmanager will throw errors to the screen that are hard to interpret
**What is the expected correct behavior?**
2. hide the error until a significant error counter or duration is reached
## Technical informations
see the forum issues:
- https://gitlab.e.foundation/e/backlog/-/issues/1414
- https://community.e.foundation/t/getting-frequent-http-502-bad-gateway-http-504-gateway-time-out-errors/34986
- https://community.e.foundation/t/504-http-gateway-time-out/34989
- https://community.e.foundation/t/debug-synchronization-error/35033
- https://community.e.foundation/t/http-502-bad-gateway/34984 (has screenshot)
## Solutions
**Workaround**
current sync interval are at 2 minutes for adressbook / calendar / tasks. With a longer interval span (30min) the likelihood of seeing availability problems is lessened.
**Possible fixes**
if unavailability is sustained for a longer time (1-2hrs), then maybe bubble up an notification with a helpful text ("x not synced for 1 hour"), possibly link to the status page of the service. Unavailability is not at all times relevant to the user.
The custom error page can be configured to be shown by the loadbalancer where /e/ has control or saved for the account at creation time. Exponential back-off mechanism can be used to not retry every 2 minutes to ease network load on errors.https://gitlab.e.foundation/e/backlog/-/issues/3673Apps UI colour issue: font is dark, if Rating is N/A2021-09-21T06:05:08ZŽroutíkApps UI colour issue: font is dark, if Rating is N/A- /e/ version: 0.18-q
- Device model(s): ~h850
- Device rooted: no
## Summary
Apps UI colour issue: font is dark, if Rating is N/A, see screenshots.
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
**What i...- /e/ version: 0.18-q
- Device model(s): ~h850
- Device rooted: no
## Summary
Apps UI colour issue: font is dark, if Rating is N/A, see screenshots.
## 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>
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![Screenshot_20210818-225131_Apps](/uploads/8b5d7ec8bbe59d5aacaf95901a5a8f07/Screenshot_20210818-225131_Apps.png)
![Screenshot_20210818-225150_Apps](/uploads/dbef52bf3ab8d17fcda93340683b390a/Screenshot_20210818-225150_Apps.png)
![Screenshot_20210818-225205_Apps](/uploads/4db087ebceda5814300e0448d3418f3b/Screenshot_20210818-225205_Apps.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>/e/OS v0.19Fahim Salam Chowdhuryfahim@e.emailFahim Salam Chowdhuryfahim@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/3553NextCloud symbol shown on browser for https://ecloud.global/login2022-07-07T08:03:51ZKumar AbhishekNextCloud symbol shown on browser for https://ecloud.global/login## Summary
NextCloud symbol shown on browser for https://ecloud.global/login
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. Clear the browser's cached data
1. Open the link https://ecloud.global/login
Ne...## Summary
NextCloud symbol shown on browser for https://ecloud.global/login
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. Clear the browser's cached data
1. Open the link https://ecloud.global/login
NextCloud symbol shown on browser
**What is the expected correct behavior?**
eCloud symbol should be shown on browser.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![NextCloud_in_ecloud](/uploads/4218e4a2e344f009f214a6e7abe40767/NextCloud_in_ecloud.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/3503Stop Clock translation after 60 seconds broken2022-12-02T13:20:11ZSwen GriepenStop Clock translation after 60 seconds broken- /e/ version: 0.17-p-20210530117384-dev-FP3
- Device model(s): FP3
- Device rooted: no
## Summary
<when starting the stopclock after 60 seconds the Minutes can not be read. Instead a small error message is shown, where the minutes sho...- /e/ version: 0.17-p-20210530117384-dev-FP3
- Device model(s): FP3
- Device rooted: no
## Summary
<when starting the stopclock after 60 seconds the Minutes can not be read. Instead a small error message is shown, where the minutes should be. No translation found for seconds >
## The problem
**start the stop clock and wait for 60 seconds**
<How one can reproduce the issue>
**What is the current behavior?**
<no minutes are shown after one minute>
**What is the expected correct behavior?**
<numbers should be running>
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
![Screenshot_20210716-055540_Uhr](/uploads/ddd7f050d3c67cb3f395217e9efa8dd0/Screenshot_20210716-055540_Uhr.png)
```
**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/2772v0.15 update with wrong label/no label in the system updater2021-06-17T04:11:26ZRalph Böhlkev0.15 update with wrong label/no label in the system updater- /e/ version: 0.15q
- Device model(s): Beryllium
## Summary
- Once an update is appearing in the system updater the update should be labelled correctly, in the present case /e/OS 0.15-q. Whereas in the present case it is only named /e/...- /e/ version: 0.15q
- Device model(s): Beryllium
## Summary
- Once an update is appearing in the system updater the update should be labelled correctly, in the present case /e/OS 0.15-q. Whereas in the present case it is only named /e/OS (IMG-1), so the user does not know what version exactly he/she will install
- Once the update is downloading, the version is being indicated (IMG-2, IMG-3) unfortunately it is named 0.14 instead.
- Once the update is installed the correct version naming is applied (IMG-4)
IMG-1
![208_e-0.15q-update1](/uploads/2937905a96d0edee943ec636525a33b1/208_e-0.15q-update1.jpg)
IMG-2
![209_e-0.15q-update2](/uploads/658bf34a0af444ad1c7857f53b6fd0c2/209_e-0.15q-update2.jpg)
IMG-3
![210_e-0.15q-update3](/uploads/533775b52a14c202a8a70b10a90d0ff7/210_e-0.15q-update3.jpg)
IMG-4
![211_e-0.15q-update4](/uploads/a0d98dfb95b84db66722c5b646b4364e/211_e-0.15q-update4.jpg)/e/OS v0.17 (codename w)Aayush Guptatheimpulson@e.emailAayush Guptatheimpulson@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/2582UI issue in Apps while updating apps2022-01-28T08:19:30ZGaël DuvalUI issue in Apps while updating apps- /e/ version:
- Device model(s):
## Summary
<Summarize the improvement briefly and precisely>
## Description
<What actually happens>
When updating several apps in our Apps installer, some icons turn blue without anything written in...- /e/ version:
- Device model(s):
## Summary
<Summarize the improvement briefly and precisely>
## Description
<What actually happens>
When updating several apps in our Apps installer, some icons turn blue without anything written inside while waiting update (some text is actually displayed but mostly invisible)
<What you should see instead>
Apps icons should display "Updating" or "Cancel" until they are updated and show "Open".
Also the corners should be rounded, not squared.
<Why this improvement is needed>
UI![photo5872722282806359380](/uploads/00c8064b989ebe6644fb9cd03fcc44c9/photo5872722282806359380.jpg)
## 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>
@rhunault @nivesh/e/OS v0.17 (codename w)Aayush Guptatheimpulson@e.emailAayush Guptatheimpulson@e.emailhttps://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/2076Radar COVID icon looks strange2022-09-26T01:03:43ZRomain HunaultRadar COVID icon looks strange- /e/ version: Q
- Device model(s):
## Summary
<Summarize the bug encountered briefly and precisely>
The Radar COVID icon looks strange
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
Install `Radar COVID` ...- /e/ version: Q
- Device model(s):
## Summary
<Summarize the bug encountered briefly and precisely>
The Radar COVID icon looks strange
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
Install `Radar COVID` icon.
**What is the current behavior?**
<What actually happens>
The icon in BlissLauncher grid looks strange, with some white border on top and left.
**What is the expected correct behavior?**
App icon take full space
<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>
![image](/uploads/de5f642f118497e830353f3750588047/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>https://gitlab.e.foundation/e/backlog/-/issues/1849Mail app need to be opened once to send notification2022-08-04T08:07:37ZRomain HunaultMail app need to be opened once to send notification
## Summary
<Summarize the bug encountered briefly and precisely>
Mail app need to be opened once to send notification
## The problem
**Steps to reproduce**
1. Install /e/
1. Configure an /e/ account
1. Receive an email
<How one ca...
## Summary
<Summarize the bug encountered briefly and precisely>
Mail app need to be opened once to send notification
## The problem
**Steps to reproduce**
1. Install /e/
1. Configure an /e/ account
1. Receive an email
<How one can reproduce the issue>
**What is the current behavior?**
<What actually happens>
It will not show any notification, unless you open once Mail app.
**What is the expected correct behavior?**
<What you should see instead>
Receive notifications even if Mail app was never opened.
## 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>/e/OS v1.2-rcFahim Salam Chowdhuryfahim@e.emailFahim Salam Chowdhuryfahim@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/1089Rename "Account Settings" into "Account extra Settings"2021-06-23T15:27:36ZRomain HunaultRename "Account Settings" into "Account extra Settings"- /e/ version: all
- Device model: all
- Reproducible with the last /e/ version: yes
- Reproducible with LineageOS: yes
## Summary
<Summarize the improvement briefly and precisely>
`Account Settings` opens the Account Manager UI, and ...- /e/ version: all
- Device model: all
- Reproducible with the last /e/ version: yes
- Reproducible with LineageOS: yes
## Summary
<Summarize the improvement briefly and precisely>
`Account Settings` opens the Account Manager UI, and should not be edit by the user (only if he knows what he is doing), as it can break some behavior (edrive, invitation, synchronisation etc.)
**This improvement concerns** <Tick at least one of the following choices>
- [x] UI
- [ ] Behavior
- [ ] Privacy
## Description
**What is the current behavior?**
<What actually happens>
![screenshot_20200327_18_50_57](/uploads/b84991ecd75e0e9aaeb0b974878d00e8/screenshot_20200327_18_50_57.png)
**What is the improved behavior?**
<What you should see instead>
Rename `Account Settings` into `Account extra Settings`
**What does it bring?**
<Why this improvement is needed>
Discourage to click on it.
## 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>
1. Open an ecloud account settings
1. Check that `Account Settings` is renamed into `Account extra Settings`/e/OS v0.18Seweryn FornalikSeweryn Fornalik