Update: While GalacticNight is still available for older devices, if you have a newer device it probably won't work. But if you have Android 4.4 or higher, my new Color Changer app may work for you and will do everything GalacticNight did (but alas at a higher software level). I am therefore discontinuing work on GalacticNight.
Edited: Now in Google Play.
Galactic Night, now in the 0.99rc2 version, provides red, green or sepia (or blue if you really want!) night modes for rooted OLED Galaxy S2, S3 and Note 1 devices (not tested on Galaxy 7.7 but might work). You can invert the screen colors (so you can browse in white on black, or green on black, or red on black). There is also an Outdoor mode which washes out the colors but might improve legibility outdoors.
I like reading ebooks in green on black when in the dark.
As of my present knowledge, various pre-release versions of this have been tested on:
Galaxy S2: Gingerbread and ICS
Galaxy S3: ICS
Galaxy Note: JB
It should work on ICS on the Note as well, but I don't have any reports. GN works by adjusting the mDNIe profile. If you have some Samsung device I haven't heard of which has a Screen Mode setting in the Display settings that includes Dynamic/Normal/Movie options (and maybe others), there is a chance that this will work for you.
My benchmarking has not shown any statistically significant impact on graphics rendering speed.
Use at your own risk. If a mode screws up the screen display, you should be able to get back to normal by pressing "Standard" or rebooting, but I offer no guarantees.
Several users have asked for customizable settings. These could easily be provided, and could adjust for screen color tint and so on, but I haven't implemented them yet. I might in fact leave those for a Pro version.
You might be curious how the nightmode differs from that in ChainFire3D. ChainFire3D's nightmode works by dropping channels. E.g., in red mode, it simply drops the green and blue channels. This means that things on screen that were in pure green or pure blue get changed to black. Galactic Night uses a different color adjustment which is equivalent to this algorithm: first convert the RGB color on the screen to a luminosity, and then use the luminosity to set the night mode color. Thus, in red mode, pure white will go to maximum brightness red, but red, green and blue will go to different shades of red. This preserves a lot of the legibility.
There is also an odd "No blue" mode which converts RGB images to RG images, so white goes to yellow, blue goes to a dark yellow, etc. I've heard that blue light makes it harder to fall asleep, so it might help with falling asleep if you switch your phone to "No blue" mode for an hour before going to bed, if you can tolerate how ugly it looks.
Here is a photo of GN in action. It is not possible to take a screenshot of it in action, because the color changing is done between framebuffer and display, so the framebuffer that the screenshot accesses will not reflect the color changes.
I've already posted about this in a few device-specific forums, but now it's ready for wider dissemination.
{
"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"
}
Let me add that the green mode should nicely help save batteries. Using just the green subpixels should use about 1/3 of the power, and yet maintain a lot of visibility because our eyes are very sensitive to green light.
Users report that on ICS there is a 1/2 second flash of the regular colors when you turn the screen on. In 0.99rc3 I implemented a red-and-black logo overlay that should cover up most of that flash (it doesn't cover up the status bar, alas). I can imagine it would be really annoying to be in the dark and get a flash of white light even for half a second.
Reports would be appreciated.
If the logo annoys, you can turn it off in GN's settings.
Great app. Works well. Having no trouble with the logo for screen on.
I'm not sure how difficult this would be to implement, but it would be useful to have a tasker plugin so that red mode could be activated when you run certain apps or at specific times of day.
Keep up the good work.
Sent from my GT-I9100 using xda app-developers app
arpruss said:
Let me add that the green mode should nicely help save batteries. Using just the green subpixels should use about 1/3 of the power, and yet maintain a lot of visibility because our eyes are very sensitive to green light.
Click to expand...
Click to collapse
The description for the app "Filter your screen" specifically says that you should avoid monochromatic filters which are not grayscale, in order to avoid some kind of burn-in, and thus a permanent tint on our (AM)OLED screens. Do you know anything about this?
I'd love to use the red or green filter, but I'm not sure I dare to, at least not for any significant amount of time.
ugumba said:
The description for the app "Filter your screen" specifically says that you should avoid monochromatic filters which are not grayscale, in order to avoid some kind of burn-in, and thus a permanent tint on our (AM)OLED screens. Do you know anything about this?
I'd love to use the red or green filter, but I'm not sure I dare to, at least not for any significant amount of time.
Click to expand...
Click to collapse
I must say I haven't thought of that. That's an issue. But it's no more an issue than if you heavily use an app that uses a single color. Or if you heavily use an app that has a single bright display element in one place.
It's going to be more an issue if your background is all white, and then it turns, say, all green, and then the green subpixels burn out faster than the red and blue. But if you use green+invert with that, then you will have a lot fewer green pixels, most of them being black.
Moreover, I assume the issue will be mitigated to some degree if you set low screen intensity, and most of us will do that at night. Just use my ScreenDim app at night and use a combination of the two sliders to set a very low brightness. (Or use ScreenFilter or something else like that.) However, this does mean that we probably don't want to use a monochromatic screen all the time during the day, unless, well, we want to use it all the time and hence the tint will irrelevant.
If the burnin does a uniform tint across the screen (which may not be the case), then we can eventually correct for it with a custom color profile.
Or you can alternate between red/green/blue modes on a regular basis.
b631nz said:
Great app. Works well. Having no trouble with the logo for screen on.
I'm not sure how difficult this would be to implement, but it would be useful to have a tasker plugin so that red mode could be activated when you run certain apps or at specific times of day.
Click to expand...
Click to collapse
It would be easy to add Tasker support at the same time as I add launcher shortcuts.
I just posted 0.99rc4. New mode: Mono sepia. The standard sepia mode just changes white to sepia. Mono sepia changes white to sepia, and makes everything monochrome.
I've discovered a great use for the mono sepia and BW modes. The Kindle app screws up subpixel rendering (just as it is screwed up on the Kindle Fire), resulting in colored shadows around letters in some orientations (portrait on my S2, but this may differ). All the single-tone modes (sepia, BW, green, red and blue) will change the subpixel antialiasing to grayscale antialiasing, which to my eyes significantly improves appearance. (Subpixel antialiasing is wonderful--but mainly when done right.)
I just uploaded 1.00.
It's now in Google Play. Free, no ads (other than a link to my other apps). I am planning a pro version that will allow (a) automatic activation on boot (with some sort of safety mechanism in case you put in some bad settings like black on black--maybe if you boot with the device upside down or something like that it won't start on boot?); (b) custom modes.
just read the article on your app, and was wondering what you need to make this work on the Galaxy Nexus if it doesn't already work on it?
ROB281 said:
just read the article on your app, and was wondering what you need to make this work on the Galaxy Nexus if it doesn't already work on it?
Click to expand...
Click to collapse
As far as I know, the Nexus doesn't support mdnie settings. Does it have display settings with dynamic, standard and movie modes?
arpruss said:
It's now in Google Play. Free, no ads (other than a link to my other apps). I am planning a pro version that will allow (a) automatic activation on boot (with some sort of safety mechanism in case you put in some bad settings like black on black--maybe if you boot with the device upside down or something like that it won't start on boot?); (b) custom modes.
Click to expand...
Click to collapse
This app is EXACTLY what I was looking for...except I have a Nexus S 4G
Any way it might get supported? Or is the display tech too different from the GS series?
Great App! i always found the darkes possible darkness too bright for night use.
is this only for stock roms or also AOSP built ones like Cyanogenmod?
Unsupported Device
App not working on Samsung Infuse 4g ( SGH-I997 ). It says Unsupported device or not rooted(it's rooted).
Galaxy Note(att) rooted ICS(cm9) "no root or unsupported"
pgm msg & log attached
Thank you !
Works on SGS1?
Doesnt work on sgs 2 running aokp must need stock software
Sent from my SGH-I777 using xda premium
mikig_mkd said:
App not working on Samsung Infuse 4g ( SGH-I997 ). It says Unsupported device or not rooted(it's rooted).
Click to expand...
Click to collapse
Same here. Sending in logcat... Rooted on Sprint S3.
Does Not work on SGS 1 Epic 4G with cm9
Related
{
"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 ChameleonOS team is proud to present to you our latest addition to the growing list of features. Please give a warm welcome to the new active display feature. With active display your device can turn on when new notifications arrive and display that information to you on the screen. There is no need to turn your device on every time you hear that distinctive notification sound. Your notifications are right where you need them without all the clutter and free from other distractions. If your device has a proximity sensor, which most touch screen phones have, you are in luck. Active display will not turn on if it detects something close to this sensor. So if you have your phone stashed away in your pocket or bag, don't worry, it won't turn the display on and waste your battery. And as an added bonus we've included an option to turn on pocket mode. When this is enabled active display will turn on your screen and display your current notifications instantly, provided you have any pending notifications.
Features
Instantly turns the device screen on and displays notifications as they arrive
Up to 8 notifications displayed in a horizontal strip that can be viewed by touching the notification icon
Short notification description can be displayed around the outside of the center ring
Touch the center ring notification to view the full notification
Unlock the device, open the app for the current notification or dismiss the current notification
Set a re-display time to have active display remind you of your pending notifications
Adjustable brightness level for when active display turns the screen on
Pocket mode which allows active display to turn on once you remove the device from your pocket or bag
Video Demonstration
* Active display will be merged into our github repos shortly and will be included in the upcoming nightly builds thereafter.
website: http://www.chameleonos.org
forums: http://forums.chameleonos.org
github: https://github.com/ChameleonOS
code review: http://review.chameleonos.org​
Now for the important stuff that developers may be interested in. Since ChameleonOS is an open source project this feature is available for other developers to pick and incorporate into other ROMs. If you want to incorporate this you'll need to grab a few commits from our frameworks base and Settings projects.
From android_frameworks_base you'll want to pick the following commits [4.3]:
0e846d1a210f9ac937689ac6fa6052decd6090bd
504a3365f429d1f9b3af4b6f4b33196623b82326
4d79213fa35bf68762d3335bcc4d89991b701338
From android_frameworks_base you'll want to pick the following commits [4.4]:
269544e60aa176ba8be7f5a66d0210bec49fa43f
And from Settings you'll want to pick these commits:
0e508d62622c403ab99655a1eb7e14b3fcaa18d8
8ab78d4d79bf124bda5b78dc2bdf9e44df25c2e2
*Note: ChameleonOS started out by using CyanogenMod as a base so some dependencies may exist which would need to be resolved when incorporating this into other ROMs. Feel free to contact me if you encounter any problems and you can't figure out the resolution.
**UPDATE**
For those that are using a 4.3 or 4.4 based ROM that does not have Active Display integrated, I've managed to develop a stand alone application that adds the functionality of Active Display. There is an ad supported version as well as a paid version for those that like to support independent developers.
Active Display (ad supported)
Active Display w/o ads
Is there a pulse setting? Or is that the re-display option?
yawdapaah said:
Is there a pulse setting? Or is that the re-display option?
Click to expand...
Click to collapse
I guess you could consider the re-display option as being similar to pulse for the LED. Active display will turn on and show pending notifications at the interval specified by the user.
0xD34D said:
I guess you could consider the re-display option as being similar to pulse for the LED. Active display will turn on and show pending notifications at the interval specified by the user.
Click to expand...
Click to collapse
I guess without the Moto X dedicated CPU a pulse option would kill the battery? If you miss the notification, you can't really tell that you've gotten one.
yawdapaah said:
I guess without the Moto X dedicated CPU a pulse option would kill the battery? If you miss the notification, you can't really tell that you've gotten one.
Click to expand...
Click to collapse
The minimum setting is 1 minute so you could set it to that. Because it turns the display on momentarily to display the notifications, there will be some power consumption because of this. There are several different values the user can set this to and in a future release I'll have it so the user can set their own time instead of being confined to the discrete values that are available in the current implementation.
...
Just 1 small question...how reliable is pocket mode ?
Cos I prefer that as the most amazing usp of active display
vampire36 said:
Just 1 small question...how reliable is pocket mode ?
Cos I prefer that as the most amazing usp of active display
Click to expand...
Click to collapse
May be it is not only using call sensors but as well acclerometer.. this way it might not turn ON.. But wondering about battery drain..
So, do we just flash this the usual way or are there special instructions on how to properly do this??
Thanks in advance, this Rom looks AWESOME!!! Can't wait to flash it on my SGS3
Sent from my SCH-I605 using XDA Premium 4 mobile app
I hope somebody makes a flashable zip for the latest PA
Sent from my Nexus 4 using Tapatalk 4
About pocket mode, it says it will turn on active display when out of the pocket. And so this means the proximity sensor will be on all the time after receiving a notification?
TheGeekHanaz said:
I hope somebody makes a flashable zip for the latest PA
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
You can't make a chane to the source code with a flashable zip. THat's more work on someone who wants to do that, or a device maintainer could just cherry-pick the commits he's highlited which would be easier imo.
tsukot said:
About pocket mode, it says it will turn on active display when out of the pocket. And so this means the proximity sensor will be on all the time after receiving a notification?
Click to expand...
Click to collapse
yes, pocket mode will enable proximity sensor when screen is off. Waving your hand over the device will also turn on the screen if there is a notification waiting as well, perfect for when my phone is on my desk.
hoppermi said:
yes, pocket mode will enable proximity sensor when screen is off. Waving your hand over the device will also turn on the screen if there is a notification waiting as well, perfect for when my phone is on my desk.
Click to expand...
Click to collapse
And so this will kill the battery slowly until the user puts the phone out of the pocket.
vampire36 said:
Just 1 small question...how reliable is pocket mode ?
Cos I prefer that as the most amazing usp of active display
Click to expand...
Click to collapse
It's been quite reliable for me. It uses the device's proximity sensor to determine if it should show the active display by listening for when the sensor goes from something being near to something being far (typically >5cm). The motivation behind adding this was because when I take my phone out of my pocket it is usually to check something. Having it turn on and display my notifications the moment I take it out just made sense to me. If you don't have any notifications then it's not going to turn on. I also use this to look at my notifications when my device is sitting on my desk. I can wave my hand over the screen and it turns on. It is an option so people can enable and disable it as they see fit.
tsukot said:
And so this will kill the battery slowly until the user puts the phone out of the pocket.
Click to expand...
Click to collapse
No it won't. Proximity sensors are interrupt based meaning they only update when the state changes from near->far or far->near. All the proximity sensors I've worked with thus far only provide two different values, one representing near and one representing far. So if the device is in your pocket, the sensor code is not going to be called until you the device. It's not like an accelerometer where values are always changing and thus code is always running.
Sunlight mode coming soon
I wanted to share a new feature coming to this implementation of active display. Some, if not all, displays are hard to see in direct sunlight so I wanted to see what I could do to make active display stand out a bit when staring at it when the sun is beating down on my display. I found that if I invert the colors, the items and text on active display are much easier to make out. If your device has a light sensor, and this mode is enabled in the settings, active display will invert the colors when it detects a bright light source. Bright in this case is greater than 8000 lumens.
For those worried about the sensor always polling, don't worry. The sensor is only being used while active display is on and showing content. Once the screen turns off or you unlock the sesnor is no longer being used.
0xD34D said:
It's been quite reliable for me. It uses the device's proximity sensor to determine if it should show the active display by listening for when the sensor goes from something being near to something being far (typically >5cm). The motivation behind adding this was because when I take my phone out of my pocket it is usually to check something. Having it turn on and display my notifications the moment I take it out just made sense to me. If you don't have any notifications then it's not going to turn on. I also use this to look at my notifications when my device is sitting on my desk. I can wave my hand over the screen and it turns on. It is an option so people can enable and disable it as they see fit.
Click to expand...
Click to collapse
Dude works a treat...awesome...thanx a lot...nexus 4
Now can just peek through apps as and when I want
Thanx a ton
0xD34D said:
The ChameleonOS team is proud to present to you our latest addition to the growing list of features. Please give a warm welcome to the new active display feature....
Click to expand...
Click to collapse
That is awesome. I really hope someone ports this over to a full stock rom. or makes it possible to install by those of us with root.
Hi!
At the beggining - I'm sorry if you won't understand something. English isn't my main language, I still learn.
In some smartphones with AMOLED screen (such as Samsung Galaxy S4) black pixel = turned off pixel.
I've always been irritated because of the fact that our batteries aren't too great, but phone producers still produce their phones with hiper-resolution, which practically we cannot even see.
I have invented something, that later I turned to real app.
I call it Pixel Battery Saver, because it displays some kind of totally black mesh on the screen (you can change its density), so at least half of the pixels (or more) are turned off (so the screen consumes less energy!), while you are still able to read anything on your screen.
If you still don't understand, just take a look at the screenshots.
{
"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"
}
I've already created this app.
You may download and test it for free,
but if you really appreciate my work - I would be grateful for every donation (every single dollar would be helpful).
Let me know if you found any annoying bug or misspelling. This is my very first app - I still learn
FAQ:
What do I need this for?
- Imagine this situation - your battery level is really low, but you have to search for something important on the Internet. Making the brightness lower often isn't enough. That's when you would need my app - to turn off some count of pixels.
There are lots of apps that dim the screen...?
- This app works different. It doesn't overlay your screen with transparent image (but there is such option in premium version if you need it too). It overlays your screen with totally black screen, which makes some count of pixels off, to prevent them from consuming battery.
Do I really need AMOLED screen?
- The best results you can get right with AMOLED screen, where black pixel means turned off pixel. However, even in other type screens black pixels are saving some battery, so it's just worth to check.
In battery stats I can see that this app consumes a lot of energy. Why?
- Don't look at the stats, look at the real battery consumption. Probably, Android Battery Stats app "thinks", that this app display an image on the screen all the time, because of what it shows an information about consuming energy. In fact, this app turns OFF the pixels (in AMOLED screens with this function), so it SAVES that energy, not consumes.
When the mesh is on, I am unable to install apps (Install button is disabled). WTH?
- That's because of the Android Security. In premium version of Pixel Battery Saver I added an option to bypass this protection. In this free version you can simply turn off the app (by clicking "Turn off" button in Settings window) before installing any app and then turn on it again.
Density of the mesh that I recommend is "High".
Changelog in post #2.
Download: Google Play
Always use the latest version with fixed bugs and new options.
[CHANGELOG]
v1.3 (coming next month):
- new option to automatically start service at specific battery level
- hidden notification icon
- option to detect package installer to prevent its bug (stops mesh activity when you're installing new app and starts it again when it's done)
- new option to dim the screen (useful at night)
- small fixes
v1.2.1:
- fixed doubled mesh after reboot (black screen)
- fixed unnecessary scrolling to the bottom ad
v1.2:
- quickly show/hide the mesh with notification action
- Ads. Sorry =)
v1.1.1:
- shortcut to the donation page
v1.1:
- new option to automatically start service on boot
- small bugfixes
[TO DO]
- Widget
- Overlay bottom navigation bar too
[KNOWN BUGS]
- I can't install any app (unable to tap Install button)
> This bug is fixed in version 1.3 (added new option to prevent this)
- The bottom navigation bar (with back, home and recent apps buttons) isn't overlayed
> I know about this, I will fix it in the future
disip said:
So, the question is - is anyone able to create an app like this?
Click to expand...
Click to collapse
There are a couple of issues with the concept as you've outlined it.
1) Turning off 50% of the screen you make small text unreadable. Even in your example the not so tiny temperature values are illegible.
2) While this would definitely conserve power in terms of physically lighting the screen, it might not be by as much as you'd think. The screen has multiple power sucking components. The first is the light producing LED's. Turning half of them off saves half the power. Simple math
. But the GPU that processes the screen imaging still runs at full speed even if the screen is blank. While the LED pixels aren't working, the GPU is still working to render a black image. So turning off half the pixels doesn't reduce the power draw required to run the entire display to 50% in total.
3) The app that overlays the black mesh will require the GPU to work overtime. It's got to render the image that's supposed to be in the screen plus it's got to render the black mesh over the native image. That could potentially use up more energy rendering the black than the black saves by not lighting the pixels.
4) The already built in option is to just turn the screen brightness down 50%. It accomplishes the same goal, requires no additional image rendering, and preserves the original image design without loss.
Skipjacks said:
There are a couple of issues with the concept as you've outlined it.
1) Turning off 50% of the screen you make small text unreadable. Even in your example the not so tiny temperature values are illegible.
2) While this would definitely conserve power in terms of physically lighting the screen, it might not be by as much as you'd think. The screen has multiple power sucking components. The first is the light producing LED's. Turning half of them off saves half the power. Simple math
. But the GPU that processes the screen imaging still runs at full speed even if the screen is blank. While the LED pixels aren't working, the GPU is still working to render a black image. So turning off half the pixels doesn't reduce the power draw required to run the entire display to 50% in total.
3) The app that overlays the black mesh will require the GPU to work overtime. It's got to render the image that's supposed to be in the screen plus it's got to render the black mesh over the native image. That could potentially use up more energy rendering the black than the black saves by not lighting the pixels.
4) The already built in option is to just turn the screen brightness down 50%. It accomplishes the same goal, requires no additional image rendering, and preserves the original image design without loss.
Click to expand...
Click to collapse
1) Why do you think so? As you can see on my image, it doesn't make the text unreadable (if the "mesh" is pixel-by-pixel)
2) Right, but everyone know that black-layout apps are muc better for our battery than colorful or white, right because black screen isn't that "hungry" of power
3) Ok, but there are lots of apps that creates a full-screen black (transparent) overlay to make the screen more "shade" (dim?) to save the power. It works, even thou all the thing you described in #3
4) Oh, right, but when my energy power is really low, I turn the screen brightness to the lowest level, but it still consumes a LOT of energy.
Anyway! This discussion isn't even important, maybe we should just CHECK if this may work, or if not?
But, as I said, I am just asking someone to create a simple app like this.
Thanks anyway for reply.
Really? No one?
disip said:
Really? No one?
Click to expand...
Click to collapse
it's not worth in my opinion, while rendering half of the screen black would help save some battery, the saving wouldn't be so great, yes the screen is what burns the most battery on android but, its not just having it on, its having the phone out of deep sleep, having the touch sensor activated and registering touches, etc, not to mention it would just kill the great viewing experience that the phone offers.
-Ric- said:
it's not worth in my opinion, while rendering half of the screen black would help save some battery, the saving wouldn't be so great, yes the screen is what burns the most battery on android but, its not just having it on, its having the phone out of deep sleep, having the touch sensor activated and registering touches, etc, not to mention it would just kill the great viewing experience that the phone offers.
Click to expand...
Click to collapse
Though when we are using our phones it has to render the whole screen anyway, so I think rendering a half of it would be better?
I am not thinking about this app making our screen always on. I just mean to display this mesh when we are using our phones and the battery level is low.
And, of course, it would kill the viewing experience, but when your battery level is 5% and you have to do some important research on the internet - you don't care about the viewing experience.
If you think turning the pixels on is not the thing that consumes the most of the battery, then turn the brightness to the highest level and then to the lowest and see how much it consumes... (changing the brightness doesn't change anything with the touch sensor and other thing you described though)
I thought my idea is really simple to develop for any Android developer and to see if it really works...
I think that if you do some comprehensive tests, you could bring some attention.
Create one image with this pattern, put on your phone and open it with any image viewer, put the bright on max. Let it run for some time.... Measure how much battery was sucked.... Test again with the same image, but without the pattern, do some statistics with the results.
Are you rooted? You could invert screen color or make it grayscale.
That's exactly what I was thinking about. I will do this tomorrow.
I'll post my quick opinion. It really depends on how the phone handles the screen, but my experience is from my old Galaxy S2 with NoLED running over night. I think NoLED program was essentially accomplishing what you are proposing (i.e. rest of screen is "off" or black) and on portion of the screen is on for the LED to hop around. However, even though the screen was black the screen was still draining at a quite high rate (~6%/hr on average). The screen needs to be "off" not just black in order to save more power.
But having stated the above, I am looking forward to your test results to compare and determine if it can save more battery.
liquidzyklon said:
I'll post my quick opinion. It really depends on how the phone handles the screen, but my experience is from my old Galaxy S2 with NoLED running over night. I think NoLED program was essentially accomplishing what you are proposing (i.e. rest of screen is "off" or black) and on portion of the screen is on for the LED to hop around. However, even though the screen was black the screen was still draining at a quite high rate (~6%/hr on average). The screen needs to be "off" not just black in order to save more power.
But having stated the above, I am looking forward to your test results to compare and determine if it can save more battery.
Click to expand...
Click to collapse
Thanks for your opinion, but the screen in s2 is way different than on s4. The screen in s2 doesn't turn off the black pixels. The one in s4 does.
II am looking forward to do this test tomorrow
I think this would be like a filter app, such as the found in Play Store.
Exactly. I was talking about it but I forgot the name. I next hour I will do some tests.
Ok, thread can be closed - I've created this app by my own. I mean, I used many of tutorials and examples, and finally got it. Thanks anyway.
Could you share your findings?
This would be pretty hard, as I have read dozens of sites and forums to understand everything. There wasn't any quick or simple solution.
Did it work and save as much battery as you expected?
leodfs said:
Did it work and save as much battery as you expected?
Click to expand...
Click to collapse
I still do not know, I have to test it multiple times to be sure.
Ok. I think it really works, but I'm still not sure. Give me few days to share the alpha version of my app (I just want to add some extra functions).
By the way, does anyone know where should I look for a list of phones with screens like in S4? I mean where the black pixel means it's off.
disip said:
Ok. I think it really works, but I'm still not sure. Give me few days to share the alpha version of my app (I just want to add some extra functions).
By the way, does anyone know where should I look for a list of phones with screens like in S4? I mean where the black pixel means it's off.
Click to expand...
Click to collapse
Here's a list of some recent ones. Pretty sure the Moto X has one as well.
http://www.oled-info.com/oled_devices/mobile_phones
When watching movies or playing games, the colour and brightness changes. It looks very bland and dead, lifeless.
It looks too bright, dull with weak colour. Sometimes brightness will change higher or lower when using the device.
Auto brightness is disabled of course. Anything I can check to try and see why my screen is acting and appearing so strange?
I'm running stock Oreo 8. Colour calibration is near the top, 12:00.
kanej2006 said:
When watching movies or playing games, the colour and brightness changes. It looks very bland and dead, lifeless.
It looks too bright, dull with weak colour. Sometimes brightness will change higher or lower when using the device.
Auto brightness is disabled of course. Anything I can check to try and see why my screen is acting and appearing so strange?
I'm running stock Oreo 8. Colour calibration is near the top, 12:00.
Click to expand...
Click to collapse
Happens to me as well, I noticed when I go outside the screen becomes brighter but more washed out, don't know why though
shae23 said:
Happens to me as well, I noticed when I go outside the screen becomes brighter but more washed out, don't know why though
Click to expand...
Click to collapse
It's a very strange issue, unsure if normal or not.
However, as you said, it happens the most when you are outdoors and it's bright, the screen appears to go very bright and colours are washed out.
After playing a game, I can see the brightness changing automatically and when quitting the application, the screen dimmed by itself. Very noticeable, WTF?
I've never seen such an problem with any other phone.
Even had a recent Huawei Honor 7X, no such issue with the screen.
I think Oreo is bugged, like Asphalt 8 plays slower than on nougat, freezes and chrashes my phone, like literally screen flicker and reboots, might just be another bug or something
kanej2006 said:
When watching movies or playing games, the colour and brightness changes. It looks very bland and dead, lifeless.
It looks too bright, dull with weak colour. Sometimes brightness will change higher or lower when using the device.
Auto brightness is disabled of course. Anything I can check to try and see why my screen is acting and appearing so strange?
I'm running stock Oreo 8. Colour calibration is near the top, 12:00.
Click to expand...
Click to collapse
guys, thats not an screen issue thats an option on developer menu, search for ''Increase readability under sunlight'' turn off and that will fix the problem have a nice day
hack4ever said:
guys, thats not an screen issue thats an option on developer menu, search for ''Increase readability under sunlight'' turn off and that will fix the problem have a nice day
Click to expand...
Click to collapse
Thanks for the tip, I've now disabled that option from the ''developer menu'' and will do some testing. I shall report back shortly! After looking through some other forums not only should it prevent the screen from dimming but also increase maximum contrast which is a bonus!
hack4ever said:
guys, thats not an screen issue thats an option on developer menu, search for ''Increase readability under sunlight'' turn off and that will fix the problem have a nice day
Click to expand...
Click to collapse
Nice
Still the same. Turning ''increase readability'' on/off makes no difference. Brightness still increasing/decreasing on it's own.
Also, when watching videos, colours are weak/washed out and appear too bright.
Probably a software issue? Unfortunately, when previously on Nougat I did not test this as I immediately flashed Oreo the day I received the phone. Oreo bug perhaps.
kanej2006 said:
Still the same. Turning ''increase readability'' on/off makes no difference. Brightness still increasing/decreasing on it's own.
Also, when watching videos, colours are weak/washed out and appear too bright.
Probably a software issue? Unfortunately, when previously on Nougat I did not test this as I immediately flashed Oreo the day I received the phone. Oreo bug perhaps.
Click to expand...
Click to collapse
im on oreo c432 and its not happening to me, try a complete day turning increase readability off, turn it off and restart your phone maybe works
hack4ever said:
im on oreo c432 and its not happening to me, try a complete day turning increase readability off, turn it off and restart your phone maybe works
Click to expand...
Click to collapse
I will give this a try. As of now, with readability disabled, the black levels/contrast look higher.
However, it is a shame. Unsure if it's a fault or not, but the screen looks pretty good when playing games or browsing through images but when watching videos/media, colours/contrast are washed out and it looks really bad, here is an example:
{
"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"
}
My video display on my phone is normal, it's good even better than my wife's ip7s and my bro's samsung s8, they look yellowish compared to my mate9
kanej2006 said:
I will give this a try. As of now, with readability disabled, the black levels/contrast look higher.
However, it is a shame. Unsure if it's a fault or not, but the screen looks pretty good when playing games or browsing through images but when watching videos/media, colours/contrast are washed out and it looks really bad, here is an example:
Click to expand...
Click to collapse
have you tried watching a movie anywhere to see if it isnt a youtube problem ?
hack4ever said:
have you tried watching a movie anywhere to see if it isnt a youtube problem ?
Click to expand...
Click to collapse
Of course. I have tried XPlayer and MX Player PRO. All movies look dull, dead, lifeless and weak colour...
kanej2006 said:
Of course. I have tried XPlayer and MX Player PRO. All movies look dull, dead, lifeless and weak colour...
Click to expand...
Click to collapse
wow, i tried youtube and netflix and now i see what you mean, i haven't noticed it before it looks like a high contrast image
hack4ever said:
wow, i tried youtube and netflix and now i see what you mean, i haven't noticed it before it looks like a high contrast image
Click to expand...
Click to collapse
EXACTLY!!! It's a shame because when browsing through images, gaming or even browsing the net, the screen looks fantastic.
However, with movies, colours are washed out and the picture looks like high contrast. Never seen this problem before.
I wish there was a fix.
After doing some basic testing, I found a way to fix the horrible looking picture when watching movies, it does not work with YouTube or Netflix, but with regular video/movie players.
For example, in MXPlayer Pro, In the settings/tools menu, go to decoder and select ''software decoder'' . When selecting HW or HW+ the screen flickers and colours are washed out and contrast/brightness is far too high.
Can others please test this on high quality MKV or MP4 movie files?
Another update, dunno how I forgot to test the difference but boy was I surprised.
Check out some high quality YouTube videos. Watch these videos on the YouTube App followed by the very same videos on YouTube in the internet browser.
For me there is a BIG BIG difference, unsure if I'm the only one but please test this. Video's look $hit on the YouTube app, too bright and dead/colourless, horrible and dull looking.
However, the very same videos seen in YouTube in my Chrome browser look simply stunning. Amazing accurate colours and deep blacks, just how they are supposed to look.
Later in the evening I will try to compare some videos myself on both the YouTube app and in the browser.
Question is, why am I getting these issues? I would of thought YouTube, whether viewed in the App or in the browser would be the same. Is this some software fault??
Please test the above and share your results.
In the YouTube app type pure black and watch the first video. When the phone is upright it looks pure black no problems. But then watch the same video with the phone horizontal and the black totally changes. Do you think the problem you're having could be related to this bug. Huawei should fix this.
I have a different problem. I see some sort of "burn in". For example when im using one app and switch to another one i can still see some parts of first one (menus etc). It's very noticable in dark room at 20% brightness. Since i'm playing CSR2 very actively this Audi logo makes me crazy
Steelrock said:
I have a different problem. I see some sort of "burn in". For example when im using one app and switch to another one i can still see some parts of first one (menus etc). It's very noticable in dark room at 20% brightness. Since i'm playing CSR2 very actively this Audi logo makes me crazy
Click to expand...
Click to collapse
I also experience screen burn. But it fades away after a while.
Note: The following post was posted on Samsung Members: I thought I'd post it on here to raise awareness: and to get help.
Recently brought a Samsung Galaxy A51 for a family member, and upon setting the fingerprint and activating the blue light filter: I realised everytime I'm on the lock screen, there's no blue light filter! Upon unlocking, the filter is applied to the rest of the phone. I read on the Samsung forum when someone asked why, that it's like that due to the fingerprint. So why can't the rest of the screen, apart from the fingerprint area, have blue light filter?! Am I expected to burn my eyes whilst trying to look at the time in the middle of the night?! I'm sure with Amoled panels, that each pixel can be controlled, so why hasn't this been applied? Samsung needs to step up their software game as a simple error like this gives a terrible experience. Not the first time something like this occured on a Samsung device.*Furthermore, I tried a third party blue light filter: Twilight which worked fine with the fingerprint. Rather use the in built one as it's lots better.
I'd appreciate any help, thanks!
You can set a Bixby routine to lower the brightness and turn on blue light filter at certain time.
I really like the lockscreen with full brightness, to enjoy the beautiful images of the dynamic wallpapers.
ramping said:
You can set a Bixby routine to lower the brightness and turn on blue light filter at certain time.
I really like the lockscreen with full brightness, to enjoy the beautiful images of the dynamic wallpapers.
Click to expand...
Click to collapse
Thanks for the suggestion. I still think samsung should e automatically implement something to make the lock-screen, eye-frienly at night time. As the screen is really nice, but it hurts your eyes at night. They really,
really need to fix the software as there are a few issues: one of which is that it's buggy.
OLED displays gets burn-in almost exclusively in places where there are a lot of elements that stay completely white all the time. Most notoriously, status bar and navbar. For some people who text a lot, I have seen burn-in for the call and video call buttons, as well as individual keyboard letters.
My question is, is there an app, or a theming engine to be precise, that would allow the user to set a time interval, during which those high persistence elements of the picture could be dimmed over time? For example, user unlocks the phone and starts typing a message - navbar, statusbar, keyboard letters are all 100% white. They remain white, then after 60 seconds they start to dim, and after 120 seconds they are at 30% brightness. So when you're having long texting sessions, keys would be dim enough so you can make them out, but since they are not leaving your muscle memory you can type just as well as if it was at 100% brightness - but you save a lot of energy and thus substantially reduce the potential for burn-in. And if you're outdoors and can't make out what the time is after those 180 seconds, you gently pull down the notification bar and it resets to 100%. Something like that.
I can't be the first person to think of this. Moreover, I think AOSP devs realized this at around version 9 and dropped the overall brightness of the status/navbar to 80%, but it remains like that the whole time. What I am proposing would be infinitely more efficient. Anyone here knows something that's able to do that?
Avoid use in direct sunlight. Seconds not minutes if you do. Use manual brightness control and keep below 50%. Typically I comfortable use 30-40% indoors. Excessive brightness prematurely kills AMOLED displays needlessly. Excessive heat with the display on ie again direct sunlight should be avoided.
Use dark mode. The red pixels are longest live, blue the shortest; heavy blue or white usage will degrade the display the fastest.
Use icon packs and layouts that support pixel conservation. Rotate widgets and icons periodically.
This heavily use N10+ has over 8k hours on its display. There is no detectable fading, failed pixels, color inaccuracies, nothing; it remains perfect. It's a mirror image next to my new N10+ with less then 50 hours on it.
AMOLED displays can be very long lived. Everything on this homepage gets rotated slightly from time to time, even the page number icons ie 3 instead of 2.
{
"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"
}
johnnyboy041 said:
OLED displays gets burn-in almost exclusively in places where there are a lot of elements that stay completely white all the time. Most notoriously, status bar and navbar. For some people who text a lot, I have seen burn-in for the call and video call buttons, as well as individual keyboard letters.
My question is, is there an app, or a theming engine to be precise, that would allow the user to set a time interval, during which those high persistence elements of the picture could be dimmed over time? For example, user unlocks the phone and starts typing a message - navbar, statusbar, keyboard letters are all 100% white. They remain white, then after 60 seconds they start to dim, and after 120 seconds they are at 30% brightness. So when you're having long texting sessions, keys would be dim enough so you can make them out, but since they are not leaving your muscle memory you can type just as well as if it was at 100% brightness - but you save a lot of energy and thus substantially reduce the potential for burn-in. And if you're outdoors and can't make out what the time is after those 180 seconds, you gently pull down the notification bar and it resets to 100%. Something like that.
I can't be the first person to think of this. Moreover, I think AOSP devs realized this at around version 9 and dropped the overall brightness of the status/navbar to 80%, but it remains like that the whole time. What I am proposing would be infinitely more efficient. Anyone here knows something that's able to do tha
blackhawk said:
Avoid use in direct sunlight. Seconds not minutes if you do. Use manual brightness control and keep below 50%. Typically I comfortable use 30-40% indoors. Excessive brightness prematurely kills AMOLED displays needlessly. Excessive heat with the display on ie again direct sunlight should be avoided.
Use dark mode. The red pixels are longest live, blue the shortest; heavy blue or white usage will degrade the display the fastest.
Use icon packs and layouts that support pixel conservation. Rotate widgets and icons periodically.
This heavily use N10+ has over 8k hours on its display. There is no detectable fading, failed pixels, color inaccuracies, nothing; it remains perfect. It's a mirror image next to my new N10+ with less then 50 hours on it.
AMOLED displays can be very long lived. Everything on this homepage gets rotated slightly from time to time, even the page number icons ie 3 instead of 2.
View attachment 5721937
Click to expand...
Click to collapse
johnnyboy041 said:
OLED displays gets burn-in almost exclusively in places where there are a lot of elements that stay completely white all the time. Most notoriously, status bar and navbar. For some people who text a lot, I have seen burn-in for the call and video call buttons, as well as individual keyboard letters.
My question is, is there an app, or a theming engine to be precise, that would allow the user to set a time interval, during which those high persistence elements of the picture could be dimmed over time? For example, user unlocks the phone and starts typing a message - navbar, statusbar, keyboard letters are all 100% white. They remain white, then after 60 seconds they start to dim, and after 120 seconds they are at 30% brightness. So when you're having long texting sessions, keys would be dim enough so you can make them out, but since they are not leaving your muscle memory you can type just as well as if it was at 100% brightness - but you save a lot of energy and thus substantially reduce the potential for burn-in. And if you're outdoors and can't make out what the time is after those 180 seconds, you gently pull down the notification bar and it resets to 100%. Something like that.
I can't be the first person to think of this. Moreover, I think AOSP devs realized this at around version 9 and dropped the overall brightness of the status/navbar to 80%, but it remains like that the whole time. What I am proposing would be infinitely more efficient. Anyone here knows something that's able to do that?
Click to expand...
Click to collapse
I think you could look into immersive mode, It has many different names Another option talk in developer forums fr your phone , otherwise its hidden somwhere in your settings
Click to expand...
Click to collapse
Galaxy store>Good Lock family of apps>Quickstar
Is there a way to prevent burn in when using the phone in a bright environment? My job requires a bright environment.
Fytdyh said:
Is there a way to prevent burn in when using the phone in a bright environment? My job requires a bright environment.
Click to expand...
Click to collapse
No other than the mods I already mentioned. AMOLEDs have a finite lifespan that's proportionately shorter or longer dependant on brightness level. The brightest stars burn the fastest...
All you can do in that case is use at minimum needed viewing brightness and try to use in shaded areas.
Maybe use a work phone so you don't burn up your personal phone.
I am under the impression that none of you even read what I asked in full. I asked a very precise question regarding a particular way to mitigate burn in, nothing on HOW to to mitigate it, as I hinted in the name of this thread.
1. "Avoid use in direct sunlight." Excuse me? Phones are meant to be used outdoors, and they have been since the birth of the idea of a mobile phone.
2. I don't have a Samsung phone. What I meant was something more universal, like a Magisk module, or a root theme engine.
3. With due respect sir, everything you mentioned is more of a paranoid hassle than an automated instant-fix. What I proposed, on the other hand, is.
johnnyboy041 said:
I am under the impression that none of you even read what I asked in full. I asked a very precise question regarding a particular way to mitigate burn in, nothing on HOW to to mitigate it, as I hinted in the name of this thread.
1. "Avoid use in direct sunlight." Excuse me? Phones are meant to be used outdoors, and they have been since the birth of the idea of a mobile phone.
2. I don't have a Samsung phone. What I meant was something more universal, like a Magisk module, or a root theme engine.
3. With due respect sir, everything you mentioned is more of a paranoid hassle than an automated instant-fix. What I proposed, on the other hand, is.
Click to expand...
Click to collapse
Welcome to the planet. The more you run it in direct sunlight the higher the risks including outright failure. That sound better?
This isn't a backlight LCD* or a LED display. OLEDs are less robust than LEDs.
Due respect my mass... prudence isn't paranoia.
8+k hours here and no detectable damage of any kind.
* direct sunlight can fry LCDs too.
blackhawk said:
Welcome to the planet. The more you run it in direct sunlight the higher the risks including outright failure. That sound better?
This isn't a backlight LCD* or a LED display. OLEDs are less robust than LEDs.
Due respect my mass... prudence isn't paranoia.
8+k hours here and no detectable damage of any kind.
* direct sunlight can fry LCDs too.
Click to expand...
Click to collapse
Dude, nobody sets their phones to sunbathe for no reason. If the situation requires me, I'm using it the open sun. That hasn't damaged any OLED screen I used in the past 10 years. You ain't gonna convince anyone to rearrange widgets every week giving a meteor strike argument, especially with that attitude. Now please, are we over useless internet forum fights? I'm not negating any technical point you made, and what you did is certainly a way to deal with the issue, but it is objectively not practical for 99% of users.