| 3 Sep 2021 |
 samueldr | for the record it's upstream too:
https://android.googlesource.com/platform/system/sepolicy/+/master/private/boringssl_self_test.te | 18:25:42 |
 kranzes | 
Download image.png | 19:18:53 |
| kranzes | In reply to @danielrf:matrix.org
your configuration looks OK to me. Have you had any success building a working image for this device outside of robotnix? wish me luck | 19:18:57 |
|  dsx joined the room. | 20:13:33 |
| dsx | Hello everyone. I've build vanilla AOSP with robotnix (time nix-build "https://github.com/danielfullmer/robotnix/archive/master.tar.gz" --arg configuration '{ device="redfin"; flavor="vanilla"; apps.fdroid.enable = true; microg.enable = true; apps.seedvault.enable = true; apps.updater.enable = true; apps.updater.url = "https://ota.example.com/redfin/"; signing.enable = true; signing.keyStorePath = "/var/lib/keys/android"; }' -A releaseScript) and after following install instructions I get an boot loop. Am I missing some steps? | 20:16:43 |
| dsx | Passing keys directly to the build sandbox with … -A factoryImg --option extra-sandbox-paths /keys=/var/lib/keys/android doesn't help much either. | 20:18:02 |
| dsx | Build finishes without errors though. | 20:18:15 |
 danielrf | Looks OK to me. I know we have at least one other redfin user (I believe on grapheneos flavor), but I don't know if we have anyone else currently using redfin+vanilla | 20:48:58 |
| danielrf | If there is please let me know | 20:49:38 |
| danielrf | But this could be an issue with how the redfin kernel is built for the vanilla flavor | 20:50:08 |
| samueldr | general checks apply, maybe: was a factory reset tried? | 20:51:41 |
| danielrf | The two things I would try to test would be 1) using `flavor="grapheneos";` and 2) using upstream prebuilt kernel with `flavor="vanilla";` but `kernel.enable=false;` | 20:52:59 |
 cde | does it bootloop after showing the boot animation, or directly from the google logo? | 20:53:35 |
| kranzes | building android without robotnix is such a nightmare | 21:02:18 |
| kranzes | even when using a docker image | 21:02:24 |
| dsx |
general checks apply, maybe: was a factory reset tried?
It has never been used before, but after every failed try I re-apply stock image. I imagine it is as good as factory reset.
| 21:12:46 |
| dsx |
does it bootloop after showing the boot animation, or directly from the google logo?
Stuck between unlocked bootloader warning and google logo. No animation.
| 21:13:24 |
| dsx |
The two things I would try to test would be 1) using flavor="grapheneos"; and 2) using upstream prebuilt kernel with flavor="vanilla"; but kernel.enable=false;
- Building it now, it will take some 6 hours or so to do. Will report as soon as I get it work.
- I'll try that too.
| 21:14:15 |
| dsx | Is there a way to use more than 2 CPU cores for building? | 23:30:46 |
| danielrf | Try something like `--cores $(nproc)` on command line, or set `cores` in /etc/nix/nix.conf | 23:42:43 |
| danielrf | It definitely can use all your cores once the build gets going | 23:43:21 |
| dsx | Thanks! I'll try that on the next run | 23:47:10 |
| 4 Sep 2021 |
| kranzes | danielrf: | 01:32:35 |
| kranzes | * danielrf | 01:32:38 |
| kranzes | Guess what? it built the rom totally fine with the docker image | 01:32:52 |
| kranzes | and booted first try | 01:33:01 |
| kranzes | total 2.2G
drwxr-xr-x 2 kranzes users 4.0K Sep 4 04:33 .
drwx------ 57 kranzes users 280K Sep 4 04:33 ..
-rw-r--r-- 1 kranzes users 1.1G Sep 4 04:21 lineage-18.1-FORK-vanilla-20210903-2209-miatoll.zip
-rw-r--r-- 1 kranzes users 1.2G Sep 3 19:39 miatoll-ota_update-2021081022.zip
| 01:34:01 |
| danielrf | Hey great that's great for debugging at least! Could you post both built images somewhere that I can download to compare? | 01:34:16 |
| kranzes | 
Download image.png | 01:34:44 |
| kranzes | notice how they are a differnet size | 01:34:48 |
