So yesterday, I plugged my headphones in and started up Canola to listen to music, and (to my considerable embarrassment, since I was in a library), it played over my N800's speakers, not the headphones. Of course, I checked the connection, and it was definitely all the way in and everything.

Also, I experimented with it a bit, and even with the headphones in, all system sounds also went over the speakers. Additionally, plugging in or removing the headphones didn't wake the display when it was dim or off like it normally does.

All this made it seem like more of a hardware problem, and not just something in software. (Also, I haven't used anything like fm radio which can switch between the two in a really long time).

Anyway, as the battery was low, I turned it off, took the battery out briefly, and then put it back in and charged it (with the unit off) to reset it as thoroughly as possible (short of flashing, of course). When I powered it back on this morning, it works fine, so it apparently isn't that the headphone jack has gotten totally disconnected from it or anything like that.

Still, I've never heard of this happening before, and I'm a bit worried. Is this something I should consider contacting Nokia about? I've had the device for almost three months now, so I doubt I can go back to the vendor (amazon.com) about it, but its still under warranty.

do you have the radio applet installed, running on your desktop?

if so, you might have accidentally hit the "speakers" button, and this automatically plays everything on the speakers, although the earphones are plugged in.

hope this helps

Ilia

No, I don't. I hadn't used it for a really long time, and had definitely rebooted (probably multiple times) since using it last. That crossed my mind too, but, yeah. Also, that the screen didn't wake up when it was plugged/unplugged, which it should have regardless.

If it happens to you again, you can try the following command (in xterm) to test if the hardware is reporting correctly the presence of the jack:

This happened to me once,and never again. I'm almost certain it's a software issue rather than hardware. I don't remember what I was doing when it happened to me but I think it was after a freeze-up.
You sure did get unlucky though, having that happen at a library :]

Hm, yeah. It hasn't been a problem since. I suppose it must've just been a software problem; I mean, it's evidently a software switch.

Thanks for that terminal command, as well, jldiaz. I didn't know that was something you could check.