As excited as we are about the ushering of the new Nexus 7 tablet, there have been some quiet— but major technical snafus for the Android hardcore which has resulted in one of the most important pieces of the AOSP disappearing from the project all together. Tech stud Jean Baptiste-Queru officially confirmed the various rumors regarding his AOSP position and thus, confirmed that he was leaving everything all together because of his frustration with the difficulty of getting factory images for the newest Google tablet. Check out the following for his reasoning:
Well, I see that people have figured out why I’m quitting AOSP.
There’s no point being the maintainer of an Operating System that can’t boot to the home screen on its flagship device for lack of GPU support, especially when I’m getting the blame for something that I don’t have authority to fix myself and that I had anticipated and escalated more than 6 months ahead.
The reasoning is certainly legit, but what’s really eye-opening is the part where he talks about a Google flagship device not being able to boot to the home screen because of the lack of GPU support. Android purists will recall that the Nexus 4— which also features a Qualcomm Snapdragon chip— originally didn’t have the factory image and source code released in full. Naturally the issues were addressed, but owners of the device weren’t able to enjoy the true Nexus experience since the source code/factory images couldn’t be modified. Now we’re going through the same exact issue as the Snapdragon-powered Nexus 7 doesn’t have the factory images available to the masses. Is it a coincidence that both devices that two Snapdragon-based Nexus devices have had factory image issues? Probably— but one thing’s definitely for sure: it’s certainly going to suck not having Jean Baptiste Queru for our AOSP needs. Hopefully the Android team will find some sort of fix or remedy for future Nexus devices.
source: Android and me
In announcing a new camera app for CyanogenMod users, the team also revealed some more information about their Nemesis project announced earlier this week. According to CyanogenMod, the Nemesis initiative is an effort to improve the user experience for Android ROMs built on the Android Open Source Project code, like CyanogenMod. The first example of where the experience falls short is in the camera app, which the CyanogenMod team thinks is lacking when compared to versions released by HTC, Samsung and LG. To correct that, CyanogenMod is releasing Focal, a completely new camera app.
Just last week we reported that MoDaCo.SWITCH had opened their ROM for those who signed up to receive the beta, but now it looks as though the beta has gone public.
The MoDaCo.SWITCH ROM allows HTC One users to effortlessly switch between stock Android and HTC Sense with the touch of a button. The best part is that the ROM uses a single set of user data so all of your apps/information/etc. are available on both UI’s.
Now that “beta 8″ is available to the public (only on the GSM HTC One) you can go and grab it below if you’re familiar with the flashing process.
MoDaCo is also working on a project to bring their ROM to the Galaxy S 4 using an Indiegogo project to raise $1500.
Download, installation, and set up instructions below.
It looks like the folks at CyanogenMod are up to something. Well, they are always up to something, but they are in the teasing mood right now. They released a very short teaser video for something they are working on. What is it? We have no idea so let the speculation begin. It’s start out by saying, “Nothing can be perfect, Things can be better.” Ain’t that the truth. There is a few more tidbits that you can check out for yourself, and then it closes with “A new challenger appears,” and “A new Nemesis appears.” I have a funny feeling they have a few more teases lined up. Any ideas as to what they might be up to? Hit the break for the video.
Last week we showed you developer Paul O’Brien’s MoDaCo.SWITCH ROM which allows HTC One users to quickly switch between HTC Sense 5 UI and stock Android (as seen on the Google Play Edition of the HTC One). All you have to do is tap on one of two options— it’s that easy.
Now it looks as though they’ve opened up a signup page allowing users to try out the beta version of their app. Hit the link below to join in on all the fun.
Android 4.3 is likely to be officially available next week for the Nexus 4, but if you just can’t wait a few extra days, a leaked version is available. The build is JWR66N and was installed on a phone bought on Craigslist from a Googler. The build is in TWRP backup format so you will need the custom recovery installed. Currently the radio and bootloader are missing, but will be added soon. We also don’t know how final this firmware is so there could be other bugs. I will simply wait, but for those of you that just can’t, hit the source link.
additional download link
Once again, the CyanogenMod team seems to be on top of things, as they just released version 10.1.1 of their famed firmware. A post on their blog today issued a follow-up to the general release. They pointed out that the CM 10.1.1 build is simply a security bug-fix release on top of their previous release, the 10.1.0.x code-base. Check out the full blog post after the break for more details.
We’ve known about the Google Play Edition Galaxy S 4 for a while now, but had pretty much assumed at this point that it would launch with Android 4.2.2… up until now. SamMobile has received the firmware for Android 4.3 to the Google Play Edition Galaxy S 4 and has since placed the file on their site— and it’s completely stock. Android 4.3 has only a few minor improvements over Android 4.2.2, but keep in mind, all of this is coming before Google even announces the new version of their mobile OS.
We (and SamMobile) advise you not to install this firmware to your standard Galaxy S4 (GT-I9505/GT-I9500) as you might brick your device. If and when we receive firmware for other versions of the device (and other devices), we will let you know. For now, this firmware is ONLY for developers.
So for all you developers out there, the information (and files) from SamMobile you’ll need to get the firmware is after the break.
While it is rare for Android users to envy anything related to iOS, CyanogenMod developer Koush openly expressed his love for iMessage in a Google+ post, also revealing that he plans to build a plugin somewhat similar into future builds of CyanogenMod. The plugin will be built into the framework, working with any SMS app to send encrypted messages to compatible devices running CyanogenMod (7 million users and counting) and falling back to standard SMS when necessary.
Not much else is known about this feature but its another step in the right direction for the CM team, who’ve been hard at working making their ROM more and more secure. For now we can only ponder possible features of this plugin, but Koush is looking for feedback so hit the source to let him know what you want to see.
Source: CyanogenMod Google+
CyanogenMod 10.1 is now officially in stable build status after its initial release announcement last fall. Up to this point, the CM team has released updated builds every month or so, and more recently, RC builds. Now we finally have CyanogenMod 10.1, Android 4.2.2, and stable builds have been hitting their build servers. Now that this is all finalized, go ahead and grab a stable build for your device. Check get.cm to see if your phone is supported.