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.
The Xperia Z is a pretty spiffy flagship phone, and tough as well, thanks to its IP55/IP57 Ingress Protection rating. But now there's a more specialized model coming, the Xperia ZR, designed specifically for waterproof functioning in even wetter environments. The new phone is manufactured to the higher IP55/IP58 standard, meaning that it can be safely submersed in 1.5 meters of water for up to 30 minutes.
The Xperia ZR roughly follows the Z's design, getting rid of some of the slim lines and premium materials for the sake of its more waterproof chassis.
Hey Sony. It's been a while since I last ranted about how you're kinda-sorta screwing up that whole smartphone business of yours. In fact, it's been almost a year to the day. I had really hoped that by this year everyone's favorite Japanese electronics mega-corporation would have figured out the smartphone market to a reasonable extent in the US, but surprise: they haven't!
I really don't mean to single out Sony, but sometimes, it's very difficult to watch a company that is very clearly capable of making good products make such terrible decisions.
Does the HTC One leave you cold, T-Mobile customer? Tired of all the plastic on Galaxies big and small? Then look at this filing in the Federal Communication Commission's ever-expanding database of certified wireless devices. It's the Xperia Z, Sony's current flagship model, with wireless bands for T-Mobile's standard HSPA+ network and its shiny new LTE spectrum as well. That makes the stylish smartphone as close to a done deal as we're likely to get until T-Mobile starts its press campaign.
Sony's Xperia Tablet Z, the tablet first announced for Japan about three months ago, and spotted again at MWC, is finally up for pre-order for those customers awaiting the device's US launch.
When we saw the Tablet Z in person at Mobile World Congress, its super thin, super light water/dust-resistant frame impressed. Its 1920x1200 10.1" display, S4 Pro processor, 2GB of RAM and promised Android 4.2 base also sounded good on paper, but we concluded it could still be held back by two things: a 6000mAh battery, and a $500 price point for the 16GB model.
It's been a long time coming, guys – we've definitely seen our fair share of upset Xperia P owners who've been waiting for this update. But, the good news is that it's finally here, and the P is joined by the go and E Dual.
According to the Sony blog, the 4.1 update not only brings Jelly Bean, but also a slew of new enhancements that Sony has been working to "blend" with the OS.
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.
It seems that the CyanogenMod team is on a roll with Sony devices. Just yesterday the first nightly turned up for the Xperia ZL, and today the Xperia Z and Xperia V are joining the ranks. We know the two phones can survive water and boiling soup, but thanks to CyanogenMod, they will now survive the test of time with the latest versions of Android.
The CyanogenMod crew is at it again, welcoming a new device into the fold. This time around, the Xperia ZL is joining the extensive collection of devices with CM 10.1 support.
It could oftentimes be unstable and not properly tested, lacking any changelogs, but eventually evolving into alphas, betas, release candidates, and finally stable releases.