Description

drzacek

opened on Aug 2, 2021

Issue body actions

I think the wake-up on wrist raise is too sensitive.

While it is nice to not have to twist your arm quickly by 90 degrees to activate the screen (like on my MiBand 4), it is pointles to have it activated almost constantly during normal day activities.

My PineTime lights up even when I'm driving on a highway and barely turn the steering wheel.

I think that battery life suffer greatly from that. Maybe tuning it down a little bit might be a good idea.

Reacted by Ross Maspero, hatmajster, Alexander Tretyakov, Brian Douglass, Heinrich Ulbricht, hellojaccc, mjnck, Jue and Mario Ebenhofer

Activity

1. Dperrigo18 commented on Aug 2, 2021

   

   Dperrigo18

   on Aug 2, 2021

   More actions

   I would recommend something like a sensitivity slider in the settings for this would be good.
   That way the user could fine tune it to what would be acceptable for them.

   Reacted by Heinrich Ulbricht, Gerald Schneider, Brian Douglass, hellojaccc and mjnck
2. atomdmac commented on Aug 3, 2021

   

   atomdmac

   on Aug 3, 2021

   More actions

   #490
3. hubmartin commented on Aug 3, 2021

   

   hubmartin

   on Aug 3, 2021

   Contributor

   More actions

   I did some experiments with Colmi P8 LIS2DH12 (chinese copy) accelerometer filtering because it was also turning on too often. I solved that by averaging last accelerometer 4 values. I have also 100Hz sampling and 2g range (reading over I2C seems like 10 Hz over my scope)
   https://github.com/hubmartin/InfiniTime/blob/64758b76247ccbb25c5ee84786b60d34618aa277/src/drivers/Bma421.cpp#L126

   Today the PineTime arrived so I did a test and PineTime BMA accelerometer code is really too much sensitive. Comparison video.
   https://photos.app.goo.gl/pEP5nXSFnpNkJMQcA

   We can solve that by different finite state machines and "AI" but the simple average filter works actually good. It might turn on when you raise wrist with something in your hand, but it will not turn on when watches are flat and you bump into something.
   I noticed that in the BMA code there is some averaging filter in hardware. Not sure how it works or if it will need to increase that a bit.

   Reacted by Adam Macumber, Jacek, Dperrigo18, hellojaccc and BOFH90
4. drzacek commented on Aug 3, 2021

   

   drzacek

   on Aug 3, 2021

   Author

   More actions

   Averaging the last values does sound good.
   I only got mine last week and I'm still setting my build env. Once I got it working I'm gonna play around with stuff.
5. Riksu9000 commented on Aug 3, 2021

   

   Riksu9000

   on Aug 3, 2021

   Contributor

   More actions

   I have also 100Hz sampling and 2g range (reading over I2C seems like 10 Hz over my scope)

   The sensor is polled at 10Hz in systemTask. This should be improved by enabling interrupts from the sensor, and reading the values into a small buffer. The frequency might not have to be much higher than 10Hz.

   We can solve that by different finite state machines and "AI" but the simple average filter works actually good.

   There's no need to make this complicated. The current wakeup code is very basic. With a small buffer and a bit higher update frequency it could easily be improved by requiring some velocity rather than looking at just the angle.

   https://github.com/JF002/InfiniTime/blob/514481ef7f9c71ad816b31d979c6ab39ce9380dd/src/components/motion/MotionController.cpp#L12
6. Avamander

   added

   enhancementEnhancement to an existing app/featureEnhancement to an existing app/feature

   on Oct 2, 2021
7. JF002

   closed this as completedin #826on Aug 17, 2023

Issue actions