Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High Pebble Battery Usage #1

Open
jones139 opened this issue Feb 15, 2016 · 3 comments
Open

High Pebble Battery Usage #1

jones139 opened this issue Feb 15, 2016 · 3 comments

Comments

@jones139
Copy link
Member

Pebble battery usage very high - can flatten battery in <24 h.
Consider reducing data transfer rate to reduce bluetooth comms.

@shymega
Copy link

shymega commented Jun 10, 2018

I just wanted to add my experiences here. I have a Pebble 2 HR watch, and from 100% to just overnight (~8-9 hours), it goes down to about 50%. Just wondering, would #3 help with this?

Background: I have been diagnosed with epilepsy myself, so I'm happy to contribute as much as I can to this project, in order to further enhance my computer program for helping with my seizures as well :-)

Really good work you're doing here though, its amazing stuff.

@jones139
Copy link
Member Author

Hi. Thank you for getting in touch.
Issue 3 is about running as a background process. I am confident that it would not alter battery consumption, as I am pretty sure that the battery consumption is dominated by the bluetooth communication. I forgot this issue was open, because I added some notes to the web site a few weeks ago (http://www.openseizuredetector.org.uk/?p=1040), and should have added it here - increasing the data transfer period up to 30 seconds makes quite a big difference to battery life - I'd be interested to know if it does the same on Pebble 2 because I don't have one of those to test on.

It would be great to receive whatever contributions you would like to make - if you would like me to explain how the seizure detector code or alarm system works a bit better let me know, and I will write a little developers guide - I have never quite got around to that!
Cheers

Graham

@shymega
Copy link

shymega commented Jun 15, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants