Using this tool, we're able to calibrate our G Flex 2 displays without the need of an unlocked bootloader and kernel modification.
http://forum.xda-developers.com/g4/orig-development/kppd-configure-post-processing-settings-t3165247
Here are the settings I'm currently using on my H950 for Screen mode Standard.
Code:
[red]=248
[green]=235
[blue]=244
[hue]=0
[saturation]=271
[value]=255
[contrast]=265
[invert]=0
Maybe someone with a colorimeter like a Spyder or the like can help get a better calibration?
Hi, so i managed to flash the zip with flashfire but that second part i don't understand can you guide me trougth it, the part with the rom toolbox
ShadowRii said:
Hi, so i managed to flash the zip with flashfire but that second part i don't understand can you guide me trougth it, the part with the rom toolbox
Click to expand...
Click to collapse
Ok, so open ROM Toolbox Lite tap on Scripter. The tap the + sign and create. Name the script KPPD Start or whatever you want. The in the commands section type in:
Code:
kppd /system/etc/postproc.conf
Save it. Then you'll find it in the list of scripts. Tap on it and tap Set at boot.
Now, whenever you make a change to the postproc.conf file, you have to go back to ROM Toolbox and Run script to see the changes on the screen. It's a little bit of a pain the butt but it's the best we can do with the locked bootloader. We don't get the real-time editing with any of the KCAL apps.
Thanks it worked!
I'm trieng to get rid of those yellow tints i have on the display by changing the gray scale hope it works
ShadowRii said:
Thanks it worked!
I'm trieng to get rid of those yellow tints i have on the display by changing the gray scale hope it works
Click to expand...
Click to collapse
Sweet! Do share your settings when you're done. I had a lot of green that took out.
my config :
[red]=240
[green]=220
[blue]=255
[hue]=0
[saturation]=255
[value]=255
[contrast]=255
[invert]=0
by this config greens is gone for me . i love cold and blue like sony displays and now its is very close to my favourit and natural colors .
I matched mine to my LG G Pad 8.3, which has been measured very close to the 6500k white balance standard. I also adjusted the contrast and saturation to get closer to my GS5 on Professional Photo mode. Here is my profile:
[mdp_version]=5
[pa_version]=2
[red]=256
[green]=235
[blue]=236
[hue]=0
[saturation]=265
[value]=255
[contrast]=260
[invert]=0
Please note: this profile is used on top of the Natural screen mode.
happyjack96 said:
I matched mine to my LG G Pad 8.3, which has been measured very close to the 6500k white balance standard. I also adjusted the contrast and saturation to get closer to my GS5 on Professional Photo mode. Here is my profile:
[mdp_version]=5
[pa_version]=2
[red]=256
[green]=235
[blue]=236
[hue]=0
[saturation]=265
[value]=255
[contrast]=260
[invert]=0
Please note: this profile is used on top of the Natural screen mode.
Click to expand...
Click to collapse
This one looks really good to me. I upped the saturation a bit and lowered the red to my taste. Thanks for sharing!
Sent from my LG-H950 using Tapatalk
I guess this can't be used to lower the minimum brightness?
nerg said:
I guess this can't be used to lower the minimum brightness?
Click to expand...
Click to collapse
No . but you can use this app : "Darker Pro"
I use it and set on 60% is good for me .
Its possible to change the LCD Density? I have a H950 5.1.1 Rooted.
Also, what would be a good LCDDensity for this phone?
My Best Results still now by this new config :
first go to setting-display-screen mode and set on Natural
then change postproc.conf by below numbers :
red : 200
green : 220
blue : 255
hue : 0
saturation : 260
value : 255
contrast : 255
invert : 0
for me this config have best colors .
please tell me your opinions about my config .
Tanx all
amir-kia said:
My Best Results still now by this new config :
first go to setting-display-screen mode and set on Natural
then change postproc.conf by below numbers :
red : 200
green : 220
blue : 255
hue : 0
saturation : 260
value : 255
contrast : 255
invert : 0
for me this config have best colors .
please tell me your opinions about my config .
Tanx all
Click to expand...
Click to collapse
This is way too blue on my screen.
Tikerz said:
This is way too blue on my screen.
Click to expand...
Click to collapse
How'd you get the damn thing to update? I can get the 5.1.1 update.
Sent from my LG-H950 using Tapatalk
robstunner said:
How'd you get the damn thing to update? I can get the 5.1.1 update.
Sent from my LG-H950 using Tapatalk
Click to expand...
Click to collapse
I used the date trick. Check for updates. Change the date to a month in the future. Check again. Go forward a few days. Check again. Etc.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Yea, I ended up getting a cool rep and they pushed it through to me via att chat. The same day my OnePlus got 5.1.1. Grrrr lol.
May I ask you for help with Flashing the KPPD file to unrooted Flex? I have tried Flash Gordon etc. and all ended with incorrect ZIP file. Thank you for any advice!
Flashing this with Flashfire borked my phone. It's been 20 minutes and no response from my phone. Dead. So just a cautionary tale.
UPDATE: Not borked. It just took 25 minutes. Odd.
rldev said:
Flashing this with Flashfire borked my phone. It's been 20 minutes and no response from my phone. Dead. So just a cautionary tale.
UPDATE: Not borked. It just took 25 minutes. Odd.
Click to expand...
Click to collapse
Flashing anything with Flashfire on LG phones takes 20-40 minutes. The phone just sits there blank for 30 minutes and it seems like it's dead but it's really not.
happyjack96 said:
I matched mine to my LG G Pad 8.3, which has been measured very close to the 6500k white balance standard. I also adjusted the contrast and saturation to get closer to my GS5 on Professional Photo mode. Here is my profile:
[mdp_version]=5
[pa_version]=2
[red]=256
[green]=235
[blue]=236
[hue]=0
[saturation]=265
[value]=255
[contrast]=260
[invert]=0
Please note: this profile is used on top of the Natural screen mode.
Click to expand...
Click to collapse
This one looks good, but white seems a little off on my phone. Almost like a rosey tint to the white. Very subtle though. I lowered Red to 240 and that looks better to me on my phone.
Related
Over the couple of months, many Moto G4 Plus owners have been complaining about the screen burn issue.
Well there wasn't a fix for this through software except Blue Light Filter (which didn't work for me), and while trying for the fix, I feel I have found one.
Prerequisites:
1. Android Nougat (7.0) (I am running on the stock NPJ25.93-14 i.e the 1st December 2016 Security Patch)
2. System UI Tuner enabled.
No Root Needed.
My device is the Indian variant XT1643 i.e 2GB RAM variant.
For those who are on Android Marshmallow CM based Custom ROM, you can try using the live display and setting the value nearby 3000~3500K (Although I am not sure if this would work since I haven't tried it yet).
Its the Night Mode!
1. Go download the "Night Mode Enabler" app from the Play Store --> https://play.google.com/store/apps/details?id=org.michaelevans.nightmodeenabler&hl=en
2. Open it and click on "Enable Night Mode".
3. It will take you to System UI Tuner where you can toggle night mode on/off.
4. Go to the quick settings edit option, and you will see a new tile - "Night Mode".
Toggle on the night mode and see the effect after some time (it started to show effect as soon as I enabled it and fixed the issue within 20 minutes for me).
[Q]. What will happen if I toggle off night mode?
[A]. The Screen burn will occur once again.
You need to have the Night Mode to be always on in order to get rid of that Screen Burn issue.
I know that many might not like the color temperature of Night Mode, so if you have a CM based ROM, you can edit the temperature with "Live Display" option.
Well, try it out and lets see if it works or not!
Credits : Mike Evans for making this app.
First of all, thank you for sharing this.
But your "fix" is just a workaround and not a proper fix for our broken displays.
The only real fix is to replace the display.
Thadeus Griff said:
First of all, thank you for sharing this.
But your "fix" is just a workaround and not a proper fix for our broken displays.
The only real fix is to replace the display.
Click to expand...
Click to collapse
Umm, I guess you are right. I have changed the title now.
Even screen replacement is not a permanent solution. I have replaced display and within 3 weeks issue reoccurred
It fixed the issue
The night mode enabler has fixed the issue for now. But the screen is of some weird color(especially white background).
Anyways, Its good to see my phone screen without the screen burn issue after such a long time.
Thanks
RGB calibration is the best fix for screen burn in !
unfortunately if u r on stock rom ,Then you have to root ur device .
Malware injector said:
RGB calibration is the best fix for screen burn in !
unfortunately if u r on stock rom ,Then you have to root ur device .
Click to expand...
Click to collapse
Where i can download?
nikkali25 said:
Where i can download?
Click to expand...
Click to collapse
Kernel Adiutor can modify rgb values for example.
Hi, finally I have time to make a thread about this. The problem is present on every non stock ROM, no matter if it is lollipop, MM or Nougat based. At low brightness, it seems like the screen is uppering-lowering brightness really fast. I have made a video, because "maybe" I didn't explain it very well :silly:
https://drive.google.com/open?id=0B1r3IiDMSm40R3Y0NlhzQXowOGs
(the phone is placed in the dock but it is NOT charging, in case you wonder. Also there is a small line of pixels that look like "interferences", at the right of the screen, near navigation bar, but this only happened with a kernel provided by optimumpro in order to try fixing the flickering issue)
Here and here I attached logs with different ROMs. (these ones have already been reviewed in other previous posts, but maybe they are still useful)
Nailyk asked me if the problem is present in recovery too, but I can't tell you, since the screen background in recovery is black and the flickering is more easily noticeable in white backgrounds. Anyway, I'd say that there is no flickering in recovery but I'm not sure. I may need a white themed recovery with a vey low minimum brightness value.
Also, it seems like I'm the only one with this problem (AFAIK) so there's always the chance that it is a hardware issue with my phone, but it would be strange cause with stock ROMs the screen is perfect, and screen brightness can go very low without problems.
So I am here to ask for help, and to help helping anyone interested in fixing the issue. Thank you very much!
@nailyk @optimumpro @Myself5
i too face this issue... i think this issue is GPU related... i also have flickering on stock roms. but of i keep my device warm enough.. the flickering goes away...
Interesting. I will test it again in a warm environment. But I think that this starts to sound more like a hardware issue...
Sent from my D6603 using Tapatalk
Glad you opened the thread.
About recovery it will be interesting to know if it is only kernel or rom+kernel issue.
Also flashing a recovery is faster than a full rom for testing purpose.
nailyk said:
Glad you opened the thread.
About recovery it will be interesting to know if it is only kernel or rom+kernel issue.
Also flashing a recovery is faster than a full rom for testing purpose.
Click to expand...
Click to collapse
I've installed a white theme in twrp and I didn't notice any flickering.
News: the bug is also present in Concept rom. I've checked twice and it is. But I forgot to take any log, so if you need them just tell me.
Also, I've checked very carefully if there's any slight flickering on stock Sony rom (actually I'm on ExistenZ with EliteKernel) and there isn't. I even lowered brightness to the minimum via kernel settings, as EliteKernel allows you to tweak colors, and I still don't see any flickering.
Sent from my D6603 using Tapatalk
blackhawk_LA said:
I've installed a white theme in twrp and I didn't notice any flickering.
News: the bug is also present in Concept rom. I've checked twice and it is. But I forgot to take any log, so if you need them just tell me.
Also, I've checked very carefully if there's any slight flickering on stock Sony rom (actually I'm on ExistenZ with EliteKernel) and there isn't. I even lowered brightness to the minimum via kernel settings, as EliteKernel allows you to tweak colors, and I still don't see any flickering.
Click to expand...
Click to collapse
Interesting.
Right now I don't have lot of time. As this flickering doesn't produce into recovery it shouldn't be kernel related.
Here are some experiments you can do: Set a high value to screen timeout then on root:
Code:
[email protected]:/ # find /sys -iname "*bright*"
/sys/devices/leds-qpnp-23/leds/rgb/brightness
/sys/devices/leds-qpnp-23/leds/rgb/max_brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_green/brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_green/max_brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_blue/brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_blue/max_brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_red/brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_red/max_brightness
/sys/devices/leds-qpnp-24/leds/wled:backlight/brightness
/sys/devices/leds-qpnp-24/leds/wled:backlight/max_brightness
[B]/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/brightness
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/max_brightness[/B]
/sys/devices/msm_sdcc.1/leds/mmc1::/brightness
/sys/devices/msm_sdcc.1/leds/mmc1::/max_brightness
/sys/devices/msm_sdcc.2/leds/mmc2::/brightness
/sys/devices/msm_sdcc.2/leds/mmc2::/max_brightness
The two interesting values are lcd-backlight/max_brightness & lcd-backlight/brightness. Your path will differ, depending on the kernel used, panel, etc...
Code:
[email protected]:/ # cat /sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/max_brightness
255
Here is my max value with a specific rom. Then I can set any value 1<x<255:
Code:
[email protected]:/ # echo 20 > /sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/brightness
and see the back-light changing.
Please make some experiments with this and collect data. Like working rom name, backlight_max_value, flickering start at 10, kernel version, and path of /brigthness.
If it is related to this value you should be able to reproduce into recovery.
P.S.: I just test on the CM-12.1 and notice something weird:
Code:
[email protected]:/ # cat /sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/max_brightness
4095
[email protected]:/ # cat /sys/devices/01-qcom,leds-d800/leds/wled:backlight/max_brightness
255
and only /sys/devices/01-qcom,leds-d800/leds/wled:backlight/brightness is affecting backlight.
Noticed flickering for 1 to 4 on my device.
Thanks for your time! I'm right now on Jaguar ROM (5.1.1)
/sys/devices/leds-qpnp-23/leds/rgb/brightness
/sys/devices/leds-qpnp-23/leds/rgb/max_brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_green/brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_green/max_brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_blue/brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_blue/max_brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_red/brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_red/max_brightness
/sys/devices/leds-qpnp-24/leds/wled:backlight/brightness
/sys/devices/leds-qpnp-24/leds/wled:backlight/max_brightness
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/brightness
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/max_brightness
/sys/devices/msm_sdcc.1/leds/mmc1::/brightness
/sys/devices/msm_sdcc.1/leds/mmc1::/max_brightness
/sys/devices/msm_sdcc.2/leds/mmc2::/brightness
/sys/devices/msm_sdcc.2/leds/mmc2::/max_brightness
Click to expand...
Click to collapse
and I have been playing with
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/brightness
Click to expand...
Click to collapse
The flickering is present with values from 1 to 5, maybe 6.
Stock values on ROM were
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/brightness = 4095
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/max_brightness = 4095
Click to expand...
Click to collapse
but I have no /sys/devices/01-qcom,leds-d800/leds/wled:backlight/max_brightness directory, nor something similar.
Eit: Mmm I don't know what I've done, but right now changing the setting
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/brightness
Click to expand...
Click to collapse
does nothing. I'll try again to find what I've done different. I'm a bit disaster, I know. I don't know how I've changed birghtness with these commands :S
blackhawk_LA said:
Thanks for your time! I'm right now on Jaguar ROM (5.1.1) and I have been playing with
The flickering is present with values from 1 to 5, maybe 6.
but I have no /sys/devices/01-qcom,leds-d800/leds/wled:backlight/max_brightness directory, nor something similar.
Click to expand...
Click to collapse
Use a find command like:
Code:
find /sys -iname "*bright*"
Anyway I noticed a problem on the cm-12.1 related to this. Didn't find the exact bug right now. My workaround was: trigger max value (with the slide) then go back to the wanted value. Flickering disappear. Need to reproduce to fix.
i have the flickring and ghosting when my z3 is cold and the problem gone when it heats a bit
could this problem be from my rom (6.0.1 ExistenZ)!
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
TechnoFreak750 said:
i too face this issue... i think this issue is GPU related... i also have flickering on stock roms. but of i keep my device warm enough.. the flickering goes away...
Click to expand...
Click to collapse
Same happens with me
i think its hardware issue
If it happens on stock rom it sounds like hardware related, but as for me it doesn't happen in stock roms, maybe it's a mix of hardware - software.
Could you take a dmesg (better if you do it just after booting) to see which model is your panel? If you don't know about adb, you can do it with this app https://play.google.com/store/apps/details?id=com.eolwral.osmonitor Go to settings, check root permissions, then go to messages -dmesg and export. @TechnoFreak750
Sent from my D6603 using Tapatalk
@nailyk @optimumpro
In stock Sony ROM there is the same 4095 for max brightness
[email protected]:/ # find /sys -iname "*bright*"
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/brightness
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/max_brightness
/sys/devices/leds-qpnp-ec948600/leds/rgb/brightness
/sys/devices/leds-qpnp-ec948600/leds/rgb/max_brightness
/sys/devices/leds-qpnp-ec948600/leds/led:rgb_green/brightness
/sys/devices/leds-qpnp-ec948600/leds/led:rgb_green/max_brightness
/sys/devices/leds-qpnp-ec948600/leds/led:rgb_blue/brightness
/sys/devices/leds-qpnp-ec948600/leds/led:rgb_blue/max_brightness
/sys/devices/leds-qpnp-ec948600/leds/led:rgb_red/brightness
/sys/devices/leds-qpnp-ec948600/leds/led:rgb_red/max_brightness
/sys/devices/leds-qpnp-ec948800/leds/wled:backlight/brightness
/sys/devices/leds-qpnp-ec948800/leds/wled:backlight/max_brightness
/sys/devices/msm_sdcc.1/leds/mmc1::/brightness
/sys/devices/msm_sdcc.1/leds/mmc1::/max_brightness
/sys/devices/msm_sdcc.2/leds/mmc2::/brightness
/sys/devices/msm_sdcc.2/leds/mmc2::/max_brightness
Click to expand...
Click to collapse
And the screen brightness is changed (at least) by the lines marked in bold. I haven't try the others as I don't know if they are screen related, notificacion LED or whatever.
Edited: One more thing. The minimum brightness in stock ROM is 29. If manually set to a low value, let's say 4, editing the file, the flickering appears on stock ROMs. Now I'm going to try Jaguar ROM again to see if "29" is as dark as stock (I will have to trust my eyes and memory), and if there's flickering with these value. Because I always felt that stock ROMs were at least as dark as AOSP when using minimum brightness in settings.
Edited 2: On Jaguar, with /sys/devices/leds-qpnp-24/leds/wled:backlight/brightness = 29 there's no flickering. It seems brighter than in stock but probably it's my perception, as I can't compare at the same time.
I think we can assume that it's somehow hardware related, but I don't know if there is any software solution or improvement, since the software and the "routes" are different in stock and AOSP.
blackhawk_LA said:
@nailyk @optimumpro
In stock Sony ROM there is the same 4095 for max brightness
And the screen brightness is changed (at least) by the lines marked in bold. I haven't try the others as I don't know if they are screen related, notificacion LED or whatever.
Edited: One more thing. The minimum brightness in stock ROM is 29. If manually set to a low value, let's say 4, editing the file, the flickering appears on stock ROMs. Now I'm going to try Jaguar ROM again to see if "29" is as dark as stock (I will have to trust my eyes and memory), and if there's flickering with these value. Because I always felt that stock ROMs were at least as dark as AOSP when using minimum brightness in settings.
Edited 2: On Jaguar, with /sys/devices/leds-qpnp-24/leds/wled:backlight/brightness = 29 there's no flickering. It seems brighter than in stock but probably it's my perception, as I can't compare at the same time.
I think we can assume that it's somehow hardware related, but I don't know if there is any software solution or improvement, since the software and the "routes" are different in stock and AOSP.
Click to expand...
Click to collapse
Great report.
Setting a 29 value will not provide the same result if max_brightness is 4095 or 255
Suppose 29 was set with max_brightness 4095 it will have a corresponding value of 2 for max_brightness 255. (cross multiplication: (255*29)/4095=1.2)
I remember reading in another thread that you are using cm-12.1 right now. Is it right?
P.S.: you can play with /sys/devices/leds-qpnp-ec948600/leds/led:rgb_*/brightness , it will bright up the notification led
nailyk said:
Great report.
Setting a 29 value will not provide the same result if max_brightness is 4095 or 255
Suppose 29 was set with max_brightness 4095 it will have a corresponding value of 2 for max_brightness 255. (cross multiplication: (255*29)/4095=1.2)
I remember reading in another thread that you are using cm-12.1 right now. Is it right?
P.S.: you can play with /sys/devices/leds-qpnp-ec948600/leds/led:rgb_*/brightness , it will bright up the notification led
Click to expand...
Click to collapse
Yes, I had some problems with Gmail on Jaguar and also I missed cm themes, so right now I'm on your latest cm12.1 A great daily driver!
Sent from my Xperia Z3 using Tapatalk
blackhawk_LA said:
If it happens on stock rom it sounds like hardware related, but as for me it doesn't happen in stock roms, maybe it's a mix of hardware - software.
Could you take a dmesg (better if you do it just after booting) to see which model is your panel? If you don't know about adb, you can do it with this app https://play.google.com/store/apps/details?id=com.eolwral.osmonitor Go to settings, check root permissions, then go to messages -dmesg and export. @TechnoFreak750
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
i have tried aosp, lineage os etc.. it always happens. finally the sulution is just keep your device warm enough.
TechnoFreak750 said:
i have tried aosp, lineage os etc.. it always happens. finally the sulution is just keep your device warm enough.
Click to expand...
Click to collapse
Can you tell us more details please? (step to reproduce)
Also do you have an original panel? If it is a replaced one read the thread to reproduce tests and giving us the panel name.
cc: @xkeita
The LED is confirmed by Motorola. I asked them a question and got an answer.
My question:
" This little dot on the right side of the flash in front is what it is then? You can see it in good lighting (moto g6). "
Response from the Motorola:
" Thanks for asking, that's interesting. The little dot on the right side part of the front flash is a sign of life LED light. It would only show/activate when the battery is deeply discharged and it's plugged into the charger. "
There is hope that in unofficial rom you will be able to use it.
Woah, woah, woah, hold up. It had an LED the entire time? So, why can't we use it? Unless it's a single color LED.
JoeGatto said:
Woah, woah, woah, hold up. It had an LED the entire time? So, why can't we use it? Unless it's a single color LED.
Click to expand...
Click to collapse
Probably all Moto G6 variants have this. Unfortunately, I can not find anywhere information whether it is a single-color LED. Motorola is pursuing a strange policy, the previous models also had a hidden diode and hardly anyone knew about it.
kemoti said:
The LED is confirmed by Motorola. I asked them a question and got an answer.
My question:
" This little dot on the right side of the flash in front is what it is then? You can see it in good lighting (moto g6). "
Response from the Motorola:
" Thanks for asking, that's interesting. The little dot on the right side part of the front flash is a sign of life LED light. It would only show/activate when the battery is deeply discharged and it's plugged into the charger. "
There is hope that in unofficial rom you will be able to use it.
Click to expand...
Click to collapse
I just saw this light turn on when I rebooted after flashing the OPW27.113-45 from this website
HTML:
https://www.getdroidtips.com/opw27-113-45-april-moto-g6-plus/#Firmware_Details
. Maybe it already works somehow in default ROM?
Controwl said:
...Maybe it already works somehow in default ROM?
Click to expand...
Click to collapse
For now I do not see newer firmware and update system for Moto G6, I do not know how it is with the Plus version. This diode is useless. You have to wait for effective solutions from unofficial developers. Probably all you need is a well-functioning root and the right application to add functionality to this diode.
EX Kernel Manager can trigger the led to do things, I have root to it works. I've got it blinking on charge and solid when done.
Bluemgt06 said:
EX Kernel Manager can trigger the led to do things, I have root to it works. I've got it blinking on charge and solid when done.
Click to expand...
Click to collapse
I can also confirm this works through EX Kernel Manager on my Moto G6 Play XT1922-7 Boost Mobile variant, I'm using the "Battery charging blink full solid full" option in the app, this is pretty neat lol! :good:
Edit: The LED is to the left of the camera on my G6 Play
Can also confirm using ex kernel manager with xt1922-7 boost variant that it does allow the led to work with charging. As well as a few other options lol just which we could choose more than one led option. Would be nice to have it for charging AND notifications lol
Maybe contacting the dev or if someone knows how that works can build an app to control it?
After installing root on my moto g6, I launched this application:
https://play.google.com/store/apps/details?id=br.com.itsmeton.motoledenabler&hl=en
https://play.google.com/store/apps/details?id=cyb.satheesh.lednotify
The diode works!
We need someone who will do a more polished application for our phones.
kemoti said:
After installing root on my moto g6, I launched this application:
https://play.google.com/store/apps/details?id=br.com.itsmeton.motoledenabler&hl=en
https://play.google.com/store/apps/details?id=cyb.satheesh.lednotify
The diode works!
We need someone who will do a more polished application for our phones.
Click to expand...
Click to collapse
We know the diode works, we already confirmed that with EX Kernel Manager.
Hi! I recently rooted my G6 Plus in order to use this charging LED. My goal is to make it blink softly when a notification arrives. I tried using Tasker according to this guide, but it didn't really work: I got it to ascend the brightness level, but it won't descend at all, even when running the second while-loop separately. After this, I can't even manage to change the brightness level until reboot. Strangely though, the script works as intended when run from adb shell. I started using "echo 1 > /sys/class/leds/charging/blink" when a notification arrives and 0 when the screen is unlocked. However, this is not ideal since the default blink is not very soft and the maximum brightness is too high. How could I make the bash script work properly in Tasker?
@pake10
You will not change the brightness or color of this diode (it's one color) so do not get tired. It's a waste of your time.
@kemoti
Thanks for answering — however, I did manage to change the brightness and make it "blink" with the script. The color can't be changed and that's okay. It seems that my problem is with Tasker since it works fine from adb Shell.
EDIT: I got it working by creating my own application, for some reason Tasker and other similar applications didn't execute the bash script properly.
hahah motorola has been putting this led on every phone i eventually had bought. the first moto g had it for notifications but g4 plus and g6 play have is as a sign of life
I got the diode working via the Resurrection Kernel when my phone is charging, but the diode is so small that you can't even see that there's anything going on. The capability is still a nice touch though.
pake10 said:
Hi! I recently rooted my G6 Plus in order to use this charging LED. My goal is to make it blink softly when a notification arrives. I tried using Tasker according to this guide, but it didn't really work: I got it to ascend the brightness level, but it won't descend at all, even when running the second while-loop separately. After this, I can't even manage to change the brightness level until reboot. Strangely though, the script works as intended when run from adb shell. I started using "echo 1 > /sys/class/leds/charging/blink" when a notification arrives and 0 when the screen is unlocked. However, this is not ideal since the default blink is not very soft and the maximum brightness is too high. How could I make the bash script work properly in Tasker?
Click to expand...
Click to collapse
Thanks--your hint worked for me!
I have a G6 with Nov , 2018 patch (OPSS27.104-92-2), I can control the LED from tasker with:
Code:
echo 1 > /sys/class/leds/charging/brightness # turn on
echo 0 > /sys/class/leds/charging/brightness # turn off
Issue:
1.Some users (like me) must have faced issue of screen ghosting or retention in which if the device is used at max brightness, they see a ghosted image on sides of their phone. (Especially visible when switching from a light theme to dark, for eg, going in chrome incognito mode you will see it)
2.Usually it happens after flashing a custom ROM or kernel.
Fix:
Method 1:
1. In case if its a custom ROM, go to Settings > Display > LiveDisplay
2. Set the Color Profile to ‘Standard'.
3. Go to color calibration setting and set the following values:
Red at 90%
Green at 90%
Blue at 90%.
4. Keep the display screen of for some time (15 min) and boom! Issue solved.
[Note: Max brightness may feel a little less than before but its still better, you will get used to it]
Method 2:
1.In case you have a custom kernel, you can refer to other threads or manually set the values of Red, Green and Blue by yourself by using a ‘Kernel Manager App'.
Just keep it at minimum than its original values.
Conclusion:
This issue is NOT a hardware issue, its a software issue that can be fixed by implementation of any following methods.
Source:
I got through some other threads of Redmi having same issue. Just the difference is in the settings I used, you can customize it as per your own will BUT make sure that the ghosting does not appear by use of that setting. If successful, you may replay
What are you talking about??
This issue is not available in Pixel exp plus pie, is this a Stock rom issue??
but i didn't experience it for whatever hours i was on stock Miui.
It is not software issue, but the low hardware quality I presume
Ravindrasan said:
What are you talking about??
This issue is not available in Pixel exp plus pie, is this a Stock rom issue??
but i didn't experience it for whatever hours i was on stock Miui.
Click to expand...
Click to collapse
It is not the case that every user will face it. In case if it occurs, you may make use of these procedures.
Mostly, if you use max brightness and switch suddenly to dark grey, you can notice it (in custom ROMs / custom kernel ).
Sent from my POCO F1 using XDA Labs
OdinDxD said:
It is not software issue, but the low hardware quality I presume
Click to expand...
Click to collapse
No it is a software issue. I am not talking about the yellow spot issue (that is hardware issue)
This one is ghosting or temporary burn in caused due to change in the default color calibration.
I faced it before but after trying the above settings, even at max brightness, the ghosting did not appear again. So it actually works.
Ghosting does not remain forever in LCD. So its not harmful to hardware in any way. (Just buggy)
Sent from my POCO F1 using XDA Labs
Devlik said:
It is not the case that every user will face it. In case if it occurs, you use make use of these procedures.
Mostly, if you use max brightness and switch suddenly to dark grey, you can notice it (in custom ROMs / custom kernel )
Sent from my POCO F1 using XDA Labs
Click to expand...
Click to collapse
What exactly will i notice, i want to know what happens??
I agree. Screen Retention or Ghosting is mostly present on other devices (I'm not talking about the Pocophone alone but on every other devices) and can be fixed via software implementations or updates. Changing color profile and/or color settings can be a solution too.
Ravindrasan said:
What exactly will i notice, i want to know what happens??
Click to expand...
Click to collapse
Umm. You can google it. For example, look at this picture: (From search result, it just occurred in dark backgrounds in my case)
Sent from my POCO F1 using XDA Labs
Devlik said:
Umm. You can google it. For example, look at this picture: (From search result, it just occurred in dark backgrounds in my case)
Sent from my POCO F1 using XDA Labs
Click to expand...
Click to collapse
Can't it be issue related to bottom bar of chrome (u said when switching to incognito mode)?
Ravindrasan said:
Can't it be issue related to bottom bar of chrome (u said when switching to incognito mode)?
Click to expand...
Click to collapse
Well it appears on every side of the screen and not just bottom. Even when I boot to twrp after being on a bright screen for long time, the status bar, some text and navigation bar appears. ... It fades away tho, not permanent as in amoled. LoL
Sent from my POCO F1 using XDA Labs
Devlik said:
Issue:
1.Some users (like me) must have faced issue of screen ghosting or retention in which if the device is used at max brightness, they see a ghosted image on sides of their phone. (Especially visible when switching from a light theme to dark, for eg, going in chrome incognito mode you will see it)
2.Usually it happens after flashing a custom ROM or kernel.
Fix:
Method 1:
1. In case if its a custom ROM, go to Settings > Display > LiveDisplay
2. Set the Color Profile to ‘Standard'.
3. Go to color calibration setting and set the following values:
Red at 90%
Green at 90%
Blue at 90%.
4. Keep the display screen of for some time (15 min) and boom! Issue solved.
[Note: Max brightness may feel a little less than before but its still better, you will get used to it]
Method 2:
1.In case you have a custom kernel, you can refer to other threads or manually set the values of Red, Green and Blue by yourself by using a ‘Kernel Manager App'.
Just keep it at minimum than its original values.
Conclusion:
This issue is NOT a hardware issue, its a software issue that can be fixed by implementation of any following methods.
Source:
I got through some other threads of Redmi having same issue. Just the difference is in the settings I used, you can customize it as per your own will BUT make sure that the ghosting does not appear by use of that setting. If successful, you may replay
Click to expand...
Click to collapse
I am neither using a custom ROM nor have done anything to change device performance.
---------- Post added at 10:04 AM ---------- Previous post was at 09:54 AM ----------
Devlik said:
Issue:
1.Some users (like me) must have faced issue of screen ghosting or retention in which if the device is used at max brightness, they see a ghosted image on sides of their phone. (Especially visible when switching from a light theme to dark, for eg, going in chrome incognito mode you will see it)
2.Usually it happens after flashing a custom ROM or kernel.
Fix:
Method 1:
1. In case if its a custom ROM, go to Settings > Display > LiveDisplay
2. Set the Color Profile to ‘Standard'.
3. Go to color calibration setting and set the following values:
Red at 90%
Green at 90%
Blue at 90%.
4. Keep the display screen of for some time (15 min) and boom! Issue solved.
[Note: Max brightness may feel a little less than before but its still better, you will get used to it]
Method 2:
1.In case you have a custom kernel, you can refer to other threads or manually set the values of Red, Green and Blue by yourself by using a ‘Kernel Manager App'.
Just keep it at minimum than its original values.
Conclusion:
This issue is NOT a hardware issue, its a software issue that can be fixed by implementation of any following methods.
Source:
I got through some other threads of Redmi having same issue. Just the difference is in the settings I used, you can customize it as per your own will BUT make sure that the ghosting does not appear by use of that setting. If successful, you may replay
Click to expand...
Click to collapse
I am neither using a custom ROM nor have done anything in past which can have these after effects. I am facing these issue or may be noticeable after the rollout of the MIUI11 ROM. So i contacted other who owns pocof1 , but their device don't have these issues. Then i contacted the service center and they reinstalled the MIUI11 but the problem persists.
So then i thinking of a screen replacement since i m on a warranty period so should i do that to solve this issue?.
Also u gave the settings to resolve the issue for a stock/CustomUI but wht for the MIUI , pls give the setting for them too.
pls answer all my queries!
Kakipa said:
I am neither using a custom ROM nor have done anything to change device performance.
---------- Post added at 10:04 AM ---------- Previous post was at 09:54 AM ----------
I am neither using a custom ROM nor have done anything in past which can have these after effects. I am facing these issue or may be noticeable after the rollout of the MIUI11 ROM. So i contacted other who owns pocof1 , but their device don't have these issues. Then i contacted the service center and they reinstalled the MIUI11 but the problem persists.
So then i thinking of a screen replacement since i m on a warranty period so should i do that to solve this issue?.
Also u gave the settings to resolve the issue for a stock/CustomUI but wht for the MIUI , pls give the setting for them too.
pls answer all my queries!
Click to expand...
Click to collapse
This reply is pretty late, sorry for that.
1.You need to be rooted.
2.Download ColorChanger app from PlayStore.
3.Give root privileges.
4.Decrease the color in Custom1/Custom2/Custom3 by long tapping to these values:
R:240
G:240
B:240
S:1.00.
5.Save it (top left corner)
Con: You need to apply this every time you boot into your device.
You can upgrade to pro and enable “Activate on boot" from app setting to make this happen automatically.
I did it but it doesn't work, I'll consider change the hole panel
Can you take a look at the attached screenshot and confirm if these values are okay. Apart from RGB values, do I need to tweak anything else? Thanks in advance.
Oh I see, I got this problem, and realize I set livedisplay profile to dynamic. I thought my screen was wore out
Devlik said:
This reply is pretty late, sorry for that.
1.You need to be rooted.
2.Download ColorChanger app from PlayStore.
3.Give root privileges.
4.Decrease the color in Custom1/Custom2/Custom3 by long tapping to these values:
R:240
G:240
B:240
S:1.00.
5.Save it (top left corner)
Con: You need to apply this every time you boot into your device.
You can upgrade to pro and enable “Activate on boot" from app setting to make this happen automatically.
Click to expand...
Click to collapse
Is it a s/w or h/w issue and if i install custom ROM(pixel experience) will that help
Kakipa said:
Is it a s/w or h/w issue and if i install custom ROM(pixel experience) will that help
Click to expand...
Click to collapse
This is a hardware problem, i tried everything and failed so i got original lcd folder replaced from the service center and now no screen retention.
I am from India itself, do you know which service center to go to? Since poco split from mi, am i in trouble or i should head to the mi service center. And my is under a warranty of 6 months and i'm in the 3rd month now....is it free or you got to pay money for the service?
Thanks in Advance.
Deleted
I solve this problem on miui oficial without root, Just applying standard contrast on screen settings.
I'm not long into the world of Xperia phones and find the display settings quiet overwhelming. Actually I stick with the creator mode but the colors looking washed out.
Can someone give advice for a good setting?
Much thanks.
I had the observation as you. Switched back to standard mode. Thought the creator mode will give better color but somehow didn't look that way.
I also asked the question in the Xperia subreddit. Someone wrote a setting to test. In the display settings toggle standard mode and the white values with manuel settings as follows: Red 66, green 39 and blue 0. So far it looks really good and I stick with this until someone comes with a better setting. You can try this and would like to see a feedback from you.
T3chDelicious said:
I also asked the question in the Xperia subreddit. Someone wrote a setting to test. In the display settings toggle standard mode and the white values with manuel settings as follows: Red 66, green 39 and blue 0. So far it looks really good and I stick with this until someone comes with a better setting. You can try this and would like to see a feedback from you.
Click to expand...
Click to collapse
Tried this. It does look better. Black is darker. I will stick to this setting for now as well. Thanks.