--- Log for 06.03.117 Server: adams.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 1 month and 0 days ago 00.11.31 Join idonob_ [0] (~Owner@S010600259c3e7d7b.vs.shawcable.net) 00.19.22 Quit pamaury (Remote host closed the connection) 00.19.37 Quit petur (Quit: Leaving) 00.21.30 Quit idonob (Ping timeout: 260 seconds) 00.32.26 Quit CrashBash-Kun (Read error: Connection reset by peer) 00.40.34 Join JanC_ [0] (~janc@lugwv/member/JanC) 00.41.51 Nick JanC is now known as Guest33463 (~janc@lugwv/member/JanC) 00.41.51 Quit Guest33463 (Killed (cherryh.freenode.net (Nickname regained by services))) 00.41.51 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC) 00.50.53 Join idonob [0] (~Owner@S010600259c3e7d7b.vs.shawcable.net) 01.01.33 Quit idonob_ (Ping timeout: 240 seconds) 01.01.59 Quit ender (Quit: foot, n. a device used for finding Lego bricks in the darkness) 01.03.20 Quit michaelni (Ping timeout: 264 seconds) 01.11.57 *** Saving seen data "./dancer.seen" 01.15.38 Join michaelni [0] (~michael@213-47-41-20.cable.dynamic.surfer.at) 01.23.24 Quit ZincAlloy (Quit: Leaving.) 01.25.38 Join superluig164 [0] (4632e65c@gateway/web/freenode/ip.70.50.230.92) 01.43.04 # I asked a question on the forums ( http://forums.rockbox.org/index.php/topic,51692.new.html#new ) and the person who replied to my post told me to come here to ask if what I want to do is feasable. Could someone answer that for me? 01.44.18 # <__builtin> saratoga_: ^ 01.44.20 # <[Saint]> hold fire 01.46.32 # <[Saint]> No. This is not feasible. 01.47.07 # <[Saint]> Errr, actually...perhaps I'm interpreting this wrong. 01.48.29 # What do you mean? 01.49.43 # <[Saint]> Just making sure I'm understanding what you want to do properly. 01.49.43 # <[Saint]> When the wiki says "the firmware is shared between players X, Y, and Z", they mean the original firmware. Not ours. 01.50.00 # <[Saint]> Rockbox is most certainly targeted to subgroups. 01.50.22 # Yes, but in my experience, if the original is exactly the same, RockBox should work just as well, no? 01.50.32 # <[Saint]> No. 01.50.57 # Aw. Would it hurt to try, though? 01.51.38 # <__builtin> it wouldn't do anything... 01.51.59 # Good point. Okay, well, I guess I'll just wait for someone to do one for the S540 01.52.09 # Thanks anyway guys 01.55.23 Quit superluig164 (Quit: Page closed) 01.56.25 # <[Saint]> It's a valid point and a logical conclusion to come to, but it's hard to explain why it isn't the case so I just settled with 'no'. 02.06.43 Join superluig164 [0] (4632e65c@gateway/web/freenode/ip.70.50.230.92) 02.07.49 Quit superluig164 (Client Quit) 02.29.15 Join idonob_ [0] (~Owner@50.67.32.65) 02.37.46 Quit idonob_ (Ping timeout: 260 seconds) 02.59.56 # So is there a good RB7xx series routerboard that can reliably run openwrt via metarouter? 03.00.51 # From my brief tests so far, it seems the older 750s (750, 750G) lack RAM capacity, whereas the newer models either lack disk (RB750Gr2) or do not support metarouter (RB750Gr3). 03.01.04 # Er, wrong channel. 03.02.30 Quit Moarc (Ping timeout: 260 seconds) 03.05.33 Join Moarc [0] (~chujko@a105.net128.okay.pl) 03.06.45 # <[Saint]> Well...you were kinda close, shrizza_, they do have RB in the name. 03.06.56 # <[Saint]> I'll award half a point. 03.07.00 # Haha. :D 03.11.59 *** Saving seen data "./dancer.seen" 03.22.35 # For anyone wondering about the off-topic question: I got it running on RB750GL with its higher disk and RAM capacity. :) 03.30.24 # <[Saint]> I know most of those words. 03.39.56 Quit MrZeus (Ping timeout: 264 seconds) 03.40.55 Quit nlogex (Ping timeout: 258 seconds) 04.31.47 Quit krabador (Remote host closed the connection) 04.43.34 Join Piece_Maker [0] (~Acou_Bass@host-89-241-250-209.as13285.net) 04.44.45 Quit Acou_Bass (Ping timeout: 264 seconds) 04.44.45 Nick Piece_Maker is now known as Acou_Bass (~Acou_Bass@host-89-241-250-209.as13285.net) 04.45.30 Quit Acou_Bass (Client Quit) 04.46.48 Join Acou_Bass [0] (~Acou_Bass@host-89-241-250-209.as13285.net) 04.56.50 Join smoke_fumus [0] (~smoke_fum@dynamic-vpdn-93-125-63-154.telecom.by) 05.06.23 Quit ungali (Quit: ungali) 05.12.03 *** Saving seen data "./dancer.seen" 05.23.04 Join athidhep [0] (~afoakf@unaffiliated/athidhep) 05.31.03 Quit Bilgus_ (Quit: Leaving) 05.32.04 Join Bilgus [0] (~Bilgus@gateway/tor-sasl/bilgus) 05.54.10 Join Asara [0] (gadget@unaffiliated/asara) 05.54.24 # hey guys, I am trying to install rockbox on my sansa fuze+ 05.54.43 # and the device keeps going into readonly mode 05.54.46 # and screwing eveyrthing up 05.54.52 # using the rockbox utility to install 05.54.54 # any suggestions? 06.00.21 Join nlogex [0] (~filip@CPE30469a4d21ac-CMa84e3f5c8560.cpe.net.fido.ca) 06.02.23 Quit smoke_fumus (Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/) 06.12.08 Quit TheSeven (Disconnected by services) 06.12.16 Join [7] [0] (~quassel@rockbox/developer/TheSeven) 06.25.05 Quit Bilgus (Remote host closed the connection) 06.25.27 Join Bilgus [0] (~Bilgus@gateway/tor-sasl/bilgus) 07.12.07 *** Saving seen data "./dancer.seen" 07.14.24 Join idonob_ [0] (~Owner@S010600259c3e7d7b.vs.shawcable.net) 07.27.47 Quit idonob_ (Ping timeout: 240 seconds) 07.47.56 Quit Senji_ (Ping timeout: 240 seconds) 08.07.19 Join idonob_ [0] (~Owner@S010600259c3e7d7b.vs.shawcable.net) 08.14.33 Quit jhMikeS (Ping timeout: 256 seconds) 08.20.04 Quit girafe (Quit: Leaving) 08.21.25 Join ender [0] (krneki@foo.eternallybored.org) 08.22.29 Join parchd [0] (~parchd@unaffiliated/parchd) 08.37.08 Quit cc_ (Ping timeout: 260 seconds) 08.38.04 Quit idonob_ (Ping timeout: 240 seconds) 08.43.30 Join cc_ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 09.00.18 Join petur [0] (~petur@rockbox/developer/petur) 09.12.12 *** Saving seen data "./dancer.seen" 09.19.48 Quit cc_ (Ping timeout: 246 seconds) 09.20.25 Join cc_ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 09.21.04 Quit nlogex (Ping timeout: 260 seconds) 09.52.43 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 10.05.41 Join MrZeus [0] (~MrZeus@2a02:c7f:7059:8e00:4d90:32ba:6fae:423b) 10.29.18 Join p3tur [0] (~petur@rockbox/developer/petur) 10.29.49 Quit petur (Disconnected by services) 10.29.54 Nick p3tur is now known as petur (~petur@rockbox/developer/petur) 10.38.26 Quit pamaury (Ping timeout: 240 seconds) 10.39.46 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 10.47.33 # oh wow i wanted a routerboard at some point 10.47.49 # but my next router needs ac 10.49.14 # shrizza_ is there any reason to use owrt on it? i thought the whole point is routeros? 10.50.46 # Asara try manual installation? 10.51.42 Join paulk-blaze [0] (~paulk@147.210.204.186) 10.55.33 Quit MrZeus (Ping timeout: 264 seconds) 10.59.09 # duo8: I need to run a python script on it. 10.59.21 # Also, there may be other reasons such as nmap. 10.59.32 # huh, ok 10.59.46 # But yeah, for the most part ROS is sufficient. 10.59.55 # do you think the hw is worth it? 11.00.09 # * gevaerts would like to point out that the topic hasn't actually changed 11.00.22 # Well, it's not an enterprise-class router. Great CPE though. 11.12.14 *** Saving seen data "./dancer.seen" 11.15.20 Join MrZeus [0] (~MrZeus@81.144.218.162) 11.21.35 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 11.41.55 Quit cc_ (Ping timeout: 260 seconds) 11.43.36 Join cc_ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 11.43.47 Quit MrZeus (Ping timeout: 260 seconds) 11.47.10 # does anyone have the binary for fiiofw unpacker? 11.56.48 Join gK-1wm-su [0] (~jircii@46.22.220.25) 11.57.37 Quit gK-1wm-su (K-Lined) 12.05.15 Quit paulk-blaze (Ping timeout: 260 seconds) 12.05.56 Join paulk-blaze [0] (~paulk@no3.u-bordeaux.fr) 12.08.20 Quit paulk-blaze (Remote host closed the connection) 12.27.32 Quit athidhep (Quit: athidhep) 12.32.10 Join MrZeus [0] (~MrZeus@81.144.218.162) 12.36.21 Quit cc_ (Ping timeout: 264 seconds) 12.36.38 Join cc_ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 12.51.58 # duo8: for fiiox1 ? can't you build it from source ? 13.03.31 Quit neutric (Ping timeout: 240 seconds) 13.04.43 Join neutric [0] (~ah@unaffiliated/neutric) 13.12.17 *** Saving seen data "./dancer.seen" 13.22.45 # yeah, i was just asking if anyone had it already since i don't have a local copy of the repo 13.23.25 # also pamaury you figured out lcd yet? 13.33.19 Join MrZeus_ [0] (~MrZeus@81.144.218.162) 13.36.21 Quit MrZeus (Ping timeout: 246 seconds) 13.37.06 Join elensil [0] (~edhelas@2001:1c02:1903:d800:11d5:cb64:d390:2272) 13.44.57 # duo8: I have the lcd init routines but I haven't tried them on device yet 13.45.34 # what interface is it? i see the soc can control several types 13.46.44 # the smart lcd 13.48.16 # is it normal that i saw only 7/8 traces on the lcd flex cable? 13.50.49 # there should be more than that, many more 13.52.07 # a typical 8086 bus interface will have CS, WR, RD, RS, DB0-7 (or 0-15, I don't remember if the bus is 8-bit or 16-bit on the fiio x1), RESET, and then power pins (and also backlight) 13.52.20 # so more like 30 traces 14.00.45 # pamaury: unless data are sent though serial interface 14.02.01 # no on the Fiio X1 I am pretty it is sent through a parallel interface 14.03.06 # duo8: are you sure it's the Fiio X1 1st generation you are looking at ? Maybe the flex cable is double-sided 14.07.39 # Asara have you got the boot loader on already? 14.10.19 # duo8: on the photos of the X1 that I have, the flex cable looks like it has 30 traces 14.24.33 Quit cc_ (Ping timeout: 258 seconds) 14.24.54 Join cc_ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 14.29.26 Quit rela (Read error: Connection reset by peer) 14.43.27 Quit cc_ (Ping timeout: 240 seconds) 14.44.16 Join cc_ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 14.51.22 # i'm looking at my dap (shanling m2 14.52.05 # wait i'll get the pic 14.57.53 # pamaury https://my.mixtape.moe/jslfnc.jpg 14.58.35 # I see 30 contacts on this photo 15.00.17 Quit cc_ (Ping timeout: 256 seconds) 15.00.40 Join cc_ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 15.02.36 # wow did you actually count 15.03.14 # anyway look below, there are only a few traces (dark lines) 15.04.19 # indeed looks like 7 or 8 lines are actually connected. 15.05.47 Quit cc_ (Ping timeout: 240 seconds) 15.05.59 # pamaury: Do you know if there is any documentation for earpods with remote? Is there some standard? Android/iPhone somehow know what to do so I assume there is one 15.07.43 Join cc_ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 15.08.56 # ctia? 15.09.26 # inline remote support in rb would be cool 15.09.48 Join jhMikeS [0] (~jethead71@d192-24-173-177.try.wideopenwest.com) 15.10.29 # duo8: hey man 15.10.33 # ? 15.10.39 # i am missing something in terms of the manual install 15.10.44 # every time i mount the device 15.10.47 # and try to do anything to it 15.10.50 # it switches to read only 15.11.20 # There is intriguing string in hiby_player /sys/bus/platform/devices/earpods_adc.0/earpods_adc/earpods_adc_sw which might mean that rocker can be controlled with inline remote on earpods 15.12.20 *** Saving seen data "./dancer.seen" 15.13.24 # yeah prob 15.13.28 # the FiiOs can 15.14.04 # hopefully the line actually gets connected 15.15.18 # unfortunately I don't have such pods to try 15.17.10 # surely you have one with a switch? 15.17.34 # nop 15.17.39 # hmm 15.17.57 # you can buy a cheap headset to test if you're willing to spend 15.18.14 # cheap android headset and a fake earpod 15.19.49 # found this http://www.wisebread.com/files/fruganomics/u784/one%20step%20beyond%20cable.jpg 15.21.20 # and https://source.android.com/devices/accessories/headset/plug-headset-spec.html 15.26.09 # duo8: That is helpful 15.26.55 # apple is slightly different but the play/pause button is the same afaik 15.42.38 Join paulk-blaze [0] (~paulk@37.168.228.34) 15.43.45 Quit wodz (Ping timeout: 246 seconds) 15.53.21 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:40c6:c3f5:3774:7926) 15.54.42 Join amayer [0] (~amayer@mail.weberadvertising.com) 16.00.21 Quit amayer (Quit: Leaving) 16.00.35 Join amayer [0] (~amayer@mail.weberadvertising.com) 16.26.07 Quit parchd (Ping timeout: 260 seconds) 16.32.25 # duo8: shanling m2 might use something different, I did not claim all devices in the world use parallel for lcd ;) 16.32.49 # wodz (logs) for earpods there is some kind of ad-hoc standards: apple and android 16.32.59 # they use resistors on the mic line usually 16.33.03 Join parchd [0] (~parchd@unaffiliated/parchd) 16.40.43 # duo8: for LCDs, SPI is quite common as well and then you just a need a few wires: GND, VDD, TX, CS, possibly RESET, maybe RX. Then backlight if it's not OLED 16.42.17 Part Asara 16.42.36 # if you want I'll have a quick look at the OF code 16.44.03 # if you can spare the time to, not like it's up there on priority list 16.44.29 # but if spi then it's not the jz lcd interface 16.45.24 # no indeed 16.47.07 # is that better or worse? 16.47.22 # neither :) just different 16.47.57 # but would it be more difficult to implement spi lcd? no docs from ingenic afaik 16.49.05 Quit paulk-blaze (Ping timeout: 256 seconds) 16.49.41 # not really. What happens in almost cases (even jz lcd interface) is that you implement the transport layer (jz lcd, spi), then you disassemble the firmware to find the (usually long) init sequence, and commands to redraw, and they you are rolling 16.50.08 # and in both cases you have the same problems: if you don't have the doc for the controll then you are stuck with whatever lcd settings the OF is using 16.50.17 # *controller 16.50.24 # huh 16.50.43 # well my lcd has literally no marking/writing 16.50.57 # and it's bonded to the shell so i can't remove it 16.51.01 # even with a marking you probably wouldn't find it 16.51.10 # damn china 16.51.37 # what I usually do is look at the registers written by the firmware and derive a best case based on experience and comparison with controller datasheets 16.51.44 # *best guess 16.52.04 # would the manufacturer have the docs? 16.52.20 # sometimes yes, but not always 16.52.56 # manufacturers usually sell lcd+controller together, and might provide an init sequence with any doc, and sometimes say "tweak this bit here to change this" 16.53.04 # *without any doc 16.53.49 # in practice there are not that many important bits in the registers that you care about 16.56.45 # hmm ok, what else is different from the fiio 16.56.49 # the DAC? 16.56.59 # probably not i2s 16.57.49 # the DAC is probably different but all DACs use i2s and i2c for control. So what will different is the DAC setup 16.58.21 # in other words, pcm (i2s) driver is the same, but codec (volume, routing, etc) driver is different 16.58.38 # but this one does dsd 16.58.53 # at least there's a datasheet 16.59.25 Quit cc_ (Ping timeout: 258 seconds) 16.59.57 # I don't see how dsd makes a difference 17.00.24 Join nlogex [0] (~filip@CPE30469a4d21ac-CMa84e3f5c8560.cpe.net.fido.ca) 17.01.05 # it might change the size of the pcm samples but data will most likely still be sent over i2s. And even then, codec usually let you choose the pcm size. So we will most likely still send 16-bit pcm samples 17.01.37 Join cc_ [0] (~ac@home.rhizogen.es) 17.04.51 # can you communicate with the pmu? it's the same axp202 17.06.09 # I don't know much about this pmu but usually yes one communicate over i2c 17.06.14 # or spi 17.06.39 Join paulk-collins [0] (~paulk@gagarine.paulk.fr) 17.07.23 # well, that's about all for hw differences 17.12.24 *** Saving seen data "./dancer.seen" 17.16.29 Join Senji_ [0] (~Senji@85.187.103.250) 17.16.35 Join ven00m [0] (~ven00m@KH83201.karlshof.wh.tu-darmstadt.de) 17.16.39 # Hello 17.16.49 Join chrisb [0] (~chrisb@pool-71-175-246-153.phlapa.east.verizon.net) 17.16.55 # I flashed Rockbox on my Xduoo X3 but it doesn't do anything since 1 hour 17.16.57 # What should I do? 17.17.18 Join superluig164 [0] (c7ebc060@gateway/web/freenode/ip.199.235.192.96) 17.17.21 # I downloaded the files and renamed it to update.zip and copied it to the sd card. 17.17.32 # just like rock-boxfull which i extracted before 17.17.43 # I went to settings and did an update 17.18.05 # so I am waiting for 1 hour now and it doesn't do anything.. can I cancel the update or what do i have to do? 17.18.26 Quit parchd (Ping timeout: 240 seconds) 17.18.45 # ven00m: the xduoo x3 port is not supported by rockbox officially. You will need to ask the person who did the port 17.19.27 # But when I cancel the update will my device be bricked? 17.20.08 Join parchd [0] (~parchd@unaffiliated/parchd) 17.21.08 # ven00m: no idea, I know nothing about the port I am afraid 17.21.18 # https://www.reddit.com/r/headphones/comments/4c2u3a/the_xduoo_x3_dap_now_has_a_fully_functional/ 17.21.26 # whats that 17.22.32 # so what happens to other mp3-players when canceling the flash ? 17.22.55 # Someone did a rockbox port, on their own, without talking to us at all. We don't know *anything* about it 17.23.09 # that depends on how it is implemented, on where it hanged. It could do nothing or it could brick your device. 17.24.33 # Damn, what should I do? 17.24.38 # Wait? > 1 hour now? 17.26.23 # ven00m: send an email to the guy who did the port ? 17.26.37 # http://xvtx.ru/rockbox/ 17.26.38 # how to find out? 17.28.44 # I wrote him 17.28.51 # Thank you.B 17.29.08 Quit superluig164 (Ping timeout: 260 seconds) 17.29.11 # But how is it possible that someone publishs a port without having talked to you guys 17.30.13 # He ported rockbox to the device but said he was not interested in joining the community and maintaining the port 17.30.37 # So is there a way I get the os to run again? 17.30.52 # the problem is that if no one maintains the port then we end in the situation where users ask questions and we don't know how to help 17.30.54 # the original firmware 17.31.03 # does this occour a lot? 17.32.27 # you'll have to ask him. Maybe he has tools to recover the device. I tink the Xduoo X3 can always be recovered, assuming he has the tools 17.32.45 # pamaury: the source code of its port isn't available? 17.32.53 # yes it's available 17.33.12 Quit petur (Quit: Connection reset by beer) 17.33.39 # at least for the port it self, but not the installer iirc 17.34.58 # https://github.com/Rockbox/rockbox/compare/master...xvortex:master 17.41.25 Join saratoga [0] (123e1fa4@gateway/web/freenode/ip.18.62.31.164) 17.41.34 # some source is available, but not for the code you downloaded 17.41.42 # so you're basically stuck asking him for help 17.42.26 Quit cc_ (Ping timeout: 240 seconds) 17.43.06 Join cc_ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 17.48.35 Quit parchd (Ping timeout: 256 seconds) 17.49.42 Join advcomp2019_ [0] (~advcomp20@65-131-154-48.sxct.qwest.net) 17.49.42 Quit advcomp2019_ (Changing host) 17.49.42 Join advcomp2019_ [0] (~advcomp20@unaffiliated/advcomp2019) 17.51.04 Quit advcomp2019 (Ping timeout: 240 seconds) 17.51.27 Quit cc_ (Ping timeout: 240 seconds) 17.52.12 Join parchd [0] (~parchd@unaffiliated/parchd) 17.56.03 Join cc_ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 18.00.51 Quit pamaury (Ping timeout: 260 seconds) 18.16.06 # thx 18.16.18 Quit ven00m (Remote host closed the connection) 18.23.28 Join mmcmac [0] (~mmcmac@inet-hqmc08-o.oracle.com) 18.35.22 Nick mmcmac is now known as uhmgawa (~mmcmac@inet-hqmc08-o.oracle.com) 18.41.59 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 18.44.23 Quit saratoga (Ping timeout: 260 seconds) 18.59.49 Quit foolsh (Remote host closed the connection) 19.01.05 Join foolsh [0] (~starchase@162-204-199-234.lightspeed.sbndin.sbcglobal.net) 19.04.25 Quit foolsh (Remote host closed the connection) 19.05.34 Join foolsh [0] (~starchase@162-204-199-234.lightspeed.sbndin.sbcglobal.net) 19.10.05 Join MrZeus [0] (~MrZeus@2a02:c7f:7059:8e00:f5ef:73d4:3803:b31f) 19.12.25 *** Saving seen data "./dancer.seen" 19.13.57 Quit foolsh (Remote host closed the connection) 19.15.11 Join foolsh [0] (~starchase@162-204-199-234.lightspeed.sbndin.sbcglobal.net) 19.19.10 Join lebellium [0] (~chatzilla@89-93-177-91.hfc.dyn.abo.bbox.fr) 19.27.11 Quit cc_ (Ping timeout: 260 seconds) 19.27.40 Join cc_ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 19.40.50 Join girafe [0] (~girafe@LFbn-1-11729-221.w2-7.abo.wanadoo.fr) 19.49.13 Quit cc_ (Ping timeout: 258 seconds) 19.50.31 Join cc_ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 19.55.40 Quit parchd (Quit: dinnertime) 20.33.31 Join TheLemonMan [0] (~root@irssi/staff/TheLemonMan) 20.38.47 Join petur [0] (~petur@rockbox/developer/petur) 20.39.14 # wodz: lebellium: so I tried to run the OF, play a song, kill it and then run rockbox (without touching the alsa controls). And it still produces crappy output 20.40.07 # it is possible that by killing the OF, it closes some file descriptors and reset some state set by the OF, or it could mean that the OF is doing some preprocessing the audio files 20.42.31 # (that's if I kill the OF when it is paused) 20.42.46 # if I kill the OF while playing, then rockbox cannot play audio, the pcm driver seems stuck 20.50.05 # stupid question but is it possible to run Rockbox while keeping the OF in background? 20.52.42 # well the problem is that usually only one program can access the audio driver 20.52.58 # and beside, it's not even clear it will help it any way 20.55.08 # also I have tried to suspend the Of but it doesn't work 20.56.52 # I still don't understand why Sony don't use the default DAC settings 20.56.57 # I'm sure it's fine enough 20.58.42 # the only clue I have so far is the OF requests the ALC (Automatic Level Control, i think) table from the driver. which may suggests it uses it to do some kind of audio processing 20.58.48 # or have the DSP do it, I don't know 21.03.46 Quit uhmgawa (Remote host closed the connection) 21.12.29 *** Saving seen data "./dancer.seen" 21.19.30 # * pamaury is running out of ideas to fix the nzw audio 21.19.35 # *nwz 21.21.02 Join mmcmac [0] (~mmcmac@inet-hqmc01-o.oracle.com) 21.21.03 # would the problem be the same with a native port? 21.22.04 # doing a native port on this thing would be insane 22.18.00 Quit [Saint] (Remote host closed the connection) 22.22.33 Join [Saint] [0] (~sinner@rockbox/staff/saint) 22.40.12 Quit [Saint] (Ping timeout: 260 seconds) 22.45.10 Join [Saint] [0] (~sinner@rockbox/staff/saint) 22.48.27 Quit fujisan (Quit: Textual IRC Client: www.textualapp.com) 22.51.21 Quit petur (Remote host closed the connection) 22.53.37 Quit [Saint] (Ping timeout: 260 seconds) 22.57.51 # pamaury, on the fuze plus I see you have absolute.z that seems to pick up how big an area the touch occupies is there any reason you didn't use that to filter key presses? 22.59.23 # Bilgus: I can't make any sense of your sentence :) 22.59.51 # <__builtin> I understand all the words at least! 23.01.07 # lcd_putsf(0, 6, "abs: %d %d %d", absolute_x, absolute_y, (int)u.s.absolute.z); <- sansa fuze plus https://github.com/Rockbox/rockbox/blob/1f8ea9fe27313228e5df67ce6447830b5c30e5e3/firmware/target/arm/imx233/sansa-fuzeplus/button-fuzeplus.c#L563 23.01.12 # yes 23.01.25 # ? 23.02.32 # I don't see what kind of filtering you are referring too 23.02.57 # the touchpad provides some information about the touch area but it's not very useful 23.03.07 # or at least I don't see how to use it 23.03.50 # like filtering out extraneous key presses the sensitivity doesn't seem to do it all that well 23.04.34 # I am not sure I see what you are referring too 23.04.57 Quit paulk-collins (Remote host closed the connection) 23.05.44 # ok for instance if I place the device in my pocket it picks up key presses somehow?? if I set the sensitivity low then it doesn't but it makes using the keypad near useless 23.06.10 # but how is that going to help ? 23.06.33 # I notice in the debug menu Z changes between 15-35 depending n how much of my finger is placed on the pad 23.06.34 # my guess is that the "absolute z" you'll get will be big in your pocket 23.07.10 # and you can lock the screen to avoid that 23.08.11 # but feel free to experiment, if you come up with something that works why not 23.08.59 # Advanced keylock helps a lot with that esp the autolock but that 10 seconds or so before it enables sucks sometimes 23.09.57 # Bilgus: you cam manaually lock the screen in the wps 23.10.02 # press power 23.10.12 # yeah I'm already aware 23.11.35 # I was jw if there was something funky with the Z that I wasn't aware of 23.12.25 # well I suggest you try by yourself, you can go to the debug menu, Show HW Info > target > press play 23.12.31 # you'll have the touchpad debug screen 23.12.32 *** Saving seen data "./dancer.seen" 23.12.34 # it displays Z 23.24.47 Quit TheLemonMan (Quit: "It's now safe to turn off your computer.") 23.25.30 # <__builtin> jhMikeS: it seems that the filesystem fails when trying to write to a file greater than 2GB in size 23.25.47 # <__builtin> the theoretical FAT limit is 4GB, any idea why? 23.26.19 # you can't represent it in off_t 23.27.29 Quit ender (Quit: Friends come and go, but enemies accumulate. —- Jones Law - ... and sometimes the real trick is telling the difference. — addendum) 23.27.38 Part chrisb ("rcirc on GNU Emacs 26.0.50.1") 23.27.55 # <__builtin> how would I fix it? 23.28.17 # <__builtin> I understand that it has to be signed, so... extend it to 64 bits? 23.30.23 # <__builtin> or would that have side effects elsewhere? 23.30.55 # it's meant to have off_t be 64 bits and FILE_SIZE_MAX set to 0xFFFFFFFF 23.31.24 # __USE_FILE_OFFSET64 would have to be defined and off_t changed 23.31.31 Quit lebellium (Quit: ChatZilla 0.9.93 [Firefox 51.0.1/20170125094131]) 23.34.17 # <__builtin> there seem to be some format strings that assume off_t is signed long 23.34.32 Nick ranmacha1 is now known as ranmachan (~ranma@yumi.uguu.de) 23.34.50 # what sort of failure was it anyway? 23.35.01 Quit tbx1024 (Quit: Leaving) 23.35.27 # <__builtin> it just failed to write after 2GB, no crash or anything 23.36.55 # yeah, that's what it does. it doesn't have to though. you just wouldn't be able to seek to beyond 2gb but could read or append. other functions wouldn't be able to return information 23.38.35 # lseek beyond 2GB and filesize would just have to fail even read and write would accept data beyond the off_t limit 23.38.58 # internally it's unsigned 23.40.19 # meh, I'm reworking some of the organization anyway with a different disk cache. It's about 1.5-2.0k smaller too. 23.41.11 # <__builtin> I'll probably do it the Right Way and split it into multiple files 23.48.48 # thats probably preferable on a 60 hour file anyway 23.56.51 Join superluig164 [0] (4632e65c@gateway/web/freenode/ip.70.50.230.92)