[Q]Galaxy s2 i9100 + bluetooth mouse. 2.3.5 breaks it. 2.3.6 fixes! - Galaxy S II Q&A, Help & Troubleshooting

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!

Related

[Q] Atrix won't maintain BT Connection

My Atrix pairs up nicely with my '01 BMW's BT system, but will drop the connection after about 15sec, and then reconnect again, hold that connection for about 15sec, then drop it. Phone will show Paired but not connected, and the car will be in a similar state. Following other's suggestions, I cleaned out my Contacts-- even with no Contacts in the phone, the same thing happens.
Any idea what's going on? My iphone 3gs and 4 connected 100%, uploaded their Contacts, and never gave me a moment's problem, so I know the BT in the car is working OK.
Help!
Sorry to hear that. I have so far no problems with connecting my phone to my built in BT system. I have a Mazda 2010. I stream music and get incoming calls too.
I used a bt headset for an hour long conference call this morning. No lost connections yet. Reboot doesn't help?
Sent from my MB860 using XDA App
Nope, rebooting doesn't help. BT on the Atrix works just fine with my Panasonic house phone that has BT on it.
I had the same issue today in my 2010 Dodge Ram. Captivate worked great in it, but the Atrix dropped the BT/Call after 30-45 seconds or so. I haven't noticed it dropping connection when I'm not using the phone (I have an icon on my ent/nav headunit), only saw the icon disappear when on a call.
Exwoodchuck said:
My Atrix pairs up nicely with my '01 BMW's BT system, but will drop the connection after about 15sec, and then reconnect again, hold that connection for about 15sec, then drop it. Phone will show Paired but not connected, and the car will be in a similar state. Following other's suggestions, I cleaned out my Contacts-- even with no Contacts in the phone, the same thing happens.
Any idea what's going on? My iphone 3gs and 4 connected 100%, uploaded their Contacts, and never gave me a moment's problem, so I know the BT in the car is working OK.
Help!
Click to expand...
Click to collapse
OK, so I messed with it some more...
If I'm super-fast, I can dial from the car's BT system-- and the name of the phone does appear on the car's Nav. That is, until the phone and/or car drops the connection.
I've asked for help on Motorola's forum, and been tracking down a Product Manager @ ATT to get the word up the chain.
I have the same issue with my 04 3-Series. I posted about this in the Problem forum.
No bt issues here. I used it yesterday with a car kit/fm transmitter to stream Slacker and nav simultaneously to my stereo for a couple of hours and it worked great.
Ziuck said:
I have the same issue with my 04 3-Series. I posted about this in the Problem forum.
Click to expand...
Click to collapse
Think we've got the same BT ULF's in our car. Please let me know if you find a solution, and I'll do the same.
mgymnop said:
Sorry to hear that. I have so far no problems with connecting my phone to my built in BT system. I have a Mazda 2010. I stream music and get incoming calls too.
Click to expand...
Click to collapse
Can you skip forward and back and pause?
I could with the iphone but have not been able to get it to work with android.
The weirdest bit is that I got it to work for Pandora ONCE... then never again.
I think it has something to do with the way android treats certain devices... I have motorola BT stereo headphones that the controls worked for WinMo W7 and iphone, but do not work on any android device I've tried.
I also lose connection with the in car BT occaisionally but not very often and can usually get it to reconnect without much hassle.
2010 mazda 3.
Exwoodchuck said:
My Atrix pairs up nicely with my '01 BMW's BT system, but will drop the connection after about 15sec, and then reconnect again, hold that connection for about 15sec, then drop it. Phone will show Paired but not connected, and the car will be in a similar state. Following other's suggestions, I cleaned out my Contacts-- even with no Contacts in the phone, the same thing happens.
Any idea what's going on? My iphone 3gs and 4 connected 100%, uploaded their Contacts, and never gave me a moment's problem, so I know the BT in the car is working OK.
Help!
Click to expand...
Click to collapse
Just because it worked with your iPhones doesn't mean the BT module isn't faulty...it might just have trouble accepting connections from certain things. Not to say the phone's *not* at fault, but don't assume it's the phone when there's a chance it could still be the phone.
I have a kenwood bluetooth module in my receiver that worked perfectly with every phone until I got an iPhone 4 (even previous iPhones worked fine). It wouldn't connect and finally when I got it to work the sound quality was horrendous (most people couldn't understand a single word). I thought the phone was obviously bad until I contacted Kenwood and they sent me a beta driver for the bluetooth module in the receiver. Updated the driver and it worked perfectly.
I agree- the BT module *could* be fault, but given that it works with all iphones and my BB Bold, I'd have to say that it's more than likely something to do with the way the Atrix/Android handles the connection.
Others are now chiming in on the Motorola Forum about this issue- including someone who has a newer BMW BT module than I have - he's also got the same issue. There's also a Dodge owner earlier in this thread that's got the same problem.
On a whim, I copied 20 contacts to the SIM, thinking that might be the problem.
Same results.
i also had bt pairing problems with my ford sync, and it seems to be android related as it also happened with my n1.
couple things to try that should help: disable wireless and make sure you aren't using the power widget on one of your home screens. also, i used autostarts to unbind the media button pressed event, and between those three things, the bt works fine...
Tried an experiement-- copied some contacts to the SIM.
Same issue- phone connects/disconnect/connects/disconnects for good.
Exwoodchuck said:
I agree- the BT module *could* be fault, but given that it works with all iphones and my BB Bold, I'd have to say that it's more than likely something to do with the way the Atrix/Android handles the connection.
Others are now chiming in on the Motorola Forum about this issue- including someone who has a newer BMW BT module than I have - he's also got the same issue. There's also a Dodge owner earlier in this thread that's got the same problem.
Click to expand...
Click to collapse
Apparently you read my post...but didn't understand it completely.
My previous receiver worked *PERFECTLY* with all phones but the iPhone 4. I used about 20+ phones with it without a single problem...but the iPhone 4 wouldn't connect 3/4 of the time, and when it did it didn't transfer any contacts and when I made a call the sound quality was *very* bad. I obviously assumed it was the iPhone 4 until I tried another one with it...turned out it *WAS* the receiver having an older firmware that wasn't compatible with the iPhone 4.
The reason a lot of Audis and BMWs aren't working with a few Android phones (the Atrix being one of them) isn't because Android is designed poorly...it's because the firmware in the receivers doesn't handle the Android setup well. The reason most people can connect but can't get contacts is because the way BMW/Audis poll for Contact lists doesn't work with Android. The car manufacturers haven't spent the time required to realize this and put out a correction. You should be complaining to BMW or Audi about this (whichever type you own) and trying to get them to release an updated BT Stack for your receiver (they might say it's not possible but it is).
Thanks for the clarification.
I doubt that BMW is going to release a firmware upgrade for my BT module - its out of production, and it's already 'state of the art', circa 2006 when they stopped producing them. I've read of other issues with newer BMW and other cars still having issues with the Phonebook upload, which is where I think the problem lies. It doesn't seem to be isolated to older cars either- I've read of 2010 models having the same issue I've got, and not just from European makers.
Digging around, this is a common theme with Android and BT not playing nicely-- many other phone manufactures have released patches/updates to correct similar issues, and I'm hoping that with the Atrix being the 'biggest and baddest', that Motorola sees fit to do the same. I've got a $600 fully integrated factory BT system thats now useless, and I'd sure like to have it working again.
I sometimes forget that I've got another BT-enabled car to test on -- a 2010 Audi A3.
My Atrix paired with no issue, then popped up with a message in the Notification area about allowing access to the Contacts. Ahh-hah! When paired to my BMW, I never get that message. So... the BMW appears to be unable to complete the handshake for PBAP access, and when it fails, it drops.
After syncing with my BMW I do not get the PBAP confirmation.
I did not get the confirmation with my Inspire 4G either but that phone DID work just fine. Contacts and audio would work and never had a drop out when I had the phone.
So there is a way to "fix" this issue without updating the vehicles BT.
Tested with my car bluetooth with 2 calls for ~30 mins in all today morning. Worked fine. It stayed paired on all the time.

[Q] Bluetooth in car auto connect issue, major anoyance for many

I know there are a variety of posts of many flavors in regards to OEM in car bluetooth handsfree systems. Some for unbranded i9100, some for the AT&T i777
For anyone out there with the knowledge: Is there anyway to find a task automater (like a macro) to lets say automatically activate the bluetooth button for the paired device, lets say 1 second after Bluetooth turns on. In connection with Auto Bluetooth app (like the ones which turns on when motion is detected) it could be automated. I would do it, except I don't know how to write program code.
I am thinking like "if bluetooth turned on, wait 1 second, trigger paired device input" . Because in that case it would connect (automatically) in most cases I though many many people posting around here.
Anybody any idea?
I am trying to connect my Galaxy S2 with they system in my 2011 Jaguar XJ. I never had a problem with my BlackBerrys. The BlackBerry autoconnects the moment I start the car and all functions work.
Absolutely not so with my S2. It seems that differnet car manufacturers differing systems which use BLuetooth differently. Some work, some don't .
Let me clearify the problem. Phone does NOT AUTOCONNECT and it drives me nuts. Before i just got in the car and never pulled the phone out of my pocket. Now I have to pull it out and manually connect.
I am posting as I may save some of you some time. I tried everything up and down the list. About every Bluetooth apps in the market place. Free or paid. Really pretty much all of them. Nothing worked. I upgraded to the (leaked) UCKJ1 and back to the original UCKH1. I rooted and unrooted.
To no avail. All I can do is use a shortcut widget to save me a few menues to navigate.
So for the ones with the same problem; you know all the things I tried. Don't waste your time.
It takes two devices to successfuly connect. If a connection doesn't happen, you can't blame just one device. My ISGS2 auto-connects to all of my devices (AV receiver, headset, PC, car, portable speaker, G-Tab) automatically every time. I get you're upset, but you can't single the phone out alone. As for cars, in the ISGS2 forum, non-iDrive (older) BMW's were the majority of the problem.
Same here. I have no problem auto connect to my BT devices. But when it comes to BT auto connections, problems are common. Both sides of the BT connection can be the cause.
Well depending on the year, make and model of the car with bluetooth. Really need more information. What Barry said is oh so true and usually anyone can tell you what their experience is. My experience with my daily driver's system *Alpine CDA 9887, Alpine KCE-BT400 made by parrot*, works flawlessly. The only time I ever had to manually connect was right after getting my sgs2 and even my captivate connected properly unless I was connected to my jawbone icon when I jumped in my truck.
HTH,
Charlie
Mine connects flawlessly in my 2010 Camaro SS.
Im in a 2011 Camry SE, and with stock ROM it connects automatically. With CM7.1, I just have to take it out of sleep, by turning on the screen, and it connects. Not a big deal.
Sent from my SGH-I777 using XDA App
Hi, Thanks to all for the responses. I completely agree that it takes two devices to do it right and I am fully keeping that in mind. I have 2 more cars I can try with. So I will check if it works with my wife's Lexus and with my Clarion system in another car I have.
It just is, that my BlackBerry (which I don't miss at all) simply did the job perfect. Obviously I can't tweak anything on the car side as that is next to impossible. There is no open source code and all is so proprietary.
So the only hope I have is to figure out a way to teach my SGSII.
Again thanks for the input. I do absolutely LOVE my Galaxy S2 (i777) therefore this is a simply irritating that I have to push buttons when I get in the car.
Hearing that it works for most of you is well, good for you and not so good for me.
Blaze9 said:
Im in a 2011 Camry SE, and with stock ROM it connects automatically. With CM7.1, I just have to take it out of sleep, by turning on the screen, and it connects. Not a big deal.
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
dmnall said:
Well depending on the year, make and model of the car with bluetooth. Really need more information. What Barry said is oh so true and usually anyone can tell you what their experience is. My experience with my daily driver's system *Alpine CDA 9887, Alpine KCE-BT400 made by parrot*, works flawlessly. The only time I ever had to manually connect was right after getting my sgs2 and even my captivate connected properly unless I was connected to my jawbone icon when I jumped in my truck.
HTH,
Charlie
Click to expand...
Click to collapse
Well, I will experiment a bit more and I will share what I will find in case others have similar problems.
This reminds me of a blog post ages ago called "Bluetooth needs a dentist"
The state of Bluetooth compatibility is abysmal in general... What is exceptionally sad is that 4-5 years ago or so, one of the most relibale and compatible Bluetooth stacks around (BlueZ) got a bunch of nastygrams from the Bluetooth SIG regarding failure to run the "offficial" compatibility/interop tests.
The short summary: Bluetooth compatibility is an epic nightmare, on both sides of the coin (host and device).
Entropy512 said:
This reminds me of a blog post ages ago called "Bluetooth needs a dentist"
The state of Bluetooth compatibility is abysmal in general... What is exceptionally sad is that 4-5 years ago or so, one of the most relibale and compatible Bluetooth stacks around (BlueZ) got a bunch of nastygrams from the Bluetooth SIG regarding failure to run the "offficial" compatibility/interop tests.
The short summary: Bluetooth compatibility is an epic nightmare, on both sides of the coin (host and device).
Click to expand...
Click to collapse
Hello,
I have to fully agree with Entropy512. Bluetooth compatibility is a disaster. Especially after all the years around. Not sure who, what and where is deciding on BT specs, drafts and so forth.
I know that with car systems it is a hit and miss. But it doesn't have to be. We all know that. I was digging on my good old Jaguar forum. What I found confirms exactly what we are saying.
Earlier Samsung Androids barely could hold a connection on Jaguars systems. Just with later versions and Gingerbread that was resolved. And none of the Samsungs autoconnect to any Jaguar system. And that is the same for Audi, Merceds and Subaru and probably some others. According to the Jag forum Samsung knows about this and worked on it.
But here is the main problem. On my wife's Lexus and on my Clarion head unit in my van it works like a charm. Automatically connects without a hitch. I understand Samsung can fix that but than it may not work on other cars. But how come BlackBerry was able to do what the Samsung unit can't???
And yes, some features like phonebook, direct dial and so forth are totally hit and miss. How do car unit manufacturers test? With what? Just one phone from 3 years ago? Same with the phone manufacturers. Is anybody talking? Seriously, why can't car head units manufacturers and phone manufacturers not figure out how to get on the same page? Car BT is becoming a standard equipment. So do BT enabled phones, no matter smart phones or what have you. There are not that many head unit manufacturers. So they can't agree on a standard which then can be used by the devolpers for a decent BT stack for phones? Completely ridiculous. Can make phones talk to you like the Apple Siri but can't get a bluetooth connection.
OK, I got that off my chest. Now I will try to get to work. All I can do is working on the i777 side, because there is no acces to anything on the Jaguar side.
Funny thing is, my phone is always stating phonebook request when I get in the car. Eventhoug I turned phone book off in the car. So the phone "hears" the car. Just without hitting the profile for the car it won't connect.
Auto connect to my Mazda 6 no issues. Same with all my other phones.
Sent from my SAMSUNG-SGH-I777 using xda premium
cpcrazyfly said:
Auto connect to my Mazda 6 no issues. Same with all my other phones.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Do you have problems with the Mazda taking too long to switch from "Music" mode to "Headset" mode, thus the vlingo voice prompt timing out? My mazda has that issue and it makes vlingo in the car pretty much useless.
I don't typically use voice commands but ill try. It has no issues taking and making calls then going right back to google music streaming.
Sent from my SAMSUNG-SGH-I777 using xda premium
I am also experiencing sporadic problems with my SGS2 and 2011 VW Golf using BT. About 75% of the time, it auto-connects fine when I start up the car. The car lets me know it linked and I can make/receive calls through the car's BT system fine. Address book loads as well (though does require a secondary authorization on the phone the very first time you use it).
However, every once in a while it either can't "find" the phone, or goes into a continuing looping state of "paired/not-paired". Generally when I actually want to use it! When it can't find the phone, manually searching for it (on the car's system) usually rectifies it temporarily, but it may go to unpaired a few minutes later. And on occasion, it simply can't find it at all. When I reboot the phone, or disable/re-enable BT on the phone itself, this problem usually goes away. This makes me think it's more of an issue with the phone then the car.
I too came from a BlackBerry torch and never once had a single pairing problem with my car.
When paired, media streaming generally works well, but occasionally I have to stop/restart it a couple times in order for the car to 'see' the media stream and allow me to chose it as the input.
The problem that I have is that the sgs2 will not report signal level to the car, so the car always shows full signal, even if i have no signal.
And it doesn't connect to the car unless the phone is in the car when the car starts. If bluetooth is turned off, or if I leave the car and go out of range, I will have to open the settings and force a connection.
Problem Solved, Autoconnect now working
Problem solved, read on:
This seems to apply to a variety of other vehicles, namely Jaguar, Mercedes, Audi, some BMW, Nissan and Subaru.
You can get your phone bluetooth auto connect to your vehicle by trying the following:
Attention, I believe this works for rooted phones only.
Get a app such as Titanium Backup Pro or MyToolbox.
under System Apps freeze "Bluetooth Share".
Now my phone automatically connects to my Jaguar XJ and all features seem to work. Having gotten around to check the phonebook yet. But all recent number log show and all seems to work.
Attention: I believe that may only work for rooted phones.
metalco said:
Problem solved, read on:
This seems to apply to a variety of other vehicles, namely Jaguar, Mercedes, Audi, some BMW, Nissan and Subaru.
You can get your phone bluetooth auto connect to your vehicle by trying the following:
Attention, I believe this works for rooted phones only.
Get a app such as Titanium Backup Pro or MyToolbox.
under System Apps freeze "Bluetooth Share".
Now my phone automatically connects to my Jaguar XJ and all features seem to work. Having gotten around to check the phonebook yet. But all recent number log show and all seems to work.
Attention: I believe that may only work for rooted phones.
Click to expand...
Click to collapse
I'm going to try this...
I've been having trouble with it automatically connecting to my 2011 WRX. My iPhone 4 always connected immediately, no problem. But the GS2 has yet to automatically connect, ever. It is paired fine and if I go into the Bluetooth settings, it is paired OK and I can manually tell it to connect. I've tried deleting the connection both from my head unit and the phone and recreating everything multiple times. Still no luck.
I'll try this and report back.
Bluetooth is def one of those technologies that could be enormously awesome but often has so much "fussiness" with it (due to incompatibilities or quirky behavior between varying BT devices) that it can easily become a right-royal PITA, IMO.
I've had quite a few Android phones over the years, now, and tried running both stock OS and many different ROMs on them with one of the expected primary functions of my phone to be as my main music player, including streaming music via BT/A2DP to my car stereo and this one function has ALWAYS proven to be the most frustrating experience. So yeah, I'll fully agree that whomever is "calling the shots" with setting up guidelines and specifications for BT and BT-based devices needs to get themselves an iron fist and put an end to this crap of inconsistent behavior and general flakiness.
When I got my AT&T SGS2 I was shocked to see that Samsung had done something to enable their stock music app to be able to transmit song metadata via BT. Android thus far has only supported AVRCP 1.0 (AFAIK) while you need AVRCP 1.3 (or higher) to be able to have metadata transmit over BT. At first I was ecstatic that FINALLY I could see my song info from my phone displayed on my car stereo while connected via BT. But then I found out that with the SGS2 and the stock music app my car stereo could no longer successfully send play/pause/forward/reverse commands to my phone! D'oh!!!
So then I went back to Poweramp (what I had been using for my primary music app on my previous phone; a Nexus S) and of course it wouldn't display the song metadata. But the big shocker was that it also couldn't recognize control commands issues from my car stereo! Not cool!
I did much tinkering and research and finally found that the music app PlayerPro would successfully work with my head unit (but still no metadata, of course) and so that's where I'm at.
Ridiculous, IMO. Nobody should have to endure such frustrating behavior with BT devices. I really wish somebody could straighten this kind of mess out in regards to Bluetooth and get things to "just work".
No luck for me. Freezing the Bluetooth Share did not fix my auto-connect problem.
ack154 said:
No luck for me. Freezing the Bluetooth Share did not fix my auto-connect problem.
Click to expand...
Click to collapse
OK, you can try one more thing;
Freeze all of those files: BluetoothPBAP, BluetoothShare and BluetoothAvrcp. If you have any other entries you can try freezing them, too. Just everything EXCEPT anything with a name like Brcm or BrcmBluetoothServices.
Just try it. And MAKE SURE to wipe cache after freezing, or better reboot. Also you want to make check they are in a "frozen" state after rebooting. I used "MyToolbox" and it worked perfect.
I haven't checked if I can still stream music, but I never use that anyways. I froze all of those and started unfreezing one by one. The experiment showed that in my case I only had to freeze the BluetoothShare. You may have to freeze the others, too.
Let me know how ot works. I am curious now.

[Q] Connecting to IOGEAR BT Device

I haven't seen anyone post this yet, and I'm hoping I won't draw the usual search you fool comments. I am trying to connect to an IOGEAR GBHFK231 handsfree car device which I know usues a passcode to connect. It pairs without prompting me for the passcode, and when it tries to connect i get a message bluetooth device has disconnected, and the BT no longer shows up in the list.
I am currently using Scotts Cleanrom 1.6.5 without any mods installed, but I have had this problem with stock before unlocking, Nils ICS, Scott's Cleanrom ICS, and a few others ICS and GB.
I have also contacted IOGEAR who says they have not received any reports of issues, and will get back with me if they get any information. I'm holding my breath. Notice the blue color.
Any ideas from this renowned collection of geniuses?
This is a cheapo device by the way, and relaceing it isn't a problem. Just looking for answers.
Thanks,
Matt
Wow no responses yet.. I had it connect one time and was able to make a call using voice dial, but after it was disconnected it went back to paired but not connected, then disappeared when attempting to connect. I'm planning to upgrad my car stereo with a bluetooth calling built in model. Am I likely to have similar problems?
Thanks again.
Am I the only one to experience this problem? anyone using a Bluetooth hands free car device and can verify it working? I'm a little hesitant to buy another and have the same problem.
Sent from my ADR6425LVW using Tapatalk
No comments about searching. See? :-D
You might try Amazon reviews to see if there are any reasonable complaints there.
Not sure where Berlin is but, if you live in the south, the bluetooth device itself may overheat on your dash, and that may cause the issue you describe.
Also, not familiar with BT pairing for your device, but you should be prompted for a pin / code. Make sure you're in BT wireless settings on your Rezound when you are trying to pair. It might be good to "forget" your BT device and start with a fresh pairing attempt.
Sent from my ADR6425LVW using Tapatalk
If you've had the device previously paired to the phone, the phone I'd has changed according to the device. Clear your pair list and re-pair or pair, delete the pair, re-pair.
Sent from my ADR6425LVW using Tapatalk
BT is flaky at best right now with the ICS rom. Mine works most of the time when it wants to. Occasionally I will have to reboot my phone to get it work right.
I have the turtle beach px500 headphones and my phone hooks up to them over Bluetooth just fine. Can make calls, listen to music.
Running innefabilis 1.0
Sent from my ADR6425LVW using XDA App
htc uses its own BT stack. Unfortunately, BT still has too many variables which is why I have never bought the BT peripheral for my pioneer system. Not worth 150 bucks to have it not pair with a phone down the line.
Thanks for all the replies. I've been through stack problems in the past with some car audio bt devices never won one yet. This issue started before I ever unlocked my phone, and I have used both GB and ICS roms with no luck so I'm going to rule that out for now. I've started getting error messages that say I am using the wrong pin to pair, but have never been given the box to enter a pin. So far as heat etc this was working fine on my Dinc, and hasn't been in the car since I switched to the Rezound. I have also connected it to other phones while trying to fix it without a problem. Does anyone have a method to force the box to open to enter the pin, or is there possible a security setting that I need to remove?
Well I figure it out. I changed the bt device to a setting to use 2 phones, then reset it to factory default and it's working now. I don't know why the other resets didn't do the same thing, but it's working.

Bluetooth Keyboard/HID Device Latency

Can anybody confirm that they are having the same problem on their Galaxy Tab 7.7? If I use a bluetooth keyboard, it pairs and sets up and works fine, but if I don't press any keys for exactly one second, then press a key, there is a latency of about 0.5 seconds for the key press to register. I don't have this problem on my Galaxy Nexus, and I can recreate it with both a bluetooth keyboard and a wiimote connected through bluez ime. However, if I connect the wiimote as a non-hid device through wiimote controller, there is no latency after however many seconds. I believe there must be some latency setting to save power, but am not sure. Can anyone advise? I play games with an external keyboard, and it really messes me up. Thanks!
I haven't timed it, but I haven't noticed any latency or issue with my Bluetooth keyboard.
palexr said:
I haven't timed it, but I haven't noticed any latency or issue with my Bluetooth keyboard.
Click to expand...
Click to collapse
Could you perhaps let me know which model you have (3g or wifi) and which firmware you're running? If you could just test to make sure that the keyboard responds instantly after not being used for about five seconds, I'll flash mine to whatever you have and be forever grateful.
i am also experiencing this, but i am using like a $12 bluetooth keyboard so i just shrug it off since im not bothered by the lag anyway
Sent from my GT-P6800 using XDA
TeeeJaay said:
i am also experiencing this, but i am using like a $12 bluetooth keyboard so i just shrug it off since im not bothered by the lag anyway
Sent from my GT-P6800 using XDA
Click to expand...
Click to collapse
Good to know that I'm not alone. Hopefully ICS will fix it. I know my galaxy nexus doesn't have this problem so I can only keep my fingers crossed. It wouldn't bother me for text input, but it bothers me hugely when trying to play games, so we'll see if anyone knows how to fix this. Thanks a lot for confirming though.
I'm using a Logitech bluetooth mouse V470 and it's really fast, yes there's a little lag when I stop using it for a few minutes but it's so little that doesn't really bother me. I cant tell you right now about a keyboard, I'll test one tomorrow with and without the mouse and we'll see what happens... I'll get back to you...
Thanks. That's the only real problem with mine right now. I've tried only the Hong Kong firmware, but I don't see there being a difference in the other ones. I imagine that if it's possible to disassemble one of the APKs related to bluetooth and change a timeout value it will work, but I have no idea where to look for such a file.
I connected the bluetooth mouse and a keyboard and they both work great simultaneously, and yes, there's always a delay after you stop using then for a moment but doesn't really bother me...
duraaraa said:
Thanks. That's the only real problem with mine right now. I've tried only the Hong Kong firmware, but I don't see there being a difference in the other ones. I imagine that if it's possible to disassemble one of the APKs related to bluetooth and change a timeout value it will work, but I have no idea where to look for such a file.
Click to expand...
Click to collapse
I'm using a Hong Kong one, and also experience the lag after I stopped using it for awhile. This also affects my Phonejoy game controller at times unfortunately.
Really hope, ICS will fix this.
Sent from my GT-I9100 using XDA Premium HD app
Same here, it bothers me, but seems it's some general bluetooth go to sleep or whatever issue, after not typing for a couple of seconds, the first keystrokes fail to register for a second or so.
I noticed identical behavior with the Samsung Note.
Glad I found this thread, because I couldn't find anything else anywhere with Google. There's a similar thread in the 7.0 Plus Accessories forum. I can confirm that I'm having the same issue, only with the Galaxy Tab 7.0 Plus. Same exact issue. I'm using both the iControlPad and a keyboard, and the issue manifests itself with both devices, so it's got to be the tablet.
I also noticed that, if a key is held down for too long (I think 3+ seconds), the corresponding action or letter will repeat for a second or two (very noticeable when playing platformer games). If that same key is held down for a shorter period (say, only 1, maybe 2 seconds), then the action or letter will cease repeating immediately after I let go of the key.
Submitted a request to Samsung to fix this, and you may want to do the same (not sure if it will help, but doesn't hurt to try).
Mobile gaming was one of the reasons I got this tablet, and games are nearly unplayable with this delay that is introduced. I'm using the same bluetooth devices with the Motorola Razr Maxx, and these delay issues are not present at all (in fact, the response with using a controller is near perfect). Hate to say it, but I will be forced to look to other tablets if this doesn't get resolved with the ICS update (and I won't get my hopes up).
I can confirm that with the vanilla ICS bluetooth implementation in the Galaxy Nexus, this problem isn't present. I actually sold my Tab 7.7 because of this problem, among other various small bugs, like programs randomly disappearing (of course it's rooted, and I can't say if this happens when not rooted).
Hopefully when ICS is released, if it does have the problem, there will be an AOKP or Cyanogenmod port which will resolve it. Sadly, I don't want to wait for that. Perhaps anyone with an SGS 2 can confirm if this problem is present in Gingerbread and in ICS, or only in gingerbread. Someone with a note could do the same.
Posted this in the 7.0 Plus thread as well. Called Samsung's support line after reporting this by email. I would normally think that this would lead nowhere, but their support line seems to lead to knowledgeable people who at least understood what I was saying (and this seems to be a very specific issue). The number is 1-800-726-7864.
I reported the issue, and I also mentioned the 7.7 tab and the Note. Not sure if that will lead anywhere, but it doesn't hurt for more people to report this.
Also asked about ICS... crickets of course
So my hope to c0nnect keyboard n mouse. Hdmi output and charging at the same time is gone.

Screen mirroring with Widi receiver

I have a Belkin Screencast widi device that I use with my laptop. I figured it wouldn't work with the screen mirroring feature on the S4, but I opened it up, and it can see the receiver. So I decided to try to connect. If you hold down on the device in the app on the phone, it lets you enter the pin to connect. It goes through the "Connecting" steps, and on the TV it says "Connected" but the phone keeps spinning, saying "Connecting" before eventually failing.
I know that people have gotten the Netgear Push2TV devices to work with it, but I had one of those, and it didn't work a damn with my laptop. The Belkin device works much better with my laptop (although it's still buggy, I would call Widi an alpha product at best - that is, an alpha level product that's expensive and has been on store shelves for a while, go Intel) but it seems strange that it can walk so far along in the connection and then fail out.
Anyone able to get the mirroring to work with a Widi 2.0 receiver?
I could never get it to work on my Galaxy Note II. However, the firmware recently updated on the belkin device when I connected my laptop to it.
After that I was able to use screen mirroring on my Galaxy S4. However, since then I have not been able to get it to work again.
I have tried everything....even a factory reset on the S4 but still no luck.
i got it to work
i have one of those belkin push2tv widi receivers too for my toshiba. i kept getting bugs like it would disconnect after 30sec after i upgraded to win 8. i was being able to connect my s4 to it though, it was working pretty good, kept kinda disconnecting but it was working. i then updated the firmware a month ago and it started working flawlessly with the laptop but it stopped working with the s4. i see there have been some new updates for firmware things in the s4. maybe now it will work. i will let u know. but it was basically saying it's not compatible ...the s4 with the belkin...when i was trying to connect them. will see if samsung fixed it. there was an update for screen mirroring from what i remember.

Categories

Resources