Why would Rogers or Bell care about a new television? Why would Apple involve them? If the rumour is true, then there’s more to this device than just being a television set.

When a customer subscribes to television from one of these companies, they need to get a hardware box that acts as a decoder and often as a PVR. This is an expensive box – several hundred dollars typically – and is usually tied to a contract.

So today, you buy whatever TV you like, and you hook it up to a box that you rented from your service provider.

What if.. Apple’s new TV integrates the provider’s box into the TV.

This would mean you’d be buying a TV that’s locked to Bell, or a TV locked to Rogers, the same as happens for cell phones. This would let the service provider subsidise the TV.

The cost of a TV these days isn’t that much different from the cost of an iPhone. An unlocked iPhone 4S costs $649 in Canada. You can get a 50″ TV set for that kind of money.

If the TV can be locked to the provider and tied to a contract, then they can subsidise it. Walk into a Bell or Rogers store, sign up for a 3 year contract, and pick up a new 50″ TV for $199.

What’s the upside for Apple? It’s hard to say at this point. Perhaps Apple uses the iTunes store model a revenue share with the provider – so you rent a movie for $4.99 and the provider gets 70% of that and Apple keeps 30%. This arrangement would also let the TV provider, which is also typically the ISP, exclude their own streaming media from bandwidth caps, something that’s hindering Netflix today.

The 3 year contract model for the TV would also answer one of the questions people have about why Apple would get into the TV business: How to get users to upgrade more frequently, since people typically buy a TV and keep it for many years. If you could get a new TV every 3 years for $199, wouldn’t you?

I fall firmly on the “the mute switch should really mute the phone” side of the fence, at least optionally.

If I’m in a location where I’m expecting my phone to be silent out of respect for something (like, in a movie, at a live performance, or at a funeral) then even if I have an alarm configured for that time, I don’t want it to go off. It’s going to embarrass me if it goes off. And yes, I even include the “Find My iPhone” sound in the list of sounds I don’t want my phone playing in these situations. There are some times when I want to know that my muted phone really isn’t going to make a sound.

But the difference is I don’t expect the phone to stay that way.

John Gruber mentioned that when he mutes his phone while in a movie, he almost never remembers to unmute it. That’s a common problem, but it’s not a hard one to solve.

There was a feature on an old phone I had, that would let you mute the phone for a period of time. “Mute for 2 hours”, for example. When you think about it, mute is almost always situational. You want your phone muted for a while, and usually you know how long. This would do away with the problem of “I muted my phone for a movie but then I missed my alarm clock the next morning because my phone was still muted”.

Better yet, make the phone muting part of a meeting setting. When I put the appointment in my calendar to go to a movie for 2 hours on Thursday, I’d like to set the phone to mute right there. That way there’s no chance I’ll forget to mute it, and no chance I’ll forget to unmute it.

This seems like an obvious feature but I’ve never seen any phone support it.

Here’s the solution that worked for me.

Edit this file in a text editor:

/Library/Preferences/SystemConfiguration/com.apple.smb.server.plist

You’ll need permissions to edit it. Run your editor using sudo, for example.

Add the following keys:

Don’t forget to edit this to copy the LocalKerberosRealm value into the KerberosRealm value.

Once you’ve done this, save the file, turn SMB sharing off and back on, and you should be able to log in. I’m not convinced this is “the fix” for everybody, but it worked for me.

The winners are:

apple
banana
almonds
avocado
beer
banana
broccoli
blueberries
chicken breast
chicken
coffee
carrots
dates
domino's pizza
dried apricot
dried cranberries
egg
egg whites
edamame
eggplant
fruit
fish
flour
grapes
grapefruit

gin
green beans
honey
hummus
hard boiled egg
ham
ice cream
indian food
iceberg lettuce
italian sausage
jello
jelly beans
jack daniels
jujubes
kiwi
kale
kfc
kraft dinner
lettuce
lasagna
lean ground beef
lentils
milk
mcdonalds
mushrooms

mashed potatoes
nuts
naan
nanaimo bar
nachos
orange
oatmeal
one egg
onion
pizza
popcorn
pumpkin seeds
pomegranate
quinoa
quiznos
quiche
red wine
rice
raspberries
rum
sushi
sweet potato
salmon
sugar
tim hortons

turkey
tomato
tea
udon
unsweetened applesauce
vodka
vegetables
wine
white wine
watermelon
walnuts
xylitol
xanthan gum
xenergy
yogurt
yam
yellow pepper
zucchini

There you have it; a list of foods that’s not really much use for anything. But still interesting.

I put “professional” and “amateur” in quotes because it seems like in this case, the results you get from these two groups are opposite from what you’d expect. The financial market, and professional analysts, have been underestimating Apple for years now.

This story at Market Watch, “Time to Sell Apple“, is a perfect example. Here’s a few points from this article.

If a business fails to take care of its customers, its customers will go elsewhere … In the case of Apple, this is happening in front of our eyes, and the risks are therefore very high. Apple has stopped serving their customers well, and unless they start to serve their customers better the company will begin to lose more market share and revenue and earnings projections will come down aggressively.

But this whole statement is based on this assertion:

Most people think Apple’s customers are the end user, but … the real customers are third-party resellers, and Apple is not treating them right.

This is just flat out wrong. Apple has never pandered to the carriers and resellers. They’re the only phone manufacturer that doesn’t, and it’s one of the reason their real customers, the folks using the phones, prefer their products.

iPhone users are people who want an iPhone. Android users are, mostly, people who want a phone, and went with the one the carrier suggested.

The company’s high-growth phase is behind it

This is where the analysts methods fail. They can only analyze the data they have available, and they have no data about future products. But it’s these future products, the ones we don’t know about yet, that is where Apple’s growth comes from.

I don’t think the market has any model that can account for this, so they look at each new, incredibly successful, incredibly profitable thing that Apple does as if it’s the last one. Because how could they do otherwise?

Apple creates new markets. Moving into an established market like the TV business, with all the content complexity and interconnection requirements, just doesn’t seem like something they’d do. It’s a highly competitive space with low margins; not Apple’s kind of business.

And the idea that the world needs an Apple TV because TVs are too hard to connect seems off the mark. Hooking up a TV isn’t difficult; it’s hooking up all the other devices – the cable box, the PS3, the Xbox 360 with the Kinect, the Wii and its sensor bar, that make it difficult. Unless Apple is planning to take over the jobs that all the other devices people do with things hooked up to their TVs, they’re not going to be making things that much simpler.

An “Apple TV” without some pretty amazing content deals would still require a cable box, and if they could pull off those deals, why tie it to a new TV? Why not just making it available through the Apple TV for everyone?

First off, I signed up during the brief window when iTunes Match was available for sale but not actually working in Canada, so I had a completely broken service for a day or so.

But once it was officially switched on, it started working. There are 3 steps to iTunes Match:

Step 1 was painless. It whipped through my ~23k songs in an hour or so, and then went on to step 2. I left it at step 2 overnight, and when I woke up in the morning, it was stuck. It was about 80% done, but not moving.

I stopped iTunes Match and restarted it, and this time paid attention to where it stopped. This time it made it to song #22548, and then hung. Stopped, restarted, and it made it to 22549. Progress, but the 10 minutes or so it took for every attempt to make it to that song number was painful. I was watching with fs_usage to see if it was getting hung up on a certain album or something, but every time it stopped it was on something completely different.

But after 2 more restarts, it made it all the way through my music library. Now it’s on Step 3, uploading, and and with 4103 items to go, this one’s going to take a while.

The message I wanted to convey in this post is: If iTunes Match is hanging during Step 2, just stop it and restart it. Eventually it will complete.

Update three days later: It’s just over half done. About 1950 songs to go. I’m on DSL, so my upstream bandwidth is about 1 megabit.

But after that .. nothing. No new UI to let me sync my songs to the cloud.

Either this is was a mistaken rollout and they’ve switched it off (in which case they’ve got a lot of refunding to do) or they are having problems with all the extra subscribers and the problem will sort itself out shortly.

I’m thinking it was a mistaken rollout. Why? Because check this out:

It would be so out of character for Apple to ship UI with a typo. I’m guessing this was supposed to be some sort of test release that accidentally got pushed live.

Update: It’s really live now, and working for me. Typo and all.

Turns out reloadRowsAtIndexPaths:withRowAnimation: will deselect whatever rows you reload. Check this out:

It’s not obvious from the documentation that this operation affects the selection, and it took me a while to figure out why my selection was being dropped. The fix is simple enough: Preserve the selection yourself around the reload call.

Hmm. Now what? There is no direct download link for Xcode; the only way to get it is through the store.

When you get Xcode through the Mac App Store, what you actually get is an app called “Install Xcode”.

You run this app and it installs Xcode. It leaves itself in your /Applications folder, and it’s this app that has the Mac App Store receipt file identifying it as an app that’s installed, so normally all you need to do is get rid of this “Install Xcode” application for the store to stop seeing Xcode as installed.

But this didn’t work for me. I removed the installer, went back to the store, and it still wouldn’t let me download.

To figure out how the App Store was finding Xcode installed, I used the fs_usage tool:

Run this in Terminal before starting the App Store. This command will log all file system activity to a file named ‘out.txt’ in your home folder. With it running, launch the App Store. Then, back in the console, hit Ctrl-C to stop fs_usage, and open the out.txt file in an editor. Search for the string “Xcode”, and you should see some lines like this:

Aha! I had a drive mounted that had an old Applications folder, where the installer was already downloaded. I have no idea how I would have found this otherwise.

(I had tried searching for the Xcode installer using Spotlight but I had told Spotlight not to index that backup drive, so it didn’t find it).