[ROM][Q/R] Unofficial, optimized LineageOS 18.1 (April 8th) & LineageOS 17.1 (April 11th)

Search This thread

hystrix65

Senior Member
May 13, 2008
305
40
Fabriano - AN
As far as I remember, some months ago I tried to update from TWRP and I had many problems, i Think i will try with fastboot, thanks. I hope to remember how to do it... :LOL:

Edit: First step done... TWRP upgrade done!
 
Last edited:

Alvin50

Senior Member
Apr 9, 2019
158
49
Venice
I cannot install your 18.1 ROM in my Galaxy J5/2017 neither with TWRP nor with OrangeFox. Both abort saying they cannot install a ROM signed for Tom Bacon as my device is J5y17lte... How can I overcome this or it's definitely wrong what I'm doing?
Kind regards
 
  • Like
Reactions: sumitinhome

sumitinhome

Senior Member
Jul 1, 2014
95
26
I cannot install your 18.1 ROM in my Galaxy J5/2017 neither with TWRP nor with OrangeFox. Both abort saying they cannot install a ROM signed for Tom Bacon as my device is J5y17lte... How can I overcome this or it's definitely wrong what I'm doing?
Kind regards

of course you are doing definitely wrong. This rom is made for Oneplus One. It cannot be installed in samsung j5. Roms are device specific man.
 
  • Like
Reactions: Tomoms

Dashur7

Senior Member
Aug 1, 2015
421
102
Hi @Tomoms , I tried flashing the latest 18.1 build as of today and it flashes without any errors on the latest TWRP. After I boot into the ROM, with or without Gapps, the screen is blank and there are glitches on the screen when I repeatedly press the hardware navigation keys. I tried grabbing a log with adb logcat but the device isn't being detected by the adb. I can still change the volume and access the power menu. The device is also detected by my PC but can't access the files because the default USB config is no file transfer. I managed to copy the dmesg file after rebooting back to the recovery; have attached it in the post.

---EDIT---
I also tried installing the 17.1 build and it's working fine; if that helps :)
https://pastebin.com/ZGDY16dY
 
Last edited:

Tomoms

Senior Member
Feb 15, 2014
2,463
5,851
Trieste
Hi @Tomoms , I tried flashing the latest 18.1 build as of today and it flashes without any errors on the latest TWRP. After I boot into the ROM, with or without Gapps, the screen is blank and there are glitches on the screen when I repeatedly press the hardware navigation keys. I tried grabbing a log with adb logcat but the device isn't being detected by the adb. I can still change the volume and access the power menu. The device is also detected by my PC but can't access the files because the default USB config is no file transfer. I managed to copy the dmesg file after rebooting back to the recovery; have attached it in the post.

---EDIT---
I also tried installing the 17.1 build and it's working fine; if that helps :)
https://pastebin.com/ZGDY16dY
Unfortunately, the last_kmsg is useless in this case; it is only useful to debug a kernel crash that leads to a reboot of the phone. What we would need here is a logcat. Can you try grabbing one again, by running adb root beforehand? If I am not mistaken, that should allow you to grab a log even when you can't manually enabled USB debugging & USB file transfer.
 

Dashur7

Senior Member
Aug 1, 2015
421
102
Unfortunately, the last_kmsg is useless in this case; it is only useful to debug a kernel crash that leads to a reboot of the phone. What we would need here is a logcat. Can you try grabbing one again, by running adb root beforehand? If I am not mistaken, that should allow you to grab a log even when you can't manually enabled USB debugging & USB file transfer.

Got it. I'll try it out as soon as I get some free time.
 

Alvin50

Senior Member
Apr 9, 2019
158
49
Venice
of course you are doing definitely wrong. This rom is made for Oneplus One. It cannot be installed in samsung j5. Roms are device specific man.
Thank you for your reply: in the changelog I didn't see any reference to a specific device, and was fooled thinking it were a generic ROM. Usually there's an easy to see banner where suitable devices are listed.
 

Tomoms

Senior Member
Feb 15, 2014
2,463
5,851
Trieste
Thank you for your reply: in the changelog I didn't see any reference to a specific device, and was fooled thinking it were a generic ROM. Usually there's an easy to see banner where suitable devices are listed.
Just under the thread's title there's the subforum hierarchy banner which shows that we are in the Oneplus One's subforum :)
 
  • Like
Reactions: Djiban

Alvin50

Senior Member
Apr 9, 2019
158
49
Venice
Just under the thread's title there's the subforum hierarchy banner which shows that we are in the Oneplus One's subforum :)
NOW I see it... You are right, but a better advertising could help who, looking to a lot of articles, usually finds this in the incipit... Let's say that, from the graphical viewpoint it's scarcely capturing the reader's attention.
Kind regards.
 

Dashur7

Senior Member
Aug 1, 2015
421
102
Unfortunately, the last_kmsg is useless in this case; it is only useful to debug a kernel crash that leads to a reboot of the phone. What we would need here is a logcat. Can you try grabbing one again, by running adb root beforehand? If I am not mistaken, that should allow you to grab a log even when you can't manually enabled USB debugging & USB file transfer.

Hey @Tomoms , I disabled the developer settings on 17.1 to try this out. The adb root command needs to find the adb device, which isn't detected as the debugging is turned off. I also tried enabling the developer options but keeping the default settings; same problem. After a little reading I found out that the persistent settings for adb are stored in one of the files in /data/property/ I tried pulling it via adb in recovery mode but it seems to have a single file post Android 9 with all of the settings merged. Is there any way else I can grab the logs?
 

Tomoms

Senior Member
Feb 15, 2014
2,463
5,851
Trieste
Hey @Tomoms , I disabled the developer settings on 17.1 to try this out. The adb root command needs to find the adb device, which isn't detected as the debugging is turned off. I also tried enabling the developer options but keeping the default settings; same problem. After a little reading I found out that the persistent settings for adb are stored in one of the files in /data/property/ I tried pulling it via adb in recovery mode but it seems to have a single file post Android 9 with all of the settings merged. Is there any way else I can grab the logs?
Yes, there's a simpler way: in the next days I'll prepare a flashable zip that, during the booting process, will auto-save the logs somewhere in the /data partition, because I need it for my personal testing purposes. I'll share it with you.

I did the OTA, if you want any feedback, let me know.
Is it me, or the new build feels a bit smoother than the previous ones?
 
  • Like
Reactions: Dashur7

Tomoms

Senior Member
Feb 15, 2014
2,463
5,851
Trieste
A new 17.1 build with March's security patches is available! It'll be available via OTA tomorrow.
EDIT: available via OTA now.

Hey everyone, I have been following this thread for a while to see when it gets almost fully stable. Are there any bugs left at this point aside from the 5GHZ hotspot?
GPS fix might be a bit slow sometimes but I think I will improve it at least a bit in the next days. WiFi screen mirroring without external devices such as Chromecasts and similar tools doesn't work but it's normal, Google killed the feature and now it is only available on newer devices. Some people face issues with mobile data & network signal but I, just like many others, cannot reproduce the issues.
 
Last edited:

Fabien70

New member
Sep 18, 2015
4
1
41
OnePlus One
Samsung Galaxy S9+
Hello
Thank for job.
I flash 18.1 without problème, all is good. But i Just have a bug, I can't configure anyway short and long press menu button.
Before i can configure it and I did not do anything special and now i can't do it.
I wipe cache and dalvik cache, no success.
Thanks for help.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 23
    I'm happy and proud to announce that I am now an official LineageOS maintainer for our Oneplus One!
    8
    A new, juicy update is available! Not only April's security patches are included, but also lots of unnecessary debugging instructions have been stripped out of several components of the OS, to avoid wasting resources on unnecessary computation. I've implemented some updates & optimizations for libpng, sqlite, jemalloc (Android's memory allocator) and bionic (Android's C standard library & math library). I've taken all of these patches from ProtonAOSP's repos, so a huge thank you goes to kdrag0n.
    This build also features an important fix that will be included in the next official nightly as well: https://review.lineageos.org/c/LineageOS/android_device_oneplus_bacon/+/307402

    The update is already visible on SourceForge, but it will be available for download & via OTA in a few minutes.
    EDIT: available now.

    @EotT I gave a look at your brightness problem but didn't manage to solve it yet.
    @madmax85812 disabling the proximity sensor seems a bit harder than expected. I'll look at it again soon.
    6
    This is great news. I hope you will continue to update your own optimized ROM for those of use that find stock LineageOS too conservative.

    I finally took the plunge today and updated from stock 17.1 to your 18.1. So far so good!
    Sure thing. My unofficial builds won't cease to exist: as I've done until now, I'll use them as a "playground" to test device-specific changes that could be implemented in official builds as well before submitting them. The "craziest" and most extreme changes/optimizations, those that would never be accepted in LineageOS, will continue to live inside my builds.
    EDIT: I'll stop updating my 17.1 builds after releasing the last one, which will come when April's patches are available.
    5
    @Saison2018 the new 17.1 build is up! It'll be available via OTA later tonight or tomorrow (it depends on how fast it'll propagate to enough download mirrors). It includes April's security patches and some of the recent improvements I've implemented in my 18.1 build.
    4
    Just an observation. The phone did not fully charge during the night. It was at 35 % in the morning. On stock 17.1 the phone would be fully charged during the night every time.

    I use an old 700mA Samsung charger to conserve the battery. I just now rooted and installed Smartpack and will keep an eye on this.
    The charging drivers my ROM uses are screwed up. Official Lineage's are even worse for me, that's why I use these older ones. Sometime they just don't accept current from slow chargers and/or old cables (I've been experiencing the same with my Sony 850 mA charger). For now, just set the charging input current to any value higher than 700 mA in Smartpack and it'll work. One day I'll have the time to look into this issue as well... The plan is to implement Sultanxda's custom charging & battery drivers, I recall they worked perfectly on his Nougat ROM.
  • 83
    In this thread I'll share with you my personal builds of LineageOS 18.1 and 17.1 (older builds of 16 and 15.1 are still downloadable). This project is inspired by idprophecy's LineageOS builds, to which I want to add my favorite features and, possibly, even more optimizations and improvements.

    MAIN FEATURES
    LineageOS 18.1 features:
    • support for MicroG (signature spoofing) - read the 2nd post!
    • improved & updated libraries: sqlite, zlib, libpng, jemalloc
    • Android RunTime (ART) updates and improvements
    • several debugging & tracing instructions are removed from the system
    • SBC Dual channel bluetooth audio codec
    • in-built F-Droid Privileged Extension
    • support for OTA updates
    • several minor tweaks and improvements
    • my custom kernel (features listed below)

    LineageOS 17.1 features:
    • all C/C++ components are build with -O3/-g0 flags (maximum optimization, minimum useless debug info)
    • support for signature spoofing (= MicroG supported) - read the 2nd post!
    • in-built F-Droid Privileged Extension
    • native support for WakeBlock by @GioBozza, for more info: WakeBlock on XDA
    • several updates & improvements to internal components: skia & libjpeg-turbo (temporarily reverted), art, bionic, libpng, sqlite, zlib
    • several debugging & tracing instructions are removed from the system
    • custom Screenshot QS tile
    • deGoogling tweaks: non-Google captive portal server & SUPL server
    • support for OTA updates
    • minor miscellaneous tweaks
    • my custom kernel (features listed below)
    Kernel features:
    • built with GCC 10
    • CPU underclocking (268 MHz) & max freq. limited to 1,9 GHz by default
    • several f2fs updates
    • power-efficient workqueues
    • cpu_input_boost by Sultanxda
    • bricked hotplug replaces mpdecision
    • CPU undervolting
    • maple I/O scheduler
    • userspace LMKD replaces the old in-kernel Low Memory Killer driver
    • DDR bandwidth boost on screen wake
    • minor adjustments and tweaks
    • several code updates and security/bug fixes
    BUGS
    Also present in official LineageOS 18.1/17.1:
    • kernel panic when changing USB mode to "File transfer" - fixed in the 20200811 build & later official nightlies
    • notification/charging LED not working - fixed in the 20200811 build & later official nightlies
    • low in-call microphone if speakerphone is enabled - fixed in the 20200811 build
    • charging hiccups when using certain 3rd-party chargers/cables - fixed in the 20200912 build
    • AUX audio output not working - fixed in all builds (unofficial & official) newer than 20200826
    • wrong time on boot until connected to a network - fixed in the 20201110 build, and in official nightlies starting from 20201224
    • the Music app is quite messed up (bug is already reported on Gitlab) - fixed by the LineageOS team as of January 2021.
    • flaky GPS - fixed (or at least improved) in the 20201213 build
    • manual mobile network scan not working - fixed in the 17.1 2021-01-23 build, also fixed on official LineageOS
    • 5 GHz hotspot is broken - but there's a workaround here
    • weird noises while playing flac files if AudioFX's Bass option is enabled (17.1)
    Bugs that are specific to my builds:
    • encryption of f2fs-formatted /data partition is broken - fixed in the 20201028 build
    • corrupted thumbnails and weird visual artifacts in the system's color picker - fixed in the 20201028 build
    • libjpeg crashes in certain apps (NewPipe, Files, and others) - fixed in the 20201017 build
    • Telegram's (and, possibly, other apps') in-built camera not working - apparently fixed in the 20200811 build

    Changelog for LineageOS 18.1:

    April 8th:​
    • synced with LineageOS (w/ April's security patches + fix for display issue)
    • some kernel updates
    • lots of debugging code disabled
    • updates for jemalloc, sqlite, bionic, libcore and libpng

    Changelog for older LineageOS 18.1 builds:
    March 9th:​
    • synced with LineageOS (w/ March's security patches)
    • some kernel updates
    • encryption is now working
    February 27th:​
    • synced with LineageOS
    • minor kernel updates
    February 9th:​
    • synced with LineageOS (with February's security patches)
    • some kernel fixes & updates
    • fix for the Gallery showing the previous photo instead of the new one, immediately after taking one
    Ferbuary 3rd:​
    • bootloop fix

    February 2nd:​
    • synced with LineageOS
    • WiFi hotspot fixed
    • Dynamic processing audio library
    • in-built F-Droid Privileged Extension
    • Dual-channel SBC codec for bluetooth headphones/speakers (untested, must be set in Developer Options)
    • minor tweaks to reduce memory usage (with negligible impacts on performance and/or graphic quality)
    • my custom kernel has been implemented
    January 21st:​
    • synced with LineageOS
    • updated & improved sqlite library (huge performance boost)
    • optimized zlib library
    • improvements for ART's memory usage
    • support for OTA updates
    January 6th:​
    • synced with LineageOS (January's security patches)
    January 3rd:​
    • synced with LineageOS
    • lockscreen PIN possibly fixed? Please confirm
    December 26th:​
    • fixed signature spoofing
    • synced with LineageOS
    December 21st:​
    • added support for signature spoofing (MicroG) and UnifiedNLP
    December 14th:​
    • initial build

    Changelog for LineageOS 17.1:

    April 11th:​
    • synced with LineageOS (w/ April's security patches)
    • some useless debugging stuff has been stripped off

    Changelog for older LineageOS 17.1 builds:
    March 11th:​
    • synced with LineageOS (w/ March's security patches)
    • all the kernel updates I've recently implemented in 18.1
    • SBC HD bluetooth codec is actually available now
    February 6th:​
    • February's security patches
    February 2nd:​
    • in-built F-Droid Privileged Extension
    • Dynamic processing audio library
    • Dual-channel SBC codec for bluetooth headphones/speakers (untested, must be set in Developer Options)
    • some kernel updates & fixes
    • synced with LineageOS
    January 22nd:​
    • synced with LineageOS
    • manual mobile network search is fixed
    January 12th:​
    • synced with LineageOS
    • full January security patchset (2 commits were missing in the previous build)
    • some kernel fixes & improvements
    January 8th:​
    • synced with LineageOS (including January's security patches)
    January 3rd:​
    • synced with LineageOS
    • several kernel updates (including power-efficient workqueues)
    • Screenshot QuickSettings tile
    • less Google-dependant: custom captive portal & SUPL servers
    December 13th:​
    • synced with LineageOS
    • December's security patches
    • many GPS updates (it works much better now)
    December 3rd:​
    • synced with LineageOS
    • TimeKeep support
    • malloc switched to low memory configuration
    • minor power saving tweak for the eMMC chip

    DOWNLOADS
    Unified download link for both 17.1 and 18.1: SourceForge
    Unofficial MinTheGapps for Android 11 & arm, built by me: here
    Unofficial OpenGapps for Android 11 & arm (suitable for bacon, thanks to AdrianDC): Mega
    Older 18.1 builds are available here: AFH
    Previous 17.1 builds are available either on AFH or on MEGA (17.1) / on MEGA (18.1).
    23
    Hello! My first LineageOS 16 build works fine and even Argon kernel is working fine :)
    However, the ROM is not ready for you to use it, especially because I have to improve the kernel's implementation (currently it's very buggy and a normal user would go crazy to make it work properly). So I will not release this build, however I think that within a few days I'll get this stuff sorted and a new build will be ready!
    23
    I'm happy and proud to announce that I am now an official LineageOS maintainer for our Oneplus One!
    19
    Hello,
    I'm happy - and also a little bit proud :victory: - to inform you that I started making some small contributions to official LineageOS for bacon: I've submitted (and I'll keep submitting) some kernel bug/security fixes that got merged into our official LineageOS kernel. This way, both users of my builds and users of the official nightlies can benefit from them!
    Also, our LineageOS maintainer has fixed the LED issue, thus it'll work in the next nightly, and of course in the next build of mines too :)
    Talking about my next build, it'll come in a couple of days!
    19
    Hello guys,
    I'd like to inform you that I plan to switch to LineageOS 16 soon. I'll start by using TugaPower, to get used to the new OS and to finish setting up my building environment (I have to pull some files from LineageOS 16 before I can start building my own releases). Then I'll start sharing my own builds. Since it'll take me a while to implement in LineageOS 16 all the features and the optimizations that I've added to my 15.1 builds, the first LineageOS 16 builds will be very close to the standard LineageOS ones, but I'll gradually get to the point I've reached with Oreo.
    I might build and upload one last 15.1 build in the next days.
    I'll keep you informed :)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone