Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2022-06-22T10:21:22Zhttps://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/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/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/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/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/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/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/2748Fix Nougat build failure for v0.152021-04-19T15:31:17ZRomain HunaultFix Nougat build failure for v0.15We faced multiple build failure for v0.15 ([pipeline 105896](https://gitlab.e.foundation/e/priv/os/build/-/pipelines/105896))
- ~condor https://gitlab.e.foundation/e/priv/os/build/-/jobs/154250
- ~falcon https://gitlab.e.foundation/...We faced multiple build failure for v0.15 ([pipeline 105896](https://gitlab.e.foundation/e/priv/os/build/-/pipelines/105896))
- ~condor https://gitlab.e.foundation/e/priv/os/build/-/jobs/154250
- ~falcon https://gitlab.e.foundation/e/priv/os/build/-/jobs/154253
- ~pinebook https://gitlab.e.foundation/e/priv/os/build/-/jobs/154283
- ~serranoltexx https://gitlab.e.foundation/e/priv/os/build/-/jobs/154288Alexandre RouxSooraj Ssooorajjj@gmail.comAlexandre Rouxhttps://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/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/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/2243Web shortcut still a little bit blurred2022-02-21T15:34:57ZRomain HunaultWeb shortcut still a little bit blurred- /e/ version: v0.13 ~nougat
- Device model(s):
## Summary
<Summarize the bug encountered briefly and precisely>
Following the work done on https://gitlab.e.foundation/e/backlog/-/issues/1438, it looks much better on ~oreo ~pie ~q, ...- /e/ version: v0.13 ~nougat
- Device model(s):
## Summary
<Summarize the bug encountered briefly and precisely>
Following the work done on https://gitlab.e.foundation/e/backlog/-/issues/1438, it looks much better on ~oreo ~pie ~q, but still blurred on ~nougat
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. Open Browser, navigate to a website
1. Press `3 dots` button, and choose `Add to Home screen`
1. Come back to Launcher
**What is the current behavior?**
<What actually happens>
The new icons is blurred
**What is the expected correct behavior?**
<What you should see instead>
New icon not blurred
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
~nougat (Samsung Galaxy S7)
![screenshot_20201211_11_06_04](/uploads/052ee5e3446668b91dd07f602cee8659/screenshot_20201211_11_06_04.png)
To compare with other Android version:
~oreo (Samsung Galaxy S9)
![screenshot_20201211_11_06_30](/uploads/7ecfcb07fc5b65ae7ca1b4116bcd1d12/screenshot_20201211_11_06_30.png)
~pie (Samsung Galaxy S8)
![screenshot_20201211_11_06_37](/uploads/35172d86a15e7268a1c6a0d4e084305d/screenshot_20201211_11_06_37.png)
~q (Fairphone 3)
![screenshot_20201211_11_06_47](/uploads/30f11a670315a6bdf2ba6a9a4f3a2d33/screenshot_20201211_11_06_47.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/2239Can't uninstall PWA2020-12-14T23:06:16ZRomain HunaultCan't uninstall PWA- /e/ version: 0.13 ~nougat
- Device model(s):
## Summary
<Summarize the bug encountered briefly and precisely>
PWA can't be removed from Launcher because of a BlissLauncher crash
## The problem
**Steps to reproduce**
<How one can...- /e/ version: 0.13 ~nougat
- Device model(s):
## Summary
<Summarize the bug encountered briefly and precisely>
PWA can't be removed from Launcher because of a BlissLauncher crash
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. Open Apps
1. In Apps settings, choose to display only PWA
1. Install PWA
1. On it displays `Shortcut added`, come back on Launcher
1. Long press on the PWA icon
1. Uninstall the PWA
**What is the current behavior?**
<What actually happens>
A `Blisslaucher crashed` popup appears. The PWA is not removed.
**What is the expected correct behavior?**
<What you should see instead>
Being able to remove PWA from Launcher
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
2020-12-10 17:36:25.746 10610-10610/foundation.e.blisslauncher E/AndroidRuntime: FATAL EXCEPTION: main
Process: foundation.e.blisslauncher, PID: 10610
java.lang.NullPointerException: package name is null
at android.content.ComponentName.<init>(ComponentName.java:99)
at foundation.e.blisslauncher.features.shortcuts.ShortcutKey.<init>(ShortcutKey.java:18)
at foundation.e.blisslauncher.features.shortcuts.ShortcutKey.fromItem(ShortcutKey.java:31)
at foundation.e.blisslauncher.features.launcher.LauncherActivity.lambda$null$25$LauncherActivity(LauncherActivity.java:1987)
at foundation.e.blisslauncher.features.launcher.-$$Lambda$LauncherActivity$R4vga1YFntIX69l9K4rT47cLV_M.onClick(lambda)
at com.android.internal.app.AlertController$ButtonHandler.handleMessage(AlertController.java:166)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6186)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
```
**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>Amit Kumaramitkma@e.emailAmit Kumaramitkma@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/2238PWA icon missing2020-12-15T18:47:54ZRomain HunaultPWA icon missing- /e/ version: 0.13 ~nougat
- Device model(s):
## Summary
<Summarize the bug encountered briefly and precisely>
PWA icon missing on Launcher
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. Open Apps
1. ...- /e/ version: 0.13 ~nougat
- Device model(s):
## Summary
<Summarize the bug encountered briefly and precisely>
PWA icon missing on Launcher
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. Open Apps
1. In Apps settings, choose to display only PWA
1. Install PWA
1. On it displays `Shortcut added`, come back on Launcher
**What is the current behavior?**
<What actually happens>
The PWA icon is the default Android one
**What is the expected correct behavior?**
<What you should see instead>
The PWA icon should be the PWA icon
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
2020-12-10 17:33:34.982 10343-10355/foundation.e.pwaplayer D/PwaProvider: insert() called with: uri = content://foundation.e.pwaplayer.provider/pwa, values = ICON=[B@93e6400 TITLE=Quiet Weather URL=https://slimekat.github.io/quiet-weather/?force=pwa&source=mlpwa SHORTCUT_ID=https://slimekat.github.io/quiet-weather/?force=pwa&source=mlpwa
2020-12-10 17:34:42.378 10343-10355/foundation.e.pwaplayer D/PwaProvider: insert() called with: uri = content://foundation.e.pwaplayer.provider/pwa, values = ICON=[B@3ca608a TITLE=Waqt URL=https://waqt-web.netlify.com/?force=pwa&source=mlpwa SHORTCUT_ID=https://waqt-web.netlify.com/?force=pwa&source=mlpwa
2020-12-10 17:35:36.898 10343-10355/foundation.e.pwaplayer D/PwaProvider: delete() called with: uri = content://foundation.e.pwaplayer.provider/pwa, selection = null, selectionArgs = [Ljava.lang.String;@b44b318
2020-12-10 17:35:36.903 10343-10355/foundation.e.pwaplayer D/PwaProvider: delete: foundation.e.browser/#Intent;action=com.google.android.apps.chrome.webapps.WebappManager.ACTION_START_WEBAPP;package=foundation.e.browser;B.org.chromium.chrome.browser.is_icon_generated=false;S.org.chromium.chrome.browser.webapp_scope=https%3A%2F%2Fwww.lequipe.fr%2F;l.org.chromium.chrome.browser.theme_color=-460552;S.org.chromium.chrome.browser.webapp_short_name=L'%C3%89quipe;i.org.chromium.chrome.browser.webapp_source=6;i.org.chromium.chrome.browser.webapp_shortcut_version=3;S.org.chromium.chrome.browser.webapp_id=5a843a36-4fba-4886-8c29-6e55a5989076;i.org.chromium.chrome.browser.webapp_display_mode=3;l.org.chromium.chrome.browser.background_color=-1;B.org.chromium.chrome.browser.webapp_icon_adaptive=false;i.org.chromium.content_public.common.orientation=7;S.org.chromium.chrome.browser.webapp_icon=iVBORw0KGgoAAAANSUhEUgAAAKgAAACoCAYAAAB0S6W0AAAABHNCSVQICAgIfAhkiAAAHBhJREFU%0AeJztnXuQXNV95z%2Fn3L63e3p6Rk%2FEU1giYIyJMX6AjXcxiFgyGD3MK8KmEiebrcVJVZLdym7tOn9k%0Ay3Gq4j9cm1Tteqs2%2F%2BxWHkbC%2BCGEBBghwCCMwZExJhgMwsZ2eAiwHtPv7nt%2B%2B8e59%2Fad0Qz0jOZ2%0A32nOt0qaVqvnnnP7fs%2Fv%2FN5HNZtNwcEhp9DDnoCDw1vBEdQh13AEdcg1HEEdcg1HUIdcwxHUIddw%0ABHXINRxBHXINR1CHXMMR1CHXcAR1yDUcQR1yDUdQh1zDEdQh13AEdcg1HEEdcg1HUIdcwxHUIddw%0ABHXINRxBHXINR1CHXMMR1CHXcAR1yDUcQR1yDUdQh1zDEdQh13AEdcg1HEEdcg1H0KwhGfVmy%2Bq6%0AOUNh2BMYZYgISilExBJKBNQiXFjp5LpKLcYF8wtH0AyhFCCCAlRpbHHICUi3i3S7I09OcATNDDJj%0AC2499QTm%2BFGU51lBugBuCUAY4q87l8KpZyJhiNKjraU5gmaAeOs1JkQHRdqHnuPV399M5%2FBhdMGL%0A%2Fn8%2BFwSUQkJBl4uc9g%2F3UjhrPdKtL5ZQzi0cQTOCiIARlOdRu%2BebtF86jK4oK%2FXUPG0cAeUpTF0o%0AX3kFpYs%2FgrSbbot3WBis9DSoICA88ibVvV9HFUClduO%2BqSWAjoRoAJVtn0EHAWG9BtpzEtRh%2FrBW%0Au0H7PlMH7qf99I9RRRAjqAV4h0QpTEMoXXg%2BYx%2FfhOl2UUovmtGVZ5w0QWcaA4potZ%2Fshd9u3NRY%0AdlyFMLfbZVDzlPi62kM6HWq7d2IagjepITS9wfu5kOp9XIUw%2FsnrKaw5DVOvo7SOyL44%2FtATv8%2FU%0A6yGqEidNUAVWgRcBY5KbGoQbWaKxldaWnHM8eYlcPSiFGAMi2c7TGFRpjNYzT1L%2F7j50CcSYaA59%0AXkMBBtBgOoK3usL4NddDtwvGZDJ3ica10lmhFupuWEScFEElvgERlFdAlXqXG5QENYA0Gyj07BI0%0AdpaDJU5QRHk6UwlKdN3a3XcQvn4cXVFgZH5iO%2F6cUkhTGL%2FpOkoXfRgAXakseggwLUFNu20XQfxs%0Al6IEtZ4PK5FUoUDnpUPU7v46orSVZJnfk0LabfxzzmP86hsQMbPPM%2FqSRQQdBLR%2B%2FM%2FUH7oHVfB5%0Ae7akHluf0kSMWIkedpj61j%2BCn5Lg810RsaM%2FAFOvcvT%2FfAXTaiy%2BcZTcZgiFEpVtN1NYczrS6STP%0AeVhQCz7IK9omxRi8cpk3%2FvLPePOv%2Fwe6wmD2dwWmBqd86S9Y8Wdf7Olls0hQI9H27xc4%2FEfbOfb3%0A30RPZDRPAYnWpyoBHlZXXMgzjuYnCqQFdDLU7zWYKoz9mws54%2FYH0ZVlSGijVUtTgirr09NBQOfl%0AX1K7bxd6uYcuq0RHyg4K6UBx%2FWlM3Pg5CM3cxhGgRFClEq1%2FOUj9wH68UzyUT2%2FbzQrGTN875%2B2c%0Aty%2BVgCopGMtwskpBQZi85VYKK1djajWU5w3d17oggkpsZIigCgXqD95D%2B6eH7JfYlWzNeAE863Yp%0Af2ILhbPXI40GojV6xpcpKWNIa0Vt7zfovnoUbzKaJxnOMzXdeRlHMVKfjxdZJhlMkcSXNvhnn0H5%0AtzbbWL9W6BwkpCxI11bKOnWUV8A06lR33QaRTk1WwlOiaytr1RbWVJi86ffsFxzN6QRXUmSJat%2Bn%0A%2B9oricNczGDIaeeQj2vMivhr0AraML7pOvy1662RpPTQyQkLIKhEBocYgyoGNA8%2BRvOJR1Cl2Kon%0AG9M4uq5ojdShvHErxYs%2BjLRaCRHTX6YkczUo36f%2BwN10fvoCqpTSCd8ZKZWzI63fdgRvZZnxLdut%0A4Im8IcMmJyyAoHbSYn1lIlR37yQ82oHIdZPJg48NaQV0DN6qMZbdcitojUhof874MlW0kKyUb1Dd%0AfRumTS%2F7ZxDRhDwjWvBKa0wTSpddTumiSzDtNhI92zxgQRLUuj6KdF56kdr9e1BFbBwnCaMs4gyj%0Aa4rYrUgaULn2BkqX%2FFuk2bQul9iN05skohRKbDy8%2BcPv03jsEVTZeh1gkee41JD6TsUYG%2BPf%2Bhl0%0AqZTkmeZBesI8CSqJawmUp6nt20335%2F%2BKLqrs9LrYktUgbUGfOsHk7%2F0xECnwqBMEtkT6aCxVq7t3%0AEB5toj21cJfPKCHakZRWSBOK559P%2BcqrMZ1O4qrLh%2FycJ0ETXc8vEE4dp7r7NqsXkgQ9FhfxSreD%0AY1owuf3fUXr%2FJUirYb9MTtQ9lQjKGJRvpXx9352oIBWPz8u3PyxED0wUSBcq196Et%2FpU6HSSxZ2X%0ANdw3QdNGhw4Cmo89ROtHB60zOvInLrraklrppikUzzubZb%2F%2FpxCGPct99l%2BxWWoFj9p3vk3n56%2Bg%0AiqkPvJMRL3oF0hIKZ6xg%2FFM3JHkUedreYR4ETYwO7SFhyNTunUg1TOLaZJFXEH%2BRYi%2B87A%2F%2FG8HZ%0A6yPLfXY3SOxlUIUC4bGj1O7aaeevouyfd%2FoWnzKOaEH5ik0E734f0m4nO2Se0L8Ejbf3IKD9%2FDM0%0AHrwbohzHaalBsT%2F5ZO4ztbUrrTBVw%2FjGTUze9DlMq4VoPetisDqygkjKN77%2FXZoHD6LGIuNoxjxn%0A%2FhnYs5n5PQ3oTzyeABIa1LhHZetnoeBZY0lZJ1Oe0F8kKRU50lpT%2B84uuq%2F%2BGj3h2RxHL%2BK5Ynp4%0AbyGI9aNIIpu24J%2BxkpX%2F%2Ba9QY%2BUk5m7%2F%2F8RBlNUJECPUdu9EWiaap4A3y3hRQoaYVJ1Q1lI2dX8o%0ANbCUtmSn0wpTE0qXfpCxy65IpKeouRIWh4f%2BCKoUyhgIAjqHX2Xq9v%2BLNMGoMIru9IwPFYAq0JNW%0AC4g%2Fx%2F5%2BQUPXsPyPv0Dp%2FZcQ1mrwFvFhFeUHqFKJ1o
2020-12-10 17:37:31.766 10343-10355/foundation.e.pwaplayer D/PwaProvider: insert() called with: uri = content://foundation.e.pwaplayer.provider/pwa, values = ICON=[B@98003ad TITLE=Telegram URL=https://web.telegram.org/?force=pwa&source=mlpwa SHORTCUT_ID=https://web.telegram.org/?force=pwa&source=mlpwa
```
**Relevant screenshots**
<Screenshots of the problem>
![screenshot_20201210_17_34_07](/uploads/4af7768a921818fac7b757f621a134ed/screenshot_20201210_17_34_07.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>Amit Kumaramitkma@e.emailAmit Kumaramitkma@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/19520.12 nougat build on August security patch level2022-02-10T15:52:23ZArnau Vàzquezarnauvp@murena.io0.12 nougat build on August security patch level
## Summary
Reported by a twitter user. Device Mido; to check for others.
0.12 build is retired from OTA/images but some users already have it on their phones.
## The problem
It should have the September patch level.
<How one can rep...
## Summary
Reported by a twitter user. Device Mido; to check for others.
0.12 build is retired from OTA/images but some users already have it on their phones.
## The problem
It should have the September patch level.
<How one can reproduce the issue>
**What is the current behavior?**
https://twitter.com/R54R41V4/status/1317044867672035328
![image](/uploads/c7c1606772c29a908aeeaa95885f0e71/image.png)
![image](/uploads/dc6d07e41cf77f2a604e747390e8fc30/image.png)
**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>Romain HunaultRomain Hunaulthttps://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/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 ...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/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/1555Calendar app dark mode makes hard to read email suggestions2021-07-30T16:54:39ZŽroutíkCalendar app dark mode makes hard to read email suggestions- /e/ version: 0.9-20200626
- Device model: LG-H850
- When it started to occur: NA
- Reproducible with the last /e/ version: yes
- Reproducible with LineageOS:
## Summary
Calendar app dark mode makes hard to read email suggestions to a...- /e/ version: 0.9-20200626
- Device model: LG-H850
- When it started to occur: NA
- Reproducible with the last /e/ version: yes
- Reproducible with LineageOS:
## Summary
Calendar app dark mode makes hard to read email suggestions to attendees.
<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**
Set the calendar app to dark mode. Edit event and start to write attendees. Suggestions come up in black font.
**What is the current behavior?**
The Dark grey BG of the app obstructs to read the suggestions properly.
**What is the expected correct behavior?**
The suggestions (the names and the suggested part of the email) should come up in light font color.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![Screenshot_20200715-091347_edit](/uploads/c93114224489bfdf3ef62582483bbd9e/Screenshot_20200715-091347_edit.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>