[bug] update to 1.1.7 hang at 95 - 99% [answered]

Question

10

[bug] update to 1.1.7 hang at 95 - 99% [answered]

asked 2015-07-15 17:54:04 +0300

evo3de

13567 ●164 ●227 ●231

http://www.tomatenmark.ne...

updated 2015-07-17 19:08:30 +0300

eric

12967 ●88 ●133 ●123

https://twitter.com/erkki...

* Broken device? *

Update seems to be hang about 99% (bar near at end) since 30 min (stand in portait, with power pluged in)

stay tuned may be it comes back to life

Update: 45 min no change.. still screen is on at 99% and device hang in nirvana before reboot. No reaction on orientation change or something else. Seems to be a broken device

Update: 1h 15 min same state.. it´s dead :(

Update: 1h 30 min i will turn off my device (replace battery), replug battery and boot... Device starts... Enter pin... deaktivating plane mode.. IT`S ALIVE - showing ver 1.1.7.24 and now i ignoring the update notification to 1.1.7.24

Update: Now all is ok (thx to @tmi)

Remark: It is a Bug to give no feedback for such a long time, may the statusbar is wrong calculated or something hangs and will be killed afer 2h timeout

The question has been closed for the following reason "the question is answered, an answer was accepted" by Alex
close date 2017-10-03 13:35:24.906131

Comments

1

Happened to me too, but after waitin looooong time (about 2 hours) the update finally finished and everything is ok.

kkarioja ( 2015-07-15 18:05:13 +0300 )

4

Maybe I was too hasty but I also pulled the battery somewhere between 1-2hrs. I got rid of the update notification with this (only I renamed the os-info to os-info.bak and there was no re-install, but anyway):

Delete the file/home/nemo/.cache/store-client/os-info
Stop the store-client process (for e.g. pkill store-client)
Reopen Settings app, check for updates again and attempt to install the OS update again

tmi ( 2015-07-15 18:17:22 +0300 )

Isn't it the the file system optimizations mentioned in release notes?

"When updating from 1.1.6 your device might go through lengthy file system optimizations before installing the update."

AliN ( 2015-07-15 20:58:01 +0300 )

1

@AliNa at least on my device, the optimization was a separate process, before backup, download and installation.

tokaru ( 2015-07-16 00:19:37 +0300 )

what is your backup size? noticed about 5minutes or so arround 95-99% i had about 6GB free because i deleted all backups (3GB) and made new backup without galery.

second jolla was maybe little slower and it has with about 700mb in backup files

both are simillar, without alien, no 3d party apps, only LEDs are adjusted....

pan tau ( 2015-07-16 02:37:49 +0300 )

see more comments

Happened to me too, but after waitin looooong time (about 2 hours) the update finally finished and everything is ok.
kkarioja ( 2015-07-15 18:05:13 +0300 )
Maybe I was too hasty but I also pulled the battery somewhere between 1-2hrs. I got rid of the update notification with this (only I renamed the os-info to os-info.bak and there was no re-install, but anyway):
Delete the file/home/nemo/.cache/store-client/os-info
Stop the store-client process (for e.g. pkill store-client)
Reopen Settings app, check for updates again and attempt to install the OS update again
tmi ( 2015-07-15 18:17:22 +0300 )
Isn't it the the file system optimizations mentioned in release notes?
"When updating from 1.1.6 your device might go through lengthy file system optimizations before installing the update."
AliN ( 2015-07-15 20:58:01 +0300 )
@AliNa at least on my device, the optimization was a separate process, before backup, download and installation.
tokaru ( 2015-07-16 00:19:37 +0300 )
what is your backup size? noticed about 5minutes or so arround 95-99% i had about 6GB free because i deleted all backups (3GB) and made new backup without galery.
second jolla was maybe little slower and it has with about 700mb in backup files
both are simillar, without alien, no 3d party apps, only LEDs are adjusted....
pan tau ( 2015-07-16 02:37:49 +0300 )

Accepted Answer

14

answered 2015-07-16 10:17:49 +0300

evo3de

13567 ●164 ●227 ●231

http://www.tomatenmark.ne...

updated 2018-06-13 15:28:40 +0300

jovirkku

23703 ●213 ●311 ●247

moderator

So @tmi told the right:

Delete the file /home/nemo/.cache/store-client/os-info
Stop the store-client process (for e.g. pkill store-client)
Reopen Settings app, check for updates again.

This solved the "Update available" - Problem

link

Comments

Thanks a lot :)

malibu1106 ( 2015-08-31 22:19:37 +0300 )

@evo3de thanks works like a charm, updated to 2.0.5.6 and it was erroneously displaying last supported software install 2.0.4.14.

DarkTuring ( 2016-12-01 22:32:41 +0300 )

Thanks man! I ran to this after upgrading to 2.1.3.7

martonmiklos ( 2017-12-02 11:59:13 +0300 )

Thanks, this worked for persistent upgrade notification with Mouhijoki 2.2.0.29

Spam Hunter ( 2018-06-01 17:59:02 +0300 )

Thank you, this worked for me. Jolla 1

Vinodh ( 2018-06-03 21:11:26 +0300 )

see more comments

Answer 2

3

answered 2015-07-16 00:13:18 +0300

Leinad
1566 ●16 ●26 ●29

it's not a bug, just be patient, for me it took more than 2 hours, but everything went fine.

link

Comments

3

So, 2h would be fine, but without feedback and a statusbar that is on 99% and not moving - it is indeed a bug.

evo3de ( 2015-07-16 10:15:43 +0300 )

If the final update can take that time, users should be warned. The update on my jolla took about an hour. After 15 minutes with the statusbasr almost at the end I went to this place and saw this thread and left the jolla. About an hour later I checked the jolla and it was back alive.

richhanz ( 2015-07-17 12:55:10 +0300 )

add a comment

[bug] update to 1.1.7 hang at 95 - 99% [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by Alex
close date 2017-10-03 13:35:24.906131

Comments

2 Answers

Comments

Comments

Question tools

Stats

Related questions

[bug] update to 1.1.7 hang at 95 - 99% [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by Alex close date 2017-10-03 13:35:24.906131

Comments

2 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "the question is answered, an answer was accepted" by Alex
close date 2017-10-03 13:35:24.906131