[ROM][UNOFFICIAL][7.1.2] LineageOS 14.1 [trlte][trlteduos]
- Thread starter jef_00
- Start date
Suddenly no network found... Note 4 (n910g)
Tried - switched of, pull sim out... But didn't work...
Tried - switched of, pull sim out... But didn't work...
Thanks now I will not trying to register my finger prints
---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------
Flashed 910G modem... Issue solved..
It's a good move, trust someone who has gone a little loopy trying to enrol fingerprints for the last month
When/if it gets fixed it should be notified on the thread and the opening post
Fingers crossed it gets fixed soon(ish)
I enabled dev option and search for fingerprint and smart lock... But couldn't find ... I am on 15.1
Dev options not needed
Both are under settings > security & privacy, then device security in the middle section, where they are under pretty much any version of lineage that supports them...
You're looking in places they arent
Thanks for replying....
I am receiving weak wifi signals... Before this I was using ported n7 ROM ... And it was all good...
Is there any solution? Earlier I flashed modem coz network issue...
Wireguard kernel suport
Upon the maturity and the stable maintenance of this build, please consider including wireguard kernel support. Thank you.
Upon the maturity and the stable maintenance of this build, please consider including wireguard kernel support. Thank you.
On 15.1 May 30th from ripee and seems to be an issue with S Pen that impacts all my drawing apps. If I'm partway through drawing a line then any part of my hand touches the screen, the pen line disappears and gets erased. I'm not aware of how this works in the background but before on 14.1 an s pen input would still continue before and after a finger input if you don't lift the pen. Now when I touch the screen while the pen is down it is like the pen is no longer in contact with the screen and drawing apps take this to mean the stroke was never finished so the lines just disappear. I use Autodesk Sketchbook most of the time and this is now happening to me regularly where it didn't on 14.1.
(I went and posted this issue on the 15.1 thread since this thread is more about the 14.1 version.)
---------- Post added at 03:08 PM ---------- Previous post was at 03:05 PM ----------
Is there somewhere I can find the last 14.1 for trlte? Looking at ripee's basketbuild everything is 15.1 now and I only see the last 5 entries. The last 14.1 trlte on mone's page is from October last year.
(I went and posted this issue on the 15.1 thread since this thread is more about the 14.1 version.)
---------- Post added at 03:08 PM ---------- Previous post was at 03:05 PM ----------
Is there somewhere I can find the last 14.1 for trlte? Looking at ripee's basketbuild everything is 15.1 now and I only see the last 5 entries. The last 14.1 trlte on mone's page is from October last year.
Last edited:
Latest 14.1 build for trlte
Hi,
Im using 14.1 a very long time and I have no time for a clean install for 15.
Can someone give me the latest build of 14.1 for trlte?
My actual build is 14.1-20180326-UNOFFICIAL-trlte.
I think there is some updated build out there of 14.1.
Thank you and sorry for my bad english
Hi,
Im using 14.1 a very long time and I have no time for a clean install for 15.
Can someone give me the latest build of 14.1 for trlte?
My actual build is 14.1-20180326-UNOFFICIAL-trlte.
I think there is some updated build out there of 14.1.
Thank you and sorry for my bad english
Hi,
Im using 14.1 a very long time and I have no time for a clean install for 15.
Can someone give me the latest build of 14.1 for trlte?
My actual build is 14.1-20180326-UNOFFICIAL-trlte.
I think there is some updated build out there of 14.1.
Thank you and sorry for my bad english
Open this thread in a web browser. You will see some buttons just above the first post. Click download. That's where the last builds are.
910f, Sudden bootloop
@ripee
Not sure if anybody is still here who could offer advice...
I have been using 09/29 since its release, and my 910f has been working perfectly. Today, out of the blue, the phone started bootlooping. Haven't flashed anything before or after that. The board was replaced just before I flashed 09/29 back then.
I can get into recovery. All I've tried was to wipe the cache. No difference.
Would be nice if I could avoid flashing anything new, but would if I really had to. Any tips, hints, or help are greatly appreciated.
@ripee
Not sure if anybody is still here who could offer advice...
I have been using 09/29 since its release, and my 910f has been working perfectly. Today, out of the blue, the phone started bootlooping. Haven't flashed anything before or after that. The board was replaced just before I flashed 09/29 back then.
I can get into recovery. All I've tried was to wipe the cache. No difference.
Would be nice if I could avoid flashing anything new, but would if I really had to. Any tips, hints, or help are greatly appreciated.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
155
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 QUESTIONSQ: When will any of the variants receive official builds from LineageOS?
(Please read them BEFORE posting anything in the thread!)
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 3 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.
[Official] Note 4 Verizon Bootloader Unlock
- ryanbg
Odin
- Odin3 v3.13.1
Heimdall
- Glass Echidna
Bootloaders and modems
- ripee
TWRP
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos
[THEME][TWRP] TWRP Materialised - Black / Dark / Light / Play [27/01/18]
- z31s1g
BasketBuild Downloader
- daktak
In the app's Settings, change Project to ripee and Device to trlte or trlteduos. Under Base Url, replace s with www.
ROMs
ripee (LineageOS su root included.)
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos
_mone
- LineageOS
LineageOS Extras
- addonsu-14.1-arm-signed.zip
- addonsu-remove-14.1-arm-signed.zip
Magisk
OpenGapps Downloader
- daktak
Open GApps
- pico
Aroma-Extras
- Creeper36
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 13.0, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 14.1 variant, which corresponds to the model of your phone!
How to flash a bootloader and/or modem and TWRP1. 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, Open GApps, and Aroma-ExtrasFULL WIPE (with external microsd card)
FULL WIPE (without external microsd card with NO Home PC access)
FULL WIPE (without external microsd card with Home PC access)
How to install SPenCommand1. 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 or Aroma-Extras 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.
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.
Bugs
- The fingerprint scanner works, but you have to go through the finger adding process twice for each finger!
- 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!
Credits
- cvxda, jef_00, lilferraro, 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
- _mone
- Corinna Vinschen
- fattire
- LineageOS
- ripee
- samsung-apq8084
XDA:DevDB Information
LineageOS 14.1 , ROM for the Samsung Galaxy Note 4
Contributors
jef_00, _mone, ripee, fattire
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Marshmallow for your variant.
Version Information
Status: Stable
Created 2017-04-13
Last Updated 2019-07-1323New Developer on XDA
Hello Guys!
I have developed a Pixel MOD for the Galaxy Note 4. This includes PixelApps, Sound, Bootanimation, Theme, Substratum .. and many more. I need 10 Thanks to make a Thread for the Mod. The Mod getting worked on Lineage EmotionOS and Emotion N Treltexx
If someone has interest, please give a Thanks so I can create the thread! Thank you20Public service announcement about the availability of my builds in the future
1. I have invested in a premium dev subscription on AFH. This will allow my build script to automatically import all of my cooked builds into each build's corresponding AFH folder as soon as it finishes uploading. Each build will become available for downloading mere minutes after uploading throughout the early morning hours, European time.
2. Thus far I have had access to my laptop, on which I build each night, on a regular basis. This will change in the coming weeks, but just because I don't post a build on a given day DOES NOT mean that I will have gotten sick of cooking LineageOS and suddenly stopped. I plan on building for all the devices linked in my signature for as long as possible while there is a dev maintaining them.
3. Just out of curiosity, I only keep the most recent 10 builds to encourage users to update and avoid reporting old bugs in old builds that may have been fixed in recent builds. I was going to stick with only one week's worth of builds but I may not be able to build daily in the future (see point 2).
