about the ActiveSync issue

---

I found this on Microsoft's support site. When turned on, it creates a very detailed sync log, maybe it will help you track down the problem:

Verbose Logging
You can also turn up logging on the device to gather more information for troubleshooting purposes.

To enable logging on the device:
Click Start, point to Programs, and then click ActiveSync.
Click Tools, click Options, click Server, and then click Advanced.
Minimize the keyboard.
Change the logging level to Verbose.
Close the Options dialog box.
The log is saved in text format in the Windows\ActiveSync folder.

The log file is cleared at the beginning of each synchronization session. To retain the log file, copy or rename the log file before you start another synchronization session. To copy the log file:
Synchronize your PocketPC device with the server. If the synchronization fails, synchronize until the point of failure.
Disconnect your PocketPC device to prevent the log file from being overwritten if an automatic synchronization is scheduled.
In Windows Explorer, expand My Device, expand Windows, and then locate the log file that is in the ActiveSync folder.
Rename the log file.

someone already did this. the rom doesnt even try to connect to the server.

but this doesn't really help fixing the issue. thanks.

chif are you Cooking something new for os.

there is nothing really new to cook...

waiting for new cht-beta-version to test.

IS AS-Issue still there if you only cook an empty rom without any modifications/optimizations? Only 2.13 ROM and 1.72 drivers?

Originally Posted by Bib_x

IS AS-Issue still there if you only cook an empty rom without any modifications/optimizations? Only 2.13 ROM and 1.72 drivers?

i'm not using 1.72 drivers. as much as possible from 2.13.
and yes, the problem is there even if i dont add/mod anything.

And what about 2.10? Is there any AS-Issue?

Maybe it is better to use older files in this case?

Originally Posted by Bib_x

And what about 2.10? Is there any AS-Issue?

Maybe it is better to use older files in this case?

same as in 2.13.
i decided to move on because i simply don't know how to fix it.
better to release a anticipated rom with this bug than releasing nothing.

many users don't use activesync at all and are happy with it (including myself).

i think it's a certificate issue.

http://forum.xda-developers.com/showthread.php?t=689930

hd2 os poll added.

progress report:

testing 21905 (com2)