Related
I'm having issues with wifi after converting my HTC one to a Google Edition.
I'll connect to my school wifi fine, but every single time, after a certain amount of time it just stops working. I'll still be connected to the wifi network, but I can't connect to the internet.(When I'm at home, I don't have this issue)
My friend also has the HTC One stock, and wifi works fine. My gf has a nexus 4, so it uses stock android with no problems.
What is with my HTC One GE that isn't working?
I've tried a factory reset twice now, and it didn't help at all.
Help is appreciated! This is super annoying and is literally hindering my productivity because I don't have enough data to just use cellular service.
Help please
Sent from my HTC One using Tapatalk
What happens on stock Sense firmware? If you are S-OFF, flash Dev edition RUU and test.
lettuceman44 said:
I'm having issues with wifi after converting my HTC one to a Google Edition.
I'll connect to my school wifi fine, but every single time, after a certain amount of time it just stops working. I'll still be connected to the wifi network, but I can't connect to the internet.(When I'm at home, I don't have this issue)
My friend also has the HTC One stock, and wifi works fine. My gf has a nexus 4, so it uses stock android with no problems.
What is with my HTC One GE that isn't working?
I've tried a factory reset twice now, and it didn't help at all.
Help is appreciated! This is super annoying and is literally hindering my productivity because I don't have enough data to just use cellular service.
Click to expand...
Click to collapse
Yeah. That is a Google Play Edition Issue on 4.4 KitKat and above... you won't be able to fix this issue (except rewriting a part of GPE)
This here helped me in Wi-Fi's like your school wifi:
[root] Pry-Fi
but if you disconnect and reconnect you have to re login because you have a new Mac...
LibertyMarine said:
Yeah. That is a Google Play Edition Issue on 4.4 KitKat and above... you won't be able to fix this issue (except rewriting a part of GPE)
This here helped me in Wi-Fi's like your school wifi:
[root] Pry-Fi
but if you disconnect and reconnect you have to re login because you have a new Mac...
Click to expand...
Click to collapse
Gah, not what I was hoping for
I was hoping it was a specific issue I had, not an actual android issue.
Why is it only GPE that is affected by this? Explains why my GF's nexus 4 works well.
This is a bummer. I guess I have to revert back to stock.......I get disconnected and reconnected from wifi all the time due to the wifi not being 100% everywhere on campus.
Thanks for the help, at least I know now that I can't do anything about it, time to go back to stock.
Are the revert to stock guides in you're sigs work from a GPE to stock?
i know how you feel
lettuceman44 said:
Gah, not what I was hoping for
I was hoping it was a specific issue I had, not an actual android issue.
Why is it only GPE that is affected by this? Explains why my GF's nexus 4 works well.
This is a bummer. I guess I have to revert back to stock.......I get disconnected and reconnected from wifi all the time due to the wifi not being 100% everywhere on campus.
Thanks for the help, at least I know now that I can't do anything about it, time to go back to stock.
Are the revert to stock guides in you're sigs work from a GPE to stock?
Click to expand...
Click to collapse
it's not just the GPE, I switched my AT&T HTC One to Developer Edition and have lost wifi since 4.4. I downgraded back to stock and worked my way up the updates with no luck. back to dev edition now 4.4.2 and still no luck
robbie09 said:
it's not just the GPE, I switched my AT&T HTC One to Developer Edition and have lost wifi since 4.4. I downgraded back to stock and worked my way up the updates with no luck. back to dev edition now 4.4.2 and still no luck
Click to expand...
Click to collapse
I just went back to stock sense 4.3 and I'm having the same issues still. Before conversion I had no issues.
Why is it still happening?
Could a factory reset work? I assumed when I flashed the ruu it just wiped everything.
lettuceman44 said:
I just went back to stock sense 4.3 and I'm having the same issues still. Before conversion I had no issues.
Why is it still happening?
Could a factory reset work? I assumed when I flashed the ruu it just wiped everything.
Click to expand...
Click to collapse
Run the full RUU if available.
What do you mean by that? I converted my phone from GPE back to stock using the AT&T ruu.
Sent from my HTC One using Tapatalk
I really need to fix this issue, it's becoming a liability
I don't know what else to do
Sent from my HTC One using Tapatalk
Bump again.
Sent from my HTC One using Tapatalk
Still looking through the internet for help, still found none.
similar issue
I'm on ViperOne 4.4.2 with similar issues. Only my router is a meter away from me, so the connection is excellent. Wifi on phone keeps disconnecting, but what is interesting, it does so like it's scheduled to do so. For an example - it'll work fine for an hour, more or less, & then it'll start to play games - disconnect, reconnect, scan for networks & show nothing, or try to connect & fail, or even get stuck at 'turning on'. Every problem that I have with my wifi can be temporarily 'fixed' with a reboot, then wifi will work fine for some time & start to disconnect again. HELP?
BTW this started after 4.4.2 update. I've downgraded back to 4.2.2, to 4.3 & now I'm back on 4.4.2, no changes. Did this update **** something up in my phone's hardware or what?
http://android-revolution-hd.blogspot.com.es/2014/02/how-to-fix-wi-fi-htc-one.html
I have a similar problem to what was initially discussed in this thread. Company wifi has multiple routers throughout the building/department - when I first connect to the system everything works great, but after moving to a different room and connecting to a different router (same network/wifi) the internet connection is lost. I stay connected to wifi, with strong signal, but don't have any data connection. In order to get internet back I have to turn the wifi off and back on - everything works fine until I walk into a different room and connect to a different router.
I'm on an HTC One Google Edition - don't remember having this problem before rooting the One from Sense to GE, but I wasn't streaming radio broadcasts of baseball games over the internet until a week ago, which was when this became a real annoyance.
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.
Hi there
I bought a Moto X 2014 last week, and I have the stock, unrooted 5.1 update (23.16.1).
Today, I had an issue where the phone was not automatically connecting to my car's bluetooth stereo. Tried manually reconnecting to the Moto X through the car's system but it kept saying "unable to connect". I decided to switch the bluetooth on the phone off and back on again - it switched off OK, but when trying to switch it back on, it would move to the "on" position for a second or two and then go back to "off". Tried it a few times but the only thing that got it working again was a reboot.
Just wondering if this is likely to be a one off or a common issue on the handset? I have read about people having issues with skipping audio but this was just bluetooth not working at all.
Thanks
James
I've run into this on my Moto X and my wife has seen it on her Nexus 5. It just seems to happen if you keep Bluetooth on for a long time and then toggle it. I've found that rebooting every few days avoids a number of issues in Android in general.
raptir said:
I've run into this on my Moto X and my wife has seen it on her Nexus 5. It just seems to happen if you keep Bluetooth on for a long time and then toggle it. I've found that rebooting every few days avoids a number of issues in Android in general.
Click to expand...
Click to collapse
Thanks for the feedback. I've come from a Nexus 5 where I'd not ever had this happen despite leaving Bluetooth on permanently. Perhaps it's an isolated thing so I'll just see how things go for now.
stock tmb note 4. CONSTANT bluetooth connectivity issues. this phone is a piece of sh!t when it comes to this and I am at my wits end. does anyone know if a 3rd party app that fiuxes this issue? we have not gotten the marshmallow update yet either so I dont even know if this is limited only to jellybean.
anyone with this same infuriating issue?
thanks!
What is the issue? You didn't actually say anything other than it's giving you problems.
FWIW my wife and I have never had a BT issue.
Never had a single issue here either.
Cannot connect to any device with any level of stabilty. I have done it all. Clearing.caches and data. Installing stupid 3rd party apps. I'm at the point where I don't care about Knox and just root but I'm leery arput doing it. Bluetooth on the note 4 for me has been nothing but a problem
Sent from my SM-N910T using XDA Free mobile app
My wife and I both have a Note 4 with TMo. Hers is bone stock and mine is stock rooted.
Never had BT issues. We both use BT connections for hours at a time with no stability problems.
Maybe try dialing *#0*# and running a self test on the BT hardware.
Not to be a jerk, but could you be more specific? You're really not giving us any kind of useful information.
What are you trying to connect to?
How far away is it?
Do you get any error messages?
What system version are you on? 4.4.4? 5.0.1? 5.1.1? I assume you're stock, so probably 5.0.1?
Can you have a friend with a different phone come over and try to connect to it to rule out the device itself being the problem?
FWIW, I highly doubt rooting your phone is going to do anything useful with your BT situation.
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.