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

Slow messaging performance after connected a while? #21

Open
natevw opened this issue Aug 19, 2013 · 2 comments
Open

Slow messaging performance after connected a while? #21

natevw opened this issue Aug 19, 2013 · 2 comments

Comments

@natevw
Copy link

natevw commented Aug 19, 2013

I'm trying to send over an image to the watch as fast as possible. When I first start the repl, I am able to send one in about 2.5 seconds which isn't great but seems reasonable considering it takes over 50 requests to complete (unoptimized data format and lots of other message overhead means I can only send three rows at a time).

However, once the watch has been connected for a while, my app only gets a request through every second or two. So it takes over a minute to fill the screen! Why does the amount of time the watch has been connected affect this?

NOTE: I'm actually using httpebble support via Aleksandyr's branch at https://github.com/aleksandyr/libpebble but given pebble/pebblekit#31 I'm wondering if this is a lower-level Bluetooth issue.

@Hexxeh
Copy link
Owner

Hexxeh commented Aug 20, 2013

It might well not be libpebble specific, possibly just a Bluetooth stack bug on whatever device you're using?

@rjcase
Copy link

rjcase commented Aug 20, 2013

@natevw yes, it's likely that it's caused by BT sniff (power-saving) mode described in pebble/pebblekit#31

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

3 participants