Quote:
Originally Posted by davidfor
With those symptoms and description of what you have, I think you need to do a factory reset and find out if it is a problem when nothing extra is installed. Until you do that, it is hard to know if it is the device or something you have added.
There is a possibility that it is a failing SD card. That could trigger issues when waking that you don't see when booting or normally, but, it would depend on exactly what part of the card was going bad.
|
I actually have the original, stock SD card of the original device somewhere. I'll probably try to reproduce the issue on that, to see if there's a stock firmware, SD card or hardware problem...
Quote:
Originally Posted by davidfor
But, it does sound like it is crashing when trying to sleep. You say it still has whatever you were reading showing when you closed the cover. That suggests the problem is early in the sleep process or even something to do with the cover. That it sleeps OK when you use the button supports this. The wake is failing possibly because of whatever happens above. It might also depend on if you close the cover after putting it to sleep. To test some of this, I would disable the sleep when closed option.
|
That's a great idea, i'll give that a shot as well. I figured the "lid close" sleep was the same as the sleep button, but who knows...
Quote:
Originally Posted by davidfor
Also, holding the power button down for 20 seconds is a way to force the device off. It is useful if the device hangs and you doesn't power off normally. After that, it should turn on normally. What happens if you power off the device when it is working OK? Does it power on with the switch?
|
That's the thing that's weird with this bug: the "20 second hold" trick just doesn't work when it crashes that way. The power led blips *once* early after pushing, and then nothing happens, it doesn't actually turn off (or, to be more specific, back on: it's hard to tell it's off in that case...)