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?
Related
Anyone on Rogers managed to get this to work? I miss not being able to see the name of the person/company who is calling me.
+1
From what I understood, we need to activate ro.ril.enable.cnap=1 in build.prop.
I tried that, no go (CM7 RC2)
Anyone have any other idea?
dgege said:
From what I understood, we need to activate ro.ril.enable.cnap=1 in build.prop.
I tried that, no go (CM7 RC2)
Click to expand...
Click to collapse
Yeah, that doesn't work on a stock ROM either. There's obviously something we are missing.
efrant said:
Anyone on Rogers managed to get this to work? I miss not being able to see the name of the person/company who is calling me.
Click to expand...
Click to collapse
I would also love to have this. The information must be being sent TO the phones, right? There must be a way.
There's gotta be a way indeed. But alas, it's way beyond my expertise
Some Android phones do support CNAP. So it must be a problem with the software/radio.
Any guru volunteering to help out?
This was a big "WTF, seriously?" for me when I got my Nexus One after having a Nokia N95 for years where this worked perfectly. I've gotten used to it, but I'd love to have the name display again.
Do other carriers do this? People I know using Bell or Telus were surprised or even didn't believe me when I said I used to get name display with my N95, which suggests maybe they don't. Anyone know how common it is for carriers to send the name? I've been with Rogers for over 10 years now and just figured it was a standard thing like with landlines.
I had my SE W810i (best non-smartphone by far) and it worked perfectly. Since then, tried many phones, none of them supported CNAP. Had a nokia that would support it but wouldn't keep it in the call list. Pretty useless when I got missed calls.
I know some android phones do support CNAP. So this is entirely possible. We just need one of the gurus to figure out what has to be done!
I think it has something to do with this file : /data/misc/rild_ril.cnap
Sent from my Nexus One using XDA Premium App
phazerorg said:
This was a big "WTF, seriously?" for me when I got my Nexus One after having a Nokia N95 for years where this worked perfectly. I've gotten used to it, but I'd love to have the name display again.
Do other carriers do this? People I know using Bell or Telus were surprised or even didn't believe me when I said I used to get name display with my N95, which suggests maybe they don't. Anyone know how common it is for carriers to send the name? I've been with Rogers for over 10 years now and just figured it was a standard thing like with landlines.
Click to expand...
Click to collapse
I believe Rogers is the only Canadian carrier that offers CNAP/name-display.
I remember the difficulties we had in trying to get it to work on Windows Mobile devices. There was a work-around, but it required , but it required using a specific file (rilphone.dll) from a Rogers ROM for the same/similar device... Maybe we need the /data/misc/rild_ril.cnap from a Rogers ROM for a similar device...
If I'm not mistaken, the Rogers Samsung Galaxy supports CNAP.
dgege said:
If I'm not mistaken, the Rogers Samsung Galaxy supports CNAP.
Click to expand...
Click to collapse
I think what we need is an HTC device that has a Rogers ROM with CNAP working, which I don't think exists...
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
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.
I just picked up my pair today, and I'm already having a minor issue. Everything works perfectly, but I can't hear/be heard when I make a phone call.
I'm hoping that this is a problem with my phone, and not my glass, but when I try to call a friend they can't hear me and I'm unable to hear them. I'm using a rooted SGS2 that's got CM10.1 running.
Anyone run into this, and if so how did you fix it?
skylenorman said:
I just picked up my pair today, and I'm already having a minor issue. Everything works perfectly, but I can't hear/be heard when I make a phone call.
I'm hoping that this is a problem with my phone, and not my glass, but when I try to call a friend they can't hear me and I'm unable to hear them. I'm using a rooted SGS2 that's got CM10.1 running.
Anyone run into this, and if so how did you fix it?
Click to expand...
Click to collapse
Try flash back to the Sammy official rom, it should resolve the problem (driver issue for CM maybe)
ytwytw said:
Try flash back to the Sammy official rom, it should resolve the problem (driver issue for CM maybe)
Click to expand...
Click to collapse
This did actually solve it. Man, I'd forgotten how ugly Touchwiz is.
skylenorman said:
This did actually solve it. Man, I'd forgotten how ugly Touchwiz is.
Click to expand...
Click to collapse
Its just the bluetooth drivers. It works for me in CM 10.1 on a GNex now. Hopefully you can go back to your custom rom
Is it a sprint s2 or all s2 bec its not working on my d710 on cm either so I'll ask the device maintainer to take a look
Sent from my SPH-D710 using Tapatalk
Every S2 on any model I have tried with C1.. Couldn't go back to stock launcher to it it so I got a Motorola g.
Sent from my Nexus 7 using Tapatalk 4
Hi All,
Got the Z1 last week about 9 dates ago as a replacement for a Samsung Galaxy S3. Generally liking it, though struggling to get used to the size of the handset. One major issue, though that I can't easily sort or find an answer to anywhere.
Basically, when I use a wired headset with inline mic for phone calls, the microphone is way too sensitive. It picks up every movement of the headphone cord, every rustle on my clothes, etc. Tried about 5 different headsets, including a dedicated Android one button Sennheiser headset. All the same. None of these proved a problem with
Anyone any ideas on what's causing it or how to fix it? Is there something simple I'm missing? It's making calls a painful experience.
Thanks in anticipation.
Sent from my iPad using Tapatalk
Did these problems with those mics occur on your galaxy s3?
LaosPerson said:
Did these problems with those mics occur on your galaxy s3?
Click to expand...
Click to collapse
Nope. In one case, the headphones/headset goes back as far as an IPhone 4, so about three years ago. This is the first time I've had the issue with any of them.
Sent from my iPad using Tapatalk
smajor said:
Check with your mic settings, after making settings then switch your phone and then switch it on. Perhaps this helps. Also check this issue by using hand free. :fingers-crossed: well, samsung 3 is better than this
Click to expand...
Click to collapse
Tried that. No change. S3 better than this? In this respect only. V pleased to see the back of the S3, as it constantly had firmware issues, caused, no doubt. Random battery life issues (sometimes lasting a day, sometimes a few hours), crashes, screen redraw issues, glitchy music playback. I could go on.
Sent from my iPad using Tapatalk
smajor said:
Check with your mic settings, after making settings then switch your phone and then switch it on. Perhaps this helps. Also check this issue by using hand free. :fingers-crossed: well, samsung 3 is better than this
Click to expand...
Click to collapse
Woah galaxy s3 better then this? no way, i had one it was laggy in ui, because of it being ruined by touchwiz and also the fact it was an at&t variant so it had bloatware ontop of samsung bloatware lol
smajor said:
Cool! :victory: well, I don't know about the bloat ware but in my home, most of us are crazy for samsung
Click to expand...
Click to collapse
oh okay, sounds like the where in the US just because it's an iPhone it's automatically better, I used to be like that defending iPhone until i tried the beauty of a GOOD android phone not a cheap one
Oh dear. Wish I hadn't bothered posting here. Another fanboy fight. Look, whatever phone you own, hope you like it. My thanks to those posters who tried to answer my original query. Still searching for an answer.
Sent from my C6903 using Tapatalk
academicbarzo said:
Oh dear. Wish I hadn't bothered posting here. Another fanboy fight. Look, whatever phone you own, hope you like it. My thanks to those posters who tried to answer my original query. Still searching for an answer.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Yeah sorry about that, we didn't answer your question
As for that mic issue it sounds very suspicious
academicbarzo said:
Oh dear. Wish I hadn't bothered posting here. Another fanboy fight. Look, whatever phone you own, hope you like it. My thanks to those posters who tried to answer my original query. Still searching for an answer.
Click to expand...
Click to collapse
I think with Root you can get work anything even the sensitivity of your microphone. It can be easy like edit build.prop that something more but I am sure the sensitivity can be managed. If I find something I will post.