android - Gear Fit. Samsung cup SDK doesn't works after reboot -


i'm trying add gear fit support software.

basically when known event occurs try create dialog on gear showing data.

well works expected when run software after brand new installation,and continues work until phone reboot. after reboot dialog on gear fit doesn't appear anymore.

test executed on note2 , note 3 running android 4 , android 5. both same results.

when works logcat show like.

04-14 18:25:17.570: i/scupdialog(17663): new dialog (100) 04-14 18:25:17.590: w/contextimpl(17663): implicit intents startservice not safe: intent { act=com.samsung.android.sdk.cup.scupservice } android.content.contextwrapper.bindservice:559 com.samsung.android.sdk.cup.scupservicecommunicator.connect:-1 com.samsung.android.sdk.cup.scupdialog.construction:-1  04-14 18:25:17.600: d/vibratorservice(754): turning vibrator off - immvibe. 04-14 18:25:17.600: v/vibratorservice(754): vibratemagnitude - package: com.villa.android.orari3, ms: 2000, token: null, magnitude: 2000 04-14 18:25:17.620: i/scupservice(1391): setcallback com.villa.android.orari3 04-14 18:25:17.620: d/scupservice(1391): found app id = 3 04-14 18:25:17.620: d/scupservice(1391): isconnected..  04-14 18:25:17.630: i/scupdialog(17663): add dialog (100) 04-14 18:25:17.640: i/scupservice(1391): sendcommand() 04-14 18:25:17.640: d/scupservice(1391): command type : command_data 

while after reboot behaviour different

04-14 18:19:08.221: i/scupdialog(10822): new dialog (101) 04-14 18:19:08.231: w/contextimpl(10822): implicit intents startservice not safe: intent { act=com.samsung.android.sdk.cup.scupservice } android.content.contextwrapper.bindservice:559 com.samsung.android.sdk.cup.scupservicecommunicator.connect:-1 com.samsung.android.sdk.cup.scupdialog.construction:-1  04-14 18:19:08.241: i/scupdialog(10822): add dialog (101) 04-14 18:19:08.251: i/scupservice(1391): sendcommand() 04-14 18:19:08.261: e/scupservice(1391): fail find client info.  04-14 18:19:08.261: e/scupservice(1391): package name : com.villa.android.orari3 04-14 18:19:08.261: d/vibratorservice(754): turning vibrator off - immvibe. 04-14 18:19:08.271: v/vibratorservice(754): vibratemagnitude - package: com.villa.android.orari3, ms: 2000, token: null, magnitude: 2000 

has experienced behavior ?

thanks suggestions.

neod

well diy , solve. cares.. problem located in manifest file. intent filter definition located in wrong place. during first installation cupservice function put application in list of "authorized applications. allow program works after first installation. when reboot occurs, scupservice scan application in order find "authorized" one. intent filter definition in wrong position means not allowed.... , reason why program not able drive gear fit anymore.

i hope else.

neod


Comments

Popular posts from this blog

css - SVG using textPath a symbol not rendering in Firefox -

Java 8 + Maven Javadoc plugin: Error fetching URL -

node.js - How to abort query on demand using Neo4j drivers -