Last night I was grabbing screenshots with my iPhone that I'll use in a forthcoming post. After snapping 4 or 5, I launched the camera app to look at them. I saw the preview thumbnail but when I clicked Camera Roll for a larger view, it appeared empty.

I restarted the iPhone to no avail. I connected it to my Mac, and iPhoto imported the screenshots without a problem. After a sync they were in my iPhone's photo album, but I still couldn't see subsequent photos taken with the built-in camera.

After some searching I found this thread on Apple's Discussion Board that describes my issue. It seems that the iPhone fails to display photos taken beyond number 10,000.* That's right, I've taken 10,000 photos with my iPhone. Or have I?

The iPhone in question is a 3GS that I purchased not too long ago. There's no way I've shot that many pictures in such a brief time. However, I did buy an original 4GB phone back on opening day. As I set up the 3GS, I did a restore from backup. Guess what came with it? The "counter" for all photos I snapped back then. The 3GS picked up where the original model left off. D'oh.

I'm glad to say that I've restored the Camera Roll's functionality. Here's how. I connected my iPhone to my Mac and launched PhoneView. From there, I clicked Settings and selected Show Entire Disk. Be careful here, because this lets you fiddle with typically hidden folders and files.

Inside the DCIM folder I found a number of folders with names like "100APPLE," which I deleted (AFTER syncing my iPhone with iPhoto and grabbing all stored pictures). Then I quit PhoneView, restarted the iPhone or good measure and presto! I was back in business.

I'm not the only one with this problem and I hope Apple addresses it in a future update. Note that you can get this done with the free trial of PhoneView, but it's a great app and only $20, so buy it as a thank you.

*Remember, this refers to number of photos shot with the iPhone, not number of photos stored.

What do you get when you combine a new parent on maternity leave with a love of gadgets and Apple products? Why, you get "baby monitor overkill!"

In response to Dave Caolo's recent ode to the Mac mini, I figured it was time to step up. I had two things gathering dust: my old standalone iSight, a gorgeous example of Apple design sadly idle since the advent of built-in iSights, and a lovely new Intel Mac Mini that was recently scored on sale at MicroCenter with plans to set it up for my older two kids once I could get my hands on a small LCD monitor.

I figured in the meantime it would serve nicely as a baby monitor, since I couldn't find a matching transmitter/receiver pair among the various baby monitors I had accumulated over the years. My idea was that it would live discreetly, headless and tailless (monitor, keyboard, and mouse-free) in the baby's room, and broadcast both locally on my network and also wide-area so grandparents could tune in remotely.

For the initial setup, I needed a monitor, but fortunately my TV has a PC (VGA) port, which I used to configure the mini. I set it to login automatically to the main account and join my Airport network. In System Preferences, I enabled screen sharing and added iChat as a login item. In iChat, I enabled Bonjour and instant messaging, added myself as a buddy, and restricted chats to preapproved users under security preferences. Because I didn't want to connect via screen sharing every time I wanted to initiate a chat, I typed the following into Terminal so that it would auto-accept any incoming video chats:

defaults write com.apple.ichat AutoAcceptVCInvitations 1

After that, I set it adrift on the network. From my main computer, I watched the mini pop up on Bonjour after reboot, and we were off and running.

While this worked great for my own local use, it had some inherent restrictions: remote users (aka "grandparents who love to watch sleeping grandsons") couldn't join the chat easily. Spouses at work had issues with company restrictions on AIM. Plus, it was iPhone-unfriendly; the holy grail for me was turning the iPhone into a video terminal that followed me around.

I went through a few different ideas: private channel on Justin.tv (great for multiple viewers, but awash in advertising, restricted at work, and unavailable on iPhone), Skype (great video, automatic call acceptance and limited iPhone capabilities, but terrible for multiple viewers), and complicated setups involving QuickTime Broadcaster. Not wanting to reinvent the wheel (well, no more than I already was doing), I hit upon SJKM's iCam software, which is an iPhone application & accompanying cross-platform video streaming tool specifically designed for video monitoring, available in the iTunes store for $4.99. Initially dismissed for lack of audio, it has since enabled audio monitoring and non-iPhone web access, making it an almost perfect setup. Why "almost?" Well, for reasons I cannot quite figure out, the video is much choppier than AIM, Bonjour, Justin.tv, or Skype. But it works over 3G and Wi-Fi, and it connects multiple viewers without requiring conference setup.

And now, with SJKM's latest update, iCam can run in the background and push notification will alert me to sound or video motion. I have not yet enabled that feature, as it is a $.99 add-on and still pending Apple approval in the store.

Ultimately, I ended up using a variety of different applications, but I can report a lot of very satisfied relatives dreamily cooing at the computer screens from Portland, OR, to Philadelphia, PA. All thanks to the mac mini and the standalone iSight. And one very cute baby (if I do say so myself.)

Upcoming: that's great, but can you make it work in the dark? Adventures in IR.....

If you've seen a string of notifications pop up on your screen and then gracefully fade away, you've probably seen Growl; it's the open source & popular system-wide framework that allows applications to let you know when something happens. For instance, a Growl notification might appear to inform you of a newly-arrived email, new mentions on Twitter, a change of song in iTunes, or a download completing in Safari or Transmission.

The notification itself is a customizable pop-up that can also include an auditory notification as well. Growl is very flexible; it allows you to choose exactly which events trigger a notice, or pick a particular notification style for a specific event. Growl includes support for hundreds of OS X applications and is one of the first items I install on a new system.

Probably the only feature that could make Growl even more awesome is if it were to support forwarding notifications to an iPhone or iPod Touch running 3.0 via the new Push framework. Enter iPhone application Prowl (iTunes link), it is a Growl client for the iPhone that sends your Mac's Growl notifications out to your iPhone. Read on for my experiences and thoughts on the first Growl application for the iPhone.

Note: AOL Instant Messenger is a product from AOL, which is also the corporate parent of TUAW & Weblogs Inc.

TUAW reader Jim Carroll is worried: "It is crunch time for your site," he warned ominously in an email yesterday.

Jim is worried that security updates made available via the iPhone OS 3.0 updates last week will only be available to iPod touch users through the obligatory $10 upgrade. "Please use your power as an Apple site to raise the issue." Please, Jim. We're blushing.

"As a long time computer user I am unaware of a similar incident where a company would charge for security updates," he writes. Companies charge money for updates all the time -- operating systems and anti-virus software take time and energy to make, and companies want to get their investment back. Apple has been kind with free updates to Safari, but only because they gain revenue from it via the Search bar.

Apple has always charged iPod touch users for major updates, of course, but security updates have most often come free. 1.0.1, 1.1.2, 1.1.3, 1.1.5, 2.1, and 2.2 all included security fixes, but were free to iPod touch users. (The latter two cases were free for those who bought the 2.0 update.)

1.1.5 is an interesting case. It was released a few days after the 2.0 update, and included security updates that were wrapped into the 2.0 update.

My advice? Have patience. This coming week or next, I have confidence we'll see an update for 2.x (2.2.2 perhaps?) that leaves out the new features, but includes the same security updates found in 3.0 at about $9.95 less.

We're also beginning to hear whispers of a 3.0.1 update for the device to help resolve WiFi issues in the new release; a German iPod user reports being told by an AppleCare representative that an update is expected shortly. Take that with the appropriately sized grain of salt.

Thanks, Jim & Oboewan!

iPod touch users are finally getting a taste of what iPhone users have had since iPhone OS 2.2: Google Street View. iPhone 3.0 Software Update for iPod touch includes an update to the Maps application that enables Google Street View, and it works just like it does on the iPhone.

Additionally, the "Find my iPhone" feature is implemented as "Find my iPod touch" for iPod touch users. It works exactly like Megan described yesterday, but is perhaps less accurate than using the iPhone's built-in GPS. It'll at least get you close, so long as it's connected to a Wi-Fi network. If it is, you can send messages to the iPod touch and wipe its memory.

If you do send a message to an iPod touch that's turned off or not connected to a Wi-Fi network, the message is queued until it's on and connected.

Both features appear to work on both first- and second-generation iPod touch devices. As Megan mentioned, since the first-generation iPod touch lacks a speaker, it won't make the "ping" noise associated with Find my iPhone unless you have speakers plugged in. Perhaps less useful for finding it in the house, but still helpful if you left it on a table at the park.

Have you found an undocumented feature that the iPhone 3.0 Software Update for iPod touch provides? Let us know by tipping us, or leaving a comment.

Thanks, Harold, Ben, Rocky, and everyone who sent this in!

A bit late to the party, I started the process of updating my iPhone at 3:00 PM Eastern. iTunes downloaded the update without a problem, but the install process was halted with the error message:

"The iPhone [your iPhone] cannot be updated at this time because the iPhone activation server is temporarily unavailable. Please try again later."

From there I've got two options: OK, which simply closes the dialog box, and More Information, which points a browser to a Knowledge Base article on iPhone activation issues. Mike also noted the appearance of an error -4 dialog earlier.

It looks to us like Apple's servers are getting slammed hard. A bit of patience ought to do the trick; you might also benefit from restarting both iTunes and your iPhone. Still, the whole thing makes me feel like Veruca Salt: "But I want an Oompa Loompa NOW!"

In my youth, I sold cell phones for Verizon. It was not a rare occurrence to have a customer sign up for a new account and get their free phone, only to come back a week later and tell me they dropped it in a toilet and wanted another one. They were shocked when the phone they got for free just a few days before now cost them close to $200.

To a lesser extent, the same thing is happening with iPhone 3G owners wishing to upgrade to the 3G S for the subsidized price. A year ago, 3G owners bought a $600 cell phone (assuming we're talking about the 8GB model) for just shy of $200. The 2-year contract guarantees that AT&T makes their $400 back over the length of your contract. So far, 3G owners are only about 1 year into their contract, so they've really only paid off about half of their subsidy to AT&T.

Most carriers would stop there, and offer no additional incentives until you've come close to reaching the end of your contract. AT&T is being about as generous as they can be by offering 3G owners half of the subsidy after completing half of their contract. Once 3G owners have fulfilled a year of their contract, they can get the 3G S for the base price ($199) plus half the subsidy ($200) for a grand total of $399.

Read on for some fun cell phone contract math.

With all the fanfare this week surrounding the iPhone, let's not forget the famed handset's red-headed stepchild: the iPod touch.

Hardware updates to the line weren't exactly expected just now. Apple tends to save their iPod updates for special music events held every year since 2003. After Apple's education promo is done and dusted, we can probably expect a special event in September where we see updates for our favorite media device. What's in store for the new iPod touch? Setting aside for the moment rumors about a tablet-sized device, there are sure to be plenty of updates for the handheld iPod touch we've come to know and love.

As far as the operating system update is concerned, we'll gain all the features compatible with the iPod touch's hardware, like copy and paste, upgrades to the iTunes store, and the landscape keyboard. These updates, like those in the past, will come at a price: In an effort to adhere to strict accounting regulations, Apple charges iPod touch users about $10 to upgrade to the new operating system. iPhone users aren't charged similarly, because revenue from the handsets is accounted on a subscription basis, which has different rules about giving updates away for free. Like the iPhone, the update for iPod touch will be available June 17.

Compared to the iPhone, planned updates to the iPod touch's hardware remain largely unknown. iPod touch models have been generally close in specification to the iPhone, but each model is slightly different. In theory, if applications require the greater horsepower the iPhone 3G S provides, some high-performance games may be incompatible with existing iPod touch models, in addition to apps that take advantage of the iPhone's built-in GPS and camera.

Cameras, however, might be on the way: Mike noted rumors last month about iPod nanos with cameras built-in. If those are true, it stands to reason that iPod touch models could get the same functionality. I've opined before about a whispernet service for the iPod touch, but I don't see that happening anytime soon, especially with AT&T's lackluster feature delivery schedule revealed during the iPhone keynote.

What do you think the next iPod touch will be? Will it become "just like the iPhone but without the phone part?" Let us know by leaving a comment.

Yeah, I know we haven't seen it yet, but based on what we do know, here's some things I'll bet Apple missed that I'd like to see ASAP.

• Unified mailbox as an option: This works great in OS X. I sure am getting tired of checking 3 email accounts with hundreds of extra finger swipes every day. Even an icon to get me to any inbox I want to see would be an improvement. Some people don't want this. A simple software switch would be fine.
• Louder speakerphone: I have no idea why this as been such a problem since day 1. The volume of this phone is just not loud enough in a noisy environment. Maybe this is a hardware thing, maybe it's software. Whatever. Just fix this!
• Getting to Bluetooth and location manager: These settings are just buried too deep. How about a switch in the top level of settings? Once again, save me all that tapping.
• Consistency of app settings: Sometimes they appear in settings, sometimes within the app. I shouldn't have to scrounge around trying to guess which app works which way.
• Moving icons around on the desktop: Have you ever tried to organize icons by type, or popularity? Gee whiz, what a nightmare. Maybe this could be done by dragging apps in iTunes, or some easy method on the phone itself would be even better. As it is now, it's like one of those old plastic puzzles where you had to get things in order. Every drag of an icon on the iPhone often has unexpected or at least unwanted results. This is not one of those 'it just works' things on the iPhone.
  

Apple might surprise me and sneak some of this stuff in. Or not. You probably have your own list. Let's hear it. C'mon Apple, we're counting on you to get these things right. For the rest of us.

If you own and iPod touch or an iPhone, you might have bought an app, deleted it for whatever reason and then downloaded it again from the App Store. Since Apple keeps a record of your purchases, you were presented with a dialog box saying that you could re-download that app for free.

According to iPodNN, some developers with preview copies of iPhone OS 3.0 have seen a dialog box (pictured at right) prompting them to either re-download a missing app for free via their computer, or simply buy it again via their iPhones. Who knows why this could be, or if it will even make the final version of iPhone OS 3.0 -- one might think it's to save AT&T bandwidth, but why not restrict the option to WiFi?

In any case, we'll find out soon enough.

iPhone OS 3.0 beta 5 was only released for general consumption yesterday, and already Apple is rocking our collective faces off with big news. While a cool new feature being uncovered would be great, what Apple has in store for would-be iPhone application submitters is a bit more challenging.

Effective today, Apple will no longer be accepting any iPhone or iPod touch applications that are not compatible with iPhone OS 3.0. According to an email sent to developers,

"Beginning today, all submissions to the App Store will be reviewed on the latest beta of iPhone OS 3.0. If your app submission is not compatible with iPhone OS 3.0, it will not be approved."

While this may make sense at first glance, consider that OS 3.0 does not yet have a release date and developers might be pushed to spend time and energy tweaking apps against an unstable OS base. Also, any devs who only ship free apps will now have to pony up $99 to join the beta if they want to debug their apps against the new version.

Further, it seems that Apple might be removing existing applications from the App Store, once iPhone OS 3.0 is released, if it is found that they are not compatible with the new operating system. So grab your Twitter clients and flame-throwers, it's gripin' time!

Update: iPhone Developer Program enrollment is required for App Store application distribution; regardless of whether the application is free or paid, the enrollment fee applies, and any developers with apps in the store have already paid their $99 for access to the beta. Thanks goes to our intrepid commenters for reminding us.

Thanks to everyone who sent this in.

[via @razorianfly & the Loop Blog]

Once again, the folks at DigiTimes have leaked information about a forthcoming Apple product. Citing "Industry sources in Taiwan," they've published an alleged parts list for the next generation iPhone.

Standout items include the 3.2-megapixel CMOS image sensor from OmniVision, which seems in line with the rumored video features in iPhone OS 3.0. Also listed is NAND flash from Samsung and Toshiba and Mobile DDR DRAM from Samsung.

Most interesing is what missing from the list. Namely, the processor. So far, there are no solid rumors on what this could be, so it's really anyone's guess. We think it's safe to say, however, that Apple will release new iPhones this summer. Those who purchased original phones two years ago will have their contracts expire in June, just around the time that iPhone OS 3.0 and WWDC will drop. Here's to this summer!

Thanks to everyone who sent this in.

[via theAppleBlog]

But you knew this, right? Fire up your downloaders, another update from Apple means the digging has already begun for a) new features or updates, b) hints for a new iPhone.

Thanks to everyone who sent this in! I'd like to note that we broke this via our Twitter feed several hours ago. Even if you don't "do" the Twitter dance, it's a good way to catch breaking news.

Earlier today, iPhone OS 3.0 beta 2 was released to developers. The big news is that push notifications and in-app purchasing followed this release, giving developers a chance to try them out. Engadget has reported on significant instability with beta 1, so here's hoping that's been improved.

There's also good and bad news with this release. The good is that MMS and tethering are supported in beta 2. The bad news is that Apple asks developers not use them. It's like owning a Ferrari without wheels.

If you're a developer, you know how to get this. Let us know how it goes, and have fun.