View Single Post
Old 05-05-2014, 10:52 PM   #8
omnimodis78
Enthusiast
omnimodis78 is kind to children and small, furry animalsomnimodis78 is kind to children and small, furry animalsomnimodis78 is kind to children and small, furry animalsomnimodis78 is kind to children and small, furry animalsomnimodis78 is kind to children and small, furry animalsomnimodis78 is kind to children and small, furry animalsomnimodis78 is kind to children and small, furry animalsomnimodis78 is kind to children and small, furry animalsomnimodis78 is kind to children and small, furry animalsomnimodis78 is kind to children and small, furry animalsomnimodis78 is kind to children and small, furry animals
 
omnimodis78's Avatar
 
Posts: 31
Karma: 6916
Join Date: Jun 2013
Location: Ontario, Canada
Device: Kobo Aura H20
@TechniSol - You are absolutely right, and I agree - better to have a weird restore than a bricked device, granted. If this was a fluke, OK, so be it - but if it wasn't, if there was some order to the madness, then I have to say it's a rather drastic first step from a programming perspective to resort to a full and immediate system wipe and restore. In my days of programming, a call would have been made for the OS to restart. This usually resolves any memory corruption, system hang or critical but not fatal errors. I saw something rather disturbing and boy I wish I could make you guys see it: just imagine it though, typing in something on the keyboard, pressing "go" and a restore starts. I mean it just didn't seem like there was even any time for things to go wrong, it just wiped data and restored. Anyways, yes, at least it's restored and all - now I just have to hope it's not a bad device, or that there's an issue with the firmware.
omnimodis78 is offline   Reply With Quote