Anthony Martin’s Weblog

A blog about some guy. 
Filed under

Apple

 

iPhone/iPod touch and Benjamin

Benjamin loves iPhone/iPod touch.  No, I don't think Apple had autistics in mind when they designed them.  But that's just it.  Apple designed it so intuitively, practically anyone can fiddle with it and figure it out without instruction.

One morning, after my shower, I found him in his room, playing with his mom's iPod touch.  He swiped it out of our room, turned it on, unlocked it, navigated through the home screen, found his favorite applications, and launched it (currently either Banner and Peanut Butter Jelly Time).  He probably did this multiple times on this morning because he likes the transition between the home screen and the app when it's launched.  But we still have to supervise him.  It might actually make sense to set up a pass key to discourage him from swiping it.  Then again, that might backfire.

Here he is using my iPhone:



So far, there are only two things I have to really watch him on.  First, he still likes to put things in his mouth, especially objects he really likes.  This hasn't happened yet, that I'm aware of.  Second, he tends to accidentally get the home screen into "uninstall/move" mode.  The main reason this happens is because sometimes he doesn't realize his other fingers are touching the icons.  Touching the icons on the home screen for more than a couple seconds causes it to switch into this mode.  When this happens, all the icons shake and non-Apple apps can be removed by tapping the X.  He hasn't managed to uninstall anything yet.

There is a feature in the Settings that allows Restrictions on various features.  It'd be nice if "uninstall" was one of the listed restrictions, but it's not as of OS version 2.2.1.

Filed under  //   Apple   Autism   Gadgets   Home Front   Mobile   Video  

Comments [0]

Google Sync vs. MobileMe

I have very low expectations for my address book.  Back in 2002, when I first started using the Apple Address Book, I made my entries as neat and polished as I could.  Each entry had a picture, if possible (even though that feature wasn't fully supported at the time).  Then, Apple introduced iSync (through Dot Mac) and my entries got trashed.  So I gave up trying to keep it polished and I just let it do whatever.

My theory is that iSync trashed my Apple Address Book because I was monkeying around with the contact pictures before it was officially offered as a supported feature.  My contacts were fairly old by the time iSync came along, so the data structure was probably non-standard.  If I had started a new address book, it might have worked out better.  But being an early adopter has its risks.

Years later, I decided to start maintaining it again.  I picked the copy that was in the best shape and went from there.  Then I noticed that Apple was allowing sync (formerly iSync) between Google and MobileMe (formerly Dot Mac).  So I tried that out and it totally trashed both contact lists again.  At that point, many of my Google contacts had names but no e-mail addresses and there were massive duplicates.  I was rather unimpressed.

Then I got an iPhone, and I decided to start messing with it again.  That's when I discovered the "Look for Duplicates..." feature that was probably there for quite a while before I noticed it.  So this really didn't solve all of my problems, but it made me feel better that duplicates were being mitigated somewhat.

Until I noticed I was having another problem.  The "Look for Duplicates..." would merge contacts with empty names.  For some reason, Google contacts with empty names were all seen by MobileMe as the same contact.  So "Look for Duplicates..." would result in five or ten distinct contacts being clumped together as one.  The more I would sync, the more of these contacts would clump together.  The contacts had e-mail addresses and that's it because Google would add them as "Suggested Contacts."  So I separated them and plunked the name in or at least copied the e-mail address to the name field to make them distinct from the standpoint of the "Look for Duplicates..." feature.  This solution worked.

At this point, my contacts became stable and I was starting to get comfortable.  Over time, both Google and MobileMe became one address book.  Only problem was that MobileMe contacts were more versatile.  For example, I could label a phone number or an e-mail address any way I wanted while Google was limited to only "Work", "Home", or "Other" labels.

All this time, I had backups of my MobileMe address book in case anything went catastrophically wrong.  So I decided to try synchronizing with Yahoo!.  Why?  I have no idea.  But it worked pretty well from the standpoint of Google and MobileMe.  When I merged with Yahoo!, I had massive duplicates again, but the MobileMe "Look for Duplicates..." feature fixed it for both Google and MobileMe.  Yahoo! was completely screwed up with massive duplicates, but I didn't care.  I rescued my contacts out of Yahoo!, so I was happy.

After about two weeks of zero complaints, Google Sync of iPhone became available.  So I decided to dive into using it for contacts (I'm not using it for calendars as of yet).  I noticed that the backup method they recommended was to just sync the way I had been all along, through MobileMe.  That means my backup was already created.  Yay.  When Google Sync was enabled, all previous contacts were deleted as expected (this is normal when activating Microsoft Exchange on iPhone, and Google Sync implements Microsoft Exchange).  But since I was just moving to the same address book, I should be fine, right?  Nothing could possibleye go wrong.

And in fact, so far nothing has gone wrong, for the most part.  Although I did lose my MobileMe custom labels, all of my contacts came in just fine.  There was a slight problem with some of the phone numbers.  If I tagged them with a custom label, they didn't appear on my iPhone.  So I had to go in and label them as "Work", Home", or "Other" and they came right up in my iPhone.  There are some cases that setting the label doesn't seem to matter.  There are still bugs here to work out for sure.  I'll be watching the forum.

So yes, my address book is dumbed down a little more due to Google's limited fields and labels support.  Some of my contacts have screwed up mailing addresses.  But most of them are fine.  Not only that, but even though my iPhone is going right to Google now for all contacts, MobileMe is still synchronizing to Google, so my Apple Address Book is still up to date!

It's not perfect at all.  No synchronization solution ever is.  But I'm happy with it.  Both Apple and Google keep improving it.  Just a few days ago Google improved the search feature, so I hope this means they will keep improving it over the long haul.

Now, I fear someone will sue Apple and Google for unfair business practices.  Usually, when two companies cooperate like this, they are accused of trying to manipulate the market or not offering proper support.  In information technology, the usual way to avoid this is to create a consortium that anyone, including competators, can join.  The IDE hard drive was developed this way.  Sun Microsystems adds features to Java this way.  If Apple and Google don't start doing this, they will get shot at.

I don't want them to get shot.  I think they should be free to do this without a consortium if they choose.  It depends on whether or not they are themselves litigious or not.  But the European Union will probably force them into it if private US litigation doesn't get to them first.

Learn more ...

Filed under  //   Apple   Best Of   Geek Stuff   Google  

Comments [4]

My New Mobile

Sent from my iPhone

Filed under  //   Apple   Geek Stuff  

Comments [1]

New RAID Array

This week I got the family desktop configured to use a RAID array (mirrored) for primary storage.  So now it's booting, mirrored, and I feel better knowing the data is safe.  The array is built from two Seagate Barracuda SATA 7200.10 and I have a backup drive offline, waiting in its static bag in case one fails.  They are 250 GB each to match the original size in order to avoid any mirroring issues and because they were inexpensive.

After setting it up, I did a disk verify on both the old and new volumes to see which one was faster.  The old volume could be verified in about 10 minutes.  The new one took almost 2 minutes.  So I'm very happy with that boost.

I didn't need any special software to do this.  All I used were the utilities and features supplied in Mac OS X 10.5 Leopard.  I've seen several approaches, some more risky than others.  Some suggest third party software to accomplish what Leopard can already do.  So I recommend the following procedure:

  1. Install the new drive.
  2. Boot and begin in the Disk Utility to erase the new drive, calling it "New Macintosh HD".
    • Quit Disk Utility and issue a terminal command:
    • diskutil enableRAID mirror /Volumes/New\ Macintosh\ HD
  3. Reopen the Disk Utility, click on the new drive, and use the Restore option to copy the boot disk onto "New Macintosh HD".
    • You will need to pay attention because the new drive has two entries in the list of volumes; slice name and RAID group name.  You want to ignore the slice.
    • In the Restore tab of the new drive, drag the old volume to the first field and the new volume to the second field.  This will cause the first field to become "/" and the second field to become "New Macintosh HD" with an icon.
  4. When the copy is complete, selected "New Macintosh HD" as the boot disk in System Preferences and reboot.
  5. Now verify the old drive to make sure there were no errors.  I recommend doing this after booting on the new drive because the verify can now be more thorough due to the fact that the system didn't boot to it.  If it's all clear, proceed.  If not, you're on your own.  You probably just need to do a repair and this procedure start over.  Make sure you boot back to the old drive after the repair.
  6. Shut down and remove the old drive and replace it with another identical drive.
    • Replacing it is optional, but the old drive is now a backup of the system.  In my case, I wanted both drives to be identical for performance reasons.
    • Boot into the one-disk (degraded) RAID group and use the Disk Utility to drag the new disk into the RAID group.  This erased the new disk and start the mirror "repair".  This may take many hours to complete.
    • You need to pay attention because the dialog window in the Disk Utility can be behind the main Disk Utility window.  If you lose it, click Window, then Disk Utility Progress.  If it stops, close the Disk Utility and open it up again.  If you get bored, open the Activity Monitor and watch the Disk Activity or go have a beer (preferably both).


This is only one of many possible solutions.  Using this as the most basic solution is great because it guards against failure and is very low maintenance once it's set up and it doesn't cost as much.  Apple's Time Machine is still my favorite solution, but it's pretty expensive to do it right .

   
Click here to download:
New_RAID_Arraytag_Information_.zip (636 KB)

Learn more ...

Filed under  //   Apple   Best Of   Gadgets   Geek Stuff   Home Front   Information Technology  

Comments [0]

Calvin and Jobs


   

Click here to download:
Calvin_and_Jobs.zip (2842 KB)

Filed under  //   Apple   Humor  

Comments [0]

My New Blog

After months of dealing with problems in iBlog (the Mac software I use to publish my previous blog), I am now switching to Posterous as my primary blogging software.  It's all in-web, but it has a neat feature that lets me blog with an e-mail client if I so desire.  So it's kind-of the best of both worlds.

I plan on keeping my old blog up for reference since I link to it in conversations with people from time-to-time.

Filed under  //   Apple   Blogging  

Comments [0]