Porting XOSP on Lineage device trees? - LeEco Le Max 2 Questions & Answers

Hello!
I have compiled Lineage for x2. Now I'm wondering if it would be hard to port new ROM (let's say XOSP) based on trees for other one. I heard, that it's hard to port CAF-based ROM (like XOSP is) on CM trees.
AFAIR @shivatejapeddi already tried to port XOSP to x2.
Can somebody tell me if it's possible to port ROM without deeper knowledge of AOSP guts? Or, maybe, where should I begin learning AOSP build process, if it's too hard for someone inexperienced?
Thanks!

---

remixn said:
Hello!
I have compiled Lineage for x2. Now I'm wondering if it would be hard to port new ROM (let's say XOSP) based on trees for other one. I heard, that it's hard to port CAF-based ROM (like XOSP is) on CM trees.
AFAIR @shivatejapeddi already tried to port XOSP to x2.
Can somebody tell me if it's possible to port ROM without deeper knowledge of AOSP guts? Or, maybe, where should I begin learning AOSP build process, if it's too hard for someone inexperienced?
Thanks!
Click to expand...
Click to collapse
if you compiled los from source then there is also source for xosp ( https://github.com/XOSP-Project/manifest ) anyway there is build of xosp ( https://androidfilehost.com/?w=files&flid=185291 ) anyway when i flashed it screen was blinking and i wasnt able even use phone.

---

kihope12 said:
if you compiled los from source then there is also source for xosp ( [ur l]h ttps : //gi thub.com/ XOSP-Project/m anifest[/ur l] ) anyway there is build of xosp ( [ur l]h tt ps :// an droidfilehost. com/? w=files&flid=185291[/u rl] ) anyway when i flashed it screen was blinking and i wasnt able even use phone.
Click to expand...
Click to collapse
Thank you for reply!
I already know that there is a build on AFH. I also know that there are sources for XOSP. In fact, I tried to compile XOSP using several slightly modified device trees (without success). When I was lurking across @shivatejapeddi's sources on GH, I saw that there is a modified display driver. That's one of things that make me curious.

---

Heyyo, eh tbh from what I've seen? It's not overly too hard. Please take a look at andr68rus dirty unicorns or his Paranoid Android which are both CAF based.
There's a chance that ROM might have a different CAF display than a different ROM (prevalent right meow in 8.1 custom ROMs such as LineageOS having a lot of changes whilst OmniROM is more of a minimal approach)

---

OK. Just compiled the ROM.
I'm surprised, that build process took only 20 minutes on old CPU.
Now, to the point. Flashed the ROM. Doesn't boot at all. Just freezes at bootloader screen (LeEco…). Make hasn't errored at all.
So, I have no idea, what should I do now…
UPDATE:
A kind of problem with RIL, I guess?

---

Hmm have you tried building with -eng build instead of userdebug or user to see if you can get ADB logcat via a PC and USB cable?
If you suspect it's RIL then yeah you could always try to swap it to CAF variant and delete the device specific variant or check what other devices on xosp use

---

remixn said:
OK. Just compiled the ROM.
I'm surprised, that build process took only 20 minutes on old CPU.
Now, to the point. Flashed the ROM. Doesn't boot at all. Just freezes at bootloader screen (LeEco…). Make hasn't errored at all.
So, I have no idea, what should I do now…
UPDATE:
A kind of problem with RIL, I guess?
Click to expand...
Click to collapse
only 20 minut? that is wierd, and RIL as i know (maybe i am wrong) is about singnal and sim, i dont think it can couse no boot, and you didnt event pass oem logo, you should try re-compile it maybe.

---

kihope12 said:
only 20 minut? that is wierd, and RIL as i know (maybe i am wrong) is about singnal and sim, i dont think it can couse no boot, and you didnt event pass oem logo, you should try re-compile it maybe.
Click to expand...
Click to collapse
Eh from my experiences with ROMs anything can cause issues. I've gotten bootloops from sensors and Bluetooth lol

---

kihope12 said:
only 20 minut? that is wierd, and RIL as i know (maybe i am wrong) is about singnal and sim, i dont think it can couse no boot, and you didnt event pass oem logo, you should try re-compile it maybe.
Click to expand...
Click to collapse
After recompiling it took ~40 mins. Still stuck on OEM logo :/

---

remixn said:
After recompiling it took ~40 mins. Still stuck on OEM logo :/
Click to expand...
Click to collapse
what edits of device tree you did?

---

kihope12 said:
what edits of device tree you did?
Click to expand...
Click to collapse
This is modified device tree: attps://github.com/remi6397/android_device_leeco_x2/tree/xosp-n-rebase
This is modified kernel: attps://github.com/remi6397/android_kernel_leeco_msm8996/tree/xosp-n-rebase
Modified LeEco vendor files are here: attps://github.com/remi6397/proprietary_vendor_leeco_x2/tree/xosp-n-rebase
Thank you!

---

remixn said:
This is modified device tree: attps://github.com/remi6397/android_device_leeco_x2/tree/xosp-n-rebase
This is modified kernel: attps://github.com/remi6397/android_kernel_leeco_msm8996/tree/xosp-n-rebase
Modified LeEco vendor files are here: attps://github.com/remi6397/proprietary_vendor_leeco_x2/tree/xosp-n-rebase
Thank you!
Click to expand...
Click to collapse
Man i am not dev, i just know very basic i can atleas give you xda thread where is how build rom from source

---

kihope12 said:
Man i am not dev, i just know very basic i can atleas give you xda thread where is how build rom from source
Click to expand...
Click to collapse
I've read several threads already. Also, I've changed only several makefiles. Nothing directly related to programming. Anyway, I'll try to fix something, then compile it again, and again…

---

remixn said:
This is modified device tree: attps://github.com/remi6397/android_device_leeco_x2/tree/xosp-n-rebase
This is modified kernel: attps://github.com/remi6397/android_kernel_leeco_msm8996/tree/xosp-n-rebase
Modified LeEco vendor files are here: attps://github.com/remi6397/proprietary_vendor_leeco_x2/tree/xosp-n-rebase
Thank you!
Click to expand...
Click to collapse
Heyyo, it's the kernel. That's the AOSPA Le Pro3 kernel that is made by GalaticStryder that isn't ported to the Le Max2 yet. I tried but ran out of personal time... It would require quite a bit of work to get functional for the Le Max2. Boot DTS files, firmware, missing drivers and so on.
Also, andr68rus based ROMs are not EAS compatible just in case that's something you really want.
I'd recommend using this kernel instead:
https://github.com/1nfrag/android_kernel_leeco_msm8996/tree/bsi?files=1
Or if you want EAS based kernel I'd recommend checking out SlimRoms For EAS compatible device tree, kernel and vendor blobs.
https://github.com/slim-x2
Sorry I should have been a little more specific with my information on that first post. My bad.

---

Ok… I've got several errors on boot, mainly from surfaceflinger.
Log: https://pastebin.com/sXDB1u0Y
Vendor: attps://github.com/slim-x2/proprietary_vendor_leeco-2
Device tree: attps://github.com/slim-x2/android_device_leeco_x2-old
----
Now I'm trying with device: attps://github.com/slim-x2/android_device_leeco_x2 + attps://github.com/slim-x2/device_leeco_msm8996-common
I've got a compile error:
Code:
ninja: error: '/home/remi/android-buildenv/xosp/out/target/product/x2/obj_arm/SHARED_LIBRARIES/libsrsprocessing_intermediates/export_includes', needed by '/home/remi/android-buildenv/xosp/out/target/product/x2/obj_arm/SHARED_LIBRARIES/libaudioflinger_intermediates/import_includes', missing and no known rule to make it
or without SRS_TRUEMEDIA:
Code:
ninja: error: 'vendor/leeco/x2/proprietary/vendor/etc/audio_output_policy_letv.conf', needed by '/home/remi/android-buildenv/xosp/out/target/product/x2/system/vendor/etc/audio_output_policy_letv.conf', missing and no known rule to make it

---

Heyyo, @moto999999 can you please give him some directions as to which branches he should be using?
I better play it safe and ask him directly just to help things along

---

Ok. Now it boots… and almost works (it even makes a sound ). System dies leaving a huge amount of logs behind itself:
Here is an important part (IMO):
Code:
--------- beginning of crash
06-20 13:41:46.873 1629 1629 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
06-20 13:41:46.873 1629 1629 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: library "libgnsspps.so" not found
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:989)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1562)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.qualcomm.location.izatserviceprovider.service.IzatServiceBase.<clinit>(IzatServiceBase.java:199)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at java.lang.Class.newInstance(Native Method)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:3198)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.app.ActivityThread.-wrap5(ActivityThread.java)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1586)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.android.server.SystemServer.run(SystemServer.java:378)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.android.server.SystemServer.main(SystemServer.java:232)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
So… There is a missing GPS blob (GLONASS?). I will try stealing that from some other device.

---

ThE_MarD said:
Heyyo, @moto999999 can you please give him some directions as to which branches he should be using?
I better play it safe and ask him directly just to help things along
Click to expand...
Click to collapse
Sure, always happy to help
remixn said:
Ok. Now it boots… and almost works (it even makes a sound ). System dies leaving a huge amount of logs behind itself:
Here is an important part (IMO):
So… There is a missing GPS blob (GLONASS?). I will try stealing that from some other device.
Click to expand...
Click to collapse
Are you trying to build nougat or oreo?

---

moto999999 said:
Are you trying to build nougat or oreo?
Click to expand...
Click to collapse
Nougat.
Now compiled with your slim device tree forked from LineageOS. It was a huge amount of work (never tried something like that before ) Everything I've tested so far works fine. I need to make some more tests, but maybe tomorrow.
PS: Thank you for your contributions to this device tree.

---

remixn said:
Nougat.
Now compiled with your slim device tree forked from LineageOS. It was a huge amount of work (never tried something like that before ) Everything I've tested so far works fine. I need to make some more tests, but maybe tomorrow.
PS: Thank you for your contributions to this device tree.
Click to expand...
Click to collapse
You should use this tree https://github.com/slim-x2/android_device_leeco_x2-old
Kernel https://github.com/moto999999/kernel_leeco_msm8996 (nougat branch)
Vendor https://github.com/slim-x2/proprietary_vendor_leeco
I don't recommend that you use my tree forked from lineage, it isn't the one I use. The forked one was just for testing