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 2016-05-28

00:02:48 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon)
00:05:22 Quit JdGordon (Ping timeout: 246 seconds)
00:10:01 Quit alexweissman (Remote host closed the connection)
00:20:54 Quit paulk-collins (Ping timeout: 260 seconds)
00:28:13 Join paulk-collins [0] (
00:28:32pamaury[7]: here ?
00:30:29 Quit paulk-collins (Remote host closed the connection)
00:32:02 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon)
00:32:40pamauryit clearly looks like a fucking broken regex and/or regex-applying-tool and/or some other tool involve in this horrible nightmare
00:33:01*pamaury wonders if he will have to tell ct-ng to rebuild every unix tool
00:34:11pamaurymake even broken make, apparently make 3.8.1 has known issues, lovely
00:34:15 Quit JdGordon_ (Ping timeout: 250 seconds)
00:36:16***Saving seen data "./dancer.seen"
00:37:05 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon)
00:37:10 Quit JdGordon (Ping timeout: 276 seconds)
00:39:06pamaurybut how the hell do you specify the make version is ct-ng ?!
00:49:59 Quit lebellium (Quit: ChatZilla 0.9.92 [Firefox 46.0.1/20160502172042])
01:13:40pamauryok so this is a nightmare, make >= 4.0 breaks C library and make = 3.8.1 also breaks it
01:40:47 Quit ender` (Quit: All general statements are false. -- The Ultimate Law)
01:55:13 Quit girafe (Read error: Connection reset by peer)
02:09:48 Quit [7] (Ping timeout: 272 seconds)
02:09:59 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven)
02:36:17***Saving seen data "./dancer.seen"
03:07:03 Quit pamaury (Ping timeout: 260 seconds)
03:14:38 Quit yosafbridge (Ping timeout: 260 seconds)
03:15:11 Join yosafbridge [0] (
03:48:46 Quit prof_wolfff (Ping timeout: 244 seconds)
03:56:43 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon)
03:58:22 Quit JdGordon_ (Ping timeout: 260 seconds)
04:26:15 Join krabador [0] (~krabador@unaffiliated/krabador)
04:36:20***Saving seen data "./dancer.seen"
05:48:09 Quit michaelni (Read error: Connection reset by peer)
05:48:51 Join alexweissman [0] (~alexweiss@
06:04:39 Join michaelni [0] (
06:36:24***Saving seen data "./dancer.seen"
06:53:37 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon)
06:56:22 Quit JdGordon (Ping timeout: 252 seconds)
06:56:40 Quit duo8 (Ping timeout: 240 seconds)
06:57:27 Quit K1773R (Ping timeout: 276 seconds)
07:18:55 Quit nlogex (Ping timeout: 244 seconds)
07:30:57 Quit alexweissman (Remote host closed the connection)
07:31:41 Join alexweissman [0] (~alexweiss@
07:32:23 Join K1773R [0] (~K1773R@unaffiliated/k1773r)
07:36:27 Quit alexweissman (Ping timeout: 276 seconds)
07:46:51 Join einhirn [0] (
07:50:04 Join einhirn_ [0] (
07:52:02 Quit einhirn (Ping timeout: 276 seconds)
07:53:11 Quit einhirn_ (Client Quit)
08:01:06 Join JdGordon [0] (
08:01:06 Quit JdGordon (Changing host)
08:01:06 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon)
08:03:49 Quit JdGordon_ (Ping timeout: 272 seconds)
08:28:19 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon)
08:31:37 Quit JdGordon (Ping timeout: 258 seconds)
08:36:26***Saving seen data "./dancer.seen"
08:50:29 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon)
08:53:51 Quit JdGordon_ (Ping timeout: 272 seconds)
08:54:42 Join petur [0] (~petur@rockbox/developer/petur)
08:55:31 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon)
08:57:23 Quit JdGordon (Ping timeout: 246 seconds)
09:08:16 Join einhirn [0] (
09:09:08 Join einhirn_ [0] (
09:09:32 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon)
09:12:35 Quit einhirn (Ping timeout: 244 seconds)
09:12:46 Quit JdGordon_ (Ping timeout: 244 seconds)
09:36:09 Join rela [0] (~x@pdpc/supporter/active/rela)
10:01:53 Quit petur (Quit: Leaving)
10:02:43 Join duo8 [0] (~ZNC-SRV-H@
10:05:18 Join einhirn [0] (
10:05:23 Quit einhirn (Client Quit)
10:05:50 Join einhirn [0] (
10:08:16 Quit saratoga (K-Lined)
10:08:19 Quit einhirn_ (Ping timeout: 260 seconds)
10:13:45 Join alexweissman [0] (~alexweiss@
10:18:03 Quit alexweissman (Ping timeout: 240 seconds)
10:24:53 Join prof_wolfff [0] (
10:36:30***Saving seen data "./dancer.seen"
10:41:13 Join einhirn_ [0] (
10:42:40 Quit einhirn (Ping timeout: 250 seconds)
10:45:19 Quit krabador (Remote host closed the connection)
10:53:40 Join lebellium [0] (
11:01:50 Join paulk-collins [0] (
11:27:52 Join lnvx [0] (530695de@gateway/web/freenode/ip.
11:32:22lnvxHey. Does Rockbox have a boot log? Mine doesn't boot (after it fell (mere twenty cms...)) (though the OF does) and I want to diagnose it. It turns off after the logo shows up and a couple of messages flash. I think I see 'exiting'.
11:33:24lnvxI mean, the word 'exiting'.
11:39:42lnvxAlso an odd thing is that it boots and runs apparently perfectly when I press-plug it into my Linux, so it hardly seems to be a corruption of the boot partition or something.
11:39:58lnvxEven odder is that the OF seems to run perfectly as well, so it doesn't seem to be some battery issue.
11:40:38lnvxIt's as if it's only RB that doesn't want to run only when the player is not plugged in.
11:40:56alexbobplnvx: I'd just reinstall rockbox, you won't lose any settings
11:41:56lnvxAll right. I glimpsed something about 'checking the filesystem' on the forums though. Any canonical ways to do that, too, for the Clip+?
11:42:21lnvxAlso, would you know if there's a bootlog either way?
11:46:56 Join ender` [0] (
11:48:38lnvxHow do I reinstall? Just check 'bootloader'?
11:54:46 Quit alucryd (Remote host closed the connection)
11:54:49lnvx...Did that, didn't help. Same symptoms.
11:55:43alexbobplnvx: what os are you on?
11:55:54 Join alucryd [0] (~quassel@archlinux/developer/alucryd)
11:55:56alexbobpand I'd check bootloader and os
11:56:10alexbobpbootloader is unlikely to break tbh
11:56:10lnvxalexbobp: RB 3.13/a recent live-DVD Ubuntu.
11:56:24lnvx'Check', how?
11:56:27alexbobpok, just do "sudo fsck -y /dev/sdfoo1"
11:56:33alexbobpwhile it's unmounted
11:56:47alexbobpand check as in checkboxes, you said check first :P
11:56:56lnvxOh, right. Sorry. :)
11:57:06lnvxYes, that's what I did.
11:57:12alexbobpah ok
11:57:54alexbobpit's always a theoretical possibility that you created an actual hardware fault but OF is able to tolerate it
11:58:33lnvxThat's what I reckon, drives get gradually corrupted all the time, right? A small fall shouldn't break a player if it doesn't break pendrives.
12:02:14alexbobpno I don't mean corruption of the flash memory
12:02:29alexbobpI mean maybe some other piece of hardware responds differently and confuses the os
12:02:40alexbobpI'm just speculating though, I don't know what to tell ya
12:04:13lnvxsudo fsck /dev/sd{a,b} gives 'superblock could not be read', but this command seems to expect EXT filesystems, while RB uses FAT I believe...
12:12:14lnvxalexbobp: I'm horribly new, but did you mean *un*mounted? fsck seems to want to proceed when it *is* mounted.
12:12:27lnvxI mean, the nonSD partition.
12:14:17alexbobpno way, fsck definitely wants an unmounted partition :P
12:15:18alexbobpit should be fat32
12:15:22alexbobpyou can use fsck.vfat
12:15:25lnvxWell when it is mounted (mount-displayed), fsck/fsck.vfat −−yes.
12:15:29alexbobpI gotta go sleep
12:15:37lnvx−−fsck.vfat says something about a 'dirty bit not set'.
12:15:54lnvxApparently it accesses something. | I see. Thank you and bye.
12:15:55alexbobpyeah it's dirty because it's mounted
12:16:02lnvxOh, I see.
12:16:10alexbobpunmount it and try
12:16:30alexbobpwell best of luck!
12:23:14 Quit Guest85177 (Ping timeout: 244 seconds)
12:25:50 Join Guest85177 [0] (
12:36:06lnvxWhen RB is run via press-plugging the player, and then plugged out, it exits immediately, perhaps as if it misread battery as 0.
12:36:18lnvxMeanwhile the OF runs and plays well so far.
12:36:33***Saving seen data "./dancer.seen"
12:36:50lnvxThis is so bizarre.
12:41:15lnvxThe battery misreading hypothesis seems confirmed by the fact that I can only even *try* to boot RB from time to time, every half a minute or so, as if it were convinced that the battery is at its last breath.
12:41:37lnvxWhile the OF boots without fail so far. I'll try to play it for the next hour or so to confirm.
12:42:59lnvxPerhaps the fall confused some inner battery counter, or something, and it has to be depleted and then reloaded fully for both players to get a correct idea.
12:56:03 Join rela_ [0] (
12:56:06 Join alexweissman [0] (~alexweiss@
12:56:25 Quit rela_ (Client Quit)
12:58:31 Quit lnvx (Ping timeout: 250 seconds)
12:59:43 Quit rela (Ping timeout: 260 seconds)
13:00:20 Quit alexweissman (Ping timeout: 240 seconds)
13:02:13 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon)
13:05:19 Quit JdGordon (Ping timeout: 258 seconds)
13:23:59 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
13:38:09 Quit Guest85177 (Ping timeout: 244 seconds)
13:40:07 Join Guest85177 [0] (
13:56:38 Join lnxn [0] (530695de@gateway/web/freenode/ip.
13:57:20lnxnIt's me. The 'doesn't boot' error turned out to be, of course, the good old 'backlight turned off on battery'. The fall had nothing to do with it.
13:57:50Horrorcatlnxn: so the device is fine otherwise?
13:58:18lnxnI reckon so. :) (Unless a lot of turning on and off as I did while testing wears the battery in itself, but I don't think it's that bad.)
13:58:36Horrorcatnah, that shouldn’t do anything. good to hear :-)
13:58:58lnxnSorry for trouble. I had the backlight setting in quick menu so to maximize battery life. Feature request: with 'backlight: off' setting, display a message saying 'don't get surprised, the screen will turn off in three seconds'. ;)
13:59:04lnxnI'm off. Cheers. :)
13:59:17 Quit lnxn (Client Quit)
14:04:30 Quit Guest85177 (Ping timeout: 244 seconds)
14:06:40 Join Guest85177 [0] (
14:10:43 Quit Guest85177 (Ping timeout: 244 seconds)
14:12:50 Join Guest85177 [0] (
14:15:48 Join JanC_ [0] (~janc@lugwv/member/JanC)
14:16:49 Nick JanC is now known as Guest83568 (~janc@lugwv/member/JanC)
14:16:49 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC)
14:18:07 Quit Guest83568 (Ping timeout: 272 seconds)
14:23:53 Quit paulk-collins (Quit: Leaving)
14:32:33pamauryTheSeven: ping ?
14:33:26 Quit Guest85177 (Ping timeout: 244 seconds)
14:34:54 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon)
14:35:24 Join Guest85177 [0] (
14:36:37***Saving seen data "./dancer.seen"
14:37:03 Quit JdGordon_ (Ping timeout: 264 seconds)
14:39:53 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon)
14:40:00 Quit JdGordon (Ping timeout: 240 seconds)
14:40:40 Quit Guest85177 (Ping timeout: 244 seconds)
14:42:40 Join Guest85177 [0] (
14:55:51 Join girafe [0] (~girafe@2a01:cb15:82aa:1200:289e:2a07:13b1:ff8e)
15:14:57 Quit PurlingNayuki (Quit: PurlingNayuki)
15:23:16 Join bob2612 [0] (c9f2b970@gateway/web/freenode/ip.
15:23:38 Quit bob2612 (Client Quit)
15:53:08fs-bluebotBuild Server message: New build round started. Revision 28920ec, 255 builds, 13 clients.
15:57:12 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon)
16:00:02 Quit JdGordon_ (Ping timeout: 240 seconds)
16:04:25fs-bluebotBuild Server message: Build round completed after 677 seconds.
16:04:26fs-bluebotBuild Server message: Revision 28920ec result: All green
16:13:18 Join einhirn [0] (
16:17:06 Quit einhirn_ (Ping timeout: 260 seconds)
16:29:58 Join PurlingNayuki [0] (
16:34:33 Join alexweissman [0] (~alexweiss@
16:36:40***Saving seen data "./dancer.seen"
16:41:12 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon)
16:43:37 Quit JdGordon (Ping timeout: 250 seconds)
16:47:28pamaurytime for a major commit that might potentially break all imx233 targets...commit diff is +66267, -42851
16:47:50gevaertsNo sense in only trying to break one target :)
16:49:11pamauryI tried it on fuzeplus, nwze380, zenxfi3
16:49:30fs-bluebotBuild Server message: New build round started. Revision eac1ca2, 255 builds, 13 clients.
16:49:48pamauryI even checked the disassembly to check that most of the code didn't change !
16:50:15pamaurythat might be the only commit on earth whose ideal goal is that the binary is the same before and after the commit while still changing 60000 lines
16:52:20pamaurygevaerts: I tried to compile the ypr0 toolchain on my build client but no success, I seem to running in the dead end because of make, I feel that I will need to compile a very specific version of make
16:53:54gevaertsMaking a build that fragile can't have been easy!
16:55:33pamauryyeah I don't understand, make 3.8.1 seems to break the build, make 3.8.2 was banned by crosstool because it's apparently buggy, and make >= 4.0 is prohibited by the configure check of ypr0. And as far as I can tell, there are no easily downloadable make version between 3.8.2 and 4.0, at least not on
16:55:59pamaurymaybe make is not the only problem, I don't know how TheSeven did it
16:59:03 Quit alexweissman (Remote host closed the connection)
16:59:24fs-bluebotBuild Server message: Build round completed after 594 seconds.
16:59:25fs-bluebotBuild Server message: Revision eac1ca2 result: 8 errors 0 warnings
17:01:03*gevaerts *really* wants to know where that error comes from
17:05:08pamaurythis error is getting annoying
17:05:23pamauryis it always the same client ?
17:07:24gevaertsI don't think it's all of them either though
17:07:28gevaertsAt least two of them
17:07:33fs-bluebotBuild Server message: New build round started. Revision f182e2d, 255 builds, 13 clients.
17:08:45pamaurycould it be a problem with parallel make ?
17:08:55gevaertsThat target has been built by lillebror1-zagor for the last seven times, and failed once
17:09:12gevaertsYes, I think it has to be a build system issue
17:16:41gevaertsAh good, I can (sometimes) reproduce it
17:17:05fs-bluebotBuild Server message: Build round completed after 571 seconds.
17:17:06fs-bluebotBuild Server message: Revision f182e2d result: All green
17:17:07fs-bluebotBuild Server message: New build round started. Revision 423c647, 255 builds, 13 clients.
17:20:42gevaertsOK, so sometimes libcodec.a has an empty ffmpeg_bitstream.o
17:21:37pamaurythat's clearly wrong
17:26:26fs-bluebotBuild Server message: Build round completed after 561 seconds.
17:26:27fs-bluebotBuild Server message: Revision 423c647 result: 28 errors 0 warnings
17:26:28fs-bluebotBuild Server message: New build round started. Revision d245b7a, 255 builds, 13 clients.
17:26:29gevaertsI don't really like that multiple codecs all compile ffmpeg_bitstream
17:26:43gevaertsThat means it's compiled more than once, and if the .o file is the same...
17:27:09*gevaerts claims that this is a clue
17:28:48pamauryah indeed this is a very good clue
17:28:59gevaertsBasically every time a SOURCES file has ".." in it, there's a risk
17:30:43gevaertsOK, looks like that's actually not even needed...
17:31:52pamauryI would say it's more a problem of different libraries recompiling the same stuff
17:32:12pamauryeach file should be compiled once
17:32:16*gevaerts nods
17:32:46gevaertsSo if I remove ../lib/ffmpeg_bitstream.c from libwma/SOURCES and libwmapro/SOURCES, things still build, but the codec files are different
17:34:32pamaurywhat do you mean ?
17:34:58fs-bluebotBuild Server message: Build round completed after 511 seconds.
17:34:59fs-bluebotBuild Server message: Revision d245b7a result: All green
17:35:00fs-bluebotBuild Server message: New build round started. Revision 941ac16, 255 builds, 12 clients.
17:35:14pamaurythat might be just a linker thing, if they don't collect garbage and include dead code maybe ?
17:35:37gevaertsffmpeg_bitstream.o "naturally" lives in libcodec.a. Both libwma and libwmapro have ffmpeg_bitstream.c in their SOURCES *and* link libcodec.a
17:35:45gevaertsSo yes, I think it's a linker tging
17:35:57gevaertsBut I'm not entirely sure
17:36:19pamauryyeah I just realized this, libwma and libwmapro should not even include this file
17:36:52pamauryI can do a test build, if you can provide me with a wma and wma pro file ;)
17:36:59 Quit krnlyng (Ping timeout: 272 seconds)
17:37:01gevaertsAh, well :)
17:37:15pamaury(that's the hard part you have to admit)
17:38:43*pamaury is on a commit spree
17:39:40gevaertsAh, small bss differences at least
17:40:01gevaertsBut text and data are the same size
17:40:10*gevaerts is fairly sure this is fine!
17:40:31*pamaury votes for it
17:42:12*gevaerts dreams of an entirely green build table!
17:43:55fs-bluebotBuild Server message: Build round completed after 537 seconds.
17:43:57fs-bluebotBuild Server message: Revision 941ac16 result: 48 errors 6 warnings
17:43:57fs-bluebotBuild Server message: New build round started. Revision c926a52, 255 builds, 13 clients.
17:44:29gevaertsWell, if someone else doesn't spoil it with a "normal" error of course :)
17:45:41pamauryouch, that's bad, sorry
17:47:30 Join lebellium_ [0] (
17:47:38 Quit lebellium (Ping timeout: 246 seconds)
17:47:42 Nick lebellium_ is now known as lebellium (
17:47:51pamauryah trivial mistake, I forgot to not compile some code on stmp3700
17:49:27 Join krnlyng [0] (
17:52:23pamaurynext commit should fix it
17:53:22fs-bluebotBuild Server message: Build round completed after 564 seconds.
17:53:23fs-bluebotBuild Server message: Revision c926a52 result: 77 errors 12 warnings
17:53:24fs-bluebotBuild Server message: New build round started. Revision ae7dd53, 255 builds, 13 clients.
18:02:33fs-bluebotBuild Server message: Build round completed after 551 seconds.
18:02:34fs-bluebotBuild Server message: Revision ae7dd53 result: 5 errors 0 warnings
18:03:02pamaurygevaerts: there seems to be another "normal" error
18:06:49 Join nlogex [0] (
18:09:30 Join alexweissman [0] (~alexweiss@
18:14:02 Quit alexweissman (Ping timeout: 240 seconds)
18:22:47gevaertspamaury: that's for TheSeven to figure out I think
18:23:05gevaertslatex errors on build clients might well mean that the latex setup isn't good enough
18:28:28 Join krabador [0] (~krabador@unaffiliated/krabador)
18:36:43***Saving seen data "./dancer.seen"
18:37:07 Quit prof_wolfff (Quit: Bye)
18:45:34 Quit Guest85177 (Ping timeout: 244 seconds)
18:47:30 Join Guest85177 [0] (
18:47:43 Quit girafe (Read error: Connection reset by peer)
18:57:34 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier.
19:04:41 Quit Guest85177 (Ping timeout: 244 seconds)
19:12:51 Join Guest85177 [0] (
19:26:52 Quit sLite_ (Quit: No Ping reply in 180 seconds.)
19:28:28 Join sLite [0] (
19:33:40 Quit sLite (Quit: No Ping reply in 180 seconds.)
19:35:12 Join sLite [0] (
19:48:05 Quit nlogex (Ping timeout: 272 seconds)
19:51:58pamauryit doesn't really look like a latex error
19:52:09pamaurybut yeah that's his problem ;)
20:01:00 Join rela [0] (~x@pdpc/supporter/active/rela)
20:08:56desowin_is there any guide about porting linux usb drivers to rockbox? Lack of TNETV105PAP datasheet makes it a bit extra complicated
20:12:37pamaurydesowin_: not really, first because you would need to port usb gadget driver (if it exists) and then they use a completely different model
20:13:03pamaurybut you can "draw inspiration" from it
20:14:08desowin_is the rockbox usbstack model described somewhere? or is just looking at other implemented drivers the way to go?
20:14:56pamaurymostly look at the other driver, first you need to be familiar with how usb works
20:15:51pamauryI also tried to document it partly in usb.h and usb_drv.h iirc but I could add more
20:36:46***Saving seen data "./dancer.seen"
20:42:48 Quit krabador (Quit: Take The Time)
21:00:24 Quit Guest85177 (Read error: Connection reset by peer)
21:00:53 Join Guest85177 [0] (
21:02:34 Quit Guest85177 (Read error: Connection reset by peer)
21:02:57 Join Guest85177 [0] (
21:05:04 Join saratoga [0] (47ae8268@gateway/web/freenode/ip.
21:05:14saratogado we have any stats for the downloads we get per release?
21:05:45saratogacurious how many download 3.13 go for instance
21:06:16 Quit puckipedia (Ping timeout: 244 seconds)
21:11:37 Join puckipedia [0] (
21:13:46 Quit Guest85177 (Read error: Connection reset by peer)
21:14:12 Join Guest85177 [0] (
21:21:48 Join krabador [0] (~krabador@unaffiliated/krabador)
21:23:21 Quit saratoga (Ping timeout: 250 seconds)
22:01:16 Quit [Saint] (Ping timeout: 260 seconds)
22:22:23 Quit sLite (Quit: No Ping reply in 180 seconds.)
22:23:57 Join sLite [0] (
22:33:17 Quit Rower (Quit: Hmmm...)
22:36:49***Saving seen data "./dancer.seen"
22:40:45 Join nlogex [0] (
22:51:29 Join lnxn [0] (53061d07@gateway/web/freenode/ip.
22:52:00lnxnHey. Me again. I just dropped my Clip+ into water. I know I know −− there are dos&don'ts for that online. I have one specific question−−
22:52:20 Join girafe [0] (~girafe@2a01:cb15:82aa:1200:b1b9:d9a0:d402:7fe8)
22:52:20 Join python476 [0] (
22:52:42lnxnit was turned on most likely. Should I turn it off, or should I do nothing, possibly letting it turn itself off in ten minutes?
22:53:09python476hi, I'm looking for hints about fixing a sansa clip+. No rockbox on it, so I'd understand if you don't want to answer but just in case .. I asked
22:53:39lnxnI know Sansas survive contact with water.
22:54:06python476ha, seems like I'm not the only one trying to revive a Sansa
22:54:45lnxnI'd like to help but I'm understandably concerned with mine ATM.
22:54:48python476you dropped yours in water ?
22:55:05lnxnYes. Was turned on.
22:55:21lnxn says 'remove battery', but Sansas' are wired in...
22:55:24lnxnShould I still do it?
22:55:40python476I'm not in a hurry like you. I have 95% of the music backuped and my father bought me a sansa clip jam last month (prescience runs strong in my family)
22:55:54lnxnOr should I just dip it into alcohol already like it says?
22:56:28python476From the few that I know, dry it as much as you can with a hair dryier (not too hot)
22:56:53python476let the invisible traces of water evaporates by letting the circuit in open air (on a table, a radiator) for 48h
22:57:31python476but I just realized that this is for devices with no electricity running , and since the Sansa is still plugged to the battery ..
22:57:42python476Maybe cut the wires if you know about electronics ..
22:57:49lnxnI don't.
22:58:54python476then at best do what I was told .. let it dry and in two days see if you were lucky
22:59:20lnxnIt was only submerged for a second or so. I shook it as soon as I fished it out.
23:00:03python476and the case is 'new' ? no openings ?
23:00:14lnxnLet me open it.
23:00:29python476Hmm there's the audio jack socket that could let water inside
23:01:13python476Did it stop altogether or was there some random things on screen .. how is it going right now ?
23:02:18lnxnProblem is, I set it to turn off the backlight as a matter of seconds.
23:02:36lnxnSo there was nothing on the display when it dropped. Nothing was even playing so I can't just plug the headphones in and check.
23:02:44lnxnI saved battery life that way. :)
23:02:50python476I have this problem too. I never know if mine is dead or just in sleep
23:02:51lnxnThanks for your interest BTW, appreciate it.
23:03:21python476No problem, just send my your credit card number so I can bill you
23:04:54lnxnAll right, opened the thing.
23:05:18lnxnShould I just cut the battery off
23:05:46python476well is there water inside ?
23:06:36lnxnHard to tell. Was some droplets on the battery (which is foiled).
23:06:44lnxnPut a piece of toilet paper on the whole thing.
23:06:49lnxnNo water seems to remain.
23:06:56lnxnI can't find the hair dryer. >_<
23:08:32python476maybe ask ##electronics I don't want to make you cut wires, I'm a noob
23:13:42 Join ZincAlloy [0] (~Adium@2a02:8108:8bc0:1664:99d6:94cb:9261:591d)
23:19:08lnxnWell, took it apart as well as I could. If it worked all the time, the auto power off would have disabled it by now, so I'll just let it be.
23:19:26lnxnIt's the second one I did this to.
23:19:39lnxnOh well, this time it was a genuine accident, I just pulled on the cable.
23:19:45lnxnWhat's your issue, python476?
23:23:53 Join girafe2 [0] (
23:25:11lnxn(At least I had my music on a SD card, which might have survived.)
23:27:58 Quit girafe (Ping timeout: 260 seconds)
23:42:03lnxnThe SD card survived. :) Sadly I had important files on the player memory, but if the card survived, then maybe the player drive will too.
23:55:39 Quit girafe2 (Quit: Leaving)
23:56:23 Join [Saint] [0] (~hayden@rockbox/staff/saint)

Previous day | Next day