<Irenes[m]> hm. I was going to test the FEL mode but I got sidetracked. I realized that the easiest way to do that would be to power it on with no bootable medium, which would mean wiping the eMMC. I'm not willing to do that until I have more stuff working.
<samueldr> there is "the FEL sdcard" that should work
<samueldr> hmm, that go command may work too http://linux-sunxi.org/FEL#Through_serial_console
h0m1 has quit [Ping timeout: 240 seconds]
h0m1 has joined #nixos-aarch64
cptchaos83 has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
cptchaos83 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 265 seconds]
<Irenes[m]> hah! nice, thank you
<samueldr> once I know whether FEL is expected to work, or not, on a pinephone where JumpDrive works, I'll test it on my device
<samueldr> kinda bummed by that issue
<Irenes[m]> I should clarify that I'm not actually familiar with JumpDrive?
<samueldr> basically exposes the eMMC like a flash drive to the host computer via usb gadget mode
<Irenes[m]> oh excellent
<Irenes[m]> but it doesn't work on yours?
<samueldr> nope
<Irenes[m]> any idea why not?
<samueldr> not really, there's no way to verify if it's the usb daughterboard, or the mainboard that has issues AFAIK
<samueldr> (I asked where relevant)
<Irenes[m]> ah yeah
<samueldr> I did try and reseat the FPC (connectors) both on the mainboard and that daughterboard
<samueldr> though didn't change anything
<samueldr> it might also be that flat cable that's defective!
<samueldr> if it is it would be amazingly annoying to change considering it's behind a protective layer
<samueldr> though I'm pretty sure it's not something like the whole usb that's broken, since the GSM modem tests do work
<samueldr> and it does charge with a dumb cable
<samueldr> (not with any of my PD chargers, but that's still unknown if it is expected it should work or not)
<samueldr> (some devs say no, some devs say yes... and they both may be right)
<samueldr> (it could very well depend on the particular PD charger!)
<Irenes[m]> yuck, that sounds super frustrating
<samueldr> the worst part is getting clear yes and no information about that
<Irenes[m]> yeah putting firmware in power cords was hubris
<samueldr> oh, not even from the PD situation
<samueldr> what I could get is that anything else than dumb charger and gadget mode should not be expected to work at the time
<Irenes[m]> (it's not even just the charger, USB-C cables from Apple and Google have active components these days)
<samueldr> yes
<samueldr> not only apple and google
<Irenes[m]> yeah
<Irenes[m]> people tend to not think it's widespread so I say it that way to explain why it is more common than they might assume
<samueldr> good intentions paves the way to hell
<Irenes[m]> yeah
<Irenes[m]> for whatever it's worth, I have been having trouble charging it also but I think that may be because the kernel is expected to have some role in making PD happen
<Irenes[m]> thus far what I know works is booting it up and then charging it while it's booted
<Irenes[m]> I don't really understand what's going on there
<Irenes[m]> I haven't definitively determined that it won't charge while powered down, yet
<samueldr> yep, anything else than dumb charger needs some involvement from bits still unfinished software-wise
<samueldr> when shut down it does charge
<samueldr> (though in my case nudging the cable acts as if I plugged/unplugged and it will turn it back on)
<Irenes[m]> good to know
<samueldr> (which is to be expected)
<samueldr> yes, it will also charge faster when shut down
<samueldr> it's not really able to charge when running with the display on :/
<Irenes[m]> yeah I have a lot of high-durability full-featured C-to-C cables because I got so frustrated with wondering whether the flake was the connector or the wire, but even so, I find it flaky
<Irenes[m]> I really wish type-C connectors were just a little bit better, mechanically
<samueldr> oh, I have a power-only type-c to type-a cable that doesn't charge the pinephone
<samueldr> but works on everything else as a dumb charger
<Irenes[m]> ah yeah :/
<Irenes[m]> 🎉 #96 merged
<{^_^}> https://github.com/NixOS/nixpkgs/pull/96 (by aszlig, 7 years ago, merged): google-talk-plugin: Prefer Debian package.
<Irenes[m]> grats!
<Irenes[m]> lol wrong repo
<samueldr> mobile-nixos#96
<{^_^}> https://github.com/NixOS/mobile-nixos/pull/96 (by samueldr, 2 weeks ago, merged): device: add pine64-pinephone-braveheart
<samueldr> yes, though trivial as I make the rules :3
<Irenes[m]> sure, yes :)
<samueldr> and one of the reason it took some time is that I wanted to work with the LEDs so you know it's booted as early as possible
<samueldr> I can't stand having no feedback
<Irenes[m]> thank you for doing that! likewise
<Irenes[m]> I'm about an hour in to copying it to an SD card, heh
<samueldr> oof, dd without bs?
<Irenes[m]> oh uh... yes, guilty
<samueldr> :)
<Irenes[m]> I got lazy lol
<samueldr> sd cards don't let you be lazy
<Irenes[m]> indeed.... is there a block size you can recommend or does it depend on the USB controller?
<Irenes[m]> (I'm using a USB dongle for it)
<samueldr> I played around with block sizes until I didn't see a change with status=progress
<samueldr> 8M
<Irenes[m]> cool lol
<Irenes[m]> thank you
orivej has quit [Ping timeout: 258 seconds]
<ashkitten> i usually do 4M because that's basically the default block size for most storage media
<ashkitten> and larger isnt usually significantly faster
cidkid has joined #nixos-aarch64
cidkid has quit [Remote host closed the connection]
<Irenes[m]> I am pleased to report that my demo build does, in fact, work!
<Irenes[m]> I think the build process may have left a stray loop device on my system - I'm not 100% that it wasn't there already from something else
<samueldr> unlikely considering no part of the image building uses loops and mounts
<samueldr> it's all done through userspace manipulation of the filesystem image
<samueldr> and additionally the nix sandbox should isolate the system from that
<samueldr> (and I'm not even sure loop mounts can happen due to that sandbox)
FRidh has joined #nixos-aarch64
<samueldr> though nice to head the demo system build works
<Irenes[m]> makes sense. probably something else that I did a while ago then.
orivej has joined #nixos-aarch64
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
wavirc22 has joined #nixos-aarch64
Darkmatter66 has joined #nixos-aarch64
Darkmatter66_ has quit [Ping timeout: 240 seconds]
Darkmatter66_ has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 264 seconds]
zupo has joined #nixos-aarch64
wavirc22 has quit [Read error: Connection reset by peer]
wavirc22 has joined #nixos-aarch64
misuzu has quit [Remote host closed the connection]
misuzu has joined #nixos-aarch64
orivej has quit [Ping timeout: 250 seconds]
Aleksejs has quit [Ping timeout: 260 seconds]
Aleksejs has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
Darkmatter66_ has quit [Ping timeout: 256 seconds]
Darkmatter66 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 264 seconds]
Darkmatter66 has joined #nixos-aarch64
WilliButz has quit [Remote host closed the connection]
WilliButz has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
wavirc22 has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
wavirc22 has joined #nixos-aarch64
andi- has quit [Remote host closed the connection]
andi- has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 240 seconds]
bennofs has quit [Ping timeout: 272 seconds]
bennofs has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
h0m1 has quit [Quit: WeeChat 2.7.1]
h0m1 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
zupo has joined #nixos-aarch64
h0m1 has quit [Quit: WeeChat 2.7.1]
h0m1 has joined #nixos-aarch64
h0m1 has quit [Client Quit]
h0m1 has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
t184256 has left #nixos-aarch64 [#nixos-aarch64]
t184256 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
lovesegfault has quit [Quit: WeeChat 2.7.1]
lovesegfault has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
FRidh has quit [Quit: Konversation terminated!]
orivej has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
zupo has joined #nixos-aarch64
adisbladis has quit [Quit: ZNC 1.7.5 - https://znc.in]
adisbladis has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
lovesegfault has quit [Quit: WeeChat 2.7.1]
zarel has quit [Ping timeout: 265 seconds]
zarel has joined #nixos-aarch64
Ox4A6F has quit [Read error: Connection timed out]
wavirc22 has joined #nixos-aarch64
Ox4A6F has joined #nixos-aarch64
codyopel has quit [Ping timeout: 246 seconds]
codyopel has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
ekleog has quit [Quit: WeeChat 2.6]
ekleog has joined #nixos-aarch64