From: Szymon Janc <ext.szymon.janc@tieto.com>
To: krishnaks@iwavesystems.com
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: GATT onWriteCharacteristic() returns status=1 (BT_STATUS_FAIL)
Date: Mon, 21 Sep 2015 13:02:49 +0200 [thread overview]
Message-ID: <2859057.ul7JxHffdl@leonov> (raw)
In-Reply-To: <ffcbfaab275d957cf387eb690b6a81ea.squirrel@iwavesystems.com>
Hi,
On Monday 21 of September 2015 06:43:20 krishnaks@iwavesystems.com wrote:
> Hi,
>
> I am using Bluez 5.33 on Android kitkat 4.4.3.
> I am testing GATT functionality and I found that sometime
> onWriteCharacteristic returns status 1 (BT_STATUS_FAIL). In android
> Application I am checking for success status (i.e. 0) which I am getting
> most of the time. But occasionally I am getting Status 1 because of which
> my application logic is failing.
>
> When Bluez will send Status 1 and on what basis? How to avoid this?
>
>
> -----------------------Working Log-------------------------------
> D/BluetoothGatt( 1359): writeCharacteristic() - uuid:
> 1d4de0a0-9f84-11e4-a042-0002a5d5c51b
> D/BtGatt.GattService( 1259): writeCharacteristic() -
> address=00:00:39:36:85:2F
> D/BtGatt.GattService( 1259): onWriteCharacteristic() -
> address=00:00:39:36:85:2F, status=0
> D/BluetoothGatt( 1359): onCharacteristicWrite() - Device=00:00:39:36:85:2F
> UUID=1d4de0a0-9f84-11e4-a042-0002a5d5c51b Status=0
> ----------------------Log End-------------------------
>
>
> --------------------------Failure Log---------------------------------
> D/BluetoothGatt( 1359): writeCharacteristic() - uuid:
> 1d4de0a0-9f84-11e4-a042-0002a5d5c51b
> D/BtGatt.GattService( 1259): writeCharacteristic() -
> address=00:00:39:36:85:2F
> D/BtGatt.GattService( 1259): onWriteCharacteristic() -
> address=00:00:39:36:85:2F, status=1
> D/BluetoothGatt( 1359): onCharacteristicWrite() - Device=00:00:39:36:85:2F
> UUID=1d4de0a0-9f84-11e4-a042-0002a5d5c51b Status=1
> --------------------------Log End-------------------------------
Please enable debug logs for daemon (check android/README for how-to) and
provide both debug logs and btmon HCI traces.
--
BR
Szymon Janc
next prev parent reply other threads:[~2015-09-21 11:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 13:31 USB BT gives problem If device plugged during boot to platform krishnaks
2015-08-28 19:07 ` Marcel Holtmann
2015-08-31 7:13 ` krishnaks
2015-09-02 12:24 ` StartLescan rerturns false krishnaks
2015-09-03 14:00 ` krishnaks
2015-09-03 14:25 ` Szymon Janc
2015-09-04 12:45 ` krishnaks
2015-09-21 10:43 ` GATT onWriteCharacteristic() returns status=1 (BT_STATUS_FAIL) krishnaks
2015-09-21 11:02 ` Szymon Janc [this message]
[not found] ` <71b8da83b60d4739a7cf443599cf4b3f.squirrel@iwavesystems.com>
2015-09-22 5:13 ` krishnaks
2015-09-22 10:26 ` Luiz Augusto von Dentz
2015-09-22 10:59 ` krishnaks
2015-09-23 11:06 ` krishnaks
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=2859057.ul7JxHffdl@leonov \
--to=ext.szymon.janc@tieto.com \
--cc=krishnaks@iwavesystems.com \
--cc=linux-bluetooth@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).