Database Users

9000 and BT WITH CALLER ID problem

:?: I bought a BT WITH CALLER ID for the 9000 it is very good and works good with the phonetic calls ,the problem is in the recognition while it makes it recognizes the number it does not make such the name(like bt800) I believe that is subject of sofware appliance.
for me even if I only have bluetooth few hours the problem is that when it calls somebody it does not transport the number with the (+) from 9000 to bluetooth, examle. + 30210555555... but 302105555555.. in the screen with result when I want to take back the one who call me it says wrong number(my nokia 6600 and ericcson v800 that I tryed it plays with no problem so it is not subject bluetooth but the 9000).
i ask now if someone knows how can the 9000 would send (+) with number? :?: :!:
I thank you
and sorry for my bad english

If you are using a Jabra BT800, just update the firmware with the new release available on Jabra site, this known problem has been fixed!
Bye!

Hi Mastelos,
I just sent this as a PM to another user of the forum so I may as well post it here also.
I hope you're technical and understand 3GPP & BT specs!
I'm basing this on the fact that nobody has said they can receive the phonebook name to the BT headset. As such I guess it's a phone issue.
When a phonecall arrives at the mobile the caller ID (CLIP) is displayed from the modem with the command AT+CLIP. When the headset is alerted to the incoming call it sends AT+CLIP to the modem also. Now the response to AT+CLIP for the phone is defined in the 3GPP 27.007 specs as "+CLIP: <number>,<type>[,<subaddr>,<satype>[,[<alpha>][,<CLI validity>]]]". Only <number> & <alpha> are of interest here where <number> is the phone number and <alpha> is the representation (address book) of the number. I'm not sure where the <alpha> is taken from (SIM or phone memory) but I guess this is phone software implimentation.
The BT specs specify that the only response to AT+CLIP from the headset should be <number>. This is understandable as not every call you receive will have an <alpha> available. Because of this most phone software doesn't impliment it. Although the BT specs only specify <number> it doesn't restrict the other responses listed in the 27.007 document, specifically <alpha>. This is what SE and Nokia are doing. Their phone software to BT stack software has been written to add the <alpha> functionality to a BT headsets AT+CLIP request / responses. It appears HTC have not taken this step to add this functionality so this is why we don't get the name on the BT headset.
This is something which could be added in the future but I don't work for HTC so can't say (
Hope this explains all... Don't worry if you want to ask anything more.
Gavin.

ok thanks
if i understand well the name not appears is htc software thing ok until now but tell me please if it is the number (+) software thing
i try to explain better ,when i recieve a call a number appears in the bluetooth headset like 3021055....... when the headset is connected with other phone like my 6600 or v800 the number appears like this +3021055... with the result if i want to call back that number from the headset with 9000 i cant i need 9000 to send + with the number
hope you understand me hi hi
Panos

i do not have the bt800 i have this
http://www.mobilefun.co.uk/product/9275.htm

Hi Mastelos,
I understand your problem now. The post I added before was to do with names not appearing and not the '+'.
Ok, to start with both my SE HBH-200 and Parrot CK3100 BT devices show the numbers with the '+' OK so this is a headset issue. This is what is probably happening. The response to AT+CLIP should be: "+CLIP: <number>,<type>[,<subaddr>,<satype>[,[<alpha>][,<CLI validity>]]]"
<number> = Phone number of the caller - if not hidden
<type> = The type <number>. 129 for national and 145 if it has a '+'.
<alpha> = The phone's 'guess' of the name associated with that number.
What I suspect is happening is the Jabra is not identifying the <type> and thus thinking its response to AT+CLIP is a national number, i.e. without the '+'. This could be a formatting issue of the AT+CLIP response or it could be the Jabra has a bug (as mentioned by Wh1sp3r) which means it doesn't get the <type> and therefore doesn't display the '+'.
This is all a guess, albiet I work in this field so it's an eductated experienced guess, I don't have a Jabra to fully test and confirm.
Wh1sp3r has the best solution - get a SW update from the headset designer.
Thanks,
Gavin.

tnx Gavin for the reply
i saw the update of jabra bt800 for this problem but i have a v-three bth-8 headset . i send e-mail to both qtek and v-three the problem is that my headset works ok( the + symbol appears with all oter phones except qtek9000 )
tnx

GavinN said:
Hi Mastelos,
I understand your problem now. The post I added before was to do with names not appearing and not the '+'.
Ok, to start with both my SE HBH-200 and Parrot CK3100 BT devices show the numbers with the '+' OK so this is a headset issue. This is what is probably happening. The response to AT+CLIP should be: "+CLIP: <number>,<type>[,<subaddr>,<satype>[,[<alpha>][,<CLI validity>]]]"
<number> = Phone number of the caller - if not hidden
<type> = The type <number>. 129 for national and 145 if it has a '+'.
<alpha> = The phone's 'guess' of the name associated with that number.
What I suspect is happening is the Jabra is not identifying the <type> and thus thinking its response to AT+CLIP is a national number, i.e. without the '+'. This could be a formatting issue of the AT+CLIP response or it could be the Jabra has a bug (as mentioned by Wh1sp3r) which means it doesn't get the <type> and therefore doesn't display the '+'.
This is all a guess, albiet I work in this field so it's an eductated experienced guess, I don't have a Jabra to fully test and confirm.
Wh1sp3r has the best solution - get a SW update from the headset designer.
Thanks,
Gavin.
Click to expand...
Click to collapse
Do you get the caller name on your V-Three with an HTC device?

no name only number

Connecting to Ford Audio

There are other car connection threads but I thought I would post this thread to provide a search hit for anyone with a Ford Bluetooth Radio. It combines bits from a couple of threads and should enable you to successfully connect to your Ford car. Thanks to all of the other posts whose work I have cobbled together here. This is confirmed as working with the HTC 1.66 WWE ROM.
Out of the box the HD2 does not initiate auto connection with the Ford, refuses to pair with the Sony radio and hangs the radio at the end of a call so...
Using Resco or similar registry editor..
1. Modify the HandsFree plug-in: HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change DWORD SupportedFeatures to 45 (was 1379)
ii. Create binary value HFBDA , set to same value as LastConnectedBda
iii. Create DWORD HFDeviceType (Dec) 2
2. Modify the WIDCOMM bluetooth general settings: HKLM\Software\WIDCOMM\BtConfig\General
i. Change binary Value bdaddr to (no value) delete the existing key value, was 00 23 76 74 2c d5
ii. Change DWORD DisableReopenAudio to 0 (default is 1) I didn't have this registry key so I created it with DWORD value (dec)0
3. Reboot device (soft reset or long press off until power off option).
These above mods make the handshaking between car and HD2 much less prone to lockups!
Go to car, check that radio has bluetooth enabled.
HD2 wil find car (Ford Audio), send a random keycode - pairing fails but this will wake up radio which displays another keycode. Re-enter this correct keycode and pair device.
If a Ford built in radio then accept incoming connections and phonebook download when prompted.
If the Sony radio (Galaxy, S-Max etc) then you must also accept the stereo music connection else it will not work.
On HD2 go to settings, menu, all settings, bluetooth and 'add knickname' to your Ford Audio connection, check that 'accept all connections' box is ticked on this page.
Only bug so far is that by accepting the stereo audio connection the music player starts playing whenever you connect to the Sony radio. The music cannot be heard as the Sony does not accept incoming streams - however if you do not enable it at the connecting stage then the phone connection subsequently fails and refuses to work again. If anyone can get around this annoying problem then please post below.

Huge thanks for pulling this together
I'd about given up hope of getting the HD2 working with my S-Max. Still not perfect, but at least now usable.
Great stuff.
Interstingly the current S-Max seems to be generally less compatible than the one from a couple of years ago.

Serial Connection to Bluesmirf Bluetooth Dongle

Hi, I'm working on an app which needs to send serial output to a bluesmirf bluetooth dongle connected to a Smartfusion eval board.
So far I have been trying to make the connection in the same way done through the BluetoothChat example app, but have had no luck. It appears that this is in some way related to a failure from the fact that the bluesmirf doesn't have the same UUID. This is the Logcat message I get right before it the connection attempt stops:
04-12 03:28:32.670: DEBUG/BluetoothService(92): Cleaning up failed UUID channel lookup: 00:06:66:04:AA:EA 8ce255c0-200a-11e0-ac64-0800200c9a66
I've been Googling any and every combination of "bluesmirf," "android," and "bluetooth" but can't find any sort of guide or help for having an app connect to anything but the same app on another phone.
Any sort of insight would be greatly appreciated.

Found Solution
Ok so following links through stackoverflow lead me to an answer that was obnoxiously simple.
If anyone else ever finds this thread for the same issue:
There is a set UUID for serial devices, and you just need to set your apps UUID to this value:
00001101-0000-1000-8000-00805F9B34FB

What does Intent.ACTION_HEADSET_PLUG: state: 2 means?

Dear developers,
I absolutely couldn't find my answer on google, so I hope you can help me out.
Problem
I'm using the Intent.ACTION_HEADSET_PLUG to detect the state of the jack-plug (plugged-in or not). But when I connect my HTC Desire with Android-2.2.2 to my Eclipse and plug-in my jackplug, I get "Intent.ACTION_HEADSET_PLUG: state: 2". But according to the android API, the state 2 doesn't even exist. What does this "state: 2" mean and how to solve this?
Android API
The intent will have the following extra values:
state - 0 for unplugged, 1 for plugged.
name - Headset type, human readable string
microphone - 1 if headset has a microphone, 0 otherwise
Click to expand...
Click to collapse
Logcat output
Code:
//When I plug IN my headset
HeadsetObserver Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=130, DEVPATH=/devices/virtual/switch/h2w, SEQNUM=1506, ACTION=change, SWITCH_NAME=Headset}
HeadsetObserver Intent.ACTION_HEADSET_PLUG: state: 2 name: Headset mic: 0
//When i plug OUT my headset
HeadsetObserver Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=0, DEVPATH=/devices/virtual/switch/h2w, SEQNUM=1505, ACTION=change, SWITCH_NAME=Headset}
HeadsetObserver Intent.ACTION_HEADSET_PLUG: state: 0 name: Headset mic: 0
Hope you can give me some more information! Looking forward to hear from you. Thanks in advance!!

Have you beat audio enabled? HTC has done a deep refactoring on audio management, for test try with another device too
Sent from my Nexus 4 using XDA Premium 4 mobile app

taomorpheus said:
Have you beat audio enabled? HTC has done a deep refactoring on audio management, for test try with another device too
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't have Beats audio, but maybe it is a code change by HTC anyway. Does anyone knows where I can find the API/HeadsetObserver source by HTC? Thanks.

Verify whether headset supports aptX?

I purchased a headset that claims to support aptX, but I can't verify it's working. I've enabled it in OP5 settings, and also tried restarting the phone for good measure. The manual for the headset specifies that it supports aptX, and it doesn't list any special steps to enable.
Looking at logcat and btsnoop output it seems to be negotiating SBC. I've tried playing FLAC and MP3 files with VLC, and streaming over Google Play music and it does not negotiate aptX. Has anyone else been able to confirm that aptX is working on their OP5?
I followed this answer on stackexchange and got the btsnoop logs, analyzed with WireShark. This is what I came up with:
Code:
AVDTP 25 Rcvd ResponseAccept - GetCapabilities - Audio SBC (16000 32000 44100 48000 | Mono DualChannel Stereo JointStereo | block: 4 8 12 16 | subbands: 4 8 | allocation: SNR Loudness | bitpool: 2..53)
The headset is obviously responding with SBC, but does this definitively mean the headset is refusing to support aptX, or could it be an issue with the OP5?
I can post more of the btsnoop logs or logcat if necessary.

How would I confirm it? I see the "aptX HD" logo briefly flash on the screen whenever I start playing video or music after connecting to my LG HBS-730, but how would I know for sure? I mean it does sound better than the same media on my wife's Moto X Play.

Chahk said:
How would I confirm it? I see the "aptX HD" logo briefly flash on the screen whenever I start playing video or music after connecting to my LG HBS-730, but how would I know for sure? I mean it does sound better than the same media on my wife's Moto X Play.
Click to expand...
Click to collapse
If you run a logcat over adb while either connecting or playing the media (I'm not sure which) you should see some output about codec negotiation. That's probably the quickest and easiest way. The btsnoop method in the stackexchange I linked is more low level, but I was hoping to see conclusively if the device supports aptX
I've never seen an aptX logo you up on screen. Hopefully that's a reliable indicator, but I would think that would get annoying!
One more thing, my understanding is that aptX and aptX HD are two different things (someone correct me if I'm wrong), even if one is working I don't think that necessarily means the other is.
I'm probably going to return this headset if I can't prove that aptX is working for it...

Here is the screenshot.
And here's an exert from logcat while trying to play some tune via Google Play Music app:
Code:
08-17 17:39:43.734 2880 20308 D bt_btif : btif_snd_ctrl_cmd : A2DP_CTRL_CMD_START DONE
08-17 17:39:43.734 2880 2900 D bt_btif : btif_av_state_opened_handler event:BTIF_AV_START_STREAM_REQ_EVT flags 0 and index = 0
08-17 17:39:43.734 2880 2900 I bt_btif_media: btif_a2dp_encoder_init SCMS_T DISABLED
08-17 17:39:43.734 2880 2900 E bt_btif : bta_av_select_codec hdl = 65
08-17 17:39:43.734 2880 2900 I bt_btif_media: btif_a2dp_encoder_init Selected Codec aptX
08-17 17:39:43.734 2880 20306 D bt_btif : btif_media_thread_handle_cmd : 5 BTIF_MEDIA_SBC_ENC_INIT
08-17 17:39:43.734 2880 2912 D bt_btif : AV Sevent(0x41)=0x120b(AP_START) state=3(OPEN)
08-17 17:39:43.734 2880 20306 D bt_btif : btif_media_thread_handle_cmd: BTIF_MEDIA_SBC_ENC_INIT DONE
The "Selected Codec aptX" bit makes me think it's working. There are a lot of crappy knock-off headsets that boast aptX "support" that isn't working right because they omit the profiles necessary for it to actually work. I remember reading an article a while back about this very problem, but can't seem to find the link anymore.

Chahk said:
The "Selected Codec aptX" bit makes me think it's working. There are a lot of crappy knock-off headsets that boast aptX "support" that isn't working right because they omit the profiles necessary for it to actually work. I remember reading an article a while back about this very problem, but can't seem to find the link anymore.
Click to expand...
Click to collapse
Ok, that logcat looks like what I was expecting to see. I agree that yours is working. Thanks!
For the record, this one *is* some cheap Chinese one I found on Amazon. The sound quality is not awful for the price, but the false advertising is unforgivable.

I see aptX logo flashed on a screen after my Sennheiser HD1 got connected via Bluetooth. And I don't see that logo when using other BT headsets.