View Single Post
Old 12-22-2012, 05:45 PM   #33
pe1dnn
Enthusiast
pe1dnn ought to be getting tired of karma fortunes by now.pe1dnn ought to be getting tired of karma fortunes by now.pe1dnn ought to be getting tired of karma fortunes by now.pe1dnn ought to be getting tired of karma fortunes by now.pe1dnn ought to be getting tired of karma fortunes by now.pe1dnn ought to be getting tired of karma fortunes by now.pe1dnn ought to be getting tired of karma fortunes by now.pe1dnn ought to be getting tired of karma fortunes by now.pe1dnn ought to be getting tired of karma fortunes by now.pe1dnn ought to be getting tired of karma fortunes by now.pe1dnn ought to be getting tired of karma fortunes by now.
 
Posts: 31
Karma: 1315217
Join Date: Oct 2011
Device: PRS-T1
Quote:
Originally Posted by entodoays View Post
Is this a possibly related issue?
I just read thought this thread and really wonder what you expect from us.

First there is a page full of messages with attempts to reset your device. Then pages with your attempts to find the cause of your problem, providing hunches about buggy epubs from Calibre, then again not, now blaming the browser without specifying what you browsed. And it goes on and on.

Maybe you think, or at least act, like this is your personal log where you can scribble down every angle you try on your problem, but it is not. We, the reader, get a shit load of inconsistent and incomplete information. I can's see how we are supposed to help. And even if we could give you a hint it is most likely useless because you already got new insights and digged into another area already.

So some general advice about trouble shooting:

1) Bring the device back into its original state using rupor's advice. This is a known good state, the baseline. If the device does not work correctly in this state any analysis is futile. There is no need to go on if you do not get this right and nobody will be able to help you since this works okay for all other users. You should be able to get this right unless your reader is really broken. In the latter case it should be send to Sony for repair.
2) Don't throw everything back at once. Instead do it ONE thing at the time, and after each time test, test and test (seriously!).
3) When the problem occurs, make a note of the last step you did. Then repeat the procedure from point 1), but at point 2) do everything EXCEPT the step that caused a problem, skip over it.
4) When all other changes are applied in the end, except of the steps that caused problems, then you should have a fine working reader and a comprehensive list of the steps or activities that causes problems.

If you still want a solution form us, then come back after step 4 and tell which steps fail, what EXACTLY you did before this step, starting from the moment you restored the reader at step 1, then what it is you did EXACLTY at the failing steps, what kind of problems it caused and how it was detected. Describe it such way that someone else can replay/repeat your steps. So "start browser" is not enough, tell us how you started it and which site you visited and how you got back out of it to do your tests of the reader responsiveness.

If you are not systematic about it nobody can help you. It becomes blind guess work and also you will not be able to verify a solution if you cannot repeat the process steps leading to the problem. There is no need to report about the intermediate steps during your problem analysis. I hope this helps.
pe1dnn is offline   Reply With Quote