The Bluetooth connection from my SGS3 to my my Sony MW600 heatset doesn't seem to be as good as I had with my HTC Desire. With my old phone I was able to listen to music over Bluetooth with the phone charging in the bedroom and me in the kitchen, but the signal keeps dropping with the new phone.
Are there any tools that will allow me to monitor, and quantify, the strength of a Bluetooth signal?
Are there any drivers I might try to flash to try and improve the situation. I've not seen any mention of where the Bluetooth drivers are in the system, should I be looking at modems, kernels, etc., or are the drivers hidden in some other closed system?
Thanks in advance.
Although i had the desire i rarely used bluetooth over a distance greater then 3-4 metres, thus i cannot comment; the same applies for the S3 really too.
Regards
Jack
(this bump is subtle isn't it )
Related
The bluetooth for sense sounds horrible with loads of static. The aosp bluetooth sounds way better in comparison. Is there any way of getting the aosp version into sense roms? When I had my tmobile g2, I switched between sense and aosp roms. Bluetooth worked from very far away on aosp and the sense roms would barely work with the phone in my pocket. That is the case now with the thunderbolt. I have the BT on my right ear and my phone in my left pocket. I have to pull the phone out and put in my right pocket to work. Ive tried numerous roms, Lighting, bamf, tesla... all the same. I'm pretty sure this wouldnt be the case in an AOSP rom though.
I haven't experienced this at all... Ive had VirusRom RC1B3, Das BAMF, The perfect Storm, and now I'm on Lotus. I've tried Ziggy's kernel, adrynalyne, and the 1.76ghz kernel from RichardTrip.
I use BT in my car with my alpine deck and with a plantronics headset. No issues steaming my music or pandora from my phone to the deck. The BT module I have hidden in the dash to so it's not out in the open or anything.
Could just be your phone? Did it happen when the phone was on a stock ROM ? I had GPS issues on all of the ROMS I tried until I got Lotus installed. Locks on quickly now and is accurate. Maybe try that rom?
I also have not experienced this... I've been using mine with a Jawbone Jambox with no issues whatsoever with either one... I've gone through about 4 different roms/kernels and combinations.
My BT's been working great with TB. Which BT device do you have?
Im experiencing this as well, maybe not that degree though. On my old D1 i could leave my phone in my car, an go as far as close to 50 feet from it before i experienced signal breakup. On my thunderbolt using the same bluetooth as with the D1, about 10 to 15 feet from the phone is max before signal loss. Maybe the bluetooth radio on these phones is weak, or turned down to save power?
I don't have any issues with distance, but the sound quality is horrid. Lots of posts can be found regarding the issue and there's no fix. Simply because most people claim to not have the problem, and no one seems interested in finding a fix. The bitpool of the stock bluetooth stack is set to low as a default (it's current setting is the lowest possible setting) and it needs to be increased. If we could just get one dev to take a look into increasing the bitpool setting this would all be resolved. Regardless if you "don't have an issue", increasing the bitpool setting can only help everyone.
The problem is real, it's not the hardware, and it needs to be fixed.
Yes, it's horrible. I had to stop using BT in my car, and just use a aux cable. From what I've read, there is a setting for BT called "bitpool" that by default on Android is set really low. I gather this is kind of a quality setting, where lower is easy to maintain a connection but lower quality sound.
CM changes this to a much higher setting, which results in much better quality. I really only experience this in my truck, my Sony BT headphones don't really have this issue unless I turn them up.
My D1 didn't have this issue, but my Samsung Vibrant was worse than the TBolt (IMO). Different manufacturers will change the bitpool setting, and I guess HTC doesn't change it from default. I really can't wait for CM7 for a variety of reasons, this being one of them.
That's just my experience.
I have 3 different BT devices paired with my TB; Jawbone Era, Sound ID 300 and Moto H17. I haven't experienced any sound issue, let alone static.
weiln12 said:
Yes, it's horrible. I had to stop using BT in my car, and just use a aux cable. From what I've read, there is a setting for BT called "bitpool" that by default on Android is set really low. I gather this is kind of a quality setting, where lower is easy to maintain a connection but lower quality sound.
CM changes this to a much higher setting, which results in much better quality. I really only experience this in my truck, my Sony BT headphones don't really have this issue unless I turn them up.
My D1 didn't have this issue, but my Samsung Vibrant was worse than the TBolt (IMO). Different manufacturers will change the bitpool setting, and I guess HTC doesn't change it from default. I really can't wait for CM7 for a variety of reasons, this being one of them.
That's just my experience.
Click to expand...
Click to collapse
Exactly. CM uses a different bluetooth stack than HTC does. I'm wondering if it's at all possible for them (them being the CM devs) to maybe make us an update.zip to just apply the bluetooth stack and get rid of the crappy closed source broadcom one that you can't make any changes to.
Is the AOSP bluetooth stack multipoint? I connect to phone and A2DP/music with two different devices.
Hi,
For about a year I have used my GS2 with a Plantronics Savi Go bluetooth headset - I normally leave the phone in its desk cradle and use MyPhoneExplorer to make/answer all my calls and send text messages (I work in a small office with no wired phone at my desk and I sent at least 500 texts/day to coordinate teams working in the field.)
Recently - after returning from a trip - I noticed that the phone and headset would not work together at all if the wifi on the phone was enabled - the headset would connect to the phone and the first 10 seconds or so of every call would be OK, but the level of interference (as heard on the headset) would increase and increase and the headset would inevitably disconnect after about 20 seconds.
With wifi disabled on the phone this does not occur.
The headset works fine with another phone and also connects fine to its Plantronics USB adapter. This headset is designed to remain connected to two devices at once (intended to be the USB adapter and a phone) so you can make calls from either Skype/a voip app or your phone without having to change anything.
I have dropped the phone about a hundred times so I changed the aerial/loudspeaker module (http://www.ebay.co.uk/itm/300715915473) but the interference still occurs.
Is there any way this could be a software issue? I hate updating as I have custom density and all sorts of other settings so my phone is still on the same android 2.3.3 stock ROM that it came with - I have also removed all the Samsung customisations and KIES etc so updating is a pain.
My opinion is that there is no way this could be a software issue and that, as the antenna replacement has not solved the problem, there's probably a hardware problem and I should just toss it and get a Note or another GS2.
However, thinking about it more - the bluetooth and wifi transmitters share the same antenna? Is there any software cooperation to make sure these devices don't try and transmit at the same time or is there hardware gating? Are there filters designed to stop the bluetooth transmitter transmitting directly 'into' the wifi receiver (as they both share the same aerial which is used both for transmit/receive) and are they software or hardware?
My thoughts are definitely hardware but I would welcome the opinions of anyone that really knows how the two transmitters/receivers are meant to work together.
Thanks!
I've been having issues with bluetooth headset dropout during a call. Pairing is never an issue, and the bluetooth connection is solid outside of a call, but during a call the bluetooth may drop out without warning. This means that while I'm talking to someone, there is no audible noise or visual cue that the connection has dropped and has defaulted back to the phone, and thus I'm relegated to a "hello? hello?" query before I check the handset and find out the caller was asking the same thing to my pocket (which also shows the devices are never more than, say 1.5m apart maximum when this happens). As far as the phone is concerned, it's still 'connected' to bluetooth, as indicated in the dialer, and somehow isn't aware the connection has been dropped (or is and isn't showing). I thus need to redirect the audio via the UI either to the handset or speakerphone (away from the bluetooth connection it still think it's on), wait for the reroute to register, then redirect once again to the bluetooth to reestablish the connection. Again, without any audio cues the caller magically appears again on the headset, and we play the whole dropout game all over again. Connection duration seems arbitrary, lasting anywhere from 10s to a tens of minutes (with a 2-3 minutes on average).
This isn't isolated to any particular hardware, as I have had this occur on every one of my phones (Nexus S @ Android 3.x, stock and custom; Meizu MX @ Android 3.x - 4.x AOSP, OEM stock, and custom; HTC One @ Android 4.2.x - 4.3, stock only) and across all the headsets I've tried (Plantronics Discovery 925, LG HBM-585, Motorola H790), with Android being the common denominator. Note, I have used a Plantronics Discovery 655 and the same Plantronics Discovery 925 headset on my Nokia 8800 in the yesteryears, and have NEVER had connection or dropout issues.
Is this a known and/or ongoing issue, or is there already a fix for it? I haven't found anyone else with the exact same symptoms I've got, but seeing as the sample spectrum is so wide I'd be surprised if there weren't.
same issues
i have the same issues with my SGS3 and plantronics bluetooth headset... I'm thinking an app is the problem, but I didn't find it yet....
li Arc said:
I've been having issues with bluetooth headset dropout during a call. Pairing is never an issue, and the bluetooth connection is solid outside of a call, but during a call the bluetooth may drop out without warning. This means that while I'm talking to someone, there is no audible noise or visual cue that the connection has dropped and has defaulted back to the phone, and thus I'm relegated to a "hello? hello?" query before I check the handset and find out the caller was asking the same thing to my pocket (which also shows the devices are never more than, say 1.5m apart maximum when this happens). As far as the phone is concerned, it's still 'connected' to bluetooth, as indicated in the dialer, and somehow isn't aware the connection has been dropped (or is and isn't showing). I thus need to redirect the audio via the UI either to the handset or speakerphone (away from the bluetooth connection it still think it's on), wait for the reroute to register, then redirect once again to the bluetooth to reestablish the connection. Again, without any audio cues the caller magically appears again on the headset, and we play the whole dropout game all over again. Connection duration seems arbitrary, lasting anywhere from 10s to a tens of minutes (with a 2-3 minutes on average).
This isn't isolated to any particular hardware, as I have had this occur on every one of my phones (Nexus S @ Android 3.x, stock and custom; Meizu MX @ Android 3.x - 4.x AOSP, OEM stock, and custom; HTC One @ Android 4.2.x - 4.3, stock only) and across all the headsets I've tried (Plantronics Discovery 925, LG HBM-585, Motorola H790), with Android being the common denominator. Note, I have used a Plantronics Discovery 655 and the same Plantronics Discovery 925 headset on my Nokia 8800 in the yesteryears, and have NEVER had connection or dropout issues.
Is this a known and/or ongoing issue, or is there already a fix for it? I haven't found anyone else with the exact same symptoms I've got, but seeing as the sample spectrum is so wide I'd be surprised if there weren't.
Click to expand...
Click to collapse
Have you found solution to this issue ????
zbisho said:
Have you found solution to this issue ????
Click to expand...
Click to collapse
It seems to happen less frequently now between my HTC One and the LG headset, perhaps due to Android updates if it indeed is an underlying problem within Android itself, but it still happens from time to time. With such a wide spectrum, however, I certainly expected many more people to have experienced this problem, instead of it being an isolated problem (if it is, I don't see the connection between the hardware).
Would love someone more knowledgeable on this case (or perhaps on Bluetooth connection continuity in general) to chime in.
li Arc
Hi all,
i use my Z5 Compact for tracking my run with an Android Wear device (LG G Watch R)
I have several problems with Bluetooth. It works for some secs, then crash. After a min re-start works and reconnect....and so on..
When i use a cardio strip also the hr disconnects.
This is a video of the problem:
youtube. com/watch?v=YgA45nP8Nk4
Can you help me? I'v yet Hard reset it 3 times.
Thanks to all
I cannot offer help unfortunately but I am seeing similar things. And I am starting to think (hope, even) it is software.
My Jawbone UP3 disconnects continually and getting a reconnection is very hard, often involving a band reboot. I also have 4 TrackR tags which are randomly but frequently showing a re-paired message (smart lock device) in the status bar for no reason at all.
I've a Pebble Time but that has not been connected too much and seems ok, equally my Jawbone Jambox and MDR-XB950BT Sony headphones have been working without issue.
Possibly then it is only Bluetooth LE that is an issue (your fitness tracker would be that) and the three working devices are regular BT connections.
With luck this is something then that a firmware update will address. I hope so, because I'm bloody sick of buying broken hardware.
I use Bluetooth at various times throughout the day. I've never had a single problem with it! I am communicating with cars and obd2 systems though not low powered items like watches and headphones. Fwiw I'm on .152 firmware.
I am having massive Bluetooth Low Energy issues, I came to post about it but will do so here.
I have the E5823 unlocked in White. Android 6.0 although this started with 5.1. 32.1.A.1.163.
Basically I am concluding BLE is totally screwed on this phone, and I was about to send it back but realise the number of other BT issues people are having means it is likely not hardware on this one unit so perhaps software resolvable.
Jawbone UP3 loses connection continually, it occasionally connects and syncs, but I cannot force this.
TrackR Bravo tags work on occasion, frequently disconnected and randomly 're-pair' to the phone with no interaction (new BT device notification all the time)
Tile same thing.
Parrot Minidrone cannot be seen by the phone most of the time, it works on occasion.
All these devices are Bluetooth Low Energy. On the other side I have a Jawbone Jambox, Sony MDR-XB950BT headphones and Onkyo-NR626 Amplifier with regular old Bluetooth and all of these work, A2DP, atpX.
The only difference I noticed with 6.0 vs 5.1 is that TrackR can now tell the range by signal strength, something that always worked on the LG G4 Android 5.1 and 6.0. So I think the z5c started with issues and has not exactly improved.
Saying this there are known bugs in Android 6.0 and BLE, solved in 6.0.1. But right now I am super angry that yet another phone I buy is broken out the box. It never ends.
had BT issues, using a smartwatch (LG W100 G Watch).. but it was more frequent when used in combo with other accessories.
updating and restoring to MM 6.0 solved any issue.. so i managed to get well working, at the same time, smartwatch, cardio band, earphones and cadence/speed sensor (for bike).. all using BT LE..
before restoring and updating i got disconnections and glitchy music
When my headphones are connected, there is sound, but there are always disconnections, even though the device appears to be connected. the sound is getting thicker and thinner all the time. Is there a solution to this?.(I used the translation, sorry if there are mistakes)
Up
i have similar problems, i used to be able to comfortably go 5-10 meters away from the phone with my bluetooth earbuds, but after installing a rom, when i move even 40 cm away, the connection drops and i have to reconnect them again manually.
I tested my earbuds with other devices and i didn't see any connection problems and i don't think my bluetooth antenna broken because it was working fine before installing ROM
im using j7 prime g610f with "H-ROM A7 PORT V6.0 [10.0][OneUI 2.0][64 bits][Treble]" rom
Is there any bluetooth tuner or settings to fix this?
maybe the phones can only operate their antennas in the best way with their own bluetooth settings and the setting of another rom is preventing me from getting full efficiency from the antenna? Is it working like that?