Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2024-03-25T06:58:19Zhttps://gitlab.e.foundation/e/backlog/-/issues/7876Magic Earth name has been changed to Maps2024-03-25T06:58:19ZBreweryMagic Earth name has been changed to MapsMagic Earth name in eOS has been changed to Maps, which is also the same name that Google Maps has. This could lead to confusion.
![Imagepipe_0](/uploads/2b2a84254a761f8694f396ad2c4acac2/Imagepipe_0.jpg)Magic Earth name in eOS has been changed to Maps, which is also the same name that Google Maps has. This could lead to confusion.
![Imagepipe_0](/uploads/2b2a84254a761f8694f396ad2c4acac2/Imagepipe_0.jpg)https://gitlab.e.foundation/e/backlog/-/issues/7779Issue with Navigation Bar text selection in native Browser2024-02-22T08:51:33ZŽroutíkIssue with Navigation Bar text selection in native Browser### Environment:
- **Device**: ~beyond2lte
- **/e/OS Version**: 1.19-s
- **Browser**: Native /e/OS Browser
### Description:
Previously, long-pressing the navigation bar in the native browser would result in the entire URL being selected...### Environment:
- **Device**: ~beyond2lte
- **/e/OS Version**: 1.19-s
- **Browser**: Native /e/OS Browser
### Description:
Previously, long-pressing the navigation bar in the native browser would result in the entire URL being selected, with a context menu appearing promptly. However, after updating to /e/OS version 1.19-s on the beyond2lte device, this behavior has changed. Now, when long-pressing the navigation bar, only a part of the URL is selected initially. To select the entire URL, additional steps are needed, such as manually adjusting the selection via the context menu. This change represents a degradation in usability, requiring extra steps for a task that was previously more straightforward.
### Steps to Reproduce:
1. Open the native browser on a beyond2lte device running /e/OS version 1.19-s.
2. Navigate to any website to ensure the navigation bar contains a URL.
3. Long press on the navigation bar where the URL is displayed.
4. Observe that only part of the URL is selected, unlike previous behavior where the whole URL would be selected.
### Expected Behavior:
Long pressing on the navigation bar should select the entire URL and present a context menu, facilitating quick actions such as copy, cut, or share.
### Actual Behavior:
Only a portion of the URL is selected upon long pressing, necessitating additional steps to select the whole URL, which complicates the usability.
### Additional Information:
- **Frequency of Occurrence**: Consistently reproducible on /e/OS version 1.19-s on beyond2lte.
- **Workaround**: Users can manually adjust the selection via the context menu, although this is less efficient than the previous behavior.
### Logcat (if applicable):https://gitlab.e.foundation/e/backlog/-/issues/7729Ambient display is not rotating automatically2024-02-21T14:49:17ZŽroutíkAmbient display is not rotating automatically- /e/ version: 1.19-s
- Device model(s): ~beyond2lte
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Ambient display is not rotating automatically. It remains rotated to the original positi...- /e/ version: 1.19-s
- Device model(s): ~beyond2lte
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Ambient display is not rotating automatically. It remains rotated to the original position of the rotated lock screen at the time of locking.
## The problem
**Steps to reproduce**
- allow ambient display
- allow lock screen rotation
- lock the screen and rotate to landscape
- wait for the ambient display
- rotate the device
**What is the current behavior?**
Ambient display do not rotate.
When ambient display is cancelled, the lock screen rotates to the current rotation position.
**What is the expected correct behavior?**
The ambient display follows the rotational position of the device.
## 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>
/label ~"type::Bug"
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/7411Settings -> Background and Stile (Theme?) crashes - unable to select background2024-02-17T10:29:09ZHelge KreutzmannSettings -> Background and Stile (Theme?) crashes - unable to select background- /e/ version: 1.15
- Device model(s):Fairphone 4
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Unable to set background due to crash of the app.
## The problem
To set the background, th...- /e/ version: 1.15
- Device model(s):Fairphone 4
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Unable to set background due to crash of the app.
## The problem
To set the background, the settings app is opened and then "background/style" (I don't know the exact English translation) is selected. Then a crash occurs.
**What is the current behavior?**
The app crash. Sometimes (e.g. on the 2nd try) I get a dialogue informing me that the app repeatedly crashed and I'm offered the opportunity to close it.
**What is the expected correct behavior?**
The app opens and I'm able to set the background.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
--------- beginning of crash
10-16 18:35:01.693 10561 10583 E AndroidRuntime: FATAL EXCEPTION: AsyncTask #1
10-16 18:35:01.693 10561 10583 E AndroidRuntime: Process: com.android.wallpaper, PID: 10561
10-16 18:35:01.693 10561 10583 E AndroidRuntime: java.lang.RuntimeException: An error occurred while executing doInBackground()
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at android.os.AsyncTask$4.done(AsyncTask.java:415)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:271)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at java.lang.Thread.run(Thread.java:920)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'int android.graphics.Bitmap.getWidth()' on a null object reference
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at com.android.wallpaper.asset.BitmapUtils.generateHashCode(BitmapUtils.java:71)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at com.android.wallpaper.module.DefaultWallpaperRefresher$GetWallpaperMetadataAsyncTask.getCurrentLockWallpaperHashCode(DefaultWallpaperRefresher.java:233)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at com.android.wallpaper.module.DefaultWallpaperRefresher$GetWallpaperMetadataAsyncTask.isLockScreenMetadataCurrent(DefaultWallpaperRefresher.java:313)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at com.android.wallpaper.module.DefaultWallpaperRefresher$GetWallpaperMetadataAsyncTask.doInBackground(DefaultWallpaperRefresher.java:119)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at com.android.wallpaper.module.DefaultWallpaperRefresher$GetWallpaperMetadataAsyncTask.doInBackground(DefaultWallpaperRefresher.java:78)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at android.os.AsyncTask$3.call(AsyncTask.java:394)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
10-16 18:35:01.693 10561 10583 E AndroidRuntime: ... 4 more
10-16 18:35:01.696 1644 10596 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
10-16 18:35:01.712 1644 2183 W ActivityTaskManager: Force finishing activity com.android.wallpaper/com.android.customization.picker.CustomizationPickerActivity
10-16 18:35:01.712 0 0 I binder : undelivered transaction 2416301, process died.
10-16 18:35:01.712 0 0 I binder : undelivered transaction 2416312, process died.
10-16 18:35:01.742 1644 3249 I WindowManager: WIN DEATH: Window{b2cff81 u0 com.android.wallpaper/com.android.customization.picker.CustomizationPickerActivity}
10-16 18:35:01.745 1644 2183 I ActivityManager: Process com.android.wallpaper (pid 10561) has died: prcp TOP
10-16 18:35:01.748 1644 3485 W WindowManager: Cannot find window which accessibility connection is added to
10-16 18:35:01.748 1644 2657 W WindowManager: Cannot find window which accessibility connection is added to
10-16 18:35:01.748 1644 1823 V WindowManager: Unknown focus tokens, dropping reportFocusChanged
10-16 18:35:01.795 1644 1824 W WindowManager: Failed to deliver inset state change to w=Window{b2cff81 u0 com.android.wallpaper/com.android.customization.picker.CustomizationPickerActivity EXITING}
10-16 18:35:01.795 1644 1824 W WindowManager: android.os.DeadObjectException
10-16 18:35:01.795 1644 1824 W WindowManager: at android.os.BinderProxy.transactNative(Native Method)
10-16 18:35:01.795 1644 1824 W WindowManager: at android.os.BinderProxy.transact(BinderProxy.java:571)
10-16 18:35:01.795 1644 1824 W WindowManager: at android.view.IWindow$Stub$Proxy.insetsControlChanged(IWindow.java:687)
10-16 18:35:01.795 1644 1824 W WindowManager: at com.android.server.wm.WindowState.notifyInsetsControlChanged(WindowState.java:4037)
10-16 18:35:01.795 1644 1824 W WindowManager: at com.android.server.wm.InsetsStateController.lambda$notifyPendingInsetsControlChanged$6$InsetsStateController(InsetsStateController.java:552)
10-16 18:35:01.795 1644 1824 W WindowManager: at com.android.server.wm.InsetsStateController$$ExternalSyntheticLambda1.run(Unknown Source:2)
10-16 18:35:01.795 1644 1824 W WindowManager: at com.android.server.wm.WindowAnimator.executeAfterPrepareSurfacesRunnables(WindowAnimator.java:345)
10-16 18:35:01.795 1644 1824 W WindowManager: at com.android.server.wm.RootWindowContainer.performSurfacePlacementNoTrace(RootWindowContainer.java:887)
10-16 18:35:01.795 1644 1824 W WindowManager: at com.android.server.wm.RootWindowContainer.performSurfacePlacement(RootWindowContainer.java:824)
10-16 18:35:01.795 1644 1824 W WindowManager: at com.android.server.wm.WindowSurfacePlacer.performSurfacePlacementLoop(WindowSurfacePlacer.java:177)
10-16 18:35:01.795 1644 1824 W WindowManager: at com.android.server.wm.WindowSurfacePlacer.performSurfacePlacement(WindowSurfacePlacer.java:126)
10-16 18:35:01.795 1644 1824 W WindowManager: at com.android.server.wm.WindowSurfacePlacer.performSurfacePlacement(WindowSurfacePlacer.java:115)
10-16 18:35:01.795 1644 1824 W WindowManager: at com.android.server.wm.WindowSurfacePlacer$Traverser.run(WindowSurfacePlacer.java:57)
10-16 18:35:01.795 1644 1824 W WindowManager: at android.os.Handler.handleCallback(Handler.java:938)
10-16 18:35:01.795 1644 1824 W WindowManager: at android.os.Handler.dispatchMessage(Handler.java:99)
10-16 18:35:01.795 1644 1824 W WindowManager: at android.os.Looper.loopOnce(Looper.java:201)
10-16 18:35:01.795 1644 1824 W WindowManager: at android.os.Looper.loop(Looper.java:288)
10-16 18:35:01.795 1644 1824 W WindowManager: at android.os.HandlerThread.run(HandlerThread.java:67)
10-16 18:35:01.795 1644 1824 W WindowManager: at com.android.server.ServiceThread.run(ServiceThread.java:44)
10-16 18:35:01.800 1644 1823 W ActivityManager: setHasOverlayUi called on unknown pid: 10561
10-16 18:35:01.803 1644 1824 W ActivityTaskManager: Can't find TaskDisplayArea to determine support for multi window. Task id=3271 attached=false
10-16 18:35:01.803 1644 1824 W ActivityTaskManager: Can't find TaskDisplayArea to determine support for multi window. Task id=3271 attached=false
10-16 18:35:01.820 0 0 I IRQ 5 : no longer affine to CPU5
10-16 18:35:01.879 1644 2708 W WindowManager: Failed looking up window session=Session{c0658a4 2329:u0a10137} callers=com.android.server.wm.WindowManagerService.windowForClientLocked:5779 com.android.server.wm.WindowManagerService.relayoutWindow:2247 com.android.server.wm.Session.relayout:235
10-16 18:35:01.882 1644 3485 W WindowManager: Cannot find window which accessibility connection is added to
10-16 18:35:01.883 1644 2708 W WindowManager: Failed looking up window session=Session{c0658a4 2329:u0a10137} callers=com.android.server.wm.WindowManagerService.windowForClientLocked:5779 com.android.server.wm.WindowManagerService.removeWindow:2051 com.android.server.wm.Session.remove:218
10-16 18:35:03.427 1644 2291 I ActivityTaskManager: START u0 {flg=0x10008000 cmp=com.android.wallpaper/com.android.customization.picker.CustomizationPickerActivity (has extras)} from uid 1000
10-16 18:35:03.428 1644 2291 W ActivityTaskManager: Can't find TaskDisplayArea to determine support for multi window. Task id=3272 attached=false
10-16 18:35:03.442 1644 1823 D CompatibilityChangeReporter: Compat change id reported: 135634846; UID 10139; state: DISABLED
10-16 18:35:03.442 1644 1823 D CompatibilityChangeReporter: Compat change id reported: 177438394; UID 10139; state: DISABLED
10-16 18:35:03.442 1644 1823 D CompatibilityChangeReporter: Compat change id reported: 135772972; UID 10139; state: DISABLED
10-16 18:35:03.442 1644 1823 D CompatibilityChangeReporter: Compat change id reported: 135754954; UID 10139; state: ENABLED
10-16 18:35:03.442 1644 1838 D CompatibilityChangeReporter: Compat change id reported: 143937733; UID 10139; state: ENABLED
10-16 18:35:03.456 1644 1838 I ActivityManager: Start proc 10602:com.android.wallpaper/u0a139 for pre-top-activity {com.android.wallpaper/com.android.customization.picker.CustomizationPickerActivity}
10-16 18:35:03.521 0 0 I IRQ 5 : no longer affine to CPU4
10-16 18:35:03.730 1644 2291 W WindowManager: Requires INTERNAL_SYSTEM_WINDOW permission if assign type to input
10-16 18:35:03.733 1644 2291 W WindowManager: Cannot find window which accessibility connection is added to
10-16 18:35:03.738 1644 2291 W WindowManager: Requires INTERNAL_SYSTEM_WINDOW permission if assign type to input
10-16 18:35:03.740 1644 2291 W WindowManager: Cannot find window which accessibility connection is added to
10-16 18:35:03.767 10602 10625 E AndroidRuntime: FATAL EXCEPTION: AsyncTask #1
10-16 18:35:03.767 10602 10625 E AndroidRuntime: Process: com.android.wallpaper, PID: 10602
10-16 18:35:03.767 10602 10625 E AndroidRuntime: java.lang.RuntimeException: An error occurred while executing doInBackground()
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at android.os.AsyncTask$4.done(AsyncTask.java:415)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:271)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at java.lang.Thread.run(Thread.java:920)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'int android.graphics.Bitmap.getWidth()' on a null object reference
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at com.android.wallpaper.asset.BitmapUtils.generateHashCode(BitmapUtils.java:71)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at com.android.wallpaper.module.DefaultWallpaperRefresher$GetWallpaperMetadataAsyncTask.getCurrentLockWallpaperHashCode(DefaultWallpaperRefresher.java:233)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at com.android.wallpaper.module.DefaultWallpaperRefresher$GetWallpaperMetadataAsyncTask.isLockScreenMetadataCurrent(DefaultWallpaperRefresher.java:313)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at com.android.wallpaper.module.DefaultWallpaperRefresher$GetWallpaperMetadataAsyncTask.doInBackground(DefaultWallpaperRefresher.java:119)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at com.android.wallpaper.module.DefaultWallpaperRefresher$GetWallpaperMetadataAsyncTask.doInBackground(DefaultWallpaperRefresher.java:78)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at android.os.AsyncTask$3.call(AsyncTask.java:394)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
10-16 18:35:03.767 10602 10625 E AndroidRuntime: ... 4 more
10-16 18:35:03.774 1644 2291 W ActivityTaskManager: Force finishing activity com.android.wallpaper/com.android.customization.picker.CustomizationPickerActivity
10-16 18:35:03.776 1644 10637 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
10-16 18:35:03.850 1644 1821 D CompatibilityChangeReporter: Compat change id reported: 168419799; UID 1000; state: DISABLED
10-16 18:35:03.974 1644 1821 W Looper : Slow dispatch took 111ms android.ui h=android.view.Choreographer$FrameHandler c=android.view.Choreographer$FrameDisplayEventReceiver@2e30cf2 m=0
10-16 18:35:04.044 1644 2183 W WindowManager: Cannot find window which accessibility connection is added to
10-16 18:35:04.046 1644 2183 W WindowManager: Failed looking up window session=Session{105722b 10602:u0a10139} callers=com.android.server.wm.WindowManagerService.windowForClientLocked:5779 com.android.server.wm.WindowManagerService.removeWindow:2051 com.android.server.wm.Session.remove:218
10-16 18:35:04.049 1644 3485 W WindowManager: Cannot find window which accessibility connection is added to
10-16 18:35:04.052 1644 3485 W WindowManager: Failed looking up window session=Session{105722b 10602:u0a10139} callers=com.android.server.wm.WindowManagerService.windowForClientLocked:5779 com.android.server.wm.WindowManagerService.removeWindow:2051 com.android.server.wm.Session.remove:218
10-16 18:35:04.072 1644 1824 W ActivityTaskManager: Can't find TaskDisplayArea to determine support for multi window. Task id=3272 attached=false
10-16 18:35:04.072 1644 1824 W ActivityTaskManager: Can't find TaskDisplayArea to determine support for multi window. Task id=3272 attached=false
```
**Relevant screenshots**
none
## Solutions
**Workaround**
Unfortunately, none known.
**Possible fixes**
None known.
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/7211System pull-down menu is overlapping the navigation bar2023-08-14T15:24:05ZRalph BöhlkeSystem pull-down menu is overlapping the navigation bar- /e/ version: v1.13-S-dev
- Device model(s): Beryllium
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
I recently restarted using the 3-button-navigation where I observed several hick-ups.
O...- /e/ version: v1.13-S-dev
- Device model(s): Beryllium
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
I recently restarted using the 3-button-navigation where I observed several hick-ups.
One of them is the following:
When the pull-down menu is longer than one screen length it is overlapping the navigation buttons. This is confusing from the user perspective.
(This behavior can be reproduced with the 2-button-navigation as well. For the gesture navigation it can be reproduced as well, but it is less of an issue as the navigation bar is very slim.)
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
- select the 3-button-navigation in the system settings (> System > Gestures > System navigation
- make sure that your pull down menu is exceeding one screen length (when it is fully pulled down). I.e.: Start music player and pull down the pull-down menu fully.
- In my case now the buttons of the audioplayer overlap the navigation buttons (as shown in the pic)
<What actually happens>
An interference of pull down menu elements in the space that should be dedicated to the navigation buttons.
<What you should see instead>
In case the pull down menu is taking as much space as a screen length, the pull down menu should slide behind the navigation buttons.
## Technical information
**Relevant logs (`adb logcat`)**
--none--
```
```
**Relevant screenshots**
![514-3-button-view](/uploads/41026c83bdd3a5c8116f0568deedad60/514-3-button-view.jpg)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/7156App Lounge UI bug prevents install2023-08-01T04:36:24ZStephen FagerhaugApp Lounge UI bug prevents install- /e/ version: 1.12.5-r-2023070330630-2-stable-zirconia
- Device model(s): teracube 2e
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
App Lounge just gives the weird error “ImageView.Drawab...- /e/ version: 1.12.5-r-2023070330630-2-stable-zirconia
- Device model(s): teracube 2e
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
App Lounge just gives the weird error “ImageView.Drawable must not be null” when I click the “Install” button for ANY app.
## The problem
**Steps to reproduce**
open app lounge
find an app to install
click the button
error is displayed at bottom of screen
**What is the current behavior?**
displays error, changes the button label like it is installing, nothing else happens.
**What is the expected correct behavior?**
install application
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
Don't know how to do this
**Relevant screenshots**
When I try to take a screenshot, the error message at the bottom of the screen is not captured
## Solutions
**Workaround**
I was playing around with Advanced Privacy and it made me think about other possible blocking technology that might interfere with the app store. I mean no one else is reporting this, so it must be just me, right?
I have a personal DNS filter installed to prevent “phone home” tracking for certain apps and to block addresses for ad/porn/hacker websites. After I whitelisted the App Lounge, it is working again. I wonder what DNS address it is calling that my filter is blocking?
**Possible fixes**
none
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/7143Notification quick settings overlapping2024-02-28T17:07:26ZAaron Chung-JukkoNotification quick settings overlapping- /e/ version: 1.12.3
- Device model(s): FP4
- Developer mode enabled: either
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
The quick settings tiles on pulling down the shade sometimes have both a 2x2 grid and a 1x4 gr...- /e/ version: 1.12.3
- Device model(s): FP4
- Developer mode enabled: either
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
The quick settings tiles on pulling down the shade sometimes have both a 2x2 grid and a 1x4 grid showing simultaneously.
![screenshot-2023-07-24-23-20-42-2](/uploads/e5cc4a181899054adf4e27899fbee702/screenshot-2023-07-24-23-20-42-2.png)
## Solutions
**Workaround**
Turn on brightness slider in Status Bar.
**Possible fixes**
Possibly a problem only when turning on the hide brightness slider dryinghttps://gitlab.e.foundation/e/backlog/-/issues/7018Apps: In light theme white buttons on white background2023-06-05T12:36:26ZbegeApps: In light theme white buttons on white background- /e/ version: 1.11-s-dev
- Device model(s): FP3
- Developer mode enabled: yes
- Device rooted: yes
- Trackers blocker enabled: yes
## Summary
In Android settings Apps: In light theme white buttons on white background
## The problem
...- /e/ version: 1.11-s-dev
- Device model(s): FP3
- Developer mode enabled: yes
- Device rooted: yes
- Trackers blocker enabled: yes
## Summary
In Android settings Apps: In light theme white buttons on white background
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
**What is the current behavior?**
<What actually happens>
**What is the expected correct behavior?**
Black buttons on white background
## 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>
~"/e/OS Settings"
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/6920Clock Stopwatch has incorrect lap times2023-05-25T07:11:28ZDeepee KhoslaClock Stopwatch has incorrect lap times- /e/ version: /e/OS 1.10-20230412278812
- Device model(s): Samsung Galaxy S7 SM-G930F
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
When using the stopwatch, lap times can get messed up.
...- /e/ version: /e/OS 1.10-20230412278812
- Device model(s): Samsung Galaxy S7 SM-G930F
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
When using the stopwatch, lap times can get messed up.
## The problem
**Steps to reproduce**
Run the stopwatch for several minutes, pressing "Lap" every few minutes.
**What is the current behavior?**
The lap times near the beginning are incorrect.
**What is the expected correct behavior?**
The lap times should be correct.
**Relevant screenshots**
In the screenshot, you can see that the first three individual and cumulative lap times are incorrect.
<Screenshots of the problem>
![Screenshot_20230417-154738_Clock](/uploads/86f175e7ac610fe11a6d4633116643b1/Screenshot_20230417-154738_Clock.png)
~"type::Bug"
~"/e/OS Clock"https://gitlab.e.foundation/e/backlog/-/issues/6747Have user friendly category names2024-03-08T05:54:28ZRalph BöhlkeHave user friendly category names- /e/ version: any
- Device model(s): any
- App Lounge: v.2.4.6
- Device rooted: no
## Summary
<Summarize the bug encountered briefly and precisely>
Some category names in App Lounge have technical names instead of user friendly names...- /e/ version: any
- Device model(s): any
- App Lounge: v.2.4.6
- Device rooted: no
## Summary
<Summarize the bug encountered briefly and precisely>
Some category names in App Lounge have technical names instead of user friendly names. As it wasn't the case when we first launched ~"App Lounge" it's probably due to a change in category names in the source. So we need to find a way to handle these changes so the Categories keeps user friendly names.
On a lesser priority in several cases the common categories and their open source counterparts do not have exactly the same names.
**Steps to reproduce**
1. Open ~"App Lounge"
2. go to "Categories"
**What is the current behavior?**
Some category names in App Lounge have technical names instead of user friendly names. For instance: `pwa_shopping`, `pwa_sports`, `pwa_travel`.
In several cases the common categories and their open source counterparts do not have exactly the same names. For instance:
- `Books & Reference`, `Books and Reference [Open Source]`
- `Personalisation`, `Personalization [Open Source]`
**What is the expected correct behavior?**
The category names all have user friendly names. For instance "Shopping" instead of pwa_shopping.
If it can be solved at the same time, the spelling of the open source category and their 'normal' counterparts should be spelled in an identical way.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![image](/uploads/297ab8db9e8b8a2ca856f82bbd042e67/image.png) ![469_AL-categories](/uploads/b486a63fce0329530de13c2f2049c20e/469_AL-categories.jpg)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/6654Calendar: suggested contact added as attendees can't be seen with dark theme2023-11-09T07:44:08ZMax NCalendar: suggested contact added as attendees can't be seen with dark theme- /e/ version: Android 11 / R 1.7-20230111250687
- Device model(s): Samsung A5 2017 (a5y17lte)
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
The suggested contact matching to the contact y...- /e/ version: Android 11 / R 1.7-20230111250687
- Device model(s): Samsung A5 2017 (a5y17lte)
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
The suggested contact matching to the contact you are adding as attendee in an event is not visible with dark theme
## The problem
**Steps to reproduce**
Enable dark them
Open an existing or new event
start to add the nam/first name of an existing contact
**What is the current behavior?**
/e/ suggests existing contacts matching with the first letters you are writing but it's displayed in a color which is not visible with dark theme
**What is the expected correct behavior?**
the suggested contact should be visible with dark theme like with light theme
## Technical informations
**Relevant logs (`adb logcat`)**
**Relevant screenshots**
![screen-20230210-021103](/uploads/4caa84e48df78174f69fd58af77106f0/screen-20230210-021103.mp4)
## Solutions
**Workaround**
switch to light theme or select the location where suggested contact is displyed.
**Possible fixes**
Change color of text with dark theme
~"type::Bug"
~"/e/OS Calendar"
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/6522Gallery dark mode - unreadable text in export dialog2024-01-16T08:56:19ZNeed NotGallery dark mode - unreadable text in export dialog- /e/ version: 1.7-beta-s
- Device model(s): alioth
- Developer mode enabled: yes
- Device rooted: yes
- Trackers blocker enabled: yes
## Summary
Some of the text in Gallery export dialog too dark to read in dark mode
## The problem
...- /e/ version: 1.7-beta-s
- Device model(s): alioth
- Developer mode enabled: yes
- Device rooted: yes
- Trackers blocker enabled: yes
## Summary
Some of the text in Gallery export dialog too dark to read in dark mode
## The problem
**Steps to reproduce**
Open picture in Gallery, click edit, then export
**What is the current behavior?**
Text between "Export..." and "Size..." inside the dialog ineligible.
**What is the expected correct behavior?**
All of the text should be readable
## Technical informations
**Relevant logs (`adb logcat`)**
N/A
**Relevant screenshots**
![image](/uploads/85544110311ebeb2617e0740292c7f83/image.png)
## Solutions
**Workaround**
N/A
**Possible fixes**
Make the text lighterhttps://gitlab.e.foundation/e/backlog/-/issues/6481Default widgets - hamonise their appearance2024-01-12T09:36:47ZRalph BöhlkeDefault widgets - hamonise their appearance- /e/ version:
- Device model(s):
- Device rooted: no
## Summary
The screenshot below shows different default widgets from /e/:
- 3x Browser
- 1x Message/SMS
- 1x Notes
- 1x Mail
- 1x Calendar
The collection of default widget does not ...- /e/ version:
- Device model(s):
- Device rooted: no
## Summary
The screenshot below shows different default widgets from /e/:
- 3x Browser
- 1x Message/SMS
- 1x Notes
- 1x Mail
- 1x Calendar
The collection of default widget does not appear very harmonic it terms of colors, text/title size, shape of the rounded corners.
There's the question as well if they all should be with a white/grey background or rather trans-lucid as the preinstalled ones.
It would be nice to have them all (including the preinstalled ones) following the same design language - ideally one that is easy to adapt for 3rd party apps to follow (in case there's an interest in the future).
![454_default-widgets](/uploads/4e723859db047ab0eb05469fca7928c9/454_default-widgets.jpg)https://gitlab.e.foundation/e/backlog/-/issues/6195Use launcher background on unlock screen2023-10-20T07:39:15ZRalph BöhlkeUse launcher background on unlock screen- /e/ version: e-1.5-S-testing
- Device model(s): FP3 + Beryllium (+ all)
- Device rooted: no
## Summary
The new unlock screen display needs some improvement.
## Description
**What is the current behavior?**
<What actually happens>
...- /e/ version: e-1.5-S-testing
- Device model(s): FP3 + Beryllium (+ all)
- Device rooted: no
## Summary
The new unlock screen display needs some improvement.
## Description
**What is the current behavior?**
<What actually happens>
The new S-testing has a new unlock screen.
- The unlock-screen now could almost be mixed up with a dialer. This is a degradation compared to previous versions. The unlock page should have the lock symbol (as it was featured by previous versions) or should be titled "unlock your device)
- It needs more contrast (https://gitlab.e.foundation/e/backlog/-/issues/6188)
| ~s | ~r |
| ------ | ------ |
| ![411-A13-Unlock-screen-new](/uploads/56d703479a452b8686eadf1ce7b6b109/411-A13-Unlock-screen-new.jpg) | ![412-A12-Unlock-screen-old](/uploads/d9ac8868c7d6fd87f1d0e5e1f110b601/412-A12-Unlock-screen-old.jpg) |
**What is the improved behavior?**
<What you should see instead>
If feasible (cf. [this comment](https://gitlab.e.foundation/e/backlog/-/issues/6195#note_409198)) use the Launcher's background on unlock screen.
If not, increase the contrast between the touchpad and the background like in this [mock-up](https://www.figma.com/file/UqyaxcrQebIz8AI7Hj6vI9/Android-12?node-id=623-6416&t=MBbFeGs73CnVUjLh-0).
**What does it bring?**
<Why this improvement is needed>
Nicer and easier to use UI
## Mock-ups
<Provide a mock-up of how it would look with the improvement>
https://www.figma.com/file/UqyaxcrQebIz8AI7Hj6vI9/Android-12?node-id=623-6416&t=MBbFeGs73CnVUjLh-0
## Examples
<Give the example of what users will be able to accomplish with the improvement>
## Validation
<List test case that will be run to validate that the issue is working as expected>
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>https://gitlab.e.foundation/e/backlog/-/issues/6188Add hint bar in quick settings2024-03-15T18:35:38ZRalph BöhlkeAdd hint bar in quick settings- /e/ version: e-1.9-S-testing
- Device model(s): any
## Summary
Add a hint bar in quick settings
![Hint_bar_final_anim](/uploads/ad14a0c2a65ffb68ef2c1bec087529f6/Hint_bar_final_anim.mp4)
## FIGMA:
https://www.figma.com/file/Uqyaxc...- /e/ version: e-1.9-S-testing
- Device model(s): any
## Summary
Add a hint bar in quick settings
![Hint_bar_final_anim](/uploads/ad14a0c2a65ffb68ef2c1bec087529f6/Hint_bar_final_anim.mp4)
## FIGMA:
https://www.figma.com/file/UqyaxcrQebIz8AI7Hj6vI9/Android-12?node-id=623-6416&t=MBbFeGs73CnVUjLh-0https://gitlab.e.foundation/e/backlog/-/issues/6078Harmonize usability of 'Message', 'Mail' and other default apps2023-10-09T15:38:23ZRalph BöhlkeHarmonize usability of 'Message', 'Mail' and other default apps- /e/ version: 1.4 and others
- Device model(s): any
- Device rooted: no
## Summary
The apps that come with /e/OS as default have their origins in other open source projects. Boxed within /e/, ideally they should look and feel in a sim...- /e/ version: 1.4 and others
- Device model(s): any
- Device rooted: no
## Summary
The apps that come with /e/OS as default have their origins in other open source projects. Boxed within /e/, ideally they should look and feel in a similar manner. Whereas the 'look' (color codes) has been harmonised, in terms of usability (the 'feel' side) there are still huge differences.
As an example I would just like to use the Mail (K9) and Message (Qsms) apps.Both apps had a similar aim - displaying messages, let the user read, reply and create new messages.
Major differences:
- Green dot for indicating unread messages: Message: right side of the message. Mail: Left side of the message
- Pic or shortcut of the senders name: Message: applied, left if the message. Mail: not applied
- Creating a new message: Message: Material Design button bottom right, Mail: hidden in the 3-dot-menu
- Getting rid of the message: Message: long-pressing the message, then the trash button for deletion or a swipe to archive it. Mail: Message: long-pressing the message, then the trash button for deletion, but no swipe-to-archive function. (issues for default settings for swipe actions [in Mail](https://gitlab.e.foundation/e/backlog/-/issues/844) and [in Message](https://gitlab.e.foundation/e/backlog/-/issues/6717))
- Search: Message: Central top space of the app, Mail: Lens-button then searching
- Hamburger menus look different in both apps
- Additional 3-dots menu: Message: not existing, Mail: existing, top right
Here is would be desirable to harmonise both apps (and subsequently other default apps)
![398-mail-qsms](/uploads/1b074a1dbafeb68522daf8a0eedeeaf9/398-mail-qsms.jpg)https://gitlab.e.foundation/e/backlog/-/issues/5809Improve visibility of the file transfer option2024-01-22T06:03:31ZAlexis NoetingerImprove visibility of the file transfer option- /e/ version: 1.1
- Device model(s): All
## Summary
Improve option to select file transfer by default in the OS.
## Description
**What is the current behavior?**
It is very hard for non-tech saavy users, or non Android experts, to ...- /e/ version: 1.1
- Device model(s): All
## Summary
Improve option to select file transfer by default in the OS.
## Description
**What is the current behavior?**
It is very hard for non-tech saavy users, or non Android experts, to understand what needs to be done to activate the file transfer option when they connect their phone to their computer.
Today it is buried in the settings.
**What is the improved behavior?**
A simple way to activate file transfer when connected to a computer. Maybe automated detection when the phone is connected to a computer ?
**What does it bring?**
More convenience for users. Less frustration, fewer tickets at the helpdesk.
## Examples
Access to their files on their phone faster and in a simpler manner.
## Validation
<List test case that will be run to validate that the issue is working as expected>
<Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue.>
## Checklist
- [ ] License
- [ ] Translations
- [ ] Documentation
- [ ] Test planhttps://gitlab.e.foundation/e/backlog/-/issues/3769Phone app proposing to use my location to propose places near me2023-12-12T06:15:46ZRalph BöhlkePhone app proposing to use my location to propose places near me- /e/ version: 0.18-R/beta, 0.18-q
- Device model(s): Beryllium, FP3
- Device rooted: yes/no
## Summary
My phone app is asking to use my location to propose places near me.
I wonder:
- Does this app try to contact G-servers?
- Is th...- /e/ version: 0.18-R/beta, 0.18-q
- Device model(s): Beryllium, FP3
- Device rooted: yes/no
## Summary
My phone app is asking to use my location to propose places near me.
I wonder:
- Does this app try to contact G-servers?
- Is that a functionality that is desired within /e/?
![264_contactinfo_for_placesnearme](/uploads/fa5c3a35e3575698e785a8562a925b6a/264_contactinfo_for_placesnearme.jpg)https://gitlab.e.foundation/e/backlog/-/issues/3761No "About" section in FM Radio2023-10-25T11:15:03ZRalph BöhlkeNo "About" section in FM Radio- /e/ version: 0.18-R/beta + 0.18-P
- Device model(s): Beryllium + Santoni
- Device rooted: no
## Summary
As the title says: The app has no "About" section- /e/ version: 0.18-R/beta + 0.18-P
- Device model(s): Beryllium + Santoni
- Device rooted: no
## Summary
As the title says: The app has no "About" sectionhttps://gitlab.e.foundation/e/backlog/-/issues/3760No "About" section in Recorder app2023-10-25T11:16:53ZRalph BöhlkeNo "About" section in Recorder app- /e/ version: 0.18-R/beta + 0.18-P
- Device model(s): Beryllium + Santoni
- Device rooted: no
## Summary
As the title says: The app has no "About" section- /e/ version: 0.18-R/beta + 0.18-P
- Device model(s): Beryllium + Santoni
- Device rooted: no
## Summary
As the title says: The app has no "About" section