Idk what this talk about other ROMs has to do with mine, but the latest update should pass safetynet regardless.
Last edited:
Not really I just turned night light off and added them again (on ~45% brightness also). I tried adding the same finger twice before but at least in my case it makes it a bit worse and sometimes reports that my finger moved.Thank you for the quick response. Did you do anything special? Like rebooting the device after deleting the existing fp and then added the new fp or like adding the same finger multiple time with different brightness etc. On K20 pro Telegram channel, a lot of people suggest a lot of different tricks and hacks. Some say, if you are planning to delete and re-register the fingers again, restart the device once after deleting the existing fingerprints, some say register the same thumb twice (one with the lowest brightness and one with highest brightness) and lot of different weird hacks. Did you follow any of them?
I don't think it requires Magisk, there's some other reason why it doesn't work. Which recovery are you using?Can we fix "Install" not rebooting in the system update menu once update has been downloaded? I'm not rooted, probably because of this it doesn't work?
Can we fix "Install" not rebooting in the system update menu once update has been downloaded? I'm not rooted, probably because of this it doesn't work?
Is your problem solved by the 12/01 release?Bug: Location history (aka Google Maps timeline) does not work with Evo 5.2/5.3. It records nothing.
I reported this earlier but now I have clean flashed Evo 5.3 again with no restore from Google Drive backup.
Everything is configured correctly, but it does not record location visits.
No. I cleared data of Google app and Maps after flashing the newest version but location history does not work.Is your problem solved by the 12/01 release?
Hide magisk manager, magisk hide pubg, delete/rename twrp folder if it exists in internal storage.Pubg crashes on the recent update... No matter what I do it crashes after a minute or two... I checked everything ... Anyone with similar issues ? PS the ROM is amazing thanks for the magnificent work.
Try wipe -> format Data "yes"
It would be nice to keep it private and share it only with users who ask for it as respect for Evolution X's code of conduct.Since EvoX supports signature spoofing I've managed to make microg work with it.
Is it allowed to rebuild the zip without gapps and upload it here for you guys (and future updates)? Of course with a note that this is not intended by the author and one should refrain from posting bug reports using these. It'd allow people who use microg to update their rom without overwriting mandatory gapps like play store and gms. Since it's my daily driver I'd - if it's allowed - share the rebuilt zip with each update posted.
Great job for the new update! It's blazing fast and I feel (maybe placebo but either way) like the FOD is way faster after updating! Also it feels more fluid though this could also be placebo. Awesome!
@stou36: EvoX uses LOSFOD. If you want support for custom kernel you'd post in their thread. Though they have a lot reports that the most recent kernel is not stable, so I highly suggest you to not use that and better stick with the stock EvoX kernel (Englezos does work fine on EvoX, too)