I can confirm this, it's how I use mine.Double tap on power button only works for the included AOSP Camera2 app, afaik. Some say you can make it work with gcam ports if you disable the stock camera app, but I haven't tried it myself.
I can confirm this, it's how I use mine.Double tap on power button only works for the included AOSP Camera2 app, afaik. Some say you can make it work with gcam ports if you disable the stock camera app, but I haven't tried it myself.
The "show device controls" toggle is supposed to show or hide "device controls" menu, like chromecast devices, Google Home devices, etc., on lockscreen. It has nothing to do with QS tiles.I think I found a bug in the lock screen.
If you disable "show device controls" in combination with "show all notifications content", you can use the device controls (e.g. reboot device, disable wifi, etc) while the screen is locked.
This is a thing that I cannot make everyone happy. Some complain the minimum brightness in adaptive brightness is too high, and some say it's too low.This has been bothering me for a while. Has anyone figured out how to set the minimum level for Adaptive Brightness? It goes down to around 15% when I'm in a dark environment and I can't see a thing. I have changed it at least 100 times, and it still goes down to that level. Cheers
Ok. But if I disable the notifications, it also locks the usage of the quick controls. Shouldn't these be two separate things. I want to be able to see notifications, but I don't want anyone to turn off my phone or my wifi without authenticationThe "show device controls" toggle is supposed to show or hide "device controls" menu, like chromecast devices, Google Home devices, etc., on lockscreen. It has nothing to do with QS tiles.
I think you're right, that's exactly how it works, I just couldn't figure out the pattern. It works for some time, then it's always reset. A think the key here is that it resets itself after reboot. It probably shouldn't do that. Your individual user preferences don't change because you reboot your phone. If someone wants to reset it, they can do that through settings. What do you think?Theoretically, if you manually adjust the brightness, the system will try to take the adjustment into account and fit your "user entered" point into the brightness curve. It will remember the adjustment until next reboot. However, if somehow it does not work for you, I can't do anything about it.
If you really want to fix it once for all, you can bump the values in this array right here:
and then build from source again.device_xiaomi_polaris/overlay/frameworks/base/core/res/res/values/config.xml at twelve · PixelExperience-Devices/device_xiaomi_polaris
Dependency of Xiaomi Mi MIX 2S (polaris). Contribute to PixelExperience-Devices/device_xiaomi_polaris development by creating an account on GitHub.github.com
No. I believe it definitely should reset after reboot. What if you mis-operated and accidentally set an incorrect user point? What if the user points accumulate over time, and the curve goes out of control?I think you're right, that's exactly how it works, I just couldn't figure out the pattern. It works for some time, then it's always reset. A think the key here is that it resets itself after reboot. It probably shouldn't do that. Your individual user preferences don't change because you reboot your phone. If someone wants to reset it, they can do that through settings. What do you think?
Current PE does not offer such feature.Ok. But if I disable the notifications, it also locks the usage of the quick controls. Shouldn't these be two separate things. I want to be able to see notifications, but I don't want anyone to turn off my phone or my wifi without authentication
What you describe is an edge case really. To most users it'll never happen. But should that be the case, one can go into settings and reset Adaptive Brightness manuallyNo. I believe it definitely should reset after reboot. What if you mis-operated and accidentally set an incorrect user point? What if the user points accumulate over time, and the curve goes out of control?
The android system is designed to be never rebooted unless there is an update, so it is natural to let the brightness curve reset after reboot.
Well Adaptive Brightness was introduced in android pie, and it has been like this since then. I can't really change the behavior because that would be against "Pixel"'s experience. However, you can probably raise this issue to Google and see what they're gonna do with it.What you describe is an edge case really. To most users it'll never happen. But should that be the case, one can go into settings and reset Adaptive Brightness manually
View attachment 5638523
The problem with resetting after reboot is that it takes a good week or two for a user to configure every brightness level to their liking. With monthly updates, this means that by the time they're all set, an update comes and they get reset. In hindsight, the issue is not that the minimum is low. It could be anything really, if users could then adjust the brightness values to what they want. The real issue is that by resetting at reboot, a single returning value is forced on every user. And that never worked in human history because we are all humans and our preferences differ
1. A reboot is not required. I just tried it on my polaris, and you only need to use pin to unlock once. Subsequent unlocks are fine with fingerprint. This seems to be the intended behavior (because internally, the security level of fingerprint is lower than pin, so perhaps "Lockdown" wants you to use the highest level of authentication once), but I'll check with other devs.Completely unrelated to the brightness topic, I think I have found two bugs:
* "Power menu > Lockdown" Locks down the phone (as expected) and the fingerprint sensor stops working entirely. You can only unlock the phone using pin. A reboot fixes it.
* Certain apps and UI elements can't recover from "Extreme Power Saving" mode. That includes the built-in Google weather widget and Google Assistant. Both of which only come back to life after reboot.
Of course it's possible that both of these only happen on my phone...
Just to be very clear about it, this isn't personal and it isn't against the work you do. I really appreciate all that. It's more a theoretical "argument" than anything, for an overall better user experience. The fact that a mammoth company does something a certain way doesn't necessarily make it right or correct in my personal opinion. I agree with you 100% though that it wouldn't be "Pixel" experience if you changed that. That's a valid point.Well Adaptive Brightness was introduced in android pie, and it has been like this since then. I can't really change the behavior because that would be against "Pixel"'s experience. However, you can probably raise this issue to Google and see what they're gonna do with it.
1, You're right, although I had to unlock with pin twice, not once. But no biggie, if it doesn't need a reboot.1. A reboot is not required. I just tried it on my polaris, and you only need to use pin to unlock once. Subsequent unlocks are fine with fingerprint. This seems to be the intended behavior (because internally, the security level of fingerprint is lower than pin, so perhaps "Lockdown" wants you to use the highest level of authentication once), but I'll check with other devs.
2. I'll let jhenrique09 know.
Actually, authentication is required before changing anything in the "Internet" tile, so other people will not be able to turn off your WiFi.Ok. But if I disable the notifications, it also locks the usage of the quick controls. Shouldn't these be two separate things. I want to be able to see notifications, but I don't want anyone to turn off my phone or my wifi without authentication
I don't know, and it never happened to me. It could be anything. Take logs next time it happens.Perhaps this is just my problem, but for the second time I've been observing that the cores are being lifted. first small x4, then large at a frequency of 2803 mhz. The first time the flashing helped, now it does not help. What's this? And because of that battery drain so fast and the phone is so hot.
How can i take logs on PE12? And it happens all the time. In real time. It doesn't stop at second.I don't know, and it never happened to me. It could be anything. Take logs next time it happens.
Are you sure you are not using any 3rd party kernel or modules? The CPU should not lock to a certain frequency in stock PE.How can i take logs on PE12? And it happens all the time. In real time. It doesn't stop at second.
adb logcat > pe_cpu_freq_stuck.log
Yes, I've never used any 3rd kernel, all was stock. Hope this will help you. Don't know why but i can't attach here. Send you via message.Are you sure you are not using any 3rd party kernel or modules? The CPU should not lock to a certain frequency in stock PE.
To take logs, enable USB debugging in developer options, connect your phone to a computer, agree to the prompt, and
Code:adb logcat > pe_cpu_freq_stuck.log
Do it when the frequency issue appears. Press "Ctrl + C" to stop the capture.
Nope. I can turn off everything. Wifi, mobile data, the phone... All without any authentication being required.Actually, authentication is required before changing anything in the "Internet" tile, so other people will not be able to turn off your WiFi.
abd shell
su
setenforce 0
getenforce