3650 + iSync: Does 3.16 firmware stop AppArcServerThread messages?

Aloha,

I have a 3650 running 2.54 firmware, and just recently got Apple iSync 1.5.1
which supports calendar syncing to the 3650. (A previous version of iSync
synced the address book, but not the calendar.)

Whenever I sync, I get this message a couple times on the phone:

App. closed
AppArcServerThread

I press OK on the phone and the process completes just fine. But I'd
really like to be able to sync without having to press buttons on the
phone in the middle of it.

Anyone else out there using iSync 1.5.1 with a 3650?

-Dan

--
Perfer et obdura; dolor hic tibi proderit olim. | http://dan.birchalls.net/

---

› See More: 3650 + iSync: Does 3.16 firmware stop AppArcServerThread messages?

"Dan Birchall" <[email protected]> ha scritto nel messaggio
news:[email protected]...
> Aloha,
>
> I have a 3650 running 2.54 firmware, and just recently got Apple iSync
1.5.1
> which supports calendar syncing to the 3650. (A previous version of iSync
> synced the address book, but not the calendar.)
>
> Whenever I sync, I get this message a couple times on the phone:
>
> App. closed
> AppArcServerThread

My friend used iSync 1.5.1 with Bluetooth 1.2 on MacOS X 10.2.6
It works fine, no message like that on the 3650, but I have to check the
firmware of his phone to see which version it is.

CC

In article <[email protected]>, Dan Birchall
<[email protected]> wrote:

> Aloha,
>
> I have a 3650 running 2.54 firmware, and just recently got Apple iSync 1.5.1
> which supports calendar syncing to the 3650. (A previous version of iSync
> synced the address book, but not the calendar.)
>
> Whenever I sync, I get this message a couple times on the phone:
>
> App. closed
> AppArcServerThread
>
> I press OK on the phone and the process completes just fine. But I'd
> really like to be able to sync without having to press buttons on the
> phone in the middle of it.
>
> Anyone else out there using iSync 1.5.1 with a 3650?

I haven't seen this, but I've heard about the issue. Were you running
a hack previously to do calendar syncing with the older version of
iSync/iCal?

One of these tricks might work. Go into the Calendar on your phone,
have an entry hilighted, then click Options, Delete, then Delete All
Entries. Now go back and try to sync the phone again.

If that still doesn't help, install a utility that will let you delete
files off the phone (I like FExplorer), then delete the
c:\system\data\calendar file. This stores all the calendar prefs, if
it's corrupt, deleting this should help. It'll be recreated next time
you run Calendar. Open Calendar first before trying a sync.

Let us know if either of these choices worked, and if you were running
the hacked iSync.

[email protected] (Jimbo) wrote:
> Dan Birchall wrote:
> > Whenever I sync, I get this message a couple times on the phone:
> >
> > App. closed
> > AppArcServerThread
> >
> > I press OK on the phone and the process completes just fine. But I'd
> > really like to be able to sync without having to press buttons on the
> > phone in the middle of it.
>
> I haven't seen this, but I've heard about the issue. Were you running
> a hack previously to do calendar syncing with the older version of
> iSync/iCal?

Hmmmm! At one point, I _tried_ one of the Mac-side hacks (it involved
changing one thing in a preference list file on the Mac), but it didn't
seem to work, so I undid it.

> One of these tricks might work. Go into the Calendar on your phone,
> have an entry hilighted, then click Options, Delete, then Delete All
> Entries. Now go back and try to sync the phone again.

I didn't think I could do this, until I stumbled upon it as an option in
MONTH view. Tried it, ran sync, still got the messages.

> If that still doesn't help, install a utility that will let you delete
> files off the phone (I like FExplorer), then delete the
> c:\system\data\calendar file. This stores all the calendar prefs, if
> it's corrupt, deleting this should help. It'll be recreated next time
> you run Calendar. Open Calendar first before trying a sync.

Tried this, ran the sync, still got the messages. And it's definitely
the calendaring that does it; they come up on the phone when iSync is
talking about syncing calendars and to do lists, not when it's talking
about syncing addresses.

> Let us know if either of these choices worked, and if you were running
> the hacked iSync.

Neither worked, and I tried a hack once but undid the modification to the
preference list file and haven't tried again.

FExplorer looks useful, though - finally a way to delete some things I
downloaded and could never figure out how to get rid of.

-Dan

--
Perfer et obdura; dolor hic tibi proderit olim. | http://dan.birchalls.net/

In article <[email protected]>, Dan Birchall
<[email protected]> wrote:

> > Let us know if either of these choices worked, and if you were running
> > the hacked iSync.
>
> Neither worked, and I tried a hack once but undid the modification to the
> preference list file and haven't tried again.
>
> FExplorer looks useful, though - finally a way to delete some things I
> downloaded and could never figure out how to get rid of.

Ok, I'm convinced that the hack must be what has triggered this. One
of the problems with it was that it caused some odd problems with the
time/date stamp of the calendar entries, and other folks had other sync
issues. I guess there's a good reason why the older iSync didn't sync
calendars to the 3650. LOL Something obviously wrote some bad data to
the phone that's stuck there till now when you're trying to sync the
calendar again with the new iSync.

Anyway, there must be some other file involved here. I've got a
feeling that resetting the phone to factory settings would probably fix
it, but that would also wipe out any apps or data you have on the
phone's internal memory. That, and I can't remember how to reset the
phone...

So... Next best thing I can think of would be to go through the
C:\system\data directory deleting other files that don't obviously tie
to some other app.

The ToDo's apparently share the same calendar data file, I've found
that deleting that file will kill any ToDo's.

Here are a few likely files I've found, might want to give these a try.
I'd restart the phone after deleting these, let the system reboot and
recreate them if necessary before trying to sync.

c:\system\iSync.ini
c:\system\Data\btstate.dat
c:\system\Data\Dtstor.ini
c:\system\Data\mrouteragent.ini
c:\system\Data\mRouterClient.dat
c:\system\Data\SyncSettings.db

[email protected] (Jeff Garbers) wrote:
> I'm also getting the AppArcServerThread message using iSync - I've
> deleted the 'calendar' file from the phone and still no joy. If
> anybody figures out what's going on here, I'd really appreciate
> hearing about it! Thanks.

Jeff, what firmware version is your phone? (*#0000# if you didn't already
know how to display the firmware version.)

It may actually be something on Apple's side, although I can't imagine
they'd have let it loose without someone testing it against a 3650...

I wonder if Panther will fix this in a week and a half?

-Dan

--
Perfer et obdura; dolor hic tibi proderit olim. | http://dan.birchalls.net/

In article <[email protected]>, Dan Birchall
<[email protected]> wrote:

> [email protected] (Jeff Garbers) wrote:
> > I'm also getting the AppArcServerThread message using iSync - I've
> > deleted the 'calendar' file from the phone and still no joy. If
> > anybody figures out what's going on here, I'd really appreciate
> > hearing about it! Thanks.
>
> Jeff, what firmware version is your phone? (*#0000# if you didn't already
> know how to display the firmware version.)
>
> It may actually be something on Apple's side, although I can't imagine
> they'd have let it loose without someone testing it against a 3650...
>
> I wonder if Panther will fix this in a week and a half?

I'm doubting it's a firmware problem, I'm on 3.16 BTW.

Everything I've heard from others indicates that this is being caused
by the iSync hack that some folks did to enable calendar syncing on the
3650. I know that this hack had some issues putting data in the
correct format for the phone, and among other things could result in
duplicate entries when folks upgraded to the new version of iSync that
supports the 3650.

My current theory is that some low level file on the phone has gotten
hosed, and this problem wasn't evident on the old version of iSync, but
now that data is being written correctly, the phone is gagging on it.

Panther should make no difference, as it's basically the same version
of iSync that's included, if I recall correctly.

If we can determine the corrupted file on the phone and delete it, we
should be fine. If I had a problem phone here I'd be happy to hack
away at it, but unfortunately (so to speak) mine is working fine, even
though I had run the hack previously.

[email protected] (Jimbo) wrote:
> I'm doubting it's a firmware problem, I'm on 3.16 BTW.
>
> Everything I've heard from others indicates that this is being caused
> by the iSync hack that some folks did to enable calendar syncing on the
> 3650. I know that this hack had some issues putting data in the
> correct format for the phone, and among other things could result in
> duplicate entries when folks upgraded to the new version of iSync that
> supports the 3650.
>
> My current theory is that some low level file on the phone has gotten
> hosed, and this problem wasn't evident on the old version of iSync, but
> now that data is being written correctly, the phone is gagging on it.
>
> Panther should make no difference, as it's basically the same version
> of iSync that's included, if I recall correctly.
>
> If we can determine the corrupted file on the phone and delete it, we
> should be fine. If I had a problem phone here I'd be happy to hack
> away at it, but unfortunately (so to speak) mine is working fine, even
> though I had run the hack previously.

I've got a new machine on the way (with Bluetooth), so when it gets here
I'll probably try to get data off the phone, reset the phone and try the
sync again from a clean system.

--
Perfer et obdura; dolor hic tibi proderit olim. | http://dan.birchalls.net/

Dan Birchall <[email protected]> wrote in message news:<[email protected]>...
> Jeff, what firmware version is your phone? (*#0000# if you didn't already
> know how to display the firmware version.)

It's 2.54, so I'm lagging behind a bit. I agree that it doesn't sound like a problem
on Apple's end; something on the phone is obviously encountering an unexpected
condition and crashing AppArcServerThread, whatever THAT'S for.

To paraphrase Alan Cooper: what do you get when you cross a computer and
a phone? Answer: a computer. I've never had a phone crash, require
firmware upgrades, run out of memory, or require rebooting before the 3650...

.... although it IS pretty cool.

In article <[email protected]>, Dan Birchall
<[email protected]> wrote:

> I've got a new machine on the way (with Bluetooth), so when it gets here
> I'll probably try to get data off the phone, reset the phone and try the
> sync again from a clean system.

Argh! So you're going to leave us waiting to find out if that fixes
it?

You should be able to get any data onto your current machine from the
phone, the data itself isn't corrupt, at least nothing that you'd be
transferring. Your calendar and contacts will be on your Mac anyway,
you'll just want to transfer any images/movies, and hopefully have any
other items you've downloaded to the phone (apps) already on your Mac
too.

[email protected] (Jimbo) wrote:
> In article <[email protected]>, Dan Birchall
> <[email protected]> wrote:
>
> > I've got a new machine on the way (with Bluetooth), so when it gets here
> > I'll probably try to get data off the phone, reset the phone and try the
> > sync again from a clean system.
>
> Argh! So you're going to leave us waiting to find out if that fixes
> it?

Unfortunately, yeah. It's a NICE new machine.

> You should be able to get any data onto your current machine from the
> phone, the data itself isn't corrupt, at least nothing that you'd be
> transferring. Your calendar and contacts will be on your Mac anyway,
> you'll just want to transfer any images/movies, and hopefully have any
> other items you've downloaded to the phone (apps) already on your Mac
> too.

Yeah. I'm hoping I saved .SIS files for the one or two apps I bought.


--
Perfer et obdura; dolor hic tibi proderit olim. | http://dan.birchalls.net/

> > Argh! So you're going to leave us waiting to find out if that fixes
> > it?
>
> Unfortunately, yeah. It's a NICE new machine.

Well, keep us posted. I'd really love to find out what's going on so I
can get the info to some others that have the same issue.

I'm actually feeling guilty that my phone is working fine... LOL

[email protected] (Jimbo) wrote:
> > > Argh! So you're going to leave us waiting to find out if that fixes
> > > it?
> >
> > Unfortunately, yeah. It's a NICE new machine.
>
> Well, keep us posted. I'd really love to find out what's going on so I
> can get the info to some others that have the same issue.
>
> I'm actually feeling guilty that my phone is working fine... LOL

Hehe.

Well, okay. I just paired the devices (which went much better than it
did when I first paired with my iBook, if only because THIS time, I
had some slightly clue what I was doing.

Now to try to get that sync-ing feeling.

-Dan

In <[email protected]> "Abimanyu" <[email protected]> writes:

>"Dan Birchall" <[email protected]> ha scritto nel messaggio
>news:[email protected]...
>> Aloha,
>>
>> I have a 3650 running 2.54 firmware, and just recently got Apple iSync
>1.5.1
>> which supports calendar syncing to the 3650. (A previous version of iSync
>> synced the address book, but not the calendar.)
>>
>> Whenever I sync, I get this message a couple times on the phone:
>>
>> App. closed
>> AppArcServerThread

>My friend used iSync 1.5.1 with Bluetooth 1.2 on MacOS X 10.2.6
>It works fine, no message like that on the 3650, but I have to check the
>firmware of his phone to see which version it is.

>CC

Just last week I installed iCal 1.5.1, the newest iSync, the newest iSync
Palm Conduit, and the newest Bluetooth out there, and it all worked just
fine....

--Seth
--
~~~~~~~~~~~~~~~~~~~~~~~~
Seth J. Bookey
New York City
[email protected]

[email protected] (Jimbo) wrote:
> > > Argh! So you're going to leave us waiting to find out if that fixes
> > > it?
> >
> > Unfortunately, yeah. It's a NICE new machine.
>
> Well, keep us posted. I'd really love to find out what's going on so I
> can get the info to some others that have the same issue.
>
> I'm actually feeling guilty that my phone is working fine... LOL

Well. Got the machine, which was running OS X 10.2.7. Upgraded it to
10.2.8, still got the AppArcServerThread messages. Just today, upgraded
it to 10.3, still got the AppArcServerThread messages.

Oh well.

-Dan

--
Perfer et obdura; dolor hic tibi proderit olim. | http://dan.birchalls.net/