Active Topics
-
Maemo repository (47)
to Community by viniciuspaes - 1 day, 20 hrs ago - more...
| The Following User Says Thank You to luf For This Useful Post: | ||
|
2013-02-02
, 21:50
|
|
Posts: 141 |
Thanked: 313 times |
Joined on May 2012
@ Czech Republic
|
#502
|
Originally Posted by don_falcone
Any result with your tests?
Hell no, not that incoming / outgoing COM port thingy again. I fought with that when i had my N73, using Symbian OPM. Will test...
Originally Posted by don_falcone
It's quiet long way to home
Regarding the root directory: Using Widcomm 6.5 i have the ability to browse for the actual directory where the file(s) to be send should be stored. But folder discovery isn't working too. I've made screenshots a while ago; will attach them when back home.
I hope you're fine.However don_falcone can you please also try to test the bluez-4.99 + obexd-0.46 with stock kernel (neither kernel-cssu nor KP)? (EDITED: it seems the blues-4.99 problem is somewhere else as merlin1991 reproduced it with stock kernel - but the hope die as the last one)
Just in case it's similar problem with pinochio one. However it seems I have to take a look into bluez kernel part
Last edited by luf; 2013-02-02 at 21:57.
|
|
2013-02-02
, 22:03
|
|
Posts: 1,523 |
Thanked: 1,997 times |
Joined on Jul 2011
@ not your mom's FOSS basement
|
#503
|
RFCOMM without L2CAP? Isn't RFCOMm supposed to work ontop of L2CAP?
EDIT: :P Yes, it was also at least a full month in between. I could only create an outgoing port (which makes no difference), an incoming can only be created if something "special" runs on the mobile side - i experienced this with my old N73. Symbian OPM's sync agent had to run, then Windows would discover this "service" / "port" and let you create an incoming COM port. Otherwise, you could not choose a device first, which is obligatory.
Last edited by don_falcone; 2013-02-02 at 22:08.
EDIT: :P
Yes, it was also at least a full month in between. I could only create an outgoing port (which makes no difference), an incoming can only be created if something "special" runs on the mobile side - i experienced this with my old N73. Symbian OPM's sync agent had to run, then Windows would discover this "service" / "port" and let you create an incoming COM port. Otherwise, you could not choose a device first, which is obligatory.
Last edited by don_falcone; 2013-02-02 at 22:08.
| The Following User Says Thank You to don_falcone For This Useful Post: | ||
|
|
2013-02-02
, 22:15
|
|
Posts: 141 |
Thanked: 313 times |
Joined on May 2012
@ Czech Republic
|
#504
|
Originally Posted by don_falcone
Maybe it's true but there is support in new obexd to run OPP just on top of L2CAP (which fails for pinochio). And OPP on top RFCOMM is working.
RFCOMM without L2CAP? Isn't RFCOMm supposed to work ontop of L2CAP?
Originally Posted by don_falcone
I'm affraid it's due to obexd-0.46 is offering also just L2CAP transport ... I'll try to disable it. I hope I'll upload the experimental package today or tomorrow (but it's not what I want at the end).
I could only create an outgoing port (which makes no difference), an incoming can only be created if something "special" runs on the mobile side - i experienced this with my old N73. Symbian OPM's sync agent had to run, then Windows would discover this "service" / "port" and let you create an incoming COM port. Otherwise, you could not choose a device first, which is obligatory.
|
|
2013-02-02
, 22:44
|
|
Posts: 141 |
Thanked: 313 times |
Joined on May 2012
@ Czech Republic
|
#505
|
@pinochio, don_falcone: please test stock kernel first with the official obexd-0.46.
After that can you also try kernel-power (or whatever kernel are you using now - before going back to the stock kernel) with this dev obexd package(s)?
This experimental package(s) should fix the Win -> N900 direction. However please test both direction and give me the result.
FYI I disabled plain L2CAP support for OPP and FTP profiles for server side (also known as GOEP 2.0 - faster transfer).
Last edited by luf; 2013-02-03 at 03:00. Reason: I forget to decrease also version in SDP records
After that can you also try kernel-power (or whatever kernel are you using now - before going back to the stock kernel) with this dev obexd package(s)?
This experimental package(s) should fix the Win -> N900 direction. However please test both direction and give me the result.
FYI I disabled plain L2CAP support for OPP and FTP profiles for server side (also known as GOEP 2.0 - faster transfer).
Last edited by luf; 2013-02-03 at 03:00. Reason: I forget to decrease also version in SDP records
|
|
2013-02-03
, 20:07
|
|
Posts: 126 |
Thanked: 160 times |
Joined on Aug 2012
|
#506
|
I did reflash, I have obexd 0.18 and stock kernel, and I can look on the N900 with my laptop. I have installed automatically Bluetooth-services as pictured, not installed is one a service, it may pose a conflict?
Last edited by pinochio; 2013-02-03 at 21:52.
Last edited by pinochio; 2013-02-03 at 21:52.
| The Following User Says Thank You to pinochio For This Useful Post: | ||
|
|
2013-02-03
, 20:49
|
|
Posts: 1,523 |
Thanked: 1,997 times |
Joined on Jul 2011
@ not your mom's FOSS basement
|
#507
|
...seems i should switch back from patching CM ROMs to Maemo...
In comparison; here are my hardware & services tabs under obexd0.46 ; i'll test in next minutes if posted packages bring a difference.
Last edited by don_falcone; 2013-02-03 at 21:27.
In comparison; here are my hardware & services tabs under obexd0.46 ; i'll test in next minutes if posted packages bring a difference.
Last edited by don_falcone; 2013-02-03 at 21:27.
| The Following User Says Thank You to don_falcone For This Useful Post: | ||
|
|
2013-02-03
, 21:16
|
|
Posts: 141 |
Thanked: 313 times |
Joined on May 2012
@ Czech Republic
|
#508
|
Originally Posted by pinochio
1) Please paste here also the kernel version (dpkg -l kernel).
I did reflash, I have obexd 0.18 and stock kernel, and I can look on the N900 with my laptop. I have installed automatically Bluetooth-services as pictured, not installed is one a service, it may pose a conflict?
Keep the stock kernel and install please obexd-0.46 (if it's still working or not - from http://merlin1991.at/~luf/obexd/obex...ssu1_armel.deb)
I need to know if stock kernel with obexd-0.46 is working well or has the issue.
2) As the second step let's try install cssu-thumb (or whatever you prefer) and try obexd attached in my previous post (dev1).
I'm on #maemo-ssu if you need more support.
Last edited by luf; 2013-02-03 at 21:23.
|
|
2013-02-03
, 21:21
|
|
Posts: 141 |
Thanked: 313 times |
Joined on May 2012
@ Czech Republic
|
#509
|
Originally Posted by don_falcone
1) let's try you current kernel + bluez-4.99 + obexd-0.46
In comparison; here are my hardware & services tabs under obexd0.46 ; i'll test in next minutes if posted packages bring a difference.
(please report here the kernel you're using: dpkg -l | grep kernel )
2) let's try stock kernel + bluez-4.99 + obexd-0.46
(please also report the kernel: dpkg -l kernel )
|
|
2013-02-03
, 21:29
|
|
Posts: 1,523 |
Thanked: 1,997 times |
Joined on Jul 2011
@ not your mom's FOSS basement
|
#510
|
EDIT: At least both directory browsing during "send files to the (N900) computer" and actually sending something over works now. In direction of N900 -> Win7, same old situation.
This is with the above attached obexd 0.46 dev packages, bluez 4.99, and KP52 (CSSU3 works too, but i'm not able to boot into stock kernel):
Last edited by don_falcone; 2013-02-03 at 21:41.
This is with the above attached obexd 0.46 dev packages, bluez 4.99, and KP52 (CSSU3 works too, but i'm not able to boot into stock kernel):
Last edited by don_falcone; 2013-02-03 at 21:41.
| The Following User Says Thank You to don_falcone For This Useful Post: | ||
Can you please try obexd-0.46 with stock kernel?
It seems to me that the problem is in L2CAP transport. Old obexd doesn't support L2CAP transport (just RFCOMM). And I find some patch related to the L2CAP in kernel-power.
Unfortunately I'm not able to install so old cssu-stable to check it.