Hi Tim, I found the bug from the CA layer which leads to map-functioning of ?Resource Discovery & Messaging? Here is the lira report for this. (https://jira.iotivity.org/browse/IOT-529 <https://jira.iotivity.org/browse/IOT-529>)
I apologize if I have interrupted the discussion with a different issue on this mailing list. Thank you. Jay. > 2015. 5. 23., ?? 11:18, Junghyun Oh <jhvics1 at gmail.com> ??: > > Hi Tim, > > Thanks for the information. > However, the simple-client still does not able to discover the server > even-though I?ve manually changed the DEFAULT_INTERFACE to ?oic.if.baseline?. > > This is the test environment that I?m using for this test. > - IDE : Android Studio > - Apps. & Devices > : Simpleserver on Android Phone A (Lolly-Pop) > : Simpleclient on Android Phone B (Lolly-Pop) > - Network : WIFI Local network. > - Test > 1. Run Simpleserver on Android Phone A > 2. Run Simpleclient on Android Phone B > 3. Simpleclient on Andoird Phone B does not report anything.. > > Could you check this? > > Thank you. > Jay. > >> 2015. 5. 23., ?? 11:49, Kourt, Tim A <tim.a.kourt at intel.com >> <mailto:tim.a.kourt at intel.com>> ??: >> >> Hi Jay, >> >> Thank you for reporting it. There was a bug introduced during the spec. >> compliance change (https://gerrit.iotivity.org/gerrit/#/c/956/ >> <https://gerrit.iotivity.org/gerrit/#/c/956/>) that has prevented the >> discovery of the resources on Android. You may find a fix here: >> https://gerrit.iotivity.org/gerrit/#/c/1103/ >> <https://gerrit.iotivity.org/gerrit/#/c/1103/> >> >> We are working to automate the Android tests to be run by the build system. >> This will prevent the Android runtime breaking commits to the IoTivity code >> base. >> >> The mismatch between the number of .so files outlined in >> BuildInstructionsForAndroidAPI.txt and reality is caused by the removal of >> coap and glib libraries. We need to update the info. >> >> The simpleserver and simpleclient apps should be fine now. >> >> Thank you, >> Tim Kourt >> >> PS: By the way, the UsatisfiedLinkError in the subject line of this thread >> was caused by the unmaintained android_api branch. <> >> >> >> From: iotivity-dev-bounces at lists.iotivity.org >> <mailto:iotivity-dev-bounces at lists.iotivity.org> >> [mailto:iotivity-dev-bounces at lists.iotivity.org >> <mailto:iotivity-dev-bounces at lists.iotivity.org>] On Behalf Of Junghyun Oh >> Sent: Friday, May 22, 2015 10:37 AM >> To: Lenahan, Charlie >> Cc: iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at >> lists.iotivity.org> >> Subject: Re: [dev] UsatisfiedLinkError on android >> >> I?m also facing a problem when I tried to test the android version of the >> Simpleserver & Simpleclient. >> >> I have successfully built iotivity for android platform with build script >> as.. >> >> ?scons TARGET_OS=android TARGET_ARCH=armeabi TARGET_TRANSPORT=IP RELEASE=1? >> >> described Readme.scons.txt file. >> >> However, the client couldn?t find the server on the android phone. >> >> Here are the questions.. >> >> 1. In the ?BuildInstructionsForAndroidAPI.txt, it says to verify that 9 >> different *.so files exist >> in the ~~/base/libs/armeabi/.. >> However, there?re only 7 so files in the directory and those are.. >> 1. libca-interface.so >> 2. libconnectivity-abstraction.so >> 3. libgnustl-shared.so >> 4. liboc_logger.so >> 5. liboc.so >> 6. libotbcstack.so >> 7. libocstack-jni.so >> >> What are the missing .so files, and don?t we need to have libcoap?? >> >> 2. When I compare the output *.so files between linux-version & >> android-version, however, >> the total number of files were not the same. >> Is it the expected result??? >> >> 3. Are those Android version of the Simpleserver & Simpleclient working >> codes? >> >> Thank you. >> Jay. >> >> 2015. 5. 23., ?? 2:06, Lenahan, Charlie <charlie.lenahan at intel.com >> <mailto:charlie.lenahan at intel.com>> ??: >> >> It looks like its erroring out in CALEGetBuildVersion when it trying to >> get the android SDK version number by making JNI calls or >> org.iotivity.jar.caedrinterface class is not found in the .apk. >> >> I?d personally switch that code to using >> property_get(?ro.build.version.sdk?,?) to keep the code in native land. >> >> Also, all that JNI code has no try-catch?es around it, but looks to be in >> C API code, so that seems bad. >> >> >> From: Davi Di?rio Mendes <ddioriomendes at gmail.com <mailto:ddioriomendes >> at gmail.com>> >> Date: Friday, May 22, 2015 at 12:06 PM >> To: Patrick Lankswert <patrick.lankswert at intel.com >> <mailto:patrick.lankswert at intel.com>> >> Cc: "iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at >> lists.iotivity.org>" <iotivity-dev at lists.iotivity.org >> <mailto:iotivity-dev at lists.iotivity.org>> >> Subject: Re: [dev] UsatisfiedLinkError on android >> >> >> I upgraded my android to api 21, now I am getting another error. >> 05-22 11:08:56.079 18181-18181/org.iotivity.base.examples.simpleserver >> A/art? sart/runtime/check_jni.cc:65] JNI DETECTED ERROR IN APPLICATION: >> JNI FindClass called with pending exception >> 'java.lang.ClassNotFoundException' >> thrown in unknown throw location >> >> The logcat is attached. This error is at line 106. >> >> At line 108 : >> >> 05-22 11:08:56.079 18181-18181/org.iotivity.base.examples.simpleserver >> A/art? sart/runtime/check_jni.cc:65] from void >> org.iotivity.ca.CaInterface.initialize(android.content.Context) >> >> Sorry Patrick, I sent the response just to you... >> >> Thanks for response. >> >> >> 2015-05-22 12:43 GMT-03:00 Lankswert, Patrick >> <patrick.lankswert at intel.com <mailto:patrick.lankswert at intel.com>>: >> >> Tim, >> >> We aspire to make the sample applications part of the build process so >> that any API change that may break a sample application can be caught >> early and part of the review process. >> >> I have downloaded SDKs with broken samples in the past and always thought >> "these jokers have got to be kidding me". Now, I am trying to not be the >> jokers. :) >> >> Pat >> >> >> -----Original Message----- >> From: iotivity-dev-bounces at lists.iotivity.org >> <mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:iotivity-dev- >> bounces at lists.iotivity.org <mailto:bounces at lists.iotivity.org>] On >> Behalf Of Kourt, Tim A >> Sent: Thursday, May 21, 2015 10:31 PM >> To: Hudson, Douglas; Keane, Erich; ddioriomendes at gmail.com >> <mailto:ddioriomendes at gmail.com> >> Cc: iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at >> lists.iotivity.org> >> Subject: Re: [dev] UsatisfiedLinkError on android >> >> Doug, >> >> The build server doesn't currently build examples for Android, since we >> didn't see any immediate need for automating this step. Instead, we >> provide >> the instructions on how to proceed with Android Studio. At the same time >> the opportunity is open. >> >> Thanks, >> Tim >> >> -----Original Message----- >> From: iotivity-dev-bounces at lists.iotivity.org >> <mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:iotivity-dev- >> bounces at lists.iotivity.org <mailto:bounces at lists.iotivity.org>] On >> Behalf Of Hudson, Douglas >> Sent: Thursday, May 21, 2015 1:36 PM >> To: Keane, Erich; ddioriomendes at gmail.com <mailto:ddioriomendes at >> gmail.com> >> Cc: iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at >> lists.iotivity.org> >> Subject: Re: [dev] UsatisfiedLinkError on android >> >> It is my understanding that the build server does a build for Android, >> so I >> would have thought that if the Android samples were missed then the build >> server should have caught it when the changeset went to Gerrit. Am I off >> track? >> >> --Doug >> >> -----Original Message----- >> From: iotivity-dev-bounces at lists.iotivity.org >> <mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:iotivity-dev- >> bounces at lists.iotivity.org <mailto:bounces at lists.iotivity.org>] On >> Behalf Of Keane, Erich >> Sent: Thursday, May 21, 2015 1:32 PM >> To: ddioriomendes at gmail.com <mailto:ddioriomendes at gmail.com> >> Cc: iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at >> lists.iotivity.org> >> Subject: Re: [dev] UsatisfiedLinkError on android >> >> So, OcConnectivityType was changed to no longer contain WIFI or Ethernet. >> It is now supposed to be IPV4 or IPV6, some of the samples were likely >> missed when we made that switchover. In the meantime, feel free to >> either >> fix locally (or submit a patch?) by switching the .WIFI or .Ethernets >> that you >> find over to .IPV4. >> >> I'm not sure about the boost stuff, it SHOULD be downloading it every >> time. >> The one thing that I found that can cause problems is the 'dep' >> directory in the iotivity root. I'd suggest deleting the entire >> directory, as well >> as everything in extlibs/boost (other than the Sconscript file!) and >> trying >> again. >> >> As far as the exception below, pthread_condattr_setclock seems to be >> missing. I believe we require NDK version r10d, if you have an earlier >> version >> of the NDK, android might not build. >> >> -Erich >> >> On Thu, 2015-05-21 at 14:25 -0300, Davi Di?rio Mendes wrote: >> >> Hi all, >> >> >> I am wonrking on master branch, commit >> 887d789ee50b0d2ca5e520d872aeb507ddbd0f31. >> >> >> I builded iotivity for android following wiki guide, now I get this >> error when run simpleserver or another else server example. In the >> clients gradle cannot find OcConnectivityType.WIFI. >> >> >> Does someone have a lead? Is not the master branch ready to work? >> >> >> I tried to build in android-api branch but the build script does not >> download boost, then stop compiling because can not find >> boost/lexical_cast.hpp. If I download boost by hand and unpack it in >> extlibs/boost, it still not finding dependencies. >> >> >> I know you are working at 0.91 release, sorry bothering with minor >> things. But I have a lecture scheduled to Friday, next week, and I do >> not want to do a checkout back to what I used. I would like to show >> what is actually done. >> >> >> Thanks. >> >> >> 05-21 14:05:58.337 >> 19920-19920/org.iotivity.base.examples.simpleserver >> E/AndroidRuntime? FATAL EXCEPTION: main >> Process: org.iotivity.base.examples.simpleserver, PID: 19920 >> java.lang.UnsatisfiedLinkError: dlopen failed: could not load >> library "liboctbstack.so" needed by "liboc.so"; caused by could not >> load library "libconnectivity_abstraction.so" needed by >> "liboctbstack.so"; caused by cannot locate symbol >> "pthread_condattr_setclock" referenced by >> "libconnectivity_abstraction.so"... >> at java.lang.Runtime.loadLibrary(Runtime.java:365) >> at java.lang.System.loadLibrary(System.java:526) >> at >> org.iotivity.base.OcRepresentation.<clinit>(OcRepresentation.java:35) >> at >> >> org.iotivity.base.examples.simpleserver.SimpleServer.onCreate(SimpleServ >> er.java:72) >> >> at android.app.Activity.performCreate(Activity.java:5458) >> at >> >> android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:109 >> 3) >> >> at >> >> >> android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2376) >> >> at >> >> android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2470) >> >> at android.app.ActivityThread.access >> $900(ActivityThread.java:174) >> at android.app.ActivityThread >> $H.handleMessage(ActivityThread.java:1307) >> at android.os.Handler.dispatchMessage(Handler.java:102) >> at android.os.Looper.loop(Looper.java:146) >> at >> android.app.ActivityThread.main(ActivityThread.java:5593) >> at java.lang.reflect.Method.invokeNative(Native Method) >> at java.lang.reflect.Method.invoke(Method.java:515) >> at com.android.internal.os.ZygoteInit >> $MethodAndArgsCaller.run(ZygoteInit.java:1283) >> at >> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1099) >> at dalvik.system.NativeStart.main(Native Method) >> >> >> >> >> -- >> Davi Di?rio Mendes >> Eng. de Computa??o - Turma de 2011 >> Universidade de S?o Paulo - EESC/ICMC >> >> _______________________________________________ >> iotivity-dev mailing list >> iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at >> lists.iotivity.org> >> https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> <https://lists.iotivity.org/mailman/listinfo/iotivity-dev> >> <https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> <https://lists.iotivity.org/mailman/listinfo/iotivity-dev>> >> >> >> _______________________________________________ >> iotivity-dev mailing list >> iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at >> lists.iotivity.org> >> https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> <https://lists.iotivity.org/mailman/listinfo/iotivity-dev> >> <https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> <https://lists.iotivity.org/mailman/listinfo/iotivity-dev>> >> >> _______________________________________________ >> iotivity-dev mailing list >> iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at >> lists.iotivity.org> >> https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> <https://lists.iotivity.org/mailman/listinfo/iotivity-dev> >> <https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> <https://lists.iotivity.org/mailman/listinfo/iotivity-dev>> >> >> _______________________________________________ >> iotivity-dev mailing list >> iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at >> lists.iotivity.org> >> https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> <https://lists.iotivity.org/mailman/listinfo/iotivity-dev> >> <https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> <https://lists.iotivity.org/mailman/listinfo/iotivity-dev>> >> >> >> >> >> >> >> >> >> -- >> Davi Di?rio Mendes >> Eng. de Computa??o - Turma de 2011 >> Universidade de S?o Paulo - EESC/ICMC >> >> _______________________________________________ >> iotivity-dev mailing list >> iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at >> lists.iotivity.org> >> https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> <https://lists.iotivity.org/mailman/listinfo/iotivity-dev> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150524/0a5d5cdd/attachment.html>
