--- Log for 14.12.116 Server: verne.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 7 days and 15 hours ago 00.01.50 Join chrisjj [0] (5001d87b@gateway/web/freenode/ip.80.1.216.123) 00.02.01 # Now of course we can also just ignore the issue 00.02.32 # or use something in-between by linking dynamically and ignoring that this doesn't solve the issue completely :) 00.03.29 # I personally don't mind if my GPL licensed code is linked against openssl, since you can still use my code according to the GPL. But that's just my opinion. 00.03.53 # gevaerts: I meant that it seems unlikely one of our devs will object. And if users object we can ignore them 00.04.00 # ;) 00.04.42 # pamaury, I'd appreciate any more inside info on the recent ZEN LCD BSoD improvement to help my testing. E.g. to what variables was the fail sensitive ... if not just completely random. 00.05.01 # hmm. There's no issue with LGPL vs openssl, right? 00.06.39 # I believe so 00.07.00 # chrisjj: I traced it back to a hardware bug, that I can reproduce fairly well (it's still random but at least I know what happens). But since this hardware bug is not in any errata, I am not sure entirely sure how to workaround it 00.07.42 # chrisjj: can you confirm that the problem always happen in the bootloader ? 00.08.06 # Confirm on latest or previous? 00.08.16 # both 00.08.27 # or maybe latest because I'm unsure about the previous 00.08.31 # it was quite old I think 00.09.00 # Previous: no. The problem happens on some boots and some USB dis/connects 00.09.43 # good. We do have LGPL code imported. 00.09.58 # Current: Tests so far show the problem rarely occurs on boot. Test have not yet targetted USB. 00.10.18 # Yes, previous was +2yrs back IIRC. 00.11.25 # chrisjj: did you at least notice an improvement with the new code ? 00.11.39 # Re current, because the problem occurrence on boot is rare, and I have no logging, I can't say if it is in the boot loader. 00.12.44 # Yes, a big improvement. So far six units on automated test show fail on boot is 1 in >=100. 00.12.51 # Previous was 1 in 5. 00.13.25 # oh, awesome :) that matches my tests then, I'd done around 50 boots without any hang 00.13.29 # * bluebrother out for today 00.14.10 # If you use the clip trick, you'll get a hang, I think. 00.16.09 # Ok I'll try it. The problem is that when the problem occurs, it's too late to solve it and it does not necessarily gives a solution to fix it. I only have a partial understanding of why the hardware goes crazy 00.16.32 # But I'll keep trying 00.17.26 # Is there any trick or logging that I can apply to show you at what stage the hang is occurring? 00.18.13 # no, I've spent many hours last week-end on it and I know exactly where it fails now. But as I said, when you reach this point, it is too late, the hardware can be recovered :( 00.18.40 Quit ender (Quit: I always wanted to have a job in construction or at a hardware store just so I could eat some pink cotton candy in front of someone in a situation that would make them think I was eating fiberglass insulation. — Chris Hallbeck) 00.19.16 # The hardware can NOT be recovered?? 00.19.23 # not until chip reset 00.20.09 # OK. So are we saying there's no value is knowing at what stage the actual hang takes place? 00.20.35 # no 00.20.55 # the nature of the problem makes it irrelevant 00.21.04 # Got you. So please clarify: what do you mean by "can you confirm that the problem always happen /in/ /the/ /bootloader/"? 00.21.51 # I remember so old report about the BSoD happening after boot (I think on backlight on/off) but this problem should be completely fixed 00.21.54 # *some 00.22.11 # Some what? 00.22.39 # *some old reports 00.23.31 # Yes, I reported the BSoD occurring soon after boot. Checking... 00.28.05 # Original report here: http://forums.rockbox.org/index.php/topic,13462.75.html "Sometimes upon Rockbox program launch, the device goes unresponsive to buttons, showing a black screen" 00.30.57 *** Saving seen data "./dancer.seen" 00.31.26 # At that time, the BsOD was after "Executing", so I take it that does not say whether it is in the bootloader or not. And I take it by "in the bootloader" you really mean sometime after boot and before Rockbox logo. 00.32.21 # This is the issue I am saying is now rare. If I could catch the rare remaining fail by eye or with some logging , I'd be able to say whether the original issue has gone completely and this is a different fail, or the original issue is greatly reduced though not eliminated. 00.35.51 # There are basically two points in time where it can fail: 00.35.51 # 1) even before any logo is displayed: you'll most probably see the Creative logo slowly fade away to black (or the screen become white/grey in some rare cases): this is what I call "in bootloader" 00.35.51 # 2) after "Executing", when starting the main firmware: you'll typically get a black screen 00.35.51 DBUG Enqueued KICK pamaury 00.35.51 # Normally, 2) should be gone and 1) is what I fixed. Although if you don't see it happen, if might not be obvious which one it 00.37.47 # (note that 1 and 2 are in fact related, simply in case 2 we have more latitude to workaround the problem compared to 1) 00.41.36 Quit Elfish (Ping timeout: 258 seconds) 00.41.46 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 00.41.46 # * pamaury goes to bed after noticing that Sony changed the keycode of some devices 00.43.26 # chrisjj: thanks for the report, I'll keep investigating 00.50.18 Quit pamaury (Ping timeout: 252 seconds) 00.52.41 Join Elfish [0] (amba@84.201.30.174) 00.56.36 Quit alexweissman (Remote host closed the connection) 01.03.01 Quit robertd1 (Ping timeout: 250 seconds) 01.15.36 Quit ZincAlloy (Quit: Leaving.) 01.21.13 # Can anyone tell me what ZEN buttons map to VOL UP and VOL DOWN? 01.43.33 # <__builtin> chrisjj: looks like BUTTON_UP/BUTTON_DOWN to me 01.43.39 # <__builtin> (apps/keymaps/keymap-zen.c) 01.43.44 Join alexweissman [0] (~alexweiss@c-68-51-123-75.hsd1.in.comcast.net) 01.50.50 # Thanks. Got it. Watching the WPS volume indicator, I thought the buttons were having no effect, but now I see the indicator changes on only one in sixteen presses. (I have no audio output currently.) 01.52.10 # Switching to rockbox_failsafe, which shows every vol change. 01.56.44 Quit alexweissman (Remote host closed the connection) 01.58.04 Join alexweissman [0] (~alexweiss@c-68-51-123-75.hsd1.in.comcast.net) 01.59.03 Quit alexweissman (Remote host closed the connection) 02.01.56 Quit skapazzo (Quit: Lost terminal) 02.06.27 Join Bilgus_ph [0] (4cf32773@gateway/web/freenode/ip.76.243.39.115) 02.06.58 # <__builtin> does g#1431 have any possible side effects? 02.07.19 # chrisjj: it all depends on your theme it seems cabbie takes a number of presses to show vol change 02.09.11 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:b18e:fbe0:3f4f:c2e6) 02.11.35 # Yes. Cabbie seems unduly low-res here. The indicator has pixel positions that are needlessly idle. 02.13.15 Quit PurlingNayuki (Ping timeout: 240 seconds) 02.15.00 # well it uses two bitmaps and just hides/shows a portion of the solid color one I believe 02.19.47 # Sure, but the hiding is in five-pixel chunks http://i.imgur.com/Gw6kDrJ.png . 02.21.44 # nope looking at the cabbie source it is using multi bitmaps from a single one 02.22.00 # and there are 9 sets 02.22.38 # This is on Creative ZEN. Do you see this chunking on your device? 02.23.28 # so choose a different theme or edit your own I seriously doubt it will get changed since it works, I see it on the clip+ and fuze with cabbie 02.23.46 # and fuze+ too 02.24.32 # Ah, now I see what you mean in the source. A separate sprite for each one. 02.24.43 # https://github.com/Rockbox/rockbox/tree/1f8ea9fe27313228e5df67ce6447830b5c30e5e3/wps you can grab the source from here and edit it to your liking 02.25.12 Quit krnlyng (Ping timeout: 264 seconds) 02.25.53 # So if I make my own theme, can I provide 45 sprites to cover all volume levels? 02.25.55 # it was probably around before the better way of doing it was incorporated 02.26.10 # NO don't do that there is a better way now 02.26.16 # Ah, the better way. :-) Where can I find that? 02.28.55 # looking 02.30.59 *** Saving seen data "./dancer.seen" 02.32.07 # Thanks. 02.33.03 Join alexweissman [0] (~alexweiss@c-68-51-123-75.hsd1.in.comcast.net) 02.35.39 # I can't find it in the wps manual.. but i will explain it to you 02.36.06 # actually hold on and i will find a theme that uses it 02.37.04 # http://themes.rockbox.org/index.php?themeid=1559&target=sansaclipplus 02.37.23 # Obv this isn't for your player but you can get the idea 02.37.40 # it has a bmp with the bar and the outline of the bar 02.38.00 Join krnlyng [0] (~liar@77.116.118.116.wireless.dyn.drei.com) 02.39.02 # ok i guess 3 states min max and the volume 02.39.33 # let me know once you open it and I can splain it to you 02.45.00 # OK... 02.46.10 # chrisjj: You can set the volume/battery to show numeric level/percentage. I believe themes can override that, though. YMMV. 02.46.31 # ok so first go to the wps/eden dir and open volume9px.bmp 02.46.36 # Got to go now. Check the manual if browsing the menu doesn't give it to you. 02.47.50 # note that there are 3 sets of images 02.49.24 # doesn't look like cabbie follows that directive to me TorC when I made my theme I had to explicity check for the numeric directive and implement it 02.49.30 # Bilgus_ph I've opened it in the Creative ZEN simulator http://i.imgur.com/CbehcDf.png and source editor. 02.49.51 Quit fs-bluebot (Ping timeout: 260 seconds) 02.50.48 Quit bluebrother (Ping timeout: 260 seconds) 02.51.11 # oh sorry you just need to open the zip file this will be on your pc not on a device. sorry 02.51.17 # And I've opened the .bmp http://i.imgur.com/05TNVVz.png 02.51.28 # OK, I've opened the ZIP. 02.51.42 # ok so there are 3 images in that png 02.51.54 # Yup. 02.52.17 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 02.52.38 # now in note pad in WPS/eden.wps 02.52.45 # Yup. 02.53.02 # %?if(%pv, <=, -81)<%xd(Cb)|%?if(%pv, >=, 6)<%xd(Cc)|%pv(0, 0, 16, 9, volume9px.bmp)>> 02.53.16 # at the top %xl(C,volume9px.bmp,0,0,3) 02.53.37 # this loads the image the 3 specifies how many states 02.54.03 # and then the part you pasted does the actual disp 02.54.46 # %pv <-81 says display the min (part b of the image) 02.55.26 # the or %pv>6 display max (part c) 02.56.15 # OK. 02.57.06 # and the last part says else %pv(0,0,16,9, volume9px.bmp) that says display a percentage of the image based on %pv 02.57.31 # do note that the bar part is at the top of the image 02.57.42 Join Senji [0] (~Senji@85.187.103.250) 02.58.01 # OK. Where's the source of this info? I don't see it in https://www.rockbox.org/wiki/CustomWPS . 02.58.27 # wellllll there are several different pages covering themes 02.59.12 # https://www.rockbox.org/wiki/CustomWPS#Bar_Tags 03.00.37 # Ah, I see it. "%XX(x, y, width, height, filename, [options])" 03.01.12 # there is a lot of info missing from that btw there are options that don't work together it will be a trial and error kinda thing tbh 03.01.25 # Tell you want I don't see though. Eden's Volume indicator on the Creative ZEN simulator! http://i.imgur.com/ctHua64.png 03.02.04 Join JanC_ [0] (~janc@lugwv/member/JanC) 03.02.29 # oh I don't know if that theme even works on the actual target it was just the first I saw that looked like it used this method 03.02.52 # Ah, right. 03.03.19 Nick JanC is now known as Guest9817 (~janc@lugwv/member/JanC) 03.03.19 Quit Guest9817 (Killed (sinisalo.freenode.net (Nickname regained by services))) 03.03.19 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC) 03.03.39 Join fs-bluebot [0] (~fs-bluebo@xd9baf76e.dyn.telefonica.de) 03.03.52 # Do you know any working theme using this new method? 03.05.07 # not off the top of my head 03.05.33 # its not really a new method just probably newer than cabbie 03.06.21 # I'm wondering whether the new method has reached production yet. The daily manual doesn't cover it: http://i.imgur.com/vCUyYRS.png . No filename. 03.06.25 Quit Senji (Ping timeout: 268 seconds) 03.07.02 # rest assure it has 03.07.06 # d 03.07.34 # You've seen it working? 03.07.46 # I played with it on my theme but ended up going with the bog standard 03.08.35 # you can also use bar tags to display a bar 03.08.42 # Did you get it working on a particular port? 03.08.51 # without specifying an image 03.09.09 # I messed with it on the sansa clip+ 03.09.38 # it works you just need to be aware some of those options do not play well together 03.10.26 # OK, thanks. I'll look out for a theme that has it working, and start from there. Thanks. 03.10.32 # %V(111,47,16,9,0) %?if(%pv, <=, -81)<%xd(Cb)|%?if(%pv, >=, 6)<%xd(Cc)|%pv(0, 0, 16, 9, volume9px.bmp)>> 03.11.15 # that %v is defining a viewport %v(x,y,w,H 03.16.45 # Thansk, but those %V lines aren't working for me. I've tried it in Eden on Creative ZEN simulator. The indicator does not appear. http://i.imgur.com/nIZuAmS.png 03.19.44 # http://themes.rockbox.org/index.php?themeid=1421&target=sansaclipplus 03.19.54 # this one uses it as well 03.23.00 # unfortunately I am not near my pc atm I can look into it later on if you'll be around, %v are viewports and they for sure work 03.26.20 # Personally I'd try on the actual device to be sure 03.31.31 # Thanks. Trying... 03.35.19 # Seems defunct here. http://i.imgur.com/d56fAu5.png 03.37.36 # That was on the Creative ZEN simulator. On the device, I see the same fail. 03.37.52 # Perhaps themes are just not transportable between devices? 03.42.08 # not completely sure I think they are 03.42.40 # in that last pic that is the failsafe theme 03.42.55 # so something didn't 3work in that last theme 03.43.35 # ill check it in a bit and paste bin something for you to try 03.43.51 Quit Bilgus_ph (Quit: Page closed) 03.44.02 # Thanks. Gotta go to bed now. 03.59.25 Quit [Saint] (Read error: Connection reset by peer) 03.59.35 Join [Sinner] [0] (~sinner@rockbox/staff/saint) 04.08.59 Nick [Sinner] is now known as [saint] (~sinner@rockbox/staff/saint) 04.09.05 Nick [saint] is now known as [Saint] (~sinner@rockbox/staff/saint) 04.10.52 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:10ba:f66f:2f2e:2a4b) 04.14.56 Quit PurlingNayuki (Ping timeout: 240 seconds) 04.31.03 *** Saving seen data "./dancer.seen" 04.43.33 Join Bilgus [0] (ae6611d9@gateway/web/freenode/ip.174.102.17.217) 04.44.02 # chrisjj:ok back did you figure anything out 04.49.05 Quit [Saint] (Remote host closed the connection) 04.49.53 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:10ba:f66f:2f2e:2a4b) 04.51.43 Join [Saint] [0] (~sinner@rockbox/staff/saint) 04.54.14 Quit PurlingNayuki (Ping timeout: 258 seconds) 05.11.39 # TorC, how are you able to format a 64GB microSD card using the FAT32 filesystem? I thought that one of the limitations of FAT32 is that it can only address 32GB of space. Maybe I'm mistaken though? Or maybe I'm just using the wrong partitioning software. 05.20.17 # MrBusiness2: I just used gparted. Most anything /should/ be able to do it. The exfat is specified by the uSD standard as what new cards should be formatted as, and IIRC some format utilities enforce redoing it that way in code. 05.23.14 # Per wiki, fat32 can address up to 2TB with a 512 sector size, and up to 16TB if one increases the sector size to 4kB. 06.03.15 # chrisjj: Here you Go http://www.mediafire.com/file/yrlq9acv7k1ykk0/cabbieedited.zip << unzip into your WPS directory 06.04.09 # turns out I had to weak it a bit to make it work using a single image and then using a bmpstrip for the empty/max states 06.04.17 # *TWEAK* 06.08.28 # MrBusiness2: I just realized I misspoke. exfat is specified by the SD (not uSD) standard for cards >=64GB (actually, I think technically >32GB, but it works out the same in practice). 06.15.08 Quit TheSeven (Ping timeout: 258 seconds) 06.15.23 # Huh? 06.15.30 # So wait, what now 06.15.34 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 06.16.33 # specified by The SD standard not micro SD standard 06.16.45 # But I mean 06.16.50 # for cards bigger than 32 GB 06.16.55 # he's saying that's the exFat standard 06.17.14 # and exFat will do 128GB easily. 06.17.19 # That's not news. 06.17.55 # So I guess my takeaway should be that I need 32GB SD cards formatted to FAT32 for my Sansa Clip Zip then, yes? 06.19.06 # I hope some future Rockbox version offers PAE and exFAT support for that device so I can just cram all my music onto one card and forget about it. 06.19.49 # http://www.rmprepusb.com/ 06.20.17 # That should allow you to format it as fat 32 and barring that http://www.techrepublic.com/blog/windows-and-office/format-fat32-drives-beyond-32gb-limit/ 06.20.29 # Guess I could man up and try to add that myself, but I imagine I'd have to get datasheets for the Sansa Clip Zip's microprocessor, a copy of the exFAT standard, a firm understanding of PAE, and the ability to write device drivers. 06.20.39 # the 32 Gb limit is imposed by windows 06.20.52 # Oh 06.21.14 # Yeah, I feel as though I've put FAT32 partitions onto SD cards larger than that before 06.21.20 # but I may have also bricked them in the process 06.21.35 # and I sort of don't get how they could exceed the limit 06.22.07 # I mean, the paging table, theoretically, only supports 32GB unless they found some way of inserting a janky form of PAE into FAT32 06.23.01 # and next time you brick a SD card that RMprepusb and this > http://www.cgsecurity.org/wiki/TestDisk 06.23.07 # should fix it 06.23.10 # what? I'm pretty sure FAT32 formatted partitions can be larger than 32GB 06.23.25 # sure in linux 06.23.28 # I've been wrong before 06.23.48 # does rockbox not support such partitions? 06.23.52 # and yeah, it was in GParted that I made > 32GB FAT32 partitions in the past 06.24.42 # The maximum disk size is approximately 8 terabytes when you take into account the following variables: The maximum possible number of clusters on a FAT32 volume is 268,435,445, and there is a maximum of 32 KB per cluster, along with the space required for the file allocation table (FAT). You cannot decrease the cluster size on a FAT32 volume so that the size of the FAT is larger than 16 megabytes (MB) minus 64 KB. You cannot format 06.25.25 # You cannot format a volume larger than 32 gigabytes (GB) in size using the FAT32 file system during the Windows XP installation process. Windows XP can mount and support FAT32 volumes larger than 32 GB (subject to the other limits), but you cannot create a FAT32 volume larger than 32 GB by using the Format tool during Setup. You cannot create a file larger than (2^32)-1 bytes (this is one byte less than 4 GB) on a FAT32 partition. 06.25.57 # no AFAIK rockbox supports 128 gb cards 06.27.14 # but 64gb is a pain to build a database in I can't begin to imagine double that 06.28.41 # Yeah, my Rockbox had a kernel panic last time I tried a database function 06.28.46 # granted no card was present 06.29.35 # I have on ocassion tried to build the database with no card inserted It just sat there forever no Panic though 06.31.06 *** Saving seen data "./dancer.seen" 06.31.23 Quit Galois (Quit: Leaving) 06.31.24 # The panic was quite spectacular 06.31.50 # It flashed some message about memory addresses and opcodes, and I do mean flash, because the screen started flashing. 06.32.12 # Had to hold the center button and power button down for what seemed about 10 seconds to get it to shut the hell down 06.32.31 # Rebooted fine 06.32.52 Join Galois [0] (djao@efnet.math.uwaterloo.ca) 06.33.44 # I wonder if any of my music files violate the 4GB limit. I severely doubt it, but there is one possible candidate 06.34.12 # which is my 4 part reading of Naked Lunch as narrated by the late William S. Burroughs himself. 06.34.17 # Great for road trips 06.34.21 # maybe a movie or some really long wav file 06.34.53 # It could be a 320kbps, non VBR mp3 06.34.58 # or rather, four of them 06.35.10 # each of relatively substantial length 06.35.24 # ah, hell, I can probably look it up 06.35.42 # Anyway, I do have a fresh 64GB Lexar card handy, so I guess I'll try this tool out 06.35.49 # After I fulfill my other obligations for the evening 06.36.00 # But before that, a break 06.38.18 Join Bray90820 [0] (~bray90820@173-25-204-30.client.mchsi.com) 06.39.36 Quit Bray90820 (Remote host closed the connection) 07.02.20 Quit scorche|sh (Ping timeout: 260 seconds) 07.11.16 # Bilgus: MrBusiness2: IIRC, there are people using 256GB cards on RB - though I can't vouch for the clip series specifically, I'm not aware of any technical limitation that should prevent it. I'm sure there are folk with 256GB+ volumes on other players. 07.11.51 # Interesting 07.12.30 # I have a slightly larger but older SanDisk that might be RockBox compatible. Maybe it can do it. I'll have to install RockBox on it first to find out 07.12.42 # and it uses some horrible proprietary charger 07.12.49 # It looks like Bilgus took the long explanation for what I apparently said unclearly: Once you buy it, any card is just a bag for bits. How you format it, and why, is your business. 07.13.06 # Interesting. 07.13.07 # Though I'd forgotten about the windows imposed restriction on formatting. 07.13.34 # I wonder if that program you linked can fix my 256GB USB3 stick that crapped out on me 07.13.47 # Probably because it's never mattered to me since 64GB+ became reasonably common. 07.14.52 # Maybe. Can't hurt to try if you've got a lousy paperweight otherwise that isn't worth expensive recovery on. Though I probably wouldn't trust it again anyway. 07.14.54 # Do you even use Windows? 07.14.58 # No. 07.15.19 # Which is why it never mattered. I gave up on Windows about the time Vista came out. 07.15.27 # I was a GNU/Linux guy for several years, prior to an incident I don't care to discuss at any length. 07.15.49 # What's your distro? 07.16.20 # I was a Ubuntu guy until the unspeakable thing happened, and I've never settled on a new distro since then. 07.16.30 # Installed Ubuntu as dual boot, but due to a bug I didn't understand how to work around I reinstalled Windows at the same time and never got it properly working again. Ran gNewSense for a while, these days I'm running Debian. 07.17.14 # If we continue this, we should probably head over to #rockbox-community 07.17.21 # I tried gNewSense. Couldn't precisely tell what it was aiming for, outside of being a Libre distro 07.17.36 # I'm down 07.17.53 # That's pretty much it. 07.18.06 # Okay then 07.18.09 # no need 07.56.29 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 07.56.44 Quit wodz (Client Quit) 07.56.54 Join edhelas [0] (~edhelas@145.133.43.230) 07.57.02 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 07.58.24 Quit pixelma (Quit: .) 07.58.24 Quit amiconn (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) 07.58.39 Join pixelma [0] (~pixelma@rockbox/staff/pixelma) 07.58.40 Join amiconn [0] (~amiconn@rockbox/developer/amiconn) 08.00.54 Quit naleo (Read error: Connection reset by peer) 08.04.56 Quit nlogex (Ping timeout: 240 seconds) 08.10.14 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:10ba:f66f:2f2e:2a4b) 08.13.42 Quit edhelas (Quit: Leaving.) 08.14.11 Join edhelas [0] (~edhelas@145.133.43.230) 08.14.44 Quit edhelas (Client Quit) 08.17.31 Quit girafe (Read error: Connection reset by peer) 08.18.11 Quit PurlingNayuki (Ping timeout: 258 seconds) 08.31.09 *** Saving seen data "./dancer.seen" 08.42.32 Join ender` [0] (krneki@foo.eternallybored.org) 08.43.11 Join edhelas [0] (~edhelas@145.133.43.230) 08.46.18 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:10ba:f66f:2f2e:2a4b) 08.50.31 Quit PurlingNayuki (Remote host closed the connection) 08.50.55 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:10ba:f66f:2f2e:2a4b) 08.55.16 Quit PurlingNayuki (Ping timeout: 260 seconds) 08.57.14 Join petur [0] (~petur@rockbox/developer/petur) 09.01.17 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 09.03.32 Quit edhelas (Quit: Leaving.) 09.19.11 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:10ba:f66f:2f2e:2a4b) 09.26.32 Quit PurlingNayuki (Ping timeout: 260 seconds) 09.30.42 # I'm a windows 10 guy 10.12.53 Join The_Prospector|2 [0] (~The_Prosp@c-73-239-179-79.hsd1.wa.comcast.net) 10.12.59 Join robertd1 [0] (~root@201.208.231.245) 10.13.40 Quit The_Prospector (Ping timeout: 248 seconds) 10.14.49 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:10ba:f66f:2f2e:2a4b) 10.21.38 Quit PurlingNayuki (Ping timeout: 246 seconds) 10.31.12 *** Saving seen data "./dancer.seen" 10.38.08 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 10.46.49 Quit mc2739 (Ping timeout: 265 seconds) 10.51.52 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 10.52.21 Join Senji [0] (~Senji@85.187.103.250) 10.56.21 Quit smoke_fumus (Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/) 11.02.03 Quit Senji (Ping timeout: 250 seconds) 11.14.45 Quit pamaury (Ping timeout: 252 seconds) 11.23.50 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:441a:9397:59af:45c5) 11.28.13 Quit petur (Read error: Connection reset by peer) 11.28.13 Join p3tur [0] (~petur@rockbox/developer/petur) 11.31.59 Nick p3tur is now known as petur (~petur@rockbox/developer/petur) 11.36.51 Join Senji [0] (~Senji@85.187.103.250) 11.44.47 Quit Senji (Ping timeout: 258 seconds) 11.51.57 Join pamaury [0] (~quassel@wks-50-63.mpi-sws.org) 11.51.57 Quit pamaury (Changing host) 11.51.57 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 11.54.15 Join pamaury_ [0] (~pamaury@rockbox/developer/pamaury) 11.57.03 Join Senji [0] (~Senji@85.187.103.250) 12.05.06 Quit Senji (Ping timeout: 258 seconds) 12.07.43 Join skapazzo [0] (~skapazzo@151.9.205.1) 12.16.57 Part robertd1 12.31.13 *** Saving seen data "./dancer.seen" 12.43.31 Quit pamaury_ (Remote host closed the connection) 12.47.59 Join pamaury_ [0] (~pamaury@rockbox/developer/pamaury) 13.26.39 Quit sLite (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) 13.26.56 Join sLite [0] (~quassel@mail.slite.org) 13.37.56 Quit dfkt (Disconnected by services) 13.38.04 Join dfkt_ [0] (~dfkt@unaffiliated/dfkt) 13.43.13 # Bilgus: re cabbiev2 edited, got it. That works on Creative ZEN simulator and device. The volume indicator scale now uses each pixel. Thanks. 13.48.24 Join MikeKennelly [0] (49f80b32@gateway/web/freenode/ip.73.248.11.50) 13.48.41 # hey everyone. can someone add me to SonyNWZE460Port 13.51.48 # hey everyone. can someone add me to SonyNWZE460Port #rockbox 13.51.48 Join robertd1 [0] (~root@201.208.231.245) 13.53.19 # do you mean you want to be able to edit the wiki page? 13.53.31 # Anyone else unable to connect to http://forums.rockbox.org ?? 13.54.01 # yes 13.54.19 # @pixelma* 13.54.33 # MikeKennelly: what do you want to edit on this page ? 13.55.01 # I just want the image, i can't download the port 13.55.38 # the port is not finished 13.56.19 # can you point me to an alternative? 13.56.49 # an alternative to what? 13.58.21 # is there any other available firmware that will work with the NWZ-E465 13.58.25 # data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAAAQABAAD/2wCEAAkGBxITEhUTExMWFRUWFxUVFRUYGBcVFRYVFhUWFhUVFRUYHSggGBolGxUVITEhJSkrLi4uFx8zODMsNygtLisBCgoKDg0OGhAQGi0lHR0tLS0tLS0rLS0rLS0tLS0tKysrLS0tLS0tLS0tLS0tLS0rLS0tLS0rKy0rLTctLTctK//AABEIAMIBAwMBIgACEQEDEQH/xAAcAAABBQEBAQAAAAAAAAAAAAAAAQIDBAUGBwj/xABDEAABAwIEAwUFBQUHAwUAAAABAAIDBBEFEiExQVFhBhMicZEUMoGx0SNCocHwBxVSYpJDU1SCk+HxM3LCFiR0g7P/xAAZAQADAQEBAAAAAAAAAAAAAAAAAQIDBAX/xAAkEQACA 13.58.28 # my bad 13.58.55 # not yet, currently the port is incomplete, it is tricky to install and sound is not working, be patient 13.59.25 # ok cool http://imgur.com/a/V9qYm 14.02.10 # Anyone lese finding font 17-ProFont metrics have gone loopy? http://i.imgur.com/bo5jW0Z.png 14.02.26 # chrisjj: forums have problems, be patient, they should be back by themselves 14.19.31 # chrisjj wanna do me a favor and test out my selective backlight patch? forums are down it is under feature ideas but here is firmware with the patch https://www.mediafire.com/?tl0828dq7lq1c 14.20.09 # pamaury: If you want me something to test on nzw 47x drop me a note 14.21.45 # wodz: sure, yesterday I tried the port on the E580 and ran into some unexpected problem, I realized that Sony made changes to its lcd ioctl() and also changed the key mapping. So I'm systematically going through kernel headers to find all possible cases. 14.22.15 # I'm also almost done with mknzwboot that should hopefully simply the creation of a bootloader 14.22.19 # ough, sound tedious 14.22.20 # *simplify 14.22.28 # wodz: I'm writing scripts ;) 14.27.09 # I also learned the hard way that Sony's fb interface returns bullshit data that is not to be trusted 14.27.32 # Bilgus: sure. Is there a brief? 14.28.05 # on the forums here is the gerrit http://gerrit.rockbox.org/r/#/c/1417/ 14.31.01 # Got it. 14.31.15 *** Saving seen data "./dancer.seen" 14.31.23 # just make a copy of your current .rockbox folder and then unzip into your root the .rockbox/lang/english.lang file and .rockbox/rockbox/creative 14.32.00 # as in the original the copy save as a backup 14.32.50 # or if you are way behind on your current version you can unzip the whole thing 14.36.14 # I renamed .rockbox and unzipped creativezenmozaic-SEL_BL-SL_-rockbox_Vbf177ae-161210.zip to the root. 14.37.40 # "No Backlight on Selected Actions" means No restoration of timed-out backlight upon selected actions" ?? 14.39.53 # yep 14.39.53 # i.e. takes effect after the backlight has been turned off by the idle timer set under Settings, Backlight? 14.40.46 # OK, then it is not working for me. 14.41.24 Quit The_Prospector|2 (Quit: when in doubt, kernel panic) 14.41.33 # yes if it is on and you press keys it resets timeout, don't press keys it turns off and won't turn back on till you press a non filtered key Settings >display > lcd settings > no backlight on selected actions 14.42.25 # On Settings, NBoSA, I engage Volume. On Now Playing, I wait for backlight to go out. The I press Up (VOLUME UP). Unexpectedly, backlight comes on. 14.42.29 # Same with Skip. 14.42.40 # This on real device Creative ZEN 2Gb. 14.42.47 # have to set it up first and if you don't have a hold button which I think you do selective softlock is in Settings > system > no softlock on selected actions 14.43.15 # I'm testing just the backlight effect first. I have made no setting change for softlock. 14.43.18 # did you set it to in in the previous screen? 14.43.25 # ?? 14.43.44 # pamaury: what you mean? 14.44.23 # in NBoSA the first screen has on/off then settings, when you do settings it asks you if you want to save them 14.44.47 # click 'OFF' and it will change to 'ON' 14.45.51 # wodz: the framebuffer interface is supposed to returned info about how the framebuffer is setup, like the line length, width, height, etc. But clearly some data in there is wrong. 14.46.06 # Bilgus: Ah, got it. Not obvious! 14.47.02 # maybe I should make it so it sets it to on automatically or move enable to within the settings? 14.48.22 # Better to follow the existing Rockbox style, I think. One command On, a separate command for Off. 14.48.49 # pamaury: Ah, that what I thought. Probably copy-paste problem on sony side 14.51.14 # headed to work post on forums or in here anything you like/dislike/bugs thanks 14.51.44 # As per e.g. Backlight on Hold. But even better would be to add an indicator of current state. Perhaps an asterisk e.g. 'On *' 14.52.37 # Bilgus: OK, will do... when forums come back up :) 14.58.54 Quit pamaury (Quit: No Ping reply in 180 seconds.) 14.59.19 Quit pamaury_ (Quit: No Ping reply in 180 seconds.) 15.00.34 Join pamaury [0] (~quassel@wks-50-63.mpi-sws.org) 15.00.34 Quit pamaury (Changing host) 15.00.34 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 15.00.41 Join pamaury_ [0] (~pamaury@rockbox/developer/pamaury) 15.02.15 Join The_Prospector [0] (~The_Prosp@unaffiliated/cornman) 15.27.23 Quit MikeKennelly (Quit: Page closed) 15.31.08 Quit wodz (Quit: Ex-Chat) 15.31.33 Join PurlingNayuki [0] (~Thunderbi@114.255.40.10) 15.35.08 Join comradekingu [0] (~comradeki@ti0005a400-4108.bb.online.no) 15.35.39 # I have had my clip+ connected charging for about a day. Unplugged from computer now. 15.35.52 Quit PurlingNayuki (Ping timeout: 245 seconds) 15.36.39 # Says: *PANIC* pc: 30046164 sp:300B8D 15.49.35 # Forums still down after two hours, so perhaps the server needs a kick? PS I'm patient :) 16.02.00 # chrisjj: be more patient ;) 16.02.57 # OK, upping the patience setting now... :) 16.04.33 # pamaury: Re the ZEN BSoD, 50 cycles of USB in/out has shown no BSoD. Though has shown some other fails. 16.04.41 Quit prg318 (Ping timeout: 258 seconds) 16.05.29 # chrisjj: which other fail? 16.05.36 Join nlogex [0] (~filip@CPE30469a4d21ac-CMa84e3f5c8560.cpe.net.fido.ca) 16.07.08 # 1) On unplug, failure to recognise unplug. 2) On unplug, text garbaged at pixel level in the pop-up and on all subsequent screens, until reboot. 16.08.18 Join prg318 [0] (~prg318@deadcodersociety/prg318) 16.08.33 # Re 2) I'd take a screenshot... if someone could tell me if there was a way of taking a screenshot after USB unplug :) 16.08.58 # 1) is a known problem, I never figured out why it happens (although I never tried really since it's not a major issue) 16.09.29 # 2) is weird though, sounds like a theme engine bug 16.09.48 # you could take a screenshot on plug after the unplug? 16.09.57 # 1) In Flyspray? 16.10.11 # No, I just know it exists 16.10.15 # OK. 16.10.21 # I think the hardware fails to fire the interrupt on unplug sometimes 16.10.29 # probably needs another workaround 16.10.30 # 2) Does theme engine affect the USB screen?? 16.11.25 # 2) I would need to check (or rather ask someone who knows about it) but theme engine affects pretty much everything I think 16.13.00 # Aw. Well, I can say something else probably went wrong first. Because the strip of garbage was sized placed and coloured as if it was a corrupt pop-up of about 30 chars, rather than the normal pop-up "Loading..." 16.14.24 # chrisjj: to which pop-up after you referring to? There is no pop-up on unplug except if you put a new version of the firmware 16.15.11 # I refer to the pop-up I see on every unplug (no firmware update). 16.15.37 # By pop-up I mean the fleeting overlayed bordered text message. 16.16.45 # ah you are right, I forgot there was one because it usually disappears really quickly 16.17.39 # so you are saying that instead of 'Loading' you see garbage, but still displayed as a pop-up? 16.19.32 # It may have been instead or in addition to Loading... 16.19.49 # It was definitely displayed as a pop-up. 16.21.14 # I will file a report, after finishing this BSoD testing. 16.22.03 # chrisjj: I admit I tend not to read flyspray anymore, but feel free to report it there 16.22.15 # And if it recurs, I'll try clearing the font cache (if I can find out how) since my hunch is that it got trashed. Nothing but font on screen was trashed. 16.22.31 # Where's the better place you read? 16.24.06 # well there is a hack for fonts: on usb, the code cannot access fonts (since they are on the storage), so the font code keeps a local cache of most used glyph. If some glyph are not in ram when called, I don't know what happens. It might also be that there is a glyph cache corruption either in ram or on file 16.24.24 # chrisjj: just tell me and hope I won't forget :-p I know this is not really optimal 16.25.04 # I should use the bug tracker 16.25.05 # OK. Perhpas best is for me to file in Flyspray AND tell you :-) 16.25.11 # yes :) 16.27.19 # Your glyph theory doesn't sound llikely to me. Just as L o a d i n g was clearly already in cache, so I'd expect the longer message's glyphs to be... unless that mystery message was in Japanese! :) 16.29.55 Quit gluytium_ (Ping timeout: 240 seconds) 16.31.19 *** Saving seen data "./dancer.seen" 16.37.42 Join Senji [0] (~Senji@85.187.103.250) 16.41.07 # http://forums.rockbox.org/ now up. 16.43.33 # pamaury: re your screendump suggestion, screendump on Creative ZEN is semi-bust. Immediately after the dump, the device hangs in WSoD. 16.45.23 # sounds like a bug with screendump, maybe no one fixed it to explain how handle 24-bpp 16.45.44 # I'll look into it 16.54.31 # I'll file a report. 16.55.21 # On the BSoD, your " I traced it back to a hardware bug, that I can reproduce fairly well (it's still random but at least I know what happens).", can you tell me how to reproduce it from the user end? 16.57.09 # There is no easy way to reproduce it as a user, I used some dev tools 17.00.25 # it's basically the same principle as rebooting all the time except that you replace the "boot rockbox" by "perform those register read/write and see if you triggered the hardware bug". I managed to narrow down the sequence to a few read/writes 17.01.33 # I believe the bug is fundamentally "random" though so there no easy way to trigger it with a 100% chance 17.03.25 # OK. 17.04.15 # Then it seems like my soak test of a few thousand boots is the best way for the boot case. 17.04.37 # And manual plug/unplug is the best way for the USB test. 17.16.58 # Anyone, does Seek left and Seek right work on your player? They don't on my Creative ZEN. :( 17.25.35 # probably a key mapping thing 17.30.33 # So, do they work for other devices? 17.31.12 Join Bilgus_ph [0] (~Bilgus_ph@108.100.135.159) 17.32.43 # I think, I mean I almost never use them but we would know if they were broken. Most likely I forgot to map seek/rewing on the zen 17.33.08 # CHRISJJ: did seek not work before you installed nBosA ALSO does it work in the sim Zen? 17.34.19 # pamaury: thanks. I'll check the .c. 17.34.33 # I least I know it works on the ZEN X-Fi 17.34.40 # Bilgus_ph: Will check. 17.35.27 # BTW, I see no sim for your nBosA. 17.36.42 # chrisjj: just had a quick look at keymap-zen.c and there is this line: 17.36.42 # { ACTION_WPS_SEEKFWD, BUTTON_RIGHT|BUTTON_REPEAT, BUTTON_NONE }, 17.36.42 # but it looks somewhat suspicious, I think it should be 17.36.42 DBUG Enqueued KICK pamaury_ 17.36.42 # { ACTION_WPS_SEEKFWD, BUTTON_RIGHT|BUTTON_REPEAT, BUTTON_RIGHT }, 17.38.27 # PAMAURY the button lookup should allow button_none there it looks for the prebutton|button_none iirc 17.39.37 # I don't understand what you just said 17.40.20 # CHRISJJ there is no sim with nBosa but if seek works on the sim then it points to nbosa or your device 17.43.15 Quit pamaury (Remote host closed the connection) 17.44.44 Quit Bilgus_ph (Ping timeout: 258 seconds) 17.46.47 Quit pamaury_ (Ping timeout: 250 seconds) 17.47.26 Quit petur (Read error: Connection reset by peer) 17.58.09 Join Bilgus_ph [0] (~Bilgus_ph@108.100.7.89) 18.01.42 # PAMAURY in action.c do_button_lookup or something along those lines it has button,prebutton which is what you just posted.. i'm pretty sure it allows you to have button_none as the prebutton and will allow any prebutton in that case 18.02.15 Quit dfkt_ (Ping timeout: 256 seconds) 18.02.41 Quit Bilgus_ph (Read error: Connection reset by peer) 18.04.29 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 18.12.28 Quit elensil (Quit: Leaving.) 18.31.22 *** Saving seen data "./dancer.seen" 18.33.20 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 18.37.41 # Bilgus: the question is not whether BUTTON_NONE is allowed. I'm just saying it's wrong in this case 18.40.49 # chrisjj: did you try the keymap fix I suggested? 18.43.39 Quit tchan (Quit: WeeChat 1.6) 18.43.57 # pamaury: "{ ACTION_WPS_SEEKFWD, BUTTON_RIGHT|BUTTON_REPEAT, BUTTON_RIGHT },"? 18.44.11 # No. I don't have a RB build setup. 18.45.28 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:2112:e4cd:7f77:fe9) 19.02.30 Join paulk-collins [0] (~paulk@gagarine.paulk.fr) 19.02.32 Join Link8 [0] (~me@145.133.168.70) 19.05.56 # i have a question 19.06.12 # i use an aux cable to listen to music with my ipod 19.06.27 # the left speaker has no sound all of a sudden 19.06.34 # i tried changing the aux cables 19.06.38 # still the same effect 19.06.53 # with earplugs in the ipod both earplugs work so it isnt the ipod 19.07.01 # if i play a cd in the car both speakers work 19.07.10 # just not thorugh the aux cable anymore now 19.07.12 # what can it be? 19.07.34 Join scorche|sh [0] (~scorche@rockbox/administrator/scorche) 19.08.13 # Link8: did you check wit the OF ? could be bad jack 19.08.24 # of? 19.08.58 # maybe the jack of the car stereo is messed up or something 19.09.03 # whats OF 19.11.54 # original firmware, apple firmware 19.12.34 # but I suspect bad jack or bad connection in your car stereo 19.12.45 # from the car stero right 19.12.49 # its not the fw 19.19.10 Quit ruhan (Quit: Connection closed for inactivity) 19.23.07 Join pamaury_ [0] (~pamaury@rockbox/developer/pamaury) 19.23.38 Quit pamaury (Ping timeout: 258 seconds) 19.49.11 Join dfkt [0] (~dfkt@unaffiliated/dfkt) 19.49.12 Quit dfkt (Remote host closed the connection) 20.01.58 Quit PurlingNayuki (Ping timeout: 258 seconds) 20.26.47 Join edhelas [0] (~edhelas@145.133.43.230) 20.27.00 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:2112:e4cd:7f77:fe9) 20.27.10 Join girafe [0] (~girafe@LFbn-1-8015-136.w90-112.abo.wanadoo.fr) 20.31.06 Quit PurlingNayuki (Remote host closed the connection) 20.31.25 *** Saving seen data "./dancer.seen" 20.33.02 Join tchan [0] (~tchan@lunar-linux/developer/tchan) 20.46.37 Join petur [0] (~petur@rockbox/developer/petur) 20.58.25 Join TheLemonMan [0] (~root@unaffiliated/thelemonman) 21.01.25 Join Senji_ [0] (~Senji@85.187.103.250) 21.04.27 Quit Senji (Ping timeout: 258 seconds) 21.06.56 Quit Moarc (Ping timeout: 265 seconds) 21.08.54 Join Moarc [0] (~chujko@a105.net128.okay.pl) 21.09.34 Join lahoal [0] (bf72dd85@gateway/web/freenode/ip.191.114.221.133) 21.09.46 # bluebrother: do I need to do something special to have c++ files in mk*boot ? 21.09.47 # hi there 21.10.10 # it fails with a weird error 21.11.51 # hey guys just a quick question, related to the ipod 7th gen (MC293) and its database 21.12.14 # lahoal: ask and someone will answer if he knows the answer 21.12.15 # I know on the stock fw the database stays on the ram which is 64mb 21.12.33 # and it kinda limits the amount of tracks you can have in it 21.12.51 # (thinking about replacing the hdd to a raid of microsds) 21.12.59 # so how does that work on rockbox :O 21.14.12 # pamaury_: tried to lurk on manuals and stuff but couldn't get an answer, maybe I'm just searching wrong 21.14.15 # the database on rockbox has virtually no limit (it's on the disk) as far as I know 21.14.38 # [Saint]: do you concur? 21.14.43 Nick pamaury_ is now known as pamaury (~pamaury@rockbox/developer/pamaury) 21.15.12 # I saw a bug reported related to that, the device was refreshing it way to often causing the stock hdd to over-work. 21.15.31 # if I have a GIANT database, say, dunno 200.000 tracks 21.15.35 Quit edhelas (Ping timeout: 240 seconds) 21.15.49 # which would be kinda 256mb size 21.16.04 # wouldn't the fw be working kinda all the time, reading it over and over? 21.16.33 # I just bought the replacement parts on ebay and I'm sure gonna try it anyway, but I wanted to have a head start on how it would work :P 21.16.34 # I think we have a recent problem that the database is now entirely on disk (the ram optimization was disabled), making it seek the disk much more than before 21.17.18 # on regular (big) databases you can use Indexes to lighten up certain queries, 21.17.20 # but otherwise the database is refreshed in the background. Of course scanning tat many tracks will take some time 21.17.38 # yeah totally 21.18.36 # I guess it doesn't hurt to try it anyway 21.18.42 # sure ;p 21.27.59 # hey and how stable is it actually? 21.28.19 Join smoke_fumus [0] (~smoke_fum@dynamic-vpdn-93-125-65-113.telecom.by) 21.29.19 # I don't know, I don't have the ipod 7th 21.29.28 # you'll have to wait until someone answers that 21.30.20 Quit smoke_fumus (Client Quit) 21.32.03 Quit robertd1 (Ping timeout: 258 seconds) 21.32.06 Join PurlingNayuki [0] (~Thunderbi@114.255.40.10) 21.32.56 Join alexweis_ [0] (~alexweiss@c-68-51-123-75.hsd1.in.comcast.net) 21.34.40 # sure :) 21.35.29 Quit alexweissman (Ping timeout: 258 seconds) 21.36.39 Quit PurlingNayuki (Ping timeout: 258 seconds) 21.41.29 Quit amayer (Quit: Leaving) 21.42.25 # pamaury: on the site there's logs of this chat through forever 21.42.35 # I'm searching on there if anyone has talked about databases 21.42.40 # there's interesting info 21.43.19 # The first thing you'll learn is that virtually no dev cares about the database :) 21.43.39 # yeah I don't think any of us dev really use the database :) 21.43.52 # Maybe because we know how it works, kinda 21.45.13 # hah 21.47.00 Join robertd1 [0] (~root@201.208.231.245) 21.47.07 Join lebellium [0] (~chatzilla@89-93-179-5.hfc.dyn.abo.bbox.fr) 21.57.11 # damn, libtools.make only knows about C and not C++, it's going to be tricky to change that 21.58.36 Quit michaelni (Read error: Connection reset by peer) 22.01.58 # alright guys, heading off 22.02.05 # bye ~  22.02.07 Quit lahoal (Quit: Page closed) 22.05.39 Quit robertd1 (Ping timeout: 248 seconds) 22.08.03 Join robertd1 [0] (~root@201.208.231.245) 22.15.43 Join michaelni [0] (~michael@213-47-41-20.cable.dynamic.surfer.at) 22.16.54 Join Bray90820 [0] (~bray90820@173-25-204-30.client.mchsi.com) 22.20.21 Part robertd1 22.29.35 # pamaury: what I was getting at earlier was in do_button_check --> if (items[i].button_code == button) { if ((items[i].pre_button_code == BUTTON_NONE) || (items[i].pre_button_code == last_button)) <-- meaning if pre button is button_none It allows any pre button as long as button is right 22.29.55 # Bilgus: and that's why it's wrong 22.30.10 # you want to trigger the action *only* when prebutton is BUTTON_RIGHT 22.30.30 # otherwise the seek action is trigger on every repeat (since BUTTON_RIGHT|BUTTON_REPEAT matches BUTTON_NONE) 22.30.47 # so basically you are constantly re-asking to seek, which I am not sure the code was designed to handle 22.31.16 # oh ok I see what you are getting at 22.31.27 *** Saving seen data "./dancer.seen" 22.31.36 # the code works the other way around: on BUTTON_RIGHT you do nothing, then on the next tick, either you get RIGHT|REL -> skip, or RIGHT|REPEAT -> seek, and then if you seek, on REL you stop seek 22.32.17 # although I think a bunch of other keymaps are the same 22.33.07 Join PurlingNayuki [0] (~Thunderbi@114.255.40.10) 22.33.23 # I'm pretty sure you will break seek if you do that tbh 22.34.03 # stop seek looks for a button|rel, button|rep and 22.34.29 # I think seek works by setting each run through 22.34.29 # stop seek requires repeat before 22.35.22 # Button, Prebutton like the key map 22.35.42 # idk ill test and brb 22.35.55 # Anyway, I'm just saying the answer is not obvious, it depends on how seeking is implemented, something which I don't want to know :-p 22.36.16 # most probably looking at the other keymaps is the simplest solution 22.37.32 Quit PurlingNayuki (Ping timeout: 260 seconds) 22.37.58 # bluebrother: I'm puzzled between adding c++ support to libtooks.make (seems annoying) and simply finding an implementation of des in C 22.38.58 # I just checked 20+ and all had Button_none as PREBUTTON 22.39.29 # I canged it to have button_right as the pre in fuze+ and it breaks seek 22.39.42 # seeks for a moment then immediately stops seek 22.39.49 # changed* 22.39.51 # then seek must rely on receiving events every tick 22.40.07 # which is weird because then stopseek looks useless 22.40.19 # agreed 22.40.55 # but perhaps in a different context it is needed 22.41.16 # maybe 22.42.21 # FMS doesn't seem to care that the pre was changed, wonder if chrisjj has a wonky fwd button 22.42.27 Quit paulk-collins (Remote host closed the connection) 22.43.26 # yeah, maybe it was a problem with the button or the button driver 22.43.36 # but I guess he would have noticed if left/right didn't work 22.48.26 Quit TheLemonMan (Quit: "It's now safe to turn off your computer.") 22.54.54 Join edhelas [0] (~edhelas@145.133.43.230) 22.59.36 Quit girafe (Read error: Connection reset by peer) 23.00.14 # "wonder if chrisjj has a wonky fwd button" Sorry, my report was inaccurate/unclear 23.05.13 # you said seek left doesn't work correct? 23.05.21 # sorry seek right 23.07.25 # Yes, I did and that is correct. 23.08.54 # ok so has that always been the case on your player or only since you installed the selective backlight firmware? 23.08.55 # For truth: On DEVICE, left works generally, but has no effect for Seek Left. Right works generally inc. for Seek Right. 23.09.40 # That's for unit P with NBoSA. 23.10.13 # oh ok so it won't rewind then ok so put your back up back on device and does it still not rewind 23.10.59 # On DEVICE unit T without NBoSA, left works inc. for Seek Left 23.11.30 # And FWIW, on SIMULATOR, Left works inc. for Seek Left. 23.11.36 # ok so before you put on nBoSA dis seek left work on unit P? 23.11.45 # dis/DID* 23.11.51 # Now ininstalling NBoSA for test... 23.12.48 # tbh sel backlight doesn't intercept any key presses it only reads them selective softlock is the one that would block a keypress 23.13.08 Quit prg318 (Quit: WeeChat 1.6) 23.14.30 # No change. I.e. On device unit P now without NBoSA , left works generally, but has no effect for Seek Left. Very odd. I will diff the two installations. 23.15.54 # Just spotted: "[22:05] you said seek left doesn't work correct? [22:05] sorry seek right [22:07] Yes, I did and that is correct." FTR I'm saying what doesn't work is Seek Left. Seek Right works. 23.17.35 Join prg318 [0] (~prg318@deadcodersociety/prg318) 23.17.39 # I'm going to say it is probably an issue with the device 23.19.04 # save your backup .rockbox folder and put a fresh install on ie delete the rockbox folder and put on the latest DEV install 23.27.40 Join amayer [0] (~amayer@mail.weberadvertising.com) 23.29.02 Quit ender` (Quit: Eighty percent of all people consider themselves to be above-average drivers.) 23.29.35 # Mystery solved. It's an issue with the device. :) A wonky button which amazingly registers a down event but not a sustained down state, unless I press it off-centre. 23.29.42 # Sorry for the false alarm. 23.32.05 # pamaury: I found a longer pop-up message on USB unplug, which could have been the one I saw corrupted: "Error accessing playlist control file" 23.32.53 # this one is fairly common, but it should not corrupt anything 23.41.20 # Sure, but it addresses your "There is no pop-up on unplug except if you put a new version of the firmware". This could be the pop-up I saw, corrupted. What I see on a new version of the firmware is not what I'd call a pop-up. It is a new screenful (on ZEN). What do you mean exactly by "pop-up"? 23.42.30 # the playlist access error message is a pop-up: it's displayed in a gray box at the center of the screen 23.46.53 # OK, then I think we agree your "There is no pop-up [additional to Loading...] on unplug except if you put a new version of the firmware" is incorrect. No problem. And we don't know anything more about that corruption. In 20 more test cycles, I found no repeat. 23.52.13 # This pop-up is supposed to be really rare 23.52.48 Quit edhelas (Ping timeout: 264 seconds) 23.52.49 # "Error accessing playlist control file" isn't rare here on ZEN. 23.52.51 # and unrelated to corruption, I can see it once in a while on all players, it's a race condition no-one bothered to fix 23.54.40 # and after this error, you said every piece of text is corrupted until reboot? 23.56.45 # <__builtin> how do I make all clients in the build cluster auto-update? 23.57.25 # pamaury: yes. Though I didn't try changing theme or font. 23.58.06 # chrisjj: which theme are you using? 23.58.16 # __builtin: they update the script automatically I think, assuming you pushed it to the repo 23.58.34 # BTW, back on v131119 I got "Error accessing playlist control file" -- fixed by upgrading to 131121.