Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    N9/N950 Email/Mail for Exchange - Get help & give feedback here

    Reply
    Page 89 of 95 | Prev | 79   87     88   89   90     91   | Next | Last
    jalyst | # 881 | 2012-12-11, 07:53 | Report

    ^A very decent man, as always

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 2 Users Say Thank You to jalyst For This Useful Post:
    Sergey_Kashin, thedead1440

     
    BanaSplit | # 882 | 2012-12-15, 19:25 | Report

    Dear all,

    I'm using Mail for Exchange on my Nokia N9 to connect to Google.

    Do you understand which impact the "End of Life" announcement (see link below) for their Google Sync service will have on our favourite device?

    Do I need to switch to IMAP and CalDAV for future sync with Google?

    http://support.google.com/a/bin/answ...7549&ctx=topic

    Thanks and regards

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to BanaSplit For This Useful Post:
    hood

     
    myk | # 883 | 2012-12-16, 02:45 | Report

    Is there any alternative to MfE for syncing contacts with google?

    They do say existing devices will continue to function. Hopefully if you need to reflash, and restore account settings from a backup it will still work. But if you delete and recreate a MfE account to solve problems as mentioned above, will it no longer work?

    Also, they say
    Originally Posted by
    Google Sync will continue to be fully supported for Google Apps for Business, Government and Education users who are unaffected
    Does this include my free legacy google apps account?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Sergey_Kashin | # 884 | 2012-12-16, 08:46 | Report

    Originally Posted by myk View Post
    They do say existing devices will continue to function. Hopefully if you need to reflash, and restore account settings from a backup it will still work. But if you delete and recreate a MfE account to solve problems as mentioned above, will it no longer work?
    Backup should work fine, but I don't think that after account re-creation you'll be able to sync it with google Of course it will depend on the Goggle's implementation on the server side, but most probably they will consider that this new account is trying to sync it self from a "different device", so server will reject the connection.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    thedead1440 | # 885 | 2012-12-16, 08:48 | Report

    Originally Posted by Sergey_Kashin View Post
    Backup should work fine, but I don't think that after account re-creation you'll be able to sync it with google Of course it will depend on the Goggle's implementation on the server side, but most probably they will consider that this new account is trying to sync it self from a "different device", so server will reject the connection.
    So Sergey if MfE is taken out for Google contacts can't the regular Google account option be expanded to include instead of just Google Talk contacts but all Google contacts?


    Also, a huge thank you for still staying around to help us

    Edit | Forward | Quote | Quick Reply | Thanks

     
    BanaSplit | # 886 | 2012-12-16, 16:40 | Report

    Originally Posted by
    Of course it will depend on the Goggle's implementation on the server side, but most probably they will consider that this new account is trying to sync it self from a "different device", so server will reject the connection.
    I can't imagine what should be the unique device identifier to check from server side. They shouldn't be able to catch your IMEI or similar?!
    Thus I rather guess that you won't be able to enable Google Sync in the future for GMail accounts where it wasn't enabled so far (unless you pay for it via Google Business Apps).
    Means, you will loose existing functionality in case that you change your sync to another non-enabled GMail account.
    I hope so...

    Edit | Forward | Quote | Quick Reply | Thanks

     
    aegis | # 887 | 2012-12-16, 22:40 | Report

    *sigh*

    It's such a pity the n9 didn't get CardDAV support.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    enerqy | # 888 | 2012-12-17, 18:34 | Report

    I'm having trouble with MfE. When I first got the phone (last Thursday), all the details synced with my gmail account. I flashed PR1.3 (no update for the region), and now it won't sync all the contact details. I ended up in a bit of a pickle at a meeting today, when I was sure I had someone's number. Luckily, I had my tablet with me. Is there any possible fix or workaround to this?

    Plus, I know this is reaching a bit, is there a way to force one-way syncing (from server-to-phone)? I noticed it all my merged contacts on the tablet unmerged :/

    Edit | Forward | Quote | Quick Reply | Thanks

     
    kollin | # 889 | 2012-12-17, 18:34 | Report

    Originally Posted by N770-Freak View Post
    I don't know where to upload the syncevlolution package... Hope ul.to is fine with you guys.

    The following package is based on the source from Ovek (http://people.debian.org/~ovek/harmattan/). I just enabled dav support!
    syncevolution_1.2.2-1_armel.deb... http://ul.to/j5wwxjd7

    I did the following steps to sync with ownCloud 4.0.4. I don't know if there's a better way to configure syncevolution, but at least it seems to work .

    DISCLAIMER / WARNING:
    You shoud first create a backup of your N9 calendar and addressbook!!! Don't blame me if you loose your data.


    Code:
    syncevolution --configure --template WebDAV username=MYNAME password=MYPASS  syncURL=http://MY.DOMAIN.TLD/owncloud/remote.php/ target-config@owncloud
    MYNAME = ownCloud login name
    MYPASS = ownCLoud password
    MY.DOMAIN.TLD = domainname
    @owncloud = identifier (maybe replaced with some other name. Important is that it is consistent within the whole configuration!)

    If you are using ssl access with a selfsigned certificate, you'll have to use the following code instead:
    Code:
    syncevolution --configure --template WebDAV username=MYNAME password=MYPASS SSLVerifyServer=0 syncURL=https://MY.DOMAIN.TLD/owncloud/remote.php/ target-config@owncloud
    CALDAV sync:
    Code:
    syncevolution --configure database=https://MY.DOMAIN.TLD/owncloud/remote.php/caldav/calendars/MYNAME/CALNAME/ backend=caldav target-config@owncloud mycalendar
    https vs. http = change this according to the URL you are using
    CALNAME = Name of your ownCloud calendar.
    mycalendar = identifier for this caldav sync.

    Code:
    syncevolution --configure --template SyncEvolution_Client sync=none syncURL=local://@owncloud username= password= owncloud
    Don't enter any credentials! username/password must be empty.
    owncloud = identifier...

    Code:
    syncevolution --configure sync=two-way backend=calendar database=N9calendar owncloud mycalendar
    N9calendar = calendarname of your N9 (empty for default calendar!)

    First sync [only first sync]:
    Code:
    syncevolution --sync slow owncloud mycalendar
    Later on you should remove "--sync slow":
    Code:
    syncevolution owncloud mycalendar

    CARDDAV sync:

    Code:
    syncevolution --configure database=https://MY.DOMAIN.TLD/owncloud/remote.php/carddav/addressbooks/MYNAME/ADDNAME/ backend=carddav target-config@owncloud myaddressbook
    https vs. http = change this according to the URL you are using
    ADDNAME = Name of ownCloud calendar
    myaddressbook = identifier

    This can be skipped if done already for caldav sync:
    Code:
    syncevolution --configure --template SyncEvolution_Client sync=none syncURL=local://@owncloud username= password= owncloud
    Don't enter any credentials! username/password must be empty.
    owncloud = identifier...

    Code:
    syncevolution --configure sync=two-way backend=addressbook database= owncloud myaddressbook
    First sync [only first sync]:
    Code:
    syncevolution --sync slow owncloud myaddressbook
    Later on you should remove "--sync slow":
    Code:
    syncevolution owncloud myaddressbook

    Hope that helps... (sorry for the bad text/layout structure, but I'm running out of time atm). Maybe someone else wants to put this in a proper wiki.
    Original thread is here: http://talk.maemo.org/showthread.php?t=85394

    Is ths method possible with google carddav and caldav? And how exactly (a little easier guide to follow)?

    P.S. Interesting line from https://syncevolution.org/documentat...onization-guis

    Originally Posted by
    SyncEvolution GUI
    SyncEvolution has a synchronization GUI, which is installed on MeeGo 1.2 as the ‘Sync’ application: http://help.meego.com/netbook/sync/about-syncing
    Is it possible porting it to Harmattan?

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by kollin; 2012-12-17 at 21:05.

     
    Jeffrey04 | # 890 | 2012-12-17, 21:50 | Report

    Originally Posted by kollin View Post
    Original thread is here: http://talk.maemo.org/showthread.php?t=85394

    Is ths method possible with google carddav and caldav? And how exactly (a little easier guide to follow)?

    P.S. Interesting line from https://syncevolution.org/documentat...onization-guis



    Is it possible porting it to Harmattan?
    it is ported to harmattan, but no official GUI

    http://people.debian.org/~ovek/harmattan/

    if you can't live without GUI, you may want to try this after installing syncevolution

    http://www.ruinelli.ch/harmattan/syncevolution-gui

    I am thinking of hosting this on my own server to sync my contacts/calendars from google

    https://github.com/xbgmsharp/sogosync

    so I can still sync using MfE using my N9

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 2 Users Say Thank You to Jeffrey04 For This Useful Post:
    hood, kollin

     
    Page 89 of 95 | Prev | 79   87     88   89   90     91   | Next | Last
vBulletin® Version 3.8.8
Normal Logout