Getting antsy here...

Any clue on when we can expect a new firmware update?

I know...I know. It will be out when its out...but man do I really want my PDF reflow bug fixed.

PDF reading was the main reason I bought this thing.

You and me both, bud.

They need to release this update soon, or they'll be missing out on a LOT of potential customers (students going back to school). What they have now is quickly becoming an antique, what with the world quickly moving to Android 2.1 and 2.2...

Like you said, I know, its done when its done... But I feel that its been a long enough time to prepare an update.

Heck, we've got Robot making his own custom firmware, and fixing bugs / adding features / finding HIDDEN or DISABLED features in the eDGe, and he is only one developer, working on it in his spare time, without any access to the source code of the OS. It seems that the eDGe developer(s) can't compare to his rate of development. Why? I know, a whole bunch of other things like bugs are popping up for the eDGe devs, but they have access to the source. They should be able to do this.

At least an estimation on when to expect an update would be... nice.

Make that three,

D4N14L, you put it very well, and even Borisd is asking for an update.
Its about time for more openness.

All,

We are definitely working hard on new features and fixes and we are not that far away from a new release. You have to understand that we have an install base, a diverse set of customers, and a pretty complicated ecosystem that we have built. It is very easy to fix or add something and break something else and affect a lot of people. I think you will like what you see in the next release as it is the result of a lot of great input we have gotten from this forum, but we are not ready to tell you when it is coming just yet. In the mean time...@brauckmiller...remind me of the PDF bug that is nearest and dearest to your heart and I will check on it for you.

DP

Thank you.

Originally Posted by D4N14L

You and me both, bud.

They need to release this update soon, or they'll be missing out on a LOT of potential customers (students going back to school). What they have now is quickly becoming an antique, what with the world quickly moving to Android 2.1 and 2.2...

Like you said, I know, its done when its done... But I feel that its been a long enough time to prepare an update.

Heck, we've got Robot making his own custom firmware, and fixing bugs / adding features / finding HIDDEN or DISABLED features in the eDGe, and he is only one developer, working on it in his spare time, without any access to the source code of the OS. It seems that the eDGe developer(s) can't compare to his rate of development. Why? I know, a whole bunch of other things like bugs are popping up for the eDGe devs, but they have access to the source. They should be able to do this.

At least an estimation on when to expect an update would be... nice.

with such an engaged, empowered and anxious community working, maybe there is room to open some of the code up to freelancers like robot and interested parties who are willing to help advance the progress.
One of the things thats entirely different between android vs mac is the open source collaboration. EE would do wonders for both agility of updates and loyalty within the community by empowering, leveraging and optimizing their dev community.
Just my 2 cents. im new here so forgive me if this has already been hammered to death as a topic.

Originally Posted by dontpanic

All,

We are definitely working hard on new features and fixes and we are not that far away from a new release. You have to understand that we have an install base, a diverse set of customers, and a pretty complicated ecosystem that we have built. It is very easy to fix or add something and break something else and affect a lot of people. I think you will like what you see in the next release as it is the result of a lot of great input we have gotten from this forum, but we are not ready to tell you when it is coming just yet. In the mean time...@brauckmiller...remind me of the PDF bug that is nearest and dearest to your heart and I will check on it for you.

DP

In PDFs that have images on the page and reflow is enabled, you cannot advance to the next page in the PDF.

Honestly, the thing is collecting dust due to this bug. I just don't want to have to wrestle with the eInk side to make it work. I'd have to use the page jump feature and it really just makes it too much of a pain to deal with.

Thanks

Craig

Craig,

I think this is specific to some books, from what I hear. It should not be the case on all PDFs (I personally have never seen it happen and I work on the device a lot). By "wrestling" you mean that when this bug manifests itself while you are reading and you get hung up on a graphic, the work around of using the go to page # function is difficult. I can understand that. This is a bug in the underlying Adobe Reader Mobile SDK that we use as the foundation for our reader. One of the things that is happening with our next release is that we are upgrading to the 9.1 version of the RMSDK. The engineering team feels that this function has been dramatically changed for the better so you should have relief fairly soon.

DP

Originally Posted by netmentor

with such an engaged, empowered and anxious community working, maybe there is room to open some of the code up to freelancers like robot and interested parties who are willing to help advance the progress.
One of the things thats entirely different between android vs mac is the open source collaboration. EE would do wonders for both agility of updates and loyalty within the community by empowering, leveraging and optimizing their dev community.
Just my 2 cents. im new here so forgive me if this has already been hammered to death as a topic.

@netmentor,

No, you are right. We really want to get our SDK released as soon as possible. We are on schedule, though. We had planned to release it at the end of this year and we still hope to. It is not as simple as just shipping it out, though, as we also need to support it. Right now we do not have an SDK to release that we feel comfortable supporting. While we do have a lot on the plate right now, we value our developer customers and are also anxious to open things up to the creativity of our user community.

DP