Sounds good to me. Changed to 60s.
Ben
On Tue, May 28, 2013 at 12:47 AM, Aleksander Morgado
wrote:
> On 28/05/13 06:04, Ben Chan wrote:
> > 60s seems a bit excessive as users most likely give up earlier. Revised
> > the patch to have a 30s timeout.
> >
>
> Remember that MM lets the connection
On 28/05/13 06:04, Ben Chan wrote:
> 60s seems a bit excessive as users most likely give up earlier. Revised
> the patch to have a 30s timeout.
>
Remember that MM lets the connection attempt to be cancelled at any time
by Disconnect()-ing the Bearer during the connection attempt (best
effort is
60s seems a bit excessive as users most likely give up earlier. Revised
the patch to have a 30s timeout.
Thanks,
Ben
On Mon, May 27, 2013 at 12:52 AM, Aleksander Morgado
wrote:
> On 26/05/13 08:45, Ben Chan wrote:
> > This patch increases the number of retries, from 4 to 10, for connection
> >
On 26/05/13 08:45, Ben Chan wrote:
> This patch increases the number of retries, from 4 to 10, for connection
> status check during a connection / disconnection request, which handles
> some scenario when the connection / disconnection request takes more
> than 5 seconds to complete.
We recently u
This patch increases the number of retries, from 4 to 10, for connection
status check during a connection / disconnection request, which handles
some scenario when the connection / disconnection request takes more
than 5 seconds to complete.
---
plugins/novatel/mm-broadband-bearer-novatel-lte.c |
