Just installed CleanROM 6 R2. Very nice ROM! I do have a continuing issue I want to put out there, see if any others have it? Confirm it?
This isn't due to the ROM, but with the new ROM installed, the problem continues, so I am curious. (Going to try another soon)
When I have pattern security, and using my Q2 Blueant Bluetooth headset, I try to make a voice call. (S Voice disabled, Assistant used for voice commands currently) When trying to make the call, I hear the tone from the phone, to start talking, but I get a "Not supported by phone" message on the headset.
If I attempt the same test, with NO lock screen security it works fine.
I attempted this test, with pattern security on a S4 for ATT, works. S4 for Verizion, NOT working. Same for the S3.
I test with the same bluetooth on a Verizon Rezound (GF phone), works perfectly.
Why does it fail on the S3, with stock 4.2.1 and now with CleanROM? I figured it was some kind of software from Verizon... maybe the firmware somehow? Remaining software of some kind?
bigb78 said:
Just installed CleanROM 6 R2. Very nice ROM! I do have a continuing issue I want to put out there, see if any others have it? Confirm it?
This isn't due to the ROM, but with the new ROM installed, the problem continues, so I am curious. (Going to try another soon)
When I have pattern security, and using my Q2 Blueant Bluetooth headset, I try to make a voice call. (S Voice disabled, Assistant used for voice commands currently) When trying to make the call, I hear the tone from the phone, to start talking, but I get a "Not supported by phone" message on the headset.
If I attempt the same test, with NO lock screen security it works fine.
I attempted this test, with pattern security on a S4 for ATT, works. S4 for Verizion, NOT working. Same for the S3.
I test with the same bluetooth on a Verizon Rezound (GF phone), works perfectly.
Why does it fail on the S3, with stock 4.2.1 and now with CleanROM? I figured it was some kind of software from Verizon... maybe the firmware somehow? Remaining software of some kind?
Click to expand...
Click to collapse
I don't have this BT issue on Clean or any other TW or ASOP rom. I use PIN lockscreen. I have used my ERA and Blueant BT with Cyberon voice commander, and both work fine. On ASOP, I get a 5 second delay in acknowledging the command bit it eventually works.
jlokos said:
I don't have this BT issue on Clean or any other TW or ASOP rom. I use PIN lockscreen. I have used my ERA and Blueant BT with Cyberon voice commander, and both work fine. On ASOP, I get a 5 second delay in acknowledging the command bit it eventually works.
Click to expand...
Click to collapse
Can you switch to pattern lock and test again with the blueant BT? I am set to immediate lock on power button. Patter required immediately. Also, are you using a Q2 Blueant?
Thanks
bigb78 said:
Can you switch to pattern lock and test again with the blueant BT? I am set to immediate lock on power button. Patter required immediately. Also, are you using a Q2 Blueant?
Thanks
Click to expand...
Click to collapse
I was using the Q2 with pattern lock. I now use the jawbone with PIN lock. Sorry for the confusion.
Thanks.
But... DAMN! LOL I can't figure out why this is happening. I will try Cyberon, but S Voice and Assistant failed for me.
http://support.verizonwireless.com/pdf/system_update/galaxy_s3.pdf
I am guessing that JZO54K.I535VRBMF1:
"Access phone screen without
unlocking device when connected via
Bluetooth headset"
Has something to do with my issue? (Wishful thinking)
bigb78 said:
http://support.verizonwireless.com/pdf/system_update/galaxy_s3.pdf
I am guessing that JZO54K.I535VRBMF1:
"Access phone screen without
unlocking device when connected via
Bluetooth headset"
Has something to do with my issue? (Wishful thinking)
Click to expand...
Click to collapse
I hope it helps you. I have been very frustrated since the JB update with BT voice dialing. ICS worked 100% better. Both S voice and Google now have been very disappointing for voice dialing. I find Cyberon to work more than 95% of the time.
jlokos said:
I hope it helps you. I have been very frustrated since the JB update with BT voice dialing. ICS worked 100% better. Both S voice and Google now have been very disappointing for voice dialing. I find Cyberon to work more than 95% of the time.
Click to expand...
Click to collapse
Yeah, I hope so too. Maybe when CleanROM is updated with MF1 I will find out.
I have been happy with Assistant, as far as quality of voice dialing interpretation. I even bought the paid version, although not needed really.
S Voice is horrible, the S3 version. My buddy has the S4 on ATT, and S Voice is WAY better. (And my BT works with patter lock on his S4. But NO WAY I got to ATT. Hahaa)
bigb78 said:
Yeah, I hope so too. Maybe when CleanROM is updated with MF1 I will find out.
I have been happy with Assistant, as far as quality of voice dialing interpretation. I even bought the paid version, although not needed really.
S Voice is horrible, the S3 version. My buddy has the S4 on ATT, and S Voice is WAY better. (And my BT works with patter lock on his S4. But NO WAY I got to ATT. Hahaa)
Click to expand...
Click to collapse
There are a couple of TW roms, including Bone Stock and Hyperdrive that give you the option to choose S4 S Voice to install. If you are on a stock kernel, you can probably flash the MF1 firmware and not bork your camera. You should check the clean rom thread to see if anyone has done that yet.
jlokos said:
There are a couple of TW roms, including Bone Stock and Hyperdrive that give you the option to choose S4 S Voice to install. If you are on a stock kernel, you can probably flash the MF1 firmware and not bork your camera. You should check the clean rom thread to see if anyone has done that yet.
Click to expand...
Click to collapse
Yep, I am watching the forum. Don't want to be the first one to try it, I don't yet have the skills to fix undocumented problems.
I think my problem though, is the Bluetooth security bypass. Not the Voice app..... but time will tell.
Just flashed the MF1 firmware and the Stock ROM for MF1, and no luck on bluetooth!
Anyone out there with a BlueAnt Q2 bluetooth and a S3, stock or another ROM that could test for me? Killing me not being able to control my phone on the motorcycle, my HTC never had the problem, only S3 and S4 on Verizon... S3 and S4 on ATT works.
I'll put a bounty on this... need to figure it out!
bigb78 said:
Just flashed the MF1 firmware and the Stock ROM for MF1, and no luck on bluetooth!
Anyone out there with a BlueAnt Q2 bluetooth and a S3, stock or another ROM that could test for me? Killing me not being able to control my phone on the motorcycle, my HTC never had the problem, only S3 and S4 on Verizon... S3 and S4 on ATT works.
I'll put a bounty on this... need to figure it out!
Click to expand...
Click to collapse
Try this link: http://forum.xda-developers.com/showthread.php?t=1896171
Related
All credit goes the great mike1986. as this was taken from his thread.
Thanks to him Ive successfully been able to fix the bluetooth voice earpiece feature that was not working on the Rom in the signature.
Ive flashed my share of Froyo Roms and it seems that a lot of them have the same problem as well as some Gingerbread maybe.
The idea is to push the call/end button on your bluetooth connected earpiece to do various call related features without having to grab your phone, its all controlled via voice command.
Many people have been looking for a fix for this.. well here it is.
Directions:
Flash via CWM, reboot and you should have the feature fully functional.
*More information on what this does here: http://www.androidtapp.com/true-hands-free-driving-and-bluetooth-voice-dialing-is-in-android-2-2/
Additionally here is a video on the Voice Actions for Android, NOTE: This is different from the Bluetooth Voice Dialer as it has additional features
http://www.youtube.com/watch?v=tPPcTN5sdX4
and
http://www.youtube.com/watch?v=8Ml34vtrGwc
Wow, this is fantastic. I was following the info posted in that AR 3.2 thread, so I'm happy to see something posted.
I'll give this a try tonight.
legend221 said:
Thanks to him Ive successfully been able to fix the bluetooth voice earpiece feature that was not working on the Rom in the signature.
Click to expand...
Click to collapse
I'm running RCMix 5.3 and the BT voice dialer works alright for me. Do I need this fix? The one thing I'd really like from the current ROM for BT voice dialing is to have a tone to cue me when the applet is ready to listen.
BillTheCat said:
I'm running RCMix 5.3 and the BT voice dialer works alright for me. Do I need this fix? The one thing I'd really like from the current ROM for BT voice dialing is to have a tone to cue me when the applet is ready to listen.
Click to expand...
Click to collapse
Thats exactly what this does, install and you'll see this for yourself mate.
Sent from my fast / stable HTC Inspire 4G
I am running AR 5.1.3. Voice dial works fine from the phone but when I try to initiate it from my bluetooth headset I get a Force Close of processcom.android.voicedialer. I uninstalled voice dialer with TB and then installed the bluetooth voice dialer from this thread via CWM and I still get the force close when initiating from my bluetooth.
Any ideas on how I can fix this other than flashing a new rom?
Okay I just flashed to LeeDroid which claims to have fixed the Bluetooth Voice Dial Problem and I still get a force close when initiating it from my headset.
Anyone have any ideas please????
Wow this is cool to have. Im not having much accuracy though. Ive got a 2 year old Jawbone Prime so my bets are that its the problem. Looks cool but hasnt played nice since day one. Anyhow this does work if you got a decent headset
Did you ever figure this out?
toadleyb said:
Okay I just flashed to LeeDroid which claims to have fixed the Bluetooth Voice Dial Problem and I still get a force close when initiating it from my headset.
Anyone have any ideas please????
Click to expand...
Click to collapse
svarzaru said:
Did you ever figure this out?
Click to expand...
Click to collapse
I'm having the same problem and would really like to see this fixed. When I tap the voice dialer app on the phone, it works as it should. However, it always FC when pressing the bluetooth button. I think the settings file associated with connecting the bluetooth button to the app is the problem, but I don't know what file it is or how to make it better.
xperi said:
I'm having the same problem and would really like to see this fixed. When I tap the voice dialer app on the phone, it works as it should. However, it always FC when pressing the bluetooth button. I think the settings file associated with connecting the bluetooth button to the app is the problem, but I don't know what file it is or how to make it better.
Click to expand...
Click to collapse
Download Cyberon Voice from the market. It does cost a couple of bucks but it makes all problem go away on every rom you need BT with. At least for me it did!
Confirmed working with Virtuous Unity 1.24.0 Sense 3.0 based on Pyramid with Vlingo
Man just what I was looking for will give it a try.....Thanks
Sent from my Inspire 4g using XDA Premium App
missing voice dialer
I tried to flash it, and it didn't do anything. I'm using Virtuous Unity v1.27.0. I even tried to extract the app from the zip (which currently doesn't exist on my phone) and install that way, but it says "application not installed". Nothing happens at all when i hit the button on my bluetooth. With the stock rom, before installing VU, it would pull up the voice dialer. But i can't even install it now. Can anyone help me out? Thanks!
EDIT: Got it to install, but now it force closes when I try to use it, with or without a bluetooth headset.
awesome!!!!!
I'm running AHD 6.1 but it lacks the ability to let bluetooth headset to do voice command. but after i flashed this it worked out fine!!
and btw im using vlingo to do voice dialing, its an awesome app!!
legend221 said:
All credit goes the great mike1986. as this was taken from his thread.
Thanks to him Ive successfully been able to fix the bluetooth voice earpiece feature that was not working on the Rom in the signature.
Ive flashed my share of Froyo Roms and it seems that a lot of them have the same problem as well as some Gingerbread maybe.
The idea is to push the call/end button on your bluetooth connected earpiece to do various call related features without having to grab your phone, its all controlled via voice command.
Many people have been looking for a fix for this.. well here it is.
Directions:
Flash via CWM, reboot and you should have the feature fully functional.
*More information on what this does here: http://www.androidtapp.com/true-hands-free-driving-and-bluetooth-voice-dialing-is-in-android-2-2/
Click to expand...
Click to collapse
Will this work with Gingerbread ROMs? mike1986's current DHD/Inspire4G ROM does not support voice dialing via bluetooth. Kind of a pain in the rear not having it!
crypted said:
Will this work with Gingerbread ROMs? mike1986's current DHD/Inspire4G ROM does not support voice dialing via bluetooth. Kind of a pain in the rear not having it!
Click to expand...
Click to collapse
The post before yours says they're running "AHD" 6.1 with this dialer and it works fine. I'm assuming this was supposed to be ARHD 6.1 which is a GB ROM
homeslice976 said:
The post before yours says they're running "AHD" 6.1 with this dialer and it works fine. I'm assuming this was supposed to be ARHD 6.1 which is a GB ROM
Click to expand...
Click to collapse
Yeah, I wasn't clear. I figured it would work since it worked on the one before, but I wasn't sure if the previous post was confirming 6.1.0 or 6.1.1. So, I'm hoping for 6.1.1 support confirmation so I don't brick this puppy.
crypted said:
Yeah, I wasn't clear. I figured it would work since it worked on the one before, but I wasn't sure if the previous post was confirming 6.1.0 or 6.1.1. So, I'm hoping for 6.1.1 support confirmation so I don't brick this puppy.
Click to expand...
Click to collapse
6.1.0 was the first version of his new base (2.3.5GB based on HTC 3.06.405.1)
6.1.1 is the same base with updates/enhancements from mike1986. I can't imagine this would bork you. If you're too worried, make a backup. This isn't going to brick your phone to a point where you can't get to recovery and flash your backup
homeslice976 said:
6.1.0 was the first version of his new base (2.3.5GB based on HTC 3.06.405.1)
6.1.1 is the same base with updates/enhancements from mike1986. I can't imagine this would bork you. If you're too worried, make a backup. This isn't going to brick your phone to a point where you can't get to recovery and flash your backup
Click to expand...
Click to collapse
Right. That was my assumption and my plan once I got home tonight to do that assuming no-one confirmed it for me. Will flash after while and edit post with results.
I flashed this to arhd 6.1.1. It don't work. App did not appear to be installed. I tried installing the apk and it would just say application not installed.
So it appears to be a no go.
Sent from my HTC Inspire 4G using XDA App
I just finished installing all the stereo parts in my car only to find out that my Captivate won't work with the voice dialing of the stereo. I guess it's the phone's fault as my wife's Focus works just fine as did my old HTC Pure. She won't trade phones with me so I'm stuck trying to find a ROM that has this.
With Samsung stating it will be fixed (added) in 2.2.1; does that mean only the 2.2.1 ROMS will have this feature? I'm currently running Cognition 4.3.1 and it does not have it; but would like to only try new ROMS that have it. What ROMS do have the feature?
Thank you for your input.
Firefly supports voice dialing. You have to start the Voice Dialling app and then say the command.
What I'm looking for is what the Droid Incredible has. I paired it to my stereo and when I hit the call button on the stereo; it launched what appeared to be a bluetooth voice dialer application that allowed me to speak into the stereo.
I just tried firefly and it did have that app, but it crashed as soon as I tried it. It also crashed the music app, failed to mount the storage drives, crashed when trying to put it in debugging mode and pretty much was unstable since it booted. I then tried to use one click odin and it went to a blue screen half way through the process. It'll be a fun night.
Probably not what you want to hear, but my BT in the car works great on my 'stock' set up. I think it has more to do with the kernel/ modem configuration than the ROM though.
dragon has this. many people are pairing it with choice dialer.
Dani897 said:
dragon has this. many people are pairing it with choice dialer.
Click to expand...
Click to collapse
I can't get Choice Dialer to work well at all. ONe example: "CAll Tom Jones", it says "CAll Tom Jones?", I say "Yes", it says "Try again". Argh...
ANd most of th time it just doesn't understand me at all.
I believe this is the apk you need. I know cog doesn't come with it. This is an old one so I don't know if there is a newer version available but when you pair your bluetooth and hit the voice command on your stereo or bluetooth set, make this the default app when the prompt shows up. It won't give you a voice prompt but if you wait 2 secs and then speak it should dial for you. Only problem is that your phone has to be awake but at least you can use voice commands from your bluetooth set. Just leave your phone plugged in and awake while your in the car. This is the only option I have found.
That worked.
Thank you for the apk. That works.
ewingr said:
I can't get Choice Dialer to work well at all. ONe example: "CAll Tom Jones", it says "CAll Tom Jones?", I say "Yes", it says "Try again". Argh...
ANd most of th time it just doesn't understand me at all.
Click to expand...
Click to collapse
It's not unusual to be called by anyone
It's not unusual to have a text from anyone
but when I try to use voice dial for anyone
It's not unusual to see me cry
Roflmfao!
studacris said:
It's not unusual to be called by anyone
It's not unusual to have a text from anyone
but when I try to use voice dial for anyone
It's not unusual to see me cry
Roflmfao!
Click to expand...
Click to collapse
Boy, ain't that the truth. It really chaps me that the one thing that should be solid on a Cell now-a-days is voice dial. Can't believe that OLD OLD technology from Microsoft on Winmo SHINES so much better than Android. Maybe that's the only thing that does, but in my opinion, one of the most important things for a cell phone...at least if you anticipate wanting to use it while driving.
That was a tom jones joke ...
I'm glad the Voice Dialer apk worked. I couldn't get it to work on any Captivate ROMs. Most reoriented i9000 ROMs have a working version, but I find all of the i9000 ROMs to be severely lacking in performance compared to KB1 ROMs.
My preferred solution in either case is to use Bluetooth Launch and Voice Search. Bluetooth Launch can be found here. Run it from the app drawer, it brings up a full list of installed apps and available activities. Choose Voice Search, and then the "VoiceRecognition" activity (must have Google's Voice Search installed first of course). Then, hit your call button, and set Bluetooth Launch as the default activity when it asks. From then on, your call button will launch Voice Actions, which support not only "call <contact>" but also a ton of other commands, including controlling music, text msgs, etc. I love sending texts without touching my phone, and it works flawlessly for me so far.
Hoping someone out there can help me
I have the Verizon G3 and have installed several custom ROM's. I really would like to have CM10 as my DD but I am running into an issue with most of the CM10 variants. I have a car stereo with Bluetooth support, I have no issues pairing the phone, that works OK. But shortly after I pair my phone I receive a dialog that asks for permission to download my address book to my stereo (this is an extremely handy feature since I can then use the car's voice activation feature to place a call e.g. "Call So-and-So on Cell". When I give the phone permission, it seems the download never completes. Normally, the stereo will display a message that says "Download Complete" but in this case I never see that message. Also, when I try to use my voice activation the stereo keeps telling me "Phone book still downloading", This happens on any CM-based ROM that I try, it is very consistent so I am assuming there is something in the base CM code. If I install any ROM based on stock I have never seen this issue, the phonebook download completes in a few seconds. I have also tried pairing an iPhone and a Blackberry and everything is fine.
I am wondering if anyone else has seen this issue and if anyone knows a way this can be fixed? This is my "acid test" for an acceptable rom for me so I am hoping I can get this addressed so I can move away from stock.
Thanks in advance!
bhauver said:
Hoping someone out there can help me
I have the Verizon G3 and have installed several custom ROM's. I really would like to have CM10 as my DD but I am running into an issue with most of the CM10 variants. I have a car stereo with Bluetooth support, I have no issues pairing the phone, that works OK. But shortly after I pair my phone I receive a dialog that asks for permission to download my address book to my stereo (this is an extremely handy feature since I can then use the car's voice activation feature to place a call e.g. "Call So-and-So on Cell". When I give the phone permission, it seems the download never completes. Normally, the stereo will display a message that says "Download Complete" but in this case I never see that message. Also, when I try to use my voice activation the stereo keeps telling me "Phone book still downloading", This happens on any CM-based ROM that I try, it is very consistent so I am assuming there is something in the base CM code. If I install any ROM based on stock I have never seen this issue, the phonebook download completes in a few seconds. I have also tried pairing an iPhone and a Blackberry and everything is fine.
I am wondering if anyone else has seen this issue and if anyone knows a way this can be fixed? This is my "acid test" for an acceptable rom for me so I am hoping I can get this addressed so I can move away from stock.
Thanks in advance!
Click to expand...
Click to collapse
Guess I am the only one with this issue? I just tried installing CM10 M1 but it still has the same issue. I will try some other JB-based variants to see if I can find something that likes my stereo :fingers-crossed:
Same thing happens with my Ford Sync system. This last time I turned on the auto download or auto update (forget what it's called) and somehow my address book is completely downloaded.
Sent from my SCH-I535 using xda app-developers app
OnceAMatrixMan said:
Same thing happens with my Ford Sync system. This last time I turned on the auto download or auto update (forget what it's called) and somehow my address book is completely downloaded.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks! I recently downloaded Incubus23jc's JellyWiz R3 running 4.1.1 (which I believe is a port from either T-Mobile or AT&T leak) and the address download works just fine. So the issue isn't directly JB-related. Guess I will try to submit a defect on the CM site.
Ok. I've seen that it is not possible to have Stk app running under Nexus S under normal circumstances. So I noticed that Galaxy S and Nexus S have the same baseband chip and that Galaxy S comes with Stk.apk and it works fine. So I was able to flash a Galaxy S radio image on my Nexus S, and for my surprise, the Stk didn't work.
Could someone give me a link to a Galaxy S I9000 or I9000B radio image which responds to Stk.apk requests? I've tested some, but I refuse to believe that it is not working cause of black magic... I was sure it would work So this is my last try, if someone have a Galaxy S radio which responds to Stk, I would really appreciate the image name.
Thanks!
HugoS said:
Ok. I've seen that it is not possible to have Stk app running under Nexus S under normal circumstances. So I noticed that Galaxy S and Nexus S have the same baseband chip and that Galaxy S comes with Stk.apk and it works fine. So I was able to flash a Galaxy S radio image on my Nexus S, and for my surprise, the Stk didn't work.
Could someone give me a link to a Galaxy S I9000 or I9000B radio image which responds to Stk.apk requests? I've tested some, but I refuse to believe that it is not working cause of black magic... I was sure it would work So this is my last try, if someone have a Galaxy S radio which responds to Stk, I would really appreciate the image name.
Thanks!
Click to expand...
Click to collapse
If you use CyanogenMod, STK works fine. It even initializes as you boot your phone or turn on then turn off airplane mode (you see the "default message" toast at the bottom of the screen).
polobunny said:
If you use CyanogenMod, STK works fine. It even initializes as you boot your phone or turn on then turn off airplane mode (you see the "default message" toast at the bottom of the screen).
Click to expand...
Click to collapse
I guess there's something else other than the radio image bugging communication of proactive commands. I've downloaded a CyanogenMod 10 build for galaxy s and flashed the modem.bin image on the Nexus. Baseband version is updated (can check trough logs and settings), but still the messages are not supported. I wonder what else could be interfering with proactive commands. Do you have any ideas?
HugoS said:
I guess there's something else other than the radio image bugging communication of proactive commands. I've downloaded a CyanogenMod 10 build for galaxy s and flashed the modem.bin image on the Nexus. Baseband version is updated (can check trough logs and settings), but still the messages are not supported. I wonder what else could be interfering with proactive commands. Do you have any ideas?
Click to expand...
Click to collapse
Sadly, no. I don't need STK here.
But what is your goal? I have the feeling you might be hunting high and low trying to flash a Galaxy S radio, only to get STK working, when if you tell us what is your end goal someone might chime in with better and more precise advice.
As I mentioned, CM10 already has STK.apk working (by the way STK has to be built for the correct OS version and phone, can't just swap it around). Usually you just have to set a SIM pin to "enable" it.
polobunny said:
Sadly, no. I don't need STK here.
But what is your goal? I have the feeling you might be hunting high and low trying to flash a Galaxy S radio, only to get STK working, when if you tell us what is your end goal someone might chime in with better and more precise advice.
As I mentioned, CM10 already has STK.apk working (by the way STK has to be built for the correct OS version and phone, can't just swap it around). Usually you just have to set a SIM pin to "enable" it.
Click to expand...
Click to collapse
My goal is to have the Stk running on Nexus S. For what I've searched the net, I haven't found anyone who was able to do it... You said CM10 already has STK working, but is this for Nexus S?
I didn't get what you said about setting up a SIM pin to enable it... As I see it, if the STK.apk is available in one phone (let's say motorola GB) this means the SIM is already configured to access sim menus and applications. So if I put the same SIM on Nexus S, the natural behavior would be to have Stk.apk pop up in the launcher...
The problem is that Nexus S doesn't show the app in the drawer, and the reason behind that is that the lower levels (proprietary ril) don't send specific messages. To be precise:
Frame work Stk sends a RIL_REQUEST_REPORT_STK_SERVICE_IS_RUNNING message to ril exepecting an ok answer.
What happens is that RIL respondes REQUEST_NOT_SUPPORTED.
My attempt of flashing a Galaxy S radio on Nexus was based on an idea after seeing this message being answered in a friend's GS.
HugoS said:
My goal is to have the Stk running on Nexus S. For what I've searched the net, I haven't found anyone who was able to do it... You said CM10 already has STK working, but is this for Nexus S?
I didn't get what you said about setting up a SIM pin to enable it... As I see it, if the STK.apk is available in one phone (let's say motorola GB) this means the SIM is already configured to access sim menus and applications. So if I put the same SIM on Nexus S, the natural behavior would be to have Stk.apk pop up in the launcher...
The problem is that Nexus S doesn't show the app in the drawer, and the reason behind that is that the lower levels (proprietary ril) don't send specific messages. To be precise:
Frame work Stk sends a RIL_REQUEST_REPORT_STK_SERVICE_IS_RUNNING message to ril exepecting an ok answer.
What happens is that RIL respondes REQUEST_NOT_SUPPORTED.
My attempt of flashing a Galaxy S radio on Nexus was based on an idea after seeing this message being answered in a friend's GS.
Click to expand...
Click to collapse
As I said, go to the security option in CM, enable SIM pin. That usually makes STK popup after a reboot in the launcher.
polobunny said:
As I said, go to the security option in CM, enable SIM pin. That usually makes STK popup after a reboot in the launcher.
Click to expand...
Click to collapse
I'll get my hands on a SIM with available pins to test this... I'll post back ASAP.
HugoS said:
I'll get my hands on a SIM with available pins to test this... I'll post back ASAP.
Click to expand...
Click to collapse
You don't have a SIM? You should be able to set a PIN password on any working SIM as far as I know.
So I just got my N5 yesterday, love it, way faster and smoother than my S4, but the voice dialer is the $hits....this could be a game changer for me. Any advice on other voice dialers so I can keep my N5??????
HELP!!!!!:crying:
caanda45 said:
So I just got my N5 yesterday, love it, way faster and smoother than my S4, but the voice dialer is the $hits....this could be a game changer for me. Any advice on other voice dialers so I can keep my N5??????
HELP!!!!!:crying:
Click to expand...
Click to collapse
It would help A LOT if you explained WHAT the problem is rather then saying there is a problem...... don't even know what your issue is?
for me, this works fine.
say: OK GOOGLE
say: Call ********
Phone will call ....
What's the issue?
n19htmare said:
It would help A LOT if you explained WHAT the problem is rather then saying there is a problem...... don't even know what your issue is?
for me, this works fine.
say: OK GOOGLE
say: Call ********
Phone will call ....
What's the issue?
Click to expand...
Click to collapse
LOL still upset...the voice dialer while paired by bluetooth using it my car with my Kenwood Navigation head unit DNX890HD. It just does not work well at all. It misses names, can`t find names that are in my contacts, adds digits on number dial....etc Contacts that S voice (on my Samsung Galaxy S4) would call with no issues what so ever do not work at all. It is poor at best. The issue is with the voice dialer over Bluetooth in the car...Ok Google now works just fine.
So anything I can do to get better results or another app to give me better results.
Hope that helps and adds more meat to the subject.
caanda45 said:
LOL still upset...the voice dialer while paired by bluetooth using it my car with my Kenwood Navigation head unit DNX890HD. It just does not work well at all. It misses names, can`t find names that are in my contacts, adds digits on number dial....etc Contacts that S voice (on my Samsung Galaxy S4) would call with no issues what so ever do not work at all. It is poor at best. The issue is with the voice dialer over Bluetooth in the car...Ok Google now works just fine.
So anything I can do to get better results or another app to give me better results.
Hope that helps and adds more meat to the subject.
Click to expand...
Click to collapse
It might be a kenwood related issue, It is working perfectly with the factory deck in my car.
caanda45 said:
LOL still upset...the voice dialer while paired by bluetooth using it my car with my Kenwood Navigation head unit DNX890HD. It just does not work well at all. It misses names, can`t find names that are in my contacts, adds digits on number dial....etc Contacts that S voice (on my Samsung Galaxy S4) would call with no issues what so ever do not work at all. It is poor at best. The issue is with the voice dialer over Bluetooth in the car...Ok Google now works just fine.
So anything I can do to get better results or another app to give me better results.
Hope that helps and adds more meat to the subject.
Click to expand...
Click to collapse
This sounds obvious but I thought i'd throw it out there anyways... have you gone into the settings and checked off the box that tells it to work through the bluetooth headset? It may just be using the mic on the phone which is why it's messing up so bad.
cc16177 said:
This sounds obvious but I thought i'd throw it out there anyways... have you gone into the settings and checked off the box that tells it to work through the bluetooth headset? It may just be using the mic on the phone which is why it's messing up so bad.
Click to expand...
Click to collapse
Yup it is activated...still the $hits...trying a app called klets, will see if that is any better. Do not mind paying for one if it works!!
caanda45 said:
Yup it is activated...still the $hits...trying a app called klets, will see if that is any better. Do not mind paying for one if it works!!
Click to expand...
Click to collapse
Wish I could help, but in my experience, Google's voice recognition is one of if not the best voice recognition software out there. I've used "OK Google" few times and few more times as a test and compared to others, it's excellent.
could be a possibility your BT mic just isn't picking it up..or isnt close enough.
How does it perform without bluetooth?
In Google now settings, go to voice and check Bluetooth headset. Google Now will now be used instead of the dated "voice dailer."
Sent from my Nexus 10 using Tapatalk 4
n19htmare said:
Wish I could help, but in my experience, Google's voice recognition is one of if not the best voice recognition software out there. I've used "OK Google" few times and few more times as a test and compared to others, it's excellent.
could be a possibility your BT mic just isn't picking it up..or isnt close enough.
How does it perform without bluetooth?
Click to expand...
Click to collapse
I agree on its own in Google now it is really good...but hooked up to my Nav unit and it is the voice dialer which I think is different to Google now in some aspects...is the $hits. Klets works I have bought it and it does what Svoice dos on SGS4...I am happier now, just wished the built in one worked!!
El Daddy said:
In Google now settings, go to voice and check Bluetooth headset. Google Now will now be used instead of the dated "voice dailer."
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
I will try that, thought I did but was rushed. So when hooked to bluetooth then the screen will always have to stay on or activate when I press on the phone button on the nav unit? Will give it a try.
Klets works fine, but would love to get google now...
delon97 said:
It might be a kenwood related issue, It is working perfectly with the factory deck in my car.
Click to expand...
Click to collapse
Same here...using Dodge/Chrysler's UConnect and I haven't had a single problem save for the same problem with some of my contacts not being able to be dialed using "Name, Home". It consistently boots me to that person's mobile number. That might be a google related issue or something else. Using numbers only hasn't given me any problems.
So here is my dilemma, Google now works when the phone is unlocked and through the blue tooth on the nav unit with ok google...when I press the telephone button on the nav unit it then defaults to either google voice dialer (the old crappy one) or klets with the always or just once options.
So it works sort of.....
caanda45 said:
Yup it is activated...still the $hits...trying a app called klets, will see if that is any better. Do not mind paying for one if it works!!
Click to expand...
Click to collapse
I couldn't get the phone voice dialer or my old standby voice dialer called cyberon to work reliably on the N5 and my sony mw600 bluetooth headset. Cyberon worked fairly reliably on my old galaxy nexus but not on the N5.
I really thought that there was a bug in the N5 kitkat which would hose any bluetooth voice dialer. At your suggestion I just loaded klets and wow, it seems to work wonderfully!
I need some time with it but I am very encouraged. Caanda45 I can't thank you enough for your remarks
NCguy said:
I couldn't get the phone voice dialer or my old standby voice dialer called cyberon to work reliably on the N5 and my sony mw600 bluetooth headset. Cyberon worked fairly reliably on my old galaxy nexus but not on the N5.
I really thought that there was a bug in the N5 kitkat which would hose any bluetooth voice dialer. At your suggestion I just loaded klets and wow, it seems to work wonderfully!
I need some time with it but I am very encouraged. Caanda45 I can't thank you enough for your remarks
Click to expand...
Click to collapse
NP glad it worked...I have ended up getting rid of my N5 but klets is a pretty good app. Any app that will let you try it free for 7 days is a good app in my books...
n19htmare said:
Wish I could help, but in my experience, Google's voice recognition is one of if not the best voice recognition software out there. I've used "OK Google" few times and few more times as a test and compared to others, it's excellent.
Click to expand...
Click to collapse
When I tried ok google for dialing I seem to recall there was no verification. I don't think I could rate a voice dialer as excellent without verification. I really don't want an old girlfriend asking me why I was calling her.
---------- Post added at 12:24 AM ---------- Previous post was at 12:22 AM ----------
caanda45 said:
NP glad it worked...I have ended up getting rid of my N5 but klets is a pretty good app. Any app that will let you try it free for 7 days is a good app in my books...
Click to expand...
Click to collapse
agreed. which phone did you settle on? Was it the voice dialing that caused you to switch?
NCguy said:
When I tried ok google for dialing I seem to recall there was no verification. I don't think I could rate a voice dialer as excellent without verification. I really don't want an old girlfriend asking me why I was calling her.
---------- Post added at 12:24 AM ---------- Previous post was at 12:22 AM ----------
agreed. which phone did you settle on? Was it the voice dialing that caused you to switch?
Click to expand...
Click to collapse
I didn't say voice dialer was excellent.. I said the voice recognition was excellent.
As for verification, there is no "yes" "no" verification but there is a few second delay before it places a call, during which you can cancel if that's not the number you wanna dial.
n19htmare said:
I didn't say voice dialer was excellent.. I said the voice recognition was excellent.
As for verification, there is no "yes" "no" verification but there is a few second delay before it places a call, during which you can cancel if that's not the number you wanna dial.
Click to expand...
Click to collapse
ok, I'll acknowledge your statement about the voice recognition. I just tried playing with the voice calling feature again to refresh my memory.
Many times ok google wasn't picked up. There is no voice verification yes/no as you stated and no repeat of who it was about to call. Yes there is a delay where you could kill it with touch but I saw no way to kill it with a voice command once it commenced. Having to kill it with touch completely misses the point of voice dialing.
While the name it picks seems to be accurate that's about the only useful thing I can say about it. Even then often it would pull the correct name but drop the "call" part of the command and instead do a default web search on the name.
IMO, the google now voice dialer is cute but practically useless as a serious voice dialing application.
NCguy said:
When I tried ok google for dialing I seem to recall there was no verification. I don't think I could rate a voice dialer as excellent without verification. I really don't want an old girlfriend asking me why I was calling her.
---------- Post added at 12:24 AM ---------- Previous post was at 12:22 AM ----------
agreed. which phone did you settle on? Was it the voice dialing that caused you to switch?
Click to expand...
Click to collapse
Believe it or not I got a Moto x and the notifications and touch less controls are outstanding!!! Solid phone, better speaker, no washed out picture off axis etc....The N5 is a powerhouse but as with most LG products, cheapo plastic....My S4 was better constructed.....just my opinion though...
caanda45 said:
Believe it or not I got a Moto x and the notifications and touch less controls are outstanding!!! Solid phone, better speaker, no washed out picture off axis etc....The N5 is a powerhouse but as with most LG products, cheapo plastic....My S4 was better constructed.....just my opinion though...
Click to expand...
Click to collapse
nice! what are you using for voice dialing on that device?
NCguy said:
nice! what are you using for voice dialing on that device?
Click to expand...
Click to collapse
It uses the Google system not the old google crappy voice dialer but the new one that is in the nexus 5...so basically google now..works really well even when I press the phone button on the nav system it defaults to google now through the nav mic. My N5 would use the crappy old google voice dialer until I used klets. All in all happy that I got rid of the N5.