I have a problem, not certain what caused it
1) either temp root and deleting some bloatware or
2) OTA update
but now my bluetooth car kit does not work properly.
before it worked fine, now it connects, can answer calls, but call audio does not transfer to car kit speaker. I deleted the connection/pairing and re-paired it, still no joy.
Wounder if i can copy in a bluetooth driver (have perm/temp root again)
Has anyone extracted such?
Again posting in DEV !
READ RULES before posting
Sorry figured i would need a dev to tell me how to fix this.
Hello, I am quite an avid reader on xda and have gained a lot of knowledge from this forum. Unfortunately I have run into a problem I cannot seem to understand.
I have a Samsung Omnia 7 (T-Mobile, flashed a stock omnia 7 rom,unbranded). Whenever I pair it with my Car audio (I have a Suzuki Alto) the audio drops atleast 5 times a second.
Also the mic voice quality is terrible (people on the other end complain of a lot of static & as if i were speaking from a thousand miles away).
I also happen to have a developer unlock on my phone so this gives me easy access to the xaps.
My Samsung Omnia 7 details are :
OS Version : 7.10.7740.16
Firmware Revision Number : 2424.11.9.2
Hardware Revision Number : 3.15.0.4
Radio Software Version : 2424.11.9.1
Radio Hardware Version : 0.0.0.800
Bootloader Version : 5.9.0.6
Chip SOC Version : 0.36.2.0
I read on the forum about using the Advanced Config tool to set the Bitpool to 51 and set Joint Stereo to 1. But whenever I tried doing that a popup would say "Unable to apply changes"
So I navigated to HKLM\SOFTWARE\MICROSOFT\BLUTETOOTH\A2DP
and I saw ONLY ONE subkey that as Devices that had 4 Subkeys labelled 1,2,3,4 each with a binary value (Address)
I added a key Settings to HKLM\SOFTWARE\MICROSOFT\BLUTETOOTH\A2DP and I added the following values to it:
Bitpool : 51 Dword
MaxSupportedBitpool : 51 Dword
SampleRate : 48000 (this was added by advanced config later when I was trying it out again)
UseJointStereo : 1
I tried testing these settings with my car bluetooth kit but the results were the same. At first I was baffled when I didn't see the key SETTINGS in the HKLM\SOFTWARE\MICROSOFT\BLUTETOOTH\A2DP path.
Is this normal?
Is there any way to fix the choppy extremely low quality bluetooth audio?
(PS I do not want bluetooth over video, also I have set SupportCLI from 0 to 1)
Hi,
Got the same problem.
BT worked in the really early days of my Omnia but since then, I am unable to listen to music on my Motorola S9 headset (even worst than you ! Drops 10 times a second !). Even the call quality when using a mono BT earpiece, sound is distorded and other side does not understand a thing of what I say !!
Sad to say but I really think Omnia 7 are subject to Bluetooth hardware failure.
Really think there is no way and quiet forgot about using BT on my handset. Shame because I was using my S9 all the time with my previous wm device and it was really working very well.
Anyway, if you figure out what's wrong, please, share with me ;-)
Last thing, did you apply some audio tricks through the Samsung diagnosis app ?
Good luck
Thomas
Sent from my OMNIA7 using Board Express
Hi, thanks for replying, I don't think the omnia 7 is subject to BT hardware failures as i've read about several omnia 7s running okay.
Also I did apply the sound trick using the diagnosis app but it messed up the audio on my phone. 30/30 sounded like the speaker is going to explode. Though the changes used to fall back upon restarting, they would come back if I played a song or if I got a call. So I had to re-flash my rom & reupdate it to mango.
I haven't tried BT on any pre-mango version but I guess its going to be the same.
Anyways lets hope Microsoft comes out with a fix in their tango update in Q2
:fingerscrossed:
Really wonder if BT problem may be linked to the sound trick. May sound weird but as I said, Bluetooth was working flawlessly at the beginning and I'm not 100% sure but it may have stopped working the day I messed with Samsung diag on sound settings.
More than that, I wonder at which OS level these settings are managed (even wondering if a hard reset or ROM flashing can roll back the whole thing to the factory settings)
I hesitated to hard reset in hope it will work again but I do not want to lose everything without being sure problem will be solved (and will never know id I don't do it )
Thomas
Sent from my OMNIA7 using Board Express
In my opinion the settings are rooted in the rom, you cannot program the hardware from the rom but only change the settings (this is what i think) anyhow, my BT settings never worked, not before messing with the audio settings in the diagnosis, not after, also what's weird is that the a2dp settings weren't present in the registry, i had to add bitpool, maxbitpool etc. manually (no change even then)
anyways, lets hope someone knows of a workaround or microsoft regards this issue as 'serious'
thanks
EDIT : @NebZoNe I tried your settings and they didn't work for me thanks for the suggestions anyways
adding a registry entry for bluetooth like bitpool should be made in ..\AD2P\Settings
see http://forum.xda-developers.com/showthread.php?t=1351043
try a registry editor instead of schaps' advanced config...better.
max supported bitpool must be 80 (dword)
if you use 51 for bitpool then you can't use jointstereo (set it to 0), or use 53 then you will be able to set 1 for jointstereo...
once you've connected your car's stereo to your device try to find the second tweak i've written (dots between \ are numbers) to make sure the sound will be streamed in stereo (if you setted bitpool at 51 for sure!)
good luck.
Hello, I used the root tools by cliff74 & advanced config to verify the settings. Anyways, I haven't tried bitpool at 53 & will do.
Question : in your post you have said this :
HKLM\Software\Microsoft\Bluetooth\Device\........\ Services\..........(then u should see u're in stereo sound settings)
enabled : Dword = 1
The dots are the numbers, so how do I know what device is which number?
Thanks!
japmeet said:
Hello, I used the root tools by cliff74 & advanced config to verify the settings. Anyways, I haven't tried bitpool at 53 & will do.
Question : in your post you have said this :
HKLM\Software\Microsoft\Bluetooth\Device\........\ Services\..........(then u should see u're in stereo sound settings)
enabled : Dword = 1
The dots are the numbers, so how do I know what device is which number?
Thanks!
Click to expand...
Click to collapse
Do you use so many BT devices that you can't identify them in that path?? i only use bt headphones so i didn't have that kind of problem sorry...
and i'm agree that what you'll find behind \Device\ is straightly linked with what you use...so you must find the string "stereo sound" for every device you connect...as well as you'll find a string value with your bt device name after first connection....
I must insist on the fact that schaps advanced config is screwing with BT's manual reg.edition...and there's no reg lines for samplerate values, they are setted up straight from bitpool level (51:48000; 53:44100; 76:96000)
unfortunately, having a look to other threads, it seems that samsung devices usually know issues with bluetooth function...
well in HKLM\SOFTWARE\Microsoft\A2DP\Devices I have 4 subkeys that are :1 ,2,3,4 each with 0 subkeys and 1 value that is address (a binary value)
In HKLM\SOFTWARE\Microsoft\Bluetooth\Device I have 1 subkey that is 00137b96be74 that has 1 subkey "Services" which has 2 subkeys :
The first subkey has the following contents :
Status (a subkey that is empty)
channel (value : 0 dword)
enabled (value :1 dword)
name (stereo sound)
sdprecord (binary value)
Similarly the other subkey of \Device\ has the same contents except for channel and name
Channel (1)
name (Hands-Free //I suppose this is my car bt audio but when i sync my phone with the car it shows BT Radio as the car's head unit's name)
Also i have logitech free pulse BT headsets and I have the same problem with that
well, seems that's alright i've got the same layout...
the only thing i can do is sharing my ad2p settings layout...
hope for you it's not a hardware issue...
I do not have the default key (not sure if that would make any difference) but anyway, thank you
japmeet said:
I do not have the default key (not sure if that would make any difference) but anyway, thank you
Click to expand...
Click to collapse
Same situation with my omnia 7 - and i have motorola s9 like you. I tried many settings in registry but all of them have absolutely no effect ((
though I shouldn't be bumping but *help?*
As I already told, sorry but I really think the reason is really simple. BT chip on Omnia 7 is defective, this is a hardware failure and I am quiet sure it can not be software solved.
There are plenty of reports on the web with people having the same problem with Omnia 7 :-(
Sent from my OMNIA7 using Board Express
But my motorola s9 worked fine with NODO.
Can we diagnose somehow that it is hardware issue? I have used following codes in Diagnosis:
*#232331# - BT RF Test Mode
*#232332# - BT Audio
*#232333# - BT Search Test
*#232337# - Bluetooth MAC Address
First one tells me that RF testmode is on, second gives me nothing... Third displays Search Failed!!! message and fourth just same code...
On my omnia
*#232331# - RF Test Mode ON!
*#232332# - Nothing
*#232333# - Search Fail!!!
*#232337# - 0x78471D364188
My bluetooth only works well when I put off the wifi on my Omnia 7
Sent from my OMNIA7 using Board Express
I've tried the codes and I have the same results as you have, sigh.
ikke008 said:
My bluetooth only works well when I put off the wifi on my Omnia 7
Click to expand...
Click to collapse
My bluetooth dont work with wifi.
And without wifi sound is choppy.
When I heard about USB audio in Android 5.x.x, I was really excited, I could finally use my G930 headset with my phone! ...then I tried it and I found out that the volume is ridiculously low. So I thought it was the headset and naturally I decided to try a different one, but as it turns out, the other one was just as quiet. Am I missing something here?
Even trying other players doesn't seem to work, with the exception being USB Audio Player, which I was able to play with the pre-amp and boost the volume to the proper levels, but the equalizer on it is horrible.
Any thoughts on this? Is USB audio even a thing in Android or it's just "there"?
CrisR82 said:
When I heard about USB audio in Android 5.x.x, I was really excited, I could finally use my G930 headset with my phone! ...then I tried it and I found out that the volume is ridiculously low. So I thought it was the headset and naturally I decided to try a different one, but as it turns out, the other one was just as quiet. Am I missing something here?
Even trying other players doesn't seem to work, with the exception being USB Audio Player, which I was able to play with the pre-amp and boost the volume to the proper levels, but the equalizer on it is horrible.
Any thoughts on this? Is USB audio even a thing in Android or it's just "there"?
Click to expand...
Click to collapse
The issue could be a million things since it's new. and since headsets aren't guaranteed support outside of a PC trial and error is your best friend.
Try different ROMs, stock ROM's, stock based, etc. you get the point.
CrisR82 said:
When I heard about USB audio in Android 5.x.x, I was really excited, I could finally use my G930 headset with my phone! ...then I tried it and I found out that the volume is ridiculously low. So I thought it was the headset and naturally I decided to try a different one, but as it turns out, the other one was just as quiet. Am I missing something here?
Even trying other players doesn't seem to work, with the exception being USB Audio Player, which I was able to play with the pre-amp and boost the volume to the proper levels, but the equalizer on it is horrible.
Any thoughts on this? Is USB audio even a thing in Android or it's just "there"?
Click to expand...
Click to collapse
Sounds like the USB mixer is set to a low volume by default.
Are you rooted? If so, you can download a binary called "tinymix" from here to view and modify the mixer.
(tinymix is part of AOSP, but does not ship with Google's Android. It may with custom ROMs.)
Copy the binary to, e.g. /system/xbin, make it executable (744), and run the following command as root in an adb shell, after you connected your USB audio device:
Code:
tinymix -D 1
For example, I have an external DAC (FiiO E18, which works fine on my N5 running stock Android 5.1) and the output is
Code:
Mixer name: 'FiiO USB DAC-E18'
Number of controls: 2
ctl type num name value
0 BOOL 1 PCM Playback Switch On
1 INT 2 PCM Playback Volume 110 110
Knowing this output you can run
Code:
tinymix -D 1 "PCM Playback Volume"
which in my case returns
Code:
PCM Playback Volume: 110 110 (range 0->110)
This means that the playback volume on my device, which can range from 0 to 110, is set to max.
What does tinymix return on your device?
chdloc said:
Sounds like the USB mixer is set to a low volume by default.
Are you rooted? If so, you can download a binary called "tinymix" from here to view and modify the mixer.
(tinymix is part of AOSP, but does not ship with Google's Android. It may with custom ROMs.)
Copy the binary to, e.g. /system/xbin, make it executable (744), and run the following command as root in an adb shell, after you connected your USB audio device:
Code:
tinymix -D 1
For example, I have an external DAC (FiiO E18, which works fine on my N5 running stock Android 5.1) and the output is
Code:
Mixer name: 'FiiO USB DAC-E18'
Number of controls: 2
ctl type num name value
0 BOOL 1 PCM Playback Switch On
1 INT 2 PCM Playback Volume 110 110
Knowing this output you can run
Code:
tinymix -D 1 "PCM Playback Volume"
which in my case returns
Code:
PCM Playback Volume: 110 110 (range 0->110)
This means that the playback volume on my device, which can range from 0 to 110, is set to max.
What does tinymix return on your device?
Click to expand...
Click to collapse
Does that affect USB volume only, or it will affect global audio output?
CrisR82 said:
Does that affect USB volume only, or it will affect global audio output?
Click to expand...
Click to collapse
USB volume only.
Note that modifying the USB audio playback gain via the mixer may not be permanent. You may have to re-adjust the playback gain every time after you have plugged in your USB audio device. If this is the case, an automation app like Tasker can be very useful.
The USB Audio Player seems to have this built-in and works pretty well...wish it's equalizer wasn't lacking even basic presets...
Will give it a go I guess
Hi there!
Most users of the Xperia C3 will know that when using headsets, audio played using audio players will randomly start distorting, stop, then start again.
If you are rooted, this fix is simple. Simply uninstall the app called 'Audio settings', and your audio problems will stop. The down side though, is that you won't be able to adjust the equalizer unless you use a third party enhancement app such as ViPER4Android.
If you are not rooted though, you can use KingRoot.net's mobile client to root your device.
EDIT: It just makes the audio more stable, without distortion. Due to the Qualcomm decoder's bugs, the audio still stops after some time for around 15 seconds. (tunnel.decode = false or tunnel.audio.decode = false doesn't work)
My C3 hasn't had any problem with songs, my model is the D5233 though.
Hi,
Recently I have a peculiar problem , I can't hear any sound during call whether its mic or loud speaker or even headphones i could't hear any sound from the phone. I've tried music with loud speaker and even in head phones still the same issue. I've tried to change a ring tone in settings->sound that too i couldn't hear sound.
I have tried in different ROM too and clean flashed multiple times and no luck with that.
When i open a video file or camera app my mobile reboots every time i tried the result is same. I've gone through some of the logs and found some lines but i couldn't understand
sample logs are
1. adev_set_parameters: ERROR: set param called even when stream out is null
2. AUDIO_OUTPUT_FLAG_FAST denied by client due to mismatching sample rate (48000 vs 44100)
3. LPAPlayer::Clip duration setting of less than 30sec not supported, defaulting to 60sec
4. Could not offload audio decode, try pcm offload (16-bit)
My Current ROM: PAC-pico-KTU84Q-UNOFFICIAL-BUILD_3
Recovery: TWRP 2.8.7.0 Recovery
note: Attached the log cat from my mobile.(hint: search from "05-17 19:17:27.560")
If Someone has a solution or faced this kind of issue and solved plz help me :crying: on this i love my little beast.