Database Users

[SOLVED]HTC HD cant be synced any more (dont know how i solved it)

Well, im currently facing a problem over my HTC HD, tht has the energy ROM wm6.5, and running a radio 1.17.
Last day i could sync my htc as i plugged it on my USB. Today tho, i cant. I had set up an FTP since last day, n nothing more. i checked the firewall settings from my win7 OS i have, nothing changed, wmdc is not being monitored. Also, i checked starting the HTC on "safe mode" (i dont remember the initals for that right now), while being connected with usb connection on my computer, it did recognized it. On usb to pc option, if i enable the view files, i can navigate through the SD. Windows sharing also is working. i tried to disable the enhanced connection something, still nothing. The only difference between enhanced setting and non enhanced is that when i enable the non enhanced, on devices i can see the WM device, while on enhanced setting its not appearing.
Any help would be apreciated.
Thanks for reading this,
Spyros Psarras aka SpyPower
Edit: i saw that on the network devices, i can see Microsoft Windows Mobile Remote Adapter. as mentioned on this site "cant post the link but it's a windows troubleshooting site" i need to uniinstall it, but after uninstalling it, and replugging the device, it keeps installing it back. I suppose that this comes from a network sharing program or something like that. I have installed WMWifirouter, but... i'll try to uninstall it.

Because i have only 1 post noone is replying to my question? seriously, i cant fix it. 3rd day today that i cant sync it. I didnt provide lots of informations?

Today i tested my blackstone on another computer and it synced perfectly. So that means that my problem is on my computer. Ill try a system restore in a min.
Ill post my results in a bit if there's someone else out there that is interested.
If you have any idea on how to fix my problems, you can always help me out by just pasting a link from wiki or typing possible solutions here. I seriously cant think of anything else.

when you plug you phone in does it show connected in devices or is there a exclamation mark?, if so then I had this problem myself. I ended up having to reflash my rom. Initially reinstalling the USB drivers sorted it but when I took it out again and put it back in it failed again.

thanks for the reply stoolzo
when i plug the phone it shows as a connected device on my computer, displaying it as a generic RNDIS on the devices list on my win7, and the driver on network list under device manager is "Microsoft Windows Mobile Remote Adapter".
When i try to update it, on my HTC's side the active sync displays "attention required" and on my computers side, it only displays that kinds of thinks i already posted before.
I tried to rollback, nothing changed. Removed WMDC, nothing changed (while it did reinstalled on its own after i removed it and rebooted and connected my HTC back again. Removed Drivers+uninstalling them, nothing changed. Tricolor screen works good with usb. File transfer mode, is working flawlessly. Wifi router mode is working too.
I may try to re-flash (omfg.. again?) later this evening.
Edit: Reflashed. Problem still exists. I cant sync my HTC while its on the windows 6.5. using energy rom.

can i have someones default environment Variables? its under Control Panel\All Control Panel Items\System under advanced system settings. I've changed that in order to install opnet, so this might be my source problem.
Also, i am trying to port scan the ports 990,999,5678,5721,26675 which only the 990 is open.

After some randome stopping on services, restarting the wmdc service, checking my ports and attacking my self from local area network. i managed to sync once my mob phone. But, i cant reproduce that again. so, im pasting down my netstat overview and tell me if the ports are correct. PID of WMDC 3732
Code:
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING 5720
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 940
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 5720
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:554 0.0.0.0:0 LISTENING 3200
TCP 0.0.0.0:990 0.0.0.0:0 LISTENING 3732
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING 576
TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING 108
TCP 0.0.0.0:1027 0.0.0.0:0 LISTENING 572
TCP 0.0.0.0:1030 0.0.0.0:0 LISTENING 636
TCP 0.0.0.0:1031 0.0.0.0:0 LISTENING 1416
TCP 0.0.0.0:1032 0.0.0.0:0 LISTENING 660
TCP 0.0.0.0:1033 0.0.0.0:0 LISTENING 3064
TCP 0.0.0.0:2200 0.0.0.0:0 LISTENING 5720
TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:8000 0.0.0.0:0 LISTENING 5720
TCP 0.0.0.0:8081 0.0.0.0:0 LISTENING 5720
TCP 0.0.0.0:9910 0.0.0.0:0 LISTENING 5720
TCP 0.0.0.0:10243 0.0.0.0:0 LISTENING 4
TCP 127.0.0.1:5679 0.0.0.0:0 LISTENING 3732
TCP 127.0.0.1:7438 0.0.0.0:0 LISTENING 3732
TCP 192.168.2.10:139 0.0.0.0:0 LISTENING 4
TCP 192.168.2.10:7821 62.38.5.240:80 CLOSE_WAIT 2936
TCP [::]:135 [::]:0 LISTENING 940
TCP [::]:445 [::]:0 LISTENING 4
TCP [::]:554 [::]:0 LISTENING 3200
TCP [::]:990 [::]:0 LISTENING 3732
TCP [::]:1025 [::]:0 LISTENING 576
TCP [::]:1026 [::]:0 LISTENING 108
TCP [::]:1027 [::]:0 LISTENING 572
TCP [::]:1030 [::]:0 LISTENING 636
TCP [::]:1031 [::]:0 LISTENING 1416
TCP [::]:1032 [::]:0 LISTENING 660
TCP [::]:1033 [::]:0 LISTENING 3064
TCP [::]:2869 [::]:0 LISTENING 4
TCP [::]:5357 [::]:0 LISTENING 4
TCP [::]:10243 [::]:0 LISTENING 4
TCP [::1]:5679 [::]:0 LISTENING 3732
UDP 0.0.0.0:500 *:* 572
UDP 0.0.0.0:3544 *:* 572
UDP 0.0.0.0:3702 *:* 1668
UDP 0.0.0.0:3702 *:* 1112
UDP 0.0.0.0:3702 *:* 1668
UDP 0.0.0.0:3702 *:* 1112
UDP 0.0.0.0:4500 *:* 572
UDP 0.0.0.0:5004 *:* 3200
UDP 0.0.0.0:5005 *:* 3200
UDP 0.0.0.0:5355 *:* 1252
UDP 0.0.0.0:50787 *:* 1112
UDP 0.0.0.0:52634 *:* 1668
UDP 0.0.0.0:55156 *:* 1112
UDP 127.0.0.1:1900 *:* 1668
UDP 127.0.0.1:49285 *:* 5788
UDP 127.0.0.1:49820 *:* 1668
UDP 127.0.0.1:53761 *:* 5628
UDP 192.168.2.10:137 *:* 4
UDP 192.168.2.10:138 *:* 4
UDP 192.168.2.10:1900 *:* 1668
UDP 192.168.2.10:49819 *:* 1668
UDP 192.168.2.10:51202 *:* 572
UDP [::]:500 *:* 572
UDP [::]:3702 *:* 1112
UDP [::]:3702 *:* 1112
UDP [::]:3702 *:* 1668
UDP [::]:3702 *:* 1668
UDP [::]:4500 *:* 572
UDP [::]:5004 *:* 3200
UDP [::]:5005 *:* 3200
UDP [::]:5355 *:* 1252
UDP [::]:50788 *:* 1112
UDP [::]:52635 *:* 1668
UDP [::]:55157 *:* 1112
UDP [::1]:1900 *:* 1668
UDP [::1]:49818 *:* 1668
UDP [fe80::3091:436:1680:1670%11]:1900 *:*
1668
UDP [fe80::3091:436:1680:1670%11]:49817 *:*
1668
C:\Users\SpyPower>

SpyPower said:
After some randome stopping on services, restarting the wmdc service, checking my ports and attacking my self from local area network. i managed to sync once my mob phone. But, i cant reproduce that again. so, im pasting down my netstat overview and tell me if the ports are correct. PID of WMDC 3732
Code:
C:\Users\SpyPower>
Click to expand...
Click to collapse
Hi SpyPower,
its not a solution sorry but is your problem the same as this thread I have just asked for help in ?
http://forum.xda-developers.com/showthread.php?t=477766&highlight=active+sync

One thing that made my connection unstable is the USB "fast connection". The dynamic creation of virtual ethernet kept being in conflict with my VPN and firewall.
On the HD, in the USB to PC connection settings, deselect the "fast connection" and try again.

ACtually i solved my problem. But its so freaking weird that im so embarrassed to type it down, and suggest that as a solution.
Your post seems to be exactly like mine. I had the same problems but i didnt try the bluetooth since i dont have one. The problems started after i had installed opnet on my computer and changed some parameters manually on my computer (im just taking a long shot).
What i did, was to play with the drivers all over the internet and it didnt work.
After like a week, i decided to install netlimiter, cause with that you can see each port a program is opening, and it could help me find my problem. and suddenly, after a reboot, BAM, it was working. Though i had to manually open the wmdc cause it couldnt automatically, open it was working.
The only thing i tried, was reinstalling the rom and other roms, and install some drivers for my usb connection.

cybermaus said:
One thing that made my connection unstable is the USB "fast connection". The dynamic creation of virtual ethernet kept being in conflict with my VPN and firewall.
On the HD, in the USB to PC connection settings, deselect the "fast connection" and try again.
Click to expand...
Click to collapse
It was not that, since it had been fixed

SpyPower said:
It was not that, since it had been fixed
Click to expand...
Click to collapse
Fair enough.
But maybe you should not have added [SOLVED] to the title? Its not so much solved, but stopped going wrong, people finding this thread will expect a clear solution if they see that keyword.

actually, its not a way to solve it, but my prob was solved. ill edit it tomorrow with more details.

Fire has Bluetooth and FM Radios but...

according to the ifixit teardown, at least on the first production run it looks like they used a Jorjin WG7310 WLAN controller that also includes BT and FM. it appears they simply left out the antenna and now that we have source, has anyone looked at how difficult it would be to cook in BT and FM support, assuming we install our own antennas?
http://www.jorjin.com/Product_SiPmodule_WG7310.htm

How do you know that they left out the antennas?

mdstricklin said:
How do you know that they left out the antennas?
Click to expand...
Click to collapse
well the antennas would have had to be detailed on the FCC filing and they were not. I can't imagine why they would pay extra to engineers to design in antenna routing for features they were never planning on using anyways. Then the cost of having the antennas put in the hardware would also be unnecessary......im fairly certain they were trying to cut every dollar out of it when possible, but i dont know for sure yet

The Nook Color has a similar chip and no antenna but Bluetooth still functions though with a range of only few feet. I don't know the correct physics terminology, but I believe the chip and the system board act as a primitive antenna. Of course, if the BT functionality operates through separate pins on that chip than the wifi then BT will only work if those data and power pins are properly connected into the system too.

heres something i just noticed.. in the init.rc it has this:
# do not launch the Radio Interface Layer daemon (RILd) service
# since there is NO modem on the board
#service ril-daemon /system/bin/rild
# socket rild stream 660 root radio
# socket rild-debug stream 660 radio system
# user root
# group radio cache inet misc audio sdcard_rw
but, then it has this:
service bluetoothd /system/bin/bluetoothd -n
socket bluetooth stream 660 bluetooth bluetooth
socket dbus_bluetooth stream 660 bluetooth bluetooth
# init.rc does not yet support applying capabilities, so run as root and
# let bluetoothd drop uid to bluetooth with the right linux capabilities
group bluetooth net_bt_admin misc
disabled
so it seems that it could support bluetooth.. i installed the bluetoothd binary, but in logcat at boot it says:
BluetoothHeadset( 1394): Could not bind to Bluetooth Headset Service
ActivityManager( 1394): Unable to start service Intent { act=android.bluetooth.IBluetoothHeadset }: not found
so im guessing the next thing is to mod the services.jar to include bt services?

just checking on the thread, if it has the hardware you would think this would be a big deal

jamesnmandy said:
just checking on the thread, if it has the hardware you would think this would be a big deal
Click to expand...
Click to collapse
the 2nd chip in the wifi module is the same as the WiFi/BT front end chip in the Nook Color. This is antenna switch, combining both the BT and WiFi connections to use only one antenna. See here and here and here.
If the BT portion is hooked up to a UART on the OMAP, and the BT power enable is wired or connected in tandem with the WiFi power, then BT should be possible.

I found this site with a good picture of the inside of the Kindle. They battery takes up most of the room.
http://www.theverge.com/2011/11/16/2565949/kindle-fire-root-teardown-source-code

pokey9000 said:
the 2nd chip in the wifi module is the same as the WiFi/BT front end chip in the Nook Color. This is antenna switch, combining both the BT and WiFi connections to use only one antenna. See here and here and here.
If the BT portion is hooked up to a UART on the OMAP, and the BT power enable is wired or connected in tandem with the WiFi power, then BT should be possible.
Click to expand...
Click to collapse
i am excite!

pyrorob said:
heres something i just noticed.. in the init.rc it has this:
# do not launch the Radio Interface Layer daemon (RILd) service
# since there is NO modem on the board
#service ril-daemon /system/bin/rild
# socket rild stream 660 root radio
# socket rild-debug stream 660 radio system
# user root
# group radio cache inet misc audio sdcard_rw
but, then it has this:
service bluetoothd /system/bin/bluetoothd -n
socket bluetooth stream 660 bluetooth bluetooth
socket dbus_bluetooth stream 660 bluetooth bluetooth
# init.rc does not yet support applying capabilities, so run as root and
# let bluetoothd drop uid to bluetooth with the right linux capabilities
group bluetooth net_bt_admin misc
disabled
so it seems that it could support bluetooth.. i installed the bluetoothd binary, but in logcat at boot it says:
BluetoothHeadset( 1394): Could not bind to Bluetooth Headset Service
ActivityManager( 1394): Unable to start service Intent { act=android.bluetooth.IBluetoothHeadset }: not found
so im guessing the next thing is to mod the services.jar to include bt services?
Click to expand...
Click to collapse
It appears that the Bluez packages are missing. In the init.ompa4430.rc, this line is disabled:
#Permissions for Bluetooth
# chown bluetooth bluetooth ro.bt.bdaddr_path
but...
the following lines are enabled (this may be for WiFi and not BT):
#change permisisons for radio
chmod 0660 /dev/ttyS0
chown radio radio /dev/ttyS0

This is Great News! Cant Wait to Start Modding!

My HTC EVO Shift has a FM radio built in and it will not turn on unless the headphones are plugged in it uses the cord as a antenna so no internal is needed.

Bluetooth working with CM7?
Anyone flashed the CM7 image that was released recently to see if Bluetooth works with that ROM?

asb2164 said:
My HTC EVO Shift has a FM radio built in and it will not turn on unless the headphones are plugged in it uses the cord as a antenna so no internal is needed.
Click to expand...
Click to collapse
Blue tooth will only work with a edited Kernel
Sent from my Kindle Fire using xda premium

BT does not work yet in CM7 or even the latest build of CM9 for the kindle fire
whistlestop said:
Anyone flashed the CM7 image that was released recently to see if Bluetooth works with that ROM?
Click to expand...
Click to collapse
Sorry guys doesn't work yet. I will try to create a custom kernel tonight though.

That would be cool if we had access to bluetooth and FM transmitters

awidawad said:
Sorry guys doesn't work yet. I will try to create a custom kernel tonight though.
Click to expand...
Click to collapse
Do your best man. This is the only thing keeping me from an ics rom
sent from my rooted kindle fire

Possible Problem...
Sorry guys might not be tonight because the basic bluetooth driver I tried for the kf won't work. I may have to make even more modifications to the kernel, so this might take awhile. Another problem is the possibility of different hardware in different kindles. http://forum.xda-developers.com/showthread.php?t=1430473&page=3 As you can see the bt and fm is crossed out in this model.

Can't wait to hear of more progress on this.

awidawad said:
Sorry guys might not be tonight because the basic bluetooth driver I tried for the kf won't work. I may have to make even more modifications to the kernel, so this might take awhile. Another problem is the possibility of different hardware in different kindles. http://forum.xda-developers.com/showthread.php?t=1430473&page=3 As you can see the bt and fm is crossed out in this model.
Click to expand...
Click to collapse
That would not be good to have different hardware in some kindles, hope mine has the good stuff, lol
Sent from my Kindle Fire using xda premium

MOTOACTV audio input development

I have found a way to record audio with the MOTOACTV (using a headset with microphone):
download the attached amixer and aplay executables.
copy them to the /system/bin/ folder in your MotoACTV
Code:
adb remount
adb push amixer /system/bin/
adb push aplay /system/bin/
adb shell chmod 755 /system/bin/amixer
adb shell chmod 755 /system/bin/aplay
adb shell ln -s /system/bin/aplay /system/bin/arecord
Now we need to configure the audio input, this is the trick:
Code:
adb shell
amixer sset 'PGA Mux Right' 'MIC2'
amixer sset 'Audio Source' 'Mic2'
amixer sset 'XSP-IP Attenuation' 63
Now, we can use arecord and aplay to test:
Code:
adb shell
arecord -f cd -d 5 /sdcard/test.wav
will record for 5 seconds
Code:
aplay /sdcard/test.wav
Now, we now that there's nothing wrong with the hardware or the kernel, but I'm not sure if the problem lies in libaudio.so, libasound.so or in one of the android configurations.
Any ideas?

You sick son of a *****. Nice. Very nice

Wow, ingenius. Using alsa utils to perform recording. Sometimes I forget how close android is to linux. Great Find.

|SavageD| said:
Wow, ingenius. Using alsa utils to perform recording. Sometimes I forget how close android is to linux. Great Find.
Click to expand...
Click to collapse
Any progress?
Got to be a library thing right?

Just curious if anyone's had any progress in this? I dusted the motoactv off yesterday and started playing with it again.
Do we still have a community? Ours is waaay better than that Samsung one - if we could just get audio working right.
I thought up kind of a neat idea on how to give vibrator support to motoactv:
we could open up a sony liveview (scrap out the screen and housing and just encase it in electrical tape or something small) and pair it with motoactv via bluetooth (running liveview on moto)... notifications would result in the liveview vibrating. ))))) bit crazy but I think it'll work.

willfck4beer said:
Just curious if anyone's had any progress in this? I dusted the motoactv off yesterday and started playing with it again.
Do we still have a community? Ours is waaay better than that Samsung one - if we could just get audio working right.
I thought up kind of a neat idea on how to give vibrator support to motoactv:
we could open up a sony liveview (scrap out the screen and housing and just encase it in electrical tape or something small) and pair it with motoactv via bluetooth (running liveview on moto)... notifications would result in the liveview vibrating. ))))) bit crazy but I think it'll work.
Click to expand...
Click to collapse
I've got one of those... a little scared to try though lol!

ClearD said:
I've got one of those... a little scared to try though lol!
Click to expand...
Click to collapse
Well we could test to see if we can even pair liveview to actv first... do we have support for serial bluetooth profile?
I got Torque to download and install on the actv and I went to connect to my obd2 bluetooth dongle... but have to pre-pair them... and my actv only seems to find bluetooth headset/a2dp type things... I'm a bit foggy but I thought I downloaded some .zip add on/mod that was supposed to allow more profiles to function. Can't remember the details though. What is the extent of people's success with bluetooth beyond headset devices?

Been able to bluetooth tether devices via a third part app. But, like you said, My Motoactv only recogines audio devices in the stock bluetooth settings.
PS. The Sony Liveview vibration is so weak, it is hardly worth the effort, even though the idea was most certainly thinking outside the "motoactv" box!

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.