• GeneralSolved

  • Wrong apps open when I search for an app and press it

Mintou

I tried on my phone and the correct app always opens. I don't know why it's messed up on yours. Have you tried a different launcher?

However, if it's a known upstream issue then Google should fix it upstream, then it'll be fixed in GrapheneOS.

      It doesnt really marrer If it's an upstream issue, the bug doesnt happen on the pixel stock os, everybody can test. It's a bug that can be fixed by grapheneos team, moreover, as seen as the video, I'm not pressing the apps particularty rapidly, just like any lambda user could do.

        Mintou the bug doesnt happen on the pixel stock os

        That's because Google uses their own launcher on Pixels, not the AOSP one. GrapheneOS launcher is the AOSP launcher.

          • [deleted]

          • Post #7

          Mintou everybody can test. It's a bug that can be fixed by grapheneos team, moreover, as seen as the video, I'm not pressing the apps particularty rapidly, just like any lambda user could do.

          I tried it many times and my phone (6a) is probably faulty, because I couldn't reproduce your issue at all.
          Being old I do not have the speed to click fast enough on the icon, and now when I am thinking about it, maybe "it" really opens different app, but I know that I wanted to open an app, so I use the app that is opened. It's a win win.

          For now, you can use a different launcher or you can change the habits how to open your apps. Or slow down 👍

            matchboxbananasynergy
            Okay, however, again, there's no way for users to test aosp launcher out of the box to see where the bug originates from.
            In practice aosp launcher isn't made to be used on any device and this issue should be higher priority and not considered "upstream", it is in a way a grapheneos bug, no other device I use has to bug (pixel 6 on stock os, other Samsung devices with same android versions). It is unacceptable to keep this bug in the launcher, as it kills the whole user experience and makes me obliged to keep using stock os.

                • [deleted]

                • Post #13

                Mintou It is unacceptable to keep this bug in the launcher, as it kills the whole user experience and makes me obliged to keep using stock os.

                Dear Mintou, your stubborness is mind blowing. You reported a minor bug, you were given an explanation and you were also provided with a bug trucker number (which means that the issue will be looked at) and you are not accepting any of it? Launcher is just an app. If you have a problem with it, install other launcher, there are many options. Your proposed solution to switch to other OS is a solution as well, radical but a solution:-)

                    I was curious about what could be causing this issue, so I looked at the code. I think I found what might be causing it. I might be wrong since this code is sort of hard to follow. I wouldn't know unless I built a whole new GrapheneOS image to test, but sadly I run an OS that isn't supported to do Android builds.

                    From what I can tell, the launcher searches all installed apps, picks 5, creates a new view for the search results, displays the new view, then starts a search transition for 300 milliseconds before completing.

                    If already in a search listing, the search transition is set to 0. This explains why if I type a first letter, wait a second, then type a second letter and immediately launch an app, the correct one launches.

                    Anyway, if I'm right, just wait 300 milliseconds and you'll launch the correct app. Not really a long time to wait if you ask me.

                    [deleted]
                    Sorry to sound stubborn, however as an active user and contributor of grapheneOS, I find it unacceptable toward customers, it's not a minor bug imo, it's a very major one and I disagree with the "upstream" tag. Every 5 minutes I have to close an wrongly opened random app it's really inconvenient and primitive way.

                    I know grapheneos is free and opensource, but if it was a paid product I would be the first to buy it because I need it for my job (journalism in ***). What I mean is that even tho the service is free, it's not ok to have such as major bug since 1 month and a half and I disagree with the label "upstream", it happens only in grapheneos.

                    Thank you everybody for your help

                      2 months later

                      Still not fixed after latest update.
                      I repear, the upstream flair should be removed, this but is specific to grapheneos, it does not happen on stock firmware.

                      • de0u replied to this.

                        Mintou GrapheneOS and the stock Google OS that runs on Pixels are siblings - both are downstream from AOSP. Samsung's OS, Xiaomi's, etc., are all downstream from AOSP.

                        GrapheneOS is shipping essentially the AOSP launcher. Bugs in the AOSP launcher absolutely affect the GrapheneOS launcher, which is downstream from the AOSP launcher.

                        Google is not shipping the AOSP launcher. So bugs in the AOSP launcher generally do not affect Google's launcher.

                        Many launchers run on GrapheneOS. It is very likely that switching to one of them is the fastest way for your experience to improve. Switching might well take under one day. It will likely take weeks or months for this upstream bug to be fixed, if it does get fixed.

                            6 days later

                            de0u
                            Thank you for the answer.
                            For what i understand then, upstream means aosp bug, İ thaught it meant "stock pixel os bug". Sorry about that I was misinformed
                            Nobody can use aosp out of the box tho, and the launcher is named "grapheneos launcher", so I think it's a bug that happens mainly on grapheneos and that it should be given more attention. This doesn't happen on any os I tried on my pixel and imo indirectly affects the credibility of grapheneos.
                            Using another launcher is of course an option, but launcher raise a lot of privacy issues and I trust grapheneos default launcher more than others

                                Mintou It would be great if Google were to open-source their OS stack, but it's important to acknowledge that what they do release (AOSP) and what they support (phones with unlockable bootloaders and five years of firmware) is already quite a contribution.

                                The paying customers (Samsung, Sony, ASUS, etc.) may well have access to code which isn't part of AOSP (perhaps including Google's launcher), but not the open-source projects.

                                I wonder which launchers are shipped by other open-source projects that derive directly from AOSP?

                                  16 days later