Database Users

Phone died for no reason... had to remove battery? wth?!

Hello guys,
I noticed something strange this morning, my phone was simply dead... no response whatsoever.
Battery was 90% charged before I went to sleep, but I thought that maybe I had active data connection and that drained my battery. Anyway I plugged in charger... orange LED indicator lit up but phone would still not turn on.
Finally removing battery and waiting 10 sec helped.
Has anyone experienced that as well?
Also I didn't have any 3rd party apps runing in background and I'm with stock rom... any ideas guys?
Regards
Pete

Had this happen to me yesterday, I just had to soft-reset the device with the re-reset button and it rebooted. In my case it may be related to .NET 3.5 and BSB Tweaks which I had just installed for the first time and was using to tweak some stuff. It never happened before (more than 1 month of use).

Damn... this is a bit scary... I mean what If you are waiting for an important phone call and your phone is simpy off?:/
In my case I did not install any 3rd party apps apart from palringo and spb wireless monitor... no tweaks anyway:/
Hopefully it won't happen again.

The same thing happened to me 2 hours ago. Absolutely no idea why. Only removing the battery helped.

There are already threads about this. Please search before posting ...

since i have a Leo Rom on my HD (1) i had this problem too. So i think there is a bug in Software.

Same happened to me guys... Also after installing BsB tweaks 1.6 and changing some things...
I think I know where the problem might be, because my green led light was flashing when I tried to unlock my phone...
I had changed the led flash light blinking time to unlimited and I am pretty sure this was the cause of it, because it happened two times to me, both of the times the flash light was blinking but I couldn't get a response from my phone!
I've turned that off now and hope it will help cause I was awake 1 hour too late today!

petexx said:
Hello guys,
I noticed something strange this morning, my phone was simply dead... no response whatsoever.
Battery was 90% charged before I went to sleep, but I thought that maybe I had active data connection and that drained my battery. Anyway I plugged in charger... orange LED indicator lit up but phone would still not turn on.
Finally removing battery and waiting 10 sec helped.
Has anyone experienced that as well?
Also I didn't have any 3rd party apps runing in background and I'm with stock rom... any ideas guys?
Regards
Pete
Click to expand...
Click to collapse
Pete,
See the topic here where this has already been mentioned.
Beards
ChefChaudart said:
There are already threads about this. Please search before posting ...
Click to expand...
Click to collapse
You are quite correct ChefChaudart, it is my topic.

Happened to me yesterday as well. Was the first time this has happened. I couldn't even do a soft reset. Had to take out the battery. Been fine ever since though...

seems strange that this happened to many people yesterday, including me! Never happened before........

Guys,
Again, there is already a Topic which covers this here.

tmobile htc hd2 wifi/battery problem

hey you guys, i was trying to turn wifi on my phone off today and when i went into settings, the wifi icon was on the "green on" switch, but it was kinda grayed out so it wouldnt let me turn it off. do any of you know what the problem could be? thanks, also my hd2s battery dies really fast, it only lasts a few hours and drains really bad when im listening to music , even with the screen turned off, i know that battery problems have been posted all over the forums but has any fix been released? or should i just get a new battery? thanks

barronedson said:
hey you guys, i was trying to turn wifi on my phone off today and when i went into settings, the wifi icon was on the "green on" switch, but it was kinda grayed out so it wouldnt let me turn it off. do any of you know what the problem could be? thanks, also my hd2s battery dies really fast, it only lasts a few hours and drains really bad when im listening to music , even with the screen turned off, i know that battery problems have been posted all over the forums but has any fix been released? or should i just get a new battery? thanks
Click to expand...
Click to collapse
You Battery is Dying fast because of the WiFi being left on. Try to re-install the ROM. Also please give more info regarding the ROM you are using. So I could help you further.

The wifi icon being gray means it's turning on or of but in your case I believe it's simply stuck. If reboot doen't do a trick, reinstall ROM or install another one.

[Q] Weird wakelock mmc0:0001:2

Under kernel wakelocks in better battery stats. Is anyone getting the mmc0:0001:2 wakelock? It has some serious counts an I think it's a culprit of some deep sleep issues. I tried with factory reset and not restoring anything, just installing bbs and its still there. I'm attaching a pic of insane 1.9 million counts. Anyone got any idea what this is?
EDIT: okay, so I did notice it was ticking like insane when I was downloading some games. And figured I would try turning off Wi-Fi, look and behold, it stopped ticking. Even when I turned it back on it back on it didn't tick up either. But if I turned if screen and later checked it was ticking again. My router had been acting weird lately so I made it forget it and put up a hot spot on my other phone. Now it doesn't tick up either, so must be my router D-Link DIR-655 with latest firmware. Good thing in getting a new router next week. Will update if it's better (going to buy a DIR-865L). Please do report if you are having same problem and find other solution though.
EDIT2: I left it using hot spot and awake time went up like 2 min and deep sleep 1.5 hours. Now it sleeps like a baby. Will update with new router next week. Hope this helps someone.
EDIT3: After a restart it started ticking up again for some reason even when connected to hot spot.

wargreymon89 said:
Under kernel wakelocks in better battery stats. Is anyone getting the mmc0:0001:2 wakelock? It has some serious counts an I think it's a culprit of some deep sleep issues. I tried with factory reset and not restoring anything, just installing bbs and its still there. I'm attaching a pic of insane 1.9 million counts. Anyone got any idea what this is?
EDIT: okay, so I did notice it was ticking like insane when I was downloading some games. And figured I would try turning off Wi-Fi, look and behold, it stopped ticking. Even when I turned it back on it back on it didn't tick up either. But if I turned if screen and later checked it was ticking again. My router had been acting weird lately so I made it forget it and put up a hot spot on my other phone. Now it doesn't tick up either, so must be my router D-Link DIR-655 with latest firmware. Good thing in getting a new router next week. Will update if it's better (going to buy a DIR-865L). Please do report if you are having same problem and find other solution though.
EDIT2: I left it using hot spot and awake time went up like 2 min and deep sleep 1.5 hours. Now it sleeps like a baby. Will update with new router next week. Hope this helps someone.
EDIT3: After a restart it started ticking up again for some reason even when connected to hot spot.
Click to expand...
Click to collapse
Galaxy Note 3 here. I'm getting the same thing, it's causing my phone to stay awake 100% of the time. I turned off my wifi and now the problem is done, but that is a huge hassle as I want to be connected to wifi all day if possible.
Will see if it's a router/modem issue or if it's a wifi on the phone issue.

Niviac said:
Galaxy Note 3 here. I'm getting the same thing, it's causing my phone to stay awake 100% of the time. I turned off my wifi and now the problem is done, but that is a huge hassle as I want to be connected to wifi all day if possible.
Will see if it's a router/modem issue or if it's a wifi on the phone issue.
Click to expand...
Click to collapse
Okay so, kinda forgot to update this thread, forgive me, Im a human I got my new router DIR-865L and I keep getting the same wakelock, however, this doesnt seem to make my phone to wake anymore, so I guess it was my old router, DIR-655 that gave the wakelocks. If you can try with a new router or at least another.

My Galaxy S4 LTE-A has the same problem. It occurs only when I connected to wifi.
Mmc0:0001:2 seems related to sd card, so I removed my external sd card.. but it did no trick.
And it is thought to lead to battery drain.
When connected wifi, battery decreases about 3% per hour, which is nearly three times to LTE.
Sent from my SHV-E330S using Tapatalk

Any updates/solutions? I have the same problem, it started after i rooted my LG G2. Unrooting/changing firmware/factroy reset or changing my router gave no effect

Same problem guys, I have this wakelock always.
Anyone has any solution for it?
send from my N9005 with tapatalk

I have the same thing now, wakelock detector app is showing it running hundreds of thousands of times with the phone only on for a few hours.

[Q] msm_hsic_host wakelock keeping s4 awake

Today I noticed this wakelock kept my device away 80% or more of the time it has been on battery (11h13m at the time of posting this). To give you an idea of how little I used it in the time screen on time is only 33 minutes. And the only time I used it for anything was when I had the screen on. I can't seem to track down any info on what would be causing this wakelock on my s4. I found in a google search about this on other devices like the nexus which pointed back to a thread here on xda that said it is due to " the 3G modem is connected to the phone as an external USB device controlled by the hsic host controller". Problem is I don't use USB for anything with my s4. No new apps or changes have been made to my s4 in ages so I can't even contribute it to anything that has changed recently. I use the same apps I have been using for ages. I've been home all day today as I had the day off. I use wifi at home. CPU spy lists my uptime as 29 hours I rebooted last night while out with friends because flixter wasn't working right. After the reboot flixter worked fine. And I put it on the charger when I got home. In case any of this has any bearing on this. Is there a way for me to find out what causes(ed) this wakelock on my s4 so that I can troubleshoot that thing and make any reports needed to the respective people to correct the problem causing it?

I have kindoff the same problem
StoneRyno said:
Today I noticed this wakelock kept my device away 80% or more of the time it has been on battery (11h13m at the time of posting this). To give you an idea of how little I used it in the time screen on time is only 33 minutes. And the only time I used it for anything was when I had the screen on. I can't seem to track down any info on what would be causing this wakelock on my s4. I found in a google search about this on other devices like the nexus which pointed back to a thread here on xda that said it is due to " the 3G modem is connected to the phone as an external USB device controlled by the hsic host controller". Problem is I don't use USB for anything with my s4. No new apps or changes have been made to my s4 in ages so I can't even contribute it to anything that has changed recently. I use the same apps I have been using for ages. I've been home all day today as I had the day off. I use wifi at home. CPU spy lists my uptime as 29 hours I rebooted last night while out with friends because flixter wasn't working right. After the reboot flixter worked fine. And I put it on the charger when I got home. In case any of this has any bearing on this. Is there a way for me to find out what causes(ed) this wakelock on my s4 so that I can troubleshoot that thing and make any reports needed to the respective people to correct the problem causing it?
Click to expand...
Click to collapse
I also have the same problem with my s4, I installed greenify and DS battery saver but they don't help. My device wont ever go into deep sleep!
I am on 4.3.1 and the thing is that I have something broken on my modem too, so maybe my situation is different. So I'm trying to use my device as a tablet but my battery gets eaten away like hell.

wlan_rx_wake (battery drain while in sleep on certain wifi)

Anyone having this problem and with a solution?
For me it's happening only at home: I have a wifi 2.4GHz router connected to a network cable coming from an adsl modem, and a 2.4GHz range extender that I use only to catch signal in the living room and is connected with a network cable to my satelite receiver.
It seems that something is keeping my phone on continuously during sleep, causing a constant discharge of 2% in 6h. I spent 3 night in the hotel and it didn't happened there.
I'll try to sort out if it's the router or the extender, but it'll take 3 nights to test.
In the meantime I'd like to know if someone else has had the same problem with wlan_rx_wake wake locks and how it got soloved?
Thanks

Let's all play nice and use this thread to help solve the problem, please don't however cross post this else where looking for further help. Let's keep it in here. Seem fair?
Have a good day all.
Forum moderator,
Matt

Matt, sorry if I post crossed, but I am desperate and was trying to find help in any possible thread that had battery drain as a subject. Been in this forum for years and never did this before, and if I did it it's cos I'm really puzzled.
I have also tried contacting Nexus support and have provided them with a bug report to look at with battery historian, but they came back to me asking for screenshots!!!!!
BTW, the bug report can be found here
https://www.dropbox.com/s/35l80fq9x...ight, during sleep-2016-08-12--06-00.zip?dl=0
in case someone is willing to have a look and let me known what the real problem is, as I can only guess it's wlan_rx_wake but I'm not even sure.
Anyhow, I am rooted now and will check what better battery stats says yonight.

found the problem: the wifi range extender. Maybe it is sending packets on the net that is keeping wifi alive and preventing phone to sleep well, causing a 2% per hour drainage. Tonight I kept it off and lost 2% in 9h.
My 3 Samsung devices (A3, S6 and Tab S2) are not experiencing this problem, so it must be a bug in nexus 6p kernel.