RE: Connection interval problem

sonnyz — Sat, 06 Jan 2018 17:16:14 GMT

Thank you very much Endnode! I have tried what you suggested and it works well!

RE: Connection interval problem

endnode — Sat, 06 Jan 2018 12:07:59 GMT

First problem is that even Apple don' follow their own recommendations. They are not updating it either, they basically don't care nowadays. Secondly all rich OS platforms like Android/iOS/Windows don't like long connection intervals. They don't like super short either, so the best is to settle with their typical value (iOS natively 30ms, Android 48.75ms, Windows 50 or 60ms - don't remember right now). If you really want to save some power by going beyond 100ms then you are in the shadow area of try and error. Which is what you experience right now I believe. I would say you should rather feel lucky that some values work, regardless how "random" and illogical they look;) I would personally consider settling down to default min = 30ms max = 60ms and use slave latency to really save power (you should be fine to set values like 8 or even more which would effectively bring you into 400-1200ms range).