[ROM][13.0_r20][OFFICIAL] Evolution X 7.5 [01/18/2023]

[parcou]

Please read through the thread before mentioning things that have already been addressed.

[ROM][13.0_r20][OFFICIAL] Evolution X 7.5 [01/18/2023]

Evolution X 7.5 for the OnePlus 8, 8 Pro, 8T & 9R [instantnoodle][instantnoodlep][kebab][lemonades] Living, Breaking, Keep Evolving. Pixel UI, customization and more, we are Evolution X! - Team Evolution X - @joeyhuab (Founder/Lead...

forum.xda-developers.com

View attachment 5721477

Forgive not understanding the file name or revisions. Why does the date keep changing on the post: https://sourceforge.net/projects/ev....220905.004.a2-09270551-unsigned.zip/download

09270551 is dated for today. I downloaded and installed the one 09192130. Should I be updating or anything? I do not see the r4 change, but I just do not understand the new date and if there are any updates I am missing?

Thx

Edit: I looked in the rom and selected update for the first time. I see there is an update so makes sense. I thought there was going to be an OTA prompt been on OOS for too long.

Need to flash Magisk in one of the sockets to keep root, right.

 

[allen-evan]

Is it possible to use quick switch or lawnchair 12 on this rom ??? It's a must have feature.. Don't know why after this update app opening closing animation become Soo laggy and slow... Please fix it

 

[Diaze]

can i flash from c35?

 

[AdmiralKirk]

Hello developers!
The ROM is excellent, I've been using it for 4 days, OP 9R, in general I'm happy with everything, everything works fine. I wanted to ask you to correct some points, if possible:
1) When you get the phone out of your pocket, the fingerprint scanner glows like a lantern, it's inconvenient in the dark.
2) Replace Google camera with a camera from OOS 12, if possible.
3) Add Dolby Atmos.
4) Add face unlock.

So normally we'd all ignore someone asking questions that have been repeatedly answered in a given thread. But now that I'm thinking about it, these may not have been answered in this new thread yet. So I'll give you the quick rundown.

1) Not 100% sure on this one, but I believe it's intentional. There were a lot of problems in regard to the fingerprint sensor not picking up fingerprints quickly or well, and I believe the solution was to make the backlight for it full intensity white to get it working better.
2) That has been an emphatic NO from the devs. I believe (don't quote me, my memory isn't what it used to be. Anierin feel free to correct me.) a lot of time and effort was required to port the OOS cam last time, and they likely believe their limited time and efforts better spent on other aspects since for 90% of cases, GCam is as good or better (there has been some discussion of OIS being inferior for some models though).
3) That would be another emphatic NO. I believe (again, don't quote me, this is from memory on a convo on Tele awhile back), that the reasoning here is that everyone likes something a little different with Audio, so they're leaving it each to their own. There are Magisk modules for Dolby, Viper, Ainur and others. Although I'm not sure how compatible each of those is with Android 13.
4) As I understand it, this is a Google thing that hasn't yet been implemented for A13 yet. I believe it doesn't even exist on the Pixel's at the moment. (As always, please correct me if I'm wrong).

 

[Koshukar]

So normally we'd all ignore someone asking questions that have been repeatedly answered in a given thread. But now that I'm thinking about it, these may not have been answered in this new thread yet. So I'll give you the quick rundown.

1) Not 100% sure on this one, but I believe it's intentional. There were a lot of problems in regard to the fingerprint sensor not picking up fingerprints quickly or well, and I believe the solution was to make the backlight for it full intensity white to get it working better.
2) That has been an emphatic NO from the devs. I believe (don't quote me, my memory isn't what it used to be. Anierin feel free to correct me.) a lot of time and effort was required to port the OOS cam last time, and they likely believe their limited time and efforts better spent on other aspects since for 90% of cases, GCam is as good or better (there has been some discussion of OIS being inferior for some models though).
3) That would be another emphatic NO. I believe (again, don't quote me, this is from memory on a convo on Tele awhile back), that the reasoning here is that everyone likes something a little different with Audio, so they're leaving it each to their own. There are Magisk modules for Dolby, Viper, Ainur and others. Although I'm not sure how compatible each of those is with Android 13.
4) As I understand it, this is a Google thing that hasn't yet been implemented for A13 yet. I believe it doesn't even exist on the Pixel's at the moment. (As always, please correct me if I'm wrong).

I don’t know exactly how things are with other A13 firmwares, but even if we discard what I wrote above, this is a very worthy ROM. The fact that it is often updated over the air is good news.

 

[Klusio19]

GCam is as good or better (there has been some discussion of OIS being inferior for some models though).

Exactly that. For OnePlus 8 series, (I don't know about other OnePlus devices, I don't own them) videos taken from anything but OOS cam are basically not usable, because they are shaky af. For the rest - GCam is godlike, that's obvious. But still, cringe fanboys will say that "GCam is the best, and they see no difference in video stabilization", etc, etc. You basically have to not take any videos at all to say that.
Also someone will also cite an argument, that you can use stabilizating feature in Google Photos - yeah, it works, but it looks bad and super unnatural.

 

[AnierinB]

I'm not adding OOS Cam or Dolby.

 

[Klusio19]

I'm not adding OOS Cam or Dolby.

You can actually write it somewhere in the OP.

 

[Marcyvee]

Is it possible with the last build, to improve Google gestures with some actions when I hold swipe omg left or right? Such as it was in the >12 version?

 

[FreshlyBaked 420]

You can actually write it somewhere in the OP.

To be totally honest, AB has probably mentioned this on every single page of the thread. It's been said a few times he's not adding it.

 

[Klusio19]

To be totally honest, AB has probably mentioned this on every single page of the thread. It's been said a few times he's not adding it.

That's why he could add it xD. So everyone can see it in the OP

 

[devsk]

Are you sure? For me, it starts to collect a bug report and then, just reboots the system without completing the bug report. Tried it from both command line and from the System->Developer Options

@AnierinB Another user did this as well and his phone rebooted as well. Do you have an idea about what's going on? Google Fi support really needs the bug report to debug the issue I am facing with mobile data.

 

[Marcyvee]

I updated to the last version yesterday.
I installed as OTA update after flash the new recovery from fastboot and sideloaded copipartition.zip. I haven't wipe any partition, anyway no problem at all. Every app seems to work fine.
I can't change the theme color, but is not a big problem. The rom looks great! No reason to not update.

 

[vacs03]

Exactly that. For OnePlus 8 series, (I don't know about other OnePlus devices, I don't own them) videos taken from anything but OOS cam are basically not usable, because they are shaky af. For the rest - GCam is godlike, that's obvious. But still, cringe fanboys will say that "GCam is the best, and they see no difference in video stabilization", etc, etc. You basically have to not take any videos at all to say that.
Also someone will also cite an argument, that you can use stabilizating feature in Google Photos - yeah, it works, but it looks bad and super unnatural.

For the time being I'm using warp stabilizier in adobe premiere pro on pc to stabilize videos taken with gcam, it isn't perfect but it's currently the best option

 

[parcou]

I cannot access the DATA folder
Internal storage > Android > Data

OP8P is rooted with Magisk, unlike on Android 12, I cannot access the DATA folder on A13. Using the FILES folder in the rom shows nothing.

I have used and the paid app for years Solid Explorer, which cannot grant access to \Data folder on A13. None of these file explorer apps can access this folder. I need access to the folders for apps like Swift Backup to back up to the cloud.

Is there a way to get rom access to the Android\Data folder?

Thx

 

[devsk]

@AnierinB my man! Google Fi support is bugging me about the bug report. I need to respond to them to get my mobile data fixed. Please help.

Is there anything that clicks in the output below:

09-30 19:27:34.916 10309 10404 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x14 in tid 10404 (IrisHWC), pid 10309
 (composer-servic)
...
09-30 19:27:35.372 22450 22450 F DEBUG   : uid: 1000
09-30 19:27:35.372 22450 22450 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000014
09-30 19:27:35.372 22450 22450 F DEBUG   : Cause: null pointer dereference
09-30 19:27:35.372 22450 22450 F DEBUG   :     x0  0000000000000000  x1  0000000000000000  x2  b400007723445558  x3  00000000ffffffff
09-30 19:27:35.372 22450 22450 F DEBUG   :     x4  0000000000000000  x5  0000000000000008  x6  0000000000000001  x7  0000000000000000
09-30 19:27:35.372 22450 22450 F DEBUG   :     x8  0000000000000000  x9  0000000000000000  x10 0000000000000000  x11 0000000000000000
09-30 19:27:35.372 22450 22450 F DEBUG   :     x12 fff4000000000000  x13 0000000000000001  x14 0000000000000028  x15 000000000000000e
09-30 19:27:35.373 22450 22450 F DEBUG   :     x16 0000000000000001  x17 00000077aab86854  x18 000000770f442000  x19 b400007723445540
09-30 19:27:35.373 22450 22450 F DEBUG   :     x20 b400007723445610  x21 b400007723445558  x22 00000000ffffffff  x23 0000000000000000
09-30 19:27:35.373 22450 22450 F DEBUG   :     x24 0000000000000030  x25 0000007712fdecb0  x26 0000007712fdf000  x27 00000000000fc000
09-30 19:27:35.373 22450 22450 F DEBUG   :     x28 00000000000fe000  x29 0000007712fdeb30
09-30 19:27:35.373 22450 22450 F DEBUG   :     lr  00000077a9e67780  sp  0000007712fde9c0  pc  00000077a9e67780  pst 0000000080001000
09-30 19:27:35.373 22450 22450 F DEBUG   : backtrace:
09-30 19:27:35.373 22450 22450 F DEBUG   :       #00 pc 0000000000017780  /apex/com.android.vndk.v33/lib64/libutils.so (android::Looper::pollInner(int)+1016) (BuildId: c200e9a85d2415f28f0687a94e6b8643)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #01 pc 0000000000017c14  /apex/com.android.vndk.v33/lib64/libutils.so (android::Looper::pollAll(int, int*, int*, void**)+296) (BuildId: c200e9a85d2415f28f0687a94e6b8643)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #02 pc 00000000000482b0  /odm/lib64/libpwirisservice.so (pxlw::DelayThread::threadLoop()+28) (BuildId: e6460e0a66759feb30484eb0f544afe4)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #03 pc 0000000000012f18  /apex/com.android.vndk.v33/lib64/libutils.so (android::Thread::_threadLoop(void*)+416) (BuildId: c200e9a85d2415f28f0687a94e6b8643)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #04 pc 00000000000f1478  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+208) (BuildId: 657a7c5a0c0be56f6df7f00bc776b77a)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #05 pc 000000000008cdec  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 657a7c5a0c0be56f6df7f00bc776b77a)
09-30 19:27:35.404 10451 12116 W NativeCrashListener: Couldn't find ProcessRecord for pid 10309
09-30 19:27:35.408 10451 11943 E NativeTombstoneManager: Tombstone's UID (1000) not an app, ignoring
09-30 19:27:35.425     1     1 I (2)[1:init][20220930_19:27:35.417124]@2 init: Untracked pid 22450 exited with status 0
09-30 19:27:35.425     1     1 I (2)[1:init][20220930_19:27:35.417160]@2 init: Untracked pid 22450 did not have an associated service entry and will not be reaped

 

[AnierinB]

@AnierinB my man! Google Fi support is bugging me about the bug report. I need to respond to them to get my mobile data fixed. Please help.

Is there anything that clicks in the output below:

09-30 19:27:34.916 10309 10404 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x14 in tid 10404 (IrisHWC), pid 10309
 (composer-servic)
...
09-30 19:27:35.372 22450 22450 F DEBUG   : uid: 1000
09-30 19:27:35.372 22450 22450 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000014
09-30 19:27:35.372 22450 22450 F DEBUG   : Cause: null pointer dereference
09-30 19:27:35.372 22450 22450 F DEBUG   :     x0  0000000000000000  x1  0000000000000000  x2  b400007723445558  x3  00000000ffffffff
09-30 19:27:35.372 22450 22450 F DEBUG   :     x4  0000000000000000  x5  0000000000000008  x6  0000000000000001  x7  0000000000000000
09-30 19:27:35.372 22450 22450 F DEBUG   :     x8  0000000000000000  x9  0000000000000000  x10 0000000000000000  x11 0000000000000000
09-30 19:27:35.372 22450 22450 F DEBUG   :     x12 fff4000000000000  x13 0000000000000001  x14 0000000000000028  x15 000000000000000e
09-30 19:27:35.373 22450 22450 F DEBUG   :     x16 0000000000000001  x17 00000077aab86854  x18 000000770f442000  x19 b400007723445540
09-30 19:27:35.373 22450 22450 F DEBUG   :     x20 b400007723445610  x21 b400007723445558  x22 00000000ffffffff  x23 0000000000000000
09-30 19:27:35.373 22450 22450 F DEBUG   :     x24 0000000000000030  x25 0000007712fdecb0  x26 0000007712fdf000  x27 00000000000fc000
09-30 19:27:35.373 22450 22450 F DEBUG   :     x28 00000000000fe000  x29 0000007712fdeb30
09-30 19:27:35.373 22450 22450 F DEBUG   :     lr  00000077a9e67780  sp  0000007712fde9c0  pc  00000077a9e67780  pst 0000000080001000
09-30 19:27:35.373 22450 22450 F DEBUG   : backtrace:
09-30 19:27:35.373 22450 22450 F DEBUG   :       #00 pc 0000000000017780  /apex/com.android.vndk.v33/lib64/libutils.so (android::Looper::pollInner(int)+1016) (BuildId: c200e9a85d2415f28f0687a94e6b8643)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #01 pc 0000000000017c14  /apex/com.android.vndk.v33/lib64/libutils.so (android::Looper::pollAll(int, int*, int*, void**)+296) (BuildId: c200e9a85d2415f28f0687a94e6b8643)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #02 pc 00000000000482b0  /odm/lib64/libpwirisservice.so (pxlw::DelayThread::threadLoop()+28) (BuildId: e6460e0a66759feb30484eb0f544afe4)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #03 pc 0000000000012f18  /apex/com.android.vndk.v33/lib64/libutils.so (android::Thread::_threadLoop(void*)+416) (BuildId: c200e9a85d2415f28f0687a94e6b8643)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #04 pc 00000000000f1478  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+208) (BuildId: 657a7c5a0c0be56f6df7f00bc776b77a)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #05 pc 000000000008cdec  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 657a7c5a0c0be56f6df7f00bc776b77a)
09-30 19:27:35.404 10451 12116 W NativeCrashListener: Couldn't find ProcessRecord for pid 10309
09-30 19:27:35.408 10451 11943 E NativeTombstoneManager: Tombstone's UID (1000) not an app, ignoring
09-30 19:27:35.425     1     1 I (2)[1:init][20220930_19:27:35.417124]@2 init: Untracked pid 22450 exited with status 0
09-30 19:27:35.425     1     1 I (2)[1:init][20220930_19:27:35.417160]@2 init: Untracked pid 22450 did not have an associated service entry and will not be reaped

It looks like it's a segfault due to me disabling softiris in kernel, which I'm not reverting until the reason why I disabled it is fixed

P.s GoogleFi support isn't going to do be able to do anything If you're running a custom ROM. I've already asked you to check if it's working on stock, although you don't want to, so why should I help?

P.s I can send a boot.img with softiris re enabled so you can take your bug report although I'd still like an answer to what I just said.

 

[devsk]

It looks like it's a segfault due to me disabling softiris in kernel, which I'm not reverting until the reason why I disabled it is fixed

P.s GoogleFi support isn't going to do be able to do anything If you're running a custom ROM. I've already asked you to check if it's working on stock, although you don't want to, so why should I help?

P.s I can send a boot.img with softiris re enabled so you can take your bug report although I'd still like an answer to what I just said.

Its some weird interaction between Google Fi app and mobile data, where when the app is disabled or uninstalled, the data works. I would gladly disable the app but then, the MMS stops working.

Now, whether that interaction is because of Android 13 or not, we don't know. But I would like Google to try to see if they can debug that.

If you can pls give me a boot.img with the revert on softirs, I get Fi support off my back.

 

[DrDominate]

I cannot access the DATA folder
Internal storage > Android > Data

OP8P is rooted with Magisk, unlike on Android 12, I cannot access the DATA folder on A13. Using the FILES folder in the rom shows nothing.

I have used and the paid app for years Solid Explorer, which cannot grant access to \Data folder on A13. None of these file explorer apps can access this folder. I need access to the folders for apps like Swift Backup to back up to the cloud.

Is there a way to get rom access to the Android\Data folder?

Thx

Using FX file explorer with the root add-on I'm able to access the Android/Data folder.

 

[ciku720]

Has anyone succeeded using a custom kernel on this Rom? I know that the blu_spark does not support the new partition system we have on the EvolutionX. I also searched few other kernels on XDA but none seem to work with Android 13 in general. Did I miss something, are there some alpha versions to try maybe?