Related
I have purchased the CallRecorder (from skvalex), the program can be trigger by a phone call, but it did not record anything.
we will have to wait for the kernel dev's to see if they can come up w/ a patch.
bought callrecorder too.
Google Voice lets you record calls.
i'm aware of that.
but there are humans outside of the US that got the galaxy nexus as well.
has anyone tried total recall from killermobile.com
they have solutions for the gs2, so am wondering if it may work for the gn?
biswasd said:
has anyone tried total recall from killermobile.com
they have solutions for the gs2, so am wondering if it may work for the gn?
Click to expand...
Click to collapse
I have tried their Total Recall. It records only caller's side like all other call recording apps I tried.
EDIT:
Just noticed what I wrote here. I meant your side (side of the person who installed the app.).
Ill wait for one to be included in a custom rom.
Had it on one of the Darky 9.0 roms back on the i9000. Worked great.
Desperately desires this as well...
Will we receive kernel with 2way recording included?
Anyone has a clue if this could be eventually solved with enabling some feature in kernel config, or is this actually firmware or hardware issue?
Almost sure it is not so simple to be solved with simple kernel recompilation... But since I am pretty new here (android land), I hadn't enough time to get know things, evaluate enviroment etc.
I'd also love to have the call recorder from skvalex working on this. I'm holding off on getting the GN until this feature works.
Work in progress... http://forum.xda-developers.com/showthread.php?t=1422779
Sent from my Galaxy Nexus using Tapatalk 2
I am experiencing problem voice dialing from bluetooth headset on jellybean roms on the vzw gNexus.
On any non jellybean rom i can say... for example... "call mom on mobile" and it will, 95% of the time call mom. On jelly bean if i say the same phrase, it will 100% of the time return "calling tim, on mobile". In fact, it doesn't mater what contact name i say, it it ALWAYS suggests the wrong contact.
I thought, ok, lets try google now. If i open google not, tap the mic(voice input) option, and say, "call mom on mobile" it will fill in the search box with "call mom on mobile" so its understanding me correctly, then below that is says
"did you mean call tim on mobile"
and lists tim then mom in a list of numbers to call.
I spent over 3 hours trying to get this to work right, flashed every JB rom i could find, wiped and rewiped and reflashed. Finally went back to ICS and retested, sure enough it works awesome on ICS.
Can anyone atleast try to replicate this problem, or is anyone already experiencing it?
THanks!
Bump
Bump again.
Almost 50 views, if anyone using a bluetooth and Jellybean can at least try it and let me know if it happens to you or not. Thanks
Works fine for me.
Sent from my Galaxy Nexus using xda premium
greyphil said:
Works fine for me.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
what phone and rom are you using? Looks like GSM, and OTA.
I just checked it again and i got:
"Call mom on mobile"
**Did you mean -Mark**
Mark
Mom
Kathy
thats from google now.
If it activate the voice dialer directly from the bluetooth, it will call bob, mark, tim, or funniest a business name that starts with "borderview". Even after 20 tries it will not dial "mom" lol.
Alternatively, I tried dialing mark, tim, bob, and borderview directly, and after 10 tries each, they will not dial if i try to dial them, only if i try and dial mom. lol very frustrating.
Yes stock gsm JB with root. Does it only happen with your headset? If so, try a different BT headset.
Sent from my Galaxy Nexus using xda premium
It happens using a $150 bose headset, as well as a $20 plantronics.
If it don't use the bluetooth i still get terrible suggestions, such as..
"call mom on mobile"
Did you mean call tim?
Tim
Mom
Mark
wtf???
That's weird. Only thing I'd try now is flashing a different JB rom, but I can't really imagine that being the problem. Have you let someone else try it? Maybe it is you after all.
In have tried 3 different roms, and have been using the voice dialer since android 2.1 on over 10 devices. Also it works flawlessly on ISC using the same hardware. Is anyone able to successfully Bluetooth voice dial on jelly bean on a vzw gnexus?
Sent from my Galaxy Nexus using xda app-developers app
I just flashed my Sprint Nexus to JB last night and have exactly the same problem. I hadn't tried any calling on ICS before I flashed, so I can't compare on the same phone.
I just came from an Epic 4G Touch that used Vlingo, and it was always about 95% accurate. I hate to step backwards, but I may have to switch back to that.
Why can't anyone mimic the old MS voice dial where it asked for confirmation before dialing? If I said, "Call mom on mobile", it would ask, "Call mom on mobile?" I said "Yes" and it would dial.
The way it is now goes against all safety concerns for hands-free driving. Now I have to look at the screen as it starts to dial and madly grab at the End Call button when it guesses the wrong name to call.
JimSmith94 said:
I just flashed my Sprint Nexus to JB last night and have exactly the same problem. I hadn't tried any calling on ICS before I flashed, so I can't compare on the same phone.
I just came from an Epic 4G Touch that used Vlingo, and it was always about 95% accurate. I hate to step backwards, but I may have to switch back to that.
Why can't anyone mimic the old MS voice dial where it asked for confirmation before dialing? If I said, "Call mom on mobile", it would ask, "Call mom on mobile?" I said "Yes" and it would dial.
The way it is now goes against all safety concerns for hands-free driving. Now I have to look at the screen as it starts to dial and madly grab at the End Call button when it guesses the wrong name to call.
Click to expand...
Click to collapse
Im glad someone finally responded and said yes i have this problem, or no i use this feature and it works every time.
THis is a huge concern and i feel its only happening on the ported(CDMA) roms.
Can anyone else confirm this on a toro or toroplus, and confirm that this is not an issue on GSM gnexus's?
Thanks!
urushiol said:
Can anyone else confirm this on a toro or toroplus, and confirm that this is not an issue on GSM gnexus's?
Click to expand...
Click to collapse
Fully stock 4.1 GSM Galaxy Nexus, no issues with voice-dialing any name.
UnknownFearNG said:
Fully stock 4.1 GSM Galaxy Nexus, no issues with voice-dialing any name.
Click to expand...
Click to collapse
This makes me feel very strongly that the issue has been caused by something in the porting process. I will PM on of the devs. and see if he can reproduce it.
i am also having this problem on my CDMA nexus with JB. Everytime it's not even remotely close to properly detecting my call request.
I absolutely love the cyberon voice dialer because it works and it has verification.
Unfortunately, under JB when you press the dial button on the bluetooth headset the google now voice dialer overrides my cyberon voice dialer. The only way to make cyberon work is to completely disable google search. This completely disables all the new voice command support and google now as well.
Basically 3rd party voice dialers are no longer compatible!
No, the built in dialer is still unusable especially without verification.
For me, I've always had absolutely horrible results when using voice dial initiated from the Bluetooth earpiece (two different Jawbone Icons, three different Android phones, Eclair through Jelly Bean, official or custom ROM.)
Using voice search, Google Now, JB voice typing, or Dragon with Swype, it's perfect..
Sent from my Galaxy Nexus using xda premium
Can the long button press be changed from voice dial to voice search? (I think those are the right terms.) Voice search understands and dials much better. Plus, it sucks to be limited to just dialing from the headset.
kynolin said:
For me, I've always had absolutely horrible results when using voice dial initiated from the Bluetooth earpiece (two different Jawbone Icons, three different Android phones, Eclair through Jelly Bean, official or custom ROM.)
Using voice search, Google Now, JB voice typing, or Dragon with Swype, it's perfect..
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Cyberon is awesome. I wouldn't use a voice dialer without confirmation. I don't want people calling me back because my dialer got it wrong. Sometimes this can cause serious problems. If google adds a confirmation option that's when I'll give them a serious try. I've been told even the iphone voice dialer has confirmation.
UnknownFearNG said:
Fully stock 4.1 GSM Galaxy Nexus, no issues with voice-dialing any name.
Click to expand...
Click to collapse
Same.
martonikaj said:
Same.
Click to expand...
Click to collapse
Are you both dialing through bluetooth? Honestly it hasn't got one right for me yet. Not one where cyberon is dead on.
Hi I have two issues with the GN2.
1. I use Outlook with about 1500 contacts and the voice dialing over bluetooth is very slow and seems to not be as accurate as it could be, and wastes steps in getting to where it starts dialing the call. I came from a Lumina 710 w/Windows 7.8 and there is no comparision to how well windows voice dials over bluetooth as compared to the GN2. It's almost a deal breaker and I might return within the 14 days. A good answer or remedy to make it more accurate and speed it up would help.
2. I am using "Record My Call" and it will only record the "incoming" portion of the call when calling with bluetooth, not my side, but is very clear and loud for the other person. I can record both sides of the call if I don't use bluetooth, but the recording quality is not as good. Is there any work around to get my side of the conversation recorded over bluetooth? Thanks.
Ken B
Well, I have my return authorization code and am returning the Note II today. Wish the voice dailing over bluetooth would have worked better because otherwise, this phone is great. Ken B.
Outlook+windows mobile=good
Outlook+google android=bad
Gmail+google++android=good
Change phones, or port contacts, me id choose the later
Android for life
What bluetooth headset r you using? Might be a compatability issue in the bluetooth stack
Sent from my SGH-T889 using Tapatalk 2
Ken B said:
Well, I have my return authorization code and am returning the Note II today. Wish the voice dailing over bluetooth would have worked better because otherwise, this phone is great. Ken B.
Click to expand...
Click to collapse
Working fine on mine. S Voice working flawlessly, have you tried a different bluetooth headset?
Sent from my SGH-T889 using xda premium
Rhiannon224 said:
Working fine on mine. S Voice working flawlessly, have you tried a different bluetooth headset?
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Hi Rhiannon, I'm using a Plantronics Pro Voyager and it is top of the line as far as I can tell. I did receive the Lumina 810, and it is just as accurate and fast as the Lumina 710 I had before or faster in voice dailing. No comparison at all with the Note II, and I really think it has to do with the "guts" of how S voice works with all the contacts I have. I think that if a person only had a hundred or so contacts S voice might work fast and accurately, but for 1200 contacts and multiple numbers per contact, it really bogged down. Maybe next phone will be Android, but for now, I will stick with Windows. Thanks.
I havent tried record my call yet im using callrecorder for root users, and I have a cheep jabra. Svoice works flawlessly
Sent from my SGH-T889 using Tapatalk 2
prepaidguy9081 said:
I havent tried record my call yet im using callrecorder for root users, and I have a cheep jabra. Svoice works flawlessly
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Using this recording over normal phone works perfect use api recording. Under standard api sertings, set bluetooth recording to voice communications, and two way recording over bluetooth will work. U also need to tick the recorde over bluetooth box
Sent from my SGH-T889 using Tapatalk 2
I have been searching everywhere and have not found a solution to this, so I apologize if I missed it somewhere. As I've learned and have read from others, S-Voice is crap! Google Now is much MUCH better at voice recognition, particularly with names. The problem is, over bluetooth, my voice commands are only picked up by S-Voice. Google Now gets stuck at the "Initializing" then says "Didn't catch that" and closes. I've gotten it to intermittently work with Utter!, but I can't rely on that. Google Now works great over headphones or from the phone itself. It's just over Bluetooth when it doesn't work. After researching I'm almost convinced Samsung (or Vlingo) set it up that way; it's as if the mic is disabled with any app other than S-Voice. My question is, has anyone figured out how to get Google Now, or any other voice app for that matter, to be recognized over bluetooth?
I'm running stock JB with root (fyi, this was going on before I rooted). I know it'll probably work just fine if I flashed CM10, but I actually like the setup I have.
Edit: After looking more, I found this thread. I tested out turning off the "Media Audio" and Google Now works, but in further investigating when I click the button on my bluetooth, it's the voice dialer that pops up and that is what doesn't work, not Google Now. I can't see, to figure out how to get Google Now to show up and not voice dialer.
Edit 2: I forgot to mention I'm using a Motorola Roadster bluetooth speaker, but I don't think that's the problem.
Same issue here. Exists on every rom I try. Bluetooth in general is buggy as heel on the S3. It's really disappointing. I don't see many answers here on XDA...
Same here and I am on a new s2 ROM sbean v12 any fix would be great
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Try going into google voice search and downloading the language you want to use
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Before selling off my Galaxy s3 i took this s-voice apk and installed it on my ONE. I am on cognition 0.6. I just clicked on the apk and installed it.
http://www.mediafire.com/download/cp88w0rdog805d8/S-Voice_Android_phone[1].apk
Proof:
What doesn't work:
. Setting alarm
What Work's:
. Navigation
. Weather
. Opening applications
. Dialing contacts by name
Note: I am not an application developer/modifier. Just wanted to share what i found with my buddies here. Please feel free to modify the apk if you intended to. Install at your own risk.
Awesome can anyone else confirm this working with out any negatives?
Sent from my HTC One using xda premium
U can't access the settings from what I can tell
Sent from my HTC One using xda app-developers app
Working on my HTC One internationnal with french language system.
Crashing when I want enter in settings and don't work with screen is off, but that apk is appreciate. :good:
I can confirm it works on my At&t HTC One running the Viper 2.1 ROM.....
I used it to:
Place a call
Send a text
Turn on Wi-fi
Turn off Wi-fi
Turn on Bluetooth
Turn off Bluetooth
The animation doesn't work well (that shows it's picking up your voice when requesting something), but it does register your voice pretty well.
Gonna try it later with my BT ear piece to see if I can get it to be the default "voice" app when I push the button on my ear piece, because the stock HTC One voice dialer stinks.
Just going to ask if anyone has had any issues with S-Voice causing Wifi not to work?
I really like S-Voice and have used it on every custom HTC One ROM I've had. I mainly use it with my bluetooth headset to make calls.... But after using it, I have issues connecting to my home Wifi. I can't say for sure it's S-Voice, but I've tried about 5 different ROMS in the past 3 months and have had wifi issues on every ROM after a short time, and this is the only app that has been consistent on all 5 ROMs, so I was wondering if anyone else has had wifi issues?
By issues, what I mean: It shows I'm connected, but doesn't work. The only way I've found to fix the issues is to dirty flash the ROM or wipe and fresh install.
I cannot get this to recognize my voice? Any more instructions? Thanks