<Irenes[m]> samueldr: I think more primers on this are good
<Irenes[m]> I think it's important to tell people why they should want security + tinkering
<Irenes[m]> I hope you write that piece
<samueldr> yes, and more importantly, to understand the nuance and how it affects the user
<samueldr> because, in the end, it's the user that's always in charge of their own security
<samueldr> so they better understand their own
<samueldr> and know *where* it fails
<Irenes[m]> yes, absolutely
<samueldr> I did some searching around and found what is likely a non-limited qualcomm programmer for the xiaomi-lavender (redmi note 7), which means it might be completely openly readable
<samueldr> I'll have to play with the oneplus3 first and understand how it works, what you can do and how it affects you
<samueldr> and see afterwards if it is useful in fixing a "bricked" xiaomi-lavender
dayou has joined #nixos-aarch64
dayou has quit [Ping timeout: 246 seconds]
dayou has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 272 seconds]
h0m1 has joined #nixos-aarch64
Darkmatter66_ has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
dayou has quit [*.net *.split]
lopsided98 has quit [*.net *.split]
andi- has quit [*.net *.split]
lordcirth has quit [*.net *.split]
leonardp has quit [*.net *.split]
qy[m]1 has quit [*.net *.split]
NickHu has quit [*.net *.split]
alienpirate5 has quit [*.net *.split]
{^_^} has quit [*.net *.split]
sphalerite has quit [*.net *.split]
andi- has joined #nixos-aarch64
lordcirth has joined #nixos-aarch64
dayou has joined #nixos-aarch64
leonardp has joined #nixos-aarch64
lopsided98 has joined #nixos-aarch64
alienpirate5 has joined #nixos-aarch64
NickHu has joined #nixos-aarch64
sphalerite has joined #nixos-aarch64
{^_^} has joined #nixos-aarch64
qy[m]1 has joined #nixos-aarch64
dayou has quit [Quit: WeeChat 2.8]
zupo has joined #nixos-aarch64
<Valodim> hexa-: I got bluetooth working briefly when I looked at it. never looked at UART (and certainly not both at the same time ;)
Darkmatter66 has joined #nixos-aarch64
Darkmatter66_ has quit [Ping timeout: 250 seconds]
mvnetbiz_ has quit [Quit: Bye!]
mvnetbiz_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 256 seconds]
<hexa-> Valodim: got both working right now 🥳
<Valodim> yay :)
<hexa-> Valodim: just in case you can access your rpi3(?), do you have bluetooth enabled?
<hexa-> in which case I'd be interested if `bluetoothctl list` shows a controller
<hexa-> would be helpful input for the rpi wiki article section
<Valodim> can do when I'm home :)
<hexa-> thx
<hexa-> fwiw, this is what was needed to get it working on the rpi4 https://bpaste.net/PLFQ
<Valodim> yeah the btattach is also what I did to get it working. way nicer as a unit file!
zupo has joined #nixos-aarch64
Darkmatter66_ has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 258 seconds]
<colemickens> would nixos managing a dual boot of itself and stock android be a thing?
<colemickens> I guess maybe if Linux on mobile takes off the Android containery/whatever things might get good enough to suffice.
t184256 has left #nixos-aarch64 ["Error from remote client"]
<samueldr> managing a dual boot could in theory happen, but in practice I wouldn't see it working well
<samueldr> the main reason things like multiboot manager worked was that it exchanged security with convenience by using the userdata partition to hold the system files
<samueldr> if you have an encrypted userdata, it becomes harder to do
<samueldr> though it might still be possible
<samueldr> I think the boot.img would need to be aware of it
<samueldr> it's a really good question
<samueldr> hmm, newer devices with boot_as_recovery are less likely to work easily
<samueldr> as they skip the initramfs
<samueldr> so you need to have a custom boot image for the android system too
<samueldr> thinking more about it, I think the safest way for that to happen is if there is multirom boot manager type thing for your device
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<samueldr> and then we make sure Mobile NixOS can manage being a booted system
<samueldr> or, that someone implements in the Mobile NixOS stage-1 the requisite hooks to boot an android system
<samueldr> (probably using kexec)
orivej has quit [Ping timeout: 265 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zarel has quit [Quit: ZNC 1.7.4 - https://znc.in]
zarel has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo 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…]