For the past several weeks I've noticed some rather strange behavior with Adium, the free and open-source multiservice IM client. On random occasions I suddenly appear invisible or offline to contacts in my buddy list while logged into my AIM account. And I'm not alone. Not a day goes by that I don't find myself asking a friend or co-worker why they are not online, only to learn they share the same problem. Either that or they're all making this up in effort to avoid conversing with me -- I have that effect on people.

The only cause to this problem, or pattern to its occurrence, I can come up with is a loose theory that it happens during periods of inactivity. My hunch is that when you appear "idle" AIM somehow misinterprets this as a disconnect. Locally you remain logged in, but AIM thinks otherwise. Luckily I may have discovered a workaround.

Launch iChat (quitting Adium is not required) and go into Preferences. Click on Accounts. Make sure your AIM account is selected, then click on the Security tab. Changing any of the settings in this options panel, then returning them to their original state, somehow magically vexes the problem, at least so far as I can tell.

I don't know whom to point fingers at in this case; AIM or Adium. Both begin with the letter A, so that makes each of them equally culpable in my opinion. Wherever the guilt may lie, I just want the problem fixed ASAP.

Something seems rotten, at least for some Mac users, with the Apple Mail program. Apple support boards are lighting up with reports of email messages being downloaded multiple times. This problem seems to be mostly with POP mail accounts, but even IMAP users are seeing it. There is another Apple support thread here with 10 pages of comments from unhappy Mail users.

I've noticed it myself twice. In the morning I bring up Mail and read what's come in overnight. Then a little later I re-open Apple Mail and the same messages download again. Of course my POP account is set to delete everything from the server, and my settings have not changed.

This is the first really bad behavior I've seen from Apple Mail since OS X came out in 2001. This most recent glitch seems to have popped up in the 10.6.1 update. There are enough people reporting it that it seems like there is an issue for some users, but obviously not everyone is seeing it.

There have been some suggestions posted, but while they worked for some they did not work for all. Are you seeing this strange behavior? Did it start with 10.6.1? Let us know, and hopefully Apple will kick the code for the next update and put this bad boy to rest.

Thanks to Mark for the tip.

In the last week, we have had a constant barrage of iPhone issues break through the lines... so much so that we feel it is our duty to inform the two of you who haven't updated what you could experience by updating to version 3.1 of the iPhone OS. This is no small problem, as you can read from the discussions on Apple's website here, here, here, and here.

The first two links are where we're getting the majority of our tips -- random shutdowns and very poor battery life. The second two, bricked phones and general slowness are still worth a mention -- even prompting our own Erica Sadun to do a live walk-through for debrickifying iPhones. We received a lot of praise for her help in that session and we'd encourage you to go back and read through the chat if you're experiencing trouble with a bricked iPhone.

I've spent quite some time reading the hundreds of posts about the "mysterious random shutdowns" and have determined that it really is what it is. As of this writing, there have been 409 posts and 28 pages in that discussion -- I've seen very little repeats and no real solutions. Some people have said that they've gone to Apple and received replacement phones because of this issue but for those of us who have out-of-warranty phones, Apple has merely said "It's $199 for a replacement." I have to agree with our tipsters -- this needs to be addressed. These people simply did not break their phones, it's a well-documented issue which we, as consumers, shouldn't have to pay to fix.

Battery life is a completely different debacle. I cannot seem to find a trend in the discussions at all. Some people claim to have removed certain apps, some claim that MobileMe sync is the culprit -- all of them agree that there is an issue with 3.1 and that battery life shouldn't dramatically decrease overnight. I'd really love to get into one of these phones and replace the battery to see what happens because the hardware guy in me says that it's not impossible. However, deductive reasoning says that there's something in the software. Whether there's a memory leak in 3.1 itself, or some apps that we're running aren't as "compatible" as they should be... we need to see another update soon to help alleviate the issues with version 3.1 of the iPhone OS.

Please feel free to use our comment system to express your concern, anger, resentment... whatever. Try to be helpful if you've come across a solution and be nice if you're not having these problems. Until Apple issues a fix or acknowledges the problem at all, just hope that you're still in-warranty.

In between watching those Sunday NFL games, we're hoping that you're snacking on some TUAW goodness. For your munching pleasure I thought I'd cook up some of the interesting tidbits that have accumulated in our inbox this morning and present them to you for consumption.

First, from TUAW reader Tom, is a fascinating look at a pre-Apple "Apple logo." Apparently in 1969, Piaggio Vespa, world-famous for their Vespa scooters, had an Italian ad campaign featuring apples with both sides missing a bite. The campaign used the Italian phrase "Chi Vespa mangia le mele," or "He who Vespas eats apples." Echoes of the campaign can still be found on various Vespa websites, including the USA site where you'll find many dingbats and buttons are apples with a bite or two taken out of them.
Next, TUAW fan Keith pointed out something interesting. If you go into Settings > General > Usage, there's a list of your iPhone usage. Down near the bottom of the list of statistics is a section called Tethering Data.
This shows up on 3G / 3GS models, since tethering is allowed by many carriers. Of course, as "Seth the Blogger Guy" notes in the AT&T video, American iPhone owners don't get the joy of using their iPhones as wireless data modems for laptops because the AT&T network has insufficient capacity. We've talked previously about AT&T's view on tethering; read here for more info. Of course, there's always the jailbreak option. Read on for more news tidbits.

There are quite a lot of posts on the Apple support forums discussing whether nor not the upgrade to iPhone OS 3.0 and later releases has trashed the GPS functionality of the device.

At last count there were 24 pages, a high percentage from users in Europe who claim that moving to 3.0 eliminated GPS functions, and all they get is Wi-Fi geolocation or cellular network triangulation.

As often happens, the passion devolves to nasty comments going back and forth, but clearly, some people are having a GPS problem which Apple is not acknowledging as a bug. They are giving some people new phones, but others aren't getting them because their iPhones are out of warranty.

Here's a typical comment from one poster:

"I could not get a satellite GPS (blinking blue dot) on my iPhone, while two other phones running 3.0 like me, got it within seconds. So I returned my unit, and got it replaced. The new phone got a correct GPS signal at once and according to MotionX GPS it was correct within 8 meters.

This leads me to the conclusion that OS 3.0 makes GPS not work on some iPhones (not all). Replacing the unit was the only solution for me, and it worked.

I recommend it to anyone who never (or almost never) get a GPS satellite signal."

Some are blaming their cell service provider, others are blaming Apple. Others are saying it was fixed by the recent version 3.1 update. Of course, with any new hardware/software there are problems, and with millions sold, a lot of reports will surface. What's odd here is that some people are solving it with resets, some with new phones, others with turning 3G off. There just doesn't seem to be any consistency in the solutions, which is probably driving Apple crazy.

Hope these folks get this problem sorted out, and Apple dives in and finds a solutions, or more likely, solutions.

Thanks to Torstein in Norway for the tip

We received a tip from a frustrated reader this morning noting that when he published a calendar to MobileMe with iCal, it wasn't showing up if there were any all-day events in the calendar.

I sorted through a few different examples and was able to verify that any calendar with 'all-day' events just doesn't publish. Of course, you'll end up with a URL, but it will go to Apple's default 404 page for Mobile Me. A quick browse through the Apple support discussions will tell you that it's not an isolated incident... the thread can be found here.

We're being told that Apple is currently working on a fix for this problem, but we thought it would be a valuable heads-up for our readers. If you have to publish to MobileMe, we'd suggest removing 'all-day' events from your calendars (or changing them to fixed-duration events) until Apple fixes this issue.

Thanks, Bob!

Ahhh, Labor Day - the weird U.S. holiday that celebrates work by encouraging people to take the day off. Since it also coincides with the beginning of September, many Americans associate Labor Day with the end of summer, which isn't until 3:18 PM on September 22nd. Since the colder temperatures of the Northern Hemisphere will soon mean no more picnics, it's a great day to get out and have one more al fresco meal.

Like a picnic, where a good time can be spoiled by a group of aggressive little ants, my first ten days of Mac OS X 10.6 Snow Leopard have been a lot of fun, interspersed with some tiny, nagging annoyances:

• Preview, an app I use constantly to resize screenshots for TUAW, crashes way too frequently
• Without having changed any preferences, the OWC Mercury Elite Pro 1 TB drive I have attached to my iMac now spins down between Time Machine backups (this actually saves power, so I'm not complaining -- I just find it strange that it didn't happen before!)
• An unexplained kernel panic the other morning when I woke up my MacBook Air by opening the "lid"
• Having to reset the synchronization between my two Macs, MobileMe, and my iPhone after duplicate calendar entries began to multiply
• Occasionally having to physically remove and plug back in the USB receiver for the Logitech wireless mouse on my iMac when the mouse refuses to work upon waking up from sleep
• Exports from iMovie '09 to YouTube aren't working properly for me

There are no real show-stoppers here, just those little oddities that have kept life with Snow Leopard from being pure bliss. What are the ants that are showing up at your Snow Leopard picnic? Leave a comment below.

It's not that we have anything against the Flash plugin for Mac browsers. Well, other than the fact that it's crashy, and slow, and makes our laptop fans spin up like we're doing wind tunnel testing for the Air Force. But other than that, we have nothing against it -- and it's lovely that the new 64-bit version of Safari in Snow Leopard can isolate Flash-related stalls and hiccups from the main browser process for enhanced crash protection. Very nice.

Unfortunately, as pointed out initially by Graham Cluley over at the security and anti-virus vendor Sophos, the version of the Flash plugin that Apple bundles with Snow Leopard is old. It's the 10.0.23.1 version, old enough that it has some notable vulnerabilities versus the currently shipping 10.0.32.18 version. You can check which version of the plugin you have by visiting this Adobe check page. Even if you had the current build on your machine before upgrading to Snow Leopard, the upgrade process replaces your Flash with the vintage Flash instead -- poor form! Cluley recommends, and Adobe concurs, that the best thing to do is head over to Adobe's download site and get the most up-to-date version instead.

It's understandable that Apple had to lock down a version of the Flash plugin for inclusion in the OS golden master, but if you're gonna do that then you've got to provide an integrated method for users to update to the current build when the time comes (like, say, via an OS-wide Software Update utility). Downgrading user security while upgrading OS versions is a rotten way to run a railroad.

[Side note, does Cluley's narration in the video above make you wonder if, just maybe, he's moonlighting as Ben 'Yahtzee' Croshaw over at The Escapist? NSFW!]

Thanks to everyone who sent this in.

Here's an interesting feature of Snow Leopard that you may or may not (probably not) find particularly useful. Apparently after upgrading to 10.6 several users at the Apple Discussion Forums -- mostly owners of Mac mini or MacBook models with the GMA950 graphics subsystem -- are reporting poor performance with Front Row.

The performance issue seems to effect navigation as well as playback, resulting in jerky video/audio in the menu and when watching a movie. This is also not limited to pesky DiVx files or QuickTime plug-ins either, as some users are reporting seeing the problem with iTunes purchases and others are even running a completely stock installation. Interestingly enough, some of the same users with Front Row issues are not seeing the same problems when playing back with QuickTime X.

In my opinion, this is not much of a surprise following such a major upgrade to many of the OS's underpinnings -- including an overhaul to QuickTime on which Front Row is largely based. This is the reason I did not upgrade the Mac mini in my living room. Aside from being a full-time webserver, I also rely on it for multimedia functionality as well.

Some folks with complaints have found solace in either Plex or Boxee as these fine media players do not rely on QuickTime or iTunes. For most though, a working Front Row would be ideal. Personally, I have not checked for problems with Front Row since my multimedia Mac hasn't been upgraded. However, I did note some wonkiness on another machine when using QuickLook to playback some video files through Finder. I have a sneaking suspicion there is something going on related to QuickTime X being used by other programs (i.e. FrontRow or QuickLook). What say you dear readers? Is your Front Row experience causing you grief or are you simply smirking because you haven't received your pre-order upgraded yet?

Thanks to Ivey for sending this in via Twitter.

Users of the MozyHome and MozyPro online backup services who also use Apple's Time Machine and a Time Capsule for onsite backups were dismayed to find last week that their Time Machine backups were not working. A bug in version 1.4.1 of the Mozy software caused Time Machine backups to Time Capsules and other network drives to pause, and then freeze up.

A user quoted on the Computerworld website last week noted that Time Machine would no longer mount his MacBook Pro's sparse bundle file while running Mozy offsite backups, and that he had to wipe the Time Machine backup in order to get the Time Machine / Time Capsule combination working again. The problem did not affect Mozy users who were backing up to a locally attached hard drive. Part of the issue was that Mozy was attempting to back up the large Time Machine sparse bundle files.

Engineers at Mozy's parent company, Decho, worked with Apple to gain resolution to the issue, and a fix was made available for download last Friday as version 1.4.3 of the Mac software for MozyHome and MozyPro.

[via Macworld and Computerworld]

Maybe it's already Saturday in the UK, or close to it: Apple has released iPhone OS 3.0.1 for iPhone, iPhone 3G & 3GS, an update that patches the phone to prevent bad actors from taking it over or taking it down with the just-demoed SMS exploit. The update weighs in at close to 300 MBabout 230 MB (like all iPhone updates, it's a full image of the OS), and as far as we can tell there are no other fixes or tweaks; just the privilege of continuing to use your iPhone in peace and security.

Update with care, and let us know in the comments how the update works for you!

14:30 ET: Apple's security mailing list just delivered the notes for 3.0.1, they are reproduced in the 2nd half of this post. Also worth noting that the SMS exploit is not endemic to the iPhone alone; both Android and Windows Mobile platforms can be attacked with similar techniques, although Google tells BW that the issue on Android phones is now fixed (presumably through carrier action on T-Mobile's side, not confirmed though).

Update 7/22: AOL has responded to the reports of misdirected push notifications, and has confirmed that the issue is due to the use of a workaround for push notifications on unlocked phones.

--

If you want to have a hot and steamy exchange with your sweetheart via AIM on the iPhone, you might want to think again -- if you have an unlocked or jailbroken phone.

CrunchGear reports that Till Schadde with Equinux has discovered an iPhone bug where AIM messages could be sent to random people without you even knowing it. Schadde discovered this when he was notified that a message he had sent to his iPhone version of AIM got intercepted by someone else. That person proceeded to contact Schaddle, sharing the screenshot shown at right with him. Schadde posted the screenshot and detailed the bug on Twitter after testing it once more from his computer.

The bug is being blamed on iPhone 3.0's push notification and seems to be limited to unlocked/jailbroken iPhones at the moment.

Edit (12:20 PT): Schadde has tweeted that he was contacted by AOL via phone this morning, and they are currently investigating the issue.

[Via CrunchGear]

A number of iPhone 3GS owners have reported slow and inconsistent data speeds, along with widely varying amounts of signal strength, when using Wi-Fi.

Users note that signal strength can fluctuate between one and full bars even when standing right next to the router or when a computer nearby shows a constant signal. This goes along with a commensurate reduction in speed. Even at full signal on both the computer and the 3GS, one user reports getting a maximum of 3Mbit downloads on the iPhone while getting nearly 7Mbit downloads on a MacBook using the O2 network. The fluctuating signal strength problem has affected me since I brought home my new iPhone 3GS.

The other, more widely reported problem is a sizable speed decrease in the iPhone 3GS as compared to the iPod touch and iPhone 3G tested under the same conditions. In one case an iPod touch garnered download speeds of 4579ms and uploads of 1363ms, while the iPhone 3GS showed only 1360ms down and 160ms up.

"My iPhone's been draining awfully fast since I installed 3.0," I commented to a fellow TUAW blogger just a few days after the release of the iPhone 3.0 firmware. At first, I wanted to think it was my phone. But, my iPhone 3G wasn't even 90 days old at the time of the observation and I'd been able to keep it on standby for several days before it needed a charge. Now, I could barely make it through a 10-hour workday before rushing out to the car to hook it up to a power source.

Aaron Vronko of RapidRepair says that this isn't an isolated incident. The iPhone 3G may now deplete its energy supply in roughly two hours, and the first generation iPhone lasts less than a day. Vronko tells Macworld that the cause is most likely push notification placing a drain on the battery's reserves. The issue has also led to complaints on Apple's support forums.

I've definitely noticed the difference. If I leave myself logged into BeeJive IM while I'm at work, my phone drains much faster than it does if I'm logged out. Regular push mail notification from MobileMe doesn't affect the battery level all that much, even with the high volume of e-mail I receive through TUAW. So, to save on the battery for now, I'm avoiding the push applications as much as I can if I don't have a charger within reach.

Vronko believes that the 3.1 release will solve the battery issues.

[Via MacNN]

I didn't really take last week's Twitocalypse that seriously, but as you probably know by now, it turned out a little worse than expected -- we'd been told that Twitterrific (and, we assumed, most other Twitter apps) would be fine, and of course, as Craig Hockenberry explains on his blog, things ended up not-so-fine. Desktop app developers, of course, could publish updates as quickly as they could code them; iPhone developers were in a different situation.

When the Iconfactory's app stopped working, most people (including me) got an API error all weekend. Craig found the bug, then he and his team were able to leverage their contacts at Apple Developer Relations to help expedite the release; in short order, an update was pushed out to the App Store. I downloaded it yesterday, and can tell you that things are fixed... at least until the numerical limit on Twitter's tweet identifier raises its head again (or the Newton flips out, but that's another story).

Hockenberry also has ideas about how to keep issues like this from happening again. Not the actual issue of a variable overflow (that will undoubtedly happen again at some point, on Twitter or any other API that scales way faster than anyone expects it to), but the issue of iPhone apps needing a quick fix. He says that Apple should give every developer a number of "incidents" -- situations rarely used, in which a high priority fix can get sent out to apps in major emergencies. He says, and it's true, that for most developers, it's not a question of if you'll need to send out a critical fix, it's a matter of when. And support by Apple, obviously limited to one or two instances per developer, would help developers, distributors, and consumers.

Of course, it's up to Apple, and it's not like they've smoothed out the approval process so well already that they can start adding wrinkles to it. But clearly, given that the Twitterrific update went through quickly, there's room for exceptions to be made.

[via DF]