Is the app crashing and Google Chrome website loading bug when multiple apps open in the background when you have root fixed in the latest update?
I tried adding this just days ago, the UI and toggles were there but it didn't isolate/restrict any apps.Is it possible to have an inbuilt firewall like LOS/CalyxOS
Pull request for calyxOS Git
Ohh, thanks for giving it a shotI tried adding this just days ago, the UI and toggles were there but it didn't isolate/restrict any apps.
This was already solved in a previous update. I'll suggest a data format.Because of the new version, I did a complete fresh reinstallation.
but now there is a problem, I have two sim cards with pin, after reboot, the password input keyboard will not show, the screen repeatedly turned off and on, and phone will auto reboot into recovery, so I must eject the card slot before reboot, after system boot finish then insert so I can enter the pin normally.
The previous version did not have this problem.
No clue. Try the older version of TWRP to backup.My problem is:
Evolution X version 2022-11-14. Bootloop after OTA. Flashed again version 2022-11-14, working OK. Unfortunately I cannot make backup from TWRP (3.7.0_9-0 official, to USB OTG), it stops with an error "createTarFork() process ended with ERROR: 255", log attached. Searching Internet I have found about this error associated with using different users / work profiles, but I don't use such things.
Any help will be appreciated
Been posted numerous times in the thread.I want to clean install the latest
Evolution X [11/27/22]
where is the DFE file to download ?
thanks
Works fine here and I'm guessing for everyone else as well. Make sure Smart Pixels is off.For some reason fingerprint reader stopped working. It was working all day after update but now the bright light from under the screen doesn't light up. Re flashed but problem persists. Anyone else have this issue? Or could it be a hardware problem?
As I said, that shouldn't be an issue as it was resolved already and nothing related to that bug has been brought back.I just flashed the new build via ADB sideload, being encrypted and with official TWRP and my phone can't enter into system, it reboots into recovery. It's the first time this happened. I had to format data to make it work.
EDIT: After a reboot, I had that sim pin flicker thing that happened some builds ago. I think I would go back to 14th build
Been crashing since Android 13 came out.
You need to FORMAT DATA. Which means you have to backup your internal storage somewhere else first, format data, then it'll boot.I'm sorry if this is a repeat problem, but I'm stupid. I am encrypted and used OTA to update to latest version. I got the bootloop and found out that I needed to update recovery. Now I am at TWRP 3.7.0_9-0 and the system still won't boot. What am I doing wrong?
You need to FORMAT DATA. Which means you have to backup your internal storage somewhere else first, format data, then it'll boot.
Just a small update as well. Lag has been removed from Saturated color profile users. Kernel has also been updated along with the OTA Rest is the same, data format is required if it still bootloops for you. Backup now before updating. Use the latest official recovery or stick with Evo recovery.
Use unofficial ofox to decrypt temporarily then. Or use DFE.How do I backup if recovery is encrypted? Thanks for the quick answer btw
How would I go about this first option?
This was already solved in a previous update. I'll suggest a data format.
As a little fix and to avoid ejecting the card slot, there's an option to disable the sim pin in the settingsNo way. Problem came back. Tried clean flash and many data formats before, after and between.
You should just ignore them, you'll always have people like that. In terms of the ROM performance, I have to say it's amazing, battery life is much better, no lag whatsoever or anything I personally had any issues with, along with plenty of features. Only issue I had was encrypted storage, which was easily fixed and not related to the ROM itself.I'll be taking a break from reading this thread until the next security patches (probably next week). All these new users just wanna nitpick on inclusions and additional features while others just can't seem to understand the concept of encryption and rooting.
These new replies are full of convoluted information and issues that aren't even experienced by the community as a whole and I'm not gonna waste more time reading everything.
No more requests and no more "can this be done" or "can I do this instead?". Either use the ROM as is or move to another.
02-01 09:27:19.839 E/WifiScoringParams(1604): Invalid frequency(-1), using 5G as default rssi array.Hello @joeyhuab,
can you be so kind to help me? Since Android 13 release I cannot connect to work WiFi (802.1x security - self signed certificate - PEAP MSCHAPV2 - Radius login). I was blaming my dirty flash from EvoX Android 12.
Yesterday, I clean flashed latest build (01/25/23) from scratch, but I'm still having the same problem. After inserting the credentials (identity & password) and setting to accept the certificate at first use the WiFi start "Connecting" but wont connect and the status go to "Saved", then it loops between "Connecting" and "Saved" without ever connecting to the wifi.
I was expecting a popup asking me to accept the certificate with its details to continue, as it was on Android 12, but this popup never show up.
I attach some log (hoping you can help me).
Thanks!
Thanks mate. If you don't mind me asking, how are you doing the sideloads and does it mean that you are losing any data that you've already got on it?
Cheers.
1. MIUI camera isn't even supposed to be included in the first place but was added due to demand. Any issues that come along with it, including issues with instantaneous access via lockscreen, will be ignored.I get your frustration, but a bug report is a bug report and not nitpicking. Just because you may or may not be able to replicate it, it doesn't make it nitpicking but it's a courtesy to let you know of that issue and ask the community of any workarounds, until you may find the time and priority to fix the issue.
My suggestion: have you thought of an issue tracker (e.g. issues in GitHub)? This way it's easier to keep an overview. I don't think spamming everything in one thread is a good idea, especially not personal installation issues.
/*
* Your warranty is void. Or valid, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/