Audio/Video Remote Control Profile (AVRCP) is a very nice feature of Bluetooth. Accessible on Advanced Audio Distribution Profile (A2DP)-capable Bluetooth Hi-Fi stereo headphones, they allow for remote controlling your media player on the Pocket PC: going straight to the next or back to the previous song or pause/resume or stop/restart the current one.
Now that I’m working on a big roundup of Bluetooth Hi-Fi stereo headphones, I’ve also thoroughly scrutinized the AVRCP capabilities of current Pocket PC multimedia players. In this article (which will be followed a lot of similar articles discussing AVCRP (and, naturally, A2DP) compliance of different stereo BT headphones), I elaborate on what you need to know about remote controlling your Pocket PC-based media player from the Plantronics Pulsar 590A stereo headset.
Unfortunately, current headsets are far from being compatible with all multimedia players and Pocket PC's. There are several multimedia players and Pocket PC's (more precisely, specific Bluetooth stack / A2DP / AVCRP implementations) not compatible with the Pulsar while it's compatible with other models and vice versa (for example, the built-in A2DP of the WM5-upgraded 2.01 hx4700 works just great with the 590A while it's almost useless with the Moto HT820). Therefore, what you read here mostly applies to the Pulsar only. Still, if you have (or, plan to purchase) a different model, this article will be really worth reading because it discusses a lot of additional hacks and tips - not only related to the Pulsar headset. For example, in addition to a lot of "which is the best media player I should look for", I also provide some dependable CPU usage statistics (playing a 112 kbps MP3 (Värttinä – Oi Dai / Oi Dai)) so that you will be able to compare the battery usage of each application (with and without the equalizer enabled – it’s only with TCPMP that enabling the equalizer caused some visible CPU usage increase. The CPU usage data was measured on my Pocket Loox 720; with WMP10, on my WM5 hx4700).
The, currently, four remote controllable third-party applications (the built-in Windows Media Player (WMP) is AVRCP-compliant in both version 9 and 10) are as follows:
The free, excellent Mortplayer (current, tested version: 3.31RC6 released slightly over a month ago). Its only downside is the lack for WMA support (the other three alternate clients support WMA.) I also recommend this thread on the AVRCP support of MortPlayer.
The free, also excellent TCPMP (current, tested version: 0.72RC1 released about half a year ago)
Pocket Player 3.0 by Conduits (current, tested version: 3.0 released two weeks ago; no build data available)
The fourth Pocket PC multimedia application to support AVRCP is 40iPlay (current, tested version: 10/01/2006 released two weeks ago), which should be accessible here. If you get a screen with a simple link when you visit the page like this, then, you’re out of luck: your IP address is banned off the site as is the case with many people having tried to access the page. Unfortunately, the developer doesn’t seem to be wanting to remove the ban of, it seems, half of the world (I also recommend this thread on this problem). If you also encounter this problem, I recommend trying it via alternate means; for example, accessing the page via your dial-up / mobile account. It’s via my GPRS account that I access the page.
It’s worth noting that, while 40iPlay runs flawlessly on my considerably older, PXA255-based WM2003 iPAQ 2210, it refuses to work on my (newer, PXA272-based) WM2003SE Pocket Loox 720 complaining about it not having an XScale CPU. This is certainly a bug in the current version; the older versions I’ve tested didn’t have this problem. Unfortunately, the hack PM'ed by FirstLoox forum member androabo (thanks for that!), that is, depressing “?” during loading the program, didn't work either.
Note that I’ve scrutinized the recording capabilities of the application in the Sound Recorder Bible.
I really recommend this media player because
it has one of the lowest CPU usage of all the applications (even slightly lower than that of TCPMP!) and has even in-app CPU speed setting capabilities to further reduce CPU consumption (please read this article (and all the past articles linked from it) for more on this subject: there, I've shown some nice examples of this fact.)
I've played a lot with the latter and found it to be highly useful and reliable. While it doesn't offer automatic scaling (unlike XCPUScalar), it's good to have it built-in on devices that otherwise, "out of the box" don't offer CPU speed setting capabilities (iPAQ hx4700 and 2210, HTC Wizard, Universal etc). It's really easy to use: you just click the Turbo ON/OFF and, then, SET icon when you want to switch back and forth between a downclocked and the original mode.
I've found playing stuff worked pretty OK with the following parameters:
h2210: 100 MHz (via wired headset!)
x51v: 208 MHz (via Widcomm A2DP) - note that the x51v also has a system-level CPU speed setter capabilities, but they're well-buried under the Power applet and you need to click a lot to access it
hx4700: 208 MHz (via A2DP)
Unfortunately, it's unable to underclock the HTC Wizard as can also be seen in this screenshot showing the CPU controls shown on the Wizard (example screenshots of running it on other devices follow: x51v, hx4700 and 2210).
its "Reverb" effect (accessible here) is by far the best I've ever heard on Pocket PC and is indeed industry-strength. I really recommend it - you'll love it
The compatibility / CPU usage can be found here - CLICK THE LINK!
CONTINUED BELOW!
The hacks I've used / referred to:
Adding A2DP (and AVRCP) support to WM2003 devices
WM2003 devices should use the Widcomm 1.6 HP Bluetooth AV upgrade to gain A2DP / AVRCP support. The update is officially only meant for HP iPAQ 5550 devices but it works (to some degree) on other Widcomm-based WM2003 devices too (you can install it on any device – the installer isn’t locked to the particular PPC model). Note that you shouldn’t except miracles: for example, on my HP iPAQ 2210, the sound sometimes stops for 1-2 seconds and, what is worse, it gets a considerably lower, really annoying pitch for some 10-15 seconds before this. That is, it’s highly possible you’ll find it useless on your particular WM2003 model too - it's only certified to work on the 5550.
Adding A2DP (and AVRCP) support to WM2003SE devices
(Widcomm-based) WM2003SE devices should use the hack CAB available here. See this and this for a generic discussion. Note that you shouldn’t try updating your WM2003SE device with the Widcomm 1.6 HP Bluetooth AV upgrade (see the WM2003-related section above) meant for plain WM2003 devices (you can, however, give it a try - it may work - or not). At least on my Pocket Loox 720, it would never stop discovering the services of my Plantronics and, therefore, seems to be useless.
Unfortunately, this update has severe problems: no matter what model it’s installed on, the sound transfer will just stop after some dozens of minutes and can only be restarted by explicitly disabling Bluetooth on the PDA and, then, reconnecting to the headphone (fortunately, no soft reset is necessary). This makes listening to music wirelessly really painful on the long run.
Note that exactly the same applies to the (current) Widcomm version 0.50 “hack” for the WM5-upgraded Dell Axim x50(v) and the entire x51(v) series: from time to time, the sound transfer will just stop and, then, you'll need to reconnect to the headset. (This problem may be only related to the 590A only - I haven't really seen similar bug reports in the above-linked thread - neither have I seen here.) This won't be a problem with most x51(v) users as the built-in A2DP / AVRCP support in AKU2.3 works with most headphones without making it necessary to install the Widcomm BT stack. It seems, however, it doesn't work with the 590A - using the standard, built-in A2DP support of WM5 AKU2, the music transfer to my 590A would stop after some 0.2-0.3 seconds. The case is exactly the same with the AKU 2.0 HTC Universal. Interestingly, FirstLoox owner Duncan hasn't run into this problem with his 590A, using the built-in A2DP support on his F-S N560.
Adding A2DP (and AVRCP) support the HTC Wizard
The HTC Wizard, unfortunately, which doesn’t have support for A2DP at all even in AKU2+ ROMs. Therefore, you'll need the CAB file available here (linked from this post in this thread; to be on the safe side, I’ve also made it available here. Note that it’s highly recommended that you also import this registry file after installing the CAB file (the latter is discussed here, here, here and here).
Note that, even with the registry hack, the sound quality of the Wizard over A2DP has remained considerably worse (it has pretty bad compression effects) than with my other test Pocket PC’s (with all media player apps - this means it's not a media player issue but that of the A2DP hack). Give it a try to see if you can live with the (comparatively) lower sound quality. Furthermore, unlike with the other solutions, after finishing a call, the music doesn’t automatically restart – you must manually press the Pause button on the headset.
Making the Pocket Player AVRCP work under WM5
(Big thanks to PPCT / AximSite forum member Haesslich for summarizing it so that I didn’t need to look / experiment with it up myself much.)
Get the Conduits WMP Plugin Adapter 1.1 from the plug-in page (I really recommend it if you, for example, want to get FLAC or MOD support for your Pocket Player) (direct link to the download).
Unzip gen_wmhost.dll from the archive and put it in the home directory of your installed application ([Storage card name]\Program Files\Conduits\Pocket Player).
Go to Menu/More/Options (in 3.0; in 2.8, Menu/Options) and select the Plugins tab (it’ll be on the far right)
Single-click “Conduits WM Plugin Adapter”, when the context menu comes up, select “Configure”.
Click the “Configure WM plugins to load” button.
Under version 2.8, it’ll ask four questions; under 3.0, two. Click “Yes” in all cases.
Click OK and restart Pocket Player. Now, remote controlling should work OK.
The results shown in the comparison chart
As can clearly be seen, with the Plantronics Pulsar 590A stereo headset, none of the four third-party applications supported it under all OS’es flawlessly. For example,
MortPlayer only supported AVRCP on WM5 devices with the Widcomm BT stack; it won’t work on WM5 devices with the Microsoft BT stack or on any pre-WM5 device
Pocket Player only supported pre-WM5 devices without additional hacking; it doesn’t work under WM5 (with neither of the two most common Bluetooth stacks). Fortunately, with the above-explained "hack" it's working just great on all my WM5 devices.
Finally, the case is just the opposite with TCPMP, which only supports WM2003SE devices, AVRCP-wise. It doesn’t work on WM2003 / WM5 devices at all.
The most AVRCP-compliant multimedia player is iPlay - it worked flawlessly on all my test devices, except for the Widcomm 1.6-based WM2003 ones. In there, previous / next wasn't available.
As can also be seen, you don’t need to be afraid of the CPU usage (battery consumption) figures of these applications. While Pocket Player uses about two times more CPU cycles than TCPMP or iPlay (the latter two without the equalizer), it’s still way better than some other, non-AVRCP-capable (and, therefore, not reviewed) multimedia players like ViTO SoundExplorer, which (at least in older versions) consumed way more CPU time when playing plain MP3 files as can also be seen in these benchmarks. Enabling the really nice Reverb feature on 40iPlay “only” doubles its CPU usage – then, it’s still not much worse than that of players that otherwise consume considerably more CPU cycles even without any DSP’s or equalizers enabled (MortPlayer, Pocket Player). That is, if you need the reverb effect (give it a try – it’s really cool), you can safely enable it.
N.B. Once again, the compatibility chart is based on my compliance tests with the Plantronics Pulsar 590A. With other headsets, you may have (slightly) different results (as has also been mentioned in the chart – see my comments in parentheses). I will continue posting compatibility information with other stereo headsets hopefully as early as next week.
Menneisyys said:
As can clearly be seen,
none of the three third-party applications support all OS’es. For example,
MortPlayer only supports AVRCP on WM5 devices with the Widcomm BT stack; it won’t work on WM5 devices with the Microsoft BT stack or on any pre-WM5 device
Pocket Player only supports pre-WM5 devices; it doesn’t work under WM5 (with neither of the two most common Bluetooth stacks)
Finally, the case is just the opposite with TCPMP, which only supports pre-WM5 devices, AVRCP-wise. It doesn’t work on WM5 devices at all.
Now, you have all the necessary information to select a compatible multimedia player for your particular OS and Bluetooth stack version
Click to expand...
Click to collapse
So, I guess that I have no choice. I have WM5 with the MS BT Stack. Am I right? If someone would be willing to tell me how to change the MS BT Stack out for the Widcomm BT Stack, I'd be very appreciative.
Also, this thread is very much needed in my opinion. Thank you for starting it.
Article heavily updated.
Another thorogh update
Menneisyys: said:
Making the Pocket Player AVRCP work under WM5
(Big thanks to PPCT / AximSite forum member Haesslich for summarizing it so that I didn’t need to look / experiment with it up myself much.)
Get the Conduits WMP Plugin Adapter 1.1 from the plug-in page (I really recommend it if you, for example, want to get FLAC or MOD support for your Pocket Player) (direct link to the download).
Unzip gen_wmhost.dll from the archive and put it in the home directory of your installed application ([Storage card name]\Program Files\Conduits\Pocket Player).
Go to Menu/More/Options (in 3.0; in 2.8, Menu/Options) and select the Plugins tab (it’ll be on the far right)
Single-click “Conduits WM Plugin Adapter”, when the context menu comes up, select “Configure”.
Click the “Configure WM plugins to load” button.
Under version 2.8, it’ll ask four questions; under 3.0, two. Click “Yes” in all cases.
Click OK and restart Pocket Player. Now, remote controlling should work OK.
Click to expand...
Click to collapse
Hopefully, this is what I've been looking for. We'll see.
Am I the only one that sees the value of this thread? I can't believe that I've had the only replies.
porterx said:
Am I the only one that sees the value of this thread? I can't believe that I've had the only replies.
Click to expand...
Click to collapse
Also make sure to link it from A2DP / AVRCP threads when needed so that the information gets to everyone
Mr
porterx said:
Hopefully, this is what I've been looking for. We'll see.
Am I the only one that sees the value of this thread? I can't believe that I've had the only replies.
Click to expand...
Click to collapse
These procedures didn't work for me. I tried 10+ times. I give up in frustration.
porterx said:
These procedures didn't work for me. I tried 10+ times. I give up in frustration.
Click to expand...
Click to collapse
Try connecting your headphones BEFORE starting PocketPlayer and the whole procedure. I didn't find this necessary, Haesslich, with his equipment, did (or at least it seems he neeeded it)
UPDATE (10/14/2006): thanks to FirstLoox and AximSite forum member androabo, now I know how iPlay can be started on the Pocket Loox 720 (or on any device that it refuses to run on because of the incompatible CPU type): just click the “info” button,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
, two times immediately after starting the application so that it displays the CPU/battery info panel (screenshot of the latter here).
Note that I've just heavily updated my generic Plantronics Pulsar 590-related article (the current one is the AVRCP-specific, not a generic, one). Make sure you read it for further information on the headphones.
Mr
Menneisyys said:
Try connecting your headphones BEFORE starting PocketPlayer and the whole procedure. I didn't find this necessary, Haesslich, with his equipment, did (or at least it seems he neeeded it)
Click to expand...
Click to collapse
It doesn't work for me.
The funny thing is that I had AVRCP working for one day. That was awhile ago and I understood less than I do now. The only thing that didn't work was FF/REW. Next/Prev track, pause, etc. worked.
I have HT820 headset. I don't get it.
porterx said:
It doesn't work for me.
The funny thing is that I had AVRCP working for one day. That was awhile ago and I understood less than I do now. The only thing that didn't work was FF/REW. Next/Prev track, pause, etc. worked.
I have HT820 headset. I don't get it.
Click to expand...
Click to collapse
Do AVRCP work with MortPlayer / WMP / iPlay with your headphones?
Mr
Menneisyys said:
Do AVRCP work with MortPlayer / WMP / iPlay with your headphones?
Click to expand...
Click to collapse
No, I can't get it to work with any of those. iPlay is a little complicated to use. That may just be me though.
I was going to put a link to the roundup thread but this is it. duh.
I should be able to get this to work. Others have. Why not me? Oh well.
porterx said:
No, I can't get it to work with any of those. iPlay is a little complicated to use. That may just be me though.
I was going to put a link to the roundup thread but this is it. duh.
I should be able to get this to work. Others have. Why not me? Oh well.
Click to expand...
Click to collapse
Making a backup & hard reset? It should work. (At least I think so - I don;thave a HT820 so I'm not absolutely sure, knowing the vast compatibility issues of both A2DP and AVRCP. HT820 users may be out of luck.)
Mr
Menneisyys said:
Making a backup & hard reset? It should work. (At least I think so - I don;thave a HT820 so I'm not absolutely sure, knowing the vast compatibility issues of both A2DP and AVRCP. HT820 users may be out of luck.)
Click to expand...
Click to collapse
I've done a hard reset between now and when it did work. I don't think it was working when I hard reset it but I can't be sure. I'll have to think about that one because setting back up after a hard reset is a PITA and I've never attempted a backup.
porterx said:
I've done a hard reset between now and when it did work. I don't think it was working when I hard reset it but I can't be sure. I'll have to think about that one because setting back up after a hard reset is a PITA and I've never attempted a backup.
Click to expand...
Click to collapse
It's certainly worth using backups - now, all the four major backup apps are fully WM5 (and, more strictly, PPC PE) compliant - see my Backup Bible ( http://www.pocketpcmag.com/blogs/index.php?blog=3&p=1270&more=1&c=1&tb=1&pb=1 ) for more info if interested.
Thank You!
I have the 8525 and the Sony DS HBH970, and have been trying to get something better than WMP so I could use the AVRCP functions and have better sound, bookmarking, etc. I'll give it the 30 day trial period, and may actually have to buy this program...
Using the information here, I am now listening to tunes - using stop/play forward/backward (however, I am used to forward/backward from my bluetooth being an entire track while this goes forward/backward within a track - I'll have to play around to figure that out).
In case anyone else is techno challenged like me, here are the steps that I took:
1) Install the Pocket Player program first. It is an exe file, so you download it to your PC then install via ActiveSync.
2) Then get the Plugin as directed. Download to to PC, then put the file on your device via ActiveSync. Then you need to unzip on your device, putting the file in where you installed Pocket Player as directed.
3) If you have Pocket Player open, close it. Open Pocket Player, tap Menu - More - Options - arrow over the tabs to tap on Plugins - tap WM Plugin - Configure as directed in these instructions.
4) My initial playing would not route to the headset, but it works when you have BT on first, hit the play button to establish the connection, then open Pocket Player, play your song.
Thank you for all of the information! Great article!
--------------------------------------------------------------------------
Making the Pocket Player AVRCP work under WM5
(Big thanks to PPCT / AximSite forum member Haesslich for summarizing it so that I didn’t need to look / experiment with it up myself much.)
1. Get the Conduits WMP Plugin Adapter 1.1 from the plug-in page (I really recommend it if you, for example, want to get FLAC or MOD support for your Pocket Player) (direct link to the download).
2. Unzip gen_wmhost.dll from the archive and put it in the home directory of your installed application ([Storage card name]\Program Files\Conduits\Pocket Player).
3. Go to Menu/More/Options (in 3.0; in 2.8, Menu/Options) and select the Plugins tab (it’ll be on the far right)
4. Single-click “Conduits WM Plugin Adapter”, when the context menu comes up, select “Configure”.
5. Click the “Configure WM plugins to load” button.
6. Under version 2.8, it’ll ask four questions; under 3.0, two. Click “Yes” in all cases.
7. Click OK and restart Pocket Player. Now, remote controlling should work OK.
scharnet said:
Thank you for all of the information! Great article!
Click to expand...
Click to collapse
Thanks
Just read about Core Player 1.1 Mobile (commercial version of TCPMP)...these articles say it has AVRCP.
http://fairdeal.modaco.com/product.asp?id=8905
http://software.pocketnow.com/product.asp?id=8935
However, their own website does not acknowledge AVRCP. http://coreplayer.com/content/view/28/44/
Just curious if anyone knows or has tired it? Would it work on the 8525 running WM5? I really like the Pocket Player, but it does not play AVI videos. Core Player does not offer free trials, so I was trying to find out...thanks!
GSPlayer
For everyone wants to use the GSPlayer with AVRCP:
http://forum.xda-developers.com/showthread.php?t=316730
I´ve developed the app on the universal under WM6, but it SHOULD work with every device under WM5 and WM6.....
If i have the WM_ messages, i could control EVERY media player with this app....
Any feedback is welcome...
Greets,
Thomas
hello,
i have a bluetooth headset philips shb 7100.
The bt-headset paired and connected successful with my device.
But the functions play/pause and back/forward not working.
I can hear music, volume control and the calloptions also working.
Is the reason the widcomm stack in acer neotouch?
There is a solution for this?
OR
knows someone a stereo bt-headset that works with this functions (play/pause,back/for)?
doesn't work for me either
Hi!
I have a motorola HT820, and I can't play/pause/next/previous with it either, all though the headset worked fine with iMate SP5 and HP 614c
The problem seems to be that Acer (or at least the ROMs I'm using) don't support the AVRCP (Audio Video Remote Control Profile).
So until someone figures out a way to include this profile, we're stuck!
/Sifaan
Hello,
sifaan said:
Hi!
The problem seems to be that Acer (or at least the ROMs I'm using) don't support the AVRCP (Audio Video Remote Control Profile).
/Sifaan
Click to expand...
Click to collapse
yes, I read it in the www
I installed the "avrcp agent" (to find here in forum)
Nothing.
What I not understand:
my headset works with the windows media player mobile with this functions, but with no other musicplayer??
(is in the wmp the avrcp support..)
but wmp is not good to use
I am now using jabra bt3030. it works perfectly in AVCRP.
however, the ACVRP funtion only works in WMP default player.
I had tried to use the funtion in pocket music, coreplayer, mortplayer, nitrogen, but all don't work.
Only works in WMP! Don't know why and hope there is a way to solve it. I don't like WMP too.
I find that it now works with WMP, but I'm not sure if it was because I installed AVRCP agent.
(When I was using Rafyvitto's vanilla ROMs, it didn't work even with WMP...)
/Sifaan
News!
pocketplayer 4.1 (no freeware) with the plugin "conduit wm adapter 2.31" (gen_wmhost.dll) works!
The plugin must be configure:
View attachment 285093
Look into the FAQs of S2P on their site. There's a link to a xda-thread where you will find a modified dll which could work with our s200. It disables the hijacking of BT-Signals by the WMP.
I actually would directly the thread, but it's not allowed for new users to post links :-(
Hope it helps...
Breaka84 said:
Look into the FAQs of S2P on their site. There's a link to a xda-thread where you will find a modified dll which could work with our s200. It disables the hijacking of BT-Signals by the WMP.
I actually would directly the thread, but it's not allowed for new users to post links :-(
Hope it helps...
Click to expand...
Click to collapse
This is the link:
http://forum.xda-developers.com/showpost.php?p=4292847&postcount=3
According to this, AVRCP should work with HTC Music Player as well (not just WMP), but in my case it only works with WMP... but let's check it and see...
/Sifaan
I tested s2p with the t-back driver.
no success
olsching said:
I tested s2p with the t-back driver.
no success
Click to expand...
Click to collapse
+1, mine is ACER neotouch S200 most recent acer ROM. Nothing work with my bluetooth headset philips shb 7100 other than the darn useless boring WMP . Sometime I just want to totally give up window mobile and try something else, but I have already invested too much on window mobile medical applications.
Car audio Bluetooth connection not working
hi...
I see many of you already have had some problems with bluetooth connections with this phone...but all of you say that at least can put the WMP working...
I'm trying to connect my S200 to the car audio (sony from 08 Ford Focus) and it's not working...the car audio system doesn't recognize the phone, but te phone says it's connected...
Is there any known bug for this? any way I can workaround this problem?
Tkx
I use Pocket Player, with plug-in 'Conduits WM Adaptor 2.31', checked to 'Intercept/Override WMP', checked to 'BT Remote Control', after that can use A2DP .
I also use PocketMusic, but still not know how to config A2DP .