The FreeXperia team of contributors help maintain CyanogenMod support for Xperia devices, and they've done such a great job that Sony has decided to hire one of the group's developers. Alin Jerpelea was one of FreeXperia's founders in 2010, and he is now the newest member of Sony's Developer Program. Having already built up a reputation for his work bringing the freshest CyanogenMod ROMs to Sony devices, he will now help the company with its open source initiatives.
You might remember the Oppo N1 as the first official CyanogenMod phone, which was quickly eclipsed by the OnePlus One. It was a very big phone (physically, not popularity-wise), but now the Chinese OEM is announcing a smaller version called, you guessed it, the N1 Mini. The thing is, the mini version of the N1 still has a 5-inch screen.
It's no secret that Bluetooth has been a problem child for Android, plagued with poor audio quality and connectivity issues. I've already covered a handful of common problems in a previous post, but another issue has been emerging in the last few months that threatens to virtually kill all Bluetooth operation on a device in the right conditions. The culprit is a nasty little oversight in the Bluetooth Low-Energy code added with Android 4.3 Jelly Bean.
Looking for the previous roundup editions? Find them here.
Expense IQ - Expense Manager
This week's roundup is brought to you by Expense IQ - Expense Manager from Handy Apps.
Since his departure from Cyanogen, Inc., Koush has been a pretty busy guy. Yesterday, he released AllCast Receiver to the Play Store, an app that essentially turns any Android device into a casting target, a la the now-extinct CheapCast. Today, he pushed an update to AllCast that brings a couple of new features, including Google Play Music streaming and the previously-teased headphone mode. Check out the latter in action:
This is essentially a jab at Roku's remote, which includes a built-in headphone jack for private listening while watching content on the TV.
Koush has certainly been busy since his departure from Cyanogen Inc. After getting AllCast working on the Fire TV with a receiver app, the AllCast Receiver is now in Google Play for use on any Android device. This essentially makes your device a streaming target in AllCast, letting you send media from one device to another.
In the past, Blu has offered budget-friendly phones with mid to mid-high end specs. The biggest issue that most power users have had with the company's handsets is a simple one: MediaTek processors. While these particular chips offer good bang for the buck, they are still mostly underpowered for heavy multi-taskers or anyone looking for lightning quickness from their handset.
It looks like we may be getting into a new era for Blu if the new Life Pure XL is any indicator of what to expect moving forward.
Sometimes when the internet really, really wants to believe something, no amount of evidence to the contrary will convince people. Such was the case with the OnePlus One and its phantom microSD card slot. The company said there is no SD card slot and the review units have no microSD card slot, so what's with the growing number of stories about a secret microSD card slot? Well, there was a mix up with the manual.
There should be no doubt, Google is getting ready to make a lot of announcements at I/O. If we've learned anything from past experiences, Google starts packing its apps full of surprises in the weeks leading up to the big show. The latest update to Play Services started rolling out yesterday and it has grown by a whopping 4 MB, almost 30% larger than the previous version. There's obviously a lot of stuff to look at, so let's just jump right in.
Remember the HTC EVO LTE? Sprint does, at least to some degree. The carrier is sending out a small software patch for the phone, reportedly removing a vulnerability from the infamous Heartbleed SSL security bug. Unpatched versions of Android 4.1.1 (and only 4.1.1) are vulnerable to Heartbleed, so EVO LTE owners probably want to get on that right away.
Heartbleed's relationship to Android is a little strange: it affects Android 4.1.1, but not earlier versions of Jelly Bean 4.1, and not later versions of any release, either, so the number of active phones and tablets at risk is comparatively small.