Feedback for v1.9

/e/OS Smartphone Operating System Build Feedback
102

Vendor Name: Fairphone
Device name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: /e/OS 1.7-s-20230111250406-dev-FP3
Is the device Rooted / Not rooted: Not rooted

No issue with updating, now on 1.9-s-20230311268558-dev-FP3.
The following things work for me:

  • Call / be called
  • Send SMS / receive SMS
  • Notification LED
  • Alarm
  • Internet via Wi-Fi
  • Internet via mobile network
  • Wi-Fi hotspot
  • Location
    • Settings - System - microG - Self-Check: all ok, including location permissions
    • Settings - System - microG - Location modules - Mozilla Location Service: enabled, configured for using Wi-Fi and Cell
    • Settings - Advanced Privacy - Location: Exposed
    • Settings - Advanced Privacy - Manage my location: Use my real location
    • Settings - Location - Location Services - Wi-Fi scanning: enabled
    • Settings - Location - Location Services - Bluetooth scanning: disabled
    • Settings - Location - App location permissions - “Allowed only while in use”: Apps are listed
  • Compass
  • Screenshot
  • Main camera (original FP3 Camera module, not +) photo + video
  • Selfie camera (original FP3 Top module, not +) photo + video
  • USB connection to PC / MTP
  • MyPhoneExplorer 2.0
    (nightly 27.01.2023 - for sync with Betterbird instead of Thunderbird)
  • Bluetooth (music playback, data connection)
  • Exposure Notifications
    • Needed to be installed again according to documentation
    • Needed permissions again according to system notification and respective message in Settings - System - microG - Exposure Notifications
3 Likes
103 
Vendor Name - Fairphone
Device name - Fairphone 4
Device CodeName FP4
Version of /e/OS or Stock which existed previously 1.8.1 - s
Is the device Rooted / Not rooted - not rooted

Fine !

Thanks to the team.

105
  • Vendor Name
  • Fairphone
  • FP4
  • /e/os 1.8
  • rooted

update took some time but worked flawlessly - pleased to see that the (not working) lense is now gone (was no problem, just annoying). camera delay with moving objects seems faster now (will check this further).
thank you for the good work! never felt so satisfied with a phone/sw-combination :wink:

thomas

106
  • Vendor Name Samsung
  • Device name A3 (2016)
  • Device CodeName a3xelte
  • Version /e/OS previously 1.8-q-dev.
  • Device Not rooted

1.9-q-20230312268823-dev-a3xelte OTA download took longer than usual. I saw the download stop around 90% but was able to get it to resume. Actual update no issues.

Camera app (v 1.50.1) crashes on launch. As Post # 104.

Clear storage makes no difference. I did not notice the issue at first as I find Secure Camera performs better.

Edit It tuns out Secure camera takes stills but fails to take video.

In a logcat e.foundation Camera Errors start at this point.

03-20 10:59:55.956  2360  2360 I ExynosCameraInterface: INFO(HAL_camera_device_close[234]):camera(1) TORCH_MODE_STATUS_AVAILABLE_OFF
03-20 10:59:55.956  2360  2360 I ExynosCameraInterface: INFO(HAL_camera_device_close[236]): out
03-20 10:59:55.956  2360  2360 D ExynosCameraInterface: DEBUG:duration time(    5 msec):(HAL_camera_device_close)
03-20 10:59:55.956  2360  5570 V Camera2WrapperCbThread: Process: Exit Thread
03-20 10:59:55.958  2254  2254 I hwservicemanager: getTransport: Cannot find entry vendor.lineage.camera.motor@1.0::ICameraMotor/default in either framework or device manifest.
03-20 10:59:55.961  2403  2651 I CameraService: disconnect: Disconnected client for camera 1 for PID 2403
03-20 10:59:56.012  2403  2651 E CameraProviderManager: isHiddenPhysicalCameraInternal: Failed to getCameraCharacteristics for id 0
03-20 10:59:56.012  2403  2651 E CameraService: supportsCameraApi: Unknown camera ID 2
03-20 10:59:56.013  2403  2651 E CameraProviderManager: isHiddenPhysicalCameraInternal: Failed to getCameraCharacteristics for id 0
03-20 10:59:56.013  2403  2651 E CameraService: supportsCameraApi: Unknown camera ID 3
03-20 10:59:56.013  2403  2651 E CameraProviderManager: isHiddenPhysicalCameraInternal: Failed to getCameraCharacteristics for id 0
03-20 10:59:56.014  2403  2651 E CameraService: supportsCameraApi: Unknown camera ID 4
03-20 10:59:56.014  2403  2651 E CameraProviderManager: isHiddenPhysicalCameraInternal: Failed to getCameraCharacteristics for id 0
107

On the issue with the camera app being reported across devices
pl add your comments and logs where possible to the GitLab issue 
 dev team has been made aware of this issue being reported by multiple users

108

Hi @aibd there is already an issue on this #6761, you can add your comments under it. The testing team has closed #6782 as it is a duplicate.

109

Same thing on my a5xelte

Je confirme reproduire ton bug.

110

Have updated my samsung S10 plus from 1.8.1 to 1.9.
One weird thing is that I got the 1.9 update available a week ago, then about an hour later it disappeared, to reappear a couple of days later, permanently this time.

Does anybody know what is the logic/algorithm for updates availability? - I notice my S7 edge (running q) received updates at least a couple of weeks after my S10 plus (running s) gets them. I also see that some people in other parts of the world start upgrading days (or even weeks) before they are available on any of my phones.

Returning to the upgrade - the upgrade itself went ok and the phone is working well after upgrade. However, there is one issue: this version was supposed to fix advanced privacy (tracker management/blocking) in Shelter. Although I didn’t see it in the list of items fixed/added to the 1.9 version, I noticed that now Advanced privacy in my main profile (the personal profile) finally shows the apps from the work profile too (the Shelter’d apps). However, enabling or disabling tracker blocking on the Shelter apps doesn’t seem to have any effect - they are always blocked (unless I turn the tracker blocking feature completely off).

111

English bellow

RĂ©capitulatif
AprĂšs de nombreux essais avec diffĂ©rents recovery: /e/recovery, TWRP, OrangeFox, Lineage recovery, j’arrive toujours Ă  la mĂȘme chose en mettant Ă  jour vers 1.9-s. Quand je redemarre sur /e/, la version reste sur 1.8.1-s.
Que je fasse la mise Ă  jour via OTA ou adb sideload, c’est la mĂȘme chose.
J’en venais donc Ă  me demander si l’image proposĂ©e sur le site est bien la bonne.

Pour en avoir le coeur net, je tĂ©lĂ©charge Lineage-19.1-20230315-microG-gauguin.zip pour l’installer via adb sideload.
Le reboot se passe bien sur Lineage ce qui prouve que je réalise bien les bonnes étapes de mises à jour.
Mais, LineageOS est en version 1.8 datée du 03/02/2023 !!!

Le problĂšme ne pourrait pas justement venir de l’image de Lineage du coup ? soit c’est toujours la 1.8, soit c’est bien la version 1.9 mais sans que les Ă©lĂ©ments l’identifiant aient Ă©tĂ© changĂ©s ?

Merci pour vos aides.
Pour rappel :

Vendor Name Xiaomi
Device name Mi10T Lite
Device CodeName Gauguin
Version of /e/OS or Stock which existed previously 1.8.1
device Not rooted

English version
Summary

After many tries with different recoveries: /e/recovery, TWRP, OrangeFox, Lineage recovery, I always get the same thing when updating to 1.9-s. When I restart on /e/, the version remains on 1.8.1-s.
Whether I update via OTA or adb sideload, it’s the same thing.

So I was wondering if the image proposed on the site is the right one.

To be sure, I download Lineage-19.1-20230315-microG-gauguin.zip to install it via adb sideload.
The reboot goes well on Lineage, which proves that I am doing the right update steps.

But, LineageOS is in version 1.8 dated 03/02/2023 !!!

Couldn’t the problem come from the image of Lineage ? either it’s still 1.8, or it’s the 1.9 version but without the elements identifying it have been changed ?

Thanks for your help.

As a reminder:

Vendor Name Xiaomi
Device name Mi10T Lite
Device CodeName Gauguin
Version of /e/OS or Stock which existed previously 1.8.1
device Not rooted
112

Could also be build type (aka release channel) related, usually dev builds are out for a few days or a few days more, then stable builds follow (where applicable, not all devices get those) 


https://doc.e.foundation/build-status

https://community.e.foundation/t/howto-give-complete-e-os-version-info-easily-for-support-answers-comparison-etc/45030

113
  • Vendor Name Fairphone
  • Device name Fairphone 3
  • Device CodeName FP3
  • Version /e/OS previously 1.8.1-r-stable
  • Device Not rooted

The OTA upgrade to 1.9-s-stable showed up around noon, both download and installation went smoothly. After rebooting the device through the updater (no notification about a pending restart was given) the fingerprint sensor did not work as expected. Another reboot solved this issue, however, and the phone works flawlessly. Even the abnormal battery draining has somewhat disappeared.

2 Likes
114

Fairphone
FP3
1.8-r
Not rooted
The version upgrade to Android S came OTA with the update to 1.9.
All went smothly, taking approx 30 min including download.
Everything is working fine, as far as I can see.
Thank you to the team!

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

After checking effectlessly for a few days the update dropped in today.
Installation went smoothly, this time it asked for a restart.

First impressions:

  • Instant information was that my SIP-account got deactivated in Android 12. Though I regret that as I use it for communication on events with a DECT/SIP environment, I appreciate it a lot to be informed right away.
    Solved this by installing Baresip+, which seems to work flawlessly so far.

  • I noticed the restart of the battery statistics (no data from before the update).

  • Being new to Android 12 I found it strange that now another button opens the screen (sound down instead of power).

  • The fingermark sensor was useless as it didn’t work though accessible in the Settings, a fingermark was saved and the function turned on. Instead it didn’t open neither the phone nor the corresponding apps. I could solve that temporarily by recording a new fingermark, which changed the behaviour to the known.
    Sadly I deleted the “old” fingermark as to avoid confusion.
    Now there was one fingermark recorded - but the single one did not work anymore.
    It was impossible to record another one (adding greyed out), so I tried to delete the new one being able to record another to regain access to the ticket wallet and unlock the phone by fingertipping - to no avail: Deleting had no effect as the fingermark kept reappearing in the settings.
    So I tried a reboot (though I know that this doesn’t qualify as a repair technique) and luckily there was the old fingermark and the add-option was available again. Left two in the settings now.
    Seems solved so far.

  • Android 12 in general seems faster than 11 was, though a few things (design and paths) seem uncommon to me, and as for design I find few options to change, e.g. the clock on the lock screen.

We’ll see how the battery usage develops.

Thanks for the good work.

116

Here’s a useful one for the clock 


1 Like
117

Thanks for the hint, though it doesn’t make a difference.
The clock is still left bound and no other options are available (font, bounding, 12/24 hrs
).

Also the drop down menu at the start screen seems unchangeable, though it seems to me like a waste of space: There was more information ready before on less space and easier to access.

118

Android S seems to pick up contemporary design trends*, i.e. use of lots of white space. I think it’s highly debatable in many cases, seeing that a more compact design was possible without necessarily having too much information on screen.

*“Contemporary” refers to the time of its inception here.

1 Like
119

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

120 
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)
121 
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
122

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