--- Log for 27.03.113 Server: hitchcock.freenode.net Channel: #rockbox --- Nick: logbot- Version: Dancer V4.16 Started: 13 hours and 8 minutes ago 00.01.48 Quit esperegu (Read error: Connection reset by peer) 00.02.33 Join esperegu [0] (~quassel@ip-213-124-221-141.ip.prioritytelecom.net) 00.04.54 Quit ender` (Quit: Space, the last best hope for peace. These are the voyages of the Millenium Falcon. Its five-year mission: to find technology to defeat the Goa'uld.) 00.05.02 Quit n1s (Remote host closed the connection) 00.05.50 Quit dhrasmus (Ping timeout: 255 seconds) 00.08.22 # when setting eq enabled on or off using setting_set, it does not make effect until you go to Settings > Sound Settings -> Equalizer -> Enable EQ > then go back 00.09.19 # is there anything to make rockbox "reload" that value? 00.09.37 # other than going to Equalizer settings 00.15.54 Quit Xerion_ (Read error: Operation timed out) 00.26.59 Quit bertrik (Ping timeout: 248 seconds) 00.33.27 Join Xerion [0] (~xerion@5419F5F4.cm-5-2d.dynamic.ziggo.nl) 00.38.18 Quit pamaury (Ping timeout: 245 seconds) 00.53.15 *** Saving seen data "./dancer.seen" 01.16.17 Join zchs [0] (~zchs@ool-ad034fd8.dyn.optonline.net) 01.25.09 Quit Scromple (Read error: Connection reset by peer) 01.28.26 Quit RiD (Read error: Connection reset by peer) 01.29.33 Join RiD [0] (GhostRider@2.83.9.62) 01.31.31 Part RiD 01.37.39 Join Scromple [0] (~Simon@119.225.209.134) 01.46.22 Join [Saint] [0] (~saint@rockbox/user/saint) 01.53.51 Quit froggyman (Ping timeout: 252 seconds) 01.53.55 Join RiD [0] (GhostRider@2.83.9.62) 02.23.53 Join froggyman [0] (~me@dhcp-155-92-105-106.nebula.msoe.edu) 02.23.53 Quit froggyman (Changing host) 02.23.53 Join froggyman [0] (~me@unaffiliated/froggyman) 02.43.45 Join Caribou00 [0] (~63e17357@www.haxx.se) 02.47.39 # uhh having a bit of trouble with themes. i installed rockbox + 7 themes with the utility. when i load a theme, the backdrop changes but the now playing screen is always a plain black screen with plain everything.. it's just stuck that way it won't even load the default rockbar theme 02.48.04 # i checked to make sure all the files are present.. they are all definitely there and intact 02.48.57 # tried holding down power for 30 sec... and tried rebooting after changing theme... no joy 02.50.45 # <[Saint]> Are you safely ejecting the volume? 02.51.04 # <[Saint]> That rather sounds like a case of filesystem corruption. 02.52.49 # okay then, it's possible since i've been trying to transfer files to rockbox with Clementine for Mac, and it the device gets ejected abruptly and then has fatal error something about parsing. the screen flashes every second and i have to power it down 02.53.00 # so that happened once or twice 02.53.17 *** Saving seen data "./dancer.seen" 02.53.21 # i'll go ahead and reinstall everything.... should i do the bootloader too? 02.53.46 # <[Saint]> No. 02.53.54 # <[Saint]> There's no need to replace the bootloader. 02.54.00 # ok 02.55.25 # <[Saint]> It is really important to safely eject volumes, or at the very least attempt to ensure that all data is written out to it. 02.56.14 # rockbox.org etc 02.56.32 # sorry 02.56.56 # rock 02.57.13 # why can;t this thing understand brackets mean brackets not delete everything 02.57.42 # <[Saint]> ...huh? 02.58.59 # trying to say that others had this problem with clementine too, rockboxed ipods won't work. it doesnt support MSC, or it thinks theyre running OF or something. it still accurately read the device info tho - by that i mean the name... rockbox.org device or whatever you call them and the author rockbox 03.10.44 # it werked ヽ(*≧ω≦)ノ♡ 03.14.15 Quit Caribou00 (Quit: CGI:IRC (EOF)) 03.20.39 Quit RiD (Quit: Zip!) 03.25.59 Join Krosis_ [0] (~Krosis@24-180-66-46.dhcp.bycy.mi.charter.com) 03.47.02 Quit Krosis_ (Ping timeout: 245 seconds) 03.50.35 Quit thegeek_ (Ping timeout: 240 seconds) 04.15.15 Join Scr0mple [0] (~Simon@rx0ht-winward.ok.bigpipeinc.com) 04.16.01 Quit amayer (Quit: Leaving) 04.16.37 Join Scromple_ [0] (~Simon@119.225.209.134) 04.17.57 Quit Scromple (Ping timeout: 248 seconds) 04.19.48 Join zamboni [0] (~bottledwa@unaffiliated/zamboni) 04.20.44 Quit Scr0mple (Ping timeout: 252 seconds) 04.35.03 Join Krosis_ [0] (~Krosis@24-180-66-46.dhcp.bycy.mi.charter.com) 04.39.52 Quit pixelma (Disconnected by services) 04.39.53 Join pixelma_ [0] (pixelma@rockbox/staff/pixelma) 04.39.55 Quit amiconn (Disconnected by services) 04.39.55 Join amiconn_ [0] (quassel@rockbox/developer/amiconn) 04.39.55 Nick pixelma_ is now known as pixelma (pixelma@rockbox/staff/pixelma) 04.39.58 Nick amiconn_ is now known as amiconn (quassel@rockbox/developer/amiconn) 04.53.21 *** Saving seen data "./dancer.seen" 04.54.13 Quit froggyman (Ping timeout: 248 seconds) 05.12.03 Quit mrtux (Ping timeout: 256 seconds) 05.15.43 Join Rower [0] (husvagn@v-413-alfarv-177.bitnet.nu) 05.17.01 Join TheSphinX_ [0] (~briehl@p57A38831.dip.t-dialin.net) 05.18.12 Join mrtux [0] (~colin@unaffiliated/mrtux) 05.19.54 Quit TheSphinX^ (Read error: Operation timed out) 05.35.54 Quit prof_wolfff (Read error: Connection reset by peer) 05.51.13 Quit TheSeven (Disconnected by services) 05.51.22 Join [7] [0] (~quassel@rockbox/developer/TheSeven) 05.55.58 Quit zamboni () 05.59.13 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 06.01.52 Quit fs-bluebot (Ping timeout: 272 seconds) 06.02.19 Join dfkt [0] (dfkt@unaffiliated/dfkt) 06.02.29 Quit bluebrother^ (Ping timeout: 252 seconds) 06.03.12 Quit dfkt_ (Ping timeout: 264 seconds) 06.03.23 Join fs-bluebot [0] (~fs-bluebo@g226068255.adsl.alicedsl.de) 06.08.33 Join akaWolf [0] (~akaWolf@unaffiliated/akawolf) 06.08.42 Nick Unhelpful_ is now known as Unhelpful (~quassel@rockbox/developer/Unhelpful) 06.19.32 Join kevku [0] (~kevku@2001:470:27:773:0:feed:c0f:fee) 06.37.48 Quit SuperBrainAK (Quit: pbly going to sleep /_\) 06.52.34 Quit Krosis_ (Quit: There's no place like 127.0.0.1) 06.53.22 *** Saving seen data "./dancer.seen" 07.21.31 Quit jhMikeS (Read error: Connection reset by peer) 07.24.10 Join jhMikeS [0] (~jethead71@50.4.247.132) 07.24.10 Quit jhMikeS (Changing host) 07.24.10 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) 07.25.39 Quit esperegu (Read error: Connection reset by peer) 07.26.07 Quit Lynx_ (Remote host closed the connection) 07.26.30 Join esperegu [0] (~quassel@ip-213-124-221-141.ip.prioritytelecom.net) 07.26.45 Join Lynx_ [0] (~bayer@109.171.130.211) 07.27.48 Join melmothX [0] (~melmoth@unaffiliated/melmothx) 07.33.58 Join olspookishmagus [0] (~pookie@host-84-205-241-1.cpe.syzefxis.ote.gr) 07.35.37 Join ender` [0] (~ender@foo.eternallybored.org) 07.43.02 Join mortalis [0] (~kvirc@213.33.220.118) 07.45.38 Quit Raptors (Ping timeout: 252 seconds) 07.50.17 Join Raptors [0] (~whoneedsa@216-58-33-203.cpe.distributel.net) 07.51.12 Quit kevku (Ping timeout: 264 seconds) 08.09.42 Quit amiconn (Remote host closed the connection) 08.09.42 Quit pixelma (Remote host closed the connection) 08.10.40 Join amiconn [0] (amiconn@rockbox/developer/amiconn) 08.10.40 Join pixelma [0] (pixelma@rockbox/staff/pixelma) 08.23.29 Join Zagor [0] (~bjst@sestofw01.enea.se) 08.23.29 Quit Zagor (Changing host) 08.23.29 Join Zagor [242] (~bjst@rockbox/developer/Zagor) 08.30.59 Quit jhMikeS (Ping timeout: 252 seconds) 08.37.22 Join pretty_function [0] (~sigBART@123.252.212.53) 08.45.32 Quit esperegu (Read error: Connection reset by peer) 08.46.05 Join esperegu [0] (~quassel@ip-213-124-221-141.ip.prioritytelecom.net) 08.48.49 Quit ender` (Quit: "Let me make sure I have this straight. The cavalry just now rode into town and it’s a Czech Gypsy porn-star zombie killer. Have I got that right?" -- Richard Kadrey: Kill the Dead) 08.49.56 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 08.50.09 Join kevku [0] (~kevku@2a01:d0:ffff:34a::8:3) 08.53.23 *** Saving seen data "./dancer.seen" 08.57.36 Join petur [0] (~petur@rockbox/developer/petur) 09.08.35 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 09.09.43 Join Rondom [0] (~rondom@2a01:488:66:1000:b24d:4f2f:0:1) 09.18.46 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 09.24.33 Quit bertrik (Ping timeout: 240 seconds) 09.25.22 Join lebellium [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 09.26.32 # [Saint]: do you know why %?tr<%xd(Va)|%xd(Vb)|%xd(Vc)|%xd(Vd)|%xd(Ve)|%xd(Vf)> is not divided equally? 09.28.09 Join y4n [0] (~y4n@unaffiliated/y4ndexx) 09.28.38 # <[Saint]> Nope. 09.30.13 # but it should, right? I mean, should I open a bug ticket? 09.30.39 # <[Saint]> Yeah, go for it. 09.31.43 Quit pretty_function (Remote host closed the connection) 09.32.06 Join redhot [0] (~kvirc@195.238.92.36) 09.32.11 # Howdy! 09.33.26 # <[Saint]> Errr...hi. 09.33.58 # <[Saint]> You're very enthusiastic. 09.43.28 # JdGordon: FS#12848 :) 09.43.29 # http://www.rockbox.org/tracker/task/12848 3Signal strength tag %tr doesn't divide equally when using conditionnals (bugs, unconfirmed) 09.45.54 # <[Saint]> lebellium: it would make life a whole lot easier if you posted the full theme in that report. 09.46.19 # why? That concerns any of my theme or anyone using this tag? 09.47.56 # <[Saint]> It saves myself, or others, have to create a test case specifically to see it in action. 09.48.19 # <[Saint]> It also allows us to see if you may or may not being doing "something stupid(TM)". 09.48.23 # I can add a link to my theme on the theme website 09.48.34 # <[Saint]> Go for it. 09.49.47 # done 09.52.12 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 09.59.00 Quit esperegu (Ping timeout: 264 seconds) 10.03.02 Join bebna [0] (~a.fasold@94.101.33.114) 10.13.07 Quit pamaury (Ping timeout: 246 seconds) 10.23.23 Join esperegu [0] (~quassel@ip-213-124-221-141.ip.prioritytelecom.net) 10.25.43 Quit Provel_ (Ping timeout: 264 seconds) 10.31.10 Join LinusN [0] (~linus@giant.haxx.se) 10.34.57 # actually it is pretty much the same for the battery indicator. %?bl<|%xd(Be)|%xd(Bf)|%xd(Bg)|%xd(Bh)|%xd(Bi)> with Be = 0 bar and Bi = 4 bars gives 10.34.59 # 4 bars 100% 10.35.01 # 3 bars 75-99% 10.35.03 # 2 bars 50-74% 10.35.05 # 1 bars 25-49% 10.35.06 # 0 bars 0-24% 10.35.07 # but here is is maybe intended and makes more sense that it is not equally divided 10.35.32 # <[Saint]> you can't do the battery indicator that way. 10.36.12 # Are you sure? I thought I copied code of cabbiev2 10.36.19 # <[Saint]> the 'state unknown' case messes up splitting it properly. 10.36.37 # <[Saint]> If you really want nice steps, use a bar. 10.36.41 Quit mortalis (Quit: KVIrc 4.1.3 Equilibrium http://www.kvirc.net/) 10.37.01 # [Saint]: CustomWPS seems to use it exactly that way 10.37.04 # "state unknown" is %xd(Be) in my code, I just removed it here 10.37.46 # <[Saint]> gevaerts: I worded it weirdly. You *can* do it that way, but it (at least used to) make the steps uneven. 10.38.17 # but not because of unknown case 10.38.59 # I wrote "%?bl<| blablabla", I could have wrote "%?bl<%xd(Be)|blablabla" 10.39.05 # written* 10.39.43 # <[Saint]> I think what you're missing is that there is a case specifically for the 100% mark. 10.40.12 # that's not clear in CustomWPS then 10.40.14 # "%?bl(-1|0|1|2|...|N) " 10.40.48 # <[Saint]> Un unclear wiki/documentation in a FOSS project!?! 10.40.53 # * [Saint] is shocked. 10.40.55 # <[Saint]> ;) 10.41.08 # that's not Foss project, that's what any dev is using as reference doc except you :) 10.41.15 # theme designer* 10.42.10 # <[Saint]> It probably states the same thing, but you _should_ be using the manual. 10.42.33 # <[Saint]> The wiki is *not* to be considered an official source of documentation. 10.42.50 # <[Saint]> There is absolutely no obligation for anyone to maintain those pages. 10.43.01 # and there is an obligation for the user manual? 10.43.08 # <[Saint]> Yes. 10.43.09 # well, it's the only source of documentation so it's not really useful to say otherwise 10.43.19 # <[Saint]> ...it often doesn't happen, but, yes. 10.43.19 # as you said, it's probably written exactly the same thing for %?bl(-1|0|1|2|...|N) . 10.43.21 # (for some things) 10.43.55 # <[Saint]> Zagor: yes, that mess really annoys me. 10.44.28 # <[Saint]> there's acutally parts of the skin code that aren't documented in either the manual or the wiki 10.44.44 # so the trick would be adding twice the 4th bar: once for 75-99% and once for 100% 10.44.51 # <[Saint]> Its on my todo...but, I haven't had the time. 10.45.20 # <[Saint]> lebellium: I assume so. The battery behaves in exactly the same way. 10.46.40 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 10.49.28 # pamaury: Does vision28 have any hw buttons? 10.49.43 # wodz: power and hold 10.49.59 # on the same slider 10.51.42 # wodz: is there a list of the common usb ids for the rockchips on the wiki ? 10.51.52 # pamaury: The firmware was compiled with different compiler version (or with different flags) so FLIRT sigs don't catch much of interesting lowlevel functions. But the functions I found by hand seems to match SDK I have 10.52.20 # pamaury: don't think so 10.52.50 # good to know 10.53.09 # maybe we could write this information somwhere, that could help people identify the chip from the usb id 10.53.24 *** Saving seen data "./dancer.seen" 10.54.31 Quit kadoban (Ping timeout: 264 seconds) 10.54.33 # pamaury: In which way? The only helpful ids are for 'dfu' modes. All other are overwritten by DAP vendors 10.55.23 # I bet vision28 don't have the same vid:pid then my unbranded rk27xx 10.55.24 # all the archos present themselves as domain technologies... 10.55.37 # wow 10.55.56 # btw the way, I got my hands on a few cheap archos devices, some of them I already received: 14 vision which seems rknano based (usb is 071b:3203), same thing for the 15b vision 10.58.56 # pamaury: my unbranded rk27xx also presents itself as 071b:3203 10.59.10 # so this is not reliable 10.59.11 # ah maybe they are rk27xx then 10.59.20 # I don't remember what is the is of rknanob 10.59.33 # the only proof is to open the dap 10.59.58 # ah, 0x071b, 0x3226 11.00.05 # sure 11.00.15 # I'll post pictures of the 14 and 15b vision tonight 11.00.44 # sad news is they don't have a sd slot 11.01.34 # I really really need to find time and finish rk27xx ftl RE 11.01.51 # is it based on something well-known or not ? 11.01.57 # not at all 11.02.59 # do you have some symbols from the sdk at least ? 11.03.12 # yes and headers 11.03.59 # I am pretty far but real life is providing interrupt storm all the time 11.04.40 Join Provel [0] (~Provel@75-132-18-44.dhcp.stls.mo.charter.com) 11.05.16 # ah and there are sources for rk28 ftl in linux kernel released by archos 11.05.28 # this is different version though 11.17.30 Join trollin420 [0] (~chatzilla@user-0c6s742.cable.mindspring.com) 11.19.13 # hey what manual would i read for the ipod classic 7g for rockbox? 11.21.58 Join pretty_function [0] (~sigBART@123.252.212.53) 11.22.12 # pamaury: archos 3 vision also reports itself as 071b:3203 11.22.33 # do you own the device ? 11.24.04 # no, just googled for 071b:3203 11.24.47 # pentagram eon cineo is most probably rebranded ramos rm970 (071b:3203 also) 11.25.03 # can someone lemme know would the ipod video be the right manual to read for the classic 7g? 11.26.43 # trollin420: this will be the closest match, yes 11.27.52 # <[Saint]> trollin420: I let you know this very thing yesterday, and the day prior. 11.27.59 # yea i know 11.28.07 # but i forgot exactly which manual 11.28.19 # wanted to be sure before i downloaded the pdf 11.31.05 # out of curiosity, whats missing to put classic manual? 11.32.17 # <[Saint]> I'm not sure to be honest. 11.32.30 # <[Saint]> Mr. Someone really needs to pick that port back up. 11.33.16 # I would prefer the7 11.35.00 # * [Saint] assumes that if he had time for it, he's do so. 11.35.17 # <[Saint]> He's studying and busing paying bills like many of the rest of us. 11.35.35 # <[Saint]> s/busing/busy/ 11.35.59 # * [Saint] considers this all essentially a moot point, though. 11.36.19 # <[Saint]> As long as there's no official bootloader, this is all largely irrelevant. 11.36.59 # <[Saint]> There's really no point in a manual for a port with no official installation method. 11.37.52 # i think that's kinda a terrible argument 11.38.02 # lots of people *are* using it, and want to use it 11.38.15 # and not providing a manual is doing them a disservice for fairly arbitrary reasons 11.38.22 # yes, the install process is weird and not what we expect 11.38.34 # <[Saint]> Yes, certainly. I didn't say I agreed - but, that's how it is. 11.38.35 # but once you install it, it works as described in the manual :) 11.38.47 # I still think we should redefine the classic port to "rockbox for emcore/classic" 11.38.57 # <[Saint]> We either decide emCORE is official, make an actual bootloader, or...do nothing. 11.39.02 # There will be a proven installation method then :) 11.39.10 Join dys [0] (~user@2a01:1e8:e100:8296:21a:4dff:fe4e:273a) 11.39.49 # [Saint]: i don't think that's the right set of choices :) 11.40.03 # we could also just start building the manual and linking to the port anyway 11.40.28 # * gevaerts nods 11.40.28 # <[Saint]> technically speaking - we shouldn;t offer any support for it. 11.40.32 # why not? 11.40.43 # we offer all support on a best-effort basis anyway 11.40.43 # <[Saint]> There's no way to actually install it. 11.40.45 # We offer support to people *porting* 11.40.47 # it's not like it actually matters 11.41.22 Join Provel_ [0] (~Provel@75-132-18-44.dhcp.stls.mo.charter.com) 11.41.33 Quit Provel (Ping timeout: 240 seconds) 11.41.39 # <[Saint]> RbUtil only installs it IFF you've already used a bootloader that by and large we make no mention of. 11.41.46 # <[Saint]> its like a secret club, really. 11.42.07 # our current port categories conflate two things: whether the port actually works or not, and whether our docs/build system/tools cover it or not 11.42.32 # the ipod classic port isn't exactly done, but it clearly works and lots of people use it, and it's in a better state than nano2g where usb is just broken :) 11.43.07 # <[Saint]> the nano2g is in a better state, really - USB needs disabling. 11.43.10 # if we want to make installing sensible, we should have rbutil detect the ipodclassic and send you to the emcore install page 11.43.16 # <[Saint]> there's no reason fot there not to be an n2g release. 11.43.17 # if nothing else 11.43.29 # just so people don't ask why they cant' install it ;) 11.43.38 # the manual should get built, etc 11.43.45 # not doing these things isn't helping anyone 11.43.54 # the people who want to run rockbox on their classics are going to anyway 11.44.01 # they're just going to have to come hassle us somewhere first, in some cases 11.44.07 # <[Saint]> n2g is fine, save for the fact that USB panics - disabling USb is trivial, and we have dual-boot. 11.44.11 # because they didn't read the right one of our numerous cryptic wiki pages 11.44.17 # <[Saint]> there really should be a release for it. 11.44.34 # [Saint]: then someone should do the work 11.44.35 # stop picking apart my arbitrary example 11.44.38 # it really doesn't matter 11.44.52 # Right now, the n2g is *not* release-worthy 11.45.04 # my point is that we should be able to say "this port is known to not be perfect and may have issues, and you have to install it in a weird manual way" 11.45.11 # It doesn't matter how big the required changes are 11.45.16 # without relegating it to a state where people *can't find how to do anything with it* 11.45.23 # because the manual is missing and th install instructions are buried 11.46.23 # <[Saint]> According to [7], making emCORE into nothing but a bare metal stub that does nothing but boots Rockbox would be trivial - but the only one that really knows that code inside out is him. 11.46.45 # i don't care how much work it would be to *actually fix the port* 11.46.50 # that's irrelevant 11.47.00 # it hasn't been done, for quite a while 11.47.07 # so there's no particular reason to assume it will be done soon either :) 11.47.16 # and even if it were, other future ports may end up in this exact same sate 11.47.18 # state 12.03.48 Quit kaputnik_ (Ping timeout: 264 seconds) 12.04.24 Quit Provel_ (Quit: y'll niggas need jesus) 12.06.09 Join Provel [0] (~Provel@75-132-18-44.dhcp.stls.mo.charter.com) 12.10.03 Quit trollin420 (Quit: ChatZilla 0.9.90 [Firefox 18.0.1/20130119203203]) 12.36.48 Quit melmothX (Ping timeout: 264 seconds) 12.40.46 Quit FOAD (Quit: I'll be back) 12.43.16 # lebellium: ping 12.43.59 Join trollin420 [0] (~chatzilla@user-0c6s742.cable.mindspring.com) 12.45.00 # hey i created a shortcut by mistake and i cant seem to delete it? I highlighted the entry and press menu? 12.45.11 # lebellium: try g#426 12.45.13 # 3Gerrit review #426 at http://gerrit.rockbox.org/r/426 : simplelist: Fix simplelist_set_line_count() so it actually sets the count by Jonathan Gordon (changes/26/426/1) 12.49.59 # [Saint]: http://www.rockbox.org/irc/log-20130325#05:16:03 <- didnt that cause a pretty ehated "discussion" about 18 months ago? 12.51.02 # <[Saint]> JdGordon: menu order in general did, yes. 12.51.04 Join FOAD [0] (~foad@83.161.135.61) 12.51.04 Quit FOAD (Changing host) 12.51.04 Join FOAD [0] (~foad@unaffiliated/foad) 12.51.09 Join mortalis [0] (~kvirc@213.33.220.118) 12.51.25 # <[Saint]> but, I don't recall sanity checking for main menu context items being discussed. 12.53.26 *** Saving seen data "./dancer.seen" 12.57.31 # hi saint think i figued this out on my own but wanted to ask you about shortcut removal. can i just open the shortcuts.txt file and delete the entry from there, i shouldnt delete the whole text file right? 12.59.42 Quit pretty_function (Remote host closed the connection) 13.00.50 # trollin420: the context menu should ask you to delte it 13.01.11 # whatever action ususally gets you that 13.01.19 # so most likely long select 13.02.00 # i highlighted the entry from shortcuts and did a long select as well no context menu from there for it to ask me to delete the shortcut 13.05.36 Quit mortalis (Quit: KVIrc 4.1.3 Equilibrium http://www.kvirc.net/) 13.06.20 # just gonna try deleting the line from the txt file 13.09.37 # yep that worked. although a reboot of the player was required.... im sure everyone knows this but to manually remove an entry from the shortcuts menu go to the .rockbox folder and open shortcuts.txt in notedpad and simply delete the line that correspondes with the shortcut you want to remove 13.12.00 Quit trollin420 (Quit: ChatZilla 0.9.90 [Firefox 18.0.1/20130119203203]) 13.25.55 Join mortalis [0] (~kvirc@213.33.220.118) 13.31.07 Quit petur (Quit: *plop*) 13.35.20 Join amayer [0] (~amayer@mail.weberadvertising.com) 13.36.09 Quit mortalis (Quit: KVIrc 4.3.1 Aria http://www.kvirc.net/) 13.36.44 Join lebellium_ [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 13.38.29 Quit lebellium (Ping timeout: 248 seconds) 13.38.38 Nick lebellium_ is now known as lebellium (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 13.44.23 Join kadoban [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 13.53.57 Quit kadoban (Ping timeout: 248 seconds) 13.59.09 Quit derf (Remote host closed the connection) 14.15.27 Quit lebellium (Read error: Connection reset by peer) 14.15.59 Join lebellium [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 14.19.19 Join lebellium_ [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 14.20.37 Quit lebellium (Ping timeout: 248 seconds) 14.20.44 Nick lebellium_ is now known as lebellium (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 14.23.02 Join lebellium_ [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 14.26.50 Quit lebellium (Ping timeout: 252 seconds) 14.26.57 Nick lebellium_ is now known as lebellium (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 14.33.09 Join krabador [0] (~krabador@unaffiliated/krabador) 14.51.21 Quit olspookishmagus (Quit: free() the malloc()) 14.53.28 *** Saving seen data "./dancer.seen" 15.14.00 Quit kevku (Ping timeout: 264 seconds) 15.14.22 Quit wodz (Quit: Leaving) 15.16.20 Join derf [0] (~derf@fuzzyneural.net) 15.22.35 Join jsntyyl [0] (~jsntyyl@223.166.17.140) 15.26.47 Quit jsntyyl (Ping timeout: 245 seconds) 15.30.15 Join jsntyyl [0] (~jsntyyl@223.166.17.140) 15.30.22 Part jsntyyl 16.03.41 Join lebellium_ [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 16.04.17 Join lebellium__ [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 16.06.16 Quit lebellium (Ping timeout: 246 seconds) 16.06.26 Nick lebellium__ is now known as lebellium (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 16.08.36 Quit lebellium_ (Ping timeout: 272 seconds) 16.08.36 Quit dys (Ping timeout: 264 seconds) 16.09.14 Join dys [0] (~user@2a01:1e8:e100:8296:21a:4dff:fe4e:273a) 16.16.28 Join lebellium_ [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 16.17.36 Quit lebellium (Ping timeout: 240 seconds) 16.17.38 Nick lebellium_ is now known as lebellium (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 16.26.47 Quit Zagor (Quit: Clint excited) 16.27.33 Join froggyman [0] (~me@msoe-00033403.nebula.msoe.edu) 16.27.33 Quit froggyman (Changing host) 16.27.33 Join froggyman [0] (~me@unaffiliated/froggyman) 16.36.26 Quit FOAD (Remote host closed the connection) 16.36.52 Quit pamaury (Ping timeout: 240 seconds) 16.38.15 Join kevku [0] (~kevku@2001:470:27:773:0:feed:c0f:fee) 16.39.31 Quit froggyman (Ping timeout: 246 seconds) 16.40.01 Join FOAD [0] (~foad@83.161.135.61) 16.40.01 Quit FOAD (Changing host) 16.40.01 Join FOAD [0] (~foad@unaffiliated/foad) 16.45.37 # sorry JdGordon, it doesn't fix the issue 16.46.55 Part dys ("Killed buffer") 16.49.05 Join lebellium_ [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 16.49.57 Quit lebellium (Ping timeout: 248 seconds) 16.50.01 Nick lebellium_ is now known as lebellium (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 16.52.56 Join SuperBrainAK [0] (~Andy@97-124-89-175.phnx.qwest.net) 16.53.31 *** Saving seen data "./dancer.seen" 16.54.18 Join kaitsu1 [0] (~bubba@a91-152-170-133.elisa-laajakaista.fi) 16.54.24 Join ej0rge [0] (~alhaz@207.135.137.71) 16.55.15 # "Undefined instruction" crash on clipzip when plugging in usb is a known issue, yes? 16.58.04 # ej0rge: may be related to FS#12639 16.58.05 # http://www.rockbox.org/tracker/task/12639 3Certain themes cause the WPS to not load properly and USB to not work (bugs, unconfirmed) 17.00.00 # lebellium: yeah that seems likely. I'll try cabbiev2 and see what happens 17.00.31 # lebellium: fwiw i was using your samsung-like theme 17.00.52 # yeah, that seems to have resolved it 17.01.03 # thanks 17.02.24 # I personaly use mainly my theme and revert back to cabbieV2 when I need to transfer files. Not really practical but well... 17.05.13 # *shrug* I have a 4gb clipzip with a 32mb card in it. First time i tried to use it as a usb device in a very long time yesterday, since it's so easy to just eject the card and plug it into a laptop. 17.09.15 # 32GB you mean :) 17.12.32 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 17.25.35 # yeah 17.33.24 Join kaputnik_ [0] (~kaputnik@port-92-206-174-134.dynamic.qsc.de) 17.44.43 Join lebellium_ [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 17.45.12 Quit lebellium (Ping timeout: 240 seconds) 17.45.24 Nick lebellium_ is now known as lebellium (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 17.53.29 # Bye! 17.53.31 Quit redhot (Quit: KVIrc 4.1.3 Equilibrium http://www.kvirc.net/) 17.56.03 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 17.59.36 Quit kaputnik_ (Read error: Operation timed out) 17.59.53 Join kaputnik_ [0] (~kaputnik@port-92-206-174-134.dynamic.qsc.de) 18.07.42 Join kadoban [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 18.10.56 Join gomgk [0] (~62ee2e88@www.haxx.se) 18.15.52 Quit gomgk (Quit: CGI:IRC (EOF)) 18.16.23 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 18.30.54 Join Strife89 [0] (~Strife89@2602:306:250d:f4d9:c4d7:502:5161:9667) 18.44.48 Join ender` [0] (~ender@foo.eternallybored.org) 18.53.33 *** Saving seen data "./dancer.seen" 19.01.37 Join pretty_function [0] (~sigBART@123.252.213.174) 19.08.02 # wodz: i've disassemble the archos vision 14, it's a rknano-b 19.08.13 # sorry 15b 19.27.48 # oh and 14 vision is also rknano-b 19.27.57 # i'll upload the pics soon 19.34.02 Quit krabador (Quit: Sto andando via) 19.34.52 Quit Rower (Ping timeout: 240 seconds) 19.35.00 # 48 hours till the deadline for GSOC mentoring orgs to apply 19.35.14 # I still haven't seen any massive appetite for it this year 19.37.25 Join Rower [0] (husvagn@v-413-alfarv-177.bitnet.nu) 19.42.00 Nick GodEater` is now known as GodEater (~whoknows@151.225.2.99) 19.42.11 Quit GodEater (Changing host) 19.42.11 Join GodEater [0] (~whoknows@rockbox/staff/GodEater) 19.42.13 Quit pamaury (Ping timeout: 246 seconds) 19.44.23 Join froggyman [0] (~me@155.92.69.181) 19.44.23 Quit froggyman (Changing host) 19.44.23 Join froggyman [0] (~me@unaffiliated/froggyman) 19.45.11 Join jhMikeS [0] (~jethead71@50.4.247.132) 19.45.11 Quit jhMikeS (Changing host) 19.45.11 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) 19.47.10 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 20.13.36 # Ain't gonna happen 20.13.39 # up 20.13.49 # ooops 20.24.34 Quit pretty_function (Ping timeout: 246 seconds) 20.24.36 Join pretty_f_ [0] (~sigBART@123.252.213.174) 20.26.01 Nick pretty_f_ is now known as pretty_function (~sigBART@123.252.213.174) 20.28.02 Quit jhMikeS (Read error: Connection reset by peer) 20.33.21 Quit kaitsu1 (Quit: ( www.nnscript.com :: NoNameScript 4.22 :: www.esnation.com )) 20.34.57 # [Saint]: it's actually not that easy. 20.35.28 # the problem is that the installation implementation in Rockbox Utility doesn't know about the selected player, it just knows about the files it's supposed to work on (and where to get them) 20.36.16 # personally I'm not too fond of the link to the Sandisk forums at all. We don't have control over that URLs and they can change at any time. 20.36.32 # I'd prefer to only link to our wiki, and we could have deep links over there. 20.37.05 # furthermore, Rockbox Utility doesn't know about the supported firmware versions. mkamsboot knows that, and it will check (and show the list in the error message) the firmware 20.37.23 Quit esperegu (Ping timeout: 264 seconds) 20.37.58 Join Strife1989 [0] (~Strife89@2602:306:250d:f4d9:c4d7:502:5161:9667) 20.38.37 Join esperegu [0] (~quassel@ip-213-124-221-141.ip.prioritytelecom.net) 20.41.05 Quit Strife89 (Ping timeout: 240 seconds) 20.46.13 Quit akaWolf (Ping timeout: 245 seconds) 20.52.59 Quit froggyman (Ping timeout: 258 seconds) 20.53.37 *** Saving seen data "./dancer.seen" 20.57.01 Quit pretty_function (Remote host closed the connection) 21.02.20 Join froggyman [0] (~me@unaffiliated/froggyman) 21.02.35 Join Krosis_ [0] (~Krosis@97-86-82-70.static.aldl.mi.charter.com) 21.27.29 Join lebellium_ [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 21.29.17 Quit lebellium (Ping timeout: 245 seconds) 21.29.24 Nick lebellium_ is now known as lebellium (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 21.35.20 Quit Krosis_ (Quit: There's no place like 127.0.0.1) 21.38.59 Join krabador [0] (~krabador@unaffiliated/krabador) 21.40.46 Quit y4n (Quit: PÆNTS ØLF!) 21.44.53 Join benedikt93 [0] (~benedikt9@unaffiliated/benedikt93) 21.59.39 # <[Saint]> bluebrother: yeah - sorry, I am aware that RbUtil itself isn't all that smart, and the various player-specific tools do the version checking for FW files, but I was trying not to overwhelm the person I was talking to with irrelevant (to them) complications. 22.01.20 # <[Saint]> The annoying thing is SanDisck's URL structure - its not even possible to dump them in the "root" of the updates page, as there doesn't seem to be any such thing. The URL is specially crafted, and this involves us playing catch-ups if we always want to point to the "right" one. :-S 22.03.32 Quit amayer (Ping timeout: 248 seconds) 22.05.11 Quit amithkk (Remote host closed the connection) 22.05.22 Join wodz [0] (~wodz@89-75-41-78.dynamic.chello.pl) 22.07.15 # pamaury: how much ram does rknano-b have? From your wiki entry it sounds like 1MB. If so is it even worth the effort? 22.11.39 Quit kaputnik_ (Ping timeout: 246 seconds) 22.12.19 Join petur [0] (~petur@rockbox/developer/petur) 22.14.46 # pamaury: BTW. http://www.amazon.cn/ONN-%E6%AC%A7%E6%81%A9-Q3-MP3-4G-%E7%B2%89%E8%89%B2/dp/B005I22XZ0 seems to support your finding about cortex-M3 in rknano-b 22.16.26 # <[Saint]> Nothing quite says "Awesome DAP" like a cupped hand holding a tiny house... 22.16.45 # [Saint]: no problem :) 22.17.08 # though as said, personally I'd prefer not to link to the Sandisk website and instead use a wiki page on our end. 22.17.25 # since that is much easier to change 22.17.40 # we could even implement some kind of forwarding mechanism ... 22.18.18 # <[Saint]> The user in question was right about the instructions being very vague about what happens here. 22.18.49 # <[Saint]> The impression given is either: any firmware will work; or; only this *specific* version will work. 22.19.00 # we don't need to confuse users by adding too much information :) 22.19.12 # <[Saint]> too little is also problematic. 22.20.21 # it might be a good idea to be a bit more verbose about automatic installation in the manual 22.20.56 # one problem is that we can't say that a specific version works because several versions do. 22.21.14 # <[Saint]> The thing I see as problematic is that we don't actually give the user any input on what FW version(s) are supported. 22.21.16 # otoh we can't say that any version works because we don't know if Sandisk released a new one in the meantime 22.21.43 # <[Saint]> if we could print the versions that *do* work, even if we can't link to them - that may be better. 22.21.45 # we do. When the user provides a firmware version that is unknown he'll get a message saying which versions to try 22.22.03 # <[Saint]> yeah - the problem is, this user didn't want to risk that. 22.22.13 # <[Saint]> remember, these people think players are made of magic. 22.22.22 # so he obviously didn't trust us enough :D 22.22.25 # <[Saint]> he thought that may brick the device. 22.22.40 # * bluebrother trusts himself pretty much. Usually :D 22.22.41 # <[Saint]> since it didn't state "yes, this is OK to do" 22.22.50 # <[Saint]> he...uhhh...didn't. 22.22.58 # <[Saint]> s/he 22.24.42 Join kaputnik_ [0] (~kaputnik@port-92-206-35-85.dynamic.qsc.de) 22.25.43 # <[Saint]> I don't think its a trust thing, I think it more a case of "some people need *very* specific steps and hand-holding". 22.26.23 # <[Saint]> Unless it actually stated "yep - this is OK", there was no way this user was going to procede. 22.26.33 # <[Saint]> We actually need more users like this one ;) 22.27.17 # <[Saint]> s/he waited a few days trying to gethold of someone to tell him/her exactly what to do, and reassure him/her that the device wouldn't catch fire. 22.27.50 # I'm not sure if we really need more such users 22.28.17 # I haven't heard of such an issue in all the years I'm working on Rockbox Utility. So I don't see much of a problem here. 22.28.35 # yes, some users need more hand holding. But we have out support channels for this :) 22.29.34 # <[Saint]> I went through the install myself (I don't actually have the device, so I had to tell lies to rbutil), and I got the impression myself that only one specific fw version is accepted. 22.29.54 # <[Saint]> the user seemed to think it problematic that it wasn't the current one, and wouldn't procede. 22.30.52 # I don't think the text in that dialog box implies only one version to work. 22.31.02 # <[Saint]> but, you're right - they can always come find us here. The non-obvious thing to the user was that the device won't actually let them do "the wrong thing" I suppose. 22.31.07 # but if you have better wording I'm all for it 22.32.02 # in general I prefer users that aren't confident enough to not install Rockbox. Changing the firmware of a device is a rather major change so you should be aware of what you're doing 22.32.28 # you don't install Linux on your Windows PC if you're not aware what you're doing either :) 22.32.40 # <[Saint]> which is why I said earlier we need more users like this guy/girl...but you disagreed ;) 22.33.06 # <[Saint]> s/he found something they didn;t understand/questioned, and stopped dead in their tracks. 22.33.09 Join amithkk [0] (uid4289@2buntu/writers/amithkk) 22.33.12 # <[Saint]> *that*s what we need more of. 22.33.12 # we need more users that require more support? I don't see a benefit from that :) 22.33.23 # aaah, now I get your point :) 22.33.30 # ok, with that one I do agree 22.33.36 # <[Saint]> more support for trivial things may directly lead to less support for serious things. 22.33.44 # yes. 22.40.51 Join amayer [0] (~amayer@h242.176.123.208.dynamic.ip.windstream.net) 22.46.40 # how many developers have shown up because they were attracted to the project VS attracted to the product? 22.47.40 # <[Saint]> Ohhhh - that's an interesting one. 22.53.21 Quit froggyman (Ping timeout: 258 seconds) 22.53.38 *** Saving seen data "./dancer.seen" 22.58.03 # <[Saint]> soap: I would think a reasonably large volume of new developers discover us because they feel thay have nice hardware that "could be more". 22.58.13 # <[Saint]> ...and then find out that there are no alternatives. 22.58.43 # <[Saint]> Without some form of survey (perhaps shoot something by way of the mailing list), you'll probably never know though. 23.02.06 Join froggyman [0] (~me@dhcp-155-92-103-232.nebula.msoe.edu) 23.02.07 Quit froggyman (Changing host) 23.02.07 Join froggyman [0] (~me@unaffiliated/froggyman) 23.06.09 Quit Strife1989 (Quit: Vamoose!) 23.08.28 # wodz: I don't know the amount of ram, probably 512kB or 1MB I would say, not much 23.09.11 Quit kevku (Ping timeout: 264 seconds) 23.15.42 Quit pamaury (Ping timeout: 246 seconds) 23.22.28 Quit petur (Quit: Leaving) 23.22.29 Quit shamus (Read error: Connection reset by peer) 23.23.42 Join shamus [0] (~shmaus@ip-206-192-195-49.marylandheights.ip.cablemo.net) 23.25.55 Part LinusN 23.32.01 Quit benedikt93 (Quit: Bye ;)) 23.38.51 # <[7]> Torne: USB is just broken on the classic as well, at least for some users 23.39.23 # <[7]> not quite sure what the reason is - if I had time for it I'd probably rip it all out and do it from scratch based on a newer USB driver that I've written for the STM32 series of chips which have the same usb core 23.40.22 # <[7]> there's no real reason to keep emcore involved in the classic port - it's just that nobody seems to be willing to cherrypick the required parts and build a rockbox bootloader out of it at this point 23.41.09 # <[7]> dualboot is another of these problems that mr. someone should look into - I bet the cause is trivial, but it needs to be found, and tracking down an OF crash is a rather painstaking process 23.41.46 # <[Saint]> [7]: I think, and this was somewhat confirmed yestarday, everyone is kinda hoping you'd do it. 23.42.34 # <[7]> yeah, if only I had the time for that... 23.42.54 # <[7]> I might try to assist a coordinated effort at least :) 23.42.54 # * [Saint] mentioned you're in study/bill-paying mode lately :) 23.43.51 # <[7]> one more thing: IF we were to kick emcore out of this process, how should the installation process look like? 23.44.37 # <[7]> from what it looks like the flashed bootloader is only exploitable on first generation classics that haven't been firmware updated 23.44.50 # <[7]> so those are the only ones that could be bootstrapped by just writing to the firmware partition 23.44.53 # <[Saint]> my assumption is; rbutil detects the model; prompts user to enter DFU and shows how if necessary; then . 23.45.19 # <[Saint]> I think DFU and pressing a button should be all the manual intervention required. 23.45.44 # <[7]> which kinda means that DFU is our only attack vector. but DFU means: 1. we need our own driver and get rid of interfering itunes stuff, or 2. we need to have itunes installed, piggyback on its driver, and stop it from interfering 23.45.57 # <[7]> do we have other targets that use a custom driver in rbutil already? 23.46.31 # <[Saint]> Ohhh - good point. 23.46.42 # <[Saint]> One supposes bluebrother is the man to ask. 23.47.00 # <[7]> then, after we are in DFU mode, we run into the next problem: we can only upload up to 128KB of data to IRAM, because DRAM isn't initialized yet. if we squeeze it really tight, we might be able to fit a rockbox bootloader with USB support into that 23.47.38 # <[7]> or, we fix the OF and just install something emcore-based that basically runs diskmode to do further installation 23.48.46 # <[7]> or we could try a totally different approach: just patching out the sigchecks in apple's bootloader, and doing an ipod video-like installation 23.49.11 # <[7]> that would magically fix dualboot for disk mode at least 23.50.08 # <[7]> it would require a specific (latest?) apple bootloader to be installed though, or some fuzzy patching algorithm 23.51.53 # <[7]> that kind of installation method would also make uninstallation even more trivial (not requiring DFU, and keeping the disabled sigchecks in place) 23.52.20 # <[7]> the nano2g/classic shares its USB driver with AMSv2, right? 23.52.32 # <[7]> does USB work properly on all AMSv2 targets? 23.52.45 # not at all 23.53.20 # <[7]> so that driver is basically just broken, and this isn't an ipod-specific problem at all? 23.54.13 # I don't know if they share the USB driver but USB is very unstable on AMSv2 23.54.19 # <[Saint]> it *does* work. 23.54.26 # <[7]> kinda fits the pattern 23.54.31 # <[Saint]> ...just, erratically. 23.54.34 # <[Saint]> and not for all. 23.54.53 # * [7] ponders doing an experiment 23.55.36 # <[7]> how bad does it fail usually, if it fails? no response at all? 23.56.13 # I would say it behaves too randomly to answer this question 23.56.32 # <[Saint]> based on your experience, perhaps. 23.56.37 # <[Saint]> for some, it works flawlessly. 23.57.10 # <[7]> I'm pondering to attempt porting over my bare metal USB driver for that core to nano2g 23.57.18 # <[7]> and try if it enumerates at all