See the entire conversation

AOSP 7.0 really only has support for a single device right now: the Pixel C. Building for anything else requires unofficial modifications.
25 replies and sub-replies as of Sep 16 2016

Google's vendor.img shell game doesn't work. They can't move apps needing platform key signatures there and not regenerating it is broken.
Not to mention the fact that their open-source components now depend on the unpublished build system used to make the proprietary blobs.
Getting tired of hearing that Android is open-source. Android Open Source Project isn't what ships on devices and can't be built unmodified.
Most devices are not even shipping an OS that Google has the sources for internally. Android == some proprietary OS that passes Android CTS.
AOSP is open source enough for vendors. It's not designed for the end users! I guess that's the price of "shipping it asap".
If vendors are really using AOSP, rather than partners receiving a different internal source tree from Google. Have some doubts.
I heared somewhere ;) that Sony switched to mailine linux kernel because it's cheaper. I guess they understood Open Source. :)
It's not possible to use a mainline Linux kernel for a device branded as Android. Sony definitely doesn't ship a mainline kernel.
Sony started towards being able to boot a serial console with the mainline kernel on their devices. Doesn't mean they use it now.
Anyway, that's not really the problem. A mainline kernel with a few patches could pass CTS but doesn't support mobile hardware.
Not yet but maybe soon. They tried to port it for all of their new devices. Only say that because I got a hint from someone.
Qualcomm would need to land their drivers upstream, otherwise they are going to need to add dozens of major drivers via patches.
If there are patches, it's not a mainline kernel.
Qualcomm wouldn't even let us have the symbol names for their drivers in public Firefox OS crash reports.
Yeah then choose exynos or mediathek based platforms. We have the same problem on x86 hardware @coreboot_org ;)
Last I tried "unmodified" bits were reasonable, but it's skeletal, and a pig: hours to build on fast machine.
It's no longer possible to do an incomplete build without setting up binary blobs (which they don't offer now).
Since device/huawei/angler/location and device/lge/bullhead/location depend on a having the blob build system.
Either way, you need blobs simply to boot but can get away with unmodified vendor.img by not having verified boot.
There are various ways that not regenerating vendor.img is broken, with verified boot being the main issue.
I was targeting in-house hardware, if you are targeting someone else's custom hardware, and it isn't open…yes.
Only talking about the hardware that it's supposed to support directly though: Nexus devices. Not so much anymore.
does that mean I want to have a Pixel C as my next device?