Related
I have an issue I'd like to debug, but I need some information to help myself:
I charge my SGS (JM1) in the evening, when it's 100% full I disconnect the charger and go to bed (23:30), phone switches to airplane mode at 24:00. When I get up 8h after, my phone is off and has absolutely no battery left.
This happens every now and then, IMHO there's no app causing this (haven't installed anything lately). I can't reproduce the issue.
How would I best debug this and try to find out what's causing the battery drain?
Can I still read the battery log after a restart?
What apps Di you have and what Firmware?
Sent from GT-I9000 Jpm OS kernel with z4mod
DamianGto said:
What apps Di you have and what Firmware?
Click to expand...
Click to collapse
Firmware JM1 (rooted)
Apps:
aContacts
Alchemie
aLogcat
AnDream
Angry Birds
APNDroid
AppsOrganizer
Asphalt 5
c:geo
CallTrack
Coloroid
Explorer
GC Tools
geniewidget
GeoHunter
GPS Test
handyCalc
ICD Auskunft
Jorte
K-9 Mail
Kitchen Timer
Meraki Wifi
N-TV
OpenSudoku
RTM
SGS Tools
Snowstorm
Solitaire
Stats
Terminal Emulator
Timeriffic
wetter.info
Xing
Don't see Amy bad apps.
You can.use sgs toolbox to see the battery usage is.
Some make the phone almost never go in powersave mode.
Sent from GT-I9000 Jpm OS kernel with z4mod
Thank you so far.
I looked at the battery usage stats and saw that bluetooth was enabled for more than 7 hours (although it was disconnected). That IMHO shouldn't have completely drained the battery though...
I am seeing the same problem recently; the battery drains out really quickly in no time even when there are no major apps running. Even the battery usage menu shows nothing major. During this time I have noticed that the phone gets really hot and the battery indicator app shows that the battery temperature as b/w 40-50 C (its around 25-35 C when there is no issue). During this time I can't even make calls or send/receive SMS!!! Seems that it just cannot get a network signal.
There were no such issues for the last couple of months. I can't imagine an app directly or indirectly causing this.
If an app keep the phone awake all.the time and use wifi/Bluetooth/gps it will drain the phone fast.
The only solution is to find out where the flaw is.
Personal i would backup the phone and do a complete wipe/ reset of the phone so it will be clean and like new. Then i would test to se if it drain the battery.
If it does then it is broken and need a.repair. Else i would start to intake the apps i need, but looking close what they do.
Sent from GT-I9000 Jpm OS kernel with z4mod
SGSI said:
During this time I have noticed that the phone gets really hot
Click to expand...
Click to collapse
Ex-act-ly the same for me!
I will disable all self-installed apps via pm disable and see what happens.
I'll then report back...
Have you installed any lagfixes recently? When I had voodoo lagfix on jg4 I would get at best 8 hours of stand by time. As soon as I flashed jpm I get 1% drain per hour
Sent from my GT-I9000 using XDA App
I have not installed any lagfixes, my phone is on stock JG4 firmware. The battery life is otherwise very good, only at times (very random) the battery starts draining from 100% to 0% in a matter of few hours.I use System panel to check if there is any app that is causing this, but it does not indicate anything like that.
The only thing that I can think of is that the phone for some reason looses network (I can't make a call and send/receive sms during this time) and keeps trying to reconnect without success and hence drains out the battery. Once I reboot the phone everything becomes fine and the battery usage becomes normal. Is there any way to find out that the phone is trying to connect to the mobile network and this is causing the battery to drain out?
Neither do I, never used any lagfix so far, I'm on stock JM1.
The only thing that I can think of is that the phone for some reason looses network and keeps trying to reconnect
Click to expand...
Click to collapse
That's possible but I don't know how to log this...
Gnarf, it just happend again. Before going to work it was all normal, now it's frozen.
I connected it to my computer, but WinXP recognized it as an unknown device.
ADB doesn't work, else I had pulled the logfiles.
maybe u should consider upgrading to JM7 or JM9. and before installing apps do a full reset and cache wipe.
MagicOnline said:
maybe u should consider upgrading to JM7 or JM9.
Click to expand...
Click to collapse
I'm waiting for CM 6.1 to sort it all out, given that "FroYo by Samsung" still isn't what I expected it to be - at least judging from the betas.
Hey guys,
the day before yesterday i flashed Darky's 9.5 on my phone.
This is the first Darkys version for me. The flashing was fine and very easy but then i got big problem regarding the Wlan battery use.
First i tell you how i flashed Darkys, perhaps i did a failure here.
1) First i flashed Darkys Reserrection Version on my phone
2) After that i configured the Darkys App from the market and flashed the reserrection.zip with CWM
3) At the end i flashed Darky's 9.5 with CWM
Now the points regarding my problem.
Yesterday night i switch off my phone with at least 85% battery. I switched off GPS,Bluetooth and i deactivated the data transfer mode for UMTS. But it was my intention to test the battery drain with active WLAN, because with the original T-Mobile Firmware the phone uses circa 25% battery a night.
But when i woke up i was really shocked. My phone turned off and the battery was complete empty. In this night the battery drained 85%. How is this possible? There were no apps running excepting the Advanced Task Killer.
Did i something wrong? (When i flashed the battery was fully charged)!!
//edit
Here are my settings:
PDA: I9000XWJS8
Phone: I9000XXJVE
CSC: I9000XXJS1
Kernel: DarkCore 1.0
I wouldn't think this was a common issue. Have you tried just re-flashing the ROM again via CWM? Maybe try the same thing again?
Thx for your answer.
Yeah i even think that it's not a common issue.
I will watch the battery this night. If the bug occurs again, i will flash the Rom with CWM again. Have i to disable the lagfix or can i do it on the fly without changing something in the current system ? If yes, where?
my battery is the best its been in a long while since using this rom so i wouldnt dismiss it just yet. what modem are u using?
I use the modem Darky's App Configurator has recommend (JQ1 but i have read that JVE is flashed (se my settings above)). But i think I will try flashing again. This night the battery drops from 100% to 47% with the same settings I mentioned above. Then i watched the battery usage, but they were strange.
Wifi and "Wifi using" uses 100% cause they were running the whole time. But the category "execution" used 75%, so the phone did not drop into sleep mode for about 75% of the whole night? How is this possible? I checked all my 3rd party apps I installed on my own and they don't have a setting to manage this.
Does one app of Darky's Configurator do this?
Well Darky can answer question best .
Me i blame the rom change the rom .
jje
Now i flashed Darkys 9.5 with wipe again.I will watch the battery drain and I will notify you about the result.
//edit
Now I go asleep and I will report tomorrow if the flash was successfull. But I got one question left:
By accident I saw in the wireless setting window that my phone scans every 5 seconds for new devices, even if its connected to my own router. (If the phone goes to standby the WLAN does not scan cause of my settings). But why das it scan every 5 or 6 seconds, even if it's connected to my own device?? Is it possible to increment the scan time?
Good morning guys,
here is my update:
I think the reflash worked. Last night my phone uses 10% battery with wifi and data transfer on, gps and bluetooth off. I think this is a good value.
By using the flightmode the next times I will save some more
Now there is the question left regarding the number of wifi scanns. (see the post above). Is it modifiable ?
smudgy456 said:
my battery is the best its been in a long while since using this rom so i wouldnt dismiss it just yet. what modem are u using?
Click to expand...
Click to collapse
If you don't mind me asking: what modem do you use? And how long does your battery usually last for?
Thanks
mister-viper said:
I use the modem Darky's App Configurator has recommend (JQ1 but i have read that JVE is flashed (se my settings above)). But i think I will try flashing again. This night the battery drops from 100% to 47% with the same settings I mentioned above. Then i watched the battery usage, but they were strange.
Wifi and "Wifi using" uses 100% cause they were running the whole time. But the category "execution" used 75%, so the phone did not drop into sleep mode for about 75% of the whole night? How is this possible? I checked all my 3rd party apps I installed on my own and they don't have a setting to manage this.
Does one app of Darky's Configurator do this?
Click to expand...
Click to collapse
Did you recalibrate your battery after upgrading to Darky's 9.5?
It is recommended that u recalibrate your battery when you flash a new ROM.
You shoukd recalibrate your battery, i.e. drain it, turn off your phone and fully charge it, completely drain it (use it heavily). Then charge it again and voila, recalibrated!
Also, I find that after flashing a new ROM the battery drains really quick the first 2 times I charge it, before actually working as it should. So it's not that strange that your phones battery was dead in the morning. But I think this also has to do with recalibrating the battery.
Darkys v9.5 has a battery life of 3-4 days for me (not heavy usage) so it should be better after recalibrating your battery!
Sent from my GT-I9000 using XDA Premium App
I’m creating this thread to help anyone who’s been affected with SOD (Sleep of Death). Here’s a brief history of what I’ve tried so far:
- I was running stock 2.2 for about a year, had lag, choppiness, etc.. but never a SOD
- Flashed CM7.1 2 weeks ago (stock kernel), phone is not amazingly fast but experiencing SODs every few days.
- Created a Tasker profile to wake the phone every 1 hour, (wait 5 seconds command), no SOD for a week
- This morning, got a SOD again.. missed my alarm and was late for work
- All SODs happen at night while charging.
- Today I downloaded ‘Wake my Android Pro’, supposedly it send a wakelock every 29 minutes and prevents the phone from entering deep sleep.
My next step if this fails and I get another SOD:
- Set CPU min clock to 350 (read that this doesn't help but will try anyway)
- Activate SoftLocker to prevent the phone from ever going to sleep, this is the last resort since it will affect my battery life (wish there was a Tasker plugin to toggle the settings so I can enable it only when charging)
Does anyone know how long after turning off the screen does the phone go into deep sleep (versus regular sleep)?
gabster21 said:
I’m creating this thread to help anyone who’s been affected with SOD (Sleep of Death). Here’s a brief history of what I’ve tried so far:
- I was running stock 2.2 for about a year, had lag, choppiness, etc.. but never a SOD
- Flashed CM7.1 2 weeks ago (stock kernel), phone is not amazingly fast but experiencing SODs every few days.
- Created a Tasker profile to wake the phone every 1 hour, (wait 5 seconds command), no SOD for a week
- This morning, got a SOD again.. missed my alarm and was late for work
- All SODs happen at night while charging.
- Today I downloaded ‘Wake my Android Pro’, supposedly it send a wakelock every 29 minutes and prevents the phone from entering deep sleep.
My next step if this fails and I get another SOD:
- Set CPU min clock to 350 (read that this doesn't help but will try anyway)
- Activate SoftLocker to prevent the phone from ever going to sleep, this is the last resort since it will affect my battery life (wish there was a Tasker plugin to toggle the settings so I can enable it only when charging)
Does anyone know how long after turning off the screen does the phone go into deep sleep (versus regular sleep)?
Click to expand...
Click to collapse
I'm also using CM7 (nightly #146) with neo kernel..I only have had SOD once (while using stock kernel IIRC). Now I'm booting every evening before going to bed and haven't noticed any problems (knocking the wood..).
Btw, as you came from froyo did you flash GB before going to CM7? Or at least GB bootloaders prior flashing?
Can't really say any solution to your problems since these sods are quite hard to catch..logcat, dmesg, etc are our friends with these kinds of problems
Sent from my GT-I9000 using xda premium
Kurre said:
I'm also using CM7 (nightly #146) with neo kernel..I only have had SOD once (while using stock kernel IIRC). Now I'm booting every evening before going to bed and haven't noticed any problems (knocking the wood..).
Btw, as you came from froyo did you flash GB before going to CM7? Or at least GB bootloaders prior flashing?
Can't really say any solution to your problems since these sods are quite hard to catch..logcat, dmesg, etc are our friends with these kinds of problems
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
No, I didn't flash GB, I installed CWM bootloader and flashed CM7 from recovery (had to find a workaround to get past the e3 protection).
So far with "Wake my Android Pro" I see the screen go on and off quickly (about 1/2 a second) every 29 minutes.. too early to tell if this is helping with SODs, I'll report back regularly to update the results
Woke up today to my alarm, wohoo! Phone doesn't seem to go to sleep and battery life is fine.
charging on a PC.
Hello
Thank you for the informative thread.
I have a Galaxy S i9000 running 2.3.6, XXJW4 and CF-root, and find it frustrating not to be able to fully trust my phone to respond whenever needed, be it listening to Internet radio, using sat nav, getting Facebook notifications (yes I got them back after reinstalling Facebook and clearing Dalvik cache but I should talk about that in another thread) and of course making and receiving calls now and then.
I was wondering whether the fact that I have been hooking it up to a PC to charge it through the day (and of course plug and unplug it a few times during the day) actually made the situation worse.
So far I have been getting an SOD every two days. The 'serious' SOD would come on after a 'less serious' SOD had already happened ie the phone went into coma and then came out of it and lasted for 6 to 8 hours longer before actually falling into the SOD coma.
I stopped using the PC as a charger (using a cheapo replacement micro USB charger) and so far 3 days have gone by without a hint of an SOD. Fingers crossed. Will keep investigating.
Cheers
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!
I have encountered a problem and need some help pls...
I recently flashed to 4.0.3 official rom German version (not leaked version), unrooted. I downloaded the firmware from samsung-updates.com, upgraded the phone, everything worked fine.
However, i found out recently that sometime if i left phone idle, the battery drains really quickly. say if i charged it up to 100% and left it over night, next morning, it will only have 60% left.
firstly, i went to Settings, then Battery, i found out even when the screen is OFF, the is still keep on "awake" -ing, i then downloaded CPU spy, i can see that when the battery drains quickly, CPU was constantly operating in 200MHz, something must be running in the background all the time.
I also downloaded betterbatterystatus, i have checked the wakelocks, everything worked fine.
I wonder if any of you guys have the same problem.
This does not happen often, and i believe restart the phone can "cure" it temporarily, but it will come back you dont know when...
btw, i have turned off google+ services.
please help and excuse my English.
Thanks
bump
You have Wifi on? Or added a new app recently? I usually reboot my phone when I install a new app since last time I installed a new app there was battery drain issue.
This helped making my phone deep sleep and decreasing battery drain
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
Take a look at this blog article
http://www.folblog.it/migliorare-la-durata-della-batteria-dei-samsung-galaxy/
Inviato dal mio GT-N7000 usando Tapatalk
I had the same issue and solved it by doing the following steps:
1. Allow a charge to 100% to occur
2. Before you unplug the charger, unlock your phone to the homescreen
3. Restart your phone
After doing this, I noticed my phone goes into deep sleep and my battery lasts longer throughout a day.
Sent from my GT-N7000 using xda premium
Mine did that, but I did the charge up, airplane mode, shutdown trick and it
fixed it.
Got a friend on an older galaxy captive, he finally got around to upgrading to GB,
and his was rooted before the update and he forgot to unroot before the update.
After the update, part of the old root program was running all the time sucking his battery down. After he figured out a way to get rid of it, the problem with battery drain stopped.
If the charge, airplane, shutdown trick doesn't work, download something like CPU Spy and see what's taking up the battery. Could be something left over from GB still running.
drilym said:
This helped making my phone deep sleep and decreasing battery drain
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
I was having a heating problem when charging the device (Battery temperature above 46C) and huge battery drain.
This was fixed after following the above steps.