Aloha,
Is there a command that disables power (and re-enables) to screen such as the proximity sensor while on call?
I am looking for the command to run from terminal as I want to make a script that works with Tasker. As such, I'm not looking for an app that does this for me so please don't link me to an app. In case you ask why it's because the apps I have found are yet another background service that I don't need/want when I know it's highly probable to accomplish the same Tasker and a simple script. And if they aren't a service, it locks the screen instead of just disabling power.
Anywho. anybody? ideas?
Thanks!
Related
I'm trying to lock out Phone/Voice calling from an HTC Hero.
I still need the device to use Data / GPS, but I need to make it impossible for the user to make or receive phone calls.
I know I can have sprint block voice calling on their end, but I'd rather modify Android so there is some kind of Alert or alternate functionality when phone button is pressed. . . or when the user try's to access the dial pad or anything related. . .
Is this possible?
Any suggestions or help would be appreciated.
I don't know if existing ROMs have some sort of User Rights Managements on them. I do know you can change the button behavior in the keypad file. But the other question is a neat idea.
I think on the stock ROM there was a way to disable the phone while there was an active data connection, i.e. downloading a file, no phone calls - it sent them to voicemail. I think it was called DDTM or something in the phone settings. Of course that doesn't turn the phone off entirely.... Also, you can remap the function of the key either by altering the keypad files manually or using the app called button remapper. The only other thing I can think of is try deleting the dialer app, but make sure you nandroid in case that's somehow connected to data. Good luck.
If I were to pair a Galaxy Gear with a M8, could I initiate a google search on my phone by pressing something on the watch? Basically I want to somewhat recreate the Moto x's ability to receive commands without the phone being on, and without an active tethering connection which will kill the battery on both devices.
Thanks so much!
my gear is setup to use google voice search/goggles/translate so i can voice command it, ask it to translate etc. caveat is i have to be BT tethered the whole time (battery life impact - i can get 18 hours on moderate use). I have the google now launcher installed and toggle between that and Nova depending on mood
works really good - when i take a photo with my gear, goggles automatically tries to identify it, i can tell my watch to launch apps and ask queries like you normally would with google voice
current limitation i have is i cannot use the hot phrase 'ok google' to initiate voice. i have to press the search i con to get started - still on the hunt on how to activate with 'ok google'
thevaristy said:
If I were to pair a Galaxy Gear with a M8, could I initiate a google search on my phone by pressing something on the watch? Basically I want to somewhat recreate the Moto x's ability to receive commands without the phone being on, and without an active tethering connection which will kill the battery on both devices.
Thanks so much!
Click to expand...
Click to collapse
animatechnica said:
current limitation i have is i cannot use the hot phrase 'ok google' to initiate voice. i have to press the search i con to get started - still on the hunt on how to activate with 'ok google'
Click to expand...
Click to collapse
Humm, "ok google" should work if Google Now has been triggered and running. Usually, you can do a followup search with "ok google".
Keeping the microphone running would be a MAJOR battery killer. Dont believe me, try it on your phone and see how quick it drains. On the Gear, tethered, you would probably get about 4 or 5 hours.
Just not quite there yet with battery technology, but hey who knows, maybe Google's Android Wear has cracked this nut and figured out a better way to initiate speech recognition.
ronfurro said:
Humm, "ok google" should work if Google Now has been triggered and running. Usually, you can do a followup search with "ok google".
Keeping the microphone running would be a MAJOR battery killer. Dont believe me, try it on your phone and see how quick it drains. On the Gear, tethered, you would probably get about 4 or 5 hours.
Just not quite there yet with battery technology, but hey who knows, maybe Google's Android Wear has cracked this nut and figured out a better way to initiate speech recognition.
Click to expand...
Click to collapse
Agreed. On the phone there is typically a setting to set the hot phrase for google now, this setting does not show up in the gear
Sent from my KFAPWI using Tapatalk
I'm using offline recognition on my gear in conjunction with Tasker and AutoVoice. I have it launch background continuous recognition whenever the screen is on, then so it when the screen turns off. I also have two orientations that turn the screen of right away without waiting for the timeout. (the positions when I naturally rest my arm on a desk and when my hand hangs at my side.) So far, this hasn't had much effect on battery life.
I use a key word of "Galaxy" to let it know I want to forward a commend to my phone, which I do with M2D Manager. I've already got quite a set of voice controls on the phone, so no need to replicate them on the watch. Otherwise, it handles the command on the watch.
The net effect here, is I lift my arm in standard watch fashion, and say commands directly. It's functionality similar to having always on recognition.
Sent from my XT1060 using XDA Premium 4 mobile app
hawkjm73 said:
I'm using offline recognition on my gear in conjunction with Tasker and AutoVoice. I have it launch background continuous recognition whenever the screen is on, then so it when the screen turns off. I also have two orientations that turn the screen of right away without waiting for the timeout. (the positions when I naturally rest my arm on a desk and when my hand hangs at my side.) So far, this hasn't had much effect on battery life.
I use a key word of "Galaxy" to let it know I want to forward a commend to my phone, which I do with M2D Manager. I've already got quite a set of voice controls on the phone, so no need to replicate them on the watch. Otherwise, it handles the command on the watch.
The net effect here, is I lift my arm in standard watch fashion, and say commands directly. It's functionality similar to having always on recognition.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
@hawkjm73 Could you elaborate on how you have this setup exactly? This may be my answer to ditch trying to get this damn "Google Now Search" to work offline in handling voice commands such as call, ect... :fingers-crossed:
hawkjm73 said:
I'm using offline recognition on my gear in conjunction with Tasker and AutoVoice. I have it launch background continuous recognition whenever the screen is on, then so it when the screen turns off. I also have two orientations that turn the screen of right away without waiting for the timeout. (the positions when I naturally rest my arm on a desk and when my hand hangs at my side.) So far, this hasn't had much effect on battery life.
I use a key word of "Galaxy" to let it know I want to forward a commend to my phone, which I do with M2D Manager. I've already got quite a set of voice controls on the phone, so no need to replicate them on the watch. Otherwise, it handles the command on the watch.
The net effect here, is I lift my arm in standard watch fashion, and say commands directly. It's functionality similar to having always on recognition.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
THIS! This is exactly what I am looking for. Screen on, send voice commands to the phone. How is this done?
thevaristy said:
THIS! This is exactly what I am looking for. Screen on, send voice commands to the phone. How is this done?
Click to expand...
Click to collapse
With a combination of Google Now Launcher and Offline voice recognition enabled...
https://www.youtube.com/watch?v=MY9OT1retpU&feature=youtu.be
Apologies for the delay in answering.
There are quite a few components working together here.
First and foremost: Null Rom. Without that, nothing else happens.
Second: offline voice recognition
This was pretty much taking all the language files from my phone and transplanting them to the watch, minding permissions.
Third: AutoVoice and Tasker
These are market apps and are fantastic for automation. You'll need them on both phone and watch. I'm using two profiles for this. The first turns on AutoVoice recognition in continuous mode whenever the screen turns on, and off when the screen goes off. The second profile is an AutoVoice recognize with "galaxy" as the command filter. It initiates an intent with the rest of what I say as a data payload.
Fourth: M2D manager
This is also available on the market, and needs to be on both devices. It is a Bluetooth bridge for Android intents. Tasker sends out an intent formed for M2D with the voice command as data. M2D transmitted it to the phone where it seems out a specified intent, still containing the command. Tasker listens for that intent. Once it had it, I use the AutoVoice test feature to send the command text in as if it had been spoken to the phone, so I can use all of my previously written voice control profiles. M2D also works the other way around, which I take advantage of for notifications and such.
Sent from my XT1060 using XDA Premium 4 mobile app
hawkjm73 said:
Apologies for the delay in answering.
There are quite a few components working together here.
First and foremost: Null Rom. Without that, nothing else happens.
Second: offline voice recognition
This was pretty much taking all the language files from my phone and transplanting them to the watch, minding permissions.
Third: AutoVoice and Tasker
These are market apps and are fantastic for automation. You'll need them on both phone and watch. I'm using two profiles for this. The first turns on AutoVoice recognition in continuous mode whenever the screen turns on, and off when the screen goes off. The second profile is an AutoVoice recognize with "galaxy" as the command filter. It initiates an intent with the rest of what I say as a data payload.
Fourth: M2D manager
This is also available on the market, and needs to be on both devices. It is a Bluetooth bridge for Android intents. Tasker sends out an intent formed for M2D with the voice command as data. M2D transmitted it to the phone where it seems out a specified intent, still containing the command. Tasker listens for that intent. Once it had it, I use the AutoVoice test feature to send the command text in as if it had been spoken to the phone, so I can use all of my previously written voice control profiles. M2D also works the other way around, which I take advantage of for notifications and such.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks! I can follow most of what you said, however, when it comes to tasker, I'm a bit challenged. Right now I do have Tasker on both watch & phone along with Taskgear. With the help of some others, I have a couple profiles set on each (visa-versa) to show the battery levels respectively per other device on a widget on each.
If you could kindly share your tasker setups, I think I could pull this off! :fingers-crossed:
https://www.dropbox.com/s/44wq0tzw4apn6tp/Screenshots_2014-12-22-16-19-43.png?dl=0
There is no call happening during that screenshot, but you can see it still persists.
It still works for a new call, but it is annoying. If you have a clue what the name of that process / app / whatever is, that will help new greatly toward troubleshooting.
Thanks in advance.
I discovered if I kill the process "Phone" from application manager, it will close the notification panel phone widget.
I attempted to use tasker to automatically close it when idle (both as root and not), but that didn't work.
Anyone know of an xposed module that has an impact on Phone?
I found it. The process name is com.android.phone. In a tasker run shell command I added:
Code:
am force-stop com.android.phone
which killed the phone once I hung it up. Root is required. Thanks for letting me troubleshoot here!
Hello people,
I don't know if anyone else is experience this but I thought I mention it. Also I apologise if this is the incorrect place to start this thread, but I have looked on xda for a tasker dedicated section for troubleshooting.
Now I have a automated WIFI profile that basically enables whenever I load a specific app. But for some strange reason it does not always execute, when a specific app does load and other times it does?
Does anyone else notice this strange behaviour going on with tasker?
If so is it a bug that needs reporting or is there something wrong with my profile?
Thanks in advance!
In Tasker settings/preferences/monitor put to "Always" the Use Reliable Alarms option.
GrippingSphere said:
In Tasker settings/preferences/monitor put to "Always" the Use Reliable Alarms option.
Click to expand...
Click to collapse
It seems the profile triggers, but not the task.
HatchetEgg said:
It seems the profile triggers, but not the task.
Click to expand...
Click to collapse
You can test the Task by manually executing it. Maybe you're using a plug-in that requires permissions to run.
GrippingSphere said:
You can test the Task by manually executing it. Maybe you're using a plug-in that requires permissions to run.
Click to expand...
Click to collapse
If I run the task manually everything executes just fine.
The task does use one plugin and thats for secure settings, but thats about it.
UPDATE: I think I might know what the problem is, and I think that tasker is unable to wake the device to execute the task, so I added a wake device action in my task and see if this works.
In LL and MM there is battery optimization where Tasker and Secure Settings should be excluded. Other 3rd party battery saving apps might also affect the operation of Tasker and its plugins.
GrippingSphere said:
In LL and MM there is battery optimization where Tasker and Secure Settings should be excluded. Other 3rd party battery saving apps might also affect the operation of Tasker and its plugins.
Click to expand...
Click to collapse
This is true I had taken the advice from here >
As far as I am aware tasker and it's plugins are whitelisted from other 3rd party on my device, so I still don't understand why it still does not work unless I add the wake device action from secure settings.
Any luck on this? I'm noticing that tasker is very slow to execute any actions outside of the app. Meaning, if I create a task that simply has one step..."beep". Next, add that task as a shortcut to my nova launcher desktop. Click the shortcut...it takes almost 30seconds for it to execute the beep. I've been a tasker user for years. Not sure why this lag is occurring.
Tried this...
Tasker is not battery optimized.
Reinstalled Tasker.
rooted Pixel, 7.1.1
I have the same problem with my periodical Wi-Fi check.I have to add the 1 second CPU wake, but it's still not very reliable.maybe the best way to get over this is turning on the screen, but this is kind of defeat the purpose for me so....
any other suggestion?
soundneedle said:
Any luck on this? I'm noticing that tasker is very slow to execute any actions outside of the app. Meaning, if I create a task that simply has one step..."beep". Next, add that task as a shortcut to my nova launcher desktop. Click the shortcut...it takes almost 30seconds for it to execute the beep. I've been a tasker user for years. Not sure why this lag is occurring.
Tried this...
Tasker is not battery optimized.
Reinstalled Tasker.
rooted Pixel, 7.1.1
Click to expand...
Click to collapse
There is one thing that you can try go to Tasker > preferences > misc and untick reduce resource usage.
alienyd said:
I have the same problem with my periodical Wi-Fi check.I have to add the 1 second CPU wake, but it's still not very reliable.maybe the best way to get over this is turning on the screen, but this is kind of defeat the purpose for me so....
any other suggestion?
Click to expand...
Click to collapse
I have tried the screen wake function, but even then it doesn't work.
I did notice however that Google connectivity was causing issues for me, such as not able to connect to my ap automatically.
Hi team,
I use one app (True Mouse/KB) which turn an Android device into a generic Blutooth mouse/kb combo, and I'd like to add some features on top of it with tasker (nothing really complicated, have some "tap" inputs sent based on long press on volume or headset buttons).
My problem is that any task I create execute fine everywhere except in that app. Is there anything I can do, or it's just that this particular app has something blocking tasker ?
Thanks in advance,
Rgds