--- Log for 25.10.123 Server: cadmium.libera.chat Channel: #rockbox --- Nick: rb-logbot Version: Dancer V4.16 Started: 12 days and 12 hours ago 00.27.41 *** Saving seen data "./dancer.seen" 00.29.53 Join dconrad [0] (~dconrad@152.117.104.216) 00.34.14 Quit dconrad (Ping timeout: 255 seconds) 00.37.18 Quit m01 (Quit: Konversation terminated.) 00.40.06 Join m01 [0] (~quassel@vps-b172b88b.vps.ovh.net) 00.59.20 Quit othello7 (Ping timeout: 255 seconds) 01.00.29 Join jacobk [0] (~quassel@utdpat242024.utdallas.edu) 01.05.57 Quit braewoods_ (Remote host closed the connection) 01.06.05 Join braewoods__ [0] (~braewoods@user/braewoods) 02.25.16 Quit braewoods__ (Ping timeout: 272 seconds) 02.27.27 Join braewoods [0] (~braewoods@user/braewoods) 02.27.44 *** Saving seen data "./dancer.seen" 02.30.13 Join dconrad [0] (~dconrad@152.117.104.216) 02.34.31 Quit dconrad (Ping timeout: 255 seconds) 02.55.09 Quit hellsnake (Quit: Connection closed for inactivity) 03.11.30 Quit jacobk (Ping timeout: 272 seconds) 03.29.05 Join jacobk [0] (~quassel@64.189.201.150) 03.31.21 # Hi! Do you know of any other devices with (hardware) support for wifi+bluetooth and a possibility for custom firmware other than the shanling q1? 03.48.00 # fiio m3k and surfans f20 + clonse 03.48.02 # clones 04.07.37 # thanks! 04.13.29 # all those devices are based on the same x1000 soc 04.14.47 Quit Nyaa (Remote host closed the connection) 04.15.09 Join Nyaa [0] (Nyaaori@cyberia.club/meow/nyaaori) 04.27.48 *** Saving seen data "./dancer.seen" 04.30.32 Join dconrad [0] (~dconrad@152.117.104.216) 04.34.50 # spork: and to all of these have wifi hardware in them as well? 04.35.06 Quit dconrad (Ping timeout: 260 seconds) 04.38.16 Quit the_sea_peoples (Ping timeout: 255 seconds) 04.47.17 # i am now starting to have doubts about that 04.47.27 # i really thought they at least all had bluetooth 04.48.28 # maybe not wifi though 04.50.56 Join the_sea_peoples [0] (~the_sea_p@c-73-53-78-62.hsd1.wa.comcast.net) 04.51.11 # sorry, i was wrong. 04.51.19 # the fiio m3k does not even have bluetooth 04.51.48 # and AIGO EROS Q / EROS K / AGPTek H3 / HIFI WALKER H2 / Surfans F20 only seem to have bluetooth 05.04.49 # hmm, so nothing else with wifi? 05.05.39 # guess I'll stick with the q1 then, though it's quite pricey 05.06.25 # i use mine a lot, but never for the wifi feature 05.06.44 # i believe it cannot do more than transfer files 05.07.38 # it definitely does not stream music if that is what you are looking for 05.07.54 # I want to make it do so :P 05.07.59 # i think the newer 'm0 pro' does that for tidal, but it is not supported by rockbox 05.13.43 Quit the_sea_peoples (Ping timeout: 260 seconds) 05.13.43 Quit CH23_M (Read error: Connection reset by peer) 05.18.12 Join CH23_M [0] (~CH23@revspace/participant/ch23) 06.27.49 *** Saving seen data "./dancer.seen" 06.30.51 Join dconrad [0] (~dconrad@152.117.104.216) 06.35.03 Quit dconrad (Ping timeout: 240 seconds) 07.04.08 # not -yet- 07.04.09 # :D 07.04.24 # baltazar: how about that new gay-ipod 07.04.32 # its got wifi+BT from launch 07.06.00 # baltazar: this; https://www.crowdsupply.com/cool-tech-zone/tangara 07.06.06 # might get rockbox eventually ;) 07.13.11 Quit sch (Ping timeout: 260 seconds) 08.09.28 # the agptek rocker also has bt. none of them have wifi IIRC. 08.09.59 # i was certain it was part of the x1000 soc but apparently not 08.10.28 # they all have an external CSR bt module 08.11.33 # honestly if oyu want one of these things to do streaming stuff, there are plenty of options but they are all effectively just non-cellular smartphones, only crappier and more proprietary. 08.12.20 # sure they may or may not have higher-quality DACs but ... the source material is highly compressed, plus you're probably using BT headphones anyway. :D 08.14.44 # there are a lot of android devices without cellular that do pretty much just that 08.21.55 # i have one of those Archos bed-alarm-clockradios with android 3(?) 08.22.00 # maybe android 2 even 08.22.10 # its cute and funny, but eh, well 08.27.51 *** Saving seen data "./dancer.seen" 08.31.11 Join dconrad [0] (~dconrad@152.117.104.216) 08.35.18 Quit dconrad (Ping timeout: 246 seconds) 08.38.21 # yeah. once you try to do streming you then have to have a full (modern!) wifi stack, tcp/ip, http, tls/ssl, and likely additional crap on top for authentication that may or may not effectively require a browser with javascript. 08.38.52 # it's an order of magnitude or two more code and required oomph. 08.48.42 # with a nice drm sauce 08.48.42 # iirc the tangara doesn't have immediate plans to light up the wifi side of things, but they use the bt side of things for audio. 08.49.50 # (that said I'm 90% sure that esp32 module relies on a proprietary binary-only stack. because of course it does..) 08.51.37 # hwcodec-bt 09.03.47 # the tcpip stack on ESP* is lwIP 09.03.55 # fyi 09.04.13 # the bt stack i have no clue about 09.04.16 Quit jacobk (Ping timeout: 272 seconds) 09.04.18 # I was referring to bt, sorry 09.04.21 # np 09.04.42 # could very well have 'no stack' 09.04.49 # lwip is decent enough, especially if you have the resources to enable its socket API 09.04.53 # and you need to implement it all, with examples in SDK 09.04.59 # speachy: yeah you can do raw sockets 09.05.06 # hell, you can even send 'raw wifi packets' :) 09.05.14 # handy for deauths etc ;) 09.05.41 # in a former lifetime I helped build a stm32-based module. 09.06.09 # er, a esp32-wrooom-like module, ie an mcu+wifi, though no bt 09.06.40 # wrote the wifi stack from scratch, and used lwip 09.07.02 Join othello7 [0] (~Thunderbi@pool-100-36-166-8.washdc.fios.verizon.net) 09.07.03 # didn't have the resources for BSD sockets though. 09.07.30 # the limitation was RAM more than anything else. 09.07.40 # (especially as it needed to handle wpa-enterprise auth!) 09.13.36 # speachy: the wifi&bt on a wroom are internal to the esp soc though ;) 09.14.51 # that doesn't mean the code tehy need to operate doesn't run on the main processors. 09.15.34 # well, partly 09.15.44 Join jacobk [0] (~quassel@129.110.242.224) 09.18.52 # speachy: the funniest thing about this whole ESP ecosystem to me is ; 09.19.07 # they made the ESP8285 first, a wifi card for SDIO usage i believe 09.19.16 # the -exact same- soc is the ESP8266 09.19.37 # they just released a SDK for the same soc, to let ppl 'arduino it up' 09.19.48 # while actually have been made as a appliance 09.19.49 # heh yeah 09.19.55 # pretty cool stuff to me :D 09.27.17 # pretty common for these SoCs to get lots of variants that differ only in which pins are brought to pad packages. 09.56.51 Quit __builtin (Read error: Connection reset by peer) 09.57.02 Join __builtin [0] (~quassel@rockbox/developer/builtin) 10.08.11 Quit jacobk (Ping timeout: 260 seconds) 10.15.36 Join jacobk [0] (~quassel@utdpat241106.utdallas.edu) 10.27.52 *** Saving seen data "./dancer.seen" 10.28.01 Quit jacobk (Ping timeout: 260 seconds) 10.31.30 Join dconrad [0] (~dconrad@152.117.104.216) 10.35.46 Quit dconrad (Ping timeout: 258 seconds) 10.56.45 Join PressY4Pie [0] (~PressY4Pi@2601:285:8000:1:f1ca:358e:c989:c24c) 11.49.41 Quit Maxdamantus (Ping timeout: 255 seconds) 11.51.22 Join Maxdamantus [0] (~Maxdamant@user/maxdamantus) 12.27.53 *** Saving seen data "./dancer.seen" 12.31.49 Join dconrad [0] (~dconrad@152.117.104.216) 12.36.19 Quit dconrad (Ping timeout: 252 seconds) 13.29.25 Join lebellium [0] (~lebellium@2a01cb040610e000cd70440fab2128bf.ipv6.abo.wanadoo.fr) 13.41.00 Quit PressY4Pie (Quit: Leaving) 13.52.25 Quit CH23_M (Ping timeout: 258 seconds) 13.52.35 Join CH23_M [0] (~CH23@revspace/participant/ch23) 14.04.38 Quit CH23_M (Read error: Connection reset by peer) 14.04.50 Join CH23_M [0] (~CH23@revspace/participant/ch23) 14.27.56 *** Saving seen data "./dancer.seen" 14.32.09 Join dconrad [0] (~dconrad@152.117.104.216) 14.36.28 Quit dconrad (Ping timeout: 255 seconds) 14.47.03 Join Pokey [0] (~pokey@spikeyCactus/hoosky) 15.03.56 Join jacobk [0] (~quassel@cpe-76-186-215-32.tx.res.rr.com) 15.09.32 Quit jacobk (Ping timeout: 248 seconds) 16.00.12 Quit bertrik (Ping timeout: 240 seconds) 16.06.11 Join bertrik [0] (~bertrik@revspace/participant/bertrik) 16.27.58 *** Saving seen data "./dancer.seen" 16.32.27 Join dconrad [0] (~dconrad@152.117.104.216) 16.36.36 Quit dconrad (Ping timeout: 240 seconds) 17.30.44 Quit lebellium (Quit: Leaving) 18.28.00 *** Saving seen data "./dancer.seen" 18.32.46 Join dconrad [0] (~dconrad@152.117.104.216) 18.36.38 Join jacobk [0] (~quassel@59.sub-97-158-209.myvzw.com) 18.37.31 Quit dconrad (Ping timeout: 264 seconds) 18.47.52 Join dconrad [0] (~dconrad@152.117.104.216) 19.31.21 Join massiveH [0] (~massiveH@2600:4040:a982:c800:27f2:68af:c6b:c898) 19.42.33 Join Moriar [0] (~moriar@107-200-193-159.lightspeed.stlsmo.sbcglobal.net) 20.09.12 Quit dconrad (Read error: Connection reset by peer) 20.10.29 Join dconrad [0] (~dconrad@152.117.104.216) 20.28.02 *** Saving seen data "./dancer.seen" 20.38.28 Quit jacobk (Read error: Connection reset by peer) 21.35.11 Quit dconrad (Remote host closed the connection) 22.05.32 Quit massiveH (Quit: Leaving) 22.09.10 Join dconrad [0] (~dconrad@152.117.104.216) 22.28.05 *** Saving seen data "./dancer.seen" 22.36.14 Quit advcomp2019__ (Read error: Connection reset by peer) 22.36.17 Join advcomp2019_ [0] (~advcomp20@user/advcomp2019) 22.44.18 Quit Moriar (Quit: Leaving.) 22.45.06 Join advcomp2019 [0] (~advcomp20@user/advcomp2019) 22.47.52 Quit advcomp2019_ (Ping timeout: 255 seconds) 23.52.10 Quit dconrad (Remote host closed the connection) 23.56.09 Join dconrad [0] (~dconrad@152.117.104.216)