Apparatus Honeycomb 3.1 is @ DASHINGTHING REVIEW

04 Jul


Apparatus Honeycomb 3.1 Assess

Apparatus 3.0 has its rough spots–many rough spots, in fact. It looks excellenton the surface, but it needs work bottom. And nearly the edges. And…well, let’s just say I’m glad that Apparatus Honeycomb 3.1 is here.

We now have more in rank about what Apparatus Honeycomb 3.1 brings to the party, thankfulness to the full revision notes on Google’s developer site, and the changes are more far-accomplishment and vital than Google disguised.

The first huge news is that this translation does to be sure fix 3.0’s flaw that caused descriptions to render improperly in the Arcade Android Honeycomb 3.1app. I’ve noted this flaw numerous times–in part since it feels like such an evident blemish on an otherwise solid start to the Honeycomb/Apparatus 3.x platform. While Google hasn’t gone into too much detail as to what caused the issue to start with, I do have confirmation from Google that 3.1 should fix this issue. I can hazard a few guesses, but ultimately, what matters is that it’s fixed—which is why I look forwards to trying out Apparatus Honeycomb 3.1 on an array of tablets and considering how my photos look.

Other additions to Apparatus Honeycomb 3.1 contain help for the Open Belt and USB host APIs. By construction the USB stack into Honeycomb, the platform now gets USB host abilities and tablets in succession Honeycomb now have in commission logic level-help for administration USB peripherals–counting gamepads, joysticks, and storage devices–frankly. Technological terms aside, this means that Apparatus 3.1-based tablets will be able to power other gadgets through USB.

The newly introduced Open Belt figure aims to integrate peripherals like music gear, robotic systems, and exercise gear into the dosage (and phone) universe, all via USB.

This is all fantastic news, but there is one catch: Apparatus Honeycomb 3.1 still isn’t intended, at the in commission logic level, for administration open-air storage devices. This detail, which came out in conversations I had with Google engineers today, clarifies why the Apparatus file logic establishment is, well, a mess, and why I’ve had such variable experiences with Apparatus and comes off storage crosswise the various Honeycomb tablets I’ve tried (and I’ve tried all of them that are available so far).

“We don’t want to expose the user to file locations,” clarified Hiroshi Lockheimer, boss of engineering at Google. “How do you deal with that as a user? The not-excellent pledge is with the file browser.” Lockheimer says that many of the experiences I’ve seen so far are what party hardwaremanufacturers have enabled, as different to what Google has provided natively. The excellent thing is that Lockheimer says Google is looking at ways to do this; but the problem hasn’t been solved yet.


A additional constituent of the USB connectivity update is the addendum of a Media Transfer Protocol, to define how applications can be told when open-air cameras are emotionally involved and indifferent. The MTP also governs accessing and administration the files and associated metadata stored on emotionally involved cameras. The real-world applications for this are exciting: For model, shutterbugs can now straightforwardly view and share descriptions in the field, taking subsidy of a dosage’s large cover and Honeycomb’s ability to show EXIF data in the Arcade app.

Performance tweaks breed as well. Google made improvements to the animation framework in Apparatus Honeycomb 3.1, so that animations–such as the one you see when you tap the Apps menu button at the top-rightcorner of the home cover–flow more smoothly. And you can now scroll through the list of recently accessed apps that appears when you tap the task-switcher button. The apps most recently opened get priority; unfortunately, there’s no way to deal with what apps show, and in what order—you can’t emove an app from this cover entirely.

Android Honeycomb 3.1The Honeycomb (3.0) homescreen.Also new: The Home cover widgets can be resized horizontally or vertically, or both. This change allows for greater flexibility and customization in cover layout, and it means developers can start widgets that let you make better use of the available space.

This may sound like small tweaks, but that’s where many of the improvements lie–in the small fine points. Like the addendum of two new audio formats: ADTS AAC streaming audio and FLAC audio. The help of Real-Time Transport Protocol API for better in-app usage of on-plea data streaming for VOIP, push-to-talk, conferencing, and audio streaming applications. The ability for developers to improve how apps can locally cache data to minimize download time via a network connection. And the Web browser gains, among other finer points, the ability to play back embedded HTML 5 video inline—with hardware stepping up where doable.

Android Honeycomb 3.1Sounds like a lot? Let’s see how it looks on Honeycomb tablets. And dredge up—this is all just an interim OS relief. Lockheimer confirms that, ultimately, Honeycomb tablets will migrate to Ice Cream Sandwich–an imminent major update to Apparatus that will unify the dosage and smartphone versions of the OS–just as Gingerbread phones will migrate to Ice Cream Sandwich. The migration is expected to start headed for the end of 2011.

Leave a comment

Posted by on July 4, 2011 in Uncategorized


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: