00:39:07 | | Quit benedikt93 (Quit: Bye ;)) |
00:48:26 | | Quit ZincAlloy (Quit: Leaving.) |
00:54:32 | *** | Saving seen data "./dancer.seen" |
01:00 |
01:00:58 | | Quit alucryd (Quit: alucryd out) |
01:01:17 | | Quit bertrik (Quit: leaving) |
01:05:08 | | Join alucryd [0] (~alucryd@archlinux/trusteduser/alucryd) |
01:07:45 | | Quit SolarAquarion (Ping timeout: 264 seconds) |
01:22:28 | | Join KiwiCAM_ [0] (~quassel@121-99-191-123.bng1.nct.orcon.net.nz) |
01:22:44 | | Quit amiconn (Disconnected by services) |
01:22:45 | | Join amiconn_ [0] (quassel@rockbox/developer/amiconn) |
01:22:49 | | Nick amiconn_ is now known as amiconn (quassel@rockbox/developer/amiconn) |
01:23:23 | | Join bluebrother [0] (~dom@rockbox/developer/bluebrother) |
01:23:29 | | Join soap_ [0] (~soap@cpe-174-102-103-175.woh.res.rr.com) |
01:23:30 | | Quit soap_ (Changing host) |
01:23:30 | | Join soap_ [0] (~soap@rockbox/staff/soap) |
01:24:30 | | Join Naked_ [0] (~naked@naked.iki.fi) |
01:24:31 | | Join shuffleb1t [0] (~ec2-user@ec2-54-198-117-181.compute-1.amazonaws.com) |
01:24:45 | | Join uwe_mobile__ [0] (~uwe@static.88-198-8-117.clients.your-server.de) |
01:24:46 | | Join Marex_ [0] (~Marex@195.140.253.167) |
01:25:40 | | Quit pixelma (Disconnected by services) |
01:25:40 | | Join pixelma_ [0] (quassel@rockbox/staff/pixelma) |
01:25:43 | | Nick pixelma_ is now known as pixelma (quassel@rockbox/staff/pixelma) |
01:28:37 | | Join AKBlindy_ [0] (~jticket@jt-lx.info) |
01:29:27 | | Quit bluebrother^ (*.net *.split) |
01:29:27 | | Quit Naked (*.net *.split) |
01:29:27 | | Quit Pessimist (*.net *.split) |
01:29:27 | | Quit AKBlindy (*.net *.split) |
01:29:28 | | Quit kiwicam (*.net *.split) |
01:29:28 | | Quit Marex (*.net *.split) |
01:29:28 | | Quit shufflebot (*.net *.split) |
01:29:28 | | Quit soap (*.net *.split) |
01:29:28 | | Quit uwe_mobile (*.net *.split) |
01:29:28 | | Quit ps-auxw (*.net *.split) |
01:31:28 | | Join ps-auxw [0] (~arneb@2001:470:c807:0:1532:4e5f:2ad3:4123) |
01:36:21 | | Quit Scall (Ping timeout: 240 seconds) |
01:44:49 | | Join Scall [0] (~chat@unaffiliated/scall) |
02:00 |
02:07:20 | | Join ender` [0] (krneki@2a01:260:4094:1:42:42:42:42) |
02:08:51 | | Quit ender| (Read error: Connection reset by peer) |
02:54:36 | *** | Saving seen data "./dancer.seen" |
03:00 |
03:00:00 | | Quit AlexP (Remote host closed the connection) |
03:14:19 | | Quit bp0 (Quit: Leaving) |
03:15:20 | | Quit ender` (Read error: Connection reset by peer) |
03:15:23 | | Join ender^ [0] (krneki@2a01:260:4094:1:42:42:42:42) |
03:16:17 | | Join TD-Linux [0] (~Thomas@about/essy/indecisive/TD-Linux) |
03:16:31 | TD-Linux | hello, I have a sansa clip+ that had rockbox firmware on it previously |
03:16:46 | TD-Linux | it appears as a block device but I can't seem to read anything off it |
03:17:06 | TD-Linux | the sansa firmware tells me that there is 90MB of space left and can't get past refreshing media |
03:17:31 | | Quit WakiMiko (Ping timeout: 256 seconds) |
03:17:57 | | Join WakiMiko [0] (~WakiMiko@unaffiliated/wakimiko) |
03:21:58 | TD-Linux | anything to do before I try unbricking? |
03:24:27 | | Join Strife89 [0] (~Strife89@adsl-98-80-212-179.mcn.bellsouth.net) |
03:53:16 | | Join ygrek [0] (~user@108.59.6.97) |
03:55:52 | | Quit lebellium (Quit: ChatZilla 0.9.90.1 [Firefox 31.0/20140716183446]) |
03:57:12 | | Quit Strife89 (Remote host closed the connection) |
04:00 |
04:00:17 | | Quit jhMikeS (Ping timeout: 245 seconds) |
04:10:07 | | Quit amiconn (Ping timeout: 260 seconds) |
04:10:35 | | Quit pixelma (Ping timeout: 260 seconds) |
04:13:01 | | Join amiconn [0] (amiconn@rockbox/developer/amiconn) |
04:13:01 | | Join pixelma [0] (pixelma@rockbox/staff/pixelma) |
04:52:44 | | Join cmhobbs [0] (~cmhobbs@fsf/member/cmhobbs) |
04:54:39 | *** | Saving seen data "./dancer.seen" |
05:00 |
05:01:36 | | Join test [0] (79363625@gateway/web/freenode/session) |
05:09:33 | | Quit test (Quit: Page closed) |
05:12:05 | | Join Raptors [0] (~Raptors@216-58-33-198.cpe.distributel.net) |
05:12:24 | Raptors | preglow, I think you're the fuze+ dev right? |
05:12:36 | Raptors | I'm kind of stuck |
05:12:56 | Raptors | My battery is too low to boot so I can't get it to boot to the OS |
05:13:10 | Raptors | when I plug it in, it goes to usb mode which doesn't seem to charge |
05:32:30 | | Quit steffengy (Disconnected by services) |
05:32:32 | | Join steffengy1 [0] (~quassel@p5088FB75.dip0.t-ipconnect.de) |
05:49:45 | [Saint] | Raptors: AFAIK, it _should_ charge over USB/bootloader USB |
05:50:11 | [Saint] | If it is deep discharged, it may take a while to register a charge. |
05:50:18 | Raptors | [Saint], it doesn't. I figured it out through google though. You have to press down while it's powering up |
05:50:27 | Raptors | and it goes to original firmware charging |
05:50:45 | Raptors | so plug it in and press volume down really fast |
05:50:53 | Raptors | it wont work if you try to charge it through comp |
05:51:00 | Raptors | you need a power plug |
05:51:11 | [Saint] | Hmmm...it can definitely charge over USB in Rockbox, I thought it could via bootloader USB too...hmmm. |
05:52:17 | [Saint] | Blindly reading the config tells me this should work. |
05:52:23 | [Saint] | Odd. |
06:00 |
06:26:00 | | Join advcomp2019 [0] (~advcomp20@unaffiliated/advcomp2019) |
06:27:33 | | Quit advcomp2019_ (Ping timeout: 240 seconds) |
06:54:43 | *** | Saving seen data "./dancer.seen" |
07:00 |
07:19:46 | | Quit Provel (Ping timeout: 264 seconds) |
07:38:09 | | Join pamaury [0] (~quassel@rockbox/developer/pamaury) |
07:52:46 | | Quit ygrek (Ping timeout: 264 seconds) |
08:00 |
08:01:08 | | Join AlexP [0] (~alex@rockbox/staff/AlexP) |
08:31:38 | | Join bp0 [0] (~bp@216.254.236.232) |
08:31:38 | | Quit bp0 (Changing host) |
08:31:38 | | Join bp0 [0] (~bp@unaffiliated/bp0) |
08:36:53 | | Quit pamaury (Ping timeout: 255 seconds) |
08:40:46 | | Join jhMikeS [0] (~jethead71@c-68-43-2-35.hsd1.mi.comcast.net) |
08:40:46 | | Quit jhMikeS (Changing host) |
08:40:46 | | Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) |
08:54:45 | *** | Saving seen data "./dancer.seen" |
08:55:33 | | Quit Raptors (Quit: Leaving) |
09:00 |
09:22:09 | | Join Provel [0] (Provel@75-132-0-140.dhcp.stls.mo.charter.com) |
09:22:09 | | Join Pessimist [0] (Elite8188@gateway/shell/elitebnc/x-kkedrllhzwofvkhb) |
09:22:30 | | Quit Pessimist (Changing host) |
09:22:30 | | Join Pessimist [0] (Elite8188@unaffiliated/pessimist) |
09:29:39 | | Quit Pessimist (Changing host) |
09:29:40 | | Join Pessimist [0] (Elite8188@gateway/shell/elitebnc/x-kkedrllhzwofvkhb) |
09:40:25 | copper | [Saint]: yes it can |
09:40:29 | copper | bootloader v2 though |
09:41:07 | copper | or whatever is the last version |
09:44:06 | copper | it even displays it's charging status |
09:44:17 | copper | but I definitely had to update the bootloader |
09:44:28 | copper | its* |
09:57:44 | | Join ender` [0] (krneki@foo.eternallybored.org) |
10:00 |
10:54:46 | *** | Saving seen data "./dancer.seen" |
11:00 |
11:25:58 | | Join ygrek [0] (~user@108.59.6.97) |
11:26:08 | | Join piknockyou [0] (4d149e31@gateway/web/freenode/ip.77.20.158.49) |
11:28:35 | piknockyou | hi there, does rockbox delete the default operating system of the clip+? |
11:42:41 | copper | no |
11:42:48 | copper | and you can dual boot, check the manual |
11:46:27 | | Join bertrik [0] (~bertrik@dhcp-089-098-143-039.chello.nl) |
11:46:27 | | Quit bertrik (Changing host) |
11:46:27 | | Join bertrik [0] (~bertrik@rockbox/developer/bertrik) |
12:00 |
12:00:37 | piknockyou | I formatted my 64 gb microsdxc for clip+ to FAT32, Sandisk OS recognizes it which is good, but I read it limits of around 8,000 songs, does anyone know if this really means songs or any data? le't say cover art count in, do you think so? |
12:01:02 | piknockyou | *counts |
12:01:59 | piknockyou | and do they mean just the database? if yes, I wouldn't care since I am only using folder navigation |
12:08:03 | | Quit bertrik (Remote host closed the connection) |
12:26:55 | piknockyou | Hi there, what does the limit really of the sandisk OS stand for? Is it like songs in the library? any single piece of data in the library? I was wondering, because I wouldn't care about library limits since I am using folder navigation. Would the clip+ also limt the "titles" in the folder navigation? Why should it? Thanks. |
12:31:36 | copper | piknockyou: why are you asking in #rockbox about a firmware that Rockbox is designed to replace? |
12:31:47 | copper | ask on the Sansa forums |
12:32:04 | copper | SanDisk* |
12:34:30 | piknockyou | cause I can't get rockbox installed. may I ask you to help me? It says no mountpoint given. |
12:34:46 | piknockyou | But it is mounted clearly as a device. |
12:35:28 | piknockyou | And when I press auto-detect, Rockbox fails, doesn't work anymore and needs to be closed. |
12:36:42 | piknockyou | If I open rockbox, it says "Your configuration is invalid. This is most likely due to a change of device path. ..." |
12:49:11 | | Join pamaury [0] (~quassel@rockbox/developer/pamaury) |
12:54:48 | *** | Saving seen data "./dancer.seen" |
12:54:53 | piknockyou | i try manually, where do I get this stuff "Create a folder called “rbinstall” on your desktop, and then extract the OF, the bootloader and mkamsboot into it." |
12:54:56 | piknockyou | ? |
13:00 |
13:05:59 | copper | piknockyou: click on the Change button |
13:06:15 | copper | there, you can manually set boht the device, and the mount point |
13:06:31 | copper | there, click on "Refresh" if need be |
13:06:49 | copper | all the while, making sure your Clip+ is actually mounted where you think it's mounted |
13:07:14 | copper | also, note that the Clip+ presents TWO drives: one for the Clip+ itself, and another one for the sd card reader |
13:09:05 | piknockyou | stay with me, please. doesn't work. |
13:09:24 | piknockyou | I chose the device but there is no mount point, the line is empty white. |
13:09:32 | piknockyou | i can not chose a mount point at all. |
13:09:49 | piknockyou | no change by refreshing. |
13:10:22 | piknockyou | no mountpoint given. |
13:10:32 | copper | can you upload a screenshot please? http://imgur.com/ |
13:10:57 | piknockyou | dou you want teamviewer? |
13:12:10 | copper | what? |
13:12:47 | piknockyou | http://www.teamviewer.com/en/ |
13:12:54 | piknockyou | controlling my computer |
13:13:08 | copper | no |
13:13:25 | piknockyou | okay, what screenshot do you exactly need? |
13:13:44 | [Saint] | copper: aha! thankyou. |
13:13:50 | copper | guys |
13:13:59 | copper | I can't change the mountpoint in the RB utility either |
13:14:09 | [Saint] | I didn't think to look at the past history of changes, I just looked at the code and saw that it /should/ work. |
13:14:11 | copper | it's stuck on '/media/clip' no matter what I do |
13:14:22 | [Saint] | I don't actually have the hardware laying around. |
13:15:07 | piknockyou | http://imgur.com/mn1wUrT |
13:15:10 | copper | "Select your device in the filesystem" is a dropdown menu containing only that one entry, and it cannot be edited |
13:15:52 | [Saint] | Is the device in MSC or MTP mode? |
13:16:03 | [Saint] | IIUC, autodetect failing here implies the former. |
13:16:47 | copper | piknockyou: click on the dropdown meny |
13:16:48 | copper | menu |
13:17:20 | piknockyou | what is the dropdown menu? |
13:17:43 | copper | the bar to the left of the refresh button |
13:17:45 | piknockyou | opkay, and then? |
13:18:00 | copper | what does it display? |
13:18:07 | piknockyou | it is empty |
13:18:13 | copper | ok |
13:18:18 | piknockyou | but you can see on the screenshot there is a device mounted |
13:18:27 | copper | boot the original firmware and set the Clip+ to MSC |
13:18:35 | piknockyou | [13:09] <piknockyou> I chose the device but there is no mount point, the line is empty white. |
13:19:32 | piknockyou | how to do this? where to do this? |
13:19:44 | piknockyou | you mean taking the device and starting it up? |
13:20:42 | piknockyou | and thenI am at it |
13:21:00 | piknockyou | got it |
13:21:11 | piknockyou | "working on it" |
13:21:35 | * | [Saint] notes that the manual covers this |
13:21:40 | [Saint] | http://download.rockbox.org/daily/manual/rockbox-sansaclipplus.pdf |
13:21:50 | [Saint] | "2.1. Before Starting" |
13:24:20 | copper | (my problem was that nothing was mounted on my system) |
13:24:21 | piknockyou | you are right, sorry about that, I have overseen that, but I am actually using the manual. :-/ |
13:24:35 | piknockyou | what is the most detailed theme in terms of ? |
13:24:44 | piknockyou | information |
13:25:20 | | Join ygrek_ [0] (~user@108.59.6.97) |
13:25:25 | copper | see for yourself |
13:25:31 | copper | on themes.rockbox.org |
13:26:32 | | Quit ygrek (Remote host closed the connection) |
13:28:34 | piknockyou | thank you so much so far |
13:39:51 | | Quit piknockyou (Quit: Page closed) |
13:47:23 | | Join ZincAlloy [0] (~Adium@pD9EEA446.dip0.t-ipconnect.de) |
13:56:13 | | Join kugel [0] (~kugel@rockbox/developer/kugel) |
14:00 |
14:49:18 | | Join benedikt93 [0] (~benedikt9@frbg-4d028526.pool.mediaWays.net) |
14:49:26 | | Quit benedikt93 (Changing host) |
14:49:26 | | Join benedikt93 [0] (~benedikt9@unaffiliated/benedikt93) |
14:54:50 | *** | Saving seen data "./dancer.seen" |
15:00 |
15:01:38 | | Join stripwax [0] (~Miranda@rockbox/developer/stripwax) |
15:02:19 | | Quit kugel (Ping timeout: 250 seconds) |
15:03:26 | | Quit stripwax (Client Quit) |
15:25:51 | | Join f[x] [0] (~user@108.59.6.97) |
15:28:53 | | Quit ygrek_ (Ping timeout: 260 seconds) |
15:43:42 | | Join b0hoon [0] (~quassel@public-gprs473765.centertel.pl) |
15:47:01 | fs-bluebot | Build Server message: New build round started. Revision 6bbfb35, 253 builds, 28 clients. |
15:53:09 | fs-bluebot | Build Server message: Build round completed after 369 seconds. |
15:54:06 | b0hoon | pamaury: any news about the Sansa View? |
15:54:56 | | Join kugel [0] (~kugel@rockbox/developer/kugel) |
15:57:25 | | Join RiD [0] (~RiD@2.83.0.55) |
16:00 |
16:12:07 | pamaury | b0hoon: not really, I have been very very busy recently, but I'll throw some work at it today and tomorrow |
16:13:25 | b0hoon | pamaury: that's great. |
16:15:43 | | Part b0hoon ("GTG... Bye.") |
16:21:43 | | Quit kugel (Ping timeout: 250 seconds) |
16:30:49 | | Join y4n [0] (~y4n@unaffiliated/y4ndexx) |
16:53:32 | | Quit cmhobbs (Ping timeout: 256 seconds) |
16:54:53 | *** | Saving seen data "./dancer.seen" |
17:00 |
17:18:38 | | Join bertrik [0] (~bertrik@dhcp-089-098-143-039.chello.nl) |
17:18:38 | | Quit bertrik (Changing host) |
17:18:38 | | Join bertrik [0] (~bertrik@rockbox/developer/bertrik) |
17:30:12 | | Join ygrek_ [0] (~user@108.59.6.97) |
17:32:49 | | Quit f[x] (Ping timeout: 255 seconds) |
17:46:01 | | Join japc [0] (~japc@bl16-10-41.dsl.telepac.pt) |
17:48:21 | | Quit japc (Client Quit) |
17:51:08 | | Join HeadWhacker [0] (84934c34@gateway/web/freenode/ip.132.147.76.52) |
17:52:22 | HeadWhacker | Hi, I have Rockbox completely running on iBasso DX90. Using the same sources from DX50 |
17:52:52 | HeadWhacker | Now there is a small problem |
17:54:38 | HeadWhacker | When quickly skipping tracks by pressing the fwd or prev button, there is a soft cracling noise at at the beginning of the track that last between 2 to 5 seconds |
17:55:48 | HeadWhacker | it's quite random and if I hear the noise on a track I just rewind to the beginning and the noise is not there |
17:56:21 | HeadWhacker | anyone has any idea where this noise is coming from? |
17:58:15 | | Quit bertrik (Remote host closed the connection) |
18:00 |
18:09:58 | | Join notben [0] (~ben@99-122-84-33.lightspeed.spfdmo.sbcglobal.net) |
18:09:58 | | Part notben |
18:24:01 | | Quit RiD (Quit: A good plan today is better than a perfect plan tomorrow.) |
18:32:21 | | Quit pamaury (Ping timeout: 240 seconds) |
18:35:17 | | Join RiD [0] (~RiD@bl22-0-55.dsl.telepac.pt) |
18:51:14 | | Join sakax [0] (~sakax@unaffiliated/sakax) |
18:54:54 | *** | Saving seen data "./dancer.seen" |
19:00 |
19:08:55 | | Quit ygrek_ (Ping timeout: 260 seconds) |
19:17:35 | | Join ulmutul [0] (~chatzilla@wprt-5d835ae0.pool.mediaWays.net) |
19:30:16 | | Join zoktar [0] (~zoktar@unaffiliated/zoktar) |
19:31:27 | | Join ygrek [0] (~user@108.59.6.97) |
19:35:02 | | Quit bluebrother (Disconnected by services) |
19:35:07 | | Join bluebrother [0] (~dom@rockbox/developer/bluebrother) |
19:36:33 | ulmutul | b0hoon: ping |
19:37:23 | | Quit fs-bluebot (Ping timeout: 240 seconds) |
19:40:37 | | Join fs-bluebot [0] (~fs-bluebo@g231123020.adsl.alicedsl.de) |
19:47:18 | | Join cmhobbs [0] (~cmhobbs@fsf/member/cmhobbs) |
19:49:44 | | Join benedikt93_ [0] (~benedikt9@frbg-5f731148.pool.mediaWays.net) |
19:53:21 | | Quit benedikt93 (Ping timeout: 264 seconds) |
20:00 |
20:06:29 | | Join b0hoon [0] (~quassel@public-gprs444182.centertel.pl) |
20:06:51 | b0hoon | ulmutul: pong |
20:08:06 | ulmutul | I've tested the latest battery monitoring patch. The results are here: http://imgur.com/7SBjsKO,Vt0Tera#1 |
20:09:09 | b0hoon | ulmutul: so? |
20:09:17 | ulmutul | Strange to say that the voltages of the two devices are quiet different. |
20:12:08 | b0hoon | ulmutul: ah, ok - two pictures |
20:12:59 | | Quit RiD (Quit: A good plan today is better than a perfect plan tomorrow.) |
20:13:04 | ulmutul | The old ones are here: http://www.bilder-upload.eu/show.php?file=1730d0-1405177222.jpg and http://www.bilder-upload.eu/show.php?file=5ab675-1405177258.jpg |
20:13:15 | b0hoon | ulmutul: maybe just different baterriesin different stages of wear |
20:14:26 | | Join saratoga [0] (123e1c18@gateway/web/freenode/ip.18.62.28.24) |
20:14:48 | b0hoon | ulmutul: i don't have an idea, OF has one way of calculate the level |
20:15:05 | saratoga | kugel: (for the logs) this might be interesting to you http://forums.rockbox.org/index.php?topic=48058.msg228993;topicseen#msg228993 |
20:15:46 | ulmutul | And the voltage code hasn't changed since the last test. So maybe different loading state or temperature or something. |
20:17:28 | b0hoon | ulmutul: aaa, one thing i didn't change the values for charging so the chart maybe be like this |
20:18:09 | ulmutul | All battery benches are made discharging. |
20:18:54 | b0hoon | ulmutul: right, i don't know then |
20:19:24 | ulmutul | Charging values are problematic anyway, because full voltage is reached very early. |
20:19:58 | b0hoon | yes, it's for all Portal Player based players |
20:20:23 | b0hoon | well, i would like to commit this patch anyway |
20:20:48 | b0hoon | and work on The mystery of RTC for YH820 |
20:21:50 | ulmutul | Yes, definitively. |
20:22:39 | ulmutul | I think I'll go in for the keymaps. |
20:22:45 | b0hoon | ulmutul: can you make some pictures of the mainboard for v2.0? as close as possible? |
20:23:30 | ulmutul | Yes, already made some :) I thought about uploading them to the wiki. |
20:23:41 | b0hoon | ulmutul: i see that for version 1.7 CLKOE is connected somwhere |
20:23:50 | b0hoon | of RTC |
20:24:02 | b0hoon | and on the schematic is not |
20:24:25 | b0hoon | great |
20:25:35 | | Quit cmhobbs (Ping timeout: 250 seconds) |
20:30:43 | ulmutul | b0hoon: here's the interesting part: http://www.bilder-upload.eu/show.php?file=4d737a-1406399368.jpg |
20:33:15 | b0hoon | connected too, looks the same :S |
20:34:10 | b0hoon | it will be hard to find the bug... |
20:35:47 | | Join kugel [0] (~kugel@rockbox/developer/kugel) |
20:39:02 | b0hoon | ulmutul: anyway, thanks if you could add the pictures on the Wiki it would be great. |
20:41:59 | | Quit benedikt93_ (Quit: Bye ;)) |
20:42:28 | | Join benedikt93 [0] (~benedikt9@unaffiliated/benedikt93) |
20:48:57 | | Quit HeadWhacker (Ping timeout: 246 seconds) |
20:54:58 | *** | Saving seen data "./dancer.seen" |
20:57:45 | | Join cmhobbs [0] (~cmhobbs@fsf/member/cmhobbs) |
21:00 |
21:00:02 | | Quit krnlyng (Ping timeout: 240 seconds) |
21:04:50 | | Quit benedikt93 (Quit: Bye ;)) |
21:17:32 | | Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) |
21:20:38 | TheSeven | how does the USB/charging detection code work these days? |
21:20:42 | TheSeven | IIRC the samsung ipods are using some deprecated way of handling that |
21:20:49 | TheSeven | and as I need to change some of that code anyway, I'd rather do it right from the beginning |
21:23:16 | | Join Rower [0] (~husvagn@h176n2-aeg-a11.ias.bredband.telia.com) |
21:24:36 | | Join krnlyng [0] (~liar@83.175.90.24) |
21:26:06 | | Quit ygrek (Ping timeout: 245 seconds) |
21:26:14 | gevaerts | TheSeven: IIRC basically you want to define USB_DETECT_BY_REQUEST |
21:26:47 | gevaerts | And I have *no* idea why it was problematic on the new ipods |
21:27:02 | TheSeven | what does that change? |
21:27:08 | gevaerts | http://gerrit.rockbox.org/r/#/c/317/ |
21:27:56 | gevaerts | It sets "host present" when an actual USB transfer has been seen (i.e. the first get_descriptor usually) instead of when an insert is detected |
21:28:43 | TheSeven | so this is something that shouldn't require any further changes... |
21:29:10 | gevaerts | With any luck :) |
21:29:10 | | Quit sakax (Quit: Leaving) |
21:29:35 | TheSeven | what exactly are the consequences of "host present" being set? IIUC that should only affect charging, mass storage, etc., but not the lowlevel USB driver? |
21:29:51 | TheSeven | are we doing anything fancy such as re-enumerating with a different set of descriptor based on what we have seen? |
21:30:08 | gevaerts | It will change the exact time when usb_core_enable_driver() is called, which might expose bugs I guess |
21:30:33 | TheSeven | what does that function do? |
21:30:47 | TheSeven | does it call any usb_drv_*? |
21:31:02 | * | gevaerts checks |
21:32:04 | TheSeven | I've found this weird thing in the s3c6400x driver: |
21:32:04 | TheSeven | void usb_attach(void) { usb_enable(true); // s5l only ? /* Nothing to do */ } |
21:32:17 | TheSeven | and I have no idea why it's there, usb_enable doesn't seem to do anything useful |
21:32:29 | TheSeven | maybe that might be related somehow? |
21:32:44 | gevaerts | Looking at the code, I don't think usb_drv_* will see anything different |
21:32:48 | * | gevaerts checks the usb_enable thing |
21:32:53 | TheSeven | anyway, I'll revisit that with the new USB driver |
21:33:39 | TheSeven | is it a known issue that rapid reconnections of the USB port will crash with various kinds of errors? (OOM panics, hangs, ...)? |
21:36:42 | gevaerts | Hmmm |
21:37:03 | gevaerts | I don't remember specific issues, but I wouldn't be surprised |
21:40:44 | TheSeven | we have a slightly tricky situation on the classic with charging state detection... |
21:40:44 | TheSeven | as far as I know, we have these GPIOs: |
21:40:44 | TheSeven | b4: IN not charging (no external power or fully charged) |
21:40:44 | DBUG | Enqueued KICK TheSeven |
21:40:44 | TheSeven | b5: IN discharging (can go high during disk activity even with external power present) |
21:40:44 | TheSeven | b6: OUT enable fast charging (500mA instead of 100mA) |
21:40:45 | *** | Alert Mode level 1 |
21:40:45 | TheSeven | b7: OUT disable charging altogether |
21:40:48 | TheSeven | c3: USB Vbus present |
21:40:50 | TheSeven | when I say "external power" above, I mean "at least one of USB or firewire" |
21:40:52 | TheSeven | there are also separate GPIOs for "USB power present" and "firewire power present" in the PMU, but we can't access those safely from IRQ mode (e.g. tick tasks) due to the I2C mutex |
21:41:32 | TheSeven | our rather cautious handling of GPIO b6 currently breaks firewire charging |
21:42:47 | TheSeven | do you think it's adequate to assert POWER_INPUT_MAIN_CHARGER for both USB and firewire (USB is kind of the main charging method), or should I use the dedicated USB power state for that? |
21:43:18 | TheSeven | and how should situations where external power is present but the battery is discharging regardless be handled? |
21:43:40 | TheSeven | to make matters even worse, I think charging and discharging can both be true at the same time |
21:44:07 | TheSeven | (charging is more of a "wants to charge, and has external power, but current limiting might not actually allow charging") |
21:44:07 | Ctcp | Ignored 1 channel CTCP requests in 0 seconds at the last flood |
21:44:07 | * | gevaerts isn't sure |
21:44:22 | gevaerts | I've never done actual charging code... |
21:46:18 | TheSeven | who did rework charging a while ago? was that Torne? |
21:46:25 | gevaerts | Yes |
21:46:32 | gevaerts | I think |
21:50:46 | *** | Alert Mode OFF |
22:00 |
22:09:41 | | Quit kugel (Ping timeout: 255 seconds) |
22:11:39 | | Join krabador [0] (~krabador@unaffiliated/krabador) |
22:19:26 | | Join Gallomimia [0] (~gallomimi@S0106c8fb267813e0.ca.shawcable.net) |
22:19:39 | ulmutul | Hello, can somebody give me write permission for the wiki? My username is "SebastianLeonhardt" |
22:22:40 | | Join franklin [0] (47474769@gateway/web/freenode/ip.71.71.71.105) |
22:25:18 | franklin | Does adding password protection to DAPs go against open-source priniciples? Is there a need/demand for it? |
22:26:58 | gevaerts | franklin: why would that go against open source principles? |
22:27:47 | franklin | gevaerts: I have suggested a lock-out feature here: http://forums.rockbox.org/index.php/topic,48411.0.html |
22:27:52 | gevaerts | ulmutul: if I didn't do anything wrong, you should have write access now |
22:28:02 | ulmutul | Thank you! |
22:29:50 | gevaerts | franklin: for the record, my laptop runs entirely on open source software, and it asks me for a password before I can do anything with it :) |
22:29:59 | franklin | gevaerts: is a lock-out feature wrong? I imagine many people would forget the password and brick their players without saving the unlock key to their computers first. |
22:30:26 | franklin | gevaerts: is an iOS-like lock-out feature wrong, I mean |
22:30:35 | gevaerts | The user would control this |
22:31:09 | gevaerts | So I don't see any philosophical issue with this |
22:31:35 | franklin | gevaerts: I just feel bad writing this code. I'm just not sure why. Maybe it smells to much like Apple |
22:31:59 | gevaerts | Apple didn't invent security |
22:32:27 | franklin | gevaerts: do you understand their passcode lock feature? |
22:32:27 | gevaerts | Still, this sort of thing means disabling dualboot and recovery modes |
22:32:36 | franklin | gevaerts: that's why |
22:32:53 | * | gevaerts is confused |
22:32:57 | gevaerts | that's why what? |
22:33:09 | franklin | gevaerts: this sort of thing means disabling dualboot and recovery modes |
22:33:59 | gevaerts | The possible problem with disabling all of that is that you basically have no means of recovery left if things go wrong |
22:34:10 | gevaerts | And things *do* go wrong |
22:34:28 | franklin | gevaerts: and it would be very hard without bricking a player or two :D |
22:34:58 | gevaerts | Not really. You don't disable dualboot until you get everything else working |
22:35:37 | gevaerts | But then of course I'd just grab your device and take the hard drive out to see what's on there :) |
22:35:57 | franklin | gevaerts: but for targets with separate bootloaders (ipod6g), it could be bypassed easily by wiping the HDD from emCORE |
22:36:13 | gevaerts | When would you wipe? |
22:36:25 | franklin | To reset the password lock |
22:36:58 | gevaerts | Yes, but I'd just take the disk out and use some usb/ata adapter to read it. I wouldn't reset the lock |
22:38:08 | TheSeven | franklin: what are you trying to achieve in the first place? |
22:38:13 | TheSeven | data security? theft prevention? |
22:38:22 | franklin | TheSeven: theft prevention |
22:38:36 | TheSeven | so you need to make it unrecoverable |
22:38:45 | gevaerts | Well, not really |
22:38:58 | franklin | gevaerts: the reason iOS passcode is so secure is that you *CAN'T* reset it, no matter what you do. In other words, it's a walled garden, completely against open-source principles |
22:39:02 | gevaerts | By the time the thief sees he has an unusable device, you've lost the device anyway |
22:39:10 | ulmutul | gevaerts: Hm, I can't edit and I don't find myself in the WikiUsersGroup ... |
22:39:27 | gevaerts | franklin: security is *not* against open source principles *at all* |
22:39:38 | franklin | gevaerts: but making walled gardens is |
22:40:00 | gevaerts | franklin: yes, how is a walled garden involved in this discussion? |
22:40:34 | franklin | gevaerts: to achieve security, it must be impossible or very hard to access the filesystem while waiting for a password |
22:40:41 | gevaerts | Yes |
22:41:01 | franklin | gevaerts: just smells bad to me |
22:41:32 | gevaerts | franklin: please tell me your email account details |
22:41:42 | gevaerts | If you don't, that must mean you're against open source |
22:41:49 | gevaerts | Or isn't that what you're saying? |
22:42:18 | gevaerts | ulmutul: that's weird. As far as I can see, you're on there |
22:42:45 | ulmutul | Hm, ok, I'll try again. |
22:43:28 | ulmutul | OK, it works now, thanks. |
22:43:35 | gevaerts | Good :) |
22:43:36 | * | TheSeven probably just fixed it |
22:44:32 | TheSeven | for some reason it looks like the contents of the page is getting ignored these days |
22:45:20 | TheSeven | gevaerts: just to confirm, you just edited him into the WikiUsersGroup page's text content, right? |
22:45:29 | gevaerts | Yes |
22:45:38 | TheSeven | that doesn't seem to be in sync with the actual group at all |
22:45:41 | franklin | gevaerts: what email? |
22:45:59 | TheSeven | the actual group is listed below, and there's an "administration" section at the very bottom of the page |
22:46:10 | gevaerts | franklin: you mean you don't want to give me your email password? |
22:46:25 | gevaerts | Why not? |
22:46:28 | TheSeven | adding him using that seems to have worked, despite just showing a page with the text "Attention" and nothing else... |
22:46:32 | TheSeven | this wiki is just weird ,) |
22:46:33 | TheSeven | ;)* |
22:46:35 | franklin | gevaerts: it's my password! :; |
22:46:37 | franklin | ;) |
22:46:58 | gevaerts | franklin: yes, so how is that different from a password on a device? |
22:47:08 | TheSeven | franklin: are you planning to do this for ipod classics specifically? |
22:47:19 | franklin | TheSeven: no |
22:47:33 | TheSeven | because there is definitely no way to lock these things down |
22:47:39 | franklin | gevaerts: the password for webmail is always on, and it is stored on a remote server |
22:47:45 | the-kyle | Encryption and password protection is definitely not against open source principles. Linux, FreeBSD and other open source operating systems implement both. |
22:47:47 | TheSeven | (otherwise we wouldn't have been able to run rockbox on them in the first place) |
22:48:41 | franklin | the-kyle: DAPs are different from computers in that it is very easy to read/modify the hard drive. |
22:49:06 | TheSeven | well I wouldn't store that kind of information on the hard drive in the first place |
22:49:23 | TheSeven | the lock would typically have to be implemented inside the bootloader flash |
22:49:31 | franklin | TheSeven: how does iOS do it? |
22:49:38 | the-kyle | Well that and disk encryption would be rather hard to implement on a low-end device I would think. |
22:49:45 | TheSeven | iOS doesn't have easily removable storage |
22:50:10 | franklin | TheSeven: you're right (and it you can't read the disk easily, you mean?) |
22:50:10 | TheSeven | the-kyle: at least on ipod classic and ipod nano2g it would actually be easy and fast |
22:50:21 | franklin | TheSeven: why? modify emcore? |
22:50:33 | TheSeven | those chips have hardware crypto accelerators |
22:50:44 | the-kyle | Disk encryption would be the most secure form of password protection, but it most likely would only work on a few targets. |
22:50:48 | TheSeven | i.e. a fast AES256 hardware implementation |
22:51:16 | franklin | TheSeven: no, just hash the password somewhere and record that password protection is enabled |
22:51:21 | TheSeven | disk encryption only provides data protection though, it isn't really a theft deterrant |
22:51:23 | the-kyle | Oh that's not bad at all. But it would probably be limited to those devices. |
22:51:49 | gevaerts | franklin: *no* password thing is going to be a theft deterrent for a DAP |
22:52:02 | franklin | gevaerts: so, it's useless :( |
22:52:02 | TheSeven | franklin: yes, that's what I'd store on the bootloader flash if anywhere, to prevent people from taking out the HDD and messing with that information |
22:52:14 | TheSeven | however they can also mess with it on the bootloader flash on ipods, so that's pointless ;) |
22:52:25 | gevaerts | If you want to prevent theft, either use conventional means (keep the thing in a safe place at all times, chain it to your body, ...), or make it look broken |
22:52:43 | * | franklin wonders what you mean by broken |
22:52:56 | TheSeven | probably "not worth stealing" |
22:53:10 | gevaerts | Dents, a cracked screen, ... |
22:53:17 | franklin | TheSeven: like, every DAP nowadays :P |
22:53:17 | the-kyle | Apply physical damage to the device that is cosmetic only. |
22:53:33 | franklin | the-kyle: I want my DAP to look somewhat nice |
22:54:08 | the-kyle | In that case, it will look to a potential thief like something worth stealing. |
22:54:32 | franklin | Or, just add some secret way to turn it on (hold down center button), and not commit it to Git :D |
22:54:43 | gevaerts | Or you could *also* carry something much more expensive, so the thief goes for that instead :) |
22:54:59 | *** | Saving seen data "./dancer.seen" |
22:55:10 | the-kyle | Or better yet, something that *looks* more expensive. |
22:55:20 | franklin | Fake gold watch... |
22:55:26 | gevaerts | franklin: *how* exactly does a thief know you've added such a thing? Surely they'd just steal the thing and notice this later when they get home? |
22:55:26 | ZincAlloy | how about getting a cheap player? |
22:55:36 | gevaerts | Do you expect them to then bring the thing back to you? |
22:57:37 | franklin | gevaerts: well..... |
22:57:41 | the-kyle | If I'm carrying around a fake something that I would hope a thief would go for instead of my less expensive DAP, I would expect the thief to be gone and not be able to find me by the time the item is discovered to be a fake. |
22:58:08 | | Join stripwax [0] (~Miranda@rockbox/developer/stripwax) |
22:58:19 | franklin | the-kyle: ok, ok :) |
22:58:20 | gevaerts | the-kyle: yes, exactly. Same as with the password thing :) |
23:00 |
23:05:33 | | Join RiD [0] (~RiD@2.83.0.55) |
23:06:03 | franklin | I fear rockbox is slowly becoming obsolete as DAPs lose popularity to smartphones :( |
23:06:34 | the-kyle | No music player on my phone can even come close to the features and power of Rockbox. |
23:07:10 | franklin | Still, only two DAPs on http://www.rockbox.org/wiki/BuyersGuide are still in production (unstable targets are, though) |
23:07:13 | the-kyle | Not to mention that the battery needs to be used to make phone calls and do web stuff, and playing music would subtract from the battery live. |
23:08:32 | franklin | the-kyle: but even though rockbox IS far superior than smartphones in many ways, it doesn't fully support enough new players to gain many new users |
23:11:21 | franklin | BTW, when will 3.14 be released? Any pi easter eggs? Pi Day 2015? |
23:13:29 | | Quit stripwax (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) |
23:19:54 | | Join bertrik [0] (~quassel@rockbox/developer/bertrik) |
23:23:18 | RiD | so thats why i use rockbox in my phone :v |
23:25:35 | | Join kugel [0] (~kugel@p5DC53E23.dip0.t-ipconnect.de) |
23:25:35 | | Quit kugel (Changing host) |
23:25:35 | | Join kugel [0] (~kugel@rockbox/developer/kugel) |
23:26:31 | preglow | android rockbox still works better than any other android players i've been able to find |
23:26:38 | preglow | so it's still got tons of merit |
23:26:43 | preglow | and a long way to go... |
23:26:43 | | Quit kugel (Client Quit) |
23:31:13 | | Quit y4n (Quit: AMIGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHAHAHAHAAAAAAAAAAAAHAHAAA) |
23:34:26 | franklin | preglow: "I have this amazing piece of software, but you need the Android NDK and SDK as well as a computer to build it all." |
23:36:01 | franklin | preglow: "Oh yeah, I also need to have a *nix-like system to build it" |
23:39:25 | saratoga | our VM image should work, although you'll need to install the NDK |
23:41:57 | franklin | saratoga: exactly. it will have zero usage outside the developer community until it is accessible through "official" channels (Play Store) |
23:42:46 | preglow | doesn't really take that much to get a build |
23:42:52 | preglow | i haven't compiled it from source in years |
23:43:03 | preglow | but sure, it should be easier to install |
23:43:06 | preglow | like i said |
23:43:20 | preglow | tons of potential for improvement |
23:43:21 | franklin | preglow: saratoga: seriously, though. will it ever get on the Play Store? |
23:43:36 | preglow | with the developer interest it has currently: doubtful |
23:43:48 | preglow | and that is without me knowing anything of google's guidelines |
23:44:02 | franklin | preglow: I though you would know :) |
23:44:27 | preglow | might be stuff going on behind the scenes i know nothing of, i haven't been an active dev for ages now |
23:44:32 | preglow | but sure doesn't look like it |
23:46:46 | franklin | saratoga: do you know? how far along is RaaA? |
23:46:59 | preglow | i still haven't been able to find anything i'd rather use, but with my fervent hatred of library based players, that's no big wonder |
23:47:24 | franklin | preglow: library based? |
23:47:42 | preglow | yeah, you know, insisting on accessing your music as a metadata based library |
23:47:55 | franklin | preglow: don't get me started :) |
23:47:59 | preglow | browsing through artists/genres/albums and shit, with no alternative |
23:48:18 | franklin | preglow: I want to see all my directories with all my files and all my games |
23:48:23 | preglow | amen |
23:48:56 | franklin | preglow: and 2048 :) |
23:49:06 | RiD | i hate that too preglow :v |
23:50:17 | franklin | saratoga: there is no malloc() in RB!? |
23:50:35 | saratoga | yes, most devices dont' have virtual memory, so theres no way to malloc |
23:51:46 | franklin | saratoga: so I need to make a huge char array to use malloc?! |
23:52:06 | saratoga | you probably shouldn't use malloc at all, but yes, you could do that |
23:53:03 | franklin | saratoga: I do understand the philosophy behind it, though. most DAPs don't have MMUs |
23:53:14 | | Quit Rower (Quit: Hmmm...) |