Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2022-12-21T02:03:22Zhttps://gitlab.e.foundation/e/backlog/-/issues/4435Samsung Galaxy S4 mini. Rear camera and torch doesn't work2022-12-21T02:03:22ZVincent BourgmayerSamsung Galaxy S4 mini. Rear camera and torch doesn't work- /e/ version: Android 7.1.2 - build number: e_serranoltexx-userdebug 7.1.2 NJH47F 20201210 dev-keys
- Device model(s): Samsung galaxy S4 mini
- Device rooted: yes/no no
## Summary
Torch app doesn't work.
When opening camera, rear came...- /e/ version: Android 7.1.2 - build number: e_serranoltexx-userdebug 7.1.2 NJH47F 20201210 dev-keys
- Device model(s): Samsung galaxy S4 mini
- Device rooted: yes/no no
## Summary
Torch app doesn't work.
When opening camera, rear camera doesn't work.
It was working few days ago.
## The problem
**Steps to reproduce**
Start device
Open Camera
**What is the current behavior?**
Camera frame Screen stay black with message telling impossible to start camera because already used by another
app (id=0)
**What is the expected correct behavior?**
Camera works
## Technical informations
- baseband version: I9195XXSCQAN
- API lineageOS: Guava (7)
- Date de compilation: december 10th 2020
- Model: GT-I9195
All update discovered are installed.
Last update december 10th 2020
Nothing special done with the phone.
Usage is: Alarm, photo, SMS & call plus one game.
**Relevant logs (`adb logcat`)**
[camera-s4-mini.txt](/uploads/146f437d73543de8dfc6500eaf3cd249/camera-s4-mini.txt)
**Relevant screenshots**
![image](/uploads/c114b840f4ee0cab8fd9691a0507040c/image.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/2104No data connection at all (4G/LTE)2022-10-07T01:03:27ZRomain HunaultNo data connection at all (4G/LTE)- /e/ version: ~q
- Device model(s): ~"FP3/FP3+"
- Community channel: https://community.e.foundation/t/fairphone-3-with-e-pre-installed-localization-not-accurate/23108/11
## Summary
<Summarize the bug encountered briefly and precisel...- /e/ version: ~q
- Device model(s): ~"FP3/FP3+"
- Community channel: https://community.e.foundation/t/fairphone-3-with-e-pre-installed-localization-not-accurate/23108/11
## Summary
<Summarize the bug encountered briefly and precisely>
A user report LTE not working on his FP3+
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
Try to connect to internet only with LTE
**What is the current behavior?**
<What actually happens>
No internet connection
**What is the expected correct behavior?**
<What you should see instead>
Being able to access internet via LTE
## 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/1172System partition too large2022-10-04T01:03:28ZRomain HunaultSystem partition too large- /e/ version: 0.8
- Device model: hammerhead, m8
- When it started to occur: April
- Reproducible with the last /e/ version: yes
- Reproducible with LineageOS: no
## Summary
<Summarize the bug encountered briefly and precisely>
Build ...- /e/ version: 0.8
- Device model: hammerhead, m8
- When it started to occur: April
- Reproducible with the last /e/ version: yes
- Reproducible with LineageOS: no
## Summary
<Summarize the bug encountered briefly and precisely>
Build failed for some devices because the system partition is too large. Consequently, those devices can't receive new updates.
<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>
Due to some modifications in our code base (need to identify precisely which ones), the size of the system partition is more important.
**What is the current behavior?**
<What actually happens>
Consequently, this size exceeds the max size allowed on some devices. Build failed, and devices can't receive updates.
**What is the expected correct behavior?**
Build succeeds
<What you should see instead>
## 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>
A workaround currently applied on some devices is to remove some default apps. It's undesirable to extend this behaviour to more devices, are it creates an inconsistent user experience between devices.
**Possible fixes**
1. Decrease the size of the system partition
1. Increase the system max size in the device tree source code, and resize partitions on the devices
**Question**
Would it be possible to resize the data partition too, to [allow encryption feature](#1180) to work out of the box?https://gitlab.e.foundation/e/backlog/-/issues/3462APN settings vanishes and cant be set -> No mobile data, no MMS2022-06-14T02:18:25ZMorgan LeijströmAPN settings vanishes and cant be set -> No mobile data, no MMS- /e/ version: q, _(Edit: to be specific: Manually installed from https://images.ecloud.global/stable/FP3/IMG-e-0.17-q-20210615117215-stable-FP3.zip - and sha256sum checked.)_
- Device model(s): FP3
- Device rooted: no
## Summary
APN s...- /e/ version: q, _(Edit: to be specific: Manually installed from https://images.ecloud.global/stable/FP3/IMG-e-0.17-q-20210615117215-stable-FP3.zip - and sha256sum checked.)_
- Device model(s): FP3
- Device rooted: no
## Summary
APN settings vanishes after update or reboot, and for some users it can not get set again.
This results in user having no mobile data connection (internet, MMS)
## The problem
Checking in settings under Network and Internet > Mobile network > Advanced > APN, there is no APN configured.
Sometimes it works to click the three dots up right and select to reset defaults, and APN appears.
This worked for me and at least one other user.
But after a failed update of /e/ APN was aging gone, and for me reset defaults no longer populate APN.
This happens for a few users - at least two of us in this thread:
See i.e https://community.e.foundation/t/solved-losing-network-connection-after-update/29622/10
My story:
On my FP3 i have been using a development version of /e/ since september 2020, and it have been working great.
But after i reinstalled to official /e/ a couple weeks ago i had no mobile connection.
After a while i found APN was clear, and reset it, and it worked for a couple days until i let it OTA update, and failed, so i selected to restore to other slot.
Now APN is gone again, and what is worse, is they do not appear if i reset to defaults.
The APN settings page is just blank, with a greyed tiny text saying that the settings are not accessible for this user.
Well I am the only user...
Anyway clicking the (+), i get to enter settings for a new APN, and clicking th ethrre dots i can select save. No visible error message, but there did not appear a APN as result.https://gitlab.e.foundation/e/backlog/-/issues/2976Apps app completely resets updated apps (that originated from a different sou...2022-05-02T11:39:27ZPixelcodeApps app completely resets updated apps (that originated from a different source?)- /e/ version: 0.15-q-20210316105636-dev-FP3
- Device model(s): FP3
## The problem
**Steps to reproduce**
Install an app from a third-party source like F-Droid, Aurora Store, the browser etc. Go to the Apps app and install an update. ...- /e/ version: 0.15-q-20210316105636-dev-FP3
- Device model(s): FP3
## The problem
**Steps to reproduce**
Install an app from a third-party source like F-Droid, Aurora Store, the browser etc. Go to the Apps app and install an update. (AFAIK the issue is limited to these third-party cases but I'm not entirely sure.)
**What is the current behavior?**
The Apps app completely replaces the updated app and deletes all user data. Specifically, I installed the 2FA app andOTP through F-Droid and the update via Apps which is why I would've lost all my important 2FA stuff if I hadn't done a backup. I noticed similar behaviour with Signal and Reddit, both from Aurora.
**What is the expected correct behavior?**
The user data should be kept and the app itself should not be reset. This actually worked well on Pie but does not on Q.
## Solutions
**Workaround**
Don't use the Apps app lol.https://gitlab.e.foundation/e/backlog/-/issues/2100Can't save attachment to sdcard2022-02-14T03:59:04ZRomain HunaultCan't save attachment to sdcard- /e/ version: ~q
- Device model(s): ~"FP3/FP3+"
- community channel: https://community.e.foundation/t/fairphone-3/23157/2
## Summary
<Summarize the bug encountered briefly and precisely>
A user reported he can't save mail attachmen...- /e/ version: ~q
- Device model(s): ~"FP3/FP3+"
- community channel: https://community.e.foundation/t/fairphone-3/23157/2
## Summary
<Summarize the bug encountered briefly and precisely>
A user reported he can't save mail attachment
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. Receive a mail with an attachment
1. From mail app, save the attachment on SDcard
**What is the current behavior?**
<What actually happens>
Mail doesn't save the attachment.
**What is the expected correct behavior?**
<What you should see instead>
Attachment saved.
## Technical informations
It's not possible to modify permission, as there is no permission requested for Mail app.
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
2020-11-17 15:10:24.591 1605-1821/system_process E/LightsService: Light requested not available on this device. 2
2020-11-17 15:10:24.674 6367-8962/foundation.e.mail D/OpenPgp API: Stopped writing due to broken pipe (other end closed pipe?)
2020-11-17 15:10:24.691 691-1407/? D/audio_hw_primary: out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
2020-11-17 15:10:24.691 691-1407/? D/audio_hw_extn: audio_extn_set_anc_parameters: anc_enabled:0
2020-11-17 15:10:24.691 691-1407/? D/audio_hw_spkr_prot: audio_extn_fbsp_set_parameters: Speaker protection disabled
2020-11-17 15:10:24.695 691-3454/? D/audio_hw_primary: start_output_stream: enter: stream(0xef64a800)usecase(1: low-latency-playback) devices(0x2)
2020-11-17 15:10:24.695 691-3454/? D/audio_hw_primary: select_devices for use case (low-latency-playback)
2020-11-17 15:10:24.695 691-3454/? D/audio_hw_primary: select_devices: out_snd_device(2: speaker) in_snd_device(0: )
2020-11-17 15:10:24.695 691-3454/? I/msm8916_platform: platform_check_and_set_codec_backend_cfg:becf: afe: bitwidth 16, samplerate 48000 channels 2, backend_idx 0 usecase = 1 device (speaker)
2020-11-17 15:10:24.696 691-3454/? D/msm8916_platform: platform_split_snd_device: snd_device(2) num devices(1) new_snd_devices(0)
2020-11-17 15:10:24.696 691-3454/? I/msm8916_platform: platform_check_and_set_codec_backend_cfg: becf: new_snd_devices[0] is speaker
2020-11-17 15:10:24.696 691-3454/? I/msm8916_platform: platform_check_codec_backend_cfg:becf: afe: Codec selected backend: 0 current bit width: 16 sample rate: 48000 channels: 2 usecase 1 device (speaker)
2020-11-17 15:10:24.696 691-3454/? D/msm8916_platform: platform_check_codec_backend_cfg:becf: afe: playback on codec device not supporting native playback set default Sample Rate(48k)
2020-11-17 15:10:24.696 691-3454/? I/msm8916_platform: platform_check_codec_backend_cfg:becf: afe: Codec selected backend: 0 updated bit width: 16 sample rate: 48000 channels: 2
2020-11-17 15:10:24.696 691-3454/? D/audio_hw_primary: check_usecases_codec_backend:becf: force routing 0
2020-11-17 15:10:24.696 691-3454/? E/msm8916_platform: platform_check_backends_match: Invalid snd_device =
2020-11-17 15:10:24.696 691-3454/? D/audio_hw_primary: check_usecases_codec_backend:becf: (65) check_usecases curr device: speaker, usecase device: backends match 0
2020-11-17 15:10:24.696 691-3454/? D/audio_hw_primary: check_usecases_codec_backend:becf: check_usecases num.of Usecases to switch 0
2020-11-17 15:10:24.696 691-3454/? D/hardware_info: hw_info_append_hw_type : device_name = speaker
2020-11-17 15:10:24.696 691-3454/? D/msm8916_platform: platform_split_snd_device: snd_device(2) num devices(0) new_snd_devices(0)
2020-11-17 15:10:24.696 691-3454/? D/audio_hw_primary: enable_snd_device: snd_device(2: speaker)
2020-11-17 15:10:24.696 691-3454/? I/soundtrigger: audio_extn_sound_trigger_update_device_status: device 0x2 of type 0 for Event 1, with Raise=0
2020-11-17 15:10:24.696 691-3454/? D/audio_route: Apply path: speaker
2020-11-17 15:10:24.696 691-3454/? D/soundtrigger: audio_extn_sound_trigger_update_stream_status: uc_info->id 1 of type 0 for Event 3, with Raise=0
2020-11-17 15:10:24.696 691-3454/? D/audio_hw_utils: audio_extn_utils_send_app_type_cfg: usecase->out_snd_device speaker
2020-11-17 15:10:24.696 691-3454/? D/msm8916_platform: platform_split_snd_device: snd_device(2) num devices(0) new_snd_devices(0)
2020-11-17 15:10:24.697 691-3454/? D/audio_hw_utils: audio_extn_btsco_get_sample_rate:Not a BT SCO device, need not update sampling rate
2020-11-17 15:10:24.697 691-3454/? I/audio_hw_utils: send_app_type_cfg_for_device PLAYBACK app_type 69937, acdb_dev_id 14, sample_rate 48000, snd_device_be_idx 2
2020-11-17 15:10:24.698 691-3454/? D/msm8916_platform: platform_split_snd_device: snd_device(2) num devices(1) new_snd_devices(0)
2020-11-17 15:10:24.698 691-3454/? D/audio_hw_utils: audio_extn_btsco_get_sample_rate:Not a BT SCO device, need not update sampling rate
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 14, path = 0, app id = 0x11131, sample rate = 48000, afe_sample_rate = 48000
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> send_asm_topology
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> send_adm_topology
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> send_audtable
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE_SIZE
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_CAL cal_type[11] acdb_id[14] app_type[69937]
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> send_audvoltable
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_STEP_TABLE_SIZE
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_STEP_TABLE, vol index 0
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> AUDIO_SET_VOL_CAL cal type = 12
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TABLE_SIZE
2020-11-17 15:10:24.698 691-3454/? D/ACDB-LOADER: ACDB -> send_audstrmtable
2020-11-17 15:10:24.699 691-3454/? D/ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TABLE_V2
2020-11-17 15:10:24.699 691-3454/? D/ACDB-LOADER: ACDB -> audstrm_cal->cal_type.cal_data.cal_size = 16
2020-11-17 15:10:24.699 691-3454/? D/ACDB-LOADER: ACDB -> send_afe_topology
2020-11-17 15:10:24.699 691-3454/? D/ACDB-LOADER: ACDB -> ACDB_CMD_GET_AFE_TOPOLOGY_ID
2020-11-17 15:10:24.699 691-3454/? D/ACDB-LOADER: ACDB -> GET_AFE_TOPOLOGY_ID for adcd_id 14, Topology Id 1025e
2020-11-17 15:10:24.699 691-3454/? D/ACDB-LOADER: ACDB -> send_afe_cal
2020-11-17 15:10:24.699 691-3454/? D/ACDB-LOADER: ACDB -> ACDB_CMD_GET_AFE_COMMON_TABLE_SIZE
2020-11-17 15:10:24.699 691-3454/? D/ACDB-LOADER: ACDB -> ACDB_CMD_GET_AFE_COMMON_TABLE
2020-11-17 15:10:24.699 691-3454/? D/ACDB-LOADER: ACDB -> AUDIO_SET_AFE_CAL cal_type[16] acdb_id[14]
2020-11-17 15:10:24.699 691-3454/? D/ACDB-LOADER: ACDB -> send_hw_delay : acdb_id = 14 path = 0
2020-11-17 15:10:24.699 691-3454/? D/ACDB-LOADER: ACDB -> ACDB_AVSYNC_INFO: ACDB_CMD_GET_DEVICE_PROPERTY
2020-11-17 15:10:24.699 691-3454/? D/msm8916_platform: platform_split_snd_device: snd_device(2) num devices(0) new_snd_devices(0)
2020-11-17 15:10:24.699 691-3454/? I/msm8916_platform: platform_get_custom_mtmx_params: no matching param with id 0 ip_ch 2 op_ch 1 uc_id 1 snd_dev 2
2020-11-17 15:10:24.699 691-3454/? D/audio_hw_primary: enable_audio_route: apply mixer and update path: low-latency-playback
2020-11-17 15:10:24.699 691-3454/? D/audio_route: Apply path: low-latency-playback
2020-11-17 15:10:24.702 691-3454/? D/audio_hw_primary: select_devices: done
2020-11-17 15:10:24.706 691-3454/? D/msm8916_platform: platform_set_channel_map mixer_ctl_name:Playback Channel Map12
2020-11-17 15:10:24.706 691-3454/? D/msm8916_platform: platform_set_channel_map: set mapping(1 2 0 0 0 0 0 0) for channel:2
2020-11-17 15:10:24.750 691-3454/? D/audio_hw_primary: start_output_stream: exit
2020-11-17 15:10:24.750 691-3454/? D/msm8916_platform: platform_split_snd_device: snd_device(2) num devices(0) new_snd_devices(0)
2020-11-17 15:10:24.750 691-3454/? I/msm8916_platform: platform_get_custom_mtmx_params: no matching param with id 0 ip_ch 2 op_ch 1 uc_id 1 snd_dev 2
2020-11-17 15:10:27.855 691-1407/? D/audio_hw_primary: out_standby: enter: stream (0xef64a800) usecase(1: low-latency-playback)
2020-11-17 15:10:27.925 691-1407/? D/audio_hw_primary: disable_audio_route: reset and update mixer path: low-latency-playback
2020-11-17 15:10:27.931 691-1407/? D/soundtrigger: audio_extn_sound_trigger_update_stream_status: uc_info->id 1 of type 0 for Event 2, with Raise=0
2020-11-17 15:10:27.931 691-1407/? D/msm8916_platform: platform_split_snd_device: snd_device(2) num devices(0) new_snd_devices(0)
2020-11-17 15:10:27.931 691-1407/? I/msm8916_platform: platform_get_custom_mtmx_params: no matching param with id 0 ip_ch 2 op_ch 1 uc_id 1 snd_dev 2
2020-11-17 15:10:27.931 691-1407/? D/hardware_info: hw_info_append_hw_type : device_name = speaker
2020-11-17 15:10:27.931 691-1407/? D/audio_hw_primary: disable_snd_device: snd_device(2: speaker)
2020-11-17 15:10:27.931 691-1407/? D/msm8916_platform: platform_split_snd_device: snd_device(2) num devices(0) new_snd_devices(0)
2020-11-17 15:10:27.931 691-1407/? I/soundtrigger: audio_extn_sound_trigger_update_device_status: device 0x2 of type 0 for Event 0, with Raise=0
2020-11-17 15:10:27.931 691-1407/? D/audio_hw_primary: out_standby: exit
2020-11-17 15:10:28.219 1605-6310/system_process W/NotificationService: Toast already killed. pkg=foundation.e.mail callback=android.app.ITransientNotification$Stub$Proxy@85eafad
```
**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/546Can't install update2022-02-10T15:53:56ZRomain HunaultCan't install update## Summary
A user reported on that he can't install the last /e/ stable update on his /e/ refurbished smartphone
## Steps to reproduce
1. Get a Galaxy S9+ with the 20th August update
2. Search for a new update
3. Install the next one ...## Summary
A user reported on that he can't install the last /e/ stable update on his /e/ refurbished smartphone
## Steps to reproduce
1. Get a Galaxy S9+ with the 20th August update
2. Search for a new update
3. Install the next one (from the 08th October)
NB: The user ran a factory reset of the device
## What is the current behavior?
The update isn't installed.
## What is the expected correct behavior?
The update should be installed
## Relevant logs and/or screenshots
![IMG_1903](/uploads/39e98a1292354070915e85d80ddc2c0c/IMG_1903.jpg)
## Possible fixeshttps://gitlab.e.foundation/e/backlog/-/issues/1065mako4 - BlissLauncher crashing when Storage permission granted (blur)2022-01-22T17:26:23ZEmilio Soccimako4 - BlissLauncher crashing when Storage permission granted (blur)- /e/ version:0.7-2020031345025
- Device model: Nexus 4
- When it started to occur: On first boot
- Reproducible with the last /e/ version: yes
- Reproducible with LineageOS: unknown
## Summary
After installing the previous version, th...- /e/ version:0.7-2020031345025
- Device model: Nexus 4
- When it started to occur: On first boot
- Reproducible with the last /e/ version: yes
- Reproducible with LineageOS: unknown
## Summary
After installing the previous version, the desktop didn't load on first boot. I eventually got an error with the Bliss Launcher. I updated to the latest version today and upgraded through the software and it won't load the desktop again.
- [x ] 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 application
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
Turn phone on and desktop fails to load
**What is the current behavior?**
unusable
Desktop should load but does not
**What is the expected correct behavior?**
Icons
## 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>MunichAmit Kumaramitkma@e.emailAmit Kumaramitkma@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/3258encryption not working2022-01-07T17:29:38ZAlexandre Rouxencryption not workingAlexandre RouxAlexandre Rouxhttps://gitlab.e.foundation/e/backlog/-/issues/2391Dialer app crashes always2022-01-07T17:29:30ZGuillermo TorresDialer app crashes always- /e/ version:0.14-q-2021010995048-test-mata
- Device model(s):Essential PH-1
## Summary
Dialer App crashes when I make a phone call
## The problem
**Steps to reproduce**
Make a phone call
**What is the current behavior?**
The app cr...- /e/ version:0.14-q-2021010995048-test-mata
- Device model(s):Essential PH-1
## Summary
Dialer App crashes when I make a phone call
## The problem
**Steps to reproduce**
Make a phone call
**What is the current behavior?**
The app crashes but the phone call remains in the background. so for example, if I use it with car bluetooth, I can hang up from the car. But once on the phone, even without bluetooth, the app crashes but the call works in the background. the other person I am calling to, has to hang up.
Also, the app dialer works until I press the button "call"
**What is the expected correct behavior?**
I should see the Dialer app
## Technical informations
**Relevant logs (`adb logcat`)**
[dialer](/uploads/8d636a758389ddce8080183f6e4e70b7/dialer)[logcat](/uploads/9f795f94b9ef5efc472f3d756d65b0c2/logcat)
```
```
**Relevant screenshots**
<Screenshots of the problem>/e/OS v0.15 (codename U)Mohit MaliMohit Malihttps://gitlab.e.foundation/e/backlog/-/issues/1164S6 edge zeroltexx reboot when locking2021-12-02T13:39:23ZAhmed JanS6 edge zeroltexx reboot when locking- /e/ version:0.8-2020040948906
- Device model:SM-G925F
- When it started to occur:on boot when turning off the screen using power button (locking)
- Reproducible with the last /e/ version:no
- Reproducible with LineageOS:unknown
## Sum...- /e/ version:0.8-2020040948906
- Device model:SM-G925F
- When it started to occur:on boot when turning off the screen using power button (locking)
- Reproducible with the last /e/ version:no
- Reproducible with LineageOS:unknown
## Summary
<Summarize the bug encountered briefly and precisely>
After booting the phone I unlock it
Use it as usual but when trying to unlock it when pressing either home or power button the screen doesn't turn on and if I keep tapping the power button the device reboots with the notification light stuck on white (all colors on)
<Please tick one of the following sentences if relevent>
- [x] 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 application
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
Turn on device
Unlock
Lock (using power button)
Try to turn to unlock
Keep tapping power button when screen doesn't turn on
**What is the current behavior?**
<What actually happens>
Device reboots
**What is the expected correct behavior?**
<What you should see instead>
Device unlocking normally
## 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/3670🐛 FP3/Q no in call audio after update to 0.18-q2021-09-17T16:47:09ZAndré Büsgen🐛 FP3/Q no in call audio after update to 0.18-q- /e/ version: 0.18-20210813129945 (Q)
- Device model(s): Fairphone 3
- Device rooted: no
## Summary
<Summarize the bug encountered briefly and precisely>
After updating my FP3 from 0.17-q to 0.18-q i don't have audio in phone calls an...- /e/ version: 0.18-20210813129945 (Q)
- Device model(s): Fairphone 3
- Device rooted: no
## Summary
<Summarize the bug encountered briefly and precisely>
After updating my FP3 from 0.17-q to 0.18-q i don't have audio in phone calls anymore.
I can't hear the other person and the other person also can't hear me.
## The problem
**Steps to reproduce**
1. Update your FP3 from 0.17-q to 0.18-q
2. Try to make a phone call
3. After picking up neither you or the other person can hear anything
4. This applies even if the other person calls first
Note: Using the recorder app i can Record and play audio. This issue seems to be only present
in calls.
**What is the current behavior?**
I don't have audio on calls.
**What is the expected correct behavior?**
Having audio on phone calls.
## Technical informations
**Relevant logs (`adb logcat`)**
I'm not sure whether this helps. But i found following exception all over the logs.
If you need more information feel free to contact me.
```
08-19 07:53:30.336 1577 3193 I Telecom : CallScreeningServiceHelper: com.android.dialer has no call screening service defined.: (...->CS.crCo->H.CS.crCo->H.CS.crCo.pICR)->CSW.hCCC@E-E-Aos
08-19 07:53:30.337 1577 3193 I Telecom : CallScreeningServiceFilter: Could not bind to call screening service: (...->CS.crCo->H.CS.crCo->H.CS.crCo.pICR)->CSW.hCCC@E-E-Aos
08-19 07:53:30.337 1577 3193 I Telecom : Event: RecordEntry TC@6: SCREENING_COMPLETED, [Allow, logged, notified]: (...->CS.crCo->H.CS.crCo->H.CS.crCo.pICR)->CSW.hCCC@E-E-Aos
08-19 07:53:30.348 1577 3193 E Telecom : CallScreeningServiceFilter: Unbind error: (...->CS.crCo->H.CS.crCo->H.CS.crCo.pICR)->CSW.hCCC@E-E-Aos
08-19 07:53:30.348 1577 3193 E Telecom : java.lang.IllegalArgumentException: Service not registered: com.android.server.telecom.callfiltering.CallScreeningServiceFilter$CallScreeningServiceConnection@1d32899
08-19 07:53:30.348 1577 3193 E Telecom : at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1756)
08-19 07:53:30.348 1577 3193 E Telecom : at android.app.ContextImpl.unbindService(ContextImpl.java:1776)
08-19 07:53:30.348 1577 3193 E Telecom : at android.content.ContextWrapper.unbindService(ContextWrapper.java:741)
08-19 07:53:30.348 1577 3193 E Telecom : at com.android.server.telecom.callfiltering.CallScreeningServiceFilter.finishCallScreening(CallScreeningServiceFilter.java:252)
08-19 07:53:30.348 1577 3193 E Telecom : at com.android.server.telecom.callfiltering.CallScreeningServiceFilter.startCallScreeningFilter(CallScreeningServiceFilter.java:240)
08-19 07:53:30.348 1577 3193 E Telecom : at com.android.server.telecom.callfiltering.CallScreeningServiceController.bindDefaultDialerAndUserChosenService(CallScreeningServiceController.java:189)
08-19 07:53:30.348 1577 3193 E Telecom : at com.android.server.telecom.callfiltering.CallScreeningServiceController.bindCarrierService(CallScreeningServiceController.java:160)
08-19 07:53:30.348 1577 3193 E Telecom : at com.android.server.telecom.callfiltering.CallScreeningServiceController.startFilterLookup(CallScreeningServiceController.java:109)
08-19 07:53:30.348 1577 3193 E Telecom : at com.android.server.telecom.callfiltering.IncomingCallFilter.performFiltering(IncomingCallFilter.java:72)
08-19 07:53:30.348 1577 3193 E Telecom : at com.android.server.telecom.CallsManager.onSuccessfulIncomingCall(CallsManager.java:639)
08-19 07:53:30.348 1577 3193 E Telecom : at com.android.server.telecom.Call.handleCreateConnectionSuccess(Call.java:1767)
08-19 07:53:30.348 1577 3193 E Telecom : at com.android.server.telecom.CreateConnectionProcessor.handleCreateConnectionSuccess(CreateConnectionProcessor.java:465)
08-19 07:53:30.348 1577 3193 E Telecom : at com.android.server.telecom.ConnectionServiceWrapper.handleCreateConnectionComplete(ConnectionServiceWrapper.java:1688)
08-19 07:53:30.348 1577 3193 E Telecom : at com.android.server.telecom.ConnectionServiceWrapper.access$100(ConnectionServiceWrapper.java:67)
08-19 07:53:30.348 1577 3193 E Telecom : at com.android.server.telecom.ConnectionServiceWrapper$Adapter.handleCreateConnectionComplete(ConnectionServiceWrapper.java:81)
08-19 07:53:30.348 1577 3193 E Telecom : at com.android.internal.telecom.IConnectionServiceAdapter$Stub.onTransact(IConnectionServiceAdapter.java:361)
08-19 07:53:30.348 1577 3193 E Telecom : at android.os.Binder.execTransactInternal(Binder.java:1021)
08-19 07:53:30.348 1577 3193 E Telecom : at android.os.Binder.execTransact(Binder.java:994)
08-19 07:53:30.349 1577 3193 I Telecom : Event: RecordEntry TC@6: CONTROLLER_SCREENING_COMPLETED, [Allow, logged, notified]: (...->CS.crCo->H.CS.crCo->H.CS.crCo.pICR)->CSW.hCCC@E-E-Aos
```
**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>/e/OS v0.18Rohit R Sekharmerothh@e.emailRohit R Sekharmerothh@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/3709lg g4 website/documentation issue2021-09-02T05:46:08ZJoao Matoslg g4 website/documentation issue/e/ lg g4 documentation issue (Apologies if this isn't the right place to report this kind of issue and if so pls point me to it). Tx
## Summary
There is a broken link on the lg g4 h815 install doc.
## The problem
**Steps to reprodu.../e/ lg g4 documentation issue (Apologies if this isn't the right place to report this kind of issue and if so pls point me to it). Tx
## Summary
There is a broken link on the lg g4 h815 install doc.
## The problem
**Steps to reproduce**
Go to here:
https://doc.e.foundation/devices/h815/install
```
Click here:
<a href="https://dl.twrp.me/h815">TWRP</a>
```
**What is the current behavior?**
404
**What is the expected correct behaviour?**
the h815 TWRP
## Technical informations
N/A
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
Manually go to https://twrp.me/lg/lgg4h815.html
**Possible fixes**
Fix the doc/site/ etc pointing to the new linkhttps://gitlab.e.foundation/e/backlog/-/issues/3077Several unexpected shutdowns a day on the FP3 with /e/OS but not with Fairpho...2021-07-07T17:54:05ZAnonymeSeveral unexpected shutdowns a day on the FP3 with /e/OS but not with FairphoneOS- /e/ version: 0.14, maybe 0.15
- Device model(s): FP3
## Summary
<Summarize the bug encountered briefly and precisely>
See more in [the thread](https://community.e.foundation/t/30764).
Two years with no problems on FairphoneOS.
The...- /e/ version: 0.14, maybe 0.15
- Device model(s): FP3
## Summary
<Summarize the bug encountered briefly and precisely>
See more in [the thread](https://community.e.foundation/t/30764).
Two years with no problems on FairphoneOS.
The shutdown problem started to occur a few hours after the installation of /e/OS.
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
**What is the current behavior?**
<What actually happens>
At home (so on Wi-Fi) it happens rarely, 1-2 times a day.
When this happens sometimes the phone is completely in standby mode (like during the night), sometimes it happens when I listen to music, sometimes it happens while I am simply actively using it (like writing a message).
While in the car it happens very often, even 3-4 times an hour, with or without Maps.
**What is the expected correct behavior?**
<What you should see instead>
## 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/528No sim card detected + unexpected restarts (Samsung Galaxy I9305)2021-02-02T11:39:09ZMartin DevilleNo sim card detected + unexpected restarts (Samsung Galaxy I9305)I installed the /e/ ROM for the first time on a samsung galaxy SIII gt-i9305 and have two major problems: the phone restarts regularly and inexpectedly, and does not detect the simcard. The sim card works on other phones.
I attach a log...I installed the /e/ ROM for the first time on a samsung galaxy SIII gt-i9305 and have two major problems: the phone restarts regularly and inexpectedly, and does not detect the simcard. The sim card works on other phones.
I attach a log so you cann see if you might help ;)
[logcat.txt](/uploads/8a2754421147e58ae3aab56e38e59690/logcat.txt)https://gitlab.e.foundation/e/backlog/-/issues/1253WhatsApp is muted just for me2021-02-02T08:03:52ZHenriqueWhatsApp is muted just for me- /e/ version: GSI
- Device model: Moto G6 Play
- When it started to occur: Since i installed it (1 week ago)
- Reproducible with the last /e/ version: -
- Reproducible with LineageOS: in Lineage is working fine
## Summary
<Summarize t...- /e/ version: GSI
- Device model: Moto G6 Play
- When it started to occur: Since i installed it (1 week ago)
- Reproducible with the last /e/ version: -
- Reproducible with LineageOS: in Lineage is working fine
## Summary
<Summarize the bug encountered briefly and precisely>
<Please tick one of the following sentences if relevant>
- [ x ] The bug concerns a third party app
## The problem
**Steps to reproduce**
WhatsApp calls or video calls are mute just for me, the other part can hear me, but i can't hear anything back.
I used the previous GSI rom version and this was okay, but i dropped it since it was all buggy, bluetooth wouldn't work and was not mantained, but the last version from April carries this WhatsApp problem.
Speaker and Mic is working fine everywhere else.
## Technical informations
**Relevant logs (`adb logcat`)**
The only log i have is the one i did with the Developer Options function, but i really am not an expert in this, i can't read logs, i just do it because in previous issues i have, people have told me to do that. So i'm attaching it.
[bugreport-lineage_treble_arm_aeN-PQ3A.190801.002-2020-05-05-18-38-42.zip](/uploads/4e42f6e74a911c27a9402c5d26817a50/bugreport-lineage_treble_arm_aeN-PQ3A.190801.002-2020-05-05-18-38-42.zip)https://gitlab.e.foundation/e/backlog/-/issues/598Crash on OnePlus 6T fajita2021-02-02T06:41:56ZColasCrash on OnePlus 6T fajita## Summary
Clean install of current /e/ e-0.7-p-2019112231580-dev-fajita.zip (or previous e-0.7-p-2019112031348-dev-fajita.zip) causes at least 2 major issues on my device: SIM card not detected, spontaneous reboot within a minute when n...## Summary
Clean install of current /e/ e-0.7-p-2019112231580-dev-fajita.zip (or previous e-0.7-p-2019112031348-dev-fajita.zip) causes at least 2 major issues on my device: SIM card not detected, spontaneous reboot within a minute when not plugged with USB.
Older version e-0.7-p-2019110830006-dev-fajita.zip works apparently fine.
## Steps to reproduce
Install current version of /e/ following https://doc.e.foundation/devices/fajita/install
## What is the current behavior?
Current bugs (possibly related):
- SIM card not detected.
- "com.android.phone has stopped" error messages, e.g. when putting into flight mode.
- The phone spontaneously reboots within less than a minute of being disconnected from the USB cable. Once the cable is disconnected, the phone usually does not reach the end of the boot.
## What is the expected correct behavior?
None of these bugs.
## Relevant logs and/or screenshots
Not sure which lines are relevant. Here are a few alarming lines, and these appear many times in the logs:
```
--------- beginning of crash
11-23 06:42:32.099 1998 1998 E AndroidRuntime: FATAL EXCEPTION: main
11-23 06:42:32.099 1998 1998 E AndroidRuntime: Process: com.android.phone, PID: 1998
11-23 06:42:32.099 1998 1998 E AndroidRuntime: java.lang.ArrayIndexOutOfBoundsException: length=1; index=1
11-23 06:42:32.099 1998 1998 E AndroidRuntime: at com.android.internal.telephony.uicc.UiccController.onGetSlotStatusDone(UiccController.java:564)
11-23 06:42:32.099 1998 1998 E AndroidRuntime: at com.android.internal.telephony.uicc.UiccController.handleMessage(UiccController.java:412)
11-23 06:42:32.099 1998 1998 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
11-23 06:42:32.099 1998 1998 E AndroidRuntime: at android.os.Looper.loop(Looper.java:193)
11-23 06:42:32.099 1998 1998 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6718)
11-23 06:42:32.099 1998 1998 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-23 06:42:32.099 1998 1998 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
11-23 06:42:32.099 1998 1998 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
```
Full logs: [fajita.log](/uploads/9538f1c1777716930fb348ea5c4bd429/fajita.log)
## Possible fixes
Don't know. A clean install of older version e-0.7-p-2019110830006-dev-fajita.zip does not exhibit such bugs.https://gitlab.e.foundation/e/backlog/-/issues/1609Samsung S5 klte: e-0.9-p-2020072865179-dev-klte fails to install2021-01-28T06:31:36ZNoraSamsung S5 klte: e-0.9-p-2020072865179-dev-klte fails to install- /e/ version: e-0.9-p-**20200728**65179-dev-klte
- Device model: Samsung S5 LTE International "klte" SM-G900F
- When it started to occur: When updating or installing freshly to e-0.9-p-**20200728**65179-dev-klte
- Reproducible with the ...- /e/ version: e-0.9-p-**20200728**65179-dev-klte
- Device model: Samsung S5 LTE International "klte" SM-G900F
- When it started to occur: When updating or installing freshly to e-0.9-p-**20200728**65179-dev-klte
- Reproducible with the last /e/ version: e-0.9-p-**20200728**65179-dev-klte
- Reproducible with LineageOS: No (lineage-16.0-20200725-microG-klte and lineage-16.0-20200718-microG-klte tested)
## Summary
After flashing e-0.9-p-2020072865179-dev-klte (
- e-screen is shown => ok
- after 2 minutes screen gets dark, no possibility to wake up
- after approx. 30 min device reboots to recovery.
This is in opposite to e-0.9-p-**20200625**60240-dev-klte, where /e/ is ready even at fresh install within less then 2 minutes after reboot.
Installed TWRP: twrp-3.3.1-0-klte.img. Device supplied with power all the time.
<Please tick one of the following sentences if relevant>
- [x] The device is unusable
- [x] 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**
Install e-0.9-p-**20200728**65179-dev-klte by
* adb sideload or
* OTA from running version e-0.9-p-**20200625**60240-dev-klte.
**What is the current behavior?**
e-0.9-p-2020072865179-dev-klte does not install properly
**What is the expected correct behavior?**
e-0.9-p-2020072865179-dev-klte shall install properly
## Technical informations
**Relevant logs (`adb logcat`)**
logcat not available.
Installation in recovery is running through with no other messages than prior version.
This was installed to a S5 phone with pure stock ROM which was reset before. No root, no Magisk,...
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
Use e-0.9-p-2020062560240-dev-klte, do not update to e-0.9-p-2020072865179-dev-klte
**Possible fixes**
No idea.Romain HunaultRomain Hunaulthttps://gitlab.e.foundation/e/backlog/-/issues/1636fastboot: error: Couldn't parse partition size '0x'. FP32020-11-16T16:18:26ZAndré Lamfastboot: error: Couldn't parse partition size '0x'. FP3- /e/ version: IMG-e-0.9-p-2020072865179-dev-FP3.zip
- Device model: FP3
- When it started to occur: -
- Reproducible with the last /e/ version: -
- Reproducible with LineageOS: -
## Summary
Some users experience problems installing /e/...- /e/ version: IMG-e-0.9-p-2020072865179-dev-FP3.zip
- Device model: FP3
- When it started to occur: -
- Reproducible with the last /e/ version: -
- Reproducible with LineageOS: -
## Summary
Some users experience problems installing /e/ on FP3.
- [ ] 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
3rd of August 2 users in the telegram support group encountered this problem while following the FP3 flashing doc:
`fastboot: error: Couldn't parse partition size '0x'. FP3` while issuing this command:
`fastboot flash boot boot.img`
platform-tools_r30.0.4-windows was used i n a first attempt, in a later attempt the fastboot executable included in the stock fairphone OS was used: FP3-REL-2.A.0134-20200703.120010-user-fastbootimage (2).7z (1.06 GB). Both gave the same error.
**reproduce the problem**
Install FP3-REL-2.A.0134-20200703.120010-user-fastbootimage then install /e/. I did not encounter the problem myself, but it's strange 2 users encountered this issue.
**What is the current behavior?**
fastboot can't flash boot.img
**What is the expected correct behavior?**
fastboot can install boot.img
## Technical informations
-
## Solutions
**Workaround**
use command `fastboot flash boot_a boot.img`
**Possible fixes**
use command `fastboot flash boot_a boot.img`
**concern**
Will OTA work with the above workaround?
Why does this happen?QuitoSooraj Ssooorajjj@gmail.comSooraj Ssooorajjj@gmail.comhttps://gitlab.e.foundation/e/backlog/-/issues/1176Visio bug with Signal2020-10-26T22:11:46ZGhost UserVisio bug with Signal- /e/ version: e-0.8-n-2020041549770-dev-hero2lte
- Device model: Samsung Galaxy S7 edge
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: Yes (Samsung Galaxy S6 - LineageOS 16 unofficial)
## Summary
<Summari...- /e/ version: e-0.8-n-2020041549770-dev-hero2lte
- Device model: Samsung Galaxy S7 edge
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: Yes (Samsung Galaxy S6 - LineageOS 16 unofficial)
## Summary
<Summarize the bug encountered briefly and precisely>
With the Signal application, when I make a visio with the front camera, it works well.
But, when I try to switch with the rear camera, the image for the other person is frozen.
<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
- [x] 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>
* Have a Samsung Galaxy S7 edge
* Download e-0.8-n-2020041549770
* Download Signal app
* Video call with Signal to another person who also has Signal
* Switching with the rear camera
**What is the current behavior?**
<What actually happens>
When I switch with the rear camera, I can see my phone's image working, but for the other person, this image is frozen.
**What is the expected correct behavior?**
<What you should see instead>
The other person should see the image from my rear camera.