| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
passing all tests w/ gcc + clang + java17 build
|
|
|
|
| |
147e17b0b41a123b2f4040cbd6df5b73b7e97164)
|
| |
|
| |
|
| |
|
|
|
|
| |
RSSI, BDADDR* change (java)
|
|
|
|
| |
array) with extra capacity and size
|
|
|
|
| |
array)
|
|
|
|
| |
add sendOnly(..) to skip waiting for response
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GATTRole::Client; BTAdapter::startDiscovery() add DBGattServerRef ref
A GattServerHandler(DBGattServer) is also possible for LL master (GATT client) connections
where the server inquires certain data points within the client's GATT.
User can pass DBGattServer to BTAdapter::startDiscovery() to enable the GattServerHandler for such cause.
Test case: Avalun's LabPad device
- DBTLabPadClient01.java
- dbt_labpadclient01.cpp
|
|
|
|
| |
for C++ for general use (commonly used to ctor a DBGattServer)
|
|
|
|
| |
enum conversion, fix byte values
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
using RPA/IRK crypto matcher for HCI events (passing RPA)
HCIConnectionRef and BTDevice store both address pairs, naming the potential RPA as 'visibleAddressAndType'.
BTAdapter's findDevice*() method seeks through all device's address first
and if the potential RPA is not found queries each device whether it
matches with its IRK (if existing).
In case the latter is positive, the identity address has been found.
Naturally, to have this work, the adapter (in server mode) needs to upload all
keys to the host adapter to allow resolving as well as instantiating
all devices per key-set.
This concept has already been implemented,
hence the IRK resolution change-set is not too dramatic.
Trial unit tests passed.
|
|
|
|
| |
id_address), SMPKeyBin storage and host upload, w/ clearing all IRKs on startup
|
|
|
|
| |
using AdapterStatusListener::devicePairingState() + SMPPairingState::PASSKEY_NOTIFY to display generated PassKey
|
|
|
|
|
|
|
|
| |
API Changes for v3.2.0:
- BTAdapter:
- setPrivacy(bool) added
- initialize() w/o args or default args removed
- initialize(final BTMode btMode, boolean powerOn) added
|
|
|
|
| |
lib-loading
|
| |
|
|
|
|
|
|
| |
- AdapterStatusListener
- BTGattHandler::NativeGattCharListener
- DBGattServer::Listener
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
See also jaulib commit 9160f9a4b74f5e5ae07f715025ea4d3aafdf6ab3
Details:
- Using 'const T&' as method argument type where applicable, i.e. not when required to pass value off-thread.
- Notable: Can also hold a default value!
- Using `const T&` in range-loop where applicable
- Drop std::move for trivial types
- ...
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Details
- Use 'size_type' instead of 'int',
propagate same 'size_type' into 'darray' etc.
- Use 'std::make_shared', 'std::make_unique'
- Use range-based for loops
- Remove redundant 'virtual', use 'override' in derived classes
- Use 'nullptr'
- Use default impl for dtor, ctor (incomplete)
- Use copy and std::move (incomplete)
- Explcitly catch std::bad_alloc in 'new' in 'noexcept' -> 'abort'
- 'abort' was issued implicitly in noexcept methods
- L2CAPServer, L2CAPClient, NopGattServerHandler,
DBGattServerHandler, FwdGattServerHandler
- Use local close_impl(), usable in virtual destructor
- L2CAPClient::read, HCIComm::read
- preset 'poll' result 'n', avoid garbage comparison
- BTAdapter::enableListening
- loop through addMgmtEventCallback() result
- JNI code
- explicit size_type is cast to jsize or jint w/o check
- unchanged semantics
|
|
|
|
| |
jau::function<void(A...)>
|
| |
|
| |
|
| |
|
|
|
|
| |
5.9 (Ubuntu 20.04), tolerate it.
|
| |
|
| |
|
| |
|
|
|
|
| |
reference to perihperal-server mode to overview.
|
|
|
|
|
|
| |
See commits
- cc53af990263bfa09947ad3127e0de6a6ffcb493
- ca228cd0512be4642a41468ff92e688dbf296fcd
|
|
|
|
|
|
|
|
|
|
| |
trial tests
Commit ca228cd0512be4642a41468ff92e688dbf296fcd defined that AdapterstatusListener::deviceFound()
is only called if not already connected and if initially found .
This change removes using the 'device processing' list,
as already the case for the trial tests.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a.removeAllStatusListener() and new mngr.removeAllChangedAdapterSet{Callbacks|Listener}() ensuring clean state even if previous test failed.
On the C++ trials using Catch2, not having issued at test launch via setupTest():
- adapter.removeAllStatusListener()
- manager.removeAllChangedAdapterSetCallbacks()
and if first test failed, the second tests
had two ChangedAdapterSetCallbacks registered and hence added the AdapterStatusListener twice
as well still had the previous test listener included.
This in turn lead to a SIGSEGV when the previous
AdapterStatusListener::deviceDisconnected() has been called
in the server's processDisconnectedDevice()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
zero sized array of BTGattServices on error
BTGattHandler::discoverCompletePrimaryServices():
- just discover the services and its characteristics and descriptors
- return bool, success of failor as returned by discovery methods (incl. their send*() command)
BTGattHandler::initClientGatt():
- clear services before retrieval and on error
- error response on
- BTGattHandler::discoverCompletePrimaryServices() failure
- no services
- no GenericAccess services
- only return true and leave services if no error
BTDevice::getGattService():
- perform BTGattHandler::initClientGatt() error checks as well
- update method API doc, describing failure included no GenericAccess service
|
|
|
|
| |
native send[Notification|Indication]() method.
|
|
|
|
|
|
|
|
| |
such in BTAdapter, ... (API CHANGE)
BTAdapter removes itself from BTManager, hence needs to ensure BTManager is not yet destructed.
This goes well along with our new JNI mapping, holding the shared_ptr reference in nativeInstance.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
== BTFactory.isInitialized()` in ctor, i.e. use w/o native libraries
DBTNativeDownlink:
- remove `static { BTFactory.checkInitialized() }`, not allowing constructing any specialization instance
AdapterStatusListener, BTGattCharListener:
- check BTFactory.isInitialized() in ctor and drop the nativeInstance w/ a System.err note
BTFactory:
- Fix isInitialized() query (duh!)
- Have initializedID be atomic and drop 'synchronized' locking on
- checkInitialized()
- isInitialized()
This tolerance is required to establish the behavior before
fixing the JNI lifecycle of AdapterStatusListener, BTGattCharListener,
i.e. allow testing using BTGattCharListener w/o a real BT subsystem.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DBTNativeDownlink and JavaUplink like AdapterStatusListener change, clean listener API + impl.
AdapterStatusListener adopted fully linked via DBTNativeDownlink (java->native) and JavaUplink (native->java).
This allows intrinsic lifecycle management.
Native destruction leads to its reference removal from the java object
and destruction of the java object removes its reference from the native object.
Both reference removals may lead to their destruction if reaching zero.
(was commit 9c5f25ccd1637728d6e79592279e4b38ecd32f59)
Same applies to BTGattCharListener:
- This removed BTGattChar::Listener, simply use BTGattCharListener
- Using private BTGattHandler::GattCharListenerPair struct for BTGattChar mapping
- No more manual or exposed BTGattChar mapping
- Java: An added BTGattCharListener instance can be used for removal now,
no more wrapper object magic returned.
Further:
- moved removed `namespace impl`, moved StatusListenerPair into private BTAdapter
- have all add/remove*Listener methods noexcept
Unit tests validating BTGattCharListener add and remove.
|
| |
|
|
|
|
|
|
| |
AdapterStatusListener derive from JavaUplink/DBTNativeDownlink
Was done in commit 9c5f25ccd1637728d6e79592279e4b38ecd32f59 to fix JNI Lifecycle
|
|
|
|
| |
impl::StatusListenerPair for BTDevice::addStatusListener() only -> Simplifying API
|
|
|
|
| |
by using shared_ptr_ref<T>
|
|
|
|
|
|
|
| |
JavaUplink/DBTNativeDownlink, resolving BTAdapter::removeAllStatusListener() and use shared_ptr_ref<T>
- AdapterStatusListener's native instance is now created at java object construction, etc .. same pattern like BTDevice ..
- Java/Native object relation is inherently thread safe due to using use shared_ptr_ref<T>
|
|
|
|
|
|
|
| |
shared_ptr_ref<T>; Made is{->Native}Valid() final for clarity
- Currently `initDownlink(..)` is intended for AdapterStatusListener
- Clarity `protected boolean isValid()` -> `protected final boolean isNativeValid()`
|
|
|
|
| |
DBGatt{Service,Char,Desc} in BTGatt{Service,Char,Desc}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
handle` -> `const bool discovered`
Motivation:
- the connection handle is known to the device already and can be retrieved, redundant information
- the flag discovered gives information whether BTAdapter has sent out a deviceFound message, i.e. the user actually issued the connection (default).
We like to detect issues where devices are automatically connected by the underlying host implementation,
i.e. BlueZ/kernel's whitelist mechanism or otherwise - an unsusal and undesired situation.
In such case, no `DEVICE FOUND` advertising is promoted and the underlying BlueZ/kernel
issues the connection itself.
Here `discovered` will be `false`.
|
|
|
|
|
|
| |
std::make_shared<jau::JavaGlobalObj>() ctor @ javaUplink->setJavaObject()
This avoids any jjobject destruction in-between
|
| |
|