[ROM][12.1][POLARIS][OFFICIAL] Evolution X [05/07/2022]

[voyteg]

Hello.
I installed this rom on a new phone right after MIUI.
Unfortunately, the front camera does not work.
When I click on GCAM, changing the camera to the front, the application closes.
I didn't find the selfiecamera button in the built-in camera.

I have one more mix2s.
I use PE rom there. After the December update of OTA, the same thing happened.
Here I have android 11 versions.

Do you know any solution to the front camera problem?

Can I upload an older version of PE via recovery?

 

[jjpprrrr]

Hello.
I installed this rom on a new phone right after MIUI.
Unfortunately, the front camera does not work.
When I click on GCAM, changing the camera to the front, the application closes.
I didn't find the selfiecamera button in the built-in camera.

I have one more mix2s.
I use PE rom there. After the December update of OTA, the same thing happened.
Here I have android 11 versions.

Do you know any solution to the front camera problem?

Can I upload an older version of PE via recovery?

You mean the front camera works in MIUI but not in PE? Front camera works fine for other people.

 

[voyteg]

You mean the front camera works in MIUI but not in PE? Front camera works fine for other people.

This guy have this same problem https://forum.xda-developers.com/t/...erience-aosp-2021-12-23.4038949/post-86219747

First mix2s changed from miui to Evolution X. Front camera is not working.
Second mix2s I used PE from June. Updates by OTA, selfie camera stopped working in December after the update.

Two phones, same problem. This is not the hardware fault.

 

[jjpprrrr]

This guy have this same problem https://forum.xda-developers.com/t/...erience-aosp-2021-12-23.4038949/post-86219747

First mix2s changed from miui to Evolution X. Front camera is not working.
Second mix2s I used PE from June. Updates by OTA, selfie camera stopped working in December after the update.

Two phones, same problem. This is not the hardware fault.

That's why I was wondering if the front camera would start working again if you go back to MIUI. This is an easy way to figure out whether it's a hardware issue or not.

There has been no change in camera related stuff for months. Our camera related blobs are all from stock MIUI. There hasn't been any MIUI updates, so I have no reason to touch camera blobs. Besides, polaris' front camera connector is quite fragile. It's not uncommon to see people suddenly reporting a broken front camera (using MIUI), especially in the Chinese community where people have had polaris for a longer time.

 

[voyteg]

That's why I was wondering if the front camera would start working again if you go back to MIUI. This is an easy way to figure out whether it's a hardware issue or not.

There has been no change in camera related stuff for months. Our camera related blobs are all from stock MIUI. There hasn't been any MIUI updates, so I have no reason to touch camera blobs. Besides, polaris' front camera connector is quite fragile. It's not uncommon to see people suddenly reporting a broken front camera (using MIUI), especially in the Chinese community where people have had polaris for a longer time.

I found this topic. https://forum.xda-developers.com/t/front-camera-not-working-with-new-hardware-in-custom-rom.4198661/

Did the kernel change in PE11 at the end of last year? https://jjpprrrr.com/pe/20211011-2303/
I would like to try a rom that has not been changed. I cannot download this file. Where can I find him?


I have uploaded the latest PE12 on one device.
Now I wanted to change the rom to an ARROWos for the test. Unfortunately, TWRP won't start.

 

[jjpprrrr]

I found this topic. https://forum.xda-developers.com/t/front-camera-not-working-with-new-hardware-in-custom-rom.4198661/

Did the kernel change in PE11 at the end of last year? https://jjpprrrr.com/pe/20211011-2303/
I would like to try a rom that has not been changed. I cannot download this file. Where can I find him?


I have uploaded the latest PE12 on one device.
Now I wanted to change the rom to an ARROWos for the test. Unfortunately, TWRP won't start.

The XDA topic is for another device. That does not apply to polaris.

The kernel cdsp issue does not break front camera. It makes gcam processing take forever. It has been fixed by Qualcomm already.

You need to format data in PE recovery first before switching to another ROM/recovery.

If you really want to test your front camera, use Mi Flash to flash a stock MIUI ROM.

 

[u.mel]

Hello!
I'm having troubles with my bootlooping device, still showing the animated E of Evolution X.

That's, what I've done:
- coming from latest PE12 i started with formating data in the PE-recovery
- installed latest twrp 3.6.0-9 for polaris via fastboot
- formated filesystem with `mke2fs -t ext4 -b 4096 /dev/block/bootdevice/by-name/cust` in the terminal of twrp
- installed evolution_polaris-ota-sq1d.211205.016.a1-01030957-unsigned via twrp from ota-usb
- wiped cache and dalvik
- formated data again under twrp

Because it did not work, i downloaded the ROM again, took another usb stick and repeated install. Still no success.

What did i wrong?

Thanks for some help.

 

[jjpprrrr]

Hello!
I'm having troubles with my bootlooping device, still showing the animated E of Evolution X.

That's, what I've done:
- coming from latest PE12 i started with formating data in the PE-recovery
- installed latest twrp 3.6.0-9 for polaris via fastboot
- formated filesystem with `mke2fs -t ext4 -b 4096 /dev/block/bootdevice/by-name/cust` in the terminal of twrp
- installed evolution_polaris-ota-sq1d.211205.016.a1-01030957-unsigned via twrp from ota-usb
- wiped cache and dalvik
- formated data again under twrp

Because it did not work, i downloaded the ROM again, took another usb stick and repeated install. Still no success.

What did i wrong?

Thanks for some help.

The process looks fine to me, although some are redundant. Here is something you can try:

- format data in PE recovery
- install TWRP
- install evolution x
- reboot

The format data in PE recovery already takes care of /data, /cache, and /metadata (cust).

Besides, you should always verify the md5 of the ROM zip before flashing.

 

[u.mel]

Going that way worked. Evolution X is ready for work now.

Thanks for your quick support and your tremendous work for Evolution X and Pixel Experience, jjpprrrr!!!

 

[Lillo85]

Big thanks for the rom, very satisfied of the performances and battery consumption. Recently I've seen 2 bugs., randomly but at least once or twice a day. First, the screen timeout doesn't work very well. I put the timeout on 15 seconds. With apparently no apps opened the screen and it doesn't turn off. Second, the quick settings background became dark even on light theme with status bar icons and words unreadable (see my attachement). Only way to solve it is manually restare SystemUi. Does anyone else have these bugs ?

 

[Lillo85]

Related to this link ?

 

[jjpprrrr]

Big thanks for the rom, very satisfied of the performances and battery consumption. Recently I've seen 2 bugs., randomly but at least once or twice a day. First, the screen timeout doesn't work very well. I put the timeout on 15 seconds. With apparently no apps opened the screen and it doesn't turn off. Second, the quick settings background became dark even on light theme with status bar icons and words unreadable (see my attachement). Only way to solve it is manually restare SystemUi. Does anyone else have these bugs ?

The dark notification background issue will be fixed in the next update. The screen timeout could be caused by multiple things, like certain apps keeping the screen awake, or bugs in AOSP. Wait for the next update and see if it still happens.

 

[jjpprrrr]

2022/01/23
Changelog: https://jjpprrrr.com/evox/01230545/

 

[Lillo85]

The dark notification background issue will be fixed in the next update. The screen timeout could be caused by multiple things, like certain apps keeping the screen awake, or bugs in AOSP. Wait for the next update and see if it still happens.

I flashed the new update with the system's integrated updater !!! Thanks for the great update, happy to see my wired headphones now seems to work even during calls !!! But screen timeout issue isn't fixed, I think it's AOSP related problem quite frequent accordig to this link, after December Security Update. Even dark background problem on quick settings panel isn't fixed for me. My phone has auto switch from light-dark theme according sunrise and sunset; This morning when I waked up and I turned off airplane mode, I've got some notifications and quick settings background become dark as my precedent attachment, all the rest was normally light. Tipically I get this problem the morning. Not so drammatic problem, I fix it manually restarting SystemUI. And for the screen timeout problem I manually turn off the screen and lock the phone. This is my feedback.

 

[u.mel]

I'm very happy with Evolution X in direct comparison with PE12: Nearly all the things I missed there are here now (camera via on-button, brightness via status etc).

One minor issue for me is Night Light: Even at minimal intensity there's too much orange on the screen for my taste.

Thanks again, jjpprrrr! Great work!

 

[u.mel]

Another finding: Adjusting screen-brightness within apps like vlc, newpipe etc. does not work.

 

[jjpprrrr]

Another finding: Adjusting screen-brightness within apps like vlc, newpipe etc. does not work.

Works fine here in VLC.

 

[u.mel]

Works fine here in VLC.

Ok, thanks!
Wiping cache & dalvik fixed that problem (unfortunately not the too heavy Night Sight)

 

[jjpprrrr]

Ok, thanks!
Wiping cache & dalvik fixed that problem (unfortunately not the too heavy Night Sight)

Night sight isn't a bug. That's how night sight works on AOSP. Not everything is the same with MIUI. if you don't like it, don't use it.

 

[u.mel]

Night sight isn't a bug. That's how night sight works on AOSP. Not everything is the same with MIUI.

Ok, I thought, it was a bug, because it is definitely more intense than I was used to with Night Sight in LineageOs and PE12. More so, because it is that orange even in the lowest setting. I switched it off.

Thanks for your reply.