From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 22 Jul 2012 12:11:02 +0300 Message-ID: Subject: Re: AVRCPv1.3 NOTIFY from CT per notification from TG From: "Von Dentz, Luiz" To: Pavan Savoy Cc: Lucas De Marchi , linux-bluetooth@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Pavan On Sun, Jul 22, 2012 at 5:07 AM, Pavan Savoy wrote: > Now, I am interested to know whether the "Playing" needs to be > displayed or something like "Paused" along with another bit of info, > which is My-Song. > So, say to begin with I register for track-changed notification, now > to read the attributes of song again, but If I have to display > "Paused" then I will have to register for "Play Status" & I can get > only 1 of them at a time ? You can register multiple events simultaneously, the only problem is that you need to register again every time it changes. Apparently this idea of registration not being persistent came from AV/C spec, while doing support for VolumeChanged event I actually step in it see patch: AVRCP: Fix not registering to VolumeChanged event again when notified Its pretty broken design if you ask me, but one that we have to live with...