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 2024-10-24

01:00
01:02:51 Join advcomp2019_ [0] (~advcomp20@user/advcomp2019)
01:03:41 Quit advcomp2019 (Read error: Connection reset by peer)
01:51:46***Saving seen data "./dancer.seen"
02:00
02:30:24 Join D_the_n [0] (~D_the_n@user/D-the-n:33076)
02:35:01 Quit D_the_n (Ping timeout: 248 seconds)
03:00
03:41:21 Quit Guest3072 (Ping timeout: 252 seconds)
03:42:53 Join buZz [0] (~buzz@192.161.48.59)
03:43:16 Nick buZz is now known as Guest5923 (~buzz@192.161.48.59)
03:51:47***Saving seen data "./dancer.seen"
05:00
05:04:49 Quit jacobk (Ping timeout: 260 seconds)
05:05:24 Join jacobk [0] (~quassel@47-186-105-237.dlls.tx.frontiernet.net)
05:51:48***Saving seen data "./dancer.seen"
07:00
07:23:32 Quit tertu (Quit: so long...)
07:25:33 Join tertu [0] (~tertu@user/tertu)
07:45:25 Join ac_laptop [0] (~ac_laptop@2a0c:e303:0:7300:e29d:31ff:fe2d:a258)
07:51:51***Saving seen data "./dancer.seen"
08:00
08:54:27 Quit jj5 (Quit: Konversation terminated!)
08:55:23 Join jj5 [0] (~jj5@100.80.216.139.dynamic.dsl.dv.iprimus.net.au)
09:00
09:29:46speachyOlsoFR: Given that you have some flakiness independent of rockbox, I don't know if that crash you hit has anything to do with my changes?
09:31:05speachyalso, "unsupported power management" means the device doesn't support the ATA PM commands −− eg "go to standby mode". You can always kill power externally.
09:32:34speachyhenk: In order. Yes, comanies can ship rockbox on a player if they want, as long as they comply with the GPL (ie complete corresponding source code to whatever they ship). I would also want to see them explicitly state that this device isn't endorsed by rockbox, yadda yadda.
09:34:02speachyNo, nobody ships Rockbox that we're aware of, though AGPTek did supply a firmware image that has the bootloader already present. I think the intent with that was to be more "cooperative" but they never did anything other than mail us two players to tinker with. (no technical assistance whatsoever)
09:39:15henkspeachy: ah, I see, thank you!
09:39:42speachyAlso I think the zishan unofficially ported rockbox to the z1 (if not that then one of the similar STM32-based designs) but they never provided anything other than a binary −− ie no sources. a shame, as that work would have been useful upstream.
09:41:14speachyAh, the Zishan T1. http://zishan.ru/files/ZiShan-T1/
09:42:50speachyblatant GPL violation due to the lack of source code but it's not like we can do anything about a russian company.
09:44:23speachyah, it has an allwinner FC100s The Z1 was the one with the STM32.
09:51:52***Saving seen data "./dancer.seen"
09:53:01henkyeah, at least not with reasonable effort …
09:53:23speachyrussian and/or chinese
09:53:32speachycan't even find a way to contact them.
10:00
10:56:30speachyfrustrating because problems in that port (stability, theming, etc) get blamed on us instead of zishan.
11:00
11:21:57TrzyzetIn that case a good announcement about this should be fine
11:22:29TrzyzetNot only about this particular player but there can be more of them
11:27:05speachyAnnouncement about what? That rockbox can be used by device manufacturers?
11:29:15speachy...or that we aren't responsible for problems in builds not produced by us?
11:51:56***No seen item changed, no save performed.
12:00
12:31:19CH23could add the device to the device roster with a message that it is not supported by rockbox.org
12:55:04speachyhonestly I'd rather not give them the benefit of being mentioned at all.
12:58:41speachyif they'd published source code they'd already be listed there. heck, the code would have probably been committed in-tree.
13:00
13:51:58***No seen item changed, no save performed.
14:00
14:31:14 Quit jacobk (Ping timeout: 248 seconds)
14:32:09 Join jacobk [0] (~quassel@47-186-105-237.dlls.tx.frontiernet.net)
14:58:04 Quit jacobk (Ping timeout: 260 seconds)
14:58:22 Join jacobk [0] (~quassel@47-186-105-237.dlls.tx.frontiernet.net)
15:00
15:09:00 Join D_the_n [0] (~D_the_n@user/D-the-n:33076)
15:52:02***Saving seen data "./dancer.seen"
16:00
16:13:55 Join OlsroFR [0] (~OlsroFR@user/OlsroFR)
16:14:07speachy... and they'd have probably sold many more units too. :D
16:15:10OlsroFR+speachy Hello. You are right, we are not going to learn more about this by using a setup that can't even be stable on Stock OS. I just unmounted back my Mini to put it again on the "recommended" iFlash setup: A real SD card of 128GB (a Lexar one). Now it boot reliably and was much more faster at transfering on the PC. Very promising.
16:15:41OlsroFROn the disk info debug menu, it now says "Flush cache: normal"
16:16:00speachyI'd not expect _any_ difference in data transfer performance FWIW.
16:16:20OlsroFRI started the battery benchmark. Is is now playing mp3's in loop
16:16:23speachyI think I have an 8GB Lexar in my mini2g's iflashCF
16:16:49speachywas the largest "real" SD card I had lying around
16:16:50OlsroFRI just feel like that 1TB micro sandisk was just too overkill. As I said, even Stock OS was struggling hard with this
16:17:05OlsroFRI kept my mini with that 1 TB card because I was too lazy to open it again and I was just using other kind of ipods
16:17:32OlsroFRHaving power management enabled on iFlash to cut off the power is a very exciting change
16:23:48 Quit OlsroFR (Quit: Client closed)
16:33:50speachyI'm sure battery life will be improved, but what I'm worried about is data corruption from incomplete writes.
17:00
17:09:31 Join Moriar [0] (~moriar@107-200-193-159.lightspeed.stlsmo.sbcglobal.net)
17:19:50 Quit Bobathan_ (Ping timeout: 272 seconds)
17:21:04 Join Everything [0] (~Everythin@178-133-200-119.mobile.vf-ua.net)
17:22:24 Join Bobathan_ [0] (~admin@syn-065-029-248-157.res.spectrum.com)
17:52:03***Saving seen data "./dancer.seen"
17:52:04 Join braewoods__ [0] (~braewoods@user/braewoods)
17:52:47 Quit braewoods_ (Read error: Connection reset by peer)
17:57:04 Quit Bobathan_ (Ping timeout: 265 seconds)
17:58:49 Join othello8 [0] (~Thunderbi@pool-100-36-176-164.washdc.fios.verizon.net)
17:59:22 Quit othello8 (Client Quit)
18:00
18:01:14 Join Bobathan_ [0] (~admin@syn-065-029-248-157.res.spectrum.com)
18:16:41 Quit Bobathan_ (Ping timeout: 244 seconds)
18:20:00 Join Bobathan_ [0] (~admin@syn-065-029-248-157.res.spectrum.com)
18:34:05 Quit ac_laptop (Ping timeout: 260 seconds)
18:51:07 Quit Everything (Quit: leaving)
18:55:45 Quit advcomp2019_ (Ping timeout: 276 seconds)
19:00
19:26:26TrzyzetSorry speachy, I meant lack of responsibility but yeah, good point about not mentioning about them at all. But i think it can be done in a way it will not mention any particular company/model
19:42:49 Join massiveH [0] (~massiveH@2600:4040:a982:dc00:4d91:ad90:c8a1:cdfd)
19:44:21 Quit Bobathan_ (Ping timeout: 248 seconds)
19:46:21 Join Bobathan_ [0] (~admin@syn-065-029-248-157.res.spectrum.com)
19:52:05***Saving seen data "./dancer.seen"
19:54:44 Join advcomp2019 [0] (~advcomp20@user/advcomp2019)
21:00
21:16:05 Quit baltazar (Ping timeout: 248 seconds)
21:18:02 Join baltazar [0] (~baltazar@user/baltazar)
21:26:41 Quit othello7 (Remote host closed the connection)
21:28:27 Join othello7 [0] (~Thunderbi@pool-100-36-176-164.washdc.fios.verizon.net)
21:52:09***Saving seen data "./dancer.seen"
22:00
22:08:06 Quit Moriar (Quit: Leaving.)
22:08:11 Quit braewoods__ (Remote host closed the connection)
22:08:54 Join braewoods__ [0] (~braewoods@user/braewoods)
23:00
23:05:12 Quit massiveH (Quit: Leaving)
23:22:28 Nick Guest5923 is now known as buZz (~buzz@192.161.48.59)
23:52:10***Saving seen data "./dancer.seen"

Previous day | Next day