I have the following issue with OK Google.
Originally it was fine, but now it is not working at all.
After trying two different clean installs (Pure Nexus, and then Chroma) with only Gapps, the phone will not even recognise the first of "Say 'OK Google' three times" when training the Voice command.
Yet if the microphone is activated in the Google search bar, it is perfect.
I've tried turning off noise cancellation, but to no avail.
I suspect that it's hardware related as this is not a common problem. Thank you
tpsnjs said:
I have the following issue with OK Google.
Originally it was fine, but now it is not working at all.
After trying two different clean installs (Pure Nexus, and then Chroma) with only Gapps, the phone will not even recognise the first of "Say 'OK Google' three times" when training the Voice command.
Yet if the microphone is activated in the Google search bar, it is perfect.
I've tried turning off noise cancellation, but to no avail.
I suspect that it's hardware related as this is not a common problem. Thank you
Click to expand...
Click to collapse
I had the same problem when I 1st set up the phone. Refused to recognise OK Googke command even in the setup screen. Fixed by switching search language from UK English to USA English. After successfully setting up I switched it back to UK and has worked fine ever since. I can see you live in New Zealand so same fix may work for you (obviously replacing UK with New Zealand).
levellerbob said:
I had the same problem when I 1st set up the phone. Refused to recognise OK Googke command even in the setup screen. Fixed by switching search language from UK English to USA English. After successfully setting up I switched it back to UK and has worked fine ever since. I can see you live in New Zealand so same fix may work for you (obviously replacing UK with New Zealand).
Click to expand...
Click to collapse
The language setting is on US English. On these latest ROMs you can get to the set-up screen only if the you're on US English.
Thanks for the try though!
Related
I have a nexus 7 4.1.1 rooted with stock ROM. My voice recongnition in google now has stopped working. It understands when I say GOOGLE then I speak and I see "Recognizing" but nothing happens. After a long while it goes back to the start and I can touch the mike and speak again with the same results.
If I do an email I can click the mike and talk and voice is turned into text just fine. I have looked all over on the N7 but can't find anything that makes the Google Now work again. HELP
PS this started before I unlocked and rooted my N7.
Mine has done that before and a simple reboot corrected it.
Tried that
I have tried rebooting but still doesn't work.
So I am running an interesting setup now where I am running a rooted and unlocked CM10.2 nightly with the GSM bit flipped and an AIO Wireless sim card. There are a few quirks that I have come across and trying to look for answers.
First:
I've had some difficulty getting my APN settings to save
Fixed using a build.prop change a few reboots.
Second:
I have an issue where my DTMF (touch tone) doesn't seem to be registering. Normally this wouldn't be a problem except for when I needed to call my insurance and they have an automated system. I don't know if this is a rom specific thing, an AIO Wireless specific thing or something else with the combination on my phone.
Third:
Since I've been running on GSM, the signal strength for my phone doesn't seem to be displaying properly. The phone works (and now I get internet), but the signal indicator doesn't seem to update. I use Lllama for some things and I see no new tower locations here either.
Fourth:
In Settings -> About phone -> Status -> My phone number is displaying as "Unknown." Not that big of a deal but I thought it was an interesting thing and wanted to see if it may be tied to any of the other issues I'm having.
If anyone has any insight on how to fix these things, that would be great appreciated and hopefully this can help any other people who may be having the same issues as me.
I'm using my Razr in GSM mode with CM10.2 on it. I'm in Italy, so maybe not everything I've done will work in other countries.
What did you changed to make the phone work in GSM mode? I just changed the following in the build.prop file (plus adding the APN):
"telephony.lteOnCdmaDevice=1" from 1 to 0
"telephony.rilV7NeedCDMALTEPhone=true" from true to false
"ro.telephony.gsm-routes-us-smsc=1" from 1 to 0
And everything works fine.
I've also tried to use the GSM fix found in this thread: http://forum.xda-developers.com/showthread.php?t=2446527, but is giving to me inconsistent results. Sometimes the phone works, sometimes drops the line, swithc from 3g to 2g, stops data download... So I flasher back a clean 10.2 ROM and added back only my previous changes.
By the way: in Settings -> About phone -> Status -> My phone number is displaying as "Unknown" too!
j27h said:
I'm using my Razr in GSM mode with CM10.2 on it. I'm in Italy, so maybe not everything I've done will work in other countries.
What did you changed to make the phone work in GSM mode? I just changed the following in the build.prop file (plus adding the APN):
"telephony.lteOnCdmaDevice=1" from 1 to 0
"telephony.rilV7NeedCDMALTEPhone=true" from true to false
"ro.telephony.gsm-routes-us-smsc=1" from 1 to 0
And everything works fine.
I've also tried to use the GSM fix found in this thread: http://forum.xda-developers.com/showthread.php?t=2446527, but is giving to me inconsistent results. Sometimes the phone works, sometimes drops the line, swithc from 3g to 2g, stops data download... So I flasher back a clean 10.2 ROM and added back only my previous changes.
By the way: in Settings -> About phone -> Status -> My phone number is displaying as "Unknown" too!
Click to expand...
Click to collapse
That totally worked! Now I have everything working properly. Thank you very much. Also, I figured out why in Status my phone number is unknown.
Open up the Phone app
Open the Settings menu
GSM call settings
Additional settings
Set your number in "My phone number"
Syphen5 said:
That totally worked! Now I have everything working properly. Thank you very much. Also, I figured out why in Status my phone number is unknown.
Open up the Phone app
Open the Settings menu
GSM call settings
Additional settings
Set your number in "My phone number"
Click to expand...
Click to collapse
Well... that's great: two solutions in two posts! Your phone is working and mine is displaing my number correctly... Hope these posts will be useful for someone else too!
j27h said:
I'm using my Razr in GSM mode with CM10.2 on it. I'm in Italy, so maybe not everything I've done will work in other countries.
What did you changed to make the phone work in GSM mode? I just changed the following in the build.prop file (plus adding the APN):
"telephony.lteOnCdmaDevice=1" from 1 to 0
"telephony.rilV7NeedCDMALTEPhone=true" from true to false
"ro.telephony.gsm-routes-us-smsc=1" from 1 to 0
And everything works fine.
I've also tried to use the GSM fix found in this thread: http://forum.xda-developers.com/showthread.php?t=2446527, but is giving to me inconsistent results. Sometimes the phone works, sometimes drops the line, swithc from 3g to 2g, stops data download... So I flasher back a clean 10.2 ROM and added back only my previous changes.
By the way: in Settings -> About phone -> Status -> My phone number is displaying as "Unknown" too!
Click to expand...
Click to collapse
Sorry for somewhat thread-hijacking, but you seem to know GSM stuff so I thought I'd ask, do you have any problems with making phone calls? I'm in the US on AT&T and when I make a call, if there is any noise coming in from the other person's microphone (either their voice or background noise),my voice starts breaking up on their end. I can hear them fine though.
I've tried several build.prop edits, such as changing persist.audio.handset.mic to 'analog' instead of 'digital', which makes my voice louder to others, but doesn't help with the audio breaking up. Do you know of any build.prop tweaks that might fix the issue? Thanks!
phantomsniper773 said:
Sorry for somewhat thread-hijacking, but you seem to know GSM stuff so I thought I'd ask, do you have any problems with making phone calls? I'm in the US on AT&T and when I make a call, if there is any noise coming in from the other person's microphone (either their voice or background noise),my voice starts breaking up on their end. I can hear them fine though.
I've tried several build.prop edits, such as changing persist.audio.handset.mic to 'analog' instead of 'digital', which makes my voice louder to others, but doesn't help with the audio breaking up. Do you know of any build.prop tweaks that might fix the issue? Thanks!
Click to expand...
Click to collapse
Hi Phantomsniper! Sorry for the late reply... to be honest I'm pretty new to the Android world (less than a year, coming from a Nokia 3310!). Maybe I've a similar issue: I can hear people fine (after cleaning the speaker), but on the other side they always say that my voice sounds too low (but not broken up for what I know). I'll try to investigate if my phone behaves as yours and if there's something we can do!
j27h said:
Hi Phantomsniper! Sorry for the late reply... to be honest I'm pretty new to the Android world (less than a year, coming from a Nokia 3310!). Maybe I've a similar issue: I can hear people fine (after cleaning the speaker), but on the other side they always say that my voice sounds too low (but not broken up for what I know). I'll try to investigate if my phone behaves as yours and if there's something we can do!
Click to expand...
Click to collapse
Yeah, that's pretty much it. Few things I noticed since my last post:
1) If I use headphones with a mic to talk, everything sounds perfect on both ends
2) When testing the bug, if I mute the other person's phone (so I can't hear what they say) then everything I say into the Razr M is clear on their phone
3) Speakerphone works fine
4) Sound problems occur with a T-Mobile SIM and perhaps a Verizon SIM too (I couldn't really test much with the VZW SIM because it was my friend's and she was in a rush so I just tried it for a minute)
I think basically, if any sound is coming through from the earpiece (the one that is right where the "MOTOROLA" logo is), then the microphone that is under the Verizon logo turns off or gets quiet or something. That would explain why speakerphone and using a headphone's mic works fine.
I don't want to get too off-topic here though. Perhaps we should talk over PMs if we find anything new.
Hi, I am newby so to come down on me if this is a dumb question
I have a quite new Galaxy Note 3, which today, whilst sitting in my pocket untouched, managed to change language settings - apparently independently - to an asian language; so that when I reached for it next, everything was coming up in an asian character set. It even managed to change my Samsung Gear in the process. I can't think why this has occurred. The only unusual thing that I have done recently is load Google Now, using the instructions and links found on this website.
I have managed to get the language back to english using some online searching to work out which buttons to press in settings... but I am wondering if there is something I need to do to avoid this happening again, or whether there is something more serious happening in the background.
Could it be that the Google Now (which incidentally works except the voice command "ok google" does not work) had some bug or issue in it, or has opened up a vulnerability?
Incidentally my Gear has seemed a little buggy as well since installing Google Now (e.g. messages not coming through straight away, or pressing on the message notification does not open the text but rather a menu) - in fact I had to re-sync after installation.
Also, before the language change, a little earlier on, the phone suddenly disconnected bluetooth devices, in this case cutting off my car's handsfree in the course of a call (as well as my Gear). This has never happened to me before.
Any advice appreciated... Thanks in advance!
Hi all,
Regular reader but hardly ever post!
I have a Galaxy S4 (GT-I9505) - with Android 4.4.2. Unrooted.
Purchased and used in Singapore on the Starhub network since around October 2013. Everything was working fine until approx Feb or March when the latest Android version, 4.4.2 got rolled out.
Ever since then I am experiencing regular disconnections from the network. But the phone does not re-connect back to the network again, the only fix is to restart the phone.
These disconnections are often once or twice a day, and are very frustrating because if I don't notice it, I may be off the network for hours before noticing it - and are therefore missing out on calls emails etc etc.
This only happened after the Android 4.4.2 got rolled out, so I am pretty confident this is the cause of the problem.
What I tried myself to fix:
- restore APN's back to default state
- Factory reset (both via settings, and via boot screen)
What I have been able to narrow down troubleshooting, is:
- Disconnects seem to only happen when Network Mode is "LTE/WCDMA/GSM (auto connect)"
- If I use network mode "WCDMA/GSM (auto connect)" the disconnections have not happened (yet!)
- When the disconnection does happen in the first mode, I cannot manually change the network mode. The radio buttons are greyed out, and if I try to select "WCDMA/GSM auto connect" the request times out (I forget the exact message - it does respond to the tap but then nothing happens)
So it seems to me this is some sort of software bug/fault introduced with Android 4.4.2 that affects 4G connections.
After that, I have taken it to Samsung for warranty service. I have now had 4 visits to them and they have not been able to fix it yet. This is what they have done so far:
- First visit - factory reset (despite telling them I already did that) - did not fix
- Second visit - checked hardware and replaced mainboard. Did not fix.
- Third visit - checked hardware again and factory reset again. Did not fix.
- Fourth visit - who knows. I think same as visit three but done via a Service Manager instead of staff, Did not fix.
When I first called them back in Feb or March, they said it was a "known Issue' and sugegsted to "wait for a patch". However since visiting them, they said the known issue was only with Note 3's (not with S4's) and replacing the mainboard on the Note 3's fixed the problem. In my case replacing the mainboard - twice - has not fixed it.
I'm getting very annoyed with Samsung who seem to just be trying the same thing each time and are not fixing it. Staying in 3G only mode is a workaround but not an acceptable solution.
Now they've asked me to take if back again - for a 5th time.
Beginning to wish I had never bought the S4, or at least never got Android 4.4.2.
So I thought I would turn to here for help instead, I think you guys and gals probably know more than the Samsung service staff!
Any suggestions?
By the way, I don't run any memory/battery saver apps. I do run one data usage monitoring app that I thought perhaps was conflicting, so I tried not installing it after one of the resets, but the problem continued.
Chikara71 said:
Any suggestions?
Click to expand...
Click to collapse
you CAN try other modem flash, but be careful with your warranty.
I do not know about the warranty conditions in your country, but in EU normally 3 unsuccessful repairs = phone refund or replacement.
I would try reflashing stock file or just flash a different modem
Hello, just like you i have been reading the post but never posting because i just came here to learn, nothing to share from this side...sorry.
But i am having the same problem as you. I bought my phone in Switzerland on march 2013 but i live in Uruguay. I was just thrilled with my s4 until the 4.4.2 update came out. My connection keeps on crashing and it doesnt matter if its on 4g or 3g just make me miserable all day. Only the two of us is having this type of problem??
I believe is some kind of issue with the new bootloader i just updated with a patched rom that came for Germany last week (the one with kids mode) the phone work fine for a hours and then crashes, so this update didnt work. I have also flashed very differents official roms and modems but nothin seem to affect the problem.
I have another problem even though my s4 is 4g i cant connect to 4g network, every configuration is fine i just cant connect, any thougths??
Thank you very much.
Sorry for my english.
Dial *#1234# and paste here what appears.
Joku1981 said:
Dial *#1234# and paste here what appears.
Click to expand...
Click to collapse
AP: I9505XXUFNBE
CP: I9505XXUFNBE
CSC: I9505OLBFNB3
I should add, I took it in *again* to Samsung, to the Service Manager. Said they would replace the antenna and try that, which they did.
Still have the same problem though.
Not sure who to believe, Samsung are starting to run out of ideas and starting to say it may be a network issue. But if the network is down, then the phone should automatically reconnect once the network is back available again. And it doesn't.
I'm convinced it's a bug introduced with KitKat, as the problem only started then, but of course I cannot prove it...
felgrab said:
Hello, just like you i have been reading the post but never posting because i just came here to learn, nothing to share from this side...sorry.
But i am having the same problem as you. I bought my phone in Switzerland on march 2013 but i live in Uruguay. I was just thrilled with my s4 until the 4.4.2 update came out. My connection keeps on crashing and it doesnt matter if its on 4g or 3g just make me miserable all day. Only the two of us is having this type of problem??
I believe is some kind of issue with the new bootloader i just updated with a patched rom that came for Germany last week (the one with kids mode) the phone work fine for a hours and then crashes, so this update didnt work. I have also flashed very differents official roms and modems but nothin seem to affect the problem.
I have another problem even though my s4 is 4g i cant connect to 4g network, every configuration is fine i just cant connect, any thougths??
Thank you very much.
Sorry for my english.
Click to expand...
Click to collapse
Sounds very similar to my problem, that it just started with Kitkat only. I'm sure it can't be just us two having this problem! I don't have anything special or different installed on my phone, and it's too suspicious that it was working fine, 100% perfectly until the KitKat software came out...
Joku1981 said:
Dial *#1234# and paste here what appears.
Click to expand...
Click to collapse
AP: I9505XXUGNE5
CP: I9505XXUGNE5
CSC: I9505OXAGNE5
Thank you so much for giving us a hand!!
Chikara71:
I know it just cant be the two of us from such diferent places in the world but, i just cant find any similar in any post or google. It has been almost 3 months from the update an me using another phone...
Well I thought I would post again to close the loop.
After Samsung tried 5 times to fix my phone, checking hardware and trying to reinstall the OS with no luck, they suggested I try replacing my SIM card.
Surprise surprise, it has fixed the problem with no recurrence yet after a week so far.
I still don't understand how the sim card could be the problem, especially as my phone was working perfectly right up to the Kitkat software update. All I can assume is somehow KitKat either had an incompatibility with my simcard (maybe the new sim is technically slightly different?) or maybe KitKat somehow changed something on the simcard, if that's even possible.
Interestingly, I did contact my telco first, and they told me to contact Samsung. As it turned out, the fix was in the control of the telcom right from day one.
Anyway, so far the problem is resolved, so I thought I would post this here to help anyone that may have this problem.
So the title pretty much states the problem. After the last update of MIUI 12, my Redmi Note 7 went crazy.
All of the calls that I get (incoming) are shown as "Unknown number" or "Anonymous". Even if I have that number saved in my address book, it just doesn't decode it.
Another problem which has risen with this update is calling without country prefix. Before this update I could enter number with local code (number 8) which would look like 8-6234567. Now if I dial number in such format, the call automatically ends without any further information. It doesn't even start to dial it, just cancels the call. I must specifically put in number with the country code so it looks like +370-6234567. This is very annoying and I should note that before the update this worked without any issues.
Things I've tried:
Flashing older version of MIUI (didn't help, tried 11.0.3 and MIUI 10). I guess something was changed deeper with this update.
Forcibly enabling VoLTE with special code *#*#86583#*#*. This helped with the number prefix issue, I can call using local prefix again, however issue of "Unknown number" on incoming calls still persist.
Clearing app cache, enabling all storage permissions on Contacts and dialer app didn't help as well
Perhaps anyone has had similar issues and found the solution?
A short Google search. Maybe it help
https://c.mi.com/thread-3208259-1-0.html
joke19 said:
A short Google search. Maybe it help
https://c.mi.com/thread-3208259-1-0.html
Click to expand...
Click to collapse
I have tried all of the following steps, sadly they didn't work. I think if it was such "top level" issue like app cache or some settings, fresh flash of an older version MIUI would have helped, but it didn't.
tauriuxx said:
I have tried all of the following steps, sadly they didn't work. I think if it was such "top level" issue like app cache or some settings, fresh flash of an older version MIUI would have helped, but it didn't.
Click to expand...
Click to collapse
Sorry, no idea. I use xiaomi.eu long time and never had this bug. With customers roms was it a bug by Google phone and contacts with permissions.
Alright so I have managed to solve this issue, although solution was very interesting. After tedious work of many re-flashes which didn't work, uninstalling apps and stuff I decided to test other SIM cards as the last resort, to make really sure that the phone has an issue.
After putting in another SIM, to my surprise everything worked perfectly. No issues with "Unknown caller", no problem with dialing numbers without country prefixes and so on.
This gave me clues that perhaps the phone itself isn't broken, but the SIM card is. I tested a few other SIM's just to be sure and all of them worked flawlessly. Therefore I just went to my provider and asked them to replace my SIM card. They did it in a few minutes and it was absolutely free.
And this worked. Now my phone works as it was working before. I've never faced such issue with SIM card and I still don't know if it was a coincidence or did the MIUI 12 update change something in the SIM firmware and it broke, because it was absolutely good before the update.
TLDR: I replaced my SIM card because apparently it was faulty (I know it is strange but that happens I guess).
Hi..All
I also got same problem after SIM change, actually I switched on the VoLTE in SIM setting.
the solution for me is (GO TO SETTING>SIM Card & mobile networks>select your prefered SIM>TURN OFF VoLTE) by doing this my problem has been solved.