Details

If I plugin a USB cable into the Nano2G while in View Battery the DAP starts charging as if I held Menu when I plugged it in. If I were to plug the DAP in while in View Battery and I exit View Battery the player refuses to play audio when you try to go into Now Playing resulting in a crash and Menu+Select reboot.

This task depends upon

Closed by amaury pouly (pamaury)
Monday, 03 May 2010, 11:10 GMT Reason for closing: Not a BugAdditional comments about closing: The Debug Menu is mainly for developers
and there is not support for it. This
"bug" has no simple solution
and thus we don't want to add extra
code to fix it.
However, the patch in FS#11101 *might* *help* if you
*really* want to *do* something about it
(it's not a miracle solution
however).

Ah, nice catch! I saw that once, but couldn't reproduce it.
I think the part that it doesn't enter USB mode when plugged in while in the view battery screen is intentional (to diagnose charging), but the latter clearly isn't.

I get more than 1000 minutes when playing high-bitrate VBR MP3, which is quite some work for the processor, and my battery is three and a half years old and heavily used.
The battery calibration was actually done. (So the percentage gauge should be accurate, even while charging.) What hasn't been done yet is analyzing how much current the iPod will take in which situation, to estimate that correctly. I consider the whole framework for that just broken, as we have can actually measure the battery current on that device to get even better estimates without the need for calibration. (For charging, this even worse, everthing is adjusted for NiMH batteries in some certain Archos devices.) One day I'll probably come up with some better approach to this, but currently I'm hesitating to calibrate that old stuff.

This is not a bug. In fact, if you plug while in battery view, the usb thread will ask all threads to acknowledge the usb insertion.
All will do except one because you are in battery view. Consequently, it will not play audio because some crucial threads are waiting for ubs removal (buffering thread for example).
I guess the behaviour for battery is intentional but nothing can be done easily about the second part.