--- Log for 07.05.111 Server: leguin.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 1 day and 1 hour ago 00.03.52 # OK, I've successfully split FS#11931 up into a bug-fixing and a feature patch. Would you think the changes need further discussion (on the mailing list), or are they trivial enough to commit now? 00.04.49 # wow, the usb code seems to actually work :-o 00.05.29 # pamaury: I'm curious whether this fixes my USB failures 00.06.01 # it needs more testing, I've only checked control transfers for now 00.09.16 # what do people think about writing the resume info on critical battery shutdown on flash devices? 00.10.03 # hum, usb serial doesn't work, I need to work this out tomorrow 00.10.04 Quit Buschel (Ping timeout: 240 seconds) 00.11.19 # saratoga: good idea. but wouldn't you think "critical" would also allow one last write even on a hard drive? 00.11.49 # sideral: usually the disk wouldn't be spun up, so trying to spin it up would kill hte battery 00.12.04 # theres a pretty big dip in battery voltage when you spin up a disk 00.12.09 # not really an issue on flash though 00.12.40 # although i don't want to enable something that could risk corrupting the FTL or something 00.12.57 # depends on how you define "critical". It could be dying hardware modulo one final disk access 00.13.04 # I was about to say the same 00.16.44 # No one senior enough around to give advice on whether FS#11931 can be committed without going to the mailing list? Oh well 00.18.00 # perhaps wait until tomorrow, it's quite late right now 00.19.11 # OK. Although I only ever seem to have time when it's either late or early :) 00.27.26 Quit {phoenix} (Remote host closed the connection) 00.28.20 # Hey folks. I was hoping someone could take a look at http://www.rockbox.org/tracker/task/11522 and let me know what needs to be done to get it committed. 00.31.37 Quit TheLemonMan (Quit: Ex-Chat) 00.32.49 # Chronon: You need to find a developer with an interest in the Game of Life plugin. Perhaps whoever write / committed it in the first place? 00.33.03 # s/write/wrote/ 00.34.37 Quit liar (Ping timeout: 258 seconds) 00.35.31 Quit sideral (Quit: Leaving.) 00.36.19 # Well, it's been hacked into its current state by several people. 00.36.36 # I'll see who has been involved in the several commits related to it. Thanks 00.42.06 Quit factor (Ping timeout: 260 seconds) 00.44.13 Quit dfkt (Quit: -= SysReset 2.55=- Sic gorgiamus allos subjectatos nunc.) 00.44.22 Join factor [0] (~factor@r74-195-188-223.msk1cmtc01.mskgok.ok.dh.suddenlink.net) 00.45.15 *** Saving seen data "./dancer.seen" 00.47.57 Quit pamaury (Remote host closed the connection) 00.48.33 Join alexb_1 [0] (~alex_b@pool-173-75-198-101.phlapa.east.verizon.net) 00.52.14 # Does anybody know if the Clip+ automatically reboots into the OF when USB is inserted? The manual says it does but pixelma expressed some doubts about this. 00.52.51 # I'm happy to write a patch if the manual needs changing. 00.54.35 # Chronon: it does not 00.54.42 # Chronon: you don't have SVN access? 00.54.48 # but if you turn it off, it will boot the OF if you plug it in 00.54.57 # saratoga: I don't have commit access. 00.55.15 Quit ender` (Quit: When one person suffers from a delusion it is called insanity. When many people suffer from a delusion it is called religion. -- Robert Pirsig) 00.55.51 # how odd 00.56.43 # At least I am not aware about gaining commit access. 00.58.25 Quit GeekShadow (Quit: The cake is a lie !) 01.00.06 Quit DerPapst1 (Quit: Leaving.) 01.19.14 # hi all, I want to see track info (length, time) on wps. I just upgraded sansa c250 to 3.8.1 and I can't make the way it was in old version. what theme /settings do I need to change? thanks. 01.21.07 Part alexb_1 ("Leaving") 01.25.33 Quit bertrik (Ping timeout: 240 seconds) 01.34.38 Join Topy [0] (~Topy44@f049000044.adsl.alicedsl.de) 01.37.21 Quit robin0800 (Quit: Leaving) 01.38.31 Quit T44 (Ping timeout: 240 seconds) 01.58.38 Quit u42p (Quit: Leaving) 02.13.41 Quit Jerom1 (Quit: Leaving.) 02.32.07 Quit jordan` (Ping timeout: 240 seconds) 02.32.32 Quit stripwax (Read error: Connection reset by peer) 02.37.56 Join jordan` [0] (~gromit@ALagny-154-1-6-54.w83-112.abo.wanadoo.fr) 02.39.35 Quit jhMikeS (Ping timeout: 258 seconds) 02.40.04 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) 02.43.58 Join alexb_1 [0] (~alex_b@pool-173-75-198-101.phlapa.east.verizon.net) 02.45.19 *** Saving seen data "./dancer.seen" 02.47.38 Quit alexb_1 (Client Quit) 02.49.47 Join timccc [0] (~lisa@112.166.15.141) 03.03.26 # Since I don't have commit access for SVN I posted a patch for the manual here: http://www.rockbox.org/tracker/task/12102 03.05.17 Join GodEater [0] (~bibble@5ada16ea.bb.sky.com) 03.05.17 Quit GodEater (Changing host) 03.05.17 Join GodEater [0] (~bibble@rockbox/staff/GodEater) 03.08.07 Quit GodEater_ (Ping timeout: 248 seconds) 03.08.57 Join JesusFreak316 [0] (~JesusFrea@pool-173-65-110-53.tampfl.fios.verizon.net) 03.14.49 Quit simonlnu (Quit: bbl) 03.22.03 Quit [Saint] (Disconnected by services) 03.22.05 Join S_a_i_n_t [0] (~st.lasciv@124-197-3-117.callplus.net.nz) 03.40.43 Join simonlnu [0] (simon@unaffiliated/simonrvn) 03.42.51 Nick timccc is now known as fdfhhjvbn (~lisa@112.166.15.141) 03.46.59 Quit soap (Remote host closed the connection) 03.47.51 Join soap [0] (~soap@cpe-76-181-78-156.columbus.res.rr.com) 03.47.51 Quit soap (Changing host) 03.47.51 Join soap [0] (~soap@rockbox/staff/soap) 03.54.00 Quit fxb (Ping timeout: 260 seconds) 03.59.25 Join mmmfuze [0] (~ae310785@giant.haxx.se) 04.04.18 # could anyone possibly apply a patch to the latest build of rb for the fuze v2 for me? I tried to understand cygwin and all, but im confused 04.06.14 # don't use cygwin 04.06.57 # i strongly recommend using a VM instead 04.06.59 # vmware? 04.07.24 # alright, thanks 04.07.28 Quit mmmfuze (Quit: CGI:IRC) 04.08.18 Quit amiconn (Disconnected by services) 04.08.19 Join amiconn_ [0] (quassel@rockbox/developer/amiconn) 04.08.20 Quit pixelma (Disconnected by services) 04.08.22 Join pixelma_ [0] (quassel@rockbox/staff/pixelma) 04.08.24 Nick pixelma_ is now known as pixelma (quassel@rockbox/staff/pixelma) 04.08.37 Nick amiconn_ is now known as amiconn (quassel@rockbox/developer/amiconn) 04.25.07 Join kugel [0] (~kugel@e178058129.adsl.alicedsl.de) 04.25.07 Quit kugel (Changing host) 04.25.07 Join kugel [0] (~kugel@rockbox/developer/kugel) 04.28.33 Quit kugelp (Ping timeout: 260 seconds) 04.29.36 Quit mshathlonxp () 04.45.21 *** Saving seen data "./dancer.seen" 04.58.31 Quit TheSeven (Disconnected by services) 04.58.40 Join [7] [0] (~TheSeven@rockbox/developer/TheSeven) 05.04.14 Join gartral [0] (~CR-48@unaffiliated/gartral) 05.06.20 # on my e250 temporary idle poweroff settings in some apps is ignored if the device is charging, first noticed with the clock app (hold center when plugging in) can someone please confirm before i submit a bur report? 05.11.15 Join Rob2223 [0] (~Miranda@p4FFF1774.dip.t-dialin.net) 05.15.12 Quit Rob2222 (Ping timeout: 260 seconds) 05.27.32 Join krazykit [0] (~krazykit@99-126-205-52.lightspeed.cicril.sbcglobal.net) 05.44.36 Quit Chronon (Remote host closed the connection) 05.47.30 Join Chronon [0] (~quassel@c-71-236-138-156.hsd1.or.comcast.net) 05.53.53 # gartral: thats not a bug 05.54.15 # saratoga: how so? 05.54.18 # it intended so you can charge the player, see the manual 05.54.34 # unless you mean it turned off ? 05.54.52 # actually reading your question its possible i don't understand what your observed 05.57.37 # saratoga: i think you misunderstand.. my backlight keeps turning off.. even though the backlight setting in clock.app is set too always on. this only happens when the device is plugged in.. when unplugged the temporary setting works as it (in my mind) should 05.58.10 # ah, idle poweroff refers to something else 05.58.26 # i had said idle poweroff by mistake, i meant backlight 05.58.44 # so the clock plugin ignores its own setting if its running off AC power? 05.59.01 # yes 05.59.29 # (i guess that AC != USB+Center button?) 06.01.09 # same thing 06.01.23 # technically USB charge mode is just using the PC as an AC adapter 06.02.10 Quit L-Strife89 (Ping timeout: 240 seconds) 06.03.59 # but anyway, yes I would file a bug report for that 06.04.04 # its likely no one has noticed 06.15.42 Join Horschti [0] (~Horscht@xbmc/user/horscht) 06.18.06 Join Strife89 [0] (~Strife89@168.16.226.82) 06.19.10 Quit Horscht (Ping timeout: 248 seconds) 06.29.42 Quit JesusFreak316 (Read error: Connection reset by peer) 06.30.48 Join JesusFreak316 [0] (~JesusFrea@pool-173-65-110-53.tampfl.fios.verizon.net) 06.36.46 # crap, i can't remember my username! and the tracker doesn't have a "forgot username, enter email" oprion 06.39.02 # saratoga: who handles the admin stuff for the website? 06.39.35 # bunch of swedes who are asleep, check back during the day 06.39.48 # grr 06.40.08 # in the meantime, feel like testing the clock.app and confirming my findings? 06.45.22 *** Saving seen data "./dancer.seen" 07.40.43 Join merbanan [0] (~banan@c-94-255-221-202.cust.bredband2.com) 07.42.49 Join Judas_PhD [0] (~kevin@misterfluffy.dsl.xmission.com) 07.44.13 Part Judas_PhD 08.08.27 Quit gartral (Ping timeout: 276 seconds) 08.30.58 Join bmbl [0] (~bmbl@unaffiliated/bmbl) 08.45.26 *** Saving seen data "./dancer.seen" 08.49.24 Join gartral [0] (~CR-48@unaffiliated/gartral) 09.04.04 # n1s: (logs) - Your patch on FS#12098 does indeed fix the issue on my targets, I was curious as it's probably not something that pops up very often as the fail case revolves around some very specific circumstances (rolo'ing a new build and disconnecting at the exact time a battery level will be voiced). 09.16.19 Join stoffel [0] (~quassel@p57B4A179.dip.t-dialin.net) 09.19.24 Quit gartral (Ping timeout: 264 seconds) 09.26.08 Join Buschel [0] (~chatzilla@p54A39F7B.dip.t-dialin.net) 09.27.24 Quit niekie (Read error: Connection reset by peer) 09.28.59 Quit sasquatch (Quit: WeeChat 0.3.2) 09.29.12 Join gartral [0] (~CR-48@unaffiliated/gartral) 09.29.20 Join niekie [0] (~niek@CAcert/Assurer/niekie) 09.29.23 Join sasquatch [0] (~username@p4FF2D8EE.dip.t-dialin.net) 09.34.45 Quit JesusFreak316 (Remote host closed the connection) 09.41.29 Quit gartral (Remote host closed the connection) 09.43.55 Quit Buschel (Quit: ChatZilla 0.9.86.1 [Firefox 3.6.17/20110420140830]) 09.44.01 Join n1s [0] (~quassel@rockbox/developer/n1s) 09.49.51 Quit jhMikeS (Ping timeout: 260 seconds) 09.52.01 Join gartral [0] (~CR-48@unaffiliated/gartral) 10.03.02 Join bertrik [0] (~bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 10.03.02 Quit bertrik (Changing host) 10.03.02 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 10.07.19 # S_a_i_n_t: cool, thanks for testing 10.08.52 # New commit by 03nls (r29828): Fix FS#12098 by ignoring battery update events in the yesno screen. 10.10.33 Join ender` [0] (krneki@foo.eternallybored.org) 10.12.34 # r29828 build result: All green 10.12.45 Nick S_a_i_n_t is now known as [Saint] (~st.lasciv@124-197-3-117.callplus.net.nz) 10.13.00 Join Judas_PhD [0] (~kevin@misterfluffy.dsl.xmission.com) 10.13.41 # <[Saint]> No worries, I like testing interesting fail cases. ;) 10.14.04 Join shai [0] (~Shai@l192-117-110-233.cable.actcom.net.il) 10.14.10 # * bertrik wonders about i2c drivers 10.14.44 # <[Saint]> Proof that it's incredibly hard to provide for each scenario during initial development, and that it can sometimes take years for a bug to show. 10.14.51 # it looks like we're driving SDA hard, while it should be driven as open-drain, in this particular driver I'm looking at 10.15.43 # [Saint]: yeah 10.17.35 Join GeekShadow [0] (~Antoine@reactos/tester/GeekShadow) 10.25.48 Join stripwax [0] (~Miranda@87-194-34-169.bethere.co.uk) 10.27.42 # hmm. Does the logo have an explicit license attached? 10.27.44 Quit mystica555 (Ping timeout: 240 seconds) 10.31.26 # bluebrother: It's on our wiki, so does that make it Gnu FDL? 10.33.05 # Llorean: not sure. Since it's part of Rockbox I'd say it's at least some GNU license. Might be nice to have that stated explicitly somewhere, just in case. 10.34.48 # Yes, definitely would be nice to have an explicit license. 10.37.07 # I'd like to move all svg logo sources to docs/logo. Any concerns left about this? 10.37.10 Join JoshuaChang [0] (~joshuacha@222.70.133.12) 10.42.17 Quit stoffel (Ping timeout: 276 seconds) 10.43.45 # does the arrays, variables in the dsp.c allways occupy the memory/sram? 10.45.00 # JoshuaChang: the global ones do, the others are on stack or dynamically allocated 10.45.29 *** Saving seen data "./dancer.seen" 10.46.31 # global ones? 10.46.33 # for example, does the crossfeed's delayline array always occupy the memory? 10.49.01 # yes, it's allocated statically and is a global var 10.49.13 # the crossfeed_data struct 10.49.31 # see line 205 10.52.49 # yes, i've found it, does it mean, if the struct in the dsp.c is instanced, it'll always occupy the memory? 10.54.00 # yes, iff it's statically allocated 10.54.11 # this is nothing special for dsp 10.54.33 # (it would be tricky to allocate dsp data structures on the stack) 10.55.33 # well, i think i should put all my delayline in system memory, for cowon d2's sram is too small to be used 10.56.11 # memory allocation can be target dependent (e.g. "put it in iram on this device but dram on that device") etc 10.57.13 # #ifdef ? 10.59.00 # yes 10.59.51 # ranmachan, do you remember which i2c controller is used in the AMS players? 11.00.17 Join robin0800 [0] (~robin0800@cpc3-brig8-0-0-cust703.3-3.cable.virginmedia.com) 11.00.32 # is there exist device have 200k+ iram? gigabeat s? 11.00.58 # the beast doesn't use iram at all 11.01.08 # it has only 4k IIRC 11.01.59 Join DerPapst [0] (~Alexander@p579168CA.dip.t-dialin.net) 11.02.00 # well, it's so fast that doesn't depend on iram at all 11.02.06 # i think the highest I've seen is 192k 11.02.14 Join gartral_ [0] (~CR-48@unaffiliated/gartral) 11.02.26 # of course that's "192k total" not "192k spare".. 11.03.15 # in cowon d2, if i put my plugin's variables, points in the system memory, it slowdown about 12% 11.03.21 Quit gartral (Ping timeout: 260 seconds) 11.04.10 # my plugins's delayline eats about 130k memory 11.04.24 # different SoC's have very different memory performance, the recent arms seem to be quite fast with regular dram 11.05.32 # you are not going to find many targets with 130k iram for plugins, also keep in mind that if you want to run your plugin at the same time as a codec you cannot use iram 11.07.48 # yes, i divide my plugin's variable into 2 parts, the huge delayline in system memory, while the small variables, points in iram 11.09.43 Quit Galois (Read error: Operation timed out) 11.24.31 Quit robin0800 (Read error: Connection reset by peer) 11.25.13 Join mystica555 [0] (~mike@71-33-152-71.hlrn.qwest.net) 11.25.14 Join robin0800 [0] (~robin0800@genld-217-240.t-mobile.co.uk) 11.27.36 Join benedikt93 [0] (~benedikt9@unaffiliated/benedikt93) 11.30.52 Quit robin0800 (Ping timeout: 252 seconds) 11.32.28 # what does the plugin do? 11.35.00 # bertrik: IIRC something we didn't have a datasheet for 11.35.08 Join Buschel [0] (~chatzilla@p54B67F6A.dip.t-dialin.net) 11.36.19 # ranmachan, but it looks like you added a lot of defines to the driver, so I guessed you got it from somewhere rather than reverse engineering 11.37.37 # bertrik: The linux patch just calls it the "AS352X AFE I2C driver" 11.38.09 # ah, ok. Maybe I'll add a comment to the source of the information. 11.38.15 Quit gartral_ (Ping timeout: 240 seconds) 11.38.17 Join gartral [0] (~CR-48@unaffiliated/gartral) 11.41.47 Quit user890104 (Read error: Connection reset by peer) 11.41.55 Join user890104 [0] (~Venci@6bez10.info) 11.45.19 Join pamaury [0] (~quassel@vit94-1-82-67-248-70.fbx.proxad.net) 11.45.19 Quit pamaury (Changing host) 11.45.19 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 11.47.12 Join robin0800 [0] (~robin0800@cpc3-brig8-0-0-cust703.3-3.cable.virginmedia.com) 11.55.24 Join TheLemonMan [0] (~lem0n@151.62.179.8) 11.56.08 Quit shai (Quit: Leaving) 11.57.17 Join stripwax_ [0] (~Miranda@87-194-34-169.bethere.co.uk) 11.57.35 Quit stripwax_ (Client Quit) 12.01.47 Join fxb [0] (~felixbrun@h230n1c1o1037.bredband.skanova.com) 12.09.38 Quit gartral (Read error: Connection reset by peer) 12.10.45 Join shai [0] (~Shai@l192-117-110-233.cable.actcom.net.il) 12.11.12 Join gartral [0] (~CR-48@unaffiliated/gartral) 12.37.37 Quit gartral (Remote host closed the connection) 12.38.06 Quit Buschel (Quit: ChatZilla 0.9.86.1 [Firefox 3.6.17/20110420140830]) 12.45.32 *** Saving seen data "./dancer.seen" 12.50.00 Quit bluebrother (Quit: leaving) 12.51.33 Join stoffel [0] (~quassel@p57B4A179.dip.t-dialin.net) 12.52.59 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 12.55.25 Quit DerPapst (Ping timeout: 240 seconds) 12.56.13 Join DerPapst [0] (~Alexander@p57954702.dip.t-dialin.net) 13.00.49 Join Jerom1 [0] (~jerome@95.171.148.84) 13.08.14 Join Galois [0] (djao@efnet-math.org) 13.28.34 Quit FoH (Ping timeout: 260 seconds) 13.35.38 Quit bertrik (Read error: Operation timed out) 13.36.34 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 14.04.45 Join gartral [0] (~CR-48@unaffiliated/gartral) 14.38.47 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 14.45.34 *** Saving seen data "./dancer.seen" 14.48.22 Join u42p [0] (~v35b@d155107.adsl.hansenet.de) 14.52.07 Join Buschel [0] (~chatzilla@p54B67F6A.dip.t-dialin.net) 15.01.21 Quit linuxguy3 (Read error: Connection reset by peer) 15.09.27 Quit Buschel (Ping timeout: 258 seconds) 15.10.42 Quit krazykit (Ping timeout: 276 seconds) 15.11.33 Quit mystica555 (Read error: Operation timed out) 15.12.19 Join krazykit [0] (~krazykit@99-126-205-52.lightspeed.cicril.sbcglobal.net) 15.12.36 Join LambdaCalculus37 [0] (~rmenes@rockbox/staff/LambdaCalculus37) 15.15.51 Quit bertrik (Ping timeout: 260 seconds) 15.25.07 Quit stoffel (Remote host closed the connection) 15.34.41 Quit LambdaCalculus37 (Quit: Fwump) 15.35.22 Quit stripwax (Read error: Connection reset by peer) 15.37.53 Join dfkt [0] (~dfkt@unaffiliated/dfkt) 15.41.42 Join mshathlonxp [0] (~roxor@5e037b20.bb.sky.com) 15.48.42 Join Luca_S [0] (~57064fe6@giant.haxx.se) 15.49.33 # android 1.5/1.6 is now next to irrelevant, I'm going to bump the minimum version to 2.1 15.49.34 # i found a screenless e250 today! 15.51.12 # kugel: what's the benefit of increasing the minimum version? 15.51.52 # dropping compatibility code 15.51.55 # bluebrother: ease of mantinence.. and a smaller apk 15.52.10 # supporting older version increases the size of the apk? 15.52.18 # it increases code size 15.52.38 # it increases both code size and apk size 15.53.01 # By how much? 15.53.08 # though, the apk comes out bytes/kilobytes smaller 15.53.09 Quit fxb () 15.53.19 # negligable 15.53.23 # meh, I actually want api level 8, which is 2.2 but that's too early 15.53.49 # gartral: so why did you bring this up? 15.53.51 # so, I'll post-pone that 15.54.03 # given that we have ~3.5MiB libmisc.so on my player I think that's not much of concern 15.54.16 # at least with MOST things, no clue.. it all depends how many legacy functions the rockbox code really uses 15.54.31 # can rockbox use asm optimize in android-app mode? 15.54.52 # i mean, the existing asm code 15.55.02 # JoshuaChang: not sure.. i dont think so.. 15.55.07 # kugel: I'm not that sure that 1.5/1.6 is irrelevant these days. Some cheap android tablets still use those I think 15.55.12 # JoshuaChang: sure 15.55.19 # * gartral is wrong 15.55.24 # as usual... 15.55.35 # gevaerts: both together have like 5% share 15.55.35 # gevaerts: i'm not always wrong! 15.55.43 # ?? 15.55.51 # google regularly puts statistics up 15.55.52 # can or can not? 15.55.59 # JoshuaChang: you can 15.56.22 # kugel: statistics of what exactly? Google Market? 15.56.28 # yea 15.56.47 # That ignores the entire non-google-branded world then 15.56.57 # i don't know why, but some c based function runs out of my expected while the asm code is ok 15.56.58 # still, why cut out 5% of potential users? If we have a technical benefit that's big enough, ok. 15.58.39 # http://hardware.slashdot.org/story/11/05/07/1215246/Micro-SD-Card-Slot-Abused-As-VGA-Port 15.58.56 Join Buschel [0] (~chatzilla@p54A39F98.dip.t-dialin.net) 15.59.06 # oh god, i have dreams about jewels on my 22" monitor driven by rockbox on a fuze :D 15.59.30 # bluebrother: writing this compatibility code causes headache because you need to find new methods via reflection 16.00.54 Quit Luca_S (Quit: CGI:IRC (EOF)) 16.04.00 # * [Saint] *really* doesn't like the idea of bumping the API version on RaaA on principle 16.04.15 # <[Saint]> while we're at it...lets drop charcell support...that's old too. 16.04.30 # <[Saint]> if we can support older devices...why the fuck not? 16.04.56 # <[Saint]> err "bliimin' heck" rather. 16.06.00 # <[Saint]> if it's not *essential*, and it's just "it's annoying, it gives me a headache"...then, I have a really hard time supporting the descision. 16.06.21 # <[Saint]> ...step aside and let someone that doesn't get a headache write it then. 16.09.53 Join mystica555 [0] (~mike@c-174-51-141-174.hsd1.co.comcast.net) 16.15.27 # [Saint]: people stop working on stuff that causes headache 16.15.44 # <[Saint]> ...ok. 16.16.07 # <[Saint]> I'm sure if it came to that, it's your descision, and someone will take your place. 16.16.12 # <[Saint]> You're not obligated. 16.16.43 # the more complicated it is to support legacy devices, the less work will be done. it just frightens off contributors 16.16.57 # <[Saint]> taking away support for devices because "I can't be bothered" is a very poor choice. 16.17.10 # <[Saint]> someone most likely *can* be bothered if it's not going to be you. 16.17.42 # that's not a given 16.17.56 # kugel: how integrated is all of this? I mean, does keeping 1.5/1.6 hold back new stuff? Can 1.5/1.6 maybe be separated out entirely (possibly up to the point that it's a separate target)? 16.18.02 # <[Saint]> So be it, but I still see bumping the API as a poor choice. 16.18.34 # <[Saint]> there's apparently no technical reason to do so apart from "a few bytes to kilobytes". 16.18.49 # <[Saint]> ...so, yeah, I see it as a poor idea from a snap descision. 16.18.57 # [Saint]: I got it 16.19.03 # <[Saint]> if you have too little time, don't spread yourself so thin. 16.19.14 # [Saint]: you're not helping here 16.20.25 # are there much people bothering about the Android at all? 16.20.26 # [Saint]: you're underestimating the scaring off new contributors aspect 16.20.58 # * bluebrother would prefer seeing the existing bugs on Android getting fixed first 16.21.26 Quit gartral (Remote host closed the connection) 16.21.31 Quit Horschti (Quit: Verlassend) 16.22.10 # <[Saint]> bluebrother: by my understanding it's limited to the handful of us that roll our own .apks, and amount of people that grab the premade builds of old off the forums. 16.22.22 # <[Saint]> perhaps kugel has dl stats, I don't know. 16.23.14 # [Saint]: well, I was thinking developer-wise. With the current bugs you can't expect users to like Rockbox on Android at all. 16.24.41 Quit bluebrother (Quit: leaving) 16.28.06 Quit pamaury (Remote host closed the connection) 16.29.23 Join pamaury [0] (~quassel@vit94-1-82-67-248-70.fbx.proxad.net) 16.29.23 Quit pamaury (Changing host) 16.29.23 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 16.29.43 # gevaerts: the compatibility code is under Helper/, so a bit of Makefile magic for conditional compilation should work 16.29.59 # but anyway, I won't change anything since I'm actually after api level 8 16.31.13 Quit Jerom1 (Quit: Leaving.) 16.32.05 # I'd say we should try to find a way to both allow people to concentrate on new stuff without too much annoyances and allow other people to maintain the old stuff 16.32.51 Join kugel_ [0] (~kugel@rockbox/developer/kugel) 16.32.51 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 16.34.44 Quit kugel_ (Read error: Connection reset by peer) 16.36.27 Join Horscht [0] (~Horscht@p5DD577CA.dip.t-dialin.net) 16.36.27 Quit Horscht (Changing host) 16.36.27 Join Horscht [0] (~Horscht@xbmc/user/horscht) 16.36.42 Quit kugel (Ping timeout: 276 seconds) 16.37.49 Join kugel [0] (~kugel@rockbox/developer/kugel) 16.43.44 # :( 16.45.36 *** Saving seen data "./dancer.seen" 16.46.05 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 16.46.45 # looks like I can't fix that bug while keeping 2.1 compatibility 16.48.15 # <[Saint]> "that bug"? 16.51.21 Quit mshathlonxp () 16.51.33 # playback controls not being passed to us 16.51.40 # i.e. from the lockscreen on CM 16.52.20 # <[Saint]> How many non-CM ROMs actually have that? 16.52.43 # htc sense, but it doesn't work 16.54.02 # I don't recall having that in Sense. 16.54.22 # it only shows if there music player is running IIRC 16.54.27 # Ah. 16.54.35 # I haven't used theirs. Heh. 16.55.16 # perhaps only in newer versions too 16.55.26 # Is the bug going to affect other things. For example, if someone installs a generic playback control widget? Are they basically system events, or something custom? 16.55.34 # * Llorean was running a quite new version. 16.56.54 # yea 16.57.15 # whatever sends plain multimedia button keys, e.g. wired remotes 16.57.34 # jumping into the fire... I wouldnt be completly against a seperate 1.5/6 build target if it meant existing bugs could be fixed more easily 16.57.34 # So right now we don't work with remotes/headset, but fixing that would fix those as well? 16.57.58 # outright dropping 1.5/6 would be shit though 16.58.45 Quit n1s (Remote host closed the connection) 16.58.56 # fixing this bug requires in interface to be present in the framework :'( 17.00.58 # and regarding the line height talk... yes, there is no way I would be happy with it being commited without being properly configurable 17.01.16 # that would be revert-without-discussion worthy 17.02.29 # not supporting special buttons is one thing ... playback stopping is something that I'd really call a bug 17.03.22 # bluebrother: I thought you're onto fixing that? 17.03.39 # * JdGordon had my phone reboot after trying to start playback from the widgt tonight 17.05.10 # <[Saint]> I considered bluebrother's patch to be a workaround...perhaps I was wrong though. 17.05.56 # <[Saint]> JdGordon: that's happened to me a few times too. 17.06.20 # <[Saint]> I also get the odd (2 or 3 a week) complete random reboots when the RaaA service is running. 17.07.06 # i get that too but i dont think rockbox is to blame 17.07.21 # kugel: well, I figured that increasing the buffer fixes it for me. But (a) I'm not a Java developer at all and (b) there seems to be something else involved 17.07.21 # general random shutoffs, nfi what cuases it 17.07.38 # and yes, I consider my patch a workaround. 17.08.09 # unless someone tells me that this is the way to go :) 17.08.27 Join fml [0] (~chatzilla@p5DF3BF14.dip.t-dialin.net) 17.09.12 # Hello. The local store has two Sansa C240 players (1 GB). I think it's the v1 players. Anybody interested? 17.09.13 Quit dfkt (Read error: Connection reset by peer) 17.09.18 Join dfkt_ [0] (dfkt@chello062178002170.1.11.univie.teleweb.at) 17.09.22 Quit dfkt_ (Changing host) 17.09.22 Join dfkt_ [0] (dfkt@unaffiliated/dfkt) 17.14.36 # hmm. Should I update Rockbox Utility to 1.2.10 to fix a single bug or should I make it 1.2.9.1? Though the latter is somewhat stupid, and those numbers are arbitrary anyway 17.15.25 # * JdGordon still wishes he could come up with a workable way to make the lists completly themeable, line heights shouldnt need to be the same for all items in the list 17.15.34 # s/heights/looks/ 17.15.49 # <[Saint]> do the version numbers actually coincide with anything in particular? Or is that what you mean by them being arbitrary? 17.16.13 # 3 numbers in the version is enough for anybody! 17.16.23 # <[Saint]> I mean, there's no "+.1 for minor fixes, +1.0 for "big" fixes rules? 17.16.52 # <[Saint]> It just needs to be versioned so people know what "new" is really no? ;) 17.17.43 # there's not really any rule 17.18.31 # basically I'd like to get Rockbox Utility 1.3 once I got around reworking the UI. Hopefully I'll manage to look into that around DevCon so people can comment on the new UI 17.19.01 # and for 1.2 ... well, there is no rule if we just increase the (current) 9 on every new version or do it in any other way. 17.19.37 # but the problem with false positives on update check with 1.2.9-1 is some kind of a problem. Hence the plan for a new version. 17.20.59 # a 1.2.9.1 could instead be release for Windows only. OTOH there's a small fix that affects all platforms, so a new version doesn't hurt either. 17.22.13 Join dfkt [0] (dfkt@unaffiliated/dfkt) 17.22.24 Join wodz [0] (~wodz@87-206-240-131.dynamic.chello.pl) 17.22.52 # \o/ getting the interface via reflection works 17.24.04 # :< reflection is EVIL! 17.24.42 Quit bertrik (Ping timeout: 240 seconds) 17.25.02 # gah, I spent 2 days looking why sd card doesn't mount and found out that its FAT16 and I assumed that 2GB card should be FAT32 :/ 17.25.24 # <[Saint]> ..ouch 17.25.36 Quit dfkt_ (Ping timeout: 240 seconds) 17.26.46 # so rockchip sd driver reached the point where it passes storage_init() and disk_mount_all(). 17.29.20 # nice 17.30.21 # I am mistaken or rockbox doesn't have a generic sd driver ? 17.30.42 # JdGordon: it is, but there's no way unless we drop support 2.1 and earlier 17.32.25 Join bertrik [0] (~bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 17.32.25 Quit bertrik (Changing host) 17.32.25 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 17.32.44 # wodz: nice to hear that :) 17.34.26 # pamaury: doesn't have one, true 17.37.04 Quit bertrik (Ping timeout: 240 seconds) 17.39.15 # New commit by 03bluebrother (r29829): Rockbox Utility: Add some more cases to version check test. 17.40.38 Join efyx [0] (~efyx@lap34-1-82-225-185-146.fbx.proxad.net) 17.41.45 # bluebrother: I vote for 1.2.10 17.42.31 # r29829 build result: All green 17.42.32 Quit Judas_PhD (Quit: This is a quitting message) 17.43.35 # kugel: I'd prefer that myself -- it's really just a number :) 17.44.20 # hmm. FS#10904 says a the patch has been updated but I can't see anything different to the original one. Except that it's not done from svn anymore. Gnah. 17.44.31 Join Judas_PhD [0] (~kevin@misterfluffy.dsl.xmission.com) 17.45.23 # I realize I don't actually need reflection, it's enough that the components are in the framework at compile time. the class loader will handle the lack at runtime with exceptions 17.48.25 Quit cjcopi (Remote host closed the connection) 17.49.22 Quit Judas_PhD (Client Quit) 17.49.39 Join bertrik [0] (~bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 17.49.39 Quit bertrik (Changing host) 17.49.39 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 17.52.36 # bluebrother: you have a 2.1 device? 17.52.40 # or [Saint] ? 17.52.51 # or, pixelma ? 17.52.51 # <[Saint]> I do. 17.52.55 # kugel: no, I'm on 2.2 17.53.50 # [Saint]: can you test a build for me? 17.53.59 # the emulator crashes when playing music 17.55.22 # <[Saint]> not right this second, but if you put up a link, sure. 17.55.32 # <[Saint]> just let me know what I need to test. 17.55.47 # New commit by 03bluebrother (r29830): SAPI voice creating: add slovak to languages. ... 17.55.50 # compiling right now 17.55.55 # just test if it plays music 17.56.00 Join Stummi [0] (~Stummi@rockbox/developer/Stummi) 17.58.36 # r29830 build result: All green 17.59.15 # [Saint]: http://www.alice-dsl.net/simonemartitz/rockbox/rockbox.apk 18.08.02 Quit JoshuaChang (Quit: ChatZilla 0.9.86.1 [Firefox 4.0.2pre/20110429182132]) 18.08.11 Quit Chronon (Remote host closed the connection) 18.11.32 # \o/ I can read files from SD in bootloader 18.11.57 Quit rdd () 18.12.17 # nice 18.12.33 # still no idea what made the sd card suddenly go into TRAN state? 18.12.39 # no 18.12.47 Join Chronon [0] (~quassel@c-71-236-138-156.hsd1.or.comcast.net) 18.13.15 # the fact is that SELECTING the card and checking for TRAN immediately after that fails always 18.13.50 # and SELECT->TRAN takes ages 18.14.04 # 5s timeout is barely sufficient 18.14.51 # wow 18.17.55 # I found out schematics for reference design of rk2706 based player. Now I understand why I couldn't find out how to read PLAY key - it is impossible while USB is plugged :-) 18.20.23 Quit mystica555 (Read error: Operation timed out) 18.20.32 # is the play key wired to some usb pin ? 18.21.28 Join Luca_S [0] (~57064fe6@giant.haxx.se) 18.21.32 # no 18.22.33 Quit bertrik (Read error: No route to host) 18.26.28 Join bertrik [0] (~bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 18.26.28 Quit bertrik (Changing host) 18.26.28 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 18.33.05 Join MethoS [0] (~clemens@134.102.106.250) 18.33.09 Quit wodz (Quit: Leaving) 18.33.32 Nick MethoS is now known as Guest49786 (~clemens@134.102.106.250) 18.34.44 Join mshathlonxp [0] (~roxor@5e037b20.bb.sky.com) 18.35.40 Quit Guest49786 (Remote host closed the connection) 18.45.38 *** Saving seen data "./dancer.seen" 18.53.01 Join rdd [0] (~rdd@c83-250-52-16.bredband.comhem.se) 18.56.27 Quit robin0800 (Quit: Leaving) 19.03.07 Join smk [0] (~smk@14.97.157.160) 19.04.15 Quit avacore (Ping timeout: 240 seconds) 19.05.07 Join avacore [0] (~avacore@1008ds1-rdo.0.fullrate.dk) 19.07.29 Quit Stummi (Quit: Bye!) 19.08.21 # hi Buschel , i got the new code. malloc usage has been reduced dramatically (if using FAAD_STATIC_ALLOC). so i don't think much work is remaining on that front.. wat do u suggest i do? 19.14.57 Part smk ("Leaving") 19.34.24 Join smk [0] (~smk@115.118.146.171) 19.35.05 Quit bmbl (Quit: Verlassend) 19.40.15 Join jhMikeS [0] (~jethead71@adsl-99-60-42-175.dsl.sfldmi.sbcglobal.net) 19.40.16 Quit jhMikeS (Changing host) 19.40.16 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) 19.44.26 Join mystica555 [0] (~mike@71-33-152-71.hlrn.qwest.net) 19.46.48 # http://www.rockbox.org/tracker/task/12102 <-- Manual - Removes bits mentioning automatic booting of OF upon insertion of USB for AMSv2 players 19.46.54 Join ibhan [0] (~yaaic@109.59.161.53.data.3.dk) 19.49.25 # how can I submit my battery bench logs? 19.49.32 Quit jhMikeS (Ping timeout: 240 seconds) 19.51.31 # aside from just editing the wiki? 20.01.06 Join jhMikeS [0] (~jethead71@adsl-99-60-42-175.dsl.sfldmi.sbcglobal.net) 20.01.06 Quit jhMikeS (Changing host) 20.01.06 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) 20.12.06 Part smk ("Leaving") 20.36.55 Quit tmzt (Read error: Operation timed out) 20.40.34 Quit bluebrother (Quit: leaving) 20.40.53 Join tmzt [0] (~tmzt@adsl-99-164-53-22.dsl.akrnoh.sbcglobal.net) 20.44.51 Join Xerion_ [0] (~xerion@5419A078.cm-5-2c.dynamic.ziggo.nl) 20.45.25 Quit tmzt (Ping timeout: 260 seconds) 20.45.41 *** Saving seen data "./dancer.seen" 20.45.53 Join tmzt [0] (~tmzt@adsl-99-164-53-22.dsl.akrnoh.sbcglobal.net) 20.47.22 Quit Xerion (Ping timeout: 276 seconds) 20.47.23 Nick Xerion_ is now known as Xerion (~xerion@5419A078.cm-5-2c.dynamic.ziggo.nl) 20.50.10 Join bluephone [0] (~yaaic@g224238086.adsl.alicedsl.de) 20.52.55 Quit fml (Quit: ChatZilla 0.9.86.1 [Firefox 4.0.1/20110413222027]) 21.04.16 Quit TheLemonMan (Ping timeout: 276 seconds) 21.04.22 Part ibhan 21.08.17 Join robin0800 [0] (~robin0800@cpc3-brig8-0-0-cust703.3-3.cable.virginmedia.com) 21.10.43 Join Stummi [0] (~Stummi@rockbox/developer/Stummi) 21.15.22 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 21.26.31 Quit Stummi (Quit: Bye!) 21.34.10 Join Stummi [0] (~Stummi@rockbox/developer/Stummi) 21.49.12 # [Saint]: I don't suppose you tested already? 21.50.02 Part u42p ("Leaving") 21.52.05 Quit Xerion (Ping timeout: 240 seconds) 21.54.00 Join smk [0] (~smk@14.97.119.90) 21.55.46 Join Xerion [0] (~xerion@5419809F.cm-5-2c.dynamic.ziggo.nl) 22.12.16 Quit Stummi (Quit: Bye!) 22.12.47 Join Judas_PhD [0] (~kevin@misterfluffy.dsl.xmission.com) 22.17.17 # pamaury: do you think it's possible to give dircache entries an id? I'd like to remove dircache_get_entry_ptr() but maintain fast lookup 22.18.04 # those entries don't move, do they? could their offset from the dircache buffer start be used? 22.21.14 # well, if they moved the direct pointer would be just as fatal 22.24.23 # entries never move, that's why I suggested to partly rewrite dircache to use offsets instead of pointers 22.24.50 # the only changes to dircache are made when deleting or creating files 22.25.02 # (or renaming) 22.27.06 # only exposing the offset would be a good start 22.27.53 # unfortunately the dircache buffer also holds the d_names so you can't treat it easily as an array of entries 22.28.12 # is that a problem ? 22.29.05 Part smk ("Leaving") 22.29.43 # we could replace pointers by opaque types and create one or more functions to access the dircache data instead of exposing the internal structure 22.37.11 # pamaury: only file.c actually uses the internals of the structures. the rest just cache the pointer to pass it back to dircache for filename lookup 22.40.48 # yeah and the usage is quite limited 22.42.08 # alright, so I'm not going to worry further about dircache_get_entry_ptr() :) 22.45.44 *** Saving seen data "./dancer.seen" 22.49.22 Quit Buschel (Quit: ChatZilla 0.9.86.1 [Firefox 3.6.17/20110420140830]) 22.54.08 Quit dfkt (Quit: -= SysReset 2.55=- Sic gorgiamus allos subjectatos nunc.) 22.57.09 Quit soap (Remote host closed the connection) 23.00.05 Quit Judas_PhD (Quit: This is a quitting message) 23.02.05 Join soap [0] (~soap@cpe-76-181-78-156.columbus.res.rr.com) 23.02.05 Quit soap (Changing host) 23.02.05 Join soap [0] (~soap@rockbox/staff/soap) 23.03.55 Quit bluebrother (Disconnected by services) 23.03.56 Join bluebroth3r [0] (~dom@rockbox/developer/bluebrother) 23.06.09 Quit bluephone (Ping timeout: 240 seconds) 23.17.30 # heh, it's pretty obvious that Slasheri wrote both dircache and tagcache 23.17.50 # the memory management is very similar 23.19.14 Quit rdd () 23.19.21 Quit Chronon (Remote host closed the connection) 23.19.56 Quit bertrik (Read error: Connection timed out) 23.20.33 Join bertrik [0] (~bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 23.20.33 Quit bertrik (Changing host) 23.20.33 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 23.21.42 Join Chronon [0] (~quassel@c-71-236-138-156.hsd1.or.comcast.net) 23.22.01 Quit Chronon (Client Quit) 23.33.20 Quit bieber (Remote host closed the connection) 23.34.13 Join bieber [0] (~quassel@162-78.97-97.tampabay.res.rr.com) 23.37.16 Join cjcopi [0] (~craig@charon.craig.copi.org) 23.38.47 Join rdd [0] (~rdd@c83-250-52-16.bredband.comhem.se) 23.39.20 # but dircache was modified and partly rewritten over time 23.39.30 # tagcache...well stayed tagcache ;) 23.49.15 Join froggyman [0] (~seth@unaffiliated/froggyman) 23.54.04 Quit benedikt93 (Quit: The higher the IQ of the individual...The more they enjoy watching a robot drive into a wall at top speed) 23.55.02 Quit bertrik (Read error: Connection timed out) 23.55.35 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 23.56.38 Quit efyx (Remote host closed the connection)