All of lore.kernel.org
 help / color / mirror / Atom feed
From: Purendra Singh <purendra.singh@nxp.com>
To: linux-bluetooth@vger.kernel.org
Cc: devyani.godbole@nxp.com, nitin.jadhav@nxp.com,
	luiz.dentz@gmail.com, pmenzel@molgen.mpg.de,
	purendra.singh@nxp.com
Subject: [PATCH BlueZ v2 1/1] gobex/gobex.c : Increase default obex timeout from 10 sec to 500 sec
Date: Fri, 20 Oct 2023 12:37:16 +0300	[thread overview]
Message-ID: <20231020093716.9654-2-purendra.singh@nxp.com> (raw)
In-Reply-To: <20231020093716.9654-1-purendra.singh@nxp.com>

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
observed.
---
 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
-- 
2.34.1


  reply	other threads:[~2023-10-20  9:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20  9:37 [PATCH BlueZ v2 0/1] Increase default obex timeout: 10 sec to 500 sec Purendra Singh
2023-10-20  9:37 ` Purendra Singh [this message]
2023-10-20  9:44   ` [PATCH BlueZ v2 1/1] gobex/gobex.c : Increase default obex timeout from " Paul Menzel
2023-10-20 17:49     ` Luiz Augusto von Dentz
2023-10-31 12:10       ` [EXT] " Purendra Singh
2023-10-20 11:15   ` Increase default obex timeout: " bluez.test.bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231020093716.9654-2-purendra.singh@nxp.com \
    --to=purendra.singh@nxp.com \
    --cc=devyani.godbole@nxp.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=nitin.jadhav@nxp.com \
    --cc=pmenzel@molgen.mpg.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.