Microsoft tells us that Mango updates began this morning around 10AM PST. The process is beginning gradually and will slowly ramp up — they hope to have the update available to most existing customers within 4 weeks. The update is being deployed globally, across all carriers and phones. They say that 98% of existing Windows Phone 7 devices will have access to the update when all is said and done. Kudos to Microsoft for getting the update to nearly all devices, rather than just to a specific carrier or specific phone before everyone else (*cough*Google/Android*cough*).
If you want to find out where your update is, Microsoft has a page which will give you some detail as to the status of the update for your particular carrier. If you’re on a US carrier, you’ll want to check here.Â InternationalÂ folksÂ shouldÂ give this link a try for Windows Phone 7.5 Mango update status. You’llÂ receiveÂ a message on your phone when the update is ready, and you’ll need to plug it into your computer for the update to commence. If you don’t already have the Zune software, or Windows Phone 7 Connector (OSX) installed, you’ll want to do that as they are required for update instillation.
As mentioned, previously not revealed facets of Windows Phone 7.5 include tethering functionality and a web version of the App Marketplace. ReportsÂ indicateÂ that tethering will only be coming to new phones with Mango installed; it’s unclear whether or not this is a software or hardware problem (my vote is on the former). The web Marketplace is already available for browsingÂ and is part for the course — offering ratings, screenshots, top app lists, and the ability to download apps to your phone wirelessly, thanks to your phone’s association with your Windows Live account.
Software, UncategorizedComments Off on Everything You Need to Know About the Windows Phone 7.5 Mango Update
I managed to whip off a quick video showing some of the enhancements for the Eee Pad transformer delivered by the Android Honeycomb 3.1 update. I bought my Eee Pad from Taiwan and the hardware identifies it asÂ TaiwaneseÂ hardware so I think I got the update earlier than devices from otherÂ Countries.
Asus claim some performance increases and reliability improvements but they’re not that noticeable to me as I thought it was pretty responsive on 3.0. They have added some new apps including a video editor and the Kindle app. There’s still patchy support for video codecs with no improvement on its ability to play a variety of formats and I haven’t found any HD video files it can play without skipping yet.
Overall an improvement especially with the new apps but I would still like to see more video format support, especially now that we can edit videos on the device.
Devices, Reviews, SoftwareComments Off on Android 3.1 Honeycomb Update for the Asus Eee Pad Transformer [video]
Our Motorola Xoom [tracking page] has finally managed to find the Android 3.1 Honeycomb update that Google pushed out the other day. We gave you a thorough overview of the 3.1 update based on the official information provided, but there’s only so much that text can say. To understand the changes sometimes you just have to experience them. Often times a lot of the little changes go largely undocumented. So to answer that call, we’ve got a hands-on video for you. Have a look:
WARNING: Please turn your volume down before 14:20. I forgot to enable airplane mode on my phone and the subsequent vibration is frighteningly loud. My apologies!
Hands On, Software, UncategorizedComments Off on Android 3.1 Hands-on Testing: Performance, Browser Quick Controls, Flash Playback, and More [video]
At Google I/O 2011, Honeycomb 3.1, which brings a number of user and developer enhancements, has been officially announced and detailed. Google also says that Honeycomb 3.1 will be making its way to Google TV powered devices this summer; very exciting news as it means that Google TV devices will now have access to apps from the Android Market!
Android 3.1 is rolling out now to Motorla Xoom [tracking page] devices on Verizon’s network, however our Xoom still has no idea that an update is available, so it’s likely coming in waves. Nicole Scott of NetbookNews.com has a tip for forcing your Xoom to check for the update (though checking for it doesn’t necessarily mean that it’ll find it!).
Honeycomb 3.1 Major Changes
Resizable Widgets and UI Changes
In Android 3.1, widgets have support for dynamic resizing which is a great feature as I can only currently see a pathetic three emails in the Gmail widget. Google notes that it is really painless for developers to add dynamic-size capability to their widgets with just a few lines of code.
There has also been a number of minor adjustments to the UI. Google says that â€œUI transitions are improved throughout the system and across the standard appsâ€ which will hopefully make homescreen swiping more smooth. I’ve been unimpressed with the fluidity of homescreen swiping (and general UI performance) thus far.
Other changes are aiming to make the experience more intuitive â€“ something that Honeycomb desperately needs. Android 3.0 is really not the intuitive experience that you hope it would be. From my own observations, novice users have a hard time using the device because of this. Sometimes I too am unsure as to where to look for a particular button or function within an application because it just isn’t clear what certain buttons will do. Trial-and-error should not be the underlying philosophy of your interface. Any changes toward making the operating system â€œeasier to see, understand, and useâ€, as Google says, will be an improvement to the OS.
Accessibility has also been enhanced, and I’m always happy to see that the industry is not skimping in this department. From Apple’s iOS to Android, accessibility options are there to help as many people as possible make use of these devices. Android 3.1 enhances accessibility with consistent voice-feedback throughout the UI.
The recent-apps button, which Google implemented in 3.0 to take place of the home-hold gesture in Android for phones, has been extended to show a greater number of recently used applications (rather than just 5) by allowing the user to scroll through the list.
Android 3.1 brings along robust USB-host support for peripherals and accessories. Google is touting support for keyboards, mice, game controllers, and digital cameras. Developers are also free to build on the USB support to add compatibility with additional devices for applications â€“ great for more obscure USB devices, or support for specific types of devices (such as a game controller with proprietary buttons).
This also opens up the realm of controlling any number of USB accessories for more interesting uses. Google lists â€œrobotics controllers, docking stations, diagnostic and musical equipment, kiosks, card readers, and much more,â€ as examples of such devices that could be controlled and interacted with using an Android device thanks to this new USB support.
Honeycomb 3.1 is also improving a number of built-in applications.
The browser’s â€œQuick Controlsâ€ have been improved. The well received Quick Controls, enabled through the labs section of the browser settings, allow the user to slide in from the left or right of the screen to get a radial menu that allows them to control the browser. Most notably, tab management has been moved into the Quick Controls which should free up even more space for web content and allow almost all browser functions to be performed from one place.
Some standards related enhancements have been made to the browser such as support for CSS 3D, animations, and CSS fixed position. There’s also support for embedded HTML5 video, and Google says that performance when zooming has been â€œdramaticallyâ€ improved â€“ I’m looking forward to that!
The Gallery app now supports something called Picture Transfer Protocol which will allow users to plug a USB camera into their 3.1 device and import photos directly into the Gallery app.
Exciting news for audiophiles: Android 3.1 now supports FLAC, the lossless audio codec (hat tip to Android Police)! I’m not sure whether or not the soundcards in most Android devices are really up to this task yet, but it’s good that the option is now available.
On the Xoom particularly, I hear a whole lot of popping and hissing coming from the device, even when no sound is playing. Even with lossless audio playback, the audio-bottleneck may well end up being the sound hardware. Perhaps we’ll see tablets pushing higher quality audio equipment to make use of FLAC and differentiate themselves from other devices down the road.
If you’re interested, here’s the technical bit that I am in no position to comment on:
Mono/Stereo (no multichannel). Sample rates up to 48 kHz (but up to 44.1 kHz is recommended on devices with 44.1 kHz output, as the 48 to 44.1 kHz downsampler does not include a low-pass filter). 16-bit recommended; no dither applied for 24-bit.
This would be a â€œtake that!â€ moment from Google to Apple, but Apple has had lossless audio support in their iOS devices for quite some time. The format is a proprietary ALAC, which only serves to lock users further into the Apple ecosystem; still, Android isn’t the only lossless game in town.
In an effort to un-fork the Android OS, which currently operates three builds (phone/tablet/TV), Google is bringing Honeycomb 3.1 to Google TV through an OTA update to existing devices this summer. This will open up the world of apps from the Android Market onto Google TV-powered devices which is exciting news for developers and users alike. New Google TV units are also in the works from Sony, Vizio, Samsung, and Logitech.
As mentioned, the Motorola Xoom on Verizon is the first device to get the 3.1 update. Google hasn’t made it clear when the rest of the world will see 3.1, and even the WiFi-only Xoom is left out in the rain at the time of writing. According to Engadget, Google has said that 3.1 would be hitting the Samsung Galaxy Tab 10 (which was given to attendees of Google I/O) in the â€œnext couple of weeks.â€ There’s some hope that all Honeycomb devices will have access to the update at that time, depending on the whims of individual carriers and OEMS.