Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

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

#rockbox log for 2024-08-03

00:01:06***Saving seen data "./dancer.seen"
00:07:14 Join bpye [0] (~bpye@user/bpye)
00:08:10bpyeHey, I recently dug out my old Sansa Fuze+ and installed the latest daily build. I've noticed that I can hear when the disk is being accessed, and there is a pretty high noise floor. I don't remember it being like this in the past - any ideas?
00:20:47bpyeIt's not super consistent though, I just booted into the original firmware and back and now the noise is gone...
00:29:40_bilgusbpye might be something we changed or don't have the right setting for
00:30:37_bilgusI haven't used my fuze+ in a long while but it did have some noise but I never remeber it being worse than the OF
00:34:44_bilgusyou may also check the battery level I do remember something about the battery being lower causing more noise or might be reversed IDR and last thing would be check your headphone and possibly clean the headpnone plug not so sure about trying to clean the port on the device though but maybe try spinning the plug around and plug remove a few times and see if it changes
01:00
01:07:56 Quit othello7 (Ping timeout: 255 seconds)
01:20:19bpyeInteresting, I'll keep an eye out if the battery level influences it. Of course it was totally dead when I pulled it out so it's probably not super happy.
01:31:22 Quit paulk (Read error: Connection reset by peer)
01:31:30 Join paulk [0] (~paulk@about/aquilenet/user/paulk)
01:34:04 Quit Moriar (Quit: Leaving.)
02:00
02:01:09***Saving seen data "./dancer.seen"
02:12:45 Quit massiveH (Quit: Leaving)
02:21:43 Quit cnx (Ping timeout: 264 seconds)
02:32:51 Join cnx [0] (~cnx@tem.loang.net)
02:54:17bpyeAnother thing I have noticed is that if I enter debug -> battery the device hangs, hard, and I have to disconnect the battery or wait for it to die, which isn't so fun
03:00
03:05:21 Quit bpye (Quit: Ping timeout (120 seconds))
03:06:01 Join bpye [0] (~bpye@user/bpye)
03:37:28 Join lebellium [0] (~lebellium@2a01cb0405d07f0038583d01f6331649.ipv6.abo.wanadoo.fr)
04:00
04:01:13***Saving seen data "./dancer.seen"
04:03:24 Quit Bobathan (Quit: ZNC 1.8.2+deb2+b1 - https://znc.in)
04:04:43 Join Bobathan [0] (~admin@syn-065-029-248-157.res.spectrum.com)
05:00
05:03:24 Quit davisr (Remote host closed the connection)
06:00
06:01:17***Saving seen data "./dancer.seen"
07:00
07:13:00 Quit PheralSparky (Quit: Leaving)
07:33:58 Quit jj5 (Ping timeout: 252 seconds)
07:35:50 Join jj5 [0] (~jj5@100.80.216.139.dynamic.dsl.dv.iprimus.net.au)
08:00
08:01:18***Saving seen data "./dancer.seen"
08:09:19 Quit retr0id (Read error: Connection reset by peer)
08:09:40 Join retr0id9 [0] (~Retr0id@user/retr0id)
09:00
09:22:47 Join Moriar [0] (~moriar@107-200-193-159.lightspeed.stlsmo.sbcglobal.net)
10:00
10:01:22***Saving seen data "./dancer.seen"
10:33:08 Quit jjs0077018310196 (Ping timeout: 255 seconds)
10:44:56_bilgusthats definitely some new behavior, there should be a few people with fuze+ maybe they can tell us i theirs has the same issue
10:45:22_bilgusyou don't have to wait for it to die there is a recovery (mode/program)
10:47:51_bilgushttps://www.rockbox.org/wiki/SansaFuzePlusPort.html#Recovery_procedure
10:48:35_bilgusyou don't need to do anything beyond the button and usb plug it should come back up unplug reboot (automatic IIRC) and it should come back up
10:54:19_bilgusI could see flaky power causing issues for this device but not crashing showing battery info, although the fuze+ is kinda weird in that charging is peripheral and you request stuff over the i2c bus, so it could be an issue there or it could be something to do with the history graph in battery info
10:54:39_bilgusthe latter being my suspect
10:56:15 Join jjs0077018310196 [0] (~jjs007@host86-191-158-3.range86-191.btcentralplus.com)
11:00
11:06:10 Quit sebagala (Read error: Connection reset by peer)
11:10:12 Join sebagala [0] (~Burak@185.25.123.34)
11:24:21 Quit Moriar (Ping timeout: 244 seconds)
12:00
12:01:24***Saving seen data "./dancer.seen"
12:11:34 Quit flyback (Quit: Leaving)
12:40:53 Join othello7 [0] (~Thunderbi@pool-100-36-176-164.washdc.fios.verizon.net)
12:51:13 Quit othello7 (Quit: othello7)
12:53:16 Join othello7 [0] (~Thunderbi@pool-100-36-176-164.washdc.fios.verizon.net)
13:00
13:02:37 Join Everything [0] (~Everythin@109.162.122.37)
13:15:51 Join davisr [0] (~davisr@fsf/emeritus/davisr)
13:28:21_bilguschris_s (logs) re g#5862 maybe we can only display the file copying progress on file sizes > x KB probably 1MB would be max on my device and yours I'm guessing 5MB so my next question is do we have a way to check the speed of the underlying disk easily?
13:28:24rb-bluebotGerrit review #5862 at https://gerrit.rockbox.org/r/c/rockbox/+/5862 : fileop: fix slow pre-scan & flashing progress bar by Christian Soffke
13:29:09_bilgusI'm finding just the copying with no indication worse than the cylon scroller that it had before
13:56:58 Quit sebagala (Remote host closed the connection)
13:57:24 Join sebagala [0] (~Burak@185.25.123.34)
14:00
14:01:27***Saving seen data "./dancer.seen"
14:27:48 Quit davisr (Quit: yeehaw)
14:32:44 Quit Everything (Quit: leaving)
16:00
16:01:30***Saving seen data "./dancer.seen"
17:00
17:05:55 Join davisr [0] (~davisr@fsf/emeritus/davisr)
17:07:25 Join chris_s [0] (~chris_s@2a02:3037:202:730f:4cce:7c55:bada:7346)
17:16:58chris_s_bilgus: I don't know about checking the disk speed, but I added some more info and the progress bar uses the size copied instead of number of items now. Does that seem sensible to you?
17:17:32chris_sSo, at most, you may not see any progress for < 1MiB copied
17:58:50 Quit chris_s ()
18:00
18:01:33***Saving seen data "./dancer.seen"
18:43:45 Quit davisr (Remote host closed the connection)
18:57:10 Join Moriar [0] (~moriar@107-200-193-159.lightspeed.stlsmo.sbcglobal.net)
19:00
19:02:51 Quit Malinux (Ping timeout: 246 seconds)
19:11:47 Join massiveH [0] (~massiveH@2600:4040:a982:dc00:a0cc:9deb:97df:aa84)
19:28:44 Quit lebellium (Quit: Leaving)
20:00
20:01:37***Saving seen data "./dancer.seen"
21:00
21:34:19 Quit kugel (Ping timeout: 264 seconds)
21:39:33 Quit jn (Ping timeout: 252 seconds)
22:00
22:01:39***Saving seen data "./dancer.seen"
22:22:34_bilgusmuch better that even makes more sense anyway
22:54:20 Join kugel_ [0] (~kugel@ip4d146a3a.dynamic.kabel-deutschland.de)
23:00
23:00:42 Quit Moriar (Ping timeout: 252 seconds)
23:23:09 Quit paulk (Ping timeout: 260 seconds)
23:23:28 Join paulk [0] (~paulk@vpn-0-22.aquilenet.fr)
23:23:28 Quit paulk (Changing host)
23:23:28 Join paulk [0] (~paulk@about/aquilenet/user/paulk)
23:36:52 Join jn [0] (~quassel@2001-4dd3-e14e-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de)
23:36:53 Quit jn (Changing host)
23:36:53 Join jn [0] (~quassel@user/jn/x-3390946)

Previous day | Next day