bloatware

See the following -

Google’s Iron Grip On Android: Controlling Open Source By Any Means Necessary

Ron Amadeo | Ars Technica | October 20, 2013

Six years ago, in November 2007, the Android Open Source Project (AOSP) was announced. The original iPhone came out just a few months earlier, capturing people's imaginations and ushering in the modern smartphone era. While Google was an app partner for the original iPhone, it could see what a future of unchecked iPhone competition would be like... Read More »

Who Controls Your Smartphone? And How to Leverage Open Source to Prevent it from Spying on You

There are many things about today’s world that warrant us asking that question. Do you or the mobile vendor control your smartphones? If you are a consumer, small or medium business (SMB) -- the answer is the vendor...What if you are a large enterprise or a government agency? The answer is still the vendor...How can the user regain control? Not all vendors have locked devices and walled gardens. Google’s line of Pixel hardware, for example, is a mid-market solution whose bootloader allows locking and re-locking. Pixels support two versions of Android. Google Mobile Services (GMS), where free services are tied to data monetization and a UX like Apple and Samsung devices. Secondly, Pixels can run Android Open-Source Project (AOSP) code that shares the same strengths as the GMS build, but the customer controls the code base and updates. There are several companies that are selling AOSP operating system builds for Pixel and other unlockable/lockable mobile phones and tablets...

Read More »