Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2023-12-19T17:16:00Zhttps://gitlab.e.foundation/e/backlog/-/issues/6613Add calendar side view in mail application in murena.io2023-12-19T17:16:00ZAlexis NoetingerAdd calendar side view in mail application in murena.io## Summary
Add a calendar side view in murena.io when checking emails
## Description
**What is the feature?**
Today, each murena.io service is not visible simultaneously, limiting the usability. As calendar and emails are essential t...## Summary
Add a calendar side view in murena.io when checking emails
## Description
**What is the feature?**
Today, each murena.io service is not visible simultaneously, limiting the usability. As calendar and emails are essential to manage one's actions, it would be useful to be able to see one's calendar when browsing emails, without having to open a new window.
The side view should enable adding a new meeting to the agenda, browse days, move a meeting by moving the block.
**Who will use this new feature?**
Everyone using murena.io mail and calendar
**Why these users would like to use this feature?**
No need to open multiple windows to see one's calendar
## Examples
Stay ahead of their schedule and not miss an important appointment
Protonmail
![Screenshot_2023-01-29_at_11-40-01_Proton_Mail](/uploads/e9a4ff08e5d9f074d28d2b6adf96968b/Screenshot_2023-01-29_at_11-40-01_Proton_Mail.png)
Gmail
![Screenshot_2023-01-29_at_11-44-54_Inbox_-_anoetinger_gmail.com_-_Gmail](/uploads/20af41b5b9e78fef5d91f94d6a0a74a5/Screenshot_2023-01-29_at_11-44-54_Inbox_-_anoetinger_gmail.com_-_Gmail.png)
## 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.>
@aude.m @arnauvp FYI @gael @rhandroshttps://gitlab.e.foundation/e/backlog/-/issues/6430Reminder notification reappear several times after the first one2024-03-18T08:59:21ZAude MReminder notification reappear several times after the first one- /e/ version: 1.7-beta.2 (but happened way before)
- Device model(s): any
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
<Summarize the bug encountered briefly and precisely>
When I schedu...- /e/ version: 1.7-beta.2 (but happened way before)
- Device model(s): any
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
<Summarize the bug encountered briefly and precisely>
When I schedule an event in my calendar and set a reminder, after the reminder has been triggered at the right moment, it is regularly triggered again until I swipe the event.
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. schedule an event with a notification reminder
2. wait for the reminder to be triggered a first time
3. keep the notification and wait
**What is the current behavior?**
<What actually happens>
After a while the reminder is triggered anew, and then another time, and again, and again until it is swiped.
**What is the expected correct behavior?**
<What you should see instead>
The event should stay in the notification bar as long as it's not swiped but shouldn't trigger any new notification display or sound.
## 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.>Fahim Masud ChoudhuryFahim Masud Choudhuryhttps://gitlab.e.foundation/e/backlog/-/issues/5627Outlook Android: can't connect to my e.email account2023-11-30T17:33:49ZAlexis NoetingerOutlook Android: can't connect to my e.email account- /e/ version: 1.0
- Device model(s): ~star2lte
- Device rooted: no
## Summary
Can't add an e.email account to Outlook Android app (4.2220.1)
## The problem
**Steps to reproduce**
- Install Outlook App, add auto config => KO
- add ...- /e/ version: 1.0
- Device model(s): ~star2lte
- Device rooted: no
## Summary
Can't add an e.email account to Outlook Android app (4.2220.1)
## The problem
**Steps to reproduce**
- Install Outlook App, add auto config => KO
- add account using manual configuration following [this guide](https://e.foundation/email-configuration/) => KO
**What is the current behavior?**
Upon adding manual settings, pop up in app saying 'Login issue','your mail server certificate is invalid. Would you like to log anyway?'
**What is the expected correct behavior?**
The account creation should work without issues or pop-up
## 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>Florent VINCENTFlorent VINCENThttps://gitlab.e.foundation/e/backlog/-/issues/5588myPayLife(at.paylife.sesam): app sees device as rooted2024-03-28T09:10:29ZAlexis NoetingermyPayLife(at.paylife.sesam): app sees device as rooted- <details><summary>Third party app icon</summary>![icon](/uploads/540621abe9bbdd39b4bc3f759901cb11/icon.png)</details>
- /e/ version: /e/OS 1.0-20220526188860
- Device model(s): ~FP4
- Device rooted: no
## Summary
MyPayLife app sees ...- <details><summary>Third party app icon</summary>![icon](/uploads/540621abe9bbdd39b4bc3f759901cb11/icon.png)</details>
- /e/ version: /e/OS 1.0-20220526188860
- Device model(s): ~FP4
- Device rooted: no
## Summary
MyPayLife app sees FP4 V1 as rooted
## The problem
**Steps to reproduce**
- install the MyPayLife App 3.4.24
- Following instructions to setup 3D Secure (see https://www.paylife.at/linkableblob/paylife/477676/944dab9eb1c71d86eb451fd0da96a625/3ds-registrierung-how-to-data.pdf)
**What is the current behavior?**
after entering the App Code the app stops the process and declares the phone is rooted:
> Error during registration for the 3D Secure procedure
>
> The registration could not be carried out for security reasons because your mobile device is rooted.
> The changes were not applied.
**What is the expected correct behavior?**
the process should go all the way and enable 3DS registration
## Technical informations
Helpdesk 997193
Helpdesk 9910056
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>https://gitlab.e.foundation/e/backlog/-/issues/5225App Lounge Allow to sort apps by Name, Note or Confidentiality2023-11-15T16:06:05ZCodainApp Lounge Allow to sort apps by Name, Note or Confidentiality## Summary
When listing applications (in Categories or when Searching) applications are sorted in an unknown order (popularity?), with no ability to tweak it.
## Description
**What is the feature?**
Have a button to change sorting or...## Summary
When listing applications (in Categories or when Searching) applications are sorted in an unknown order (popularity?), with no ability to tweak it.
## Description
**What is the feature?**
Have a button to change sorting order on an app list.
**Who will use this new feature?**
Anyone who is not looking for a specific app but want to discover new applications.
**Why these users would like to use this feature?**
Sorting by Confidentiality would allow to highlight applications with a high mark by putting them on top of the list.
## Examples
When clicking on the button, the user is given the opportunity to select a sorting criteria and an ascending or descending order among:
- Default (which is popularity?)
- Confidentiality: Sort by Confidentiality then by Note then by Name
- Name: Sort by name
- Note: Sort by note then Confidentiality then Name
## Reflection
**Mockups**
**Diagrams**
## Validation
## Checklist
- [ ] Define criteria proposed to user
- [ ] Implement the featurehttps://gitlab.e.foundation/e/backlog/-/issues/5797"Enable TOTP" checkbox gets ticked even if its not enabled successfully.2024-02-07T10:13:03ZJatin Garg"Enable TOTP" checkbox gets ticked even if its not enabled successfully.ecloud.global / murena.io
## Summary
Enable TOTP checkbox gets check marked even if we cancel enabling it. And hitting the ticked checkbox again results in endless loop. Reloading the page in any case shows the correct unchecked behavi...ecloud.global / murena.io
## Summary
Enable TOTP checkbox gets check marked even if we cancel enabling it. And hitting the ticked checkbox again results in endless loop. Reloading the page in any case shows the correct unchecked behavior.
## The problem
- login to murena.io / ecloud.global
- Click Avatar on the top right and go to `Settings` >> `Security`
- Under Two Factor Authentication, Hit the enable TOTP checkbox
- Click cross on the `Authentication required` popup to cancel enabling the checkbox
- User receives Could not enable TOTP notification but the checkbox is shown as ticked
- Now Try unchecking the checkbox which will result it in endless loading.
- Now reload the page so it shows the box unchecked as desired.
<How one can reproduce the issue>
**What is the current behavior?**
User receives Could not enable TOTP notification but the checkbox is shown as ticked, until the next reload of the page.
<What actually happens>
**What is the expected correct behavior?**
If Enabling TOTP fails the checkbox should remain unchecked. And ticked only when TOTP is successfully enabled.
<What you should see instead>
**Relevant screenshots**
![Screenshot_from_2022-07-12_15-06-42](/uploads/35853a966d0da0c25565b74213473906/Screenshot_from_2022-07-12_15-06-42.png)
/cc @arnauvp
<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.>Ronak Patelronak.patel@e.emailRonak Patelronak.patel@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/5593Krankenkassen(de.barmergek.serviceapp): see device as rooted2023-11-17T08:14:30ZAlexis NoetingerKrankenkassen(de.barmergek.serviceapp): see device as rooted- <details><summary>Third party app icon</summary>![icon](/uploads/749dd885f850867290992ca42a5445e1/icon.png)</details>
- /e/ version: 1.0
- Device model(s): ~FP4
- Device rooted: no
## Summary
<Summarize the bug encountered briefly a...- <details><summary>Third party app icon</summary>![icon](/uploads/749dd885f850867290992ca42a5445e1/icon.png)</details>
- /e/ version: 1.0
- Device model(s): ~FP4
- Device rooted: no
## Summary
<Summarize the bug encountered briefly and precisely>
## The problem
**Steps to reproduce**
Krankenkassen-App sees FP4 V1 as rooted
**What is the current behavior?**
The app can be installed but once the user tries to log in, it fails.
**What is the expected correct behavior?**
The login should work flawlessly
## Technical informations
de.barmergek.serviceapp version 4.3.7
Helpdesk ticket 998365
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>https://gitlab.e.foundation/e/backlog/-/issues/5212App Lounge Changelog for updates missing2024-01-22T02:12:10ZbegeApp Lounge Changelog for updates missing- /e/ version: 0.23-q
- Device model(s): FP3
- Device rooted: yes
## Summary
Changelog for updates is missing
## The problem
**Steps to reproduce**
Show detail page of updatable app
**What is the current behavior?**
No changelog i...- /e/ version: 0.23-q
- Device model(s): FP3
- Device rooted: yes
## Summary
Changelog for updates is missing
## The problem
**Steps to reproduce**
Show detail page of updatable app
**What is the current behavior?**
No changelog is displayed even if it is available in F-Droid, Aurora Store or Play Store
**What is the expected correct behavior?**
Show changelog
## 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>
~"app lounge"https://gitlab.e.foundation/e/backlog/-/issues/791Make blisslauncher usable as an "assistant" app (to act as a quicklauncher)2024-03-05T06:18:54ZthiloMake blisslauncher usable as an "assistant" app (to act as a quicklauncher)Hi there Amit,
As discussed in telegram here is my feature request:
Please consider to make blisslauncher register as an assistant app. (like kiss launcher for instance)
It should be selectable (and maybe seleceted by default here):
...Hi there Amit,
As discussed in telegram here is my feature request:
Please consider to make blisslauncher register as an assistant app. (like kiss launcher for instance)
It should be selectable (and maybe seleceted by default here):
![Screenshot_20200102-211151_Settings](/uploads/dc1f28a1533e3b6a4893a7b34f45a50e/Screenshot_20200102-211151_Settings.png)
I imagine that it would be beneficial if triggering it as an assistant would open up the search thingy (just like a swipe-down does on the launcher screens). This way it can be opened (as a quick launcher) even when another app is in foreground. It saves the necessity to click once (or twice when foreground app was launched from a folder) to return to the home screen before one can perform the swipe-down. Instead one would just long press the home button to launch assistant / Blisslauncher search.
Especially because bliss displays all app with no way to remove them from the pages (while keeping it installed) and has no app drawer one needs to rely on third party quicklaunchers to achieve a reasonable "app find and launch" performance (or return to homescreen first). Would be great to use bliss directly without the need for yet another app. :)
Thanks!https://gitlab.e.foundation/e/backlog/-/issues/925Deletion of paused system updated is not intuitive2023-10-06T15:19:40ZMarkusDeletion of paused system updated is not intuitiveIn order to delete a paused update the user has to long-press on the paused update, which is not very intuitive.
To trigger this issue:
1. Start to download a system update
2. Pause the download before it is finished
3. Wait until the n...In order to delete a paused update the user has to long-press on the paused update, which is not very intuitive.
To trigger this issue:
1. Start to download a system update
2. Pause the download before it is finished
3. Wait until the next system update is available
4. Download and install the new system update
![Screenshot_20181013-085731](/uploads/68c142bd206116926d89a57b05bb6ed9/Screenshot_20181013-085731.png)
Pressing the "Resume" button just opens a notification:
![Screenshot_20181013-092306](/uploads/7b29e59fdf51306d5156b92bcd0e6cc5/Screenshot_20181013-092306.png)
When a newer update is installed I would expect that the "Resume" button is replaced by a "Delete" button, since the "Resume" button has no functionality in this case.https://gitlab.e.foundation/e/backlog/-/issues/7888New default shortcut in Browser: Murena.com2024-03-28T08:37:02ZAude 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.>https://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/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`