Got fed up with the lack information so I did some googling and made a post on my blog.
My Bloggy
If anyone has any good links or info to add that would be greatly appreciated! I'm still personally trying to find my own settings.
The Automatic Backlight settings (CyanogenMod settings-->Display-->Automatic Backlight) allow you to customize how your phone reacts to changes in ambient light measured by the phone. You can control how many light level ranges you want to monitor, and how bright you want the screen, keys, and keyboard buttons to be at each range. Of course you have to enable Automatic Backlight in the normal Android settings first (Display-->Brightness).
In googling around on this I've found a number of different approaches and preferences, and it really is something that is very subjective - enough light for one person at a particular ambient light level is too much for another, and vice versa.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The first three settings: Windows length, Reset threshold and Sample interval control the filter conditions. The Windows length is the amount of time for the average figure, while the Sample interval is how long the system waits to take a sample. Personally, I go with larger figures to reduce system load and save battery life.
There are two primary benefits offered by filtering:
1. It can allow you to set up smoother brightness transitions (assuming you also increase the number of custom levels)
2. It can decrease the likelihood of screen flicker in mixed lighting. ( You may find yourself in mixed lighting conditions that straddle two raw brightness levels. Without filtering, these raw levels may cause your screen to repeatedly shift back and forth between two brightness settings. I've found this can easily happen with artificial lighting as it is more directional than natural lighting. Sitting in your office, for example, you may find that simply shifting the angle at which you hold the phone changes the brightness reading.)
Notice that without filtering, the screen brightness jumps back and forth between 70 and 55, which can be very distracting. The filter, on the other hand, maintains a single value for the screen brightness, even under these fluctuating lighting conditions.
Window Length: Filtered value is the average sensor value during this period. Larger values = slow response.
Reset Threshold: There may be times in which you want the screen to respond quickly to changes rather than slowly ramping. Moving from a dark building out in to broad daylight, for example, you don't want to watch your screen slowly brighten over the course of 30 seconds: those are 30 seconds in which your phone may be unreadable. This is where the reset threshold comes in handy. If a raw reading differs from your current average by this amount, the filtered value is immediately reset to the raw value. Finding the right value for your reset threshold allows you the best of both worlds: a screen that gradually changes based on subtle light changes, but responds rapidly to extreme changes.
Sample Interval: Low value can improve accuracy but uses some more CPU.
Allow Light to Decrease: This is a very simple option. If this is checked, your screen brightness will increase and decrease according to your custom levels. If it is unchecked, your screen will brighten as the light sensor reads higher values, but will never darken, even if the sensor detects that you have moved to a very dark area. I'm not quire sure why anyone would want to uncheck this, but maybe I'm missing something.
Decrease Hysteresis: Reduces flicker when decreasing brightness
In conclusion, if you want a screen that responds very rapidly to changes in ambient lighting, possibly at the risk of flickering, decrease your filter window (or disable the filter completely) and increase your sample interval. If you want a screen that never flickers, possibly at the risk of slow responsiveness, increase your window.
Filter A: 10 second window, 2 second interval
Filter B: 20 second window, 2 second interval
Filter C: 30 second window, 2 second interval
Filter D: Same as Filter C, but includes a reset threshold of 2000
*Note how the inclusion of a reset threshold on Filter D allows for immediate responsiveness under extreme light changes while still preserving the gradual shifts at smaller changes.
As for the light sensor levels, you'll have to play with them yourself. Go to a dark area... and adjust the screen level until it's at a brightness that's comfortable for you. Then gradually increase it up to whatever is fine for outside brightness. Near the bottom you can select more levels as well.
As previously said, I mainly want to collaborate and find the best settings for our phone. Any information to add would be great. Thanks.
Sources:
Numerical explanation of the CM7 automatic backlight settings
CyanogenMod Secrets: Custom Automatic Backlight settings
Very detailed explanation, should be pinned and include in the CM wiki if not already done so!
Thanks!
Sent from my Xoom using Tapatalk 2
Thank you so much for the detailed overview. Very well done. Agreed...should be stickied.
How about you post your settings?
Excellent post. Needs to be a sticky.
And for those that are curious these ROMs (likely others) have the same implementation:
-AOKP,
-Gummy,
-Slim,
-???
CMNein said:
And for those that are curious these ROMs (likely others) have the same implementation:
-AOKP,
-Gummy,
-Slim,
-???
Click to expand...
Click to collapse
liquid
Sent from my Galaxy Nexus using XDA
emd2009 said:
How about you post your settings?
Click to expand...
Click to collapse
+1
Sent from my Galaxy Nexus using xda premium
s4vva said:
Excellent post. Needs to be a sticky.
Click to expand...
Click to collapse
This isn't really my work so I don't think it should be stickied. I just found some old posts and read **** on the internet. lol
wow first time i read this 3ad..very usefull.i always have some doubt about how it works the automatic backlight settings..honestly i have always the phone to max brightness,but now i want to know better how it works this features.thanks for the wonderfull 3ad.
Related
On my E4GT, when I turn the display brightness really low with my ScreenDim app, and then look at something (e.g., a PDF file) which fills the screen with a white background (and black text), while being in a dark room, I can see that the middle third of the screen is slightly pinkish, forming a pinkish vertical stripe, instead of white.
Does anyone else have the issue? If you want to try to see if yours has the issue, you can use ScreenFilter and turn the brightness really low, or you can use the free ScreenDim Trial and set to 25% or a bit lower (in Easy Mode). I'm wondering if I should return the phone to the store, or if they're all like this.
Does the lack of replies mean that I am the only one having the problem?
arpruss said:
Does the lack of replies mean that I am the only one having the problem?
Click to expand...
Click to collapse
LOL, good for you for being persistent AR.
I tested this for you on mine and I'd say mine is a little over half on the left side as what you described.
Edit: Title is a little misleading but your initial comment about the whole left side of the screen seems to be correct.
Sounds like a symptom of the application. I have not seen a single et4g with a pink line/screen come through my service and repair centers.
eeeeeeeeek said:
Sounds like a symptom of the application. I have not seen a single et4g with a pink line/screen come through my service and repair centers.
Click to expand...
Click to collapse
This is something you wouldn't normally see in a stock scenario. The lighting app allows for drawing the screen down below 25% and the discoloration is very faint. I wouldn't probably have even noticed it unless I was asked specifically to look for it.
I don't think AR was pointing it out as a problem. He was probably just curious if anyone else could duplicate it using the same setup (well, and to make sure he wasn't really having an issue too I suppose ).
ee[LEFT said:
[/LEFT]eeeeeeek;26299088]Sounds like a symptom of the application. I have not seen a single et4g with a pink line/screen come through my service and repair centers.
Click to expand...
Click to collapse
No, I don't think it's a software problem. The app lowers screen brightness to the lowest level allowed by the OS and then draws a light gray overlay over the screen. The device isn't rooted and the app uses standard documented apis. None of this should produce a nonuniform effect like this stripe. In theory, the same issue should come up if one turns the brightness to a minimum with the OS settings and them loads a light gray image. I'll see if I can produce it.
Also, you only see the effect well if you are in a quite dark room. But since I like to read in the dark, this matters to me. If all units have this, I'll live with it. But if it's only mine, I want it to be fixed.
This issue is one of the reasons I haven't rooted: I may need to return the unit.
You are right. I would want to know if it is my phone or not before I make a decision to have it replaced. What if the replacement phone not only has the same issue, but a couple of new ones as well?
Here's a test that doesn't require any special app.
Turn off automatic brightness and set brightness to minimum.
Then view this test image with the browser
http://pruss.mobi/test/A0.jpg
Zoom until it fills the screen. Go into a dark closet or other windowless room without lights. View the screen from different angles. To me, the discoloration is most visible if I view it in portrait mode, straight on. It disappears if I tilt the screen side-to-side a bit. Here is an attached copy:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here are some other test images. For me, the above one showed the discoloration best, but it might be different for different people.
http://pruss.mobi/test/70.jpg
http://pruss.mobi/test/80.jpg
http://pruss.mobi/test/90.jpg
http://pruss.mobi/test/B0.jpg
http://pruss.mobi/test/C0.jpg
http://pruss.mobi/test/D0.jpg
http://pruss.mobi/test/E0.jpg
The images are all solid gray.
Here's a QR code for the A0 image:
Hi AR. I tried it out again but I still do not have a line down the screen. I tried several screen brightness levels all the way to 0% where I could barely see the grey and still no line for me. Hope this helps and hopefully someone else will try it for you too.
tdunham said:
Hi AR. I tried it out again but I still do not have a line down the screen. I tried several screen brightness levels all the way to 0% where I could barely see the grey and still no line for me. Hope this helps and hopefully someone else will try it for you too.
Click to expand...
Click to collapse
The other issue my screen has is that if I view a 100% black image, and go into a very dark area (when I tested this most thoroughly, I was in a closed, windowless garage at night), and let my eyes get adjusted to the dark, eventually (after a bit of dark adaptation) I see an gray glow from the screen, with many irregular small patches that are completely black peeking out of the grayness. This is a very small aberration, but it is noticeable when outside at night running an astronomy app.
Interestingly, after a couple of months the problem seems to have decreased. Or my brain is screening it out.
Compared to my N4, the screen has deeper blacks, but in a very bad way. You lose so much detail on some pictures, even at full brightness. Like with a picture of black fur my N4 will show all the nuances and shadows caused by the fur, but the Sony will just be pitch black. The amount of detail is pretty significant. Overall, the tone of the screen is just darker, and it kind of makes you sad using it.
I have the same opinion, this is the most annoying thing on this phone. I had very strong feeling to return it back to the shop.
Any solution for this? I can increase screen backlight, but it is not ideal solution and it does not solve the problem.
toiletsss said:
Like with a picture of black fur my N4 will show all the nuances and shadows caused by the fur
Click to expand...
Click to collapse
Upload the picture please.
Yes, blacks are heavily crushed on this device. Here's an earlier discussion of it with links to calibration testers:
http://forum.xda-developers.com/showthread.php?t=2646749
See Erica Griffin's mini review where she discusses the calibration problems and charts the wonky gamma levels here:
http://www.youtube.com/watch?v=a7tQ5n32no8#t=564
If you don't want to install the Display Tester app, here's a link to a black level test image for viewing in your phone browser:
http://www.lagom.nl/lcd-test/black.php
Ideally all of the black squares should be distinguishable to ensure proper reproduction of detail in shadowed areas of an image or video. With Nexus 5, for instance, squares are distingushable from square 2/3 upward.
For Sony Z1 Compact with JDI panel, squares are distinguishable only from square 7 upward. Result: all black levels below 7 look the same on the Z1C, meaning no detail can be distinguished at these levels. One consequence is that low light photos look very inaccurate compared to how they'll look on other displays - if you share or edit them, for example.
I have exactly the same feeling, im from a nexus 4 too and i try to watch some movies on my Z1C and the contraste is juste horrible.
Any ideas on how to fix this?
when its bright ppl say " zomg its wash out"
when black then complain too black
xerox89 said:
when its bright ppl say " zomg its wash out"
when black then complain too black
Click to expand...
Click to collapse
This has nothing at all to do with the brightness of the black levels. This is about how many black levels can actually be seen with this screen. And yes, this is a legitimate complaint.
ghtop said:
This has nothing at all to do with the brightness of the black levels. This is about how many black levels can actually be seen with this screen. And yes, this is a legitimate complaint.
Click to expand...
Click to collapse
This exactly. And thank you for your previous post, it was extremely informative. I was really hoping I just had a faulty screen because I love the phone otherwise. I really love sony's products but the screens on the Z1, Z1s, and Z1c have all been problematic, particularly in dealing with blacks and whites. I really hope these problems are addressed in the Z2 because I really need a replacement for this N4.
Edit: So this affects JDI panels too? From what I read, the JDI panel is much better than the AUO panels.
This is mine, JDI panel...
Using the website...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ghtop said:
With Nexus 5, for instance, squares are distingushable from square 3 upward.
Click to expand...
Click to collapse
Using the app...
Heh, remember that there's little point taking a screenshot for comparison unless 1) you shoot it with a camera that has accurate black levels 2) you view it on a screen that has accurate black levels. Otherwise we're all just looking at different things.
Useful info to share in this thread would be how many black levels from that test page you can actually see on your screen (i.e. the number of the last square you can distinguish from another).
ghtop said:
Useful info to share in this thread would be how many black levels from that test page you can actually see on your screen (i.e. the number of the last square you can distinguish from another).
Click to expand...
Click to collapse
I can see from square 7 using the app and the website.
XperienceD said:
I can see from square 7 using the app and the website.
Click to expand...
Click to collapse
Edit: Argh, sorry, my mistake, it should have been 7 instead of 13, as stated in the original thread - corrected now. You can only really see those levels at full brightness in a dark room, though. More detail is lost at normal brightness levels where you aren't being blinded by the whites.
Have to agree, black levels are way too dark. You lose loads of detail in any dark scene, video and photos. Also gamma levels are far too low, at about 1.6 across the board. They should be around 2.2. I'm coming from a galaxy s2 which now seems to have more accurate colour reproduction. Which is disappointing considering it's a super amoled screen vs an ips panel.
Sent from my D5503 using XDA Premium 4 mobile app
There is very simple workaroud for this . Install "Screen Adjuster" app from Google Play, open it, set Contrast value to ca "-30", switch "Adjuster OFF" to "ON" and voila, now you can see black levels up to 1 otherwise, I'm able to clearly recognize only values up to 7 on full brightness on 4.4.2 latest FW .757 with JDI panel using Color Test app
Screen Adjuster: https://play.google.com/store/apps/details?id=com.netmanslab.sa
source: http://forum.xperia.cz/viewtopic.php?f=85&t=9946&p=163390
pcpepik said:
There is very simple workaroud for this . Install "Screen Adjuster" app from Google Play, open it, set Contrast value to ca "-30", switch "Adjuster OFF" to "ON" and voila, now you can see black levels up to 1 otherwise, I'm able to clearly recognize only values up to 7 on full brightness on 4.4.2 latest FW .757 with JDI panel using Color Test app
Screen Adjuster: https://play.google.com/store/apps/details?id=com.netmanslab.sa
source: http://forum.xperia.cz/viewtopic.php?f=85&t=9946&p=163390
Click to expand...
Click to collapse
Excellent, excellent post! Thank you so much for this. It definitely works!
pcpepik said:
There is very simple workaroud for this . Install "Screen Adjuster" app from Google Play, open it, set Contrast value to ca "-30", switch "Adjuster OFF" to "ON" and voila, now you can see black levels up to 1 otherwise, I'm able to clearly recognize only values up to 7 on full brightness on 4.4.2 latest FW .757 with JDI panel using Color Test app
Screen Adjuster: https://play.google.com/store/apps/details?id=com.netmanslab.sa
source: http://forum.xperia.cz/viewtopic.php?f=85&t=9946&p=163390
Click to expand...
Click to collapse
Wish I saw this earlier. Might have to buy it again. Can anybody show examples with dark, detailed photos?
toiletsss said:
Wish I saw this earlier. Might have to buy it again. Can anybody show examples with dark, detailed photos?
Click to expand...
Click to collapse
I just wonder why the hell the Screen adjuster needs full network access, view my network connections, reads precise position GPS, needs access to my bookmarks and history, read the device accounts... Why ? I prefer that sony will modify the contrast in next firmware...
fidel73 said:
I just wonder why the hell the Screen adjuster needs full network access, view my network connections, reads precise position GPS, needs access to my bookmarks and history, read the device accounts... Why ? I prefer that sony will modify the contrast in next firmware...
Click to expand...
Click to collapse
And use 20% of my batteries...
Excellent. I can now see it from box 1. Not sure about battery draining though. So disabling the app for now and waiting for an actual fix in the next release. For some reason, I am very happy that it's a bug in the configuration settings and not an actual hardware issue. Sony has again succeeded in screwing their awesome specs with a ****ty software.
fidel73 said:
I just wonder why the hell the Screen adjuster needs full network access, view my network connections, reads precise position GPS, needs access to my bookmarks and history, read the device accounts... Why ? I prefer that sony will modify the contrast in next firmware...
Click to expand...
Click to collapse
It's ad-ridden, but there is a cheap paid version that requires only the essential draw over other apps permission and does not drain battery
What is PWM?
Pulse Width modulation (PWM) is a way to control display brightness.
When you lower the brightness, the light intensity of the display is not reduced by voltage, but instead quickly turned off and on by the electronics with a fixed frequency.
If this frequency is high enough (>4000hz), it is indistinguishable by the human eye.
Why is Samsung AMOLED using PWM?
AMOLED can't be dimmed low enough (<40cd/m2) by just reducing voltage without noticeable image deterioration.
This deterioration affects grayscale linearity, color temperature and shows another display issue called mura defects.
Grayscale linearity and color temperature can be corrected to some extent by the display driver.
But mura defects are basically small irregularities / deviations caused by the OLED production process and will become more visible with lesser voltage applied.
PWM can prevent those issues by dimming the brightness with short on/off intervals instead of voltage dimming, thus the applied voltage can be high enough (~100cd/m2) to avoid optical deterioration and we still perceive a lower brightness.
What is the problem with PWM?
PWM is not bad per se, it is the very low frequency of 240hz that Samsung chooses to implement.
Some people that are very susceptible to flickering (often without knowing it), may notice eye strain, headache or even nausea (comparable with motion sickness).
This is also the reason why almost all modern computer displays are assembled with a flickerfree backlight.
Oscilloscope measurements
Default kernel PWM behaviour with 240hz (10% on-time and 90% off-time ratio).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flickerfree kernel with a more consistent amplitude (note: the 60hz refresh interval is intended).
Kernel PWM comparison
Default kernel.
Flickerfree kernel.
PWM visualized in slow motion
Both videos are starting at 100% brightness -> 60% -> 20% -> 5%.
Left video: stock kernel, right video: flickerfree kernel (the pink stripe is the refresh interval).
Disadvantages
If the brightness is below 40cd/m2 the visibility of the above mentioned mura defects will increase.
Download:
flickerfree_dream2lte.zip
Credits:
Kernel Source by Samsung
Vendor libraries from Renovate
Exynos DTBH from jcadduono
ixbt.com review
laptopmedia.com review
Source:
kernel_samsung_dream2lte
The refresh interval (Vsync) seems like a necessary OLED function, as it is also used by LG OLED PWM free devices Flex 2 (60hz) and B6 (120hz):
ixbt.com
rtings.com
It is a pleasure to see around again, mate. Your work has always been an inspiration.
Hi, please
work with oreo?
Hi
Thanks for your work. I have been looking for this and its great to have it.
I have flashed it but the phone is stuck at Samsung logo. It doest boot. Please can you help me. I have a dual dim unlocked INS phone and am on latest Ironman RoM.
Edit: flashed v2 it is stuck at installing android app 39 to 56.
@neitin
This seems like a problem with mismatching vendor libraries, i use the Kernel with the current stock Samsung firmware (G955FXXU1AQK7).
I will later take a look what might cause this issue on the custom rom.
does it work on AQH3 ?
Wootever said:
@neitin
This seems like a problem with mismatching vendor libraries, i use the Kernel with the current stock Samsung firmware (G955FXXU1AQK7).
I will later take a look what might cause this issue on the custom rom.
Click to expand...
Click to collapse
Hi Wootever, please can i ask you to let me know which RoM are using, I flashed Batman rom with stock kernel and flashed your kernel, but failed, tried on ironman rom with stock kernel in aroma and it fails to boot.
Thanks in advance.
@neitin
I'm using the current default Samsung rom (G955FXXU1AQK7), it can be downloaded with SamFirm.
Edit:
Region codes can be found here.
If you decide to flash the stock Samsung rom via Odin, don't forget to create a backup of your /data and /sdcard partition to an external card as the original boot.img will encrypt those partitions.
Thanks @Wootever
I was on RpmAur-2.1 and flashed the kernel, all works well and I can proudly say that my eyes are not burning as it used to earlier.
Thank you for your work, Cheers
Don't boot, stay in Samsung logo
Renovate AQK7 + Firmware AQK7
jujusito said:
Don't boot, stay in Samsung logo
Renovate AQK7 + Firmware AQK7
Click to expand...
Click to collapse
I had the same issue. Refer couple of post above for resolution
Sent from my SM-G955F using Tapatalk
I made some adjustments to retain the calibration and overall image quality, it should be pretty much identical with the stock kernel now.
The difference is basically the increased visibility of mura defects without PWM (flickerfree kernel behaviour) or almost no visible mura defects with PWM enabled (stock kernel behaviour).
Here is a quick comparison photo:
(Stock kernel is on the left side; if you look closely you can see the some repeating transversal lines, those are the typical PWM lines captured by camera.)
(Flickerfree kernel is on the right side; there are some bright dots that looks like compression artifacts, those are mura defects.)
Edit:
Here is another photo for a better comparison (left side: mura defects masked by PWM, right side: visible mura defects due to missing PWM).
(Note: those mura defects are especially visible on very low brightness <20cd/m2, anything above 40cd/m2 shouldn't be noticeable).
More information about can be found in the Samsung AMOLED patent description: Organic light emitting display device and driving method thereof
neitin said:
I had the same issue. Refer couple of post above for resolution
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
If the solution is flashing stock rom with odin i don't want this.
This kernel need more compatibility with custom roms, v3 and v4.
Don't work for me, stay in Samsung logo when boot.
Welcome aboard sir! I was just curious about this kernel last night. Was thinking to myself, I miss the flicker kernel for the edge and was going to seek you out to see about a port but looks like its an early Christmas for me
jujusito said:
If the solution is flashing stock rom with odin i don't want this.
This kernel need more compatibility with custom roms, v3 and v4.
Don't work for me, stay in Samsung logo when boot.
Click to expand...
Click to collapse
Just an heads up I have tested on Batman Rom and it works flawlessly.
Sent from my SM-G955F using Tapatalk
Nice to see this on S8 source
Can we still toggle it via echo 0 / echo 1 ?
I added the flickerfree setting to the S8 (G950F) panel driver. If someone is willing to test this version please report back if it's working correctly.
flickerfree_dreamlte.zip
(note: for now the lowest brightness step is set much higher (300cd/m2) to verify that the flickerfree brightness table is working.)
@djb77
Not yet, but i might add that in a future version.
Wootever said:
I added the flickerfree setting to the S8 (G950F) panel driver. If someone is willing to test this version please report back if it's working correctly.
flickerfree_dreamlte.zip
(note: for now the lowest brightness step is set much higher (300cd/m2) to verify that the flickerfree brightness table is working.)
@djb77
Not yet, but i might add that in a future version.
Click to expand...
Click to collapse
I've been speaking with @morogoku (author of MTweaks) about it. We may even able to patch it to make it work.
I'll have a look at both sources today (hero and dream) and see what I can do.
I've noticed the changes in the hero code which check for the 0 or 1 o be enabled, doesn't look too complicated, but ofcourse if you do have time it would be appreciated if you can do it yourself to make sure its 100% correct.
Once again thanks for supporting the S8 with this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Video showcase https://streamable.com/friseg
Shot by @Serial Kazama.
Similar to this or a shine effect only around camera or tens of other styles can be used to indicate an event such as charging, music playing or a notification to help you to know even who texted you just by a glance far from your phone.
some of you may know this app before and some may had struggled with it in its bad moment with a broken version but it did not stop improving and all got fixed and many more feature added.
Because this app has tons of options to customize your phone, even wallpapers, I will start by writing instructions for how to enable the basic options of the feature which this thread is about:
How To:
1- Search google play "AOE" or "Always On Edge" and install this ~6MB App
2- Enter section #1 "Main Settings"
choose if you want the LED effect to be shown within System Ambient Display or a separated screen
3- enable accessibility services and give required permissions
4- Go back and enter section #2 "App settings"
for when to light choose "when a notification comes" and/or charging lighting as you like
5- scroll to bottom and save.
6- Enter enabled apps section and make sure the app you will test with is enabled
https://play.google.com/store/apps/details?id=com.used.aoe
Please give the app some time only once and then you will not need to even open it:
After testing please discover all sections the app can do what ever you need for such feature
like at the same place of step 4 you can enable Mixer which show all current notifications colors
and Reminder which repeat lighting every X seconds and let other options you may like.
in lighting settings section you can customize the general style of lighting.
the app is indeed complicated due to variety of options and I'm always working on improving it.
Battery Drain:
I use it personally for notifications only, all apps, while screen is on and off, reminder for 5 seconds every 5 seconds limited to 30 repeat and I got 100s of emails and messages and the app is not even on system battery use list. but in general this app can be used with no noticeable difference in battery usage and it can drain your battery in few hours. it depends on the options you choose, there are a lot of options to minimize battery consuming it basically depends on lighting time and enabled widgets.
in worst cases there is options to prevent the app from working if device is not charging and other 10s of options so you can set when the app should not light as when the app should light.
App brief description:
AOE contain a lot of features and options and all can be customized as you like, here is some of the main features:
Edge lighting can also be customized for charging, music, wallpaper and many other events
It can be customized to work in a highly flexible way with AOD clock or independently, or even both like Tap to Light feature.
Lighting can be around all screen or around front camera or both with many other lighting place options like LED style with variety of animations.
You can use it to show lighting effects for many events like notifications including missed calls of course, charging, fully charged, screen lock, screen unlock, headset plugged, listening to music ,
ongoing or outgoing calls, recent apps menu and flash after unlock.
You can customize lighting color, style, effect and place for each event, each app, each contact name or even each chat group.
Notifications light has more useful additional features like Reminder which the lighting will be repeated every period you choose and you can even choose to make a sound alert for notification reminder,
and Mixer which will iterate through all current notifications colors..
Brightness can be adjusted regardless of the lighting is independent or with Always On Display, on top of that you can set high brightness for lights and low brighting for AOD/clock widgets.
It has many options to restrict its job like prevent the app from lighting if device is charging, not charging, not in landscape mode, low battery, sleep time or to follow Do Not Disturb mode.
with a block list to prevent it from working for someone
AOE also support lighting in all screen states, turned off or turned on, horizontal or vertical.
Click to expand...
Click to collapse
Pretty cool! I didn't know about this app so thanks for sharing! Anyone else have any cool mods or recommendations for settings?
Awesome. Could you add the settings you use to center it on the hole? I'm getting there but just be nice as a starting point then could adjust thickness to taste . Thanks again! So cool. Takes me to back to OMG! NEXUS HAS A NOTIFICATION LED.
@
letrain02
sorry I do not have a pixel but automatic adjustment should be fine initially (is not it?) then click preview and adjust manually a little bit using -+ buttons
Already paid for the Lifetime. This works really well!
letrain02 said:
Awesome. Could you add the settings you use to center it on the hole?
Click to expand...
Click to collapse
This is as close as I could get it to center.
That's seems different from mine. By 10+ on some. I wonder how much the display size setting effect it. Thank you for the starting point.
I managed to use this app but everytime I got a new message after a restart, the app just don't work, does anybody knows a workaround? or it's just me not having a correct config?
seems gone from the playstore
GintoSama said:
seems gone from the playstore
Click to expand...
Click to collapse
Yeah, unfortunately. I just discovered it yesterday so I installed it from here. https://www.apkmirror.com/apk/alrbea-ent/always-on-edge-edge-lighting-/
But I also wanted to unlock all features by buying pro and that seems not to work without PlayStore
Anyone knows if is possible change resolution in adb? Or someting
Pretty sure you used to be able to use the following command
For resolution:
adb shell wm size 1080x1920
For screen density:
adb shell wm density 390
Obviously adjust numbers to suit your needs.
I accept no responsibility for any issues which may occur if you use these commands
Edit:
Did a quick bit of googling and found this which echos the above:
https://www.reddit.com/r/pokemongodev/comments/6554k1/_/dgfpesr
I know this is quite an old post, but couldn't find a newer one mentioning if changing screen res works. Did these commands worked fine with the 6 pro? And is there any noticable difference in battery life/performance if it does work?
I'm interested too. Give it a shot and report back on the results? I'm in the car all day, otherwise I would
There is also the "smallest width" setting under the developers options menu. I set mine to 720 for higher resolution.
B from C said:
There is also the "smallest width" setting under the developers options menu. I set mine to 720 for higher resolution.
Click to expand...
Click to collapse
I just tried that and needed to pull out my magnifying glass lol. Everything was so small!!
I've got mine at 474 with font set to large... happy medium for me
Gave it a try just now and it does work, however definitely not what I expected. Basically adds 2 huge top/bottomn notches and brings your rendered screen in the middle. Bottom gestures are almost impossible, as you have to start somewhere middle in the screen. And for unlocking the device - now you need 2 fingers - one to trigger the FP scanner because it ends up in the bottom right and one on the actual Scanner. Also you end up with a weirdly placed camera cutout that you cant remove.
I might try to run my phone like this for a day, as I wanted to experiment how the battery behaves. Menus seems really fast and smooth, but can be because the animations have less space and are shorter . If anyone has an idea for a command to stretch the screen over the whole display, I'd love to try.
Edit: Never mind, dumb me didnt adjust for screen ratio not being what I'm used to. After taking that into account 1080x2340 works. Fingerprint and camera cutout issues still persist though.
While this may be a little small/sharp for some people, I've been running "Smallest Width" at 720, which seems to yield a "Display Size" of 320dpi, along with default font size for awhile and have had no issues with the camera cutout or the fingerprint reader. I also use the AOD Notify app to put a glowing ring around the camera and didnt need to make any offsets so I'm pretty sure my camera cutout is where it's supposed to be.
I ran 320dpi/720width for years on a few Samsung Note devices prior to my P6P so that's what I'm used to (I'm one of those people who run a 4k tv as a monitor with no scaling). You may need to play with different dpi and font combinations until you find something you are comfortable with. In rare situations I have needed to restart the device or clear the cache for all UI elements to resize correctly after a change.
After a couple days of testing (it did indeed took me 2 days to kill my phone) I figured that for whatever reason, on the Pixel (maybe exynos) lowering the render res does indeed save some battery. On 1080p I managed to get around 1%/h - 2%/h less consumption on Screen on Time, which for people like me who manage to get 5+ hours of screen on time can result in quite of a difference. I regularly end days with something between 30-40% battery, which is still really good but I won't go to a second day as the 2 hours charge time is really annoying me .
With the lower resolution I ended the first day with 57% and I ended up with 37.5 hours of standby and 8 hours and 40 min of SoT in a full charge. I even went further by reducing the resolution to 720p, but it is really obvious that Google never made a 720p phone - almost all UI's broke and even changing the brightness was a hassle. I also believe that it might have triggered some rouge process as my phone lost 10% battery in less than an hour, so I switched back to my original 1440p.
To conclude this - is changing your resolution to 1080p worth the broken finger print - depends. In my example, I would probably do it if I know I am going on a trip where lots of pics/videos will be taken and heavy navigation use, as my phone is more of a tool in cases like that and I always try to squeeze every bit of battery I can. If google does implement the ability to change the res though - I would definitely switch.
I just wonder, why does it made such a big difference on this phone, but it didnt for S10(the only battery test I found on a video). Is Android 12 harder to drive? Or are these LTPO panels more intense on the GPU? Or is it even exynos/mali GPU not as efficient as SD on rendering UIs? If anyone wants to chime in - Id' be glad to hear some opinions. ( Or maybe I just used my phone less.. that would be the worst )
P.S. Just to say this was done on 60hz and that your milage might vary, if you decide to try. Everyone's usage is different and in my case I work from home - so WiFi connection (although router is far) but horrible signal, as I am a top flat in the UK (worst case scenario). The setting I used for the adb command is 1080x2340 and denstity was 400, although density is preference I guess and I believe wont affect battery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yessss... I changed it... All. Works
Download app easy dpi changer from playstore
Easy DPI Changer [Root] - Apps on Google Play
Make your screen yours
play.google.com
And set this value
Need root
If want to stock values only tap to reset and all come back to stock value
liver20 said:
Yessss... I changed it... All. Works
Download app easy dpi changer from playstore
Easy DPI Changer [Root] - Apps on Google Play
Make your screen yours
play.google.com
And set this value
Need root
If want to stock values only tap to reset and all come back to stock value
Click to expand...
Click to collapse
For what it's worth, with Android 13 Stable and the Kirisakura custom kernel, you can now change to 1080p from Android settings.
XDA Article: Google Pixel 6 Pro gains 1080p support thanks to Android 13 and a custom kernel
roirraW edor ehT said:
For what it's worth, with Android 13 Stable and the Kirisakura custom kernel, you can now change to 1080p from Android settings.
XDA Article: Google Pixel 6 Pro gains 1080p support thanks to Android 13 and a custom kernel
Click to expand...
Click to collapse
And doesn't break the fingerprint scanner like Easy DPI changer does
There must be a way of doing it without opening the bootloader, right? Or do you guys think it's impossible without breaking stuff like the fp scanner? I'd love to lower my resolution but I really didn't want to lose all my stuff and have to reinstall everything at this moment.
Another method to adjust screen resolution/size/dpi: I noticed the "AOSP Mods" module for LSposed/Magisk has an option in the "Miscellaneous" section for "Display resolution". The slider does work and changes the resolution on my P6P without modifying the smallest width developer setting. YMMV
forum link
B from C said:
Another method to adjust screen resolution/size/dpi: I noticed the "AOSP Mods" module for LSposed/Magisk has an option in the "Miscellaneous" section for "Display resolution". The slider does work and changes the resolution on my P6P without modifying the smallest width developer setting. YMMV
forum link
Click to expand...
Click to collapse
Thanks a million for this. The module fixed my screen flickering - couldn't go over approx 50% without flicker . I set the screen brightness from within Miscellaneous. Only problem is that I can't access Miscellaneous again without module force closing (other options are fine) - looking into the reason for it.