Quote:
Originally Posted by HarryT
Thats probably because it only existed for a few weeks before Bookeen fixed it. The Gen3's was released in November; Bookeen fixed the bug in December.
|
The interesting thing is when somebody know that it was possibly fixed. And that was much later. It was when you updated the firmware and confirmed it and that was a month ago or so.