<ashkitten>
well i'm stepping out of this one, i'm way out of my depth
<samueldr>
though this could be for mainline, I'm unsure now
<samueldr>
still something useful I hadn't seen
<samueldr>
oh, Dan//ct12[m] is right here
<samueldr>
(looked at the issue text and not the linked comment)
<samueldr>
and using halium seems to be working for 'em so I figure since halium might be the pragmatic solution for more devices that's going to be the way forward
<ashkitten>
fair enough
<samueldr>
when I said "right here" I meant "in this channel" :)
<ashkitten>
we can worry about getting devices on mainline kernels and such later, getting it working is more important i think
<samueldr>
though it would be nice if a non-halium solution existed too
<samueldr>
yes!
<samueldr>
make it trivial to port a non-mainline system so the distro is not used by only a handful, but maybe a couple handfuls of developers!
<ashkitten>
yes hehe
<ashkitten>
what is halium?
<samueldr>
especially since getting a useful phone system (e.g. phone GUI), a good chunk of the work will be the same regardless of mainline or not
<ashkitten>
right
<samueldr>
brielfy said, and probably wrong, halium is a way to get a container based on android to run the blobby bits on non-android https://docs.halium.org/en/latest/
<ashkitten>
ah i see
<ashkitten>
how trivial is that going to be to incorporate into mobile nixos?
<ashkitten>
(i said it the right way around this time!)
<samueldr>
:)
<samueldr>
unknown yet, but I will not make it harder on myself than it should, I'll compromise and dot the rootfs with some android-specific folders if it helps
<ashkitten>
heh
<ashkitten>
save cleanup for ourselves later
<ashkitten>
i'm sure in a year or two when mobile nixos is getting support for more devices we'll be able to start making it more nix-y
<samueldr>
that's part of the dream
<ashkitten>
c:
<samueldr>
invoking cunningham's law, doing it wrong so others can correct me ;)
<ashkitten>
ahaha
* ashkitten
clicks "reboot", phone shuts down
* ashkitten
clicks "shut down", phone reboots
<ashkitten>
:V
<ashkitten>
i guess "reboot" means "reboot but slower" and "shutdown" means "reboot quickly" now
<samueldr>
is it plugged into the power?
<ashkitten>
yeah
<samueldr>
most qualcomm phones will not shutdown when plugged
<ashkitten>
hmph
<samueldr>
yes hmph
<samueldr>
pretty annoying
<samueldr>
they do boot in a special "battery" os, but I think that OS may have been "broken" by bad assumptions by Mobile NixOS
<ashkitten>
i shut it down from the bootloader
<ashkitten>
and then it rebooted
<ashkitten>
into the os
<samueldr>
yep
<ashkitten>
hnnnnn
<ashkitten>
whatever, i'll just leave it unplugged
<samueldr>
I believe the default initramfs has a way to detect that condition and uses it to stay in a special boot mode
<samueldr>
probably a kernel commandline
<ashkitten>
right
* samueldr
notes to check the issue
<samueldr>
it would be best if we could somehow handle it
<ashkitten>
anyway i'm gonna make a pull request to make marlin match walleye a bit more, because it also has boot_as_recovery and vendor_partition
<ashkitten>
and ab_partitions
<samueldr>
great, thanks
<samueldr>
it has boot as recovery?
<samueldr>
it doesn't seem to need the skip_initramfs patch
orivej_ has quit [Ping timeout: 264 seconds]
<samueldr>
oh no
<samueldr>
it does
<samueldr>
yes
<ashkitten>
it does, all ab devices do i think
<samueldr>
I didn't recognize the patch name
<samueldr>
I'm not positive they all do, but I would assume it's more likely
<samueldr>
there's some OEMs doing funky stuff
<ashkitten>
as far as i know, all a/b devices lack a recovery partition
<samueldr>
xiaomi redmi note 7 has boot as recovery like things, e.g. does skip_initramfs funkyness, but still has a recovery partition... but yeah that's not A/B
<samueldr>
I don't have the docs page for it, but IIRC the android docs don't say that boot as recovery is dependent on A/B and A/B on boot as recovery
<samueldr>
Valodim: noted, can you open an issue with what you know and tried with the issue, cc @samueldr ?
<samueldr>
not sure though when I'll personally be able to get to that, but if it's on the github issue tracker, hopefully when others have the issue it'll centralise the reports
<Valodim>
will do, thanks
orivej has quit [Ping timeout: 264 seconds]
zupo has quit [Ping timeout: 250 seconds]
<Valodim>
I wonder if not having a working installation image might be a blocker for 20.03, since rpi3 is officially supported?
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
v0|d has quit [*.net *.split]
tilpner has quit [*.net *.split]
cptchaos83 has quit [*.net *.split]
v0|d has joined #nixos-aarch64
cptchaos83 has joined #nixos-aarch64
wavirc22 has joined #nixos-aarch64
FRidh has quit [Quit: Konversation terminated!]
tilpner has joined #nixos-aarch64
kai_w has quit [Quit: Konversation terminated!]
orivej has joined #nixos-aarch64
wavirc22 has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Client Quit]
wavirc22 has joined #nixos-aarch64
lovesegfault has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
logand`` has quit [Ping timeout: 256 seconds]
<ashkitten>
samueldr: so it looks like from the halium documentation, it wants you to use its own stage-1?
<samueldr>
I don't know yet
leonardp has quit [Remote host closed the connection]