-
Notifications
You must be signed in to change notification settings - Fork 664
[Mi Pad 4] Flickering Backlight #128
Comments
I'm adjusting the backlight slider really slow and observing the brightness I actually get. The backlight slider on this device is exactly like 15-16 normal slider concat together. Please let me know if there's anything or any file you want. |
What have you got in /sys/class/backlight/panel0-backlight/max_brightness ?
Le mer. 25 juil. 2018 à 07:34, Asureus <notifications@github.com> a écrit :
… I'm adjusting the backlight slider really slow and observing the
brightness I actually get.
Here's what I found:
The backlight slider on this device is exactly like 15-16 normal slider
concat together.
Within each tiny slider segment, brightness changes smoothly, when my
finger crosses segment border backlight suddenly jumps between darkest and
brightest.
I think that explains the flickers when I adjust the slider normally.
Please let me know if there's anything or any file you want.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAOOuSaWrjscaWsQtDyeRg_o5sw9WFlks5uKANfgaJpZM4VfZOH>
.
|
Thanks for the quick reply! I find the situation similar to #72
I blindly went on with nothing changes, still got about 16 segments
|
What about setprop persist.sys.qcom-brightness 4093 ?
Le mer. 25 juil. 2018 à 08:38, Asureus <notifications@github.com> a écrit :
… Thanks for the quick replay.
I find the situation similar to #72
<#72>
Except I don't have /sys/class/backlight
/system/bin/sh: cd: /sys/class/backlight: No such file or directory
I blindly went on with
setprop persist.display.max_brightness 4095
or
setprop persist.display.max_brightness 255
and reboot
nothing changes, still got about 16 segments
phhgsi_arm64_a:/ $ getprop ro.vendor.build.fingerprint
Xiaomi/clover/clover:8.1.0/OPM1.171019.019/8.7.19:user/release-keys
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAOOjCjBAwE2lkLsAmm71Vn4mk0iFESks5uKBJogaJpZM4VfZOH>
.
|
On the other hand it seems the lowest possible brightness is much higher than before. Now if I set brightness to lowest, when the screen dims (like when it's idle) it can dims much more. Is it the right time to send you my framework-res.apk? |
Oh, that's interesting for the minimum backlight, I probably missed that,
thanks.
Can you browse /sys to find where you might have max brightness? I'd say
something like /sys/class/leds/lcd-backlight0/max_brightness
As for framework-res, I'm guessing that if you're asking it's because you
have no auto backlight?
Le mer. 25 juil. 2018 à 08:54, Asureus <notifications@github.com> a écrit :
… setprop persist.sys.qcom-brightness 4093
Thanks it's working! Now the backlight slider is a whole segment. Flicker
is completely gone.
On the other hand it seems the lowest possible brightness is much higher
than before. Now if I set brightness to lowest, when the screen dims (like
when it's idle) it can dims much more.
Is it the right time to send you my framework-res.apk?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAOOiy1WMyTRo2BMSAilh9DGAmtmGhDks5uKBZBgaJpZM4VfZOH>
.
|
Thanks got it:
when setting brightness slider to lowest:
I can safely do You are right auto backlight is not working here. I took the liberty to attach framework-res.apk from latest stock ROM Also when first installed v22, the UI is ridiculously large and it's phone UI
Then it's working great. Is it OK for you to somehow integrate this tweak for our device? thank you |
Possibly fixed with phhusson/device_phh_treble@5efefba |
I've tried v103 yesterday and it has the same issue as i outlined in issue #168, so that release certainly doesn't fix it for the Mi 6x. However, the fix mentioned in this thread does work! The reason it aint working is probably because the fix in #5efefba specifically checks for "Xiaomi/clover/clover" whereas my fingerprint seems to be: I "think" you might be best off to check if "persist.sys.qcom-brightness" is set and if not then set it. Regardless of device. Of if that's too generic, set it for all Xiaomi devices? |
About Xiaomi Mi 6X (wayne): |
greetings, tested v103 and also v104 on Mi Pad 4 Enabling auto brightness also practically fix the issue of min brightness not being low enough. turn on "adaptive brightness" on v104 and cover the ambient light sensor, The case becomes more drastic on Mi 8 SE, where manual brightness minimum is But that's another issue on another device. I'll provide more info to #148 later For Mi Pad 4, it's now completely solved. Thank you again. |
v22 booted on Mi Pad 4, a Treble-enabled tablet.
Everything seems to be working except I get similar backlight issue as #121
Backlight can be set in a lottery way, with 24 very bright, 25 darkest, 27 brightest, 31 darker etc.
Seems most of the time it sticks to brighter backlight.
Because of this, a should-be smooth backlight transition, like during the seconds when screen goes on or turns off, backlight jumps rapidly hence the flicker.
After boot I waited 30 minutes before change brightness then logcat:
MiPad4_brightness_logcat.txt
Backlight is working smoothly on the stock ROM which I installed v22 on
The text was updated successfully, but these errors were encountered: