Madness Without Method

Before I tackle this issue, I wanted to share my experience with an awesome Blackberry product out there. I’ve used it to totally trick out my Blackberry… it’s really sweet! You can get the latest movies for your Blackberry, videos, ringtones, themes, and wallpapers. Check it out!

I absolutely love my Blackberry and I don’t know what I would do without it. I also love Google and the organization/email/mobile tools that they make available. Google came out with a Blackberry application called Google Sync. It synchronizes the contact and calendar information on your Blackberry with Google Calendar. It’s a great concept and it works pretty well– with one exception. I’ve found that things get screwed up when you create an all-day or multi-all-day event on your Blackberry and it syncs with Google. I’ve isolated the issue to Google calendar because I’ve created the event on my Blackberry and then gone back in and verified that it looks good. It always done until I do a force-sync with Google, then it all falls apart. For me, the one all day event looks like a multi-day event that runs from 8 pm to 8 pm across two days. It’s really annoying!

I’ve tried various “fixes” that I’ve found online, but nothing worked for me. I synced timezones in Google calendar to the timezone on my Blackberry. I thought it was a timezone issue and was sure that would fix it– no dice.

I did find one fix that works although it is a little annoying to implement. It really will work fine, though, until Google comes out with a new version of Sync to address this (although it’s been a while since the issue popped up, so they don’t seem too motivated to repair it). I think the root of the problem is with the “All Day Event” button on the event setup screen. Don’t use that button! Instead, create your events as running from 12:00 AM – 11:59 PM on the day of your event. If you have a multi-day event, just use the times. I haven’t run into any issues with this approach. I haven’t seen this simple solution out there… good luck! Please leave a comment if you have a better fix or workaround.