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

Search This thread

logosA

Recognized Contributor
Nov 17, 2013
3,432
3,289
Heraklion Crete
twrp 3.5.2_9

 

Attachments

  • Screenshot_2021-04-09-20-57-27.png
    Screenshot_2021-04-09-20-57-27.png
    101.6 KB · Views: 22
  • Screenshot_2021-04-09-20-57-07.png
    Screenshot_2021-04-09-20-57-07.png
    121.3 KB · Views: 22
  • Screenshot_2021-04-09-20-58-39.png
    Screenshot_2021-04-09-20-58-39.png
    224.1 KB · Views: 22

DjDiabolik

Senior Member
Jun 25, 2014
618
140
It's someone obtain NO 4G signal randomly at reboot of phone ??!?!?!?!

I have reboot my phone....... at reboot wi-fi apparently works. SIM it's be found (i can see my number) but i can't see any signal. Phone say "No Service".

It's a bug ?!?!!? It's fixable or it's a know hardware fault ???

Before reboot phone it's works for days whitout any issue............. how it's append ?
 

Butterstulle

Member
Feb 17, 2020
13
2
It's someone obtain NO 4G signal randomly at reboot of phone ??!?!?!?!

I have reboot my phone....... at reboot wi-fi apparently works. SIM it's be found (i can see my number) but i can't see any signal. Phone say "No Service".

It's a bug ?!?!!? It's fixable or it's a know hardware fault ???

Before reboot phone it's works for days whitout any issue............. how it's append ?
2 or 3 times i had similar problems.
Phone didnt recognize sim at every boot.
One time sim seems to dismount itselve during the day, then I had to reboot.
I will observe it further to check the circumstances...

But overall, I´m still very satisfyed with this ROM!

The bug that phone is draining battery while swiched off is present in my phone (SM-N910F), too. But it is not bothering me so much since I usually never swich it off.
 
Last edited:

DjDiabolik

Senior Member
Jun 25, 2014
618
140
2 or 3 times i had similar problems.
Phone didnt recognize sim at every boot.
One time sim seems to dismount itselve during the day, then I had to reboot.
I will observe it further to check the circumstances...
during use I don't seem to have this problem.... at least for now and I hope you don't start doing that.

I have search on entire thread and @73sydney has speak and discuss about a similar issue in the pass.

maybe he can tell us if there is a solution.

you know by chance if on the other threads related all other roms about this phone someone reports a similar issue ??

On my case it's a SM-N910F.... same as you ?
 

Butterstulle

Member
Feb 17, 2020
13
2
during use I don't seem to have this problem.... at least for now and I hope you don't start doing that.

I have search on entire thread and @73sydney has speak and discuss about a similar issue in the pass.

maybe he can tell us if there is a solution.

you know by chance if on the other threads related all other roms about this phone someone reports a similar issue ??

On my case it's a SM-N910F.... same as you ?
Yes, it`s a SM-N910F..

I haven´t searched in other threats so far..
 
Last edited:

prkfsz

Senior Member
Jun 16, 2020
92
33
For the record, other than Inkypen's fooling around with the sources, absolutely no work has been done toward 18.1. This is because the 17.1 sources are still too unstable to build upon, especially the power off battery drain that none of us have been able to figure out so far. I don't know if Inkypen will put in any more work on R other than porting his own R branch to Havoc R.

If I get the time to re-do the 17.1 sources, this time working from the S5 msm8974 sources rather than the Nexus 6 (shamu) apq8084 sources, I will then proceed with R sources, also from msm8974. But I cannot give you a realistic timeline as my day job is related with fighting covid.

The best thing about ever getting R on trlte is that it is technically easier to bring up from Q than Q was from P, but Q is still not up to our standards, for which I take responsibility since I was the one who brought up Q for trlte in the first place.

Don't know if it helps anything regarding theories on battery drain, but i've noticed that if i plug in the charger even just for a short moment when the device is turned off, there is no battery drain later. I haven't tested having it off for more than half a day yet, but i thought i might write this to you, perhaps kan help.

I am running LOS16, haven't tried it on LOS17, but i'm thinking there are similarities and the issue is on both roms.

Perhaps one more thing to be mentioned here, even if it probably has less to do with the problem, but still - I remember on my Note 8.0 (tablet), on the LOS14 (android 7).
I had it in the book cover (no seethrough windows). While the device was turned off and i opened the cover, the buttons at the bottom lit up. I am thinking some sensors were kept running despite the whole device was switched off. Can't remember battery drain being this considerable, tho.

Want to seize the opportunity and thank you for your struggle with keeping this awesome piece of tech alive.

I also have a humble wondering if there is any possibility to port a version of /e/ from any of your LOS versions. I'd donate extra for your time.
I know you are busy and cudos to you for also fighting corona. (y)(y)(y)
 
Last edited:

Nokiotto

Member
Mar 21, 2018
19
0
Catania
Hello everyone! I have installed the rom update for sm-910 / F, but the problem persists. The battery drains when the phone is turned off. Are there any solutions? Thanks for the great work.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    I think they are focusing on LineageOS 18 now.

    For the record, other than Inkypen's fooling around with the sources, absolutely no work has been done toward 18.1. This is because the 17.1 sources are still too unstable to build upon, especially the power off battery drain that none of us have been able to figure out so far. I don't know if Inkypen will put in any more work on R other than porting his own R branch to Havoc R.

    If I get the time to re-do the 17.1 sources, this time working from the S5 msm8974 sources rather than the Nexus 6 (shamu) apq8084 sources, I will then proceed with R sources, also from msm8974. But I cannot give you a realistic timeline as my day job is related with fighting covid.

    The best thing about ever getting R on trlte is that it is technically easier to bring up from Q than Q was from P, but Q is still not up to our standards, for which I take responsibility since I was the one who brought up Q for trlte in the first place.
    5
    Changelog

    Builds 0415 for all variants
    * Android 11 is here!
    * Synced with LineageOS sources.
    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.
    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.
    3
    Changelog

    Builds 0501 for trlteduos
    * SIM 1 works again, SIM 2 is left...
    * Synced with LineageOS sources.
  • 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