yashsingh1/xdaforums huggingface dataset:
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] blaczero:
I searched this thread and cannot find anything on this. Apologize if it's been covered, please tell me where.

I just installed the latest Jaguar on my oneplus 8pro, having a strange issue. Boots fine, and when I get in I go to play store and try to install something I get "Free up space" (attached)

Then if I hit the "Settings>Storage" link in the "Free up space" screen it shows I have plenty of space available (attached)

Strangely it's saying I do have 32 gig of "Photos & video's" though, and I just installed this ROM.

Any help? I verified the play store has all permissions.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
You forgot to do a factory reset. Just go to recovery and do it.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] blaczero:
Awesome thanks, that worked
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
October 16, 2023. New Release V37.1

1. Reverted some commits to fix black screen on some Gcams

2. Wellbeing, Google (Velvet) and Google Soundpicker removed. They could be installed from Playstore

3. Kernel to 4.19.296

Download in post #3.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] mac796:
Can someone share the recovery file. Link on op not working. Thanks

Edit. Looks like I can use TWRP and not worry about it.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
I've updated the link and instructions.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] Binary Assault:
Adb-sideloaded v37.1 full on-top of 35 full (dirty) and am stuck in a crash dump loop. Appears after a few seconds of unlocking. 'Phone finishing update' doesn't complete.

Any suggestions? All flashes before this worked for me with the same process. Using Jag recovery

Reflashed v35 and can't get past boot screen

Flashed v37 and boots then crash dumps

Not related but the link for v36 is dead

Still stuck in crash dump loop. I also cleared webview data using 'adb shell pm clear com.android.webview' and that hasn't helped any

Turns out the crash dump (for me) is related to a Magisk module. Haven't been able to pinpoint which it is yet
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
All right. Next time, instead of reflashing, just boot into recovery, change slot and boot into the prior version. First of all, you'll have a functional device and second, from there you can do things.

As I've mentioned in the PM, Rikka app causes lots of errors in logcat. There are also a few selinux denials that don't exist on Oneplus 8 and 9. I'll take a look at them.

Edit: Rikka asks for 'proc' permission (access to kernel), which gets denied by Selinux. Third party apps are not allowed to have it, unless they ask for Root.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] Binary Assault:
I'm assuming Rikka might be app ops or shizuku. They both run without issue.

The crash dump comes when enabling the universal safety net fix linked below. Enabling it via magisk crashes the phone in v37, but not in v35 of Jag. It's needed to pass safety net.

GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] Binary Assault:
Additionally, I'm assuming I have some web view issues with the current release. Many apps don't work, just spinning the loading icon. Tried clearing storage of web view to no avail
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
Kdragon no longer works. There is another module available here.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] Binary Assault:
Thank you, that fixed safety net. But my web view is still not functional (can't use a handful of apps)
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
Wipe storage and cache for webview in Apps & Notifications.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] Binary Assault:
Tried that already
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
Per several users on TG: Open Magisk manager and update Magisk: pick direct install and follow prompts. This should fix webview.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] Binary Assault:
Still not working. I'll try collecting a logcat this weekend if it'll help.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
Look at a TG screenshot.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] Binary Assault:
Still no luck. Some apps are spinning on startup, others are force closing.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] Binary Assault:
Not sure what happened, but I haven't changed anything and haven't reset since the last suggestion - but some apps that were not working are now working. Not all, but some.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
November 7, 2023. New Release V38. Get ready for a long changelog:

1. November security patches

2. Android r73

3. Fixed Auto call recording

4. Fixed Edge light

5. Added Edge light layout

6. Added Edge light width

7. Added Lockscreen shortcuts

8. Fixing icon alignment in RomSettings and OneplusSettings, when an option includes adjustment bar

9. More workspaces for larger screens

10. Background opacity for hotseat in launcher

11. Smart mute (call silenced by flipping the phone).

12. Toggle to integrate some third party messenger calls into builtin Dialer

13. Fixed bluetooth battery icons on lockscreen in QS appearing black on black.

14. An option to use WP3 protocol only in Hotspot.

15. Added Presidential alerts with a toogle to disable

16. Kernel to .297 including latest SVE

17. Updated webview

Download in post #3
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] Binary Assault:
Updated to v38 without issue. No new webview issues and all the apps that previously had issues for whatever reason are functional for me. Nice work OP
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] zement:
I can’t install V38 VANILLA from scratch, either through TWRP or using ADB.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] zement:
I'll add to my post. I install recovery.img from version V38 and the phone cannot boot into recovery. I think this is the reason why I can't install V38.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
What command did you use to install recovery? Also, what stock firmware you have on the phone?
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] zement:
Good afternoon. I install OxygenOS 11.0.11.11 in both slots. I try to install recovery using

fastboot flash recovery recovery.img

, then

fastboot reboot recovery

and it doesn’t go into recovery, it just freezes. I tried installing recovery in both slots, but I still can’t boot into recovery.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
Use this recovery.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
December 6, 2023. New Release V39

1. December security patches

2. Android r74

3. Separate toggles to disable Phone and Camera shortcuts

4. Sound volume level per app

5. Camera/Microphone/Sensor toggle made into a standalone QS toggle

6. Separate 5G switch

7. Statusbar battery icons in color depending on charging level

8. Option to disable gestures in Gaming mode (when in Gestural navigation)

9. More apps added to system-wide dark mode, including SetupWizard

10. Reboot into SystemUI (soft reboot)

11. E-Tugra certificate removed

12. Kernel to .299

13. Updated webivew

Download in post #3.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
New releases with fixed recovery posted.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] zement:
Good afternoon. I would be grateful if you could implement the "Pocket detection" mode as it is done in crDroidAndroid-13.0.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
You have more than in Crdroid. Do a search for 'pocket' in Settings.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] zement:
I know that. But this mode does not work correctly. I described the problem in the following posts. Problem with "Pocket detection" mode Problem with "Pocket detection" mode.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
If you get a call on locked screen, you'll get the dialer interface, but when the conversation is over, your phone remains locked. You need to unlock it either with FP or Pin.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] zement:
Good evening. I believe that the correct operation of "Pocket detection" mode is as implemented in crDroidAndroid-13.0.

Spoiler content hidden.

I would be grateful if you implemented the same in your assemblies.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] zement:
Good evening. I installed the latest build of rom V39 VANILLA. And checked the operation of the "Pocket detection" setting. The video result is below. This is not a complaint, it's just a request to implement this setting as it was done in crDroidAndroid-13.0.

Spoiler content hidden.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
Never fully understood what you are trying to show. All 3 videos show nav buttons not responding. Only the second video appears to be on Jaguar. The other 2 - not the original AOSP dialer.

Video #2 shows the normal response. That's what the message says: when proximity sensor is covered, screen is supposed to be non-responsive.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] zement:
Indeed, this is not an AOSP dialer, I install AGContacts.

1. In this post https://xdaforums.com/t/rom-11-0_r7...december-6-2023.4342937/page-48#post-89223739 installed rom crDroidAndroid -13.0 shows that when the proximity sensor is closed, the screen is completely blocked and does not respond to touches. After the answer, the navigation buttons are fully functional.

2. In the following post https://xdaforums.com/t/rom-11-0_r7...december-6-2023.4342937/page-48#post-89260502 rom V39 VANILLA is installed . Video #1 shows that when you close the proximity sensor, the screen lights up and does not lock; after answering, the navigation buttons do not respond to touches. Video #2 should have been the first and showed that the “Pocket detection” setting is enabled, but when closing the proximity sensor, the screen is not completely blocked, and navigation buttons appear that respond to touches and perform actions. Video #3 shows the same problem as video #1.

By the way, if you use gestures instead of navigation buttons, they will also not work after an incoming call with the “Pocket detection” setting enabled.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
January 7, 2024. New Release V40

1. January 2024 security patches

2. Android r75

3. Local Update option (you can upgrade Jaguar on a live device without recovery)

4. Sim switch is back

5. Fixed Settings accent color in White mode

6. Fixed remaining few icons appearing black on black in QS

7. Fixed delay in clock alarms

8. Bluetooth sound on 9 series - addressed

9. Audio service restructured - should address voip issues in TG/WhatsApp

10. Added support for advanced extensions in Camera (should extend GCAM capabilities)

11. Seedvault backup now has its own icon in app drawer

12. Added 30 seconds automatic timeout for torch

13. Wireguard removed. Users can install as a third party app

14. Updated webview

15. Updated kernel

Download in post #3.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] zement:
Installed on pure rom V40 VANILLA. Wireless headphones do not work as a bluetooth headset. I don’t hear the call and I can’t hear the other person’s conversation.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] Freakon:
I have the same problem with V40 Full.

Music via Bluetooth works fine

Calls I don’t hear the call and I can’t hear the other person’s conversation.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
Bluetooth issue has been fixed, new release coming today. In the mean time, if you have a newer headset, you can switch to one of Qualcomm's codecs instead of AAC. It works. Switching (in Developer settings) could be done only when your headset is connected.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
Jaguary 21. New Release fixing bluetooth AAC codec issue

1. Fixed bluetooth

2. Fixed sound (after VOIP calls) going into earpiece instead of the main speaker

3. Updated webview

4. Updated kernel

Download in post #3.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] keinlelele:
STAY AWAY!

DEVELOPER DOES NOT OWN THE DEVICE TO EVEN DO SIMPLE BETA TESTING AND (soft)BRICIKED MY PHONE WITHOUT ANY ERROR ON MY SIDE!

My Oneplus 8 Pro got bricked by rebooting intro v38 recovery.

It wont boot any further than showing the pixelated image anymore. No reboot helped, cant boot into recovery or system, only fastboot works, shows that bootloader version could not be displayed anymore:

"Bootloader Version - "

Device does not get recognized from pc via usb in fastboot mode.

[EDIT:]

I was now able to do a reflash with MSM and lost all my data. Dev told me in email that he "normally tells the user that he does not have to disable the 'OEM Unlock'". Sadly he forgot that part in the email to me when i bought the key to relock the bootloader, so all my data is lost.

I will stay with lineage or stock.

Please dont forget that the warning about your ****ed up recovery should maybe be IN RED, CAPITAL LETTERS ON TOP OF FIRST POST!

I already lost data at beginning of my jaguar journey, when the "delete old files automaically after X days" was on by default...

[/EDIT]

I used jaguar v38 and magisk, nothing more that would interfere with the system. Dev told me that it could not have happened from his rom, it must be my fault. Does not even own the device to test his statement.

I will return to lineage os where every device has its own maintainer.

I use custom roms since 2014 and you, sir, produced my first brick.

I use Jaguar since v24 and i paid for relocking bootloader, what ironically might be the reason for my bricked phone xD

Please help if possible.

I still wish you the best for your project, just ask you to stick to good developing practices.

Cheers Mate
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] keinlelele:
Thx for making that public, now please also upload the email correspondence regarding the bootloader locking procedure where u forgot to tell me to keep "OEM unlock" enabled ;)

Only magisk module I installed was the safety net as well as microg...

I have some Linux knowledge myself and wold be happy to know if you at least can tell me in detail what happened when you screwed up the recovery.

I assume you are either relatively young, or from a low income country if you don't own all devices you develop for. That's nothing bad or to be ashamed of. But as I said, please stick to good developing practise, and either write automated tests to identify basic problems like that, or at least find another way to do beta testing before you release. Having the latest kernel ist not everything ;)

Cheers mate
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
'Thx for making that public'

I can see you are hurting. My heart goes out to you, but I wasn't the one screaming Stay Away..

'I assume you are from a low income country'

Lol. I am in the US.

"screw recovery'

You don't install MicroG on locked bootloader. You don't mess with system partition except for Magisk modules. I didn't screw recovery. You screwed your system partition and that's why you couldn't boot. And by the way, even if I had 8 Pro, I would have booted the device fine and would have no way to know that there was no access to recovery until the next release.

Anyway, I appreciate your input. Now, take your own advice: Move on to Lineage and Stay Away' . :)

Very best regards.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] keinlelele:
So no answer about the technical details?

And just to be clear, the phone bricked when I wanted to boot into recovery for update...

I've run v38 since around it's release without errors. Don't know how that's related to my as you say "screwed system partition".

All these magisk modules where installed since v24. All the updates since then worked flawlessly.

Also I would be interested why you should not install microg on a locked bootloader. Please pardon my lack of knowledge, your ROM was ma first with locked bootloader, so as I said please clarify the technical details.

And as if the US isn't a low income country depending on the region xP

Cheers
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
I made some changes in the device tree. There... .

Happy Lineage. Remember, try not to scream 'Stay Away' in the same post where you ask for help. :cowboy:
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] keinlelele:
Can you tell me what change to the tree you made in detail, so that I can understand the reason for the brick?

And could it be related to the disabled "OEM unlock" ;)

Remember, try to say at least "sorry" to people who's phone got screwed because you forgot to put a Textblock with some instructions into an email or to publish that information in the thread...

Cheers
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
I didn't forget anything. Temporarily enabling 'OEM unlock allowed' before update, is simply a good practice, the same way as removing your pin/password, just in case that something goes wrong. Neither is required, but you simply want to be on the safe side. If you had that toggle enabled, you could have unlocked bootloader, instead of going through MSM, but in any case, your data would have been lost.

When your bootloader is locked, any change to system partitions would result in no boot. Try to install something in System on stock rom with locked bootloader and you won't boot. That is why Magisk is included in the rom, and so are Gapps in the full version. Read about Android AVB2 protection, which is not enforced on unlocked bootloader.

As far as changes, that had to do with screen resolution.

"Try to say sorry"

I am sorry but I don't owe you an appology. There are no other 'people' who screwed their phones, and in your case, it was your own doing, i.e., installing MicroG on locked bootloader.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] keinlelele:
So then, I did not change anything since my v24 install, and booted into recovery since v24 at least for every update without problems. Micro g etc never got reinstalled, I simply installed it on v24 and since then just left it installed.

Why has this boot into recovery lead to the disappearance of the bootloader version in Fastboot, made booting into recovery being stuck after first loading of OnePlus logo where it's stuck with a pixelated full screen image that looks like TV with no signal (I get that instead of the OnePlus animation since I installed v24, just that it went away after ~2 secs and started normal), and same problem when trying to boot into system?

Cheers
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
Bootloader version is not displayed regardless of your issue. It's not displayed on my Oneplus 8 either. You simply didn't notice that before.

The pixelated image (on 8 Pro only) lasts for 2-3 seconds and does not prevent or prolong normal boot. It has to do with 'offline charging' mode, which the phone briefly enters during normal boot process. On 8 Pro, the screen gets pixelated in offline charging mode. It happens very early on boot and therefore can't be debugged.

Edit: MicroG has to be reinstalled on every update, because each update goes into inactive slot. Read about A/B slot system. If your current rom version is in slot A, the next update would go to slot B where there is no MicroG. MicroG probably has a survival script that runs on every update and reinstalls itself into the new slot.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] blair.sadewitz:
I am not a developer myself. That said, I have been using custom ROMs on Android phones for over a decade, easily, and have been using linux and UNIX-like operating systems for 30 years or so (ugh, it hurt to actually type that), and have done system/network administration professionally, etc. This is easily one of the most patronizing, disdainful posts I've encountered on this forum. If I had the money, I'd bet a considerable sum that you haven't so much as built a ROM from source before.

First off, once you unlock your bootloader, what happens to your device is solely your responsibility. Did you happen to notice any sort of warranty in the initial post? I'm pretty sure there isn't one! Even if the developer provided a flashable zip that did nothing except dd /dev/null to the whole-disk device of your emmc, no one else is responsible for that except you.

Beyond that, the scenario that you describe just isn't possible unless you did something wrong. It's not complicated. Unless you hosed your device somehow, you'd be able to boot from other slot. You can't modify protected partitions with a locked bootloader--that *is the point* of a locked bootloader. I've been using this dev's ROM for the oneplus 8 for years on and off, and it is far and away the most assiduously maintained out of any I have ever used. I happened to open this thread by accident, actually (I was looking for the instantnoodle thread), saw your post, and just had to say something. I couldn't resist.

And WTF was with that bit about the "low-income country"? Seriously? How is that even relevant? Obviously, you know it isn't. You're simply a ... nevermind. Forum rules.

You don't need "OEM unlock" enabled to use the phone. All that does it allow you to unlock it via fastboot. You don't need "OEM unlock" enabled to upgrade. But you DO need "OEM unlock" enabled if you want to flash protected partitions. This is something that it is up to YOU to know. It's YOUR DEVICE. This applies no matter which ROM you're using.

"Write automated tests"? That isn't the sort of thing that automated tests are for. You're just embarrassing yourself.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
Big New Privacy Feature is coming in the next release: Toggle to Disable Clipboard Access.

Users will able to disable access to Clipboard for all.

Google has been promising this for 10 years, but it never happened.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
February 6. New Release V41

1. February 2024 security patches

2. Android r76

3. New feature - Toggle to disable access to clipboard for all apps

4. Toggle to disable Fast/Dash charge

5. Updated kernel

6. Updated webview

Download in post #3.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] mornioas:
@optimumpro Unfortunately I am having the same issue as 'angry bob' keinlelele.

I had some troubles loading your rom zip. But after a while it sudddenly 'accepted' it. I renamed it to PE.zip.

It started working, the phone screen showed in the log it had been verified and completed. I accidentally rebooted back into recovery instead of just rebooting the phone. The top says the Jaguar version 20 or something (didn't think much of it other than ah it worked).

I then just rebooted, and I am stuck on The boot loader is unlocked... etc etc. With a pixelated top 'band'. I cannot turn off the phone, and device manager shows Unknown USB Device.

Help would be appreciated. I used a custom rom before, but used MSM to install the original rom, then again updated to get the certificate back. Then used the recovery.img in your original post (perhaps that was my mistake?).
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
With unlocked bootloader you should have no problem at all. Just flash good recovery (see OP) in fastboot.

Shutdown the phone by pressing volume up and down + power button until the screen goes black. Let the phone sit for about 20 seconds. Then restart it the same way as shutdown. Once the phone vibrates, release the buttons. Once in fastboot just flash recovery.