Adam Outler · Jun 18, 2012 at 11:00 pm

Nvidia and the Problems with Closed Hardware

Here at XDA-Developers we hold very few ideas close to our hearts: Openness, new concepts, and development. These all revolve around one core principal: Technological advancement of society. Those who do not practice these concepts are generally given warnings and eventually banned from XDA.

What do we do when a manufacturer violates our values? We don’t support that manufacturer. Linus Torvalds sums it up nicely in this video from Aalto Talk with Linus Torvalds, hosted by Aalto Center for Entrepreneurship (ACE) in Otaniemi on June 14, 2012.

I’ve been saying it for a long time.  Nvidia and Qualcomm are the problem children of Android. Yet HTC, for some reason embraces their closed and problem-causing ways.  There is quite simply no reason whatsoever for an Open Platform like Android to be reduced to running on Closed Hardware like Tegra or Snapdragon.

Closed hardware makes it difficult for developers to isolate and troubleshoot problems.  You can take a look into the past, almost one year ago, when Android 4.0 Ice Cream Sandwich was released.  The first fully supported processor was the Samsung Exynos, followed up quickly by the Texas Instruments OMAP, and shortly thereafter, the Samsung Hummingbird.  It was quite literally months of development work, which involved getting data through official and not-so-official channels to get ICS on these closed-hardware NVIDIA and Qualcomm processors.

So, I will now end this bit of ranting by backing up Linus (father of Linux and Grandfather of Android) Torvalds by saying: “NVIDIA, F*** you,” and follow up with a “Qualcomm, F*** you too.”

 


_________
Want something on the XDA Portal? Send us a tip!
TAGS:
Emil Kako · Jan 31, 2015 at 02:59 pm · 2 comments

Do You Prefer Physical or on Screen Buttons?

More and more smartphone manufacturers have been moving towards on-screen buttons, with Google really pushing for it over the physical button alternative. However, there are still a few OEMs (we're looking at you, Samsung) that have preferred to keep things a bit more traditional. Tell us which way you prefer and why.

DISCUSS
Pulser_G2 · Jan 31, 2015 at 02:08 pm · 1 comment

New AOSP Branch Details Potential Build System Upgrades?

While there are frequent unexplained changes and pushes to Google's AOSP repositories, an interesting-looking new branch has been pushed out recently, called "master-soong". Taking a look at the changes made to the manifest repository (which is used to specify the repositories to be downloaded when building Android), it appears there are some new repositories making an appearance. Of note here are new prebuilt repositories for Go, and Ninja. Go is a programming language, created by Google, which compiles to produce...

XDA NEWS
GermainZ · Jan 30, 2015 at 09:29 pm · 1 comment

Send Links to Any Nearby Device with CaastMe

There already are many solutions on the Google Play store if you want to send a link to one of your devices -- but what if you wanted to do it quickly without having to install any software or logging in to a website on the recipient end? Most apps require you to do either or both, which can be a hassle (or even a security risk) in some cases. Luckily, XDA Forum Member wyemun has developed CaastMe. Inspired by...

XDA NEWS