Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2023-07-03T01:03:29Zhttps://gitlab.e.foundation/e/backlog/-/issues/367Auto Rotate is not working on e-0.6-n-2019052911634 [Treltexx]2023-07-03T01:03:29ZSchizoAuto Rotate is not working on e-0.6-n-2019052911634 [Treltexx]Hi there,
Auto Rotation is working but partly. What does mean partly? When you rebooted your phone you are able to auto rotate your screen. After 15-20 minutes if you try again you won’t rotate your screen because it won’t work anymore....Hi there,
Auto Rotation is working but partly. What does mean partly? When you rebooted your phone you are able to auto rotate your screen. After 15-20 minutes if you try again you won’t rotate your screen because it won’t work anymore. You have just 1 shot.
Source: https://community.e.foundation/t/note-4-n910c-fingerprint-encryption-auto-rotate-set-dns-and-import-contacts-from-sim-is-not-working/4032
Thank you in advance.https://gitlab.e.foundation/e/backlog/-/issues/1529'Add to Homescreen' always adds to Bliss instead of current selected 'Home' app2023-04-21T01:03:24ZPete Fotheringham'Add to Homescreen' always adds to Bliss instead of current selected 'Home' app- /e/ version: 0.9-n-20200602-UNOFFICIAL-SUZURAN (NOUGAT build)
- Device model: suzuran
- When it started to occur: always present
- Reproducible with the last /e/ version: yes, but some apps only in Nougat version
- Reproducible with Li...- /e/ version: 0.9-n-20200602-UNOFFICIAL-SUZURAN (NOUGAT build)
- Device model: suzuran
- When it started to occur: always present
- Reproducible with the last /e/ version: yes, but some apps only in Nougat version
- Reproducible with LineageOS:
## Summary
With a Launcher other than Bliss as the home app, When some apps try to add a shortcut to the Home screen, the shortcut appears in Bliss but not in the currently selected Home app.
Affected apps are Contacts and Shelter (in Nougat), Browser (Nougat and Pie
- [ ] The bug is the source of a data loss or a big waste of time
## The problem
**Steps to reproduce (in PIE builds) **
Install OpenLauncher, and set it as your Home app
Open Browser app, browse to any page
From the three dots menu, select 'Add to Home screen'
**What is the current behavior?**
The shortcut does not appear on the OpenLauncher home screen. If you change your Home screen app to Bliss, then you see that the shortcut is created there.
**What is the expected correct behavior?**
Shortcut should appear on OpenLauncher Home screen
## Technical informations
In Nougat builds, the same problem occurs when you
1. In Contacts app, select a contact, then choose 'Place on Home screen'. (In Pie this option is not present in Contacts app)
2. in Shelter app (in PIE, the following behaves as expected - shortcuts appear in OpenLauncher)
2.1. when Shelter is installed, duplicate shortcuts should appear for 'Contacts', 'Files', and 'microG
Services core'.
2.2 when a new app is installed in Shelter, the shortcut should appear on the homescreen
2.3. when you choose 'Create Unfreeze and/or Launch shortcut
In all the above cases, the created shortcuts are visible in Bliss, but not in OpenLauncherhttps://gitlab.e.foundation/e/backlog/-/issues/101Music cannot play FLAC files2023-03-29T01:03:24ZBenoît LabaereMusic cannot play FLAC files# Music app cannot play FLAC files
## Summary
Music app fails to produce any sound when trying to play a FLAC file.
## Steps to reproduce
Copy or download a FLAC file to the sdcard
Start the Music app
Try to play the selected song.
##...# Music app cannot play FLAC files
## Summary
Music app fails to produce any sound when trying to play a FLAC file.
## Steps to reproduce
Copy or download a FLAC file to the sdcard
Start the Music app
Try to play the selected song.
## What is the current behavior?
The Music App loads the song, the progress indicator is displayed, the icon goes from 'Play' to 'Pause' but no sound is produced.
## What is the expected correct behavior?
I should hear the song.
## Relevant logs and/or screenshots
* https://www.reddit.com/r/LineageOS/comments/6vaqr7/cannot_play_flac_files/
* https://jira.lineageos.org/browse/BUGBASH-263
## Possible fixes
This can only be fixed upstream in LineageOS ?https://gitlab.e.foundation/e/backlog/-/issues/2271Nougat PWA icons looks shifted2023-03-09T02:03:21ZAmit Kumaramitkma@e.emailNougat PWA icons looks shifted- /e/ version:
- Device model(s):
## Summary
<Summarize the bug encountered briefly and precisely>
PWA icons on nougat looks shifted instead of being centered.
## The problem
**Steps to reproduce**
<How one can reproduce the issue>...- /e/ version:
- Device model(s):
## Summary
<Summarize the bug encountered briefly and precisely>
PWA icons on nougat looks shifted instead of being centered.
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
Add a PWA (Quiet Weather for example) from Apps and it will be shown a bit shifted in Launcher.
**What is the current behavior?**
<What actually happens>
PWA shortcut icon is shifted.
**What is the expected correct behavior?**
<What you should see instead>
Icon should be centered.
## 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/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/500S7 Bluetooth link and GPS Tomtom unstable and unusable2022-10-06T01:03:57Zc.perriS7 Bluetooth link and GPS Tomtom unstable and unusableBonjour
S7 Bluetooth link and GPS Tomtom unstable and unusable
the Bluetooth connection between a Samsung S7 (/e/OS V 0.7-2019091323560) and a TomTom Go Basic GPS. The association between the two devices is going well but the connection...Bonjour
S7 Bluetooth link and GPS Tomtom unstable and unusable
the Bluetooth connection between a Samsung S7 (/e/OS V 0.7-2019091323560) and a TomTom Go Basic GPS. The association between the two devices is going well but the connection cuts off every second, use impossible. Problem existing with previous /e/OS versions.
[logcat-1.txt](/uploads/90a8760e2766c0a332ec160accf8610c/logcat-1.txt)
Thank youhttps://gitlab.e.foundation/e/backlog/-/issues/4457herolte nougat : Tried to setup /e/ account on the device and the device is s...2022-10-03T13:13:57ZKumar Abhishekherolte nougat : Tried to setup /e/ account on the device and the device is stuck on that page- /e/ version: e-0.20-n-20211221153032-dev-herolte
- Device model(s): herolte
- Device rooted: no
## Summary
For S7(herolte), after enrolling my fingerprint and the security Pin, I tried to setup /e/ account on the device and my device...- /e/ version: e-0.20-n-20211221153032-dev-herolte
- Device model(s): herolte
- Device rooted: no
## Summary
For S7(herolte), after enrolling my fingerprint and the security Pin, I tried to setup /e/ account on the device and my device is stuck on that page. Can neither move forward, nor backward.
## The problem
**Steps to reproduce**
1. Perform a fresh installation of e-0.20-n-20211221153032-dev-herolte.zip on herolte.
2. Perform the initial setup and try to add /e/ account as well.
**What is the current behavior?**
Tried to setup /e/ account on the device and device is stuck on that page. Can neither move forward, nor backward.
**What is the expected correct behavior?**
Account should have been successfully added.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
12-22 17:16:22.464 4128 4128 I Choreographer: Skipped 38 frames! The application may be doing too much work on its main thread.
12-22 17:16:22.480 4825 4825 W ResourceType: Failure getting entry for 0x3f061006 (t=5 e=4102) (error -75)
12-22 17:16:22.480 4825 4825 W ResourceType: Failure getting entry for 0x3f061001 (t=5 e=4097) (error -75)
12-22 17:16:22.480 4825 4825 D AndroidRuntime: Shutting down VM
12-22 17:16:22.481 4825 4825 E davx5 : [foundation.e.accountmanager.App] Unhandled exception!
12-22 17:16:22.481 4825 4825 E davx5 : EXCEPTION java.lang.RuntimeException: Unable to start activity ComponentInfo{foundation.e.accountmanager/foundation.e.accountmanager.ui.setup.LoginActivity}: java.lang.UnsupportedOperationException: Can't convert value at index 1 to color: type=0x1
12-22 17:16:22.481 4825 4825 E davx5 : at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2684)
12-22 17:16:22.481 4825 4825 E davx5 : at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2751)
12-22 17:16:22.481 4825 4825 E davx5 : at android.app.ActivityThread.-wrap12(ActivityThread.java)
12-22 17:16:22.481 4825 4825 E davx5 : at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1496)
12-22 17:16:22.481 4825 4825 E davx5 : at android.os.Handler.dispatchMessage(Handler.java:102)
12-22 17:16:22.481 4825 4825 E davx5 : at android.os.Looper.loop(Looper.java:154)
12-22 17:16:22.481 4825 4825 E davx5 : at android.app.ActivityThread.main(ActivityThread.java:6186)
12-22 17:16:22.481 4825 4825 E davx5 : at java.lang.reflect.Method.invoke(Native Method)
12-22 17:16:22.481 4825 4825 E davx5 : at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
12-22 17:16:22.481 4825 4825 E davx5 : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
12-22 17:16:22.481 4825 4825 E davx5 : Caused by: java.lang.UnsupportedOperationException: Can't convert value at index 1 to color: type=0x1
12-22 17:16:22.481 4825 4825 E davx5 : at android.content.res.TypedArray.getColor(TypedArray.java:463)
12-22 17:16:22.481 4825 4825 E davx5 : at android.app.Activity.onApplyThemeResource(Activity.java:4035)
12-22 17:16:22.481 4825 4825 E davx5 : at android.view.ContextThemeWrapper.initializeTheme(ContextThemeWrapper.java:198)
12-22 17:16:22.481 4825 4825 E davx5 : at android.view.ContextThemeWrapper.setTheme(ContextThemeWrapper.java:140)
12-22 17:16:22.481 4825 4825 E davx5 : at android.app.Activity.setTheme(Activity.java:4013)
12-22 17:16:22.481 4825 4825 E davx5 : at androidx.appcompat.app.AppCompatActivity.setTheme(AppCompatActivity.java:144)
12-22 17:16:22.481 4825 4825 E davx5 : at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2630)
12-22 17:16:22.481 4825 4825 E davx5 : ... 9 more
12-22 17:16:22.489 3347 4086 I ActivityManager: START u0 {flg=0x10000000 cmp=foundation.e.accountmanager/.ui.DebugInfoActivity (has extras)} from uid 10046 on display 0
12-22 17:16:22.490 3347 3395 W ResourceType: Failure getting entry for 0x3f061006 (t=5 e=4102) (error -75)
12-22 17:16:22.490 3347 3395 W ResourceType: Failure getting entry for 0x3f061002 (t=5 e=4098) (error -75)
12-22 17:16:22.490 3347 3395 W ResourceType: Failure getting entry for 0x3f061002 (t=5 e=4098) (error -75)
12-22 17:16:22.490 3347 3395 W ResourceType: Failure getting entry for 0x3f061006 (t=5 e=4102) (error -75)
12-22 17:16:22.491 3347 3395 W WindowManager: Token{fa1ec97 ActivityRecord{6a79b16 u0 foundation.e.accountmanager/.ui.DebugInfoActivity t8}} failed creating starting window
12-22 17:16:22.491 3347 3395 W WindowManager: java.lang.UnsupportedOperationException: Can't convert value at index 35 to color: type=0x1
12-22 17:16:22.491 3347 3395 W WindowManager: at android.content.res.TypedArray.getColor(TypedArray.java:463)
12-22 17:16:22.491 3347 3395 W WindowManager: at com.android.internal.policy.PhoneWindow.generateLayout(PhoneWindow.java:2407)
12-22 17:16:22.491 3347 3395 W WindowManager: at com.android.internal.policy.PhoneWindow.installDecor(PhoneWindow.java:2628)
12-22 17:16:22.491 3347 3395 W WindowManager: at com.android.internal.policy.PhoneWindow.getDecorView(PhoneWindow.java:2047)
12-22 17:16:22.491 3347 3395 W WindowManager: at com.android.server.policy.PhoneWindowManager.addStartingWindow(PhoneWindowManager.java:3306)
12-22 17:16:22.491 3347 3395 W WindowManager: at com.android.server.wm.WindowManagerService$H.handleMessage(WindowManagerService.java:8457)
12-22 17:16:22.491 3347 3395 W WindowManager: at android.os.Handler.dispatchMessage(Handler.java:102)
12-22 17:16:22.491 3347 3395 W WindowManager: at android.os.Looper.loop(Looper.java:154)
12-22 17:16:22.491 3347 3395 W WindowManager: at android.os.HandlerThread.run(HandlerThread.java:61)
12-22 17:16:22.491 3347 3395 W WindowManager: at com.android.server.ServiceThread.run(ServiceThread.java:46)
12-22 17:16:22.492 4825 4825 I art : System.exit called, status: 1
12-22 17:16:22.492 4825 4825 I AndroidRuntime: VM exiting with result code 1, cleanup skipped.
12-22 17:16:22.522 3347 3532 I ActivityManager: Process foundation.e.accountmanager (pid 4825) has died
12-22 17:16:22.522 3347 3532 D ActivityManager: cleanUpApplicationRecord -- 4825
12-22 17:16:22.522 3031 3031 I Zygote : Process 4825 exited cleanly (1)
12-22 17:16:22.523 3347 3532 W ActivityManager: Scheduling restart of crashed service foundation.e.accountmanager/.syncadapter.EeloAccountAuthenticatorService in 1000ms
12-22 17:16:22.533 3347 3532 I ActivityManager: Start proc 4850:foundation.e.accountmanager/u0a46 for activity foundation.e.accountmanager/.ui.DebugInfoActivity
12-22 17:16:22.549 4850 4850 W System : ClassLoader referenced unknown path: /system/app/AccountManager/lib/arm64[herolte-dev-account-add.txt](/uploads/7d15996d8002e1821c178bdbb30c4b36/herolte-dev-account-add.txt)
```
**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/1629System UI stops when using search assistant2022-09-29T01:03:23ZPorrumentzioSystem UI stops when using search assistant- /e/ version: 0.9-2020062660259 (mido)
- Device model: Xiaomi Redmi Note 4 X
- When it started to occur: N/A
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: N/A
## Summary
When using **search assistant** b...- /e/ version: 0.9-2020062660259 (mido)
- Device model: Xiaomi Redmi Note 4 X
- When it started to occur: N/A
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: N/A
## Summary
When using **search assistant** button-option (it is default on long pressing Home button), System **UI stops**.
<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 third-party application
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
Select "Search assistant" on some Button actions (`Settings > Buttons`) and execute it. Happens with *any* language locales and assigned to any button-action.
**What is the current behavior?**
The System UI stops with the message
> System UI has stoped
> X Close app
> X Mute until device restarts
**What is the expected correct behavior?**
That action "Search assistant" should be executed.
## Technical informations
**Relevant screenshots**
![eOS-home-button-search-error](/uploads/5a1d898f9d2401e3a9df23774aa63b74/eOS-home-button-search-error.gif)
## Solutions
**Workaround**
Tap "Close app" and unlock the phone again.https://gitlab.e.foundation/e/backlog/-/issues/1659Calendar is default configured to open www.google.com links2022-09-29T01:03:21ZPorrumentzioCalendar is default configured to open www.google.com links- /e/ version: Nougat 0.9 & 0.10
- Device model: Xiaomi Redmi Note 4 X
- When it started to occur: always
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: N/A
## Summary
Calendar is configured to open www.go...- /e/ version: Nougat 0.9 & 0.10
- Device model: Xiaomi Redmi Note 4 X
- When it started to occur: always
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: N/A
## Summary
Calendar is configured to open www.google.com links on `Applications > Settings (the wheel) > Default > Links that will be opened`
<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 third-party application
- [x] The bug concerns security
- [x] The bug concerns privacy
## The problem
**Steps to reproduce**
Go to `Applications > Settings (the wheel) > Default > Links that will be opened` and see that Calendar is configured to open google.com links.
**What is the current behavior?**
Calendar is configured to open google.com links. But opening that link, Browser will open, not Calendar (as expected)
**What is the expected correct behavior?**
Avoid Google as possible. It is not necessary that a calendar open a website. And in fact it does not open it, or at least Browser has priority.
Maybe the problem is only of GUI, not of real behavior.
## Technical informations
**Relevant screenshots**
![IMG_20200808_101629_155](/uploads/c758ca48f532576f616c01620da7de2f/IMG_20200808_101629_155.jpg)https://gitlab.e.foundation/e/backlog/-/issues/1750"Can not uninstall this app": duplicated, strange app-icons2022-09-28T01:03:50ZPorrumentzio"Can not uninstall this app": duplicated, strange app-icons- /e/ version: 0.10-n
- Device model: Xiaomi Redmi Note 4 X
- Reproducible with the last /e/ version: yes
## Summary
Twice on my usetime of /e/OS, first for TWRP installed via Aurora Store and secondly with [Element 1.0.5 via F-Droid](...- /e/ version: 0.10-n
- Device model: Xiaomi Redmi Note 4 X
- Reproducible with the last /e/ version: yes
## Summary
Twice on my usetime of /e/OS, first for TWRP installed via Aurora Store and secondly with [Element 1.0.5 via F-Droid](https://f-droid.org/packages/im.vector.app), happened that an app has a duplicated icon which has not the expected icon, but an default-android icon (image below) and it's not possible to remove that second icon: this message appears: `Can not uninstall this app`
<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
- [x] The bug concerns a third-party application
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
Maybe, download Element 1.0.5 from F-Droid, but not sure.
**What is the current behavior?**
A duplicated, strange icon is created with the same name as the app. But that duplicate can't be uninstalled.
**What is the expected correct behavior?**
1- That duplicated icon should not appear.
2- If appeared, it should be able to remove it.
## Technical informations
**Relevant screenshots**
![Screenshot_20200823-235244](/uploads/86c4817b4bc1bfa9eb5fe778db0a7934/Screenshot_20200823-235244.png)
## Solutions
**Workaround**
* Using Bliss Launcher, move that icon to another area.
* Clear data and cache of Bliss Launcher [[solved by *omniDHTM* on Forum](https://community.e.foundation/t/app-shortcut-unable-to-delete-it-crashes-bliss-launcher-at-attempt/19990/11)], although this removes all the configuration.
* Use another launcher.
**Possible fixes**
> Clear data and cache of Bliss Launcher
The problem could be about some data stored on Bliss Launcher.
<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/2743Stylus is not working N71002022-09-15T01:03:52ZVERA ALLISTERStylus is not working N7100- /e/ version:
- Device model(s):
## Summary
<Summarize the bug encountered briefly and precisely>
## The problem
**I installed e-0.14-n-2021013099019-dev-n7100 to Samsung Galaxy Note 2 (7100) after watching video on YouTube, link ht...- /e/ version:
- Device model(s):
## Summary
<Summarize the bug encountered briefly and precisely>
## The problem
**I installed e-0.14-n-2021013099019-dev-n7100 to Samsung Galaxy Note 2 (7100) after watching video on YouTube, link https://www.youtube.com/watch?v=A61P3vP6dog. It shows that S-Pen is working as regular Stylus (that would be fine); mine is not working at all (it was working with Official ROM and diagnostic told S-Pen is good) **
<How one can reproduce the issue>
**S-Pen was working with ROM e-0.9-n-2020051554230-dev-n7100.zip on video from YouTube but it's not working with e-0.14-n-2021013099019-dev-n7100**
<What actually happens>
**I contacted @Manoj and Shenol, they believe there is a bug related to Stylus on e-0.14-n-2021013099019-dev-n7100. Would you please fix it?**
<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/3006Build in failure for condor2022-09-09T01:03:38ZRomain HunaultBuild in failure for condorhttps://gitlab.e.foundation/e/priv/os/build/-/jobs/161450https://gitlab.e.foundation/e/priv/os/build/-/jobs/161450https://gitlab.e.foundation/e/backlog/-/issues/3007Build in failure for falcon2022-09-09T01:03:37ZRomain HunaultBuild in failure for falconhttps://gitlab.e.foundation/e/priv/os/build/-/jobs/161453https://gitlab.e.foundation/e/priv/os/build/-/jobs/161453https://gitlab.e.foundation/e/backlog/-/issues/3008Build in failure for pinebook2022-09-09T01:03:37ZRomain HunaultBuild in failure for pinebookhttps://gitlab.e.foundation/e/priv/os/build/-/jobs/161483https://gitlab.e.foundation/e/priv/os/build/-/jobs/161483https://gitlab.e.foundation/e/backlog/-/issues/3009Build in failure for serranoltexx2022-09-08T01:03:41ZRomain HunaultBuild in failure for serranoltexxhttps://gitlab.e.foundation/e/priv/os/build/-/jobs/161488https://gitlab.e.foundation/e/priv/os/build/-/jobs/161488https://gitlab.e.foundation/e/backlog/-/issues/1440Maps asks for permissions on nougat2022-06-22T10:22:02ZRomain HunaultMaps asks for permissions on nougat* /e/ version: 0.9-n-2020062259639-test
* Device model: kiwi
* When it started to occur:
* Reproducible with the last /e/ version: yes
* Reproducible with LineageOS: -
## Summary
<Summarize the bug encountered briefly and precisely>
F...* /e/ version: 0.9-n-2020062259639-test
* Device model: kiwi
* When it started to occur:
* Reproducible with the last /e/ version: yes
* Reproducible with LineageOS: -
## Summary
<Summarize the bug encountered briefly and precisely>
Following https://gitlab.e.foundation/e/backlog/-/issues/1050, Maps still asks for permissions on nougat
<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>
1. Install the last test build
2. Open Maps app
**What is the current behavior?**
<What actually happens>
The location permission isn't given by default. User have to click on the "Find me" button to get the app asking for it.
**What is the expected correct behavior?**
<What you should see instead>
Our default apps don't ask for default permissions.
## 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/1439Contact asks for permissions on nougat2022-06-22T10:21:51ZRomain HunaultContact asks for permissions on nougat* /e/ version: 0.9-n-2020062259639-test
* Device model: kiwi
* When it started to occur:
* Reproducible with the last /e/ version: yes
* Reproducible with LineageOS: -
## Summary
<Summarize the bug encountered briefly and precisely>
F...* /e/ version: 0.9-n-2020062259639-test
* Device model: kiwi
* When it started to occur:
* Reproducible with the last /e/ version: yes
* Reproducible with LineageOS: -
## Summary
<Summarize the bug encountered briefly and precisely>
Following https://gitlab.e.foundation/e/backlog/-/issues/1049, Contacts app still asks for permissions on nougat
<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>
1. Install the last test build
2. Open Contacts app
**What is the current behavior?**
<What actually happens>
At the first start of the Contacts application, it asks for permissions.
**What is the expected correct behavior?**
<What you should see instead>
Our default apps don't ask for default permissions.
## 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/4556GmsCore: Remove v1-nougat branch2022-06-22T10:21:22ZJonathan KleeGmsCore: Remove v1-nougat branch## Summary
Remove GmsCore v1-nougat branch we created to workaround the e-ui.sdk on nougat
## Description
We had to create a new branch on nougat but it won't be maintainable in the time.
We should try to use Build.VERSION_CODES.N wi...## Summary
Remove GmsCore v1-nougat branch we created to workaround the e-ui.sdk on nougat
## Description
We had to create a new branch on nougat but it won't be maintainable in the time.
We should try to use Build.VERSION_CODES.N within the code and have a unique branch.Jonathan KleeJonathan Kleehttps://gitlab.e.foundation/e/backlog/-/issues/2583Launcher display default Android Icons2022-06-10T03:56:22ZManoj NairLauncher display default Android Icons- /e/ version: nougat - e-0.14-n-2021013099019
- Device model(s): Galaxy Note 2 GT-N7105
## Summary
Launcher displays default Android App Icons.[image](/uploads/f7d6395dff2078ba68f65cca28042b94/image)
## The problem
Install third pa...- /e/ version: nougat - e-0.14-n-2021013099019
- Device model(s): Galaxy Note 2 GT-N7105
## Summary
Launcher displays default Android App Icons.[image](/uploads/f7d6395dff2078ba68f65cca28042b94/image)
## The problem
Install third party Apps
<How one can reproduce the issue>
App icons showed is the Default Android App icon instead of the actual icon for the particular application
<What actually happens>
The correct application icon should be displayed
**Pl note** This issue is reported on the nougat build of /e/
<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/1713Automatic Brightness setting creates bug rotation2022-03-07T16:40:22ZmarineAutomatic Brightness setting creates bug rotation* /e/ version: 0-9.2020051153544
* Device model: galaxy s7 with herolte
* When it started to occur: several month ago[bugreport-NJH47F-2020-06-19-21-34-31.zip](/uploads/930436b96d611216e1884b1ab795ca2a/bugreport-NJH47F-2020-06-19-21-34-3...* /e/ version: 0-9.2020051153544
* Device model: galaxy s7 with herolte
* When it started to occur: several month ago[bugreport-NJH47F-2020-06-19-21-34-31.zip](/uploads/930436b96d611216e1884b1ab795ca2a/bugreport-NJH47F-2020-06-19-21-34-31.zip)
If I disactivate the automatic brightness setting (using the Ambient light sensor), the screen of my phone get stuck vertically almost every time I get out sleep mode.
It makes the phone pratically unusable ...