CyanogenMod
  1. CyanogenMod
  2. CYAN-20

Bluetooth AVRCP 1.3+ (needs porting from CM10 to CM10.1)

    Details

    • Type: New Feature New Feature
    • Status: Resolved Resolved
    • Priority: Normal Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Bluetooth
    • Labels:
      None
    • Model:
      a700, ace, anzu, aoba, aria, blade, bravo, bravoc, buzz, c660, c800, captivatemtd, cdma_droid2we, click, coconut, cooper, crespo, crespo4g, d2att, d2cri, d2mtr, d2spr, d2tmo, d2usc, d2vzw, desirec, doubleshot, droid2, droid2we, e400, e510, e720, e730, e739, encore, endeavoru, epicmtd, es209ra, espresso, everest, evita, fascinatemtd, galaxys2, galaxys2att, galaxysbmtd, galaxysmtd, glacier, grouper, haida, hallon, harmony, hercules, hero, heroc, hikari, holiday, i777, i9100, i9100g, i9300, inc, iyokan, jewel, jordan, jordan_plus, legend, liberty, maguro, mako, mango, mesmerizemtd, mimmi, mint, morrison, motus, n7000, n7100, n8000, n8013, nozomi, odroidu2, olympus, one, p1, p1c, p1l, p1n, p3, p3100, p3110, p3113, p350, p4, p4tmo, p4vzw, p4wifi, p5, p500, p51xx, p5wifi, p720, p920, p925, p930, p970, p990, p999, passion, pyramid, quincyatt, quincytmo, robyn, ruby, s5670, saga, satsuma, shadow, shakira, sholes, shooteru, showcasemtd, skate, skyrocket, smb_a1002, smultron, speedy, steelhead, stingray, su640, sunfire, supersonic, t0lte, t769, tass, tenderloin, tf101, tf201, tf300t, tf700t, tilapia, toro, toroplus, u8150, u8160, u8220, urushi, v9, vega, vibrantmtd, ville, vision, vivo, vivow, wingray, z71, zepplin, zero, zeus, zeusc

      Description

      This feature was well-implemented in CM10, but in CM10.1 has been reverted back to AOSP, which lacks a modern AVCRP Bluetooth profile to support functionality such as communicating audio track information to car stereos over bluetooth.

        Activity

        Hide
        Carl Quirion added a comment -

        I have tested this and it works (as supposed) on 10.2 nightlies (on SGH-i747m (d2att)). I think this JIRA is no longer needed as it is part of Android 4.3

        Show
        Carl Quirion added a comment - I have tested this and it works (as supposed) on 10.2 nightlies (on SGH-i747m (d2att)). I think this JIRA is no longer needed as it is part of Android 4.3
        Hide
        Julien STEPHAN added a comment -

        not fixed, not working as supposed on nexus 4

        Could you please change the status to not fixed ?

        thanks

        Show
        Julien STEPHAN added a comment - not fixed, not working as supposed on nexus 4 Could you please change the status to not fixed ? thanks
        Hide
        anthony thomas added a comment -

        Seems to work fine on mine now on 10.2

        Show
        anthony thomas added a comment - Seems to work fine on mine now on 10.2
        Hide
        Justin W added a comment -

        The topic of this ticket is pretty clearly, 'Bluetooth AVRCP 1.3+'. Android 4.3 only supports 1.2. I specifically signed up to follow this ticket to see when Cyanogen might get 1.3+ support, as that's what I'm looking for.

        Show
        Justin W added a comment - The topic of this ticket is pretty clearly, 'Bluetooth AVRCP 1.3+'. Android 4.3 only supports 1.2. I specifically signed up to follow this ticket to see when Cyanogen might get 1.3+ support, as that's what I'm looking for.
        Hide
        Carl Quirion added a comment - - edited

        http://www.android.com/about/jelly-bean/ says 1.3 and anything below 1.3 doesn't send metadata (track titles, etc) and i can confirm that i get them.
        Also, i've never heard of 1.2 ... 1.0 then 1.3, yes.
        1.4 does indeed looks interesting but as for the title of this JIRA, we do have 1.3 now.
        Granted it may not work on some devices ? (Those devices owner may want to start other jira...)

        Show
        Carl Quirion added a comment - - edited http://www.android.com/about/jelly-bean/ says 1.3 and anything below 1.3 doesn't send metadata (track titles, etc) and i can confirm that i get them. Also, i've never heard of 1.2 ... 1.0 then 1.3, yes. 1.4 does indeed looks interesting but as for the title of this JIRA, we do have 1.3 now. Granted it may not work on some devices ? (Those devices owner may want to start other jira...)

          People

          • Assignee:
            Unassigned
            Reporter:
            DA6030
          • Votes:
            73 Vote for this issue
            Watchers:
            72 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: