Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

#rockbox log for 2014-09-09

00:00:25 Quit lebellium (Quit: ChatZilla [Firefox 33.0/20140902214533])
00:05:56 Join [Franklin] [0] (
00:16:16 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS)
00:19:01 Quit bertrik (Remote host closed the connection)
00:21:02ZincAlloy1the bigger the album art, the sooner playback stops..
00:21:56ZincAlloy1on rockbox for android
00:29:54 Quit xorly (Ping timeout: 268 seconds)
00:35:52 Quit ulmutul (Quit: ChatZilla [Firefox 31.0/20140716183446])
00:37:41[Franklin]what happens?
00:39:21ZincAlloy1when album art is loaded and I play a song, it stops after a certain time
00:40:41 Join ungali [0] (
00:40:41 Quit ungali (Changing host)
00:40:41 Join ungali [0] (~ungali@unaffiliated/ungali)
00:43:48ZincAlloy1more album art oddness. a couple of covers that worked at 500x500px don't load at 570x570
00:45:11ZincAlloy1while I had a couple syntax errors when I switched album art sizes I opened these. maybe that broke them? they still work when I try the SD card in my clip zip
00:47:50 Join ploco [0] (dce9b7f9@gateway/web/freenode/ip.
00:48:47ZincAlloy1ah. they, still load at 500x500.
00:50:20[Franklin]ZincAlloy1, this whole thing is weird...
00:51:35plocoZincAlloy1: sounds like out of buffer. check system>rockbox info> buffer while playing music
00:52:16ZincAlloy1buffer: 469kb
00:53:55 Quit ender` (Quit: Be wary of strong drink. It can make you shoot at tax collectors and miss. -- Robert A. Heinlein)
00:55:49plocomight need to build with MEMORYSIZE 24 or 32 (in Makefile) to smooth playback.
00:56:08ploco*for smooth playback
00:56:26ZincAlloy1I see. I've been simply using rasher's builds so far..
01:00:41plocothat build has default MEMORYSIZE=8, a tiny 8mb that even a 720x1280 backdrop would use up almost half of the buffer
01:02:01***Saving seen data "./dancer.seen"
01:02:11ZincAlloy1not suitable for a little eye candy then
01:04:02plocoits very hard to make a theme for 720p and 1080p without increase the memorysize
01:14:58 Quit efyx (Ping timeout: 255 seconds)
01:18:36ZincAlloy1why is the default memory size for these so small then?
01:19:19plocoI guess back then 320x480 was the mainstream.
01:21:00ZincAlloy1for small targets it probably needs to be that small
01:21:32ZincAlloy1never ran into any buffer issues with themes before
01:27:31 Join efyx_ [0] (
01:28:41plococan consider you as the lucky one? I run out of buffer all the time. always try to draw on the backdrop layer.
01:30:01 Join roj [0] (
01:32:07ZincAlloy1[Saint], do you know how to activate absolute point mode in a wps?
01:32:43[Saint]ZincAlloy1: it needs to have at least one touch area.
01:32:59ZincAlloy1aha! so I've been messing that one up
01:33:26[Saint]Without at least one touch area, absolute point won't actually be able to _do_ anything.
01:33:55ZincAlloy1I've been trying to make the progress bar a touch area
01:34:10[Saint]But, unless the theme specifically disables touch areas, or you're using a fucking _ancient_ binary, a progressbar should be creating its own touch areas.
01:34:25[Saint]In fact, any bar should automagically create its own touch area.
01:34:49[Saint]You shouldn't need to do anything to make a progressbar a touch area.
01:34:59[Saint]It should "Just Work".
01:35:04ZincAlloy1oh? interesting
01:35:11ZincAlloy1I still have that 3x3 grid
01:35:16[Saint](unless you pass the notouch tuple in bar params)
01:35:30 Quit ungali (Quit: ungali)
01:35:47ploco[Saint]: will you accept a patch that make all android MEMORYSIZE=32 ?
01:36:31[Saint]ploco: there's really no point in doing so - unless you can demonstrate a reliable fail case.
01:36:44[Saint]Disk access on these targets is essentially free.
01:36:51[Saint]No reason to expand it really.
01:37:46plocoI can provide one of my theme to test on default 8mb build and 32mb build
01:38:21ZincAlloy1Or is there a workaround?
01:38:36[Saint]If your theme is using enough resources to completely deplete an 8MB're quite probably "Doing It Wrong(TM)".
01:38:52[Franklin][Saint], bitmaps can get quite big
01:39:07[Saint]No shit sherlock.
01:39:34[Franklin]8MB, /UNCOMPRESSED/ bitmaps are even bigger
01:40:48ploco << this surely will eat up all 8mb. draw on the whole backdrop in wps
01:41:04 Quit roj (Quit: Leaving)
01:41:24[Franklin]9.2 meg, zipped
01:41:34[Franklin]so yeah, definitely
01:41:48[Saint]You're likely counting fonts in there too, erroneously.
01:42:02*[Franklin] hasn't downloaded yet
01:42:09[Saint]We don't preload all glyphs.
01:42:13[Saint]Only 200 of them.
01:42:15ZincAlloy1the backdrops for my theme are 2.8MB earch. Once the cover art comes it things go horribly, horribly wrong
01:44:04ZincAlloy1I guess I could make it much smaller. but then it would need plenty of files, making a simple theme more complicated than it needs to be
01:44:24[Saint]The absolute worst case scenario for a 1280x1024 bitmap with an alpha channel is 3.9MB, and that still leaves ~4MB for everything else.
01:44:42[Saint]For the present, I don't think there's any need to increase the buffer.
01:44:48[Saint]At least, not to 32MB.
01:44:51[Franklin]but two of them...
01:45:02[Saint]You're an idiot.
01:45:26[Saint]Why would there be two backdrops in the buffer at any one point in time?
01:45:36[Saint]We can only display one.
01:46:01ZincAlloy1a backdrop plus cover art will cause issues
01:46:02[Franklin]no... backdrop, album art... duh!
01:47:00[Franklin]ah sorry, I didn't make it clear
01:47:02[Saint]Uuuugh - who uses bitmap AA?
01:47:09ZincAlloy1I use jpg
01:47:41[Franklin]but Rockbox still stores it uncompressed in RAM, right?
01:47:42ZincAlloy1still have many tiny bmp cover arts left from back in the day when rockbox didn't support jpg cover art :D
01:47:43plocotheres two layer, top and backdrop, it double the needs
01:48:17 Join chrisb [0] (
01:49:46[Saint]Well, if we assume .jpg, and fullscreen album art, and keeping with our 1280x1024 scenario, we're still talking....what, ~500kB?
01:50:18[Saint]If one were to be using fullscreen bitmap AA, then then could be problematic I guess.
01:50:25[Saint]*then that
01:50:41[Franklin][Saint], I'd think that Rockbox would still store it in raw bitmap format internally. Please correct (nicely) me if I'm wrong.
01:50:45[Saint]Either way - I think 32MB is pretty bloody ridiculous.
01:51:15[Saint]16 would be ample.
01:51:43[Franklin]so it doesn't matter what the compressed size is, right?
01:51:44[Saint](unless we're talking fullscreen bitmaps on RaaA hosted on a 4K television or so...)
01:52:51ZincAlloy1A 720x1280 backdrop and 500x500px album art already cause issues for me. my mp3s stop after around 19 seconds
01:53:12plocoI wouldn't be so sure 16mb is enough when we have to build targets 1080x1920 these days
01:53:15ZincAlloy1under 5 seconds with 570x570
01:53:20[Saint]Jeesus Christ...what are these themes doing?
01:53:45[Saint]My 720x1280 theme uses around 4MB
01:54:00ZincAlloy1It was hardly doing anything
01:54:16[Franklin]BTW, I'd say G#950 is Git-quality now
01:54:18*[Saint] boggles
01:54:20fs-bluebotGerrit review #950 at : FS #9583 - periodic table by Franklin Wei
01:54:23[Franklin]Even works on c200
01:54:23ZincAlloy1shall I share my work in progress with you?
01:56:03[Saint]We should /probably/ have ifdefed buffer allocations for hosted targets.
01:56:27[Saint]Allocating 32MB of static buffer to RaaA on, for example, a 240x320 target...
01:57:06[Saint]Some of those devices only have ~512MB or less for the system in total.
01:57:19[Saint]Allocating 32MB would probably cause Android to kill it.
01:57:44[Saint]Or, lots of other background tasks, depending on how the host operates.
01:58:11[Saint]Some will kill the allocating task, others will kill off everything else to try to accomodate the allocating task.
01:58:36plocoRCC has a script in configure , allocate different buffer size based on target resolution. I can try to extract that if needed
02:00:48[Saint]Something along the lines of "worst case scenario fullscreen ARGB bitmap" X 4, or so, would likely be sufficient for all targets.
02:01:33[Saint]That would almost certainly allow for the buffer to be reduced on some targets.
02:04:08ploco line 3394, only applys to android
02:11:58chrisbwhich platforms besides sansa are still in production?
02:12:15[Franklin]latest ipod classic
02:12:20[Franklin]but that's just overstock
02:12:22[Saint]iPod Classic
02:12:34[Saint][Franklin]: no - its still in active production.
02:12:41ZincAlloy1weren't there rumours that the clip zip is out of production?
02:13:07[Franklin]but expect it's end of life soon (as in 5 years)
02:13:21ZincAlloy1"I work for a large online retailer, in our stock system the zip, + & Fuze all have stock re-supply issues & marked as being 'discontinued by manufacturer'."
02:13:47[Saint]Yeah - I'd take that with a grain of salt, personally.
02:14:00[Saint]SanDisk is still selling both new and refurbished units.
02:14:34ZincAlloy1hope it survives a little longer. it's a great player with rockbox. not too sturdy, but very handy
02:14:43[Franklin]but expect the death of the ipod classic soon... :(
02:14:52[Franklin]sad but true
02:15:19[Saint]Ohhhh, stop spreading fud.
02:15:42[Franklin]apple barely even acknowledges it exists
02:16:18copperit's right there, smack in the middle
02:16:37[Franklin]all they ever talk about is "ipod touch", "iphone", "ipad", and "mac"
02:16:41copperhere it is again, in the middle
02:16:43[Saint]Its well established that facts don't prevent [Franklin] from making wild assumptions.
02:16:59 Join cmhobbs [0] (~cmhobbs@fsf/member/cmhobbs)
02:18:49chrisbi didn't think the port for the 160G ipod classic was in good shape though...
02:19:09[Franklin]it is
02:19:23[Franklin]just the install is too hard, and doom doesn't work without a workaround :)
02:19:53 Quit [Franklin] (Quit: Leaving)
02:21:01chrisbah, that's right, the install to ipod classic is the problem...
02:24:50[Saint]The installation method isn't what's holding it back.
02:25:00[Saint]Its the fact that there's no bootloader.
02:25:46[Saint]It can't progress to unstable until it has a Rockbox supplied bootloader, regardless of how functional the port is.
02:26:27[Saint]It'll continue to be "unusable" for as long as installation and boot relies on emCORE and the Freemyipod project.
02:26:56[Saint](because Rockbox doesn't offer any officially supported means of installation, it needs to be marked as unusable)
02:29:33chrisbthanks. is it the same issue for the install for the SonyNWZE3xx
02:32:08ZincAlloy1[Saint], I have no idea what I'm doing wrong. My WPS still has the 3x3 grid.. with a progressbar present it shouldn't, right? I've also tried to define a touch area for the progress bar..
02:33:01[Saint]ZincAlloy1: is it possible that config.cfg is defining gridmode?
02:33:27[Saint]config.cfg will take preference here.
02:33:48[Saint]Even if the theme provides touch areas, its still possible to run it in gridmode.
02:35:08 Quit krabador (Quit: Take the time.)
02:35:51 Quit jhMikeS (Ping timeout: 260 seconds)
02:37:47ZincAlloy1no, config.cfg is alright
02:38:24ZincAlloy1so should it run in absolute mode as soon as there is a progress bar?
02:38:51[Saint]As far as I'm aware, it should, yes.
02:39:04[Saint]As progressbars automagically create their own touch areas.
02:39:24[Saint]Any bar should automagically create its own touch area.
02:39:50[Saint]Unless you're passing the notouch tuple in bar params.
02:43:12ZincAlloy1resetted all settings and reloaded the theme. no luck
02:46:44[Saint]You shouldn't have to, but, what happens if you select absolute point specifically?
02:47:48ZincAlloy1general settings>display>touchscreen settings?
02:47:50[Saint](so refreshing to read skin code that is nicely laid out and wasn't written by a complete retard)
02:47:57ZincAlloy1that only changes modes in the menus
02:48:07ZincAlloy1ha, thanks
02:48:21ZincAlloy1gotta make it easy to read or working with it will be a nightmare.
02:48:54[Saint]ok, sec, lets try something.
02:49:38[Saint]try this theme:
02:49:48[Saint]bah, stoopid pastebuffer.
02:50:02[Saint]There we go.
02:50:26[Saint]Its for 480x800, but, it'll try to position its elements in a semi-sane fashion.
02:50:53[Saint]Its not supposed to have to deal with such a large jump in resolution, but, it should work for our requirements now.
02:51:34ZincAlloy1ugh? what happened there? it's supposed to be a zip file but I ended up with a .dmg?
02:52:17ZincAlloy1348kb instead of 257?
02:52:48ZincAlloy1ah, gotta uncheck the download manager thingy
02:52:53[Saint]It should be exactly 269,566 bytes
02:53:32[Saint]Glargh. Sorry. DIdn't mean to paste that.
02:53:41[Saint]I've got ten bajillion pastebuffers open.
02:54:42ZincAlloy1that works
02:54:58[Saint]Bet it looks bloody crazy.
02:55:20[Saint]Its only supposed to have to deal with 10~20px discrepancies.
02:55:57[Saint]For weird targets where the OS steals some of the resolution for virtual softkeys, or ones with screwy resolution.
02:56:33[Saint]720x1288, etc. 856x1200, <other_crazy_resolution_here>, and so on.
02:56:39ZincAlloy1that theme reminds me… I've got to find a huge iconset
02:56:48[Saint]How huge is huge?
02:56:57[Saint]I can whipe you up one now if you want.
02:57:46[Saint]256x256px? :)
02:57:57[Saint]64? 48?
02:58:13ZincAlloy1quite sure yet. Maybe I'll change the line spacing again… I'll let you know!
02:59:17ZincAlloy1oh my… your theme won't let me select the upper most items in lists
02:59:23ZincAlloy1I can't switch back to my theme :D
02:59:44[Saint]Hmmm...I wonder why that is...
03:00:02 Quit AlexP (Remote host closed the connection)
03:00:26[Saint]ZincAlloy1: (icon sets with viewers, 48x48~256x256px)
03:00:27ZincAlloy1fixed it. I was able to turn on grid :D
03:00:43ZincAlloy1excellent! thanks!
03:00:59[Saint]If you need any other resolution, just give me a yell.
03:01:03ZincAlloy1switching from your theme to mine produces awesome artifacts..
03:01:38[Saint]Yeah, I don't use a backdrop at all, and even though Rockbox should be clearing the backdrop buffer when exiting/entering a screen, it...doesn't seem to.
03:01:43 Join AlexP [0] (~alex@rockbox/staff/AlexP)
03:01:52[Saint]Its reproducible with switching any theme that uses a backdrop.
03:02:02***Saving seen data "./dancer.seen"
03:04:53 Join saratoga [0] (123e1c18@gateway/web/freenode/ip.
03:05:24saratogacan one of the android port developers comment if the changes to how the android target builds here are ok: (see tools/configure)
03:05:58saratogait changes the NDK version for instance
03:08:41[Saint]saratoga: that looks all good to me.
03:09:49saratogaeven the changes to LDOPTS?
03:11:42[Saint]Yes. But it shouldn't be pushed without also changing the error message that resides somewhere around line 660ish
03:12:09[Saint](there's an error the prints the min SDK version if its unmet, which would now be completely misleading)
03:12:31 Quit ZincAlloy1 (Quit: Leaving.)
03:12:40[Saint]*NDK version, sorry.
03:12:41saratogacan you post that to gerrit?
03:12:45saratogai'd like to push this soonish
03:12:48[Saint]I can indeed.
03:13:28 Quit saratoga (Quit: Page closed)
03:14:18plococherry-picked. compiling. gonna test on my phone before say "yes, not affecting android at all"
03:15:25[Saint]I sincerely doubt that anyone that's building Android or any other project that relies on the NDK still has NDK _5_ installed.
03:15:57[Saint]We've been on platform-16 for an age now.
03:17:42[Saint]ploco: your ART patches change the NDK path min to _19_.
03:17:48[Saint]I think we're good here.
03:18:31plocohaha. true. but still want to check anything else got affected.
03:18:32[Saint](sorry - that was too delicious to not point out)
03:20:07[Saint]The same applies to that patch too, by the way.
03:20:30[Saint]If we bump the min NDK version, we also need to bump the min NDK unmet error.
03:21:15plocohmm..the build crash when it try to start Rockbox. this is not a good sign
03:22:05[Saint]As far as I'm aware it should be fine.
03:22:18[Saint]Must be something I'm overlooking.
03:23:34plocowould you might cheery-pick that and test on the phone? I'm going to read the adb log see what cause this crash
03:29:13[Saint]ploco: do you have your ART workaround patch in the same local tree?
03:29:36[Saint]perhaps that's not playing nice.
03:31:16plocono. I check out from a official master before cherry pick the dx90 patch
03:35:18 Join krabador [0] (~krabador_@unaffiliated/krabador)
03:36:33 Quit steffengy (Disconnected by services)
03:36:33 Join steffengy1 [0] (
03:36:54plocoE/AndroidRuntime(10615): java.lang.UnsatisfiedLinkError: dlopen failed: "/data/app-lib/org.rockbox-2/" has unexpected e_type: 2
03:37:18plocogee.. link error
03:38:54plocoso he needs to work on configure line 673~676 to keep android build works
03:39:30[Saint]Oh my God!
03:39:45[Saint]What am I missing in order to save a comment in gerrit?
03:46:18[Saint]aha - man, that's fucking braindead.
03:46:19 Quit dys (Ping timeout: 260 seconds)
03:55:37 Join Ecaz [0] (
03:55:40 Quit Ecaz (Changing host)
03:55:40 Join Ecaz [0] (~z@unaffiliated/ecaz)
03:58:27 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS)
04:15:12 Join Strife89 [0] (
04:21:26 Quit ploco (Quit: Page closed)
04:29:16chrisbok, emcore is going on the ipod classic...
04:41:02 Join Frogging101-chan [0] (~Frogging1@
04:45:32chrisbnow that i have rockbox on the iPod classic, how can i put the device in usb MSC mode to write music files?
04:45:42chrisbis there a manual?
04:48:30Strife89There is a manual, but Rockbox doesn't have a mode selector. It's effectively MSC; it just looks like a USB storage device to a computer.
04:49:01Strife89For the record, a link to the Rockbox manual is on the left of the front page.
04:51:10Strife89Bah, I forgot that the Classic is still considered "unusable". So technically there is no manual for that device - yet.
04:51:46 Quit amiconn (Disconnected by services)
04:51:46 Join amiconn_ [0] (amiconn@rockbox/developer/amiconn)
04:51:46 Quit pixelma (Disconnected by services)
04:51:47 Join pixelma_ [0] (pixelma@rockbox/staff/pixelma)
04:51:49 Nick pixelma_ is now known as pixelma (pixelma@rockbox/staff/pixelma)
04:51:49 Nick amiconn_ is now known as amiconn (amiconn@rockbox/developer/amiconn)
04:52:06chrisbStrife89: ok when i plug in, the disk presents /dev/sdb and after i mount it, i don't see any directories, not even .rockbox/
04:52:55chrisbStrife89: when i press left while plugging in, i dont see any disk at all, just a usb connection good for power
04:54:32Strife89Sorry, chrisb - I don't know enough about the Classic to help beyond general or Rockbox-specific advice.
04:54:44Strife89I only own a couple of Sandisk devices.
04:56:22Strife89But, are you literally mounting "/dev/sdb", or are you mounting sdb1?
04:56:45[Saint]chrisb: if you didn't complete the installation, that would be entirely expected.
04:56:55[Saint]I suspect this is the case.
04:57:42[Saint]If all you're seeing is a black and white main menu structure, you'll have your answer.
04:58:30[Saint]Strife89: Classic is superfloppy under Rockbox
04:58:41Strife89[Saint]: Ahhh.
04:58:43[Saint]So, no partitions.
04:59:02[Saint]It'll happily accept a partition table, however.
05:00:31[Saint]chrisb: to clarify, if you're booting Rockbox, and all you see is a black and white main menu structure (no colour, at all), then the installation isn't complete, and you'll need to finish it by uploading a Rockbox binary.
05:01:16[Saint]emCORE supplies its own (stripped down) Rockbox binary as a fallback.
05:01:27[Saint]Which is almost certainly what you're seeing now.
05:02:03***Saving seen data "./dancer.seen"
05:02:45[Saint]In fact, there's a bright red warning about this very thing on the Freemyipod installation wizard:
05:02:47[Saint]"Even though Rockbox starts, the installation is not complete yet. Continue reading and following the instructions to the end of the page!"
05:03:16chrisbi power up, emcore flashes, then gives me a boot menu with powerdown, rockbox, console and tools.
05:03:36chrisbthen i select rockbox, and i'm in a nice new installation
05:04:01[Saint]That doesn't answer my question.
05:04:26[Saint]If you see colour, you're good. If you don't, you goofed.
05:05:23chrisbi went through the steps to do the full install from RockboxUtility
05:06:08[Saint]If that is the case, then the /.rockbox directory absolutely _will_ be present.
05:06:19[Saint]But I note you still haven't actually answered my question.
05:06:46chrisbmy version is 0ff739c-140908
05:07:17chrisbi see color, a snowy background when i powerup
05:07:33 Quit AlexP (Ping timeout: 272 seconds)
05:07:43*chrisb checks the build id
05:09:12chrisbgit pull gives Head: 0ff739c Fix typo in fuze+ deadzone manual entry
05:09:27[Saint]In _rockbox_.
05:09:28[Saint]Whatever you see in the emCORE main menu is irrelevant.
05:10:21 Quit cmhobbs (Ping timeout: 240 seconds)
05:10:52chrisb[Saint]: ok. what should i look for in rockbox?
05:11:29[Saint]You should just tell me what you see. If its black and white, the installation didn't complete/wasn't completed.
05:12:12[Saint]If you see colour at all (the line selector is a good indicator of this), then the installation was successful, and the /.rockbox directory will definitely be present.
05:12:30[Saint]That is, after all, the issue you mentioned.
05:12:34 Join roj [0] (
05:12:37chrisb[Saint]: there are colors
05:12:47[Saint]Right. Then /.rockbox exists.
05:13:22chrisbi agree, i can't properly mount the disk over USB to see it, though
05:13:27Strife89"Dot directories" are usually just hidden.
05:13:36chrisbi am familiar with ls -al
05:13:51Strife89Ah, sorry.
05:13:54[Saint]chrisb: emCORE main menu -> Tools -> Run Rockbox fallback image
05:14:18chrisbthere is also a partition tool, too
05:14:23[Saint]Use this flow in order to mount the device.
05:14:40[Saint]Nope, there's not.
05:14:41chrisb[Saint]: beautiful, thatmakes sense
05:15:25[Saint]Though, this should "Just Work" if you're on a Linux based system.
05:15:49[Saint]It is highly unusual that you would need to resort to the fallback image on a Linux based system.
05:15:55[Saint]Very much so.
05:16:18rojhi folks... just tried to upgrade my fuze v1 8gb to the latest rockbox build and copy files to it. installed rockbox using rockbox utility. started rockbox successfully. turned off fuze and reconnected it to pc. downloaded fuze v1 latest build and copied rockbox folder over top of installed folder. restarted fuze and rockbox started successfully. went into settings and customized a bit (crossfeed and the like). shut down fuze and reconnected i
05:16:19rojt to pc. tried copying some files to the ##music/music folder. copy FAILED after 6th file. this is similar to what happened with the standard 3.13 buikd. usb file copy support broken on fuze v1. in addition used 3.13 on two other fuze v1s weith identical results.
05:16:51rojthought you ought to know. hitting the sack now after reverting to sansa firmware
05:17:06[Saint]roj: use the OF for USB transfer.
05:17:29rojwell and good but that's not a solution - that's a workaround.
05:17:32[Saint]This has always been the case for those who have issues with SanDisk USB transfer.
05:17:41 Quit TheSeven (Ping timeout: 272 seconds)
05:18:02[Saint]If you want a solution...its open source. Go fix it.
05:18:04rojthe thing is it used to work more reliably on previous versions
05:18:25roji'm no programmer
05:18:44 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven)
05:18:44[Saint]Then I guess you're going to have to accept the workaround, aren't you?
05:19:22rojsadly yes - i always love when folks try to make something better... and it isn't :)
05:19:41[Saint]I would posit you got what you paid for.
05:20:02[Saint]You're always welcome to not use the product, as well.
05:20:07rojin any event, that's my experiment for the evening. the fuze v2 is more stable provided you start the player before oyu plug it in
05:20:15chrisb[Saint]: i can see it now, both on the fallback and on the dev-image thanks for your help
05:21:04[Saint]chrisb: aha - great, so the development binary mounts successfully for you now? That's excellent.
05:21:24[Saint]I was quite puzzled as to why it wouldn't mount.
05:21:35[Saint]Were you on a Windows system I wouldn;t be surprised at all.
05:21:52[Saint]But, on a *nix system, it should absolutely "Just Work".
05:22:38rojsadly again that's the standard reply when something is broken in open source land these days. in any event i;m not here to argue. i made my test, documented it and i'm headed for bed. if someone wants to fix it they can
05:22:51 Quit roj (Quit: Leaving)
05:24:04[Saint]Oh noes! People have better things to do than bend over backwards trying to fix an issue that has eluded the project for _years_ and some guy is mad at me...boohoo.
05:24:21 Quit chrisb (Ping timeout: 240 seconds)
05:35:36 Quit Scr0mple (Ping timeout: 245 seconds)
05:36:25 Join JdGordon [0] (
05:36:25 Quit JdGordon (Changing host)
05:36:25 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon)
05:37:06 Quit TheSeven (Disconnected by services)
05:37:27 Join [7] [0] (~quassel@rockbox/developer/TheSeven)
05:37:51 Quit JdGordon_ (Ping timeout: 240 seconds)
05:38:43 Quit amiconn (*.net *.split)
05:38:43 Quit pixelma (*.net *.split)
05:38:44 Quit mikroflops (*.net *.split)
05:38:44 Quit Cultist (*.net *.split)
05:38:44 Quit markun (*.net *.split)
05:38:51 Join ikeboy [0] (
05:39:25 Join Topy [0] (
05:40:02 Join chrisb [0] (
05:40:20 Join amiconn [0] (quassel@rockbox/developer/amiconn)
05:40:32 Quit krabador (*.net *.split)
05:40:34 Quit WakiMiko (*.net *.split)
05:40:35 Quit Elfish (*.net *.split)
05:40:38 Quit Bluefoxicy (*.net *.split)
05:40:39 Quit Topy44 (*.net *.split)
05:40:40 Nick Topy is now known as Topy44 (
05:40:45 Join Elfish [0] (amba@2001:1608:12:1:13:3:3:7)
05:40:57 Join krabador [0] (~krabador_@unaffiliated/krabador)
05:41:42 Join WakiMiko [0] (~WakiMiko@unaffiliated/wakimiko)
05:42:41 Join pixelma [0] (pixelma@rockbox/staff/pixelma)
05:42:41 Join mikroflops [0] (~yogurt@
05:42:41 Join Cultist [0] (
05:42:41 Join markun [0] (~markun@rockbox/developer/markun)
05:45:50 Join Bluefoxicy [0] (
05:47:49[Saint][7]: wodz: (logs) I fixed up the whitespace errors in g#949 but accidentally fucked up the author
05:47:53fs-bluebotGerrit review #949 at : usb-designware: New USB driver for Synopsys DesignWare USB OTG core. by Hayden Pearce
05:49:00chrisbwow, which players use cores with synopsys USB?
05:49:10chrisband what does OTG mean?
05:50:05[Saint]Ummmm...iPod Classic, iPod Nano 2G, errrr..the iMX based devices, IIRC.
05:50:18[Saint]O(n) T(he) G(o)
05:51:07[Saint](it pays to note that no targets I'm aware of actually support USB-OTG, however. Except for the hosted targets that won't be using this driver)
05:51:41 Quit krabador (Quit: Take the time.)
06:01:54 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon)
06:04:44 Quit JdGordon (Ping timeout: 264 seconds)
06:06:16 Quit chrisb (Ping timeout: 276 seconds)
06:09:38 Join JdGordon [0] (
06:09:54 Quit JdGordon (Changing host)
06:09:54 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon)
06:11:04 Quit JdGordon_ (Ping timeout: 255 seconds)
06:13:20 Quit ikeboy (Quit: Leaving)
06:18:53 Nick DormantBrain is now known as SuperBrainAK (~andy@
06:33:24 Quit Strife89 (Ping timeout: 260 seconds)
06:57:37 Join kugel [0] (~kugel@rockbox/developer/kugel)
06:57:47kugel[Saint]: you can restore the original author
07:00:00kugelgit commit −−author="A X (" −−amend −−reuse-message=HEAD
07:02:04***Saving seen data "./dancer.seen"
07:13:33 Join pamaury [0] (~quassel@rockbox/developer/pamaury)
07:17:14[Saint]kugel: I tried that, but it gave me a warning about the author email not matching my account.
07:17:58 Join ygrek [0] (~user@
07:20:04[Saint]remote: ERROR: In commit 8fec86aeebeb990420b7b85f0bb905eedbc50aef
07:20:04[Saint]remote: ERROR: author email address
07:20:04[Saint]remote: ERROR: does not match your user account.
07:20:04DBUGEnqueued KICK [Saint]
07:20:04[Saint]remote: ERROR:
07:20:04[Saint]remote: ERROR: The following addresses are currently registered:
07:20:06[Saint]remote: ERROR:
07:20:08[Saint]remote: ERROR:
07:20:10[Saint]remote: ERROR: To register an email address, please visit:
07:20:12[Saint]remote: ERROR:
07:20:20[Saint]gah...shit, that's not a pastebin link now is it?
07:20:27[Saint]Anyway - yeah, that.
07:20:37kugeloh, that's gerrit disallowing it then
07:21:04kugelalso, TheSeven was the original author i think?
07:21:06jhMikeSpoor markun should now expect alot of spam :)
07:21:07[Saint]There _is_ a way to do it, and, I've done it before.
07:21:14[Saint]But, apparently this time I failed.
07:22:53kugeljhMikeS: why that?
07:23:05kugelthat's not markun's mail :)
07:23:34jhMikeSoops, wrong guy, whatever though :)
07:26:16 Nick SuperBrainAK is now known as DormantBrain (~andy@
07:26:46 Join mortalis [0] (~kvirc@
07:39:30 Join Scromple [0] (~Simon@
07:43:40 Join wodz [0] (
07:43:53 Quit amiconn (Remote host closed the connection)
07:43:53 Quit pixelma (Remote host closed the connection)
07:44:05wodz[Saint]: does it mean that g#949 works for you?
07:44:09fs-bluebotGerrit review #949 at : usb-designware: New USB driver for Synopsys DesignWare USB OTG core. by Hayden Pearce
07:44:32[Saint]It does.
07:44:39wodzholly shit
07:44:52wodzNn all variants?
07:45:03[Saint]Just tested Classic.
07:45:10wodzit locked up hard on [7]'s classic
07:45:12[Saint]Can't find an N2G until I get home.
07:45:31[Saint]Oh. Weird.
07:46:01[Saint]There's some i.MX targets that use this Synonsis core, is there not?
07:46:02 Join pixelma [0] (pixelma@rockbox/staff/pixelma)
07:46:04 Join amiconn [0] (amiconn@rockbox/developer/amiconn)
07:46:15wodzn2g is probably more complicated. It at least needs g#843
07:46:17[Saint]...not that I have any of them.
07:46:18fs-bluebotGerrit review #843 at : Fix cache coherency on ARM940T (and other ARMv4T cores). by Michael Sparmann
07:46:33[Saint]Aha. Right, yes. Thanks for reminding me.
07:47:00wodz[Saint]: imx233 uses arc
07:47:31[Saint]Ah. Hmmm. There's more than just the Classic and N2G using this USB core, no?
07:47:39[Saint]Or am I imagining this...
07:49:40 Quit ygrek (Ping timeout: 272 seconds)
07:49:46 Quit pamaury (Ping timeout: 245 seconds)
08:01:10jhMikeS[Saint]: So, what's so weird about the iPods? Sounds interesting.
08:02:42 Join dys [0] (~user@2a01:1e8:e100:8296:21a:4dff:fe4e:273a)
08:02:55[Saint]jhMikeS: in what way?
08:03:34jhMikeS[Saint]: I remember seeing a comment earlier about it tripping up even "experienced developers", I think you made it
08:04:18[Saint]Just a few of its oddities.
08:04:29[Saint]Superfloppy formatted by default from emCORE.
08:04:33[Saint]emCORE in general.
08:05:02[Saint]Really weird installation process entirely different to any other iPod.
08:09:49wodz[Saint]: BTW I still see white space errors in the desgnware driver (although in comments which will eventually be ripped off)
08:11:30[Saint]Oh? Ah. I may need to adjust my de-whitespace-ifyer
08:11:49[Saint]Looking at the code its skipping comments.
08:12:07[Saint]Not entirely nonsensical.
08:12:16[Saint]But, you're quite right.
08:25:04 Join ender` [0] (
08:36:56 Join pamaury [0] (~quassel@rockbox/developer/pamaury)
08:40:51 Join cholero [0] (d4f3026a@gateway/web/freenode/ip.
08:41:30 Part cholero
08:56:26 Quit wodz (Quit: Leaving)
08:56:39 Join petur [0] (5bb7304d@rockbox/developer/petur)
09:02:08***Saving seen data "./dancer.seen"
09:05:27 Quit ender` (Quit: It's is not, it isn't ain't, and it's it's, not its, if you mean it is. If you don't, it's its. Then too, it's hers. It isn't her's. It isn't our's either. It's ours, and likewise yours and theirs.)
09:10:26 Join ygrek [0] (~user@
09:20:38 Join rela [0] (~x@pdpc/supporter/active/rela)
09:48:52 Quit kugel (Ping timeout: 255 seconds)
09:51:00 Join goom [0] (
09:51:33 Quit goom (Client Quit)
09:54:01 Quit amiconn (Read error: Connection reset by peer)
09:54:35 Join amiconn [0] (quassel@rockbox/developer/amiconn)
09:54:52 Join wodz [0] (
09:54:57 Quit pamaury (Ping timeout: 252 seconds)
09:56:56wodz[Saint]: From comment on gerrit I assumed you tested designware driver on n2g but you said here you didn't. I am a bit confused, what is the actual status?
09:56:58 Join pamaury [0] (~quassel@rockbox/developer/pamaury)
10:09:53 Quit rela (Quit: Leaving)
10:13:21[Saint]wodz: yeah - I got mixed up there. I confused myself. I'm /indirectly/ using the new driver on N2G, a binary provided by [7].
10:13:45[Saint]I'm home now, though, so I can make ammends.
10:16:44fs-bluebotBuild Server message: New build round started. Revision 9a18ca4, 253 builds, 29 clients.
10:17:03[Saint]I built a binary for it as soon as you posted the updated task, but I must've put the the wrong one on there.
10:17:14[Saint](or possibly never got around to updating the binary at all)
10:25:19fs-bluebotBuild Server message: Build round completed after 515 seconds.
10:28:53wodz[7]: ping
10:40:42 Quit petur (Ping timeout: 246 seconds)
10:43:16 Join einhirn [0] (
10:48:26 Join petur [0] (~petur@rockbox/developer/petur)
10:53:52 Join petur2 [0] (~petur@
10:54:03 Nick petur2 is now known as p3tur (~petur@
10:54:13 Quit p3tur (Changing host)
10:54:13 Join p3tur [0] (~petur@rockbox/developer/petur)
10:54:43 Quit petur (Quit: qicr for android: faster and better)
10:54:49 Nick p3tur is now known as petur (~petur@rockbox/developer/petur)
10:56:28 Join LinusN [0] (
10:57:16 Quit ygrek (Ping timeout: 255 seconds)
10:59:45 Join foolsh [0] (
11:02:03 Quit petur (Read error: Connection reset by peer)
11:02:11***Saving seen data "./dancer.seen"
11:03:16 Join petur [0] (~petur@rockbox/developer/petur)
11:05:27 Quit petur (Read error: Connection reset by peer)
11:06:23 Join petur [0] (~petur@rockbox/developer/petur)
11:08:31 Quit petur (Read error: Connection reset by peer)
11:09:27 Join petur [0] (~petur@rockbox/developer/petur)
11:11:36 Quit petur (Read error: Connection reset by peer)
11:12:48 Join petur [0] (~petur@rockbox/developer/petur)
11:18:38 Quit petur (Read error: Connection reset by peer)
11:20:00 Join petur [0] (5bb7304d@rockbox/developer/petur)
11:39:37 Join edhelas [0] (
11:42:30 Quit krnlyng (Quit: huiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii)
11:50:55 Join bcobco [0] (~bcobco@
11:51:18 Join ygrek [0] (~user@
12:05:20 Join krnlyng [0] (~liar@
12:08:22 Join ZincAlloy [0] (
12:32:41 Quit scorche (Disconnected by services)
12:32:44 Join scorche` [0] (~scorche@rockbox/administrator/scorche)
12:48:55 Quit ygrek (Ping timeout: 245 seconds)
12:58:34 Join ygrek [0] (~user@
13:00:16wodz[7]: Could you suggest reasonable timeouts in busyloops?
13:02:13***Saving seen data "./dancer.seen"
13:19:30 Quit ygrek (Ping timeout: 268 seconds)
13:19:30 Join scorche [0] (~scorche@rockbox/administrator/scorche)
13:22:10 Quit scorche` (Ping timeout: 272 seconds)
13:22:51 Quit jhMikeS (Ping timeout: 240 seconds)
13:27:33 Join ygrek [0] (~user@
13:31:51 Quit ygrek (Ping timeout: 240 seconds)
13:32:50 Quit foolsh (Quit: foolsh)
13:34:08 Join foolsh [0] (
13:39:54 Join ygrek [0] (~user@
13:44:40 Quit ygrek (Ping timeout: 255 seconds)
13:49:03ZincAlloy[Saint], I've introduced another touch area and now it works. The progress bar, too.
13:54:19 Quit einhirn (Ping timeout: 252 seconds)
13:54:23 Quit pamaury (Ping timeout: 252 seconds)
13:55:39 Join pamaury [0] (~quassel@rockbox/developer/pamaury)
14:01:22 Quit mikroflops (*.net *.split)
14:01:22 Quit Cultist (*.net *.split)
14:01:22 Quit markun (*.net *.split)
14:02:42 Quit edhelas (Ping timeout: 276 seconds)
14:05:53 Join mikroflops [0] (~yogurt@
14:05:53 Join Cultist [0] (
14:05:53 Join markun [0] (~markun@rockbox/developer/markun)
14:19:50 Join cmhobbs [0] (~cmhobbs@fsf/member/cmhobbs)
14:26:09 Quit K1773R (Excess Flood)
14:28:05 Quit fs-bluebot (Quit: connection lost?)
14:28:13 Join K1773R [0] (~K1773R@unaffiliated/k1773r)
14:30:24 Quit cmhobbs (Ping timeout: 268 seconds)
14:32:42 Join fs-bluebot [0] (
14:56:22 Quit wodz (Quit: Leaving)
15:02:14***Saving seen data "./dancer.seen"
15:04:51 Join amayer [0] (
15:07:33 Join ygrek [0] (~user@
16:30:18 Join pmarty [0] (5be2c216@gateway/web/freenode/ip.
16:42:45 Quit eternnoir (Remote host closed the connection)
16:57:08 Join chrisb [0] (
17:02:15***Saving seen data "./dancer.seen"
17:06:17 Join eternnoir [0] (
17:06:21 Quit chrisb (Ping timeout: 240 seconds)
17:13:38 Join Riviera [0] (~Riviera@2a03:b0c0:1:d0::10:b001)
17:18:52 Quit ygrek (Ping timeout: 255 seconds)
17:19:30 Join chrisb [0] (
17:19:52CtcpIgnored 1 channel CTCP requests in 0 seconds at the last flood
17:19:52*chrisb enjoying ipod classic + emcore + rockbox
17:21:02 Quit pmarty (Quit: Page closed)
17:24:38copperwelcome to the club
17:27:44 Quit petur (Ping timeout: 246 seconds)
17:29:28chrisbcopper: don't get me wrong, i love my sansa e200 and fuze, and hate the overprice of the iPod
17:31:32chrisband i just got dock support working for my fuze,which was a long time goal
17:32:26chrisbmy gtkpod has been broken for months, so i could no longer put files on the iPod with apple firmware
17:34:32copperit's not overpriced if there's no competition :P
17:39:02chrisbcopper: but it was overpriced when there was lots of competition
17:41:21*ZincAlloy is enjoying Rockbox on his phone
17:46:23chrisbZincAlloy: how do you do that? emulator?
17:47:09*chrisb goes to check other emcore targets...
17:47:11ZincAlloyThere are rockbox builds for android">
17:48:25ZincAlloylarge album art won't work. other than that it's really nice once you've made a good theme..
17:50:59 Join ikeboy [0] (
17:54:39chrisbZincAlloy: thanks
17:55:24foolshchrisb: Are your sansa dock output changes in gerrit?
17:56:35chrisbfoolsh: no, just in my local branch. i started with tenfoot's patch from 2011
17:57:17foolshcool I'll check that, and you should upload them if you care to
18:00:24foolshbtw g#922 has really nice DSP effects but needs tested on more targets if anyone has time, give it a shot
18:00:27fs-bluebotGerrit review #922 at : three new DSPs (WIP) by Chiwen Chang
18:00:58foolshI've had it running on fuze+ two days no trouble
18:01:14chrisbfoolsh: can create a patch from git and send it to you for evaluation? also, i only checked it on one platform, fuzev2
18:02:46foolshI can if you wish, but it's not necessary, Id rather you learn how it not hard, if you can of course if not I'd be honored to
18:03:52foolshGerrits not permanent you can make changes and reach more people
18:10:14foolshDon't worry if you mess up, you only get yelled at a little bit by the devs ;-)
18:17:44chrisbthanks for your encouragement
18:19:32foolshYour welcome, ask for help anytime as well
18:32:41 Join ygrek [0] (~user@
18:36:34chrisbrockbox is so good, i hope something like this may happen to keep the hardware available:
18:42:16 Quit pamaury (Ping timeout: 246 seconds)
18:43:32 Join bertrik [0] (~quassel@rockbox/developer/bertrik)
18:46:25 Quit ygrek (Ping timeout: 245 seconds)
19:02:18***Saving seen data "./dancer.seen"
19:08:55 Quit efyx_ (Ping timeout: 245 seconds)
19:16:23 Quit Riviera (Ping timeout: 260 seconds)
19:16:31 Join fml [0] (
19:17:07fmlHello. The new deadzone option should also be described in the section about the settings (don't know what appendix that is)
19:17:12 Join lebellium [0] (
19:17:26fmlI mean in the manual
19:19:37foolshThanks again fml, I'll get to tit then ;-)
19:19:41chrisbdeadzone for clip or fuze+?
19:19:43foolshto it*
19:19:51 Join y4n [0] (~y4n@unaffiliated/y4ndexx)
19:21:11fmlsorry for the nagging but if we (you) do it we should do it properly
19:21:52foolshAbsolutely, and really thank you, it's not nagging :-)
19:22:45 Quit Scromple (Ping timeout: 245 seconds)
19:23:45 Join efyx_ [0] (
19:26:18 Join edhelas [0] (~edhelas@
19:27:45 Join pamaury [0] (~quassel@rockbox/developer/pamaury)
19:46:30 Quit mortalis (Ping timeout: 245 seconds)
19:47:58foolshfml: Do you mean in the "The Main Menu > Settings" section? I see the system settings are missing from it completely, I have my work cut out for me now ;-)
19:48:50foolshor rather General > System Settings
19:50:07ZincAlloy[Saint], check it out, it came out pretty slick - other than the album art issue
19:51:24 Join Rower [0] (
19:54:42 Join bluebrother^ [0] (~dom@rockbox/developer/bluebrother)
19:54:49 Quit bluebrother (Disconnected by services)
19:55:23foolshfml: I'm slightly confused now, the other sections of "The Main Menu > Settings" do not reference their subsections either. Is it some where else you had in mind I should be looking? Sorry
19:58:28 Quit fs-bluebot (Ping timeout: 268 seconds)
20:00:40 Quit edhelas (Ping timeout: 252 seconds)
20:03:08 Join fs-bluebot [0] (
20:06:48foolshfml: There appears to more inconsistencies in the manual than just that, so I'm going to post a forum post and try to draw more discussion to this, thank you again
20:23:32 Join steffengy [0] (
20:26:21 Quit steffengy1 (Ping timeout: 240 seconds)
20:30:16 Part Frogging101-chan ("I'm up, over, and gone.")
20:31:50 Quit Rower (Quit: Hmmm...)
20:38:05 Quit steffengy (Disconnected by services)
20:38:07 Join steffengy1 [0] (
20:47:02 Join ygrek [0] (~user@
21:02:22***Saving seen data "./dancer.seen"
21:11:23 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS)
21:14:52foolshWill rockbox be joining the internet slow down day tomorrow?
21:15:54 Join ender` [0] (
21:21:07fmlfoolsh: I meant the appendic "Config file options"
21:21:20 Quit chrisb (Ping timeout: 240 seconds)
21:21:58foolshAh thank you, I missed that one
21:28:46foolshAnd the touchpad sensitivity setting is missing too it looks like. So I'll get *to it* then :-D
21:33:50 Join steffengy [0] (
21:34:57 Join chrisb [0] (
21:35:35 Join oskie_ [0] (
21:36:11oskie_hello. I have a Sansa Clip Zip but I wonder if there's newer players suitable for Rockbox?
21:36:49oskie_looking that the wiki BuyersGuide it seems the Sandisk Sansa are the only ones in production
21:37:07 Quit steffengy1 (Ping timeout: 264 seconds)
21:39:04 Quit fml (Quit: ChatZilla [Firefox 31.0/20140717132905])
21:39:20 Quit ygrek (Ping timeout: 245 seconds)
21:40:13ikeboyI'd personally recommend the fuze+. It's older than the clip zip (I think) but has a big screen and good control imo.
21:40:30ikeboySome people have complained about the touchpad though
21:42:07 Quit ikeboy (Quit: Leaving)
21:48:55copper19:36:51 UTC <oskie_> looking that the wiki BuyersGuide it seems the Sandisk Sansa are the only ones in production
21:48:58copperdidn't you ask this before?
21:49:17copperFuze+, iPod Classic
21:53:45 Quit bcobco (Remote host closed the connection)
21:54:11 Join bcobco [0] (~bcobco@
22:05:03 Quit chrisb (Ping timeout: 255 seconds)
22:07:58oskie_copper: before? must've been months ago
22:09:35copper2014/09/09 00:12:00 UTC <chrisb> which platforms besides sansa are still in production?
22:09:43coppersomeone else then
22:10:29copperanyway, looks like the iPod Classic is finally out of production
22:10:42copper redirects to and the Classic isn't listed
22:11:22gevaertsSo now it *finally* can start becoming a classic
22:11:54copperand the Rockbox port still is "unusable" :(
22:12:12gevaertsSo are most Apple devices when they leave the factory :)
22:12:30coppersassy mouth
22:16:56copper → Apple kills iPod Classic in total silence | TUAW: Apple news, reviews and how-tos since 2004 | Original URL:
22:22:07copperthey should have updated it with a super large SSD
22:22:31copperin Champagne Gold :D
22:29:18 Join Scromple [0] (~Simon@
22:52:45 Quit pamaury (Ping timeout: 255 seconds)
23:02:23***Saving seen data "./dancer.seen"
23:03:55 Join ooh [0] (
23:05:19 Join roj [0] (
23:11:30 Quit roj (Quit: Leaving)
23:12:35 Quit amayer (Quit: Leaving)
23:15:14 Quit lebellium (Quit: ChatZilla [Firefox 33.0/20140902214533])
23:29:54ZincAlloythe button assignment in android could use some work. a long press on the back button doesn't do anything. It could be used as a shortcut to the wps.
23:30:55ZincAlloyand a long press on the menu button will bring up the context menu. Not all that useful. a long touch on any list item will bring up the context menu as well.
23:38:18 Join xorly [0] (
23:39:53copperuseful for identifying iPods, maybe?
23:40:43copper"If you're of a certain age, then, you can get ready to tell your grandchildren about the days when people carried 160GB of music in their pocket instead of streaming it all from the cloud. Oh, and get ready to explain what a spinning hard drive is, too."
23:46:33 Join [Franklin] [0] (
23:46:52copper"Now that Apple is able to offer iPhones in 128GB solid-state storage options, the iPod classic would have felt particularly redundant as a product."
23:47:09[Franklin]who said that?
23:47:16copperexcept the Classic was selling for 250-300 euros, and the 128 GB iPhone will sell for a thousand euros
23:47:28[Franklin]another reason for them to cut it
23:47:33[Franklin]make them more money!
23:47:46[Franklin]any chance that rockbox could run on the iWatch?
23:48:18*copper pukes
23:48:35*[Franklin] just noticed apple's new website
23:49:34[Franklin]"Single computer architecture on a single chip"
23:49:55[Franklin]So RAM, CPU, and Flash storage on one chip...
23:50:50[Franklin]Inductive charging...
23:51:11copperthe charging thing is brilliant
23:51:14[Franklin]If some way could be found to run arbitrary code, then it will definitely have the power to run rockbox
23:51:37copperit doesn't work as a standalone thing
23:51:43copperand there's no headphone plug
23:51:47*the-kyle wouldn't want flash storage on the same chip with the CPU.
23:51:55[Franklin]the-kyle, that's what apple did
23:52:13copperthe-kyle: because of noise?
23:52:46[Franklin]ahh true
23:52:53[Franklin]but it seems to be a big "chip"
23:53:12*[Franklin] can't find any tech specs on the thing
23:53:53[Franklin]any *real* tech specs, not apple's marketing propaganda
23:53:53the-kyleYes because of noise, but also because flash is short-lived.
23:54:29the-kyleThe CPU part of the chip would definitely outlast the flash.
23:55:08*[Franklin] considers a forum post on the topic
23:55:26the-kyleAnd of course, since it's an Apple product, it most likely won't have a way to replace or supplement the flash with external storage.
23:55:32[Franklin]maybe there's a piezo in there :)
23:55:35[Franklin]and LOL
23:57:09[Franklin]the "S1" seems to be pretty big
23:57:17[Franklin]so I doubt it's one piece of silicon
23:58:21[Franklin]was anyone expecting a new ipod classic at the keynote today?
23:58:40*[Franklin] was kinda hoping for one

Previous day | Next day