--- Log for 24.10.111 Server: leguin.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 20 days and 16 hours ago 00.00.01 # My mp3 player is a Samsung R0, the RB port is in good progress thanks to an Italian developer. I actually ported the now playing screen of Samsung and improved it a bit (bitrate + album year ) 00.02.17 # Darko: Did the Clip just die, as in refuse to turn on again? If it's recognised as a drive on your PC, then you should just be able to format it to Fat and just drag the Firmware .bin file onto it. 00.02.50 Quit dfkt (Quit: -= SysReset 2.55=- Sic gorgiamus allos subjectatos nunc.) 00.03.12 # I tried that KiwiCam at first, I formatted it as FAT32 and dragged m30pa.bin and still black screen 00.03.20 # should i disconnet USB and resolder battery? 00.03.34 *** Saving seen data "./dancer.seen" 00.04.06 # maybe it needs FAT system to boot? 00.04.27 Quit Strife89 (Quit: Here we go!) 00.04.36 # Have you got the correct version of the Firmware? There's an 01 & an 02 for the V2 00.04.55 # Darko: you need to follow those instructions 00.05.22 # lebellium: i haven't heard much about that device lately, who is working on it? 00.06.59 # well, the firmware IS right because before rockboxing procedure I updated it with Sandisk utility and it said 02.01.35 00.07.24 # thats the one I downloaded later from sandisk page for manual installation 00.08.03 # i hope it is right, has same name in zip archive clip02.01.35.zip 00.08.09 # saratoga: Lorenzo is working on. RB runs on his and on my R0. The interface shows up, keys work, plugins work and there is a basic audio support (for the moment 100% hardware volume so much distorsion and hiss). You can follow the progress on ABI but soon he'll update the RB wiki page 00.08.27 # and m30pa.bin when extracted 00.08.32 # is this an App port or firmware port? 00.09.07 # saratoga: the R0 has a Linux kernel so that's more like an app port :) 00.09.16 # ah ok 00.09.33 # i didn't realize that had progressed so far, yeah you guys should update the wiki 00.09.49 # might be a good idea to keep in contact with people here working on the android stuff so that its easier to merge your changes as well 00.09.51 # Darko: I've never had to recover an AMS sansa, so I don't know the details, but I have a vague memory that you need more than the OF file you download from sandisk. IIRC you need a larger dump from a working player 00.10.05 # saratoga: http://www.anythingbutipod.com/forum/showthread.php?p=580604#post580604 00.11.05 # lebellium: That looks like a great device. Nice price too. I'd grab one if it was half the size and the same resolution. 00.11.47 # KiwiCam: I could give one, I have 3 R0 among my 30 DAPs hihi 00.12.19 # @gevaerts you mean that (what you wrote) for this manual copying of .bin image from windows? 00.13.57 Quit [Saint] (Ping timeout: 252 seconds) 00.14.37 # Darko: I have no idea what you're asking 00.14.39 # lebellium: are you working on it too, or just that guy? 00.15.25 # gevaerts, you said i need more than OF file 00.15.38 # you mean, dd and .bin is not enough? 00.16.16 # saratoga: No, I don't really work on it, I don't have any Rockbox knowledges, he's the current main developer (but 2 other guys already worked on the port previously) and I'm the Community or Project Manager lol 00.16.33 # lebellium: hmm ok 00.16.48 # they should really post their source and let the app people here know what they're doing or else they may have quite some trouble merging their changes in 00.17.39 # Yeah but he was waiting for setting the R0 target before posting on the RB wiki 00.17.40 # Darko: as I remember it, the .bin file you can download from sandisk doesn't have all data you need, so you need a .bin file dumped from a working player 00.17.56 # a-ha! 00.17.59 # Before it was rather draft work 00.18.02 # why dont you say so :) 00.18.19 # do you know a place for that on rocbox forum maybe? 00.18.48 # lebellium: FWIW i think everyone who has ever done that has not managed to get their code into SVN . . . 00.19.06 # usually they show up with some big mess that no one else wants to touch 00.19.26 # it works much better if people provide feedback while the port is working so that bad decisions get caught early while they're easy to fix 00.19.51 # gevaerts this is it http://daniel.haxx.se/sansa/amsfw.html 00.20.21 # i found this page before, never asumed fot its purpose - now i do :) 00.20.37 # That was a big mess, now the target is set up, he cleaned the shit and we'll be able to post on the RB site soon and share with anyone :) 00.20.47 # ok 1 step closer... 00.20.59 Quit keyb_gr (Ping timeout: 252 seconds) 00.22.26 Quit robin0800 (Quit: Leaving) 00.23.13 # the problem is that your idea of clean will probably not match ours :) 00.23.20 # i've posted in that thread 00.23.42 Quit KiwiCam (Quit: Leaving) 00.23.58 # saratoga: that's possible, actually I don't have any idea what's clean for you and for us, I'm not developing at all excep basic language on my TI at the time lol 00.24.06 Join KiwiCam [0] (~KiwiCAM@206.192.69.111.dynamic.snap.net.nz) 00.24.33 Quit kadoban (Ping timeout: 276 seconds) 00.24.43 Join keyb_gr [0] (~chatzilla@p4FF04A81.dip.t-dialin.net) 00.26.49 Join fyrestorm [0] (~nnscript@cpe-24-90-84-81.nyc.res.rr.com) 00.27.19 Join telliott [0] (~Tim@d27-96-170-180.evv.wideopenwest.com) 00.27.59 # Any new developements in the newest iPoc Classic battery issue? 00.28.39 Quit keyb_gr (Client Quit) 00.30.37 Quit liar (Remote host closed the connection) 00.31.49 # New commit by 03pamaury (r30835): sbtools: be more verbose on real key and iv; add very advanced code to craft images 00.33.01 # pamaury: whats the install process for the fuze+ like at the moment? 00.33.38 # r30835 build result: All green 00.34.11 Quit ender` (Quit: Where there's a will, there's an inheritance tax.) 00.34.26 Join Scromple [0] (~Simon@115-64-195-104.static.tpgi.com.au) 00.35.11 # installing the bootloader is a bit tricky; there are two ways. In any case, one needs to decrypt a valid firmware, extract some part of it, insert rockbox code and rebuild the firmware image. Then either one uses the OF update code (just put firmware.sb at root) or build a not-dualbooting version of the bootloader that gives access to the OF partition and then send it in recovery mode and then dd'it using the firmware.sb file (basically) :) 00.35.29 # The tricky point here is building the firmware image so that it actually dual-boot 00.40.54 Join robin0800 [0] (~robin0800@149.254.61.39) 00.43.18 # saratoga: Currently building the firmware images requires to use two tools: sbtoelf and elftosb, but I think I will write a condense version of both just to build the dual boot image, so it's easier to integrate it into rbutil 00.43.49 # pamaury: so it would work like ams where you patch a firmware and then copy it over? 00.44.04 # yes 00.44.13 # except that the format is much more complicated 00.44.44 # mkimxboot :) 00.44.46 # in any case you need the OF for the hardware init but you can easily build a non dual booting version of it 00.47.05 Quit Darko (Quit: Page closed) 00.48.06 Quit pamaury (Remote host closed the connection) 00.49.15 Join Topy44 [0] (~Topy44@f049179229.adsl.alicedsl.de) 00.53.40 # hey saratoga 00.54.48 # hey 00.54.51 # funman 00.58.33 Quit lebellium (Quit: ChatZilla 0.9.87 [Firefox 8.0/20111019081014]) 00.58.35 # you put the clipv2 image online ? 00.59.54 # funman: no i was asking if you did 01.00.08 # i don't have a copy of it, but i believe you did at one point? 01.07.01 Quit linuxstb (Ping timeout: 245 seconds) 01.07.24 Join linuxstb [0] (~linuxstb@94-193-103-239.zone7.bethere.co.uk) 01.07.24 Quit linuxstb (Changing host) 01.07.24 Join linuxstb [0] (~linuxstb@rockbox/developer/linuxstb) 01.21.29 Quit Hadaka (Remote host closed the connection) 02.03.35 *** Saving seen data "./dancer.seen" 02.41.20 Join ChickeNES [0] (~ChickeNES@128.135.100.102) 02.45.14 Quit hilbert (Quit: Textual IRC Client: http://www.textualapp.com/) 02.49.45 # saratoga: perhaps it's still on a ocmputer in south of france 02.49.53 # lol 02.50.35 # i'll ask around and see if anyone else saved one 02.53.41 Quit AlexP (Remote host closed the connection) 02.56.11 # ok 02.56.14 Quit funman (Quit: leaving) 02.56.36 Quit Scromple (Ping timeout: 245 seconds) 03.06.59 Join ruboboo [0] (~jasonwest@24-236-32-91.nm.warpdriveonline.com) 03.40.49 Quit ChickeNES (Read error: Connection reset by peer) 03.41.11 Join ChickeNES [0] (~ChickeNES@128.135.100.102) 03.41.52 Quit ChickeNES (Read error: Connection reset by peer) 03.42.13 Join ChickeNES [0] (~ChickeNES@128.135.100.102) 03.44.03 Quit MethoS- (Remote host closed the connection) 03.44.22 Join Rob2223 [0] (~Miranda@p4FFF11E0.dip.t-dialin.net) 03.47.51 Quit Rob2222 (Ping timeout: 245 seconds) 03.48.52 Quit ChickeNES (Read error: Connection reset by peer) 03.49.59 Join ChickeNE_ [0] (~ChickeNES@128.135.100.102) 04.03.36 *** Saving seen data "./dancer.seen" 04.12.01 Quit robin0800 (Ping timeout: 258 seconds) 04.19.03 Quit telliott (Quit: Leaving) 04.21.19 Quit ChickeNE_ (Quit: Computer has gone to sleep.) 04.22.08 Quit [7] (Disconnected by services) 04.22.19 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 04.36.25 Join ChickeNES [0] (~ChickeNES@128.135.100.102) 04.52.41 Quit amiconn (Disconnected by services) 04.52.41 Join amiconn_ [0] (quassel@rockbox/developer/amiconn) 04.52.46 Join Scromple [0] (~Simon@115-64-195-104.static.tpgi.com.au) 04.53.03 Nick amiconn_ is now known as amiconn (quassel@rockbox/developer/amiconn) 04.53.41 Quit pixelma (Disconnected by services) 04.53.43 Join pixelma_ [0] (quassel@rockbox/staff/pixelma) 04.53.45 Nick pixelma_ is now known as pixelma (quassel@rockbox/staff/pixelma) 04.54.56 Join kadoban [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 05.15.10 Quit ChickeNES (Quit: Computer has gone to sleep.) 05.23.12 Nick soap is now known as soap_ (~soap@rockbox/staff/soap) 05.37.28 Quit Topy44 (Read error: Connection reset by peer) 05.38.22 Join Topy44 [0] (~Topy44@f049179229.adsl.alicedsl.de) 05.39.40 Join ntkm [0] (~taku@g1-223-25-129-7.bmobile.ne.jp) 05.40.31 Join Rob2222 [0] (~Miranda@p4FFF0F04.dip.t-dialin.net) 05.43.00 Quit ntkm (Client Quit) 05.43.38 Quit Horscht (Quit: Verlassend) 05.44.07 Join [Saint] [0] (~Saint]@101.98.129.152) 05.44.07 Quit [Saint] (Changing host) 05.44.07 Join [Saint] [0] (~Saint]@unaffiliated/saint/x-8516940) 05.45.01 Quit Rob2223 (Ping timeout: 276 seconds) 05.45.18 # * [Saint] wonders if the sansaAMSunbrick page should be harder to find... 05.45.57 # <[Saint]> reading the forum, I sincerely doubt that "crack open and reset" was the first logical step to take in that users case. 05.46.12 Quit antil33t (Ping timeout: 240 seconds) 05.46.16 # <[Saint]> especially given the apparent skill level of said user. 05.46.40 Join antil33t [0] (~antil33t@203-100-223-143.callplus.net.nz) 05.46.58 # <[Saint]> .Its easy to say now, as, what's done is done and it can't be proven...but, I'd put money on it at the time that it just needed a hard resetr 05.46.59 # holy crap! 05.47.13 # <[Saint]> ...yeah. 05.48.02 # I tihnk a nice warning on the wiki page (if it isnt there already) wouldnt hurt 05.49.25 # <[Saint]> I think the common convention of "crashed==bricked" leads users there. We can't fix that. 05.49.31 # <[Saint]> Unfurtunate, though. 05.49.39 # <[Saint]> *unfortunate 05.50.42 # <[Saint]> The really funny thing is (reading now) the unbrick page fails to mention that to fully recover you need a dd of a perfectly working player's FW partition. 05.51.21 # <[Saint]> copying a patched OF there is enough to get RB to boot, but the OF expects more magic. 05.51.38 # * JdGordon adds a warning 05.52.13 # <[Saint]> ah "You can write the whole OF-Image onto that by using e.g.:" 05.52.20 # <[Saint]> it *does* assume you already have this image. 05.52.31 # <[Saint]> its just not exactly clear about how you need to get it ;) 05.52.36 # it shouldnt be :) 05.52.43 # forces people to come and ask!' 05.53.01 # but yeah, i remember dding the of image from their website when i did mine 05.53.14 # <[Saint]> Yeah..."hey, do you mind cracking open your player and dumping for me" is a bit of a hard ask. 05.53.52 # <[Saint]> JdGordon: Was that enough to get the OF fully working? IIUC, it shouldn't have been. 05.54.29 # I'm assuming he had the clipv2 problem where it can't boot the patched firmware 05.54.51 # <[Saint]> saratoga: I think it just crashed. And he didn't know about hard reset. 05.55.04 # did he ever get it to actually boot? 05.55.05 # hey [Saint] 05.55.10 # are there any new interesting android interfaces I should try? 05.55.44 # <[Saint]> saratoga: Form the forums...I'm guessing not. Unless there's more I missed from here. 05.55.55 Join ChickeNES [0] (~ChickeNES@128.135.100.102) 05.56.08 # if it never booted after he patched the firmware he did the right thing, if it booted and then crashed he fucked up badly 05.56.46 # <[Saint]> alexbobp: Not presently, sorry. I need to get my current work on the tracker. I'll remember to give you a buzz when I do. 05.56.51 # <[Saint]> saratoga: "Hi! 30 minutes ago I had perfectly working Clip v2, now it's dead. Or it appears to be so. "Crashed" or "Bricked", what's the differece? Rockbox configured and installed succesfully, but now it won't boot. Battery is/was at 100% charge." 05.57.02 # [Saint]: alright. 05.57.02 # <[Saint]> So yeah..."messed" up badly. 05.57.15 # i don't think its clear from that what he did 05.57.26 # [Saint]: it was so long ago I dont remember, but I did get a working clip+ again after doing it 05.57.31 # <[Saint]> Well, it mentions it installed correctly. 05.58.05 # i think hes managed to phrase that description in such a way that it describes nothing 05.58.54 Quit fyrestorm (Read error: Connection reset by peer) 05.59.38 # <[Saint]> ...it just scares me that we get first posts like that in the forums. I *really * scares me. I mean at least there's no "and its your fault!" though. 06.00.36 # i just gave him the benefit of the doubt since he managed to open his player, but after the rest of the thread i'm not sure it was warrented 06.00.46 # I wonder if thats because anyone smart enough to find and follow those steps knows its unlikely we did anything on purpose 06.01.14 # anyone outright dumb will complain but be happy with "hard reset your player" type recovery steps 06.01.38 # [Saint]: i have a bricked clip+ -- are you saying I don't need to crack it open? I saw that page and then gave up 06.02.04 # <[Saint]> sillytones: It probably wasn't the first step, no. 06.02.04 # sillytones: are you *sure* it is bricked... that you cant get it to any recovery mode? 06.02.08 # <[Saint]> But, what's done is done. 06.02.21 # <[Saint]> JdGordon: It sure is now ;) 06.02.30 # I just can't get it to turn on. 06.02.47 # <[Saint]> the FW partition is now FAT32, she's not turning on... 06.02.56 # plugged in to usb or not. last thing I saw was a frozen screen that I hard powered down 06.03.39 *** Saving seen data "./dancer.seen" 06.03.40 # i don't think it should be possible to get a clip+ into a state where you need those directions without screwing up a firmware patch 06.03.49 # sillytones: you want to talk to funman (who isnt on irc much anymore) 06.03.53 # if it stops working and you can't get it to power on its probably just broken 06.04.10 # also that ^ 06.04.25 # <[Saint]> What you're going to need to do (assuming its not just broken), is delete the partition from the FW partition you uncovered. And place a ROckkbox patched firmware file in it and reboot. 06.04.27 # hold the power button/switch for a good 30s and plug in usb 06.04.50 # <[Saint]> JdGordon: That *would* work, assuming the FW partition was intact. that's past, now. 06.05.08 # assuming you've let it sit for a couple days, plugging it into USB should be enough to reboot it 06.05.11 # <[Saint]> s/*would/*should*/ 06.05.12 # ok i'll try it 06.05.23 # [Saint]: sillytones is not the person in the thread 06.05.37 # <[Saint]> Oh...wow. Fail. 06.06.02 # <[Saint]> That was, a weird coincidence. 06.06.18 # I'd also be willing to mail it to someone in rockbox if there's anybody who'd want a possibly bricked or broken Clip+ to mess around with 06.06.40 Nick froggyman_ is now known as froggyman (~seth@50.105.149.180) 06.06.45 # did you try plugging it into USB after it sat around for more then a few days? 06.06.49 Quit froggyman (Changing host) 06.06.49 Join froggyman [0] (~seth@unaffiliated/froggyman) 06.06.56 # <[Saint]> No, no...sorry. I thought you were someone in our forums having a similar problem. 06.07.07 # <[Saint]> It should be sufficient to let the batter drain. 06.07.12 # <[Saint]> *battery 06.07.38 # [Saint]: yeah it was talking about that similar problem that attracted my interest :) 06.08.02 # saratoga: i'm not sure. it's been sitting in my drawer for a few weeks now though 06.08.11 # plug it in and see if it comes on 06.08.21 # so my plan is to hold down the power button for a good 30s and then plug it in 06.09.22 # no just plug it in 06.09.24 # nothing more 06.09.31 # alright here goes 06.09.48 Join ageis00 [0] (~ageis@c-76-127-201-198.hsd1.ma.comcast.net) 06.10.03 # well windows says "installing device software--> ready to use 06.10.19 # and that I need to format the drive 06.10.24 # but the screen doesn't come on 06.10.26 # did the player boot up? 06.10.36 Quit ageis (Ping timeout: 252 seconds) 06.10.40 Quit linuxstb (Read error: Operation timed out) 06.10.41 Quit simabeis (Write error: Broken pipe) 06.10.45 Join simabeis_ [0] (~simabeis@lobmenschen.de) 06.10.46 # no, the screen did not change at all 06.10.47 # thats probably just a bad memory chip 06.11.02 Join linuxstb [0] (~linuxstb@rockbox/developer/linuxstb) 06.11.10 Nick ageis00 is now known as ageis (~ageis@c-76-127-201-198.hsd1.ma.comcast.net) 06.11.21 # you could try flashing a new firmware image to it, but my guess is that the nand isn't working anyway so it wouldn't work 06.11.47 # should I format it 06.12.02 # and can I use rockbox utility to try a firmware flash 06.12.31 # how big is the disk that mounts? 06.13.25 # explorer thinks it is 0 bytes 06.13.58 # but it also wants to format it, so it might just not be able to tell how big it is 06.14.33 # you at least arent at the point you need to to the full unbrick 06.14.43 # the disk manager can tell you how big unformatted disks are 06.16.06 # <[Saint]> right click on My Computer and hit Manage 06.16.21 Quit ChickeNES (Quit: Computer has gone to sleep.) 06.16.25 # thanks [Saint] 06.16.55 # 31 MB 06.17.15 # that's a far cry from 2 GB 06.17.22 # thats recovery mode 06.17.34 # <[Saint]> ...how the? weird. 06.18.54 # huh, never heard of someone getting a disk that size 06.19.05 # JdGordon: is that a good thing or a bad thing 06.19.16 # <[Saint]> its supposed to be ~900MB for recovery mode iirc. 06.19.32 # I *thought* that was a good thing, but sounds like im misremembering, listen to saratoga i tihnk :) 06.20.02 # <[Saint]> I have seen people manage to uncover a partition of this size before. 06.20.16 # <[Saint]> I don't think we have any idea why, or what it is. 06.21.06 # I can reboot into ubuntu if that would help 06.21.07 # <[Saint]> Sometimes I've seen people go through the unbrick steps and think they've hit recovery mode but its this 30oddMB partition. 06.21.53 # <[Saint]> from memory, and the unbrock page seems to document, it should be ~980MB 06.21.59 # <[Saint]> *unbrick 06.22.32 # At first I thought the memory chip went bad like saratoga thought, and all it had working was 31 MB 06.24.21 # <[Saint]> I have seen this before, I'm just nowhere near educated about the target to say what this means. 06.25.15 # what do you think I should do from here 06.25.28 # who is funman and how can I contact him? 06.26.47 # <[Saint]> funman is/was the resident SansaAMS expert. He floats in and out these days, Rockbox isn't so much a priority for him any longer. 06.29.48 Join Buschel [0] (~chatzilla@p54A3BA9C.dip.t-dialin.net) 06.34.00 Join freddyb [0] (~freddybbb@216.8.239.112.etczone.com) 06.38.09 # JdGordon: At this point I favor wrong and working vs. right and broken. You outrank me by a long shot and you can get r30826 reverted if you want but I don't think you should. 06.38.36 # freddyb: hey, woah now :) 06.38.54 # I just want to make sure the correct code gets in... 06.39.10 # I dont think the font_get_ui() call it so bad, but it is in the wrong place 06.39.56 # Ok, what do you propose? 06.40.59 # font.c should only deal with id's and the magic sysfont. any FONT_UI/FONT_SYSFIXED magic ideally would be handled by the screen_access api 06.41.05 # <[Saint]> freddyb: I think there would be seven different types of uproar from..."a few select people" if Jd tried to suggest reverting anything, right wroung or no. 06.41.45 # [Saint]: see the mailiong list how a revert request should happen.... 06.42.02 # freddyb: see apps/screen_access.c screeb_helper_setfont() 06.42.28 # I'd like an equivilant for getfont() which is exactly what you've done with font_get_ui() 06.42.34 # [Saint]: Please don't stir the pot right now... 06.44.37 # freddyb: that screen_helper_Setfont() isnt quite a good example as that was dont to hook between plugins and font api, but thats where the ui font handling should be imo 06.45.13 # also, font.c should get a font_get_height(int id) function which would remove a good deal of issues elsewhere L( 06.45.51 # JdGordon: I thought about sticking in font_get_height() myself. 06.46.18 # that really is a no brainer when you see what calls font_get() :) 06.48.02 # JdGordon: I have no objection to moving everything to use global_status.xxx or userland_get_user_font() except that it hasn't been done yet and a plugin that asks for FONT_UI and gets a theme font with only 12 glyphs for a timer display is going to saw through the hard drive. 06.48.18 Quit Topy44 (Ping timeout: 256 seconds) 06.48.35 # (Each glyph miss can be/ is likely to be three disk seeks.) 06.49.40 # global_status.font_id[screen] is set from the global_setting.font filename so that wont happen 06.49.44 # unless that changes also 06.50.11 # No. I mean if a plugin or whatever is not updated and makes the get_font(FONT_UI) call. 06.50.29 # remove get_font() from the plugin api 06.50.44 # or hook a wrapper in 06.50.47 # which i tinhk i did 06.51.38 # ah, no, i didnt get to doing that 06.52.07 # It really wasn't clear to me that FONT_UI was deprecated... 06.53.04 # yeah, well I was hoping to finish the work myself... 06.53.28 # but that is irrelevant anyway 06.53.47 # I don't remember any plugins which call font_get() for any reason other than getting the font height 06.55.09 # rockpaint does some weird/nice stuff, but otherwise all other calls can be worked around 06.56.20 # I really didn't look but if they want the height, we should give them the right number. 06.57.03 # lrcplayer uses the font* to call font_get_width() which is fine, but that plugin should load its own copy of the user font really 06.57.10 # or a font it wants 06.57.42 # rb->font_load() will be a noop anyway if it is already loaded 06.59.32 # I'd prefer to narrow this discussion to just getting the right font index to the callers. The metrics have already been worked out, right? 07.00.01 # ? 07.00.34 # Not every plugin wants to have it's own font. Most of them just want what used to be FONT_UI, right? 07.00.44 # correct 07.01.49 # So, if we can agree on some user space (app space?) way of getting what used to be FONT_UI we're set, right? Does global_settings.xxx[] satisfy that? 07.02.05 # yes 07.02.51 # if font_set/get_ui() is moved to apps and hooked into the screen_access and plugin api's that would be great 07.03.04 # then it is transparent to plugins 07.03.42 # screen_access_set_defaults or something? 07.04.12 # if i wasnt at work I'd do the patch quicky for you now 07.05.09 # I'm in no hurry, if you want to post it on FS that would suit me. 07.05.24 # I'll see about doing it tonight, depends how late i get home 07.05.51 # http://www.rockbox.org/tracker/task/12337?getfile=24204 is wrong which is why i brought it up 07.05.58 # - skin_viewport->vp.font = global_status.font_id[display->screen_type]; 07.05.59 # + skin_viewport->vp.font = font_get_ui(); 07.06.22 # FONT_UI depends on the screen, so that change will get the wrong one 07.08.31 Quit Riviera (Ping timeout: 248 seconds) 07.09.33 # TheSeven: if you have some spare time it would be great if you could check FS#12310 07.09.33 # http://www.rockbox.org/tracker/task/12310 3Crash when inserting USB while playback (since r30097) (bugs, new) 07.10.55 # seems like since a change from jhMikeS (r30097) the interrupt or DMA handling for USB and PCM interfere 07.12.29 Quit Buschel (Quit: ChatZilla 0.9.87 [Firefox 7.0.1/20110928134238]) 07.12.52 # saratoga: [Saint]: can anything worse happen to my clip + if I try to use rockbox utility on it? 07.14.09 # <[Saint]> I would expect it to fail personally. I have my doubts it could make anything worse, but, wait for saratoga to respond. 07.28.53 Join n1s [0] (~quassel@rockbox/developer/n1s) 07.29.07 Quit freddyb (Quit: Leaving) 07.32.49 Quit factor (Read error: Connection reset by peer) 07.36.14 Quit n1s (Ping timeout: 255 seconds) 07.50.23 Join factor [0] (~factor@74.197.205.204) 08.03.41 *** Saving seen data "./dancer.seen" 08.25.51 Join mortalis [0] (~c3133585@www.haxx.se) 08.37.00 Quit factor (Ping timeout: 240 seconds) 08.39.35 Join Zagor [242] (~bjst@rockbox/developer/Zagor) 08.54.32 Quit [Saint] (Ping timeout: 245 seconds) 08.58.23 # Buschel: ACK (put on my todo list :P) 09.02.40 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 09.02.50 Join ender` [0] (~ender@foo.eternallybored.org) 09.03.52 Join factor [0] (~factor@74.197.205.204) 09.09.45 Join tails___ [0] (chikakitaa@ip-78-139-196-175.danet.in) 09.09.45 Quit chkktri_ (Read error: Connection reset by peer) 09.12.24 Quit Scromple (Quit: Leaving) 09.14.43 Nick tails___ is now known as chkktri_ (chikakitaa@ip-78-139-196-175.danet.in) 09.16.20 Quit ruskie (Quit: ...) 09.27.28 Join petur [0] (~petur@rockbox/developer/petur) 09.32.53 Quit bieber (Read error: Connection reset by peer) 09.37.21 Join ruskie [0] (ruskie@sourcemage/mage/ruskie) 09.53.14 Join Naked [0] (~naked@naked.iki.fi) 10.03.44 *** Saving seen data "./dancer.seen" 10.06.08 Join [Saint] [0] (~Saint]@101.98.129.152) 10.06.08 Quit [Saint] (Changing host) 10.06.08 Join [Saint] [0] (~Saint]@unaffiliated/saint/x-8516940) 10.17.50 Join Darko [0] (5fb434a9@gateway/web/freenode/ip.95.180.52.169) 10.18.01 # hello 10.18.16 # ehat Linux distro to use for Sansa Clip recovery? 10.18.21 # what 10.18.44 # <[Saint]> any. Its not even necessary to use Linux. 10.18.59 # <[Saint]> the equivalent tools on WIndows will work just fine. 10.19.06 # well it is not listend on Knoppix DVD release 10.19.19 # <[Saint]> "it" == ? 10.19.19 # what are equivalent tools on Win? 10.19.29 # dd tools 10.19.35 # I was last evening here 10.19.40 # thats what I was told 10.19.59 # <[Saint]> If every standard linux tool was listed...it would be a LONG list ;) 10.20.05 # ok 10.20.05 # <[Saint]> and Linux distro will have dd 10.20.10 # <[Saint]> *any 10.20.33 # do you know Windows equivalent? 10.20.38 # dd for Win i tried 10.20.44 # but nothing happend 10.21.18 # this is a command from Linux 10.21.20 # dd if=orig_image.bin of=/dev/sde 10.21.26 # i understand the second part 10.21.42 # can you help if my .bin image of OF is on my C: drive 10.21.51 # <[Saint]> Ah! you're the guy who panicked and decided to open their player and attempt to "unbrick it", yes? 10.21.59 # <[Saint]> from the forums? 10.21.59 # what would be correct sintax 10.22.07 # yes i am :) 10.22.08 # same nick 10.22.15 # my name really 10.23.30 # <[Saint]> dd if=whatever_your_binary_image_is_called.bin of=/path/to/device 10.23.59 # but how it will know my image is on root of C drive? 10.24.27 # <[Saint]> easy, you go to the location of it from the commandline ;) 10.25.01 # ok, but how to do that 10.25.17 # how to run command line in Linux? (what Linux also?) 10.25.24 # root 10.25.53 # you understand what troubles me right? 10.26.05 # <[Saint]> Look...what OS are you running RIGHT NOW? 10.26.11 # Windows XP Sp3 10.26.34 # <[Saint]> dd for win should be fine (assuming its setup correctly) 10.26.49 # i said up there i tried dd win 10.26.54 # nothing happend 10.27.09 # sintax was something like this 10.27.37 # <[Saint]> My assumption would be user error, but, ok. Lets try a Linux distro. 10.27.49 # <[Saint]> Boot a liveCD of your choice, and come back. 10.28.20 # ok i just need to download it and that will take a while 10.28.25 # thanks Saint :) 10.28.33 # Ubuntu is ok? 10.28.40 # isn't the question simply "what is the raw device syntax in windows"? 10.28.40 # <[Saint]> Yes, Ubuntu is fine. 10.30.07 # Zagor, are you trying to say if my OF image is on C: and broken Sansa (unformatted) on G: what would be the syntax in dd for Win? 10.31.10 # I found WinDD here http://sourceforge.net/projects/windd/ 10.31.16 # what do you think of it? 10.31.44 # its for people with less IQ like me :) (around 140) 10.33.01 # I know how dd works, but I don't know how dd works in windows, since the device syntax is completely different. 10.34.03 # I assume "dd if=file.bin of=g:" is not working? 10.34.36 # <[Saint]> (where g: == "correct drive letter) 10.35.45 # Zagor I havent tried in Linux yet, Ubuntu is downloading right now, but i won't be at home till later this day 10.36.07 # I also found this pages http://www.chrysocome.net/dd and http://www.chrysocome.net/rawwrite 10.36.25 # in dd, do i have to define block size? 10.36.32 # this was for windows. only windows uses the colon syntax 10.36.58 # because only windows uses (user visible) drives 10.36.59 # sorry 10.37.20 # the first site suggest you can get the device names with the --list option 10.37.40 # @ukleinek user visible drives -- but it is not formatted - how it will be seen then? 10.39.23 # block size - anyone? 10.39.36 # no you don't have to specify block size 10.40.02 # ok 10.40.17 # well thank you everyone 10.40.33 # will wait to download Ubuntu and will try later this evening 10.40.40 # See you 10.48.17 Quit Darko (Quit: Page closed) 10.51.42 Quit Naked (Remote host closed the connection) 11.06.29 # judging from the commits over the weekend, it doesn't look like we're ready to branch off 3.10 today? 11.07.40 # probably not, but still, is there a list of required fixed issues before we just drop the release all together? 11.08.13 # *if* voice is actually broken I'd say thats a candidate to forget about it 11.08.45 # I'd say the pink ones on our bug list sounds like stuff we can't release 11.09.14 # and it appears amiconn still hasn't added his lockup bug 11.09.40 Quit ageis () 11.14.21 Join hilbert [0] (~hilbert@adsl-89-217-34-158.adslplus.ch) 11.24.24 Join dfkt [0] (dfkt@unaffiliated/dfkt) 11.28.01 Join MethoS- [0] (~clemens@134.102.106.250) 11.29.56 Quit mortalis (Quit: CGI:IRC (EOF)) 11.34.34 Join ageis [0] (~kevin@c-76-127-201-198.hsd1.ma.comcast.net) 11.36.07 Join amiconn_w [0] (5795b6ef@gateway/web/freenode/ip.87.149.182.239) 11.42.10 Join GodEater_ [0] (93722cd0@rockbox/staff/GodEater) 11.46.37 Quit amiconn_w (Ping timeout: 265 seconds) 11.47.27 Join bluebrother [0] (~dom@g231121000.adsl.alicedsl.de) 11.47.27 Quit bluebrother (Changing host) 11.47.27 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 11.48.28 Quit bluebrother^ (Read error: Operation timed out) 11.49.35 Quit fs-bluebot (Ping timeout: 240 seconds) 11.50.27 Join mortalis [0] (~c3133585@www.haxx.se) 11.51.15 Join fs-bluebot [0] (~fs-bluebo@g231121000.adsl.alicedsl.de) 12.03.48 *** Saving seen data "./dancer.seen" 12.03.49 Join amiconn_w [0] (5795b6ef@gateway/web/freenode/ip.87.149.182.239) 12.05.39 Join Thra11 [0] (~thrall@245.39.113.87.dyn.plus.net) 12.31.10 Quit MethoS- (Read error: Connection reset by peer) 12.32.38 Join MethoS- [0] (~clemens@134.102.106.250) 12.35.10 Join Ryuku [0] (~5f07662e@www.haxx.se) 12.36.09 # ohai 12.36.38 # http://www.rockbox.org/wiki/SansaFuzePlusPort?rev=13 12.36.51 # how long will it take some has an idea ? 12.40.19 # <[Saint]> "as long as it takes, and no sooner" is the general timeframe. 12.40.43 # <[Saint]> no one can tell if there's be some blocker that might make it *never* be released, until it is. 12.46.47 # i see :( thx 12.48.30 Quit Ryuku (Quit: CGI:IRC) 12.50.11 Quit amiconn_w (Quit: Page closed) 12.51.06 Join dfkt|x [0] (~dfkt@chello062178002170.1.11.univie.teleweb.at) 12.51.06 Quit dfkt|x (Changing host) 12.51.06 Join dfkt|x [0] (~dfkt@unaffiliated/dfkt) 12.54.02 Quit kadoban (Ping timeout: 244 seconds) 13.00.26 # is there an issue with album art display in current raaa builds? no cover.jpg or embedded art will show up for me 13.01.12 # using the latest build from rasher's site 13.03.57 Quit GodEater_ (Ping timeout: 265 seconds) 13.05.59 # Zagor: I know :\ I want to test on other targets too, meanwhile I found a few more things about this bug 13.06.30 Quit dfkt|x (Remote host closed the connection) 13.06.30 Join GodEater_ [0] (93722cd0@rockbox/staff/GodEater) 13.06.34 # It seems that all voice from voice file is broken on H1x0, i.e. only talk clips work 13.07.18 # it would be helpful if you put the bug in flyspray, so everyone knows about it 13.07.34 # If some operation would trigger voice output, it either is silently ignored, or it freezes. I even can't start playback within folders with no .talk clip - it freezes immediately 13.07.46 Join lorenzo92 [0] (~chatzilla@95.233.108.83) 13.08.03 # (probably because it tries to fall back to spelling, which uses the voice file) 13.12.01 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 13.14.41 Quit mortalis (Quit: CGI:IRC) 13.22.57 Join dfkt|x [0] (~dfkt@unaffiliated/dfkt) 13.35.38 # Zagor: another option is wait another week (or whatever) and if people still dont think its up to scratch we release from pre-buflib svn 13.38.33 # yes, we have several options. for now I think we should aim at getting 3.10 out, if somewhat late. 13.38.47 # I mean trunk 13.39.04 # late drags out to never though 13.39.34 # yep, it's a risk 13.39.58 # however we've seen pre-buflib also has a number of old bugs 13.46.16 Quit MethoS- (Read error: Connection reset by peer) 13.47.23 Join MethoS- [0] (~clemens@134.102.106.250) 13.52.59 Quit hilbert (Quit: Textual IRC Client: http://www.textualapp.com/) 13.53.27 Quit ReimuHakurei (Quit: Leaving...) 14.01.47 Quit antil33t (Read error: Connection reset by peer) 14.02.10 Join antil33t [0] (~antil33t@203-100-223-143.callplus.net.nz) 14.02.40 Quit dfkt|x (Remote host closed the connection) 14.03.52 *** Saving seen data "./dancer.seen" 14.15.24 Join hilbert [0] (~hilbert@7-111-204-62-static.cable.fcom.ch) 14.28.54 Quit ruboboo (Quit: Leaving) 14.29.27 # [Saint], thanks for your help yesterday. i went a bit crazy on the progress bar / peak meter combination :) - http://forums.rockbox.org/index.php/topic,29103.0.html 14.32.10 # <[Saint]> dfkt: Happy to help. 14.49.01 Quit hilbert (Quit: Computer has gone to sleep.) 14.50.51 Join hilbert [0] (~hilbert@7-111-204-62-static.cable.fcom.ch) 14.59.45 Quit lorenzo92 (Quit: ChatZilla 0.9.87 [Firefox 7.0.1/20111008085652]) 15.01.39 Quit hilbert (Quit: Textual IRC Client: http://www.textualapp.com/) 15.02.01 Join hilbert [0] (~hilbert@7-111-204-62-static.cable.fcom.ch) 15.11.52 Join bigmuffins449 [0] (~d054895b@www.haxx.se) 15.11.56 # i need help!!!!! 15.12.08 # my ipod is dying! 15.12.21 # Its black!!!!! 15.12.29 # and white!!!!! 15.12.50 # SOMEONE HELP!!!!!!!!!!!!!!!!!!!!!!! 15.12.58 # NOOOOOOWWWWWWW!!!!!!!!!!!!!!!!!!!!!!!!!!!! 15.13.22 # ggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggg 15.14.41 # Spamming the channel isn't going to make people want to help you. 15.14.43 Mode "#rockbox +o Torne" by ChanServ (ChanServ@services.) 15.14.50 # It's just going to invite a kick or a ban. People aren't always around. 15.14.52 Kick (#rockbox bigmuffins449 :not if you spam) by Torne!~torne@rockbox/developer/Torne 15.15.43 # thanks. 15.16.32 Mode "#rockbox -o Torne" by Torne (~torne@rockbox/developer/Torne) 15.28.37 Join GermanMushroom [0] (~c@s5146db6a.adsl.wanadoo.nl) 15.32.41 Join mortalis [0] (~4d6c62b0@www.haxx.se) 15.33.26 Join fatboy [0] (~d054895b@www.haxx.se) 15.33.38 # i lovr ou 15.33.45 # i love babies 15.33.50 # how about u 15.33.55 # i heasrt boobies 15.34.00 # i suck rats 15.34.06 # i love pumkins 15.34.11 # and i love bats 15.34.15 # i only two 15.34.21 # but i have great boobs 15.34.25 # i know you want them 15.34.30 # so ill give them to you 15.34.34 # rock box sucks 15.34.38 # iLInux rules 15.34.47 # you guys know nothing 15.34.54 # about YouTube 15.34.59 # Llorean is fat 15.35.06 # and i AM DUMB 15.35.13 # i like them skinny 15.35.18 # and opened up 15.35.23 # kick me 15.35.25 # kicke me 15.35.29 # i dint care 15.35.32 Mode "#rockbox +o Torne" by ChanServ (ChanServ@services.) 15.35.39 Mode "#rockbox +b *!*d054895b@*.haxx.se" by Torne (~torne@rockbox/developer/Torne) 15.35.39 Warn Banlist contains 19 bans! 15.35.39 Kick (#rockbox fatboy :fatboy) by Torne!~torne@rockbox/developer/Torne 15.36.04 Mode "#rockbox -o Torne" by Torne (~torne@rockbox/developer/Torne) 15.36.48 # <[Saint]> We just got freestyle trolled. 0_o 15.37.07 # <[Saint]> Word. 15.39.02 Quit Farthen (Excess Flood) 15.39.07 Join Farthen [0] (~Farthen@2a01:4f8:101:2a4:0:bc28:b2e1:9) 15.56.47 Join WalkGood [0] (~4@unaffiliated/walkgood) 15.58.11 Join ReimuHakurei [0] (~reimu@165.139.179.10) 16.00.08 Quit Zarggg (Quit: Rebooting client...) 16.03.53 *** Saving seen data "./dancer.seen" 16.11.25 Quit ReimuHakurei (Quit: Leaving...) 16.14.34 Join ChickeNES [0] (~ChickeNES@128.135.100.102) 16.17.43 # suddenly ../tools/configure complains about my android sdk magically not being in the path.. well, it is and always was in .bash.rc. does anyone have an idea what could went wrong from one day to the other? 16.24.46 Join n1s [0] (~quassel@rockbox/developer/n1s) 16.26.56 # dfkt: don't like the playlist viewer? 16.26.59 Quit ps-auxw (Ping timeout: 240 seconds) 16.27.22 # dfkt: you need ANDROID_SDK_PATH, not PATH 16.27.35 Join ps-auxw [0] (~arneb@2001:470:c807:0:1532:4e5f:2ad3:4123) 16.28.30 # kugel, i set it up (a long time ago) according to the wiki or docs page, but i can't find it again... could you please tell me the correct line? 16.28.38 # also, what's with the playlist viewer? :) 16.29.18 # dfkt: execute 'env' to see if it's set (or set incorrectly) 16.29.42 # 'export ANDROID_SDK_PATH=/path/to/sdk' would be correct 16.30.28 # <[Saint]> (same for NDK, with SDK>NDK also) 16.30.54 Join dfkt|x [0] (~dfkt@chello062178002170.1.11.univie.teleweb.at) 16.30.55 Quit dfkt|x (Changing host) 16.30.55 Join dfkt|x [0] (~dfkt@unaffiliated/dfkt) 16.32.45 Join ender1 [0] (~ender@foo.eternallybored.org) 16.32.46 Quit ender` (Read error: Connection reset by peer) 16.34.50 # dfkt: no shortcut implemented in your theme :) 16.35.22 # ah... well, i only use file/folder browsing, and i don't even shuffle ;) 16.36.18 # ok, one step further: [WARNING] The compiler you must use (arm-linux-androideabi-gcc) is not in your path! 16.36.42 # no idea how this all disappeared... gah 16.38.11 # <[Saint]> Did you update your SDK? It sounds like a: soemthing went wrong, or b: directories changed. 16.38.39 # no changes... i just updated vmware, which shouldn't affect the guest os, i assume 16.41.23 # <[Saint]> It can't find the NDK, if its spitting that error. 16.41.54 # <[Saint]> (re-)export the PATH to the NDK 16.42.36 # <[Saint]> (assuming the NDK is indeed present) 16.43.06 Quit dfkt|x (Remote host closed the connection) 16.43.59 Join bieber [0] (~quassel@162-78.97-97.tampabay.res.rr.com) 16.44.32 # both sdk and ndk are present 16.45.25 # <[Saint]> well, the toolchain is located in the NDK, so, apparently the OS can't "see" it. 16.46.35 # maybe i need to export the /toolchains folder explicitely? 16.48.21 # <[Saint]> Nope. 16.48.57 # <[Saint]> Just the path to the SDK and NDK, as "ANDROID_*_PATH" 16.49.32 Quit ageis (Remote host closed the connection) 16.49.35 # <[Saint]> (where * is either SDK or NDK, if that wasn't clear) 16.50.34 # woohoo, working again! thank you 16.51.16 # i exported it via commandline - not sure if that sticks. i can just write the same two export lines in .bashrc? 16.51.35 Join The_Seeker [0] (~seeker@5ac8994b.bb.sky.com) 16.52.47 # dfkt: via commandline won't stick - add those two lines to .bashrc 16.53.45 # thanks 16.58.09 Join dfkt|x [0] (~dfkt@chello062178002170.1.11.univie.teleweb.at) 16.58.10 Quit dfkt|x (Changing host) 16.58.10 Join dfkt|x [0] (~dfkt@unaffiliated/dfkt) 17.03.22 Part Zagor 17.05.21 Quit dfkt|x (Quit: Leaving) 17.06.00 Join ageis [0] (~kevin@c-76-127-201-198.hsd1.ma.comcast.net) 17.06.54 # kugel, i could change the long press on tags from menu to playlist, since i guess all android devices have a menu soft-button anyways 17.11.11 # wait - playlist is in context menu :) 17.12.58 Quit The_Seeker (Quit: Stay hungry, stay foolish) 17.20.16 Quit ChickeNES (Quit: Computer has gone to sleep.) 17.26.30 Join ReimuHakurei [0] (~znc@reimuhakurei.net) 17.39.36 Nick [sanyi] is now known as [Sanyi] (~sanyi@unaffiliated/alexanderc) 17.42.16 Join Riviera [0] (~Riviera@gateway/tor-sasl/riviera) 17.44.47 Quit hilbert (Quit: Textual IRC Client: http://www.textualapp.com/) 17.49.45 Quit GodEater_ (Quit: Page closed) 17.50.24 # does anyone have the "list spacing" patch mentioned here? - http://forums.rockbox.org/index.php/topic,27394.0.html 17.51.14 # SVN 17.51.29 # I believe 17.51.47 Nick kugel is now known as kugelp (~kugel@rockbox/developer/kugel) 17.51.54 # hmm, just did a new build, and the list items in android have huge gaps between 17.52.22 # its in svn now, yes 17.53.22 # ah, it's not under theme settings, but in display :p 17.53.28 Nick [Sanyi] is now known as [sanyi] (~sanyi@unaffiliated/alexanderc) 17.55.35 Join funman [0] (~fun@rockbox/developer/funman) 17.58.31 Quit petur (Quit: *plop*) 18.03.38 Join y4n [0] (y4n@unaffiliated/y4ndexx) 18.03.57 *** Saving seen data "./dancer.seen" 18.04.02 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 18.06.09 Join ChickeNES [0] (~ChickeNES@128.135.100.102) 18.08.03 Quit WalkGood () 18.10.39 Quit ChickeNES (Read error: Connection reset by peer) 18.11.00 Join ChickeNES [0] (~ChickeNES@128.135.100.102) 18.15.03 Join Topy44 [0] (~Topy44@f049179229.adsl.alicedsl.de) 18.17.11 Quit funman (Quit: Lost terminal) 18.25.20 Quit ChickeNES (Quit: Computer has gone to sleep.) 18.29.44 Quit mortalis (Quit: CGI:IRC) 18.35.08 Join kadoban [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 18.35.34 Join hilbert [0] (~hilbert@adsl-89-217-34-158.adslplus.ch) 18.37.52 Quit GeekShadow (Ping timeout: 276 seconds) 18.39.28 Join mortalis [0] (~4d6c62b0@www.haxx.se) 18.45.04 Join Jerom [0] (~jerome@79.132.42.48) 18.46.34 Join bertrik [0] (~bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 18.46.35 Quit bertrik (Changing host) 18.46.35 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 18.46.43 Quit GermanMushroom (Read error: Connection reset by peer) 18.47.49 Join domonoky [0] (~Domonoky@rockbox/developer/domonoky) 18.52.24 Quit tchan (Read error: Connection reset by peer) 18.53.14 Join tchan [0] (~tchan@lunar-linux/developer/tchan) 18.53.26 Join Guinness` [0] (Slayer@c-68-55-111-159.hsd1.va.comcast.net) 18.53.35 Quit Guinness (Read error: Connection reset by peer) 19.11.00 Quit MethoS- (Read error: Connection reset by peer) 19.13.13 Quit factor (Read error: Connection reset by peer) 19.21.20 Join Horscht [0] (~Horscht@p5DD57E07.dip.t-dialin.net) 19.21.21 Quit Horscht (Changing host) 19.21.21 Join Horscht [0] (~Horscht@xbmc/user/horscht) 19.30.50 Join factor [0] (~factor@74.197.205.204) 19.31.55 Join ReimuHak_ [0] (~reimu@165.139.179.10) 19.33.36 Quit mystica555 (Quit: Ekkusu Chatto) 19.34.18 Join mystica555 [0] (~Mike@71-211-218-103.hlrn.qwest.net) 19.40.17 Quit saratoga (Ping timeout: 265 seconds) 19.46.21 Join lorenzo92 [0] (~chatzilla@95.232.110.163) 19.47.58 Quit Topy44 (Ping timeout: 240 seconds) 19.52.57 Join Topy44 [0] (~Topy44@f048161046.adsl.alicedsl.de) 19.55.19 Quit mortalis (Quit: CGI:IRC (EOF)) 19.58.55 Quit Thra11 (Read error: Operation timed out) 20.04.01 *** Saving seen data "./dancer.seen" 20.07.17 Quit hilbert (Quit: Computer has gone to sleep.) 20.09.47 Join hilbert [0] (~hilbert@adsl-89-217-34-158.adslplus.ch) 20.11.19 Join Thra11 [0] (~thrall@87.114.24.48) 20.13.28 Nick kugelp is now known as kugel (~kugel@rockbox/developer/kugel) 20.19.18 Quit kadoban (Ping timeout: 260 seconds) 20.21.54 Join Darko [0] (5fb434a9@gateway/web/freenode/ip.95.180.52.169) 20.22.09 # hello 20.22.26 # people are we ready to rockbox my Sansa Clip? 20.22.31 # :) 20.22.50 Join MethoS- [0] (~clemens@134.102.106.250) 20.23.03 # returned home from university.... Ubuntu is burned on CD and now show begins 20.23.20 # hopes are low though :) 20.23.31 # <[Saint]> Possibly ;) Step one is, you'll want a Rockbox patched OF file. 20.23.40 # hi Saint 20.23.50 # my guide to heaven :) 20.24.03 # * [Saint] makes no promises :) 20.24.03 # I will try with original firmware first 20.24.14 # simple things are priority atm 20.24.39 # ah if I only read forums more carefully before I rushed 20.24.41 # <[Saint]> There's a very high likelyhood (since you formatted the FW partition) the OF won't boot...but you can try. 20.24.55 # I deleted partition with Gpart 20.25.06 # <[Saint]> Same effect. ;) 20.25.13 Join kadoban [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 20.25.28 # its now clean, even Win does not see it as mounted wthatsoever 20.25.41 # you mean it doesnt matter 20.26.46 # <[Saint]> What I meant was "you killed the OF partition, so, replacing solely the OF may not have all the sufficient files required for the OF to function" 20.27.06 # <[Saint]> This has been seen on Fuzes before. 20.27.24 # <[Saint]> *How* the FW partition was killed is irrelevant. 20.28.07 # <[Saint]> But, we can try. 20.29.18 Join Darko_ [0] (5fb434a9@gateway/web/freenode/ip.95.180.52.169) 20.29.31 # <[Saint]> Let me know once you a: have a terminal open in Ubuntu, and b: have identified the correct mountpoint of the device. 20.29.40 # ok 20.29.56 # <[Saint]> (hint: using dd is *dangerous*, you need to know the mountpoint of the device) 20.30.07 # <[Saint]> lsusb can help here. 20.30.15 # don't worry 20.30.26 # i am using old machine and I have backup ghost for it 20.30.31 # nothing can be screwed 20.30.33 Quit Darko (Ping timeout: 265 seconds) 20.30.51 # here we go Ubuntu is booting up, fingers crossed 20.33.25 # cool desktop background :) 20.34.56 Join Buschel [0] (~chatzilla@p54B66EDC.dip.t-dialin.net) 20.37.10 # <[Saint]> Applications → Accessories → Terminal or ALT+F2 20.37.18 # <[Saint]> then do "lsusb" 20.37.39 # <[Saint]> you should be able to identify the mountpoint from the lsusb output 20.38.19 # ok its still installing... will notify you 20.38.43 # <[Saint]> Ah...you tricked me saying "desktop" ;) 20.39.27 # well it was that magenta thing 20.39.39 # then vanished and now appeared again 20.40.16 # its just mouse and background and cd is still spinning 20.40.47 # Microsoft really spoiled us :) 20.41.40 # <[Saint]> Running a distro from a LiveCD really can't be compared to "real" Linux in any way. 20.42.04 # <[Saint]> it depends on the speed of your optical drive, and loopback filesystems are really bad for disk IO speeds. 20.42.27 # I know just kidding before "operation", this PC has little memory now I remembered 20.43.33 Nick ender1 is now known as ender` (~ender@foo.eternallybored.org) 20.44.31 Quit kadoban (Ping timeout: 245 seconds) 20.47.04 # if that doesn't work youcan try using puppy linux from usb - it's fast 20.47.06 Join mortalis [0] (~4d6c62b0@www.haxx.se) 20.49.41 # <[Saint]> sillytones: assuming the host machine supports boot from USB 20.49.48 # <[Saint]> (many older machines don't) 20.57.06 # [Saint]: true, but you can use puppy from cd and it's still pretty fast 20.57.32 # or you can use PLoP boot manager to boot from cd first, and then transfer to usb 20.58.00 # * [Saint] slaps himself for sliding conversation offtopic 20.59.06 # finally booted 21.00.32 # [Saint]: not much else to do waiting :P 21.01.32 # <[Saint]> This is an "on-topic" channel, though. You'll remember this fromt he guidelines you read when you joined, right? ;) 21.03.08 Join Urne [0] (Webmaster@0x4dd4477e.adsl.cybercity.dk) 21.03.18 # sorry people, collegue called from university... had a long talk 21.03.32 # this machine has only 256MB RAM, its a bit slow 21.03.44 # hope it wont destroy anything 21.04.04 # this machine doesnt support usb boot as far as i know 21.04.29 # [Saint]: i think it was on topic as it pertains to Darko_'s situation 21.04.35 # now i see ubuntu desktop 21.05.19 # is here a File Manager somewhere? 21.05.34 # I forgot to copy OF to this computer... oops :) 21.07.07 Join [Saint_] [0] (~Saint]@unaffiliated/saint/x-8516940) 21.08.05 Nick [Saint_] is now known as [Saint_Work] (~Saint]@unaffiliated/saint/x-8516940) 21.08.28 # people i decided to boot Ubuntu on new computer and switch internet connection to the old one 21.08.34 # this is way to slow 21.09.12 Quit Darko_ (Quit: Page closed) 21.10.37 Quit [Saint] (Ping timeout: 276 seconds) 21.12.20 Nick [Saint_Work] is now known as [Saint] (~Saint]@unaffiliated/saint/x-8516940) 21.15.58 Quit Buschel (Ping timeout: 248 seconds) 21.17.11 Join Darko [0] (5fb42eb0@gateway/web/freenode/ip.95.180.46.176) 21.17.27 # its me again 21.17.38 # officially running Ubuntu and Firefox 21.17.41 # :) 21.17.50 Join thomasjfox [0] (~thomasjfo@rockbox/developer/thomasjfox) 21.21.23 # Saint is @ work 21.21.38 # does anyone knows how to start Terminal in latest Ubuntu? 21.21.55 # Applications > then something, but I dont se Applications anywhere 21.22.10 # only Ubuntu Software Center 21.22.40 Join AlexP [0] (~alex@rockbox/staff/AlexP) 21.23.11 # Darko: what version of ubuntu 21.23.39 Quit ReimuHak_ (Quit: Leaving...) 21.23.42 Join robin0800 [0] (~robin0800@cpc3-brig8-0-0-cust848.3-3.cable.virginmedia.com) 21.23.51 # Darko: you probably hit the ubuntu dash button, then type terminal in the seach box 21.24.01 # Ubuntu 11.10 32bit 21.24.44 # Press the Windows Key button and type Terminal. I can not remember the keyboard shortcut right now unfortunately 21.24.48 # thanks! it worked 21.24.53 # Terminal up & running 21.24.58 # I think the shortcut is control-t 21.24.59 # Darko, ctrl+alt+t 21.25.12 Join Zarggg [0] (~zarggg@24.229.139.169.res-cmts.sm.ptd.net) 21.25.28 # Dashboard > search did the trick! 21.25.42 # now i will wait for Saint 21.26.02 # he said to wait for him and he will guide me how to restore Sansa Clip v2 21.26.05 # if possible at all 21.26.39 # he mentioned to check something, i forgot now what... 21.26.43 # usb command 21.28.42 # <[Saint]> lsusb 21.29.56 Quit y4n (Quit: HOLY SHIT! WE'RE ALL JUST LIVING ON A GINORMOUS FUCKING SPINNING ROCK FLOATING THROUGH SPACE CIRCLING A BIG FUCKING BALL OF FIRE!!!) 21.31.02 # yes thanks Saint! 21.31.54 # <[Saint]> This assumes the device is connected, and in recovery mode already. 21.32.01 # Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 09da:000a A4 Tech Co., Ltd Port Mouse Bus 001 Device 003: ID 0781:6200 SanDisk Corp. 21.32.46 # I reckon its allright :gree: 21.33.04 # :green: 21.33.10 # <[Saint]> Hum...lsusb doesn't give the mountpoint...well, I fail. 21.33.17 # type 'mount' 21.33.22 # thatwill give mountpoints 21.33.36 # without quotes 21.33.55 # so many text here 21.34.01 # to paste all? 21.34.12 # <[Saint]> Use pastebin. 21.34.18 # look for one like /dev/sdb1 21.34.29 # or with mounpoints in /media/ 21.34.36 # When I had to unbrick my clip+, there was a disk the size of (nearly?) exactly the size of the firmware image, so about 30 MB. I still wonder why. 21.34.45 # bertrik: !!! 21.34.48 # that's where I am now 21.34.55 # how did you recover from there 21.35.10 # <[Saint]> bertrik: yes, I questioned that earlier. 21.35.12 # I dd'ed the firmware image to the USB disk 21.35.21 # the original firmware 21.35.26 # bertrik: to the 30mb partition? 21.35.26 # <[Saint]> sillytones: has the same "problem" 21.36.35 # sillytones, make sure you know exactly which disk is the sansa, unmount any filesystem that is on it, then dd the original firmware to it 21.36.54 # <[Saint]> The recovery partition should be almost 980MB afaik, no idea what this 30MB partition is. 21.37.25 # [Saint], how do you know? 21.37.35 Join GeekShadow [0] (~antoine@151.214.192.77.rev.sfr.net) 21.37.41 # I dd'ed to the 30MB one and that fixed it eventually 21.38.29 # <[Saint]> bertrik: the early ams days and funman discovering it. 21.38.29 # here is text, nothing alike im afraid 21.38.35 # i don't want to risk dd in windows, so i'll reboot to kubuntu in a few minutes 21.38.47 # Also what I did, was to just bridge the 'unbrick' pin for a short time, only during USB plug-in 21.39.02 # [Saint], have you ever unbricked an AMS sansa yourself? 21.39.11 # ugh, i don't want to open my clip+ 21.39.14 # <[Saint]> bertrik: yes. 21.39.30 # <[Saint]> Fuze v1 and v2 21.39.38 # how to use pastebin command on IRC? 21.39.57 # Darko: give us the pastebin url 21.39.57 # <[Saint]> Darko: Google it. Its not an orchestra command. 21.40.06 # <[Saint]> *irc command 21.40.17 # the problem seems to be that no-one really writes down what they do exactly when unbricking, most people panic and do random stuff it seems 21.40.45 # bertrik: i can write what i'm doing i guess 21.40.59 # <[Saint]> If the spelling doesn't give it away, I'm on my phone...this isn't the easiest for me ;) 21.41.10 # you know, I learned so much from a broken Sansa :) 21.41.14 # here is a link 21.41.15 # http://pastebin.com/2ZrA5QMU 21.41.52 # looks like it's not mounted 21.42.08 # so how to do that? 21.42.08 # it should not be mounted when doing dd 21.42.16 # aha ok 21.42.23 # i forget how to find the device name for unmounted things 21.42.31 # besides cheating and opening up gparted 21.42.40 # so now its time to dd' it? 21.42.50 # Darko: you need to know its name 21.43.17 # I think you can do 'sudo fdisk -l' to see all disks 21.44.09 # <[Saint]> sudo fdisk -l should show all disks. 21.44.12 # sudo here it is 21.44.14 # http://pastebin.com/MBidsps1 21.44.15 # <[Saint]> Bah! 21.44.46 # is your clip 1 gb? 21.44.49 # or check with 'dmesg' what happened when you plugged it in, or look in /var/log/syslog 21.45.16 # its sdb 21.45.22 # it's probably /dev/sdb 21.45.23 # yes 21.45.27 # yes 1gb only 21.45.38 # <[Saint]> That's wrong then. 21.45.51 # <[Saint]> You need to expose the recovery partiron. 21.45.53 # why? 21.46.01 # <[Saint]> Not the entire raw device. 21.46.09 # maybe its Gigabits and GibiBits 21.46.19 # bertrik: i'm going to reboot now, will you still be here to walk me through? 21.46.25 # <[Saint]> If you don't expose the recovery partiron, THIS WILL NOT QORK 21.46.33 # <[Saint]> *WORK 21.46.36 # well 21.46.45 # in windows it was reported as 980 Mb 21.46.57 # 979,75 MB 21.47.12 # how to that exposure? 21.47.17 # <[Saint]> You bridged the unbrick pins while connecting to USB? 21.47.18 # I think I only ever saw a 30 MB raw device, not a 1 GB one 21.47.23 # no other method that I know of 21.47.43 # yes, two small ones beside small chip 21.47.52 # i mean not now 21.47.58 # yesterday 21.48.11 # <[Saint]> You need to do this every time you connect USB. 21.48.14 # i think it wont make any difference 21.48.19 # <[Saint]> It does. 21.48.31 # rebooting, brb 21.48.32 # i tried shorting pins several times afterwards in windows 21.48.34 # nothing happend 21.48.40 # ok will try 21.48.43 # again 21.49.22 # <[Saint]> If you can't expose the recovery partition, which we can't help you with, there's nothing we can do. 21.50.01 # will give my best 21.50.34 # I guess the unbrick pins have to be shorted while the player starts up 21.51.15 # so, IMO, turn off the player with a long press on POWER, then short the pins, plug it in USB with pins shorted, release the short after a few seconds 21.51.53 # <[Saint]> bertrik: that's how I did it. 21.53.05 # <[Saint]> Mind you...I got a 980MB partition, not 30MB :-S 21.53.26 # <[Saint]> This doesn't seem an exact science. 21.54.12 # [Saint]: i got 30 without doing anything to pins 21.54.31 # bertrik: alright trying what you said, first looking for firmwares 21.54.37 # <[Saint]> Yeah...I'm still curious about that. 21.56.01 # <[Saint]> bertrik: in case you missed it, sillytones' device decided to expose this 30mb partition all by itself after a hard power down and sitting a week or so. 21.56.27 # well it still is same 21.56.31 # what devices are we talking about really? 21.56.32 # 1027 MB reported 21.57.05 # [Saint]: isn't darko looking at disk size not partition size since nothing is mounted 21.57.22 # i did it 21.57.23 # bertrik: i've got a clip+, Darko has a clip v2 21.57.27 # 4 MB partition reveiled 21.57.29 # ! 21.57.37 # I used metal tool 21.57.47 # <[Saint]> 4 MB? !? 21.57.49 # whats its name in english... grabber of metal 21.57.56 # and shorted nand IC rendomly 21.58.01 # and now i see 4MB 21.58.16 # yeah 21.58.23 # maybe i fried it :) 21.58.49 # very.. interesting! 21.59.04 # <[Saint]> Never seen, nor heard of, that before. A 4mb partition. The OF would not fit there. 21.59.06 # http://pastebin.com/tN2EgjJE 21.59.22 # maybe some stripped down version? :) 21.59.37 # just mp3 support, no room for radio :) 22.00.22 # to try another time? 22.00.39 # I think we've seen the 4MB disk before, but never really understood what it was good for, maybe funman knows 22.00.57 # [Saint]: bertrik: I'm not seeing the clip+ in fdisk 22.01.44 Join [Saint_] [0] (~Saint]@unaffiliated/saint/x-8516940) 22.01.48 # sillytones, I thought you already had the 30 mb disk? 22.02.00 # bertrik: i did in winows 22.02.01 # windows 22.02.04 # now i repeated with old pins everybody nows and its back to 1027MB 22.02.17 # i think we have to accept this is it 22.02.25 # bertrik: i restarted into ubuntu to use dd, now I don't see it 22.02.28 # all we can do now is try dd-ing 22.02.32 Quit mortalis (Quit: CGI:IRC) 22.02.47 # Darko, I think it can't get any worse by trying ... 22.02.50 # <[Saint_]> What...you were shorting RANDOM pins? 22.03.01 # yeah :) 22.03.12 # ESD protection worked 22.03.19 # <[Saint_]> Do you LIKE this device? :) 22.03.22 # [Saint]: could I have rehidden the 30mb partition by leaving it plugged in too long 22.03.26 Quit [Saint] (Ping timeout: 248 seconds) 22.03.33 # easy come easy go 22.03.47 # really i have 5 exams in next 2 months 22.03.55 # really must keep calm :) 22.04.05 *** Saving seen data "./dancer.seen" 22.04.12 Quit robin0800 (Quit: Leaving) 22.04.40 # i 22.05.01 # sillytones, you can try powering it down and then turn it on by plugging USB 22.05.08 # i'm not seeing the disk anymore. i really don't know what to do at this point. 22.05.28 # but i really appreciate your help 22.05.40 # you have to shortpin it 22.05.42 # bertrik: it never powers up when it's plugged in 22.06.51 # open a separate terminal window or terminal tab and type 'tail -f /var/log/syslog' 22.07.20 # in this mode, you cannot tell if it's powered up or not just by looking at the display 22.08.09 # alright, looking at syslog. now should I hold down the power button for 30s and then plug it in? 22.08.14 # bertrik i also did that 22.08.15 # or just plug it in 22.08.21 # how you know if its powered 22.09.08 # you know it's powered if syslog shows a USB device when it's plugged in 22.10.00 # bertrik: got something (pastebinning) 22.10.47 # looks like a recurring pattern 22.11.07 # AFAIK, the most promising method is to 1) unplug the device from USB 2) hold power button for 20sec or so to make sure it's powered off 3) bridge the unbrick pins 4) while bridged, plug it in USB 5) release the unbrick pins after syslog shows that something USB was detected 22.11.50 # if you get a 30 MB disk, try dd-ing the original firmware image to it 22.11.57 # here it is, shorted pins, plugged and then checked 22.11.58 # http://pastebin.com/zxmxcHca 22.12.11 # (not the .zip by the way, but the binary image inside the .zip) 22.13.00 # so i wont to try dd 22.13.06 # Darko, what does sudo fdisk -l say now? 22.13.06 # bertrik: http://paste.ubuntu.com/718220/ 22.13.54 # sudo fdisk -l unchanged 22.13.56 # http://pastebin.com/APf32zwH 22.14.06 # sillytones, hm, there seems to be some other problem, the USB disk is not coming up 22.14.54 # bertrik: i think i got it 22.15.11 # bertrik:after hodling down the power button it looks like it found it 22.15.55 # http://paste.ubuntu.com/718221/ 22.17.03 # great, now it's dd time 22.17.10 # awesome, clippa.bin? 22.17.37 # dd ~/clppa.bin /dev/sdb ? 22.17.43 # I don't dd frequently 22.18.04 # dd is a bit weird with respect to arguments 22.18.21 # you have to do 'sudo dd if=~/clppa.bin of=/dev/sdb' 22.18.32 # alright. here goes 22.19.37 # its going 22.20.21 # i wonder what dd is like if you make it more verbose 22.20.57 # alright 16MB copied. should I try powering it on now? 22.21.21 Quit Zarggg (Ping timeout: 252 seconds) 22.21.26 # yeah, unplug, then turn it off and then on again 22.21.27 # <[Saint_]> Yep. 22.22.17 # nothing :( 22.22.46 # <[Saint_]> What happened exactly? 22.23.17 # [Saint_]: i held the power button down for 30 s, waited 5 seconds, and pressed it, expecting the screen to come on 22.23.25 # I didn't notice any change 22.23.30 Join Stummi [0] (~Stummi@rockbox/developer/Stummi) 22.23.44 # <[Saint_]> Hum... 22.24.11 # whatever that 30mb partition was, I dd'd over it though... 22.24.18 # do you see anything different in /var/log/syslog when plugging it into USB ? 22.24.28 # bertrik: hold on i'll try 22.25.04 # sorry sillytones to hear that :( 22.25.14 # Saint I got another idea 22.25.24 # i unsoldered "-" battery wire 22.25.34 # i will unsolder "+" wire too 22.25.37 # and try reseting 22.25.45 # maybe it is blocking it 22.26.01 # or... i could just try dd-ing now as it is 22.26.21 # what you think? 22.26.26 # unsoldering the "+" wire is not going to help IMO 22.26.39 Join matze` [0] (~pflaume@p54989EA8.dip.t-dialin.net) 22.27.14 # <[Saint_]> Nip...you may as well try DD to the raw device...but, I really doubt success. 22.27.18 # <[Saint_]> *Nup 22.28.03 # bertrik: http://paste.ubuntu.com/718229/ there's a slight difference compaired to the previous one 22.28.07 # a few lines missing 22.28.49 # mostly looks the same though 22.29.04 # i'm taking a look in fdisk 22.29.23 Join [Saint] [0] (~Saint]@unaffiliated/saint/x-8516940) 22.29.36 # well it was worth trying 22.29.38 # ok 22.29.43 # now its dd time 22.29.56 # sillytones, indeed I see no significant change 22.29.57 # if i am not mistaken 22.30.09 # m30pa.bin is on my sd1 drive 22.30.17 # but i want toheck that 22.30.26 # is there a File manager 22.30.34 # bertrik: fdisk sees /dev/sdb as a 32mb disk with no partition table 22.30.38 # toheck = to check 22.31.05 # sillytones, I don't know what to try anymore, maybe you can try again a few more times 22.31.13 # bertrik: ok 22.31.26 # Darko: there is, just click on the dock icon that looks like a folder 22.32.02 # I can't remember if there really was a partition, or that I copied the original firmware image directly to the raw disk 22.32.33 # maybe the 30 mb raw disk needs to be partitioned first 22.32.47 # bertrik: would it be fat 16 or fat 32? 22.32.59 Quit [Saint_] (Ping timeout: 240 seconds) 22.34.08 # I don't know, it didn't have a file system when I did it 22.34.54 # i'll try 16 then 32 22.35.04 # after formatting do I use the same dd command? 22.35.58 Quit [Saint] (Ping timeout: 240 seconds) 22.36.10 # create an ms-dos partition table? 22.36.11 # ok thanks sillytone 22.36.18 # It doesn't need formatting, maybe only partitioning 22.36.38 # now just to put something in my mouth, never do important job on empty stomach :) 22.37.07 # wash your hands after soldering, before eating 22.37.20 # bertrik: hmm,, what technique do you suggest I use? I only know gparted, and it says i need a partition table first 22.37.28 # oh i disconnected soldering iron 22.38.18 # sillytones, sorry I don't know 22.38.39 # i guess it doesn't hurt to try 22.38.40 # I think we (the rockbox dev team) should have a closer look at the internal AMS code 22.38.59 # what does AMS stand for btw? 22.39.10 Quit thomasjfox (Remote host closed the connection) 22.39.16 # Austria mircosystems 22.39.21 # micro* 22.39.22 # austria micro systems, the manufacturer of the main chip 22.39.55 # funman appeared earlier, but said something about needing to charge his laptop, too bad we can't ask the expert 22.40.10 # was just about to ask. I just found there was 184 abbrevations for AMS. 22.40.12 # btw wasn't formatting and or partitioning a nice way to get serious trouble with some older sansa in recovery mode? 22.40.28 # i never remember how these weird recovery modes work 22.40.33 # maybe i shouldn't partition then 22.41.29 Join Naked [0] (~naked@naked.iki.fi) 22.41.50 # i'd say that the best way would be to get ahold of someone who knows how to do this and not try random stuff unless you can't find any such person 22.41.54 # think i should send funman a memo and see if he'd be willing to help me out later 22.44.08 Quit hilbert (Quit: Textual IRC Client: http://www.textualapp.com/) 22.44.23 Join hilbert [0] (~hilbert@adsl-89-217-34-158.adslplus.ch) 22.46.45 # ok fresh as new :) too bad my Sansa is not :( 22.47.25 # ok, my .bin is on a 7.7GB partition (root) 22.47.30 # and my sansa is sdb 22.47.36 # now to dd it 22.48.03 # alright sent a memo to funman 22.48.08 # m30pa.nin 22.48.15 # hope he's able to help 22.48.17 # m30pa.bin 22.48.35 # can someone help me with the right command? 22.50.03 Join [Saint] [0] (~Saint]@unaffiliated/saint/x-8516940) 22.50.21 # Saint welcome back 22.58.40 Join lebellium [0] (~chatzilla@91-65-137-216-dynip.superkabel.de) 23.01.59 Join Staphylo [0] (~Staphylo@mareo.fr) 23.02.19 Quit Darko (Ping timeout: 265 seconds) 23.03.13 Join saratoga [0] (98034408@gateway/web/freenode/ip.152.3.68.8) 23.03.19 Quit lorenzo92 (Quit: ChatZilla 0.9.87 [Firefox 7.0.1/20111008085652]) 23.03.43 # bertrik: according to the wiki, just sending over an OF.bin file won't work, so probably no surprise it didn't work here 23.03.50 # i think you need to send over an image from a working player 23.05.32 Join Darko [0] (5fb42eb0@gateway/web/freenode/ip.95.180.46.176) 23.05.46 # Saint 23.05.57 # can you help me with dd command? 23.08.39 # does using a peak meter in a theme use significantly more processing power/battery? 23.09.00 # it uses some more power, probably depends on the target 23.09.07 # the screen will refresh a lot more IIRC 23.10.20 # i see. too bad that's not easily measured with batter runtime, except one wants to 'burn in' the screen 23.11.11 # hopefully we're smart enough to not calculate it when teh screen is off 23.11.23 # can someone help me with dd command? 23.11.27 Quit froggyman (Quit: Ex-Chat) 23.11.38 Join froggyman_ [0] (~seth@50.105.149.180) 23.11.38 # its getting late at my place :) 23.12.15 Quit Urne () 23.12.26 Quit Stummi (Quit: Bye!) 23.13.07 Quit n1s (Remote host closed the connection) 23.15.27 # regarding screen refresh - i'd like text lines scrolling as smooth as possible, meaning in 1px steps. but then the maximum speed of 15 is kind of slow. would it be easy to tweak the source to provide faster speed? 23.16.30 # its probably just a variable somewhere in the wps code, but i don't know much about that 23.16.34 # kugel could probably tell you 23.16.38 # i will have a look 23.17.46 # the scroll speed settings are in the menu, it's something general, not something WPS or theme specific (code wise) 23.18.45 # What is at 0xc607000 in the AMSv2? 23.20.23 Nick froggyman_ is now known as froggyman (~seth@50.105.149.180) 23.20.32 Quit froggyman (Changing host) 23.20.32 Join froggyman [0] (~seth@unaffiliated/froggyman) 23.22.15 # menu.c has a lot of scrolling references 23.23.24 Join ReimuHak_ [0] (~reimu@208.119.81.194) 23.26.15 # ah, settings_list.c seems to be the right one 23.27.47 Quit ReimuHak_ (Ping timeout: 240 seconds) 23.27.52 # bertrik 23.27.54 # is it hard to get the clipv2 open? 23.28.02 # can you help figuring dd command? 23.28.08 # saratoga no 23.28.16 # clip v2 is very easy to open 23.28.28 # I used razor/scalpel tool 23.28.41 # gently it will open by very little force 23.28.46 # you have youtube video 23.28.58 # then you have 5-6 little screws 23.29.42 # gently remove heatsink and you will see one side of the board with battery attached to it with double-sided mini tape 23.30.16 # i haven't gone dipper then this 23.30.41 # unless you wish to dissasamble oled screen and get to other side 23.31.39 # its getting late here at my place 23.32.15 # i wish to try dd-ing my sansa, so far it is seen as 1014 MB drive, not mounted 23.32.40 # i have m30pa.bin on my 7GB partition and sansa is sbd 23.32.54 # what should be the proper command? 23.37.39 # I have trouble figuring first part of command 23.38.01 # dd if=???/m30pa.bin of=/dev/sdb 23.38.27 # how to find out source drive letters 23.38.36 # i tried sda1 (first partition) 23.38.51 # but it reports no such dir 23.41.46 Join aussa [0] (~andres@190.158.10.28) 23.42.00 # any help anyone? 23.47.44 # ill try tomorow, bye everyone! 23.48.08 Quit Darko (Quit: Page closed) 23.49.02 Quit Thra11 (Read error: Operation timed out) 23.50.27 # * bertrik now has a nearly complete disassembly of the clip+ internal rom 23.50.42 # cool 23.51.47 Quit parafin (Ping timeout: 240 seconds) 23.52.53 # saratoga: I happen to have another working clip+ 23.53.05 # how do I get the image 23.53.11 # i changed the scroll speed from 15 to 25 here - http://pastie.org/2753038 - it shows up, but it's not doing anything. any hints on where else to look? 23.54.07 # sillytones: with the dd command on the wiki page 23.54.21 Join parafin [0] (parafin@paraf.in) 23.54.29 # (in the recovery mode) 23.54.40 # do I need to get the recovery partition first? 23.54.43 # i guess we could also dump it pretty easily from rockbox, but you'd have to write some code to do it 23.55.09 # bertrik: where did you get the ROM from? dumped in recovery mode or?