For most computer users, developers and all the work they do to write code for apps is invisible, so it should be no surprise that a new tool from Google designed for developers is flying under the radar. The tool is a new code repository call Cloud Source Repositories and is a move by Google to get into the source code repository hosting market where they will be competing against companies like GitHub, Atlassian, Microsoft and Amazon. Read more
With the first batch of Android One devices on the way, MediaTek has released the kernel source code for the devices for developers to take advantage of. The source is available on Google’s Android repository.
Other OEMs that use MediaTek processors typically aren’t compliant with releasing source code for their hardware, so it’s nice to see the company bypassing the company and releasing this on their own. Hopefully we’ll see other companies follow suit.
source: Google Source
Not long after releasing the device itself, Motorola has posted up source code for the kernel of the Moto X. They’ve released the files on SourceForge, and although it’s not enough source code to actually develop ROMs or anything similar, it’s enough to tinker with kernel specific details of the device. After Google’s acquisition, though, I can’t say I’m surprised to see Motorola complying with releasing code so quickly.
If you’re interested, you can check out the source at the link below. Otherwise, just sit tight and wait for some tweaked kernels to start showing up on XDA and the like.
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
Sure HTC may be dealing with unprecedented shipping delays for its One smartphone, but that hasn’t stopped it from releasing the coveted source code for the anticipated device, as well as the DROID DNA smartphone to the general public. This means that all of you fiddlers and hooligans that like to “tweak” the device will finally have one of the major tools necessary to make the phone just a wee bit better. DROID DNA owners will no doubt be happy about this news, but here’s hoping that all One fans will be patient for just a little longer because hey— the wait will certainly be worth it.
source: HTC (Twitter)
Many of you Verizon Galaxy S III owners are just recently enjoying that awesome Jelly Bean goodness, but there is additional good at hand. Samsung has quietly dropped the latest Jelly Bean source code (version LK3) for Verizon’s popular device– so this brings all of you developers and fiddlers one giant step closer to custom mod glory. Interested parties can find all the juicy deets once they hit the source link below.
source: Samsung Open Source
HTC’s DROID DNA has earned tons of praise from the Android community, but it’s certainly apparent that all the hardcore tinkerers out there have been itching to get down and dirty into the real guts of the device— and HTC has delivered by releasing the open source code and binaries to the masses. The code is based off Android 4.1 and is specifically meant for developers and should allow for some slight
‘modifications’ improvements to the device and subsequently, the various custom ROMs out there. This should especially be of major importance to those of you who went ahead and unlocked the DROID DNA’s bootloader as well.
Interested parties can grab the source code (version 1.15.605.4) at the source link below.
With the Samsung Galaxy Note 10.1 ready to roll out around the world, Samsung has released kernel source code for a couple versions of the tablet. Samsung has made available the code for model number SHW-M480K to be branded for Korea Telecom and for model number SHW-M480S to be branded for Southern Korean Telecom. Code for the WiFi-only version of the Galaxy Note 10.1 has not yet been released. The files can be downloaded from the Samsung Open Source Release Center using the source link below.
source: Samsung Open Source Release Center
Welcome to the party Verizon. Samsung released the source code for the Sprint, T-Mobile, AT&T over a week ago so it was only a matter of time before Verizon customers got their fix. The Samsung open source bank has been updated to include the latest kernel files for the SCH-I535, the Verizon Galaxy S III. Unfortunately you’ll still have a locked bootloader to content with however I’m sure this latest news will be welcomed by the developer community all the same. Modders, start your engines.
For those of you wanting to tinker with the ICS source files for the AT&T and T-Mobile Galaxy S III, I have some good news for you. Samsung just dropped the source for the SGH-I7474M and the SGH-T999V, and can be downloaded through the links below. It’s nice to see that Sammy is keeping their source codes up to date and is offering them before the devices actually launch. I wonder if this means the Verizon version of the source is just around the corner?
via: Android Police
source: AT&T GSIII Source / T-Mobile GSIII Source