maemo.org Bugzilla – Bug 6374
Add support for Google calendar
Last modified: 2011-03-31 16:39:07 UTC
You need to
before you can comment on or make changes to this bug.
Maemo 5 SDK final release. Should apply therefore also to the product.
EXACT STEPS LEADING TO PROBLEM:
Google calendar is a very popular Calendar and I think Google calendar should
be supported for better and complete user experience
I want to be able to add Google calendars.
Only local and birthday calendars a are supported.
EXTRA SOFTWARE INSTALLED:
IMHO, I think a lot of users take this as granted on devices as the Nokia N900.
*** This bug has been confirmed by popular vote. ***
You can sync google calendar using Mail for Exchange.
It isn't prefect but can work while waiting for a different kind of support.
Thanks for reporting this.
For future reference, please do not set priority to High. Thanks.
(In reply to comment #2)
> You can sync google calendar using Mail for Exchange.
True, but note that it is not officially supported. If it works, you are lucky.
Also, feel free to vote for this report.
Also see http://talk.maemo.org/showthread.php?t=36082 for a how-to.
I think Juanjo Marin already said this, but I just want to make it clear.
The limited support of Google calendars in MfE will only allow synchronizing
the first calendar in your google calendars. Consider how limiting this is in
Let's say you have two calendars, a personal calendar and a business calendar.
With existing support, you can only synchronize personal calendar and not the
It makes the transparent syncing of Android very attractive in comparison.
The scope of bugs.maemo.org are bugs and only very specific and no-brainer
enhancement requests. This report contains a feature request that is too
generic for bugs.maemo.org. Please post this problem and propose your
solution in Maemo Brainstorm instead:
More information: http://wiki.maemo.org/Maemo_brainstorm
I've added a brainstorm for this bug with all your comments. Thanks for your
help and interest !
*** Bug 12111 has been marked as a duplicate of this bug. ***