Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2024-02-22T08:51:33Zhttps://gitlab.e.foundation/e/backlog/-/issues/7779Issue with Navigation Bar text selection in native Browser2024-02-22T08:51:33ZŽroutíkIssue with Navigation Bar text selection in native Browser### Environment:
- **Device**: ~beyond2lte
- **/e/OS Version**: 1.19-s
- **Browser**: Native /e/OS Browser
### Description:
Previously, long-pressing the navigation bar in the native browser would result in the entire URL being selected...### Environment:
- **Device**: ~beyond2lte
- **/e/OS Version**: 1.19-s
- **Browser**: Native /e/OS Browser
### Description:
Previously, long-pressing the navigation bar in the native browser would result in the entire URL being selected, with a context menu appearing promptly. However, after updating to /e/OS version 1.19-s on the beyond2lte device, this behavior has changed. Now, when long-pressing the navigation bar, only a part of the URL is selected initially. To select the entire URL, additional steps are needed, such as manually adjusting the selection via the context menu. This change represents a degradation in usability, requiring extra steps for a task that was previously more straightforward.
### Steps to Reproduce:
1. Open the native browser on a beyond2lte device running /e/OS version 1.19-s.
2. Navigate to any website to ensure the navigation bar contains a URL.
3. Long press on the navigation bar where the URL is displayed.
4. Observe that only part of the URL is selected, unlike previous behavior where the whole URL would be selected.
### Expected Behavior:
Long pressing on the navigation bar should select the entire URL and present a context menu, facilitating quick actions such as copy, cut, or share.
### Actual Behavior:
Only a portion of the URL is selected upon long pressing, necessitating additional steps to select the whole URL, which complicates the usability.
### Additional Information:
- **Frequency of Occurrence**: Consistently reproducible on /e/OS version 1.19-s on beyond2lte.
- **Workaround**: Users can manually adjust the selection via the context menu, although this is less efficient than the previous behavior.
### Logcat (if applicable):https://gitlab.e.foundation/e/backlog/-/issues/7778Being able to refer (copy URL) to files and folders that are shared with peop...2024-02-21T14:41:51ZRik ViergeverBeing able to refer (copy URL) to files and folders that are shared with people (relevant for B2B)- /e/ version: - (Murena Cloud)
- Device model(s): - (Murena Cloud)
## Summary
Improvement request for Murena.io, Files section. I would like to be able to refer, using a URL, to files and folders that I have shared with people.
## D...- /e/ version: - (Murena Cloud)
- Device model(s): - (Murena Cloud)
## Summary
Improvement request for Murena.io, Files section. I would like to be able to refer, using a URL, to files and folders that I have shared with people.
## Description
**What is the current behavior?**
I have shared a folder with around 20 people. There are multiple ways to do this:
1) make the folder accessible via a URL and share that
2) invite people via email (and potentially add a password to their login)
When you do (2), which is more secure, everyone gets their own login URL and password. Subsequently, it becomes impossible in an email or other communication to refer to a folder or file within the Shared Drive - because every accesses it via a separate URL. This is really unhandy when co-working on a project.
**What is the improved behavior?**
I can tell someone via email "Please go this subfolder" or "Please go this file" **using a URL** for a folder that was shared from murena.io with other people via option (2) above.
**What does it bring?**
Much easier collaboration with other people when you use Murena.io as a shared drive/folder for a project.
## Mock-ups
## Examples
## Validationhttps://gitlab.e.foundation/e/backlog/-/issues/7777QKSMS seems abandoned2024-03-06T14:59:43ZBreweryQKSMS seems abandonedQKSMS, the app eOS message is based, seems abandoned.
So, issues will no longer be fixed.
https://github.com/moezbhatti/qksms/issues/1970QKSMS, the app eOS message is based, seems abandoned.
So, issues will no longer be fixed.
https://github.com/moezbhatti/qksms/issues/1970https://gitlab.e.foundation/e/backlog/-/issues/7772Netflix won't start on One plus 8T Android 132024-02-22T08:53:07Zmichel memeteau - EkimiaNetflix won't start on One plus 8T Android 13- /e/ version: 1.19.1 ( Android 13 )
- Device model(s): kebab ( One plus 8T )
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: no
## Summary
<Summarize the bug encountered briefly and precisely>
## The pro...- /e/ version: 1.19.1 ( Android 13 )
- Device model(s): kebab ( One plus 8T )
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: no
## Summary
<Summarize the bug encountered briefly and precisely>
## The problem
**Steps to reproduce**
Launch Netflix
**What is the current behavior?**
- Netflix logo for few minutes
- Error message : 501,-172
**What is the expected correct behavior?**
the Netflix login page
## Technical informations
**Relevant logs (`adb logcat`)**
```
02-20 16:07:47.831 6917 7057 D ProfileInstaller: Installing profile for com.netflix.mediaclient
02-20 16:09:12.120 1758 5012 D CoreBackPreview: Window{6e76de9 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.launch.UIWebViewActivity}: Setting back callback OnBackInvokedCallbackInfo{mCallback=android.window.IOnBackInvokedCallback$Stub$Proxy@ecf332b, mPriority=0}
02-20 16:09:12.131 6917 6917 W com.netflix.mediaclient: type=1400 audit(0.0:48): avc: denied { read } for comm=4C6F6767696E674167656E74202331 name="policy" dev="selinuxfs" ino=20 scontext=u:r:untrusted_app:s0:c209,c256,c512,c768 tcontext=u:object_r:selinuxfs:s0 tclass=file permissive=0 app=com.netflix.mediaclient
02-20 16:09:12.131 6917 6917 W com.netflix.mediaclient: type=1400 audit(0.0:49): avc: denied { getattr } for comm=4C6F6767696E674167656E74202331 path="/sys/kernel/tracing/trace_marker" dev="tracefs" ino=11139 scontext=u:r:untrusted_app:s0:c209,c256,c512,c768 tcontext=u:object_r:debugfs_trace_marker:s0 tclass=file permissive=0 app=com.netflix.mediaclient
02-20 16:09:12.135 6917 6917 W com.netflix.mediaclient: type=1400 audit(0.0:50): avc: denied { getattr } for comm=4C6F6767696E674167656E74202331 path="/dev/pmsg0" dev="tmpfs" ino=11379 scontext=u:r:untrusted_app:s0:c209,c256,c512,c768 tcontext=u:object_r:pmsg_device:s0 tclass=chr_file permissive=0 app=com.netflix.mediaclient
02-20 16:09:12.135 6917 6917 W com.netflix.mediaclient: type=1400 audit(0.0:51): avc: denied { getattr } for comm=4C6F6767696E674167656E74202331 path="/sys/kernel/tracing/trace_marker" dev="tracefs" ino=11139 scontext=u:r:untrusted_app:s0:c209,c256,c512,c768 tcontext=u:object_r:debugfs_trace_marker:s0 tclass=file permissive=0 app=com.netflix.mediaclient
02-20 16:09:12.168 3603 6853 D GmsDummySvc: bound by: GetServiceRequest{serviceId=UNKNOWN(322), gmsVersion=12451000, packageName='com.netflix.mediaclient', extras=Bundle[{}]}
02-20 16:37:44.417 1758 3091 W ProcessStats: Tracking association SourceState{868bed9 com.netflix.mediaclient/10209 Top #2378} whose proc state 1 is better than process ProcessState{c421063 com.google.android.gms/10118 pkg=com.google.android.gms} proc state 6 (0 skipped)
```
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
We add several similar problems on 1.4 on other devices ( same error code ) , we should see how this was corrected
Netflix works perfect on other devices with 1.19.1 lie dumpling or crownlte
/label ~"type::Bug"
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/7771[Feature Request] Allow to set battery charging limit2024-02-28T19:35:55ZErwan Georgete.i9dnw@passmail.net[Feature Request] Allow to set battery charging limit- /e/ version: 1.19
- Device model(s): FP5, but may apply to other devices
## Summary
As explained in this [Ifixit blog post](https://www.ifixit.com/News/90983/why-charging-your-gadgets-over-80-is-such-a-bad-idea), it is best to not ch...- /e/ version: 1.19
- Device model(s): FP5, but may apply to other devices
## Summary
As explained in this [Ifixit blog post](https://www.ifixit.com/News/90983/why-charging-your-gadgets-over-80-is-such-a-bad-idea), it is best to not charge your phone above 80% to preserve its battery. If it isn't as much of a ploblem with a device like the FP5 (which has a replaceable battery), it is for most of the phone supported by /e/os.
The official FP5 image has this option, as such it should be quite easy to develop as it already prove it is doable. Multiple open-source apps does the same, but all of them requires a rooted device.
## Description
**What is the current behavior?**
No such option is available. Phone won't stop charging until it is at 100%
**What is the improved behavior?**
In the settings, an option allows to set a limit to 80% (or any other custom percentages) of the nominal capacity.
**What does it bring?**
The ability to set max charging to a level that preserve the battery (80%).
## Validation
- On a device which battery is bellow 80%, Set limit to 80%
, then charge it -> It should stop charging around upper 80% (like 80.95%), and not start charging again before it reach around 79% (like 80.05%).
Previous issue : #5879
<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/7770Low call volume on s10e+ speaker mode2024-02-22T08:48:15ZŽroutíkLow call volume on s10e+ speaker mode- /e/ version: 1.19-s
- Device model(s): ~beyond2lte
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
S10e+ speaker call volume is really low compared to other audio outputs, with in-ear call...- /e/ version: 1.19-s
- Device model(s): ~beyond2lte
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
S10e+ speaker call volume is really low compared to other audio outputs, with in-ear call volume being satisfactory.
## The problem
**Steps to reproduce**
1. Initiate a call.
2. Switch to speaker mode to emit sound publicly.
3. Adjust the volume, decreasing and increasing it.
4. Observe that the amplitude between the lowest and highest volume settings is minimal, and the maximum volume is significantly lower than expected.
Note: The volume for phone calls using the private in-ear option is adequate, with the device sometimes automatically adjusting it to a lower level for comfort. The maximum call volume on speaker mode is approximately 2/3 of the volume level experienced when using Spotify or other audio applications, indicating that this issue may not be hardware-limited.
**What is the current behavior?**
The speaker call volume remains low even at its maximum setting, providing an unsatisfactory difference in volume levels when adjusting. This suggests that the issue may not be due to hardware limitations.
**What is the expected correct behavior?**
There should be a significant difference in amplitude between the lowest and highest volume settings, with the maximum volume being sufficiently high for clear audio during speaker calls.
## Technical informations
**Relevant logs (`adb logcat`)**
(Please include any relevant logs here to help diagnose the issue)
**Relevant screenshots**
(If possible, add screenshots of the low volume issue to provide visual context)
## Solutions
**Workaround**
Currently, there is no known workaround to effectively increase the speaker call volume. Adjusting the volume settings does not significantly impact the low volume issue.
**Possible fixes**
Investigating the audio management system within /e/OS for the s10e+ device could uncover specific settings or limitations causing the low speaker call volume. Adjusting these settings or optimizing the software's audio output management might provide potential fixes.https://gitlab.e.foundation/e/backlog/-/issues/7769Feature request: week agenda view in calendar2024-02-22T08:51:08ZRik ViergeverFeature request: week agenda view in calendar## Summary
I would like to propose that we develop the calendar view in the image below for the eOS calendar app. It is, imo, by far the best view and to my knowledge it is not available in any Foss app.
![Screenshot_20240220-003008_D...## Summary
I would like to propose that we develop the calendar view in the image below for the eOS calendar app. It is, imo, by far the best view and to my knowledge it is not available in any Foss app.
![Screenshot_20240220-003008_DigiCal](/uploads/ace891860594d6f7e98db6a78ea89ddf/Screenshot_20240220-003008_DigiCal.png)
## Description
**What is the feature?**
Week agenda view for default calendar app
**Who will use this new feature?**
It is a popular view
**Why these users would like to use this feature?**
Best overview of meetings this week combined with enough info about each.
## 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/7768Improvement request: Settings and unified inbox options on 1st menu screen of...2024-02-22T08:47:55ZRik ViergeverImprovement request: Settings and unified inbox options on 1st menu screen of mail app- /e/ version: 1.19.1-t-20240113373116-dev-sagit
- Device model(s): sagit
## Summary
Hi, to me it is a bit odd that in this screen of the eOS mail app we don't see the options "all inboxes" and "settings":
![Screenshot_20240219-232020...- /e/ version: 1.19.1-t-20240113373116-dev-sagit
- Device model(s): sagit
## Summary
Hi, to me it is a bit odd that in this screen of the eOS mail app we don't see the options "all inboxes" and "settings":
![Screenshot_20240219-232020_Mail](/uploads/f29ddf047f51943d80bb430954400fae/Screenshot_20240219-232020_Mail.png)
To see those two options we first have to click on one of the mailboxes:
![Screenshot_20240219-232011_Mail](/uploads/6ef13b4ec7f9c0094ba036c395101ebb/Screenshot_20240219-232011_Mail.png)
So this is an improvement request for making those two options visible in the first screenshot, which is the first screen we get when we click the menu button in the mail app.
## Description
**What is the current behavior?**
"all inboxes" and "settings" options only show after clicking an individual account, even though both are overarching account things (the settings too apply to all accounts)
**What is the improved behavior?**
These two options are shown in the first menu screen above or below the email accounts
**What does it bring?**
<Why this improvement is needed>
## Mock-ups
<Provide a mock-up of how it would look with the improvement>
## Examples
<Give the example of what users will be able to accomplish with the improvement>
## Validation
<List test case that will be run to validate that the issue is working as expected>
/label ~"type::Improvement"
<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/7767Feature request: create option to "show all apps" by default on Murena.io (in...2024-02-22T09:27:00ZRik ViergeverFeature request: create option to "show all apps" by default on Murena.io (instead of a selection)- /e/ version: Murena.io
- Device model(s): na
## Summary
Feature request: create option to "show all apps" by default on Murena.io
## Description
**What currently happens ?**
I have to press "show more apps" every time to see all ...- /e/ version: Murena.io
- Device model(s): na
## Summary
Feature request: create option to "show all apps" by default on Murena.io
## Description
**What currently happens ?**
I have to press "show more apps" every time to see all apps
**What is the improved behavior?**
Users can click an option in the Settings to always show all apps by default.
**What does it bring?**
Ease of use for users who use apps that are not in the default selection + more awareness about apps outside the default selection (i had missed them for quite a while)
## Mock-ups
<Provide a mock-up of how it would look with the improvement>
## Examples
<Give the example of what users will be able to accomplish with the improvement>
## Validation
<List test case that will be run to validate that the issue is working as expected>
/label ~"type::Improvement"
<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/7763Youtube stops playing after 1 minute2024-02-23T14:45:49ZJonathan KleeYoutube stops playing after 1 minute- <details><summary>Third party app icon</summary>![icon](/uploads/6c9b8fd6f601e8fdda7d7595d02470d1/icon.png)</details>
- /e/ version:1.10-s-20230412278810-stable
- Device model(s):Fairphone 3 and 4
- Developer mode enabled: no
- Device ...- <details><summary>Third party app icon</summary>![icon](/uploads/6c9b8fd6f601e8fdda7d7595d02470d1/icon.png)</details>
- /e/ version:1.10-s-20230412278810-stable
- Device model(s):Fairphone 3 and 4
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes/no (tried with and without blocker)
## Summary
When watching a video on youtube, it stops loading after a minute more or less. Several Commown customers reported this issue, and we reproduced it too.
## The problem
**Steps to reproduce**
Install youtube from App Lounge and start a random video. Just wait ~1 minute until it stops working
**What is the current behavior?**
Video stops and is infinitely loading.
**What is the expected correct behavior?**
Whole video plays without issue
## Solutions
**Workaround**
Use NewPipe: https://f-droid.org/packages/org.schabi.newpipe/
**Possible fixes**
Latest version of microG may fix this problem since a new PoToken implementation has been introduced in microG:
https://gitlab.e.foundation/e/os/GmsCore/-/commit/3a8cdceb8a22c15cc88d5188f5c3269520ae36dc
<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/7760Improving gesture navigation with keyboard arrow keys in2024-02-22T08:49:55ZŽroutíkImproving gesture navigation with keyboard arrow keys in- /e/ version: 1.19-s
- Device model(s): ~beyond2lte
## Summary
Proposal to introduce arrow keys for cursor movement in gesture navigation mode to enhance text editing capabilities.
This proposal aims to enhance the user experience b...- /e/ version: 1.19-s
- Device model(s): ~beyond2lte
## Summary
Proposal to introduce arrow keys for cursor movement in gesture navigation mode to enhance text editing capabilities.
This proposal aims to enhance the user experience by providing more precise control over cursor movement during text input, aligning with user expectations for efficient and intuitive navigation.
## Description
**What is the current behavior?**
Currently, gesture navigation mode lacks the functionality of arrow keys for cursor movement on the keyboard, limiting user efficiency in text editing tasks.
**What is the improved behavior?**
1. Implement an option within keyboard settings to enable arrow keys for cursor movement in gesture navigation mode.
2. Explore the possibility of removing the bottom bar when not in use, or repurposing it for additional keyboard functionalities such as cursor movement.
**What does it bring?**
It'd make typing and editing text on /e/OS feel smoother and faster. Plus, it could make the screen look nicer, whether by clearing clutter or adding useful keys.
## Mock-ups
<Provide a mock-up of how it would look with the improvement>
## Examples
<Give the example of what users will be able to accomplish with the improvement>
## Validation
/label ~"type::Improvement"https://gitlab.e.foundation/e/backlog/-/issues/7759Dialer App notification persists after action2024-02-22T08:45:23ZŽroutíkDialer App notification persists after action- **/e/ version:** 1.19-s
- **Device model(s):** beyond2lte
- **Developer mode enabled:** yes
- **Device rooted:** no
- **Trackers blocker enabled:** yes
## Summary
Persistent notification issue in dialer app on beyond2lte running /e/O...- **/e/ version:** 1.19-s
- **Device model(s):** beyond2lte
- **Developer mode enabled:** yes
- **Device rooted:** no
- **Trackers blocker enabled:** yes
## Summary
Persistent notification issue in dialer app on beyond2lte running /e/OS 1.19-s, where the notification does not dismiss after the dialer app is opened and the caller is no longer highlighted, deviating from expected behavior similar to the Messages app.
## The problem
**Steps to reproduce**
1. Receive a call, which triggers a notification.
2. Open the dialer app.
3. Tap the caller so the highlighting is dismissed.
**What is the current behavior?**
The notification remains active in the notification tray even after the above steps.
**What is the expected correct behavior?**
The notification should be dismissed once the caller is no longer highlighted in the dialer app or when the app is opened, similar to how notifications behave in the Messages app.
## Technical information
**Relevant logs (`adb logcat`)**
**Relevant screenshots**
(Please add screenshots of the problem if available. Screenshots can significantly help in understanding the issue visually.)
## Solutions
**Workaround**
(Currently, there might not be a direct workaround that addresses the notification issue without dismissing it manually.)
**Possible fixes**
(A thorough examination of how notifications are managed within the dialer app compared to the Messages app might reveal discrepancies in handling state changes or intent flags. A potential fix could involve aligning the dialer app's notification dismissal logic with that of the Messages app.)https://gitlab.e.foundation/e/backlog/-/issues/7758Telephone App - Call screen2024-02-22T08:45:04ZByjaTelephone App - Call screen- /e/ version: 1.17-s-20231109350748-stable-FP4
- Device model(s): FP4
## Summary
Incoming call screen of the default Telephone app should contain more contact info, if available.
## Description
Currently, only the contact's Name and...- /e/ version: 1.17-s-20231109350748-stable-FP4
- Device model(s): FP4
## Summary
Incoming call screen of the default Telephone app should contain more contact info, if available.
## Description
Currently, only the contact's Name and Surname are displayed on the call screen.
<What actually happens>
At the very least, the Title, Department and Company should be displayed below the Name and Surname.
Ideally, the users should be able to customise displayed contact fields in the settings of the Telephone app.
<What you should see instead>
It will be easier to tell who is calling, especially if there are several contacts with the same name and surname.
<Why this improvement is needed>
/label ~"type::Improvement"
<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/7755Connect a USB-C to 3,5mm adapter to Murena Fairphone 5 defaults the OS to Ch...2024-03-01T14:13:30ZAlexis NoetingerConnect a USB-C to 3,5mm adapter to Murena Fairphone 5 defaults the OS to Charging over USB- /e/ version: 1.19
- Device model(s): ~FP5
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: not relevant
## Summary
When connecting a USB-C to 3,5mm jack adapter to the Murena Fairphone 5, a charging notif...- /e/ version: 1.19
- Device model(s): ~FP5
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: not relevant
## Summary
When connecting a USB-C to 3,5mm jack adapter to the Murena Fairphone 5, a charging notification is displayed and charging mode is engaged, preventing audio output.
## The problem
**Steps to reproduce**
Connect a USB-C to 3,5mm jack adapter to the Murena Fairphone 5
**What is the current behavior?**
The OS displays the notification "Charging connected device via USB". There is no audio signal as an output via the jack adapter.
**What is the expected correct behavior?**
When the adapter is connected, the OS should not go to charging mode as there is no power source connected to the USB-C port.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![photo_2024-02-16_10.09.12](/uploads/d27baee005c8494acede2bee6e2ab2d4/photo_2024-02-16_10.09.12.jpeg)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
/label ~"type::Bug"
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/7754can't restore paid app if connected with google account on app lounge2024-02-22T08:44:17Zdev.3xm0fcan't restore paid app if connected with google account on app lounge- /e/ version: 1.18-s20231209360970-dev-d2s
- Device model(s): d2s samsung galaxy note 10+
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
I have paid app on a google account, I want to res...- /e/ version: 1.18-s20231209360970-dev-d2s
- Device model(s): d2s samsung galaxy note 10+
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
I have paid app on a google account, I want to restore them, I can't
## The problem
1. have some paid app on a google account
2. login using this account on app lounge
3. search for the paid app (app lounge don't list paid app)
4. the app is shown as unpaid (the price is still displayed)
5. trying to install it does nothing
<How one can reproduce the issue>
**What is the current behavior?**
can't install my paid app
**What is the expected correct behavior?**
I should be able to install my paid app
## Technical informations
**Relevant logs (`adb logcat`)**
[apploungepaidappbug_diff.log](/uploads/aa3f3af12afe035077777599fc172921/apploungepaidappbug_diff.log)
## Solutions
**Workaround**
maybe dowload it on a device with google play store, send it by blueetooth to the device and install it by hand?
**Possible fixes**
don't know
/label ~"type::Bug" ~"/e/OS Account Manager"
<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/7753Devices failed in 1.20-rc, 1.20-rc.22024-03-22T18:04:54ZSayantan RoychowdhuryDevices failed in 1.20-rc, 1.20-rc.2build-dev-r-zl1 - https://gitlab.e.foundation/e/priv/os/build/-/jobs/845655build-dev-r-zl1 - https://gitlab.e.foundation/e/priv/os/build/-/jobs/845655/e/OS v2.0-betaAhmed Harhashemail@lacentix.meAhmed Harhashemail@lacentix.mehttps://gitlab.e.foundation/e/backlog/-/issues/7751Check the new Universal Android Debloater results2024-03-19T19:29:28ZJonathan KleeCheck the new Universal Android Debloater results## Summary
Check the new Universal Android Debloater results
<Summarize the improvement briefly and precisely>
## Description
The Next Genetion Universal Android Debloater is being developed. It is worth having a look at what we obta...## Summary
Check the new Universal Android Debloater results
<Summarize the improvement briefly and precisely>
## Description
The Next Genetion Universal Android Debloater is being developed. It is worth having a look at what we obtain and make sure everything is needed.
Example on a FP3 on /e/OS:
<img src="/uploads/349ee1db9b811d47973f3739af7581c3/photo_2024-02-14_15-43-54.jpg" width="500"/>
To install the software: https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation/wiki/Getting-started#getting-started
**What is the current behavior?**
<What actually happens>
The software gives us results.
**What is the improved behavior?**
We should have the minimum number of elements in this lists.
<What you should see instead>
**What does it bring?**
<Why this improvement is needed>
## Mock-ups
<Provide a mock-up of how it would look with the improvement>
## Examples
<Give the example of what users will be able to accomplish with the improvement>
## Validation
<List test case that will be run to validate that the issue is working as expected>
/label ~"type::Improvement"
<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.>
@rhunault @aude @thescarastic @merothh/e/OS v2.0-alphahttps://gitlab.e.foundation/e/backlog/-/issues/7750Redmi 8T - old Android version2024-02-14T05:44:36ZRobert KlaucoRedmi 8T - old Android version- /e/ version:
- Device model(s):
Xiaomi Redmi 8T
## Summary
LineageOS has already Android 11 for this device. Would it be possible to move forward with Redmi 8T from /e/os version R?
## Description
The current system is pretty stabl...- /e/ version:
- Device model(s):
Xiaomi Redmi 8T
## Summary
LineageOS has already Android 11 for this device. Would it be possible to move forward with Redmi 8T from /e/os version R?
## Description
The current system is pretty stable, but quite outdated. I am missing quite a lot of features (such as wifi network that is saved, but will not autoconnect, etc.).
**What does it bring?**
Newer Android version with bugfixes, improvements and also security patches.
## Mock-ups
N/A
## Examples
N/A
## Validation
N/A
<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/7748Recent Apps View often hangs when using multiple users on the same phone2024-03-26T15:45:40ZErwan Georgete.i9dnw@passmail.netRecent Apps View often hangs when using multiple users on the same phone- /e/ version: 1.19-t, 1.20-t, 1.21-t
- Device model(s): FP5
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## The problem
Recent Apps View often hang after user switch. Reboot is needed to get it bac...- /e/ version: 1.19-t, 1.20-t, 1.21-t
- Device model(s): FP5
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## The problem
Recent Apps View often hang after user switch. Reboot is needed to get it back.
- Create a secondary user (Multiple User Setting enabled)
- Open some apps on the main user
- Switch to secondary user
- Open some more apps
- Use the secondary user for a little while
- Switch back to primary user
- Try to switch app using the Recent Apps View
**What is the current behavior?**
The Recent Apps View animation freezes at the beginning, preventing from switching app or doing anything in the Recent Apps View. Note that It doesn't happens every time, I'm still trying to determine the specific combination of triggers that make this bug occur.
**What is the expected correct behavior?**
The Recent Apps View animation should complete successfully and show the recently opened apps.
## Technical informations
**Relevant logs (`adb logcat`)**
I don't know how to use logcat yet, will update as soon as I learn and get something of note.
## Solutions
**Workaround**
Rebooting the phonehttps://gitlab.e.foundation/e/backlog/-/issues/7747Some fdroid apps are not updated automatically with App Lounge2024-03-12T09:24:32ZBrewerySome fdroid apps are not updated automatically with App Loungeeos 1.19.1
Samsung a52q
Latest Fennec from [fdroid](https://f-droid.org/en/packages/org.mozilla.fennec_fdroid) is 122.0.0 released on 2024-01-30
If I manually search Fennec on App Lounge the update is shown, but on updates tab nothing ...eos 1.19.1
Samsung a52q
Latest Fennec from [fdroid](https://f-droid.org/en/packages/org.mozilla.fennec_fdroid) is 122.0.0 released on 2024-01-30
If I manually search Fennec on App Lounge the update is shown, but on updates tab nothing appears so it is not updating automatically
![Imagepipe_0](/uploads/6f91762a1f90bdbd9f27fe9c52e9b7e6/Imagepipe_0.jpg)
![Imagepipe_1](/uploads/6ef985901551224476c30a51ff27dd9f/Imagepipe_1.jpg)