On Tue, 2008-04-22 at 19:54 +0400, Ilya Bakulin wrote: > On Mon, 21 Apr 2008 19:28:32 +0100 > Mark Ellis <[EMAIL PROTECTED]> wrote: > > > You're not wrong, in fact sync-engine appears to not be set up to deal > > with locked WM6 in general, this is not just on hal. Your patch is on > > the right lines, but I've got a nasty feeling it wont work in all cases, > > I just need to think about it. > > > > With any luck Guido or John are reading and may be able to pitch in. > > > > OK, I'll continue testing SyncEngine working with this patch. By now I > haven't encountered any problems. Perhaps you could advise me what to do to > see if it will fail? > > As I understand, device lock-state shouldn't change once it's connected and > unlocked?
You're right, it shouldn't change, except for the locked to unlocked changed when you authenticate. The problem is that WM5 can be unlocked directly by the sync-engine auth procedure (and also indirectly if something else authenticates) while WM6 is always a more indirect process. Mark ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
