--- Log for 30.12.120 Server: card.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 24 days and 16 hours ago 00.14.16 Quit sakax (Remote host closed the connection) 00.19.36 Join Strife89|Home [0] (~quassel@adsl-74-250-150-57.ags.bellsouth.net) 00.21.20 Quit Strife89 (Ping timeout: 265 seconds) 01.58.17 *** Saving seen data "./dancer.seen" 03.28.06 Join Rower [0] (~Rower@78-73-72-39-no2340.tbcn.telia.com) 03.58.20 *** No seen item changed, no save performed. 04.08.17 Join lebellium [0] (~lebellium@89-92-69-66.hfc.dyn.abo.bbox.fr) 04.16.59 Quit mendel_munkis (Read error: Connection reset by peer) 04.17.11 Join mendel_munkis [0] (~mendelmun@ool-43568247.dyn.optonline.net) 05.58.22 *** Saving seen data "./dancer.seen" 06.21.45 Join ZincAlloy [0] (~Adium@ip5f5acf9f.dynamic.kabel-deutschland.de) 06.26.15 Quit ZincAlloy (Ping timeout: 265 seconds) 06.32.09 Join ZincAlloy [0] (~Adium@2a02:8108:943f:d824:482d:646b:d611:ec92) 06.37.11 Quit ZincAlloy (Ping timeout: 272 seconds) 06.37.55 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 06.49.01 Join ZincAlloy [0] (~Adium@2a02:8108:943f:d824:c5e:a6bf:4666:f42a) 07.32.35 Quit Stanley00 () 07.33.45 Quit St3ak (Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net) 07.38.55 Join St3ak [0] (~st3ak@st3ak3000.powered.by.lunarbnc.net) 07.41.58 Quit St3ak (Client Quit) 07.43.25 Quit pamaury (Ping timeout: 264 seconds) 07.58.26 *** Saving seen data "./dancer.seen" 08.22.11 Join St3ak [0] (~st3ak@st3ak3000.powered.by.lunarbnc.net) 08.34.19 Join massiveH [0] (~massiveH@ool-18e4e82f.dyn.optonline.net) 08.43.01 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 08.54.56 Quit pamaury (Ping timeout: 256 seconds) 09.23.56 Quit prof_wolfff (Ping timeout: 240 seconds) 09.29.49 Quit massiveH (Quit: Leaving) 09.34.57 Quit mendel_munkis (Read error: Connection reset by peer) 09.35.15 Join mendel_munkis [0] (~mendelmun@ool-43568247.dyn.optonline.net) 09.43.21 Join langest [0] (~langest@193.9.112.117) 09.58.27 *** Saving seen data "./dancer.seen" 09.59.45 Quit langest (Quit: Leaving) 10.13.27 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 10.13.51 Join fs-bluebot_ [0] (~fs-bluebo@55d4be35.access.ecotel.net) 10.13.54 Quit fs-bluebot (Ping timeout: 265 seconds) 10.15.21 Quit bluebrother^ (Ping timeout: 265 seconds) 10.25.25 Join MrZeus [0] (~MrZeus@2a02:c7f:70d0:6a00:4c:438d:fe24:711a) 10.57.54 Join sakax [0] (~r0b0t@unaffiliated/r0b0t) 11.35.30 # Hi, I'm not sure if anyone is aware, but I think the rockbox wiki is down 11.38.26 Quit sakax (Ping timeout: 264 seconds) 11.52.23 Quit kakaka (Ping timeout: 240 seconds) 11.56.16 # speachy: one for you I think ^^ 11.57.26 # speachy: looks serious. DB crash of some kind. 11.58.30 *** Saving seen data "./dancer.seen" 12.28.19 Join kakaka [0] (~koniu@gateway/tor-sasl/koniu) 12.36.26 Join jdarnley [0] (~J_Darnley@d51A44418.access.telenet.be) 12.37.04 Quit J_Darnley (Ping timeout: 246 seconds) 12.44.32 Quit fauweh (Quit: ) 12.45.16 Join fauweh [0] (~root@ithaqua.unzane.com) 12.48.38 Quit mendel_munkis (Ping timeout: 264 seconds) 12.51.22 Join knightworx [0] (~KNiGHT-W0@cpe-173-88-86-123.columbus.res.rr.com) 12.54.05 # iPod 5.5 gen30 GB drains battery when connected to charger. Any ideas? I know it sounds crazy, but that’s an actual problem I am currently going through. The only way the iPod charges if rockbox is on is if I have it locked with the hold switch. If the screen is on it’ll lose a percentage every few seconds or so. But when it’s off, then it charges. Any way I could fix that? I copy/pasted this from a thread o 12.54.05 # n the rockbox subreddit, but it is impacting me now as well. The OP has a modded hdd, I do not. They were also using the latest nightly at the time, and found that it's still happening on the latest stable version, much like myself. 12.54.56 # Yes, forced charging is on. i left and came back and it had charged 10 percent with the screen off. the second I turned the screen on it started bleeding very hard 12.55.42 # On a dedicated charger plugged into a power strip, it doesnt deteriorate no matter the screen status. only when plugged into a computer. 13.00.25 # knightworx: there's a huge difference right there. computers usually have a limit to how much power they provide over USB. 13.00.40 # i'd grab a power meter and see for yourself. 13.00.53 # there's usb watt meters you can find on the cheap 13.01.15 # knightworx: dedicated chargers usually can provided up to 3A at 5V. 13.01.15 # but it doesn't do it when on the default firmware. and i'm using a powered hub. 13.01.28 # well it sounds like a USB issue in any case. 13.01.39 # try some diagnostics 13.02.28 # the rockbox wiki is just getting an error for me, says the database needs to be recovered 13.02.32 # i have usb power meters for this very reason 13.02.33 # BDB0087 DB_RUNRECOVERY 13.02.38 # nihilazo: we know. 13.02.49 # the only person that can fix isn't around 13.03.29 # ah ok 13.03.43 # oh, sorry. Didn't notice somebody reported it before in the log 13.03.59 # "kalube | Hi, I'm not sure if anyone is aware, but I think the rockbox wiki is down" 13.04.10 # still on my screen here 13.04.41 # knightworx: i'd grab a power meter and see what you can learn. it will help you talk to the people that might be able to help. 13.04.49 # knightworx: if you need an example... 13.05.21 # I mean it sounds like a driver issue but i would have no way of fixing that 13.05.41 # knightworx: iirc rockbox debug menu on the 5g reports battery consumption in mA, see what it spits out with charger plugged/unplugged 13.06.47 # IS the powered hub connected to your PC? It's possible that it doesn't register properly and the PC limits it to 100ma which could maybe cause that 13.07.07 # https://www.ebay.com/itm/USB-Power-Tester-Voltage-Current-Capacity-Meter-4-20V-3A-Test-Chargers-Cables/123946852024 13.07.13 # yes, the powered hub is connected to both my pc and an AC adapter 13.07.21 # this is what i was thinking of 13.07.36 # i bought it in order to run multiple sensors for my VR setup 13.07.38 # i've been using mine to diagnose power issues 13.08.21 # braewoods: damn only one person can fix the rockbox wiki?! 13.08.46 # speachy is our admin and i only know of him having access to the necessary systems 13.08.59 # kalube: my computer sees this device as 30 different things, the main one being a keyboard, so it sounds like that may have something to do with it 13.09.13 # i know, bus factor and all. 13.09.41 # knightworx: like i said, knowing how much power is being drawn could be very useful. 13.09.47 # it would help eliminate some stuff. 13.09.55 # instead of it being stabs in the dark 13.10.26 # do you know where i could find information on what it's supposed to draw 13.10.29 # knightworx: 30?? The keyboard is because rockbox defaults to being a HID device, it's very possible that your computer just doesn't allow more than 100ma draw for HID devices, although weird. Maybe try changing the input mode to storage and see if that helps 13.10.45 # knightworx: no idea but you can correlate that with your other observations 13.10.51 # Look at the power draw in rockbox battery debug when the device is unplugged, then plug it in and see how it changes 13.10.55 # knightworx: how much varies with the device 13.11.22 # maybe there's a debug for it but an external meter can be useful as well 13.11.43 # knightworx: but you need some way to know the power flow 13.11.54 # under the circumstances where you know it is working 13.11.59 # but if it's the OF 13.12.03 # then i doubt it has this 13.12.11 # in which case you need the external meter 13.12.26 # i went to battery in the debug and you can visibly see it plummet when its plugged in 13.12.28 # lol 13.12.39 # Oh that's definitely wrong 13.12.40 # values? 13.13.04 # if true it suggests insufficient external current to supply basic needs 13.13.12 # so it has to drain the battery 13.13.45 # Ibat: fluctuation between low 70s to ~99 mA 13.14.13 # Vbat: 289 - 380 mW 13.14.58 # knightworx: What's the before / after current? 13.15.02 # its constantly swapping between charging and discharging, which i would assume might have something to do with it 13.15.22 Join S|h|a|w|n [0] (~shawn156@unaffiliated/shawn156) 13.15.45 # Actually, before getting into the gory details, if you plug it straight into a USB port on your motherboard, does that fix it? How about a wall adapter for a phone? 13.18.17 # on the phone charger plugged into the wall it give me no vbat/ibat usage (says 0 for both), though with the screen on it still says discharging 13.18.34 # i know for a fact it charges with the screen off fully, because i used it last night, 13.18.50 # i have the brightness turned to like 20% btw 13.19.29 # Seems like a dodgy ipod to me... When booted into stock firmware does it charge normally? 13.20.36 # how do i boot into normal firmware? My observations from before were before i installed rockbox... older ipod batteries can be sketchy so i was watching for drain and didn't notice anything weird offhand 13.22.14 # Hold menu and select until the screen goes blank, then release select and keep holding menu 13.22.20 # Basically, hold menu while it boots up 13.22.27 # oh ok 13.24.22 Join prof_wolfff [0] (~prof_wolf@148.red-83-49-157.dynamicip.rima-tde.net) 13.26.31 # ...yeah absolutely no longer getting weird battery power level issues as it now says i am fully charged when on stock firmware 13.26.53 # its almost as if the power indicator in rockbox was incorrectly monitoring it? 13.27.47 # no idea 13.28.25 # well i mean at least via process of elimination it's certainly a rockbox thing 13.29.11 # braewoods: would you happen to know anything about the iPod classic (6g) ? I'm hoping to get hold of a datasheet but they only seem to be available for the S5L8700X, not the S5L8702 in the classic 13.29.49 # The headers in rockbox give a lot of insight, it looks like the initial porting was done entirely through reverse engineering... 13.29.51 # it's not uncommon for a single datasheet to cover multiple chips that only differ slightyl. 13.30.26 # it sounds like X is to cover all the variants using the same scheme 13.30.35 # They are similar, it's mostly register addresses that vary, but the existing datasheet for the S5L8700X definitely doesn't include the S5L8702 13.30.48 # The X doesn't replace the 2 13.31.56 # it's an apple chip it seems so there's probably no public datasheet 13.32.21 # Yeah... You've confirmed my suspicions 13.32.45 # Impressive that it got a rockbox port considering, it seems like a great deal of research was done to get it going 13.32.52 # apple prefers to keep all their hardware details close to the vest 13.32.59 # so 13.33.08 # part of why i don't buy ipods and such 13.33.15 # not that android is generally any better 13.34.25 # I'd be prone to agree, I'm certainly not interested in Apple's newer hardware, I doubt I'd have bough a 6G if I didn't know it supported Rockbox 13.34.54 # they're basically engineered to be mindless consumer devices 13.34.58 # and we're not that market 13.35.11 # True that 13.58.33 *** Saving seen data "./dancer.seen" 14.02.05 Join mendelmunkis [0] (~mendelmun@ool-43568247.dyn.optonline.net) 14.33.12 # kalube: as an individual that has owned a 6th gen since launch and is going to install rockbox on it, i can tell you it's only been ported fairly recently, and requires a piggyback off of another, (now defunct) projects bootloader. I remember reading about how it'd never get cracked because of how it was setup, so needless to say i got excited to see that it was available and supported 14.34.09 # knightworx: yeah originally it used the emcore bootloader iirc, although I thought it first got rockbox in 2012? 14.34.37 # I guess what i meant was, it took 6 years for it to happen lol 14.34.50 # Ah yeah lol 14.35.06 # It's a really really nice device 14.37.27 # Mine is 13 years old and just has a minor battery issue, so absolutely. 14.37.57 # wiki fixed. 14.38.11 # sorry it took so long; I've been installing flooring. 14.38.24 # kalube: thanks for reporting it 14.52.02 # unfortunately un-wedging the wiki requires root access. 14.55.30 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 15.12.57 # Ah right, that makes sense 15.21.34 Quit pamaury (Ping timeout: 246 seconds) 15.23.42 # speachy: is there anything better out there? the website seems to go down at least once a month. 15.26.36 Quit _bilgus (Ping timeout: 240 seconds) 15.35.04 # mediawiki is pretty good, and I guess migrating to something backed by CI (like gitlab CI) where the entire website is stored on git and supports clean builds so you aren't dependant on a root password or a particular environment 15.36.13 Quit fs-bluebot_ (Ping timeout: 264 seconds) 15.36.26 Quit bluebrother (Disconnected by services) 15.36.31 Join bluebrother^ [0] (~dom@rockbox/developer/bluebrother) 15.36.44 Join fs-bluebot [0] (~fs-bluebo@55d4a1d0.access.ecotel.net) 15.39.11 # having a wiki backed by git with the web copy built from what people commit into the git repo is a cool idea, I'm not sure how that would look implemented for rockbox 15.41.01 # I've been contributing to the postmarketOS project, and their wiki has a git repo (https://gitlab.com/postmarketOS/wiki) and it seems to sync up all wiki edits to git commits, so there's always a safe copy of the wiki that just gets imported into and synced with a mediawiki instance (https://wiki.postmarketos.org/wiki/Main_Page) 15.48.23 # that's really cool 15.48.45 # didn't know pmos did it like that, I was thinking kinda like how gh pages works but multiple users have commit access and that is how the wiki is edited 15.52.09 Quit Rower (Ping timeout: 268 seconds) 15.58.36 *** Saving seen data "./dancer.seen" 16.01.59 # I was incorrect. my ipod seems to be on the brink of a dead battery with the screen on the entire time it was in stock firmware as well 16.10.15 Quit MrZeus (Read error: Connection reset by peer) 16.11.44 Join MrZeus [0] (~MrZeus@90.218.41.119) 16.14.22 Join _bilgus [0] (~bilgus@cpe-107-11-237-184.columbus.res.rr.com) 16.16.17 Join efqw [0] (uid412670@gateway/web/irccloud.com/x-hzcaexyyyyetxlwn) 16.16.32 Quit _bilgus (Read error: Connection reset by peer) 16.17.21 Join _bilgus [0] (~bilgus@cpe-107-11-237-184.columbus.res.rr.com) 16.17.33 # knightworx: replacement is usually cheap for those 16.17.55 # depends on the model though 16.18.21 # did you say it was a 5.5 earlier? I think those are fairly easy to replace the batteries in. Not sure though 16.18.48 # yeah i have another one on the way 16.19.00 # i just am not sure if the battery drain is rockbox related or not 16.19.32 # because its situational and not indicative of a normal old battery 16.20.33 # the battery was not doing this during the time before I installed it as well, though im not 100% for certain 16.21.12 # its also VERY odd to me that someone else had the exact same battery issue as me, model and all 16.26.59 Quit _bilgus (Remote host closed the connection) 16.28.07 Join _bilgus [0] (~bilgus@cpe-107-11-237-184.columbus.res.rr.com) 16.29.59 Quit ZincAlloy (Quit: Leaving.) 16.33.57 Quit _bilgus (Read error: Connection reset by peer) 16.34.09 Join _bilgus [0] (~bilgus@cpe-107-11-237-184.columbus.res.rr.com) 16.42.05 Quit _bilgus (Read error: Connection timed out) 16.43.15 Join _bilgus [0] (~bilgus@107.11.237.184) 16.53.01 Join ac_laptop [0] (~ac_laptop@186.2.247.129) 16.56.16 Quit _bilgus (Read error: Connection reset by peer) 16.57.38 Join _bilgus [0] (~bilgus@cpe-107-11-237-184.columbus.res.rr.com) 17.00.37 Join _bilgus_ [0] (~bilgus@cpe-107-11-237-184.columbus.res.rr.com) 17.01.04 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 17.01.41 # Surely given the devices are nearing 15 years old it makes sense for multiple people with the same model to have the same issues with stuff like battery? 17.02.16 Quit _bilgus (Ping timeout: 240 seconds) 17.07.40 # the battery on my 6th gen kinda skips down to 0, but not while charging with the screen on 17.18.01 # kalube: depends. they are all used and abused differently. 17.18.19 # usage is a heavy factor in when batteries die 17.18.32 # if it only say light use, the battery may have life still 17.18.36 # but of course time also ages them 17.19.03 Quit genevino (Quit: Great minds discuss ideas. Average minds discuss events. Small minds discuss people.) 17.19.31 Join genevino [0] (~genevino@m2m.pm) 17.25.27 Quit genevino (Quit: Great minds discuss ideas. Average minds discuss events. Small minds discuss people.) 17.26.56 Join armin [0] (~armin@m2m.pm) 17.30.42 Quit lebellium (Quit: Leaving) 17.58.38 *** Saving seen data "./dancer.seen" 18.02.10 Quit _bilgus_ (Ping timeout: 256 seconds) 18.15.16 Join _bilgus [0] (~bilgus@cpe-107-11-237-184.columbus.res.rr.com) 19.18.36 Quit pamaury (Ping timeout: 256 seconds) 19.54.59 # braewoods: there are (much) better wiki engines; the catch is migrating the data+history. 19.56.05 # speachy: i see. would you be willing to share a DB dump? I'd like to see what there is to process. 19.56.15 # maybe it's possible to port it to another wiki engine. 19.56.35 # the wiki "database" is a filesystem of RCS files. 19.56.49 # Oh. It's not a proper SQL database? 19.56.59 # I actually migrated it over to a git repo as an experiment a while back 19.57.03 # * braewoods sighs. 19.57.19 # I see your challenge now. 19.57.46 # Well, I think something could be done. 19.58.08 # but i'd need data samples to try it all out 19.58.15 # foswiki has a ton of other stuff it does on top of of the pages too; as well as the actual markup itself (which is a straightforward PITA) there are some special processing flows that automagically happen; supposedly rockbox is using some already. 19.58.28 # it goes well beyond templating 19.58.42 *** Saving seen data "./dancer.seen" 19.58.42 # i see 19.58.55 # what else is there though? 19.59.06 # all i see is a bunch of static content embedded in special markup 19.59.38 # it seems like the wiki is suffering from bit rot too 19.59.45 # parts keep breaking 19.59.58 # the old foswiki version only uses a database for "caching" -- and it's a real WTF of an implementation. 20.00.33 # can you share the entire file set, whatever it is? i'd need to look at it to see what needs porting 20.00.50 # it may be easier just to make a new wiki and move the old one to archive state 20.01.01 # convert over stuff 20.01.06 # there's a ton of bitrot. bringing it generally up-to-date is a pretty signifigicant undertaking. 20.01.22 # including outdated information? 20.01.37 # plus it's still sort of written around an Archos-is-the-primary-target perspective. 20.02.04 # how important is the history? 20.02.09 # it's important to keep. 20.02.17 # ok.. 20.02.33 # well to make a successful move i need access to the data files 20.02.35 # Granted, a git repo might be sufficient 20.02.38 # read-only at least 20.03.14 # any preferences in wiki sets? 20.03.19 # short of "crawl the wiki and store the HTML statically" keeping it up in read-only isn't really any different from what it is now, operationally. 20.03.52 # i've seen crux use pmwiki for years. 20.03.56 # seems to work well for them 20.03.59 # it's flat file 20.04.26 # is something like mediawiki prefered? 20.04.27 # I'm personally partial to dokuwiki; since it uses flat files (or git) for pages instead of a DB, it's a lot easier to programically add files. 20.04.44 # ah 20.05.41 # we may not be able to fully port the PWs used in the old wiki 20.05.59 # due to differences in how they're stored or so 20.06.11 # it's rare for those to port 1 to 1 but it can happen 20.06.28 # just seems like every system has a different preference for how to store them 20.06.35 # I'd strongly prefer something that renders static pages; so a DB/git/whetever isn't needed unless someone wants to update things. 20.06.57 # sounds like a job for a static site generator 20.07.06 # we also don't need any sort of "private" or "depends on who's logged in" stuff other than administrative things. 20.07.17 # almost anyway 20.07.23 # we could move to the github page model 20.07.30 # updates are PRs to a repo 20.07.32 # or so 20.07.36 # but 20.07.39 # seems more work 20.07.44 # foswiki tries to be a full CMS with roles and scripting and all sorts of other insanity. 20.07.48 # wikis don't require pre-approval 20.08.40 # unfortunately we do need to maintain pre-approval, at least insofar as we need to keep spammers out. 20.08.56 # pre-approval for accounts 20.08.57 # but not for edits 20.08.59 # eyep 20.09.41 # most of the rest of the wiki complexity comes from being able to log in/edit from the web page directly. 20.11.43 # it's definitely nicer for drive-by contributions but it perversely discourages mroe advanced users. 20.12.02 # (vs a "real" editor and direct git integration, for example) 20.16.09 # anyway, I'll get you a dump sometime in the next few days. need to get back to flooring so the kiddo will have a bed to sleep in tonight. 20.28.18 Quit MrZeus (Ping timeout: 256 seconds) 20.31.19 Join massiveH [0] (~massiveH@ool-18e4e82f.dyn.optonline.net) 21.23.16 Quit _bilgus (Read error: Connection reset by peer) 21.23.37 Join _bilgus [0] (~bilgus@cpe-107-11-237-184.columbus.res.rr.com) 21.43.25 Quit _bilgus (Read error: Connection reset by peer) 21.43.42 Join _bilgus [0] (~bilgus@cpe-107-11-237-184.columbus.res.rr.com) 21.58.44 *** Saving seen data "./dancer.seen" 22.20.11 Join Stanley00 [0] (~stanley00@unaffiliated/stanley00) 22.52.13 Quit ac_laptop (Ping timeout: 260 seconds) 23.17.02 Quit massiveH (Ping timeout: 260 seconds) 23.28.21 Quit [7] (Disconnected by services) 23.28.28 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 23.38.08 Join fs-bluebot_ [0] (~fs-bluebo@55d4a8e9.access.ecotel.net) 23.38.15 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 23.39.16 Quit fs-bluebot (Ping timeout: 256 seconds) 23.39.27 Quit bluebrother^ (Ping timeout: 260 seconds) 23.42.50 Join pablocastellanos [0] (~emergency@li79-248.members.linode.com) 23.58.45 *** Saving seen data "./dancer.seen"