Hasta La Gadget!

Google’s been iterating its Maps client for Android devices at a positively ridiculous pace lately, burning through versions 3.4 and 4.0 in a span of just a few days last month — but hey, March is upon us, which apparently means it’s time for another fresh cut. This time around we’re looking at 4.1, though the mere 0.1 bump in the version number really doesn’t do this thing justice — they’ve redesigned the results screen, added a swipe gesture for moving between results, served up a new Latitude widget for the home screen, and brought in support for multiple Google accounts (for seeing different Buzz follows, for instance). The icing on the cake, though, is a new live wallpaper for Android 2.1 phones that’s a live map of your location, which sounds absurdly awesome — assuming it doesn’t beat your battery to a bloody pulp with constant GPS access, of course. It’s available now from the good ol’ Market for devices running Android 1.6 and up, so if you’re on a device that’s still stuck on Cupcake, feel free to shake your fist angrily at the sky a couple times. Interestingly, Google specifically says that the live wallpaper feature works on “Android 2.1+” devices — a sign that the next major build is around the corner, perhaps?

Google Maps 4.1 for Android brings multiple account support, trippy live map wallpaper originally appeared on Engadget on Thu, 18 Mar 2010 01:16:00 EST. Please see our terms for use of feeds.

Permalink Android Central  |  Google Mobile Blog  | Email this | Comments

HTC hasn’t filed its official reply to Apple’s patent lawsuit in court yet, but the company just gave us an updated and expanded statement on the case, saying that while it “strongly advocates intellectual property protection,” it disagrees with Apple’s actions and will “fully defend itself.” Natch. HTC obviously wasn’t eager to divulge whether or not that means it’s going to countersue Apple with its own patents, but we’re sort of expecting it — we’ll find out more when lawyers do their thing in a few weeks. Oh, and we also asked HTC if and when Google would get involved, but didn’t get an answer — we’ll let you know if we hear anything. Full statement after the break.

Continue reading HTC responds to Apple’s patent lawsuit, will ‘fully defend itself’

HTC responds to Apple’s patent lawsuit, will ‘fully defend itself’ originally appeared on Engadget on Thu, 18 Mar 2010 00:01:00 EST. Please see our terms for use of feeds.

Permalink   |   | Email this | Comments

Microsoft certainly set off a firestorm of controversy yesterday with the revelation that Windows Phone 7 Series won’t have copy and paste, since it doesn’t necessarily line up with what the company has said in private before — and the issue seems to have gotten even more clouded as people have started hacking around the emulator. So let’s set the record straight on what we were told, since it wasn’t ambiguous in any way: Microsoft says leaving clipboard operations out was a conscious design decision based on user research showing that people don’t actually use copy and paste very often, and that instead 7 Series features a systemwide data detection service which recognizes things like phone numbers and addresses so you can take action on them. Third-party apps can hook into this service, so that an email address can be routed to the email client of your choice, but there’s no copy and paste functionality. We specifically asked about Office and OneNote, and we were told that Microsoft’s research shows that people mostly want to view and comment on documents, not move things around. We also specifically asked if copy and paste was coming later and were told no, although we’d guess that it’s at least being worked on for a future version. Don’t take it from us, though — listen to Microsoft’s Todd Brix for yourself:

Microsoft on copy and paste in Windows Phone 7 Series: ‘people don’t do that’ originally appeared on Engadget on Wed, 17 Mar 2010 21:56:00 EST. Please see our terms for use of feeds.

Permalink   |   | Email this | Comments

We’ve definitely learned a ton about Windows Phone 7 Series here at MIX, but getting the full picture on multitasking has been difficult, since the OS isn’t ready, no one has final hardware, and the emulator seems to behave differently than actual devices and Microsoft’s descriptions. So let’s set the record straight on multitasking: it’s not going to happen, at least not in the traditional way. Not only have we directly confirmed this with Microsoft executives several times, but the developer sessions here are totally clear on the matter — you don’t tell 1000+ devs that they should expect their apps to be killed whenever the user switches away from them if you don’t mean it. Now, that’s not to say that the OS can’t do multitasking: first-party apps like the Zune player and IE can run in the background, and third-party apps are actually left running in a suspended state (Microsoft calls it “dehydrated”) as long as the system doesn’t need any additional resources. If the user cycles back to an app, it’s resumed (“rehydrated”) and life continues merrily along, but if the user opens other apps and the system needs additional resources, the app is killed without any indication or remorse.

If that sounds familiar, it’s because it’s basically a single-tasking riff on Android and Windows Mobile 6, both of which also purport to intelligently manage multiple running applications like this, and both of which usually find themselves greatly improved with manual task managers. We’ll have to see if Windows Phone 7 Series can do a better job once it ships — we have a feeling it will — and later down the line we’ll see if Microsoft decides to extend multitasking to third-party apps. But for now, just know that you’re not going to be running Pandora in the background while you do other tasks on a 7 Series device — it is a question we have specifically asked, and the answer, unfortunately, is no.

P.S. Still don’t believe us? Hear it for yourself directly from Microsoft’s Todd Brix:

Windows Phone 7 Series multitasking: the real deal originally appeared on Engadget on Wed, 17 Mar 2010 20:34:00 EST. Please see our terms for use of feeds.

Permalink   |   | Email this | Comments

While most of the FCC’s new Broadband plan has been about, well, broadband, there’s also some great news for HDTV fans. We expected a few mentions about CableCARD and its future when the FCC requested comments and declared it a failure, but we’re still glad to see that the FCC listened to consumer electronics companies like TiVo and Sony — among others. The biggest news is that the FCC has asked the industry to come up with a residential IP gateway that is open and that will provide same abilities as your provider’s equipment, and most importantly, it should enable the very same gear to work no matter what type of service you prefer, whether it be satellite, cable or fiber — for example, via various gateways the same TiVo would work with either DirecTV or Comcast. But while the FCC has given the industry until December of 2012 to define and deploy these IP gateways before implementing an “appropriate enforcement mechanism,” in the meantime the FCC wants to see the biggest issues with CableCARDs resolved by this Fall. The list below of immediate fixes is pretty impressive, and other than the persistent lack of video on demand support, it’ll help make CableCARD a pretty respectable solution.

• Ditch Tuning Adapters and let devices with Ethernet ports communicate upstream via IP to tune SDV channels.
• If a customer has a CableCARD in their leased set-top box, it must be reflected on the bill like any other CableCARD would.
• If the provider offers a self install for leased set-top boxes, they must also allow self install of a CableCARD.
• Software shouldn’t require the same CableLabs certification hardware does.

Continue reading A CableCARD replacement is due by December 2012, bandaids by this Fall

A CableCARD replacement is due by December 2012, bandaids by this Fall originally appeared on Engadget HD on Wed, 17 Mar 2010 19:41:00 EST. Please see our terms for use of feeds.

Permalink   |  Broadband.gov  | Email this | Comments