-
Notifications
You must be signed in to change notification settings - Fork 0
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
C5 emulator sleep #6
Comments
Weird. I tested all the bluetooth hardware with an emulator build before shipping, and all of them stayed connected to Android. Also tested a few against iOS and didn't see any drop outs. I'll give this a go with the fab command and see what happens. Which build number did you try? |
This is with the 7255 build. If you see something different send me your .hex file or I can send you the On Fri, Dec 5, 2014 at 5:27 PM, Michael Giannikouris <
|
Just sent a HEX over that you can try. I wonder if I was supposed to do something in fab that automatically sets DEFAULT_POWER_MANAGEMENT=ALWAYS_ON when emulator is selected. |
I tried your firmware and I get the same behavior. Plugged into PC over With fab, I do get the ALWAYS_ON option: Compiled with options:
I'm not sure what we're doing different if you don't see the same behavior. Eric Marsman On Fri, Dec 5, 2014 at 6:00 PM, Michael Giannikouris <
|
I just updated to the latest iOS 8.1 and got the same behavior. |
After we spoke yesterday, it sounds more like this is the original timing issue with iOS connections, not any issue with the device power management. To find out, I've increased the time delay well beyond what is needed to avoid crashing the connection with our iOS devices. Please build the latest commit and let me know the result. |
When compiling with 'fab c5 emulator build' the resulting c5 devices connects to an iOS device over Bluetooth, but only for a few (<5) seconds. Then it goes away. Has been confirmed on 2 different C5 builds and iOS devices. Seems like emulator isn't keeping the BT alive?
The text was updated successfully, but these errors were encountered: