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

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

Search This thread

timandolly

Senior Member
Jun 9, 2021
95
20
Verizon Samsung Galaxy Note 4
The 0630 build was the last one with the kernel set to permissive. Now that it is enforcing, the SIM access on the N910V variant maybe caused by a kernel permission not being set properly.

N910V users: please post logs from the SysLog app. Root the rom first then run this app.
I have 2 910v phones that are on verizion i will try to load the latest rom on both of them and get you syslogs. Again thank you for this rom
 

timandolly

Senior Member
Jun 9, 2021
95
20
Verizon Samsung Galaxy Note 4
The 0630 build was the last one with the kernel set to permissive. Now that it is enforcing, the SIM access on the N910V variant maybe caused by a kernel permission not being set properly.

N910V users: please post logs from the SysLog app. Root the rom first then run this app.
Here is one 1 log see if this one is ok this rom reboots to maintenance log
This is the 7/28 build
 

Attachments

  • 2021-07-31_15.25-N910V.zip
    259.6 KB · Views: 1
Last edited:

eilongi

Member
Apr 12, 2021
16
0
Yeah wish it worked for me it doesn't i just tried and it goes back to the dreaded no sim error :(
Have you tried the trick with changing the mode to Airplane mode (On)?

Reboot a couple of times after the change setting Airplane mode to On (till you see no data instead of no sim or something similar) and then change back Airplane mode to Off and hopefully it will recognize the SIM and you'll have cell connectivity.
 

gserp4sox

Senior Member
Apr 24, 2009
124
21
The 0630 build was the last one with the kernel set to permissive. Now that it is enforcing, the SIM access on the N910V variant maybe caused by a kernel permission not being set properly.

N910V users: please post logs from the SysLog app. Root the rom first then run this app.

The 0630 build was the last one with the kernel set to permissive. Now that it is enforcing, the SIM access on the N910V variant maybe caused by a kernel permission not being set properly.

N910V users: please post logs from the SysLog app. Root the rom first then run this app.

Here's a 910V log from 8-1 ROM version. No sim. Hope this helps. Thanks
 

Attachments

  • 2021-08-01_910V.zip
    358.1 KB · Views: 2

petrmegac

Member
Dec 17, 2009
24
7
Samsung Galaxy Note 4
Hi
I would like to describe some experiences with bluetooth.

Watch Honor GS Pro:
- pairing without problems
- transferring data from activity measurements without problems
- phone calls without problems

Car Suzuki
- pairing without problems
- phonebook browsing without problems
- after the call is connected it disconnects, the car thinks the call is in progress, the time is still 0:00 and no sound, the call is terminated on the phone side

Windows 10 computer (two different ones)
- pairing without problems
- permanent connection does not work
- file transfer does not work

I have tried all AVRCP and MAP profiles. HD audio cannot be turned on. Codec cannot be selected, only some standard one. SBC, AAC, aptX, LDAC are not working. See attached picture. From various discussions I believe this is a LineageOS problem directly. Maybe the magisk module https://forum.xda-developers.com/t/module-aptx-hd-for-android-11-10-9-8-lineageos-18-1.4081693/ and https://forum.xda-developers.com/t/...s-loss-android-11-10-pie-oreo-nougat.4017735/ would solve something.
When I turn on Gabeldorsch, my bluetooth does not work at all.

N910F
 

Attachments

  • Screenshot_20210802-184718_Nastavení.png
    Screenshot_20210802-184718_Nastavení.png
    186.5 KB · Views: 6
  • Screenshot_20210802-184748_Nastavení.png
    Screenshot_20210802-184748_Nastavení.png
    178.9 KB · Views: 6
  • Screenshot_20210802-184805_Nastavení.png
    Screenshot_20210802-184805_Nastavení.png
    195.1 KB · Views: 5
  • Screenshot_20210802-184819_Nastavení.png
    Screenshot_20210802-184819_Nastavení.png
    179.4 KB · Views: 6

iman.saja.111

New member
Aug 3, 2021
3
0
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
Do you have lineage 18.1 for sm-n910h?
Thanks
 

timandolly

Senior Member
Jun 9, 2021
95
20
Verizon Samsung Galaxy Note 4
Here is the 08/02/21 build that has the dreaded no sim on Verizon hope it helps. I can get the mobile data Verizon show up after restoring a boot image from a previous build but it turns off SELinux.
 

Attachments

  • 2021-08-03_20.38-910V.zip
    352.5 KB · Views: 1
Last edited:

ponko3

Member
Jun 25, 2021
33
1
On the Verizon 910V, the Lineage 18.1 0630 ROM recognizes the SIM and I can configure the SIM.
However, other date ROMs do not seem to recognize the SIM.
Lineage17.1 will not boot.
Lineage 16 boots and recognizes the SIM, but does not proceed to the SIM settings.
Is this the same situation for all 910V users?

Lineage 18.1's 0630 day ROM recognizes the SIM, but the Japanese KDDI SIM doesn't seem to be able to communicate because the signal doesn't match.
If you have a Verizon SIM, can you use the 0630 day SIM?


Translated with www.DeepL.com/Translator (free version)
 

broski2025

New member
Dec 13, 2015
2
0

download magisk apk file
rename it to magisk zip, using a file manager
keep both files in your sd card
apk and zip
boot in twrp
flash rom, flash gapps(if you are using Gapps)
flash magisk zip
boot up
after setting up rom, find magisk apk and install it
it will ask for additional setup and reboot
there you go, you are rooted
late reply from me but wanted to say thansk for the help appreciate it
 

ripee

Recognized Developer / Recognized Contributor
Here is the 08/02/21 build that has the dreaded no sim on Verizon hope it helps. I can get the mobile data Verizon show up after restoring a boot image from a previous build but it turns off SELinux.
Logs from the old permissive kernel don't help since they don't show the problems with the enforcing kernel.

New builds in a few hours.
 

clod22

Senior Member
Jul 24, 2011
484
184
Bucharest
First of al, thank @ripee for hard work, i just dirty installed last rom trlte on F910 over 06.30 version, but i cannot see no files on internal disk , is any setting, Thank.
 
Last edited:

timandolly

Senior Member
Jun 9, 2021
95
20
Verizon Samsung Galaxy Note 4
ripee I have no mobile network in the settings menu. I have used wipe telephone zip and pulled sim and put back i. I have the latest apn settings from Verizon.
Still no mobile network in the settings menu, IN Root explorer it shows all the vpn settings are in the system but the mobile network is greyed out in settings Hope this helps.
 
Last edited:

ripee

Recognized Developer / Recognized Contributor
ripee I have no mobile network in the settings menu. I have used wipe telephone zip and pulled sim and put back i. I have the latest apn settings from Verizon.
Still no mobile network in the settings menu, IN Root explorer it shows all the vpn settings are in the system but the mobile network is greyed out in settings Hope this helps.
What was the last build that gave you mobile settings, 0630?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Already posted here @ripee I am not getting more info. Maybe compare the rom from micky387 what he has in it? because that one work with your new twrp version lineage-15.1-20180309-UNOFFICIAL-tblte I might think it was from here https://forum.xda-developers.com/t/...lineage-15-1-rom-for-note-edge-03-09.3739646/

    The problem is that I have no idea what your variant is, because looking at micky's old builds won't help me figure out why they work and mine don't. Flash 15.1 and figure out in it what your variant is. It's not what is written in the settings, you have to use any given app that gives you the technical details of your phone.

    Edit: Your flashing problem probably has to do with whatever mistakes I made in updating the init_tblte.cpp file in the tblte device tree when I was updating it for R. I will take a look at micky's old 15.1 init_tblte.cpp and make the necessary changes to our R source.

    is it possible to manually edit something to get wifi calling to work? would it require a rebuild of the rom? is there any documentation on this?

    Buy a phone from another manufacturer, the long and short of it. Same answer regarding VoLTE.
    2
    First of all, the me say great work!
    I just installed 8/25 version on a N910V with unlocked bootloader N910VVRU2CPD1 and N910VVRU2CQL1 modem following the FULL WIPE (with external microsd card) instructions. Later also installed Magisk v23. In both cases everything seems to work fine except that when moviing around the phone has issues switching cell towers (on US Mobile/Verizon). When checking with Network Cell Info Lite it shows all cells towers (current and neighbors) using LTE Band 1. I restored N910VVRU2CQL1 and I have Bands 4 and 13. Went back and reinstalled 8/25 version installing also WipeTelephonyProviderData.zip, but no change (same as before). I searched XDA and internet but I have not seen this issue reported anywhere. Does anyone have any idea how to fix this?
    I have (had?) that issue for about 8 weeks, don't know if that started with a certain build. I also observed (Network Signal Info Pro) that the field strength of the towers is OK, my N4s won't re-connect until after re-boot. I'm thinking the providers are working on 5G upgrades (TMO) but my stock LG V20 can handle that just fine. Others with Apple devices say they don't lose signal at all on the same route.
    Do I need to look into my Radio/Base Band?

    Ripee's 08/25 did it for me. No SIM problem, finger print works, head set plug works, sound is loud enough without tweaking. Mobil data must be turned on manually. -I also remove IP-6 from my APN-
    I had Google re-store problems due to "not sufficient memory" even though no memory was used. Fixed that by doing the DATA FORMAT after wiping in TWRP.
    No comments on network loss or GPS yet, will be traveling later this week.
    2
    ripee you have found the silver lining 08/24 boots up with sim on Verizon showing up with no Magik or nothing Hats off to you and all the developer's that have worked on this rom. Thanks for all the hard work. now for Android 12. 🤣
    1
    Update: tried this using magisk as you requested and couldn't get it work either. Side note, not sure if this is related but after attempting this on an older version I was able to get the card to recognize, but have a lot of drops in signal when driving in areas I had no issue before. Wiped and tried a different OS, the Havoc 4.2 and had the same signal drops. Not sure if anyone else has had the same issue or if my Sim is possibly bad. Works fine at home with us being near a tower but driving have multiple drops.
    I can confirm this behavior too. Signal loss when switching towers on my way to and from work. That started with late July builds, I skipped some. Not HW related (I have 3 Note4) and not network related, stock works just fine as does 0630.
    1
    Here some information. I place the old twrp 3.1.0 back on from micky387 and the command gives some info back. So the newer twrp 3.5.2_9-1 from ripp doesn't give that reaction back but works on the phone finally again. Also from the orio rom that mick made it says now it is an SM-N915F with the original rom it says it's a modelnummer SM-N915FY with the baseband-versie N915FYXXU1DPC3. So would this help? The terminal info in the image is from the old twrp 3.1.0 and the rom is from orio version 8.1.0 but also work with the new twrp 3.5.

    Original rom, you mean stock TouchWiz? Yes! rom firmware from samsung self. I call that original. the stock model will say SM-N915FY, but twrp that micky387 made give with the command back ro.product.model: SM-N915F and ro.product.device: tblte also with his ROM firmware build of orio 8.1. As you can see in the picture. If you need image from stock firmware in the settings, I can deliver that if it is needed.
    That's ok, I understand what's going on. Perhaps micky changed the build fingerprint in the sources from N915FY to N915F, but I will post a new twrp 3.5.2_9-2 later in the twrp thread that contains both N915F and N915FY, just so it makes more sense.

    Also, I fixed the build fingerprints in the tblte source, so that they point to the proper variant. Since your stock rom identifies your phone as N915FY, let's hope that the new twrp and future roms will as well.
  • 58
    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
    Join us on Telegram!

    LineageOS is part of the triplr_dev_users
    group, courtesy of tripLr.
    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.
    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.