[Dx-packages] [Bug 1420169] Re: Alarms don't wake up the phone when it is powered off
** Changed in: canonical-devices-system-image Assignee: John McAleely (john.mcaleely) => (unassigned) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1420169 Title: Alarms don't wake up the phone when it is powered off Status in Canonical System Image: Confirmed Status in indicator-datetime package in Ubuntu: Invalid Status in platform-api package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Bug description: The alarms API is not setting the device's RTC alarm to power on the phone when an alarm should ring and the device is powered off. This causes alarms to be lost. We are instead using Android's /dev/alarm interface which only works while the phone is on or suspended. See bug #1375855 which confirms this works on Android. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420169/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices
** Changed in: indicator-bluetooth (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: canonical-pocket-desktop Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: Fix Committed Status in Canonical System Image: Fix Committed Status in Canonical Pocket Desktop: Fix Committed Status in indicator-bluetooth package in Ubuntu: Fix Committed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices
I think it will be helpful to have a short new bug for this discussion, so I've opened: bug #1587366. Please continue the discussion there. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: Fix Committed Status in Canonical System Image: Fix Committed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices
** Changed in: avila Milestone: ww04-2016 => ww06-2016 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: In Progress Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices
This in silo 79 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: In Progress Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices
Is the linked branch believed to be a fix, or simply part of the puzzle? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: In Progress Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices
** Changed in: avila Assignee: (unassigned) => Alejandro J. Cura (alecu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: Confirmed Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices
** Changed in: avila Milestone: ww06-2016 => ww04-2016 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: Confirmed Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices
** Changed in: indicator-bluetooth (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: Confirmed Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: In Progress Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices
** Changed in: avila Status: Confirmed => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: In Progress Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices
This also occurs on frieza, OEM bug: #1534318 ** Changed in: canonical-devices-system-image Importance: High => Critical -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: Confirmed Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1530807] Re: Bluetooth cannot be activated on Nexus 7
** Also affects: avila Importance: Undecided Status: New ** Summary changed: - Bluetooth cannot be activated on Nexus 7 + Bluetooth cannot be activated on several devices ** Changed in: avila Status: New => Confirmed ** Changed in: avila Importance: Undecided => Critical ** Changed in: avila Milestone: None => ww06-2016 ** Changed in: canonical-devices-system-image Milestone: None => ww08-2016 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: Confirmed Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices
Additional OEM bug that's probably a dupe: bug #1544084 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: Confirmed Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1488569] Re: MPRIS controls don't reflect the current player state
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Alejandro J. Cura (alecu) ** Changed in: canonical-devices-system-image Milestone: None => ww40-2015 ** Changed in: canonical-devices-system-image Importance: Undecided => Critical -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1488569 Title: MPRIS controls don't reflect the current player state Status in Canonical System Image: New Status in indicator-sound package in Ubuntu: New Bug description: The MPRIS controls (play/pause, next, previous) should reflect the current state of the current media player in media-hub. The following are what I would expect: 1. When media-hub reports that CanGoNext/Previous are false, the next and previous buttons in the indicator are disabled and visually greyed out or something to this effect. 2. The play button should show when media-hub reports that the current player is stopped or pause. 3. The pause button should show instead of the play button when media- hub reports that the current player is playing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488569/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1373313] Re: Media Hub not exporting MPRIS controls
OK, so we've broken out the indicator work into bug #1488569. Landing the MPRIS controls is stalled until that bug is fixed. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1373313 Title: Media Hub not exporting MPRIS controls Status in Canonical System Image: In Progress Status in Ubuntu Music App: Invalid Status in indicator-sound package in Ubuntu: In Progress Status in media-hub package in Ubuntu: Fix Committed Bug description: Pressing the previous or next button in the indicator sound menu does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373313/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1488569] Re: MPRIS controls don't reflect the current player state
I understand the fixes for this bug belong in silo 55 for testing with the media-hub changes -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1488569 Title: MPRIS controls don't reflect the current player state Status in Canonical System Image: New Status in Ubuntu UX: New Status in indicator-sound package in Ubuntu: New Bug description: The MPRIS controls (play/pause, next, previous) should reflect the current state of the current media player in media-hub. The following are what I would expect: 1. When media-hub reports that CanGoNext/Previous are false, the next and previous buttons in the indicator are disabled and visually greyed out or something to this effect. 2. The play button should show when media-hub reports that the current player is stopped or pause. 3. The pause button should show instead of the play button when media- hub reports that the current player is playing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488569/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1488569] Re: MPRIS controls don't reflect the current player state
This bug blocks bug #1373313 from landing. ** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1488569 Title: MPRIS controls don't reflect the current player state Status in Canonical System Image: New Status in Ubuntu UX: New Status in indicator-sound package in Ubuntu: New Bug description: The MPRIS controls (play/pause, next, previous) should reflect the current state of the current media player in media-hub. The following are what I would expect: 1. When media-hub reports that CanGoNext/Previous are false, the next and previous buttons in the indicator are disabled and visually greyed out or something to this effect. 2. The play button should show when media-hub reports that the current player is stopped or pause. 3. The pause button should show instead of the play button when media- hub reports that the current player is playing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488569/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1367818] Re: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state.
please open a new bug, rather than commenting on a long-closed one. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1367818 Title: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state. Status in Canonical System Image: Fix Released Status in Ubuntu UX: Fix Committed Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu RTM: Fix Released Bug description: - "When the sound is muted, the volume icon to the left of the volume slider should have a red "/" running through it." - "Add an explicit "Mute" button to the sound indicator menu." - "Pressing and holding the icon to the left of the volume slider should mute volume straight away." -- Desired resolution: Once the sound is muted icon should change but not the colour. We have an icon for muted https://www.dropbox.com/work/Apps%20and%20Platform%20Team/9.%20Icons/Suru%20Icon%20Theme/status/81?preview=volume-min.png The behaviour has already been illustrated by MPT To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1367818/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1481913] Re: UI volume warnings need revision
Thanks alecu - it seems that the code moved on in the second branch, and my experiment suggests the key in question is: com.canonical.indicator.sound warning-volume-decibels If I set this to -16.0 (the default is -8.0) the warning appears around the 50% mark of the indicator. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1481913 Title: UI volume warnings need revision Status in Canonical System Image: Fix Committed Status in indicator-sound package in Ubuntu: Fix Released Bug description: As raised in OEM bug #1474364 (the title there is poor), the warning scheme used by Ubuntu does not currently follow the letter of the EU regulations for mobile devices (it seems to follow the spirit). Design have now reviewed the regulations (bug #1480912), and propose: https://wiki.ubuntu.com/Sound#limits This is the diff: https://wiki.ubuntu.com/Sound?action=diffrev2=146rev1=145 The UI notification scheme needs to be updated to match the new design. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481913/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1373313] Re: Media Hub not exporting MPRIS controls
** Changed in: canonical-devices-system-image Milestone: ww34-2015 = ww40-2015 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1373313 Title: Media Hub not exporting MPRIS controls Status in Canonical System Image: In Progress Status in Ubuntu Music App: Invalid Status in indicator-sound package in Ubuntu: Confirmed Status in media-hub package in Ubuntu: In Progress Bug description: Pressing the previous or next button in the indicator sound menu does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373313/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1481913] Re: UI volume warnings need revision
In extremis, if we can't adjust the driver sucessfully, what value should be modified to move the level at which the warning UI appears? I would like to confirm that if I get the warnings to appear at the 50% point on the indicator slider, we do conform to the regulations (ie that point matches the required output dB/mV). -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1481913 Title: UI volume warnings need revision Status in Canonical System Image: Fix Committed Status in indicator-sound package in Ubuntu: Fix Released Bug description: As raised in OEM bug #1474364 (the title there is poor), the warning scheme used by Ubuntu does not currently follow the letter of the EU regulations for mobile devices (it seems to follow the spirit). Design have now reviewed the regulations (bug #1480912), and propose: https://wiki.ubuntu.com/Sound#limits This is the diff: https://wiki.ubuntu.com/Sound?action=diffrev2=146rev1=145 The UI notification scheme needs to be updated to match the new design. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481913/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1373313] Re: Media Hub not exporting MPRIS controls
@jim, does this one close when silo48 lands? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1373313 Title: Media Hub not exporting MPRIS controls Status in Canonical System Image: In Progress Status in Ubuntu Music App: Invalid Status in indicator-sound package in Ubuntu: Confirmed Status in media-hub package in Ubuntu: In Progress Bug description: Pressing the previous or next button in the indicator sound menu does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373313/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1481913] Re: UI volume warnings need revision
** Tags added: audio -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1481913 Title: UI volume warnings need revision Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Confirmed Bug description: As raised in OEM bug #1474364 (the title there is poor), the warning scheme used by Ubuntu does not currently follow the letter of the EU regulations for mobile devices (it seems to follow the spirit). Design have now reviewed the regulations (bug #1480912), and propose: https://wiki.ubuntu.com/Sound#limits This is the diff: https://wiki.ubuntu.com/Sound?action=diffrev2=146rev1=145 The UI notification scheme needs to be updated to match the new design. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481913/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1465806] Re: Alarms not shown in indicator datetime after upgrade to ota4
@pmcgowan, is this in vivid-overlay? It's hard to tell from the bug text -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1465806 Title: Alarms not shown in indicator datetime after upgrade to ota4 Status in the base for Ubuntu mobile products: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Status in indicator-datetime source package in Vivid: New Bug description: STEPS: 1. Flash image 22 from stable 2. Set a one time alarm and a recurring alarm 3. Update to 23 EXPECTED: Alarms should be up and running as expected ACTUAL: Alarms are not shown in the datetime indicator but show up as active in and available in the clock. Because the indicator is in control of the alarm trigger the alarm never goes off. TEMPORARY WORK AROUND: Disable and enable all your alarms and then they work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1465806/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1373313] Re: Media Hub not exporting MPRIS controls
so, are the changes to the controls in #8 something we need before progressing media-hub? ** Changed in: canonical-devices-system-image Assignee: (unassigned) = John McAleely (john.mcaleely) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1373313 Title: Media Hub not exporting MPRIS controls Status in the base for Ubuntu mobile products: Confirmed Status in Media Hub: Triaged Status in Music application for Ubuntu devices: Invalid Status in indicator-sound package in Ubuntu: Confirmed Bug description: Pressing the previous or next button in the indicator sound menu does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373313/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness
That info seemed to belong on askubuntu: http://askubuntu.com/questions/609938/how-do-i-factory-reset-a-bq- aquaris-e4-5-ubuntu-edition-from-the-handset -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in the base for Ubuntu mobile products: Fix Released Status in indicator-power package in Ubuntu: Invalid Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness
Even if the OTA goes live, I'm not sure how you might get it on a phone if you can't interact with it. You have two choices: - update the phone manually from an attached ubuntu desktop - Use the handset's factory reset proceedure. The first is well covered by our developer documentation. Simply reflashing to the current image with --wipe will reset the brightness to a sensible value (and wipe all your other data) The second would be hold down 'volup' + power. When the machine starts rebooting (~10 sec) a red led lights, and you should release just the power button. You will eventually be presented with a menu. follow the on-screen instructions to select recovery. When the ubuntu logo appears, use 'Volup' again to get a menu of options. One of which is 'factory reset'. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in the base for Ubuntu mobile products: Fix Released Status in indicator-power package in Ubuntu: Invalid Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness
Exactly what it says, which is perhaps not helpful :-) The cache partition is used for downloads, etc which are in your browser (and other) caches. It should contain only transient data. One notable data type stored here are OTA updates before they are installed. In your case, I don't imagine resetting it will change anything. On 16 April 2015 at 11:01, Joseph Wakeling j...@webdrake.net wrote: @John -- thanks very much for the feedback. One question: what does the wipe cache partition option mean (as opposed to the factory reset, which is obvious)? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in the base for Ubuntu mobile products: Fix Released Status in indicator-power package in Ubuntu: Invalid Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+subscriptions -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in the base for Ubuntu mobile products: Fix Released Status in indicator-power package in Ubuntu: Invalid Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1367818] Re: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state.
@pat, what is the behaviour we should see, since it seems not to be the exactly requested behaviour in the bug description. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1367818 Title: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state. Status in the base for Ubuntu mobile products: Fix Released Status in Ubuntu UX bugs: Triaged Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu RTM: Fix Released Bug description: - When the sound is muted, the volume icon to the left of the volume slider should have a red / running through it. - Add an explicit Mute button to the sound indicator menu. - Pressing and holding the icon to the left of the volume slider should mute volume straight away. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1367818/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1367818] Re: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state.
@pmcgowan I note that the UX task is still triaged. On the OTA3 image, you get a little cross for 'silent mode' next to the indicator. For the volume OSD, the visual language is different, where as you take the volume down to zero, you get a cross. Which is confusing. @patty davilla, is there still work to be done in this area, or is your task in need of an update. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1367818 Title: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state. Status in the base for Ubuntu mobile products: Fix Released Status in Ubuntu UX bugs: Triaged Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu RTM: Fix Released Bug description: - When the sound is muted, the volume icon to the left of the volume slider should have a red / running through it. - Add an explicit Mute button to the sound indicator menu. - Pressing and holding the icon to the left of the volume slider should mute volume straight away. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1367818/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness
@pat, please can you triage this onto a milestone, so I know where to land it. Thanks. ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in the base for Ubuntu mobile products: New Status in indicator-power package in Ubuntu: Incomplete Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness
I just tried the same kind of proto handset rsalveti mentioned side by side with a production Ubuntu edition device. Both devices appeared to still show a (dim) backlight at the lowest setting the UI allowed. I could see that the screen backlight went all the way off when the device was turned off with the power button. Is there some other step (setting auto brightness, tweaking something else?) we need to do to see the effect you observe? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in indicator-power package in Ubuntu: Incomplete Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1436538/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1409696] Re: There is no 'headset' icon in the indicator bar when a headset is connected
@Noemi - the status indicates it is still under discussion. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1409696 Title: There is no 'headset' icon in the indicator bar when a headset is connected Status in Ubuntu UX bugs: Triaged Status in indicator-sound package in Ubuntu: Incomplete Bug description: Reported by an OEM who's phone currently does have such an icon, there is no visual indication that a wired headset has been connected to the phone and in use: [Procedures] 1.insert the earphone [Expect results] should be has earphone icon and notification shows in Status Bar [Actual results] There is no earphone icon in indicator Bar when inserting the earphone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1409696/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1367818] Re: Silent Mode causes no indication of a change in [icon] state.
Can this be triaged onto a milestone for canonical-device-system image? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1367818 Title: Silent Mode causes no indication of a change in [icon] state. Status in the base for Ubuntu mobile products: New Status in indicator-sound package in Ubuntu: Triaged Bug description: - When the sound is muted, the volume icon to the left of the volume slider should have a red / running through it. - Add an explicit Mute button to the sound indicator menu. - Pressing and holding the icon to the left of the volume slider should mute volume straight away. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1367818/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1394105] Re: Sometimes significant lag between snap dialog and ringtone start
** Package changed: telepathy-ofono (Ubuntu) = canonical-devices- system-image -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1394105 Title: Sometimes significant lag between snap dialog and ringtone start Status in the base for Ubuntu mobile products: New Status in indicator-messages package in Ubuntu: Invalid Status in ofono package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r140 krillin When testing a large number of phone calls it could be seen that on certain calls there would be a significant delay between the snap decision dialog being displayed and the ringtone beginning to play. In extreme circumstances this could cause calls to be missed as there would not be enough time to answer. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394105/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1394105] Re: Sometimes significant lag between snap dialog and ringtone start
@toykeeper - can you get the logs rsalveti requests? ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) = Selene Scriven (toykeeper) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1394105 Title: Sometimes significant lag between snap dialog and ringtone start Status in “indicator-messages” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: New Status in “pulseaudio” package in Ubuntu: Incomplete Status in “telepathy-ofono” package in Ubuntu: New Bug description: Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r140 krillin When testing a large number of phone calls it could be seen that on certain calls there would be a significant delay between the snap decision dialog being displayed and the ringtone beginning to play. In extreme circumstances this could cause calls to be missed as there would not be enough time to answer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1394105/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1296431] Re: Phone doesn't alert user of critical power situations
Not sure how this bug should be tagged, but I assume this is in scope for RTM? (Note duplicate bugs) ** Tags added: rtm14 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1296431 Title: Phone doesn't alert user of critical power situations Status in “indicator-power” package in Ubuntu: In Progress Bug description: The phone doesn't currently alert the user when the battery is critical. This leads to power loss at times and the user doesn't know it's about to happen or had happened. e.g. during a call, or while listening to music. Also if the phone is sat on the desk unplugged from power connection. https://wiki.ubuntu.com/Power#Warnings: When the device’s battery/batteries are discharging and reach — or begin discharging and already have — 1 hour or less remaining (PC) or 20% or less remaining (phone/tablet), a notification bubble should appear ... When the device’s battery/batteries are discharging and reach — or begin discharging and already have — 30 minutes or less remaining (PC) or 10% or less remaining (phone/tablet), an alert should appear... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1296431/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1358293] Re: Turning off Bluetooth in the Indicator Crashes the Phone
** Also affects: indicator-bluetooth
Importance: Undecided
Status: New
** No longer affects: indicator-bluetooth
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1358293
Title:
Turning off Bluetooth in the Indicator Crashes the Phone
Status in “indicator-bluetooth” package in Ubuntu:
Confirmed
Bug description:
Steps:
1. Enable a bluetooth headset or earbuds
2. Start the music player and play an album
3. Confirm that the music is playing
4. Turn off the screen and listen to the music for a few tracks
5. Turn on the screen and pause the music player
6. Pull down the indicator and try to disable bluetooth
The indicator freezes for a time, then the whole phone reboots
root@ubuntu-phablet:/# cat /proc/last_kmsg
ram console header, hw_status: 2, fiq step 40.
bin log 0.
x104) from [c07e9958] (dump_stack+0x20/0x24)
[ 1164.156265] (1)[2070:unity8][c07e9958] (dump_stack+0x20/0x24) from
[c0014238] (handle_IPI+0x21c/0x250)
[ 1164.157473] (1)[2070:unity8][c0014238] (handle_IPI+0x21c/0x250) from
[c00085bc] (do_IPI+0x18/0x1c)
[ 1164.158638] (1)[2070:unity8][c00085bc] (do_IPI+0x18/0x1c) from
[c07fa0d4] (__irq_usr+0x34/0xc0)
[ 1164.160851] (0)[2053:indicator-bluet]init emmc for ipanic dump
[ 1164.175534] (0)[2053:indicator-bluet][pll]0xF020924C = 0x8001
[ 1164.176285] (0)[2053:indicator-bluet][pll]0xF0209240 = 0x121
[ 1164.176992] (0)[2053:indicator-bluet][mux] 0xF060 = 0x1818100
[ 1164.177749] (0)[2053:indicator-bluet][mux] 0xF070 = 0x81808101
[ 1164.178519] (0)[2053:indicator-bluet][clk] 0xF0003010 = 0x0
[ 1164.179213] (0)[2053:indicator-bluet][clk] 0xF0003018 = 0x2fecffd
[ 1164.180068] (0)[2053:indicator-bluet]send cmd0
[ 1164.184692] (0)[2053:indicator-bluet]cmd1: resp(0xff8080), i=500
[ 1164.185430] (0)[2053:indicator-bluet]send cmd0
[ 1164.213984] (0)[2053:indicator-bluet]cmd1: resp(0xc0ff8080), i=498
[ 1164.216746] (0)[2053:indicator-bluet]resp: 0x11010030 0x30384739
0x32009acc 0xa9373149
[ 1164.240817] (0)[2053:indicator-bluet]read fifo done, wait xfer_compl
interrupt
[ 1164.241712] (0)[2053:indicator-bluet]emmc offset (0x5c00)
[ 1164.244389] (0)[2053:indicator-bluet]init eMMC success
[ 1167.466826] (0)[2053:indicator-bluet]card_dump_func_write failed (18),
size: 0x58000
[ 1167.467803] (0)[2053:indicator-bluet]CPU: 0Tainted: GW
(3.4.67 #1)
[ 1167.468745] (0)[2053:indicator-bluet]PC is at l2cap_chan_destroy+0x3c/0x88
[ 1167.469599] (0)[2053:indicator-bluet]LR is at __raw_write_lock+0x34/0xa8
[ 1167.470437] (0)[2053:indicator-bluet]pc : [c07a6adc]lr :
[c07f9b74]psr: 600f0013
[ 1167.470444] (0)[2053:indicator-bluet]sp : d8897d68 ip : 00100100 fp :
d8897d7c
[ 1167.472412] (0)[2053:indicator-bluet]r10: cc583a20 r9 : cf9db800 r8 :
c74e1300
[ 1167.473335] (0)[2053:indicator-bluet]r7 : 0067 r6 : c74e13bc r5 :
cc58380c r4 : cc583800
[ 1167.474419] (0)[2053:indicator-bluet]r3 : 00200200 r2 : 00100100 r1 :
00200200 r0 : c1128f40
[ 1167.475505] (0)[2053:indicator-bluet]Flags: nZCv IRQs on FIQs on Mode
SVC_32 ISA ARM Segment user
[ 1167.476664] (0)[2053:indicator-bluet]Control: 10c5387d Table: 8ddd806a
DAC: 0015
[ 1167.480769] (0)[2053:indicator-bluet]Process indicator-bluet (pid: 2053,
stack limit = 0xd8896300)
[ 1167.481881] (0)[2053:indicator-bluet]Stack: (0xd8897d68 to 0xd8898000)
[ 1167.482697] (0)[2053:indicator-bluet]7d60: 0009
cf548400 d8897d94 d8897d80 c07ac5b8 c07a6aac
[ 1167.483989] (0)[2053:indicator-bluet]7d80: 0002 cc583800 d8897da4
d8897d98 c07ac690 c07ac580 d8897ddc d8897da8
[ 1167.485279] (0)[2053:indicator-bluet]7da0: c07a2fc8 c07ac684 c74e13c4
d00bf400 d8897ddc d00bf400 d6dd6d00 d6dd6d00
[ 1167.486570] (0)[2053:indicator-bluet]7dc0: 0009 d6dd6808 d8897f78
d6dd6828 d8897df4 d8897de0 c07aa9dc c07a2f0c
[ 1167.487861] (0)[2053:indicator-bluet]7de0: d6dd6cec d00bf400 d8897e14
d8897df8 c0793444 c07aa9bc d6dd6800 d6dd6ecc
[ 1167.489151] (0)[2053:indicator-bluet]7e00: 0008 d6dd6ca0 d8897e4c
d8897e18 c078ee50 c07933a8 d8897e34 c07f9818
[ 1167.490442] (0)[2053:indicator-bluet]7e20: d8897e4c dbdb7600 0001
0008 d883e0c0 0008 d8897f78 be9d7e48
[ 1167.491733] (0)[2053:indicator-bluet]7e40: d8897e5c d8897e50 c078f094
c078ed90 d8897e74 d8897e60 c07e270c c078f080
[ 1167.493023] (0)[2053:indicator-bluet]7e60: dbdb7600 c0c59bb0 d8897e9c
d8897e78 c07e288c c07e2688 00010302
[ 1167.494314] (0)[2053:indicator-bluet]7e80: d883e0c0 0008 c07e2774
d8896000 d8897f6c d8897ea0 c0147b30 c07e2780
[ 1167.495605] (0)[2053:indicator-bluet]7ea0: d8896000 d9f1ed04 d8897ec4
d8897eb8 c07f98b0 c07f932c d8897ed4 d8897ec8
[ 1167.496895] (0)[2053:indicator-bluet]7ec0: c09abcb8 c09abcc4 c09abcd0
