More and more smartphone manufacturers have been moving towards on-screen buttons, with Google really pushing for it over the physical button alternative. However, there are still a few OEMs (we're looking at you, Samsung) that have preferred to keep things a bit more traditional. Tell us which way you prefer and why.
4.4 KitKat Omni Lands on the Xperia T
As many of you are aware, an announcement was made during the BABBQ by some of the most outstanding developers in the Android world. A new ROM, called OmniROM, would be getting to an Android device near you and everything was find and dandy. Threads have been created in many fora across the site, where experienced and beginner devs alike have shown interest in trying to get this new community project working on as many devices as possible.
All the hype blew over, honey moon was done, and people stepped out of the public spotlight and got down with their hands dirty and sleeves up, attempting to get this to work. On top of that, we got the latest gift from Google in the form of source code for their latest sweet treat, Android 4.4 KitKat. (Personally, I still think that Key Lime Pie was a better, less commercial idea, but oh well.) After the drop, AOSP builds started popping across our site on many, many devices. Also, we got news that CM11 was ready for a few devices, including those in the Sony line up. Well, combining all the aforementioned, we get the news that a new build of 4.4 (Omni distro) is out for the Sony Xperia T, courtesy of XDA Recognized Developer tilal6991.
The build is currently in an alpha state, which means that tons of bugs are to be expected. Having said that, according to the dev, the only “real” issue that seems to be plaguing the device seems to be HDMI out. However, unless you have a dock or an MHL cable, you have little to nothing to worry about. The Omni project (as well as most AOSP versions of KitKat out there) is in a very early stage. So if you are downloading this to try and impress your friends with your new OS, keep in mind that things could happen along the way. Right now, the way the project basically requires that if you do download the ROM and attempt to install it, you must read and follow all instructions. If you are able to provide any kind of useful feedback in the shape of logcats, all the better. And if you do, please make sure that you submit these to the correct place.
So, if you have a Sony Xperia T and feel like giving it a new look with everything that the new version of Android has to offer, please feel free to drop by the thread and flash this to have your break of a KitKat bar.
You can find more information in the original thread. Happy flashing!
Want something on the XDA Portal? Send us a tip!
While there are frequent unexplained changes and pushes to Google's AOSP repositories, an interesting-looking new branch has been pushed out recently, called "master-soong". Taking a look at the changes made to the manifest repository (which is used to specify the repositories to be downloaded when building Android), it appears there are some new repositories making an appearance. Of note here are new prebuilt repositories for Go, and Ninja. Go is a programming language, created by Google, which compiles to produce...
There already are many solutions on the Google Play store if you want to send a link to one of your devices -- but what if you wanted to do it quickly without having to install any software or logging in to a website on the recipient end? Most apps require you to do either or both, which can be a hassle (or even a security risk) in some cases. Luckily, XDA Forum Member wyemun has developed CaastMe. Inspired by...