Bluetooth profile flashing question for XT1060 - Moto X Q&A

I was wondering if there was any way to add MAP to the bluetooth profiles to add messaging support for receiving texts in the car. I see that Moto left out this profile for some reason and I kind of miss that feature. I wasn't sure if there was a way to add this and reflash the radio drivers to the phone.
My phone is an unlocked Dev Edition XT1060 on 4.4.

htmwrx said:
I was wondering if there was any way to add MAP to the bluetooth profiles to add messaging support for receiving texts in the car. I see that Moto left out this profile for some reason and I kind of miss that feature. I wasn't sure if there was a way to add this and reflash the radio drivers to the phone.
My phone is an unlocked Dev Edition XT1060 on 4.4.
Click to expand...
Click to collapse
I am not quite sure what you are asking. Do you want to have messages from other programs read out from Moto Assist?
Or do you want to have your texts read out over a different BT profile?
It might not be quite what you are looking for but this app (http://forum.xda-developers.com/showthread.php?t=2123493) was mentioned in this thread (http://forum.xda-developers.com/showthread.php?t=2599230) regarding bluetooth operation in Kitkat.

mechanical tool said:
I am not quite sure what you are asking. Do you want to have messages from other programs read out from Moto Assist?
Or do you want to have your texts read out over a different BT profile?
It might not be quite what you are looking for but this app (http://forum.xda-developers.com/showthread.php?t=2123493) was mentioned in this thread (http://forum.xda-developers.com/showthread.php?t=2599230) regarding bluetooth operation in Kitkat.
Click to expand...
Click to collapse
Not exactly. On my previous phone, when I received a text message, the message would be sent to the car via bluetooth and read aloud. The Bluetooth profile used is called MAP, or Message Access Profile. Motorola did not include this profile in their drivers, presumably to encourage users to use the moto assist feature . I was wondering if it was possible to add this profile and reflash the updated radio drivers. But this may also include adding lines of code to the rom itself. I was unsure if this was even probable to do.

Related

Enable Motorola Assist with NFC/Tasker?

I like the Motorola Assist feature that reads back texts to you. My problem is, I don't want it enabled every time I'm in a car. For example, I do not want it to read back texts to me when I'm a passenger in someone else's car. I also don't want it to read back texts when I have passengers in my car.
Is there a way I can create a Tasker task that would enable the Motorola Assist Driving function via an NFC tag with NFC Task Launcher? I'm pretty familiar with NFC Task Launcher but I'm pretty much a total noob with Tasker.
Sorry...I meant to post this in the Q&A forum. Moderators, feel free to move it if necessary.
bump
clankfu said:
I like the Motorola Assist feature that reads back texts to you. My problem is, I don't want it enabled every time I'm in a car. For example, I do not want it to read back texts to me when I'm a passenger in someone else's car. I also don't want it to read back texts when I have passengers in my car.
Is there a way I can create a Tasker task that would enable the Motorola Assist Driving function via an NFC tag with NFC Task Launcher? I'm pretty familiar with NFC Task Launcher but I'm pretty much a total noob with Tasker.
Click to expand...
Click to collapse
I just received my Moto X and had this exact thought. I'd like to be able to automatically trigger Driving mode, but only conditionally when an NFC tag is triggered, and then have it determine when I'm not driving anymore on its own.
Unfortunately, this would almost certainly require an API to be open by the Motorola Assist app that would allow another program to talk to it and issue it commands. I don't think that's the case, which is a bit of a bummer, since it's so useful.
I was taking a short drive back to my office, so I didn't bother to pull my phone out of my pocket. Sure enough, about 2 minutes into the ride, my Pandora station started back up automatically, and since it's paired to Bluetooth, it just started playing through my car speakers, which was awesome. Would be more awesome if it was triggered automatically by BT, and/or NFC though...
unless you can get the intent info for assist the best option may be to use tasker and input taps to open assist and toggle it on/off.
I haven't tested this at all because I just decided to make my own version of this in tasker that I can enable/disable any time I want with other profiles or via voice commands.
ntalbert000 said:
unless you can get the intent info for assist the best option may be to use tasker and input taps to open assist and toggle it on/off.
I haven't tested this at all because I just decided to make my own version of this in tasker that I can enable/disable any time I want with other profiles or via voice commands.
Click to expand...
Click to collapse
Sorry if I sound dumb, but I am new to Tasker. Is your solution possible without root? Is it possible for you to post the steps you used to create this toggle?
THANKS!
jmgordon613 said:
Sorry if I sound dumb, but I am new to Tasker. Is your solution possible without root? Is it possible for you to post the steps you used to create this toggle?
THANKS!
Click to expand...
Click to collapse
pretty sure you need root for input taps

Gear with moto g

i was wondering i have gear manager installed on my moto g and it links with my phone i can make and receive calls but i cannot seam to get any of the other functions notifications or phone book etc to work is it something im doing or do they only work with samsung phones...
Many thanks
In order for all the features to work you need touchwiz framework. Which unfortunately is exclusive to Samsung.
However, if you check out the thread titled "nexus 5 for kit Kat" you might be able to get notifications to work other ways.
http://forum.xda-developers.com/showthread.php?t=2596455
440bro said:
In order for all the features to work you need touchwiz framework. Which unfortunately is exclusive to Samsung.
However, if you check out the thread titled "nexus 5 for kit Kat" you might be able to get notifications to work other ways.
http://forum.xda-developers.com/showthread.php?t=2596455
Click to expand...
Click to collapse
Hi I have a quick question. Do we need to have nfc enabled phone to get gear features work on moto g? Or blue tooth is enough. I know that moto g does not have nfc chip
Nfc is a fast, convenient way of setup. But it's not needed. It can pair like a regular Bluetooth device too.

Disable bluetooth MAP?

My X is paired to my 2013 F-150 via SYNC and it automatically adds the voice, media and message features upon connecting. However, every time I get a text, SYNC stops everything to tell me I have a new text message, and it's annoying. You can turn MAP off temporarily by manually disabling it while the phone is paired, but once it re-pairs with SYNC, it automatically activates MAP again. I do use the voice and media though.
My question is this... is there any way to permanently disable the MAP feature on the X? I don't use it and never will. I always check my phone when a new message arrives or wait until I'm at a stop. I just want to be able to be able to remove the MAP feature.
triton302 said:
My X is paired to my 2013 F-150 via SYNC and it automatically adds the voice, media and message features upon connecting. However, every time I get a text, SYNC stops everything to tell me I have a new text message, and it's annoying. You can turn MAP off temporarily by manually disabling it while the phone is paired, but once it re-pairs with SYNC, it automatically activates MAP again. I do use the voice and media though.
My question is this... is there any way to permanently disable the MAP feature on the X? I don't use it and never will. I always check my phone when a new message arrives or wait until I'm at a stop. I just want to be able to be able to remove the MAP feature.
Click to expand...
Click to collapse
You can probably unpair (from both the phone and sync) and then repair and when you repair just deny the MAP access request.
Also, you should be able to turn off new message download in Sync
triton302 said:
My X is paired to my 2013 F-150 via SYNC and it automatically adds the voice, media and message features upon connecting. However, every time I get a text, SYNC stops everything to tell me I have a new text message, and it's annoying. You can turn MAP off temporarily by manually disabling it while the phone is paired, but once it re-pairs with SYNC, it automatically activates MAP again. I do use the voice and media though.
My question is this... is there any way to permanently disable the MAP feature on the X? I don't use it and never will. I always check my phone when a new message arrives or wait until I'm at a stop. I just want to be able to be able to remove the MAP feature.
Click to expand...
Click to collapse
Did you ever find a solution for this? I just got a '14 Raptor and it does the same damned thing. I've deleted the phone pairing and repaired and deny access when repairing but it still automatically connects to all 3 protocols when I get in the truck. My phone is actually an LG G3 but it seems to be an android problem and not a specific phone problem.
boosting1bar said:
Did you ever find a solution for this? I just got a '14 Raptor and it does the same damned thing. I've deleted the phone pairing and repaired and deny access when repairing but it still automatically connects to all 3 protocols when I get in the truck. My phone is actually an LG G3 but it seems to be an android problem and not a specific phone problem.
Click to expand...
Click to collapse
Nope. I also got a '14 Focus ST and the bluetooth "feature" is even worse on it. Since I have the full touchscreen, it will now display the notification that I have a text, and who it's from. Again, you can temporarily disable it on the phone but not permanently.
triton302 said:
Nope. I also got a '14 Focus ST and the bluetooth "feature" is even worse on it. Since I have the full touchscreen, it will now display the notification that I have a text, and who it's from. Again, you can temporarily disable it on the phone but not permanently.
Click to expand...
Click to collapse
Yeah that's exactly what I'm getting in my 14 Raptor. Terrible, I guess I have to disable it every time I get in the car now.
triton302 said:
Nope. I also got a '14 Focus ST and the bluetooth "feature" is even worse on it. Since I have the full touchscreen, it will now display the notification that I have a text, and who it's from. Again, you can temporarily disable it on the phone but not permanently.
Click to expand...
Click to collapse
Do you guys have root? if so maybe you can try something. but keep in mind I have not tried this myself and also I could be completely wrong.
Anyway, I noticed in my moto x build.prop file (that sets the phone settings on boot) that one of the lines seems to disable Bluetooth SAP on boot. The line is
ro.qualcomm.bluetooth.sap = false
if that can turn off SAP maybe
ro.qualcomm.bluetooth.map = false
can turn off MAP on boot.
Keep in mind editing build.prop the wrong way can give you boot up problems. Backup the file, and also keep track of and set the appropriate permissions for the file.
In fact, it's probably better before editing build.prop to try the setting on the fly. In a terminal emulator with SU enabled try the line
setprop ro.qualcomm.bluetooth.map false
then check that with getprop and with your car.
this is safer if you have any problems you can just reboot. if it works you can proceed to build.prop
dtg7 said:
Do you guys have root? if so maybe you can try something. but keep in mind I have not tried this myself and also I could be completely wrong.
Anyway, I noticed in my moto x build.prop file (that sets the phone settings on boot) that one of the lines seems to disable Bluetooth SAP on boot. The line is
ro.qualcomm.bluetooth.sap = false
if that can turn off SAP maybe
ro.qualcomm.bluetooth.map = false
can turn off MAP on boot.
Keep in mind editing build.prop the wrong way can give you boot up problems. Backup the file, and also keep track of and set the appropriate permissions for the file.
In fact, it's probably better before editing build.prop to try the setting on the fly. In a terminal emulator with SU enabled try the line
setprop ro.qualcomm.bluetooth.map false
then check that with getprop and with your car.
this is safer if you have any problems you can just reboot. if it works you can proceed to build.prop
Click to expand...
Click to collapse
Great idea, however I just tried it with no avail.
I just thought of something as well... my fiance has a '13 Focus SE with the base stereo, and she has the same model phone as me (VZW X Dev). Her SYNC doesn't alert her to new messages, but my truck with the same SYNC setup did, but I figured my truck had a more recent version of SYNC. I dunno, all I know is it's annoying as hell and I'd like to find a more permanent solution. Especially since I'm contemplating on buying the Droid Turbo in the future and I'm sure it will do the same thing.
triton302 said:
Great idea, however I just tried it with no avail.
Click to expand...
Click to collapse
That sucks... Just to clarify I assume you tried this with a terminal emulator. did you remember to give it root before running the setprop command? i.e. type su and enter. without root setprop will appear to go through but won't actually set anything. And if it's set properly, getprop ro.qualcomm.bluetooth.map should return false like it does for SAP. otherwise it will return empty.
Another thing that might or might not make a difference, was Bluetooth on when you tried this, if so try it with Bluetooth off.
As for the difference between the two SYNCs my guess is you're right the version difference could be affecting something. A quick Google search suggests some versions of SYNC have a setting for MAP. in SYNC menu check System Settings -> Advanced -> MAP Profile
dtg7 said:
That sucks... Just to clarify I assume you tried this with a terminal emulator. did you remember to give it root before running the setprop command? i.e. type su and enter. without root setprop will appear to go through but won't actually set anything. And if it's set properly, getprop ro.qualcomm.bluetooth.map should return false like it does for SAP. otherwise it will return empty.
Another thing that might or might not make a difference, was Bluetooth on when you tried this, if so try it with Bluetooth off.
As for the difference between the two SYNCs my guess is you're right the version difference could be affecting something. A quick Google search suggests some versions of SYNC have a setting for MAP. in SYNC menu check System Settings -> Advanced -> MAP Profile
Click to expand...
Click to collapse
The newer SYNC version doesn't have that MAP option, that was the first thing I found when googling as well. (and for the record I don't have a moto, I'm using an LG G3 and found this thread while searching for a solution). Unfortunately my build.prop doesn't have those lines in it. Not sure if I could just add the MAP entry or not, that's above my knowledge base
boosting1bar said:
The newer SYNC version doesn't have that MAP option, that was the first thing I found when googling as well. (and for the record I don't have a moto, I'm using an LG G3 and found this thread while searching for a solution). Unfortunately my build.prop doesn't have those lines in it. Not sure if I could just add the MAP entry or not, that's above my knowledge base
Click to expand...
Click to collapse
well without putting in commands manually I see two things you guys can try. the first doesn't need root while the second one does.
1) turn on Bluetooth on your phones, then go to Settings -> Apps -> Running -> Bluetooth Share then just Stop the Map service. This method will stick as long as you don't turn off Bluetooth and start it again, and as long as you don't restart the phone. if you do either you'll have to do the stopping again.
2) this requires that your phone be rooted, but on the plus side it might be more permanent. There's a nifty app in the play store made by some benevolent developer that claims to disable any service started by any app. appropriately enough the app is called Disable Service. You open the app, slide over to the System Apps section, find Bluetooth Share and click it, then just uncheck the Maps service box. So simple, but won't work without root. Try it with Bluetooth off and if that doesn't work reset it then try it with Bluetooth on. But word of caution you don't want to go messing around disabling other things unless you're sure of what you're doing. disabling the wrong thing will cause you problems.
https://play.google.com/store/apps/details?id=cn.wq.disableservice
good luck.
dtg7 said:
well without putting in commands manually I see two things you guys can try. the first doesn't need root while the second one does.
1) turn on Bluetooth on your phones, then go to Settings -> Apps -> Running -> Bluetooth Share then just Stop the Map service. This method will stick as long as you don't turn off Bluetooth and start it again, and as long as you don't restart the phone. if you do either you'll have to do the stopping again.
2) this requires that your phone be rooted, but on the plus side it might be more permanent. There's a nifty app in the play store made by some benevolent developer that claims to disable any service started by any app. appropriately enough the app is called Disable Service. You open the app, slide over to the System Apps section, find Bluetooth Share and click it, then just uncheck the Maps service box. So simple, but won't work without root. Try it with Bluetooth off and if that doesn't work reset it then try it with Bluetooth on. But word of caution you don't want to go messing around disabling other things unless you're sure of what you're doing. disabling the wrong thing will cause you problems.
good luck.
Click to expand...
Click to collapse
Thanks so much! Option 2 is exactly what I've been looking for! Option 1 doesn't work for me because I use Trigger and have conditional BT on/off and that would just recreate the same problem lol.
Just tried option 2... If any of those services are unchecked, Bluetooth itself turns off automatically and won't turn back on until that service is restored.
triton302 said:
Just tried option 2... If any of those services are unchecked, Bluetooth itself turns off automatically and won't turn back on until that service is restored.
Click to expand...
Click to collapse
Yep same here, tried it on my way home yesterday and the disable service app completely disables bluetooth if you disable MAP.
boosting1bar said:
Yep same here, tried it on my way home yesterday and the disable service app completely disables bluetooth if you disable MAP.
Click to expand...
Click to collapse
Wow no breaks...but not quite out of ideas yet. a few more to spitball, going from simple to more complex:
a) we've established there's no option to disable MAP from within SYNC under System Settings. What about under Phone Settings? Indications are there should be an option there to turn off Message Notification. If it's there set it to OFF. frankly I'd expect there to be such a setting somewhere in there.
b) reaching a bit here, but in Disable Service app I notice there's another system app that has Bluetooth service settings. the app's name is org.codeaurora.bluetooth (Apparently Code Aurora is the Qualcomm Linux kernel). No idea if this will work where the other failed but won't hurt to try. the service says BluetoothMasService but if you check the full name it is map (maybe service instead of profile).
c) this one brings out the big guns. not only do you need root, but you also need Xposed installed. if you already have Xposed then it would be quick to try. if not, just read up on it. anyway, with Xposed installed you need the AppOpsXposed module. when you have that up and running you open the App Ops screen of the Bluetooth Share app (a few ways to do that, doesn't matter how). in that screen you turn off all of Bluetooth Share's access to SMS. Basically you disable Bluetooth from interacting with Messaging. you revoke the permissions. Bluetooth will still work unaware that it can't access messages, and I figure if it can't access messages it damn well can't send them to the car.
There's another module that can do this more thoroughly, but App Ops is less scary/more user friendly.
that's it. personally I still prefer my original idea of figuring out how to do it manually thru setprop and build.prop, but if that's not an option then try these.
Roger, I'm off work today so I'll try these out here shortly.
EDIT: From what I recall, if you have a recent version of MFT, there are no options whatsoever for MAP, in phone or system settings. I'll double check.
EDITING EDIT: #2 doesn't work.
dtg7 said:
Wow no breaks...but not quite out of ideas yet. a few more to spitball, going from simple to more complex:
a) we've established there's no option to disable MAP from within SYNC under System Settings. What about under Phone Settings? Indications are there should be an option there to turn off Message Notification. If it's there set it to OFF. frankly I'd expect there to be such a setting somewhere in there.
b) reaching a bit here, but in Disable Service app I notice there's another system app that has Bluetooth service settings. the app's name is org.codeaurora.bluetooth (Apparently Code Aurora is the Qualcomm Linux kernel). No idea if this will work where the other failed but won't hurt to try. the service says BluetoothMasService but if you check the full name it is map (maybe service instead of protocol).
c) this one brings out the big guns. not only do you need root, but you also need Xposed installed. if you already have Xposed then it would be quick to try. if not, just read up on it. anyway, with Xposed installed you need the AppOpsXposed module. when you have that up and running you open the App Ops screen of the Bluetooth Share app (a few ways to do that, doesn't matter how). in that screen you turn off all of Bluetooth Share's access to SMS. Basically you disable Bluetooth from interacting with Messaging. you revoke the permissions. Bluetooth will still work unaware that it can't access messages, and I figure if it can't access messages it damn well can't send them to the car.
There's another module that can do this more thoroughly, but App Ops is less scary/more user friendly.
that's it. personally I still prefer my original idea of figuring out how to do it manually thru setprop and build.prop, but if that's not an option then try these.
Click to expand...
Click to collapse
I think we have a winner! #3 works perfectly.
I tested it with the phone unlocked and locked, rebooting the phone, toggling bluetooth on and off, turning the car on and off... seems to work every time. As long as you turn off just the SMS/MMS options, you can still have it send and receive calls and allow the device to remain unlocked while connected.
Ahhhh...... Success feels good...
Xposed is pretty amazing... It gives us a fighting chance lol.
if only they'd installed Xposed on Skynet things might have turned out differently...
dtg7 said:
c) this one brings out the big guns. not only do you need root, but you also need Xposed installed. if you already have Xposed then it would be quick to try. if not, just read up on it. anyway, with Xposed installed you need the AppOpsXposed module. when you have that up and running you open the App Ops screen of the Bluetooth Share app (a few ways to do that, doesn't matter how). in that screen you turn off all of Bluetooth Share's access to SMS. Basically you disable Bluetooth from interacting with Messaging. you revoke the permissions. Bluetooth will still work unaware that it can't access messages, and I figure if it can't access messages it damn well can't send them to the car.
There's another module that can do this more thoroughly, but App Ops is less scary/more user friendly.
Click to expand...
Click to collapse
Awesome, worked here as well!! I'd looked through xposed and didn't see any modules that would do what we were after, completely forgot about AppOps. Outstanding work and thanks so much for the help!
You're welcome!
boosting1bar said:
Awesome, worked here as well!! I'd looked through xposed and didn't see any modules that would do what we were after, completely forgot about AppOps. Outstanding work and thanks so much for the help!
Click to expand...
Click to collapse
How did you get this yo work? I am on a cm12 Rom also with the same issue.
Did all the above, but anytime I start the Bluetooth afterwards, it just reactivates the "Read / Write sms messages permission all over again nd im back to square 1.
Sorry to bump an old thread. But its still yhe same issue I am dealing with.

Custom Rom with "always listening" voice activation?

Hi!
I've extensively googled, reddited and searched on XDA, but haven't found an answer.
Are there ROMs supporting the "voice anywhere"-feature (the sound processor of the Moto X) to be activated even with an activated lockscreen/handsfree?
I've setup my room with Philips Hue Lights and various interactions with other devices via tasker and all is controlled via the "Moto Voice/Auto Voice" feature.
I'm unrooted yet but would like to switch to a custom rom now, but haven't found anything conclusive whether the devs were able to implement the always-listening function.
Alas I think I can say for sure it doesn't exist ..there's one for the 1st gen so maybe there is hope
The ones for 2013 are only modified stock not aosp. Far as I know the moto specific features like touch less controls and active display or whatever they call them now are not open source this you will not find them on anything but stock
Sent from my XT1053 using Tapatalk 2

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)...

Categories

Resources