Monday , 31 March 2014
Breaking News
HomeNewsBreaking NewsAOSP Maintainer Jean-Baptiste QUITS

AOSP Maintainer Jean-Baptiste QUITS

android_locked_bootloader AOSP

AOSP King Quits Development:

Android is the most popular mobile OS in the World. There are many reasons for this but most importantly it is due to it being free open sourced which allows programmers everywhere to contribute to this continuously evolving OS and try to make it even better than before.

But sadly, there are times when corporate companies and lawyers spoil the openness of Android by limiting the amount of code and binaries available to the general public using the excuse of proprietary licenses. Yesterday, a long time Android favorite and the technical lead and chief maintainer of the Android Open Source Project (AOSP), Jean Baptiste Queru (JBQ) announced that he will be leaving the project due his frustrations with it.

JBQ was revered in the Android community due to his passion for Android and his willingness to collaborate with and help independent developers get access to its code. He was known for his quick responses to questions posed by people on Google Groups and ensuring that Android remains open sourced. Which is why his decision to leave the project is such a shock and have made many people wonder why he was forced to take this extreme step and give up.

The smart folks over at Android Police decided to do a little investigating and put the pieces of this mystery together. The answer was a very sad one – the main culprits over here seems to be Qualcomm; a company notorious for its excessive ‘proprietary’ intellectual property safeguards. Many of the biggest smartphones and tablets nowadays run on the Qualcomm Snapdragon processor which has gained a commanding lead in the SoC industry thus giving the company leverage to blatantly enforce its trademarks.

Google released its new Nexus 7 tablet a few days back that runs on a Qualcomm Snapdragon processor and many people started to notice that no factory images or binaries for it were made available by the company. So, naturally, JBQ was asked why they weren’t available and when will they be made available on the Android building group where he responded by saying that there is no ETA known to him at the moment and that he doubted whether the images will ever be made available. It was his later comment pointing out how Google never released factory images for the Nexus 1 too that divert our attention towards Qualcomm, as the company was responsible for its SoC as well.

Here is a list of SoC’s used in the Nexus line.

Here is a list of SoC’s used in the Nexus line.

Nexus One: Qualcomm

Nexus S: Samsung

Galaxy Nexus: TI

XOOM: Tegra

Nexus 7: Tegra

Nexus 4: Qualcomm

Nexus 10: Samsung

Nexus Q: TI

Nexus 7 (2013):Qualcomm

In order to put all this rampant speculation to rest, JBQ sent out a tweet yesterday apparently confirming our suspicions.

jbq-gplus-aosp-645x340

Of course he cannot delve into more specifics due to the legal terms of his contract. But this is a very disappointing development and one which is sure to shake the confidence of many developers in the open nature of Android.

[Via: Android Authority]

Leave a Reply