My Sony Xperia T has worked perfectly since new, however since accepting the OTA Android update to 4.3 my Bluetooth doesn't work properly in my car now (used to work perfectly).. I can still make and receive calls, and get audio through the car audio, if I initiate the call (or answer the call) directly using the phone screen rather than the car controls, but if I try to make a call (or answer a call) using the car controls, it doesn't work. I have already tried deleting and re "pairing" the devices etc, and after reading several posts it would appear that there are bugs with the 4.3 update..
This is the first time that I have experienced any issues with my phone so I'm a bit new to this.. Is this something that might be resolved quickly, I assume that Sony are aware of these issues already, and are working on an update to fix them?? Or is it something that I can fix myself?
steve_the_diver said:
My Sony Xperia T has worked perfectly since new, however since accepting the OTA Android update to 4.3 my Bluetooth doesn't work properly in my car now (used to work perfectly).. I can still make and receive calls, and get audio through the car audio, if I initiate the call (or answer the call) directly using the phone screen rather than the car controls, but if I try to make a call (or answer a call) using the car controls, it doesn't work. I have already tried deleting and re "pairing" the devices etc, and after reading several posts it would appear that there are bugs with the 4.3 update..
This is the first time that I have experienced any issues with my phone so I'm a bit new to this.. Is this something that might be resolved quickly, I assume that Sony are aware of these issues already, and are working on an update to fix them?? Or is it something that I can fix myself?
Click to expand...
Click to collapse
Firstly, head over to xperia T forum, this is the z ultra
It's most likely a rom issue and downgrade is probably best solution but ask your guys to make sure.
Sent from my C6833 using XDA Premium 4 mobile app
Related
Ok, I've this issue since the day I upgraded from v1.6 to 2.1 and until there isn't any fix available. The topic exists in Official SE Forum and there isn't any useful info provided by them.
In hope to get help from XDA members, here is the issue:
Does anyone notice that when you are using bluetooth headset, the proximity sensor doesn't work? Is it a bug in Android v2.1 or am I missing something? I'm using MW-600 with X10i Android 2.1 if that matters. (The same phone and bluetooth worked fine with Android v1.6)
I'm interested into it too but it seems that there is no way to fix it! :-/
The proximity sensor works when the phone is connected to MW-600, but it will not work when dialing or receiving a call because the audio is directed to the bluetooth device and you dont use the phone's earpiece to hear the audio.
sharathx10 said:
The proximity sensor works when the phone is connected to MW-600, but it will not work when dialing or receiving a call because the audio is directed to the bluetooth device and you dont use the phone's earpiece to hear the audio.
Click to expand...
Click to collapse
Agreed, but when you are using bluetooth, I hope you don't expect me to carry to phone in my hand. I usually leave it in my pocket and this causes unnecessary touches and often ends in either disconnect bluetooth or call ended.
Sometimes I notice it causes to open the contacts and dial someone's number
Please also mind that all these problems aren't found when you use the same bluetooth the same way with Android 1.6 !!! Now how to justify that?!?
So, I'm having a strange issue with my new Note that I can't quite determine where the root cause may be, or if it's a known issue.
If I register my Note with my car as both a phone and an audio device (how the Infiniti nav/stereo works) I can use the Note as a phone fine UNLESS I start an audio app, such as Pandora. Once a2dp audio starts the Note will no longer connect as a phone device, but it works fine for audio.
I had the phone paired with the stock ATT rom but only used it as a phone, so unfortunately, without a restore to stock, I can't tell if the problem exists with the stock rom.
I flashed to flappjaxxx's rom (which I love) the same day I setup the phone to run Pandora via Bluetooth and that's when I started seeing the problem.
I also see some random connect/reconnects that seem a bit more than usual.
So, I can't say there's a correlation, or if this is a known ICS beta issue or what, but I'm hoping it is and that it's not a design flaw
Way I see it it's either:
1. Flashing to any ICS beta rom has the problem, currently?
2. It's in flappjaxxx's build (doubtful)
3. It's user error...(possible )
4. It's an app issue (ie. Pandora is causing the problem?)
Anyone have any thoughts, suggestions or insights? I've done some searching but haven't found this exact issue yet on any posts.
Thanks!
I have a Kenwood DNX9960 in my Avalanche. It connects also for phone and for streaming media. I can be streaming media from either the stock music player or an internet site like pandora or TuneIn and my calls will automatically come through. When the call ends it goes right back to streaming.
It autoconnects to both as long as my phone is in range when I turn on the kenwood. I did have an issue at first where it would not autoconnect. I deleted the pairing from both my phone and headunit. Then when I repaired I paid close attention to check any boxes to "Always" allow connection and I haven't had any issues since.
I understand the normal pairing process, I've had several phones before that worked fine prior to the Note. So, I'm thinking that it is probably a corrupt bluetooth db... I'm going to be reflashing to Flaps new rom and we'll see how that does
Is there a way to delete the pairing from the nav? I would try that
Sent from my SAMSUNG-SGH-I717 using xda premium
There is. I've tried it all, on both sides of the pairing.
I've reflashed the phone to the B6 from FJ, still no joy. The pairing db was new (so no chance of corruption on the phone) and the pairing deleted on the device.
It seems to be a problem with the phone switching between a2dp and phone bt. When a call comes in (while playing say Pandora over bt) the audio cuts out and then the car shows "disconnected" and then "connection failed" if trying to reconnect to the Note as a phone (ie hitting the phone button in the car).
I'm hoping it's the current ICS build. Just have no way to really know. Hoping some other folks will have seen the same issue.
Going to run some tests with different audio sources and see if the behavior is the same.
Well things seem to be working now, for no obvious reason I'll have to assume that the reflash resolved the issue, I just can't tell for sure why it didn't work immediately after. I think it's due to deleting the old pairing on the car and not shutting down the vehicle.
Cheers.
BT connections
I have similar problem connecting to van audio system (vauxhall). After some experimentation it appears to be an ICS problem, if I reflash my note with gingerbread I have seamless connections for both audio and phone. As soon as I upgrade even with offical ICS bluetooth connections become problematic, I can pair but not autoconnect. Tried samsung and they just "fob off" with it's an incompatable device. Until a bug fix is issued it appears as though it's a choic of staying with gingerbread and have a working system or ICS and no handsfree.
Hi all,
Having some issues with my z2 bluetooth dropping. Very strange.
I can connect my bluetooth on the z2 to any device without issue ( namely my 2013 Hilux), however, after 40s, my bluetooth will drop, and reconnect withing about 2-3 seconds, and start the cycle again, on and on forever. I am not sure why it does this? It happens when i just leave it connected and do nothing with it, or when i play music too.
The interesting thing is, if i receive a call, i will be able to speak with someone for the first 40s, then the bluetooth will disconnect and reconnect (all in about 2-3) seconds, and after that i will not experience any more bluetooth drops for the entirety of my journey, either through leaving it there connected not doing anything or playing music. Very strange.
Ive tried turning, stamina off, wifi off, nfc off, etc but nothing seems to change it.
Does anyone have any insight on this? Its like the bluetooth on the z2 is requesting something from my other devices, and when it doesnt receive it, shuts off, then as my bluetooth is on and recognizes my paired device is nearby, reconnects straight away. If i get a call as ive mentioned, its like whatever the z2 is looking for it just ignores it and keeps the connection regardless.
Happens to me in my 2014 MB. It's definitely something sony is doing wrong with their Bluetooth. I never had that issue with other phone brands (Samsung, HTC, Moto).
Paperinik68 said:
Happens to me in my 2014 MB. It's definitely something sony is doing wrong with their Bluetooth. I never had that issue with other phone brands (Samsung, HTC, Moto).
Click to expand...
Click to collapse
Ahh so not an isolated case!
I have no issue with my Note 3 or my older HTC One. Its strange. I remember reading something about Bluetooth 4.0 requesting a device descriptor or something descriptor (my bluetooth knowledge is a bit lacking), could it be that thats what its not receiving and hence dropping out? Surely there must be someone on XDA who knows a workaround for this issue.
I have the same issue with 2011 C-Class and Z2 drop out constantly and turn it self off.
The Xperia Z fix seems to have fixed the issue and will auto reconnect, but it is still annoying with the temporary connection drop.
Anyone know if this will be fixed in firmware update?
Ive found that 4.4.2 has alot of base module issues
You will have wait for sony to update to 4.4.3 or 4.4.4 or 5.0
Sent from my D6503 using XDA Premium 4 mobile app
Any idea when the update will be out?
Extremely annoying, even with the Xperia bluetooth fix, the BT fix app will constantly come up with connecting/reconnecting messages.
Almost unusable in the Mercedes...
Mjollnir1983 said:
Any idea when the update will be out?
Extremely annoying, even with the Xperia bluetooth fix, the BT fix app will constantly come up with connecting/reconnecting messages.
Almost unusable in the Mercedes...
Click to expand...
Click to collapse
This month or next month
About 2-5 weeks from now says Sony service centre employees
Sent from my D6503 using XDA Premium 4 mobile app
I turned off the Bluetooth media functions and enable only the telephony features, seems to have stabilized...
I have BT music streaming problem too. Z2 connects to pioneer deh-x9600bt car radio, but the songs keep skipping every now and then. I have tried every possible settings, changed memory card, tested spotify and deezer and problem still exists. HTC phones working without issues in my car, so must be something to do with Sony.
edit: running 4.4.4 existenz currently, but problem has been from the start
any update to this issue? Just bought my Z2 and I am also experiencing this Bluetooth "skipping, jumping, dropouts" every minute or so while listening to my Chevy Volt bluetooth audio. I am on 4.4.4 but am considering downgrading it to 4.4.2, root, and check out other roms to see if problem still persists.
fixed!
found a fix!
1) install this app: https://play.google.com/store/apps/details?id=de.devmil.xperiabluetoothmediafix&hl=en
2) open app, check the BT connection that have stuttering / dropouts
3) restart phone
4) wait for message box to appear momentarily to say "BT XXX reconnected" or something to that effect
5) test it out and....???profit!
update: perhaps I spoke too soon. A week of using the app this BT connection dropouts still appears at random. Rebooting the phone is what usually fixes it. I wonder if the bluetooth stack would fix it...can it be replaced in the phone kernel?
well I did more experiment with it this morning. Little background info: My car has bluetooth audio for phone, stereo, and message. The phone is C6503 with .167 firmware. These are the result to see if it fixes the stuttering:
1) toggleing bluetooth on/off: no
2) toggleing throw (audio cast) on/off: no
3) disable auto throw in throw setting: no
4) restarting phone: yes (but AVRCP would stop working; i.e. can't skip track from car. Also notices option to read text message was gone)
5) delete MAP profile in bluetooth setting: yes (seems to work for the rest of the ride...stay tune)
So if you don't mind not able to have the car read your text, this is the fix.
I've spent the last hour hunting for a Bug List for CM12 or AOSP Lollipop on the Z2, but I can't find anything useful. I'd love to install AOSP on my Z2 but I don't see the point if any of the hardware is non-functional.
Can anyone point me at the list of known issues for CM12, or the common ones for AOSP roms?
Do any of the ROMS actually have the Camera, WIFI, BlueTooth, Data, Tap to wake, etc all working well enough for a daily driver?
The only thing I found is the Known issues list on the CM12 WIKI but it was last updated 3 months ago, and the list looks way to short to be true.
As far as I tried it, only problem is the speaker is not working on calls. I mean you can make a call through the earspeaker, headset, Bluetooth etc. but you can not make it through the speaker. The sound just won't come out.
Other than that everything works.
Compared to stock Sony software;
-Google photos app isn't full screen unlike Sony Album.
-it's still far better than many phones on the market but Sony's Walkman sounds slightly better than CM's music apps.
-CM's music and call sounds are noticeably higher, but slightly worse on quality
-no Xposed for Lollipop yet
-when using Sony software, I always use it on power save mode but on the AOSP Lollipop, the top bar is orange when powersave mode is on. That's annoying
Sent from my D6503 using XDA Free mobile app
Sounds like there aren't any really big issues to worry about unless you need to put a call on loudspeaker, which I almost never do. It's bound to be a few months before we see lollipop arrive from a the mobile carry. Think I'll pick a ROM and try it out.
Thanks _delice_doluca_ most helpful
Edit: Xposed for lollipop... http://forum.xda-developers.com/showthread.php?t=3034811
lazarus_mub said:
Sounds like there aren't any really big issues to worry about unless you need to put a call on loudspeaker, which I almost never do. It's bound to be a few months before we see lollipop arrive from a the mobile carry. Think I'll pick a ROM and try it out.
Thanks _delice_doluca_ most helpful
Edit: Xposed for lollipop... http://forum.xda-developers.com/showthread.php?t=3034811
Click to expand...
Click to collapse
I'm on CM12 and the issues I have come across so far are
loudspeaker not working and earpiece not working on whatsapp calls.
There are some random force closes in the camera app
As a daily drivers it's good enough.
You cannot hear any sound on earspeaker from apps like Viber or Skype.. Voice on Loudspeaker is working fine during Internet calls.
My speaker does not work at all in any app or in calls. Also, Double Tap to Wake does not work.
Here is list of CM12 bugs that i came across. Not official. http://forum.cyanogenmod.org/topic/103915-cm-12-nightlies/
AlanDS said:
You cannot hear any sound on earspeaker from apps like Viber or Skype.. Voice on Loudspeaker is working fine during Internet calls.
Click to expand...
Click to collapse
Hello guys,
My XAU Dual showing microphone issues during making calls! when I make a phone call my friends keep complaining about barely hearing me (very low voice) or my voice is like someone talking in a deep tunnel with too much echo ..sort of that!
here are some things I tried to fix the issue but all failed to fix it:
1- I tried factory resetting my device
2- tried repairing my device software using Xperia Companion
3- tried disabling audio enhancement (ClearAudio+ ....etc)
4- in settings>call>SIM>Equalizer ...set to normal
5- tried looking for microphone noise suppression in settings.. can't find it
Didn't drop my device & never exposed to any fluids!!
Tho, I ran diagnostics>tested my microphone, one time I hear my voice good, then gave it another try later on & the microphone recorder a very low sound!!
Am really outta options here & this issue really sucks
My device model number is F3212, running android 6.0, build number 36.0.B.2.146.
Any ideas..
I've been experiencing this problem on two different XA Ultras. The microphone seems to switch to the one on the top of the phone so if you hold the phone upside down people can hear you. I've had to switch to speakerphone output to talk to people when this happens. Switching back to phone from speakerphone sometimes makes it work normally but not all the time.
I suspect it has something to do with an app that is running earlier, maybe google play music or OK google.
I have tried reset and it doesn't help. The problem comes back.
There is a similar if not identical issue on another Sony phone, the solution being to turn off microphone noise suppression. I haven't tried this.
grogzero said:
I've been experiencing this problem on two different XA Ultras. The microphone seems to switch to the one on the top of the phone so if you hold the phone upside down people can hear you. I've had to switch to speakerphone output to talk to people when this happens. Switching back to phone from speakerphone sometimes makes it work normally but not all the time.
I suspect it has something to do with an app that is running earlier, maybe google play music or OK google.
I have tried reset and it doesn't help. The problem comes back.
There is a similar if not identical issue on another Sony phone, the solution being to turn off microphone noise suppression. I haven't tried this.
Click to expand...
Click to collapse
I didn't notice that flipping the phone or switching to speaker output might work, gotta try it first.
What bugs me the most is the fact that I can't find anything related to disabiling microphone noise suppression at an section of this device settings!
Am using a headphone currently & waiting for Android nougat to hit the device & hopefully fix the issue.
This problem was never there when I first used my device out of its box, but later on it appeard after may be 2 upgrade patches of Android 6.0 few months later.
Waiting is my only hope...