[Q]Galaxy s2 i9100 + bluetooth mouse. 2.3.5 breaks it. 2.3.6 fixes!

---

I just recently bought a white galaxy s2 from newegg. I have an MHL to HDMI cable incoming, and when I saw that you could use a mouse with the device, I was really excited.

link: I'm too new to post links, but search google for "magic mouse samsung s2" and the youtube link should pop up first.

However, even though I am able to pair a mouse (I've tried a magic mouse and a mini presentation Microsoft Bluetooth mouse so far) when it connects, it instantly disconnects... and it keeps doing that over and over.

Bluetooth is able to keep a connection with other devices, like a headset and transfer data over bluetooth to my computer.

When I called Samsung support, first the girl didn't know connecting to a mouse was possible, and upon seeing the video, her response was why would I ever want to do that, and there was nothing she could do to help.

I saw other threads mentioning bluetooth problems could be fixed with a factory reset, but after doing so I have identical behavior. I don't think its a hardware issue, and I applied the newest update 2.3.5... I'm really confused here. What should I do? Any other details required? Maybe my magic mouse just doesn't like my phone?

From what I have heard apple magic mouse does not connect correctly.do you or a friend have a different bt mouse to test?

Sent from my GT-I9100 using XDA App

I have now tested the Bluetooth with a Logitech lazer Bluetooth mouse, in addition to the magic mouse and Microsoft mouse, with the same results. Does anyone else have this problem? Could the mouse HID been disabled by Samsung? or should I do a hardware warantee exchange?

Sent from my GT-I9100 using XDA App

I bought a cheap (8€) noname bluetooth mouse from amazon and it works perfectly on the Galaxy S2 on the stock rom, it also works on my Galaxy S running CM7.
Are you sure you have set your mouse to pairing mode?
(I had to press the connect button for 5 seconds)

I'm sure it's pairing. I press and hold connect on the mouse until it becomes visible to my galaxy s2. It ends up showing up as paired after I tap, but when I tap again, it only connects for a second (enough that the options for that device now show me HID) but it just drops immediately. But perhaps these mice with special buttons (like the Microsoft presentation mouse) and apple mice, and the Logitech mouse, are all beyond the scope of running on the phone.

I bought a super basic and cheap bluetooth mouse ($15 cdn) from amazon, it should arrive in 1-2 weeks. I'll follow up with this then. If the phone can't connect to that, I'm going to call Samsung and ask for a hardware exchange.

Also, I may be able to get my hands on a USB host cable, to see if i can get any mouse period working.

I really can't imagine it being faulty hardware though, considering all other Bluetooth functions work? or am I incorrect in assuming that?

So I decided to see what happens with a Bluetooth keyboard, and indeed I get the same result, connecting for a second then dropping.

I'm going to exchange my unit for a new one, hopefully that solves the issue. I'm getting paranoid that something is different with the white galaxy s2, can someone extinguish those fears for me?

Sent from my GT-I9100 using XDA App

Alright, follow up post. The new phone connects to mice/keyboards fine. It is current on 2.3.3. Could someone with an updated 2.3.5 s2 just confirm that the feature still works after update?

Edit: Ok, i let me phone upgrade from 2.3.3 to 2.3.5, and nothing can pair once again. Wow. Did Sammy really remove this functionality?

Final edit: Flash stock 2.3.6, and mouse will work again. So to recap, 2.3.3 good, 2.3.6 good, 2.3.5 bad

I have an Apple Mighty Mouse which work fine with my SGS1. It doesn't connect to SGS2. Same issue, the connection drops out after a second. My SGS2 is running on 2.3.6 Batista ROM with Siyah 2.3 kernel.

HID Bluetooth killed by 2.3.5 upgrade

---

Hi, I think I have a good picture of what has happened having trawlled the net looking for answers. In summary:

2.3.3 and 2.3.4 supported and worked with bluetooth HID devices (like my sandberg mini bluetooth keyboard).
2.3.5 as suggested by Samsung key's had issues with bluetooth from the start. It all looked good until you turned bluetooth on then it went into a FREEZE, BLACK SCREEN, LOCK SCREEN cycle with a 20-30 second window at best to try and turn bluetooth off once you realised it, repeating "ad infinitum".
Some folks found that a factory reset cured this. I got a replacement from Otrange UK after a lengthy discussion!
BUT however you may have fixed this is seems that any bluetooth HID device (Mouse, Keyboard) will not stay connected against 2.3.5. They pair ok, they even actually connect for a fraction of a second then bomb out again.
I just spoke to Orange UK Tech who in turn spoke to Samsung who said they were "Not aware" of the issue but would "Escalate a resolution" and get back to me. 2.3.6 is supposedly about to come out for Orange UK within "2 Months" and will contain a fix. Apparently. Looking at other stuff, 2.3.6 does appear to be the best hope.
They confirmed something though; 2.3.5 back to 2.3.3 / 2.3.4 is not supported/advised/safe so waiting for the new version is the only hope.

All this, so the lists won't bounce a'la APPLE and have a blue "bottom of list" flash instead... Ok, maybe there was some good stuff in the rom but it's kinda been overshadowed for me

Good luck out there and hold on to your hope!

I heard back from Samsung support today (Orange having referred my case).

They said that their 2.3.5 was new (erm, yes) and that it wasn't backwards compatible, and for any devices that no longer worked I would have to get that devices supplier to provide new software on that device.

They used a car kit as an example.

So I specifically asked "Are you saying you released an update without any warning, that would render all previosuly compatible bluetooth HID hardware incompatible?" And he answered that this was the case and that I would have to ask Sandberg to update my device so that it would connect to 2.3.5

Now, either he had absolutely no idea what he was talking about, or there is something very wrong at Samsung.

I have asked for him to confirm this to me in an email. (I intend to make use of this writen statement if it confirms the above conversation.)

Has anyone else ever heard anything so bizzarre?

I surely hope this can't be right!