Good afternoon. I want to finally switch from Android 9 to Android 12L. Making moral and technical preparations
These vendor images include the avc hardware decoder if you want it.
I know that YouTube on Android 9 without a vendor image doesn't pull above 720p. I was wondering if that would solve the problem. But, thanks anyway.
A9 doesn't use a vendor image .
Make a backup from the original vendor image in TWRP for example, or simply reflash the ROM,
- Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
- Open Magisk and update the App (and do a reboot if it's asking)
- Enable Zygisk in Magisk
- Download and install microG installer in the Magisk manager, reboot
- Download and install safetynet-fix in the Magisk manager, reboot
- Check with a safetynet checker app and you should pass
Not really, zram should be limited because it consumes many resources of the CPU,
Hi, guys! Confirming, have the same bug. N8000, 64gb, EN/RU language. Version 20220405 works fine, but in 20220506 and later versions AOSP keyboard doesn't work correctly. First time seen with clear upgrading from someone old LOS, may be 16. Then tried clean install after full hardware reset or install 20220405 with on air upgrade later - result is the same. Tried many actions in input settings, but can't find any repeatable successful result. For example, once helped manual theme changing in AOSP keyboard settings, but a few minutes later problem returned and never cleared again when trying the same actions.Hi, i need help. I am just flashed latest version (20220506) on my gt-n8000 from stock firmware. Everything for now working fine except one thing. Every time when i trying to use keyboard (onscreen) almost all screen covered by black element. I can uncheck in settings displayed onscreen keyboard and now nothing happen at all. This seems like he try to use hardware keyboard but i do not have one. Also in notification link to setting hardware keyboard.
Html6405, yes. first try I made clean install like recommended in "Instructions" on 1st page of this thread, also applying "Swipe to Factory Reset" during procedure because there was installing fresh TWRP also. May be problem affilated with some localization?
Ok that's really crazy, I try to find out what could be the cause, on my clean installation I'm not facing any problems, but I had the same thing once after a dirty upgrade.Html6405, yes. first try I made clean install like recommended in "Instructions" on 1st page of this thread, also applying "Swipe to Factory Reset" during procedure because there was installing fresh TWRP also. May be problem affilated with some localization?
Yesterday I tried a "dirty" flashing experiment: manual downgrade through TWRP from last version to 20220405 without clearing cashes and so on, and it solve problem. But when repeat upgrade to last version on air - problem returns.
Temporarily installed and switched to Gboard application, like others.
You could downgrade to the previous version, download gboard and re-upgrade (or wait) for example.
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. * */
Searching 30 seconds for you: