Can you recap the actual error? I didn't understand what effect
increasing the verbosity should have to the framework other than making
it slower.
not fully. it always boild down to a message saying "resource gsm could
not be enabled, status is enabling" or soemthing to that effect.
i always got the impression, either the resource is stuck or just to slow.
my reasoning is as follows:
fso attempts to enable the resource. the resource gets ready. fso is
notified about the resource being enabled and continues.
but in our case the resource apprently does not get ready in the time fso
expects it to.
when increasing verbosity, the resource gets somehow more time to get
ready -- probably due to the delay caused by creating and outputing the
messages.
thus, if we could identify the point where the delay in fact causes the
resource to get the time needed, we could have simply an increased timeout
there.
for faster resources/hardware it would not be an issue, since once the
resource gets ready, fso is notified anyway and does not wait.
_______________________________________________
Smartphones-userland mailing list
Smartphones-userland@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
