Useless information for the day...

[hellraiser666]

You may notice that the backlight automatically switches off as you close the clamshell on the NX70V....when the LCD screen faces the thumb keyboard that is!

Close it slowly and watch the backlight magically turn off!

Interesting huh! LOL

Thank you and good night!

[rldunn]

Actually, the whole screen is turning off, not just the backlight. It's just like turning the Hold button on.

[hellraiser666]

Did you know this all along? I've had my NX70V for around three weeks, and I only discovered this 'feature' yesterday!

[rldunn]

I had an NR since June until I got my NX last weekend, and it did the same thing. I definitely didn't notice it for awhile after I got my NR, but figured it out one day. Given that it works that way, I don't know why anyone would use the Hold button on an NR/NX; seems to serve no purpose except to scare the crap out of people that bump the Hold button and can't figure out why their Clie won't work anymore!!

[CrakerZ]

BTW, with the NR, if an alarm such as World Alarm Clock, activated, it turned on the screen and backlight, even if closed. The NX no longer turns on either, though the unit turns on. The old WAC also wouldn't shut off until acknowledged, draining battery life!

[aardvarko]

The Hold switch disables the power button, which the clamshell does not.

[n2ifp]

Originally posted by aardvarko
The Hold switch disables the power button, which the clamshell does not.

Nor does it disable the camera button, unless the hold slide switch is operated.

[rldunn]

But with the hold button activated, you still have the problem with apps such as DB5, where an alarm will turn the device on and not turn it back off after two minutes.

[n2ifp]

Originally posted by rldunn
But with the hold button activated, you still have the problem with apps such as DB5, where an alarm will turn the device on and not turn it back off after two minutes.

Right, that was a problem with the NR series, fixed on the NX series.

[rldunn]

I tested it this morning and thought it was still happening on the NX, but I must have screwed up the test. I just tried it again, and you're right, it's not a problem anymore. Sorry about that.