FYI, some (many? a lot?) of NC's are experience a sound wakeup failure. Google searching comes up with a lot of posts. I too had one of the 'broken' nooks. I mention it here just to assure anyone else with it, it's not a rooting issue.
The symptom is obvious and easily reproducible. When the device sleeps (by default 2 minutes) when you wake it up you don't have any sound. You have to power it down and up to get sound back which lasts until you let it sleep again. NOTE: You can't just hit the screen lock, you have to let it sleep.
Most people are reportedly getting their local B&N's to exchange it although some B&N's are now saying "Known issue, no exchanges, wait for a fix.". I had no problems personally exchanging for a good one (tested in the store with Pandora before leaving) YMMV. The manager was a bit evasive when I asked if anyone else had seen the problem and she offered, "You know you can set the screen time out for a longer period." as if that's a solution.
Since all Nooks are identical (at least before we got our hands on them) this, IMO, stems from a hardware issue. The problem does persist with 2.1 and 2.2 if your nook has the problem so don't think rooting will resolve it. It also persists from 1.0 and 1.0.1. Apparently some tech people were telling customers that 1.0.1 was going to fix the problem too, at least that's what they're saying in their posts.
Anyway, just wanted to pass the information along.
The symptom is obvious and easily reproducible. When the device sleeps (by default 2 minutes) when you wake it up you don't have any sound. You have to power it down and up to get sound back which lasts until you let it sleep again. NOTE: You can't just hit the screen lock, you have to let it sleep.
Most people are reportedly getting their local B&N's to exchange it although some B&N's are now saying "Known issue, no exchanges, wait for a fix.". I had no problems personally exchanging for a good one (tested in the store with Pandora before leaving) YMMV. The manager was a bit evasive when I asked if anyone else had seen the problem and she offered, "You know you can set the screen time out for a longer period." as if that's a solution.
Since all Nooks are identical (at least before we got our hands on them) this, IMO, stems from a hardware issue. The problem does persist with 2.1 and 2.2 if your nook has the problem so don't think rooting will resolve it. It also persists from 1.0 and 1.0.1. Apparently some tech people were telling customers that 1.0.1 was going to fix the problem too, at least that's what they're saying in their posts.
Anyway, just wanted to pass the information along.