<danielrf[m]>
hmenke had this problem, but only when using a signed version of the build
<matthewcroughan>
danielrf[m]: I just end up with Update requires 'TZ.BF.2.0-2.0.0109' or 'TZ.BF.2.0-2.0.0123' or 'TZ.BF.2.0-2.0.0134'. if I try to use the IMG
<matthewcroughan>
previously I tried to flash the ZIP
<matthewcroughan>
`Device version-trustzone is ''.`
<danielrf[m]>
Perhaps try flashing the recovery from robotnix first
<matthewcroughan>
what recovery is it?
<matthewcroughan>
twrp?
<danielrf[m]>
just the standard one from a lineageos build
<danielrf[m]>
instead of using `-A ota` on your earlier build command, use `-A recoveryImg`
<matthewcroughan>
dam
<matthewcroughan>
danielrf[m]: Is the recovery inside the IMG not okay?
<matthewcroughan>
I see a recovery.img inside
<danielrf[m]>
nvm about using `-A recoveryImg`, I never set that up properly
<matthewcroughan>
I kinda want to keep my twrp also
<matthewcroughan>
I've just tried `fastboot lfash system system.img
<matthewcroughan>
danielrf[m]: It does in fairness get to the lineageOS splash screen
<matthewcroughan>
oh, interesting, it boots when I flash the system image raw
<danielrf[m]>
Hmm, interesting
<matthewcroughan>
bluetooth stopped working though
<danielrf[m]>
and flashing recovery first is the only thing that might have contributed
<danielrf[m]>
but hey, if it's working for you now, great!
<matthewcroughan>
yeah but what if I want to keep twrp?
<matthewcroughan>
oh no, you're misreading the instructions I believe
<matthewcroughan>
they're just telling you to make sure there's a recovery that isn't the default one on the device first.
<danielrf[m]>
even though I've been using nix for a while, I'm always a little amazed that "builds just work" :)
<danielrf[m]>
reflash twrp after, I suppose?
<matthewcroughan>
danielrf[m]: me too :D
<ajs124>
in my experience. depending on the device, the instructions in the lineageos wiki are borderline dangerously wrong
<ajs124>
as in, I literally soft-bricked my payton, because I followed them instead of the XDA thread -.-
<danielrf[m]>
yeah, unfortunately, pixel phones are the only ones I"m confident about
<danielrf[m]>
and with how much variation there is across android devices, I'm hesitant to give strong recommendations for other devices
<ajs124>
yeah. They all seem to be templated and the maintainers don't seem to edit them. It's kind of weird.
<matthewcroughan>
apps.updater is the craziest abstraction I have ever seen in my entire life danielrf[m]
<matthewcroughan>
My jaw is on the floor
<danielrf[m]>
Haha thanks. You'll be less impressed when you realize there isn't any lineageos updater integration yet :(
<danielrf[m]>
But in principle that shouldn't be too hard to figure out
<ajs124>
did I ever dig up and give you the things on the json(?) they expect on the server?
<danielrf[m]>
I remember seeing them in nixdroid
<ajs124>
yeah, they're in there somewhere. apparently for the url, you set lineage.updater.uri (or did on android 9 or 10 or whatever I was building, at least).
<matthewcroughan>
danielrf[m]: is there any real benefit to using LineageOS
<ajs124>
maybe I should just try and add those two things to robotnix, it really doesn't seem like much
<danielrf[m]>
matthewcroughan: from my perspective, just the number of supported devices. But other than that, the functionality of vanilla android is sufficient for me.
<matthewcroughan>
danielrf[m]: what do you use for maps?
<matthewcroughan>
going to guess OsmAnd
<danielrf[m]>
yep
<danielrf[m]>
although with covid, I haven't really used maps as much as otherwise
<matthewcroughan>
danielrf[m]: heh, can you provide the source code for android apps you want to bake in, with robotnix?
<danielrf[m]>
Sure, the `apps.prebuilt.<name>.apk` option allows you to specify the apk to include
<danielrf[m]>
and that apk can be built however
<matthewcroughan>
OMG
<matthewcroughan>
yeah, so in order to do this with APKs, you'd need to do what exactly? Have a git LFS module?
<matthewcroughan>
because the apks could get large
<danielrf[m]>
In fact, some of the other apps like `apps.fdroid` or `apps.seedvault` are implemented using the `apps.prebuilt.<name>.apk` option
<matthewcroughan>
Wow, those simple apps are getting good
<matthewcroughan>
danielrf[m]: How would I generate aosp for my phone ? How do I know if it would work? etc
<matthewcroughan>
and would it be aosp11? How do I set the version I want to generate?
<danielrf[m]>
you mean vanilla aosp?
<danielrf[m]>
Robotnix currently only supports pixel phones for vanilla aosp
<danielrf[m]>
Presumably if you wanted to make a vanilla aosp for another phone you'd have to ensure the device source dirs are included in the build and then just set the `device` and `flavor` options correctly
<matthewcroughan>
danielrf[m]: are there any examples of non-pixel phones in robotnix at the moment?
<matthewcroughan>
what does it mean to "include" them in the build?
<danielrf[m]>
Not currently, just the ones for lineageos
<matthewcroughan>
you mean like the device's kernel and device tree?
<danielrf[m]>
Yep
<matthewcroughan>
so just those two things, you think?
<danielrf[m]>
you'd set the `source.dirs` option to ensure those repos are included
<danielrf[m]>
depends on the device, but at least those
<danielrf[m]>
they might have their own dependencies
<danielrf[m]>
for an end-user it'd also be nice to have the stuff to generate the vendor image as well
<danielrf[m]>
For lineageos device this comes the TheMuppets repos
<danielrf[m]>
and for pixels it's generated from the upstream factory images via "android-prepare-vendor"
ajs124 has quit [Ping timeout: 240 seconds]
ajs124 has joined #robotnix
<samueldr>
>> Update requires 'TZ.BF.2.0-2.0.0109' or 'TZ.BF.2.0-2.0.0123' or 'TZ.BF.2.0-2.0.0134'
<samueldr>
to me that sounds like you need to update parts from the vendor
<samueldr>
e.g. boot partition or modem partition
<danielrf[m]>
Robotnix-compiled boot partition should be available by building with `-A bootImg`