Android Honeycomb 3.1 has its rough spots–many rough spots, in fact. It looks excellent on 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 app. 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. Read more at allitreview.com