Cool found it. here. https://xdaforums.com/t/recovery-of...-trlte-trlteduos.3933427/page-2#post-85648997 I can also confirm that it works. I have also now the android 11 working on it. didn't test the sim card in it. but the wifi part also works. Thanks for making this phone a longer time usable @ripee !
[ROM][UNOFFICIAL][11] LineageOS 18.1 [tblte][trlte][trlteduos]
- Thread starter ripee
- Start date
I'm tracking down my connection issues for the last two weeks. The problem is disconnects at low field strengths and no re-connect even with max power signal right next to a tower. A re-boot will not always fix it. That happens with each of three N910T trlte so I conclude not an hardware issue. I went back a few builds but the problem persists, adding the SIM problem. I compared with an stock LG V20 while driving which indicates identical cell signals but never disconnects.
So now I tend to believe that the ROM I flash is to blame. The earlier builds from May/June/July are not available anymore but April is which I will try next.
Please someone let me know if this is just my problem.
>>Weeks later, no improvements on the signal loss problem even with the latest builds of October/21. I flashed one of my TWRP backups and it got better to the point of what I was used to. Still bad compared to other phones. So the status is an older version (April/21) makes for better connectivity on my trlte than later versions.. Now I'm at the point to revert back to 17.1 or stock, just to prove....something.
Last edited:
I've got a very similar issue whereby when I go through a no signal area, I get a message on the top of the lock screen that says "No network - No SIM card inserted".
I have to turn phone on and off again, which just clears the message until the next time.
I'm on trlte here too.
SM-N910F
LineageOS 18.1-20210615-UNOFFICIAL-trlte
I'm confident that it is a build issue, I had it on a different ROM with my Note, and ended up using a different one that didn't have the issue.
As above, this is definitely not a hardware issue.
I have tried enabling and then disabling Airplane mode, but this doesn't work.
I have to turn phone on and off again, which just clears the message until the next time.
I'm on trlte here too.
SM-N910F
LineageOS 18.1-20210615-UNOFFICIAL-trlte
I'm confident that it is a build issue, I had it on a different ROM with my Note, and ended up using a different one that didn't have the issue.
As above, this is definitely not a hardware issue.
I have tried enabling and then disabling Airplane mode, but this doesn't work.
Last edited:
Of course "No Network" always shows during disconnects / signal loss. But the "No Sim Card" is cured starting with build 08/25. We are currently at build 09/17 and my problems started some time before your 06/15 version.
On my W8 the 0917 ROM seems to work well generally except for the GPS not tracking the phone particularly well in Google Maps when i'm driving. It's been that way the last few ROMs i've tried.
Oh, another issue I've found is that the two touch buttons at the bottom of the phone randomly light up, as if I've pressed the screen, even if I'm not touching the phone.
err... and if the phone is off, and you plug it in to charge, it will crash and you have to take the battery out to turn it back on again.
It charges still, but crashes, so I can only assume there is a missing animation which is causing the issue.
(is there a changelog or bug fix list anywhere, please?)
err... and if the phone is off, and you plug it in to charge, it will crash and you have to take the battery out to turn it back on again.
It charges still, but crashes, so I can only assume there is a missing animation which is causing the issue.
(is there a changelog or bug fix list anywhere, please?)
Last edited:
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.
bmwdroid
Senior Member
- Mar 8, 2014
- 2,195
- 1
- 925
You mean advanced restart?
Settings/system advanced /gestures/power menu
@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 ?
github.com
Thanks for this wonderful Rom, I really enjoy it, it would be great if you could help me to build the kernel Thanks! Alex
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 ?
local_manifests/trlte.xml at lineage-17.1 · apq8084/local_manifests
Contribute to apq8084/local_manifests development by creating an account on GitHub.
github.com
Thanks for this wonderful Rom, I really enjoy it, it would be great if you could help me to build the kernel Thanks! Alex
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
Last edited:
My bootloader and baseband are the same version. I don't know if this makes a difference.
I reinstalled the BL/Modem files again to make sure they are of same version. No luck, it failed to flash 0926 build with Error 1.
Have you any success with trlteduos 0926 build? Thanks
I have 3 910v phones running lineage 9/25 two through Verizon and 1 with T-Mobile
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
76
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: Whenever I try flashing any lineage-18.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
(Please read them BEFORE posting anything in the thread!)
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.
[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!FULL WIPE (with external microsd card)
How to flash LineageOS and Open GApps
FULL WIPE (without external microsd card with NO Home PC access)
FULL WIPE (without external microsd card with Home PC access)
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 Installation1. 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-1519Join us on Telegram!
LineageOS is part of the triplr_dev_users group, courtesy of tripLr.16Changelog
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.11Changelog
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.
