- When i run configure, it fails with the error: configure: error: cannot find install-sh or install.sh in . ./.. ./../.. message
- I have compilation errors. What can i do ?
- I run anyRemote and got the following: ERROR: Fails in init_cfg()
- I can run anyRemote but something doesn't work ...
- Does anyRemote support application XXX?
- J2ME client can not find PC with anyRemote
- Seems anyRemote works ... but something is going wrong. How can i fix it?
- I have tried all suggestions ... but it still doesn't work. What else can I do?
- It is impossible to control sound volume with some configuration files.
- Should I run Bemused server to make anyRemote work?
- Sometimes J2ME client can not connect to anyRemote
- I've created a configuration file for application XXX. Can I share it with other anyRemote users?
- I've got an error when trying to connect to the phone using cu
- kAnyremote crashes with python: xcb_lock.c:33: _XCBUnlockDisplay ... message
- I have Nokia Series40 phone and can not upload J2ME client to it
- I have Nokia Symbian phone got openConnection Exeption java.io.IOExeption SymbianOS error=-1 : General: System error message
- J2ME client can not find PC with anyRemote (Bluez issue)
- How can i add some phone-specific initialization command ?
- Some application did not woks under KDE4. Why ?
- Does anyRemote J2ME client supports WinMobile devices ?
- I've got xargs: xargs.c:445: main: Assertion bc_ctl.arg_max <= (131072-2048) error when browse files.
- I see no icons in gAnyRemote menu items. How to fix it ?
- I see no gAnyRemote/kAnyRemote tray icon in Unity. How to fix it ?
- Can not establish connection in KDE4
When i run configure, it fails with the error: configure: error: cannot find install-sh or install.sh in . ./.. ./../.. message
Problem can be solved by executing:
aclocal automake -a autoconf
Make sure all needed development packages are installed on your system. For example, if your compiler can not find bluetooth.h header file, you need to install development packages for Bluez. To determine which package is absent is not so hard. Just remember which file was not found by compiler, then open rpm.pbone.net or rpmfind.net and try to search the package you need to install.
you have to specify a configuration file which will be used by anyRemote:
anyremote -f /path/to/configuration/file
Try to localize problem. Do not use GUI frontends and run anyRemote from command line with -log option set. Do not test configuration files one by one. Just choose the simplest one, like kdialog.cfg and inspect what does work and what does not. Look at $HOME/.anyRemote/anyremote.log for error messages.
In principle it is possible to support almost any application with anyRemote. There are several ways to do that:
- Some appication (for example Tvtime, Xdtv, Xmms) have command line management utility.
- KDE4 and Gnome applications can supports D-BUS interface.
- KDE3 applications supports DCOP command-line interface.
- Finally it is possible to manage application with keyboard and mouse emulation. Use Emulate(...) command to do that. If you are not satisfied with Emulate(...) command it is possible to use external software like XAutomation
Be sure you are using a Server-mode configuration file. Be sure the page and inquiry scan are enabled on bluetooth interface (this could be done with command hciconfig hci0 piscan). Also see #17
Well, different phones works differently, so it can happen. Try to upgrade to the latest version of anyRemote. Inspect <home>/.anyRemote/*anyremote.log files to determine the possible reasons of undesirable behavoiur. Make sure you have run anyRemote with
command line parameter. Also, make sure that the version of the J2ME client is the same as the version of anyRemote.
Send an e-mail to firstname.lastname@example.org. 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.
See Tips & Tricks page.
This could happen if J2ME 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 prevent the J2ME client to connect to anyRemote. You can just wait a bit and try to connect again.
Definitely. Send a letter with a short description and attached configuration file. We'll add it to the next release of anyRemote.
cu -l /dev/rfcomm0 -s 19200 cu: open (/dev/rfcomm0): Connection refused cu: /dev/rfcomm0: Line in use
Bluez 4.X and newer does not allow to directly connect to RFCOMM device. You need to update anyRemote to the version 5.4 or newer to fix this issue.
Update to the version v5.1 or newer.
It is impossible to upload JAR files using OBEX to some old Nokia Series40 phones (6021, 6230i). It needs to use Gammu or Nokia tool suite (works under MS Windows).
I have Nokia Symbian phone got openConnection Exeption java.io.IOExeption SymbianOS error=-1 : General: System error message
The problem is still under investigations. Try to reinstall J2ME Client to the phone's memory (not to the memory card !!!). If You have entered bluetooth address directly, be sure it looks like btspp://0008F4163038:19 (no spaces and only one semicolon). Send report to anyRemote
sdptool browse local
If You see something like:
Browsing FF:FF:FF:00:00:00 ... Service Search failed: Success
then Your have got it. Mandriva 2008.1 and Suse 11.0 contains this issue.
A workaround: instead of search in J2ME Client, enter bluetooth address of PC directly.
Create file $HOME/.anyRemote/hook_connect and put all needed commands there. These commands will be added to the end of (Connect) command sequence.
KDE4 uses D-BUS instead of DCOP for interprocess communication. As a result, application which were rewritten for KDE4 (like Amarok2, KsCD and Gwenview) will not work with old configuration files, created for KDE3 and it needs to use new version of configuration file designed for use with KDE4.
It depends on Midlet Manager You use. The best variant is Esmertec Jeodek. anyRemote J2ME client runs flawlessly under it.
You can try (but it is not recommended) Esmertec's JBed. In this case it needs to use only anyRemote-nojsr82.jar. But anyway, there are exist a couple of serious issues under JBed. Seems they are related to Jbed itself.
These is a list of known issues under JBed:
- It needs to press "Connect" twice to connect.
- After disconnecting J2ME client could hangs.
- Sometimes icons is not shown.
- Touchscreen does not works.
It seems anyRemote works better with older versions of JBed,than with newer ones.
All existing Midlet Managers does not supports JSR-82, so it is possible to use Wi-Fi connection only.
I've got xargs: xargs.c:445: main: Assertion bc_ctl.arg_max "<= (131072-2048) error when browse files.
There is a bug in xargs. Just google around that error message. To fix it it needs to update findutils package.
See Tips section here.
gsettings set com.canonical.Unity.Panel systray-whitelist "['all']"
Possible it needs to switch off BlueDevil integration for your device in KDE.