[ROM][UNOFFICIAL] LineageOS 18.1 for onyx

Search This thread
2okPze5.png



Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.

Features
Individuality

Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended 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.

More detailed instructions at:
Install LineageOS on onyx.

Downloads
Download LineageOS 18.1 for OnePlus X
Download TWRP Recovery for OnePlus X
Recommended Google Apps package: Open GApps (Choose the arm pico package - NOT arm64)

Source code
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.

The device specific source code can be found in the LineageOS Github repo.
OnePlus X device tree
OnePlus X kernel

Changelog:
Initial

Bug reports:
Please submit bugs and other errors in this thread

Donate to support development:
Donate via PayPal to vware
Donate via PayPal to LineageOS

Contributors
Georg Veichtlbauer
ROM OS Version: Android 11
ROM Kernel: Linux 3.4.x

Version Information
Status:
Experimental

Created 2022-06-12
Last Updated 2022-07-24
 
Last edited:

niravnn

Senior Member
Aug 12, 2011
933
275
Bardoli
OnePlus X
Thank you so much, I''ll be installing it tomorrow and will be active here if I found some bugs will report with logs :) once again thank you so much, much appreciated your work
 
  • Like
Reactions: ze7zez

niravnn

Senior Member
Aug 12, 2011
933
275
Bardoli
OnePlus X
The in call volume is very high even at the lowest volume level and screen doesn't go off when answering a call or dialing a call

let me know that do I need to post logs for this issue :)
 
as ive said in the other thread, this is pretty much just built on top of the trees of Yume. you can find the sources there, or on my github (linked in my profile).

however, also, just a post above, ive stated i am working on re-upstreaming the whole thing, i am not done yet. and its summer ;P once ive got news, i'll update the thread.
 
  • Like
Reactions: niravnn

niravnn

Senior Member
Aug 12, 2011
933
275
Bardoli
OnePlus X
just quick update
clean Installed it and so far it's fine. in call volume is perfect and screen also goes of now :)

I'll test it and see if I find any other bugs.. hopefully not 🤞

1 update: when it boots up it says signed with public keys
 
Last edited:

niravnn

Senior Member
Aug 12, 2011
933
275
Bardoli
OnePlus X
Random reboots keeps happening. Mainly when I try to switch between more than two apps or it could be something else. I've attached logs if it helps
 

Attachments

  • 2022-06-23_20.35.zip
    277.3 KB · Views: 17
  • Like
Reactions: ze7zez

niravnn

Senior Member
Aug 12, 2011
933
275
Bardoli
OnePlus X
sadface. did the other build crash for you guys too?
no other build was fine it wasn't rebooting like your latest build. but the in call volume was so high at the lowest volume that it was unsable as daily driver and also screen wasn't turning off when receiving a call or dialing a call so it was also creating issue. so I only used your other build for like 30 minutes but not a single reboot at that time.

but with your latest build, it rebooted every 5 minutes. so it's completely unusable..
 

Patjutzu

Senior Member
Aug 3, 2013
139
13
Berlin
OnePlus 8T
The version of the lineage-18.1-20220612-UNOFFICIAL-onyx.zip runs so far well with me no restart without reasons present.
Unfortunately, the display does not go off when making calls with the version lineage-18.1-20220612-UNOFFICIAL-onyx.zip when the phone is at the ear.
For me, the volume was ok, but not perfect either, I felt it was more quiet than loud.
It could be a bit louder.

Their new version lineage-18.1-20220623 I tested only briefly and then went back to the old one because of the constant reboots.
 

Patjutzu

Senior Member
Aug 3, 2013
139
13
Berlin
OnePlus 8T
Sorry I noticed something else
So for one the proximity sensor still doesn't work and the display doesn't turn off while on the phone and just stays on when the phone is at your ear.

What also does not work is the interactivity display.

My settings are set to: Wave On, Pick Up On and Pocket On.
however nothing happens so I guess the sensor is not working because the phone just stays dark when in standby.
 

Baron1971

Senior Member
Oct 8, 2007
453
102
Colọnia Agrippinẹnsis
Good work for this old Phone!! And we have nothing to pay...! ;) One Question ist there an Option to customize the Navbar (center Clock, change Battery Icon, etc.)? I can't find anything.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    lineage 19 or newer is not going to happen on onyx (and for that matter, any device that has a kernel older than 4.4), due to google switching major functionality in android to use eBPF.

    someone would have to port a 4.4 kernel to onyx, but for me, it's just not worth the massive effort. the only exception i know of right now is xiaomi 8996, someone ported a 4.4 kernel to that.

    sorry to be the bearer of bad news, but you may stop waiting for pretty much all of these legacy devices.
    2
    (...) for me, it's just not worth the massive effort. (...)
    Your version of LOS 18.1 is good enough.

    The undisputed record holder in terms of the number of successive versions of android (from 2.3.5 to 13) is the Samsung Galaxy S2 (i9100), which currently runs Lineage 20.
    1
    yeah, and don't get me wrong, with some trickery it's still doable (in a janky way), we also ran dumpling without the ebpf stuff... but random reboots, wrong stats, etc were observed... so no daily driver material
  • 14
    2okPze5.png



    Introduction
    LineageOS, an open-source Android distribution, is available for several devices,
    with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
    Join us and breathe new life in your device, be it old or new.
    If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.

    Features
    Individuality

    Customization is paramount to productivity.
    That’s why LineageOS promises to push for user personalization and preference.
    Everyone is unique and your device should be too.
    Security
    Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
    Trust will help you understand the security of your device and warn you about possible threats.
    We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
    And to make your device more secure, lock everything behind an enhanced lock screen.
    Longevity
    LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
    Installation:
    If you are on stock OS, you need a custom recovery first. You can get the recommended 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.

    More detailed instructions at:
    Install LineageOS on onyx.

    Downloads
    Download LineageOS 18.1 for OnePlus X
    Download TWRP Recovery for OnePlus X
    Recommended Google Apps package: Open GApps (Choose the arm pico package - NOT arm64)

    Source code
    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.

    The device specific source code can be found in the LineageOS Github repo.
    OnePlus X device tree
    OnePlus X kernel

    Changelog:
    Initial

    Bug reports:
    Please submit bugs and other errors in this thread

    Donate to support development:
    Donate via PayPal to vware
    Donate via PayPal to LineageOS

    Contributors
    Georg Veichtlbauer
    ROM OS Version: Android 11
    ROM Kernel: Linux 3.4.x

    Version Information
    Status:
    Experimental

    Created 2022-06-12
    Last Updated 2022-07-24
    5
    new build is up, quite a lot of changes. proximity sensor works fine for me, in call and also during inactivity display. unless i make some progress on my "internal" goals, this will be the one to get for some time, as it works for everything i need it to.
    3
    Thanks for the smooth ROM, but the gallery shows the wrong GPSposition of the photos in the properties. My position in the mapsapp is OK. The same on LOS17.1...
    that's not a device related issue i am afraid, so i'd have to ask you to file a report at the official lineage bugtracker.

    Will there be an Update with August Security fix?
    most likely not. i'm mainly working on oneplus 5/5t devices, and we are getting ready for android 13. i am using my private resources (i.e. beefy build server) to build lineageos, and i don't have the capacity (time, space and these days money) to work on too many things at once.
    3
    running either one of the 2022-07-01 or 2022-07-24 builds and initiating storage encryption the ROM reboots to encrypt but keeps displaying the bootanimation. aborting the bootup with a hard reset leaves the phone with a working but unencrypted - seemingly untouched - /data partition.

    when reformatting /data, wiping /system & flashing other YumeMichi LineageOS ROMs and then trying to encrypt again the operation fails as well until i zero-out reserve2, the partition that holds the encryption footer in YumeMichi's device tree.

    when building from source with YumeMichi's device tree and kernel using this manifest (last repo sync & build tested September 15, tested both lineage-17.1 and lineage-18.1) storage encryption works as expected. however, it is not possible to use "Secure Startup" on the lineage-18.1 branch as the ROM never finishes the second round of booting after passcode entry for decryption. YumeMichi's TWRP build decrypts /data just fine after providing the passcode. when wiping /data without formatting it and flashing an older YumeMichi ROM it is able to boot properly after providing the passcode.
    Secure Startup was fully functional on LineageOS versions prior to 18.1
    the issue is not present up until los_v2.zip and first reproducible in los_v3.zip as uploaded by YumeMichi to the Telegram group. in this case the device doesn't even boot to the passcode entry.
    in the system settings these builds report as 18.0-20201106-UNOFFICIAL-YumeMichi-onyx and 18.0-20201130-UNOFFICIAL-YumeMichi-onyx with kernel versions 3.4.113-Sultan-g39904a6f7cd and 3.4.113-Sultan-g5de6a8a8e18 respectively. los_v2.zip is SELinux permissive while los_v3.zip enforces it. the issue is reproducible when building from current lineage-18.1 source with permissive SELinux.
    there were no commits to YumeMichi's device tree in that period. these are all commits between the reported kernel versions.

    the only similar issue i could find affected legacy devices on lineage-17.1 but was reportedly eliminated by updating to LineageOS 18.1
    i tried gathering useful logs using advice from said issue with no luck. adb didn't spin up during the unsuccesful encryption operations or infinite reboots. maybe /proc/last_kmesg could be another option.

    i recognize that these are up to 3 distinct issues but i tried to collect every bit of related info that i know about.

    ----- Update 2022-10-20
    i did some extra testing with current lineage-18.1 sources and vanilla yumemichi device tree at the latest commit.

    when i apply the commit onyx: Start bootanim before mounting data partition from your device tree the ROM boots fine as long as /data is unencrypted
    if i try to boot the rom on an already encrypted /data it fails to boot and jumps to recovery.
    trying to encrypt /data with reproduces the behavior described at the beginning of this post. however, if i do a hard reset and restore the unpatched init.qcom.rc and reboot it successfully encrypts and boots up.

    from a user perspective, i do not perceive any issue this commit might be intended to address and a web search for "aosp bug 30118894" does not return anything.

    i am always compiling without the patch onyx: Enable encryption in all tests i've described so far.
    applying it in isolation breaks encryption - trying to encrypt results in a bootloop. doing a hard reset leaves the /data partition seemingly encrypted with TWRP and ROM asking for a passcode. this is with secure startup disabled / no screen lock set before encrypting.
    on your build lineage-18.1-20220724-UNOFFICIAL-onyx.zip when i write the original version of init.qcom.rc with cat init.qcom.rc > /system/vendor/etc/init/hw/init.qcom.rc trying to encrypt bootloops as well but after a hard reset /data is left unencrypted and booting works as well as data access in TWRP.
    setting only TARGET_LEGACY_HW_DISK_ENCRYPTION to true appears to be fine / not change the behavior from yumemichis original device tree.
    3
    new release. beware: quite a lot of changes, mostly bringing configs back to stock (original maintainers didnt understand the usage of i2s in the sound config apparently). however: this may cause unexpected problems, so please let me know if anything new goes wrong here ;)
    also, current source links are updated