[CLOSED][ROM][12.1_r22][EOL][OFFICIAL] Evolution X 6.7 [08/14/2022]

Status
Not open for further replies.
Search This thread

devsk

Senior Member
Dec 14, 2008
2,052
763
I updated this afternoon and now the OOS Camera is broken. It FCs on launch. Anybody else seeing the same thing? I cleared cache and storage, but no help.

Logcat:
Code:
05-15 16:32:18.569 24672 24672 E AndroidRuntime: FATAL EXCEPTION: main
05-15 16:32:18.569 24672 24672 E AndroidRuntime: Process: com.oneplus.camera, PID: 24672
05-15 16:32:18.569 24672 24672 E AndroidRuntime: java.lang.RuntimeException: Unable to get provider com.oplus.epona.internal.EponaProvider: java.lang.ClassNotFoundException: Didn't find class "com.oplus.epona.internal.EponaProvider" on path: DexPathList[[zip file "/system_ext/priv-app/OnePlusCamera_sm8250/OnePlusCamera_sm8250.apk"],nativeLibraryDirectories=[/system_ext/priv-app/OnePlusCamera_sm8250/lib/arm64, /system_ext/priv-app/OnePlusCamera_sm8250/OnePlusCamera_sm8250.apk!/lib/arm64-v8a, /system/lib64, /system_ext/lib64, /system/lib64, /system_ext/lib64]]
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at android.app.ActivityThread.installProvider(ActivityThread.java:7466)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at android.app.ActivityThread.installContentProviders(ActivityThread.java:6977)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6748)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at android.app.ActivityThread.access$1500(ActivityThread.java:256)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2091)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:106)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at android.os.Looper.loopOnce(Looper.java:201)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:288)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:7872)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)
05-15 16:32:18.569 24672 24672 E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: Didn't find class "com.oplus.epona.internal.EponaProvider" on path: DexPathList[[zip file "/system_ext/priv-app/OnePlusCamera_sm8250/OnePlusCamera_sm8250.apk"],nativeLibraryDirectories=[/system_ext/priv-app/OnePlusCamera_sm8250/lib/arm64, /system_ext/priv-app/OnePlusCamera_sm8250/OnePlusCamera_sm8250.apk!/lib/arm64-v8a, /system/lib64, /system_ext/lib64, /system/lib64, /system_ext/lib64]]
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:218)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at android.app.AppComponentFactory.instantiateProvider(AppComponentFactory.java:147)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at androidx.core.app.CoreComponentFactory.instantiateProvider(CoreComponentFactory.java:67)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        at android.app.ActivityThread.installProvider(ActivityThread.java:7450)
05-15 16:32:18.569 24672 24672 E AndroidRuntime:        ... 11 more
05-15 16:32:18.573  1572 11525 W ActivityTaskManager:   Force finishing activity com.oneplus.camera/.OPCameraActivity

I also notice that the following log still floods:

Code:
05-15 16:32:18.567  1029  1029 E qdmetadata: paramType 32 not supported
05-15 16:32:18.567  1029  1029 E qdmetadata: paramType 32 not supported
05-15 16:32:18.567  1029  1029 E qdmetadata: paramType 32 not supported
05-15 16:32:18.567  1029  1029 E qdmetadata: paramType 32 not supported
05-15 16:32:18.567  1029  1029 E qdmetadata: paramType 32 not supported
@AnierinB I just updated with the 0521 OTA and the OOS camera is still crashing. Any ideas? Do I need to dirty flash it from 'adb sideload'?
 

devsk

Senior Member
Dec 14, 2008
2,052
763
I think OTA has something to do with it. I was hoping the 2nd OTA will clean it up but apparently not
 

devsk

Senior Member
Dec 14, 2008
2,052
763
It says the application size is about 350KB
 

Attachments

  • Screenshot_20220520-220509_OOS_CAM.png
    Screenshot_20220520-220509_OOS_CAM.png
    124.4 KB · Views: 50

devsk

Senior Member
Dec 14, 2008
2,052
763
Code:
05-20 22:08:40.277 16974 16974 E AndroidRuntime: Process: com.oneplus.camera, PID: 16974
05-20 22:08:40.277 16974 16974 E AndroidRuntime: java.lang.RuntimeException: Unable to get provider com.oplus.epona.internal.EponaProvider: java.lang.ClassNotFoundException: Didn't find class "com.oplus.epona.internal.EponaProvider" on path: DexPathList[[zip file "/system_ext/priv-app/OnePlusCamera_sm8250/OnePlusCamera_sm8250.apk"],nativeLibraryDirectories=[/system_ext/priv-app/OnePlusCamera_sm8250/lib/arm64, /system_ext/priv-app/OnePlusCamera_sm8250/OnePlusCamera_sm8250.apk!/lib/arm64-v8a, /system/lib64, /system_ext/lib64, /system/lib64, /system_ext/lib64]]
05-20 22:08:40.277 16974 16974 E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: Didn't find class "com.oplus.epona.internal.EponaProvider" on path: DexPathList[[zip file "/system_ext/priv-app/OnePlusCamera_sm8250/OnePlusCamera_sm8250.apk"],nativeLibraryDirectories=[/system_ext/priv-app/OnePlusCamera_sm8250/lib/arm64, /system_ext/priv-app/OnePlusCamera_sm8250/OnePlusCamera_sm8250.apk!/lib/arm64-v8a, /system/lib64, /system_ext/lib64, /system/lib64, /system_ext/lib64]]
 

Melcore127

Member
Jul 19, 2021
26
9
Hey I've flashed this and till now have had a great time with it. I just noticed that sometimes the system UI is funky and i have to restart it or the weird big won't go like sometimes when I press the edit tiles or rearrange then on the top it just blacks out and it just bugs out other than that I haven't seen anything else and I've been loving it hopefully this small nick gets fixed. Thanks
 
  • Like
Reactions: enjoy_life

Harris shaj

New member
Aug 10, 2016
1
0
Back gesture is not working after disabling on-screen navigation bar.( settings->The Evolver->Buttons->On-screen navigation bar)
Device : Oneplus 8 (instantnoodle)
Can someone please take a look.
 

devsk

Senior Member
Dec 14, 2008
2,052
763
I think I have something for battery life on this ROM.
So, I figured out why the battery life took a nosedive with this ROM compared to OOS 11. There are few things in this ROM specifically that seemed to have added to the bad battery life:

1. GPU overclock to 900Mhz from 587Mhz. I think we don't need to OC the GPU on this phone for silky smooth operation. I limited this back to stock and I see no effects in smoothness.

My request is that ROM writers provide a switch, named "Overclock GPU" in the Settings->Evolver somewhere, default it to false and let people who want to choose to OC, tick it.

2. AOD brightness is not adjusted. AOD is too bright. The reason for this is that brightness adjustment from apps is broken in 12. Its a private secure system setting and apps, even when granted the permission to change System Settings, can not change the brightness. I was lowering the brightness upon Display Lock using Automate to a lower brightness because I don't need a bright AOD, which is mostly used to see the time and see if any notification needs my attention. That seems to fail with A12.

This is a major battery sucker!

My request is that ROM writers provide a switch to disable Auto Brightness and lock the brightness to a custom level from the AOD settings.

I know about the "Extra Dim" setting, but its too dim for normal use and its not specific to AOD.

3. Memory writes. This ROM seems to be overly busy writing logging stuff to circular memory buffers, over and over again. Its a likely a bug somewhere that needs to be fixed but writing flooding logs to circular memory buffers repeatedly consumes a lot of CPU cycles as well as memory cycles, both leading to power usage.

So, turned off logging of several components using 'adb' commands to quieten down the memory writing.

4. There are some VM kernel parameters which are set wrong in this ROM. Particularly, the default usage of dirty_ratio and dirty_background_ratio. With small memory systems, these are fine to use but with a big memory system like OnePlus, the default settings accumulate too much dirty buffers for the system to dispose off in a reasonable time. This not only leads to more power usage because it blocks processes but also because it keeps the system awake longer. The inline IO can also cause micro-stutters in the processes which take on the job of the dumping these large dirty buffers to disk.

A way to solve this is to set dirty_bytes and dirty_background_bytes. This way you can limit the dirty buffers and dump them from time to time way sooner than, let's say 3GB (25% of 12GB RAM). A typical rule of thumb to keep any latency below a UI visible watermark(e.g. 200ms) is to see how fast the NAND is and use that calculate a value for dirty_bytes and dirty_background_bytes. I use a value of 15MB i.e. don't let more than 15MB of dirty buffers to accumulate.

Code:
function setupVmParams()
{
  setAllDebugInfoLogsToError

  # VM changes
  echo 15000000 > /proc/sys/vm/dirty_background_bytes
  echo 15000000 > /proc/sys/vm/dirty_bytes
}

function setAllDebugInfoLogsToError()
{
  # top 25 debug/info/verbose polluters
  for comp in $(logcat -d | awk '{if (($5 == "D") || ($5 == "I") || ($5 == "V")) { print $6}}' | sort | uniq -c | sort -n | tail -25 | awk '{print $2}')
  do
    comp=${comp%%/*}
    comp=${comp%%\|*}
    comp=${comp%%\[*}
    level=$(getprop log.tag.${comp%*:})
    if [[ "${level}" != "ASSERT" ]] && [[ "${level}" != "ERROR" ]] && [[ "${level}" != "WARN" ]]
    then
      echo "Setting the component ${comp} to WARN"
      setprop log.tag.${comp%*:} WARN
    fi
  done

  # top warning/error polluters greater than 500 count
  for comp in $(logcat -d | awk '{if (($5 == "E") || ($5 == "W")) { print $6}}' | sort | uniq -c | sort -n | tail -25 | awk '{if ($1 > 500) {print $2}}')
  do
    echo "Setting the component ${comp} to ASSERT"
    setprop log.tag.${comp%*:} ASSERT
  done
  setprop log.tag.ActivityManager INFO
  setprop log.tag.lowmemorykiller INFO
}

function setBrightnessNormal()
{
  settings put system screen_brightness_mode 1
  settings put system screen_brightness 15
}

# use this instead of automate's screen brightness block, which is not
# working in A12
function setBrightnessLow()
{
  settings put system screen_brightness_mode 0
  settings put system screen_brightness 1
}

function onePlus8ProTricks()
{
  # echo performance > governor &&

  (cd "/sys/devices/platform/soc/3d00000.qcom,kgsl-3d0/devfreq/3d00000.qcom,kgsl-3d0" &&
    echo 587000000 > max_freq &&
    cd "/sys/devices/platform/soc/3d00000.qcom,kgsl-3d0/kgsl/kgsl-3d0" &&
    echo 3 > max_pwrlevel &&
    setprop log.tag.qdmetadata ASSERT
  )
}
After doing all these tricks, I am now close to what I was getting with OOS11, which is about 26 hour run time with 5-6 hr of SOT (I have AOD on). This ROM is truly great now!
 
Last edited:

enjoy_life

Senior Member
Mar 5, 2016
211
94
1. GPU overclock to 900Mhz from 587Mhz. I think we don't need to OC the GPU on this phone for silky smooth operation. I limited this back to stock and I see no effects in smoothness.
Well, you are wrong. 900 Mhz mode is activated only in games. By getting the maximum frequency back to stock you ain't saving any battery %. If you're playing games, be ready for heavy battery usage anyway. I would take higher performance in games over 1-3% of saved battery due to stock frequency.
 

devsk

Senior Member
Dec 14, 2008
2,052
763
Well, you are wrong. 900 Mhz mode is activated only in games. By getting the maximum frequency back to stock you ain't saving any battery %. If you're playing games, be ready for heavy battery usage anyway. I would take higher performance in games over 1-3% of saved battery due to stock frequency.
hmm...but it seems to have used that power state as per state transition data in /sys. In my system, it went from 305 to 900 N number of times, then step-wise went down N number of times to each of the lower frequencies until the target frequency of 305.

I didn't play any games on this ROM yet. So, apparently you are the one who is wrong here!
 
Last edited:

Lifusiek

Member
Apr 25, 2022
6
0
So far battery look much worse compared to oos11, after 4hours od listening to music @bt headset with LTE on and Galaxy watch connected i lost 32% compared to about 20% on oos11. Hope that battery life improves after a few days od usage.
 
D

Deleted member 8880810

Guest
So far battery look much worse compared to oos11, after 4hours od listening to music @bt headset with LTE on and Galaxy watch connected i lost 32% compared to about 20% on oos11. Hope that battery life improves after a few days od usage.
Mine did. It got progressively better till the 3rd day and I'm personally satisfied. I almost flashed evo Android 11 but honestly was too tired and got lazy. Happy I didn't.
 

abdel khalis

Member
Jun 8, 2018
5
0
Samsung Galaxy S10+
Alternative installation method:

* Download Evolution-X (ROM zip & Fastboot ROM Installer) and extract the files.

* Copy payload.bin from the ROM zip to Payload Dumper, specifically to Payload Input folder.

* Run payload_dumper.exe and wait for extraction to complete.

* After fully extracted, go to Payload Output folder and copy all the image files to the main folder where fastboot files are located.

* Connect your device to PC

* Reboot your device into fastboot mode

* Run ROMinstaller.exe

* Wait until all images have been flashed

* When done, go to recovery mode and factory reset (wiping is a MUST if coming from another ROM, it's not required if you're updating)

* Reboot to system and #KeepEvolving
will it works by flashing on adb sideload ?
 
Status
Not open for further replies.

Top Liked Posts