Very pleased with the new phone but I've had the home screen freeze on me twice in the same horrible way.
While swiping the lock screen away, it will stick covering about a 1/4 of the screen - then the screen completely locks. After a while a partially hidden alert box comes up with some warning about the Activity TwLauncher not responding and you can see the close/wait buttons, but you cannot press them. Pressing the sleep button blanks the screen, but it displays the same mess when the home button is pressed.
The OS underneath still seems to be running, because if I call the phone, the dialer appears and I can take a call - just that after ending the call, the screen goes back to the frozen home screen with the half hidden alert box under a partial lock screen.
Even holding the power button down will not pop up the dialogue box for power off - so the only way I've found to recover is to pull the battery.
Has anyone else encountered this bug - couldnt find anything similar using the forum search tool - or a quick google.
I did recently update to KE7.
Galaxy Nexus
Android Version: 4.2.2
Steps to reproduce the problem:
- plug in headset
- lock screen
- press headset button for several seconds
What happened:
- No reaction, Google Now / Voice Actions not launched
- Manually unlock screen
- Long press with unlocked screen correctly launches Voice Search
What you think the correct behaviour should be:
Long press of headset button should launch Google Now / Voice Actions even with locked screen. Having to dig the phone out of your pocket in order to launch Voice Actions with a headset e.g. to place a call kinda defeats the purpose of using Voice Actions in the first place.
Adding insult to injury: long press is not broadcast to other applications because of Google Now, so it can't even be put to good use e.g. as volume control.
This was open and ignored by code.google.com Issue 48616
I also have the same problem. The restriction is not due to the lockscreen, apparently. If you disable the option "Power button immediately locks screen" and set "Automatically lock screen after sleep" time to a long enough time, still the long press doesn't work.
It works fine only when screen is on and unlocked. Weird. There is no point of this shortcut if our phone is unlocked and on, because in such a scenario, if headset is connected and phone is awake and unlocked, it means the phone is in our hands. And if it is in our hands, we can just press the button on the Search widget instead of long pressing the headset button. This is pathetic.
rhoadster91 said:
I also have the same problem. The restriction is not due to the lockscreen, apparently. If you disable the option "Power button immediately locks screen" and set "Automatically lock screen after sleep" time to a long enough time, still the long press doesn't work.
It works fine only when screen is on and unlocked. Weird. There is no point of this shortcut if our phone is unlocked and on, because in such a scenario, if headset is connected and phone is awake and unlocked, it means the phone is in our hands. And if it is in our hands, we can just press the button on the Search widget instead of long pressing the headset button. This is pathetic.
Click to expand...
Click to collapse
I'm affected by this as well.. I love calling upon Google Now from the headset, but sucks that I have to first unlock the screen on the Nexus 4 to do this. I'm OK with this being off by default, but users should be offered an option to turn this on while screen is locked.
Levistras said:
I'm affected by this as well.. I love calling upon Google Now from the headset, but sucks that I have to first unlock the screen on the Nexus 4 to do this. I'm OK with this being off by default, but users should be offered an option to turn this on while screen is locked.
Click to expand...
Click to collapse
Android apparently wants you looking at the screen so you can see the advertisements, so much for being the "open" OS.
So, guys, still no solution to fix this???
Darksydecad said:
Galaxy Nexus
Android Version: 4.2.2
Steps to reproduce the problem:
- plug in headset
- lock screen
- press headset button for several seconds
What happened:
- No reaction, Google Now / Voice Actions not launched
- Manually unlock screen
- Long press with unlocked screen correctly launches Voice Search
What you think the correct behaviour should be:
Long press of headset button should launch Google Now / Voice Actions even with locked screen. Having to dig the phone out of your pocket in order to launch Voice Actions with a headset e.g. to place a call kinda defeats the purpose of using Voice Actions in the first place.
Adding insult to injury: long press is not broadcast to other applications because of Google Now, so it can't even be put to good use e.g. as volume control.
This was open and ignored by code.google.com Issue 48616
Click to expand...
Click to collapse
Levistras said:
I'm affected by this as well.. I love calling upon Google Now from the headset, but sucks that I have to first unlock the screen on the Nexus 4 to do this. I'm OK with this being off by default, but users should be offered an option to turn this on while screen is locked.
Click to expand...
Click to collapse
vivekiny2k said:
Android apparently wants you looking at the screen so you can see the advertisements, so much for being the "open" OS.
Click to expand...
Click to collapse
Elastep said:
So, guys, still no solution to fix this???
Click to expand...
Click to collapse
Please check this link
rhoadster91 said:
Please check this link
Click to expand...
Click to collapse
I got so fed up I wrote my own app. If you have s voice, the phone wakes up on long press and My app takes over. I an releasing another version tomorrow. I still have to update the video demo.
http://forum.xda-developers.com/showthread.php?t=2289104
There's a solution
Darksydecad said:
Galaxy Nexus
Android Version: 4.2.2
Steps to reproduce the problem:
- plug in headset
- lock screen
- press headset button for several seconds
What happened:
- No reaction, Google Now / Voice Actions not launched
- Manually unlock screen
- Long press with unlocked screen correctly launches Voice Search
What you think the correct behaviour should be:
Long press of headset button should launch Google Now / Voice Actions even with locked screen. Having to dig the phone out of your pocket in order to launch Voice Actions with a headset e.g. to place a call kinda defeats the purpose of using Voice Actions in the first place.
Adding insult to injury: long press is not broadcast to other applications because of Google Now, so it can't even be put to good use e.g. as volume control.
This was open and ignored by code.google.com Issue 48616
Click to expand...
Click to collapse
You can enable it by, either
1) setting the unlock pattern to none(that will completely disable locksreen, and you can use the google now feature even in screen off)
2) setting the unlock to any pattern and uncheck the "power button instantly locks screen" - in this way you can use the the feature withing the time you specify in the lock screen
CellSmart! said:
You can enable it by, either
1) setting the unlock pattern to none(that will completely disable locksreen, and you can use the google now feature even in screen off)
2) setting the unlock to any pattern and uncheck the "power button instantly locks screen" - in this way you can use the the feature withing the time you specify in the lock screen
Click to expand...
Click to collapse
Sorry, I have the same problem, I tried this, but this doesn't work...
Any ideas?
Cheers,
--
Steph
Me too
I'm also in the boat of wanting to access Google now while the phone sits in my pocket and I'm wearing headphones. I can kinda understand why they disallow this (so a thief can't make calls on your dime), but it'd be very nice to at least launch apps.
Even xposed's app settings, with Google search allowed to show on the lock screen, doesn't make it happen. I just get a message saying I need to unlock my phone.
The only idea I currently have to launch it over the lock screen is to use auto voice with Tasker. Perhaps I could get it to launch/listen with a triple tap (because long press is locked up by Google now) via degauss. I just hope it all works over the lock screen. I'll update if/when it happens.
tcg-2 said:
I'm also in the boat of wanting to access Google now while the phone sits in my pocket and I'm wearing headphones. I can kinda understand why they disallow this (so a thief can't make calls on your dime), but it'd be very nice to at least launch apps.
Even xposed's app settings, with Google search allowed to show on the lock screen, doesn't make it happen. I just get a message saying I need to unlock my phone.
The only idea I currently have to launch it over the lock screen is to use auto voice with Tasker. Perhaps I could get it to launch/listen with a triple tap (because long press is locked up by Google now) via degauss. I just hope it all works over the lock screen. I'll update if/when it happens.
Click to expand...
Click to collapse
I found a fix for this (yes I know this is old but anyway). You have to install the xposed module "xposed additions" and set the long press headset button to unlock the phone. when the phone is unlocked you can simply long press the button again and google voice search will come up. this way you have to long press the button twice but at least it works
spiderflash said:
I found a fix for this (yes I know this is old but anyway). You have to install the xposed module "xposed additions" and set the long press headset button to unlock the phone. when the phone is unlocked you can simply long press the button again and google voice search will come up. this way you have to long press the button twice but at least it works
Click to expand...
Click to collapse
thanks spiderflash, this would work but fully unlocks the phone instead of just the Google now search, guess we have to wait for google to fix it.
I've got it
I've developed a good way to do this now. I've had it for the past 2 months or so, but I was waiting until I could go 2 weeks without a hitch.
You need 4 apps: tasker, secure settings, headset button controller and (if you don't for some reason have it) Google Now.
1. Tell hbc to perform a Tasker task (whatever you want to name it, e.g. 'launch voice search') for 3 clicks
2. Task should do the following: turn screen on, keep screen on at least 15 seconds, launch Google voice search [this is where you say your command, e.g. 'play some music'], lock screen, turn screen off.*
If you want to make this slightly less complex, you can simply have it turn the screen on, then you have to manually say 'OK Google,' then say your voice command (as long as you have Google Now available from the lock screen), but I'm trying to get directly to voice search, which won't launch directly if the screen is locked.
For some reason clicking the headset button 3 times sometimes doesn't trigger the first time after you plug in your headset (but works fine once it's triggered the first time until you unplug and re plug). Sometimes you need to do it twice if you don't hear the little Google Now voice beep.
So I hope this helps, but if you develop a better way to do this, please let me know.
* This is because, before I added this, motion in my pocket with the screen on caused it to swipe to the camera, where it will not turn off by itself. It stayed on for a good half hour in my pocket that day.
I have found the solution.
I had three Assist Apps . When I long pressed headset button while screen unlocked, it asked me to choose between Google, Autovoice and Tasker Secondary. I chose Google. From there on Assistant wakes up on long press headset button when screen is on.
When the screen is off, and you long press the headset button the same options popup but you don't see because screen is locked. Now Assistant can't run untill you set the default assist app on lockscreen.
Solution:
Lock your screen.
Long press headset button.
Within 3 sec pressing quickly unlock the phone.
You will see the dialogue asking to choose assist app.
Choose google.
Solved.
Hi
I have a galaxy s3 with cm11 and boeffla kernel. Today, out of nowhere, my home button and menu button started acting weird. I have the home button setted to sleep my phone on long press and wake it up when the screen is off and do nothing on double press . The menu is set to open the recent apps. It has always worked this way till today.
When I press the home button inside an app it won't return to the home but it still wakes the phone when the screen is off. Also the menu won't open the recent apps and it doesn't vibrate either. The back button still works but does not vibrate. I used gravity box to activate the navigation bar and the home button doesn't work on the navigation bar either.
I tried installing upgrating my firmware to the latest nightly, wipe cache and dalvik but no luck.
You won't repair a modded framework, wipe and start again.
So I need to do a factory reset? Is there a way to know what happened? I didn't touch anything. Is it possible that some xposed module caused this?
Is there anyway I can have the navigation bar on all the time? Including fullscreen videos? I hate having to click back on the camera (and other apps) for the navbar to appear when I can just press home if the navbar was always on. Is there anyway to do this through Xposed orany other method?
The soft keys?
If you're talking about the soft keys then there are 2 ways for them to pop up on the screen.
1. Tap the screen (this only works on certain apps)
2. Swipe - if you're in landscape mode then swipe the right edge inwards the soft keys will appear.
If you're in Portrait then swipe up from the bottom edge and the soft keys will appear.
But if you're talking about the Navigation bar then you need to swipe Downward no matter if you're in Landscape or Portrait..
Double0EK said:
The soft keys?
If you're talking about the soft keys then there are 2 ways for them to pop up on the screen.
1. Tap the screen (this only works on certain apps)
2. Swipe - if you're in landscape mode then swipe the right edge inwards the soft keys will appear.
If you're in Portrait then swipe up from the bottom edge and the soft keys will appear.
But if you're talking about the Navigation bar then you need to swipe Downward no matter if you're in Landscape or Portrait..
Click to expand...
Click to collapse
I know how to make them appear, I'm asking if there's a way to make them stay there all the time like physical keys. Off topic is there also a way to remove the delay response of holding the power button for the power options to appear?
KanBorges said:
I know how to make them appear, I'm asking if there's a way to make them stay there all the time like physical keys. Off topic is there also a way to remove the delay response of holding the power button for the power options to appear?
Click to expand...
Click to collapse
Sorry I can't give you firm answers because my phone is with LG for repair, but I do recall seeing in settings options for when the buttons appear and disappear. It allowed you to set it on a per-app basis.
As for the delay response for the power button, your best bet would be to see if there is an Xposed plugin. To use Xposed you'll need to root the phone.
When I get my phone back I can give you more specifics, but LG has the worst warranty repair service and has yet to fix the issue after sending it to them four times.
You at JBLM? Thanks for your service!
silcam18 said:
Sorry I can't give you firm answers because my phone is with LG for repair, but I do recall seeing in settings options for when the buttons appear and disappear. It allowed you to set it on a per-app basis.
As for the delay response for the power button, your best bet would be to see if there is an Xposed plugin. To use Xposed you'll need to root the phone.
When I get my phone back I can give you more specifics, but LG has the worst warranty repair service and has yet to fix the issue after sending it to them four times.
You at JBLM? Thanks for your service!
Click to expand...
Click to collapse
Thanks for your reply :angel: but I've looked at everything possibly related to power button delay or the navigation bar (soft keys) on Xposed before posting here and still nothing. I did find a screenshot delay remover in Xposed and works great. Finding the power button is not as important as the soft keys because I can just use Rom Toolbox's rebooter and power/reboot/recovery etc... The soft keys thing on the other hand I would like to have because I hate having to pull up for them to make them appear... Iv'e looked at the settings you mention for showing/not showing per app but every app is not listed, its just some of the apps on your phone (apps that I would like to have the soft keys always on are mostly video apps which are not listed on this settings.) I', almost used to it by now, I just rather have the keys always on or a phone with actual physical keys.
Yes I live in JBLM . I'm a dog handler in the Army.
It's been bugging me for a while, I was occasionally getting no response when hitting the home button (traditional on-screen navigation) and think I've figured out what's happening.
If I hit the button with a slight upward swipe it shows the Google assistant/shade animation but doesn't perform the button action. (I'd tried disabling assist, turning swipe navigation on/off and even resetting the tablet but nothing had any effect.)
This is on an 8.4 inch tablet with the Pie update and I have a feeling that the problem didn't exist before, can anyone still on Oreo confirm that this issue doesn't exist with that or anyone on Pie confirm that they are also being affected.
I have a feeling that the code to detect the swipe gestures is still there when using traditional nav but set to take no action.
If it affects others using Pie, I'll log a support ticket with a Huawei.
Thanks...
Sent from my SHT-W09 using Tapatalk
No problems here EMUI 8