Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2020-04-10T07:03:44Zhttps://gitlab.e.foundation/e/backlog/-/issues/1043Notes sync is missing2020-04-10T07:03:44ZRomain HunaultNotes sync is missing* /e/ version: /e/ test hobart
* Device model: kiwi (nougat)
* When it started to occur: both on fresh install and after update
* Reproducible with the last /e/ version: -
* Reproducible with LineageOS: -
## Summary
<Summarize the bug ...* /e/ version: /e/ test hobart
* Device model: kiwi (nougat)
* When it started to occur: both on fresh install and after update
* Reproducible with the last /e/ version: -
* Reproducible with LineageOS: -
## Summary
<Summarize the bug encountered briefly and precisely>
Notes sync is disabled and can't be enabled
<Please tick one of the following sentences if relevant>
- [ ] The device is unusable
- [ ] The bug is the source of a data loss or a big waste of time
- [ ] The bug concerns a third party app
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. Install the /e/ test build
1. Add an /e/ account
1. Open Notes app
**What is the current behavior?**
<What actually happens>
1. The app show a message informing the user that sync is disabled
1. Under ecloud account sync settings, the Notes button is missing
**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>
Message from the Notes app:
![screenshot_20200309_14_56_00](/uploads/4dcafd695f3745697915d2c84ac41d39/screenshot_20200309_14_56_00.png)
Under ecloud account sync settings, no entry for Notes
![screenshot_20200309_11_13_05](/uploads/27973cf01eff3d170858fb35c0167e43/screenshot_20200309_11_13_05.png)
![screenshot_20200309_11_13_10](/uploads/6a4fe57aa2ded15cc45fc524da94a6b7/screenshot_20200309_11_13_10.png)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>IstanbulSumit PundirSumit Pundirhttps://gitlab.e.foundation/e/backlog/-/issues/918Fix Task fork sync functionality2020-04-10T07:03:46ZRomain HunaultFix Task fork sync functionality- /e/ version: test
- Device model:
- When it started to occur:
- Reproducible with the last /e/ version:
- Reproducible with LineageOS:
## Summary
<Summarize the bug encountered briefly and precisely>
The AccountManager does not hand...- /e/ version: test
- Device model:
- When it started to occur:
- Reproducible with the last /e/ version:
- Reproducible with LineageOS:
## Summary
<Summarize the bug encountered briefly and precisely>
The AccountManager does not handle the new task app (forked from Tasks).
<Please tick one of the following sentences if relevant>
- [ ] The device is unusable
- [ ] The bug is the source of a data loss or a big waste of time
- [ ] The bug concerns a third party app
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
Run a build with using our Tasks app and setup an ecloud account.
<How one can reproduce the issue>
**What is the current behavior?**
Tasks are not synced.
<What actually happens>
**What is the expected correct behavior?**
ecloud account is set in tasks, and data are synced
<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>
/label ~Bug
IstanbulMohit MaliMohit Malihttps://gitlab.e.foundation/e/backlog/-/issues/1042Too many button in /e/ account conf2020-04-10T07:03:42ZRomain HunaultToo many button in /e/ account conf* /e/ version: /e/ test hobart
* Device model: kiwi (nougat)
* When it started to occur: both on fresh install and after update
* Reproducible with the last /e/ version: -
* Reproducible with LineageOS: -
## Summary
<Summarize the bug ...* /e/ version: /e/ test hobart
* Device model: kiwi (nougat)
* When it started to occur: both on fresh install and after update
* Reproducible with the last /e/ version: -
* Reproducible with LineageOS: -
## Summary
<Summarize the bug encountered briefly and precisely>
There is too many button (without any label) in the ecloud account sync configuration.
<Please tick one of the following sentences if relevant>
- [ ] The device is unusable
- [ ] The bug is the source of a data loss or a big waste of time
- [ ] The bug concerns a third party app
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. Install the /e/ test build
1. Add an /e/ account
**What is the current behavior?**
<What actually happens>
At the bottom, too many buttons without label are here.
**What is the expected correct behavior?**
<What you should see instead>
If the buttons are useful, they should have a label.
If not, they should not be shown.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![screenshot_20200309_11_13_10](/uploads/a1b5144a2381e320b6a3e5779d814476/screenshot_20200309_11_13_10.png)
<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>IstanbulSumit PundirSumit Pundirhttps://gitlab.e.foundation/e/backlog/-/issues/1014Browser Homepage url link is not working2020-04-10T07:03:40ZManoj NairBrowser Homepage url link is not working- /e/ version: Pie builds
- Device model: Tissot
- When it started to occur: 1 month (?)
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: NA
## Summary
- Browser open to a broken home page link
<Please tick...- /e/ version: Pie builds
- Device model: Tissot
- When it started to occur: 1 month (?)
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: NA
## Summary
- Browser open to a broken home page link
<Please tick one of the following sentences if relevant>
- [ ] The device is unusable
- [ ] The bug is the source of a data loss or a big waste of time
- [ ] The bug concerns a third party app
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
- Tap the Browser icon
**What is the current behavior?**
- It shows a Home page with a message "This site cannot be reached"
- Browser url is chrome://blank/
**What is the expected correct behavior?**
- It should show a proper default home page with /e/ specific graphics or a blank [age at the least
## Technical information
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![Screenshot_20200226-073044_Browser](/uploads/6a212aa23b66de1368462a669b939665/Screenshot_20200226-073044_Browser.png)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>IstanbulSumit PundirSumit Pundirhttps://gitlab.e.foundation/e/backlog/-/issues/852Unable to enable Mail authorizations2020-03-06T11:14:28ZFlorent BédécarratsUnable to enable Mail authorizations## Summary
Authorisations for Mail app for distant control of mailboxes, mail reading and mail deletting
## Steps to reproduce
Go to Parameters>Applications>Mail>Authorizations>Additional authorizations
Enable the 3 options and quit
Go ...## Summary
Authorisations for Mail app for distant control of mailboxes, mail reading and mail deletting
## Steps to reproduce
Go to Parameters>Applications>Mail>Authorizations>Additional authorizations
Enable the 3 options and quit
Go back to Parameters>Applications>Mail>Authorizations>Additional authorizations
The enabled authorization were automatically disabled.
## Current behaviour
The emails do not appear as read or deleted on my webmail when I delete them on my phone + they are reverted back to unread/undeleted each time I refresh.
## Expected behavious
The enabled authorization should remain enabled after I close the parameter panel and the sync with mail accounts should work.
## Configuration
Galaxy S7
/e/OS 0.7-2019090322469
Emails accounts are gmail (I'm quitting but still need it in the transition), posteo and /e/
All in IMAPIstanbulFlorent BédécarratsFlorent Bédécarratshttps://gitlab.e.foundation/e/backlog/-/issues/845After few weeks, gmail is not synced anymore2020-04-10T07:03:48ZRomain HunaultAfter few weeks, gmail is not synced anymore## Summary
After having being able to use a gmail account from Mail during few weeks, a user reports that he is not able to use it anymore
## Steps to reproduce
Add a Google account ... and wait few weeks.
I don't know if it's relevan...## Summary
After having being able to use a gmail account from Mail during few weeks, a user reports that he is not able to use it anymore
## Steps to reproduce
Add a Google account ... and wait few weeks.
I don't know if it's relevant, but the account has 2FA enabled
Last but not least, it does not matter where the Google is added (Mail or AccountManager).
## What is the current behavior?
Few weeks after, gmail account is not synced anymore. A notification error appears `Échec d'authentification pour <gmail address>`
## What is the expected correct behavior?
Gmail account is synced until it is removed.
## Relevant logs and/or screenshots
![Capture_du_2019-10-31_16-37-09](/uploads/7410a17bc752c5d857b152a3dcb8b450/Capture_du_2019-10-31_16-37-09.png)
What is strange is there is nothing in logs
## Possible fixes
I think there is something with an authentication token. It should be valid during few week, and can't be renewed.IstanbulAlexandre RouxAlexandre Rouxhttps://gitlab.e.foundation/e/backlog/-/issues/1045PDF viewer icon still visible2020-08-03T15:10:29ZRomain HunaultPDF viewer icon still visible- /e/ version: /e/ test hobart
- Device model: kiwi (nougat)
- When it started to occur: both on fresh install and after update
- Reproducible with the last /e/ version: -
- Reproducible with LineageOS: -
## Summary
<Summarize the bug ...- /e/ version: /e/ test hobart
- Device model: kiwi (nougat)
- When it started to occur: both on fresh install and after update
- Reproducible with the last /e/ version: -
- Reproducible with LineageOS: -
## Summary
<Summarize the bug encountered briefly and precisely>
After installing the test build as an update, the PDF viewer app icon is still shown.
<Please tick one of the following sentences if relevant>
- [ ] The device is unusable
- [ ] The bug is the source of a data loss or a big waste of time
- [ ] The bug concerns a third party app
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. Install the /e/ test build by updating a previous version
1. Go on the launcher grid
**What is the current behavior?**
<What actually happens>
1. The PDF viewer app is still present on the grid
1. Its icon is missing
**What is the expected correct behavior?**
<What you should see instead>
The icon have to be hidden, both on a fresh install (that's working) and after an update.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
![screenshot_20200309_10_28_27](/uploads/3a92717b96e12519c844be34d030b1b5/screenshot_20200309_10_28_27.png)
<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>IstanbulAmit Kumaramitkma@e.emailAmit Kumaramitkma@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/866"About" in Mail is for standard K9, not /e/2020-04-10T07:03:49ZWill"About" in Mail is for standard K9, not /e/Hi,
I noticed that the About page in Mail appears to be for standard K9 Mail, not the /e/ fork. Is this correct?Hi,
I noticed that the About page in Mail appears to be for standard K9 Mail, not the /e/ fork. Is this correct?IstanbulMohit MaliMohit Malihttps://gitlab.e.foundation/e/backlog/-/issues/825Apps installed on SD disappear from launcher2020-04-10T07:03:42ZRomain HunaultApps installed on SD disappear from launcher## Summary
After each OTA update, icon grid is reset
## Steps to reproduce
Download and install an OTA update.
## What is the current behavior?
On first boot after OTA update, all icons are reset.
## What is the expected correct behav...## Summary
After each OTA update, icon grid is reset
## Steps to reproduce
Download and install an OTA update.
## What is the current behavior?
On first boot after OTA update, all icons are reset.
## What is the expected correct behavior?
After OTA, icon groups and place is preserved.
## Relevant logs and/or screenshots
## Possible fixes
FYI @gael
IstanbulAmit Kumaramitkma@e.emailAmit Kumaramitkma@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/1015Message app (sms) crashes with a vcard message2020-04-06T06:00:14ZGaël DuvalMessage app (sms) crashes with a vcard message- /e/ version: 0.7-o-20200208
- Device model: Chiron
- When it started to occur: unknown
- Reproducible with the last /e/ version:
- Reproducible with LineageOS:
## Summary
Message app crashes with VCARD
- [ ] The device is unusable
-...- /e/ version: 0.7-o-20200208
- Device model: Chiron
- When it started to occur: unknown
- Reproducible with the last /e/ version:
- Reproducible with LineageOS:
## Summary
Message app crashes with VCARD
- [ ] The device is unusable
- [ ] The bug is the source of a data loss or a big waste of time
- [ ] The bug concerns a third party app
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
Have a SMS sent to our device which contains a VCARD (contact)
Open the Message app, touch the discussion with the VCARD.
Application is crashing
Application shouldn't crash, VCARD should be accessible and usable.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
02-27 10:26:24.112 1834 1834 E RecyclerView: No adapter attached; skipping layout
02-27 10:26:24.113 1834 1834 E RecyclerView: No adapter attached; skipping layout
02-27 10:26:24.235 1087 1142 I ActivityManager: Displayed foundation.e.message/com.moez.QKSMS.feature.compose.ComposeActivity: +361ms
02-27 10:26:24.260 1834 1882 D OpenGLRenderer: endAllActiveAnimators on 0x79197c2800 (RippleDrawable) with handle 0x7916281800
02-27 10:26:24.410 767 767 E QCOM PowerHAL: Failed to acquire lock.
02-27 10:26:24.429 1834 1834 W System.err: io.reactivex.exceptions.OnErrorNotImplementedException: The exception was not handled due to missing onError handler in the subscribe() method call. Further reading: https://github.com/ReactiveX/RxJava/wiki/Error-Handling | java.lang.IllegalStateException: vcard.formattedName must not be null
02-27 10:26:24.429 1834 1834 W System.err: at io.reactivex.internal.functions.Functions$OnErrorMissingConsumer.accept(Functions.java:704)
02-27 10:26:24.429 1834 1834 W System.err: at io.reactivex.internal.functions.Functions$OnErrorMissingConsumer.accept(Functions.java:701)
02-27 10:26:24.429 1834 1834 W System.err: at io.reactivex.internal.observers.LambdaObserver.onError(LambdaObserver.java:77)
02-27 10:26:24.429 1834 1834 W System.err: at io.reactivex.internal.observers.LambdaObserver.onNext(LambdaObserver.java:67)
02-27 10:26:24.429 1834 1834 W System.err: at com.uber.rxdogtag.DogTagObserver.lambda$onNext$3$DogTagObserver(DogTagObserver.java:56)
02-27 10:26:24.429 1834 1834 W System.err: at com.uber.rxdogtag.-$$Lambda$DogTagObserver$Bul2aJuZ0nriT_735invreaJZFw.run(Unknown Source:4)
02-27 10:26:24.429 1834 1834 W System.err: at com.uber.rxdogtag.RxDogTag.guardedDelegateCall(RxDogTag.java:221)
02-27 10:26:24.429 1834 1834 W System.err: at com.uber.rxdogtag.DogTagObserver.onNext(DogTagObserver.java:56)
02-27 10:26:24.429 1834 1834 W System.err: at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.drainNormal(ObservableObserveOn.java:201)
02-27 10:26:24.429 1834 1834 W System.err: at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.run(ObservableObserveOn.java:255)
02-27 10:26:24.429 1834 1834 W System.err: at io.reactivex.android.schedulers.HandlerScheduler$ScheduledRunnable.run(HandlerScheduler.java:124)
02-27 10:26:24.429 1834 1834 W System.err: at android.os.Handler.handleCallback(Handler.java:790)
02-27 10:26:24.429 1834 1834 W System.err: at android.os.Handler.dispatchMessage(Handler.java:99)
02-27 10:26:24.429 1834 1834 W System.err: at android.os.Looper.loop(Looper.java:164)
02-27 10:26:24.429 1834 1834 W System.err: at android.app.ActivityThread.main(ActivityThread.java:6494)
02-27 10:26:24.429 1834 1834 W System.err: at java.lang.reflect.Method.invoke(Native Method)
02-27 10:26:24.429 1834 1834 W System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
02-27 10:26:24.429 1834 1834 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
02-27 10:26:24.429 1834 1834 W System.err: Caused by: java.lang.IllegalStateException: vcard.formattedName must not be null
02-27 10:26:24.429 1834 1834 W System.err: at com.moez.QKSMS.feature.compose.part.VCardBinder$bindPart$5.accept(VCardBinder.kt:66)
02-27 10:26:24.429 1834 1834 W System.err: at com.moez.QKSMS.feature.compose.part.VCardBinder$bindPart$5.accept(VCardBinder.kt:42)
02-27 10:26:24.430 1834 1834 W System.err: at io.reactivex.internal.observers.LambdaObserver.onNext(LambdaObserver.java:63)
02-27 10:26:24.430 1834 1834 W System.err: ... 14 more
02-27 10:26:24.430 1834 1834 W System.err: io.reactivex.exceptions.OnErrorNotImplementedException: The exception was not handled due to missing onError handler in the subscribe() method call. Further reading: https://github.com/ReactiveX/RxJava/wiki/Error-Handling | java.lang.IllegalStateException: vcard.formattedName must not be null
02-27 10:26:24.430 1834 1834 W System.err: at io.reactivex.internal.functions.Functions$OnErrorMissingConsumer.accept(Functions.java:704)
02-27 10:26:24.430 1834 1834 W System.err: at io.reactivex.internal.functions.Functions$OnErrorMissingConsumer.accept(Functions.java:701)
02-27 10:26:24.430 1834 1834 W System.err: at io.reactivex.internal.observers.LambdaObserver.onError(LambdaObserver.java:77)
02-27 10:26:24.430 1834 1834 W System.err: at io.reactivex.internal.observers.LambdaObserver.onNext(LambdaObserver.java:67)
02-27 10:26:24.430 1834 1834 W System.err: at com.uber.rxdogtag.DogTagObserver.lambda$onNext$3$DogTagObserver(DogTagObserver.java:56)
02-27 10:26:24.430 1834 1834 W System.err: at com.uber.rxdogtag.-$$Lambda$DogTagObserver$Bul2aJuZ0nriT_735invreaJZFw.run(Unknown Source:4)
02-27 10:26:24.430 1834 1834 W System.err: at com.uber.rxdogtag.RxDogTag.guardedDelegateCall(RxDogTag.java:221)
02-27 10:26:24.430 1834 1834 W System.err: at com.uber.rxdogtag.DogTagObserver.onNext(DogTagObserver.java:56)
02-27 10:26:24.430 1834 1834 W System.err: at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.drainNormal(ObservableObserveOn.java:201)
02-27 10:26:24.430 1834 1834 W System.err: at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.run(ObservableObserveOn.java:255)
02-27 10:26:24.430 1834 1834 W System.err: at io.reactivex.android.schedulers.HandlerScheduler$ScheduledRunnable.run(HandlerScheduler.java:124)
02-27 10:26:24.430 1834 1834 W System.err: at android.os.Handler.handleCallback(Handler.java:790)
02-27 10:26:24.430 1834 1834 W System.err: at android.os.Handler.dispatchMessage(Handler.java:99)
02-27 10:26:24.430 1834 1834 W System.err: at android.os.Looper.loop(Looper.java:164)
02-27 10:26:24.430 1834 1834 W System.err: at android.app.ActivityThread.main(ActivityThread.java:6494)
02-27 10:26:24.430 1834 1834 W System.err: at java.lang.reflect.Method.invoke(Native Method)
02-27 10:26:24.430 1834 1834 W System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
02-27 10:26:24.430 1834 1834 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
02-27 10:26:24.430 1834 1834 W System.err: Caused by: java.lang.IllegalStateException: vcard.formattedName must not be null
02-27 10:26:24.430 1834 1834 W System.err: at com.moez.QKSMS.feature.compose.part.VCardBinder.bindPart(VCardBinder.kt:66)
02-27 10:26:24.430 1834 1834 W System.err: at [[ ↑↑ Inferred subscribe point ↑↑ ]].(:0)
02-27 10:26:24.430 1834 1834 W System.err: at [[ Originating callback: onNext ]].(:0)
02-27 10:26:24.430 1834 1834 W System.err: at [[ ↓↓ Original trace ↓↓ ]].(:0)
02-27 10:26:24.430 1834 1834 W System.err: at com.moez.QKSMS.feature.compose.part.VCardBinder$bindPart$5.accept(VCardBinder.kt:66)
02-27 10:26:24.430 1834 1834 W System.err: at com.moez.QKSMS.feature.compose.part.VCardBinder$bindPart$5.accept(VCardBinder.kt:42)
02-27 10:26:24.430 1834 1834 W System.err: at io.reactivex.internal.observers.LambdaObserver.onNext(LambdaObserver.java:63)
02-27 10:26:24.430 1834 1834 W System.err: ... 14 more
02-27 10:26:24.432 1087 2657 W ActivityManager: Force finishing activity foundation.e.message/com.moez.QKSMS.feature.compose.ComposeActivity
02-27 10:26:24.439 1087 2657 W ActivityManager: Force finishing activity foundation.e.message/com.moez.QKSMS.feature.main.MainActivity
02-27 10:26:24.449 1087 1115 I ActivityManager: Showing crash dialog for package foundation.e.message u0
02-27 10:26:24.487 1087 6310 I OpenGLRenderer: Initialized EGL, version 1.4
02-27 10:26:24.488 1087 6310 D OpenGLRenderer: Swap behavior 2
02-27 10:26:24.936 1087 1114 W ActivityManager: Activity pause timeout for ActivityRecord{6e9ab16 u0 foundation.e.message/com.moez.QKSMS.feature.compose.ComposeActivity t20218 f}
02-27 10:26:25.094 1087 1115 W Looper : Dispatch took 138ms on android.ui, h=Handler (com.android.server.am.ActivityManagerService$UiHandler) {d885ea0} cb=null msg=31
02-27 10:26:25.096 7909 7909 D WeatherIconUtils: Decoding resource id = 2131230977 for density = 640
02-27 10:26:25.322 822 4875 D NuPlayerDriver: NuPlayerDriver(0xdda98db0) created, clientPid(1778)
02-27 10:26:25.331 822 1972 D GenericSource: FileSource remote
02-27 10:26:25.337 822 1971 D NuPlayerDriver: notifyListener_l(0xdda98db0), (1, 0, 0, -1), loop setting(0, 0)
02-27 10:26:25.346 1087 4438 I MediaFocusControl: requestAudioFocus() from uid/pid 10034/1778 clientId=android.media.AudioManager@ab7a6a7 callingPack=com.android.systemui req=3 flags=0x0 sdk=27
02-27 10:26:25.366 1778 1778 D StatusBar: disable<e i a s b h r c s q >
02-27 10:26:25.546 7909 7909 D NotificationRepository: updateNotification() called with: list = [85]
02-27 10:26:25.560 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:1 lineCount:1
02-27 10:26:25.561 1778 1778 I chatty : uid=10034(com.android.systemui) identical 1 line
02-27 10:26:25.564 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:1 lineCount:1
02-27 10:26:25.630 7909 7909 D NotificationRepository: updateNotification() called with: list = [85]
02-27 10:26:25.679 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:1 lineCount:1
02-27 10:26:25.679 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:2 lineCount:2
02-27 10:26:25.679 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:2 lineCount:2
02-27 10:26:25.680 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:3 lineCount:3
02-27 10:26:25.680 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:1 lineCount:1
02-27 10:26:25.681 1778 1778 I chatty : uid=10034(com.android.systemui) identical 6 lines
02-27 10:26:25.682 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:1 lineCount:1
02-27 10:26:25.682 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:7 lineCount:7
02-27 10:26:25.682 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:7 lineCount:7
02-27 10:26:25.697 7909 7909 D NotificationRepository: updateNotification() called with: list = [85]
02-27 10:26:25.699 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:6 lineCount:6
02-27 10:26:25.699 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:1 lineCount:1
02-27 10:26:25.699 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:6 lineCount:6
02-27 10:26:25.699 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:1 lineCount:1
02-27 10:26:25.700 1778 1778 I chatty : uid=10034(com.android.systemui) identical 4 lines
02-27 10:26:25.701 1778 1778 W StaticLayout: maxLineHeight should not be -1. maxLines:1 lineCount:1
02-27 10:26:25.780 7909 7909 D NotificationRepository: updateNotification() called with: list = [85]
02-27 10:26:25.781 7909 7909 D HorizontalPager: dispatchDraw() called with: canvas = [android.view.DisplayListCanvas@c6be478]
02-27 10:26:25.849 1778 1778 V MediaRouter: onRestoreRoute() : route=RouteInfo{ name=Phone, description=null, status=null, category=RouteCategory{ name=System types=ROUTE_TYPE_LIVE_AUDIO ROUTE_TYPE_LIVE_VIDEO groupable=false }, supportedTypes=ROUTE_TYPE_LIVE_AUDIO ROUTE_TYPE_LIVE_VIDEO , presentationDisplay=null }
02-27 10:26:25.849 1778 1778 V MediaRouter: Selecting route: RouteInfo{ name=Phone, description=null, status=null, category=RouteCategory{ name=System types=ROUTE_TYPE_LIVE_AUDIO ROUTE_TYPE_LIVE_VIDEO groupable=false }, supportedTypes=ROUTE_TYPE_LIVE_AUDIO ROUTE_TYPE_LIVE_VIDEO , presentationDisplay=null }
02-27 10:26:25.849 822 24104 D NuPlayerDriver: start(0xdda98db0), state is 4, eos is 0
02-27 10:26:25.850 822 1971 I GenericSource: start
02-27 10:26:25.860 1744 2310 V Avrcp : Media update: id -1➡-1? [MediaAttributes: France Inter - by InterVenez (0 0/0) ] : [MediaAttributes: France Inter - by 0% buffered… (0 0/0) ]
02-27 10:26:25.860 1744 2310 V Avrcp : Check if NowPlayingList is updated
02-27 10:26:25.865 1744 2310 I AddressedMediaPlayer: null queue from tunein.player, constructing single-item list
02-27 10:26:25.867 1744 2310 E Avrcp : play status change 0➡1 mPlayStatusChangedNT: 1
02-27 10:26:25.867 1744 2310 E bt_btif : register_notification_rsp: Avrcp device is not connected, handle: 0x0
02-27 10:26:25.885 822 1988 I OMXClient: Treble IOmx obtained
```
**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>IstanbulSumit PundirSumit Pundirhttps://gitlab.e.foundation/e/backlog/-/issues/778Uber crashes2020-03-11T10:39:49ZRomain HunaultUber crashesIt seems the last Uber version crashes with the last MicroG update (e-20200106 stable)
```
01-15 18:06:02.282 10157 10157 W System.err: io.reactivex.exceptions.OnErrorNotImplementedException: Inferred subscribe point: njo.a(:266249)
01-...It seems the last Uber version crashes with the last MicroG update (e-20200106 stable)
```
01-15 18:06:02.282 10157 10157 W System.err: io.reactivex.exceptions.OnErrorNotImplementedException: Inferred subscribe point: njo.a(:266249)
01-15 18:06:02.282 10157 10157 W System.err: at com.ubercab.rx2.java.stackelementtagging.TaggingObserver.onError(:237864)
01-15 18:06:02.282 10157 10157 W System.err: at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.a(:139677)
01-15 18:06:02.282 10157 10157 W System.err: at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.e(:139695)
01-15 18:06:02.282 10157 10157 W System.err: at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.run(:139752)
01-15 18:06:02.282 10157 10157 W System.err: at io.reactivex.android.schedulers.AsyncHandlerScheduler$ScheduledRunnable.run(:256445)
01-15 18:06:02.282 10157 10157 W System.err: at android.os.Handler.handleCallback(Handler.java:790)
01-15 18:06:02.282 10157 10157 W System.err: at android.os.Handler.dispatchMessage(Handler.java:99)
01-15 18:06:02.282 10157 10157 W System.err: at android.os.Looper.loop(Looper.java:164)
01-15 18:06:02.282 10157 10157 W System.err: at android.app.ActivityThread.main(ActivityThread.java:6494)
01-15 18:06:02.282 10157 10157 W System.err: at java.lang.reflect.Method.invoke(Native Method)
01-15 18:06:02.282 10157 10157 W System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
01-15 18:06:02.282 10157 10157 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
01-15 18:06:02.282 10157 10157 W System.err: Caused by: com.mapbox.mapboxsdk.q.a: Map interactions should happen on the UI thread. Method invoked from wrong thread is latLngForPixel.
01-15 18:06:02.282 10157 10157 W System.err: at com.mapbox.mapboxsdk.maps.NativeMapView.f(Unknown Source:53)
01-15 18:06:02.282 10157 10157 W System.err: at com.mapbox.mapboxsdk.maps.NativeMapView.a(Unknown Source:2)
01-15 18:06:02.282 10157 10157 W System.err: at com.mapbox.mapboxsdk.maps.w.a(Unknown Source:2)
01-15 18:06:02.282 10157 10157 W System.err: at org.microg.gms.maps.mapbox.ProjectionImpl.fromScreenLocation(Unknown Source:17)
01-15 18:06:02.282 10157 10157 W System.err: at com.google.android.gms.maps.internal.IProjectionDelegate$Stub.onTransact(Unknown Source:97)
01-15 18:06:02.282 10157 10157 W System.err: at android.os.Binder.transact(Binder.java:627)
01-15 18:06:02.282 10157 10157 W System.err: at cpi.a(:240258)
01-15 18:06:02.282 10157 10157 W System.err: at dit.a(:241558)
01-15 18:06:02.282 10157 10157 W System.err: at dia.a(:241446)
01-15 18:06:02.282 10157 10157 W System.err: at hha.fromScreenLocation(:123836)
01-15 18:06:02.282 10157 10157 W System.err: at njf.a(:266046)
01-15 18:06:02.282 10157 10157 W System.err: at njf.a(:266055)
01-15 18:06:02.282 10157 10157 W System.err: at -$$Lambda$njf$XnEnBj5IX9rzICBwhj9mHA7tGgE8.apply(Unknown Source:44)
01-15 18:06:02.282 10157 10157 W System.err: at io.reactivex.internal.operators.flowable.FlowableMap$MapSubscriber.onNext(:132780)
01-15 18:06:02.282 10157 10157 W System.err: at io.reactivex.internal.operators.flowable.FlowableObserveOn$ObserveOnSubscriber.g(:132999)
01-15 18:06:02.282 10157 10157 W System.err: at io.reactivex.internal.operators.flowable.FlowableObserveOn$BaseObserveOnSubscriber.run(:132845)
01-15 18:06:02.282 10157 10157 W System.err: at io.reactivex.internal.schedulers.ScheduledRunnable.run(:144312)
01-15 18:06:02.282 10157 10157 W System.err: at io.reactivex.internal.schedulers.ScheduledRunnable.call(:144295)
01-15 18:06:02.282 10157 10157 W System.err: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
01-15 18:06:02.282 10157 10157 W System.err: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
01-15 18:06:02.282 10157 10157 W System.err: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
01-15 18:06:02.282 10157 10157 W System.err: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
01-15 18:06:02.282 10157 10157 W System.err: at -$$Lambda$gvh$WntKdu3NGlhy_S71wZzZG1W9lzY.run(Unknown Source:7)
01-15 18:06:02.282 10157 10157 W System.err: at java.lang.Thread.run(Thread.java:764)
```IstanbulAlexandru Chircualexch@e.emailAlexandru Chircualexch@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/690TED videos not loading2020-07-30T09:23:31ZRik ViergeverTED videos not loadinghi, just posted that /e/ is working great on a Lenovo Tab 3 Plus LTE. https://community.e.foundation/t/unofficial-build-lenovo-yoga-tab-3-plus-lte-ytx703l/7681/4 great work!!
One small thing though: TED, an app that many people use a l...hi, just posted that /e/ is working great on a Lenovo Tab 3 Plus LTE. https://community.e.foundation/t/unofficial-build-lenovo-yoga-tab-3-plus-lte-ytx703l/7681/4 great work!!
One small thing though: TED, an app that many people use a lot, is not loading videos.
Expected behaviour: the TED app works normally and videos load.
Current behaviour: the TED app installs, loads, logs me in as a user, searches, basically does everything, except when i press on a video to play it, the video never loads. I checked using the TED web application in the /e/ browser on the same tablet, there the videos load fine, so it's not my wifi or the tablet, it has something to do with the TED app and /e/.
Do let know if you need more info.
Rik
ps sorry i see i placed this in the wrong category but unsure how to change that. IstanbulAlexandru Chircualexch@e.emailAlexandru Chircualexch@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/688WhatsApp crashes when attaching my position2020-04-10T07:03:47Zangelo dureghelloWhatsApp crashes when attaching my positionHi all,
i am on S7 herolte G930F kernel 3.18.14-g1b5fc11fcdb
build Wed Dec 25 03:09:07 2019
lineage_herolte-userdebug 7.1.2 NJH47F 20191225 dev-keys
I installed whatsapp (2.19.360) trough "A". When i attach my position, application c...Hi all,
i am on S7 herolte G930F kernel 3.18.14-g1b5fc11fcdb
build Wed Dec 25 03:09:07 2019
lineage_herolte-userdebug 7.1.2 NJH47F 20191225 dev-keys
I installed whatsapp (2.19.360) trough "A". When i attach my position, application crashes just after i tap on "current position", or any other choices.
Once restarted Whatsapp, seems position sharing has worked, other user received it, and it's correct, but whatsapp crashes again just after some seconds.
If i install Whatsapp trough Shelter, as in https://community.e.foundation/t/howto-using-whatsapp-under-shelter/5662 issue it's the same.IstanbulAlexandru Chircualexch@e.emailAlexandru Chircualexch@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/510GPS does not work with some applications2020-03-11T10:48:20ZR1C4RD0 54R41V4GPS does not work with some applicationsIstanbulAlexandru Chircualexch@e.emailAlexandru Chircualexch@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/1020App HealthMate crashes when Displaying Mapbox Map2020-04-10T07:03:48ZjklingenApp HealthMate crashes when Displaying Mapbox Map- /e/ version: 0-7-o-2020021240990-dev-pioneer
- Device model: H3113 / Sony Xperia XA2
- When it started to occur: since I first tried a few days ago
- Reproducible with the last /e/ version: ?
- Reproducible with LineageOS: ?
## Summar...- /e/ version: 0-7-o-2020021240990-dev-pioneer
- Device model: H3113 / Sony Xperia XA2
- When it started to occur: since I first tried a few days ago
- Reproducible with the last /e/ version: ?
- Reproducible with LineageOS: ?
## Summary
The Withings app Healthmate crashes whenever it displays a Mapbox map.
- [ ] The device is unusable
- [ ] The bug is the source of a data loss or a big waste of time
- [x] The bug concerns a third party app
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
1. Install and Open Health Mate
2. On the dashboard, click the plus button and start a new outdoor activity (walking, running, hiking, etc)
3. Move around outside to have some waypoints tracked.
4. Stop the activity, close and reopen the app
**What is the current behavior?**
When opening the app the next time, it crashes immediately while rendering the dashboard with the map on it.
After one or two days, there is enough other stuff on the dashboard, so that the map is not within the visible screen area. The app does not crash immediately while rendering the dashboard, but still crashes as soon as one scrolls the map into view.
**What is the expected correct behavior?**
The app does not crash.
## Technical informations
**Relevant logs (`adb logcat`)**
:point_down: not sure whether the following are relevant, but those happen a lot before the exception occurs, always with field num 8, 9, 10 or 11.
```
02-27 17:49:28.976 11843 11843 D SafeParcel: Unknown field num 8 in com.google.android.gms.maps.model.PolylineOptions, skipping.
02-27 17:49:28.977 11843 11843 D SafeParcel: Unknown field num 9 in com.google.android.gms.maps.model.PolylineOptions, skipping.
02-27 17:49:28.977 11843 11843 D SafeParcel: Unknown field num 10 in com.google.android.gms.maps.model.PolylineOptions, skipping.
02-27 17:49:28.977 11843 11843 D SafeParcel: Unknown field num 11 in com.google.android.gms.maps.model.PolylineOptions, skipping.
```
:point_down: definitely relevant:
```
02-27 17:49:29.743 11843 11843 D AndroidRuntime: Shutting down VM
02-27 17:49:29.744 11843 11843 E AndroidRuntime: FATAL EXCEPTION: main
02-27 17:49:29.744 11843 11843 E AndroidRuntime: Process: com.withings.wiscale2, PID: 11843
02-27 17:49:29.744 11843 11843 E AndroidRuntime: java.lang.IllegalArgumentException: Parameter specified as non-null is null: method c.i.d.j.b, parameter bitmap
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at org.microg.gms.maps.mapbox.GoogleMapImpl.snapshot(Unknown Source:7)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at com.google.android.gms.maps.internal.IGoogleMapDelegate$Stub.onTransact(Unknown Source:387)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at org.microg.gms.maps.mapbox.GoogleMapImpl.onTransact(Unknown Source:0)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at android.os.Binder.transact(Binder.java:627)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at com.google.android.gms.internal.maps.zza.zzb(Unknown Source:2)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at com.google.android.gms.maps.internal.zzg.snapshot(Unknown Source:4)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at com.google.android.gms.maps.GoogleMap.snapshot(Unknown Source:3)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at com.google.android.gms.maps.GoogleMap.snapshot(Unknown Source:1)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at com.withings.wiscale2.a.c.d.b.q.run(WorkoutBigItemViewHolder.kt:1)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:790)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6494)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
02-27 17:49:29.744 11843 11843 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
```
**Relevant screenshots**
<Screenshots of the problem>
## Solutions
**Workaround**
Not tracking activities with location data. :shrug:
**Possible fixes**IstanbulAlexandru Chircualexch@e.emailAlexandru Chircualexch@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/952Google references in contacts app2020-03-24T21:36:48ZRik ViergeverGoogle references in contacts app[Forum discussion](https://community.e.foundation/t/eos-googled-version/12049/30?u=rik)
“Contacts” app still seems to be Google.
* [x] When you go in to “Contacts > menu (typical Google hamburger icon above left) > about contacts > pr...[Forum discussion](https://community.e.foundation/t/eos-googled-version/12049/30?u=rik)
“Contacts” app still seems to be Google.
* [x] When you go in to “Contacts > menu (typical Google hamburger icon above left) > about contacts > privacy policy” your default browser shows the Google privacy policy webpage.
* [x] The same thing happens in “Contacts > menu (typical Google hamburger icon above left) > about contacts > Terms of service” your default browser opens the Google terms of service webpage.IstanbulMohit MaliMohit Malihttps://gitlab.e.foundation/e/backlog/-/issues/877Update /e/ account's Creation UI2022-06-22T10:21:27ZVincent BourgmayerUpdate /e/ account's Creation UIGael Duval, [30.07.19 13:23]
![image](/uploads/6aed845d3d69b1539be15b45d61b977e/image.png)
Gael Duval, [30.07.19 13:24]
Je suppose que c'est https://FQDN (et non FQDN), peux tu me confirmer?)
Gael Duval, [30.07.19 13:26]
Je propose d'a...Gael Duval, [30.07.19 13:23]
![image](/uploads/6aed845d3d69b1539be15b45d61b977e/image.png)
Gael Duval, [30.07.19 13:24]
Je suppose que c'est https://FQDN (et non FQDN), peux tu me confirmer?)
Gael Duval, [30.07.19 13:26]
Je propose d'ailleurs qu'on fasse deux petites modifs pour cet écran:
- "Login with an other account" -> "Use a specific server"
- "Server URL" -> "Server URL (https://server_url)"IstanbulMohit MaliMohit Malihttps://gitlab.e.foundation/e/backlog/-/issues/773Notes Widget : the text is unreadable2020-04-10T07:03:44ZSerge FNotes Widget : the text is unreadable# Summary
Using lawnchair launcher, after the notes widget added on a desktop the text of each notes are unreadable because its background color is blue on black text.
# Steps to reproduce
Install /e/ on a device
Add your /e/ account
Op...# Summary
Using lawnchair launcher, after the notes widget added on a desktop the text of each notes are unreadable because its background color is blue on black text.
# Steps to reproduce
Install /e/ on a device
Add your /e/ account
Open Notes apps
Add some notes
Install Lawnchair launcher and start it
Add the notes widget on your desktop
# What is the current behavior?
Notes are not visible because the text color is black and background is blue navy color.
# What is the expected correct behavior?
Notes are visible in the widget.
# Possible fixes
Change the widget code in order to have text color in white...?
# Relevant logs and/or screenshots
![Screenshot_NotesWidget](/uploads/9e965869a3fab7fd872cc70d9b328260/Screenshot_NotesWidget.png)Istanbul