[UNOFFICIAL BUILD] (Updated) Sony Xperia XZ1 Compact (lilac) e-1.5.1-s-20221110

/e/OS Devices UnOfficial Builds
121

Downlaod secure & flash e-recovery onto your device:

fastboot flash recovery recovery.img
122

Any chances for further updates on this ROM @ronnz98 ?
Maybe even to Android 14? There is a LOS 4 microg build for that already…
Would be awesome, such a great little device, theres really nothing like it if you want a small but smart phone!

1 Like
123

At the moment the upstream lineage-21 / Android 14 does not build. Work is needed from the maintainer before new builds can be made.

124

Hi Pete,

do you refer to this sources?
https://xdaforums.com/t/rom-lineageos-21-0-unofficial-1-1-2024-06-16.4658694/

1 Like
125

Yes. I use the sources linked in that thread, and others by the same github user, to make builds (los4microg, IodéOS) for lilac and the other Sony devices that use the Yoshino platform (poplar, maple). I believe the needed changes are in the ‘yoshino-common’ source tree.

1 Like
126

Hi there gentle people for XZ1 Compact.

  • Would there be some (step-by-step) documentation to create new UNOFFICIAL builds for /e/os for this mobile?

  • What are the hints to know? How long takes a build on a regular PC?

  • Which Q/S version would be the most stable and recommended to start with?

Thank for your info!

127
128

@piero Thanks for the link!
Only, there is nothing about the XZ1 on the Muppets link:

(is it actually a safe source ?)

@petefoth Would you eventually have a step by step/command lines guide to your Builds? So someone could take the relay on /e/os builds for XZ1 Compact.

+ Have anyone tried U (\https://gitlab.e.foundation/e/os/android.git -b v1-u) on XZ1 Compact?
I wonder also the advantages to be upstream with Android (U vs. Q/R/S/T) ; I just want a MultiUser/Secured phone that can take photos and run major apps.

+ Newbie question: Is it possible to upgrade the build, without loosing all OS parameters and Apps/content? Or a full backup of everything is needed and settings need to be reapplied?

1 Like
129

I don’t have a step-by-step guide, but as far as I know, it should be straightforward using the /e/ Docker Image,

No need to mess around trying to extract proprietary blobs: the following manifest will pick up everything you need to build /e/OS for XZ1 Compact lilac(as well as XZ1 poplar & polar_dsds and XZ Premium maple(including binary blobs as well as device and kernel sources). It’s the manifest I use to build LineageOS for microG 21.1 and IodéOS 5 for these devices.

Good luck!

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
      <!-- kernel -->
      <project name="whatawurst/android_kernel_sony_msm8998" path="kernel/sony/msm8998" remote="github" revision="lineage-21" />

      <!-- device trees -->
      <project name="whatawurst/android_device_sony_yoshino-common" path="device/sony/yoshino-common" remote="github" revision="lineage-21" />
      <project name="whatawurst/android_device_sony_maple" path="device/sony/maple" remote="github" revision="lineage-21" />
      <project name="whatawurst/android_device_sony_maple_dsds" path="device/sony/maple_dsds" remote="github" revision="lineage-21" />
      <project name="whatawurst/android_device_sony_poplar" path="device/sony/poplar" remote="github" revision="lineage-21" />
      <project name="whatawurst/android_device_sony_poplar_dsds" path="device/sony/poplar_dsds" remote="github" revision="lineage-21" />
      <project name="whatawurst/android_device_sony_lilac" path="device/sony/lilac" remote="github" revision="lineage-21" />

      <!-- binary blobs  -->
      <project name="whatawurst/android_vendor_sony_maple" path="vendor/sony/maple" remote="github" revision="lineage-21" />
      <project name="whatawurst/android_vendor_sony_maple_dsds" path="vendor/sony/maple_dsds" remote="github" revision="lineage-21" />
      <project name="whatawurst/android_vendor_sony_poplar" path="vendor/sony/poplar" remote="github" revision="lineage-21" />
      <project name="whatawurst/android_vendor_sony_poplar_dsds" path="vendor/sony/poplar_dsds" remote="github" revision="lineage-21" />
      <project name="whatawurst/android_vendor_sony_lilac" path="vendor/sony/lilac" remote="github" revision="lineage-21" />
      <project name="whatawurst/android_vendor_sony_yoshino-common" path="vendor/sony/yoshino-common" remote="github" revision="lineage-21" />
      <project name="TheMuppets/proprietary_vendor_sony_tama-common" path="vendor/sony/tama-common" remote="github" revision="lineage-21" clone-depth="1" />
      <project name="TheMuppets/proprietary_vendor_sony_xz2c" path="vendor/sony/xz2c" remote="github" revision="lineage-21" clone-depth="1" />
 
</manifest>

Firstly you will need a machine (real, virtual, or in the cloud) running Linux. I use Linux Mint, LineageOS for microG uses Debian, and recent versions of Ubuntu should work.

Building locally, on an 2011 Macbook Pro with 2.3GHz Intel Core i5, 16GB RAM and a 2TB SSD takes around a day and a half. Much easier to use a machine in the cloud, from e.g. Krystal, OVH or Vultr. A VM with 48 or 64 vCPUs and 48-72 GB RAM should complete a build in 2.5-5 hours. and cost around €5. Many cloud providers have introductory offers with a certain amount of free credit, so your first builds will cost even less.

2 Likes