Feedback for v1.9

Samsung S9+ SM-G965F
(purchased in /e/-shop)
not rooted
just updated from
e-1.8.1-q-20230203257075-stable-star2lte to e-1.9-q-20230310268292-stable-star2lte

e_star2lte-user 10 QQ3A.200805.001 eng.root.20230310.191910 dev-keys,stable-release

waiting for the the bliss pbm (4 days without icons automatic reorganization !) nor empty launch bar.

Note : seems to have a a battery drain (less than 12h from 100% to 20%).
Arnaud

Vendor Name - Fairphone
Device name - Fairphone 3+
Device CodeName - FP3+
Version of /e/OS or Stock which existed previously - 1.8.1-r (stable)
Is the device Rooted / Not rooted - not rooted

Thank you very much for the OTA r-to-s upgrade! That’s really great service. It ran smoothly and rather quick.

What I found:

  • Fingerprint wasn’t working after upgrade and first reboot. Since second reboot, all is fine.
  • Clock in locked screen was displayed weirdly (huge numbers in two line), there was an option selected to have it that way; I was able do disable that, so all fine.
  • Fonts are a bit too large in the options screen?
  • The worst bug so far: The note tool (“Notizen” in German) does not work anymore. It looks like it was deleted and reinstalled during upgrade (the button for the tool disappeared from the first “page” and was added as last button on the last page). When I start it first time, it crashed. Since then, it asks me which account I want to use, and I can choose between “xy@e.email” (my account so far, probably) and “New account”. If I choose the first, it crashes with this report:
App Version: 3.7.1
App Version Code: 3007001
App Flavor: ACCOUNT_MANAGER

Files App Version Code: 402060000OS 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: HTTP-Anfrage ist fehlgeschlagen mit HTTP-Statuscode: 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)

Vendor Name - Fairphone
Device name - Fairphone 3+
Device CodeName - FP3+
Version of /e/OS or Stock which existed previously - 1.8.1-r (stable)
Is the device Rooted / Not rooted - not rooted

It is crazy that I started a long time ago with v0.1x and Android 10 and now my FP3+ got Android 12. A big thank you to the team and I just donated to the cause. I encourage everyone here to also send some well deserved cash and donate as well. Even better, buy like me a cloud subscription so they have a steady income stream :wink:
Nothing is for free and they do a great job, thanks guys!

FYI I’m not affiliated to /e/, I’m just a happy user :heart:

3 Likes

Upgrade from 1.8 to 1.9 for redmi note 9 pro miatoll without problems.
I noticed just that e-drive process is always active (im not using murena account but my nextcloud instance) and drains my battery

I have problems with “Shelter” and “whatsapp” in shelter.

  • Update to 1.9 is done.
  • Whatsapp crashes every start
  • Uninstall WA in shelter
  • Uninstall shelter
  • Install shelter
  • Cannot start shelter, permissions problem…

Does anyone know a solution?

  • Vendor Name: Fairphone
  • Device name: Fairphone 3+
  • Device CodeName: FP3
  • Version of /e/OS or Stock which existed previously: 1.8
  • Device is not Rooted

Update worked fine. No issues till now.

By the way: Why are you reducing customisation options? E.g. why is there no option to change colours for the menu buttons as it was before? Why are there no options to get the round buttons back? Now there are only 4 buttons in quick view instead of 6. More freedom of choice would be nice for the next version.

4 Likes

Fairphone 3+
FP3
1.8r stable to 1.9s stable
Not rooted

Installed smoothly and still checking for any potential issues, but I am seeing the same VPN problem.

I run Proton VPN with kill switch enabled in settings. After a reboot or if I change VPN server the phone will not reconnect. The only solution I’ve found is to turn both wi-fi and mobile internet off and then back on. Connection is then made.

Other than this all appears to be working so far.

Welcome to Android 12.
Many users across many devices were and are as enthusiastic about the new Android 12 quick settings as you are :wink: .

I suppose this will be coming with V1.9? Great!

Stable builds might take some days more for the update?

1 Like

Hi @Manoj,

Can we still plan with a FP3/3+ v1.9 stable release today or will it be delayed to tomorrow ?

If you don’t want to wait, you can enable test channel following this instructions and then choose the stable upgrade. It worked OTA without any issue. I’ve done that because my FP3 is not my daily driver, otherwise I would wait a few more hours… I’m sure dev team will release it as soon as possible.
Cheers

Thanks for your answer. I can easily live with an upgrade tomorrow :hugs:. Some others might want to know as well ; some communication over it might be of some help

1 Like

The last update I had last night is that it has been moved forward to today, 21 March. Will check with the team, once they are in office, and update on this thread.

2 Likes

Thanks for your answer :+1:. It might be due to the camera issue reported by some people (Camera app not working since update 1.9 (#6761) · Issues · e / Backlog · GitLab) ?

Maybe, but probably not every /e/OS build or device is affected.
While my Fairphone 2 (1.9-r-dev) shows the issue raised in the GitLab, too, on my Fairphone 3 (1.9-s-dev) both cameras work fine (original modules, not +).

Good point then :+1:

The FP3 OTA OS upgrade build should be visible if you are on the v1.8.1 FP3 stable build

3 Likes

Aucune nouvelle version à ce stade.
FP3 Android 11 /e/OS 1.8.1-r20230204257076-stable-FP3

Have shared the feedback with the dev team reg the FP3 upgrade build not showing up. Will update

La mise à jour OTA est en cours !
La mise à jour s’est bien déroulée, tout semble fonctionner parfaitement ! Aucune perte de données.
Un grand merci pour le travail réalisé.