[ROM][UNOFFICIAL][9] LineageOS 16.0 [tblte][trlte][trlteduos]

Search This thread

Scolaro

Senior Member
May 8, 2011
111
29
Maybe this is due to my sd card or a simple user mistake, but I have the following problem since switching to this ROM:
First time installing the ROM from scratch I didn't format the sd card and whenever I restarted the phone (e. g. to update the ROM) and tried to use the playlists I got an error saying "this file type cannot be played". Playing the same music piece directly from the folder worked.
Sometimes it helped to copy over the playlist files again, other times it didn't.

In the end I called myself an idiot for trying to save a few minutes during the first setup, wiped phone AND sd card, and installed ROM/Gapps/Magisk once more. Then I copied the music over to the sd card, chose to use it as regular storage and tried the playlists which were working fine. After the next restart, however, they were again not playing the music anymore, so it doesn't seem to have anything to do with my not formatting the sd card in the first place.

A similar thing, connected to that, I believe, is my alarm clock that's set to playing a specific melody. The same happens here: I set it up, it works fine, I restart the phone, the app has switched back to the default melody.

Does anyone experienced something like this or has an idea where this issue may come from?
 

sebas4200

Member
Jan 23, 2019
29
4
Pixel launcher is very buggy, especially if you installed from opengapps full.

Sorry About That Thought Pixel Launcher Was A Stock launcher , mostly Everything "I want" is working almost perfect , It's A Damn Great Start ,

Thanks Again For Taking The Time , Hope we Get Those Linage Settings Soon
 

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,410
6,405
tiny.cc
Sorry About That Thought Pixel Launcher Was A Stock launcher , mostly Everything "I want" is working almost perfect , It's A Damn Great Start ,

Thanks Again For Taking The Time , Hope we Get Those Linage Settings Soon

The Pixel Launcher is fine if you install it as a user app. Through trial and error, I found that P-4623511 works best.
 
  • Like
Reactions: tripLr

ninja_unmatched

Senior Member
Dec 21, 2007
891
355
ninjatechc.com
Hi. spendcommand can not be installed, do you know any way to solve this problem and be able to install spendcommand?

Enviado desde mi SM-G950F mediante Tapatalk
Not sure why you can't install spencommand... Which version? I do know you have to install the latest beta or newer if he has one. (Ver. 1.2.38)

Sent from my SM-N910P using Tapatalk
 

73sydney

Senior Member
Jul 21, 2018
1,543
1,252
Sydney
Google Pixel 2 XL
Not sure why you can't install spencommand... Which version? I do know you have to install the latest beta or newer if he has one. (Ver. 1.2.38)

Sent from my SM-N910P using Tapatalk

Genuine released and bought spencommand installs fine - at least two of us have confirmed this, so thats the subject closed

warezed and or previous versions will likely not....dont ask for help with those...this is what i suspect he is trying
 

ninja_unmatched

Senior Member
Dec 21, 2007
891
355
ninjatechc.com
I'm a very newbie to all this world. But I just would like to THANK @ripee, @_mone , and @mobspyguy , and every member and contributor who worked on this ROM. Its fast and awesome. I appreciate it!

I was able to figure out how to install it on my n910v. I'm still trying to get used to it and figure my way around pie coming from 6.0.1 LOL. A lot of things don't make sense to me but I'm learning. hhhhh



-I want to report that the finger print scanner intermittently stops working when I try to unlocks my phone. So I have to use the PIN to unlock.

-is there a way to do face-unlock? (edit: sorry , i figured this out and it's working! :) )

-is there a way to install the old stock Samsung keyboard?

-the camera also intermittently not start. I have to close the app and try again. No big deal. Just FYI.


Thank you
I think you could try but remember this is now pie. You have to find a version of the apk for pie. Which Samsung phone has pie? Oreo may work also. Then there are it's dependencies. There is another folder of files it will need. On any custom ROM it is usually in the same folder. SamsungIME

I am curious so I may try this out when I have time.

Sent from my SM-N910P using Tapatalk

---------- Post added at 06:12 AM ---------- Previous post was at 06:05 AM ----------

Genuine released and bought spencommand installs fine - at least two of us have confirmed this, so thats the subject closed



warezed and or previous versions will likely not....dont ask for help with those...this is what i suspect he is trying
The one right be this one.. listed stable does not work... But yeah the one I listed installs fine...

Sent from my SM-N910P using Tapatalk
 

Ahrius

New member
Mar 2, 2019
2
2
910F

I want to thank you for your great work! Now i have to use my Note 4 for another 2-3 years :good:
(made a clean install and it worked well)

Its really awesome work and its going to be my daily driver.
But yeah there are some bugs like the scrolling glitch. The scrolling glitch happens in contacts, whatsapp and also in apps like Swiftkey on the top options side scroller.

I think the biggest problem is that many apps from the play store can not be installed. "Not supported device"

I guess the battery drain is also higher than the "normal" touchwizz 6.0 :confused:

The fingerprint scanner arent able to unlock the phone but i dont care, because i dont really like the slow note 4 fingerprint scanner...

Keep it up!

Another short newbie question: If there are new versions of this ROM, do i have to manually download the files and install it or will there be the "normal" update mechanism with no lost data?
 
Last edited:

Shizzle2889

Senior Member
Apr 17, 2015
121
126
Chicago
Samsung Galaxy A71 5G
So i am running 0221 currently. Clean install, with cleaning the sd from a windows pc, rather than twrp. I started off and the fingerprint scanner seems to be acting like it did early on for 15.1, scan your finger as fast as possible to register and then it is hit or miss on unlock, but most 3rd party apps that use fingerprint authentication always work. I had gotten the lower screen glitch commonly, but after a few days the issue went away. The only issue i have now is the commonplace lag where the app stops responding for a few minutes and the consistent anr messages.

In addition, I miss having the aicp extras from the time i spent on aicp 13.1. Regardless, los 16 seems to working fantastic for this early on into the note4 pie life. Thank you @rippee and @_mone
 
  • Like
Reactions: 73sydney and tripLr

ninja_unmatched

Senior Member
Dec 21, 2007
891
355
ninjatechc.com
I want to thank you for your great work! Now i have to use my Note 4 for another 2-3 years :good:
(made a clean install and it worked well)

Its really awesome work and its going to be my daily driver.
But yeah there are some bugs like the scrolling glitch. The scrolling glitch happens in contacts, whatsapp and also in apps like Swiftkey on the top options side scroller.

I think the biggest problem is that many apps from the play store can not be installed. "Not supported device"

I guess the battery drain is also higher than the "normal" touchwizz 6.0 :confused:

The fingerprint scanner arent able to unlock the phone but i dont care, because i dont really like the slow note 4 fingerprint scanner...

Keep it up!

Another short newbie question: If there are new versions of this ROM, do i have to manually download the files and install it or will there be the "normal" update mechanism with no lost data?
He not supported message is more a version of phone thing. Magisk hide plus changing some config files can get around that.

Sent from my SM-N910P using Tapatalk
 
  • Like
Reactions: Ahrius

Myskiis2fast4u

Senior Member
Feb 1, 2017
64
15
Is anyone else encountering frequent resets? I havent put a use case scenario together but seems to be around the use of chrome. March 1 version of rom.... Just curious. I 3 been dirty updating maybe 2x's a week. Wondering if that has anytjing to do with it.? Thank u again for the dev work here. Thank u!!!
 
So i am running 0221 currently. Clean install, with cleaning the sd from a windows pc, rather than twrp. I started off and the fingerprint scanner seems to be acting like it did early on for 15.1, scan your finger as fast as possible to register and then it is hit or miss on unlock, but most 3rd party apps that use fingerprint authentication always work. I had gotten the lower screen glitch commonly, but after a few days the issue went away. The only issue i have now is the commonplace lag where the app stops responding for a few minutes and the consistent anr messages.

In addition, I miss having the aicp extras from the time i spent on aicp 13.1. Regardless, los 16 seems to working fantastic for this early on into the note4 pie life. Thank you @rippee and @_mone
Acip extras can be installed as an apk.
 
  • Like
Reactions: jufegoco

TitanFoxX

Member
Nov 1, 2012
31
4
I want to thank you for your great work! Now i have to use my Note 4 for another 2-3 years :good:
(made a clean install and it worked well)
Probably not. This year it will get mandatory for developers to provide both 32 and 64 bit versions of their apps. Next year - I believe around May - only 64 bits apps will be allowed at Google's Play Store, meaning that there will not be any updates for legacy apps.

The Snapdragon 805 in the international (EU = SM-910F) version is a 32-bit SoC, so it is likely that you'd have to upgrade to a phone with a 64 bit platform in about 15 months. Don't know about the Exynos versions of this phone, though.

That said, my Galaxy Note 4 had a good run for over 4 years. I will replace it with a Galaxy Note 10 later this year. Hopefully that phone will be just as enjoyable :)
 

Wetzel402

Senior Member
Jan 7, 2012
402
99
I have a few items to report....
1) This ROM is running well and I am happy with it coming from your previous Oreo ROM.
2) SELinux does not enforce
3) I can't seem to get 4G LTE (running on Verizon). I am getting 3G though.
4) My WiFi sometimes just gets stuck at obtaining IP address. I try toggling WiFi and rebooting. I'm not sure if it is the phone or my router.
5) The same screen glitches others are seeing.
 

Myskiis2fast4u

Senior Member
Feb 1, 2017
64
15
In case anyone else is reading line by line i just wanted to add that i made a post on top here (first on pg20) and i stated i was experiencing resets.... Long story short is previous to the resets i messed about with other batteries and somehow jammed up the battery calibration??? Even a FULL format....clear....wipe...and install two different backups saved prior to my my battery games and resets fixed it.... I then did another full wipe and dumped all of my saved backups and did a full fresh install and im up and running reset free..... I noticed my battery percentage was different EVERY time i did an install and was also different from what twrp said the battery was..... actually in 2 full formats and installs of images my battery percentage did not change (no charger connected either). Very odd. Im now at 34% and cant figure out for the life of me what was hung up in the system that caused the issue resetting. Anyhow im back up and runnning a clean install.
 

Shizzle2889

Senior Member
Apr 17, 2015
121
126
Chicago
Samsung Galaxy A71 5G
Ok, so haven't heard anything in regards to sim death here. Just got hit with one though. So ever since i rooted and custom rom m y phone, i cannot take a picture using flash using facebook messenger. If i do, it freezes in the middle. Figured i would give it a go with this rom. When my phone came back up, the mobile data quick tile says no sim. I have no mobile data on the status bar (icon missing). On the lock screen, it appears to be reading my sim though- at the top left where it normally has the roaming message or have also seen "123456", it reads verizon wireless, which i havent seen there since stock. Kind of funky mess lol.
 

73sydney

Senior Member
Jul 21, 2018
1,543
1,252
Sydney
Google Pixel 2 XL
Ok, so haven't heard anything in regards to sim death here. Just got hit with one though. So ever since i rooted and custom rom m y phone, i cannot take a picture using flash using facebook messenger. If i do, it freezes in the middle. Figured i would give it a go with this rom. When my phone came back up, the mobile data quick tile says no sim. I have no mobile data on the status bar (icon missing). On the lock screen, it appears to be reading my sim though- at the top left where it normally has the roaming message or have also seen "123456", it reads verizon wireless, which i havent seen there since stock. Kind of funky mess lol.

If you havent heard anything about sim death here, you havent used the search box......

You should try it sometime, its not broken

And i should know because i posted several posts about sim death, and include a fix (its also in my signature)

Search box...use it, it works...not there for decoration

---------- Post added at 05:01 AM ---------- Previous post was at 04:59 AM ----------

Is anyone else encountering frequent resets? I havent put a use case scenario together but seems to be around the use of chrome. March 1 version of rom.... Just curious. I 3 been dirty updating maybe 2x's a week. Wondering if that has anytjing to do with it.? Thank u again for the dev work here. Thank u!!!

Nope, no frequent resets, none at all in fact

If youve been dirty flashing and then something go hinky, logic should dictate the first thing you try is doing a full wipe and clean flash ......always backup your apps and/or data first
 

BeauSmith

Senior Member
May 11, 2012
113
7
Hey guys I'm dealing with my damn dialer going to black screen. I can't open the dialer back up. I read up on this, replaced with a patch dialer. Actually got xposed for Android 9, was able to disable my proximity sensor. still doing it. I've seen this problem before but Android 9 is likely different. Any help is appreciated.

-Beau
 

Top Liked Posts

  • There are no posts matching your filters.
  • 69
    android-p-logo.jpg


    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. :p


    [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 GApps
    FULL WIPE (with external microsd card)
    1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
    2. Download your LineageOS Rom and GApps Package,
    3. Move your LineageOS Rom and GApps Package to the external MicroSD storage,
    4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
    5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
    6. Swipe to Wipe at Bottom of Screen,
    7. Back to Main start screen,
    8. Wipe > Format Data,
    9. Type 'Yes' and press blue checkmark at the bottom-right corner,
    10. Go Back to Main Start Screen to Install Rom and GApps,
    11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
    12. Reboot System! Enjoy!


    FULL WIPE (without external microsd card with NO Home PC access)
    1. Move any files you want to keep to a safe folder - ! Or you will lose them !
    2. Download your LineageOS Rom and GApps Package,
    3. Move your LineageOS Rom and GApps Package to the internal storage,
    4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
    5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
    6. Swipe to Wipe at Bottom of Screen,
    7. Back to Main start screen,
    8. Wipe > Format Data,
    9. Type 'Yes' and press blue checkmark at the bottom-right corner
    10. Go Back to Main Start Screen to Install Rom and GApps,
    11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
    12. Reboot System! Enjoy!


    FULL WIPE (without external microsd card with Home PC access)
    1. Move any files you want to keep to your Home PC - ! Or you will lose them !
    2. Download your LineageOS Rom and GApps Package,
    3. Move your LineageOS Rom and GApps Package to the internal storage,
    4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibrate),
    5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
    6. Swipe to Wipe at Bottom of Screen,
    7. Back to Main start screen,
    8. Wipe > Format Data,
    9. Type 'Yes' and press blue checkmark at the bottom-right corner,
    10. Go Back to Main Start Screen to Install Rom and GApps,
    11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
    12. Reboot System! Enjoy!
    13. Once first boot is completed you can safely move your files back onto your Internal Storage.



    Important information about stock S Pen functionality!
    The apps, libraries, and drivers that allow for the advanced S Pen-based functions in stock TouchWiz and TouchWiz-based custom roms WILL NEVER BE INCLUDED IN ANY AOSP-BASED ROMS due to their proprietary nature. The scope of these functions goes beyond simple vendor blobs and enters the realm of 3rd party intellectual property licensed to Samsung. The S Pen does work in all AOSP-based custom roms, however it acts simply as an alternative input device. Various open source 3rd party apps are available that take advantage of the Note 4's stylus (see above), but their functionality is a fraction of that of stock TouchWiz.

    Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.


    Problems known to happen after a Dirty Installation
    1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.

    * Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.

    * Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.


    Bugs
    - 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
    - triplr-dev

    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
    18
    The lineage-17.1 thread is up!

    [ROM][UNOFFICIAL][10] LineageOS 17.1 [tblte][trlte][trlteduos]

    If you don't mind not having a working fingerprint sensor, or audio through the headphone jack, then Q is stable enough for daily use. As always when coming from an older rom version, it is highly recommended not to waste your time dirty flashing and just clean flash.

    Q is still a work in progress, so I will still be releasing Pie builds, though maybe not as often. As in years past, once the Q bugs have been fixed up to the current Pie level, I will post about when my last Pie build will be. I will upload it to the Downloads tab located at the top of each page of this thread, and link it in the OP.
    14
    Its embarassing how dev answers on trivial questions but on bootloops you get no answer

    Do you honestly believe that comments like this will inspire anyone with more experience than you to explore the bootloop issue on the Note Edge with any more urgency?

    That is not to say that this bootloop issue is not important, but if you wish to contribute constructively, please get a logcat and post it in this thread. If you do not know how to do so, please empower yourself in the spirit of self-education.
    14
    Congregations @ripee

    Q .. First Boot

    The lineage-17.1 build that is in my trlte folder does indeed boot, but most things are broken, and if you flash Magisk or gapps, it'll promptly reboot. There are many things missing and lots of changes still left to be made, but feel free to play with it. I'll keep it up until the time for the next build comes sometime tomorrow. Right now, the proper logs I got from the first successful boot will take time to go through and implement.

    There will be no Q thread until the rom is stable and most things work.
    13
    Starting from 0422, NO MORE LINEAGE SU ROOT INCLUDED IN MY BUILDS!

    I've given this some thought, and for the sake of minimizing problems with Magisk as well as being able to run apps that check for root, I've decided to take it out.

    Of course you will still be able to flash it with the official addon zip linked in the OP, as well as flash Magisk like you always could, but Magisk's ability to remove lineage su root automatically is not as reliable at this time than it used to be.

    Also, I cherry-picked a bunch of memory- and camera-related commits from khalvat, who is the official maintainer of Havoc-OS for trlte and trlteduos:

    android_device_samsung_apq8084-common
    android_device_samsung_trlte-common

    Regarding Havoc-OS for tblte, I will work with him to bring it to tblte as well.