I wrote an App that lets you control your phone's brightness provided it's running Android 8.0+ and has a compatible fingerprint sensor.
I wrote it because I change my phone's brightness as often as I change it's volume, if not more, and I was upset I didn't have dedicated hardware for it. When Oreo launched and it added fingerprint gesture detection, I figured it was time
I own and test on the OG Google Pixel, and the app has been out for 2 weeks so I've been able to squash most bugs.
Feedback and suggestions are most welcome!
https://play.google.com/store/apps/details?id=com.tunjid.fingergestures
Link doesn't work.
Dude... THANK YOU. Aside from ad-blocking and kernel tweaks, one of the main reasons I've always rooted was for the status bar brightness slider, and this is an even better implementation of it (I love hardware switches). The ads would never get in my way at all, but I went ad-free just out of appreciation.
mmartenn said:
Link doesn't work.
Click to expand...
Click to collapse
Thanks for catching that, fixed!
How to check is my fingerprint compatible?
Device is OnePlus 3T.
mihata said:
How to check is my fingerprint compatible?
Device is OnePlus 3T.
Click to expand...
Click to collapse
For your device to be compatible, you have to be running Android Oreo and your OEM would need to support fingerprint gestures on a firmware level. I don't believe the One Plus 3T Oreo beta supports it at the moment.
The app is super cool; I love the option to adjust brightness via the fingerprint reader! One major complaint keeps me from using it though, which is that it always disables adaptive brightness when making an adjustment. This is extremely jarring when it's dark and I just want to dim the screen a bit, but bringing it down from 40% (adaptive) to 20-30% (absolute) actually makes the screen brighter. I hope for the next version you consider having the option to leave adaptive brightness on while making adjustments. Thanks!
teiglin said:
The app is super cool; I love the option to adjust brightness via the fingerprint reader! One major complaint keeps me from using it though, which is that it always disables adaptive brightness when making an adjustment. This is extremely jarring when it's dark and I just want to dim the screen a bit, but bringing it down from 40% (adaptive) to 20-30% (absolute) actually makes the screen brighter. I hope for the next version you consider having the option to leave adaptive brightness on while making adjustments. Thanks!
Click to expand...
Click to collapse
Hi! I experimented with this previously, but since adaptive brightness is managed by the system, leaving it on when you adjust brightness will cause the brightness to be reset immediately by the adaptive brightness service. The compromise I added was allowing adaptive brightness to be restored as soon as the screen is turned off and on again.
@youtube10 thanks for this
when Oxygen OS will be on Oreo, do you think your tweak will works on OnePlus 5 ?
i change too, very often the brightness on my device...
sunnyraid said:
@youtube10 thanks for this
when Oxygen OS will be on Oreo, do you think your tweak will works on OnePlus 5 ?
i change too, very often the brightness on my device...
Click to expand...
Click to collapse
Hi! I'm not sure. I'm going to set up a way for beta testing so people with phones not supported can check and verify if the app is compatible with their device. I should be getting around to that in the coming days. I'm just not sure if it should be through the Play Store or XDA. I don't think the Play Store allows for beta testing on specific devices.
youtube10 said:
Hi! I'm not sure. I'm going to set up a way for beta testing so people with phones not supported can check and verify if the app is compatible with their device. I should be getting around to that in the coming days. I'm just not sure if it should be through the Play Store or XDA. I don't think the Play Store allows for beta testing on specific devices.
Click to expand...
Click to collapse
thanks! don't hesitate to send beta apks, i can test them on my OP5 :good:
youtube10 said:
Hi! I experimented with this previously, but since adaptive brightness is managed by the system, leaving it on when you adjust brightness will cause the brightness to be reset immediately by the adaptive brightness service. The compromise I added was allowing adaptive brightness to be restored as soon as the screen is turned off and on again.
Click to expand...
Click to collapse
Thanks for the reply. As another user mentioned, I'd be using your app primarily to replace the status bar quick finger slide feature from most custom ROMs, and those are generally able to work alongside auto brightness, which is why I assumed it would be possible. Personally I find this too frustrating to work around, but I appreciate that you considered this.
teiglin said:
Thanks for the reply. As another user mentioned, I'd be using your app primarily to replace the status bar quick finger slide feature from most custom ROMs, and those are generally able to work alongside auto brightness, which is why I assumed it would be possible. Personally I find this too frustrating to work around, but I appreciate that you considered this.
Click to expand...
Click to collapse
Out of curiosity, on those ROMs, how long did it take for adaptive brightness to restore the brightness to what it was before you adjusted it?
I don't think adaptive brightness and system brightness are 2 different values. It's possible you didn't give permissions to read or write to settings so that when you try reducing the brightness with adaptive brightness on, I can't read the current value of your brightness so I default to the highest. This would explain the "jump" in brightness you see while adjusting.
If you don't mind, try giving it another go and checking that you give both accessibility permissions, and permissions to write to settings. After that, with adaptive brightness on, try changing the brightness again and please let me now if the jump still occurs. Also, left and right swipes my default toggle minimum and maximum brightness respectively, so there might've been an accidental recognition of either gesture.
Absolutely love the app! Thank you so much.
Out of curiosity, why doesn't this app support previous Android versions? Asking for my own knowledge and would definitely love to use it on my spare devices running MM and Nougat.
I could see that certain fingerprint gesture apps like this do support the previous versions. Any specific difference?
DJBhardwaj said:
Absolutely love the app! Thank you so much.
Out of curiosity, why doesn't this app support previous Android versions? Asking for my own knowledge and would definitely love to use it on my spare devices running MM and Nougat.
I could see that certain fingerprint gesture apps like this do support the previous versions. Any specific difference?
Click to expand...
Click to collapse
It's because the gesture API was introduced in Android Oreo
youtube10 said:
It's because the gesture API was introduced in Android Oreo
Click to expand...
Click to collapse
Thanks for responding! Totally loved it! Did a research yesterday and found out the same
youtube10 said:
I wrote an App that lets you control your phone's brightness provided it's running Android 8.0+ and has a compatible fingerprint sensor.
I wrote it because I change my phone's brightness as often as I change it's volume, if not more, and I was upset I didn't have dedicated hardware for it. When Oreo launched and it added fingerprint gesture detection, I figured it was time
I own and test on the OG Google Pixel, and the app has been out for 2 weeks so I've been able to squash most bugs.
Feedback and suggestions are most welcome!
https://play.google.com/store/apps/details?id=com.tunjid.fingergestures
Click to expand...
Click to collapse
Excellent work, my friend! This works great on my Pixel 2.
You've been featured!
https://www.androidunfiltered.com/d...htness-with-fingerprint-gestures-android-8-0/
youtube10 said:
Out of curiosity, on those ROMs, how long did it take for adaptive brightness to restore the brightness to what it was before you adjusted it?
I don't think adaptive brightness and system brightness are 2 different values. It's possible you didn't give permissions to read or write to settings so that when you try reducing the brightness with adaptive brightness on, I can't read the current value of your brightness so I default to the highest. This would explain the "jump" in brightness you see while adjusting.
If you don't mind, try giving it another go and checking that you give both accessibility permissions, and permissions to write to settings. After that, with adaptive brightness on, try changing the brightness again and please let me now if the jump still occurs. Also, left and right swipes my default toggle minimum and maximum brightness respectively, so there might've been an accidental recognition of either gesture.
Click to expand...
Click to collapse
I didn't view it as a bug in the app, just a side effect of disabling adaptive brightness. For example, the screen gets roughly to its dimmest with the brightness slider at around 20% and adaptive brightness on, so then if you slide that down to 10% but with adaptive brightness off, the screen will actually be brighter (the "jump" I described before). The issue is definitely not a result of a mis-swipe, as I can see the displayed percentage changing as expected.
I don't quite understand what you mean by "adaptive brightness to restore the brightness to what it was before you adjusted it"--my experience of sliding my finger along the status bar on my old phone to change brightness was the same as sliding the brightness slider in the quick settings, which can be done whether adaptive brightness is on or off. The adaptive brightness algorithm doesn't adjust the slider.
edit: I think I understand now; you're saying that the adaptive brightness algorithm actually changes the value displayed by the brightness slider. My Pixel 2 (as well as my previous phone, the HTC 10) both do not work this way, though I know some of the phones I have used in the past do. The Pixel's adaptive brightness adjusts the actual brightness based both on the ambient light and the slider, rather than adjusting the slider to what it considers an appropriate value.
teiglin said:
I didn't view it as a bug in the app, just a side effect of disabling adaptive brightness. For example, the screen gets roughly to its dimmest with the brightness slider at around 20% and adaptive brightness on, so then if you slide that down to 10% but with adaptive brightness off, the screen will actually be brighter (the "jump" I described before). The issue is definitely not a result of a mis-swipe, as I can see the displayed percentage changing as expected.
I don't quite understand what you mean by "adaptive brightness to restore the brightness to what it was before you adjusted it"--my experience of sliding my finger along the status bar on my old phone to change brightness was the same as sliding the brightness slider in the quick settings, which can be done whether adaptive brightness is on or off. The adaptive brightness algorithm doesn't adjust the slider.
edit: I think I understand now; you're saying that the adaptive brightness algorithm actually changes the value displayed by the brightness slider. My Pixel 2 (as well as my previous phone, the HTC 10) both do not work this way, though I know some of the phones I have used in the past do. The Pixel's adaptive brightness adjusts the actual brightness based both on the ambient light and the slider, rather than adjusting the slider to what it considers an appropriate value.
Click to expand...
Click to collapse
You're right. They do seem like 2 different values. Especially that the lowest brightness setting with adaptive brightness turned on is lower than the lowest setting without adaptive brightness. I'll try getting it and the gestures to work together again.
teiglin said:
I didn't view it as a bug in the app, just a side effect of disabling adaptive brightness. For example, the screen gets roughly to its dimmest with the brightness slider at around 20% and adaptive brightness on, so then if you slide that down to 10% but with adaptive brightness off, the screen will actually be brighter (the "jump" I described before). The issue is definitely not a result of a mis-swipe, as I can see the displayed percentage changing as expected.
I don't quite understand what you mean by "adaptive brightness to restore the brightness to what it was before you adjusted it"--my experience of sliding my finger along the status bar on my old phone to change brightness was the same as sliding the brightness slider in the quick settings, which can be done whether adaptive brightness is on or off. The adaptive brightness algorithm doesn't adjust the slider.
edit: I think I understand now; you're saying that the adaptive brightness algorithm actually changes the value displayed by the brightness slider. My Pixel 2 (as well as my previous phone, the HTC 10) both do not work this way, though I know some of the phones I have used in the past do. The Pixel's adaptive brightness adjusts the actual brightness based both on the ambient light and the slider, rather than adjusting the slider to what it considers an appropriate value.
Click to expand...
Click to collapse
You're absolutely right. They are 2 different brightness values: https://stackoverflow.com/questions/29349153/change-adaptive-brightness-level-programatically
It seems the Adaptive Brightness one is hidden and not supposed to be a public api, so I am hesitant to try to change it's value. However I can try to read it's value so that it would prevent the brightness jump if adaptive brightness is on and you're trying to adjust the brightness manually. Adjusting it manually will still cause adaptive brightness to be turned off however. It can be turned back on when the screen goes off and on and you checked the option.
I asked the same question on r/oneplus.
So I've bought a OP 7 Pro just 1 month ago and I'm really paranoid about burn in.
I searched a lot about amoled technology and from what i read i assumed screen burn in it's not something recoverable. And I took all the security measures to not make it happen. Auto-brightness, screen timeout to 30s, AOD turned off, and i never leave a static image on my phone.
Today I noticed that when i plugged my phone and the colors screensaver started, the fingerprint icon left a visible mark like it was burned in. But it lasted only a couple seconds and then it disappeared. Same thing happens with the signal icon on the status bar.
So, is that screen burn in? Or it's just image retention? And why is it recovering? Should I worry about it becoming permanent? I'm not even enjoying the phone anymore :c
Sorry for my english and thank you
Not that big of a deal. Especially with screen technology these days. Walk into your local carrier store, or Best Buy, look at an old phone that has an amoled screen and that's left on all the time for display. That's burn in. When the image stays there after a long period of time and doesn't disappear when the screen is turned off and on. When I had my S8 and S9, it was noticeable that the clock and always-on home button shifted all of the time. With screen technology the way it is now, a lot of OEM skins have some sort of burn-in protection in place. I've left the screen on my 7 Pro on for hours on end, alas at the lowest brightness, with the screen timeout set to never and I've never had an issue.
I'm paranoid about burn-in too. I use navigation gestures and systemui tuner app to hide status bar. I use battery widget reborn to see battery percentage and other notifications can be seen in notifications pull down shade. Use auto brightness to change brightness more frequently. I use amoled antiburn app to check for any burn-in. All clear so far.
Since launch, Not much chatter concerning this as an issue... Enjoy your device
I have Google maps burned in..? I hate it because you can see see on a white background alot.
So I just got this phone yesterday and am now updated to the latest available 7.1 version. I noticed that the default color temperature was a bit too warm for me and I reduced it to my liking.
So now basically the colour temperature is as I want but the temperature is still the default warm tone on the lockscreen. I can see the temperature change when unlocking.
Anyone else have this issue? Any fixes?
Sent from my CPH2023 using Tapatalk
It will go to default temp on lockscreen to ensure performance for fingerprint reader. It's usually most visible when you have a blue light filter on and try to unlock, then the lockscreen is visibly cooler and it goes to normal as soon as it's unlocked. It's normal, I had it on every phone I had with optical in screen FP sensor.
Lockscreen color doesnt change so it can luminate your finger properly
Just curious. How many of you are seeing screen-burn in on your phones?
I use CF.Lumen to adjust the screen to be warmer at night. I notice some darker areas/burn-in with CF.Lumen enabled and the screen brightness dimmed to super low levels (using CF.Lumen's built-in darkness slider for Sleep mode)
What I notice is a sort of dark spot at very low brightness, and a sort of dark shadowy line running down the screen close to the left side. It's kinda annoying but I really only see it when I have text on the screen (and I'm trying to read text) at lower-than-stock dimness levels. I'm slowly getting used to it. At first I panicked thinking that my screen had burned in already at a few months of use, but when I have CF.Lumen off and I have the stock brightness slider set all the way to 0, I don't notice any lines or weird dark spots.
Then again, 0 brightness using the stock brightness slider is still VERY bright if you're coming from iOS's Accessibility settings. Android has poor screen filter settings and few good screen filter apps outside CF.Lumen and f.lux and I doubt Android 12 will change that.
So, are any of you experiencing screen burn-in? OLED burn-in is something that always has me worried. I try to avoid OLED phones for this reason, because I'm paranoid.
OLEDs have a finite lifespan. The brighter they burn, the shorter they last.
The higher energy blue emitters have the shortest life span, while red the longest.
Darker screen wallpaper, dark mode and less white icons/headers helps reduce wear.
Use manual brightness control and avoid going over 50% whenever possible. Don't use in direct sunlight... this is a killer.
Move icons and widgets periodically on the homescreen. Avoid prolonged white screen viewing and apps that are dark mode illiterate.
These practices also increase battery life substantially.
Use Screen Test to see if any damage is present.
After over 1.5 years of heavy usage and one battery replacement, my AMOLED display on my Note 10+ shows no signs of damage. How you use it day to day/what you view with it makes a big difference in display longevity.