2 Comments

Summary:

Shown off this week, HTC’s new One is better than the old One in several ways and it may share the same processor as the Samsung Galaxy S4. Plus you can now play with Ubuntu on a Nexus device now.

android-this-week

This week saw the introduction of HTC’s next flagship phone, named the HTC One just like its predecessor. The handset materials and design are a bit of a departure for HTC as the new phone will use an all aluminum enclosure and a pair of front-facing speakers. As a result, the audio experience ought to be a highlight for the One, but visually oriented readers will be happy with the display as well: HTC is packing in 468 pixels per inch on the 4.7-inch, 1080p display.

HTC OneHTC’s One will include an LTE radio for fast mobile broadband and run on Google’s Android Jelly Bean software. The company is also including several of its own software features: BlinkFeed streams news, social networking updates and other information; Sense TV provides video content guides and uses an infrared sensor turning the One into a remote control; customized home screens are available, similar to prior versions of HTC’s sense software.

The flagship phone doesn’t yet have a price tag as that will come from carriers — likely next month — but will be available in both a 32- and 64 GB option. Other internal specs include a 1.7 GHz quad-core Snapdragon 600 chipset, 2 GB of memory, NFC radio and integrated 2300 mAh battery.

Speaking of Snapdragons, Qualcomm’s chip may power the Samsung Galaxy S4 phone. Samsung has yet to introduce the revised Galaxy but online benchmarks and other evidence point to the company opting for a Snapdragon over its own Exynos chip. Reports indicate the same Snapdragon 600 found in the HTC One will be inside the Galaxy S4, due to heat issues when testing the Samsung 8-core Exynos chip.

This wouldn’t be the first time Samsung chose a competitors chip to power its own smartphones however. The US version of the Galaxy S III also used a Snapdragon chip, mainly because at the time of launch, Samsung hadn’t yet integrated LTE support in the Exynos silicon. In some sense, Samsung is lucky that it has a secondary option for chipsets, else its flagship phone could face delays. We’ll get the story for sure within the next few weeks as Samsung is expected to hold a launch event for the new Galaxy smartphone on or around March 14.

Ubuntu on NexusWe don’t, however, have to wait to see Ubuntu on a smartphone: This week, Canonical released instructions on how to install a preview of the alternative platform on Google’s Nexus line of tablets and phones. You’ll end up wiping out your Android system if you do this, but Canonical provided the handy links to Google’s own factory images for all Nexus devices, making it easy to reinstall Android.

I haven’t taken the Ubuntu plunge on my Galaxy Nexus yet, but expect to next week. From all accounts I’ve read so far, the Ubuntu interface is intuitive, but the software is still rough around the edges. There are still quite a few features and functions not ready yet although the Nexus phones will still be able to make calls and connect to both Wi-Fi and mobile broadband networks.

  1. The s4 will ot use the same processor that the htc one does. It will use a snappdragon 600 yes but with 1.9 ghz not 1, 7, the same report said the s4 would be 7, 7 mm thick and will use a new type of LCD screen (full hd) not a amoled

    Share
  2. Can you run any of the various virtual Android installs on top of Ubuntu-on-nexus?

    There’s the Android emulator out there (I don’t recall what it’s called), plus there’s VMware-like solutions, with Android VM images. I sort of wonder if there’s anything like that you could run on top of the Ubuntu-on-Nexus to get a tablet that is fully usable with both Ubuntu and Android simultaneously.

    And, then, there’s the future possibility of the lesser option: someone creates a way to dual boot between Ubuntu and Android.

    The thing I sort of hope for:
    a) ChromeOS as the base layer, with all of the things it does to handle integrity of the underlying OS
    b) the ability to run Ubuntu and/or Android in virtual environments on top of ChromeOS

    Then you’ve got a good solid, lean fast booting infrastructure, but the flexibility and power to still do real work (Ubuntu) or recreational tablet stuff (Android).

    Share

Comments have been disabled for this post