Related
Hi,
let me thank you for all the help you may give me.
The problem is i get stuck on obtaining ip address or the cell doesn't even try to connect automatically so i have to manually start the wifi connection to the network after turning on wifi.
The problem of my SGS not connecting automatically is rare, the first is not, it's actually quite often.
I looked through all the guides and sugestions but i couldn't find any permanent solution for this problem.
Note: I've used the AllShare app but sometimes even that doesn't work.
Thank you for all help
The same problem kept happening with me. Some of the fixes which I tried were
Change channel on router - didnt work for me
Use the allshare app first - worked
Set up a static ip in advanced settings - almost always worked
But I have found that I didnt have this problem with other routers, only mine, maybe because of a power problem with the router.
Many of baffling errors are usually caused by bad input power to devices.
Hope it helps
Thanks for the reply, the problem is that i use it alot on my university, where i can't do any changes to their router (or use static IP).
Also the AllShare app is indeed a fix, but only if used every time i think. I'll do some more testing, this problem is really annoying and that's a shame because it complicates the use of most of the smartphone capabilities.
So if anyone else as another solution i would be glad to hear it.
Also i'm on stock rom installed by my operator Vodafone (had the same problem on JPY).
Edit: After a very quick test, it seems that using Allshare once does work, but i had the impression that sometimes it would be needed more than once (even without rebooting). TY for the tip.
Update:
After some more tests i came to the conclusion that at home i need to use AllShare every time i want to connect to my network.
This seems to be a problem affecting several users of SGS, does anyone know the answer to this problem? Or at least an app that minimizes it?
It's quite bad and very frustrating. Thanks, for any and all help.
I had the same problem with stock Android 2.2.1 on 3 phones all Galaxy S. Dropping the packages on voip calling, internet was slow most of the time. I use a linksys wrt54g with dd-wrt, I never had problems with any other devices.
My problem was solved when I installed GingerReal. Also on Miui I didn't had any problems with the wifi connection.
Maybe is just the stock driver incompatibility with some devices.
Thanks for the reply,
I've only had bad experiences with flashing, last time i did everytime right and Odin just hanged, i almost had a serious problem in my hands.
Since this is probably the first and last good phone i'll ever have, i would really like not to kill it (also some people in my family would be very disappointed, it was a gift).
So any workaround? Sorry i'm so insistent but i think that are a lot more people interested in this. TY.
well, my wifi is acting wierd... reception is good and it doesn't disconnect too often, theres just this little anoying thing!
everytime roughly 3-4 days after i flash a new rom my wifi simply refuses to connect to network, and not a specific one, any network at all!
and it stays like this for a couple of hours and then all of a sudden it picks up a a networks and it works fine for a while, untill i happens again...
i've tried restarting and taking out the battery and turning the wifi off for a while, nothing seems to help, he just decides on his own when he is whilling to connect again....
if i flash a brand new rom the problem disapear for a few days but then it comes back... i'm assuming it has to do with some sort of a cache that is filling up with loads of crap and ruining the wifi activity but i tried googling for this and found nothing..
ideas anyone? (btw this happens on all roms: stock, existenz, beanstalker etc...)
its a hardware problem and not so uncommon look here
http://forum.xda-developers.com/showthread.php?t=2531711
if you can take it to a customer support and if you cant sell it and again if you cant, then just get along with no wifi/bluetooth/NFC check all of them you should have problem with them too
dragunov_lq said:
its a hardware problem and not so uncommon look here
http://forum.xda-developers.com/showthread.php?t=2531711
if you can take it to a customer support and if you cant sell it and again if you cant, then just get along with no wifi/bluetooth/NFC check all of them you should have problem with them too
Click to expand...
Click to collapse
absolutly not related, my NFC and bluetooth works just fine, i don't need to press hard anywhere...
and my wifi works just fine after a fresh rom install... so it's defenetly a software problem...
shteren said:
absolutly not related, my NFC and bluetooth works just fine, i don't need to press hard anywhere...
and my wifi works just fine after a fresh rom install... so it's defenetly a software problem...
Click to expand...
Click to collapse
to me that sounds like the start of it because mine was the same at the first few days flashing a new rom or something would help alot but then i just found out the only thing that was helping it to get fixed was the heat from the device not the rom, but it doesnt hurt to play around with it a little so go ahead and try some other roms or repairs.
you see good reception for wifi
you try to connect
at the authorizing or connecting you will see only one point of signal and connection would kinda like disappear.
this is how it was for me but at the first days it was random it was connected good and ready, when i would left the phone in stand by after a few minutes it would DC, so i thought its kind of a sleep mode malfunction or something but after a few days almost 1-2 weeks it turned out to be hardware problem like ohers so if you see any symptom like that start looking for service centers.
but i hope it would be a software problem for you, so good luck.
Well, once he connects he stays on for days, no problem there... Just sometikes he refuses to connect... Pressing the nfc button doesnt help...
Sent from my C6903 using Tapatalk
shteren said:
Well, once he connects he stays on for days, no problem there... Just sometikes he refuses to connect... Pressing the nfc button doesnt help...
Click to expand...
Click to collapse
What Wi-Fi channel is your network on and have you tried 5GHz?
Didn't look into those things, but it happens with all networks except ones without passwords
Sent from my C6903 using Tapatalk
Have you tried deleting wpa_supplicant.conf in data/misc/wifi and reconnecting to the network? (this will delete all saved passwords and settings for known wi-fi networks) also try to disable Auto IP in advanced wi-fi settings
Well the phone is qith my sister now, I got a new z1 so far wifi worka for her, it stoppes for a few hours yestarday but came back, I might try to flash. 310 and see if it works better with it. And the Wapa_sup sounds like a good idea. Btw z1 is also jittering some with wifi, it's a global Sony problem...
Sent from my C6903 using Tapatalk
temp solution?
Well, it is probably a hardware problem. I have had the same problem, everything looks fine, but you can't connect to any network.
So, searched, reinstalled, etcétera, nothing worked. Untill I read a crazy solution link://talk.sonymobile.com/t5/Xperia-Z-ZL-ZR/xperia-zr-wifi-association-rejected/td-p/516275/page/4
and found out that if you put pressure on the back of your pone right at the NFC chip, with a finger or so, the Wifi will come alive again.
Personally I had to hit my pone's back at that exact spot with my finger (for not damaging it with excesive force) a few times, but then suddenly it worked.
So, I am convinced it's a hardware problem. Hope it works for other people too.
I've got an annoying problem with my phone where the Wifi turns off when my phone is idle or asleep. This means my WhatsApp for Web disconnects and also my Moto Connect plays up too.
I've got the same problem at home, work and parents house so can't be an issue with all 3 networks. The keep wifi on during sleep option is set to Always before anyone mentions this to me.
Phone is running Lollipop 5.0 in the UK and is NOT rooted.
I noticed it doesn't happen when the phone is charging though.
Any ideas?
Right I've now tried changing the Sleep setting to Never but get the same problem.
Also tried connecting to the router via WPS but no luck.
Router is a Superhub 2. I've ruled out that it's the Superhub as I have a Samsung Galaxy S4 Mini that is running fine without a single drop out.
Definitely something Moto X related.
I've also tried on both the 2.4GHz and 5GHz bands with same results!
Try looking within the WiFi settings on the phone. Mine has this
. Added photo
Sent from my HTC One using XDA Free mobile app
Mine is identical to yours other than the fact that I don't have the wifi optimization option.
Right I've just cleared the cache as instructed by Motorola support.
Still have the same problem even after clearing cache.
Ok I can confirm that the issue goes away when in safe mode.
This is starting to piss me off as I don't have any way of checking if it's an app affecting my wifi disconnections!!!
I've finally found and fixed the problem myself!!
I decided to turn my bluetooth on (even though it wasn't connected to any bluetooth devices). This seems to stop the phone from causing the wifi to go to sleep!
It seems like it's a bug in the Moto X Lollipop firmware. How do I report bugs to Motorola??
It's funny how most say it's apps that cause strange behaviour but for me it's been the actual Android firmware each time I've ever had an issue!
I hope it gets fixed soon.
Wutang200 said:
I've finally found and fixed the problem myself!!
I decided to turn my bluetooth on (even though it wasn't connected to any bluetooth devices). This seems to stop the phone from causing the wifi to go to sleep!
It seems like it's a bug in the Moto X Lollipop firmware. How do I report bugs to Motorola??
It's funny how most say it's apps that cause strange behaviour but for me it's been the actual Android firmware each time I've ever had an issue!
I hope it gets fixed soon.
Click to expand...
Click to collapse
It's a known bug of 5.0, and already fixed for 5.1. Source, at the "Bug fixes section".
Great that you found a workarround.
Cheers!
Manuel.
Hey glad to know it's a well known bug. The work around still doesn't work. It still keeps disconnecting all the time! Driving me mad!! If the 5.1 update doesn't fix it for me, I'll need to try and get a refund and go for something else. Shame as I really like the Moto X but I can't live with an issue as stupid as this!
I'm not sure Motorola are aware of this issue at all. See their comment below from one of their support staff I'm speaking to now:
Santhosh: We have not received any reports regarding Wi-FI issue after the Android Lollipop update but please give me a moment I will provide the solution for this issue.
His solution for the issue was to get me to do a factory reset lol. I already did this when I first got updated to Lollipop!!
Going to try doing another one now to see if it actually makes any difference. Then will install a few apps at a time or something.
I am connected to WiFi just about all of time, and I have never experienced this.
Right I've done a factory reset and started completely afresh with none of my data or apps restored. WiFi has been solid; I've not had a single drop out!
I'm going to install just a couple of apps at a time and keep an eye out if the issue comes back until I find the culprit.
Hi
My phone was perfect (until now) with the WIFI since november 2014 even after I upgraded it to 5.0
But today, it suddenly starts with this problem by itself. so I restored it to factory defaults with no luck, I installed a new firmware, and still has the bug.
So, why it shows up until now by itself without any mod, app or update?
Sorry for my English.
Today I upgraded it to 5.1 and the issue persists
I had to back to stock 4.4.4. and now my wifi has been fixed so far, working good without interruption until now.
I hope this has fix the problem from sourse, and I'll wait a few days to upgrade it again.
EDIT: Has been a month since my downgrade to 4.4.4. and my WIFI still rocks.
Just want to say that I'm having the same issue since the update to 5.1. Wifi is set to be always on during sleep, but I regularly wake up my phone only to find it connected to 4G, and switching to wifi a few seconds after waking up.
I'm on a locked bootloader (unrooted of course). I did a full reset after the update...
I'm sorry to say that I've seen more little glitches since 5.1 than anything I noticed on 5.0.
EDIT: another issue I'm having is the stock mail client not syncing saying that there is no network connection. My exchange account (push) works fine however...
Just to say the issue has started for me too since the update to 5.1.
I've done 2 factory resets but no luck trying to fix this very annoying problem.
Motorola have asked me to send my phone in for repair so I'll try that and see what happens.
Hello everyone,
I'm having major issues with my Nexus 6 over the past 3 weeks or so.
I've had this phone for almost 2 full years now and love it, however, over the past 3 weeks the bluetooth function keeps turning off when I reboot my phone every night.
It NEVER did this in the past 2 years. Only the last 3 weeks. It seems to be some sort of battery saving feature, I would presume.
What drives me nuts, is I always like to have my bluetooth on, since I get in my truck and it auto connects to my GMC IntelliLink (which is also a problem).
So does anyone know why, all of a sudden, after reboot, bluetooth defaults to off and I have to manually turn it on every time? My Nexus 6 has been flawless up until now.
I've looked everywhere for an "auto start" option for bluetooth, but cannot find one. I have ZERO idea how this happened all of a sudden. I've been running the same ROM since last February with no problems (ROM screenshot attached).
As for my bluetooth truck problem, that started today. All of a sudden "phone audio" will not let me select the box, only "Media Audio" and "Contact Sharing" boxes are selected. Thus my Pandora plays over bluetooth, but my phone calls will not.
Also my Bose Quiet Comfort headphones used to connect perfectly with my Nexus 6, now I'm at work and I notice if I turn the headphones off, then come back and turn on, it'll say "connected to Nexus 6", but the sound is playing through the phone instead of the headphones, even though the bluetooth connection has been established.
Again, this is only over the last few weeks.
Any help would be greatly appreciated.
I'm willing to update to a new ROM or do a wipe, I just tend to live by the motto "if it ain't broke, don't fix it"........ except now it is broke and I want to fix it.
Thank you-
Paste a logcat here. A dev could take a look and help you out.
or
Backup your stuff and do a clean install of a new pure nexus or whatever rom, if it's still present after that, maybe it's just your battery starts to dying after 2 years.
Edit: I'm using crdroid as daily driver and have no bt issues
So glad you posted this, I'm having the same issue! After either a restart or just a period of time my Bluetooth turns to disabled. It is especially frustrating as I have it connected to my watch, which allows me to unlock with smart unlock. When the Bluetooth is disabled, I have to punch my pin in.
I am on stock 7.1.1, February update. I am rooted and flashed the Echo Permissions Fix. I was going to flash stock again this morning, but decided to check here first for a solution. I am just happy to know that it's not just me.
That being said, like @MVLJR, I recently flashed PureNexus ROM and that for me is when this began. I flashed back to stock via flashall, but it has not stopped the problem. Could it be a PureNexus thing?
As we have PureNexus somewhat in common, I am doing some searching on that page. I had previously posted there about it, but I don't think I ever got a response. Someone mentions it on Page 3417, I'll keep reading to see if I find a solution.
My post, by the way, is on page 3420.
I had a problem like this on Pure Nexus and flashed back to stock (N6F26R) to see if the problem goes away...
Previously on stock (release before N6F26R) and never had an issue. I use Bluetooth with a watch, fitness band and sometimes my Wife's Ford...
Sent from my Nexus 6 using Tapatalk
@muiriddin, did the problem go away for you? Because I flashed back to stock and the problem persists.
@MVLJR, I suspect that the problem is Android Wear 2.0 on our phones. Do you have a smart watch?
Edit: On the PureNexus forum, people without Android Wear are also experiencing it. So back to the drawing board. I still do not think it is your ROM.
Reading this thread reminded me of something I dealt with a while back, I don't know if this will do it for all of you, but I figured I'd post this. I screenshotted a reddit thread that fixed the problem for me. I can't remember if what I experienced was the same as all of you, and I am not having the problem now. But I hope this helps. Please see the attached screenshot.
I don't have an android watch, but I do have a fitbit and don't have any problems with it.
A little update, I cleared my Bluetooth cache and changed the name of my device, which seems to have helped.
My Bose headphones now autoconnect like before.
However, my Bluetooth still shuts off after reboot. My GMC Intellilink still won't let me select "Phone Audio" either.
I think I'm going to flash a new ROM this week, which sucks because I've grown attached to the Pure Nexus ROM.
Can someone show me how to post a logcat?
Thanks
This (and similar) bluetooth issues have been reported on the nougat product pages. It's not unique to PureNexus or the Nexus 6.
Reports are that 7.1.2 (beta) fixes the issue on devices that have access to it. Hopefully a fix comes down the pipe for the Nexus 6 as well, as I have some of the same issues.
Similar posts can be found on the nexus6 and googlepixel subreddit pages.
My question is, what prompted this?
I've had the same ROM for a year, no OTA updates. Had to be an app update, correct?
No other way to explain how it worked for a year, now problems all over the place
You've been using the same ROM, but updating the version of the ROM, correct?
And the ROM updates are based on updates made to Android by Google.
So if a bug makes it into Nougat, it will (generally) make it into the modified ROM as well.
Incorrect, I've been on the same version of Pure Nexus since last February, screen shot in original post
I take it the fix I posted didn't help? I was really hopeful that it was the same issue and that would fix it up.
I haven't tried it yet, at work right now, I'll give it a shot later.
I'll update my findings.
Thanks
Will keep my fingers crossed. One thing to note, when doing that fix, it *will* wipe your bluetooth auto-pair devices. So don't fret if nothing automatically connects afterwards. You have to repair everything.
It is not a new problem, there are many threads in the Q&A forum if you search. Here is one:
https://forum.xda-developers.com/nexus-6/help/bluetooth-off-reason-pattern-t3435436
(there are more links and suggested workarounds in that thread from me)
That said, installing the AW 2.0 DP 4 totally solved my BT disconnects from my Huawei watch and LG stereo headset.
The changelog on the latest Huawei AW 1.5 mentions BT issues, but I have not tried it.
AW 2.0 official is supposed to start rolling out OTA tomorrow, so we shall see. (finners crossed tite )
I'm on Jan 21 PN 7.1.1, latest AW app. I have no suggestions of those having issues with no Android Wear, but there are threads here with suggested workarounds that solved this for many of us before, you might want to check them.
@Morpherios and @MVLJR
I don't know if it's of any note, but one of the actions I attempted in trying to fix mine was to reset all network settings via the "More" option in Wireless & Networks settings (I backed up wifi settings in advance). That's essentially a nuking of all network settings, including wifi, cell, and bluetooth. It did not resolve my issue.
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening. How the software on the watch (as opposed to the AW app on the phone) would be causing bluetooth to crash, I'm not sure. But it's not outside the realm of possibility.
larrysteeze said:
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening.
Click to expand...
Click to collapse
My words were / are different than that:
AW 2.0 DP 4 totally solved my BT disconnects
That means they do NOT happen any more, since Dec 11, 2016 when I installed AW OS 2.0 DP4 was released and I installed it on my watch. Not. One. Disconnect. None. Nada. Zero. Zip. Zilch. Nein.. :victory:
BT devices communicate both directions. The watch CAN control the phone, and was turning off BT. It was obvious when it happened, when my headphones prompt "Out of Range, trying to connect" (I came to hate hate that voice prompt )
I would immediately open the AW app on the phone at disconnect and was prompted to turn on BT because it was off.
@Pkt_Lnt I completely agree that it BT communication is two-way...I stated that it's not outside the realm of possibility because there are a number of factors that could do it, including the phone receiving a message it simply doesn't know what to do with and causing a fault. This could explain my bluetooth share crash messages that I received on occasion.
It's encouraging to know that it's fixed with AW 2.0 for you. I hope it carries through to me when I get the update. If the OTA doesn't drop tomorrow, I may have to flash the DP as well.
As I've already read, SD 835 phones including this one suffer Wi-Fi drops and disconnects. My particular issue is that even though the device is connected to wifi either speed seems to slow down a lot or internet simply doesn't work, I can tap whatever I want in Chrome and the loading bar below the address bar fills in a millisecond and disappears. Happens on different routers, router configuration reset doesn't help nor does device reset. Was the issue already addressed by any update or should I wait?
Opel_Astra said:
As I've already read, SD 835 phones including this one suffer Wi-Fi drops and disconnects.
Click to expand...
Click to collapse
Is this a known issue? I came here to post about it.. What a bummer, will have to return this it seems.
rpgdev said:
Is this a known issue? I came here to post about it.. What a bummer, will have to return this it seems.
Click to expand...
Click to collapse
It is, however most people complain about disconnects making them restart the phone. In my case wifi is still connected, but it sometimes seems to stop working while still being connected and wifi relaunch fixes the issue.. 145 fw didn't solve it, so I guess we should wait.
Opel_Astra said:
It is, however most people complain about disconnects making them restart the phone. In my case wifi is still connected, but it sometimes seems to stop working while still being connected and wifi relaunch fixes the issue.. 145 fw didn't solve it, so I guess we should wait.
Click to expand...
Click to collapse
Is the US version affected by this?
rpgdev said:
Is the US version affected by this?
Click to expand...
Click to collapse
No idea, but if people stating it's Snapdragon 835 issue are right , US version should also be affected. I'd rather ask an owner though.
Opel_Astra said:
No idea, but if people stating it's Snapdragon 835 issue are right , US version should also be affected. I'd rather ask an owner though.
Click to expand...
Click to collapse
As I recall there was a wifi lag problem with the first couple of builds, but I've had no issues with wifi since November. So perhaps it was fixed in a firmware update?
Didgesteve said:
As I recall there was a wifi lag problem with the first couple of builds, but I've had no issues with wifi since November. So perhaps it was fixed in a firmware update?
Click to expand...
Click to collapse
I've updated to .145 a few days ago (branded rom) and wifi connection seems to have improved, no more hangs. It might be different router in use, so I'll confirm when I'm back home so that I test in on the device I've had problems with.
Opel_Astra said:
I've updated to .145 a few days ago (branded rom) and wifi connection seems to have improved, no more hangs. It might be different router in use, so I'll confirm when I'm back home so that I test in on the device I've had problems with.
Click to expand...
Click to collapse
I've been using .145 all this time. I'm still experiencing the issue.
rpgdev said:
I've been using .145 all this time. I'm still experiencing the issue.
Click to expand...
Click to collapse
I confirm the issue still sadly occurs on .145. let's keep waiting then.
Opel_Astra said:
I confirm the issue still sadly occurs on .145. let's keep waiting then.
Click to expand...
Click to collapse
I returned mine and ordered the US version to see what's what. Should be present there too but one can hope... don't want to give up on the phone but if I encounter it there too then I'll have to go for another model. I'll report back whatever I'll find.
Have a similar wifi problem using (US) firmware .145. A restart fixes it, but eventually the problem resurfaces again. May wait to update until firmware following .179 is available, as I've read that in some cases .179 makes the problem worse. (?)
rpgdev said:
I returned mine and ordered the US version to see what's what. Should be present there too but one can hope... don't want to give up on the phone but if I encounter it there too then I'll have to go for another model. I'll report back whatever I'll find.
Click to expand...
Click to collapse
I did this. Problem was still present on US phone as some predicted. Returned that phone as well.
I'm using CE1 .145 firmware and it started to do that problem a week ago. I have never experienced that before that time. I have to restart my phone at least twice a day and it appears even I'm not connected to any wifi router.
I'll see when update will come. It's horrible.
Odesláno z mého G8441 pomocí Tapatalk
I'm not experiencing the Wi-Fi disconnect very often, fortunately, but it makes the problem more difficult to diagnose. Odd that some people experience it regularly, even several times a day.
pseudonym58 said:
I'm not experiencing the Wi-Fi disconnect very often, fortunately, but it makes the problem more difficult to diagnose. Odd that some people experience it regularly, even several times a day.
Click to expand...
Click to collapse
For me it happened several times in a couple of minutes time. I'm on a college campus though, a lot of wifi hotspots around because of the university's wifi network, I think that made it worse.
Solving Wifi Issue of Sony Xperia XZ1 SOV36
Opel_Astra said:
As I've already read, SD 835 phones including this one suffer Wi-Fi drops and disconnects. My particular issue is that even though the device is connected to wifi either speed seems to slow down a lot or internet simply doesn't work, I can tap whatever I want in Chrome and the loading bar below the address bar fills in a millisecond and disappears. Happens on different routers, router configuration reset doesn't help nor does device reset. Was the issue already addressed by any update or should I wait?
Click to expand...
Click to collapse
Several days ago, my xperia also sufering wifi issues. The wifi is disabled by my device.
I have done so much attempts to solve it until I got this:
Connect the device to the PC and open ADB Fastboot. Then, conduct this codes:
adb shell
settings put global captive_portal_detection_enabled 0
That's all. My wifi work again.
I hope that will work on you.
Code:
adb shell
settings put global captive_portal_detection_enabled 0
This worked for me. Thank you