UPDATE:
so I went through root explorer side by side with my droid and my brothers droid2
in /system/etc/bluetooth/audio.conf there are differences, the bottom lines of the droid are as followed
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
when I looked at the audio.conf of the droid 2 it had differences here...
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=1
[AVRCP]
InputDeviceName=AVRCP
MetaDataSupport=1
ControllerSupport=1
also there was a bluetoothDUN.apk file on the droid2 . I saved his audio.conf and the apk and put them on my sdcard, swapped out the audio.conf file and rebooted, connected and paired bluetooth then played music and used superbtmonofroyo with no luck. I went back to my sd card and installed the bluetoothDUN apk and rebooted connected bluetooth again and still was unable to listen to music (actually this time an error popped up saying bluetoothdun not working properly force close, so I uninstalled the btdunl.apk)....are the .conf files connected to permissions somewhere that I am missing ? does anybody know?
orig.
I have a droid1 and Im running Charity Rom before that I just had stock 2.2.1 rooted. both are unable to stream audio through a mono bluetooth , but when I tried using Super BT mono froyo on my brothers droid 2 it works perfect.
when I flashed the charity rom I noticed that I had lost the ability to rotate my google maps in the new 3d view mode with multitouch and there was a simple permissions fix here http://forum.xda-developers.com/showthread.php?t=880445
Is it possible the answer to this bluetooth bug might be a permissions or config issue?
Hi there since yesterday I have a Problem with my HTC Topaz. While calling I can't hear the other side. The phone did NOT crashed, got NO Impact or Shock! I tried to reboot, then I flashed 5 different ROMs and tried 2 Stock ROMs 6.5 and 6.1, I changed 3x the radio (4.49.25.91, 3.43.25.19, 4.49.25.17) without any progres.
Otherwise the phone works correctly.
The phone speaker works correctly - music plays, the phone is ringing...
I can make calls using headset without any problem...
I still think it is not a HW problem (speaker and headset works), but have no other Idea how to fix it.
Any Idea / Suggestion before I send the damn phone to service or buy (most likely) new one?
EDIT 1: Just tried to replace the mainboard (got second - broken - Touch Diamonda 2) Board functionality 100%, but still the same error - no sound while calling.
EDIT 2: Problem solved: It was HW problem! After replacing the speaker, the phone works good again. What I do not understand is, why the phone made sounds, played music and malfunctioned only during calls. Nevertheless, problem solved. I found this disassemlby guide very helpfull: http://translate.google.co.uk/translate?u=http%3A%2F%2Fwww.pdacenter.ru%2Frazborka%2Fhtc-touch-diamond2%2F&sl=ru&tl=en&hl=en&ie=UTF-8
EDIT 3: Photo attached
Regards Martin
I've recently acquired a new car which has a built in stereo system (Renault Megane Estate 2012 Bose edition) which is able to receive CBR encoded A2DP streams. It works well, connects, music plays, even controls work.
Awesome!
Using catlog I can see that the bitpool that is negotiated is 51. While the sound isn't horrible, I believe the handsets (Samsung Galaxy SIII Int. and Nexus 7, both running CM10 nightly) are able to encode and transmit at a higher bitrate/bitpool then currently is set.
I've tried my best effort in changing this settings. I've built my own Ubuntu kitchen, followed all the guides and have from the looks of it compiled a successful ROM image. Sadly enough when I flash it, my tablet dies (black screen) and even CWM is destroyed. Using fastbood and USB I've been able to recover the tablet, so no problem there, but still, no working ROM. Even without changing something. But that is not what this thread is for, I'll figure that out eventually.
I am trying to recreate the results that are in the following topic : http://forum.xda-developers.com/showthread.php?t=1880298
Sadly, the files provided are not compatible with my CM10 devices and changing the source and then compiling it and replacing the files yields no result. Whatever I try, it stays at 51 (The bitpool it SENDS to the radio as max). There are several files which are connected to the settings, such as cbr.c , audio.a2dp.default.so, etc. but I don't really know what to change to get the desired results.
If anyone is able to help, that would be greatly appreciated. Point me to the right file where I can find the values to change, either in a compiled ROM or in the source so that I can compile it and change the files in
my running ROM using rootexplorer. Whatever works.
I would like to try settings as high as 125. But ideally, I would like to experiment what my headunit accepts, what it can be forced to, and thus finding the highest quality possible using my combination of equipment.
In this the Nexus 7 is the most important because that will be permanently located in the car.
update--
I have found a thread on bluez surrounding this topic.
http://www.spinics.net/lists/linux-bluetooth/msg23091.html
Could someone more knowledgeable then me please take a look at this for me and maybe change the file? Sadly that goes way beyond my programming knowledge, but I would really love to give it a try!
update--
Some extra information and a good explanation as to why I am looking for this (and maybe more people with me).
Bitpool values as high as 128 are possible on Windows Mobile devices (including mine), which means they are possible in A2DP. Such a high value is necessary for some genres of current music, which are highly
compressed (the problem was once discussed in one of Xiph Foundation's articles). SBC is unable to encode such material properly if it doesn't have enough bandwidth.
Click to expand...
Click to collapse
I've done some more tests editing and replacing files and I think I've actually gotten it to sync higher but it still displays it's at 51. The sound just sounds a lot better, but of course, that can always be a placebo effect. :silly:
So, anyone have any insight, or who can point me into the right direction of what needs to be changed and where? As said, I think I have reached the quality increase (bitpool 100) but the logs still display 51.... not quite there yet. And in light of people using the Nexus 7 in a cars a lot (which I also intend) and the borked headphones output I read everywhere, CD quality streaming over A2DP (It's possible) would be awesome!
Kitchen fixed
So I got my kitchen working and am cooking working ROM's.
Just getting the right files changed is giving me some problems.
I think I fixed most of it, but for some reason when I check the logs it still states that it's sending a max bitpool of 51. I believe in the background it's using the 128 as I stated in the source files, but still. I would like the logs to show the same, just to acknowledge I'm a not having a placebo effect.
The files I have changed are the following:
/android/system/external/bluetooth/bluez
a2dp.c
gsta2dpsink.c
gstscenc.c
liba2dp.c
pcm_bluetooth.c
I used the patch listed above on the pcm_bluetooth.c. And I do believe it overrides the settings and it's not set to 51 anymore but the 128 I put in all the files manually. Music sounds great, but it's hard to subjectively test.
Hopefully we can find some people who have a greater understanding of bluez.
Little kick
Little kick to see if someone wants to assist me on this or not. I think it could potentially benefit a lot of people making Bluetooth audio/A2DP go from barely adequate to High Fidelity!
I'd love to help you test this - I also find the A2DP quality to be lacking in a lot of more "active" or compressed music. Acoustic and softer music sounds great, but rock/metal tends to sound like a 128kbps mp3. It actually seems to sound better from my Galaxy Nexus than the 7 as well. I'm running a Bugless Beast ROM now but was running CM10.
Also, not sure if you've seen this but I found an article (soundexpert.org/news/-/blogs/bluetooth-audio-quality-a2dp, sorry can't post links yet) that shows the bitrate per bitpool value. At a bitpool value of 53, the bitrate is around 320kbps. A2DP itself supports a bitrate of up to 512kbps for stereo, but through other optionally-supported codecs. SBC however, in this profile, only seems to go to ~320. It might be worth checking out if your car stereo supports mp3 over A2DP - there is an option in /etc/bluetooth/audio.conf to set MPEG12Sources from 0 to 1 and SBCSources from 1 to 0.
ROM up for download
Hi there, thnx's for joining the cause.
I compiled a new daily today with settings set to bitpool 128. But I don't really hear much change, maybe the setting is too high, maybe something else is going wrong. As stated above, in the logs I can only see it sending 51 as max pool to the device and setteling with it. But since I'm using an edit pcm_bluetooth.c it should override that setting, say it's going to do 51 and then stream and the values I defined in the files.
.....in theory at least...... the only subjective evidence I have for this are my own ears.
So, I will provide you with access to the 128 version and am going to compile a 64 version while I'm at it.
Use an FTP client to connect to:
host: oss.quindorian.org
user: XDA
pass: ROMROM
Anyone is welcome to give it a try. I have put limits on the FTP site, so please beware of that. But I'll put ROM's there you can try and report back on. Tell me if you think it does nothing or if you think it makes it sound like a singing angel. Any feedback is appreciated.
As source I use the CM10 repository so I am basically building modded nightly builds. Today it allready has the 4.1.2 flavor with the newest drivers and everything included. Don't forget to flash gapps if you need them.
Understand
ChrisK15 said:
Also, not sure if you've seen this but I found an article (soundexpert.org/news/-/blogs/bluetooth-audio-quality-a2dp, sorry can't post links yet) that shows the bitrate per bitpool value. At a bitpool value of 53, the bitrate is around 320kbps. A2DP itself supports a bitrate of up to 512kbps for stereo, but through other optionally-supported codecs. SBC however, in this profile, only seems to go to ~320. It might be worth checking out if your car stereo supports mp3 over A2DP - there is an option in /etc/bluetooth/audio.conf to set MPEG12Sources from 0 to 1 and SBCSources from 1 to 0.
Click to expand...
Click to collapse
Yeah, I understand what that article says. But for me, the quality just isn't up to par to listening to a 320Kbit stream. Also, there is what A2DP officialy supports and there is what works. I'm shooting for the last type. If I can get a 1000Kbit stream between my device and my headunit, I will, even if it doens't add much above say 786Kbit, more is always better in this case. If it works that is, ofcourse.
Because I wish to use spotify, I believe my only choice is to use the SBC encoder. Spotify will never let you transfer it's source file to anywhere because of DRM. Alternativly, if we could enable an AAC stream or something (also supported I believe) we'd need less bitrate/bitpool for better quality! And from what I have read, the SBC encoder standard used it just quite crappy. So while a 320Kbit LAME encoded MP3 might sound great/perfect, using a sub-standard encoder can still give it artifacts and low quality. Thus the hunt for insane amounts of bitrate!
Awesome, I'll definitely give it a shot. If it's possible to exceed the Bluetooth standard spec then that'd be awesome. I'm more worried about our receivers not being able to support the higher bandwidth - my head unit is new but only supports SBC unfortunately.
Cool
ChrisK15 said:
Awesome, I'll definitely give it a shot. If it's possible to exceed the Bluetooth standard spec then that'd be awesome. I'm more worried about our receivers not being able to support the higher bandwidth - my head unit is new but only supports SBC unfortunately.
Click to expand...
Click to collapse
Cool, I just put the bitpool64 version there too. Tested it and I notice no real difference. Sadly the quality is still not great, it's not horrible.... but certainly not great so I still feel like my settings are maybe not having any effect whatsoever. As reflected by the logs using catlog. It sen bitpool 51 max and settles for that. For all the values I have changed in the files and that stay the same, I really do not understand. Wish I could fix that, but with my knowledge I have just run out of places where to look.
Let me know if in your case it makes any difference!
I just tried it out and to me it seems like there's an improvement. I normally stream Pandora One in my car, and that definitely seemed like it had more clarity. However Google Music streaming sounded the same, although it was already good to begin with. I would think that compressing more highly-compressed music from the start (Pandora) would have a worse effect on quality than less-compressed music, which seems to be the case. Or maybe I'm just hearing things
Thanks for looking into this, I've been trying to find a way to do this for a while!
Quindor said:
Hi there, thnx's for joining the cause.
I compiled a new daily today with settings set to bitpool 128. But I don't really hear much change, maybe the setting is too high, maybe something else is going wrong. As stated above, in the logs I can only see it sending 51 as max pool to the device and setteling with it. But since I'm using an edit pcm_bluetooth.c it should override that setting, say it's going to do 51 and then stream and the values I defined in the files.
.....in theory at least...... the only subjective evidence I have for this are my own ears.
(...) .
Click to expand...
Click to collapse
perhaps you can test if the patch does anything - by setting bitpool to some very LOW value ?
ChrisK15 said:
It might be worth checking out if your car stereo supports mp3 over A2DP - there is an option in /etc/bluetooth/audio.conf to set MPEG12Sources from 0 to 1 and SBCSources from 1 to 0.
Click to expand...
Click to collapse
On my CM12.1 official nightly ROM (2015/12/03) for my Samsung i9505, there is no file audio.conf
Does that mean I can simply create it with the two lines
MPEG12Sources=1
SBCSources=0
in order to test wether a bluetooth SNK device such as a car stereo or a headset supports mp3 over A2DP?
So does anyone have some actual logs or HCI captures showing bitpool above 53?
..
Hello everyone!
Not sure if it's been posted before, but there's a relatively big batch of Lumia 930 devices that have microphones that short circuit after a while. It's heavily discussed in this topic on Windows Central and I'm also a victim of it.
What happens is that 2 of the 4 mics (mostly at the back) on the 930 suddenly don't work anymore. Therefor the device can't record any sound while filming in Windows Camera (W10M), Whatsapp, Voice recorder, etc. Those apps use only the two back microphones. The front microphones are disabled or are used to cancel noise by default. When calling, the bottom front (still working) microphone is used.
Is there a hack that could make it possible to use the other (front) microphones on the phone to record sound while filming? Like a "use all microphones" hack? Or maybe a tweak to disable noise cancellation?
I checked in several forum if there is any solution to the problem , but almost all ask to take the appliance to a technical assistance .
My phone is no longer under warranty , the repair value is too expensive (better buy a new one)
But I'm thinking about changing the microphone , I saw that there are websites selling like this user ( brittech14) on Ebay.
Anyone know if replacing the microphone solves the problem ?
Also looking for an answer to this problem if it is either possible to disable mic 3&4, force apps to use mic 1&2 instead of 3&4 or a way to fix this by disassembly.
Would really appreciate if someone knows more about fixing this issue.
Hi,
The only way to solve mics problem is replacing them. Changing the mics functionality through software hacking is impossible. Since, the Lumia 930 has two product code, RM-1087 and RM-1045 (the latter is popular), as a small chance (but risky) you can try the firmware of RM-1087 on your device (Download Links).
Having the same issue with a phone that is out of warranty, curious if there is any solution, registry edit, tweak, etc. to remap 3rd and 4th mics to the working 1 and 2...
Fortunately, some of HW issues such as mic problem are supposed to be fixed in future w10m updates, probably RS2.
does not solve problem, just replaced the microphone still does not work
My Xperia XZ1 Compact has a strange problem: Both of my BT devices (Jabra Evolve 65, Denon Envaya Mini) work well with my phone if I answer phone calls. But playing audio files does not work. I tried two audio players (Mort Player and the lineageos music app) and played a MP3 file from Youtube. On another phone both devices play music perfectly. So it is obvious that my devices are not the problem. It is definitively the phone.
In the bluetooth settings of both devices, media is on. I also tried to deactivate phone call in the settings but it did not help.
I tried to change the protocol version to 1.4, I deleted the bluetooth cache and resetted the bluetooth settings.
Please have a look at my Logcat attached. What I basically did while it ran is: Click the volume button, select the bluetooth symbol and changed from one device to the other.
I can't tell you which firmware I have. I did not find any information about it.
It seems like in 18.1 this has been fixed. But is there a quick way fixing the problem without upgrading to 18.1/2.0? Perhaps by changing a few values somewhere?