--- Log for 22.07.113 Server: hitchcock.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 1 day and 10 hours ago 00.00.11 # see if I can isolate the problem as much as possible 00.01.44 # good night 00.06.43 Quit bertrik (Remote host closed the connection) 00.18.55 Quit ender` (Quit: "The Einherjar can go toast their foreskins." -- Kevin Hearne: Hunted) 00.26.02 Quit efyx (Quit: Quitte) 00.30.12 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 00.37.29 Quit Scr0mple (Read error: Connection reset by peer) 00.38.07 Join Scromple [0] (~Simon@161.43.73.67) 00.53.57 Quit Strife89 (Quit: Heading home.) 00.59.17 Join dell [0] (~dell@ool-435622d3.dyn.optonline.net) 01.03.31 *** Saving seen data "./dancer.seen" 01.03.49 Join robin0800 [0] (~Robin0800@cpc1-brig15-2-0-cust755.3-3.cable.virginmedia.com) 01.37.48 Quit robin0800 (Read error: Connection reset by peer) 01.40.37 Nick guymann_ is now known as guymann (~c@unaffiliated/guymann) 01.44.38 Quit ZincAlloy (Quit: CGI:IRC (EOF)) 01.53.02 Quit dell (Quit: Ex-Chat) 02.00.56 Quit B4gd3r (Remote host closed the connection) 02.18.27 Join Zarggg [0] (~zarggg@24.229.140.62.res-cmts.sm.ptd.net) 02.57.41 # <[Saint]> pixelma: the touchscreen variable tags do that. 02.57.55 # <[Saint]> variable set/get/etc. 02.58.10 # <[Saint]> its rather amausing if you don't know what's happening. 02.58.15 # <[Saint]> *amusing too. 03.03.32 *** Saving seen data "./dancer.seen" 04.00.21 Join dell [0] (~dell@ool-435622d3.dyn.optonline.net) 04.23.40 Quit Rower (Quit: soer) 04.35.55 Join pixelma_ [0] (pixelma@rockbox/staff/pixelma) 04.35.55 Quit pixelma (Disconnected by services) 04.36.01 Join amiconn_ [0] (quassel@rockbox/developer/amiconn) 04.36.01 Quit amiconn (Disconnected by services) 04.36.04 Nick amiconn_ is now known as amiconn (quassel@rockbox/developer/amiconn) 05.03.35 *** Saving seen data "./dancer.seen" 05.05.40 Quit dell (Ping timeout: 248 seconds) 05.54.12 Quit TheSeven (Disconnected by services) 05.54.24 Join [7] [0] (~quassel@rockbox/developer/TheSeven) 06.03.21 Join tertu [0] (~tertu@65-128-181-81.mpls.qwest.net) 06.07.10 Join pixelma [0] (pixelma@rockbox/staff/pixelma) 06.07.33 Quit [7] (Disconnected by services) 06.07.41 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 06.07.57 Join amiconn_ [0] (amiconn@rockbox/developer/amiconn) 06.07.58 Quit amiconn (Disconnected by services) 06.08.00 Nick amiconn_ is now known as amiconn (amiconn@rockbox/developer/amiconn) 06.08.10 Join Zarggg_ [0] (~zarggg@24.229.140.62.res-cmts.sm.ptd.net) 06.13.02 Quit pixelma_ (*.net *.split) 06.13.02 Quit Zarggg (*.net *.split) 06.17.22 Join FOAD_ [0] (~foad@unaffiliated/foad) 06.18.27 Quit FOAD (*.net *.split) 06.18.28 Nick FOAD_ is now known as FOAD (~foad@unaffiliated/foad) 06.29.06 Join kevku [0] (~kevku@2001:470:27:773:0:feed:c0f:fee) 06.47.25 Quit tertu (Ping timeout: 256 seconds) 06.57.27 Join tertu [0] (~tertu@65-128-181-81.mpls.qwest.net) 07.03.36 *** Saving seen data "./dancer.seen" 07.38.18 Join ungali [0] (~yaaic@184.64.50.234) 07.39.08 Join jlbiasini [0] (~metaphysi@89.136.132.239) 07.39.34 Join olspookishmagus [0] (~pookie@host-84-205-241-1.cpe.syzefxis.ote.gr) 07.48.52 Quit tertu (Ping timeout: 248 seconds) 07.57.40 Join tertu [0] (~tertu@65-128-181-81.mpls.qwest.net) 08.23.54 Join ender` [0] (krneki@foo.eternallybored.org) 08.28.03 Quit jlbiasini (Quit: jlbiasini) 08.34.49 Quit bluebrother (Disconnected by services) 08.34.54 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 08.36.18 Join melmothX [0] (~melmoth@unaffiliated/melmothx) 08.42.05 Quit tertu (Ping timeout: 264 seconds) 08.49.41 Join lorenzo92 [0] (~chatzilla@95.237.111.245) 08.55.21 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 08.58.47 # interesting: the blinking bug occurs when the color of the field in question is NOT the "front color" as defined in the theme file 09.00.37 # it also occurs if the background color is not the one defined in the theme 09.03.40 *** Saving seen data "./dancer.seen" 09.04.27 Join fs-bluebot [0] (~fs-bluebo@g231121115.adsl.alicedsl.de) 09.16.05 Quit Zarggg_ (Quit: Zarggg_) 09.27.46 # * [Saint] very much dislikes hardcoding the background/foreground colors in themes 09.27.58 # <[Saint]> its supposed to be user selectable. 09.29.10 # <[Saint]> most of the time the background color is irrelevant, due to the use of a backdrop, and the foreground color should be able to be set by the user. 09.29.44 # <[Saint]> nice catch, though, copper. 09.29.54 # <[Saint]> JdGordon_: can you think of a reason for this? 09.30.06 # <[Saint]> (no rush, just curious) 09.33.13 # <[Saint]> copper: its certainly not a "fix" for your situation, but, its good practice to not specify fg/bg colors for viewports unless it is absolutely necessary or you're going for a specific effect. 09.33.48 # [Saint]: hmmm, not sure what you mean 09.34.18 # I specify fg and bg colors in the theme file (.cfg) and a foreground color in the wps 09.34.41 # cabbiev2 does that 09.34.50 # <[Saint]> is the fg color in the .wps different from that of the fg color in the .cfg? 09.35.36 # <[Saint]> if its not, best to just set it via the .cfg, then the user can modify it with the color picker. 09.36.48 # <[Saint]> I don't believe its too well known that users can override the theme's fg/bg colors. 09.38.11 # yes it's different 09.38.25 # I set a default color, and for some fields, I use a different color, with %Vf() 09.39.11 # dunno if you followed, but I fixed it by putting the color definition and the metadata on the same line 09.39.31 # %V(140,116,170,20,-)%Vf(666666)%s%ac%?id<%id|Untitled> 09.39.43 # that fixes the bug, for some reason 09.40.05 # <[Saint]> my God that's ugly... 09.40.14 # <[Saint]> But, if it fixes it. 09.40.33 # any clue wtf is going on there? 09.41.22 # <[Saint]> Absolutely none. I have nbo idea why that would make a difference at all, but, there's a few tags that do Very Weird Shit (TM) relative to their placement. 09.41.43 # <[Saint]> This is really JdGordon_'s field of expertise. 09.42.19 # it's strange because I can't reproduce it on the Fuze+ 09.42.21 # ? 09.47.04 # <[Saint]> JdGordon_: rough breakdown of it - http://pastebin.com/pS1XAMTY 09.48.41 # <[Saint]> the tl;dr version is (apparently) specifying a fg color anywhere other than the .cfg apparently causes scrolling text to "blink" if the viewport dimensions are quite specific. 09.48.47 # correction: it also blinks with significantly larger values 09.49.09 # <[Saint]> aha, I missed that, that makes it much easier to catch. 09.51.30 # it also occurs when there is no color definition in the cfg, but the wps color differs from the user set color 09.54.12 # aaa.cfg: http://pastebin.com/raw.php?i=Udm5zudj 09.54.38 # aaa.sbs: http://pastebin.com/raw.php?i=efNVFchu 09.55.02 # aaa.wps: http://pastebin.com/raw.php?i=SivV5uiU 09.55.23 # the blinking is more obvious when the length of the metadata value is only slightly larger 09.55.44 # when the length is significantly larger, it scrolls more or less normally, but when it stops scrolling, it disappears for a second 09.56.12 # the "blinking" effect is really the metadata value disappearing at a higher frequency (because of the lack of scrolling) 09.56.58 # for reference, this happens on my iPod Classic and in the iPod Video sim, but not on the Fuze+ 09.57.07 Quit Scall (Ping timeout: 240 seconds) 10.01.40 Join Scall [0] (~chat@unaffiliated/scall) 10.03.26 # also happens when setting a different background color 10.06.10 # I don't think I can isolate it much more than that 10.17.09 # http://www.rockbox.org/tracker/task/12884 10.18.30 # HTH 11.03.43 *** Saving seen data "./dancer.seen" 11.10.23 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 11.12.55 Join ZincAlloy [0] (~d9eebfd8@www.haxx.se) 11.41.47 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 11.47.11 Quit [Saint] (Remote host closed the connection) 11.48.16 Join [Saint] [0] (~saint@rockbox/user/saint) 11.52.05 Join jlbiasini [0] (~metaphysi@213.233.101.160) 11.52.23 # pamaury: ping 12.25.09 Quit Scall (Ping timeout: 256 seconds) 12.27.42 Join Scall [0] (~chat@unaffiliated/scall) 12.34.57 # jlbiasini: pong 12.35.45 # pamaury: I've done some work to implement basic power function for the f+ touchpad following the RMI protocol 12.36.33 # And I've made some work to implement touchpad desactivation on lock and also having volume keys while being lock 12.37.04 # I tried to do it as clean as I could but I would need your advice on how to mae it cleaner 12.38.54 # It's difficult to get direction because there are basically 3 kind of people: people who have no clue about rb and programming, people who are against such implementation, people that don't care if it's implemented because they don't have a f+ 12.39.47 # with the notable exception of gewearts that give me a hint on how it should be done (see yesterday log) 12.40.04 # ok, is it on gerrit ? 12.41.46 # pamaury: yes, patches are: g#523 g#524 g#525 g526 g#527 12.41.49 # 3Gerrit review #523 at http://gerrit.rockbox.org/r/523 : 3Disable touch device on keyhold for targets that handle it by Jean-Louis Biasini (changes/23/523/3) 12.41.51 # 3Gerrit review #524 at http://gerrit.rockbox.org/r/524 : 3Do not lock hard keys on touchpad device by Jean-Louis Biasini (changes/24/524/2) 12.41.53 # 3Gerrit review #525 at http://gerrit.rockbox.org/r/525 : 3[Fuze+][Touchpad] Improve touchpad power managment by Jean-Louis Biasini (changes/25/525/4) 12.41.55 # 3Gerrit review #526 at http://gerrit.rockbox.org/r/526 : 3[Fuze+] activate the automatic touchpad disable on keylock by Jean-Louis Biasini (changes/26/526/1) 12.41.56 # 3Gerrit review #527 at http://gerrit.rockbox.org/r/527 : 3[Fuze+] Define Hard keys for Fuze+ by Jean-Louis Biasini (changes/27/527/1) 12.42.16 # good bot! /me scratchs bot 12.43.11 # pamaury: you don't have to bother rewriting stuff, just tell me want to do! 12.44.00 # pamaury: I'm also testing having low power seting for the touchpad and it seems to be just as stable as normal power 12.44.22 # I want to test it a bit over to see if its really stable 12.45.03 # jlbiasini: out of curiosity, I wonder if the touchpad consumes a lot of energy or not, ie does it save battery to enter low power mode or not. 12.45.23 # yes that what I want to know to 12.45.24 # I'll have a look at this, you have been on fire this week-end 12.45.42 # yes!! 12.45.59 # but the basoc implementation was not that difficult 12.46.10 # My guess is that it doesn't consume much power, much less than the screen for example 12.48.08 # for what gevearts told me: first i've to separate the disabling of touchpad from putting it to sleeps, we should generalised that code to any touch device... 12.48.52 # ok, i'm going for lunch, we can discuss that later, or maybe example that better to me 12.49.39 # pamaury: what do you mean by " example that better to me"? 12.51.16 # haha 12.51.19 # explain, perhaps 12.51.37 # netsplit between his brain and his fingers 12.58.35 Join Rower [0] (husvagn@v-413-alfarv-177.bitnet.nu) 13.02.59 Join robin0800 [0] (~Robin0800@cpc1-brig15-2-0-cust755.3-3.cable.virginmedia.com) 13.03.44 *** Saving seen data "./dancer.seen" 13.27.08 Join DexterLB [0] (~dex@77-85-0-255.btc-net.bg) 13.28.30 Quit amiconn (Remote host closed the connection) 13.28.30 Quit pixelma (Remote host closed the connection) 13.28.53 Join amiconn [0] (amiconn@rockbox/developer/amiconn) 13.28.53 Join pixelma [0] (pixelma@rockbox/staff/pixelma) 13.29.34 Quit amiconn (Remote host closed the connection) 13.29.34 Quit pixelma (Remote host closed the connection) 13.30.00 Join amiconn [0] (quassel@rockbox/developer/amiconn) 13.30.00 Join pixelma [0] (pixelma@rockbox/staff/pixelma) 13.32.29 # jlbiasini: why do we need to separate sleep for disable ? 13.32.50 # I guess that's just to make it more general, because some touchpad may have a power gate 13.34.22 # I think he means that not responding to touchpad and putting it to sleep should be 2 different stuff (example: not reponding to touch device while locked shouldn't be dependend on device's driver handling power function) 13.35.06 # ok, make sense 13.35.55 # he also told me something about putting those those 2 function touchdev_wakeup and touchdev_disable in another place more general 13.37.15 # "in button.h" to quote him 13.37.37 Nick evilnick_ is now known as evilnick (~evilnick@d54C370E0.access.telenet.be) 13.37.50 Quit evilnick (Changing host) 13.37.50 Join evilnick [0] (~evilnick@rockbox/staff/evilnick) 13.44.34 # pamaury: but it add a dificulty: the advantage of disabling the touchpad is that action.c doesn't have to bother from where are coming the key shooted (hardkeys vs virtual) after that. So for instance I don't know what would be cleaner to turn that around. I can either have a define of all non virtual keys for each touch device, that I compare to the key fire in action and ignore it while locked OR I can rewrite touch device drivers to have a void 13.44.34 # touchdev_shutthefuckup(void) function that keep it quiet 13.45.40 # I like the patches above, very useful when I resume R1 port ;) 13.45.59 # +1 for the function name too :D 13.47.14 # thks, do you mean you are using those patch on another port? or that they interfere with it? 13.47.32 # nono just because R1 has a touchscreen :) 13.47.46 # great 13.48.05 # you can find the source for it as a gerrit patch, let me see (it's quite some time, I need to clean it up :) ) 13.48.09 # like I said we are looking on how to make it the more general as possible 13.48.58 # jlbiasini: g#395 13.49.02 # 3Gerrit review #395 at http://gerrit.rockbox.org/r/395 : 3Samsung YP-R1 target port! by Lorenzo Miori (changes/95/395/3) 13.49.16 # (this bot is pretty ^^) 13.50.48 # lorenzo92: you mean that you have a fully functionnable port on gerrit, why isn't it merge as unstable already? 13.51.32 # kugel: ping 13.51.35 # no idea, I think there was an issue regarding plugins (i.e. too many change in a shot), kugel knows. 13.51.44 # I need to clean it up now 13.52.17 # talking of kugel is he in holiday or something? 13.52.25 # once my firmware tools are merged (g#506) 13.52.29 # 3Gerrit review #506 at http://gerrit.rockbox.org/r/506 : 3Firmware tools for Samsung YP-R0/YP-R1 (and possibly others) by Lorenzo Miori (changes/06/506/4) 13.53.01 # I have a few plugin PLAzation toget reviewed... 13.53.19 # great 13.54.05 # pamaury: any idea about the best way to ignore touchdev? ^ 13.54.32 # or should I ask on mail? 13.55.55 # by the way, maybe a silly question, I have some python scripts I used to decompress some newer samsung firmware files. they are very rough, is it wort putting them in rockbox utils/ ? 13.56.19 # ah also some tools to manipulate .aui samsung sound resource files 14.03.59 # jlbiasini: good question, I don't know what is the best solution, I think being able to disable the touchpad is better than having a distinction between hard and soft keys 14.05.18 # any idea how many touchdevice we have? 14.05.41 # samsung YP-R1, hosted, has a nice touch driver (multi touch too!!) 14.05.46 # I'm on for a drivers rewriting session... 14.06.19 # wait I will ask on the mailing list anyway just to be sure I don't start something for nothing 14.06.39 # indeed, let's discuss that there... 14.08.28 # lorenzo92 is that touchpad RMI? 14.10.19 Quit amiconn (Remote host closed the connection) 14.10.19 Quit pixelma (Remote host closed the connection) 14.10.39 Join pixelma [0] (pixelma@rockbox/staff/pixelma) 14.10.40 Join amiconn [0] (amiconn@rockbox/developer/amiconn) 14.10.53 # jlbiasini: hum I don't know, how to see that? 14.11.15 # btw, RMI stands for? I don't think it's related to java ^^ 14.11.34 # arf no it's a hosted so I guess you get the virtual button directly from os 14.12.02 # nope 14.12.07 # I manage the chip directly 14.12.17 # it's a special hosted, like R0 :) 14.12.51 # it's just a standalone player which runs linux, but most of the control is still done by some app (the only running) 14.13.37 # yes I had a look at your code so I don't think it directly called 14.14.14 # practically I get a data blob 14.22.46 # <[Saint]> the R* ports are quite clever. 14.24.47 # <[Saint]> its a shame my R0 decided to wreck itself. its a weird device, but its quite nice. 14.28.19 # why weird? :) 14.28.45 # for me after almost 3 years of usage is still fine and I like it 14.31.47 Quit pamaury (Ping timeout: 245 seconds) 14.37.22 # pamaury: for a start should the power function be implemented directly in the RMI driver? 14.37.54 # <[Saint]> Oh, I liked it. I guess I mean...different, not weird, most of my targets are scrollwheel/clickwheel type. 14.39.12 # <[Saint]> Various iPods, Fuze V1/2, various Clip variants etc. 14.39.50 # ah yeah now I get the meaning, yes you are absolutely right :) 14.41.58 Join mortalis [0] (~mortalis@175.195.185.119) 14.45.02 Quit ZincAlloy (Quit: CGI:IRC (EOF)) 14.48.27 Quit mortalis (Ping timeout: 245 seconds) 14.48.45 Join amayer [0] (~amayer@mail.weberadvertising.com) 14.52.11 Quit ungali (Quit: Yaaic - Yet another Android IRC client - http://www.yaaic.org) 14.54.24 # paaury: any idea why the fuze+ bootloader display a different charge value than rockbox? 14.54.40 # pamaury:^ 15.03.47 *** Saving seen data "./dancer.seen" 15.04.32 Join mortalis [0] (~mortalis@175.195.185.190) 15.09.36 Nick SuperBrainAK is now known as DormantBrain (~andy@shared02.balt01.cd.2g2u.net) 15.10.32 Join tertu [0] (~tertu@65-128-181-81.mpls.qwest.net) 15.11.28 Quit mortalis (Ping timeout: 264 seconds) 15.18.34 # jlbiasini: no, just very busy at the moment (master thesis, etc) 15.20.59 # kugel: ok ok I just have to very obvious PLA patches for plugin g#518 and g#520 those are exact replica of previously pushed ones 15.21.03 # 3Gerrit review #518 at http://gerrit.rockbox.org/r/518 : 3[Plugins] Stopwatch PLA integration by Jean-Louis Biasini (changes/18/518/3) 15.21.06 # 3Gerrit review #520 at http://gerrit.rockbox.org/r/520 : 3[Plugins] text_editor PLA integration by Jean-Louis Biasini (changes/20/520/2) 15.21.51 # so if you have 5 minutes you can push it but there is of course no hurry about them... 15.22.11 # I have to go 15.22.18 Quit jlbiasini (Quit: jlbiasini) 15.22.51 Join ZincAlloy [0] (~d9eebfd8@www.haxx.se) 15.28.52 Quit ender` (Ping timeout: 240 seconds) 15.30.27 Join ender` [0] (krneki@foo.eternallybored.org) 15.41.17 Join dv__ [0] (~quassel@chello080108009040.14.11.vie.surfer.at) 15.41.37 Quit dv_ (Ping timeout: 245 seconds) 15.47.11 Join mortalis [0] (~mortalis@175.195.185.190) 15.53.08 Quit mortalis (Read error: Connection reset by peer) 16.00.56 Quit [Saint] (Remote host closed the connection) 16.01.54 Join [Saint] [0] (~saint@rockbox/user/saint) 16.06.32 Join mortalis [0] (~mortalis@175.195.185.190) 16.20.41 Quit tertu (Ping timeout: 276 seconds) 16.21.18 Quit mortalis (Ping timeout: 246 seconds) 16.23.08 Join jlbiasini [0] (~metaphysi@86.34.67.25) 16.42.37 Join mortalis [0] (~mortalis@175.195.185.190) 16.44.20 Quit olspookishmagus (Quit: free() the malloc()) 17.00.30 Nick dv__ is now known as dv_ (~quassel@chello080108009040.14.11.vie.surfer.at) 17.02.15 Quit mortalis (Ping timeout: 246 seconds) 17.02.38 Join mortalis [0] (~mortalis@175.195.185.190) 17.03.50 *** Saving seen data "./dancer.seen" 17.06.52 Quit fyre^OS (Read error: Connection reset by peer) 17.07.15 Join fyrestorm [0] (~nnscript@cpe-24-90-158-3.nyc.res.rr.com) 17.21.54 Quit fyrestorm (Read error: Connection reset by peer) 17.22.10 Join fyrestorm [0] (~nnscript@cpe-24-90-158-3.nyc.res.rr.com) 17.23.46 Quit ZincAlloy (Quit: CGI:IRC (EOF)) 17.26.20 Join ZincAlloy [0] (~d9eebfd8@www.haxx.se) 17.32.13 Quit mortalis (Quit: Leaving) 17.47.38 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 17.50.49 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 17.56.19 # jlbiasini: yes, we can implement touchpad disable and low power in RMI (i'm not sure low power is needed, just disable) 17.57.06 # jlbiasini: probably because in rockbox the battery charge is filtered whereas the bootloader shows the raw value 17.57.22 # well as it is in the rmi sheet I thought to implement it but if it's really useless 17.57.25 # by the way, I think we might need to recalibrate the charge/discharge curves 17.57.43 Join dell [0] (~dell@ool-435622d3.dyn.optonline.net) 17.58.09 # pamaury I making some bettery test with the power state low_power 17.58.26 # how long do you think we need to have a reliable idea? 18.00.02 # the point of low power can be to save more power on device that can be use like that without any difference 18.00.41 Join EstebanMonge [0] (~emonge@200.110.251.210) 18.00.48 # I've been using it for 2 days now and it's really just as in normal mode whereas very_low_power make it difficult to use 18.01.23 # I would do a normal battery bench (ie big album), for at least 10 hours 18.01.54 # ok it's on 18.02.07 # maybe start with normal vs very_low_power, to make the difference more obvious if any 18.02.43 # did you noticed that the bootloader report a different power level than rockbox, 18.03.26 # well I'm starting with disable 18.03.57 # because anyway this is what we will have when the device is lockes 18.04.24 Quit dell (Quit: Ex-Chat) 18.05.24 Quit EstebanMonge (Ping timeout: 248 seconds) 18.05.25 # the difference comes from bad calibration probably, as I said we need to redo the charge/discharge curve 18.25.29 Join EstebanMonge [0] (~emonge@200.110.251.210) 18.34.34 Quit derf (Ping timeout: 260 seconds) 18.48.27 Join belak51 [0] (~belak@facebook/engineering/belak) 18.55.42 # pamaury: talking about power I saw that a lot of lcd driver implement lcd_power_off/on but not the fuzeplus. Is ist because ours lcd cannot be put to sleep or because you didn't wrote the function yet? 18.57.59 # well the ili9325 datasheet does document a sleep mode 19.03.51 *** Saving seen data "./dancer.seen" 19.10.17 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 19.12.30 Join derf [0] (~derf@fuzzyneural.net) 19.18.56 # pamaury actually if the very low power mode is really interesting we could set it after some inactivity then go back to the normal mode on first touch. The way I implement it could even be more power saving because I didn't reduce the reporting rate that could also be cut down while not active... 19.25.24 Quit robin0800 (Quit: KVIrc 4.3.1 Aria http://www.kvirc.net/) 19.33.28 Quit melmothX (Quit: #) 19.38.39 Quit funman (Changing host) 19.38.39 Join funman [0] (~fun@rockbox/developer/funman) 20.00.43 # pamaury: you or wodz found out that we don't do the sd card switch_func command quite right on AMSv1/2, right? 20.34.42 Join akaWolf [0] (~akaWolf@188.134.9.161) 20.34.42 Quit akaWolf (Changing host) 20.34.42 Join akaWolf [0] (~akaWolf@unaffiliated/akawolf) 20.35.48 Quit ender` (Ping timeout: 248 seconds) 20.36.15 Join Strife89 [0] (~Strife89@2602:306:250e:c3c9:20a:95ff:fef3:ec5f) 20.51.21 Join ender` [0] (krneki@foo.eternallybored.org) 21.03.55 *** Saving seen data "./dancer.seen" 21.13.52 Quit lorenzo92 (Ping timeout: 264 seconds) 21.14.41 # what's "PLA integration"? 21.40.16 Join einhirn [0] (Miranda@bsod.vpn.tu-clausthal.de) 22.17.19 Part Strife89 ("Leaving") 22.22.40 Part dunpeal 22.24.05 Join micah [0] (~micah@debian/developer/micah) 22.30.23 Join saratoga_ [0] (123e1c0a@gateway/web/freenode/ip.18.62.28.10) 22.30.29 # dunpeal: IIRC its a system for having generic keymaps for some plugins 22.31.53 # i've got an ipod classic, 80gb and looking at http://www.rockbox.org/wiki/IpodClassicPort - it looks like I can put rockbox on, but i'm not positive I understand the steps here 22.32.01 # i think the first thing I'll do is charge it all the way up 22.33.20 # but I'm wondering if this thing is any good 22.33.39 # i plugged it into my linux system and I got weird errors in dmesg 22.35.35 # What sort of errors? 22.51.19 # Gallomimia: [201706.648645] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE 22.51.23 # [201706.648653] Sense Key : Medium Error [current] 22.51.25 # [201706.648667] Add. Sense: Unrecovered read error 22.51.32 # [201725.169633] end_request: critical target error, dev sdh, sector 155907504 22.51.41 # etc... I can pastebin the whole thing if you think it is useful 22.52.09 # this device has been used on an apple, but not for a long time, it is now on and saying "Connected Eject before disconnecting" 22.52.18 # i dont know what that means to 'eject before..." 22.52.35 # Unmount, basically 22.52.46 # But that does look like a disk going bad 22.53.07 # the drive isn't mounted, so I wouldn't be able to unmount it 22.53.22 # Yes, but it doesn't really know that :) 22.53.50 # is there a way to check the drive's integrity? I could try and run badblocks on it to remap bad blocks... 22.54.40 # it seems to function fine in the ipod interface 22.55.06 # but it does have a noticible "sound" to it 22.55.13 # when I plug in the usb cable 22.55.18 # There's a diagnostic mode on at least some of the ipods IIRC that can do SMART, but I don't know about the classic 22.55.51 Nick DormantBrain is now known as SuperBrainAK (~andy@shared02.balt01.cd.2g2u.net) 22.56.01 # Well, if you figure out where the bad blocks are, you might be able to work around them with some creative partitioning 22.56.31 # But then errors tend to spread over time, so that probably isn't a good long term solution 23.03.57 *** Saving seen data "./dancer.seen" 23.05.50 Join ender1 [0] (krneki@foo.eternallybored.org) 23.06.40 Quit ender` (Ping timeout: 264 seconds) 23.07.20 # gevaerts: i've had good luck mapping out badblocks in disks I've used over time, so I'll give it a try 23.07.32 # but... once I'm done with this - what is the process I need to do to get rockbox on this bad boy 23.07.36 # It definitely can't hurt 23.07.53 # it looks like maybe first I need to get the emCORE bootloader on it 23.09.18 # Yes. I'm not a specialist (I don't have a classic myself), but I understand you install emcore on it, which might include a rockbox build IIUC, and then you install a fresh rockbox build (the one included with emcore is *old*, but kept there because it's known to be working at least well enough to recover stuff with) 23.10.36 # ok, i'll do some disk testing first and then try to get emcore on there and then see if I have troubles 23.13.13 Quit amayer (Quit: Leaving) 23.15.26 # there's also hddscan2 :) 23.15.56 # which I developed exactly for that purpose (to take care of buggy toshiba ipod drives which run out of spare sectors) 23.16.46 # emcore (and rockbox, at least with a patch) can load a software bad block remapping layer which takes care of this 23.17.31 # and hddscan2 is the tool which scans the drive's surface (taking the firmware bugs into account, which makes the scan take literally days to weeks), and sets up the remapping data structures on the drive 23.20.28 # TheSeven: days to weeks? 23.20.29 # wow 23.20.40 # i was hoping to use this in one week's time :) 23.21.02 Quit ender1 (Quit: The state must declare the child to be the most precious treasure of the people. As long as the government is perceived as working for the benefit of the children, the people will happily endure almost any curtailment of liberty and almost any deprivati) 23.21.21 # TheSeven: do you have a link to hddscan2? 23.21.39 # i'm finding hddscan, but not 2 23.22.36 # oh is that part of emcore? 23.22.52 # http://files.freemyipod.org/tmp/hddscan2.ubi 23.23.10 # sorry I'm a bit new here, what is a .ubi file? 23.23.17 # basically a boot image 23.23.39 # in this case an emcore kernel with the hddscan2 app embedded into it 23.23.43 # ok, do I just dd that over my ipod? :) 23.23.58 # you boot the ipod into UMSboot mode, and drop the ubi file into the ramdisk 23.24.43 # * micah looks up what UMSboot mode is 23.26.17 # is this it? http://www.freemyipod.org/wiki/EmCORE_Installation/iPodClassic/PrepareDFULinux 23.26.57 # yes, that's the way to load UMSboot on a non-emcore'd ipod 23.27.06 # once emcore is installed you can just launch it from the boot menu 23.28.02 # TheSeven: oh ok, I'm going to emcore this anyways. so I can just do that. I just need to figure out how to emcore it :) 23.28.39 Quit jlbiasini (Quit: jlbiasini) 23.28.41 # seems like that is the process to do that 23.28.53 # once you're in UMSboot mode, just drop the installer UBI file into the ramdisk :) 23.36.28 Quit EstebanMonge (Ping timeout: 246 seconds) 23.43.17 Quit kevku (Ping timeout: 245 seconds) 23.48.00 Quit liar (Remote host closed the connection) 23.54.00 Join tertu [0] (~tertu@65-128-181-81.mpls.qwest.net) 23.55.56 Join EstebanMonge [0] (~emonge@200.110.251.210)