Errata : that'd be to thr main UI ofc :)
On Wednesday, July 17, 2019, Tone Kastlunger
wrote:
> Yes so, it appears that the buteo-sync-plugin relies on bluez4 heavily
too.
> About the ui, it is possible, although it remains to be seen how, as the
contribution flow to the main uk is a bit unclear (
Yes so, it appears that the buteo-sync-plugin relies on bluez4 heavily too.
About the ui, it is possible, although it remains to be seen how, as the
contribution flow to the main uk is a bit unclear (and silica is not fully
open).
On Tuesday, July 16, 2019, deloptes wrote:
> Tone Kastlunger wro
Tone Kastlunger wrote:
> PS found this one :
>
> https://wiki.merproject.org/wiki/Sync_plugins
>
Yes I read this. It is history and it is outdated as of "Sync with
libsyncml". Libsyncml does not exist anymore (it died may be 6-7y ago), but
it has good information. This is why I use syncevolutio
PS found this one :
https://wiki.merproject.org/wiki/Sync_plugins
On Tue, Jul 16, 2019 at 9:42 PM Tone Kastlunger
wrote:
> About the syncmlserver;
> which command line options have you used?
>
> On Tue, Jul 16, 2019 at 8:24 PM deloptes wrote:
>
>> Tone Kastlunger wrote:
>>
>> > So so far I hav
About the syncmlserver;
which command line options have you used?
On Tue, Jul 16, 2019 at 8:24 PM deloptes wrote:
> Tone Kastlunger wrote:
>
> > So so far I have a patch for buteo-syncfw;
> > and you mentioned you had to change something in buteo-sync-plugins too;
> > is there a patch available
Tone Kastlunger wrote:
> So so far I have a patch for buteo-syncfw;
> and you mentioned you had to change something in buteo-sync-plugins too;
> is there a patch available for that too?
Not yet, I'll need more time. It is still very rough and not working at all.
But w.r.t buteo-syncfw, you see i
>I do not have the time to work much on this (unfortunately, because of
>priorities). I have 1-2h a day and my goal for now is to understand the
>system and what exactly needs to be corrected.
That's totally ok :)
and I think what has been done so far is great!
So so far I have a patch for buteo-
Tone Kastlunger wrote:
> Yes, so to clarify:
> I have rebuilt openobex, buteo-syncfw and buteo-syncml (against bluez5)
> and installed all the rpm's on my xperia;
> I have then reloaded the systemd config, and started msyncd ;
>
> at this point, sdptool browse from my laptop over to the paired x
Tone Kastlunger wrote:
> I guess im missing something?
buteo-sync-plugins
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Yes, so to clarify:
I have rebuilt openobex, buteo-syncfw and buteo-syncml (against bluez5)
and installed all the rpm's on my xperia;
I have then reloaded the systemd config, and started msyncd ;
at this point, sdptool browse from my laptop over to the paired xperia
still seems
to not see any SYN
Tone Kastlunger wrote:
> Correction; found it.
> Apologies for the spamming.
OK, but this is exactly the part of the exercise. Much of this is still
written to work with bluez4. Since Xperia X is using bluez5 this does not
work out of the box.
So this patch makes the syncfw work with bluez5. How
Correction; found it.
Apologies for the spamming.
On Mon, Jul 15, 2019 at 8:22 PM Tone Kastlunger
wrote:
> So after building openobex from the mer repo (10 years old :) ),
> it seems syncml client is also not available (and not present on the mer
> repos).
> deloptes, where did you get the sourc
So after building openobex from the mer repo (10 years old :) ),
it seems syncml client is also not available (and not present on the mer
repos).
deloptes, where did you get the sources from?
Best,
tk
On Mon, Jul 15, 2019 at 7:37 PM Tone Kastlunger
wrote:
> Hello;
> so some progress; I installe
Hello;
so some progress; I installed the built rpm (with the patch deloptes
provided) succesfully;
however, sdptool didnt find anything related to SYNCML.
Upon further checks, it appears the syncml client wasnt installed on my
xperia, so I attempted to install it, however:
[root@Sailfish nemo]# z
Yep;
missed that one thanks!
Noticed spec file doesnt mention this; can I get the rpmbuilder to choose
the "replace" option by default?
On Mon, Jul 15, 2019 at 2:20 PM deloptes wrote:
> Tone Kastlunger wrote:
>
> > [mersdk@SailfishSDK build]$ mb2 -t SailfishOS-3.0.3.9-armv7hl -s
> > ../rpm/bute
Martin Kampas wrote:
> It is not the '-d' flag that fixes it - this is a shortcut for
> '--enable-debug' :) Just the path to the source directory '..' is enough.
:) yes indeed you are right :) sorry for that confusion
___
SailfishOS.org Devel mailing l
Hi,
It is not the '-d' flag that fixes it - this is a shortcut for '--enable-debug'
:) Just the path to the
source directory '..' is enough.
BR,
Martin
On pondělí 15. července 2019 13:20:40 CEST deloptes wrote:
> Tone Kastlunger wrote:
> > [mersdk@SailfishSDK build]$ mb2 -t SailfishOS-3.0.3.9
Tone Kastlunger wrote:
> [mersdk@SailfishSDK build]$ mb2 -t SailfishOS-3.0.3.9-armv7hl -s
> ../rpm/buteo-syncfw-qt5.spec build
when you try to build from within a build directory, you have to specify the
root directory with -d flag
I use following
mb2 -t SailfishOS-3.0.2.8-armv7hl -s ../rpm/b
Hi,
> updated the sdk to the latest & greates and I cant build :
>
> [mersdk@SailfishSDK build]$ mb2 -t SailfishOS-3.0.3.9-armv7hl -s
> ../rpm/buteo-syncfw-qt5.spec build
>
> [...]
> Usage: /usr/lib/qt5/bin/qmake [mode] [options] [files]
>
> [...]
This may be because there are multiple .pro f
So even more fun;
updated the sdk to the latest & greates and I cant build :
[mersdk@SailfishSDK build]$ mb2 -t SailfishOS-3.0.3.9-armv7hl -s
../rpm/buteo-syncfw-qt5.spec build
The following 17 NEW packages are going to be installed:
bluez bluez-configs-mer bluez-libs doxygen fdupes glib2-deve
Tone Kastlunger wrote:
> qmcebatterystatus.h
/srv/mer/targets/SailfishOS-3.0.2.8-armv7hl/usr/include/mce-qt5/qmcebatterystatus.h
is in libmce-qt5-devel
Strange because I did not install it manually
regards
___
SailfishOS.org Devel mailing list
To
https://git.sailfishos.org/mer-core/libmce-qt/blob/master/lib/include/qmcebatterystatus.h
On 13/07/2019 00:30, Tone Kastlunger wrote:
Btw, your patch is not building on my sdk:
Where does the #include come from?
As you can see, I should have everything installed in the target for
it to build;
PS : oh and this is against the latest buteo repo version :)
On Sat, Jul 13, 2019 at 12:30 AM Tone Kastlunger
wrote:
> Btw, your patch is not building on my sdk:
> Where does the #include come from?
> As you can see, I should have everything installed in the target for it to
> build;
> but the
Btw, your patch is not building on my sdk:
Where does the #include come from?
As you can see, I should have everything installed in the target for it to
build;
but the file in question does not show up (see find command below).
Logs:
--
[SB2 sdk-bu
Yes,
for an example, the pcsuite (as mentioned in the previous mail) is not
included in the (original) build configuration
of bluez5, as the configure is missing the --enable-experimental.
Now before we go all heroish and open pandora's box, i'd say we could try
to track down the source pack of the
Tone Kastlunger wrote:
>> IMO it is missing OBEX File Transfer Profile.
> Is this profile supposed to be used for non-file data (i.e. contacts) as
> well?
> There seems to be some file-related test cases in the repo of bluez5
>
> https://git.sailfishos.org/mer-core/bluez5/blob/master/test/list-f
Thanks for the links!
As said, im really not familiar with
the syncml stack!
One thing i noticed from them:
>set the username and password for synchronization on your phone to be empty
hows this implemented on the sfos side?
On Friday, July 12, 2019, deloptes wrote:
> forgot to paste this
>
>
forgot to paste this
https://wiki.merproject.org/wiki/Buteo/SyncML
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Tone Kastlunger wrote:
> and me again;
> it appears the PC Suite plugin is marked as EXPERIMENTAL on the make
> files; needless to say, this EXPERIMENTAL option is not enabled by the
> configure of the bluez5 project.
>
>
>
Cool! thank you for researching and in the sense sharing some work
and me again;
it appears the PC Suite plugin is marked as EXPERIMENTAL on the make files;
needless to say, this EXPERIMENTAL option is not enabled by the configure
of the bluez5 project.
On Fri, Jul 12, 2019 at 12:00 AM Tone Kastlunger
wrote:
> ..and more stuff can be found from the obexd/
..and more stuff can be found from the obexd/plugins folder:
https://git.sailfishos.org/mer-core/bluez5/tree/master/obexd/plugins
On Thu, Jul 11, 2019 at 11:42 PM Tone Kastlunger
wrote:
> PS from here:
>
>
> https://git.sailfishos.org/mer-core/bluez5/blob/master/test/get-obex-capabilities
> it
PS from here:
https://git.sailfishos.org/mer-core/bluez5/blob/master/test/get-obex-capabilities
it seems you can get some obex capabilities (although I have yet to be able
to do so);
also, have a look at /usr/libexec/obexd-wrapper (shell script); it allows
for tracing of obexd activity apparentl
> IMO it is missing OBEX File Transfer Profile.
Is this profile supposed to be used for non-file data (i.e. contacts) as
well?
There seems to be some file-related test cases in the repo of bluez5
https://git.sailfishos.org/mer-core/bluez5/blob/master/test/list-folders
On Thu, Jul 11, 2019 at 9:4
Tone Kastlunger wrote:
> It seems obexd might have some issues with bluez5 yes (as it's labeled as
> conflicting):
>
>
https://git.sailfishos.org/mer-core/obexd/commit/6e9de8842715dec6e3b4348d6a076dbf247fa43b
>
> Now Im in no way an expert on obex / obexd. So if someone has more intel,
> please
It seems obexd might have some issues with bluez5 yes (as it's labeled as
conflicting):
https://git.sailfishos.org/mer-core/obexd/commit/6e9de8842715dec6e3b4348d6a076dbf247fa43b
Now Im in no way an expert on obex / obexd. So if someone has more intel,
please share!
Best,
tk
On Thu, Jul 11, 2019
Tone Kastlunger wrote:
> I have always been suspecting Jolla using the missing BT export as
> a lock-in technique; but even switching between sfos phones (jolla 1 ->
> jolla c -> xperia x for me,
> probably a xa2 coming up soon) is impossible as it is now, so that
> (luckily) kills the theory.
>
I have always been suspecting Jolla using the missing BT export as
a lock-in technique; but even switching between sfos phones (jolla 1 ->
jolla c -> xperia x for me,
probably a xa2 coming up soon) is impossible as it is now, so that (luckily)
kills the theory.
I'd be glad to be able to help, a (s
Tone Kastlunger wrote:
> Perhaps the exposed bt profile of the syncml client matches first?
I don't know exactly. What I see is, there was a different syncml server
probably from Nokia with different UUID. I would be glad if someone can
provide history on that.
I also need to understand how this
Tone Kastlunger wrote:
> btw, deloptes, any luck with the mer/sfos git account?
> I'd love to test the changes you made on the bt stack on my xperia x!
Hi,
I was able to contact lbt and get an account, but no time to look around.
I'll be able to work on that past this weekend and I will be also g
btw, deloptes, any luck with the mer/sfos git account?
I'd love to test the changes you made on the bt stack on my xperia x!
On Wed, Jul 10, 2019 at 11:28 AM Tone Kastlunger
wrote:
>
> Perhaps the exposed bt profile of the syncml client matches first?
>
> On Tue, Jul 9, 2019 at 11:51 PM deloptes
Perhaps the exposed bt profile of the syncml client matches first?
On Tue, Jul 9, 2019 at 11:51 PM deloptes wrote:
>
> Tone Kastlunger wrote:
>
> > If syncevolution works fine with n9, sfos should be working fine with it
> > too?
> >
>
> In theory yes. The problem is that many things changed sinc
Tone Kastlunger wrote:
> If syncevolution works fine with n9, sfos should be working fine with it
> too?
>
In theory yes. The problem is that many things changed since N9 on the
mobile side. We have bluez5 and bluez5-obex and openobex. Bluez5 changed
dramatically from bluez4 and code must be rew
If syncevolution works fine with n9, sfos should be working fine with it too?
Best,
tk
On Sun, Jul 7, 2019 at 12:22 AM deloptes wrote:
>
> Hi,
>
> I was wondering if someone knows what exactly is hidden behind Nokia
> specific SyncML profiles. When I run
> sdptool browse
>
>
> Service N
Hi,
I was wondering if someone knows what exactly is hidden behind Nokia
specific SyncML profiles. When I run
sdptool browse
Service Name: Nokia SyncML Server
Service RecHandle: 0x1000c
Service Class ID List:
UUID 128: 5601--1000-8000-0002ee01
Protocol Descriptor List:
44 matches
Mail list logo
