search

lumica89 / prs-plus

Automatically exported from code.google.com/p/prs-plus
0 stars 0 forks source link

Prs-650: Random but not-so-rare complete freezes #362

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Your model / PRS+ version?
PRS-650 / Nightly build 168

What steps will reproduce the problem?
1. I'm sorry I haven't found an exact trigger. I know you, as developers, hate 
this kind of bug reports. But I cannot give better one.

2. My problem is that WITHOUT using apps, or even without having ever used apps 
BTW, (as a distinction to bug 191), my PRS-650 is suffering quite frequent 
freezes. When they happen the device gets completely unresponsive till I press 
the Reset button and then power button. When the device completely reboots, it 
usually doesn't remember the position I had in my current ebook before the 
crash happened.

3. Since last Sunday (launch of custom dictionary support), so in just one 
week, I've suffered 2 blocks and both of them have occurred performing 
dictionary actions. The first one happened when I was calling the dictionary by 
double tap on a word and the second one when I pressed OK in the dictionary 
swap menu, from Oxford American English to English-Spanish Oxford dictionary. 
(I haven't used any of the new custom dictionary support features yet, I don't 
have any custom dictionary installed).

But nevertheless, I've suffered similar freezes before this build, so I guess 
that the new dictionary support is not the root problem.

4. Possibly the best hint I can give you. I have PRS+ stand-by options set to 
just Sony default behaviour and within Sony options I've got stand-by setting 
with Picture On/Message Off. All my stored photos (all in internal memory) are 
selected as possible stand-by photos.

Well, in this situation I've noticed that sometimes when I go to stand-by mode, 
NO photo is shown. Just a white screen appears. When this bug happens, I 
"think" I've noticed that the freeze is really near ahead...

5. Nevertheless I'll try to narrow/find a reliable trigger but it seems quite 
hard

Original issue reported on code.google.com by alr...@gmail.com on 21 Dec 2012 at 9:38

GoogleCodeExporter commented 8 years ago 
Thanks for bugreport.

Note that the plan is abandoning 2.1.x and working on 2.2.x based on (much more 
stable and performant) 2.0.x adding features in small chunks.

Original comment by msukhias...@gmail.com on 21 Dec 2012 at 9:43