| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Change-Id: I54ded27ab85d46eef3d2cca84f2394b1ffe88ced
|
| |
|
|
| |
Change-Id: I6bc04efd1292784bae5fc4786949d9da79e4aa22
|
| |
|
|
| |
Change-Id: I2218b97647e381bfe6d329b1b6134bb76c1832b6
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Bug: 2561150
Race condition: We were basing whether the event loop is
running or not on whether nat->pollData was null or not.
In rare cases, eventLoopMain would have not started,
isEventLoopRunning returns true; java side makes a dbus call
and the watches get set to null, causing a crash in
dbus_connection_set_watch_functions when eventLoopMain starts.
Change-Id: I863f182185a8e956fd53cb58783b7fe0ecfb2ddb
|
| |\
| |
| |
| | |
Change-Id: Ie60db5faf407344b8fbe3d5c1e7c01e927ff251e
|
| | |
| |
| |
| |
| |
| | |
Using close instead of shutdown on the file descriptors and only clear the file
descriptor that was closed. If both file descriptors are cleared the thread
will not be able to close it.
|
| | |
| |
| |
| |
| |
| | |
When device is already created, and we call CreateDevice, we
need to report the error correctly. Only then the SDP query
will be done from java land.
|
| |/
|
|
|
|
|
| |
We were registering a match for 'AudioSink', but unregistering 'audio.sink'.
This does not immediately cause an error, but stress testing of BT off/on found
that the leak causes a DBus Limits Error after ~300 iterations. It then becomes
impossible to turn BT on again until a reboot.
|
| |
|
|
|
|
|
| |
This reverts commit 3d0726b4d8a30e57852b70f1dcf4d8d20508cd1e
Change-Id: Ie1ce5d09cc0b799ef0799f30eedc95f0ca5d3fad
DrNo: jerrryw
|
| |
|
|
|
|
|
| |
Change-Id: I2492bffe57bded65fdbef5cf98e22cef3937e537
DrNo: eastham
Bug: 2089423
Joke: Why don't anteaters get sick? Because they're full of anty-bodies!
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hide createRfcommSocket(int channel)
Add createRfcommSocketWithServiceRecord(UUID uuid)
Rename listenUsingRfcomm(String,UUID) -> listenUsingRfcommWithServiceRecord(..)
Now we have a complete API for developers to make peer-peer RFCOMM connections
with hard-coding the limited (30) RFCOMM channels, instead using SDP lookup
of an UUID.
This commit addresses two serious bugs:
- Do not throw IOException on accepting an incoming RFCOMM connection with
BluetoothSocket. This was a regression from commit 24bb9b8af4ff6915
- Workaround failure of bluez to update SDP cache when channel changes by
trying to use the same RFCOMM channel on the server every time, instead
of picking server channels randomly. This is a pretty ugly workaround,
and we are still trying to fix the caching issue - but with this
workaround we are at least shippable and apps will work at least until
they start colliding on the 30 RFCOMM channels.
DrNo: eastham
Bug: 2158900
Joke: What did the digital watch say to his mom? "Look mom no hands."
Change-Id: Ia4879943b83afac06b6f1a3f2391cf1628afce7d
|
| |
|
|
|
|
|
|
|
| |
Add new API which clients can use to force an SDP query.
The result is broadcast using an intent having the UUIDs.
The intent is broadcast after a timeout, in case of an error.
This timeout is greater than the page timeout.
Change-Id: I61e6db4c05b34c42f679a66987e37e2063a793b6
|
| |
|
|
|
|
|
|
|
|
| |
1) Handle incoming 2.1 pairing requests
2) Modify displaying error messages on bond failures.
3) Add delay while accepting incoming pairing for certain 2.1 devices.
When MITM is on, the link key request might come more than once.
Auto accept with a delay.
4) Handle DisplayPasskey callback for pairing a 2.1 keyboard with
a 2.1 device
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
We were running out of local refs when there are lots of devices.
Instead of deleting every single local ref, create a local stack frame.
This operation is inexpensive so doesn't add a high overload and keeps
the code clean instead of deleting every single local ref.
|
| |
|
|
|
| |
Phone panics while streaming over A2DP and scanning for new device
BluetoothEventLoop should delete reference
|
| |
|
|
|
| |
Note: Some cases have not been tested yet, as we would need to
get proper UI support.
|
| |
|
|
| |
This reverts commit 228b2f3a813e93413a0f9e2f29dfbfc54590a356.
|
| |
|
|
|
| |
Note: Some cases have not been tested yet, as we would need to
get proper UI support.
|
| |\
| |
| |
| |
| |
| |
| | |
Merge commit 'c9dc19bb96d2d77ec50f6e40fc22d1ff615f2044'
* commit 'c9dc19bb96d2d77ec50f6e40fc22d1ff615f2044':
Fix runtime restarts due to sending the wrong flags to dbus.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
In eventLoopMain we were correctly translating from unix events to dbus flags,
but a coding typo then gave the unix events to dbus. Fix this typo.
Also noticed that we were passing raw dbus flags to poll() in another area.
This did not cause any immediate problem, since POLLIN | POLLPRI is harmless
and we do not usually need POLLOUT. But fixed anyway.
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This was causing the system server to quietly die. Naughty DBUS!!
Now you will just see errors in the log "DBUS connection disconnected"
on every DBUS call.
There is still the root cause problem of why the DBUS connection disconnects,
which is not addressed by this change.
|
| | |
| |
| |
| |
| |
| | |
BUG=1244263
Automated import of CL 144241
|
| | | |
|
| | |
| |
| |
| |
| | |
Changes in the Bluetooth JNI calls and framework functions
for Bluez4.
|
| |/
|
|
|
|
| |
Original author: rgreenwalt
Automated import of CL 144392
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
