Nexus die-hard fans love the products due to their good design, specs and not to mention the first priority given to the gadgets when it comes to software updates. Well, the Google owned Nexus 7 that was released a couple of weeks ago is facing difficulties with their partner company Qualcomm involved in the manufacturing of the chipset driving the powerful processor in releasing the proprietary binary code. The contents of the code aren’t public as yet and due to the close ties that Google has with the top processor manufacturer and orders not to release, Google is playing family holding on to what the Open Source community regards important to the progress being made to the Android Open Source Project. This makes Opens source partially closed quite literally.
It’s important to note that developers worldwide use these codes provided by all players in the Android market in coming up with improved versions of the same in order to improve the general experience of all users. Throughout the history of Android, starting with HTC Dream, all the way to the LG G2, the attribute of open source has created a safe-haven for Linux developers, app developers, programmers, and more. It’s important to keep the operating system as open-source as possible.
In light of this, came the report that the long-time Android Open Source Project maintainer and community participant Jean-Baptiste Quéru (JBQ) left his post on the 7th of August at the Android team to take on other endeavors within Google. It is believed that JBQ exit was anticipated after expressing his concerns six months in advance and after being frustrated in his efforts he’s finally ready to hang his boots and move on to greener pastures.
On 30th of June JBQ posted this on his Twitter page ;
“That feeling when lawyers sabotage the launch you spent 6 months working on? I haz it. Sad sad sad sad sad sad.”
Followed by this on the 4th of August on Twitter
“I don’t want to go to work tomorrow. I don’t want to be doing that job any more.”
Well seems JBQ’s patience came to a close when he finally posted this on Google+
Well, I see that people have figured out why I’m quitting AOSP.There’s no point being the maintainer of an Operating System that can’t boot to the home screen on its flagship device for lack of GPU support, especially when I’m getting the blame for something that I don’t have authority to fix myself and that I had anticipated and escalated more than 6 months ahead.”
A petition is on at Change.org in support of JBQ’s plight and at the time of writing this the votes were at 1152 in support of the release of the codes to the public. We hope to bring this to the attention of our android readers and request you to sign the petition and let’s give the developers of Android the power to make this experience better.