Hi all!!!!
I just bought the N-Gage QD, and I'm having some trouble getting it to sync with my Mac with iSyng, as far as I can tell, iSync was abble to read the info I had in my phone but it can't write anything to it... the phone will crash and in the end iSync will give some error message to...
As anyone tried this... did it work... I know the QD is not in the supported list of phones in the apple/isync site, but... :P
anyway, my QD software is v03.15
hugs,
mari0
Try pairing your QD with iSync again. I had problems initially and almost gave up, but I tried again (turn BT on the QD on and off), and voila, it worked.
Good luck!
I tried that with no luck... every time that I start to sync, the N-Gage will crash with a message saying something like...
App. closed AppArcServerThread, and then in the end iSync will give some error...
I think that the bluetooth in the N-Gage has some problems, maybe they will sort it out in a future software update!!!!
hugs,
mari0
I have exactly the same problem. Every time I try to sync I get a message like that. I wonder if you guys found a solution for this problem... 🙄
powertowin wrote:I have exactly the same problem. Every time I try to sync I get a message like that. I wonder if you guys found a solution for this problem... 🙄
I can usually sync Address Book stuff, but calendars have never made it to my QD. I get the same error message frequently.
I guess there must be some subtile difference between the original n-gage and the QD that causes these difficulties. I'm guessing the next major revision to iSync will cure these problems. I hope, anyway.
I did a Hard Reset to my n-gage QD and re-installed applications one by one. I had 2 applications that cause the problem: SmartLauncher and PocketCounter. I really like the Launcher (I don't like the original n-gage orange menus) but I have to live without it... I informed the developers of this problem and if I get ananswer from them I will post it.
😉 For now the problem is solved, n-gage and iSync are cooperating with me again...
The odd thing is that I ran into errors like the ones described above without any custom apps loaded.