Problem could be solved by executing:
aclocal automake -a autoconf
Make sure all needed development packages have installed on Your system. For example, if compiler could not find bluetooth.h header file, You need to install development package for Bluez. To determine which package is absent is not so hard. Just remember which file was not found by compiler, then open http://rpm.pbone.net/ or http://rpmfind.net and try to search package You need to install.
In principle it is possible to support any application with anyRemote. There are several ways to do that:
Be sure You have used Server-mode configuration file. Be sure the page and inquiry scan enabled on bluetooth interface (this could be done with command hciconfig hci0 piscan)
Well, different phones works differently, so it could happens. Try to upgrade to the latest version of anyRemote. Inspect $HOME/.anyRemote/*anyremote.log file to determine the possible reasons of undesirable behavoiur. (Make sure You set Log=true and Debug=true in cfg.file You use). Also, make sure what version of Java Client is the same as version of anyRemote.
Drop me a letter and i try to help. Please, describe the problem, specify phone model and version of distro You have. Also attach to the letter full log file ($HOME/.anyRemote/*anyremote.log.*) as well as terminal output of anyRemote.
No. AnyRemote does not use Bemused server. It could emulate it to some extent instead. See for details.
This could happen if java client tries to connect to anyRemote at the moment when bluetooth browsing process is active. In normal situation KDEBluetooth or anyRemote GUI tries to find bluetooth devices around from time to time. Unfortunately this could prevents java client to connect to anyRemote. You can just wait a bit and connect again.
Definitely. Send me a letter with short description and attached cfg.file. I'll add it to the next release of anyRemote. One note: Your cfg.file should works with both anyRemote/kAnyRemote and should not call any external custom made scripts.