Hello,
Is Sony SmartWatch compatible with Galaxy Note 2? Has anyone tried using it? I'm planning to buy one, is it worth or not?
Thanks!
Yeh I'm using it, it works great, fully compatable.
Sent from my GT-N7100 using xda premium
jadaress1 said:
Yeh I'm using it, it works great, fully compatable.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Hi,
Do you have standard or custom rom installed?
I use the omega (3.0), no connection possible (not detected in BT).
nevermind the above.
I reset the watch (15 secs button press) reinstalled all smartwatch software and it works perfectly
Sony Smartwatch MN2 call handler app issue
Hi
My friend bought a Samsung Galaxy Note 2 and i tried to connect the Sony SmartWatch MN2 of mine with it, and its paired perfect, every thing is fine with it but when there is a call i can only find the decline button in smartwatch no Answer button, so is the same thing happening with you ??
Is there any option to make the answer button activate, or it is not working only for me ??
And what about the music App ??
Please Help me !! as i wanted to buy Note 2, but dont want to waste my SmartWatch MN2
ShawkatAlam said:
Hi
My friend bought a Samsung Galaxy Note 2 and i tried to connect the Sony SmartWatch MN2 of mine with it, and its paired perfect, every thing is fine with it but when there is a call i can only find the decline button in smartwatch no Answer button, so is the same thing happening with you ??
Is there any option to make the answer button activate, or it is not working only for me ??
And what about the music App ??
Please Help me !! as i wanted to buy Note 2, but dont want to waste my SmartWatch MN2
Click to expand...
Click to collapse
if the sony smartwatch is anything like my motorola motoactv, then the answer button only pops up if you have headphones connected to the watch itself. if no headphones detected, it will default to decline.
ngr.hd said:
Hello,
Is Sony SmartWatch compatible with Galaxy Note 2? Has anyone tried using it? I'm planning to buy one, is it worth or not?
Thanks!
Click to expand...
Click to collapse
It works, but not flawlessly. There's an issue with the OS that can activate talk-back (or parts thereof). It only comes into play if you install some of the third-party notification apps, like Watch It (really good). It can be fixed permanently (in a non-ideal why) or temporarily fixed (less convenient but does not require disabling Engines). You'll know when you've got this issue, because your phone will unexpectedly say to you "the folder is opening..." when you open a folder. It's a minor irritation, but it gets on your nerves very quickly.
The watch itself works very well with my Note 2. Never dropped connection so far, seems to reliably get notifications (I have actually started to turn some off - as I get more than I thought I did!).
I like how it works with my phone. I see the Smartwatch as an evolutionary step to a decent version, which hopefully Sammy or Google will release. And at $100, you can't really go wrong.
Quite a few apps, and one or two of the paid ones are worth it, but mostly the free ones will do you just fine.
Hyppy New Year
wizlon said:
It works, but not flawlessly. There's an issue with the OS that can activate talk-back (or parts thereof). It only comes into play if you install some of the third-party notification apps, like Watch It (really good). It can be fixed permanently (in a non-ideal why) or temporarily fixed (less convenient but does not require disabling Engines). You'll know when you've got this issue, because your phone will unexpectedly say to you "the folder is opening..." when you open a folder. It's a minor irritation, but it gets on your nerves very quickly.
The watch itself works very well with my Note 2. Never dropped connection so far, seems to reliably get notifications (I have actually started to turn some off - as I get more than I thought I did!).
I like how it works with my phone. I see the Smartwatch as an evolutionary step to a decent version, which hopefully Sammy or Google will release. And at $100, you can't really go wrong.
Quite a few apps, and one or two of the paid ones are worth it, but mostly the free ones will do you just fine.
Hyppy New Year
Click to expand...
Click to collapse
Actually i just wanted to know that the apps for smartwatch are perfectly working with Note 2 or not, as i tried the call handler app in smartwatch with note 2, then i find that there is no accept button on smartwatch to accept the call only decline button is there and also find the issue with the music app. So the issue is just with mine or every one facing the same . If you are facing the same issue then is there any way to get rid of this.
Please please please reply.
ShawkatAlam said:
Actually i just wanted to know that the apps for smartwatch are perfectly working with Note 2 or not, as i tried the call handler app in smartwatch with note 2, then i find that there is no accept button on smartwatch to accept the call only decline button is there and also find the issue with the music app. So the issue is just with mine or every one facing the same . If you are facing the same issue then is there any way to get rid of this.
Please please please reply.
Click to expand...
Click to collapse
The SmartWatch is not fully compatible with the Note 2 for the phone answering App. It only works fully with Sony phones. There is no accept-call option in anything other than Sony phones.
Regards.
Considering you probably will want to take the phone out of your pocket before answering it, I don't see that as a real issue. "watch it" (and other programs that use accessibility settings) clashes with some other settings on the phone causing unexpected voice feedback and disabling the continuous input on the stock keyboard.. Other than that its fine..
joshofbass said:
Considering you probably will want to take the phone out of your pocket before answering it, I don't see that as a real issue. "watch it" (and other programs that use accessibility settings) clashes with some other settings on the phone causing unexpected voice feedback and disabling the continuous input on the stock keyboard.. Other than that its fine..
Click to expand...
Click to collapse
Can we control our music player functions like play/pause,next,previous,forward-rewind also how is the battery backup with continuous use. I am also thinking of buying this product. Also does it have a earphone audio out port?
liondroid said:
Can we control our music player functions like play/pause,next,previous,forward-rewind also how is the battery backup with continuous use. I am also thinking of buying this product. Also does it have a earphone audio out port?
Click to expand...
Click to collapse
Yes you can control music: start/stop, last/next, volume up/down.
No, there is no earphone port (use bluetooth headphones - who needs cables?)
I have found the watch controls music flawlessly, albeit not very conveniently in all honesty. Personally, I use the watch more to screen incoming messages and notifications. I don't try to do anything too fancy as it's easier to just use the phone.
On the subject of incompatibility with the TTS engines, there's no doubt this is an inconvenience, but not a great one. What happens is that the Note II (and I think other Android phones) starts talking to you when you don't want it to. For me, the biggy was it speaking out aloud "the folder is open..." (or "...closed") whenever I opened/closed a folder containing Apps. To say the least, it's distracting. If you disable the TTS engines (as I have done, undone, redone etc.) to fix the "folder is open..." issue (which fixes it for me, anyway) then you lose "DRIVING MODE" capability (which I rarely use) at least, and probably other speech apps too. The good news is that Navigation still works fine, even with the Samsung and Google TTS engines disabled. This is clearly not ideal, but only Google can fix it at the OS level, and they seem to be in no hurry at all.
I still think the Sony watch is a good product, as it allows me to receive and screen emails, RSS, tweets and to read them discreetly. It's much less distracting (and much less obvious, e.g. at meetings) than trying to read a phone.
I do still hope Samsung looks at this market though, as they will clean Sony's clock if they ever launch a similar product.
wizlon said:
It works, but not flawlessly. There's an issue with the OS that can activate talk-back (or parts thereof). It only comes into play if you install some of the third-party notification apps, like Watch It (really good). It can be fixed permanently (in a non-ideal why) or temporarily fixed (less convenient but does not require disabling Engines). You'll know when you've got this issue, because your phone will unexpectedly say to you "the folder is opening..." when you open a folder. It's a minor irritation, but it gets on your nerves very quickly.
The watch itself works very well with my Note 2. Never dropped connection so far, seems to reliably get notifications (I have actually started to turn some off - as I get more than I thought I did!).
I like how it works with my phone. I see the Smartwatch as an evolutionary step to a decent version, which hopefully Sammy or Google will release. And at $100, you can't really go wrong.
Quite a few apps, and one or two of the paid ones are worth it, but mostly the free ones will do you just fine.
Hyppy New Year
Click to expand...
Click to collapse
I have this exact issue and its driving me nuts!!!!
How do I turn off the 'open folder, close folder' talk back setting??
I am so glad someone else has this problem, thought i was going crazy.
BazzaR22 said:
I have this exact issue and its driving me nuts!!!!
How do I turn off the 'open folder, close folder' talk back setting??
I am so glad someone else has this problem, thought i was going crazy.
Click to expand...
Click to collapse
Heh. No it's very common. I know of two fixes: one is TEMPORARY, but does not require you to disable any apps; the other seems to PERMANENTLY fix the problem, but it results in disabling TTS apps. You have to figure out which of these two evils is the lessor:
Temp fix - go to setting-> applications and find the two TTS Aps (Google and Samsung). Clear the cache on both. It temporarily fixes the problem (on my Note II anyway). Bad news: it comes back, seems to be random. I have never figured out why, and now I don;t even try...
Permanent fix (the one I have today). Go to settings->apps and DISABLE said google and Samsung TTS engines. Problem goes away, but you may lose some important functionality (I haven't - Driving Mode is killed, but I don;t use it anyway). You can always re-enable these apps, by going to settings->apps, scrolling all the way to the bottom and re-enabling them. I have tried re-enabling, but this little bug comes right back after a random delay, so now, I just accept it.
Regards,
Andrew
PS - don't blame Samsung, blame google. This is their problem.
PPS - all SonyWatch notification apps seem to trigger this - on my Note II anyway. I tried 'em all.
Had to resurrect this thread, are you guys talking about the smart watch 2 or 1? I am thinking of buying smart watch 2 atm.
Hello I have noticed that ok Google is not recognizable from any of my devices either my smartwatch 3 or my note 3 I have already tried to set up ok google but it can recognize my voice I have tried to teach to my phone the sound of my voice but nothing I can't even pass the first object of learning any idea how to fix this problem? Thanks
Sent from my SM-N9005 using XDA Free mobile app
o-ellinas said:
Hello I have noticed that ok Google is not recognizable from any of my devices either my smartwatch 3 or my note 3 I have already tried to set up ok google but it can recognize my voice I have tried to teach to my phone the sound of my voice but nothing I can't even pass the first object of learning any idea how to fix this problem? Thanks
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure it's your devices and not you? I find "Okay Google" to be awkward to pronounce, especially several times in a row, due to the "k" and double "g" combo. Wish we could change the hotword. I just touch the watch...find this to be easier and more reliable. Once I do that, I find the boice recognition to be surprisingly accurate, even with names, foreign-sounding places, etc. Does your watch recognize voice if you activate it by touch? If not, you may have a microphone problem. Also, if you have an accent or something, or a stutter, I'd try having someone else say it to see if it's the device or it's you. And also, make sure the watch is lit up first and out of ambient mode. I don't think it works when the watch is in low power mode. As for not working on the phone, I had that issue on the Note3 as well when using Nova Launcher, worked fine in TouchWiz. But I'm pretty sure the watch keyword detection is not dependant on the phone, since I can activate mine even when it's disconnected from my phone.
I'm having issues with my OK Google too. It's like my watch microphone isn't working. I can't do any voice dictation into the watch. It just says "Sorry didn't catch that" when I talk to it. It worked at one point and seems to work sporadically. Now it doesn't work at all.
Not sure for how long but I think it's something like 1 week that voice commands don't work any more for me.
They are opened as web searches instead.
eg. I used to say "OK Google, set a timer for 5 minutes" and the timer would start. Now it opens web link suggestion...
Same with most other voice commands that used to be really useful.
Anyone having same problem?
Hi!
I bought one sony sw3 3 days ago, and have the same problem...I say the voice comands and it always do the search... anyone solved this? In my note 2 the comands are working fine, like call someone, send a text...
In the watch it always makes the search sugestions.
Thanks
Hi Everyone. I hope you could help me with my situation.
I had the watch about a month now. It was working nicely till a couple of days ago, the ok google stopped working.
When I tap the screen twice, there is a red G speak now. I cant tap on that icon. When replying a sms, the watch doesn't go into the voice recognising mode. I also tried sync with another phone.
I tried resetting to factory default. Reinstalling android wear and moto connect. Still doesn't work. I even tried the settings in Google settings, re recognising the ok google..
Running out of options.. Please help
When the red G Speak now appears do the following:
Speak.
This is the new design since Wear 2.0 Update
I spoke ...
but nothing happens...
Ferderico said:
I spoke ...
but nothing happens...
Click to expand...
Click to collapse
Strange, could your microphone have something in the little hole?
i doubt that something is stuck in the little hole at the 9 o'clock position.
cos if i tap on Speak Now - it should have some bars which emulates a sound equaliser... but in my case, there isnt.
So i suspect is a setting. ... sigh..~ btw i am using Samsung Note 4
Ok, excuse me for my upper post.
But without the further infos you have now given, i could not resist to write this.
Test the microphone with an other app.
SleepAsAndroid, LED Music Controller or any soundrecorder which uses the moto360 microphone.
Have you rooted your Samsung and are you restricting apps with xprivacy or a similar program?
If the sound test fails I think your microphone is broken...
Try this. My problem was that "OK Google" only working from Voice Settings Screen using Moto 360 with my Samsung Galaxy S4 running Lollipop. I could not get the "OK Google" feature to work anywhere EXCEPT when I had the SETTINGS/MY DEVICE/LANGUAGE AND INPUT/GOOGLE VOICE TYPING screen open on my phone. Turns out that you have to have the GOOGLE NOW LAUNCHER as the home screen software. It will not work with the TOUCHWIZ HOME as the home screen software. To change this, go to SETTINGS/MORE/DEFAULT APPLICATIONS/HOME and select GOOGLE NOW LAUNCHER.
Static sound coming out
I am having the same issue. Also I am using a custom rom for note 4. I have tried the solution above and it doesnt work. I installed the "wear audio recorder" app and I only hear static sound... Is there an app or something to see if the communication between components working?
On my N910V running VRU2CPF3 CM13.0-20160724, I have noticed a very strange behavior with the Google Now app (recently re-branded as simply, the "Google" app). Immediately after a phone call (and during other circumstances I haven't identified precisely yet), the Google app will lost the ability to "hear" me, even if I press the microphone button and start talking. The "ok Google" function doesn't work during the issue either, nor can I retrain the ok google voice model because it plain doesn't register any mic input. I can make calls and people hear me fine, and I can record audio on my camera, so my microphone is working.
The issue always goes away if I reboot, but eventually comes back, even if I haven't made any calls. On one occasion, I got the mic function for the Google App back after opening my phone app, then lost it after closing my phone app. On another occasion, I got the mic function back for the Google app after uninstalling Google Chrome and Chrome Beta (per this post). I was also able to get functionality back once by plugging in an external headset and then unplugging it, and another time by force killing all open apps. All of these "fixes" failed to fix the issue this time around - strange, right? Again, reboot always gives a temporary fix, and a phone call usually (not always) causes the issue to occur. I have found at least one individual with the same issue (khalil) here
I have tried a fresh install of the system, and the issue seems to go away for hours or even days at a time, but always comes back. I froze every user installed app on my phone using Titanium backup to see if an app was the issue, but the issue persisted. However, the issue does not seem to occur when booted into safe mode (which screams of software problem). I am currently in the process of reflashing a blank system to see if the issue persists without any user apps.
This behavior is not specific to this operating system; I had a similar issue when I was on stock unrooted 5.1.1. I did not notice the issue on Jasmine rom running 6.0.1, but I also didn't run it for very long. I seem to recall having a similar issue with my Galaxy S3 on CM11 (though it was a while ago so I can't confirm the truth of this!), so I suspect that something about my setup is to blame, rather than the hardware.
One more juicy tidbit: force uninstalling the google app fixed the issue for a day, then the app started force closing on launch, and no amount of finagling would stop the force closing. For the record, I've flashed google apps mini from opengapps.
I don't know what tools to use for proper logging of hardware - ie, when an application has control of the mic or not. I suspect that the issue is coming from improper ending of microphone use state in a certain program.
... and has a way to fix them?
1. the phone will decrease its refresh rate from time to time and stays there, and the "stuttering" is only fixed by rebooting. Yes, I am aware, that Whatsapp and Telegram voice messaging is occasionally linked to it, and can be handled by removing the apps from memory. But not in the mentioned cases.
2. "Ok, Google" accessing the assistant doesnt work from now and then. And is back to normal a few tries later.
3. When talking over the phone with speaker mode and browsing on the phone, the notification bar cannot be pulled down any more, which is annoying cause I cant easily open the phone tab to end the call.
Anyone, guys?
2. I have a similar bug with quick tap, it seems that a system app freezes/crashes, and without knowing the exact culprit the entire system needs to be rebooted to enable the function again.
Plus my "Ok, Google" also stopped working in the past, found no way to fix it yet. It's probably an Android 12 bug.
Since yesterday I noticed my AOD does not work when on a call, screen goes dark. I go into AODsettings and it still turned ON.
There's only been one update since the phones been released, besides the FPS update, after a few updates it'll be fine
I have noticed "OK Google" not responding at times as well.. not as bad as my 2XL was at times, only a reboot would fix that...but is annoying to say the least especially when driving. And I don't think it works while using Waze or Maps for navigation either which stinks, maybe I need to use Android Auto for that integration to work right.