After doing the OTA upgrade to 3.7 on my FP3, I cannot open most files on my phone anymore. The files (both in internal memory and on the SD card) are still shown in the file manager (with thumbnails in the case of pictures), but:
trying to open them will not work (e.g. opening a picture just shows a black screen in the gallery app)
trying to access the file from another app, e.g. uploading or sharing, results in an error
This problem first appeared after completing the upgrade to 3.7. I have rebooted the phone several times, but the problem persists. My version is:
3.7-t-20260412607473-official-FP3
I would appreciate a quick solution for this, as my phone is practically unusable now.
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 build feedback thread, not just FP3 owners either.
(āNew users are only allowed to post two links.ā Really?! Limiting cross-thread linking?)
Yes, I had the same issue with Keepass. Thank you for replying and linking the other reports.
Interesting enough: Opening some new files (e.g. screenshots, photos) works, others not (e.g. downloaded pictures). Feels like the file creation date might play a role in this, and thatās what causes problems in downloaded files?
I havenāt been able to find any correlation between file ctimes, atimes or mtimes and the ability to open them.
I think itās some kind of missing permission for the default Files app (com.android.documentsui).
If I try to open a photo from the Files app using the Gallery app, the Gallery app opens but with a blank white space instead of the photo.
If I open the Gallery app, I am able to open all the photos that show up there.
If I install the Fossify File Manager (mentioned by another FP3 owner with the same issue: Feedback for v3.7 - #76 by Bacartely) and I grant it the special āAll files accessā permission it asks for, I am able to open photos from the Fossify File Manager using the Gallery app (so no more blank screen like when doing the same with the Files app).
The problem with this approach is that all my KeePass databases use a keyfile. The KeePassDX app uses the Files app (Documents UI) as a file picker for the databases but also for the keyfiles, so even though I can let the KeePassDX app read the database now (opened with Fossify File Manager), I still have to use the Files app to select the keyfile, which the KeePassDX app still cannot read.
I will however not create a new mail address to be able to register. I do not think this is a reasonable expectation, and posteo is definitely not a typical source for spam as you have to pay for mailboxes.
Yes, this seems to somehow degrade over time from a userās perspective.
At first you could simply write an email to helpdesk to get access. When helpdesk went to being exclusive for paying customers, the page referred to this forum where @Manoj provided the necessary help. Now it seems they streamline the process by simply requiring Murena accounts.
Murena can make a case for all of this being sensible (limiting helpdesk to paying customers is a valid business decision, and using the forum detour looked more like a fuzzy workaround than a solution, getting a Murena account instead is more clear and defined), but in the end itās just raising the hurdles higher and higher for users to report issues in the way Murena want to get reports.
Itās Murenaās loss of valuable user interaction and satisfaction in exchange for the process looking better from their side.
There is a reason behind wanting users to create Gitlab issues. Developers need logs to help with the debugging process. That way the developer can directly interact with the user. We have seen issues which are location, service provider specific which slip though QA testing.
The Murena Workplace account require was more to check spamming that was rampant on the gitlab as it was on the forum.
Initially we kept the rules simple to help all users but soon found that there were a large number of spam accounts and people who tried to block our services from being efficient. These checks have been introduced to prevent and detect misuse of the gitlab and forum.
I agree with @AnotherElk, and I will not create two additional accounts (when I have a perfectly working email address), to be able to raise an issue on gitlabs - which I otherwise would have happily done. There are plenty of other spam protection measures that work well enough for thousands of other services out there.
This is not the main problem here, though, the main problem is that I canāt open the majority of my files since the update. @Manoj is there solution in sight for that?
I am happy to provide logs, but refuse to create a new mail address to be able to do so.
Didnāt you come to /e/ because you were forced to use an app by your IT department? You should be able to understand why people dislike being forced to use a specific service. Itās just not functional. Should I monitor one more mail inbox, on top of the five I already have, for notifications on gitlab? Itās just stupid. If you want people to contribute you have to find a proper spam protection, not lock them out.
This is the process the team has set due to rampant spamming. I conveyed the message the developers shared. They need logs to debug and they will have further questions for you. The developer would want to directly get in touch with you. That only happens with an issue on gitlab. You can always delete the account after your issue is resolved.
Hello, thank you for your answer, I have marked my related topic as solved. However, I am now stuck with the downgrade. I tried what you mentioned and there is the result :
Local update does not work, I obtain the error āFailed to import local updateā, I suppose this is another bug of the file systemā¦
My recovery mode does not have this option.
My recovery mode does not have this option.
Does not work, I obtain the error āUpdate package is older than the current buildā.
In addition, I made a reset to factory but it did not help, I am just much stuck with my phone now. With few searches, I saw that it is possible to obtain the downgrade by other way, but I donāt want to do a bad mistake. Do I have to reinstall completely from the terminal ?
sorry, the āanti-rollbackā feature is efficient.
BECAUSE YOUR BOOTLOADER HAS BEEN RELOCKED, and because unlike expected, even dropped by Gogol, āAndroid Security Updateā have been backported by Lineage developpersā¦ so the index have been updated
ouch ! ā¦
. . .
yes,
But donāt relock the bootloader in 3.6 if unlocked today with 3.7 registred in the index !
