Related
Headset: Motorola S9-HD
ROM: Haykuro 6.0
Radio: ota-radio-2_22_19_26I
Issue: a2dp audio skips due to location of phone... or so it seemed. The audio would skip if the phone was placed across my body from the antenna or in a pocket.
Resolution: I began researching the bluez stack and found several places in the code that alluded to the hfp and a2dp being intertwined. This lead me to remember that android also attempts to switch between the hfp and a2dp for incoming calls.
I found that my headset was connected by default with both profiles active (not one at a time).
Thus after several test i found that disabling the hfp will eliminate the skipping.
Explanation: My best analysis is that the phone is keeping both profiles open at the expense of splitting the channel. Thus when the phone has gsm related events (incoming calls, tower hopping, background edge data) it is tying up the hfp by error thus causing a2dp to get reduced resources, low signal strength, and possibly packet collisions. Try for yourself. The skipping instantly stopped for me. Let me know how it goes for you! Thanks to all the devs for these great roms and info.
can i get an english translation lol jk...can u explain it in noob form
interesting, plausible explanation
where in the code do you make the change?
noob translation: turning off the headphone profile possibly frees up room for audio to stream uninterrupted...
ps. that might still confuse some... lol
alapapa said:
interesting, plausible explanation
where in the code do you make the change?
Click to expand...
Click to collapse
no changes were made yet... the bluez stack is written to have a bridge between a2dp and headphone profile. i think android is sending packets to the headset via hfp for gsm events. I would think android should discard the packets instead of sending them out and relying on the headset to ignore them.
i would think the code can't be changed without making LOTS of other changes... i would be essentially rewriting how android handles the two profiles at the same time. (ALOT of work)
if this ends up fixing it for everyone... then i might look into trying to increase a2dp's priority in transmitting or some other solutions...
crushsuitandtie said:
no changes were made yet... the bluez stack is written to have a bridge between a2dp and headphone profile. i think android is sending packets to the headset via hfp for gsm events. I would think android should discard the packets instead of sending them out and relying on the headset to ignore them.
i would think the code can't be changed without making LOTS of other changes... i would be essentially rewriting how android handles the two profiles at the same time. (ALOT of work)
if this ends up fixing it for everyone... then i might look into trying to increase a2dp's priority in transmitting or some other solutions...
Click to expand...
Click to collapse
i think I gotcha...you just killed the hfp profile on your PC or w/e...?
Menu button>Settings>Wireless Controls>Bluetooth Settings>(long press) Your headset name>Options...>uncheck phone....
thanks for that tip. i was cutting my grass the other day. g1 in rear pocket. stereo bluetooth headphones on. signal kept cutting out on me. i'm gonna try this and see if it helps.
crazythunder said:
thanks for that tip. i was cutting my grass the other day. g1 in rear pocket. stereo bluetooth headphones on. signal kept cutting out on me. i'm gonna try this and see if it helps.
Click to expand...
Click to collapse
No problem. I'm just trying to add something constructive around here. I'm still not even close to some of these guys.
Hey you're right! I just connected my S9 to "media" only (disabling the phone connection in bluetooth settings) and it doesn't skip anymore, even with wifi on! I'm going to give this a try on my sony head unit in my car when I get the chance and I'll report back.
DOHCtor said:
Hey you're right! I just connected my S9 to "media" only (disabling the phone connection in bluetooth settings) and it doesn't skip anymore, even with wifi on! I'm going to give this a try on my sony head unit in my car when I get the chance and I'll report back.
Click to expand...
Click to collapse
Glad to hear that! im back at work and its heavily laced with wifi and the building gets poor edge/3G signal.So if you walk out the entrance toward the parking lot, the phone would connect to the cell towers (plus the wifi antennas are strong here) and my headphones would skip almost non-stop. This no longer happens. I'm quite happy.
Interresting hypothesis. I have my phone relatively close to my headphones so it hasnt been a big problem. Wifi had to be off or it didnt matter how close.
Eventhough it defeats the purpose of my S9's I'm going to give it a try.
atoy74 said:
Interresting hypothesis. I have my phone relatively close to my headphones so it hasnt been a big problem. Wifi had to be off or it didnt matter how close.
Eventhough it defeats the purpose of my S9's I'm going to give it a try.
Click to expand...
Click to collapse
i kept wi-fi off because I was in the gym or walking to my car... it would skip an absurd amount and i would nearly throw my phone and headset 8 blocks from pure frustration. The crazy part is BT is easily strong enough to transmit from a pocket to a headset on my head. I like to think i am tall but not that tall and disproportionate that my pocket is over 30 feet from my head! lol.
any skipping from that short of a distance is actually indicative of a problem to me. Thats like putting on a normal earpiece and getting nothing but static from that distance.
1) tests with my Sony Ericcson K850i showed it wasn't the headset....
2) i sat the phone on the floor directly under me when i was benchpressing, and simply because i layed down and partially covered the back of the headset the music started skipping non-stop. covering the antenna can cause some interferance but honestly with the phone that close it really shouldnt matter...
Tried the same test with my K850... no skipping. Tried with hfp disabled.... no skipping. Turn on hfp and a2dp... skips heavily.
thats the short version of how i came up with the split bandwidth part of my theory.
crushsuitandtie said:
no changes were made yet... the bluez stack is written to have a bridge between a2dp and headphone profile. i think android is sending packets to the headset via hfp for gsm events. I would think android should discard the packets instead of sending them out and relying on the headset to ignore them.
i would think the code can't be changed without making LOTS of other changes... i would be essentially rewriting how android handles the two profiles at the same time. (ALOT of work)
if this ends up fixing it for everyone... then i might look into trying to increase a2dp's priority in transmitting or some other solutions...
Click to expand...
Click to collapse
The handsfree profile will periodically send out "indicators" for things such as battery status and signal strength. These are small packets, which in a well designed Bluetooth stack, should not cause any disruption in the A2DP stream. The thing to look for would be how data transmission is prioritized. If, for example, BlueZ simply sends data in a "round robin" style, then sending a small data packet may delay the transmission of an A2DP streaming packet just enough to cause the problems you are describing.
I'm using JF1.51 and am not experiencing any of the audio problems you describe, even with WiFi and Handsfree connections enabled. I ran some tests and used a Bluetooth sniffer to capture the data traffic. One time I did hear an audio dropout at about the same time that the phone sent a signal strength indicator, which doesn't exactly validate your theory, but does make me wonder. However, I only saw 5 indicators sent by the phone over a 30 minute session.
Does using this method affect you from using the headset for calls?
Am I understanding that you would use this to listen to music... and if a call comes in would would talk over the handset normal?
What I've found is using A2DP indoors works perfectly (with our without HFP.) The explanation I've read is that the 2.4GHz waves bounce off the walls enhancing reception. Once outside is when I see degradation of quality/drops which would support the theory.
You might be on to something. If the bandwidth is being cut to share data over two profiles then, once you step outside, you'll have less distance before data packets drop.
paesano said:
I'm using JF1.51 and am not experiencing any of the audio problems you describe, even with WiFi and Handsfree connections enabled. I ran some tests and used a Bluetooth sniffer to capture the data traffic. One time I did hear an audio dropout at about the same time that the phone sent a signal strength indicator, which doesn't exactly validate your theory, but does make me wonder. However, I only saw 5 indicators sent by the phone over a 30 minute session.
Click to expand...
Click to collapse
you might have misread one of my posts... what you descrribed is exactly what i was saying... gsm events are possibly clogging bandwidth for a2dp. the one time you heard it is what i am experiencing constantly in some areas.
it appears to be a combination of several factors that are somehow hitting some people all at once....
1)"gsm or phone events being broadcasted"
2) possible split BT channel for HFP and A2dp
3) weak overall BT signal strength from g1 (dialed down in drivers to save power?)
4) interference from other wifi sources (enterprise access points aka "High gain antennas")
P.S. I guess its obvious i'm a systems analyst... lol
this really does work!!!!
if you guys remember windows mobile , the BT stack by default is set with the bit pool min and max @ 31 ,it works great but the sound quality sucks.. if you use a registry editor and increase the max bit pool sound quality gets better, but if you go to high you would get the cliping that we now get . i used to do this with my wing , using this same S9 headphone ,the trick was not to go to high with max bitpool and to lower min to 12 and this worked great,, max was @ 46 min was @ 12 ,, no skipping at all.. and great sound . WE need to find a way to get these adjusted on android , this should fix
now i do believe the wing and G1 both use Broadcom stacks ,could be wrong>>
remember Schap's tools - Advanced Configuration this did the trick
crushsuitandtie said:
you might have misread one of my posts... what you descrribed is exactly what i was saying... gsm events are possibly clogging bandwidth for a2dp. the one time you heard it is what i am experiencing constantly in some areas.
it appears to be a combination of several factors that are somehow hitting some people all at once....
1)"gsm or phone events being broadcasted"
2) possible split BT channel for HFP and A2dp
3) weak overall BT signal strength from g1 (dialed down in drivers to save power?)
4) interference from other wifi sources (enterprise access points aka "High gain antennas")
P.S. I guess its obvious i'm a systems analyst... lol
Click to expand...
Click to collapse
Sorry, I must not have been very clear. I did understand what you were saying, and I confirmed seeing what you saw in the one dropout I heard. However, in my case, there were only 5 "GSM Events" during the duration of my test. Not really enough to cause a lot of trouble. I can see that if a lot of GSM events occur (The spec calls them indicators), then there could be a lot of errors. Perhaps this happens when the GSM signal is weak and constantly changing.
If you want to look at making changes to the Bluetooth software, here's my analysis of the 4 points above:
1) If a lot of indicators are being sent by the G1, then I can see that a Bluetooth stack implementation could have streaming audio problems if not properly implemented. Unfortunately, the only way to fix this problem is in software by only sending indicators (and any other data) "in between" the A2DP streaming packets. Streaming packets should never get delayed. It would be better to toss the streaming packet than to delay it.
2) When both HF and A2DP are connected, the signal is not actually split. They both have access to the full bandwidth of the Bluetooth stack. The only time that there would be a problem is when both are sending at the same time, which could cause an audio packet to get delayed in a transmit queue, causing a dropout (as described above). Perhaps BlueZ doesn't do a very good job of prioritizing data, so that audio data is never delayed by other data packets. In my opinion, #1 and #2 are the same problem.
3) A week BT signal would definitely cause this. I can reliably listen to stereo audio with my Sony headset at around 10-15 ft. Outside that range, I start to hear dropouts. Also, If I put my hands over the headset, I can cause dropouts at even 2 ft. So, your body will definitely cause problems if it gets in the way of the signal. Finally, the sensitivity of the radio on the headset will affect the range as well. It may or may not be possible to increase the TX power by sending the Bluetooth controller a command in the software. The only other solution is to try and not get in the way.
4) WiFi certainly can cause interference, as can a microwave oven. However, adaptive frequency hopping (AFH) should mitigate most problems. Perhaps AFH is not turned on for some reason, or there are multiple WiFi networks around, making it very difficult for the Bluetooth controller to find any reliable frequencies. AFH is turned on by sending the Bluetooth controller the command.
This application is a hotfix for a really annoying (and potentially unsafe!) bug in the Epic4G:
http://code.google.com/p/android/issues/detail?id=11372
http://forum.sdx-developers.com/epi...audio-routing-on-epic-4g/msg115990/#msg115990
The long and sort of it is that when anything is plugged into the 3.5mm headphone jack, the phone will only play call audio over that jack.
In order to route the audio through the earpiece, bluetooth or speakerphone, you must pull the plug out of the jack. This is at the very least annoying, and at the very worst potentially dangerous if, for example, you're driving.
How-To
Download the APK attached below for your android version.
Install like any other APK using adb or your favorite file manager.
What it does
This simple application allows you to pick the audio device to use for call audio to override this behavior, and can be changed on the fly.
All in-call audio will be routed to the device you specify when something is plugged into the 3.5mm headphone jack. If nothing is in the jack, the default behavior for the phone applies.
This also allows you to use the Speaker Phone when the headphone jack is occupied, even though the button on the call screen is disabled!
Your configuration should persist between reboots.
What it doesn't do
This app does not route any other type of audio. Your music, notifications, etc will still play over the headphone jack or phone speaker.
Again, this *only* affects in-call voice audio, and only when something is plugged into the headphone jack.
Notes
This app completely overrides the options on the call page! If you want to switch outputs during a call, you will have to do it from this app - your call will not be dropped when changing the output device.
In order to route the call audio properly, the system's mediaserver service must be restarted, however.
This means that any other audio you have playing when you apply the change will be disrupted, and related services may force close. For example, Pandora will skip to the next song. Other applications may not behave that well.
Disclaimer
This app modifies files in the /system partition, so use this at your own risk! I am not responsible for any problems that arise from this hotfix on your device!
This is currently for the EPIC4G *ONLY* - Do not use this on any other device. Please contact me if you have a different phone which experiences this bug and I will see if I can get it working for you as well.
This is *BETA* software, a work in progress, please post here if you experience any issues, but I cannot guarantee it will work for you!
ROM DEVs, feel free to bake this into your roms in whole or part, I encourage it as this provides a workaround for a safety issue, but please give credit if you use or derive from this application.
Special thanks to UberPinguin - his initiative, debugging, code-diving and testing helped make this happen every step of the way!
Many, many thanks to everyone in #samsung-epic for helping me test and work this out.
Be sure to download the APK for the right android version on your phone!
epicBT - v0.3.5 (Froyo)
* Fixed crash/reboot when applying settings in DK17 roms
epicBT - v0.3
* Layout cleanup when root is unavailable
epicBT - v0.2
* Requires root!
* Superuser compatible
* auto-remounts /system RW if necessary
* Sends call audio to wired device ( default ), speaker phone, or bluetooth
Sources
https://github.com/cicada/epicBT
If this works as described above I will be so f-ing happy. One of my biggest gripes, solved.
No sh#t! I was just about to start searching the Market for an app like this! Downloading now to test.
Thank you!
bigdbag said:
If this works as described above I will be so f-ing happy. One of my biggest gripes, solved.
Click to expand...
Click to collapse
I agree
updated OP with source link
First of all,...Thank you, Thank you, Thank you for working on this... This was one of my biggest gripes with this phone and I couldn't understand why the "geniuses" at Samsung/Sprint couldn't get this right.
I've done some extensive testing in my car for the Eclair version and wanted to share my results:
For the most part, the app does what it's supposed to...but I did notice that:
1) the "on the fly" feature doesn't work so well. That is, when changing from one mode to the other, I had to reboot the phone to get the new setting to take effect. This feature would be great with an app like Tasker, which could automatically open up the app and ask you which setting you want to use when a headset/aux jack is plugged in,...thus giving you the flexibility to use the best option depending on your situation. Is there a way to tweak the app to recognize the switch without rebooting by resetting something like the mediashare service?
2) For some reason, the mic volume (volume heard on the opposite end of call) on the bluetooth setting is lower when the headset/aux jack is plugged in. I'm not sure whether the regular phone mic, speaker phone mic, or the bluetooth mic is utilized in this setting, but the volume is definitely harder to hear on the other end than when the headset jack is unplugged. I would guess about 20-25% lower. I tested this effect during the call as well by plugging and unplugging the jack while counting 1 to 10 and it's the same. Is there away to increase the sensitivity of the bluetooth mic when the headset jack is plugged in?
Donation coming if you can get this working! Thanks again.
sinman02 said:
1) the "on the fly" feature doesn't work so well. That is, when changing from one mode to the other, I had to reboot the phone to get the new setting to take effect.
Click to expand...
Click to collapse
Strange, it works well for me - it takes a second to switch outputs while mediaserver is restarting, but never had to reboot. I'll look into this, may have accidentally tweaked something in the last build.
UberPinguin and I are still looking at the sources to find a better fix that works the way it's supposed to - the trouble seems to be that Phone.apk is actually selecting the 'correct' source and setting options appropriately, but the underlying OS isn't switching outputs. Restarting mediaserver was the only workaround I could find for this.
sinman02 said:
2) For some reason, the mic volume (volume heard on the opposite end of call) on the bluetooth setting is lower when the headset/aux jack is plugged in. I'm not sure whether the regular phone mic, speaker phone mic, or the bluetooth mic is utilized in this setting, but the volume is definitely harder to hear on the other end than when the headset jack is unplugged. I would guess about 20-25% lower. I tested this effect during the call as well by plugging and unplugging the jack while counting 1 to 10 and it's the same. Is there away to increase the sensitivity of the bluetooth mic when the headset jack is plugged in?
Click to expand...
Click to collapse
I hadn't noticed any volume issues but truthfully I haven't been using the BT often because of this bug - I've just been letting my calls go to VM instead of crashing my car Volume selection should be working properly so I'll see if I can add something to select volume as well.
To be clear on the MIC, input should always be the proper input for whichever mode you choose - phone MIC for speakerphone and BT mic for BT HP/HS.
If you're on stock then the phone mic should be used when your wired device doesn't have it's own, however this is broken in all of our custom community kernels - Wired Headset mode should only be used when you actually have a wired headset with a MIC of it's own if you're using one of these, otherwise the phone doesn't enable any MIC at all.
I should note, that all my tests were conducted on outgoing phone calls. I don't know if incoming calls are any different. I am using the Syndicate rom.
If you can get the bluetooth volume issue resolved, I'll likely leave it there, but it would be nice to be able to switch on the fly to speakerphone mode when bluetooth isn't handy.
Question: Does the froyo version have the same implementation?
Please keep up the good work!
Sent from my SPH-D700 using XDA App
sinman02 said:
Question: Does the froyo version have the same implementation?
Click to expand...
Click to collapse
Yes, the froyo version is the same - Samsung used a different asound.conf in froyo ( added in some interesting VOIP pcm ), so this is the only difference between versions currently.
cicada said:
This application is a hotfix for a really annoying (and potentially unsafe!) bug in the Epic4G:
The long and sort of it is that when anything is plugged into the 3.5mm headphone jack, the phone will only play call audio over that jack.
In order to route the audio through the earpiece, bluetooth or speakerphone, you must pull the plug out of the jack. This is at the very least annoying, and at the very worst potentially dangerous if, for example, you're driving.
Click to expand...
Click to collapse
...So this should work on for Sip/VOIP apps like Sipdroid, 3CX, and Fring? I managed to pick up 3CX and Sipdroid through my bluetooth headset but no mic...meaning the other end could not hear me... There aren't that many good sip/voip soft wares out there for the Android today.. I rated Fring the BEST but with no bluetooth support.
EDIT: Nevermind... I read the post again.. I don't think this will do the job other than support for the actual phone.. but it would be nice to have that option for sip/voip as well.
The SIP/VoIP stuff may work better in Froyo considering there are dedicated PCM devices listed in the asound.conf - however I've never used any of these applications, so this is pure speculation.
You're correct, this does only effect in-call phone audio, those applications would be handling (or in this case, not) the bluetooth audio routing directly. I've found lots of other similar quirks with BT on the Epic4G, such as the << and >> buttons on my A2DP headphones not working.
cicada said:
The SIP/VoIP stuff may work better in Froyo considering there are dedicated PCM devices listed in the asound.conf - however I've never used any of these applications, so this is pure speculation.
You're correct, this does only effect in-call phone audio, those applications would be handling (or in this case, not) the bluetooth audio routing directly. I've found lots of other similar quirks with BT on the Epic4G, such as the << and >> buttons on my A2DP headphones not working.
Click to expand...
Click to collapse
I am using Froyo the DJ29 Build on the epic... Dare I try?
****ing yea! Thanks, downloading now. This has been my biggest complaint with the phone
Sent from my SPH-D700 using XDA App
Hell Yea! You rock! I Threw out a fairly long search sentence in google and actually found your post here. No sooner did I install and set it up that my phone rang while plugged into the car audio and FINALLY I can use my friggin BT headset without yelling hold on hold on I gotta unplug the stereo cable. This has really peeved me off since I got the phone. Now what I don't get is why this obvious flaw has been ignored by Samsung and Sprint. Nice job on making it work like it should. BTW running stock 2.1 with root. No bugs so far.
THANK GOD. someone fixed this. bugged me so much in the car when i'm receiving a call. will report any bugs.
bump, updated to fix crash in DK17 based roms
cicada said:
I hadn't noticed any volume issues but truthfully I haven't been using the BT often because of this bug - I've just been letting my calls go to VM instead of crashing my car Volume selection should be working properly so I'll see if I can add something to select volume as well.
To be clear on the MIC, input should always be the proper input for whichever mode you choose - phone MIC for speakerphone and BT mic for BT HP/HS.
If you're on stock then the phone mic should be used when your wired device doesn't have it's own, however this is broken in all of our custom community kernels - Wired Headset mode should only be used when you actually have a wired headset with a MIC of it's own if you're using one of these, otherwise the phone doesn't enable any MIC at all.
Click to expand...
Click to collapse
As others, I'm very grateful for this fix. After trying it out, if it works for me, donation on the way.
Regarding the MIC: My experience, all the way back to pure stock (IIRC) is that there is no MIC at all when a two-channel, stereo plug is inserted (headphones, cassette adapter, etc.). Every time I've been driving, listening to something via the headset jack, when a call comes in I can hear the other party, but they can't hear me at all until I unplug from the jack. So, even though there was no mic plugged in and the device was correctly sending 2-channel audio out through the jack (usually to a cass adapter, so I can listen via my car stereo), but doesn't "do the right thing" with the mic, even though the hardware and drivers are capable of detecting the absence of the mic.
It should, of course, default to the BT mic if there is a BT connection, or the built-in mic otherwise. For some reason this simple flow-diagram logic eludes Samsung.
So I got my first experience with this today...worked great. I was streaming Pandora, phone call came in, music was paused and I answered the call. Once I finished the call, the music continued playing. Minor detail, but since I was on WiFi, is there anyway that the music could have kept on playing while I was still on the call for the sake of my guys who were still working while I was taking the call? It's great that the music paused and resumed by itself, but it would have been cooler to have it keep going while I was on the call.
m5james said:
.. is there anyway that the music could have kept on playing while I was still on the call .. ?
Click to expand...
Click to collapse
Unfortunately Pandora's phone-state listeners control that, it'd have to be modified or their devs would have to add options for it. Would be cool though, I agree
I've got a hacked version of Pandora that allows unlimited skips, I'll have to ask the guy who did it to see if they can tweak that as well. Come to think of it, it'd be nice to have it keep going for the times I'm driving down the road as well so whoevers in the car doesn't have to sit there and listen to me blah blah blah.
I have been having intermittent issues with Bluetooth audio cutting out on my Captivate while I am on a phone call over Bluetooth. I believe the problem stems from Samsung's inability to do anything right and their implementation of Bluetooth 3.0. A new feature of Bluetooth 3.0 is the ability for a Bluetooth connection to transfer data over Wifi if both Bluetooth devices support 3.0 and have compatible Wifi chips. Samsung implemented this poorly, not a real surprise, and now Wifi is causing the Bluetooth data transfers to be spotty causing streaming data, voice calls or audio streaming, to to be adversely affected.
I was able to finally narrow down the problem. I received a phone call yesterday on my cell phone and I picked up the call on my Bluetooth enabled home phone. The call sounded horrible, noise and the other caller was cutting out, but not enough that I couldn't understand the other person, so I continued the call. The person on the other end did not seem to have any idea that the call sounded so badly, so it seemed to be something limited to my end. During the call, I went over to my Captivate and turned off Wifi. Instantly, the call cleared up and the quality was good to excellent.
I use Wifi all of the time especially at home, so I wasn't going to be turning off Wifi all of the time, so I needed a workaround. Using an App called Setting Profiles, I am able to have Wifi automatically turn off anytime I am on a call and then when the call is completed it turns Wifi back on. What's even better is that the app will note the state of Wifi before a call, so if Wifi is already off before a call, it will not turn Wifi on when the call is ended. The Tasker app will allow you to do the same thing, so if you already have Tasker you won't need Setting Profiles.
This tip will probably only work on the Samsung Galaxy S line because these phones use Bluetooth 3.0, where most Android phones use 2.1 or earlier and do not support Bluetooth file transfers over Wifi. I have only experienced it on the Captivate so I can't say if it will work for any other Galaxy S phone.
Since both wi-fi and BT uses the same 2.4Ghz frequency, interference maybe anticipated although new BT hardwares are pretty good at reduce such interferences.
Did you try change your wi-fi router frequency/channel so that it won't interfere with your BT? Try that so that you may not need to turn off wi-fi on the phone at all.
I have had the issue occur in my car while not near any Wifi router. Also, the router was still on when the call quality improved. It's not like the radio waves from the router and three other Wifi devices in my house disappeared around my phone just because I turned off the Wifi on my phone.
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks for the tip
Issue on my HOX. 1.85, rooted. When streaming via BT to and A2DP speaker or headphones, the WiFi becomes unmanageably slow. Meaning I sometimes can't even get enough wifi speed to stream a 192k file. If I go to speedtest while playing music through BT I get less than 500kbps. Turn the BT off, and bam ~20-30mbps. This is all when sitting within 10 feet of my router.
I know that BT and wifi conflict due to same frequency, etc....but is there any setting hiding anywhere in a DB or something that can help?
I had the same issue with my HTC Titan (Windows Phone 7) but I never found a solution for it (except to disable the bluetooth when I needed good wireless but that is not really a solution).
At least I can confirm the issue on the HOX. I tried making a phone call using my bluetooth headset and then while on the phone ran a speed test over the wireless. It jumped around (very erratically) under 100k then failed due to a communication issue. Immediately disabled the bluetooth on the HOX and then ran the same speed test and I got 7277kbps down and 5229kbps up on the phone using wireless and the speed was much smoother.
After running the test multiple times, the best that I got with the bluetooth enabled and in use was 374kbps down and 819kbps up...and again the speeds are very up and down with the bluetooth enabled and in use.
If I find any kind of solution I'll post back here.
Bt and WiFi run on the same2.4 GHz band. Typically, Bt chip set has circuit too detect WiFi and use a frequency less interference with WiFi. Sounds like this is not the case with the bt 4.0 chip inside HOX. Try change the WiFi channel on your router to see if it helps.
Sent from my HTC One X using XDA
Good idea! My router was on channel 7 and I changed it to channel 1. My test results are much better...2000+kbps down and 3000+kbps up - but still not very smooth (much up and down and stuttering). My results are still much higher with the bluetooth off but changing the wifi channel made a difference for me. Thanks again.
Hi everyone,
I have paired my OP 9 with my Cambridge Audio Melomania Touch Bluetooth earphones as soon as I got the phone, about eight months ago.
The phone has received several updates and upgrades in the meantime, but an issue has surfaced recently, as the title indicates: when I'm in a public place and there are other BT devices around, the music playing from the phone into my earphones suffers interruptions and distorsions, as if the phone was trying to pair with those devices, or maybe the Melomania Touch, I don't know.
I'd tend to think it's the phone, because I've had those earphones for about two years now, and with my previous phones (Xiaomi/Poco, Samsung), I never had such an issue. Once paired, the devices would deliver a solid, steady sound, with the occasional hiccup if the phone was in my pant pocket and I turned my head in the opposite direction, but that was it.
With the OP 9, however, every time I'm on the bus or the tram, or even waiting at the bus stop and a car passes by, I hear an interruption in sound delivery and I know the car in question had BT enabled.
In the Bluetooth settings, I've unchecked the option to make my phone visible by other devices, and in the Developer options, I've limited the number of devices the phone should try to connect to to 2, the Melomania Touch (it used to be 3, the third device being a Sony WH-700 BT headset I have at home, but I cleared it from the list).
I don't see any other settings to play with to make this inconvenience go away, and the Melomania Touch app doesn't offer any option either. The earphones are set to deliver max performance (not Low Energy BT).
I'm counting on you guys on this one!
Have to tried to enable HD audio (AAC) from that device's Bluetooth settings?
shadabkiani said:
Have to tried to enable HD audio (AAC) from that device's Bluetooth settings?
Click to expand...
Click to collapse
Hi and thanks for taking the time!
Yes, HD Audio is enabled, though I found it in the Developer options. BT options are pretty basic on this phone, if you ask me, but sound quality is really good, especially with those earphones.
UglyStuff said:
Hi and thanks for taking the time!
Yes, HD Audio is enabled, though I found it in the Developer options. BT options are pretty basic on this phone, if you ask me, but sound quality is really good, especially with those earphones.
Click to expand...
Click to collapse
Hmm... I don't know what could be the issue then. Maybe someone else with more knowlege can give more suggestions...