Android Wear: DataItem API vs Channel API -


i need collect sensor data on android wear device , want stream on android smartphone. is, have regular set of values want send on phone on extended period of time. data rate not high, say, 100 samples per second, 20 bytes per measurement sample. seems either implemented series of dataitems (for dataitem api) or series of small blobs (for channelapi). both dataitem , channel apis work. there reason choose 1 or other? other questions: 1) i've read android docs , looks dataitem protocol allows caching , retransmission in case of dodgy wireless transport. channelapi also? 2) push each sample measurement on separate item (or blob) , expect these accumulate on time. makes sense once phone receives data (and copies local storage) should remove dataitem (or blob). affect data on wear device? thanks!

okay, i'm answering own question. after several months working datalayer api, can works , surprisingly robust. have 3 wear devices each pushing 100hz sensor data common android phone app , works flawlessly no data bottlenecks. works when outside , near wifi ap. regarding questions: 1) yes, caching works , have not yet encountered issue missing packets. don't know channel api though. 2) haven't found issue. 1 writes data object on wear device, issue putrequest , appears on phone side call ondatachanged(). how handled in background blissfully transparent.


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more