--- Log for 20.06.122 Server: tantalum.libera.chat Channel: #rockbox --- Nick: rb-logbot Version: Dancer V4.16 Started: 1 month and 17 days ago 00.13.04 Join kkffiirr [0] (~androirc@95.86.84.100) 00.14.05 # Hi 00.14.37 # I have installed yesterday's daily build on my zen x-fi3 00.15.41 # After setting a theme the screen went white, after pressing the reset button, the device became a brick, nothing on the screen and the pc doesn't identify it.... 00.16.04 # Any insights on what can be done and what happened there? 00.17.09 Quit kkffiirr (Remote host closed the connection) 00.17.37 Join kkffiirr [0] (~androirc@95.86.84.100) 00.21.58 Quit yang (*.net *.split) 00.21.58 Quit woffs (*.net *.split) 00.22.37 Join yang [0] (sid23779@id-23779.lymington.irccloud.com) 00.25.29 Nick yang is now known as Guest2334 (sid23779@id-23779.lymington.irccloud.com) 00.27.00 Quit mrkrisprolls (*.net *.split) 00.28.02 Join kkffiirr2 [0] (~androirc@2.53.175.121) 00.30.07 Quit kkffiirr (Ping timeout: 256 seconds) 00.30.08 Quit MayeulC (*.net *.split) 00.30.08 Quit melmothX (*.net *.split) 00.30.42 Join melmothX [0] (~marco@amusewiki/marco) 00.31.15 Nick kkffiirr2 is now known as kkffiirr (~androirc@2.53.175.121) 00.36.13 Join mrkrisprolls [0] (mrkrisprol@mrkrisprolls.orange.ircnow.org) 00.46.17 Join MayeulC [0] (~mayeulc@2001:470:69fc:105::35e) 00.53.02 Quit libomsai[m] (Ping timeout: 272 seconds) 00.53.58 # <_bilgus__> kkffiirr, likely its stuck have to wait for it to run down unless there is a reset pinhole or something 00.57.31 # I pushed the reset pin hole 00.57.54 # Now it is not responsive and recognized 01.04.13 Join libomsai[m] [0] (~libomsaim@2001:470:69fc:105::1:add) 01.20.11 *** Saving seen data "./dancer.seen" 01.35.17 Quit spork (Quit: leaving) 02.09.10 Join spork [0] (topic@i121118.upc-i.chello.nl) 03.20.14 *** Saving seen data "./dancer.seen" 04.11.06 Quit kkffiirr (Remote host closed the connection) 04.11.18 Join kkffiirr [0] (~androirc@2.53.175.121) 04.58.55 # Okay, I had opened it, shorted the battery for two seconds and then it worked 04.59.06 # Guess it was frezzed in deep level 05.08.25 Quit kkffiirr (Remote host closed the connection) 05.20.15 *** Saving seen data "./dancer.seen" 06.02.29 Quit Galois (Ping timeout: 246 seconds) 06.17.51 Join woffs [0] (3cd46299b2@woffs.de) 07.20.18 *** Saving seen data "./dancer.seen" 07.29.54 Join LambdaCalculus37 [0] (~LambdaCal@gateway/vpn/pia/lambdacalculus37) 07.31.20 # @speachy Don't know if you saw before, but I had an aarch64 build of RBUtil 1.5.1 up on the forums for some time now: https://u.pcloud.link/publink/show?code=XZfilFVZDb4bGIieru5MBhjPjc8MwYntbcxy 07.32.13 # Tested it with my iriver H320 and successfully installed a newer build and a theme with it. 07.35.12 Quit LambdaCalculus37 (Quit: LambdaCalculus37) 08.29.31 Join massiveH [0] (~massiveH@ool-4a5862ee.dyn.optonline.net) 09.20.20 *** Saving seen data "./dancer.seen" 09.55.14 Join Galois [0] (djao@efnet.math.uwaterloo.ca) 10.39.40 Quit massiveH (Quit: Leaving) 11.03.36 Quit amiconn (Quit: No Ping reply in 64 seconds.) 11.03.49 Join amiconn [0] (jens@p200300ea8741be00305e95fffec66ff3.dip0.t-ipconnect.de) 11.20.24 *** Saving seen data "./dancer.seen" 12.19.09 Join lebellium [0] (~lebellium@2a01cb04012c0900c480511deea4a7b3.ipv6.abo.wanadoo.fr) 12.41.03 Nick funman_ is now known as funman (~fun@chui-pas.net) 13.20.28 *** No seen item changed, no save performed. 14.40.36 Join emanuele6 [0] (~emanuele6@user/emanuele6) 14.40.45 Part emanuele6 (WeeChat 3.5) 15.20.32 *** Saving seen data "./dancer.seen" 15.45.42 Quit Galois (Ping timeout: 264 seconds) 15.45.58 Quit woffs (Ping timeout: 240 seconds) 15.47.30 Quit spork (Ping timeout: 268 seconds) 15.47.39 Join spork [0] (topic@i121118.upc-i.chello.nl) 15.55.39 Join Galois [0] (djao@efnet.math.uwaterloo.ca) 17.20.34 *** Saving seen data "./dancer.seen" 17.54.14 Quit lebellium (Quit: Leaving) 17.54.35 # <_bilgus__> im honestly surprised shorting the battery didn't blow the fuse on the battery but good now I just wonder why a theme was able to take his device down 18.00.41 # _bilgus__: depends on the design, but i guess they didn't want to wait for the battery to drain. 18.01.31 # depending on the protection circuit, it could just disconnect the load circuit until the short is remedied 18.01.53 # i've used BMS where a short circuit will cause the load circuit to be disconnected until it is reconnected 18.02.06 # <_bilgus__> I don't have very good luck with that :p 18.03.24 # a properly sized resistor could also protect against external shorts by acting as a CC limiter 18.59.05 # Build Server message: 3New build round started. Revision ed37c2e894, 303 builds, 8 clients. 19.20.38 *** Saving seen data "./dancer.seen" 19.29.58 # Build Server message: 3Build round completed after 1853 seconds. 19.30.01 # Build Server message: 3Revision ed37c2e894 result: 60 errors 0 warnings 20.18.49 # Build Server message: 3New build round started. Revision 6cdd142d5c, 303 builds, 8 clients. 20.18.56 # <_bilgus__> that was dumb 20.18.59 # <_bilgus__> lol 20.41.18 # Build Server message: 3Build round completed after 1349 seconds. 20.41.20 # Build Server message: 3Revision 6cdd142d5c result: All green 21.20.39 *** No seen item changed, no save performed. 22.58.11 Quit akaWolf (Ping timeout: 246 seconds) 23.20.42 *** Saving seen data "./dancer.seen" 23.29.15 Join akaWolf [0] (~akaWolf@akawolf.org)