[ROM][UNOFFICIAL][11] LineageOS 18.1 [tblte][trlte][trlteduos]

Search This thread

clod22

Senior Member
Jul 24, 2011
483
184
Bucharest
I have last rom 0415, i checked if is true with battery drain and last night i put the phone off and in the morning i have same level of battery. maybe you have battery issue.
 

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,375
6,346
tiny.cc
I tried last night, power off and in the morning same level. F variant.
By same level, do you mean something above the bare minimum needed to function, such as above 15%? This would not be a bug if users with healthy batteries could power off at 100% charge, leave the battery in the phone without pulling it out for any reason, leave the phone powered off and not connected to a charger or computer for a few hours, then power on and check the charge level. If it goes down only by a couple percentages over a longer period of time, such as overnight, then that's normal. But in Q most users reported a charge loss of 30%+ overnight. Either their batteries are old, or this is indeed a bug.

Regarding the IR blaster, I picked the necessary commits from Inkypen, backported them to Q, and they work on both for most people.
 
  • Like
Reactions: clod22

barywsf

Member
Jul 31, 2018
39
8
San Francisco
I am using a phone with a new battery. I was at 100% at 11 am and down to 60% after 3 hours after having shutdown the phone. I will keep testing but I think this is still an issue.

I have a SM - N910V running the 20210415 build, Android 11.
 

[email protected]

Senior Member
Oct 10, 2019
55
16
Den Helder
This is absolutely a bug.
Any other phone I use wakes up in the same battery state as when powered off, even after weeks.
And the fact fhat my battery lastst for 3-4 days when powered on, proves fhat it is fine.
Leaving the phone powered off for around a day and it's empty.

Bu there is now a work around: after powering down connecting to a charger for a couple of seconds and fhe battery stays alive.
 
  • Like
Reactions: ripee and Nokiotto

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,375
6,346
tiny.cc
Update regarding the battery drain while powered off

After trying different kernel images made from different sources branches, the worst is when I combined all P and Q commits together: 3.42% of power loss per hour.

Using our purposely outdated P kernel branch, which I had kept outdated relative to the official P branch due to the official branch not booting, reduced the loss to 2.86 %/h. The problem is, there are hundreds of commits between each of the branches that we have to sort through to figure this out.

It could be worse, the S5 Plus users have been suffering from this power drain since Oreo. They had reported this bug to Lineage's JIRA on gitlab but none of the Lineage people were able to help.
 

keithscot

New member
Apr 18, 2021
4
0
Having problems flashing Magisk when upgrading to 18.1.
Full clean flash.
After flashing 18.1, TWRP complains that Magisk-22.1.zip has "invalid zip file format" and with previously flashable Magisk-v20.4 it gives "Error 1" after it cannot mount /vendor.
I have tried with TWRP versions; new twrp-3.5.2_9-0 and older twrp-3.3.1-0 and both give the same result.

If I flash Magisk before 18.1 then Magisk-v20.4 flashes OK but Magisk-22.1 still complains that it is an invalid zip file format.
Flashing Magisk before 18.1 does not result in being able to get root.
I am stumped - any help appreciated.
 

ticky33

Senior Member
Apr 3, 2012
174
49
Bordeaux
I flashed twrp 3.5.2 then Los 18.1 0416, bitgapps r20 and magisk 22 and no issue.
Just always the same power off battery drain issue.
This is the only one issue (but too big for a daily driver) I noticed.
Thanks to all the devellopers
 

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,375
6,346
tiny.cc
Another update regarding the powered off battery drain

R-ifying the 15.1 kernel branch resulted in a loss of 2.29 %/h. I guess we have to go down to the branch cm-10.1 (too bad it doesn't exist) to get the percentage loss down to what it should be, which should be no more than 5% in 24 hours (0.21 %/h).
 
  • Like
Reactions: ticky33

clod22

Senior Member
Jul 24, 2011
483
184
Bucharest
By same level, do you mean something above the bare minimum needed to function, such as above 15%? This would not be a bug if users with healthy batteries could power off at 100% charge, leave the battery in the phone without pulling it out for any reason, leave the phone powered off and not connected to a charger or computer for a few hours, then power on and check the charge level. If it goes down only by a couple percentages over a longer period of time, such as overnight, then that's normal. But in Q most users reported a charge loss of 30%+ overnight. Either their batteries are old, or this is indeed a bug.

Regarding the IR blaster, I picked the necessary commits from Inkypen, backported them to Q, and they work on both for most people.
Thank for clarification, for me is clear that is not o bug regarding battery drain with phone off. Please check again if IR blaster working, and if the answer is yes,, maybe i have a issue with this, because in A10 was working but with last rom( 0415 ) not working. Pls. sent me in right direction with this. Thank
 

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,375
6,346
tiny.cc
Thank for clarification, for me is clear that is not o bug regarding battery drain with phone off. Please check again if IR blaster working, and if the answer is yes,, maybe i have a issue with this, because in A10 was working but with last rom( 0415 ) not working. Pls. sent me in right direction with this. Thank
It's very interesting that you are not experiencing any battery charge reduction when you power off. Just to be absolutely sure, do you power off the phone from Lineage or TWRP? May I ask your battery percentage at the time you turn off your phone, and the percentage you see when you turn it on again?

The IR blaster didn't work on the first R build that I ran, 0414, because I had not yet merged Inkypen's 2 commits that copied the old version of it from the hardware_samsung repo to our device tree, thereby overriding the new IR blaster hardware_samsung source. But all builds from 0415 have the necessary IR commits in them.
 

keithscot

New member
Apr 18, 2021
4
0
Having problems flashing Magisk when upgrading to 18.1.
Full clean flash.
After flashing 18.1, TWRP complains that Magisk-22.1.zip has "invalid zip file format" and with previously flashable Magisk-v20.4 it gives "Error 1" after it cannot mount /vendor.
I have tried with TWRP versions; new twrp-3.5.2_9-0 and older twrp-3.3.1-0 and both give the same result.

If I flash Magisk before 18.1 then Magisk-v20.4 flashes OK but Magisk-22.1 still complains that it is an invalid zip file format.
Flashing Magisk before 18.1 does not result in being able to get root.
I am stumped - any help appreciated.
This is on a SM-N910F that I have been running 17.1 as a daily driver.
Indeed using twrp-3.5.2_9-0, if I re-flash 17.1 and Magisk-v20.4, it completes without error

But with lineage-18.1-20210416 (or lineage-18.1-20210414) and Magisk-v20.4, when TWRP flashes Magisk-v20.4.zip it gives me "cannot mount /vendor" and "Updater process ended with Error: 1"
 

clod22

Senior Member
Jul 24, 2011
483
184
Bucharest
Thank for clarification, for me is clear that is not o bug regarding battery drain with phone off. Please check again if IR blaster working, and if the answer is yes,, maybe i have a issue with this, because in A10 was working but with last rom( 0415 ) not working. Pls. sent me in right direction with this. Thank
With 04.18 IR Blaster working, F variant, Thank @Dev.
 

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,375
6,346
tiny.cc
With 04.18 IR Blaster working, F variant, Thank @Dev.
Great, now may I ask the battery percentage that didn't go down for you after a few hours of being powered off?

This is on a SM-N910F that I have been running 17.1 as a daily driver.
Indeed using twrp-3.5.2_9-0, if I re-flash 17.1 and Magisk-v20.4, it completes without error

But with lineage-18.1-20210416 (or lineage-18.1-20210414) and Magisk-v20.4, when TWRP flashes Magisk-v20.4.zip it gives me "cannot mount /vendor" and "Updater process ended with Error: 1"
Download Magisk-v22.1.apk and rename it to Magisk-v22.1.zip. Also remember to flash 11.0 gapps, I recommend https://sourceforge.net/projects/opengapps/files/arm/test/20210130/
 

clod22

Senior Member
Jul 24, 2011
483
184
Bucharest

keithscot

New member
Apr 18, 2021
4
0
Great, now may I ask the battery percentage that didn't go down for you after a few hours of being powered off?


Download Magisk-v22.1.apk and rename it to Magisk-v22.1.zip. Also remember to flash 11.0 gapps, I recommend https://sourceforge.net/projects/opengapps/files/arm/test/20210130/
Thanks @ripee It looks like I had somehow got a zip of Magisk 22.1 sources. Sorted now thanks.

Can you say why you recommend opengapps over the other options like BiTGApps or NikGApps for Android 11?

And this is such good work you and all devs have done with this ROM series, it is hugely appreciated.
 

Top Liked Posts

  • 1
    Changelog

    Builds 0508 for all variants
    * May 5, 2021, Android security patch level.
    * Synced with LineageOS sources.

    NOTE EDGE USERS: I'm still looking for anyone able to generate logs on their phone. I need these to be able to enforce the kernel later.
  • 5
    Changelog

    Builds 0415 for all variants
    * Android 11 is here!
    * Synced with LineageOS sources.
    4
    Update regarding the battery drain while powered off

    After trying different kernel images made from different sources branches, the worst is when I combined all P and Q commits together: 3.42% of power loss per hour.

    Using our purposely outdated P kernel branch, which I had kept outdated relative to the official P branch due to the official branch not booting, reduced the loss to 2.86 %/h. The problem is, there are hundreds of commits between each of the branches that we have to sort through to figure this out.

    It could be worse, the S5 Plus users have been suffering from this power drain since Oreo. They had reported this bug to Lineage's JIRA on gitlab but none of the Lineage people were able to help.
    4
    Changelog

    Builds 0426 for trlte
    * Power off battery drain bug may be fixed. I identified a series of commits applied by Corinna in 2018 during the Oreo bringup that allowed apq8084 to use the new QTI power HAL, which I reverted here.
    * Synced with LineageOS sources.
    3
    Changelog

    Builds 0501 for trlteduos
    * SIM 1 works again, SIM 2 is left...
    * Synced with LineageOS sources.
    2
    No, no problem with the battery. The problem occurs only if I turn off the phone, the battery drains quickly. If I leave it on all night, consumption is very low.
    Same here. In standby the battery lasts some 4 days, when powered off it's empty overnight.
  • 50
    image17.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.

    Code:
    * [B][U]Your warranty is now void.[/U][/B]
    * We are not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or your 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 us for messing up your device, we will laugh at you.


    FREQUENTLY ASKED QUESTIONS

    (Please read them BEFORE posting anything in the thread!)
    Q: Whenever I try flashing any lineage-18.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
    A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.5. Simply flash the linked below version 3.5 or higher, reboot back into recovery, and flash the rom zip again.

    Q:Will any of the variants receive official builds from LineageOS?
    A: In short, no. While official support would certainly add credibility to our work, there is absolutely no reason to believe that unofficial builds are any less secure or stable than official ones. Naturally all the bugs listed below would first need to be fixed, but still the process of submitting and maintaining official support is very time-consuming and not something I, for one, am unable to make such a commitment.
    Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.

    Q: Why is my phone warmer/hotter and the battery noticeably drained after flashing a build?
    A: The wipe process that is a part of the installation procedure deletes some important configuration data, ie. BATTERYSTATS, which keep track of the battery's power level. These data ensure a balanced power management profile for all the hardware components of your phone. This is normal and nothing to worry about at all. Your battery drain will return to normal within a day or two.

    If, however, you notice increased battery drain over a few days, check your signal. Android automatically re-directs battery power to the antennas to compensate for a weak signal from the tower to which your phone is connected at that time. If your signal is strong, check the following:
    1) You missed one of the Wipe steps in the flashing procedure.
    2) You are running an old bootloader or modem. Flash the most recent one listed for your variant under the links in the TWRP thread. Note: Use the "AP" button in Odin to flash ripee's combined BL_CP tar files.
    3) How old is your battery? Official replacement Samsung batteries typically last around 1 year if you recharge them regularly, ie. once a day. Since the Note 4 is almost 6 years old, it is normal for your original battery to start failing, but official Samsung batteries should not cost more than USD 20 nowadays.
    4) If all else fails, start over! Go through the entire installation procedure, including flashing a stock Marshmallow build, and going from there. Do NOT skip any steps this time!

    Q. Flashing a build failed with the message "eMMC Write Fail".
    A. This is the infamous embedded Multi-Media Controller bug that indicates that your internal flash memory is dead or dying. Do NOT try any tricks or crazy ideas to fix it, as they are all hoaxes! The ONLY way to get rid of it is to open your phone up and replace its logic board. :p


    [Official] Note 4 Verizon Bootloader Unlock
    - ryanbg

    Open GApps

    ROMs
    - SM-N910F/G/P/R4/T/T3/V/W8: trlte
    - SM-N9100ZC/ZH/6W/9W: trlteduos
    - SM-N915F/G/P/R4/T/W8: tblte

    Magisk

    SPenCommand

    - It is against XDA Developers rules to post links to paid apps and games. Please find this app on your own if you wish to use it.

    WipeTelephonyProviderData
    - hsbadr



    If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 18.1 variant, which corresponds to the model of your phone!


    How to flash LineageOS and Open GApps
    FULL WIPE (with external microsd card)
    1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
    2. Download your LineageOS Rom and GApps Package,
    3. Move your LineageOS Rom and GApps Package to the external MicroSD storage,
    4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
    5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
    6. Swipe to Wipe at Bottom of Screen,
    7. Back to Main start screen,
    8. Wipe > Format Data,
    9. Type 'Yes' and press blue checkmark at the bottom-right corner,
    10. Go Back to Main Start Screen to Install Rom and GApps,
    11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
    12. Reboot System! Enjoy!


    FULL WIPE (without external microsd card with NO Home PC access)
    1. Move any files you want to keep to a safe folder - ! Or you will lose them !
    2. Download your LineageOS Rom and GApps Package,
    3. Move your LineageOS Rom and GApps Package to the internal storage,
    4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
    5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
    6. Swipe to Wipe at Bottom of Screen,
    7. Back to Main start screen,
    8. Wipe > Format Data,
    9. Type 'Yes' and press blue checkmark at the bottom-right corner
    10. Go Back to Main Start Screen to Install Rom and GApps,
    11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
    12. Reboot System! Enjoy!


    FULL WIPE (without external microsd card with Home PC access)
    1. Move any files you want to keep to your Home PC - ! Or you will lose them !
    2. Download your LineageOS Rom and GApps Package,
    3. Move your LineageOS Rom and GApps Package to the internal storage,
    4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibrate),
    5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
    6. Swipe to Wipe at Bottom of Screen,
    7. Back to Main start screen,
    8. Wipe > Format Data,
    9. Type 'Yes' and press blue checkmark at the bottom-right corner,
    10. Go Back to Main Start Screen to Install Rom and GApps,
    11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
    12. Reboot System! Enjoy!
    13. Once first boot is completed you can safely move your files back onto your Internal Storage.



    Important information about stock S Pen functionality!
    The apps, libraries, and drivers that allow for the advanced S Pen-based functions in stock TouchWiz and TouchWiz-based custom roms WILL NEVER BE INCLUDED IN ANY AOSP-BASED ROMS due to their proprietary nature. The scope of these functions goes beyond simple vendor blobs and enters the realm of 3rd party intellectual property licensed to Samsung. The S Pen does work in all AOSP-based custom roms, however it acts simply as an alternative input device. Various open source 3rd party apps are available that take advantage of the Note 4's stylus (see above), but their functionality is a fraction of that of stock TouchWiz.

    Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.


    Problems known to happen after a Dirty Installation
    1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.

    * Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.

    * Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.


    Bugs
    - When the phone is powered off from Lineage and the battery is not removed, the battery charge will fall at an approximate rate of 2% per hour of time that the phone is powered off without the battery having been removed since it was powered off. This does not occcur when powering off from TWRP, having first powered up to TWRP or rebooted to TWRP from Lineage. It also does not occur if the battery is removed from the phone before being put back in, either after powering off from Lineage or being pulled out while Lineage is running. This bug has affected the apq8084 chipset since Oreo (as described by the S5 Plus community, which uses the same chipset). However, the S5 Plus had received official lineage-15.1 and 16.0 support despite being affected by this bug. Furthermore, we have deduced that it must be caused by one or more of the 652 commits that separate the Nougat and Oreo kernel branches. We will never have the time to go through each and every one of these commits to fix this bug outright, but we are always open to suggestions.
    - If NFC is turned off when the phone is booted up, the NFC toggle will freeze in the "off" position and remain off until the phone is rebooted. If NFC is turned on when the phone is booted up, the NFC toggle will function properly to turn NFC both on and off. However, if NFC is turned off and the phone is rebooted, this bug will reappear.
    - The 2nd SIM slot does not work in any trlteduos variant.
    - VoLTE is not supported, and will not be supported for the foreseeable future.
    - You tell us!

    Changelog
    All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.

    Credits
    - Our resident Developer Emeritus fattire, Elektroschmock for his work on shamu (Nexus 6), and every other open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the tblte, trlte, and trlteduos.

    Sources
    - LineageOS
    - apq8084

    XDA:DevDB Information
    LineageOS 18.1, ROM for the Samsung Galaxy Note 4

    Contributors
    ripee, Inkypen, logosA, ghostwheel, ananjaser1211, khalvat, tripLr
    ROM OS Version: Android 11
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: Stock Marshmallow for your variant.

    Version Information
    Status:
    Stable
    Current Stable Version: 11
    Stable Release Date: 2021-04-14

    Created 2020-03-16
    Last Updated 2021-04-15
    17
    Changelog

    Builds 0421 for all variants
    * Fingerprint sensor is fixed.
    * Increased microphone levels to improve video recording, courtesy of Telegram user AomineDaiki87.
    * Synced with LineageOS sources.
    16
    Changelog

    Builds 0322 for all variants
    * trlte-common: Enable comp backpressure. This is supposed to improve the overall smoothness of the rom.
    * Synced with LineageOS sources.
    13
    Join us on Telegram!

    LineageOS is part of the triplr_dev_users
    group, courtesy of tripLr.
    11
    Changelog

    Builds 0329 for all variants
    * Video playback in Chrome, YouTube, etc., is fixed by removing the widevine instance from the manifest.
    * Synced with LineageOS sources.
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