summaryrefslogtreecommitdiffstats
path: root/device
Commit message (Collapse)AuthorAgeFilesLines
* gfx: Create a separate gfx component out of ui.sadrul@chromium.org2013-09-301-0/+1
| | | | | | | | | | | Landed previously in r225857, which was reverted in r225859 because it broke android tests. BUG=103304 R=ben@chromium.org Review URL: https://codereview.chromium.org/25015003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225909 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 225857 "gfx: Create a separate gfx component out of ui."ckocagil@chromium.org2013-09-281-1/+0
| | | | | | | | | | | | | | | > gfx: Create a separate gfx component out of ui. > > BUG=103304 > R=ben@chromium.org > > Review URL: https://codereview.chromium.org/25015003 TBR=sadrul@chromium.org Review URL: https://codereview.chromium.org/25161002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225859 0039d316-1c4b-4281-b951-d872f2087c98
* gfx: Create a separate gfx component out of ui.sadrul@chromium.org2013-09-281-0/+1
| | | | | | | | | BUG=103304 R=ben@chromium.org Review URL: https://codereview.chromium.org/25015003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225857 0039d316-1c4b-4281-b951-d872f2087c98
* dbus: Replace PostTaskTo*Thread methods with Get*TaskRunnerhashimoto@chromium.org2013-09-261-2/+2
| | | | | | | | | | | | | By exposing TaskRunners, we'll be able to use utility functions like base::PostTaskAndReplyWithResult BUG=None TEST=git cl try R=satorux@chromium.org Review URL: https://codereview.chromium.org/24554002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225324 0039d316-1c4b-4281-b951-d872f2087c98
* Convert most run_all_unittests.cc files to use new unit test launcher.phajdan.jr@chromium.org2013-09-052-10/+1
| | | | | | | | | | | | | Note that the new code is still behind a runtime flag (--brave-new-test-launcher), but compiling tests with support for it will make further testing possible. BUG=236893, 79359 R=akalin@chromium.org, enne@chromium.org, erikwright@chromium.org, joi@chromium.org, keybuk@chromium.org, sky@chromium.org, thestig@chromium.org, tommi@chromium.org, wtc@chromium.org, xhwang@chromium.org, yzshen@chromium.org Review URL: https://codereview.chromium.org/23442019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221464 0039d316-1c4b-4281-b951-d872f2087c98
* There was a missing check to return the right record.etienneb@chromium.org2013-07-314-7/+25
| | | | | | | | | R=erikwright@chromium.org, youngki@chromium.org BUG= Review URL: https://chromiumcodereview.appspot.com/21089002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214751 0039d316-1c4b-4281-b951-d872f2087c98
* Use a direct include of the message_loop header in dbus/, device/, ↵avi@chromium.org2013-07-174-4/+4
| | | | | | | | | | | | extensions/, google_apis/, gpu/, ipc/, jingle/. BUG=260807 TEST=none TBR=ben@chromium.org Review URL: https://chromiumcodereview.appspot.com/19607005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212157 0039d316-1c4b-4281-b951-d872f2087c98
* device: Gyp organization part 3 - final.tfarina@chromium.org2013-07-051-0/+0
| | | | | | | | | | | Rename device.gyp to device_tests.gyp now that it only contain test targets. BUG=None R=bryeung@chromium.org, miket@chromium.org Review URL: https://codereview.chromium.org/18266002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@210256 0039d316-1c4b-4281-b951-d872f2087c98
* Taking ownership of USB related librariesikarienator@chromium.org2013-07-041-0/+1
| | | | | | | | BUG= Review URL: https://chromiumcodereview.appspot.com/18298006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@210240 0039d316-1c4b-4281-b951-d872f2087c98
* Use a direct include of time headers in courgette/, crypto/, dbus/, device/, ↵avi@chromium.org2013-06-281-1/+1
| | | | | | | | | | | | google_apis/, gpu/, ipc/, jingle/. BUG=254986 TEST=none TBR=ben@chromium.org Review URL: https://codereview.chromium.org/18156002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209149 0039d316-1c4b-4281-b951-d872f2087c98
* Fix wrong header guards found by clang's new Wheader-guard.thakis@chromium.org2013-06-171-1/+1
| | | | | | | | | | | | | | | | | | | | | Example diagnostic: In file included from ../../ppapi/tests/test_flash_file.cc:5: ../../ppapi/tests/test_flash_file.h:5:9: error: 'PAPPI_TESTS_TEST_FLASH_FILE_H_' is used as a header guard here, followed by #define of a different macro [-Werror,-Wheader-guard] ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../ppapi/tests/test_flash_file.h:6:9: note: 'PPAPI_TESTS_TEST_FLASH_FILE_H_' is defined here; did you mean 'PAPPI_TESTS_TEST_FLASH_FILE_H_'? ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PAPPI_TESTS_TEST_FLASH_FILE_H_ 1 error generated. BUG=none R=ben@chromium.org Review URL: https://codereview.chromium.org/17321002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@206837 0039d316-1c4b-4281-b951-d872f2087c98
* Update CrOS to use scoped_refptr<T>::get() rather than implicit "operator T*"rsleevi@chromium.org2013-06-143-18/+22
| | | | | | | | | BUG=110610 TBR=darin Review URL: https://chromiumcodereview.appspot.com/16998003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@206357 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: drop "Experimental" from Chrome OS backendkeybuk@chromium.org2013-06-1214-582/+526
| | | | | | | | | BUG=221813 TEST=device_unittests Review URL: https://chromiumcodereview.appspot.com/14932007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@205777 0039d316-1c4b-4281-b951-d872f2087c98
* Rename base/hash_tables to base/containers/hash_tables.brettw@chromium.org2013-06-113-5/+5
| | | | | | | | | | | Remove forwarding header BUG= R=avi@chromium.org Review URL: https://codereview.chromium.org/16667019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@205584 0039d316-1c4b-4281-b951-d872f2087c98
* Use a direct include of strings headers in crypto/, dbus/, device/.avi@chromium.org2013-06-1115-17/+17
| | | | | | | | | | BUG=247723 TEST=none TBR=ben@chromium.org Review URL: https://chromiumcodereview.appspot.com/16123026 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@205457 0039d316-1c4b-4281-b951-d872f2087c98
* Linux/CrOS: Listen for mtpd service owner change events and communicate with ↵thestig@chromium.org2013-06-101-19/+41
| | | | | | | | | | | | | the new service owner. The mtpd dbus service may not start right away. Any attempts to use it may be racy due to the lack of a service owner. Listening for service owner changes fixes this race. BUG=241302 TEST=Manual, see bug for repro case. Review URL: https://chromiumcodereview.appspot.com/15741025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@205331 0039d316-1c4b-4281-b951-d872f2087c98
* Use a direct include of utf_string_conversions.h in chrome_frame/, ↵avi@chromium.org2013-06-073-3/+3
| | | | | | | | | | | | chromeos/, cloud_print/, components/, courgette/, device/, extensions/. BUG=none TEST=none TBR=ben@chromium.org Review URL: https://chromiumcodereview.appspot.com/16614002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@204961 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: use updated constantskeybuk@chromium.org2013-06-051-10/+10
| | | | | | | | | BUG=221813 TEST=device_unittests Review URL: https://chromiumcodereview.appspot.com/14964007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@204339 0039d316-1c4b-4281-b951-d872f2087c98
* device: Gyp organization part 2.tfarina@chromium.org2013-06-042-49/+54
| | | | | | | | | | | | | | | This moves media_transfer_protocol targets into: device/media_transfer_protocol/media_transfer_protocol.gyp So it's consistent with what we have done with bluetooth and usb directories/targets. R=bryeung@chromium.org,miket@chromium.org,thestig@chromium.org TBR=thestig@chromium.org Review URL: https://chromiumcodereview.appspot.com/16142004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@204040 0039d316-1c4b-4281-b951-d872f2087c98
* Update remaining files to use WeakPtr<T>::get() instead of "operator T*"akalin@chromium.org2013-06-041-3/+3
| | | | | | | | | BUG=245942 TBR=darin@chromium.org Review URL: https://codereview.chromium.org/16136005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@203872 0039d316-1c4b-4281-b951-d872f2087c98
* device: Restructure the layout of gyp files.tfarina@chromium.org2013-06-0358-157/+178
| | | | | | | | | | | | | | | | | | This follow the same structure used by ui/keyboard/. Now the directory hierachy looks like this: device/bluetooth/bluetooth.gyp device/bluetooth/bluetooth_strings.gyp device/bluetooth/bluetooth_strings.grd device/bluetooth/strings device/usb/usb.gyp R=bryeung@chromium.org,miket@chromium.org Review URL: https://chromiumcodereview.appspot.com/16231013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@203652 0039d316-1c4b-4281-b951-d872f2087c98
* Use base::MessageLoop in more files.xhwang@chromium.org2013-05-301-1/+1
| | | | | | | | | | | These are either missed in the first pass, or added after the first pass. TBR=thestig@chromium.org BUG=236029 Review URL: https://codereview.chromium.org/16092013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@203259 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: remove legacy backendkeybuk@chromium.org2013-05-2512-5007/+0
| | | | | | | | | BUG=221813 TEST=device_unittests Review URL: https://chromiumcodereview.appspot.com/15020009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@202281 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: remove enable-experimental-bluetooth flagkeybuk@chromium.org2013-05-234-30/+3
| | | | | | | | | | BUG=221813 TEST=device_unittests, verify Bluetooth options still available on Chrome OS Review URL: https://chromiumcodereview.appspot.com/15024005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@201871 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: Profile support for Chrome OSkeybuk@chromium.org2013-05-0910-6/+1071
| | | | | | | | | | | | Implement support for the BluetoothProfile API for the BlueZ 5.x stack on Chrome OS, including BluetoothSocket support. BUG=229636 TEST=device_unittests Review URL: https://chromiumcodereview.appspot.com/14487002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199095 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: Parse the bluez.Error.Failed on pairing error.deymo@chromium.org2013-05-082-0/+45
| | | | | | | | | | | | | | | The method org.bluez.Device1.Pair can return with different errors. Among those, an org.bluez.Error.Failed: "Device or resource busy" is a possible option. This patch parses that D-Bus error as an ERROR_FAILED. BUG=238479 TEST=BluetoothExperimentalChromeOSTest.PairUnpairableDevice on device_unittests passed with the fix, and fails without it. Review URL: https://chromiumcodereview.appspot.com/15016004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199048 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 198844 "Move sequenced_task_runner to base/task"dbeam@chromium.org2013-05-084-6/+6
| | | | | | | | | | | | | | | | | Reverting revisions that rely on r198820 so to unbreak the build. > Move sequenced_task_runner to base/task > > BUG= > R=akalin@chromium.org > > Review URL: https://codereview.chromium.org/14927008 TBR=brettw@chromium.org Review URL: https://codereview.chromium.org/14985007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198848 0039d316-1c4b-4281-b951-d872f2087c98
* Move sequenced_task_runner to base/taskbrettw@chromium.org2013-05-084-6/+6
| | | | | | | | | BUG= R=akalin@chromium.org Review URL: https://codereview.chromium.org/14927008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198844 0039d316-1c4b-4281-b951-d872f2087c98
* Enable Clang warnings in .cc files for Linux+[Aura/ChromeOS]rsleevi@chromium.org2013-05-071-11/+10
| | | | | | | | | BUG=115047 R=darin Review URL: https://chromiumcodereview.appspot.com/14890005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198649 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: set a name for the adapterkeybuk@chromium.org2013-05-063-1/+41
| | | | | | | | | | BUG=220820 TEST=bt_console, show R=youngki@chromium.org Review URL: https://chromiumcodereview.appspot.com/14898004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198544 0039d316-1c4b-4281-b951-d872f2087c98
* Implemented BluetoothDeviceWin::ConnectToProfile()youngki@chromium.org2013-05-057-34/+110
| | | | | | | | | | | | I mostly reused BluetoothServiceRecordWin to implement this method (for now). Even if we deprecate BluetoothServiceRecord, I think we could keep BluetoothServiceRecordWin for Windows platform. After I submit this I will send out cleanup CLs to delete the unused code. BUG=229636 Review URL: https://chromiumcodereview.appspot.com/14582010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198350 0039d316-1c4b-4281-b951-d872f2087c98
* Add a method to check if a D-Bus service has an owner. Use it for mtpd.thestig@chromium.org2013-05-041-24/+47
| | | | | | | | BUG=181064 Review URL: https://chromiumcodereview.appspot.com/14568005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198328 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: make BluetoothProfile constructor protectedkeybuk@chromium.org2013-05-031-4/+1
| | | | | | | | | | BUG=none TEST=device_unittests R=youngki@chromium.org Review URL: https://chromiumcodereview.appspot.com/14884002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198241 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: fix metrics collectionkeybuk@chromium.org2013-05-032-52/+60
| | | | | | | | | | | | | | | | | | | | | | | Bluetooth.PairingMethod was always sent with UMA_PAIRING_METHOD_NONE even when another method was used because the pairing_delegate_used_ flag was never updated. Bluetooth.PairingResult was never called with UMA_PAIRING_RESULT_SUCCESS; add this add the end of OnConnect(), adding a after_pairing flag to the connect chain to ensure we only record this as part of a paring attempt. Bluetooth.PairingResult failures were recorded for ordinary Connect() calls, use the added after_pairing flag to only record them when pairing. BUG=237340 TEST=chrome:///histograms R=youngki@chromium.org Review URL: https://codereview.chromium.org/14889002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198171 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: Check IsPaired() before IsConnected() to avoid false connectionsdeymo@chromium.org2013-05-034-4/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bluetooth devices can be connected to the adapter for several reasons. One of the reasons is that the user is activelly using the device, so the device is paired/trusted, connected and also connected to a given profile. But that's not the only one, since a Bluetooth device is allowed by the spec to connect to any other device or adapter to do some basic operations like requesting the SDP records. Because of this, IsConnected() can be true in situations where the user didn't inted a connection. If IsPaired() is true, the value of IsConnected() almost implies that the device is connected to the applications (but we can't be sure about that). If IsPaired() is false, the device is neither paired nor trusted, and the value of IsConnected() is mostly irrelevant, since the device is for sure not connected to any application. This fix adds a comments explaining this behavior to the common BluetoothDevice interface and also corrects some ussages of IsConnected() where that value was used even when IsPaired() is false. BUG=237285 TEST=Manual test. Manual test procedure: 1. Go to the settings page: chrome://settings 2. Scan for new devices, select the "Motorola KZ450" Keyboard. 3. Attempt a connect to it. A passkey number should be shown on the screen. 4. Click on "cancel" on that pairing dialog. 5. Immediately after, try to add a new device again. 6. In the "add Bluetooth device" dialog, click on the "Motorola KZ450" keyboard. 7. The "connect" button should be enabled. Click it. 8. The keyboard should ask again for a passkey/pincode to type. Review URL: https://chromiumcodereview.appspot.com/14569023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198083 0039d316-1c4b-4281-b951-d872f2087c98
* Relanding addProfile/removeProfile patch with heapchecker fix.youngki@chromium.org2013-05-016-7/+56
| | | | | | | | | | | | | | | | This is a relanding of r197554 with heapchecker fix. Some profile-dependent services depend on UI thread to clean up, so I had to add UI message loop in bluetooth_event_router_unittest.cc to make sure that all the objects are released at the end of test. I verified with valgrind that this patch does not introduce any new memory leak. BUG=229636 Review URL: https://chromiumcodereview.appspot.com/14569007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197741 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 197554 "Implemented chrome.bluetooth.addProfile and chrom..."timurrrr@chromium.org2013-05-016-56/+7
| | | | | | | | | | | | | | | | | | | This has introduced a few memory leaks on the Valgrind and HeapChecker bots. > Implemented chrome.bluetooth.addProfile and chrome.bluetooth.removeProfile. > > We will reject the registration of the profiles that have already been registered. > When there is an incoming connection, we will route that connection to the extension that registered the profile. > > BUG=229636 > > Review URL: https://chromiumcodereview.appspot.com/14311007 TBR=youngki@chromium.org Review URL: https://codereview.chromium.org/14682006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197580 0039d316-1c4b-4281-b951-d872f2087c98
* Implemented chrome.bluetooth.addProfile and chrome.bluetooth.removeProfile.youngki@chromium.org2013-05-016-7/+56
| | | | | | | | | | | We will reject the registration of the profiles that have already been registered. When there is an incoming connection, we will route that connection to the extension that registered the profile. BUG=229636 Review URL: https://chromiumcodereview.appspot.com/14311007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197554 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: fix fake device classeskeybuk@chromium.org2013-04-301-8/+8
| | | | | | | | | | | | | | | | | | | | | Fake devices are used not only in test cases, but also when running a Chrome OS build of Chromium on Linux. Fix the inverted keyboard/mouse classes so that the "Microsoft Mouse" behaves as the real device and returns false for IsPairable(). This means it can be used to exercise the Connect-without-Pairing case. Add a new "Unconnectable Device" for the test that was testing a device actually failing to connect after being paired. BUG=none TEST=device_unittests, -Dchromeos=1, chrome --enable-experimental-bluetooth, pair with MS Mouse, verify no pairing dialog appears R=satorux@chromium.org, youngki@chromium.org Review URL: https://chromiumcodereview.appspot.com/14273033 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197215 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: gather usage metricskeybuk@chromium.org2013-04-2912-7/+248
| | | | | | | | | | | Resubmit; this was reverted in 196993 due to a missing initialization in a unit test. BUG=233820 TEST=chrome:///histograms Review URL: https://codereview.chromium.org/14109028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197148 0039d316-1c4b-4281-b951-d872f2087c98
* device: Use base::MessageLoop.xhwang@chromium.org2013-04-291-26/+28
| | | | | | | | | BUG=236029 R=keybuk@chromium.org Review URL: https://chromiumcodereview.appspot.com/14305031 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197112 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: unregister the agent on CancelPairing()keybuk@chromium.org2013-04-291-1/+7
| | | | | | | | | | | | | | | | BluetoothOptionsHandler will call BluetoothDevice::CancelPairing() when it's being torn down, after which pointers to it (e.g. the pairing_delegate_ pointer) are invalid. Thus unregister the agent at this point rather than waiting for a response from the backend. BUG=none TEST=verify no crash when clicking Cancel or Reject during pairing Review URL: https://chromiumcodereview.appspot.com/14273036 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197085 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 196990 "Bluetooth: gather usage metrics"thakis@chromium.org2013-04-2812-248/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Broke this test on the CrOs main waterfall bots: MetricsLogTest.RecordEnvironment: [19521:19521:0428/105537:1031147919:FATAL:dbus_thread_manager.cc(562)] Check failed: g_dbus_thread_manager. DBusThreadManager::Get() called before Initialize() [0x7fd74d7ce060] base::debug::StackTrace::StackTrace() [0x7fd74d8085ab] logging::LogMessage::~LogMessage() [0x7fd744a60cfe] chromeos::DBusThreadManager::Get() [0x000003d84f8f] chromeos::BluetoothAdapterChromeOS::BluetoothAdapterChromeOS() [0x000003d82c19] device::BluetoothAdapterFactory::GetAdapter() [0x0000026f1274] MetricsLog::RecordEnvironmentProto() [0x0000026f0bf2] MetricsLog::RecordEnvironment() [0x0000013ad864] MetricsLogTest::TestRecordEnvironment() [0x0000013a95d1] MetricsLogTest_RecordEnvironment_Test::TestBody() [0x000002f37967] testing::internal::HandleSehExceptionsInMethodIfSupported<>() [0x000002f35132] testing::internal::HandleExceptionsInMethodIfSupported<>() [0x000002f2a4e6] testing::Test::Run() [0x000002f2ad0a] testing::TestInfo::Run() [0x000002f2b438] testing::TestCase::Run() [0x000002f303e3] testing::internal::UnitTestImpl::RunAllTests() [0x000002f3876e] testing::internal::HandleSehExceptionsInMethodIfSupported<>() [0x000002f358f7] testing::internal::HandleExceptionsInMethodIfSupported<>() [0x000002f2eeb2] testing::UnitTest::Run() [0x0000045f17ac] base::TestSuite::Run() [0x0000042fe020] content::UnitTestTestSuite::Run() [0x00000306ea62] main [0x7fd73e27b76d] __libc_start_ > Bluetooth: gather usage metrics > > BUG=233820 > TEST=chrome:///histograms > R=isherman@chromium.org, satorux@chromium.org, youngki@chromium.org > > Review URL: https://codereview.chromium.org/13872017 TBR=keybuk@chromium.org Review URL: https://codereview.chromium.org/14001008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@196993 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: gather usage metricskeybuk@chromium.org2013-04-2812-7/+248
| | | | | | | | | | BUG=233820 TEST=chrome:///histograms R=isherman@chromium.org, satorux@chromium.org, youngki@chromium.org Review URL: https://codereview.chromium.org/13872017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@196990 0039d316-1c4b-4281-b951-d872f2087c98
* fixing the crash: pass the data pointer instead of the class pointer.youngki@chromium.org2013-04-271-2/+2
| | | | | | | | BUG= Review URL: https://chromiumcodereview.appspot.com/14307022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@196952 0039d316-1c4b-4281-b951-d872f2087c98
* device: Remove use of ALLOW_THIS_IN_INITIALIZER_LIST.scherkus@chromium.org2013-04-261-1/+1
| | | | | | | | | | It's no longer providing value as the MSVC warning is disabled during compilation. Refer to bug for details. BUG=234765 Review URL: https://codereview.chromium.org/14478006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@196805 0039d316-1c4b-4281-b951-d872f2087c98
* Implemented chrome.bluetooth.getProfiles().youngki@chromium.org2013-04-261-0/+1
| | | | | | | | BUG=229636 Review URL: https://chromiumcodereview.appspot.com/14472013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@196756 0039d316-1c4b-4281-b951-d872f2087c98
* Bluetooth: send DeviceChanged for more propertieskeybuk@chromium.org2013-04-243-21/+69
| | | | | | | | | | | | | | | | | | | The address and trusted properties of the underlying D-Bus device interface correspond to BluetoothDevice properties, so DeviceChanged() must be sent for a change in value of those too. In addition the reconnect_mode property of the D-Bus input interface changing (including the interface being added and removed for this object) corresponds to BluetoothDevice::IsConnectable() so DeviceChanged() must also be sent. BUG=233370 TEST=device_unittests R=youngki@chromium.org Review URL: https://codereview.chromium.org/14065018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@196177 0039d316-1c4b-4281-b951-d872f2087c98
* Implemented BluetoothDeviceMac::ConnectToProfile().youngki@chromium.org2013-04-2417-7/+209
| | | | | | | | | | | | This CL implements BluetoothProfileMac::Connect(), which makes an explicit outgoing connection to the device. I will add unittests once I get a preliminary review from reviewers. BUG=229636 Review URL: https://chromiumcodereview.appspot.com/14405008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@196099 0039d316-1c4b-4281-b951-d872f2087c98
* D-Bus: notify properties changed from fakeskeybuk@chromium.org2013-04-241-3/+0
| | | | | | | | | | | | | | | | | Call the property changed callback when fakes use ReplaceValue() or ReplaceValueWithSetValue(), since the actual implementation will always call the callback. This avoids issues with property changed notifications being missing when properties structures are built within fakes. BUG=none TEST=dbus_unittests, device_unittests R=satorux@chromium.org, youngki@chromium.org Review URL: https://codereview.chromium.org/14443003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@195977 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-12 07:32:13 +0000