On 06.01.2012 16:53, Mathieu Trudel-Lapierre wrote:
> The issue probably also affects o-d-s, so let's keep a task open for it
> too.
Not to be disrespectful but it seems that nobody in this topic has
opened his eyes I provided both the reason why it happens (some devices
fail to connect immediately after scan) and a tentative fix. Granted,
the fix is ugly and the real way would be to wait 3 seconds only if
initial attempt fails, but it's more of a technical for someone familiar
with the code given that the reason is known.
On 06.01.2012 16:53, Mathieu Trudel-Lapierre wrote:
> The issue probably also affects o-d-s, so let's keep a task open for it
> too.
Not to be disrespectful but it seems that nobody in this topic has
opened his eyes I provided both the reason why it happens (some devices
fail to connect immediately after scan) and a tentative fix. Granted,
the fix is ugly and the real way would be to wait 3 seconds only if
initial attempt fails, but it's more of a technical for someone familiar
with the code given that the reason is known.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko