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
Related
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.
is there still no Gingerbread ROM/kernel that supports call recording?
is anyone aware of the current state of development?
is there any?
ippon said:
there still no Gingerbread ROM/kernel that supports call recording?
is anyone aware of the current state of development?
is there any?
Click to expand...
Click to collapse
Last I heard the one country that allowed it, didnt add it to the last update. To be Honest I dont think it is a good idea. While useful, all it takes is one person to find out they were recorded without consent and boom lawsuits everywhere. The main reason I never add it to my roms
zelendel said:
Last I heard the one country that allowed it, didnt add it to the last update. To be Honest I dont think it is a good idea. While useful, all it takes is one person to find out they were recorded without consent and boom lawsuits everywhere. The main reason I never add it to my roms
Click to expand...
Click to collapse
Depends on the country.. North of the 49th, we are allowed to record calls if one party is aware that the call is being recorded (ie the caller). would love to see this feature incorporated into a rom, as I have not been able to find a working app that will do it properly.
still no dev on introducing call recording on ginger?
Bump. I sure could use this feature. Worked great on Continuum 4. Wish I still had it on GB roms. :-(
Wont work on gB for a while. The Korean phone we got it off of had froyo at the time so we could port it. The phone doesn't have 2.3.5 GB so it will be very hard to port
Sent from my I897 using XDA App
I'm using an Incredible S. I dont receive messages sometime. It's getting delayed. Sometimes calls are droped. Any idea why ?
Thanks
Does anyone know how to fix this ?
Take a look here http://androidforums.com/htc-incredible-s/357978-solution-fix-2-3-3-update-sms-delay.html
Thanks a lot. If I use GSM only I can use 3G. :-(
awesomexda said:
Thanks a lot. If I use GSM only I can use 3G. :-(
Click to expand...
Click to collapse
No you can't that's the problem!
What are the alternatives available to solve this problem ?
awesomexda said:
What are the alternatives available to solve this problem ?
Click to expand...
Click to collapse
There aren't, it seems like a bug in the software with HTC, which they said there is a fix "coming soon".
Read this thread here
okay thanks
awesomexda said:
okay thanks
Click to expand...
Click to collapse
awesomexda, where did you purchase your inc s from? what country are you currently in?
What country has the phone originated from?
This is what happened this morning.
"I just had HTC contact in regards to my **** feedback to them lol.
The lady went on to say that someone else had contacted her about the exact same issues and she told me that MobiCity should not be selling overseas phones to us because of frequency problems and so on. She said she is going to contact them directly aswell as aussie warranty to either send me an australian built one or give me a refund because of the rare situation we are in.
So it seems like it is something with the way the phones built.
I'll keep you guys updated. "
That's on android forums.
Thanks neo-X for the information !
I'm in sri lanka. It's HTC asia one. I bought it here. I think this is a major issue. most of the people who bought the phone have been experiencing issues like this. I'm disappointed with HTC becuase they said INC S is a flagship device and has no errors. But I still luv me device even though it has got problems.
Thanks people
awesomexda said:
Thanks neo-X for the information !
I'm in sri lanka. It's HTC asia one. I bought it here. I think this is a major issue. most of the people who bought the phone have been experiencing issues like this. I'm disappointed with HTC becuase they said INC S is a flagship device and has no errors. But I still luv me device even though it has got problems.
Thanks people
Click to expand...
Click to collapse
Yeah it seems that asian sourced phones will sometimes not work properly in other countries for some reason.
For more information follow this thread here
Thanks for the info !
Cyanogen and MIUI roms have no SMS delays with 3G Preferred is selected.. Lets hope HTC fixes their rom rather than going from sense 2 to 3.5.. :|
jpkbeddu said:
Cyanogen and MIUI roms have no SMS delays with 3G Preferred is selected.. Lets hope HTC fixes their rom rather than going from sense 2 to 3.5.. :|
Click to expand...
Click to collapse
Yeah the latest is that HTC are releasing a new asia rom to fix this problem in the next week. I heard that like 2 months ago though!
neo-X said:
Yeah the latest is that HTC are releasing a new asia rom to fix this problem in the next week. I heard that like 2 months ago though!
Click to expand...
Click to collapse
Wow.. Thats great. But is this delayed SMS problem is localized to Asia-Pacific regions alone ?
jpkbeddu said:
Wow.. Thats great. But is this delayed SMS problem is localized to Asia-Pacific regions alone ?
Click to expand...
Click to collapse
No idea mate. That's all i got from them.
Here is my experience- I contacted HTC support in Singapore this week and was excited to read the email response:
"I would suggest you to go to the local service center to install the lately released patch on your Incredible S on the spot."
I rushed to the service centre, only to find out that HTC's definition of a "lately released patch" was to roll back to 2.2
At least the delayed SMS issue is now resolved!
jpkbeddu said:
Cyanogen and MIUI roms have no SMS delays with 3G Preferred is selected.. Lets hope HTC fixes their rom rather than going from sense 2 to 3.5.. :|
Click to expand...
Click to collapse
I've tried MIUI, I like it, but it didn't really fix the problem. It seemed to make it slightly better, but I was still getting messages 10 mins late or so. I've just flashed CM7 Nightlies, but it doesn't show the time stamp of when the message was sent, only of when it was received so I can't really judge if it fixes the problem or not.
Tartarus1 said:
I've tried MIUI, I like it, but it didn't really fix the problem. It seemed to make it slightly better, but I was still getting messages 10 mins late or so. I've just flashed CM7 Nightlies, but it doesn't show the time stamp of when the message was sent, only of when it was received so I can't really judge if it fixes the problem or not.
Click to expand...
Click to collapse
Same here, im on cm7 but can't judge it.
Here is what HTC said.
"Dear _,
Thank you for your reply.
After checking, we regret to inform you that we have been aware that the message delay is a known issue after Incredible S upgrades from Android 2.2 to 2.3 But currently our engineer is trying to finding out a workable solution for it. If there is any update or patch for the issue, we would put the information on our official webstie. And from our side, if there is any update, we will also inform you. We do apologize for any inconvenience which was brought by the phone issue.
We have to say that currently for the SMS delay issue, the only method is trying to select "GSM only" mode.
But for the **phone ringing issue**, we would suggest that you may try to put your phone in the safe mode to see whether there is improvement for the phone ringing problem.
Before you put your phone in safe mode, make sure that you have your fast boot option unchecked: Menu > Settings > Power > Make sure "Fast Boot" is unchecked.
To put the Sensation into Safe Mode, you may follow the steps 1.With the Device turned off 2.Press the power button briefly 3.keep holding the Volume down button once you see the splash screen (HTC quietly brilliant) 4. Once it loads you will see on the “Safe Mode” on the bottom left of the screen.
****, we are looking forward to your kind action and appreciate the time taken to write to us. Please feel free to contact us should you require further assistance.
Best Regards
June"
Apparently Optus kicked up a stink with HTC and made them fix this issue. There is a new Optus ROM but can't find it anywhere on here.
Just switched from iOS to Android (used to be an active member of the forums for WinMo), so forgive me as I know this has been asked before, but I didn't find any results in HTC ONE forum. I am having issues with the call history. It doesn't show a time only the date. There has to be a way to fix this on the stock dialer but I can't seem to find it anywhere in the settings. Any advice would be ideal. I prefer not to download a third party app for this fix but if this is the only way that would be fine, I guess. Thank you in advance.
redbandana said:
Just switched from iOS to Android (used to be an active member of the forums for WinMo), so forgive me as I know this has been asked before, but I didn't find any results in HTC ONE forum. I am having issues with the call history. It doesn't show a time only the date. There has to be a way to fix this on the stock dialer but I can't seem to find it anywhere in the settings. Any advice would be ideal. I prefer not to download a third party app for this fix but if this is the only way that would be fine, I guess. Thank you in advance.
Click to expand...
Click to collapse
What Rom are you on? I'm on 4.2.2 sense 5 and I have times and dates.
Sent from my HTC One using Tapatalk
lampel said:
What Rom are you on? I'm on 4.2.2 sense 5 and I have times and dates.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Good question. 4.3 Sense 5
Date and time for text messaging only date for call history. It's annoying and I'm already over the 14 day mark otherwise I would return the device for that simple reason.
redbandana said:
Just switched from iOS to Android (used to be an active member of the forums for WinMo), so forgive me as I know this has been asked before, but I didn't find any results in HTC ONE forum. I am having issues with the call history. It doesn't show a time only the date. There has to be a way to fix this on the stock dialer but I can't seem to find it anywhere in the settings. Any advice would be ideal. I prefer not to download a third party app for this fix but if this is the only way that would be fine, I guess. Thank you in advance.
Click to expand...
Click to collapse
Yes, I'm have the same issue. I just got mine a week ago and installed the upgrade to 4.3 soon afterwards. The software on HTC One is not as intuitive as other phones I have had. The time of call is a basic and important part of call information, so it's beyond comprehension how anyone could leave this off.
I will contact HTC, and hopefully they will include a fix in their next update. How ridiculous to forget something like this. They seemed to have focused on doing a great job on the hardware and completely ignored UX on this phone.
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?