Rogers Wireless has a little over one week left of its Canadian iPhone exclusivity. Wireless carrier Telus announced today that it'll start sales of the iPhone 3G and iPhone 3GS on Thursday, November 5, 2009.

While the Telus network has been CDMA-only, the carrier is not selling a modified phone. Rather, the company is launching its iPhone-compatible HSPA network, which it's marketing to consumers as 3G+.

Prices on the new network match what many expected from Bell, which is also starting Canadian iPhone sales soon. Telus will sell an 8GB iPhone 3G for $99 (Cdn$), a 16GB iPhone 3GS for $199.99, or a 32GB iPhone 3GS for $299.99 with three-year contracts. Minus the monthly plans the 8GB iPhone 3G will run buyers $599.99, the 16GB iPhone 3GS will run $699.99, and the 32GB iPhone 3GS will run buyers $799.99.

[via Telus]

Update: As of this writing, Total Apps reports that it's back in the UK App Store. We still don't see it in the US store.

That sure didn't last long. Just shortly after the discovery of a 3G "backdoor" for the EyeTV app, it has been pulled from the App Store.

The workaround let users of the app stream video over a 3G or other cellular network connection, something that AT&T has objected to in the past. Specifically, users can connect to ElGato's My EyeTV service to schedule and stream recordings.

When users try to stream video outside of a Wi-Fi connection, a dialog box appears saying that a Wi-Fi network is required, but streams the video anyway. Elgato says they have just submitted an update to Apple, after Apple removed it from the App Store, removing "test code" that allowed this streaming:

"Some test code that enabled live TV streaming over the cellular network was accidentally left in the the EyeTV App. Apple requested that we remove the code since their agreement with AT&T does not allow redirecting TV signals over the cellular network. The code was removed and a 1.0.1 version of the EyeTV app was submitted," they told TotalApps.

This app rejection is similar to the removal of the Commodore 64 app, that was pulled after hidden access to a BASIC interpreter was discovered. This removal adds just more trouble and frustration to users and developers, especially because of the current state of the Google Voice app.

[Via Total Apps]

When I opened my iPhone 3GS, I was surprised to find that the power adapter was nothing but a little 2-prong AC plug (I live in the US) that allowed you to plug in the standard USB to 30-pin connector to charge the phone.

I wanted to get a spare; checking online told me that the Apple Store wanted US$29 for the little plug, which just seemed like too much for too little, so I went shopping.

On eBay I found a bunch of auctions based in Hong Kong selling what looked like the exact same thing for anywhere from under around $2-4, and they often included the USB cable to boot.

I ordered four from a vendor and after a few weeks received them. They looked perfect, right down to the little green dot -- but none of them worked. They might start charging, but after a few minutes the iPhone would beep a few times and I would be informed that "this accessory is not compatible." And so it went for all four pieces. After sending some pictures back and forth and reading a few emails containing a combination of surprise and amazement from the vendor, my money was refunded.

Undaunted, or maybe just dumb, I went back to eBay and found another vendor that claimed to be selling, "100% Brand New Original OEM Charger and Original OEM USB Cable for iPhone/iPod" for around US$4. I just checked eBay and found this same vendor raising the price to US$10 in one auction and lowering it to $US.01 in another.

The iPhone was slow to launch in Canada and after a rocky start, Rogers has been the exclusive carrier. That changed this week when Bell and Telus both announced independent deals with Apple. Starting in November, each will carry the 3G an 3GS. Just in time for holiday shopping!

Keen customers know that both Bell and Telus are CDMA-only right now. However, they've both pledged to deploy compatible HSPA networks that will serve as an inroad to 4G.

Neither company has released details like pricing, plans, etc., but Telus has set up a web page for interested customers.

After the debacle earlier this year when I lost my iPhone 3G, I decided to not only protect the new phone -- my lost 3G had been "naked" -- but make sure that whatever I used to protect it had a bit of heft.

My choice of case was the locally-grown (Fort Collins, CO) OtterBox Defender, which fit the bill perfectly. It has what OtterBox refers to as a 3-layer design, including a thick screen protector, a hard shell that encloses the iPhone, and a rubberized exterior jacket that cushions shocks and keeps ports covered. While it has been an awesome case in terms of protection, it's pretty chunky and I've often wished I had something a bit skinnier.

OtterBox came to the rescue last week with a new line of protective cases called the Commuter. There are two models -- the Commuter (US$34.95) and Commuter TL (US$29.95). Like the Defender, these cases work with both the iPhone 3G and 3GS. Read on to hear more about the OtterBox Commuter cases, and a chance to win either a Commuter or Commuter TL case from TUAW and OtterBox.

The legendary Dev-Team has done it again. It just released the new version of the Pwnage Tool, a desktop application that's used to create custom firmware packages to jailbreak iPhones and iPod touches.

Jailbreaking is the act of modifying the official firmware in order to run applications not approved by Apple. Chief among those applications, at least for the iPhone crowd, is the SIM unlock that allows the phone to be used on unofficial cell phone service providers.

The Dev-Team has found holes in previous versions of the iPhone OS that allow this code modification and has developed tools to make exploitation easier for the average user to accomplish. Once implemented, the jailbreak process installs an app that acts an unofficial App Store of sorts. The iPhone or iPod touch user can browse and install games, utilities, themes, and general applications. Cydia, one of these installer apps, even has a store with applications for sale.

Traditionally, when Apple releases a new iPhone OS version, that software upgrade breaks any jailbreak and SIM unlock present on the device. And so, you end up with the cat-and-mouse game that Steve Jobs alluded to shortly after the first firmware loophole was exploited and the original iPhone was unlocked.

Well, the mouse has stolen the cheese once again, and the Pwnage Tool released today will jailbreak the latest firmware, version 3.1.*

The big asterisk at the end of that previous sentence is that the Tool will only work on about half of the devices that use the iPhone OS -- only the original iPhone, original iPod touch, and iPhone 3G. The iPod touch line just released, as well as the 2nd generation iPod touch and the iPhone 3GS, cannot be jailbroken at this time. That means if you've already upgraded to 3.1 on your 3GS, you still won't be able to SIM unlock it as of the time of this post.

So, if you want to SIM unlock your iPhone 3G or the original model, Pwnage Tool 3.1 should do the trick. On the 3G, you'll need to use Icy or Cydia to also install the ultrasn0w app that actually performs the software unlock; however the original iPhone should be unlocked without this additional step.

You will need a Mac to run Pwnage Tool 3.1, but a Windows version is expected in the near future. Also expected soon is redsn0w, for both Mac and Windows, that further simplifies the jailbreak process by avoiding the need to create a custom firmware package.

Keep in mind, if you've been waiting for a jailbreak solution before upgrading to the latest firmware, many users have had fairly substantial issues with iPhone 3.1. My fellow TUAW blogger, Josh Carr, has reported that lots of iPhones and iPod touches are working poorly after upgrading. You may wish to hold off and stick with 3.0 or 3.0.1 until a solution is found, either by Apple or some other group of smart people.

But, if you're so inclined, you may find links to download Pwnage Tool 3.1 on the Dev-Team's official blog. Make sure to read the instructions thoroughly, and take heed of all of the warnings. They are there for a reason.

The Apple Support forums are a'buzz with reports of several users upgrading to iPhone OS 3.1 and discovering a new "feature" which was not available previously. As mentioned in our comments, after upgrading to 3.1, some original iPhone and iPhone 3G owners with Exchange accounts are having trouble accessing their email. Apparently the server-side encryption policy option for mobile devices (only available as of Exchange 2007 SP1) is now being appropriately enforced.

This is not affecting owners of the iPhone 3GS, due to the newer device's support for Exchange encryption. Prior to iPhone OS 3.1 the encryption policy was ignored for all models. Now that 3.1 is available, users are seeing this policy being correctly enforced and older iPhones without encryption support are left without access to Exchange services.

I have yet to find any reports of issues with the iPod touch, but I suspect that it will also be affected by this software change. We're awaiting confirmation from Apple on whether this will impact the newly announced iPod touch models as well.

While many are reacting to this issue as though it's a bug, and are reporting it as such, the reality is that the Exchange encryption requirement is a feature and the fact that it was not being correctly enforced was actually a security hole. IT administrators with Exchange 2007 SP1 servers and iPhone clients are probably going to be fielding an above-average level of incoming questions, but at least they can rest easy knowing that Exchange encryption is now working correctly. Cold comfort for their users, though.

If you are running into this issue, the straightforward (though pricey) solution is to upgrade to the iPhone 3GS; or consider bribing your IT guy with Red Bull so he will disable the encryption requirement for mobile devices. But we want to hear from you; are you using an Exchange account? Can you still access it following the upgrade to 3.1? Which device are you using, iPhone or iPod touch; 3G or 3GS? Is this a little thing that means a lot to you from a security perspective or have you been left high and dry without access to critical email?

Update: MacRumors points out that Apple has now covered this situation in a new KB article.

[Via Broadband Reports]

One of the first surprises out of today's Apple event, other than Steve Jobs appearing on stage again (!!!), was the announcement that iPhone OS 3.1 and iPod touch OS 3.1.1 were available. We're still waiting for the download to complete, so this won't be a hands-on review, but we do want you to know what the new features of 3.1 are:

• Improved syncing for music, movies, TV shows, podcasts, and photos
• iTunes U content organization
• Redeem iTunes Gift Cards, codes, and certificates in the App Store
• Display available iTunes account credits in the App Store and iTunes Store
• Save video from Mail and MMS into Camera Roll
• Option to Save as new clip when trimming a video on iPhone 3GS
• Better iPhone 3G Wi-Fi performance when Bluetooth is turned on
• Remotely lock iPhone with passcode via MobileMe
• Use Voice COntrol on iPhone 3GS with Bluetooth headsets
• Paste phone numbers into the keypad
• Option to use Home button to turn on accessibility features on iPhone 3GS
• Warn when visiting fraudulent websites in Safari (anti-phishing)
• Improved Exchange calendar syncing and invitation handling
• Fixes issue that cause some app icons to display incorrectly

There's now also a App Store Genius function, which will recommend Apps based on your purchase history. The Genius of Apple also extends to iTunes, which will now create up to 12 playlists for you based on what's in your library. You can now purchase and download ringtones from your iPhone, and organize apps in iTunes.

Apple's security info page will be listing the security content of the OS updates shortly. The new versions include 10 security fixes, including patches for SMS vulnerabilities, Exchange passcode lock workarounds, and Unicode character spoofing flaws.

We'll have a hands-on review later!

It appears that China Unicom has been selected as the sole distributor of iPhones in China, according to a report in the International Business Times today. While the deal has yet to be finalized, the company has purchased 5 million WCDMA iPhones without Wi-Fi from Apple at a price of 10 billion yuan (US$1.46 billion).

China Unicom is to begin selling the 3G phones in September at company stalls in Carrefour stores, as well as at several large China Unicom retail outlets. The phones are expected to sell for 2,400 yuan (US$352 as of this writing) for an 8GB model and 4,800 yuan (US$704) for a 16GB iPhone. It's estimated that Apple's profit from each sale is about 1,100 yuan (US$161).

China Unicom faces stiff competition from black market iPhones, which are selling for as low as 400 yuan ($59). The International Business Times report notes that Apple made large concessions to China Unicom in order to enter the massive Chinese market. To give some scale to the size of this sale, Apple reported during the 3Q 2009 conference call with Wall Street analysts that they had sold a total of 5.2 million iPhones in the last quarter.

While I love the functionality of Apple's microphone-enabled headphones (both the Apple Earphones with Remote and Mic, which comes with the iPhone 3G S, and the iPhone Stereo Headset, which came with previous iPhones), I've found that the extra layers of functionality also bring extra layers of troubleshooting when they're not working right. For simplicity sake, I'll refer to said models as "iPhone headphones" in this post (non-volume control model pictured).

The most common issues I've come across pertain to the microphone. Unlike most non-microphone enabled headphones, which use a standard two-ring TRS connector (tip, ring, sleeve), the iPhone adds an extra ring to support microphone functionality. This is what the hardcore audiophile refers to as TRRS (tip, ring, ring, sleeve).

But if your pockets are consistently filled with lint and dust (or tater tots if you happen to store them there), that extra ring won't make full contact with the iPhone's headphone jack. Which means that you, unfortunately, will lose microphone functionality.

One way to fix this is to remove any dust or lint trappings in the phone's jack. I've found that wrapping a toothpick with a thin layer of toilet paper and brushing it lightly against the walls of the headphone jack helps out a great deal. It's also important to not dip said toothpick in water or moisture. There's a moisture sensor in the iPhone's headphone jack. When exposed to moisture, it changes color and could potentially void your warranty. Also, the usual disclaimer in do-it-yourself scenarios apply: you're doing this at your own risk, so proceed with caution.

Sometimes, when I see something new, I have to smack myself in the head and think: "Why didn't I think of that?" Remember the old V8 Juice commercials? I just heard about one of these and It's the X-Power1 USB Rechargeable Battery Backup Cable from Xmultiple.

It looks like a USB charging cable swallowed a AA battery. What's inside is a lithium-ion battery with more capacity than built into any current iPhone or iPod. Using this cable, sync or charge your device while the internal cable battery charges. It will take about 3 hours to fully charge. Then when your device runs out of juice, plug in the cable and get power while you charge your device's battery.

I spoke with Alan Pocrass, the CEO of Xmultiple, and found that the information now circulating around the Internet is wrong. If you've already read something about the product, that information was based on a production prototype that will not be be built. The publicity picture is also inaccurate. The cable will work with iPhones, iPod touches and USB-charging iPods only, so earlier iPod owners (those that charge via Firewire) are out of luck.

Keep reading for more specifications...

More coverage of the ongoing Wi-Fi struggles of iPhone 3.0 users: In a discussion comment, Liam noted that he got full bars but no Internet using his iPhone 3GS until he turned off Bluetooth. After reading that, I wondered if Bluetooth is another suspect in the widening catalog of speed and signal problems reported with the iPhone 3GS and the iPhone 3G / iPod touch combination.

I ran the DSLReport speed test on my iPhone 3GS and found that with Wi-Fi and Bluetooth both enabled, latency increased a bit, and download speed decreased by over a third when compared to running the test with Bluetooth disabled. Upload speed didn't seem to be affected.

A possible reason was proposed by Doug Hogg of Toy Kite Software, creators of the Bluetooth-enabled two person game iSamurai: Real Life Sword Fight. Doug discovered problems in playing the game after updating to iPhone 3.0 software, but found that turning off either Bluetooth or Wi-Fi solved everything. It seems that both Bluetooth and Wi-Fi share the same antenna, so when Bluetooth was made active in the 3.0 software, conflicts arose.

On the Toy Kite Software site, Doug was a bit more specific. The iPhone 3.0 software brought with it a service discovery process that switches between looking for another device on Wi-Fi and Bluetooth using the single antenna. While searching, problems can occur with already established connections that can cause lags and loss of data packets sent between devices. Apple is working with Toy Kite Software to correct all this, but I wonder how much speed and even signal strength loss can be regained by turning off Bluetooth when it's not being used. In my case the difference was substantial.

It's also interesting to note that the iPhone 3GS uses a combination Wi-Fi / Bluetooth Broadcom chip that handles 802.11a/b/g as well as Bluetooth 2.1. Previously separate Wi-Fi and Bluetooth chips were used.

If you are having any speed or signal problems, try turning off Bluetooth and see what happens. I don't think that this will solve everything, but until Apple gets its act together on fixing all of this, what we're left with is a rag-tag assortment of tricks that may or may not help.

Let us know if this one works for you.

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.....

Wi-Fi connectivity problems are not limited to the iPhone 3GS, not by a long shot. The iPhone 3G is widely reported to have connectivity problems that, according to the large number of people discussing it on the Apple Support Discussions, dwarf the reports regarding the 3GS.

In over fourteen Apple Discussion threads, over six hundred messages have been posted with the first one being written on June 17th, shortly after the release of iPhone 3.0 software. These threads have been read by thousands of users. Unfortunately, to date, a solution is not at hand.

The problem, verified by many, is that when updating to the new software, Wi-Fi connectivity on the iPhone 3G either decreased or vanished entirely. Those who were used to getting full bars of Wi-Fi connectivity now experience markedly less bars. Worse, even if some signal strength bars are displayed, often there is no Internet connectivity.

Many solutions have been proposed including resetting the router, changing settings (seemingly at random), and even putting the 3G in the freezer:

"Also i might note, I turned off wifi, turned off the phone, put it in the freezer (in a bag) for 10 mins, turned the phone back on, put the phone right next to my wifi antenna and then turned on wifi and it joined, it JUST joined and I couldnt believe it," says one forum poster. Several others report similar results, but this fix did not last long. In fact, blog posts have been written about possible solutions, but none of them seemed to pan out after using Wi-Fi for a short period of time.

Some writers have said that the 3.1 update will fix the problem while a larger number say that the new software release won't help at all.