The Bluetooth button on the phone screen (during a call) has never worked for me. To turn on bluetooth I have to go back to home screen and turn it on from there. Is this only my phone or is this true for others?
drraypalmer said:
The Bluetooth button on the phone screen (during a call) has never worked for me. To turn on bluetooth I have to go back to home screen and turn it on from there. Is this only my phone or is this true for others?
Click to expand...
Click to collapse
I haven't used Bluetooth recently, but as an option you could also put the Bluetooth widget in the strip of notifications power widget, available when you pull the notification bar down. More convenient than on the in-call screen anyway.
Configure what widgets are present and what order they're presented in here -> Settings/CyanogenMod settings/Interface/Notification power widget
From there choose "Widget buttons" to choose what widgets to show, and "Widget button order" to change what order they're shown in.
Hint: If you unchoose all the notification power widgets from the "Widget buttons" menu, and then re-choose only the ones you want and in the order you want them, you won't have to re-order them in the "Widget button order" menu.
Thanks, I actually had the button on the notification screen, just hadn't thought of using it during a call yet. Good idea! I'm still curious why the in-call button doesn't work, but this will make it easy enough to turn on.
Just flashed from GSBv2.2G to GSBv2.5 this morning and haven't tried that bluetooth button on the phone screen yet.
I'm using the notification power widget and it works like a charm. Super fast compared to stock.
drraypalmer said:
Thanks, I actually had the button on the notification screen, just hadn't thought of using it during a call yet. Good idea! I'm still curious why the in-call button doesn't work, but this will make it easy enough to turn on.
Click to expand...
Click to collapse
You're welcome! Probably just an oversight in the CM7 development.
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.
i have read this post http://forum.xda-developers.com/showthread.php?t=1168660
but i still don't know what to do for my phone
the power menu is easy to bring up in the lockscreen while i am holding the phone, or in my pocket. and so it is easy to reboot itself accidentially
if anyone help how to disable the power menu in the lockscreen, it will be very helpful .
thanks so much
Wake up!
Waking up this same problem..
Is there any way to disable the phone options when the screen is locked. Main purpose is when stolen. I told my friends to hide my phone on one of their pockets, then i'll send an alarm text using Gotya! app but nothing happened..
Found out that one of my friends turned off my phone by using phone options on the lockscreen..
http://forum.xda-developers.com/showthread.php?t=2404042
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.
My Chromebook used to turn off the screen anytime I pressed the power button. I often use it to type notes during presentations, and I loved having a fast easy way to turn off the screen to save power if I knew I wouldn’t be typing anything for 5 or 10 minutes.
A few months ago, a ChromeOS update changed this so it only works it tablet mode now, pressing the power button in laptop mode now opens an on-screen menu with options to shutdown, log off, or lock screen. The best workaround I have found so far is to use the brightness keys to get the screen off, but it’s a pain to get it back to the right brightness level every time.
I have the Chromebook in developer mode, and I would like to do one of the following (in order from most to least preferred):
1. Restore power button functionality to how it was before.
2. Re-purpose the lock screen button on the keyboard for turning off the screen.
3. Add a keyboard shortcut to toggle the screen on and off.
4. Add a “Turn off screen” option to the current on-screen menu.
I never really modified ChromeOS before. Has anyone else done these things? Where should I begin? Thank you.
Here is some relevant documentation, maybe the information at the bottom is useful?:
https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/docs/power_buttons.md
I was able to do it by adding the flag "--force-tablet-power-button" to /etc/chrome_dev.conf and restarting the UI, but changes to that file don't seem to persist accross system reboots.
edit: I used the instructions at the bottom of this page: http://www.chromium.org/developers/how-tos/run-chromium-with-flags