Ever since the gingerbread upgrade, I've noticed that when answering calls, I have to wait 2-3 seconds before saying "hello".
Anyone else notice this?
lol I thought I was the only one that notices this
I have also noticed this issue, sometimes I have to repeat the greetings even though I already hear the other side.
This is a know gb nexus problem try the search button next time
Sent from my Nexus One using XDA App
I have to do this also. I say hello and they don't hear me. I didn't know it was a known issue.
please star the issue on the tracker
http://code.google.com/p/android/issues/detail?id=15297
same thing for me and 2 other nexus users I know
just answer, pause half a second and say Hello or Yellow or S'up or whatever you kids say these days
There's an app on XDA CM7 thread called Dewonkificator--solved my problem
It is run on rooted phones--not sure if you guys are rooted--or can run the app if not
Ken
I've had this issue on my nexus since I got it. On the shipping ROM as well as CM6, Enoms Official and CM7. It seemed that until the call timer appeared on screen during a call no one could hear me. I also never had the call wonk on CM7 when I was still using my nexus.
wastegate13 said:
I've had this issue on my nexus since I got it. On the shipping ROM as well as CM6, Enoms Official and CM7. It seemed that until the call timer appeared on screen during a call no one could hear me. I also never had the call wonk on CM7 when I was still using my nexus.
Click to expand...
Click to collapse
Exactly, I thought this has always been present too. I've always just waited till the timer starts before speaking.
RogerPodacter said:
Exactly, I thought this has always been present too. I've always just waited till the timer starts before speaking.
Click to expand...
Click to collapse
Glad I wasn't the only one. My uncle has a nexus also but I've never asked him if he experiences the same thing.
To make matters more exciting, this is NOT an issue & has been declined by Google! Check issue on Google Code.
If you're having the call delay problem (note this is not the wonk, which appears in CyanogenMod 7, that's a different problem), please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
As KoolPal said, Google recently declined this known Gingerbread bug, saying it was "device specific" (to the Nexus One).
However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.
Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.
Thanks.
Maybe that's why the SGS GB update was pulled by Google.
cb474 said:
If you're having the call delay problem (note this is not the wonk, which appears in CyanogenMod 7, that's a different problem), please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
As KoolPal said, Google recently declined this known Gingerbread bug, saying it was "device specific" (to the Nexus One).
However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.
Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.
Thanks.
Click to expand...
Click to collapse
I can't get behind that. My nexus always had that little quirk and not only on gingerbread. My inspire on cm7 has never had this issue.
wastegate13 said:
I can't get behind that. My nexus always had that little quirk and not only on gingerbread. My inspire on cm7 has never had this issue.
Click to expand...
Click to collapse
I don't know how to explain that. The problem has been very widely reported with Gingerbread on the Nexus One and you're the first that I've seen who says they had it before Gingerbread. I certainly didn't.
The problem has also been widely reported on the Desire and reports are starting to come in on the Galaxy. But everyone says it started with Gingerbread.
Perhaps your problem is slightly different? Or a carrier/network problem?
The Google employee following up on the call delay issue, in the Google support forums, is asking people to fill out the following form, to gather information about how people are affected and on what devices.
http://goo.gl/10HJ1
cb474 said:
I don't know how to explain that. The problem has been very widely reported with Gingerbread on the Nexus One and you're the first that I've seen who says they had it before Gingerbread. I certainly didn't.
The problem has also been widely reported on the Desire and reports are starting to come in on the Galaxy. But everyone says it started with Gingerbread.
Perhaps your problem is slightly different? Or a carrier/network problem?
Click to expand...
Click to collapse
I have the exact issue that you're describing, answer a call and the other party can't hear me for the first few seconds. I got in the habit of waiting for the call timer to appear before I started to speak and that worked for me. My nexus always did this, every single time and on every ROM that I ever ran.
wastegate13 said:
I have the exact issue that you're describing, answer a call and the other party can't hear me for the first few seconds. I got in the habit of waiting for the call timer to appear before I started to speak and that worked for me. My nexus always did this, every single time and on every ROM that I ever ran.
Click to expand...
Click to collapse
Well, that is strange. Many many people are reporting this issue as something that appeared with Gingerbread. You are the only person I've seen say they had it before Gingerbread. I don't really know how to explain that.
Looks like the bug report I started on this, expanding the issue to include all affected devices (not just the Nexus One), has been reopened. See comment #89.
http://code.google.com/p/android/issues/detail?id=16230
And someone else pointed out that the googlenexus twitter feed says the upcoming 2.3.4 update has bug fixes for the Nexus One.
https://twitter.com/#!/googlenexus
Hooray. Perhaps there is hope after all. Although I'll believe it when I see it.
Related
Hi
Just wanted to know if others experience this too?
when making a phone call, my sound is lagging/blurry/scratching. Sometimes sound like (kind of) a robot.
I live in the city, and signal loss or network change is therefore not an issue.
Just thought it was wierd, but guess it will be fixed with update.
From post #12:
I hoped this was just a software error, but baseband upgrade and custom ROM didn't work. This is how it sounds
http://dl.dropbox.com/u/4651820/Stemme 002.amr (starts around 15 sec)
Exact same thing here. Sounds like a loose connection in the speaker. Same city as you, but on 3 instead of TDC. Nothing to do with network, it's either soft-or hardware error in the LG. Let's just hope it's soft
no problem here the sound is perfekt. i have telia
Its a known problem.
I sent the phone back as DOA because of this and few other problems.
Sorry. Forgot to change provide r, I'm on 3 as well...
I hope it's software too. Waiting for better rom from paul before testing...
My camera has stopped working as well of today : s
Started of so well with the phone. But sucks with bugs on stock rom
Sent from my LG-P990 using Tapatalk
raf2k said:
Its a known problem.
I sent the phone back as DOA because of this and few other problems.
Click to expand...
Click to collapse
Do you know if it's software or hardware related?
Sent from my LG-P990 using Tapatalk
See this thread here. Give LG a buzz as they are accepting bug reports for a major update.
fen_nyc said:
See this thread here. Give LG a buzz as they are accepting bug reports for a major update.
Click to expand...
Click to collapse
Thanks for heads up. Looks like it's software error fortunately, so Im more calm now
Found this at Paul's forum.
"Problem solved with the new baseband I think. Haven't noticed any tinny sound effect when in phone - either 2G or 3G connectivity.
It's a shockingly large improvement. Really bad that LG sells the phone with that software because mine was almost unusable in crowds because you had no idea what the other person was saying. Will be keen to jump to newer basebands now if they become available since it's proven it does make a huge difference. At least it's not a reason to NOT buy this phone anymore since it's easily fixable thanks to Paul now "
Problem was solved after update.
Check for updates here: http://android.modaco.com/content/lg-optimus-2x-2x-modaco-com/335049/in-call-sound-quality/
larsn84 said:
Thanks for heads up. Looks like it's software error fortunately, so Im more calm now
Found this at Paul's forum.
"Problem solved with the new baseband I think. Haven't noticed any tinny sound effect when in phone - either 2G or 3G connectivity.
It's a shockingly large improvement. Really bad that LG sells the phone with that software because mine was almost unusable in crowds because you had no idea what the other person was saying. Will be keen to jump to newer basebands now if they become available since it's proven it does make a huge difference. At least it's not a reason to NOT buy this phone anymore since it's easily fixable thanks to Paul now "
Problem was solved after update.
Check for updates here: http://android.modaco.com/content/lg-optimus-2x-2x-modaco-com/335049/in-call-sound-quality/
Click to expand...
Click to collapse
Hehe, funny to be quoted here, from a thread I started over at MoDaCo. According to my poll there a lot of 2X users experience bad sound.
Like I wrote at MoDaCo - I haven't noticed any weird sound after the baseband flash, so please upgrade and tell me if you also notice an improvement. I'll update the thread accordingly.
Btw, what baseband are you currently on?
sibbor said:
Hehe, funny to be quoted here, from a thread I started over at MoDaCo. According to my poll there a lot of 2X users experience bad sound.
Like I wrote at MoDaCo - I haven't noticed any weird sound after the baseband flash, so please upgrade and tell me if you also notice an improvement. I'll update the thread accordingly.
Btw, what baseband are you currently on?
Click to expand...
Click to collapse
Hehe. Im just having trouble remembering which i wrote in and which i read in :-D
But...
I Updated baseband now = no difference.., still scratchy sound...
Flashed pauls custom rom = still scratchy sound...
Seems in some cases it might ne hardware related :-(
Perhaps im unlucky.
The volume is okay/high enough. I just got scratching.... similar to white noise
Sent from my LG-P990 using XDA Premium App
larsn84 said:
Seems in some cases it might ne hardware related :-(
Click to expand...
Click to collapse
If this is truly a hardware issue, don't delay- send it back. Furthermore, be mindful of the replacement you receive. Here is an example of an "ugly" situation that happened between two owners. Be firm & inspect your replacement thoroughly- if it's not in "like-new" condition or has residual data from a previous owner, argue for a brand new 2X.
fen_nyc said:
If this is truly a hardware issue, don't delay- send it back. Furthermore, be mindful of the replacement you receive. Here is an example of an "ugly" situation that happened between two owners. Be firm & inspect your replacement thoroughly- if it's not in "like-new" condition or has residual data from a previous owner, argue for a brand new 2X.
Click to expand...
Click to collapse
I think we got quite good policies in Denmark, so I'll probably just get a new one at first But thanks for the advice. Hopefully the next will show up better.
A friend of mine experienced pixel "errors" on his AND his girlfriends, so the next one better be fully functional... I know that TDC provider in Denmark wanted to postpone the release too, because of malfunctioning devices. This was before they ever sold any, and they haven't got them in stock yet
I hoped this was just a software error, but baseband upgrade and custom ROM didn't work. This is how it sounds
http://dl.dropbox.com/u/4651820/Stemme 002.amr (starts around 15 sec)
Now I just have to wait for "three" to send it in, and return a new one... if it happens three times, I'll get my mony back, and perhaps go for the SGS2 and hope it gets Tegra2... a shame, such a nice phone otherwise. Hope they make it work, but I hear a lot of complaints *fingers crossed*
EDIT: Damn, just heard of three occasions of the same problem here in Denmark... hope they can fix it
I'm not experiencing any scratchy sounds like you, not even before I upgraded baseband. So I guess it's not all O2X in Denmark that has the problem.
I bought mine through Callme.
Aduck79 said:
I'm not experiencing any scratchy sounds like you, not even before I upgraded baseband. So I guess it's not all O2X in Denmark that has the problem.
I bought mine through Callme.
Click to expand...
Click to collapse
The problem has been there all the time for me. Just saying the update didn't work for me, so I guess it is hardware related in my case. There has just been some discussions about wether it is hardware or software related.
The problem doesn't occure on all devices, but some are unlucky. 2 of my friends, which bought it on the release date, as my self, has experienced the same problem.
Also, on mobildebat.dk (danish forum) people complain about having the same problem. Such a shame.
I turned in my phone now, and has to wait for up to 10 days for LG to come up with a solution now Hope it goes faster. If i went down to the store last wednesday, I would hav gotten a new phone right away, due to 14 days return policy. Now I have to use my Nokia N82, damn it's slow
Hi,
I have had the same problems on my week old phone. Scrathy sound, Buzzing sound that both ends can hear and the other end sounding "tinny" or like a robot.
I also had random reboots.
Sent it in to repairs monday, hopefully it won't come back with "no faults found".
MY local Telia shop, where I bought the phone, hadn't heard about the problem from more than 1-2 people. Danish LG customerservice also hadn't heard about it. (This was a week ago.)
BTW: Is it normal for camera area to get very hot during calls? I had that too. Battery time was ok. 1-1½ day of normal use. Heavy wifi/talk/gps = less than a day.
I made a recording of the buzzing sound (starts at around 20secs in.):
dl.dropbox.com/u/4130839/Out_2011_03_27_14-06-29_%2B4550800950.3gp
This buzzing is sometimes so loud you cant hear what ppl are saying, and they have a hard time hearing you too.
pslind69 said:
Hi,
I have had the same problems on my week old phone. Scrathy sound, Buzzing sound that both ends can hear and the other end sounding "tinny" or like a robot.
I also had random reboots.
Sent it in to repairs monday, hopefully it won't come back with "no faults found".
MY local Telia shop, where I bought the phone, hadn't heard about the problem from more than 1-2 people. Danish LG customerservice also hadn't heard about it. (This was a week ago.)
BTW: Is it normal for camera area to get very hot during calls? I had that too. Battery time was ok. 1-1½ day of normal use. Heavy wifi/talk/gps = less than a day.
I made a recording of the buzzing sound (starts at around 20secs in.):
dl.dropbox.com/u/4130839/Out_2011_03_27_14-06-29_%2B4550800950.3gp
This buzzing is sometimes so loud you cant hear what ppl are saying, and they have a hard time hearing you too.
Click to expand...
Click to collapse
I got the same buzzing sound if I call
davjan said:
I got the same buzzing sound if I call
Click to expand...
Click to collapse
Yeah, It's really strange =/
Just in cas you haven't saw it but seems that the latest radio fix this :
http://forum.xda-developers.com/showthread.php?t=1008070
goulloux said:
Just in cas you haven't saw it but seems that the latest radio fix this :
http://forum.xda-developers.com/showthread.php?t=1008070
Click to expand...
Click to collapse
I updated the baseband , but the problem is still there
davjan said:
I updated the baseband , but the problem is still there
Click to expand...
Click to collapse
Damn, I was hoping it was just a bad sw =/
Hey guys,
After JVK update I've been having this problem with delays in answering calls. The call wouldn't be answered for about 2 seconds even after sliding the answer call button. I have pure JVK, 512 pit and bootloader. No root or etc.
Is there anyway for me to fix this? It's so damn irritating..
Have you done anything to the ROM after installing it? I'm running XXJVK and don't have this issue.
Intratech said:
Have you done anything to the ROM after installing it? I'm running XXJVK and don't have this issue.
Click to expand...
Click to collapse
Question revised.
Very strange bro, if you haven't modified the ROM in anyway I'm at a loss. I'm assuming you didn't use a custom ROM. I flashed the version with the bootloader so don't know if that made any difference.
I can confirm that!
STOCK JVK
+1 to that
Also when I'm calling somebody I cant hear the initial "hello", we end up helloing each other like dumbnuts...
STOCK JVK
//edit: F.... double
Yes, for me that problem aswell, and it was with 2.3.2 rom aswell
Sent from my GT-I9000 using Tapatalk
I have made a small research and it seems all 2.3.3 phones (Nexus one, HTC) have this problem. And there is an app at the market named: Call Delay Patch. I did not try it yet. In fact I do not want to try! Because it is the basic function of a phone to be able to answer a call! You should not install some third party app to do that! Do you hear me Google!
i have exactly the same problem, this might be a bug, but why some of us have it, and some dont?
Sent from my GT-I9000 using XDA App
zalimtayyar said:
I have made a small research and it seems all 2.3.3 phones (Nexus one, HTC) have this problem. And there is an app at the market named: Call Delay Patch. I did not try it yet. In fact I do not want to try! Because it is the basic function of a phone to be able to answer a call! You should not install some third party app to do that! Do you hear me Google!
Click to expand...
Click to collapse
it is not google, it is samsung
teltel said:
it is not google, it is samsung
Click to expand...
Click to collapse
I said other Gingerbread phones like Nexus and Htc have the some problem. So; yes it is Google!
someone found a fix? does the earlier mentioned app work?
teltel said:
it is not google, it is samsung
Click to expand...
Click to collapse
It's officialy Google not Samsung. Google admited the bug at last.
Maybe the reason Google pulled the JVK update...
If you're having the call delay problem, especially on a device that is not the Nexus One, please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
This is a known bug with Gingerbread, that Google recently declined, saying it was "device specific" (to the Nexus One).
However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.
Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.
Thanks.
The Google employee following up on the call delay issue, in the Google support forums, is asking people to fill out the following form, to gather information about how people are affected and on what devices.
http://goo.gl/10HJ1
Download this app called multitouch visible test from Google play store. Also watch this video first. Type in google Nexus 7 touchscreen problem caught on video its on zdnet. Can't post links since am under 10 post
http://www.zdnet.com/nexus-7-touchscreen-problem-caught-on-video-7000001325/
I don't have the issue.... I think the issue he is showing is software related.
krelvinaz said:
http://www.zdnet.com/nexus-7-touchscreen-problem-caught-on-video-7000001325/
I don't have the issue.... I think the issue he is showing is software related.
Click to expand...
Click to collapse
Just to be on the safe side I think everyone should try this. I have done this and am all good
Where do you get a Tegra 3 game that will push the cores since that seems to be a factor?
You can find the demo here: https://play.google.com/store/apps/details?id=com.eneko.puddle.thd.lite
Jaybuz said:
You can find the demo here: https://play.google.com/store/apps/details?id=com.eneko.puddle.thd.lite
Click to expand...
Click to collapse
Eh the Galaxy Nexus had THIS EXACT problem when it first came out. Software update fixed it.
I'm not worried.
I would suggest not testing if you don't notice anything. So many people discover issues they wouldn't have cared about otherwise because of threads like this. The screen separation issue is one. How many people wouldn't have even noticed? I wouldn't have, especially once I got my Nexus in a case.
So far I have no issues at all with my tablet. Have been using it since yesterday and working perfect. But I hate chrome browser even though it's better then it was on the a500.maybe I just need to get used to it. Also I get lagg in resizing text auto.
We have been discussing this issue here http://forum.xda-developers.com/showthread.php?t=1789450 the multitouch test shows the bug even if you didn't play, you only need to put the tablet on the desk and it will happen ;(
Has anyone experienced this problem on the RAZR i (but possibly not realised it or thought it was just occasional) with regards to people phoning you, you saying hello and them clearly not hearing you as they don't respond. Only when you say 'hello' again is it quite clear they didn't hear anything at first as they don't act surprised or confused.
It must be 1-2 seconds or so at most, but it's quite annoying and seems to be happening every time I answer. This makes me suspect it's the phone, not the network (Orange/EE if anyone cares).
I thought it might just be the person at the other end not listening, but I've since asked people who didn't respond if they heard my first hello and they say no - so it's as if the mic isn't activated straight away.
Before I report it as a bug to Motorola, I really want to know if anyone else has suffered the same problem?
mee to
81.5.32002.XT890.Retail.en.EU
Rooted with Motofail2go
Never noticed it but i'll take notice tomorrow to see if my GB firmware also does it.
wozn said:
Never noticed it but i'll take notice tomorrow to see if my GB firmware also does it.
Click to expand...
Click to collapse
So you know, my phone is;
81.5.31002.XT890.Retail.en.GB
I have exactly the same problem, but on my 2 years old Desire, and I've only had it since I installed the latest version of a custom ROM, so there is a very big possibility, that it's just a software bug. But I agree, it gets annoying as hell, so it would be great for as many people with this problem to let Motorola know about it, so they fix it as soon as possible.
Can't wait to get my hands on this beauty, by the way!
Mine is fine. Done a reset?
I checked mine out as not noticed a problem. Turns out to be fine. Hope you sort the issue.
Sent from my XT890 using xda premium
mine doesn't work anymore, i m downloading 8.1.5.40002.Retail.en.EU to test
Hi,
I'm hoping someone can help me with a strange issue. S-voice does not work for me on the GG using a recently updated (4.3 stock rom) Note 2. What I mean is that every time I try to use S-voice a highly distorted voice says "I didn't catch that", regardless of what I say. I tested the device on my gf's Note 3 and it works fine. As such, there are no issues with the GG device, per se. So, I continued to troubleshoot and figured it was my Note 2 S-voice that is the problem. I was thinking that since I installed the G4 s-voice, which worked fine on my Note 2, this might be the cause. I uninstalled S-voice on my phone and tried to run S-voice on the GG. The watch gave me a message stating I needed to install S-voice on my phone. When I looked at my phone it took me to the Samsung app store with the S-voice app ready to download. I installed the app from the app store on my phone and tried again. Same problem. I don't know how to fix this. So, I was wondering if anyone else is having a similar issue. Here is my info.
sgh317m (Canada)
Stock rom 4.3
rooted phone
official s-voice
If I forgot any pertinent details, please let me know.
Thank you everyone in advance.
Omg, same issue here, i317m on Rogers, stock rooted note 2, 4.3 and for the life of me s - voice doesn't work! Same exact issue! I thought I forgot how to s - voice lol!!
Sent from my SGH-I317M using Tapatalk
thekenderman said:
Omg, same issue here, i317m on Rogers, stock rooted note 2, 4.3 and for the life of me s - voice doesn't work! Same exact issue! I thought I forgot how to s - voice lol!!
Sent from my SGH-I317M using Tapatalk
Click to expand...
Click to collapse
I'd be curious to know if you also loaded the S4 s-voice or have you always been using the default version? I noticed Samsung updated the app for the Note 2 in the app store, but I'm not sure if my upgrading unofficially may have cause any issues such, as no longer being a system file? I'm not sure. Such knowledge is beyond me.
Hopefully, a wise soul will enlighten us.
No s4 s - voice... Just stock note 2 s - voice. So, really, it should work as is. Apart from a complete Odin and reroot, I dunno.
Sent from my SGH-I317M using Tapatalk
thekenderman said:
No s4 s - voice... Just stock note 2 s - voice. So, really, it should work as is. Apart from a complete Odin and reroot, I dunno.
Sent from my SGH-I317M using Tapatalk
Click to expand...
Click to collapse
Fair to assume you never had an issues with s-voice? I seem to recall when I first put s-voice on my SGS II I had a similar experience to current predicament, but I'm not sure what resolved it.
I've never had an issue at all with s - voice.
Sent from my SGH-I317M using Tapatalk
Hey guys... found this thread on Google. This was the only note 2 s voice issue with GG that I've found so it's reassuring (unforunately) that this is a common issue...
I have a stock note 2. No mods or anything... s voice does not work at all on galaxy gear. Works 100% brilliantly on the note 2... it's a garbled mess of "I didnt catch that" on the Gear. I've tried everything and I have no accent (just a normal Canadian, eh ; ) lol. ... but of the million commands I gave that are in the "?" Icon as legit 'things to say' it did not once do anything but say "I didnt catch that"....
...I hope Samsung is aware of this and fixes it... lol... I returned a watch and said it was defective already hahaha.
Phatronica said:
Hey guys... found this thread on Google. This was the only note 2 s voice issue with GG that I've found so it's reassuring (unforunately) that this is a common issue...
I have a stock note 2. No mods or anything... s voice does not work at all on galaxy gear. Works 100% brilliantly on the note 2... it's a garbled mess of "I didnt catch that" on the Gear. I've tried everything and I have no accent (just a normal Canadian, eh ; ) lol. ... but of the million commands I gave that are in the "?" Icon as legit 'things to say' it did not once do anything but say "I didnt catch that"....
...I hope Samsung is aware of this and fixes it... lol... I returned a watch and said it was defective already hahaha.
Click to expand...
Click to collapse
Hi I am using a Bell Note 2 with the GG and have no problems with s-voice but I am using the Skynote RC9z 4.3 custom Rom. I am interested to know is anyone on the stock bell having the issue? If so I could flash back to stock and see what happens. Also anyone on stock having issues with the GG weather app? mine keeps telling me to set the city on the device widget but it is set. Funny thing though when I ask svoice on the watch what the weather is like it has no problem telling me.
shoichet said:
Hi I am using a Bell Note 2 with the GG and have no problems with s-voice but I am using the Skynote RC9z 4.3 custom Rom. I am interested to know is anyone on the stock bell having the issue? If so I could flash back to stock and see what happens. Also anyone on stock having issues with the GG weather app? mine keeps telling me to set the city on the device widget but it is set. Funny thing though when I ask svoice on the watch what the weather is like it has no problem telling me.
Click to expand...
Click to collapse
Mine is unlocked from Rogers and am using it on Koodo. Of course I installed the Rogers rom. My weather app works fine unless I use s voice.
I've been playing with the language settings (switching between Samsung and Google) and I got s voice to work 4 whole times but not successively. Maybe someone else could mess about as well?
I'm on bell. Stock note 2. S voice isn't working.
Im Glad that this is happening to a few people, as i was thinking my watch was defective -
I ended up calling SAMSUNG about this and they had no clue of course, so i explained 'our' issue and they have opened a case -
If all you guys feel like calling in to complain about this PLEASE DO !!
The more complaints they have the faster they will action this.
Here is the case number that was opened for me for your information - CASE # 2123030231
Thanks all !!
EviLLoNe said:
Im Glad that this is happening to a few people, as i was thinking my watch was defective -
I ended up calling SAMSUNG about this and they had no clue of course, so i explained 'our' issue and they have opened a case -
If all you guys feel like calling in to complain about this PLEASE DO !!
The more complaints they have the faster they will action this.
Here is the case number that was opened for me for your information - CASE # 2123030231
Thanks all !!
Click to expand...
Click to collapse
What's the number buddy? I'll give'em a ring...
EviLLoNe said:
Im Glad that this is happening to a few people, as i was thinking my watch was defective -
I ended up calling SAMSUNG about this and they had no clue of course, so i explained 'our' issue and they have opened a case -
If all you guys feel like calling in to complain about this PLEASE DO !!
The more complaints they have the faster they will action this.
Here is the case number that was opened for me for your information - CASE # 2123030231
Thanks all !!
Click to expand...
Click to collapse
Defiantly going to make that call - I tested out my Galaxy Gear with my Wife's S4, worked no problem, so...it sounds more like a Note 2 issues.
Okayyyy... i talked to samsung Canada support... they said that they're aware of an issue with the 4.3 update. I had already mentioned that i returned a watch already. He made it clear "there's nothing wrong with your hardware... it was an error in the update" ... He said to wait a few days and call back, they'll likely have a solution or at least more information on a coming solution.
Phatronica said:
I'm on bell. Stock note 2. S voice isn't working.
Click to expand...
Click to collapse
Has anyone tried calling Samsung tech support?
rekil goth said:
Has anyone tried calling Samsung tech support?
Click to expand...
Click to collapse
Edit: I mean anyone else besides the two who've already stated. I tried but the rep told me there aren't any issues and so he's not sure why I'm having trouble. Seems like each call gets a different reply. Was hoping others could chime in.
Just to be clear, I called the number below and ended up talking with some guy in the Caribbean.
Call Product & Customer Support
1-800-726-7864
8:30am – 12:00am midnight (EST)
Customer support is available 7 days a week, 365 days of the year.
He looked around and couldn't find anything pertaining to my complaint.
If you guys call and they have no idea, try referring them to the CASE # 2123030231 and see what they say -
I'm planning on calling back next week even though the rep told me not to expect anything to happen for at least a month or so.
bleh..
EviLLoNe said:
Just to be clear, I called the number below and ended up talking with some guy in the Caribbean.
Call Product & Customer Support
1-800-726-7864
8:30am – 12:00am midnight (EST)
Customer support is available 7 days a week, 365 days of the year.
He looked around and couldn't find anything pertaining to my complaint.
If you guys call and they have no idea, try referring them to the CASE # 2123030231 and see what they say -
I'm planning on calling back next week even though the rep told me not to expect anything to happen for at least a month or so.
bleh..
Click to expand...
Click to collapse
Here's a fun fact. I called Samsung Canada today and the rep said he can't find that case number. He went on to say that there are no known issues with using the GG and note 2. Really brightened my day.
Any one else have any luck?
Phatronica said:
I'm on bell. Stock note 2. S voice isn't working.
Click to expand...
Click to collapse
Ok I have now flashed a Rogers and a Bell stock on my note 2 both have the same issue s-voice sounds like its underwater and says it cant understand me but if I flash the SkyNote 9z custom ROM based off the AT&T 4.3 update the watch s-voice works just fine. I tried decompiling some of the relevant APKs and JARs and it seems that there are differences in the implementation of the Bluetooth.apk but flat swapping that file crashes BT services and I am not skilled enough to figure out how to correct the issue via programming.
I am headed back to SkyNote at least till they fix this.
shoichet said:
Ok I have now flashed a Rogers and a Bell stock on my note 2 both have the same issue s-voice sounds like its underwater and says it cant understand me but if I flash the SkyNote 9z custom ROM based off the AT&T 4.3 update the watch s-voice works just fine. I tried decompiling some of the relevant APKs and JARs and it seems that there are differences in the implementation of the Bluetooth.apk but flat swapping that file crashes BT services and I am not skilled enough to figure out how to correct the issue via programming.
I am headed back to SkyNote at least till they fix this.
Click to expand...
Click to collapse
I might be wrong but do you think this has something to do with 4.3 rom using LE BT whereas 4.1 had BT?
I was just curious what might happen if we installed the BT apk from 4.1. Would s voice work? Or am I way off?