Got Android 11 Last Night
- Thread starter lion7718
- Start date
It's OK once you learn where it is, but I find it a bit illogical (in that there's no particular logic to placing it where it is now) and I don't see any usability advantage to the change. I have learned it, but the first few times I wanted to take a screenshot I wasted a lot of time finding it, which was never an issue with the previous method.
It's also a bit non-intuitive, since you change from the view you are going to capture to the "overview" view before you press the button to capture it.
But as I've been running 11 for about 6 weeks I've had time to get used to it. It's just "change for no good reason" to my mind.
It's also a bit non-intuitive, since you change from the view you are going to capture to the "overview" view before you press the button to capture it.
But as I've been running 11 for about 6 weeks I've had time to get used to it. It's just "change for no good reason" to my mind.
How were you guys accessing the screenshot function previously? I've always gone for the Volume Down + Power shortcut for as long as I can remember.
I've always used the two button method, like @codesplice. I never had much issue and it seems to be the method used on a lot of other phones, too.
I've used just the power switch for awhile now. I would hold it down and had the option for a screenshot along with the other options. Now with 11 I have to hold in power and volume down.
Interesting: I thought power+vol down was no longer there, but managed to get it to work just now (after failing several times yesterday). As I say, I find it finnicky (seems to rely on the 2 buttons being pressed together, perhaps with timing margins too tight for my phone's keys).
The new feature is that you can go into the recent apps overview and take a screenshot from there: it will take a shot of whichever app screen is currently being viewed.
I preferred the power button only method, but I guess they have overloaded the power menu with payment methods, passes, device controls now so maybe think there isn't room (though there is for me, since I don't use most of that stuff).
The power button was great, also the assistant button has disappeared...you know have to say "Take A Screenshot". Having it in resent apps makes no real sense since you have have to change the gestures from 2 button to 3 button. I changed it for a day, but couldn't get used to the old 3 button setup anymore.
Ah, I don't know about "assistant buttons": with a Pixel 2 I have the "virtual bixby button" (or "active edge" as Google call it) as well as whatever UI triggers they have, but as I disabled the Google app years ago in order not to be bothered by prompts to enable Assistant whenever I accidentally pressed a home button for too long I have no idea what their current methods of launching it are.
Not even with 11 but I delete random screenshots all the time. Gotta be a button thing.
That's got to be generated by one of your installed applications. You can verify this by booting your phone into Safe Mode (which disables your installed applications) and watching to see if the toast appears again.
Do you use Firefox Lockwise? I've seen a few folks mention that it might be the culprit. Try disabling it as an Autofill service to see if the toasts disappear.
Problem solved I went straight to the input menu on system settings. Kaspersky password manager was selected for keyboard autofill. I switched it to gboard and it has solved the problem.
Thank you anyway 👍
It's probably related to the fact that "custom toast messages" were deprecated in Android 11. Any app that used such a thing and hasn't been updated will now generate "null" toasts until it is updated to remove them.
Oh, good info! I was trying to figure out why my Bitwarden password manager wasn't causing me to get these toasts since it did appear to be tied to the autofill service.
Another thing, this Forum app kept crashing until I changed the autofill
I'm not sure of the number of programmers here... but other people ( ie non-programmers ) are unlikely to even know about the change. From the quick Google search I did, they just dropped one of the two text toast methods, the foreground method still works, the background method was disabled. No doubt some programming directed forum discussed it... this forum seems to be far from that. I was completely oblivious to it until I googled it personally.
Define "programmer"? I've written software for high energy physics for 30 years or more, in several languages and for real time as well as offline applications. But I'm not an Android developer, so would only come across technical details of changes if there was something that caught my interest enough to want to find out.
Although there is a development section, this is primarily a forum for Android users rather than developers.
Although there is a development section, this is primarily a forum for Android users rather than developers.
I wouldn't dare try defining the term if it were a serious discussion... it's obviously subjective depending on everyone's own opinions. .. For instance, I can make some complex spreadsheets, but I wouldn't call that programming excepts in the most basic sense at best. Still, I suspect if someone is creating a "toast message" to pop up information... I'd assume they are creating some type of app or program.
I could certainly venture a guess ( ie big grain of salt ) on why a toast message from an app/program that is in the background is no longer supported... would be to help save power. It seems that the newer Android OS versions allow fewer background apps running in the background without specific permissions for that purpose... it's make sense if they are doing similar things for toasts and notifications as well. Still, that is coming from a non-dev type and may have nothing to do with it.
Of course it seems at times that Google acquires, creates and then kills perfectly good stuff quite often .. often without saying why they did it. So at that point, it's probably anyone's guess.
I could certainly venture a guess ( ie big grain of salt ) on why a toast message from an app/program that is in the background is no longer supported... would be to help save power. It seems that the newer Android OS versions allow fewer background apps running in the background without specific permissions for that purpose... it's make sense if they are doing similar things for toasts and notifications as well. Still, that is coming from a non-dev type and may have nothing to do with it.
Of course it seems at times that Google acquires, creates and then kills perfectly good stuff quite often .. often without saying why they did it. So at that point, it's probably anyone's guess.
Similar threads
