Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2024-03-01T14:10:42Zhttps://gitlab.e.foundation/e/backlog/-/issues/7490Emergency broadcast message with illegible text2024-03-01T14:10:42ZToni PanadèsEmergency broadcast message with illegible text- /e/ version: 1.15-r-20230915330641-stable-star2lte
- Device model(s): SM-G965F
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
I received an emergency broadcast message with illegible text....- /e/ version: 1.15-r-20230915330641-stable-star2lte
- Device model(s): SM-G965F
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
I received an emergency broadcast message with illegible text. Other devices at the edge with different operating systems could read it correctly.
## The problem
**Steps to reproduce**
Can't reproduce by myself (emergency message broadcasting)
**What is the current behavior?**
I receive the broadcast message, but illegible, maybe because is not correctly decoded ?
Displayed in my /e/os mobile phone : _.D¿l,Å@ @4¥Δæ@2@R£òù¿Æ@ @L¥p
¡1@R£òù æ@x@8£ £@é@&£xè Π@E@h$@è@(@¤£(é@_@E@8$¡
¡)@¡
Other phones near mine in the same moment :
ALERTE MÉTÉO
Préfets du Finistère, des Côtes-d’Armor et de la Manche
Vigilance ROUGE à partir de minuit dans le Finistère, les Côtes d’Armor et la Manche.
1. Mettez-vous à l’abri en lieu sûr dès à présent ;
2. Limitez vos déplacements aux seules urgences absolues ;
3. N’empruntez pas les routes inondées ;
4. Écartez-vous des berges, des cours d’eau et du littoral.
Respectez les consignes diffusées à la radio, la télévision et sur les médias sociaux.
SOYEZ PRUDENTS
<details><summary>Screenshot</summary>
![image](/uploads/b7302580a0a9598135e1abb309e26ce5/image.png)
</details>
**What is the expected correct behavior?**
Be able to decode alerts correctly.
## Technical informations
**Relevant screenshots**
![IMG_20231101_211531](/uploads/36dd478bc55c2557980552091ef823c7/IMG_20231101_211531.jpg)
![alert_message_notification_20231102](/uploads/8ff28d02d2ca491a3d491b4a4906d286/alert_message_notification_20231102.png) ![alert_message_notification_expanded_20231102](/uploads/a290e5e4eb1991c46cd34a9884611387/alert_message_notification_expanded_20231102.png)
**Logs**
Aude has logs available if needed.
## Solutions
**Workaround**
No workarpund possible
**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/7381Notifications are not issued2024-03-18T06:50:51ZHaydee ElizondoNotifications are not issued- /e/ version:1.15
- Device model(s): Fairphone 4 / Fairphone 3 / Teracube 2e
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: no
## Summary
In some cases the phone does not issue notifications until you unl...- /e/ version:1.15
- Device model(s): Fairphone 4 / Fairphone 3 / Teracube 2e
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: no
## Summary
In some cases the phone does not issue notifications until you unlock the screen, the phone is not in battery saving mode and this happens with some applications. Permissions to receive notifications have been checked and all permissions appear to be enabled.
Among the applications that do not issue notifications are,
Telegram, Signal, Calendar, SMS, Instagram.
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
**What is the current behavior?**
If the phone is with the screen locked, notifications do not arrive until it is unlocked and the app is entered.
**What is the expected correct behavior?**
To issue notifications from applications that have permission to alert.
## Technical informations
[bugreport-lineage_FP3-SQ3A.220705.004-2023-10-05-12-44-03.zip](/uploads/be679640d0c9acbdb7393c69f73823d9/bugreport-lineage_FP3-SQ3A.220705.004-2023-10-05-12-44-03.zip)
<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/4501NFC extended length not working2024-03-27T09:18:14ZGabor BNFC extended length not working- /e/ version: 0.20-q-20211216151800-dev-starlte
- Device model(s): Samsung Galaxy S9 (starlte)
- Device rooted: yes
## Summary
NFC extended length is not supported. It is important for example for eGovernment capability using the el...- /e/ version: 0.20-q-20211216151800-dev-starlte
- Device model(s): Samsung Galaxy S9 (starlte)
- Device rooted: yes
## Summary
NFC extended length is not supported. It is important for example for eGovernment capability using the electronic ID card from Germany. This is probably a downstream issue in LineageOS. LOS supports NFC extended length since LOS 15.1, but the configuration needs to be setup per device.
AusweisApp2 from Aurora Store, try to read an ID card with the phone.
**Steps to reproduce**
How to test: Install AusweisApp2 from Aurora Store, try to read an ID card with the phone.
**What is the current behavior?**
The ID card recognition fails with the error message that NFC extended length is not supported.
**What is the expected correct behavior?**
Expected: NFC extended length is supported by the OS. The phone is capable of NFC EL with Samsung ROMs.
## Technical informations
**Relevant logs (`adb logcat`)**
---
**Relevant screenshots**
![Screenshot_20211228-110417_AusweisApp2](/uploads/1210a748294b1d6143825b94498db8db/Screenshot_20211228-110417_AusweisApp2.png)
## Solutions
**Workaround**
n/a
**Possible fixes**
LOS supports NFC extended length since LOS 15.1, but the configuration needs to be setup per device. See: [link](https://www.lineageos.org/Changelog-15/)