Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2024-01-07T06:53:42Zhttps://gitlab.e.foundation/e/backlog/-/issues/7642Issue with navigation buttons2024-01-07T06:53:42ZRalph BöhlkeIssue with navigation buttons- /e/ version: e-1.7-S-dev
- Device model(s): Beryllium
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes (default)
## Summary
The 3 navigation buttons (triangle, circle, square) are one of the options fo...- /e/ version: e-1.7-S-dev
- Device model(s): Beryllium
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes (default)
## Summary
The 3 navigation buttons (triangle, circle, square) are one of the options for navigating Android systems.
Within the e-ecosystem there is an issue that under certain circumstances the navigation items appear in the same color as their background - and therefore become invisible.
## The problem
**Steps to reproduce**
1- While using the 3 navigation buttons, the buttons disappear while using the app for some time constantly. I was unable to determine an exact moment when they disappear. An app where I notified this 'disappearance': Firefox.
2- There are some few apps where the navigation buttons remain invisible due to same color background is the Withings app (com.withings.wiscafe2)
**What is the current behavior?**
The navigations buttons are not/almost not visible but still work.
See screenshot below.
**What is the expected correct behavior?**
The navigation buttons should constantly adapt to their current background color in order to be always visible.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![559-navigation-white](/uploads/f8a0b978c82647bd65f7bd793bd905f9/559-navigation-white.jpg)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
/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/7447Major flaw that hinders a proper usage of the device2023-10-30T16:54:36ZRalph BöhlkeMajor flaw that hinders a proper usage of the device- /e/ version: e-1.15-S-dev
- Device model(s): Beryllium
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes (default)
## Summary
Today I experience, the fist time since years, a major flaw with /e/OS that ...- /e/ version: e-1.15-S-dev
- Device model(s): Beryllium
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes (default)
## Summary
Today I experience, the fist time since years, a major flaw with /e/OS that hinders a proper usage of the device.
- **Unlocking the device.** When pressing the on/off button the device usually displays an overview page with notifications and the time. Now I see a black screen (while the status bar still shows). The screen unlock via fingerprint works but seems to take a little longer than usually, so I am able to unlock the device.
- **Pull-down Menu** The Pull-down Menu with notifications and the buttons (such as Wifi on/off) does not appear. When swiping-down, the navigation buttons at the bottom of the screen changing colour (from white to grey). When swiping-down several times a notification window is popping-up stating that BlissLancher isn't responding. Then I can chose to "Wait" or "Close the app". When I opt for the latter Bliss seems to restart, but the device continues behaving strangely.
For now, I cannot say what triggered this strange behaviour. I discovered this strange behaviour (while listening to a radio stream) when the phone notified (by sound) the arrival of a new message and I tried to display it on the screen.
I chose to restart the device, now everything seems to work again.
## The problem
**Steps to reproduce**
Cannot say for now.
**What is the current behavior?**
- When the screen is off, and the on/off button is pressed, the overview screen with current notifications and the current time does not show - instead the screen is black (only the status bar shows). Otherwise, the screen does not react on anything, I can only opt to press again the on/off button, to switch off the screen.
- I can press the fingerprint sensor, then the screen is switching on correctly (but with a slight delay).
- I cannot display the Pull-down Menu when swiping down. When attempting, the navigation buttons are turning grey.
**What is the expected correct behavior?**
- When the screen is off, and the on/off button is pressed, the overview screen with current notifications and the current time should show
- When pressing the fingerprint sensor, the screen should switch on correctly without delays.
- When swiping down on the screen, the Swipe-down Menu should show.
## Technical informations
**Relevant logs (`adb logcat`)**
I save three consecutive logfiles, I share all three.
[546-major-flaw-1-logcat_10-25-2023_08-49-23.txt](/uploads/cf1eb9022673ef829d0287582f130100/546-major-flaw-1-logcat_10-25-2023_08-49-23.txt)
[547-major-flaw-2-logcat_10-25-2023_08-52-12.txt](/uploads/cd019186c021812b41d18b1b8cdfc614/547-major-flaw-2-logcat_10-25-2023_08-52-12.txt)
[548-major-flaw-3-logcat_10-25-2023_08-53-32.txt](/uploads/4d9412332a469c788851c8e31c01850e/548-major-flaw-3-logcat_10-25-2023_08-53-32.txt)
```
```
**Relevant screenshots**
![549-major-flaw-4-photo_2023-10-25_09-41-59](/uploads/a01644d0871a01707aa009df4c7afd0b/549-major-flaw-4-photo_2023-10-25_09-41-59.jpg)
![550-major-flaw-5-photo_2023-10-25_09-41-41](/uploads/9ee680e77feb784ee77caf14f66a7d45/550-major-flaw-5-photo_2023-10-25_09-41-41.jpg)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/7387The recent apps button stop responding randomly.2023-12-15T09:15:46ZBah AThe recent apps button stop responding randomly.- /e/ version: 1.15-dev
- Device model(s): Android 12 Xiaomi poco f1 "beryllium"
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
The recent apps button stop responding randomly.
## The probl...- /e/ version: 1.15-dev
- Device model(s): Android 12 Xiaomi poco f1 "beryllium"
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
The recent apps button stop responding randomly.
## The problem
**Steps to reproduce**
Install 1.15 and the recent apps button stop responding randomly.
**What is the current behavior?**
When the behavior starts, only restarting the phone helps, until next time.
It's started to occur last week and keep happening a few times a day.
**What is the expected correct behavior?**
The recent apps navigation button will work as expected.
## Solutions
**Workaround**
Reboot the phone
**Possible fixes**
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/7004Network speed monitor completely missing from beryllium2023-06-26T12:48:10ZBah ANetwork speed monitor completely missing from beryllium- /e/ version: 1.11-s
- Device model(s): Android 12 Xiaomi poco f1 "beryllium"
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Network speed monitor completely missing from beryllium
## The...- /e/ version: 1.11-s
- Device model(s): Android 12 Xiaomi poco f1 "beryllium"
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Network speed monitor completely missing from beryllium
## The problem
**Steps to reproduce**
Go to Parameters > Systems > Status bar > the network monitor is completely missing.
Or anywhere else in the system
**What is the current behavior?**
Network speed monitor, completely missing from the system
**What is the expected correct behavior?**
The feature to appear in the setting and to be able to turn on the feature
## Technical informations
N/A
**Relevant screenshots**
N/A
## Solutions
**Workaround**
Bring back the network traffic feature.
It has been available on the MIUI so don't see a reason to cut it off from this phone.
**Possible fixes**
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/6983Profile trusted provider org.lineageos.profiles keeps crashing2024-01-17T16:05:26ZBah AProfile trusted provider org.lineageos.profiles keeps crashing- /e/ version: 1.11
- Device model(s): Android 12 Xiaomi poco f1 "beryllium"
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Profile trusted provider org.lineageos.profiles keeps crashing. Th...- /e/ version: 1.11
- Device model(s): Android 12 Xiaomi poco f1 "beryllium"
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Profile trusted provider org.lineageos.profiles keeps crashing. The behavior reappear every 5~10 minute.
I can't use the phone normally
## The problem
**Steps to reproduce**
Keep using the phone normally, no special action required
**What is the current behavior?**
org.lineageos.profiles crashing constantly
**What is the expected correct behavior?**
The org.lineageos.profiles shouldn't crash
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
Attached![Screenshot_20230526-001139_DuckDuckGo](/uploads/04950855ad0b6bbc854f52d5acdac880/Screenshot_20230526-001139_DuckDuckGo.png)
**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/6893WLAN Calling not working2023-05-25T07:06:56ZLupus LupusWLAN Calling not working- /e/ version: 10 / 12
- Device model(s): Pocophone F1 "beryllium", OnePlus 5T "dumpling"
- Developer mode enabled: ~~yes~~/**no**
- Device rooted: ~~yes~~/**no**
- Trackers blocker enabled: ~~yes~~/**no**
## Summary
Cannot use WLAN ca...- /e/ version: 10 / 12
- Device model(s): Pocophone F1 "beryllium", OnePlus 5T "dumpling"
- Developer mode enabled: ~~yes~~/**no**
- Device rooted: ~~yes~~/**no**
- Trackers blocker enabled: ~~yes~~/**no**
## Summary
Cannot use WLAN calling.
## The problem
**Steps to reproduce**
No mobile network available. SIM card is inserted. Use WLAN calling to call.
**What is the current behavior?**
I got the error message: "Mobile network is not available. Connect to a wireless network to make a call."
**What is the expected correct behavior?**
I can make a call without mobile network but with WLAN.
## Technical informations
**Relevant screenshots**
![settings](/uploads/c6149eb904c2bfba6bc9643e1e14856f/settings.jpg)
![IMG1](/uploads/8b0e2b7d5bf2753defc1dfdaeff6e1a7/IMG1.jpg)
## Solutions
**Workaround**
Thats my question.
**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.>