hi joey, I would wanna ask what kind of hardware you are compiling this rom with, and a estimate of how much time it takes to compile?
It will bootloop. Just wipe data and update to the latest firmware found in the main post as well.Hi everyone, I'm currently on previous Evolution X ROM (https://forum.xda-developers.com/t/closed-rom-11-raphael-discontinued-evolution-x-05-03-22.4179163/)
Do you think I can just apply this RTOM without wiping anything ? Or I must have to wipe everything before ?
Thank in advance and thank you for this ROM !
Okay thank ! And If i put this ROM, i'll be able to apply future updates without wiping anymore ?It will bootloop. Just wipe data and update to the latest firmware found in the main post as well.
For the time being, yesOkay thank ! And If i put this ROM, i'll be able to apply future updates without wiping anymore ?
Try format data after flashing zip.that worked for meI've just wiped everything and just flashed latest zip (evolution_raphael-ota-tq2b.230505.005.a1-05261738-unsigned.zip) and it always return into orangefox recovery.
Anyone already have this issue and know how to resolve it ?
I've tried twice and same result
Thanks, it works.
Just installed the latest version on my daughter's phone. It's setup via family link so has certain restrictions.
I tried to set up fingerprint unlock for her, at which point it asks for my (parent) password. After this it asks me to agree to something but then I get a blank screen right after.
Is there any solution for this?
You'd think it's a bug until you realize fingerprint won't unlock when night light is active on the lockscreen itself. It's the intended behavior as our fingerprint sensor isn't the same with the Pixels.Bug description: There is a bug with the "On screen fingerprint". Whenever I turn of my screen the night mode (the one that make screen yellow) also stops. But after unlocking it the device, the night mode turns back on.
Yea, I was also thinking the same lol.You'd think it's a bug until you realize fingerprint won't unlock when night light is active on the lockscreen itself. It's the intended behavior as our fingerprint sensor isn't the same with the Pixels.
Can you think of a way that could help better understand this bug then? I can reproduce it as many times as I want.
No. It's an issue with your setup as no one else is reporting the same behavior. I advise a data format or just move to another ROM entirely. Tired of hearing about this isolated issue.Hi @joeyhuab,
I am still experiencing this bug. Do you have any idea on how I could produce meaningful logs that you could look into?
No. It's an issue with your setup as no one else is reporting the same behavior. I advise a data format or just move to another ROM entirely. Tired of hearing about this isolated issue.
Yeah I suggest everyone to just disable sim pin for now. It's something i really can't bother to fix right now as not everyone uses that.
It worked for me using twrp. it's now booting into the rom, but I had to use a previous version because the new one had the zip file corrupted for some reason...
Just update the firmware to the latest and stop using non-root vanced and switch to RVX Lite.logcat is not really helping on that stuttering issue. I started logging immediately before I brought the youtube app into background and immediately the video stopps.
Code:09-18 07:40:20.138 2255 2312 V WindowManager: Unknown focus tokens, dropping reportFocusChanged 09-18 07:40:20.821 2255 4849 W WindowManager: applyWithNextDraw with mSyncState=1, Window{fb50a02 u0 com.google.android.youtube/com.google.android.apps.youtube.app.watchwhile.WatchWhileActivity}, com.android.server.wm.Task.setMainWindowSizeChangeTransaction:4466 com.android.server.wm.Task.setMainWindowSizeChangeTransaction:4449 com.android.server.wm.WindowOrganizerController.applyTaskChanges:745 com.android.server.wm.WindowOrganizerController.applyWindowContainerChange:1580 com.android.server.wm.WindowOrganizerController.applyTransaction:550 com.android.server.wm.WindowOrganizerController.applyTransaction:481 com.android.server.wm.WindowOrganizerController.applySyncTransaction:236 android.window.IWindowOrganizerController$Stub.onTransact:224 09-18 07:40:20.856 2255 6030 D CoreBackPreview: Window{c842ab1 u0 pip-dismiss-overlay}: Setting back callback OnBackInvokedCallbackInfo{mCallback=android.window.IOnBackInvokedCallback$Stub$Proxy@83d5304, mPriority=0} 09-18 07:40:21.443 2255 2269 W SoundTriggerHelper: prepareForRecognition: loadSoundModel failed with status: -2147483648 09-18 07:40:21.443 2255 2269 W SoundTriggerHelper: startRecognition failed to prepare model for recognition 09-18 07:40:21.443 4213 5253 W AlwaysOnHotwordDetector: startRecognition() failed with error code -2147483648 09-18 07:40:22.590 2255 2255 E SoundTriggerHelper: onServiceDied!! 09-18 07:40:22.591 4213 7915 I AlwaysOnHotwordDetector: onError: -32
Change the icon pack once. Settings > The Evolver > themes > icon pack.Since quite a lot of time, I can't manage to change system color via monet palette in settings, there is still this issue in latest build. Is there a toggle somewhere that need to be turned on or off? Thanks
I don't have the update option in the settings. I have previously updated using the setting but now it is not showing. Any help appreciated.
I wish you people could ACTUALLY read changelogs more often. It was stated that I disabled OTA to prepare for Android 14 arrival to avoid dirty flash accidents. Jeez. READ PEOPLE.
Feel free to move to another ROM. Everyone will be forced to clean flash anyways once Android 14 arrives. You're just trying to delay the inevitable.OMG I will never use evo x again, updates are a total disaster, use evo x don't store important photos, anything important
/*
* 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.
*/