Building this ROM

[Ethanol10]

Hi there, I was attempting to follow ponces guide on how to build a GSI to get a start on modifying this one, however I'm hitting an issue where it can't find default.xml in the main root of the project, is that usual?

[Ethanol10]

To be clear, i'm at step 6 on this page: https://github.com/phhusson/treble_experimentations/wiki/How-to-build-a-GSI%3F

where it's trying to clone the repo from lineageOS, I replaced the URL with the git link here, but to no avail.

[Archfx]

Just use the steps in the treble_experiementation to familiarize yourself with building AOSP since it is a bit outdated now. Once you do that, you will see the similarities in the build.sh and the above steps.

• build.sh automates the entire process, but you have to fix any patch-related issues if exist (using git patch).
• You can create your own public-private key pair to sign the release versions. Steps are here
• Finally, you will need a Linux machine with at least 24GB RAM with 24GB Swap and about 400GB of Disk space with a bit of patience.

Good luck, I hope to see some contributions in the future.

[Ethanol10]

In the meantime, I was wondering how to interface with the pen charger on SD2, I can't seem to follow any SDKs that contain information on this. Do you have an idea on where to look @Archfx ?

[Archfx]

Unfortunately, publicly available content is not that helpful. You have to rely on reverse engineering based on the contents from here.

• Surface duo SDK
• Duo kernel

Thai-ng was very helpful in most of the cases since he worked on the device at Microsoft. However, there were several cases where things were not working as expected with the TD patches (which make the AOSP backward compatible with old kernel devices).

[Ethanol10]

I got the build script running but I've hit a wall with gradle:

--> Building treble_app

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

is this just a matter of downgrading gradle?

[Archfx]

You can ignore the gradle version warnings.

[Ethanol10]

Is there a way to build this into an app to deploy? I would like to test changes but unsure on the build process for this system service:
https://github.com/Archfx/duoPosture

[Archfx]

Yes, you can build using the build.sh, but you can't test the display and other changes without persistent setting in the build file. Since all the production images are signed, you can't replace a persistent app.

One option would be to remove the persistent settings, change the package name to another, and use log files to debug the functionality. Compile, install, and observe the logs working as described. Once done we can move the changes back to the original repo.

If you want to test the app as it is, we have to use eng mode builds instead of userdebug. Then you can replace the persistent mode apps with new ones using adb.