Anyone beside me still use the 3 button navigation option? I often find the current apps (right most) button unresponsive, and often the "learn more" button on facebook pages unresponsive. Using gesture navigation works fine but not button navigation. I've tested this with 3 different launchers to verify it is not my Apex launcher I've be using for ages. Anyone else observe this?
I did still use 3-button navigation until my Pixel 6 Pro. I think my wife still uses the 3-button navigation, though.
I *might* have briefly had 3-button navigation enabled on the P6P, and it sounds familiar that I might have seen issues like what you describe with Recents. I didn't notice any problems regarding "learn more" on Facebook. I use Nova Launcher Prime.
Fakebook? People actually use that? I always blacklist all their domains on my DNS servers, pure hostile privacy invading trash.
Related
Our phone has a feature called Quicklinks, whereby if you pressed the search button plus a hardware keyboard key, you could quickly launch applications (i.e. search+e = email app).
Now, a bug in the software meant that the phone would sometimes think the search button was constantly pressed, so you would open the keyboard to answer to an SMS for example, and find yourself launching an app instead. The only workaround was to use the on-screen keyboard.
Before, in GB, this functionality could be disabled by going to Settings->Applications and disabling QuickLinks. This made the problem go away.
------
Enter ICS. The feature, with the same bug is still there, but I cannot find the QuickLinks entry in Settings->Applications. I've looked everywhere and I cannot find it.
Does anybody know where it is or how to disable it on the unusable official build of ICS?
I googled it and found that this may be what many people were looking for but I don't know why it started to behave like this.
I do find the swiping up from home button gesture useful for me to launch Google search but somehow it stop working. There usually should be a semicircle with 'Google' on top when halfway swiping up but what I get now is a search icon that function as it will launch last used app (if swiping gesture is done in launcher) or will do nothing (when gesture done in any app other than launcher). I did not disable Google Search, reboot didn't help, and clearing cache of Google search didn't help too.
I don't know what I did to get this as a result. Any clue on what's happening? Nexus 7 2013 stock kitkat
solution found
Dolphin browser causing this. Uninstalled it and everything is back to normal
I noticed that certain apps do not let me use the menu key/button. When i hold down the recents key for the menu on things like google search, drive or nova launcher, nothing happens. I feel it vibrate like it registered, but no menu pops up. I tried uninstalling exposed, using gravity box to add a nav bar, lmt/pie launcher, and still no menu commands work.
there are workarounds to access the menu on all of these, but it's just kind of annoying. Like these apps are on a blacklist somewhere saying to ignore the menu input.
Can anyone confirm if this is the case with them as well? I noticed this on stock and on iron rom. i have the 8.4.
thanks!!!!
I have Samsung Galaxy S5 Model 900T (klte)
Lineage OS 14.1 November 23, 2017
API Level Guava (7)
Security Patch Level Novembefr 6, 2017
Baseband Version: G900TUCU1GQC2
Kernel Version 3.4.113-lineageos-g746d931
Build Number: lineage_klte-userdebug 7.1.2 NJH47F-c26202ea25
The phone randomly switches to the split screen mode, usually when I am opening apps or using them (eg. ES File Explorer, Blue Mail, Google Search, Cloud Library, IHeart Radio app). I hear a short vibration, then the phone switches into split screen mode.
I have tried an app called MultiWindow Toggle but this does not solve the problem.
I have tried to switch the function of the short press of the recent button to no action and the long press of the recent button to recent apps switcher, but this makes the phone switch to the recent apps switcher.
I don't know if this is a hardware issue or a software issue, and if the latter, is it the os or some of the apps? Does any one have any guidance for how to solve this issue? It is very intrusive, and I really like the Lineage OS.
Thanks for any help that can be offered.
Sounds like a Hardware issue. Can you deactivate the button and activate software nav bar?
kurtn said:
Sounds like a Hardware issue. Can you deactivate the button and activate software nav bar?
Click to expand...
Click to collapse
I managed to modify the file named build.prop using some instructions I found online. It did activate the software nav bar. I expected it to disable the hardware buttons, but it did not. I still had the same problem.
I had to go into the settings for lineage and set the "recents" button to do nothing on short press and nothing on long press. The leftmost button on the nav bar now does nothing as well. The phone still vibrates a short blast randomly, but does not switch. The right most button on the software nav bar the one with the rectangle face, that one activates the task switcher now. The rightmost hardware button still acts as a "back" button, I want that function so I will leave it as is. I can live with that. I don't know a way to activate the split screen in this configuration, but I can live with that as well. Both the hardware home button and the center button on the software nav bar do the same thing now. I would like to be able to program the nav bar to do what I want it to do, is there a way to do that. If not, I can live with this.
Thanks for your help.
A couple of days ago, my HTC 10's "swipe down to expand notifications" gesture completely stopped working in all apps except launchers.
In both my chosen launcher, Nova, and the stock HTC Sense launcher, it still works. Having found that some buttons in full-screen games which are right at the top of the screen are also unresponsive, it seems that the top strip of the screen has become unavailable, except in launchers.
This bug appeared spontaneously - the phone was bought unlocked and stock and runs an unmodified Android 8.0.0. It has survived a power cycle and a phone reset.
Can anyone tell me what has happened and how to correct it? I've Googled the bug but found nothing helpful.
Thanks in advance for any light you can shed.