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!
Related
Hi all.
I've been experiencing a weird issue.
I've been a RocketROM user for a while now, and never had any battery issues.
Yesterday i decided to try the Abyss kernel. As soon as i flushed it (wiping caches before) i started experiencing high battery drain.
BetterBatteryStats showed WLAN_RX_WAKE as the main culprit while the built in battery stats showed Android OS as the culprit.
So I decided to roll back to the backup i've done prior to installing Abyss (FM Kernel - Rocket V11) but noticed that even after restoring i am experiencing the same issue.
I have since tried clean wipe and at least 3 different restore points (all with FM kernel), but in each case i keep experiencing high battery drain and the phone can't get to deep sleep, all the while the only thing that BBS shows is a kernel wakelock WLAN_RX_WAKE and android OS as the highest "spender".
I suspect that Abyss left some file/residue that keeps causing the issue even after i removed it/clean wiped.
Is that possible ?
I know there's a kernel cleaning script for SGII.. never heard a mention of it for the note.
Would appreciate any pointer/suggestion at this point, as i am quite lost.
mfractal said:
Hi all.
I've been experiencing a weird issue.
I've been a RocketROM user for a while now, and never had any battery issues.
Yesterday i decided to try the Abyss kernel. As soon as i flushed it (wiping caches before) i started experiencing high battery drain.
BetterBatteryStats showed WLAN_RX_WAKE as the main culprit while the built in battery stats showed Android OS as the culprit.
So I decided to roll back to the backup i've done prior to installing Abyss (FM Kernel - Rocket V11) but noticed that even after restoring i am experiencing the same issue.
I have since tried clean wipe and at least 3 different restore points (all with FM kernel), but in each case i keep experiencing high battery drain and the phone can't get to deep sleep, all the while the only thing that BBS shows is a kernel wakelock WLAN_RX_WAKE and android OS as the highest "spender".
I suspect that Abyss left some file/residue that keeps causing the issue even after i removed it/clean wiped.
Is that possible ?
I know there's a kernel cleaning script for SGII.. never heard a mention of it for the note.
Would appreciate any pointer/suggestion at this point, as i am quite lost.
Click to expand...
Click to collapse
+1. Exactly the same issue here.
I'm having the same problem, but on my new Skyrocket SGS2. Leaving wifi on drains my battery due to these wakelocks. Tried new roms and kernels, but it still plagues me.
styx66 said:
I'm having the same problem, but on my new Skyrocket SGS2. Leaving wifi on drains my battery due to these wakelocks. Tried new roms and kernels, but it still plagues me.
Click to expand...
Click to collapse
Is your wifi on a Windows 7 network? I fixed my problem by cleaning up some things that were multi-casting from my Win7 desktops and keeping the phone active continually. Check Entropy512's known battery drainers thread in the i777 forums for some stuff I posted (and a lot of other good ideas to track it down).
Yeah i saw that and turned off the WMP network service and others, but after doing a Shark dump i don't think they were responsible.
I reflashed my phone to bone stock and monitored my network packets. 98.4% of the packets recorded are ARP protocol packets. My FIOS router and my computer asking "Who has 192.168.1.2? Tell 192.168.1.1" etc like that. Pretty much every second. During that time my phone was i think 25% in wakelock from wlan_wake and wlan_rx_wake.
It seems to only be polling and asking to find computers that aren't there any more. I turned my PC off and ran another test, and the router blasted my phone with "Who has 192.168.1.9" which was my PC's address. And blasted it so much that time it kept me 50% wakelocked.
Not sure how to stop these but it seems like these could be the cause... Or are they part of every network like that and my phone should be ignoring them? I'm gonna post my data in that Known battery issues thread later too.
I saw exactly the same behavior on my wndr3700 router. It keeps sending Arp requests every second or so. I too wasn't able to find out whether this is normal or not. seeing it happen on a completely different router suggests its normal but a confirmation from someone who knows would help.
Sent from my GT-N7000 using Tapatalk
mfractal said:
I saw exactly the same behavior on my wndr3700 router. It keeps sending Arp requests every second or so. I too wasn't able to find out whether this is normal or not. seeing it happen on a completely different router suggests its normal but a confirmation from someone who knows would help.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Best solution imo is to flash a stock rom with Odin. Let it boot, and wipe the phone with *2767*3855# to original factory settings.
Than you`ll start clean again.
gee2012 said:
Best solution imo is to flash a stock rom with Odin. Let it boot, and wipe the phone with *2767*3855# to original factory settings.
Than you`ll start clean again.
Click to expand...
Click to collapse
Did you even read his post? The issue is his router, NOT the phone.
---------- Post added at 07:24 AM ---------- Previous post was at 07:20 AM ----------
gee2012 said:
Best solution imo is to flash a stock rom with Odin. Let it boot, and wipe the phone with *2767*3855# to original factory settings.
Than you`ll start clean again.
Click to expand...
Click to collapse
styx66 said:
Yeah i saw that and turned off the WMP network service and others, but after doing a Shark dump i don't think they were responsible.
I reflashed my phone to bone stock and monitored my network packets. 98.4% of the packets recorded are ARP protocol packets. My FIOS router and my computer asking "Who has 192.168.1.2? Tell 192.168.1.1" etc like that. Pretty much every second. During that time my phone was i think 25% in wakelock from wlan_wake and wlan_rx_wake.
It seems to only be polling and asking to find computers that aren't there any more. I turned my PC off and ran another test, and the router blasted my phone with "Who has 192.168.1.9" which was my PC's address. And blasted it so much that time it kept me 50% wakelocked.
Not sure how to stop these but it seems like these could be the cause... Or are they part of every network like that and my phone should be ignoring them? I'm gonna post my data in that Known battery issues thread later too.
Click to expand...
Click to collapse
I'm still getting the ARP requests, but they aren't stopping the phone from sleeping and my battery life is excellent now. Cutting down the ones with "destination port: wcbackup" is what "fixed" mine. Try following this: http://www.corrupteddatarecovery.com/Port/8912udp-Port-Type-wcbackup-wcbackup.asp
and see if you can shut off the processes that are the worst offenders.
Thanks a lot for the confirmation. Could you say which rom and kernel are you using?
Sent from my GT-N7000 using Tapatalk
mfractal said:
Thanks a lot for the confirmation. Could you say which rom and kernel are you using?
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Sorry, missed the question - I'm using UnNamed 2.2.1, with Entropy512's 1/30/2012 kernel. At the time you asked, I was running the same ROM, but the 1/2 kernel. And the 1/30 kernel has cut my battery drain in half! Hope that helps.
Phone does not go into deep sleep and for a few hours drains the battery ....
How can I solve this .. It is a German rom for Galaxy note,oficial1...
In attachment pitcure you can see all....Pls helppp...
voja89 said:
Phone does not go into deep sleep and for a few hours drains the battery ....
How can I solve this .. It is a German rom for Galaxy note,oficial1...
In attachment pitcure you can see all....Pls helppp...
Click to expand...
Click to collapse
I had this issue too.
If (and only if) you're rooted and know how to use it... try setCPU. Recommended settings and ondemand + set on boot.. gonna try this for a few days and post the results
Sent from my GT-N7000 using xda premium
I had that problem initially and I *think* it was related to having WiFi enabled even while the phone was supposed to be asleep. Have a look at this thread for a few ideas which may (or may not) help....
http://forum.xda-developers.com/showthread.php?t=1649041
Sorr to double my post, but...
So, I found the problem.
This is kernel wakelock, wlan_rx_wake.
Many people also suffered from this problem on Nexus.
The issue directly related to Dynamic IP/DHCP on your network. Due to kernel fault, wi-fi module can'to go into deep sleep, and therefore drains the battery. Not much, but about 2-3% per hour.
Goddamn Samsung devs.
So
This whorked for mee....
Try the instructions below, fixed my deep sleep problem(thanks to Mister Jozo)
0.go to settings > sound and turn off touch sounds and screen lock sounds
These steps stop the kernel wakelock 100% problem:
1.turn on aeroplane mode
2.turn off device
3.take out battery for 10 seconds
4.turn on device
5.wait for everything to load
6.turn off aeroplane mode
voja89 said:
This whorked for mee....
Try the instructions below, fixed my deep sleep problem(thanks to Mister Jozo)
0.go to settings > sound and turn off touch sounds and screen lock sounds
These steps stop the kernel wakelock 100% problem:
1.turn on aeroplane mode
2.turn off device
3.take out battery for 10 seconds
4.turn on device
5.wait for everything to load
6.turn off aeroplane mode
Click to expand...
Click to collapse
Not for me. Those are steps for fixing audio_output wakelock, not wi-fi.
ahalford said:
Not for me. Those are steps for fixing audio_output wakelock, not wi-fi.
Click to expand...
Click to collapse
Hmmm i dont have any kernel wakelock, deep sleep works how it should. Maybe you have installed any app which gives that wakelock
EdgaBimbam said:
Hmmm i dont have any kernel wakelock, deep sleep works how it should. Maybe you have installed any app which gives that wakelock
Click to expand...
Click to collapse
I don't know...very same set of apps, as it was on lp5 and lp6 repacks, and there the battery life was significantly better, than now. There is deep sleep, just in "kernel-wakelock" I'm seeing this wi-fi issue. And it not happens on mobile network.
This whorked for mee....
Try the instructions below, fixed my deep sleep problem(thanks to Mister Jozo)
0.go to settings > sound and turn off touch sounds and screen lock sounds
These steps stop the kernel wakelock 100% problem:
1.turn on aeroplane mode
2.turn off device
3.take out battery for 10 seconds
4.turn on device
5.wait for everything to load
6.turn off aeroplane mode
I dont know what was the problem from start but this worked for mee....Picture is the evidence....
voja89 said:
This whorked for mee....
Try the instructions below, fixed my deep sleep problem(thanks to Mister Jozo)
0.go to settings > sound and turn off touch sounds and screen lock sounds
These steps stop the kernel wakelock 100% problem:
1.turn on aeroplane mode
2.turn off device
3.take out battery for 10 seconds
4.turn on device
5.wait for everything to load
6.turn off aeroplane mode
I dont know what was the problem from start but this worked for mee....Picture is the evidence....
Click to expand...
Click to collapse
that worked perfectly for me!!! Many thanks!!!
Left my WiFi and Latitude/Maps running and apps and FB updating over night..
100% charge.
7 hours 38Min 85% remaining
Running odex stock rooted German LPY ROM. Flashed from mobile Odin Pro with injected SU and everrott and ALL wipes checked.
By some standards this may be poor. I am extremely happy with these results given I run everything all the time. I usually am charging every night. I decided to leave it off charge last night to see if I had excessive drain.
eybee1970 said:
that worked perfectly for me!!! Many thanks!!!
Click to expand...
Click to collapse
Just to understand - were you on cf-root kernel or stock kernel, rooted in another way?
ahalford said:
Just to understand - were you on cf-root kernel or stock kernel, rooted in another way?
Click to expand...
Click to collapse
I was and I am on cf-root.
Ok...I solved this problem another way
ahalford said:
Ok...I solved this problem another way
Click to expand...
Click to collapse
Care to share?
Already did it HERE, post #73
the solution posted by OP worked for me thanks!!
I seem to have a problem with the calendar storage... whatever that means. Restarting, taking battery out etc. didn't help. And the problem is that the phone is getting hot too. Any suggestions please?
Sent from my GT-N7000 using XDA
I seem to have a problem with the alarm amanger not letting mine go into deep sleep.
3545 wakelocks over a 2 hour period!!!
I have 2 daily alarms set in the stock clock.
Surely this shouldn't be preventing the phone from sleeping?
Or is it related to some other app?
Well one of the things i've noticed is that while charging my phone never goes to deep sleep, it remains on 200mHz. If i take it off the charger it will go to deep sleep.
I've read about a similar problem with the original samsung car holder /charger. As it seems while charging in landscape mode and receiving a call gives a problem. Without the charger all seems to be fine.
In my opinion i think it's rom related (wow, did figure it out myself) but i think it's also related with the usb port. Try it and you will see....
Hope this helps someone.
becosemsaida
I'm using Kingdroid v7.1 with notecore v10 kernel. But even before these, the phone never goes deep sleep after unplug the charge until i reboot. I read some blogs lots of people have this issue on ICS. Have you face it and did you solve it?
Thanks.
hotboy_ist said:
I'm using Kingdroid v7.1 with notecore v10 kernel. But even before these, the phone never goes deep sleep after unplug the charge until i reboot. I read some blogs lots of people have this issue on ICS. Have you face it and did you solve it?
Thanks.
Click to expand...
Click to collapse
Try not to install app that has something to do with your cpu or access to, for example temperature and consumption. This i notice when i install those app then suddenly i had wakelock problem. This is only my own observation.
Others said after charging unlock your phone first before pulling the cord.
I've also heard this,
Unplugging while locked leads to issues for some....
Personally I'd throw BetterBattStats & CPU Spy on and see what information you can get from here...
jonpaslim said:
Others said after charging unlock your phone first before pulling the cord.
Click to expand...
Click to collapse
this is a complete bull**** myth that belongs to fairy tales!
what does locking the phone (pulling the charger) and the battery drain have to do in all of these??
I never read such a silly and crappy advice than this... this gotta top the lists of silly jokes on my end
anyway OP.
Don't rely on mumbo jumbo advices. These advices are worthless and totally just a piece of crap
I would go with the advice of just totally wiping your phone first.. don't install 3rd party apps(aside from cpu spy) on your phone, disable all background syncs, datas, 3G wifi, and BT.
With CPU SPY (the one app that you only need to be installed on your phone)... check back if your still getting deep sleep ish...
in that way.. you can really try to resolve your issue thru the process of elimination thru careful selection(of apps your going to install one by one later on)
Hey I have a problem with battery drain..AGAIN! My battery drained over night abnormally, over 20%. In BBS paerial wakelock was audioout_2. I resolved that with installing an old version of viber. After that,the phone was working almost 2 days without problem. Then anothe problem occurred.. Yesterday,I charged my phone to max, killed wifi,cleared RAm,did the fast reboot.. Over the night it used 34% of battery!!! In BBS, partial wakelock it said baseband_xmm power! How can I fix that?
I have to say, this JB sucks! This never happened on ICS...
It seems to be tegra3 issue that randomly pops up. I've found no solution yet
i got this wakelock too, factory reset did not solve it
When I woke up and so the wakelock, I just rebooted the phone and the wakelock was gone,and so far it is not a problem anymore... But I still dont know what caused that...
I keep having this problem as well. Rebooting temporarily fixes it but it comes back after a while. A solution would be much appreciated.
umut.t said:
I keep having this problem as well. Rebooting temporarily fixes it but it comes back after a while. A solution would be much appreciated.
Click to expand...
Click to collapse
Same for me guys, I would like to add that I'm using the Zaiben ROM; are you using that too?
The reboot didn't fix the problem on my phone
im using portuguese 20A, and i can´t get rid of this damn wakelock, sometimes it goes away with a reboot, but eventually comes back...
I'm on Asia 20A with the same problem. 26% lost overnight. Not good at all. In ICS it was like 6% overnight, lol.
Dunno but in official bootloader unlock thread it needs you to be connected to real network for some time then I would say there's a way to monitor that time and maybe this is it - maybe it disappears after bootloader unlock
my bootloader is unlocked
My baseband_xmm_power wakelock is showed in kernel wakelocks but in partial wakelocks there isnt any wakelock worth mentioning.. But over the day,when i turn wifi on and do a reboot it doesnt show at all..
Thats my biggest problem,it shows up randomly...
I have the same issue, 6.6%/h battery drain last night. And the big problem is baseband_xmm_power. I check my wife phone (not tegra device) and "baseband.." not even in the kernel wakelock. I read somewhere (forgot the site) it's tegra kernel problem, and after they install custom kernel the problem with baseband is gone.
I'm not developer but I wish lg will release kernel source now, so somebody can optimize the kernel asap
Sent from my Transformer using Tapatalk 2
future81 said:
Dunno but in official bootloader unlock thread it needs you to be connected to real network for some time then I would say there's a way to monitor that time and maybe this is it - maybe it disappears after bootloader unlock
Click to expand...
Click to collapse
Mine's unlocked too.
me too, battery drain 20% more overnight, cause by baseband_xmm_power kernal wakelock, 6h 20m.
is that JellyBean 4.1.2 got bug?
ming0000 said:
me too, battery drain 20% more overnight, cause by baseband_xmm_power kernal wakelock, 6h 20m.
is that JellyBean 4.1.2 got bug?
Click to expand...
Click to collapse
It seems to affect a lot of the Tegra 3 devices, however, I owned two Optimus G's (they're not Tegra 3) and they both had issues with battery drain too and it also had to do with the baseband. I surely hope my next LG, which may be the Optimus G Pro, doesn't have these issues.
archie87 said:
It seems to affect a lot of the Tegra 3 devices, however, I owned two Optimus G's (they're not Tegra 3) and they both had issues with battery drain too and it also had to do with the baseband. I surely hope my next LG, which may be the Optimus G Pro, doesn't have these issues.
Click to expand...
Click to collapse
erm, really problem for this issue, hope that can settle.
seen i looking forword bout G2, 5" inch.
Hey guys
I already posted my problem in the thread related to LineageOS, but since the issue couldn't be solved I want to try it this way.
So what is my problem?
While using my phone it gets very hot. According to Powerful Monitor the CPU gets up to 65 °C and battery up to 35 °C, while under load. Besides this my battery goes down rapidly. So watching 10 minutes of YouTube sucks up 8-9 % battery. Just a plain normal video.
What is my setup?
I9295, running LineageOS 14.1-2017-06-06-UNOFFICIAL-jactivelte, OpenGApps 06-07-17 nano, only apps installed manually are GeekBench, Powerful Monitor and YouTube. Baseband is I9295XXUDOB4 (German unbranded DBT). I bought a new original Samsung battery and currently using it. So it's basically stock LineageOS.
What have I already tried?
- flashed stock firmware (all available for Germany that are unbranded). With and without erasing NAND, with different Odin versions. Last time I flashed I used Odin 3.07
- different batteries: the old ones the phone came with (bought it used), the new one I bought separately, a new one from PowerCell with higher capacity (2900 mAh)
- different phones. I have a second I9295 from a friend, that worked definitely without any issues. Same problem.
- different custom ROMs: now I'm running LineageOS, but I also tried CM13 (20161228), CM12.1, MIUI and Super WizCyan (everything from xda)
Is it possible break something ciritcal when disassembling the phone? Both phones came with broken covers for the USB port, so I opened it, but only removed the screws and the mid-frame (?) and replaced the cover. Nothing was damaged, at least I was very carefully and didn't see anything that looked suspicious.
Another very strange thing I noticed:
If I use the phone a lot (lets say 30 minutes, so almost 25 % battery!) and after that the phone is not in use for an hour or so, the battery goes up for up to 7-8 %. How it that possible?
I really have no idea what else to do.
Any help is appreciated.
dotnano said:
Hey guys
While using my phone it gets very hot.
I bought a new original Samsung battery and currently using it. So it's basically stock LineageOS.
Any help is appreciated.
Click to expand...
Click to collapse
Hey there. Well, there are tons of possible reasons why your phone acts like that. My modest opinion is that you have some sort of wakelock active in background. Install both Wakelock Detector and Gsam Battery Monitor, grant all the permissions and let it obtain data for some minutes. Than look at the results, and check if there's any Wakelock active. If instead Gsam shows an excessive consume by the kernel, try in terminal the following commands:
Code:
su
setenforce 1
setenforce 0
Then see if there's still the drain (you have to wait some minutes).
If it still doesn't work, I'd advice you to update to the latest stock firmware (doesn't matter which Country, just select a non-branded one), reinstall LOS again and verify if with nothing installed you still get the battery drain.
Anyway, IMHO it's not an hardware related problem, even messing up with the components this shouldn't happen. The only hardware fault could be the battery short-life, but 1st you said you just replaced it, 2nd it would not justify the thermal overload. Let us know
Thank you very much for your answer. I'm quite short on time next days but maybe I have a few minutes on sunday.
On the matter latest stock firmware: already tried that on monday, still too much battery drain, but I didn't install LOS till now. Maybe sunday.
But still thank you
Finally I found some time to try your suggestions
I skipped the part of trying it on the old setup, so I flashed everything new with latest stock(UDOB4-DBT, not the last one but still Android 5.0.1), then TWRP 3.1.0, after that LOS 14.1-20170606 and OpenGApps 7.1 nano from 17-06-06. Only apps I installed beside that are GSam Battery and Wakelock Detector. Root activated and granted where asked and needed.
Here I uploaded the pictures I took from GSam Battery.
So what seems strange to me:
- why is Phone Radio used at all? I don't have a SIM card inserted...?! It's on a very high level, even if the screen isn't on.
- The battery gets hot quite fast. If it's not in use, everything is fine. But as soon as I use the phone it gets hot.
- As you said: kernel usage seems quite high, tried to install "Terminal Emulator" and executed the commands - no difference.
According wakelock: where do I check that?
dotnano said:
- Why is Phone Radio used at all? I don't have a SIM card inserted...?! It's on a very high level, even if the screen isn't on.
- The battery gets hot quite fast. If it's not in use, everything is fine. But as soon as I use the phone it gets hot.
- As you said: kernel usage seems quite high, tried to install "Terminal Emulator" and executed the commands - no difference.
According wakelock: where do I check that?
Click to expand...
Click to collapse
Sorry for the delay, but if you do not quote/reply me I cannot see the message cause I'm not extremely active on XDA. Anyway...
- Phone Radio is used even without SIM, at least in TouchWiz, dunno in LOS, but it looks like so. The only way to disable it is Airplane Mode.
- It gets hot due to kernel usage, what I still do not understand is why it does so.
- Those commands where the only commands I think could be useful in this case (they set SELinux Permissive/Enforcing)
But if you say you get the Drain on TouchWiz too, the problem is serious and there's a (little?) chanche it would be HW related.
IvanCristina said:
Sorry for the delay, but if you do not quote/reply me I cannot see the message cause I'm not extremely active on XDA. Anyway...
- Phone Radio is used even without SIM, at least in TouchWiz, dunno in LOS, but it looks like so. The only way to disable it is Airplane Mode.
- It gets hot due to kernel usage, what I still do not understand is why it does so.
- Those commands where the only commands I think could be useful in this case (they set SELinux Permissive/Enforcing)
But if you say you get the Drain on TouchWiz too, the problem is serious and there's a (little?) chanche it would be HW related.
Click to expand...
Click to collapse
No need to apologise, you're doing this in your free time...
Besides that, I wasn't at home all week, so I couldn't try anything even if you had answered.
So, how do I get the kernel to calm down and stop draining my battery? I mean, I didn't install anything besides clean LOS and GApps. So what could lead to so much kernel usage? Are there any further information that could help you?
dotnano said:
Thank you very much for your answer. On the matter latest stock firmware: already tried that on monday, still too much battery drain, but I didn't install LOS till now.
Click to expand...
Click to collapse
I didn't read this post before, the points are two:
- No need to write Thanks, there's a button for it. It's free and very grateful
- If it drains even on stock it's a serious problem.
dotnano said:
So, how do I get the kernel to calm down and stop draining my battery? I mean, I didn't install anything besides clean LOS and GApps. So what could lead to so much kernel usage? Are there any further information that could help you?
Click to expand...
Click to collapse
The situation is very weird. Let's analyze.
1) TW/LOS doesn't matter. Battery drain in both
2) No apps installed which could cause wakelocks
3) Battery SHOULDN'T be the problem
4) The drain is recognised as kernel "usage", though it couldn't be real 'cause of point 1
5) Neither Permissive nor Enforcing SELinux mods helped
At this point it doesn't look so much a SW problem, but more an HW one. About:
dotnano said:
If I use the phone a lot (lets say 30 minutes, so almost 25 % battery!) and after that the phone is not in use for an hour or so, the battery goes up for up to 7-8 %. How it that possible?
Click to expand...
Click to collapse
Well, sometimes the discharge happens so fast the battery doesn't calculate the remaining capacity so well, and after some minutes the real charged cells are more than the "estimated" ones. It would explain the "goes up" of the percentage, but still not the drain.
It's very strange and very rare, but there's an infinitesimal possibility that the thermal paste went to the hell. And in this case there's not that much to do.
That's pretty pessimist though. I'd advice you to format everything, reinstall the latest stock TW and stick with it, and if it still doesn't work, try with some apps like Greenify and ForceDoze (this one works just with 6.0+) in order to at least TRY to reduce the drain.
I'm sorry I cannot help you more, if anyone has some suggestion, please let us know.
IvanCristina said:
I didn't read this post before, the points are two:
- No need to write Thanks, there's a button for it. It's free and very grateful
- If it drains even on stock it's a serious problem.
The situation is very weird. Let's analyze.
1) TW/LOS doesn't matter. Battery drain in both
2) No apps installed which could cause wakelocks
3) Battery SHOULDN'T be the problem
4) The drain is recognised as kernel "usage", though it couldn't be real 'cause of point 1
5) Neither Permissive nor Enforcing SELinux mods helped
At this point it doesn't look so much a SW problem, but more an HW one. About: Well, sometimes the discharge happens so fast the battery doesn't calculate the remaining capacity so well, and after some minutes the real charged cells are more than the "estimated" ones. It would explain the "goes up" of the percentage, but still not the drain.
It's very strange and very rare, but there's an infinitesimal possibility that the thermal paste went to the hell. And in this case there's not that much to do.
That's pretty pessimist though. I'd advice you to format everything, reinstall the latest stock TW and stick with it, and if it still doesn't work, try with some apps like Greenify and ForceDoze (this one works just with 6.0+) in order to at least TRY to reduce the drain.
I'm sorry I cannot help you more, if anyone has some suggestion, please let us know.
Click to expand...
Click to collapse
Next strange thing is, I have two S4 Active devices, both have the same problems. Am I just unlucky enough to get two broken phones?
Still, the device I got from I friend was ok the moment he gave it to me. He said battery lasted for only one day, but that would be ok. So it has to be something I did with the phone.
Youre are not alone. My Phone was/is also getting hot.
Then I did a full wipe ( format also internal memory partition!)
I'm current running cm13 (CM13 (20161228)). Batterie works now / normal ok / 1 / 2 Day s ( no great usage ). But when i telephone with someone it's getting hot in 15 min. Modem Version is I2995XXUDPB3.
dotnano said:
Next strange thing is, I have two S4 Active devices, both have the same problems. Am I just unlucky enough to get two broken phones?
Still, the device I got from I friend was ok the moment he gave it to me. He said battery lasted for only one day, but that would be ok. So it has to be something I did with the phone.
Click to expand...
Click to collapse
Have you flashed any custom ROM? Try downloading an entire stock firmware for your country / carrier from sammobile and flash through odin 3.09 and check. The S4 active generally gets hot on usage but should not get very hot. You can also try using powersave mode that limits cpu max freq and prevents heating. Battery on normal usage shoukd last for little under a day to a day with normal usage unless you are using data (otherwise set mobile networks to GSM only which saves battery and reduces heat)
JASONRR said:
Have you flashed any custom ROM? Try downloading an entire stock firmware for your country / carrier from sammobile and flash through odin 3.09 and check. The S4 active generally gets hot on usage but should not get very hot. You can also try using powersave mode that limits cpu max freq and prevents heating. Battery on normal usage shoukd last for little under a day to a day with normal usage unless you are using data (otherwise set mobile networks to GSM only which saves battery and reduces heat)
Click to expand...
Click to collapse
I have flashed the latest DBT (unbranded German) and I have the same problems. Does the version of Odin make a significant difference? I used 3.10.6.
dotnano said:
I have flashed the latest DBT (unbranded German) and I have the same problems. Does the version of Odin make a significant difference? I used 3.10.6.
Click to expand...
Click to collapse
Normally i have seen issues flashing through odin 3.10 and prefer 3.07 or 3.09. If the firmware flashed correctly and you do not have any issues then it should be fine.
CPU temp of 65% without powersave mode is fine and watching youtube videos does consume battery. Try a different charger / cable combination as that too can have issues. If the battery gets charged quickly (on stock kernel under 2 - 2.5 hours from 0 to 100) then there is definitely an issue with the charger and it will drain quickly too.
JASONRR said:
Normally i have seen issues flashing through odin 3.10 and prefer 3.07 or 3.09. If the firmware flashed correctly and you do not have any issues then it should be fine.
CPU temp of 65% without powersave mode is fine and watching youtube videos does consume battery. Try a different charger / cable combination as that too can have issues. If the battery gets charged quickly (on stock kernel under 2 - 2.5 hours from 0 to 100) then there is definitely an issue with the charger and it will drain quickly too.
Click to expand...
Click to collapse
I tried 3.10, 3.12 and 3.07 so far. Not successfully. Tried 3.09 now, we'll see.
I have a Sony Xperia Z1C as comparison, YouTube needs maybe 1% for 5 Minutes.
Cables/Chargers shouldn't be the problem. I have the original Samsung, also cable. Charged to 0 to 75 % in 90 Minutes. Same with cable and charger from Anker. So should be fine?
So no new ideas?
dotnano said:
So no new ideas?
Click to expand...
Click to collapse
I have no idea too but i have the same Trouble with mine BUT I'm still using the original Rom and didn't flash it. So maybe it is an Hardware issue.
My Battery is getting old, yes, but it is the third one. The Phone gets hotter than in its first years.
I hope you'll find a reason!
My i9295 always has been like this: 1 minute on-screen time = 1% battery loss. So this basically is a 2 hour phone... Stock or custom rom didn't matter. A friends i9505 used a lot less power, therefore I assume that the LCD (instead of the S4's AMOLED) is the problem.
Vardion said:
My i9295 always has been like this: 1 minute on-screen time = 1% battery loss. So this basically is a 2 hour phone... Stock or custom rom didn't matter. A friends i9505 used a lot less power, therefore I assume that the LCD (instead of the S4's AMOLED) is the problem.
Click to expand...
Click to collapse
Nah, why should it? There are a lot of i9295 users that don't have any problems.