[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [trlte][tblte][trlteduos]

Search This thread

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,410
6,405
tiny.cc
Just installed 7/08 and now i have a # symbol next to the network status and can not figure out what this is for. Any ideas?

This is because you are using lineage's built in su binary. Flashing Magisk or SuperSU will make it go away.

Latest Magisk Beta 16.6 works fine

Suggest if youre upgrading magisk to flash the magisk uninstall zip first, to have the original boot image restored, and then flashing the new magisk....

Only had one module not install because of the changes, Sysconfig Patcher - will not install via new magisk manager, but flashing it via TWRP works fine...

Magisk automatically uninstalls its old version and any other su binaries automatically when you flash its new version, so these extra steps are unnecessary.

It is for out date su binary. The way I get rid of is by installing su.Zip.

This will have no effect, see what I just wrote above. ;)
 

pro99line

Member
May 17, 2018
10
2
This is because you are using lineage's built in su binary. Flashing Magisk or SuperSU will make it go away.



Magisk automatically uninstalls its old version and any other su binaries automatically when you flash its new version, so these extra steps are unnecessary.



This will have no effect, see what I just wrote above. ;)

Are you saying that the new magisk will automatically get rid of the built in su binary when flashing or do I still need to flash addonsu-remove-15.1-arm-signed first?
 

gravityecho

Member
Feb 2, 2018
11
3
oklahoma City
Note 4 Oreo 7.7.18 day 2

Yep using 7.7.18 (day2), everything seems to work very nicely. I have noticed that if set to turn on torch with long press power button it will restart phone when turned off, so that's not good. But no big deal I went back to chop twice flashlight app. Still waiting on advice about the S-pen not making keyboard appear when tapped into text boxes.:confused:
 

seriosbrad

Senior Member
Sep 2, 2010
476
227
Alberta
www.seriosbrad.ca
Yep using 7.7.18 (day2), everything seems to work very nicely. I have noticed that if set to turn on torch with long press power button it will restart phone when turned off, so that's not good. But no big deal I went back to app. Still waiting on advice about the S-pen not making keyboard appear when tapped into text boxes.:confused:

Flashlight thing is happening to me too. :crying:
 

fattire

Inactive Recognized Developer
Oct 11, 2010
2,280
6,473
www.eff.org
Quick update.

Wanted to update my post from a week or so ago about my ongoing messing with the bluetooth to try to fix the disconnect.

the changes in r32 weren't enough to do it, so I'm now merging source with r41. I also (at the suggestion of Luk1337) added this:

Code:
diff --git a/bluetooth/bdroid_buildcfg.h b/bluetooth/bdroid_buildcfg.h
index 3d68cbb..7279c03 100755
--- a/bluetooth/bdroid_buildcfg.h
+++ b/bluetooth/bdroid_buildcfg.h
@@ -21,6 +21,8 @@
 #include <cutils/properties.h>
 #include <string.h>
 
+#define BTM_BYPASS_EXTRA_ACL_SETUP TRUE
+
 static inline const char* BtmGetDefaultName()
 {
     char product_device[PROPERTY_VALUE_MAX];

So far no breaks but I only had about 15 minutes of media playing. If anyone wants to try that flag you can see if it does anything. Otherwise I'll report back if I still get the occasional crash.

ft

I had an annoying BT disconnect at random times (with no error in the UI) that correlated to this:

06-26 11:07:20.113 10732 10732 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
06-26 11:07:20.122 10732 10732 F DEBUG : Abort message: '[FATAL:future.cc(64)] Check failed: future != NULL.


...and I've been trying to track down the issue. For fun i tried building using this repo in place of the lineageos one. I used the "android-8.1.0_r32" branch because I noticed that the most recent commit in lineageos updated to r30, so it's r2-better, right?

Okay so that said, I have not had any BT crashes yet. But it's only been about 6 hours of which I've barely had bt connected, only for a few moments-- just because I haven't really had occasion to try it. But anyway if I notice anything is fixed, it might be interesting to switch to that repo or try to figure out what is fixed there. I'll report back if I find any issues.

If anyone wanted to try something similar I figured I'd just let people know. I'm also open to any other suggestions of what could be wrong. I didn't track the bug down too diligently, I admit.
 

zwingler

New member
Jul 9, 2018
3
0
customizing assistant is crashing every time

Hello,

I have the problem, that after flashing the assistant at the beginning is crashing every time... I cannot customize my note 4... What ist going wrong.

Any suggestions?
 

Shizzle2889

Senior Member
Apr 17, 2015
121
126
Chicago
Samsung Galaxy A71 5G
Hello,

I have the problem, that after flashing the assistant at the beginning is crashing every time... I cannot customize my note 4... What ist going wrong.

Any suggestions?

Make sure you have the matching version of gapps that match the date on the ROM and try reflashing that. If not, could try a slightly earlier version. Also, i would suggest starting with pico and once set up, install what you need from there once into the trebuchet launcher.
 
Flashed my Canadian N910W8 on July 4th, working well so far, only a few bugs that aren't really important but it's stuff I would love to see fixed ;

Bluetooth crashing (only happened twice on the first day)
Sound crackles a lot if using any equalizer app
NFC is on, but it's not working
Fingerprint scanner can only register one fingerprint
Trusted device bugs the lock screen (I'm on the lock screen but I'm seeing the launcher... confusing AF)
Gboard crashes randomly (it's still on screen but doesn't register key press, hitting back and tapping on the text to bring it back fixes this)


Regardless, I love this ROM, keep up the great work!!! :good:

I just found the equalizer function in VLC. It works awesome
 
  • Like
Reactions: WakedPaul

zwingler

New member
Jul 9, 2018
3
0
Thanks a lot. I had the wrong google apps... 64bit was mine but for the Snapdragon 801 i need 32 bit...

Thanks for the hint...

---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------

Hello,

is there a possibility to activate volte and/or WIFI calling for O2 germany in this ROM?
 

jackstyle

Member
Jan 4, 2018
28
2
Can you fix this bug in the picture? The bug is battery usage data isn't available.Thanks for your work! @ripee
 

Attachments

  • Screenshot_Settings_20180709-230649.png
    Screenshot_Settings_20180709-230649.png
    200.5 KB · Views: 218

jackstyle

Member
Jan 4, 2018
28
2
Can you fix this bug in the picture? The bug is battery usage data isn't available.Thanks for your work! @ripee

---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------

Can you fix this bug in the picture? The bug is battery usage data isn't available.Thanks for your work! @ripee
 

sronweb

Senior Member
Jul 25, 2010
1,421
485
Sicily
OnePlus 6T
Can you fix this bug in the picture? The bug is battery usage data isn't available.Thanks for your work! @ripee

---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------

Can you fix this bug in the picture? The bug is battery usage data isn't available.Thanks for your work! @ripee
I don't have this bug. Maybe it depends on the way you have updated the rom. Did you try to reboot after wipe cache from recovery?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 118
    android-o-logo.jpg

    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-15.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.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.

    Q: When will any of the variants receive official builds from LineageOS?
    A: Not before all the issues listed under "Bugs" below are fixed.
    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: What will some of the differences be between unofficial and official builds?
    A: The following technical changes will take effect:
    - Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
    - Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
    - The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
    Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.

    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 either under the links below. 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 4 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

    Odin
    - Odin3 v3.13.1

    Heimdall
    - Glass Echidna

    Bootloaders and modems
    - ripee

    TWRP for Samsung Galaxy Note 4 (Qualcomm)

    [THEME][TWRP] TWRP Materialised - Black / Dark / Light / Play [27/01/18]
    - z31s1g

    Open GApps

    OFFICIAL !!
    I am not building for oreo anymore, devs have moved to pie,
    thanks everyone !!
    tripLr

    Code:
    LAST ROM Downloads for Oreo
    triplr
    Source Code http://www.github.com/tripLr
    @kevintm78 kernel development
    https://forum.xda-developers.com/note-4/snapdragon-dev/kernel-flashpoint-v3-1-stock-n7-ports-t-t3727407

    (LineageOS su root included.)

    ROMs Note 4
    SM-N910F/G/P/R4/T/T3/V/W8:
    click to open trlte drive folder
    https://drive.google.com/drive/folders/1XWrdmxHeC0A7zGK-TGOH3XG2VfKYP-IA?usp=sharing
    <build date>.zip <flashable zip>
    <build date>.zip.md5sum <md5 checksum for build>
    <build date>.zip.img <backup kernel image install image in twrp>

    ROMs Note 4 Edge
    Note 4 Edge Thanks to @micky387 and @ripee
    Which device is supported ??
    I'm do the best for support multi note edge device so tell me if you see an issue and write it here with you variant
    Support SM-N915F SM-N915FY SM-N915G SM-N915T SM-N915P SM-N915V
    Google Drive Download Folder Click to open and browse to latest
    https://drive.google.com/drive/folders/1lD5vLRFYr8XyGIgL2oT9VXFmdcLOWe3F?usp=sharing
    file names
    <build date>.zip <flashable zip>
    <build date>.zip.md5sum <md5 checksum for build>
    <build date>.zip.img <backup kernel image install image in twrp>

    ROMs Note 4 DUOS
    - SM-N9100ZC/ZH/6W/9W:
    click to open trlte duos folder
    https://drive.google.com/drive/folders/1uibdRnVs9-klbJhtvB5__5B9XFYel1jK?usp=sharing
    file names
    <build date>.zip <flashable zip>
    <build date>.zip.md5sum <md5 checksum for build>
    <build date>.zip.img <backup kernel image install image in twrp>

    Code:
    # Depreciated
    [B]ripee[/B] [I]([COLOR="Teal"]LineageOS[/COLOR] su root included.)[/I]
    - SM-N910F/G/P/R4/T/T3/V/W8: [URL="https://forum.xda-developers.com/devdb/project/dl/?id=31259"][B]
    lineage-15.1-20190218-UNOFFICIAL-trlte.zip[/B][/URL]
    - SM-N9100ZC/ZH/6W/9W: [URL="https://forum.xda-developers.com/devdb/project/dl/?id=31260"][B]
    lineage-15.1-20190218-UNOFFICIAL-trlteduos.zip[/B][/URL]
    
    [B]_mone[/B]
    - [URL="https://androidfilehost.com/?w=files&flid=140308&sort_by=date&sort_dir=DESC"][B]LineageOS[/B][/URL]
    
    [B]micky387[/B]
    - SM-N910F/G/P/R4/T/T3/V/W8: [URL="https://androidfilehost.com/?w=files&flid=257279&sort_by=date&sort_dir=DESC"][B]Note 4[/B][/URL]

    [/CODE]LineageOS Extras
    - addonsu-15.1-arm-signed.zip
    - addonsu-remove-15.1-arm-signed.zip

    Magisk

    The SELinux Switch
    - Ibuprophen

    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 15.1 variant, which corresponds to the model of your phone!

    How to flash a bootloader and/or modem and TWRP
    1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu,
    2. In Odin, import the bootloader.tar file with the "BL" button and the modem.tar file with the "CP" button, or a combined BL_CP.tar file with the "AP" button, for your variant,
    3. Download the .tar file of the latest version of TWRP from the link above,
    4. Reboot into Download mode again and import the TWRP .tar file with the "AP" button.

    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.

    How to install SPenCommand
    1. Install The SELinux Switch and Select SELinux mode as PERMISSIVE,
    2. Reboot into System,
    3. Install SPenCommand.

    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
    - Temporary fix for random SIM death on all trlte variants, courtesy of _mone: boot-1223-trlte.img
    - The fingerprint scanner has not yet been integrated into either trlte or trlteduos.
    - The front camera force closes, requiring a reboot to work again.
    - Bluetooth does not see some wearable devices.
    - The built-in camera app is slow and crashes randomly, especially when the flash fires, requiring a reboot to function again.
    - Video recording in 4K resolution is not possible with either the built-in camera app or any 3rd party camera/camcorder apps.
    - 5GHz hotspot gives an error message when attempting to turn it on.
    - 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 (yet) supported.
    - 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
    - fattire 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 trlte and trlteduos.

    Sources
    - LineageOS
    - triplr-dev

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

    Contributors
    micky387, ripee, tripLr, _mone, cvxda
    ROM OS Version: 8.x Oreo
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: Stock Marshmallow for your variant.

    Version Information
    Status: Snapshot
    Current Stable Version: 8.1.0

    Created 2018-03-09
    Last Updated 2019-07-13
    26
    How's the SIM death? :D
    No SIM death for now.. No SIM at all (LOL). I was even without wifi (that's fixed now). Hopefully I'll keep making progress, once it's a bit more stable I'll start sharing pieces of pie.
    22
    Hi guys.
    Sorry, very busy with my home/work/build but working on new release ;)

    From what I read in last comment, i have fixed Bluetooth pairing.
    Last lineage15.1 source code fix lot of issue too and more new feature :p

    I will add new release today i think (it's 04h15 Am here in France)

    In the future,can you add your device model for your issue please ?? not very simple to add few device support ;)

    Thanks
    20
    Hi there!

    Test build for trlte users:
    lineage-15.1-20180728-UNOFFICIAL-trlte.zip

    Looking for feedback regarding reboot and SIM issues.
    For me the modem finally initialize properly with this build, a first from cm-14.1. Too early to speak about SIM death or reboot issue, I'll keep running this build the whole day (going out in a bit), when I'll be back home I'll see if there will be some feedback from you and decide if the changes are worth pushing to github or not.