Last night I was checking out Cyanogen's web site and I came across this:
Bluetooth Voice Commands Missing in CM6?
Hello,
One of the newer features that I liked so far in CM-6 was the ability to long press my bluetooth headset action button which resulted in a voice telling me to say a command. This was much better than the original phone voice dialer, which requires manual intervention to pick a number from its list of guesses after you speak, and which offers no voice prompt to let you know when it's ready.
Well, as of upgrading to CM-6.0 from the 8-25 nightly, the bluetooth/headset dialer is gone and when I long press my bluetooth headset button It's back to the old phone voice dialer which requires manual intervention to place a call and offers no voice prompt. How do I get the bluetooth dialer back?
I have attached the 09SEP-VoiceDialer.apk from CM-6 release for easy downloading.
***Instructions- Download the file into your root of your SD card, using Root Explorer remove the old VoiceDialer.apk and install the new 09SEP-VoiceDialer.apk
The OLD VoiceDialer.apk can be found under /system/app
Mine is working great!
Any questions, PM me....
Enjoy!
my bluetooth headset can now operate the voice commands, however, after a command is given, Voice Dialer FCs.
KF34
gohamstergo said:
my bluetooth headset can now operate the voice commands, however, after a command is given, Voice Dialer FCs.
KF34
Click to expand...
Click to collapse
Did you remove the old VoiceDialer.apk?
Also, don't forget to change the permissions on the 09SEP-VoiceDialer.apk after yoo move it to /system/app.
This is working great for me, back to the way it was before the update!
Sent from my FroyoEris using XDA App
so as far as the instructions:
***Instructions- Download the file into your root of your SD card, using Root Explorer remove the old VoiceDialer.apk and install the new 09SEP-VoiceDialer.apk
is install the new file is just copying it then pasting it into the system/app folder using root explorer, longpress on app and change permissions to allow all. then reboot.
EDIT: apparently yes, my bt headset works perfectly with voice dialer now. thank you.
This is great -- restores the BT voice dialing functionality that should have been stock in the Eris from the start
Is the source for this APK available? I wonder if it would be possible to modify to add an optional "confirmation" step:
User: "Call Jim Somename"
Phone: "Calling Jeff Someothername, is that correct?"
User: "No"
Could certainly be fancier, like presenting several options, but the above would be sufficient to prevent misdialing people you don't mean to call in other area codes, etc. That's my main hesitation to use it right now; my wife's name, in particular, seems to mismatch to other names often.
I haven't done much Android development yet, but I'd be interested in poking at this code.
jmastron said:
This is great -- restores the BT voice dialing functionality that should have been stock in the Eris from the start
Is the source for this APK available? I wonder if it would be possible to modify to add an optional "confirmation" step:
User: "Call Jim Somename"
Phone: "Calling Jeff Someothername, is that correct?"
User: "No"
Could certainly be fancier, like presenting several options, but the above would be sufficient to prevent misdialing people you don't mean to call in other area codes, etc. That's my main hesitation to use it right now; my wife's name, in particular, seems to mismatch to other names often.
I haven't done much Android development yet, but I'd be interested in poking at this code.
Click to expand...
Click to collapse
I do not know but I can give you a link to Cyanogen's post if you would like....
http://forum.cyanogenmod.com/topic/6497-bt-voice-dialing/page__p__57811__hl__bluetooth__fromsearch__1#entry57811
I remove the old voicedialer. I copied over to system/app change the perms and reboot. when long pressing the bluetooth the dialer comes up but never prompts. I tried renaming the file. I tried just an install. that worked once but FC verytime after.
What am i doing wrong
Thanks for this
I can't believe that Google has worse technology than MS on this! MS Voice Command is far superior.
I tried vlingo with mixed results.
Will try this.
Just installed on my Aria running Liberated 2.2 and it works great!
BTW, I couldn't for the life of me delete the old VoiceDialer.apk using a file explorer, so I just took a shot and installed this Voice Dialer, so no real need as far as I can tell to go through the hassles of the instructions above.
Many thanks.
I tried.this but I keep getting a parsing error ???? I'm a noob have no clue what that means..lol
Sent from my Eris using XDA App
I realize that this is a bit of a dead post, but do you think this apk would work on a Samsung Captivate? I'm currently running with Perception 10.3 and Speedmod kernel, but for some reason the BT Voice Dialer has decided to stop working and is continually stuck at Starting Up.
I'm trying to get this to work on my Aria running FR0008 but no dice. Even using Root Explorer I simply cannot get either the original Dialer.apk deleted or the replacement 09SEPDialer.apk installed.
What am I doing wrong? I REALLY want the proper Bluetooth dialer in this ROM as I use a headset often and at the moment I prefer it to the Cyanogen ROMS.
woodbane said:
I'm trying to get this to work on my Aria running FR0008 but no dice. Even using Root Explorer I simply cannot get either the original Dialer.apk deleted or the replacement 09SEPDialer.apk installed.
What am I doing wrong? I REALLY want the proper Bluetooth dialer in this ROM as I use a headset often and at the moment I prefer it to the Cyanogen ROMS.
Click to expand...
Click to collapse
Have you tried this? Download the 09Sep-VoiceDialer.apk to your computer. Rename it VoiceDialer.apk and place it in your tools directory of SDK. Connect your phone to PC. Open a command prompt window and navigate it to your tools directory of SDK. Type adb remount. Then type adb push VoiceDialer.apk /system/app. Then adb reboot. Be certain to take not to the caps in the file name as well so it will overwrite the one that's already in place on your phone. Hope this helps
CondemnedSoul said:
Have you tried this? Download the 09Sep-VoiceDialer.apk to your computer. Rename it VoiceDialer.apk and place it in your tools directory of SDK. Connect your phone to PC. Open a command prompt window and navigate it to your tools directory of SDK. Type adb remount. Then type adb push VoiceDialer.apk /system/app. Then adb reboot. Be certain to take not to the caps in the file name as well so it will overwrite the one that's already in place on your phone. Hope this helps
Click to expand...
Click to collapse
That sounds very helpful, only problem is I have no idea about SDK and ADB. Is there a really abbreviated way of getting me up and running with this?
woodbane said:
That sounds very helpful, only problem is I have no idea about SDK and ADB. Is there a really abbreviated way of getting me up and running with this?
Click to expand...
Click to collapse
Try here http://developer.android.com/sdk/index.html
There's instructions for installation and the downloads. Everything you should need
CondemnedSoul said:
Try here http://developer.android.com/sdk/index.html
There's instructions for installation and the downloads. Everything you should need
Click to expand...
Click to collapse
Awesome, I'll try giving that a whirl later this evening. Thanks for the pointer.
So, I gotta be honest, I just simply do not have the technical know how to get this working. I've downloaded and installed all relevant files but can't even seem to get the phone connected.
Here's what I'd love to be able to do, simply replace the VoiceDialer.apk in the Aria FR008 ROM - which does not support Bluetooth voice dialing with this one that apparently does.
I have tried unzipping the FR008 ROM and replacing the file and rezipping. When I go to install it from card in recovery mode it immediatly crashes. I'm seeing that the FR008 zip is "signed" and guess that I'm missing doing something important here, resigning either the whole ROM or just the file?
Can anyone please help me out here as I'm really struggling with this.
woodbane said:
So, I gotta be honest, I just simply do not have the technical know how to get this working. I've downloaded and installed all relevant files but can't even seem to get the phone connected.
Here's what I'd love to be able to do, simply replace the VoiceDialer.apk in the Aria FR008 ROM - which does not support Bluetooth voice dialing with this one that apparently does.
I have tried unzipping the FR008 ROM and replacing the file and rezipping. When I go to install it from card in recovery mode it immediatly crashes. I'm seeing that the FR008 zip is "signed" and guess that I'm missing doing something important here, resigning either the whole ROM or just the file?
Can anyone please help me out here as I'm really struggling with this.
Click to expand...
Click to collapse
Yeah... if you unzip it you will need to sign it when you zip it in order to flash it. Try opening to rom with 7zip or winrar and just drag and drop the new one into the zip to replace the old one. Don't unzip it.
Sent from my Blackened Ginger using XDA App
Hi guys,
when i dial *363# from my leo, it says "Command not supported"
is hd2 not supported for cusd command ? or is there anything i can do to enable that command ( registry hack maybe ? )
thanks
still need answer from the expertise what should i do ....
not seen that command before, couldnt find it on google, , whats it (supposed to) do?
I have the same problem but with different company and different number - my is #96*phone_number*cash#. It is for transfer some cash to other number but it says like ronald_delgeano said in his first post: "Command not supported". Simple Nokia 6233 doesn't have such problem. Obviously it's a "feature" of Windows Moblie, but I hope there is some registry hack/change to fix it.
Come on, somebody had to experience this problem and found a solution.
PS My hardware is Omnia II.
Hello,
Right so tech savy people lets get the creative juices flowing!
Problem?
1. I cant remove the gmail account I added to my phone,sure others cant either.
2. I can technically, WITH A FACTORY RESET, but I dont want to do this.
Ive searched on XDA for a fix to this and Ive ran across an attachment for the HTC Desire. Havnt tried it because its not for the Vibrant. Maybe someone can play around with it and make it work on Vibrant?
AND... Ive came across this code/walkthrough (not for vibrant)
"download from xda developers UniversalAndroot 1.6.1
download the sqlite browser here
install universalandroot.apk on your mobile
run it and get the root access
select the debug from menu->settings->applications->development->usb debugging
plug in the phone on your pc and select the sync method with pc
download the SDK from google android site.
copy the zip content in c:\android
open cmd and go to c:\andorid\tools\
lunch adb.exe shell
you will see the $
write su
look on the screen of your phone. You will be asked to accept the root connection. just accept.
now in cmd you will see #
cd /data/data/com.android.providers.contacts/databases
cat contacts2.db > /sdcard/contacts2.db
open the db from your sdcard with sqlite browser and modify the _sync_ table removing the unwanted account row.
cd /data/data/com.google.android.providers.gmail
delete the unwanted [email protected] file
from /data/system/sync/accounts.xml delete all account rows you don't need more and modify the sequence id
from /data/system/accounts.db remove the row of unwanted account and save the file (as in 17th step)"
Anyhow... anyone can help me and a ton of other people out there?
Thanks,
Tim
Are you rooted? If you are you can use root explorer from the market (paid app) to remove it.
Well I will give that a try. Sounds fairly simple. Now would I have to worry about contact and other data being erased when I try this? =)
And ill still be able to use another google account as the primary right?
Thanks,
Tim
any answers for me?
Becool0130 said:
Well I will give that a try. Sounds fairly simple. Now would I have to worry about contact and other data being erased when I try this? =)
And ill still be able to use another google account as the primary right?
Thanks,
Tim
Click to expand...
Click to collapse
Well did it work?
Sent from my SGH-T959 using XDA Premium App
well man the thing about it is... I dont know what exactly to delete ?
and thanks
Hey all, I've had this issue for quite awhile and have looked around extensively on the internet before coming here. So if you don't wanna read what I've already found out, just skip to the last paragraph for a summary of my problem.
So I have a home automation system setup for my house and I'm loving everything about it. I already have an app on my Galaxy S that will let me control the devices. I took it a step farther and delved into how to send commands using the HTTP post commands. I've already created perl scripts that can activate and deactivate the devices, but as you know Android doesn't have perl inbuilt.
I want to be able to make a shortcut on my Android device to start the devices. The reason why I want to do this is simply because I want an alarm on my android device to trigger a shortcut which turns on everything I want in the morning without me having to actually touch my phone. I already have the Alarm app that can open the shortcut, but I need a script that will work.
I need a shortcut that would enable the devices. So my first thought would be a bash script (and make a shortcut using Gscript for the Alarm App). But there's the problem, because I don't know how to send a http command from the Android terminal. I know (and have tested) perl commands, but perl isn't available for Android. That was the only way I know how to do this. I know you can use java, but then you're creating other files and to me it seems too much of a hassle. I just need something that can access the http page without opening an internet browser or anything else.
Summary:
I need a shortcut on my android device that accesses an http page without opening an internet browser or any other program. The http page has a standard username/password prompt, but can be easily worked around.
What's the easiest way of going about this? If a shell script is needed, what would be the command to open the webpage without opening a browser?
Things to know:
- Weblink only needs to be opened (no interaction required) for the specific device to be turned on
- Website is password protected using standard http protocol (but can be worked around if there is a problem)
- In perl, all I would need to do is issue the following command to get the devices to turn on or off:
perl -u username : password h-t-t-p-whatever.com/device_3_on
Sorry for the drawn out post, but I really wanted to explain my situation as best as I could. I'm sure there is probably an easier way that I'm missing here, so I need help from any and all people that would know about these things. Any [helpful] advice is welcome
Ok, i post because i'm a noob programing in android
but i got a idea to fix the problem with the ussd codes in gsm networks.
so far i achieved see USSD codes via Log.
so i use this line in adb shell or terminal emulator
logcat -b radio -s RIL-MX | grep "Read Ch0"
Click to expand...
Click to collapse
if you run a ussd code, you can view the response of the ussd code.
so i try to make a app we can dialing a ussd code and filter that log to show only the ussd response.
Good luck.....
Waiting....for it
According to my findings photon is able to send USSD Codes (able to use recharge coupons which use ussd code) But unable to read the response from network. It may related to phone apk , dialer apk or framework apk.
Sent from my Motorola Electrify using Tapatalk 2
gtuxyco said:
Ok, i post because i'm a noob programing in android
but i got a idea to fix the problem with the ussd codes in gsm networks.
so far i achieved see USSD codes via Log.
so i use this line in adb shell or terminal emulator
if you run a ussd code, you can view the response of the ussd code.
so i try to make a app we can dialing a ussd code and filter that log to show only the ussd response.
Click to expand...
Click to collapse
... this will be great if you get succeeded ...
According to the Motorola forums, they crippled photon ussd codes due to the basis this was targeted as a cdma phone and use of gsm through sprints higher cost roaming. Now if you could compare the GSMmmicode smali in atrix 2.3.4 framework.jar with the photon 2.3.4 framework.jar file. You might find the right switch. Or just replace with the atrix gsmmmicode smali file. The Motorola forums said that the ussd code was fixed better in 2.3.6 atrix code.
I'm not working on it, but just pointing out where to fix it.
See post 46 for the location of the GSMmmicode.java file.
http://code.google.com/p/android/issues/detail?id=2226#c46