Reporting Fairphone6 firmware bugs -- where to report?

[pgfair]

I’ve a FP6 + e/OS 3.4, purchased via Murena in the US

I’ve filed a detailed bug @ their Gitlab re: issues with the Modem firmware, and failed MMI code dialing.

They confirm that it’s a Fairphone modem-code issue – and only in the hands of Fairphone devs; nothing @Murena can do.

So, I’m trying to file the issue @ Fairphone’s Gitlab.
Every time I attempt to create an account, my email’s refused,

Fairphone GitLab
1 error prohibited this user from being saved:
Email is not allowed for sign-up. Please use your regular email address. Check with your administrator.

regardless of which valid “regular email address” I use – whether the Murena email, the address I use here, any of my other mail providers’, or my own servers/domains.

Is there an admin contact for the Fairphone Gitlab lurking around here?
Or a moderator that can put me in touch?
So that I can get registered there?

[Ingo]

All we know that instance only existed for FP Open OS on FP2 and has been abandoned ever since.

Why was the GitLab instance (and FPOS) deprecated?

I’ve the same problem. Does a replacement for that GitLab instance exist anymore, even for solely the FP2? I remember being able to visit it a year ago, and Discourse isn’t a particularly competent issue tracker in the meantime, whereas ZenDesk is both private and entirely overwhelmed, (to the point of non-response to any technical report). Even if FP had considered a FOSS OS unmaintainable, I don’t see why a tracker isn’t desirable. ZD is a private and/or more formal version of Discourse, wh…

[urs_lesse]

Fairphone does not develop and maintain /e/OS, Murena does. I think you might have success here:

Report an issue

[pgfair]

It’s not an e/OS issue.
It’s an issue in the Fairphone modem firmware.

[yvmuell]

you can’t you have to contact support. There is no public bug tracker.

However as you have e/OS installed report it to Murena as Urs suggested

[pgfair]

As I said in my OP, i did.

Murena clarified that it’s not an e/OS issue, but in the modem firmware … which is developed/distributed by Fairphone. Not by Murena.

And needs to be taken up with Fairphone.
Which normally would entail filing a bug report.

That said, I understand that in any case I’ll not find support here …

[Ingo]

As fellow users we indeed can’t help you except pointing to https://support.fairphone.com/ which is how Fairphone as a company wants to be contacted.

[pgfair]

fair nuf.

sigh.

given the ‘abandonment and support issues’ mentioned above , this should be ‘fun’.

for reference for anyone else that stumbles on this while trying to get a firmware bug addressed – especially if on the Murena e/OS variant – just fyi:

Reading

The Fairphone (Gen. 6) - Build Instructions
https://code.fairphone.com/projects/fairphone-gen-6/build-instructions.html#fairphone-gen-6-build-instructions

"Fairphone (Gen. 6) makes use of Qualcomm’s single system image (QSSI),
 thus two source trees are needed: QSSI (higher level Android system) and
 target (most of the device specific code, including the Linux kernel).
"

references two binary-only components

Android 15 (QSSI)
Android 15 (target)

available – as blobs – at

The Fairphone (Gen. 6) - Binary Blobs Package
https://code.fairphone.com/projects/fairphone-gen-6/binary-blobs-package.html

to be used as includes – in the e/OS (or any derivative ROM) build

‘QSSI’ contains closed-source components related to the generic QSSI
; not specific to FP6 device itself, but required for base chipset functionality.

‘target’, otoh, contains closed-source specific to the FP6.
THIS includes firmware and drivers for the device’s specific hardware configuration – specifically including the modem firware that interfaces with the device RIL.

The blobs’ license is pretty clear:

“Fairphone grants you a free of charge, non-exclusive, non-sublicensable, non-transferable, limited copyright license to download, install and use the Software for non commercial purposes only on a Fairphone 6 device in machine-readable (i.e., object code) environment. You are not allowed to use the Software in any other way. You are also not allowed to remove portions of the Software, alter or otherwise modify it, or translate, reproduce, copy, reverse engineer, reverse compile, disassemble or transfer the Software.”

, and appears to explicitly prohibit a “3rd-party” like Murena from fixing a bug in, e.g., the modem firmware, or even reverse engineer or decompile to troubleshoot.

Addressing the bug rests with Fairphone, either to address it directly, &/or with Qualcomm.

[rokejulianlockhart]

@pgfair

I’m trying to file the issue at Fairphone’s GitLab. Every time I attempt to create an account, my e-mail’s refused.

@pgfair, at which URI did you attempt registration? (gitlab.fairphone.com/users/sign_in?) If so, the registration page is solely visible due to what ≥ gitlab.com/gitlab-org/gitlab/-/issues/580919#note_2937543214 describes.

Regardless, the best way to report a bug to FP is to: ^[1]

1. create a post at this Discourse forum (especially, if you’ve Beta access), then

2. create a report at Google’s Buganizer instance, in its AOSP component, using the Developer Bug Report template (or the wizard, depending upon what you are able to access, without the permissions that I possess) that cites the Discourse post, then

3. create a ticket at FP’s ZenDesk instance, that references both.

To demonstrate this:

Settings's facial recognition detection caused it to crash

@rokejulianlockhart to clarify, the fix we’ve staged specifically targets that SIGSEGV in libanc_faceid_jni.so related to the nativeSetConfig JNI call. I can’t confirm yet if this also resolves the LiteManager issue, as it wasn’t the primary target of this investigation. If it does clear up, it’s likely due to an indirect dependency on the memory management we patched. If you’re still seeing crashes there after the update, let us know and we’ll have a look at it as a separate case.

Additionally, if you know that Qualcomm provides this firmware, report it to them.

---

1. reddit.com/r/fairphone/comments/1pv8zc4/comment/nw08mk6 ↩︎