Google’s Patch Reward Program adds numerous open source software projects

by Jeff Causey on
tagged , , , ,

google_flat_logo

Approximately six weeks ago, Google launched a new program it was calling the Patch Reward Program. The program encourages coders to take a proactive approach to improve “third-party” software that Google believes is key to the health of the Internet. According to Google:

“The goal is very simple: to recognize and reward proactive security improvements to third-party open-source projects that are vital to the health of the entire Internet.” » Read the rest

Jean-Baptiste Queru surfaces at Yahoo!

by Jeff Causey on
tagged , , ,

jbq_new_job_tweet

Jean-Baptiste Queru, aka JBQ, who was the lead for Google’s Android Open Source Project, announced via a tweet that he is now working at Yahoo! with the team developing their mobile apps. You may recall last month, after the release of the Nexus 7 2013, that JBQ became extremely frustrated with the inability to get factory images thanks to hesitancy on the part of Qualcomm in releasing their binaries. That frustration led to JBQ walking away from Google and the AOSP. That in turn appears to have triggered Google and Qualcomm to resolve the issues and post the factory images, though apparently too late to retain one of their leads.

JBQ indicates he started in his new position as an architect and senior principal engineer this week.

source: @jbqueru
via: AllThingsD

Android 4.3 for Nexus 10 still isn’t supported in AOSP due to GPU driver issues

by Jared Peters on
tagged , , ,

Nexus_10_TA_Front

Remember those issues with the Nexus 7 factory images that couldn’t be released because of proprietary graphic drivers? Unfortunately, the Nexus 10 seems to be running into a few of the same problems. The GPU binaries are unable to be released to AOSP which prevents developers from building Android 4.3 from source for the Nexus 10. Factory images are still available, but the source-builds are going to be held up by those GPU drivers and binaries.

Jean-Baptiste Queru confirmed the issues on a Google product forum and stated that only Android 4.2.2 could be built for the Nexus 10 until these drivers were released. Until then, a factory image is your best option if you want to tinker around with what Google has available for their flagship 10 inch tablet.

source: Google Developers

Google Forums

via: Android Police

Nexus 7 tablet experiencing difficulties in getting factory images available for the masses, causing Jean Baptiste-Queru to give up and leave AOSP all together

by Roy Alugbue on
tagged , , , ,

Nexus_7_ASUS

 

As excited as we are about the ushering of the new Nexus 7 tablet, there have been some quiet— but major technical snafus for the Android hardcore which has resulted in one of the most important pieces of the AOSP disappearing from the project all together. Tech stud Jean Baptiste-Queru officially confirmed the various rumors regarding his AOSP position and thus, confirmed that he was leaving everything all together because of his frustration with the difficulty of getting factory images for the newest Google tablet. Check out the following for his reasoning:

 

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.

 

The reasoning is certainly legit, but what’s really eye-opening is the part where he talks about a Google flagship device not being able to boot to the home screen because of the lack of GPU support. Android purists will recall that the Nexus 4— which also features a Qualcomm Snapdragon chip— originally didn’t have the factory image and source code released in full. Naturally the issues were addressed, but owners of the device weren’t able to enjoy the true Nexus experience since the source code/factory images couldn’t be modified. Now we’re going through the same exact issue as the Snapdragon-powered Nexus 7 doesn’t have the factory images available to the masses. Is it a coincidence that both devices that two Snapdragon-based Nexus devices have had factory image issues? Probably— but one thing’s definitely for sure: it’s certainly going to suck not having Jean Baptiste Queru for our AOSP needs. Hopefully the Android team will find some sort of fix or remedy for future Nexus devices.

source: Android and me

Sony Xperia Tablet Z receives AOSP support

by Aditya Thawardas on
tagged , ,

Sony opened AOSP software code for the  Sony Xperia Z last month, and now the Xperia Tablet Z has been added to the program as well. This will be the first tablet to receive the AOSP port from Sony. The source code will be available through GitHub, usable after the bootloader on the tablet is unlocked. Keep in mind, this software is not intended for everyday use and several apps and services will not be functional.

You can see a Jelly Bean walkthrough of AOSP on the Tablet Z in action below.

YouTube Preview Image

Source: Sony Blog

Sony Xperia Z released to AOSP

by Jeff Causey on
tagged , , ,

sony_xperia_z_aosp_banner

Sony announced today that they have opened the software code for their Sony Xperia Z smartphone to the Android Open Source Project. The software has been uploaded to Sony’s GitHub. Between that and information available at Sony’s Developer World site, external developers should have everything they need to get started. The project will be overseen by the same people who were over the Sony Xperia S AOSP. Sony points out that the software is not intended for everyday use and several apps and services one might expect on a standard smartphone are not present. Hit the break for a short video about the project and some shots of what is included in the code. » Read the rest

Roll Your Own Android: Android 4.2.2 Code and Binaries pushing to Android Open Source Project (AOSP)

by Jason Bracey on
tagged , , ,

android-4.2-jelly-bean

Great news for Nexus users, AOSP is pushing Android Jelly Bean 4.2.2 binaries for several devices in the Nexus product lineup.  The build, JDQ39 (tag: android-4.2.2_r1), is the same as the one currently being rolled out to Nexus devices.

As listed on the Google Developers site, binaries are available for the following devices:

» Read the rest

Google Publishes New Android 4.2.1 Open Source Code To AOSP

by Roy Alugbue on
tagged , , ,

 

It appears that another Jelly Bean build is now on the way folks. Now before you all go thinking this would bring the version at 4.3 or even a 4.2.2— you may want to think again. Google published its Android-4.2.1_r1.1 and Android-4.2.1_r1.2 open source codes  which correspond with the JOP40G and JOP40F Android builds. For now, it appears that the new open source codes bring some very minor bug fixes— but there may be a surprise or two trickled in there somewhere.

You’ll find additional details once you hit the source links.

source: AOSP 1 | AOSP 2

Itching To Grab A Nexus 4, But Tired Of Playing The Waiting Game? Try Using A Special Hack To Convert The Optimus G To A Nexus 4 Instead

by Roy Alugbue on
tagged , , , , , ,

 

Ah yes, the Nexus 4 smartphone. It’s no secret that waiting for that elusive device has been nothing short of frustrating and with LG’s rumored decision to take a break from the Nexus 4 production— it appears that Android fans will either need to wait for Google to have more inventory available or try to find some other sort of ummm… “alternatives” to suffice. With that in mind— the wizkid team of G33k3r, Rohan32, et. al came up with one hell of a Nexus 4 alternative for those who just can’t wait— and all you need is an LG Optimus G smartphone to start off with. As you know, the the Nexus 4 loosely based off the Optimus G smartphone (save for some minor differences like a pesky custom UI and all). With that in mind, the savvy folks basically figured out a way to overwrite the AT&T-based Optimus G firmware to that of a stock Nexus 4. What this does is literally changes everything from the bootloader to the actual AOSP software— effectively giving you an unofficial Nexus 4. Of course this special mod means that Optimus G users are willing to attempt this special modification will lose a lot which includes the coveted LTE capabilities and 8GB of the available 16GB storage space as the mod will cap the partition at a mere 8GB only.

Still, those are only minor things to nitpick really. This special modification will certainly be appealing to more than a few of you out there. If you’re up for trying this out or want more deets, hit the source link for more information.

source: XDA Forums

After stops on Nexus 4, Nexus 7, and Nexus 10 devices, Android 4.2.1 lands in AOSP

by Jeff Causey on
tagged , , , , , ,

Android 4.2.1 Update

Over the course of the past day, we have seen Google start to rollout an Android update, first to Nexus 10 devices, then to Nexus 4 devices, and most recently to Nexus 7 devices. The OTA update to version 4.2.1 is probably still in the process of propagating to all device owners. In the meantime, the source code has landed in the Android Open Source Project according to Technical Lead Jean-Baptiste M. Queru. Factory images for devices are expected to be available in a few days according to Queru.

The update is small, but packs an important fix in correcting the missing month of December. According to sources, the update also includes support for HID gamepad/joystick devices and some improvements to handling of vibration notifications.

source: Android Building Google Group

1234