Closed Bug 1111976 Opened 10 years ago Closed 8 years ago

Enable/Disable Bluetooth Snoop log from Settings Developer Menu debugging options

Categories

(Firefox OS Graveyard :: Bluetooth, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.0 affected, b2g-v2.0M fixed, b2g-v2.1 affected, b2g-v2.1S affected, b2g-v2.2 affected, b2g-master affected)

RESOLVED WONTFIX
Tracking Status
b2g-v2.0 --- affected
b2g-v2.0M --- fixed
b2g-v2.1 --- affected
b2g-v2.1S --- affected
b2g-v2.2 --- affected
b2g-master --- affected

People

(Reporter: shawnjohnjr, Assigned: shawnjohnjr)

References

Details

Attachments

(1 file, 4 obsolete files)

Enable/Disable Bluetooth Snoop log from Settings
This bug is public and general bug, not only 2.0m+ bug.
blocking-b2g: --- → 2.0M?
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Attachment #8540000 - Flags: review?(btian)
Attachment #8540000 - Flags: feedback?(jaliu)
Attachment #8540000 - Attachment is obsolete: true
Attachment #8540000 - Flags: review?(btian)
Attachment #8540000 - Flags: feedback?(jaliu)
Comment on attachment 8540002 [details] [diff] [review] [2.0m] Bug 1111976 - Config Bluetooth snoop log from Developer menu Review of attachment 8540002 [details] [diff] [review]: ----------------------------------------------------------------- r=me with comment addressed. ::: dom/bluetooth/bluedroid/BluetoothServiceBluedroid.cpp @@ +1422,5 @@ > return sBtInterface; > } > > void > +BluetoothServiceBluedroid::ConfigHciDumpLog(bool aEnabled) { nit: newline for { @@ +1423,5 @@ > } > > void > +BluetoothServiceBluedroid::ConfigHciDumpLog(bool aEnabled) { > + if (sBtInterface) { Rewrite with guardian clause to reduce nested if: if (!sBtInterface) { // print log/warning msg } int ret = sBtInterface->config_hci_snoop_log(aEnabled); if (ret != BT_STATUS_SUCCESS) { BT_LOGR("Fail to ConfigHciDumpLog"); } @@ +1426,5 @@ > +BluetoothServiceBluedroid::ConfigHciDumpLog(bool aEnabled) { > + if (sBtInterface) { > + int ret = sBtInterface->config_hci_snoop_log(aEnabled); > + if (ret != BT_STATUS_SUCCESS) { > + BT_LOGR("Fail to ConfigHciDumpLog"); Print |aEnabled|. ::: dom/bluetooth/bluez/BluetoothDBusService.cpp @@ +2163,5 @@ > > +void > +BluetoothDBusService::ConfigHciDumpLog(bool aEnabled) > +{ > + // Only avaiable for BT HAL interface typo: avai'l'able ::: dom/bluetooth/bluez/BluetoothDBusService.h @@ +179,5 @@ > virtual nsresult > SendInputMessage(const nsAString& aDeviceAddresses, > const nsAString& aMessage) MOZ_OVERRIDE; > + > + virtual void ConfigHciDumpLog(bool aEnabled) MOZ_OVERRIDE; nit: newline after this line. ::: dom/bluetooth/ipc/BluetoothServiceChildProcess.cpp @@ +389,5 @@ > MOZ_CRASH("This should never be called!"); > } > > +void > +BluetoothServiceChildProcess::ConfigHciDumpLog(bool aEnabled) { nit: newline for {
Attachment #8540002 - Flags: review?(btian) → review+
Assignee: nobody → shuang
Blocks: Woodduck
blocking-b2g: 2.0M? → 2.0M+
m-c now is going to change a lot due to Bluetooth Daemon will be introduced in these two weeks, so i preferred to wait for that big patch get landed.
Sounds like it can land on v2.1 in the mean time? If so, please request approval for that at least.
Flags: needinfo?(shuang)
v2.1 also uses the new design, so I guess I will handle it for m-c only.
Flags: needinfo?(shuang)
Leave 2.1 decision to Steven.
blocking-b2g: 2.0M+ → 2.1S?
Flags: needinfo?(styang)
Need it for 2.1S
blocking-b2g: 2.1S? → 2.1S+
Flags: needinfo?(styang)
Comment on attachment 8540028 [details] [diff] [review] [2.0m] Bug 1111976 - Config Bluetooth snoop log from Developer menu, r=btian Review of attachment 8540028 [details] [diff] [review]: ----------------------------------------------------------------- ::: dom/bluetooth/BluetoothService.h @@ +359,5 @@ > /** > + * Enable/disable snoop log > + */ > + virtual void > + ConfigHciDumpLog(bool aEnabled) = 0; I'd like to suggest to call this method |ConfigHciSnoopLog|; here and everywhere else. That would be consistent with Bluedroid terminology.
(In reply to Thomas Zimmermann [:tzimmermann] [:tdz] from comment #15) > Comment on attachment 8540028 [details] [diff] [review] > [2.0m] Bug 1111976 - Config Bluetooth snoop log from Developer menu, r=btian > > Review of attachment 8540028 [details] [diff] [review]: > ----------------------------------------------------------------- > > ::: dom/bluetooth/BluetoothService.h > @@ +359,5 @@ > > /** > > + * Enable/disable snoop log > > + */ > > + virtual void > > + ConfigHciDumpLog(bool aEnabled) = 0; > > I'd like to suggest to call this method |ConfigHciSnoopLog|; here and > everywhere else. That would be consistent with Bluedroid terminology. Thanks, i will change it for m-c. We also need to check settings value for 'bluetooth.snoop.enabled' instead of 'bluetooth.debugging.enabled'
Shawn, do you still need this for 2.1S?
Flags: needinfo?(shuang)
(In reply to Steven Yang [:styang] from comment #17) > Shawn, do you still need this for 2.1S? Not really hard requirement now for v2.1+.
blocking-b2g: 2.1S+ → ---
Flags: needinfo?(shuang)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: