Calling bcharge via udev script or in the terminal on my 7100 only works on the 2nd connection. The 1st loads the modules but doesnt initiate them in time for the bb's handshake. then by the 2nd connection there already loaded and manage the handshake. I think the only way around this would be to keep the modules loaded in memory or to slow the device down, which is what the prompt on mass storage option will be doing. Unless anyone can change the code so that the handshake is a seporate module which gets called into memory and executed while the other parts of the drivers are still loading.
|