[MOD-2314] Core Motion Pedometer Not Giving Correct Step Count

Description

var CoreMotion = require("ti.coremotion"); 
if (CoreMotion.isStepCountingAvailable()) { 
	// If it can, it starts the step counter and outputs the data to the console 
	CoreMotion.startStepCountingUpdates({stepCounts: 1}, function(e) { 
	//$.stepLabel.text = e.numberOfSteps; 
	// Ti.API.info(JSON.stringify(e.numberOfSteps)); 
	//CoreMotion.startStepCountingUpdates({stepCounts: 1}, function(e){ 
Ti.API.info(JSON.stringify(e.numberOfSteps)); 
 $.stepLabel.text = JSON.stringify(e.numberOfSteps); 
	}); 
	} 

var CoreMotion = require("ti.coremotion"); 

var pedometer = CoreMotion.createPedometer(); 

if(pedometer.isStepCountingAvailable()){ 
	$.stepLabel.text = "IT IS NOW!"; 
	pedometer.startPedometerUpdates({ 
	start: new Date(new Date().getTime() - 60 * 60 * 1000) 
	}, function(e) { 
	$.stepLabel.text = e.numberOfSteps; 
	}); 
} 

Attachments

Comments

1. Sharif AbuDarda 2016-03-03 Hello, Please provide a full reproducible Alloy code which demonstrate the issue. Also provide the full steps to follow. We will try to regenerate the issue in our environment. Thanks.
2. Taylor Thompson 2016-03-03 Can you tell me how I can get you the attached project? It's 50mb and the size limit on attachments is 10MB? I cannot post this project to GIT.
3. Taylor Thompson 2016-03-03 I was able to attach the projects app directory with the code in it?
4. Chee Kiat Ng 2016-03-06 Hi may i know the coremotion module version you are using?
5. Hans Knöchel 2016-03-06 The fact that http://docs.appcelerator.com/platform/latest/#!/api/Modules.CoreMotion does not show the latest docs is a DOC issue that should be filed for [~bimmel]. Probably something isn't deployed correctly. Regarding the module itself, I guess you're using the latest 2.0.0 version which is pre-packaged in the latest Ti-release, coming from https://github.com/appcelerator-modules/ti.coremotion. I will debug the issue over the next days, thanks!
6. Hans Knöchel 2016-03-06 UPDATE: The method definitely returns the correct number of steps, bubbled from the native API. The difference between the two methods is, that the first one (startStepCountingUpdates) triggers the callback after a certain number of steps is reached. The new API provided by Apple (bridged to startPedometerUpdates) is based on a start date. That's why you receive 200 steps, because that's the number of steps in the last hour (60*60*1000). So if you want to use the step counter API, there is no problem in doing that, but Apple still courages to migrate it to the new API, that's why we also deprecated it. Considering that, I wouldn't and can't change anything, except of clarifying this behavior in the docs. Thanks!
7. Motiur Rahman 2016-03-06 Hi, I also, get the similar behaviour as like reporter, new Pedometer code that gives inaccurate value but old code that seems to work correctly. *Steps To Reproduce:* 1. Create an Alloy app. 2. Replace the reporter attached code. 3. Import "ti.coremotion" module into the tiapp.xml file. 4. Run the app to the iPhone device. *Testing Environment:* Operating System Name = Mac OS X Version = 10.11.3 Architecture = 64bit # CPUs = 4 Memory = 8589934592 Node.js Node.js Version = 4.2.2 npm Version = 2.14.7 Titanium CLI CLI Version = 5.0.6 Titanium SDK SDK Version = 5.2.0.GA, 5.1.2.GA Target Platform = iphone Module Version: 2.0.0 iOS device version : 9.2.1 Thanks.
8. Hans Knöchel 2016-03-06 [~morahman] Did you read me comment above? It's no inaccurate value, it's just a different one. Further reading about the behavior [here (Example)](http://pinkstone.co.uk/how-to-access-the-step-counter-and-pedometer-data-in-ios-9/) and [here (Apple docs)](https://developer.apple.com/library/prerelease/ios/documentation/CoreMotion/Reference/CMPedometer_class/index.html#//apple_ref/occ/instm/CMPedometer/startPedometerUpdatesFromDate:withHandler:). If we use new Date() instead (which is the current date), it should give similar/same values. [~TaylorThompson] please validate so we can close this one, thank you for bringing up!
9. Taylor Thompson 2016-03-07 This still isn't giving me the behavior I'd expect. I changed the start: line to three different things below: start: new Date() start: new Date(new Date()) start: new Date(new Date().getTime()) All of which give me similar behavior and I even have logic in my code so when I press a button it's supposed to give me back the last minute count of steps as what was provided in the documentation: $.btn.addEventListener('click', function(e){    pedometer.queryPedometerData({        start: new Date(new Date().getTime() - 60*1000),         end: new Date()    }, function (e) {            $.stepHistory.text = "You walked " + e.numberOfSteps + " steps in the last minute.";    });}); When I deploy to phone and shake 10 times I get an output of around 170-180 and another 10 steps results in 300-400. When clicking the button to give me the last minute worth of steps I get the same number. What I'd expect is if I walk 10 steps, I'd get a number close to 10? I'm just trying to figure out how to get there... SDK 5.2.0 GA Target Platform = iphoneModule Version: 2.0.0 iOS device version : 9.2.1
10. Taylor Thompson 2016-03-14 Hey Hans, Just wanted to check and see if you've been able to take another look at this yet? I tested the code above and still ended up with a value I didn't expect. I'm just trying to figure out what I need to do to get a value that I'd expect like what I get using the old code. In other words, if I walk 10 steps I'm needing to get a value close to 10. TT
11. Hans Knöchel 2016-03-20 Hey Taylor. Just thought the fact that it could be a thread-related issue. If you set <run-on-main-thread>true</run-on-main-thread> inside the <ios> section of your tiapp.xml, does that change something? EDIT: Or try [this version](https://www.dropbox.com/s/dpxhwa5hjsczm2c/ti.coremotion-iphone-2.0.1.zip?dl=0). Thanks!
12. Taylor Thompson 2016-03-21 I've tried both to run on main thread as well as use the new CoreMotion module you sent. Instead of returning (e.numberOfSteps) I've changed it to return e. Looking at the screenshot I've linked below, you can see where it shows a time difference of about 10 seconds in the start and end date. However, the numberOfSteps value is 226 which can't possible be correct. https://oneok.sharefile.com/d-s9c9d60f9953477b9
13. Taylor Thompson 2016-03-25 What's the status on this?
14. Hans Knöchel 2016-03-25 I'm working on a native example to compare it 1:1, but as we have other issues to also work on, it will take some more time here.
15. Taylor Thompson 2016-04-19 Hans, Any update on this yet? Do you know if there is any way to get health data out of the default iOS Health app as a workaround?
16. Hans Knöchel 2016-04-19 Hey Taylor! Unfortunately not, yet. Too many different things to work on. If you want to help me, grab one of the demo apps from the web accessing the Pedometer API and log your results here. I didn't forget the issue, but please give me some more time to sort things out.
17. Hans Knöchel 2016-11-05 [~TaylorThompson] You can still get the data from HealthKit (use Ti.HealthKit), but I still don't get how the data can be differently like natively, since no custom logic is applied. I will hand this one over to [~vijaysingh] have a second pair of eyes on it.
18. Vijay Singh 2016-11-18 This issue is in Core motion module. So moving it to Module .
19. Vijay Singh 2016-11-18 CMPedometerData properties "numberOfSteps" , "distance" etc., in Coremotion framework of apple , are NSNumber object type . In our code we were converting these properties to NSNumber assuming they are Int . PR: https://github.com/appcelerator-modules/ti.coremotion/pull/16
20. Hans Knöchel 2016-11-18 Hey [~TaylorThompson], can you test [ti.coremotion-iphone-2.0.1.zip](https://www.dropbox.com/s/dpxhwa5hjsczm2c/ti.coremotion-iphone-2.0.1.zip?dl=0) with yout setup? I know it has been a while, but the changes in the casting could actually do the difference. Thank you!
21. Hans Knöchel 2016-11-21 Test-Case:

        var CoreMotion = require("ti.coremotion"); 
         
        var pedometer = CoreMotion.createPedometer(); 
        
        var win = Ti.UI.createWindow({
            backgroundColor: "#fff"
        });
        
        var btn = Ti.UI.createButton({
            title: "Start counting"
        });
        
        var stepLabel = Ti.UI.createLabel({
             top: 75
        });
        
        btn.addEventListener("click", function() {
           if (pedometer.isStepCountingAvailable()) { 
               stepLabel.text = "IT IS NOW!"; 
               pedometer.startPedometerUpdates({ 
                   start: new Date(new Date().getTime() - 60 * 60 * 1000) 
               }, function(e) { 
                   stepLabel.text = e.numberOfSteps; 
               }); 
           } 
        });
        
        win.add(stepLabel);
        win.add(btn);
        win.open();
        

22. Hans Knöchel 2016-11-21 New release: https://github.com/appcelerator-modules/ti.coremotion/releases/tag/v2.0.1
23. Eric Merriman 2018-08-06 Cleaning up older fixed issues. If this issue should not have been closed as fixed, please reopen.

JSON Source