yashsingh1/xdaforums huggingface dataset:
[OnePlus 5 & 5T Cross Device Development] robertogl:
AOSP for OnePlus 5/5T - Android 14​

Introduction

View attachment 6017843

This ROM is based on the work on Android 13 from here: https://xdaforums.com/t/rom-13-0-oneplus-5-5t-aosp-for-oneplus-5-20-sep-2023.4480549/

As usual, only builds with enforcing SELinux, no root access and 'user Android build flavor' will be posted here.

Known issues

None that I'm aware.

Changelog

See second post.

Download

Releases can be found on SourceForge:

OnePlus 5 (Cheeseburger): https://sourceforge.net/projects/aosponeplus/files/Cheeseburger_OTA_A14_4.14/

OnePlus 5T (Dumpling): https://sourceforge.net/projects/aosponeplus/files/Dumpling_OTA_A14_4.14/

Installation

Backup everything.

The provided zip can be installed using the TWRP recovery: clear data while doing that.

The ROM expects the firmware from OOS 10.0.1: different firmwares are not tested.

LiteGapps are available for Android 14.

The provided recovery allows only flashing signed images: use TWRP if you need to flash GApps or different packages.

Sources

Kernel on github: https://github.com/roberto-sartori-gl/4.14-kernel-oneplus-msm8998

ROM sources: https://github.com/roberto-sartori-gl/local_manifests/tree/a14/gl

Telegram discussion group here!

XDA:DevDB Information

AOSP for OnePlus 5/5T, ROM for the OnePlus 5/5T

Contributors

robertogl

Thank you to @T1mb3

ROM OS Version: Android 14

ROM Kernel: Linux 4.14.x

Version Information

Status: Initial release

Created 2023-10-05

Last Updated 2024-07-02
[OnePlus 5 & 5T Cross Device Development] robertogl:
Changelog

New release, 02/07/2024

- Cheesburger

- Dumpling

Changelog:

Synced with AOSP android-14.0.0_r53 (July security patches)

Upgrade to kernel 4.14.348 (OpenELA)

Fix an issue causing the dialer to not be working after installing gapps

New release, 19/06/2024

- Cheesburger

- Dumpling

Changelog:

Synced with AOSP android-14.0.0_r51

Fixed display brightness level on Dumpling (5T)

New release, 12/06/2024

- Cheesburger

- Dumpling

Changelog:

Added back DocumentsUI

New release, 12/06/2024

- Cheesburger

- Dumpling

Changelog:

June 2024 security patches, Synced with AOSP android-14.0.0_r50

Android 14 QPR3

Signed build (let me know if there are issues upgrading from previous build!)

Replaced AOSP apps with Fossify apps - https://github.com/FossifyOrg (https://github.com/FossifyOrg)

New release, 30/04/2024

- Cheesburger

- Dumpling

Changelog:

Fix call recording

Fix an issue that was causing the volume to be fixed during calls

Sync blobs with Lineage

Fix an issue that was causing the wifi to disconnect every 5 minutes under certain condition

Fix data on second sim

New release, 03/04/2024

- Cheesburger

- Dumpling

Changelog:

April 2024 security patches, Synced with AOSP android-14.0.0_r30

Fix notifications light not working immediately after boot

Support DSU (Dynamic System Updates) (from adb)

New release, 24/03/2024

- Cheesburger

- Dumpling

Changelog:

Various kernel updates

- Enable incremental fs

- Enable verity fs

Use and mount the metadata partition

- The previously unused logdump partition is used as metadata partition

Fix gestures not working

Include Open Camera as default camera app (AOSP camera has been removed)

March 2024 security patches

Synced with AOSP android-14.0.0_r29 (QPR2 release)

New release, 07/03/2024

- Cheesburger

- Dumpling

Changelog:

March 2024 security patches

Synced with AOSP android-14.0.0_r29 (QPR2 release)

06/02/2024

- Cheesburger

- Dumpling

Changelog:

February 2024 security patches

Synced with AOSP android-14.0.0_r25

Various kernel fixes (fixed slow boot, fixed usb tethering)

07/12/2023:

- Cheesburger

- Dumpling

Changelog:

December 2023 security patches

Synced with AOSP android-14.0.0_r17

Various kernel fixes

07/11/2023:

- Cheesburger

- Dumpling

Changelog:

November 2023 security patches

Synced with AOSP android-14.0.0_r12

Updated to kernel 4.14.314

Various kernel fixes

22/10/2023:

- Cheesburger

- Dumpling

Changelog:

Synced with AOSP android-14.0.0_r10

Updated to kernel 4.14.304

Removed some flags from the cmdline to trick safetynet

Added 'deny_usb' proc node

Started working on the support for Android 14 QPR1

08/10/2023:

- Cheesburger

- Dumpling

Changelog:

Fix 'Wallpaper & Style' section crash in the Settings app

05/10/2023:

- Cheesburger

- Dumpling

Changelog:

First release, October 2023 security patches, synced with AOSP android-14.0.0_r1
[OnePlus 5 & 5T Cross Device Development] robertogl:
Reserved
[OnePlus 5 & 5T Cross Device Development] robertogl:
@sunblade7 mm this should not happen, it happens if you sync from the main branch though. Can you check the last commit hash on frameworks/opt/net/wifi/ and hardware/qcom/wlan?
[OnePlus 5 & 5T Cross Device Development] robertogl:
Minor release:

Changelog

New releases:

- Cheesburger

- Dumpling

Changelog:

Fix 'Wallpaper & Style' section crash in the Settings app
[OnePlus 5 & 5T Cross Device Development] shibaa987:
As of now only LiteGApps for Android 14 is available:

Android 14 GApps Download

Android 14 GApps contains all Google Apps packages which are required after installing an Android 14 custom ROM. Visit this link to download several GApps packages.

cyanogenmods.org
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Oops. I didn't checkout manifests correctly. Everything is working correctly now. Builds just fine.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Perfect!
[OnePlus 5 & 5T Cross Device Development] sunblade7:
@robertogl When I boot recovery from an a14 user build, recovery encounters an error and shows the belly-up droid with the text "No command" and no recovery menu options. I can bypass the error and get the recovery menu by pressing volume-up and power quickly. The issue is not present for recovery from a userdebug build.

I first encountered this in a13 r67 that I thought might go away with a14 but it hasn't so I thought I would ask if you have observed this as well.
[OnePlus 5 & 5T Cross Device Development] robertogl:
This is the expected behavior with AOSP recovery, not sure what google was thinking:)
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Ok that is news to me but good to know. I see standard incremental/full OTAs work fine anyways. But 2-step OTAs are broken, which means I can't update the recovery partition via OTA.

Do you know how to prevent the "No command" error from showing? It would be nice if I could fix 2-step OTAs.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Is there a reason you are using stock recovery and not TWRP?
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Yes I'm building a custom ROM with a custom recovery.
[OnePlus 5 & 5T Cross Device Development] robertogl:
If userdebug doesn't behave the same, you can check where the build variant is verified and modify that path.
[OnePlus 5 & 5T Cross Device Development] Bubble-be:
Just reporting in that I'm now running A14 + Litegapps + Magisk Delta without major problems. There are some minor things, but it's not clear to me yet if it's just A14 or one my apps misbehaving.

You do a great job of keeping this device alive. :love:

I have one small request though: all the references/text name in the rom only say 5 on the 5T, could you change that?
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Are these changes by chance pushed up already?
[OnePlus 5 & 5T Cross Device Development] Slamb:
when i install android 13 + litegapps lite for a13, it shows meets_device_integrity + meets_basic_integrity and device is certified in google play store, but with android 14 + litegapps lite for a14, i get only meets_basic_integrity and play store shows device not certified 😔 it causes problems with several apps like banking, google wallet etc, what could be wrong? 🤔 i always wipe everything and i dont root, just os + lite gapps lite in both cases
[OnePlus 5 & 5T Cross Device Development] robertogl:
Did you also install magisk and safety net modules? That is needed in some cases.
[OnePlus 5 & 5T Cross Device Development] Slamb:
no, just os and litegapps lite, with android 13 it works fine, only with android 14 is this problem now :unsure:

i would not rather install magisk because i dont need rooting, if there was a way how to fix this device integrity check
[OnePlus 5 & 5T Cross Device Development] techster69:
I see good things happening. Awesome!
[OnePlus 5 & 5T Cross Device Development] robertogl:
New release, 30/04/2024

- Cheesburger

- Dumpling

Changelog:

Fix call recording

Fix an issue that was causing the volume to be fixed during calls

Sync blobs with Lineage

Fix an issue that was causing the wifi to disconnect every 5 minutes under certain condition

Fix data on second sim
[OnePlus 5 & 5T Cross Device Development] kranthir42:
install instructions from and13 ver of this rom???
[OnePlus 5 & 5T Cross Device Development] robertogl:
Like any update, recovery and flash rom, Gapps, magisk if you have it.
[OnePlus 5 & 5T Cross Device Development] kranthir42:
no firmware or diff files??? no wipe???
[OnePlus 5 & 5T Cross Device Development] robertogl:
No firmware, no wipe, I don't know what 'diff files' are.
[OnePlus 5 & 5T Cross Device Development] kranthir42:
you dont need to wipe from going from android 13 to 14???
[OnePlus 5 & 5T Cross Device Development] robertogl:
No?
[OnePlus 5 & 5T Cross Device Development] JMS74:
I'm using still the lastest official version of OxygenOS on my op5 (cheeseburger).

I don't have ever unlock the bootlader (on this phone at least) and so never installed anything on it except official updates.

Not even changed the recovery cause I didn't unlock the bootlader.

But things have changed since I bought the op5. Partitions, methods of unlocking, flashing and other stuff necessary seem to have changed a lot.

Can anyone tell me on a concise step by step process of what I have to do to install this when considerind the status of my op5, original until the last OxygenOS 10 for the op5.

Please help,.gradly and enormously be grateful.
[OnePlus 5 & 5T Cross Device Development] sunblade7:
@JMS74 The usual instructions apply:

- Backup your stuff

- Enable Developer Options

- Enable OEM unlock

- Reboot to fastboot (VOL UP + POWER)

- Unlock bootloader: fastboot oem unlock (WARNING: ALL YOUR DATA IS GONE)

- Flash recovery and boot to recovery: fastboot flash recovery.img

- Install zip via ADB sideload: adb sideload full_ota.zip

@robertogl Are you able to grant the Call Logs permission to the Contacts app? I can't and if I open the contacts app it closes immediately and issues a toast that says "You have disabled a required permission". If I try to grant the permission with adb shell pm grant com.android.contacts android.permission.READ_CALL_LOG it gives the error E PermissionManager: Cannot grant hard restricted non-exempt permission android.permission.READ_CALL_LOG for package com.android.contacts.
[OnePlus 5 & 5T Cross Device Development] robertogl:
It seems to be a permission added lately, I'll fix it on the next release.
[OnePlus 5 & 5T Cross Device Development] Deion86:
Thanks for this ROM. The stock Android 10 didn't work with OTG USB Cameras so I had to upgrade and found this for my OP5.

Using it with NikGapps Omni, Magisk, PlayIntegrityFork and Lawnchair.
[OnePlus 5 & 5T Cross Device Development] robertogl:
I tried to replicate this, but without success.

I flashed the image and the call log permissions is granted by default to the Contacts app (I can see this from the 'app permissions' view in the Settings)
[OnePlus 5 & 5T Cross Device Development] ntonto:
google pay working?
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Interesting. I just tried clearing the storage on the contacts app and it has the same problem. I installed a different contacts app as a workaround.
[OnePlus 5 & 5T Cross Device Development] Deion86:
I'm trying to use the "Extra Dim" feature from Android 12. I launched com.android.settings.Settings$ReduceBrightColorsSettingsActivity using Activity Launcher but as i enable it the phone sort of soft reboots.

I assume there is some support missing from the kernel or hardware? Or is there a way to enable this?
[OnePlus 5 & 5T Cross Device Development] Deion86:
Recently Google made in more difficult to pass device integrity. Apparently the rom/build needs to be signed with something other than the aosp test key. https://crdroid.net/blog/2024-06-01-sign-your-crDroid-builds-and-keep-play-integrity-happy

Could the next release be signed with "release keys" instead?
[OnePlus 5 & 5T Cross Device Development] robertogl:
It will be signed, yes.
[OnePlus 5 & 5T Cross Device Development] sunblade7:
There was a headphone jack problem reported some time ago where the icon remains in the status bar after unplugging. Actually I still see this issue almost on a daily basis. It doesn't happen if I plug/unplug fairly quickly. Seems to only happen when it is left plugged in for an extended time (say an hour?).

Is there anything I can do to help debug?
[OnePlus 5 & 5T Cross Device Development] robertogl:
Well I really cannot replicate the issue, which is the main reason it was not investigated :)

Does it happen randomly?
[OnePlus 5 & 5T Cross Device Development] sunblade7:
It seems fairly consistent given how regularly I run into it. So I wouldn't say it is random. It just seems to require that the plug is inserted into the jack for a long time. Let me know if there is something I can do to help.
[OnePlus 5 & 5T Cross Device Development] Lingaraj Guttedar:
How to install it .
[OnePlus 5 & 5T Cross Device Development] robertogl:
The thing is that I left the jack inserted like 12 hours and no issue, multiple times :D I'll try again just in case
[OnePlus 5 & 5T Cross Device Development] robertogl:
Do you detach the headphones while the device has the screen off/is deep sleeping, or with the screen on?
[OnePlus 5 & 5T Cross Device Development] ludskyrider:
Hello guys

I tested android 14 with lineageOS 21 and Elixir

But each time, I encounter a major problem: I use a Galaxy Watch 5 pro and in both cases I am absolutely unable to connect it. It seems that Google Mobile Service is missing or there is a bug.

Whereas for these same ROMs under Android 13 I have no problems.

Does this work with this ROM please?
[OnePlus 5 & 5T Cross Device Development] sunblade7:
I normally detach while the screen is on after manually stopping playback. Of course the screen is off while playing and does play long enough to enter deep doze.
[OnePlus 5 & 5T Cross Device Development] robertogl:
If you are playing music, the device does not enter deep sleep. It may doze though, but it should not be relevant.

Interesting issue that I cannot replicate yet :)
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Fair enough. Odd thing is I have multiple OP5 phones and on some devices I can not reproduce it either.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Ah, can you get logs after detaching the jack on devices with the issue? When the issue appears of course :)

So that we can check the differences.
[OnePlus 5 & 5T Cross Device Development] sunblade7:
I saw this in the logs after I pulled out the headphones and observed the stale headphones icon in the status bar:

06-10 22:00:01.240 815 1317 D audio_hw_primary: out_standby: enter: stream (0xf0e44330) usecase(0: deep-buffer-playback)
06-10 22:00:02.478 815 1317 D audio_hw_primary: disable_audio_route: reset and update mixer path: deep-buffer-playback headphones
06-10 22:00:02.481 815 1317 E soundtrigger: audio_extn_sound_trigger_update_stream_status: invalid input device 0x0, for event 2
06-10 22:00:02.481 815 1317 D soundtrigger: audio_extn_sound_trigger_update_stream_status: uc_info->id 0 of type 0 for Event 2, with Raise=1
06-10 22:00:02.481 815 1317 I sound_trigger_platform: platform_stdev_check_and_update_concurrency: Received STREAM event, event type 2, usecase type 0
06-10 22:00:02.481 815 1317 D sound_trigger_platform: platform_stdev_check_and_update_concurrency: dedicated path 0, reset backend 1, tx 0, rx 0,concurrency session allowed
06-10 22:00:02.481 815 1317 D msm8974_platform: platform_split_snd_device: snd_device(9) num devices(0) new_snd_devices(0)
06-10 22:00:02.481 815 1317 I msm8974_platform: platform_get_custom_mtmx_params: no matching param with id 0 ip_ch 2 op_ch 2 uc_id 0 snd_dev 9
06-10 22:00:02.482 815 1317 D hardware_info: hw_info_append_hw_type : device_name = headphones
06-10 22:00:02.482 815 1317 D audio_hw_primary: disable_snd_device: snd_device(9: headphones)
06-10 22:00:02.482 815 1317 D msm8974_platform: platform_split_snd_device: snd_device(9) num devices(0) new_snd_devices(0)
06-10 22:00:02.495 815 1317 I soundtrigger: audio_extn_sound_trigger_update_device_status: device 0x9 of type 0 for Event 0, with Raise=0
06-10 22:00:02.495 815 1317 D audio_hw_primary: out_standby: exit

I'm not sure if that captured anything useful. I'll try to capture more logs when it happens.
[OnePlus 5 & 5T Cross Device Development] robertogl:
New release, 12/06/2024

- Cheesburger

- Dumpling

Changelog:

June 2024 security patches, Synced with AOSP android-14.0.0_r50

Android 14 QPR3

Signed build (let me know if there are issues upgrading from previous build!)

Replaced AOSP apps with Fossify apps - https://github.com/FossifyOrg (https://github.com/FossifyOrg)
[OnePlus 5 & 5T Cross Device Development] aldosu:
Everything is ok, except play protect certificate says not certified.
[OnePlus 5 & 5T Cross Device Development] robertogl:
New release, 12/06/2024

- Cheesburger

- Dumpling

Changelog:

Added back DocumentsUI
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Do you have a commit to push that updates rs.xml comment to r50?
[OnePlus 5 & 5T Cross Device Development] robertogl:
Code has been pushed right now!
[OnePlus 5 & 5T Cross Device Development] robertogl:
New release, 19/06/2024

- Cheesburger

- Dumpling

Changelog:

Synced with AOSP android-14.0.0_r51

Fixed display brightness level on Dumpling (5T)
[OnePlus 5 & 5T Cross Device Development] whywilson:
Thank you. I was trying to flash back to Android 13 because of the brightness. You saved my time.

And the file picker is not working on the last build. I'm trying on this.
[OnePlus 5 & 5T Cross Device Development] satand:
thanks again for this great rom. works perfect.

is there a way to hide magisk root properly? i can't get some apps working because of the detected root. it worked with A13.
[OnePlus 5 & 5T Cross Device Development] wannabegt4:
What GApps is everyone using? I tried NikGapps and it didn't replace the default apps which caused some issues namely not being able to answer incoming calls. I'm wondering if this is because of the move to Fossify apps?
[OnePlus 5 & 5T Cross Device Development] robertogl:
Correct, you need to remove/rename the '/vendor/overlay/Telecom__aosp_cheeseburger__auto_generated_rro_vendor.apk' file from recovery to fix this issue.

I don't have a solution for it as it should be the nikgapps package to remove this overlay, but of course they don't know that people may be using different apps compared to the AOSP ones...

I'll probably switch back to the AOSP dialer starting from the next release.
[OnePlus 5 & 5T Cross Device Development] wannabegt4:
Thanks for the quick reply and thanks for your work keeping this perfectly capable phone relevant.
[OnePlus 5 & 5T Cross Device Development] robertogl:
I may have actually found a solution for that dialer/calls issue, it will be included in the next release.
[OnePlus 5 & 5T Cross Device Development] robertogl:
File picker should work on the latest release, it has already been fixed.
[OnePlus 5 & 5T Cross Device Development] Deollzz:
Hello robertogl

When I follow your build instructions on Github, I get an error message during repo sync: "Please make sure that the correct access permissions exist

and the repository exists".

The ssh access to Github is configured correctly.

Do I need special permissions to access your "local_manifests" ? sources on Github.

I found your instructions on Github and wanted to try it myself.

Thank you very much

Regards deollz
[OnePlus 5 & 5T Cross Device Development] robertogl:
You need access to the vendor blobs repo, give me your GitHub username to get access
[OnePlus 5 & 5T Cross Device Development] Deollzz:
Hello robertogl,

wow I'm flattened, that was quick.

My user name : deollz

Thank you very much for saving the rainy Sunday.

Best regards deollz
[OnePlus 5 & 5T Cross Device Development] robertogl:
I added the username, you should have access now.

You need of course you have your ssh key in your building machine.
[OnePlus 5 & 5T Cross Device Development] Deollzz:
the output of ssh -T git@github.com results in :

Hello deollz! You've successfully authenticated, but GitHub does not provide shell access.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Just sync, you don't need to enter via ssh of course.
[OnePlus 5 & 5T Cross Device Development] Deollzz:
Hi robertogl

I don't want to be annoying, when fetching I get the following message: "ERROR: Repository not found.

fatal: Could not read from remote repository.

Please make sure that you have the correct access permissions

and the repository exists."

Did I miss something in your build instructions on Github ?

So far I have compiled Lineageos for my cell phones and included TheMuppets for the vendor blobs, which was simple in comparison.

Sorry if I'm being too stupid.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Just try 'repo sync vendor/oneplus/msm8998-common/' and see if it gives you error.

You need to load your ssh keys to allow repo to use it.
[OnePlus 5 & 5T Cross Device Development] Deollzz:
"repo sync vendor/oneplus/msm8998-common/" results in :

fetching: 0% (0/1) 0:05 | 1 job | 0:05 OnePlus-5-T/4.14-vendor_oneplus_msm899..

ERROR: Repository not found.

fatal: Could not read from remote repository.

Please make sure that you have the correct access permissions

and the repository exists.

OnePlus-5-T/4.14-vendor_oneplus_msm8998-common:

ERROR: Repository not found.

fatal: Could not read from remote repository.

Please make sure that you have the correct access authorizations

and that the repository exists.
[OnePlus 5 & 5T Cross Device Development] robertogl:
You have to add your ssh to your system :) It depends on your system of course, usually this is enough https://docs.github.com/en/authenti...rm=linux#adding-your-ssh-key-to-the-ssh-agent
[OnePlus 5 & 5T Cross Device Development] Deollzz:
That's exactly what I did, following these instructions
[OnePlus 5 & 5T Cross Device Development] robertogl:
Can you access the repo from the browser?

Loading

github.com
[OnePlus 5 & 5T Cross Device Development] robertogl:
Did you accept the invite via mail? Github should have sent it to you.
[OnePlus 5 & 5T Cross Device Development] Deollzz:
Oops shame on my head after confirming the dialog it worked directly :

repo sync vendor/oneplus/msm8998-common/

Fetching: 100% (1/1), done in 16.397s

vendor/oneplus/msm8998-common/: leaving master; does not track upstream

Checking out: 100% (1/1), done in 0.766s

repo sync has finished successfully.

Sorry, I did not check the emails.

In any case, you can drink a cold beer to me for the time you are taking
[OnePlus 5 & 5T Cross Device Development] Deollzz:
via Paypal ogru.....
[OnePlus 5 & 5T Cross Device Development] Deollzz:
II hope you can get a cold beer for 10€ (depending on where you live).
[OnePlus 5 & 5T Cross Device Development] robertogl:
Yup, appreciated!
[OnePlus 5 & 5T Cross Device Development] Deollzz:
well done
[OnePlus 5 & 5T Cross Device Development] satand:
how do i get the custom led manager working on this rom? it is activated in settings extra and i am using the config file from the A13 rom.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Mm it should work exactly the same as on a13