--- Log for 09.05.116 Server: verne.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 2 months and 6 days ago 00.02.33 *** Saving seen data "./dancer.seen" 00.05.04 Quit pamaury (Read error: Connection reset by peer) 00.06.20 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 00.14.31 Quit ender` (Quit: There are times, Sember, when I could believe your mother had a secret lover. Looking at you makes me wonder if it was one of my goats. -- David Gemmel: The King Beyond the Gate) 01.49.26 Quit PurlingNayuki (Remote host closed the connection) 01.53.37 Quit pamaury (Ping timeout: 276 seconds) 02.02.35 *** Saving seen data "./dancer.seen" 02.06.26 Join PurlingNayuki [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 02.09.13 Quit TheSeven (Ping timeout: 276 seconds) 02.10.25 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 02.12.02 Join PurlingNayuki1 [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 02.12.55 Quit PurlingNayuki (Ping timeout: 260 seconds) 02.12.56 Nick PurlingNayuki1 is now known as PurlingNayuki (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 02.21.28 Quit PurlingNayuki (Remote host closed the connection) 02.24.00 Join PurlingNayuki [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 03.09.23 Quit ZincAlloy (Quit: Leaving.) 03.32.22 Quit krabador (Remote host closed the connection) 03.50.59 Quit PurlingNayuki (Remote host closed the connection) 03.51.03 Join PurlingNayuki1 [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 03.53.25 Nick PurlingNayuki1 is now known as PurlingNayuki (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 04.02.37 *** Saving seen data "./dancer.seen" 04.08.14 Quit prof_wolfff (Ping timeout: 260 seconds) 04.17.33 Quit PurlingNayuki (Ping timeout: 240 seconds) 04.18.49 Join PurlingNayuki [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 04.20.54 Join prof_wolfff [0] (~prof_wolf@82.159.0.123.dyn.user.ono.com) 04.34.43 Quit PurlingNayuki (Ping timeout: 244 seconds) 04.57.15 Join PurlingNayuki [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 05.11.39 Quit PurlingNayuki (Remote host closed the connection) 05.41.07 Join Strife89|Quassel [0] (~quassel@adsl-98-80-196-173.mcn.bellsouth.net) 05.45.10 Quit Strife89 (Quit: Vamoose.) 05.45.15 Nick Strife89|Quassel is now known as Strife89 (~quassel@adsl-98-80-196-173.mcn.bellsouth.net) 06.02.40 *** Saving seen data "./dancer.seen" 06.03.28 Join PurlingNayuki [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 06.48.30 Quit foolsh (Remote host closed the connection) 06.50.47 Join foolsh [0] (~starchase@2601:241:c200:4bc5:945f:7129:6f0b:17e7) 07.43.22 Quit pixelma (Remote host closed the connection) 07.43.23 Quit amiconn (Remote host closed the connection) 07.45.48 Join pixelma [0] (~pixelma@rockbox/staff/pixelma) 07.45.49 Join amiconn [0] (~amiconn@rockbox/developer/amiconn) 07.52.45 Join xorly [0] (~xorly@ip-89-176-117-132.net.upcbroadband.cz) 08.02.45 *** Saving seen data "./dancer.seen" 08.15.41 # pamaury font rendering is broken 08.16.02 # also it looks very different from other qt programs, there's no theme for one 08.18.26 # http://i.imgur.com/MK6ZD5X.png 08.19.32 Join ender` [0] (krneki@foo.eternallybored.org) 08.22.54 Quit xorly (Ping timeout: 250 seconds) 08.24.38 Quit jtdesigns01 (Ping timeout: 250 seconds) 08.32.51 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 08.33.47 Nick suYin is now known as suYin`OFF (mysuyin@server2.shellfire.net) 08.33.53 # is the genlang script deprecated? 08.33.56 # can't find it 08.40.30 Quit holgersson (Remote host closed the connection) 08.40.59 Join holgersson [0] (~quassel@unaffiliated/holgersson) 08.42.56 # nvm, it just moved, the wiki should be updated 08.58.43 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 09.15.23 Quit nlogex (Ping timeout: 246 seconds) 09.20.38 Quit utrack (Quit: brb, hunting bears) 09.40.38 # is raaa broken on Android 5+ or is it just my builds? 10.02.46 *** Saving seen data "./dancer.seen" 10.03.38 # It's broken with ART. There's a gerrit task about it with a hacky fix (according to wodz) 10.04.33 # rasher ^ 10.05.38 # Well, its hacky but nowhere a fix. 10.06.16 # Ah, then I misunderstood 10.09.21 # I was playing around to understand where is the problem. The gerrit task was simply to document it. My understanding is that it is not feasible to workaround ART restrictions with rockbox thread model 10.13.05 Join edhelas [0] (~edhelas@2001:1c02:1903:d800:490c:8afe:3994:6cc5) 10.27.16 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 10.27.59 Join fs-bluebot [0] (~fs-bluebo@xd9bee9df.dyn.telefonica.de) 10.30.11 Quit bluebrother^ (Ping timeout: 244 seconds) 10.30.36 Quit fs-bluebot_ (Ping timeout: 265 seconds) 10.43.45 Quit edhelas (Quit: Leaving.) 10.54.21 Join edhelas [0] (~edhelas@2001:1c02:1903:d800:490c:8afe:3994:6cc5) 10.54.21 Quit edhelas (Client Quit) 10.58.00 Join xorly [0] (~xorly@wced-236-219-32-147.feld.cvut.cz) 11.42.17 Join edhelas [0] (~edhelas@2001:1c02:1903:d800:490c:8afe:3994:6cc5) 11.53.14 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 11.58.24 # duo8: this is weird, you must be the only one to have this problem with RBUtil, I wonder why it's like this on your machine 12.02.47 *** Saving seen data "./dancer.seen" 12.04.31 # duo8: are you running it as root ? 12.16.41 Quit pamaury (Ping timeout: 246 seconds) 12.17.46 Quit TheSeven (Ping timeout: 250 seconds) 12.20.34 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 12.41.46 Quit xorly (Ping timeout: 260 seconds) 12.47.06 Quit PurlingNayuki (Quit: PurlingNayuki) 13.15.57 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 13.17.27 Join krabador [0] (~krabador@unaffiliated/krabador) 13.21.51 # wodz: well that's sad news 13.59.58 Quit holgersson (Remote host closed the connection) 14.00.37 Join holgersson [0] (~quassel@unaffiliated/holgersson) 14.02.49 *** Saving seen data "./dancer.seen" 14.08.02 Join ZincAlloy [0] (~Adium@p57B95226.dip0.t-ipconnect.de) 14.14.45 Quit yosafbridge` (Quit: Leaving) 14.24.38 # whenever I turn rockbox on my phone, other apps will crank the volume randomly.. really funny.. 14.45.42 Join yosafbridge [0] (~yosafbrid@2607:5300:100:200::160d) 14.51.37 Join xorly [0] (~xorly@wced-18-219-32-147.feld.cvut.cz) 14.59.13 Quit wodz (Ping timeout: 260 seconds) 15.03.18 Quit xorly (Ping timeout: 260 seconds) 15.21.03 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 15.25.22 Join amayer [0] (~amayer@mail.weberadvertising.com) 15.29.44 Quit __builtin (Ping timeout: 250 seconds) 15.30.51 Join nlogex [0] (~filip@dhcp-108-168-15-53.cable.user.start.ca) 15.31.54 Join __builtin [0] (~franklin@unaffiliated/franklin) 15.41.07 # So has there been any word of when the Android port will work on Lollipop/Marshmallow? 15.44.17 # Presumably as soon as the issues are fixed 15.51.16 # :P I understand that. Is there a bug report for it? I know soon after Lollipop hit it was discovered and that has been quite a while 15.52.30 # Hmm doesnt seem to be http://www.rockbox.org/tracker/index/proj1?string=android&project=1&type%5B0%5D=2&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=&do=index&order=dateopened&sort=desc 15.52.40 # Holy long URL, Bataman 16.00.24 # http://gerrit.rockbox.org/r/#/c/1211/ has some information 16.01.06 # Ahh thanks. I knew I had seen something posted but wasn't sure where. 16.02.52 *** Saving seen data "./dancer.seen" 16.04.52 Join PurlingNayuki [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 16.13.53 # pamaury no 16.14.44 # what's the most complete font at size 13? 16.15.40 # *that isn't included, since every one I've tried misses characters 16.24.03 Quit nlogex (Ping timeout: 240 seconds) 16.40.14 Quit wodz (Ping timeout: 246 seconds) 16.58.05 Join girafe [0] (~girafe@2a01:cb15:810a:4100:44c:f7ad:f28a:82e3) 17.19.40 Quit krabador (Read error: Connection reset by peer) 17.36.21 Quit krnlyng (Ping timeout: 260 seconds) 17.48.49 Join krnlyng [0] (~liar@178.112.139.141.wireless.dyn.drei.com) 17.49.24 Join xorly [0] (~xorly@89.176.117.132) 17.53.38 Quit Rower (Ping timeout: 260 seconds) 18.02.55 *** Saving seen data "./dancer.seen" 18.03.29 Quit edhelas (Quit: Leaving.) 18.06.32 Join Rower [0] (husvagn@d83-183-134-99.cust.tele2.se) 18.06.41 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 18.20.00 Quit Moarc (Quit: i znowu NADMUCHAŁ BALONA) 18.39.32 Quit xorly (Ping timeout: 240 seconds) 18.49.52 Join rela [0] (~x@pdpc/supporter/active/rela) 19.04.45 # duo8: if you run RBUtil from command line, does it print any error message ? 19.09.50 Join nlogex [0] (~filip@dhcp-108-168-15-53.cable.user.start.ca) 19.16.00 Join petur [0] (~petur@rockbox/developer/petur) 19.20.59 Join lebellium [0] (~chatzilla@89-93-179-187.hfc.dyn.abo.bbox.fr) 19.31.49 Quit PurlingNayuki (Remote host closed the connection) 19.32.51 Join PurlingNayuki [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 20.02.16 Quit pamaury (Remote host closed the connection) 20.02.58 *** Saving seen data "./dancer.seen" 20.07.06 Nick suYin`OFF is now known as suYin (mysuyin@server2.shellfire.net) 20.23.48 Join krabador [0] (~krabador@95.235.183.31) 20.23.52 Quit krabador (Changing host) 20.23.52 Join krabador [0] (~krabador@unaffiliated/krabador) 20.32.43 Join xorly [0] (~xorly@ip-89-176-117-132.net.upcbroadband.cz) 20.44.16 Quit scorche` (Read error: Connection reset by peer) 20.49.44 Join scorche [0] (~scorche@rockbox/administrator/scorche) 21.12.01 Join JT923 [0] (60e20687@gateway/web/freenode/ip.96.226.6.135) 21.16.34 # Hello there! So I have an NWZ-E385 and I am trying to install rockbox. This is the first time I have tried to install rockbox and after following the instructions I don't think it worked and I am not sure what to do or what I did wrong. If someone could help me figure out what I need to do that would be great! 21.21.05 Join ZincAlloy1 [0] (~Adium@p57B95226.dip0.t-ipconnect.de) 21.21.06 Quit ZincAlloy (Read error: Connection reset by peer) 21.45.21 Join saratoga [0] (123e11e0@gateway/web/freenode/ip.18.62.17.224) 21.45.30 # do we have a wiki page on all these ipod hard disk mods that everyone seems to be trying? 21.45.35 # and why they don't seem to work 22.02.59 *** Saving seen data "./dancer.seen" 22.13.09 Quit soap_ (Ping timeout: 250 seconds) 22.18.30 Quit JT923 (Quit: Page closed) 22.29.09 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 22.54.00 Quit petur (Remote host closed the connection) 23.04.32 # damn, why poeple can't just wait after they ask a question :'( 23.15.21 Quit xorly (Ping timeout: 244 seconds) 23.19.41 # <[Saint]> saratoga: No. I don't believe so. 23.20.16 Join ved [0] (ved@ddsbox.tk) 23.22.35 Quit lebellium (Quit: ChatZilla 0.9.92 [Firefox 46.0.1/20160502172042]) 23.28.40 Quit Mir (Ping timeout: 246 seconds) 23.30.56 # hello, anyone here knowledgable with arm 23.31.11 # sry, arm sansa fuze+ recovery procedures? 23.32.16 # <[Saint]> What do you mean, precisely? 23.32.46 # <[Saint]> There is no known lowlevel recovery method for the Fuze+. 23.33.09 # I am able to use the recovery mode to use recovery.sb code to work (i get status output on the display), but dd'ing OF on the sdb2 seems not to work, that is, after unplugging i get an info about 23.33.13 # *PANIC* at specific pc/sp (and mount0), and despite the apparent correct flashing (i can hexdump sdb2 to see the content of OF) it still does not boot 23.34.00 # <[Saint]> Oh. Shit. Sorry....coffee hasn;t set in yet. That's iMX based isn;t it. 23.34.02 # <[Saint]> Derp. 23.34.14 # You want pamaury I think 23.34.35 # probably, what is his (?) timezone? 23.35.09 # <[Saint]> I'm guessing "The recovery mode of the fuze+ (of the imx233 to be precise) is HID based but has a quirk: if doesn't like being send a GET_REPORT. On linux kernel versions up to somwhere between 3.2 and 3.7, a change was made to the usbhid driver which sends a GET_REPORT by default. A quirk was added for this particular device somewhere between 3.7 and 3.8. Consequently, if you a running a recent kernel but not the trunk, it will break your device. 23.35.09 # <[Saint]> There are several ways to fix this problem. In all cases, unplug the device, apply the fix and replug your device." is relevant here. 23.35.16 # Well, he was still awake half an hour ago 23.36.13 # I'm here 23.36.23 # [Saint]: thanks, I tried to google enough before bothering You, thanks anyway, I have kernel 4.2 from relatively new ubuntu version, should be ok 23.36.33 # <[Saint]> Hum. 23.37.26 # ved: I can imagine several reasons why it's not working, maybe the MBR is corrupted 23.37.59 # let's go back to the basics: if you start from a power down state and plug the device, what is output of lsusb ? 23.38.34 # pamaury: sorry to bother, after doing 'sbloader recovery.sb' i get a nice response from my fuze+, it displays charging stats and such, but after dd'ing firmware.sb to the second partition (ssb2 as 23.38.38 # well) whenever i unplug the device i get information about some crash(?) '*PANIC* *PANIC* mount: 0 pc: 601018c8 sp:6011e0f0 bt end. Have you maybe encountered something like that? (i tried using 23.38.42 # 'sync' command after dd, but the effect seems the same) 23.38.59 # pamaury: lsusb shows recovery mode 23.39.15 # ved: ok so recovery mode even if you don't press the recovery button ? 23.39.49 # yes, exactly, volume down, volume up, no keypress, plugging it in on USB gives me only recovery mode 23.40.06 # by the way the panic is normal, the recovery.sb is not able to mount any usable partition, that's expected 23.40.09 # it gets 'unlocked' after i sbload it with recovery.sb, but on first plugin it is always recovery 23.40.17 # ah, good to know 23.40.36 # ok, so now upload recovery.sb 23.40.59 # can you use fdisk to get the partition table of the device ? (use pastebin.com to copy and paste) 23.41.06 # (you know how to use fdisk ?) 23.41.25 # yup, status passed, the device is alive showing stats, kde even tries to mound sdb3 without success, but yea, i have the 4 partitions 23.41.51 # shall we do it here, or priv? 23.42.30 # here, paste the output on pastebin.com and put the link here 23.42.42 # that may be useful for future reference 23.43.44 # http://pastebin.com/ZDKKt44q 23.44.14 # looks quite ok, over 40MB on the 2nd partition (OF file is ~35MB) 23.46.59 # a little backstory, i got back to this device after a few (like 3-4 years) after i was testing some experimental rockbox version for this device, afair it died out of battery and i left it alone. 23.47.03 # After this time i thought it was the charger issue, i tried using charging code, it apparently worked but it is not the main issue. Status screen after recovery.sb shows 75% of battery right now, so 23.47.07 # the battery should be ok. 23.49.05 # funfact, now it says 'power up source: 20', it used to say '1', whatever it means 23.50.01 # 20 means powerup from usb, basically 23.50.25 # the partition looks normal, let me double check with mine 23.51.05 # well, it is really reassuring the PANIC at the end is to be expected, so i may at least try to use other OF versions 23.51.24 # in the mean time, you can try something: reset the device and use sbloader to upload the OF directly 23.51.31 # ie sbloader firmware.sb 23.51.47 # were firmware.sb is the fuze+ firmware (unpacked from zip of course) 23.54.33 Quit girafe (Read error: Connection reset by peer) 23.54.39 # *where 23.54.48 # reset after unplug? After unplugging there is PANIC, and after reset the device shows as recovery, so uploading needs sending recovery.sb first 23.55.12 # no, just use sbloader to upload firmware.sb instead of recovery.sb 23.55.18 # oooh 23.55.29 # trust me, it works (usually) 23.56.49 Nick suYin is now known as suYin`OFF (mysuyin@server2.shellfire.net)