Merge lp:~seb128/ubuntu-system-settings/bluetooth-device-visibility-tweak into lp:ubuntu-system-settings
| Status: | Merged |
|---|---|
| Approved by: | Ricardo Salveti on 2015-03-06 |
| Approved revision: | 1316 |
| Merged at revision: | 1344 |
| Proposed branch: | lp:~seb128/ubuntu-system-settings/bluetooth-device-visibility-tweak |
| Merge into: | lp:ubuntu-system-settings |
| Diff against target: |
75 lines (+25/-1) 4 files modified
plugins/bluetooth/PageComponent.qml (+18/-0) plugins/bluetooth/bluetooth.cpp (+5/-0) plugins/bluetooth/bluetooth.h (+1/-0) plugins/bluetooth/devicemodel.h (+1/-1) |
| To merge this branch: | bzr merge lp:~seb128/ubuntu-system-settings/bluetooth-device-visibility-tweak |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Ricardo Salveti (community) | Approve on 2015-03-06 | ||
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-02-25 | |
| Ken VanDine | 2015-02-18 | Needs Information on 2015-02-20 | |
|
Review via email:
|
|||
Commit Message
bluetooth: disable device visiblity when switching out, that way it's not
staying on if the settings are closed from the switcher or if the user switch
to another software
Description of the Change
bluetooth: disable device visiblity when switching out, that way it's not
staying on if the settings are closed from the switcher or if the user switch
to another software
| Ken VanDine (ken-vandine) wrote : | # |
Do we really want to make it discoverable regardless of the previous state?
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:1313
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 1314. By Sebastien Bacher on 2015-02-25
-
rebase on trunk
- 1315. By Sebastien Bacher on 2015-02-25
-
delay the start by a second as described on the spec
| Sebastien Bacher (seb128) wrote : | # |
> Do we really want to make it discoverable regardless of the previous state?
The specification states it should be made discoverable when the view is open, so yes? I've pushed a small update to delay the start by 1s since that's what the spec describes
- 1316. By Sebastien Bacher on 2015-02-25
-
revert buggy rebase change
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1315
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1316
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Ricardo Salveti (rsalveti) wrote : | # |
This is still not going to fix the case when the app gets closed before getting suspended.
Same happens if you kill the app.
I think the proper implementation here would be to set a timeout when making the device visible, and only trigger it again (after the timeout) if the bt screen is opened.
| Ricardo Salveti (rsalveti) wrote : | # |
Silo available at https:/
| Ricardo Mendoza (ricmm) wrote : | # |
For this, you could use the DiscoverableTimeout property of bluez, just set it to something reasonable and have a way for the user to make it discoverable again.
Short of this, I don't know how much we can do about the app being closed / crashing case. It's always safer to have the timeout, even if you'd like to make it a 5 minutes one.
| Ricardo Mendoza (ricmm) wrote : | # |
Of course, the timeout being in addition to whats already provided by this MR. The timeout is only to safeguard against the closing/crashing case if it happens while the app is in focus.
| Ricardo Salveti (rsalveti) wrote : | # |
Yeah, after talking over IRC and looking to understand why the default timeout in bluez was 0, it's clear that it should be fixed there instead (which was fixed already in upstream).
So pushed a new bluez in the same silo to change the default timeout value.


FAILED: Continuous integration, rev:1313 jenkins. qa.ubuntu. com/job/ ubuntu- system- settings- ci/1975/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- vivid-touch/ 1408 jenkins. qa.ubuntu. com/job/ ubuntu- system- settings- vivid-i386- ci/245 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- vivid-mako/ 1245 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 1406 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 1406/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 18143
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/ubuntu- system- settings- ci/1975/ rebuild
http://