Related
i've had my phone since launch and ever since my screen brightness gets automatically reduced due to overheating.
At first, the screen will dim itself ever so slightly. After a few seconds later, it returns to normal brightness and it repeats itself.
Eventually, i notice upper half of my phone as well as the screen itselft getting really hot and the brightness dims permanently.
I usually keep my brightness setting at the highest level but when i go into the menu to increase the brightness setting back to highest, it tells me the brightness is reduced due to overheating. only way to increase the brightness back to highest is to turn off the screen and let it cool down for a few min.
whenever this happens im usually browsing the internet for no longer than 10 min before this kicks in. i seriously dont think im using too much cpu by browsing forums for this super phone to be overheating.
i've read other post regarding auto brightness feature causing issues but i have not enable this feature on my phone. and its kinda hard to believe that i have to lower my brightness to prevent it from overheating.
anyone having this issue? man i'd hate to return this phone and start from scratch. tia
I would love to hear more about this...My experience matches yours perfectly. Does everyone's phone do this? If enough people say no I'm going to get a new one...it is absurd. I got those phone almost primarily for it's beautiful screen which I can't see at full brightness for more than a minute or two!?? fnck that.
Is it possible for us to get a brand new replacement unit even if your 15 day return period is over? Assuming that other users are not experiencing the same problem.
Mine does this as well, I think it's some kind of fail safe if your phone is running hot cranking up the brightness is just going to add more heat so they limit it while it's running hot. Once it cools down then it will allow it again
I have this same issue, I have to recharge above 30 percent to get the point where I can max the brightness up again
Hmmmm... guess im not the only one with this issue and hoping that it is addressed in the future update. However, it seems odd that no one brought this up? Could it be that there are only a few of us that are affected? If so, im beginning to think that this is a hardware defect?
Ive had the phone since day one. I am not having this problem. The only time it ever gets noticeably warm is when using the phone for extended periods while charging. And this is not hot like some people are reporting. I would try exchanging the phone.
Mine did this the other day, I normally have auto brightness on but I was showing a photo so i went to turn it off and crank the brightness up but it didn't let me. I pulled the battery for 10 seconds and it let me do it.
I think alot people are not experiencing this issue because they either keep the auto brightness feature turned on or keep the brightness setting at a low level. I dont wanna exchange my phone if im gonna have the same issue. What can i do?
icexige said:
I think alot people are not experiencing this issue because they either keep the auto brightness feature turned on or keep the brightness setting at a low level. I dont wanna exchange my phone if im gonna have the same issue. What can i do?
Click to expand...
Click to collapse
You may be on to something.... I rarely ever have my screen at 100%, mostly because its just too bright for me.
Although, I did watch 2 hours of video (1 hour from the SD card, one streaming from Netflix) at full brightness, and never had a heat issue. A little warm, maybe, but certainly not hot.
This thread deals specifically with the 'Auto brightness backlight flicker'. Which only occurs when the phone is set to 'Auto brightness'.
This does not deal with the various other screen glitches, or the constant flicker at various brightness levels when looking at grey screens.
Please do not get the two issues confused.
_____________________________________________________________________________________________
I have observed a few patterns, on two seperate handsets with the same symptoms....
*Firstly, the flicker occurs while the CPU is under load, and particularly at lower battery levels.
*Secondly, The flicker occurs momentarily when you plug in a charger.
*Thirdly, The flicker doesn't occur while the device is charging.
*Fourthly (is that even a word), The flicker is often seen immediately after a screen settles, such as when the screen stops moving after scrolling.
All of these things are evidence of a power management issue. As if the backlight voltage is not being regulated correctly.
I did some more testing over the last few hours and have found something interesting. If you go to 'Settings' - 'Developer Options' - and enable 'Show Screen Updates', your phone will blink the screen different colours whenever the screen is updated. I found that when the screen settles, the screen is updated one final time, just a moment after it has settled. This is exactly when the flicker occurs. As i see it, this is further evidence that the flicker is power management related.
It seems to me that when the CPU goes from load to idle and changes its power draw, the backlight voltage regulation does not filter these fluctuations and the backlight flickers.
The question is, can this be altered either by the power management built in to the kernel, or by other power management software? Or is it a physical design flaw in the power regulation circuit?
The fact that the fluctuation only seems to occur when the brightness is set to auto leads me to believe that it indeed can be fixed with software.
If it was a physical supply voltage fluctuation when the CPU goes from load to idle, it would surely flicker all the time, not only on Auto Brightness.
I assume that the CPU voltage is altered by the kernel as the load level changes.
My question is, if the governor is changed to one which doesn't allow the CPU to scale or voltage step, does the issue go away?
Is there anyone out there who has rooted their device and can test my theory? I don't want to root my device as I may need to send it back DOA (it's only a day old).
If you can change the governor to a profile which doesn't allow stepping or voltage adjustment (100% Voltage and Frequency all the time), and the problem goes away, we have an answer and HTC can work on developing a new Kernel to fix the issue.
Thanks!!
Sentinel196 said:
Please do not get the two issues confused.
Click to expand...
Click to collapse
It is highly likely that all the graphics issues are related. This includes various types of flickering, notification bar corruption, and strange bands in the camera app. Similar issues occurred with the Teg3 Asus Prime when it launched and all were corrected with updates. There are also some performance variations that can be seen in benchmarks when the issues are at their peak that go away when the phone's rebooted.
Nvidia, not HTC (or the devs) controls the Teg3 low-level code, drivers, and kernel. All this has been discussed in the other two threads. As has a communication from HTC UK received yesterday that they've identified the issue and will be issuing an update (not 1.29) to address it.
64 pages of flickering and graphics issues discussion here:
http://forum.xda-developers.com/showthread.php?t=1617009
Thanks for the info. I'm well aware of the other thread and have been following it closely.
Not looking to start a debate about the cause and if the problems are related. Just looking for someone to help me test my theory.
Sentinel196 said:
This thread deals specifically with the 'Auto brightness backlight flicker'. Which only occurs when the phone is set to 'Auto brightness'.
This does not deal with the various other screen glitches, or the constant flicker at various brightness levels when looking at grey screens.
Please do not get the two issues confused.
_____________________________________________________________________________________________
I have observed a few patterns, on two seperate handsets with the same symptoms....
*Firstly, the flicker occurs while the CPU is under load, and particularly at lower battery levels.
*Secondly, The flicker occurs momentarily when you plug in a charger.
*Thirdly, The flicker doesn't occur while the device is charging.
*Fourthly (is that even a word), The flicker is often seen immediately after a screen settles, such as when the screen stops moving after scrolling.
All of these things are evidence of a power management issue. As if the backlight voltage is not being regulated correctly.
I did some more testing over the last few hours and have found something interesting. If you go to 'Settings' - 'Developer Options' - and enable 'Show Screen Updates', your phone will blink the screen different colours whenever the screen is updated. I found that when the screen settles, the screen is updated one final time, just a moment after it has settled. This is exactly when the flicker occurs. As i see it, this is further evidence that the flicker is power management related.
It seems to me that when the CPU goes from load to idle and changes its power draw, the backlight voltage regulation does not filter these fluctuations and the backlight flickers.
The question is, can this be altered either by the power management built in to the kernel, or by other power management software? Or is it a physical design flaw in the power regulation circuit?
The fact that the fluctuation only seems to occur when the brightness is set to auto leads me to believe that it indeed can be fixed with software.
If it was a physical supply voltage fluctuation when the CPU goes from load to idle, it would surely flicker all the time, not only on Auto Brightness.
I assume that the CPU voltage is altered by the kernel as the load level changes.
My question is, if the governor is changed to one which doesn't allow the CPU to scale or voltage step, does the issue go away?
Is there anyone out there who has rooted their device and can test my theory? I don't want to root my device as I may need to send it back DOA (it's only a day old).
If you can change the governor to a profile which doesn't allow stepping or voltage adjustment (100% Voltage and Frequency all the time), and the problem goes away, we have an answer and HTC can work on developing a new Kernel to fix the issue.
Thanks!!
Click to expand...
Click to collapse
i like the theory, but on the 4 out of 6 handsets i've had, the flicker started off only on auto brightness, then got worse over a day or two, and then would develop into a constant flicker, regardless of backlight settings.
Well i really hope thats not the case here as I only have 10 hours left of DOA return window. :S
Sentinel196 said:
This thread deals specifically with the 'Auto brightness backlight flicker'. Which only occurs when the phone is set to 'Auto brightness'.
This does not deal with the various other screen glitches, or the constant flicker at various brightness levels when looking at grey screens.
Please do not get the two issues confused.
_____________________________________________________________________________________________
I have observed a few patterns, on two seperate handsets with the same symptoms....
*Firstly, the flicker occurs while the CPU is under load, and particularly at lower battery levels.
*Secondly, The flicker occurs momentarily when you plug in a charger.
*Thirdly, The flicker doesn't occur while the device is charging.
*Fourthly (is that even a word), The flicker is often seen immediately after a screen settles, such as when the screen stops moving after scrolling.
All of these things are evidence of a power management issue. As if the backlight voltage is not being regulated correctly.
I did some more testing over the last few hours and have found something interesting. If you go to 'Settings' - 'Developer Options' - and enable 'Show Screen Updates', your phone will blink the screen different colours whenever the screen is updated. I found that when the screen settles, the screen is updated one final time, just a moment after it has settled. This is exactly when the flicker occurs. As i see it, this is further evidence that the flicker is power management related.
It seems to me that when the CPU goes from load to idle and changes its power draw, the backlight voltage regulation does not filter these fluctuations and the backlight flickers.
The question is, can this be altered either by the power management built in to the kernel, or by other power management software? Or is it a physical design flaw in the power regulation circuit?
The fact that the fluctuation only seems to occur when the brightness is set to auto leads me to believe that it indeed can be fixed with software.
If it was a physical supply voltage fluctuation when the CPU goes from load to idle, it would surely flicker all the time, not only on Auto Brightness.
I assume that the CPU voltage is altered by the kernel as the load level changes.
My question is, if the governor is changed to one which doesn't allow the CPU to scale or voltage step, does the issue go away?
Is there anyone out there who has rooted their device and can test my theory? I don't want to root my device as I may need to send it back DOA (it's only a day old).
If you can change the governor to a profile which doesn't allow stepping or voltage adjustment (100% Voltage and Frequency all the time), and the problem goes away, we have an answer and HTC can work on developing a new Kernel to fix the issue.
Thanks!!
Click to expand...
Click to collapse
As for your first issue regarding flickering at lower power levels, have you tried accessing the power-saving settings and turning off the setting which changes brightness at lower battery levels? The method of accessing power-saving settings is outlined here: http://forum.xda-developers.com/showthread.php?t=1627517
oh well again i guess
NVIDIA PRISM Display Technology - PRISM (or Pixel Rendering Intensity and Saturation Management) reduces a mobile device’s backlight power while simultaneously enhancing the pixel color to deliver the same visual quality with substantially extended battery life.
Click to expand...
Click to collapse
http://www.nvidia.com/object/tegra-3-processor.html
Thanks. I'll test that out to see if it makes a difference too.
Still hopeful someone with root can test changing the scaling setting for the CPU.
hamdir said:
oh well again i guess
Click to expand...
Click to collapse
It's a great guess. The sensitivity of this being wonky was one of the things causing problems on the Prime. It also affected individual devices differently, was worse in certain apps, and was most prominent when the display was showing a predominantly dark background.
So how did they fix it?
Sentinel196 said:
So how did they fix it?
Click to expand...
Click to collapse
Drivers and low-level code. And it took four updates to get everything stabilized (battery usage, CPU performance/stepping, graphics). This has little to do with HTC (the XL having no similar issues) and everything to do with Nvidia.
designgears said:
Pretty sure this has to do with the crappy gfx drivers. The same thing that cause the camera to have issues and the notification bar. While I had the international one x, the phone benched really well while those problems weren't happening, but as soon as I was able to reproduce them and ran the tests again, score was reduced by a lot.
I could reboot the phone and the problems would go away, only to come back after some use.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1619432
OK. So it looks like I'm on the right track and it's hopeful that this can be fixed in future updates
Thanks for the info.
Sentinel196 said:
OK. So it looks like I'm on the right track and it's hopeful that this can be fixed in future updates
Thanks for the info.
Click to expand...
Click to collapse
There were a bunch of really smart people and quite a few established devs on the Prime forum when it launched. When these problems started to occur, everyone was equally flummoxed. The one question that never was answered is why devices with identical h/w and s/w would perform differently and react to updates differently. Clearly they shouldn't. No one believed the issues could be corrected with s/w alone. Somehow they were. Neither Asus nor Nvidia ever answered the question as to the differences in individual device behavior. I don't blame anyone here for being skeptical. Something really funky is going on with Teg3 that no one will probably every truly understand. Truthfully, if the HSPA version of the One X was S4 too I’d have preferred it.
I guess it just comes down to variation in the tolerances of components.
I used to work in mil-spec electronics design and manufacturing and even with the tightest possible manufacturing tolerances, there was always variation.
BarryH_GEG said:
There were a bunch of really smart people and quite a few established devs on the Prime forum when it launched. When these problems started to occur, everyone was equally flummoxed. The one question that never was answered is why devices with identical h/w and s/w would perform differently and react to updates differently. Clearly they shouldn't. No one believed the issues could be corrected with s/w alone. Somehow they were. Neither Asus nor Nvidia ever answered the question as to the differences in individual device behavior. I don't blame anyone here for being skeptical. Something really funky is going on with Teg3 that no one will probably every truly understand. Truthfully, if the HSPA version of the One X was S4 too I’d have preferred it.
Click to expand...
Click to collapse
there is a lot to love about the Tegra mate, h264 video playback is amazing on it, also android is on steroids thanks to T3
but yes im with you on the issues, semi accurate reported crazy silicon issues, i don't find it hard to image that the Prism feature is just a cover up too
it was added later on the nvidia specs page
So, to sum this up guys - are you closer to say that flickering problem is actually only a matter of s/w?
I'm wondering how long it'll take HTC to admit that there are real issues and then how long we'll have to wait for the possible solution - replace, repair or just update the firmware :O
Anyways, this made me a bit more optimistic, since with unlocked bootloader it'd be hard to fight for the replacement
Sentinel196 said:
I guess it just comes down to variation in the tolerances of components.
I used to work in mil-spec electronics design and manufacturing and even with the tightest possible manufacturing tolerances, there was always variation.
Click to expand...
Click to collapse
Here's my theory. Nvidia's having yield issues with Teg3 and what's shippable is functional but varies in spec to a degree. The s/w is anticipating a range of responses from the h/w and what it's receiving is outside that range causing it to bork. Nvidia's "fix" is a combination of taming the h/w via low-level code and expanding what the s/w and drivers are capable of interpreting. And because of variations between chips, it's hard to test in a lab which is why it took four updates to resolve the Prime's issues. Again, just my theory.
I also believe both Asus and HTC were victims. There's no way both companies could be so ****ty at testing to have not caught this pre-production. My second theory is that Nvidia provided hand-picked chips early on that were right on spec and consistent so all the internal testing passed and units sent to professional reviewers all behaved optimally. It wasn't until production that inconsistencies between chips started to rear their ugly heads. Add to this that Nvidia's code, their drivers, and the kernel (still GB vs. ICS on the XL) are proprietary so both Asus and HTC are 100% dependent on them to resolve these issues.
Pretty ugly if I'm right.
BarryH_GEG said:
Here's my theory. Nvidia's having yield issues with Teg3 and what's shippable is functional but varies in spec to a degree. The s/w is anticipating a range of responses from the h/w and what it's receiving is outside that range causing it to bork. Nvidia's "fix" is a combination of taming the h/w via low-level code and expanding what the s/w and drivers are capable of interpreting. And because of variations between chips, it's hard to test in a lab which is why it took four updates to resolve the Prime's issues. Again, just my theory.
I also believe both Asus and HTC were victims. There's no way both companies could be so ****ty at testing to have not caught this pre-production. My second theory is that Nvidia provided hand-picked chips early on that were right on spec and consistent so all the internal testing passed and units sent to professional reviewers all behaved optimally. It wasn't until production that inconsistencies between chips started to rear their ugly heads. Add to this that Nvidia's code, their drivers, and the kernel (still GB vs. ICS on the XL) are proprietary so both Asus and HTC are 100% dependent on them to resolve these issues.
Pretty ugly if I'm right.
Click to expand...
Click to collapse
not hard to believe
one of the advertised features of Gerfoce 6 series was the pure video decoder, the entire 1st gen batch did not even work, it was broken in the silicon and Nvidia did not admit it until much later when the series was obsolete
hamdir said:
not hard to believe
one of the advertised features of Gerfoce 6 series was the pure video decoder, the entire 1st gen batch did not even work, it was broken in the silicon and Nvidia did not admit it until much later when the series was obsolete
Click to expand...
Click to collapse
Then you'll find this fascinating. Nvidia's PR exceeds their product’s capabilities by about 2:1.
http://semiaccurate.com/2012/05/01/why-cant-nvidia-supply-keplergk104gtx680/
BarryH_GEG said:
Then you'll find this fascinating. Nvidia's PR exceeds their product’s capabilities by about 2:1.
http://semiaccurate.com/2012/05/01/why-cant-nvidia-supply-keplergk104gtx680/
Click to expand...
Click to collapse
still you cant live without them bro, in our CG industry they are pioneers now thanks to their cuda cores and language
im sure they let marketing tint their transparency but semi accurate goes too far
Maybe an odd question for XDA, but a question I need answered before I pull the trigger on this phone. Earlier this year while buying a new television set, I learned that I am amongst a small minority of people who are sensitive to LED-lit electronic displays that use pulse width modulation to control brightness. Apparently, I can look at a PWM CCFL-backlit (i.e. my 5-year-old computer monitor or my Nexus 5) screen or a DCM LED-backlit screen (my television set) for hours with no issue whatsoever but I can only focus on a PWM LED-lit screen briefly before I start experiencing symptoms of eyestrain and motion sickness. It's like looking at a CRT that flickers because the refresh rate is set too low. Now I know an AMOLED lacks a backlight layer, but it still has to adjust for brightness, so if it uses PWM to do so, then I have to presume it will cause the subtle flicker leading to the same problems that I've experienced with LED-LCD displays. Is there anyone here who could possibly shed some light (no pun intended) on this issue?
Yes, it uses PWM. My suggestion is to buy the phone, and if it bothers you, utilize the return window where you will receive a full refund.
So far I'm liking my G7 but I have noticed that although I have auto brightness turned off, the display dims over time (plugged in or running on battery) requiring me to jack up the slider. An ideas?
CraigVMN said:
So far I'm liking my G7 but I have noticed that although I have auto brightness turned off, the display dims over time (plugged in or running on battery) requiring me to jack up the slider. An ideas?
Click to expand...
Click to collapse
I've literally watched mine move around but I do have auto brightness turned on. I'll turn it off and let you know if I have the same experience. It could possibly be a bug, I would factory reset if possible.
same happens here
I forget which phone it was, might've been my Nexus 5X (an LG phone), but even with Ambient Brightness and Auto Brightness settings turned off, the screen would subtly dim itself due to internal temperature. It was subtle, yet definitely noticeable when the same content was displayed on the screen for a while. I wouldn't doubt that's what you're seeing here. Do you notice this happening after prolonged use or when the phone is getting warm? I haven't noticed it with my phone yet but I'll keep an eye on it. I don't run with Auto brightness to begin with because it stinks on this phone.
Alcolawl said:
I forget which phone it was, might've been my Nexus 5X (an LG phone), but even with Ambient Brightness and Auto Brightness settings turned off, the screen would subtly dim itself due to internal temperature. It was subtle, yet definitely noticeable when the same content was displayed on the screen for a while. I wouldn't doubt that's what you're seeing here. Do you notice this happening after prolonged use or when the phone is getting warm? I haven't noticed it with my phone yet but I'll keep an eye on it. I don't run with Auto brightness to begin with because it stinks on this phone.
Click to expand...
Click to collapse
Now that you mention it, it does occur when I'm playing games
CraigVMN said:
Now that you mention it, it does occur when I'm playing games
Click to expand...
Click to collapse
Yeah. My guess is the kernel decides to dim the screen slightly before throttling the CPU or GPU. This way performance isn't impacted while still reducing heat. The screen itself produces a bit of heat but the real concern here is probably the battery, which will get quite toasty while gaming.
CraigVMN said:
Now that you mention it, it does occur when I'm playing games
Click to expand...
Click to collapse
Alcolawl said:
Yeah. My guess is the kernel decides to dim the screen slightly before throttling the CPU or GPU. This way performance isn't impacted while still reducing heat. The screen itself produces a bit of heat but the real concern here is probably the battery, which will get quite toasty while gaming.
Click to expand...
Click to collapse
CraigVMN said:
So far I'm liking my G7 but I have noticed that although I have auto brightness turned off, the display dims over time (plugged in or running on battery) requiring me to jack up the slider. An ideas?
Click to expand...
Click to collapse
For those that experience this effect while playing games, it's actually a changeable option. Go to Settings/General/Gaming and untick Break Time.
Otherwise I don't know yet. :|
Just installed P and now previous brightness level of 63 it's so dim? I have to have it almost on 90% brightness now, why have they messed with this, it was fine as it was
Ady1976 said:
Just installed P and now previous brightness level of 63 it's so dim? I have to have it almost on 90% brightness now, why have they messed with this, it was fine as it was
Click to expand...
Click to collapse
Same for me. WTF Google?
The actual brightness is the same, they just changed how the slider works. The first half moved it fast, last half moved it slower. Now the slider is more uniform.
https://www.androidpolice.com/2018/...c-brightness-slider-introduced-android-p-dp3/
Sent from my Pixel 2 XL using Tapatalk
It's definitely not smooth across the entire range, all my brightness is almost all the last 10% and actually a pain to set properly, it's worse for me.
That's more accurate because in bright indoor lighting or outside it's going to be towards the end of the scale. Dim indoor lighting I'm currently at 43%. And in pitch black it goes to 0%. I pretty much never touch my slider anymore after a couple adjustments. Don't get caught up on the percentages. I would be willing to bet that with Oreo at 40% and Pie at 90% the lumens output of the screen was the same.
Ady1976 said:
It's definitely not smooth across the entire range, all my brightness is almost all the last 10% and actually a pain to set properly, it's worse for me.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
EeZeEpEe said:
That's more accurate because in bright indoor lighting or outside it's going to be towards the end of the scale. Dim indoor lighting I'm currently at 43%. And in pitch black it goes to 0%. I pretty much never touch my slider anymore after a couple adjustments. Don't get caught up on the percentages. I would be willing to bet that with Oreo at 40% and Pie at 90% the lumens output of the screen was the same.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yeah I don't touch mine once it is setup generally but it's definitely not even throughout the scale, only gets really bright from like 85% onwards, just seems odd the real brightness is so high up, makes for fine tuning a bit difficult.
The screen has been rated a minimum of 1.78 nits and a maximum of 496 so if it truly is linear now, 50% is something like only 247 which isn't that bright at all.
Ady1976 said:
Yeah I don't touch mine once it is setup generally but it's definitely not even throughout the scale, only gets really bright from like 85% onwards, just seems odd the real brightness is so high up, makes for fine tuning a bit difficult.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
Hi
So much for AI on adaptive brightness, it's rubbish, and why do Google try to fix things that aren't broken, who needs AI for adjusting a backlight? Seems nothing more than just being able to market the phone as having AI! Never had an issue on Oreo, had it set at 25% with adaptive brightness and it was always the correct brightness wherever I was, which shouldn't be difficult given it's got a sensor to read the light levels.
Now since Pie, last night I turned my phone on in the dark and was blinded by a bright display (Oreo it would have been at it's lowest level in the dark), so turned the brightness down, turned it again later and the same thing, way too bright, and again this morning in a fairly dark room the same thing, far too bright, so I turn it down again. How long will it take to learn? The old method it was tamed immediately, now I'm constantly fiddling with the brightness, how is that progress!
Is there an option to go back to the old method?
Wish I hadn't bothered upgrading, just another year with an Android update with changes for changes sake.
Regards
Phil
PhilipL said:
Seems nothing more than just being able to market the phone as having AI!
Click to expand...
Click to collapse
Totally agree on this. Adaptive battery and adaptive battery are almost non-sense. Only something cool to brand the item.
And Pixel Visual Core is just something super-expensive to make Whatsapp, Facebook and Twitter cameras use HDR+. I'd rather pay something less and not having this feature that is probably expensive (or modifies the perception of the Pixel 2 as super-new and mega futuristic). Also, I've got the feeling they won't use it for Pixel 3 or 4.
Moto X1 was the last to use more CPUs to optimize the phone, before Qualcomm introduced more chips.
Hi
For any one having this issue please report this from your device at Settings > System > About Phone, the more people that flag it the more likely it will get fixed.
For me, I hate these updates that break simple basic functionality and overall add nothing extra to what we had with Oreo. Google really need to test these things properly and stop trying to fix things that simply are not broken!
Regards
Phil
PhilipL said:
Hi
For any one having this issue please report this from your device at Settings > System > About Phone, the more people that flag it the more likely it will get fixed.
For me, I hate these updates that break simple basic functionality and overall add nothing extra to what we had with Oreo. Google really need to test these things properly and stop trying to fix things that simply are not broken!
Regards
Phil
Click to expand...
Click to collapse
Already reported, i shouldn't have to have my phone on 90% to be the same as what it was on 63%