Though there's a definite streak among power users to prefer Google's "pure" Android on their phones, some of the manufacturer skins from HTC and Samsung have charming features as well. Modder and ROM developer Paul O'Brien, better known as MoDaCo, has been testing a solution to give you the best of both worlds. MoDaCo.SWITCH is a dual-boot solution for power users that lets two ROMs (manufacturer stock and AOSP, for example) which share user data, allowing a seamless switch between interfaces.
It's been less than 24 hours since Google announced Jelly Bean 4.3 and published the new code to the Android Open Source Project, and Sony is already talking up their plans for phone updates. That's what I call customer service! In a short blog post, Sony confirmed a 4.3 update for six of their latest phones and (one) tablets:
This isn't necessarily an exhaustive list, and no timeframe has been announced.
The day is here, AOSP fans: you can go pick up a gloriously stock Samsung Galaxy S4 or HTC One in the Google Play Store now. The "Google Play Edition" phones went live this morning, right on time, and are now for sale next to the Nexus phones and tablets. The GS4 Google Edition can be had for $649, while the HTC One goes for slightly less at $599. Both are running the latest version of Android 4.2 shod of all skins and add-ons, with promised updates via Google itself.
There's a lot to like about Sony's latest generation of Android devices. One od the things that most people don't like is the custom interface that Sony puts on pretty much everything. If you want to do away with it and get some sweet, clean Android Open Source Project code running on your shiny new Xperia Tablet Z, Sony is happy to oblige. They've posted an AOSP 4.2 build for the Tablet Z to GitHub, following their surprisingly open approach to other devices, most recently the Xperia Z flagship.
Among dedicated Android fans, there is a consensus that stock Android is the best experience. That being said, not everyone is smitten with the Nexus hardware. A new option for conflicted users is rumored to be dropping tomorrow at Google I/O. A version of the Samsung Galaxy S4 – dubbed the Google Edition – could be released with the latest version of stock Android on board.
If this is indeed true, it wouldn't be the first time Google has created a new variant of a Samsung product.
The difference is huge - it's like it went from Cupcake days to Jelly Bean in the blink of an eye. It would be nice if you could update Android the same way, wouldn't it?
Here are some images of the old (visible at archive.org) and new sites side-by-side (can you guess which one is which?):
After some teasing, Paranoid Android has unveiled (in a lovely promo image) their plan for multi-window functionality on Android, which they promise to "get right," – Halo.
The premise is simple, yet extremely ambitious in scope – allow apps to give you notifications right on top of your screen, which allow you to pop into that app without leaving the one you're in (no matter what it is), take care of business, and resume your experience uninterrupted.
Back in August of '12, Sony teamed up with Google to make the Xperia S an officially supported AOSP device. The project initially got off to a decent start, but after an issue with some proprietary software binaries that couldn't be released by either Sony or Google, the project was canned on the official side and moved to Sony's GitHub, where it can still be found today.
Now, the company is doing something similar with the Xperia Z, minus Google's interaction from the get-go.
Earlier today, Google started pushing some new open source code to AOSP (Android Open Source Project) marked with 2 new tags: android-4.2.2_r1.1 and android-4.2.2_r1.2. The build number corresponding to the 4.2.2_r1.2 release is JDQ39E.
The dates you see here are commit dates, not dates the commits were made public (which is today, April 17th 2013)
After weeding out the changes from the commit logs, it looks like all of them are, as expected, very minor.
As an addendum to the announcement of Google completing AOSP rollout for Android 4.2.2, I wanted to highlight a big milestone for the Nexus program - something that has never been the case before today.
After asking JBQ (not to be confused with JDQ39) a follow-up question, I was able to get some clarity on his earlier post and confirm that as of today, with the release of Android 4.2.2 binaries, we have for the first time ever Nexus devices that have 100% of proprietary binaries available.