[ROM] [OFFICIAL] [AOKP 9.0/Pie] [cheeseburger] AOKP Pie for OnePlus 5

[shane87]

[ROM][AOKP 9/PIE][cheeseburger] AOKP Pie for OnePlus 5

*** 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!

Introduction
WE ARE LIVE!!
AOKP is a ROM developed by TeamKang, based on AOSP/LineageOS with magical unicorn bytes (awesome features) baked right in!

Features

• Android 9 Pie
• OMS/Substratum Support - Theming baked right in
• SU baked in - No need for SuperSU/Magisk (Unless you want them!)
• Custom animations
• Customizable AOKP logo in status bar
• So many other features, explore and find them on your own!
• ROMControl App - A centralized place to manage all almost all the cool features Magical unicorn Bytes!!

Known Issues

• Pixel Launcher crashes constantly if you try to use it. This is an upstream issue, Lineage-16.0 has the same issue.
• 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

• Ensure you have the proper firmware installed (9.0.9)
• Backup your data! (nandroid, TiBu, etc.)
• Wipe Data/Factory Reset (You did backup, right?)
• Flash ROM
• Flash GAPPS
• Wipe Cache/Dalvik Cache
• Reboot

Download

Official AOKP download page:
AOKP cheeseburger files

Source:
AOKP Source
Kernel source

Changelog
Initial Official release.

Thanks To/Credits

• TeamKang
• tdm
• LineageOS

PayPal Donations and thanks are always appreciated!

XDA:DevDB Information
Pie Android Open Kang Project for OnePlus 5 [cheeseburger], ROM for the OnePlus 5

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

ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, TWRP 3.2.3 or later by codeworkx (Other TWRP versions not tested!!), Firmware package from OOS 9.0.9
Based On: LineageOS, CyanogenMod, OmniRom, AOSP

Version Information
Status: Nightly

Created 2020-01-20
Last Updated 2020-01-24

 

[shane87]

Reserved

 

[shane87]

Reserved

 

[shane87]

Builds are LIVE!!

Hey guys, AOKP Pie is OFFICIAL! Download links are in the OP, and I am including them below.

http://xfer.aokp.co/?developer=AOKP&folder=cheeseburger

 

[Pokemetti2]

This ROM doesn't officially support signature spoofing/microg?

 

[shane87]

This ROM doesn't officially support signature spoofing/microg?

No. AOKP has never officially supported signature spoofing/microg. We did discuss it in the past, but we decided not to, due to the security concerns of allowing signature spoofing.

 

[fosunite]

Does this rom has a working googlepay support?

I have been on stock oxygen OS roms for too long and i am thinking about a change.

EDIT: it is working. Had to make sure that safetynet is passed and using hidemagisk on google products

 

[d1n0x]

No. AOKP has never officially supported signature spoofing/microg. We did discuss it in the past, but we decided not to, due to the security concerns of allowing signature spoofing.

May I ask what kind of security concerns? AFAIK the signature spoofing permission needs to be explicitly granted on a per-app basis OR the spoofing app needs to be installed in /system.

For the first point, you would have to be a special kind of retard to just grant any app that permission.

And as for the second point, you would either have to have a ROM that already has a malicious app installed in /system in the first place, or you would have to explicitly install an app in /system through a flashable zip, TWRP file manager or Magisk. And for that you would have to have user interaction and know what you are doing.

So it basically all boils down to the user being the biggest security concern.

@Pokemetti2 you can try patching it either with NanoDroid patcher (if AOKP is deodexed, I don't know) or patch it manually using one of many methods such as haystack, tingle or others. Just look at the NanoDroid documentation.

 

[shane87]

May I ask what kind of security concerns? AFAIK the signature spoofing permission needs to be explicitly granted on a per-app basis OR the spoofing app needs to be installed in /system.

For the first point, you would have to be a special kind of retard to just grant any app that permission.

And as for the second point, you would either have to have a ROM that already has a malicious app installed in /system in the first place, or you would have to explicitly install an app in /system through a flashable zip, TWRP file manager or Magisk. And for that you would have to have user interaction and know what you are doing.

So it basically all boils down to the user being the biggest security concern.

@Pokemetti2 you can try patching it either with NanoDroid patcher (if AOKP is deodexed, I don't know) or patch it manually using one of many methods such as haystack, tingle or others. Just look at the NanoDroid documentation.

Yes, that is the case. However, with a rooted device, it would not be difficult for a malicious app to gain root access, then install itself into system, where it would then have access to the signature spoofing. Also, not everyone pays attention to the prompts that pop up on their phone, nor do they understand the ramifications of granting permissions, so it also wouldn't be difficult for a malicious app to gain permission for spoofing. Especially if the app has been granted permission to draw over other apps. It could actually hide the permission request under an innocuous sounding request.

;TLDR
Team Kang made the decision not to include signature spoofing/microg support. If you want to use NanoDroid patcher, or build your own unofficial AOKP with microg support, you are more than welcome to. But we will not be adding microg support officially.

 

[Pokemetti2]

Yes, that is the case. However, with a rooted device, it would not be difficult for a malicious app to gain root access, then install itself into system, where it would then have access to the signature spoofing. Also, not everyone pays attention to the prompts that pop up on their phone, nor do they understand the ramifications of granting permissions, so it also wouldn't be difficult for a malicious app to gain permission for spoofing. Especially if the app has been granted permission to draw over other apps. It could actually hide the permission request under an innocuous sounding request.

;TLDR
Team Kang made the decision not to include signature spoofing/microg support. If you want to use NanoDroid patcher, or build your own unofficial AOKP with microg support, you are more than welcome to. But we will not be adding microg support officially.

That's fine by me, just wanted to know whether I had to flash NanoDroid Patcher.

 

[shane87]

Update to OP

Hey guys, I just wanted to point out that I made a small update to the OP. I included a notice of the required firmware package from OOS that this ROM needs. Currently that is 9.0.9. We ran into an issue over on 5T, and it likely had to do with incorrect firmware on the phone. I forget that not everyone pours over gerrit as much as I do, so they don't see the required firmware commits.

I will update the OP, and post an announcement, any time that we update the firmware base required.

 

[fosunite]

I ve been on this rom for a couple of days and i have not experienced a crash so far.

Camera, gps, bluetooth and wifi are working. I can phone and everyone can hear me clearly.

I like the feature with the energy saving that you can use smart pixels to use less pixels on screen in order to increase the screen on time.

As for the sound effects, i had to disable the audioFX app to get Viper4Android working in order to get global sound effects.

What bothers me, is that once i have started up the phone, that it pops up a message that sim2 is not working and you get asked too early to switch to sim1. Perhaps if possible, adding a delay if 1minute has passed and that defined standard sim still has no reception, then ask for a simcard switch.

Also i wasnt able to find an option to turn off the alwaysOn display effect.


Above all else, great rom! Still using it as my daily driver.

 

[shane87]

I ve been on this rom for a couple of days and i have not experienced a crash so far.

Camera, gps, bluetooth and wifi are working. I can phone and everyone can hear me clearly.

I like the feature with the energy saving that you can use smart pixels to use less pixels on screen in order to increase the screen on time.

As for the sound effects, i had to disable the audioFX app to get Viper4Android working in order to get global sound effects.

What bothers me, is that once i have started up the phone, that it pops up a message that sim2 is not working and you get asked too early to switch to sim1. Perhaps if possible, adding a delay if 1minute has passed and that defined standard sim still has no reception, then ask for a simcard switch.

Also i wasnt able to find an option to turn off the alwaysOn display effect.


Above all else, great rom! Still using it as my daily driver.

I am pleased to hear everything is working well for you.

As far as sim1/sim2 goes, I only have a single sim card in my OP5, so I have not seen anything with it saying sim2 is not working. It automatically disables sim2 on boot. I will take a look this weekend, and bring it up to the team, see if there is anything we have changed that would affect sim1/sim2.

To the best of my knowledge, we have no feature to disable always on display. There are options to disable the Ambient Display, but that only affects whether the display pulses notifications on pick up, or removal from pocket.

 

[fosunite]

I am pleased to hear everything is working well for you.

As far as sim1/sim2 goes, I only have a single sim card in my OP5, so I have not seen anything with it saying sim2 is not working. It automatically disables sim2 on boot. I will take a look this weekend, and bring it up to the team, see if there is anything we have changed that would affect sim1/sim2.

To the best of my knowledge, we have no feature to disable always on display. There are options to disable the Ambient Display, but that only affects whether the display pulses notifications on pick up, or removal from pocket.

Thanks for the reply.
About sim1 and sim2: i use both simcards and when i reboot, i ve noticed, that one of my simcards caught up reception quicker than the other one. So i got that message just like that i ve attached in the post. Although both are working after 10seconds, i still need to acknowledge with "no" to keep my settings with the standard sim cards.

It s quite hard finding the option to disable alwaysOn display. I ve tried finding the option through settings=>display=>ambient display but it does not turn off the ambient display. Instead, i had to enter the keyword ambient on the searchbar in settings and click on the first entry to disable the option.

I find it quite misleading that the term ambient display is there but you cannot find the actual option to disable alwaysON. Please see picture 2 and 3 and 4.

 

[shane87]

Thanks for the reply.
About sim1 and sim2: i use both simcards and when i reboot, i ve noticed, that one of my simcards caught up reception quicker than the other one. So i got that message just like that i ve attached in the post. Although both are working after 10seconds, i still need to acknowledge with "no" to keep my settings with the standard sim cards.

It s quite hard finding the option to disable alwaysOn display. I ve tried finding the option through settings=>display=>ambient display but it does not turn off the ambient display. Instead, i had to enter the keyword ambient on the searchbar in settings and click on the first entry to disable the option.

I find it quite misleading that the term ambient display is there but you cannot find the actual option to disable alwaysON. Please see picture 2 and 3 and 4.

I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.

In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).

 

[shadowstep]

Added to the OnePlus 5 Index Thread here.

 

[fosunite]

I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.

In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).

Sorry it will take a while, because i am unfamiliar with doing logcat. I will try connect my phone to pc via adb and try to log the events. It s quite tough doing while phone should boot.

 

[rikkker]

newest build (01/31) doesnt boot for me (it reboots to twrp)
anyone else facing this issue?

 

[fosunite]

I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.

In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).

Ok, Finally managed to pull a logcat. Hope this helps.

newest build (01/31) doesnt boot for me (it reboots to twrp)
anyone else facing this issue?

I ve been there. Please do following steps:

1) If you have wiped data/factory reset already Flash Rom
2) Flash Gapps
3) Flash a no verity OP5

DO not flash Magisk. do your first boot and then flash magisk afterwards. Also some magisk plugins like Oxy ify doesnt let you boot.

 

[shane87]

Ok, Finally managed to pull a logcat. Hope this helps.

I ve been there. Please do following steps:

1) If you have wiped data/factory reset already Flash Rom
2) Flash Gapps
3) Flash a no verity OP5

DO not flash Magisk. do your first boot and then flash magisk afterwards. Also some magisk plugins like Oxy ify doesnt let you boot.

Thanks for the logcat. I'll dig into it this weekend and see if it shows anything interesting. Quick question, have you tried lineage 16? If so, does it do the same thing as far as the sim1/sim2? Since we base off of Lineage, I want to make sure that the issue is linked to AOKP, and not something that we have inherited from lineage. I only have a single sim, so I can't test myself.

On the flashing sequence, I have personally never had any issues with flashing magisk right away, but ymmv. I do a wipe/factory reset, (after backing up via tibu and/or nandroid back up in twrp), manually wipe system, cache, and dalvik cache, flash ROM, flash magisk, flash gapps. Again, YMMV.

Also, you ONLY need the no verity flash if you have unencrypted your data partition. I left my data partition encrypted.

I have not flashed the 01/31 build yet, but I will check it out, probably tomorrow.