this post was submitted on 10 Jan 2024
15 points (94.1% liked)

Android

17633 readers
227 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

πŸ”—Universal Link: !android@lemdro.id


πŸ’‘Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.


Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

πŸ’¬Matrix Chat

πŸ’¬Telegram channels / chats

πŸ“°Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 1 year ago
MODERATORS
 

Right, so for as long as I have had this phone (Sony Xperia 5 iii), I have encountered numerous issues. However, one that I cannot for the life of me not figure out is why my Overview Button stops working. I dont know how to reproduce it, I'm pretty certain it happens at random, when pressing the button.

The expected behaviour is that I should be able to access other recently used apps. However nothing happens. The only way to fix this issue (each time) is, as far as I know, change my default home launcher, back to the stock one, then open a new app and after that it will work again. I use Kvaesitso Launcher as my daily driver, however this bug has affected my throughout all launchers I have used, including the stock one.

At this point I'm looking to find a way to run a script or something to automate the process of changing the launcher and back again, as I'm sick of doing it. No idea if that's even possible yet.

I also just had the phone in for service where I mentioned the problem, along with various other problems. Phone came back with new screen and main board, if thats relevant information.

Anyone have any idea what could be causing this? Or how to fix it?

Would highly appreciate it if you have any tips or tricks. I am desperate.

top 8 comments
sorted by: hot top controversial new old
[–] Ottomateeverything@lemmy.world 5 points 10 months ago* (last edited 10 months ago) (1 children)

I wish I had a better answer for you.... But....

This seems to be some bug in Android 14. I reported it numerous times during the beta program MONTHS ago, and it's never been fixed. The public release came out and multiple friends have told me they're having this issue too. It still isn't fixed.

I don't know what the fuck Google is doing, but I've heard people have this issue with different launchers so I can't imagine they've all got the same bug - this seems to be Google's fault. The launcher I use has fixed multiple Android 14 bugs, but not this one. I don't think they can.

Fwiw, you should be able to force stop your launcher which is a little faster than changing launchers and changing back. And it's a hell of a lot faster than a restart... Pull down notification shade, tap settings, type Kvaesitso in the search bar which should let you tap to get to the app settings, and on that page should be a "force stop" button. Tap that, tap home, and it should be fixed.

I find this shit infuriating and I don't understand how Google deems this OK. I doubt this gets fixed before Android 15 at this point. Google has their fucking heads up their ass on this one.

I don't know if it does anything, but there's an issue about it here: https://issuetracker.google.com/issues/302132145 Commenting/subscribing/etc might help get this more attention.

[–] LunchEnjoyer@lemmy.world 2 points 10 months ago (1 children)

Too typical... At least I'm not alone on this, was about to go crazy. Thanks for the post, will follow it up πŸ‘πŸ‘

I've been crazy for months over this lmao. Glad I could help 😜

[–] Crazychicken563@lemmy.world 3 points 10 months ago

Happens to me constantly on the P6P. Rebooting phone fixes it. Absolutely hate this bug

[–] monotremata@kbin.social 3 points 9 months ago (2 children)

I had a similar issue on my Pixel 6, where I'm using Nova launcher. (I know they changed hands and are not great now, but it's still more usable than the Pixel Launcher.) There the solution was to go into the Apps settings, find Pixel Launcher, and choose force stop, then clear cache, then clear settings. Apparently there was some bug in Android 14 causing both launchers to try to intercept the "recent apps" press, and it caused it to hang like that.

Obviously that's not going to be exactly the same issue on your phone, since presumably Pixel Launcher isn't on there, but maybe doing the "force stop, clear cache, clear storage" on the default launcher on your phone would help?

There the solution was to go into the Apps settings, find Pixel Launcher, and choose force stop, then clear cache, then clear settings.

Fwiw, force stopping your actual launcher should fix the issue without restarting etc but it does come back.

I think I've tried doing this on the Pixel launcher with no dice, but going to give that a shot since it shouldn't hurt. I doubt this would impact the issue if it's actually based on what you claim though.

[–] LunchEnjoyer@lemmy.world 1 points 9 months ago

Nice tip! Will give it a try and see if it solves anything. Might also just remove the default launcher through ADB and see if that does anything.

[–] mp3@lemmy.ca 2 points 10 months ago

It rarely happens to me, but I had to reboot my Pixel 7 Pro (Android 14) to make it work again.

I'm using Ruthless Launcher.