I just Download Z-Device test and everything is ticked apart from NFC (obviously) and Temperature sensor?
I was wondering why my Temperature Sensor had an X instead of a tick. Does this mean it's not working?
Can somebody else who uses this app confirm if they get the same results.
Thanks.
Maybe the software is not reading the hardware correctly.
Tinderbox (UK) said:
Maybe the software is not reading the hardware correctly.
Click to expand...
Click to collapse
That's why I wanted to know other peoples results to see if it was the app or my phone?
I just installed Z-Device myself and the temperature sensor test is crossed out for my to, I must just be a fault in the software, maybe you should report it, As i have seen the temperature sensor working fine in all the cpu apps i have downloaded.
Tinderbox (UK) said:
I just installed Z-Device myself and the temperature sensor test is crossed out for my to, I must just be a fault in the software, maybe you should report it, As i have seen the temperature sensor working fine in all the cpu apps i have downloaded.
Click to expand...
Click to collapse
Thankyou for checking, much appreciated.
What other apps are there that are similar?
Z-Device could be looking for an external temperature sensor that measures the temperature of the environment.
I use an app called elexir to chek all my sensors and 2 sensors are shown as not installed which is pressure and temperature sensors. so i assume those sensors are for ambient temp & pressure.
Sent from my GT-I9100 using Tapatalk
simacca said:
I just Download Z-Device test and everything is ticked apart from NFC (obviously) and Temperature sensor?
I was wondering why my Temperature Sensor had an X instead of a tick. Does this mean it's not working?
Can somebody else who uses this app confirm if they get the same results.
Thanks.
Click to expand...
Click to collapse
Hi simacca,
I'm part of the developers team of Z-DeviceTest .
Answering your question:
All models ussually comes with a temperature sensor for battery, due that a very high temperature (>80º Celsius) could provoque a battery degradation, even explosion in rare cases.
The sensor is used to minimice sensor & CPU usage in order to get the battery colder or even, automatic turn off the phone in overheat events.
Z-DeviceTest controlls this sensor that you could find in battery screen test as "Temperature:".
The temperature sensor showed on main screen, is an extra sensor always included on digital compass sensor, due that the physical principle used to measure magnetic fields (Hall effect) is higly temperature dependant.
Depending on the ROM you have instaled, the access to this temperature sensor is granted or not, and if the O.S., could access and read the sensor, we detect it and show the measure, or not.
I hope to have helped you with this issue.
Best Regards.
zausan said:
Hi simacca,
I'm part of the developers team of Z-DeviceTest .
Answering your question:
All models ussually comes with a temperature sensor for battery, due that a very high temperature (>80º Celsius) could provoque a battery degradation, even explosion in rare cases.
The sensor is used to minimice sensor & CPU usage in order to get the battery colder or even, automatic turn off the phone in overheat events.
Z-DeviceTest controlls this sensor that you could find in battery screen test as "Temperature:".
The temperature sensor showed on main screen, is an extra sensor always included on digital compass sensor, due that the physical principle used to measure magnetic fields (Hall effect) is higly temperature dependant.
Depending on the ROM you have instaled, the access to this temperature sensor is granted or not, and if the O.S., could access and read the sensor, we detect it and show the measure, or not.
I hope to have helped you with this issue.
Best Regards.
Click to expand...
Click to collapse
Thanks for the reply.
I am using the stock unbranded KE7 XEU rom.
Maybe when I get the new update that's due out any time it will fix the problem.
You are wellcome.
¿Could you please confirm back if you can read battery temperature trough the battery screen test of Z-DeviceTest?
Thanks in advanced.
Best regards.
zausan said:
You are wellcome.
¿Could you please confirm back if you can read battery temperature trough the battery screen test of Z-DeviceTest?
Thanks in advanced.
Best regards.
Click to expand...
Click to collapse
Yes I can see the battery temperature
Thank you again !
Is there an apk of z-test, I have no wifi or data access (so can't get it from the market) but need to check my wifi status as trying to turn it on just returns "error".
Thanks
Matt
zausan said:
You are wellcome.
¿Could you please confirm back if you can read battery temperature trough the battery screen test of Z-DeviceTest?
Thanks in advanced.
Best regards.
Click to expand...
Click to collapse
Works for me too , using Cognition 1.07 Rom.
msiviter said:
Is there an apk of z-test, I have no wifi or data access (so can't get it from the market) but need to check my wifi status as trying to turn it on just returns "error".
Thanks
Matt
Click to expand...
Click to collapse
im not allowed to post links so...
www[dot]4shared[dot]com/file/7y7UXjvt/Z-Device_Test_v167.html
I'm using Andro Sensor app (market) for temp reading, works very well.
Related
Use gsam battery minor monitor and click apps, view sensor usage, and click android system.
For the amount of time you phone has been discharged, the pressure sensor has been on and active 99 - 100% of the time.
Now, I've tried to find ways to doable this useless pressure sensor (also know as barometer), but to no hope.
I wonder if we can work out how to disable this useless sensor..
The pressure sensor model is BMP180: http://www.bosch-sensortec.com/content/language1/downloads/Flyer_BMP180_v5_032011_web.pdf
Sent from my XT910 using xda app-developers app
the razr does not even have a pressure sensor...
Killer2k8 said:
the razr does not even have a pressure sensor...
Click to expand...
Click to collapse
+1
Andrey G. said:
+1
Click to expand...
Click to collapse
+2
XT910 - Kexec JB
pressure=DOES NOT MEAN PRESSURE SENSOR ACTIVE TIME AT ALL
means just ... working time!
Hoax here
Inviato dal mio Rasoio Motorola
Killer2k8 said:
the razr does not even have a pressure sensor...
Click to expand...
Click to collapse
You are 100% wrong. I don't feel like digging around on the Web for 20 minutes to find the links, but I did do so a few months ago and found that the hardware for both a barometer and FM radio are both definitely present in all RAZRs, just not implemented in software.
iolinux333 said:
You are 100% wrong. I don't feel like digging around on the Web for 20 minutes to find the links, but I did do so a few months ago and found that the hardware for both a barometer and FM radio are both definitely present in all RAZRs, just not implemented in software.
Click to expand...
Click to collapse
I agree with this
Sent from my HTC Sensation using Tapatalk 2
Thread Moved
As OP contains no development
I've been looking at this as well the last few weeks as a possible cause for my reduced battery drain. Ignore the pressure, it's the accelerometer on all the time that I'm curious about. In gsam you'll notice that accelerometer and pressure are listed, also, accelerometers can be used for pressure also. (currently doing that at work ) However looking at the datasheet and current draw, you would hardly notice the drain from the sensor.
I have noticed that keeping the facebook app to update every hour BUT with all the push stuff switched off in notifications, ie messages, wall alerts etc has reduced my current consumption by around 30mA. I'm currently keeping my eye on this.
As the title suggests, I'm wondering where the ambient temperature sensor is located on the device. I've read conflicting things, so I'm not sure if there is actually a dedicated 'ambient' temperature sensor or if the reading is the result of some calculation. Either way, it doesn't seem to be wholly accurate.
Also, what apps are you using to see the ambient temp sensor's reading? I'd like to hear about an app that has a clean-looking, low memory widget I could use to get a quick glance at ambient temp, pressure, and humidity. Currently using 'Temperature', which has a barebones widget that only displays the temp.
Thanks in advance.
Dont know where the sensor is. Search ambient temperature in the app store. I will say its not very accurate tho because any heat generated by the device causes it to read higher. The application lists everything you want but the widget just shows the temp.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Dont know where the sensor is. Search ambient temperature in the app store. I will say its not very accurate tho because any heat generated by the device causes it to read higher. The application lists everything you want but the widget just shows the temp.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
That's actually the app I got. Kinda weird, it's title changed to just 'Temperature' once installed (it's the one with the C° icon).
I'm much more curious about the humidity sensor. It would be neat to be able to leave my phone in a guitar case for a couple minutes and view a graph of the average humidity in there and A / B that with the room the case is in, since humidity will affect the wood! :fingers-crossed:
This module aims to fix Nexus 5 ambient light sensor issues leading to random auto-brightness spikes under certain lighting.
The issue
Sometimes the light sensor goes crazy and reports 30000 lux even in a dim light because of what auto-brightness attempts to blind you in a moment. These random spikes happen when you hold a phone at certain angles and depend on light bulbs used in a room.
The solution
The fix is implemented as an Xposed module.
Basically, it is a filter inserted near a point where native HAL communicates to Android framework. It intercepts all sensor readings and replaces abnormal 30000 lux (and 0 lux following 30000) with an averaged value from a sliding window. This affects any process that use Android sensors API including system_process, so that default Android auto-brightness works fine too (no need to use apps like Lux Dash to workaround the issue).
Installation
Download and install Xposed framework
Then install Nexus 5 Light Sensor fix module and activate it
Reboot
Usage
The module provides no user interface, nor it runs any services in a background. It only injects a proxy method to the implementation of Android sensors API. You won't be able to notice it in the main menu or in a task manager. Think of it as a patch that can be turned on and off through Xposed installer.
Source
The mod is open source (with permissive MIT licence), the source code is available on my GitHub.
Thanks
@rovo89 for his Xposed framework
@n3ocort3x and @wantabe for the initial attention and for kicking me up to finally create a new thread
and you (the community) for your feedback
More on the issue
Two major issues with the Nexus 5 ambient light sensor (original module announcement)
Palmadores said:
1. The sensor reading often jumps to 30000lx momentarily, (measured using Lux Dash in Debug mode), and so the phone blinds you for while. This happens in a repeatable fashion when you hold the phone at certain angles. Try it yourself.
2. The N5 reads zero lux even in moderate/dim light, while my old N4 still reads around 10 lux.
Click to expand...
Click to collapse
exorz said:
Using the Lux app debug mode I rotated the phone while in a room lit with incandescent bulbs and one lit with daylight. When rotating the phone I sometimes see a spike of 30000 lx but more importantly the sensor drops to 0 even though there is plenty of ambient light. During daylight I don't see the 30000 lx spikes but I still see the sensor dropping to 0 when there's plenty of ambient light.
Click to expand...
Click to collapse
Is the Auto-Brightness Functionality wonky on the Nexus5?
Aria807 said:
I think it may be bugged with Halogen lighting (correct me if I'm wrong). My home is ~ 18 years old, and we have some bulbs that have not been changed yet (yellow). Sometimes when I use my N5 under those lighting, the sensors go whack and don't register properly picking up 0lx, then spike up to 30000lx. Once I move to areas in the house with newer bulbs, the sensors work normal, picking up the right readings.
Click to expand...
Click to collapse
Well done! Auto-brightness accuracy is much improved indoors! Appreciate your work on this!
Do I need to disable the modules if I dirty flash a new Carbon nightly? Or is that not necessary
augoza said:
Do I need to disable the modules if I dirty flash a new Carbon nightly? Or is that not necessary
Click to expand...
Click to collapse
I'm not sure, cause I use stock ROM, but I guess there is no need to disable it. As I can see from Carbon sources, related parts of code was not modified at all. To be sure, please ask ROM developers or other Xposed guys.
1.1 update won't install on nexus 5 signature mismatch
Sent from my Nexus 5 using Tapatalk
ddloco said:
1.1 update won't install on nexus 5 signature mismatch
Click to expand...
Click to collapse
I know, this is my fault and this is actually stated in the module description. Please remove version 1.0 and install 1.1 from scratch.
Still coming up very bright compared to Lux. Battery drain WILL be an issue.
mcnob said:
Still coming up very bright compared to Lux. Battery drain WILL be an issue.
Click to expand...
Click to collapse
The mod only removes random spikes reported by sensors. It does not affect an algo used by stock auto-brightness (any auto-broghtness is basically a function that maps a given input value from the sensors to the screen brightness; the mod just removes some trash from the input).
AFAIK the stock auto-brightness is configured through framework-res (google: config_autoBrightnessLcdBacklightValues, e.g. http://forum.xda-developers.com/showthread.php?t=2616914). Probably there is some app/mod for tweaking these options.
Wonder if custom ROMs like Omni and CM already have the fix baked in?
Anyone tries this on something other than an N5?
Motorola perhaps?
Sent from my DROID RAZR M using Tapatalk
FirePsych said:
Anyone tries this on something other than an N5?
Motorola perhaps?
Click to expand...
Click to collapse
I'm pretty sure this wouldn't make any sense, at least with current implementation, which compares each input value against hardcoded 30000 lux.
bland.life said:
Wonder if custom ROMs like Omni and CM already have the fix baked in?
Click to expand...
Click to collapse
The problem is that a code to be patched is located in a device-independent part of Android, but only Nexus 5 build should be modified. However, I didn't research well whether there is a way to build some piece of base framework only for a particular device. Probably Omni/CM guys know better.
mcnob said:
Still coming up very bright compared to Lux. Battery drain WILL be an issue.
Click to expand...
Click to collapse
Must be a variance between different devices because on my N5 auto-brightness indoors at night looks just a little on the dim side. In brighter light it looks good to me but I can't tell you what percentages it's using. I would probably like it 2 or 3 percentage points higher indoors but I'm fine with the way it is now. At least on my device I haven't seen any noticeable effect on battery life with auto-brightness on most of the time. Still getting 5-9 hrs of screen on time with my use. I made a comment in a previous post about auto-brightness being more accurate, I was referring to the way it would constantly adjust the brightness level and the changes would be big ones. Personally I think auto-brightness is much better with the module installed and in my case useable now. No, it's not as accurate as the auto-brightness is on my One X, which is amazingly accurate, for that kind of accuracy I would use something like Lux, maybe in conjunction with the module. I would give it a shot myself but I've purchased enough apps to modify the display brightness as it is. Running stock 4.4.2.
Edit:
Forgot to mention I'm using the dimmer backlight setting in the config file for the ElementalX kernel. I don't think that makes much of a difference in accuracy, if any, just how dark the display can potentially go. I also completely forgot that the dimmer backlight and auto-brightness levels are options available in the GravityBox module. As effing long as I've used GB I've never used those two options!
abusalimov said:
I'm pretty sure this wouldn't make any sense, at least with current implementation, which compares each input value against hardcoded 30000 lux.
Click to expand...
Click to collapse
Yup. Didn't work on my Razr M.
Sent from my DROID RAZR M using Tapatalk
I don't know what the issue is lol, but I have Franco kernel so I assume I'm immune to this right?
Sent from my Nexus 5 using Tapatalk
Deeco7 said:
I don't know what the issue is lol, but I have Franco kernel so I assume I'm immune to this right?
Click to expand...
Click to collapse
It doesn't matter, which kernel do you run, ALS is a user space driver. BTW I use franco kernel too.
10000 lux
My N5 reports 10000 lux instead of 30000, very annoying
Running CM11.0 m5
zbloh said:
My N5 reports 10000 lux instead of 30000, very annoying
Running CM11.0 m5
Click to expand...
Click to collapse
Thanks for reporting. Is it reproduced on CM11.0 M5 only, did you try other ROMs? Does it show exactly 10000.0 lux? If so, I could catch this value as well.
New version 1.2 is available now:
- Always replace 0 lux with 1 lux to prevent auto-brightness changing hither and thither in a very low light environment
- Do not feed replaced values back to EMA filter (makes it more responsive to newly coming proper readings)
- Filter out 10000 lux as well (reported by zbloh)
Hello Everybody,
So after a lot of reading, it looks like this wonderful Amazfit Stratos could perfectly matches with all my new hopes and finaly
substitute for a perfect relation equipement/price ;my old school Suunto X6)
Though, there is often a "but",
I'm pretty sure this special use could interest a lot of people in specific outdoor activities, and hope we will find a way
So
I'm skydiver and would like use the watch at least under canopy for landing. (I doubt about the speed refresh while freefall, but not the matter)
Means I need calibrate manualy the altimeter on 0 (zero) before going in the plane, and landing safely after the jump on same altitude I had calibrate just before
Means probably too, the altimeter should works imperatively on just barometric data...?
Is there a solution to reach my goal? even if I should try to tamper the firmware or kind of push a special room??
Any idea is welcome))
Anyway sorry for my unperfect english
I was planning to build an apk that could do it. Because I also need it for paragliding.
Like configure current air pressure at sea level.
Calculate the current hight based on the air pressure etc.
I know the app GreatFit https://forum.xda-developers.com/smartwatch/amazfit/app-watchface-greatfit-v1-1-settings-t3791516 has the option to show your hight on the watch face.
I would be extremely wary of this. My Pace barometer is pretty accurate but the altitude isn't. I live by the sea so I have the perfect opportunity to test it. There is no way to zero or calibrate.
Interesting.
I was also planning to create an app for this, then I realized where the heck I could get the current temperature from. My pace doesn't have a thermometer, does it?
I am no expert here, but I think we need the pressure AND the temperature to accurately calculate the altitude. The altitude reading from the watch can't be accurate if the temperature isn't taken into account or perhaps the watch just gets the altitude from GPS.
thx for your answers
Anox, for what use do you wish realize this app?
So
I'm pretty sure I had read about the Stratos the altitude is linked to the GPS( after searching again, of course impossible to find
again the intel)
Effectively, On the Suunto X6 there exists also a temperature probe; I don't know if it use it to manage the altitude simultanously with the barometer
Then, looks like could be more simple to build an app than modify totaly a ROM)) that's already good news
How many times it could takes to build this kind of app?
The stratos and pace have barometer sensor, maybe it could be enough to make a try?
(i need specify with Suunto X6, by day I often have 5/10 meters of variation, I could reset and calibrate on the ground, or not,
15/20 sometimes, 30 meters when weather changes totaly though in this case we stop jumping)
I guess isn't either a problem for Istaveren while paragliding, 5 to 20 meters could be corrected by vision and experience?
Finaly
I found this
"Running mode uses GPS for altitude. trial run mode uses the barometer for altitude"
here
https://forum.xda-developers.com/smartwatch/amazfit/app-barometric-altitude-amazfit-pace-t3765765
looks like it depends quite of the mode...
eFreDosS said:
thx for your answers
Anox, for what use do you wish realize this app?
Click to expand...
Click to collapse
It's an altimeter that can show altitude based on pressure. You can also use it to measure the height of an object.
Then, looks like could be more simple to build an app than modify totaly a ROM)) that's already good news
How many times it could takes to build this kind of app?
Click to expand...
Click to collapse
I've been working on it for some time now, currently testing it. You know it's not easy to test this kind of app, 'cause I don't have a private jet. If time allows, I may release it this weekend.
I found this
"Running mode uses GPS for altitude. trial run mode uses the barometer for altitude"
here
https://forum.xda-developers.com/smartwatch/amazfit/app-barometric-altitude-amazfit-pace-t3765765
looks like it depends quite of the mode...
Click to expand...
Click to collapse
Right. And the compass widget uses GPS.
@anox:
I'm looking foreward to your app. Especially if it has the ability to calibrate the altitude.
@eFreDosS:
"Running mode uses GPS for altitude. trial run mode uses the barometer for altitude"
Click to expand...
Click to collapse
This rumor is quite persistent but was never proven and I'm quite sure it is wrong. From my experience with the pace it seems, that every activity with altitude measurement is starting by using the altitude from the GPS to calibrate and later on some mix of GPS and barometer to measure the changes in altitude. To realize this one must use the data from the pace directly since as soon as the data is processed in the phone app, altitude data is corrected on the base of an online altitude/shape map.
The stratos and pace have barometer sensor, maybe it could be enough to make a try?
Click to expand...
Click to collapse
that every activity with altitude measurement is starting by using the altitude from the GPS to calibrate and later on some mix of GPS and barometer to measure the changes in altitude
Click to expand...
Click to collapse
Remember slightly in all my reading some people had same feeling as you....you surely right!
So, with what we have as data;
"yes": shutdown the gps source informations, only use barometer and add possibility to reset/calibrate ??
cause I don't have a private jet.
Click to expand...
Click to collapse
Me neither)) It's winter, I don't jump currently(anyway I still don't have the Stratos dream), though perhaps someone on the thread could help to test the altitude tool created ?
nhedgehog said:
@anox:
I'm looking foreward to your app. Especially if it has the ability to calibrate the altitude.
Click to expand...
Click to collapse
eFreDosS said:
Me neither)) It's winter, I don't jump currently(anyway I still don't have the Stratos dream), though perhaps someone on the thread could help to test the altitude tool created ?
Click to expand...
Click to collapse
Check it out https://forum.xda-developers.com/smartwatch/amazfit/app-paceup-v1-0-altimeter-pace-stratos-t3893743
simply "WoNdErFuL" thank you very much for your precious time
Anyone else having problems with automatic brightness changes?
Every evening when it gets dark the brightness level goes to the lowest level, which is much to dark to read anything. Every evening I have to adjust the ''automatic'' level to halfway the level-slider, multiple times.
Do you have night mode enabled ?
I have this feature enabled from 9pm to 7am and indeed the auto brightness goes lower than normal value during this time slot .
Pouic said:
Do you have night mode enabled ?
I have this feature enabled from 9pm to 7am and indeed the auto brightness goes lower than normal value during this time slot .
Click to expand...
Click to collapse
No eye comfort modus
No Adaptive sleep modus
Only 'dark modus' enabled day and night
The same is happening to me. The brightness of the screen in darker lights is too low. Every time I move the slider to upper brightness but next time I open the screen is lower again.
marselcj said:
The same is happening to me. The brightness of the screen in darker lights is too low. Every time I move the slider to upper brightness but next time I open the screen is lower again.
Click to expand...
Click to collapse
I tried to wipe the system settings but the problem persists. I hope they can fix this in an update
BartKey said:
I tried to wipe the system settings but the problem persists. I hope they can fix this in an update
Click to expand...
Click to collapse
I might state the obvious, but the sensor is a bit high up on the device and it might be covered by your phone case, u sure it's not just a goof with an off brand cover?
The sensor is not covered. I use an original OnePlus cover.
Strange thing ... Everybody or at least majority of Oneplus Nord 2 owners had complained about automatic brightness . It's true in my case as well but now problem is solved with a 3-d party apk . Velis Auto Brightness from G.Play . Calibrating autobrightness is very accurate but the app remain active in background all the time and I didn't know how this affect battery drain . I read all OnePlus latest phones have this annoying bug and it's pitty none of latest updates solved it , worst here on XDA or OnePlus forum no one offer any solutions to calibrate automatic brightness .
Some smart guys said there is not "automatic brightness" but "adaptive brightness" so we had to learn phone AI how to adjust brightness a few days and then restart the phone . This are childish thoughts of those which are nothing to do else .
So , what do you think about this ? There are solutions to calibrate or fix this issue ?
I noticed that when the phone is on below 15% or lower and the battery saver is on ( for me it's 10%) the phone brightness goes to automatic mode and it becomes even less bright. I think it has to be a certain feature which is connected to battery saving IMO.
I'm using Velis for 3 months as well. This solves the problem. But OnePlus definitely should solve this.
Even latest update v11.3 EU, doesn't solve it. I even did a factory reset. 3 hours work to reset everything back as is was, for nothing...
Look at a possible solution (for me didn't work) :
"
stevendumondCupcake
stevendumond , Sep 25, 2021 :
stevendumond said: ↑
FYI: I did this a few minutes ago. I think that may be it. Before I did this, the screen brightness did not work at all. I could slide that slider up and down and nothing ever changed on screen brightness, auto or manual. Now it works! On auto and manual!
Hopefully this is the "fix"! But disabling a feature is NOT a fix, it's a workaround. Luckily I don't need that feature
Click to expand...
Click to collapse
So far the screen brightness has not faded into darkness. Phone is working fine now. This is a workaround that works.
Settings> Battery> Battery Optimization> Advanced Optimization (3 dots in upper right)> Sleep Standby Optimization: OFF
Click to expand...
Click to collapse
Since A.14 OTA , Adaptive Brightness is better but not entirely satisfying . It seems they solve bugs by little steps ... which is quite annoying !
muppetz said:
Since A.14 OTA , Adaptive Brightness is better but not entirely satisfying . It seems they solve bugs by little steps ... which quite annoying !
Click to expand...
Click to collapse
Not better here with a.14. Same problem as before... Indeed very annoying
BartKey said:
Not better here with a.14. Same problem as before... Indeed very annoying
Click to expand...
Click to collapse
Minimum level (especially in low light) is a little bit higher , sensitivity is more accurate and transition between levels is also a little bit faster . I'm pretty sure there are some improvements , that's a fact not a feeling .
muppetz said:
Minimum level (especially in low light) is a little bit higher , sensitivity is more accurate and transition between levels is also a little bit faster . I'm pretty sure there are some improvements , that's a fact not a feeling .
Click to expand...
Click to collapse
Let's hope it improves a lot more. My previous devices, Moto g, Moto G5 plus, never had such problem, even on any custom ROM...
BartKey said:
Let's hope it improves a lot more. My previous devices, Moto g, Moto G5 plus, never had such problem, even on any custom ROM...
Click to expand...
Click to collapse
Oh , yes I still have Motorola One Vision and automatic brightness is flawless ...