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 ...
Appears that the Bluetooth PBAP process is running away when paired with my car's head unit. It was running for the duration of my drive (51 minutes) and drained about 40% of my battery. I've verified this on several drives now. Killing the process (after pairing) corrects the problem, and there doesn't seem to be any side effects.
Anyone else experiencing this (tried multiple ROMs all with same behavior, leading me to believe it is a Samsung Bluetooth stack issue)
I'm a big Bluetooth fanboy! I use the BlueAnt G2 like all the time. I have noticed on all the roms I flashed, I get HORRIBLE battery life, even though everybody boasting how good their battery life is.. I just couldn't understand it, so I aways go back to my backed up stock. I seem to get tremendous battery life on my stock rom (that came with my sgs2 from T-Mobile).. This would explain it!
I even experience this issue on downloadable tweaked stock roms you can find here. Nothing compares to my battery life when I restore my backed up rooted stock rom.
Interesting find!
Sent from my SGH-T989 using xda premium
That's interesting to hear. I've been attempting to troubleshoot the issue further, and I think that Samsungs bluetooth implementation is a bit wonky. I noticed their MAP (Message Access Profile [sms over bt]) is not working right, and that the PBAB responses are off a bit causing the host to attempt OBEX x-fers over and over again. Interesting that your experience with stock roms proves otherwise. Perhaps it's a kernel thing, but I think the BT stack is binary straight from Samsung.
(Take all this with a grain of salt, I'm by far an expert, and am probably talking out my @ss )
I'm going to give stock a try. 51 minute drive, 100% started, 62% ended - awful indeed
SIDE NOTE: I recognize you and your (wifes) picture... what other nicks do you go by? I've seen you somewhere before.
lawalty said:
I'm a big Bluetooth fanboy! I use the BlueAnt G2 like all the time. I have noticed on all the roms I flashed, I get HORRIBLE battery life, even though everybody boasting how good their battery life is.. I just couldn't understand it, so I aways go back to my backed up stock. I seem to get tremendous battery life on my stock rom (that came with my sgs2 from T-Mobile).. This would explain it!
I even experience this issue on downloadable tweaked stock roms you can find here. Nothing compares to my battery life when I restore my backed up rooted stock rom.
Interesting find!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I can confirm that the Samsung BT stack from a stock phone has BT PBAB problems. I've not looked at the battery drain because there's a much more obvious one whenever trying to pair the phone to a BMW bluetooth system. Once connected the car system cannot download the phone's phonebook without first killing the PBAB process first. If you Google for BMW and PBAB you'll be able to read about lots of folks having this problem including this thread, and the only solution is to kill the PBAB process.
Funny enough there isn't a similar issue when connecting to a Toyota bluetooth system. The Toyota BT does support the stereo profile allowing the phone to play music over BT, while the BMW system does not.
Good Luck..
Hey, thanks for the feedback, and other forum link. I'm going to do some extensive testing with mine and try freezing selected BT services to see just what happens. I've done the kill PBAB service and that seems to stop the VERY rapid battery drain.
I can usually tell it's gone awry when the phone starts heating up. (It's in a holster on my belt, and I can feel the heat start, reminding me to go kill the pbab service)
I hadn't though of freezing it (or renaming it) as I figured it was required for the phone book to x-fer. We'll see how it works out.
Can anyone confirm that MAP (Message Access Profile) works anywhere with this phone? (SMS over bluetooth)
More to come.
jasnn said:
I can confirm that the Samsung BT stack from a stock phone has BT PBAB problems. I've not looked at the battery drain because there's a much more obvious one whenever trying to pair the phone to a BMW bluetooth system. Once connected the car system cannot download the phone's phonebook without first killing the PBAB process first. If you Google for BMW and PBAB you'll be able to read about lots of folks having this problem including this thread, and the only solution is to kill the PBAB process.
Funny enough there isn't a similar issue when connecting to a Toyota bluetooth system. The Toyota BT does support the stereo profile allowing the phone to play music over BT, while the BMW system does not.
Good Luck..
Click to expand...
Click to collapse
Hmm..im going to test this out too. I run pandora when im in the car and sync my car to my bluetooth fm receiver..i ll attach screens on how i ll control the proccess using llma.
Sent from my SGH-T989 using xda premium
I've had similar experience in my Acura, albeit I reckon my situation is worse.
If pbap is running, the phone will NOT connect to the car's bluetooth. Moreover if I try to kill pbap after getting in the car, the phone (and the car) go wonky and both bluetooth systems hang until reset. The only way it works if I kill pbap before getting in the car, which sucks as it tends to start itself every time bluetooth is started.
I'm searching for a way to kill it PERMANENTLY. Any suggestions?
You can freeze the PBAB in Titanium (pro) or rename it (if you have root) - also causing a lot of problems with BMW/Nissan/Toyota and others is the BluetoothSharing process.
TCUENGR said:
I've had similar experience in my Acura, albeit I reckon my situation is worse.
If pbap is running, the phone will NOT connect to the car's bluetooth. Moreover if I try to kill pbap after getting in the car, the phone (and the car) go wonky and both bluetooth systems hang until reset. The only way it works if I kill pbap before getting in the car, which sucks as it tends to start itself every time bluetooth is started.
I'm searching for a way to kill it PERMANENTLY. Any suggestions?
Click to expand...
Click to collapse
Samsung S II Batery Drain Related to Bluetooth
After weeks of troubleshooting this issue, I discovered that my high battery drain was caused by uninstalling the Toyota Entune application on my Android. After reinstalling Entune from the Google Play Market my phone my high CPU utilization and corresponding battery drain completely stopped and my phone works as expected. Perhaps corruption from the install/uninstall of phone to car software is causing Bluetooth corruption:good:.
Hi,
I recently got a Galaxy Nexus and loving it and my question is regarding Bluetooth. Could be applied to other Android devices as well.
Is it better to toggle Bluetooth ON and OFF constantly (through apps such as Tasker) or to keep it ON (w/without any paired devices) until its turned off manually or by a constraint? What is a better battery saving option?
Thanks.
bluetooth
I tend to just leave bluetooth on all the time, I don't notice much drain and it makes connecting to my car a lot easier. I'm assuming that it acts like gps (i leave that on all the time too) and it only drains power when it is in use, like when i open google maps. Just because the toggle is on doesn't mean that it's in use and draining power, at least that's what i think...
I wouldn't mind that either, but the icon is there all the time and just makes me feel as if it is draining at least some amount of battery. Or using the Android system even if not in use. So I would rather have it turned off. But you're right, I haven't noticed much of a drain with Bluetooth always on (non-paired most of the time) and toggling it. Actually I think I have seen it eat more battery if I toggle. But I might be wrong!
Anyone use Carat at all? It's a UC Berkeley project/app that runs only when you launch it, looks at your open apps over time and identifies apps you should kill or restart right now, apps that are buggy on your phone (and thus using more than the normally aggregated across all Carat-running phones amount of battery life), apps that are known to use a lot of battery when running.
They also assign you a score out of 100 they call a J-score, which is supposed to be a measure of your average battery life compared to the average life of all other phones or devices running Carat. On official ICS I used to get a J-score of 89 or so, which was not bad at all. I'd hit low battery about 5-6PM every day (no 4G, no Bluetooth, screen auto bright, Wifi off except when in range of a known hotspot, then on as much as possible, never autosleep). Ever since I updated to official JB, I get a J-score of 12.
So! I'm convinced it's software, since my hardware and usage patterns haven't changed. Problem is, of course, there aren't any apps that ever show up in my battery life system meter (see attached).
What do you think?
There were lots of comments (and still are) about how wifi is a battery killer on android wear. I'm not seeing this to be the case at all, when it's working like it's supposed to.
Since 5.1.1 my battery use has been around 3% and hour with all features on. Turning off bluetooth on my phone, with a 2/3 wifi signal on the watch, I'm seeing 2.5 to 3%.
Quick drain happens when walking around the edge of bluetooth range, as the watch switches back and forth between bluetooth and wifi. It seems that as long as it's not finding bluetooth, battery use is normal at worst for me.
I know that the moto 360 will switch to a state of only checking for updates occasionally to save battery, but I don't see this happening. Notifications are coming to the phone, and shortly afterward on the watch. I have not seen a time when a notification was delayed more than a few seconds.
The downside to wifi-only use: some apps that communicate with a phone app don't work. My watchmaker face doesn't update the phone battery level. Google voice commands fail too often, maybe half of the time.
I think google should change the frequency of attempting to reestablish bluetooth connection while on wifi.
Has anyone else tried this? Either turn off your phone's bluetooth, or make sure it is well out of range.
I'll give it a go tomorrow at the office and report back.
Sent from my Xperia Z3
Thanks to a heads up by DarkRazorZ, I learned wifi can be turned on in airplane mode. Will be looking to see if this makes any more difference.
Watch maker has been my biggest battery drain. It also makes the drop down menu laggy and impossible to use.
Yeah, I had that problem with watchmaker. I use intelligent and it seems to work well. Other people report facet works too.
I concur. Wi-Fi uses a lot less battery than Bluetooth, with an acceptable lag - 1-2 seconds on notifications. Bluetooth seems like a big battery drain on the phone and on the watch.
Sent from my Xperia Z3+