Hi all. Not sure if this is a general Android problem or a Samsung issue but posting here to see if anyone else is having this issue. Upon using the Hey Google voice command, the green light in the corner indicating the mic is in use turns on, but nothing pops up and no Google Assistant is visible. If I tap on the green light it tells me Google is using the mic (obviously), so I go into the mic permissions from there and toogle off and then on the Google Assistant mic permissions. I can then use the voice command and Google Assistant will come up as usual. This then repeats many times per day.
Is anyone else having similar issues? I have tried all fixes I've seen online and nothing helps.
If the Google command is not working despite the microphone light being on, there could be a few possible reasons. Here are some troubleshooting steps you can try:
Check your internet connection: Ensure that you have a stable internet connection. Voice commands require an active internet connection to function properly.
Restart your device: Sometimes, a simple restart can resolve temporary issues. Try restarting your device and see if the Google command starts working again.
Clear cache and data: Go to the settings of the Google app or your web browser and clear the cache and data. This can help resolve any temporary glitches that might be causing the issue.
Check microphone settings: Make sure that the microphone is enabled and properly configured on your device. You can do this by going to the settings and checking the microphone settings.
Update Google app or browser: Ensure that you have the latest version of the Google app or web browser installed. Updates often contain bug fixes and improvements that can address issues with voice commands.
If none of these steps resolve the problem, it may be a more complex issue that requires further troubleshooting or assistance from technical support.
Arun.k2742 said:
If the Google command is not working despite the microphone light being on, there could be a few possible reasons. Here are some troubleshooting steps you can try:
Check your internet connection: Ensure that you have a stable internet connection. Voice commands require an active internet connection to function properly.
Restart your device: Sometimes, a simple restart can resolve temporary issues. Try restarting your device and see if the Google command starts working again.
Clear cache and data: Go to the settings of the Google app or your web browser and clear the cache and data. This can help resolve any temporary glitches that might be causing the issue.
Check microphone settings: Make sure that the microphone is enabled and properly configured on your device. You can do this by going to the settings and checking the microphone settings.
Update Google app or browser: Ensure that you have the latest version of the Google app or web browser installed. Updates often contain bug fixes and improvements that can address issues with voice commands.
If none of these steps resolve the problem, it may be a more complex issue that requires further troubleshooting or assistance from technical support.
Click to expand...
Click to collapse
Unfortunately I did all of that besides clear the Google app completely because that is a nightmare...but if it keeps happening I may have to. All of the normal stuff I've tried.
So I did clear Google app data and it's still happening as of tonight. I'm on a locked S23 ultra in the US directly from Samsung so I don't know how something like could break this badly without being rooted or something.
I've had this happen to me. I am rooted and on dr.ketan ROM.
After wiping data and setting up Google app again it starts working, but stops again the next day.
I have 2 same phones that are basically mirrors as far as setup and this was only happening to one of them.
After many attempts including clearing data and setting up Google app again it always stopped working on the next day.
Eventually I restored TWRP back up which is from before the problem occurred. Now it is working again.
This is why I would never use a phone without root or TWRP.
Had this problem too until yesterday, it was just an issue with the specific app Version of Google.
Newest Update fixed it
Arun.k2742 said:
If the Google command is not working despite the microphone light being on, there could be a few possible reasons. Here are some troubleshooting steps you can try:
Check your internet connection: Ensure that you have a stable internet connection. Voice commands require an active internet connection to function properly.
Restart your device: Sometimes, a simple restart can resolve temporary issues. Try restarting your device and see if the Google command starts working again.
Clear cache and data: Go to the settings of the Google app or your web browser and clear the cache and data. This can help resolve any temporary glitches that might be causing the issue.
Check microphone settings: Make sure that the microphone is enabled and properly configured on your device. You can do this by going to the settings and checking the microphone settings.
Update Google app or browser: Ensure that you have the latest version of the Google app or web browser installed. Updates often contain bug fixes and improvements that can address issues with voice commands.
If none of these steps resolve the problem, it may be a more complex issue that requires further troubleshooting or assistance from technical support.
Click to expand...
Click to collapse
Bro..are/were you part of Google tech support? Your trouble shooting steps uncannily resembles the same steps that Google tech support would normally advice!
So this is still happening, even after all updates, many clearing cache and data, many restarts of the phone. It will work initially, and then the next time I need it the mic light will come on and google assistant doesn't pop up. Anyone else perhaps have had this happen?
xgerryx said:
So this is still happening, even after all updates, many clearing cache and data, many restarts of the phone. It will work initially, and then the next time I need it the mic light will come on and google assistant doesn't pop up. Anyone else perhaps have had this happen?
Click to expand...
Click to collapse
This happened again to me yesterday. I went to app info, cleared cache and force stopped Google app, then without opening the app said "hey Google" and it started working again. It still works today. Hopefully it will stay that way.
xgerryx said:
So this is still happening, even after all updates, many clearing cache and data, many restarts of the phone. It will work initially, and then the next time I need it the mic light will come on and google assistant doesn't pop up. Anyone else perhaps have had this happen?
Click to expand...
Click to collapse
I have a sort of similar issue where randomly google assistant will just stop waking up to the hey google command. I have found in my case if you go into default apps then switch the default assistant to a different option and then set it back to Google it resolves my issue for a while. May not work in your case but worth a try.
tiho5 said:
This happened again to me yesterday. I went to app info, cleared cache and force stopped Google app, then without opening the app said "hey Google" and it started working again. It still works today. Hopefully it will stay that way.
Click to expand...
Click to collapse
Yea this does work temporarily. I tried it again just now and it happened exactly the way I described before. Just the mic light, nothing popped up, tap the mic light, mic being used by Google. Just a total disaster at this point. I can only hope that the June update (if we ever get one) somehow fixes this.
znel52 said:
I have a sort of similar issue where randomly google assistant will just stop waking up to the hey google command. I have found in my case if you go into default apps then switch the default assistant to a different option and then set it back to Google it resolves my issue for a while. May not work in your case but worth a try.
Click to expand...
Click to collapse
Setting the default app to something else for assistant and then putting it back to Google had no effect for me. Still wasn't working until I cleared cache and force stopped Google.
Related
To begin I love this ROM, it removes all the bloat and looks great; I just have a few problems I can't seem to resolve.
1. When I first set up my google account I managed to sync my gmail, contacts, etc. just fine to the phone. However when I tried to use either Google Plus or Google Now I was receiving both connection errors or security errors (Couldn't sign in - A problem occurred while communicating with Google Servers.). I managed to solve the latter by removing the network time synchronization options, however the connection problem persists. If I leave these options disabled all of my google apps cease to function so I've re-enabled them. Note at no point in time did my data stop working, I can browse the net just fine on the phone.
I have noticed that someone did post about similar issues in the main thread for the rom, however I was unable to find the solution they used to solve the problem. I would appreciate any help that could be provided.
If it is of any help I did attempt to flash Speed Rom, and it doesn't have these issues, so it leads me to believe it is some sort of configuration error.
2. GPS doesn't appear to be getting a lock. I'm indoors so this may be the reason for it not working, however the icon shows that it has gathered a lock, but my accuracy remains at 30 meters. I will test this further when I am out and about tomorrow to see if it works any better.
1. This problem came from Google server that has been widely reported on other forums as well. Honestly I don't know how to fixed it but I would recommend you try to re-flash the rom. Perhaps the data were save while Google server acted up and hence it saved to your phone. I personally turn-off the Google Now since it consumed too much battery though.
2. GPS: Download GPS Status & Toolbox or Faster Fix to get the right regional for your location. read the description when downloading those app since they may required Busybox installed
In order for GPS fast and accurate locked, sometime you need to turn-on Google Location service
Good luck
First and foremost, thank you for your response.
I did as you suggested and re-installed the rom. This time before doing anything else I enabled only my wifi and attempted to add an account right away.
System Settings > Accounts & sync > ADD ACCOUNT
Doing this left me with the following message:
"Couldn't sign in
Can't establish a reliable connection to the server.
This could be a temporary problem or your android device may not be provisioned for data services. If it continues, call Customer Care."
Note this is over wifi not 3G. I have tried a few times to re-flash this rom and that doesn't seem to help. Any other idea's?
Did you, by any chance, turn-on data in setting>mobile data ?
This last time I didn't. Since I was using wifi I figured I wouldn't need to turn on my data?
jay-pee said:
This last time I didn't. Since I was using wifi I figured I wouldn't need to turn on my data?
Click to expand...
Click to collapse
Doesn't hurt to try my friend
By turning on 3G I have managed to log into my account and have it sync. However I am still getting a "Sign-in error".
Also the browser was unable to sync so I've disabled that. Now when I launch Google Plus I get the following:
"No connection
Couldn't connect to the server."
And with Google Now I'm getting
"Network error..."
Had this problem earlier too. It happened to me because I didn't do a data wipe when upgrading from Craigtuts earlier rom. HTH
Sent from my HTC Amaze 4G using xda app-developers app
Just a quick update, I have managed to get this ROM working.
There was suggestion in the original thread, by Ninjistix, for this ROM suggesting the installation of SpeedROM 7.8. Once installed go ahead and log into your google account, then flash this ROM by "formatting" / "wiping" everything except data. THIS DID NOT WORK FOR ME.
Out of desperation, I decided to restore my backed up STOCK rom. After doing so I, I logged into my google account and found that everything was working, no sign-in errors from anything at all. So I wiped everything EXCEPT data, flashed this rom and its been working perfectly since.
I'd like to thank Ninjistix for inspiring my fix and craigtut for making such a beautiful rom. Hopefully one of these two methods works for everyone else trying to flash this ROM.
Original Post - Suggestion
jay-pee said:
Just a quick update, I have managed to get this ROM working.
There was suggestion in the original thread, by Ninjistix, for this ROM suggesting the installation of SpeedROM 7.8. Once installed go ahead and log into your google account, then flash this ROM by "formatting" / "wiping" everything except data. THIS DID NOT WORK FOR ME.
Out of desperation, I decided to restore my backed up STOCK rom. After doing so I, I logged into my google account and found that everything was working, no sign-in errors from anything at all. So I wiped everything EXCEPT data, flashed this rom and its been working perfectly since.
I'd like to thank Ninjistix for inspiring my fix and craigtut for making such a beautiful rom. Hopefully one of these two methods works for everyone else trying to flash this ROM.
Original Post - Suggestion
Click to expand...
Click to collapse
thanks for the shout out, i was just coming here to direct you to one of my other post's related to that annoying sign-in error, we still haven't figured out the main reason behind it yet, but i as long as we have the work around of keeping the (user) data then i guess "all's well that ends well"
I've been troubleshooting voice recognition issues for a while now dating back to the GS3 before I got the GN2. So this will not be phone specific.
This applies to an unrooted and locked GN2. In other words, full stock. I am running Go Launcher but that should not matter.
Statement of Problem ("Problem"): Google Now voice search, and Google voice recognition from keyboard microphone buttons, will often not connect to Google over 3G/4G with valid data connection, with the screen showing "Initializing" (when on Google Now) for 20 seconds and then "Can't connect to Google" message, or a frozen/suspended microphone icon when attempting voice recognition via keyboard. Note: The Problem does NOT happen when on WiFi.
Analysis: Google Now and Google voice recognition services work fine on wifi. When driving, signal shows 3G or 4G with 2 or more signal bars, however, Problem symptoms appear.I confirm 3G/4G data because web browsers work and Google Play store works.
During troubleshooting, I learned that Google Now and Google voice recognition services require an active internect connection - however I have confirmed I do have an active internet connection via 3G/4G because Google Play works. The stock voice recognition via stock keyboard does NOT require active internet connection. I have confirmed that the mic button on the stock keyboard always works over 3G/4G. I have confirmed the mic on Swift Key keyboard, when Google voice services is selected as input mode, does not work on 3G/4G but does on wifi. But this cant be a Swift Key issue because whenever the mic does not work, Google Now voice recognition does not work.
What I have ruled out: It always works on wifi. Almost always does not work on 3G/4G despite confirmed signal. I turned OFF wifi just in case the code has a bug thinking there should be a wifi signal which is not present. I tried turning OFF Google Now and still have same problems with Google search and Google voice recignition.
What I think i found: I uninstalled the Play Store Update for Google Search to return Google Search to stock version of Google Search App. As soon as I do that, Google Now and Google voice recognition services work again over 3G/4G.
Is anyone else experiencing this problem? If so, can you try and uninstall the Google Search update and go back to the Google Search stock app to see if it works? You can always reinstall the update to compare.
I am out of ideas. I want my Google Now and Google voice recog over 3G/4G in addition to wifi.
Adam
P.S. One last note..... I searched high and low on the internet and cannot find folks with this problem. So that tells me maybe it is a setting on my phone? But I am good at this... I cant figure it out. If my un-installationof the Google Search Update fixes this... I may have found an unreported bug! I am testing this solution now over next 48 hours.
I had the same problem couple times when not on wifi at home. Not big deal for me but will keep it in mind in case it go worst. Thanks
Sent from my SCH-I605 using Tapatalk 2
voice
I notice the problem after I got the Samsung Galaxy Note 2 from Verizon, and updated Google search. The Voice to text stopped working. That first update I believe was on December fifth 2012, and then the update of Google search today, December 13th 2012.
First update: 12/5/2012,
Second update: 12/13/2012.5pm EST
App update of Google Search
The app update downloaded just fine, no issues with the updated download at all.
No error messages at all.
When I install the update, the microphone on voice to text just times out. I can go to Google Now and when I hit the mic there it will time out a few times, but eventually it will light up and work that 1 time. Then have to hit it a few more times to get it again. But with text messaging, won't work at all. If I have already clicked on the mic button, and I get a notification of a new email, which goes to my bluetooth, it will light up and work that one time. Also just noticed that after the update, if I go to settings: bluetooth, and un click media audio, the update mic will then work. I have tried a few different bluetooth earpieces, blueant Q2, jawbone era, Motorola elite flip, and Motorola Silver, all with the same outcome.After update of Google Search, voice mic will not work unless media audio is un-checked, but then I lose navigation and all other messages to the bluetooth.
AdamHLG said:
I've been troubleshooting voice recognition issues for a while now dating back to the GS3 before I got the GN2. So this will not be phone specific.
This applies to an unrooted and locked GN2. In other words, full stock. I am running Go Launcher but that should not matter.
Statement of Problem ("Problem"): Google Now voice search, and Google voice recognition from keyboard microphone buttons, will often not connect to Google over 3G/4G with valid data connection, with the screen showing "Initializing" (when on Google Now) for 20 seconds and then "Can't connect to Google" message, or a frozen/suspended microphone icon when attempting voice recognition via keyboard. Note: The Problem does NOT happen when on WiFi.
Analysis: Google Now and Google voice recognition services work fine on wifi. When driving, signal shows 3G or 4G with 2 or more signal bars, however, Problem symptoms appear.I confirm 3G/4G data because web browsers work and Google Play store works.
During troubleshooting, I learned that Google Now and Google voice recognition services require an active internect connection - however I have confirmed I do have an active internet connection via 3G/4G because Google Play works. The stock voice recognition via stock keyboard does NOT require active internet connection. I have confirmed that the mic button on the stock keyboard always works over 3G/4G. I have confirmed the mic on Swift Key keyboard, when Google voice services is selected as input mode, does not work on 3G/4G but does on wifi. But this cant be a Swift Key issue because whenever the mic does not work, Google Now voice recognition does not work.
What I have ruled out: It always works on wifi. Almost always does not work on 3G/4G despite confirmed signal. I turned OFF wifi just in case the code has a bug thinking there should be a wifi signal which is not present. I tried turning OFF Google Now and still have same problems with Google search and Google voice recignition.
What I think i found: I uninstalled the Play Store Update for Google Search to return Google Search to stock version of Google Search App. As soon as I do that, Google Now and Google voice recognition services work again over 3G/4G.
Is anyone else experiencing this problem? If so, can you try and uninstall the Google Search update and go back to the Google Search stock app to see if it works? You can always reinstall the update to compare.
I am out of ideas. I want my Google Now and Google voice recog over 3G/4G in addition to wifi.
Adam
P.S. One last note..... I searched high and low on the internet and cannot find folks with this problem. So that tells me maybe it is a setting on my phone? But I am good at this... I cant figure it out. If my un-installationof the Google Search Update fixes this... I may have found an unreported bug! I am testing this solution now over next 48 hours.
Click to expand...
Click to collapse
AdamHLG said:
What I think i found: I uninstalled the Play Store Update for Google Search to return Google Search to stock version of Google Search App. As soon as I do that, Google Now and Google voice recognition services work again over 3G/4G.
Click to expand...
Click to collapse
This solved another problem that was driving me nuts. Over Wi-Fi or 3/4G unlocking via personalized voice commands in S Voice (other than "Hi Galaxy") weren't working at least 75% of the time in totally quiet rooms. Uninstalling the Search update reversed the percenteges. Also getting S Voice to properly record the personalized voice commands was a hit or miss mess. That's not an issue now either. Google's got some work to do.
So far after 24 hours the Problem I identified in the first post is solved provided the Google Search update is NOT installed.
AdamHLG said:
I've been troubleshooting voice recognition issues for a while now dating back to the GS3 before I got the GN2. So this will not be phone specific.
This applies to an unrooted and locked GN2. In other words, full stock. I am running Go Launcher but that should not matter.
.
Click to expand...
Click to collapse
This might not even be device specific. I believe this is the same issue I observed on my wife's Galaxy Nexus this weekend. She just got the phone a couple of weeks before me, but doesn't really explore all the features. I was trying to demonstrate how cool Google Now and Voice was.....needless to say, the performance issues as you've noted here pretty much soured her to the idea of even bothering to use Voice search and google now.
I'll see if she has the update and try uninstalling it.
I haven't had any issues with it on my Note 2 however.
Confirmed on my phone that this happens. But I also found out that if I click the mic before waiting for everything to load in Google Now, the issue doesn't occur. Very odd...
Sent from my SCH-I605 using XDA Premium HD app
I can confirm that the after one week of testing, the Problem disappears if the Google Search update is removed. Once I add the update back, the Problem begins again.
There is very little on the internet about this from my searching. It seems others on this thread can confirm the issue. Do you other guys not notice this happening or do you not use Google Now while on 3G/4G and no WIFI. If it's working for you (the majority of the time), do you have the Google Search update installed or is your phone factory stock and you never updated Google Search from the Play Store?
By the way I am not rooted or unlocked.
How do I tell Google about this? I mean someplace real where they'll respond if they know about it or log it for an app update? (yeah right).
Im root but I have not experience any problem. You can post your finding here http://code.google.com/p/android/issues/list
Sent from my SCH-I605 using Tapatalk 2
Uninstalling Google Search did not solve the problem for me!
AdamHLG said:
I can confirm that the after one week of testing, the Problem disappears if the Google Search update is removed. Once I add the update back, the Problem begins again.
There is very little on the internet about this from my searching. It seems others on this thread can confirm the issue. Do you other guys not notice this happening or do you not use Google Now while on 3G/4G and no WIFI. If it's working for you (the majority of the time), do you have the Google Search update installed or is your phone factory stock and you never updated Google Search from the Play Store?
By the way I am not rooted or unlocked.
How do I tell Google about this? I mean someplace real where they'll respond if they know about it or log it for an app update? (yeah right).
Click to expand...
Click to collapse
I have been searching the net to solve this problem and came across your post. This solution did not work on my Note 2. Very frustrating as the ability to speak a text is very convenient and necessary for me. I press the button and can not get the red to appear. When on WiFi it works. Please help with this because not a lot of folks are having the issue as nothing online....this may be the only thing. REALLY NEED THIS FEATURE! HELP!!!!!
Thanks! I'll post the issue to Google using that link.
Sent from my SCH-I605 using Tapatalk 2
Confirming.
Worked when I first loaded a custom rom...then after a week or so, Google search would just initialize. Based on this thread, I went into application manager and saw "Uninstall Update" which I did....now I'm gold again...
THANKS
Hello folks. Been lurking on the forums, grabbing what info and software and tips I needed for a couple years, but never had a need to post something. Now, the problem has been described already in the topic title, but I'll elaborate.
Somewhere in a period of 24-36 hours of being turned on continuously, my phone (a Sony Xperia Go with Cyanogenmod 11 running on it, but the problem was there before with stock rom too) needs to be rebooted, else I can't receive or send text messages or call. The text messages simply won't be sent and I don't get a waiting tone (or any sound for that matter) when I try to call and it'll eventually fail.
Now when I still used a stock rom, I'd see that I had lost network connection, but on the current Cyanogenmod build I still have full bars. This issue I then have to fix by rebooting my phone, as I stated. I have not tried setting it to airplane mode for a quick fix, but in all honesty, I'm looking for a permanent fix, not a temporary one. And this also seems to be an issue that isn't just with my type of phone.
I tried looking for a solution already several times, but all I could find that described my problem was this thread. I have not tried ordering a new sim card from T-Mobile yet, since that costs money over here in the Netherlands, and I wanted to make sure I had exhausted every possible software fix before trying to fiddle with hardware.
Hope this is enough information for you guys to at least tell me something. Even if it's "yup, you're boned."
Gentle bump. Apologies for doing so, but I'm fairly certain I'm not the only one with this problem.
I'm having this same issue. I'm running the latest stable build of CyanogenMod on Maguro (CM11/Snapshot7). I push my SMS's through Google Voice (using CM Voice+ which is now integrated into the systems menu). I didn't notice exactly when the problem started because I have Hangouts and SMS integrated in the Hangouts app, and chat with people using both all the time. I do know that The problem didn't start after a CM update, it happened in the middle of the day while the phone was on as far as I can tell. Since then I have tried clearing caches, updated to the newest nightly release, and so forth to no avail. Rather than rebooting, I can just turn on airplane mode and turn it off to get my SMSs, but still quite a bother.
Did OP figure this out?
Nope. I ended up having to get a new phone, as it was getting worse and worse, up to a point where I had to reset it every hour. I just assumed it was a hardware problem and got a new phone.
I did a factory reset / complete reinstall and still have the problem.
After the reset and recovery, I assumed it was a telephony issue and messed with the APN and data settings as much as I could, including checking and editing the default databases. No avail.
I uninstalled Google Voice and turned off Voice+ and SMS's began working with my SIM number. Bingo! So I started messing with Google settings. Log out, log in. Reinstall apps, etc. I eventually discovered that whenever I tried to clear the cache on my Google Play Services my Settings would crash. So i figured that I had a corrupted Google Play Services, which was preventing my phone from syncing with Google Servers except on reboot or connection refresh. I later realized that I should have been tipped off to this by the orange wifi/wireless icons in my Settings dropdown.
I couldn't uninstall or update Google Play Services so I just downloaded the latest version of CM GAPPS, cleared app and Dalvik caches, and flashed GAPPS into place.
Bing, bang boom... it still didn't work. Icons still orange, Google Play Services still crashes when I try to open it from Settings>Apps.
Not sure what to do next except maybe another factory reset, and instead of using Titanium Backup to restore, I will just load a fresh version of CM11 and not update it. ??
Hey,
I'm suffering some issues with two Samsung mobiles, namely a S3 and a Note2. Push notifications simply won't work reliably on both devices (lacking a data-capable SIM, I could only test on wifi, where other devices work like a charm).
I flashed with M9, then went to nightly, flashed the most recent GApps, and also tried push notification fixer, disabled wifi optimization, re-logged in via Hangouts, to no avail. Without a visible pattern, one or both devices fail getting GCM messages at all. Moving the device to airplane mode and back seems to newly roll the dice.
Wifi on those devices work, as I could ping them reliably, it's just GCM that doesn't work, visible in apps like Threema, but also in the Android device manager that is unable to locate the device, or the Play store when I remotely try to install an app. Putting the device on (unlocking not required) seems to cure the problem for a little while.
Having researched a bit, I'm quite clueless. As both devices IMHO are the same Exynos platform, and have been cleanly installed just a few days ago, is that maybe a known issue, related to Android 4.4 and wifi drivers?
Any chance of debugging GCM to see where the issue is?
Thanks!
AndroUser83 said:
Hey,
I'm suffering some issues with two Samsung mobiles, namely a S3 and a Note2. Push notifications simply won't work reliably on both devices (lacking a data-capable SIM, I could only test on wifi, where other devices work like a charm).
I flashed with M9, then went to nightly, flashed the most recent GApps, and also tried push notification fixer, disabled wifi optimization, re-logged in via Hangouts, to no avail. Without a visible pattern, one or both devices fail getting GCM messages at all. Moving the device to airplane mode and back seems to newly roll the dice.
Wifi on those devices work, as I could ping them reliably, it's just GCM that doesn't work, visible in apps like Threema, but also in the Android device manager that is unable to locate the device, or the Play store when I remotely try to install an app. Putting the device on (unlocking not required) seems to cure the problem for a little while.
Having researched a bit, I'm quite clueless. As both devices IMHO are the same Exynos platform, and have been cleanly installed just a few days ago, is that maybe a known issue, related to Android 4.4 and wifi drivers?
Any chance of debugging GCM to see where the issue is?
Thanks!
Click to expand...
Click to collapse
Are you apply or modifying anything to do with battery saving?
Have you tried reseting to factory setting, wiping /system and /data (warning you will lose all data so backup). reinstall rom gapps plus those specific apps that don't work and tested it?
Thanks for your reply!
Are you apply or modifying anything to do with battery saving?
Click to expand...
Click to collapse
No, not at all.
Have you tried reseting to factory setting, wiping /system and /data (warning you will lose all data so backup). reinstall rom gapps plus those specific apps that don't work and tested it?
Click to expand...
Click to collapse
I did so before installing the system, both devices are a completely fresh setup, incl. wiping of system and data. I thought I had luck with wiping cache & dalvik as it worked yesterday, but today, once again, only one of those devices works.
Seems in fact GCM loses connection on one of the devices (the second one seems to work like a charm now). Removed Google account and re-added it, but status in *#*#426#*#* shows google play failed connection ev:1 err:16 net:1
No idea how to fix that though ;-(
If you have done a complete clean flash and not touched any settings im afraid im out of ideas.
Is anyone else experiencing issues with the GPS not working? The phone is able to determine my current location but is unable to actually navigate anywhere. Google maps never shows an arrow to indicate the GPS is locked. I've also used several Gps app to help correct it. I've done multiple resets and app updates I've even sent the phone back to Nokia twice just for them to tell me nothing is wrong. My phone is running the latest update as of March 11. Please help!
Andronoob1 said:
Is anyone else experiencing issues with the GPS not working? The phone is able to determine my current location but is unable to actually navigate anywhere. Google maps never shows an arrow to indicate the GPS is locked. I've also used several Gps app to help correct it. I've done multiple resets and app updates I've even sent the phone back to Nokia twice just for them to tell me nothing is wrong. My phone is running the latest update as of March 11. Please help!
Click to expand...
Click to collapse
Review your 'Location' settings.
Go to Settings - - > Security & Location
Look for Location (it should say On) press to open Location menu screen, review all options shown.
Near bottom of list look for Scanning and select. This will bring up options to use wifi and Bluetooth to scan for positioning. Turn them both on.
They help even when not using. System uses to triangulate (better identify location).
Also check 'Google Location Accuracy'. I know from experience if that selection is off GPS will work, but navigation Apps are fairly useless.
Some suggestions. Hope it helps.
bkttk2 said:
Review your 'Location' settings.
Go to Settings - - > Security & Location
Look for Location (it should say On) press to open Location menu screen, review all options shown.
Near bottom of list look for Scanning and select. This will bring up options to use wifi and Bluetooth to scan for positioning. Turn them both on.
They help even when not using. System uses to triangulate (better identify location).
Also check 'Google Location Accuracy'. I know from experience if that selection is off GPS will work, but navigation Apps are fairly useless.
Some suggestions. Hope it helps.
Click to expand...
Click to collapse
Tried all of that to no avail. They were already on so switched them off then on, checked maps, restarted phone and checked again.
Andronoob1 said:
Tried all of that to no avail. They were already on so switched them off then on, checked maps, restarted phone and checked again.
Click to expand...
Click to collapse
Sorry it didn't work. Only ideas I have currently.
bkttk2 said:
Sorry it didn't work. Only ideas I have currently.
Click to expand...
Click to collapse
Thanks for the suggestions. If you've gotten anymore please let me know.
Mod edit - translated by https://translate.google.com/:
Hello, I have this problem too, there is no solution
**************************
你好，我也遇到同样的问题，没办法解决。
turn off: Google Location Accuracy, GPS will working.
when open google maps, it will ask to turn on Google Location Accuracy .... select NO!!!
On my device, this worked. Download the app "GPS Test" from F-Driod (might be in Play Store? I never looked...) https://f-droid.org/en/packages/com.android.gpstest.osmdroid/
In the app, click the "Clear assist data" wait a few minutes. I've waited between 1 - 20 minutes in the past. The GPS redoes all it's data and starts working again for me.
I had the same problem. Contacted Nokia, it's a known problem caused by an update.
About a month ago I received a new update and since then everything GPS related is working fine again.
I had the same problem and sent my phone to repair. They confirmed the issue and corrected it. Since then the GPS works well.
Relipuj said:
I had the same problem. Contacted Nokia, it's a known problem caused by an update.
About a month ago I received a new update and since then everything GPS related is working fine again.
Click to expand...
Click to collapse
Everything worked well up to today. Since today same problem again. No GPS signal... Nothing seems to get it back working again... Big disappointment!