Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
FlynDice:
re: abi forums and "temp brick" reports.
Please don't be alarmed by ^^^ there are no bricks being reported! Just a temporary unresponsiveness for 2-3 mins.
From practical experience I think this is related to the v1.0 bootloader. I was using one I compile myself for awhile and then last week tried the v1.0 to see if it made any difference with some of the things I was working on. It didn't but I started to get these "temp bricks". Holding the pwr button for 10 secs did not reset but 20 secs did reset. I'm now running a bootloader produced from r25821 and have not had any more of these "temp Bricks" so I've got the feeling this is bootloader v1.0 related.
bilditup1:
I got lazy about this graph thing. Anybody have a simple tool to do it for me?
My battery_bench.txt is attached.
My Fuze v2, build 25836, quit at 15:48:06, after starting at 93% (but 100% according to the OF). This is with 5-track alt-present-extreme LAME-encoded mp3 album that was 40 minutes long. Flat EQ, no replay gain, and volume at -20db.
In other news - I tried playing some NSFs and SPCs today on a whim. The NSFs played fine, but the scroll light was at the disco. SPCs played at an absurdly low volume, and also had scroll light problems. I don't know if these are issues specific to this port or Rockbox in general. While plugged in, it looks like the light now comes on and off at random during mp3 playback, too.
I've experienced a few crashes while scrolling through menus, with and without music playing, but otherwise, everything looks stable. Will investigate charges of volume being too low next - yay dual boot!
funman:
--- Quote from: FlynDice on May 06, 2010, 01:41:31 PM ---re: abi forums and "temp brick" reports.
From practical experience I think this is related to the v1.0 bootloader.
--- End quote ---
Very likely, there were some fixes added after bootloader release: I think of the cache functions particularly, and also some race condition with the PMU ascodec register.
--- Quote from: bilditup1 on May 06, 2010, 01:48:56 PM ---I got lazy about this graph thing. Anybody have a simple tool to do it for me?
--- End quote ---
Have a look at gnuplot
--- Quote from: bilditup1 on May 06, 2010, 01:48:56 PM ---My battery_bench.txt is attached.
My Fuze v2, build 25836, quit at 15:48:06, after starting at 93% (but 100% according to the OF). This is with 5-track alt-present-extreme LAME-encoded mp3 album that was 40 minutes long. Flat EQ, no replay gain, and volume at -20db.
--- End quote ---
Thanks, did you force CPU boosting?
I had 18:20 on my fuzev2 (starting with 100% in OF and 94% in rockbox)
--- Quote from: bilditup1 on May 06, 2010, 01:48:56 PM ---While plugged in, it looks like the light now comes on and off at random during mp3 playback, too.
--- End quote ---
Yeah this is normal, read the last pages of this thread.
yimmu:
Battery benchmarking for Fuze v2, build r25814.
Volume was at -14db, playing a 17 track mp3 album at 128kb/s which was being played off a µSD card, with the equalizer was set to the preset 'rock'.
bilditup1:
I forced nothing; I'm not quite sure how to boost speeds at all. Maybe the backlight was on when I wasn't looking (in my pocket). Maybe I checked the player one too many times. Maybe it's because the tracks were on the microSD? Should I try again? Will look up gnuplot.
I'd like to echo problems with recording (panics right and left when trying to change options) and charging (stops at ~67%).
-e
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version