From: Pavel Nikulin <firstname.lastname@example.org> To: Luiz Augusto von Dentz <email@example.com> Cc: Bruno Randolf <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org> Subject: Re: bluetoothd: Please don't filter UUIDs Date: Fri, 11 Oct 2019 16:12:18 +0600 Message-ID: <CAG-pW8Ev_ntv1=o0ndd_2FXTdbsvHJ=FVsB-YXUucVtyKSO0Sg@mail.gmail.com> (raw) In-Reply-To: <CABBYNZKUmctzTRxix9P-FBK=15v01tkHWMCirFefStpCS2ukBQ@mail.gmail.com> Hello On Wed, Oct 9, 2019 at 7:35 PM Luiz Augusto von Dentz <email@example.com> wrote: > Right, so I assume then every application interested on battery would > then attempt to subscribe for the battery level on the own instead of > using org.bluez.Battery1? Either way that would be done via D-Bus but > dealing with a characteristic seem quite a bit more expensive not to > mention is another object the daemon has to maintain. There is an issue with org.bluez.Battery1 currently that I wrote to linux-bluetooth about a week ago. The quickest solution other than leaving it to client programs would be to fix the battery plugin. As of now, it doesn't seem to support a use case where you have battery service, but no battery attribute. Also, HFP/HSP own battery level indication mechanism doesn't seem to be implemented at all. I contacted the original contributor of LE code for org.bluez.Battery1, but he said he is no longer involved with that.
next prev parent reply index Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-01 16:32 Bruno Randolf 2019-10-03 13:04 ` Luiz Augusto von Dentz 2019-10-09 13:09 ` Bruno Randolf 2019-10-09 13:34 ` Luiz Augusto von Dentz 2019-10-11 10:12 ` Pavel Nikulin [this message] 2019-10-18 9:21 ` Bruno Randolf
Reply instructions: You may reply publically 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='CAG-pW8Ev_ntv1=o0ndd_2FXTdbsvHJ=FVsB-YXUucVtyKSO0Sg@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /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
Linux-Bluetooth Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-bluetooth/0 linux-bluetooth/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-bluetooth linux-bluetooth/ https://lore.kernel.org/linux-bluetooth \ firstname.lastname@example.org email@example.com public-inbox-index linux-bluetooth Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-bluetooth AGPL code for this site: git clone https://public-inbox.org/ public-inbox