Database Info

[APP] Different auto-brightness

I was tired with the stock autobrightness sensor always setting screen too bright for my eyes - i read in the darkness at night. So i wrote this little thing (thanks to britoso).
Right now it has 4 different brightness settings depending on the ambient light.
as always - created for NEXUS One, tested on FroYo. Needs ROOT
Known issues - not smooth brightness change..
Donno how it will affect the battery life, i may change the sensor sensitivity in the future.
pre-alpha
Comments welcome.
p.s. remember to disable system auto-brightness in settings.

Just installed, I'll report back!

Sounds awesome! Will check it out after work

I will also give it a try

I have te opposit feeling i don't like auto-brightness because it's always to low for me (next to the ipod my screen is lot darker in same light condition)...
I will look into your app later today but maybe an idea to have a slider for adjusting it higher or lower by yourself to fit everyones needs
Will try later, but sounds good to me!

jaapschaap said:
I have te opposit feeling i don't like auto-brightness because it's always to low for me (next to the ipod my screen is lot darker in same light condition)...
I will look into your app later today but maybe an idea to have a slider for adjusting it higher or lower by yourself to fit everyones needs
Will try later, but sounds good to me!
Click to expand...
Click to collapse
hm ye i think ill add some customization so u can select preferred brightness for different lights.. its not hard just need time..
also i still havent decided on how much "steps" should it have..
right now its 4 - full daylight, in-home light, dark-room light, full darkness..
i can set it to a max of 255 steps.. but i guess its not needed + i think that the more sensitive the sensor is the more battery it consumes.. although im not sure

Great idea. Runs fine.
some suggestions:
1) add a progress bar (0..max_value) set to the current sensor value. Alongside the digital value.
2)show the current brightness setting next to or below the sensor value. A progress bar with 4 stops will look good here too.
Its nice to see my android react to its surroundings

Alright unfortunately doesn't work on CM 5.0.8 which is also written above
Can it be customized for it or not?

britoso said:
Great idea. Runs fine.
some suggestions:
1) add a progress bar (0..max_value) set to the current sensor value. Alongside the digital value.
2)show the current brightness setting next to or below the sensor value. A progress bar with 4 stops will look good here too.
Its nice to see my android react to its surroundings
Click to expand...
Click to collapse
does it works ok with ur led app? 2 programs abusing shell at a same time
can u also check if desire got the same path that i PMed you?
Paraglider1982 said:
Alright unfortunately doesn't work on CM 5.0.8 which is also written above
Can it be customized for it or not?
Click to expand...
Click to collapse
ill take a look tomorrow..

t0ol said:
does it works ok with ur led app? 2 programs abusing shell at a same time
can u also check if desire got the same path that i PMed you?
Click to expand...
Click to collapse
I've not been successful with the max_brightness setting for the led yet.
Does not matter how many apps open their own shell, its important that the shell is reused though.
The desire path should be similar to the path for LEDs. /sys/devices/platform/leds-microp/....

britoso said:
Does not matter how many apps open their own shell, its important that the shell is reused though.
Click to expand...
Click to collapse
guess thats why i receive random FCs sometimes with my app..

hi,
just ran across your app.
Do you think there is a way to lower the brightness below androids default low setting? It is still to bright for me at night, so would be great to have something like a "night-mode". i do not want to disable auto-brightness, that works fine for me, it is just the minimum setting that bothers me.

this might end up being very nice after a few updates....brightness level on Android NEVER goes to minimum level even at night which results in useless battery drain.

hm, so who can do this? A simple widget that sets brightness to the absolute minimum...

you can use scripter (needs root,busybox) to run a simple command that does it.
Code:
echo 0 > /sys/devices/virtual/leds/lcd-backlight/brightness
max brightness is 255
Above script as a qr-code thats scannable in "scripter"
{
"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"
}

watercool said:
hm, so who can do this? A simple widget that sets brightness to the absolute minimum...
Click to expand...
Click to collapse
There is a widget light that. I am personally looking for Automatic solution with possibly adjustable light sensor sensitivity

britoso said:
you can use scripter (needs root,busybox) to run a simple command that does it.
Code:
echo 0 > /sys/devices/virtual/leds/lcd-backlight/brightness
max brightness is 255
Above script as a qr-code thats scannable in "scripter"
Click to expand...
Click to collapse
.. thanks! just found out i can do this with tasker too
tasker has been released today to the market
edit: hm, ok.. screen is still to bright with value = 1

make sure auto brightness is off.

There's an app that was posted in this forum which I just found free in the Market
App Title: Dimmer (Night Mode)
Dev: geekyouup
Nothing automatic about it. Opening the app sets brightness to 10. Open again and it says brightness=90.
Sorry if this doesn't help, but seemed relevant.

This app definitely has potential. Would love the ability to fully customize the levels and cut off points (let the user define the number of brightness levels, the brighness %, and the light sensor ranges). Would be PERFECT if it also integrated with settings profiles or simply had a low battery brightness default option. Because right now I use settings profiles to lower the brightness when I reach low battery and unfortunately right now it looks like your app overrides that.

Save Battery Power by 30 percent or more

People who design phones, and set and sync them up for the market, always ignore one thing. Battery backup.
Screen Display ( Screen on time) eats away the most of it, since most of us use Whatsapp, Mails and Text and Facebook and most of the time if we use the 'USEFUL' ( as claimed ) Auto Brightness feature, we still see that most of this Auto Set Brightness is getting wasted.
In the Manual Mode, it is tiresome to on and off set the Display Brightness from Zero ( In a dark room, reading mode) to Driving in the Open (100% on)..
This is where LUX helps..
You can assign (LINKING FEATURE) the Various Luminousity Levels in *LUX ( 1 Lux to as much as 40,000 lux or more) to the Screen Brightness Levels (0% to 100%) As and when You require, and Not what an Android Phone Developer wants you to Compromise with.
For Instance :
In Default Mode on most Androids, The settings are:
In dark Room, Read Mode at Night with all lights off, The *Lux Level of 2-3 gives 25% Screen Brightness ( This is Too much even for eyes to Handle !!!)
Similarly in a Normal Room or Office, with Lights On (Lux Level Varying from 50 to 1500) the Display level is 50% to 80%...(Android Default)
This is the Normal range where most of our phones are operated throughtout our indoor days...
On the upper side , Outdoors while Driving or at a Club or Pool (Lux Level 35,0000 Plus) the Display goes up to 100% (This is Valid and acceptable)
With Lux You can automatically Reduce your Screen Brightness by as much as 50% And This Overrides the Default Android Setting which we have no option but to Accept
In Read Mode (dark room) with Lux Level 2-3 / I can assure you that Brightness Zero -10 works more than comfortabely Good.
Most of you would Set (Link) that to Zero Only ...
And in Normal Indoor Day to Day, (depending on lights in the room) , A Lux Level 50-1500 , one can read more than comforably well with Display set between 25% to 30% (Mine is set at 28%)
However for 30,000 Plus Lux Level, ie Outdoors, I have set it to 100% Brightness ( same as default )
This alone gives me around 30-40% battery boost and its No Joke that after 1 hours talk time and 2 hours screen on with wifi / 2g/3g I still have more than 50% battery remaining till late evening, which earlier needed a recharge at late afternoons.
There also is a MANUAL option, or WAKE up option..where LUX one set Manually STAYS on a Fixed Level on days when u want to save Battery / Or resumes to That Assigned by default on phone wake up
More features are below
★FEATURES★
■ Custom auto brightness.
■ Sub-zero brightness to make reading in the dark significantly less irritating.
■ Battery efficient
■ Handy brightness widget
■ Option to use the camera to read in ambient light.
■ Power-user settings such as choice of interpolation, sensor debugging, and linked sample editing.
■ Backup to SD.
■ 'Ascending' auto mode for phones with inaccurate light sensors.
■ Gradual fade for backlight adjustments.
■ Astronomer mode adds a red filter to the screen to preserve the eyesight of stargazers.
■ Jitter control to prevent constant small changes to the backlight.
■ Automatic night mode, to change the colour temperature of the display for comfortable night time viewing.
■ Add app specific exceptions via sleep mode
■ No ads, or other nuisances.
■ Tasker and Locale support!
Preview:
{
"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"
}

There's already an official thread by the actual Dev of the app here

[2.3+]NightLamp: Sleep better at night!

NightLamp turns your phone into an intelligent night light and clock, allowing you to sleep with ease.
If you need a little bit of light before going to bed, this app is perfect for you! It will automatically fade to black after at a preset time. Woke up during the night? Simply tap the screen or activate one of the sensors to turn the light back on again.
If you need a brighter light to move around the house, just flip the phone over and the flashlight will turn on! Woohoo!
You can control the light using various sensors on the phone:
-Flip the phone over to activate the camera flashlight
-Shake the phone to toggle the screen
-The phone responds to the ambient light, turning on and off as needed
-Voice recognition to turn the light on/off using hotwords
Note: Voice recognition is very beta right now.
{
"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"
}
***Alpha software, may blow up.***
The Android API that involves camera and sensors is a pain to support on all devices, because there is no unified way to do something like turning on the flashlight. So it would have to be supported for each phone model, which takes some time, so be patient as I work the kinks out.
Please do not give negative reviews due to crashes, because this app still needs testing to support a lot of devices...
If you do use the app, please do shoot me an email about your experience with it if possible
Tested to work on Galaxy Nexus so far.
Play store link

Some word on power consumption please....

RmatriX1218 said:
Some word on power consumption please....
Click to expand...
Click to collapse
Since it puts the screen at full brightness for a while, I highly recommend hooking the phone to a power source. If you have an AMOLED screen, the power drain from the app while the screen is dim would be small, but it would still drain the battery faster than if the phone is sleeping.

as I tap on Start, it shows a grey clock on white background but I hear a continuous BEEP once every second almost. Galaxy S4 GT-I9505 latest stock firmware ITV
that's the sound the voice recognition beeps to tell you it's listening.
disabling the voice recognition, the sound goes away as well.
You should also enable the android power saving so to reduce cpu and network usage like it almost does in standby.
Nice little app.

Zibri said:
as I tap on Start, it shows a grey clock on white background but I hear a continuous BEEP once every second almost. Galaxy S4 GT-I9505 latest stock firmware ITV
that's the sound the voice recognition beeps to tell you it's listening.
disabling the voice recognition, the sound goes away as well.
You should also enable the android power saving so to reduce cpu and network usage like it almost does in standby.
Nice little app.
Click to expand...
Click to collapse
Google borked the speech recognizer code in recent versions (since Android 4.1) with a forced beep sound, I tried to mute it but it doesn't seem to work uniformly across devices, so I will have to change the speech recognition engine in the future.
I will look into power saving, thanks for letting me know!

You're welcome!

very nice UI =)

Zibri said:
as I tap on Start, it shows a grey clock on white background but I hear a continuous BEEP once every second almost. Galaxy S4 GT-I9505 latest stock firmware ITV
that's the sound the voice recognition beeps to tell you it's listening.
disabling the voice recognition, the sound goes away as well.
You should also enable the android power saving so to reduce cpu and network usage like it almost does in standby.
Nice little app.
Click to expand...
Click to collapse
Added a new version where you can swipe the screen to adjust brightness of the front light. Additionally, speech recognition is no longer enabled by default due to bugs.

Cool app. I ended up using it for reading so I don't have to turn a light on but if I fall asleep then it'll fade down and all is well.
Works well on an Asus TF101 running 4.2.2 (katkiss v224 based on eos4). I can confirm the continuous beep bug too with the volume to silent fix.
One thing that would be awesome down the road would be to have a continuous fade of the display brightness over the course of the time you set. For example say you set the fade for 10 minutes, three minutes in it'll have reduced to 70%. Don't know if it's doable but it's just an idea.

mmm.waffles said:
Cool app. I ended up using it for reading so I don't have to turn a light on but if I fall asleep then it'll fade down and all is well.
Works well on an Asus TF101 running 4.2.2 (katkiss v224 based on eos4). I can confirm the continuous beep bug too with the volume to silent fix.
One thing that would be awesome down the road would be to have a continuous fade of the display brightness over the course of the time you set. For example say you set the fade for 10 minutes, three minutes in it'll have reduced to 70%. Don't know if it's doable but it's just an idea.
Click to expand...
Click to collapse
Sounds like a nice improvement, I'll look into it.

[APP] AMOLED PWMfree

Summary:
A simple application that uses a transparent overlay to dim the device brightness, effectively removing PWM.
Download PWMfree
More Information:
Why PWM is such a headache
Brief explanation about PWM
Default brightness control:
{
"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"
}
PWMfree brightness control:

Thanks, runs on my S9 on AOSP 8.1. Affects auto-brightness a bit but seems to work as intended. Great work!

Wrong section man

Can someone explain to me what this app on s9 does?

Its suspicious

@amakuramio
Not sure why the installation is prevented.
The application itself just creates an accessibility overlay and changes the permission for /sys/class/backlight/panel/brightness to prevent access from liblights.
Edit:
Seems like this is the common behaviour for non-playstore apps: disable Google Play Protect

The brightness does not change while sliding the slider, only after releasing the slider. Please fix, thx.

Can this work on other models (like my Galaxy A3 2017 AMOLED) ?

vratnik said:
The brightness does not change while sliding the slider, only after releasing the slider. Please fix, thx.
Click to expand...
Click to collapse
Unfortunately not possible.
victo24dord said:
Can this work on other models (like my Galaxy A3 2017 AMOLED) ?
Click to expand...
Click to collapse
The overlay itself should work on every device, only the brightness slider override that requires root is device dependent.
But this isn't particularly well-working, i will probably ditch this override and just add a widget slider so it can be used without root.

So is this root only? Cause I saw my screen change brightness immediately after turning accessibility access on, and I'm not rooted, stock rom.

@qb74
Root permission is used to prevent liblights (android system brightness handler) from accessing the kernel brightness path (/sys/class/backlight/panel/brightness).
The brightness slider on the notification bar then only modifies the transparency of the accessibility overlay, not the display (kernel) brightness.
Without root permission it controls both the overlay and kernel brightness, but this prevents the pwmfree usage as the kernel brightness needs to be at 100% to avoid pwm dimming.

Trying out on s8+. But weird thing is, when enabled, if you lower the brightness to 0% the screen becomes completely dark. It should not happen like this, I presume. The app has root access too.

@parser
The lights service might be different on the S8 and is not correctly halted by the application.
Here is a first version that works without root and only relies on the accessibility service: (link in the original post)
It locks the device brightness at 100% and uses it's own slider to control it.

Wootever said:
@parser
The lights service might be different on the S8 and is not correctly halted by the application.
Here is a first version that works without root and only relies on the accessibility service: pwmfree.apk
It locks the device brightness at 100% and uses it's own slider to control it.
Click to expand...
Click to collapse
So this version works with non-root? Great! Why does the brightness need to be 100%? From the looks of your graph, all brightness levels seem more consistent?

Wootever said:
@parser
The lights service might be different on the S8 and is not correctly halted by the application.
Here is a first version that works without root and only relies on the accessibility service: pwmfree.apk
It locks the device brightness at 100% and uses it's own slider to control it.
Click to expand...
Click to collapse
Hmm, well than I hope you make this wonderful app s8/+ compatible too
Thanks for your work mate. Would love to use it :good:

qb74 said:
So this version works with non-root? Great! Why does the brightness need to be 100%? From the looks of your graph, all brightness levels seem more consistent?
Click to expand...
Click to collapse
Only the device (kernel) brightness needs to be set at 100%, at this stage the amoled panel only uses a short 59hz vsync signal (this is the small amplitude on the graph).
Anything below ~95% uses the amoled typical 240hz pwm dimming.
The pwmfree overlay now dims the full kernel brightness by decreasing it's transparency, this is somehow similar to lcd contrast dimming.
@parser
The new version should work on all amoled devices, although the widget type brightness slider is a bit less comfortable than the android system one.

Wootever said:
Only the device (kernel) brightness needs to be set at 100%, at this stage the amoled panel only uses a short 59hz vsync signal (this is the small amplitude on the graph).
Anything below ~95% uses the amoled typical 240hz pwm dimming.
The pwmfree overlay now dims the full kernel brightness by decreasing it's transparency, this is somehow similar to lcd contrast dimming.
@parser
The new version should work on all amoled devices, although the widget type brightness slider is a bit less comfortable than the android system one.
Click to expand...
Click to collapse
Trying it atm, the only down side is, as u said, adjusting the brightness by hand. If I am in a game and need brighter screen, have to go desktop and adjust it :/
Would it have an effect on battery efficiency too?

@parser
The overlay is managed by SurfaceFlinger and shouldn't cause any impact. The amoled panel seems to work identical with the contrast dimming and i would guess the battery usage is similar, but i can't tell for sure yet.
As for the brightness slider, i think this can be placed on the notification bar instead, which should increase the usability.

Wootever, you're BEST!
P.S. I sold my Note 8

I installed it but it won't run, s7 stock rooted.

Development [APP] PixelParts - V1.0 [CUSTOMS]

{
"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"
}
About the app
PixelParts began as a simple High Brightness Mode (HBM) tool. Since then, it has evolved to include a detailed battery information panel, a display saturation level adjuster, charging limiter and more. The app now offers a wide range of features, transitioning from its original function as an HBM tool to a hub for device tweaks and stats on customs, with a lot more planned going forward. The application needs to be included at build time, so this is a project for device maintainers from other ROMS to use if they'd like.
Current features​
CategoryFeatureDescriptionQS TileRequired kernel changesBatteryBattery infoView various battery informationN/AN/AStart/Stop chargingStart/stop charging at specific percentagesN/AN/ADisplayHigh brightness mode (HBM)Directly enable high brightness modeYesN/AAutomatic HBMAutomatically enable high brightness mode based on sunlight intensity (lux)YesN/ASaturationControl the saturation level of the displayN/AN/ALEDsTorch strengthAdjust the brightness of the Pixel Torch flashlight QS-TilePixel TorchN/AUi-BenchJitterCalculate rendering jitter.N/AN/AUSBUSB 2.0 fast chargeEnable CDP mode for faster charging on USB 2.0 ports.YesCommit 1/1
Including PixelParts in your AOSP build
1. Remove HbmSVManager
Commit 1/2 (vendor)
Commit 2/2 (device tree)
2. Clone PixelParts to packages/apps/PixelParts in your AOSP source tree
Run the following cmd at the root of your source tree:
Code:
git clone https://github.com/Evolution-X-Devices/packages_apps_PixelParts packages/apps/PixelParts
3. Include the app at build time
Commit 1/1 (device tree)
This includes the device.mk file from the PixelParts repository, which will add the PixelParts application, its initialization script (init.rc), and the necessary security policies (sepolicies) to your AOSP build during compilation.
Testing new changes
When testing new changes, it is much faster to compile the application standalone and update it manually rather than running a full AOSP build. Please note that some changes may require you to chmod 0666 sysfs nodes and set selinux to permissive. When compiling a full AOSP build, this is not needed assuming the init cmds and sepolicies have been properly configured.
Lunch your device and run the following cmd:
Code:
m PixelParts
This also assumes you are already running an AOSP build including PixelParts as a priv-app in /system_ext.
Screenshots
Source code
GitHub - Evolution-X-Devices/packages_apps_PixelParts: Parts application for pixel 6/7 series
Parts application for pixel 6/7 series. Contribute to Evolution-X-Devices/packages_apps_PixelParts development by creating an account on GitHub.
github.com
Translations
Crowdin
crowdin.com
Credits​
WorkAuthorBase preference fragment & CustomSeekBar preferenceNeobuddy89Original AutoHBMServiceHikari no Tenshi & maxwenShakeUtilsAmeChanRainFirst launch warning dialogRamyskiLeonids particle systemPlattysoftRandomized color particle effectLorD ClockaNUSB 2.0 Force CDP kernel changeeng.stk

Reserved

Thanks! this app helps so much!

Thanks. I guess it is not possible to use it on stock rom? Could not find a reason to test custom roms on this device tbh

Automatic HBM is someting I would like a lot Will be available on OP9 Pro also?

I've just checked the code and it seams to me that it could be improved in that way:
1) set HBM on immediatelly when lux > luxThreshold and hold it in time KEY_HBM_ENABLE_TIME + start timer to be sure that HBM goes off after the amount of time)
2) set HBM off when lux < luxThreshold or time KEY_HBM_ENABLE_TIME finished. Hold HBM off in the KEY_HBM_DISABLE_TIME (to release and cool a display)
This helps to protect the display - typical use case: I have turn-by-turn navigation on, the sun is shining so I want to switch HBM off after a while to protect my screen. It would be great if HBM can go off when temperature is high also (at least battery temperature, better phone temperature)

thuryn said:
I've just checked the code and it seams to me that it could be improved in that way:
1) set HBM on immediatelly when lux > luxThreshold and hold it in time KEY_HBM_ENABLE_TIME + start timer to be sure that HBM goes off after the amount of time)
2) set HBM off when lux < luxThreshold or time KEY_HBM_ENABLE_TIME finished. Hold HBM off in the KEY_HBM_DISABLE_TIME (to release and cool a display)
This helps to protect the display - typical use case: I have turn-by-turn navigation on, the sun is shining so I want to switch HBM off after a while to protect my screen. It would be great if HBM can go off when temperature is high also (at least battery temperature, better phone temperature)
Click to expand...
Click to collapse
There are some major improvements coming to the HBM aspect of the app. One of them being the ability to define a temp threshold. The entire autohbm service is being rewritten, and it's preference and sub preferences will be relocated to their own fragment/activity soon.

AnierinB said:
There are some major improvements coming to the HBM aspect of the app. One of them being the ability to define a temp threshold. The entire autohbm service is being rewritten, and it's preference and sub preferences will be relocated to their own fragment/activity soon.
Click to expand...
Click to collapse
really, really cool, thank you a lot fot this

Moved autohbm preferences into their own fragment. Finishing the AutoHBMService rewrite and adding a temperature threshold now.
PixelParts: Move autohbm preferences into their own fragment · Evolution-X-Devices/[email protected]
Signed-off-by: AnierinB <[email protected]>
github.com
PixelParts: Display the current lux level in AutoHBM fragment · Evolution-X-Devices/[email protected]
During onSensorChanged, the lux level is set as the summary for the current_lux_level preference. Listener is registered when enabling the main switch and when the fragment is resumed (only if the...
github.com

That's great. Just my experience today with my OP9Pro. I was reading PDF file outside, on the sun, HBM off and event thought, battery temperature (other sensor is not present) shows 53 °C. I don't know what makes the hear - CPU or display, but it could be good if CPU frequency goes down for a while or display goes to lower brightness. Or 53 °C is OK, I don't know.

One more experience with heating - I've found that when I ride a motorbike, turn-by-turn navigation on, even if display is on low brithness the phone heats a lot and battery is not charged because of that. So some CPU throttling is needed

thuryn said:
One more experience with heating - I've found that when I ride a motorbike, turn-by-turn navigation on, even if display is on low brithness the phone heats a lot and battery is not charged because of that. So some CPU throttling is needed
Click to expand...
Click to collapse
Most definitely not a result of the app.

AnierinB said:
Most definitely not a result of the app.
Click to expand...
Click to collapse
Of course not, it's like an advice for the next feature ;-)

thuryn said:
One more experience with heating - I've found that when I ride a motorbike, turn-by-turn navigation on, even if display is on low brithness the phone heats a lot and battery is not charged because of that. So some CPU throttling is needed
Click to expand...
Click to collapse
The problem with heat, overall, in my experience is related to one thing; the sun. If the phone is charging on my Dash and I'm in a position where the phone is in the sun, the heat goes up quickly. Otherwise, usage has never caused heat with this phone as it did with the P6P

HipKat said:
The problem with heat, overall, in my experience is related to one thing; the sun. If the phone is charging on my Dash and I'm in a position where the phone is in the sun, the heat goes up quickly. Otherwise, usage has never caused heat with this phone as it did with the P6P
Click to expand...
Click to collapse
Interesting. I've found that also - the sun. But the CPU is also the source of heat (because I ride after sunset). Anyway, I've found a solution - slow down the CPUs by Tasker.

Great app. Just curious, will adaptive charging work together with stop charging in pixel parts? (Assuming i set the stop charging at 100%) or it will disregard the adaptive charging and charge it to 100% and stop there