[Bug 4835] N900: fails to synchronize with some distros
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=4835
--- Comment #21 from danielb <dbet1(a)gmx.net> 2011-09-06 14:31:06 UTC ---
(In reply to comment #19)
> (In reply to comment #18)
> > I have the same problem on two different machines, both with the same software
> > installed: Ubuntu Linux 10.04 (Lucid) with Syncevolution 1.1.1. This means the
> > same kernel, bluez software and so on. But on one machine it works, on the
> > other this bug occurs.
> >
> > How can I help?
> As I read the bug it could be due to a bug in openobex1.4 which is used in N900
> PR1.3:
> http://git.kernel.org/?p=bluetooth/openobex.git;a=blobdiff;f=lib/obex_obj...
>
> Here you can find a openobex1.5 for Armel
> http://talk.maemo.org/showthread.php?p=731941#post731941
> The bug shows when the message is to big to transfer in one packet. So you can
> test it on systems which fail with very small address books.
Openobex 1.5 does not help. As I said, on one machine it works out of the box.
On the machine at which the sync does not work with the N900, I can sync a
Nokia E7 without any problems.(In reply to comment #20)
> (In reply to comment #19)
> > (In reply to comment #18)
> > > I have the same problem on two different machines, both with the same software
> > > installed: Ubuntu Linux 10.04 (Lucid) with Syncevolution 1.1.1. This means the
> > > same kernel, bluez software and so on. But on one machine it works, on the
> > > other this bug occurs.
> > >
> > > How can I help?
> > As I read the bug it could be due to a bug in openobex1.4 which is used in N900
> > PR1.3:
> > http://git.kernel.org/?p=bluetooth/openobex.git;a=blobdiff;f=lib/obex_obj...
> >
> > Here you can find a openobex1.5 for Armel
> > http://talk.maemo.org/showthread.php?p=731941#post731941
> > The bug shows when the message is to big to transfer in one packet. So you can
> > test it on systems which fail with very small address books.
>
> Openobex 1.4 does not help. As I said, on one machine it works out of the box.
> On the machine at which the sync does not work with the N900, I can sync a
> Nokia E7 without any problems.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: major
Priority: High
Keywords:
Status: WAITING FOR UPSTREAM
Who: dbet1(a)gmx.net
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=4835
--
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
9 years, 4 months
[Bug 4835] N900: fails to synchronize with some distros
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=4835
--- Comment #20 from danielb <dbet1(a)gmx.net> 2011-09-06 14:27:36 UTC ---
(In reply to comment #19)
> (In reply to comment #18)
> > I have the same problem on two different machines, both with the same software
> > installed: Ubuntu Linux 10.04 (Lucid) with Syncevolution 1.1.1. This means the
> > same kernel, bluez software and so on. But on one machine it works, on the
> > other this bug occurs.
> >
> > How can I help?
> As I read the bug it could be due to a bug in openobex1.4 which is used in N900
> PR1.3:
> http://git.kernel.org/?p=bluetooth/openobex.git;a=blobdiff;f=lib/obex_obj...
>
> Here you can find a openobex1.5 for Armel
> http://talk.maemo.org/showthread.php?p=731941#post731941
> The bug shows when the message is to big to transfer in one packet. So you can
> test it on systems which fail with very small address books.
Openobex 1.4 does not help. As I said, on one machine it works out of the box.
On the machine at which the sync does not work with the N900, I can sync a
Nokia E7 without any problems.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: major
Priority: High
Keywords:
Status: WAITING FOR UPSTREAM
Who: dbet1(a)gmx.net
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=4835
--
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
9 years, 4 months
[Bug 736] Detect 'device model' for phones
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=736
--- Comment #7 from pohly <patrick.ohly(a)intel.com> 2011-09-06 13:19:19 UTC ---
The Python bluetooth-device-id-inspector.py utility script for gathering
hardware IDs is also in SyncEvolution:
commit 5b712a15e5f3bb787f260b1face0ed4380895d31
Author: Chris Kühl <chrisk(a)openismus.com>
Date: Mon Aug 29 16:37:03 2011 +0200
Add script to query for the bluetooth device id
We currently only have a few devices added to our bluetooth product
lookup table.
This script is intended to allow user to query the information from
device they own and instructs them to send it to a syncevolution
devoloper (me for the time being). The goal is to crowd-source sa much
phone data as we can.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: enhancement
Priority: Undecided
Keywords:
Status: RESOLVED
Who: patrick.ohly(a)intel.com
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=736
--
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
9 years, 4 months
[Bug 736] Detect 'device model' for phones
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=736
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #6 from pohly <patrick.ohly(a)intel.com> 2011-09-06 13:17:26 UTC ---
Resolved in master branch:
commit 9f4a9a801755829a237caa1f6cb1f096e5757e88
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Tue Sep 6 12:53:42 2011 +0200
D-Bus server: send hardware info in new "hardwareName" read-only property
The previously suggested (and implemented) approach of reusing the
peerName property to convey hardware information didn't pass the smell
test (too complex to explain that the same property has different
meanings depending on the context).
So now a new "hardwareName" property is used instead. Also renamed
the TemplateDescription member accordingly, updated the API docs
and implemented the "hardwareName only set if known" part of it.
commit d347a548c6624346ef1a16a906fb6b6c9980c3b2
Author: Chris Kühl <chrisk(a)openismus.com>
Date: Mon Aug 29 16:12:46 2011 +0200
Make deviceName and peerName more well-defined.
Previously the DeviceDescription deviceName was being stored in the
TemplateDescription peerName.
This patch defines devicename in both DeviceDescription &
TemplateDescription as storing the user-modifiable device name, thus
unifiying the meaning. The peerName is defined to hold the vendor
and/or model information discovered using the Bluetooth Device ID
profile (DIP) or, in the case that DIP is not supported, peerName will
be an empty string. Whether the peerName includes the model of the
device is dependent on whether a matching entry was found in the
product lookup table.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: enhancement
Priority: Undecided
Keywords:
Status: RESOLVED
Who: patrick.ohly(a)intel.com
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Flags:
Changed: Status Resolution
--------
https://bugs.meego.com/show_bug.cgi?id=736
--
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
9 years, 4 months