Related
Hey all,
Testing on this kernel has concluded for the time being, the batt code has been committed.
Hopefully there'll be a new test soon, I'll update this thread when there is!
Reserved...
So far for me it connects and my phone detects that it is connected via USB so it activates Debugging and Mass Storage. My computer (windows 7) detects the device but cannot install all of the device drivers as follows:
USB Composite Device: Ready to use
USB Mass Storage Device: Ready to use
XDA: No Driver Found
CDC Abstract Control Model (ACM) No Driver Found
CDC ACM Data: No Driver Found
HTC XDA USB Device: Ready to use
CDC ACM Data: No Driver Found
Charging is working and battery percentage seems quite accurate too. I turned on USB tethering but ofcourse because all the drivers are not installed it doesnt work. I will post the log as soon as I figure out how to do it. This looks promising!
I2es
Raph100
well the boot process looks a little different but so far so good. actually charging on this kernal as my battery just died but i'll give it all a good run for the money tonight.
edit: ok seem to have problem with adb.
only 1 driver didn't install: CDC Abstract Control Model (ACM) No Driver Found
the others didn't come up for me so i assume no issues there (xp machine).
however i can see adb connected but no devices pull up. unplugged and replugged usb, restarted device, can see it in my device manager on the laptop and i can see usb debugging started in android but no talkie.
I'll be happy to do realworld testing with this kernel on my Fuze.
Apparently breaks data. 3g icon is there but no data connectivity. Had to use wifi
Sent from my MSM using Tapatalk
hamagc said:
Apparently breaks data. 3g icon is there but no data connectivity. Had to use wifi
Sent from my MSM using Tapatalk
Click to expand...
Click to collapse
This didnt happen for me. 3G works fine, just GPS still doesnt work for me.
Using data kills battery read accuracy, actually. It works for me on my HTC Fuze. I went from 87% down to 59%. After pausing Pandora Radio, the battery level jumped up to 65%, then finally 86%. It's definitely a huge improvement over Viruscrazy's previous revision! Mass Storage fails to work on Linux. The oddities with using data causing random kernel panics seems to have stopped with this build(they started with viruscrazy's previous revision).
So moral of the story? AVOID DATA USE with this particular revision, and you will see an improvement. I'd like to note that the battery level seems to make decreasing increments of 3% every 1-2 minutes when data is in use. I look forward to the next revision. Thanks for releasing this, arghhh . I'll post up my battery log after a whole day of using this phone.
EDIT: I neglected to mention that battery levels seem fairly accurate while charging, and it did properly detect USB versus AC. So that's definitely an improvement as before it always read AC, and finished charging after 2 seconds.
EDIT #2: USB Tethering works as expected! I'm running Ubuntu right now, so I'm not sure if it works on Windows.
gm112 said:
Using data kills battery read accuracy, actually. It works for me on my HTC Fuze. I went from 87% down to 59%. After pausing Pandora Radio, the battery level jumped up to 65%, then finally 86%. It's definitely a huge improvement over Viruscrazy's previous revision! Mass Storage fails to work on Linux. The oddities with using data causing random kernel panics seems to have stopped with this build(they started with viruscrazy's previous revision).
So moral of the story? AVOID DATA USE with this particular revision, and you will see an improvement. I'd like to note that the battery level seems to make decreasing increments of 3% every 1-2 minutes when data is in use. I look forward to the next revision. Thanks for releasing this, arghhh . I'll post up my battery log after a whole day of using this phone.
EDIT: I neglected to mention that battery levels seem fairly accurate while charging, and it did properly detect USB versus AC. So that's definitely an improvement as before it always read AC, and finished charging after 2 seconds.
Click to expand...
Click to collapse
Awesome! Thanks for the report, I'm glad to hear it's working well for you. Not sure if you use wifi, but how does that relate to battery life/status? Hamagc was sayin on IRC that it was pretty good... Almost too good haha.
arrrghhh said:
Awesome! Thanks for the report, I'm glad to hear it's working well for you. Not sure if you use wifi, but how does that relate to battery life/status? Hamagc was sayin on IRC that it was pretty good... Almost too good haha.
Click to expand...
Click to collapse
Oh, I never use wifi because it's always caused random hangs where as using celluar data didn't . I could give it a test if you'd want me to!
gm112 said:
Oh, I never use wifi because it's always caused random hangs where as using celluar data didn't . I could give it a test if you'd want me to!
Click to expand...
Click to collapse
Oh you don't have to, I just wanted to see how it compared to Hamagc's findings... and especially since you noticed such a perceived drain when using 3g, I'm wondering if you notice the same drain with wifi. I would appreciate it
gm112 said:
Using data kills battery read accuracy, actually. It works for me on my HTC Fuze. I went from 87% down to 59%. After pausing Pandora Radio, the battery level jumped up to 65%, then finally 86%. It's definitely a huge improvement over Viruscrazy's previous revision! Mass Storage fails to work on Linux. The oddities with using data causing random kernel panics seems to have stopped with this build(they started with viruscrazy's previous revision).
So moral of the story? AVOID DATA USE with this particular revision, and you will see an improvement. I'd like to note that the battery level seems to make decreasing increments of 3% every 1-2 minutes when data is in use. I look forward to the next revision. Thanks for releasing this, arghhh . I'll post up my battery log after a whole day of using this phone.
EDIT: I neglected to mention that battery levels seem fairly accurate while charging, and it did properly detect USB versus AC. So that's definitely an improvement as before it always read AC, and finished charging after 2 seconds.
EDIT #2: USB Tethering works as expected! I'm running Ubuntu right now, so I'm not sure if it works on Windows.
Click to expand...
Click to collapse
So far I have had no issues with Battery Drain at all...had 3G going with autosync enabled (have FB, Twitter, gmail and Emails syncing every 30mins) and have used market place a bit too (got updated Gmail app ).
I turned WiFi on but there aren't any networks around to test it properly.
I2es
arrrghhh said:
Oh you don't have to, I just wanted to see how it compared to Hamagc's findings... and especially since you noticed such a perceived drain when using 3g, I'm wondering if you notice the same drain with wifi. I would appreciate it
Click to expand...
Click to collapse
Just to note in my "test", I disabled 3G Data, and the battery drain is worse with wifi... it's actually really noticeable. I went from 58%(I let the phone idle a bit to make sure I had an accurate reading) to under 10% in just 10 seconds of launching Pandora Radio and streaming music over my wifi. I stopped the test seeing as how my phone was about to die on me. On my router, WPA/WPA2 TSK encryption is enabled.
Hmmm.. as I'm writing this post, I figured it would be best if I should let my phone die. After about two minutes of letting my phone stream Pandora Radio, the phone started off doing the same thing as it did before, with the battery life dropping down under 15%. Then it stopped dropping and jumped back up to 14%. After about another minute, it went back up to 31%. After that, the battery level will jump down a few percentiles and essentially "repeat the loop"(it will go back down under 15% again).
Heheh. Everything so far works as advertised! I am actually surprised wifi even worked for me this time around. Data just overall seems more stable this build.. was there any work done in regards to that area with this build?
EDIT: THe battery returned to about 41% a minute after I disabled data. I don't think the power drain as indicated by the battery level is accurate . (now it's at 57%, so battery life is most likely longer than what we may think)
Just thought i would also mention, my incoming call mic does not work with the kernel still (not sure if this was meant to be fixed or not).
I2es
I2essurected said:
Just thought i would also mention, my incoming call mic does not work with the kernel still (not sure if this was meant to be fixed or not).
Click to expand...
Click to collapse
I don't think everyone is reporting/having this issue... What's your device? Is it the mic for regular calls & when you put them on speakerphone?
Oy, I'm going to start mixing up RHOD and RAPH again, this is the RAPH section!
I really didn't realize that was an issue on RAPH... anyone else?
arrrghhh said:
I don't think everyone is reporting/having this issue... What's your device? Is it the mic for regular calls & when you put them on speakerphone?
Oy, I'm going to start mixing up RHOD and RAPH again, this is the RAPH section!
I really didn't realize that was an issue on RAPH... anyone else?
Click to expand...
Click to collapse
I have a Raph 100 (Touch Pro T7272). Regular mic for all incoming, and only incoming, calls. Have not tried speaker phone, sorry.
I have also just noticed that the "Battery Info" section in Spare Parts is showing that I have 100% charge still, I have had it unplugged for a good hour or so now.
EDIT: Just did a shut down and it restarted my phone, not a full shut down like it used to.
EDIT 2: After restart it is showing 97% so it is definitely changing....
I2es
Am I to assume this is usable with the 2.2 final (9-17-10) release version for testing?? Of all time's to accidentally leave my Touch Pro at my brothers house (LOST without it too!!!!), i will be getting it back in a day or two tops, and will FOR SURE be helping test this out for further feedback (looks like enough support feedback so far though.) as i would love to help squash the problems with the battery metering, and noticed USB driver's being worked on EVEN with this, double bonus!!!
I usually do thorough testing when I do it. (IE- Testing, going back and forth a few times throughout, letting it drain completely, charging it fully after to better calibrate the meter, sometime's using apps, sometime's normal usage with little using, sometime's in a call, etc.)
Thanks so much in advance for your hard work with trying to get us helping get this working TON'S better on our touch pro's and diamond's and such to get battery as close to perfect as we can get, and even better hoping it get's included in the official android trunk builds, so when we update files, we don't have to worry about breaking compatibility.
i having Touch Pro and have same problem as I2essurected
dont know if my startup.txt is a problem but it looks like below
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 1910
set cmdline "root=/dev/mmcblk0p2 init=/init rootwait rw rootdelay=3 acpuclock.oc_freq_khz=620000 lcd.density=210 msmts_calib=0x7a.0x5e.0x35a.0x37f msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,-2,3 board-htcraphael-navi.wake=0 physkeyboard=raph"
boot
Looking forward to the day finally arrived, thanks!
Mass Storage doesn't work for me. Option appear in the notifications bar, drivers are installed, but when I try enable it, the "wait wheel" is spinning, and spinning, and nothing happens.
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:.
Hello,
I’m looking for help with a rather strange problem. I’m getting a lot of awake time in Android OS. I installed BetterBatteryStats and noticed it was the service BTLowPower that was doing a lot of kernel wakelocks.
I turned bluetooth off a couple of days (and have rebooted in the meantime even) but still the top service in kernel wakelocks is BTLowPower by a very large margin ... how can this be if bluetooth is turned off ?
Stats are in BetterBatteryStats Kernel Wakelocks
Unplugged 12h47min.
BTLowPower 9h33min, 74.7%
I've attached a screenshot
I have a Galaxy Nexus which is running stock Jellybean.
Thanks in advance for any advice !
Same here.
Please help.
My battery drains out because of this in 12h and 1.5h of screentime
Sent from my Galaxy Nexus
bat0nas said:
Same here.
Please help.
My battery drains out because of this in 12h and 1.5h of screentime
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Do you guys have other Bluetooth devices around? I have a Motorola S805 headset as well as a cheapo BT2.0 dongle from DealExtreme.
I typically don't have the headset turned on unless it's connected to the computer, but what I'm finding is that if I just leave my phone with the dongle turned off and the headset turned off then I don't get the BTLowPower battery drain.
If I turn the dongle on, and turn on the headset then I typically get the BTLowPower battery drain in my GNex. I have to reboot the phone for it to go away. I'm not really sure the exact sequence of events to cause the drain to occur, but I feel like it's definitely related to turning on and off my S805 headset or being around the dongle.
There might be other bluetooth devices around (such as phones of a colleague or something), however the bluetooth on my phone is turned OFF and I still keep getting the BTLowPower in kernel wakelocks Today for example it kept my phone awake for over 10 hours
Anyone ? I keep having this problem ...
Same problem here. BTLowPower keeps draining my battery.
I have bluetooth and Jabra headset off...
It usually happends when I unplug my GNex from charging.
Please help....
-----------
sorry for my bad english.
Same issue
I'm running a Toro Gnex with the Vanir AOSP ROM. It's buttery smooth, and I've had no problems at all, other than this specific kernel wakelock. Same scenario as the OP.
If anyone finds out more about it, I would be grateful!
Airplane Mode
NicholasFarseer said:
I'm running a Toro Gnex with the Vanir AOSP ROM. It's buttery smooth, and I've had no problems at all, other than this specific kernel wakelock. Same scenario as the OP.
If anyone finds out more about it, I would be grateful!
Click to expand...
Click to collapse
I've been reading about this all morning. I run Automateit Pro and have it go into airplane mode at night. After losing 25% battery overnight, the investigation began. BTlowpower was keeping the phone awake. It looks like airplane mode can be the culprit, possibly in combination with Wifi set to always on. I am set up to turn Bluetooth off a couple of minutes after going into airplane model tonight, I'll follow up with my findings over the weekend.
bigknowz said:
I've been reading about this all morning. I run Automateit Pro and have it go into airplane mode at night. After losing 25% battery overnight, the investigation began. BTlowpower was keeping the phone awake. It looks like airplane mode can be the culprit, possibly in combination with Wifi set to always on. I am set up to turn Bluetooth off a couple of minutes after going into airplane model tonight, I'll follow up with my findings over the weekend.
Click to expand...
Click to collapse
Great, keep us posted. I also turn airplane mode on at night, but my Bluetooth is always off.
Did anyone try to hard reset their phone ? I called Samsung but I got the standard reply to hard reset my phone, I haven't tried it yet because I doubt it would work and I have a lot of authenticators on it and it's a bit of a hassle. But if any of you guys already tried it I would love to hear if it worked ! Thanks !
BTlowpower solved
Darthy1980 said:
Great, keep us posted. I also turn airplane mode on at night, but my Bluetooth is always off.
Did anyone try to hard reset their phone ? I called Samsung but I got the standard reply to hard reset my phone, I haven't tried it yet because I doubt it would work and I have a lot of authenticators on it and it's a bit of a hassle. But if any of you guys already tried it I would love to hear if it worked ! Thanks !
Click to expand...
Click to collapse
BTlowpower issue solved by turning Bluetooth on and then off again after Airplane mode activated. However, that caused another issue - modem_usb_gpio_wake to crush my battery. Doing more testing today to resolve that one - will post again when that one is solved.
BTlowpower and modem_usb_gpio_wake resolution
bigknowz said:
BTlowpower issue solved by turning Bluetooth on and then off again after Airplane mode activated. However, that caused another issue - modem usb gpio wake to crush my battery. Doing more testing today to resolve that one - will post again when that one is solved.
Click to expand...
Click to collapse
After testing different configurations this weekend, it looks like turning off sync causes these 2 kernel wakelocks. I tested 2 states: Airplane mode + no Wi-fi, and no data (no Wi-fi + no Wireless data, voice signal on). In either instance, the wakelock occurs with sync off. Leaving sync on finally achieved the low overnight battery drain (< 5%) I've been looking for. Regardless, to avoid battery drain after shutting data off:
Turn Bluetooth On and then Off again. If you are using airplane mode (this may be overkill), also turn Wireless Data On and then Off again.
Let me know if this helps.
bigknowz said:
After testing different configurations this weekend, it looks like turning off sync causes these 2 kernel wakelocks. I tested 2 states: Airplane mode + no Wi-fi, and no data (no Wi-fi + no Wireless data, voice signal on). In either instance, the wakelock occurs with sync off. Leaving sync on finally achieved the low overnight battery drain (< 5%) I've been looking for. Regardless, to avoid battery drain after shutting data off:
Turn Bluetooth On and then Off again. If you are using airplane mode (this may be overkill), also turn Wireless Data On and then Off again.
Let me know if this helps.
Click to expand...
Click to collapse
Hi thanks for posting !
Just to make sure I understand, you say the solution is to turn bluetooth on and off again after turning off airplane mode ?
Just for completeness sake, this is my situation: overnight I turn on airplane mode and I sometimes have the wakelock draining my battery during the day (but not always). Draining doesn't occur during the night as while it's on airplane mode I'm also charging it.
I will try every morning when I turn airplane mode off to turn bluetooth on and off again afterwards for a few days and see if that helps. Let me know if I misunderstood.
Thanks,
Jorn
Just found a kind of workaround at another thread, this might be helpful (if it works ).
It doesn't, the drain still occurs >_<
gwindlord said:
Just found a kind of workaround at another thread, this might be helpful (if it works ).
It doesn't, the drain still occurs >_<
Click to expand...
Click to collapse
I actually have a workaround that works for me. During the night I turn off my phone instead of using airplane mode. I no longer have BTLowPower and I also am able to successfully connect every time very quickly with bluetooth to my carkit, which previously was very flaky. It's definitely a standard issue though with the galaxy nexus, I can reproduce it on 2 other galaxy nexi as well.
I just installed BetterBatteryStats two days ago, and I'm seeing the exact same results. I can't help but wonder if the issue is at all related to the kernel I'm using (LeanKernel v4.7), or if perhaps a resolution to the problem could be solved by a modification within the kernel code. The ROM I'm running is BAMF Paradigm v2.4, which is based on AOSP v4.1.2. Like the rest of you, I'd really like to get this fixed.
trestevenson said:
I just installed BetterBatteryStats two days ago, and I'm seeing the exact same results. I can't help but wonder if the issue is at all related to the kernel I'm using (LeanKernel v4.7), or if perhaps a resolution to the problem could be solved by a modification within the kernel code. The ROM I'm running is BAMF Paradigm v2.4, which is based on AOSP v4.1.2. Like the rest of you, I'd really like to get this fixed.
Click to expand...
Click to collapse
Anyone have any updates on this? My GNex just started doing this randomly after being stable for a long time.
the7thson said:
Anyone have any updates on this? My GNex just started doing this randomly after being stable for a long time.
Click to expand...
Click to collapse
After three days or so, the issue seemed to go away on its own. I didn't make any changes to any of the apps I was running, nor did I update the kernel. I really have no clue what took care of it for me, but I haven't seen it since.
trestevenson said:
After three days or so, the issue seemed to go away on its own. I didn't make any changes to any of the apps I was running, nor did I update the kernel. I really have no clue what took care of it for me, but I haven't seen it since.
Click to expand...
Click to collapse
Weird, mine went away as well after toggling BT a couple times. Guess we'll file this one under unsolved mysteries
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
Hello everybody.
I have recently rooted my phone to try and identify the cause to my fast battery drain, which is primarily from the Android OS process.
I can't seem to find it. I see that the process "system" is working a lot and that the Android OS is awake for way to long.
Maybe you guys can point out something I'm missing here.
I would appreciate every help from you !
Thx
raied115 said:
Hello everybody.
I have recently rooted my phone to try and identify the cause to my fast battery drain, which is primarily from the Android OS process.
I can't seem to find it. I see that the process "system" is working a lot and that the Android OS is awake for way to long.
Maybe you guys can point out something I'm missing here.
I would appreciate every help from you !
Thx
Click to expand...
Click to collapse
This really could be anything. I recently had this and experimented for days whenever I took a break. For me, it turns out that it was my work's wifi hotspot making my phone stay awake to stay connected. I turned off wifi and it was fixed. But this isn't a solution. I ended up connecting to my own wireless repeater and problem was gone.
Bottom line is you'll have to figure out what's going on yourself.
htr5 said:
This really could be anything. I recently had this and experimented for days whenever I took a break. For me, it turns out that it was my work's wifi hotspot making my phone stay awake to stay connected. I turned off wifi and it was fixed. But this isn't a solution. I ended up connecting to my own wireless repeater and problem was gone.
Bottom line is you'll have to figure out what's going on yourself.
Click to expand...
Click to collapse
Thank you for your reply.
I couldn't find any cause to the problem, that's why I thought that maybe another pair of eyes (or more ) might help...
raied115 said:
Thank you for your reply.
I couldn't find any cause to the problem, that's why I thought that maybe another pair of eyes (or more ) might help...
Click to expand...
Click to collapse
I'll tell you what I've done for battery life on my phone and maybe on of those will fix your problem.
1. Uninstall stock bloat (only the stuff actually running in the background; no need to remove stock launcher ect.)
2. Disable Wi-Fi scanning when wifi off
3. Use Amplify to limit wakelocks and alarms
4. Freeze the apps you don't regularly use. I have a titanium backup widget on my homescreen that will unfreeze snapchat and launch it. It is the pressed again to freeze it after use.
5. Greenify apps you don't want running in the background for no good reason. If you get the donate version, you can still get GCM notifications so it's win win. For apps that don't have GCM notifications, it will coalesce the notifications so your phone doesn't wake up as often.
6. Make sure you have all logging turned off from the LG hidden menu.
7. If you're on a bad wi-fi network run by work/school, then get the auto disable IPv6 app on the play store.
8. Use the HEBF Optimzer app to prevent Google wakelocks and battery drains.
9. Use PNF Root app on the play store to custom choose how often your phone checks for GCM notifications.
With these changes, I finish the day with around 4 hours of screen on time doing regular things. Don't believe the posts about 7-8 hours SOT because you don't know what they were doing. I once used my phone as a timer while studying and had the screen on for 3 hours and only drained 12% battery.
absolutely the same issue here. No luck with factory reset, not using whatsapp or messenger, not using wifi, not using mobile data, no luck with any kind of debloating, uninstalling, installing greenify, amplify whatever. In the end, the Android OS will come back and drain the battery. I've spent a way too much time on this issue.
kakaovnik said:
absolutely the same issue here. No luck with factory reset, not using whatsapp or messenger, not using wifi, not using mobile data, no luck with any kind of debloating, uninstalling, installing greenify, amplify whatever. In the end, the Android OS will come back and drain the battery. I've spent a way too much time on this issue.
Click to expand...
Click to collapse
Try clearing the Google Play Services data, then removing all Google accounts and then adding them back. This time, make sure not to agree to any data collection.
When you turn GPS on, it should show as GPS only in the location settings. Disagree to any prompts.
If your location defaults to high energy GPS and networks, then try flicking the toggle on and off very quickly after you have cleared the play services data. This is how I got the prompt for data collection to come back. It's annoying and you have to always disagree but it fixed my mysterious battery drains from android os.