Related
Hi Android experts,
is there any possibility/app/hack/mod/etc to end a phone call with a "hardware" button?
I couldn´t find anything here in the forum or at the market.
Thanks in advance!
Polle
polle55 said:
Hi Android experts,
is there any possibility/app/hack/mod/etc to end a phone call with a "hardware" button?
I couldn´t find anything here in the forum or at the market.
Thanks in advance!
Polle
Click to expand...
Click to collapse
No one an idea?
On the Droid X, you can do this in the settings, but only so much as to make the power/lock button end your call.
Settings > Accessibility Settings > (last option, "Power button ends call")
Edit: Wow, this was my first post on the forums. I am such a despicable lurker.
On the samsung captivate running perception 9 also has the option to end call with the power button. It works good but I turned it off since if you on a long phone call you can end the call but now the screen was locked so I could not go back to unlock the screen to check something ( like directions or such while still on the call.
Sent from MY Perception 9 Rockin and OverClockin on XDA App
Maybe I got something for you:
http://forum.xda-developers.com/showthread.php?t=880844
probably only works on Nexus One.
EDIT// Oh and if you are using Cyanogenmod (I have 6.1.0, I think 6.0 had't implemented that feature!) you can go to
Settings -> Accessibility (fourth last option) -> last option (dont know it in english, my phone is in german
if you activate it, it will end the phone call - however it will not answer it!
Does anyone know of anyway to disable bluetooth voice dial? I never use it and I want to use a app that will map my bt buttons to my music player "headset button controller" but bt voice dial always comes up. I have searched around the web and found tons asking but seen nothing on XDA the only thing close I can find is this thread http://forum.xda-developers.com/showthread.php?t=827472 but it really has on tips on how to do it just that you need root any help would be appreciated. Riding season is almost here and I want to control my tunes
quik99 said:
Does anyone know of anyway to disable bluetooth voice dial? I never use it and I want to use a app that will map my bt buttons to my music player "headset button controller" but bt voice dial always comes up. I have searched around the web and found tons asking but seen nothing on XDA the only thing close I can find is this thread http://forum.xda-developers.com/showthread.php?t=827472 but it really has on tips on how to do it just that you need root any help would be appreciated. Riding season is almost here and I want to control my tunes
Click to expand...
Click to collapse
If you don't use voice dial at all you can remove the voice dial app with sdx app removal tool but you will have to root to use it. If you search for one click root and unroot it should pop up. I can get you links this evening if you need them.
Do you BONSAI?
As a matter of fact there is a video on rooting with 2.5.5 in the stickies at the beginning of General Thread.
Do you BONSAI?
I'm rooted and on a custom rom thats not the issue I just didnt know how to get it turned off. I have played with the sdx remover will give it a shot Thanks
Well that didnt work. with voice dial removed now when I'm in the music player and hit the button my phone freaks out it doesnt FC but it hangs up eventually goes to the lock screen I can wake it up but the screen does not respond. Also tried holding power before it locked and got reboot etc screen but the touch screen does not work. oh well maybe I wont be getting this function lol
quik99 said:
Well that didnt work. with voice dial removed now when I'm in the music player and hit the button my phone freaks out it doesnt FC but it hangs up eventually goes to the lock screen I can wake it up but the screen does not respond. Also tried holding power before it locked and got reboot etc screen but the touch screen does not work. oh well maybe I wont be getting this function lol
Click to expand...
Click to collapse
Sorry. Did you restore voice dial with sdx? You could go back to Eclair where there was no bluetooth voice dial
We need better bluetooth controls. I used Top Voice Control and picked that to open when I hit the Bluetooth button and it screwed up so wanted the basic voice dilaer back and had to delete Top Voice to do that.
kennyglass123 said:
Sorry. Did you restore voice dial with sdx? You could go back to Eclair where there was no bluetooth voice dial
We need better bluetooth controls. I used Top Voice Control and picked that to open when I hit the Bluetooth button and it screwed up so wanted the basic voice dilaer back and had to delete Top Voice to do that.
Click to expand...
Click to collapse
Ya i was able to restore and its working fine now. I think I will tough it out lol
Can't stand that annoying Voice Command app that pops up whenever you accidently double-tap the home button? Well, apparently it can be removed if you have ICS, though not the typical way.
Thanks goes out to Marrr over at AF for pointing this out.
Step 1: Install Go Launcher
Step 2: Long-press voice command in the app drawer, and when the red "x" comes up, hit it. Follow the prompt and the app will be completely uninstalled.
Step 3: Uninstall Go Launcher if you want (and delete the Go Launcher/Store folders it created in your USB storage).
It really is THAT simple!
Or just don't double tap the Home button
In a year of owning a Galaxy SII I can't say I've every double tapped the Home button by mistake
PFC Hudson said:
Or just don't double tap the Home button
In a year of owning a Galaxy SII I can't say I've every double tapped the Home button by mistake
Click to expand...
Click to collapse
It's weird, but lately, occasionally when I hit the home button the app would just launch. It's like the device was registering a double-tap. Not sure if it was me, or a hardware issue. Either way, it was annoying and I've seen a few others complain about the same issue.
If you're not affected, then you're set. But if you are, this seems to work wonders.
PFC Hudson said:
Or just don't double tap the Home button
In a year of owning a Galaxy SII I can't say I've every double tapped the Home button by mistake
Click to expand...
Click to collapse
I agree, I never experienced the issue and laugh when I see people complain.
I know multiple people with the S2 and none of them experience.
I admit, maybe it may be hardware; but I would think if it was hardware it would be on a larger scale. I personally think people don't realise they double tapped it.
T__ said:
laugh when I see people complain.
Click to expand...
Click to collapse
And I laugh when I see someone who assumes that because their phone works perfectly, everyone else must have a perfect phone too.
Does this remove the double tap delay though? Always drove me mad about gs2, and I've always got rid of it as soon as I can
Sent from my GT-I9100 using xda premium
jaykresge said:
Can't stand that annoying Voice Command app that pops up whenever you accidently double-tap the home button? Well, apparently it can be removed if you have ICS, though not the typical way.
Thanks goes out to Marrr over at AF for pointing this out.
Step 1: Install Go Launcher
Step 2: Long-press voice command in the app drawer, and when the red "x" comes up, hit it. Follow the prompt and the app will be completely uninstalled.
Step 3: Uninstall Go Launcher if you want (and delete the Go Launcher/Store folders it created in your USB storage).
It really is THAT simple!
Click to expand...
Click to collapse
I agree....it is annoying. It comes up all the time when I don't want to. Anyone know the name that is appears in Titanium Backup so I can remove it?
Voice command. Just filter for "vlingo"
i have a hardware problem, when i press home button, like 30% of time the voice command will appear, but i dont want to uninstall the app, there is any other way for disabling it?
jaykresge said:
Can't stand that annoying Voice Command app that pops up whenever you accidently double-tap the home button? Well, apparently it can be removed if you have ICS, though not the typical way.
Thanks goes out to Marrr over at AF for pointing this out.
Step 1: Install Go Launcher
Step 2: Long-press voice command in the app drawer, and when the red "x" comes up, hit it. Follow the prompt and the app will be completely uninstalled.
Step 3: Uninstall Go Launcher if you want (and delete the Go Launcher/Store folders it created in your USB storage).
It really is THAT simple!
Click to expand...
Click to collapse
Boys install system app remover, no need for root, and uninst apps u don't need. Quicker, safer, legal ,
i had the same issue (about 30% of erroneous voice command starts). i had frozen
the app with Titanium Backup and since then had about 30% of keypress failures.
Is there a program that shows if there was a keypress or not?
Thanks for a nice tip, that voice is useless in Russia anyway.
BTW, I also can unistall readers hub in that way, why it allows me to unistall it, but I cant unistall music hub, they're seems to be both system apps.
ES File Explorer can also uninstall it.
Select the App Manager then long press on the app you want to remove, eg Voice Commamd, choose uninstall, and its gone.
Help
I've tried go launcher and it doesnt have a red x by it when i press and hold.... i tried apex launcher and the same thing. Anyone else have this problem.... please help. i'm using the SGH-i777 with stock ICS
is this the solution
utahst8 said:
I've tried go launcher and it doesnt have a red x by it when i press and hold.... i tried apex launcher and the same thing. Anyone else have this problem.... please help. i'm using the SGH-i777 with stock ICS
Click to expand...
Click to collapse
I don't have the problem because I fixed it.
Search for root app uninstaller, install it, and find voice talk, or viingo as it is called, and uninstall the app, so uninstall root app installer so you can't launch it by a mistake and double tap and see what's happening, now nothing happens when I double tap home button, so it's fixed.
I hope I can help other people.
Its the most frustrating app ever even more frustrating than Touchwiz. Its like whenever I press the home button around 80% of chances are that it would pop up with that annoying voice,"What would you like to do ?"
And I'm like GTFO off my device. Finally removed it using Root Explorer forever after...
Sent From My Pencil
Finally, after 2 years ...
jaykresge said:
Can't stand that annoying Voice Command app that pops up whenever you accidently double-tap the home button? Well, apparently it can be removed if you have ICS, though not the typical way.
Thanks goes out to Marrr over at AF for pointing this out.
Step 1: Install Go Launcher
Step 2: Long-press voice command in the app drawer, and when the red "x" comes up, hit it. Follow the prompt and the app will be completely uninstalled.
Step 3: Uninstall Go Launcher if you want (and delete the Go Launcher/Store folders it created in your USB storage).
It really is THAT simple!
Click to expand...
Click to collapse
Thank you very much. Just to say so I went through that buttcracking process of making like my millionth forum account, but that one was worth it. Thx a bunch, I really have a device where pressing home leads you to the voice crap in 99,456%. Now its finally fallen off board. Thx again.
removing voice command easier
you don't have to change a theme or anything like that. you should download "Smart App Protector Free" and and in the apps section inside the app scroll down until you get to "voice command". click on it and choose uninstall. that easy
You can also use system app uninstaller from the market, just go into regular apps and remove voice command.
tiggerlator said:
You can also use system app uninstaller from the market, just go into regular apps and remove voice command.
Click to expand...
Click to collapse
This is an outdated thread. You can now disable the app.
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