--- Log for 01.04.112 Server: Not connected Channel: None joined --- Nick: No nick Version: Dancer V4.16 Started: 0 seconds ago 01.12.22 *** Started Dancer V4.16 01.12.22 *** Connected to irc.freenode.net on port 6667 01.12.22 *** Logfile for #rockbox started 01.12.26 Mode "logbot_ :+i" by logbot_ 01.12.30 *** Server message 501: 'logbot_ :Unknown MODE flag' 01.12.30 Join logbot_ [0] (~rockbox@giant.haxx.se) 01.12.30 Join The_prospector [0] (baconmaste@unaffiliated/cornman) 01.12.30 Join stoffel [0] (~quassel@pD9E43A71.dip.t-dialin.net) 01.12.30 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 01.12.30 Join pixelma [0] (pixelma@rockbox/staff/pixelma) 01.12.30 Join amiconn [0] (amiconn@rockbox/developer/amiconn) 01.12.30 Join T44 [0] (~Topy44@f049011058.adsl.alicedsl.de) 01.12.30 Join domonoky [0] (~Domonoky@rockbox/developer/domonoky) 01.12.30 Join anewuser_ [0] (~anewuser@186.93.175.208) 01.12.30 Join fs-bluebot [0] (~fs-bluebo@g226070233.adsl.alicedsl.de) 01.12.30 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 01.12.30 Join remlap [0] (~Patrick@190.28.169.217.in-addr.arpa) 01.12.30 Join curtism [0] (~curtis@unaffiliated/programble) 01.12.30 Join enthdegree [0] (~BitchX@unaffiliated/enthdegree) 01.12.30 Join FOAD [0] (~foad@unaffiliated/foad) 01.12.30 Join Guinness` [0] (Slayer@c-68-55-111-159.hsd1.va.comcast.net) 01.12.30 Join Cthulhux [0] (cthulhux@piratenpartei/ni/tux) 01.12.30 Join kadoban_ [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 01.12.30 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 01.12.30 Join Bagder [241] (~daniel@rockbox/developer/bagder) 01.12.30 Join AlexP [0] (~alex@rockbox/staff/AlexP) 01.12.30 Join lebellium [0] (~chatzilla@g225187034.adsl.alicedsl.de) 01.12.30 Join thegeek [0] (thegeek@171.17.9.46.customer.cdi.no) 01.12.30 Join nosa-j [0] (~m00k@adsl-74-235-42-150.clt.bellsouth.net) 01.12.30 Join prof_wolfff [0] (~prof_wolf@81.61.201.173.dyn.user.ono.com) 01.12.30 Join qnm [0] (~qnm@2001:44b8:3110:f300:208:9bff:fec0:179a) 01.12.30 Join Rower85 [0] (husvagn@v-413-alfarv-90.bitnet.nu) 01.12.30 Join lembas [0] (iam@lembas.ws) 01.12.30 Join [Saint] [0] (~Saint]@unaffiliated/saint/x-8516940) 01.12.30 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 01.12.30 Join pystar90 [0] (~pystar90@frnk-590d5257.pool.mediaWays.net) 01.12.30 Join ved [0] (~ved@2001:41d0:1:5914::2) 01.12.30 Join Galois [0] (djao@efnet-math.org) 01.12.30 Join bieber [0] (~quassel@97.97.75.169) 01.12.30 Join advcomp2019__ [0] (~advcomp20@unaffiliated/advcomp2019) 01.12.30 Join Sleepy_Coder [0] (~z_Z_z_Z_z@unaffiliated/sleepycoder/x-938672) 01.12.30 Join jordan` [0] (~gromit@2001:660:3302:2826:225:90ff:fe20:d9a8) 01.12.30 Join k4tfish [0] (~caff7@reniced.net) 01.12.30 Join azhag [0] (azhag@dug.net.pl) 01.12.30 Join fyrestorm [0] (~nnscript@cpe-68-173-235-85.nyc.res.rr.com) 01.12.30 Join gevaerts [0] (~fg@rockbox/developer/gevaerts) 01.12.30 Join adnap [0] (~adnap@rrcs-108-178-116-149.sw.biz.rr.com) 01.12.30 Join tchan [0] (~tchan@lunar-linux/developer/tchan) 01.12.30 Join efyx [0] (~efyx@lap34-1-82-225-185-146.fbx.proxad.net) 01.12.30 Join SynrG [0] (~synrg@debian/developer/synrg) 01.12.30 Join Naked [0] (~naked@naked.iki.fi) 01.12.30 Join ender| [0] (~ender1@foo.eternallybored.org) 01.12.30 Join KiwiCam [0] (~KiwiCAM@101.98.171.48) 01.12.30 Join ruskie [0] (ruskie@sourcemage/mage/ruskie) 01.12.30 Join Zoiah [0] (zoiah@matryoshka.zoiah.net) 01.12.30 Join funman [0] (~fun@rockbox/developer/funman) 01.12.30 Join martii [0] (~martii@212.33.90.253) 01.12.30 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) 01.12.30 Join nuskool [0] (~nuskool@s.pl0rt.org) 01.12.30 Join TBCOOL [0] (~tb@c-123071d5.09-42-73746f22.cust.bredbandsbolaget.se) 01.12.30 Join Synergist [0] (~synfn@unaffiliated/synergist) 01.12.30 Join amithkk [0] (u4289@2buntu/writers/amithkk) 01.12.30 Join n17ikh [0] (~peter@c-174-56-150-44.hsd1.sc.comcast.net) 01.12.30 Join mystica555 [0] (~Mike@71-211-200-241.hlrn.qwest.net) 01.12.30 Join soap [0] (~soap@rockbox/staff/soap) 01.12.30 Join alexbobp [0] (~alex@capitalthree.pwnz.org) 01.12.30 Join guymann [0] (~charles@64-252-120-203.adsl.snet.net) 01.12.30 Join yosafbridge [0] (~yosafbrid@li125-242.members.linode.com) 01.12.30 Join crwl [0] (~crwlll@dsl-jklbrasgw1-ffb9c300-103.dhcp.inet.fi) 01.12.30 Join ps-auxw [0] (~arneb@2001:470:c807:0:1532:4e5f:2ad3:4123) 01.12.30 Join froggyman [0] (~froggyman@unaffiliated/froggyman) 01.12.30 Join Torne [0] (~torne@rockbox/developer/Torne) 01.12.30 Join vsrinivas [0] (U2FsdGVkX1@batman.acm.jhu.edu) 01.12.30 Join Staphylo [0] (~Staphylo@mareo.fr) 01.12.30 Join saratoga [0] (980329b4@gateway/web/freenode/ip.152.3.41.180) 01.12.30 Join sinthetek [0] (~sinthetek@unaffiliated/sinthetek) 01.12.30 Join preglow [0] (thomj@tvilling2.pvv.ntnu.no) 01.12.30 Join aevin [0] (eivindsy@unaffiliated/aevin) 01.12.30 Join freqmod [0] (~quassel@2001:700:300:1430:226:18ff:fe82:1a24) 01.12.30 Join kugel [0] (~kugel@rockbox/developer/kugel) 01.12.30 Join Mir [0] (~Mir@pool-71-109-219-163.lsanca.dsl-w.verizon.net) 01.12.30 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 01.12.30 Join nomada [0] (~nomada@irc.consciente.de) 01.12.30 Join Zambezi [0] (Zulu@bnc.fran.dotbnc.se) 01.12.30 Join scorche [0] (~scorche@rockbox/administrator/scorche) 01.12.30 Join ThomasAH [0] (~thomas@aktaia.intevation.org) 01.12.30 Join wtachi [0] (~wtachi@bloom.wtachi.us) 01.12.30 Join Riviera [0] (~Riviera@92.51.147.16) 01.12.30 Join Rondom [0] (~rondom@2a01:488:66:1000:b24d:4f2f:0:1) 01.12.30 Join scorche|sh [0] (~scorche@rockbox/administrator/scorche) 01.12.30 Join kaner [0] (~kaner@zzz.strace.org) 01.12.30 Join Poodlemastah [0] (~Poodlemas@h-152-191.a218.priv.bahnhof.se) 01.12.30 Join user890104 [0] (venci@Addicted.to.Minecraft.ipv6.6bez10.info) 01.12.30 Join Utchy [0] (~Utchy@rps6752.ovh.net) 01.12.30 Join ej0rge [0] (~alhaz@207.135.137.71) 01.12.30 Join Elfish [0] (amba@fuplz.co.cc) 01.12.30 Join CIA-44 [0] (~CIA@cia.atheme.org) 01.12.30 Join Barahir [0] (~Barahir@fb08-acstud01.anorg.chemie.uni-giessen.de) 01.12.30 Join simabeis_ [0] (~simabeis@lobmenschen.de) 01.12.30 Join ack [0] (~ack@mingbai.org) 01.12.30 Join eintopf [0] (~eintopf@zzz.strace.org) 01.12.30 Join pjm0616 [0] (~user@175.209.206.227) 01.12.30 Join desowin_ [0] (~desowin@ip-69-162-133-251.static.chi2.systeminplace.net) 01.12.30 Join ranma|tokyo [0] (ranma@2a01:4f8:130:9321::2) 01.12.30 Join rasher [0] (~rasher@rockbox/developer/rasher) 01.12.30 Join beta2k [0] (~Beta2K@d24-36-128-84.home1.cgocable.net) 01.12.30 Join mikroflops_ [0] (~yogurt@h-34-156.a238.priv.bahnhof.se) 01.12.30 Join GodEater [0] (~bibble@rockbox/staff/GodEater) 01.12.30 Join Farthen [0] (~Farthen@2a01:4f8:101:2a4:0:bc28:b2e1:9) 01.12.30 Join ehntoo [0] (ehntoo@gateway/shell/mtu-lug/x-byhoqxhlifvcvcxf) 01.12.30 Join Slasheri [0] (miipekk@rockbox/developer/Slasheri) 01.12.30 Join @ChanServ [0] (ChanServ@services.) 01.12.30 Join zu [0] (~zu@ks387228.kimsufi.com) 01.12.30 Join maraz [0] (maraz@kapsi.fi) 01.12.30 Join Jack87 [0] (Jack87@nasadmin/admin/jack87) 01.12.30 Join bzed [0] (~bzed@devel.recluse.de) 01.12.30 Join Unhelpful [0] (~quassel@rockbox/developer/Unhelpful) 01.12.30 Join ranma_ [0] (ranma@2a01:4f8:62:2262::2) 01.12.30 Join timotimo [0] (~timo@gallifrey.wybt.net) 01.12.30 Join GeekShadow [0] (~antoine@50.104.75.86.rev.sfr.net) 01.12.30 Join rudi_s [0] (~simon@austria125.server4you.de) 01.12.30 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 01.12.30 Join dionoea [0] (~dionoea@videolan/developer/dionoea) 01.12.30 Join knittl [0] (~knittl@unaffiliated/knittl) 01.14.29 # hey the site's back! hooray 01.15.05 Quit domonoky (Read error: Connection reset by peer) 01.17.13 # morning 01.22.15 Topic "3.11 has been branched | Please read before speaking: http://www.rockbox.org/wiki/IrcGuidelines | Please direct offtopic/social chat to #rockbox-community | This channel is logged at http://www.rockbox.org/irc" by ChanServ (ChanServ@services.) 01.25.47 # JdGordon: morning, as I asked you when you were sleeping, do you have any idea why a list would "jitter" on a touchscreen target in grid mode ? 01.26.20 # depends what jitter means :) 01.29.34 Quit bertrik (Quit: And That, My Liege, Is How We Know the Earth to Be Banana Shaped) 01.31.16 Quit The_prospector (Read error: Connection reset by peer) 01.31.22 Join The_prospector [0] (baconmaste@unaffiliated/cornman) 01.32.02 # JdGordon: it will "go up" by a few pixels then back to the original position. And it happen every time you scroll. And on some list nearly empty lists, it will even jitter without touching the device 01.38.37 # are you sure everything thinks it is in grid mode? 01.39.34 # what do you mean ? 01.40.09 # I didn't modify anything, it even happen in the root menu 01.40.44 # ok, why do you tihnk you're in grid mode? 01.41.42 # because it behaves exactly like in grid mode: depending on where you touch the screen it either goes up or down one element, select the element or goes back to the previous menu 01.44.24 # you dont have gdb on target do you? :p 01.45.42 # no 01.46.07 # I could check if it also happen in the simulator though 01.48.26 # but I haven't add the stuff to successfully build the simulator :-/ I'll try tomorrow, thanks for your help 01.49.18 Quit guymann (Quit: brb) 01.50.28 Join guymann [0] (~charles@64-252-120-203.adsl.snet.net) 01.50.55 Quit lebellium (Quit: ChatZilla 0.9.88.1 [Firefox 12.0/20120328051619]) 01.51.46 Quit guymann (Client Quit) 01.53.40 Join enth [0] (~BitchX@unaffiliated/enthdegree) 01.54.41 Quit pamaury (Remote host closed the connection) 01.55.16 Join guymann [0] (~charles@64-252-120-203.adsl.snet.net) 01.55.49 Join Keripo [0] (~Keripo@eng412.wireless-resnet.upenn.edu) 01.56.14 Quit enthdegree (Ping timeout: 246 seconds) 02.13.41 Join othniel [0] (~othniel@75.92.51.2) 02.18.34 Quit othniel (Ping timeout: 260 seconds) 02.21.56 Quit stoffel (Remote host closed the connection) 02.27.10 Join XavierGr [0] (~xavier@rockbox/staff/XavierGr) 02.41.06 Quit enth (Read error: Connection reset by peer) 02.42.33 Join enthdegree [0] (~BitchX@unaffiliated/enthdegree) 02.43.20 Quit enthdegree (Read error: Connection reset by peer) 02.54.19 Quit kadoban_ (Quit: bye) 02.54.29 Join kadoban_ [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 03.00.51 Quit kadoban_ (Ping timeout: 265 seconds) 03.11.41 Join guest829385 [0] (~aoeu@112.166.15.141) 03.12.24 *** Saving seen data "./dancer.seen" 03.14.16 Quit guest829385 () 03.15.01 Quit Keripo (Quit: Leaving.) 03.16.43 Join guest829385 [0] (~aoeu@112.166.15.141) 03.21.51 Quit guest829385 (Remote host closed the connection) 03.22.40 Join guest829385 [0] (~aoeu@112.166.15.141) 03.53.55 Join CaptainKewl [0] (captainkew@207-237-110-248.c3-0.nyr-ubr2.nyr.ny.cable.rcn.com) 03.54.52 Quit prof_wolfff (Ping timeout: 246 seconds) 04.25.40 Join othniel [0] (~othniel@75.92.51.2) 04.30.00 Quit othniel (Ping timeout: 252 seconds) 04.44.44 Quit Rower85 (Quit: Hmmm...) 04.45.31 Quit TheSeven (Disconnected by services) 04.45.41 Join [7] [0] (~quassel@rockbox/developer/TheSeven) 04.51.32 Quit pixelma (Disconnected by services) 04.51.32 Join amiconn_ [0] (quassel@rockbox/developer/amiconn) 04.51.32 Quit amiconn (Disconnected by services) 04.51.34 Join pixelma_ [0] (pixelma@rockbox/staff/pixelma) 04.51.36 Nick pixelma_ is now known as pixelma (pixelma@rockbox/staff/pixelma) 04.51.54 Nick amiconn_ is now known as amiconn (quassel@rockbox/developer/amiconn) 04.57.20 Quit anewuser_ (Read error: Connection reset by peer) 04.58.49 Quit pystar90 (Ping timeout: 272 seconds) 05.08.33 Quit mc2739 (Ping timeout: 244 seconds) 05.10.43 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 05.11.49 Join Keripo [0] (~Keripo@eng412.wireless-resnet.upenn.edu) 05.12.28 *** Saving seen data "./dancer.seen" 05.20.35 Join perrikwp [0] (~quassel@173-102-239-122.pools.spcsdns.net) 05.20.35 Quit k4tfish (Quit: ZNC - http://znc.in) 05.28.44 Join diginet [0] (~diginet@ppp-70-246-16-75.dsl.hstntx.swbell.net) 05.54.38 Quit XavierGr (Ping timeout: 265 seconds) 06.13.34 Part Cthulhux 06.38.11 Join othniel [0] (~othniel@75.92.51.2) 06.42.31 Quit othniel (Ping timeout: 252 seconds) 07.12.31 *** Saving seen data "./dancer.seen" 07.30.17 Join robin0800 [0] (~robin0800@149.254.61.216) 07.32.03 Quit diginet (Ping timeout: 260 seconds) 07.45.41 Quit guest829385 (Read error: No route to host) 07.45.57 Join guest829385 [0] (~aoeu@112.166.15.141) 07.48.59 Join pystar90 [0] (~pystar90@frnk-590d5358.pool.mediaWays.net) 08.09.42 Quit CaptainKewl (Ping timeout: 264 seconds) 08.50.21 Join othniel [0] (~othniel@75.92.51.2) 08.55.08 Quit othniel (Ping timeout: 265 seconds) 09.08.50 Join bertrik [0] (~bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 09.08.50 Quit bertrik (Changing host) 09.08.50 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 09.12.34 *** Saving seen data "./dancer.seen" 09.13.12 Join stoffel [0] (~quassel@pD9E42CD4.dip.t-dialin.net) 09.36.59 Join kadoban_ [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 09.41.17 Join bitcraft [0] (~bitcraft@173-20-20-92.client.mchsi.com) 09.55.57 Join Carcino [0] (~Miranda@dsl-kvlbrasgw2-fec9dc00-77.dhcp.inet.fi) 09.57.00 # Hello. Was just wondering why morse code input is disabled on the clip plus. Couldn't the setting still be available although there can't be a hotkey for switching the mode? 10.06.51 Join z180 [0] (~chatzilla@ip-109-42-182-219.web.vodafone.de) 10.07.00 Quit bitcraft (Remote host closed the connection) 10.34.34 Join PaulFertser [0] (paul@paulfertser.info) 10.35.55 # Hi there :) I have an old cool sansa e200 here and i wonder what's the reason behind forcing to load OF when plugged in with usb inserted now that there's nice and stable support for USB in Rockbox itself? 10.42.07 # But nowadays it looks like if i flash the latest bootloader to it i'll have it waiting for me to unplug it from the usb because it would automatically get into bootloader usb mode, right? 10.43.28 # with an up-to-date bootloader you aren't forced and if you want to charge only you can hold any button while plugging USB which should be described in our manual 10.43.44 # As far as I know, the bootloader should boot to rockbox, unless you hold a special button 10.44.44 # I'm reading http://git.rockbox.org/?p=rockbox.git;a=blob;f=bootloader/main-pp.c;h=28aee9cf90b6138415e484ccdf401b9b4166dc2c;hb=HEAD 10.45.39 Part Carcino ("I'm a happy Miranda IM user! Get it here: http://miranda-im.org") 10.46.35 # bertrik: indeed, but what if i turn the device on while having it plugged into a pc? 10.48.05 Join ender` [0] (~ender@foo.eternallybored.org) 10.48.16 # I don't know, sounds like a pretty hard to reach state anyway, since the device turns on by itself the moment you plug it in AFAIK 10.48.18 # I guess i'd get dropped to "bootloader usb mode" but what'd be the benefit of that for me comparing to loading full rockbox? 10.48.49 # bertrik: it turns on, the bootloader starts, sees usb connection present, tries negotiating with the host, succeeds, stucks in bootloader usb mode. 10.48.54 # bertrik: if i'm reading the sources correctly. 10.51.16 Join pamaury [0] (~quassel@vit94-1-82-67-248-70.fbx.proxad.net) 10.51.17 Quit pamaury (Changing host) 10.51.17 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 10.51.41 # pixelma: we're apparently talking about different bootloaders, i'm talking about the usual PP one that just enables verbose if any button (except for the hold switch and "left" which loads OF) pressed. 10.52.13 # my e200 boots into Rockbox when usb is plugged in 10.52.22 # and I haven't updated the bootloader since long 10.52.35 # bluebrother: usb charger or usb host? 10.52.41 Join icarusfactor [0] (~factor@74.195.96.67) 10.53.07 # bluebrother: what revision of the bootloader and compile options provide that result? I can't see it in the current code. 10.53.13 Nick icarusfactor is now known as factor (~factor@74.195.96.67) 10.53.52 # usb host. Aka PC 10.54.24 # and that's with v6 bootloader 10.56.08 Join Rower85 [0] (husvagn@v-413-alfarv-90.bitnet.nu) 10.56.24 # bluebrother: sorry, i can't translate that easily into a git hash or svn id... 10.58.53 # well, the bootloader file for e200 on the download server is 5th july 2009 10.59.04 # so it has to be around that date. 10.59.18 # seems there wasn't a tag made (or the tag isn't descriptive enough) 11.03.01 Join othniel [0] (~othniel@75.92.51.2) 11.09.09 # bluebrother: hm, real-life testing with http://download.rockbox.org/bootloader/sandisk-sansa/e200/PP5022.mi4 confirms your observation. 11.12.35 *** Saving seen data "./dancer.seen" 11.13.50 # bluebrother: but if you compare the 5th July date of the said file to http://git.rockbox.org/?p=rockbox.git;a=history;f=bootloader/main-pp.c;h=28aee9cf90b6138415e484ccdf401b9b4166dc2c;hb=HEAD you'll see that there were quite some changes since then. 11.15.04 Quit kadoban_ (Ping timeout: 265 seconds) 11.16.57 # bluebrother: i think http://git.rockbox.org/?p=rockbox.git;a=commitdiff;h=76083359e08c85f28874a7c07e5332fda2a5b503 proofs that nowadays that "bootloader usb mode" is enabled for e200s. But what is the benefit of that? 11.18.38 # <[Saint]> USB when your rockbox image is trashed. 11.19.00 # <[Saint]> errrr...s/image/binary/ 11.19.35 # <[Saint]> It basically allows you an opportunity to mount and fix errors with just the bootloader itself, without having to boot the OF. 11.19.40 # [Saint], why not just boot to the OF in that case? 11.19.48 # <[Saint]> Hassle? 11.20.34 # <[Saint]> iPods have this enabled too...when they could (in theory {afaik}) just boot the OF too. 11.20.49 # I don't see the point of a bootloader USB mode to be honest 11.21.02 # <[Saint]> Many targets have it now. 11.21.11 # just makes the bootloader more complicated 11.21.14 # <[Saint]> Its not entirely useless, but, I agree. 11.30.10 # [Saint]: i do not see any point in having that bootloader usb mode either, OF is supposed to be untrashable anyway, and it's not a hassle to boot it in case of emergency. 11.30.35 # <[Saint]> Its not anything to do with the OF. 11.30.47 # <[Saint]> So, we can disregard that. 11.31.07 # <[Saint]> (fwiw, its also *very* possible to trash the OF) 11.31.34 # [Saint]: but following the official instructions, unlikely, right? 11.32.36 # <[Saint]> Picture this scenario...you plug USB, but, "Oh Noes! my .rockbox folder is entirely f****d/trashed/missing/etc", what do you do? Boot the OF and transfer a new one...well, you could do that, or, it could just mount right then and let you do it in the bootloader. 11.32.54 # [Saint]: i think this bootloader usb mode also complicates charging a flat battery: if one's device is depleted and he plugs it to usb to charge he's getting stuck in the bootloader usb mode and has to rely on rarely used BL charging code instead of the widely tested rockbox charging code, right? 11.32.55 Join TomColler [0] (~thomas@net-93-144-166-3.cust.dsl.teletu.it) 11.33.27 # <[Saint]> the charging code isn't exactly complicated... 11.33.36 Quit stoffel (Ping timeout: 276 seconds) 11.34.17 # [Saint]: and yet it has to take that 100/500mA limits into account, program the PMU chip properly etc, plenty of opportunities to get it wrong. 11.35.02 # <[Saint]> And plenty of people to review it, and some exceptionally smart individuals that coded it in the first place. 11.35.16 # <[Saint]> The time to raise issues about this was *many* moons ago ;) 11.35.19 Join leavittx [0] (~leavittx@89.221.199.187) 11.36.23 # <[Saint]> As long as the bootloader still fits where its supposed to in space constrained targets, I really don't see the problem if it lights up an LED array to spell out "help! I'm broken, fix me!" 11.36.53 # [Saint]: http://www.rockbox.org/tracker/task/12615 basically confirms my concerns 11.37.58 # <[Saint]> That has pretty much nothing to do with bootloader USB or charging. 11.38.04 # <[Saint]> But rather safe shutdown limit. 11.38.27 # <[Saint]> Its likely the battery is just on its way out too...that's the other possibility. 11.39.22 # [Saint]: i'd appreciate if you explained to me why this issue is not the problem with charging in bootloader usb mode that wouldn't exist if the bootloader usb mode didn't exist. 11.39.58 # <[Saint]> Its an issue with the value (potentially) that is deemed "safe" for a critically low battery. 11.40.20 # <[Saint]> If it is so low that it cannot power the device to a state where it can charge, *that* is the problem. 11.40.47 # <[Saint]> It could also just be a case a a bad battery. 11.40.49 # And yet it can boot OF? 11.41.10 # "Currently rockbox doesn't charge when in bootloader USB mode. The solution is to hold volume down on plug so that it boots to the OF and charge. This should be fixed in the next version of the bootloader." 11.41.29 # <[Saint]> Where does it say he booted the OF? 11.42.13 # That's what pamaury suggested as a workaround for a known issue. 11.43.21 # <[Saint]> He ran down the battery to a level where rockbox decided that it needed to shutdown, if indeed after that it couldn't power itself to a point where it could even get the bootloader to a point where the charging code could take over *that* is the problem, IMO. 11.44.52 Join jae [0] (~jae@dedicated.jaerhard.com) 11.45.37 # <[Saint]> The critical battery limit should allow a full boot, even several. 11.45.50 # <[Saint]> Its not even as though it has a disk to spin up. 11.46.21 # <[Saint]> So that tells me that its either set too low, or the battery is bad in this instance. 11.47.49 Quit z180 (Ping timeout: 244 seconds) 11.47.57 # <[Saint]> Take my iPod 4G with a big clunky old HDD for instance, when Rockbox decides the battery is so low it needs to shut down...its still perfectly capable of powering itself to a point where it can charge itself. This is intentional. 11.47.58 # What if his device was gathering dirt for several months after that, it'd have depleted his battery all right. 11.48.53 # <[Saint]> Well, that would count as neglect, and if you really expected a deep discharged battery to boot anything, you'd be rather unpleasantly surprised. 11.49.08 # <[Saint]> deep discherge == bad :) 11.49.14 # <[Saint]> -e+a 11.50.13 # I've enabled charging in usb mode, I can't remember if jean-louis updated the bootloader image on the wiki 11.50.46 # but we haven't released a new official bootloader yet 11.51.09 # <[Saint]> pamaury: with the flyspray entry above...am I right in thinking that might indicate the safe shutdown limit is too low? 11.51.22 # <[Saint]> (or possibly just a bad battery) 11.52.18 # why too low ? 11.52.31 # <[Saint]> I mean, if its read as written, and it shut down and then couldn't power itself up to get to a point where it could charge itself... 11.53.36 # pamaury: my question is what benefits the bootloader usb mode brings if one is still able to boot OF in case he damaged his .rockbox install while i see potential pitfalls of this mandatory bootloader usb mode e.g. caring about the charging inside the BL itself which shouldn't have been necessary if it booted straight to rockbox. 11.53.40 # <[Saint]> Even HDD targets can spin up the disk for long enough to boot into Rockbox and start charging after a low battery shutdown. 11.53.52 # <[Saint]> So I'm wondering if its set too low in this instance. 11.55.22 # <[Saint]> PaulFertser: Can you explain how one boots into Rockbox with a damaged binary? 11.55.30 # <[Saint]> (or did you word that incorrectly?) 11.56.11 # [Saint]: the PMU chip is supposed to have sensible defaults so it should be able to boot the BL and then the BL should be able to boot Rockbox which should enable charging all right. 11.56.36 # The problem is when you're stuck in BL with disabled (or wrong) charging settings. 11.56.45 # And that issue is not a single report of a similar problem. 11.56.58 # <[Saint]> but, you said "in case he damaged his .rockbox install" *and* "caring about the charging inside the BL itself which shouldn't have been necessary if it booted straight to rockbox" 11.57.07 # <[Saint]> those two don't gel together. 11.57.42 # <[Saint]> If the .rockbox binary is damaged, it *won't* boot into Rockbox...that's the point. 11.58.01 # [Saint]: then the user would press the key to boot into OF which has charging code all right. 11.58.38 # <[Saint]> Or...it could charge via the bootloader, and use bootloader USB, and not require any intervention (much cleaner) 11.58.58 # Much more code, much more chances of something being broken. 11.59.20 # And this kind of brokenness was actually observed on several devices. 11.59.40 # <[Saint]> I go back to my scenario of "as long as it does what its supposed to, and fits where it should, I don't care if it whilstles dixie while doin git" 12.00.09 # my opinion on that is that's it not a real problem. The fuze+ is in development, people should now that such things could happen. This problem in particular is fixed if one uses the latest bootloader image I think. The bl usb mode is useful for development and allows you to completely bypass the OF even when the rockbox binary is broken 12.00.22 # <[Saint]> and that, yes. 12.00.37 # <[Saint]> Things break, its a risk you take installing experimental firmware. 12.01.02 # you can't really break your device anyway 12.03.43 # <[Saint]> iiuc, the Fuze+ isn't even classed as "unusable" yet, is it? 12.03.58 # I think it is 12.04.07 # err no, it's unstable 12.04.10 # pamaury: ok, i see, thanks for the clarificiation. Anyway the released binaries for e200 are so old that the bootloader usb mode is not enabled there :) folks in here tried to convince me that's the current official behaviour while i was looking at the code and clearly seeing it's not :) 12.04.14 # <[Saint]> If it is, the main page needs updating. 12.04.20 # <[Saint]> pamaury: ^ 12.04.30 Quit Keripo (Quit: Leaving.) 12.04.51 # [Saint]: it's marked as unstable on the main page! 12.05.13 # * [Saint] cleans his glasses. 12.06.21 # There is one thing on which you are right: recovering from this situation is a bit tricky and we should probably have some tool to do it on linux *and* windows (in RbUtil for example) 12.06.22 # <[Saint]> PaulFertser: whether intentional or not, the "official" behaviour is that of what is released, I would say. 12.07.06 # PaulFertser: are you running bootloader v9 from the wiki page ? 12.07.08 # [Saint]: 2009 is not relevant. 12.07.32 # pamaury: no, those folks are running http://download.rockbox.org/bootloader/sandisk-sansa/e200/PP5022.mi4 12.07.46 # And it's the same file mentioned in sansapatcher sources btw 12.08.02 # <[Saint]> Why so? If that's the last bootloader released, that's "the official bootloader"..whether its intentional or not. 12.08.04 # * pamaury missed the point where we switched to e200 12.09.27 # <[Saint]> As did I, actually. I was linked to concerns regarding Fuze+ 12.09.51 # [Saint]: i'm using rockbox long before there was any "stable" release at all. 12.10.00 Join Topy [0] (~Topy44@f049239039.adsl.alicedsl.de) 12.10.01 # 14:04 < PaulFertser> pamaury: ok, i see, thanks for the clarificiation. Anyway the released binaries for e200 are so old 12.10.58 # <[Saint]> PaulFertser> [Saint]: i'm using rockbox long before there was any "stable" release at all. <-- I really don't see where you're going with that. 12.11.28 # [Saint]: that for me what's relevant is the code i see in gitweb, not some abitrary releases. 12.11.46 # <[Saint]> That's a poor assumption, then. 12.12.03 # Ok :) 12.12.08 # <[Saint]> the current code might be reverted at any point and NEVER make it into ANY release. 12.12.24 # 3.11 tagged 12.12.36 # \o/ 12.12.55 # [Saint]: the thing is that when i was asking about the behaviour i gave a link to the _current_ code revision, so it was clear i'm talking about git HEAD and not about some release back from 2009. 12.12.55 Quit T44 (Ping timeout: 246 seconds) 12.13.49 # <[Saint]> PaulFertser: And if you're trying to lodge bugs against user built and/or unreleased binaries...there's a problem. 12.15.00 # <[Saint]> Releases are expected to work, sure. Current code may be broken in many wide and varied fashions. 12.15.04 # the behaviour of bootloader is the one of released binaries, it has always been because bootloader are delicate pieces of code, HEAD is basically irrelevant for bootloaders 12.15.16 # huh? 12.15.34 # I'd expect HEAD to represent the state-of-the-art code, to be used for the next release 12.15.49 # even for bootloaders 12.16.09 # Commit e46382a in rockbox by 03Alex Parker: Bump builds.pm so that Rockbox Utility notices 3.11 12.16.16 # <[Saint]> But we know that isn't the case, as, things break. Intentional or not. 12.16.31 # at some point we don't change the bootloaders, most targets did not get a bootloader release in a while, perhaps the current code would not even work 12.16.43 # then why the hell do we commit stuff for bootloaders? 12.16.48 # [Saint]: i gave the git hash i'm talking about early into the talk anyway, so i can't understand what's wrong with asking specific questions mentioning specific code revision. 12.16.52 # But if a new bootloader releße was needed, it would come from HEAD 12.17.02 # If that is currently broken, irt would be fixed first 12.17.12 Join lebellium [0] (~chatzilla@g225187034.adsl.alicedsl.de) 12.17.39 # <[Saint]> PaulFertser: I think you successfully managed to confuse at least two of us :) 12.17.54 # [Saint]: practice makes perfect :) 12.18.12 # And i had enough of practice in confusing people :) 12.19.44 # <[Saint]> Nano2g is actually a pretty good example of "sometimes HEAD gets so messed up we just can't use it" 12.20.48 # BTW, i'm still amazed by the incredible awesomeness of the Rockbox project, that's clearly the only portable player firmware worth using and i can imagine how much work (including a rather complicated RE) was put into it. The team is really great. 12.23.10 # <[Saint]> 10 years of effort from literally hundreds of individuals, and a metric butt-load of revisions. It really is quite impressive, indeed. 12.35.33 # AlexP: did you see any Swedes around yet? 12.35.39 # gevaerts: No 12.35.58 # Is build_info on the website updated from builds.pm once a day? 12.36.03 # At 03:00? 12.36.30 # I don't know. Usually they give it a push on release day I think 12.37.06 # Yeah, must do 12.37.19 # Otherwise it'd always take a day to be picked up 12.38.00 # I think that that is all that is needed 12.38.33 # I don't think the files have been moved in place yet 12.38.38 # ah 12.39.47 # Bagder: When you get a moment, could you let us know so we can finish off the release stuff? 12.48.20 Join Horscht [0] (~Horscht@xbmc/user/horscht) 12.52.46 # e46382a build result: 1 errors, 2 warnings (Alex Parker committed) 12.56.01 Join prof_wolfff [0] (~prof_wolf@81.61.201.173.dyn.user.ono.com) 12.56.49 # I'm going to go ahead and say that wasn't me 12.57.03 # Also, 36 minutes is an impressive build time :) 12.57.25 # <[Saint]> ...unless its for one target ;) 13.07.15 Join Zagor [242] (~bjst@rockbox/developer/Zagor) 13.09.47 # AlexP: I don't really have much time today, maybe Zagor can help though 13.11.02 # OK, thanks 13.11.22 # I think it just needs files moving, build_info given a push and www made live 13.12.36 *** Saving seen data "./dancer.seen" 13.13.17 # I'm on it 13.14.23 # Thanks muchly 13.16.43 # does anyone use RTL languages? 13.18.14 # soo... one thing tha was used at MS for translation testing was they had a "language" which was the english string with some random unidode chars appended.. can anyone with scriptfo make that happen for us? :) 13.22.44 Join petur [0] (~petur@rockbox/developer/petur) 13.23.19 # <[Saint]> JdGordon: I believe I know why you referenced RTL langs, and I'm looking at the code now. There are indeed bit where the RTL text can get messed up in some cabbie versions. 13.23.25 # <[Saint]> *bits 13.23.25 # petur: hey, the histogram in the rec screen was commited right? where is it supposed to be displayed? 13.23.52 # below the peakmeters iirc 13.24.06 # is it disabled in the sim then? 13.24.43 # don't think so, but it might only be enabled for iriver 13.25.07 Nick guest829385 is now known as user845847 (~aoeu@112.166.15.141) 13.25.51 # <[Saint]> JdGordon: as pretty much the only person I know I can bug that's even vaguely aware of how RTL stuffs should be handled...does it make sense to flip the fill direction of the progress bar also? 13.26.04 # <[Saint]> (as well as elapsed/remaining time) 13.26.17 # I think so 13.26.23 # <[Saint]> Right, thanks. 13.26.42 Quit Poodlemastah (Quit: ZNC - http://znc.in) 13.26.44 # 3.11 is now out 13.27.04 # <[Saint]> I'll make this (sane RTL handling) tomorrows task, I feel like ass at present. 13.27.59 # it's pretty annoying the theme needs to handle it :/ 13.28.34 Quit user845847 (Read error: Connection reset by peer) 13.28.50 Join guest829385 [0] (~aoeu@112.166.15.141) 13.29.05 Join Poodlemastah [0] (~Poodlemas@h-152-191.a218.priv.bahnhof.se) 13.29.23 # JdGordon: we could just flip the whole framebuffer ;) 13.30.20 # Zagor: Great, thanks 13.30.52 # <[Saint]> JdGordon: there's not actually a lot of fuss in doing so. 13.31.06 # <[Saint]> Its actually really easy to handle, its just easily forgotten it seems. 13.31.11 Quit fyrestorm (Read error: Connection reset by peer) 13.31.15 # [Saint]: yes there is, there is maybe 1 theme which handles it correctly :) 13.31.26 Join dfkt [0] (dfkt@unaffiliated/dfkt) 13.31.30 Join fyrestorm [0] (~nnscript@cpe-68-173-235-85.nyc.res.rr.com) 13.31.46 # <[Saint]> if you %ax every textual viewport, its fine, and will "just work". 13.32.15 # <[Saint]> flipping the fill direction of the bar takes a little effort, but, its stilla one line thing. 13.32.38 Topic "3.11 released! | Please read before speaking: http://www.rockbox.org/wiki/IrcGuidelines | Please direct offtopic/social chat to #rockbox-community | This channel is logged at http://www.rockbox.org/irc" by ChanServ (ChanServ@services.) 13.33.39 Nick guest829385 is now known as timccc (~aoeu@112.166.15.141) 13.33.54 # <[Saint]> If you mix %ax and %aL/R, "fun things" happen...but, that's not really much of an isue, as it should be reasonable obvious that each tag cancels part of the other out. 13.34.46 # <[Saint]> pretty much every viewport that isn't centrally symetrical should be "%ax'd", and alignment tags "just work". 13.35.24 # <[Saint]> (for both LTR and RTL langs) 13.35.56 # all of that could happen in the code 13.36.02 Quit Poodlemastah (Quit: ZNC - http://znc.in) 13.36.12 # it owuld be nice to know if a particular string shold be RtL'd or not 13.36.20 # <[Saint]> But it doesn't...and never has...and I need something to do tomorrow ;) 13.36.41 # hum looks like theme downloading with rockbox utility has not been fixed, it tells me "network error: request aborted" 13.37.09 Join Poodlemastah [0] (~Poodlemas@h-152-191.a218.priv.bahnhof.se) 13.37.51 # <[Saint]> lebellium: It wasn't ever announced that it should indeed be fixed, was it? 13.37.59 Join anewuser [0] (~anewuser@186.93.175.208) 13.37.59 Quit anewuser (Changing host) 13.37.59 Join anewuser [0] (~anewuser@unaffiliated/anewuser) 13.38.01 # <[Saint]> Or did you expect the release to make it work? 13.38.17 # yes I thought that would work along with the new 3.11 13.38.43 # <[Saint]> afaik, its "git hashtag weirdness" and it only hits some targets, and only for some revisions. 13.38.43 # No, it is unrelated sadly 13.38.55 # Or not directly anyway 13.38.58 # Maybe :) 13.39.03 # <[Saint]> Its not a case of something being obviously broken that just wasn't fixed because people are lazy. 13.39.11 # <[Saint]> its "weird sh*tTM" ;) 13.39.44 # ah ok 13.40.14 # <[Saint]> AlexP: Oh? Hmmm...that's both interesting and not nice. 13.40.30 # <[Saint]> Is there a new direction to look in, or is it back to shoulder shrugging? 13.41.04 # I suspect I've misunderstood, so just ignore me :) 13.41.29 Nick timccc is now known as user485763 (~aoeu@112.166.15.141) 13.42.07 Quit user485763 (Quit: Leaving.) 13.43.59 Join user485763 [0] (~aoeu@112.166.15.141) 13.47.41 # Has anyone tested a regular install of 3.11 yet? 13.54.05 # <[Saint]> It'd be nice if RBUtil could report successful installation stats. 13.54.26 # <[Saint]> (and failed installations also) 13.54.37 # OK, it seems to work on my F60 13.54.41 # themes still fail though 13.54.55 # GET /rbutilqt.php?target=gigabeatfx&release=3.11&revision=&rbutilver=1.2.13& HTTP/1.1 13.55.01 # HTTP/1.0 500 Internal Server Error 13.56.05 # rasher: ping 13.57.37 # rasher: maybe we could try to remove the revision_syntax_changed handling from rbutilqt.php? 13.57.58 # Hm, no, that's not it 13.59.44 # Someone who knows php needs to actually look on the server what's going on 14.00.26 # bluebrother: maybe rockbox utility could distinguish 500 Internal Server Error from not being able to connect to show a better error message? 14.05.57 Join diginet [0] (~diginet@ppp-70-246-16-75.dsl.hstntx.swbell.net) 14.06.32 Quit [Saint] (Quit: Quit) 14.13.24 Join [Saint] [0] (~Saint]@unaffiliated/saint/x-8516940) 14.17.16 # gevaerts: yes it could :) 14.17.44 # congratulation on new release :) 14.24.39 Join T44 [0] (~Topy44@f049239039.adsl.alicedsl.de) 14.24.39 Quit Topy (Read error: Connection reset by peer) 14.26.30 Quit T44 (Read error: Connection reset by peer) 14.26.36 Join Topy [0] (~Topy44@f049239039.adsl.alicedsl.de) 14.29.41 # kugel: ping 14.31.03 # so apparently RTL is broken in the android builds 14.31.24 Join T44 [0] (~Topy44@f048111169.adsl.alicedsl.de) 14.32.46 # I have no idea why it shold be broken on some targets and not others though 14.34.19 Quit Topy (Ping timeout: 246 seconds) 14.34.56 Join domonoky [0] (~Domonoky@rockbox/developer/domonoky) 14.37.18 Join Cthulhux [0] (cthulhux@piratenpartei/ni/tux) 14.41.04 Part Zagor 14.44.30 # Just upgraded my clip+ from 3.9 to 3.11 14.44.35 # seems to work fine so far 14.47.17 # [Saint]: yeah, i tinhk the proper thing to do is just magically make skins work with rtl without the extra tags 14.49.20 # can't we just flip the frame buffer? :D 14.49.36 # sorry 14.50.25 Join benedikt93 [0] (~benedikt9@unaffiliated/benedikt93) 14.56.07 Quit Horscht (Quit: Verlassend) 14.56.45 Join lebellium_ [0] (~chatzilla@g229116188.adsl.alicedsl.de) 14.58.07 Quit lebellium (Ping timeout: 246 seconds) 14.58.10 Nick lebellium_ is now known as lebellium (~chatzilla@g229116188.adsl.alicedsl.de) 15.12.39 *** Saving seen data "./dancer.seen" 15.12.54 Join Zx432 [0] (~kiborg@89-212-91-200.static.t-2.net) 15.13.01 # Hi 15.13.55 # I am trying to instal rockbox on ubuntu to update my iRiver H100 and I can't get it to install. 15.15.01 # you can't install Rockbox on Ubuntu 15.15.16 # Really? 15.15.19 # you can use Ubuntu to install Rockbox to your player, but that's something different 15.15.34 # :) Semantics 15.15.53 # well, the difference is important here. 15.16.00 # OK. 15.16.16 # so what exactly are you trying to do? Are you trying to run Rockbox Utility? 15.17.45 # I downloaded the file, Rockbox Utility so that I could upgrade my iRiver 15.17.48 # H100 15.18.20 # But now I have the file and don't know what to do. 15.18.30 # and where do you have problems? Did you manage to run Rockbox Utility? 15.18.41 # "the file" meaning Rockbox Utility or what? 15.20.38 # yes the file Rockbox Utility the 64 bit version 15.21.01 # so you have the archive downloaded. Have you already extracted it? 15.21.20 # yes 15.21.29 # have you managed to start it? 15.22.37 # no 15.22.42 # that is the problem 15.22.55 # and what exactly is the problem here? 15.23.05 # it won't start 15.23.16 # well, is your machine actually 64bit? 15.23.22 # yes 15.23.33 # and your Ubuntu installation as well? 15.23.44 # yes it is all 64 bit 15.23.59 # ok, do you get any error message when trying to start it? 15.27.54 # error: Could not show "/media/Počasn/Programi/rockb...-v1.2.13-64bit/RockboxUtility" The program that supports the executable files is not installed. (I translated this from slovenian so the actuall english version might be a bit different.= 15.28.23 # huh? Never heard of such an error message 15.28.37 # are you trying to run it from a terminal or via a file browser? 15.28.59 Quit petur (Quit: Bye) 15.29.16 # Via file browser 15.29.16 Join petur [0] (~petur@rockbox/developer/petur) 15.30.26 # what version of Ubuntu? 15.30.51 # 11.10 15.30.56 Quit petur (Client Quit) 15.31.09 Join petur [0] (~petur@rockbox/developer/petur) 15.31.45 # maybe it's related to this? https://wiki.ubuntu.com/SecurityTeam/Policies#Execute-Permission_Bit_Required 15.31.54 # can you check if the executable bit is set on the file? 15.32.49 # (and https://wiki.ubuntu.com/Security/ExecutableBit) 15.34.34 # Ok so it is clearly not marked as executable. 15.34.41 # wow 15.34.51 # so yet another stupid Ubuntu thing :( 15.36.41 # Yep 15.37.09 # the file in the archive definitely has the x bit set. Just checked ... 15.37.47 # Well I know what is the problem now. Ubuntu sets it automatically as untrustworthy. 15.38.42 # seems they are trying hard to copy Windows when it comes to treating the user as stupid m( 15.40.24 # :) 15.40.43 # Now jujst to figure how to force change. 15.41.54 # Zx432: do you really mean tar drops the executable bit when you untar something? 15.42.33 # yes http://ma65p.wordpress.com/2008/08/04/how-to-make-a-file-executable-in-ubuntu/ 15.42.47 # If you check point 3 15.43.05 # The red thing should be as on pisture 15.43.10 # *picture 15.43.53 # If I try to tick it it unticks itserf instantly. And I am logged as admin. 15.44.41 # that's impossible -- Ubuntu doesn't allow users to log in as root 15.45.04 # instead it requires you to use sudo all the time 15.45.40 # (well, unless you're familiar enough with U untu to change that, but then you shouldn't have stumbled across this behaviour :) 15.46.05 Join y4n [0] (~y4n@unaffiliated/y4ndexx) 15.46.10 # have you actually extracted the binary or are you trying to run it directly from the archive? 15.47.51 # it is extracted. I am certain of that. 15.48.09 # ok 15.54.21 Quit perrikwp (Ping timeout: 260 seconds) 15.56.43 # hmm. Just tried that in a VM with said Ubuntu version, can't reproduce Archive Manager removing the x bit 15.57.21 # it looks totally broken though. Seems some font stuff is missing. Or Qt is using the wrong fonts. 15.57.56 # So it doesn't work for you? 15.58.07 # it does work. 15.58.12 # oh 15.58.14 # ok 15.58.32 # the fonts are rendered horribly, but that doesn't make it non functional 15.59.03 # ok 15.59.42 # I guess I need to check the Qt used for building the binary against Ubuntu :( 15.59.52 # the binary works fine on Debian 16.01.57 # have you stored Rockbox Utility on some other drive? Like the player itself? 16.04.01 # It is on one of my HDDs that are part of the system. They are not on the player. 16.04.41 # ok. Storing it on some FAT32 formatted drive would have been a possible explanation. 16.05.24 # * bluebrother is out of ideas 16.05.44 # you can of course always compile it yourself. Or use a Windows machine. Or install manually. 16.08.05 # None are fat32 16.08.27 # I stored it on the same one that the OS is using. 16.08.46 Join Strife89TX [0] (~upirc@207.144.201.128) 16.10.57 # I was trying to download 3.11 build from the Manual installer page just now, but all of the Firmware links ... aren't. 16.21.22 # aren't what? 16.21.36 # Aren't links. 16.21.47 # they are here 16.22.00 # Ah. :/ 16.22.04 # You are looking at http://www.rockbox.org/download/byhand.cgi right? 16.22.10 Quit petur (Quit: Bye) 16.22.25 Join petur [0] (~petur@rockbox/developer/petur) 16.22.31 # Then Blazer is proably not rendering the page right. 16.22.47 # It is fine here in firefox 16.22.54 # AlexP: I believe so. 16.23.56 # (Blazer is the stock browser on the Palm TX.) 16.28.18 # Oh well, I'll try with my laptop next chance I get. 16.29.44 Quit Strife89TX (Quit: Leaving) 16.36.42 Quit leavittx (Ping timeout: 265 seconds) 16.37.51 Join leavittx [0] (~leavittx@89.221.199.187) 16.38.54 Join XavierGr [0] (~xavier@rockbox/staff/XavierGr) 16.39.03 Quit leavittx (Read error: Connection reset by peer) 16.51.44 Join bitcraft [0] (~bitcraft@173-20-20-92.client.mchsi.com) 17.03.00 Join n1s [0] (~n1s@nl118-175-223.student.uu.se) 17.03.00 Quit n1s (Changing host) 17.03.00 Join n1s [0] (~n1s@rockbox/developer/n1s) 17.03.26 Join CaptainKewl [0] (captainkew@207-237-110-248.c3-0.nyr-ubr2.nyr.ny.cable.rcn.com) 17.11.54 # hmm, my fuze just hung while copying a file to the sd card via usb 17.12.42 *** Saving seen data "./dancer.seen" 17.13.08 Quit bitcraft (Remote host closed the connection) 17.14.50 # retrying it paniced 17.26.04 # dmesg shows a couple of "usb 1-1.1: device descriptor read/64, error -110" and then i get an i/o error message and the player hangs in the usb screen 17.27.47 # * n1s moves the card to a c200 and tries again 17.35.14 # in the c200 it works fine 17.36.30 Quit Zx432 (Quit: Leaving.) 18.15.53 Quit nosa-j (Ping timeout: 252 seconds) 18.16.02 Join nosa-j [0] (~m00k@adsl-74-235-42-147.clt.bellsouth.net) 18.28.05 Join perrikwp [0] (~quassel@173-102-239-122.pools.spcsdns.net) 18.43.09 Join bitcraft [0] (~bitcraft@173-20-20-92.client.mchsi.com) 18.45.25 # what in hells name 18.45.45 Quit curtism (Quit: Live Long and Prosper) 18.46.13 # my music folder isnt showing up on a E280 V1 when using the file browser 18.46.48 # Mir: what is your Show FIles setting set to? 18.47.14 Quit robin0800 (Quit: Leaving) 18.51.14 Join Shovelware [0] (~Shovelwar@host-68-169-137-65.MIDOLT2.epbfi.com) 19.10.35 Quit Shovelware (Quit: ChatZilla 0.9.88.1 [Firefox 11.0/20120312181643]) 19.12.40 Quit bitcraft (Remote host closed the connection) 19.12.43 *** Saving seen data "./dancer.seen" 19.15.07 Join bitcraft [0] (~bitcraft@173-20-20-92.client.mchsi.com) 19.35.03 Quit n1s (Quit: Ex-Chat) 19.35.25 # my show files setting set to? 19.36.14 # all 19.36.39 # and when i said folder i meant /music/ 19.36.46 # not the stuff thats in it 19.37.04 # how can i see the stuff thats in the folder if i cant see the folder 19.37.50 # interesting 19.38.00 # after charging it its now working :| 19.38.12 # maybe the all setting didnt sink in 19.50.06 Part TomColler 20.00.21 Join kadoban_ [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 20.07.15 Join enthdegree [0] (~BitchX@unaffiliated/enthdegree) 20.09.44 Quit bitcraft (Remote host closed the connection) 20.10.09 Join bitcraft [0] (~bitcraft@173-20-20-92.client.mchsi.com) 20.10.33 Join bitcraft_ [0] (~bitcraft@173-20-20-92.client.mchsi.com) 20.10.34 Quit bitcraft (Read error: Connection reset by peer) 20.23.37 Quit perrikwp (Ping timeout: 246 seconds) 21.11.37 Quit scorche (Read error: Connection reset by peer) 21.12.47 *** Saving seen data "./dancer.seen" 21.19.22 Join scorche [0] (~scorche@rockbox/administrator/scorche) 21.21.39 Quit enthdegree (Ping timeout: 265 seconds) 21.23.53 Quit bitcraft_ (Remote host closed the connection) 21.29.17 Join bitcraft [0] (~bitcraft@173-20-20-92.client.mchsi.com) 21.30.17 Join wodz_ [0] (~wodz@89-76-160-35.dynamic.chello.pl) 21.52.33 Join enthdegree [0] (~BitchX@unaffiliated/enthdegree) 21.54.26 Quit enthdegree (Read error: Connection reset by peer) 21.54.54 Quit bitcraft (Remote host closed the connection) 21.57.00 Quit bluebrother (Disconnected by services) 21.57.07 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 21.57.26 Join Horscht [0] (~Horscht@xbmc/user/horscht) 21.59.06 Join bitcraft [0] (~bitcraft@173-20-20-92.client.mchsi.com) 21.59.31 Quit fs-bluebot (Ping timeout: 246 seconds) 22.00.47 Join fs-bluebot [0] (~fs-bluebo@g231123094.adsl.alicedsl.de) 22.02.53 Join z180 [0] (~chatzilla@ip-109-45-181-41.web.vodafone.de) 22.05.37 Quit bitcraft (Remote host closed the connection) 22.23.33 Quit y4n (Quit: PÆNTS ØLF!) 22.28.32 Join saratoga_ [0] (980329c4@gateway/web/freenode/ip.152.3.41.196) 22.29.18 Quit benedikt93 (Quit: Bye ;)) 22.32.43 Part jordan` 22.38.26 # OK, theme installation from rockbox utility should be working again 22.38.55 # you should tell that guy on the forums who was interested about it 22.39.09 # gevaerts: Good work! 22.39.12 # What was up? 22.40.10 # Unbalanced parens 22.40.20 # ah 22.40.30 # My php is good enough to find those given a log that tells me which line is wrong :) 22.40.41 # handy :) 22.41.41 # works for me now too 22.41.50 # saratoga_: done 22.41.58 # Unless there's more than one of those 22.42.03 Quit wodz_ (Quit: Leaving) 22.42.33 # no i think that was it 22.42.37 Quit pamaury (Ping timeout: 260 seconds) 22.44.03 Join pamaury [0] (~quassel@vit94-1-82-67-248-70.fbx.proxad.net) 22.44.03 Quit pamaury (Changing host) 22.44.03 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 22.45.38 # meh, getting weird database issues again 22.51.55 # did Lorenz092 end up getting GIT access yet? 22.54.01 # I ask him now 22.55.45 Quit Rower85 (Quit: Hmmm...) 22.56.06 # saratoga_: no he did not have time for that yet, he's quite busy atm 22.56.27 # hmm ok 22.57.59 Quit Horscht (Quit: Verlassend) 22.58.10 # he should probably get it anyway though since so much of that port is his work and he continues to maintain it 23.04.32 # yes sure he wants the FM radio to be included, finally. As soon as he's done with his university work, he'll work again on the port :à 23.09.24 # I have a Cowon C2, not supported by Rockbox so far. Can anyone compare improvements on other Cowon-players? 23.11.46 # D2 is supported so I have hopes. 23.12.13 # gevaerts: nice. Wasn't aware you have access to that box :) 23.12.48 # bluebrother: I suddenly remembered that scorche gave me access a while ago to look at a preformance issue 23.12.49 *** Saving seen data "./dancer.seen" 23.13.13 # bluebrother: don't interpret this to mean that I understand php! 23.13.35 # Zambezi: I'm not sure what you mean 23.14.10 Quit pamaury (Read error: Operation timed out) 23.15.35 # gevaerts: at least it's working again, which is a good thing 23.15.51 Join pamaury [0] (~quassel@vit94-1-82-67-248-70.fbx.proxad.net) 23.15.51 Quit pamaury (Changing host) 23.15.51 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 23.16.20 # Can anyone compare improvments on Cowon stock firmware and Rockbox on Rockbox-supported model? Cause somethings on stock firmware on Cowon C2 is quite annoying. Like locked screen and you can still adjust the volume. 23.17.04 # gevaerts: Better? 23.19.44 # Zambezi: yes. I can't really answer, I'm not too familiar with the D2. I do know several people have asked to allow changing volume while on hold though :) Glad to see not everyone agrees that that's a good idea 23.22.16 # gevaerts: The touch screen is responding abit odd, but I bought it mostly because my old broke and I wanted one with SD-card. Sony had a nice without the SD-card and without FLAC-support. No go. 23.22.29 # What, there's been progress on the D2? 23.22.54 # FOAD: not really, no 23.23.27 # i committed charging detection for the D2+ a while back based on a patch someone sent in 23.23.28 # Shucks. 23.23.35 # i think thats the only work on the d2 in recent years 23.23.36 # FOAD: We spoke about the stock firmware. 23.23.50 # Yeah well I just got triggered by "D2". :P 23.24.17 # FOAD: I assume you got one your self. 23.24.18 # What's a good modern player that I can enjoy Rockbox on? One that's nothing to do with *pple. 23.24.21 # I do. 23.25.02 # FOAD: I like the way it handle firmware upgrade. Just transfer, restart. 23.25.48 # All I ever did with it was get the D2+ firmware on it really. 23.26.02 # Zambezi: nearly all semi-recent players do that 23.26.36 # FOAD: What's better with D2+ compare to D2 firmware? 23.26.42 # I got it because it seemed there was some decent work on the Rockbox D2 front being done at the time. But it never panned out really. 23.26.58 # Not much really. I never felt much of a difference at all. :) 23.28.09 # FOAD: I don't like the connection. A proper USB-mini/micro/whatever would be much better. 23.28.38 # I'm beat today. I really need to go to bed. Night peeps! 23.29.08 # Zambezi: huh? My D2's got a USB mini port. 23.29.14 # Bye Zambezi. 23.36.01 Quit petur (Ping timeout: 250 seconds) 23.39.54 Join petur [0] (~petur@rockbox/developer/petur)