yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] duckjube:
As you can see in the pictures. Statusbar goes crazy after a few moments of use. This is not the only problem with the system ui. The navigation bar also changes its place. On the lock screen time,date,lock icon....After locking and unlocking everything is back in place(just for a moment). I have tried several times to install JaguarRom, as recommended, but each time the problem presented appears,so annoying. Has anyone encountered this? How to fix it? I don't want another rom!
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Ulises31:
I have found same problem in both corners in the status bar. Just time to time and fix it switching the screen off/on. Never, till now, with the navigation bar.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] duckjube:
Thanks for the message. I changed to 3 button navigation bar and the problem still occurs. Less so, but the statusbar dances from side to side, top to bottom. My eyes do not accept it....
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Ulises31:
I have not as severe issue as you. In fact, my statusbar is quite stable. No issue at all with the nav bar, I am using 3-buttons also
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] AtomCity:
Hi All,

I'm on LineageOS 20 currently, but I don't like it and hesitate to come back to A11 but before flashing this Jaguar ROM I'd like to clarify some points:

How is the battery operating time? On LOS20 it is horrible for me... Draining more than 30% in a single night.

If I'm not wrong (because of this is an A11 based ROM) the QuickSettings tiles are the regular old fashioned small icons as in the last stable OOS11?

Is there a SIM1/SIM2 toggle for mobile data in the QuickSettings as in the OOS11?

Can I set default SIM1/SIM2 settings for each contacts for mobile calls? I mean for xy contact I'm setting SIM1 by default and for yz contact I'm setting the SIM2?

MS Teams and Outlook working is mandatory, can I use them by default?

(I was not able use them on the last stock OOS11 because of the outdated version of Android Security Update, but I can use them on LOS20...)

That's all for first.

Thank you in advance!
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
April 12. New Release V-31

1. April security patches.

2. Android r66

3. Toggle to disable AGPS

4. Toggle to disable Direct Share

5. Number of users increased to 32

6. Webview to 112.x

7. No phone ID sent to servers when AGPS used

8. Shelter integrated as Work Profile Manager

9. No more statusbar icons cut off when burnin is shifting

10. No more ghost fingerprint icon.

Download in post #3.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Ulises31:
Panic settings (under settings > security) do not work, didn't work in the previous version. Just a balck screen.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
You need to have an app that is provisioned for panic button. Silence SMS, OpenKeychain and some others, then they will show up in Panic screen.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
May 7, New Release V-32

1. May security patches

2. Android r67

3. Amoled black switch (for dark mode)

4. Sometimes missing SMS fixed

5. Bionic and Art updated to latest upstream (Android 13)

6. Gray accents darkened

7. Updated webview

8. InCall UI now takes selected system-wide accents

9. Battery Bar centered.

Download in post #3.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Ulises31:
Updated. So far so good.

Thanks for keeping our old OP6 updated
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
June 7. New Release V-33

1. June security patches

2. Android r68

3. Updated webview

4. New 'about Jaguar' section

5. New system-wide accents added: total over 70

6. Forced disable AGPS toggle now disables PSDS servers too

7. Access to Radio preference in 'about phone'

8. Option for figerprint icons to take system-wide accents

9. DocumentsUI/Files now can set homescreen shortcuts for most files

Download in post #3.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] bzyzny:
Thanks for continuing to update this ROM! I noticed that Magisk has an update to version 26.1 available, according to the change log they made some significant changes. Anyone know if the update works with Jaguar?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
Should work, works fine on my Oneplus 8.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Depressed T.Bear:
Yes, it's working perfectly fine. I'm using it since release. Keep in mind: Due to the changes, the TWRP flashing is no longer fully supported. This means for us: follow the normal update procedure (with flashing magisk via TWRP). After beeing in system again, open Magisk and it will tell you that an additional installation is mandatory. When prompted, install magisk via 'direct install' , reboot and you're good to go.

So basically just another step after an update, but it shouldn't be a big deal :)
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Dukas2k23:
does this rom has game space like color os?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] bzyzny:
Thanks, can confirm this worked for me
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
July 7. New Release V-34

1. July security patches

2. Android r69

3. Updated webview

4. Option to have incoming calls to set maximum brightness

5. Allow block/unblock Conversations notifications

6. Ghost FOD appearance fixed (again) - hasn't appeared for 3 weeks

7. Updated OpenCamera

Download in post #3.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
July 16. New Release V-34.5

1. Pitch black interface by default

2. Fixed panel opacity on black

3. Ghost FOD finally fixed (code responsible for that removed).

Download in post #3.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] tqmatvey:
Hello! Thanks for working on this, but i have question

Why is the ROM running outdated kernel? latest linux kernel is currently 4.9.337, sadly EOL but still, the ROM is running 4.9.283, this is for sure considered a security hole
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
Are you on Oneplus 6? Are you on Jaguar? Or you are looking for something else?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] tqmatvey:
i am on enchilada, latest Jaguar ROM V-34.5, i am just saying that its running quite outdated kernel.

latest linux kernel that you should upstream to is currently 4.9.337

Linux 4.9.337 [LWN.net]

lwn.net
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
Can you do me a favor and post a screenshot from your phone showing the latest version and install date?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] tqmatvey:
Here, latest release, just flashed this morning, linux kernel is 4.9.283 while the latest linux 4.9 from kernel.org is 4.9.337

View attachment 5955851
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
Coming. Check kernel link again.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] tqmatvey:
you are doing it in a very bad way, squashing, with 0 authorship, even worse, you are clearly dropping and skipping a lot of stuff, taking your .313 commit, it changes

but looking at the actual linux 4.9.313 changes, i see that

I do however understand that some commits can be dropped, or maybe you picked them before, but i can take any of your upstream commits and see same results, you are clearly skipping stuff and doing it in a very bad way.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
Yeah. I suspected from the outset you were not a real rom user, but rather looking for trouble.

Apart from that, about 80% of the commits are NOT related to Oneplus 6, which is an arm64 Qualcomm device. I dropped many, because they are for different devices, mainly PCs. However, all Qualcomm related commits are there, and you know that.

Move on to another rom, if you don't like this one or pay me $5K to do it the way you want.

Best regards, pal.

P.S. For your information: GPL license does NOT require authorship.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
Locked myself out of TG group and tech support is slow. See new matrix group in the OP.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
Working Matrix link updated in the OP
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Seelbreaker:
Hey, just reactivated my oneplus 6.

I'm in RSV1.210329.026.

Can i just Download the latest full Rom.zip in the 3rd post, vor do i have to usw the update first?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
If you are on an older version of Jaguar, you can just flash the latest release straight. If not on Jaguar, then read the first time install instructions.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Seelbreaker:
Perfect, i thought that due to beeing on android 11 i have to do some special stuff, but then i just gonna update trough twrp.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
No. If you are now on Jaguar (earlier version), then you could simply flash the latest one, but if you are on OOS 11 or a custom rom based on OOS 11, then you need to first downgrade to OOS 10 in both slots, and then flash Jaguar. Again, if you are coming from another rom, read first install instructions.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
August 9, 2023. New Release V35

1. August security patches

2. Android r70

3. Updated webview

4. Updated kernel

5. Some additional connections to Google servers during testing removed

Download in post # 3.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] ZoranderEU:
Two potential issues with August release.

1. Fingerprint setting allowed 1 fingerprint, now keeps on crashing. I can authenticate but cannot change / add / remove the fingerprint.

2. Location doesn't seem to be working fully, will investigate further. Symptom: Pokemon complains about No GPS signal found.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
Fingerprint issue - confirmed and already fixed. Location - can't reproduce.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] ZoranderEU:
Regarding location: after further investigation, it was the specific app (Pokemon Pro doesn't like rooted phones), so issue no longer relevant.

Thanks!
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Depressed T.Bear:
I have a question regarding rooting our OP6 running Jaguar OS in the future.

Already a while ago, the dev(s) of Magisk informed & warned us that 'installing Magisk through custom recoveries on modern devices is no longer recommended' and this method is now considered 'deprecated and maintained with minimum effort' [source].

Up to now, the installation via the recovery still works. Kind of, at least. After flashing Magisk via recovery, a subsequent 'completing' installation via the Magisk Manager in the running system is now mandatory (Magisk v26.x+).

With the latest releases (starting with Magisk v26.2), a function has been added to automatically extract and patch (pre-root) the boot image from a given payload.bin, to flash it directly via recovery or fastboot (which is the recommended installation of Magisk nowadays) [source].

Now this makes it very easy for us to create a pre-rooted boot image of future Jaguar releases on our own.

My question is now mainly directed at @optimumpro : What is the correct installation procedure for rom updates with a pre-rooted boot image?

To my knowledge, it should be as follows:

Reboot to TWRP

Flash the latest Jaguar

Flash TWRP installer

Reboot to recovery

opt.: Flash latest GAPS

Flash pre-rooted boot.img to boot slot

reboot to system

Admittedly, my knowledge about partitions and TWRP installation is very outdated. As far as I remember, TWRP was installed in the recovery partition back in the days, not altering the boot partition.

So my concern is that flashing the patched boot.img as the last step would overwrite TWRP - because after flashing TWRP installer, it normally states that 'you are unrooted now'.

I'd be very happy about any further information about this!

Cheers

EDIT:

I found additional information.

'the stock recovery has to be replaced with a custom recovery, inside the boot partition where the kernel lives. But on Android, you cannot modify partitions through fastboot – you can only flash over them. [...] With recovery and these other custom mods now all living together in the same partition, it is possible for one of them to overwrite files used by another mod. This is why you may need to reflash magisk after updating a custom kernel or custom recovery' [source]

So this basically answers my first question(s). So I guess we have no choice but to hope that flashing Magisk via recovery will keep working in the future? :(
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
You don't need any of that. You can upgrade from Magisk 26.1 to 26.3 within the app. Pick direct install and you are done. I' did it on my Oneplus 6. I am sure flashing 26.3 with TWRP directly would work too (haven't tried though).
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
September 9. New Release V36

1. September security patches

2. Android r71

3. Updated webview

4. Add icons to Settings in keyboard

5. Toggle to have system emoji icon permanently in keyboard

6. Add support for new VVC codec

Download in post #3.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Depressed T.Bear:
Hi, thank you for your answer.

It seems you didn't quite understand where I was coming from. I am aware that I can easily upgrade via the app. That's how I'm used to doing it :)

My point is the installation of Magisk after an update of Jaguar OS via TWRP. But it seems that there is no way to flash a Magisk-patched (pre-rooted) boot.img without losing TWRP. Therefore, we will probably have to continue flashing Magisk via TWRP as long as it will still be possible.

Or is there any other way to patch a given boot.img in advance with TWRP and Magisk?

BTW: Thanks for the latest release and the ongoing support for our OP6! <3
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
After an update, flash twrp installer, reboot in twrp and flash Magisk.

Also, patched image could be easily flashed within twrp. You are not going to lose twrp, if you flash twrp installer as the last step, as twrp installer doesn't touch Magisk changes.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Depressed T.Bear:
>>> twrp installer doesn't touch Magisk changes

That's an interesting information! So it makes totally sense what you said, since I haven't updated to Jaguar V36, I'll give it a try later with the patched boot image. If it works out as intended, it's a good way to do it if flashing the Magisk zip stops working in the future.

Thank you very much, really appreciate your help and knowledge!
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Depressed T.Bear:
Followup Update:

Flashing the patched boot image and TWRP after that did

not

work - resulted in losing root.

My procedure was:

Spoiler content hidden.

I gave it a second try, rebooted to recovery again, flashed patched boot image + TWRP and rebooted system. Without success.

So I followed the 'normal' procedure

Spoiler content hidden.

which brought me back to the updated, fully working Jaguar.

I don't know what went wrong, I'll stick to the 'normal' procedure as long as possible.

However, I noticed on my regular check after an update that my Play Store became uncertified and Safetynet checks fail. After some troubleshooting, I found further information on XDA. It looks like Google did some work and kdrag0n's Universal SafetyNet Fix module became outdated/obsolete.

The currently best (and working!) way, is to remove/disable Didgeridoohan's MagiskHide Props Config (which is deprecated) and flash chiteroman's Play Integrity Fix via Magisk Manager! It's especially recommended for OnePlus devices over Displax's Universal SafetyNet Fix [MOD].

Play Integrity Fix automatically removes kdrag0n's Universal SafetyNet Fix module after flashing, and works perfectly fine together with Shamiko.

I'm passing SafetyNet again, along with having a certified Google Play Store.

I provide this information just in case, someone else faces this issue.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Ulises31:
I Haven't had any issue to flash magisk. After updating I flash TWRP again and then Magisk, I think was v25.2, from TWRP without patching boot.img. After rebooting and opening Magisk app, the app was updated to 26.3. And it was unnecessary to flash safetynet fix. No problem at all with my banking app nor Play store.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Depressed T.Bear:
I neither have issues flashing Magisk. It's about flashing a pre-rooted boot image! Flashing the Magisk zip still works for now.

So that's very interesting. You didn't flash any Play integrity fix and your Play Store still shows that your device is certified under settings?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Ulises31:
Yes, indeed, that's right. I have only two Magisk modules installed: ACC and Pixelify. Google Play Store and banking app work fine doing nothing.

However, this ROM doesn't emulate Google Pixel phone as other ROM do. So I guess unlimited storage in Google Photos is not allowed.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Depressed T.Bear:
There you have it. Pixelify also spoofs your device information to make it look like a "normal" Pixel phone to get its benefits. Similar to what Magisk Hide Props did, which explains everything.

To get the unlimited Google Photos, you need to configure Pixelify to mimic a Pixel XL. There should also be 'Pixelify Sub Modules' for that, I couldn't find any though.

I'd also rather not support you in this regard here, since this thread is dedicated to Jaguar and I would never, under any circumstances, support or advise uploading data into any cloud without proper encryption done by yourself.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Ulises31:
I was refering to a kind of switch to emulate a Pixel XL as other ROMs have, just this. It`s not a problem for me.

On the other hand, I am not very sure to have understood what you mean with "...support me... uploading data into any cloud without proper encryption done by yourself"
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Depressed T.Bear:
I just want to raise some more attention to what you upload. And especially if you do it encrypted or not.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
Settings/Accessibility/Unlimited backup for photos.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Ulises31:
Done it! Thank so much
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
October 6, 2023. New Release V37

1. October security patches

2. Android r72

3. Updated webview

4. Webp vulnerability CVE-2023-5217 fixed in native code and webview - NOT fixed by Google yet

5. New offline charging animation with percentages

6. Launcher: option to manually restart

After booting wipe cache/data for Webview

Download in post #3.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Depressed T.Bear:
Thank you for the update and your ongoing support. The update went smoothly as always and the new charging animation looks very good (y)
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Ulises31:
Updated and everything is working fine so far.

Thank so much for maintaining our old OP6.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
October 17, 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

Download in post #3.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Candiety:
Thanks again.

P.s the new mega uploads are blocked on mobile, without premium or the app. Switching to desktop mode (surprisingly) fixes it. Little tip for everyone.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Depressed T.Bear:
I'm still on V37, update is however loading.

I found a concerning bug today when I wanted to show a friend of mine the secured (blocked) power menu access while the device is locked.

Reboot etc. are successfully blocked until the device is unlocked. However, 'shut down' works immediately and without unlocking the device 😱

Hopefully you can reproduce and fix it, otherwise I'll provide logs for your as soon as I am back from holidays.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
The feature prevents showing of the menu and it works, but It does not affect forced shutdown (volume + power button), which is hardware based.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Depressed T.Bear:
Yes, the 'Power Button Security' option prevents showing the power menu perfectly fine if toggled off.

I'm referring however to the option 'secure power menu', right below the first one.

View attachment 6025012

This option should ask for my pin to execute a reboot, power off, etc.

It's working fine for reboots (asks for pin), but it doesn't if I select shut down.

Can you confirm that it's asking for an authentication (pin) before it executes the shut down on your device? Otherwise I'll provide you with logs as soon as I'm back home.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
Deleted
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
This is an on lockscreen feature only, never intended for unlocked device. If you want no access to power menu on locked device, disable both power menu and power button and it would work the same way as access to QS and Statusbar.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Depressed T.Bear:
Maybe it's because English is not my first language. I'll try to put it very clearly again.

I know that it is a "lockscreen-only" feature - I also mean all the time that the problem occurs while in the lockscreen (hence the potential security risk).

Here's exactly how you might be able to reproduce the issue:

1. Set the two settings like in the previous screenshot

2. Lock the device → wake it without unlocking - we are now in the lockscreen (!)

3. Hold the powerbutton until the power menu appears

4. Select reboot (choose an option) ---> you need to enter the pin before execution (exactly what we want!)

5. Select shut down ---> device immediately shuts down ----> no need to enter pin before execution! Something what we absolutely don't want and shouldn't happen.

It should ask as intended, just like with the reboot option, for an authentication before performing the shut-down.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
Your English is fine.

In my view, the true security is when Power Menu does not appear at all on locked screen. This way you always need to authenticate first.

What's the point of asking for a pin to shut down, when anyone can force shut down the phone with Volume and Power buttons? There is no point to ask for a pin on reboot either, i.e. force shut down and then reboot.

I understand what you are saying, but this AOSP feature (not very useful in the first place) becomes redundant, once you have the option to prevent Power Menu from appearing on lockscreen.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Depressed T.Bear:
I totally agree with you, a non-appearing power menu gives the most security.

Personally, I still like to access the power menu for two reasons: a) I can use the "lock" tile to force a pin authentication instead of f.e. fingerprint (useful in some situations!) and b) to toggle OTG before fully unlocking the phone. I admit, the latter is just a habit - could easily be done from the quick settings as well.

Also, not every thief / intruder knows about the key combo for the force shutdown with the volume rockers.

Moreover, I'm pretty sure it was working in the past. After I found this feature in your ROM and confirmed it's working, I stopped using Cerberus Anti Theft, which also had the same functionality.