Progress update: I managed to get Bluetooth working, currently investigating ways on how to enable audio support.
Out-of-the-box ALSA-only audio seems to be further away than anticipated.
If anyone with a Sony Xperia X (single- or dual-SIM) would like to help, contributions are welcome. :)
@yamiyukisenpai said in Help building Halium for International Galaxy S4 (jfltexx):
I think the actual error is the line right after what you quoted and I think that means you miss something in your manifest. Did you use this one: https://github.com/Halium/projectmanagement/issues/59 if not, why not and share it/the difference to #59
Well, @doniks, I have tried creating files of various sizes with dd and doing an adb push with them, and there are some results:
-Images of 1 GB or 1,5 GB are not created by an error of insufficient space in halium-install
-Images of 2 GB or more are created but when I try to push it to the phone vía adb push (filename) /data it gives me an error of not enough partition size.
I have tried it not only with Ubuntu Touch images, also with Plasma Mobile rootfs and Halium reference rootfs.
If your sources have the file init.qcom.rc, with this line:
export LD_SHIM_LIBS /system/lib/libril.so|libril_shim.so:/system/lib/libcrypto.so|libboringssl-compat.so
try change this to
export LD_SHIM_LIBS /system/lib/libril.so|libril_shim.so
build system.img and install again.
I do not think this will work since Ubuntu Touch uses not a standard way of building it. Its also not a "ROM" since its loaded to the phone in a different way.
Also we do not support Android 8.1 at the moment...
could a virtual trackpad be added?
@zzarr generally speaking, I think anything is possible if someone with the necessary knowledge and skills wants to improve something in UT :) but I don't know the technical requirements of that to give you an specific answer
@bluekenny I got KDE Plasma Mobile working with this kernel patch! I think Ubuntu Touch is broken with Halium 7.1, and CAF devices atm, though.
To merge the patch, cd into the kernel directory, and run curl https://github.com/Halium/android_kernel_oneplus_msm8996/commit/3e019b8700b36aef379846a748e3a447a8c3dbe7.patch | patch -p1
Really!? More crossposting?
Also it seems everytime you crosspost in a new place you give less information. If this is meant as a followup it needs a summary and references to what has happened earlier. But you give nothing.
Just to give an answer here which might or might not help. Ignore:
recovery.fstab - probably only used for recovery, and will not be needed for porting. The recovery make step will do the same for UBports recovery as for Android recovery, so if it is needed, it will be placed in the right place.
charger.fstab - In charger mode there is also a little Android running, it will pick this up from the regular build, see before
the common and aosp.common, try to look at their differences. And try to go with the common one first ;)
Looks like your connection to UBports Forum was lost, please wait while we try to reconnect.