@Johann doesn’t this sentence from the license, if interpreted strictly: 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 2 device in machin…

Well, the distributed Firefox OS package is blob-free, but it still requires the blobs to work, so it doesn’t really work without the binary blobs. From what I’ve gathered what you’re referring to is just a sort of a workaround that downloads the blobs from the phone and integrates them to the distr…

Yes, you are right the Fairphone 2 builds will be blob free, but you will still need the proprietary blob in order to make the builds. This depends on the fact that not all Fairphone 2 drivers are free and open source.

This “issue” is really bothering me. How do other custom rom developers circumvent such a license issue? I think this is the same for many other phones out there. Replacing parts with opensource code, but the rest? Please fix this license:(

[image] Arvil: And I know FP’s official answer to “can we share our ROMs ?” is “no” for a reason. The reason is that Fairphone as a company certainly can’t publicly say that we should share the blobs. What private persons do is a different story. You are right, though, that this issue should…

As there are so many struggling with selfcompiling here my,question: Do the builds contain in any way personal data? I guess no. So is there a problem to share a build anonymously? And directly refering to this question: do the final builds have the same checksum? so can we publish checksums and e…

I guess, this post answers both of your questions: [image] [HOWTO] pencil2 Compiling Fairphone Open OS / Rooting Development I don’t think checksums are usable, the build contains information about your username, computer name, date/time, kernel on your computer etc. But …

[image] bigCrash: Do the builds contain in any way personal data? I guess no. So is there a problem to share a build anonymously? The question is also whether other people would want to flash anonymously posted ROMs. I personally wouldn’t unless there are means to verify that the ROM is indee…

@tphysm yes, this is answering all my questions. Thanks! @jftr Very true, indeed. Then i think people have to learn to compile the code by themselves. Maybe with a better tutorial, though i do not know where the difficulties lay, besides maybe installing linux :frowning:

[image] bigCrash: Do the builds contain in any way personal data? I guess no. So is there a problem to share a build anonymously? Define a) “personal data”, b) “share a build anonymously”, oh and c) integrity :slight_smile: a) There are some scripts that add the username/host/timezone/dates …

[image] fp1_wo_sw_updates: a) “personal data” Data which might identify me clearly. Clearly enough to get sued by the rightsholders. [image] fp1_wo_sw_updates: b) “share a build anonymously” Upload it via VPN to an OCH (mega,zippy,etc…)… [image] fp1_wo_sw_updates: c) integrity …

FP2: License for binary blobs

Participate Development

tphysm February 17, 2016, 12:09pm 27

I guess, this post answers both of your questions:

1 Like