ChromiumOS Enhanced Vanilla Build – R72-11316.B

New Vanilla Builds out today!

Download 64 bit build from https://chromium.arnoldthebat.co.uk/special//Camd64OS_R72-11316.B-Vanilla.7z

SHA256: 984270791378b6e023bca2cd65a60e7fbb9a7d4e18144f40f99aa366dcfb46ec

These builds are an enhancement to the normal Vanilla builds in the fact they support the Broadcom STA wireless stack as well as additional kernel resident wireless drivers. No additional graphics support is provided however.

Enhancements

  • R72 Chromium Release
  • Additional Realtek wireless support
  • Additional Atheros wireless support

Note: Google Play Store is still not working!
Known Issues: https://github.com/arnoldthebat/chromiumos/issues
Change Log: https://arnoldthebat.co.uk/wordpress/chromiumos-special-builds/chromiumos-special-builds-change-log/

The Update Server will be made available in the next week or so.




11 thoughts on “ChromiumOS Enhanced Vanilla Build – R72-11316.B”

  1. Hello, I really love your work. I was just wondering if you are gonna include wifi drivers for Qualcomm based wifi cards? I don’t have wifi in any of your builds.

      1. Thank you so much for getting back. That’ll be great to have wifi on my laptop. Cloudready has support for my laptop but in my experience they aren’t very stable.

  2. Thanks Arnold! Just loaded up the vanilla build on the chromebook pixel (2013) and it seems very stable so far. Thanks for adding the keyboard backlight driver! The ALT brightness keys still don’t work, but I can now control the backlight by changing the value in /sys/class/leds/chromeos::kbd_backlight/brightness. Everything else seems very smooth and fast. Only other thing I’ve noticed is that the files app won’t open Google drive, even after loading the API values in /etc/chrome_dev.conf. Not sure if anyone else is having that issue or found a fix. Thanks again for doing this! It is really appreciated!

      1. Thanks Arnold. I saw that article and the section on “passing keys at runtime” so I enabled the Google Drive API and got my own API key, client ID and secret. I added those to chrome_dev.conf but no luck. Are you passing your own keys at build time in args.gn? I wonder if those override any runtime keys? That would explain hitting the rate limit.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.