[ROM][UNOFFICIAL][PIE][ALPHA] LineageOS 16.0 for BQ Aquaris X5 plus (gohan)

Search This thread

urobbot

Senior Member
Nov 14, 2012
112
70
Milan
I also saw before in your earlier post that you've had GPS not working on 16, which made me think twice before testing this ROM... Do you have now a list of major bugs on your latest release?

On the earlier post I said that GPS was not working because I had disabled it to compile the ROM.
At the moment we don't have a booting rom on Oreo or Pie, but we will post here once we have one!
 

AndDiSa

Senior Member
Dec 2, 2009
3,701
5,074
Heidelberg
HTC Desire
Nexus 7
@matador-2 @urobbot sorry, it took a bit longer before I was able to start on developing / updating the kernel sources for gohan. I am still in the work on merging the upstream kernel but this time getting commit by commit from the upstream repo. Currently I have successfully updated the kernel sources up to 3.10.95 The branch is cm-14.1-updated ...

I was able to successfully build and to successfully boot Lineage-14.1 with the current version of the kernel. I'll try to move on the next days / weeks to get the rest of the upstream kernel merged, too.
 
  • Like
Reactions: Matador-67

Matador-67

Member
Dec 22, 2013
41
8
Yes the new Kernel ist running in my last 14.1 build.

Gesendet von meinem Aquaris X5 Plus mit Tapatalk
 

urobbot

Senior Member
Nov 14, 2012
112
70
Milan
Thank you @AndDiSa for your effort on the kernel for Aquaris X5 Plus.
What do you mean on merging the upstream kernel? by upstream I guess you mean mainline kernel right?
Can you explain give a little more detail on the work you are doing?
 

Matador-67

Member
Dec 22, 2013
41
8
We have a .108 Kernel running, since Yesterday you can find it at GitHub Moosburger/android_kernel_bq_msm8976.
Please contribute @moosburger a thanks for this.

Gesendet von meinem Aquaris X5 Plus mit Tapatalk
 
Last edited:
  • Like
Reactions: AndDiSa

AndDiSa

Senior Member
Dec 2, 2009
3,701
5,074
Heidelberg
HTC Desire
Nexus 7
Thank you @AndDiSa for your effort on the kernel for Aquaris X5 Plus.
What do you mean on merging the upstream kernel? by upstream I guess you mean mainline kernel right?
Can you explain give a little more detail on the work you are doing?

yes, I mean the mainline kernel and I am currently merging all commits missing in cm-14.1 from the mainline as that cm-kernel was on 3.10.85 only while mainline finished at 3.10.108.
After this is finished, the kernel should have all the security issues / bugs patched which were known when the kernel went EOL (November 2017). In addition so it's more easy if you want to backport features / patches which are released to newer kernels.

Btw.: a few moments ago I pushed the current state of the cm-14.1-updated kernel , updated until 3.10.108, too.
 

jmpf_bmx

Senior Member
Thank you @AndDiSa for your effort on the kernel for Aquaris X5 Plus.
What do you mean on merging the upstream kernel? by upstream I guess you mean mainline kernel right?
Can you explain give a little more detail on the work you are doing?

Hi,
@urobbot, one friend is helping on the development of x5 plus and we have an oreo kernel and device tree.
I think if i can work on it and my friend can will be available on the next days
 
Last edited:
  • Like
Reactions: AndDiSa

urobbot

Senior Member
Nov 14, 2012
112
70
Milan
Hi,
@urobbot, one friend is helping on the development of x5 plus and we have an oreo kernel and device tree.
I think if i can work on it and my friend can will be available on the next days

Hi @jmpf_bmx, that's great news!
Is the resulting ROM booting yet?
Would you mind uploading the kernel and device tree to github so other can contribute to bugfixing?
 

AndDiSa

Senior Member
Dec 2, 2009
3,701
5,074
Heidelberg
HTC Desire
Nexus 7
I think I found the repo you are refering to: https://github.com/Maanush2004/android_device_bq_gohan and https://github.com/Maanush2004/android_kernel_bq_msm8976. I saw it already some time ago but I was not sure about the state. Today I tried that kernel together with cm-14.1 ... it's booting, but unfortunately fingerprint sensor is not working. I suppose it's related to some commit regarding the binder adaptations as I tried to add the commits from Maanush to my kernel, too, and also in that case the fingerprint sensor was not working.
There is also the chance that the fingerprint libs are incompatible to the newly defined binder devices ... analyzing that needs a bit time.

Edit: looks like ther are permissions missing after moving to multiple binder devices
 
Last edited:

AndDiSa

Senior Member
Dec 2, 2009
3,701
5,074
Heidelberg
HTC Desire
Nexus 7
@urobbot what is the current state of your work?
I have a kernel with binder devices support (which is a precondition for Android 8+) which is booting on cm-14.1 fine. I have an adapted device tree for lineage 15.1 and the build goes through. Unfortunately I am not able to boot, it's stuck in a bootloop :(
I suppose it's related to sepolicy / file_context / ... but currently I have no idea how to get some additional light into the dark.
 
  • Like
Reactions: Matador-67

Matador-67

Member
Dec 22, 2013
41
8
Hello @AndDiSa,

can you please Share your Sources? You know i am looking for a working Tree too.
May be we can find the Solution together.

Gesendet von meinem CMR-W09 mit Tapatalk
 

AndDiSa

Senior Member
Dec 2, 2009
3,701
5,074
Heidelberg
HTC Desire
Nexus 7
@matador-2 sure, I'll upload the current state to my repo and will give you a ping when it's done.
---------- Post added at 08:48 AM ---------- Previous post was at 08:12 AM ----------

[/COLOR @matador-2 I just pushed my current version to github.
The kernel souces can be found here: https://github.com/AndDiSa/android_kernel_bq_msm8976/tree/lineage-15.1. This kernel is booting on cm-14.1, too, but you need additional permissions to keep the fingerprint sensor working:
1) https://github.com/AndDiSa/android_device_bq_gohan/commit/4a1c64c3d14bcd06e2c99a18579c58d0888e63ff
2) https://github.com/AndDiSa/android_device_bq_gohan/commit/f75504869403439d2ac4882d1842035bc68c7f2c

The current device tree can be found here: https://github.com/AndDiSa/android_device_bq_gohan/tree/staging
I was trying to align with the device tree from https://github.com/LineageOS/android_device_leeco_s2 which has a working Lineage-16.0 build and has almost the same specs as our device.
 
Last edited:
  • Like
Reactions: datecasp

Matador-67

Member
Dec 22, 2013
41
8
Hi @AndDiSa ,

I had a look in BoardConfig.mk i think there is a Line missing:
TARGET_USES_32_BIT_BINDER := true

This is Like the Line in S2 Repo: TARGET_USES_64_BIT_BINDER := true.





Gesendet von meinem CMR-W09 mit Tapatalk
 
  • Like
Reactions: AndDiSa

AndDiSa

Senior Member
Dec 2, 2009
3,701
5,074
Heidelberg
HTC Desire
Nexus 7
Hi @AndDiSa ,

I had a look in BoardConfig.mk i think there is a Line missing:
TARGET_USES_32_BIT_BINDER := true

This is Like the Line in S2 Repo: TARGET_USES_64_BIT_BINDER := true.





Gesendet von meinem CMR-W09 mit Tapatalk
Good hint, I'll try to build with this entry.

I am a bit further: it's not a bootloop, but boot is stopped completely, I suppose when data needs to be decrypted:

Code:
08-19 09:00:01.890   362   362 E hwservicemanager: BINDER_SET_INHERIT_FIFO_PRIO failed with error -1
08-19 09:00:01.935   364   376 E vold    : Failed to chmod /data/system_ce/0: No such file or directory
08-19 09:00:01.935   364   376 E vold    : Failed to chmod /data/misc_ce/0: No such file or directory
08-19 09:00:01.935   364   376 E vold    : Failed to chmod /data/media/0: No such file or directory
08-19 09:00:02.151   400   400 E QSEECOMD: : Listener: index = 0, hierarchy = 0
08-19 09:00:02.155   406   406 E PerMgrProxy: Starting pm-proxy service
08-19 09:00:02.156   400   400 E DrmLibRpmb: rpmb_init succeeded! with ret = 0
08-19 09:00:02.156   400   400 E QSEECOMD: : Listener: index = 1, hierarchy = 0
08-19 09:00:02.159   400   400 E SSD     : ssd_init_service succeeded!
08-19 09:00:02.159   400   400 E QSEECOMD: : Listener: index = 2, hierarchy = 0
08-19 09:00:02.190   400   400 E QSEECOMD: : Init dlopen(libsecureui.so, RLTD_NOW) is failed....
08-19 09:00:02.191   418   418 E QSEECOMD: : Listener: index = 0, hierarchy = 1
08-19 09:00:02.193   418   418 E QSEECOMD: : Listener: index = 1, hierarchy = 1
08-19 09:00:02.196   418   418 E QSEECOMD: : Listener: index = 2, hierarchy = 1
08-19 09:00:02.202   418   418 E QSEECOMD: : Init dlopen(libsecureui.so, RLTD_NOW) is failed....
08-19 09:00:02.202   418   418 E QSEECOMD: : Listener: index = 3, hierarchy = 1
08-19 09:00:02.205   418   418 E QSEECOMD: : Listener: index = 4, hierarchy = 1
08-19 09:00:02.207   418   418 E QSEECOMD: : Listener: index = 5, hierarchy = 1
08-19 09:00:02.219   418   418 E QSEECOMD: : Listener: index = 6, hierarchy = 1
08-19 09:00:02.219   418   418 E QSEECOMD: : Init dlopen(libqisl.so, RLTD_NOW) is failed....
08-19 09:00:02.219   418   418 E QSEECOMD: : Listener: index = 7, hierarchy = 1
08-19 09:00:02.219   418   418 E QSEECOMD: : Init dlopen(libGPreqcancel.so, RLTD_NOW) is failed....
08-19 09:00:02.220   418   418 E QSEECOMAPI: : Error::Cannot open the file /firmware/image/keymaste.mdt errno = 2
08-19 09:00:02.220   418   418 E QSEECOMAPI: : Error::Loading image failed with ret = -1
08-19 09:00:02.514   402   402 E qdutils : getPluggableNode: Failed to find HDMI node.
08-19 09:00:02.514   402   402 E qdutils : getPluggableNode: Failed to find HDMI node.
08-19 09:00:02.515   407   407 E Diag_Lib:  Diag_LSM_Init: Failed to open handle to diag driver, error = 13
08-19 09:00:02.515   407   407 E PPDaemon: Diag_LSM_Init() failed.
08-19 09:00:02.515   407   407 E PPDaemon: Initialization diag library failed
08-19 09:00:02.515   407   407 E PPDaemon: Failed to open file descriptors and register diag lib
08-19 09:00:02.515   407   407 E PPDaemon: Unable to initialize DCM
08-19 09:00:02.521   402   402 E qdhwcomposer: Unknown display attribute 6
08-19 09:00:02.521   402   444 E qdhwcomposer: vsync_loop:unable to open event node for dpy=0 event=3, No such file or directory
08-19 09:00:03.156   361   361 E SELinux : avc:  denied  { find } for service=vendor.qcom.PeripheralManager pid=406 uid=1000 scontext=u:r:init:s0 tcontext=u:object_r:binder_per_mgr_service:s0 tclass=service_manager permissive=1
08-19 09:00:03.359   399   413 E PerMgrSrv: power on modem failed /dev/subsys_modem: Out of memory
08-19 09:00:07.215   389   389 E sound_trigger_platform: platform_stdev_init: ERROR. Unable to open the mixer, aborting
08-19 09:00:07.215   389   389 E sound_trigger_hw: stdev_open: ERROR. platform init failed
08-19 09:00:07.215   389   389 E SoundTriggerHalImpl: couldn't open sound trigger hw device in sound_trigger.primary (No such device)
 

Matador-67

Member
Dec 22, 2013
41
8
08-19 09:00:02.220 418 418 E QSEECOMAPI: : Error::Cannot open the file /firmware/image/keymaste.mdt errno = 2

This looks like a typing error, i thing it shoud be /firmware/image/keymaster.mdt but i don't know in witch File.



Gesendet von meinem CMR-W09 mit Tapatalk
 

AndDiSa

Senior Member
Dec 2, 2009
3,701
5,074
Heidelberg
HTC Desire
Nexus 7
08-19 09:00:02.220 418 418 E QSEECOMAPI: : Error::Cannot open the file /firmware/image/keymaste.mdt errno = 2

This looks like a typing error, i thing it shoud be /firmware/image/keymaster.mdt but i don't know in witch File.



Gesendet von meinem CMR-W09 mit Tapatalk
I am not quite sure as the firmware partition has vfat format, so there is a chance that filenames are restricted to 8 chars only. But I agree that this might be the / one of the blocking reasons.

Currently I am doing eng-builds and I can see the logcat while booting ... only that it suddenly stops. The screen is black but nevertheless I am able to use ADB shell and I can analyze everything
 

AndDiSa

Senior Member
Dec 2, 2009
3,701
5,074
Heidelberg
HTC Desire
Nexus 7
@matador-2 Only a bit of progress until yet, i.e. firmware is loading and there are no major issues showing up during the boot (device tree is updated). Unfortuntely the boot process still stops suddently :(
I suppose it's due to missing binaries / wrongly configured startup scripts. Probably I should have better taken Motorola G4 (e.g. https://github.com/Jleeblanch/device_motorola_athene/tree/8.1.x-arm) as template for the device tree as the Motorola comes with 32 bit kernel, too, while leeco is using 64bit. But I saw only today.

I am a bit sorry but I have to give away my device the next days so I do not have any longer the possibility to test the builds.
 
  • Like
Reactions: Matador-67

Top Liked Posts