• 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

Romaingue

Member
Sep 3, 2021
10
0
Ok, thank's. I will try Viper4android.

Meanwhile, I understood that I needed to flash a separate modem and bootloader. And now the fingerprints seems to work. ;) I can add, delete, and it works well.

Also the whatsapp problem wasn't caused by the rom, but a corrupted file in my save. It works ok now.
 

Romaingue

Member
Sep 3, 2021
10
0
Ok, I have tried Viper4Android. I was able to lower the general volume. But it wasn't working. It lowers the sound, but not the static noise behind. It's like if something with too much gain was lowered after.

I've tried to edit the "mixer_paths.xml" file, but it doesn't change the sound level. I don't know enough to do that. :unsure:
 
Last edited:

croc_87

Member
Aug 14, 2021
26
0
I have the phone full working now the N915FY with android 11. I have a question is the fast charging doesn't look to work. is this disabled or is any image or notification may be switched off? Can someone confirm or do I have to enable it in settings ? Already thanks for the reply.
 

ripee

Recognized Developer / Recognized Contributor
I have the phone full working now the N915FY with android 11. I have a question is the fast charging doesn't look to work. is this disabled or is any image or notification may be switched off? Can someone confirm or do I have to enable it in settings ? Already thanks for the reply.
I added the fast charging toggle to the settings, but I'm trying to figure out how to enable the lock screen message that it's charging slowly or rapidly.
 

croc_87

Member
Aug 14, 2021
26
0
I added the fast charging toggle to the settings, but I'm trying to figure out how to enable the lock screen message that it's charging slowly or rapidly.
Oke, I place a USB with voltage and current checker and it is charging with 9V. So it looks that works only it doesn't say fast charging anymore as a message. Not a big thing yet but I Normally got it always. So maybe it's a habit to see. Is it a big thing to get the message or maybe add as other led color light indicator is also good or change the battery image in the corner :) I understand you want the message , me 2 ;) but love the work that is done! Now thinking about it. can't you check on the PD command message? normally you send a command to the charger and says command back to the mobile yeah charging with fast charging.
 
Last edited:

Romaingue

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

Attachments

  • mixer_paths_ok75sur vals.xml
    69.2 KB · Views: 9

ripee

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

Romaingue

Member
Sep 3, 2021
10
0
Ok, very nice, thanks!
In the file I sent there was only modifications on a part of the values.
I have done it better here, I modified all the rx1 and rx2 values to 78. Also rx3/4/6/7 at 78 at the beginning of the file. And let rx5 at 88 because it seems to be the speaker.
78 is a compromise, it can be heard a little noise, but very faint. At 75 the voice calls are a little too low.
Ideally I think that around 80 would be nice for calls with headphone and headset. And 75 for games, video, audio. I don't know enough to do it.
Also there is the mixed_paths_i2s, I don't know what is it's purpose, so I didn't modify it. (Maybe a viper or audio fx related file?)

I join the new file with volume at 78.
 

Attachments

  • mixer_paths-78.xml
    69.2 KB · Views: 4

Romaingue

Member
Sep 3, 2021
10
0
There is also a minor glitch when you split the app. At the point of selecting the second app. Either in portrait or landscape mode, it doesn't fills all the screen size.
After having selected a second app, it works ok, the 2 apps share half of the screen.
Sorry for the bad news... 🙃
 

Romaingue

Member
Sep 3, 2021
10
0
There is also a minor glitch when you split the app. At the point of selecting the second app. Either in portrait or landscape mode, it doesn't fills all the screen size.
After having selected a second app, it works ok, the 2 apps share half of the screen.
Sorry for the bad news... 🙃
 

Attachments

  • Screenshot_20211005-154036_Trebuchet.png
    Screenshot_20211005-154036_Trebuchet.png
    3.1 MB · Views: 31
  • Screenshot_20211005-154059_Fennec.png
    Screenshot_20211005-154059_Fennec.png
    3.7 MB · Views: 32

timandolly

Senior Member
Jun 9, 2021
114
24
Verizon Samsung Galaxy Note 4
O
Ok, very nice, thanks!
In the file I sent there was only modifications on a part of the values.
I have done it better here, I modified all the rx1 and rx2 values to 78. Also rx3/4/6/7 at 78 at the beginning of the file. And let rx5 at 88 because it seems to be the speaker.
78 is a compromise, it can be heard a little noise, but very faint. At 75 the voice calls are a little too low.
Ideally I think that around 80 would be nice for calls with headphone and headset. And 75 for games, video, audio. I don't know enough to do it.
Also there is the mixed_paths_i2s, I don't know what is it's purpose, so I didn't modify it. (Maybe a viper or audio fx related file?)

I join the new file with volume at 78.
On the 910V I have no static in phone speaker Bluetooth or wired head phones. I have three phones and none of them have any static.
 

Reinhard79111

Member
Sep 19, 2016
34
6
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?
Screenshot vices_Core.jpg
 

ripee

Recognized Developer / Recognized Contributor
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.
 

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.
Another attempt to clean flash the latest 1006 build but it failed again with Error 1. I tried to reflash the stock boot.img. Again, it did not work. Any idea? Appreciate any help. Thanks.
 

Reinhard79111

Member
Sep 19, 2016
34
6
Thanks for your advice.
If someone's interested, here is how to get signature spoofing in Android 11:
1) install riru module via magsik
2) install riru-lsposed module via magisk
3) install lsposed manager apk
4) install fakegapps fork from whew-inc
5) activate fakegapps inside lsposed manager
6) restart - now signature spoofing is enabled in microg
 
  • Love
Reactions: breversa

tharg2

New member
Oct 7, 2021
4
2
I've had to revert to 0926 build after huge standby battery drain on 1005 (even in flight mode). Back on 0926 all is good again.
 

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.