{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 The star\" 的问题《WearableListenerService STICKY Vs NOT_STICKY》','https://www.manongdao.com/q-1065912.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I am trying to find the difference between having the WearableListenerService sticky or not sticky. This is because of the nature of the WearableListenerService that it does not run constantly. So is there any advantages of having it Sticky or not sticky? According to my testing, in both cases the behaviour of the service is the same. Service is created when phone reboots or when app launches. Even when it is not sticky, the wear is capable of connecting at any time, etc. Thanks!
相关问题
- Delete Messages from a Topic in Apache Kafka
- Jackson Deserialization not calling deserialize on
- How can I create this custom Bottom Navigation on
- How to maintain order of key-value in DataFrame sa
- StackExchange API - Deserialize Date in JSON Respo
In most normal cases, that service is started through binding and not explicitly by calling startService, so sticky or not doesn't make any difference. If there is a particular use case that you have in mind, feel free to share that with us to help you further.