Samsung has really been talking up the Note II lately. For good reason, too - it looks pretty amazing. While they have already showed off some of its more notable features, a new video of the Korean version is now available on YouTube highlighting a few features that we haven't seen before, like multi-window. Start around the two-minute mark below to catch it in action.
We've all heard the old saying "better late with a newer version of Android than never," right? That's how I've always heard it said, and apparently I'm not alone. Telstra just announced its own variant of the Samsung Galaxy S III, which will be available beginning October 9th.
The Aussie 4G version of the device is basically identical to the international edition:
4.8" SAMOLED display
1.4GHz quad-core Exynos processor
8MP Rear shooter
16GB storage, microSD Card slot
4G LTE, HSPA+ Dual Channel 3G
Android 4.1 with Touchwiz
The good news here is that the superphone will ship with Jelly Bean out of the box, so users won't have to wait for an OTA update to become available to get the latest version of the OS.
If you've been waiting to get your hands on a 4G GSIII in Australia, the wait is over in ten days.
You may recall the collective scream of horror emitted by the Android community when it was confirmed over the summer that the Verizon model of the Galaxy S III would ship with a locked bootloader. As a consolation, Samsung decided to sell an unlocked "Developer Edition" for full price online. While the regular device has since been cracked, it's a lot cleaner to buy the dev version and now it's on sale.
It seems like everyone's getting a Galaxy S III lately, and C Spire Wireless (formerly Cellular South) didn't want to be left out. If you're unfamiliar with the company, they're a regional provider in the Southeastern US, with a Verizon-sourced regional MVNO (mobile virtual network operator) national network. C Spire operates its own network on its home turf, and that includes a growing LTE footprint. That LTE, for now, is quite limited, basically to a few parts of the Southeast US.
Wow, AT&T. Instead of sending multiple device announcements on different days, the company just announced a few new smartphones and a tablet for its 4G LTE network, all of which are made by Samsung. Let's take a look, shall we?
Samsung Galaxy Express
The Galaxy Express seems to be sort of a tweener device. Not in terms of "your child between the ages of 10 and 12 will love it!" but in that it appears to be right in the middle of the Galaxy S III and some mid-range devices.
We already know the Galaxy Note II is headed to all of America's "big four" carriers with Exynos and LTE (well, LTE on 3 out of 4) in tow. What we don't know is when. Samsung promised "before the holidays," but that's a pretty large window. It seems likely that window is about to close - next month.
Samsung has announced an event to be held on October 24th in NYC, and the invitation makes it quite obvious what the topic of discussion will be.
If downloading source code and picking through lines of code is something you enjoy doing, then today is a day of gifts: Samsung just released not one, but two different kernel source codes. I can almost feel your excitement.
First up, the GSIII. The international variant (i9300) was recently updated to Jelly Bean, and Samsung just made available the respective kernel source. So, if you've been waiting on that, it's ready for you.
The newest sets of binaries for Nexus devices have been published and are now available to download on Google's Nexus drivers page. This new batch of binaries is for Android 4.1.1 build JRO03R, and covers basically all Nexus phones and tablets:
There has been a lot of misinformation floating around this morning about an alleged "exploit" on Samsung phones that allows the entire device to be wiped from the browser using what's called a USSD code.
Update 2: This exploit probably won't work on most Galaxy S III's as long as they have the most recent OTA update, as we demonstrate on video here.
Update: This issue is, unsurprisingly, a lot more nuanced than the video here lets on. The bug is based in the stock Android browser, is in fact quite old, and has been patched in more recent builds of Android - this is probably why Nexus devices running the most recent OTAs are unaffected.