Closed GoogleCodeExporter closed 8 years ago
Original comment by rdama...@google.com
on 18 May 2010 at 2:23
This had also been filed as a feature request in the internal bugtrack, here
are the
previous comments on it:
Note that there seems to be a hardware constraint on the G1: Once the screen
switches
off the accelerometer does, too. That would mean we need to keep the screen on
all
the time, which would cause a lot of additional battery drain. This needs to be
confirmed before we start putting efforts into implementing this feature.
Original comment by rdama...@google.com
on 18 May 2010 at 2:35
The Zephyr HxM product also contains hardware to measure cadence (step-count).
Original comment by djh.sthlm
on 28 Jun 2010 at 11:23
Issue 117 has been merged into this issue.
Original comment by rdama...@google.com
on 25 Aug 2010 at 1:59
Wouldn't it be smart to use the Zephyr HxM for this as djh.sthlm mentioned?
That way it wouldn't be necessary to depend on the internal accelerometer which
implementation might differ from phone to phone.
Or are all Android phones required to have the same accelerometer
implementation?
Original comment by aaaha...@gmail.com
on 2 Sep 2010 at 10:22
I have a funny recollection from somewhere that this was an android software
bug and not a hardware constraint issue (I mean the turning off screen and
accelerometer happening together). It could be that a later android update
fixes or has already fixed this. I cannot remember where I read about this
though.
On the usage of the accelerometer I could also suggest adding a cadence feature
for cyclists (by calculating rpm from measuring up/down movement in
accelerometer assuming the phone is strapped on the cyclist's leg).
Original comment by kal...@gmail.com
on 1 Oct 2010 at 11:19
I think the hardware contraint mentioned in second post was Android bug number
3708 (http://code.google.com/p/android/issues/detail?id=3708) which has been
released, however not everyone is running latest build so may be limited
availability. Zephyr HxM support is being worked on under Issue 9, including
Cadence.
Original comment by matt...@gmail.com
on 22 Oct 2010 at 6:34
(just removing OpSys-Android label, all issues are in Android anyway)
Original comment by rdama...@google.com
on 26 Jul 2011 at 1:00
I think this would be a useful feature, implemented as cadence and distance per
step. To avoid battery drain I suggest monitoring briefly at each new
lap-count (e.g. per km) rather than continually.
Some potentially useful code may be at http://code.google.com/p/pedometer/
Original comment by miles.so...@gmail.com
on 24 Dec 2013 at 3:49
I think that Google Play Services has some pedometer functionality for Android
4.4. Maybe this can be used to track cadence during walking or running.
Original comment by 2emoo...@gmail.com
on 24 Mar 2014 at 7:15
Original comment by jshih@google.com
on 13 Oct 2014 at 9:40
Original issue reported on code.google.com by
joeell...@gmail.com
on 14 May 2010 at 12:29