Revision history [back]

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630. The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors (aborts) I never experienced so many Bluetooth connection errors (aborts) while pairing or transferring data (every second to third try).

2. Detection of Bluetooth profiles while pairing When initiating the pairing from the T630, both phones detect only a sing,le (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla). When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla! The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried thst many times).

3. File transfers I was able to transfer files with the extension ”.jpg” from the T630 to the Jolla, but that was it! Pushing any other file type to the Jolla results in an aborted transfer right after the BT connection was established. These aborted transfers are always correctly logged in the Jolla's notifications. By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. All these actions always fail, which is logged under «Settings --> System --> Transfers» each time with ”failed”. Well, as the file extension ”.vcf” differs from ”.jpg” it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the Jolla does not detect the right Bluetooth profiles on the T630, it is not surprising to see SailfishOS's Bluetooth sync fail.

5. Minor Bluetooth bugs Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

NB: All in all you are definitely on the right track IMHO, e.g licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1 Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630. T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors (aborts) errors

   I never experienced so many Bluetooth connection errors (aborts) while pairing or transferring data (every second to third try).

2. Detection of Bluetooth profiles while pairing pairing

   When initiating the pairing from the T630, both phones detect only a sing,le (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla). Jolla).

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla! Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried thst this many times).

3. File transfers transfers

   I was able to transfer files with the extension ”.jpg” from the T630 to the Jolla, but that was it! Pushing any other file type to the Jolla results in an aborted transfer right after the BT connection was established. These aborted failed transfers are always correctly logged in the Jolla's notifications. notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. All these actions always fail, which is logged under «Settings --> System --> Transfers» each time with ”failed”. ”failed”.

   Well, as the file extension ”.vcf” differs from ”.jpg” it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the Jolla does not detect the right Bluetooth profiles on the T630, it is not surprising to see SailfishOS's Bluetooth sync fail.

5. Minor Bluetooth bugs bugs

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

NB: All in all you are definitely on the right track IMHO, e.g licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1 v1

Kudos for the good work.
work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (every second to third try).

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a sing,le single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla).

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer files with the extension ”.jpg” from the T630 to the Jolla, but that was it! Pushing any other file type to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. All these actions always fail, which is logged under «Settings --> System --> Transfers» each time with ”failed”.

   Well, as the file extension ”.vcf” differs from ”.jpg” it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the Jolla does not detect the right Bluetooth profiles on the T630, it is not surprising no surprise to see SailfishOS's Bluetooth sync fail.

5. Minor Bluetooth bugs

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

NB: All in all you are definitely on the right track IMHO, e.g licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (every second to third try).

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla).

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer files with the extension ”.jpg” from the T630 to the Jolla, but that was it! Pushing any other file type to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. All these actions always fail, which is logged under «Settings --> System --> Transfers» each time with ”failed”.

   Well, as the file extension ”.vcf” differs from ”.jpg” it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the Jolla does not detect the right Bluetooth profiles on the T630, it is no surprise to see SailfishOS's Bluetooth sync fail.

5. Minor Bluetooth bugs

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (every second to third try).

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla).

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer files with the extension ”.jpg” from the T630 to the Jolla, but that was it! Pushing any other file type to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. All these actions always fail, which is logged under «Settings --> System --> Transfers» each time with ”failed”.

   Well, as the file extension ”.vcf” differs from ”.jpg” it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the Jolla does not detect the right Bluetooth profiles on the T630, T630 it is no surprise to see SailfishOS's Bluetooth sync fail.

5. Minor Bluetooth bugs

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (every (about every second to third try).

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla).

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer files with the extension ”.jpg” from the T630 to the Jolla, but that was it! Pushing any other file type to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. Trying to import the T630's contacts by «Settings --> Apps --> People --> From device with Bluetooth» or the «Import wizard» shows no available devices after the search for Bluetooth devices, although the devices are paired. All these actions always fail, which is some of them are logged under «Settings --> System --> Transfers» each time with ”failed”.

   Well, as the file extension ”.vcf” differs from ”.jpg” it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the Jolla does not detect the right Bluetooth profiles on the T630 it is no surprise to see SailfishOS's Bluetooth sync and import fail.

5. Minor Bluetooth bugsbug

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (about every second try).

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla).

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer files with the extension ”.jpg” from the T630 to the Jolla, but that was it! Pushing any other file type to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. Trying to import the T630's contacts by «Settings --> Apps --> People --> From device with Bluetooth» or the «Import wizard» shows no available devices after the search for Bluetooth devices, although the devices are paired. All these actions always fail, some of them are logged under «Settings --> System --> Transfers» with ”failed”.

   Well, as the file extension ”.vcf” differs from ”.jpg” it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the Jolla does not detect the right Bluetooth profiles on the T630 it is no surprise to see SailfishOS's Bluetooth sync and import fail.

5. Minor Bluetooth bug

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

And does the Jolla phone with SailfishOS 1.1.4.29 currently really solely expose the Bluetooth profile ”object push”?

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (about every second try).

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla).

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer files with the extension ”.jpg” from the T630 to the Jolla, but that was it! Pushing any other file type to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. Trying to import the T630's contacts by «Settings --> Apps --> People --> From device with Bluetooth» or the «Import wizard» shows no available devices after the search for Bluetooth devices, although the devices are paired. All these actions always fail, some of them are logged under «Settings --> System --> Transfers» with ”failed”.

   Well, as the file extension ”.vcf” differs from ”.jpg” it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the Jolla does not detect the right Bluetooth profiles on the T630 it is no surprise to see SailfishOS's Bluetooth sync and import fail.

5. Minor Bluetooth settings bug

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

And does the Jolla phone with SailfishOS 1.1.4.29 currently really solely expose the Bluetooth profile ”object push”?

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (about every second try).

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla).

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer files with the extension ”.jpg” from the T630 to the Jolla, but that was it! Pushing any other file type to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. Trying to import the T630's contacts by «Settings --> Apps --> People --> From device with Bluetooth» or the «Import wizard» shows no available devices after the search for Bluetooth devices, although the devices are paired. All these actions always fail, some of them are logged under «Settings --> System --> Transfers» with ”failed”.

   Well, as the file extension ”.vcf” differs from ”.jpg” it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the Jolla does not T630 is unable to detect the right any other Bluetooth profiles on the T630 but ”object push” on the Jolla it is no surprise to see SailfishOS's Bluetooth sync and import fail.fail (as they are not supported from the T630's view).

5. Minor Bluetooth settings bug

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

And does the Jolla phone with SailfishOS 1.1.4.29 currently really solely expose the Bluetooth profile ”object push”?

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (about every second try).

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla).

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer files with the extension ”.jpg” from the T630 to the Jolla, but that was it! Pushing any other file type to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. Trying to import the T630's contacts by «Settings --> Apps --> People --> From device with Bluetooth» or the «Import wizard» shows no available devices after the search for Bluetooth devices, although the devices are paired. All these actions always fail, some of them are logged under «Settings --> System --> Transfers» with ”failed”.

   Well, as the file extension ”.vcf” differs from ”.jpg” it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the T630 is unable to detect any other Bluetooth profiles but ”object push” on the Jolla it is no surprise to see SailfishOS's Bluetooth sync and import fail (as they are not supported from the T630's view).

5. Minor Bluetooth settings bug

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

And does the Jolla phone with (with SailfishOS 1.1.4.29 1.1.4.29) currently really solely expose the Bluetooth profile ”object push”?

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (about every second try).

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla).

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer files with the extension ”.jpg” from the T630 to the Jolla, but that was it! Pushing any other file type to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. Trying to import the T630's contacts by «Settings --> Apps --> People --> From device with Bluetooth» or the «Import wizard» shows no available devices after the search for Bluetooth devices, although the devices are paired. All these actions always fail, some of them are logged under «Settings --> System --> Transfers» with ”failed”.

   Well, as the file extension ”.vcf” differs from ”.jpg” it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the T630 is unable to detect any other Bluetooth profiles but ”object push” on the Jolla it is no surprise to see SailfishOS's Bluetooth sync and import fail (as they are not supported from the T630's view).

5. Minor Bluetooth settings bug

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

And does the Jolla phone (with SailfishOS 1.1.4.29) currently really solely expose the Bluetooth profile ”object push”?

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (about every second try).

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla).Jolla). IIRC these two BT profiles are the same : OPP = Object Push Profile

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer files with the extension ”.jpg” from the T630 to the Jolla, but that was it! Pushing any other file type to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. Trying to import the T630's contacts by «Settings --> Apps --> People --> From device with Bluetooth» or the «Import wizard» shows no available devices after the search for Bluetooth devices, although the devices are paired. All these actions always fail, some of them are logged under «Settings --> System --> Transfers» with ”failed”.

   Well, as the file extension ”.vcf” differs from ”.jpg” it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the T630 is unable to detect any other Bluetooth profiles but ”object push” on the Jolla it is no surprise to see SailfishOS's Bluetooth sync and import fail (as they are not supported from the T630's view).

5. Minor Bluetooth settings bug

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

And does the Jolla phone (with SailfishOS 1.1.4.29) currently really solely expose the Bluetooth profile ”object push”?

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (about every second try).try). Mostly the BT connection errors occur either before a connection is established successfully or right at the start of a data transfer; rarely a connection error happens in the middle of a data transfer.

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla). IIRC these two BT profiles are the same : same: OPP = Object Push Profile

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer files with the extension ”.jpg” from the T630 to the Jolla, but that was it! Pushing any other file type to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. Trying to import the T630's contacts by «Settings --> Apps --> People --> From device with Bluetooth» or the «Import wizard» shows no available devices after the search for Bluetooth devices, although the devices are paired. All these actions always fail, some of them are logged under «Settings --> System --> Transfers» with ”failed”.

   Well, as the file extension ”.vcf” differs from ”.jpg” it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the T630 is unable to detect any other Bluetooth profiles but ”object push” on the Jolla it is no surprise to see SailfishOS's Bluetooth sync and import fail (as they are not supported from the T630's view).

5. Minor Bluetooth settings bug

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

And does the Jolla phone (with SailfishOS 1.1.4.29) currently really solely expose the Bluetooth profile ”object push”?

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (about every second try). Mostly the BT connection errors occur either before a connection is established successfully or right at the start of a data transfer; rarely a connection error happens in the middle of a data transfer.

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla). IIRC these two BT profiles are the same: OPP = Object Push Profile

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer graphics files with the extension extensions ”.jpg” and ”.gif” from the T630 to the Jolla, but that was it! Pushing any other file type (I tried a couple of audio file formats, e.g. ”.wav” and ”.mid”) to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. Trying to import the T630's contacts by «Settings --> Apps --> People --> From device with Bluetooth» or the «Import wizard» shows no available devices after the search for Bluetooth devices, although the devices are paired. All these actions always fail, some of them are logged under «Settings --> System --> Transfers» with ”failed”.

   Well, as the file extension ”.vcf” differs from ”.jpg” denotes this is no graphics file, it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the T630 is unable to detect any other Bluetooth profiles but ”object push” on the Jolla Jolla, it is no surprise to see SailfishOS's Bluetooth sync and import fail (as they are not supported from the T630's view).

5. Minor Bluetooth settings bug

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

And does the Jolla phone (with SailfishOS 1.1.4.29) currently really solely expose the Bluetooth profile ”object push”?

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (about every second try). Mostly the BT connection errors occur either before a connection is established successfully or right at the start of a data transfer; rarely a connection error happens in the middle of a data transfer.

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla). IIRC these two BT profiles are the same: OPP = Object Push Profile

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer graphics files with the extensions ”.jpg” and ”.gif” from the T630 to the Jolla, but that was it! Pushing any other file type (I tried a couple of audio file formats, e.g. ”.wav” and ”.mid”) to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. Trying to import the T630's contacts by «Settings --> Apps --> People --> From device with Bluetooth» or the «Import «--> Import wizard» shows no available devices after the search for Bluetooth devices, although the devices are definitely paired. All these actions always fail, some of them are logged under «Settings --> System --> Transfers» with ”failed”.

   Well, as the file extension ”.vcf” denotes this is no graphics file, it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the T630 is unable to detect any other Bluetooth profiles profile but ”object push” on the Jolla, it is no surprise to see SailfishOS's Bluetooth sync and import fail (as they are not supported from the T630's view).

5. Minor Bluetooth settings bug

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

And does the Jolla phone (with SailfishOS 1.1.4.29) currently really solely expose the Bluetooth profile ”object push”?

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (about every second try). Mostly the BT connection errors occur either before a connection is established successfully or right at the start of a data transfer; rarely a connection error happens in the middle of a data transfer.

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla). IIRC these two BT profiles are the same: OPP = Object Push Profile

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer graphics files with the extensions ”.jpg” and ”.gif” from the T630 to the Jolla, but that was it! (EDIT1: and ”.wav”) from the T630 to the Jolla. Pushing any other file type types (I tried a couple of old audio file formats, e.g. ”.wav” ”.imy” and ”.mid”) to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. Trying to import the T630's contacts by «Settings --> Apps --> People --> From device with Bluetooth» or the «--> Import wizard» shows no available devices after the search for Bluetooth devices, although the devices are definitely paired. All these actions always fail, some of them are logged under «Settings --> System --> Transfers» with ”failed”.

   Well, as the file extension ”.vcf” denotes this is no graphics file, it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the T630 is unable to detect any other Bluetooth profile but ”object push” on the Jolla, it is no surprise to see SailfishOS's Bluetooth sync and import fail (as they are not supported from the T630's view).

5. Minor Bluetooth settings bug

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

And does the Jolla phone (with SailfishOS 1.1.4.29) currently really solely expose the Bluetooth profile ”object push”?

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29) 1.1.4.29, retested with 1.1.6.27) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (about every second try). Mostly the BT connection errors occur either before a connection is established successfully or right at the start of a data transfer; rarely a connection error happens in the middle of a data transfer.

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla). IIRC these two BT profiles are the same: OPP = Object Push Profile

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer files with the extensions ”.jpg” and ”.gif” (EDIT1: and ”.wav”) from the T630 to the Jolla. Pushing other file types (I tried a couple of old audio file formats, e.g. ”.imy” and ”.mid”) to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

   Solution: See hmallat's post below.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. Trying to import the T630's contacts by «Settings --> Apps --> People --> From device with Bluetooth» or the «--> Import wizard» shows no available devices after the search for Bluetooth devices, although the devices are definitely paired. All these actions always fail, some of them are logged under «Settings --> System --> Transfers» with ”failed”.

   Well, as it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the T630 is unable to detect any other Bluetooth profile but ”object push” on the Jolla, it is no surprise to see SailfishOS's Bluetooth sync and import fail (as they are not supported from the T630's view).

5. Minor Bluetooth settings bug

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

And does the Jolla phone (with SailfishOS 1.1.6.27 and 1.1.4.29) currently really solely expose the Bluetooth profile ”object push”?

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29, retested with 1.1.6.27) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (about every second try). Mostly the BT connection errors occur either before a connection is established successfully or right at the start of a data transfer; rarely a connection error happens in the middle of a data transfer.

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla). IIRC these two BT profiles are the same: OPP = Object Push Profile

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer files with the extensions ”.jpg” and ”.gif” (EDIT1: and ”.wav”) from the T630 to the Jolla. Pushing other file types (I tried a couple of old audio file formats, e.g. ”.imy” and ”.mid”) to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

   Solution: Workaround: See hmallat's post below.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. Trying to import the T630's contacts by «Settings --> Apps --> People --> From device with Bluetooth» or the «--> Import wizard» shows no available devices after the search for Bluetooth devices, although the devices are definitely paired. All these actions always fail, some of them are logged under «Settings --> System --> Transfers» with ”failed”.

   Well, as it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the T630 is unable to detect any other Bluetooth profile but ”object push” on the Jolla, it is no surprise to see SailfishOS's Bluetooth sync and import fail (as they are not supported from the T630's view).

5. Minor Bluetooth settings bug

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

And does the Jolla phone (with SailfishOS 1.1.6.27 and 1.1.4.29) currently really solely expose the Bluetooth profile ”object push”?push”? Edit3: No, supposedly these Bluetooth profiles are supported, see https://jolla.zendesk.com/hc/en-us/articles/201440697-What-Bluetooth-profiles-does-SailfishOS-support-. Thus this is a bug.

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.

Using a Jolla phone (SailfishOS 1.1.4.29, retested with 1.1.6.27) and a SonyEricsson T630.

The Bluetooth 1.1 implementation of these SonyEricsson mobile phones (I used BT on T610, T630 and K700i a lot) always worked well with many different USB Bluetooth sticks at PCs (old BT 1.1 ones as well as BT 2.x ones), mobile phones (Nokia N900 & Symbian phones, and between aforementioned SonyEricsson phones) and a couple of BT headsets (mostly from SonyEricsson). Bluetooth was and is my preferred way of transferring files and most importantly contacts between mobile phones, especially when migrating to a newer phone. I am not willing to use a ”sync service” due to privacy of the data. By browsing other BT related posts here at together.jolla.com it became obvious, that flawlessly working Bluetooth is essential for many, but seems to be problematic on the Jolla phone. But no one seems to have dug deeper into the issues and faced so many of them, yet. My original aim was to just quickly transfer all contacts from the T630 to the Jolla phone (three days (this was months ago).

1. Bluetooth connection errors

   I never experienced so many Bluetooth connection errors while pairing or transferring data (about every second try). Mostly the BT connection errors occur either before a connection is established successfully or right at the start of a data transfer; rarely a connection error happens in the middle of a data transfer.

2. Detection of Bluetooth profiles while pairing

   When initiating the pairing from the T630, both phones detect only a single (!) BT profile on the other phone: ”object push” (Jolla's profiles detected by T630) respectively ”OPP” (T630's profiles detected by Jolla). IIRC these two BT profiles are the same: OPP = Object Push Profile

   When initiating the pairing from the Jolla phone, the Jolla detects all available BT profiles on the T630 (SPP, DUN, SYNC, OPP, SPP, HSP, BIP), but the T630 still sees only ”object push” on the Jolla!

   The T630 has a menu entry, which allows to redetect available BT services on an already paired device, but the T630 always just sees ”object push” on the Jolla (I tried this many times).

3. File transfers

   I was able to transfer files with the extensions ”.jpg” and ”.gif” (EDIT1: and ”.wav”) from the T630 to the Jolla. Pushing other file types (I tried a couple of old audio file formats, e.g. ”.imy” and ”.mid”) to the Jolla results in an aborted transfer right after the BT connection was established. These failed transfers are always correctly logged in the Jolla's notifications.

   By reading together.jolla.com this seems to be a really evil feature of SailfishOS.

   Workaround: See hmallat's post below.

4. Migrating contacts to the Jolla via Bluetooth

   ... always fails! Neither pushing all contacts or a single contact from the T630 to the Jolla nor pulling the T630's contacts to the Jolla via «Settings --> System --> Bluetooth sync» works. Trying to import the T630's contacts by «Settings --> Apps --> People --> From device with Bluetooth» or the «--> Import wizard» shows no available devices after the search for Bluetooth devices, although the devices are definitely paired. All these actions always fail, some of them are logged under «Settings --> System --> Transfers» with ”failed”.

   Well, as it seems that the Jolla does not accept the contacts when pushing them from the T630, and as the T630 is unable to detect any other Bluetooth profile but ”object push” on the Jolla, it is no surprise to see SailfishOS's Bluetooth sync and import fail (as they are not supported from the T630's view).

5. Minor Bluetooth settings bug

   Even though «Always accept connections from this device» was switched on while pairing, the Jolla asked each time for allowing a new Bluetooth connection when trying to push data from the T630. Toggling this setting off and on again resolved this, i.e. the feature then works as intended.

Now, how do I transfer my contacts from the T630 to the Jolla easily?

And does the Jolla phone (with SailfishOS 1.1.6.27 and 1.1.4.29) currently really solely expose the Bluetooth profile ”object push”? Edit3: No, supposedly these Bluetooth profiles are supported, see https://jolla.zendesk.com/hc/en-us/articles/201440697-What-Bluetooth-profiles-does-SailfishOS-support-. Thus this is a bug.

NB: All in all you are definitely on the right track IMHO, e.g the licensing, the development model, keeping Nemo alive, but the software stack is what it is: v1

Kudos for the good work.