Feedback for v3.7

Release Information

Please share feedback on v3.7 build for your device and let us know how it is working with applications that you use.

- We will be releasing a v3.7.1 build starting today for all devices except those on A13. The changes in v3.7.1 are given in the release notes.

  • The following release came as a part of v3.7
    • v3.7.1
    • v3.7.2
    • v3.7.3
  • You can check the details of what came in each build in the release notes.

:backhand_index_pointing_right: Release Date: 16 - 24 April (for v3.7)

:backhand_index_pointing_right: Release Notes

(Sharing details in advance as some users have requested that they be given an advance notice of a release)


Feedback poll

We will also have a poll to rate this build.

  • I have updated to v3.7 on my device and it is working well
  • I updated to v3.7 but I am having issues (Please share the issue details on this thread)
  • I am not able to update to v3.7 (Please share the issue details on this thread)
0 voters

:backhand_index_pointing_right: To report issues with the build or applications raise an issue on gitlab. Ideally first discuss the issue here and check if users of the same device on this build are having the same issue.

When sharing your feedback or issues, Please add the following details

  • Vendor Name

  • Device name

  • Device CodeName

  • Version of /e/OS or Stock which existed previously

  • Is the device Rooted / Not rooted

Refer this table for vendor, codename details

Refer this guide to share more details in your feedback


:warning: Do not share test build information on the forum or in this thread

  • This thread has been created specifically for posting information on official and community /e/OS builds.

  • To understand the difference between build types refer this guide

  • Please do not post information or links to /e/OS test builds on the forum.

  • The test builds are as yet untested and under development and may in some cases cause user devices to soft brick.

  • Such information can confuse other users who do not see these builds in the updater.

  • Remember not all users who come to this forum are experts in installing and formatting custom ROMs and can end up seriously damaging their devices by trying out these test builds

  • If you are genuinely interested in helping with the testing activities and also understand how to fix and do some minor level of testing on custom ROMS, you are welcome to join the testing team

  • As part of the testing team you can share your comments on the dedicated testing telegram channel.

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services

7 Likes

Will the FP6 get the A16 in this round ?

Everything looks fine so far. Thanks a lot :+1:

1 Like

A16 for FP6 is still under development. Not due with v3.7. Will share the release once we have the build ready.

7 Likes
  1. Vendor Name: Samsung
  2. Device name: S5e
  3. Device CodeName: gts4lvwifi
  4. Version of /e/OS or Stock which existed previously: 3.6 → 3.7 community a15
  5. Is the device Rooted / Not rooted: not rooted
  6. Bootloader Locked / Unlocked: unlocked

All good

  • Vendor Name: Oneplus
  • Device name: 9
  • Device CodeName: lemonade
  • Version of /e/OS or Stock which existed previously: 3.6 a16
  • Is the device Rooted / Not rooted: not rooted
  • Bootloader Locked / Unlocked: unlocked

No problems detected since update.

Thanks a lot.

* Vendor Name: Fairphone
* Device name: The Fairphone (Gen. 6)
* Device CodeName: FP6
* Version of /e/OS or Stock which existed previously: 3.6
* Is the device Rooted / Not rooted: not rooted

Update was smooth and fast. No issue so far. Thank you! :wink:

  • Vendor Name: Oneplus

  • Device name: 11

  • Device CodeName: salami

  • Version of /e/OS or Stock which existed previously: 3.6 A16

  • Is the device Rooted / Not rooted: not rooted

Everything good so far. Thank you again!

No issues so far - Thanks a lot :balloon:

1 Like
  • Vendor Name: Fairphone
  • Device name: FP4
  • Device CodeName: FP4
  • Version of /e/OS or Stock which existed previously: 3.6
  • Is the device Rooted / Not rooted: not rooted
  • Bootloader Locked / Unlocked: don’t know (haven’t touched that)

Got hit by bug FP4: Reaching charging control limit triggers a fast charge/non-charge loop (#8383) · Issues · e / Backlog · GitLab

Fortunately the workaround mentioned in Gitlab seems to be working.

No other problem so far.

1 Like
  1. Vendor Name: Sony

  2. Device name: Xperia XA2

  3. Device CodeName: Pioneer

  4. Version of /e/OS or Stock which existed previously: 3.6-a16

  5. Is the device Rooted / Not rooted: Not rooted

I updated to U-community 3.7 a16, everything works fine. Thank you guys.

1 Like
  • Vendor Name: Murena
  • Device name: FP4
  • Device CodeName: FP4
  • Version of /e/OS or Stock which existed previously: 3.6
  • Is the device Rooted / Not rooted: not rooted
  • Bootloader Locked / Unlocked: don’t know (haven’t touched that)

Stock Mail APP keeps on crashing when sync is activated. Keep fingers crossed this will be resolved by A16 release.
Hadn’t yet the opportunity if the too low sound level of incoming call being resolved.

So far, no other issues. Thanks to the developers & test community :sparkles:

1 Like
  1. Vendor Name: Murena
  2. Device name: FP4
  3. Device CodeName: FP4
  4. Version of /e/OS or Stock which existed previously: 3.6 (I think)
  5. Is the device Rooted / Not rooted: not rooted

The update went smoothly. But… I always used the default keyboard and it had this nice convenient button to switch languages with one tap. Now it has been replaced by a smiley button and I have two taps to switch languages which is really not convenient when switching often like I do.

1 Like
  • Samsung
  • S10e
  • beyond0lte
  • Version previously: 3.6-a16-community
  • Not rooted

Update went smooth and fast. No issues so far.
Thanks to the team maintaining this device.

3 Likes

You may switch keyboard-language by long-pressing the space-bar.

Does that suffice?

1 Like

No issues so far - Thanks a lot :balloon:

1 Like
  • Fairphone

  • FP4

  • FP4

  • Previous version: 3.6

  • Not rooted

The call volume is still much too quiet at maximum setting, even though it was supposed to be fixed on 3.6. There was no difference then, and still no difference.

I have a hard time hearing phone calls even in environments that are not that loud.

4 Likes

Hi Sami,
I have added your FP4 low call volume feedback here Issues reported on v3.6 (#9277) · Issues · e / Backlog · GitLab (though this gitlab issue refers to 3.6).
Thanks

1 Like

Hi!

This charging problem occurs sporadically at my FP4. Maybe once in a month.

But the data transfer issue occurs permanent. When I want to copy photos to the computer (Ubuntu) it only works after a reboot of the phone.

  1. Vendor Name: Nothong Phone (1)
  2. Device name: A063
  3. Device CodeName: Spacewar
  4. Version of /e/OS or Stock which existed previously: 3.6
  5. Is the device Rooted / Not rooted: Not rooted

Update went smooth, most thing function fine. But. 3.7 broke my fingerprintscan. When searching for the setting in the settingsmenu I can find the setting, can see that there is a fingerprint stored, but I cannot remove or add another fingerprint. When scrolling in the settingsmenu and looking for the setting for fingerprints, this disappeared from ‘lockscreen’ part of the settings. The fingerprintscan symbol is still shown on the lockscreen, but doesn’t function. In all the apps that support fingerprint to proceed, the fingerprint is broken as well.

AA gave me some trouble when updating to 3.6, I did a quick test in 3.7 and all seems fine. O, and since 3.6 my battery duration improved a lot. Thanks for that!

1 Like