Background:
- GSM Galaxy Nexus purchased from Play Store
- Unlocked & Rooted running stock 4.1.1
- on AT&T Network
- Came from an iPhone 4 -- some people still report their phones still try to text me as imessage, despite my having contacted AT&T repeatedly about this and going into apple and clearing out all my data as I've seen recommended online
- I have English (US) downloaded for voice typing and everywhere else it says I can download it.
With that out of the way. Whenever I'm on mobile data and I try to use Google Now, it'll hang on "initializing" for about 30 seconds, then it'll fail. When I retry, it usually works just fine and is quite quick. This problem happens intermittently, although it ALWAYS happens when I first use Google Now when I switch to mobile network.
As a frame of reference, I also have this problem with voice typing. Voice typing won't hang though, it just takes longer (at least 10 seconds) to boot up. Also, I have absolutely no issues on WiFi, other than the occasional issue of Google Now refusing to open a link even though I click it, but that's for another thread and another time.
What's going on here? How can I fix this? I really like using Google Now while driving to pick songs to listen to, but this is an incredible hassle. Thanks y'all
This is happening to me as well.... only difference is mine is NOT rooted, and I'm using NET10.
I also purchased my Galaxy Nexus Unlocked from the Play store.
Dolfan058 said:
Background:
- GSM Galaxy Nexus purchased from Play Store
- Unlocked & Rooted running stock 4.1.1
- on AT&T Network
- Came from an iPhone 4 -- some people still report their phones still try to text me as imessage, despite my having contacted AT&T repeatedly about this and going into apple and clearing out all my data as I've seen recommended online
- I have English (US) downloaded for voice typing and everywhere else it says I can download it.
With that out of the way. Whenever I'm on mobile data and I try to use Google Now, it'll hang on "initializing" for about 30 seconds, then it'll fail. When I retry, it usually works just fine and is quite quick. This problem happens intermittently, although it ALWAYS happens when I first use Google Now when I switch to mobile network.
As a frame of reference, I also have this problem with voice typing. Voice typing won't hang though, it just takes longer (at least 10 seconds) to boot up. Also, I have absolutely no issues on WiFi, other than the occasional issue of Google Now refusing to open a link even though I click it, but that's for another thread and another time.
What's going on here? How can I fix this? I really like using Google Now while driving to pick songs to listen to, but this is an incredible hassle. Thanks y'all
Click to expand...
Click to collapse
Still having this issue. It's damned annoying. I believe it has something to do with Google trying to use online voice recognition but not getting a good enough signal and subsequently failing.
Why not just default to offline? We already have the language pack installed. Wish I could choose, so that way I can setup a Tasker profile to automatically default to offline when I'm away from Wifi.
Sent from my Nexus 7 using xda app-developers app
Have this same issue too. Voice search was actually better/more reliable with ICS (hell even froyo). All I get is initializing. Annoying.
Solved!
Still no fix coming from Google, but at least one nice guy made a temp fix while they do it.
Look for "Voice Command" app on Google Play. Developer's name is IT-DEV-CROWD or code.google.com/p/android/issues/detail?id=42178#c37
It worked for me, after trying a lot of different configurations.
Related
Every so often when I run the Play Store it says "No connection". And as many times as I push the Retry button it says the same thing. Even if I force close the app
I kinda just have to wait a bit and it starts working again. I never lose network connection though. I'm betting its not actually an issue with Google's servers so I'm wondering if its an issue with my phone or setup
I'm running the latest stable aokp and Franco
Also I have the USA unlocked gsm
Sent from my Galaxy Nexus using XDA
same problem
i had a same problem like your since yesterday.
I have that too every now and then. Verizon Nexus.
Sent from my Galaxy Nexus using xda premium
I don't have this problem. VZW AOKP franco
Happened today when trying to set up Google voice... said it couldn't connect even though I had a connection
Quite annoying
Sent from my Galaxy Nexus using XDA
Same. Just happens every now and then.
P. S. I'm on CM9
Sent from my Galaxy Nexus using xda premium
Haven't had this happen.
Just had this happen. On insert coin 5.5.0 and bricked 1.1
Not working here either.. stock ROM with root and speedmod kernel. Even Gmail app is not working..
Anyone has a solution yet?
What worked for me but still no explanation
I'm a lousy member on this Forum, 2 years or so and my first post
I had 2 Nexus Ones and both of them took a swim (literally)
Gave up used BB-Gun.
Anyhow, I just obtained MyTouch 4G Slide and encountered the same problem, this place here was the last that I looked for an answers..on low/mid end Forums I've found a lot of half answers for example,
"yeah it happens"
"power off and/or restart,,it worked for me" (it didn't work for me)
My observations, at the same time that connection with G Play don't work also Google Maps does't work..Reason? No Data connection.
All was fine until I installed G Voice (conflict/ bug?)
What I did, is the following I switched to Wi-Fi, and it worked, then i uninstalled G Voice.
And tried again but this time I was connected to Wi-Fi, installed G Voice and the same problem..turned off the Wi-Fi switched to regular connection and it worked.
I know that I didn't offer any explanation or fix for the problem but there is a pattern
Fixed it!
I have found the answer! Well, at least this was what was wrong with mine:
It was just that the date on my tablet had reset to 2010. Put it back to today's date and the Play store works perfectly now.
Hope that helps.
Kay
kay_piggy_wig said:
I have found the answer! Well, at least this was what was wrong with mine:
It was just that the date on my tablet had reset to 2010. Put it back to today's date and the Play store works perfectly now.
Hope that helps.
Kay
Click to expand...
Click to collapse
Worked like a dream. I installed jellybean ((cm10) i think)) and wanted to go backto my ice cream sandwich. When i did, play store and youtube didnt work. I guess google apps in general. If google made it it said no connection. I tried uninstalling the updates and reinstalling them to no avail. I searched and found this thread. My date changed when i restored my back up. I didnt even realize it till i read this thread. My years changed to 2005. Switched it back to 2012 and no problems. Network connection fine. Thanks alot.
I have a Play Store GSM Nexus running stock rooted Jellybean and this sounds crazy but it reboots when I go to a Stop and Shop grocery store (a grocery store chain in the Northeast US). When I go to this store, I usually wake my phone and use my Key Ring app to scan the barcode at the Scan It station (this is a handlheld wireless scanner that lets shoppers scan while they shop and just pay for the whole cart at checkout).
After the JB update, I was having reboot problems which I thought were related to the Key Ring app. I cleared data on that app and this went away. Since then, I have returned to the store and the rebooting still occurs after waking the phone not when trying to do something specific. While in the store the phone will boot up but remains very sensitive and reboots often. After leaving the store, everything runs fine. I was not until I went to the store again today that I finally made the coorelation.
Could something in that store really be causing my phone to reboot? They do have a Scan It Mobile app which allows the entire scanning function to work on the phone without using one of the store scanners but I have never installed it or tried it on any of my devices. So they have a system in the store that can communicate with phones unless the information is shared over 3G. The handheld scanner certainly are wireless but I am not sure which band. I checked the Scan It Mobile app reveiws on the Play Store and there are a couple bad reviews with notes "Don't install this on a Nexus running Jellybean or it will cause reboots". But again, I don't even have the app installed.
orb_526 said:
I have a Play Store GSM Nexus running stock rooted Jellybean and this sounds crazy but it reboots when I go to a Stop and Shop grocery store (a grocery store chain in the Northeast US). When I go to this store, I usually wake my phone and use my Key Ring app to scan the barcode at the Scan It station (this is a handlheld wireless scanner that lets shoppers scan while they shop and just pay for the whole cart at checkout).
After the JB update, I was having reboot problems which I thought were related to the Key Ring app. I cleared data on that app and this went away. Since then, I have returned to the store and the rebooting still occurs after waking the phone not when trying to do something specific. While in the store the phone will boot up but remains very sensitive and reboots often. After leaving the store, everything runs fine. I was not until I went to the store again today that I finally made the coorelation.
Could something in that store really be causing my phone to reboot? They do have a Scan It Mobile app which allows the entire scanning function to work on the phone without using one of the store scanners but I have never installed it or tried it on any of my devices. So they have a system in the store that can communicate with phones unless the information is shared over 3G. The handheld scanner certainly are wireless but I am not sure which band. I checked the Scan It Mobile app reveiws on the Play Store and there are a couple bad reviews with notes "Don't install this on a Nexus running Jellybean or it will cause reboots". But again, I don't even have the app installed.
Click to expand...
Click to collapse
Clearly your phone has gained awareness and is telling you to not shop there. I'd take heed.
On a serious note, the building is probably causing tower signal interference. If it severe enough, it will cause the device to reboot. JB has a weaker signal than ICS on some devices. Although some disagree with me.
I wonder if there could be a privacy issue also and jellybean isn't compatible with it so it just causes it to reboot.
Sent from my Galaxy Nexus using Tapatalk 2
Privacy issue?
One word: Skynet. LOL.
Sent from my Galaxy Nexus using xda premium
orb_526 said:
I have a Play Store GSM Nexus running stock rooted Jellybean and this sounds crazy but it reboots when I go to a Stop and Shop grocery store (a grocery store chain in the Northeast US). When I go to this store, I usually wake my phone and use my Key Ring app to scan the barcode at the Scan It station (this is a handlheld wireless scanner that lets shoppers scan while they shop and just pay for the whole cart at checkout).
After the JB update, I was having reboot problems which I thought were related to the Key Ring app. I cleared data on that app and this went away. Since then, I have returned to the store and the rebooting still occurs after waking the phone not when trying to do something specific. While in the store the phone will boot up but remains very sensitive and reboots often. After leaving the store, everything runs fine. I was not until I went to the store again today that I finally made the coorelation.
Could something in that store really be causing my phone to reboot? They do have a Scan It Mobile app which allows the entire scanning function to work on the phone without using one of the store scanners but I have never installed it or tried it on any of my devices. So they have a system in the store that can communicate with phones unless the information is shared over 3G. The handheld scanner certainly are wireless but I am not sure which band. I checked the Scan It Mobile app reveiws on the Play Store and there are a couple bad reviews with notes "Don't install this on a Nexus running Jellybean or it will cause reboots". But again, I don't even have the app installed.
Click to expand...
Click to collapse
I'm having the same issue. I have a Verizon Samsung Galaxy Nexus running Bugless Beast Jelly Bean .
I was in a Giant Grocery Store that has the Scan-it program. I had poor 4G reception, so I tried to connect to the store's wifi. I didn't realize that he wifi that I was connecting to was for the Scan-it program. I phone continue to reboot until I left the store.
Yesterday, I went to a different Giant store and pulled my phone out of my pocket to check the time and noticed that it was rebooting. This time, I was able to turn wifi off which fixed the problem. I'm positive it's the SCAN-IT WiFI that's causing the endless-reboot issue.
ryanoc said:
I'm having the same issue. I have a Verizon Samsung Galaxy Nexus running Bugless Beast Jelly Bean .
I was in a Giant Grocery Store that has the Scan-it program. I had poor 4G reception, so I tried to connect to the store's wifi. I didn't realize that he wifi that I was connecting to was for the Scan-it program. I phone continue to reboot until I left the store.
Yesterday, I went to a different Giant store and pulled my phone out of my pocket to check the time and noticed that it was rebooting. This time, I was able to turn wifi off which fixed the problem. I'm positive it's the SCAN-IT WiFI that's causing the endless-reboot issue.
Click to expand...
Click to collapse
Odd, I have a GSM nexus and have no issues going to Giant. (I also thought their WiFi was for internet, not the scanners). My phone never rebooted even if I connected to the Scan-It network.
So I went to a different Stop and Shop yesterday and confirmed the association with WiFi. I stood in front of the scanner stand and the phone was working fine. I than switched on the WiFi and the phone instantly rebooted.
Thinking about it later at home, I went into the WiFi settings and found a remembered network "scanit_mobile". I selected it and chose "forget". I must have tried to connect to it a long time ago on ICS thinking that it might give WiFi access in the stores which do typically have bad data service. Something that the network is doing does not play well with JB. That is my best theory anyway. I need to go back and test if this fixes the reboots. It still does not explain how it is happening though.
Sent from my Xoom using Tapatalk 2
The wifi is the problem; affects Nexus S (with Jelly Bean) also
I can confirm that the wireless is the issue. Before the JB update, my Nexus S worked fine with the Scan-It program. Since that program requires you to associate with their internal wifi network (ScanIt_Mobile), it was one of the saved networks and my phone kept trying to associate with it. Each time it began to boot, it would almost immediately reboot until I jumped in and quickly forgot the network from the wifi settings. When I tried to reconnect, it restarted the boot loop.
Is there any way to capture log information to diagnose what the network is doing to reboot the phone?
Got the same issue on JB Gnex. In Russia, at about every SubWay restaurant. Something's weird with their wifi, I guess. Though my macbook finds their wifi, which got no internet connection.
Ever since the Jelly Bean update the Google Voice function has been intermittently unavailable. If I keep canceling it out and opening it back up eventually it works. I did a factory reset and it didn't help. No one has posted about the issue so I wondered am I the only one? And is there a fix for it? Thanks, Jeff.
Note: Sometimes if I wait long enough the error that pops up says server unavailable.
App is called "Voice Search" by Google Inc and is version 2.1.4
You need to download "google search" that is google now. Both should be downloaded and in tts settings should be set to whatever you use. I use ivona because it sounds much better like a real voice.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Also every portion of the phone needs to be set to US english... the google now settings, tts settings, and the keyboard i believe....
It's not either of those. It's installed already and set up correctly. I even have english downloaded for offline use. I forgot to mention I'm all stock touchwiz never rooted, so there's no excuse for this issue. I don't know if the JellyBean data Keis put on my phone was corrupted somehow, or if everyone else has this issue but found a solution. That said does anyone have this problem or just me?
jeffdaman said:
It's not either of those. It's installed already and set up correctly. I even have english downloaded for offline use.
Click to expand...
Click to collapse
Well not everything gets spoken, but try to duplicate the issue again.... Ask it the same question over and over... ask it what time is it, it always reads that... then ask it who is the president of the united states, or what is the date.... all of those get read back... see if stumbles, and report back, and also report have u tried any resets or anything... stock jb?
I think I figured it out. My Smart Keyboard wants to use the voice and so did Google Voice Typing, so I unchecked the one I don't use and for the last minute I've had no issue. It will be a few days before I can be sure but I usually have this problem pretty frequently.
View attachment 1582431
jeffdaman said:
I think I figured it out. My Smart Keyboard wants to use the voice and so did Google Voice Typing, so I unchecked the one I don't use and for the last minute I've had no issue. It will be a few days before I can be sure but I usually have this problem pretty frequently.
View attachment 1582431
Click to expand...
Click to collapse
Say, "Google, do a barrel roll"
Quasimodem said:
Say, "Google, do a barrel roll"
Click to expand...
Click to collapse
It's just "do a barrel roll." Unless saying google is supposed to open search for me.
jeffdaman said:
It's just "do a barrel roll." Unless saying google is supposed to open search for me.
Click to expand...
Click to collapse
Saying google while in google now makes it listen...
I was wrong about figuring this out by un-checking one of the voice keyboards in the keyboard menu. That solution worked out of coincidence.
I found that I could fix it every time I restarted; then I found I could go into airplane mode and back out to fix it; then I tried all the things airplane mode affected and found that I could turn off Bluetooth and it would work, and when I turned on Bluetooth it would stop working. I found this while sitting in my car which connects my Bluetooth to the radio and a microphone above my head. I will try to narrow the problem down further to see if any other Bluetooth situations cause the issue, and I will report back.
I've the the problem with bluetooth as well, but I literally just started experiencing the issue without bluetooth enabled about 5 minutes ago. No matter what I do Google can't connect to the server.
goodtimes50 said:
I've the the problem with bluetooth as well, but I literally just started experiencing the issue without bluetooth enabled about 5 minutes ago. No matter what I do Google can't connect to the server.
Click to expand...
Click to collapse
Ugh don't tell me that, I've even finally rooted this thing and tried roms but they still had the issue. Now the only other solution is to set in on fire and push it down a hill....That's how we had to deal with Yeller as well
jeffdaman said:
Ugh don't tell me that, I've even finally rooted this thing and tried roms but they still had the issue. Now the only other solution is to set in on fire and push it down a hill....That's how we had to deal with Yeller as well
Click to expand...
Click to collapse
Turns out it's something with my router's configuration. When I disabled wifi on the phone it started working. Anyone have any ideas what router settings might interfere with Google's voice recognition?
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
Okay, after some Googling I setup port forwarding for port 19294 and now it's working. Not sure why this new router is blocking that port as none of the others I've used ever have...
I am experiencing this issue as well. At home on wifi, google voice comes on right away and listens. On the road (in the car and with bluetooth on) it keeps saying initializing. Today I will try voice recognition in the car with bluetooth turned off and will report back.
Is it me or is Google Now very flakey on the Note 3? It seems like a women in a menstruel cycle. Sometimes it talks back, sometimes ( more than often) she just sends me to links via Google - mute.
As an example I placed my flight information into my Google Calender, it still 9 times out of 10 not read it to me, it says something to the effect of this information is for your personal use only.
Yeah it is buggy, but it hasn't technically even been released yet, and not for use with this phone, so I guess we can't complain just yet.
Edit: I didn't take into account that you were not using the new nexus 5 Google now, so if you aren't, my bad. Other than that, I don't really use it except to get directions every once in a while..
Sent from my SM-N900T using XDA Premium 4 mobile app
Got a Note 3 right after they came out.
Had an issue with the first one, not the least of which was the pervasive WiFi disconnect issue many of us have been seeing; in my case also had extreme battery drop all of a sudden - like 45% in an hour - not abnormal use.. So, swapped it about 20 days ago for another one.
Seeing the same WiFi connectivity issue I saw with the first one and then all of a sudden got a pop up :
"Prevention Information"
An application has been forced to stop for an unauthorized attempt to access system in your device. It may be safe to delete an application obtained from an unauthorized route. Check Now? (with a Do not show for 30 days check box; Cancel or Ok buttons)
If you click cancel pop up comes back after about 10 mins more or less; if you click Ok you get brought to a list of what you have downloaded to weed through whatever you've installed.
Full disclosure: This device is out of the box, not rooted; stock Rom. Only none play store apps installed were Adobe Flash and Amazon App store. I use WiFi extensively for WiFi calling at my office, since there isn't a carrier on the planet can get me a decent signal. I live and die behind WiFi calling it's why I went T-Mobile to start with.
* So I proceed to scan hell out of this, using Lookout, Sophos and MalwareBytes can't find anything..
* Ok so I uninstall everything I've been experimenting with thinking maybe the mix is a problem. Doesn't solve it
* So then I do a software Backup and restore - and go to put back the one app I need the most for my Hosted Exchange connectivity to work the best for my needs adding them back one at a time to see what's causing this . Of course I turn WiFi back on to connect to my network and signing into my Google Account Google Play takes off to restore all my stuff and do all updates for anything stock on the phone. (Phone Vendors WAKE UP; Stop making the default Google Play behavior Up Date Automatically when on WiFi, let the user decide before taking off to do what you think is best) And - The pop up is back just as I get the 1 app I need on the phone. (email support for the app saying it's them - MANY APOLOGIES to Nitro Desk, it's not them.
* Very long story and many soft and hard resets, to try control the behavior, later; including running 2 miles up the road to control Google Play auto update on WiFi, but, only be on the T-Mobile network for the initial startup....
With nothing but a minimal start-up and No Apps installed other than what Google Play demanded to be able to work at all out of the box when signing in; once I got the phone back to the office and started WiFi for my network - Blammo ! the pop up is back.
This "error" or warning message is from the base Android/Samsung/T-Mobile deployment configuration for a Note 3 when starting WiFi at all.
So, I happen to be near the T-Mobile store I bought this at and go in to tell them about this and the guys there running a Note 3 say they all get the same issue.
My conclusion is that this is a miss-configuration of software and/or permissions at the core OS level when starting WiFi; likely contributing or the primary cause of WiFi connectivity issues on this device; as reported in this and other forums.
I have screenies of this condition and would love to pass this to T-Mobile and Samsung engineering, but, unlikely I can get at them to do so; hopefully they are already aware of this and working on a fix.
The other interesting thing I noticed is that when doing a hard reset: during the start of recovery mode I get an "error" then no command message under the little droid as it settles down to the menu.
Also at the end of the recovery mode process for wipe data/factory reset I get an "error" message in red as well.
Again, seems to me there's a serious flaw in their Core programming setting up proper permissions for the base WiFi stack to start without triggering a security violation.
It doesn't matter if you connect to an AP or not. Just starting WiFi the pop up will come up in 60 - 90 seconds.
This is consistently reproducible.
T-Mobile is sending me another phone; but, I believe it will behave the same way - hope not, we'll see.
cef1000
You really need to SEARCH before posting. There are many threads about Prevention Information and it has nothing to do with WiFi.
krelvinaz said:
You really need to SEARCH before posting. There are many threads about Prevention Information and it has nothing to do with WiFi.
Click to expand...
Click to collapse
That may be, but, in this case it is 100% reproducible under these conditions and happens if WiFi is turned on at all before any updates and before any additional apps are installed, other than the ones the Play store insists on bringing in to work properly once initially signing in, happens to me in this very limited and controlled startup of the device and only when starting WiFi and no other time in that controlled condition; before any updates or Play Store apps are installed.
It also happens after they are; so it seemed,to me at least, to have value because of the controlled diagnostic startup; since the condition is 100% reproducible using these steps and under these limited initial startup conditions, at least on the device I have in my hands at the moment.
A replacement should be here sometime today and will attempt to reproduce it on the replacement; T-Mobile tech support seems to think it will behave the same way as well; FWIW to anyone.
Thanks so much for the input and advice; duly noted.
Best regards,
cef1000
Knock yourself out....
You might try doing a simple Google Search for samsung "Prevention Information" and see just how many threads there are about this issue. It is not just the Note 3 but a number of other Samsung devices as well.
Actually it has everything to do with wifi. Knox is thinking wifi is trying to collect information from your device as if it is a type of virus. Samsung is fully aware of the issue & there is an update coming based around that specific issue.
Sent from my SM-N900T using XDA Premium 4 mobile app
sIpInWiT mYdRoId said:
Actually it has everything to do with wifi. Knox is thinking wifi is trying to collect information from your device as if it is a type of virus. Samsung is fully aware of the issue & there is an update coming based around that specific issue.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+1 Thank you slpn...
I'm glad to hear there's some fix in the works. Do you have a link handy for that? It's clear that the shipped Knox/SEAndroid configuration shipped on this device (and perhaps other Samsung models) really wasn't tuned very well before release.
OP, if you want to know more about this read some of the other threads here about Knox - the Everything Knox thread in this forum is pretty good IIRC, and the Samsung Knox whitepaper is an interesting read too (here). Basically, Samsung rolled their own solution for bring-your-own-device enterprise users, which is based in part on the SELinux extensions to Android (SEAndroid) along with some lower-level supervisory logic that's probably somewhere in the boot loader / modem / etc. [speculation] and some degree of hardware support such as the "knox warranty void" flag.
Unfortunately they developed this alongside/outside the reference implementation of SEAndroid, wrote their own APIs for interaction, etc. and don't seem to have done it terribly well. I'm tempted to ask that Samsung provide some way to actually control it, or provide a signed development FW that won't trip the hardware flag, as it really is an intrusion for non-enterprise customers. >.<
sIpInWiT mYdRoId said:
Actually it has everything to do with wifi. Knox is thinking wifi is trying to collect information from your device as if it is a type of virus. Samsung is fully aware of the issue & there is an update coming based around that specific issue.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Actually I've gotten the notification without wifi although it usually happens when I do turn it on.
Totally agree though that a simple search would have saved a HELLS of a lot of trouble. Smh
Yes it's a bug but it's not really that big of an issue. I can almost guarantee it will be fixed soon with some kind of minor update.
Well I have two other issues besides the "prevention information" for some reason my note 3 keeps giving me a unstable wifi connection when the connection to the wifi is good for example on my note 2 is perfect mo issues no lags on the note 3 however I get that unstable wifi connection, and for my second issue I get a damn google+ app crash every time im on the phone or any app . This note 3 has become a nightmare with bugs . I was wondering if anyone else has the same issues besides the prevention information ???
Sent from my SM-N900T using xda premium
westkhalifa13 said:
Well I have two other issues besides the "prevention information" for some reason my note 3 keeps giving me a unstable wifi connection when the connection to the wifi is good for example on my note 2 is perfect mo issues no lags on the note 3 however I get that unstable wifi connection, and for my second issue I get a damn google+ app crash every time im on the phone or any app . This note 3 has become a nightmare with bugs . I was wondering if anyone else has the same issues besides the prevention information ???
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
I think I had the unstable connection problem a long time ago. I may have made my phone "forget" my wifi network and obviously have connected to it since and have not have that problem. So it's possible simply "forgetting" the network, scanning, and then connecting to it again could fix it?
How often do you use Google+? Is it possible that if you hardly use it you could just sign out of the app and then it won't search for your location so much? I see the new G+ update says something about refreshing friends location more often or something, could be tied in to that?
I dont use google+ at all. It updated on its own and it started crashing since. I just turnt off all my auto updates and I uninstalled the last google+ update lets see if that does the trick .
Sent from my SM-N900T using xda premium
westkhalifa13 said:
I dont use google+ at all. It updated on its own and it started crashing since. I just turnt off all my auto updates and I uninstalled the last google+ update lets see if that does the trick .
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
You can take it how you'd like cause i know how some are when they hear about an update, not saying your one of these people who flame on the other person who try to provide helpful info about an update, but that is also being included in the update i spoke of a few posts above.
What is going on is your phone is scanning your signal & even if you have a full WiFi signal, instead of just leaving you on WiFi like you'd like, it boots you off of WiFi saying internet is unstable if it considers the data connection as being a stronger signal. its a real ignorant move and overlook they made when adding this function. if on WiFi they should let you choose if you want to change connections,or better yet not even bother you to choose between the 2 cause it will interfere with what your doing at that time while you have to choose which connection you want to use. But this is involved with the update we are getting. Verizon already got an update that had to do with WiFi issues with this being one of the issues it fixed.
If you haven't been told yet though, go in to WiFi advanced settings in your WiFi connections menu, and turn off auto connect & always scanning, then dial *#0011#, click your bottom left button on the white part of the phone you'd usually use to bring up the settings menu option, choose WiFi, turn off WiFi power save mode, WiFi power save mode being tuned off cause your battery to drain about 25% faster but this is proven to work. But after a day or 2 always leave WiFi auto connect off & always scanning off, but you can then dial *#0011# & turn WiFi power save mode back on & it's almost as if those functions done together trains your phone to not boot you off WiFi anymore. This seriously works and definitely helps many i have offered the information to. Me and about 3 others figured out how to do this in a thread about 2wks after the phone was released because the wifi booting us off was killing us. People had told us to just turn off auto connect but that would just stop the pop up, but you'd still be getting booted off from WiFi but just wouldn't be told by the pop up yet you'd know because the page you'd be loading on the browser would just stop loading, or say something your using like Facebook would lose signal & tell you an error occurred. Hope this large posts helps you if you read it or anyone else who stumbles upon it.
westkhalifa13 said:
I dont use google+ at all. It updated on its own and it started crashing since. I just turnt off all my auto updates and I uninstalled the last google+ update lets see if that does the trick .
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
You have to actually go into the Google+ app to see if you are signed in, unfortunately it will automatically sign you in if you are not already. So even if you accidentally open G+ or some other program or app causes it to open, you still need to actually sign out of it. Hopefully uninstalling the updates does the trick.
Auto connect in wifi advance settings is the network switch box right ???
Sent from my SM-N900T using xda premium
westkhalifa13 said:
Auto connect in wifi advance settings is the network switch box right ???
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
Yes thats it.
Sent from my SM-N900T using XDA Premium 4 mobile app
i had a wifi problem with my Note 2 before and now it is better with my Note 3.