[device-port] [aries] Sony Xperia Z3C

[ghost]

This port is broken. It worked a year ago. Can't build system image. Too many files are missing.

Progress:

• [ ] Boot image and system image build successfully
• [ ] Device boots into rootfs, usb: Manufacturer: GNU/Linux Device appears in dmesg on host.
• [ ] LXC container starts and does not crash
• [ ] libhybris tests
  • [ ] test_gps
  • [ ] test_hwcomposer
  • [ ] test_lights
  • [ ] test_vibrator
  • [ ] test_wifi
  • [ ] test_sensors
  • [ ] test_audio
  • [ ] test_camera
  • [ ] test_input
  • [ ] test_nfc
  • [ ] test_recorder

https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_z3c https://wiki.postmarketos.org/wiki/Sony_Xperia_Z3C_(sony-aries)

[lnjX]

The part with the signapk.jar doesn't sound correct. Try to remove everything of Java / APKs from the makefiles (you can fork the repos and publish your changes).

---

Ok the signapk thing is a general problem, but better comment out the lines in the vendor makefile, so that the apks are not added to the systemimage (we don't need them).

And you can fork the kernel repo and change the defconfig there on a halium-7.1 branch :)

[lnjX]

Please try with my new manifest: https://github.com/Halium/halium-devices/blob/halium-7.1/manifests/sony_z3c.xml For me it works fine!

[ghost]

Thank you. I'll start over again with an empty build directory and report the results. If it works for you it should also work for me.

[lnjX]

I'm just curious, did you already have time to test it on the device?

[lnjX]

That bug is not related to the manifest, it's something in your halium checkout. 😐 I'm not really sure if that helps, but have you tried recloning?

[ghost]

Got another error when running the halium-install script. It's memory related. On my device I got 1G RAM free before but only 40M when it fails.

/file_contexts: line 588 error due to: Out of memory mmap: Out of memory

[lnjX]

You need at least 2GB free disk space on the data partition. You can also format the partition.

[lnjX]

Why should the recovery need more than 3GB RAM? - Even the uncompressed image is only 2GB ...

[ghost]

Wait. I monitored storage space, cpu load and RAM on the phone during script execution. Free RAM was 1GB before but only 40MB when the script failed. The /data partition had enough free space the whole time.

[lnjX]

Which script do you use? The official or the @JBBgameich's one?

[ghost]

First I tried the official one. Then JBB's AppImage but I got the same error with both of them.

[lnjX]

Strange ... Is there another recovery system for your device available? Or try pushing it on your los/android system (you'll need some changes to the scripts)?

[lnjX]

The out of memory error could be caused by this: https://github.com/Halium/halium-scripts/pull/5

Try installing using the modified version of the script.

[ZeroPointEnergy]

It seams the /recovery partition is not present/mounted in recovery mode on every device hence it probably writes to a ramdisk. I modified it to use /sdcard to make it work for the Samsung Galaxy S7 since that is the directory Lineage OS uses. But I have no idea if this is a mounted partition on all devices.

https://github.com/ZeroPointEnergy/halium-scripts/commit/12a2d5d52d13e88489b34282da0bfe7bc5741212

[ghost]

Thank you for the scripts. I tried both versions but got the same error on my phone. Then I installed another version of TWRP (3.0.2-1) and it worked. So it was a TWRP problem.

[ghost]

This port is broken. I get plenty of build errors with system image.