-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Leshan with android #573
Comments
I never tested it, but we based our code on californium(CoAP stack) and I know that some people use it on android. Did you test Leshan client on android ? If yes could you quickly explain what you have done ? and which problems you face ? and we could try together to make it works. |
https://github.com/ApplicationPlatformForIoT/LwM2MDemoClientAndroid I have successfully tested the above client previously. It looks like an Ericsson demo based on the objects created. So short answer is yes I think you can get it working but no you can't just run the Leshan client demo. |
Here another example of Leshan used with Android : https://github.com/xgswust/leshan-android-demo (from #719) |
In #800, I activate animal-sniffer-maven-plugin for ensure we don't use class signature which are not present in android. This will not guarantee that all Leshan API will works correctly but at least that we don't use class which is not present in Android framework. Animal sniffer is activated on main module ( Currently Leshan target android-api-level-19/4.4.2 (aka KitKat) which should cover a great part of android devices. About leshan dependencies :
|
I updated the F.A.Q by adding a question about android. |
I close this issue as there is not so much we can do now. (Except maybe develop an android demo ? 🤔 ) |
some interesting explanation and links about android developments : eclipse-californium/californium#1664 (comment) |
Hello everyone,
I'm wondering if a Leshan client can be deployed on an android board? If so, what are the things I need to consider before doing this?
Thank you for your help.
The text was updated successfully, but these errors were encountered: