Contacts created on phone never make it to Groupwise, and folder changes do not behave properly.

In this case I'm testing with an Android phone (HTC Hero on Sprint to be exact), it seems more reliable on our WinMo phones (HTC Snap & Touch Pro 2, but happens there too).

On the phones that have the problem, you can create a contact in Groupwise and it will send to the phone fine. Once it is on the phone you can change/delete it etc. from the phone and this change will propagate back to Groupwise. However, NO new contacts created on the phone ever get to GW - nor do "events" to convert them ever show up on the info page you get to by clicking the user name on the Mobility Connector monitor. It's like the Android activesync doesn't even see them.

Steps to reproduce:
1. Create contact (as an exchange contact obviously).
2. Make sure to file it in a syncing folder BEFORE saving. Saving it before filing seems to screw up the syncing almost 100% on WinMo phones (ie if you make a generic contact then change the category to one of the folders you are syncing, it will rarely get sent to GW), so I'm extra careful to file before saving on Android.
3. Wait.

Other contact weirdness:
*Changes in the folder a contact is filed in DO NOT pass on to phone BUT you:
*CAN delete a contact (from phone->GW) from the original book even if you change the book on the phone & it no longer matches.
IE:
1. "Bob Smith" is in folder A in Groupwise and on the phone.
2. In phone, move Bob Smith to Folder B
3. In Groupwise, nothing ever happens
4. On phone, delete Bob Smith (who is filed in Folder B on the phone & Folder A in GW)
5. Bob Smith will (usually) get deleted from GW.

*CANNOT delete a contact (from phone->GW) from the original book if you change the book on groupwise
*CAN delete a contact (from GW->phone), if the name matches
1. "Bob Smith" is in folder A in Groupwise and on the phone.
2. In GW, move Bob Smith to Folder B
3. On phone, nothing ever happens
4. In GW, delete Bob Smith from Folder B (he should have already been removed from Folder A when you moved him)
5. Bob Smith will get deleted from the phone, where he was still in folder A

Summary:
*folder changes on either side do not propagate correctly, but do seem to behave predictably

My guess is that this is because Mobility stores contacts via the name, so you run into a situation similar to the "bad contact/same name/no name" error. If you:
1. Delete Bob Smith from Folder A in GW
2. Wait until the delete propagates to phone
3. Add Bob Smith to folder B in GW

It will usually propagate correctly. The software just can't handle a "move" (which GW doesn't seem to support anyway you have to do a copy, delete) because it makes the changes too fast.

?