Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2022-09-09T01:03:39Zhttps://gitlab.e.foundation/e/backlog/-/issues/3003Build in failure for j5nlte2022-09-09T01:03:39ZRomain HunaultBuild in failure for j5nltehttps://gitlab.e.foundation/e/priv/os/build/-/jobs/161169https://gitlab.e.foundation/e/priv/os/build/-/jobs/161169https://gitlab.e.foundation/e/backlog/-/issues/2747Fix Oreo build failure for v0.152021-04-19T15:27:25ZRomain HunaultFix Oreo build failure for v0.15We faced multiple build failure for v0.15 ([pipeline 105776](https://gitlab.e.foundation/e/priv/os/build/-/pipelines/105776))
- ~j5lte https://gitlab.e.foundation/e/priv/os/build/-/jobs/154102
- ~j5ltechn https://gitlab.e.foundation...We faced multiple build failure for v0.15 ([pipeline 105776](https://gitlab.e.foundation/e/priv/os/build/-/pipelines/105776))
- ~j5lte https://gitlab.e.foundation/e/priv/os/build/-/jobs/154102
- ~j5ltechn https://gitlab.e.foundation/e/priv/os/build/-/jobs/154103
- ~j5nlte https://gitlab.e.foundation/e/priv/os/build/-/jobs/154104
- ~j53gxx https://gitlab.e.foundation/e/priv/os/build/-/jobs/154101Alexandre RouxSooraj Ssooorajjj@gmail.comAlexandre Rouxhttps://gitlab.e.foundation/e/backlog/-/issues/2230Disconnected call when the loudspeaker is switched on2022-09-23T01:04:11ZRadek TůmaDisconnected call when the loudspeaker is switched on- /e/ version: e-0.12-o-2020100176269-dev-j5nlte
- Device model(s): Samsung Galaxy J5N LTE
## The problem
Hello,
if I turn on the loudspeaker during a call, the call is disconnected.- /e/ version: e-0.12-o-2020100176269-dev-j5nlte
- Device model(s): Samsung Galaxy J5N LTE
## The problem
Hello,
if I turn on the loudspeaker during a call, the call is disconnected.https://gitlab.e.foundation/e/backlog/-/issues/1498Weird image appeared on images.ecloud.global2021-02-02T07:55:36Zsmart5Weird image appeared on images.ecloud.global- Device model: J500FN / J5nlte
## Summary
The Samsung J500FN is supported by /e/ with e-0.8 but an image for e-0.9 appeared some days ago on the list here https://images.ecloud.global/dev/j5nlte/ . Weird
Note that the changelog linke...- Device model: J500FN / J5nlte
## Summary
The Samsung J500FN is supported by /e/ with e-0.8 but an image for e-0.9 appeared some days ago on the list here https://images.ecloud.global/dev/j5nlte/ . Weird
Note that the changelog linked to this image refers to e-0.7. Really weird
- [x] The bug concerns security
- [x] The bug concerns privacyhttps://gitlab.e.foundation/e/backlog/-/issues/1497Unable to encrypt device after fresh install2023-04-03T01:03:28Zsmart5Unable to encrypt device after fresh install- /e/ version: e-0.8-o-2020041649925-dev-j5nlte
- Device model: Samsung J500FN
- When it started to occur: right after a fresh install
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: Device not supported
## ...- /e/ version: e-0.8-o-2020041649925-dev-j5nlte
- Device model: Samsung J500FN
- When it started to occur: right after a fresh install
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: Device not supported
## Summary
After a fresh install of [e-0.8](https://images.ecloud.global/dev/j5nlte/e-0.8-o-2020041649925-dev-j5nlte.zip) I can't encrypt the device in Settings > Security > Encrypt : the smartphone just restart and nothing is encrypted
- [x] The bug concerns security
- [x] The bug concerns privacy
## Solutions
Go into TWRP > Wipe > Advanced Wipe > select Data > Repair or Change File System > Resize File System > swipe to confirm. Reboot into the system and try to encrypt again, this time it will work.
Source : https://community.e.foundation/t/unofficial-build-samsung-galaxy-j5-2015-j5nlte-e-os-pie/15952https://gitlab.e.foundation/e/backlog/-/issues/1181NFC is missing from /e/ but the phone has it on j5nlte2022-10-06T01:03:56ZAnonymeNFC is missing from /e/ but the phone has it on j5nlte- /e/ version: e-0.8-o-2020041649925-dev-j5nlte
- Device model: j5nlte
- When it started to occur: Since always I think
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: No
## Summary
<Summarize the bug encou...- /e/ version: e-0.8-o-2020041649925-dev-j5nlte
- Device model: j5nlte
- When it started to occur: Since always I think
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: No
## Summary
<Summarize the bug encountered briefly and precisely>
My phone has NFC but there is 0 mention of NFC in Settings in /e/ Oreo.
<Please tick one of the following sentences if relevant>
- [ ] 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
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
Try to activate NFC somewhere, you won't find any setting to do it. Nothing in Settings, and nothing in the control center (in the notification pannel).
**What is the current behavior?**
<What actually happens>
**What is the expected correct behavior?**
<What you should see instead>
I should have settings to activate NFC, which is the case in [LineageOS 17.1](https://forum.xda-developers.com/galaxy-j5/development/unofficial-lineageos-17-1-beta-galaxy-j5-t4038777) and probably in [LineageOS 16.0](https://forum.xda-developers.com/galaxy-j5/development/unofficial-lineageos-16-0-galaxy-j5-t3851124) (I forgot to check).
I have never used NFC in this phone so I can't be 100% sure it's there and it's working, but on the internet, I see everywhere that this phone has it. And if it's there in LineageOS 17 (and activate by default), I guess it's really here and working.
So I really think /e/ "forgot" to activate it in the build or I don't know.
## 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/1180Encryption not working without resizing data partition on j5nlte2023-04-04T05:32:26ZAnonymeEncryption not working without resizing data partition on j5nlte- /e/ version: e-0.8-o-2020041049060-dev-j5nlte
- Device model: j5nlte
- When it started to occur: Since always
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: Yes
## Summary
<Summarize the bug encountered ...- /e/ version: e-0.8-o-2020041049060-dev-j5nlte
- Device model: j5nlte
- When it started to occur: Since always
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: Yes
## Summary
<Summarize the bug encountered briefly and precisely>
The phone can't be encrypted without resizing the data partition into TWRP.
<Please tick one of the following sentences if relevant>
- [ ] 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
- [ ] The bug concerns security
- [x] The bug concerns privacy
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
I installed the stockROM in order to do a fresh installation of a new version of TWRP and custom ROMs.
With [LineageOS 17.1](https://forum.xda-developers.com/galaxy-j5/development/unofficial-lineageos-17-1-beta-galaxy-j5-t4038777) : Encryption not working, even after the use of the "Resize File System" into TWRP, and even after manually resizing the partition in the terminal of TWRP. Trying to encrypt the phone will mess the system and you won't be able to enter in it again without format the data partition.
**What is the current behavior?**
<What actually happens>
With [LineageOS 16.0](https://forum.xda-developers.com/galaxy-j5/development/unofficial-lineageos-16-0-galaxy-j5-t3851124) and /e/ Oreo : When I try to encrypt the phone after a fresh installation, the phone restarts (kind of, it's quick and the SIM PIN code isn't asked) but the phone isn't encrypted.
**What is the expected correct behavior?**
<What you should see instead>
The user should be able to encrypt the phone directly without any more actions.
## Technical informations
There is no difference between :
- Use the "Resize File System" in TWRP > Wipe > Advanced Wipe > select Data > Resize or Repair File System > Resize File System.
- Or resize the data partition in the Terminal of TWRP
Both of those actions will decrease the /dev/block/mmcblk0p28 to 1257975 instead of 1257979.
## 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>
If possible, automatically resize the data partition to 1257975 in the installation process.https://gitlab.e.foundation/e/backlog/-/issues/1174No DRM at all on j5nlte2021-02-02T11:33:03ZAnonymeNo DRM at all on j5nlte- /e/ version: e-0.8-o-2020041649925-dev-j5nlte.zip
- Device model: j5nlte
- When it started to occur: always
- Reproducible with the last /e/ version: yes
- Reproducible with LineageOS: YES in [LineageOS 16.0](https://forum.xda-develope...- /e/ version: e-0.8-o-2020041649925-dev-j5nlte.zip
- Device model: j5nlte
- When it started to occur: always
- Reproducible with the last /e/ version: yes
- Reproducible with LineageOS: YES in [LineageOS 16.0](https://forum.xda-developers.com/galaxy-j5/development/unofficial-lineageos-16-0-galaxy-j5-t3851124) / NO with [LineageOS 17.1](https://forum.xda-developers.com/galaxy-j5/development/unofficial-lineageos-17-1-beta-galaxy-j5-t4038777)
## Summary
<Summarize the bug encountered briefly and precisely>
I have no DRM on my phone. No Security Level 1 or L3 neither. I think there are others /e/OS phone that don't have this issue.
In [LineageOS 16.0](https://forum.xda-developers.com/galaxy-j5/development/unofficial-lineageos-16-0-galaxy-j5-t3851124), same thing, it doesn't work.
In [LineageOS 17.1](https://forum.xda-developers.com/galaxy-j5/development/unofficial-lineageos-17-1-beta-galaxy-j5-t4038777), it works, I have Security Level 3.
<Please tick one of the following sentences if relevant>
- [ ] 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
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
Try to use an app that requires DRM right (like an app to watch a TV channel (Molotov, Netflix).
And "DRM Info" app shows no DRM info at all.
**What is the current behavior?**
<What actually happens>
It will show an error message about the DRM and I won't be able to watch what I want.
When I install DRM Info on my phone with LineageOS 17.1, it works (see screenshot).
It doesn't work with /e/ on Oreo and doesn't work on LineageOS 16.0.
**What is the expected correct behavior?**
<What you should see instead>
The phone should have DRM L1 or at least L3.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
How the "DRM Info" app is supposed to look like (screenshot from Aurora Store) :
![254eb441dd65c469826d301d89b4e75595c224b70216defaed8e98c99e916cd4](/uploads/b8efd1f11b5bf2cf771706a61edf1e41/254eb441dd65c469826d301d89b4e75595c224b70216defaed8e98c99e916cd4)
How it is on my phone :
![500b6b4a635ac67d45cc9a31b739376a29eafa91b4c4ca3d51c9b79d043502d0](/uploads/46d6b6ac1253e079157bca78f376be35/500b6b4a635ac67d45cc9a31b739376a29eafa91b4c4ca3d51c9b79d043502d0)
How it is on my phone with LineageOS 16.0 :
![LOS_16.0_DRM](/uploads/51fd1f0fb2061d96910a7310d090d0d3/LOS_16.0_DRM.png)
How it is on my phone with LineageOS 17.1 :
![Screenshot_20200418-145403_DRM_Info](/uploads/c5eb080533aa93e5f423ec3ef1b390c2/Screenshot_20200418-145403_DRM_Info.png)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>https://gitlab.e.foundation/e/backlog/-/issues/1173Samsung Galaxy J5N LTE can't find new version2022-02-10T15:52:47ZRadek TůmaSamsung Galaxy J5N LTE can't find new version- /e/ version: e-0.8-o-2020041049060
- Device model: Samsung Galaxy J5N LTE
Hello,
I have version e-0.8-o-2020041049060-dev-j5nlte. I see in https://images.ecloud.global/dev/j5nlte/, that exist new version e-0.8-o-2020041449616-dev-j5nl...- /e/ version: e-0.8-o-2020041049060
- Device model: Samsung Galaxy J5N LTE
Hello,
I have version e-0.8-o-2020041049060-dev-j5nlte. I see in https://images.ecloud.global/dev/j5nlte/, that exist new version e-0.8-o-2020041449616-dev-j5nlte. But my phone says, that new versions are not founded.
Radek Tumahttps://gitlab.e.foundation/e/backlog/-/issues/901Wake up the phone using the back button in the settings is not reflected2021-12-14T16:08:46ZRadek TůmaWake up the phone using the back button in the settings is not reflected- /e/ version: e-0.7-o-2020012438713-dev-j5nlte
- Device model: Samsung Galaxy J5N LTE
Wake up the phone using the back button in the settings is not reflected.- /e/ version: e-0.7-o-2020012438713-dev-j5nlte
- Device model: Samsung Galaxy J5N LTE
Wake up the phone using the back button in the settings is not reflected.https://gitlab.e.foundation/e/backlog/-/issues/646Samsung Galaxy J5N LTE - update from e-0.7-o-2019122435222 to e-0.7-o-202001...2022-10-06T01:03:56ZRadek TůmaSamsung Galaxy J5N LTE - update from e-0.7-o-2019122435222 to e-0.7-o-2020011237311 ends at TWRP without further activity- /e/ version: e-0.7-o-2020011237311
- Device model: Samsung Galaxy J5N LTE
## Summary
Update from e-0.7-o-2019122435222 to e-0.7-o-2020011237311 ends at TWRP without further activity (like some previous updates).
![IMG_20200112_15411...- /e/ version: e-0.7-o-2020011237311
- Device model: Samsung Galaxy J5N LTE
## Summary
Update from e-0.7-o-2019122435222 to e-0.7-o-2020011237311 ends at TWRP without further activity (like some previous updates).
![IMG_20200112_154118](/uploads/f7e0269c39f819ac7d9eb841c77c80f4/IMG_20200112_154118.jpg)I followed the instructions at https://community.e.foundation/t/howto-update-e/3222 - B) Cases where the update must be done manually.
Then was appeared unnecessary prompt to install TWRP (I have the latest 3.3.1-0) - see attached picture. Then maybe it would be good to add it to the documentation at https://community.e.foundation/t/howto-update-e/3222 - that choose do not install if the current version is installed.
Radek Tumahttps://gitlab.e.foundation/e/backlog/-/issues/628SElinux is Permissive by default and can't be Enforcing without issues2023-11-30T10:39:54ZAnonymeSElinux is Permissive by default and can't be Enforcing without issues- /e/ version: e-0.8-o-2020041649925-dev-j5nlte
- Device model: j5nlte (& j5lte)
- When it started to occur: Since always
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: Yes with LineageOS 17.1
## Summary
<...- /e/ version: e-0.8-o-2020041649925-dev-j5nlte
- Device model: j5nlte (& j5lte)
- When it started to occur: Since always
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: Yes with LineageOS 17.1
## Summary
<Summarize the bug encountered briefly and precisely>
<Please tick one of the following sentences if relevent>
- [ ] The device is unusable
- [ ] The bug is the source of a data loss or a big waste of time
- [ ] The bug concerns a tierce app
- [x] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
**What is the current behavior?**
<What actually happens>
In System > About phone, SElinux status is Permissive.
In Trust it shows Disabled but looks like it shows Disabled when it's not enforcing.
With an app and root access I switched to Enforcing, but the camera wasn't working anymore in Open Camera and Signal. Maybe other errors would have happen, I switched back to Permissive immediately.
Here is the topic on the forum :
https://community.e.foundation/t/how-to-turn-on-selinux/10423?u=anonyme
**What is the expected correct behavior?**
<What you should see instead>
SElinux should be "Enforcing" by default and without issues.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
![IMG_20191216_163810](/uploads/ed3c3458ffcbd9b1889bc56a57c45264/IMG_20191216_163810.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>