--- Log for 08.06.116 Server: leguin.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 8 days and 14 hours ago 00.03.06 Quit petur (Quit: Leaving) 00.04.05 Quit amayer (Ping timeout: 250 seconds) 00.09.34 Quit ender` (Quit: Gray is a color; grey is a colour.) 00.13.38 Quit bertrik (Ping timeout: 276 seconds) 00.14.41 Quit girafe (Read error: Connection reset by peer) 00.22.57 Quit Guest85177 (Ping timeout: 244 seconds) 00.24.02 Quit alexweissman (Remote host closed the connection) 00.24.21 Join Guest85177 [0] (~Slayer@c-69-255-136-113.hsd1.va.comcast.net) 00.29.36 # <__builtin> hmm, maybe I could make the OTP plugin type the OTP for you :D 00.29.58 # <__builtin> after all, I did write ducky a while back 00.32.55 Quit japonecka (Ping timeout: 258 seconds) 00.48.51 Join JdGordon [0] (~jonno@210-84-40-172.dyn.iinet.net.au) 00.48.51 Quit JdGordon (Changing host) 00.48.51 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 00.50.25 # <__builtin> n1cky_: I just added the ability to type passwords over USB, would you be willing to test? 00.51.42 Quit JdGordon_ (Ping timeout: 252 seconds) 00.51.46 # <__builtin> (after I get it to compile, that is) 00.57.43 # <__builtin> actually it seems that HID on the clip zip is broken 00.58.04 # <__builtin> so never mind 00.59.15 Quit saratoga (Ping timeout: 250 seconds) 01.10.23 Quit foolsh (Ping timeout: 250 seconds) 01.12.19 Join alexweissman [0] (~alexweiss@99-138-109-34.lightspeed.cicril.sbcglobal.net) 01.16.24 Join foolsh [0] (~starchase@2601:241:c200:4bc5:2908:e608:e1c1:8b0c) 01.17.01 *** Saving seen data "./dancer.seen" 01.17.26 Quit pamaury (Ping timeout: 260 seconds) 01.22.56 Quit foolsh (Ping timeout: 250 seconds) 01.27.40 Join foolsh [0] (~starchase@2601:241:c200:4bc5:2908:e608:e1c1:8b0c) 01.31.11 Quit Bray90820 (Remote host closed the connection) 01.32.24 Join Bray90820 [0] (~bray90820@50-81-116-153.client.mchsi.com) 01.37.53 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 01.40.38 Quit JdGordon (Ping timeout: 260 seconds) 02.11.02 Quit foolsh (Ping timeout: 250 seconds) 02.11.25 Join foolsh [0] (~starchase@2601:241:c200:4bc5:2908:e608:e1c1:8b0c) 02.20.34 Quit foolsh (Ping timeout: 250 seconds) 02.23.01 Join JanC_ [0] (~janc@lugwv/member/JanC) 02.24.04 Nick JanC is now known as Guest74845 (~janc@lugwv/member/JanC) 02.24.04 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC) 02.24.49 Quit Guest74845 (Ping timeout: 250 seconds) 02.25.47 Join foolsh [0] (~starchase@2601:241:c200:4bc5:2908:e608:e1c1:8b0c) 02.31.57 # __builtin: Aww that's really too bad; that's a feature I'd be really interested in 02.32.28 # __builtin: have you got a source for HID being broken? 02.44.47 Join [Saint] [0] (77e01fae@rockbox/staff/saint) 02.45.48 Nick n1cky_ is now known as n1cky (~sielicki@104.236.246.142) 02.58.21 Quit ZincAlloy (Quit: Leaving.) 03.03.31 Quit alexweissman (Remote host closed the connection) 03.17.03 *** Saving seen data "./dancer.seen" 03.24.50 # <__builtin> n1cky: config.h 03.25.07 # <__builtin> n1cky: firmware/export/config.h 03.26.02 # * __builtin will try to maintain backwards compatibility for the plugin from now on 03.45.02 Quit fishbulb (Remote host closed the connection) 03.45.56 Quit foolsh (Ping timeout: 250 seconds) 03.51.14 Join foolsh [0] (~starchase@2601:241:c200:4bc5:2908:e608:e1c1:8b0c) 04.05.26 Quit prof_wolfff (Ping timeout: 246 seconds) 04.14.06 Join alexweissman [0] (~alexweiss@2602:306:38a6:d220:1196:ba28:f165:2be0) 04.18.27 Quit alexweissman (Ping timeout: 250 seconds) 05.13.54 Join fishbulb [0] (~fishbulb@unaffiliated/fishbulb) 05.14.24 # hey if I install a drive with nothing on it into my player with a rockbox bootloader 05.14.27 # can I install shit 05.14.31 # and format the drive 05.14.50 # it's an iriver h340 and I have a msata SSD and all the adapters 05.14.59 # to get it inside the device 05.15.34 # BUT if the drive is blank or NTFS or whatever, I have to format it to fat32, and the standard firmware doesn't support this drive setup 05.17.04 *** Saving seen data "./dancer.seen" 05.17.45 # so can I format the thing with the drive in there? 05.18.04 # or do I have to put the drive into another computer, and then format and blah blah 05.18.41 # then put it into the rockboxed player. can you rockbox a player that has a hard drive which is blank? 05.21.22 Join Stroboko1p [0] (~Strobokop@x4d06792b.dyn.telefonica.de) 05.24.42 Quit Strobokopp (Ping timeout: 244 seconds) 05.45.59 Quit foolsh (Ping timeout: 250 seconds) 06.03.23 Join foolsh [0] (~starchase@2601:241:c200:4bc5:2908:e608:e1c1:8b0c) 06.41.15 Quit fishbulb (Remote host closed the connection) 07.06.53 Join fishbulb [0] (~fishbulb@unaffiliated/fishbulb) 07.07.07 # how do I rockbox a player in linux 07.07.27 # windows 10 doesn't recognise the working player I have and sure as fuck doesn't detect the ssd I have in this device 07.07.48 # which I'm not sure is formatted or anything, I get ata -1 error sometimes, or a white screen for way too long 07.08.26 # can I put an unformatted msata ssd into a player and format it through the usb port or should I copy the contents of the old spinning hard drive to the msata first, then try booting 07.08.50 # and how the hell do you install rockbox with this windows 10 shit that won't even detect a fully functional one? 07.09.06 # <[Saint]> Someone really needs to write down full manual and guided installation instructions and compile it into some form of documentation, a manual if you will, and upload it to rockbox.org 07.09.11 # <[Saint]> that would really hlep. 07.09.13 # the bootloader is on there, it either comes up with ata -1 error while booting 07.09.18 # or it hangs 07.09.50 # so you're fully aware of all the snags with the iriver h340 msata SSD conversion then 07.10.09 # and it's just unwritten 07.10.18 # or are you being a shit head and literally saying "rtfm" 07.10.42 # because that's a worthless piece of advice, I'm looking at the manual 07.12.28 # ata-11 is nothing connected, that comes up when the cables are connected wrong, or there's literally nothing connected to the player 07.13.23 # ata-1 comes up after about a minute of the thing trying to boot, or less regularly it will hang at the boot screen and not detect the drive. I don't know if the drive is formatted or anything like that, it's an MSATA SSD and there are adapters that eventually connect it to ATA 07.13.27 Quit nlogex (Ping timeout: 272 seconds) 07.13.38 # <[Saint]> If you're looking at the manual you should be able to clearly see the linux applicable manual installation instructions. 07.13.48 # the bootloader is installed 07.13.54 # <[Saint]> that won't magically help you if you have non-standard hardware however. 07.14.19 # so you're saying the answer is in the documentation 07.14.38 # because it sounds to me like you're just saying "rtfm" becuase you have no clue 07.14.49 # <[Saint]> you asked 'how do I rockbox a player in linux', the manual answers this. 07.15.09 # <[Saint]> it does NOT answer 'How do I make my VERY specific case of non-standard hardware work" 07.15.25 # thanks for the worthless advice 07.16.29 # <[Saint]> FOr answering your question, you mean? Yeah, no problems. 07.17.01 # I would expect it to be worthless. Ripping apart your mp3 player and swapping out hardware components is not going to be in the manual of, you know, a software project whose main purpose is to work on unmodified hardware. 07.17.06 *** Saving seen data "./dancer.seen" 07.17.17 # it was very clear what my actual question was, you just parroted "RTFM" and pretended like I wasn't talking about an extremely specific problem 07.17.22 # <[Saint]> Fukken bingo. 07.17.25 # and including hte error message 07.17.53 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 07.17.55 # ok so don't fucking answer, if you don't know the answer, don't bleat "RTFM" like that's some revalation nobody has ever thought of 07.18.16 # <[Saint]> Your question was "how do I rockbox a player in linux" 07.18.22 # <[Saint]> fuck me for taking it literally, right? 07.18.23 # fuck off you idiot 07.18.40 Mode "#rockbox +o [Saint]" by ChanServ (ChanServ@services.) 07.18.46 # <[Saint]> ...come again? 07.19.17 # I said fuck off. you are ignoring about 30 lines of text and telling me what my actual question is 07.20.14 Kick (#rockbox fishbulb :'no, you.') by [Saint]!77e01fae@rockbox/staff/saint 07.20.22 Quit JdGordon_ (Ping timeout: 250 seconds) 07.20.36 Mode "#rockbox -o [Saint]" by ChanServ (ChanServ@services.) 07.36.50 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 07.41.01 Join trampith [0] (~trampith@B9255603.rev.sefiber.dk) 07.52.49 # Is work on the AndroidPort still in progress or is it dead, will there be a supported port at the end? I could download a daily build apk at rasher's site and install it, but it doesn't work - what has to go into the rockbox folder to get it work? Is that possible to get it running without building rockbox from sources on my own? Thanks for hints. 07.53.32 Join prof_wolfff [0] (~prof_wolf@82.159.0.123.dyn.user.ono.com) 07.56.18 # [Saint]: you should have kicked yourself from the channel too at this point 07.58.47 # <[Saint]> pixelma: cool story 07.59.15 # <[Saint]> trampith: if you're on Android 5.0 or higher, nothing you do will allow it to function. 08.00.06 # <[Saint]> And, no, there is no ongoing development. 08.01.08 # <[Saint]> regarding 'what has to go in the rockbox folder to get it to work", strictly speaking, nothing. 08.01.40 # <[Saint]> anything therein isn't a hard requirement to functionality. 08.02.35 Quit wodz (Ping timeout: 258 seconds) 08.09.45 # Saint: OK, I see, I use 5.0. It's a pity. Someone should update the website regarding the AndroidPort and add this information. Thank you very much! 08.09.53 # <[Saint]> trampith: actually, if you specifically elected to use the ART runtime on 4.4, it won't function there either. 08.10.03 # <[Saint]> But there you have the option of reverting. 08.12.00 # <[Saint]> Basically it boiled down to it being A Lot Of Work (TM) to get it to work with our threading in the ART runtime, and no one with the necessary traits available or willing to do that work. 08.12.51 # <[Saint]> If you really wanted Rockbox on Android, there is a pretty convoluted workaround. 08.13.27 # <[Saint]> You could use a chroot image in the Android data partition and run a tightvnc server and the Rockbox SDL app therein. 08.14.26 # <[Saint]> But if I got wind of anyone doing that I think I might have to stage a digital intervention and get that person the help they require, because they obviously have thoughts of self harming. :p 08.18.44 # [Saint]: *lol* well, I have to tell you, that I will not go such far. :p But thanks anyway - I guess I just give my iAudio X5 a new battery and use the joystick even more carefully from now on. 08.21.05 # <[Saint]> I can't even think of an application that is even remotely close as a substitute for you. 08.30.17 # [Saint]: I know, that's exactly THE pity! ArmAmp is quite ok but rockbox is just the real thing for me and I use it since eight years very happily. 08.30.45 Join ender` [0] (krneki@foo.eternallybored.org) 08.35.49 Join alexweissman [0] (~alexweiss@2602:306:38a6:d220:54ff:2751:4ce5:ef1) 08.36.27 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 08.38.48 Quit JdGordon (Ping timeout: 250 seconds) 08.40.10 Quit alexweissman (Ping timeout: 250 seconds) 08.47.19 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 08.50.45 # trampith: There are serious technical limitations of how Android port works. It doesn't work on ART runtime and will probably never be. Putting this aside there is no active developer to pickup this and push further. 08.52.08 Quit n1cky (Quit: Lost terminal) 08.58.00 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 08.58.31 # wodz: i tested the saratoga n2g build, used a 2GB Nano and copied about 6GB of small files in 4 rounds with no errors and all md5sum ok, even i used the HID mouse mode some time while coping files, could you give me more details?, at first glance it seems it could be due to flash (HW or driver) or the USB connection (HW or driver) 08.59.23 # even after real I/O error the disconnects seems strange for me, really i don't know how it should behave, i am going to simulate I/O errors to see it there is some bug there 08.59.48 # prof_wolfff: I need to do more tests. I took the player with me so I can test it on a few machines at work 09.00.12 # ok, tell me about them 09.01.58 # wodz: thanks, already aware of that now. pity. 09.04.10 # <[Saint]> I have somewhere the very beginnings of wrapping an Android native UI around ffmpeg. 09.04.33 # <[Saint]> But, like a lot of the things I start one day, I have very little want or reason to continue working on it. 09.05.06 # <[Saint]> Joe User just plain doesn't seem to want a full featured Android audio player. 09.06.31 Quit sparetire (Ping timeout: 244 seconds) 09.06.46 # <[Saint]> I often get the impression that a large body of Rockbox users don't actually use a majority of the features Rockbox actually offers anyway. 09.07.10 # <[Saint]> wide codec support is likely the initial draw card. 09.08.31 # [Saint]: you're right, it's real for the audiophile power user and us geeks :p 09.09.29 # <[Saint]> Somewhat ironically, I doubt that most of the active users make extensive use of the Rockbox advanced feature set outside of testing either. 09.09.38 # well, gentlemen, have to go. thank you very much for the insight. cleared the fog a bit. let's hope the best for our little perl! :p CU 09.10.08 # <[Saint]> I know that a very large percentage of us don't even touch the database or plugins. 09.10.20 Part trampith ("Leaving") 09.17.09 *** Saving seen data "./dancer.seen" 09.26.15 Quit [Saint] (Ping timeout: 250 seconds) 09.42.47 # things I use from rockbox (off the top of my head): database, file browser, guitar tuning plugin, fft plugin, dynamic range compressor, crossfeed-stereo, USB-HID (no multimedia keys on this notebook!), sleep timer, queueing tracks (I cannot even believe that not every player software can do that), … 09.43.07 # equalizer! 09.50.20 Join elensil [0] (~edhelas@2001:1c02:1903:d800:79cd:e599:dd9:e972) 09.54.50 Join petur [0] (~petur@rockbox/developer/petur) 10.11.36 Quit foolsh (Ping timeout: 250 seconds) 10.36.44 Quit igitoor (Ping timeout: 260 seconds) 10.37.23 Join igitoor [0] (igitur@2a00:d880:3:1::c1ca:a648) 10.45.33 Quit [7] (Disconnected by services) 10.45.42 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 10.45.52 Quit igitoor (Changing host) 10.45.52 Join igitoor [0] (igitur@unaffiliated/contempt) 10.46.28 Join ZincAlloy [0] (~Adium@2a02:8108:8bc0:1664:75c5:bf85:ccb5:79b0) 10.54.57 Join sparetire [0] (~sparetire@unaffiliated/sparetire) 11.17.12 *** Saving seen data "./dancer.seen" 11.57.30 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 12.20.30 # Horrorcat: did you see my messages from yesterday night ? 12.22.12 # pamaury: yes, I already built it and put it on my device 12.22.24 # do you still need numbers? 12.32.57 # what do you mean ? 12.33.08 # 20:55:44 < pamaury> Horrorcat: I am looking at the zenxfi3 problem, I was thinking about it: when the display goes weird in bootloader mode, what is the value displayed in parenthesis ? (that's the voltage) 12.33.50 # ah, huh right now no, I realized yesterday the calibraion curve is wrong, that's why the percentage is wrong. I am currently running a battery benchmark to recalibrate it 12.34.00 # ah I see 12.34.18 # Did you observe the power off problem with the new patch yet ? 12.34.20 # I guess this will need a bootloader rebuild to fix it there, too? 12.34.31 # no, but I have been in a lecture since I rebuilt, so not really any chance to test it 12.35.25 # ok, yes it will 12.35.59 # i have no idea how I produced these values in the first place but I was clearly high ^^ 12.36.15 # heh :) 12.37.32 # I need to go, I hope the patch will prove useful 12.37.40 # I’ll let you know! 12.42.01 Quit pamaury (Ping timeout: 246 seconds) 12.54.38 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 13.17.16 *** Saving seen data "./dancer.seen" 13.26.31 Join AndyP_ [0] (b92ed446@gateway/web/freenode/ip.185.46.212.70) 13.29.39 # edhelas: I have finally managed to get my Mini1G and 4thGen GreyScale ipods to switch between the dock and the remote serial ports. 13.31.03 # For some reason the Mini2G and the 4thGen Color don't appear to work through the remote connector using the same code. 13.31.35 # What variant have you managed to get to work through the remote? 13.32.03 # AndyP_: well it was working with a hacky patch on my Mini2G 13.33.46 # AndyP_: if I remember I just removed the #else there http://git.rockbox.org/?p=rockbox.git;a=blob;f=firmware/target/arm/pp/uart-pp.c;h=069ae596a0c8deacfb35edf25b3bbdd04815f9c8;hb=6548dc294357f4f13a17bf34206038a3a93f1ff7#l112 13.35.54 Join krabador [0] (~krabador@unaffiliated/krabador) 13.35.58 # Apologies, its the Mini1G that doesn't work, the Mini2G does. 13.37.13 # AndyP_: and there's differences between the 4thGen and the 4thGen Color ? 13.38.17 # Yes, the 4thGen Grey remote works, but I can't get the color to talk at all. 13.39.21 # you have the patch somewhere ? I'll try to have a look at it tonight :) 13.39.21 # Both serial ports work OK using the OF but not under Rockbox. 13.40.23 # I'll upload a patch when I get home. 13.41.32 # Probably about 5-6 hours from now. 13.41.48 # it was basically rerouting the serial correctly or you made some changes in IAP as well ? 13.42.09 # you also tried with a serial-top-connector Apple Remote ? 13.42.31 Join xorly [0] (~xorly@193.85.203.185) 13.43.49 # Just rerouting the serial with no change to IAP. I tried 3 different serial-top-connector remotes, only 1 works under Rockbox. 13.44.38 # I think the others don't quite give the correct baud rates and the OF is more forgiving. 13.45.56 # I also remember to have some weird behaviour with the Apple Remote (some play/pause/forward events sent several times…) 13.48.14 # In the end I made a serial cable to connect to the serial-top-connector and used a piece of software called IpodExplorer.exe to talk to the ipod. 13.50.05 # eheh what a hacker :p 13.50.14 # Using that software I can send and receive the same as with the dock connector but the Mini1G and the 4thGen color just don't want to play. 13.50.42 # I'll still try to apply your patch and have a look 13.52.23 # OK, it should apply cleanly to the latest gerrit code. Must go, work is shouting...... 13.52.42 # thanks o/ 13.52.45 Part AndyP_ 13.57.39 Quit alucryd (Ping timeout: 240 seconds) 14.24.45 Join fishbulb [0] (~fishbulb@unaffiliated/fishbulb) 14.24.59 # does anyone know how a solid state drive should be configured 14.25.15 # define "should be configured" 14.25.20 # there is that huge beast called ATA spec 14.25.33 # it's MSATA 14.25.48 # goes through an adapter to zif 14.25.56 # i recall your scenario 14.25.59 # then zif to pata? whatever the 14.26.04 # ok it's working 14.26.14 # but comes up with errors because there's nothing to spin down 14.26.24 # what kind of errors? 14.26.50 # there's one here now I haven't seen Error accessing playlist control file (-4) 14.27.09 # are you sure it’s because of the spindown? 14.27.23 # this one? this just appeared on the screen now 14.27.31 # I'm wondering what happens to the spindown and all that shit 14.27.39 # in the best case, the SSD just shrugs 14.27.43 # in the worst case, it chokes 14.27.50 # chokes how 14.27.54 # I set it to 3s 14.27.55 # like mine does 14.28.00 # like yours does what 14.28.08 # being unreliable, random crashes, corrupt filesystem 14.28.15 # great. 14.28.38 # well, it's those things 14.28.40 # you could try my patches and see whether they make things worse or better for you 14.28.51 # ah, do you have the original HDD at hand? 14.29.03 # this took like 7 hours to do 14.29.09 # I am so fucking over this 14.29.23 # I'm not doing it now 14.29.24 Join alucryd [0] (~quassel@archlinux/developer/alucryd) 14.29.25 # could you tell me the voltage rating of the original HDD? 14.29.34 # voltage or amperage 14.29.37 # voltage 14.29.38 # 3.3v 14.29.40 # okay 14.29.41 # all of them are 14.29.55 # yeah, I had vaguely remembered that it was 2.5v 14.30.02 # what? 14.30.09 # no, 3.3 14.30.12 # that’s good 14.30.17 # the msata is 3.3 14.30.30 # I don't know of a drive that's anything other than 3.3 14.30.37 # if you don’t mind using a rockbox uploaded by a stranger from the internet, I could make you a build 14.30.41 # but the hard drive says 500mA 14.30.57 # the msata drive says 1.6A 14.30.59 # eww 14.31.02 # that's phenomenally more 14.31.05 # that’s... yes 14.31.10 # despite the other one being a spinning disk 14.31.14 # I didn't notice it, it's a samsung drive 14.31.30 # it was supposed to be low energy consumption 14.31.44 # I guess it’s low compared to desktop spinning disks… 14.31.55 # um 14.32.00 # probably 14.33.20 # what would you patch? 14.33.20 Quit Jinx (Read error: Connection reset by peer) 14.33.20 # whta do you patch 14.33.20 # what wouldst thou patch 14.33.51 # I have some patches which essentially talk more to the drive instead of trying to guess its power state 14.33.57 Quit xorly (Ping timeout: 252 seconds) 14.34.03 # this has somewhat improved the situation for me 14.40.44 Join Jinx [0] (Dojo@unaffiliated/jinx) 14.40.47 Join athidhep [0] (~afoakf@unaffiliated/athidhep) 14.44.33 Join japonecka [0] (~OK@37-48-5-180.tmcz.cz) 14.50.25 Join xorly [0] (~xorly@193.85.203.185) 14.51.08 # what the fuck 14.51.22 # *PANIC* 14.51.44 # Dir entry 4 in sector 0 is not free! 03 00 78 00 14.52.13 # white screen, everything stopped, had to hard reset again 14.52.17 # :| 14.53.30 Quit TheSeven (Ping timeout: 258 seconds) 14.54.30 # same error again 14.54.44 # the track playing slowed down 14.54.47 # then stopped 14.56.07 # 3.3x1.6 = roughly 6? 14.56.12 # 6A peak draw? 14.56.30 # compared to 500mA I dunno what that was, that's the only amperage written on the whole drive 14.56.35 # a spinning platter drive 14.57.54 # ok this error is happening regularly 14.57.59 # fishbulb: don't know anything about your ssd hack but this panic (Dir entry 4 in sector 0 is not free! 03 00 78 00) is not about sata, it's essentially saying your FAT (filesystem) is corrupted 14.58.05 # the battery is being HOSED 14.58.28 # I formatted it as fat32 14.59.05 # stock bootloader, pretty normal rockbox, msata ssd 14.59.07 # well unless we have a bug in our fat driver it means it is corrupted 14.59.08 # IF the offending drive gets 3x peak current to the designed one I bet voltage regulator isn't happy 14.59.20 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 14.59.34 # the drive is corrupted? 14.59.37 # how do I format it? 14.59.57 # a crash can corrupt the fat, windows can check for errors and linux has fsck 15.00.09 # um 15.00.18 # (you need to plug it to computer) 15.00.21 # fsck.vfat /dev/foo, and if it reports errors just bump it over 15.00.31 # I mean DAP designer considered 500mA peak current and selected caps and regulator accordingly 15.00.35 # I'm on arch, what do I do 15.00.58 # I can check it for errors with gparted 15.01.09 # no drives I own fail ever 15.01.11 # fishbulb: lsblk; plug the device in and wait a few seconds; lsblk. two new entries should have appeared (sdx and sdx1). run (as root) fsck.vfat /dev/sdx1 15.01.32 Quit wodz (Quit: Leaving) 15.01.36 # plug it in usb bootloader mode or load rockbox and plug it in 15.01.41 # use bootloader mode 15.01.48 # that will be happier if you make changes to the FS 15.02.07 # (fun fact: rockbox looks very confused if you run mkfs.vfat on its device while it is running :D) 15.02.09 # what changes? 15.02.17 # like, if fsck.vfat finds errors and wants to repair them 15.02.31 # what do I run 15.02.37 # scan it with gparted? 15.02.41 # yeah, that’ll do 15.03.40 Quit xorly (Ping timeout: 250 seconds) 15.06.18 # it isn't happy 15.07.34 # I suspected that 15.07.35 # input output error 15.07.37 # eww 15.07.46 # on read on /dev/sdc1 15.08.26 # it said grow filesystem to fill partition 15.08.31 # ok, fuck gnome 15.08.39 # I'm sick of this shit. 15.09.06 # how do I format this SSD again? 15.09.16 # and I use FAT or FAT32 ? 15.09.35 # what does input output error during read on this drive mean 15.09.38 Quit PurlingNayuki (Remote host closed the connection) 15.09.48 # something really bad? 15.10.37 # use fat32 15.11.04 # the I/O error can have many causes. One could be that the voltage drops and the SSD gets confused/in an inconsistent state/reset in the middle of an operation 15.11.19 # fuck that 15.11.21 # it's probably that 15.11.38 # considering that USB 2.0 only delivers 500mA, I consider this very likely 15.11.49 # it might even be that your USB host simply cut off the power because the device took too much 15.11.57 # um 15.12.04 # I'll plug it into usb3 15.12.19 # which is an expresscard adapter :/ 15.12.23 # that might not help, as the device won’t negotiate USB3 15.12.32 # it'll give more power surely 15.12.45 # give it a try 15.12.59 # the h340 is usb2 15.13.08 # I dont' want to waste too much more time 15.13.45 # USB3 is at most 900mA while the device is registered with data transfer support 15.14.24 # ok, shut down and started again 15.14.32 # ATA error -11 15.14.46 # insert USB cable and press a button 15.14.52 # :( 15.15.11 # meh 15.15.16 # sucks 15.15.28 # send the SSD back and try the microSD adapter chain ;) 15.15.44 # great 15.15.47 # no 15.15.57 # FUCK. 15.17.19 *** Saving seen data "./dancer.seen" 15.18.26 Join xorly [0] (~xorly@193.85.203.185) 15.19.58 Join amayer [0] (~amayer@mail.weberadvertising.com) 15.25.13 # so this is not going to work at all? 15.27.32 Quit duo8 (Ping timeout: 276 seconds) 15.28.42 # fishbulb: it appears you were even unluckier than me with the choice of SSD :( 15.29.06 # yeah appears that way. 15.29.08 # shit 15.29.20 # I'll try it in a computer 15.29.30 # now that my h320 is revived I’m going to give the microSD adapter chain a shot though 15.29.57 # in the hope that it proves to be more stable 15.32.04 # I looked up the datasheet for this thing 15.32.08 # before I bought it 15.32.27 # the read and write power requirements aren't 1.6A on the datasheet 15.32.47 # what’s written on the datasheet w.r.t. power consumption? 15.33.25 # I don't remember, it was within the drives that were reported as working on the rockbox site though 15.33.35 # they had a few listed and some had massive power requirements 15.33.51 # anyway, this doesnt' work, and I'm disappointed. 15.34.15 # I might pull the one out of this thinkpad though 15.37.43 Quit xorly (Ping timeout: 246 seconds) 15.37.59 # replace it with one half the size 15.38.58 Join fs-bluebot [0] (~fs-bluebo@xd9beecef.dyn.telefonica.de) 15.39.15 Quit bluebrother (Disconnected by services) 15.39.20 Join bluebrother^ [0] (~dom@rockbox/developer/bluebrother) 15.40.21 Join xorly [0] (~xorly@193.85.203.185) 15.41.14 Quit fs-bluebot_ (Ping timeout: 264 seconds) 15.47.10 Join duo8 [0] (~ZNC-SRV-H@117.6.48.103) 15.49.32 # fantastic 15.50.21 # this shouldn't have failed, the datasheet said nothing about 1.6A 16.02.50 # original drive back in 16.03.27 # done. what a waste of a day. 16.16.20 Quit athidhep (Quit: athidhep) 16.19.48 Join T-rack [0] (4d638c8d@gateway/web/freenode/ip.77.99.140.141) 16.21.24 # Hi 16.25.43 Quit T-rack (Ping timeout: 250 seconds) 17.17.21 *** Saving seen data "./dancer.seen" 17.20.23 Quit duo8 (Ping timeout: 260 seconds) 17.23.30 Join nlogex [0] (~filip@dhcp-108-168-15-53.cable.user.start.ca) 17.24.35 Join duo8 [0] (~ZNC-SRV-H@117.6.48.103) 17.25.07 Quit petur (Quit: *plop*) 17.37.05 Quit krnlyng (Ping timeout: 252 seconds) 17.46.30 Join alexweissman [0] (~alexweiss@2602:306:38a6:d220:80c1:7b06:4804:db1a) 17.49.09 Join krnlyng [0] (~liar@178.112.199.24.wireless.dyn.drei.com) 18.04.00 Quit elensil (Quit: Leaving.) 18.12.35 Quit xorly (Ping timeout: 250 seconds) 18.13.17 Join paulk-nyan-big [0] (~paulk@188.25.244.20) 18.40.50 Quit krabador (Quit: Take The Time) 18.46.23 Quit paulk-nyan-big (Ping timeout: 250 seconds) 18.52.08 Join dan-- [0] (~d@101.165.168.135) 18.52.08 Quit dan-- (Changing host) 18.52.08 Join dan-- [0] (~d@freenode/corporate-sponsor/privateinternetaccess.com/doaks) 18.52.38 Quit dan- (Ping timeout: 264 seconds) 18.53.51 Nick dan-- is now known as dan- (~d@freenode/corporate-sponsor/privateinternetaccess.com/doaks) 19.03.52 Quit Rower (Quit: Hmmm...) 19.05.49 Join Rower [0] (husvagn@d83-183-134-99.cust.tele2.se) 19.06.29 Join edhelas [0] (~edhelas@145.133.43.230) 19.11.53 Quit Petri152 (Quit: ZNC - http://znc.in) 19.15.33 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 19.17.22 *** Saving seen data "./dancer.seen" 19.19.38 Quit japonecka (Ping timeout: 264 seconds) 19.21.51 Join paulk-nyan-big [0] (~paulk@188.25.244.20) 19.35.41 Join japonecka [0] (~OK@37-48-5-180.tmcz.cz) 19.44.05 Quit paulk-nyan-big (Ping timeout: 244 seconds) 19.53.38 Quit pamaury (Remote host closed the connection) 20.06.23 Quit edhelas (Ping timeout: 276 seconds) 20.08.39 Join petur [0] (~petur@rockbox/developer/petur) 20.10.08 Quit duo8 (Ping timeout: 258 seconds) 20.10.48 Join duo8 [0] (~ZNC-SRV-H@117.6.48.103) 20.22.35 Join ceka [0] (~OK@37-48-5-180.tmcz.cz) 20.23.11 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 20.25.52 Quit japonecka (Ping timeout: 276 seconds) 20.36.08 # <__builtin> fishbulb: ping 20.36.47 # <__builtin> crap, sorry 20.36.52 # <__builtin> wrong person 20.56.03 Join AndyP_ [0] (bcdc32e6@gateway/web/freenode/ip.188.220.50.230) 20.58.22 # elensil: Uploaded ipod remote serial patch to gerrit. Works fine on my 2G Mini and 4Gen Greyscale. Still not with 1G Mini or 4th Gen Color/Photo. 21.03.34 Quit ceka (Ping timeout: 246 seconds) 21.17.26 *** Saving seen data "./dancer.seen" 21.23.56 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 21.24.27 # pamaury: I have new stories :-) 21.25.03 # pamaury: I had another "does not turn on" situation. I got the bootloader to start by plugging the device into the "always powered" usb port of my notebook while the notebook was in standby 21.25.31 # then the bootloader hang at "USB Connecting", maybe because I unplugged the USB very quickly after I saw the device turning on 21.25.55 # after I plugged it back in and waiting for a few seconds, it continued to "Loading Firmware" and "Executing", but hang there for several seconds (which is not normal), so I resetted it 21.26.18 # then some other stuff happened I don’t quite recall (I reset the device at least once more) and then I was able to turn it on normally with the power button 21.26.23 # afterwards, rockbox reported 100% battery 21.28.06 # just in case this is in any way helpful 21.30.17 # unfortunately the "freeze after usb unplug in bootloader" is a known bug, I simply does know how to fix 21.31.12 # ok, that’s easily avoidable 21.32.03 # I *think* the weird stuff i cannot quite recall involved the bootloader starting but hanging before Loading Firmware when i used the power button to turn it on 21.38.42 Join andyp__ [0] (~andyp@bcdc32e6.skybroadband.com) 21.39.15 Quit AndyP_ (Quit: Page closed) 21.41.19 Quit andyp__ (Client Quit) 21.43.02 Join lebellium [0] (~chatzilla@89-93-179-187.hfc.dyn.abo.bbox.fr) 21.47.08 Join xorly [0] (~xorly@ip-89-176-117-132.net.upcbroadband.cz) 21.52.43 # Horrorcat: I am almost done with the calibration curve, as soon as I have, I will push it 21.52.55 # I will push the power off commit immediately, it cannot hurt anyway 21.53.41 # Build Server message: 3New build round started. Revision 9a6700d, 255 builds, 16 clients. 21.54.33 # runtime was almost 22 hours, not bad given the size of the player and the age of the battery 21.56.56 # <__builtin> does someone have a USB HID-enabled device? 21.59.25 # __builtin: yes 22.00.26 # * __builtin gets a patch ready 22.01.21 # Build Server message: 3Build round completed after 460 seconds. 22.01.22 # Build Server message: 3Revision 9a6700d result: 0 errors 99 warnings 22.02.11 # <__builtin> pamaury: can you build and run g#1343 on said device? 22.02.12 # 3Gerrit review #1343 at http://gerrit.rockbox.org/r/1343 : 3OTP plugin: add typing code over USB by Franklin Wei 22.02.23 # <__builtin> the "otp" plugin under "apps" 22.02.23 Join edhelas [0] (~edhelas@145.133.43.230) 22.03.26 # building... 22.03.30 # what is this plugin doing ? 22.04.25 # <__builtin> it generates one-time passwords for online services 22.05.05 # * __builtin hopes it can type the passwords automatically now 22.05.29 Quit idonob (Ping timeout: 252 seconds) 22.05.54 Join idonob [0] (~Owner@S010610c37b922980.vs.shawcable.net) 22.06.57 # ok, what do I do with it ? 22.07.51 Join PurlingNayuki [0] (~Thunderbi@v163-44-154-238.a00f.g.sin1.static.cnode.io) 22.09.19 # <__builtin> ok, paste this content into a .txt file in the root: 22.09.29 Quit alexweissman (Remote host closed the connection) 22.09.37 # <__builtin> otpauth://hotp/test?secret=AAAAAAAA&counter=0 22.10.04 Join alexweissman [0] (~alexweiss@99-138-109-34.lightspeed.cicril.sbcglobal.net) 22.10.06 # <__builtin> then import the account (from file") 22.11.48 # done 22.13.31 # I tried the usb typing thing but it fails quite horribly: it generates an sequence of "_" (ie _______________________________) and never stops and freezes (had to hard reset) 22.14.18 # <__builtin> crap 22.14.20 Quit alexweissman (Ping timeout: 258 seconds) 22.17.17 # <__builtin> oh, it's a stupid mistake 22.18.40 # <__builtin> should be fixed now 22.18.59 Join girafe [0] (~girafe@LFbn-1-8020-64.w90-112.abo.wanadoo.fr) 22.21.50 # __builtin: now it generates something like "&é-(_" and then freezes 22.21.59 # still need to hard reset 22.22.24 # <__builtin> can you use the "show codes" feature properly? 22.22.39 # <__builtin> or did I break that too? ;) 22.26.03 # you mean generate code ? yes it works 22.26.10 # at least it displays numbers ^^ 22.27.07 # <__builtin> ok, that's a start 22.30.10 # pamaury: hey, if you have some time I can debug the usb audio patch 22.30.53 # <__builtin> pamaury: pushed a patch set with some debug info 22.31.08 # <__builtin> actually, the debug info is bugged too :P 22.31.10 # edhelas: huh sorry, not really right now and since I realized this patch is not the latest version (ie it misses some code I don't have anymore), I have to rewrite that part before any debugging is useful 22.31.11 # <__builtin> hang on 22.31.22 # pamaury: ok sure ;) 22.33.19 # <__builtin> pamaury: the newest patch set should splash some debug info before typing 22.35.09 # __builtin: displayed code is correct, typed one is not 22.35.31 # <__builtin> alright 22.35.39 # also still need to hard reset 22.36.12 # __builtin: I am slightly puzzled by your code 22.36.23 # <__builtin> yeah, it's due to the lack of an itoa() in rockbox 22.36.26 # while(*ptr++) go to the next character (!) 22.36.49 # I would rather do while(*ptr) and then char c = *ptr++ for a start 22.41.44 # ok with this suggestion the code now does not freeze but code is still not correct 22.41.55 # I wonder if there is a problem with the hid use page w.r.t key code 22.44.11 # <__builtin> weird 22.44.28 # <__builtin> what does it type? garbage? 22.44.54 # "àè""'_" 22.45.06 # yeah garbage but like "shifted" garbage 22.45.38 # I don't see an obvious mistake in the code 22.47.38 # <__builtin> maybe there isn't one 22.47.49 # <__builtin> could it be on a lower level? 22.48.12 Join paulk-nyan-big [0] (~paulk@188.25.244.20) 22.48.42 # __builtin: ok found the problem I think 22.49.09 # <__builtin> yeah? 22.49.10 # HID spec says code 0x1e is "Keyboard 1 and ! 4" 22.49.26 # so it might depend on the shift/maj/verrnum possibly 22.49.35 # just a theory 22.50.15 # but consistent with what I observe 22.51.26 # <__builtin> weird 22.51.40 # and I am not sure there is any good fix in the sense that the HID spec explicitely mandates that key codes are not actually key code, they are key position for this usage 22.51.57 # so "0" does not mean "character 0" it means "key at the same position that the usual 0 key" 22.52.10 # which is "à" on my french keyboard and I need to shift to get 0 22.52.13 # <__builtin> maybe using the keypad is better? 22.52.32 # keypad is better is you find how to make sure you are in number mode 22.52.46 # <__builtin> ohh crap 22.53.06 # or other pages 22.54.13 Quit xorly (Ping timeout: 244 seconds) 22.54.41 # <__builtin> does the host send it's numlock status to the device? 22.55.43 # no it should be the opposite: device sends its numlock status 22.56.33 # <__builtin> what about led status? 22.58.02 # yes it is reported as led status 22.58.19 # <__builtin> but are they consistent across locales? 22.58.49 # no idea 22.59.06 # <__builtin> I know the yubikey supports this same feature 23.00.08 # but somehow raw ascii data must be supported, I can't believe it's not the case 23.01.29 # <__builtin> dang, it appears the firmware is closed source 23.06.14 # __builtin: thereis the unicode page 23.06.20 # that's what you want to use 23.07.13 # <__builtin> yay :D 23.07.40 # the spec is quite vague, it should be in ISO/IEC 10646-1 UCS-2 (the two-octet form) 23.08.10 # * __builtin 's crappy router is failing to resolve usb.org 23.08.20 Quit petur (Remote host closed the connection) 23.08.55 # * pamaury is trying to understand how this page works 23.10.03 Quit Guest85177 (Ping timeout: 244 seconds) 23.10.16 # hum, I am not sure if this page is meant to send character to the host or from the host 23.10.51 # <__builtin> it's HID so probably to the host 23.12.39 # no 23.12.41 Join Guest85177 [0] (~Slayer@c-69-255-136-113.hsd1.va.comcast.net) 23.12.48 # it's from the host :( 23.13.03 # I have a small question. When no sound is played on Rockbox I heard a small white-noise on the iPodColor that I don't have on the Mini, anyone knows why ? 23.13.23 # HID is not only for dev -> host communication, LED are a perfect example: they can be changed by both host and dev. More generally HID supports lots of things 23.13.36 # <__builtin> darn 23.13.55 # <__builtin> well, I think for now I'll just have to assume a US keyboard layout 23.14.08 # <__builtin> unless... it could be user-configurable 23.14.24 # edhelas: probably hardware, it's quite common on many devices, unless it's really loud I guess, but I don't know for this specific device 23.14.38 # __builtin: maybe keypad would be a mostly working idea 23.14.49 # <__builtin> but how would it ensure number mode? 23.15.06 # <__builtin> besides asking for user intervention 23.16.18 # maybe keyboards are allowed to change their numlock status as long they notify host 23.17.19 # pamaury: it's funny because it seems even louder on the stock firmware 23.17.27 *** Saving seen data "./dancer.seen" 23.17.37 # well then don't complain :-p 23.17.44 # maybe caused by the default volume 23.18.04 # <__builtin> hardware issues, maybe 23.19.11 # going back to rockbox, when I don't play any song but having the volume at 0db I can clearly hear it, this is not caused by the software I imagine 23.20.18 # what does rockbox do actually when you change the volume ? it tell some chipset to get more power to amplify the sound more, which can cause the white noise to be louder ? 23.20.25 # edhelas: no, at best software is configuring hardware correctly and noise is generated because , worse this is hardware design problem and you can't do anything about it 23.20.41 # *no configuring 23.21.15 # but as I said this is a very frequent problem 23.21.25 Quit Guest85177 (Ping timeout: 244 seconds) 23.21.39 # on some/many chips, you could have no noise but then you would have a pop when you resume so... 23.21.40 # okay :) it's not an issue to me, I was just curious, thanks for the answer 23.28.52 Join Guest85177 [0] (~Slayer@c-69-255-136-113.hsd1.va.comcast.net) 23.36.07 # __builtin: it's kind of tricky but it's potentially possible: you could have a virtual button to ask the host to switch num lock and since the keyboard knows numlock, you can switch it if needed (and then back to restore proper lock after) but it's not exactly nice 23.39.45 # <__builtin> hmm, that would work 23.40.46 # <__builtin> the only issue is that my menu system is totally from scratch 23.40.57 # <__builtin> so adding it will be a bit of a hassle 23.41.26 # * pamaury has a try at the numlock thingy 23.41.43 # * __builtin thinks he can do it 23.42.43 # <__builtin> ok, this should work 23.43.52 # <__builtin> pamaury: pushed new patch set 23.44.10 # <__builtin> you should have a new option in the send code menu for numlcok 23.44.13 # <__builtin> *lock 23.44.35 # __builtin: I had in my mind something more "automatic", let me try it and I'll send you the code 23.45.09 # <__builtin> cool 23.50.17 # * pamaury spots something clearly wrong the hid driver but already knows about it and pretends he didn't see it 23.52.19 # <__builtin> what is it? 23.52.59 # usb_drv_recv might return before buffer is filled 23.53.22 # it's irrelevant is almost all drivers but on hid it's potentially a problem for led status 23.53.54 Quit lebellium (Quit: ChatZilla 0.9.92 [Firefox 46.0.1/20160502172042])