• 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

parahumanoid

Member
Jan 7, 2011
17
3
I am running 18.1-20210808-UNOFFICIAL-trlteduos on my SM-N9109w and the primary issue I am experiencing is that when I insert a blank SD card and choose to use it as an extension of main memory, the unit reboots immediately and nothing of use comes of this. Has this been fixed? As of what build if so? If not, is there hope?
As an aside that I don't have much hope for, is there a way I can get the unit unbound from the China Telecom Card? The last hack that worked for that was for the original Android 5.0 ROM and that was never updated to work with later versions. If I could get it working on the official 6.0 ROM I probably would have stayed content with that.
Separately, a huge thank you goes out to everyone involved in devoping the version for this handset and the Lineage dev community as a whole. You make our lives better and we greatly appreciate that.
 

Reinhard79111

Member
Sep 19, 2016
34
5
I have a folder with 1200 mp3-files on my sd-card (configured as external sd-card).
When I put the sd-car in my note 4 with Android 10 it's super fast.
But with Android 11 (same card) it takes a long time until I can access the folder.
 

croc_87

Member
Aug 14, 2021
25
0
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.



Buy a phone from another manufacturer, the long and short of it. Same answer regarding VoLTE.
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.2_9-1 to load in.
 

Attachments

  • 20210911_133907_resized.jpg
    20210911_133907_resized.jpg
    815.2 KB · Views: 34
  • 20210911_133408_resized.jpg
    20210911_133408_resized.jpg
    856.3 KB · Views: 34

ripee

Recognized Developer / Recognized Contributor
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.2_9-1 to load in.
Original rom, you mean stock TouchWiz? TWRP 3.5.2_9-1 specifically doesn't have a build fingerprint entry for N915F, just N915FY, which I changed on purpose to see if it would make a difference on your phone.

But anyway, what matters is the device info in the stock rom About Phone settings page.
 

croc_87

Member
Aug 14, 2021
25
0
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.



Buy a phone from another manufacturer, the long and short of it. Same answer regarding VoLTE.
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? TWRP 3.5.2_9-1 specifically doesn't have a build fingerprint entry for N915F, just N915FY, which I changed on purpose to see if it would make a difference on your phone.

But anyway, what matters is the device info in the stock rom About Phone settings page.
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.
 

ripee

Recognized Developer / Recognized Contributor
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.
 
  • Like
Reactions: croc_87

McGlockin

Member
Dec 3, 2010
20
0
@ripee I grabbed the 18.1 908 build and installed on a clean device (N910V). Took a couple logs of a few signal drops along with having to put the phone into airplane mode on a fresh start to get data to work (I'm fine with doing so just wanted to note that here in case the issues are related). Still waiting for my N910G to arrive to see if I have the same issue.

Let me know if anything further is needed - thanks in advance.
 

croc_87

Member
Aug 14, 2021
25
0
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.
a question, any idea when both rom and twrp would be available for testing out? Or maybe a sign when it is for testing?
 

adrigen

New member
Nov 9, 2016
1
0
I just loaded 18.1-20210908 and curiously I now have a new os which is Android 9 Linage 16.
Not sure how this happened. It's running beautifully, so Im not sure if I will tempt fate and try another zip.

Thanks for the great job in making this available, regardless!
 

Attachments

  • 20210916_160115.jpg
    20210916_160115.jpg
    656.5 KB · Views: 35

XDA-DB

Member
Jul 26, 2021
7
0
For those wanting to provide information for Ripee, I have a better solution than taking pictures of your screens.

SCRCPY - Allows you to remotely view and control your phone via your pc. It works on windows, mac and linux. You can use a mouse and keyboard to control the phone, and copy paste information using CTRL+C CTRL+V keyboard commands. Other cool stuff too.

You can screenshot or even video record your phone screen (mp4 format) and copy log files instantly for uploading.

I wont link the program in case its against forum rules but its free open source and you can grab it from github.
 

ppp86

Member
Apr 7, 2016
43
12
N910F here, I have these issues with all builds:
- wifi disconnection when the screen is off (it reconnects 3 4 seconds after the screen is back on)
- bluetooth rdm disco/reco (might be due to my bt headset tho idk, samsung galaxy buds)
 

Yesthatsme

Member
Dec 13, 2020
12
9
Hi and thanks @ripee for the great work on that ROM!

I´m running lineage-18.1-20210917-UNOFFICIAL-trlte and I´m having issues connecting to a Wifi-Router in WPA2/WPA3 mode.

I had the same issue with one of the earlier builds of @followmsi 's ROM for the Google Nexus 7:

The issue has meanwhile been resolved and maybe the solutiuon works for your ROM as well.

Cheers
 

ripee

Recognized Developer / Recognized Contributor
Hi and thanks @ripee for the great work on that ROM!

I´m running lineage-18.1-20210917-UNOFFICIAL-trlte and I´m having issues connecting to a Wifi-Router in WPA2/WPA3 mode.

I had the same issue with one of the earlier builds of @followmsi 's ROM for the Google Nexus 7:

The issue has meanwhile been resolved and maybe the solutiuon works for your ROM as well.

Cheers
As you can see, followmsi mentioned this fix that has been in our sources for over a month. Sorry to hear that it didn't help you but this has been implemented in many devices.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I use this ROM with microG - which tells me that signature spoofing isn't supported.
    @ ripee: Do you know whether it will be supported in future releases?View attachment 5426619
    You guys keep coming up with very inventive ways to ask me questions. Do I know whether it will ever be supported? Other than the obvious answer, no, since I never mentioned it, if you want it to be supported but you don't ask directly, the answer will always be no. I have no interest in it myself, but if you do, please contribute links to the sources that have the necessary changes. I do not have the time or interest to dig up this extra functionality that is not part of vanilla Lineage.

    Whatever happened to users motivating themselves to find their own solutions instead of waiting for other people to do the work for them? How do you think I motivated myself to learn how to do monkey work with Android? I got tired of waiting for others to lift a finger for me.
    1
    I know that there is a thing to do with a log, to report bugs. If you send me a link or explain me how to do, I can try to do it.
    Play store or Aurora etc. Downland syslog and use to get your logs
    Hit the 👍 please, if this helps
    1
    I have done tests, by reinstalling the stock rom. The background noise is still there, but way less, maybe 3/4 times lower.
    Also the maximum volume is much much stronger on this rom than on the stock rom. So I think that the rom base volume may be too high? Maybe it also could explain the phone calls that have a high volume
    I also have another phone (Galaxy A5 2016) which runs on lineage OS, and the volume don't goes so high either.

    Is there a file where the base volume could be customized by modifying a value? Or engineer mode (I don't know how to access to that)? Something like that. :)
    you can use Viper4andriod. The program is in Magisk. go into Magisk and look in the apps. you can do bass and a lot of customizing's.
    Hit the 👍 please, if this helps
    1
    I have edited the file mixer_paths.xml. i lowered the values from 88 to 75, and now it's paradise... :) No more background noise... And the sound still can go loud enough (more than the stock rom).
    I've changed some parameters of rx1-2, wich are the headset and the headphone. I haven't modified all the parameters though, because at some poing there is no sound anymore.
    It should also lowers the phone calls.
    I put the file for those interested. You have to rename it mixer_paths.xml. And put it in root/system/vendor/etc . And put the right permissions like the orogonal file.
    I will make these changes in the sources, thanks.
    1
    Hello, can someone re-upload the trlte version on GDrive, can't download any version.
    Thx in advance!
    Log in to gdrive with google account - usually sorts that out.
  • 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.