Let's be real: a four-digit code isn't very much separating a determined bandit from your data, which is all that the iPhone affords. Granted, the phone locks up after a few attempts to slow your arch-nemeses down a notch or two, but if your code is your birthday or the last four digits of your phone number -- and you know it is, so just admit it -- they'll eventually figure it out anyway. On second thought, though, never mind, because it turns out there's a pretty effective way around these formalities -- 2.0.1 and 2.0.2 have both been confirmed to let you around the passcode lock simply by hitting Emergency Call and double-clicking the home button. At this point, the user will have access to your Favorites list, which is pretty bad as-is, but from here, they'll be able to click on an arrow and use links within your contacts to get out to the SMS, Maps, or Safari apps. If you change the home button functionality from the default (Favorites) to Home, then nothing will happen at the Emergency Call screen -- your phone is safe from prying eyes, we guess. The iPod option will kick the user into the iPod app, though, which we think is almost as bad as the Favorites exploit, because we'd really rather not our thieves know that we listen to Hannah Montana. MacRumors is reporting that it may have already been fixed for a future firmware release, so yeah, any minute now would be just great, Apple.

[Thanks to everyone who sent this in]

We're not sure if it's coincidence or if there's some concerted effort to push out overdue Windows Mobile 6.1 updates all of a sudden, but for whatever reason, Verizon's XV6800 is joining the AT&T Tilt this week in offering an official upgrade package for the first time. Could've come a little quicker, honestly -- Sprint beat 'em out the door by a country mile -- but let's just thank our lucky stars that it finally happened, shall we?

[Thanks to everyone who sent this in]

Hey, S60 owners, have you had this nagging sense over the past year or two that you're somehow getting slighted by Nokia, but you haven't been able to put your finger on why? No worries, we've figured it out: it's the calculator. Nokia's mainstream dumbphone platform has featured a far better and more capable built-in calculator app than S60 for a while now, which really doesn't make a whole heck of a lot of sense; granted, you can get better ones from third-party developers, but the point is you shouldn't have to. Thankfully, Nokia agrees, and they've started to toy around with the idea of replacing the S60 calc with its little brother's -- a relatively easy process, since the latter is written in Java. On one hand, it'd be a shame to see a core S60 app move from native code to Java, but on the other hand, if it's a better app and the JVM is transparent, who really cares? Anyway, the ported app is chilling in Nokia's Beta Labs as we speak, just waiting for customer feedback before the higher-ups make a judgment call on whether to integrate it into future S60 releases. The power's in your hands, people, so you may as well take advantage.

So patent holding firm Klausner Technologies figures it has this whole litigation thing down to a T at this point, having already sued a who's-who of companies having anything to do with visual voicemail in the past and ultimately coming away with a whole bunch of lucrative license agreements for its efforts (eleven, to be exact). Needless to say, any new company that tries to break into the game at this point is probably going to get treated with the same warm, fuzzy love, and Verizon and LG are experiencing that firsthand. Klausner has announced that it has filed suit against both companies in Texas federal court, presumably in response to Big Red's recent launch of the refreshed Voyager featuring visual voicemail software on board. Given the track record Klausner has, guys, you might just want to cut to the chase here and pay up.

Pretty much everyone's saying that location-based services for phones are the Next Big Thing -- thing is, they've been saying that for three or four Things back now. Integrated GPS, AGPS, and comprehensive, highly accurate cell databases are finally making trackdowns a reality these days, but finding decent software to take advantage of the capability can still be a challenge thanks to some of the same issues that have been plaguing mobile platforms for years: platform dependence, slow uptake on downloads, bugginess, the list goes on. Wouldn't it be great if you could just hit up your favorite mobile-optimized site and get a location lock, no app required? That's what Google's hoping to do with its new Gears Geolocation API, which third parties can plug into their sites and automatically take advantage of both tower and GPS-based positioning. It only works on Internet Explorer on WinMo pieces at the moment, but naturally, they're looking to spread it far and wide over time.

[Via Phone Scoop]

It leaked ages ago, but the Windows Mobile 6.1 upgrade for your beloved Tilt is now ever so slightly more legit now that it's made an official appearance on HTC's support site. The big draws here are Video Share support, reconfigurability for the push-to-talk button, and all the other spoils that come with the WinMo 6.1 we know and love, tolerate, or hate, depending on your disposition.

[Via MobileBurn and WMExperts, thanks to everyone who sent this in]

So we can rest easy for another night -- and the so can the Bluetooth headsets of would-be Dream owners, knowing they've dodged a bullet and won't be unceremoniously tossed into the compactor in a couple months' time. The removal of Bluetooth APIs for developers in the latest build of the Android SDK stoked fears that the nearly ubiquitous standard would somehow get dropped from the first round of devices, but Google has stepped in with the straight dope to clarify why exactly the references disappeared: Android's developers plumb ran out of time to make it available and fully functional to third parties. Engineer Nick Pelly makes it clear on no uncertain terms that the first devices will support headsets and the like out of the box, but to meet the gold deadline, they had to nix it from the publicly accessible APIs. The good news is that they want to add usable APIs back in with a future, post-1.0 release, but that won't be doing the first round of devs (and buyers) much good.

The story with another yanked API, meanwhile, is a little different. As the name implies, GTalkService was intended to open up Google Talk's XMPP-based framework to applications in such a way that they could be handled like any other message on the device. Cool, yes, but the company's security gurus realized that the functionality opened up a potential can of security worms, noting for instance that a multiplayer game could repurpose a user's Google Talk account for in-game contact, at which point a bunch of random n00bs could suddenly appear on your buddy list. Not cool. Google's verbiage leads us to believe that GTalkService won't be reintroduced any time soon, either, so we're just going to have to get over that one.

[Via Android Community]

Along with the all-new form factor will come an all-new -- well, kinda new -- software build for RIM when it releases the BlackBerry Pearl (or KickStart, or whatever the hell they decide to call it) 8200 series later this year. The most fliptastic of the Pearls will join the Bold in sporting BlackBerry OS 4.6, and shots are surfacing of what exactly that'll look like once it gets grafted onto T-Mobile's WiFi-equipped 8220 model. As one might expect, it looks like it's taking a lot of UI cues already seen and enjoyed on the Bold with the usual T-Mobile twists added in like myFaves support; in particular, we're loving the insanely slick stopwatch display. Too bad we'll use it... oh, never. Cell Phone Signal likes October for the 8220's release, which runs the risk of burying it beneath the Dream -- maybe that rumored $50 out-the-door price can move a few, though. That, or overflow once the Dream stock dries up.

Developers are mad as hell about the copy / paste situation on the iPhone, and they're not gonna take it anymore. Despite rumblings of the long-overdue feature making an appearance in version 2.1, a grass-roots effort has been started in the form of OpenClip.org to implement a totally independent, third-party clipboard solution that apparently manages to remain entirely within the bounds of Apple's airtight SDK agreement that significantly limits what App Store apps can and cannot do. Some eleven apps are already listed as having pledged support for the OpenClip standard, which will inevitably be wiped out if Apple decides to do something official -- which, let's be real, should've happened ages ago. Follow the break for a video demo of OpenClip in action.

[Via MacRumors]

Hey, hackers! Now that we've got the attention of millions upon millions of incredibly talented individuals, here's your next challenge. India's Airtel -- which is offering Apple's iPhone 3G at a near-stratospheric price -- has claimed that "even the most deadly hackers on the planet won't be able to crack the codes that support the iPhone's Airtel applications with rival company SIMs." Just so you know, it appears that Airtel worked with Apple to develop "operator-specific iPhone applications," which is an interesting tidbit in and of itself. But let's focus on the task at hand here, and that's proving that making ridiculous claims about impenetrability always comes back to bite ya.

[Image courtesy of Zedomax, thanks Akshay]

And to think, we actually believed that Nike and Apple were this close to delivering the long-awaited running application for the iPhone. While it was widely reported that these shots were indeed the real deal, AppleInsider is pointing out a chink in the armor: Cupertino doesn't offer iPhone developers a programming interface for accessing one's music, yet this mysterious program clearly showed someone listening to Chris Martin and friends (an unreleased song, evidently) while attempting to make it to 0.02km. The take away? It's still pretty likely that the two outfits are working to create a fitness program for the App Store, but those screenshots ain't it.

[Thanks, Michael]

Billed as a "compliment" to the existing PwnageTool, iphone-dev has released a working beta of what it calls QuickPwn, a utility that uses a crafty new jailbreaking method to forgo the installation of a fresh IPSW. In layman's terms, that means you can have a fully jailbroken phone running 2.0.1 (and soon 2.0.2, we'd imagine) without the mild discomfort of having to restore your precious sidearm from scratch. The tool's still being developed and is currently only available on Windows, though the team is quick to point out that because QuickPwn operates only on the iPhone's app processor, any screw-ups should be totally undoable. Be that as it may, you know the drill: keep your gloves up, protect yourselves at all times, and let's have a clean fight.

[Via Boy Genius Report]

Hopes were high that 2.0.2 would decisively crush the reception woes some iPhone 3G owners have experienced since taking delivery of their cracking beauties; dropped calls, latching onto EDGE reception when 3G (also known as "the good stuff") is available, and general signal strength wonkiness have all plagued a select group of handsets since launch, making for a decidedly MobileMe-like user experience. Some upgraders are actually reporting just the opposite, though -- for these lucky few, 2.0.2 seems to be making reception somehow worse than it already was, and what's more, there are intermittent reports cropping up of broken third-party apps, too. With the 1.x line of builds having chugged along with relatively little drama for a year, here's our question: what the hell is going on? Why does 2.0, after two post-launch builds, still feel like a beta? MobileMe took the lion's share of the fall for Apple having spread itself too thin through the launch-heavy summer months, but did some of that fire-drill mentality trickle over to the breadwinner, too? Sound off in comments with your experiences putting 2.0.2 through its paces so far!

[Via Mobility Site]

Update: Apparently Steve Jobs, who should have his face buried in a developer workstation somewhere in Cupertino slaving away on iPhone bug fixes, somehow found the time to slack off for half an hour and fire off an email to some guy who wrote him complaining about third-party apps that are crashing on startup. Jobs allegedly says that the issue is a "known iPhone bug" and that it'll be fixed in the next update come September -- but frankly, we wish he'd let his assistants attend to this sort of needless communication so he could get back to, you know, writing code and inventing phones. Thanks, Alexander!

Update 2: An Ars Technica reader seems to have developed a workaround to the crushing pain of dead third-party (and installed first-party) apps and iPod player weirdness: go back to iTunes 7.7 from 7.7.1. It's not for the faint of heart because you've got to reset the phone and delete some files off the computer, but until this supposed firmware update (and possible iTunes update) rolls around in September, it may be the best thing affected users have going. Thanks, Garrett!

It has taken its sweet, sweet time in arriving, but it seems the iPhone Nike+ running application is just... about... here. A slew of new screenshots of the application have emerged, and while there are no juicy tidbits to accompany 'em (release date, cost, etc.), we all know how many lines of text a single snapshot is worth. Hang tight runners, the app you've been waiting (and waiting) for can't be far from the finish line now.

[Via MacRumors]

Google feels really badly about that several month-long stretch where it kept any and all updates to its Android SDK out of the public limelight, developers, honest, but it wants to make it up to you. It seems that yesterday's 0.9 release, which represented the first official SDK available with a platform even remotely resembling what Google intends to release on retail devices this fall, was just the first in a string of goings-on leading up to the grand 1.0 launch in the coming months according to a new roadmap published on the Android site. To start, there'll be "additional Android 1.0 (pre) SDK releases made available, as necessary" in September, followed by the first 1.0-compatible release in the Q3 to Q4 timeframe (that's any time between now and the end of December, for you calendar-disadvantaged folk). Finally, the Android source will leak out in the fourth quarter along with the first "Android 1.0 devices" -- pay special attention to the plural "devices" there -- and an announcement about Android Developer Challenge II. It gives us a warm fuzzy to see that Google's interested in keeping its devs engaged with these contests on an ongoing basis, because let's be honest: "prize money" has a much nicer ring to it than "VC money" ever will.

[Via Talk Android]