Update: The Verge has a response straight from the horse's mouth. It doesn't completely dismiss the idea of local content playback, but it doesn't exactly justify Google's disabling of the feature, either. Basically it's a "hurry up and wait" situation - we won't know exactly how Google intends to go forward until the developer preview for the SDK ends.
CyanogenMod 10 is still cooking, and heck, CM9 isn't even fully baked for all devices yet. That hasn't stopped Steve Kondik, aka the guy who puts the Cyanogen in CyanogenMod, from posting preview builds of CM10 over on XDA for the AT&T and T-Mobile Galaxy S III variants. Plus, a third preview build being posted for the Sprint version by another developer. Keep in mind, of course, that "preview build" translates into "absolutely nothing is guaranteed to work." It is exciting, nonetheless.
If you own a Sony SmartWatch, you may want to ignore the impending update to the SmartWatch app on the Play Store right now. Some users are reporting that, after updating the required app, their watches are experiencing random reboots, notifications no longer working, and random disconnects. We've reached out to Sony for comment, but so far we've heard nothing back.
It appears that version 1.2.33 of the software began causing problems.
The YouTube app just received an update to bring a few new features, including a +1 button, "watch later" queue, and the ability to upload while editing video info, along with one unexpected issue. The app description now says it's for Android 2.2-2.3.3, and, as a result, isn't showing up on devices running other versions, including Honeycomb tablets. Despite this, I was able to pull the update on my Incredible running CM7 (Android 2.3.7), although Artem couldn't even see YouTube in the Market on his stock rooted Epic 4G Touch (Android 2.3.4).
The Honeycomb SDK preview, allowing everyone to take a peek and play around with Honeycomb using the Android emulator, was launched yesterday, but after we got past the initial excitement, we found that the emulator itself was dog slow and pretty much unusable. In fact, it was so frustrating to use it that I wanted to punch walls and rip out my hair after 5 minutes with it. And I'm not even going to talk about orientation problems - how the Android team managed to ship the SDK with orientation broken by default (there is a fix for it in the Settings > Display) is beyond me and beyond the scope of this article.
Motorola's ruggedized DEFY (which our own Brad Ganley reviewed) is a pretty cool phone. In my book, any time you can stick a gadget in a glass of water (or beer, as the case may be) with absolutely zero negative repercussions, I'm interested. The DEFY is no poser - Motorola's made the first industrial-strength Android.
Unfortunately, a substantial number of users across the globe are reporting a fatal flaw with the device, and surprisingly it's not MOTOBLUR-related.
A few days ago, the code for the Nexus One's 2.2.1 update went AOSP (Android Open Source Project), meaning that the source code became available to developers. It was comprised mostly of bugfixes and other things that weren't major... oh, and it also patched the exploits that allowed Universal Androot to unlock your device. We had a short conversation about it on Twitter with Cyanogen (the conversation starts at the bottom and goes up):
As if breaking Universal Androot wasn't enough, apparently the new update also prevents existing installations of Swype and some other aftermarket keyboards from working.
According to HTC's official Twitter account, Twitter and the manufacturer have ironed out the bugs that were created when Twitter changed its authorization system a few days ago and broke both Peep and Friend Stream logins:
I have tested it on my EVO and can confirm that it is working properly. I'm not sure how such a major screwup could have fallen through the cracks at HTC, but let's hope it won't happen again.