--- Log for 13.11.113 Server: sendak.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 6 days and 18 hours ago 00.05.37 Quit rdn (Quit: Ex-Chat) 00.09.16 Quit habys (Ping timeout: 245 seconds) 00.11.57 Join habys [0] (~luke@arikui.org) 00.19.30 Quit wodz (Quit: Leaving) 00.25.46 # andypotter: it appears to be using a custom cable, i think its called MEDIA-IN (stupid name imo) 00.26.31 # its a big chunky manypinned connector on the vw side, and a standard ipod connector on the other 00.26.45 # doesnt appear to be usb 00.26.51 # i could be wrong though 00.27.17 Quit kugel (Ping timeout: 272 seconds) 00.27.34 # do we support the tall ipod nanos? 00.28.07 # gen5 nano 00.28.22 # No 00.28.49 # thats a shame, the wife just found hers from a few years ago :p 00.28.53 # Still the old lineup. 1g and 2g 00.29.05 # Still with the non-working USB on the 2g 00.29.07 # oh, its called mdi cable i guess 00.29.12 # fucking inconsistent manual 00.31.09 Quit krabador (Quit: Sto andando via) 00.32.57 Join krabador [0] (~krabador_@unaffiliated/krabador) 00.37.22 Quit krabador (Client Quit) 00.37.30 # andypotter: the vw part number for the cable i have is 5N0 035 554 B 00.38.03 Join krabador [0] (~krabador_@unaffiliated/krabador) 00.38.40 # its got some pretty heavy integration with the head unit though, so this isnt going to be an easy fix at all, but possibly it will improve other peoples lot who have similar head units 00.40.11 Quit liar (Quit: huiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii) 00.40.28 Join krnlyng [0] (~liar@83.175.90.24) 00.44.46 Quit bertrik (Remote host closed the connection) 00.44.54 Quit krabador (Quit: Sto andando via) 00.46.25 Join krabador [0] (~krabador_@unaffiliated/krabador) 00.47.00 Quit ruskie (Ping timeout: 264 seconds) 00.50.43 Join MarcAndersen [0] (~no_znep@62-135-233-71-dynamic.dk.customer.tdc.net) 00.52.18 # Hi. I see that something should be ready now for my zen x-fi. Can someone guide me through installing? 00.53.12 # You'll need pamaury for that, but I don't know if he's still awake 00.57.25 Join ruskie [0] (ruskie@sourcemage/mage/ruskie) 00.57.37 # the biggest problem is the recovery menu. I am blind and as such I can't read where the correct option is 01.00.20 Quit ender` (Quit: You know you created god in your image when he hates the same people you do.) 01.04.44 # is it just my newly set up system, or is building RAAA generally quite outdated and needs lot of fixes to build without errors? 01.05.33 # I don't think it needs a lot of fixes. I'd say one or two should do it :) 01.06.02 # The problem I'm aware of is that newer android sdks dropped some of the scripts we're using 01.06.16 # well, i had to hunt down the old 4.4.3 arm-eabi, had to find a source of the apkbuilder script, some 4-5 symlinks, and a few changes in /app/action.c 01.06.17 # :) 01.06.39 # By "aware of", I mean I know there's an issue :) 01.07.01 # yeah, the issue is mainly in the sdk, shuffling files/folders around, and ditching some stuff 01.07.51 # but it seems i just did a successful build on debian x64, with latest sdk and ndk 01.10.36 # jsut pushed it... yep, it works :) 01.13.52 # hmm, im betting theres no public pinout for this adapter cable 01.14.21 # gues sill have to get a 30pin breakout and map it to the vw side 01.14.27 Quit lebellium (Quit: ChatZilla 0.9.90.1 [Firefox 26.0/20131107161719]) 01.21.22 # theres definitely more than 4 pins hot though, so im pretty sure it isnt usb 01.33.39 *** Saving seen data "./dancer.seen" 01.35.29 Quit scorche|sh (Changing host) 01.35.29 Join scorche|sh [0] (~scorche@rockbox/administrator/scorche) 01.36.26 Quit pamaury (Ping timeout: 264 seconds) 01.40.20 Join stripwax [0] (~Miranda@rockbox/developer/stripwax) 01.50.58 # my android thing has that nasty bug that when the backlight turns off while rockbox is the active app, it won't turn on again - only a reset or adb reboot helps 01.51.12 # would action.c and/or buttons.c be the place to look for a fix? 01.51.44 # *button.c 01.54.28 # haha lovely 01.54.32 # how does that happen? 01.54.50 # i have no idea... on two other android things it works fine 01.55.26 # on this one (galaxy tab 7.7) it never wakes the backlight, no matter if stock firmware, CM, PAC, whatever 01.56.23 # when those lines are commented out in action.c, it builds, when not, the following error ensues: http://pastie.org/8476218 01.56.36 # and i guess that's the issue right there 01.57.17 # (i just had to comment them out right now, on my new setup, on my old machine it built fine with those lines in, but the results were the same) 02.01.26 # wtf is set_backlight_on_keypress_oracle()? 02.04.54 # action.c is Copyright (C) 2006 Jonathan Gordon.. you better ask him ;) 02.05.59 # That function sure aint one of That Crazy Clown's 02.06.09 # weird indeed 02.07.58 # did another git pull, and the oracle went away 02.10.06 Quit habys (Ping timeout: 245 seconds) 02.11.56 # i never touched that file... well, it built fine. 02.12.35 # but still no waking up of the screen, ffs 02.14.52 Join habys [0] (~luke@arikui.org) 02.24.58 # <[Saint]> JdGordon: ...Wile. E. Coyote is a committer? 02.25.31 Quit stripwax (Read error: Connection reset by peer) 02.25.37 # he may have slipped through the real name policy? 02.25.39 # <[Saint]> (if anyone gets that, well done) 02.35.30 # <[Saint]> Oh. Heh. 02.35.46 # <[Saint]> So...the E380 *is* just a rebranded E370. 02.53.24 Nick DormantBrain is now known as SuperBrainAk (~andy@74.112.200.73) 02.53.33 Quit Onay (Ping timeout: 241 seconds) 02.54.42 Join Onay [0] (~onay@unaffiliated/onay) 02.54.48 Quit pystar89 (Ping timeout: 246 seconds) 02.57.16 Quit krabador (Quit: Sto andando via) 03.33.40 *** Saving seen data "./dancer.seen" 03.46.45 Join cmhobbs [0] (~cmhobbs@fsf/member/cmhobbs) 03.56.17 Quit cmhobbs (Ping timeout: 245 seconds) 04.32.08 Quit pixelma (Disconnected by services) 04.32.08 Quit amiconn (Disconnected by services) 04.32.08 Join amiconn_ [0] (amiconn@rockbox/developer/amiconn) 04.32.08 Join pixelma_ [0] (pixelma@rockbox/staff/pixelma) 04.32.08 Nick pixelma_ is now known as pixelma (pixelma@rockbox/staff/pixelma) 04.32.08 Nick amiconn_ is now known as amiconn (amiconn@rockbox/developer/amiconn) 04.37.12 Join cmhobbs [0] (~cmhobbs@ip70-178-52-92.ks.ks.cox.net) 04.37.12 Quit cmhobbs (Changing host) 04.37.12 Join cmhobbs [0] (~cmhobbs@fsf/member/cmhobbs) 04.42.17 Quit ladyblink (Ping timeout: 240 seconds) 04.44.21 Join ladyblink [0] (bassgeisha@selectah.drop.that.bass.aikyou.bassgeisha.com) 04.51.36 Join krabador [0] (~krabador@unaffiliated/krabador) 05.01.07 Quit Scall (Ping timeout: 272 seconds) 05.01.55 Join Guest56744 [0] (~chat@host10-17-static.5-79-b.business.telecomitalia.it) 05.24.12 Quit kiwicam (Remote host closed the connection) 05.31.43 Quit TheSeven (Disconnected by services) 05.31.57 Join [7] [0] (~quassel@rockbox/developer/TheSeven) 05.33.41 *** Saving seen data "./dancer.seen" 05.35.15 Quit Guest56744 (Ping timeout: 264 seconds) 05.36.55 Join Scall- [0] (~chat@host10-17-static.5-79-b.business.telecomitalia.it) 05.41.16 Quit krabador (Remote host closed the connection) 05.56.47 Quit cmhobbs (Ping timeout: 245 seconds) 06.31.22 Quit B4gder (Ping timeout: 245 seconds) 07.01.50 Join dfkt_ [0] (~dfkt@unaffiliated/dfkt) 07.03.16 Quit dfkt (Ping timeout: 248 seconds) 07.03.58 Join mortalis|2 [0] (~kvirc@213.33.220.118) 07.08.30 Nick mortalis|2 is now known as mortalis (~kvirc@213.33.220.118) 07.28.37 Quit Scall- (Ping timeout: 240 seconds) 07.29.44 Quit derf (Ping timeout: 245 seconds) 07.30.55 Join Scall [0] (~chat@unaffiliated/scall) 07.33.43 *** Saving seen data "./dancer.seen" 07.43.33 Join LinusN [0] (linus@giant.haxx.se) 07.47.14 Join derf [0] (~derf@fuzzyneural.net) 07.49.12 Part Onay 07.50.30 Join ender` [0] (krneki@foo.eternallybored.org) 08.03.08 Quit ladyblink (Ping timeout: 244 seconds) 08.03.27 Join ladyblink [0] (bassgeisha@selectah.drop.that.bass.aikyou.bassgeisha.com) 08.13.42 Join akaWolf [0] (~akaWolf@unaffiliated/akawolf) 08.43.46 Join kugel [0] (~kugel@91-66-52-103-dynip.superkabel.de) 08.43.46 Quit kugel (Changing host) 08.43.46 Join kugel [0] (~kugel@rockbox/developer/kugel) 08.50.09 Join Zagor [242] (~bjst@rockbox/developer/Zagor) 08.58.09 Join kevku [0] (~kevku@2a01:d0:ffff:34a::8:3) 09.04.57 Join kiwicam [0] (~quassel@121.99.176.30) 09.25.44 Join lebellium [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 09.29.02 Join petur [0] (5bb7304d@rockbox/developer/petur) 09.33.47 *** Saving seen data "./dancer.seen" 09.42.11 Part LinusN 09.43.46 Join LinusN [0] (linus@giant.haxx.se) 10.02.48 Join Guest17648 [0] (~husvagn@90-230-140-28-no41.tbcn.telia.com) 10.13.18 Quit Guest17648 (Ping timeout: 245 seconds) 10.13.46 Join Guest17648 [0] (~husvagn@90-230-140-28-no41.tbcn.telia.com) 10.27.12 Quit mc2739 (Read error: Connection reset by peer) 10.27.17 Join mc2739_ [0] (~mc2739@rockbox/developer/mc2739) 10.27.22 Nick mc2739_ is now known as mc2739 (~mc2739@rockbox/developer/mc2739) 10.45.42 Quit Zagor (Ping timeout: 252 seconds) 10.48.27 Quit Scall (Ping timeout: 245 seconds) 10.49.50 Join maruk [0] (~papier@titanium.v6.sdv.fr) 10.54.31 Join Scall [0] (~chat@unaffiliated/scall) 11.01.37 Join foolsh [0] (~foolsh@c-24-14-134-34.hsd1.in.comcast.net) 11.28.20 Join pystar89 [0] (~pystar89@ip-109-90-154-150.unitymediagroup.de) 11.33.34 Join Mir_ [0] (~Mir@pool-71-109-219-225.lsanca.dsl-w.verizon.net) 11.33.44 Quit Mir (Ping timeout: 245 seconds) 11.33.50 *** Saving seen data "./dancer.seen" 11.40.07 Quit [Saint] (Ping timeout: 244 seconds) 11.40.08 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 11.40.25 Join [Saint] [0] (~saint@rockbox/user/saint) 11.44.56 Quit Guest17648 (Ping timeout: 246 seconds) 11.45.52 Join Guest17648 [0] (~husvagn@90-230-140-28-no41.tbcn.telia.com) 11.46.42 # MarcAndersen: hi 11.47.41 # [Saint]: yes it appears so, but we need to test on target to be sure 11.48.01 # <[Saint]> pamaury: were you so stuck in RE mode you missed it? 11.48.30 # missed what ? 11.49.02 Quit akaWolf (Ping timeout: 272 seconds) 11.59.13 # [Saint]: except if you have some information I don't have, I don't know how you could tell for sure this is the case 11.59.45 # <[Saint]> I don't...I'm going entirely from information you have given. 12.00.15 # <[Saint]> I was given the impression that for now at least you were fairly convinced they were one in the same. 12.01.19 # <[Saint]> Which made me wonder how that happened, since (afaik) they were both being reversed at approximately the same time. 12.01.40 # I reversed the E370 way before the E370 12.01.42 # *E380 12.02.24 # <[Saint]> Ah - I see. I got the impression they were fairly close to each other, relative to time. 12.02.49 Join rela [0] (~x@pdpc/supporter/active/rela) 12.03.10 # I disassembled the E370 a few weeks ago already. I only gave a shot at the E380 last week end and it was pretty obvious from the code that it was the same: same lcd, same pins, (same crap) 12.04.42 # It is just that I created the forum thread and wiki pages approximately at the same time ^^ 12.14.43 # pamaury: some typos: E360port "The point of the recovery procedure is too reinstall" E360: "The Sony NWZ-E370 features 11 hardware buttons" 12.15.04 # hum bold fail 12.15.23 # I wanted to highligh "too" and "E370" 12.16.47 # lebellium: thanks, will fix that 12.16.59 # lebellium: do you have a E380 ? 12.17.36 # Nope. Not sure it's worth buying it since it's worse than my E360. I rather consider buying some E4xx series 12.18.00 # yeah you're right 12.18.46 # which E4xx do you have ? 12.19.10 # for now none 12.19.32 # But I'm looking for a cheap 8GB Sony player. 12.19.45 # 4GB on my E360 is not enough 12.20.05 # yeah, no micro-sd port is really bad 12.20.44 # * [Saint] simply couldn't go back to "conventional" flash storage. 12.21.09 # <[Saint]> Unless someone makes a very high capacity Rockboxable device in the near future, which I doubt. 12.21.41 # you have 64GB sd cards now ;) 12.21.47 Nick SuperBrainAk is now known as DormantBrain (~andy@74.112.200.73) 12.21.59 # <[Saint]> That's still a quartar of what I'm used to. :) 12.22.09 # <[Saint]> *quarter, even 12.22.18 # we need a player with four micro-sd ports then :D 12.22.24 # <[Saint]> :) 12.22.25 # do you think only the E440 can be handled or a more recent model like the E470 could be too? 12.23.33 # <[Saint]> Maybe I could get a uSD RAID card and a string of adapters to turn MSATA into uSD? :) 12.23.42 # lebellium: E440 is imx233 based but unfortunately it uses raw NAND (instead of eMMC) and I haven't reverse the FTL 12.24.22 # arf 12.24.24 # [Saint]: I think on principle you could have a msata to µsd adapter but I wonder where you would put the ssd then ^^ 12.24.36 # <[Saint]> Huh...uSD RAID cards are actually disturbingly cheap. 12.25.00 # <[Saint]> (likely sue to being crap, and really, really weird) 12.25.28 # <[Saint]> pamaury: duct taped to the player - no larger than my personal amp. :) 12.25.59 # woa, didn't know it existed ^^ 12.26.21 # lebellium: E470 is based on linux, awful similar to E460 it seems 12.26.28 # <[Saint]> I found them about a year ago, but they weren't this cheap back then. 12.26.38 # <[Saint]> And I still think the same as I did then; "why?" 12.26.55 # yeah, why, why would you want to do that ?! 12.28.07 # pamaury: the E470 looks very different from the E460. I don't know inside though 12.28.45 # they are both based on linux and I think it is safe to think we can handle most if not all sony nwz linux players at once, at least the recent ones 12.29.00 # lebellium: just to be clear, I have a lot of interest in reversing the FTL (because of E440 and Zen X-Fi2) but it's huge task really 12.29.45 # I can imagine. But on the X-Fi 2 there is a sd slot as workaround right 12.30.23 # when I had a look at how it's implemented on the E460, it was obvious that they put some effort into abstracting the hardware so that their software is independent of the actual player. That way they can sell you more crippled players :-/ 12.35.18 # lebellium: so at the moment, the best you can do would be to find a very cheap E460 so that I can do the port and you test it/help me. And when it's more ready, you buy more expensive linux based players 12.36.51 # yeah, the only problem is "cheap" :D Look, 35€ for 4GB :S http://www.leboncoin.fr/image_son/554482847.htm?ca=12_s 12.37.25 Quit Guest17648 (Ping timeout: 240 seconds) 12.37.38 Join Guest17648 [0] (~husvagn@90-230-140-28-no41.tbcn.telia.com) 12.41.58 # lebellium: http://www.leboncoin.fr/image_son/561214551.htm?ca=12_s, don't know the model though 12.42.23 # lebellium: E470 brand new, 8GB: http://www.leboncoin.fr/image_son/560426011.htm?ca=12_s 12.43.19 # the 1st one could be a E454 12.43.26 # <[Saint]> pamaury: if you need the(se) device(s), can The Fund not compensate you for them? 12.44.06 # <[Saint]> I realize lebellium will probably buy this device (and every other in existence) anyway, but, you could get your own. 12.44.16 # lol 12.44.32 # I already told him to ask for the fund 12.44.40 # he deserves it 12.44.48 # <[Saint]> Certainly. 12.44.58 # lol yeah, I should probably ask the fund to give a little money back for the Creative players I bought 12.49.55 # ok I ask for the €40 E474. It's tempting^^ 12.50.22 Quit Guest17648 (Ping timeout: 252 seconds) 12.50.28 # indeed 12.50.44 # if you don't I will :p 12.51.18 # but 40€ + shipping costs could be the same as 50€ in Paris http://www.leboncoin.fr/image_son/567789275.htm?ca=12_s 12.52.04 # good point, is this one 8GB ? 12.52.13 # yes, both are 8GB 12.52.37 # maybe one for you, one for me :D 12.53.25 # pikc the one on Paris then, since I'm abroad, I'll need the seller to send it by post anyway 12.54.50 # ok, first I will see what the guy from nantes says about shipping and payment method 12.55.01 # I let you know 13.18.54 Join Guest17648 [0] (~husvagn@90-230-140-28-no41.tbcn.telia.com) 13.19.39 Join akaWolf [0] (~akaWolf@unaffiliated/akawolf) 13.21.28 Join pretty_function [0] (~sigBART@123.252.213.171) 13.21.36 Quit pretty_function (Remote host closed the connection) 13.24.11 Join krabador [0] (~krabador_@unaffiliated/krabador) 13.30.05 # what's the difference between "button code" and "prereq button code" in keymap-nwz? 13.31.12 Quit Guest17648 (Ping timeout: 244 seconds) 13.31.13 # <[Saint]> iirc, the prereq things are things like "button does foo, but only when bar is held" 13.31.55 Join Guest17648 [0] (~husvagn@90-230-140-28-no41.tbcn.telia.com) 13.33.53 *** Saving seen data "./dancer.seen" 13.34.13 # I think it's more like if "blah happens or is true before", which could be holding another button before or together but it's also used to separate long or short button presses IIRC 13.35.38 # for example I see 13.35.40 # " { ACTION_STD_OK, BUTTON_PLAY|BUTTON_REL, BUTTON_PLAY }," 13.38.41 # I'd like to fix the E360 keymapping since pamaury seems to be short of time but this looks a bit difficult to me. Sometimes the "prereq button code" is "BUTTON_NONE" and sometimes it's the same as the "button code" 13.38.42 Quit maruk (Quit: Leaving.) 13.40.33 # and I don't understand "BUTTON_REL" either. "Button release"?" 13.45.49 # yes, button release. If you have an action on a long press of a button (with BUTTON_REPEAT) and one for a short press of the same button you have to make sure that a long press doesn't trigger both 13.45.56 # that's what it is used for 13.48.01 # ok 13.48.07 # I forgot the details a bit though :\ 13.48.38 # the prereq button code is still unclear to me though 13.52.23 # "if there's no need to check the previous button's value, use BUTTON_NONE" 13.52.31 # that should help me to understand 13.53.50 Join B4gder [0] (~daniel@205.164.11.246) 13.53.51 Quit B4gder (Changing host) 13.53.51 Join B4gder [241] (~daniel@rockbox/developer/bagder) 13.56.56 # { ACTION_WPS_PLAY, BUTTON_POWER|BUTTON_REL, BUTTON_POWER } -> here I understand that first button_power needs to be check to know if it's on play or pause status. 13.56.57 # { ACTION_WPS_SKIPNEXT, BUTTON_RIGHT|BUTTON_REL, BUTTON_RIGHT } -> But here I don't understand why it's needed. Why not BUTTON_NONE? 13.57.43 # <[Saint]> fastforward, sweetie. :) 13.58.05 # <[Saint]> need to check if its a skip or a seek. 14.00.15 # there probably is an action with BUTTON_RIGHT|BUTTON_REPEAT - as [Saint] says probably seek forward 14.00.43 # there is " { ACTION_WPS_SEEKFWD, BUTTON_RIGHT|BUTTON_REPEAT, BUTTON_NONE } 14.00.51 # but why this one doesn't need to check then? 14.06.19 # there are also some inconsistencies in the code, I remember them too. I'm not sure but the latter is probably correct whether you have BUTTON_NONE or BUTTON_RIGHT as prerequisite or not. The first is necessary so that you don't skip forward if you release the button after seeking, I believe - so in this case necessary. Unfortunately my memories are a bit blurry about this now 14.08.04 # I don't remember either, I think you can put BUTTON_NONE or BUTTON_RIGHT in the case of a repea 14.08.05 # t 14.10.00 Quit akaWolf (Ping timeout: 272 seconds) 14.10.10 # so basically the rule of dumb is: 14.10.10 # 1) want some action on release of X -> { ACTION_xxxx, BUTTON_X | BUTTON_REL, BUTTON_X} 14.10.10 # 2) want some action on repeat of X -> { ACTION_xxx, BUTTON_X | BUTTON_REPEAT, BUTTON_NONE} 14.10.10 DBUG Enqueued KICK pamaury 14.10.10 # 3) want some action on press of X -> {ACTION_xxx, BUTTON_X, BUTTON_NONE} 14.10.11 # <[Saint]> button_right/left needs to be the prereq for seeking, no? 14.12.45 # well, if you are already detect the button repeat, the button must have been pressed before, no? I think that's implicit 14.12.57 # *detecting 14.14.48 # lebellium: just inspire from the other keymaps and everything should go well :) 14.15.19 # <[Saint]> and when inspiration fails, c/p. 14.15.43 # <[Saint]> (cut and paste...not the other kind, that'll get you arrested) 14.17.46 # pamaury: I am here now if you could help me with that zen x-fi. 14.18.38 # MarcAndersen: about the zen x-fi, you will need voice files I guess but I don't know how to generate them 14.19.13 # <[Saint]> RbUtil can do it. 14.19.47 # is there a dev build of rbutil which contains the x-fi? 14.19.51 # can it for unusable targets ? 14.19.58 Join Narod [0] (~Narod@p5DDDB7A5.dip0.t-ipconnect.de) 14.20.39 # <[Saint]> I was under the understanding it didn't need to take target staus into account and just looked for the lang files on the device. 14.20.48 # <[Saint]> *status 14.21.16 # oh, maybe. that would be so cool 14.22.44 # <[Saint]> pamaury: it definitely can for the Classic, but that was added as a special case. 14.23.04 # ok, let me try with my zen x-fi and dev build of rbutil 14.23.10 # <[Saint]> To do so I think one might have to lie to RbUtil a little and say its another device in order to give it a mountpoint to work with. 14.24.08 # maybe this is a stupid question, but why do you call the x-fi unusable when it can run rockbox? 14.24.10 # hum, actually I think RbUtil doesn't even know about the zen x-fi yet 14.24.48 # MarcAndersen: we have three status for targets: stable, unstable and unusable. Targets usually start in unusable 14.25.37 # ok 14.26.27 # <[Saint]> It basically means "Hey, normal users - don't use this unless you know exactly what you're doing, or are doing so under supervision" 14.27.10 # <[Saint]> A slightly veiled way of saying "You might possibly have a very bad time using this" 14.27.34 # MarcAndersen: for now there are two majors issues: you cannot really dual-boot, and you cannot charge (you need to use recovery mode to charge) 14.27.47 # and you will loose all your files currently on the device 14.27.56 # <[Saint]> pamaury: is there frequency scaling yet? 14.28.13 # no, so battery life is probably not great either 14.28.20 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 14.28.20 # * [Saint] nods 14.28.39 # <[Saint]> I recalled tht being an issue, but I've missed a bit of recent development. 14.28.51 # my x-fi is already empty 14.29.11 # it works on imx233/stmp3780 but not on stmp3700 yet, I just need to do the work 14.29.31 # [Saint]: so you say I should trick Rockbox Utility into thinking it's another device ? 14.29.39 # which chip does the x-fi use? 14.30.02 # <[Saint]> pamaury: assuming it works the way I think it does, that should suffice yes. 14.30.18 # MarcAndersen: stmp3700 14.30.37 # <[Saint]> I don't think it cares about the device, but you need to specify a device type to give it a mountpoint iirc. 14.31.12 # ok. should we try to install the bootloader on mine? 14.32.08 # just trying the voice files first, give me a minute 14.32.21 # pamaury: sure 14.33.08 # I have selected sansa e200, creating voice files...let's see if it works 14.34.46 Join cmhobbs [0] (~cmhobbs@fsf/member/cmhobbs) 14.35.50 # [Saint]: I created the voice files but now it won't let me install them, claiming the rockbox on my device is a development version 14.36.34 # <[Saint]> Oh. Crap. Well, that was unexpected. Do they sit in the cache? 14.38.09 # cannot find them, strange 14.38.23 Join amayer [0] (~amayer@mail.weberadvertising.com) 14.38.45 Join amayer_ [0] (~amayer@mail.weberadvertising.com) 14.39.06 # bluebrother: here ? 14.39.16 # let's ask our RbUtil expert 14.39.40 # ah wait 14.39.45 # in fact it installed them 14.40.09 # so "create voice files" actually mean "create and install voice files", nice to know 14.40.20 # <[Saint]> Possibly-premature-Huzzah! 14.40.21 # pamaury: ok I successfully changed the keymap. Only the volume in SBS doesn't work I don't know why. Maybe because of "#ifdef HAVE_VOLUME_IN_LIST" ? 14.40.50 # MarcAndersen: ok it works :) 14.41.02 # pamaury: great! 14.41.04 # <[Saint]> Actual-Huzzah! 14.41.37 # <[Saint]> I was fairly certain I had used the "trick RbUtil" method before, but not certain enough to say "this will definitely work" 14.41.50 # <[Saint]> Its nice when ones memory isn't wrong for a change. 14.42.01 # however I don't know it does voice files and directories, maybe you know that ? 14.42.09 # *I don't know how it 14.43.10 # That's no problem. I just need to get rockbox installed, the voice stuff I should be able to work out 14.43.16 # for directories and file names there should be "create talk clips" or somesuch. There's also the option to have them spelled out which works if you have a voice file installed 14.43.19 # <[Saint]> isn't there a "create .talk clips" thing in accessibility section? 14.43.28 # <[Saint]> Or am I parsing the question incorrectly? 14.43.31 Quit amayer (Quit: Leaving) 14.44.02 # ah yes 14.44.02 # ok, let's go then ^^ 14.44.03 # MarcAndersen: are you using Windows ? 14.44.35 # pamaury: if we need to use rbutil, then yes because that is not accessible on anything else 14.44.48 # <[Saint]> that's untrue. 14.45.11 Join akaWolf [0] (~akaWolf@unaffiliated/akawolf) 14.45.13 # <[Saint]> It runs on all major flavors. 14.45.45 # <[Saint]> ... 14.45.50 # sorry, i mean for screen reader users, we call that as being accessible, sorry. 14.45.57 # <[Saint]> Suddenly I get the sense I parsed that incorrectly. 14.46.04 # <[Saint]> Ah. 14.46.54 # Note to self: don't mention to SanDisk tech support that you're using a SanDisk microsdxc card with a SanDisk DAP that doesn't officially support it. 14.47.36 # <[Saint]> ...because they might want to know how, and then tell you to GTFO when they find out? :) 14.47.43 # at some point, running Rockbox becomes "obvious" and "normal" 14.47.47 # I think the Utility is supposed to be accessible on all systems but doesn't work the same with the different screen readers 14.47.59 # [Saint]: I got off easy, they only told me that I shouldn't do it :D 14.48.30 # <[Saint]> Remind them of the pitch bug, say they owe you. 14.48.36 # <[Saint]> :) 14.48.38 # lol 14.49.24 # pamaury: can you have a look at https://www.dropbox.com/s/53u3qgqqq8o7xvr/keymap-nwz.c :) 14.50.07 # MarcAndersen: you need to download three files: https://www.dropbox.com/s/zh6h6oetw85zog0/firmware-zenxfi.nk 14.50.25 # https://www.dropbox.com/s/9vwc4qdyh0c6e0p/sendfirm.exe and https://www.dropbox.com/s/t96injmo9d2jhgt/MTP_DLL.dll 14.51.17 # lebellium: thanks, I'm going to check that, can you briefly explain what you did/change/add ? 14.54.11 # pamaury: got them. 14.54.23 # play/pause > play button instead of power. Short press on power: quickscreen (added). Long press on power: context menu (changed). Short press on back: browse (changed). Long press on back: home menu (changed). Volume up/down: up/down + volume up/down (added). But volume doesn't work in SBS I don't know why. 14.55.14 # MarcAndersen: now you need to enter recovery mode on the zen x-fi. The only bulletproof way to do that is to use a paper clip/pen to press the reset button, then hold the play button and slide the power button (while holding player) 14.56.17 # pamaury: you should check if it works with E370 too since this one has no volume buttons 14.57.23 # lebellium: what do you mean by volume doesn't work in SBS ? 14.57.28 # you mean in WPS ? 14.57.32 # no 14.58.10 # in WPS it works but in SBS it doesn't work, maybe because you did not define: HAVE_VOLUME_IN_LIST 14.58.15 # <[Saint]> That's only for targets with dedicated volume keys (ones that don't chare any other action) or touchscreens. 14.58.23 # <[Saint]> *share 14.58.36 # we know that [Saint] :) 14.59.13 # Didn't I define HAVE_VOLUME_IN_LIST for the E360 ? Pretty bad overlook 14.59.28 # I used the same keymap as for Fuze+ (also has dedicated volume buttons) so since it doesn't work, it's probably because of the lack of HAVE VOLUME 14.59.36 # <[Saint]> I thought lebellium said he tried enabling that, my mistake. 14.59.44 # <[Saint]> No, it won't work without that defined. 14.59.53 # <[Saint]> Nor should it. 15.00.06 # I don't see it here pamaury http://git.rockbox.org/?p=rockbox.git;a=blob;f=firmware/export/config/sonynwze360.h 15.00.17 # indeed one needs to be care with keymap-nwz because it handles both E360 and E370 which has not dedicated volume keys; ok sorry for that 15.01.00 # I don't know if a conditional is used or if the E370 will simply skip my decicated volume buttons-related lines 15.01.06 # you should double check 15.01.16 Quit cmhobbs (Ping timeout: 246 seconds) 15.01.17 # you have to use a conditional because it will not compile on E370 15.02.01 # pamaury: how do i know if it's in recovery? 15.03.15 # ah indeed "/home/ubuntu/rockbox/apps/keymaps/keymap-nwz.c:68: error: ‘BUTTON_VOL_UP’ undeclared here (not in a function)". So I let you add the conditionnal before commiting the new keymap^^ 15.05.39 # MarcAndersen: well, you cannot tell for sure unfortunately 15.05.56 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 15.06.18 # i first pressed reset, then held play while sliding power, correct? 15.06.26 # yes 15.06.34 # i've done that now 15.08.12 # ok assuming you are in recovery mode, it is a menu with four options: Clean Up, Format All, Reload Firmware, Reboot. So you need to press down three time, press select, it will ask you for confirmation, press up once to go to Yes and then press select 15.08.49 # It usually takes a few seconds to erase firmware and then you are back to the menu. At which point you can connect it your computer 15.09.19 # isn't it 2 times, or does it start above the first option? 15.09.26 # yeah sorry 15.09.37 # ok, doing it now... 15.11.51 # actually it is not entirely true, there is one way to distinguish between recovery mode and OF: if you plug the device in OF, it will give you a proper disk with 4/8/16 GB storage, whereas if you plug in recovery mode, it will not show up as a disk or as a very small disk (~60MB) 15.12.14 # i connected it, and there is a creative zen x-fi under portable devices in device anagement 15.12.17 # but you'll agree that's not a very convenience way... 15.13.11 # ok, now make sure the sendfirm.exe and MTP_DLL.dll files are in the same directory. You need to use the command line promp (cmd.exe), and run "sendfirm.exe firmware-zenxfi.nk" 15.13.24 # yes! it is 60 mb! 15.13.48 # perfect ! I wasn't sure Windows would display this information but apparently it does 15.14.34 # but it is not a drive letter, it is still a portable player 15.14.43 # should i still do it? 15.14.50 # yes, that's normal in recovery mode 15.14.59 # ok, doing it now 15.15.50 # Upload will take as long as one minute, if I remember correctly the windows tools has a progress indicator but it shows unreliable figures 15.16.40 # Once it is uploaded (sendfirm.exe might report an error but ignore it), it will take possibility a few minutes to upgrade on the player itself and then it should reboot by itself and show up as a mass storage device if everything went well 15.16.49 Quit kevku (Ping timeout: 245 seconds) 15.17.43 # If after a few minutes nothing seem to happen, press reset; sometimes booting into rockbox from the recovery mode in unreliable 15.18.31 # wow! it comes up asking if i want to format the disk 15.18.50 # perfect, you should say yes 15.19.06 # make sure to use FAT and not NTFS 15.19.14 # (if you have a choice) 15.19.21 # fat32 or exfat? 15.19.36 # fat32 15.20.16 # what about the sector size or what it's called in english, it is on 4096 byte, is that ok? 15.20.54 # that must be cluster size, the default value should do, it's not crucial 15.21.32 # now it's formatting 15.22.32 # i made a full format, it takes some time 15.27.01 # it's going to take about 20 minutes 15.33.57 *** Saving seen data "./dancer.seen" 15.45.56 # ok, it's finally done. what now? 15.47.32 # now you need to install a nightly build of rockbox: download http://build.rockbox.org/data/rockbox-creativezenxfi.zip 15.47.46 # and unpack it at the root of the drive 15.48.27 # if later you want to upgrade rockbox, you just need to redownload and unpack it again, you don't need to change the bootloader (or only very rarely when we release new bootloader versions) 15.49.36 # i have unpacked it 15.50.10 # you should have a folder called ".rockbox" at the root of the drive now, correct ? 15.50.17 # yes 15.50.18 # <[Saint]> probably best to avoid updating if voice strings are going to change, no? 15.50.37 # <[Saint]> At least until there's official support (without trickery) for this device in RbUtil. 15.50.55 # voice strings don't change very often anyway, but yeah it's safer to recreate them on update 15.51.25 # MarcAndersen: now you need to download Rockbox Utility, the latest stable version should do 15.51.42 # and create voice files for the e200? 15.52.53 Part LinusN 15.53.11 # yes, in the UI select any stable device like the e200, select the correct mount point and in the "accessibility" panel, press create the voices 16.01.32 # the voice has been created, and is 2112 kb 16.03.25 # should i disconnect the player? 16.03.37 # yes 16.05.30 # it didn't say anything after i disconnected it 16.05.57 # the speaker is not hanled, you need to use the headphones 16.06.00 # *handled 16.06.17 # will it be at some time? 16.06.43 # guess what, it speaks! yeeeeees! 16.07.16 # yes it will, since speaker is low priority (rather poor quality) I haven't done the work to support it yet. Good :) 16.08.07 # and you said i couldn't charge it in rockbox, how do i then get to and from charging mode? 16.08.40 # you charge, enter the recovery mode: shut down rockbox, hold play and power on, then plug usb 16.08.46 # *to charge 16.08.59 # <[Saint]> Ohhhh - that's nasty. 16.09.10 # be sure to plug usb *after* power on, you cannot enter recovery mode if usb is plugged 16.09.25 # and how do i get back to rockbox? 16.09.26 # * [Saint] stops typing a variant of the above. 16.09.42 # unplug and power off (slide power of a few seconds) 16.09.48 # then power on normally 16.10.04 # charging is definitely the most outstanding issue at the moment 16.10.17 # <[Saint]> Does the unit charge while powered down? 16.10.22 # no 16.10.22 # <[Saint]> (I know some do) 16.10.29 # <[Saint]> AH, bummer. 16.11.24 # wow! do you know when you will make the speaker? what was my biggest reason of moving from my clip zip 16.11.30 # that was* 16.11.31 # MarcAndersen: just one very important detail, charging is not implemented and battery readout is not calibrated so I advise you recharge regularly just in case, because if you reach a very low battery level, you might not be able to enter recovery mode easily 16.11.59 # hum, I can have a look at it tonight, in theory it is easy to add 16.12.30 # anyway, will it require a new bootloader? 16.12.41 # no 16.12.49 # ok. nice. 16.21.02 # i just shut it down and now it will not start up again 16.22.03 Quit fs-bluebot (Ping timeout: 245 seconds) 16.23.24 Join fs-bluebot [0] (~fs-bluebo@g231120185.adsl.alicedsl.de) 16.24.08 # MarcAndersen: try reset ? 16.25.38 # that worked, i'm so stupid 16.26.36 # I noticed that after booting from recovery mode, strange thing happen. In normal circumstances though, nothing start strange should happen. else reset is your friend ^^ 16.32.01 Quit Marex_ (Ping timeout: 264 seconds) 16.32.29 Join Marex [0] (~Marex@195.140.253.167) 16.38.20 Join kevku [0] (~kevku@2001:470:27:773:0:feed:c0f:fee) 16.38.27 Quit Marex (Ping timeout: 246 seconds) 16.39.44 # is it correct that the zen x-fi is in recovery and charging when there is a creative zen x-fi under portable devices? 16.39.53 Join Marex [0] (~Marex@195.140.253.167) 16.40.57 # MarcAndersen: yes 16.41.47 # pamaury: thanks for all your help! i am so happy that I didn't sell my x-fi 16.43.21 # you're welcome, thanks for trying :) 16.43.42 # oh, will the charge thing require a new bootloader? 16.53.05 Join mortalis|2 [0] (~kvirc@213.33.220.118) 16.53.06 Quit mortalis (Read error: Connection reset by peer) 16.55.22 Quit amayer_ (Quit: Leaving) 17.02.38 # MarcAndersen: only to charge in the bootloader, but not to charge in rockbox itself 17.02.38 # so eventually yes, but in the short term 17.03.18 # ok 17.04.06 Join amayer [0] (~amayer@mail.weberadvertising.com) 17.18.42 Join ikeboy [0] (~ikeboy@ool-435622d3.dyn.optonline.net) 17.24.41 Quit petur (Quit: Page closed) 17.30.22 Quit B4gder (Quit: It is time to say moo) 17.33.58 *** Saving seen data "./dancer.seen" 17.35.22 Join Szczepancio [0] (~Szczepanc@acfq169.neoplus.adsl.tpnet.pl) 17.35.51 # pamaury: how to install bootloader into e380? 17.36.05 # pamaury: it's having .sb file format 17.37.51 Quit Szczepancio (Client Quit) 17.50.03 Join Szczepancio [0] (~Szczepanc@acfq169.neoplus.adsl.tpnet.pl) 17.50.07 # Ok, i'm here :> 17.53.38 # Szczepancio: boot into the OF, put it at the root of the internal storage, make sure it is named firmware.sb, eject properly and reboot 17.53.45 Quit Guest17648 (Read error: Connection reset by peer) 17.53.53 # pamaury: thankls 17.53.59 # OF is recovery mode? 17.54.27 Quit mortalis|2 (Ping timeout: 248 seconds) 17.54.41 # OF is the original (sony) firmware 17.55.21 Join Guest17648 [0] (~husvagn@90-230-140-28-no41.tbcn.telia.com) 17.55.29 # Ah, thank's. 17.55.31 # Nice name 17.55.55 # yeah, strong habit, writing original firmware is too long ^^ 17.59.59 Quit Guest17648 (Read error: Connection reset by peer) 18.00.00 Quit ikeboy (Quit: ikeboy) 18.00.22 # pamaury: It's running, woo hoo. 18.00.40 # are the buttons working as expected ? 18.00.59 # like is up actually up and so on or they seem mixed up ? 18.01.33 # They arent mixed up. 18.01.55 Join Guest17648 [0] (~husvagn@90-230-140-28-no41.tbcn.telia.com) 18.02.27 # But why there are any games and so? 18.02.28 Join pretty_function [0] (~sigBART@123.252.213.171) 18.02.49 # is sound working ? 18.02.53 # It's early port, so no games/apps implemented for this hardware (resolution, procesor, etc.)? 18.03.13 # I haven't written the keymaps for the games, so they are disabled 18.03.27 # sound is working 18.03.29 # Stupid but very practical reason :-/ 18.03.52 # Colors are other than at sansa clip. 18.03.53 # ok, can you check backlight: go into settings and try the different backlight values 18.04.54 # they are working 18.05.32 # ok, last check: can you go into debug menu > fm tuner or fm registers, don't remember how its called 18.06.04 # fm radio 18.06.18 # HW detected: yes 18.06.21 # right, what does it display ? 18.06.23 # STRFM1000 regs: 18.06.30 # chipid: 0x12 18.07.13 # rebranded player bouuuh :) 18.08.05 # ok thanks, so it's indeed STFM1000, TB2 to be precise 18.08.14 # the radio was the only point I was not sure about 18.08.21 # so it's really the same player 18.08.24 # pamaury: Understood. 18.08.51 # pamaury: does that mean that it should be possible to install the E380 firmware on E370 to get the AAC support? 18.09.45 # lebellium: yes, with some little trick about firmware version though 18.10.22 # Szczepancio: great thanks, if you want to restore the OF for your dad, it is a very similar procedure: download https://www.dropbox.com/s/ph4a0uaf8pjvgsw/sonynwze380_1.0.0.firmware.sb, boot into OF (power down and then press back for one second), put this file at the root of the player (name it firmware.sb), reboot into OF once again 18.11.15 # lebellium: because on the E370, there are two versions of the OF: 1.0.0 and 1.0.1, and the OF checks version on upgrade. On the E380 it is 1.0.0 so to upgrade 1.0.1 E370 to E380, you need to change the version number 18.11.32 # (assuming Sony didn't put any more checks) 18.11.51 # downgrade is not possible then? 18.11.52 # pamaury: No problem, you don't really must thank's, I must thank's for you :) 18.11.53 # At least I'm sure I will never buy the E380 now :) 18.12.14 # pamaury: Because it's the same hardware, yep? 18.12.15 # :D 18.12.34 # pamaury: I am still waiting a hack for a e470, u know. 18.12.47 # lebellium: not without modifying the version number. That's just a number, it is not related with the actual code. That is you can repack firmware 1.0.0 with version 1.0.1, it is still 1.0.0 but it pretends to be 1.0.1 for the upgrade 18.13.11 # <[Saint]> Szczepancio: Now, if only waiting for things worked - you'd be set! 18.13.14 # <[Saint]> :) 18.13.49 # pamaury: and how can you do that? hex-edit the firmware.sb file? 18.14.26 # lebellium: it is a bit more complicated that hex-edit but it's the same idea 18.14.41 # We my tools, it's actually pretty trivial to do so 18.15.12 # I can write you the instructions somewhere if you want to try, assuming you can compile things from the repository 18.15.18 # [Saint]: You mean waiting is the best thing i can do? My english is just awful. 18.16.13 # pamaury: no no, it was just by curiosity :) 18.17.38 # <[Saint]> Szczepancio: No, I mean waiting is entirely unprofitable when you want something to happen, it has no bearing on it happening or not. 18.18.16 # <[Saint]> Best is to get stuck in to it yourself up to your elbows, because someone who wants something badly enough is the ebst person to implement it. :) 18.18.24 # <[Saint]> *the best 18.18.56 # [Saint]: So, the best thing I can to do it myself? 18.18.58 # assuming we can all do what pamaury does. I'll get stuck to waiting :) 18.19.23 # But, i think like lebellium, so, yes, we are waiting for pamaury :D 18.19.57 # <[Saint]> Well, although it makes a fun tale to believe so - pamaury wasn't borm with superhuman reverse engineering powers. :) 18.20.04 # <[Saint]> *born 18.20.19 # <[Saint]> He learned, we can too. 18.20.30 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 18.20.49 # [Saint]: I got it :0 18.20.53 # :) 18.21.21 # <[Saint]> ...though, there is a chance pamaury reverse engineered *himself*, in order to be better at reverse engineering. 18.21.28 # <[Saint]> ;) 18.21.47 # <[Saint]> The Patron Saint of RE. 18.22.39 # I'm sure there are other people as good if not better than me at RE, I'm just crazy enough to try and succeed 18.22.56 # Do you know the global division of labour theory by Ricardo [Saint] ? That's how I think. Why would I do the same thing as pamaury if he can do it much better and faster than I do. I would rather do something I'm better than him, for example themeing (not even sure about that though^^). 18.23.29 # lebellium: I will never, ever, theme rockbox, not even under torture :D 18.23.51 # <[Saint]> I don't necessarily think about it being a "better at" or "worse at" thing. 18.24.00 # <[Saint]> I just think of it as doing something you enjoy. 18.24.53 # <[Saint]> If people thought that way you descibed all the time, there wouldn't ever be any advancement. 18.25.58 # When I started, I thought the people writing rockbox and doing RE were some kind of dark sorcerer with supernatural knowledge ^^ 18.26.09 # <[Saint]> Yep. 18.27.26 # took me two years to do the Fuze+ port but now I can do many ports way faster :D I knew a lot of things about computer already, admitted 18.29.54 Join n1s [0] (~n1s@130.243.168.30) 18.29.54 Quit n1s (Changing host) 18.29.54 Join n1s [0] (~n1s@rockbox/developer/n1s) 18.32.33 # Hum I forgot you had a Zen V (Plus) pamaury. You haven't done anything on these ones right? 18.33.17 # lebellium: yes I did, but it's stmp3600 based and the current stmp3600 is broken (even though it used to work), I promised lorenzo I would have a look at it 18.33.31 # I have the Sansa Express on my list too 18.33.41 # I wanted to commit stmp3700 work before 18.33.52 # and solve major issues like charging 18.34.19 # <[Saint]> ...will we get a network stack then? :P 18.35.35 # not sure about this ^^ The X-Fi is the only player I know with Wifi and only the most expensive 16GB have one 18.35.44 # (mine has :p) 18.36.16 # if someone wants to port some IP/TCP stack why not, I'm not sure what to do with it though 18.36.37 # I will *not* port Firefox to rockbox ! 18.36.42 # pamaury: Can I help you with keymaps for e370/e380? 18.36.53 # Firefox at rockbox, lol. 18.36.59 # Net over usb? Non-sense. 18.37.04 # <[Saint]> I guess porting IwIP is feasible. 18.37.05 # Szczepancio: you should see that with lebellium, he is the new keymap expert 18.37.13 # lol 18.37.30 # Ahh, i didn't saw, net over wifi. Nice. 18.37.35 # [Saint]: yeah I think so. However one needs to reverse the wifi driver first, I couldn't find any documentation about the chip 18.37.45 # * [Saint] nods 18.37.58 # <[Saint]> *LwIP 18.38.04 # pamaury: I'm not sure how to add the conditionnal for E370. I would prefer if you do it (since anyway I can't commit anything myself) 18.38.08 # <[Saint]> stoopid letters, all close together and stuff. 18.38.30 # it is some bcm chips, probably with some custom firmware like bcm always do 18.38.30 # lebellium: wait a second, I will upload an example 18.40.06 # pamaury: and there are other players with Wifi such as Zune HD, Sony X1050 etc :) 18.40.19 # lebellium: https://gist.github.com/pamaury/7453149 18.40.35 Join bertrik [0] (~quassel@ip117-49-211-87.adsl2.static.versatel.nl) 18.40.36 Quit bertrik (Changing host) 18.40.36 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 18.41.06 # notice that the volume in list I keep the HAVE_VOLUME_IN_LIST conditional and in WPS I test to see if there is a Volume UP button defined 18.41.16 # * [Saint] thinks there shouldn't be a Zune port on principle alone. 18.41.29 # a yes, but I'm not sure if we know how to run code on the Zune HD 18.41.50 # and isn't X1050 Android based ? 18.42.08 # <[Saint]> I believe so. 18.42.24 # no 18.43.02 # what is the SoC inside this ? 18.43.04 # <[Saint]> Then they went to great lengths to gie the impression it was. 18.43.15 # <[Saint]> The UI is quite Android-esque. 18.43.23 # <[Saint]> *give 18.43.24 # you mix up with the android-based Z1000 18.43.34 # the X1050 was released in 2009 18.43.40 # it has wifi but no android 18.43.56 # competitor to the Cowon S9 and Samsung YP-P3 back to the time 18.44.28 # <[Saint]> Hmmmm. Looking at images of it, I can definitely see why I thought it was Android based. 18.45.02 # <[Saint]> Damn Sony, you make some *ugly* DAPs. 18.45.20 # pamaury: ok interesting! you took my file as basis right? So i'll try to compile with your now 18.45.28 # yours* 18.45.43 # lebellium: yes, it's your file 18.45.52 # the X1050 is linux based, it is in the Sony open source center 18.46.08 # chances are that it's the same soc as other sony players 18.46.26 # Szczepancio: I can compile a E370 build with my improved keymapping if you want 18.46.50 # pamaury: How much I will wait for e470 port? I can change a e380 for e470, but I really prefer e470. 18.47.06 # Szczepancio: no idea, I cannot tell 18.47.13 # <[Saint]> With ports, always assume "anywhere between now and never" 18.47.25 # <[Saint]> and its much safer to assume never. 18.47.31 # I don't wanna to be urgent, u know. 18.47.43 # lebellium: Can you compile it with plugins? 18.47.53 # No 18.47.59 # <[Saint]> ...not without hours of work first. 18.48.10 # pamaury disabled them and explained to you why, I don't know how to enable them 18.48.44 # you cannot enable them, they just don't compile right now, you need to write the keymap 18.49.30 # I can explain you how to enable compilation of them and compile and then you'll need to go through each of them. It's rather tedious but I would appreciate it a lot 18.50.31 # pamaury: I must write keymap's for the apps? 18.50.33 # not sure I have the courage to do that now. Maybe later :) 18.50.38 # Or just compile? 18.50.48 # if you want them yes 18.50.49 # define the keymap for each plugin yes 18.50.51 # Ahh, I understood. 18.51.07 # it is very tedious as there are many plugins 18.51.09 # Compile, and next test it and write keymaps for it, and next compile, test it, etc. 18.52.47 # yes, unfortunately there is not way (afaik) to disable some plugins easily, it's either all or none 18.52.58 # except if you compile them yourself one by one 18.54.20 # Off topic, but wasn't there a unified key map structure thingy in the works at one time? 18.54.29 # Szczepancio: you can try this build with improved keymapping: https://www.dropbox.com/s/a5cnex3a31v980u/rockbox_NWZ-E370_131113.zip 18.54.39 # Still parts left here and there 18.55.35 # Instead of adding more and more "#ifdefine"s for every new port. It will one day get out of hand 18.56.10 # there are pluginlib actions but those only work (and were limited again to this later on) to plugins that only need basic actions like directional keys, menu, select 18.56.19 # <[Saint]> ...wouldn;t a unified keymap just be a giant clusterfuck of ifdeffs, though? :) 18.56.52 # <[Saint]> seems like avoiding a problem by simply amassing it all in one hideous space. 18.57.03 # Yeah but only one collective cluster fuck in one file, manageable from one place 18.57.13 # <[Saint]> "manageable" 18.57.41 # not manageable due to major differences in keymaps -> "fix one, break others" 18.57.43 # it's unsolvable: for basic action pluginlib is good but some plugins requires complex combo because of the lack of buttons 18.57.55 # and because of the physical layout of the keys 18.58.11 # * foolsh nods 18.58.12 Join thegeek_ [0] (~thegeek@60.36.34.95.customer.cdi.no) 18.58.25 # <[Saint]> If you think you can make a single unified keymap that is "manageable"...go for it. 18.58.27 # if you play doom for example, some configurations might make sense but just don't fit well the physical layout of some players 18.58.36 # <[Saint]> But I rather suspect you'll eventually give up. 18.58.42 # <[Saint]> ...or go insane. 18.58.46 # someone tried and gave up iric 18.58.47 # *iirc 18.59.14 # though some plugins might be converted to pluginlib because they were written before it, maybe 18.59.23 # like battery bench 19.01.38 Quit thegeek (Ping timeout: 245 seconds) 19.01.57 # no, someone even started but went back to the basic action approach, because there were some plugins converted and partially broken for some players (I remember metronome) with the fix being "introduce more and more exceptions and more contexts with the result of having the same thing as before but even harder to read" 19.02.14 # *we went back 19.05.24 Quit lebellium (Ping timeout: 272 seconds) 19.05.27 Join lebellium_ [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 19.05.38 Nick lebellium_ is now known as lebellium (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 19.07.39 Join mortalis|2 [0] (~kvirc@213.33.220.118) 19.10.31 Quit lebellium (Ping timeout: 245 seconds) 19.16.10 Join lebellium [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 19.22.38 Quit krabador (Ping timeout: 260 seconds) 19.30.22 Join krabador [0] (~krabador_@unaffiliated/krabador) 19.34.00 *** Saving seen data "./dancer.seen" 19.36.23 Join y4n [0] (~y4n@unaffiliated/y4ndexx) 19.37.06 Quit krabador (Ping timeout: 260 seconds) 19.46.12 Quit Guest17648 (Quit: Hmmm...) 19.48.03 Quit akaWolf (Ping timeout: 248 seconds) 19.48.35 Join Guest17648 [0] (~husvagn@90-230-140-28-no41.tbcn.telia.com) 20.07.16 Join krabador [0] (~krabador_@unaffiliated/krabador) 20.07.37 Join cereal_killer [0] (b2be067a@gateway/web/freenode/ip.178.190.6.122) 20.10.11 Quit rela (Quit: Leaving) 20.10.12 Quit pretty_function (Remote host closed the connection) 20.10.34 Join rela [0] (~x@pdpc/supporter/active/rela) 20.10.39 Join pretty_function [0] (~sigBART@123.252.213.171) 20.10.44 # [Saint]: Congratulations to your 256GB iPod Video. May I ask which SSD you use and which guide you followed, to install the SSD? I want to replace the HD of my rockboxed iPod too. 20.13.20 Nick DormantBrain is now known as SuperBrainAk (~andy@74.112.200.73) 20.14.07 # will there be a windows simulator for the zen x-fi on the rasher site at some point? 20.15.06 Quit pretty_function (Ping timeout: 246 seconds) 20.16.51 # <[Saint]> cereal_killer: 240GB 40pin ZIF SSD someone left at my local hackerspace that I kind-of-sort-of manage, sometimes. 20.17.05 # <[Saint]> Renixe? Renice? ...something like this. 20.17.11 # <[Saint]> Renice. 20.17.14 # MarcAndersen: the simulator compiles so I guess it's a matter of asking rasher 20.17.46 # IIRC, it doesn't compile with mingw 20.17.47 # <[Saint]> cereal_killer: its certainly not something I would *buy*...heck no. Those mothers are *expensive* 20.17.48 # I don't know how rasher generates those simulators 20.17.53 # rasher: really ?! 20.18.08 # do you the compile log ? 20.18.12 # *do you have 20.18.13 # Well, I'm not sure of the model, but a bunch of them don't compile 20.18.17 # sadly no 20.18.25 # I did pastebin some manual runs 20.18.31 # <[Saint]> gigabeat and...shit, somethinng. 20.18.32 # rasher: that's the Fuze+/Ondia/Gigabeat no? 20.18.40 # <[Saint]> Two of the targets in the list at the bottom. 20.18.42 # shrug 20.19.04 # I'm guessing it's all of the missing ones - probably the same problem too 20.19.05 # Lucky you. And did you have to format it first, or did you just put it into the iPod and let iTunes restore it? 20.19.13 # <[Saint]> cereal_killer: as for which guide I followed, I didn't. Its a straight replacement. 20.19.23 # <[Saint]> iTunes restore. 20.19.29 # the Zen X-Fi should be added to a file as it's still a unusable target (like we did for Zen X-fi 2/3) 20.19.39 # but I don't remember which file 20.19.47 # Hm, looks like the pastebin is gone 20.20.13 # I think there is a windows sim for the x-fi 2 and 3 but not the original x-fi 20.20.25 # MarcAndersen: yes 20.20.38 # because we added the X-Fi2/3 to the necessary file 20.20.58 # they are also unusable, right? 20.21.03 # yes 20.21.29 # why doesn't the x-fi simulator compile with mingw then? 20.21.37 # I'm not sure it doesn't 20.21.38 # maybe it does 20.21.39 # thank you for the information [Saint], and how about the fitting? Did you need some padding with foam, or changed the backplate? 20.21.51 # rasher talks about the Fuze+/Onda/Gigabeat 20.21.59 # not about the X-Fi I think 20.22.02 # tools/release/sims.pl is the file to add unusable targets, that can compile the sim 20.22.12 # ah! 20.22.15 # oh sorry. so the x-fi windows sim will be made at some point? 20.22.17 # that's the one I was looking for 20.22.42 Nick Mir_ is now known as Mir (~Mir@pool-71-109-219-225.lsanca.dsl-w.verizon.net) 20.22.50 # rasher: so we just need to add the X-Fi there :) 20.22.57 # Probably 20.23.15 Join cela [0] (5770ee53@gateway/web/freenode/ip.87.112.238.83) 20.23.17 # <[Saint]> cereal_killer: the IO isn't as great as I would've expected (~100MB/s read, ~80MB/s write), but it beats the pants off the original disc. As for the sizing, I stole the foam padding from an old 4G ipod and cut it up and stuffed it in the back of the "fat" Video case. 20.23.28 # <[Saint]> (I didn;t have a spare "thin" case backing) 20.23.42 # <[Saint]> But you reminded me I should order one. :) 20.24.33 # pamaury: you can add the new creative targets there and it should be enough for the rasher website :) 20.24.39 # pamaury: Do you know how to shutdown e370? 20.24.47 # Option button don't work, only lock it. 20.25.02 # Szczepancio: did you try my build? 20.25.13 # lebellium: w8 20.25.24 # ? 20.25.38 # Just been trying out the X-Fi port, Anyone getting a display issue? Mine goes white after a few minutes of use. 20.26.04 # yes, a thin backplate is a good idea, but the headphone jack does not fit then, right? 20.26.20 # Szczepancio: press "power" button for a few seconds 20.26.52 # cela: you mean when backlight shut down ? 20.27.08 # lebellium: ok i'll do 20.27.51 # Yes if you press a button to wake up the display after a few minutes. 20.28.38 # cela: I'm not sure I understand, does the display goes dark after some inactivity time or does the screen just stays white when you wake up ? 20.28.51 # or use the caption backlight to wake it 20.29.03 # <[Saint]> cereal_killer: I believe the backings are interchangeable, but I shall cross this bridge when I come to it. 20.29.04 # MarcAndersen: if there is no mingw issue, the X-Fi sim should be there soon, once pamaury added it to simp.pl 20.29.08 # Yes when you wake it up agian 20.29.24 # <[Saint]> If not, I would need to purchase a new switch assembly, but that's no biggie. 20.29.39 # ok, so lcd init problme apparently, I will have a look at it, it was a common problem when I developped the port, I thought I solved the problem 20.30.08 # ok, thank you for sharing the information and have fun. 20.31.39 # I have a 8GB X-Fi non wifi version, but I guess that makes no difference, Easiest way to test for display problem is to set the caption backlight and wait a few minutes. 20.32.19 # I don't have this problem, it may be a timing issue, such problem can be pretty random or even depend on PCB versions (wifi vs non-wifi) or things like this ^^ 20.34.02 # be back soon 20.36.06 Quit rela (Read error: Connection reset by peer) 20.36.38 Part cereal_killer 20.38.26 Quit pamaury (Ping timeout: 245 seconds) 20.40.09 Quit cela (Ping timeout: 250 seconds) 20.42.22 Quit y4n (Quit: Assumption is the mother of all fuckups) 20.45.14 # pamaury: what do you mean with need glue code to enable the speaker on the zen x-fi? 20.51.16 # <[Saint]> I'm not sure if its universal, but, I usually use the term to refer to a section of code that would normally be considered an ugly hack were it not the only option. 20.52.22 # <[Saint]> Hmmm...though, I also use it to refer to a section of code with no functional value other than pointint two or more other sections of code at each other. 20.52.41 # <[Saint]> The latter is probably the more "accepted" term, I would guess. 20.53.11 # <[Saint]> s/pointint/point/ 20.53.31 # <[Saint]> Lets see what a dictionary thinks... 20.53.49 # <[Saint]> Aha, close: "In programming, glue code is code that does not contribute any functionality towards meeting the program's requirements, but instead serves solely to "glue together" different parts of code that would not otherwise be compatible. Glue code often appears in code written to let existing libraries or programs interoperate, as in language bindings or foreign function interfaces like the Java native interface, or when mapping objects to a 20.53.49 # <[Saint]> database using object-relational mapping, or when integrating two or more commercial off-the-shelf programs. Glue code may be written in the same language as the code it is gluing together, or in a separate glue language." 20.54.06 Quit krabador (Ping timeout: 260 seconds) 20.56.07 Join krabador [0] (~krabador_@unaffiliated/krabador) 20.57.09 # [Saint]: thanks for the explanation 20.57.25 # <[Saint]> Wikipedia did it much better than I did. :) 20.57.37 # haha 21.01.52 Join kimya [0] (~Kimya@213-67-32-186-no154.bredband.skanova.com) 21.03.03 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 21.05.54 Quit krabador (Quit: Sto andando via) 21.07.59 # Hi, I get "Not enough space for music DB" on my Sansa Clip+. Any ideas what to do? 21.08.17 # <[Saint]> Freeing up some space might be an idea. 21.08.28 # <[Saint]> ...just sayin'. 21.08.51 # I can't mount my device. :( 21.09.16 # <[Saint]> But Rockbox can delete files and folders, so it doesn't matter. 21.09.49 # I have OF on the device. 21.10.06 # <[Saint]> So, this is unrelated to Rockbox at all? 21.10.39 # Yes 21.11.19 # <[Saint]> I would suggest talking to SanDisk then. 21.12.26 # <[Saint]> If you have an sdcard (with media) attached to the device, eject it, and try that - if that fails, no idea, and SanDisk would be much better suited to offer you support. 21.13.36 # I have eject my media. I have also tried must of the unbrick tips I have found on Internet. Nothing works. 21.14.48 # <[Saint]> Do NOT try ANY of the unbricking instructions you find on our wiki, it *will* end badly. 21.14.58 # <[Saint]> Talk to SanDisk. 21.16.40 # I haven't tried the more advance unbrick instructions (taking apart the device). I thought there should be some clever combinations to press... 21.16.51 # I will talk to SanDisk. 21.17.16 Join krabador [0] (~krabador_@unaffiliated/krabador) 21.17.46 # Thank you for your time and guidelines! 21.17.51 # <[Saint]> did you try searching the term you posted here? That gives me a lot of helpful information, from SanDisk, no less. 21.18.03 # <[Saint]> first hit: http://kb.sandisk.com/app/answers/detail/a_id/848/kw/not%20enough%20space%20for%20music%20db 21.19.13 # Yes, I have search for that term. Alot of people have the same problem. 21.20.18 # <[Saint]> Your issue seems to be compounded by the fact that you cannot mount the device, and I can only speculate on the reasoning for that - as I have no idea what steps you have or haven't taken to resolve this. 21.20.56 # <[Saint]> WHatever the reason for that is, unfortunately, this isn;t really the place for it. If you were running Rockbox, not only would this be relevant here it would be trivial to fix. 21.20.59 # <[Saint]> But, alas. 21.21.20 # The thing with rockbox is that one of the reasons we like it is that we don't actually have to know anything about using the original firmware 21.21.37 # I tried something I read on rockbox: Connect USB, when logo comes up, deattach USB, then the menu should apper, but it didn't. 21.21.43 # <[Saint]> That's it in a nutshell. 21.21.54 # So, maybe counterintuitively, we tend not to know a lot about it 21.22.22 # <[Saint]> Exactly, my solution for this is "use Rockbox"...which is of no use to you. :) 21.23.25 # My goal is to use Rockbox. It looks great. But I have to solve my problem first. 21.25.22 Quit krabador (Ping timeout: 260 seconds) 21.26.43 Join krabador [0] (~krabador_@unaffiliated/krabador) 21.26.45 # <[Saint]> It may be worthwhile to see if you *really* have a space issue or not. 21.27.00 # <[Saint]> A botched allocation table could also cause this. 21.27.14 # <[Saint]> Oh - heh, ..but, you'd need to be able to mount it for that. Gah. 21.28.16 # <[Saint]> See? Hopeless. :) Talk to SanDisk, even if they have no idea what to do they'll be able to tell you this in an official capacity. 21.28.25 Quit krabador (Read error: Connection reset by peer) 21.28.52 # I think I have a bad filesystem on my device. 21.29.33 # Does the OF work 21.29.33 # ? 21.29.40 # If so, can't you format from there? 21.29.55 # <[Saint]> It doesn't get that far. 21.30.06 Join krabador [0] (~krabador@unaffiliated/krabador) 21.30.07 # Right 21.30.13 # No, logo comes up, then the error message "Not ..." 21.32.43 # <[Saint]> One would think "Hey, there's no space for the Database, we'll let you boot so you can actually do something about it" would be a saner approach. 21.33.16 # Yes 21.33.49 # <[Saint]> But if original firmwares weren't crap, Rockbox wouldn't exist. ;) 21.34.05 *** Saving seen data "./dancer.seen" 21.34.19 # Well, these are the same people who on the c200 said "Oh, the FAT superblock is corrupt. Let's believe what it says about device size instead of reading it from the sd chip so we report a negative size over USB" 21.35.23 # I would realy like to switch to Rockbox. My device have been "bricked" for over a year. When I found Rockbox, I thought I give it a try to unbrick it. 21.36.03 # It's definitely worth it, but that doesn't really help you... 21.41.30 # True. My win xp box is having trouble format my device. Do you think I have better results with win7? 21.52.19 # Thank you for time and god ideas. I will try win7 and some other tips I read about. Here in Sweden it's soon 10 PM. Have a good night and thanks again! 21.57.58 Quit kimya (Read error: No route to host) 21.58.26 Quit bluebrother (Disconnected by services) 21.58.31 Join bluebrother^ [0] (~dom@rockbox/developer/bluebrother) 22.00.07 Quit fs-bluebot (Ping timeout: 244 seconds) 22.01.24 Join fs-bluebot [0] (~fs-bluebo@g226071034.adsl.alicedsl.de) 22.05.09 Join wodz [0] (~wodz@87-207-223-0.dynamic.chello.pl) 22.05.37 Quit krabador (Quit: Leaving) 22.10.48 Join krabador [0] (~krabador_@unaffiliated/krabador) 22.12.18 Quit krabador (Read error: Connection reset by peer) 22.17.12 # lol, funny things happen when you toggle by mistake the chip enable pin of the sdram ^^ 22.18.37 # What happens? Can you remember? ;) 22.19.13 # everything went black ;) 22.19.55 Join krabador [0] (~krabador_@unaffiliated/krabador) 22.20.55 # <[Saint]> I knew it! 22.21.04 # <[Saint]> Robot! 22.21.30 # pamaury: Could you please look at atj213x usb core register map? Maybe you will spot some similarities with cores you know. fw_update_4_brom_fage_verify/adfu/include/adfuserver_63.h has some defines. 22.22.03 # wodz: I had a look iirc and it's wasn't obvious for me I saw it before 22.22.20 # it bears some far similarly with some cores, like in "it's a usb core" ;) 22.22.25 # *similarity 22.23.01 # let me recheck 22.23.48 # gevaerts: what do you think I should do about the NWZ-E380 ? As far as we know it is just a rebranded NWZ-E370 so how should I handle it ? Create a new target anyway ? 22.24.15 Quit andypotter (Ping timeout: 272 seconds) 22.25.23 # I found some realtek? SoC which has similar reg map for otg but now I can't find my notes what SoC it was :/ 22.25.39 # pamaury: I don't think so. It's similar to the 1st and 2nd gen ipods I'd say 22.26.32 # gevaerts: so just keep E370 and tell people the E380 is just a E370 ? 22.26.43 # by create a new target I mean add an entry in configure 22.26.47 # mostly 22.27.02 # but it's a bit stupid to compile twice the same code 22.27.09 # I'd leave new targets for actually different things 22.27.20 # or so call it E370/E380 in configure then ? 22.27.24 Quit Narod () 22.27.38 # That probably makes sense 22.27.43 # * bertrik agrees 22.28.01 # Ha, found it. It is ralink rt-n56u not realtek 22.28.08 # Or call it E3[78]0 :) 22.28.09 # pamaury: I think the E370/E780 is best name for it. 22.28.09 Quit zoktar (Quit: -) 22.28.25 # It don't have sense to create two target's for the same device, I think. 22.28.35 # wodz: do you have the DS for it ? 22.28.39 # Or E3⅞0 22.28.45 # (for the ralink) 22.28.54 # pamaury: no only linux source 22.29.02 # E370 and E380 is like a PSP 1000 and PSP 2000, both are the same, only few changes isnide. 22.29.13 # ok 22.30.01 # pamaury: https://dev.openwrt.org/browser/trunk/target/linux/ramips/patches-3.9/0162-USB-MIPS-ralink-add-rt5350-mt7620-UDC.patch?rev=37058 22.30.16 # wodz: Polak? 22.30.39 # Szczepancio: yes 22.30.45 # wodz: Me too :) 22.36.38 # wodz: that's a long patch ! 22.41.16 Quit Szczepancio (Quit: Leaving) 22.42.17 # Build Server message: 3New build round started. Revision 457d64f, 243 builds, 36 clients. 22.42.41 # lebellium: I added some targets to sims.pl 22.42.58 # Thanks pamaury 22.43.24 # great 22.45.31 # next you see with rasher :p 22.46.16 # <[Saint]> I think that's the end of the process. 22.46.21 # indeed 22.46.33 # <[Saint]> I don't think there's any intervention to be done other than adding targets to the "magic file". 22.46.41 # the targets will automatically be added tomorrow 22.46.54 # at next build round 22.47.58 # <[Saint]> I don't think they're generated per-round. 22.48.26 # <[Saint]> I believe it may well be daily? 22.49.22 # yes that's what I meant actually. I know that it's only once a day max 22.49.46 # Build Server message: 3Build round completed after 450 seconds. 22.51.35 Quit n1s (Quit: Ex-Chat) 22.51.56 # would be great to fix the Fuze+/Gigabeat/Onda sim stuck to April, 1st but I don't remember what's the exact issue. 22.54.44 Quit kevku (Ping timeout: 245 seconds) 22.56.16 # is there any convention on how speaker volume should be treated ? 22.56.55 # on the x-fi? just decibel i should think 22.56.56 # the only targets with speaker at the moment just don't seem to have to handle this issue but on imx233 once can independely select headphone and speaker volume 22.57.52 # MarcAndersen: no I mean should we have independent volume control or unified, we don't have even have speaker mute on headphone insertion as far as I know 22.58.25 # I would say combined volume + mute on hp insert 22.58.47 # mute on hp insert should be handled by app 22.59.21 # oh. that is a good question. 22.59.28 # it's a combination of HAVE_SPEAKER and HAVE_HEADPHONE_DETECT + setting which says speaker disabled/disabled on hp/enabled at all time 22.59.49 # I guess I'll have to write it 23.01.04 # I wish i could do some C programming, but I'm only doing scripting at the moment. 23.02.51 Join andypotter [0] (~andypotte@97e6f4b0.skybroadband.com) 23.03.15 # lonoxmont: a custom cable is good as it probably is IAP over Serial. 23.03.17 # Have you managed to build your own rockbox binary? If so, creating a build that includes (a)dvanced and (l)ogf should allow for capturing the IAP commands to a file that we could then examine and see where it barfs. 23.05.55 # who knows things about audio signals ? The manual says "This bit field controls the left volume of the lineout, LOL. The first 16 combinations allow for adjusting the lineout peak to peak voltage in small steps. Each lsb change in this range changes the RMS output voltage by 25mV under these conditions. This allows the block to tweak out gain errors in the system or to potentially save power in applications not requiring a large outpulevel. The 23.05.55 # next 16 values decrease the gain in 2dB steps. The decrease is cumulative with the first 16 settings. (11111)=-35dB.". I understand the setting >=16 but I don't understand the relationship between 25mV RMS and dB, probably ignorance 23.07.22 # I suspect you want saratoga 23.07.38 # if I read correctly, if you set it to (11111)=31 you are doing (31-16+1) -2dB steps so that's -32dB and then it means each of the first step actually reduces by -0.2dB but why -0.2dB == -25mV RMS ? 23.07.43 # Yes but he is not there :( 23.08.11 # Knowing him, he might appear at any moment :) 23.21.15 # hum, I think my reasoning is just wrong in fact, the first settings are not dB, they linearly decrease the volume whereas dB would decrease it in a logarithmic fashion 23.21.30 # hopefully saratoga can explain this 23.25.55 Quit amayer (Quit: Leaving) 23.34.08 *** Saving seen data "./dancer.seen" 23.35.15 # pamaury: http://www.cypress.com/?docID=27095&dlm=1 this looks similar also to the core in atj the reg addresses are completely different but general layout is similar 23.36.27 Quit [7] (Disconnected by services) 23.36.41 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 23.39.37 Quit Guest17648 (Quit: Hmmm...) 23.47.24 Join Guest17648 [0] (~husvagn@90-230-140-28-no41.tbcn.telia.com) 23.48.13 Join stripwax [0] (~Miranda@rockbox/developer/stripwax)