bluez-dbus | bluetooth library for linux OSes using DBus

by hypfvieh Java Version: 0.1.4 License: MIT

X-Ray Key Features Code Snippets(1)Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | bluez-dbus Summary

bluez-dbus is a Java library typically used in Networking applications. bluez-dbus has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub, Maven.

bluetooth library for linux OSes using DBus and bluez (

Support

Quality

Security

License

Reuse

Support

bluez-dbus has a low active ecosystem.

It has 55 star(s) with 19 fork(s). There are 8 watchers for this library.

It had no major release in the last 12 months.

There are 2 open issues and 48 have been closed. On average issues are closed in 84 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of bluez-dbus is 0.1.4

Quality

bluez-dbus has 0 bugs and 0 code smells.

Security

bluez-dbus has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

bluez-dbus code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

bluez-dbus is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

bluez-dbus releases are not available. You will need to build from source code and install.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

It has 3585 lines of code, 447 functions and 117 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed bluez-dbus and discovered the below as its top functions. This is intended to give you an instant insight into bluez-dbus implemented functionality, and help decide if they suit your requirements.

Setup a bluetooth scan filter
Finds all nodes in the DB
Create a new Document instance from the given String
Scan for bluetooth adapters
Apply an XPath expression on the given document
Finds a BluetoothAdapter by its unique identifier
Configures the filter to be used
Register a new profile
Convert the specified options to a map
Register an agent with the given path and capability
Request a default agent
Unregisters a previously registered agent
Connect to the remote device
Get the Bluetooth device name
Unregister a profile

Get all kandi verified functions for this library.

bluez-dbus Key Features

No Key Features are available at this moment for bluez-dbus.

bluez-dbus Examples and Code Snippets

bluez-dbus

Java

Lines of Code : 5

License : Permissive (MIT)

Copy


    com.rm5248
    dbus-java-nativefd
    1.0

Community Discussions

Trending Discussions on bluez-dbus

Could not load FFI provider when using module-info.java

BLE with RPI, wrong endpoint ID selected

QUESTION

Could not load FFI provider when using module-info.java

Asked 2020-Sep-19 at 01:59

my Linux Java application uses bluetooth devices. I use this library in order to communicate with bluez stack : https://github.com/hypfvieh/bluez-dbus.

It worked very well until I added module-info.java to my client code. Suddenly I got this error:

Exception in thread "main" java.lang.UnsatisfiedLinkError: could not load FFI provider jnr.ffi.provider.jffi.Provider at jnr.ffi@2.1.15/jnr.ffi.provider.InvalidRuntime.newLoadError(InvalidRuntime.java:101) at jnr.ffi@2.1.15/jnr.ffi.provider.InvalidRuntime.findType(InvalidRuntime.java:42) at jnr.ffi@2.1.15/jnr.ffi.Struct$NumberField.(Struct.java:872) at jnr.ffi@2.1.15/jnr.ffi.Struct$Unsigned16.(Struct.java:1240) at jnr.unixsocket@0.33/jnr.unixsocket.SockAddrUnix$DefaultSockAddrUnix.(SockAddrUnix.java:209) at jnr.unixsocket@0.33/jnr.unixsocket.SockAddrUnix.create(SockAddrUnix.java:174) at jnr.unixsocket@0.33/jnr.unixsocket.UnixSocketAddress.(UnixSocketAddress.java:53) at dbus.java@3.2.3/org.freedesktop.dbus.connections.transports.UnixSocketTransport.(UnixSocketTransport.java:32) at dbus.java@3.2.3/org.freedesktop.dbus.connections.transports.TransportFactory.createTransport(TransportFactory.java:37) at dbus.java@3.2.3/org.freedesktop.dbus.connections.AbstractConnection.(AbstractConnection.java:161) at dbus.java@3.2.3/org.freedesktop.dbus.connections.impl.DBusConnection.(DBusConnection.java:334) at dbus.java@3.2.3/org.freedesktop.dbus.connections.impl.DBusConnection.getConnection(DBusConnection.java:149) at dbus.java@3.2.3/org.freedesktop.dbus.connections.impl.DBusConnection.getConnection(DBusConnection.java:169) at dbus.java@3.2.3/org.freedesktop.dbus.connections.impl.DBusConnection.getConnection(DBusConnection.java:219) at dbus.java@3.2.3/org.freedesktop.dbus.connections.impl.DBusConnection.getConnection(DBusConnection.java:184) at bluez.dbus@0.1.3/com.github.hypfvieh.bluetooth.DeviceManager.createInstance(DeviceManager.java:74) at ...

Caused by: java.lang.UnsatisfiedLinkError: could not get native definition for type POINTER, original error message follows: java.lang.UnsatisfiedLinkError: could not locate stub library in jar file. Tried [jni/x86_64-Linux/libjffi-1.2.so, /jni/x86_64-Linux/libjffi-1.2.so] at jffi@1.2.23/com.kenai.jffi.internal.StubLoader.getStubLibraryStream(StubLoader.java:450) at jffi@1.2.23/com.kenai.jffi.internal.StubLoader.loadFromJar(StubLoader.java:375) at jffi@1.2.23/com.kenai.jffi.internal.StubLoader.load(StubLoader.java:278) at jffi@1.2.23/com.kenai.jffi.internal.StubLoader.(StubLoader.java:487) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:427) at jffi@1.2.23/com.kenai.jffi.Init.load(Init.java:68) at jffi@1.2.23/com.kenai.jffi.Foreign$InstanceHolder.getInstanceHolder(Foreign.java:49) at jffi@1.2.23/com.kenai.jffi.Foreign$InstanceHolder.(Foreign.java:45) at jffi@1.2.23/com.kenai.jffi.Foreign.getInstance(Foreign.java:103) at jffi@1.2.23/com.kenai.jffi.Type$Builtin.lookupTypeInfo(Type.java:242) at jffi@1.2.23/com.kenai.jffi.Type$Builtin.getTypeInfo(Type.java:237) at jffi@1.2.23/com.kenai.jffi.Type.resolveSize(Type.java:155) at jffi@1.2.23/com.kenai.jffi.Type.size(Type.java:138) at jnr.ffi@2.1.15/jnr.ffi.provider.jffi.NativeRuntime$TypeDelegate.size(NativeRuntime.java:178) at jnr.ffi@2.1.15/jnr.ffi.provider.AbstractRuntime.(AbstractRuntime.java:48) at jnr.ffi@2.1.15/jnr.ffi.provider.jffi.NativeRuntime.(NativeRuntime.java:57) at jnr.ffi@2.1.15/jnr.ffi.provider.jffi.NativeRuntime.(NativeRuntime.java:41) at jnr.ffi@2.1.15/jnr.ffi.provider.jffi.NativeRuntime$SingletonHolder.(NativeRuntime.java:53) at jnr.ffi@2.1.15/jnr.ffi.provider.jffi.NativeRuntime.getInstance(NativeRuntime.java:49) at jnr.ffi@2.1.15/jnr.ffi.provider.jffi.Provider.(Provider.java:29) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500) at java.base/java.lang.reflect.ReflectAccess.newInstance(ReflectAccess.java:124) at java.base/jdk.internal.reflect.ReflectionFactory.newInstance(ReflectionFactory.java:346) at java.base/java.lang.Class.newInstance(Class.java:604) at jnr.ffi@2.1.15/jnr.ffi.provider.FFIProvider$SystemProviderSingletonHolder.getInstance(FFIProvider.java:68) at jnr.ffi@2.1.15/jnr.ffi.provider.FFIProvider$SystemProviderSingletonHolder.(FFIProvider.java:57) at jnr.ffi@2.1.15/jnr.ffi.provider.FFIProvider.getSystemProvider(FFIProvider.java:35) at jnr.ffi@2.1.15/jnr.ffi.Runtime$SingletonHolder.(Runtime.java:82) at jnr.ffi@2.1.15/jnr.ffi.Runtime.getSystemRuntime(Runtime.java:67) at jnr.unixsocket@0.33/jnr.unixsocket.SockAddrUnix.(SockAddrUnix.java:46) at jnr.unixsocket@0.33/jnr.unixsocket.SockAddrUnix$DefaultSockAddrUnix.(SockAddrUnix.java:208) at jnr.unixsocket@0.33/jnr.unixsocket.SockAddrUnix.create(SockAddrUnix.java:174) at jnr.unixsocket@0.33/jnr.unixsocket.UnixSocketAddress.(UnixSocketAddress.java:53) at dbus.java@3.2.3/org.freedesktop.dbus.connections.transports.UnixSocketTransport.(UnixSocketTransport.java:32) at ...

I tried to require everything related to this error in the module-info.java without success:

...

ANSWER

Answered 2020-Sep-19 at 01:59

TL;DR

This worked for me…

Source https://stackoverflow.com/questions/63934326

QUESTION

BLE with RPI, wrong endpoint ID selected

Asked 2020-Sep-18 at 20:31

Trying to communicate with a BLE device (smart lamp).

I use the following dependency:

...

ANSWER

Answered 2020-Sep-16 at 22:42

gattool is one of the eight tools that have been deprecated by BlueZ.

To debug this I would advise using bluetoothctl to workout what the correct paths are for the connected device. A session might look like this:

Source https://stackoverflow.com/questions/63926205

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install bluez-dbus

You can download it from GitHub, Maven.
You can use bluez-dbus like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the bluez-dbus component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: