Experimentar problemas con Spleeft es posible, debido a que cada smarphone, especialmente los Android, tienen diferentes tipos de acelerómetros y gamas de los mismos.Aquí te dejamos algunos consejos para solventar o ayudara mejorar algunos de los problemas más comunes basados en el gran feedback de nuestros usuarios.
Estamos trabajando en traeros actualizaciones específicas para intentar solucionar cada uno de ellos
En general, la app demanda mucha capacidad a la CPU del teléfono, por lo que trata de utilizarlo con suficiente memoria (tanto en la RAM como el almacenamiento interno) y batería, especialmente en la versión de Android.
Problema 1. El acelerómetro no me ofrece ningún tipo de medición o feedback.
This type of problem is very common along Android users, even those with high-quality phones. Remember that the app just measure the velocity on the vertical axes, so movements like leg extension, for example, will not be measured.
Spleeft implements some filters to reduce the signal noise-induced errors. Those filters are adjusted dynamically by the app based on the data of the previous reps. of the series. Spleeft set as an acceptable range (that is not considered a measurement error) 35% below and above the mean range of motion of the series. For the velocity, Spleeft considers a measurement error a velocity loss of 40% below the mean of the series.
Si tienes problemas con repeticiones que no son contadas, prueba las siguientes recomendaciones:
– Try to calibrate your phone’s sensor with the app at the real-time velocity screen (just for Android). Check if the deviation from 0 m/s2 when the phone is not moving is significant, and calibrate that error if needed.
– Another option is to disable automatic filters in settings and set the range of motion filter and the velocity filter to the minimum. In that case, maybe the app counts more reps than you have performed but just try. Then you have to adjust your filters depending on the movement you will do (i.e if you perform squats normally with 60 kg and 0.6 m/s set a velocity threshold of 0.4 m/s). The closer the filter value is to the actual value, the more accurate the measurement will be. However, the more likely it is that a real repeat will not be displayed.
Recomendamos establecer filtros manuales de 20 cm por debajo del ROM previsto y de 0,2 m/s por debajo del valor de velocidad previsto.
Pruebalo realizando sentadillas con tu peso corporal y tu smartphone en tus manos.
Problema 2. El feedback de velocidad no se ofrece de manera instantánea.
Some users, both on iOS and Android, do not receive the velocity feedback instantaneously after finishing the concentric phase of the movement. This is due to the noise that the accelerometer detects because of the explosive final of the movement (the bar oscillates due to the final thrust for a few seconds.). Spleeft looks for zero acceleration to calibrate the accelerometer signal and give the velocity feedback. However, maybe some athletes start the next rep. without reaching the zero velocity and listening to the velocity feedback, which can let to non-counted reps and lack of feedback. We will fix this issue by implementing more noise filters to smooth the signal, but it is recommended to wait until the velocity feedback to get accurate measurements. In the sports science literature, this strategy is called cluster set.
¿Está experimentando con otro tipo de error de medición o problema que le gustaría compartir con nosotros? Póngase en contacto con nosotros aquí.
