I have a stock Galaxy S6 with stock ROM and no mods at all.
Problem:
The problem started couple months ago where when I tap the back capactive key it acts like it was on hold for a time so it triggers the options context menu of the current app. That would trigger on some apps most of the time, another apps will sometimes pass, sometimes have the problem.
Here is exactly what happens when I tap the back key:
Tap *Vibration to let me know the hardware received my gesture*
No action
Tap again *no vibration this time - phone trying to complete (on its own) the time needed for the key to be held to trigger the HOLD action and open the options menu on the currently active app*
After some time, option menu (eg. settings menu on the top right corner of Whatsapp for example opens up)
This exact process happens so fast, and was inconsistent so I acted as if it was never there, and after sometime, it was gone for a short period of time, until Today, the problem reoccured again but now with the home button and the recent button.. Back button is fully working now.
Home button: Triggers Google Assistant
Recent button: Triggers Split View
I restarted my phone and now it's gone, but I know it is coming back.
I think it is not a hardware issue, how do I fix that annoying issue?
Current Version Info:
SM-G920F
Baseband: G920FXXU6ERCA
Android 7.0
Security Patch Level: March 1, 2018
Related
I was a bit surprised to just discover, by accident, that whenever I press any of the front hardware buttons when my device is in standby then the Touch Cruise doesn't completely ignore them, it switches on the button-panel lights for a while and then they go off after the timeout. For the red hangup key it also makes a beep when the button is pressed as well as activating the button lights.
As far as I can tell this is all the device does, it doesn't switch on the screen or activate any of the functions associated with the buttons I press (as far as I can tell) but I still worry that if I accidentally get the TC in a position in my pocket (when I'm driving or just sitting down for instance) where I'm constantly activating a button then after a few hours I could either drain the battery unnecessarily by keeping the button lights permanently on and/or I could crash the device by swamping it with button-pressed messages.
Do other people see the same behaviour when their TC is in standby and is there any hack to disable this?
- Julian
Try going into Settings - System - Key Lock
and change it to the top option "Lock all buttons except power button"
Same suggestion - doesn't make a sound here
That DOES happen when he is locked and NOT in standby. Still then - the volume keys work which is not really desired but hey...
Thank you mouseymousey and SabbeRubbish. You fixed my problem, but not in the way you probably intended.
I'd just been narrow minded and assumed that, if this option was available, it would be in the Button settings app so I hadn't seen the Key Lock settings app. Thanks to you both I found this and, guess what, the top "Lock all buttons except power button" WAS set but my buttons still activated the backlight and sometimes beeped.
Confused, I changed the option to the bottom "Do not lock buttons" and it behaved as expected, i.e. any button press completely woke up the device. I then set the option back to the top "Lock all buttons except power button" and this time my problem is solved, i.e. no reaction whatsoever from pressing the front buttons.
Wierd. My TC obviously got itself into an odd state and toggling the button lock preference seems to have fixed it. I'll keep an eye on this one.
Thanks again for the invaluable advice.
- Julian
I shouldn't let misleading info lie here so here's my confession. This issue turned out to be nothing to do with my device getting confused about its key lock setting. The fact that it fixed itself when I toggled the key lock setting was a coincidence, what I did at the same time as toggling the setting was to also close down Conduits PocketPlayer which I had still minimised and running (although not playing any music) in the background.
The problem appears to be with PocketPlayer (PP) and is 100% reproducible. If PP is still running (even minimized) when the device is put into standby then I get the behaviour described in my initial post, close down PP before going into standby and everything is OK and the front buttons are totally inactive.
I have of course filed a bug with Conduits but the good news is that noone needs to worry about any generic TC/WM6 wierdness here.
- Julian
Guys, since several versions of (mainly Energy) Roms (with Manila 2.1 as well as with 2.5) I have this problem: When I press the left phone button the phone does nothing instead of jumping into the phone mode. I need to switch it of (display switch on top of the phone) and on again, then it mostly works. Also the home button and the back button often scroll through the tabs instead of jumping directly to the home screen or ... Anybody else with this issue or - even better - with a solution?
Moved as not ROM Development.
When I press the left phone button the phone does nothing instead of jumping into the phone mode. I need to switch it of (display switch on top of the phone) and on again, then it mostly works. Also the home button and the back button often scroll through the tabs instead of jumping directly to the home screen
Click to expand...
Click to collapse
I have been having exactly the same problem for a few months. I was first thinking a hardware problem, perhaps the button contacts got munged (too much kevtris?). But it is very intermittent. Sometimes the problem lasts for a day, other times just a few minutes. Summary of intermittent problems:
Home button non-responsive. When running an app or in Sense/Manila/TouchFlo, pressing home does nothing.
Home button switches to the left Sense tab when in Sense. When viewing email, switches to a different email account. [Obviously being interpreted as a left-arrow.]
Back button non-responsive. When running an app, pressing back does nothing. Which makes it more difficult to navigate around.
Short-press send button non-responsive. Doesn't display dialer either when trying to start a new call, or returning to the dialer in a call.
Long-press send button non-responsive. Mapped to my task manager so should start that.
Possibly related - When reading emails zooming text size using the scroll wheel only works about half the time.
The PTT, volume, and power buttons always work fine.
I haven't noticed whether sleep/unsleep (short-press power button) helps.
Soft-reset sometimes helps, not always.
I don't hard-reset unless upgrading the ROM; this has survived across three different versions of EnergyROM.
I have had my phone since Nov 2008 and it was free, so I figure I got my money's worth.
EnergyROM 09.Mar.2010 WWE
Windows Mobile 6.5 Professional
CE OS 5.2.21895 (Build 21895.5.0.90)
Manila version: 2.1.19202517
Radio version: 1.14.25.35
Protocol version: 52.64c.25.35H
To orkan95: I have exact same problem as you: the "Answer", "Back", "Home" buttons sometimes scroll through different tabs, what's even worse for me is that when I open some item list (e.g. Emails, RSS ), it automatically scrolls up and down randomly (my finger wasn't even touch the phone) .
This has been a very annoying problem since Day 1 I had flashed my HTC Touch Pro with custom roms. I had been googling for a solution for this issue for several months now and no luck at all and would really appreciate if any experts in this forum could answer to this issue. Thanks!
FYI, I personally don't think it's the hardware's problem as it worked well with the original official Rom (6.1). The problem only emerged when I flashed with any Custom Roms.
Hi all, I want to try Cyanogenmod 7 (latest nightly of course), but I realized that the end button (red end call button) behavior is different from the stock rom. The stock rom behavior is:
if not in home screen -> go to home screen
if in home screen -> do nothing
if locked and screen turned on -> turn screen off
everything else -> do nothing
Notice that pressing the end button seems to be different than pressing the home button: if the current foreground activity does not respond, home button won't work (ANR window will show up); end button, instead, will simply go to home screen, like if it's killing the current activity. However, relaunching the closed activity restores its previous state (like when I use the home button to get away from an activity).
Cyanogenmod has stock gingerbread behavior (which should be fine, I know it's the android way), but I really would like to preserve my habits.
I already tried:
Spare parts: does not have the option I'd like
Remapping keys via keymaps: doesn't work since behavior cannot be defined using the available built-in commands
I'll get my hands dirty in the Android code if necessary (I'm a developer), but I really want to know if there is another way before looking at the source code.
I got my OnePlus One 64 GB, Indian edition (so no updates from CM) 2 days ago. I quickly switched to software keys (creature of habit, previous phone had them). My personal preference for software navigation keys is to place the back button on the right side and the multitasking one on the left, plus a rightmost toggle for search button/magnifying glass (I find this configuration very productive). I use the following process to change them:
1. Settings->Buttons
2. Software buttons layout->Lock icon
3. Make changes->Lock icon again to save changes
The said changes are reflected, and I'm able to observe them.... until the device locks. After unlocking, the software keys are reset to the default configuration: back key, home and multitasking button. I've tried rebooting the device and it doesn't help. Only thing I've changed in the device is switching to ART, everything else is stock. Can't wrap my head around the issue, so any help would be appreciated. Thanks!
I'm having a weird issue with my Pixel 1, all of a sudden my swipe from bottom home gesture stopped working. I enabled the soft buttons bar again but even tapping the home button there does nothing neither does the app drawer button, however the back gesture and button works fine.
There's also a few more oddities like my registered fingerprints got deleted so I had to register them again, some settings were changed like the order of the quick action icons, swiping the fingerprint reader down doesn't open notifications, and so on.
I've had issues with my battery for a while so I thought it could be related but I still have issues after replacing it. Is this a know issue or some sort of malware maybe? I'm thinking about doing a factory reset but I'm wondering if there's a less nuclear option.
Thanks!
Device Model: G-2PW4200
Android Version: 10