Related
Yesterday I had this problem with l2_hsic......
Read the rest here
I moved my post because I will need the space for the findings, as I don't see the light at the end of the tunnel.
Here are the findings till now from some users.
I will update this when new ideas/solutions have posted.
what is l2_hsic read the rest here
anirudhgargi said:
HSIC is technology for inter processor comminication. Our phone has two main chipsets AP (here snapdragon, thus the name MSM ) and modem chipset (again by qualcomm). They both are connected via hsic, ...........
anirudhgargi said:
Yes, HSIC is an hardware along with its device driver used for Inter Processor Communication.
Main principle is Android RIL communicates with help of hsic driver to communicate to the CP (modem) chip. And vice-versa. Modem chip also has the same hsic at there side also.
.............
That L2 does not stand for L2 of OSI layer................ There are 4 states (L0(active),L1,L2,L3) state of power saving in USB link also , hsic also uses the same convention.
................
Click to expand...
Click to collapse
Click to expand...
Click to collapse
kernel related? read the rest here
DaKiller147 said:
Hello
I've been encountering L2_hsic and a few other related wakelocks for months (even years), ever since updating my I9100T to ICS (which I did the minute custom ICS roms hit web).......
I searched around and found out the l2_hsic wakelocks are generated by a kernel file "/drivers/misc/modem_if/modem_link_device_hsic.c" which is also responsible for rpm_hsic and tx_hsic wakelocks.
From there I went to CM git and with help from their IRC channel I found the source code for their version of this file:
https://github.com/CyanogenMod/andr...rivers/misc/modem_if/modem_link_device_hsic.c
Click to expand...
Click to collapse
A explanation from anirudhgargi what hsic is! (09/06/12) post 264 :
anirudhgargi said:
HISC is the interface that connected the main Soc processor ( Also called Applciation Processor AP) to the modem ( 3G or 4G if there are two modems separately )
HSIC is used the standard USB core library. And it is stanrd given by usb.org. The HSIC by itself consumes very less power and is one of the very power efficient and space efficient ways of interconnecting chips. Currently common to Qualcomm and Sammy Exynos architectures.
The reason you seeing too many HSIC wake lock and other wake us's is due to the fact that the HSIC interface is waken up by modem (Normal scenarios are also so many) .
Click to expand...
Click to collapse
A find about hsic from becosemsaida (09/06/12) post #107 :
becosemsaida said:
Well i have the wake-lock too and after some digging around i found this:
http://www.synopsys.com/dw/ipdir.php?ds=dwc_usb_lpm_hsic
Click to expand...
Click to collapse
A article about wakelocks from unthinkable apps(18/06/12) post #126 :
rockky said:
Interesting that academia is researching this issue.
www.theregister.co.uk/2012/06/13/fixing_android_no_sleep_bug/
Click to expand...
Click to collapse
A sume of what we know from Shaftenberg(20/06/12) post #136
shaftenberg said:
- equal which modem we are using (GB or ICS)
- all available kernels are affected
- all ICS-ROMs are affected
- disable fast dormancy doesn't help(?)
- Wifi settings aren't responsible
- AC charger is equal (maybe a random thing for this user)
- turning airplane mode or data on/off does not help to kill the service
Click to expand...
Click to collapse
a found on the kernel code from funky81 (25/06/12) post #179
funky81 said:
After search codes in the kernel related with this problem, I've found out the conclusion is that this wild uncontrolled wake lock related with data communication (modem)
Code:
./drivers/misc/modem_if/modem_link_device_hsic.c:wake_lock_init(&pm_data->l2_wake, WAKE_LOCK_SUSPEND, "l2_hsic");
I will try to update the code w/ Samsung Galaxy S3 source code in my kernel...
I will inform you if there's any progress with this
Click to expand...
Click to collapse
Could a app with it's traffic causing it? (26/01/13) post #273
samdal said:
....... I got suspicious. I then forced notifications from Asphalt 7 off in Jelly Beans App Administration. After doing that, I have had no l2_hsic wake lock. ......... Problem solved for me
Click to expand...
Click to collapse
Till now 4.0.4 dbt is not giving high numbers of wakelocks with l2_hsic, 11min in 24 hours cycle
Dates are using DD/MM/UT format
Sent from my GT-N7000 using Tapatalk 2
I have the same kernel wakelock l2_hsic in my phone when it is otherwise idle... no idea what it is though, but in my feeble understanding it means that the phone never gees into deep sleep - and that can't be good can it?
I have the same problem of the l2_hsic wakelock popping up and eating battery. A reset always cures it for some time but it eventually appears again... Very annoying, I hope someone figures out how to get rid of it..
Same here, l2_hsic keeps my phone awake. It's seems to start at some random point and never "switches off" again until I reboot the phone. After a reboot it takes usually takes a couple of hours before this lock reappears.
Never saw this lock on GB, btw.
I'm having the same issue too. Has anyone figured out what it is yet?
I gave up.
Went back to Gingerbread using PC Odin and flashed a pre-rooted LA1.
Installed Mobile Odin Pro and flashed official LPY using Everroot and the 2 injects.
So far it has been running nicely with no wakelocks worth mentioning.
Disclaimer: I am a noob, what i have done might be unsafe and stupid.
same problem here. I also have not found a solution, even though I force-stopped all installed programs it was still there. Bad thing, it reduces my battery life from about 3 days to 14 hrs :/
i have a bunch of random kernel wakelocks that randomly start up and keep going. l2_hsic is one of the worst offenders tho.
frasch42 said:
I gave up.
Went back to Gingerbread using PC Odin and flashed a pre-rooted LA1.
Installed Mobile Odin Pro and flashed official LPY using Everroot and the 2 injects.
So far it has been running nicely with no wakelocks worth mentioning.
Disclaimer: I am a noob, what i have done might be unsafe and stupid.
Click to expand...
Click to collapse
Update: Phone is doing great now, with uptime of about 36h.
L2_HSIC does show up in kernel wakelocks but only for about 10 minutes in this 36h period.
Yesterday it seemed like my note cured itself, the l2_hsic wakelock was up for about 10 minutes and after 19 hrs I had 45% left. Without changing anything today it is worse like before. The Samsung-Support did not know what to do except for a factory reset, but I'd really like to find a better solution.
It seems like a restart cures the wakelock for about 24 hrs. I restarted it 1 hour ago and until now the l2_hsic hasn't come up...
you mention "2 injects" -- what are you referring to there? I did the LPY flash via mobile odin pro, but still have the l2_hsic battery drain issue, so perhaps I can try the '2 injects'?
edit: oh, SU and everroot?
SU and Mobile Odin with Everroot selected as well, of course
this deep sleep issue is the reason i went back to gb. believe me this issue will keep coming. im aware that rebooting by turning it off could fix it, but once u charge ur note while awake it will lock at 200mhz again. so annoying,..
bejoanakmami said:
this deep sleep issue is the reason i went back to gb. believe me this issue will keep coming. im aware that rebooting by turning it off could fix it, but once u charge ur note while awake it will lock at 200mhz again. so annoying,..
Click to expand...
Click to collapse
You're right. I have the same problem. A reboot fixes it but it's always back when you least expect it. You only notice it once the battery is down by an inexplicable 20%
How do we bring this to the notice of someone who knows how to fix it.
On gingerbread I have other wakelocks. "gps" and sometimes "fuel_alerted".
I joined the club and have this strange wakelock too ^^
Only 4,6% though, so it's no battery drain but regardless of that i was curious and wanted it removed :
Hope there is a more permanent solution for this than rebooting
I use the LPY rom together with CF-Kernel LPF. I had the l2_hsic problem too. For me reflashing the kernel with mobile odin resolved the problem.
bejoanakmami said:
this deep sleep issue is the reason i went back to gb. believe me this issue will keep coming. im aware that rebooting by turning it off could fix it, but once u charge ur note while awake it will lock at 200mhz again. so annoying,..
Click to expand...
Click to collapse
I stand corrected, it DID come back, L2_hsic startet some 4h ago and never stopped again.
I've had it, I'll switch to CM9.
When on charger, it's always awake at 200Mhz...
I've read somewhere that if you unplug from charger with the Note in "sleep mode", it will not enter Deep Sleep.
I had the fuel alerted wakelock because the bat was down to 5% and charged it and unplug it while screen off.
Also had the "no Deep Sleep" problem, but after I've started to wake up the phone prior to unplug the cord, it sleeps like a baby (2 days with usage) and always deep sleep when screen is off (checked by spy cpu).
Hope it helps...
Regards
nunosm said:
When on charger, it's always awake at 200Mhz...
I've read somewhere that if you unplug from charger with the Note in "sleep mode", it will not enter Deep Sleep.
I had the fuel alerted wakelock because the bat was down to 5% and charged it and unplug it while screen off.
Also had the "no Deep Sleep" problem, but after I've started to wake up the phone prior to unplug the cord, it sleeps like a baby (2 days with usage) and always deep sleep when screen is off (checked by spy cpu).
Hope it helps...
Regards
Click to expand...
Click to collapse
I've also read this somewhere on xda. And when I had the problem it was exactly like this. The problem was there when I unplugged the phone with the screen off.
Sent from my Galaxy Note running ICS
Unplugging while "Awake" is not the solution.
My phone goes into this permanently awake state randomly after upgrading to ICS. (I am stock, and upgraded via Kies...never messed with this phone before). I too noticed the L2_hsic taking alot of time.
I have made a concious effort to investigate this, and I can confirm that unplugging the phone while "awake" as a solution is false.
Not once since I discovered this problem have I unplugged while sleeping, but alas, I am again in a zero deep sleep situation.
Back to restarting this stupid thing every 2 days after finding my battery draining 15-20% in some short minutes.
I abslutely love this phone!!! Best in the world hands down!!! I love ICS!!! But if this problem doesn't go away, I am giving up! Samsung is both the best...and the worst!
Device: Samsung Galaxy S GT i9000
Symptoms:
When Charging Device is hot to the Touch in the upper half of the screen and on the rear between the camera and the heat vent.
Battery drains at around 15-25% per hour when IDLE. 15% when in deep sleep in airplane mode with ALL APPS KILLED. 25% when I leave ALL network connections open and allow sync.
Phone was new less than 2 months ago. Still under warranty and I will send it back if no ideas come from this but wanted to see if anyone had a solution as I have noticed HUNDREDS of similar posts all vaguely scattered through different threads on different sites around the web and this seems like the definitive place to come to see if anyone can put their finger on it.
When did this occur?:
A short while after (days) of flashing CM9 nightly from the beginning of June (05/06 I think but can't recall exactly).
Tests performed:
Purchased new battery and fully charged - no change.
Flashed stock GB ROMs where the issue had not occured - no change.
Cleared battery stats several times - no change.
Tried different modems/radios including Nexus S radios- no result
Current ROM: CM 7.2
Kernel: Glitch 13.1
Other ROMs/Kernels where the same results were achieved...
CM9 (latest nightlies)
Stock JVU, JVS, JW4 and JW5
Semaphore Kernel, Devils Kernel
I use Voodoo Sound/Colour kernels apart from the testing I did with stock ROMs
Will leave it on over night after clearing stats so you can see for yourselves.
Any questions ask away.
I should add:
Used OS Monitor and one of the more detailed CPU monitors to look at what was going on.
Did not appear at any time to be using what I would consider high CPU utilisation, typically trending between 0 and 30ish. No background apps running, all radios turned off.
The only anomaly that stuck out at me is that system_server was using ~105% of RAM which I would have thought was rather difficult. Made me wonder if there was something loading/unloading itself from RAM.
As I am a heavy music user I have tested the Mediaserver issue where corrupt files are continually scanned by mediaserver process. Removed all media files from both my external and internal storage then formatted both while on a stock ROM (JVU and JW4). There was no change.
EDIT: I should add - The thing that makes this so strange to me is that the battery decreases at a rapid rate when Battery stats regarding usage DO NOT CHANGE. The percentages for the apps that WERE using the battery - i.e. winamp/mediaserver/android system do not change.
The reason I have posted this is that i have seen literally HUNDREDS of people posting this very same issue but never in the same place and never getting an answer.
Also - Thankyou to the kind mod/admin who approved my account so I can edit stuff. It was getting a bit annoying for the first week there.
Re
Hi,
To be honest I never heard/read of the problem you are describing. Most users report high battery drain on a certain ROM/kernel/modem but you say you have tried quite a lot.
If the phone is new, the only thing that comes to mind is that the USB charging socket is faulty. It may not charge properly or even have some bad connectors that are damaging the battery.
In any case, Samsung support is the way to go here.
Hope this helps
OMG, im having the same exact problem... the phone is super hot on the back where the sim card is inserted. I did everything as you, still no change, my battery lasts like 7 hours on deep sleep. Guess our phone is broken. super crap.
Anyone knows how to fix this? Is there anyway that my phone has some files from previous custom roms even though used odin to flash samsung original ones?
Had the same problem when my device was only 6 months old, the battery was becoming faulty, got a new battery and problem solved.
I bought a new battery and i still have the same problem... which battery did u get?
streakpt said:
I bought a new battery and i still have the same problem... which battery did u get?
Click to expand...
Click to collapse
An official samsung battery from Amazon, re flash you device with another rom and wipe battery stats.
Did all that, the problem still continues... mega battery drain and the phone is at 44C degrees... is there any tool i can use to diagnose the problem?
Hi snaleman,
You could try BetterBatteryStats, to help diagnose your issue further, there is a paid version on the market (Google Play Store). There is also a thread on this forum, from the dev....hint
I tried winamp for android, ages ago, but had similar issues. (This player might well be your issue.) So I now use "PowerAmp". Neutron MP is cool too.
Also, do you use lippol94's kernel cleaning script. I use this every kernel/ROM change.
Search here for this:
ultimate_kernel_cleaning_script
Hope this info helps your baby.
Hey
U can try to flash a stock rom from sammmobile.com..
Use it for a few days and check...may help u..
Cheers
Sent from my GT-I9000 using xda app-developers app
Backup your apps with titanium backup or something else.
Make a backup from CWM recovery
Wipe data/cache/dalvik
Restore user apps and not system app
If your problem is not fixed you can restore your CWM backup
Nothing you guys posted worked... battery lasts 11 hours on sleep...
Another problem that im facing is that when im on a phone call, theres is alot of breaks in the other persons voice and sometimes the voice call goes out and i lose all my network signal.
If you are using the Voodoo sound app that may be the cause. I've noticed on my phone that deep sleep no longer works when the voodoo app is installed, most likely the app is holding a partial wake lock and not releasing it.
See if it happens with the app uninstalled or frozen.
Sent from my Nexus 7 using Tapatalk 2
Signal Strength¿
streakpt said:
Another problem that im facing is that when im on a phone call, theres is alot of breaks in the other persons voice and sometimes the voice call goes out and i lose all my network signal.
Click to expand...
Click to collapse
You've just made me think of something else that it may be.
Do you have 4 or 5 bars of signal strength?
I've found when in certain areas (very close to "deadspots" in network reception), that if I use another frequency, [eg. 900 & 2100 (for my network), yours may be different] I can get a better signal, also much better battery life, as the phone is not struggling to reach the network.
If you use your dialer to enter this code
*#*#197328640#*#*
Then
[1] DEBUG SCREEN
THEN
[8] PHONE CONTROL
then
[7] NETWORK CONTROL
then
[2] BAND SELECTION
you will then have a selection of frequencies available. The asterisk * will tell you what one(s) is/are active.
"Google" your network service providers frequency bands. I found mine were on a "Wiki" page.
Hello everyone,
I switched my 16 months old 4x to CyanogenMod 10.1 about 2 months ago, and updated to 10.1.3 about a week after the release. About a week later, I had my first problems with rapid battery draining. I have switched kernels thrice, now running the most recent optimus prime for CM, and have tried fiddling with the values TricksterMOD provides, but I haven't found a way to get any decent battery life out of the device ever since. Last night, the battery drained 50% in about 12 hours of non-use (phone was left with display off in my jacket pocket, and that's not even the worst drain I witnessed in the last two weeks.
I'm running BetterBatteryStats to get a clue about the origin of this drainage, and can see that my device seems to me awake far too long when I'm not using it. At the moment, I'm looking at 44.6% awake, 55.4% Deep Sleep after 2.5 hours of not using the phone once (I was driving home from work half of the time). In "Kernel Wakelocks", I see "wlan_rx_wake" with 21:03 minutes on top, in "Partial wakelocks", the highest value is 20 seconds for "AlarmManager".
I have the usual suspects of communication/networking apps - Facebook (set to 2hr update), Google+, K-9 Mail, WhatsApp, plus AndroidWeather (set to 30min update) - and news apps which are allowed to send push messages. I use wifi, but no bluetooth. I never watch movies, play games or listen to music with my phone.
I have attached a BetterBatteryStats log from the 50% drain in 12 idle hours I mentioned. View attachment BetterBatteryStats-2013-10-17_092335401.txt
Can anybody give me any pointers as to what I going wrong here? I really would like to use my phone without having to plug in the power supply every few hours. If you need any additional information, I'll gladly try to provide it.
Anyway, thanks in advance for any help.
Cheers, Pit.
only 3 letters. O M G ! this battery report just made me like this face here
u cant flash kernels one after another. there are bugs this way. dont all kernels use the same names for files. leftover files will cause problems. do the whole procedure. go to recovery , format data, reboot to recovery and install new rom
kessaras said:
only 3 letters. O M G ! this battery report just made me like this face here
u cant flash kernels one after another. there are bugs this way. dont all kernels use the same names for files. leftover files will cause problems. do the whole procedure. go to recovery , format data, reboot to recovery and install new rom
Click to expand...
Click to collapse
You mean you cant flash Android roms one after another. You can freely flash kernels one after another without wiping anything, Its completely modular.
JoinTheRealms said:
You mean you cant flash Android roms one after another. You can freely flash kernels one after another without wiping anything, Its completely modular.
Click to expand...
Click to collapse
then explain his situation... he said he flashed kernels not roms. why does he have such a bad battery drain during night sleep ? in his report i didnt see he has any so "bad" app.... (just asking out of curiosity, its good to have knowledge generally)
kessaras said:
then explain his situation... he said he flashed kernels not roms. why does he have such a bad battery drain during night sleep ? in his report i didnt see he has any so "bad" app.... (just asking out of curiosity, its good to have knowledge generally)
Click to expand...
Click to collapse
Not sure about the battery drain, it could be caused by a kernel, but its not because hes flashed multiple kernels.
some background:
Android kernels are packaged into boot.img's (these .imgs can be placed in .zips with instructions on how the custom recovery should handle flashing it) Inside a boot.img you will find a zImage (kernel) and a initrd.img (This stands for initial ram disk, its simply a basic file system that the kernel mounts, containing mainly scripts that handle mounting all the necessary partitions etc, then handing control over to Android. )
The boot.img is stored in a emmc partition (/dev/block/mmcblk0p*). When you press the power button, the bootloader is initialized , it then powers on necessary hardware devices, the bootloader than pulls the boot.img from its partition, extracts it and boots the zImage(kernel), which will start initializing less necessary hardware, but mainly mounts the initrd.img and runs the containing instructions.
Bootloader -> Kernel --------------------->
.........................Initrd.img-> ........Android
To move back on track, the zImage and initrd.img only operate within RAM, they only lie in emmc when they are achieved as a boot.img. When you shut your device down, nothing from the kernel persists in the next boot (maybe /proc/last_kmsg ), this is why you dont need to wipe anything on your device between kernel flashes.
JoinTheRealms said:
Not sure about the battery drain, it could be caused by a kernel, but it's not because he's flashed multiple kernels.
Click to expand...
Click to collapse
Thanks for clarifying that; it saves me some trouble.
Does the BatteryStats log give any indication as to why the phone is awake half of the time?
Cheers, Pit.
Dont know, but maybe O Prime is one of these kernel which hides the xmm baseband wakelock.... that would be the missing awake time in your log
OnAir783 said:
Dont know, but maybe O Prime is one of these kernel which hides the xmm baseband wakelock.... that would be the missing awake time in your log
Click to expand...
Click to collapse
Yep optimus prime hides the baseband wakelock
Sent from my LG-P880 using xda app-developers app
OnAir783 said:
Dont know, but maybe O Prime is one of these kernel which hides the xmm baseband wakelock.... that would be the missing awake time in your log
Click to expand...
Click to collapse
Is there a different kernel you would recommend I should try out? I selected the OPrime because it claims to be focussing on stability and battery life instead of raw power.
Furthermore, what would the baseband wakelock tell us in terms of how the fast drain happens?
Cheers, Pit.
Hello all,
just to try it one more time: is there any way I can get decent battery life out of CM10.1.3 on my 4x? This is my profile from today, where I unplugged my phone from the charger around 7:30 a.m. and didn't use my phone thereafter until 5:30 p.m. where the phone was down to 38% already (stats taken around 8:30 p.m.) . The governor is set to conservative and the max frequency to 1.1 GHz, which already makes the UI a bit sluggish. The other settings are unchanged from above.
Secondly, if there really is no chance of improvement under CM10.1.3, which ROM (and kernel) would you suggest for my phone, so that I can at least get a full 24 hours of battery life when I'm not using my phone most of the time?
Thanks in advance, Pit.
Format SD card and wipe everything before flashing new ROM. When I say everything I mean : catche - dalvik - format system - format sd card (sd card is 11gb internal memory of device and external sd card is your inserted sd card). Try latest liquid rom i have good battery life with its stock kernel.
Sent from my microwave.
The baseband wakelock is hidden at his kernel
Gesendet von meinem LG-P880 mit Tapatalk
Try rebooting again after first reboot installing kernel
I'm not sure why but when wiping dalvik and cache the phone has trouble going into sleep
Flash -> wipe cache/dalvik -> Reboot -> Reboot again
Hi everyone,
well, that was a bust. After spending the better part of a day formatting and installing over and over again, I'm now running CarbonRom [20131023] - and having the same battery problems as before.
I tried LiquidSmooth (2.23), but I never got it to work properly; after installing I always got "application someName was teriminated" every few seconds (while the Play Store app was redownloading and reinstalling my apps, but also when I tried to activate SwiftKey, which calls the settings app at one point, which abruptly quits before I can type in anything. I then tried
ParanoidAndroid (3.99, which I didn't like UI-wise)
and SlimBeam (1.9, where the Google apps I downloaded as stated would install fine, but then not appear for some reason - at that point I didn't spend much time trying to fix it, because I was already fed up with it all)
before finally installing CarbomRom, which worked fine. Thus, after downloading my apps, I tried out my battery again. I unplugged the phone, turned the display off, and went shopping for about two hours, touching the phone just once for a few seconds.
The result is again about 30% awake time during these two hours, losing 10% battery in the process (BetterBatteryStat included). That is pretty much unchanged from my experiences with CM10.1.
What am I repeatedly doing wrong that I don't get halfway decent battery runtime out of my 4x (which used to run fine battery-wise for a year when I used the original LG firmware (which had other issues, but could last 36 to 48 hours, depending on usage? As I don't see hordes of 4x owners throwing the device against the wall in frustration, I must do something other don't. But I haven't got the slightest clue what that might be.
I will try PACman (nightly 20131021) next, but if anyone has any pointers, please please help! I'm running out of ideas.
This was my procedure, by the way:
Reboot into CWM
Format system, cache, data, sd card
flashing ROM
Rebooting
after bootup reboot again into CWM
add the Google apps
reboot again
After bootup, reboot again into CWM
just to be sure, reset to factory defaults
reboot, connect with Wifi and Google and start redownloading the other apps
Frustrated greetings, Pit.
Hi again,
PACman is even worse. First off all, the UI is laggy as h*ll; sometimes, it takes more than two seconds for a button touch to be recognized.
That would be somewhat tolerable if the battery life was better. But in 2.5 hours of leaving the device lying idly on my table (display turned off), more than 50% of the time, the phone was active. BetterBatteryStats are again included as an attachment; perhaps someone can find out what the problem is with them. At least, this kernel doesn't hide the xmm_baseband wakelock, though I have no idea what that means whatsoever.
This is getting ridiculous - is there really no way to get the phone to last more than ten hours (doing nothing with it - when I use it even for occasional browsing/e-mail checks, it's way less than that) anymore? Why is no one else having problems on that scale?
Typing this post cost 3% of my battery. And I'm typing it on my computer, not on my phone.
Depressed greetings, Pit.
When i watch your battery stats its your wifi did your try to install then wifi update of demetris? Try then samething with your wifi off i think it would increase slot of your battery
Sent from my LG-P880 using xda app-developers app
moneyvirus said:
When i watch your battery stats its your wifi did your try to install then wifi update of demetris? Try then samething with your wifi off i think it would increase slot of your battery.
Click to expand...
Click to collapse
Thanks, for the info, I will investigate that, though I haven't found this "wifi update of demetris" on first Google try yet, just recommendations what to do with your WLAN router and PC settings.
But I my second-to-last try - where I was out shopping - the wlan_rx wakelock wasn't the problem, rather the xmm_baseband wakelock, where I still am clueless as to what that means at all. I fear that getting rid of the wlan wakelocks wouldn't help my general problems, just the problems I had at home last night in my last try.
Furthermore, if I can use the phone only by carefully switching off and on wlan manually whenever I leave the house, the phone will become pretty much useless to me. Yesterday alone, I forgot switching wifi back on twice. That way, either notifications would go through mobile data connection or not happen at all.
I will reflash my device again this morning - as the PACman UI lags are unbearable for me - and see what I can do about the wlan drain. I cannot reconfigure all the wifi networks I connect to, as some of them aren't mine to configure.
http://forum.xda-developers.com/showthread.php?t=2425455
Look in the seccond post your will zee a long story but at then and of that story you see 3 zip files flash then then nvida 4.3+ broadcom driver update by cwm dunno if it solves your probleme for me its great
Goodluck
Sent from my LG-P880 using xda app-developers app
I don have any problems with liquid rom. Also I flash gaps imidiatly after flashing rom without reboot. Try flashing 4.2.2 android it is better for our prone then 4.3 builds.
Sent from my microwave.
dimi89 said:
I don have any problems with liquid rom. Also I flash gaps imidiatly after flashing rom without reboot. Try flashing 4.2.2 android it is better for our prone then 4.3 builds.
Click to expand...
Click to collapse
I tried that earlier today, and the LiquidSmooth 2.9 (Android 4.2.2) installed fine by your instructions. But it didn't help at all with the battery usage. Phone is running on conservative governor limite to 1 GHz, and I even tried the Broadcom Wifi Update mentioned here earlier (otherwise, I'm on the LS standard kernel).
It all doesn't help, the BetterBatteryStats are still full of wlan wakelocks (even though I switched to static IP as someone mentioned that might help). Result: 10,8% battery drop per hour of leaving the phone with display off on the table.
Before I flash another ROM for the 14th time this weekend, I will collect some results with wifi turned off. Not that that would be a feasible option for me, but I want to get to the bottom of this.
Cheers, Pit.
It seems that the source of my battery problems is coming from this keeping the phone awake. I searched Google and got a total of 8 results - all in German or Russian. I have no idea what app this could come from. I have factory reset, cleared cache, flashed stock firmware, etc. but it will not go away. I have root and uninstalled the T-Mobile apps as well as the Google/Samsung apps that do not get used. I'm at a loss.
My phone has been unplugged for an hour and 5 minutes. lli_pm_wlock has kept it awake for 97% of that time. The phone enters deep sleep, but very rarely. Any advice would be appreciated. If I can't get this figured out I'll go back and exchange the handset. I've tried everything (while keeping it stock) but no luck so far.
I'm also wondering what this wakelock is, but are you sure this is your culprit? It's showing the wake count of this particular wakelock as 0
Best I can tell, it is. It is continually running up and matches the keep awake time on GSam
I have flashed factory firmware and did a factory reset (again) and will be exchanging the device this evening.
I don't know what lli_pm_wlock does, but its in use only 34 min out of 7 hrs, or 8% on mine vs 97% on yours, so something it definitely awry. You are probably better off exchanging the phone. Hopefully the next one will be better.
sublimaze said:
I don't know what lli_pm_wlock does, but its in use only 34 min out of 7 hrs, or 8% on mine vs 97% on yours, so something it definitely awry. You are probably better off exchanging the phone. Hopefully the next one will be better.
Click to expand...
Click to collapse
I hope so. I'm really hoping the T-Mobile location doesn't give me any problems taking it back.
exchanging a phone for a software problem? I don't get the thought on that. I can understand your worry, as my phone has been getting this as well. But, I wouldn't exchange it. I'm just trying to find the culprit.
Globalrebel said:
exchanging a phone for a software problem? I don't get the thought on that. I can understand your worry, as my phone has been getting this as well. But, I wouldn't exchange it. I'm just trying to find the culprit.
Click to expand...
Click to collapse
It may have been hardware causing a software issue - I don't know. All I know is factory resets did nothing, flashing carrier firmware via Odin did nothing, and since exchanging it for a phone built a month later, I'm getting fantastic battery life with no modifications. Literally double the battery life if not more.
Hello, did anyone find what this wakelock is?
fstomaz said:
Hello, did anyone find what this wakelock is?
Click to expand...
Click to collapse
I had no luck - still no idea what it is. I suspect it is related to the power manager.
It would be really nice to figure this one out. I'm also being affected by it, intermittently. Sometimes it's about 30% obtrusive. Others, 100%. And then, usually after a reboot, it goes away - for a while.
It's modem related and it won't go away unless a kernel Dev fixes it
Sent from my SM-G925F
skivnit said:
It's modem related and it won't go away unless a kernel Dev fixes it
Sent from my SM-G925F
Click to expand...
Click to collapse
This is my biggest drainer as well since the newest modem..
Sent from T-Mobile GS6
I searched and haven't found any battery life thread quite like the problem I am having.
I got my Nexus 6 new last September and until recently the battery has always lasted all day for me. I never looked at battery stats or tried to optimize because I never needed to. About a week ago, the battery started running out by 3PM every day. And the phone is always warm to the touch.
The only thing I can think of that changed was I noticed that my Google Contacts were not syncing properly and so I tried a bunch of stuff to get them syncing properly. I went through a checklist of stuff like wiping the contact apps data, deleting the google account and recreating, etc. I might have deleted and then installed the contact app, I'm not sure. I just tried a bunch of stuff until the contacts were syncing correctly. I don't think that is the cause - I mention it because it is the only change I can think of around the time the battery life degraded. I don't allow the play store to auto update apps, so other than something related to google contacts, there were no app version changes. I didn't change anything about how I use the phone.
I am running the ROM from here:
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
which is, I believe, very close to stock. Since the May security patch level came out shortly after I started having battery life problems, I did a clean install of that version. I wiped system, cache, dalvik and data in TWRP before installing the new version. I've run that for a few days now and my battery life is still terrible and the phone is always warm.
Anyone have any ideas what could be causing the problem or how I can diagnose the problem? I've looked at the battery stats, but because I've never looked at them before, I have no idea what they are supposed to look like. The top item in the list is always "Android System" at 18 - 30% of the battery use.
is google play services eating a lot of the battery?
Or did you tried betterbatterystats? Or smth like that? So you can track in detail.
simms22 said:
is google play services eating a lot of the battery?
Click to expand...
Click to collapse
I haven't looked for it before. I don't see "google play services" in the list right now. The is "Google Services" and that has used 5% today.
Get screenshot of both graphs in settings.
1 - settings/battery
2- Tap on the battery graph from (1) to show another graph that has several horizontal bars below it.
2a -may give clues about weak phone signal, excess gps etc
2b - See if there are long periods when screen is off but device is awake...
electricpete1 said:
Get screenshot of both graphs in settings.
1 - settings/battery
2- Tap on the battery graph from (1) to show another graph that has several horizontal bars below it.
2a -may give clues about weak phone signal, excess gps etc
2b - See if there are long periods when screen is off but device is awake...
Click to expand...
Click to collapse
Yes it looks like it is awake most of the time. I've attached a screenshot.
johninor said:
Yes it looks like it is awake most of the time. I've attached a screenshot.
Click to expand...
Click to collapse
your phone is constantly awake, not sleeping. AND you have both Bluetooth and WiFi turned on. you'll get terrible battery. one way to rectify it, kinda, is to turn your screen brightness down a lot. since your phone is constantly awake, that means your CPU is working doing something, is it by your choice?
simms22 said:
your phone is constantly awake, not sleeping. AND you have both Bluetooth and WiFi turned on. you'll get terrible battery. one way to rectify it, kinda, is to turn your screen brightness down a lot. since your phone is constantly awake, that means your CPU is working doing something, is it by your choice?
Click to expand...
Click to collapse
I want bluetooth and wifi always on and I have never had to turn them off to conserve battery before.
It sounds like the problem is the phone is awake all the time. Now how do I find out why?
johninor said:
I want bluetooth and wifi always on and I have never had to turn them off to conserve battery before.
It sounds like the problem is the phone is awake all the time. Now how do I find out why?
Click to expand...
Click to collapse
you can use something like wakelock detector(app) to find if you have any unusual wakelocks.
I agree, it is abnormal for the phone to be awake the whole time from 9am-2pm including long periods when screen was off. The at 2pm (slgithly after you started charging), those wakelocks stopped and remained stopped even after you want back off the charger. It might be a clue... any idea what might have changed just after 2pm (some program that you stopped or killed or setting that you changed)? At any rate I agree something like better battery stats is a valuable tool to help narrow down the cause of wakelocks although it's not always easy.
Another thing I notice is that your phone signal is very weak... red orange and yellow. (mine is mostly green with a little yellow). They put that on the battery screen because it certainly can affect battery life as you phone has to work harder just to find/keep its signal. Weak signal might possibly be related to the wakelocks although I'm not sure. Most likely phone signal is something you can't control or wouldn't change, unless you were in a different location or unless (longshot) it is related to your radio. You might try flashing stock radio if you have a different radio.
simms22 said:
you can use something like wakelock detector(app) to find if you have any unusual wakelocks.
Click to expand...
Click to collapse
electricpete1 said:
I agree, it is abnormal for the phone to be awake the whole time from 9am-2pm including long periods when screen was off. The at 2pm (slgithly after you started charging), those wakelocks stopped and remained stopped even after you want back off the charger. It might be a clue... any idea what might have changed just after 2pm (some program that you stopped or killed or setting that you changed)? At any rate I agree something like better battery stats is a valuable tool to help narrow down the cause of wakelocks although it's not always easy.
Another thing I notice is that your phone signal is very weak... red orange and yellow. (mine is mostly green with a little yellow). They put that on the battery screen because it certainly can affect battery life as you phone has to work harder just to find/keep its signal. Might possibly be related to the wakelocks although I'm not sure. Most likely phone signal is something you can't control or wouldn't change, unless you were in a different location or unless (longshot) it is related to your radio. You might try flashing stock radio if you have a different radio.
Click to expand...
Click to collapse
Thanks for your help. I can't remember if I did anything that could have changed the behavior around 2PM, but now that I know, I can keep an eye out for any similar change.
I have never looked at the battery stats before, so I don't know if that cell signal is how it has always been or something that has changed recently. I suspect it has always been like that because I usually see 0 or 1 bars on the status bar icon when I am at home. I have not changed radios, but I may try that after figuring out this problem.
It looks like I need to look at wavelocks to try to see what is keeping the phone awake. I'll investigate and report back with results and or further questions.
Just remembering you said it started after the May security patch.
I'm assuming you flashed it rather than OTA'd it.
Here is the recent history of factory images for Nexus 6
FEB: MMB29Q
MAR: MMB29V
APR: MMB29X, MOB30D
MAY: MMB30G, MOB30I
The MOB series introduced a new radio (the same new radio in MOB30D and MOB30I). I heard that the reason there are two imagesw in April and May is that not all carriers have tested/approved the new radio yet (those carriers - whoever they are - delivered OTA's to MMB29X and to MMB20G). I haven't heard any reports of problems from the new radio and I know it works fine for me on AT&T. Maybe if you came from something other than MOB30D before, and just changed to MOB30I in May, then it might be worth trying the radio from MMB30G instead (there shouldn't be any problem mixing/matching radios.. radio is independent of the rest of the image).
---------- Post added at 01:07 PM ---------- Previous post was at 12:47 PM ----------
I just read you didn't change radio and you've always had a low signal. So, disregard my post above.
another thing - a standard troubleshooting suggestion (not related to anything in your post), try wiping cache in recovery.
Settings -> Google -> Security -> Turn off everything
What ROM are you currently running? Or kernel?
MellowRoms Nexus 6
Facebook Group Page https://www.facebook.com/groups/212715385759035/
electricpete1 said:
Just remembering you said it started after the May security patch.
I'm assuming you flashed it rather than OTA'd it.
Click to expand...
Click to collapse
It didn't start after the May security patch. It started a bit before and it started out of the blue. I did a clean install of the updated ROM with the may security patch. I was thinking the clean install of the ROM would fix it, but there was no change. One thing I didn't mention is that after installing the ROM, I restored system data and user apps and data with Titanium backup.
Slipknot8Wwe said:
What ROM are you currently running? Or kernel?
MellowRoms Nexus 6
Facebook Group Page https://www.facebook.com/groups/212715385759035/
Click to expand...
Click to collapse
I am running the ROM here:
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
I haven't done anything to change the kernel - does the kernel come with the ROM?
I have installed Wavelock detector free and poked around with it. I've attached a screenshot. It looks like the problem is in something labeled *backup* in the android system. Now that I have this info I am off to google android backup wakelock and see if I can find out more.
The problem went away for a while again and I can't think of anything I did other than install the wavelock detector app. Then the problem returned again.
johninor said:
I am running the ROM here:
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
I haven't done anything to change the kernel - does the kernel come with the ROM?
Click to expand...
Click to collapse
No idea what ROM it is cause it says that it has been deleted by the administrator
MellowRoms Nexus 6
Facebook Group Page https://www.facebook.com/groups/212715385759035/
johninor said:
I have installed Wavelock detector free and poked around with it. I've attached a screenshot. It looks like the problem is in something labeled *backup* in the android system.
The problem went away for a while again and I can't think of anything I did other than install the wavelock detector app. Then the problem returned again.
Click to expand...
Click to collapse
Try this if it helps
Sent from my AO5510 using Tapatalk
Thank you all for your help. I looked at the google backup settings and I had backup turned on, but there was no backup account set. I put in my google account as the backup account. So far the problem is gone. That doesn't prove the missing account was the cause, so if the problem comes back, I think that disabling backup entirely should "fix" it.