Database Develop

[Q] [HELP!!]Battery drained in 8h on standby, random restarts and power offs

Hi.
I'm having bit of a problems with my SGS in last couple days; i'll give you last example, but same thing is happening last couple days:
- yesterday I have fully charged my phone; I have disconnected it form charger before I went to sleep.
- today in morning (8h later), phone was turned off
- when I turn it on, I got message to connect it to charger, because battery was on 15% (from 100% to 15% in 8h on standby)
- because this thing was happening last couple days, I have made sure that I didn't leave any apps running in background, that will be able to drain battery that fast.
- I opened settings and take a look at battery statistics;
Cell standby was over 70%!!
When I click on it, it says "Time without signal 70%"
So basically, he has drained almost entire battery by searching for GSM signal. But I have full GSM signal all the time.
But what's the weirdest thing; now that I'm awake, phone will work normally all day; it will last on those 15% almost whole day on standby.
But when i'll go to sleep, ti will start to go crazy over night.
And it's no a problem that he drains almost entire battery over night (it is, but not biggest); problem is that he powers off, so I can miss some important calls in morning (this is my business phone).

do you use a taskkiller? If so, stop using it for a while to see if things improve.

Have you upgraded to Froyo?

pwhooftman said:
do you use a taskkiller? If so, stop using it for a while to see if things improve.
Click to expand...
Click to collapse
I use task manager, and he is "manual" task killer; so I don't have any automatic task killers.
_dsk_ said:
Have you upgraded to Froyo?
Click to expand...
Click to collapse
I'm still on 2.1 android.

Did you install any new apps recently, did you change anything etc?

nwsk said:
Did you install any new apps recently, did you change anything etc?
Click to expand...
Click to collapse
A week ago I made factory reset and clean up my phone, because I had installed bunch of stuff there that I didn't need, and this was faster solution then unistalling one by one app.
I have then rooted my phone (it was rooted also before factory reset), and I have installed voodoo lag fix (before I had one click lag fix).
After that I setup my phone with just stuff I use, and it was working brilliantly till last couple days; only thing that I can remember that I have installed in last couple days was update for angry birds.
One user on Samsung galaxy forum suggested that I switch on flight mode, and than turn it off. Now I will see if this will help; apparently this resets GSM radio.

Voodoo has always been known to kill batteries. I got 8hours on single charge when I was on voodoo. No big deal
single finger pecked on a galaxy s

Recent sleep deaths.

Hello xda!
Lately my phone has been acting real crazy. I've been on Cognition rom for about a month and I never experienced any issue. However, after flashing SpeedMod k12t, my phone kept freezing while on sleep after 1-2 hours of use. I decided to reflash firebird 2 to make sure it wasn't the new kernel, but my phone recently froze in screen off. I am now sure this has nothing to do with a specific kernel. I have been trying to figure out what's wrong with my phone. I am pretty sure it has nothing to do with my modem either, since I have been using jk4 for about a week or three and this issue never came up until now.
All I'm really thinking of would be my setcpu settings. I recently started to use profiles with the following settings :
Screen off : 200-200 performance (now 400)
Charging : 1000
Battery < 101% : 800 - 1000 conservative
Battery < 39% : 400 - 800
I am thinking the screen off settings are causing all of this trouble. I only started using these a day or two before all of this started. Back then I was testing out a couple different kernel (suckerpunch, gb's kernel, firebird, speedmod). I had a rather poor uptime with suckerpunch because it took a while for me to find the correct settings, and when I did, I remember getting a sleep death that I blamed on the kernel because of the history of charge death it had back then.
Also, my original kernel was firebird and my phone was quite stable during the 3 weeks I've used it. I'm leaving the possibility of a bad kernel away because of this.
So here's my question, xda : What's up with my phone? Is reflashing back to stock and back to Cognition the only possible fix for this? Could me flashing kernels without disabling voodoo be the cause of all of this? Could disabling voodoo and reflashing the kernel fix this? Can set cpu be the cause of all of my trouble (i disabled it for now).
Thanks,

I have the same exact problem and it drives me insane. I have no solution for it except if your last 4 IMEI numbers (under your battery) are below 6000. Mine is 8355 so i dont know.

The last four numbers under my battery are 6, 5, 5, and 9. 6559. This only started a day or two ago. I've only had this phone for a month. So far the problem seems gone, but I've noticed my battery went from 67% to 80 after rebooting my phone to check the numbers under my battery. I recently wiped my battery stats though.

I've only had my phone for about a month too, so i don't know any more than you do. The only thing different for me is the shutdowns were already happening, and the the ROM I flashed just increased it.

Yeah, my phone also seems to freeze when alseep but only if its charging. Sometimes if i disconnect it, it will freeze or if i get a phone call while its charging.

My Captivate had sleep death (randomly) and charge death on some ROMs. After flashing several combinations of ROM/kernel/modem, it seems ok now. I think I will keep on finding a better combination.
SetCPU has some issue with OC/UV kernel on my Captivate, so if you have the same problem try to disable SetCPU first and see if the problem goes away.

Since last flash I have had absolutely bullsh!t awesome battery usage :-) *READ*

Ok...this is going to sound completely outrageous! It seems outrageous to me even I have never had this good of battery consumption ever! The phone was purchased 16/08/10 and has retained the standard battery all this time and had various Samsung ROMs on it. Mostly DarkyROMs that have improved battery quite considerably. It currently has its first stable ROM of ICS since I started flashing ICS from just prior to RC1. The ROM is a bit of a mix-matched frankenstein build of a ROM by me originated from MyICS and OneCosmis RC3.1. I have recently experienced allot of issues (including very poor battery drain) prior to this last flash and so have many of my users...actually most jumping **** (and I don't blame them).
My last ROM flash seemed to stable and go through perfectly, I was running with my own 2.0.1 and was about to release this ROM (that I'm currently on from a system dump) as a 2.2.0 version update for everyone else.....however I have held back because of the announcement of RC4.....so any of the improvements I haven't released. The install procedure backs up battery stats so as not to need re-calibration and has done so for the last 3 or 4 install. I am running the latest platypus kernel made for RC4 though
Anyway the last time I had my phone on any decent charge 22hours ago. It's currently 10.40pm EST and phone went on charge about 12.30pm lastnight. Since then I have had data left on (something I wouldn't normally do...I was used to renaming APN prior to ICS) and wifi on* (granted I have latest Juice defender ultimate)
*set to trained locations to auto-on within 250m of known wifi access point and disable 3G when wifi connected
I have gone the whole day today, with a small amount of internet (damn genie widget gets me every time with cool interesting things flashing up on the screen lol) and moderate phone usage; texting and a hand full of 10-15min phone calls....nothing out of the ordinary.
I plugged the phone to USB to transfer some things from work and it was plugged in for approximately 15-20seconds. I use multi-mount SD card app (I have included the lite version in my ROM) and allows for fast transactions and also to be able to use the phone whilst connected etc (read up about it). And I did the same here at home to transfer the things off again. It has remained sitting beside my PC untouched (unusual cause I like to fiddle) for the last 3 hours...and decided to pick it up and glaced at the battery 90%. Ok so I waited another hour and glanced again and STILL 90%.
Is there something weird going on here that I should know about? My phone has never been this good even if I left it completely on standby and in flight mode it would have eaten more than that! It seems almost stupidly impossible.
Fill me in on your take of this situation? Happy to do a complete system dump to try figure this sh!t out cause I made so many mods last ROM update I wouldn't know which one is contributing or if all or none?
edit: included more information

It's now 2:20am I am going to bed. My phone is 86%
A drop of only 4% in nearly 4hours. 1% per hour is not too bad

How do you handle synchronization, and why kind of tweaks do you perform with juicedefender?

heh i know what you mean
Im using as well icssgs rc4 (pulled) for 3 days, and right now i have 10% left after 29 hours of using my phone as wifi, downloading, sync, calls, sms and some music, all i can say is that rc4 +platypus kernel is the beast for the battery. my phone never lasted for such a long time, even on rc3.1 it used to die after 18 hours of being idle.

Reporting
7am 77%
10am 62%
10.55am - poor signal and market prompted to download an update for LinkedIn battery has plumited to 23%
36hours use and still 23% battery is pretty good. At least the resil
I will be making a deodexed version of RC4 sometime soon with a few extra bonuses ....however it won't be all that special as I have been giving away my secrets everywhere on the forum to help others on any ROM (not just my own) so anything included in my next release will be old news lol
Juice defender? Tweaks? I am not sure what you mean? You mean what are my settings?

Ok...wtf? Battery is climbing back up again now? That is something that has never happened before! Im on 26% again

realy ? ))

Offfical time of death 4.34pm EST. approximately 40hours after full charge. I am stoked with that.
Edit: I will be making a donation to Platypus Kernel right now

Can you tell which rom you had before flashing rc4 and another question are you experiencing any other problems with the rom like sd problems because im considering to go rc4 too.

dimon28 said:
Can you tell which rom you had before flashing rc4 and another question are you experiencing any other problems with the rom like sd problems because im considering to go rc4 too.
Click to expand...
Click to collapse
I am still running RC3.1, I am just using the RC4 kernel
I am in the process of developing my own RC4 ROM based off this RC3.1 (my own version of it anyway) that is the first ROM I have that is stable. All versions of my ROMs prior to this have been very unstable. ROM is still odexed so that will be my first point of call and then repackage and get it up and running.
I am in the process of compiling some java code for wifi calling on vibrant though so I am too busy to even start on my ROM

HTC Vivid Stock ICS Issues

I've seen threads with this issue or that issue, but no single thread yet dedicated to issues that have cropped up for HTC Vivid users since the ICS OTA update.
I run stock-- No root, no custom rom, just stock the way it came from AT&T.
The phone has been wonderful. Battery standby time was phenomenal (on a full charge, I could expect to take my phone to work around 6:30 am, and see a minimum 60% to 75% left when I got home around 5:30 pm). I never experienced random reboots, crashes, etc.
Then I updated OTA to the new ICS using standard AT&T procedure-- This would be the official release, downloaded and installed last week.
Now, if I reboot the phone, I have to wait while it installs updates it already had when I installed ICS. This is a minor incovenience, but annoying.
I also see noticeably less standby time. I'm lucky now to have 50% left when I get home from work.
Most alarming, though, is the nightly crash on the charger. My dad is in and out of the hospital with heart issues, so turning off my phone to charge it isn't really an option. Every night since I updated, my phone random reboots on the charger (last night it did it twice).
So now I'm seriously wondering:
(1) Is anyone else having these new issues since updating to the official ICS release?
(2) Is there some way I can "downgrade" to the more stable version my phone had before (the extra features and tweaks aren't worth the tradeoff for stability and standby time)?
Thanks to any and all who take the time to consider this post and reply accordingly.

Why not try downloading the official RUU since you are still locked,
http://www.htc.com/us/support/vivid-att/downloads/ and install it
sounds like something scewed up when you uploded the OTA update via phone.

A little more detail...
I think it's important to note that these random reboots I've been getting since upgrading to ICS are only partially random.
They only happen when the phone is on the charger and "on." I recall a "charge death" issue with my old Samsung Captivate that perhaps I'm experiencing now with the upgraded HTC Vivid?
I know the obvious workaround is to charge it before going to bed, take it off the charger, then top it off the following morning. Perhaps I'll try that before doing the upgrade over again using the RUU. It's perplexing due to when it happens-- I know the phone doesn't require a full 3.5 hours to charge from, say, 35%, so it's some sort of charger keep-alive that must be forcing the reboot.
I'm still curious, though, to learn if anyone else is having these exact same issues after upgrade.
Thanks, Pumpiron579, for your suggestion! I've just downloaded the RUU and have it ready when I decide to try the update again.

I've upgraded to the latest ICS from AT&T and am not experiencing any of the reboot issues that you're speaking of. I put my Vivid on a charging dock and it goes into doc mode and is that way when I wake up in the morning. I even have it trip an alarm at 7AM. If it's rebooting overnight, I'm not aware of it. In GB there was a screen that told you the up time and sleep time. I can't find it on ICS otherwise I could confirm whether or not it is rebooting overnight.
As for battery life, it doesn't appear to be any worse than GB for me and for today, It's been on the battery over 1.5 hrs and still at 100% battery.

mug318ca said:
I've upgraded to the latest ICS from AT&T and am not experiencing any of the reboot issues that you're speaking of. I put my Vivid on a charging dock and it goes into doc mode and is that way when I wake up in the morning. I even have it trip an alarm at 7AM. If it's rebooting overnight, I'm not aware of it. In GB there was a screen that told you the up time and sleep time. I can't find it on ICS otherwise I could confirm whether or not it is rebooting overnight.
As for battery life, it doesn't appear to be any worse than GB for me and for today, It's been on the battery over 1.5 hrs and still at 100% battery.
Click to expand...
Click to collapse
Menu - Settings - Power - Battery Use
Select the Up time counter for more details

Thanks for that, homeslice, but I don't see overall up time. With GB, there was some counter that could show the hundreds of hours that it has been up since the last reboot.

mug318ca said:
Thanks for that, homeslice, but I don't see overall up time. With GB, there was some counter that could show the hundreds of hours that it has been up since the last reboot.
Click to expand...
Click to collapse
I've never paid too much attention to this...but when you go in and click on the battery time underneath the battery level, there's another uptime below the graph that i figured was total uptime?

I updated with the RUU and have had no problems with my phone what so ever, I have had no reboots when chargeing and the battery life is about the same for my phone.Also my phone is stock with bootloader locked.

My battery life seems to be about the same. However, I am getting a better LTE signal - 3 bars vs 1-2 bars before the upgrade.
The one thing that I've found to be an irritation is that before the upgrade, any photos attached to emails were automatically saved in a folder accessible by the Gallery. After the upgrade, they are saved in the Downloads; and that folder is not accessible from the Gallery. I have to use a file manager program like Astro to manually move the photo file to one of the Gallery accessible folders.
If there's a way to fix this, I would be all ears.

Battery life sucks after ICS upgrade
after I upgraded to ICS my batter life sucks, it used to come for a day, now its reaching 15% before evening.
Is this a known issue, is there a way to get a better battery life
Thanks

everything is fine fore me except the android is upgrading part every power on.
is that a problem?

houstonsveryown said:
everything is fine fore me except the android is upgrading part every power on.
is that a problem?
Click to expand...
Click to collapse
It's not a problem but a feature for all ICS installations.

mug318ca said:
It's not a problem but a feature for all ICS installations.
Click to expand...
Click to collapse
As far as I can tell you get the android is upgrading/optimizing every time dalvik cache is cleared..which from what I can tell happens on every reboot with a Rom that's not deodexed..like the stock Roms. Get on a Rom that's been deodexed and this won't happen. Otherwise enjoy the feature lol
Sent from my HTC PH39100 using xda premium

fix battery issues
Sorry to hear about the random reboots, and I hope a solution comes around. I personally have found no reboot issues at all. There is a problem with using Bluetooth hands free though, you can't press the call button on the device to make a voice call because Android removed the voice dialer so now you just hear a beep.
In regards to your battery, install Advanced Task Killer from the market. In the settings, set up the recommended kill list, the aggressiveness, and activate auto kill. I've been using it for a while and i can go all day with Bluetooth, Wi-Fi, Pandora, and other apps. After 10+ hours at work i get home with 35-40% battery still. Hope this helps. It also has a widget you can out on a homescreen so you can simply click and it kills what you set up already.

I used to have some random reboots in GB, turned to be an app or a widget that caused the problem. I did then a wipe amd installed minimal apps that I needed and didn't have the problem anymore. Then I started to install other apps one by one monitoring which one might be the problem, but I couldn't replicate it nomore. It was in the same time I experienced multiple (if not all of them) launchers and widgets so I don't even remember what I really had on it. This also might be for battery life too. Now I only use sense and the stock widgets and adw ex once in a while, I have >180 apps installed and no reboots and also battery life is very good.
Sent from my HTC Vivid via Tapatalk

Twice while streaming pandora over bluetooth I've had the phone just die. My music shuts off, screen is off, phones not responding, have to pull the battery. Also I've had issues with music skipping on bluetooth. Also third party apps won't show contact pictures that rely on Facebook. Worked fine before the
Update. Im considering wiping it and reinstalling everything.
Sent from my HTC PH39100 using XDA

Total newbie...delete if necessary
Downloaded the update last night and haven't sleep trying to fix this (OCD )...
I cannot see any updates on FriendStream event though I have my FB account linked to it.
I removed my FB account from "Accounts & Sync" synced it again received a notification "Allow HTC sense to access your FB account" and before Im able to click it the program keeps running and adds my FB account. Go to FriendStream and nothings there...

Found my issue
I have uninstalled few apps, seems to be that drained my batteries all day, now it looks better

Same Issue
WirelessMike said:
I've seen threads with this issue or that issue, but no single thread yet dedicated to issues that have cropped up for HTC Vivid users since the ICS OTA update.
I run stock-- No root, no custom rom, just stock the way it came from AT&T.
The phone has been wonderful. Battery standby time was phenomenal (on a full charge, I could expect to take my phone to work around 6:30 am, and see a minimum 60% to 75% left when I got home around 5:30 pm). I never experienced random reboots, crashes, etc.
Then I updated OTA to the new ICS using standard AT&T procedure-- This would be the official release, downloaded and installed last week.
Now, if I reboot the phone, I have to wait while it installs updates it already had when I installed ICS. This is a minor incovenience, but annoying.
I also see noticeably less standby time. I'm lucky now to have 50% left when I get home from work.
Most alarming, though, is the nightly crash on the charger. My dad is in and out of the hospital with heart issues, so turning off my phone to charge it isn't really an option. Every night since I updated, my phone random reboots on the charger (last night it did it twice).
So now I'm seriously wondering:
(1) Is anyone else having these new issues since updating to the official ICS release?
(2) Is there some way I can "downgrade" to the more stable version my phone had before (the extra features and tweaks aren't worth the tradeoff for stability and standby time)?
Thanks to any and all who take the time to consider this post and reply accordingly.
Click to expand...
Click to collapse
I am having the same issue. I am working with HTC on this issue. I have no idea what is causing this. You will find that it does it more frequently, not only when it is charging.

WirelessMike said:
So now I'm seriously wondering:
(1) Is anyone else having these new issues since updating to the official ICS release?
(2) Is there some way I can "downgrade" to the more stable version my phone had before (the extra features and tweaks aren't worth the tradeoff for stability and standby time)?
Thanks to any and all who take the time to consider this post and reply accordingly.
Click to expand...
Click to collapse
So are we able to go back to the Original Stock/Shipped Rom if we don't like this update?
I saw some things I liked about it in the recent reviews, but others that I didn't.

L2_hsic (latest update 12/12/13)

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!