It gets installed with the latest update. Plus, Magisk is included, so, you just boot.
It gets installed with the latest update. Plus, Magisk is included, so, you just boot.
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.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?
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)?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.
Magisk modules should be installed within Magisk manager.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)?
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.
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.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.
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.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 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.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.
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:All roms using kernel from 2 years ago, no one really bothers to update this ever, not if its lack of knowledge or laziness.
Yup, it's configurable tooGood 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.Good afternoon. Is it possible to add an ambient display clock setting?
I wrote about setting the clock itself in size, font and shape.If you mean scheduling AOD, it is there. If you mean 'burn' protection, i.e., shifting is not.
AOD brings your currently selected clock, which could be configured including color. You can also pick out of many clock designs in launcher.I wrote about setting the clock itself in size, font and shape.
This is why I drive a Honda CRV, because its safe and reliable like Jaguar!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.
A thing I miss is to have the fingerprint directly ready in the Always-on DisplayA 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).
I think it is trying to shift icons to prevent burnins, but due to various margins and camera cutout or if you have too many icons, it just doesn't look good.
Is there something I need to re-enable to get FOD with AOD functional again? Stopped working in v25.January 4. New release V-28
1. January security patches
2. Android r63
3. Kernel to .269
4. Bionic ported from Android 13
5. Smart pixels removed (poorly implemented and unfixable)
6. Trustcor certificates removed
7. DIsplay color modes should be fixed
Download in post #3.
Lol take it easy man, he's just sharing a ROM, theres no obligation here.Dev should really consider dropping support for 8 pro. Clearly just because his device doesn't have the issue he thinks everyone's device should be the same.
Two people have mentioned the same issues and instead of fixing it he's showing screenshots. DFKM.
I'M DONE