Leopard talks to the Motorola MaXX
As you may recall at the begining of the year I had to buy a new phone - so I lashed out and got a Motorola Maxx after doing so research on getting it to work with my Mac. Given what I'd learnt back then I thought I write it up for anyone else going through a similar process.
Well with Leopard upon us and the MaXX still around (only until the 3G iPhone ships in Australia...) here's what I've learnt after this afternoon's upgrade to my Mac Pro.
The first is that the venerable yet buggy RAZRV6.phoneplugin no longer works with Leopard (and you get a nice warning from iSync the first time it runs). Leopard seems to have a focus on helping users because not only was I told that the plug-in wasn't compatible but I was also given some choices to reveal the file and let me throw it in the trash, "before restarting iSync". Unfortunately I didn't get a screenshot of this helpful little dialog.
Given the events so I thought I'd better run through the whole Bluetooth setup etc to make sure my phone was talking to the Mac at least. OK, so opening the Bluetooth System preference and connecting was nothing spectacular but the the results were fantastic. Not only can I connect to the MaXX V6 now but I can browse the media on it and the installed MMC.
All I do is open the Bluetooth menu from the main menu bar, select "Craig's Maxx" and then select "Browse"
No more clunky hacks to get file's off the phone...
Or to load them...
Now some of you will be saying "hey you could do this in Tiger" - well lets put it this way not as well. My previous experiences were, shall we say, less than enjoyable... Don't worry though it gets better...
Remember I had to remove the very useful (until now) RAZRV6.phoneplugin I recommended back in January - well iSync gave me a nice surprise when I fired it up. There as a supported device was an icon for my phone - brilliant! Unfortunately closer inspection revealed that it was only phone book/contacts support as "This phone does not support calendar synchronization" which will explain why the previous plug-in had so many problems with new events going either way...
