Develop Bugs

[Q] HTC Kaiser CPU Doesn't Sleep?

Did a search, and didn't find anything regarding this, so I'll point this out. I've noticed whenever my Kaiser (KAIS100) goes to sleep, it doesn't actually sleep, I can still press every button and the phone will "wake", screen comes on.
When I check Spare Parts > Battery History, it shows my phone's been running for 5days even though it's been on for 10 minutes actual. If I continue to put the phone to sleep that time grows exponentially.
Is my KAIS really sleeping, or is there a bug somewhere?
I'm running l1q1d's latest .32 kernel, with Fat Free Froyo build with system/data on NAND.
Battery also only lasts about 8hrs in "standby", and not even 2hrs with full use. With WinMo, I get about 36hrs standby, and about 5hrs full use.

Krazy-Killa said:
I've noticed whenever my Kaiser (KAIS100) goes to sleep, it doesn't actually sleep, I can still press every button and the phone will "wake", screen comes on.
Click to expand...
Click to collapse
Screen comes on, obiusly, but its locked right? that the way its ment to be... if you wanna check the hour or see if u got messages or missed calls... or it unlocks?
Krazy-Killa said:
When I check Spare Parts > Battery History, it shows my phone's been running for 5days even though it's been on for 10 minutes actual. If I continue to put the phone to sleep that time grows exponentially.
Click to expand...
Click to collapse
I guess its not completley implemented yet, search this forum I remember I looked something about it, or post a comment to our good friend n2rjt in that thread:
http://forum.xda-developers.com/showthread.php?t=782269
Have you modified .nbh file with atools and entered the correct value on the advanced batt capacity? (units = battery real mAh * 1.6) if you havent or if you own an old battery you'll experience a lot of batt consumption or inaccurate readings....

albertorodast2007 said:
Screen comes on, obiusly, but its locked right? that the way its ment to be... if you wanna check the hour or see if u got messages or missed calls... or it unlocks?
I guess its not completley implemented yet, search this forum I remember I looked something about it, or post a comment to our good friend n2rjt in that thread:
http://forum.xda-developers.com/showthread.php?t=782269
Have you modified .nbh file with atools and entered the correct value on the advanced batt capacity? (units = battery real mAh * 1.6) if you havent or if you own an old battery you'll experience a lot of batt consumption or inaccurate readings....
Click to expand...
Click to collapse
The phone locks like it's suppose too, but the problem I'm having is the CPU of the Kaiser isn't actually falling asleep. I'm getting the same battery consumption as when the screen is off compared to on, and sitting there (no activity on my part, just leaving the screen on for no reason )
Every so often the phone will be asleep, and the only way to bring it back on is by hitting the power button, but about 95% of the time I can press the call button, end button, OK button, IE button, hell even push down on the wheel on the other side of the Kaiser and the screen will come on showing the lock screen.
As far as the battery capacity, I have not done that, but the phone's been auto-learning my capacity, and it will get to the 2160 units, compared to the 2000 it's always set too, and sometimes reach 2377 units.
I have tried several Radio versions, down to 1.65.xx.xx version (which was the original version on my phone), and no changes, and tried different builds and no change either. DZOs kernel doesn't make a difference either, except screw up my battery meter completely. lol

uhm thats wierd.. i can only unlock through the power button, what i have experienced is that if its conected to an external power source it does reacts to any button I press.... but not on battery... maybe its a build issue... right now im using scoots CM rls 5a, dont remember if warbyte's donut behave like that...

albertorodast2007 said:
uhm thats wierd.. i can only unlock through the power button, what i have experienced is that if its conected to an external power source it does reacts to any button I press.... but not on battery... maybe its a build issue... right now im using scoots CM rls 5a, dont remember if warbyte's donut behave like that...
Click to expand...
Click to collapse
Did some more testing, and found that without it plugged into power it does only respond to the power button, but again it's only about 15-20% of the time, and even those times seem iffy as it just seems like the phone's just slow to respond.
Phone is also somewhat warm as well even when "off", and I do have the phone overclocked to 450MHz, kernel is set to 425 (running a test on speed/stability atm)
At 425MHz it's still reasonably warm, and at 450 the temperature jumps alot.
Anyone else have an issue of the tap sounds when tapping on the screen sometimes not playing? Granted phone quality is great, and GPS is working well, though Camera is broken on my end, even though it was working before.

It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.

n2rjt said:
It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.
Click to expand...
Click to collapse
by chanse wasnt weather widget? had a really bad slowdown over scoots CM because of that widget, was constantly trying to update the weather....

albertorodast2007 said:
by chanse wasnt weather widget? had a really bad slowdown over scoots CM because of that widget, was constantly trying to update the weather....
Click to expand...
Click to collapse
Yes that's the one. it needs to be removed, and can be replaced by Fancy Widget.
Sent from my Android on HTC Kaiser/Kaiser/Polaris using XDA App

n2rjt said:
It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.
Click to expand...
Click to collapse
Ok, I'll give it a whirl, and remove some of the widgets I have running, and see if it does help out. Right now though I'm re-installing /system as I tried messing around with the density as 110 seems to work real well with where things are placed on the home screen (no widgets are overlapping each other), but Market won't work, and the Android Keyboard keeps crashing (on-screen).
But anyways, phone's booting back up, so I'll test out the battery life here again, as I got about 95% charge right now, so should serve as a good test for battery life, and CPU Sleepage.

Having a similar issue, seems to behave ok (screen lock comes on when I press power button) but power usage on standby is similar to original poster's. About 8 hours standby. Went to bed last night and it said 66% charged (1300mAH battery) and it didn't last the night. Takes a looooong time to charge to full though so I doubt it's lying about fully charging the battery, suggesting it's using it up at a fast rate.
How do I check background tasks?
Edit: This is with WiFi, GPS and Sync OFF by the way. On the other hand I live in a low signal area (typically 1-2 bars) could it be straining to get a better signal? Used to have an old nokia that used to run itself flat in no time when there was a low/missing signal!
Edit 2 : Figured it out, turns out the ebay app has a service and a process running - even with notifications turned off! Have killed these and see if anything improves

That could very well be part of the problem, although it shouldn't kill it from 66% with just the radio. How much capacity does it calibrate itself to?

cycloid said:
Having a similar issue, seems to behave ok (screen lock comes on when I press power button) but power usage on standby is similar to original poster's. About 8 hours standby. Went to bed last night and it said 66% charged (1300mAH battery) and it didn't last the night. Takes a looooong time to charge to full though so I doubt it's lying about fully charging the battery, suggesting it's using it up at a fast rate.
How do I check background tasks?
Edit: This is with WiFi, GPS and Sync OFF by the way. On the other hand I live in a low signal area (typically 1-2 bars) could it be straining to get a better signal? Used to have an old nokia that used to run itself flat in no time when there was a low/missing signal!
Click to expand...
Click to collapse
Phone Radio really shouldn't use more power with low signal, in fact it really shouldn't affect power output at all (well except the fact that it's on). I have a 1350mAH battery, but it's reading at 2470 adjusted, so I re-flashed a new kernel with the new battery changes, now it's reading 2437units adjusted, which is over 1500mAH for the battery which is not what I own. But on the bright side, my battery capabilities are improving, and the battery meter is starting to read alittle more accurately.

Krazy-Killa said:
Phone Radio really shouldn't use more power with low signal, in fact it really shouldn't affect power output at all (well except the fact that it's on). I have a 1350mAH battery, but it's reading at 2470 adjusted, so I re-flashed a new kernel with the new battery changes, now it's reading 2437units adjusted, which is over 1500mAH for the battery which is not what I own. But on the bright side, my battery capabilities are improving, and the battery meter is starting to read alittle more accurately.
Click to expand...
Click to collapse
yes, i boutght seidio 1600 mAh, and the kernel ended up adjusting it to 3260 units... (about 2000 mAh) maybe the 1.6 factor isnt right just as n2rjt said, maybe its closer to the 2.0

Seems like ebay may have been the culprit. Killed the ebay process and application in the background and only used about 10% over night (as opposed to over 60% the night before). I'll have to leave it overnight with ebay running again for a proper scientific test next

cycloid said:
Seems like ebay may have been the culprit. Killed the ebay process and application in the background and only used about 10% over night (as opposed to over 60% the night before). I'll have to leave it overnight with ebay running again for a proper scientific test next
Click to expand...
Click to collapse
Yah, I'm starting to run into issues with certain apps keeping the phone awake and not letting it sleep. I kill some of the apps and it actually helps out the battery some.
I installed the original launcher from one of the other froyo builds, but came across with an FC with acore, so now back with ADW.Launcher or LauncherPro.

Krazy-Killa said:
Yah, I'm starting to run into issues with certain apps keeping the phone awake and not letting it sleep. I kill some of the apps and it actually helps out the battery some.
I installed the original launcher from one of the other froyo builds, but came across with an FC with acore, so now back with ADW.Launcher or LauncherPro.
Click to expand...
Click to collapse
When you install a app, take a look at its requirements, like "PREVENT FROM SLEEP". You might have a app doing just that..

daedric said:
When you install a app, take a look at its requirements, like "PREVENT FROM SLEEP". You might have a app doing just that..
Click to expand...
Click to collapse
Yep, most of the apps I download have that. But in sad news, I'm actually going back to WMO 6.5 as I can't seem to keep Android stable on my kaiser.. I've reinstall the same build twice (which I know is not corrupted, as it was working fine 2 days ago), and Market is always corrupted...... So, for now, until I have a secondary phone I can revert too, I'll be going back to WMO for the time being.

Krazy-Killa said:
Yep, most of the apps I download have that. But in sad news, I'm actually going back to WMO 6.5 as I can't seem to keep Android stable on my kaiser.. I've reinstall the same build twice (which I know is not corrupted, as it was working fine 2 days ago), and Market is always corrupted...... So, for now, until I have a secondary phone I can revert too, I'll be going back to WMO for the time being.
Click to expand...
Click to collapse
Umh... sad...
We'll wait for you! Bye bye

daedric said:
Umh... sad...
We'll wait for you! Bye bye
Click to expand...
Click to collapse
LOL! Not like I'm leaving, I'll be popping on here every so often, and still doesn't mean I'll use Haret to load up Android to test out new builds that come out, and new kernels that are released in the future.

Krazy-Killa said:
LOL! Not like I'm leaving, I'll be popping on here every so often, and still doesn't mean I'll use Haret to load up Android to test out new builds that come out, and new kernels that are released in the future.
Click to expand...
Click to collapse
Man... that's a sin! You can't do that! You'll be off from the Brotherhood!
Kiddin' ;D

N7100 Wake up lag

My note 2 always takes around 1-2 seconds to wake up every time with wake up button. I found its quite annoying compared to my old i4. Does anyone have the same problem. Any fix?

I have the same problem.
sometimes it is instant, but sometimes it takes a sec.

Try turning off S-Voice activation on the home button and also 'Pop up Note on Lockscreen' in the lock screen settings.
Try turning off the lock screen ripple effect also.

Normal
That is normal behavior and I believe is part of the android platform (so the note2 is not to blame). When you lock your android phone, it goes into "deep sleep" (unless you have an app running in the background which is preventing it from doing so). Deep sleep is basically a phase where the cpu clock speed gets very low to save battery. When you wake your phone it takes about a full 1-1.5 seconds to wake it from that phase.
If you're not getting that 1-1.5sec delay, that means your phone wasn't in the deep sleep phase when you woke it up.
I'd say ~1 sec delay when waking your device up is a good trade-off for a better standby battery performance.

interfreak said:
Try turning off S-Voice activation on the home button and also 'Pop up Note on Lockscreen' in the lock screen settings.
Try turning off the lock screen ripple effect also.
Click to expand...
Click to collapse
I already turned off all above. I cant get to ripple effect because i use vpn and it forced me to use pattern lock. Thanks anyway

MohJee said:
That is normal behavior and I believe is part of the android platform (so the note2 is not to blame).
Click to expand...
Click to collapse
No. This is not normal behavior. The Nexus 3 does not have this lag despite running the latest OS (same as the Note 2). It's ****ing annoying.....

It is a good sign, it means that the phone was in deep sleep state.

It is basically the quad core thing..takes time to go from deep sleep to rev up.the cores
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

interfreak said:
Try turning off S-Voice activation on the home button and also 'Pop up Note on Lockscreen' in the lock screen settings.
Try turning off the lock screen ripple effect also.
Click to expand...
Click to collapse
thanks for the tip, did them all, and it is much faster now.
"edit"
I think it is a deep sleep issue after waiting a while

MohJee said:
That is normal behavior and I believe is part of the android platform (so the note2 is not to blame). When you lock your android phone, it goes into "deep sleep" (unless you have an app running in the background which is preventing it from doing so). Deep sleep is basically a phase where the cpu clock speed gets very low to save battery. When you wake your phone it takes about a full 1-1.5 seconds to wake it from that phase.
If you're not getting that 1-1.5sec delay, that means your phone wasn't in the deep sleep phase when you woke it up.
I'd say ~1 sec delay when waking your device up is a good trade-off for a better standby battery performance.
Click to expand...
Click to collapse
What you have said is basically CRAP. It has nothing to do with deep sleep and everything to do with the chipset that Samsung uses in most of their recent phones. The Nexus is a notable exception. It has NO WAKUP LAG. If this was an Android thing, as you have incorrectly stated, the Nexus would have wakeup lag and so would HTC phones. They don't.
If you have no idea what you are talking about, please don't post your own theories, which in this case are totally WRONG.

appro77 said:
What you have said is basically CRAP. It has nothing to do with deep sleep and everything to do with the chipset that Samsung uses in most of their recent phones. The Nexus is a notable exception. It has NO WAKUP LAG. If this was an Android thing, as you have incorrectly stated, the Nexus would have wakeup lag and so would HTC phones. They don't.
If you have no idea what you are talking about, please don't post your own theories, which in this case are totally WRONG.
Click to expand...
Click to collapse
@ appro77 - thanks for your input, (I always like it when a theory is proved wrong by demonstrating proof of the apposing theory.) while I agree with you I can only hope your constructive input will inspire a solution.

MohJee said:
That is normal behavior and I believe is part of the android platform (so the note2 is not to blame). When you lock your android phone, it goes into "deep sleep" (unless you have an app running in the background which is preventing it from doing so). Deep sleep is basically a phase where the cpu clock speed gets very low to save battery. When you wake your phone it takes about a full 1-1.5 seconds to wake it from that phase.
If you're not getting that 1-1.5sec delay, that means your phone wasn't in the deep sleep phase when you woke it up.
I'd say ~1 sec delay when waking your device up is a good trade-off for a better standby battery performance.
Click to expand...
Click to collapse
That's absolutely incorrect to blame Android as the culprit. This is the only Android device I've had that has such considerable wake-up lag.

appro77 said:
What you have said is basically CRAP. It has nothing to do with deep sleep and everything to do with the chipset that Samsung uses in most of their recent phones. The Nexus is a notable exception. It has NO WAKUP LAG. If this was an Android thing, as you have incorrectly stated, the Nexus would have wakeup lag and so would HTC phones. They don't.
If you have no idea what you are talking about, please don't post your own theories, which in this case are totally WRONG.
Click to expand...
Click to collapse
Im not sure if thats crap, but i also heard kinda things all the time from many CM devs, when i was using note N7000, Milestone3 and LG O2X, those CM devs said same thing like wakeup lag cause by deep sleep, if device wake up instantly, it means the battery is draining.....
But the lag is like 1 second, not 2 seconds, so if my note2 can wake up around 1 second, i can accept it and count the "wake up lag" theory is true, if this is a false theory, please correct me with the true one.

It's normal behaviour for a stock rom.
It's certainly fixable with source built roms
Affects to battery and 'deep sleep' are debatable.
S3 has identical behaviour
If it bothers you, take your head out of your rectum.
Sent from my GT-N7105 using xda app-developers app

Hi I am on the at&t version but we have it as well but it kinda a exnous processor thing every one that I had with that processor does it. I install soft locker on the market completely gets rid of it and dont show any real adverse battery effects. Just my two cents .
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

because of google play???
moved to new threat

Screen wake lag - Let's solve this thing

EDIT: According to garyd9, this is an Exynos issue and cannot be fixed. I believe him that this is an Exynos issue because it supports what I've seen, and he's a smart guy. I'm still holding out hope that there is some possible resolution in the future. Why else are we here if not to find ways to make our phones better, right? However, because of the nature of this issue, it's not going to be resolved by app settings, disabling apps, etc. If you don't see the lag yourself, it's because your phone isn't in deep sleep when you try to wake it.
Original Post:
Alright guys, some of you have probably noticed that this phone suffers from the wake lag that others (all Samsung?) have also suffered from.
Symptom: When you press the power or home button it takes 1-2 seconds before the screen turns on.
This DOES NOT happen when the phone is plugged in, likely because the problem is a delay getting the phone out of deep sleep. Deep sleep does not occur while the phone is plugged in.
Culprit: Anybody know? My wife's AT&T GS2 has this same problem and has with every ROM/Kernel combo I've tried (AOSP, AOKP). My Skyrocket has the issue on some of the more recent versions of Sky Jelly Bean, which I believe Sean said was a Kernel problem.
Fixes that don't work: This morning I tried the most popular suggestions:
Turn off Lock Screen Popup note
Lock Screen Ripple Effect
S-Voice home key
S-Voice Auto-start speaker
S-Voice wake up command
NONE OF THESE WORK!
So, let's band together and solve this thing. Do some tests and find something that works. Preferably, a solution that takes as little modding as possible.
Is this something that can only be solved by a customer kernel? If so, let's see if a dev is up to the task!
EDIT TO ADD: This seems to be an issue on all variations of this device. I'm searching their forums for an answer, but don't see one yet. I decided to post this here to get more eyeballs on the problem
More info from Entropy512:
Entropy512 said:
To be more detailed: It seems to be specific to how Samsung wires up the modem interfaces of Exynos devices. On Exynos4 devices, they're always hung off of HSIC (a variant of USB) buses. Since HSIC is based on USB, it has the same slow suspend/resume of USB. Almost all Exynos3 devices hung the modem off of a serial port if I recall correctly, and these devices could suspend/resume much faster. If you look at a resume sequence, there are huge time gaps, and after the first 200-300 msec, almost all resume activity is modem stuff.
The only solution, unless someone figures out a way to make the HSIC resume faster (I'm not messing with it, I have enough trouble getting it not to drop the bus randomly!!!!!!!), is to inhibit deep sleep with a wakelock - but this will be bad for battery life.
Click to expand...
Click to collapse

Jrockttu said:
Alright guys, some of you have probably noticed that this phone suffers from the wake lag that others (all Samsung?) have also suffered from.
Symptom: When you press the power or home button it takes 1-2 seconds before the screen turns on.
This DOES NOT happen when the phone is plugged in, likely because the problem is a delay getting the phone out of deep sleep. Deep sleep does not occur while the phone is plugged in.
Culprit: Anybody know? My wife's AT&T GS2 has this same problem and has with every ROM/Kernel combo I've tried (AOSP, AOKP). My Skyrocket has the issue on some of the more recent versions of Sky Jelly Bean, which I believe Sean said was a Kernel problem.
Fixes that don't work: This morning I tried the most popular suggestions:
Turn off Lock Screen Popup note
Lock Screen Ripple Effect
S-Voice home key
S-Voice Auto-start speaker
S-Voice wake up command
NONE OF THESE WORK!
So, let's band together and solve this thing. Do some tests and find something that works. Preferably, a solution that takes as little modding as possible.
Is this something that can only be solved by a customer kernel? If so, let's see if a dev is up to the task!
Click to expand...
Click to collapse
I'm not feeling major sleep lag on att , Sprints on the other hand was pretty bad with 2-3 sec delay

Simple soft locker from market... doesnt seem to effect battery. Try it out works great
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

u921333 said:
Simple soft locker from market... doesnt seem to effect battery. Try it out works great
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
The app creates a partial wakelock, so it will affect battery. A wakelock will keep the phone from going into deep sleep, which is what extends Android phone battery life. With such a large battery, it won't be as noticeable on this phone, but it still has substantial negative effects.

sling said:
I'm not feeling major sleep lag on att , Sprints on the other hand was pretty bad with 2-3 sec delay
Click to expand...
Click to collapse
I'm getting about 2 second lag on both mine and my wife's AT&T N2s. Mine is rooted, hers is not.

Jrockttu said:
Alright guys, some of you have probably noticed that this phone suffers from the wake lag that others (all Samsung?) have also suffered from.
Symptom: When you press the power or home button it takes 1-2 seconds before the screen turns on.
This DOES NOT happen when the phone is plugged in, likely because the problem is a delay getting the phone out of deep sleep. Deep sleep does not occur while the phone is plugged in.
Culprit: Anybody know? My wife's AT&T GS2 has this same problem and has with every ROM/Kernel combo I've tried (AOSP, AOKP). My Skyrocket has the issue on some of the more recent versions of Sky Jelly Bean, which I believe Sean said was a Kernel problem.
Fixes that don't work: This morning I tried the most popular suggestions:
Turn off Lock Screen Popup note
Lock Screen Ripple Effect
S-Voice home key
S-Voice Auto-start speaker
S-Voice wake up command
NONE OF THESE WORK!
So, let's band together and solve this thing. Do some tests and find something that works. Preferably, a solution that takes as little modding as possible.
Is this something that can only be solved by a customer kernel? If so, let's see if a dev is up to the task!
EDIT TO ADD: This seems to be an issue on all variations of this device. I'm searching their forums for an answer, but don't see one yet. I decided to post this here to get more eyeballs on the problem.
Click to expand...
Click to collapse
I have everything that you have listed except Turn off screen popup mode & I have no lag at all.

It's a side effect of the exynos SOC. You can't "fix" it. It just takes about 800ms to wake from deep sleep.

garyd9 said:
It's a side effect of the exynos SOC. You can't "fix" it. It just takes about 800ms to wake from deep sleep.
Click to expand...
Click to collapse
800ms???? No way can I wait that long lol jk
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

garyd9 said:
It's a side effect of the exynos SOC. You can't "fix" it. It just takes about 800ms to wake from deep sleep.
Click to expand...
Click to collapse
Bummer.

Jrockttu said:
The app creates a partial wakelock, so it will affect battery. A wakelock will keep the phone from going into deep sleep, which is what extends Android phone battery life. With such a large battery, it won't be as noticeable on this phone, but it still has substantial negative effects.
Click to expand...
Click to collapse
I have used it on my galaxy s2 and my international galaxy s3 without seeing any negative battery issues. Now granted it has to have some effect but even with the not so great life on s2 wasnt noticeable. Try it out and see if it works for you. I was skeptical at first.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

It is in fact S-Voice.. completely remove it from the Note and you will remove the lag.. this has been an issue with virtually every device with S-Voice... I bet there will be a bebloated ROM come along in the next day or 2 and itll fix it.
Sent from my SAMSUNG-SGH-I317 using xda premium

I dont but I do know my galaxy s3 had it even when I was on aokp.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

daddymatt said:
It is in fact S-Voice.. completely remove it from the Note and you will remove the lag.. this has been an issue with virtually every device with S-Voice... I bet there will be a bebloated ROM come along in the next day or 2 and itll fix it.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Like the poster above this says, my wife's Galaxy S2 has the lag on AOKP and AOSP based roms that do not have S-Voice. As much as I don't want to believe it, Gary is likely right that it's an exynos issue. I was just hoping that it could be solved through a kernel.
Tested it for ****s and giggles, definitely not S-Voice. I disabled it and restarted phone. Let it settle about a minute from start up, opened BetterBatteryStats to CPU state screen and looked at the "deep sleep" state. Turned screen off for a few seconds, lagged, checked deep sleep state to make sure it had increased (ensuring it was recovering from deep sleep). This is the simple method to test any of these supposed fixes that people say will solve the laggy wake.
Anybody that says their phone doesn't lag when they wake up the screen is likely because they're looking at it while they're charging it, they're playing music, they have an active notification, or they're turning it off and back on really quick. All of these prevent the phone from deep sleeping. Deep sleep is what causes the issue.

I had lag on my Note I whenever it would deep sleep on any Rom. This only happened when I had Wi-Fi off when sleeping. When I turned Wi-Fi on all the time lag was gone. Not a clean battery friendly fix but the lag was driving me crazier than charging the battery a little sooner.
Sent from my GT-N7000 using Tapatalk 2

I have the att version and I was just wondering...the same thing...I am willing..to try anything...I mean it sucks just waiting a little bit. I was just waiting for a new rom

daddymatt said:
It is in fact S-Voice.. completely remove it from the Note and you will remove the lag.. this has been an issue with virtually every device with S-Voice... I bet there will be a bebloated ROM come along in the next day or 2 and itll fix it.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I would have to say this is true. I've seen people do this in videos and it seems to work. They say its the wake looking and checking to see if you held the button or double clicked it that will solves this problem. Are there any other settings that control the home button settings like how you show recent apps or s-voice?

http://www.youtube.com/watch?v=UHMIxBUclh0&feature=plcp

truth77 said:
I would have to say this is true. I've seen people do this in videos and it seems to work. They say its the wake looking and checking to see if you held the button or double clicked it that will solves this problem. Are there any other settings that control the home button settings like how you show recent apps or s-voice?
Click to expand...
Click to collapse
The only thing disabling S-Voice does is make your Home key work faster once the phone is already on because it's not waiting to see if you're double tapping it. S-Voice has no impact on the wake issue.

Mj23foreva said:
http://www.youtube.com/watch?v=UHMIxBUclh0&feature=plcp
Click to expand...
Click to collapse
That's the first thing I watched this morning when investigating this issue. If you notice, his "fix" doesn't seem to work that well for him. Try it yourself, it won't work. That's why I put it in the OP that these don't work.

No lag here and the phone's been in use/running for 24 hours now.

[APP][GPLv3] SnooZy Charger - Battery saver for Galaxy Nexus ghost charging

Hi everyone,
SnooZy Charger is an open-souce (GPLv3) Android app I developed initially for a friend whose Galaxy Nexus phone had battery issues due to the Gnex ghost connections!
Some devices randomly detect a power connection without any charger being actually connected to the phone. This would drain the battery because of the screen turning on to display the "Charging" message, multiple times per hour till screen timeout.
The app runs as a background service, listening to power (dis)connections. The event is logged into a power connection history (can be useful!) and the screen is turned off to save battery consumption by the display.
The APK and source code are available on GitHub. Scan the QR Code to download for free on the Playstore.
Attached files:
Installable APK
Screenshots
Playstore QR Code
Feedback, comments and suggestions are most welcome! Please take into consideration that this is still a beta version...
thanks,
mudar

I never knew that my phone had the ghost charging problem this bad. In 2 hours I had 1247 events, thats way too much. I didnt even touch the phone and it dropped 30% battery. The app is a bit aggresive I know its still in beta but this is what I saw. It turns off my acreen real fast when I'm in the lockscreen, sometimes it takes me up to 3 times to unlock my phone because the phone's screen turns off fast.
Btw: The app is really sinple to use and I like the holo style it is very clean looking, thanks for your time and effort, hopefully you are able to find a solution for this problem.

droid4lif3 said:
I never knew that my phone had the ghost charging problem this bad. In 2 hours I had 1247 events, thats way too much. I didnt even touch the phone and it dropped 30% battery. The app is a bit aggresive I know its still in beta but this is what I saw. It turns off my acreen real fast when I'm in the lockscreen, sometimes it takes me up to 3 times to unlock my phone because the phone's screen turns off fast.
Btw: The app is really sinple to use and I like the holo style it is very clean looking, thanks for your time and effort, hopefully you are able to find a solution for this problem.
Click to expand...
Click to collapse
Thanks for your comments
I never imagined that events could occur so often! I'll look into a cleaner way to do the screen lock, to be able to handle that frequency.
Technically speaking, the app does not handle screen on/off:
App listens to power connection/disconnection
OS turns the screen ON on power connection
App, afterwards, locks the phone. This is based on settings (is phone locked? Is it power loss?)
Locking the phone, turns the screen off.
The more efficient way would be to tell the OS not to turn the screen ON on power connection/disconnection (if the screen is turned OFF). However, I don't have the impression the Android SDK allows such functionalities!
It will probably be simpler to add Screen lock aggressivity (0, 2 o5 seconds) in settings, which would define the delay between consecutive screen locks.
Will see what I can do!

Cyanogenmod has a feature to not wake the screen on power connects/disconnects as well. Good idea with the app for everyone else!

I had this issue and it was caused from my phone getting moisture, not exactly wet but having it in my pocket from sweating or being in the rain. I dried it out with a blow dryer and haven't had this issue since. Also I used alcohol and cleaned the battery port from corrosion and that seemed to really do the trick.
Great app though in case I am wrong about my phone I can surely use it. thanks for sharing!

jmdsdf said:
Cyanogenmod has a feature to not wake the screen on power connects/disconnects as well. Good idea with the app for everyone else!
Click to expand...
Click to collapse
Is this feature added in cm 10.1? cause I am using cm 10 and I didnt find this anywhere. can you tell where can I find it

nachiket_xda said:
Is this feature added in cm 10.1? cause I am using cm 10 and I didnt find this anywhere. can you tell where can I find it
Click to expand...
Click to collapse
Settings>Display and lights>wake on plug

App Updated
droid4lif3 said:
I never knew that my phone had the ghost charging problem this bad. In 2 hours I had 1247 events, thats way too much. I didnt even touch the phone and it dropped 30% battery. The app is a bit aggresive I know its still in beta but this is what I saw. It turns off my acreen real fast when I'm in the lockscreen, sometimes it takes me up to 3 times to unlock my phone because the phone's screen turns off fast.
Click to expand...
Click to collapse
Version 1.0 released!
I've added a new setting: Screen lock delay. Values available are Immediately / 3 sec / 5 sec. [screen capture attached]
This should solve the locking too fast on phones with furious ghost charging like yours Thanks again for your feedback!
https://play.google.com/store/apps/details?id=ca.mudar.snoozy
https://github.com/mudar/SnooZy
http://snoozy.mudar.ca/
mudar

nachiket_xda said:
Is this feature added in cm 10.1? cause I am using cm 10 and I didnt find this anywhere. can you tell where can I find it
Click to expand...
Click to collapse
It seems to me that Wake on plug (Settings/Display and lights) has be introduced in CM 10.2 and possibly for some unofficial CM 10.1
Such a feature does solve the battery drain issue in a better way, but SnooZy can still be useful for unrooted phones!
mudar

New Version 1.2
New version released, version 1.2
Changelog:
Control cache history age in Settings (7, 14 or 30 days).
Display is not turned off when incoming call.
Updated text descriptions.
Norwegian translation by Aeyoun.
APK attached here. Update is also available on the playstore

New Version 1.5, Material Design
Version 1.5 released. Changelog:
Updated to Material Design!
Added "Connection status" setting: power connection, disconnection or both
Added "Charger type" setting: AC adapter, USB, Wireless, all
Select custom notification sound
Added "no history" option
APK and screenshots attached here. Update is also available on the playstore

oreo
mudar1488 said:
Version 1.5 released. Changelog:
Updated to Material Design!
Added "Connection status" setting: power connection, disconnection or both
Added "Charger type" setting: AC adapter, USB, Wireless, all
Select custom notification sound
Added "no history" option
APK and screenshots attached here. Update is also available on the playstore
Click to expand...
Click to collapse
i never needed this app until yesterday when i updated to oreo from nougat. but lineage oreo (unofficial) seems to have removed or maybe just moved the option to not wake the screen on charge and as i use wireless charging that tends to connect / disconnect regularly it was driving me crazy until i found this app to keep the screen off. works great for me and on oreo :laugh:

Wrong version
mudar1771 said:
Version 1.5 released. Changelog:
...
APK and screenshots attached here. Update is also available on the playstore
Click to expand...
Click to collapse
The linked version is not 1.5 but 1.2
I´ve got version 1.54 from this link.

Note 3 neo lockscreen lag FIXED!

Hi guys I have found a solution to the lag at the lockscreen!
Please download the following app:
https://play.google.com/store/apps/details?id=eu.thedarken.wl
App Name- Wake Lock Manager
Steps:
1. Install the above app and open it.
2. Click on PARTIAL_WAKE_LOCK.
3. The above numbers should go to 4.
4. Now go into options (by pressing the menu button)
5. Check the following boxes:
Autostart On boot
Notifications
6. Close the app and enjoy!
You may go in app manager and untick "show notifications" if you find the app notifications annoying or unnecessary.
I have tried this on 5 phones and it works perfectly. It does not affect the phone otherwise and it also does not use extra battery(I have tested it).
Questions are always welcomed!
Here is my link to the youtube video for the same:
https://youtu.be/QqT63RrAims
Thank you.

It works well , thank you for sharing.

musmax said:
It works well , thank you for sharing.
Click to expand...
Click to collapse
Anytime!

thnks a lot

Surely it works, but this isn't a good solution.
Selecting number 4 in that app means that your phone will be "forced" in a partial wake lock state.
In other words when the screen goes off, the cpu it's still running and will never go to deep sleep (normal standby state).
If you use your phone a lot, this will affect battery life only a bit.
However if with a single charge your phone usually last 1-2 days, forcing a partial wake lock will affect a lot battery life.
Battery will discharge also when you are not using your phone... because cpu will be always on (partial wake lock).
So.. this is a "solution", but not a good solution.
Thanks for sharing this tips, but be aware.. if you use this app your phone's cpu will never go to deep sleep.
Hi!

anshul1490 said:
thnks a lot
Click to expand...
Click to collapse
Welcome bro!

FSRider said:
Surely it works, but this isn't a good solution.
Selecting number 4 in that app means that your phone will be "forced" in a partial wake lock state.
In other words when the screen goes off, the cpu it's still running and will never go to deep sleep (normal standby state).
If you use your phone a lot, this will affect battery life only a bit.
However if with a single charge your phone usually last 1-2 days, forcing a partial wake lock will affect a lot battery life.
Battery will discharge also when you are not using your phone... because cpu will be always on (partial wake lock).
So.. this is a "solution", but not a good solution.
Thanks for sharing this tips, but be aware.. if you use this app your phone's cpu will never go to deep sleep.
Hi!
Click to expand...
Click to collapse
Hi FSRider,
I know what you are trying to say and I had the same doubts earlier. So I tested it for a week.
What i did was,
First I didnt use phone much(only calling and msging) for a day and then did the same thing using the app running. I found that the difference in consumption was very less. In first case 30% was consumed and in the 2nd case 33% was consumed.
Secondly, I played some heavy games for 1 and half our and without the app the consumption was 28% and with the app it was 31%.
Thirdly, I just didnt touch my phone for 5 hours. Without the app the consumption was 1% or less and beleive me with the app too it was 1%.
Cheers!

Hi all lockscreen lag fixed in latest build which is on sammobile download it and flash you will not face any issue

sidcool121 said:
Hi all lockscreen lag fixed in latest build which is on sammobile download it and flash you will not face any issue
Click to expand...
Click to collapse
I have installed the latest build but still the lockscreen lag is present. I guess currently the above given method is the only method to remove that lag.