Related
I have two bluetooth devices that look like headsets to my (CDMA)Hero -- an AT&T cordless phone that pretends to be a headset and treats it like a second landline (ie, I can make outgoing calls, and answer incoming calls, using any of the cordless phone's handsets), and Ford SYNC (which also appears to be a bluetooth headset and integrates it with the car stereo for handsfree use while driving).
The problem is, SYNC doesn't "turn off" when the car is off -- not even when the car is off and the alarm is on. It's *always* active, and always trying to be the Hero's metaphorical object of desire. Worse, it seems to have a more powerful radio and/or better antenna than the AT&T cordless phone, and fights with it constantly for the phone's attention.
This isn't a new problem... it happened all the time with my Vogue/Touch/PPC6900, but back then I didn't know what the root of the problem was. I just knew that my phone seemed to flake out a few times a week, and I'd get incoming calls that couldn't be answered with the cordless phone handsets. Since the Hero helpfully "makes Toast" and alerts me every time there's a handoff, I quickly discovered the problem's root. Now, I'm just trying to find a solution to it.
Just to give you an idea of how bad it is, my car is about 25 feet from my kitchen (where the AT&T cordless phone's base is), on the other side of a concrete wall and two drywall walls... and it *still* occasionally manages to grab possession of the phone away from the AT&T cordless phone.
So... is there some way to tell the phone, "If you see both SYNC and the AT&T cordless phone, ignore SYNC and pair with the phone... in fact, just ignore SYNC entirely if you've seen the AT&T cordless phone within the past 30-60 seconds"? Or, failing that, is the Hero's bluetooth pairing behavior governed by something that can be overridden by a program of my own -- say, an event handler that wedges itself into the bluetooth event chain and prevents the Hero from ever hearing SYNC's mating call if it's currently connected to the AT&T base? Where in the API would I even *look* for something like this?
Hey everyone,
Has anyone noticed bluetooth issues? I've pointed them out in other threads, but they seem to be glossed over. I hate to seem like a noob by creating new threads, but I fear that the issue is being looked over by most people. I've read a few reports of people having issues with their phones connecting to their cars or headsets automatically. Has anyone else faced these issues?
I specifically cannot get my BT headset to connect unless I unpair and repair it everytime I want to use it. Sometimes even during a phone call the headset will drop connection and wont reconnect unless i turn it off and on a few times. For reference, I've tried multiple BT headsets and they all behave the same way. These headset's also work just fine with my Galaxy S2, just not with my S3 (international on XLE8)
No problems with bluetooth here and I use it a lot (HS3000, Logitech Boombox, PS3 and Wii controllers too).
No issues here. Phone sometimes doesn't pair automatically with the BT kit in my work car, but I've had that issue with my S1 and S2 in the same car so I'd say it's a problem with the headunit.
Works perfectly with the Sony headunit in my own car, and connects to my mate's fine.
ok, what firmware rev are you guys running? im going nuts not being able to use bluetooth here!!
somewhat related.
i often leave my sgs3 connected to my laptop via usb when i fall asleep. at morning, battery's charged 100% obviously and phone isn't hot.
last time around, i was listening to music via hm3700 bluetooth headset. then later turned off the bluetooth headset. i forgot to turn off the bluetooth on sgs3 and again fell asleep while it's still connected via usb to laptop.
when i woke up at morning as usual battery's charged 100% but the sgs3 was hot, not so hot but isn't anywhere the normal hot we're accustomed to.
connects automatically to my car's BT built-in system. Only needed to pair once.
Works very well with my Sennheiser PXC 310 BT.
If I switch on the headphones the phone automatically connects to it.
can everyone please detail their firmware/kernel they are using?
i am on XXALE8, with the stock kernel
I have problems on XXLE8 as well connect it to my car head unit and it acrually crashes the headunit after 5 mins being connected . After the heaf unit crashes 3 times it requires a pin code. Iphone 4, 4s and gs2 connect no issues.
Sent from my GT-I9300 using Tapatalk
bean12147 said:
I have problems on XXLE8 as well connect it to my car head unit and it acrually crashes the headunit after 5 mins being connected . After the heaf unit crashes 3 times it requires a pin code. Iphone 4, 4s and gs2 connect no issues.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
thanks for your input, i upgraded to XALF5 and still having the same issues. this is frustrating!!!!
Oddly - my phone will automatically connect to my cars in-built BT system, but it won't auto connect to my Jawbone Era without switching BT of and back on....
I also have problems, with my build-in bt in my car. Have XXBLH3. Connect fine, but drop the connection 2-3min after. My SGSII have no problems
No Ringtone through Bluetooth
Okay here is my problem……I want my custom ringtones i have set for contact to play in my Bluetooth headset when a receive a call, not that dumb ring. That way I will know if I want to take the call or not because I can tell by the ringtone who is calling. Why would Samsung disable this feature. my iPhone 4s plays the ringtone I have setup when I get a call. Is there anyway to do this. I ride a motorcycle and I have a device called a Chatterbox that let’s me connect via Bluetooth to my phone so I can hear my music and talk and make calls while I am riding. On my iPhone 4s my music would pause my custom ringtone would play and I could decide it I wanted to take the call or send it to voicemail, then my music would start right back up from where it left off. Right now my Galaxy i717 and my Galaxy i747 (Note and S III) just play this annoying ring and I can’t tell who it is! Any have a fix or work around for this.
Hmmm, the sound on my cars bluetooth gets distorted and only a reconnect will fix, and more worringly sometimes the S3 will not wake up after disconnecting from my car and only a hard reset will solve it.
My S2 did pretty much the same thing.
This seems to be a known problem, but after a day of research, I still don't see a solution, or really understand if this will eventually be fixed by (1) a developer update by someone here much smarter than me, (2) a Samsung update, or (3) will never be fixed.
Issue is:
When the SGS3 headphone is engaged (ie: a stereo phone cable from my SGS3 to my car AUX input), you cannot hear and calls in or out from the built in auto bluetooth (mine is an Audi A3). I've tested many alternatives seen on these forums including, TTY settings, call settings, grinding down the stub of the cable so it doesn't fully engage the headphone, etc.
All to no avail, as when the headphone is engaged (a notification of this pops up on the screen), the default sounds ALL go to the headphone source. Of course, the car mutes the audio mode when the bluetooth is enabled, so the sound is lost! What needs to happen is that the phone needs to allow the phone sounds to flow through the bluetooth. Why this doesn't happen by default confuses me. Never had a problem with my HTC Inc2.
Can a solution to this be developed by some of you talented guys out there working on fixes and mods?
[email protected] said:
This seems to be a known problem, but after a day of research, I still don't see a solution, or really understand if this will eventually be fixed by (1) a developer update by someone here much smarter than me, (2) a Samsung update, or (3) will never be fixed.
Issue is:
When the SGS3 headphone is engaged (ie: a stereo phone cable from my SGS3 to my car AUX input), you cannot hear and calls in or out from the built in auto bluetooth (mine is an Audi A3). I've tested many alternatives seen on these forums including, TTY settings, call settings, grinding down the stub of the cable so it doesn't fully engage the headphone, etc.
All to no avail, as when the headphone is engaged (a notification of this pops up on the screen), the default sounds ALL go to the headphone source. Of course, the car mutes the audio mode when the bluetooth is enabled, so the sound is lost! What needs to happen is that the phone needs to allow the phone sounds to flow through the bluetooth. Why this doesn't happen by default confuses me. Never had a problem with my HTC Inc2.
Can a solution to this be developed by some of you talented guys out there working on fixes and mods?
Click to expand...
Click to collapse
Maybe if you go into the control panel of your car's built in computer and check the audio and Bluetooth settings it has, that might fix things.
Thread moved
This does not belong in Development.
So you have bluetooth for phone only and younlisten to your music with aux in? I would say if you had an aux in cable with the mic on it like the headphones, then the phone audio would go out over to the radio... But do they make those or how hard would it be to hack your free headphones you got into a double male aux cable
There are no options anywhere in the car settings.
Car mutes phone audio.
Juicy92 said:
So you have bluetooth for phone only and younlisten to your music with aux in? I would say if you had an aux in cable with the mic on it like the headphones, then the phone audio would go out over to the radio... But do they make those or how hard would it be to hack your free headphones you got into a double male aux cable
Click to expand...
Click to collapse
The sound does go through the phone audio already. But like almost all cars, when the car sees a bluetooth call in or out, it MUTES the audio coming in from the radio, the CD, or any AUX input. The phone should send call audio through bluetooth, but it does not.
Is it not possible to either play the music through the bluetooth or to turn off bluetooth all together. The phone mic would pick up wouldn't it
This is only possible if you have a newer car stereo with A2DP.
Sent from my SCH-I535 using xda app-developers app
So is this just a Samsung problem for me, or for all?
So I am correct that nobody with a bluetooth car phone setup (but no bluetooth streaming) is able to plug their headphones into their aux jacks and still make/receive calls?
Or is this related just to the SGS3? Or just to my Audi bluetooth options?
Would an eventual solution come from a xda brainiac update, from Samsung, or somewhere else?
Do some of you have built in car setups (no bluetooth streaming) that DO WORK with the headphones plugged in?
I can attempt to pair to my brothers car today or tomorrow if that will make you feel better. My bluetooth setup is aftermarket and streams both
I am also curious as to what happens if you don't have bluetooth enabled at all
What about car audio only. Wouldn't it automatically mute your music and then throw the call over bt or is the aux out overpowering the bluetooth signal. Let me look for a way to possibly disable the process that starts when you plug in headphones. Don't count on anything though
---------- Post added at 01:11 AM ---------- Previous post was at 12:52 AM ----------
I was doing a little brainstorming here and even though I am quite a novice with tasker, you may be able to make a task that pauses music and transfers call to bluetooth when both bluetooth and headphones are connected. I am not sure if it is an input device problem or if the phone is just dumb or what, but it may be worth a shot
Juicy92 said:
I can attempt to pair to my brothers car today or tomorrow if that will make you feel better. My bluetooth setup is aftermarket and streams both
I am also curious as to what happens if you don't have bluetooth enabled at all
What about car audio only. Wouldn't it automatically mute your music and then throw the call over bt or is the aux out overpowering the bluetooth signal. Let me look for a way to possibly disable the process that starts when you plug in headphones. Don't count on anything though
---------- Post added at 01:11 AM ---------- Previous post was at 12:52 AM ----------
I was doing a little brainstorming here and even though I am quite a novice with tasker, you may be able to make a task that pauses music and transfers call to bluetooth when both bluetooth and headphones are connected. I am not sure if it is an input device problem or if the phone is just dumb or what, but it may be worth a shot
Click to expand...
Click to collapse
Your setup is not like mine, and should probably work, as you don't have to plug in the headphone jack. Yes, the problem is that IF the headphone jack is plugged in, ALL sound output goes through that and the bluetooth is disabled (even the symbol on the phone screen is grayed out.
With your bluetooth plugged in, just try putting the earbuds in the phone, then make a call to anyone, then see if your bluetooth icon on the phone call is not grayed out. Now unplug the ear buds and see if the icon doesn't come back on. This is the problem I have.
Never had any problems with either stereo worked fine in my altima and benz. I used aux + bluetooth no problem on my epic4g for the past 2 years and when I first got my s3 it was working until I did an update. Then it broke it.
Sick of having to unplug the aux cable everytime I get a call to allow it to switch to bluetooth
Need some people to test this, please...
I'd like to see if the problem is with the rooted phone image or if this problem also exists on stock, unrooted phones.
If you can:
1) pair your phone to your factory car bluetooth, or even a bluetooth headset that does not stream audio.
2) have any pair of headsets or an aux cable ready to plug in.
3) make a call using the bluetooth to anyone (ideally something that has an automatic answer phone cue like this 919-238-2000)
4) while the call is proceeding with the car bluetooth or bluetooth headset, plug in the headphones, or any cable into the headphone jack.
5) WHAT HAPPENS???
Is it (a) you still hear the phone call through the bluetooth, or
(b) you don't hear the call any more and the bluetooth headset icon on the phone pad goes out?
6) Please state what phone you have, what provider you have, and whether the phone is stock or rooted.
THANKS.
[email protected] said:
I'd like to see if the problem is with the rooted phone image or if this problem also exists on stock, unrooted phones.
If you can:
1) pair your phone to your factory car bluetooth, or even a bluetooth headset that does not stream audio.
2) have any pair of headsets or an aux cable ready to plug in.
3) make a call using the bluetooth to anyone (ideally something that has an automatic answer phone cue like this 919-238-2000)
4) while the call is proceeding with the car bluetooth or bluetooth headset, plug in the headphones, or any cable into the headphone jack.
5) WHAT HAPPENS???
Is it (a) you still hear the phone call through the bluetooth, or
(b) you don't hear the call any more and the bluetooth headset icon on the phone pad goes out?
6) Please state what phone you have, what provider you have, and whether the phone is stock or rooted.
THANKS.
Click to expand...
Click to collapse
I'm pretty sure I wasn't rooted the first time I tried it. In any case, I wrote to Samsung support on Facebook, and got this reply:
"Hi Chris, thanks for reaching out! You are correct, you cannot use both Bluetooth and Aux at the same time. A few of our customers found a work around by using an A2DP profile with hands free in the car. I apologize for the inconvenience."
So we know they are getting reports or they wouldn't push AD2P as a solution. I think if enough people write in, they will fix this in an update. We really need a critical mass of people to complain to Verizon and Samsung for this to happen. He did say when I replied asking about a fix, that he had passed my concerns on, etc., etc.
Mention "lawsuits from car accidents" when you write in...
sluzbenik said:
I'm pretty sure I wasn't rooted the first time I tried it. In any case, I wrote to Samsung support on Facebook, and got this reply:
"Hi Chris, thanks for reaching out! You are correct, you cannot use both Bluetooth and Aux at the same time. A few of our customers found a work around by using an A2DP profile with hands free in the car. I apologize for the inconvenience."
So we know they are getting reports or they wouldn't push AD2P as a solution. I think if enough people write in, they will fix this in an update. We really need a critical mass of people to complain to Verizon and Samsung for this to happen. He did say when I replied asking about a fix, that he had passed my concerns on, etc., etc.
Mention "lawsuits from car accidents" when you write in...
Click to expand...
Click to collapse
I have an issue when it's plugged in via Auxiliary there's a nasty echo the caller hears on the other end because of this headphone mode. Anyway to turn it off?
I will probably return it for this reason amongst others.
Belkin Y37 from Amazon will solve this issue, or provide an alternative.
I can fully confirm the functionality of the Belkin F8Z492TTP. It is now custom installed in my A3 with a direct power hookup and direct connection to the aux input. For power, I had to hook up a 12 volt car outlet behind the dash, insert a 12v to usb adapter, and splice the power cord from the factory transformer to a USB cable. Power is with a micro type H plug that Radio Shack does not have. They should give you a usb to type H cable with it.
Anyway, the Galaxy S3 will connect to two bluetooth devices at the same time...the Audi bluetooth and the Belkin Y37 Bluetooth. I put a shortcut button for bluetooth on my home screen which pulls up the options. You DO HAVE TO RECONNECT BLUETOOTH each time you get in the car, but you had to manually plug in the cable the other way.
When a call is made, the car bluetooth takes over with full steering wheel controls, and when it ends, the audio goes back on (I think automatically). Since I have constant power to the Belkin through the 12v, if you step away and then come back, you can automatically regain your connection, which is nice.
I did the modification to the Belkin where I broke it carefully open and pulled the metal innards that are purely designed to give it a feeling of mass. All that is inside is a teeny circuit board that must have cost $1 tops! Belkin lists this at $50, although it is half that on Amazon.
All in all, a decent solution to a frustrating problem. Sound is pretty decent.
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