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.

when navigating the menus, <prev> does what menu does in the original firmware, <next> duplicates the center press, play takes you to the wps and menu toggles between where you are and the root menu, but I find I never use that

that should work pretty well. the downscaler is area average, and there's a linear upscaler as well, on color. they both look pretty good. the greyscale targets have the nearest-neighbor scaler, and it looks good enough, as far as having album art look good on 2-bit greyscale goes

there will be some cost for scaling, i'd expect it's pretty small, but nobody's run a battery bench just yet. the scaler checks quite frequently if it needs to yield to other processes, i can't get it to make playback skip, so far.

basically, the line scaler right now returns output that's been brought back down to a 0..255 range. it wouldn't be hard to drop the repiprocal multiply from it that does that, and divide by (sw*sh) in the vertical scaler instead of by sw in the line scaler and sh in the vertical

the setup functions would just store the divisor they need in the scaler context, instead of the reciprocal, and then the vertical scaler would multiply its divisor by that before calculating its scaling reciprocal

scorche: My F20 is barelly still alive. Tends to shut down on its own randomly, the audio connector is so bad that I constantly have to move the earphone plug around just to get sound on both phones, and the battery life is down to about 10hrs

it works fine and is charging while I'm playing. with an older (~1+ year ago?) pre-3.0-revision of rb it worked fine (restoration of usb power while in "car mode" would do the ~10 second rewind (as configured) and resume playing just fine)

unplugging normal power successfully pauses, but doesn't rewind+resume on restore, which is fine with me as long as it doesn't freeze. -usb remove+restore freezes in my car. (was digging trying to find a usb power source that won't attempt to mount it as a mass storage device; think I've got one somewhere)

in my car when I experience the freeze when I turn my car back on after filling up with gas: 1) power on, 2) hold menu and plugin car adapter -> usb power, 3) play audio, 4) turn off car, cutting usb power and pausing play, 5) turn car on, restoring usb power.

webguest82: I could install espeak+mbrola tools in windows which someohow integrates with SAPI, espeak provides free voices. Found all needed info there but don't remember much as it's quite a while ago

fredddy: just build http://paste.ubuntu.com/83964/ as normal firmware and keep your old bootloader. I added another comment on FS #9617 (by the way if you use 'FS#' a direct link to the task is made on the irc log)

fredddy: it tests 2 things: 1/ if the tuner is detected (if it's not you'll have to remove the panicf() from firmware/drivers/tuner/si4700.c) and 2/ reads data from a mysterious device (which might be the buttons)

bapdog: There were ports started that never got finished. The iriver iFP series has a partial port that's currently stalled, and another was for the Archos Gmini devices, which was finally stopped and pulled from the source tree when the only developer working on it was forced to stop.

I have a WPS which worked fine wrt scrolling last week, updated build today and scrolling only works in some of them and if I see correctly, the ones where scrolling works are fixed ones and in preloaded/conditional viewports it doesn't

funman: nevermind then. I'm gonna put up a some modifications of the lcd_driver. a) remove lcd_delay b) add a write another lcd_write_cmd i found in disassembly, c) modify lcd_enable a bit, and d) little fixes in lcd_update_rect

another question: I'm reading "detection of the fm tuner has failed", but I apparently overlooked what made you think so. The best way to tell if a tuner is detected is to look at the main menu. The radio item will only be there if the radio is detected at runtime

I finally have some time to install rockbox on my ippod 5.5 with 80gb hd, I use the last version of rbutil, the ipod was detected as ipo and I choose the option with the 80gb hd, everything download and install

domonoky: but I remember there was a discussion about that and it was decided the other way round. And it also worked that way. I.e. resume playback should go to the last "sound producing" screen. I'm almost 100% sure that it worked that way. That's why I'm asking.

fml: I know that if you're in the Radio screen, go to the main menu, and press play (the button equivalent of Resume Playback), it'll return you to the radio. Seems a little inconsistent, but I always just hit Play, anyway.

MarcGuay: ah, I did again (press Enter) Yes. And, actually, it behaves like the "FM radio" menu entry in the sense that the FM entry unconditionally gets you to FM. And ResumePlayback always gets you to mp3 playback. So it's ok if you ask me.

there was a commit by jhMikeS this week and the comment says it was fixed - didn't try myself though. I also don't know if it also fixes the issue that is mentioned in some forum threads that the recording screen freezes when keyclick is enabled

gevaerts: i guess it has to, but as the suggestion in the bug's comment from pondlife i think a generic pcm playback disabling while recording would be nice, to take care of both keyclick and voice in one place

The same file could very well play 10 times and fail on the 11th when i used buffering.c , and I noticed that no codecs were actually better than another (at the exception of wav which gave me longer playback before crashing)

gevaerts: I don't think I've mentioned it here yet, but I've been able to dump the 'spare' bytes from every page of the D2's NAND over USB (128MB worth) and I'm in the process of writing a PC-based TCC NAND simulator to try and work out where the remaining FTL issues lie. There is light at the end of the tunnel but lack of time is holding me back somewhat :(

gevaerts: In theory, if I write known values to the first 16 bytes of each logical sector using the OF's MSC mode, and then get a dump of the first 16 bytes of each physical sector, that combined with the spares dump "should" be enough information to nail this once and for all.

what I have seen is that some memory_handle struct would get corrupted. I remember an index (~= pointer) over 2MB (the whole SDRAM available) which makes me think of corruption, perhaps because of an overflow on the small memory target