Noticed an issue on Monday the 16th of November. Had old 1 year old Jabra Easygo bluetooth headset and it was working fine on my S6 Edge+. On Monday, the Jabra Easygo started beeping like when you leave your phone in the holder in your car and you walk too far away and the bluetooth beeps an alert that you are too far from your phone. But the problem was, I was standing right beside my phone. The phone and Jabra were both charged. I have been using the Jabra easygo BT headset for weeks since bought the phone in June 2015 with not one single problem. Now, it beeps, disconnects then reconnects (briefly before beeping again) connecting only for phone audio, then disconnects again and may not reconnect at all or it does and this time maybe only for media playing. Super frustrating!! The whole time beeping like I have walked 500 steps away and got out of range for the BT to connect. But I haven't.
So I am thinking - well - the Jabra Easygo - is about 1 1/2 years old or so - maybe its time to get a new BT. (Still not suspecting the phone at this point...) So I went out purchased a brand new Jabra Talk - great battery life - can stream music/Audio, easy touch buttons. "Perfect!" I say.
So I pair it up with my phone (took a bit for the phone to find it - but then it paired fine. Go figure same issue as the EasyTalk - so now I am the proud owner of 2 bluetooth devices - neither of which will connect and stay connected with this fancy a** new phone - (Now suspecting its the phone...)
So larger nutshell. Bluetooth was working fine until Nov 16 2015 (ish)
My phone was on auto update and is now Android system 5.1.1
My old bluetooth started beeping on Monday Nov 16th and disconnecting/reconnecting /not connecting - but pairs up fine
replaced old Blue tooth with brand new one and same problem
cleared cache, logged into safe mode on phone to see if it was an app that was causing the issue (it isn't)
basically have done everything except a factory reset.
Bell mobility is the carrier and have had no issues with them.
I'm going to take the phone to the bell store and see if they can figure it out - just wondered f anyone has had similar in or near same time period
Will update when/if i ever find a reason or a solution.