--- Log for 28.05.116 Server: tepper.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 5 days and 9 hours ago 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] (~paulk@gagarine.paulk.fr) 00.28.32 # [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.40 # it 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.11 # make 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.06 # but 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.40 # ok 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] (~yosafbrid@68.ip-149-56-14.net) 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@50.95.191.79) 06.04.39 Join michaelni [0] (~michael@chello213047041020.graz.surfer.at) 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@50.95.191.79) 07.32.23 Join K1773R [0] (~K1773R@unaffiliated/k1773r) 07.36.27 Quit alexweissman (Ping timeout: 276 seconds) 07.46.51 Join einhirn [0] (~Miranda@p4FC12995.dip0.t-ipconnect.de) 07.50.04 Join einhirn_ [0] (~Miranda@bsod.rz.tu-clausthal.de) 07.52.02 Quit einhirn (Ping timeout: 276 seconds) 07.53.11 Quit einhirn_ (Client Quit) 08.01.06 Join JdGordon [0] (~jonno@210-84-21-62.dyn.iinet.net.au) 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] (~Miranda@p4FC12995.dip0.t-ipconnect.de) 09.09.08 Join einhirn_ [0] (~Miranda@bsod.rz.tu-clausthal.de) 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@117.6.48.103) 10.05.18 Join einhirn [0] (~Miranda@p4FC12995.dip0.t-ipconnect.de) 10.05.23 Quit einhirn (Client Quit) 10.05.50 Join einhirn [0] (~Miranda@p4FC12995.dip0.t-ipconnect.de) 10.08.16 Quit saratoga (K-Lined) 10.08.19 Quit einhirn_ (Ping timeout: 260 seconds) 10.13.45 Join alexweissman [0] (~alexweiss@50.95.191.79) 10.18.03 Quit alexweissman (Ping timeout: 240 seconds) 10.24.53 Join prof_wolfff [0] (~prof_wolf@82.159.0.123.dyn.user.ono.com) 10.36.30 *** Saving seen data "./dancer.seen" 10.41.13 Join einhirn_ [0] (~Miranda@bsod.rz.tu-clausthal.de) 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] (~chatzilla@89-93-179-187.hfc.dyn.abo.bbox.fr) 11.01.50 Join paulk-collins [0] (~paulk@gagarine.paulk.fr) 11.27.52 Join lnvx [0] (530695de@gateway/web/freenode/ip.83.6.149.222) 11.32.22 # Hey. 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.24 # I mean, the word 'exiting'. 11.39.42 # Also 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.58 # Even odder is that the OF seems to run perfectly as well, so it doesn't seem to be some battery issue. 11.40.38 # It's as if it's only RB that doesn't want to run only when the player is not plugged in. 11.40.56 # lnvx: I'd just reinstall rockbox, you won't lose any settings 11.41.56 # All right. I glimpsed something about 'checking the filesystem' on the forums though. Any canonical ways to do that, too, for the Clip+? 11.42.21 # Also, would you know if there's a bootlog either way? 11.46.56 Join ender` [0] (krneki@foo.eternallybored.org) 11.48.38 # How do I reinstall? Just check 'bootloader'? 11.54.46 Quit alucryd (Remote host closed the connection) 11.54.49 # ...Did that, didn't help. Same symptoms. 11.55.43 # lnvx: what os are you on? 11.55.54 Join alucryd [0] (~quassel@archlinux/developer/alucryd) 11.55.56 # and I'd check bootloader and os 11.56.10 # bootloader is unlikely to break tbh 11.56.10 # alexbobp: RB 3.13/a recent live-DVD Ubuntu. 11.56.24 # 'Check', how? 11.56.27 # ok, just do "sudo fsck -y /dev/sdfoo1" 11.56.33 # while it's unmounted 11.56.47 # and check as in checkboxes, you said check first :P 11.56.56 # Oh, right. Sorry. :) 11.57.03 # ;) 11.57.06 # Yes, that's what I did. 11.57.12 # ah ok 11.57.54 # it's always a theoretical possibility that you created an actual hardware fault but OF is able to tolerate it 11.58.33 # That'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.14 # no I don't mean corruption of the flash memory 12.02.29 # I mean maybe some other piece of hardware responds differently and confuses the os 12.02.40 # I'm just speculating though, I don't know what to tell ya 12.04.13 # sudo 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.14 # alexbobp: I'm horribly new, but did you mean *un*mounted? fsck seems to want to proceed when it *is* mounted. 12.12.27 # I mean, the nonSD partition. 12.14.17 # no way, fsck definitely wants an unmounted partition :P 12.15.18 # it should be fat32 12.15.22 # you can use fsck.vfat 12.15.25 # Well when it is mounted (mount-displayed), fsck/fsck.vfat --yes. 12.15.29 # I gotta go sleep 12.15.37 # --fsck.vfat says something about a 'dirty bit not set'. 12.15.54 # Apparently it accesses something. | I see. Thank you and bye. 12.15.55 # yeah it's dirty because it's mounted 12.16.02 # Oh, I see. 12.16.04 # Thanks. 12.16.05 # :P 12.16.10 # unmount it and try 12.16.30 # well best of luck! 12.23.14 Quit Guest85177 (Ping timeout: 244 seconds) 12.25.50 Join Guest85177 [0] (~Slayer@c-69-255-136-113.hsd1.va.comcast.net) 12.36.06 # When 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.18 # Meanwhile the OF runs and plays well so far. 12.36.33 *** Saving seen data "./dancer.seen" 12.36.50 # This is so bizarre. 12.41.15 # The 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.37 # While the OF boots without fail so far. I'll try to play it for the next hour or so to confirm. 12.42.59 # Perhaps 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] (~x@p200300764D796F005DBB77515501A3CB.dip0.t-ipconnect.de) 12.56.06 Join alexweissman [0] (~alexweiss@50.95.191.79) 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] (~Slayer@c-69-255-136-113.hsd1.va.comcast.net) 13.56.38 Join lnxn [0] (530695de@gateway/web/freenode/ip.83.6.149.222) 13.57.20 # It'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.50 # lnxn: so the device is fine otherwise? 13.58.18 # I 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.36 # nah, that shouldn’t do anything. good to hear :-) 13.58.58 # Sorry 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.04 # I'm off. Cheers. :) 13.59.12 # o/ 13.59.17 Quit lnxn (Client Quit) 14.04.30 Quit Guest85177 (Ping timeout: 244 seconds) 14.06.40 Join Guest85177 [0] (~Slayer@c-69-255-136-113.hsd1.va.comcast.net) 14.10.43 Quit Guest85177 (Ping timeout: 244 seconds) 14.12.50 Join Guest85177 [0] (~Slayer@c-69-255-136-113.hsd1.va.comcast.net) 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.33 # TheSeven: 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] (~Slayer@c-69-255-136-113.hsd1.va.comcast.net) 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] (~Slayer@c-69-255-136-113.hsd1.va.comcast.net) 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.201.242.185.112) 15.23.38 Quit bob2612 (Client Quit) 15.53.08 # Build Server message: 3New 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.25 # Build Server message: 3Build round completed after 677 seconds. 16.04.26 # Build Server message: 3Revision 28920ec result: All green 16.13.18 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 16.17.06 Quit einhirn_ (Ping timeout: 260 seconds) 16.29.58 Join PurlingNayuki [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 16.34.33 Join alexweissman [0] (~alexweiss@50.95.191.79) 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.28 # time for a major commit that might potentially break all imx233 targets...commit diff is +66267, -42851 16.47.50 # No sense in only trying to break one target :) 16.49.11 # I tried it on fuzeplus, nwze380, zenxfi3 16.49.30 # Build Server message: 3New build round started. Revision eac1ca2, 255 builds, 13 clients. 16.49.48 # I even checked the disassembly to check that most of the code didn't change ! 16.50.15 # that 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.20 # gevaerts: 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.54 # Making a build that fragile can't have been easy! 16.55.33 # yeah 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 ftp://ftp.gnu.org/gnu/make/ 16.55.59 # maybe 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.24 # Build Server message: 3Build round completed after 594 seconds. 16.59.25 # Build Server message: 3Revision eac1ca2 result: 8 errors 0 warnings 17.01.03 # * gevaerts *really* wants to know where that error comes from 17.05.08 # this error is getting annoying 17.05.23 # is it always the same client ? 17.07.08 # no 17.07.24 # I don't think it's all of them either though 17.07.28 # At least two of them 17.07.33 # Build Server message: 3New build round started. Revision f182e2d, 255 builds, 13 clients. 17.08.45 # could it be a problem with parallel make ? 17.08.55 # That target has been built by lillebror1-zagor for the last seven times, and failed once 17.09.12 # Yes, I think it has to be a build system issue 17.16.41 # Ah good, I can (sometimes) reproduce it 17.17.05 # Build Server message: 3Build round completed after 571 seconds. 17.17.06 # Build Server message: 3Revision f182e2d result: All green 17.17.07 # Build Server message: 3New build round started. Revision 423c647, 255 builds, 13 clients. 17.20.42 # OK, so sometimes libcodec.a has an empty ffmpeg_bitstream.o 17.21.37 # that's clearly wrong 17.26.26 # Build Server message: 3Build round completed after 561 seconds. 17.26.27 # Build Server message: 3Revision 423c647 result: 28 errors 0 warnings 17.26.28 # Build Server message: 3New build round started. Revision d245b7a, 255 builds, 13 clients. 17.26.29 # I don't really like that multiple codecs all compile ffmpeg_bitstream 17.26.43 # That 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.48 # ah indeed this is a very good clue 17.28.59 # Basically every time a SOURCES file has ".." in it, there's a risk 17.30.43 # OK, looks like that's actually not even needed... 17.31.52 # I would say it's more a problem of different libraries recompiling the same stuff 17.32.12 # each file should be compiled once 17.32.16 # * gevaerts nods 17.32.46 # So if I remove ../lib/ffmpeg_bitstream.c from libwma/SOURCES and libwmapro/SOURCES, things still build, but the codec files are different 17.34.32 # what do you mean ? 17.34.58 # Build Server message: 3Build round completed after 511 seconds. 17.34.59 # Build Server message: 3Revision d245b7a result: All green 17.35.00 # Build Server message: 3New build round started. Revision 941ac16, 255 builds, 12 clients. 17.35.14 # that might be just a linker thing, if they don't collect garbage and include dead code maybe ? 17.35.37 # ffmpeg_bitstream.o "naturally" lives in libcodec.a. Both libwma and libwmapro have ffmpeg_bitstream.c in their SOURCES *and* link libcodec.a 17.35.45 # So yes, I think it's a linker tging 17.35.57 # But I'm not entirely sure 17.36.19 # yeah I just realized this, libwma and libwmapro should not even include this file 17.36.52 # I 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.01 # Ah, well :) 17.37.15 # (that's the hard part you have to admit) 17.38.43 # * pamaury is on a commit spree 17.39.40 # Ah, small bss differences at least 17.40.01 # But 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.41.44 # There! 17.42.12 # * gevaerts dreams of an entirely green build table! 17.43.55 # Build Server message: 3Build round completed after 537 seconds. 17.43.57 # Build Server message: 3Revision 941ac16 result: 48 errors 6 warnings 17.43.57 # Build Server message: 3New build round started. Revision c926a52, 255 builds, 13 clients. 17.44.29 # Well, if someone else doesn't spoil it with a "normal" error of course :) 17.45.41 # ouch, that's bad, sorry 17.47.30 Join lebellium_ [0] (~chatzilla@89-93-179-187.hfc.dyn.abo.bbox.fr) 17.47.38 Quit lebellium (Ping timeout: 246 seconds) 17.47.42 Nick lebellium_ is now known as lebellium (~chatzilla@89-93-179-187.hfc.dyn.abo.bbox.fr) 17.47.51 # ah trivial mistake, I forgot to not compile some code on stmp3700 17.49.27 Join krnlyng [0] (~liar@178.112.241.133.wireless.dyn.drei.com) 17.52.23 # next commit should fix it 17.53.22 # Build Server message: 3Build round completed after 564 seconds. 17.53.23 # Build Server message: 3Revision c926a52 result: 77 errors 12 warnings 17.53.24 # Build Server message: 3New build round started. Revision ae7dd53, 255 builds, 13 clients. 18.02.33 # Build Server message: 3Build round completed after 551 seconds. 18.02.34 # Build Server message: 3Revision ae7dd53 result: 5 errors 0 warnings 18.03.02 # gevaerts: there seems to be another "normal" error 18.06.49 Join nlogex [0] (~filip@dhcp-108-168-15-53.cable.user.start.ca) 18.09.30 Join alexweissman [0] (~alexweiss@50.95.191.79) 18.14.02 Quit alexweissman (Ping timeout: 240 seconds) 18.22.47 # pamaury: that's for TheSeven to figure out I think 18.23.05 # latex 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] (~Slayer@c-69-255-136-113.hsd1.va.comcast.net) 18.47.43 Quit girafe (Read error: Connection reset by peer) 18.57.34 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 19.04.41 Quit Guest85177 (Ping timeout: 244 seconds) 19.12.51 Join Guest85177 [0] (~Slayer@c-69-255-136-113.hsd1.va.comcast.net) 19.26.52 Quit sLite_ (Quit: No Ping reply in 180 seconds.) 19.28.28 Join sLite [0] (~quassel@mail.slite.org) 19.33.40 Quit sLite (Quit: No Ping reply in 180 seconds.) 19.35.12 Join sLite [0] (~quassel@mail.slite.org) 19.48.05 Quit nlogex (Ping timeout: 272 seconds) 19.51.58 # it doesn't really look like a latex error 19.52.09 # but yeah that's his problem ;) 20.01.00 Join rela [0] (~x@pdpc/supporter/active/rela) 20.08.56 # is there any guide about porting linux usb drivers to rockbox? Lack of TNETV105PAP datasheet makes it a bit extra complicated 20.12.37 # desowin_: 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.03 # but you can "draw inspiration" from it 20.14.08 # is the rockbox usbstack model described somewhere? or is just looking at other implemented drivers the way to go? 20.14.56 # mostly look at the other driver, first you need to be familiar with how usb works 20.15.51 # I 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] (~Slayer@c-69-255-136-113.hsd1.va.comcast.net) 21.02.34 Quit Guest85177 (Read error: Connection reset by peer) 21.02.57 Join Guest85177 [0] (~Slayer@c-69-255-136-113.hsd1.va.comcast.net) 21.05.04 Join saratoga [0] (47ae8268@gateway/web/freenode/ip.71.174.130.104) 21.05.14 # do we have any stats for the downloads we get per release? 21.05.45 # curious how many download 3.13 go for instance 21.05.49 # got 21.06.16 Quit puckipedia (Ping timeout: 244 seconds) 21.11.37 Join puckipedia [0] (~puck@irc.puckipedia.com) 21.13.46 Quit Guest85177 (Read error: Connection reset by peer) 21.14.12 Join Guest85177 [0] (~Slayer@c-69-255-136-113.hsd1.va.comcast.net) 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] (~quassel@mail.slite.org) 22.33.17 Quit Rower (Quit: Hmmm...) 22.36.49 *** Saving seen data "./dancer.seen" 22.40.45 Join nlogex [0] (~filip@dhcp-108-168-15-53.cable.user.start.ca) 22.51.29 Join lnxn [0] (53061d07@gateway/web/freenode/ip.83.6.29.7) 22.52.00 # Hey. 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] (~user@2a02-8420-6f5c-4200-021f-3bff-fe7d-f603.rev.sfr.net) 22.52.42 # it 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.09 # hi, 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.39 # I know Sansas survive contact with water. 22.54.06 # ha, seems like I'm not the only one trying to revive a Sansa 22.54.29 # No. 22.54.33 # *:) 22.54.45 # I'd like to help but I'm understandably concerned with mine ATM. 22.54.48 # you dropped yours in water ? 22.55.05 # Yes. Was turned on. 22.55.21 # http://www.wikihow.com/Fix-Your-Mp3-Player-That-Got-Wet says 'remove battery', but Sansas' are wired in... 22.55.24 # Should I still do it? 22.55.40 # I'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.54 # Or should I just dip it into alcohol already like it says? 22.56.28 # From the few that I know, dry it as much as you can with a hair dryier (not too hot) 22.56.53 # let the invisible traces of water evaporates by letting the circuit in open air (on a table, a radiator) for 48h 22.57.31 # but I just realized that this is for devices with no electricity running , and since the Sansa is still plugged to the battery .. 22.57.42 # Maybe cut the wires if you know about electronics .. 22.57.49 # I don't. 22.58.20 # heh 22.58.54 # then at best do what I was told .. let it dry and in two days see if you were lucky 22.59.20 # It was only submerged for a second or so. I shook it as soon as I fished it out. 23.00.03 # and the case is 'new' ? no openings ? 23.00.14 # Let me open it. 23.00.29 # Hmm there's the audio jack socket that could let water inside 23.00.42 # Yes. 23.01.13 # Did it stop altogether or was there some random things on screen .. how is it going right now ? 23.02.18 # Problem is, I set it to turn off the backlight as a matter of seconds. 23.02.35 # lol 23.02.36 # So 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.44 # I saved battery life that way. :) 23.02.50 # I have this problem too. I never know if mine is dead or just in sleep 23.02.51 # Thanks for your interest BTW, appreciate it. 23.03.21 # No problem, just send my your credit card number so I can bill you 23.04.54 # All right, opened the thing. 23.05.18 # Should I just cut the battery off 23.05.19 # ?... 23.05.46 # well is there water inside ? 23.06.36 # Hard to tell. Was some droplets on the battery (which is foiled). 23.06.44 # Put a piece of toilet paper on the whole thing. 23.06.49 # No water seems to remain. 23.06.56 # I can't find the hair dryer. >_< 23.08.32 # maybe 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.08 # Well, 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.26 # It's the second one I did this to. 23.19.39 # Oh well, this time it was a genuine accident, I just pulled on the cable. 23.19.45 # What's your issue, python476? 23.23.53 Join girafe2 [0] (~girafe@LFbn-1-8020-64.w90-112.abo.wanadoo.fr) 23.25.11 # (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.03 # The 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)