[Q] One S/Sense 4.0 based ROMS and phone lock-ups? - HTC Sensation

I've tried a few Sense 4.0 ROMs based on the One S and with each I've had problems where the phone will become unresponsive. I can't unlock it, even though it's not dead (if I plug into my computers, the screen will show the lockscreen, adb works, if the kernel has sweep2wake the buttons light up, etc). I installed catlog a few days ago and when the phone locked up I reviewed the logs and noticed it happening around the time there was lots of WiFi activity (specifically, switching between WiFi and the T-moble data networks).
I next disabled WiFi and the phone was fine for a day; I enabled WiFi, went for a walk, and sure enough had the display freeze up again. It's become so predictable that it's very easy for me to reproduce now; turn on WiFi, leave my office, walk to a nearby building which has a access point on the same WPA2/PSK network (I'm on a university with campus-wide WiFi), spend about two minutes there (the phone network is weak in this building, so it may or may not be able to pick up the T-Mobile network in that building) , leave the building and walk across the campus. Within two to four minutes of leaving the building, the problem occurs.
I don't have the posting history yet to make posts in the dev sections, so I'm want to see here whether others who've had their phone become unresponsive can confirm that they have something similar happening. If so, think back to where you were when you noticed the problem. If you have left the vicinity of a WAP, try retracing your steps with WiFI on and see if it happens. Also, try turning off WiFi and using for a while to see if the problem still occurs or resolves itself.

Related

4G & WiFi 'connected' but cannot I access internet connection???

Some background on my phone and situation:
I've been rooted, unlocked, and on Synergy ROM for quite some time now, since August 2012. I've updated the ROM many times. I've had a recurring problem where my WiFi is turned on, but randomly cuts out my internet connection. Right now, both 4G and WiFi are on, but I cannot connect to the play store, chrome, email, radio streams, etc. This has happened before and I cannot figure out the problem for the life of me, but holy crap is it ANNOYING!!!! I've done MANY searches and can't seem to find another person with this same problem, using the same terminology, so here I am. Also, it seems I NEVER have more than 2 bars signal strength on 4G (entire other issues - not as important).
I'm running firmware MF1 with MB1 TZ to fix camera, on Synergy r484 (current). However, this has happened to me often over the past many months. I use Unified Remote to control my home PC from the couch, which I gave up on because the app could never establish a wifi connection, or took 30 minutes to get working - I can't handle that. I try doing the *#0011# to turn off wifi power saving mode, but I do not get the same option people talk of when hitting the menu button, and the VZW voice says the update failed or some crap - I don't even know what this is exactly, I just tried it because I'm at my wits end!
Somebody, PLEASE help! This **** is the most annoying thing I've ever had to deal with, and have been dealing with it sporadically for the past many months.

Real Cause of battery drain/wake lock in MJ7/MK2 and fix

I am posting this as it is very hard to wade through information in forums. I'm hoping the following will be useful to those, who like me, experienced battery drain caused by Android Wake Locks after upgrading to MJ7 / MK2.
I am 100% certain the battery drain in MJ7/MK2 is caused by connecting to WIFI networks in environments that have multiple AP's. i.e. once WIFI roams from one AP to another the battery drain starts. All my testing confirms this - consistently. I have actually tested being connected to one AP in a multiple AP environment for a long period and observed no wake locks on Android OS. Yet as soon I move to another location (i.e when I make it roam) the wake lock and battery drain starts. All this rubbish about clearing cache, factory resetting, nobbling your phone and so on are all stabs in the dark - It's the reboot that temporarily fixes it so people mistakenly put two and two together. So, if you use WIFI in a large building with multiple AP's try forgetting the network and not connecting to WIFI with multiple AP's. If you have already connected to a SSID with multiple AP's reboot your phone because once the battery drain starts it does not seem to stop until you reboot. You don't have to disable WIFI at all as scanning does not cause the wake lock. I have tested this thoroughly and so far I have not had any battery drain since not connecting to SSIDs with multiple APs. I can also back this up as I can create battery drain at will by simply connecting to a WIFI environment with an SSID distributed over multiple AD's.
My battery life is again fantastic and I am happy now that I know the cause.
Pretty poor testing by Samsung/Google as I see in past versions of Android Roaming has been an issue.
mongoose3800 said:
I am posting this as it is very hard to wade through information in forums. I'm hoping the following will be useful to those, who like me, experienced battery drain caused by Android Wake Locks after upgrading to MJ7 / MK2.
I am 100% certain the battery drain in MJ7/MK2 is caused by connecting to WIFI networks in environments that have multiple AP's. i.e. once WIFI roams from one AP to another the battery drain starts. All my testing confirms this - consistently. I have actually tested being connected to one AP in a multiple AP environment for a long period and observed no wake locks on Android OS. Yet as soon I move to another location (i.e when I make it roam) the wake lock and battery drain starts. All this rubbish about clearing cache, factory resetting, nobbling your phone and so on are all stabs in the dark - It's the reboot that temporarily fixes it so people mistakenly put two and two together. So, if you use WIFI in a large building with multiple AP's try forgetting the network and not connecting to WIFI with multiple AP's. If you have already connected to a SSID with multiple AP's reboot your phone because once the battery drain starts it does not seem to stop until you reboot. You don't have to disable WIFI at all as scanning does not cause the wake lock. I have tested this thoroughly and so far I have not had any battery drain since not connecting to SSIDs with multiple APs. I can also back this up as I can create battery drain at will by simply connecting to a WIFI environment with an SSID distributed over multiple AD's.
My battery life is again fantastic and I am happy now that I know the cause.
Pretty poor testing by Samsung/Google as I see in past versions of Android Roaming has been an issue.
Click to expand...
Click to collapse
Funny thing is that when i am using mobile data the drain is worse, So I'm pretty sure this is not the main issue man. Also, I have a Mobile 'WiFi' router. Only me has WiFi connection in my entire hostel. So I don't really think it's the issue. Good finds tho! It will definitely help someone. Cheers!
Agree with stanley, this is not the only cause.
39089665568
vndnguyen said:
Agree with stanley, this is not the only cause.
Click to expand...
Click to collapse
Agreed. There are many things that will cause elevated use. But Im talking the rapid drain that occurs when you're not using the phone. Ever since taking the action I describbed my battery life has been excellent. Eg 94% after 14 odd hours with no use. And, I'm still connecting to my home wifi. Beforehand it could be below 60% with no use and this is the real problem people are talking about. Hope that makes sense.
Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.
aydc said:
Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.
Click to expand...
Click to collapse
I don't get it. What am I supposed to do exactly?
aydc said:
Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.
Click to expand...
Click to collapse
What about unicast traffic? i know the Client Isolation sort of "VLAN"s every client associated, just wondering if that might affect client to client communication?
Good point btw, im also wondering how many services wake the damn thing up, waking up over network is more an enterprise workstation scenario...to me it sounds like HotSpot 2.0 services being active, but i have not enabled it.
HS2.0 can let client and AP sort of talk without associating.
Nazty111 said:
I don't get it. What am I supposed to do exactly?
Click to expand...
Click to collapse
Most modems have a sort of 'guest mode' or allow you to open another access point and isolate it from the rest of the network. If you connect your phone to this guest access point or isolated access point, your phone will reach internet without problems, but will not reach the local network through the router. Nor will any other device on the network reach your phone.
Most of the problems with Wifi draining battery, like wifi wakelocks, occurs because devices on the network keep sending packets to the phone waking it up. With the method I describe above, you will isolate your phone and the phone will remain in deep sleep, significantly increasing battery life.
aydc said:
Most modems have a sort of 'guest mode' or allow you to open another access point and isolate it from the rest of the network. If you connect your phone to this guest access point or isolated access point, your phone will reach internet without problems, but will not reach the local network through the router. Nor will any other device on the network reach your phone.
Most of the problems with Wifi draining battery, like wifi wakelocks, occurs because devices on the network keep sending packets to the phone waking it up. With the method I describe above, you will isolate your phone and the phone will remain in deep sleep, significantly increasing battery life.
Click to expand...
Click to collapse
This is very true. Back on my old GNex i used to have crazy wifi wakelocks and I couldn't for the life of me figure it out. I never figured it out, actually. But I am positive it is one of the two PC's on my network that are broadcasting packets across the network, waking my phone up. I haven't had time to extensively test the wifi wakelock in the environment i've previously encountered it in to see if it still applies, but since I haven't changed anything regarding any of the two computers involved on that network, I'm positive I will have the same wifi wakelock issue when I get back and test. Is there a way (besides using Shark) to see what programs are broadcasting packets across the network?
But to get back on topic, I am experiencing battery drain connected to ONE router with ONE AP. I am in an apartment building with several other routers nearby, though. Maybe they are broadcasting packets somehow that the kernel is interpreting and keeping the phone awake? However it seems as though the Android OS bug keeps coming back for everyone no matter what, even in airplane mode.
Wifi has evolved a lot the last decade, not just by technology standards but into integration as well. carriers use them as small cells, we'll see them more often in the future (malls, stadiums, etc), and HS2.0 adds to make it a bit more seamless, they call it offload, taking your data needs through small wifi cells rather then the macro cells (3g, 4g), hence offload.
my point is that they would have never invested in that if the wifi chips inside consumer products were not efficient enough, so nearby APs shouldnt be a problem at all. But im still puzzled for what would one need the waking up process through wifi?
If Wifi is the general bugger, then somebody throw an eye on the Passport service, thats the consumer name for HS 2.0 services.
PS, tested AP Isolation on my sh!tty WRT120N, no difference unfortuantely.
Will there be a future update from Sammy or will we get Kitkat directly
Sent from my SM-N900 using Tapatalk
Just a follow up. I have still had no battery drain since avoiding connecting to wifi networks that use multiple APs. Now, i only connect to wifi networks where i know there is only one AP. Before I stumbled across this the drain and Android os wake lock was bad, really bad, after I had connected to large wifi networks - I just hadn't put two and two together. This is more than coincidence - my testing is sound and replicable. And, this week I have been in remote areas with weak to no 3g signal and the battery life has still been fantastic and no wake locks so that sort of rules that out - Sure there is a little increase in battery usage but nothing dramatic, something to be expected and certainly not something to complain about. I have seen many claims to fix battery drain but these are just fine tuning and not addressing the major drain caused by Android OS wake locks. Clearly, there must be an issue with the wifi software driver in MJ7/MK2 and I hope Samsung/Google are aware of it. The annoying thing is getting Samsung to acknowledge the issue and take feedback.
I get wake locks even if I manually turn wifi off and only use data. When I use wifi i am connected to only one AP and I still get wake locks. The wake locks aren't apps, they are "Powermanager.wakelocks" and "Powermanager.Display" and show up as "Android OS" in battery settings.
I am still not convinced avoiding multiple AP wifi networks is the one-for-all solution for everyone.
However, I have put "wifi on during sleep" to "never," yet my phone slept maybe 50% yesterday but wifi was on 100% of the time. Why is this? Shouldn't it have turned off the 50% that the phone was sleeping?
Something is weird with the wifi module..
Sent from my SM-N9005 using xda app-developers app
EddieN said:
I get wake locks even if I manually turn wifi off and only use data. When I use wifi i am connected to only one AP and I still get wake locks. The wake locks aren't apps, they are "Powermanager.wakelocks" and "Powermanager.Display" and show up as "Android OS" in battery settings.
I am still not convinced avoiding multiple AP wifi networks is the one-for-all solution for everyone.
However, I have put "wifi on during sleep" to "never," yet my phone slept maybe 50% yesterday but wifi was on 100% of the time. Why is this? Shouldn't it have turned off the 50% that the phone was sleeping?
Something is weird with the wifi module..
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Have you ruled out any other wifi connections? Have you tried rebooting if you have connected to another wifi network? Have you tried forgetting all wifi networks? Reboot after forgetting all networks. Then give it a couple of days with out connecting to any wifi network - just a test to confirm it is wifi related. I tend to think setting wifi to never on during sleep makes no difference - I had previously tried it too. Once the drain starts the only way to stop it is to reboot.
mongoose3800 said:
Have you ruled out any other wifi connections? Have you tried rebooting if you have connected to another wifi network? Have you tried forgetting all wifi networks? Reboot after forgetting all networks. Then give it a couple of days with out connecting to any wifi network - just a test to confirm it is wifi related. I tend to think setting wifi to never on during sleep makes no difference - I had previously tried it too. Once the drain starts the only way to stop it is to reboot.
Click to expand...
Click to collapse
Yes, just last week I was on another Wifi AP about ~300km away (totally different environment) and I still had the same wake locks. I have rebooted when connecting to another wifi network. I have tried forgetting all wifi networks i have connected to, and reconnecting to them. I have also rebooted once forgetting networks. During this time I also took the liberty of doing the normal rounds of disabling location services etc. before rebooting, but nevertheless i did reboot once forgetting the network. All networks I have been connected to have been single-AP wifi networks.
I have not let it sit for a few days without connecting to any wifi networks. That's the only thing I haven't tried. However I have let it go a whole day with wifi turned off (and only data enabled), but the same wakelocks persisted. For me it's always "Powermanage.Display" and "Powermanager.Wakelocks" no matter how long i just let my phone sit around with the screen turned off. I have it right beside me so I always have visual access to the screen in case the phone wakes up on its own, but it never has. I guess I could try turning wifi off for a few days and seeing how it fares, but I doubt I will see any difference (wake lock wise).
I'm thinking something is strange with the wifi module anyway. Surely wifi should turn off by itself once the phone sleeps, right? Like I said in my other post, my phone slept maybe 50-60% of the time on a 14 hour day. That means Wifi should have been on 40-50% of that time, and off 50-60% since the phone technically should have been sleeping. Yet I can see in the battery settings menu that wifi is a solid green bar all across the 14 hours.
EddieN said:
Yes, just last week I was on another Wifi AP about ~300km away (totally different environment) and I still had the same wake locks. I have rebooted when connecting to another wifi network. I have tried forgetting all wifi networks i have connected to, and reconnecting to them. I have also rebooted once forgetting networks. During this time I also took the liberty of doing the normal rounds of disabling location services etc. before rebooting, but nevertheless i did reboot once forgetting the network. All networks I have been connected to have been single-AP wifi networks.
I have not let it sit for a few days without connecting to any wifi networks. That's the only thing I haven't tried. However I have let it go a whole day with wifi turned off (and only data enabled), but the same wakelocks persisted. For me it's always "Powermanage.Display" and "Powermanager.Wakelocks" no matter how long i just let my phone sit around with the screen turned off. I have it right beside me so I always have visual access to the screen in case the phone wakes up on its own, but it never has. I guess I could try turning wifi off for a few days and seeing how it fares, but I doubt I will see any difference (wake lock wise).
I'm thinking something is strange with the wifi module anyway. Surely wifi should turn off by itself once the phone sleeps, right? Like I said in my other post, my phone slept maybe 50-60% of the time on a 14 hour day. That means Wifi should have been on 40-50% of that time, and off 50-60% since the phone technically should have been sleeping. Yet I can see in the battery settings menu that wifi is a solid green bar all across the 14 hours.
Click to expand...
Click to collapse
Well that's interesting. At least in both cases we know it's Wi Fi. I wonder if it's something if it comes down to the type of connection. Eg 2.4 vs 5ghz
mongoose3800 said:
Well that's interesting. At least in both cases we know it's Wi Fi. I wonder if it's something if it comes down to the type of connection. Eg 2.4 vs 5ghz
Click to expand...
Click to collapse
It could be. Both networks I have been connected to have been 2.4GHz Wireless-N capable routers. I just find it odd that a lot of things don't add up when looking at awake times in Settings -> Battery and comparing it to kernel/partial wakelocks in BBS/WLD/CPU Spy. All of the times seem to be roughly in the same ballpark, but they never add up to correspond to each other. Surely there must be information missing in this regard.
I can confirm the WiFi issue on my N9005 but there's another one.
1. Wifi: I experienced this at my university, where we have good Wifi coverage on the whole campus. They use Radius for logging in. After using Wifi for about 15min, I had these wakelocks, which didn't stop until I rebooted the phone. Since I knew this, I haven't been using Wifi there any more. But: In the meantime, I did a factory reset and got this little stability update. A few days ago, I gave it a try again. Used Wifi at university for ~25min and hat no issues. Maybe it's gone, I will test again some day.
2. I had an app called "gentle alarm". On my GNexus, which I used before my Note 3, I also had wakelocks, but couldn't figure out what it was, since wakelock detector, better battery stats etc. didn't show more than PowermanagerService.Wakelocks/Display. So I got my new Note 3 and still had these Wakelocks - I did much Monitoring and: It was this tiny alarm app. Very funny: After having excluded every other possibility and having the wakelocks active I uninstalled the app on my Note 3 and it instantly rebooted!
Great battery life now.
Hope this helps someone. BTW: The Wifi issue on larger networks seems to be a problem not only on Samsung phones, many people are experiencing this (e.g. found similar reports for Nexus 5...).
duffmannr3 said:
I can confirm the WiFi issue on my N9005 but there's another one.
1. Wifi: I experienced this at my university, where we have good Wifi coverage on the whole campus. They use Radius for logging in. After using Wifi for about 15min, I had these wakelocks, which didn't stop until I rebooted the phone. Since I knew this, I haven't been using Wifi there any more. But: In the meantime, I did a factory reset and got this little stability update. A few days ago, I gave it a try again. Used Wifi at university for ~25min and hat no issues. Maybe it's gone, I will test again some day.
2. I had an app called "gentle alarm". On my GNexus, which I used before my Note 3, I also had wakelocks, but couldn't figure out what it was, since wakelock detector, better battery stats etc. didn't show more than PowermanagerService.Wakelocks/Display. So I got my new Note 3 and still had these Wakelocks - I did much Monitoring and: It was this tiny alarm app. Very funny: After having excluded every other possibility and having the wakelocks active I uninstalled the app on my Note 3 and it instantly rebooted!
Great battery life now.
Hope this helps someone. BTW: The Wifi issue on larger networks seems to be a problem not only on Samsung phones, many people are experiencing this (e.g. found similar reports for Nexus 5...).
Click to expand...
Click to collapse
Thanks for your input. Is the wifi issue you are talking about the fact that it doesnt turn off when having "wifi on during sleep -> never" set? Or the multiple-AP issue the thread is talking about?
What stability update is it that you have received? What country are you in and what firmware are you using? Did you get this stability update while on MJ7/MK2 firmware? I haven't received any notification for a stability update OTA...
Thanks for the Powermanager.Display/Wakelock issue. I guess I will have to sift through my apps and uninstall each, one by one, to see if the wakelocks disappear. If not, there is some other issue
EddieN said:
Is the wifi issue you are talking about the fact that it doesnt turn off when having "wifi on during sleep -> never" set? Or the multiple-AP issue the thread is talking about?
Click to expand...
Click to collapse
It's the issue about "multiple" APs, but I don't think that it is about the number of APs. What I have read is that there is so much traffic on those big networks, e.g. broadcasts from other devices. I don't know how it should be with your problem that wifi doesn't turn off - can you see if it's reconnecting after some standby time? If yes, then wifi is turned off during sleep, but is just not shown in statistics.
EddieN said:
What stability update is it that you have received? What country are you in and what firmware are you using? Did you get this stability update while on MJ7/MK2 firmware? I haven't received any notification for a stability update OTA...
Click to expand...
Click to collapse
I'm currently on MJ7/MK2. My device is unbranded and I'm living in Germany. It came on 26th of December and was about 30MB or so.
EddieN said:
Thanks for the Powermanager.Display/Wakelock issue. I guess I will have to sift through my apps and uninstall each, one by one, to see if the wakelocks disappear. If not, there is some other issue
Click to expand...
Click to collapse
It's definitely worth a try! There was absolutely no hint that pointed to this one app. I started with having a look at the battery statistics ~every 30min after a fresh reboot. After a few days it was clear that it only could be the alarm app, battery draining started only in the morning.

Bluetooth causing extremely slow wifi

So I've had my m8 since launch, about May of 2014. I've never once had a problem with my wifi, until last week. All of a sudden, I noticed all of my wifi connections (home, work, etc) are all extremely slow. Speed tests are barely getting 1mbps down or up, and the test itself is very erratic, bobbing up and down the whole time. All my other devices are fine, and nothing with any of my wifi connections has changed. I uninstalled about 3 apps that I had installed within the last month, with no change. Verizon sent me a replacement m8, and I got it yesterday, loaded up all my stuff, and low and behold, still slow wifi.
After talking with numerous Verizon techs, they can't solve it, even after multiple factory resets. However, this morning I saw a post while googling it, not an m8 but still android. They said that if Bluetooth is on, but not connected to a device, it could cause issues. So I turned my bluetooth off, and speeds were perfect, getting exactly what my internet connection is. Turned it back on, and back to 1mbps.
So one, why is this happening? I've read that the bluetooth and wifi antennas are the same, and that could cause interference, but it should not be this bad. Second, why did this just now all of a sudden start? I didn't usually leave bluetooth on, but I got a new car about 3 months ago, and decided to leave it on to automatically connect when I'm driving. But it was fine until last week, why the change?
Have you discovered anything new? I've had my Verizon m8 since April 2014 and have always left bluetooth on for my fitbit to sync. I only recently started having problems and can't identify any recent update that happened this month that would cause it. When bluetooth is on and a device is connected my wifi performance is very slow - 100+ ms ping, 1-2Mbps up/down doing a speedtest. Turn bluetooth off and speed test again then wifi performance jumps to 20Mbps up/down with 12ms ping times to the same speedtest server.
I have factory reset my phone 3 times, changed wifi channels, tried 2 different routers and 1 access point. None of the wifi changes affected speeds until bluetooth was turned off. It seems to be a little quicker 3-5 Mbps with bluetooth on and no devices paired but still that's not acceptable.
sitlet said:
So I've had my m8 since launch, about May of 2014. I've never once had a problem with my wifi, until last week. All of a sudden, I noticed all of my wifi connections (home, work, etc) are all extremely slow. Speed tests are barely getting 1mbps down or up, and the test itself is very erratic, bobbing up and down the whole time. All my other devices are fine, and nothing with any of my wifi connections has changed. I uninstalled about 3 apps that I had installed within the last month, with no change. Verizon sent me a replacement m8, and I got it yesterday, loaded up all my stuff, and low and behold, still slow wifi.
After talking with numerous Verizon techs, they can't solve it, even after multiple factory resets. However, this morning I saw a post while googling it, not an m8 but still android. They said that if Bluetooth is on, but not connected to a device, it could cause issues. So I turned my bluetooth off, and speeds were perfect, getting exactly what my internet connection is. Turned it back on, and back to 1mbps.
So one, why is this happening? I've read that the bluetooth and wifi antennas are the same, and that could cause interference, but it should not be this bad. Second, why did this just now all of a sudden start? I didn't usually leave bluetooth on, but I got a new car about 3 months ago, and decided to leave it on to automatically connect when I'm driving. But it was fine until last week, why the change?
Click to expand...
Click to collapse
I too have had bluetooth on for months to be able to connect to my car, never had a problem until about a month or so ago. I did two factory resets, and everything seemed to work fine, but after a day or so, when all my apps were back on the phone, it would start up again. I have a hard time believing a specific app is doing this, unless it was one of the HTC Home updates or something.
Verizon sent me a replacement M8, I got all my apps on it, and the same thing, after a day or so it's super slow with Bluetooth on, horrible ping and less than 2mbps down and up.
So then I contacted HTC directly, did all their troubleshooting, factory reset, and it's still there. They sent me a replacement as well. I turned it on, but did not put my sim into it. I spent 2 days with it, and only downloaded the Speedtest app, nothing else. Speeds are fine with bluetooth on. I then downloaded the rest of my apps (I actually do have quite a few apps, so if it's one of them it will be a pain to figure out which one). It's been two days now and speeds are still good with bluetooth on. Later today I'm going to offically move over to this phone and put my sim in it.
It's just really frustrating to keep turning bluetooth off and on again, and there should be no reason for this to be happening out of the blue all of a sudden.
sitlet said:
I too have had bluetooth on for months to be able to connect to my car, never had a problem until about a month or so ago. I did two factory resets, and everything seemed to work fine, but after a day or so, when all my apps were back on the phone, it would start up again. I have a hard time believing a specific app is doing this, unless it was one of the HTC Home updates or something.
Verizon sent me a replacement M8, I got all my apps on it, and the same thing, after a day or so it's super slow with Bluetooth on, horrible ping and less than 2mbps down and up.
So then I contacted HTC directly, did all their troubleshooting, factory reset, and it's still there. They sent me a replacement as well. I turned it on, but did not put my sim into it. I spent 2 days with it, and only downloaded the Speedtest app, nothing else. Speeds are fine with bluetooth on. I then downloaded the rest of my apps (I actually do have quite a few apps, so if it's one of them it will be a pain to figure out which one). It's been two days now and speeds are still good with bluetooth on. Later today I'm going to offically move over to this phone and put my sim in it.
It's just really frustrating to keep turning bluetooth off and on again, and there should be no reason for this to be happening out of the blue all of a sudden.
Click to expand...
Click to collapse
Strange issue, but from how you described it, it must be a 3rd party application. What I would do in this situation, is do the factory reset, and download 5 apps at a time. Until you narrow it down to the 5 apps that are causing the issue, then you can narrow it down much easier out of the 5 applications. A pain, yes. but once you figure out the app that's causing the issue, you may decide you don't need it, or you only use it once in awhile and can remove it, until you need it, or possibly download an app ops application from the Playstore and remove the Bluetooth permissions and see if that fixes it.
Best of luck.
Seems to help...
I just tried the solution offered in another forum (xda won't let me post the link so I'll copy and paste the information here:
Open page with the available "Wi-Fi" networks (Settings, WI-FI)
Tap on the "3 dots" in the upper right corner
"Wi-Fi Direct"
Tap on the "3 dots" in the upper right corner
"Rename device"
Replace "Android_ed2c" with "HTC One" (or whatever you want) and hit "OK"
Before doing this I had a 300ms ping when Bluetooth is on, and very low bandwidth. Now with Bluetooth on the wifi ping is around 50ms (normal for my home internet) and the bandwidth is back to normal. Time will tell if it sticks, but so far so good!
So I had been running all my apps on my replacement phone for about a week now, and have had no problems. The other day I officially swapped my sim card into this new phone, and for two days now, it's been fine. Bluetooth and wifi are on constantly, and I see no issues with bandwidth. So who knows why the last two devices had a problem, but for now it seems to be fixed.
Having the same issue, originally posted on reddit and then found this thread: https://www.reddit.com/r/techsupport/comments/3kv6z6/wifi_issues_with_multiple_phones/
Turned off bluetooth and it's fine... Will be experimenting with my gf's m8 this weekend.
MJB_One said:
I just tried the solution offered in another forum (xda won't let me post the link so I'll copy and paste the information here:
Open page with the available "Wi-Fi" networks (Settings, WI-FI)
Tap on the "3 dots" in the upper right corner
"Wi-Fi Direct"
Tap on the "3 dots" in the upper right corner
"Rename device"
Replace "Android_ed2c" with "HTC One" (or whatever you want) and hit "OK"
Before doing this I had a 300ms ping when Bluetooth is on, and very low bandwidth. Now with Bluetooth on the wifi ping is around 50ms (normal for my home internet) and the bandwidth is back to normal. Time will tell if it sticks, but so far so good!
Click to expand...
Click to collapse
Thanks for the post. Tried this, but no luck. Hopefully it can work for others
Sent from my HTC6525LVW using Tapatalk
Multiple threads discussing this issue...
http://forums.androidcentral.com/htc-one-m8/565952-app-causing-slow-wifi.html | 2015-AUG-12
http://forum.xda-developers.com/ver...luetooth-causing-extremely-slow-wifi-t3177402 | 2015-AUG-12
https://www.reddit.com/r/htcone/comments/3kr2sb/why_did_my_htc_one_m8_wifi_get_so_slow/ | 2015-SEP-13
https://www.reddit.com/r/techsupport/comments/3kv6z6/wifi_issues_with_multiple_phones/ | 2015-SEP-13
https://www.reddit.com/r/htcone/comments/3n8xu1/problems_with_wifi_connection_unable_to_find_help/ | 2015-OCT-02
https://www.reddit.com/r/htcone/comments/3n663y/m8_wireless_downloads_falling_to_the_center_of/ | 2015-OCT-01
Same HTC M8 issue - very slow WiFi when Bluetooth is running
Same problem on an HTC M8... speedof_dot_me speed test shows 96 ms latency with D/L at 0.07 mbps (really!) on an 11 mbps router. Turned off Bluetooth, and voilla! Latency dropped by 85% and WiFi speeds increased by a factor of 60! I suspect an HTC issue since an August or September update... since this wasn't occurring prior to August.
Verizon sent me a replacement M8 that was on 4.x.x android. I updated via on-air update (not rooted) to Lollipop and installed all my apps. Everything was fine. That night, it did a security update and, since then, my wifi+bluetooth were horked when turned on together.
Do, I did a factory reset (which doesn't undo the updates), but since doing the factory reset and installing just the basic Play-store updates 24 hours ago, the problem is not back.
I'm going to slowly add back my normal apps this time.
Solved on one plus one
Hello, i had since two weeks the similar issue. when bluetooth is switchef on (unconnected), wifi is very slow. in the past this different, so no issue with hardware and frequencies. Finally, I found out that it was linked to an App that accesses Bluetooth.
In my case it was the App Accu-Chek, I read in a big forum that it was linked to a Garmin app.
Uninstalling the App solved the issue.
My wife has a similar issue on Stock Galaxy S4 mini with that App.
This is definitely app-related. I tried force closing out of a bunch of apps that weren't related to the video I was playing and it seemed to fix the bandwidth issue with bluetooth enabled. Guess I'll need to experiment with closing certain apps until I find the culprit.
I was having this same problem. It looks like the RetailMeNot App was the culprit for me.
clusterchuck said:
I was having this same problem. It looks like the RetailMeNot App was the culprit for me.
Click to expand...
Click to collapse
You sir deserve a cookie. Thanks for pointing out the worst app of 2015.
Solved on my Phone!
I used to have the same problem. I am having a Sony Xperia Z1 Compact and a Smartband Talk. At the beginning everything was fine but after sometime (strongly caused by a software related issue) I begin to face the same problem. While bluetooth is on WiFi bandwith dropped to a very little amount (around 0,02- 0,01 Mbits/s). Then I read somewhere, about how to verify whether it is a software or hardware issue via checking it in the Safe Mode. So I unpaired by smartband talk and uninstalled the smartband talk software (smartband talk requires a bluetooth connection for functioning). Then restarted my phone in to safe mode by tapping and holding the power off on the shutdown menu. I downloaded the smartband talk software and turned on my bluetooth and paired my smartband talk again. Then restarted my phone in to normal mode. And voila, problem solved.
It is not a guaranteed method but worth to try.
Wish you good luck.

Wi-Fi bug on all stock and custom roms

Greetings!
I wanted to share my strange problem and ask if anyboby has and idea on how to solve it.
Recently I have been having trouble with my Wi-Fi. When I leave the phone with Wi-Fi turned on and it falls asleep, or when I push the power button to make the phone fall asleep, Wi-Fi crashes... I can still use the phone, I can still charge it... The Wi-Fi indicator in the status bar is active too... Another thing is, If I leave the phone charging, Wi-Fi never crashes, I can leave it for throughout the night, I usually do that when I watch a Twitch stream and fall asleep, Wi-Fi works perfectly there... Decided to dig around a bit, I read a lot of threads, tried deleting /data/misc/wifi; tried freezing the logic board in the fridge; tried BAKING the logic board (it survived perfectly); tried switching stock roms, custom roms, radios even and a bunch of other things I can't recall now... Then, I decided to look at the logs and there were a lot of errors (log attached below), I looked at dmesg, there was NO problem powering on the Wi-Fi chip at all (as it is with other people having problems)... BUT, I thought of something funny! Why not install Firefox OS, I've never tried it and guess what... Wi-Fi was perfect there, the phone was able to fall asleep, Wi-Fi turns off when the phone falls asleep, then it turns back on perfectly! I don't want to be stuck with Firefox OS though, hence creating my first ever thread in XDA!
What do you guys think, is the logic board screwing around and having fun with me (hw failure) or is it something software-related? I am at a total loss...
Best regards to everybody!

[6039s] Google Play (I think) wakelock issue

I can't figure this out to save my life. 6039s Android 6. No root. No special mods. Nothing. Bone stock.
In the middle of the day today I suddenly started getting a horrendous wakelock. I thought it was a Google Play issue but it turned out that it's some kind of mobile data issue.
My LTE connection isn't working right. It's slow for some apps and non existent for others.
For instance my sports score app loads at 2G speeds. My web browser seems to work okay. But my t mobile tuesday's app gives me a big warning that I'm not connected to the internet at all. And the Google Play app gives me all kinds of warning that I need to have background data enabled to use Play, but background data IS enabled.
Making matters worse, when this issue is happening my phone enters a miserable and unstoppable wake lock that drains the battery so fast it hard to even charge it. And it saps up the system resources to heavily that the phone slows down to a crawl and can't be used for anything else. Not to mention the phone gets insanely hot from the excess processing. Could a tower issue that's causing a connection problem cause such a wakelock?
I tried doing a reset of the radio connections in settings, but I don't think it actually did anything because all my settings and connections were still there. Still had my wifi password, BT connections, etc.
I tried wiping cache in recovery but it didn't work. Says it did it. But on reboot I didn't get the "app 1 of 82 is updating". So I don't think it actually did that either.
I cannot figure this out to save my life.
I thought maybe it was a tower issue. But my wife has the exact same phone and it's working fine. I called T Mobile and they said they are having a tower problem near my house, but still...wife's phone is fine. And I've seen this problem now in 3 different locations across about a 5-6 mile range. So I have to have been on more than 1 tower in that time.
When I turn on wifi and have a wifi connection the problem goes away entirely. That's telling me that the problem is the system getting upset that it doesn't have a solid internet connection. Changing the connection to 3G or 2G does not solve the issue.
The problem lasted the whole second half of yesterday, was fine overnight while I left wifi on, was fine on day 2 when I was back to 4G networks, and then suddenly is back again.
Anyone got any ideas or suggestions?
Is there some server android is trying to stay in constant contact with that I can block the connection to? Perhaps limit background data to something? I can't figure out what.
This update was irrelevant. Turned out to be a red herring. Still having the problem.
Nevermind this update. STill having the problem
I give up. I'm about to throw the phone against a wall to smash it. The system has become totally loused up. Whenever it goes into these goofy wakelock states the system is so overtaxed that everything takes forever to process. Nothing solves it.
And its' getting worse. Now I have oddly limited connectivity.
T Mobile's tech support was useless. They had me thinking it was a tower issue. That was 3 days ago. Now suddenly they have no records of a tower issue in my area over the last week.
I can make voice calls. But I cant' send text messages. I can use my web browser to search the internet, but not SOME apps that need data like a weather app or Google Play. Other apps work fine to pull data.
Yet it says I have an LTE connection the whole time.
This is the single weirdest issue I've ever seen on Android.
What in the hell could have just jumped in out of nowhere and started causing these issues?

Categories

Resources