|
2010-07-28
, 22:17
|
|
Posts: 597 |
Thanked: 490 times |
Joined on Dec 2009
@ Germany
|
#42
|
/usr/lib/obex/obexd --debug --opp --ftp --pcsuite --pbap --symlinks --root .obex-root --root-setup /usr/bin/obex-root-setup --capability !/usr/bin/gen-obex-capability.sh
/usr/lib/obex/obexd --nodaemon --opp --ftp --pcsuite --pbap --symlinks --root .obex-root --root-setup /usr/bin/obex-root-setup
|
2010-07-29
, 06:47
|
Posts: 197 |
Thanked: 101 times |
Joined on Dec 2009
@ Netherlands
|
#43
|
The Following 2 Users Say Thank You to mirakels For This Useful Post: | ||
|
2010-07-29
, 07:54
|
Posts: 6 |
Thanked: 0 times |
Joined on Mar 2010
|
#44
|
/usr/lib/obex/obexd --nodaemon --opp --ftp --pcsuite --pbap --symlinks --root .obex-root --root-setup /usr/bin/obex-root-setup
|
2010-07-29
, 08:26
|
|
Posts: 597 |
Thanked: 490 times |
Joined on Dec 2009
@ Germany
|
#45
|
I think the most important aspect is to make sure pcsuite connection works fine with the obexd from hschmitt.
|
2010-07-29
, 10:32
|
Posts: 197 |
Thanked: 101 times |
Joined on Dec 2009
@ Netherlands
|
#46
|
The Following User Says Thank You to mirakels For This Useful Post: | ||
|
2010-07-29
, 10:33
|
Posts: 197 |
Thanked: 101 times |
Joined on Dec 2009
@ Netherlands
|
#47
|
ho do you try to start this obexd service? If i give this commandit says to me "Cant register with session bus". i am under root.Code:/usr/lib/obex/obexd --nodaemon --opp --ftp --pcsuite --pbap --symlinks --root .obex-root --root-setup /usr/bin/obex-root-setup
Also from where gets this original obexd started? i mean after reboot it stills runs for me without pbap, maybe i should change it from somewhere else.
The Following User Says Thank You to mirakels For This Useful Post: | ||
|
2010-07-29
, 11:40
|
|
Posts: 597 |
Thanked: 490 times |
Joined on Dec 2009
@ Germany
|
#48
|
the problem is not the --debug or --nodeamon switches.
The second versions also ommits the --capability switch (and its argument).
Apperantly the capabilitties are needed by pc-suite. I guess it tells pc-suit all the relevant info about your n900 (serial number, software version etc. )
Just try to run the /usr/bin/gen-obex-capability.sh script from an x-terminal and see for yourself what info will be passed
/usr/lib/obex/obexd --nodaemon --opp --ftp --pcsuite --pbap --symlinks --root .obex-root --root-setup /usr/bin/obex-root-setup --capability !/usr/bin/gen-obex-capability.sh
|
2010-07-29
, 12:50
|
Posts: 6 |
Thanked: 0 times |
Joined on Mar 2010
|
#49
|
you probably still have another obexd process running. Check it out with the 'ps' command and if so use 'killall obexd' to stop it before starting a new one.
|
2010-07-29
, 13:55
|
Posts: 49 |
Thanked: 23 times |
Joined on Oct 2009
@ Oulu, Finland
|
#50
|
About your new obexd:
In order to test this properly I wanted an environment with working PC Suite connection to begin with.
Thus I downgraded my N900 to original state and reconnected it to my newly installed Win7 laptop - just to realize Win7 is missing some Bluetooth drivers for N900 :
Device Manager lists 2 "Peripheral Bluetooth" devices as unknown and in Bluetooth Devices -> N900 -> Properties -> Services both "Filetransfer (obex)" and "Objectpush (obex)" are unchecked.
So far I was not able to find those missing drivers/solve this problem or get PC Suite to work via Bluetooth even with original obex
Therefore I guess I am not able to help testing PC Suite connection via Bluetooth at the moment
However, USB Cable connection was working after downgrade, but
when reconnecting with your new obexd PC Suite says "Windows now installs PC Connectivity Cable Drivers, please wait.." and stays like that forever
How can I give you some debugging information?
/var/log/syslog does not exist on my N900...
Edit: Stupid me, of course I dont have syslog - forgot to install sysklogd
Ok, installed syslogd and restarted obex with this command (as posted by mirakles):
Last edited by Reflektorfalke; 2010-07-28 at 20:09.