• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

diabl0w

Senior Member
Mar 5, 2015
455
136
Your SM-N910V/trltevzw was on latest stock from 2018-01-17?
Which TWRP version did you flash?

Correct, it was running latest stock MM 6.0.1 before unlocking/rooting. I tried the official TWRP image (i think its 3.4 or 3.0.4) as well as the twrp that is provided by that guide during the second to last step. Definitely don't think it is twrp related. Of course all best practices of wiping data between flashes etc were used. I like to think I am a pretty advanced user.

When booting into download mode, it correctly says I am in developer mode or whatever because of the CID change.

---------- Post added at 10:45 AM ---------- Previous post was at 10:31 AM ----------

here are some logs after booting lineageos that I took thru adb while the device was on but the screen was black: https://pastebin.com/7yhL7FzM

looks like mostly errors about fingerprint sensor, radio drivers, some stuff about thermals, and camera drivers.
 

buffaloquinn

Senior Member
I like the ROM thanks a lot. But I still get the issue of a total crash, when trying to format SD for internal Storage. Did clean install, tested 20201017 and 20201110 on two Phones N910F. Updated Modem/Firmware/TRWP. :confused:

Any ideas hints?

I can confirm the Phones sometimes not detecting the sim card when restarting. I also experience Bluetooth crashes / restarts.
Well, it's almost universally recommended on here and other threads to NEVER format the SD card for internal storage.
 

ripee

Recognized Developer / Recognized Contributor
@diabl0w gotta admit I never used this ROM here.
But on my N910F crDroid 6.12 is running perfectly well.
Perhaps you give that a try.
Never used fingerprint on custom ROMs although.

Since transi1 uses our lineage sources with no changes whatsoever, any improvements are due to CrDroid, not the device sources.

Well, it's almost universally recommended on here and other threads to NEVER format the SD card for internal storage.

This was fixed over a month ago.
 
Since transi1 uses our lineage sources with no changes whatsoever, any improvements are due to CrDroid, not the device sources.... .

.... i don't think we have fingerprint on this device
Didn't want to lessen the work of the lineage team.
I knew that crDroid is based on LOS.
Just thought it's worth mentioning.

Acc to here: https://mobilespecs.net/phone/Samsung/Samsung_Galaxy_Note_4_SM-N910F.html we do have Fingerprintsensor.
 

SeaFargo

Senior Member
Feb 24, 2011
322
59
Rome
rvd.it
Is there anybody who have enable camera2api in this LineageOS on SM-N910F?? I've tryed several ways (Magisk module, hal3, ecc) but any results. I still do not know if it can be a "software trick" or it's an hardware requirement ...

In any way congrats to the developer!! This porting is amazing and very stable, exepting for first fingerprint recordings but works at the end ...
 

jennygrant

Member
Apr 26, 2017
6
1
Hello!
First of all, what a great effort - for me this has been the best Note 4 ROM ever, certainly since Samsung ceased support. It seems that everything I use now works, however, Bluetooth audio... The first ROM I loaded had it working in the sense that it would connect, but Bluetooth output level was incredibly low and the microphone was pretty similar. The 20201110 version has raised the levels, so that at MAX external volume I can hear and the microphone doesn't elicit complaints. Any chance of raising the Bluetooth output volume a bit more, so I don't have to set the car to MAX?
 

Quacoo

New member
Nov 25, 2020
4
0
Since transi1 uses our lineage sources with no changes whatsoever, any improvements are due to CrDroid, not the device sources.



This was fixed over a month ago.


I know, I read it. But my test told different and I don't know why. Did someone test positive?

I never formatted SD for internal storage. I started in LOS16 because I did not know how to get write access to SD from all Apps. In LOS17.1 I noticed write access in the developer options. Now I use this, but I still cannot store camera pics directly on SD. So if there is a way to get this strait, I'll be happy to stay this way.

Installed BL, CP, TRWP, LOS17.1, Magisk 21, did all wipes and formats, but no google apps.

At the moment the issue of not recognizing SIM supersedes. Only way to get this working again is to take Battery out. Switching off or restarting does not do anything.
 

SeaFargo

Senior Member
Feb 24, 2011
322
59
Rome
rvd.it
Boot down into TWRP. There go to "Reboot" - "Power Off"
Phone is switched off without power drain.
I've to report the same power drain issue in my N910F with fresh clean install (from the very latest Samsung tw). I've turned off the phone yesterday night full charged and this morning I turned it on with 68%!!! It's an incredible issue. The OEM shut down procedure may be corrupted. Any suggestion other than TWPR? Have you ever tested some non-recovery app or module?
 
Last edited:

Quacoo

New member
Nov 25, 2020
4
0
I've to report the same power drain issue in my N910F with fresh clean install (from the very latest Samsung tw). I've turned off the phone yesterday night full charged and this morning I turned it on with 68%!!! It's an incredible issue. The OEM shut down procedure may be corrupted. Any suggestion other than TWPR? Have you ever tested some non-recovery app or module?

That tells me the Phone does not shut down completely. There are some processes remaining that drain the battery and keep the phone from reconising the SiM when restarting.
 

SeaFargo

Senior Member
Feb 24, 2011
322
59
Rome
rvd.it
That tells me the Phone does not shut down completely. There are some processes remaining that drain the battery and keep the phone from reconising the SiM when restarting.
I'm not sure it's a process remaining issue. The standalone charging system and the recovery system continue to boot properly. I've test this issue even with no SIM card.
Paradoxically the phone drains less battery if leaved switched on 😆😆. It's a very strange issue. I'm looking to find a shut down procedure/command that really and cleanly shut down. If somebody find different than twpr way let me know...
 

louisJJ

Senior Member
Oct 3, 2010
178
2
Hey guys,
I installed the last version (lineage-17.1-20201205-UNOFFICIAL-trlte) and when I run Titanium backup and go to Preferences > backup folder location, if I choose /storage/3839-3131/TitaniumBackup (which is a folder on my SDcard) it says "the folder doesn't have write access"... This prevents me from having my Titanium backups on the SDcard (which is mandatory for keeping them across the rom flashes).

Isn't that weird that:
- my sdcard is mounted to /storage/3839-3131/
- whereas /sdcard points to /storage/emalated/0 (which seems to be the normal mount moint)
?

Although from Root Browser app, I see the permissions for /storage.3839-3131 are drwxrwx-x .... so the permissions seem right, no ?
 
Last edited:

logosA

Recognized Contributor
Nov 17, 2013
3,434
3,290
Heraklion Crete
Hey guys,

I installed the last version (lineage-17.1-20201205-UNOFFICIAL-trlte) and when I run Titanium backup and go to Preferences > backup folder location, if I choose /storage/3839-3131/TitaniumBackup (which is a folder on my SDcard) it says "the folder doesn't have write access"... This prevents me from having my Titanium backups on the SDcard (which is mandatory for keeping them across the rom flashes).

Isn't that weird that:
- my sdcard is mounted to /storage/3839-3131/
- whereas /sdcard points to /storage/emalated/0 (which seems to be the normal mount moint)
?


Although from Root Browser app, I see the permissions for /storage.3839-3131 are drwxrwx-x .... so the permissions seem right, no ?


There is an easy way of giving TitaniumBackup write access to the external sdcard.
Android uses a very clean security-solution by giving apps that request write access to external SD, permission only to their own folder – not to the entire card!
In order to get TitaniumBackup to work perfectly , you can simply create a folder on the external sdcard,using the following folder-structure:
Android/data/com.keramidas.TitaniumBackup/
This is the name titanium backup uses for its default storage location.
So go with a file manager to external sdcard, in the folder Android/data, simply create a new folder named com.keramidas.TitaniumBackup
(copy paste from this post if you want, for not making typing mistakes)
If you already have existing backups, which want to keep, move them with a file-explorer from their current place to that folder, sometimes Titanium by its own, asks you if you want to move them there, too.
Finally, go to the preferences of TitaniumBackup, choose “Backup folder location” and choose the above specified folder.
Android will ask you to give permissions and you should allow access to that.
After that, sdcard's folder will be ''greened'' and you will be able to use it as your backup folder
That will be all.
Reboot your phone.
Finish.
 

barywsf

Member
Jul 31, 2018
39
8
San Francisco
It's there any change log specifically for our porting or some news about the battery drain while phone is off issue??

The battery drain issue has been reported before by several people but doesn't seem to be true for everyone. When I am not using my phone, I remove the battery. A bit of a hassle but the ROM is solid.

Hopefully someone will figure out the issue and resolve it.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Please get logs or I can't help. I am trying to enforce the kernel by taking care of all remaining selinux denials, but I can't take care of all such denials until I get logs from all affected variants, such as N910V.

    Try my updated gapps builds.
    Device: SM-N910T
    Battery: A larger third party battery
    A clean install of just the rom, lineage-18.1-20210705-UNOFFICIAL-trlte.zip, using TWRP.
    Interesting to note that the file manager can't access the internal storage and exporting it was fun.
    Also the sim card is not detected unless I reinstall lineage-18.1-20210630-UNOFFICIAL-trlte.zip.
    I have attached the logs. I hope this helps with the selinux denials.
    1
    New builds are on their way! They include all the selinux denials that audit2allow found in your logs, including some that cover the bugs you mentioned. So these upcoming builds should be slightly less buggy.
    1
    Nice ROM. I think it’s ready and stable for daily drive.
    But, to take notes on my device I use the s-pen very often - and sadly this ROM has the palm-rejection bug, like all other Linage ROMs since LOS14.

    When I touch the display with my hand, in parallel when I'm writing, the last stroke/draw gets immediately erased.

    ghostweel seems to find a solution on this thread - but my coding skills are to weak for implementing it by myself.
    Is there a chance, that the palm-rejection feature will be enabled on this ROM in future?

    The second curious thing is, that MS OneNote goes crazy when I'm write a stroke or letter with the s-pen (only tested on Note Edge). I can read my handwritten letters at first, when I left the surface of the display with the s-pen. Before that, it shows abstract lines and glitches.

    I tested many ROMs with my Note 4 and a Note Edge device - (super clean install) every time the same bug. And yes - the stock ROM runs fine with palm rejection.
    1
    Hi
    after a dirty install build 0713 GPS is excellent. Attached are the images. Accuracy almost 3m (sometimes), fix up to 12 satellites. Both Glonass and Beidou are used, although not as much as GPS. I would be interested in the opinions of other users. Still try to tweak gps.conf for faster fix in Europe.
    Thanks ripee.
    1
    Hello, @ripee. First of all, thank you for bringing android 11 to Note4! I love it! I just flashed 7/18 today. While testing, everything works including wifi, mobile data, gps, etc. However, after a while (may be a couple hours), the phone restarted itself. When it finished loading, I noticed there is no phone signal anymore. So I found out, baseband and imei are lost. Luckily, I backed up modem and efs files. So, I restored them easily. But it keeps happening again randomly. I don't know what causes it. I attached the log, the last line is right before it shutdown, for you (i did logcat -d). Not sure if it tells you anything. My phone is N910F. Hope this is useful.
  • 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
    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.
    15
    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.