Back in much simpler times, TomTom's navigation app had claimed compatibility with all iPhone and iPod touch models. Then suddenly, somewhere along the primrose path to publication, original iPhone and iPod touch support evaporated. But no more. TomTom's pushed an update that allows for turn-by-turn navigation, but of course, you'll still need the car kit to work. Was this the missing link between your $100 and owning this app? [Warning: iTunes link]

[Thanks, Scott M]

The Intel P55 Express chipset snafu that caused iPhones to lose their syncing minds has now been remedied -- at least by one motherboard maker. Gigabyte has issued a BIOS update making things all hunky-dory between the phone and the mobo, putting your troubles to an end. The P55 is Intel's latest midrange chipset and orchestrates things for newer Core i5 / i7 machines. The other two P55 purveyors, ASUS and MSI, were also caught by the bug, and there are anecdotal reports of success with an ASUS BIOS update, but not official fixes as of yet. Given the competitive nature of this market, though, we'd be surprised if those two companies didn't quickly follow suit. All's well that ends well, right?

Read - Gigabyte Beta BIOS download page
Read - Update fixes iPhone sync problem

The iPhone is one of the most wildly popular phones the world has ever seen, while Windows 7 is well on its way to becoming the globe's most ubiquitous OS. So compatibility between the two would be kinda sorta important, right? Tell that to Intel's quality control team who seem to have somehow missed an issue between Apple's app carrier deluxe and the P55 Express chipset's USB controller. Consistent (and persistent) syncing issues have been reported on Apple's support forums, wherein iTunes on Windows 7 machines recognizes the iPhone, but spits out an "error 0xE8000065" message whenever the user attempts to sync. While some have found limited success with using PCI-based USB cards (and bypassing the chipset), this is clearly a major issue and something Apple would expect to be fixed before shipping its Core i5 / i7 iMacs, which are likely to sport the chipset. Hit the read link for the original thread of sorrow and regret, and do chime in with your own experience in the comments.

[Via The Register]

One of Apple's many curious restrictions on iPhone apps has now been lifted. It used to be that, in order for developers to have microtransactions / in-app purchases, they had to charge something upfront for the software, essentially requiring consumers to pay at least twice, or not at all. Well, all that's changed, as the company has sent word to its developer community that the restriction has been lifted, meaning those annoying "Lite" and "Full" versions cluttering the app store can now be one and the same, with folks downloading the demo and paying to upgrade from within the app itself, a model that's worked to success in other software ecosystems like Xbox Live. Sure, there's gonna be developers out there that abuse the newly-minted business model, but it's not like anything was stopping them before when they charged $2 upfront only to get you again later. The mass email announcement is reprinted after the break. [Warning: read link requires iPhone developer account]

[Via Daring Fireball]

The game's back on. Palm just announced the availability of its 1.2.1 update to WebOS for the Palm Pre and, well, that's it for the time being. It fixes Exchange mail syncing issues experienced by some users, which is nice, but for everyone else it re-enables media sync with iTunes 9.0.1, with or without the USB-IF's support. In fact, Palm has signaled its commitment to its rogue approach by improving synchronization with the Photos app to keep the album structure in tact while allowing lower-resolution images to be synced to the Pre. Oh happy day -- enjoy it while it lasts Pre owners.

We've just heard from AT&T that new carrier settings for the iPhone 3G and 3GS will be available "late morning" Pacific Time (which would be early afternoon Eastern) this Friday, September 25, which will finally enable MMS support. Owners will have to tether up to iTunes to grab those settings, so fish out your cable (as if you don't have it permanently attached to your machine already) and make sure you've got some solid time in front of the computer to check for the update over and over (and over) again, alright?

[Thanks, Frank]

The very public fight between Palm and Apple to allow the Pre to sync directly to iTunes (without just... you know, doing it the same way as everyone else) is showing no signs of slowing down, with Palm continuing to pursue every angle it can to rile up Cupertino -- most recently taking the battle up to the USB Implementers' Forum in an effort to stop Apple from restricting iTunes usage by the hardware's Vendor ID. Hard to say what ended up going down behind closed doors, but on an official level, the USB-IF is issuing a terse statement that it "communicated its position on the matter to both companies" and won't be speaking further on the issue "at this time." We'll see if anything ends up changing on the software side from the conversation, but separately, the Forum has mentioned to us that it considers this a member-to-member concern -- so in all likelihood, they're taking a hands-off approach.

Update: Digital Daily has come away with a very, very different story from the actual leaked communication, and it turns out that the USB-IF has actually sided against Palm on two different fronts. First, the Forum has told Palm that it doesn't see how blocking Palm's Vendor ID from accessing iTunes violates its policies; and second -- this might be the big one -- Palm's actually riled up the Forum by saying that it'll be using Apple's Vendor ID on the Pre going forward. It wants a clarification of Palm's "intent" within a week, saying such a move would be contrary to the rules and regs set out for the proper use of USB. At this point the question becomes, how many companies and industry bodies is Palm willing to piss off to keep iTunes working exactly the way it wants?

We had a feeling this day was coming. After Spotify's subscription music app was approved, offline listening intact, there was every indication that Rhapsody was next for christening. Especially with the feds watching Apple's every move. The free download just went hot and requires a $15 per month Rhapsody To Go subscription -- you can try it for free for a week -- and streams 64kbps quality (ugh) music over WiFi or cellular data (only, no off-line access) from a catalog of about 8 million tracks offered by the MTV and RealNetwork tie-up. Now go 'n get it.

Update: Added video demo after the break.

[Via Komo News, thanks Bill Y.]

Read -- Rhapsody App [iTunes link]

Here we go again: round umpteen of the fight to break and re-enable Pre syncing with iTunes is now underway thanks to the release of iTunes 9, and we're sure there's plenty more where this came from. Endlessly amusing to casual observers, yes, but Pre customers are the ones losing out -- sure, Palm might be able fix this in a jiffy (especially since they continue to tout compatibility with the Pixi), but meanwhile, media sync's out of the picture once more. Stay tuned for more on this as it develops.

As expected, Apple has blessed Spotify's streaming subscription music application with a home in its iTunes App Store. Additionally, the app is also making a first, less ballyhooed appearance on the Android Market. The free app allows you to stream any of its nearly 4 million tracks over WiFi or 3G and syncs playlists for playback while disconnected. It's available exclusively to Spotify Premium members in the UK, Sweden, Spain, France and Norway -- only the iPhone app is available in Finland. Great, so does that mean Rhapsody is next? Magic i-ball says all signs point to yes. Video overview of each app after the break.

P.S. We're seeing reports that the iPhone app won't play music in the background. The fix? Android.

[Thanks to everyone who sent this in]

Read -- Spotify on Android
Read -- Spotify on App Store

Yeah, we're pretty much all peeved by Apple suddenly ejecting all traces of Google Voice from the app store, but now it looks to have drawn the ire of the Federal Communications Commission, as well. According to a report from The Wall Street Journal, the agency has sent out three letters, one each to Apple, AT&T, and Google. To the latter company, it asked for a description of the Google Voice app and whether previous Google apps have been approved for the store (it has, but that's another interesting story). To Cupertino, it's asking the phone manufacturer to explain itself over the sudden exorcism and what involvement, if any, AT&T had in this decision. The report doesn't make a direct indication of what the letter to the carrier said, but we can imagine it's similar to what Apple got, plus some doodles at the end of a stick figure letting out an exasperated sigh. In a statement today, FCC Chairman Julius Genachowski said it "has a mission to foster a competitive wireless marketplace, protect and empower consumers, and promote innovation and investment." Hey Julius, while you're at it, can you see about Skype and Slingbox for us, too? Thanks.

Update: TechCrunch has published the three letters sent out, all very interesting reads. The FCC asks Apple specifically if any approved VoIP apps are allowed to be used over AT&T's 3G network, and more generally what are the "standards for considering and approving iPhone applications" and more details into the approval process. It also asks for the contact information of all developers of rejected Google Voice apps, presumably for further investigation. In the Google letter, it seems to be asking if Voice will be able to be utilized in any capacity over the web, without inclusion in the iTunes store. Unsurprisingly, a number of questions to Apple and AT&T concern the carrier's involvement in which apps or types of apps get rejected. All companies have until August 21st to respond and can request confidentiality on all or portions of their response.

So well-mannered, straight-laced iPhone users got a pretty big slap in the face yesterday by way of Apple's (and AT&T's, no doubt) total Google Voice rejection. Looks like jailbreakers are picking up the pieces, as GV Mobile developer Sean Kovacs -- whose app was in the iTunes store for some time before being yanked yesterday -- has ported the Voice client over to Cydia free of charge, although donations are gladly accepted. Even more interesting, but less concrete, Kovacs said he was already working on a web app version, possibly for submission to Palm's app catalog. No word on the fate of GVdialer, an app that was also unceremoniously pulled, but we wouldn't be surprised if it followed in similar footsteps.

Read - GV Mobile now on Cydia
Read - Sean Kovacs on Twitter

Perhaps the big G spoke too soon when it said its new Google Voice service was coming to iPhone. First, GV Mobile developer Sean Kovacs relays a phone call he had with Apple where he was notified of his app being removed from the iTunes store for duplicating built-in iPhone features -- an app that was originally and purportedly approved by Phil Schiller himself. Next out the door was GVdialer, and if you thought that was all bad, now comes word that Google's official Voice app was flat-out rejected by Cupertino. Now it's hard to say with certainty who's to blame for these app rejections, but a good many fingers are pointing to the cellular carriers -- and given AT&T's previous statements about the SlingPlayer app, it's hard to argue with that. For its part, the company hinted at finding a workaround via web apps, much like they did when Apple gave Latitude a cold shoulder -- but doesn't that feel just a little 2007?

[Via Apple Insider]

Read - Official Google Voice App Blocked from App Store
Read - GV Mobile is getting pulled from App Store
Read - Sean Kovac's Twitter status on Schiller

You should be refilling that popcorn bucket right about now. While we thought the next round of the Pre / iTunes syncing fiasco would probably be something simple like Apple releasing another quick patch, Palm has stepped it up a notch by complaining to the USB Implementers Forum over what it sees is "improper use of the Vendor ID number" by the gang at Cupertino. What the company means is that when an ID is applied for, a form is signed that states:

"Unauthorized use of assigned or unassigned USB Vendor ID Numbers and associated Product ID Numbers are strictly prohibited."

The implication here is that Palm believes Apple is violating this stature by disallowing certain Vendor IDs -- namely, Palm's -- from using iTunes. So how'd Palm manage to "fix" that syncing hole Apple managed to fill? From the looks of it, by misrepresenting its own Vendor ID, so that the Pre now shows up as a iPod / mass storage device made by Apple (ID 0x05ac) as opposed to one by Palm (ID 0x083) -- hence the complaint. Of course, lying about your own ID would seem to break with the aforementioned rule, too, so what we're left here is some muddled grey area and Palm apparently being okay with fudging some data to correct what it sees is an injustice. If anyone's curious, DVD Jon points out that the root USB Node is still identified as "Pre," so we very likely could see another round of these shenanigans in the not-too-distant future.

Finally, now's as good of a time as any to take a look at some of the peripheral casualties from this war of attrition. In an essay on his personal site that's been circulating the interwebs, Marc Deslauriers outlines the pangs he and the Linux community have felt over the years trying to use iPods on the open source platform, surmising that Apple is intentionally and repeatedly seeking ways to block non-iTunes programs from syncing in any way with its devices. This story is far from over, and as ugly as it looks now, it's probably only gonna get worse.

[Via Digg and Pre Central]

Read - Marc Deslauriers, "Goodbye Apple"
Read - Palm's lodges complaint with USB IF
Read - USB Vendor ID application
Read - Palm Pre USB hack confirmed