Hi, On Fri, Oct 20, 2023 at 2:44 AM Paul Menzel <pmenzel@xxxxxxxxxxxxx> wrote: > > Dear Purendra, > > > Thank you for sending version 2. (No space is necessary in the prefix > before the colon.) > > > Am 20.10.23 um 11:37 schrieb Purendra Singh: > > This issue is observed when multiple profiles are active from > > multiple connected devices: A2DP + HID + OBex File transfer > > > > File received status of some reference devices is delayed, > > that causes timeout and file transfer status error (Variation > > of timeout is between ~100 seconds to ~450 seconds). > > > > We tested with Motorola Edge, Samsung M33, OnePlus 6T. > > > > Experimentaly we increased the timeout and at 500 seconds no issue was > > Experimentally > > > observed. > > Oh, it’s really seconds. Isn’t greater than 8 minute timeout *not* very > user friendly? Yeah, something like that would probably cause the user to assume the operation didn't work. > > --- > > gobex/gobex.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/gobex/gobex.c b/gobex/gobex.c > > index e9b89cead..f0e1c2c83 100644 > > --- a/gobex/gobex.c > > +++ b/gobex/gobex.c > > @@ -22,7 +22,7 @@ > > #define G_OBEX_MINIMUM_MTU 255 > > #define G_OBEX_MAXIMUM_MTU 65535 > > > > -#define G_OBEX_DEFAULT_TIMEOUT 10 > > +#define G_OBEX_DEFAULT_TIMEOUT 500 > > #define G_OBEX_ABORT_TIMEOUT 5 > > > > #define G_OBEX_OP_NONE 0xff > > > Kind regards, > > Paul -- Luiz Augusto von Dentz
