Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2024-02-29T11:27:14Zhttps://gitlab.e.foundation/e/backlog/-/issues/7811Integrated PGP for Murena email on murena.io and /e/OS2024-02-29T11:27:14ZRik ViergeverIntegrated PGP for Murena email on murena.io and /e/OS## Summary
Feature request for integrating PGP better into our email functionalities in the cloud and in /e/OS, so that:
* every email user automatically when they sign up gets a Pgp key (automatically in a non-visible way, it just hap...## Summary
Feature request for integrating PGP better into our email functionalities in the cloud and in /e/OS, so that:
* every email user automatically when they sign up gets a Pgp key (automatically in a non-visible way, it just happens in the background, visible in the Settings of course, but if you don't want to look it up you don't have to, similar to Proton)
* use Autocrypt to then ensure that emails between Murena.io members (and other PGP users) are automatically encrypted?
* Allow people to view, delete and change their PGP key in the Settings (eg when people want to upload their own) or not use it at all
This would also be a real USP for B2B: it would automatically enable encryption of emails between all employees.
## Description
**What is the feature?**
Integrated PGP for Murena email on murena.io and /e/OS
**Who will use this new feature?**
Everyone, both B2C and B2B
**Why these users would like to use this feature?**
Automatic better privacy and security without having to burden yourself with the complicated PGP stuff
## Examples
## Reflection
**Mockups**
**Diagrams**
## Validationhttps://gitlab.e.foundation/e/backlog/-/issues/6715Switch base of /e/OS Tasks2024-02-29T10:23:28ZMichael BaumgartnerSwitch base of /e/OS Tasks- /e/ version: 1.8.1-s-20230203257059-stable-FP4
- Device model(s): Fairphone 4
## Summary
[OpenTasks](https://github.com/dmfs/opentasks), the current base of the /e/OS Tasks app, seemed to be not longer maintained.
## Description
*...- /e/ version: 1.8.1-s-20230203257059-stable-FP4
- Device model(s): Fairphone 4
## Summary
[OpenTasks](https://github.com/dmfs/opentasks), the current base of the /e/OS Tasks app, seemed to be not longer maintained.
## Description
**What is the current behavior?**
The actual /e/OS Tasks app maybe wouldn't get any updates (bugfixes, improments, ...) from the upstream project any more.
**What is the improved behavior?**
There should be an switch to another opensource tasks app, which is maintained.
Suggestion (with openTasks for comparison) - feel free to add any further suggestion and functional requirements
| name | repo link | calDAV | recurrence |
| ---- | --------- | ------ | ---------- |
| OpenTasks | https://github.com/dmfs/opentasks | :white_check_mark: (via DAVx5) | :x: |
| tasks | https://github.com/tasks/tasks | :white_check_mark: (via DAVx5 and standalone) | :white_check_mark: (not with DAVx5) |
| jtx Board | https://github.com/TechbeeAT/jtxBoard | :white_check_mark: (via DAVx5) | :white_check_mark: |
**What does it bring?**
An maintained upstream project have many benefits. For example security fixes and new features.
## Mock-ups
<Provide a mock-up of how it would look with the improvement>
## Examples
The support of recurrence tasks would be an direct benefit for all users.
## Validation
<List test case that will be run to validate that the issue is working as expected>https://gitlab.e.foundation/e/backlog/-/issues/6714WebCalenderManager can find hostname or can't connect to host2024-02-29T10:19:40ZMichael BaumgartnerWebCalenderManager can find hostname or can't connect to host- /e/ version: 1.8.1-s-20230203257059-stable-FP4
- Device model(s): Fairphone 4
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
ICS calenders can't be added with the WebCalenderManager. There...- /e/ version: 1.8.1-s-20230203257059-stable-FP4
- Device model(s): Fairphone 4
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
ICS calenders can't be added with the WebCalenderManager. There is always an error.
## The problem
**Steps to reproduce**
1. Start the WebCalenderManager app (for example via settings - accounts - add account - Web Calendar Manager)
2. Enter an ICS adress (example of an free accessable adress with german holidays: http://de-kalender.de/downloads/feiertage_deutschland_2022.ics)
3. Go an step further with the arrow in the upper right corner
**What is the current behavior?**
There appears an error message.
With de-kalender.de adress it is this one:
<details><summary>message with stack trace</summary>
failed to connect to de-kalender.de/91.250.100.88 (port 80) from /192.168.178.102 (port 40792) after 10000ms
java.net.SocketTimeoutException: failed to connect to de-kalender.de/91.250.100.88 (port 80) from /192.168.178.102 (port 40792) after 10000ms
at libcore.io.IoBridge.connectErrno(IoBridge.java:236)
at libcore.io.IoBridge.connect(IoBridge.java:180)
at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:142)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:390)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
at java.net.Socket.connect(Socket.java:621)
at okhttp3.internal.platform.Platform.connectSocket(Platform.kt:128)
at okhttp3.internal.connection.ConnectPlan.connectSocket(ConnectPlan.kt:254)
at okhttp3.internal.connection.ConnectPlan.connectTcp(ConnectPlan.kt:128)
at okhttp3.internal.connection.SequentialExchangeFinder.find(SequentialExchangeFinder.kt:33)
at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:267)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:84)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:65)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:205)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:533)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:920)
</details>
With the address for the bavarian holidays from schulferien.org there is error, which I also seen with one private adress. (Url from schulferien.org is only available after solving an chapter, so I am not sure if I should post the link here directly.)
<details><summary>message with stacktrace</summary>
Unable to resolve host "www.schulferien.org": No address associated with hostname
java.net.UnknownHostException: Unable to resolve host "www.schulferien.org": No address associated with hostname
at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:156)
at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:103)
at java.net.InetAddress.getAllByName(InetAddress.java:1152)
at okhttp3.Dns$Companion$DnsSystem.lookup(Dns.kt:49)
at okhttp3.internal.connection.RouteSelector.resetNextInetSocketAddress(RouteSelector.kt:169)
at okhttp3.internal.connection.RouteSelector.nextProxy(RouteSelector.kt:132)
at okhttp3.internal.connection.RouteSelector.next(RouteSelector.kt:74)
at okhttp3.internal.connection.RealRoutePlanner.planConnect(RealRoutePlanner.kt:147)
at okhttp3.internal.connection.RealRoutePlanner.plan(RealRoutePlanner.kt:67)
at okhttp3.internal.connection.SequentialExchangeFinder.find(SequentialExchangeFinder.kt:30)
at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:267)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:84)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:65)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:205)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:533)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:920)
Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
at libcore.io.Linux.android_getaddrinfo(Native Method)
at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:136)
at libcore.io.BlockGuardOs.android_getaddrinfo(BlockGuardOs.java:221)
at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:136)
at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:135)
... 23 more
</details>
**What is the expected correct behavior?**
It should can process this addresses. The native ICSx⁵ app can handle this adresses without errors on the same device. The native app only have sometimes errors, that the host can't be found for an update, but that only appears sporadically.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
Use the native ICSx⁵ app is the actual workaround for me.
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
**Labels**
~"type::Bug" ~"/e/OS Calendar"
(The label command seems not to work for me, to add the labels to the ticket.)
<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/7603Brightness is temporarily set to max after using the fingerprint sensor2024-02-28T21:48:21ZNoah GilBrightness is temporarily set to max after using the fingerprint sensor- /e/ version: 1.17-t (dev)
- Device model(s): OnePlus 7T (hotdogb)
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: no
## Summary
Whenever the fingerprint sensor usage is prompted, after it is dismissed (w...- /e/ version: 1.17-t (dev)
- Device model(s): OnePlus 7T (hotdogb)
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: no
## Summary
Whenever the fingerprint sensor usage is prompted, after it is dismissed (whether or not you actually scan your fingerprint), the display brightness is set to maximum. The brightness setting does not appear to be changed, however; instead, it is only visually set to max. Changing the brightness setting in any way resolves this temporary increase.
## The problem
1. Get the fingerprint sensor prompt to appear (e.g. when unlocking the phone)
2. Dismiss the fingerprint sensor (e.g. unlock the phone with your fingerprint)
**What is the current behavior?**
The display is at maximum brightness.
**What is the expected correct behavior?**
The display is at the configured brightness.
## Technical informations
**Relevant logs (`adb logcat`)**
I filtered the logcat output for brightness or biometrics related entries. The actions I took that generated these logs are as follows:
0. Start with display off and phone locked
1. Press power button to turn on display
2. Put finger on the fingerprint scanner
3. Phone unlocks
4. Drag down the notification shade and set the brightness
```
--------- beginning of system
12-05 14:35:23.106 1761 1842 V DisplayPowerController[0]: Brightness [0.040225886] reason changing to: 'manual', previous reason: 'screen_off'.
12-05 14:35:23.106 1761 1842 I DisplayPowerController[0]: BrightnessEvent: disp=0, physDisp=local:4630946883826275713, brt=0.040225886, initBrt=0.0, rcmdBrt=NaN, preBrt=NaN, lux=0.0, preLux=0.0, hbmMax=1.0, hbmMode=off, rbcStrength=84, powerFactor=1.0, thrmMax=1.0, wasShortTermModelActive=false, flags=, reason=manual, autoBrightness=false
12-05 14:35:23.106 1761 1842 I DisplayPowerController[0]: BrightnessEvent: disp=0, physDisp=local:4630946883826275713, brt=0.040225886, initBrt=0.040225886, rcmdBrt=NaN, preBrt=NaN, lux=0.0, preLux=0.0, hbmMax=1.0, hbmMode=off, rbcStrength=84, powerFactor=1.0, thrmMax=1.0, wasShortTermModelActive=false, flags=, reason=manual, autoBrightness=false
12-05 14:35:23.199 1761 1842 I DisplayPowerController[0]: BrightnessEvent: disp=0, physDisp=local:4630946883826275713, brt=0.040225886, initBrt=0.040225886, rcmdBrt=NaN, preBrt=NaN, lux=0.0, preLux=0.0, hbmMax=1.0, hbmMode=off, rbcStrength=84, powerFactor=1.0, thrmMax=1.0, wasShortTermModelActive=false, flags=, reason=manual, autoBrightness=false
12-05 14:35:23.288 1761 1842 I DisplayPowerController[0]: BrightnessEvent: disp=0, physDisp=local:4630946883826275713, brt=0.040225886, initBrt=0.040225886, rcmdBrt=NaN, preBrt=NaN, lux=0.0, preLux=0.0, hbmMax=1.0, hbmMode=off, rbcStrength=84, powerFactor=1.0, thrmMax=1.0, wasShortTermModelActive=false, flags=, reason=manual, autoBrightness=false
--------- beginning of kernel
12-05 14:35:24.571 539 539 E : (3)[539:crtc_commit:139][20231205_14:35:24.569174]@3 dsi_cmd hbm_brightness_off brightness 91
12-05 14:35:24.591 539 539 E : (3)[539:crtc_commit:139][20231205_14:35:24.581557]@3 dsi_cmd hbm_brightness_off brightness 91
12-05 14:35:24.600 1761 1761 V Biometrics/AuthenticationClient: onAuthenticated(true), ID:765233471, Owner: com.android.systemui, isBP: false, listener: com.android.server.biometrics.sensors.ClientMonitorCallbackConverter@acaaec4, requireConfirmation: false, user: 0, clientMonitor: {[572] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintAuthenticationClient, proto=3, owner=com.android.systemui, cookie=0, requestId=251, userId=0}
12-05 14:35:24.601 1761 1761 D BaseClientMonitor: marking operation as done: {[572] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintAuthenticationClient, proto=3, owner=com.android.systemui, cookie=0, requestId=251, userId=0}
12-05 14:35:24.605 1761 1761 D BiometricStateCallback: Client finished, state updated to 0, client {[572] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintAuthenticationClient, proto=3, owner=com.android.systemui, cookie=0, requestId=251, userId=0}
12-05 14:35:24.605 1761 1761 D BiometricSchedulerOperation: [Finished / destroy]: {[572] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintAuthenticationClient, proto=3, owner=com.android.systemui, cookie=0, requestId=251, userId=0}
12-05 14:35:24.611 1761 1761 D BiometricScheduler/Fingerprint21: [Finishing] {[572] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintAuthenticationClient, proto=3, owner=com.android.systemui, cookie=0, requestId=251, userId=0}, success: true
12-05 14:35:24.611 1761 1761 D BiometricCoexCoordinator: removeAuthenticationClient(Udfps), client: {[572] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintAuthenticationClient, proto=3, owner=com.android.systemui, cookie=0, requestId=251, userId=0}
12-05 14:35:24.669 724 16908 I keystore2: keystore2::super_key: In try_unlock_user_with_biometric: Successfully unlocked with biometric
12-05 14:35:27.082 1761 1842 V DisplayPowerController[0]: Brightness [0.040225886] reason changing to: 'temporary', previous reason: 'manual'.
12-05 14:35:27.082 1761 1842 I DisplayPowerController[0]: BrightnessEvent: disp=0, physDisp=local:4630946883826275713, brt=0.040225886, initBrt=0.040225886, rcmdBrt=NaN, preBrt=NaN, lux=0.0, preLux=0.0, hbmMax=1.0, hbmMode=off, rbcStrength=84, powerFactor=1.0, thrmMax=1.0, wasShortTermModelActive=false, flags=, reason=temporary, autoBrightness=false
12-05 14:35:27.087 1761 1842 V DisplayPowerController[0]: Brightness [0.04858939] reason changing to: 'manual', previous reason: 'temporary'.
12-05 14:35:27.087 1761 1842 I DisplayPowerController[0]: BrightnessEvent: disp=0, physDisp=local:4630946883826275713, brt=0.04858939(user_set), initBrt=0.040225886, rcmdBrt=NaN, preBrt=NaN, lux=0.0, preLux=0.0, hbmMax=1.0, hbmMode=off, rbcStrength=84, powerFactor=1.0, thrmMax=1.0, wasShortTermModelActive=false, flags=user_set , reason=manual, autoBrightness=false
12-05 14:35:27.088 1761 1761 I BrightnessSynchronizer: [2446] New Update 0.04858939(f) set brightness values: 13(i)
```
**Relevant screenshots**
Not applicable
## Solutions
**Workaround**
Simply changing the brightness in any way fixes the brightness to be back to what is configured.
Another solution I found that is tailored for unlocking the phone is to use the enable the setting "Long press on fingerprint sensor to unlock phone". When the display is off, and you unlock the phone by placing your finger on the sensor, the phone will unlock, very briefly flash the display at max brightness, and then revert to the configured brightness value. This does not resolve using the fingerprint sensor for other usages, such as authenticating in an application.
**Possible fixes**
I don't have any familiarity with the OS code, so I am unable to suggest a solution.
<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/7542All mail notifications are doubled2024-02-28T19:59:36ZLorenzo PistoneAll mail notifications are doubled- /e/ version: 1.17-s-20231109350748-stable-emerald
- Device model(s): Teracube 2e emerald
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
All notifications for emails appear twice. See scre...- /e/ version: 1.17-s-20231109350748-stable-emerald
- Device model(s): Teracube 2e emerald
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
All notifications for emails appear twice. See screenshot. Vibration signal seems to be duplicated as well.
## The problem
**Steps to reproduce**
Configure a gmail account via OAuth, then receive any email.
**All versions since at least 1.15 are affected.**
**Relevant screenshots**
![photo_2023-11-20_14-11-18](/uploads/b7e687d9fbbb70533ec5754f75528e8a/photo_2023-11-20_14-11-18.jpg)https://gitlab.e.foundation/e/backlog/-/issues/6802Problem to open Memo / Notes2024-02-28T19:52:16ZFair FProblem to open Memo / Notes- /e/ version:1.9
- Device model(s): fairphone
- Developer mode enabled:don't know
- Device rooted: yes
- Trackers blocker enabled: yes
## Summary
<i can't open my app Notes (in french) probably Memo in english)
## The problem
**Step...- /e/ version:1.9
- Device model(s): fairphone
- Developer mode enabled:don't know
- Device rooted: yes
- Trackers blocker enabled: yes
## Summary
<i can't open my app Notes (in french) probably Memo in english)
## The problem
**Steps to reproduce**
You try to open an app on your fairphone and there's a long message error that is apparearing after you had the choice to choose your account (error message below)
## Technical informations
**Relevant logs (`adb logcat`)**
App Version: 3.7.1
App Version Code: 3007001
App Flavor: ACCOUNT_MANAGER
Files App Version Code: 402060000
---
OS Version: 4.9.337-perf+(eng.root.20230310.165932)
OS API Level: 32
Device: FP3
Manufacturer: Fairphone
Model (and Product): FP3 (lineage_FP3)
---
com.nextcloud.android.sso.exceptions.NextcloudHttpRequestFailedException: La requête HTTP a échoué avec le statut HTTP :301
at com.nextcloud.android.sso.api.AidlNetworkRequest.performNetworkRequestV2(AidlNetworkRequest.java:188)
at com.nextcloud.android.sso.api.NextcloudAPI.performNetworkRequestV2(NextcloudAPI.java:159)
at com.nextcloud.android.sso.api.NextcloudAPI.lambda$performRequestObservableV2$0$com-nextcloud-android-sso-api-NextcloudAPI(NextcloudAPI.java:113)
at com.nextcloud.android.sso.api.NextcloudAPI$$ExternalSyntheticLambda0.subscribe(Unknown Source:6)
at io.reactivex.internal.operators.observable.ObservableFromPublisher.subscribeActual(ObservableFromPublisher.java:31)
at io.reactivex.Observable.subscribe(Observable.java:12284)
at io.reactivex.internal.operators.observable.ObservableSingleMaybe.subscribeActual(ObservableSingleMaybe.java:31)
at io.reactivex.Maybe.subscribe(Maybe.java:4290)
at io.reactivex.Maybe.blockingGet(Maybe.java:2320)
at io.reactivex.Observable.blockingSingle(Observable.java:5381)
at it.niedermann.owncloud.notes.persistence.CapabilitiesClient.getCapabilities(CapabilitiesClient.java:32)
at it.niedermann.owncloud.notes.importaccount.ImportAccountActivity.lambda$onActivityResult$5$it-niedermann-owncloud-notes-importaccount-ImportAccountActivity(ImportAccountActivity.java:108)
at it.niedermann.owncloud.notes.importaccount.ImportAccountActivity$$ExternalSyntheticLambda2.run(Unknown Source:4)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:920)
Caused by: java.lang.IllegalStateException: <html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
at com.nextcloud.android.sso.InputStreamBinder.processRequestV2(InputStreamBinder.java:246)
at com.nextcloud.android.sso.InputStreamBinder.performNextcloudRequestAndBodyStreamV2(InputStreamBinder.java:27)
at com.nextcloud.android.sso.InputStreamBinder.performNextcloudRequestV2(InputStreamBinder.java:2)
at com.nextcloud.android.sso.aidl.IInputStreamService$Stub.onTransact(IInputStreamService.java:43)
at android.os.Binder.execTransactInternal(Binder.java:1179)
at android.os.Binder.execTransact(Binder.java:1143)
```
<Screenshots of the problem>
## Solutions
?
**Possible fixes**
App Memo App Notes not openinghttps://gitlab.e.foundation/e/backlog/-/issues/7452tethering USB no longer works after OTA update to e-1.16-t on Samsung a52q2024-02-28T19:52:07ZBrewerytethering USB no longer works after OTA update to e-1.16-t on Samsung a52q- /e/ version: e-1.16-t-20231018342574-dev-a52q
- Device model(s): a52q
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
tethering USB no longer works after OTA update to e-1.16-t on Samsung a52, either ...- /e/ version: e-1.16-t-20231018342574-dev-a52q
- Device model(s): a52q
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
tethering USB no longer works after OTA update to e-1.16-t on Samsung a52, either from changing default mode in developer's option or doing it manually in the settings
## Technical informations
**Relevant logs (`adb logcat`)**
```
10-25 16:48:03.453 E/Tethering(1975): ERROR getIOffloadConfig error java.util.NoSuchElementException
10-25 16:48:03.453 E/Tethering(1975): [OffloadHardwareInterface] ERROR Could not find IOffloadConfig service
```
[logcat.txt](/uploads/98645bd9186cbb1d256ff1eae488c9a6/logcat.txt)
<To get the feature working or at least to make the device usable>
<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/6807Wrong GPS location reported by apps2024-02-28T19:51:41ZShenol MustafovWrong GPS location reported by apps- /e/ version: 1.19
- Device model(s): FP3, FP4, Murena One
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: no
## Summary
Apps installed on Fairphone 3 report wrong location. Apps like Maps, Google Maps etc...- /e/ version: 1.19
- Device model(s): FP3, FP4, Murena One
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: no
## Summary
Apps installed on Fairphone 3 report wrong location. Apps like Maps, Google Maps etc. report wrong location.
## The problem
**Steps to reproduce**
Likely happening when there is not enough GPS signal to locate. The phone uses other methods to calculate location.
In My Location app, the location reported by UnifiedNLP Backends is wrong or outdated/ not exact.
**What is the current behavior?**
The phone thinks it is at another location
**What is the expected correct behavior?**
Right location, or no location.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![photo_2023-03-27_13-56-11](/uploads/43748df54a5eb67b9c3a739376ad8636/photo_2023-03-27_13-56-11.jpg)
## Solutions
**Workaround**
Possibly "clear agps data" button in My Location app helps.
**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/6429Feature proposal: Pre-install Nulide's FindMyDevice as a replacement for Goog...2024-02-28T19:41:37ZPixelcodeFeature proposal: Pre-install Nulide's FindMyDevice as a replacement for Google's Find My Device- /e/ versions: all
- Device model(s): all
- Device rooted: irrelevant
Currently, no ungoogled Android-based operating system I'm aware of offers an open-source replacement for Google's `Find My Device` service. As its name suggests, it...- /e/ versions: all
- Device model(s): all
- Device rooted: irrelevant
Currently, no ungoogled Android-based operating system I'm aware of offers an open-source replacement for Google's `Find My Device` service. As its name suggests, it lets you easily find your missing phone using Google services and GPS.
However, there is, in fact, an open-source alternative called [FindMyDevice](https://gitlab.com/Nulide/findmydevice). Perhaps it could be pre-installed as a system app?
In fact, FMD requires users to grant it the `WRITE_SECURE_SETTINGS` permission by running the following ADB command: `adb shell pm grant de.nulide.findmydevice android.permission.WRITE_SECURE_SETTINGS`
This would not be necessary if FMD had system privileges in the first place. Including FMD in /e/ OS would not only allow users who have never heard of the app before to use that feature, but would also allow them to use it without having to touch the command line.https://gitlab.e.foundation/e/backlog/-/issues/7543RCS doesn't work2024-02-28T19:38:49ZPixelcodeRCS doesn't work- /e/ version: 1.17-s-20231111351092-dev-FP3
- Device model(s): Fairphone 3
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes (irrelevant)
## Summary
[Rich Communication Services](https://en.wikipedia.or...- /e/ version: 1.17-s-20231111351092-dev-FP3
- Device model(s): Fairphone 3
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes (irrelevant)
## Summary
[Rich Communication Services](https://en.wikipedia.org/wiki/Rich_Communication_Services) are not available on the FP3 running /e/ OS.
## The problem
Since the built-in SMS app (`foundation.e.message`) does not support RCS natively, it may be assumed that RCS could at least be used via a third-party app, such as Google Messages. However, that is not possible, not even when installing the Google Carrier Services.
**Steps to reproduce**
0. Use a SIM card of a telecom provider that supports RCS (my provider [does](https://www.wetell.de/service/faq)).
1. Install [Google Carrier Services](https://play.google.com/store/apps/details?id=com.google.android.ims)
2. Install [Messages by Google](https://play.google.com/store/apps/details?id=com.google.android.apps.messaging)
3. Open Messages, go to the RCS option in the settings.
4. It says: “RCS is not supported by your device.”
**What is the current behavior?**
RCS is not supported.
**What is the expected correct behavior?**
RCS should be supported.
## Technical informations
**Relevant logs (`adb logcat`)**
none
**Relevant screenshots**
none
## Solutions
**Workaround**
none
**Possible fixes**
???
<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/7771[Feature Request] Allow to set battery charging limit2024-02-28T19:35:55ZErwan Georgete.i9dnw@passmail.net[Feature Request] Allow to set battery charging limit- /e/ version: 1.19
- Device model(s): FP5, but may apply to other devices
## Summary
As explained in this [Ifixit blog post](https://www.ifixit.com/News/90983/why-charging-your-gadgets-over-80-is-such-a-bad-idea), it is best to not ch...- /e/ version: 1.19
- Device model(s): FP5, but may apply to other devices
## Summary
As explained in this [Ifixit blog post](https://www.ifixit.com/News/90983/why-charging-your-gadgets-over-80-is-such-a-bad-idea), it is best to not charge your phone above 80% to preserve its battery. If it isn't as much of a ploblem with a device like the FP5 (which has a replaceable battery), it is for most of the phone supported by /e/os.
The official FP5 image has this option, as such it should be quite easy to develop as it already prove it is doable. Multiple open-source apps does the same, but all of them requires a rooted device.
## Description
**What is the current behavior?**
No such option is available. Phone won't stop charging until it is at 100%
**What is the improved behavior?**
In the settings, an option allows to set a limit to 80% (or any other custom percentages) of the nominal capacity.
**What does it bring?**
The ability to set max charging to a level that preserve the battery (80%).
## Validation
- On a device which battery is bellow 80%, Set limit to 80%
, then charge it -> It should stop charging around upper 80% (like 80.95%), and not start charging again before it reach around 79% (like 80.05%).
Previous issue : #5879
<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/6706Screen recording turns on Screen Cast, and Screen Cast stops recording2024-02-28T19:35:09ZPixelcodeScreen recording turns on Screen Cast, and Screen Cast stops recording- /e/ version: 1.8.1-s-20230203257074-dev-FP3
- Device model(s): Fairphone 3
- Device rooted: no
## Summary
When starting a screen recording, Screen Cast is turned on. Disabling Screen Cast silently stops the screen recording, but to t...- /e/ version: 1.8.1-s-20230203257074-dev-FP3
- Device model(s): Fairphone 3
- Device rooted: no
## Summary
When starting a screen recording, Screen Cast is turned on. Disabling Screen Cast silently stops the screen recording, but to the user the recording seems to continue. The actual video file ends at the exact time the Screen Cast was stopped.
## The problem
**Steps to reproduce**
1. Start screen recording.
2. Turn off Screen Cast, but don't stop the screen recording.
2. The screen recording appears to continue (but it doesn't).
3. Open the video file of the screen recording and notice that it ends where Screen Cast was stopped.
**What is the current behavior?**
Ending the Screen Cast stops the screen recording, but to the user the screen recording appears to continue.
**What is the expected correct behavior?**
Either ending the Screen Cast should not stop the screen recording in the first place, or it should be obvious to the user that the screen recording has ended.
## Screenshots
Here's a video of the issue. Note that I stopped the Screen Cast at exactly 20:48:48 system time but the screen recording only at 20:49:02. According to the red screen recording notification, the recording should be exactly 20 seconds in length.
However, the actual screen recording file stops exactly at 20:48:48 system time and is only 9 seconds in length.
![FP3_Android_S_Screen_Cast_ends_screen_recording](/uploads/a709c32461752f72356f9cbba205dc25/FP3_Android_S_Screen_Cast_ends_screen_recording.mp4)
![FP3_Android_S_Screen_Cast_screen_recording](/uploads/9428c38044e6b16ad9ed95bc124b8829/FP3_Android_S_Screen_Cast_screen_recording.mp4)https://gitlab.e.foundation/e/backlog/-/issues/7026Screen recording only records third-party app sounds2024-02-28T19:27:11ZPixelcodeScreen recording only records third-party app sounds- /e/ version: `1.11-s-20230511288805-dev-FP3`
- Device model: Fairphone 3
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes (irrelevant)
## Summary
When doing a screen recording and enabling the option ...- /e/ version: `1.11-s-20230511288805-dev-FP3`
- Device model: Fairphone 3
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes (irrelevant)
## Summary
When doing a screen recording and enabling the option to also record device audio, then the alarm of the clock app won't be recorded while ringing.
## The problem
1. Set an alarm in the clock app.
2. Open the screen recording popup.
3. Enable “Record device audio”.
4. Record the screen while the alarm is ringing.
5. Open the recording and notice that nothing can be heard.
This issue also exists in Lineage OS A13. I tested it with `20-20230605-microG-gts4lvwifi`.
**What is the current behavior?**
The alarm is silent in the recording. Note that other sounds are properly recorded, such as YouTube videos.
**What is the expected correct behavior?**
The alarm should be recorded as expected.
**Screenshots**
“Record device audio” is enabled:
![image](/uploads/94fa83f2dbc5ede7528ed720284516f3/image.png)https://gitlab.e.foundation/e/backlog/-/issues/7160"Choose a color" doesn’t work in "Style and Background"2024-02-28T17:50:46Zwatt"Choose a color" doesn’t work in "Style and Background"- /e/ version:1.9-q-20230310268292-stable-herolte
- Device model(s): Samsung galaxy S7
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## The problem
Parameters->Screen->Style and backgrounds.
On t...- /e/ version:1.9-q-20230310268292-stable-herolte
- Device model(s): Samsung galaxy S7
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: yes
## The problem
Parameters->Screen->Style and backgrounds.
On the interface “choose à colour”, nothing happen when I tap on the blue dot. It is impossible to change the colour. The fonts, icons, and shapes options work well, but not the colour.
**What is the current behavior?**
nothing happen
**What is the expected correct behavior?**
I expect a palet of color
## Technical informationshttps://gitlab.e.foundation/e/backlog/-/issues/7518Wi-Fi Calling not available on Galaxy S82024-02-28T17:48:26ZRoman EngesserWi-Fi Calling not available on Galaxy S8- /e/ version: 1.16-r-20231017342509-stable-dreamlte
- Device model(s): Samsung Galaxy S8 SM-G950F
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: does not work either way
The option to turn on/off Wi-Fi Ca...- /e/ version: 1.16-r-20231017342509-stable-dreamlte
- Device model(s): Samsung Galaxy S8 SM-G950F
- Developer mode enabled: yes
- Device rooted: no
- Trackers blocker enabled: does not work either way
The option to turn on/off Wi-Fi Calling is not available (carrier: Swisscom). It's not under Network & Internet and not in the call settings. Funnily enough it appears in settings search, but when selected it just brings you to the network settings without any option for Wi-Fi calling.
When I was using a e/os on a Fairphone 3 I could turn it on/off in the network settings, using the same carrier as now (Swisscom).https://gitlab.e.foundation/e/backlog/-/issues/6876wifi connected to macos hotspot but "no internet" - Murena S92024-02-28T17:45:50Zmrak ewifi connected to macos hotspot but "no internet" - Murena S9I am using an S9 running e-1.9 that was bought on the Murena store. When connecting to a hotspot from a macos desktop however, I get the message "Connected, no internet". I know for a fact that the hotspot works fine, because I use it to...I am using an S9 running e-1.9 that was bought on the Murena store. When connecting to a hotspot from a macos desktop however, I get the message "Connected, no internet". I know for a fact that the hotspot works fine, because I use it to connect a macos laptop, an iOS tablet, and a googled android phone. I note that I am able to connect to several wifi routers without problems, it is just to macos hotspot.
Other information that might be of use: I am using the device MAC address. I am also using private DNS (via nextcould). I am not using any of the /e/OS advanced privacy features. Finally, I note that I also can not connect to the univeristy "eduroam" wifi network, but I am not sure if this is a related or different problem.
I would be happy to provide any other information you might need.https://gitlab.e.foundation/e/backlog/-/issues/6785WiFi on Murena One turning off periodically after updating to /e/OS 1.92024-02-28T17:30:22ZKnight WhoSaysNiWiFi on Murena One turning off periodically after updating to /e/OS 1.9- /e/ version:1.9-20230310268291
- Device model(s): Murena One
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
After updating to the aforementioned version of /e/OS (from 1.8 to 1.9), the WiF...- /e/ version:1.9-20230310268291
- Device model(s): Murena One
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
After updating to the aforementioned version of /e/OS (from 1.8 to 1.9), the WiFi on my Murena One turns off sporadically but periodically. This may happen a few times an hour or up to several times within a few minutes, rendering the phone basically unusable for any WiFi-related task.
This is not the usual kind of WiFi disconnects that may appear when the network is too weak or out of range -
The WiFi symbol above the notification bar is actually turning off.
## The problem
**Steps to reproduce**
Updating /e/OS on the Murena One from 1.8 to 1.9 and start using the WiFi connection.
I suspect this bug to occur more frequently when the connection is used (e.g. surfing with the browser, syncing tasks, etc.)
**What is the current behavior?**
WiFi is constantly turning off and therefore disconnecting.
**What is the expected correct behavior?**
WiFi should stay enabled until turned off manually (or by manually activating the airplane mode)
## Technical informations
**Relevant logs (`adb logcat`)**
*None*
Feel free to tell me what information I may provide to assist in troubleshooting this issue.
**Relevant screenshots**
*None*
## Solutions
**Workaround**
I don't know any workaround besides manually re-enabling the WiFi and trying to keep calm ;)
**Possible fixes**
*None*https://gitlab.e.foundation/e/backlog/-/issues/7173App Lounge does not install apps after clicking install2024-02-28T17:10:07ZShenol MustafovApp Lounge does not install apps after clicking install- /e/ version:
- Device model(s): FP4
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
When searching for apps, and clicking install, nothing happens.
## The problem
**Steps to re...- /e/ version:
- Device model(s): FP4
- Developer mode enabled: yes/no
- Device rooted: yes/no
- Trackers blocker enabled: yes/no
## Summary
When searching for apps, and clicking install, nothing happens.
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
**What is the current behavior?**
<What actually happens>
**What is the expected correct behavior?**
<What you should see instead>
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
<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/5977FP4 can't select charging sound None2024-02-28T17:09:03ZFrank MüllerFP4 can't select charging sound None- /e/ version: IMG-e-1.3-r-20220823212872-stable-FP4 and earlier
- Device model(s): Fairphone 4 (FP4) ~FP4
- Device rooted: no
- System language: german
## Summary
If I navigate to settings -> Sound -> Advances -> Charging sounds -> N...- /e/ version: IMG-e-1.3-r-20220823212872-stable-FP4 and earlier
- Device model(s): Fairphone 4 (FP4) ~FP4
- Device rooted: no
- System language: german
## Summary
If I navigate to settings -> Sound -> Advances -> Charging sounds -> Notification Sounds > Select in the drop down menu "None".
The change does not take effect. If you select something else from the drop down menu, the selection works. Only the deactivation of the sound does not work.
I want to enable vibrations by start charging and disable the notification sound. To have vibration only as charging hint.
~"type::Bug"
~FP4https://gitlab.e.foundation/e/backlog/-/issues/7143Notification quick settings overlapping2024-02-28T17:07:26ZAaron Chung-JukkoNotification quick settings overlapping- /e/ version: 1.12.3
- Device model(s): FP4
- Developer mode enabled: either
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
The quick settings tiles on pulling down the shade sometimes have both a 2x2 grid and a 1x4 gr...- /e/ version: 1.12.3
- Device model(s): FP4
- Developer mode enabled: either
- Device rooted: no
- Trackers blocker enabled: yes
## Summary
The quick settings tiles on pulling down the shade sometimes have both a 2x2 grid and a 1x4 grid showing simultaneously.
![screenshot-2023-07-24-23-20-42-2](/uploads/e5cc4a181899054adf4e27899fbee702/screenshot-2023-07-24-23-20-42-2.png)
## Solutions
**Workaround**
Turn on brightness slider in Status Bar.
**Possible fixes**
Possibly a problem only when turning on the hide brightness slider drying