4 ms·
>How many people are capable of manually flashing an image onto a Nexus/Pixel, and then what subset of that group is interested in a "more secure" ROM? It's mo
by bubblethink 8y ago
>How many people are capable of manually flashing an image onto a Nexus/Pixel, and then what subset of that group is interested in a "more secure" ROM?
It's mostly their commercial clients. Very few regular people can use COS for recent devices (for free) since you need to build it from source.
- garyfirestorm 8y agoIt's not that hard. I'm a mechanical engineer who happens to care about privacy. I was able to build it by following a guide. There are many tutorials if you search. I don't have any degrees in computer science or IT, if I could build it I would guess anyone could.
- bubblethink 8y agoYeah, it's not hard. The steps are pretty well documented. It's just not very practical. You need to do it every month and flash manually. You lose the OTA mechanism unless you also set up an update server and hack on the code to point to your update server. I don't know how well that stuff is documented. In any case, all this is extremely niche. You need a good HPC like system to have reasonable build times. Note that you are also building chromium in addition to the ROM. The parent's point was about user numbers, and I am pretty sure that that's minuscule outside of their paid users.
- craftyguy 8y agoWell, you can't do any of that if there's even a hint of commercial use because of the CC BY-NC-SA license they (CopperheadOS) used. So you can basically only build it for yourself.
- detaro 8y agoAnd the uncertainty of what Creative Commons means for code. It likely extends to the produced binary. Does it extend to the use of that binary - are you violating the license if you use a phone with self-built CopperheadOS for work purposes?