Hi
Any ideas on how to adjust the a2dp bitpool settings. I am coming from windows mobile where this was easy to do in the registry. The stock bitpool seems to be 32 as per the logcat readout below. This is coming from an Evo 4G:
W/BTLD ( 1677): ### :: codec open ::
W/BTLD ( 1677): ### mtu 512, 660 bytes/frame, bitrate 229, nbr ch 0, freq 240
W/BTLD ( 1677): ### alloc : 3, blk len 240, chmode:15, bitpool 32:2, subbands 12
the sound is ok but could be better.
Another interesting part of the logcat is:
V/A2dpAudioInterface( 136): setParameters() bt_headset_name=DRC-BT15;bt_headset_nrec=on
E/AudioHardwareQSD( 136): setParameters() bt_headset_name=DRC-BT15;bt_headset_nrec=on
I/AudioHardwareQSD( 136): Using default acoustic parameters (DRC-BT15 not in acoustic database)
(I wonder what the acoustic database is.)
Any suggestions would be welcome. I did search around and found nothing easily implemented. Also nothing on the market.
Thanks
I want to know the exact same thing and not ready to accept that WinMo is superior to Android in any way...
I just found this page here which discuss some terminal and backend files in OSX for modifying these settings. Is there any similar file or terminal command we can do on our own unix based systems?
I have spent the last couple of weeks working on this and have come up with nothing. But I am not a programmer. Hope someone knows where to make the changes.
any update on this?
I am no programmer in any way, but I would realy like to know the outcome of this thread because it's been bugging me since I bought my Desire. I realy can't stand the loss of sound quality when listening to music on a bluetooth headset with my sennheiser headphones(HD215) connected.
I was wondering about the same thing. I used to tweak my WinMo Bitpool and samplerate. Any way to do this on Android?
I have been following this too. There must be a way to edit this somehow!! The a2dp quality of the evo/desire is awful! Must find a way!!!
I'm also disappointed in the audio quality on my Desire. I use my phone to listen to music in my car or mobile speaker via bt. But there are many tracks with high frequencies (or frequencies in some range), that causes some really disturbing clicking noise! Which I don't had on my Nokia N82 and SE K800i.
This really annoys me, and I consider to change to a different phone if there will not be a solution I'm currently using the original HTC firmware/radio, because I haven't rooted my phone yet. Is it possible that flashing a different radio will help?
I'm not sure if this is caused by the bitpool setting.
I will try to capture/upload some fragment with this clicking...
Edit: The microphone isn't good enough to record the clicking, but this fragment illustrates it very well (the clicking was actually in the track itself, but it sounds almost the same):
fragment (mp3)
Has there been any kind of an update on this one? A fix or a setting that could be changed?
I'm thinking of buying a Desire Z, but I will certainly stick to my ancient Touch Pro if the A2DP quality on Android is as bad as you all say. Bitpool of 32 is unlistenable, and I can't believe that neither Google nor HTC care about it.
Now that Cyanogen has fixed this in their ROM, I don't understand why no one has released a method for people not running Cyanogen.
So it has been fixed? What bitpool does that ROM run? I can't seem to find any info :S
And will they make a ROM for Vision with that fix?
I know I've got stupid noobish questions, but I'm completely new to the whole Android story and I haven't used these forums for ages so I'm quite lost atm...
CM6 is running 53
Thanks for the info
I'm having issues with an epic I just got (luckily in the 30 day return period). The a2dp audio sounds like garbage. The a2dp audio on my touch pro stock (before tweaked) was much better.
This could be a dealbreaker for me.
naorion said:
Now that Cyanogen has fixed this in their ROM, I don't understand why no one has released a method for people not running Cyanogen.
Click to expand...
Click to collapse
This is good news, but surely Mr.Cyanogen can pass on his method to Cotulla or one of the other primary Android Devs.... Hmm!
Any news on this? I flashed to Cyanogen 6.1. A2DP sounds much better. I now have mulitple exchange accounts working. The few issues are the Expensify receipt image capture does not work, 4G and HDMI also (know issues). I hope someone can find a fix for this.
I had a look at the bluez source code posted on HTC's developer site and I believe this is where the bitpool value is being set:
Code:
supersonic_bt.zip/external/bluetooth/bluez/liba2dp.c:
static uint8_t default_bitpool(uint8_t freq, uint8_t mode)
...
case BT_SBC_SAMPLING_FREQ_44100:
switch (mode) {
case BT_A2DP_CHANNEL_MODE_MONO:
case BT_A2DP_CHANNEL_MODE_DUAL_CHANNEL:
return 31;
case BT_A2DP_CHANNEL_MODE_STEREO:
case BT_A2DP_CHANNEL_MODE_JOINT_STEREO:
return 53;
default:
ERR("Invalid channel mode %u", mode);
return 53;
}
Changing the "return 31;" to "return 53;" and recompiling -or- hex editing the binary liba2dp.so on the phone ought to do the trick.
The same code block also appears in ipctest.c, pcm_bluetooth.c, sink.c, and source.c, so one or more of those files may also need to be modified.
I just got my Evo and I don't know enough about it yet to try this myself, but if someone else is able to then I think we'd all appreciate it if you could give it a shot. (Not all of us are interested in running a custom ROM just to fix this one problem.)
Edit: Another way may be to just force your desired min and max bitpool settings in the function bluetooth_a2dp_init():
Code:
cap->min_bitpool = min_bitpool;
cap->max_bitpool = max_bitpool;
Disregard that last post of mine. I had another look at liba2dp.c as well as some D/A2DP log output. All of the log output I could find posted online contains "channel_mode: JOINT STEREO", which according to default_bitpool() means the "default" bitpool should be 53. I originally thought the problem might be the bitpool setting of 31 referenced in that function, but I could not find any log output that contained "channel_mode: DUAL CHANNEL". (It shouldn't be too hard to verify this.)
So why is a lower bitpool value used? Look at this code snippet from bluetooth_a2dp_init():
Code:
min_bitpool = MAX(MIN_BITPOOL, cap->min_bitpool);
max_bitpool = MIN(default_bitpool(cap->frequency,
cap->channel_mode),
cap->max_bitpool);
cap->min_bitpool = min_bitpool;
cap->max_bitpool = max_bitpool;
The max_bitpool value is set to the lower of 1) the "default" bitpool and 2) the max bitpool reported by the audio sink (ie. your headset). If your headset reports a max bitpool of 32, then that is what will be used since it is less than 53. My understanding of the bluetooth spec is that audio sinks are supposed to accept bitpool values higher than 32 in order to support up to 512 Kb/s audio. Lower bitpool settings are more reliable, though, so perhaps that is why many headsets are configured to report artificially low values.
The actual bitpool value used is simply max_bitpool. See bluetooth_a2dp_setup():
Code:
data->sbc.bitpool = active_capabilities.max_bitpool;
The a2dp code isn't set up to take bitpool parameters from a configuration file, so liba2dp.c will need to be modified and recompiled. Possible quick fixes would be to change the "max_bitpool = MIN(" line to "max_bitpool = MAX(" or to manually set your desired bitpool value (ie. "data->sbc.bitpool = 53").
Hi,
I just want to say that since unfortunately my programming capabilities are close to non-existent I'm afraid I'm not able to provide much actual help in solving this issue but i highly appreciate that there are people who are looking into this and trying to remedy what Android OS designers and phone manufacturers neglected. I've been using A2DP headsets for the past 3-4 years with Nokia E51 and E52 phones which provided very good sound quality virtually indistinguishable from a cable connection and now after buying a Samsung Galaxy S phone I'm terribly disappointed at its A2DP performance comparable to 112kbps MP3s with even the highest quality sources.
I own three different A2DP headsets manufactured by Sony Ericsson, Nokia and unnamed Chinese labourers respectively and a set of quality IEM earphones plugged into quite good and relatively trained ears. Since A2DP support on both Nokias and a Samsung Blackjack I owned shortly (and let go of just because of its pitiful A2DP performance) has not always been perfect I know a thing or two about how A2DP works and performs. So if there is anything I can do to help regarding testing, preparing and submitting logs etc. just let me know and I will be very happy to help if that's what is needed.
Thanks!
Petr
Related
I need to lower the microphone gain.
My audio codec is clipping becouse of incoming PCM samples saturated from
the mic. I don't need AGC becouse it doesn't work well with my app.
I just need to manipulate the mic gain via software.
Is there a way to do it? I'm using waveform audio api ti capture voice.
Actually the gain is too loud !!!
Thanks.
Anyone knows?
OK, I don't have the answer. But since no one is responding I'll try to give a few ideas that might help.
First, I have a hp6315 and an apache. Under settings, they both have a utility to enable/disable AGC. The ipaq's utility is labeled "ipaq audio" if you disable agc, you can then configure the microphone gain. This gain is stored in the registry. I think searching for gain or audio will find it. The apache doesn't have this. searching for audio, gain, wav, volume in the apache registry doesn't find anything that looks like microphone gain. I guess this is a "value added" thing from hp. But you could try searching anyway.
Then there's the mixer API. This is the way that user level apps are meant to control the audio. Works great on the desktop. Use mixerGetNumDevs() to find out how many devices you can control. On the h6315 mixerGetNumDevs returns 0. I haven't tried the apache, but I can remember a few years ago reading that many (most?) devices return 0. Oh well, hopefully you'll have better luck. However, there are two mixers that are implemented on the pocketPC the question is how to access them.
see this link for info on the mixers
http://blogs.msdn.com/medmedia/archive/2007/01/12/what-do-you-mean-by-mixer.aspx
Here's a link that shows the relationship between the mixer api and the other mixers, wavedev2 mixer, and software mixer.
http://msdn2.microsoft.com/en-us/library/ms923709.aspx
You'll notice that the the mixer api interacts with the mixer in the device driver not the software mixer in the WaveAPI.dll. You'll so notice that this section on audio drivers has pages for MDD/PDD drivers and Unified Audio Model (UAM) drivers. Platform Builder for WinCE 5.0 comes with a sample for each of these model drivers. Both models handle WAV_IOControl Messages. There are two types of messages, IOCTL_MIX_MESSAGE for the mixer, and IOCTL_WAV_MESSAGE for the rest of the driver. It looks like these IOCTL_MIX_MESSAGE are the way the mixer API controls the mixer. In the MDD/PPD sample they can be used to set WPDMX_MIC_VOL and WPDMX_LINEIN_VOL. In the UAM driver it's AC97_MIC_VOL and AC97_LINEIN_VOL. Perhaps sending the right IOCTL will solve the problem.
This blog entry
http://blogs.msdn.com/medmedia/archive/2007/01/03/windows-ce-audio-driver-samples.aspx
seems to say that a wavedev2 sample is available now. Also, while the WinCE 5.0 page above only metions two models the corresponding wince 6.0 also talks about wavedev2. I suspect if you got the current version of platform builder for WinCE 6.0 (trial version is free) you would have get the sample code for wavedev2, which is likely to be the best documentation of how this works. Amazingly, the drivers aren't that hard to read.
Both of the functions waveInMessage() and waveInSetProperty() are available to user apps. Hopefully both should be able to change the microphone gain if you can set the parameters properly. While most of these things are about windows CE, I think most (or all) apply to windows mobile 5.
Windows mobile 5, likely uses wavedev2 devices not MDD/PDD or UAM drivers.
Another interesting page about wavedev2 audio is here:
http://blogs.msdn.com/medmedia/archive/2007/01/04/the-wavedev2-gainclass-implementation.aspx
If your able to succeed or even learn more, be sure to post it back here.
I said a lot so I probably got something wrong. Anyone, please feel free to correct anything.
mixerGetNumDevs() returns 0 on my device
I can't find any registry entry which suggests microphone gain manipulation.
Perhaps i just need to send a waveInMessage properly.
I'm getting confused, should i implement a driver for this?
How do i know what kind of driver is running on my device and what messages
does it accept?
Thanks.
i think this may be what you need(?)
use a registry editor, (phm do a good free one)
hkey_local_machine/software/htc/audiogain (and audiogain 0 and 1 and 2)
try playing with the settings in there, soft reset to take effect
I don't have that keys on my HTC, should i create it?
Do you mean audiogain0 audiogain1 audiogain2?
Thanks.
see the attached screenshot, if you don't have those settings to adjust, a similar/same question was asked last night in a other thread, with different answers here
http://forum.xda-developers.com/showthread.php?t=306655
Looks like the cab file from the link provided by bbobeckyj just sets those audiogain registry settings. I don't have those settings on my apache. I don't think adding will help, but "you never know".
If you want to use waveInMessage() or waveInSetProperty() search for them at microsoft. You'll find there are a few parameters that you don't know. Read though the sample drivers that you can get with platform builder. See what values they expect, and which one cause them to change the microphone level. Try calling the function with values from the sample driver. While there is no guarantee that they use the same values, it's like that they do. I would start with the wavedev sample.
I don't know why microsoft doesn't seem to allow access to the source without agreeing to download all of platform builder, but it looks like that's the only way to get it. You can download the trial version for free. The source often helps if your trying to fingure out how something really works.
Uhmmm, i havn't found any download link about platform builder for windows CE 6.0. I've only found the 5.0.
Should't the trial be free?
Thanks.
I need to fix audio gain in my Itel Experience Phone (Windows Mobile 6.0 Pro)?
Please help.
I need to mute mic while on a call. Anyone has a idea of how may i do it?
Thanks
moved to the right forum, please post in the correct forums.
We wouldn't have an obscene amount of the same Bluetooth questions if a few things were made clear.
Bluetooth is a radio protocol.
"Bluetooth" is useless to us end-users without "Bluetooth Profiles". Details on these profiles can be found here.
A2DP/AVRCP (Advanced Audio Distribution/Audio Video Remote Control) is what is, and has been working for many HERO ROMs for quite some time. This profile allows for high-quality, stereo audio (not exclusively though) to be sent 1-way.
HSP/HFP (Headset/Handsfree) has not and to my knowledge, still does not work is many/most HERO/Sense ROMs. These profile allow for voice communication, enhanced dialing, and caller ID functionality.
If Devs/Mods clearly stated something like the following, and kept their #1 post updated, then even the forum noobs shouldn't need to keep asking the same questions over and over again.
Version X.X.X - Bluetooth A2DP [IS/IS NOT] working. Bluetooth HSP [IS/IS NOT] working.
This is already done for GPS and WiFi so why should Bluetooth be any different? I don't mean to sound demanding of the Devs/Mods/Ops, but EVERYONE has to wade through the extra posts, and it would help everyone know better what a ROM does/doesn't have to offer so why not do it?
P.S. If someone knows of a HERO/Sense ROM with all the above working for a 32B MT3G, I'd love to hear about it.
Thanks for the info!
I'm pretty worthless for the most part so I try to help when I see a chance
rainabba said:
We wouldn't have an obscene amount of the same Bluetooth questions if a few things were made clear.
Bluetooth is a radio protocol.
"Bluetooth" is useless to us end-users without "Bluetooth Profiles". Details on these profiles can be found here.
A2DP/AVRCP (Advanced Audio Distribution/Audio Video Remote Control) is what is, and has been working for many HERO ROMs for quite some time. This profile allows for high-quality, stereo audio (not exclusively though) to be sent 1-way.
HSP/HFP (Headset/Handsfree) has not and to my knowledge, still does not work is many/most HERO/Sense ROMs. These profile allow for voice communication, enhanced dialing, and caller ID functionality.
If Devs/Mods clearly stated something like the following, and kept their #1 post updated, then even the forum noobs shouldn't need to keep asking the same questions over and over again.
Version X.X.X - Bluetooth A2DP [IS/IS NOT] working. Bluetooth HSP [IS/IS NOT] working.
This is already done for GPS and WiFi so why should Bluetooth be any different? I don't mean to sound demanding of the Devs/Mods/Ops, but EVERYONE has to wade through the extra posts, and it would help everyone know better what a ROM does/doesn't have to offer so why not do it?
P.S. If someone knows of a HERO/Sense ROM with all the above working for a 32B MT3G, I'd love to hear about it.
Click to expand...
Click to collapse
Although I agree, isn't it rather a question of the kernel? IMO Case_ did an excellent job outlining the problem in his comment on his ROM. At least for a noob as me it became much clearer.
You forgot to explain Bluetooth OBEX and FTP
android 2.0 has support for OPP (Object Push Profile) it seems.
feicher said:
Although I agree, isn't it rather a question of the kernel?
Click to expand...
Click to collapse
I think it's a combination of both.
And big thanks to rainabba for the clarification, I've been kinda lost in the bluetooth terminology myself, having not used BT pretty much at all.
I've been trolling the threads looking for info on support for Bluetooth SAP (Sim Access Profile) so that I can get full functionality with my car.
I haven't found anything as yet but would like to be proven wrong.
Anyone hear or read anything on this profile with Android?
I have a HTC Trophy, coming from a HTC Touch Pro 2. The speaker phone was awsome on the TP2 and on the trophy, if there is small noises in the room (even a low computer fan) with the phone on mute, you can bearly hear the people on the phone. It's so low that with any low background noise, it's hard to hear.
Is it possable to increase the volume on the speaker phone on WP7 higher than 10 (maybe up to 15 or so) ???
Thanks !
TP2 has the best spekaer phone ever! It is highly unlikely that Trophy (or any other, I have HTC 7 Pro and spekaer phone is not as good as TP2) can reach it, maby by changing rege, but it can only harm the speaker since it will be overloaded.
I, too, miss TP2 speaker phone and talking in the car without jelling...
DavidinCT said:
I have a HTC Trophy, coming from a HTC Touch Pro 2. The speaker phone was awsome on the TP2 and on the trophy, if there is small noises in the room (even a low computer fan) with the phone on mute, you can bearly hear the people on the phone. It's so low that with any low background noise, it's hard to hear.
Is it possable to increase the volume on the speaker phone on WP7 higher than 10 (maybe up to 15 or so) ???
Thanks !
Click to expand...
Click to collapse
There is a registry edit to increase the # of increments, but it doesn't increase volue at all. It just adds more "steps". Haven't found anyway to increase the volume. It seems to be a driver issue on all HTC devices. HTC needs to get their act together & issue a patch to fix this. It's almost impossible to hear music/videos/movies. Any background noise & you can't hear ****.
I think I just fixed this. I saw a registry edit for WM 6 & it the directory still exists.
HKCU\ControlPanel\SoundCategories\
In each of it's sub directories, change the InitVol value to 100. I notice some were 100 already while others were 85 or even 65. I think this means 100% volume/85% volume/65% volume. Change them all to one value & you'll equalize the volume across the board.
drkfngthdragnlrd said:
I think I just fixed this. I saw a registry edit for WM 6 & it the directory still exists.
HKCU\ControlPanel\SoundCategories\
In each of it's sub directories, change the InitVol value to 100. I notice some were 100 already while others were 85 or even 65. I think this means 100% volume/85% volume/65% volume. Change them all to one value & you'll equalize the volume across the board.
Click to expand...
Click to collapse
Doesn't this just, like you said, increse the step but, not give a higher volume ?
SHould I be opening a ticket with HTC about this ?
DavidinCT said:
Doesn't this just, like you said, increse the step but, not give a higher volume ?
SHould I be opening a ticket with HTC about this ?
Click to expand...
Click to collapse
No, this is different. I just found it. The registry value I was talking about before is;
HKCU\ControlPanel\Volume\
MaxInCallUIVolume & MaxSystemUIVolume
I just did this new edit I just found (this one in the above post) & now I can hear youtube videos over my pc with tv playing on it lol.
thanks, I just gota figure out how to edit the registry with mango and I'll give it a shot.
drkfngthdragnlrd said:
No, this is different. I just found it. The registry value I was talking about before is;
HKCU\ControlPanel\Volume\
MaxInCallUIVolume & MaxSystemUIVolume
I just did this new edit I just found (this one in the above post) & now I can hear youtube videos over my pc with tv playing on it lol.
Click to expand...
Click to collapse
LG quantum here:
this is what it reads (dword)
HKCU\ControlPanel\Volume\
MaxInCallUIVolume = 10
MaxSystemUIVolume = 30
you set yours to 100?
also, I am not sure from your two posts, which one was necessary to get your volume up to max - entries from both posts?
with MFG I am not able to see the subcategories you mention in the post before under "SoundCategories". So I would have to query "blind" keys. too many to type them here?
thanks
derausgewanderte said:
LG quantum here:
this is what it reads (dword)
HKCU\ControlPanel\Volume\
MaxInCallUIVolume = 10
MaxSystemUIVolume = 30
you set yours to 100?
also, I am not sure from your two posts, which one was necessary to get your volume up to max - entries from both posts?
with MFG I am not able to see the subcategories you mention in the post before under "SoundCategories". too many to type them here?
thanks
Click to expand...
Click to collapse
No, that is the "steps". It just adjust how many increments you have. It's the other post.
HKCU\ControlPanel\SoundCategories\
In each of it's sub directories,
InitVol = 100
You can adjust the volume done for those who complain about the volume being too loud by entering a lower value.
drkfngthdragnlrd said:
No, that is the "steps". It just adjust how many increments you have. It's the other post.
HKCU\ControlPanel\SoundCategories\
In each of it's sub directories,
InitVol = 100
You can adjust the volume done for those who complain about the volume being too loud by entering a lower value.
Click to expand...
Click to collapse
thanks, problem with the MFG registry editor is that it does not show the sub directories. One would have to enter them before they can be edited, therefore one would need to already know the names of the sub categories.
thanks again
derausgewanderte said:
thanks, problem with the MFG registry editor is that it does not show the sub directories. One would have to enter them before they can be edited, therefore one would need to already know the names of the sub categories.
thanks again
Click to expand...
Click to collapse
Alarm\
DTMF\
InCall\
InCall2\
Notification\
Reminder\
Ring\
RingPreview\
System\
SystemNotification\
SystemVibrate\
drkfngthdragnlrd said:
Alarm\
DTMF\
InCall\
InCall2\
Notification\
Reminder\
Ring\
RingPreview\
System\
SystemNotification\
SystemVibrate\
Click to expand...
Click to collapse
terrific and thank you
what is DTMF? default on the LG is 65
(System = 85, SystemNotification = 85, SystemVibrate = 85, the rest is on 100)
derausgewanderte said:
what is DTMF? default on the LG is 65
(System = 85, SystemNotification = 85, SystemVibrate = 85, the rest is on 100)
Click to expand...
Click to collapse
I have no clue what DTMF is. I believe the value stands for % of max volume. I set them all to 100. Now I may just be hearing things, but it sure sounds louder to me. I had the TV playing on my PC & the YouTube video on my HD7 droned out the TV. (heard YouTube Video clearly, but couldn't here TV). Now keep in mine I have 200 Watt RMS Logitech 2.1 Speakers w/a Sub Woofer on my PC & they were at 33% volume.
as most are on mango now...
so the subcategories are named...can you name the keys to edit?
even better would be a *.reg-file we can provxml
diboze said:
as most are on mango now...
so the subcategories are named...can you name the keys to edit?
even better would be a *.reg-file we can provxml
Click to expand...
Click to collapse
see drkfngthdragnlrd's post #9, they key is the same for all:
InitVol = 100
change the number you find to 100. Most of them are already on 100.
drkfngthdragnlrd said:
I have no clue what DTMF is. I believe the value stands for % of max volume. I set them all to 100. Now I may just be hearing things, but it sure sounds louder to me. I had the TV playing on my PC & the YouTube video on my HD7 droned out the TV. (heard YouTube Video clearly, but couldn't here TV). Now keep in mine I have 200 Watt RMS Logitech 2.1 Speakers w/a Sub Woofer on my PC & they were at 33% volume.
Click to expand...
Click to collapse
DTMF (dual tone multi frequency) is the signal to the phone company that you generate when you press an ordinary telephone's touch keys. In the United States and perhaps elsewhere, it's known as "Touchtone" phone (formerly a registered trademark of AT&T). DTMF has generally replaced loop disconnect ("pulse") dialling. With DTMF, each key you press on your phone generates two tones of specific frequencies. So that a voice can't imitate the tones, one tone is generated from a high-frequency group of tones and the other from a low frequency group.
:http://searchnetworking.techtarget.com/definition/DTMF
derausgewanderte said:
see drkfngthdragnlrd's post #9, they key is the same for all:
InitVol = 100
change the number you find to 100. Most of them are already on 100.
Click to expand...
Click to collapse
Hi,
You did not understand. After update to Mango there is no possibility to edit registry yet. So we need a full code to do it by provxmal. If you have access you can do it for us.
PanNet said:
Hi,
You did not understand. After update to Mango there is no possibility to edit registry yet. So we need a full code to do it by provxmal. If you have access you can do it for us.
Click to expand...
Click to collapse
I do understand. if you want to inject this into the registry via provxmal then you need to convert this into code for the registry, no?
[HKEY_CURRENT_USER\Control Panel\SoundCategories\Alarm\]
"InitVol"=dword:00000064
or
"InitVol"=hex(b):64,00,00,00,00,00,00,00
(100 dec = 64 hex). I am sure the programmers here know exactly what to do with it.
and the same for
DTMF\; InCall\; InCall2\; Notification\; Reminder\; Ring\; RingPreview\; System\; SystemNotification\; SystemVibrate\
but maybe I am missing something....
PanNet said:
Hi,
You did not understand. After update to Mango there is no possibility to edit registry yet. So we need a full code to do it by provxmal. If you have access you can do it for us.
Click to expand...
Click to collapse
EDIT: Speaking of which, I found another registry that deals with how audio is handled. Attached is the provxml for it. This CustClear.provxml has all the volume registry edits I have done. It give you 50 steps for volume in call & default system.
derausgewanderte said:
I do understand. if you want to inject this into the registry via provxmal then you need to convert this into code for the registry, no?
[HKEY_CURRENT_USER\Control Panel\SoundCategories\Alarm\]
"InitVol"=dword:00000064
or
"InitVol"=hex(b):64,00,00,00,00,00,00,00
(100 dec = 64 hex). I am sure the programmers here know exactly what to do with it.
and the same for
DTMF\; InCall\; InCall2\; Notification\; Reminder\; Ring\; RingPreview\; System\; SystemNotification\; SystemVibrate\
but maybe I am missing something....
Click to expand...
Click to collapse
Hi,
Thanks. Can you write default settings for InCall, InCall2, Ring, RingPreview.
There is an Android 2.2 800Mhz 256MB 8GB 6,2" TFT CAR DVD on sale (about 800 USD with delivery to door in Russia) that I have bought recently and after some software installations it does deliver what I have wanted to have in the car.
Nevertheless there are a few major complaints to its performance: http://www.youtube.com/watch?v=cx53a6N7_ws
As well there are several other minor things that would be great to change if possible.
If there is someone interested and able to cook a custom ROM for this device - I can send this device for free as a gift and for experiments. We really want a good ROM for this CA-Fi Car Stereo and the guy's in China don't seem caring enough.
I will check this thread once in a while and provide contact details for anyone interested in developing this device. It is very close to being a great thing for a CAR! I have updated my email in the XDA profile so you can as well use this option to contact me.
I Have a ROM update file that came from the device vendor (dealer). I can send it out for revision.
The way to install this rom on the car stereo is to extract files to the root of a microSD card, insert it, switch off the device, then, while holding the screen tapped, power on – the device starts an install mode. When finished it asks for screen calibration and restarts with a new rom as after a hard reset (erases everything).
*******************
I understand you if you only need to have music playing while driving, as well as some people who still prefer using monochrome cell phones. This is a matter of needs.
Regarding the sound quality of this particular CA-Fi device its surprisingly fine. I use its 4x45W out lines conneted directly to car OEM speakers (its a Chrysler PT) and the subwoofer RCA out channel connected via a 1KW Kenwood amplifier to a large Polk Audio woofer. With the available in this device GEQ and Bass/Treble settings the unit provides perfectly sharp and clear sound in the high+mid ranges for the OEM speakers that in company with the powerful sub make a really impressive rich and clear sound scene with no distortion at any volume.
This sound setup is very easy and efficient. Honestly, to my hearing it is not lacking comparing to my previous JVC Mosfet 192/24 DAC car stereo that was routed through amplifiers for all channels to Focal speakers instead of the OEM... That was too much trouble for the gained advantage. Again, depending on the needs. Trully - the sound of this Android Radio is fine, a sound of a branded Hi-Fi car stereo.
And if you had a Win7 Car PC setup that is quite complicated to arrange you should agree that this easy one-box Android PC solution is a great idea. It provides the music and all the tablet PC advantages. It's really nice after switching on the ignition to hear from your car that you have a new e-mail arrived, and enjoy other goodies like that.
---------- Post added at 08:42 PM ---------- Previous post was at 08:23 PM ----------
Quote:
Originally Posted by leppie
And there is the Parrot as well.
yes, I considered the Parrot, but found it limited for modifications and with a too small screen. There is as well a Clarion at present under development, but it does not appeal to me neither. It is a concept from the Clarion Malaysia division and most likely will be limited for modifications; if it will ever be released at all:
http://www.youtube.com/watch?v=xNQC56S5NFI
http://www.youtube.com/watch?v=N1TFiy2Dsdg
I really have spent some plenty of time on the web before selecting this CA-Fi device and I couldnt find anything better. To be honest I even went trough a mistake and loss of money by ordering an Android/WinCE dual OS device first. Result - I installed it into my dad's car (its better than his OEM 2003 Mercedes device anyway). But that one is wierd. My advice: be aware not to get one of those by mistake. For example, mine had GPS only in WinCE and 3G only in Android - so I couldnt have the Navigation system working along with traffic updates.... this spoiled everything for me.
PS
Important to know that CA-Fi offer a few dozens of versions of the same model with different front panels to match many of original car dashboards without the need of modifying the panels - the device fits in as a replacement for the OEM unit! As well for those who think that there are many different Android car stereos to choose from - this may be the same model with different front facing.
Like all of theese are the same device:
FINAL UPDATE November 14th, 2013:
As if we didn't have enough proof. But as confirmed by LG support, logcats with BTsnoop debugging enabled to the fullest. When pairing an APT-X device the Nexus 5 uses SBC codec. So NO APT-X support. However. KitKat 4.4 is compiled with a higher SBC bitrate (see: http://code.google.com/p/android/issues/detail?id=39632#c284)
See posts: #32 and #33 for more information.
Special thanks to Jur1nator for doing the heavy lifting with providing the relevant logs!
-----------
Original Post:
Hi guys,
For those audiophiles out there. Does the Nexus 5 have APT-X (bluetooth codec)?
The Nexus 10 and the S4 Google Edition (proven by logcat) had APT-X, so it is not outside the realm of possibility that the Nexus 5 has APT-X.
If anyone is able to confirm once the devices shipped out (I realized I posted this a little pre-emptively), let us know in this thread.
--
EDIT: I have ordered a Nexus 5 32GB Black for my brother, and will see if I can get him to tell me if it includes APT-X. I will update this thread once an answer is found. If I didn't update yet, it means I'm still looking. I will not leave you guys hanging. Send me a PM if you want to remind me
EDIT2 (November 5th, 2013): Though not confirmed, bobrock has provided the thread http://www.bloghandy.de/nexus-5-alle-daten-geleakt-ab-morgen-vorbestellbar which does mention aptX. I will not say for sure yet (as it does appear to be a copy-paste from S4's Audio/Video) that it does until I am 100% confident. I might buy Nexus 5 but shipping times will be 3-4 weeks, if you guys are patient.
EDIT3 (November 6th, 2013) was searching around and found http://productforums.google.com/d/msg/nexus/az9UzY_t6P8/NH7rjp2ANeMJ
I ask google, they told me to ask LG. I ask LG, they told me, the NEXUS 5 does NOT support aptx (
Click to expand...
Click to collapse
Could be disappointing...
---
Thanks!
I would like to know it too
Not according to the aptX developer:
http://www.csr.com/technology-solutions/av/audio-products-powered-by-csr-aptx/smartphone
that list is often not updated (nexus 10 for example wasn't listed)
m3talm0rph is correct on this one. Most of the time that list is properly maintained (but not always), when the S4 was released, the S4 was added to the list. When the Note 3 was release, despite having confirmed APT-X on both models (some by logcat tests, some by aptX being on the boxart), that list still does not include the Note3.
The only way I see this being confirmed is someone testing with their Nexus 5 device themselves, via logcat or a headset that can tell you when it is in APT-X mode (some headsets have different LED colors depending on codec used). CSR is not helpful with relaying this information to customers.
I will try my best to figure this one out , if anyone else has any information through, feel free to post!
Thanks
would like to know too
There isn't a single LG device on that list. Don't hold your breath on LG suddenly plopping apt-x on a Nexus device.
Vincent Law said:
There isn't a single LG device on that list. Don't hold your breath on LG suddenly plopping apt-x on a Nexus device.
Click to expand...
Click to collapse
The LG G2 has apt-X.
According to german site below, it does support apt-X! Huray!
_w_w_w*b_l_o_g_h_a_n_d_y*d_e/n_e_x_u_s_-_5_-_a_l_l_e_-_d_a_t_e_n_-_g_e_l_e_a_k_t_-_a_b_-_m_o_r_g_e_n_-_v_o_r_b_e_s_t_e_l_l_b_a_r_
As long as someone does not confirm it I take this with a grain of salt. (See: Adobe Flash 10.1 support)
Remove "_" & "*"
bobrock said:
According to german site below, it does support apt-X! Huray!
As long as someone does not confirm it I take this with a grain of salt. (See: Adobe Flash 10.1 support)
Click to expand...
Click to collapse
Hi bobrock, thanks for letting us know that link. I added it to the main post in an EDIT. Being a devils advocate I will say it's possible that is not true, this site has the EXACT same block of text for audio, which may mean for the Nexus 5 it is a copy-paste rather than an actual confirm.
http://www.pocketpc.ch/samsung-gala...-s4-vorbestellen-verfuegbarkeit-preise-4.html (S4)
From the link above:
Audio- / Videoformate: MP3, AMR-NB/WB, AAC/AAC+/eAAC+, WMA, OGG, FLAC, AC-3, apt-X, MPEG4, H.264, H.263, DivX, DivX3.11, VC-1, VP8, WMV7/8
Click to expand...
Click to collapse
Exact same block of text.
i have an aptx sony bt headset...
is there an actual way or app i can test or see if i am using aptx on my n5?
Jur1nator said:
i have an aptx sony bt headset...
is there an actual way or app i can test or see if i am using aptx on my n5?
Click to expand...
Click to collapse
I don't know if your BT headset does it, but depending on which codec is used, it has a different LED (like RED = AAC, Blue = APTX, etc)
If that can't tell you, we'll have to hope that the logcat on the device side has the information about what codec it uses.
Most likely the steps would be:
-Root (or not)
-adb logcat (or get a logcat app off playstore)
-turn on bluetooth
-connect device
-turn on music
-look for something like the following
Here is a copy-paste from the Galaxy S4 Google Edition, in logcat when APT-X is enabled
D/CODEC_IF( 1543): codec_if_open: opening libbt-codec_aptx.so...
D/CODEC_IF_MOD( 1543): codec_open: codec_open
D/CODEC_IF_MOD( 1543): codec_open: apt-x encoder initialized successfully
D/CODEC_IF_MOD( 1543): codec_open: version : 1.0.1.0
D/CODEC_IF_MOD( 1543): codec_open: build : AND2.3-000
D/CODEC_IF( 1543): codec_if_open: codec module opened (v0.1
D/CODEC_IF( 1543): codec_if_close: codec_if_close hdl 1102352388
D/CODEC_IF_MOD( 1543): codec_close: codec_close
D/CODEC_IF_MOD( 1543): codec_close: freed apt-x encoder
Click to expand...
Click to collapse
I'll do that tomorrow to try to find out the truth on the matter
€dit..:
why wait and go to sleep and find out.. just did it.. but unfortunatly haven`t found anything related to aptx in the logs
maybe its just me being not super good with logcats but searched a bit through them and did not find anything codec related
just a bunch of a2dp and bluetooth related stuff :S
I have my N5 with and paired it with my AptX receiver.
I think the Nexus 5 has AptX because
1) It sounds great via Bluetooth (the built in speaker of the N5 is pathetically poor, even by N4 standards)
2) The bluetooth volume typically default to maximum when an AptX connection is made (my own observations)
Would still like confirmation from someone who knows how to check
I too am highly interested in the results of this investigation. I was eyeballing the Apt-X receiver Monoprice sells...
Jur1nator said:
why wait and go to sleep and find out.. just did it.. but unfortunatly haven`t found anything related to aptx in the logs
maybe its just me being not super good with logcats but searched a bit through them and did not find anything codec related
Click to expand...
Click to collapse
If you're up to it (assuming you can save it), do it again form start to finish and just copy paste the whole logcat to http://paste2.org and give us the pastebin link. I can look at it and see if I can find any valuable info (atleast to see WHAT codec it is using with A2DP). Thanks!.
There are APT-X enabled phones that don't mention it in logcat, so there is still a chance
iOStoAndroid said:
I have my N5 with and paired it with my AptX receiver.
I think the Nexus 5 has AptX because
1) It sounds great via Bluetooth (the built in speaker of the N5 is pathetically poor, even by N4 standards)
2) The bluetooth volume typically default to maximum when an AptX connection is made (my own observations)
Would still like confirmation from someone who knows how to check
Click to expand...
Click to collapse
This is good however still anecdotal and not definite. However thank you for trying to check .
Anyone else willing to chime in and help would be greatly appreciated , even if we get the answer we don't want I want to be 100% certain!
--
EDIT
I found some information on BTSnoop (bluetooth snoop) and this stuff is included in the Nexus 5 rom in \system\etc\bluetooth folder
I also found this thread on Google for debugging:
http://www.skavs.com/2013/07/debugging-bluetooth-on-android-4-2-jellybean/
I've never had a jellybean+ device so this is new to me, but if someone wanted to look and see if maybe something of value is there?
If anyone wants to do it that'd also be helpful, requires root to modify these files though I think!
Thanks guys!
here you go :
pastebin
really hope it helps, because i really want to know if it is working
@iOStoAndroid
don`t take me wrong, anyone helping is cool.. but your two points seem very subjectively
Jur1nator said:
here you go :
pastebin
really hope it helps, because i really want to know if it is working
Click to expand...
Click to collapse
Thanks! I was looking through the source code of bta_av_main.c (which I found out about through your logcats) and I found an interesting line
https://code.google.com/p/android-s...h--bluedroid&name=android-sdk-support_r11#596
Within the bta_av_api_register function it mentions the debug
if(AVDT_CreateStream(&p_scb->seps[index].av_handle, &cs) == AVDT_SUCCESS)
{
p_scb->seps[index].codec_type = codec_type;
APPL_TRACE_DEBUG3("audio[%d] av_handle: %d codec_type: %d",
index, p_scb->seps[index].av_handle, p_scb->seps[index].codec_type);
index++;
}
Click to expand...
Click to collapse
So there definitely is some debugging for codec_type (however I don't know 100% if this is the right code). I wonder how we can tap into APPL_TRACE_DEBUG3. I'm not 100% versed in this stuff but I will try to keep looking.
If you need more logs or something I am more than willing to help find out that mystery..
But looking through your findings it really doesn't tell me a lot
Also.. Let's say the n5 has aptx.. Is it bound to stock software or will I also have it once I move to cm?
Jur1nator said:
If you need more logs or something I am more than willing to help find out that mystery..
But looking through your findings it really doesn't tell me a lot
Also.. Let's say the n5 has aptx.. Is it bound to stock software or will I also have it once I move to cm?
Click to expand...
Click to collapse
I wish I knew how to decipher it more than now. From what I can tell APPL_TRACE_DEBUG3 does to logcat. You are basically right beyond the A2DP stuff there's no indication of what codec is being used. Someone else might need to jump in with their own knowledge, I'm stuck at the moment.
Going to CM you will lose APT-X. CM uses a modified BlueZ bluetooth stack and BlueZ does not have APT-X. It can be integrated from what I know, but no dev wants to do it because APT-X is proprietary and needs to be licensed.
I was searching around:
http://productforums.google.com/d/msg/nexus/az9UzY_t6P8/NH7rjp2ANeMJ
I ask google, they told me to ask LG. I ask LG, they told me, the NEXUS 5 does NOT support aptx (
Click to expand...
Click to collapse
Could be disappointing...