Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2024-02-28T16:59:23Zhttps://gitlab.e.foundation/e/backlog/-/issues/7538spellcheck switch off doesn't work2024-02-28T16:59:23ZA Fspellcheck switch off doesn't work- /e/ version: 1.16-s-20231017342507-stable-FP4
-s-- Device model(s): FP4
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
I switched the spellcheck / automatic correction off (settings/system...- /e/ version: 1.16-s-20231017342507-stable-FP4
-s-- Device model(s): FP4
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
I switched the spellcheck / automatic correction off (settings/system/languages/tools). I use German language.
So the device should not change the words I type, but it still does! No matter which app I use.
## The problem
**Steps to reproduce**
always
**What is the current behavior?**
the words I type are automatically change into a correction (spellcheck) after i type [space] - although this setting is switched off
**What is the expected correct behavior?**
no change no matter what I type
<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>
<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/7716In Message App: some history and contact became unavailable and unusable (can...2024-02-28T16:42:08ZBrunoIn Message App: some history and contact became unavailable and unusable (cannot send SMS to them anymore)- /e/ version: 1.19.1
- Device model(s): FP4 (bought from murena.com)
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Since some week I am unable to see SMS history for **some** contacts in ...- /e/ version: 1.19.1
- Device model(s): FP4 (bought from murena.com)
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Since some week I am unable to see SMS history for **some** contacts in Message app. Most of them work well, but **some** of them are completely unavailable and more important unsable **at all** (cannot send them messages).
## The problem
**Steps to reproduce**
1. Open Messages app
2. Look for some contact (JK in the first screenshot)
**What is the current behavior?**
1. Open the history in order to view it and to send him a message
- text area is unusable
- few seconds after I got a message stating that the Message app (as in the second screenshot) is stalled (click on waiting do not change anything)
**What is the expected correct behavior?**
1. I should view the message history, be able to input text and send it to my contact
## Technical informations
**Relevant screenshots**
1. ![Screenshot_20240127-151157_Message](/uploads/c96d6f6d25301ec178cbf6bddfddb7c6/Screenshot_20240127-151157_Message.png)
2. ![Screenshot_20240127-151132_Message](/uploads/2efe402987a1c537b96414557395a7e2/Screenshot_20240127-151132_Message.png)
## Solutions
**Workaround**
None as of today
**Possible fixes**
None as of today
~"type::Bug" ~"/e/OS Message" ~Regression ~FP4https://gitlab.e.foundation/e/backlog/-/issues/7675Murena 2 display issues2024-02-28T16:35:06ZHaydee ElizondoMurena 2 display issuesSelect a template in the above field according to what you want to do: report a bug, suggest an improvement or propose a feature :)Select a template in the above field according to what you want to do: report a bug, suggest an improvement or propose a feature :)https://gitlab.e.foundation/e/backlog/-/issues/770526th Feb 20242024-02-28T15:33:04ZKumar Abhishek26th Feb 2024- [x] 25% availability of ~t dev builds except :warning: ~FP3
- [x] 100% availability of ~s dev builds
- [x] 100% availability of ~r dev builds
- [x] Open upgrade for ~herolte stable builds from ~q to ~r
- [ ] ~~Release to flash statio...- [x] 25% availability of ~t dev builds except :warning: ~FP3
- [x] 100% availability of ~s dev builds
- [x] 100% availability of ~r dev builds
- [x] Open upgrade for ~herolte stable builds from ~q to ~r
- [ ] ~~Release to flash stations for ~s, ~r dev builds (if applicable)~~
- [x] 25% availability of ~s stable builds
- [x] 25% availability of ~r stable builds
- [x] 25% availability of ~s partner builds/e/OS v1.20Alexandre RouxSayantan RoychowdhuryAlexandre Roux2024-02-26https://gitlab.e.foundation/e/backlog/-/issues/7702Release 1.202024-02-28T14:44:28ZKumar AbhishekRelease 1.20# đ Tasks
* [ ] Release notes
* [x] Validation of %"/e/OS v1.20-beta"
* [x] Run dev builds about %"/e/OS v1.20-beta"
* [x] Share https://gitlab.e.foundation/e/qa/testing-community/-/issues/65 with testing community
* [x] Validation of...# đ Tasks
* [ ] Release notes
* [x] Validation of %"/e/OS v1.20-beta"
* [x] Run dev builds about %"/e/OS v1.20-beta"
* [x] Share https://gitlab.e.foundation/e/qa/testing-community/-/issues/65 with testing community
* [x] Validation of %"/e/OS v1.20-rc"
* [x] Validation of %"/e/OS v1.20-rc.2"
* [x] Validation of %"/e/OS v1.20"
/cc @nicofonk/e/OS v1.20https://gitlab.e.foundation/e/backlog/-/issues/7663Media player in notification stuck on previous sound / does not work2024-02-28T12:44:44Zwil zutMedia player in notification stuck on previous sound / does not work- e/os/ version : 1.17-s-dev
- device model(s): OnePlus 6 enchilada
- Developer mode enabled: yes
- Device rooted: yes
- Trackers blocker enabled: yes
## Summary
When I play a music for the first time with spotify for example, the medi...- e/os/ version : 1.17-s-dev
- device model(s): OnePlus 6 enchilada
- Developer mode enabled: yes
- Device rooted: yes
- Trackers blocker enabled: yes
## Summary
When I play a music for the first time with spotify for example, the media player works normally.
Then if I stop listening to music, kill spotify app etc. and start to listen to music again later, the media player does not appear in fixed notifications.
And if I fully scroll to bottom to see it, it is stuck on the previous song and is not synced anymore with spotify
## The problem
**Steps to reproduce**
- Play a song with Spotify
- Stop the music
- Kill the app
- Relaunch spotify app and restart a music
- The media player does not appear
**What is the current behavior?**
The media player does not appear when playing music for the second, third, ... time
Fun and strange thing, I can click on play / pause and it works, but the player still shows the previous played sound (see the recorded video, it shows Roddy Ricch but I am listening to bbno$)
**What is the expected correct behavior?**
The media player should be visible when I scroll down to see notifications, and it should be synced with the currently playing music
<!--
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
-->
**Relevant screenshots**
![screen-20240108-105331](/uploads/d3fd8dd925978de424fe1dd5580bb0dd/screen-20240108-105331.mp4)
## Solutions
**Workaround**
When i restart the phone it works again but only the first time
**Possible fixes**
đ¤ˇ
<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/360[Feature Proposal] Parental control / junior digital wellbeing2024-02-28T09:38:21ZRalph BĂśhlke[Feature Proposal] Parental control / junior digital wellbeing# (Issue title)
[Feature Proposal] Parental control / junior digital wellbeing
## Context
Children starting to use and own smartphones earlier and earlier.
There is not a single answer on the question *What's the right way of using ...# (Issue title)
[Feature Proposal] Parental control / junior digital wellbeing
## Context
Children starting to use and own smartphones earlier and earlier.
There is not a single answer on the question *What's the right way of using a smartphone?*, as it involves a broad knowledge - for instance content related or technical understanding. So, exposing juniors to IT gear always requires face-to-face-time together, explanations and guidance. But some technical support in this can be quite helpful as the *adult* discussion on *digital wellbeing* is showing.
The purpose of such kind of feature for kids should not be in anyway to spy on a kid, but to set certain limits to early age smartphone users. Therefore I am proposing a JUNIOR DIGITAL WELLBEING feature built-in /e/.
Furthermore, extending the target group of /e/ from (the often mentioned) âMums and Dadsâ to youngsters, could ease the media visibility of the system: /e/ as a privacy enabling OS and/or a child OS.
## Feature Overview
**What this Junior Digital Wellbeing should offer:**
- Defining usage time for the device and specific apps.
- Blacklisting / Whitelisting certain apps/app groups & locking APK installation.
- Visualising usage behaviour/time per app/app group/device for 1/7/15 day(s).
- Extending usage time (exceptions) by for instance 15min app/device.
**What this Junior Digital Wellbeing should NOT offer:**
- Geographically locating or geofencing the junior.
- Providing detailed communication logs to parents.
- Webfiltering.
## Proposed features 1
- **Introducing a parental (control) section** in device settings (to be password locked). Right there, various parameters can be set (all directly at the youngsters phone).
- **Settings:** Restrict (on/off) display of app in Bliss.
- **Settings:** Restrict (on/off) installation of APKs (with blacklisting and whitlelisting capabilities, especially whitelisting Open Source apps).
- **Settings:** Restrict (on/off) usage of Bluetooth, camera, GPS, microphone, mobile data, NFC and Wifi. Mobile data ideally allow to set a quota.
- **Settings:** Time limit of usage of the device per day and/or per app/day. Junior user with get notifications 5 minutes before the limit is reached.
- **Settings:** Set downtime of the device (over night) - eventually: only calls and SMS would be permitted for pre-defined contacts, like parents for emergency.
- **Feature (on/off):** Permitting junior user to get 15mins extra per app/ phone (in case itâs needed). This extra time could be deducted from tomorrows time account.
In the Parental Control tab this extra time would be notified.
- **Feature:** Change the default extra-time (15min) to something else.
- **Feature:** Simple unlock of the phone with the parental password (on/off/24h).
- **Display:** Usage time left and history of the time per application over the last 7 days with details for each day (maybe in a Bliss widget).
- **Display:** For transparency reasons, in the Parental Control section the junior user has to be able to see all the settings, but of course not be able to change them without the parent password.
All features proposed above could be set directly on the junior user's phone,
## Proposed features 2 (some additional thoughts)
I was talking to some other parents using Parental Control services.
- Most of them were on the iOS, so they used the integrated Screen Time feature. They confirmed that it is an easy to use and well working service.
- But: They underlined the importance of remotely modify the settings from their own phone (this is not part of the above mentioned list of proposed features 1). Especially: Parents should be able to remotely oversee the juniors usage behaviour and to remotely grant extra time to the junior user from their own phone. And moreover: their kids would not be keen at all on handing over their phones to their parents to get some settings modified.
These features might not get along with the *My data is MY data* philosopy, that's why they are presented in a separate section. This probably requires some furhter thinking.
## Notes:
- **Competitors:** various. Most of them are tracker and ad stuffed. Otherwise, there is one little offer on a privacy respecting and easy to use parental control tools.
Among the promising alternatives there are two worth mentioning:
Apple introduced (easy to use) child safety features on OS level straight into iOS12. For Android there is a (not very user friendly but Open Source) app named TimeLimit.
- **Android Pie:** JUNIOR DIGITAL WELLBEING features could be thought as part of the digital wellbeing features, as they were introduced with Android Pie.
## References:
- **TimeLimit**
https://timelimit.io/en & https://gitlab.com/timelimit.io/opentimelimit-android/tree/HEAD & https://fossdroid.com/a/timelimit.html
- **iOS/Parental Control**
https://support.apple.com/en-us/HT201304, https://www.youtube.com/watch?v=ZAXcyGw8Q2Y, https://www.youtube.com/watch?v=0agSm9AmuGg
- **Android Pie/Digital Wellbeing**
https://mashtips.com/google-digital-wellbeing/
This feature proposition is based on a discussion (late May 2019) in the Community Forum https://community.e.foundation/t/child-safety-features-in-e-some-thoughts/3960
Thank you donut3, haggisns, VitTh, willisama, Manoj and in particular Anonyme for your valuable input.https://gitlab.e.foundation/e/backlog/-/issues/7645Easy Installer always delivers Stable build ? - No, sometimes dev2024-02-28T03:12:35ZIain Brown DouglasEasy Installer always delivers Stable build ? - No, sometimes dev- ~"Easy-installer"
- Device model(s): ~guacamole ~instantnoodle ~instantnoodlep ~coral ~sunfish ~bramble ~flame
## Summary
This is a request for clarification ~"Documentation"
## Description
We understand from current documentation ...- ~"Easy-installer"
- Device model(s): ~guacamole ~instantnoodle ~instantnoodlep ~coral ~sunfish ~bramble ~flame
## Summary
This is a request for clarification ~"Documentation"
## Description
We understand from current documentation that Easy Installer is expected to install a stable build.
These commits July 29 2023: https://gitlab.e.foundation/e/devices/easy-installer/-/commits/40f995f9771f6804d8a089ae58b7230db6538038
contain in the title **"Promote to S and switch to dev build"**.
I believe the above list of affected devices may be incomplete as one or more devices may have been changed to receive dev previously.
**What change is required?**
Small changes to documentation to make potential users aware that Easy Installer will deliver stable or dev, device dependent.
A slot in the forum "Development and Testing Updates" https://community.e.foundation/tag/development-updates might be sufficient.
### Examples
In this forum post the user was adversely affected. https://community.e.foundation/t/unable-to-install-e-on-oneplus-8-with-easyinstaller/54360/
##
~"type::Improvement" ~"type::Documentation"Easy Installer v0.21Manoj NairManoj Nairhttps://gitlab.e.foundation/e/backlog/-/issues/7533Easy Installer - Error while downloading e-latest-rflame2024-02-27T17:07:59ZV SEasy Installer - Error while downloading e-latest-rflameHi there, it is been nearly a couple of ours waiting and there is nothing going on since the first time I ran the Easy installer.
It is not an Internet issue. Certainly I do not understand why the download does not start.
I'm about to in...Hi there, it is been nearly a couple of ours waiting and there is nothing going on since the first time I ran the Easy installer.
It is not an Internet issue. Certainly I do not understand why the download does not start.
I'm about to install e/OS on a Pixel 4.
Thanks for your help!
[Screenshot](/uploads/bc376c13dc2bc4a9c60bb3dde62285e9/Captura_de_Pantalla_2023-11-16_a_les_14.48.07.png)Easy Installer v0.21https://gitlab.e.foundation/e/backlog/-/issues/7243Easy Installer not working for Teracube 2e (Zirconia)2024-02-27T17:05:15ZKen MillerEasy Installer not working for Teracube 2e (Zirconia)- /e/ version: 1.13
- Device model(s): Teracube 2e Zirconia (aka 2020)
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: none that I'm aware of
## Summary
As [originally reported](https://community.e.foundat...- /e/ version: 1.13
- Device model(s): Teracube 2e Zirconia (aka 2020)
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: none that I'm aware of
## Summary
As [originally reported](https://community.e.foundation/t/issue-with-easy-installer-on-teracube/51012) by user Mezmoin on the /e/ forums, the Easy Installer stalls out after the download reaches 1.11gb/1.11gb. Easy Installer is Version 0.18.1.
## The problem
**Steps to reproduce**
1. Install drivers for Teracube 2e
2. Flash stock ROM onto Teracube 2e
3. Attempt to run Easy Installer, following all directions to a T (OEM unlock, USB debugging, USB file transfer).
4. Get stuck at the "downloading /e/OS and necessary files" step.
**What is the current behavior?**
Download proceeds as usual, then "finishes" but will hang on this potentially forever. For at least "over night" per Mezmoin.
**What is the expected correct behavior?**
Easy Installer should proceed as normal and install /e/OS 1.13 on my Teracube 2e.
## Technical informations
**Relevant logs (`adb logcat`)**
[See here.](https://app.box.com/s/ina6k0j7nyedd7hqsgi4a9wftcpdn2is)
**Relevant screenshots**
![image](/uploads/1ebfc68696b9bdc74ef80c4162504a35/image.png)
## Solutions
**Workaround**
None apart from Manual Install which also does not work on my end.
**Possible fixes**
Sadly, I'm not a dev so my ideas would be "some really big if-else statements or something?".Easy Installer v0.21https://gitlab.e.foundation/e/backlog/-/issues/7218Easy Installer gets stuck at download for "OnePlus 8 pro" instantnoodlep2024-02-27T17:04:44ZPete GunterEasy Installer gets stuck at download for "OnePlus 8 pro" instantnoodlep- /e/ version: current
- Device model(s): OnePlus 8 pro
- Developer mode enabled: yes
- Device rooted: I dont know, currently vanilla OxygenOS 11 installed
- Trackers blocker enabled: I dont know
## Summary
Easy Installer on Kubuntu 22...- /e/ version: current
- Device model(s): OnePlus 8 pro
- Developer mode enabled: yes
- Device rooted: I dont know, currently vanilla OxygenOS 11 installed
- Trackers blocker enabled: I dont know
## Summary
Easy Installer on Kubuntu 22.04 gets stuck at download for OnePlus 8 pro instantnoodlep:
## The problem
**Steps to reproduce**
- connect phone to computer
- start Easy Installer and follow the steps
**What is the current behavior?**
- Easy Installer gets stuck at download
**What is the expected correct behavior?**
- Easy Installer does not get stuck at download
## Technical informations
**Relevant screenshots**
![image](/uploads/9428fa941502123cc48a286d313e554c/image.png)
[7760bc7b-4274-46e1-8ddb-40f5951cee16.log](/uploads/dda79108029d1a45701288e867d94057/7760bc7b-4274-46e1-8ddb-40f5951cee16.log)
## Solutions
**Workaround**
none
**Possible fixes**
no ideaEasy Installer v0.21https://gitlab.e.foundation/e/backlog/-/issues/7644Murena Account Sync/WebDav Account Sync do not show date of last synchronizat...2024-02-27T15:28:53ZStefan KraftMurena Account Sync/WebDav Account Sync do not show date of last synchronization for calendar and tasks- /e/ version: 1.18-t-202312100360971-dev-enchilada
- Device model(s): OnePlus 6
- Developer mode enabled: yes
- Device rooted: yes (Magisk)
- Trackers blocker enabled: yes
## Summary
"Accounts" > (Choose Murena Account or WebDAV accou...- /e/ version: 1.18-t-202312100360971-dev-enchilada
- Device model(s): OnePlus 6
- Developer mode enabled: yes
- Device rooted: yes (Magisk)
- Trackers blocker enabled: yes
## Summary
"Accounts" > (Choose Murena Account or WebDAV account) > Select "Account sync" > It shows a timestamp that is older than the last real synchronization
## The problem
- Let the smartphone run for some time so that automatic calendar and/or task sync by the account manager happen in the background.
- Go to "Accounts"
- Choose Murena Account or WebDAV account
- Select "Account sync"
- Remember the timestamps of the displayed last synchronizations
- Go (again) to "Accounts"
- Murena Account: Select Murena Account > Choose "My Account" > "Settings" > Choose Murena account > Select "CALDAV" tab > tap on the three dots of one calendar, select "Properties" > check the last synchronization timestamp
- WebDAV Account: Choose WebDAV account > Choose "Manage accounts" > Choose WebDAV account > Select "CALDAV" tab > tap on the three dots of one calendar, select "Properties" > check the last synchronization timestamp
In both cases, the synchronization in the CALDAV tab is the actual synchronization timestamp while the timestamp in "Account sync" is out of date.
**What is the current behavior?**
See above: The synchronization timestamp is older on the "Account sync" page
**What is the expected correct behavior?**
The timestamps in the CALDAV tab and the "Account sync" page should be equal.
## Technical informations
The problem seems to have appeared after the upgrade to /e/OS T (Android 13).
(no logcat available)
**Relevant screenshots**
![Screenshot_20231231-093807_Einstellungen](/uploads/6b417f2fba32aee5b71ef2727e93f4d7/Screenshot_20231231-093807_Einstellungen.png)![Screenshot_20231231-093840_Kontenverwalter](/uploads/b4954acb9f94306927bc537b984c1fc7/Screenshot_20231231-093840_Kontenverwalter.png)
## Solutions
**Workaround**
On "Account sync" page, tap the three buttons in the upper right corner and select "Sync now". A (foreground) synchronization happens, and the timestamps of the calendar and/or task entry are updated.
**Possible fixes**
Possible fixes are unclear, unfortunately.https://gitlab.e.foundation/e/backlog/-/issues/7219Add a "Do not show again" check box in the dialog explaining how to request a...2024-02-27T15:24:35ZAude MAdd a "Do not show again" check box in the dialog explaining how to request an Exodus report## Summary
<Summarize the improvement briefly and precisely>
With [this issue](https://gitlab.e.foundation/e/backlog/-/issues/6537) the user has the possibility to request an Exodus report and a dialog has been implemented to explain t...## Summary
<Summarize the improvement briefly and precisely>
With [this issue](https://gitlab.e.foundation/e/backlog/-/issues/6537) the user has the possibility to request an Exodus report and a dialog has been implemented to explain the different steps. After a few request the user will not need to be reminded of the steps so we need to give them the opportunity to hide the dialog.
## Description
**What is the current behavior?**
<What actually happens>
The dialog is systematically displayed when the user clicks `Request Exodus report`.
**What is the improved behavior?**
<What you should see instead>
There is a check box which says `Do not show again` at the bottom left of the dialog (but above the buttons). When this checkbox is checked and the user then clicks on `OK`, the dialog isn't displayed anymore in the future when the user requests an Exodus report in the future: clicking on `Request Exodus report` directly navigates to Exodus' page in the browser with the app of the name prefilled.\
If the user checks the checkbox but then clicks on `Cancel`, it's not taken into account and the dialog will be displayed the next times.
**What does it bring?**
<Why this improvement is needed>
Better user experience.
## Mock-ups
<Provide a mock-up of how it would look with the improvement>
> Clicking on "OK" will open a tab in your browser with the app's package name prefilled.\
> Click on "Perform analysis" to start the analysis by Exodus.\
> When the button "See the report" is displayed (it can take a while depending on the app) you can close the tab and go back to the app description in App Lounge where you should see the Privacy Score. Sometimes Exodus can fail to analyze the app.
>
> NB: it can take up to 10 min for the score to be displayed in the app description
>
>
> - [ ] Do not show again
>
> [Cancel] [OK]
## 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.>https://gitlab.e.foundation/e/backlog/-/issues/7789App request: spotify lite on FP42024-02-27T15:04:40ZTy SinoApp request: spotify lite on FP4## Summary
I would like to install Spotify Lite on FP4 with /e/OS.
## Description
**What is the feature?**
Spotify Lite is downloadable from App Lounge.
**Who will use this new feature?**
People having problems with the normal Spot...## Summary
I would like to install Spotify Lite on FP4 with /e/OS.
## Description
**What is the feature?**
Spotify Lite is downloadable from App Lounge.
**Who will use this new feature?**
People having problems with the normal Spotify App.
**Why these users would like to use this feature?**
The normal Spotify App has a bug in registration as media player (the notification and lock screen controls don't appear). Spotify refuses to fix it because it is mainly related to MicroG.
The issue is discussed in the [Spotify Community](https://community.spotify.com/t5/Android/Spotify-loses-registration-as-media-player-in-quick-settings/m-p/5854968) and in the [MicroG issue tracker](https://github.com/microg/GmsCore/issues/2118).
## Examples
As stated by users in the Spotify community forum, the lite version doesn't have this issue.
## Reflection
I don't know if this App is already available for other phones running /e/OS, but apparently not for FP4 running 1.17-s-20231109350748-stable-FP4 (Android 12).https://gitlab.e.foundation/e/backlog/-/issues/7283Weather widget does not arrange text properly.2024-02-27T12:45:36ZShenol MustafovWeather widget does not arrange text properly.- /e/ version: 1.14
- Device model(s): FP4
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
Weather widget sets 2 rows to day name, and the temperature is moved downwards.
## The p...- /e/ version: 1.14
- Device model(s): FP4
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
Weather widget sets 2 rows to day name, and the temperature is moved downwards.
## The problem
**Steps to reproduce**
Unknown
**What is the current behavior?**
Temperature moves down
**What is the expected correct behavior?**
Temperature should not move
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![image](/uploads/54f6710934d7c0420e5bfb55791a2468/image.png){height=600}
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
May be related to the text size etc.
<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 v2.0-alphaYash Gargyash.garg.ext@murena.comYash Gargyash.garg.ext@murena.comhttps://gitlab.e.foundation/e/backlog/-/issues/7796Feature request: addition of 2FA app for /e/OS2024-02-27T11:22:55ZRik ViergeverFeature request: addition of 2FA app for /e/OS## Summary
Given /e/OS focus on providing an open-source, privacy-safe, sustainable OS for mainstream users, it would be good if it comes with default apps for everything mainstream users need these days. One of those things is 2FA. AFA...## Summary
Given /e/OS focus on providing an open-source, privacy-safe, sustainable OS for mainstream users, it would be good if it comes with default apps for everything mainstream users need these days. One of those things is 2FA. AFAIK there appears to be agreement that the best FOSS 2FA app is https://2fas.com/. So this is a suggestion to include this app as a default app in /e/OS.
## Description
**What is the feature?**
2FA default app
**Who will use this new feature?**
everyone needs 2FA. This gives them a 2FA app as a default app in /e/OS.
**Why these users would like to use this feature?**
Ease: it is easy to have it as a default app that, for example, sync with your /e/OS phone
## Examples
<Give the example of what users will be able to accomplish with the feature>
## Reflection
**Mockups**
**Diagrams**
## Validation
<List test case that will be run to validate that the issue is working as expected>
/label ~"type::Feature Proposal"
<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/770422nd Feb 20242024-02-26T22:01:44ZKumar Abhishek22nd Feb 2024- [x] Update the App Lounge APK at https://doc.e.foundation/support-topics/app_lounge#download-app-lounge-apks
- [ ] Publish ~microG EN
- [ ] Release Documentation
- [ ] Open download for new devices
- [ ] Open download for device upgrad...- [x] Update the App Lounge APK at https://doc.e.foundation/support-topics/app_lounge#download-app-lounge-apks
- [ ] Publish ~microG EN
- [ ] Release Documentation
- [ ] Open download for new devices
- [ ] Open download for device upgrade
- [x] Update ~FP5 documentation if security patch level has changed
- [x] Update ~FP4 [documentation](https://doc.e.foundation/devices/FP4/install#downloads-for-the-fp4) if security patch level has changed
- [x] 25% availability of ~s dev builds
- [x] 25% availability of ~r dev builds
- [ ] Share the release on `/e/OS - Murena team` Telegram channel/e/OS v1.20Alexandre RouxSayantan RoychowdhuryAlexandre Roux2024-02-22https://gitlab.e.foundation/e/backlog/-/issues/6865Inaccurate GPS location in Murena One2024-02-26T10:25:24ZHaydee ElizondoInaccurate GPS location in Murena One- /e/ version: 1.9
- Device model(s):Murena One
## Summary
The user identifies inaccuracies in the Murena One's location.
## The problem
Inside buildings the phone shows an incorrect location within a range of 1km.
<How one can rep...- /e/ version: 1.9
- Device model(s):Murena One
## Summary
The user identifies inaccuracies in the Murena One's location.
## The problem
Inside buildings the phone shows an incorrect location within a range of 1km.
<How one can reproduce the issue>
**What is the current behavior?**
In outdoors, it takes a few seconds and then the GPS signal is strong enough and the location is correct.
While in a building, the Murena One based on the GPS Test app shows "No solution". And there are zero (!) satellite signals available.
After a minute, some GPS signals are received and the app shows "3D Fix", but the location is totally wrong, like 1 km away.
**What is the expected correct behavior?**
## Technical informations
**Relevant logs (`adb logcat`)**
```
```
**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/7423Lingoes Dictionary is not available to install in App Louge2024-02-25T14:47:40ZBreweryLingoes Dictionary is not available to install in App Louge- /e/ version: e-1.15-t-20230917331436-dev-a52q
- Device model: a52q
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
cannot install Lingoes Dictionary using anonymous account
https://play.go...- /e/ version: e-1.15-t-20230917331436-dev-a52q
- Device model: a52q
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
cannot install Lingoes Dictionary using anonymous account
https://play.google.com/store/apps/details?id=com.luc.dict.lingoes
**Relevant screenshots**
![lingoes](/uploads/194c205bc4d2dd534852124d42656aaa/lingoes.png)
## Solutions
**Workaround**
use Aurora Store with anonymous account
<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/6642Action Camera is suggested twice when attaching item to gitlab issue2024-02-25T06:16:11ZĹ˝routĂkAction Camera is suggested twice when attaching item to gitlab issue- /e/ version: 1.7-q
- Device model(s): ~h850
- Device rooted: no
## Summary
Action Camera is suggested twice when attaching item to gitlab issue.
## The problem
**Steps to reproduce**
- Create/edit issue/comment at gitlab (here)....- /e/ version: 1.7-q
- Device model(s): ~h850
- Device rooted: no
## Summary
Action Camera is suggested twice when attaching item to gitlab issue.
## The problem
**Steps to reproduce**
- Create/edit issue/comment at gitlab (here).
- attach an item, use the paperclip icon
**What is the current behavior?**
- Camera Camera Files are suggested as actions for the user.
- both Camera open the camera
**What is the expected correct behavior?**
- Reduce the number of Camera
- or correct one to open Images, I assume that that was a behavior few months ago.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![Screenshot_20230207-110740_Android_System](/uploads/f1efb44dc135b4e32f78935f94e3386e/Screenshot_20230207-110740_Android_System.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.>