From what I can see and hear I cannot reproduce this issue in firmware SA30 build 1206 version 1.7 anymore. It seems to be resolved. Maybe this has been fixed in an earlier build, I will mark this issue as solved now.
From what I can see and hear I cannot reproduce this issue in firmware SA30 build 1206 version 1.7 anymore. It seems to be resolved. Maybe this has been fixed in an earlier build, I will mark this issue as solved now.