Activesync Constantly Starts Up

[lexluthor]

Still can't get this to work.

After using PolloLoco's method last night, Activesync didn't start up on it's own all night.

But, this morning, I did activesync it with my desktop. Activesync started up and worked fine. When the sync was done, Activesync was still loaded. I terminated it. After a short amount of time, it started up on it's own and then continued to do so after each time I started it.

I then used dan-htc-touch's suggestion and disabled the replog notification event that had to do with the time change. I rebooted, Activesync started upon reboot (which it didn't after I did Polloloco's method last night). I closed it and it restarted. Should I have deleted the notification entry rather than disabled it? Would that have made any difference?

So, for me, Polloloco's method worked, but only until I Activesyncd for the first time, then it went back to the way it was.

Any other ideas?

[PolloLoco]

Originally Posted by lexluthor

Still can't get this to work.

After using PolloLoco's method last night, Activesync didn't start up on it's own all night.

But, this morning, I did activesync it with my desktop. Activesync started up and worked fine. When the sync was done, Activesync was still loaded. I terminated it. After a short amount of time, it started up on it's own and then continued to do so after each time I started it.

I then used dan-htc-touch's suggestion and disabled the replog notification event that had to do with the time change. I rebooted, Activesync started upon reboot (which it didn't after I did Polloloco's method last night). I closed it and it restarted. Should I have deleted the notification entry rather than disabled it? Would that have made any difference?

So, for me, Polloloco's method worked, but only until I Activesyncd for the first time, then it went back to the way it was.

Any other ideas?

I don't know what you're doing wrong - but I suspect you must be doing something wrong. Since I've done the fix exactly as I specified - I haven't had activesync pop up once. And I have connected to my computer via activesync since. When I then closed out activesync via the drop down menu - it stayed closed.

[lexluthor]

Well, here's where I'm at now.

I followed the link Zoheb posted above and followed that procedure.

The one change I made was the in dotfred's notification section, I only disabled all of the repplog entries (except for the one with AppRunAfterRndisFnDetected in it) instead of deleting them. I don't know why disabled wouldn't work and it's a lot easier to reverse that way.

Also, it's a little different from what you posted as that it doesn't delete the fake server after it's created.

So far after activesyncing and rebooting, activesync hasn't started up again on me.

I was waiting a little more to be sure and then I'll try to write up details of exactly what I did.

I'm not sure which fixes it, adding the fake server or disabling the repplog notifications or both. It could be that only one is needed, but I haven't tested that.

[chappy]

I was under the impression that active sync was what kept the time updated.

[lexluthor]

Originally Posted by chappy

I was under the impression that active sync was what kept the time updated.

I think you might be right. I think any of the above steps would disable that, no?

I can live with that if it keeps AS from starting up all day.

Is there a way to manually update the time?

Also, I don't think this stopped my phone from randomly waking up. That still happens.

[lexluthor]

I'd say this is definitely resolved for me. Not sure exactly which combination did it, but it's not starting up anymore except when connected to the PC via Activesync.

Thanks all.

One last question. Since this method turned off the auto update of the time, is my time going to slowly get off track? If I just do the update now button in that section where I turned off the time sync, will that re-sync it manually, just that one time?

[edog11]

I think I had similar issue with Activesync starting on it's own on sprint touch pro. But I think when I turned off BEAM (unchecked to receive incoming beams), Activesync stopped starting on it's own. This was a while back so you may have different issue.