Feedback for v3.7

[olli0371]

May be switch off, remove battery and remove SIM card.

Then put everything together and try again

Best regards

Oliver

[Napalm45]

Vendor Name Samsung

Device name Galaxy S10

Device CodeName SM-G973F

Version of /e/OS or Stock which existed previously 3.7-t-20260412607474-community-beyond1lte

Is the device Rooted / Not rooted No

I have a problem on pdf viewer. It’s not possible to open pdf via MJ pdf. I install another viewer and sa me problem. I can’t also send mail with pdf inside..

I also got problem with Keepass which don’t want to sync my database. That said nullPointer. No update are did, Just the update from 3.6 to 3.7.

Thanks to dev team

[feko]

I tried that also, sadly it did not help.

[Lionel.R]

I have the same issues on my S10 since the update from 3.6-t to 3.7-t.

I found a workaround by installing another file manager App ( fossily file manager) and I’m now able to open my pdf files and my keepass database files from fossily file manager.

The bug seems to be in the default file app. Clearing cache and stockage didn’t help….maybe it’s time to upgrade our S10 to v3.7-a16 !!!

[ericht]

1. Vendor Name: Fairphone
2. Device name Fairphone 3+
3. Device CodeName ?
4. Version of /e/OS 3.7
5. device Not rooted

I also facing issues with KeepassDX 4.3.3 and e/os v3.7:

My KeepassDX file is synched with syncthing. After updating to v3.7 I couldn’t open my keepass file anymore (no reaction at all after pressing the “unlock” button). I had to uninstall KeepassDX, install KeepassDX v4.3.2 and resynch the file to be able to open it again. Only installing the older version did not help. The behavior was the same after updating again to KeepassDX 4.3.3, meaning it is reproducible. But I could use KeepassDX v4.3.3 with e/OS version 3.6. This points to an problem of e/os and not of KeepssDX. I hope you could fix it.

Anyhow - thanks for your support and a your good work so far!

PS: clearing cache and reboot does not help

[p4tr1ck]

• Vendor Name: Murena

• Device name: The Fairphone (Gen. 6)

• Device CodeName: FP6

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

• Is the device Rooted / Not rooted: Not rooted

The random reboots are gone. Thanks for fixing this!

[detomassino]

• Vendor Name OnePlus

• Device name 9pro

• Device CodeName lemonadep

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

• Is the device Rooted / Not -not rooted

Hello, the update went smoothly with very fast download.

Leverything seems to be working including the usual culprits Revolut, starling and amex UK.

Thank you very much for another great update.

[Napalm45]

Thanks Lionel, that works for me ! I Will check for going to a16 if it’s possible, I have to check a tuto to do this..

Thanks again for your help you save me

[Tentos]

@macalca

It’s absolutely impossible to activate WhatsApp on my brand new Fairphone 6, neither by downloading the application from App Lounge nor from the official WhatsApp website.

Hello @macalca , you are the second one in a short amount of time that has reported a WhatsApp problem on the FP6 , see Unable to activate whatsApp on fairphone 6 with 3.6

I unfortunately do not have a solution. Similar problems have been reported before a couple of years ago, see You need the official WhatsApp to log in erroror message

@Manoj : This may be something the developers should look into - maybe WhatsApp currently recognizes the FP6 (and other devices) with /e/OS where WhatsApp is used for the first time as “compromised” or something similar?

[Tentos]

@Manoj

• Vendor Name - OnePlus
• Device name - OnePlus 6
• Device CodeName - enchilada
• Version of /e/OS or Stock which existed previously - e-3.6-a15-20260315594305-community-enchilada
• Is the device Rooted / Not rooted - rooted (Magisk)

No problems with the update, no problems detected so far.

I have had a strange problems in the context of the last and this update: I usually do a backup before the update and export my contacts (which are only saved on the device, not synced to Murena Cloud or another external service). I have observed that some newly added contacts have disappeared - they were also not included in the contact export file.
I currently cannot say when (and how) the contacts disappeared. Fortunately, I could restore them because they were added from WhatsApp. As I use XPrivacy Lua, i.e., not really “vanilla AOSP” when it comes to contact access, this may be the reason. I will see whether I can reproduce (and hopefully solve) the problem.

[Albati]

• Vendor Name: Murena

• Device name: Fairphone 3

• Device CodeName: FP3

• Version of /e/OS or Stock which existed previously: 3.6 t→ 3.7 t official

• Is the device Rooted / Not rooted: not rooted

Smooth and fast update, not problems so far.

Thanks for your great service.

[macalca]

Hi Oliver, did you read my previous message carefully? I said I tried it from App Lounge and also from the official WhatsApp website. In your opinion, is the app from F-Droid more “authentic” than the one from the WhatsApp website, so that it’s recognized as official? mmm I don’t think so.
It’s possible that my number is NOW banned—marked for having tried it several times, I repeat, NOW, but it wasn’t the first time I tried. And I’ve also tried with another number that wasn’t previously registered on WhatsApp (a completely new mobile number), and it won’t let me register that number either.

[Bacartely]

Hello, thank you very much for your work, but I experience a severe issue. Here is my device’s information :

1. Vendor Name : Fairphone
2. Device : FP3
3. CodeName : FP3
4. Previous e/OS version : 3.6
5. Not rooted

I cannot be absolutely sure that my issue was caused by the update, but it seems so. This week, synchronization issues appeared with the application Orgzly : namely, it is now unable to read the related files on my file system. I investigated and it seems that the file system itself has weird behavior : I can no longer copy/move files with de default file manager. However, it works with Fossify File Manager. So far, Orgzly seems to be the only app affected.

I opened a topic concerning this issue, I would appreciate any help that anybody could give me.

Thank you for your attention

Best

[_mm3]

I think this might be something related to /e/os or MicroG. I’ve been using custom ROMs for ages, and when I tried /e/os for the first time, the WhatsApp error happened and I haven’t got rid of it since. It seems my account became permanently flagged and I can’t use WhatsApp with unlocked bootloader any more.

[obdi]

Same issue here with Pixel 5 (redfin).

Password DB could not be opened anymore.

Even using older version KeepassDX 4.3.2 nor using KeepassDroid did not help.

I can confirme as well, that the installation of KeepassDX 4.3.2 is not possible with standard file manager, by using fossify file manager the installation of KeepassDX 4.3.2 was possible.

My temporary workaround is to use the password manager provided by murena.io.

@Manoj: Would it make sense to add a test case with a local password manager? If yes could u please share which one has been used?

Best

[mark.a.podesta]

1. Vendor Name - Oneplus
2. Device name - Nord
3. Device CodeName - Avicii
4. Version of /e/OS - 3.5
5. Is the device Rooted - yes

No wifi after updating, and unable to sideload magisk

[PLA]

Vendor Name: Google
Device name: Pixel 5
Device CodeName: Redfin
Previous Version of /e/OS: 3.6-t-20260312593432-official-redfin
Version of /e/OS: 3.7-t-20260412607473-official-redfin
Device: Not rooted
Bootloader: Locked

As some others, the download was very fast (~2 mn), but the update itself took hours.
It seems the progress bars run faster while the phone hasn’t enter lock mode (after being idle or manually locked).

No problem so far, apart the ‘as usual’ :
The Advanced Privacy “frenzy” is still here, since 3.2.
I have to toggle off the ‘Tracker control’ flag to calm it down.

KeepassDX runs fine; its database is in the space managed by Nextcloud sync app.

And, as others, I worry about Android 13 being obsolete and not receiving security patches since february (correct me if I’m wrong).

For an OS that claims to be privacy centered, being so much loose on security starts to worrying me.
And not talking about Gael Duval repeated stands against really secure OS…

[Warsiepuma]

Fairphone

FP4

FP4

Previous version: 3.6

Not rooted

At 3.6, Google maps stopped working (always offline) and so did Strava GPS tracking. At 3.7, it’s working again, but the GPS tracking in the Strava app is still not working. Not sure if it’s related

[santa-klaus]

1. Vendor Name: Fairphone
2. Device name: FP3+
3. Device CodeName: FP3
4. Version of /e/OS or Stock which existed previously: 3.6
5. Is the device Rooted / Not rooted: not rooted

Since I updated I cannot open the majority of my files, such as pictures and my keepass database. Reboot did not solve the problem. New files (new photos/screenshots) can be opened, however downloaded pictures can’t. More details here:

Cannot open files after upgrade to /e/OS 3.7 on FP3

I’ve just discovered the exact same issue, with a bit more sensitive use-case to say the least: I’m no longer able to open up my KeePass database. /e/ OS version 3.7-t-20260412607473-official-FP3 Build number TQ3A.230901.001 A fairly critical issue to leave in an ‘official’ build, especially given that Android 13 no longer gets security updates; what was the point of this update for FP3 again…? EDIT because ‘replying too quickly’(???): Many people are reporting the same issue in the 3.7 bu…

Issue with the file system

I have also file access Problems on my FP3 since eos 3.7-t official Problems play Audiofiles: Voice Audiobook Player plays no more Musicolet plays only in restricted mode Game Emulator ScummVM don’t find any files no more

[Lepanto]

I have a problem of low volume when i call (or receive call), if i put on loudspeaker it’s good… i try to reboot the device but nothing happend

Vendor Name: Fairphone

Device name: FP4

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

Is the device Rooted / Not rooted: Not rooted