Quote:
Originally Posted by JSWolf
But this bug (as you call it) can be patched away in two different ways. You know where to find the patches and you know you can update to 3.17.0 without getting caught by sickle.
|
If we gonna argue if something is a bug or not, the end is there.. I call unwanted behaviour a bug.
I know how to patch it,but there is more (ok hard to imagine) then M.R. on this world.
There are so, so many people that are only just scared by the word patching... It is not about what we can or not, it is what all those customers outside M.R. experience.
Do they see the connection with a sudden rebooting device and the new firmware, especially when it starts after a few days ??
How many device would be sended back as defect / warranty ?
How does the dealer handle this.. I know of dealers that "leave it on the shelf" for about 3 weeks before even sending it back to their delivery company.
Then you can wait for a month or more before your reader comes back, without being repaired because nothing is there to repair..
For as far as I know there is no changed manual that says: when your device becomes unstable, it will reset itself, this is normal.. in practice, a lot of people will try to use the pinhole to stop this unwanted behaviour..and that doesn't solve it..
And.. why is it that we are used to the word patching and find it normal to do.. a patch is for an emergency, not a common used thing..
The patches I use are not fancy patches, just the ones needed to have a normal reading experience..
This are consumers devices, not hobby projects for advantage users..