yashsingh1/xdaforums huggingface dataset:
[OnePlus 5 & 5T Cross Device Development] robertogl:
1) The user data should always be kept, can you clarify the update procedure you used?

2) There is no pixel launcher in the ROM, so this is expected.

3) Due to the latest changes in Play Integrity from Google, the ROM is not expected anymore to pass play integrity/be certified without magisk modules. I'm not fighting Google anymore as at this point op5 is just not certified anymore.

4) I don't even know that 'at a glance' is :D Is it a google thing (not AOSP)?

5) I cannot replicate it. Do you see it in the stock settings app?
[OnePlus 5 & 5T Cross Device Development] robertogl:
I just updated the local manifest.
[OnePlus 5 & 5T Cross Device Development] aldosu:
I always do the update the same way and it always worked for me until this last update. I download the .zip of the image and the gapps and proceed to install them both from Teawin

After the first boot, I install the pixel launcher that I downloaded from apkmirror and apparently everything works. The phone certification happens after 10 days or so.

The at a glance is a pixel widget that is placed at the top left with various information about events, tasks, time, etc. Before this version everything worked correctly, now it only shows the current date.

And finally about the history, I'll send you a screenshot to see if it clarifies anything. That light colored background is impossible to change.

It happens in any area where I use Google search.

I insist this, everything started to happen to me with this new version.

Thanks a lot
[OnePlus 5 & 5T Cross Device Development] aldosu:
I think I have found a solution to this last point. I downloaded the October version from apkmirror of pixel launcher and it has been resolved. I will continue investigating the rest but the problem may come from the version of pixel launcher.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Cool.

Actually the thing I'm most worried about is the data loss during the update, even if this is the first (and only report) I had.
[OnePlus 5 & 5T Cross Device Development] bonswouar:
Glad to see everything seems to work, I hope this means a LOS 21 release might be on the way :)

Although I personally use microG, and I'm not sure how close it is to be usable on a14..
[OnePlus 5 & 5T Cross Device Development] im32day:
how unlock bootloader+flash twrp on 1+5
[OnePlus 5 & 5T Cross Device Development] satand:
@robertogl

many thanks for your work. thanks to you I'm still using my OP5 as my daily driver.

my OP5 is currently on your android 13 rom. is this rom stable enough for an update?

I would like to use my OP5 as a digital key for my BMW car. but the BMW app does only support a few devices like:

Google Pixel 8 / 7 / 7a / 7 Pro / 6 / 6a / 6 Pro / Fold, Android 13 or newer.

OnePlus 11* / Open, Android 13 or newer.

Do you have an idea how to spoof the device to become one of the above? I already tried to use magisk hide props config. but the fingerprints used by the module are android 12. it does not work...maybe because of the A12 fingerprints, maybe for another reason.
[OnePlus 5 & 5T Cross Device Development] DigitalCorrosion:
Really wanna make the jump but afraid my banking apps etc wont work with this. Anyone have any issues with banking apps?

I'm on 10.0.1 official if that helps.

Don't care to root my phone as it is. Can we get a definitive list of what is/not working? I have flipped through the thread and saw a few issues but havent seen many of them saying they are resolved.
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Is USB tethering expected to work? On the latest version of the OS, enabling USB tethering freezes the phone and reboots shortly thereafter. Nothing much in the logs:

I TetheringManager: startTethering caller:com.android.settings

Of course a WiFi hotspot is a reasonable fallback. Also realized that ethernet tethering is a thing and it works.
[OnePlus 5 & 5T Cross Device Development] robertogl:
This is a recent issue, right?

I remember I tested USB tethering and it was working fine until a couple of months ago, but yeah, now it is not working anymore.
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Unfortunately I don't have any information on when this issue began. I only recently tried USB tethering.
[OnePlus 5 & 5T Cross Device Development] robertogl:
No problem, I found the issue in the kernel: it was a commit introduced a month ago.

I'll include the revert that will fix the issue starting with the next release.
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Awesome. Good to hear.

Would it be possible to include USB tethering in the available list of quick tiles? I'm not sure if it is supported anymore but if it is it would go here.
[OnePlus 5 & 5T Cross Device Development] sunblade7:
When I initially tested USB tethering, WiFi hotspot, and ethernet tethering, I was using WiFi as the internet source. In that case WiFi hotspot and ethernet tethering successfully provided internet to my laptop (USB tether produced a crash, as noted above).

Recently I tested it "properly" and used cellular data as the internet source. I'm finding that it refuses to provide internet if the internet source is cellular data. Both WiFi hotspot and ethernet tethering provide a link to my laptop, which reports the connection as "connected". But nothing is routable. No DNS, No IP ping. Nada.

I thought that was strange so I tested a few different versions of this ROM:

- A14 Oct 5 2023

- A13 Dec 17 2022

Same results. All ROMs refuse to provide 4G internet to a laptop via WiFi hotspot or ethernet tethering.

I also confirmed these results for the hotspot using a second cell phone. No routing. Device reports "No internet" after connecting to WiFi hotspot.

Is this a known issue?

I should also note that the OP5 does have cellular data for itself, just tethering/hotspot is not working. I know the SIM card is not the issue because I can do tethering/hotspot without issues if I insert it into another phone or use Lineage OS on my OP5.
[OnePlus 5 & 5T Cross Device Development] robertogl:
There will be fixes for tethering starting with the next release, let me know after it is released.

I was not able to replicate your issues but these fixes may help.
[OnePlus 5 & 5T Cross Device Development] robertogl:
New 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)
[OnePlus 5 & 5T Cross Device Development] Wisniew:
Hi, I found a bug. When I unplug the wired headphones using the jack I can still see the headphones indicator on the status bar. at this point all apps think the headphones are not connected except for the phone call app. In order for me to hear the caller I have to reconnect the headphones and listen though headphones or reboot the phone so I can hear the conversation through the phone's speaker.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Does this always happen?

I don't see this issue, I've tried multiple times and rebooting various times but the indicator on the status bar always disappears after I unplug the headphones.
[OnePlus 5 & 5T Cross Device Development] Wisniew:
Only when I leave the headphones plugged in all night. When I plug it in and unplug it after a while it works fine.
[OnePlus 5 & 5T Cross Device Development] sunblade7:
USB tethering and WiFi hotspot are now working (y)
[OnePlus 5 & 5T Cross Device Development] robertogl:
Cool!
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Well this is a bit of a doozy. WiFi hotspot and USB tethering were working flawlessly on this latest build since I posted. Then a few days ago, with no changes to the system, it just stopped working. I tried rebooting, wiping Dalvik/cache but it has regressed to the prior behavior. Only other thing I could test is wipe + reflash. Any clues?

Also I do get the headphone jack issue. It is sometimes difficult to reproduce. Sometimes it happens over short periods of time (< 30 min), sometimes it does not happen overnight. Race condition? It's a bit of a nasty one because it mutes notifications until next reboot.

Thanks in advance for all your hard work on this ROM!
[OnePlus 5 & 5T Cross Device Development] robertogl:
New release, 07/03/2024

- Cheesburger

- Dumpling

Changelog:

March 2024 security patches

Synced with AOSP android-14.0.0_r29 (QPR2 release)
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Somehow flashing the latest zips fixed the hotspot/tether issue so please ignore those details in my last post. :D

I noticed that a fresh clone of the AOSP cheeseburger repo fails on lunch (after . build/envsetup.sh) and no build targets are listed:

Warning: Cannot display lunch menu.

Note: You can invoke lunch with an explicit target:

usage: lunch [target]

Which would you like? [aosp_arm-trunk_staging-eng]
Pick from common choices above (e.g. 13) or specify your own (e.g. aosp_barbet-trunk_staging-eng)

Seems related to TARGET_RELEASE in envsetup.sh. Did you address this on your end? Any commits not pushed?
[OnePlus 5 & 5T Cross Device Development] robertogl:
Commands to build have changed, I did update the instructions though so the new ones should work.
[OnePlus 5 & 5T Cross Device Development] aldosu:
Hello. Everything ok except one thing, gesture navigation does not work correctly. The return to home gesture does not work. I have tried to download the new version from the 9th but it is not possible.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Yeah this should be fixed in the next release (in the next days).
[OnePlus 5 & 5T Cross Device Development] robertogl:
I uploaded a new release (March 11), could you try that one?
[OnePlus 5 & 5T Cross Device Development] aldosu:
I don't know the reason but the links don't work.

aosponeplus - Browse /Cheeseburger_OTA_A14_4.14/11-Mar-2024 at SourceForge.net

sourceforge.net
[OnePlus 5 & 5T Cross Device Development] robertogl:
Working fine for me (?)
[OnePlus 5 & 5T Cross Device Development] aldosu:
I have tried from 2 mobile phones and from a PC and nothing goes down. I have tried changing the mirror and only San Diego appears
[OnePlus 5 & 5T Cross Device Development] aldosu:
I have managed to find the file but it downloads very slowly. I'll let you know.
[OnePlus 5 & 5T Cross Device Development] aldosu:
I tell you: I have proceeded with the installation of only the new image from the 11th, but I was getting various Google errors, including Google Play. I have proceeded to install the Google applications https://sourceforge.net/projects/ni...ps-full-arm64-13-20240307-signed.zip/download The problem is that now only Pixel Launcher appears and not the default one and no gesture works for me
[OnePlus 5 & 5T Cross Device Development] robertogl:
GApps have not been updated to support qpr2 from what I know, so this may cause *some* issues
[OnePlus 5 & 5T Cross Device Development] aldosu:
De acuerdo
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Ok I see the new build command in the OTA instructions but there is still one lunch command that has not been updated in the readme:

lunch aosp_cheeseburger-user

I have updated my build commands and it builds fine now (y)
[OnePlus 5 & 5T Cross Device Development] robertogl:
Ah right, fixed now :)
[OnePlus 5 & 5T Cross Device Development] sunblade7:
I can confirm the HOME button/gesture issue is fixed on the latest build :D

Have you considered adding more Google kernel repos to removed.xml in local_manifests? Some of them are quite beefy. I have these added locally:

<remove-project name="device/google/bluejay-kernel" />
<remove-project name="device/google/felix-kernel" />
<remove-project name="device/google/lynx-kernel" />
<remove-project name="device/google/pantah-kernel" />
<remove-project name="device/google/raviole-kernel" />
<remove-project name="device/google/shusky-kernel" />
<remove-project name="device/google/tangorpro-kernel" />
[OnePlus 5 & 5T Cross Device Development] kranthir42:
is there a file picker ui like documentsui???
[OnePlus 5 & 5T Cross Device Development] satand:
when updating from A13 to A14 is a wipe including media mandatory or does it work without wiping media (but all other partitions)?
[OnePlus 5 & 5T Cross Device Development] robertogl:
If you are on AOSP13, you don't need to wipe anything.
[OnePlus 5 & 5T Cross Device Development] robertogl:
I did have more repos in the past, however sometimes google likes to remove repos and if they remove one of these repo, we get an error while syncing that needs to be fixed.

They are big repos but they are just downloaded once so... You can of course keep your local manifest with these too :)
[OnePlus 5 & 5T Cross Device Development] satand:
thanks! yes, its your A13 rom I want to update.
[OnePlus 5 & 5T Cross Device Development] kaidelorenzo:
@sunblade7 are you currently building your own signed images to use with a locked bootloader? Do you think yellow state might be good enough to get play integrity to pass device level?
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Almost certainly no. There's no GAPPs, no green state and no Qualcomm SPU so no hardware-backed attestation.

If you want Google verification, use a stock googled device. This is the wrong ROM for that purpose.
[OnePlus 5 & 5T Cross Device Development] kaidelorenzo:
The OnePlus 5 doesn't really support hardware attestation at all though right (isn't only AVB 1.0)? But even so Stock OOS passes play integrity (or at least up through level 2 which is enough for most everything)
[OnePlus 5 & 5T Cross Device Development] robertogl:
There is no correlation between bootloader status and passing play integrity on op5 because any magisk module can just fake the bootloader status.

Locking the bootloader only gets rid of the 5 seconds wait at boot, that why I removed support: it is basically useless.
[OnePlus 5 & 5T Cross Device Development] kaidelorenzo:
Ok yeah. You're right thanks. Getting to a yellow status isn't going to mean anything.
[OnePlus 5 & 5T Cross Device Development] robertogl:
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)
[OnePlus 5 & 5T Cross Device Development] jauhari:
why didn't include GCam?
[OnePlus 5 & 5T Cross Device Development] robertogl:
Open camera is open source.
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Nice work on the latest updates. Builds and works fine for me.

I think I found an old bug. Can you please confirm if you observe the same?

- Reboot phone (ensure internet will automatically reconnect)

- Turn off screen and send a message to trigger a notification on the phone

- PROBLEM: Observe the notification LED does not light up

- SOLUTION: Plug in a charging cable to force the charging LED on for a few seconds

- Turn off screen without checking message and observe the notification LED is working again (or just send another message)

I can reproduce this on every reboot, even on older builds.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Thanks for the report.

This should be fixed in the next release. If you build from sources, I already pushed the change (vendor/rs) so you should be able to test this already.
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Pulled, built, flashed and confirmed it is fixed!
[OnePlus 5 & 5T Cross Device Development] robertogl:
Great!
[OnePlus 5 & 5T Cross Device Development] DuckDodger70:
@robertogl Are there any issues with the recent apps button? I'm able to touch it and feel the vibration but nothing is actually happening...

Am i missing a setting or something??
[OnePlus 5 & 5T Cross Device Development] robertogl:
Third party launcher?
[OnePlus 5 & 5T Cross Device Development] DuckDodger70:
Currently using Nova. Was originally using Pixel Launcher but having the exact same issue...

Decided to reflash and all seems to be working fine now. Just installed Nova again and seems to be working fine.
[OnePlus 5 & 5T Cross Device Development] techster69:
Awesome!!!

How long will this ROM be maintained, any idea?
[OnePlus 5 & 5T Cross Device Development] robertogl:
It depends on how many years my op5 will survive :)
[OnePlus 5 & 5T Cross Device Development] techster69:
Hahaha, I gotta say, it's one tough phone. I have it since April 2019. Using it without a case for almost a year now. I still can't let go of it :)
[OnePlus 5 & 5T Cross Device Development] robertogl:
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)
[OnePlus 5 & 5T Cross Device Development] brianyz:
I've been running these AOSP 13/14 roms on my OP5 and they run perfect. I bought a new OP9 last year, and other than the display, I don't really notice a huge performance difference.

I have a quick general question about the OP5 since we are all tinkering with it. Ever since flashing custom roms (Lineage, Derp, CRDoid, etc) to it, I would randomly get bootloops after rom updates, or it wouldn't boot, boot to rom boot animation then restart, etc. I would restore a TWRP backup, but they rarely worked either. Restoring a full TWRP backup, then flashing the latest rom over it sometimes would work. Only thing that worked 100% of the time was to wipe the phone and format data and start over... which got old every month. It was never the same behaviour, just a phone that wouldn't boot to the launcher.

Mainly since using ASOP 14 I've learned that just restoring the boot backup from TWRP would work, but randomly it still wouldn't. Anyways, after all these years, I've narrowed it down to Magisk. When installing roms TWRP would do the addon Magisk survival script, and sometimes I would flash Magisk again just to see if it would help. One of these last rom updates I finally renamed Magisk to uninstall.zip and now get trouble free rom updates.

Question is, how are you guys handling Magisk when updating the rom?

For me it is:

1. TWRP flash new ROM (Magisk restores itself via survival script) and Encrypt disabler

2. reboot to TWRP and flash core Gapps

and thats it.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Procedure is quite simple , enter TWRP and without even rebooting flash in order

- ota zip

- Gapps

- magisk

- encrypt disabler stuff

Then reboot.
[OnePlus 5 & 5T Cross Device Development] sunblade7:
I think I found a bug in the March 7th release (absent in Feb 6 release) but it's rather unusual so I will take some time to explain it very carefully. The bug is observed as audio call disconnect every 5 minutes (like a clock) in Conversations. You're probably thinking how is a Conversations bug related to AOSP? I'm not sure myself but just read further and you can decide...

INITIAL CONDITIONS

Two OnePlus 5 phones with identical states:

- Flash Feb 6th AOSP ROM (OOS 10.01) and wipe data

- Latest F-Droid Conversations v2.14.1 installed

- conversations.im account configured

- Both phones on same WiFi LAN network (no STUN/TURN complexities here)

BASELINE PASSING TEST

- Start an audio call between the two phones

- OBSERVE: Call is stable. No disconnect/reconnect cycles.

FIRST FAILING TEST

- Upgrade Phone 1 to Mar. 7 release via OTA in recovery and wipe Dalvik/cache (Phone 2 stays on Feb 6th). No changes are made to Conversations on either phone.

- Start an audio call between the two phones

- OBSERVE: The call will show regular disconnect/reconnect cycles every 5 minutes (to the second) on Phone 2 (NOT Phone 1). The call on Phone 1 will appear stable.

SECOND FAILING TEST

- Upgrade Phone 2 to Mar. 7 via OTA (and wipe Dalvik/cache) so that now both phones are on the same OTA. No changes are made to Conversations on either phone.

- Start an audio call between the two phones

- OBSERVE:

- The call will show regular disconnect/reconnect cycles every 5 minutes on BOTH phones.

- The disconnect/reconnect cycles are out of sync for the two phones. So there are 2 disconnect/reconnect cycles per every 5 min (one for each phone).

Do you know what is the culprit here?
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Sample logs for passing test:

04-05 21:33:45.391 4020 4020 D conversations: toggle forced foreground service after receiving event (action=ping)
04-05 21:33:45.395 4020 4020 D conversations: defaulting to microphone foreground service type
04-05 21:33:45.403 4020 4020 D conversations: ForegroundService: on, notification: 10485760
04-05 21:33:45.407 4020 4058 D conversations: user@conversations.im send ping (action=ping,lowTimeout=false)
04-05 21:38:46.392 4020 4020 D conversations: toggle forced foreground service after receiving event (action=idle_ping)
04-05 21:38:46.395 4020 4020 D conversations: defaulting to microphone foreground service type
04-05 21:38:46.397 4020 4020 D conversations: ForegroundService: on, notification: 10485760
04-05 21:38:46.399 4020 4020 D conversations: toggle forced foreground service after receiving event (action=ping)
04-05 21:38:46.400 4020 4058 D conversations: user@conversations.im send ping (action=idle_ping,lowTimeout=false)
04-05 21:38:46.401 4020 4020 D conversations: defaulting to microphone foreground service type
04-05 21:38:46.403 4020 4020 D conversations: ForegroundService: on, notification: 10485760

Sample logs for failing test (notice 5 min interval):

04-05 23:29:58.707 4036 4490 D conversations: user@conversations.im: PeerConnectionState changed to DISCONNECTED
04-05 23:29:58.708 4036 4490 D conversations: defaulting to microphone foreground service type
04-05 23:29:58.710 4036 4490 D conversations: ForegroundService: on, notification: 10485760
04-05 23:29:58.710 4036 4490 D conversations: onStateChanged(1)
04-05 23:29:58.710 4036 4490 D conversations: onJingleRtpConnectionUpdate(RECONNECTING)
04-05 23:30:02.507 4036 4490 D conversations: user@conversations.im: PeerConnectionState changed to CONNECTED
04-05 23:35:00.274 4036 4490 D conversations: user@conversations.im: PeerConnectionState changed to DISCONNECTED
04-05 23:35:00.277 4036 4490 D conversations: defaulting to microphone foreground service type
04-05 23:35:00.289 4036 4490 D conversations: ForegroundService: on, notification: 10485760
04-05 23:35:00.289 4036 4490 D conversations: onStateChanged(1)
04-05 23:35:00.289 4036 4490 D conversations: onJingleRtpConnectionUpdate(RECONNECTING)
04-05 23:35:02.305 4036 4490 D conversations: user@conversations.im: PeerConnectionState changed to CONNECTED

And finally see attached file for over 1 hour of unfiltered ADB logs.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Did you tried also with telegram, WhatsApp, the default dialer, or any other app in general?
[OnePlus 5 & 5T Cross Device Development] sunblade7:
No. Unfortunately I don't have accounts with any of those apps. I'm unable to test regular POTS calls either. Just Conversations.
[OnePlus 5 & 5T Cross Device Development] robertogl:
Can you tru with the latest april release?

I'm trying now and the current call is lasting 7 minutes and proceeding with no issue.
[OnePlus 5 & 5T Cross Device Development] Mohdzubaidi:
Hello,

Thanks for your amazing work! ,

i want to ask about snapchat on this rom the camera is the same of the original rom ? not zoomed in on snapchat or getting stuck or anything like that,

iam using the camera on Snapchat and Instagram all the time
[OnePlus 5 & 5T Cross Device Development] sunblade7:
Unfortunately same problem with same timing on both phones after upgrading to latest April release. Did you monitor ADB logs for Conversations?
[OnePlus 5 & 5T Cross Device Development] robertogl:
Yes, I see the same logs you see on the working phone. No disconnection.

Wifi or 3g/4g?