Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2021-04-19T15:22:22Zhttps://gitlab.e.foundation/e/backlog/-/issues/2746Fix Pie build failure for v0.152021-04-19T15:22:22ZRomain HunaultFix Pie build failure for v0.15We faced multiple build failure for v0.15 ([pipeline 105774](https://gitlab.e.foundation/e/priv/os/build/-/pipelines/105774))
- ~YTX703F https://gitlab.e.foundation/e/priv/os/build/-/jobs/154082
- ~a5y17lte https://gitlab.e.foundati...We faced multiple build failure for v0.15 ([pipeline 105774](https://gitlab.e.foundation/e/priv/os/build/-/pipelines/105774))
- ~YTX703F https://gitlab.e.foundation/e/priv/os/build/-/jobs/154082
- ~a5y17lte https://gitlab.e.foundation/e/priv/os/build/-/jobs/154041
- ~dipper https://gitlab.e.foundation/e/priv/os/build/-/jobs/154047
- ~dream2lte https://gitlab.e.foundation/e/priv/os/build/-/jobs/154049
- ~enchilada https://gitlab.e.foundation/e/priv/os/build/-/jobs/154051
- ~ether https://gitlab.e.foundation/e/priv/os/build/-/jobs/154052
- ~f1f https://gitlab.e.foundation/e/priv/os/build/-/jobs/154053
- ~find7 https://gitlab.e.foundation/e/priv/os/build/-/jobs/154055
- ~guacamoleb https://gitlab.e.foundation/e/priv/os/build/-/jobs/154061
- ~s2 https://gitlab.e.foundation/e/priv/os/build/-/jobs/154073
- ~tissot https://gitlab.e.foundation/e/priv/os/build/-/jobs/154078Alexandre RouxSooraj Ssooorajjj@gmail.comAlexandre Rouxhttps://gitlab.e.foundation/e/backlog/-/issues/2424Microphone choppy on LeEco S2 X5222022-09-21T01:03:51ZEric RothoffMicrophone choppy on LeEco S2 X522- /e/ version:e-0.11-p-2020090271190-dev-s2
- Device model(s):LeEco S2 X522
Technically it is a LeEco S3 Le X522-b which I was told using the LeEco S2 X522 image from the LineageOS/ reddit
## Summary
<Summarize the bug encountered brie...- /e/ version:e-0.11-p-2020090271190-dev-s2
- Device model(s):LeEco S2 X522
Technically it is a LeEco S3 Le X522-b which I was told using the LeEco S2 X522 image from the LineageOS/ reddit
## Summary
<Summarize the bug encountered briefly and precisely>
When making phone calls, my voice when talking is choppy. Incoming is crystal clear, and I checked with another phone, and it isn't a problem with the service. I don't remember it being choppy on the standard ROM but it is an older phone. I tried just doing a recording with the phone, and it recorded and replayed crystal clear. So the problem isn't with the Mic, but with the program sending the sound to the carrier.
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
Making a call using the phone and asking the person listening how the sound quality is. You can hear fine.
**What is the current behavior?**
<What actually happens>
Choppy sound received on the other end of a phone call.
**What is the expected correct behavior?**
<What you should see instead>
The sound on the other end should be as clear and what you are receiving.
## 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/2417Volume on LeEco S2 X5222023-04-05T01:03:28ZEric RothoffVolume on LeEco S2 X522- /e/ version:
e-0.11-p-2020090271190-dev-s2
- Device model(s):
LeEco S2 X522
## Summary
<Summarize the bug encountered briefly and precisely>
The Up and Down Volume on the phone only affects the Media Volume and not the Ring Volume or...- /e/ version:
e-0.11-p-2020090271190-dev-s2
- Device model(s):
LeEco S2 X522
## Summary
<Summarize the bug encountered briefly and precisely>
The Up and Down Volume on the phone only affects the Media Volume and not the Ring Volume or the Notifications Volume.
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
Press the up or down volume on the phone while having the Sound open and you can see only the one is effected.
**What is the current behavior?**
<What actually happens>
The Up and Down Volume on the phone only affects the Media Volume and not the Ring Volume or the Notifications Volume.
**What is the expected correct behavior?**
<What you should see instead>
I believe that at least you should have the option to have the phone volume effect all three, the media volume, the Ringer Volume and the Notification Volume. Currently you have the option to tie the Ringer Volume with the Notification Volume, but that isn't connected to the volume on the phone. This makes it hard to turn off the ringer when you go to a meeting. The ideal would be when you have the phone open and talking, the phone volume adjusts the call volume, When you have media playing, the phone volume adjusts the media volume, and when neither of them are running the phone volume adjusts the Ringer Volume and notification volumes. (Having an option to tie the two together is good, but then you should have another option for the phone volume to control one or both of them.)
## 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>
Right now you can change the volumes by going into settings, and change the volumes there, but it is very inconvenient if you go into a lot of meetings.
**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/1341Always on VPN not working FP32020-05-27T18:01:11ZAndré LamAlways on VPN not working FP3- /e/ version: e-0.9-p-2020051454091
- Device model: FP3, Leeco S2
- When it started to occur: Always
- Reproducible with the last /e/ version: IMG-e-0.9-p-2020051454091-dev-FP3
- Reproducible with LineageOS: -
## Summary
Always on VPN ...- /e/ version: e-0.9-p-2020051454091
- Device model: FP3, Leeco S2
- When it started to occur: Always
- Reproducible with the last /e/ version: IMG-e-0.9-p-2020051454091-dev-FP3
- Reproducible with LineageOS: -
## Summary
Always on VPN does not start after reboot.
- [ ] 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 app
- [X] The bug concerns security
- [X] The bug concerns privacy
## The problem
Always on VPN does not start after reboot, message is shown. Used VPN is Private Internet Access (PIA)
**Steps to reproduce**
Enable VPN > Always on VPN
Reboot.
**What is the current behavior?**
VPN is not turned on after reboot.
**What is the expected correct behavior?**
VPN on after reboot.
## Technical informations
**Relevant logs (`adb logcat`)**
[adb.txt](/uploads/6d2db68e369a5eff30318e46717f8095/adb.txt)
**Relevant screenshots**
![vpn1](/uploads/3580452c23c14f0711300fd310eebb99/vpn1.jpg)
![vpn2](/uploads/fecd380d0a14a3c4fe6086e9c7726b4c/vpn2.jpg)
## Solutions
-
**Workaround**
-
**Possible fixes**
-https://gitlab.e.foundation/e/backlog/-/issues/574LeEco L2 significant battery drop with "airplane" mode2019-11-08T12:41:39ZTheMajorTom 🏄LeEco L2 significant battery drop with "airplane" modeThe night, when "airplane" mode is on, i notice a recurrent battery drop by 20% (approximately).
* System version : 0.1-201810241661 (not only with this version)
* Apparel model : LeTv L2 X52X
* API LineageOS : Guava(7)
* Kernel : ...The night, when "airplane" mode is on, i notice a recurrent battery drop by 20% (approximately).
* System version : 0.1-201810241661 (not only with this version)
* Apparel model : LeTv L2 X52X
* API LineageOS : Guava(7)
* Kernel : 3.10.84-lineageos-g50894e77117
* Build : Le2_CN-userdebug 7.1.2 NJH47F 200181024 dev-keyshttps://gitlab.e.foundation/e/backlog/-/issues/201Phone not switching on LeEco le22019-12-16T15:14:04ZroncosPhone not switching on LeEco le2# (Issue title)
## Summary
I am having trouble with starting up my phone after running the battery down to 0% and recharging.
Even when the battery is back up to 100% the phone won't turn on. In the past this has also happened after up...# (Issue title)
## Summary
I am having trouble with starting up my phone after running the battery down to 0% and recharging.
Even when the battery is back up to 100% the phone won't turn on. In the past this has also happened after upgrading the OS. In the past the phone did restart after 1 or 2 attempts or sometimes a hard reset. Now nothing seems to get it started.
Issue has previously discussed here: https://community.e.foundation/t/phone-not-switching-on-leeco-le2/1740/4
Seems like it is maybe related to this: https://gitlab.e.foundation/e/management/issues/85
## Steps to reproduce
Run battery to 0% and try to turn on phone.
## What is the current behaviour?
* Hold power button until LeEco logo appears
* Release power button
* /e/ logo appears with bouncing dot beneath
* The "My data is my data" slogan does NOT appear.
* Phone goes dead.
If I hold power and up volume the phone does enter recovery, but I have not researched which options to choose here yet.
## What is the expected correct behavior?
Phone should start-up normally
## Relevant logs and/or screenshots
I will paste logs if someone tells me how to get them.https://gitlab.e.foundation/e/backlog/-/issues/179Freezing device with six taps on "Airplane mode"-icon2019-12-07T11:58:07ZMarkusFreezing device with six taps on "Airplane mode"-icon# Freezing device with six taps on "Airplane mode"-icon
## Summary
It is possible to reliably freeze the device with 6 taps on the "Airplane mode"-icon in the status bar.<br>
The first time I stumbled over this issue, I needed only 2 ta...# Freezing device with six taps on "Airplane mode"-icon
## Summary
It is possible to reliably freeze the device with 6 taps on the "Airplane mode"-icon in the status bar.<br>
The first time I stumbled over this issue, I needed only 2 taps. Reproducing this issue with only 2 taps is possible, but this seems to be a bit random and related to timing.
Image: e-0.1-201811292121-nightly-s2
## Steps to reproduce
As a prerequisite, Airplane mode is off.
1. Extend the status bar.
1. Tap on the "Airplane mode"-icon
1. Wait about 3 seconds
1. Tap on the "Airplane mode"-icon
1. Wait until prompted for PIN and log in
1. Extend the status bar.
1. Tap on the "Airplane mode"-icon
1. Wait about 3 seconds
1. Tap on the "Airplane mode"-icon
1. Wait about 3 seconds
1. Tap on the "Airplane mode"-icon
1. Wait about 3 seconds
1. Tap on the "Airplane mode"-icon
## What is the current behavior?
Several seconds after the last tap, the lock-screen is displayed but it is unresponsive.<br>
Again several seconds later the display switches off and the only way to access the device is to press the power button very long, so that the device reboots.
## What is the expected correct behavior?
The device should stay responsive.
## Relevant logs and/or screenshots
I have a logcat (2.8MB), that contains the process of reproducing this issue and the logcat ends when the device freezes.<br>
PM me, if you want access to that logcat.
This video shows the final two taps of reproducing the bug, the unresponsive pin-screen, the freeze, and the reboot:
![freeze-device4](/uploads/f4f579b2194d878e5602821246c2d9c7/freeze-device4.mp4)
## Workaround
Don't press the "Airplane mode"-icon multiple times in quick succession.https://gitlab.e.foundation/e/backlog/-/issues/23Device: leEco Le2 (s2) "Serious camera error"2022-07-22T18:45:30ZAndré LamDevice: leEco Le2 (s2) "Serious camera error"Lot of serious camera error's. Also with Camera2 API enabeled. Happen's on Lineage OS 14.1 also...Lot of serious camera error's. Also with Camera2 API enabeled. Happen's on Lineage OS 14.1 also...https://gitlab.e.foundation/e/backlog/-/issues/18IR not allowed SELinux leEco Le2 (s2)2021-04-23T22:28:55ZAndré LamIR not allowed SELinux leEco Le2 (s2)IR apps not working, not allowed by SELinux.IR apps not working, not allowed by SELinux.