Build-lineageos-sargo icon indicating copy to clipboard operation
Build-lineageos-sargo copied to clipboard

Pointers on building for Pixel/sailfish and a boot loop

Open eike-fokken opened this issue 5 years ago • 1 comments

Thanks for the repo!

I tried to build lineage 17.1 for the Pixel/sailfish and based my efforts on this repo.

I cloned your repo and used this command to build:

docker run \
       -e "BRANCH_NAME=lineage-17.1" \
       -e "DEVICE_LIST=sailfish" \
       -e "INCLUDE_PROPRIETARY=false" \
       -e "CLEAN_AFTER_BUILD=false" \
       -e "SIGN_BUILDS=true" \
       -e "SIGNATURE_SPOOFING=restricted" \
       -e "SUPPORT_UNIFIEDNLP=true" \
       -e "BOOT_IMG=true" \
       -e "CUSTOM_PACKAGES=GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend com.google.android.maps.jar FDroid FDroidPrivilegedExtension" \
       -v "$PWD/src:/srv/src" \
       -v "$PWD/zips:/srv/zips" \
       -v "$PWD/logs:/srv/logs" \
       -v "$PWD/ccache:/srv/ccache" \
       -v "$PWD/local_manifests:/srv/local_manifests" \
       -v "$HOME/.android-certs:/srv/keys" \
       solidhal/docker-lineage-cicd

the key difference is that I don't supply any user scripts as I thought that they probably are device specific.

The build went through but then on first boot the phone told me constantly that

Settings app keeps crashing, stop it or wait

I guess you know what kind of dialog I mean. Therefore my question is: Is this the kind of boot loop that should be prevented by the patch in the before user-script? If not, is any of the built-in apps known to cause issues?

Thanks for your work, it started me on trying to build my own lineage!

eike-fokken avatar Jun 24 '20 07:06 eike-fokken

I have no experience building for sailfish, but it should just work... Maybe try not building in any custom packages? You are correct though that the user scripts are specific to sargo. Very possibly a bug in lineageos-17.1 as well, you could try asking in their IRC

SolidHal avatar Aug 08 '20 07:08 SolidHal