Related
Anyone out there with this issue? I have multiple wifi network profiles on my Tab for Home (2) and at Work (1). Out of these 3 profiles , 1 profile from home (wpa) and the other from work (802.1x EAP) will reboot the GT each time i turn on the wifi. The only way to stop this from happening is to remove these profiles. Not very productive but thats the only way to get rid of the booting. Anyone facing this issue ?
Sent from my GT-P1000 using XDA App
It just happened to me too. Got the Android panic screen.
Mine just reboots wo any panic icon
Re-flash with the latest firmware.
Dear zyborg, i am a complete noob in this area coming from the WM platform. Can u point me to the link on how to flash a GT rom? B4 i take the step to do that , i would like to try hard resetting first...which will totally remove the rooting and not just the privacy - return to factory default? Is there such a thing like that for android devices? TQ in advance
Reflashed at Samsung centre. Issue stil there.
Sent from my GT-P1000 using XDA App
Take it back as it sounds defective..
I have the same problem. Did you get it solved or is it a hardware error?
I couldnt prove it to Samsung when i was at the sevice centre because the reboot didnt hapen at their wifi router. I came to a conclusion that the problem only arises on certain profiles and certain wifi routers. Compatibility issues? So far my dlink router and corporate router, cisco is giving me this issue. I had another 7 inch tablet, CSL and i never faced such issues with the same settings
Sent from my GT-P1000 using XDA App
I found out that the reboot does not occur when i only have one wlan profile configured.
So i think it is an softwarebug. Do you agree?
Thanks!
Yes. I agree. Looks like its only u and me for the time being. Btw my rom is dxjj1. What is yours?
Sent from my GT-P1000 using XDA App
Pda and phone:
XXJID
CSC:
XAJID
As i have baught my tab at Amazon, i have the possibility to change it on warranty for a new one. Maybe i will do this on next weekend.
I will keep you informed about my encounters.
Thanks lulatsch99. Would really like to know the outcome from yr side. Tomorrow i am getting a help from samsung tech guy to meet me at my office to test out his tab. Will try to simulate the same profiles to see if his machine boots too.
Sent from my GT-P1000 using XDA App
Hi,
today i got my brand new exange tab from Amazon. I tested it without installing any Apps.
The same reboot problem appeared. As soon as i had configured more than 1 wlan profile, the tab rebooted after switching off and on wlan. The same happens when i activate and deactivate the Offline modus.
This even happened when i had one profile for real and one dummy profile configured. After the reboot the wireless lan connection works fine until switching off and on wlan.
Both profiles i configured with wpa2 psk.
Now i really think this is a software/driver bug. Most of the tab users seam to have only one wlan profile, otherwise more people would have this problem.
Oh, i also contacted the german Samsung support. They never heard of this problem.
Please let me now if you got better results with or from the tech guy.
The tech guy from Samsung couldnt make it. Next schedule is next week. I am not too hopeful now since ur scenarrio proved its not hw related. Maybe Samsung in Germany and Malaysia should talk to each other. Thats provided the log down our issues in the database. Will update you once i get to test their units. I also tested that this problem will exist if one profile is on wpa while the other is on 802.x
Sent from my GT-P1000 using XDA App
I have the same issue. The tab also reboot eventhough I have only 1 wifi profile configured. I try "factory default" several times but issue still exist even no any app installed at all.
my version is also P1000DXJJ1.
After phone consult with local Samsung call center, they have never seen this problem.
P7570 said:
I have the same issue. The tab also reboot eventhough I have only 1 wifi profile configured. I try "factory default" several times but issue still exist even no any app installed at all.
my version is also P1000DXJJ1.
After phone consult with local Samsung call center, they have never seen this problem.
Click to expand...
Click to collapse
Either Samsung is trying to cover up till the next major update or not enough ppl is having this problem to make it a major issue. May I know which country you are from ? I am from Malaysia. If we at the same location, then maybe we can go there together and make a point.
Ii finally met up with the Samsung tech guy today. Same issue with his TAB. So I guess its a bug with the software. He will feedback to Samsung and I guess all we can do is wait till the next official ROM to see if they have solved it. I will try the DXJK5 ROM later this week to see if the problem appears there.
cmloo said:
May I know which country you are from ? I am from Malaysia. If we at the same location, then maybe we can go there together and make a point.
Click to expand...
Click to collapse
Hi cmloo, I am from Thailand. I have posed on some thailand's user webbroad but no one has this issue. I recently not have this issue for 1 week also for normal use which not repeatly turning on/off wifi.
Thank you for your update.
@cmloo
I fully agree! Thanks for the upgrade!
My WiFi connection has always been reliable and robust before the update to 2.3.6,but now it works wrong,the wifi is scanning repeatedly.When I try to connect my wireless,the connection button is disable.
Anyone else seeing this? Would you give me a suggestion?
Thank you!
I've had the same problem since 2.3.6 was pushed to my Nexus One. There seems to be some people with this and other serious issues, but there doesn't appear to be any acknowledgement of the problems from Google. I have read some posts by people who use their phones for their business and such, and the issues with 2.3.6 are causing them to lose time and money. I don't know why they released this, they obviously didn't test it very well.
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.
Even with the latest update as of May 2022, my new Tab A8 exhibits Wi-Fi stability issues not seen on the old Tab A7.
After leaving a connected tablet to sleep, Wi-Fi for some apps won't work and only a WiFi OFF + WiFi ON reset will restore connectivity.
Anyone else encountered this problem?
Same - it just won't stay on any network for long at all. It won't connect at all to my VirginMedia router saying 'couldn't get ip number'
Doesn't happen to me from what I've seen... Have Xfinity cable internet together with a Netgear router/modem.
Have you guys done all the system updates?
Yup, up to the latest from April. Tested on 2 devices and it's the same. Factory reset doesn't help.
I'm hoping that if not before, at least the Android 12 update will resolve this.
I just updated to Android 11 firmware update from last week - X200XXU1AVG1 - but the issue remains the same
On Build number RP1A.200720.012.X200XXU1AVC1, no updates I'm aware of. When this happens to me and I toggle wifi off and back on, no networks display. If I toggle airplane mode it they will appear again.
II'm in the USA, using an asus blue cave router.
What's everyone else using?
Anyone know what wifi chipset this tablet uses?
Got the update to Build number RP1A.200720.012.X200XXU1AVG1 it still occurs, and I'm also noticing bluetooth connection issues, both are cured by cycling airplane mode on and off.
Yeah... let's hope Android 12 includes fixes for this... really, the Tab A7 was a much better device with a nicer screen
KoMarCek said:
Yeah... let's hope Android 12 includes fixes for this... really, the Tab A7 was a much better device with a nicer screen
Click to expand...
Click to collapse
I reported the issue via Samsung members app with a bunch of screenshots,
SM-X205 is now getting Android 12 but nothing available yet for SM-X200. Will probably take a couple more days
OK now SM-X200 also got the first Android 12 update and the results are... BAD! Still the same issue and I'm quite done with Samsung for now. Unbelievable that they do not test the basic functionality well enough. I expected some WiFi driver updates under the hood but it seems they are oblivious to the fact Tab A8 has issues.
Had the issue one time since the 15th it's not solved but less frequent at least
What I notice now is that the wifi will turn off randomly. If turned back on it reconnects but shortly thereafter bluetooth dies and cycling airplane mode is required