Related
Apologies for any double posts in two forums; thought This would be a better place to ask than the General Forum.
Mods: Didn't know whether to post in this thread: http://forum.xda-developers.com/showthread.php?t=540559..
http://forum.xda-developers.com/showthread.php?t=540559
-----
I've Had my phone rooted, new Radio (Since Dec.) running latest LeeDroid.
Had my phone just the way i like everything, been very impressed with battery life over the past month with brilliant ROM updates.
Then randomly last week Wi-Fi usage shot up to the 60-90 mA level.
Why?
No new Rom had been installed for 2 weeks, so it wasn't that.
Wi-Fi off was 1-4 mA.
- I thought maybe its the applications I updated; Uninstalled all of them
Didn't work
- Maybe its fiddly settings like SYnc etc that have changed since App updates etc...
No settings had been altered.
- Maybe its a cache stats thing, I'll do a full wipe (Via CWM in Recovery Mode, select "Wipe Data/FactoryReset" option) and re-installed an even newer version of LeeDroid.
Still the battery drained 7-9 percent an hour on Standby(Screen Off).
1) Is it my router?
2) Is it a faulty WiFi part in the phone
3) What else besides the other two could it be?
i.e. - Battery was 60 percent with Wi-Fi on. -- Phone put into what appeared to be "Sleep Mode" (Pressing the power button once.)
-- 8 hours later battery was 15 percent!
Spare Parts showed "Time since Phone was in sleep" 8H
"Time since Wi-fi was in sleep" 8H.
Help greatly appreciated.
I had the same problem, disabling email sync in gmail solved the problem for me
Thanks GurliGebis; Tried that too even though I hadn't changed that setting since last week (When everything was fine).
Still no luck.
Any other thoughts?
Although almost 5 months have passed from the last reply on this thread I continue to have the EXACT same problem as you Tapori...
Have u figured it out mate?
Please reply if u have.
Thanks
DanteGR said:
Although almost 5 months have passed from the last reply on this thread I continue to have the EXACT same problem as you Tapori...
Have u figured it out mate?
Please reply if u have.
Thanks
Click to expand...
Click to collapse
Have you checked the drain in other routers?? Check it in another place, friends house, work.. and see if its happening the same every where
Sent from my Toilet using XDA App
elazari said:
Have you checked the drain in other routers?? Check it in another place, friends house, work.. and see if its happening the same every where
Sent from my Toilet using XDA App
Click to expand...
Click to collapse
I have tried it elsewhere and drain seems to be ok as far as i can recall. The problem is that even with my home router SOMETIMES there is no problem and drain seems normal.
So it's just a random thing but oh so annoying when it happens.
Thanks for trying to help though
As said in title, I have a problem after updating to Gingerbread. In battery use it says that Dialer is using about 20% of battery. Does anyone else have this problem and are there any solutions for it?
I have this problem too, i opened another thread, btw i made a factory reset but the problem is still present.
I think that there aren't solution now, because htc in this new 2.3.3 rom change the radio,
i forced mine to only wcdma mode and disabled always-on mobile data.also i disabled best wi-fi performance when wifi is enabled.also when mobile data is switched on, i turn off wifi and vice versa. far now it is much better. if anyone do like me, pls tell me if is any improvement for you.
sedatif781 said:
i forced mine to only wcdma mode and disabled always-on mobile data.also i disabled best wi-fi performance when wifi is enabled.also when mobile data is switched on, i turn off wifi and vice versa. far now it is much better. if anyone do like me, pls tell me if is there any improvement
Click to expand...
Click to collapse
Perhaps leaving wcda always active will consume more than ever to leave gsm mode?
However disabling always-on mobile data in 2g/3g settings menu,your apps and widgets are updated automatically?
when i leave only wcdma, i think will consume less power because it didnt try always and always to switch to better signal (from 2g to 3g and vice versa).i have only weather auto update on and i didnt noticed any change .
sedatif781 said:
when i leave only wcdma, i think will consume less power because it didnt try always and always to switch to better signal (from 2g to 3g and vice versa).i have only weather auto update on and i didnt noticed any change .
Click to expand...
Click to collapse
Now i have only GSM mode, btw i can try to disable always on mobile data keep active in the 2g/3g menu and hope that this radio will consume less power.
I thought maybe the problem could be caused by a bug introduced with the new management processes that consume the battery, also because there is the graphic that was not there.
Let me explain:
The details of the processes that consume battery is correct because if I go on "DIALRE" the voice tells me that the CPU has been used only 6 minutes in 20 hours, so little, but shows the % is too high.
Same thing with regard to the voice "Telephone inactive", says it's been idle for less than 20 minutes that I used. but the % is too low.
So it could be a bug that we see that the phone uses too much and we blame the new radio?
Hi everyone
Dialer uses much battery, because it's using the sensors all the time (even with screen off/standby).
You can check that for example in "Battery History for GB" app (you'll find it on xda...)
I wrote some posts about this issue on the ARHD thread in DHD Development (just search for "Dialer" on the thread).
So far no one has a solution... so I guess it's a bug HTC build in... :/
If any one has a solution or a fix please post it
EDIT:
jackalac said:
So it could be a bug that we see that the phone uses too much and we blame the new radio?
Click to expand...
Click to collapse
I tried 3 different radios... I had that problem with each one of them.
scungilli said:
Hi everyone
Dialer uses much battery, because it's using the sensors all the time (even with screen off/standby).
You can check that for example in "Battery History for GB" app (you'll find it on xda...)
I wrote some posts about this issue on the ARHD thread in DHD Development (just search for "Dialer" on the thread).
So far no one has a solution... so I guess it's a bug HTC build in... :/
If any one has a solution or a fix please post it
EDIT:
I tried 3 different radios... I had that problem with each one of them.
Click to expand...
Click to collapse
So, the problem is the official 2.3.3 not the new radio?
Btw, also with dialer voice at 30% of consume, i have 28% of battery available now and the last unplugged was 1g and 15 hours ago, with medium use,.
Whit the 2.2.1 with the same use, my best was 1g and 6h.
jackalac said:
So, the problem is the official 2.3.3 not the new radio?
Btw, also with dialer voice at 30% of consume, i have 28% of battery available now and the last unplugged was 1g and 15 hours ago, with medium use,.
Whit the 2.2.1 with the same use, my best was 1g and 6h.
Click to expand...
Click to collapse
Seems like it's a problem with the official release.
If you google the issue you'll find people with other phones solving the issue by setting the "Turn to mute" feature to off...
Problem with this: We don't have that setting :/
For me Dialer doubles the standby battery use... so battery life is good, but could be much better.
scungilli said:
Seems like it's a problem with the official release.
If you google the issue you'll find people with other phones solving the issue by setting the "Turn to mute" feature to off...
Problem with this: We don't have that setting :/
For me Dialer doubles the standby battery use... so battery life is good, but could be much better.
Click to expand...
Click to collapse
So we can not do anything to solve this problem? We have to wait a patch from google? HTC will not do it then maybe never or maybe the 2.3.4
Maybe in the other Roms, cooker have solved this problem..
can we turn off the proximity sensor?
jackalac said:
So we can not do anything to solve this problem? We have to wait a patch from google? HTC will not do it then maybe never or maybe the 2.3.4
Maybe in the other Roms, cooker have solved this problem..
can we turn off the proximity sensor?
Click to expand...
Click to collapse
I think the problem is within the htc dialer app, so htc has to fix it...
Does anyone know if the "turn to mute" option was there in the official froyo roms?
Maybe it's possible to edit the setting manually then and switch off the feature in the settings file by copying the relevant settings string from the old config...
EDIT:
Maybe it's possible to use the old dialer app from froyo in GB...
Somebody has to try ^^
EDIT2:
Turning off the proximity sensor completely would resolve in dropping calls with your ear, because display doesn't turn off when you move your phone to your ear ^^
Update:
Installing HTCDialer.apk from ARHD 3.7 on 5.1.4 does not work...
Same issue for me : the dialer is supposed to be using 10 to 20% of battery, eventhough it only used the CPU for less than one minute...
I'm quite sure this wasn't the case on Froyo...
I am investigating this problem, the point is that I have heard other people with the desire hd on an Italian forum, and apparently almost no one experience this problem.
I'm thinking that maybe the problem is due to some app, widget, or maybe some setting of the carrier.
jackalac said:
I am investigating this problem, the point is that I have heard other people with the desire hd on an Italian forum, and apparently almost no one experience this problem.
I'm thinking that maybe the problem is due to some app, widget, or maybe some setting of the carrier.
Click to expand...
Click to collapse
I made a fullwipe twice and reflashed the rom, I restored nothing, really nothing - and the issue was there.
So it must have something to do with provider or maybe the hardware (some components from another manufacturer than most phones?) I don't now. Maybe just an ultra rare random bug in the original firmware, that happens when your IMEI starts with what not (just joking).
I can also confirm that the bug was not in froyo but in many gingerbread Roms on different phones. So maybe a general bug in gingerbread. If only someone could figure out a way to disable the "turn to mute" feature.
After what I read that should solve our problem...
Sent from my Desire HD using XDA App
scungilli said:
I made a fullwipe twice and reflashed the rom, I restored nothing, really nothing - and the issue was there.
So it must have something to do with provider or maybe the hardware (some components from another manufacturer than most phones?) I don't now. Maybe just an ultra rare random bug in the original firmware, that happens when your IMEI starts with what not (just joking). No clue really :/
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Or maybe just those who are not experiencing the issue is why does not realize it because they use the phone so heavy, and more % are given by other processes, so that they see "dialer" is a 6% 7% max.
jackalac said:
Or maybe just those who are not experiencing the issue is why does not realize it because they use the phone so heavy, and more % are given by other processes, so that they see "dialer" is a 6% 7% max.
Click to expand...
Click to collapse
Yeah could be... We need to turn this feature off, my best guess at the moment...
Sent from my Desire HD using XDA App
Mine is around 11% at the end of the day, but I only made a 1mn call...
And it was always nearly 0% in Froyo...
Is it increasing with phone call lengh?
I'm also wondering if this is just a new way to compute the battery usage : maybe Froyo wasn't able to "see" this usage, so the percentage was allocated to other items, but in this case the battery lengh would be the same. Just the ratio per item would be different. What do you think?
My screen battery usage was around 80% before upgrading, now it is only 58%, Dialer increased, system increased, but I'm under the feeling that my battery still last the same time...
samsenteur said:
Mine is around 11% at the end of the day, but I only made a 1mn call...
And it was always nearly 0% in Froyo...
Is it increasing with phone call lengh?
I'm also wondering if this is just a new way to compute the battery usage : maybe Froyo wasn't able to "see" this usage, so the percentage was allocated to other items, but in this case the battery lengh would be the same. Just the ratio per item would be different. What do you think?
My screen battery usage was around 80% before upgrading, now it is only 58%, Dialer increased, system increased, but I'm under the feeling that my battery still last the same time...
Click to expand...
Click to collapse
Hi,
as far as I noticed it's not increasing with call lenght.
It actually starts to drain battery, when you make a one second call, then it uses the sensors the whole time.
If you reboot your phone and don't start the dialer or take a call, then it will not drain your battery.
That leads to my conclusion, that it is a bug in the dialer, because it should'nt use the sensors when my phone is in standby overnight.
EDIT:
My battery life seems to have decreased comparing to froyo.
scungilli said:
Hi,
as far as I noticed it's not increasing with call lenght.
It actually starts to drain battery, when you make a one second call, then it uses the sensors the whole time.
If you reboot your phone and don't start the dialer or take a call, then it will not drain your battery.
That leads to my conclusion, that it is a bug in the dialer, because it should'nt use the sensors when my phone is in standby overnight.
EDIT:
My battery life seems to have decreased comparing to froyo.
Click to expand...
Click to collapse
I have the voice "dialer" with high % of consume also when removed from charge and I leave the dhd on the desk, inactive in standby, and I do not make any phone call.
That's why I say that I think the problem is not the proximity sensor problem, but maybe other.
However to me the battery lasts much longer but even with this problem, I can do at least 10 hours in more than Froyo with the same usage.
@ samsenteur: I asked on another Italian forum, and many users do not have this problem, perhaps because the % of telephone as it changes when the high screen and system are high, so with a heavy phone during the day.
Edit : scungilli Many thanks for your help and willingness to resolve that you giving ...
Does anyone have this issue at random times when the phone is idle? Sometimes calls and sms are not recieved when the phone is idle. The calls are sent to my google voice and sms spams like crazy when I turn on the screen. This has happened with ICS rom and the Pacman rom from the jellybean.
I've had this issue as well. I think it's a pecular interaction between AT&T towers (I'm on an AT&T MVNO) and Google Voice because it happened for me on official GB too.
I'm on tmobile. Do you think its the google voice software causing this? I didn't have issues when I was on gingerbread.
I also notice how I can tell if the phone went into idle where it rejects all calls and sms. If I turn on the screen, the time will move really quickly. The minute will move really fast till it catches up to the current time.
Today I will be testing the [ROM] [ICS] LiteROM 0.9.0 to see if it also has the same effect. Thegreatergood said he'll implement a fix where the CPU speed is upped a little so the phone doesnt idle too much. I'll let you guys know if the issue is still there.
The ROM [ICS] LiteROM 0.9.0 has the same issue.
So try some JB Roms. I'm running one now - looks promising :good:
kekehi said:
Does anyone have this issue at random times when the phone is idle? Sometimes calls and sms are not recieved when the phone is idle. The calls are sent to my google voice and sms spams like crazy when I turn on the screen. This has happened with ICS rom and the Pacman rom from the jellybean.
Click to expand...
Click to collapse
I have the same 'No response to a call' issue after flashing AT&T UCLJ3 rooted on a Rogers i927R Glide.
Essentially, after the Glide has been idle for a while, not sure how long, at least 30 mins I think,
there is no response from the Glide when calling it, and it goes to voice mail, but not straight away though.
I can hear a ringing tone from the phone I'm calling from, but the Glide just sits there in sleep mode.
Try several calls but the Glide does not wake up.
Haven't tried sending it an SMS when this has happens though.
If I then wake up the Glide manually, and then put it into standby again and call it, it responds as normal and starts ringing.
The thing is, it doesn't happen every time, sometimes the phone could be idle for 2 hours and still respond to a call, other times it doesn't after say 30mins on standby.
Hard to troubleshoot as its so intermittent.
This did not seem to happen on stock Rogers GB.
kekehi said:
Does anyone have this issue at random times when the phone is idle? Sometimes calls and sms are not recieved when the phone is idle. The calls are sent to my google voice and sms spams like crazy when I turn on the screen. This has happened with ICS rom and the Pacman rom from the jellybean.
Click to expand...
Click to collapse
What does everyone have this settings on:
WiFi advanced option "Keep Wi-Fi on during sleep" ?
I always had mine set to: "Always" so that when I'm at home or at work I'm constantly connected to a Wi-Fi access point.
I've changed this to "Only when plugged in" so that it will disconnect from Wi-Fi when going to sleep off charge, which I think will use more data and more battery but will see if this makes a difference receiving calls.
One thing I noticed is that when the phone is on charge, it always responds to a call.
kekehi said:
Does anyone have this issue at random times when the phone is idle? Sometimes calls and sms are not recieved when the phone is idle. The calls are sent to my google voice and sms spams like crazy when I turn on the screen. This has happened with ICS rom and the Pacman rom from the jellybean.
Click to expand...
Click to collapse
I've been running this app for a few days now and have not had any instance of the phone not coming out of sleep to receive a call.
https://play.google.com/store/apps/d...Rhcmtlbi53bCJd
Choose PARTIAL_WAKE_LOCK in the config.
BUMP ! I have this problem also on ORANGE in Romania Europe. I tryed with many custom roms, including RootBox, AOKP, Stock, And LITERom 0.9 baseband UCLJ9 and litekernel 1.2.2. The fix with wakelock seems to work but it's battery hungry (10%) two hours.
I heard that someone from S3 have the same problem and seems related on how the phone switch to different Version of radio (SHPDA UMTS etc) when recieving a call.
Is your phone set to forward to voicemail/GV? See here for how to find the setting.
Lysander said:
Is your phone set to forward to voicemail/GV? See here for how to find the setting.
Click to expand...
Click to collapse
No, its not set to divert to voicemail.
Sent from my GT-I9305 using xda app-developers app
The problem is that the phone will not ring for either incoming or outgoing calls. Someone phoning me gets no rings, it goes immediately to voice mail. When i try to call out the screen looks perfectly normal - all of the correct icons are showing up so it looks like it is ringing, but it is not ringing either at my phone or at the person i am calling.
The problem is cured by restarting the phone. Only after i restart the phone do i get notification about any messages that were left.
This happens only when the battery is at about 40%, but not always - just occasionally and rarely. It happened today for the first time in a few months; it also happened a few times, a few months ago.
I would think that at 40% battery there should be no battery charge related problems? 40% should be plenty to run the phone?
Any ideas? I am going to return it to the store and ask about this, but i would like to have some more info to go on, if any is available.
TIA,
Mick
mdawdy said:
... This happens only when the battery is at about 40%, but not always - just occasionally and rarely. It happened today for the first time in a few months; it also happened a few times, a few months ago ...
Click to expand...
Click to collapse
Update: It may very well be happening more often than i thought. I do not get a lot of calls, certainly not every day, so it could be quite consistent and i may not have noticed. For the next while i'll let it run down every other day and check.
It happened today. I just decided arbitrarily to check. Battery at ~35%. I phoned to check if i had any messages. Everything looked normal as i said in my original post, but it did not ring and did not connect.
Before re-starting i checked to see if Mobile Data was working. It was not. After re-start both Mobile Data and the Phone were working.
I am wondering what is the technical significance to the Phone problem of the Mobile Data also not working? They must be somehow related in the hardware or software structure of the phone.
I got my phone back today. On the report it says ...
Complaint
#1[]C56-no service
phone antenna cutting out intermittently
Symptom code C56
Work performed
[202]-Full sw upgrade & phone reset
;sw re-flashed then rebuild to factory default
Repair code 202
I'll see if it happens again or not over the next few days and report back. To me it sounds like they did nothing to the physical components of the phone, just flashed/installed/configured the various software components.
Mick
Here we are, exactly one week later, and the phone failed in exactly the same way. So the "repair" process they applied did not work. I'll be returning it to the Rogers store today and will report back here with the results.
I may have the solution to this problem of network drops now, finally. I took it back to the Rogers store where i bought it. This time there was a more knowledgeable guy there. He took one look at the screen and said "I know exactly what is the problem". What he noticed was that the LTE notification was not showing. This city is an LTE hot spot. The phone should connect with LTE virtually anywhere, anytime. He said it is not the phone at all, but that there is a "switch" that needs to be reset for my account; something to do with the SIM card. After a couple of phone calls he returned the phone and said that it is fixed.
Time will tell. I'll post again.
Mick
False alarm. The fix made it worse. Now it not only drops network connections, but also drains 50% of the battery over the course of one day with very little use. Used to drain 20%.
Mick
Just reporting that the so-called knowledgeable guy was incorrect. Still dropping the networks. I went back and he was incorrect again as he believed that you had to have Mobile Data enabled to make/receive calls. Oh well, he was doing his best. Got thru today so far with no dropouts, and battery drain returned to normal ~20% loss for the day. Will see what happens overnight and tomorrow.
Getting kind of tired of having an unreliable device. Hope this gets settled soon. I'll be back to him as soon as it drops out again.
Mick
I really do wish some of the more technical guys on this forum would take an interest in this perplexing problem.
Here is a summary of this problem and of the work done by the official repair center, the results, and finally at the end a couple of questions ...
Here is a description of the technical problem with the phone ...
1. The phone will work normally for an indeterminate time period, perhaps a few hours or maybe a week or so. Then it will malfunction as follows -
2. Signal strength is tiny. The phone will not ring for either incoming or outgoing calls. Someone phoning me gets no rings, it goes immediately to voice mail. When i try to call out the screen looks perfectly normal - it visually appears to be calling as the active icon is on the screen and the message says "dialing". There is no dialing sound. It never connects, it eventually gives up.
3. Mobile Data is not working. With Mobile Data enabled there is no icon on the notification bar. Google search and PlayStore do not run.
4. Wi-Fi is working. The icon is on the notification bar when it is enabled. Google Search and PlayStore work with Wi-Fi.
5. The problem is temporarily cured by restarting the phone. Only after i restart the phone do i get notification about any messages that were left. Then eventually the problem re-occurs.
When i sent phone back the first time this is what they did ...
[202]-Full sw upgrade & phone reset
;sw re-flashed then rebuild to factory default
When i sent it back the second time this is what they did ...
[051]-No trouble found
;RF Calibration performed to enhance RX/TX performance and network connectivity. Passed RF compliance test to meet manufacturer soecifications. Adjusted battery level to optimize power usage
When i sent it back the third time they did exactly the same as the second time. The phone is now working better as i will explain, but it has not been long enough to confirm if the real problem is solved.
I have set up the CleanMaster [CM] and BatteryDoctor [BD] Apps. I have turned off any automatic options in both. I make only light use of the phone - a few calls per day, maybe one Google search, nothing else. I run the 1 Tap Boost CM Widget and the Save Power BD Widget after each use of the phone.
I also have installed NoWallpaper [saves a wee bit of battery power], SmoothCalendar [very nice and very useful] and one of the Clock Apps [with a useful 1 x 2 Widget].
I have not yet disabled the 50+ Apps that CleanMaster reports as harmless to disable as my phone is still under warranty and has this issue that the service people have not yet been able to resolve. But i will be doing that and i highly recommend it to others.
I have had the phone back from the 3rd repair for 6 days now. I am leaving it powered on overnight. At the end of the first day battery = 89%, second day 74%, 3rd day 55%, 4th day 46%, 5th day 31%. That is 5 days of light use. Was 23% this morning so i re-charged it to 100%. I'm happy with 5 days of light use.
I do not have written notes on the previous battery performance. But from memory it used more than 20% the first day, at least an additional 30% the second day. There was not enough to trust it for the third day as it lost more overnight. I was running BD and CM, using the CM Widget but not the BD Widget.
I am wondering when the phone will fail again. I'll post again when that happens as i feel certain that it will. But i secretly hope it will not
So, finally, here are my two questions ...
What is the actual, presumably hardware, problem with the phone that they are not able to find?
What did they do to improve the battery performance so dramatically? Did they for example lower the CPU clock rate?
mdawdy said:
I really do wish some of the more technical guys on this forum would take an interest in this perplexing problem.
Here is a summary of this problem and of the work done by the official repair center, the results, and finally at the end a couple of questions ...
Here is a description of the technical problem with the phone ...
1. The phone will work normally for an indeterminate time period, perhaps a few hours or maybe a week or so. Then it will malfunction as follows -
2. Signal strength is tiny. The phone will not ring for either incoming or outgoing calls. Someone phoning me gets no rings, it goes immediately to voice mail. When i try to call out the screen looks perfectly normal - it visually appears to be calling as the active icon is on the screen and the message says "dialing". There is no dialing sound. It never connects, it eventually gives up.
3. Mobile Data is not working. With Mobile Data enabled there is no icon on the notification bar. Google search and PlayStore do not run.
4. Wi-Fi is working. The icon is on the notification bar when it is enabled. Google Search and PlayStore work with Wi-Fi.
5. The problem is temporarily cured by restarting the phone. Only after i restart the phone do i get notification about any messages that were left. Then eventually the problem re-occurs.
When i sent phone back the first time this is what they did ...
[202]-Full sw upgrade & phone reset
;sw re-flashed then rebuild to factory default
When i sent it back the second time this is what they did ...
[051]-No trouble found
;RF Calibration performed to enhance RX/TX performance and network connectivity. Passed RF compliance test to meet manufacturer soecifications. Adjusted battery level to optimize power usage
When i sent it back the third time they did exactly the same as the second time. The phone is now working better as i will explain, but it has not been long enough to confirm if the real problem is solved.
I have set up the CleanMaster [CM] and BatteryDoctor [BD] Apps. I have turned off any automatic options in both. I make only light use of the phone - a few calls per day, maybe one Google search, nothing else. I run the 1 Tap Boost CM Widget and the Save Power BD Widget after each use of the phone.
I also have installed NoWallpaper [saves a wee bit of battery power], SmoothCalendar [very nice and very useful] and one of the Clock Apps [with a useful 1 x 2 Widget].
I have not yet disabled the 50+ Apps that CleanMaster reports as harmless to disable as my phone is still under warranty and has this issue that the service people have not yet been able to resolve. But i will be doing that and i highly recommend it to others.
I have had the phone back from the 3rd repair for 6 days now. I am leaving it powered on overnight. At the end of the first day battery = 89%, second day 74%, 3rd day 55%, 4th day 46%, 5th day 31%. That is 5 days of light use. Was 23% this morning so i re-charged it to 100%. I'm happy with 5 days of light use.
I do not have written notes on the previous battery performance. But from memory it used more than 20% the first day, at least an additional 30% the second day. There was not enough to trust it for the third day as it lost more overnight. I was running BD and CM, using the CM Widget but not the BD Widget.
I am wondering when the phone will fail again. I'll post again when that happens as i feel certain that it will. But i secretly hope it will not
So, finally, here are my two questions ...
What is the actual, presumably hardware, problem with the phone that they are not able to find?
What did they do to improve the battery performance so dramatically? Did they for example lower the CPU clock rate?
Click to expand...
Click to collapse
Based upon your post, should my daughter stay away from this phone. She has a G2 right now.
alhadee12 said:
Based upon your post, should my daughter stay away from this phone. She has a G2 right now.
Click to expand...
Click to collapse
I have posted about this problem on four S4 mini forums and on one S forum. No one has ever seen or heard of this problem. It is clear that my phone is the only one with this problem.
mdawdy said:
I have posted about this problem on four S4 mini forums and on one S forum. No one has ever seen or heard of this problem. It is clear that my phone is the only one with this problem.
Click to expand...
Click to collapse
Thanks fort the response, i told her not to get the phone.
Well, it gets worse. The phone messed up today same as before. A bit more than two weeks after the "repair". I was at home in one of the strongest signal areas. Would not receive or make calls or use mobile data. So back to the Rogers store. By the time i got there it had started working again so i could not demonstrate the problem. Also used a lot of battery power today, about 40% with light usage compared to 15% or less per day for the past two weeks.
What the counter guy at the Rogers store said is that there is nothing wrong with the phone, that all cell phones do this, and that i should adjust my expectations.
Here's another ConnectionChecker app. This one attempts to reconnect ...
https://play.google.com/store/apps/details?id=net.jeremychase.ConnectionChecker
Before I begin, let me state that I have already factory reset countless times and reflashed my firmware at least 3 times in the past week. Neither of these have helped me at all, so PLEASE do not suggest this. I've been trying to solve this problem for a week or two and everyone has suggested this to me and of course I've already done it, so it hasn't helped me at all.
PHONE: E980
FIRMWARE: Stock 4.4.2 E98020g
BASEBAND: APQ8064/MDM9x15M
SYMPTOMS:
-Battery draining ridiculously fast (appx 10%/hr, but before my last reflash, it was draining 50%/2hrs!)
-Phone only lasts about 5hours.
-Android OS is consuming about 80-90% of battery, followed by Screen at around 10%
-Phone is constantly warm
-Phone rarely enters Deep Sleep (it stays awake 95% of the time).
TESTS DONE:
-As I said, I factory reset numerous times with the same exact problem
-I reflashed my firmware 3x, with same problems
-I usually keep auto-sync on, but the issue occurs whether it is on or not.
-There is supposably a Kitkat 4.4.2 (in general) issue where the camera will consume a ton of CPU resources and get stuck that way. I haven't used my camera much, but do use Smart Stay, so I disabled this. No positive result.
-Disabled the Google Now "OK Google" hotword detection. This helped reduce the drain, but didn't solve it. Drain went from like 15%/hr to 10%/hr.
-Took battery out of phone for 10 minutes and placed back in. Seemed to help at first, but after about an hour or so, it returned.
-"Recalibrated" the battery numerous times. This was done by draining the battery until the phone shut itself off. Then I charged the phone to 100% while the phone was still off. Once the phone read as having 100% charge, I let it charge for another 1 hour. Then I unplugged the phone and booted it up. Again, this appeared to help at first, but after a while, the phone began to drain rapidly again.
NARROWING THE ROOT PROBLEM:
-Both WakeLock Detector and BetterBatteryStats show "wlan_wake" and "wlan_wd_wake" as being the largest wakelocks.
-As previously mentioned, "Android OS" is consuming a huge amount of battery
-Problem only seems to happen when wifi is on, whether it is connected to an SSID or not.
OTHER:
I have narrowed the issue down to wifi but I can't seem to figure it out any more than this.
Both of the "wlan_" wakelocks are caused by wifi being on and I need wifi on whenever possible because I can't afford a huge data plan. My current one is 2GB/mo and it is shared between 3 people.
I noticed today that my phone drained 10% within 1 hour after taking the phone off the charger, and I was connected to my home wifi. I then went to work, but still had wifi turned on on my phone. At work, I was only connected to mobile data (but the phone was just sitting in my pocket). The battery drained another 15% within an 1hr 30min, and the phone was warm in my pocket (very uncomfortable!). I then turned wifi off completely, and the battery drain completely disappeared!!! The battery life was amazing in fact!
PICTURES:
I've provided some screenshots with notes. Please take a look at them.
I'm going to manually make the problem happen again and will upload new pictures afterwards. They will be of WLD and BBS. Any current info I have is tainted since I turned wifi off and the problem temporarily turned off too. I want to get only screenshots of what is going on when the problem is happening.
EDIT: BTW, the problem occurs whether my mods are installed or not (the mods used to remove the icons in statusbar, AdAway, etc)..
The issue seems to be pureply related to wifi and nothing else.
IDEAS:
Could adding a wifi supplement scan interval to the build.prop solve this problem?
Is Wifi bugged in this firmware? (This never happened on Jelly Bean!!!!)
Is maybe the "Battery Saving for Wifi" feature bugged?
Would maybe flashing the Jelly bean modem (e98010p) solve this issue (since it didn't happen on Jelly Bean)? If so, does anyone have a flashable version of this? <- I just did some research and it seems that the baseband (AKA modem) is the same in Kitkat as it was in Jelly Bean. Weird....
These pictures were taken shortly after making my first post. I already had wifi turned off, so I turned it back on and after a few minutes, the battery began to plummet. I went from roughly 77% to 66% in just an hour!!!!
Just to make sure that it is clear, I have both BBS and WLD set to start recording data after the phone has been unplugged from the charger. So to restart the data collection, I simply plugged the phone into my charger for a few seconds and then removed it. THEN I turned wifi on. The data seen in the pictures should only have occurred between the time when I unplugged the phone and the time I took the pictures.
EDIT: Also just to make sure it's clear: All the data shown in the System picture is actually since I unplugged the phone this morning. I only posted these pictures to show any changes from the similar ones posted earlier.
PLEASE! Can anyone help me solve this!?
Or is this a major Kitkat bug!? (or ATT bug, or modem bug, etc etc).
After a full week of this problem, I think I just made another breakthrough. Unfortunately, I think it IS one of my Xposed modules, which is weird because I didn't think any of them would have a need to constantly connect to the internet.
All I know is that I just completely uninstalled the Xposed Framework and the phone started to sleep like a baby... with wifi on!
Now I just need to pinpoint the module, which I can do myself.
MODS CAN CLOSE THIS THREAD.
Sorry I created it and (mostly) solved my own problem. This happens to me a lot. I have a problem, can't figure it out, ask for help, then solve it myself. :/
spexwood said:
MODS CAN CLOSE THIS THREAD.
Sorry I created it and (mostly) solved my own problem. This happens to me a lot. I have a problem, can't figure it out, ask for help, then solve it myself. :/
Click to expand...
Click to collapse
Please do not be sorry for this thread :good:
Someone else may have a similar issue so we will just leave it as it is
Glad your issue is fixed
Toledo_JAB said:
Please do not be sorry for this thread :good:
Someone else may have a similar issue so we will just leave it as it is
Glad your issue is fixed
Click to expand...
Click to collapse
In this case, I need to be more specific about my solution then.
The problem seems to be caused by the module, Xposed Torch. It's still usable, but you need to tap the overflow (3-dot) icon and disable ads (it's free to do this). The module requires internet access permissions, which I was not aware of, and it constantly connects to the internet to stream the ads. This in turn causes the wifi to constantly receive data (thus the wlan_wd_wake and wlan_wake). When wifi is on, but not connected to a network, I think it forces wifi to constantly scan in order to find a connection so that it can get that ad data. I'm not sure why it doesn't just use mobile data though... unless it does and it's just more power efficient.
So far, I have disabled the ads via module settings and the phone is now sleeping like it should.
So if anyone else is having wlan_wake wakelocks of any kind, especially followed by wlan_wd_wake or wlan_rx_wake, then this means that something on your phone is constantly accessing the internet via wifi. FIrst turn off auto-sync, and if this doesn't help, then you need to uninstall apps until the problem ceases.
My phone is currently icy cold in my hand and I've never been so happy to feel it like this!
Problem came back today. I've basically uninstalled every app now and the battery is still draining whenever wifi is turned on.
Under Better Battery Stats, there is a process (?) called dhc_dpc that's been running the entire time my phone has had wifi on. There are also the wlan_wakes too. (NOTE: IIm backing up my phone right now, so these names are coming from memory).
According to this thread (different phone and unknown Android version, but similar problem), the wifi driver may be bugged. They recommend doing a reinstall, but I've done this many times now and it doesn't seem to help:
http://forum.xda-developers.com/galaxy-s2/help/dhddpc-t1246190
EDIT: I think I've found the culprit and while it is definitely wifi-related, it's NOT an app. It's the actual Android system constantly pinging the internet. According to my research, it's constantly collecting location data by using either mobile data or wifi and will do this whether you have location services (gps) or Location Reporting enabled. This has been described as a "bug." It was introduced by Google as a cool new feature, but it's implementation was buggy.
I am currently testing a fix to resolve this issue, but want to be certain that it's fully working first.
Just an an FYI, this fix SHOULD help anyone running Android 4.4.2 and experiencing high battery drain caused by Android OS. Even better, the fix does not require root, so anyone can do it!
have you try a full factory reset using lg driver to bring full stock rom back and not just a factory wipe from the phone
3617 said:
have you try a full factory reset using lg driver to bring full stock rom back and not just a factory wipe from the phone
Click to expand...
Click to collapse
Not to be rude, but the first sentence of my first post says I did this several times.
I had those ridiculous battery drains on both stock ROMs with xposed, but never found a direct connection with it.. So first, (if you already haven't), try to disable xposed completely and try again. LG's stock ROM doesn't like that kind of modifications. Also, one of the biggest problems I had with Kit Kat was Location services, so you should check them too.
If that doesn't help, check your apps and download stats, maybe there is something downloading or trying to download stuff.
zamajalo said:
I had those ridiculous battery drains on both stock ROMs with xposed, but never found a direct connection with it.. So first, (if you already haven't), try to disable xposed completely and try again. LG's stock ROM doesn't like that kind of modifications. Also, one of the biggest problems I had with Kit Kat was Location services, so you should check them too.
If that doesn't help, check your apps and download stats, maybe there is something downloading or trying to download stuff.
Click to expand...
Click to collapse
It's definitely Xposed related I think.
I've disabled Xposed during some testing a day or two ago and yeah, battery definitely improved.
The only modules I have installed are:
App Settings
Enable BatteryStats Permission (just to allow me to track this issue. I installed this after problems had already begun)
Greenify (all Xposed settings checked)
YouTube AdAway
I have also been using G2 TweaksBox up until last night. I only used it to declutter my status bar and to enable the advanced reboot menu. (I hate all the icons in the status bar!!!). Last night I disabled G2 TB and battery life improved dramatically!
I can't explain why G2 TB would cause battery drain, but I did notice it doing something odd yesterday. I have the lockscreen off sound enabled in the system settings, so I hear the sound whenever I lock the screen. Well, I turned my phone on yesterday for some reason when in my car. I then turned the screen off, heard the lock sound, and started driving. 15 minutes (NOT seconds!) into my drive, I randomly heard my phone make the locking sound, but the screen was not turned on!! I wonder if G2 TB delays my lock somehow.
I switched to GravityBox[KK] today since so many people claim that it works perfectly on their OGP, and so far, battery drain is MUUUUUCH better than with G2 TB activated, but it still may not be as good as pure stock. I need more time to figure it out though. This morning, my battery dropped 5% in 40 minutes while connected to my home wifi. I then left my house for a few hours, but left wifi turned on on my phone (it's hard for me to remember to switch it off and on all the time!). The battery seemed to be pretty stable after that, but I can't explain the weird 5% drop, but I did receive 2 missed calls and a text during that time too. Should I lose 5% just from getting a text and having my phone ring?
It's now night time and I'm at 75% battery. This past week, I would be at about 10% by now or even DEAD, so I'm happy as heck right now.
I would LOVE to be able to keep using GB, but I now just need to figure out if it too is draining battery, or if everything is stable. I'm going to continue comparing stock VS GB tonight and tomorrow. I'll live with stock if needed, but I'm just very OCD about the statusbar clutter.
In GB, I only disabled some icons, centered the clock, enabled advanced reboot menu, and enabled the lockscreen torch.
Try with GB and post results, it looks like it doesn't drain that much... Unfortunately for me, I had problems with every xposed module ever tried, so I simply gave up and now I'm using another rom. I think that LG's ROM is problematic, especially if you use a lot of SystemUI customisations, like GravityBox does.
Are wakelocks from orginal post still active?
G2 Tweaks aren't even compatible with our phone (as much I understood), never managed to do anything with them. I assume that G2's SystemUI is too different from OGP's, so that may be one of the problem sources.
With my normal usage (1-2 hours of music, 2-3 hours of internet - wifi or mobile, K9 sync, viber, sometimes games, ~60 SMS and few longer calls per day), battery was holding up to 35, sometimes 45 hours. With xposed, barely a day, if I turn mobile data and sync off. I usually have a dilemma about putting it to a charger before sleep, there is alway around 60-50% of battery at the end of the day.
zamajalo said:
Try with GB and post results, it looks like it doesn't drain that much... Unfortunately for me, I had problems with every xposed module ever tried, so I simply gave up and now I'm using another rom. I think that LG's ROM is problematic, especially if you use a lot of SystemUI customisations, like GravityBox does.
Are wakelocks from orginal post still active?
G2 Tweaks aren't even compatible with our phone (as much I understood), never managed to do anything with them. I assume that G2's SystemUI is too different from OGP's, so that may be one of the problem sources.
With my normal usage (1-2 hours of music, 2-3 hours of internet - wifi or mobile, K9 sync, viber, sometimes games, ~60 SMS and few longer calls per day), battery was holding up to 35, sometimes 45 hours. With xposed, barely a day, if I turn mobile data and sync off. I usually have a dilemma about putting it to a charger before sleep, there is alway around 60-50% of battery at the end of the day.
Click to expand...
Click to collapse
OK, so I just got home from work and today I not only had GravityBox disabled, but I also had the ENTIRE Xposed Framework uninstalled.
My battery is now at 30% and I was only gone for 7 hours!!!!!!!!!!!!!!!!!! This is ridiculous!!!!!!!!!
*sigh* <- frustrated with this whole situation
Yes, the wakelocks are still active.
The top two Kernel Wakelocks are "wlan_wd_wake" (46.3%) and "wlan_wake" (46.2%) in that order. The next in line is "PowerManagerService.Wakelocks" (8.0%) and then "msm_hsic_host" (6.1%). This was since my last reboot, which was about 2 hours ago (I had to rebooted after removing an app that I thought was the culprit... apparently it wasn't).
Again, I keep Auto Sync on, but disablign it seems to not help in this matter at all.
I also keep wifi on. When at work, it isn't connected to a network, but I often forget to disable wifi when I leave the house, or I come home and forget to enable it and end up sucking my data plan dry. Nonetheless, I also did this while on Jelly Bean and had no issues whatsoever.
My phone is only staying in deep sleep less than 10% of the time and the time when it is awake, the CPU is running at full 1.7GHz! This is causing the phone to get warm in my pocket. It doesn't hurt, but it's enough to make things uncomfortable.
According to the battery stats (in system settings), Android OS is consuming 83% of the battery.
The biggest network drainers are "Google Play Services" (33.3%), something simply called "0" (14.8%), and a weather app. I had the weather app open manually not too long ago though, so that explains that one, but the other two I can't. I have no clue what "0" is and I have not opened Play at all today.
It's something to do with wifi itself I think, and maybe not a specific app accessing wifi. (?)
I turned wifi completely off about an hour ago and the battery drain has been stable. It's been like this for days too. If I turn off wifi, the drain is "normal." If wifi is on and connected, drain is higher than with wifi off, but barely. If wifi is on and not connected, the battery level plummets like a rock in a pond.
OH! One thing I just thought about and should mention:
Before I discovered that G2 TweaksBox was causing serious drain, I was on another battery-related thread in the OGP forum. Someone told me to delete the "libiq_client.so" file from System/lib. He assured me this would give me excellent battery life (which apparently it did not). So I did. Normally, I just rename system files so I can restore them if needed, but I guess I accidentally deleted this one.
Could this be causing the drain, and if so, can someone upload a copy of libiq_client.so so I can try it on my phone (after setting it's permissions correctly)?
Um, that's not good.
Check wireless settings, and disable "Scanning always available" if enabled.
You don't have a nand backup, do you? I have E988 variant so maybe my file isn't good, I don't know if there are big differences between them. I can upload it if you want.
It is possible that Google Services are messing things up since they are between top processes... have you tried clearing their cache/data? Also, if you have a custom recovery, clear cache/dalvik cache, maybe it helps. Also, if High precision location is enabled, try disabling it if you don't need that service, I had some problems with that in combination with weather widgets.
What partial wakelocks are active?
zamajalo said:
Um, that's not good.
Check wireless settings, and disable "Scanning always available" if enabled.
You don't have a nand backup, do you? I have E988 variant so maybe my file isn't good, I don't know if there are big differences between them. I can upload it if you want.
It is possible that Google Services are messing things up since they are between top processes... have you tried clearing their cache/data? Also, if you have a custom recovery, clear cache/dalvik cache, maybe it helps. Also, if High precision location is enabled, try disabling it if you don't need that service, I had some problems with that in combination with weather widgets.
What partial wakelocks are active?
Click to expand...
Click to collapse
"Scanning always available" has been disabled since day 1
The only nand backup I have is after I already deleted the file :/
I did try clearing Google Service's cahce/data at one point and I think it helped for a few hours. It may have been a placebo effect though. I also di the recovery cache wipe and dalvik wipe with same results.
I don't keep location on at all since I don't use it. It's always off, but at one point, I did enable it to select the battery mode and then turned it off again. I did this mainly so that if and when I do use location, it would always use Battery and not High Precision.
I'm currently backing up my rom, so all partial wakelocks were cleared for now. Sorry.
I'm trying to reflash the stock rom real quick and grab the libiq_client.so file, then restore the backup and insert the file back into system. Unfortunately, I may not be able to tell if it solves the problem until sometime tomorrow.
EDIT: BTW, the only reason why I won't just start all over again on the reflash is because 1) I want to figure out what's causing this problem so it won't happen again, and 2) I don't have the time to spend hours setting my phone up again
EDIT2: Oh and every time I reflashed my ROM, the first things I did was rename/delete that library file and installed G2 Tweaksbox. And every time I had horible battery drain, so i'm really hoping it's due to the lack of this library file.
spexwood said:
"Scanning always available" has been disabled since day 1
I'm trying to reflash the stock rom real quick and grab the libiq_client.so file, then restore the backup and insert the file back into system. Unfortunately, I may not be able to tell if it solves the problem until sometime tomorrow.
EDIT: BTW, the only reason why I won't just start all over again on the reflash is because 1) I want to figure out what's causing this problem so it won't happen again, and 2) I don't have the time to spend hours setting my phone up again
EDIT2: Oh and every time I reflashed my ROM, the first things I did was rename/delete that library file and installed G2 Tweaksbox. And every time I had horible battery drain, so i'm really hoping it's due to the lack of this library file.
Click to expand...
Click to collapse
Try it. I can upload file from my backup if you're willing to experiment with that, to save you from all that flashing.
Also, if you edited your build.prop and changed pm.sleep_mode and ro.ril.disable.power.collapse, undo that. It only disabled deep sleep state for me (had similar problems few days ago when flashed a new rom, mmc1_detect, suspend_backoff and some other weird things, so I even tried that)
Have you tried using another roms?
zamajalo said:
Try it. I can upload file from my backup if you're willing to experiment with that, to save you from all that flashing.
Also, if you edited your build.prop and changed pm.sleep_mode and ro.ril.disable.power.collapse, undo that. It only disabled deep sleep state for me (had similar problems few days ago when flashed a new rom, mmc1_detect, suspend_backoff and some other weird things, so I even tried that)
Have you tried using another roms?
Click to expand...
Click to collapse
It's OK, I'll get the file from the flashing. I know it'll be a pain, but this may be safer just in case there is some sort of difference between the E988 and E980 versions. I doubt there would be, but better safe than sorry I guess.
I did add those settings to my build.prop as a test, but I was smart there and backed up my stock build.prop first and ended up restoring it a few hours later. It was causing my screen to not always turn on when I pressed the power button.
I have not tried any other ROMs. I prefer to stick to stock ROMs (or modified versions of stock... basically anything stock-based and not CyanogenMod or AOSP). I had bad experiences with AOSP-based ROMs on my old phone.
If I tried a stock-based ROM though, it must have everything working though. I mean everything: calls, texts, LTE, bluetooth, speaker phone, etc etc.
EDIT: OH MY GOSH!!!!!!
I just found where the libiq_client file went. I moved it to my internal storage.
Well, good to know I wasn't totally stupid and knew not to completely delete the file! Unfortunately I was still dumb enough to misplace it....
spexwood said:
EDIT: OH MY GOSH!!!!!!
I just found where the libiq_client file went. I moved it to my internal storage.
Well, good to know I wasn't totally stupid and knew not to completely delete the file! Unfortunately I was still dumb enough to misplace it....
Click to expand...
Click to collapse
Better to misplace than to delete it, trust me
Post results.
zamajalo said:
Better to misplace than to delete it, trust me
Post results.
Click to expand...
Click to collapse
I can see that as being true LOL
I'll need some time to test this, but I'll definitely post results ASAP.
spexwood said:
I can see that as being true LOL
I'll need some time to test this, but I'll definitely post results ASAP.
Click to expand...
Click to collapse
Libiq.so enables carrier IQ, its removal should only help battery drain, not cause it.
Just to ask, have you tried adjuating wifi scan interval? You can try as well the xposed module, "wifi deep sleep". Helped minimize my wifi related drain