$600 Chromebooks are a dangerous development for Microsoft

Re:$600 Chromebooks are a dangerous development for Microsoft by nextos on Saturday September 01, 2018 @12:47PM (#17892679)

Why not? I'm running vanilla AOSP with F-Droid apps only. No Google Apps framework.

Threats are limited then to regular baseband radio issues. I know I could be doing better if we had open hardware, but that's the most practical solution I can implement today I think.

[ Parent | on HN ]

Re:$600 Chromebooks are a dangerous development for Microsoft by Fnoord on Saturday September 01, 2018 @01:17PM (#17892841)

That does solve the tracking issues, parent assumed you flashed OpenGapps w/it.

You can also run microG (LOS + microG I recommend; what I use on my smartphone) which contains UnifedNlp for location services.

[ Parent | on HN ]

Re:$600 Chromebooks are a dangerous development for Microsoft by paulcarroty on Saturday September 01, 2018 @02:32PM (#17893277)

Vanilla AOSP still use Google DNS by default and Google servers for an internet connection checker.

[ Parent | on HN ]

Re:$600 Chromebooks are a dangerous development for Microsoft by nextos on Saturday September 01, 2018 @03:29PM (#17893521)

I patch that, and a few other things. It's a poor man's CopperheadOS.

[ Parent | on HN ]

Re:$600 Chromebooks are a dangerous development for Microsoft by TheAceOfHearts on Saturday September 01, 2018 @06:14PM (#17894172)

Have you considered writing a guide on how you do this and what changes you make? I also own a Pixel, but kept running into problems when I tried to compile Android, eventually making me give up.

[ Parent | on HN ]

Re:$600 Chromebooks are a dangerous development for Microsoft by nextos on Saturday September 01, 2018 @08:08PM (#17894611)

There's great work around from many people. See e.g.: https://github.com/dan-v/rattlesnakeos-stack

That's a whole toolset to compile your AOSP in AWS and then build your own over-the-air updates.

[ Parent | on HN ]