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

Update from 3.0.0.11 to 3.0.0.8 suggestion [answered]

asked 2018-12-12 11:30:54 +0300

svalx gravatar image

I recently updated from version 2.2 to 3.0.0.11, but after day the system offers me to upgrade to version 3.0.0.8. My device is INOI R7 with Sailfish Mobile OS RUS. If I update it to 3.0.0.8, OS suggest for update to 3.0.0.11, and back in loop. I can not remove this suggestion from Events screen.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by svalx
close date 2019-01-11 11:06:16.301279

2 Answers

Sort by » oldest newest most voted
1

answered 2018-12-12 11:48:04 +0300

Maximilian1st gravatar image

updated 2018-12-12 11:49:15 +0300

Hi, you might want to try the solutions given at the end of this TJC thread https://together.jolla.com/question/191276/how-to-enable-blocked-developer-mode-and-fix-wrong-update-notification/?answer=194719#post-id-194719

edit flag offensive delete publish link more

Comments

Following the recommendations from this thread I killed store-client and removed /home/nemo/.cache/sailfish-osupdateservice/os-info. Also I set manual mode updates checks in Settings -> Sailfish OS updates. As result of this actions I have "Updated" state in Settings with current version 3.0.0.11, but message about 3.0.0.8 not gone from Events screen. How to remove this notification? If I do manual update, I get the original condition with update loop.

svalx ( 2018-12-12 13:14:44 +0300 )edit

Not sure but can you hold your finger on the notification and delete it? Just a wild guess and hope it works ;-)

Maximilian1st ( 2018-12-12 15:13:41 +0300 )edit

Unfortunately not. Unlike other messages, this cannot be removed with a long tap.

svalx ( 2018-12-12 15:22:00 +0300 )edit
0

answered 2019-01-11 11:05:38 +0300

svalx gravatar image

Now it is fixed.

edit flag offensive delete publish link more

Comments

1

Would you mind sharing how the issue got solved?

Or did it magically disappear?

Thanks.

simosagi ( 2019-01-11 16:35:04 +0300 )edit

It is fixed on server side. No actions needed on device, only check for update.

svalx ( 2019-01-11 17:35:16 +0300 )edit

Question tools

Follow
2 followers

Stats

Asked: 2018-12-12 11:30:54 +0300

Seen: 1,021 times

Last updated: Jan 11 '19