I don't use Google Assistant, so I disabled it, by (1) opening the Google app, then (2) going to settings from the profile icon, then (3) choosing "Google Assistant" settings, then (4) scrolling a long way down to "General" settings, then (5) toggling off the top toggle that simply says "Google Assistant". However, sometimes the device thinks I long-pressed the home button (e.g. if I swipe up too slowly) and pops up a Google Assistant nag screen asking me to re-enable it. How do I stop the Home button from doing this? There don't seem to be any related settings in the Google app settings. I've found dozens and dozens of articles explaining how to disable Google Assistant - which I've already done - but not how to stop this home button behaviour. Device is a Samsung S22 Ultra running Android 14 and OneUI 6.0 if that's relevant.

How come the device's Home button now cannot turn the screen on, i.e., unlock the screen to get into Android 11? How to recover its ability to do so? This is after trying to disable the Google Assistant prompt, then turning the screen on and unlocking the screen to get into OS's accesses: 1. Open built-in system settings 1. Choose Apps and Notifications 1. Choose: Default Apps 1. Go to "Digital Assistant Apps" 1. Tap on the text "Device Assistant App" with "Google" under it, having the gear/cog icon on the right side (which must not be tapped) 1. Choose the first option: "None" 1. Exit the system settings How to recover the device's Home button's ability to turn the screen on?

I would like to reverse a behaviour on Android 14 that was introduced with the September update. - Previously (this is what i would like to see): Long-press of the home button brings up Google Assistant (eg. for Calling, setting alarms, etc.) - Behaviour since the update: Long-press of the home button brings up some google overlay feature to "circle to search". Bringing up the assistant now moved to some obscure swipe gesture from the corner in. I have looked in the settings on how to define behaviour of the home button but not found anything. Ideally there would be sth like a mapping table. On here, the closest thing I found to this usecase is a ticket that deals with switching off both functionalities (assistant and the circling feature: https://android.stackexchange.com/questions/255899/how-to-stop-disabled-google-assistant-popping-up-on-home-button-long-presses Any nifty way where I can directly define the behaviour of the homebutton and set it to the assistant? Alternatively any other way, eg a launcher? - Android version: 14, September Update - Phone: Samsung A55 5G Thanks all!

So this is happening for the last 2 weeks. Whenever I (short) press the home button on my Galaxy S7 (on Android 8.0.0) specifically in the (facebook) messenger app it registers as a long click (opening the google assistant until i disabled it). I'm not sure if it is a messenger problem since Im sure I had this happen in the playstore app as well but cant replicate it right now (so right now its only happening in messenger app). I played around with the Tasker and Automate apps around the time this started happening, but I have also uninstalled them around that time. Might just be a coincidence. I have tried reinstalling the messenger app but that didnt help. Does anyone have any idea what could cause this or at least give me some pointers on how I might troubleshoot it? Edit: definitely happens in other apps as well but still mostly in messenger

I want to fix it so the home button long press kills a particular app. I can't see the option for home long press in Tasker or Macrodroid. Galaxy S5, rooted, CM Marshmallow, Xposed installed.

On my Samsung Galaxy A3 (2017) with Android 8, I used to be able to press the home button to directly go to the home screen. Some configuration must have changed because now when I press the home button, it only activates the screen but doesn't take me to the home screen. I need to press the home button to activate the screen and then swipe to go the home screen. Anyone can help me restore the previous functionality?

Few years ago on my android was possible keeping pressed the home button, to activate a feature that would allow to translate everything on screen. Unfortunately in a subsequent update google decided to replace that awesome functionality with the useless google assistant. Do you know how I can do to get that back? I know it is possible to update screenshots but that it is a way more cumbersome process.

Is there an easy way to change the add to home screen image on Android devices? I know how to change the HTML manually but for example I would like to change it for the YouTube web app for example.

I dropped my OnePlus One, and now the bottom half of the touchscreen doesn't work. I connected a mouse to disable the lock screen, and I can now work with most apps (apart from Strava and the Camera) by rotating the screen 180 degrees (turning my phone upside down). (By the way, the phone is running a recent build of LineageOS.) My main issue now is that I can't switch between applications. When I receive a notification, it appears at the top of the screen, and I can pull down, and touching the message opens the app. But I can't open other applications, as I can't access the home screen. The only option I know of is to reboot. The OnePlus One has 3 capacitive (touch) buttons below its screen, and these also don't work. The middle one of these would normally bring me to the home screen. Is there another way to access the home screen other than using these 3 touch buttons?

It's driving me crazy. On a Moto G5s Plus (with Android 7.1.1) how do I set the screen I want as the default one, so that is shown when I press the Home button? At the moment the left-most screen (of 3 screens) is the default. I wan to set the middle one as default one. * I already disabled *Google Feed*. * I already tried to long press one screen, get the setup view (change order, remove, Widgets, etc) **but there is no icon** (usually a "Home") at the top of the screen to be pressed for setting the default screen. I find this method everywhere but **doesn't behave like that** * I already tried to pinch-in with 3 fingers; nothing happens

Got a bit of a hopefully-not-*too*-interesting one :) For reasons unknown, my (secondhand) Note 3 seems to have a bit of a tendency to crash when I use the "Move to SD card" button in *App info*. Doesn't happen every time. By "crash", I mean that: everything freezes for about 5 seconds (I often notice this and go "...ah, it's gone again"), the screen goes black momentarily, the Samsung bootup animation runs for about a minute, and then it's back at the lockscreen. It **doesn't** show the Android logo/splashscreen that I see if I perform a device restart, just the Samsung animation. I'm actually new to Android, so I don't know if I'm witnessing some sort of respring sort of thing or what. In any case the above is what happens. I knew that something was a bit wonky/flaky, but I just accepted it as "normal" for this device (put it down to "eh, it's an old version of Android") and I figured the reboot-thing it was doing was resolving whatever the issue was. The app transfer process seems to make the CPU get mildly impressively hot, but I don't expect that this has any impact. (Translation, I hope very very much that this thing was system-integrated properly and I didn't make it legitimately overheat ;)) IIUC, on Android 5, moving apps to the SD card can only be done via App info, manually, on a per-app basis. All AppMgr III can do for me to batch-move apps over is queue up hundreds of App Info windows so I can hit the *Move* button myself. Each transfer takes about 2 minutes and that's annoying enough, but the semi-continuous reboots meant I had to keep opening AppMgr, reselecting everything, ... Soooo, I finally finished a script this afternoon (...:D...) that uses ADB to poke around in the package list, figure out what's on internal storage, open the *App info* window using the ActivityManager, figure out whether a given app is movable (based on whether the Move button is clickable), and if it is, click the Move button to move the app over. (The script also implements a bunch of heuristics to figure out when the phone has "crashed": **it's actually accessible via adb shell the entire time**, but a bunch of services stop then restart.) To clarify, this script basically just poked the screen at the right moment so I didn't have to keep staring at the phone. After some final tweaks it happily dug its way down my list of (way too many) games and apps all afternoon. My **guess** is that the CPU was sitting at a _minimum_ of 60° for a while. :/ I happened to check in on the phone after probably the 4th or 5th move-induced crash, and noticed it was behaving very strangely: the font settings were wrong, some persistent notifications I have open (system monitors) were gone, *and the Home button wasn't doing anything*. My launcher configuration was still intact (whew), my phone still knew its lock code and my Wi-Fi's PSK. But things like font settings, keyboard preferences, etc etc were all gone. Hard-resetting (Power+Home for 30sec), standard restarts, and wiping the cache partition from the recovery options have not restored my Home button's functionality. What's really weird is that - Pressing Home when the screen is off wakes the device up - Pressing Home repeatedly enables Talkback - Pressing Home twice doesn't do anything - Pressing it once doesn't do anything - Long-pressing doesn't open the recent activity view Also - the quick-access buttons in the pull-down menu have all reverted back to factory settings, *and the Settings and Show-All buttons have stopped working*. My next expected step is backing everything up and doing a full reset. Just thought I'd share where I'm up to in case anyone has any other ideas. Thanks for reading!

Is there a way to add app launchers to the stock android's home button long press menu? I know you're able to do this in CM, but there must be some Xposed module, right?

I have a **Samsung** device and i need to use the **Android recovery mode** for some reason.As for **Samsung**, i have to use the **volume-down** and **home key** to enter **recovery mode** But the problem is, my **home key** is broken and as a result, I can't use the normal way to enter **recovery mode**. I can use **ADB** to do that with my **PC** but i can't do that every time when i need. **So, is there a way to do that without using the home key?** > Note: My phone is **not rooted** and i know that i can change the **recovery mode entering configuration** easily if i **root** my phone but i don't want to **root** my phone.

I click the home button to activate the phone. If I don't swipe within two seconds, it goes black and I have to hit Home again. This is frustrating when I want to just view the time and weather on the lock screen. It's almost enough time to view time and weather, but if I also want to see what date it is, then 2 seconds isn't enough time to view all three things and digest the information. So I find myself hitting the Home button 2 or three times. So I guess I might as well just swipe and activate the phone. But I really wanted to just set the screen to stay on a little longer. I set the display timeout to 10 minutes but this doesn't affect the lock screen. It still blinks off after 2 seconds. Is there any setting or something from a Tasker app or something, that can extend the time the lock screen will appear?

In short, I wondered if there was a way of configuring the home/recent apps button to go to the app launcher instead? (Perhaps it is a software recommendations/tweaks question.) EDIT: This lost its relevance as I have now upgraded to Android 9 where a double up swipe gets me past the downgraded recents apps view into the launcher quickly.

My guess is that the reason there's a delay when pressing the home button is due to the fact that it could be re-purposed into launching "Google Now" or "S Voice" by **pressing it twice**. So it has to wait for a second before it sends a signal "this is a single press" to the OS. I don't believe it's caused by phone waking up from sleep because it happens every time and it's consistent. If my guess is correct and I'm not using "Google Now" or "S Voice", it would be great to remove this delay. How do I do that? Is that even possible? In my opinion, it is annoying. The moment I press the home button I'm expecting an instant response by showing up the home screen as immediately as possible. EDIT: I already disabled all the apps that could possibly make use of double pressing the home button like "S Voice". Now when I open an app to foreground, pressing the home twice doesn't take me to home screen but instead nothing happens. That means there's no longer any function that is currently bound to double pressing the home button. If I press the home button once, it still takes a delay before it takes me back to the home screen.

I just installed ViperOS on my Moto G5 – and I **cannot** find the bottom bar with home, back and the other button. It is just not displayed. And I have not found **anything** on the Internet on how to solve this issue.

I have a China-branded tablet running Android 4.2. The tablet has the "new" Jellybean 4.2 home screen button layout where the software buttons are centered on the screen, rather than aligned left as in common desktop operating systems such as Windows and Linux (with the KDE or Gnome 2 desktop). The problem is that the button layout in my tablet differs in a slight, but annoying way from the Android 4.2 default, which is to put the home button at center, surrounded by the back button at the left and the recent apps button at the right. Instead, my tablet has the home button displaced one position left of center, which is occupied by the recent apps button followed by the two volume buttons (down/up). Is there a way to edit the layout/order of the software buttons of the Android home screen? My ideal would be this sequence: volume down, back, home, recent apps, volume up. (Such a layout would retain the volume buttons, while keeping the home button in the familiar center slot.) I know that Cyanogenmod has a settings tab precisely for fixing this problem. However there's no Cyanogenmod port for my tablet, its main saving grace being that it comes "pre-rooted", which allows me in theory to mess with any system settings if only I knew how.

I have removed Google Now in order to assign long press on home button to open another app. But recently it comes back with a different interface I'm familiar with. I guess the phone just has updated it. However I'm unable to disable or uninstall it. In Google Play I can't find which app has just been updated. In the setting of the app there is no option to disable it. These are some system Google apps that's under my suspicion: Google Services Framework, Google Partner Setup, Google One Time Init, Google Play Store and Google Play services. But I find no evidence to against them.

I have a Nexus 9 running Android 7.1.1, and the home button, recent button, *all* notifications, and the top pull-down menu all stopped working. The home and recent buttons respond to being tapped in that the animation that indicates I tapped them runs (the gray circle expands out from the button), but nothing happens. I can open the top pull-down menu, but it always says that there are no notifications, and I can't pull the menu down further to expand the icons. I have about 15 GB out of about 30 GB available, and memory usage is listed at 1.6 GB out of 1.8 GB. I've tried restarting the device multiple times. If I remember correctly, I accidentally drained the battery before this happened, but I can't recall if the device was simply powered off. When I powered up the device, the PIN prompt buttons caused the device to vibrate, even though I had had previously had that setting turned off. I restarted the device, and that setting turned back off. Double-tapping to wake up the device doesn't work consistently. Any ideas?