***BETA***[ROM][AOKP 8.1/Oreo][HLTE] AOKP Oreo for Galaxy Note 3 (Unified)***BETA***

[shane87]

These are beta builds!!! Stuff may be broken/missing/jank!!! You have been warned.

[ROM][AOKP 8.1/OREO][HLTE] AOKP Oreo for Galaxy Note 3 (Unified) Beta Builds

These are beta builds!!! Stuff may be broken/missing/jank!!! You have been warned. Again.

*** Disclaimer***
Your warranty is now void!
I am not responsible for damages caused by this ROM
YOU are choosing to install it!
If you have any concerns about potential issues or features with this ROM, do your research!
If you accuse me of causing problems with your device, you WILL be ridiculed!

Read the above warnings again! These are BETA builds!
They are [B]NOT[/B] feature-complete, nor are they guaranteed to run!
By installing them, [B]YOU[/B] are assuming the risk of any potential problems!

Introduction
AOKP is a ROM developed by TeamKang, based on AOSP with magical unicorn bytes (awesome features) baked right in!
These builds have been tested on SM-N9005/SM-N900P

Features

• Android 8.1 Oreo
• OMS/Substratum Support - Theming baked right in
• SU baked in - No need for SuperSU/Magisk (Unless you want them!)
• ROMControl App - A centralized place to manage all almost all the cool features Magical unicorn Bytes!!
• More features coming soon! (P.S. Asking for ETA's is bad, unless you like NOT getting new features! )

Known Issues

• Bluetooth does not work with some devices - This is a known issue that also affects LineageOS-15.1Fixed?
• You tell me! I have limited testing time, so the more reports I get the better. Please see below for proper issue reporting!

Proper Issue Reporting

• Make sure you are seeing the issue on a CLEAN install! If the problem pops up after a dirty flash, wipe data/factory reset and see if it still happens before reporting it
• Make sure you have not flashed anything extra, such as 3rd party kernels, SuperSU, Magisk, Xposed, etc. These extra packages can cause their own issues. As above, try a full wipe and then only flash the ROM package and Gapps package, and see if the issue persists before reporting
• In your report please include the following:
  • Issue you are seeing, and how to recreate it
  • Logcat/kmesg from right after the issue if possible
  • Build date of ROM you are running
  • Gapps package you have installed

Installation instructions

• Backup your data! (nandroid, TiBu, etc.)
• Wipe Data/Factory Reset (You did backup, right?)
• Flash ROM
• Flash GAPPS
• Wipe Cache/Dalvik Cache
• Reboot

Download

shane87 AndroidFileHost page:
shane87's AFH page for AOKP Oreo Builds (BETA)

Source:
AOKP Source

Changelog

[B][U]Detailed changelogs between each version can be found at download link[/U][/B]

[B][U]Current changelog: 07/21/2019[/U][/B]
*[fix]BT bug fixed......again......maybe? lol
*[update]Latest AOSP/LOS upstream changes (No AOKP changes since last build - We are all focused on Pie, when we have time!)

[B][U]Changelog: 07/06/2019[/U][/B]
*[fix]BT bug finally squashed! - I hope anyway, let me know guys!
*[update]Latest AOSP/AOKP/LOS upstream changes

[B][U]Changelog: 12/09/2018[/U][/B]
*[fix?]Changes in hardware/samsung (6 commits) - MAY fix BT issues!
*[update]Latest AOSP/AOKP/LOS upstream changes

[B][U]Changelog: 11/18/2018[/U][/B]
*[fix?]Set proper WBS sample rate - MAY fix BT issues!
*[update]Update to Android 8.1_r50 base
*[update]All upstream changes since 09/16

[B][U]Changelog: 09/16/2018[/U][/B]
*[update]Update to Android 8.1_r46 base
*[new/update]Add SystemProfiles QS Tiles
*[fix]Fix some QS tiles, remove some deprecated QS Tile code
*[fix?]Fix spacing in bluetooth_vnd.txt, [i]possible[/i] BT issue fix?
*Full changelog available at download link

[B][U]Changelog: 08/19/2018[/U][/B]
*[fix]Remove reference to mIsTap and Handler in absListViewWidgets.java (frameworks/base) - Fixes ListView mod widget issue
*[fix]Camera regression from 08/12 build fixed - No clue what happened, but everything is working again.
*[update]Add QS animation options to ROM Control
*[update]Add QS title hide option to ROM Control
*[update]Add AOKP logo on status bar option to ROM Control
*Full changelog available at download link

[B][U]Changelog: 08/12/2018[/U][/B]
*[fix]su issues from previous build fixed
*[update]Revert soundboost to stop speaker distortion [update]SoundBoost mods available at dl links!
*Full changelog available at download link

[B][U]Changelog: 07/31/2018[/U][/B]
*[update/fix?]Remove CarrierConfigs from hlte/hltetmo device trees; CarrierConfigs was duplicated in msm8974-common
*[update/fix]Remove vendor security patch level from device trees, move to common tree
*Full changelog available at download link

[B][U]Changelog: 06/24/2018[/U][/B]
*[update]Use mpdecision from G900FXXU1CRA2_G900FOXA1CRA2_BTU
*[update]Drop lib_cutils_atomic shim (was only needed for old mpdecision)
*[fix?]Changing mpdecision and dropping the shim [B][U]SEEMS[/U][/B] to have fixed rotation on LOS, hopefully fixed for us
*Full changelog available at download link

[B][U]Changelog: 06/03/2018[/U][/B]
*[fix]Boost sound levels across all devices
*Full changelog available at download link

[B][U]Changelog: 05/14/2018[/U][/B]
*[fix?]Commit pulled in from AOKP source to fix camera recording issues.
*[update]Latest changes from AOKP source
*Full changelog available at download link

[B][U]Changelog: 05/06/2018[/U][/B]
*[update]Minor changes to QS header images support
*[new]Scrollable QS tiles
*[new]Add builds for hltechn/hltekor/hltetmo
*Full changelog  available at download link

[B][U]Changelog: 4/30/18[/U][/B]
*[fix?]Changes to phone call audio routing, may help BT phone audio issues
*[fix?]New overlay that may help with auto-rotation bug
*[new]Customizable header images
*Full changelog available at download link

[B][U]Changelog: 4/23/2018[/U][/B]
*[new]Initial AOKP Oreo Beta release for hlte

Thanks To/Credits

• TeamKang
• tdm
• LineageOS
• @stonedead - for finding sensor batching overlay; a potential rotation bug fix!
  
  PayPal Donations and thanks are always appreciated!

XDA:DevDB Information
Oreo Android Open Kang Project for Samsung Galaxy Note 3 (HLTE), ROM for the Sprint Samsung Galaxy Note 3

Contributors
shane87
Source Code: http://aokp.co/source/

ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP 3.2.1-1
Based On: AOKP

Version Information
Status: Beta
Current Beta Version: 2019-07-21
Beta Release Date: 2019-07-21

Created 2018-04-24
Last Updated 2019-07-21

 

[shane87]

Reserved

 

[shane87]

As far as an update schedule goes, I will TRY to do weekly builds with the latest commits. I will also TRY to pull in pending commits when possible, assuming I can get them to build.

 

[MuDDuQ]

this is pretty good news I will try to get this installed this weekend thanks for keeping this phone alive

 

[len207]

I also installed this ROM and will do some testing. So far what I have tried, voice, data, GPS have worked as expected. It also connects with my Asus smart watch. I will continue to test things out and provide feedback as appropriate. BTW BT phone audio is not working as noted on OP. If that is corrected this would be my daily driver. Thanks to the dev for the work on this Note 3 ROM!

 

[shane87]

I also installed this ROM and will do some testing. So far what I have tried, voice, data, GPS have worked as expected. It also connects with my Asus smart watch. I will continue to test things out and provide feedback as appropriate. BTW BT phone audio is not working as noted on OP. If that is corrected this would be my daily driver. Thanks to the dev for the work on this Note 3 ROM!

What bt device did you try phone audio on?

 

[len207]

What bt device did you try phone audio on?

I've tried two BT headsets the 6xxPlantronics and Motorola H19txt. They both work fine on Nougat ROM including AOKP and they also work with LineageOS 15.1 on the Note 4. I have also paired it with my car's BT Hands Free system with the same results. In all cases BT is seen and used for phone audio however, there is initially some white noise followed (after about 5 seconds) with silence.

 

[shane87]

I've tried two BT headsets the 6xxPlantronics and Motorola H19txt. They both work fine on Nougat ROM including AOKP and they also work with LineageOS 15.1 on the Note 4. I have also paired it with my car's BT Hands Free system with the same results. In all cases BT is seen and used for phone audio however, there is initially some white noise followed (after about 5 seconds) with silence.

Alright,I'll do some testing this weekend. I have a Plantronics Legend headset. It works perfect with AOKP Oreo on my LG g3. I'll test on my wife's Note 3 this weekend and see what I get.

 

[Unidave199]

Decided to make the jump!

Hooray for O.R.E.O.!

I was able to do an easy upgrade and so far its running along but had a few observations...

1. Do we not have to "allow instillation from unknown sources" under 'security' anymore?

2. GPS, DATA, CELL all working well. Will test bluetooth with my fitbit and speakers later today.

3. I am using Nova Launcher. I would like to put in a calendar widget, but it says "problems loading widget" no matter what widget I use. Google Calendar, Calendar Widget, and Chronos all not working. Chronos says it does not have OREO support anymore. Can anyone recommend a nice transparent calendar widget?

4. Hotspot Works... YAY!!

5. When trying to select my quick setting tiles, I can of course edit what I want to have appear. However, when I select to edit additional choices, the additional options are white on a white background so kinda hard to see.


I will be happy to provide logcats anyone is interested. But be advised. I am still unable to update my baseband from NC5 to PL1. But I dont think that has anything to do with the minor errors I am getting.

My thanks to all! And I will be happy to help further test this ROM if there is anything I can do, just ask!

 

[shane87]

Hooray for O.R.E.O.!

I was able to do an easy upgrade and so far its running along but had a few observations...

1. Do we not have to "allow instillation from unknown sources" under 'security' anymore?

2. GPS, DATA, CELL all working well. Will test bluetooth with my fitbit and speakers later today.

3. I am using Nova Launcher. I would like to put in a calendar widget, but it says "problems loading widget" no matter what widget I use. Google Calendar, Calendar Widget, and Chronos all not working. Chronos says it does not have OREO support anymore. Can anyone recommend a nice transparent calendar widget?
4. Hotspot Works... YAY!!

5. When trying to select my quick setting tiles, I can of course edit what I want to have appear. However, when I select to edit additional choices, the additional options are white on a white background so kinda hard to see.


I will be happy to provide logcats anyone is interested. Bt be advised. I am still unable to update my baseband from NC5 to PL1. But I dont think that has anything to do with the minor errors I am getting.

My thanks to all! And I will be happy to help further test this ROM if there is anything I can do, just ask!

1. Installation from unknown sources is now handled like Nougat/Oreo permissions: on an app-by-app basis as each app tries to install an app from unknown sources. You will be prompted to give permission for it. For example, my Amazon app had an update yesterday, and when I hit install it prompted me to give Amazon permission to install from unknown sources.

2. Awesome to hear. Let me know how bt goes.

3. That must be a Nova issue. I run Apex, and I was able to add a calendar widget (from Google Calendar), with no issue. To be fair, I am also using an LG G3 right now, though I can't imagine that would make a difference, since I built the hlte and d855 builds back to back.

4. Good to hear. I haven't tested hotspot.

5. We are still ironing out some issues!

 

[Unidave199]

2. Awesome to hear. Let me know how bt goes.

So... more good news! Paired with my Fitbit just fine, also paired with my stereo and speaker

3. That must be a Nova issue. I run Apex, and I was able to add a calendar widget (from Google Calendar), with no issue. To be fair, I am also using an LG G3 right now, though I can't imagine that would make a difference, since I built the hlte and d855 builds back to back.

I also tried the Trebouchet launcher that came with the ROM and it was acting weird too. Seems to be that the Analogue clock will post but not the digital one. Also size changes seem to prevent the digital clock from working

The voice input doesn't seem to be working as part of the keyboard. It does work for Google Assistant though...

Thank you again! I hope this is not nit picking.

Dave

 

[shane87]

Thank you again! I hope this is not nit picking.

Dave

Not at all. I need someone to find all these little bugs, lol. I haven't tried voice input, I don't have much use for it, tbh. I'll do some digging this weekend, and see what I find in testing.

 

[Unidave199]

Thank you again! I hope this is not nit picking.

Dave

Dig away! So I decided to load the Nugat ROM on my phone and I see that the Clock/Calendar applications work fine with Nova Launcher. As to the voice issue I think it is my fault. I need to "enable voice typing" on the system. I did so with Nougat and it works just fine.

I would love to play a deeper role with compiling and code writing but I am still way too much of a noob but happy to do my part. I am a fairly heavy "power user" of almost all the systems so I give this GREAT phone a good workout.

I even use the infra red. Peel remote seems to be working......

Dave

 

[shane87]

Alright guys, I have been doing some digging into @trader418 and I can't find anything in particular that helps the rotation bug. In his unofficial Lineage 14 thread, he mentions some cm/los updates that fixed the rotation issues, but doesn't mention the exact commit. Also, it sounds like those changes should already be in these builds, since AOKP's hlte device trees, and kernel source, are forked from LineageOS trees. And I do make sure to pull in the latest LOS changes. So I am still stumped on the rotation bug. On to better news. I have just finished a new build, with the latest AOKP changes synced in. I also pulled in some open commits that add customizable header image support. Along with a few open commits from LOS, mostly to do with phone call audio, so hopefully that may help with BT issues. I am going to do some personal testing before I upload, so be patient, new goodies are on their way!

 

[shane87]

New Release!

Alright guys, I have a new build up at the download link in the OP. For this build, I pulled in some LOS changes that deal with phone call audio routing, which could help with bt phone audio issues, and I also enabled an overlay that may help with the rotation bug. The overlay was discovered by @stonedead so a HUGE thanks to him! I may have never discovered the overlay on my own. I also have included pending AOKP commits to add customizable header images. This build also includes all of the latest AOKP commits that have been merged, including fixes and some tweaked features. As always, I upload a changelog with all of the commits pulled in since the last build, so detailed information on the changes between the 4/23 build and todays build can be found there.

I HAVE NOT had a chance to personally test this build! As I have mentioned before, my only test phone is my wife's daily driver, and if she is busy using it, not much of a chance for me to test lol. With that being said, there shouldn't be any major bugs introduced in this build.

Changelog:

• Changes to phone call audio routing, may help BT phone audio issues
• New overlay that may help with auto-rotation bug
• Customizable header images
• Full changelog available at download link

 

[len207]

Thank you for your ongoing efforts but unfortunately the BT phone audio on my n900p has not changed. The BT headphone is seen by the system and pairs just fine. In phone app the BT headphone is also seen. However, when making a call the earpiece only produces white noise slowly decreasing in volume to silence. The person on the other end of the connection hears nothing...

 

[Unidave199]

[SOLVED] Control Backlighting.

I seem to recall someone having problems with their backlights on the menu and 'back' button. I had it too until i went to SETTINGS> BUTTONS>HARDWARE KEYS...

Just toggle them off and back on then the buttons should respond to your desired preference...

As a side note... I wrote earler about using Clock and Calendar displays in NOVA launcher and they just don't seem to work... but they work fine in Apex Launcher which is free and very similar to NOVA..

Keep up the GREAT ROM! Thank you for the snack jump from KitKat to Oreo!

D-

 

[shane87]

New Release!

Hey guys, new builds are up. Nothing major with these builds, some minor changes to QS Header image support, and scrollable QS Tiles. The big news with this release is

Wait for it...

Wait some more...

Builds for hltechn/hltekor/hltetmo!!!
I have NOT tested these builds! I don't have access to anything other than hlte, so PLEASE test these builds if you have the device! And let me know what you find!

The info and download links for the new builds can be found on my main thread

 

[Unidave199]

I will give the new build a try tonight!

Unfortunately I had the hotspot function working, and then it stopped. I will get the nerve to Odin the PL1 update and then see if that fixes the problem...

Can we just dirty flash the new builds? Do we need to re flash GAPPS as well? I tired doing that and it would crash out so I had just dirty flashed the new build without GAPPS and without wipe of cache which seems to work better for me..

Thank you for keeping this build alive!!

D-

 

[shane87]

I will give the new build a try tonight!

Unfortunately I had the hotspot function working, and then it stopped. I will get the nerve to Odin the PL1 update and then see if that fixes the problem...

Can we just dirty flash the new builds? Do we need to re flash GAPPS as well? I tired doing that and it would crash out so I had just dirty flashed the new build without GAPPS and without wipe of cache which seems to work better for me..

Thank you for keeping this build alive!!

D-

Dirty flashing is ok. The only caveat with dirty flashing is, if you run into issues, wipe and clean flash to see if that fixes the issue BEFORE reporting the problem.

As far as GApps, you don't need to reflash GApps on a dirty flash. In theory, reflashing GApps shouldn't hurt, since it should remove existing GApps before installing. However, if you have updated any of the GApps through the playstore, and you flash and older GApps build, you will downgrade the app in question, which may cause issues.

I hope that makes things clear as mud!

TL;DR:
Dirty flashing is ok, as long as you clean flash BEFORE reporting issues.
On a dirty flash, no need to flash GApps again.