@satchmoz not as much commentary on #CopperheadOS, but it was brought up in discussion: https://talkgroup.xyz/t/my-phone-is-dying-what-should-be-my-next-mobile-device/293
I would hate to spend that much money on a phone. I ended up going with a #Nextbit #Robin ($150 now the company was bought and support has ended) loaded with #LineageOS, sans gapps. It hits enough points, and is *very* pretty, though that wasn't a requirement.
@maiki @GenTollis it came up a few tines on replicant dev forums. Incidents with non AOSP camera apps being shipped that were not entirely compliant. (though I think that reverted) I know some people were striping the first time run wizard from cyanogenmod towards the end out of freedom concerns.
@GenTollis @satchmoz I've been an avid user, but I don't really track the project's politics, unless it means I lost support for a device. But there is https://en.wikipedia.org/wiki/CyanogenMod#Commercialization_controversy.
@GenTollis @maiki not quite what I remembered but close. CyanogenSetupWizard required proprietary google components. https://github.com/nvllsvm/freecyngn/blob/master/README.md
@maiki @GenTollis Looks like LineageOS has been fixing these things. https://github.com/nvllsvm/freecyngn/issues/40
@satchmoz I should know that, but I don't. I did intense research a few months ago, and decided #LineagoOS was okay, but dumped the facts from memory.
@maiki Would you happen to know if LineageOS is taking a hard stance against the kinds of proprietary componants that were slipping into CyanogrnMod toward the end?