Related
Hi,
I recently bought this nice bluetooth earphone (Sony Ericsson MW600) - because it was mentioned, it works great on Nexus One.
But I got a somehow strange problem:
when it is connected to the phone (at least, bluetooth settings say so), I can phone with this headset but I cannot listen to any music.
Settings say, it's connected to phone and media.
I tried enomthers and cyanogens latest roms.
Has anybody any idea, what is wrong?
edit: tested it with a SE v640i - works perfektly - must be an issue with the nexus/rom/whatever :-/
Thanks,
bastie
how did you buy them?
via ebay
it is unused and the package was not opened, too...
okay, after searching through the net for several hours - here's the solution:
it does not work, when wireless lan is turned on - for whatever reason
so:
first turn off wireless lan
then connect mw600 and play music
seems like bluetooth and wlan are blocking each other
Good to know. I just ordered one for 50 bux shipped when I preordered from mobilecityonline.com, which still is selling for the same price but now shipping is no longer free because it's no longer a preorder item. I figured its better than retail or ebay after my stint with a fake SE product a few years back. Thanks for the info!
One thing I learn is never buy bluetooth headsets or memory cards from ebay. 99.9% of them are fakes.
kpjimmy said:
Good to know. I just ordered one for 50 bux shipped when I preordered from mobilecityonline.com, which still is selling for the same price but now shipping is no longer free because it's no longer a preorder item. I figured its better than retail or ebay after my stint with a fake SE product a few years back. Thanks for the info!
Click to expand...
Click to collapse
Hello Everyone,
kpjimmy, I ordered and received my MW600 from mobilecityonline.com too. They seem to have nice service.
How can we tell if we got a counterfeit device or not. I had problems in the past with serveral brands?
Did you find the instruction in the box were not detailed ?
I went to sony ericsson support page for the MW600, no user guide pdf file. Only the warranty pdf. I noticed for the other devices such as the DS205,DS970,DS980 there are user guide pdf files. Have you found one for the MW600?
Must say, I am impressed with the battery life. I took out of the box, charged for 8 hours as per instructions. Turned it on, paired it, turned on the FM radio with 100% volume. It went 10.75 hrs, even a few phone calls before dead. Did 3 full 8 hrs charges/10.75hrs to full discharges cycles.
Thank you,
Monnie
I have used the headset for a week or so and I must say it is an awesome little headset for the cash! I also have the plantronics 590A but that is for my personal home use, but the MW600 is great for the office or when you are out and about. I haven't taken any calls with the headset yet though.
As for this being possibly a fake headset? I have to say my last 'fake' headset was in the box, (wasn't sealed btw) and when used, the sound was too tinny like cheapo headsets you get at your local convenience store. This one I received from Mobilecityonline, in my opinion the real deal. The sound is nice and functions as it should. Very satisfied with the headset.
Anyone want a aliph icon? LOL kiddin...that's what I use when in the car.
Jimmy you work for SE? you haven't take any calls yet? and you used it for so long? or do you work for mobilecityonline.com? let me know what is your deal?
I hace one and very annoying problem with this headset . When i plug id to HD2 and turn on the WIFI , music freeze for a less then second and sound geting disorted and very thin (it sound like the music change frequency to very low. Anyone had this problem ?
loaferkan said:
Jimmy you work for SE? you haven't take any calls yet? and you used it for so long? or do you work for mobilecityonline.com? let me know what is your deal?
Click to expand...
Click to collapse
I don't work for either. I am a BT and tech junkie . I have taken a call on the MW600 and all sounds fine and works great as expected. I have since use my Aliph Icon with the new A2DP drivers installed.
However, I also have gotten the BlueAnt S4. I have used this more than the MW600 and I have to admit I love the thing. It is truely handsfree and the sound is great, clear, loud and is truly handsfree.
shr3nron said:
I hace one and very annoying problem with this headset . When i plug id to HD2 and turn on the WIFI , music freeze for a less then second and sound geting disorted and very thin (it sound like the music change frequency to very low. Anyone had this problem ?
Click to expand...
Click to collapse
You plug in? The MW600 does not need to be plugged in. The HD2 has A2DP. All you need to do is turn on your bluetooth and pair the phone with the headset. When you play the music with your bluetooth on, the phone should automatically connect to the headset and play wirelessly, no plugging in necessary. Please give us additional detail. Thanks!
my mw600 works great - 5.0.5.3 through froyo.
so the skip forward/back and play/pause buttons on this can control the music?
Because I've lost the original N1 remote and am looking for decent replacements.
Thanks
it controls music. display obviously doesn't show the track like it might if paired with a sony device however. touch volume slider is kinda annoying.
shr3nron said:
I hace one and very annoying problem with this headset . When i plug id to HD2 and turn on the WIFI , music freeze for a less then second and sound geting disorted and very thin (it sound like the music change frequency to very low. Anyone had this problem ?
Click to expand...
Click to collapse
Same here !!!
Really annoying!
Just got it. Had a Nokia BH-103 before but it broke. On the Nokia the sound sometimes was getting faster or a bit slower from time to time but that did not annoy me that much, now i can hardly hear on song. even if i turn of wifi the issue remains. please please help. really was looking forward to use my new mw600 and now the expirence is ruined.
headset works great with ps3 and notebook even over "big" distance (can hear music in every room of my flat)
so i guess it's the devices fault
having a htc hero using villian rom 10.2
PLEASE HELP
SOLVED !!!!!
setting the cpu speed somehow messes up bluetooth audio transfare
disabled overclocking now works like a charm
I tried my friend's SE MH-100 which he uses for his Aino, but my N1 can't even find it via bluetooth. I ordered the MBS 200 which is a bluetooth speaker also from SE and I'm still waiting for it.
Any clue why it can't find the MH-100? Im afraid it wont be able to scan the MBS200's bletooth as well
UPDATE: It's working great
I ordered one from ebay just now because Sony Ericsson Canada is selling is for $99.99 (mobilecityonline sells it for $50 but charges $40 US for shipping too Canada...)
After reading stories about fake bluetooth, I am worried. How do I tell if the one I bought is genuine or not? I bought it from this seller: http://cgi.ebay.com/SonyEricsson-MW...ewItem&pt=PDA_Accessories&hash=item1e5cfdeebe
I purchased one from mobilecityonline in person.
I don't really like the volume control, but I encounter a pairing problem with nexus one.
If I keep the pairing with the phone, it works 100%, but if I connect it to another device, it refuse to connect to nexus one again except I pair them again.
The battery is awesome though, I play 8 hours of wireless music and the battery doesn't run out.
I know this should probably be posted in my device's forum (Samsung Focus), but I figure more people will probably look here and the topic about headphones in that forum is pretty dead.
I'm looking for headphones that are 100% compatible with a Samsung Focus, or any WP7 for that matter (I might be upgrading to a Focus S or a Titan - not sure yet). I don't want anything too expensive, I just want there to be volume up, volume down, pause / play / next / previous / answer call, and a microphone. I currently use iPhone headphones (as I bought my Focus used and never received a headset) and everything works except for the microphone and volume buttons (I'm surprised that much works).
So can anybody confirm 100% working headphones with the Focus / any WP7 device? Again, I am sorry that I'm not putting this in the right forum but that one has been dead for a few months.
EDIT:
I've looked at headphones here, but nobody has posted reviews on any of the headphones.
Diablosblizz said:
I know this should probably be posted in my device's forum (Samsung Focus), but I figure more people will probably look here and the topic about headphones in that forum is pretty dead.
I'm looking for headphones that are 100% compatible with a Samsung Focus, or any WP7 for that matter (I might be upgrading to a Focus S or a Titan - not sure yet). I don't want anything too expensive, I just want there to be volume up, volume down, pause / play / next / previous / answer call, and a microphone. I currently use iPhone headphones (as I bought my Focus used and never received a headset) and everything works except for the microphone and volume buttons (I'm surprised that much works).
So can anybody confirm 100% working headphones with the Focus / any WP7 device? Again, I am sorry that I'm not putting this in the right forum but that one has been dead for a few months.
EDIT:
I've looked at headphones here, but nobody has posted reviews on any of the headphones.
Click to expand...
Click to collapse
Hi Diablosblizz,
I use a simple A2DP receiver and then use whatever earphones/buds that i preferr at the time. All of the controls that you desire are held in the receiver unit and as i say the earphone type/price/quality remain your choice.
Hope this helps,
Creamy
I totally agree with last answer...the jack plug on my phone is dead from first day so i bought a 20€ bluetooth headphone (msound brand)...everything you need works, just an annoying thing since mango: music stops 10secs when a new message coming.
Sent from my HD7 T9292 using XDA Windows Phone 7 App
creamy said:
Hi Diablosblizz,
I use a simple A2DP receiver and then use whatever earphones/buds that i preferr at the time. All of the controls that you desire are held in the receiver unit and as i say the earphone type/price/quality remain your choice.
Hope this helps,
Creamy
Click to expand...
Click to collapse
So, basically it is a Bluetooth device that connects to the phone and then I plug my headphones into it? I'm curious as to if this will continue to play my music. I have a PS3 Bluetooth headset that connects to the phone and works perfectly, but I can't listen to music through it.
Is there any way possible you could link me to your device so I could look into it more?
Hi,
I am having troubles with my mobile network provider for some months now.
I got the Galaxy R and can't use it with my bluetooth hands-free kit. bt pairing is ok but the audio quality is such bad that it's not possible to understand anything.
I tried the following:
SGR + Volvo hands-free = pairing and connection OK but very bad audio
SGR + parrot hands-free = same
Both hands-free had the newest firmwares from manufacturer.
I tried the device from my friend, a SGS2 which seems to be pretty similar to the SGR
SGS2 + Volvo hands-free = crystal clear audio
SGS2 + Parrot hands-free = same
My conclusion was that my SGR must be defect. I went to the Samsung support and they flashed a "new" firmware (it was the same I already had). Still same problem. Then I took the phone to my network provider (Austrian 3, www.drei.at) and after some weeks I got back a new SGR from them. Again the same troubles with this device. My network provider refuses to swap my SGR to a SGS2, even with a extra charge. Now I'm pretty angry about this **** Galaxy R (sorry )
I have the newest Kies updates installed on it and everything else than hands-free is working.
Does anybody has a similar problem?
Any tips or suggestions?
If not, my next step would be to give this case to my legal protection :-( but I am still hoping...
Edit 1:
Additional Version infos for the SGR:
Samsung Galaxy Royal
Modellnummer: GT-I9103
Buildnummer: GINGERBREAD.XWKI5
SW-Version: Android 2.3.5
Basisbandversion: I9103NEKI1
Kernel-Version: 2.6.36.3-I9103XWKI5-CL577705 [email protected]#3
Hi!
I have 2.3.5 version in my SGR and I have no audio problems with my nokia headset, toshiba headset, motorola stereo headset and ford focus V2C free hand. The synchronization is better than with my old nokia X6, but audio is louder with the nokia, specially with V2C free hand.
If we count that volvo accesories are nearly the same as ford accesories (ford was the owner of volvo until august 2010), we can expect that your volvo free hand has a bluetooth 2.0 nokia module, 100% compatible with our SGR. In the parrot, you can find exactly the same nokia bluetooth module if it was maded before 2011 (parrot changed to another brand in some free hand models).
I suggest to try another device with a different bluetooth brand module. Bluetooth stereo headsets are really good to test that, specially if you use them in a crowded place, with a lot of possible interference. You don't have to buy ones, you can go to a big electronic store, like Media Markt or Carrefour(I don't know where are you from but here are the biggest ones) where you can try different headsets with your phone. If you play a high bitrate song loud and it is not crystal clear audio, your device has a problem and you can use the warranty, or try a custom rom to fix it...of course, loosing the warranty option.
boskyman said:
Hi!
I have 2.3.5 version in my SGR and I have no audio problems with my nokia headset, toshiba headset, motorola stereo headset and ford focus V2C free hand. The synchronization is better than with my old nokia X6, but audio is louder with the nokia, specially with V2C free hand.
If we count that volvo accesories are nearly the same as ford accesories (ford was the owner of volvo until august 2010), we can expect that your volvo free hand has a bluetooth 2.0 nokia module, 100% compatible with our SGR. In the parrot, you can find exactly the same nokia bluetooth module if it was maded before 2011 (parrot changed to another brand in some free hand models).
I suggest to try another device with a different bluetooth brand module. Bluetooth stereo headsets are really good to test that, specially if you use them in a crowded place, with a lot of possible interference. You don't have to buy ones, you can go to a big electronic store, like Media Markt or Carrefour(I don't know where are you from but here are the biggest ones) where you can try different headsets with your phone. If you play a high bitrate song loud and it is not crystal clear audio, your device has a problem and you can use the warranty, or try a custom rom to fix it...of course, loosing the warranty option.
Click to expand...
Click to collapse
thanks for your post
1.) I tried two SGR with two different hands-free kits. Both were not working with both devices. With a SGS2 I had no problems with both hands-free kits. I'd say that there must be a problem with the SGR.
2.) I'm from Austria(Österreich) a german sproken country in Europe. My provider is called hudchison three (drei.at). Both, the shipped image and the KIES updated image are both not working.
Is it possible to flash for example a standard ROM from Germany over my austrian drei image?
What do you mean with custom rom? I didn't found any for the SGR. Just some custom Kernels. Nevertheless it would be very risky for me to loose the warranty when still having troubles with it.
I use the sony ericsson mw 600 without any problem, and exellent sound
If you don't want to lose warranty, as I said, I recomend to you to go to a big electronics store like Media Markt, where you can find different bluetooth headsets and try them. If you have not really good sound go to samsung service and tell them what is your problem. I know this is not a solution, but without touch your phone it's what you can do, because an incompatibility problem will not be cover by the warranty, but if you prove that your bluetooth has a general problem it must be repaired.
If you decide to taste some kernels, or the new InfectedRom to upload your android version to 2.3.6 you can ask to the developer if it fix your problem. If not, if you have made a backup of your hole device, you will return the virginity of your phone, but you have to read a lot to do all this things if you don't know how.
I don't know anyone from Austria with a SGR from the forum. You can try to find another users to see if they have the same problems. I will probe mine next sunday in a parrot free hand from a friend that has a SGS and it works really well.
Using the sony ericsson mw600 as well, works great, even gets track names if I use the stock music app
Sent from my GT-I9103 using XDA App
problem fixed with latest update from drei.at
I am wondering if any of you fellow Verizonites would be willing to help me test this out, as I have already asked my friend with the AT&T version if his does this, and it does not:
When connected to the aux in (very common on cars and stereos nowadays, you know, so you can listen to music off your phones and iPods and MP3 players, etc.) I now have the SAME incredibly aggravating problem I could never resolve with my Fascinate. As usual, I have my bluetooth connected to take the call. When I answer the call, I hear NOTHING over my bluetooth unless I disconnect the audio cable out of the headphone jack!!! This is a huge safety hazard, as it takes your hands and eyes off the road, requiring you to disconnect a cable every time you get a call!!
I called Verizon and complained about this with my Fascinate to no avail. I never had this issue with my Droid X, HTC Eris, or my Galaxy Nexus, another dual core Snapdragon based Verizon LTE phone made by Samsung.
Not to mention the SGS III is laggier and less responsive than my Nexus, although not as bad once you disable S Voice (S is for stupid, by the way, at least in my opinion ... I can't get it to work worth a darn!! Could be that I'm the stupid one, but I've certainly given it a lot of effort in a very quiet environment.)
This is horrible because the screen is incredible, and the battery life far outpaces every other smartphone I've ever had by a ridiculous margin, so PLEASE, fellow Verizon SGSIII friends, help me out if you can!! I don't want to have to return this phone, but reasons to do so are stacking up.
If there's no fix for the audio cable thing, that is a definite deal breaker, and enough to make the phone "defective" in my opinion. That is such a blatant safety hazard. I do NOT want a "Fascinate 2". The other issues pale in comparison to the audio cable issue.
Here is a video of the AT&T version NOT having this glaring safety and functionality issue:
http://www.youtube.com/watch?v=A37p4fF-h-k
This is a glaring safety issue you are right. I planned to have bluetooth on my ear to take calls but have the phone plugged in for music on my car speakers.
The other thing is I bought a Samsung HM7000 thinking it would work with the SAMSUNG S III. Pff. I guess FreeSync App doesn't support the S III yet. I will definitely express to Verizon/Samsung why I have to return this headset if this isn't solved in a few weeks. I will contact Verizon on this.
So this doesn't affect other US Galaxy S III units only Verizon? That's so weird but it also suggests it's an easy fix.
I tested it with Bose Bluetooth earpiece and that works, somewhat. If you have the Aux plugged in and get a call, the phone picks up your voice from the Bluetooth and plays the other guys voice through the Aux. Unplugging the Aux mid-call will route the other guys voice back to the Bluetooth. In both cases both me and my friend could hear each other.
There is a problem though. When the Aux is plugged in, with Bluetooth our not, the call quality will drop significantly. It will sound as if you're in a horrible signal area and will cut out every other second or so making it impossible to carry on a conversation. Funny thing is as soon as I unplug the Aux the call is back to normal and we can hear each other just perfect. It's as if with Aux the noise cancellation kicks in and starts cancelling out everything, including your and the other guys voice, lol. Not sure if that's just my phone or SGS3 in general. I actually intentionally used this "glitch" to avoid taking to annoying person. Just tell them "I'm in a bad area and can't talk" and plug in the aux mid-call and they will stop bugging you as soon as they hear the voice glitch up
My bluetooth headset works fine with the audio out through the "dock" connector.
macdroid01 said:
This is a glaring safety issue you are right. I planned to have bluetooth on my ear to take calls but have the phone plugged in for music on my car speakers.
The other thing is I bought a Samsung HM7000 thinking it would work with the SAMSUNG S III. Pff. I guess FreeSync App doesn't support the S III yet. I will definitely express to Verizon/Samsung why I have to return this headset if this isn't solved in a few weeks. I will contact Verizon on this.
So this doesn't affect other US Galaxy S III units only Verizon? That's so weird but it also suggests it's an easy fix.
Click to expand...
Click to collapse
Same here
Using bluetooth in a 2009 infiniti, AUX jack prevents proper bluetooth calling or receiving. I had come to rely on this in my other phones (HTC).
same here too
I upgraded from a fascinate to a s3 and have the same problem on both phones. It is really annoying and I'd love to find a fix for it.
adsbar said:
Using bluetooth in a 2009 infiniti, AUX jack prevents proper bluetooth calling or receiving. I had come to rely on this in my other phones (HTC).
Click to expand...
Click to collapse
I think I am having the same problem with the Bluetooth in my 2010 G37. It seems like if u connect via Bluetooth for media audio, I can't get calls and vice versa. Plus when I connect to media audio and try and switch back to just phone, it doesn't auto connect when I get in the car.
My Rezound didn't seem to have any of these issues.
Sent from my SCH-I535 using xda app-developers app
This was the case with my 1st generation galaxy s epic 4g. Looks like Samsung still hasn't recognized this as an issue. The smart developers here ultimately fixed this on my epic but my s3 is still suffering from this... Btw I'm on synergy. I would love for someone smarter than me to figure this out. Please, please....
Sent from my SCH-I535 using Tapatalk 2
sinman02 said:
This was the case with my 1st generation galaxy s epic 4g. Looks like Samsung still hasn't recognized this as an issue. The smart developers here ultimately fixed this on my epic but my s3 is still suffering from this... Btw I'm on synergy. I would love for someone smarter than me to figure this out. Please, please....
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I don't know who to blame, Samsung or Verizon. I have the Samsung Galaxy Nexus and it does NOT have this issue. Never had that issue, with stock or custom ROMs. A good friend has the SIII on AT&T and it also does NOT have this issue, as the video above demonstrates. He also owns the Galaxy SII, which also does not have this issue. I used to rock a Droid X. At least my Droid X did not have this issue, although I have read reports of other Droid X owners' phones having this problem. My old HTC Eris also didn't have this issue. But, as mentioned above, my Fascinate does have this issue.
It's horrible. I have messaged Samsung, and they have responded that they are looking into it. It's the same response they gave me several weeks ago when I first posted on the support page on Facebook about this issue. I have also called and complained, after which their support tech said she wasn't yet fully trained on the SGS III yet, and they had a special number for me to call, which of course wasn't open at the time.
If a dev can figure this out, he can at least count on a donation from me.
I am sick of this ... I decided to keep this phone despite this issue, because of all the other goodness it brings to the table (especially battery life!! Wow!!) But this is still a horrible issue.
SirKronan said:
I don't know who to blame, Samsung or Verizon. I have the Samsung Galaxy Nexus and it does NOT have this issue. Never had that issue, with stock or custom ROMs. A good friend has the SIII on AT&T and it also does NOT have this issue, as the video above demonstrates. He also owns the Galaxy SII, which also does not have this issue. I used to rock a Droid X. At least my Droid X did not have this issue, although I have read reports of other Droid X owners' phones having this problem. My old HTC Eris also didn't have this issue. But, as mentioned above, my Fascinate does have this issue.
It's horrible. I have messaged Samsung, and they have responded that they are looking into it. It's the same response they gave me several weeks ago when I first posted on the support page on Facebook about this issue. I have also called and complained, after which their support tech said she wasn't yet fully trained on the SGS III yet, and they had a special number for me to call, which of course wasn't open at the time.
If a dev can figure this out, he can at least count on a donation from me.
I am sick of this ... I decided to keep this phone despite this issue, because of all the other goodness it brings to the table (especially battery life!! Wow!!) But this is still a horrible issue.
Click to expand...
Click to collapse
I have the same problem - my 2008 Tundra does not have A2DP for audio streaming, but does have BT for phone calls (and works great). On my previous Droid2, I could use the AUX jack for music and the BT for calls no problem. Now, with the S3, if I hook up AUX for music and BT for calls, then when a call comes in the phone keeps the audio out going to the AUX jack while my truck switches to BT for sound. Therefor, I can't hear the other person (but they can hear me) unless I unplug the audio jack.
From what I've found on the net, it seems it's something in the bluetooth settings/drivers in how Samsung has them implemented on the phone, which is not the same as how they are implemented in the Motos and HTCs. I was unaware that other carrier versions and/or certain other Samsung phones (S2, Nexus) did not have this problem.
For now, I've solved it by getting my hands on a car dock for the ATT Infuse 4G, which has the "dock" mode built into the USB connector with both power and audio output. I dock my S3 into this dock and changed the settings to output audio out the dock. Then I plug my AUX cable into the dock and it works like I expected it to from the start.
CIPuyleart said:
I have the same problem - my 2008 Tundra does not have A2DP for audio streaming, but does have BT for phone calls (and works great). On my previous Droid2, I could use the AUX jack for music and the BT for calls no problem. Now, with the S3, if I hook up AUX for music and BT for calls, then when a call comes in the phone keeps the audio out going to the AUX jack while my truck switches to BT for sound. Therefor, I can't hear the other person (but they can hear me) unless I unplug the audio jack.
From what I've found on the net, it seems it's something in the bluetooth settings/drivers in how Samsung has them implemented on the phone, which is not the same as how they are implemented in the Motos and HTCs. I was unaware that other carrier versions and/or certain other Samsung phones (S2, Nexus) did not have this problem.
For now, I've solved it by getting my hands on a car dock for the ATT Infuse 4G, which has the "dock" mode built into the USB connector with both power and audio output. I dock my S3 into this dock and changed the settings to output audio out the dock. Then I plug my AUX cable into the dock and it works like I expected it to from the start.
Click to expand...
Click to collapse
Does the S3 fit into the dock ok? Any stability problems? And you get proper 3.5 inch output for your car's input, plus your bluetooth call works? I have the same kind of deck in my Freestyle. Installed it myself. It does bluetooth for calls but not A2DP. Thanks for your responses so far! I am willing to buy a dock if it works like that. I would just appreciate any reassurance you could give me that it will work out ok ...
but that's a really nice idea that i didn't consider. I would really like to get this thing working and willing to apply any dev fix. what's interesting is that skype calls work fine, yet regular phone calls do not i'll give this doc a try.
Ok, I have the dock now, and wanted to update everyone on this. Audio quality is good, better than bluetooth, but an ever so slight downgrade from just plugging straight into the headphone with an audio cable, but it's certainly good enough.
The one thing that is annoying enough to prevent me from using it is that there is an audible click between each song. I haven't a clue how to get rid of this!! ARGHH!!! I haven't tested the dock with video or pandora output to see if the clicks persist, but as of right now, it's a bit annoying on a long trip. Otherwise, this would work really nicely, and is a pretty cheap fix for $18, not to mention getting a fully functional windshield/dash mount to use your phone as a GPS with.
Hoping my new ROM I installed might solve the audio issue. It has a custom kernel, and possibly improved car dock compatibility. We shall see...
Hello everyone!
I just upgraded to the SIII from my Droid 4 and am having this same issue. Does anyone have a fix? It seems silly to have to buy additional items to get it to work when it worked fine on other phones.
I like the stock ROM, but will flash if necessary to get this to work, as its very distracting while driving.
misterpat1975 said:
Hello everyone!
I just upgraded to the SIII from my Droid 4 and am having this same issue. Does anyone have a fix? It seems silly to have to buy additional items to get it to work when it worked fine on other phones.
I like the stock ROM, but will flash if necessary to get this to work, as its very distracting while driving.
Click to expand...
Click to collapse
SoundAbout Pro is an app that will override Samsung's stupidity when it comes to BT/AuxJack audio routing. Well worth the price of admission.
Hello,
Pardon if this has been answered already, I simply did not find my exact question answered.
I am using my unmodified Nexus 5 (not even rooted), with the latest KitKat (v.4.4.2 build KOT49H) with quite a few wired and wireless headsets and people always complain they cannot hear me. Eventually I got my hands on an old Samsung Galaxy S2 and tried my best bluetooth headset with it: Imagine my surprise, I could hear myself quite clearly even when I was talking really really softly, barely above a whisper. My headset is excellent. My phone is not.
My questions revolve around what to do about it.
Nothing in KitKat allows me to adjust the bluetooth microphone gain, nor does it let me use an equalizer on my microphone. I can adjust the volume of the headset, but this does not do anything to the microphone gain.
So...
Question 1: am I the only person with this problem?
Question 2: what do you people do about it?
Question 3: are there any mods / custom ROMs out there that attempt to fix this problem? Google does not appear to be interested in doing so.
Thanks in advance!
*bump*
Any ideas? I have tried re-pairing my bluetooth headset - no go. I have tried flashing custom ROMs and kernels - no go again. It seems to be a problem with the phone, but I have no idea how to fix it. And Google searches always return other people having this problem. Noone with solutions, though.
Using a wired headset results in even worse results, if that were at all possible.
Has anyone tried to replace the bluetooth stack or driver with something that works?
Thanks!
*bump*
Yesterday I spent quite a few hours tinkering with my phone. I tried every last radio out there for the Nexus 5 and none had any effect on bluetooth microphone levels. Then I tried a few AOSP ROMs: CM11 and Omni. They turned out to be so closely related I might as well have just tried one. None had any effect on bluetooth microphone. Heck if CM11 doesn't do it, there really are no alternatives out there! I tried the FauxAudio tweak, even paid $2 to Faux, which successfully managed to do nothing: app didn't was written badly. Finally, I tried a bunch of volume boost tweaks. That worked, actually. That is, it boosted the wrong volume. Finally, in a moment of true and utter desperation, I opened an ADB shell and edited that mixer file by hand. I then discovered that microphone gain on bluetooth is not controlled there.
I tried all my wired headsets again: Etymotic HF3's microphone produces such an atrocious sound, if I am to rely on it I need to seriously consider becoming a mime. Then there were my Bose QC15 headphones with a remote cable for Android by some off-brand company: that was terrible, the cable is useless. Heck, not even mime lessons can help me there.
Eventually I chanced upon an old microphone cable for my QC15 headphones. Just microphone, no remote. Surprisingly, this one is loud and clear! That after being anything but loud or clear on my old cell phone. Interesting. Unfortunately, it's been out of production for a few years. My working theory is that Bose realized putting a decent microphone on expensive headphones gives people real value, makes them spend money, and that way lies madness. We can't have that, can we. So when that cable starts cutting, so does my use of this cell phone.
I am screwed.
In any case, I will stop bumping my own thread, you guys obviously don't know a solution or there would have been a lively conversation right now. And I am pretty sure there is a moderator or two frowning right now, possibly getting ready to throw an encyclopedia at me. My only hope is that Google is going to do something about that pesky Broadcom driver that doesn't work sometime before the mass exodus to the iPhone. And before my precious microphone cable stops working, or I will be leading the way for that exodus. It's a phone, damnit, if it doesn't work like one it's no good.
Hmmm.... it should be possible to wire a good lavalier mike on a cell phone cable... maybe I can get an op-amp from an old tape recorder to get decent amplification... When attaching a 9V battery on my headphone cable begins to look appealing, we really have a problem.
Yes, if nobody reply you is because no one can help u.
But for what it's worth, i had an Xperia Play for 2 years. Using an Motorola Bluetooth Headset H350 while driving and a MW600 Sony Ericsson Stereo Bluetooth Headset, both never had a problem.
Now from 2013 Christmas both headsets with my new N5: still never a problem and not noticing any low volume or mic. Sorry
same issue
Dany XP said:
Yes, if nobody reply you is because no one can help u.
But for what it's worth, i had an Xperia Play for 2 years. Using an Motorola Bluetooth Headset H350 while driving and a MW600 Sony Ericsson Stereo Bluetooth Headset, both never had a problem.
Now from 2013 Christmas both headsets with my new N5: still never a problem and not noticing any low volume or mic. Sorry
Click to expand...
Click to collapse
hi,
i am having the same issue with my Nexus 5 in combination with my Logitech H800 Wireless headset (people can`t hear me).
Anybody who did find a solution for this?
Thx
pitchdown said:
hi,
i am having the same issue with my Nexus 5 in combination with my Logitech H800 Wireless headset (people can`t hear me).
Anybody who did find a solution for this?
Thx
Click to expand...
Click to collapse
No solution. I tried everything, everything I could think of. I got FauxAudio to work eventually and that did nothing for Bluetooth performance (and it said it wouldn't, but I was desperate).
I returned a lot of high end bluetooth headsets over this issue. Eventually I came upon the Plantronics Voyager Legend. I would like to tell you this really expensive headset works fine, but no - microphone gain is still low, though this time around people can hear me okay. Not great, just okay. I am using that now. It's not perfect, it's far from perfect, but finally usable. Sort of. If I speak loudly.
For what it is worth, the ElementalX kernel improves Bluetooth stability on the N5 quite a bit. Microphone gain is still low, though. Another thing that sometimes helps a little is turning off the multimedia profile on the headset, though why THAT would make a difference is beyond me.
All we can do is wait, watch the Samsung Galaxy S5 get released and wonder if we should switch.
kangelov said:
No solution. I tried everything, everything I could think of. I got FauxAudio to work eventually and that did nothing for Bluetooth performance (and it said it wouldn't, but I was desperate).
I returned a lot of high end bluetooth headsets over this issue. Eventually I came upon the Plantronics Voyager Legend. I would like to tell you this really expensive headset works fine, but no - microphone gain is still low, though this time around people can hear me okay. Not great, just okay. I am using that now. It's not perfect, it's far from perfect, but finally usable. Sort of. If I speak loudly.
For what it is worth, the ElementalX kernel improves Bluetooth stability on the N5 quite a bit. Microphone gain is still low, though. Another thing that sometimes helps a little is turning off the multimedia profile on the headset, though why THAT would make a difference is beyond me.
All we can do is wait, watch the Samsung Galaxy S5 get released and wonder if we should switch.
Click to expand...
Click to collapse
Somebody advised me to download the app "persist"
This is free from the playstore.
Can you try this and let me know this is working for you?
Thx
pitchdown said:
Somebody advised me to download the app "persist"
This is free from the playstore.
Can you try this and let me know this is working for you?
Thx
Click to expand...
Click to collapse
This app controls the bluetooth volume, not the bluetooth gain. The bluetooth volume was never a problem.
kangelov said:
This app controls the bluetooth volume, not the bluetooth gain. The bluetooth volume was never a problem.
Click to expand...
Click to collapse
Ok,
i am having the problem with my Logitech H800 headset with the nexus 5.
So this is a android kitkiat 4.4 issue?
Or is this problem only on several Nexus 5-devices?
pitchdown said:
Ok,
i am having the problem with my Logitech H800 headset with the nexus 5.
So this is a android kitkiat 4.4 issue?
Or is this problem only on several Nexus 5-devices?
Click to expand...
Click to collapse
My guess is either the bluetooth baseband or the bluetooth kernel driver used in the N5 is flaky. This is why I think so:
Problem does not exist on my old Samsung Galaxy S2, including when it runs the same nightly of CM11, nor does it exist on my computer or my desk phone. All the headsets I've owned performed admirably there, so the headsets are not directly the cause. From what I've seen no ROM and no kernel out there seem to be making a difference as far as Bluetooth gain is concerned, the problem is persistently there and the same. Best I could tell it's just the N5 with a problem and it's just for the phone profile. I've tried the Bose headset (the worst performer headset with the N5 of the lot) on a colleague's N5 and his phone was just as bad with it as mine. I am not sure if it's a small batch of N5s having a problem, I don't own lots and lots of N5 phones to try on, but I doubt it: with anything digital things are usually all-or-nothing and the N5 has an off-the-shelf Bluetooth chip, which is not unique to the N5. My guess is it's the entire model, but having only tried on 2 N5 phones, this is no more than a guess.
From what I saw online, the entire Nexus line has poor Bluetooth performance, not just the 5, and Google changed the Bluetooth stack with KitKat besides possibly introducing more problems. If you have a non-Nexus phone, the manufacturer most certainly replaced the Bluetooth driver and radio with one of their own, so problem goes away, but the Nexus line does not enjoy such attention.
An interesting thing to try would be for someone to put the LG G2 Bluetooth driver on a N5 kernel and try it out. I don't have the time or the expertise to do that, but there are plenty of people who do. Assuming the G2 does not have problems with bluetooth gain, if the problem still persists it will tell us if it's the N5 baseband or hardware doing it, and noone can help us there if that's the case.
I have this problem too, using my Nexus5 with iphone headsets. Peoples told me in skype and hangouts, that they hear me bad...
Shiver2005 said:
I have this problem too, using my Nexus5 with iphone headsets. Peoples told me in skype and hangouts, that they hear me bad...
Click to expand...
Click to collapse
That's a different problem. The wired headset problem is easily solvable with FauxAudio and a supported kernel.
This maybe realted to the changes Google made to the core Bluetooth stack as of Android 4.3+ I know they made adjustments for the BLE [low poer Bluetooth devices like pedometers and other senor type crap]. It is BEYOND me as to why Google keeps adding functionality ot the core Bluetooth stack when it is GLARINGLY OBVIOUS they have real problems with Bluetooth as a whole. WHY NOT fix the core issues so Bluetooth is much better at the basics before trying to add functionality or more complex?
I know they complained it would cost a bit for a different newer Bluetooth license but I mean in my personal experience with many different phones Bluetooth is SUPER flaky even at it's best in Android, and does not even work the same way across devices [I have used 3 different Jabra speakerphones on my bosses Galaxy 3 recently and they all worked to varying degrees even though they all use the same version of Bluetooth protocol], but my T989 [Galaxy 2 T-mobile], my parents G2s My bosses older Bionic, My fathers new Droid X, etc. all have random problems. You can usually find one device that works well with a certain phone/ROM, but that can change between ROM versions and devices so it is like you need to go and buy 1 of everything every time there is an update and go crazy finding the ONE that works [and as noted on page 1 with the gentleman using the same Platronics Voyager Platinum as I have it is a super expensive very nice device that worked BEAUTIFULLY in ICS, but now in 4.1 + you can not get more than 1 or 2 words across the mic unless you are YELLING at it like a crazy person on the SAME device].
So all that to say I think it is prolly related to changes Android made in 4.3+ flipped the Bluetooth operability on it's head.
Mic Volume OK with KitKat 4.4.4 and cheap "HB-800" headset
there've been no posts for a while so maybe the problem has gone away with the KitKat updates.
But anyway:-
I have a Nexus 5 and recently bought a cheap generic stereo earbud headset with mic from eBay .... $14.82 Ozzie including delivery to Western Australia.
I've actually asked the other party whether they can hear me (specifically "am I loud enough?") because I read this thread and have been assured that it's all good.
In fact it's a pity the sound quality at MY end isn't better, but that's probably the low quality ear buds rather than electronics / firmware reasons.
Of course, ymmv.
Here's the ebay item title in case anyone wants to look it up or I can pm the item number if it helps.
"Headphones Earphones with MIC 1st Stereo Bluetooth Hands-Free Wireless HV/HB-800"
No, the problem is still there. Reason there are no posts is that no one has a solution. Nothing has changed since March. I am somewhat controlling it with CM11 running on the ElementalX kernel. Without this kernel Bluetooth performance is unbearable. With it it is barely adequate.
It's funny that a cheap headset would work okay while multiple top-of-the-line everything-but-the-kitchen-sink models like the Plantronics Voyager Pro would still be having problems.
I was seriously considering getting the OnePlus One, the Nexus 6 and even the iPhone 6 hoping the issue would finally be fixed. It's ridiculous that a phone commonly accepted as the measuring stick of the Android world would be having problems with simple tasks like driving a bluetooth headset. *very disappointed*
Me too. Two days with my new N5 and when I use my Sony SBH20 people hear me bad... With my N4 no problem. Its annoying! Ive to speak with headset because Ive problems with my left arm and legs, I only have the right to hold the phone, I cant do anyhing more and when I walk I need that arm to hold my cane.
I dont see a real solution, I will have to return the N5