Posts tagged source
The Google Glass kernel source is apparently available to download for developers to start playing with it.
Karthik’s Geek Center reports that it has found the Google Glass kernel source “in a temporary location on Google Code” from where it should be moved to a more permanent location in the future. In case you’re interested in getting your hands on it, head on to the Source links below to get yours – you’re looking at a 68.9MB tar.xz file.
What’s interesting about the Google Glass kernel is that it has some NFC references in it, as the same source points out:
On digging into the Kernel, looks like it has got all the headers required for NFC support. May be Glass is NFC enabled? Or may be, since its running Android source, it has the NFC drivers by default?
However, there’s nothing to suggest that Google Glass will have any NFC-related features. In fact, NFC is not mentioned in the specs sheet of the product – and by now we also learned more details about the processor type, RAM and Android version Google Glass runs.
Getting back to developing for Glass, you should also know that Google Glass has already been rooted, with the process described as “easy” by at least one developer.
Meanwhile, Google said via Eric Schmidt that it will exercise some caution initially by pre-approving apps for Glass, with the process opening up in the future. The same Schmidt also revealed in a recent interview that the commercial launch of the Glass will only take place in about a year or so.
In case you happen to have a great Google Glass app in the works, drop us a shout!
Two years after Google announced it would acquire Motorola, questions about the value of the deal still linger. A source told The Verge that the misstep might have contributed to the ousting of Andy Rubin from the Android team.
In a piece analyzing the strategic and tactical advantages that Google obtained, but mostly failed to obtain, by acquiring Motorola Mobility, The Verge’s Nilay Patel revealed some potential clues about the true reasons behind Andy Rubin’s leaving from the Android team.
As a backgrounder, Google announced that Andy Rubin would no longer lead the Android team in early March. In a blog post, CEO Larry Page said that Rubin “decided it’s time to hand over the reins and start a new chapter at Google”, making it sound like the founder of Android was leaving voluntary. But rumors quickly emerged painting a less rosy picture of Rubin’s leaving.
Now a supposedly well connected source confirmed to the The Verge that Andy Rubin was ousted from the Android team, following missteps including the Motorola acquisition:
Andy stood behind the deal and thought it was important to Google. As [new Motorola CEO] Dennis Woodside started to look into the details, he couldn’t see what Andy supposedly saw, which added more fuel to the fire to oust him.
This information suggests that, Google was already dissatisfied with Rubin at the time when the Motorola purchase was announced, and, when the positive outcomes of the merger failed to materialize, Rubin shouldered the blame.
At this point, it is unclear what role has Andy Rubin adopted inside Google. We’ve heard rumors about a new moonshot program due to be introduced soon, but it’s all speculation at this point. What we do know is that Android wouldn’t exist today without Andy Rubin, so regardless of what he’s currently doing at Google, we hope he’ll stay with the company.
After finding himself too busy with personal matters and development for another app, Chris Lacy has admitted that he can no longer play an active role in improving Tweet Lanes, a Twitter app for Android. That said, he has turned Tweet Lanes into an open source project, passing on the future of the app to the Android community.
Yes, we know there are quite a lot of other apps in the Play Store to manage your Twitter apps. New ones keep appearing and some existing ones have dedicated developers who are still consistently pushing updates and features. But what really sets Tweet Lanes apart from the Twitter app flock is its Holo-themed user interface, intuitive navigating through swiping, multiple account support, and flexible customizations. Leaving the app to die just because its creator can no longer commit is just plain wrong. But by relegating the development work to the community, Tweet Lanes might just receive the time and attention it deserves.
Besides announcing the switch to open source in Google+, Lacy revealed that the only thing he can do for Tweet Lanes is “syncing with the master branch and releasing a signed version of the app to the Play Store a few times a week.” He then continued to list the tasks he can’t commit to such as implementing new features, addressing flaws, feedback response, and more. He hopes that the community, which he suggests should be led by a volunteer dev lead and community manager, can perform those responsibilities to keep the project afloat.
Lacy is still currently looking for volunteers. But if no one steps up, the latest Tweet Lanes update will probably be the last.
Would you like a side of kernel source with your Sony Xperia Z? If the answer is yes, you’ll be thrilled to hear that Sony has released the kernel source code for its latest flagship phone — despite the fact that the Xperia Z won’t be hitting stores internationally for another few weeks or so.
This is just one of the many good gestures that Sony has been showing to the developer community. Last month, the Japanese phone maker shared the alpha build of Jelly Bean for the Xperia T prior to the official rollout of the Android 4.1 firmware.
What exactly separates Sony from the likes of Samsung? As pointed out by XDA-developers, Sony actually releases a “complete, compilable, and working kernel source.” There you go.
If you’re up for some compiling fun, you can head to Sony Developer’s website to grab the Xperia Z kernel source. Of course, you won’t be able to test it out on the handset right away, unless you live in Japan.
Does this make you ache for the Xperia Z more? Feel like giving Sony a virtual pat on the back? Hit the comments below.