On Thursday, March 20, 2014 4:44:23 AM UTC-7, gjs wrote: > > Hi, > > Risk - that B won't work as well A and (many?) users will complain. Reward > - you won't be bothered by the deprecation warnings. >
Put that way, it's a no brainer. Deprecation warnings only scratch at the perfectionist in me, if any. User complaints sap time and money that could be spent on more features and benefits for those users. However, is there risk for staying with A? That it is already broken on some devices? That it will break completely on 4.5, since we've had plenty of notice? I can't say whether A is broken yet. Every release, some user is sure to tell me I broke all compass functionality, but -Some devices have bad sensors -Some whole models have bad or nonexistent sensors. Of course they blame the app. -Users don't know how to calibrate their devices and use them near metal or magnets. - I have an algorithm that switches from static to moving direction at the right speed, and that can fail. > > A little while back I also implemented & tested method B for the same > reasons & I found that method B had more jitter (than method A) & had to be > smoothed somewhat, but worse that method B suffered from an apparent > 'gimbal lock' when pointed towards west, with the readings fluctuating > wildly when pointed at or near to 270 degrees (with the device in landscape > orientation). I only tested briefly on a few (recent & popular phone) > devices with each having the same issue so I gave up, manly due to time > constraints & continue using method A. > > My suggestion would be to implement both A & B in parallel, test/log & > compare results from both methods on as many devices as you can reasonably > try before deciding on making the change. > > To do that, I'd have to put a user setting in. Only advanced users would find that setting, but it could protect you in the event of sudden death of Method A. > I'd be interested to read about the experiences of other people on this > topic, particularly regarding the 'gimbal lock' for method B. > Me too. Nathan -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
