Active Topics
-
Firefox with Leste (10)
to Maemo 7 / Leste by teroyk - 3 days, 6 hrs ago - more...
|
2013-09-05
, 14:48
|
|
Posts: 141 |
Thanked: 313 times |
Joined on May 2012
@ Czech Republic
|
#552
|
Originally Posted by fuel__2001
Unfortunately the version part is trimmed. Please can you use:
thanks for getting back to me, here is the following info you required.
CSSU version is 21.2011.38-1Smaemo6.1
bluez 4.60-0maemo1.6 Bluetooth tools and daemon
obexd 0.46-1maemo5+0 D-Bus OBEX server
dpkg -l | grep bluez
dpkg -l | grep obex
That also gives you and idea what packages you need to update/upgrade.
Originally Posted by fuel__2001
You should update/upgrade all packages which you have currently installed. I suggest to test just obexd package at first. You could have more troubles with bluez.
whats packages do i need from those links?
It's better to cooperate bluez upgrade steps via IRC if you're unsure (e.g. AFAIK also kerio is using the experimental bluez).
|
|
2013-09-05
, 15:18
|
|
Posts: 141 |
Thanked: 313 times |
Joined on May 2012
@ Czech Republic
|
#553
|
Originally Posted by Android_808
Pairing is purely bluez thing. It shouldn't be related to the obexd.
As stated in the CSSU-T thread just now, pairing seemed to be a little erratic for me so it may have something to do with that. I'll have another stab at it tomorrow as I haven't tried it since pairing in mate-bluetooth.
And you're using stock bluez if I remeber it right.
Originally Posted by Android_808
Strange. Can you please enable bluez and obexd debug in same time and send me the syslog output from the FTP and also map-client?
Decided to take another look, wish I hadn't
...
I've just removed all the bluetooth userland from the laptop and gone back to blueman. Mate was giving a service record not found error on trying to send. Going back to blueman, send results in remote device refused connection. Now even map-client is giving errors.
Also output from "sdptool browse <BTID of phone>" should be useful (e.g. sdptool browse FF:FF:FF:FF:FF:FF - your phone has different BTID for sure)
Can you give me also your /etc/bluetooth/ settings from phone and computer?
However the linux client side of obexftp is simply terrible. I had to patch some packages on RHEL and Fedora to get it working (I have no idea right now where I have it). Right now I'm able to just browse the phone over bluetooth in gnome nautilus. I have to manually mount it
Code:
gvfs-mount obex://[BTID]
BTW the best full bluetooth reset is to stop obexd and bluetoothd. Remove /var/lib/bluetooth/<local BTID>. Restart computer/phone (or just bluetoothd and obexd).
Beware you'll loose all pairing as it's saved there.
Please also describe how you're trying to browse the device.
Last edited by luf; 2013-09-05 at 15:24.
| The Following User Says Thank You to luf For This Useful Post: | ||
|
|
2013-09-05
, 19:35
|
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#554
|
I went out and bought a different bluetooth adaptor for Win PC and laptop to test if is hardware related. Retailer website and driver download site list Vista as supported, product wasn't so it went back.
Managed to pair and browse successfully using cli (bluez-simple-agent & obexfs) so it would seem the problem is with blueman and gvfs. Why pair button and setup wizard have 2 different scenarios is beyond me. I would say that obexfs is actually giving a more reliable connection than any other method has been for a long long time.
GVFS code you mentioned gives:
I need to do a little more digging, map-client is giving a dbus noreply error at the moment all the time.
Managed to pair and browse successfully using cli (bluez-simple-agent & obexfs) so it would seem the problem is with blueman and gvfs. Why pair button and setup wizard have 2 different scenarios is beyond me. I would say that obexfs is actually giving a more reliable connection than any other method has been for a long long time.
GVFS code you mentioned gives:
Code:
gvfs-mount obex://[EC:9B:5B:93:22:3C] Error mounting location: Connection to the device lost
|
|
2013-09-08
, 14:44
|
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#555
|
Post below duplicated
Last edited by Android_808; 2013-11-16 at 15:34.
Last edited by Android_808; 2013-11-16 at 15:34.
|
|
2013-09-08
, 14:46
|
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#556
|
Managed to get map-client output back to its previous state of an empty listing. I had to edit a reference to a non existant plugdev group in 60-openobex.rules to TAG+="uaccess".
sdptool output seems to look ok:
gvfs-mount was giving connection refused errors at one point but has gone back to connection lost. obexfs method still working fine, but I do get an error message about being unable to preserve attributes whilst copying to the phone using Thunar.
Should I be looking for anything particular in /etc/bluetooth/*? I'm still leaning towards a dbus/gvfs issue on the laptop side. All I keep seeing is disconnect or cancel messages but no reason behing them.
I've managed to get ModemManager/NetworkManager working again, I'm posting this whilst tethered to the N900 over bluetooth from the same laptop I'm having the other issues with.
If anyone can recommend a decent USB bluetooth adaptor (that works for Linux and Vista) I'd like to try setting up a VM on a Windows PC using a) Archliunx to see if it is device specific or b) another distro to see if it is only Arch.
sdptool output seems to look ok:
Code:
Service Name: Headset Audio GatewayService RecHandle: 0x10000
Service Class ID List:
"Headset Audio Gateway" (0x1112)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 12
Profile Descriptor List:
"Headset" (0x1108)
Version: 0x0102
Service Name: Hands-Free Audio GatewayService RecHandle: 0x10001
Service Class ID List:
"Handsfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 13
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0105
Service Name: Audio SourceService RecHandle: 0x10002
Service Class ID List:
"Audio Source" (0x110a)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 25
"AVDTP" (0x0019)
uint16: 0x102
Profile Descriptor List:
"Advanced Audio" (0x110d)
Version: 0x0102
Service Name: AVRCP TGService RecHandle: 0x10003
Service Class ID List:
"AV Remote Target" (0x110c)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x103
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0100
Service Name: AVRCP CTService RecHandle: 0x10004
Service Class ID List:
"AV Remote" (0x110e)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x103
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0100
Service Name: Dial-Up NetworkingService RecHandle: 0x10005
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
Service Name: Nokia OBEX PC Suite ServicesService RecHandle: 0x10006
Service Class ID List:
UUID 128: 00005005-0000-1000-8000-0002ee000001
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 24
"OBEX" (0x0008)
Profile Descriptor List:
"" (0x00005005-0000-1000-8000-0002ee000001)
Version: 0x0100
Service Name: Object Push serverService RecHandle: 0x10007
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 9
"OBEX" (0x0008)
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100
Service Name: File Transfer serverService RecHandle: 0x10008
Service Class ID List:
"OBEX File Transfer" (0x1106)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 10
"OBEX" (0x0008)
Profile Descriptor List:
"OBEX File Transfer" (0x1106)
Version: 0x0100
Service Name: Phonebook Access serverService RecHandle: 0x10009
Service Class ID List:
"Phonebook Access - PSE" (0x112f)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 15
"OBEX" (0x0008)
Profile Descriptor List:
"Phonebook Access" (0x1130)
Version: 0x0100
Service Name: Message Access serverService RecHandle: 0x1000a
Service Class ID List:
"Message Access - MAS" (0x1132)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 16
"OBEX" (0x0008)
Profile Descriptor List:
"Message Access" (0x1134)
Version: 0x0100
Service Name: IRMC Sync serverService RecHandle: 0x1000b
Service Class ID List:
"IrMC Sync" (0x1104)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 14
"OBEX" (0x0008)
Profile Descriptor List:
"IrMC Sync" (0x1104)
Version: 0x0100
Service Name: SyncML ClientService RecHandle: 0x1000c
Service Class ID List:
UUID 128: 00000002-0000-1000-8000-0002ee000002
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 25
"OBEX" (0x0008)
Profile Descriptor List:
"" (0x00000002-0000-1000-8000-0002ee000002)
Version: 0x0100
Service Name: Nokia SyncML ServerService RecHandle: 0x1000d
Service Class ID List:
UUID 128: 00005601-0000-1000-8000-0002ee000001
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 26
"OBEX" (0x0008)
Profile Descriptor List:
"" (0x00005601-0000-1000-8000-0002ee000001)
Version: 0x0100
Should I be looking for anything particular in /etc/bluetooth/*? I'm still leaning towards a dbus/gvfs issue on the laptop side. All I keep seeing is disconnect or cancel messages but no reason behing them.
I've managed to get ModemManager/NetworkManager working again, I'm posting this whilst tethered to the N900 over bluetooth from the same laptop I'm having the other issues with.
If anyone can recommend a decent USB bluetooth adaptor (that works for Linux and Vista) I'd like to try setting up a VM on a Windows PC using a) Archliunx to see if it is device specific or b) another distro to see if it is only Arch.
|
|
2013-11-10
, 10:32
|
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#557
|
I'm finally able to establish a stable connection the phone, at the cost of being able to transfer files at the moment since switching over to bluez 5.9 and now 5.10 on the laptop along with an updated pulseaudio. Pulseaudio support appears to be what was causing the disconnects.
At present I'm managing the connection using bluetoothctl -a. Has anyone got any experience using the new obexctl test app in bluez 5.10 so I can test MAP/PBAP? All my attempts at the moment result in client proxy not available.
At present I'm managing the connection using bluetoothctl -a. Has anyone got any experience using the new obexctl test app in bluez 5.10 so I can test MAP/PBAP? All my attempts at the moment result in client proxy not available.
|
|
2013-12-26
, 18:43
|
|
Posts: 2 |
Thanked: 0 times |
Joined on Feb 2012
|
#558
|
hi, any news about getting obexd 0.46 working inside N9 ? I have obexd version 0.42 but there is no MAP support :-(. I can try to build myself but i have no idea how to start.
|
|
2014-01-14
, 20:45
|
|
Posts: 45 |
Thanked: 36 times |
Joined on Jan 2010
|
#559
|
I'm having problem getting MAP and PBAP to work... I used the manual installation from the wiki page, but when I test it, MAP appears to be working, however it just shows empty folder as if there are no messages and PBAP responds with "Forbidden"...
Is there anyone around who got it working? I didn't do any debug yet, I'm going to do it tomorrow when I'll have more time, but I'm not sure if it will help me.
Thanks
Is there anyone around who got it working? I didn't do any debug yet, I'm going to do it tomorrow when I'll have more time, but I'm not sure if it will help me.
Thanks
| The Following User Says Thank You to JoHnY For This Useful Post: | ||
|
|
2016-01-28
, 00:12
|
|
Posts: 141 |
Thanked: 313 times |
Joined on May 2012
@ Czech Republic
|
#560
|
Originally Posted by JoHnY
We found the root cause on IRC channel. The problem was that older PR used different ID in rtcom.
I'm having problem getting MAP and PBAP to work... I used the manual installation from the wiki page, but when I test it, MAP appears to be working, however it just shows empty folder as if there are no messages and PBAP responds with "Forbidden"...
Is there anyone around who got it working? I didn't do any debug yet, I'm going to do it tomorrow when I'll have more time, but I'm not sure if it will help me.
Thanks
It started to work with patched rtcom-eventlogger-async.
| The Following 2 Users Say Thank You to luf For This Useful Post: | ||
BTW I need whole package name/version unfortunately dpkg -l obexd is cutting it
I'm sorry that I gave not the best advice last time.