4 ms·
there is open source and open source thru google's gates. on the later you submit patches, they will be included in the next 2 to 3 versions of public release
by gcb0 8y ago
there is open source and open source thru google's gates.
on the later you submit patches, they will be included in the next 2 to 3 versions of public release (if they dont't add any feature that impacts google's ad bottom line, for example, adding any sort of referrer control to chrome), then you have to hope that in those 2-3 version cycle your device is still supported, now you just have to wait for the convenient over the ait update provided by your telco or phone manufacturer (in most cases you actually need both entities to take part)
- icebraining 8y agoThat's not Google's gates, that's the OEM's and the ISP's. Google can only control that for their own devices, and the Nexuses have always been some of the most modded ones.
- gcb0 8y agoGoogle own the merge rigths, and what goes into each version. and their process timings ensure that by the time you patch is out, your device is not getting updates anymore (update timeframe that they set both in contract with oem or via "example" via their nexus series)
- icebraining 8y agoWhat merge rights? You can build Android yourself and install it directly on your phone, and let others do the same - unless if the OEM's and ISP's gates prevent you.
- gcb0 8y agounless "your device" is the emulator, there is no way to get hold of drivers or firmware for anything other than lifting them of an blessed rom ... and only if you can get the parity you need with the kernel you are using. there's a very good reason the "supported device list" of all forks is always very, very small (even with the outlandish claims on most of them such as "supported. touch screen and modem still not working" ) just becuase the build steps for your fork project automates some of that driver/kernel lifting, doesn't make it any better.
- icebraining 8y agoAnd all of that is also gatekeeping by the OEMs.