ChadKirchner.com

So I have a 32gb iPod touch as a portable music player.  When I purchased my 2010 Ford Fusion Hybrid, I was pleased to know that it came equipped with Sync, so that I could take my iPod with me in the car.  During the first sync to the car, all of the music transferred properly, and almost all of the songs would play without difficulty.  Over time, several iPod software updates came along, followed by several Sync updates as well.  After the first time I updated the iPod with new music, and re-plugged it into the car, it no longer worked correctly.

It would take HOURS for the iPod touch to completely index and then when it would index, it still would not be able to play all the songs.  Over time it would not even play 50% of the songs on the device, skipping to the next track time and time again.

Today I purchased a 16gb iPod nano.  In the past, when I have had iPod adapters and interfaces in cars (mainly through the aftermarket), the nano always seemed like the device that would work the best.  It has faster seek times than the classic, and is not nearly as complex as the touch.

So far, after my first synchronization, it appears that the nano is working perfectly fine in the Fusion.  I will continue to document my woes as time progresses.  I love the Sync interface, but I just want it to work well with my iPod as well.

Last Thursday, my New Every Two renewal was set up for Verizon Wireless, and I decided that a Motorola Droid would be a suitable replacement to my previous phone.  I was intrigued by the Google integration and looked forward to downloading a bunch of customizable apps.  Yes, the Google integration worked well, and I did find some great apps, I had to return the phone yesterday, and here are the reasons why.

1. On Monday of this week, I was driving to work and my car (Sync-enabled Ford Fusion Hybrid) announced that it had lost the Bluetooth connection to the phone.  I attempted to reconnect it with the phone and with the car, and neither method worked.  Force closing all open applications did not fix it either.  I had to perform a complete reboot (which is not a quick process on that phone) in order to re-enable the Bluetooth connection.
2. On Tuesday of this week, I was participating in a conference call for one of my online classes, and during the call the phone decided to freeze up and stop working.  A Force Quit dialog box came up, asking me if I wanted to quit the phone application.  NO!  I was in the middle of something important.  I was able to wait it out and regain control of the phone, but this was disheartening.
3. Yesterday I received a phone call from work, and when I answered the phone I could hear them, but they could not hear me.  I then proceeded to call someone else and they could not hear me either.

I need a phone that I can trust.  I expected to have some bugs and glitches, but this is technically version 2.0 of the Android software, so I did not expect it to be this bad.  I do not know if it is a Motorola problem or a Verizon problem, but I have never had a good Motorola phone in my life.  That is why it was returned.