• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][11.0][UNOFFICIAL][Testing] LineageOS 18.1 for Wileyfox Swift

Search This thread

115ek

Senior Member
Jan 30, 2017
588
662
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Remarks:
This thread is thought to collect issues and ideas. It has to be considered being a TESTING version.
Once everything is mature, an official build may be possible.

Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended Lineage recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.

Also make sure you've got the correct firmware installed before installing LineageOS.
More detailed instructions at:
Install LineageOS on crackling

115ek's test builds (for testers only)
Downloads

Recommended Google Apps package:
none: GApps don't fit at the moment. A repartitioning is needed. Currently thinking about this...

Donate to support development:
Donate via PayPal to LineageOS
 
  • Love
Reactions: afacanc38

115ek

Senior Member
Jan 30, 2017
588
662
Changelog

11.09.2021

  • fixed livedisplay
  • updated lineage sources
22.07.2021
  • initial version
 
Last edited:

petexd

Senior Member
Dec 2, 2017
64
1
It's been a while since I tried 18 and I'm tempted to look at the latest. Before I do, are there any major problems other than gapps. I appreciate it needs to be tested but I'd like to be aware if there are any major parts not working.
 

115ek

Senior Member
Jan 30, 2017
588
662
It's been a while since I tried 18 and I'm tempted to look at the latest. Before I do, are there any major problems other than gapps. I appreciate it needs to be tested but I'd like to be aware if there are any major parts not working.
Livedisplay is not working at the moment.
 

petexd

Senior Member
Dec 2, 2017
64
1
I had to remove it because it wouldn't load my photos and I didn't have time to play around with it. It's actually my only phone. It did, however, instal basic flamegapps.
I also got error 255 when tryin to restore my backup but I'm up and running now with 17.1. I'll try 18.1 again soon when I have more time to mess around with it and if I can sort out error 255
 

ajjin0

New member
Jul 24, 2021
2
0
Very cool, thanks! What is the upstreaming status? That would be great as microG builds would be available automatically as well. That one I'd install right away.
 

mmustermann717

New member
Jan 4, 2016
3
1
@115ek Thank you for the new build.
I tried to compile Lineage18.1 myself, but ended up in a boot loop. I assume this is the relevant part of the log, since it repeats over and over again:
Code:
01-01 21:28:58.399  4357  4357 I [email protected]: LiveDisplay HAL service is starting.
01-01 21:28:58.404  4357  4357 D DISP_API: disp_api_get_num_display_modes.
01-01 21:28:58.458  4357  4357 D DISP_API: disp_api_get_num_display_modes successful getting num-of-modes = 6.
01-01 21:28:58.458  4357  4357 D DISP_API: disp_api_get_num_display_modes.
01-01 21:28:58.510  4357  4357 D DISP_API: disp_api_get_num_display_modes successful getting num-of-modes = 6.
01-01 21:28:58.512   220   220 I hwservicemanager: getTransport: Cannot find entry [email protected]::IDisplayModes/default in either framework or device manifest.
01-01 21:28:58.512  4357  4357 E HidlServiceManagement: Service [email protected]::IDisplayModes/default must be in VINTF manifest in order to register/get.
01-01 21:28:58.513  4357  4357 E [email protected]: Could not register service for LiveDisplay HAL DisplayModes Iface (-2147483648)
01-01 21:28:58.514  4357  4357 E [email protected]: LiveDisplay HAL service is shutting down.
01-01 21:28:58.521     0     0 I init    : Service 'vendor.livedisplay-hal-2-0-legacymm' (pid 4357) exited with status 1
01-01 21:28:58.521     0     0 I init    : Sending signal 9 to service 'vendor.livedisplay-hal-2-0-legacymm' (pid 4357) process group...
01-01 21:28:58.521     0     0 I libprocessgroup: Successfully killed process cgroup uid 1000 pid 4357 in 0ms
01-01 21:28:59.391   219   219 I servicemanager: Since 'android.hardware.power.IPower/default' could not be found, trying to start it as a lazy AIDL service
01-01 21:28:59.391  4193  4193 W ServiceManager: Waited one second for android.hardware.power.IPower/default
01-01 21:28:59.393   219  4360 W libc    : Unable to set property "ctl.interface_start" to "aidl/android.hardware.power.IPower/default": error code: 0x20
01-01 21:28:59.395     0     0 E init    : Control message: Could not find 'aidl/android.hardware.power.IPower/default' for ctl.interface_start from pid: 219 (/system/bin/servicemanager)
01-01 21:29:00.392   219   219 I servicemanager: Since 'android.hardware.power.IPower/default' could not be found, trying to start it as a lazy AIDL service
01-01 21:29:00.392  4193  4193 W ServiceManager: Waited one second for android.hardware.power.IPower/default
My local manifest looks like:
Code:
<?xml version="1.0" encoding="UTF-8"?> 
<manifest>
  <project name="115ek/android_device_wileyfox_crackling" path="device/wileyfox/crackling" remote="github" />
  <project name="115ek/android_device_cyanogen_msm8916-common" path="device/cyanogen/msm8916-common" remote="github" />
  <project name="115ek/proprietary_vendor_wileyfox" path="vendor/wileyfox" remote="github" />
  <project name="LineageOS/android_kernel_cyanogen_msm8916" path="kernel/cyanogen/msm8916" revision="lineage-17.1" />
  <project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" />
</manifest>
Does your manifest look the same? Are there any additional patches I have to apply to get it working? I would highly appreciate it if you could share your steps to build LineageOS 18.1.
 
  • Like
Reactions: petexd

115ek

Senior Member
Jan 30, 2017
588
662
Does your manifest look the same?
This should be fine, yes.
Are there any additional patches I have to apply to get it working?
Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94

The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
             <name>IDisplayColorCalibration</name>
             <instance>default</instance>
         </interface>
+        <interface>
+            <name>IDisplayModes</name>
+            <instance>default</instance>
+        </interface>
         <interface>
             <name>IPictureAdjustment</name>
             <instance>default</instance>

You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
 

mmustermann717

New member
Jan 4, 2016
3
1
This should be fine, yes.

Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94

The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
             <name>IDisplayColorCalibration</name>
             <instance>default</instance>
         </interface>
+        <interface>
+            <name>IDisplayModes</name>
+            <instance>default</instance>
+        </interface>
         <interface>
             <name>IPictureAdjustment</name>
             <instance>default</instance>

You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
Thank you very much! That worked.
 

petexd

Senior Member
Dec 2, 2017
64
1
I increased the system partition, a little while ago and backups were restoring OK so I've decided to try 18.1 again.
I must say, it performs really well for the stuff I need. I also like that I can now do calendar etc backups to my sdcard. Much more sensible IMO.
Thanks 115ek. A great job.
I'd like to have a go at building but I'm not sure where to start without the explicit menu like 17.1
 

petexd

Senior Member
Dec 2, 2017
64
1
Thanks to 115ek for the 18.1 set up and to mmustermann717 for his local manifest. I have managed to build 18.1 after a few errors which appeared to be out of memory problems.
I fixed that and was able to complete the build.
Thanks both of you

I was too quick to brag. Im getting a boot loop. I made the changes from 115ek's response #12, so I don't know where I've gone wrong.
Can either of you tell me please?
 
Last edited:

petexd

Senior Member
Dec 2, 2017
64
1
This should be fine, yes.

Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94

The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
             <name>IDisplayColorCalibration</name>
             <instance>default</instance>
         </interface>
+        <interface>
+            <name>IDisplayModes</name>
+            <instance>default</instance>
+        </interface>
         <interface>
             <name>IPictureAdjustment</name>
             <instance>default</instance>

You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
I've tried all of this several times. I get a successful build but a boot loop every time.
The lineage source says successful, it doesn't actually boot so I have no idea how to find any error? Is there anything I can look for? Or can you guess?
I'd appreciate the help if you can. Thanks.
 

115ek

Senior Member
Jan 30, 2017
588
662
Hey :)
how to find any error?
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
You could, but I'm not sure if that really helps.
Is there anything I can look for?
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
 

petexd

Senior Member
Dec 2, 2017
64
1
Hey :)

The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.

You could, but I'm not sure if that really helps.

What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
This is the line you asked about:

BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.selinux=permissive

I've tried my build with your boot.img but it still bootloops.
 
Last edited:

petexd

Senior Member
Dec 2, 2017
64
1
Hey :)

The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.

You could, but I'm not sure if that really helps.

What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
I've tried again and the last 4 lines of the build are: 2021-10-18 16:11:33 - ota_from_target_files.py - INFO : done. Warning: could not find RADIO/filesmap in <zipfile.ZipFile object at 0x7f982df1bf50>. Warning: could not find RADIO/filesmap in <zipfile.ZipFile object at 0x7f982df1bf50>. Compressing system.new.dat with brotli warning radio-update: no radio image in input target_files; not flashing radio [100% 24/24] build bacon Package Complete: out/target/product/crackling/lineage-18.1-20211018-UNOFFICIAL-crackling.zip #### build completed successfully
Is this OK? I thought bacon was another phone (oneplus?)
 

petexd

Senior Member
Dec 2, 2017
64
1
Hey :)
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.

You could, but I'm not sure if that really helps.

What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
I get this , just bfore the build completes successfully. Do you know if this has anything to do with the problem.
99% 463/464] Package OTA: out/target/product/crackling/lineage_crackling-ota-eng.pet
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read VENDOR/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read VENDOR/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read PRODUCT/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read PRODUCT/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM_EXT/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM_EXT/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read ODM/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read ODM/build.prop
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Does your manifest look the same?
    This should be fine, yes.
    Are there any additional patches I have to apply to get it working?
    Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
    But permissive mode should work. You can switch to permissive for now by:
    adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94

    The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
    Code:
    --- a/manifest.xml
    +++ b/manifest.xml
    @@ -184,6 +184,10 @@
                 <name>IDisplayColorCalibration</name>
                 <instance>default</instance>
             </interface>
    +        <interface>
    +            <name>IDisplayModes</name>
    +            <instance>default</instance>
    +        </interface>
             <interface>
                 <name>IPictureAdjustment</name>
                 <instance>default</instance>

    You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
    1
    Code:
    #include <std_disclaimer.h>
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */

    Remarks:
    This thread is thought to collect issues and ideas. It has to be considered being a TESTING version.
    Once everything is mature, an official build may be possible.

    Installation:
    If you are on stock OS, you need a custom recovery first. You can get the recommended Lineage recovery in the official installation instructions link below.
    If you are coming from stock or other ROMs, you need to make a factory reset.
    As always, make sure to backup before installing this ROM.

    Also make sure you've got the correct firmware installed before installing LineageOS.
    More detailed instructions at:
    Install LineageOS on crackling

    115ek's test builds (for testers only)
    Downloads

    Recommended Google Apps package:
    none: GApps don't fit at the moment. A repartitioning is needed. Currently thinking about this...

    Donate to support development:
    Donate via PayPal to LineageOS
    1
    New build is up. Livedisplay is working now.
    Download
    1
    @115ek Thank you for the new build.
    I tried to compile Lineage18.1 myself, but ended up in a boot loop. I assume this is the relevant part of the log, since it repeats over and over again:
    Code:
    01-01 21:28:58.399  4357  4357 I [email protected]: LiveDisplay HAL service is starting.
    01-01 21:28:58.404  4357  4357 D DISP_API: disp_api_get_num_display_modes.
    01-01 21:28:58.458  4357  4357 D DISP_API: disp_api_get_num_display_modes successful getting num-of-modes = 6.
    01-01 21:28:58.458  4357  4357 D DISP_API: disp_api_get_num_display_modes.
    01-01 21:28:58.510  4357  4357 D DISP_API: disp_api_get_num_display_modes successful getting num-of-modes = 6.
    01-01 21:28:58.512   220   220 I hwservicemanager: getTransport: Cannot find entry [email protected]::IDisplayModes/default in either framework or device manifest.
    01-01 21:28:58.512  4357  4357 E HidlServiceManagement: Service [email protected]::IDisplayModes/default must be in VINTF manifest in order to register/get.
    01-01 21:28:58.513  4357  4357 E [email protected]: Could not register service for LiveDisplay HAL DisplayModes Iface (-2147483648)
    01-01 21:28:58.514  4357  4357 E [email protected]: LiveDisplay HAL service is shutting down.
    01-01 21:28:58.521     0     0 I init    : Service 'vendor.livedisplay-hal-2-0-legacymm' (pid 4357) exited with status 1
    01-01 21:28:58.521     0     0 I init    : Sending signal 9 to service 'vendor.livedisplay-hal-2-0-legacymm' (pid 4357) process group...
    01-01 21:28:58.521     0     0 I libprocessgroup: Successfully killed process cgroup uid 1000 pid 4357 in 0ms
    01-01 21:28:59.391   219   219 I servicemanager: Since 'android.hardware.power.IPower/default' could not be found, trying to start it as a lazy AIDL service
    01-01 21:28:59.391  4193  4193 W ServiceManager: Waited one second for android.hardware.power.IPower/default
    01-01 21:28:59.393   219  4360 W libc    : Unable to set property "ctl.interface_start" to "aidl/android.hardware.power.IPower/default": error code: 0x20
    01-01 21:28:59.395     0     0 E init    : Control message: Could not find 'aidl/android.hardware.power.IPower/default' for ctl.interface_start from pid: 219 (/system/bin/servicemanager)
    01-01 21:29:00.392   219   219 I servicemanager: Since 'android.hardware.power.IPower/default' could not be found, trying to start it as a lazy AIDL service
    01-01 21:29:00.392  4193  4193 W ServiceManager: Waited one second for android.hardware.power.IPower/default
    My local manifest looks like:
    Code:
    <?xml version="1.0" encoding="UTF-8"?> 
    <manifest>
      <project name="115ek/android_device_wileyfox_crackling" path="device/wileyfox/crackling" remote="github" />
      <project name="115ek/android_device_cyanogen_msm8916-common" path="device/cyanogen/msm8916-common" remote="github" />
      <project name="115ek/proprietary_vendor_wileyfox" path="vendor/wileyfox" remote="github" />
      <project name="LineageOS/android_kernel_cyanogen_msm8916" path="kernel/cyanogen/msm8916" revision="lineage-17.1" />
      <project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" />
    </manifest>
    Does your manifest look the same? Are there any additional patches I have to apply to get it working? I would highly appreciate it if you could share your steps to build LineageOS 18.1.