[Windows Phone 7 Q&A, Help & Troubleshooting] quetzalcoatl.pl:
As I have the phone on my desk for a few days, I've decided to check a few things more. Here's the log:

Legend for some symbols:

"-" means disconnected, killed, terminated etc

"+" means launched, connected, or things actually done by me

":" is the response/result

"vsdeploy" means deploying an app to the device via VisualStudio

"[!]" points of interest

empty line: nothing, just text formatting

###

Experiment #1 (typical setup for unlocking, but without Zune running)

-Zune (app, closed normally)

-WMZuneComm (service, killed via taskmanager)

-ZuneWlanCfg (service, killed via taskmanager)

-phone (device, unplugged)

+rebooted the phone

+phone (in airplane mode)

:vsdeploy fails with "zune not launched"

:chevron fails "connect usb/start zune"

+wp7connect succeeds

:WMZuneComm starts

:vsdeploy fails with "app launch fail. ensure screen unlocked and developer unlocked"

:chevron starts

+unlock

:chevron succeeds

:vsdeploy succeeds

+relock

:chevron succeeds

:vsdeploy succeeds [!]

:chevron restarted, claims device IS locked

:vsdeploy succeeds [!]

+wp7connect succeeds

:chevron restarted, claims device IS locked

:vsdeploy fails with "app launch fail. ensure screen unlocked and developer unlocked"

###

Experiment #2

-WMZuneComm (was started by wp7connect, killed via taskmanager)

ZuneWlanCfg (wanst running)

Zune (wanst running)

-phone

+phone (DIFFERENCE: noairplane, but not connected to any network)

:vsdeploy fails with "zune not launched"

:chevron fails "connect usb/start zune"

+wp7connect succeeds

:WMZuneComm starts

:vsdeploy fails with "app launch fail. ensure screen unlocked and developer unlocked"

:chevron starts

###

Experiment #3

+WMZuneComm (was started by wp7connect in Ex#2; DIFFERENCE: left running)

ZuneWlanCfg (wanst running)

Zune (wanst running)

-phone

+phone (DIFFERENCE: connected to WIFI)

:vsdeploy fails with "zune not launched"

:chevron fails "connect usb/start zune"

+wp7connect succeeds

:vsdeploy fails with "app launch fail. ensure screen unlocked and developer unlocked"

:chevron starts

+unlock

:chevron succeeds

:vsdeploy succeeds

+relock

:chevron succeeds

:vsdeploy succeeds [!]

:chevron restarted, claims device IS locked

:vsdeploy succeeds [!]

+wp7connect succeeds

:chevron restarted, claims device IS locked

:vsdeploy fails with "app launch fail. ensure screen unlocked and developer unlocked"

conclusion: WMZuneComm does not need to be killed or restarted

conclusion: airplane/noairplaine/nowifi/wifi on the phone is irrelevant

###

Experiment #4

-WMZuneComm (killed via taskmanager)

ZuneWlanCfg (wanst running)

Zune (wanst running)

-phone

+phone (connected to WIFI)

+Zune (with update pending and "updatelater" was chosen)

:WMZuneComm started

:ZuneWlanCfgSvc started [!] (wp7connect/chevron/vsdeploy did not need that)

:vsdeploy fails with "ensure phone is connected" [!] (different message)

:chevron fails "connect usb/start zune"

-Zune

:chevron fails "connect usb/start zune"

+wp7connect succeeds

:chevron starts

###

Experiment #5

-WMZuneComm (killed via taskmanager)

-ZuneWlanCfgSvc (killed via taskmanager)

-Zune (closed)

-phone

+Zune (idle)

+phone (connected to WIFI, plugged to PC *after* Zune was started)

:WMZuneComm started

:ZuneWlanCfgSvc started

+waited till Zune finds an update, and with update pending and "updatelater" chosen

:vsdeploy fails with "ensure phone is connected" [!] (different message)

:chevron fails "connect usb/start zune"

-Zune

:chevron fails "connect usb/start zune"

+wp7connect succeeds

:chevron starts

###

Experiment #6

WMZuneComm (DIFFERENCE: I've accidentially forgot to kill it)

ZuneWlanCfgSvc (DIFFERENCE: I've accidentially forgot to kill it)

-Zune (closed)

-phone

+phone (connected to WIFI)

+Zune (with update pending and "updatelater" NOT chosen by the user, Zune as left with the black "update me to update phone" screen)

->WMZuneComm

->ZuneWlanCfgSvc

:vsdeploy fails with "???oops..I didn't write down"

:chevron fails "connect usb/start zune"

DIFFERENCE: I've forgot to quit Zune

+wp7connect succeeds [!] (normally it would complain about Zune running)

:vsdeploy fails with "app launch fail. ensure screen unlocked and developer unlocked"

:chevron starts

+unlock

:chevron succeeds

:vsdeploy succeeds [!]

And since Ex#6, when somehow I managed to successfully simultaneously run Zune and WPConnect.exe, I cannot force the soft/dev to the original state, where the Zune was blocking the phone because of the pending update.

Now if the Zune is UP, chevron and vsdeploy work properly, regardless of any updates pending, phone-airplane on/of, phone-wifi on/of. The same with connection made by wpconnect. It seems a permanent state, I've already tried restarting services, zune and rebooting the phone. The only thing left is rebooting the PC which I do rarely, but will do in a few days just to make sure it's permanent.

------------------------

Conclusions:

C1) from Ex#1: wpconnect seems sufficient to run and operate chevron properly, and to deploy apps to the device. service ZuneWlanCfg is not needed. WMZuneComm is ensured to run by wpconnect

C2) from Ex#1: opened wp7connect-connection seem to remember the device being in UNLOCKED state. If phone connection was opened with wpconnect to a locked device, and the device was then unlocked and relocked, until unplugging the device, the connection acts as if the phone is unlocked all the time since unlocking. Unplugging and replugging shows the device was actually unlocked and relocked properly by chevron.

C3) from Ex#1: opened wp7connect-connection does not remember the device being in LOCKED state. If phone connection was opened with wpconnect to a locked device, the connection acted as if the device is locked. If the device was then unlocked, the connection acts as if the phone is unlocked.

C4) from Ex#2: running WMZuneComm is not enough for chevron and vsdeploy. the wpconnect must be re-run after every unpluggin-repluggin of the device

C5) from Ex#2 & Ex#3: having active airplane/noairplaine/nowifi/wifi on the phone seems irrelevant to chevron/vsdeploy operations

C6) from Ex#1 & Ex#3: WMZuneComm does not need to be killed or restarted, re-running wpconnect is sufficient to reset the phone-connection's state

From the previous post, F1 and F2 are now broken on my PC.

From the previous post, U1 turned out to be FALSE [relocking really disabled vsdeploy abilities]

From the previous post, U2 turned out to be PARTIALLY TRUE [an active connection started by a single launch of wpconnect.exe remembers UNLOCKED state even if the dev is relocked]

From the previous post, U1 turned out to be FALSE [relocking really disabled vsdeploy abilities]

From the previous post, U1 turned out to be TRUE [except the chevron's crash 'explanation'. by the way, during today, chevron has never crashed]