asked 2014-12-19 12:12:09 +0300
I have been waitting for update 10 for a long long time . I don't want to wait agian just because of a bug that I will never encounter. Can Jolla PLEASE RE-RELEASE update 10 and with it came a warning about the critical bug it has. The warning should popped up before we update .
answered 2014-12-19 12:27:57 +0300
Just have a little patience. It can't be on hold for too long.
Do something fun in the meantime.
answered 2014-12-19 12:45:06 +0300
a warning isn't good enough for this one i'm afraid, this isn't a 'reboot the device and its fixed' kind of bug this is a 'you're going to need serious help' kind of bug, which is bad, and saying 'well you should have read the release notes' doesn't solve the fact that people need to send their phone into care.
I have to skip 9 for 10 and now this happened . btw Siren song new update rocks :)
sirzero1997 ( 2014-12-19 13:17:42 +0300 )editanswered 2014-12-19 12:28:13 +0300
Jolla has to fix the bug or deactivate problem before releasing again. At least I am willing to wait till Uppdate is fully functional. Even with warning some people are going to do the wrong thing and brake the device...
I personally think that's their problems since they don't know how to read properly
sirzero1997 ( 2014-12-19 12:35:04 +0300 )edit@sirzero1997 no way. you can't have people bricking their devices like this on a non-opt-in, especially when quite a few people are getting bricks from the update process itself, depending on their lock screen settings. the android power consumption is kind of game breaking, too.
meowmeow ( 2014-12-19 13:38:50 +0300 )editAsked: 2014-12-19 12:12:09 +0300
Seen: 1,017 times
Last updated: Dec 19 '14
I know that this request is already marked as answered, but
If this happens again (a software update is released, but withdrawn due to a discovered critical bug; someone doesn't feel the need for that specific function triggering the bug, and therefore requests/demands that the update will continue to roll out, _without any measurements taken, at all_), are you
willing to pay whatever the resulting costs are, for Jolla to
1) repair locked-out devices
2) ship repaired devices back
willing to be responsible for all devices that may need to be repaired due to device _owner_ having opted in, and understood the risks, but someone _else_ have borrowed their device _without their supervision_, and used the function resulting in a locked-out device
Give us an honest answer: Are you?
Personally, I'd rather have Jolla's developers fixing this thing, with a limited number of devices affected, and then continue working on upcoming updates, than having them both work on upcoming updates _and_ fix something that could have been further prevented.
phle ( 2014-12-19 17:36:11 +0300 )edit