H11: Fix new location for biometryd #79
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This allows for easier modification of the manifest. Change-Id: I0c31884ace61561578c8dfbbb37c74db68c54358 Signed-off-by: Alexander Martinz <alex@amartinz.at>
Change-Id: Iddf5885c75c7e8cd8de6dc5425380bb170e43a41
Change-Id: Icb7af23d3f80c266760e356315f5b07296803e9f
Change-Id: I78b9b7ff7cd5aabf9928f8451b70775f82dabbd7 Signed-off-by: Alexander Martinz <alex@amartinz.at>
To be used for vndkservicemanager in case that comes from stock vendor partition.
Use the ubports recovery instead of the straight lineage-17.1 fork and add external/gpg to get a static gpg binary, which is used by the recovery to verify system updates. Change-Id: I845a2f91d75581eeb55d4e956ee6ebf6873ac5ab Signed-off-by: Alexander Martinz <alex@amartinz.at>
Upstream 1dbd7dd Change-Id: I5709abb407b5ff8a16d0ce64e697539e821e183f Signed-off-by: Alexander Martinz <alexander@ubports.com>
halium: track lineage's external/aac for ASB 2022-06
Issue: HALXI-2 Change-Id: Ibfed89df08b373da42dda19a09cd45b82db8eb69 Signed-off-by: Alexander Martinz <alexander@ubports.com>
snippets: halium: pin droidmedia to a working revision
In SailfishOS, gst-droid is built against droidmedia-devel which is provided by the adaptation-common repository. In the current (4.4) release of Sailfish, droidmedia is expected to be 0.20211101.0. Because on Halium, droidmedia is provided by the halium rootfs, the version must match the version in the current release because changes in the headers used to build gst-droid may result in crashes if there is a mismatch. I would like to keep the version used in Halium in line with the current released SailfishOS version to minimise problems. I dont think there are currently any other users of droidmedia and gst-droid so this should have minimal impacts.
| @@ -10,7 +10,7 @@ | |||
| <linkfile src="." dest="halium/devices" /> | |||
| </project> | |||
| <project path="vendor/halium/audioflingerglue" name="Halium/audioflingerglue" revision="master" /> | |||
| <project path="vendor/halium/biometryd" name="ubports/core/biometryd" revision="ubports/xenial_-_android9" remote="gitlab" /> | |||
| <project path="vendor/halium/biometryd" name="ubports/development/core/biometryd" revision="ubports/xenial_-_android9" remote="gitlab" /> | |||
There was a problem hiding this comment.
Now the branch should be main for 20.04 and similar changes should also be reflected in platform-api repo below.
#80 probably should also be updated along with Halium 9 and 12 getting PRs (should I submit those?) to do similar changes and hopefully merge all around the same time as they'll likely need manual intervention to fix repo sync after URL/branch change.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Needed change after our restructuring