Hello. So I finally got around to trying your ROM.
I made the install directions about as clear as I possibly can. This was the way I did it and it worked the first time without issue. I don't use Google crap so I can't help you there other than to suggest Aurora Store.So I just flashed the rom and before I say anything, shout out to @optimumpro for making a NOT ****ty rom WITHOUT Google crap.
I just wanted to help with the install directions. I found a way to avoid some of the pain of installing this rom. 2 parts that made the install a breeze especially if you're using the T-mobile branded device.
1) Use whatever oneclick solution (MSM) you use to get to stock. Unlock bootloader. Reboot to fastboot and "fastboot boot twrp.img" Then sideload this It'll copy the partition for you without any added headache. Now you have A11 on both slots. Reboot and flash the boot.img file from the OP. Then install the rom
2) After the rom is installed, i installed the magisk apk. Afterwards, reboot to fastboot and simply boot the TWRP image. Not install it. So "fastboot boot twrp.img" again. Then flash the same magisk apk from within TWRP. Reboot to system and that's it. No data loss no problem. Everything works great!
The rom in of itself has nothing to do with the issue. It's the browser you are using. If you are using firefox types or chrome variety, it is possible that some default settings in 'about:config (firefox)' or 'chrome://flags' prevent loading of pages with invalid SSL certificate.I've been using Jaguar for about a month now and really enjoy it as a daily driver.
I am having an issue though when it comes to SSL and certain sites. Newpipe, for example, throws a 'Javax.net.ssl.SSLHandShakeException' error. In browsers half the websites I try to access throw a 'NET::ERR_CERT_AUTHORITY_INVALID' error and won't load at all.
Is anyone else having this issue or know how to fix this? I've tried the typical fixes suggested online like setting automatic time, wiping caches, etc without any success.
Thanks for the info, man. I tried the debug version and had the same issue as I did with v23.1.Upon further investigation, I can reproduce the issue you have with Firefox if I want. All I had to do was connect to a vpn. This isn't an issue with the rom. It's an issue with the ****ty companies that don't want you on their website if they can't track everything about you.
Ah, that's how the props aspect works. Thanks for clearing that up. I hadn't played with it beyond the rough setup.As I said earlier, I don't f**k with Google at all so safety net is of no concern to me. However, this can be easily managed using props config within magisk. Pick whatever fingerprint you want and it'll work. I tested it before with the Pixel fingerprint and it worked great. It'll walk you through the specific commands by asking you to select an option rather than enter the commands manually.
Weird that the debug version didn't fix your new pipe. It was a reported bug numerous times on GitHub and once I used the fix, it completely fixed my issue. Glad you got it worked out though
MagiskHidePropsConf. Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.github.com
fastboot flash boot_a boot.img fastboot flash boot_b boot.img
You don't install Android 9, 10 Gapps on Android 11. You also need to flash Gapps before the first boot into system, i.e, flash the rom, reboot in recovery and flash Gapps.