[ROM][11.0_r63]JAGUAR ONEPLUS 8 PRO OFFICIAL V28 Updated January 4, 2023

[optimumpro]

Where is the link for the new recovery?

It gets installed with the latest update. Plus, Magisk is included, so, you just boot.

 

[optimumpro]

While troubleshooting I accidentally disabled a package that casued a boot loop. I ended up having to complelety wipe the device and start over.

Good news is, no more permission issues. Still don't know the root cause.

Oddly though, with twrp, nothing I did stuck. The file, on system partition, that I needed to modify would revert on reboot. Any files I transfered disappeared on reboot. Any idea why? Basically twrp acted like I never did anything after a reboot. Because of that I had to delete data and start over (using jag recovery). Which makes twrp completely useless.


Edit -just saw you figured out the permissions issue, awesome!

Any chance for AOD fingerprint to
cont back?

System: that's because Magisk is installed with 'enable verity' flag, which means nothing could be changed in system partition except through Magisk, which actually does not change system, but rather makes system believe that Magisk layer is a part of System. So, whatever changes you make to System partition directly, will be reverted on reboot.

 

[Binary Assault]

System: that's because Magisk is installed with 'enable verity' flag, which means nothing could be changed in system partition except through Magisk, which actually does not change system, but rather makes system believe that Magisk layer is a part of System. So, whatever changes you make to System partition directly, will be reverted on reboot.

I know its off topic, but with enable verify, would I be able to make and flash a Magisk module in TWRP to solve my problem (needed to update a permission in a config file on the system partition)?

 

[optimumpro]

I know its off topic, but with enable verify, would I be able to make and flash a Magisk module in TWRP to solve my problem (needed to update a permission in a config file on the system partition)?

Magisk modules should be installed within Magisk manager.

Which permission you wanted to change/add?

 

[optimumpro]

Several points about kernel updating and security:

For some reason, most custom rom kernels, including Lineage kernels, haven't been updated for almost 2 years. Although, Google security patches for AOSP are regularly merged, not so with kernels. Here is just one example. Lineage's latest kernel for Oneplus 8 series (whether A11, A12 or A13), all stopped being updated from upstream at 4.19.157. The current upstream code is at 4.19.261. Again, that's 2020 and we are almost in 2023. These are literally thousands of commits many including various fixes for 'overflows' and 'leaks', which constitute 'back doors' for exploitation. They are as important, if not more, than AOSP security patches.

To find out kernel update level, look into Makefile at the top. For Example:

Here is Oneplus 8 Lineage's kernel Makefile. It says 4.19.157. The last update (to .157) was merged in November 2020, two years ago. The same is true with other kernels, see the infamous Blue_Spark kernel: also 4.19.157... . Think Oneplus stock kernel is any different? Think again: also 4.19.157. Here is GrapheneOS 4.19 kernel: 4.19.239 - much better than the above, but still behind the curve.

To contrast, look at the current upstream kernel (same 4.19.x version), which is at 4.19.261 as of October 5, 2022, and this is Jaguar kernel, also 4.19.261 as of October 6, 2022.

This is not in any way to criticize other developments: we all do what we do according to our choices and time constraints.

 

[xtcislove]

Several points about kernel updating and security:

For some reason, most custom rom kernels, including Lineage kernels, haven't been updated for almost 2 years. Although, Google security patches for AOSP are regularly merged, not so with kernels. Here is just one example. Lineage's latest kernel for Oneplus 8 series (whether A11, A12 or A13, all stopped being updated from upstream at 4.19.157. The current upstream code is at 4.19.261. Again, that's 2020 and we are almost in 2023. These are literally thousands of commits many including various fixes for 'overflows' and 'leaks', which constitute 'back doors' for exploitation. They are as important, if not more, than AOSP security patches.

To find out kernel update level, look into Makefile at the top. For Example:

Here is Oneplus 8 Lineage's kernel Makefile. It says 4.19.157. The last update (to .157) was merged in November 2020, two years ago.

Here is the current upstream kernel (same 4.19.x version), which is at 4.19.261 dated October 5, 2022.

Here is Jaguar kernel, also 4.19.261 dated October 6, 2022.

This is not in any way to criticize other developments: we all do what we do according to our choices and time constraints.

That is nice to know thank you. Can you think of a reason of not updating the kernel? For my understanding, if i have the latest security updates but my kernel is exploitable, security updates are not a good argument anymore.

 

[optimumpro]

That is nice to know thank you. Can you think of a reason of not updating the kernel? For my understanding, if i have the latest security updates but my kernel is exploitable, security updates are not a good argument anymore.

I don't know for sure, but generally, unlike the Linux community, Android one primarily focuses on the looks, i.e., monet, accents, animations and features. Security is of no particular concern. After all, most custom roms run only on unlocked bootloaders, where many security features are disabled.

Why is that? Linux developers are adults.

 

[xtcislove]

I don't know for sure, but generally, unlike Linux community, Android one primarily focuses on the looks, i.e., monet, accents, animations and features. Security is of no particular concern. After all, most custom roms run only on unlocked bootloaders, where many security features are disabled.

Why is that? Linux developers are adults.

You made some good points. I run on unlocked bootloaders etc. since android is a thing, i dont use anything than Windows Defender on my PC and i never had any security issue, because i know what i do. Same clearly goes for the majority of root users. Leaving quality aside apple does a good job for most people. In a closed down system you dont need to know anything to be secured.

 

[optimumpro]

You made some good points. I run on unlocked bootloaders etc. since android is a thing, i dont use anything than Windows Defender on my PC and i never had any security issue, because i know what i do. Same clearly goes for the majority of root users. Leaving quality aside apple does a good job for most people. In a closed down system you dont need to know anything to be secured.

You may know what you are doing, but what if your phone gets in someone else's hands whether by accident or force? If your system isn't locked, it is exposed to all kinds of trouble.

 

[afonsohenri17]

All roms using kernel from 2 years ago, no one really bothers to update this ever, not if its lack of knowledge or laziness.

 

[optimumpro]

All roms using kernel from 2 years ago, no one really bothers to update this ever, not if its lack of knowledge or laziness.

I have never said it was the lack of knowledge or laziness. It's a matter of priorities. Folks just have no clue about security and privacy. That's why they don't bother. And by the way, this is not kernels only, the whole concept of custom roms for Android is devoid of security:

1. Most roms, Lineage included, are user-debug where security is several layers below user builds. In fact, even Google says user-debug builds are for developers only, security is mostly disabled to make the process of bug discovery easier. Google says user-debugs are not fit for production.

2. Unlocked bootloader: nothing is being enforced at all. In addition, and comically enough, Lineage also disables avb and verity in kernel on unlocked bootloader, where neither can be enforced. Do they have a clue?

In my view, if you have no clue about privacy and security, you shouldn't be developing software.

P.S. Magisk also disables verity. My kernel for 8 series is not just prepatched on the phone and then included as prebuilt in the rom zip. This would have broken avb and the ability to lock bootloader. Rom script and Magisk scripts are modified so that Magisk could run during the build and before the final signing. It actually runs right after boot.img is built, and scripts apply 'keep verity' (see attached screenshot from my build Box terminal). So, when you flash the rom, there is no flashing Magisk. You just install Magisk manager, as a regular app, and let it finish setup.

 

[zement]

Good afternoon. Is it possible to add an ambient display clock setting?

 

[Binary Assault]

Good afternoon. Is it possible to add an ambient display clock setting?

Yup, it's configurable too

 

[optimumpro]

Good afternoon. Is it possible to add an ambient display clock setting?

If you mean scheduling AOD, it is there. If you mean 'burn' protection, i.e., shifting is not.

 

[zement]

If you mean scheduling AOD, it is there. If you mean 'burn' protection, i.e., shifting is not.

I wrote about setting the clock itself in size, font and shape.

 

[optimumpro]

I wrote about setting the clock itself in size, font and shape.

AOD brings your currently selected clock, which could be configured including color. You can also pick out of many clock designs in launcher.

 

[woonaval]

Just to provide my feedback about this ROM. I'm really surprised how well everything works in general in comparison with other OnePlus 8 Pro ROMs. I can keep this one as a daily driver whitout worrying about a random crash or restart, which is great. I even relocked the bootloader with the donation option and now I feel quite safe
I'm happy that fingerprint unlock works very well, and camera photo quality is very good. I configured Magisk correctly and installed the required modules and now all my bank/corporate apps are working perfectly.
Even if it's close to perfection, it also has some issues I would like to point out:
Battery drain: In comparison with stock rom, battery drains much faster. Previously I could end my day with around 50-60 of battery left. With optimus I need to be careful and at the end of the day maybe I have 20-30 left. Knowing this I charge the battery more often. I don't know if this is expected, or maybe I have some misconfiguration or something.
Brightness: ROM's default screen brightness seems too high for me, I find myself lowering it very often and seems like my new values don't get stuck every time.
Camera: of course this is not the ROM's fault or anything, but camera stability and features are not at the same level as with OP camera. I installed a gcam which has lots of features and it's great (LMC v14), but sometimes it acts strange. I will try to use the default Open Camera to see if at least I get full stability. Maybe OP camera could be integrated somehow in this ROM, as it's in others?

A thing I miss is to have the fingerprint directly ready in the Always-on Display as it is with stock rom. In Jaguar I need to doubletap to enable the lockscreen and then fingerprint unlock. Also about AOD, having "burn protection" would be great (right now the date/time are static at the same place).

Even with these things I mentioned, the ROM is great and I will keep it for a long time. Thanks a lot optimumpro for your great work!

 

[JedidroidX]

Several points about kernel updating and security:

For some reason, most custom rom kernels, including Lineage kernels, haven't been updated for almost 2 years. Although, Google security patches for AOSP are regularly merged, not so with kernels. Here is just one example. Lineage's latest kernel for Oneplus 8 series (whether A11, A12 or A13), all stopped being updated from upstream at 4.19.157. The current upstream code is at 4.19.261. Again, that's 2020 and we are almost in 2023. These are literally thousands of commits many including various fixes for 'overflows' and 'leaks', which constitute 'back doors' for exploitation. They are as important, if not more, than AOSP security patches.

To find out kernel update level, look into Makefile at the top. For Example:

Here is Oneplus 8 Lineage's kernel Makefile. It says 4.19.157. The last update (to .157) was merged in November 2020, two years ago. The same is true with other kernels, see the infamous Blue_Spark kernel: also 4.19.157... . Think Oneplus stock kernel is any different? Think again: also 4.19.157. Here is GrapheneOS 4.19 kernel: 4.19.239 - much better than the above, but still behind the curve.

To contrast, look at the current upstream kernel (same 4.19.x version), which is at 4.19.261 as of October 5, 2022, and this is Jaguar kernel, also 4.19.261 as of October 6, 2022.

This is not in any way to criticize other developments: we all do what we do according to our choices and time constraints.

This is why I drive a Honda CRV, because its safe and reliable like Jaguar!

Thank you Optimumpro for your dedication to this spectacular rom!

Just one question, is Android 12 in your sights eventually or maybe skipping 12 and going to 13? Sorry, I had to ask as I know other users must be wondering the same. And thank you again for everything!

 

[DuronHD]

Hi I love this rom, but like in @woonaval case battery is the issue but more drastically. Its constantly draining and throught night battery drops from 100% to 64%.

Is it possible to find source of draining? may by some app or in some logs?

I think that it must be cause by some setting or app, bcs after clean flash without any app it lost 1% battery per night.

Second what it bothers me is not working auto brightness or if it working it is set to high.

I'll be glad for any tips guys!

 

[optimumpro]

A thing I miss is to have the fingerprint directly ready in the Always-on Display as it is with stock rom. In Jaguar I need to doubletap to enable the lockscreen and then fingerprint unlock. Also about AOD, having "burn protection" would be great (right now the date/time are static at the same place).

A thing I miss is to have the fingerprint directly ready in the Always-on Display

You can have it regardless of AOD. Just go to Settings/Display/Lockscreen/Ambient display and enable 'pick up'. This way, each time you pick up the phone, you'll have lockscreen with fingerprint ready.