• 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
114
24
Verizon Samsung Galaxy Note 4
I had to put a t-moblie sim in my 910v because where I'm going for a month to WVA. they have no Verizon service. The sim works and ii have t-mobile service with it. my phones will charge if off but will not boot till I take the battery out after unplugging. This happens on all three 910v phones I have. If the phone is on it will charge without any problems.
 
  • Like
Reactions: ucof

eliotargy

Senior Member
Oct 24, 2013
218
16
Hangzhou
I've been away for over a year and just installed Lineage 18. Where are the restart options like of old?
I tried searching this thread but the search took me to Xiaomi!
 

sensn

Member
Sep 5, 2018
6
0
@ripee
Hello,
I think i finally found a fix for USB MIDI in the kernel. I found it on an ODRIOD Forum. It says that the g_midi driver was broken. I had a look at your kernel and the fix mentioned there for f_midi.c is not in your kernel.
It's the last post here: Odroid USB MIDI FIX Kernel

So i wanted to give it a try. I have repo synced lineage 18.1.

but i cannot find a local manifest for my device (910F) for 18.1

Should I still use the one for 17.1 ?


Thanks for this wonderful Rom, I really enjoy it, it would be great if you could help me to build the kernel Thanks! Alex
 

greenleaves

Senior Member
Dec 15, 2010
185
21
Philadelphia
Just did another clean fresh of the latest trlteduos 0926 version but still failed with Error 1, see attached. Similar Error 1 also occurred in 0917 version with twrp-3.5.2_9-0-trlteduos. Appreciate your help. Thanks.
 

Attachments

  • IMG_20210926_205443_tigr~2.jpg
    IMG_20210926_205443_tigr~2.jpg
    1.1 MB · Views: 50

greenleaves

Senior Member
Dec 15, 2010
185
21
Philadelphia
Is your bl/modem the right one. It looks like you are using trlte bl/modem not the 9100 bl/modem.
Those are the boot-loader and modem files I got from ripee's TWRP recovery thread. On the other hand, in the last Samsung version N9100ZHU1DQH2_N9100ZZH1DQH2_TGY I found that the two modem files have different dates, 8/29/2017 and 9/15/2020. It could be the reason why it failed, but not sure. The attached shows my current bl/modem versions in version 10.

Mine is SM-N9100 duo SIM version currently running version 10. Appreciate your help and thanks for the heads-up.
 

Attachments

  • IMG_20210927_210800_tigr~3.jpg
    IMG_20210927_210800_tigr~3.jpg
    2.9 MB · Views: 30
Last edited:

timandolly

Senior Member
Jun 9, 2021
114
24
Verizon Samsung Galaxy Note 4
Those are the boot-loader and modem files I got from ripee's TWRP recovery thread. On the other hand, in the last Samsung version N9100ZHU1DQH2_N9100ZZH1DQH2_TGY I found that the two modem files have different dates, 8/29/2017 and 9/15/2020. It could be the reason why it failed, but not sure. The attached shows my current bl/modem versions in version 10.

Mine is SM-N9100 duo SIM version currently running version 10. Appreciate your help and thanks for the heads-up.
My bootloader and baseband are the same version. I don't know if this makes a difference.
 

alla_mezon

New member
Jan 5, 2011
3
0
Hello eveyone,
@ripee Could you tell us what is the ChangeLog of your 0926 (date) new build ?
I use a 910F (trlte).
Does Lineageos upgrades are profitable ? Are they integrated in your 0926 build ?
Sorry for these newbe questions... ;-)
Thank you !
 
Last edited:

eliotargy

Senior Member
Oct 24, 2013
218
16
Hangzhou
I have the 910V. There is rapid battery drain with L18. Actually, the phone gets hot and stays hot until the battery is dead. Is there a solution to this particular issue?
 

Juanpapm

Member
May 28, 2020
7
0
Hello. I got an issue and it is that I have bootloop when I install GApps after installing LineageOS. Before installing Gapps it performs well, but after that it stay in bootloop and then boot recovery after few minutes.

What should I do?

Thanks.

Sorry for my english.
 

Romaingue

Member
Sep 3, 2021
10
0
Hello, thank you for your nice developping work!
I have a N910F, without gapps, with magisk, deodexed rom and microg installed by nanodroid as a magisk module.

Some functions works very well : the gps and network are really good. I have had problems with the resurrection remix for exemple. With this rom, the gps fix is very fast. Also the lte works well. For the bluetooth I don't know, I don't use it.

I have some bugs to report, sorry if it has already been said :
- It was working at the beginning, but the phone now don't go to sleep mode. I think it's after having used the quick option "cafeine". I have had the same problem on rr rom.
- It's impossible to remove a fingerprint. It was working at the beginning, with the install fresh. I've been through worse with other descendent lineage custom roms tho. ^^
- The option to turn on the flash light is really buggy. It makes the phone reboot. And when it reboots like that, the sim card is not recognized. It's the same, I have had this problem on all lineage based roms.
- There was some bug and all my messages of a day from whatsapp have been deleted after a reboot. The application was saying that the history wasn't working. I don't know if the problem comes from the rom.
- There is a parasite noise on the sound. It can be heared when calling or with headsets. It's like white noise. And at times like an "ultrasonic" whistling. On rr rom, this kind of ultrasonic whistling was always there. I don't know if my phone has itself a problem, or if it's rom based. On the stock rom, there is no whistling, but I don't know for this background noise.
 

Romaingue

Member
Sep 3, 2021
10
0
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.
 

Romaingue

Member
Sep 3, 2021
10
0
Is the rom still under developpement?

I have noticed some other bugs :
- I tried to record the parasite sound with the video recorder present in the quick setings. The audio doesn't records (no sound on the video) when using he option "device only" (I didn't try the other recording option).
- I recorded the audio with the recorder present in the rom (the green and orange circle). It works and the parasite noise is recorded, with makes mething that it's not an hardware problem, but software.
Strangely the parasite noise is much more strong in the recording than in headset, and the music much weaker, barely hearable. Strange bug.
- Also the phone calls are very loud. Even at the minimum setting they can be too loud. This was present on all lineage based roms I've tested.

For the flashlight that makes the phone reboot, it's with the option to activate flashlight from the power button, with the screen turned off.
 

Romaingue

Member
Sep 3, 2021
10
0
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. :)
 

timandolly

Senior Member
Jun 9, 2021
114
24
Verizon Samsung Galaxy Note 4
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
 
Last edited:
  • Like
Reactions: Romaingue

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    As per previous post, 18.1-20211107 might be a working build, I'd happily try that if someone could provide it for download.

    You can download it here: 18.1-20211107
    3
    Which firmware did you used? Did the same, but still not working. I used the latest DTM firmware for N910F.
    Hi
    i have the very same issue with mobile data on my friends N910F which i got today to flash with it LOS, stock firmware was on latest DBT-N910FXXU1DRI2.

    I tried all the builds which are available for download:

    18.1-20211121 no mobile data
    18.1-20211117 no mobile data
    18.1-20211116 no mobile data
    17.1-20210414 hangs at LOS logo, never completes initial boot
    16.0-20211117 mobile data OK

    Gapps (obviously) don't make a difference, but tried with/without as well, no changes.

    As per previous post, 18.1-20211107 might be a working build, I'd happily try that if someone could provide it for download.

    @ripee, thank you very much for the great work! Let's keep fighting planned obsolescence!
    2
    I'm back from build 20211121 to 20211107 and LTE and GPS are working.
    1
    20211117 on N910f mobile data not working. WiFi is ok.
  • 60
    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.