37
Google still hasn't fixed delayed notifications on Pixels, but you can try this
(www.androidauthority.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Sep 2024
37 points (100.0% liked)
Google Pixel
5920 readers
6 users here now
The World's Google Pixel community!
This community is for lemmings to gather and discuss all things related to the Google Pixel phone and other related hardware. Feel free to ask questions, seek advice, and engage in discussions around the Pixel and its ecosystem.
We ask you to be polite when addressing others and respect Lemmy.world's rules.
NSFW content is not allowed and will immediately get you banned.
It also goes without saying that self-promotion of any nature and referral links are not allowed. When in doubt, contact the mod team first.
Also, please, no politics.
For more general Android discussions, see !android@lemmy.world.
This community is not in any way affiliated with Google. If you are looking for customer support regarding your Pixel phone, look here instead: https://support.google.com/pixelphone/
founded 1 year ago
MODERATORS
They still haven't fixed the task switch button from the three button layout becoming non-functional after four years: https://issuetracker.google.com/issues/204650736
It's a byproduct of the home and task switch button now being managed by the Pixel Launcher regardless of which launcher you use. The animation delay makes it so the button becomes inactive and won't be made active again until the Pixel Launcher is killed or the phone restarted.
From my perspective, Google is losing interest in maintaining Android at all.
Try switching to gestures. I haven't had that problem on my Pixel 6A and I only use gestures (imo they are way better and more convenient to use.
Gestures are not better for me and my situation. Please stop suggesting that I work against my better interests.
They are objectively slower and less precise, just to start with.
What? You say that like I say that constantly to you.
I just suggested what works for me. Calm down mate.
Also for me they are objectively faster since I have to move my fingers less. Especially the back gesture which is miles better than the button. I very rarely use the app switcher. It's easier to just swipe to the next app or go to the home screen and open the app again.
You're the second person in this thread to try convincing me to switch.
I use the app switcher constantly. I'm using it now to jump between my Lemmy client and YouTube. It works. It's fast. The back navigation also interferes with productivity apps, many of which still use a drawer. I use those apps constantly as well.
Gesture navigation will never be a proper use case for me.
That's fine. Don't pretend it's objectively better though.
I said it was subjectively better and objectively faster. And it is.
Not everyone will agree faster is better, and that's fine.
It might be faster for you. But it's not for me.
In other words it's subjective. (duh)
The default Android animation transition length is 300 milliseconds. The gesture based navigation uses this delay.
The task switch button, for whatever reason, can interrupt this delay, making it as fast as I can tap, which is a lot faster than 300 milliseconds. In fact, this is what triggers the bug. I had to set the animation scale to 0 on my device just so it can keep up with me.
Speed, time, and duration are not subjective measurements. I will accept that it's more comfortable for you, however.
When your navigation preference breaks the Android animation duration because you're using it so quickly, get back to me.
I have no doubt you can click very fast.
I was more referring to travel distance though.
Uhu..
https://s6.ezgif.com/tmp/ezgif-6-8241f7536d.webp
~~https://s5.ezgif.com/tmp/ezgif-5-10d5b9032f.mp4~~
The link expired - uploaded to YouTube here: https://youtu.be/HYSM-U1rYpI?si=w9AuFzbBwaj7Kn4C
I remember that being a super annoying problem, and then it went away. I haven't thought about that issue in years. Maybe it only happened on my old 4a.
It's been a constant thorn in my side on my Pixel 4 XL, my Pixel 6 Pro, and now my Pixel 8 Pro.
I confirmed with a friend that it still occurs on her Pixel 9 Pro XL.
I used to be a die hard three buttoner, but the two button layout (with swipe up from home being the task switcher), plus the nice swipe-the-button-bar to flip through tasks one by one is an improvement for me.
It is not nearly a replacement for me.
I use gesture navigation on mine, no buttons at all. I also use Nova launcher (with updates blocked because they just got bought by an ad company). Never had a problem!
It depends on how often and how quickly you use the task switch button. I use it to rapidly switch between two apps frequently by double tapping the button and trigger it multiple times a day still. Google still recognizes it as an open bug.
To note, this occurs with the three button layout, so the fact that you're not having a problem is expected.
I'll only switch from the three button layout if I'm forced to. The gesture based navigation is slower and less precise.
I'm glad you intuited that I meant "gesture" navigation - had an autocorrect problem. There's a bug I've seen for years where, when swiping back to home, the screen is unresponsive to taps for like a half second. Maybe that's related? Apparently it's more noticeable with third party launchers like mine.
I'll have issues after taking a screenshot and navigating back - I just get a non-responsive black screen sometimes except for the navigation buttons. Those are partially unresponsive, and I have to tap them chaotically to get rid of the black screen.
I think the whole Android system navigation has been broken since Google started rolling it into the Pixel Launcher.
That sounds quite frustrating - I'm glad I've not had that so far. Agreed about the launcher.
Weird. It doesn't happen at all on my Pixel 7 Pro.
Third party launcher and three button navigation?
Yup. I use Lawnchair and 3-button nav, and I double-tap the recent apps button 100 times a day.
I just tried it out - triggered it after about an hour. ๐
Google is just starting to capitalize big on Android with its strangle hold. They've recently introduced tracking your device while it's off. Scoped storage, where it excludes itself. Stock Pixel devices cannot use other gallery apps to view their images. Google requires developers to submit their key to sign their apps for Google Play Store. Google has copied almost all popular productivity apps to push their own above everyone else. And so on and so on.
Their AI stuff is probably analyzing your data on-device and sending aggregate to their servers. Which they can conflate and market as "not sending your data" but it just means not sending the raw data.
So I really doubt they're losing interest in Android.
They're certainly losing interest in maintaining core Android, which is closer to what I meant. Everything you've described is within their Play Services environment.
Some of what you've said is incorrect as well - I have a third party gallery that works just fine on my stock Pixel 8 Pro. Its access is just managed by a separate permission.
Peak was pre-12.
I feel like it's been downhill since Jelly Bean.
I kept my Incredible for over a decade, rooted it at a boring job within weeks of buying it and kept trying builds from a dev forum, kept a few on a sd and had clockwork.
I had one job that required 4, so before leaving I'd back up, then wipe, then install the 4.x build with their app on it.
At the end of the day I'd wipe and restore the 3.x build I was using, by the time I got home it was back to the way it was.
This is what I want in a phone again, not hide and seek with predatory data companies. Not only that, but it was fun and I learned things.
With the Pixel phones, there's GrapheneOS. It might be my go-to one day.
I have GrapheneOS on my Pixel and I experience this notification issue.
Right - I wasn't suggesting that it would fix the notification issue, just that it might give the previous commenter the Android environment they're looking for.