--- Log for 22.05.117 Server: hitchcock.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 13 days and 23 hours ago 00.00.26 # Bah. Errant space in the input line got sent by mistake. Sorry. 00.01.01 # <__builtin> Linton (logs): I might know why 00.02.49 # <__builtin> well, maybe not actually 00.04.38 Join PurlingNayuki [0] (~Thunderbi@114.255.40.60) 00.06.40 # so it looks like something destroyed my build VM 00.07.05 # something must have run rm -rf * in the rockbox user's home directory, quite probably the build client or the nightlies job 00.07.43 # possibly as a result of the VM running out of disk space (or at least believing to be doing that due to a btrfs bug) 00.09.01 # is it work trying to get that repaired, or would it make more sense to move the nightly win32 sim + android builds over to whatever will host the new repository? maybe some sort of CI system? 00.09.07 # is it worth* 00.10.13 # <[Saint]> we'll need to make some changes in mainline before RaaA builds again. 00.10.27 # <[Saint]> Unless you happened to keep all your platform tools and ancient SDK around. 00.10.51 # <[Saint]> It's practically impossible to find the versions head will build with these days. 00.11.24 # <[Saint]> Though, this isn't a bad thing. Probably should've bumped the platform API yeeeeeeeeeeeeeaaaaaaaaaars ago. 00.11.34 # <[Saint]> ...I think we still target 14. 00.12.19 # just wondering if I should put any effort in trying to get that back up and running or if we should consolidate that stuff somewhere else anyway 00.12.38 # <[Saint]> A few things need to happen, the linker needs to be changed, the platform target needs to be bumped, and there's a couple of paths that moved. 00.13.19 # <[Saint]> TheSeven: to be honest, I have some serious doubts about the need to keep RaaA alive. 00.13.37 Quit mc2739 (Ping timeout: 268 seconds) 00.13.39 # <[Saint]> Without an ungodly hack it's not even possible to run it on anything past 4.* 00.14.03 # <[Saint]> And anything under 6.* is a massive security clusterfuck no one in their right mind should use for anything. 00.14.17 # <[Saint]> I'm...conflicted about it. 00.14.41 # what about the win32 sim builds? I guess we should at least take care of those 00.15.00 # <[Saint]> Yes, quite probably. 00.17.08 Quit petur (Remote host closed the connection) 00.29.50 Quit TheSeven (Remote host closed the connection) 00.33.38 *** Saving seen data "./dancer.seen" 00.44.56 Quit PurlingNayuki (Ping timeout: 240 seconds) 00.47.35 Join Linton [0] (586862d9@gateway/web/freenode/ip.88.104.98.217) 00.54.24 # __builtin: In addition to the 5 puzzles that only crash on today's build or 3.14, there are 8 which only crash on Thursday's build, namely dominosa, lightup, magnets, pegs, range, signpost, slant, and untangle. 00.55.13 # That's in addition to the 4 that always crash: fifteen, intertia, rect and tents 00.55.14 # <[Saint]> That makes no immediate sense. 00.56.18 # Because there are no changes in today's build that could cause a crash, logically? 00.57.12 # <[Saint]> Yes. 00.57.13 # <[Saint]> On the surface of things, 6bba062 should be entirely benign. 00.57.38 # <[Saint]> It's just a slightly different way of doing what was already happening, without the chance for unwanted collision. 00.58.38 # Yes, that's what I thought from reading the source code, but testing seems to say different. 01.02.12 # <[Saint]> Can you be a Sweetheart for me and, if you haven't, attempt to reproduce from an absolutely clean .rockbox? 01.03.05 # <[Saint]> I would just like to know that you can reproduce this with a clean config and no chance of binary weirdness. 01.03.57 # <[Saint]> preferably back up your .rockbox in case it does magically fix it so I can have a look at why. 01.07.08 Quit ender` (Quit: A user interface is like a joke. If you have to explain it, it's not that good.) 01.07.15 Quit __builtin (Quit: No Ping reply in 240 seconds.) 01.08.40 Join __builtin [0] (~xray@rockbox/developer/builtin) 01.15.43 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 01.19.25 Quit paulk-collins (Quit: Leaving) 01.24.04 # [Saint]: I've done as you asked (deleted .rockbox, clean install of 6bba062 from the zip rockbox.org), and, believe it or not, the strangeness persists. 01.24.39 # <[Saint]> Oh, I believe it. It just makes zero sense on the surface. 01.26.27 # I copied the .rock files for bridges, flip, galaxies, map, netslide, tracks from 504346a and ran them on 6bba062 without crashes. 01.28.12 # <[Saint]> o_o 01.34.05 Quit amiconn (Ping timeout: 246 seconds) 01.34.26 Quit pixelma (Ping timeout: 246 seconds) 01.41.09 Join pixelma [0] (~pixelma@rockbox/staff/pixelma) 01.41.40 Join amiconn [0] (~amiconn@rockbox/developer/amiconn) 01.42.31 Join chatter29 [0] (ac68513f@gateway/web/cgi-irc/kiwiirc.com/ip.172.104.81.63) 01.42.36 # hey guys 01.42.39 # allah is doing 01.42.44 # sun is not doing allah is doing 01.42.45 # to accept Islam say that i bear witness that there is no deity worthy of worship except Allah and Muhammad peace be upon him is his slave and messenger 01.42.50 Quit chatter29 (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client) 01.43.58 Mode "#rockbox +o [Saint]" by ChanServ (ChanServ@services.) 01.43.59 Mode "#rockbox +b chatter29!*@*" by [Saint] (~sinner@rockbox/staff/saint) 01.43.59 Mode "#rockbox -o [Saint]" by ChanServ (ChanServ@services.) 01.45.04 Quit TheSeven (Read error: Connection reset by peer) 01.47.12 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 01.53.22 Quit TheSeven (Remote host closed the connection) 01.55.46 # <[Saint]> __builtin: does that make even the slightest bit of sense to you? 01.56.09 Quit cc___ (Ping timeout: 255 seconds) 02.09.46 Quit amiconn (Ping timeout: 240 seconds) 02.09.46 Quit pixelma (Ping timeout: 240 seconds) 02.10.02 # <__builtin> wait, so let me get this straight 02.10.44 # <__builtin> there's a difference in what crashes and what doesn't after my commit today? 02.10.56 # <__builtin> that's... very highly improbable 02.12.03 # <__builtin> there's no requirement that a plugin release the audio buffer when exiting, is there? 02.12.42 # <[Saint]> it's not required, AFAIK, but...why wouldn't you? 02.13.08 # I should point out that I'm running the builds from the website - possibly I'm getting an artifact from different build enviroments, rather than a true result of source code changes? 02.13.20 # <__builtin> possibly 02.13.56 # <__builtin> that's the only thing that would explain it, actually 02.15.04 # <[Saint]> it's not really /possible/ to get a build system artefact, is it? 02.15.30 # <[Saint]> ccache would only work for binary identical objects, and $OUT gets nuked between rounds. 02.15.39 Join pixelma [0] (~pixelma@rockbox/staff/pixelma) 02.15.46 Join amiconn [0] (~amiconn@rockbox/developer/amiconn) 02.16.12 # <__builtin> they're all built using the same toolchain, too, right? 02.16.34 # <[Saint]> Yes. 02.16.58 # <__builtin> I'll take a look at the .rock files from each build 02.18.25 # <__builtin> Linton: you're testing on the zip? 02.19.46 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 02.20.34 # Yes, that's right. 02.21.42 # <__builtin> argh, no archived builds available online 02.22.32 # <__builtin> I'll just build both locally and see if there's any significant difference in the binaries 02.26.29 # <__builtin> yep, both 504346a and HEAD are byte-for-byte identical 02.27.35 # <__builtin> which is expected, they were built from the same preprocessed sources 02.32.21 # http://download.rockbox.org/daily/sansaclipzip/rockbox-sansaclipzip-20170519.zip 02.33.41 # ...contains non-crashing versions of bridges and tracks. 02.33.43 *** Saving seen data "./dancer.seen" 02.34.43 Join Rower [0] (husvagn@m83-184-183-163.cust.tele2.se) 02.35.50 # https://build.rockbox.org/data/rockbox-sansaclipzip.zip (as of 5 hours ago, at least) contains crashing versions. 03.04.26 Quit Moarc (Ping timeout: 240 seconds) 03.07.08 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 03.08.35 Join Moarc [0] (~chujko@a105.net128.okay.pl) 03.08.35 Quit ZincAlloy (Quit: Leaving.) 03.15.43 Quit TheSeven (Ping timeout: 255 seconds) 03.17.48 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 03.19.50 Quit Bilgus_ph (Quit: Page closed) 03.31.03 Quit Rower (Ping timeout: 240 seconds) 03.31.47 Join Rower [0] (husvagn@m176-64-132-2.cust.tele2.se) 04.23.03 # https://www.rockbox.org/wiki/ArticlesAboutRockbox First update in four years. :) 04.33.45 *** Saving seen data "./dancer.seen" 04.33.59 Quit idonob (Quit: unbreaking crap) 04.34.35 Join idonob [0] (~Owner@S010600259c3e7d7b.vs.shawcable.net) 05.11.05 Quit mc2739 (Ping timeout: 240 seconds) 05.17.04 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:3c02:4deb:3525:5992:7ffd) 05.26.32 Quit athidhep (Read error: Connection reset by peer) 05.37.59 Quit Linton (Ping timeout: 260 seconds) 05.47.53 Quit PurlingNayuki (Quit: PurlingNayuki) 05.49.05 Quit prof_wolfff (Ping timeout: 240 seconds) 05.59.07 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:3c02:f53a:7fcc:e55e:7d74) 06.07.34 Join PurlingNayuki1 [0] (~Thunderbi@2001:da8:215:4ff:14a7:fdd8:338:91dd) 06.09.53 Quit PurlingNayuki (Ping timeout: 255 seconds) 06.09.53 Nick PurlingNayuki1 is now known as PurlingNayuki (~Thunderbi@2001:da8:215:4ff:14a7:fdd8:338:91dd) 06.33.16 Quit pixelma (Quit: .) 06.33.16 Quit amiconn (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) 06.33.27 Join pixelma [0] (~pixelma@rockbox/staff/pixelma) 06.33.28 Join amiconn [0] (~amiconn@rockbox/developer/amiconn) 06.33.46 *** Saving seen data "./dancer.seen" 06.37.20 Quit TheSeven (Ping timeout: 255 seconds) 06.37.32 Join [7] [0] (~quassel@rockbox/developer/TheSeven) 06.43.38 Quit PurlingNayuki (Ping timeout: 255 seconds) 06.45.57 Quit munch (Quit: Let's blast this shit and get naked) 06.46.02 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:14a7:fdd8:338:91dd) 06.53.00 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 07.03.39 Join munch [0] (pls@gateway/shell/elitebnc/x-rmqgsixvujgjihwz) 07.10.41 Quit Bilgus (Ping timeout: 248 seconds) 07.12.51 Quit dys (Ping timeout: 245 seconds) 07.13.25 Quit jhMikeS (Ping timeout: 255 seconds) 07.22.18 Join Bilgus [0] (~Bilgus@gateway/tor-sasl/bilgus) 07.28.14 Join PurlingNayuki1 [0] (~Thunderbi@114.255.40.60) 07.30.21 Quit PurlingNayuki (Ping timeout: 240 seconds) 07.30.21 Nick PurlingNayuki1 is now known as PurlingNayuki (~Thunderbi@114.255.40.60) 07.40.04 Quit pamaury (Ping timeout: 240 seconds) 07.58.20 Join deevious [0] (~Thunderbi@193.226.142.214) 08.25.54 Quit michaelni (Ping timeout: 272 seconds) 08.33.47 *** Saving seen data "./dancer.seen" 08.34.50 Join xorly [0] (~xorly@ip-86-49-24-93.net.upcbroadband.cz) 08.38.25 Join michaelni [0] (~michael@213-47-41-20.cable.dynamic.surfer.at) 08.39.27 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 08.49.22 Join ender` [0] (krneki@foo.eternallybored.org) 09.02.07 Quit PurlingNayuki (Ping timeout: 268 seconds) 09.04.04 Quit zagor (Ping timeout: 246 seconds) 09.08.54 Quit Moarc (Ping timeout: 268 seconds) 09.10.05 Join Moarc [0] (~chujko@a105.net128.okay.pl) 09.10.30 Join jhMikeS [0] (~jethead71@d192-24-173-177.try.wideopenwest.com) 09.15.12 Quit jhMikeS (Ping timeout: 260 seconds) 09.31.04 Quit Rower (Ping timeout: 240 seconds) 09.41.46 Quit LinuxArie (Ping timeout: 260 seconds) 09.43.04 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:4928:8194:1c9d:ea15) 10.02.32 Quit PurlingNayuki (Ping timeout: 255 seconds) 10.07.15 Join elensil [0] (~edhelas@2001:1c02:1900:7800:759c:d57:8ce8:8c6b) 10.23.01 Join paulk-collins [0] (~paulk@gagarine.paulk.fr) 10.33.51 *** Saving seen data "./dancer.seen" 10.38.03 Quit deevious (Ping timeout: 240 seconds) 10.45.27 Join Rower [0] (~husvagn@d83-183-134-99.cust.tele2.se) 10.49.57 Quit Rower (Ping timeout: 240 seconds) 10.50.42 Join Rower [0] (~husvagn@d83-183-134-99.cust.tele2.se) 10.55.22 Join deevious [0] (~Thunderbi@193.226.142.214) 11.53.33 Quit xorly (Ping timeout: 268 seconds) 12.12.31 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:9c09:7b7a:ca1a:5237) 12.12.37 Join robertd1 [0] (~root@201.242.174.75) 12.27.04 Quit fs-bluebot (Ping timeout: 255 seconds) 12.27.28 Quit bluebrother (Ping timeout: 268 seconds) 12.33.52 *** Saving seen data "./dancer.seen" 12.39.04 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 12.40.43 Join fs-bluebot [0] (~fs-bluebo@port-92-196-18-165.dynamic.qsc.de) 12.50.56 Join JanC_ [0] (~janc@lugwv/member/JanC) 12.51.55 Quit JanC (Ping timeout: 246 seconds) 12.52.13 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC) 13.09.04 Join xorly [0] (~xorly@wced-161-219-32-147.feld.cvut.cz) 13.11.48 Join Bilgus_ [0] (~Bilgus@gateway/tor-sasl/bilgus) 13.13.56 Quit Rower (Ping timeout: 240 seconds) 13.14.56 Quit Bilgus (Ping timeout: 248 seconds) 13.17.22 Join PimpiN8 [0] (~textual@2a02:a454:38ea:1:d11:8f22:be3a:1de3) 13.36.14 Quit dfkt (Quit: SIC GORGIAMVS ALLOS SVBJECTATOS NVNC.) 13.37.13 Join dfkt [0] (~dfkt@unaffiliated/dfkt) 13.47.03 Quit xorly (Ping timeout: 240 seconds) 13.53.50 Join xorly [0] (~xorly@wced-161-219-32-147.feld.cvut.cz) 14.03.33 Join krabador [0] (~krabador@unaffiliated/krabador) 14.07.18 Quit bluebrother (Ping timeout: 260 seconds) 14.07.26 Join LinuxArie [0] (~Arie@ip54579264.direct-adsl.nl) 14.07.27 Quit fs-bluebot (Ping timeout: 260 seconds) 14.11.03 Quit xorly (Ping timeout: 240 seconds) 14.12.07 Join fs-bluebot [0] (~fs-bluebo@port-92-196-111-137.dynamic.qsc.de) 14.14.07 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 14.18.31 Quit bluebrother (Ping timeout: 260 seconds) 14.18.31 Quit fs-bluebot (Ping timeout: 260 seconds) 14.23.00 Join Bilgus [0] (~Bilgus@gateway/tor-sasl/bilgus) 14.24.21 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 14.25.52 Quit Bilgus_ (Ping timeout: 248 seconds) 14.26.13 Join xorly [0] (~xorly@wifi-cl-57.feld.cvut.cz) 14.32.12 Join fs-bluebot [0] (~fs-bluebo@port-92-196-12-143.dynamic.qsc.de) 14.33.55 *** Saving seen data "./dancer.seen" 14.46.33 Quit diox (Ping timeout: 264 seconds) 14.55.10 Quit krabador (Remote host closed the connection) 15.06.51 Join diox [0] (~u@c80-216-222-77.bredband.comhem.se) 15.11.22 Join amayer [0] (~amayer@mail.weberadvertising.com) 15.16.38 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 15.29.27 Quit xorly (Ping timeout: 240 seconds) 15.48.06 Quit wodz (Ping timeout: 260 seconds) 16.02.58 Join Bilgus_ [0] (~Bilgus@gateway/tor-sasl/bilgus) 16.04.35 Quit Bilgus (Remote host closed the connection) 16.10.43 Join jhMikeS [0] (~jethead71@d192-24-173-177.try.wideopenwest.com) 16.33.56 *** Saving seen data "./dancer.seen" 16.57.39 Quit jhMikeS (Ping timeout: 260 seconds) 17.00.15 Join asymsucon [0] (5037dc16@gateway/web/freenode/ip.80.55.220.22) 17.00.45 # saratoga: I wouldn't mind testing, but as far as optimization, I'm afraid I lack the required skills 17.23.38 Join athidhep [0] (~afoakf@unaffiliated/athidhep) 17.26.07 Quit fs-bluebot (Ping timeout: 240 seconds) 17.27.04 Quit bluebrother (Ping timeout: 240 seconds) 17.28.55 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 17.40.55 Join fs-bluebot [0] (~fs-bluebo@port-92-196-38-213.dynamic.qsc.de) 17.47.55 Join xorly [0] (~xorly@ip-86-49-24-93.net.upcbroadband.cz) 17.59.56 Quit elensil (Quit: Leaving.) 18.10.28 Quit asymsucon (Ping timeout: 260 seconds) 18.23.16 Join jhMikeS [0] (~jethead71@d192-24-173-177.try.wideopenwest.com) 18.23.25 Quit PimpiN8 (Quit: My MacBook has gone to sleep. ZZZzzz…) 18.33.15 Join petur [0] (~petur@rockbox/developer/petur) 18.33.59 *** Saving seen data "./dancer.seen" 18.35.16 Part robertd1 18.48.41 Join dys [0] (~dys@ip1f13984f.dynamic.kabel-deutschland.de) 18.52.24 Join johnb3 [0] (~johnb2@p5B3AFF15.dip0.t-ipconnect.de) 19.03.39 Quit LinuxArie (Ping timeout: 260 seconds) 19.05.22 # i can pick up an ipod 5g 30gb 19.05.38 # how does it compare to the 60gb version (which has more memory) 19.05.51 # or newer 6g/7g models? 19.06.35 # The 60gb will (IIRC) also be thicker, heavier, and have a bigger battery 19.06.57 # Memory isn't guaranteed if there's a repair/refurbish history 19.08.01 # CPU is a bit slow for the display size, everything really depends on what you want to do with the thing 19.08.13 # * gevaerts will delegate explaining why the 6g is better to [Saint] :) 19.12.22 # but is there an advantage to 64mb memory? 19.12.36 # and what do you mean the cpu is "slow"? 19.14.29 # 64mb will give you more audio buffer, which means fewer disk spin-ups, which means more battery life 19.15.12 # By "slow" I mean, "not fast" :) 19.17.02 # eh it plays music so i guess it's fine 19.17.17 # i can use it as a primary player till mine gets a port 19.17.18 # Basically while actively using the device (browsing files, ...) the CPU needs to spend some time on every pixel on the screen, and the video with its *huge* 320x240 16 bit colour screen has to do a lot more work than say a mini (which has more or less the same CPU) with a 160x128 2 bit screen 19.17.52 # And then of course some audio formats want more CPU, or things like EQ 19.17.59 # does it lag or something 19.18.47 # The UI might feel a bit slow, and if you try audio that's too heavy it'll skip or not play at all 19.19.02 # It all depends on what sort of thing you want to play 19.21.14 # ogg, flac, mp3 will always be fine (I'm assuming 44.1/48kHz 16 bit max. Anything higher isn't sane *anyway*), I'm not sure about opus, and ape is not a good idea on *any* portable device 19.21.55 # https://www.rockbox.org/wiki/CodecPerformanceComparison might help, or it might confuse you :) 19.23.38 # Basically you want at least something like 120% realtime, and if you want EQ a bit (to a lot, depending on how many bands) more 19.24.23 # Sorry, when I said "ape is not a good idea on any portable device", I meant "ape is not a good idea" :) 19.26.51 # I suspect the 6g will be a lot better in (almost?) every respect, but I guess it'll also be a lot more expensive 19.29.47 Join lebellium [0] (~chatzilla@89-93-178-245.hfc.dyn.abo.bbox.fr) 19.45.33 # yeah they really are 19.45.49 # this beat up ipod 5g 30gb: $10 19.46.01 # ipod 6g: $100 19.47.13 # is there already a ipod with micro usb? :) 19.47.49 # never 19.47.55 # too bad 19.48.08 # apple will die 3 times before they adhere to any popular standard 19.49.47 # Oh, also, any ipod video you get today will of course probably have a ten year old battery in it, so you may well have to replace that 19.51.08 # yeah 19.51.19 # does it require soldering ? 19.53.36 # I don't think so, but opening the case cleanly is a bit tricky 19.53.41 # ifixit has a guide 19.53.54 # oh yeah 19.54.14 # that one that tells you to use a putty spade 19.54.44 # They make a *fortune* selling those :) 19.56.09 Join LinuxArie [0] (~Arie@ip54579264.direct-adsl.nl) 20.01.44 # wait it's called a putty knife 20.03.18 # http://i.imgur.com/XztJTrp.png 20.11.35 # "opening the case cleanly is a bit tricky" – opening it is usually the easy task. at least with welded/glued cases like the sansa 20.12.07 # btw: is there a good way to close a sansa clip+ after opening it? 20.12.18 # (or just glue?) 20.26.39 Join Bilgus_ph [0] (~Bilgus_ph@108.115.238.34) 20.27.45 # HUH the sansa clip+ has like 6 clips inside same with the sport maybe you mean the clip v1? 20.29.40 # what? it has clips? :O no, I have the clip+ but never opened it 20.29.59 # Also i can tell you a metal anything is not the way to open a plastic case unless its a screwdriver to remove screws always go plastic credit cards guitar picks. plastic silverware etc. plastic putty knives even 20.30.01 # feared to break it and never get it together again 20.30.25 Join JanC_ [0] (~janc@lugwv/member/JanC) 20.30.35 # then I should really think about replacing that dying battery 20.31.16 Quit JanC (Ping timeout: 240 seconds) 20.31.23 # (clip+ has clips, duh!) 20.31.42 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC) 20.31.59 # I used two credit cards and started on the long side opposite of the volume switch take a look at the photos of the internals on rockbox.org and note where those clips are 20.32.46 # Be careful dont pry at the sd slot opening its super thin 20.33.33 Join TheLemonMan [0] (~root@irssi/staff/TheLemonMan) 20.34.01 *** Saving seen data "./dancer.seen" 20.34.13 # thanks for the tips! shouldn't be hard for me, opened so many clipped cases in my life… 20.34.20 # Make sure sd card is out the open it like a book with the power port being the spine 20.36.12 # The adhesive on battery is the hardest part imo. Use side of credit card to push through the foam take care with wires you don't want to rip the pads off the board 20.40.11 # Starting it is the key thats where two cards comes in so you can keep the clips on one side from re clippping 20.45.59 Quit Bilgus_ph (Read error: Connection reset by peer) 20.53.16 Quit johnb3 (Ping timeout: 240 seconds) 20.57.32 Quit jhMikeS (Ping timeout: 240 seconds) 21.04.25 Quit alucryd (Remote host closed the connection) 21.06.13 Join alucryd [0] (~quassel@archlinux/developer/alucryd) 21.15.41 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 21.42.26 Quit pamaury (Ping timeout: 260 seconds) 21.43.53 Join prof_wolfff [0] (~prof_wolf@62.83.49.172.dyn.user.ono.com) 22.26.15 Join Airwave [0] (~Airwave@188.195.9.46.customer.cdi.no) 22.27.34 # I have a Sansa Clip+. Software-wise it works great (running Rockbox 3.14), but the buttons are very slugglish, requiring hard presses and multiple attempts. I think it might be dust, so I'm considering opening it up and trying to clean it out. Any tips? 22.32.24 # I don't think I'd try you are likely to break the screen trying to get it detached 22.34.02 *** Saving seen data "./dancer.seen" 22.35.40 Join edhelas [0] (~edhelas@54693F03.cm-12-2a.dynamic.ziggo.nl) 22.50.35 Quit Galois (Ping timeout: 240 seconds) 23.01.23 Quit TheLemonMan (Quit: "It's now safe to turn off your computer.") 23.09.19 Quit lebellium (Quit: ChatZilla 0.9.93 [Firefox 53.0.3/20170518000419]) 23.10.00 Quit gluytium (Ping timeout: 246 seconds) 23.14.09 Quit xorly (Ping timeout: 255 seconds) 23.14.39 Join gluytium [0] (U2FsdGVkX1@ma.sdf.org) 23.16.16 # Bilgus_: Any other ideas? 23.20.46 # the buttons are the metal dome cheapos so idk 23.21.23 # is it all the buttons or just one or two? 23.22.37 Quit petur (Quit: Leaving) 23.22.49 # I mean it would be possible to remap a working button to ones that do work 23.28.50 # non-working 23.32.11 # Bilgus_: All of the buttons are annoying to push, but to varying degrees. 23.32.22 # The down, select, and home buttons are especially bad. 23.34.27 Join Galois [0] (djao@efnet-math.org)