MobileRead Forums - View Single Post - Opus Strange issues with Opus (the old white edition)

Zzyzx · 07-19-2010, 05:03 AM

I'm sorry if this information exists somwhere already but I haven't found anything yet. I'm just looking for if anyone else have the same problems I do, I'm not expecting a "fix". Though I would of course appreciate any help.

We have two Opuses in our household. They have different issues. Both are running 2.1.

Opus #1: After upgrading firmware to 2.1 the reader behaves strangely. Yesterday I made sure to check the battery level before starting reading and it said 60%. I started from the deep sleep mode, it was not completely turned off. I continued to read for 25 minutes and then activated deep sleep again. This morning the device was completely dead. No response at all, not even a blink of the light. I worked around it by plugging it into a charger for five minutes. When I started it again it went through the complete startup process and the battery indicator still said 60%.

This has happened before. On the old firmware the battery actually was depleted (I just forgot to check it regularly) but now it really does seem like the battery indicator is wrong. I base that on the time between charges, which is often 2 weeks or more. 60% after two weeks is a bit on the optimistic side.

Opus #2: This one seems to have problems with the data connection. It connects fine but it takes its time about appearing in windows. The real problem is that when I'm waking it from deep sleep, I expect that it almost immediately starts on the page I was reading last (like #1 does), but it doesn't. It starts by showing the "connecting" screen and then reboots to cycle through the complete startup.

We have tried several things to get rid of this. Reinstalled the firmware and gone through a proper connect / disconnect to the computer. The startup procedure doesn't happen every time, probably 50% of the time. An annoyingly amount anyway. I do suspect that the internal memory may be corrupted or that there may be something wrong with the memory card used. (The memory card is checked on several computers, no fault found.)

Oh, and another problem following the first problem is that if I haven't gone to the main menu and the battery suddenly is empty, the device does not remember where I was in the book. It does if I exit the book which I of course do not do on a regular basis when I use the deep sleep mode.

So, anyone else with similar trouble? Any tips on what I could try to rectify the issues? Any and all feedback is most welcome.

07-19-2010, 05:03 AM	#1
Zzyzx Enthusiast Posts: 39 Karma: 4454 Join Date: Jan 2010 Location: Oslo, Norway Device: Kindle Keyboard, Opus, Odyssey Frontlight, Kobo Mini	Strange issues with Opus (the old white edition) I'm sorry if this information exists somwhere already but I haven't found anything yet. I'm just looking for if anyone else have the same problems I do, I'm not expecting a "fix". Though I would of course appreciate any help. We have two Opuses in our household. They have different issues. Both are running 2.1. Opus #1: After upgrading firmware to 2.1 the reader behaves strangely. Yesterday I made sure to check the battery level before starting reading and it said 60%. I started from the deep sleep mode, it was not completely turned off. I continued to read for 25 minutes and then activated deep sleep again. This morning the device was completely dead. No response at all, not even a blink of the light. I worked around it by plugging it into a charger for five minutes. When I started it again it went through the complete startup process and the battery indicator still said 60%. This has happened before. On the old firmware the battery actually was depleted (I just forgot to check it regularly) but now it really does seem like the battery indicator is wrong. I base that on the time between charges, which is often 2 weeks or more. 60% after two weeks is a bit on the optimistic side. Opus #2: This one seems to have problems with the data connection. It connects fine but it takes its time about appearing in windows. The real problem is that when I'm waking it from deep sleep, I expect that it almost immediately starts on the page I was reading last (like #1 does), but it doesn't. It starts by showing the "connecting" screen and then reboots to cycle through the complete startup. We have tried several things to get rid of this. Reinstalled the firmware and gone through a proper connect / disconnect to the computer. The startup procedure doesn't happen every time, probably 50% of the time. An annoyingly amount anyway. I do suspect that the internal memory may be corrupted or that there may be something wrong with the memory card used. (The memory card is checked on several computers, no fault found.) Oh, and another problem following the first problem is that if I haven't gone to the main menu and the battery suddenly is empty, the device does not remember where I was in the book. It does if I exit the book which I of course do not do on a regular basis when I use the deep sleep mode. So, anyone else with similar trouble? Any tips on what I could try to rectify the issues? Any and all feedback is most welcome.