If that's the case, it's not full proof. But thank you, it's functional now.
To bypass it, you can simply take a screenshot then click share in some editor (I used simple gallery) and that works. But the actual screenshot isn't available after that
If that's the case, it's not full proof. But thank you, it's functional now.
This toggle is useful when you hand your phone to someone else. Clearly, they are not going to do a research on how to go around this... .If that's the case, it's not full proof. But thank you, it's functional now.
To bypass it, you can simply take a screenshot then click share in some editor (I used simple gallery) and that works. But the actual screenshot isn't available after that
That's because you don't read instructions:Did everything exactly as you said on the actual oneplus 8 pro thread this time. Same exact thing only when i install it it actually installs no problems only to reboot after factory reset into fastboot bootloop mode. seriously dont know whats wrong and i have no idea how to put android 11 in both slots prety vague about that one if u ask me.
you need to have stock Android 11 in both slots. So, either update stock OTA to populate the second slot or flash stock rom with TWRP.
Just used MSM to get back to OOS 11 Your saying i can fastboot boot twrp.img and flash another oos11 in the other slot?That's because you don't read instructions:
Read 8 pro general section: you will find a thread for all stock roms. There are several methods: you can use MSM to OOS 11 and then use TWRP to flash to the second slot. Or you can use TWRP to flash once, reboot, then back to TWRP and flash again. TWRP could be booted via fastboot or installed.
Yes. Boot, unlock bootloader, then boot TWRP in fastboot and flash OOS11. Boot again, then follow directions to install Jaguar. Use June recovery, and don't forget to do factory reset after flashing Jaguar.Just used MSM to get back to OOS 11 Your saying i can fastboot boot twrp.img and flash another oos11 in the other slot?
So i just click install on TWRP and install OOS 11 OTA again i dont have to specify which slot? Because i already used MSM for the first slotYes. Boot, unlock bootloader, then boot TWRP in fastboot and flash OOS11. Boot again, then follow directions to install Jaguar. Use June recovery, and don't forget to do factory reset after flashing Jaguar.
You don't need to flash Magisk, just install Magisk manager (rename Magisk25.2 zip into Magisk.apk) as a regular app, start it and let it finish the process.
Don't specify anything. Roms are always flashed into inactive slot, which on boot becomes the new active one. So, when you boot TWRP, it will automatically boot into your currently active slot that has OOS 11. When you flash OOS11, this time with TWRP, it will go into inactive slot, which currently doesn't have OOS11. Once you boot after flashing, your inactive slot becomes active, and you will have OOS11 in both slots.So i just click install on TWRP and install OOS 11 OTA again i dont have to specify which slot? Because i already used MSM for the first slot
Do I need safetynet fix and all like that? I probably will donate to be able to lock the bootloader at some point but for noe just want to pass device integrity and basic and force attestation to basic. Do I just need to install the usual suspects? Safteynet fix denylist, and magisk hide props? I'm kind of new but did experiment on OOS12 managed to pass safteynet, google pay and wallet worked whereas before they didn't but my Santander banking is very determined in detecting root. I think they already use the strong integrity with play api idk u prob know betterDon't specify anything. Roms are always flashed into inactive slot, which on boot becomes the new active one. So, when you boot TWRP, it will automatically boot into your currently active slot that has OOS 11. When you flash OOS11, this time with TWRP, it will go into inactive slot, which currently doesn't have OOS11. Once you boot after flashing, your inactive slot becomes active, and you will have OOS11 in both slots.
Yes, you do. There are detailed instructions in the OP.Do I need safetynet fix and all like that? I probably will donate to be able to lock the bootloader at some point but for noe just want to pass device integrity and basic and force attestation to basic. Do I just need to install the usual suspects? Safteynet fix denylist, and magisk hide props? I'm kind of new but did experiment on OOS12 managed to pass safteynet, google pay and wallet worked whereas before they didn't but my Santander banking is very determined in detecting root. I think they already use the strong integrity with play api idk u prob know better
Don't specify anything. Roms are always flashed into inactive slot, which on boot becomes the new active one. So, when you boot TWRP, it will automatically boot into your currently active slot that has OOS 11. When you flash OOS11, this time with TWRP, it will go into inactive slot, which currently doesn't have OOS11. Once you boot after flashing, your inactive slot becomes active, and you will have OOS11 in both slots.
Don't jump to conclusions. Get familiar with the rom and features. There is opacity settings, as well as raise to wake. The latter is in Settings/Display/Lockscreen/Ambient Display.Raise to wake? I can't find this optionis it in here. And some way you can add to make notification opacity inside drop down menu and also heads up ones
Yea I figured they were checking the bootloader. It led me to locking it while I was rooted. Which led to me finding out about MsM ironically... Hahaa your ROM is cool mate first ROM I installed and I think I chose a pretty good one.Yes, you do. There are detailed instructions in the OP.
By the way, it's not the root that Santander is looking, but rather bootloader status: for example I have no Gapps at all on my Oneplus 8 and with locked bootloader SantanderUS works fine without any hiding module.
No that does not work like OxygenOS12's raise to wake. My phone screen doesn't come on when I raise my phone and instantly unlock with face unlock. This is what I want to achieve. Nothing to do with always on display.Don't jump to conclusions. Get familiar with the rom and features. There is opacity settings, as well as raise to wake. The latter is in Settings/Display/Lockscreen/Ambient Display.
I also can't edit screenshots with the gallery app or Google photos. And they don't save.Don't jump to conclusions. Get familiar with the rom and features. There is opacity settings, as well as raise to wake. The latter is in Settings/Display/Lockscreen/Ambient Display.
It's not 'always on display'. In ambient display you have 'Pick up' options. If you set ambient display on, you can pick bring up on pick up or on wake. In other words, the phone will wake up when raised.No that does not work like OxygenOS12's raise to wake. My phone screen doesn't come on when I raise my phone and instantly unlock with face unlock. This is what I want to achieve. Nothing to do with always on display.
Settings/Privacy/Enable screenshot saving.I also can't edit screenshots with the gallery app or Google photos. And they don't save.
I tried these options they did not work the way i expect maybe im doing something wrong or just dont understand the way you have worded it. Im not used to custom roms or rooting android. Only jailbreaking iphone on ios 12.1.2 when unc0ver first came out for it. Jailbroke a PSP and ofcourse mod all sorts of things on PC but never an android phone.It's not 'always on display'. In ambient display you have 'Pick up' options. If you set ambient display on, you can pick bring up on pick up or on wake. In other words, the phone will wake up when raised.
Lovely ROM, lovely support. I got everything worki fine how i want it. Except notifications opacity.
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.
When it worked, enrollment was buggy, as well as screen unlocking.If that is true, why did it work all the way up to v24 then stopped in v25?
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