Thanks I have an idea what might be causing the crash.
Do you have any guidance on the stepcount issue?
Search found 10 matches
- Tue Jul 18, 2017 8:20 pm
- Forum: Stable Version
- Topic: Anyone know how to get accurate step count since 4.1.0
- Replies: 2
- Views: 3537
- Tue Jul 18, 2017 5:20 pm
- Forum: Beta Version
- Topic: WatchMaker Premium Faces Steps Not Showing
- Replies: 14
- Views: 20251
Re: WatchMaker Premium Faces Steps Not Showing
Hi I'm Alex the WM dev - I did't get the mail but thanks for trying. I created another thread which was approved today but I can repost here : http://forum.ticwear.com/viewtopic.php?f=7&t=2228 I am getting many reports of 0 stepcount since Ticwear 4.10 update. We use the standard sensor count code -...
- Fri Jul 14, 2017 3:51 pm
- Forum: Stable Version
- Topic: Anyone know how to get accurate step count since 4.1.0
- Replies: 2
- Views: 3537
Anyone know how to get accurate step count since 4.1.0
I am the WatchMaker dev and getting many reports of 0 stepcount since Ticwear 4.10 update. We use the standard sensor count code - is there something else we should be doing since Ticwear 4.10 update? m_sensorManager.registerListener(m_sensorListener, m_sensorManager.getDefaultSensor(Sensor_TYPE_STE...
- Wed Mar 15, 2017 9:30 pm
- Forum: General
- Topic: Watchmaker beta for iOS!!
- Replies: 15
- Views: 16217
Re: Watchmaker beta for iOS!!
We have submitted the standalone watch app to Mobvoi which is currently under review.
This will make it possible for Ticwatch2 users to install without adb.
This will make it possible for Ticwatch2 users to install without adb.
- Wed Mar 01, 2017 10:53 am
- Forum: TicWatch Development
- Topic: Detect when notifications window is visible
- Replies: 0
- Views: 2460
Detect when notifications window is visible
I want to detect this so that WatchMaker will not allow click-through to tap actions beneath this window.
Neither onVisibilityChanged nor onAmbientModeChanged are being called.
Neither onVisibilityChanged nor onAmbientModeChanged are being called.
- Wed Mar 01, 2017 10:33 am
- Forum: TicWatch Development
- Topic: Intents to launch calendar and voice search
- Replies: 0
- Views: 2239
Intents to launch calendar and voice search
Anyone know these for Ticwear?
I am trying to add them as defaults for WatchMaker.
I am trying to add them as defaults for WatchMaker.
- Fri Feb 24, 2017 9:50 am
- Forum: TicWatch Development
- Topic: Appkey mismatch
- Replies: 3
- Views: 4772
Re: Appkey mismatch
I confirmed with Yongce at Ticwatch that appkeys can be cached on the device.
So recommendation at minimum is to reboot phone and watch.
So recommendation at minimum is to reboot phone and watch.
- Thu Feb 23, 2017 12:15 pm
- Forum: TicWatch Development
- Topic: Appkey mismatch
- Replies: 3
- Views: 4772
Appkey mismatch
We launched Ticwatch2 support for WatchMaker in beta yesterday. We are getting mixed results with some users eventually getting it working after many reinstalls etc. In all cases the problems seem to come from mismatched keys between mobile and wear. W/AppKeyRegister(19804): signature mismatch for p...
- Wed Feb 22, 2017 9:12 am
- Forum: TicWatch Development
- Topic: Reliable way of detecting a Ticwatch
- Replies: 3
- Views: 4497
Re: Reliable way of detecting a Ticwatch
I'm the WatchMaker dev!
- Fri Feb 17, 2017 10:55 am
- Forum: TicWatch Development
- Topic: Reliable way of detecting a Ticwatch
- Replies: 3
- Views: 4497
Reliable way of detecting a Ticwatch
I am writing my wearable code to run on Android Wear and Ticwatch. What is a reliable way of checking if the current device is a Ticwatch and therefore needs to send all data and message requests using Mobvoi API. e.g. something like android.os.Build.MODEL.startsWith("Ticwatch") although I dont thin...