Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2024-03-29T08:02:29Zhttps://gitlab.e.foundation/e/backlog/-/issues/7889Fix padding for Voice over LTE indicator2024-03-29T08:02:29ZMohammed Althaf ThayyilFix padding for Voice over LTE indicator- /e/ version: 1.22
- Device model(s): all
## Summary
Fix padding for the icon as mentioned in [discussion](https://gitlab.e.foundation/e/backlog/-/issues/7865#note_522503)
## Description
**What is the current behavior?**
There's so...- /e/ version: 1.22
- Device model(s): all
## Summary
Fix padding for the icon as mentioned in [discussion](https://gitlab.e.foundation/e/backlog/-/issues/7865#note_522503)
## Description
**What is the current behavior?**
There's some extra padding for volte icon left and right.
**What is the improved behavior?**
There's no extra padding for volte icon left and right.
![image](/uploads/2bfd634616362f8b6af0413ad0d3e169/image.png) ![image](/uploads/3e9c8fa0bda6376782926fbdc9d203c1/image.png)
**What does it bring?**
## Examples
## Validation
The dialer have to display a VoLTE icon in the dialer if a VoLTE is available.
## Design
https://www.figma.com/file/B0ICdQKmT1aFsRoKVCUkhT/Launcher-icons?node-id=1126%3A16
cc @rhunault @AlexDuCens @aude @rhandros @nicofonkhttps://gitlab.e.foundation/e/backlog/-/issues/7888New default shortcut in Browser: Murena.com2024-03-29T13:51:21ZAude MNew default shortcut in Browser: Murena.com## Summary
Add a new default shortcut in ~"/e/OS Browser" to the murena.com website
## Description
**What is the feature?**
Add a new default shortcut in ~"/e/OS Browser" to the murena.com website. Users who wish it can choose to in...## Summary
Add a new default shortcut in ~"/e/OS Browser" to the murena.com website
## Description
**What is the feature?**
Add a new default shortcut in ~"/e/OS Browser" to the murena.com website. Users who wish it can choose to install it as a webapp from the browser's options. Users will be automatically logged into based on their /e/OS user login after the implementation of https://gitlab.e.foundation/e/backlog/-/issues/6287.
**Who will use this new feature?**
Everyone who uses the Murena.com website from the mobile
**Why these users would like to use this feature?**
It will be easier for everyone to access the shop
## Examples
<Give the example of what users will be able to accomplish with the feature>
## Reflection
**Mockups**
**Diagrams**
## 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.>/e/OS v2.0-betahttps://gitlab.e.foundation/e/backlog/-/issues/7887advanced privacy shows 2 trackers on Maps (magic earth)2024-03-27T18:51:54ZBreweryadvanced privacy shows 2 trackers on Maps (magic earth)- /e/ version: 1.20t
- Device model(s): Samsung a52q
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
advanced privacy shows 2 trackers on Maps (magic earth) 7.1.23.51
## The problem
**Step...- /e/ version: 1.20t
- Device model(s): Samsung a52q
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
advanced privacy shows 2 trackers on Maps (magic earth) 7.1.23.51
## The problem
**Steps to reproduce**
1. Enable advanced privacy
2. Use Maps for a while
3. Look at Maps' trackers in advanced privacy
**What is the current behavior?**
Advanced privacy detects 2 trackers:
- Google AdMob
- Google DoubleClick
**What is the expected correct behavior?**
According to [exodus](https://reports.exodus-privacy.eu.org/it/reports/com.generalmagic.magicearth/latest) Magic Earth has no trackers.
This is also confirmed if I run [ClassyShark3xodus](https://f-droid.org/it/packages/com.oF2pks.classyshark3xodus) on the installed Maps
## Technical informations
**Relevant screenshots**
<Screenshots of the problem>
![Imagepipe_2](/uploads/a4d7c0228f6f368c045b569c3579d5e5/Imagepipe_2.jpg)
![Imagepipe_3](/uploads/c8dfc91cdd11073b722d1d409b195eb2/Imagepipe_3.jpg)
![Imagepipe_1](/uploads/7fcd112472698800a88f7aa42e84b93f/Imagepipe_1.jpg)
![Imagepipe_0](/uploads/da54315247cb97978240039efe20edc5/Imagepipe_0.jpg)
/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/7878Wrong link to Exodus Privacy website2024-03-25T16:48:46ZMR TNWrong link to Exodus Privacy website- /e/ version: /e/OS 1.20 S
- Device model(s): Fairphone 3+
## Summary
Avoid getting an incorrect link to the Exodus Privacy website through the App Lounge.
## Description
**What is the current behavior?**
When you view the Privacy ...- /e/ version: /e/OS 1.20 S
- Device model(s): Fairphone 3+
## Summary
Avoid getting an incorrect link to the Exodus Privacy website through the App Lounge.
## Description
**What is the current behavior?**
When you view the Privacy Analysis of an app in the App Lounge, if you look at 'Tackers' you can be redirected via a link to that app's report on the Exodus Privacy website.
As an example, I am using Spotify and the link looks like this : https://reports.exodus-privacy.eu.org/nl/reports/422100/
In this case, I keep getting a 'Not Found' message from my browser (Fennec). When I change the '_/nl/_' part from the link to '_/en/_' I do land on the website.
Check : https://reports.exodus-privacy.eu.org/en/reports/422100/
**What is the improved behavior?**
Since the Exodus Privacy website only supports 6 languages (de, el, en, es, fr, it) the links in the App Lounge would default to one of these languages (english I suppose) when the system language of /e/OS is different (in my case Dutch/Netherlands -> nl).
**What does it bring?**
Users land on the Exodus Privacy website (even if it is not in their native language) instead of a 'Not Found' notification from the browser.
## Mock-ups
## Examples
Wrong link : reports.exodus-privacy.eu.org/~~**nl**~~/reports/422100/
Correct link : reports.exodus-privacy.eu.org/**en**/reports/422100/
## Validation
<List test case that will be run to validate that the issue is working as expected>
/label ~"type::Improvement"
<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/7877File names of notification sounds mixed up2024-03-25T06:57:42ZbegeFile names of notification sounds mixed up- /e/ version: S,T
- Device model(s): FP3, Shift6mq
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
Some notification sound files have wrong names
## The problem
- /product/media...- /e/ version: S,T
- Device model(s): FP3, Shift6mq
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
Some notification sound files have wrong names
## The problem
- /product/media/audio/notifications/Syrma.ogg should be TaDa.ogg
- TaDa.ogg should be Talitha.ogg
- Talitha.ogg should be ?
## 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/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/7874SafetyNet works on first 2 attempts, then always fails2024-03-26T07:01:22ZMossroySafetyNet works on first 2 attempts, then always fails- /e/ version & Device model(s): SM-P610: 1.20-t-20240222382228-dev-gta4xlwifi, FP5: 1.20-t-20240220382010-stable-FP5, FP3: 1.20-s-20240220382012-stable-FP3, SM-G900F: 1.20-r-20240221382014-dev-klte
- Developer mode enabled: only on some...- /e/ version & Device model(s): SM-P610: 1.20-t-20240222382228-dev-gta4xlwifi, FP5: 1.20-t-20240220382010-stable-FP5, FP3: 1.20-s-20240220382012-stable-FP3, SM-G900F: 1.20-r-20240221382014-dev-klte
- Developer mode enabled: only on some of these devices
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
Apps that test SafetyNet do not report a consistent result, whatever the device
## The problem
**Steps to reproduce**
* Restart the device
* Run app “SafetyNet Test”, and click on “run test”. Test passes
* Do it a second time. Test passes
* Do it a third time. Test fails
* Do it again an again. Test always fails
Similar behavior with YASNAC app: first 2 tests succeed, and the following ones make the app crash.
**What is the current behavior?**
SafetyNet only works on first 2 attempts
**What is the expected correct behavior?**
SafetyNet should work consistently: whatever the result, it should always be the same
## Technical informations
**Relevant logs (`adb logcat`)**
This is the adb log with YASNAC app, when it crashes (on a third attempt to test SafetyNet, on a FP3):
```
03-23 16:03:32.147 7697 7825 W id.gms.unstabl: Shared library "/data/user/0/com.google.android.gms/app_cache_dg/bafc9a1420cf208f3652b1b9a5c91dd0ba217db3/the.apk!/libd55E5F2B2681F.so" already opened by ClassLoader 0x207(dalvik.system.DexClassLoader[DexPathList[[zip file "/data/user/0/com.google.android.gms/app_cache_dg/bafc9a1420cf208f3652b1b9a5c91dd0ba217db3/the.apk"],nativeLibraryDirectories=[/system/lib64, /system/system_ext/lib64, /system/product/lib64]]]); can't open in ClassLoader 0x6e25a7bfcc(dalvik.system.DexClassLoader[DexPathList[[zip file "/data/user/0/com.google.android.gms/app_cache_dg/bafc9a1420cf208f3652b1b9a5c91dd0ba217db3/the.apk"],nativeLibraryDirectories=[/system/lib64, /system/system_ext/lib64, /system/product/lib64]]])
03-23 16:03:32.148 7697 7825 W id.gms.unstabl: Shared library "/data/user/0/com.google.android.gms/app_cache_dg/bafc9a1420cf208f3652b1b9a5c91dd0ba217db3/libd55E5F2B2681F.so" already opened by ClassLoader 0x3a7(dalvik.system.DexClassLoader[DexPathList[[zip file "/data/user/0/com.google.android.gms/app_cache_dg/bafc9a1420cf208f3652b1b9a5c91dd0ba217db3/the.apk"],nativeLibraryDirectories=[/system/lib64, /system/system_ext/lib64, /system/product/lib64]]]); can't open in ClassLoader 0x6e25a7bfcc(dalvik.system.DexClassLoader[DexPathList[[zip file "/data/user/0/com.google.android.gms/app_cache_dg/bafc9a1420cf208f3652b1b9a5c91dd0ba217db3/the.apk"],nativeLibraryDirectories=[/system/lib64, /system/system_ext/lib64, /system/product/lib64]]])
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: Error during handle init
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: org.microg.gms.droidguard.core.BytesException: java.lang.reflect.InvocationTargetException
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.HandleProxy.<init>(HandleProxy.kt:26)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.HandleProxyFactory.createHandleProxy(HandleProxyFactory.kt:169)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.HandleProxyFactory.createHandle(HandleProxyFactory.kt:38)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.DroidGuardHandleImpl.initWithRequest(DroidGuardHandleImpl.kt:50)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at com.google.android.gms.droidguard.internal.IDroidGuardHandle$Stub.onTransact(IDroidGuardHandle.java:100)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at android.os.Binder.execTransactInternal(Binder.java:1184)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at android.os.Binder.execTransact(Binder.java:1143)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at android.os.BinderProxy.transactNative(Native Method)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at android.os.BinderProxy.transact(BinderProxy.java:571)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at com.google.android.gms.common.internal.IGmsCallbacks$Stub$Proxy.onPostInitComplete(IGmsCallbacks.java:132)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.DroidGuardServiceBroker.handleServiceRequest(DroidGuardServiceBroker.kt:24)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.DroidGuardServiceBroker.getService(DroidGuardServiceBroker.kt:19)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at com.google.android.gms.common.internal.IGmsServiceBroker$Stub.onTransact(IGmsServiceBroker.java:505)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at org.microg.gms.AbstractGmsServiceBroker.onTransact(AbstractGmsServiceBroker.java:271)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at android.os.Binder.execTransactInternal(Binder.java:1184)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at android.os.Binder.execTransact(Binder.java:1143)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: Caused by: java.lang.reflect.InvocationTargetException
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at java.lang.reflect.Constructor.newInstance0(Native Method)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at java.lang.reflect.Constructor.newInstance(Constructor.java:343)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.HandleProxy.<init>(HandleProxy.kt:24)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: ... 15 more
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: Caused by: java.lang.RuntimeException: Stored in static init
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at com.google.ccc.abuse.droidguard.DroidGuard.<init>(PG:35)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at com.google.ccc.abuse.droidguard.DroidGuard.<init>(PG:22)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: ... 18 more
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: Caused by: java.lang.RuntimeException: During static init
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at com.google.ccc.abuse.droidguard.DroidGuard.<clinit>(PG:10)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: ... 18 more
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: Caused by: java.lang.UnsatisfiedLinkError: Shared library "/data/user/0/com.google.android.gms/app_cache_dg/bafc9a1420cf208f3652b1b9a5c91dd0ba217db3/libd55E5F2B2681F.so" already opened by ClassLoader 0x3a7(dalvik.system.DexClassLoader[DexPathList[[zip file "/data/user/0/com.google.android.gms/app_cache_dg/bafc9a1420cf208f3652b1b9a5c91dd0ba217db3/the.apk"],nativeLibraryDirectories=[/system/lib64, /system/system_ext/lib64, /system/product/lib64]]]); can't open in ClassLoader 0x6e25a7bfcc(dalvik.system.DexClassLoader[DexPathList[[zip file "/data/user/0/com.google.android.gms/app_cache_dg/bafc9a1420cf208f3652b1b9a5c91dd0ba217db3/the.apk"],nativeLibraryDirectories=[/system/lib64, /system/system_ext/lib64, /system/product/lib64]]])
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at java.lang.Runtime.load0(Runtime.java:929)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at java.lang.System.load(System.java:1620)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at com.google.ccc.abuse.droidguard.DroidGuard.loadDroidGuardLibrary(PG:173)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: at com.google.ccc.abuse.droidguard.DroidGuard.<clinit>(PG:1)
03-23 16:03:32.150 7697 7825 W GmsGuardHandleImpl: ... 18 more
03-23 16:03:32.150 7697 7709 D GmsGuardHandleImpl: init(attest)
03-23 16:03:32.150 7697 7709 D GmsGuardHandleImpl: initWithRequest(attest, null)
03-23 16:03:32.150 7697 7719 D GmsGuardHandleImpl: snapshot({contentBinding=enZtLs0JLI7C8v2L79fxacG+y1JSA8KPUhI5sYAWjvA=})
03-23 16:03:32.151 7697 7719 W DGFallback: create(attest)
03-23 16:03:32.151 7697 7719 W DGFallback: kotlin.NotImplementedError: An operation is not implemented: Not yet implemented
03-23 16:03:32.151 7697 7719 W DGFallback: at org.microg.gms.droidguard.core.FallbackCreator.create(FallbackCreator.kt:31)
03-23 16:03:32.151 7697 7719 W DGFallback: at org.microg.gms.droidguard.core.FallbackCreator.create(FallbackCreator.kt:21)
03-23 16:03:32.151 7697 7719 W DGFallback: at org.microg.gms.droidguard.core.DroidGuardHandleImpl.snapshot(DroidGuardHandleImpl.kt:86)
03-23 16:03:32.151 7697 7719 W DGFallback: at com.google.android.gms.droidguard.internal.IDroidGuardHandle$Stub.onTransact(IDroidGuardHandle.java:84)
03-23 16:03:32.151 7697 7719 W DGFallback: at android.os.Binder.execTransactInternal(Binder.java:1184)
03-23 16:03:32.151 7697 7719 W DGFallback: at android.os.Binder.execTransact(Binder.java:1143)
03-23 16:03:32.151 3099 5201 D GmsClient: disconnect()
03-23 16:03:32.151 3099 5201 D GmsMultiConKeeper: unbind(com.google.android.gms.droidguard.service.START, org.microg.gms.common.GmsClient$GmsServiceConnection@f652594)
03-23 16:03:32.151 3099 5201 D GmsMultiConKeeper: Connection(com.google.android.gms.droidguard.service.START) : unbind()
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: Error during handle init
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: org.microg.gms.droidguard.core.BytesException: java.lang.reflect.InvocationTargetException
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.HandleProxy.<init>(HandleProxy.kt:26)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.HandleProxyFactory.createHandleProxy(HandleProxyFactory.kt:169)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.HandleProxyFactory.createHandle(HandleProxyFactory.kt:38)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.DroidGuardHandleImpl.initWithRequest(DroidGuardHandleImpl.kt:50)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.DroidGuardHandleImpl.init(DroidGuardHandleImpl.kt:29)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at com.google.android.gms.droidguard.internal.IDroidGuardHandle$Stub.onTransact(IDroidGuardHandle.java:76)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at android.os.Binder.execTransactInternal(Binder.java:1184)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at android.os.Binder.execTransact(Binder.java:1143)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: Caused by: java.lang.reflect.InvocationTargetException
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at java.lang.reflect.Constructor.newInstance0(Native Method)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at java.lang.reflect.Constructor.newInstance(Constructor.java:343)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.HandleProxy.<init>(HandleProxy.kt:24)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: ... 7 more
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: Caused by: java.lang.RuntimeException: Stored in static init
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at com.google.ccc.abuse.droidguard.DroidGuard.<init>(PG:35)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at com.google.ccc.abuse.droidguard.DroidGuard.<init>(PG:22)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: ... 10 more
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: Caused by: java.lang.RuntimeException: During static init
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at com.google.ccc.abuse.droidguard.DroidGuard.<clinit>(PG:10)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at java.lang.reflect.Constructor.newInstance0(Native Method)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at java.lang.reflect.Constructor.newInstance(Constructor.java:343)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.HandleProxy.<init>(HandleProxy.kt:24)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.HandleProxyFactory.createHandleProxy(HandleProxyFactory.kt:169)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.HandleProxyFactory.createHandle(HandleProxyFactory.kt:38)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.DroidGuardHandleImpl.initWithRequest(DroidGuardHandleImpl.kt:50)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at com.google.android.gms.droidguard.internal.IDroidGuardHandle$Stub.onTransact(IDroidGuardHandle.java:100)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at android.os.Binder.execTransactInternal(Binder.java:1184)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at android.os.Binder.execTransact(Binder.java:1143)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at android.os.BinderProxy.transactNative(Native Method)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at android.os.BinderProxy.transact(BinderProxy.java:571)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at com.google.android.gms.common.internal.IGmsCallbacks$Stub$Proxy.onPostInitComplete(IGmsCallbacks.java:132)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.DroidGuardServiceBroker.handleServiceRequest(DroidGuardServiceBroker.kt:24)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at org.microg.gms.droidguard.core.DroidGuardServiceBroker.getService(DroidGuardServiceBroker.kt:19)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at com.google.android.gms.common.internal.IGmsServiceBroker$Stub.onTransact(IGmsServiceBroker.java:505)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at org.microg.gms.AbstractGmsServiceBroker.onTransact(AbstractGmsServiceBroker.java:271)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: ... 2 more
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: Caused by: java.lang.UnsatisfiedLinkError: Shared library "/data/user/0/com.google.android.gms/app_cache_dg/bafc9a1420cf208f3652b1b9a5c91dd0ba217db3/libd55E5F2B2681F.so" already opened by ClassLoader 0x3a7(dalvik.system.DexClassLoader[DexPathList[[zip file "/data/user/0/com.google.android.gms/app_cache_dg/bafc9a1420cf208f3652b1b9a5c91dd0ba217db3/the.apk"],nativeLibraryDirectories=[/system/lib64, /system/system_ext/lib64, /system/product/lib64]]]); can't open in ClassLoader 0x6e25a7bfcc(dalvik.system.DexClassLoader[DexPathList[[zip file "/data/user/0/com.google.android.gms/app_cache_dg/bafc9a1420cf208f3652b1b9a5c91dd0ba217db3/the.apk"],nativeLibraryDirectories=[/system/lib64, /system/system_ext/lib64, /system/product/lib64]]])
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at java.lang.Runtime.load0(Runtime.java:929)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at java.lang.System.load(System.java:1620)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at com.google.ccc.abuse.droidguard.DroidGuard.loadDroidGuardLibrary(PG:173)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: at com.google.ccc.abuse.droidguard.DroidGuard.<clinit>(PG:1)
03-23 16:03:32.174 7697 7709 W GmsGuardHandleImpl: ... 18 more
03-23 16:03:32.174 7697 7709 D GmsGuardHandleImpl: close()
03-23 16:03:32.176 6770 7272 I TAZ : [INFO ] new event arrived <mobile_riskscore_change>
03-23 16:03:32.177 6770 7272 I TAZ : [INFO ] event processing aborted by preprocessor
03-23 16:03:32.181 6770 7272 I TAZ : [INFO ] Creating TSSVM sigfile header
03-23 16:03:32.235 6770 7272 I TAZ : [INFO ] new event arrived <mobile_riskscore_change>
03-23 16:03:32.236 6770 7272 I TAZ : [INFO ] event processing aborted by preprocessor
03-23 16:03:32.250 7630 7630 D AndroidRuntime: Shutting down VM
03-23 16:03:32.256 6770 7272 I TAZ : [INFO ] Creating TSSVM sigfile header
03-23 16:03:32.257 7630 7630 E AndroidRuntime: FATAL EXCEPTION: main
03-23 16:03:32.257 7630 7630 E AndroidRuntime: Process: rikka.safetynetchecker, PID: 7630
03-23 16:03:32.257 7630 7630 E AndroidRuntime: java.lang.IllegalStateException: pending composition has not been applied
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at ua.q(Unknown Source:75)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at ua.h(Unknown Source:4)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at Bw.a(:2)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at L9.a(:2)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at ua.b(Unknown Source:10)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at Tn.L(:44)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at iz.t0(:43)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at rq.b(:5)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at Un.b(:2)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at LJ.s(:16)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at ct.a(:44)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at On.x(:9)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at Dl.n0(:12)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at Ju.e0(Unknown Source:0)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at Iu.d(:2)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at Rs.q0(:2)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at Qs.s(:2)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at ct.a(:37)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at Rs.n0(:7)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at oq.e(:28)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at oq.d(:4)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at androidx.compose.ui.platform.AndroidComposeView.Z(Unknown Source:8)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at uA.k(Unknown Source:7)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at androidx.compose.ui.platform.AndroidComposeView.dispatchDraw(:2)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.View.draw(View.java:22707)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.View.updateDisplayListIfDirty(View.java:21579)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:4512)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:4485)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.View.updateDisplayListIfDirty(View.java:21535)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:4512)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:4485)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.View.updateDisplayListIfDirty(View.java:21535)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:4512)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:4485)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.View.updateDisplayListIfDirty(View.java:21535)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:4512)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:4485)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.View.updateDisplayListIfDirty(View.java:21535)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ThreadedRenderer.updateViewTreeDisplayList(ThreadedRenderer.java:534)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ThreadedRenderer.updateRootDisplayList(ThreadedRenderer.java:540)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ThreadedRenderer.draw(ThreadedRenderer.java:616)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ViewRootImpl.draw(ViewRootImpl.java:4531)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:4251)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:3374)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:2179)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:8793)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1037)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.Choreographer.doCallbacks(Choreographer.java:845)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.Choreographer.doFrame(Choreographer.java:780)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1022)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7870)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
03-23 16:03:32.257 7630 7630 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)
03-23 16:03:32.260 1505 8010 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
03-23 16:03:32.260 1505 2258 W ActivityTaskManager: Force finishing activity rikka.safetynetchecker/.main.MainActivity
03-23 16:03:32.280 7630 7630 I Process : Sending signal. PID: 7630 SIG: 9
03-23 16:03:32.398 0 0 I binder : undelivered transaction 459413, process died.
03-23 16:03:32.399 1505 1566 I WindowManager: WIN DEATH: Window{daa05c0 u0 rikka.safetynetchecker/rikka.safetynetchecker.main.MainActivity}
03-23 16:03:32.399 1505 6096 I ActivityManager: Process rikka.safetynetchecker (pid 7630) has died: prcp TOP
03-23 16:03:32.399 1505 1566 W InputManager-JNI: Input channel object 'daa05c0 rikka.safetynetchecker/rikka.safetynetchecker.main.MainActivity (client)' was disposed without first being removed with the input manager!
03-23 16:03:32.401 760 760 I Zygote : Process 7630 exited due to signal 9 (Killed)
03-23 16:03:32.405 1505 1714 I libprocessgroup: Successfully killed process cgroup uid 10014 pid 7630 in 5ms
03-23 16:03:32.428 564 564 E ClientCache: failed to get buffer, invalid process token
03-23 16:03:32.444 3083 3083 D android.widget.GridLayout: horizontal constraints: x4-x0>=992, x4-x3<=247, x3-x2<=247, x2-x1<=247, x1-x0<=247 are inconsistent; permanently removing: x4-x3<=247.
03-23 16:03:32.465 1505 1691 W WindowManager: Failed to deliver inset state change to w=Window{daa05c0 u0 rikka.safetynetchecker/rikka.safetynetchecker.main.MainActivity EXITING}
03-23 16:03:32.465 1505 1691 W WindowManager: android.os.DeadObjectException
03-23 16:03:32.465 1505 1691 W WindowManager: at android.os.BinderProxy.transactNative(Native Method)
03-23 16:03:32.465 1505 1691 W WindowManager: at android.os.BinderProxy.transact(BinderProxy.java:571)
03-23 16:03:32.465 1505 1691 W WindowManager: at android.view.IWindow$Stub$Proxy.insetsControlChanged(IWindow.java:687)
03-23 16:03:32.465 1505 1691 W WindowManager: at com.android.server.wm.WindowState.notifyInsetsControlChanged(WindowState.java:4045)
03-23 16:03:32.465 1505 1691 W WindowManager: at com.android.server.wm.InsetsStateController.lambda$notifyPendingInsetsControlChanged$6$InsetsStateController(InsetsStateController.java:552)
03-23 16:03:32.465 1505 1691 W WindowManager: at com.android.server.wm.InsetsStateController$$ExternalSyntheticLambda1.run(Unknown Source:2)
03-23 16:03:32.465 1505 1691 W WindowManager: at com.android.server.wm.WindowAnimator.executeAfterPrepareSurfacesRunnables(WindowAnimator.java:345)
03-23 16:03:32.465 1505 1691 W WindowManager: at com.android.server.wm.WindowAnimator.animate(WindowAnimator.java:226)
03-23 16:03:32.465 1505 1691 W WindowManager: at com.android.server.wm.WindowAnimator.lambda$new$1$WindowAnimator(WindowAnimator.java:106)
03-23 16:03:32.465 1505 1691 W WindowManager: at com.android.server.wm.WindowAnimator$$ExternalSyntheticLambda0.doFrame(Unknown Source:2)
03-23 16:03:32.465 1505 1691 W WindowManager: at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1035)
03-23 16:03:32.465 1505 1691 W WindowManager: at android.view.Choreographer.doCallbacks(Choreographer.java:845)
03-23 16:03:32.465 1505 1691 W WindowManager: at android.view.Choreographer.doFrame(Choreographer.java:775)
03-23 16:03:32.465 1505 1691 W WindowManager: at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1022)
03-23 16:03:32.465 1505 1691 W WindowManager: at android.os.Handler.handleCallback(Handler.java:938)
03-23 16:03:32.465 1505 1691 W WindowManager: at android.os.Handler.dispatchMessage(Handler.java:99)
03-23 16:03:32.465 1505 1691 W WindowManager: at android.os.Looper.loopOnce(Looper.java:201)
03-23 16:03:32.465 1505 1691 W WindowManager: at android.os.Looper.loop(Looper.java:288)
03-23 16:03:32.465 1505 1691 W WindowManager: at android.os.HandlerThread.run(HandlerThread.java:67)
03-23 16:03:32.465 1505 1691 W WindowManager: at com.android.server.ServiceThread.run(ServiceThread.java:44)
03-23 16:03:32.496 1505 1690 W ActivityManager: setHasOverlayUi called on unknown pid: 7630
03-23 16:03:32.501 564 564 E BpTransactionCompletedListener: Failed to transact (-32)
03-23 16:03:32.507 1505 1691 W ActivityTaskManager: Can't find TaskDisplayArea to determine support for multi window. Task id=43 attached=false
03-23 16:03:32.507 1505 1691 W ActivityTaskManager: Can't find TaskDisplayArea to determine support for multi window. Task id=43 attached=false
```
**Relevant screenshots**
![image.png](/uploads/010d2211676b8b363d1e409a7a977431/image.png)
![image.png](/uploads/43f65cad98a1072c30f12a4bce902b31/image.png)
![image.png](/uploads/d3f973a3e0580914edff1b45c21c4255/image.png)
![image.png](/uploads/1c8146b4625b139e5d311bcffaa79682/image.png)
![image.png](/uploads/721cf674e7470c7d5997d854e02750a9/image.png)
![image.png](/uploads/10f2cc70d7a1bd7f0002c37c051d03bf/image.png)
![image.png](/uploads/ea5d3042bbd0039595994c32bb9e1517/image.png)
![image.png](/uploads/a21dcdc92f8b0e0c81dac6c0ce6cbd8a/image.png)
## Solutions
**Workaround**\
Restart the device
**Possible fixes**https://gitlab.e.foundation/e/backlog/-/issues/7873Quik from fdroid is not available in App Lounge2024-03-25T09:39:55ZBreweryQuik from fdroid is not available in App Loungehttps://f-droid.org/it/packages/dev.octoshrimpy.quik
is not available in App Loungehttps://f-droid.org/it/packages/dev.octoshrimpy.quik
is not available in App Loungehttps://gitlab.e.foundation/e/backlog/-/issues/7872Evway is not available in App Lounge2024-03-22T22:44:05ZBreweryEvway is not available in App LoungeeOS 1.20-t
[Evway](https://play.google.com/store/apps/details?id=com.route220.route220) from play store is not available in App LoungeeOS 1.20-t
[Evway](https://play.google.com/store/apps/details?id=com.route220.route220) from play store is not available in App Loungehttps://gitlab.e.foundation/e/backlog/-/issues/7870Periodic Alternating Screen Brightness Under Certain Indoor LED Lights on bey...2024-03-22T22:45:51ZŽroutíkPeriodic Alternating Screen Brightness Under Certain Indoor LED Lights on beyond2lte with /e/OS 1.19-s## Device Information
- **Device Model:** beyond2lte
- **/e/OS Version:** 1.19-s
## Summary
The screen brightness alternates periodically when the device is used indoors under specific LED light sources. This issue does not occur outdoo...## Device Information
- **Device Model:** beyond2lte
- **/e/OS Version:** 1.19-s
## Summary
The screen brightness alternates periodically when the device is used indoors under specific LED light sources. This issue does not occur outdoors or under traditional light bulb illumination.
## Steps to Reproduce
1. Turn on adaptive brightness.
2. Use the device indoors under the specific LED lighting conditions.
## Expected Results
The screen brightness should adjust smoothly and remain consistent based on the ambient light conditions without noticeable fluctuations.
## Actual Results
The screen brightness changes periodically, creating a flickering effect, specifically under certain LED light conditions indoors. This issue does not manifest outdoors or under traditional light bulb lighting.
## Frequency
This issue occurs consistently under the specified conditions.
## Additional Information
- The issue is specific to indoor conditions and certain LED light sources.
- No similar behavior is observed outdoors or under conventional lighting, suggesting a possible sensitivity or calibration issue with the light sensor and LED lighting frequencies.
## Workarounds
None found so far.https://gitlab.e.foundation/e/backlog/-/issues/7865Add a Voice over LTE indicator in the dialer2024-03-29T08:01:12ZMohammed Althaf ThayyilAdd a Voice over LTE indicator in the dialer- /e/ version: 1.22
- Device model(s): all
## Summary
Add a VoLTE indicator in the dialer in order to know that the user is making a VoLTE call.
## Description
**What is the current behavior?**
We don't know from the dialer which ki...- /e/ version: 1.22
- Device model(s): all
## Summary
Add a VoLTE indicator in the dialer in order to know that the user is making a VoLTE call.
## Description
**What is the current behavior?**
We don't know from the dialer which kind of call is performed. Sometime we have the HD indicator on some devices but it is displayed with the cellular data on or off.
**What is the improved behavior?**
The user is aware that the phone call is performed through VoLTE with a small indicator in the dialer (instead of the HD icon). The icon says 4G or LTE depending on the term used in the region the user lives.
![image](/uploads/2bfd634616362f8b6af0413ad0d3e169/image.png) ![image](/uploads/3e9c8fa0bda6376782926fbdc9d203c1/image.png)
**What does it bring?**
QA team will be happy to know this information instead of deduce it and this indicator is probably useful too for all of our users.
## Examples
<details><summary>Click to expand</summary>
| cell data on | cell data off |
| ------ | ------ |
| ![photo_2022-09-30_09-26-00](/uploads/b27874589c02da11594bb03e9c0e70e7/photo_2022-09-30_09-26-00.jpg) |![Screenshot_20220929-183333_Téléphone](/uploads/4f4e0227b29cce7337f5599c5333799b/Screenshot_20220929-183333_Téléphone.png) |
We have probably to use the [FEATURES_VOLTE](https://developer.android.com/reference/android/provider/CallLog.Calls.html#FEATURES_VOLTE) flag and having a VoLTE icon.
Here the source code ref about the [setShowHd](https://gitlab.e.foundation/e/os/android_packages_apps_Dialer/-/blob/v1-s/java/com/android/dialer/calldetails/CallDetailsEntryViewHolder.java#L140).
</details>
## Validation
The dialer have to display a VoLTE icon in the dialer if a VoLTE is available.
## Design
https://www.figma.com/file/B0ICdQKmT1aFsRoKVCUkhT/Launcher-icons?node-id=1126%3A16
cc @rhunault @AlexDuCens @aude @rhandros @nicofonk/e/OS v2.0-betahttps://gitlab.e.foundation/e/backlog/-/issues/7862Can't install e/OS on Samsung Galaxy A52 with adb2024-03-22T22:46:27ZIslam BahnasyCan't install e/OS on Samsung Galaxy A52 with adb- /e/ version:T
- Device model(s):Samsung Galaxy A52
- Developer mode enabled: yes
- Device rooted: no
## Summary
Can't flash e/os to the device using adb after the recovery has been flashed successfully.
## The problem
**Steps to r...- /e/ version:T
- Device model(s):Samsung Galaxy A52
- Developer mode enabled: yes
- Device rooted: no
## Summary
Can't flash e/os to the device using adb after the recovery has been flashed successfully.
## The problem
**Steps to reproduce**
Flash custom recovery
Try to flash e/os ROM using `adb sideload e-1.20-t-20240221382228-dev-a52q.zip`
**What is the current behavior?**
Installation is aborted after about 40%
On Linux I get `Total xfer: 1.00x`
On the phone I get:
`ERROR: this package requires Android 13 based firmware, Please upgrade firmware and retry!`
`ERROR: recovery: Error in /sideload/package.zip (status 1)`
`Install completed with status 1`
`Installation aborted`https://gitlab.e.foundation/e/backlog/-/issues/7858The WeChat app crash a few seconds after opening after /e/OS upgrade.2024-03-22T22:47:18ZHenrik HemrinThe WeChat app crash a few seconds after opening after /e/OS upgrade.- /e/ version: 1.20-r-20240221382013-stable-starlte (upgraded from 1.19-r-xxx)
- Device model(s): Samsung S9 SM-G960F/DS
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
The WeChat app crash a...- /e/ version: 1.20-r-20240221382013-stable-starlte (upgraded from 1.19-r-xxx)
- Device model(s): Samsung S9 SM-G960F/DS
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
The WeChat app crash a few seconds after opening after /e/OS upgrade.
## The problem
**Steps to reproduce**
After upgrade of /e/OS the app WeChat (WeChat 8.0.42.114) stopped working. When it is opened, it is frozen and crashes a few seconds after it was opened. After maybe five times, WeChat Safe mode screen opens with button to start its repair process, but same behaviour persist when WeChat is opened after the repair. I have done this multiple times. The app was installed from App Lounge.
Directly after upgrade of /e/OS was completed, I got a notification from App Lounge that WeChat wanted to install extra modules, but it could not because I was also notified I needed to sign in again to the App Lounge. After some troubles I managed to login again to App Lounge, but I am not aware of any extra WeChat module ever was installed.
Apparently I am not the only one with trouble, see the forum thread for this release, which has a couple of entries related to WeChat issues.
[e.foundation forum thread](https://community.e.foundation/t/feedback-for-v1-20/55758)
**What is the current behavior?**
The WeChat opens but is closed after a few seconds. After a couple of attempts, WeChat goes to Safe mode and try (but fails) to repair.
**What is the expected correct behavior?**
I should see the same screen on WeChat, but it should stay open and react when pushing on eg its buttons.
## Technical informations
**Relevant logs (`adb logcat`)**
No
**Relevant screenshots**
No
## Solutions
**Workaround**
Someone (in forum thread) has as a work around installed WeChat from the website, a version of the app that does not use Google services and is as I understand a mainland China version of the app. To install an uncontrolled app from mainland China instead of a controlled app from AppLounge app store is a work around that is very doubtful to use and not anything I consider to do. My workaround is to use an old iPhone for WeChat instead for time being until it works with /e/OS.
**Possible fixes**
No
<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/7856Being able to change one events color in an event series2024-03-20T07:54:38ZShenol MustafovBeing able to change one events color in an event series- /e/ version: all
- Device model(s): all
## Summary
When a recurring event is created, user wants to change the color of one of the events to indicate for example that it is cancelled. Currently this is not possible.
## Description
...- /e/ version: all
- Device model(s): all
## Summary
When a recurring event is created, user wants to change the color of one of the events to indicate for example that it is cancelled. Currently this is not possible.
## Description
**What is the current behavior?**
User has a lot of recurring appointments. If one of them is announced as canceled, he has to mark it in color, otherwise it is overlooked. Unfortunately, this is not possible with the Murena calendar. When user tries to save the one appointment in another calendar, the whole series is converted to the second calendar. Perhaps it would be possible to change the color of the individual appointments.
![image](/uploads/8199d106c8e556a80d3c95c7e0f47e3d/image.png)
**What is the improved behavior?**
be able to change the color
**What does it bring?**
usability
## Mock-ups
<Provide a mock-up of how it would look with the improvement>
## 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>
/label ~"type::Improvement"
<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/7854Notifications not issued when user is on Data Saver mode even if the app is w...2024-03-18T06:02:18ZAude MNotifications not issued when user is on Data Saver mode even if the app is whitelisted- /e/ version: any
- Device model(s): ~star2lte ~starlte ~dream2lte ~dreamlte ~FP4 ~avicii
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
<Summarize the bug encountered briefly ...- /e/ version: any
- Device model(s): ~star2lte ~starlte ~dream2lte ~dreamlte ~FP4 ~avicii
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
<Summarize the bug encountered briefly and precisely>
When `Data saver` is on, the user doesn't get some notifications until they open the app even if said app is whitelisted in the `Data saver` option.
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. install a third party messaging app like Signal or Telegram
2. set an account
3. Set `Data saver` to on
4. start exchanging messages with friends
**What is the current behavior?**
<What actually happens>
Sometimes the notification for new messages are not issued right away or until the user opens the app. Even if the user whitelist the app in the Data saver option, notifications are not issued.
It's not systematic with all these apps even on the same phone (for instance I have the problem with Signal but it seems to me I do not have it with Telegram)
**What is the expected correct behavior?**
<What you should see instead>
Notifications are issued right away when the app is whitelisted in the `Data saver` option
## 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>
<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/7852MJ PDF crashes2024-03-26T11:06:58ZTy SinoMJ PDF crashes- /e/ version: 1.20-s-20240220382012-stable-FP4 ; 1.21-t-dev-river ; 1.20-r-stable-dreamlte
- Developer mode enabled: no/yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
MJ PDF viewer crashes on a specific pdf file, w...- /e/ version: 1.20-s-20240220382012-stable-FP4 ; 1.21-t-dev-river ; 1.20-r-stable-dreamlte
- Developer mode enabled: no/yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
MJ PDF viewer crashes on a specific pdf file, where other viewers don't crash.
## The problem
**Steps to reproduce**
Open the [pdf file](https://arxiv.org/pdf/1706.04599.pdf).
Or this one: [Règlement-attribution-subvention-Ploudalmézeau.pdf](/uploads/09226e73620a8243c0f2e34f8e3e6a50/Règlement-attribution-subvention-Ploudalmézeau.pdf).
**What is the current behavior?**
The viewer crashes after about a second.
**What is the expected correct behavior?**
Viewing the PDF.
## Technical informations
**Relevant logs (`adb logcat`)**
[crash_MJPDF_20240318](/uploads/8fec6c24fd385ad878f5d41a7aac851b/crash_MJPDF_20240318)
## Solutions
**Workaround**
None, or use other app./e/OS v2.0-alphaAbhishek AggarwalMohammed Althaf ThayyilAbhishek Aggarwalhttps://gitlab.e.foundation/e/backlog/-/issues/7851New default shortcut in Browser: Murena.io2024-03-29T13:51:16ZRik ViergeverNew default shortcut in Browser: Murena.io## Summary
Add a new default shortcut in ~"/e/OS Browser" to the murena.io website
## Description
**What is the feature?**
Add a new default shortcut in ~"/e/OS Browser" to the murena.io website. Users who wish it can choose to inst...## Summary
Add a new default shortcut in ~"/e/OS Browser" to the murena.io website
## Description
**What is the feature?**
Add a new default shortcut in ~"/e/OS Browser" to the murena.io website. Users who wish it can choose to install it as a webapp from the browser's options. Users will be automatically logged into based on their /e/OS user login after the implementation of https://gitlab.e.foundation/e/backlog/-/issues/6287.
**Who will use this new feature?**
Everyone who uses the Murena.io website from the mobile
**Why these users would like to use this feature?**
It will be easier for everyone to access their personal cloud
## Examples
<Give the example of what users will be able to accomplish with the feature>
## Reflection
**Mockups**
**Diagrams**
## Validation
<List test case that will be run to validate that the issue is working as expected>
/label ~"type::Feature Proposal"
<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.>/e/OS v2.0-betahttps://gitlab.e.foundation/e/backlog/-/issues/7850Make the Murena.io Bookmarks and the bookmarks in the /e/OS default browser s...2024-03-16T00:02:51ZRik ViergeverMake the Murena.io Bookmarks and the bookmarks in the /e/OS default browser sync as part of the general /e/OS sync## Summary
Make the Murena.io Bookmarks and the bookmarks in the /e/OS default browser sync as part of the general /e/OS sync
## Description
**What is the feature?**
Make the Murena.io Bookmarks and the bookmarks in the /e/OS default...## Summary
Make the Murena.io Bookmarks and the bookmarks in the /e/OS default browser sync as part of the general /e/OS sync
## Description
**What is the feature?**
Make the Murena.io Bookmarks and the bookmarks in the /e/OS default browser sync as part of the general /e/OS sync
**Who will use this new feature?**
All users that make use of the Bookmarks function
**Why these users would like to use this feature?**
It is nice to have your bookmarks on both PC and mobile
## Examples
view their favorite websites from PC on mobile also or vice versa
## Reflection
**Mockups**
**Diagrams**
## Validation
<List test case that will be run to validate that the issue is working as expected>
/label ~"type::Feature Proposal"
<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/7849add 4 default Murena bookmarks to Murena.io Bookmarks App2024-03-14T16:16:15ZRik Viergeveradd 4 default Murena bookmarks to Murena.io Bookmarks App- /e/ version: all
- Device model(s): all
## Summary
Add 4 default bookmarks to the Murena.io bookmarks for every new Murena.io user:
* murena.io
* murena.com
* e.foundation
* spot.ecloud.global
## Description
**What is the current ...- /e/ version: all
- Device model(s): all
## Summary
Add 4 default bookmarks to the Murena.io bookmarks for every new Murena.io user:
* murena.io
* murena.com
* e.foundation
* spot.ecloud.global
## Description
**What is the current behavior?**
**there are no default bookmarks in the ****Murena.io**** bookmarks**
**What is the improved behavior?**
**there are 4 default bookmarks in the Murena.io bookmarks**
**What does it bring?**
**easy for users to easily access their Murena websites**
## Mock-ups
## Examples
## Validationhttps://gitlab.e.foundation/e/backlog/-/issues/7848Add 4 default bookmarks to the /e/OS browser2024-03-14T16:10:14ZRik ViergeverAdd 4 default bookmarks to the /e/OS browser- /e/ version: all
- Device model(s): all
## Summary
Add 4 default bookmarks to the /e/OS browser:
* murena.io
* murena.com
* e.foundation
* spot.murena.io
## Description
**What is the current behavior?**
**there are no default b...- /e/ version: all
- Device model(s): all
## Summary
Add 4 default bookmarks to the /e/OS browser:
* murena.io
* murena.com
* e.foundation
* spot.murena.io
## Description
**What is the current behavior?**
**there are no default bookmarks in the /e/OS browser**
**What is the improved behavior?**
**there are 4 default bookmarks in the /e/OS browser**
**What does it bring?**
**easy for users to easily access their Murena websites**
## Mock-ups
## Examples
## Validation