We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2014-05-04 22:53:34 +0200

jgr gravatar image

Privacy, Security, Usability [subjective]

Dear Jolla team,

  • Privacy
  • Security
  • Usability

these were the reasons when deciding to buy a and support Jolla – at least based on the history (N900, N9) I hoped, Jolla would aim for these. Unfortunately, you failed on all 3 topics.

Privacy

Just as examples:

  • GPS continuously transmits data to HERE severs (https://together.jolla.com/question/32285/is-it-possible-to-disable-here-data-collection/)
  • TOH: It is still not clear, what data is transferred to (and stored by) Jolla servers related to TOH management, when first installing a TOH and when switching between TOHs
    Data allocated to (at least) the user account are stored: https://together.jolla.com/question/8153/bug-unable-to-download-ambience-2nd-hand/
  • It is still not clear, what data is transferred to (and stored by) Jolla servers related to app management (Jolla store).
    (I expect that at least some of the data are stored together with the handset or user account in one way or another.)
  • When enabling developer mode, a corresponding information is transmitted to Jolla servers, and again it is yet undisclosed which data exactly (https://together.jolla.com/question/18957/difficult-to-use-the-phone-in-bright-sunlight-need-for-blackwhite-and-or-hight-contrast-ambiance/)

I do not want to be tracked/trackable. Do not gather any more data than absolutely necessary for the current task.

Security

There is a known security hole (plain text password accessible by apps that may phone home).
https://together.jolla.com/question/39495/security-risk-with-sqlite-db-in-jolla-passwords-in-plain-text-in-user-space/

While such basic mistake (plain text password accessible by applications) should not happen in the first place, I had expected a hot fix as soon as possible – no action yet (for almost 3 weeks). Personally, I regard this security hole as important. I limited my use of the Jolly handset to minimize the risk of exposing my passwords to 3rd parties.

There seems to be another password issue, publicized Saturday morning (it is 32 hours later now), I wonder what you will do about this – ignore it again? https://together.jolla.com/question/41642/e-mail-smtp-sending-out-password-in-certain-circumstances/

Usability

  • The unlock code cannot be properly entered outdoor in just decent sun light: Simply, the figures (the ones on the keys as well as the ones shown when typed) are too faint. If you know your device sufficiently, you may be able to type blind – hopefully you have not set a retry limit.
    (Yet we have spring only, what about summer?)
    This general visibility problem has been discussed in many questions, just to mention a few:
    https://together.jolla.com/question/35442/screen-not-visible-under-sun-light/
    https://together.jolla.com/question/18957/difficult-to-use-the-phone-in-bright-sunlight-need-for-blackwhite-and-or-hight-contrast-ambiance/
    https://together.jolla.com/question/34569/suggestion-keyboard-and-system-settings-for-people-with-eyesight-problems/
    https://together.jolla.com/question/16786/ways-to-enhance-text-readability-in-sailfish-ui-incl-apps/
    https://together.jolla.com/question/32221/a-way-to-freely-select-fonts-font-colors-and-other-ui-components/
  • The same for dialing numbers: The number keypad as well as the numbers dialed are too faint. Asterisk and plus sign are on the same key: It is impossible to differentiate them when shown in the number to be dialed while there is just a little bit more environmental light than there is typically indoors.
  • Occasionally it is impossible to answer a call (e.g.
    https://together.jolla.com/question/27179/bug-trying-to-answer-a-call-pulley-menu-cannot-be-pulled-down/,
    https://together.jolla.com/question/40409/bug-call-answering-pulley-menu-jumps-erratically/)
  • The handset may suddenly shut down – with or without the user realizing this. (During recent shut-downs, I observed that first the indicated battery charge suddenly dropped down from a couple of ten percent [as much as >70%] to 0% and subsequently the handset shut down. Thereafter I could reboot and battery charge was back to the original amount.)
    This problem may be hardware related, but even if so, you should acknowledge the problem and present a solution.
    There are a lot of battery related posts, including overheating, inexplicable high drain etc. These may or may not be related to each other. None of them seems to be solved (the user hint to insert a piece of paper between battery and casing may work – but I do not regard it as official, i.e. Jolla solution until you officially declare to do so). Of the many posts on the subject, just a major one for reference: https://together.jolla.com/question/7144/jolla-randomly-shuts-down-10516/)

These are only the main issues rendering the Jolla handset as unusable for deployment as the only/main mobile phone in private as well as in business environments.

What does Jolla?

Instead of solving the issues above, you provide a hot fix for MMS functionality (https://together.jolla.com/question/40658/hotfix-mms-changes-for-paarlampi-10519/). In my eyes: Features are the wrong focus as long as the basics are not solved.

While I used to use the Jolla as the only mobile phone since January, now I am starting to look for another smart-phone that ensures privacy, is secure and can reliably be used as mobile phone.

Privacy, Security, Usability [subjective]

Dear Jolla team,

  • Privacy
  • Security
  • Usability

these were the reasons when deciding to buy a and support Jolla – at least based on the history (N900, N9) I hoped, Jolla would aim for these. Unfortunately, you failed on all 3 topics.

Privacy

Just as examples:

  • GPS continuously transmits data to HERE severs (https://together.jolla.com/question/32285/is-it-possible-to-disable-here-data-collection/)
  • TOH: It is still not clear, what data is transferred to (and stored by) Jolla servers related to TOH management, when first installing a TOH and when switching between TOHs
    Data allocated to (at least) the user account are stored: https://together.jolla.com/question/8153/bug-unable-to-download-ambience-2nd-hand/
  • It is still not clear, what data is transferred to (and stored by) Jolla servers related to app management (Jolla store).
    (I expect that at least some of the data are stored together with the handset or user account in one way or another.)
  • When enabling developer mode, a corresponding information is transmitted to Jolla servers, and again it is yet undisclosed which data exactly (https://together.jolla.com/question/18957/difficult-to-use-the-phone-in-bright-sunlight-need-for-blackwhite-and-or-hight-contrast-ambiance/)

I do not want to be tracked/trackable. Do not gather any more data than absolutely necessary for the current task.

Security

There is a known security hole (plain text password accessible by apps that may phone home).
https://together.jolla.com/question/39495/security-risk-with-sqlite-db-in-jolla-passwords-in-plain-text-in-user-space/

While such basic mistake (plain text password accessible by applications) should not happen in the first place, I had expected a hot fix as soon as possible – no action yet (for almost 3 weeks). Personally, I regard this security hole as important. I limited my use of the Jolly handset to minimize the risk of exposing my passwords to 3rd parties.

There seems to be another password issue, publicized Saturday morning (it is 32 hours later now), I wonder what you will do about this – ignore it again? https://together.jolla.com/question/41642/e-mail-smtp-sending-out-password-in-certain-circumstances/

Usability

  • The unlock code cannot be properly entered outdoor in just decent sun light: Simply, the figures (the ones on the keys as well as the ones shown when typed) are too faint. If you know your device sufficiently, you may be able to type blind – hopefully you have not set a retry limit.
    (Yet we have spring only, what about summer?)
    This general visibility problem has been discussed in many questions, just to mention a few:
    https://together.jolla.com/question/35442/screen-not-visible-under-sun-light/
    https://together.jolla.com/question/18957/difficult-to-use-the-phone-in-bright-sunlight-need-for-blackwhite-and-or-hight-contrast-ambiance/
    https://together.jolla.com/question/34569/suggestion-keyboard-and-system-settings-for-people-with-eyesight-problems/
    https://together.jolla.com/question/16786/ways-to-enhance-text-readability-in-sailfish-ui-incl-apps/
    https://together.jolla.com/question/32221/a-way-to-freely-select-fonts-font-colors-and-other-ui-components/
  • The same for dialing numbers: The number keypad as well as the numbers dialed are too faint. Asterisk and plus sign are on the same key: It is impossible to differentiate them when shown in the number to be dialed while there is just a little bit more environmental light than there is typically indoors.
  • Occasionally it is impossible to answer a call (e.g.
    https://together.jolla.com/question/27179/bug-trying-to-answer-a-call-pulley-menu-cannot-be-pulled-down/,
    https://together.jolla.com/question/40409/bug-call-answering-pulley-menu-jumps-erratically/)
  • The handset may suddenly shut down – with or without the user realizing this. (During recent shut-downs, I observed that first the indicated battery charge suddenly dropped down from a couple of ten percent [as much as >70%] to 0% and subsequently the handset shut down. Thereafter I could reboot and battery charge was back to the original amount.)
    This problem may be hardware related, but even if so, you should acknowledge the problem and present a solution.
    There are a lot of battery related posts, including overheating, inexplicable high drain etc. These may or may not be related to each other. None of them seems to be solved (the user hint to insert a piece of paper between battery and casing may work – but I do not regard it as official, i.e. Jolla solution until you officially declare to do so). Of the many posts on the subject, just a major one for reference: https://together.jolla.com/question/7144/jolla-randomly-shuts-down-10516/)

These are only the main issues rendering the Jolla handset as unusable for deployment as the only/main mobile phone in private as well as in business environments.

What does Jolla?

Instead of solving the issues above, you provide a hot fix for MMS functionality (https://together.jolla.com/question/40658/hotfix-mms-changes-for-paarlampi-10519/). In my eyes: Features are the wrong focus as long as the basics are not solved.

While I used to use the Jolla as the only mobile phone since January, now I am starting to look for another smart-phone that ensures privacy, is secure and can reliably be used as mobile phone.

Privacy, Security, Usability [subjective]

Dear Jolla team,

  • Privacy
  • Security
  • Usability

these were the reasons when deciding to buy a and support Jolla – at least I hoped, Jolla would aim for these. Unfortunately, you failed on all 3 topics.

Privacy

Just as examples:

  • GPS continuously transmits data to HERE severs (https://together.jolla.com/question/32285/is-it-possible-to-disable-here-data-collection/)
  • TOH: It is still not clear, what data is transferred to (and stored by) Jolla servers related to TOH management, when first installing a TOH and when switching between TOHs
    Data allocated to (at least) the user account are stored: https://together.jolla.com/question/8153/bug-unable-to-download-ambience-2nd-hand/
  • It is still not clear, what data is transferred to (and stored by) Jolla servers related to app management (Jolla store).
    (I expect that at least some of the data are stored together with the handset or user account in one way or another.)
  • When enabling developer mode, a corresponding information is transmitted to Jolla servers, and again it is yet undisclosed which data exactly (https://together.jolla.com/question/18957/difficult-to-use-the-phone-in-bright-sunlight-need-for-blackwhite-and-or-hight-contrast-ambiance/)
  • There is no privacy concept for apps (https://together.jolla.com/question/9670/api-security-model/), they may for example collect and call home with whatever data (https://together.jolla.com/question/10925/add-rights-management-for-native-apps/).

I do not want to be tracked/trackable. Do not gather any more data than absolutely necessary for the current task.

Security

There is a known security hole (plain text password accessible by apps that may phone home).
https://together.jolla.com/question/39495/security-risk-with-sqlite-db-in-jolla-passwords-in-plain-text-in-user-space/

While such basic mistake (plain text password accessible by applications) should not happen in the first place, I had expected a hot fix as soon as possible – no action yet (for almost 3 weeks). Personally, I regard this security hole as important. I limited my use of the Jolly handset to minimize the risk of exposing my passwords to 3rd parties.

There seems to be another password issue, publicized Saturday morning (it is 32 hours later now), I wonder what you will do about this – ignore it again? https://together.jolla.com/question/41642/e-mail-smtp-sending-out-password-in-certain-circumstances/

Usability

  • The unlock code cannot be properly entered outdoor in just decent sun light: Simply, the figures (the ones on the keys as well as the ones shown when typed) are too faint. If you know your device sufficiently, you may be able to type blind – hopefully you have not set a retry limit.
    (Yet we have spring only, what about summer?)
    This general visibility problem has been discussed in many questions, just to mention a few:
    https://together.jolla.com/question/35442/screen-not-visible-under-sun-light/
    https://together.jolla.com/question/18957/difficult-to-use-the-phone-in-bright-sunlight-need-for-blackwhite-and-or-hight-contrast-ambiance/
    https://together.jolla.com/question/34569/suggestion-keyboard-and-system-settings-for-people-with-eyesight-problems/
    https://together.jolla.com/question/16786/ways-to-enhance-text-readability-in-sailfish-ui-incl-apps/
    https://together.jolla.com/question/32221/a-way-to-freely-select-fonts-font-colors-and-other-ui-components/
  • The same for dialing numbers: The number keypad as well as the numbers dialed are too faint. Asterisk and plus sign are on the same key: It is impossible to differentiate them when shown in the number to be dialed while there is just a little bit more environmental light than there is typically indoors.
  • Occasionally it is impossible to answer a call (e.g.
    https://together.jolla.com/question/27179/bug-trying-to-answer-a-call-pulley-menu-cannot-be-pulled-down/,
    https://together.jolla.com/question/40409/bug-call-answering-pulley-menu-jumps-erratically/)
  • The handset may suddenly shut down – with or without the user realizing this. (During recent shut-downs, I observed that first the indicated battery charge suddenly dropped down from a couple of ten percent [as much as >70%] to 0% and subsequently the handset shut down. Thereafter I could reboot and battery charge was back to the original amount.)
    This problem may be hardware related, but even if so, you should acknowledge the problem and present a solution.
    There are a lot of battery related posts, including overheating, inexplicable high drain etc. These may or may not be related to each other. None of them seems to be solved (the user hint to insert a piece of paper between battery and casing may work – but I do not regard it as official, i.e. Jolla solution until you officially declare to do so). Of the many posts on the subject, just a major one for reference: https://together.jolla.com/question/7144/jolla-randomly-shuts-down-10516/)

These are only the main issues rendering the Jolla handset as unusable for deployment as the only/main mobile phone in private as well as in business environments.

What does Jolla?

Instead of solving the issues above, you provide a hot fix for MMS functionality (https://together.jolla.com/question/40658/hotfix-mms-changes-for-paarlampi-10519/). In my eyes: Features are the wrong focus as long as the basics are not solved.

While I used to use the Jolla as the only mobile phone since January, now I am starting to look for another smart-phone that ensures privacy, is secure and can reliably be used as mobile phone.

Privacy, Security, Usability [subjective]

Dear Jolla team,

  • Privacy
  • Security
  • Usability

these were the reasons when deciding to buy a and support Jolla – at least I hoped, Jolla would aim for these. Unfortunately, you failed on all 3 topics.

Edit (2014-05-05): Please note also the Answer below by Aard. It contains details in particular to the Privacy topic but covers the other topics as well.

Privacy

Just as examples:

  • GPS continuously transmits data to HERE severs (https://together.jolla.com/question/32285/is-it-possible-to-disable-here-data-collection/)
  • TOH: It is still not clear, what data is transferred to (and stored by) Jolla servers related to TOH management, when first installing a TOH and when switching between TOHs
    Data allocated to (at least) the user account are stored: https://together.jolla.com/question/8153/bug-unable-to-download-ambience-2nd-hand/
  • It is still not clear, what data is transferred to (and stored by) Jolla servers related to app management (Jolla store).
    (I expect that at least some of the data are stored together with the handset or user account in one way or another.)
  • When enabling developer mode, a corresponding information is transmitted to Jolla servers, and again it is yet undisclosed which data exactly (https://together.jolla.com/question/18957/difficult-to-use-the-phone-in-bright-sunlight-need-for-blackwhite-and-or-hight-contrast-ambiance/)
  • There is no privacy concept for apps (https://together.jolla.com/question/9670/api-security-model/), they may for example collect and call home with whatever data (https://together.jolla.com/question/10925/add-rights-management-for-native-apps/).

I do not want to be tracked/trackable. Do not gather any more data than absolutely necessary for the current task.

Security

There is a known security hole (plain text password accessible by apps that may phone home).
https://together.jolla.com/question/39495/security-risk-with-sqlite-db-in-jolla-passwords-in-plain-text-in-user-space/

While such basic mistake (plain text password accessible by applications) should not happen in the first place, I had expected a hot fix as soon as possible – no action yet (for almost 3 weeks). Personally, I regard this security hole as important. I limited my use of the Jolly handset to minimize the risk of exposing my passwords to 3rd parties.

There seems to be another password issue, publicized Saturday morning (it is 32 hours later now), I wonder what you will do about this – ignore it again? https://together.jolla.com/question/41642/e-mail-smtp-sending-out-password-in-certain-circumstances/

Usability

  • The unlock code cannot be properly entered outdoor in just decent sun light: Simply, the figures (the ones on the keys as well as the ones shown when typed) are too faint. If you know your device sufficiently, you may be able to type blind – hopefully you have not set a retry limit.
    (Yet we have spring only, what about summer?)
    This general visibility problem has been discussed in many questions, just to mention a few:
    https://together.jolla.com/question/35442/screen-not-visible-under-sun-light/
    https://together.jolla.com/question/18957/difficult-to-use-the-phone-in-bright-sunlight-need-for-blackwhite-and-or-hight-contrast-ambiance/
    https://together.jolla.com/question/34569/suggestion-keyboard-and-system-settings-for-people-with-eyesight-problems/
    https://together.jolla.com/question/16786/ways-to-enhance-text-readability-in-sailfish-ui-incl-apps/
    https://together.jolla.com/question/32221/a-way-to-freely-select-fonts-font-colors-and-other-ui-components/
  • The same for dialing numbers: The number keypad as well as the numbers dialed are too faint. Asterisk and plus sign are on the same key: It is impossible to differentiate them when shown in the number to be dialed while there is just a little bit more environmental light than there is typically indoors.
  • Occasionally it is impossible to answer a call (e.g.
    https://together.jolla.com/question/27179/bug-trying-to-answer-a-call-pulley-menu-cannot-be-pulled-down/,
    https://together.jolla.com/question/40409/bug-call-answering-pulley-menu-jumps-erratically/)
  • The handset may suddenly shut down – with or without the user realizing this. (During recent shut-downs, I observed that first the indicated battery charge suddenly dropped down from a couple of ten percent [as much as >70%] to 0% and subsequently the handset shut down. Thereafter I could reboot and battery charge was back to the original amount.)
    This problem may be hardware related, but even if so, you should acknowledge the problem and present a solution.
    There are a lot of battery related posts, including overheating, inexplicable high drain etc. These may or may not be related to each other. None of them seems to be solved (the user hint to insert a piece of paper between battery and casing may work – but I do not regard it as official, i.e. Jolla solution until you officially declare to do so). Of the many posts on the subject, just a major one for reference: https://together.jolla.com/question/7144/jolla-randomly-shuts-down-10516/)

These are only the main issues rendering the Jolla handset as unusable for deployment as the only/main mobile phone in private as well as in business environments.

What does Jolla?

Instead of solving the issues above, you provide a hot fix for MMS functionality (https://together.jolla.com/question/40658/hotfix-mms-changes-for-paarlampi-10519/). In my eyes: Features are the wrong focus as long as the basics are not solved.

While I used to use the Jolla as the only mobile phone since January, now I am starting to look for another smart-phone that ensures privacy, is secure and can reliably be used as mobile phone.

Privacy, Security, Usability [subjective]

Dear Jolla team,

  • Privacy
  • Security
  • Usability

these were the reasons when deciding to buy a and support Jolla – at least I hoped, Jolla would aim for these. Unfortunately, so far you failed on all 3 topics.

Edit (2014-05-05): Please note also the Answer below by Aard. It contains details in particular to the Privacy topic but covers the other topics as well.

Privacy

Just as examples:

  • GPS continuously transmits data to HERE severs (https://together.jolla.com/question/32285/is-it-possible-to-disable-here-data-collection/)
  • TOH: It is still not clear, what data is transferred to (and stored by) Jolla servers related to TOH management, when first installing a TOH and when switching between TOHs
    Data allocated to (at least) the user account are stored: https://together.jolla.com/question/8153/bug-unable-to-download-ambience-2nd-hand/
  • It is still not clear, what data is transferred to (and stored by) Jolla servers related to app management (Jolla store).
    (I expect that at least some of the data are stored together with the handset or user account in one way or another.)
  • When enabling developer mode, a corresponding information is transmitted to Jolla servers, and again it is yet undisclosed which data exactly (https://together.jolla.com/question/18957/difficult-to-use-the-phone-in-bright-sunlight-need-for-blackwhite-and-or-hight-contrast-ambiance/)
  • There is no privacy concept for apps (https://together.jolla.com/question/9670/api-security-model/), they may for example collect and call home with whatever data (https://together.jolla.com/question/10925/add-rights-management-for-native-apps/).

I do not want to be tracked/trackable. Do not gather any more data than absolutely necessary for the current task.

Security

There is a known security hole (plain text password accessible by apps that may phone home).
https://together.jolla.com/question/39495/security-risk-with-sqlite-db-in-jolla-passwords-in-plain-text-in-user-space/

While such basic mistake (plain text password accessible by applications) should not happen in the first place, I had expected a hot fix as soon as possible – no action yet (for almost 3 weeks). Personally, I regard this security hole as important. I limited my use of the Jolly handset to minimize the risk of exposing my passwords to 3rd parties.

There seems to be another password issue, publicized Saturday morning (it is 32 hours later now), I wonder what you will do about this – ignore it again? https://together.jolla.com/question/41642/e-mail-smtp-sending-out-password-in-certain-circumstances/

Usability

  • The unlock code cannot be properly entered outdoor in just decent sun light: Simply, the figures (the ones on the keys as well as the ones shown when typed) are too faint. If you know your device sufficiently, you may be able to type blind – hopefully you have not set a retry limit.
    (Yet we have spring only, what about summer?)
    This general visibility problem has been discussed in many questions, just to mention a few:
    https://together.jolla.com/question/35442/screen-not-visible-under-sun-light/
    https://together.jolla.com/question/18957/difficult-to-use-the-phone-in-bright-sunlight-need-for-blackwhite-and-or-hight-contrast-ambiance/
    https://together.jolla.com/question/34569/suggestion-keyboard-and-system-settings-for-people-with-eyesight-problems/
    https://together.jolla.com/question/16786/ways-to-enhance-text-readability-in-sailfish-ui-incl-apps/
    https://together.jolla.com/question/32221/a-way-to-freely-select-fonts-font-colors-and-other-ui-components/
  • The same for dialing numbers: The number keypad as well as the numbers dialed are too faint. Asterisk and plus sign are on the same key: It is impossible to differentiate them when shown in the number to be dialed while there is just a little bit more environmental light than there is typically indoors.
  • Occasionally it is impossible to answer a call (e.g.
    https://together.jolla.com/question/27179/bug-trying-to-answer-a-call-pulley-menu-cannot-be-pulled-down/,
    https://together.jolla.com/question/40409/bug-call-answering-pulley-menu-jumps-erratically/)
  • The handset may suddenly shut down – with or without the user realizing this. (During recent shut-downs, I observed that first the indicated battery charge suddenly dropped down from a couple of ten percent [as much as >70%] to 0% and subsequently the handset shut down. Thereafter I could reboot and battery charge was back to the original amount.)
    This problem may be hardware related, but even if so, you should acknowledge the problem and present a solution.
    There are a lot of battery related posts, including overheating, inexplicable high drain etc. These may or may not be related to each other. None of them seems to be solved (the user hint to insert a piece of paper between battery and casing may work – but I do not regard it as official, i.e. Jolla solution until you officially declare to do so). Of the many posts on the subject, just a major one for reference: https://together.jolla.com/question/7144/jolla-randomly-shuts-down-10516/)

These are only the main issues rendering the Jolla handset as unusable for deployment as the only/main mobile phone in private as well as in business environments.

What does Jolla?

Instead of solving the issues above, you provide a hot fix for MMS functionality (https://together.jolla.com/question/40658/hotfix-mms-changes-for-paarlampi-10519/). In my eyes: Features are the wrong focus as long as the basics are not solved.

While I used to use the Jolla as the only mobile phone since January, now I am starting to look for another smart-phone that ensures privacy, is secure and can reliably be used as mobile phone.