@Chainfire,
Can you throw a hint to when rootless mode on android 10+ will be supported?
Thanks for the elaboration! I was always under the impression that KCAL was superior in performance AND quality, so I never really compared the two, when I had devices that supported both. Do you know how the built in "night light" works in comparison to what cflumen does?It's gotten a bit confusing, but 'best quality' just means using one of CF.lumen's own drivers. Be it compatibility, performance, or anti-flicker mode (only compatibility mode is supported on Android 10+). The quality is better than KCAL and PCC/RGB modes, though on older devices KCAL is faster (best performance vs best quality).
You're not imagining things about the color tone. Though the different variants of CF.lumen's own driver use different methods to accomplish it, they all end up applying a full-blown color matrix to what is rendered on-screen. KCAL and PCC/RGB modes apply an integer scalar to each individual color channel. Additionally CF.lumen's modification is done by the GPU while the kernel-based ones may be applied in the display, which could differ in visible output.
Using a color matrix is not only significantly more precise in its per channel output, it also allows for precise gamma correction and darkening, and it allows information from one color channel to be used in calculation for the other channels. That is why for example the RED mode for night usage looks so good - it converts the entire display to proper luminance-based grayscale (using information from red, green and blue channels), then outputs that in shades of red rather than shades of gray. The closest you can get with KCAL is just outputting the red channel only, discarding the green and blue channels completely.
Aside from the channel information cross-over, you could say that KCAL compounds rounding errors, reducing quality. If that's something the average user can objectively see is another question though.
It's totally understandable why you can't be bothered with it any more. But I love how you pop up once in a while, and bring something as unique as this app, up to the latest version of AndroidGoogle's endless bullshit is one of several reasons I'm so done with Android/Mobile; not the biggest, but close to.
Ah yeah I totally forgot that it's only open source. I don't use it much either. Figured it just was an alternative play store of sorts, lol.That'd require open sourcing it, which requires more work on my end. And I don't use or support F-Droid really, so...
Thanks for the elaboration! I was always under the impression that KCAL was superior in performance AND quality, so I never really compared the two, when I had devices that supported both. Do you know how the built in "night light" works in comparison to what cflumen does?
Thanks so much for the update. I saw it through the play store.v3.74 released, attached to the 2nd post. Changelogs post also updated. Uploaded to Play but I have some doubts if they'll approve the update.
Night light uses the same color matrix facility CF.lumen does in compatiblity mode. You just don't have any influence over the contents of that matrix.
"stacktrace: java.lang.RuntimeException: Unable to stop activity {eu.chainfire.lumen/eu.chainfire.lumen.ui.FilterSelectActivity}: java.lang.SecurityException: eu.chainfire.lumen was not granted this permission: android.permission.WRITE_SETTINGS"
What the app needs is write to settings permission, which I don't think you can grant in Android Settings.
You can try to grant the permission using adb.
I see. Perhaps you can disable automatic filter switching.Thank you, but now I cant even try to fix this. The new issue completely breaks the app... I uninstalled then reinstalled the app on both devices, and now I experience the instant crash that I was talking about (when clicking on "Master filter mode")
Exactly the same happens on Realme.
Log: https://del.dog/bileakexat.txt (OnePlus 3 - Android 10)
Does going back to the old version fix the issue? If so, you may wish to just stay on that version. All the new version does is add Android 11 support as Chainfire said.Thank you, but now I cant even try to fix this. The new issue completely breaks the app... I uninstalled then reinstalled the app on both devices, and now I experience the instant crash that I was talking about (when clicking on "Master filter mode")
Exactly the same happens on Realme.
Log: https://del.dog/bileakexat.txt (OnePlus 3 - Android 10)
I see. Perhaps you can disable automatic filter switching.
Does going back to the old version fix the issue? If so, you may wish to just stay on that version. All the new version does is add Android 11 support as Chainfire said.
Try the attached version, see if it fixes the issue
logcatStill crashes on oneplus 7 pro android 10 OOS.
1 download the old version 1.72Still crashes on oneplus 7 pro android 10 OOS.
not work 1.75 - Android 10, It's like version 1.74 what you changed. I am using 1.72 on android 10.Try with the version posted a few posts above. I don't debug old release.
not work 1.75 - Android 10, It's like version 1.74 what you changed. I am using 1.72 on android 10.