Click in the nick column to highlight everything a person has said.
The icon identifies that the person is a core developer (has commit access).

Notice: Only Gecko based browsers prior to FF4 support the multipart/mixed "server push" method used by this log reader to auto-update. Since you do not appear to use such a browser, this page will simply show the current log, and not automatically update.

do I need to force it? i just plugged it in and it said discharging until i added ac power

00:15:18

Quit ender`(Quit: "I'm the head wizard now. I've only got to give an order and a thousand wizards will ... uh ... disobey, come to think of it, or say 'What?', or start to argue. But they have to take notice."-- Archchancellor (Terry Pratchett: Lords and Ladies))

I think people have argued against it, but I honestly can't remember anything beyond "some buttons could have unexpected behaviour like fast forward" which doesn't seem much of a real problem / likelihood (I think people will realize holding a button will do whatever that button *does* until they insert the USB cable)

JdGordon|: Well there still needs to be a decision for cases where a menu can't come up, or be used for whatever reason, so menuless behaviour is still good whether or not a menu will go in in the future.

JdGordon|: right now, test_codec calls "do_menu" and then checks the result to figure out what to do, what would I need to have an option to set boosting to yes/no without returning from teh do_menu call ?

Say I install RB to a Fuze v2, and all is good. Later I upgrade RB, but some core RB boot file gets corrupted, and RB won't boot. Does this mean I will have to CRACK OPEN my player in order to shot the two pins that allow recovery mode?

If you can't boot without power from USB, isn't going into USB charging mode acceptable? You could then replug if you'd like UMS much like you have to if you're charging anyway and decide you want UMS access.

I'd really like a button to drop out of MSC, honestly, for my car where trying to hold down things is impractical, or where the player is waked by USB power and then enters MSC and replugging the cable is potentially unsafe while driving.

My ideal would be an option to decide if the default is connect or charge, every button (or nearly every button) causing it to perform the other action, and a button that gets me out of MSC if I'm accidentally in it without having to replug.

saratoga: that code isn't originally mine (although I may have accidentally removed it at some point and then readded it), but the reason for it is that (at least on MTP H10s) you have to hold the right button to get to the ROM USB mode, so in practice you have to hold the right button already before the reboot

depends on your way of using it. I just remember reports about slowdown when all three is enabled (not sure if this is still the case). Some of these could also help decreasing boot time when enabled (as gevaerts mentioned)

gevaerts, rockbox totally captured my interest in portable music, and by the day i rockboxed my fuzev1 , i'm only really interested with deveopment on it. I really would contribute, but i'm not a developer

pixelma: It shouldn't be that it looped around because I played on it for a bit before the screen started just going to black, also I have no idea how to reset the settings without being able to see the screen and I have no cord atm to hook it to my pc

some players let you reset settings during boot by holding a specific button. I'm not sure if this is implemented on the Fuze and which button it would be if it is, you could search around in our manual

it's not in the Fuze (v2) manual where it would be (in "Advanced Settings > Managing Settings", a not under the description of the "Reset Settings" menu item). So it's either not implemented yet or an oversight in the manual source

bertrik: it goes from 0 (total black) to 255 (total white) but on mine at least it should actually only be 0 to 127 (127 is total white too and 128 is total black again), It is as if the range is there twice but I remember someone looking into some datasheet and saying 256 steps would be correct...

pixelma, I'm trying to figure out if the full range is perhaps possible by configuring some other part of the display. There is a note in the ds that says that under some circumstances the range is less. If that's not possible, I'm inclined to just reduce the range to 0-127 to avoid the wrap at 128

OK I've found the commit that broke a function for me (perhaps it's a "fix"?). The way it used to work on my e200v1: Location: WPS > Context Menu > Playlist Menu > Playlist > View Current Playlist. Function: Press Play/Pause button ("up" button) returned you to WPS. Since r28139 or r28140 (same author/file) this button now does nothing. Anyone care to take a look? http://svn.rockbo

JdGordon: You said you think there is already a patch for the Play/Pause button not returning to WPS from "View Current Playlist". I can't find it. Were you here ~45 minutes ago when I was talking about the revision that broke me? (r28139 or 28140) Those were committed on Sept. 22, so the bug/patch you were thinking of −− is it that young?