DR800 Any official information about firmware 2.0 release data?

[Dellaster]

Originally Posted by Franky

i tried the beta and one of my readers is constantly getting slower and slower in turning a page. no i went back to the default content and the problem is gone. very extremely irritating, because i can't use some features of the beta version.

I've had some slow page turning. Annoying but tolerable. Now I have a new PDF ebook from O'Reilly (Heads Up Java Second Edition) that goes kinda okay for a few pages then gets stuck in an endless delay for the next page. Well, maybe not endless. After five minutes I reset the device. Tried again and turned it off after another few minutes of waiting for a page turn. I'll read it on the eDGe instead and hope for the final 2.0 firmware update.

This particular PDF has lots of images, which may explain it (but not excuse it). It's 44MB.

[HansTWN]

I have put some machine and spare parts catalogues on my DR800. Some are up to 50 MB each, about 3-500kb per page. Page turns are pretty slow for graphic intensive pages -- I would estimate 3-5 seconds -- but once I have opened a page, then go back to a previous page, and return to the new page again it turns very quickly. Seems to cache a few pages in memory.

The whole thing is a little slow, but quite usable for keeping so many different things with me at all times, which I would not otherwise have. The best we can do with current technology -- in most places I go to they wouldn't allow me to bring a tablet computer for security reasons.

[repods]

Originally Posted by Dellaster

I've had some slow page turning. Annoying but tolerable. Now I have a new PDF ebook from O'Reilly (Heads Up Java Second Edition) that goes kinda okay for a few pages then gets stuck in an endless delay for the next page. Well, maybe not endless. After five minutes I reset the device. Tried again and turned it off after another few minutes of waiting for a page turn. I'll read it on the eDGe instead and hope for the final 2.0 firmware update.

This particular PDF has lots of images, which may explain it (but not excuse it). It's 44MB.

yes it's a bit slow with graphical pdf..
the scanned books for example..
but it caches the pages after first read..

[Dellaster]

Originally Posted by repods

yes it's a bit slow with graphical pdf..
the scanned books for example..
but it caches the pages after first read..

I'm not sweating it. Beta releases have bugs, else they'd be final releases. I'm still rather amazed at how few minuses there are (with tons of pluses) in this 2.0 beta. I can live with one PDF being unusable until the finished firmware update is done.

[repods]

yes the device with this beta is very good..
I think that it's the best e-reader on the market at the moment..
only one with a slightly bigger screen could be better..
maybe the edge ..

[CoolDragon]

Originally Posted by repods

yes the device with this beta is very good..
I think that it's the best e-reader on the market at the moment..
only one with a slightly bigger screen could be better..
maybe the edge ..

So repods, back to the original question, still this week, right? Less than 4 days to count....

[Kolenka]

Originally Posted by Shaggy

I assume you're not a programmer?

No kidding. "It is just software programming" is probably the worst assumption of the decade from the end-customer.

There are varying degrees of programmer, which will all get work done on different schedules, and the better ones tend to be expensive since they can follow the money easily.

I work for a larger company, and our product tends to run up roughly 50k bugs per major release. That's before the user gets to see anything in their hands, and it does include some pretty silly things that can easily be an hour to fix, but some take up to a week for a dev to fix them depending on how familiar they are with the code the bug is in.

Small projects tend to be very fluid, fixes for simple bugs can be pushed out to customers in days, and so on. This is true especially if the bugs found after a release are small in number (good dev practices). Large projects tend to draw in a lot more time, and iRex is pushing a modified Linux OS on their devices. Their devs are responsible for customizing that OS for their device, in addition to their apps which run on top of it to make the e-reader and actual e-reader.

I'd still be interested to see exactly what caused the delay (miscalculation on the incoming bug count on the beta? Overall schedule slips from bad estimates on how long the work would take?).

[repods]

mmm.. they are making ma say a lie .. the week is quite finished..
bad guys..

[CoolDragon]

It depends on who told you this. Sales, marketing, engineer, support, manager? For some people, it is their job to lie to customers

[HansTWN]

Originally Posted by repods

mmm.. they are making ma say a lie .. the week is quite finished..
bad guys..

Cheer up, we have our Beta, which is quite usable. I would be really annoyed if we only had 1.0. Hopefully they will finish the regular 2.0 soon, but it is not such a big deal now. Let them take a little longer and make 2.0 (almost) bug free and with additional functionality.

[repods]

damn.. never trust the sales guys..
the week is gone and nothing has been released..
the actual beta should be improved in some points..

[nsr]

为伊消得人憔悴！

[al1972]

Originally Posted by nsr

为伊消得人憔悴!

it's really helpful!

[repods]

Originally Posted by al1972

it's really helpful!

mmm.. I found another defect.. that the irex sales men lie too often

[CoolDragon]

Originally Posted by repods

mmm.. I found another defect.. that the irex sales men lie too often

Just curious, what sales man you were talking with? I don't think IREX sell devices directly.