[Q] Allow buetooth bypass questions - Motorola Droid 3

Hello, I am trying to implement a shortcut to launch an app when a bluetooth control button is pressed, and would appreciate some help.
Running:
XT860 (Droid 3 GSM version)
Maverick 4.0
Safestrap 3.0
Situation:
I have a car stereo system that has media controls but not a dedicated bluetooth phone button.
My proposed solution:
Modify AVRCP.kl to remap the back key to the voice command
Edit vSuite.apk to include search_long_press as an intent-filter
Sign the apk and re-install
This all works well, but I have run into the problem of how to bypass the lock screen. Now when I press the back key, the phone will wake, and stop at the lock screen. If I unlock, then the voice command app will launch.
There is the "Allow bluetooth bypass" option under security, but I guess AVRCP commands are separate from that (AVRCP works regardless of if the option is enabled or not)
I came across an app in the play store called "Bluetooth Voice Dial Widget" that does what I want, but it disables all other AVRCP commands. For example, if I assign the voice command button to the previous media key, play and next both stop working.
Looking at the logcat, it seems that bluetooth commands are handled differently than AVRCP commands.
So, my question is: Is there a way to bypass the lockscreen? Or do I need to edit the apk for MediaButtonIntentReceiver?
Haha, I am new to android. So, please point out anything I have said wrong.
Thank you.

Related

[Q] Bluetooth call button

Okay, I bought a bluetooth headset and when pressing the call button it does nothing.
I am actually trying to write an app using the Gmate (enables bluetooth GSM phone calls) to make calls.
For this I would like my app to start upon pressing the call button.
I have tried the following:
-Use remapping apps (does nothing)
-Enable voice in framework (not possible in android 4.3)
-Using mediabutton intent (does not enable call button)
-Reading the android source. Only found that telephone uses something like IBluetoothPhoneHeadset.Stub. I tried to include this but that wasn't possible.
The only three options I can still think of are:
-cross-compiling a bluetooth library and using this to read bluetooth input.
-Create custom intents in android source and then either recompiling android rom or update.zip.
-Edit android telephony source.
Since all these options take a lot of time and the new android version will be released soon I decided to post this question.
Perhaps somebody knows a quick fix?
My bluetooth headset: Jabra street 2
Thanks for reading and I really hope someone can help me.

[Q} Send/simulate bluetooth headset button click from Gear to phone?

Is it possible to send/simulate a bluetooth headset button click from the Gear to the attached phone?
My goal is to have that click activate Google Voice Search on the phone, but all the options I've tried don't work well enough.
1) Sending bluetooth commands through rooted terminal like: echo -e "AT\r" > /dev/ttySAC0
sending any command to ttySAC0 would crash the bluetooth connection. I guess this is a serial interface and isn't designed to accept text commands (I don't have a full understanding of this, just conjecture). Other devices like 'uhid' and 'uinput' didn't work either (everything just returns 1, and I don't know what that means either), I tried all the ones that showed up under 'ls -l /dev/' with 'bluetooth' in their properties.
2) Using tasker+autoremote: works when bluetooth tethering is on but is slow (command going through internet and back), and works when bluetooth direct receiving is enabled on the phone, but this drains battery a lot (Autoremote always awake listening on bluetooth). Neither one of these is a palatable side effect (slow, or battery drain).
3) Using tasker to intercept a command from the Gear media controller app
Works sometimes, I usually use the 'previous' button, but the need to 'Grab' the media button interferes with using it for music playback, and using another tasker task to enable/disable this profile leads to erratic behavior (sometimes the media player, Winamp in this case, will start working immediately, sometimes not). The bigger issue is that the media controller app stops responding after an hour or two, requiring rebooting the phone, or killing some of the Samsung Accessory services running in the background, which then relaunch themselves. I think there's too much interaction here with Tasker, Winamp, and the Samsung Accessory stuff to know what's happening though. The delay is also highly variable, which is annoying, and sometimes when the Voice Search launches I do not get the initial 'ding' audio through the Gear, though there could be a ton of reasons for that as well.
Long story short, I'm hoping being able to simulate bluetooth headset button presses/commands would solve all of the above problems, getting faster response, no/minimal extra power consumption, and be very reliable. Also, this may sound dumb, but I don't actually have a normal bluetooth headset to test with either.
Thanks to everyone that's on xda-developers, this is my first post ever, but I've been coming to this site for stuff for years.
We haven't found anything yet
(There are a few older threads around)
Oops. Should have guessed that. Thank's for the quick reply.
Brendo said:
We haven't found anything yet
(There are a few older threads around)
Click to expand...
Click to collapse
ulnah said:
Oops. Should have guessed that. Thank's for the quick reply.
Click to expand...
Click to collapse
A possible work around would be to activate Google Now on your phone, then goto gear manager and have it send notifications from Google search. Once you get some notifications from Google search, you can click the "show on device" button and it should open, and you can say "OK Google" to start start it up. (make sure you turn that feature on in the Google search settings )
My solution, for anyone interested...
I use AutoVoice rather than Google Now, although any command not matched by AV I have sent to Google Now for processing.
Anyway, there doesn't appear to be any faster way of communicating than via whatever it is that the Gear and my Note II communicate over by default. Not having the know-how to tap into this, I figured I would just use an existing method of communicating and use Tasker to intercept and pretend that was a BT button press instead.
So what I've done is just set it up so that when I use the dialer to run a USSD code that doesn't mean anything on my phone, this triggers what would ordinarily happen on a BT button press on autovoice - that is:
When variable %WIN matches "USSD code running" -> Perform task with actions: "Input - back" and then Plugin - State - Autovoice - Recognise... or whatever it is you want.
So that last action could be replaced by launching Voice Search if you want Google Now to take control.
I've probably not explained that well at all, will post a proper how to if anyone's interested.
mattytj said:
I use AutoVoice rather than Google Now, although any command not matched by AV I have sent to Google Now for processing.
Anyway, there doesn't appear to be any faster way of communicating than via whatever it is that the Gear and my Note II communicate over by default. Not having the know-how to tap into this, I figured I would just use an existing method of communicating and use Tasker to intercept and pretend that was a BT button press instead.
So what I've done is just set it up so that when I use the dialer to run a USSD code that doesn't mean anything on my phone, this triggers what would ordinarily happen on a BT button press on autovoice - that is:
When variable %WIN matches "USSD code running" -> Perform task with actions: "Input - back" and then Plugin - State - Autovoice - Recognise... or whatever it is you want.
So that last action could be replaced by launching Voice Search if you want Google Now to take control.
I've probably not explained that well at all, will post a proper how to if anyone's interested.
Click to expand...
Click to collapse
This is actually quite a clever work around, great thinking.
I can't get this to work. For example, when I use '*#111222#' and press 'dial' on my phone, it tries, then errors (this is good I think)
But when I tried to dial the same number from my Gear, I get '*#111222# not supported. Are you on null rom on your Gear?
mattytj said:
I use AutoVoice rather than Google Now, although any command not matched by AV I have sent to Google Now for processing.
Anyway, there doesn't appear to be any faster way of communicating than via whatever it is that the Gear and my Note II communicate over by default. Not having the know-how to tap into this, I figured I would just use an existing method of communicating and use Tasker to intercept and pretend that was a BT button press instead.
So what I've done is just set it up so that when I use the dialer to run a USSD code that doesn't mean anything on my phone, this triggers what would ordinarily happen on a BT button press on autovoice - that is:
When variable %WIN matches "USSD code running" -> Perform task with actions: "Input - back" and then Plugin - State - Autovoice - Recognise... or whatever it is you want.
So that last action could be replaced by launching Voice Search if you want Google Now to take control.
I've probably not explained that well at all, will post a proper how to if anyone's interested.
Click to expand...
Click to collapse
fOmey said:
This is actually quite a clever work around, great thinking.
Click to expand...
Click to collapse
Thanks mate, big fan of your work with the Gear, would have returned this thing after a day without you ROM.
ulnah said:
I can't get this to work. For example, when I use '*#111222#' and press 'dial' on my phone, it tries, then errors (this is good I think)
But when I tried to dial the same number from my Gear, I get '*#111222# not supported. Are you on null rom on your Gear?
Click to expand...
Click to collapse
Are you using the phone app on your gear or the dialer app? I am running _null.
Using the dialer means it just passes the dialer digits to the phone to process, so I simply dial "2" on the dialer and call. 2 gets picked up as a ussd code, which does nothing, but tasker intercepts and Pepper, my phone, asks me what she can do for me. I speak into my watch and she proceeds to ignore or misunderstand me.
All operating as normal.
Sent from my GT-N7105 using xda app-developers app
For some reason I thought it would have to start with '*#' to be recognized as a code, but '2' works as well.
Some quick testing shows no problems, I hope it stays that way. I had tried something similar by dialing a dummy number, having it hang up, and then start, but that took a long time and was much worse than this. Thank you!
This works excellent !
Only thing I dont like is the "unknown code" error that pops up on my phone, once I figure how to terminate that, its perfect.
fOmey said:
This works excellent !
Only thing I dont like is the "unknown code" error that pops up on my phone, once I figure how to terminate that, its perfect.
Click to expand...
Click to collapse
If it's an OCD type issue like me, trigger an overlay scene on the error message that destroys itself when the error isn't in focus, something like "Initiating...." . So mine does that, with a back action also triggered by the error. My attribute trends to lag so the error it's thrown before recognition. If after, adapt the scene to say, executing... or something. Point is, it of sight, out of mind!
mattytj said:
If it's an OCD type issue like me, trigger an overlay scene on the error message that destroys itself when the error isn't in focus, something like "Initiating...." . So mine does that, with a back action also triggered by the error. My attribute trends to lag so the error it's thrown before recognition. If after, adapt the scene to say, executing... or something. Point is, it of sight, out of mind!
Click to expand...
Click to collapse
Iv attempted to simulate a back button press with tasker, works fine if the phone is unlocked.. although if the phone is locked, im presented with a "UNKNOWN CODE" error which frustrates me
Ill have to get back to the drawing board and figure it out..
EDIT: Shortly after writing the above I came up with this, works a treat:
Code:
Task: Phone Trigger (36)
A1: AutoVoice Recognize [ Configuration:
Voice command with headset Package:com.joaomgcd.autovoice Name:AutoVoice Recognize Timeout (Seconds):0 ]
A2: Wait [ MS:0 Seconds:4 Minutes:0 Hours:0 Days:0 ]
A3: Run Shell [ Command:input keyevent 4 Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ]

[Q] Touchless control to activate Utter?

I'm running version 4.4, not rooted, Moto x. Utilizing Tasker, what is the easiest way to have the touchless control prompt "ok google now" directly initiate/bring up the Utter voice command app to it's listening state? I can accomplish this no problem with the screen on and unlocked, but I want the ability to also launch it with the screen off/inactive. I am most familiar with utter but will be fine using any voice command app if necessary. I just want to be able to utilize UItter voice command capabilities without it always being in a permanent listening state, which really drains my phone's battery life. Thanks for any suggestions!
I am also interested in this. The following thread should give you some leads:
http://forum.xda-developers.com/moto-x/general/moto-x-offline-recognition-solved-t2571466
Utter
masterfisher166 said:
I'm running version 4.4, not rooted, Moto x. Utilizing Tasker, what is the easiest way to have the touchless control prompt "ok google now" directly initiate/bring up the Utter voice command app to it's listening state? I can accomplish this no problem with the screen on and unlocked, but I want the ability to also launch it with the screen off/inactive. I am most familiar with utter but will be fine using any voice command app if necessary. I just want to be able to utilize UItter voice command capabilities without it always being in a permanent listening state, which really drains my phone's battery life. Thanks for any suggestions!
Click to expand...
Click to collapse
I use the Ok Google now trigger intent xposed module and in tasker use it to launch the utter! Shortcut available from the playstore so that way I have always listening capability without the battery drain that permanent recognition from utter brings and it works perfectly everytime, the alternative is to use touchless controls together with auto voice recognise within tasker and get the Google now api xposed module so that you're still using Google now but tasker tasks can be implemented by voice in Google now, hope that helps although you need to be rooted which I have only just reread your comment to see that you are not
Without root, your options are a bit limited. Utter! Has a direct shortcut to launch its voice recognizer? If so, you can say "OK, Google now, open (utter! shortcut name) app" Kinda awkward, but it should work.
Sent from my XT1060 using XDA Premium 4 mobile app
<br />
I use the Ok Google now trigger intent xposed module and in tasker use it to launch the utter! Shortcut available from the playstore so that way I have always listening capability without the battery drain that permanent recognition from utter brings and it works perfectly everytime, the alternative is to use touchless controls together with auto voice recognise within tasker and get the Google now api xposed module so that you're still using Google now but tasker tasks can be implemented by voice in Google now, hope that helps although you need to be rooted which I have only just reread your comment to see that you are not<br/>
Can you elaborate on this? I'm not a big Tasker user.
Sent from my XT1053 using Tapatalk
Touchless utter
overthatscreen said:
<br />
I use the Ok Google now trigger intent xposed module and in tasker use it to launch the utter! Shortcut available from the playstore so that way I have always listening capability without the battery drain that permanent recognition from utter brings and it works perfectly everytime, the alternative is to use touchless controls together with auto voice recognise within tasker and get the Google now api xposed module so that you're still using Google now but tasker tasks can be implemented by voice in Google now, hope that helps although you need to be rooted which I have only just reread your comment to see that you are not<br/>
Can you elaborate on this? I'm not a big Tasker user.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Download and install utter quick launch from the playstore and the okgooglenowtriggerintent module from xposed, once you have activated it and rebooted in xposed framework open tasker and create a new profile, hit event then in the popup start to type intent and send intent will appear, hit that and in the action section type the following:
com.hawkjm.okgooglenowtriggerintent.AUDIO_TRIGGER
Press back and new task popup will appear, choose application and select utter quick launch, make sure tasker is running and the new profile is active in tasker and keep pressing back until tasker exits, now everytime you say ok Google now utter will listen instead of Google now, you might want to customise the response from your command in utter, I changed mine simply to yes each time I activate utter and bear in mind that it has nothing to do with the wake up command settings in utter, I hope that all makes sense
If it's the tasker tasks in Google now that you are interested in then download autovoice from the playstore and the Google search api from the xposed framework application downloads section and activate it and reboot,
Open autovoice and scroll to the bottom and make sure that Google search api is enabled then open the Google search api app that you downloaded (should now be an icon) swipe across to the right and make sure autovoice is there, if not then reboot, if so open tasker, create a profile, select state, plugin, autovoice recognised then next to configuration hit the edit button, scroll to command filter and type the Phrase that you want to be recognised for example Toggle bluetooth, back out of it and hit the tick, then select the task that you want to perform (the possibilities are endless) and back out of tasker until it closes then try out your command, create new profiles for each autovoice command that you want to execute,
Google search will try and search for whatever you say even though it will execute your task, if you're fine with that then leave it as it is, if you want Google search to close after executing certain commands then under each task that you create press plus, select if and make the top line look like this:
%avsource ~ googlenow
Then hit back, hot plus and type kill application and select that option, search for google search and tick use root,
Hit back again and hit plus and type end if and select it and then hit back until tasker exits. Now whenever you say that particular command Google now will execute it and then return to where you were previously, if you don't want to do that for each task simply create a profile for recognising the Phrase homepage and have it run the task homepage
mpd81 said:
Download and install utter quick launch from the playstore and the okgooglenowtriggerintent module from xposed, once you have activated it and rebooted in xposed framework open tasker and create a new profile, hit event then in the popup start to type intent and send intent will appear, hit that and in the action section type the following:
com.hawkjm.okgooglenowtriggerintent.AUDIO_TRIGGER
Press back and new task popup will appear, choose application and select utter quick launch, make sure tasker is running and the new profile is active in tasker and keep pressing back until tasker exits, now everytime you say ok Google now utter will listen instead of Google now, you might want to customise the response from your command in utter, I changed mine simply to yes each time I activate utter and bear in mind that it has nothing to do with the wake up command settings in utter, I hope that all makes sense
If it's the tasker tasks in Google now that you are interested in then download autovoice from the playstore and the Google search api from the xposed framework application downloads section and activate it and reboot,
Open autovoice and scroll to the bottom and make sure that Google search api is enabled then open the Google search api app that you downloaded (should now be an icon) swipe across to the right and make sure autovoice is there, if not then reboot, if so open tasker, create a profile, select state, plugin, autovoice recognised then next to configuration hit the edit button, scroll to command filter and type the Phrase that you want to be recognised for example Toggle bluetooth, back out of it and hit the tick, then select the task that you want to perform (the possibilities are endless) and back out of tasker until it closes then try out your command, create new profiles for each autovoice command that you want to execute,
Google search will try and search for whatever you say even though it will execute your task, if you're fine with that then leave it as it is, if you want Google search to close after executing certain commands then under each task that you create press plus, select if and make the top line look like this:
%avsource ~ googlenow
Then hit back, hot plus and type kill application and select that option, search for google search and tick use root,
Hit back again and hit plus and type end if and select it and then hit back until tasker exits. Now whenever you say that particular command Google now will execute it and then return to where you were previously, if you don't want to do that for each task simply create a profile for recognising the Phrase homepage and have it run the task homepage
Click to expand...
Click to collapse
Great topic! Learning more about integrating Google Now and AutoVoice, but i have some doubts yet
I have a MotoX and do not want to leave the continuous mode autovoice on because MotoX has dedicated processor for voice recognition, intend
use "OK Google Now" to enable the continuous mode autovoice.
Could be accomplished?
"OK NOW GOOGLE", "MOTO X" "TURN ON TV"
^MotoX feature
^Enable AutoVoice
^Action
dont like Utter!...
Easily acomplished
klucilla said:
Great topic! Learning more about integrating Google Now and AutoVoice, but i have some doubts yet
I have a MotoX and do not want to leave the continuous mode autovoice on because MotoX has dedicated processor for voice recognition, intend
use "OK Google Now" to enable the continuous mode autovoice.
Could be accomplished?
"OK NOW GOOGLE", "MOTO X" "TURN ON TV"
^MotoX feature
^Enable AutoVoice
^Action
dont like Utter!...
Click to expand...
Click to collapse
You can accomplish it a couple of ways, if you use the okgooglenowintent xposed module as described above and instead of choosing utter quick launch you choose autovoice recognise as your task and give your commands that way (using this xposed module doesn't use autovoice permanent recognition, it uses the same as the touchless control does its just intercepting and switching touchless control for whatever app you replace it with so it doesn't drain any battery)
Or you can get the Google search api xposed module and set it up like I have above so that all of your tasker tasks are accomplished using Google now, so for example at screen off "OK Google Now turn on the tv" and providing you have the tasker task setup using the autovoice recognised profile or will perform the task for you
Just to clarify, using autovoice recognised under profile in tasker does not drain the battery as it's not the same thing as continuous listening mode in autovoice and you are using the moto x dedicated core for listening for your ok Google now command

Google voice commands / "oke google"

Hi,
I'm wondering if some of you KLD / KLG / MX / etc unit owners are using google voice commands. I can't use it properly on my unit, it crashes all the time. Sometimes it works, but usually it crashes. I'm using Malaysk rom. Is there anybody who can you use google voice without any problems? Or is there a simpel solution to fix my issues? I'm using a external mic connected with a jack to the backside of my unit.
I have spent a lot of time with this issue. My views are that the OEM version of the Google app is the only stable version(for voice use) for these HUs. My JY solution was to extract the Velvet.apk from the factory ROM. After updating to a Malsysk ROM, I replaced the pre updated apk back to the older factory version. You will lose out out on some updated features, but having a working voice command is nice tradeoff.
Velvet.apk, OEM JY Version
https://drive.google.com/file/d/0B0iQtPEIFgeHR3hQdGlvd2RrVUk/view?usp=sharing
Missing features.
carter.w.jason said:
I have spent a lot of time with this issue. My views are that the OEM version of the Google app is the only stable version(for voice use) for these HUs. My JY solution was to extract the Velvet.apk from the factory ROM. After updating to a Malsysk ROM, I replaced the pre updated apk back to the older factory version. You will lose out out on some updated features, but having a working voice command is nice tradeoff.
Velvet.apk, OEM JY Version
Click to expand...
Click to collapse
Hi, Does your okay google now allow you to make phone calls, send email etc.... what features are you loosing out by going this route. Thanks!!!!
aledesma said:
Hi, Does your okay google now allow you to make phone calls, send email etc.... what features are you loosing out by going this route. Thanks!!!!
Click to expand...
Click to collapse
Phone calls? No. I believe this is a common issue, there is no phone hardware onboard. Though I'm not that familiar with that feature.
Email and other task could be handled with Autovoice if Google app can not. Again, not that familiar.
For me, the main missing feature was choice of navigation app. Nav questions will only launch GMaps, newer version can launch Waze or your nag app choice, by default.
carter.w.jason said:
I have spent a lot of time with this issue. My views are that the OEM version of the Google app is the only stable version(for voice use) for these HUs. My JY solution was to extract the Velvet.apk from the factory ROM. After updating to a Malsysk ROM, I replaced the pre updated apk back to the older factory version. You will lose out out on some updated features, but having a working voice command is nice tradeoff.
Velvet.apk, OEM JY Version
https://drive.google.com/file/d/0B0iQtPEIFgeHR3hQdGlvd2RrVUk/view?usp=sharing
Click to expand...
Click to collapse
Thanks for your comment. I tried your solution and its working better, i still get some errors time to time, but is much better...thanks
[
aledesma said:
Hi, Does your okay google now allow you to make phone calls, send email etc.... what features are you loosing out by going this route. Thanks!!!!
Click to expand...
Click to collapse
If you have a phone connected via BT you can make phone calls using OK Google.
Tumke32 said:
Hi,
I'm wondering if some of you KLD / KLG / MX / etc unit owners are using google voice commands. I can't use it properly on my unit, it crashes all the time. Sometimes it works, but usually it crashes. I'm using Malaysk rom. Is there anybody who can you use google voice without any problems? Or is there a simpel solution to fix my issues? I'm using a external mic connected with a jack to the backside of my unit.
Click to expand...
Click to collapse
I've read some posts in the Malaysk ROM thread and many people have modded their units by opening them up and re-runing the internal mic. It's that mic, not the external, that is used for voice commands and apparently it is an unshielded wire that allows for a lot of interference and therefore unreliable google voice. I'm still foggy on the voice dialing but someone somewhere got this to work but not through the native bluetooth app. I think I read that they used the RK3066/Rk3188 app in the google play store or something...I'm just getting started with my unit and it's not even installed yet. Hopefully some of this was insightful for you.
newt_dunbarton said:
I've read some posts in the Malaysk ROM thread and many people have modded their units by opening them up and re-runing the internal mic. It's that mic, not the external, that is used for voice commands and apparently it is an unshielded wire that allows for a lot of interference and therefore unreliable google voice. I'm still foggy on the voice dialing but someone somewhere got this to work but not through the native bluetooth app. I think I read that they used the RK3066/Rk3188 app in the google play store or something...I'm just getting started with my unit and it's not even installed yet. Hopefully some of this was insightful for you.
Click to expand...
Click to collapse
I am using the latest Malaysk ROM dated 10th January 2016 for RK3188 1024*600. It lets me speak Ok Google and Call (contact name) to the phone when after pressing the call button. The way it works for me is:
1. Whatever is playing on the unit, it stops when I press the call button on my steering;
2. It launches the unit's dial screen;
3. I say 'OK Google', it launches the ok google listener on the phone;
4. I say 'Call (contact name)' and it calls.
Few things I had to manage before this started working was:
1. Enable the option to receive commands over bluetooth in Google Now settings in the phone;
2. Enable to XPOSED MTC in the XPOSED framework in the head unit;
3. Change the setting to integrate with phone's google now interface (something like that) in XPOSED MTC module.
Hope this helps.
Can you elaborate on this process please?
carter.w.jason said:
I have spent a lot of time with this issue. My views are that the OEM version of the Google app is the only stable version(for voice use) for these HUs. My JY solution was to extract the Velvet.apk from the factory ROM. After updating to a Malsysk ROM, I replaced the pre updated apk back to the older factory version. You will lose out out on some updated features, but having a working voice command is nice tradeoff.
Velvet.apk, OEM JY Version
https://drive.google.com/file/d/0B0iQtPEIFgeHR3hQdGlvd2RrVUk/view?usp=sharing
Click to expand...
Click to collapse
Did you go to file manager and replace the Malaysk version? Where is it located? or did you simply install with with apk instal app. Than you so much!!!!
aledesma said:
Did you go to file manager and replace the Malaysk version? Where is it located? or did you simply install with with apk instal app. Than you so much!!!!
Click to expand...
Click to collapse
Uninstalled with Titanium Backup. Velvet.apk is located in /system/priv-app. Copy/Paste replacement Velvet.apk using Root Explorer. !!! Set file permissions to 644 with Root Explorer !!! Reboot.
shaiq123 said:
I am using the latest Malaysk ROM dated 10th January 2016 for RK3188 1024*600. It lets me speak Ok Google and Call (contact name) to the phone when after pressing the call button. The way it works for me is:
1. Whatever is playing on the unit, it stops when I press the call button on my steering;
2. It launches the unit's dial screen;
3. I say 'OK Google', it launches the ok google listener on the phone;
4. I say 'Call (contact name)' and it calls.
Few things I had to manage before this started working was:
1. Enable the option to receive commands over bluetooth in Google Now settings in the phone;
2. Enable to XPOSED MTC in the XPOSED framework in the head unit;
3. Change the setting to integrate with phone's google now interface (something like that) in XPOSED MTC module.
Hope this helps.
Click to expand...
Click to collapse
Hi,
1. Enable the option to receive commands over bluetooth in Google Now settings in the phone;
Were can i find this option? I have a nexus 5 and i updated my google now, but there no option like that in google now. Or do you mean the option "bluetooth headset" under voice?
3. Change the setting to integrate with phone's google now interface (something like that) in XPOSED MTC module.
I can't find any options in Xposed MTC related to what you are writing. Are you sure this option is in Xposed MTC?
Thank you!!!
carter.w.jason said:
Uninstalled with Titanium Backup. Velvet.apk is located in /system/priv-app. Copy/Paste replacement Velvet.apk using Root Explorer. !!! Set file permissions to 644 with Root Explorer !!! Reboot.
Click to expand...
Click to collapse
I will give it a shot!!!
Hi there,
I to have been wondering about the best way to get voice dialling working and as my google voice crashes the HU more often than not, I think it is best to do this as shaiq123 has suggested by pressing the call button the steering wheel and then Ok Googling the phone to make the call.
But my phone goes to lock screen in the car and that stops this working. What I would like is that when my phone connects to the car bluetooth it
1) stops it going to lockscreen
2) activates wifi hotspot
3) activates 'ok google' if it is not normally activated
and it reverses on disconnecting.
Is this something easily done or do I need some kind of app to do this?
A final thing that would be helpful, is that it would be useful to give the play music command to direct the HU to play music from an HU attached SD card rather than the phone memory. Is there a way to also configure that (i.e. that the command would seek music stored on HU rather than phone first?)
Cheers
Mr Bigglesworth said:
Hi there,
I to have been wondering about the best way to get voice dialling working and as my google voice crashes the HU more often than not, I think it is best to do this as shaiq123 has suggested by pressing the call button the steering wheel and then Ok Googling the phone to make the call.
But my phone goes to lock screen in the car and that stops this working. What I would like is that when my phone connects to the car bluetooth it
1) stops it going to lockscreen
2) activates wifi hotspot
3) activates 'ok google' if it is not normally activated
and it reverses on disconnecting.
Is this something easily done or do I need some kind of app to do this?
A final thing that would be helpful, is that it would be useful to give the play music command to direct the HU to play music from an HU attached SD card rather than the phone memory. Is there a way to also configure that (i.e. that the command would seek music stored on HU rather than phone first?)
Cheers
Click to expand...
Click to collapse
You could achieve the first part using Tasker, you would just create a profile to run your tasks that actives when your phone connects to the headunit. Its a great app for automating stuff like that.
dc5daft said:
You could achieve the first part using Tasker, you would just create a profile to run your tasks that actives when your phone connects to the headunit. Its a great app for automating stuff like that.
Click to expand...
Click to collapse
Thanks - in fact this morning I have downloaded the trial for Tasker as well as Automate to see if they can do what I am looking for.
I've decided what would be really helpful would be if I could
1) Use app to detect when phone connects to car HU via bluetooth
2) Launch Wifi Hotspot
3) set the camera button to unlock screen and activate google voice
Now 1&2 look like its not too difficult and may even be doable using the Sony Smart Connect app (on a Z2, not rooted).
3 doesn't seem to be as instantly obvious. In tasker, I put in a new profile>event>hardware>button camera, also selected non beginner settings so could pit priority to highest and activate stop event, then put the task as launch voice search app - but it just keeps doing the camera?
Mr Bigglesworth said:
Thanks - in fact this morning I have downloaded the trial for Tasker as well as Automate to see if they can do what I am looking for.
I've decided what would be really helpful would be if I could
1) Use app to detect when phone connects to car HU via bluetooth
2) Launch Wifi Hotspot
3) set the camera button to unlock screen and activate google voice
Now 1&2 look like its not too difficult and may even be doable using the Sony Smart Connect app (on a Z2, not rooted).
3 doesn't seem to be as instantly obvious. In tasker, I put in a new profile>event>hardware>button camera, also selected non beginner settings so could pit priority to highest and activate stop event, then put the task as launch voice search app - but it just keeps doing the camera?
Click to expand...
Click to collapse
Create a new Profile>State>Net>BT Connected then click the magnifying glass next to name and select the name of your headunit. This will mean whenever your bluetooth is connected to the headunit it will run the tasks associated with it. It will give you the option to name and create a task once you create your profile then create new>Net>WiFi Tether and set to On.
I have a Z2 as well and just tried the camera button as a profile and it didn't work for me either, you'll need to do some googling on that, not sure why it doesnt work. It's best to set a flash (Alert>Flash) in your task as a test to see if your task runs but I'm sure you need to need to have root to unlock the screen.
dc5daft said:
Create a new Profile>State>Net>BT Connected then click the magnifying glass next to name and select the name of your headunit. This will mean whenever your bluetooth is connected to the headunit it will run the tasks associated with it. It will give you the option to name and create a task once you create your profile then create new>Net>WiFi Tether and set to On.
I have a Z2 as well and just tried the camera button as a profile and it didn't work for me either, you'll need to do some googling on that, not sure why it doesnt work. It's best to set a flash (Alert>Flash) in your task as a test to see if your task runs but I'm sure you need to need to have root to unlock the screen.
Click to expand...
Click to collapse
Thanks for this - and yes this where I had got to (which make me feel better!). And I too think the camera button may not be workable without root.
I think I need to change my plans and see if I can prevent the lockscreen to come on when connected to this bluetooth device. That way I can fall back to using ok google as the lockscreen prevents ok google from completing requests.
Okay - think I've done that and it was easy enough, now have a profile which when connected to HU through bluetooth does (1) set off wifi tether and (2) Set keyguard off. Then with (3) double tap to wake screen and (4) Ok google should be able to do what I need it to.
Last thing I'm wondering if you could do is to create a large voice dial icon (double normal size etc) on screen (in case initial ok google doesn't work)...

Tasker to "Type to Bixby"

Does anyone know if there is an intent or plugin. That would let me send text to Bixby.
I don't want to root and it would be good to turn on vpns, toggle mono audio and many others. That can be done via bixby and no other way without root.
Been hunting, but all my searches end up being about changing the action of the button.
Thanks
Broomfundel said:
Does anyone know if there is an intent or plugin. That would let me send text to Bixby.
I don't want to root and it would be good to turn on vpns, toggle mono audio and many others. That can be done via bixby and no other way without root.
Been hunting, but all my searches end up being about changing the action of the button.
Thanks
Click to expand...
Click to collapse
I don't know about Crappy Bixby, but I use Tasker without root with Google voice commands mapped to the Bixby button using THIS APP (well worth the purchase) for various stuff like toggle WiFi, Bluetooth, Torch, launch apps etc. Also use Tasker for automation like, turning GPS on when maps is launched and then off again when exited, stereo notification sounds, vibration pattens, loudspeaker auto on/off via proximity sensor when on a call, etc etc.... I was a bit concerned when I got the Note 9 as I really relied on Tasker on my Oneplus 3T (which was rooted) as I don't want to root, just yet Just go to THIS PAGE and install the command as shown and you are good to go
padlad said:
I don't know about Crappy Bixby, but I use Tasker without root with Google voice commands mapped to the Bixby button using THIS APP (well worth the purchase) for various stuff like toggle WiFi, Bluetooth, Torch, launch apps etc. Also use Tasker for automation like, turning GPS on when maps is launched and then off again when exited, stereo notification sounds, vibration pattens, loudspeaker auto on/off via proximity sensor when on a call, etc etc.... I was a bit concerned when I got the Note 9 as I really relied on Tasker on my Oneplus 3T (which was rooted) as I don't want to root, just yet Just go to THIS PAGE and install the command as shown and you are good to go
Click to expand...
Click to collapse
I will have a play and see if I can get it working for VPN and Mono Audio. Trust me Bixby will only ever be a means to an end.
Thanks

Categories

Resources