Hello,
Problem #1: Voice Actions and Voice Dialing are not accurate, especially in French. Plus, I drive around a lot so this is significant (read: safety and fines).
Solution I have so far: installed Nuance VSuite 3.2 extracted from some Motorola phone as per http://forum.xda-developers.com/showthread.php?t=943688
The recognition works beautifully, but...
Problem #2: I can start the app with my Bluetooth headset's button, but only if the screen is on (the phone can still be locked). If the screen is off and I press the button, I'll hear the headset's speaker turn on, then off shortly after. The screen also flickers in a similar fashion. Only when I press the Power button on the phone will the app launch...
So my question: is there a solution to this delayed start/screen flicker?
Things I've tried/checked already:
-As of writing this, there are no voice recognition apps whatsoever on the market in French. (And few in English, but that's not really an option here.)
-There are phones with VSuiteApp 4.x instead of 3.2, but my attempts at making those versions work have not been successful yet. (I have: Motorola Droid X and Samsung Fascinate both stock and deodexed) The best I've managed was for those apps to start and disappear immediately. Force close didn't work?! I'm not sure if my problems are due to the app having been created for an older version of Android or missing framework files...
Thanks in advance,
Darkshado
Hey guys. I currently have the kwiboo V1 ICS rom on my Nexus S 4G. I was just playing around with the google voice recognition and found that we have a couple more things that we can do via voice commands which is pretty cool. My friend has an iPhone 4S with siri and I was noticing he has to repeat himself a lot when trying to give it commands. I was doing some research online comparing siri to androids voice commands and one of the features of ICS is that its going to have an "Open Mic" feature which keeps androids voice-input system open so that it's always listening for voice commands instead of having to press a button. Has anyone seen this in action? I was curious about it and was wondering how effective this would be/how much extra battery consumption it would take.
I don't think it's quite available yet.
mic button disabled
Hey I recently updated my Galaxy S plus to ICS using CM 9. Later I figured out my keyboard mic button is always disabled. But my voice recognition search is working fine. Any way to enable it?? plzz guys..
Solution: I have installed swype, and it seems they use a different system for voice transcription which works just fine! However this still doesn't fix the issue for people who don't like swype. But my Mom does like swype so it works out.
Hello, I just got my Mom a LG Optimus T today, and I have successfully flashed the CM10 rom for my Mom's LG Optimus T. I trimmed it and it works great. I found out that these devices can't use the google now voice function, bummer.
But this thread: http://forum.xda-developers.com/showpost.php?p=36781540&postcount=126
Says that voice can work for google now through the keyboard mic. However the stock keyboard doesn't have one, so I installed swiftkey and the mic button gives an error when I long press it. Any Ideas? The keyboard voice functionality is kind of important to my Mom, she couldn't care less about the google now voice, just the keyboard. Thanks!
Edit: The keyboard Mic button doesn't show up for either stock or swiftkey keyboard when in google now, but it shows up in browser. Both keyboards give the same full screen "Exclamation Mark in a triangle" error when mic is pressed, when it's available in browser.
Do I have to downgrade my mom to ICS and lose Project butter to be able to have voice transcription on the keyboard?
Edit: I have installed swype, and it seems they use a different system for voice transcription which works just fine!
Electriccars said:
Solution: I have installed swype, and it seems they use a different system for voice transcription which works just fine! However this still doesn't fix the issue for people who don't like swype. But my Mom does like swype so it works out.
Hello, I just got my Mom a LG Optimus T today, and I have successfully flashed the CM10 rom for my Mom's LG Optimus T. I trimmed it and it works great. I found out that these devices can't use the google now voice function, bummer.
But this thread: http://forum.xda-developers.com/showpost.php?p=36781540&postcount=126 ...
Click to expand...
Click to collapse
Now, one can (well, almost but ...) have the whole hawg!
Here is how:
Buy (will not break the bank) the voice-search-assistant app.
Buy (creepers!) the paid version of Overlay (featured on recent portal!).
1. Create an app-profile for Google Search.
2. Drag the shortcut icon to the upper right corner.
3. Select voice-search-assistant.
4. Set minimum icon size, no text, transparent background, minimum visibility.
5. Reposition at upper right if need be.
6. Set start Overlay at boot.
Now when one clicks Google Now's mic icon, one gets the voice-search-assistant instead!
(Would love/prefer to do this as an Xposed/framework module. Means learning this API and doing some serious mid-level programming. Overlay does the job well enough, no need for other apps.)
Yeah, thanks but that's not the main issue. My mom just wants to have keyboard voice functions. Which only swype can give apparently. Otherwise she doesn't care.
But furthermore, it's not even an issue anymore! A few days after getting this phone for $20 off of craigslist, I saw an ad for 2 HTC sensations for only $180! At first I thought I was top late as he posted 6 1/2 hours before I saw it, but I text the guy, emailed him, the next morning I tried calling him, then I tried calling with a different phone and he answered! I talked to him and it turns out it was a mistake to answer, he had been trying to wait and text everyone at once later that night. But because he talked to me I was able to meet him after work. I had to wait with my sister 4 1/2 hours because he went to a get together with his family but it was worth it! Now, along with myself, my Mom and sister both have fantastic phones!
But this'll still be my brothers phone until we can get him a really good phone as well. And it's awesome when running jelly bean. thanks for trying to help!
And keep your eye on craigslist! You never know what luck you'll have.
Sent from my HTC Sensation using Tapatalk 2
Ok as some of the members of this forum may know I got off to a shaky start with my Android wear watch (a Sony SW3).
I've now had it about four weeks and have over come the major problems I initially had, so I thought I would start a tread highlighting the things I love and the things I hate so others can assess if a smart watch is for them.
Firstly, what I love:
- Reading messages from Text, Email, Whatsapp and Messenger
It's so simply to just quickly look at my wrist see if I'm interested, if not I delete, if I am, may read further on the watch or if the message is to long, find my phone and continue there.
- Voice control
A really unexpected plus for me. I thought 'OK Google' was a bit of a gimmick at first, but how wrong could I have been. It's fantastic (OK, I feel a bit of a nerd saying OK Google to get it started, but that's a tiny problem). Driving and going to be late, OK google, Send text message to XXXX, then speak your message eg ' Sorry running late will be with you in 30 minutes. The translation is actually pretty accurate and it's done, you don't have to take your eyes off the road!
- It's an accurate watch, not sure where it gets it's time from but I guess it comes from the phone which in turn gets the time from the network which means no more setting, not running fast or slow. Not sure how it works when you change time zone though but I'll find that out soon enough.
- It's waterproof. Don;t forget to turn the touch screen off, but I've now been swimming with it, I regularly shower with it. Not a hint of a problem.
- Control you music system. I use Sonos around my home and I can turn the volume up and down, change track. Ok it's limited but it still an unexpected benefit.
- Control Bluetooth music with Spotify. Really a feature best used in the car. There's an app that will fire up Spotify on your phone which in turn will use the blue tooth audio to connect to your car. No more digging around to find you phone, unlock it, fire up spotify, find your play list etc etc etc.
- Incoming calls. Nice feature as I can decide if I want to take the call without having to find my phone to see who's calling.
What I hate (ok hate is a bit strong, but)
- The UI I think is not properly thought through You have al these options, tilt to wake, tilt to scroll through cards. Clumsy at best and a battery drain at worst (tilt to wake particularly) Even the touch screen to wake is not that cleaver as it can be operated but a lot of things touching the screen not just me, eg a sleeve, particularly one that is damp
- Voice control Ok I know I've said above that voice control is fantastic but it has one major down side, it needs internet connectivity. If it doesn't have it, it just doesn't work! Wish it would use the processing power of my phone to process voice.
- Wifi, ok I accept this is probably a bug, but wifi doesn't currently work properly, for some reason it will drain all the all the battery for no apparent reason and it does it very fast. I've now turned it off and only turn it on on the occasions because it's great to have full functionality
- Screen, the screen is fine, but that's damming it with faint praise. I would really like to see a higher quality screen and a little bit bigger would be nice.
- Incoming calls. When rejecting a call, it would be good to be offered a 'rejection message' that is sent via text giving a reason for the rejection.
When rejecting calls you can slide up instead of left por right swipe ano it will show up predefined messages that it will automaticly send to The caller.
::enviado do meu oneplus one via tapatalk::
My complaints (1 month usage) is the app tray feels bloated. Not every app needs to be displayed. Not every app has options set through the watch. Also the layout feels cramped to me. I would prefer some options (icons only, 1x2, list mode, 1x1 mode, text/no text, recent shortcuts at top on/off, etc.)
2. Embedded speaker for taking quick calls without digging for your phone last minute. 1 problem a watch introduces is that your phone starts to be left behind. I now leave my phone on the counter while I buzz around my home. Phone rings, its a mad dash down stairs to find my phone.
3. Some sort of keyboard. I'll take the old school T9 input. Just let me type a few things.
player911 said:
My complaints (1 month usage) is the app tray feels bloated. Not every app needs to be displayed. Not every app has options set through the watch. Also the layout feels cramped to me. I would prefer some options (icons only, 1x2, list mode, 1x1 mode, text/no text, recent shortcuts at top on/off, etc.)
Click to expand...
Click to collapse
Download wear mini launcher from the playstore. It's a brilliant replacement that let's you customise the watch to how you want it.
I totally agree with you. I also use Android wear for
Reading messages from Text, Email, Whatsapp and Messenger
Voice control
Agree with some points according to my experience with my old android wear.
Hope my new one will work better.
My most of my complaints are solved with the Asus ZenWatch2. It is a solid upgrade to the LG G Watch. Once Marshmallow drops, we'll get a new app tray and speaker support (Zenwatch2 and Huawei) for calls.
I tried the alt launchers and it doesnt replace the stock launcher but runs over top of it. So it just adds to the chaos. However after the nostalgia wore off, I dont really use apps thus dont need to go into the app drawer.
Keyboard: try FlickKey
player911 said:
3. Some sort of keyboard. I'll take the old school T9 input. Just let me type a few things.
Click to expand...
Click to collapse
Try FlickKey Keyboard for Wear. It adds a keyboard to any app that wants to call it. Right now, that is limited to Wear Messenger, Coffee for Wear, and K-9 for Wear - you need one of those messaging apps to be able to use it. BTE, FlickKey is not a T9 style keyboard - it works better than that.
I have tried various keyboards. What I was referring to was an option, by default, in Android wear to have a keyboard input. I don't use any of those apps, thus having a keyboard right now would be irrelevant.
What apps would you like to use a keyboard with?
player911 said:
I have tried various keyboards. What I was referring to was an option, by default, in Android wear to have a keyboard input. I don't use any of those apps, thus having a keyboard right now would be irrelevant.
Click to expand...
Click to collapse
I certainly agree that users should be able to decide for themselves if they want to use a keyboard or not, and which one they want on their smartwatch. What apps would you like to use a keyboard with? FlickKey can be added to any app with just about 15 lines of code. So message the dev who makes the app you want FlickKey in and let them know they can easily add it for free.
I find Android Wear to be very useful - when it works. Performance on my original 360 hasn't been very consistent either but I'm sure the S400 watches fare much better. Seriously though - every Android OEM needs to switch to AMOLED as soon as possible since it's much more suitable for smartwatch use.
I have installed AW on a Samsung Gear 2 (ported to the watch by @biktor_gj) and it runs really great !
Much much better than the default Tizen where it comes with normally.
Since I am using AW, I'm really hooked on it.
I love to be able to navigate with my watch and/or get notifications (from Google Maps) about any traffic jams or hold ups on my route.
I love to be able to use my voice to respond to whatsapp messages or even use my voice to make a new message without even holding my phone.
Really looking forward to the upcoming version (Marshmellow?), which suppose to have speaker support, because the Gear 2 has a build-in speaker.
So that means I can make calls too again from my watch (which is now only possible in Tizen, but not AW).
Hangouts and Messenger and Email (I know there are email clients that support wear and flickkey). I doubt Hangouts or Messanger will get it support.
Ok guys, I am pretty spent in terms of ideas here, I hope somebody can help. I'm not sure if this is a cyanogen thing or a Oneplus thing but here goes:
So I just got the Oneplus One and it's pretty damn nice, save for the twitchy Wi-Fi and BT, but they work fine most of the time so I'm fine with that.
However I am having a really strange issue. I have been using ExDialer on my old Galaxy Nexus because its stock dialer was crap. At this point I am married to exDialer. I've been using it for so long and it is so good and don't feel comfortable using anything else.
Problem is that the Oneplus never asks me about changing the default dialer after I install it. And once I try to call a number from it, it jumps to the stock dialer, with the phone number typed in instead of ringing the contact directly. And apparently there are no defaults. Neither the stock dialer nor the ExDialer are set as default, according to their app info.
So far easy, peasy, right? I downloaded a 3rd party app and forced ExDialer to be come default. And no joy. Still the same thing. When I try to call a number, it goes to the stock dialer and I have to click the dial button there as well in order to call.
I tried disabling the stock dialer entirely and when I try to make a call from EX, it apparently still wants to do the same thing as before and tells me the dialer has stopped working and to go ** myself.
And apparently it's not just ExDialer. I get the same issue when I try to call a number from Google Now, by voice command or by typing, as well as the Google voice dialer app - again, it does its thing says "calling X"" and then goes to the stock dialer where I am required to press the call button again. This one is pretty annoying too because it pretty much precludes me from being able to dial numbers by voice commands from my BT headset. Each time, I have to get the phone out of my pocket and press "call" on the stock dialer to finish the dialing.
I never got any of those issues with the Galaxy Nexus... both ExDialer and Google Now dial numbers directly and don't do this. So any help would be appreciated.
Thanks!
EDIT: Probably should have mentioned that this is Cyanogen 11.0. I am holding off on upgradingt to Lollipop for the time being. So this is the stock Android dialer in Kitkat that we are talking about.
The issue persists after updating to CM12.1 . Does anyone have any ideas?
I should mention that after my initial post I found out that if I dial numbers with +359 (I am in Bulgaria) the issue doesn't happen and they are dialed directly, however if I try to dial the same numbers, starting with 0, which should be the normal way to do it, when dialing numbers in my own country, it always happens. If I use 0 the stock dialer pops up and I have to press "call" again and the calls go out. And if I use +country code, instead of 0, they are dialed directly from EXdialer or GoogleNow as they should be.