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

Application (cutespotify) can brick device

asked 2014-02-07 17:03:02 +0300

joenix gravatar image

updated 2014-02-08 09:24:33 +0300

foss4ever gravatar image

I understand that cutespotify is still in development and has bugs, however I don't think it should be possible for a random application to mess up the OS in such a way that a recovery is needed. I suppose this could have happened with any other application as well.

As I was able to reproduce the problem here are the steps to reproduce:

  1. Install cutespotify
  2. Launch cutespotify and sigin using premium credentials
  3. Make some large playlists available online (about 150 songs)
  4. Wait for the playlists to be available offline
  5. Choose Settings in the pulley menu and choose Log out
  6. In the cutespotify login screen, choose clear cache and offline files from the pulley menu, this should finish rather quickly
  7. Choose clear cache and offline files again from the pulley menu, you'll get a message the app is not responding. Keep on waiting it will respond after a while.
  8. When all is done, try to launch any application, it won't launch.
  9. Restart the phone
  10. What happens now is probably somewhat dependent on how long you waited before restarting the phone. The first time the phone booted and the interface was in landscape (which didn't align very well) and none of the applications (nor settings) could be opened. The second time the phone booted and the welcome screen appeared, after the welcome screen the same behaviour as the first time occurred. A launcher in landscape which didn't align well and none of the applications would open.

I had to reset to factory using the recovery mode of the phone.

This was using jolla Sailfish OS

Apps installed:

  • All essential jolla apps except Android support
  • File browser
  • Warehouse (openrepos)
  • Cutespotify 1.3.0-15 (openrepos)

Suggestion: It would be nice if the phone would make a btrfs snapshot once a while (without keeping all snapshots) to which could be recovered instead of factory reset.

edit retag flag offensive close delete



Also, you wrote "brick device" in the title. I don't think that means what you think it means.

bart ( 2014-02-07 17:44:09 +0300 )edit

also you wrote take large playlist and set online.. think you mean offline

teun ( 2014-02-07 19:37:10 +0300 )edit

also think you should report this to app developers

teun ( 2014-02-07 19:38:48 +0300 )edit

Yes, the outcome is indeed the same as https://together.jolla.com/question/21898/jolla-phone-not-working-properly-after-1038-update/. "Bricked": "due to a serious misconfiguration can no longer function". I had to boot the phone in recovery mode (volume down and power button) and reset to factory. The state the phone was in made the device no longer function. Btw: The first time I installed cutespotify without openrepos installed.

joenix ( 2014-02-07 19:39:21 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2014-07-12 01:51:45 +0300

simo gravatar image

This answer given to a months old question also looks deeper into the type of questions we have here at TJC. The question itself includes an important issue, but it has gathered only 5 votes in 5 months, and there could be a reason for this. At the same time this is hopefully an acceptable answer to @joenix too:

Any applications can do harm in the OS side, especially if they run on OS version which they don't fully support / are not fully supported on. Apps outside Jolla Store might work on certain released versions of Sailfish OS very well, but they might become less functional/worse/awful over any system update.

Jolla seems to be working hard (and beeing quite strict...) with the Store and the Harbour QA policy for new apps. Hopefully also with checking of all installed Store Apps over a system update. Apps available in Jolla Store should be tested to work over updates, or become invisible and be automatically uninstalled from the phone if they are not supported after a certain update. Developers should be well informed in forehand if their apps might face issues over the next update, so that they can prepare for it with enough of time for further developing.

App developers sharing their apps elsewhere are doing great work, very great indeed. When their apps are ready to run well and use reasonable amount of the phone's resources, even over system updates, they will eventually appear in the Jolla Store. Using these apps in forehand should be seen more like beta testing and ppl should take into count that some of them might be designed - at that point - to support just one Sailfish OS version. Of cource, some of them might already be fully supported too. However, I think we shouldn't report issues about apps from other sources here at TJC at this point for two reasons:

  • First, any negative issues might have a negative effect to the app's popularity, and even to the whole app sharing platform among common users - even that the app itself has only positive sides left when it's ready
  • Second, our TJC is currently quite full of issues which should be worked over first

Our portal can work as an open portal including discussion with the app developers starting already from the idea of an app. But if the developer hasn't started the discussion here at any point, we might consider contacting him/her directly or use the forums he/she is already using, concerning apps not yet available in Jolla Store. Thanks and sorry :)

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools



Asked: 2014-02-07 17:03:02 +0300

Seen: 928 times

Last updated: Jul 12 '14