> CopperheadOS currently supports the Nexus 5X and Nexus 6P as a free offering. Pixel and Pixel XL support is available as a product.
They show a Nexus 5 on the landing page for CopperheadOS. Why not show a supported device?
Review: Copperhead OS
91–100 of 162 posts
Re: Review: Copperhead OS
#92Earlier quoted context omitted.
> Sometimes I am wondering what Google employees think when they read headlines like this one. Hello Google employee here! I suspect we don't all have the same opinion but I can share my own since you asked. Note that I work in Cloud so I work in an area far far away from this stuff and opinions are obviously my own. Frankly the headline makes me a little bit sad because of course I would like to make things which pe…
You might be a Google employee, but you do not seem to be an Open source proponent. That's you prerogative, but you completely miss the point of the discussion if you ask why should users want to be independent from proprietary services. Sure, 99% don't want that and would click any colored and shiny button if it promises them a free Justin Bieber ringtone, but this is not the topic of the thread.
Cloud services are probably the thing that is the farthest away from being open-source non-proprietary software... and he is working on cloud services, so I can understand where he comes from...
Re: Review: Copperhead OS
#93I may have to go this or a similar route, to go back to using WiFi and Bluetooth on my ~5.5 month old Motorola G5+ [1].
I mean, come on! Ship a patch/update, already!
1) That replaced a bootlooped ~1.4 year old Nexus 5X. Wasn't going to spend big bucks after that burn and while waiting for the Pixel 2 or Samsung whatever, or Apple's new line, to drop in a month or two.
And now, with all the crap going on with all those various new models...
I've griped about this, before, but damn it, they deserve the criticism. And the only time they make positive changes seems to be when the public image and pressure get bad enough. (And things get worse again, as soon as that pressure relents -- or gets distracted.)
Re: Review: Copperhead OS
#94I think there are some misconceptions in this thread (due to the title). Personally I use CopperheadOS as my daily driver because it stays continually ahead of Google (and groups like AOKP, LineageOS etc) in terms of Android hardening. It goes well beyond just not having Google Play services. See their details on their approach and design: https://copperhead.co/android/docs/technical_overview They make continued patc…
Copperhead uses Grsecurity, and I used to use Grsecurity, when it was widely available, now that it's not and the developer has decided to act in hostile ways to the Linux community(1), it's made me rethink using his work and/or supporting him. Plenty of consultants make do fine without resorting to closing off their source code, and decide to act better with the community and/or companies.
(1) https://www.theregister.co.uk/2017/12/22/grsecurity_defamati...
Re: Review: Copperhead OS
#95Earlier quoted context omitted.
My hope is in the Halium Project https://halium.org/ Now I'm running UBPorts in my Nexus 5 https://ubports.com/ Edit: if you are downvoting this comment, please explain why at least. It improves the conversation. Thank you.
So do you consider UBports stable on your phone
Yes I do. It works great after the recent OTA-3 release.
Re: Review: Copperhead OS
#96Earlier quoted context omitted.
What functionality is AOSP missing that is necessary to pass Android certification?
See, e.g., https://twitter.com/CopperheadOS/status/907720250501844994 It's mostly not functionality missing to pass the CTS, but just broken untested AOSP-only code (that is replaced by Google closed source code in Google builds).
These only fail because there is extra unused noop functionality in AOSP that CTS complains about (a bug in AOSP), not because Google services are required to pass CTS.
Re: Review: Copperhead OS
#97Earlier quoted context omitted.
My hope is in the Halium Project https://halium.org/ Now I'm running UBPorts in my Nexus 5 https://ubports.com/ Edit: if you are downvoting this comment, please explain why at least. It improves the conversation. Thank you.
Is Halium an old project? If it is, I imagine everything just got a whole lot easier with Project Treble and with the new six-year LTS Android kernels.
No, it's a fairly new project and the devs are pretty active.
The best place to keep you updated about Halium is their Telegram group https://t.me/halium
Re: Review: Copperhead OS
#98Earlier quoted context omitted.
See, e.g., https://twitter.com/CopperheadOS/status/907720250501844994 It's mostly not functionality missing to pass the CTS, but just broken untested AOSP-only code (that is replaced by Google closed source code in Google builds).
These only fail because there is extra unused noop functionality in AOSP that CTS complains about (a bug in AOSP), not because Google services are required to pass CTS.
The point was that AOSP isn't a perfect base, because the Android team obviously don't care enough to actually test it, not that Google services are required.
Re: Review: Copperhead OS
#99Earlier quoted context omitted.
I use that but it's all Google based. Not sure if you can decouple it from Play Services without breaking everything.
LineageOS runs fine without Play Services. It's actually the default mode. It just limits your app choices. My needs are simple so I don't really mind, and I appreciate the improved battery life and speed. It turns out many apps from the Play Store don't actually have a hard dependency on Play Services. Example: Slack works, except for notifications and (IIRC) receiving calls, which is good enough if you don't need t…
Same with Discord. I don't get any notifications from Discord on my de-Googled LineageOS devices, but the application works just fine (although I had to silence its constant notifications about Play Services).
Re: Review: Copperhead OS
#100Ain't here maps a good alternative to google maps? I use both of them 50/50 and I love the offline capabilities of here maps