The behavior you are seeing might be caused by the
bug described in this post. If FFDL causes metadata to be sent to the device a second time during a connect, the bug could cause the Read info to change back to what it was before the connect. I am not sure, but it sounds that that is what you are describing.