Since the debut of Android 4.1 Jelly Bean back at I/O, everyone has been clamoring for CyanogenMod 10. With the addition of each new device to the list of those with official nightly support, hopeful users of flagship handsets like the HTC One X and Samsung Galaxy SIII wondered when their day would come. While most variants of the SIII have already received nightlies, the US Cellular variant (d2usc) joined that list last night, along with a few other devices. Included among the new inductees are AT&T's HTC One X (Evita), the HTC One S (Ville), and Sprint's Evo 4G LTE (Jewel).
After dropping source code for the Wi-Fi Galaxy Tab 7.0 Plus (along with the Galaxy Note 10.1 and Tab 10.1) just last week, Samsung is once again providing eager developers with something to play with over the weekend, releasing kernel source code for T-Mobile's variants of both the Galaxy Note and the Galaxy Tab 7.0 to their Opensource download center.
Both packages carry source code for their respective devices' Ice Cream Sandwich-powered kernels.
Those looking to grab a handful of fresh source code and begin tinkering with the T-Mobile connected Galaxy Note and Galaxy Tab 7.0 Plus need only click through the appropriate link below to grab the download.
Despite Verizon's best efforts to keep their own variant of the Galaxy SIII locked down, ingenious users haven't been deterred in rooting, flashing custom ROMs, and even bypassing the device's locked bootloader to use custom kernels. The fact remained, however, that VZW's SIII had a locked bootloader which, in general, is a hassle for developers and tweakers hoping to customize the SIII to its fullest potential. It was this fact that made Samsung's promised Developer Edition SIII appealing to many.
Things started to look a little brighter for SIII users on Verizon today though, with the introduction of an unsecure bootloader "leaked by an African-Canadian Sock Monkey," revealed earlier this evening at XDA.
I remember the first time I really heard about Flash for Android. Well, maybe not heard about it. The first time I got sort of excited about it. It was in San Francisco, at a trendy Spanish-restaurant-meets-brewery back in the summer of 2010. The taps were pouring freely (and by that, I mean free of charge), tasty little hors d'oeuvres came at us from from all directions, and everyone was having a good, if typically nerdy-awkward, time. The free booze definitely helped. It was also, coincidentally, the first time I met the man in charge of Android Police, Artem, and one of our long-standing editors, Aaron Gingrich.
I've written more than a few of these giveaways for products covering just about every aspect of Android development, and written by dozens of authors. But this one... well, this is special, because it's a series of LiveLessons from none other than former Android Police contributor Ian Clifton.
- Michael Pardon
- Tania N
- Alex (Dupree?)
- Mario II Valenzuela
- Jeff Miller
- Keyz Karanza
- CHRIS S
Congratulations, guys - all of you will be contacted for your information in the near future!
Everyone else - keep participating and stay tuned to Android Police so that you don't miss our upcoming giveaway announcements.
It seems the announcement of "root for Samsung device x" always manages to occur well before most consumers actually have their hands on it. Today marks yet another such occasion, with the Galaxy Note 10.1 having already been cracked by Zedomax over at the surprisingly aptly-named RootGalaxyNote.com.
It's so easy that I'm just going to give you the gist, head to the source for the full instructions. Basically, you need a Galaxy Note 10.1, Odin, Samsung USB drivers, and a firmware file. All of this is available there. The one catch is that the root method used here is "pre-injected" firmware, meaning you'll have to flash either a Saudi Arabian / UAE or European firmware to your Note 10.1.
Back in late June, Google teased a new, cleaner developer console. A couple weeks after that, the beta signup went live, allowing devs to get in line for an early look at the next-gen console. Now, for those who signed up for said beta, the updated console is beginning to show up.
The first impression that we're hearing from developers who've used the new console is that it feels faster, has a much better UI, and is far easier to use. Sounds good to us.
If you signed up for the beta, go ahead and check it out - it should be available for you now.
As Android Police's unofficial person who knows things about laws (as always, none of this is legal advice), sometimes I see law stuff going on in the tech world that just makes me mad. This is one of those times. Appigo, an iOS and OS X developer, filed for a trademark on the word "Todo" (see it here) under the scope of a software application (basically).
Yesterday, we received an email from a developer of an app for Android called Star Trek ToDo Agenda. He was contacted by Appigo, with the following email (private information redacted):
I'd like to discuss a small issue with one of your apps:
Your App Name: Star Trek ToDo Agenda
Your App URL: https://play.google.com/store/apps/details?id=com.stanlm.startrektodoagenda&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5zdGFubG0uc3RhcnRyZWt0b2RvYWdlbmRhIl0.
In a post to Google's Android Building group today, Jean-Baptiste Queru once again acted as the bearer of good tidings for developers and tweakers everywhere, announcing that "a new set of proprietary binaries for Jelly Bean are available."
The new batch of binaries includes those of the Nexus S and Nexus S 4G (Crespo and Crespo4G respectively), the latter of which we just recently saw added into the AOSP fold.
The set also includes updates to the both the GSM Galaxy Nexus (maguro), and Verizon's Galaxy Nexus (toro, which itself is ever so close to full AOSP support).
Conspicuously absent from the party is Sprint's variant of the Galaxy Nexus, but there's no surprise there.
The day that many ROM enthusiasts have been dreading has arrived: the CyanogenMod Team has announced the end of life support for the original Nexus One, along with other first-generation Snapdragon devices, including the HTC EVO 4G, [Droid] Incredible and Desire and others. None of these devices have official builds of CyanogenMod 9 (though plenty of independent ROM developers have done their best) and they won't be getting any CM updates beyond the 7.X Gingerbread branch.
The reason is a limitation in the media libraries of most of these devices, as well as a general lack of on-board storage in the second generation of Android hardware.