Sprint's been more vocal than others about working on Froyo updates for its phones, whether it's a blog post, or taking to Twitter. But if you're thinking about bugging someone on the phone or in a store, you're not likely to get anywhere. Above is a memo that went out yesterday regarding the Samsung Epic 4G and Transform, and the Sanyo Zio. Clearly, there's no date scheduled for Froyo to ship, so don't ask.
You will, however, hear that Sprint "works closely with our manufacturing partners" in getting updates out the door and "as quickly as possible" and all the usual bullet points. No surprise there, other than the Zio's possibly going to get Froyo. We were on the fence about the Transform, but it's listed, too, so there you go.
Sprint's said it, and we'll say it again, too -- it'll be ready when it's ready.
Have you poked around in the Android Market recently? Unable to find an application that suites your needs due to the incredible amount of apps in the market? Well, have no fear, your friends here at Android Central are back at it again with another weekly rendition of our favorite app picks, so let's hit the jump and see what they are this week!
We know "something big is coming" from Samsung at Mobile World Congress in a few short weeks. And if this leaked teaser video (which almost looks unfinished) is any indication (and if it's real), we could well be looking at a Galaxy Tab 2. The rumor mill's got it coming with a Tegra 2 processor, and nobody can make up their minds on the screen tech.
And by the way, that SamsungUnpacked site has changed slightly, with word of an invite-only event Feb. 13, and open event Feb. 14. Guess we'll have to go to Barcelona to find out what's what. And go we shall. [YouTube via OLED-Display]
This is a big one, folks. The DL09 maintenance update that was recently pushed to the Samsung Fascinate breaks emergency calling -- for some of us, anyway -- when the phone is using a pattern lock. Discovered by SEAKevin from the Android Central Forums, the bug relates to the Emergency Call button when the pattern lock is enabled. Normally, when that button is pressed, the system will allow for E911 calls you having to unlock the phone. We are able to successfully reproduce the bug.
Instead of being taken to the emergency dialer screen, nothing happens. The dialer only shows after the correct unlock pattern has been entered -- completely defeating the purpose.
A couple of you are noting in the comments that you're not seeing this, so there might be some variables involved. But the fact that it's happening for anyone certainly is cause for some concern. Video of the bug is after the break. [Android Central Forums] Thanks, SEAKevin!
The good news -- the T-Mobile Vibrant indeed is getting its Froyo update. The bad news -- it looks like (thus far) you have to do it through Samsung's Mini Kies program. That's right, in this day and age of over-the-air updates, you have to plug your phone into a computer to update. Le sigh.
We've only been at it for an hour or so now, and Kies is still seeing our Vibrant as an "Unregistered device." Whatever that means.
You know that Froyo complacency a few of you have accused us of? It's rapidly going away. There's really no excuse for making an update this difficult. [via TMoNews]
The weekend is upon us once again, finally. Lots of exciting stuff has gone down this week so be sure to click back and catch up on anything you may have missed. Especially the podcast, it was pretty awesome. Be sure to hit up the forums and check out what's happening. Hope you all have a great weekend!
You want some actual news about accessories to go along with the initial pricing info for the Motorola Xoom tablet, eh? We've got you covered. Above is what Verizon apparently will have on hand, and it's quite the portfolio. You've got a camera kit cable (oooh, fancy), a media dock and advanced HDMI dock, silicone cases, travel charger and car charger. Everything a budding Android tableteer could need, we reckon. Thanks, K!
We haven't been blessed by Google with the update on our Nexi just yet, so we're on the lookout for the download link. If you feel like helping in the search, grab Alogcat from the market (link after the break), install it and run the app after you get the update message, but before you run the update. Save the output, and contact us. [Android Central forums] Thanks Droid800!
You might have stumbled across a story or two on the web today about Florian Mueller from FOSSpatents finding 43 more files in the Android source that look to be copied from Sun. I know I did, and had a heart wrenching editorial all ready to go, all about Google's open source strategy in their fight against Oracle, how it might fail, and how I was going to shave my beard and cry.
Then I stumbled across Ed Burnette's story on ZDNet.
All the fuss, all the hysteria, and most importantly all the cries against Google proclaiming them as thieves aren't what they seem. There are two sets of files in question -- a series of seven (PolicyNodeImpl.java, AclEntryImpl.java, AclImpl.java, GroupImpl.java, OwnerImpl.java, PermissionImpl.java, and PrincipalImpl.java) that contain proprietary code from Sun, and do exist, but they are in the unit test area of the AOSP source tree. This means they are only used to test software after it's built, and before it's shipped. To be clear -- these files are not used to build Android, nor are the shipped with Android. To take things a step further, these files were published by Sun on their own website to assist developers to test and debug -- exactly what Google is using them for.
The other 37 files exist as well, but are inside a zip file in an area of the source tree used for one particular audio chipset. These files look like they were uploaded by mistake, and also aren't used to build Android or ship with any Android devices. These will probably just be deleted from the tree, as they don't do anything.
Word on the street and in the Android Central Forums (same difference, really) is that the Nexus One is in the midst of an update to Android 2.2.2 -- build FRG83G. Nope, not Gingerbread yet. The new Froyo version is a scant 558kb, which Google says "contains important bug fixes."
Portions of this page are modifications based on work created and shared by the Android Open Source Project
and used according to terms described in the Creative Commons 2.5 Attribution License. AndroidCentral is an independent site
that is not affiliated with or endorsed by Google.