Related
Jelly Bean introduced headset controls which allowed Play/Pause and Next for single and double presses respectively on headsets. I can confirm both these work just fine.
However, the long-press option to launch Voice Search only works while screen is unlocked. When screen is locked, long-press has no effect (it does not even register as a single press)
I tried the following:
1. Disabling Pattern lock (which I mostly use)
2. Turning on screen (but still locked) and then long pressing.
3. Keeping Google Search on in the background and then locking screen.
No luck.
Cannot seem to get any useful info regarding this on the Internet.
There is no point in the voice search shortcut on headsets if the phone has to be dug out from my pocket and unlocked. There has to be a way to bypass that.
Can somebody help??
EDIT: I am also unsure if this is an Android-specific problem or a ROM specific problem, so it would be kind of you if you could test it yourself. You can see my ROM details in the signature. I use Samsung headset in combination with my Nexus 4.
UPDATE: I tried turning off the "Power button immediately locks phone" option and set "Automatically lock phone after sleep" time to 30 minutes. Still the long press doesn't work. It works only after screen is turned on again. Whaaaaa...?!
ANOTHER UPDATE: This issue is present on Google Code but it has been closed without further comments. Please star this issue so that it is noticed by the development team.
Been really frustrated about this as well. Any help would be greatly appreciated.
I'm running Jellybeer 4.0 on SGH i717m
Astounding. I even have to use a third party app to dial by voice reliably. What good is Google's extensive voice technology if you can't use it?
I'm equally as confused. One advantage of owning an iPhone is that you've got an excellent bike companion that could read and reply to texts, make calls, check the time, etc all while keeping my eyes on the road and hands on my handlebars. I always figured my Nexus S didn't do that because I was running a different ROM - but 4.2 on a brand new Nexus.....come on.
rhoadster91 said:
Jelly Bean introduced headset controls which allowed Play/Pause and Next for single and double presses respectively on headsets. I can confirm both these work just fine.
However, the long-press option to launch Voice Search only works while screen is unlocked. When screen is locked, long-press has no effect (it does not even register as a single press)
I tried the following:
1. Disabling Pattern lock (which I mostly use)
2. Turning on screen (but still locked) and then long pressing.
3. Keeping Google Search on in the background and then locking screen.
No luck.
Cannot seem to get any useful info regarding this on the Internet.
There is no point in the voice search shortcut on headsets if the phone has to be dug out from my pocket and unlocked. There has to be a way to bypass that.
Can somebody help??
EDIT: I am also unsure if this is an Android-specific problem or a ROM specific problem, so it would be kind of you if you could test it yourself. You can see my ROM details in the signature. I use Samsung headset in combination with my Nexus 4.
UPDATE: I tried turning off the "Power button immediately locks phone" option and set "Automatically lock phone after sleep" time to 30 minutes. Still the long press doesn't work. It works only after screen is turned on again. Whaaaaa...?!
ANOTHER UPDATE: This issue is present on Google Code but it has been closed without further comments. Please star this issue so that it is noticed by the development team.
Click to expand...
Click to collapse
the closest thing that i know of is using touch control to swipe to unlock (like pressing the power button) the using NAV RING to swipe the nav ring to google search, or what ever app you like. not sure if this is what you want but it may get you closer.
HB66 said:
the closest thing that i know of is using touch control to swipe to unlock (like pressing the power button) the using NAV RING to swipe the nav ring to google search, or what ever app you like. not sure if this is what you want but it may get you closer.
Click to expand...
Click to collapse
Here is what appears to be the correct place to file this complaint.
https://productforums.google.com/d/msg/websearch/ZbaIyhTIje4/GAKOqRrNjnAJ
Someone else started the report, I added as well, maybe someone at google will see and fix this oversight.
I have to admit I have wanted to be able to do this for a long time on my motorcycle, being able to press one button and use voice controls would be a god send, although when riding I use an E-Dash app that keeps the screen awake so voice is available.
Still.......would be nice to be able to leave the phone alone, say in a bag or on my hip and use my Bluetooth headset to do all the work
Sent from my Nexus 4 using xda app-developers app
WilliamWynter said:
Been really frustrated about this as well. Any help would be greatly appreciated.
I'm running Jellybeer 4.0 on SGH i717m
Click to expand...
Click to collapse
Solutions Etcetera said:
Astounding. I even have to use a third party app to dial by voice reliably. What good is Google's extensive voice technology if you can't use it?
Click to expand...
Click to collapse
bryantee said:
I'm equally as confused. One advantage of owning an iPhone is that you've got an excellent bike companion that could read and reply to texts, make calls, check the time, etc all while keeping my eyes on the road and hands on my handlebars. I always figured my Nexus S didn't do that because I was running a different ROM - but 4.2 on a brand new Nexus.....come on.
Click to expand...
Click to collapse
HB66 said:
the closest thing that i know of is using touch control to swipe to unlock (like pressing the power button) the using NAV RING to swipe the nav ring to google search, or what ever app you like. not sure if this is what you want but it may get you closer.
Click to expand...
Click to collapse
thedarkharlequin said:
Here is what appears to be the correct place to file this complaint.
https://productforums.google.com/d/msg/websearch/ZbaIyhTIje4/GAKOqRrNjnAJ
Someone else started the report, I added as well, maybe someone at google will see and fix this oversight.
Click to expand...
Click to collapse
Lord_alias said:
I have to admit I have wanted to be able to do this for a long time on my motorcycle, being able to press one button and use voice controls would be a god send, although when riding I use an E-Dash app that keeps the screen awake so voice is available.
Still.......would be nice to be able to leave the phone alone, say in a bag or on my hip and use my Bluetooth headset to do all the work
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Please check this link
My solution:
1. Download Bluetooth Launch from Play Store
2. Launch, scroll to Google Search and expand it
3. Enable option “com.google.android.googlequicksearchbox.VoiceSearchActivity”
4. close
5. launch Google Now go to Settings -> Voice and enable Bluetooth Headset option
6. connect not working Bluetooth or wired headset and long press button. Dialog should appear and select Bluetooth Launcher always!
7. test if this is the complete solution for you. If it doesnt work properly when screen is locked try following:
- Install Xposed Framework
- go to Downloads and Install "AppSettings"
- open AppSettings and go to Google Search
- Turn On Settings and check "Show when locked"
- save
- restart Phone
If you are having issues with your selected language in Google Now. Also use AppSettings and change Location for Google Search to desired one. Now you should be able to use Google Now in your preferred language.
stunner2002 said:
My solution:
1. Download Bluetooth Launch from Play Store
2. Launch, scroll to Google Search and expand it
3. Enable option “com.google.android.googlequicksearchbox.VoiceSearchActivity”
4. close
5. launch Google Now go to Settings -> Voice and enable Bluetooth Headset option
6. connect not working Bluetooth or wired headset and long press button. Dialog should appear and select Bluetooth Launcher always!
7. test if this is the complete solution for you. If it doesnt work properly when screen is locked try following:
- Install Xposed Framework
- go to Downloads and Install "AppSettings"
- open AppSettings and go to Google Search
- Turn On Settings and check "Show when locked"
- save
- restart Phone
If you are having issues with your selected language in Google Now. Also use AppSettings and change Location for Google Search Now you should be able to use Google Now in your preferred language.
Click to expand...
Click to collapse
But Exposed Framework requires your phone to be rooted, which I'm done doing... to much of a pain when it comes time to update
Would it be possible? Including the voice wake functionality "Okay, Google Now" instead of "Hi Galaxy"?
How many would be interested in something like this?
Should not be too hard to do, what do you think?
Probably will need root to achieve it
----
SOLVED: using a very simple tasker profile/action (see here)
UPDATE: Install this tiny free app from the Play store: https://play.google.com/store/apps/details?id=hu.viczian.deathtosvoice (created using Tasker App Factory)
Works on galaxy advancement
vgergo said:
Would it be possible? Including the voice wake functionality "Okay, Google Now" instead of "Hi Galaxy"?
How many would be interested in something like this?
Should not be too hard to do, what do you think?
Probably will need root to achieve it
Click to expand...
Click to collapse
Works on galaxy advancement? thank you
Leonardosilvaa said:
Works on galaxy advancement? thank you
Click to expand...
Click to collapse
For some reason, I can now double tap home button and I get the option for S-voice or Google voice. I think I cleared the defaults in app settings.
Presjar said:
For some reason, I can now double tap home button and I get the option for S-voice or Google voice. I think I cleared the defaults in app settings.
Click to expand...
Click to collapse
Any idea how to replicate this?
Presjar said:
For some reason, I can now double tap home button and I get the option for S-voice or Google voice. I think I cleared the defaults in app settings.
Click to expand...
Click to collapse
Yeah I got this too. It happened after I installed SoundHound.
Now I have the options of
Google
S Voice
SoundHound
Interesting but without the option to activate gvoice with screen off its not a huge benefit. I tested open mic+ but it lacks admin rights to bypass the lockscreen etc.
vinokirk said:
Yeah I got this too. It happened after I installed SoundHound.
Click to expand...
Click to collapse
The free version? I've tried that but I don't see a menu after double clicking home.
mgutt said:
Interesting but without the option to activate gvoice with screen off its not a huge benefit. I tested open mic+ but it lacks admin rights to bypass the lockscreen etc.
Click to expand...
Click to collapse
You mean root permissions?
Sorry, I was wrong. I thought S-Voice is able to bypass a pin lockscreen but it isn't. It is only admin (not root) to allow the screen off command.
The problem of open mic+ is, that it is buggy. It seems to freeze after a short time. Sometimes Google Now freezes as well so I think it is because of Open Mic+ but I didn't tested it enough to verify it. S-Voice seems to be more stable, but is not present if you are in other apps like Maps.
But both systems are too weak in rights. e.g. I'm not able to stop apps (ok root would be needed), not able to say my lockscreen pin, stop a phone call, etc.
Tasker
I just had an idea: it should be possible to create a very simple tasker action, which would be triggered by opening s-voice. It would exit s-voice and switch immediatelly to Google Voice Search. This should work even without rooting.
If this would work, all the convenient ways to start S-Voice would become actually useful to start Google Voice search, including voice-wake, home-double-click, headset-long-press.
I will try this as soon as I get my N3
How do you want to exit S-Voice without root
There's the point! Okay, without root we can just switch away (would mic input focus stay? that would be a problem), with root it should be possible to kick s-voice too.
If one app opens the mic the other will display an error.
Tasker solution works well on unrooted phone
mgutt said:
If one app opens the mic the other will display an error.
Click to expand...
Click to collapse
I am happy to report, that the solution I came up with before I had access to the Note 3 works without a hitch.
1. Enable wake-up hotword detection in S-Voice (keep double click Home if you like that too)
2. Create "S Voice" app-triggered tasker profile
3. The activated task should load "Voice Search"
4. Optional step: after starting voice search, my task also kills S-Voice to save memory
(and killing s-voice every time makes you me good)
There is no concurrency problem with the mic (as we were anticipating)
Say "Hi galaxy" while having the screen turned off
(I actually like to "say Die galaxy")
phone wakes up,
home screen unlocks,
s-voice flashes on screen for half a sec (beeps too)
then google voice search appears immediately
it too beeps and listens for the search term or command
Next project: it would be nice to be able to change the "hi galaxy" wake up command
The changeable wake up command is part of the Galaxy S4 S-Voice so I think it will be part in the Note 3 in one of the next updates (hopefully).
Of course I tested your idea, too. But it seems that it works better with Llama than with Tasker as Google Voice starts immediately. As I'm not rooted its not as perfect as yours (I need to tap backwards fast to bypass restarting Google Voice), but the goal is reached
Look:
http://www.maxrev.de/google-sprachsuche-statt-s-voice-mp4-v377253.htm
Update:
Ok I found a better solution. Know I'm using three rules instead of one and this is how it works:
Final Demo Video
The first rule starts Google Voice, but checks if the variable "googleSearch" is not 1 (this is important as it fails, too if the variable does not exist after rebooting the device). The second rules sets the var to "1" if Google Voice is open. The last rule resets the var to "0" with a delay of 3 seconds after Google Voice has been closed. So I'm having 3 seconds to close S Voice before Google Voice would start again.
If you don't want to here the "ping" sound of S Voice after closing Google Voice it would be possible to mute the device for 3 seconds as well, but I don't think this is really important
mgutt said:
The changeable wake up command is part of the Galaxy S4 S-Voice so I think it will be part in the Note 3 in one of the next updates (hopefully).
Of course I tested your idea, too. But it seems that it works better with Llama than with Tasker as Google Voice starts immediately. As I'm not rooted its not as perfect as yours (I need to tap backwards fast to bypass restarting Google Voice), but the goal is reached
Look:
http://www.maxrev.de/google-sprachsuche-statt-s-voice-mp4-v377253.htm
Update:
Ok I found a better solution. Know I'm using three rules instead of one and this is how it works:
Final Demo Video
The first rule starts Google Voice, but checks if the variable "googleSearch" is not 1 (this is important as it fails, too if the variable does not exist after rebooting the device). The second rules sets the var to "1" if Google Voice is open. The last rule resets the var to "0" with a delay of 3 seconds after Google Voice has been closed. So I'm having 3 seconds to close S Voice before Google Voice would start again.
If you don't want to here the "ping" sound of S Voice after closing Google Voice it would be possible to mute the device for 3 seconds as well, but I don't think this is really important
Click to expand...
Click to collapse
thats excellent Mgutt
the note does the transition across to google now/voice commands very quickly.. you have put the note back on the table as an option for my next phone.. im just holding out to see if the LG G2 will use the S800 for always on listening when it gets kitkat..
Im a bit spooked by AMOLED now that my galaxy S2 is marred by burn in
etherspin said:
thats excellent Mgutt
the note does the transition across to google now/voice commands very quickly.. you have put the note back on the table as an option for my next phone.. im just holding out to see if the LG G2 will use the S800 for always on listening when it gets kitkat..
Im a bit spooked by AMOLED now that my galaxy S2 is marred by burn in
Click to expand...
Click to collapse
I'm having one problem left. But I think its because of Llamas limited amount of triggers. The problem is: Google Voice is not able to receive the next command while its open. Instead S Voice waits for the next "Hello Galaxy". To bypass this problem I tried to switch off the display automatically. This works, but only with a fixed delay as I'm not able to trigger "last touch/last talk + 10 seconds" with Llama.
Would this work with Tasker (and without Root)?
The next option would be to activate "Open Mic+" as long Google Voice is open. But I did not tested if this would work.
mgutt said:
Would this work with Tasker (and without Root)?
Click to expand...
Click to collapse
Well we can set the display timeout to 15sec, then restore the default (it's 30 sec for me because of smart stay) when google voice search disappears.
Because of the 30 sec display timeout it hasn't been much of a problem for me, but I was also wondering how to get it to prompt for a next question.
Curious: why doesn't the "ok, google" hotword work in google now? I've just tested the google experience launcher and hot word detection doesn't work in there either.
vgergo said:
Well we can set the display timeout to 15sec, then restore the default (it's 30 sec for me because of smart stay) when google voice search disappears.
Click to expand...
Click to collapse
I'm using this setup (after 20 seconds display is turned off) and this is not good if you press the microphone button. Then the display switches off, too. So we need an additional "on touch" condition to avoid that.
mgutt said:
I'm using this setup (after 20 seconds display is turned off) and this is not good if you press the microphone button. Then the display switches off, too. So we need an additional "on touch" condition to avoid that.
Click to expand...
Click to collapse
Okay, then set the display timeout to 15sec, wait 15sec then set it back to whatever it used to be. Then if the screen was touched (and the display timeout extended) then it will stay on...
I hope to be able to test these with tasker in the afternoon
If anyone does not want the vibration to occur when opening the camera with the wrist twist method, I found that it can be turned off by using the Xposed mod: (you need root) install AppOpsXposed then going to App Ops in setting, go to device, and turn off vibration rights on the camera app. No more vibration! I was also looking for a way to turn off vibration when unlocking in active display (though the 4.4 update made it a lot less intense) but I haven't found a way without just turning all vibration off. I have a love hate thing with haptic feedback. Anyway, hope this helps someone.
Pwnicorn said:
If anyone does not want the vibration to occur when opening the camera with the wrist twist method, I found that it can be turned off by using the Xposed mod: (you need root) install AppOpsXposed then going to App Ops in setting, go to device, and turn off vibration rights on the camera app. No more vibration! I was also looking for a way to turn off vibration when unlocking in active display (though the 4.4 update made it a lot less intense) but I haven't found a way without just turning all vibration off. I have a love hate thing with haptic feedback. Anyway, hope this helps someone.
Click to expand...
Click to collapse
You can probably do this without Xposed and just using App Ops (and/or App Ops X). I saw that camera had vibrate but didn't make the connection to the twist to launch gesture. I don't mind it because it tells me that it worked.
I've got a problem with the moto display in my Moto X Style XT1572 with Android 6.0.1.
When I receive a message, whatsapp, email etc, the display begins to turn on and off continuously until I confirm the notification.
I haven't turned on the option to turn on teh display when I approached my hand, or double tap of launcher nova or anything like that, any help?
Thankkksss
You have to turn off wake on approach, notifications, etc. in the Moto app. They use a separate app instead of integrating those settings with Display or Sound & Notifications.
jason2678 said:
You have to turn off wake on approach, notifications, etc. in the Moto app. They use a separate app instead of integrating those settings with Display or Sound & Notifications.
Click to expand...
Click to collapse
Which app? I'm only seeing Moto but that's just the voice assistant.
Sailor Gerry said:
Which app? I'm only seeing Moto but that's just the voice assistant.
Click to expand...
Click to collapse
Not on stock anymore, so I can't check. I remember an app called Moto that had moto display, moto voice, and something else (maybe the chop/twist gestures) all controlled from it.
Sailor Gerry said:
Which app? I'm only seeing Moto but that's just the voice assistant.
Click to expand...
Click to collapse
Open Moto app then tap on stars in the upper right corner of the screen
Pinguin61 said:
Open Moto app then tap on stars in the upper right corner of the screen
Click to expand...
Click to collapse
Cracking, thank you!
I'm creating this thread to collect bugs found in the Oreo software that devs can take a look at for their ROMs, and possibly report to HTC depending on importance.
My first bug is cosmetic. The app icons are not consistent at all, and this goes further than the home screen launcher. If you hit the share button, the size of the icons vary, some big and some small.
My second bug is a little more annoying, and I'm not sure how to replicate. I was using Google Maps in and out of PiP mode (I drive Uber, so I come in and out of Maps constantly), and after some extensive switching, the PiP app wouldn't maximize, and my Recent Apps panel would not activate. The actual recents button could still activate multi-window, but it wouldn't cycle through the last two apps or activate the Recents carousel. The behavior returned to normal after a reboot. I am currently stock rooted, but I'm quite certain that has nothing to do with this issue. I will report if this happens again, and pay more attention to any possible causes. I might report this one to HTC.
My third bug is cosmetic, but a little on the annoying side. When switching Bluetooth audio profiles (found in dev options, for those who don't know), the codec that is displayed doesn't change, but you still hear the difference in audio. Also, aptx HD doesn't work for me. When selected, I hear no difference in the sound.
Ok....so my nav buttons are not working, but my home button is still working....am In the only one who is experiencing this? It is very sporadic, and fixes with a reboot.
AarSyl said:
Ok....so my nav buttons are not working, but my home button is still working....am In the only one who is experiencing this? It is very sporadic, and fixes with a reboot.
Click to expand...
Click to collapse
You're not the only one. My Nav buttons stopped responding 3 times in last 2 days. Had to restart.
Has anyone tried PIP ?
Its not working for me on youtube, whatsapp , chrome ..
U11 | ⓣⓐⓟⓐⓣⓐⓛⓚ | TabS
amit_sen said:
Has anyone tried PIP ?
Its not working for me on youtube, whatsapp , chrome ..
U11 | ⓣⓐⓟⓐⓣⓐⓛⓚ | TabS
Click to expand...
Click to collapse
YouTube requires a YouTube Red subscription.
amit_sen said:
Has anyone tried PIP ?
Its not working for me on youtube, whatsapp , chrome ..
U11 | ⓣⓐⓟⓐⓣⓐⓛⓚ | TabS
Click to expand...
Click to collapse
PIP is not convenient to use now. For example, you can open youtube.com in chrome, request desktop site, play some video in fullscreen, press home button, then you get your PIP feature.
After update my battery reduction too much..
Maybe not exactly bugs, but a few things that bother me are how ugly the icons are and that it's using the default notification sound when I'm on low battery and it plays the notification sound coming in and out of night mode as well. I don't need to be notified with a sound about coming in and out of night mode and I'd prefer the regular buzz buzz sound of the low battery rather than thinking I got a message of something.
I hate the persistent notifications of things running in the background or drawing over... Not a bug, but a 'feature'.
AarSyl said:
Ok....so my nav buttons are not working, but my home button is still working....am In the only one who is experiencing this? It is very sporadic, and fixes with a reboot.
Click to expand...
Click to collapse
It might seem a weird thing to do but try clearing cache and data from Google play services, playstore etc. I remember when I turned off all permissions to playservices my buttons stopped working as well except home button. Worth a try.
miffymiffy said:
I hate the persistent notifications of things running in the background or drawing over... Not a bug, but a 'feature'.
Click to expand...
Click to collapse
here the second solution works for me in my htc u11 whit oreo
https://www.thecustomdroid.com/hide-persistent-notifications-on-android-oreo/
Turn on Wi-Fi automatically
Turn on Wi-Fi automatically function is missing in wifi preferences, according to oreo new function it as to be there
The settings area on top has got to be the stupidest thing they have done. "Suggestions". Who the hell cares about it. Mine will not go away. Keeps saying connect usonic ear phones. I deleted all of touch pal junk as well.
caxio said:
here the second solution works for me in my htc u11 whit oreo
https://www.thecustomdroid.com/hide-persistent-notifications-on-android-oreo/
Click to expand...
Click to collapse
Third option worked great for me. Thanks
Probably more a feature than a bug, but I miss being able to pull down the notification shade and toggling between Do Not Disturb, Priority Mode, and Normal. Now tapping the icon just turns on Priority Mode. I can't seem to find an easy way to turn on Do Not Disturb without long-pressing the icon. Does anyone else know a better way?
xanadu1979 said:
Probably more a feature than a bug, but I miss being able to pull down the notification shade and toggling between Do Not Disturb, Priority Mode, and Normal. Now tapping the icon just turns on Priority Mode. I can't seem to find an easy way to turn on Do Not Disturb without long-pressing the icon. Does anyone else know a better way?
Click to expand...
Click to collapse
Because I have a smartwatch, I'm constantly in DND mode that I activate during phone's initial setup with Vol. Down...
GSE20 said:
Maybe not exactly bugs, but a few things that bother me are how ugly the icons are and that it's using the default notification sound when I'm on low battery and it plays the notification sound coming in and out of night mode as well. I don't need to be notified with a sound about coming in and out of night mode and I'd prefer the regular buzz buzz sound of the low battery rather than thinking I got a message of something.
Click to expand...
Click to collapse
You can turn off the night mode notification. I set it to still show the icon in the top bar but not make a sound. It took a while to find, and I forget where it is. Maybe the notification settings for the system app.
When the screen is off and you double click the power button to access camera, it will not pop up with a preference choice (assuming you have more than one camera installed) unless you time it exactly with putting your fingerprint on the scanner
My shortcut options when you long press an icon are completely gone on every launcher.
Edit: Suddenly works. Odd.
My phone's bluetooth connects with my car's. Tried to play spotify But the audio plays on my phone still. My car sees th title of the song, just for display....Wasn't like this before the update... Must be the bluetooth 5.0 thing?