Code:
/*
* Your warranty will be VOID after installing a custom ROM.
*
* Get notified yourself that I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you 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 me for messing up your device,
* I will laugh at you.
*/
# LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
# What's working
WIP: Almost all look working fine as much as my LineageOS 19.1 does except the lists below
# What's not working
LTE (SM-T825)
USB OTG
SELinux permissive
Data encryption (FBE, FDE)
Please see the "Known issues" part of this post
# Downloads
## LineageOS 20.0
Galaxy Tab S3 LTE (gts3llte, SM-T825)
Galaxy Tab S3 WiFi (gts3lwifi, SM-T820)
## Google Apps
NikGapps
The other Gapps will work too, but I only confirmed that NikGapps working
## TWRP Recovery
You can use mine, please visit this thread.
[RECOVERY][SM-T820][SM-T825][UNOFFICIAL] TWRP for Galaxy Tab S3
# How to install
To fix the boot-loop problem, we need to install the previous custom ROM at least once.
Unlock the bootloader.
Download TWRP and flash the recovery image via Odin.
Download any Android 11/12 based custom ROM, such as LineageOS 19.1 for Galaxy Tab S3.
Download LineageOS 20.0 for Galaxy Tab S3.
Be aware of the board name.
Download GAPPS for Android 13 and the others you want to flash.
Enter TWRP recovery.
The first boot to TWRP might be very slow because of the unmatched file systems.
Format the whole system, data, cache partitions using the format menu.
You will type `yes` to do that.
Install Android 11/12 based custom ROM, such as LineageOS 19.1.
Boot once, and if the initial setup screen appears then reboot and enter the TWRP again.
Erase the partitions using the advanced wipe option.
It'd be the system, data, caches, and internal storage.
Flash the images, including LineageOS 20.
If you're going to install GApps or something, you have to install the LineageOS first.
Reboot the system.
Done.
# Known issues
Camera somewhat buggy
On webcam chat apps, there is a vertical green bar and the color is not properly displayed.
Audio bugs
No sound for the microphone and speaker in voice calls, such as the regular phone call or voice chat with a meeting app.
Boot-loop after formatting data partition in TWRP
For an unknown reason, we can't use it after formatting partitions using the format menu in our TWRP. Please refer to the installation instruction.
Thank all of you for the feedback
# Sources
Device Tree
gts3l-common: https://github.com/awesometic/android_device_samsung_gts3l-common
gts3llte: https://github.com/awesometic/android_device_samsung_gts3llte
gts3lwifi: https://github.com/awesometic/android_device_samsung_gts3lwifi
Kernel: https://github.com/awesometic/android_kernel_samsung_msm8996
Vendor: https://github.com/awesometic/proprietary_vendor_samsung
# Telegram Groups
If you are interested in developing this potential machine, please tell me through PM then I will send you the invitation link.
If you need a general discussion channel for this potential machine or want to share the news of its Android projects from anyone to everyone, you can join our discussion group chat.
Galaxy Tab S3 General Discussion
# Buy me a coffee
If you like my efforts or would like to support me, please don't hesitate to buy me a cup of coffee.
https://www.paypal.com/paypalme/awesometic
# Credits / Special thanks to
Android Open Source Project
LineageOS Team
LOS17.1) @Valera1978 for his amazing previous work including his MSM8996 kernel
LOS18.1) @supermike86 and @samsuffit for testing LineageOS 18.1 for T820, which is I don't have one
LOS18.1) @bmwdroid and @cherepanov for confirming the LTE works
LOS18.1) @sebmue for letting me know that the useful information for palm rejection, and @ghostwheel for sharing its working source codes on Android 9
General) @switchgott for helping me in the development discussion and creating Telegram groups
General) All from our Telegram discussion channel, @EonOfBlack , Sands, David Becker, ...
LOS18.1) @LuK1337 for giving me a hint to fix the quad-speakers
LOS19.1) @followmsi , @html6405 , @ThE_MarD for giving me a hint to bring up Android 12
LOS19.1) @masdaster for the fix of MDFPP Keystore on our device
## Changelogs
2023. 2. 13
Synced with the latest LineageOS sources
2023. 1. 2
Synced with the latest LineageOS sources
Minor improvements
2022. 10. 27
Initial release
## Special Notes
You must do clean-install if you are willing to upgrade from another ROM such as an Android 11, 12 based one
Keep in mind that this is on the ALPHA stage, please backup your previous system and data
reserved
Getting Boot-Loop
(t825 lte/wifi version),
TWRP 3.6.0_9.0
wiped everything
then format data -> yes,
then flashed rom ,
flashed nikgapps 13
Boot logo -> Lineage Loading Screen -> reboot -> Boot logo -> Lineage Loading Screen.... loop
bouuman said:
Getting Boot-Loop
(t825 lte/wifi version),
TWRP 3.6.0_9.0
wiped everything
then format data -> yes,
then flashed rom ,
flashed nikgapps 13
Boot logo -> Lineage Loading Screen -> reboot -> Boot logo -> Lineage Loading Screen.... loop
Click to expand...
Click to collapse
So do I. I tried several times and failed . same issue.
bouuman said:
Getting Boot-Loop
(t825 lte/wifi version),
TWRP 3.6.0_9.0
wiped everything
then format data -> yes,
then flashed rom ,
flashed nikgapps 13
Boot logo -> Lineage Loading Screen -> reboot -> Boot logo -> Lineage Loading Screen.... loop
Click to expand...
Click to collapse
doridori88 said:
So do I. I tried several times and failed . same issue.
Click to expand...
Click to collapse
Sorry for the inconvenience. I will look into on my side. It works well for me after clean install, but maybe something goes wrong.
Is there anyone who can give me the logcat of this issue?
First of all, thank you very much for the effort, Regarding the bootloop I did a test, if I perform a clean installation the system starts booting, but if I perform the dirty flash the system starts normally
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm using the LTE model, and previously used the crdroid release with no issues.
After a factory reset (wipe data/cache/system) I flashed this rom WITHOUT any gapps or magisk and I confirm a successful installation and able to boot and use normally.
After a few hours I rebooted, flashed bitgapps 1.6 and that went well too no bootloops and I'm able to install my applications as normal.
1) To remove the bottom taskbar:
Settings > System > Buttons > Toggle onscreen nav bar so it's enabled/lights up > go to previous menu then return back > new task bar button will appear > turn it off then bottom taskbar will turn black/default android > then disable/turn off the topmost "enable task bar" toggle > bottom bar now disappears permanently
2) Allow network access to google services
Sometimes both google services and google play store will appear offline/you can't sign in/can't download apps
Go to Settings > Apps > Google Play Store (and Google Services) > Mobile data & WiFi > toggle Allow Network Access
EDIT: go to android settings > your network's WiFi settings, and toggle so it's set to unmetered, sometimes play store won't work if its set to Automatic (I.e. it decides that your WiFi is metered therefore it won't download)
You're welcome
Dirty flash worked true, lineage 19.1+nikgapps12L, start Lineage, then flash lineage 20+nikgapps13. Works as workaround to flash this rom.
Pact said:
I'm using the LTE model, and previously used the crdroid release with no issues.
After a factory reset (wipe data/cache/system) I flashed this rom WITHOUT any gapps or magisk and I confirm a successful installation and able to boot and use normally.
After a few hours I rebooted, flashed bitgapps 1.6 and that went well too no bootloops and I'm able to install my applications as normal.
1) To remove the bottom taskbar:
Settings > System > Buttons > Toggle onscreen nav bar so it's enabled/lights up > go to previous menu then return back > new task bar button will appear > turn it off then bottom taskbar will turn black/default android > then disable/turn off the topmost "enable task bar" toggle > bottom bar now disappears permanently
2) Allow network access to google services
Sometimes both google services and google play store will appear offline/you can't sign in/can't download apps
Go to Settings > Apps > Google Play Store (and Google Services) > Mobile data & WiFi > toggle Allow Network Access
EDIT: go to android settings > your network's WiFi settings, and toggle so it's set to unmetered, sometimes play store won't work if its set to Automatic (I.e. it decides that your WiFi is metered therefore it won't download)
You're welcome
Click to expand...
Click to collapse
Thank You!
Not sure if the trick is to do "format data" (data/cache/system) and NOT to format->yes ... because i did it like you said:
format data wipe data/cache/system then i DIDNT->"format->yes" and flashed rom20+nikgapps13, rom started.
Usually i wipe everything (only not external storage ofc) and then i do format->yes... with this method i get boot-loops in this rom.
bouuman said:
Thank You!
Not sure if the trick is to do "format data" (data/cache/system) and NOT to format->yes ... because i did it like you said:
format data wipe data/cache/system then i DIDNT->"format->yes" and flashed rom20+nikgapps13, rom started.
Usually i wipe everything (only not external storage ofc) and then i do format->yes... with this method i get boot-loops in this rom.
Click to expand...
Click to collapse
Yeah I confirm I did not do the step that requires typing "yes"
Instead I just did the factory reset wipe where it just wipes /data and only after that did I go to advanced wipe and ticked and wiped /system /data /cache - three separate options in one go, and after that I flashed the ROM as usual.
Though the bootloop is probably due to flashing both the ROM and gapps in one go instead of rebooting first.
Pact said:
Yeah I confirm I did not do the step that requires typing "yes"
Instead I just did the factory reset wipe where it just wipes /data and only after that did I go to advanced wipe and ticked and wiped /system /data /cache - three separate options in one go, and after that I flashed the ROM as usual.
Though the bootloop is probably due to flashing both the ROM and gapps in one go instead of rebooting first.
Click to expand...
Click to collapse
so format-data may be the problem which cause boot loops.
Clean install on T820 but keeps getting "Failed to map" the ROM file and "Error installing the zip" errors. Installation failed.
Tried both TWRP 3.6.0_9.0 and 3.5.2_9.0
Wiped everything then format data
then flashed the new rom and got "Failed to map" error.
Appreciate any help. Thank you.
Looks like formatting data partition using TWRP is the culprit for this situation. I will check them
Sorry for the inconvenience.
Awesometic said:
Looks like formatting data partition using TWRP is the culprit for this situation. I will check them
Sorry for the inconvenience.
Click to expand...
Click to collapse
How can we fix LTE issue for SM-T825?
Awesometic said:
Looks like formatting data partition using TWRP is the culprit for this situation. I will check them
Sorry for the inconvenience.
Click to expand...
Click to collapse
Take your time, thank you for your hard work and for keeping this excellent device alive!
Awesometic said:
Code:
/*
* Your warranty will be VOID after installing a custom ROM.
*
* Get notified yourself that I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you 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 me for messing up your device,
* I will laugh at you.
*/
# LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
# What's working
WIP: Almost all look working fine as much as my LineageOS 19.1 does except the lists below
# Untested
FBE for userdata
# What's not working
LTE (SM-T825)
USB OTG
SELinux permissive
Please see the "Known issues" part of this post
# Downloads
## LineageOS 20.0
Galaxy Tab S3 LTE (gts3llte, SM-T825)
Galaxy Tab S3 WiFi (gts3lwifi, SM-T820)
## Google Apps
NikGapps
The other Gapps will work too, but I only confirmed that NikGapps working
## TWRP Recovery
You can use mine, please visit this thread.
[RECOVERY][SM-T820][SM-T825][UNOFFICIAL] TWRP for Galaxy Tab S3
# How to install
Unlock the bootloader.
Download TWRP and flash the recovery image via Odin.
Download LineageOS 20.0 for Galaxy Tab S3.
Be aware of the board name.
Download GAPPS for Android 13 and the others you want to flash.
Enter TWRP recovery.
The first boot to TWRP might be very slow because of the unmatched file systems.
Format the whole system, data, cache partitions using the format menu.
You will type `yes` to do that.
Flash the images.
If you're going to install GApps or something, you have to install the LineageOS first.
Reboot the system.
Done.
# Known issues
Camera somewhat buggy
On webcam chat apps, there is a vertical green bar and the color is not properly displayed.
Audio bugs
No sound for the microphone and speaker in voice calls, such as the regular phone call or voice chat with a meeting app.
Thank all of you for the feedback
# Sources
Device Tree
gts3l-common: https://github.com/awesometic/android_device_samsung_gts3l-common
gts3llte: https://github.com/awesometic/android_device_samsung_gts3llte
gts3lwifi: https://github.com/awesometic/android_device_samsung_gts3lwifi
Kernel: https://github.com/awesometic/android_kernel_samsung_msm8996
Vendor: https://github.com/awesometic/proprietary_vendor_samsung
# Telegram Groups
If you are interested in developing this potential machine, please tell me through PM then I will send you the invitation link.
If you need a general discussion channel for this potential machine or want to share the news of its Android projects from anyone to everyone, you can join our discussion group chat.
Galaxy Tab S3 General Discussion
# Buy me a coffee
If you like my efforts or would like to support me, please don't hesitate to buy me a cup of coffee.
https://www.paypal.com/paypalme/awesometic
# Credits / Special thanks to
Android Open Source Project
LineageOS Team
LOS17.1) @Valera1978 for his amazing previous work including his MSM8996 kernel
LOS18.1) @supermike86 and @samsuffit for testing LineageOS 18.1 for T820, which is I don't have one
LOS18.1) @bmwdroid and @cherepanov for confirming the LTE works
LOS18.1) @sebmue for letting me know that the useful information for palm rejection, and @ghostwheel for sharing its working source codes on Android 9
General) @switchgott for helping me in the development discussion and creating Telegram groups
General) All from our Telegram discussion channel, @EonOfBlack , Sands, David Becker, ...
LOS18.1) @LuK1337 for giving me a hint to fix the quad-speakers
LOS19.1) @followmsi , @html6405 , @ThE_MarD for giving me a hint to bring up Android 12
LOS19.1) @masdaster for the fix of MDFPP Keystore on ou
Click to expand...
Click to collapse
Deleted !
Concept48 said:
UPDATE : Format data unfortunately brings up bootloop as you will see in the video , I will flash A12 CRDROID to it , do a normal wipe and upgrade to 13 - results soon
Click to expand...
Click to collapse
1.) flashing previous lineage19 a12L version,
2.) then wipe (without formatting after wipe),
3.) then flash lineage 20 a13,
works too. This rom can be flashed like this, without bootloops and works great.
Tested 2 days looks good so far.
bouuman said:
flashing previous lineage19 version, then wipe without formatting, then lineage 20, works too. Tested 2 days looks good so far.
Click to expand...
Click to collapse
deleted
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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: When will any of the variants receive official builds from LineageOS?
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)
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 and optionally Aroma-Extras,
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 and optionally Aroma-Extras,
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 and optionally Aroma-Extras,
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.
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-13
Reserved
Reserved
this build is special for @ripee
changelog:
fixed recent view borders
jef_00 said:
this build is special for @ripee
changelog:
fixed recent view borders
Click to expand...
Click to collapse
Thank you for the mention and of course for your hard work, @jef_00
I'll flash it tomorrow afternoon cuz I have an early morning tomorrow.
Does this work with the 910T? Any support for 10,000mAh battery?
ripee said:
Thank you for the mention and of course for your hard work, @jef_00
I'll flash it tomorrow afternoon cuz I have an early morning tomorrow.
Click to expand...
Click to collapse
No problem mate! @ripee
Rick7C2 said:
Does this work with the 910T? Any support for 10,000mAh battery?
Click to expand...
Click to collapse
Not yet sorry!
Can anyone make data for tmobile N4?
Sent from my SM-G935F using XDA-Developers Legacy app
@jef_00
_mone said:
Clone, fork, rebase, merge, do whatever you want with the repos, but please share it; we are here for that!
Click to expand...
Click to collapse
I don't mind if you copy/paste my thread but, please, add the links to the source that you're using.
Rick7C2 said:
Does this work with the 910T? Any support for 10,000mAh battery?
Click to expand...
Click to collapse
jef_00 said:
Not yet sorry!
Click to expand...
Click to collapse
Is that no on the 910T, or no on the 10 AH battery?
I have a 910T and would love to try this build.
Didn't the trltexx CM build work on the 910T?
I had some time to flash build 01/11. The recent tiles are definitely fixed!
I guess now attention can be turned to the fingerprint scanner?
I also noticed that the setting to have the display save power is missing from LiveDisplay, the one usually at the bottom of that submenu.
Thank you @jef_00!
_mone said:
@jef_00
I don't mind if you copy/paste my thread but, please, add the links to the source that you're using.
Click to expand...
Click to collapse
it is done sorry about copy/paste
Just flashed the ROM, wiped cache/dalvik cache and booted.
First impressions:
-Turning the screen on is quite slow like on all non-TouchWiz roms I've tried in the past compared to TW roms (I come from x-rom Note7 port rom). Unlike CM13 on the LG G2
I have no idea why no one talks about this. It takes around 1.4 seconds to show the lockscreen, around 40% more than stock roms.
-Low volume when listening to voice clip recorded by myself on Whatsapp from earpiece
-During the first 15 minutes with the phone I experienced constant freezings (3+ sec. duration) very often while scrolling anywhere. Settings app seems to stop responding too often, perhaps it's related to the freezings. However, right now as I'm writing this I don't seem to be experiencing them anymore...
-After using the phone for 30+ minutes the automatic rotation stops working (only works on camera app).
-Half the translation is in English instead of in Spanish some of which are erratic (Under Gestures: "Proximity wake up: wake up when shaking the phone". Those are two different things.)
- No way to set a different vibration intensity on capacitive buttons (too strong by default IMO).
-Duplicate contacts on DIALER APP (due to having contacts on whatsapp). Went to contacts app-->contacts to show--> set only Google contacts and they stop showing duplicated only on contact app, not on the dialer app. You did it again Google! I saw this stupid behavior back in CM13.
Things I liked/surprised me:
-Built-in option to disable home button from waking up the device.
-Show notifications (black and white screen, ideal for amoled screen phones) when uncovering proximity sensor.
-Speed in general.
The slow lock screen turning on isn't restricted to this rom, as you wrote.
You can link contacts together in the settings of each contact.
The rotation bug is well known throughout 14.1 aosp-based roms for all devices.
ripee said:
The slow lock screen turning on isn't restricted to this rom, as you wrote.
You can link contacts together in the settings of each contact.
The rotation bug is well known throughout 14.1 aosp-based roms for all devices.
Click to expand...
Click to collapse
What is it restricted to?
About the contacts...so if I have 1M contacts I have to spend my whole life doing that task? Haha.
aLexzkter said:
What is it restricted to?
About the contacts...so if I have 1M contacts I have to spend my whole life doing that task? Haha.
Click to expand...
Click to collapse
It's restricted to all 7.1.1 aosp roms.
Only for those who are in multiple accounts. I have 250 and I linked about 75 in total.
ripee said:
It's restricted to all 7.1.1 aosp roms.
Only for those who are in multiple accounts. I have 250 and I linked about 75 in total.
Click to expand...
Click to collapse
I experienced it on all 6.0.1 aosp roms too...
Tanks for this ROM!!!
jef_00 said:
this build is special for @ripee
changelog:
fixed recent view borders
Click to expand...
Click to collapse
Hi jef_00 ! Im back again to Test Your ROMs. Thanksf or this Build. (Sorry that I was a Longer Time "Out"). My PC was Totaly Damaged. So I cant Flash and Testing Your CM13 Builds. Now Im back.
SUREFACE said:
Hi jef_00 ! Im back again to Test Your ROMs. Thanksf or this Build. (Sorry that I was a Longer Time "Out"). My PC was Totaly Damaged. So I cant Flash and Testing Your CM13 Builds. Now Im back.
Click to expand...
Click to collapse
glad you are back!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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-15.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.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
Q: When will any of the variants receive official builds from LineageOS?
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 4 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 for Samsung Galaxy Note 4 (Qualcomm)
[THEME][TWRP] TWRP Materialised - Black / Dark / Light / Play [27/01/18]
- z31s1g
Open GApps
OFFICIAL !!
I am not building for oreo anymore, devs have moved to pie,
thanks everyone !!
tripLr
Code:
LAST ROM Downloads for Oreo
triplr
Source Code http://www.github.com/tripLr
@kevintm78 kernel development
https://forum.xda-developers.com/note-4/snapdragon-dev/kernel-flashpoint-v3-1-stock-n7-ports-t-t3727407
(LineageOS su root included.)
ROMs Note 4
SM-N910F/G/P/R4/T/T3/V/W8:
click to open trlte drive folder
https://drive.google.com/drive/folders/1XWrdmxHeC0A7zGK-TGOH3XG2VfKYP-IA?usp=sharing
<build date>.zip <flashable zip>
<build date>.zip.md5sum <md5 checksum for build>
<build date>.zip.img <backup kernel image install image in twrp>
ROMs Note 4 Edge
Note 4 Edge Thanks to @micky387 and @ripee
Which device is supported ??
I'm do the best for support multi note edge device so tell me if you see an issue and write it here with you variant
Support SM-N915F SM-N915FY SM-N915G SM-N915T SM-N915P SM-N915V
Click to expand...
Click to collapse
Google Drive Download Folder Click to open and browse to latest
https://drive.google.com/drive/folders/1lD5vLRFYr8XyGIgL2oT9VXFmdcLOWe3F?usp=sharing
file names
<build date>.zip <flashable zip>
<build date>.zip.md5sum <md5 checksum for build>
<build date>.zip.img <backup kernel image install image in twrp>
ROMs Note 4 DUOS
- SM-N9100ZC/ZH/6W/9W:
click to open trlte duos folder
https://drive.google.com/drive/folders/1uibdRnVs9-klbJhtvB5__5B9XFYel1jK?usp=sharing
file names
<build date>.zip <flashable zip>
<build date>.zip.md5sum <md5 checksum for build>
<build date>.zip.img <backup kernel image install image in twrp>
Code:
# Depreciated
[B]ripee[/B] [I]([COLOR="Teal"]LineageOS[/COLOR] su root included.)[/I]
- SM-N910F/G/P/R4/T/T3/V/W8: [URL="https://forum.xda-developers.com/devdb/project/dl/?id=31259"][B]
lineage-15.1-20190218-UNOFFICIAL-trlte.zip[/B][/URL]
- SM-N9100ZC/ZH/6W/9W: [URL="https://forum.xda-developers.com/devdb/project/dl/?id=31260"][B]
lineage-15.1-20190218-UNOFFICIAL-trlteduos.zip[/B][/URL]
[B]_mone[/B]
- [URL="https://androidfilehost.com/?w=files&flid=140308&sort_by=date&sort_dir=DESC"][B]LineageOS[/B][/URL]
[B]micky387[/B]
- SM-N910F/G/P/R4/T/T3/V/W8: [URL="https://androidfilehost.com/?w=files&flid=257279&sort_by=date&sort_dir=DESC"][B]Note 4[/B][/URL]
[/CODE]LineageOS Extras
- addonsu-15.1-arm-signed.zip
- addonsu-remove-15.1-arm-signed.zip
Magisk
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, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 15.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 and Open GAppsFULL 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.
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 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
- Temporary fix for random SIM death on all trlte variants, courtesy of _mone: boot-1223-trlte.img
- The fingerprint scanner has not yet been integrated into either trlte or trlteduos.
- The front camera force closes, requiring a reboot to work again.
- Bluetooth does not see some wearable devices.
- 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!
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
- fattire 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
- LineageOS
- triplr-dev
XDA:DevDB Information
LineageOS 15.1, ROM for the Samsung Galaxy Note 4
Contributors
micky387, ripee, tripLr, _mone, cvxda
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Marshmallow for your variant.
Version Information
Status: Snapshot
Current Stable Version: 8.1.0
Created 2018-03-09
Last Updated 2019-07-13
Reserved
Reserved
known bugs?
Rom for note 4 duos N9100???
I am gonna test it now on N910T and will report back.
Thank you.
.
By the way i got some cool amoled wallpapers of lineage os below.
Thx ,keep the note 4 alive ,I will try this weekend
aafranki said:
known bugs?
Click to expand...
Click to collapse
Some camera issue (minor) and ??
merc200k said:
Rom for note 4 duos N9100???
Click to expand...
Click to collapse
Not support
Trex888 said:
I am gonna test it now on N910T and will report back.
Thank you.
Click to expand...
Click to collapse
Perfect ,report after
Becareful read closely OP.
When @ripee or @_mone are ready , they will continue this project
not support N9100??? so I cant test it..
maybe in the future?
Downloading it for the N910F. Gonna test it tonight. Thanks!
edit: ok, installed fine. But no sounds for the speaker, nothing.
Fingerprint dosnt work.No sound too.
Sound is not in this package
nisi3nt said:
Sound is not in this package
Click to expand...
Click to collapse
bt don't work, call sound don't work, speaker sound don't work= phone inusable
petzku said:
Downloading it for the N910F. Gonna test it tonight. Thanks!
edit: ok, installed fine. But no sounds for the speaker, nothing.
Click to expand...
Click to collapse
scpeter1 said:
Fingerprint dosnt work.No sound too.
Click to expand...
Click to collapse
nisi3nt said:
Sound is not in this package
Click to expand...
Click to collapse
aafranki said:
bt don't work, call sound don't work, speaker sound don't work= phone inusable
Click to expand...
Click to collapse
Yes ,error in script.
Upload in progress with new build.
Sorry for this mistake
aafranki said:
bt don't work, call sound don't work, speaker sound don't work= phone inusable
Click to expand...
Click to collapse
That's right but I am jockeying a little the dev well fix this in the next update
nisi3nt said:
That's right but I am jockeying a little the dev well fix this in the next update
Click to expand...
Click to collapse
Yes, Done. New build available in Op
Sorry again
micky387 said:
Yes, Done. New build available in Op
Sorry again
Click to expand...
Click to collapse
download link?
hmm link dosen work error 404
micky387 said:
Yes, Done. New build available in Op
Sorry again
Click to expand...
Click to collapse
Rom dl Link not working.
Fingerprint dosntworking again.Sound is back.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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-16.0 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.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
Q: When will any of the variants receive official builds from LineageOS?
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 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 5 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
triplr
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos
- SM-N915F/G/P/R4/T/W8: tblte
_mone
- LineageOS
LineageOS Extras
- addonsu-16.0-arm-signed.zip
- addonsu-remove-16.0-arm-signed.zip
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 16.0 variant, which corresponds to the model of your phone!
How to flash LineageOS and Open GAppsFULL 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 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
- 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 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 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 16.0, ROM for the Samsung Galaxy Note 4
Contributors
ripee, _mone, mobspyguy, khalvat, cvxda, tripLr
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Marshmallow for your variant.
Version Information
Status: Stable
Current Stable Version: 9
Stable Release Date: 2019-02-16
Created 2019-02-16
Last Updated 2020-04-04
Reserved
Join us on Telegram!
LineageOS is part of the triplr_dev_users group, courtesy of tripLr.
Reserved
Please create this RAM for Exynos SM-N910c phones. We are waiting for your goodness.
hamid6831 said:
Please create this RAM for Exynos SM-N910c phones. We are waiting for your goodness.
Click to expand...
Click to collapse
As has been explained in every Qualcomm thread, what you are asking for is like trying to grow oranges using tomato seeds. Please contact the appropriate dev in the appropriate forum about Exynos support.
It's not really important at all, but is there a way to change the boot logo on this ROM (the Galaxy Note 4 logo displayed when starting the phone)? I tried to extract param.bin, it didn't work
Rom , after a total clean flash with Open Pico Gapps and Magisk 18.1, has booted up in just 2 minutes.
Android setup finished in less than a minute.
No hick ups, no errors.
Everything has run smooth and fast.
This is a job very well done.
Thank you all for taking us to the next level of Android.
Thank you @ripee, thank you @_mone , thank you @mobspyguy
Unofficial lineageos pie superuser add on
https://androidfilehost.com/?fid=11410963190603875495
Works on my tab s2
Credit
https://forum.xda-developers.com/moto-g-2014/orig-development/rom-lineageos-16-0-t3833953/page1
Lets have a look inside it
holy crap, will be trying this asap
piemanny said:
holy crap, will be trying this asap
Click to expand...
Click to collapse
Love your username
---------- Post added at 10:21 PM ---------- Previous post was at 10:17 PM ----------
First time I have ever seen ALL MY WIFI
Without having to edit nvram_net.txt
Had a issue installing from a otg.
WiFi is extremely fast on 5gz.
Downloading my gapps.
Sofar what I need works with ROM only.
Awesome
---------- Post added at 11:00 PM ---------- Previous post was at 10:21 PM ----------
FYI, when installing without su or any gapps, root may be enabled for adb in developer mode. Don't know what it does but the selection is there.
Stock ROM no gapps
Everything works
Except ... Fingerprint
And low mic volume
Still wow.
Gapps pico and supersu
Typing in this app doesn't show each letter
As you go. Weird. Oh, battery was low. Put on charger, back to normal.
Bluetooth works
tripLr said:
Stock ROM no gapps
Gapps pico and supersu
Typing in this app doesn't show each letter
As you go. Weird. Oh, battery was low. Put on charger, back to normal.
Bluetooth works
Click to expand...
Click to collapse
Here same strange thing.
Typing message in XDA App and cannt really see what you type.
after a while, or when hit ender, letters show up..
Pico Gapps with magisk, battery foul.
So, its not battery related, or root.
logosA said:
Lets have a look inside it
Click to expand...
Click to collapse
Can I add these to the OP?
ripee said:
Can I add these to the OP?
Click to expand...
Click to collapse
of cource you can.
Its your work after all
logosA said:
of cource you can.
Its your work after all
Click to expand...
Click to collapse
Thanks but it's _mone's and mobspyguy's work
Sim Death....or No Service
For what its worth, even with an earlier modem (and i even rolled back the 1st 6.0.1 modem available for my region N910GDTU1DPF4), i still get the occasional sim death..not quite as bad as on Oero though
Usually i would manually reset the Ril Daemon via RIl Control from F-Droid
Today i finally got tired of doing this manually and set out to automate ril restarting with tasker
Please note i have never used Tasker before, so my shared profile may be less than ideal, im open for suggestions from more seasoned users, but for me it works well enough, or it seems to....
Tasker profile removed - it just wasnt as effective as Automate, harder to use, and unreliable in its State function....
Meanwhile i have been using Automate and testing this Automate flow i cobbled together - Updated 19/02/19 (similar to Tasker, but waaay easier to work with, flowchart based...) It currently checks for mobile connectivity every 5 minutes, and restarts ril-daemon if needed
The Automate way seems to be working better than Tasker....like u said I've not used Tasker before, and its horribly complicated compared to Automate...
Update: As of using my last Automate flowchart (updated above this morning), i have had zero sim death, dunno why, maybe polling connectivity every 5 minutes is enough to stop sim death, it hasnt gotten as far as the ril-daemon restart so far...will update if it does....
Of course, i spoke too soon, and jinxed myself
An hour after my last update i finally had my first sim death/ril-daemon reset...still, it was automatically recovered
I've tried this and mobspyguy's rom. the problem I have is that in my area I have good lte and data signal with these roms. But for some reason I have to drive 3 miles out of town before I can make a call. I'm on N910v straight talk on verizon network. P. S. The data works great while I'm at home just can't make calls.
Anyone run into SDCard showing as corrupted
ninja_unmatched said:
Anyone run into SDCard showing as corrupted
Click to expand...
Click to collapse
Although this shouldn't be the case, going from one version to another, your sd card can usually be expected to work best when you format it with the new version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
[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 GAppsFULL 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 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-15
Join us on Telegram!
LineageOS is part of the triplr_dev_users group, courtesy of tripLr.
Reserved
thank you dev for everything
Thank you for talking us to the next level
KUDOS
Congrats on the release ripee ! :good:
Well done ripee!
Hat off for your work.
Amazing! Thank you so much, ripee! I haven't tried this ROM yet, but am looking forward to it!
@ripee
there is no lineage-17 ROM in the tblte dir (or duos) - only 16
zan44 said:
@ripee
there is no lineage-17 ROM in the tblte dir (or duos) - only 16
Click to expand...
Click to collapse
I just flashed, all are running smooth, Thank for your hard work.
Well done! @ripee
Special shout out to @ghostwheel for showing us the debugging tools and how to use them .
And all the other devs who have brought up 32 bit devices into Android Q.
" If you put your mind to it nothing is impossible "
??
Did a clean install. Starts to boot then turns off the phone. SM-910V
very good work, keep it up.
Enviado desde mi Nexus 9 mediante Tapatalk
I dont think Note4 had a faster rom than this, before
Can someone tell me if playstore have all applications like Waze in it, please ?
Good job team !
Interesting, I'll have to wait until Google let me download it.
Well done ripee and team.
Running well, fast and smooth, on my n910f.
I echo @logosA's report.
While it does boot, and its the first version to ever boot on the 910G
After a few reboots it gets stuck in booting into download mode only
Reflashed all and testing further
clod22 said:
I just flashed, all are running smooth, Thank for your hard work.
Click to expand...
Click to collapse
Thanks, the others were uploaded a few hours after.
Thanks a lot for this. I want to ask if I need to update to the latest TWRP before flashing this rom?
Sent from my SM-A505G using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you 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 me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.LineageOS is based on the Android Open Source Project, with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.All the source code for LineageOS is available in the LineageOS GitHub organization.And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.You can also view the changelog for a full list of changes & features.Official LineageOS website : http://lineageos.orgAbout LineageOS Legal : http://lineageos.org/legal
Important Information
1. This ROM operates without ODM images, just follow the installation instructions.2. This ROM does not intended to support Google Camera, but you can try to play with some mods.
About FDE and FBEFull-disk encryption (FDE) has been completely deprecated since Android 13, and now we use software implementation of File-based encryption (FBE).FDE and FBE methods are incompatible with each other. FBE cannot decrypt data encrypted with FDE and cannot encrypt existing files. That's why you need to perform factory reset/format data (not just "wipe data") before switching between ROM's with different encryption methods.To make it a bit clear:- FDE (e.g. stock, LineageOS-16/19) -> FBE (LineageOS-20) -> NOT POSSIBLE! Format data is required.- FBE -> FBE -> POSSIBLE! You can update/upgrade using "dirty" installation as before, in case if encryption methods are the sameMoreover, to work with new encryption you need a recovery with appropriate support.Downloads Links
LineageOS 20:Unofficial: https://sourceforge.net/projects/loire-development/files/lineageos-20/suzuGoogle Applications (optional):MindTheGapps: https://androidfilehost.com/?w=files&flid=322935 (Android 13.0 -> arm64)XDA post about GApps: https://xda-developers.com/download-google-apps-gappsRecommended Recovery (optional):TWRP 3.x: https://forum.xda-developers.com/-/-t3786431
Flashing and updating
Before installation, please make sure you have read and understood everything correctly about FDE and FBE encryption methods.LineageOS clean install:
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)
About the builds:
Kernel sources: https://github.com/Chippa-a/android_kernel_sony_msm8956
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Grab a logcat right after the problem has occurred
(Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0
(Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Also thanks to:
The LineageOS Team
The SODP Team
Everyone involved in working and testing
Contributors
Chippa_a
ROM OS Version: 13.x
ROM Kernel: Linux 4.9.x
Version Information
Status: Beta
FEATURES AND ISSUES
Boot: Ok
Bluetooth: Ok
WiFi: Ok
WiFi Hotspot: Unknown
RIL - Phone - Data: Ok
GPS: Ok
Camera: Ok
Camcorder: Unknown
Lights: Ok
MicroSD: Ok
Accelerometer: Ok
Compass: Ok
Gyroscope: Ok
QTI sensors: Ok
Touchscreen: Ok
FM Radio: N/A
Fingerprint: Ok
Vibrator: Ok
Microphone: Ok
Audio & music: Ok
Bluetooth audio: Ok
NFC: Unknown (HCE: Unknown)
Kernel: Ok (WIP)
Graphics: Ok
3D Rendering: Ok
Clock: Ok
DRM: Unknown
Offline Charging: Ok
USB: Ok
USB Tethering: Unknown
USB OTG: Ok
Encryption: Ok
SEPolicies: Enforcing
You are an amazing person..
- There was a problem
Random Reboot in previous versions
- In addition to the problem of phone data not working, knowing that my network is
Orange Jordan
After months, the reason appeared to be an error in the DNS of the device. I do not know whether the problem was resolved or not.
I will try the version today and give you the result.
Thank you again
I didn't expect to have a13 on my phone! Thank you for your works. Will try this now.
amazing, thank you very much.
already flashed on my suzu, works really fine
Hi Chippa_a, Thanks for a great ROM and supposting our old device.
Chippa_a said:
2. This ROM does not intended to support Google Camera, but you can try to play with some mods.
Click to expand...
Click to collapse
This version of Google Cam work great with this ROM and if you don't use Gapps, you can install Google Cam Services and use it without Gapps.
Chippa_a said:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you 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 me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.LineageOS is based on the Android Open Source Project, with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.All the source code for LineageOS is available in the LineageOS GitHub organization.And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.You can also view the changelog for a full list of changes & features.Official LineageOS website : http://lineageos.orgAbout LineageOS Legal : http://lineageos.org/legal
Important Information
1. This ROM operates without ODM images, just follow the installation instructions.2. This ROM does not intended to support Google Camera, but you can try to play with some mods.
About FDE and FBEFull-disk encryption (FDE) has been completely deprecated since Android 13, and now we use software implementation of File-based encryption (FBE).FDE and FBE methods are incompatible with each other. FBE cannot decrypt data encrypted with FDE and cannot encrypt existing files. That's why you need to perform factory reset/format data (not just "wipe data") before switching between ROM's with different encryption methods.To make it a bit clear:- FDE (e.g. stock, LineageOS-16/19) -> FBE (LineageOS-20) -> NOT POSSIBLE! Format data is required.- FBE -> FBE -> POSSIBLE! You can update/upgrade using "dirty" installation as before, in case if encryption methods are the sameMoreover, to work with new encryption you need a recovery with appropriate support.Downloads Links
LineageOS 20:Unofficial: https://sourceforge.net/projects/loire-development/files/lineageos-20/suzuGoogle Applications (optional):MindTheGapps: https://androidfilehost.com/?w=files&flid=322935 (Android 13.0 -> arm64)XDA post about GApps: https://xda-developers.com/download-google-apps-gappsRecommended Recovery (optional):TWRP 3.x: https://forum.xda-developers.com/-/-t3786431
Flashing and updating
Before installation, please make sure you have read and understood everything correctly about FDE and FBE encryption methods.LineageOS clean install:
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)
About the builds:
Kernel sources: https://github.com/Chippa-a/android_kernel_sony_msm8956
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Grab a logcat right after the problem has occurred
(Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0
(Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Also thanks to:
The LineageOS Team
The SODP Team
Everyone involved in working and testing
Contributors
Chippa_a
ROM OS Version: 13.x
ROM Kernel: Linux 4.9.x
Version Information
Status: Beta
Click to expand...
Click to collapse
Good evening.
After a few days of use.
There are some points of the system:
- No light when charging
- There is a repetition of the process of unlocking the phone, "that is, after entering the password, the phone will be locked again, and you will enter the password again."
- The problem of phone data does not work, and this problem is from version 16 until now, without a solution.
Battery consumption is higher than the previous version
- There is a problem with the sound, "it suddenly disappears" and the sound cannot be returned until after restarting the phone.!
...
These are the most important points.
tareqabamawi said:
Good evening.
After a few days of use.
There are some points of the system:
- No light when charging
- There is a repetition of the process of unlocking the phone, "that is, after entering the password, the phone will be locked again, and you will enter the password again."
- The problem of phone data does not work, and this problem is from version 16 until now, without a solution.
Battery consumption is higher than the previous version
- There is a problem with the sound, "it suddenly disappears" and the sound cannot be returned until after restarting the phone.!
...
These are the most important points.
Click to expand...
Click to collapse
Been testing this for few days now. (With Gapps)
- I have no problem with light when charging.
- I can confirm there's a repetition when unlocking, but this only happen to me once.
- mobile data works for me.
- I can confirm sound suddenly disappear and restart fix it, this happened just once.
I also wanted to add.
- GPS works.
- USB OTG works.
So far I'm very satisfied with this. Feels smoother than a12 , also camera quality seems improved. Thank you for bringing this great works.
I had a problem with this rom
the phone does not charge , it makes the charging light turn on and the charging icon for 2 seconds then the light flashes once then it wont charge anymore
i install the rom without twrp, i used lineage 20 recovery
Nice Rom for the Sony X so far.
The recorded Voice in Whatsapp is to low/quiet.
In Ventor/ect is the mixer_paths_tasha.xml
Which parameter do you have to change for a louder recording?
Thank you in advance for the help.
After 7 days as a daily companion, here is a summary of this ROM (lineage-20.0-20230308-UNOFFICIAL-suzu)
(Clean Install with TWRP 3.7.0_12-0-20230309-suzu and MindTheGapps-13.0.0-arm64-20221025_100653)
Pro:
-Google Cam (DMGC_7.3.020_ver.4.5) works perfect with HDR
-ROM runs smooth without lags or random reboots
-Better overview thanks to the higher resolution on the Display (everything is a little smaller as Android 11)
-WiFi stability (WPA2 5ghz) is better than Android 11 (last Official Build)
-GPS, Bluetooth, Simcard recognition/Phone Data (O2 Germany 4G), OTG, Fingerprint, Audio Speaker, Lights....everything works perfectly
Cons:
-Microphone in Apps like Whatsapp or Recorder is much too quiet (unusable) but when making normal calls everything is ok
-Power consumption too high, cell phone gets very warm and charges longer
-Screen retention effect (Fake burn in from the last Screen)
I like this ROM and I hope that these few bugs can still be fixed.
That's how long I'll be back on Android 11 for now.
XxAttackerxX said:
After 7 days as a daily companion, here is a summary of this ROM (lineage-20.0-20230308-UNOFFICIAL-suzu)
(Clean Install with TWRP 3.7.0_12-0-20230309-suzu and MindTheGapps-13.0.0-arm64-20221025_100653)
Pro:
-Google Cam (DMGC_7.3.020_ver.4.5) works perfect with HDR
-ROM runs smooth without lags or random reboots
-Better overview thanks to the higher resolution on the Display (everything is a little smaller as Android 11)
-WiFi stability (WPA2 5ghz) is better than Android 11 (last Official Build)
-GPS, Bluetooth, Simcard recognition/Phone Data (O2 Germany 4G), OTG, Fingerprint, Audio Speaker, Lights....everything works perfectly
Cons:
-Microphone in Apps like Whatsapp or Recorder is much too quiet (unusable) but when making normal calls everything is ok
-Power consumption too high, cell phone gets very warm and charges longer
-Screen retention effect (Fake burn in from the last Screen)
I like this ROM and I hope that these few bugs can still be fixed.
That's how long I'll be back on Android 11 for now.
Click to expand...
Click to collapse
How many time can phone in idle ?
FYA_EXel said:
How many time can phone in idle ?
Click to expand...
Click to collapse
Over Night with Android 11 you have 4-5 Percent and with Android 13 from here you have 8-10 Percent Drop in Standby. (Wlan, Bluethooth, GPS is deactivated)
Is kernel 4.9 more stable than 4.14? Which is the latest I see on sony sw binaries https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
What is fixed or new in Version lineage-20.0-20230416-UNOFFICIAL-suzu ?
Changelog please. Thanks
Hi ! Thanks for this work.
I wonder if Lineage Os 20 ( Android 13 ) will run well on a 3GB RAM device.
It's actually my wifi device only for banking ap. On Lineage Os 18 and Gapps.
( I've seen a difference between android 11 nd 12 on my XA2 with iOdé Os - and also 3GB of RAM only )
Best regards.
@Chippa_a changelog for latest build please...
Thanks a lot for this ROM and the latest Update (22nd of May)!
I didn´t managed to install the ROM on my single-sim suzu using TWRP (tried 3.7.0._9-0 and _12-1). With LOS 18 recovery I succeded in the first try. Didn´t understood by now what is the problem.
Didnt found a bug in 3 days of use without Gapps. Fingerprint-sensor is working better than ever. Accu-drain is less than with LOS 18. LOS-Stock camera is fully sufficient for my needs.
Best regars.
Does the built-in updater (Settings -> System -> etc) list also the installed version offering to reinstall it?
alfacrux said:
Does the built-in updater (Settings -> System -> etc) list also the installed version offering to reinstall it?
Click to expand...
Click to collapse
yes