Database Info

Updated:(3/6/2011) Lets Solve G2x Freezing Issue (Solved:Random Freezing in standby)

I know there are countless threads related to G2x Problems but none of the threads are focusing on isolating the reasons of Freezing Issue. I have recently upgraded my phone from Galaxy S Vibrant to G2x and i have to say i love the hardware and performance. Only Issue for me is random freezing.
After using the phone for 2 weeks and trying 3 roms
1. Stock
2. EB 1.04
3. Dark Sinister 1.1
I have come to a conclusion that kernel and rom is not the solution. At least not for me.
So i will try to solve the problem using hardware testing.
From my past 2 weeks experience.
1. Phone Freezes at night during charging
2. Phone Freezes when ever i turn off/on wifi and bluetooth and gps and Data (4g/3g) (Still have to figure out which of them is the cause. Cause i usually turn all off when i need to save battery).
Test Day 1
For Reason 1
I am using SetCpu and have changed Min from 216 to 312Mhz. I am trying this because i think very low cpu usage in standby for a very long period causes the phone to freeze. Its a Hunch i am not sure.
For Reason 2
I will keep wifi, Bluetooth and GPS off.
I will keep 4g/3g Data On all the time.
To My Surprise its been 16 hours no freeze. It includes charging at night. Lets see how long i can go without a freeze. Upon freezing i will make some changes.
Update 31/5/2011 (Test Day 2)
Ok its been more than 40 hours and not a single crash...
I removed the following possibilities as well....
It wont crash upon excessive usage.
Also Normal Heat up does not cause the crash.
As i have been playing Samurai II Vengeance all day long... Until I ended it. Several times charging along playing. I even played it on TV using HDMI. Not a single crash. I used to have around 3 crashes a day on stock rom when i unboxed my new G2x.
I also started using GPS from today. So lets see how it goes. I will update it every 24 hour.
Update 3/6/2011 (Test Day 5)
Ok i am considering Random Freezing On standby as solved because i havent had a single freeze at night after setting CPU Clock at 312 MHz using SetCPU. There are also other comments that back up my solution. I am considering this the solution of one problem.
2nd Issue of freezing while using cell phone apps is because of certain applications that are either buggy or not compatible with tegra Platform. For that i will start another thread with individual application testing for all apps that can cause the system to freeze or crash.
Please Discuss apps System Bloat-ware/User Apps that cause your G2x to Crash or Freeze in the following thread i created:
http://forum.xda-developers.com/showthread.php?p=14399089
Thanks for all the feedback.

Luckily I dont get that issue, buy I think this is a good test :u

Good point. I have not had these issues but i do have trinity kernel and minimum speed is 300
G2x with CM7 and trinity kernel

All you have to do is be careful what apps you install. I've had the phone for over a month and the one time it rebooted or froze was when I used an app the phone didn't agree with.
I am almost certain that people are experiencing reboots and freezing because of the apps they have on their phone. Hopefully the update will solve the problem because it shouldn't be that way.
Sent from my LG-P999 using XDA App

In my opinion, the shut down has to do with temperature of the phone. As long as I keep the phone cool by not charging and multitask with other things, then my phone is fine.

garrychau said:
In my opinion, the shut down has to do with temperature of the phone. As long as I keep the phone cool by not charging and multitask with other things, then my phone is fine.
Click to expand...
Click to collapse
I used to think the same thing but the problem is my phone gets hot and works fine. I am almost positive it has something to do with an issue in the kernel that's being exposed by certain apps. My Xoom on release had reboots and SOD and it went away with app updates and removals. It also has Tegra 2
Sent from my LG-P999 using XDA App

mobilehavoc said:
I used to think the same thing but the problem is my phone gets hot and works fine. I am almost positive it has something to do with an issue in the kernel that's being exposed by certain apps. My Xoom on release had reboots and SOD and it went away with app updates and removals. It also has Tegra 2
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Do you or @kangxi remember what Apps gave you issues?

it has to be a driver issue, its virtually the only explanation for why devs have not hammered it out yet or even CM7 team for that matter... it has problems on pure AOSP which leaves drivers or overheating (unlikely)... LG has to come up with the fix because they know their drivers and hardware better than everyone else...

Well the obvious problem I see is that they are all based on the stock rom. Try using one build from AOSP or a CM variety.
I didn't stay stock long but I did have reboot using the leaked Gingerbread (which is what EB is built from). I don't follow it but one is based off the stock 2.2.2 rom and the other is based off the leaked 2.3.3 rom.
I had nothing but problems with the stock roms. Thus your problem I think. Move over to Bionic, CM7, Gigglebread, or something.
I tested my phone and I didn't have a reset in like 5 days (which then my battery died overnight because I forgot to plug it in). I usually crackflash the CM nightlies and haven't had any problems with reboots or any issues requiring a reboot (aside from the flashlight killing audio, but just don't use it).

There are definitely two problems - software and the battery. I used to way more problems until I exchanged the battery for a new one and that solved most of my issues. The issues that remain are definitely software based.

tackleberry said:
Good point. I have not had these issues but i do have trinity kernel and minimum speed is 300
G2x with CM7 and trinity kernel
Click to expand...
Click to collapse
Thanks for this information/ Changing the minimum speed didnt affect the battery life but it has survived two nights without crashing. So i am planning to keep it at 312Mhz min.

kangxi said:
All you have to do is be careful what apps you install. I've had the phone for over a month and the one time it rebooted or froze was when I used an app the phone didn't agree with.
I am almost certain that people are experiencing reboots and freezing because of the apps they have on their phone. Hopefully the update will solve the problem because it shouldn't be that way.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I Completely Agree with you. Some Applications do cause system crashes. But I have removed all the t-mobile bloatware and i only have few games and GPS apps. All games are from tegra zone. So I am sure they are supported.
For GPS App i am using Copilot and it didnt crash on me once.

I just installed setcpu and set minimum to 312. I'm keeping everything else the same to see if this change has any difference. Will report back.
Sent from my LG-P999 using XDA App

Looks like you are gaining progress. Sounds like keeping the processor revved up a little more does the trick.
It would be a simple fix for people to try that have reboot issues. I can't get mine to reboot, so unfortunately I cannot help you. My contribution was to resist from flashing for as long as possible to test how long I could get my "uptime" to. I got up to 127 hours when I passed out without charging it.
I'm running 20 hours now because I forgot to charge it again (seems to be my only problem, lol).

Looks like you may have fixed your rebooting issues. It sounds feasible that the clock speed could be causing it. I never had a reboot so I can't help you out but I can tell you that I have a profile under SETCPU that clocks it at 216 min and 216 max when the display is off and I don't have a problem. I wonder why the low clock speeds would only effect certain devices? Maybe it's certain apps that stay running in the background (since there poorly written) that require higher clock speeds than what the G2X gives at idle?

jrwingate6 said:
Looks like you may have fixed your rebooting issues. It sounds feasible that the clock speed could be causing it. I never had a reboot so I can't help you out but I can tell you that I have a profile under SETCPU that clocks it at 216 min and 216 max when the display is off and I don't have a problem. I wonder why the low clock speeds would only effect certain devices? Maybe it's certain apps that stay running in the background (since there poorly written) that require higher clock speeds than what the G2X gives at idle?
Click to expand...
Click to collapse
I've definitely noticed that the G2X wakes up faster and smoother (fade in from screen off) when min is set to 312mhz that's for sure. if this is all it will take to stop the reboots, I'll be super happy because otherwise this phone is just amazing.

mobilehavoc said:
I've definitely noticed that the G2X wakes up faster and smoother (fade in from screen off) when min is set to 312mhz that's for sure. if this is all it will take to stop the reboots, I'll be super happy because otherwise this phone is just amazing.
Click to expand...
Click to collapse
Have you noticed any changes in battery usage? I haven't really played around with SETCPU much but can the clock speed be set lower and if it can, have you tried slightly lower settings than 312mhz?

y are u guys using setcpu? and its def cuz the min is too low faux has his at 400 and no problems morfic also has his a little higher then what is it i think 216?? thats too low thats y setcpu isnt supported yet.....pimp my cpu

Someone asked me a question earlier. Only app I had issues with was fring. Soon as I opened it and started playing around with it, phone rebooted.
I uninstalled and it never happened again.
Sent from my LG-P999 using XDA App

mobilehavoc said:
No clue what you're trying to say but setCPU works fine. At startup for first time I selected Tegra2 and it works great. I have max set to 1000 and min to 312mhz (default was min to 216mhz). I'm running stock ROM but with root. that's all.
Click to expand...
Click to collapse
well thats y it works for u, u cant overclock over a thousand mhz so in ur situation ur ok i guess it only applies for people running a custom kernel then setcpu doesnt work, then u would need pimp my cpu

ATTENTION: Potential fix for sleep death

Ive had sleep death since day 2 of ownership....three days ago i flashed existz jvp voodoo gb kernel and have NOT had sleep death. I need people to see if this is a fix or just luck. If your on gingerbread, (NOT miui or cm7) try this kernel and see if it fixes it. I *think* its compatible with all jvo and jvp. Im on jvo and it works
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.

Appreciate the heads up fyi for us all. I'm running DG's latest right now but will keep this in mind.

I dont think it would work on newest cog due to different kernel source. This is I9000 based and cog is captivate based.
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.

Yeah, I just meant I'll keep it in mind for when I flash to a Rom that could use that Kernel. Again, thanks for the fyi.

topiratiko said:
Ive had sleep death since day 2 of ownership....three days ago i flashed existz jvp voodoo gb kernel and have NOT had sleep death. I need people to see if this is a fix or just luck. If your on gingerbread, (NOT miui or cm7) try this kernel and see if it fixes it. I *think* its compatible with all jvo and jvp. Im on jvo and it works
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.
Click to expand...
Click to collapse
I personally tried every kernel/rom combo out there and finally just had to replace my phone. I really hope you found a solution for your phone, but when I'd find a good combination for my phone it would usually start shutting down again eventually. Not trying to shoot you down, just letting you know my experience with the issue.
The only thing that actually put a band-aid on my issue was the app "Captivate Keep Alive". I say "band-aid" because although the phone was no longer shutting off on it's own, the battery would drain real fast, so it wasn't really the ideal solution. If you're still under warranty, I recommend just getting it replaced.
Thread with same issue: http://forum.xda-developers.com/showthread.php?t=731560

id10terror said:
I personally tried every kernel/rom combo out there and finally just had to replace my phone. I really hope you found a solution for your phone, but when I'd find a good combination for my phone it would usually start shutting down again eventually. Not trying to shoot you down, just letting you know my experience with the issue.
The only thing that actually put a band-aid on my issue was the app "Captivate Keep Alive". I say "band-aid" because although the phone was no longer shutting off on it's own, the battery would drain real fast, so it wasn't really the ideal solution. If you're still under warranty, I recommend just getting it replaced.
Thread with same issue: http://forum.xda-developers.com/showthread.php?t=731560
Click to expand...
Click to collapse
I know the feelin...i was using softlocker...same as keep alive but without the atrocious status bar icon....if it shuts down on this kernel ill do the warranty....its been 4 dayz with no shutdowns and 8 + hours of phone idle nightly....lookin good so far
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate. Yea I get 2000+ on quadrant. Yea ive pulled 5.17 mbps down from a tower. I appreciate XDA helping me turn this phone into a beast.

One day without random shutdown, may be it really works.
I've tried many Roms and kernels with no luck, thanks

pexo74 said:
One day without random shutdown, may be it really works.
I've tried many Roms and kernels with no luck, thanks
Click to expand...
Click to collapse
Glad its working. Keep me posted...day 5 no shutdown
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.

The reason you may not be having any sleep death is if the governor is set not to go into Deep Sleep. The Talon kernel supports OC/UV and that may be the culprit. However, my experience with voltage regulation kernels has not been nearly as stable as with ones that don't. I had to just replace my phone when I had the sleep death issues...good luck though.

Is sleep death a reboot. Ive been on oc/uv talon kernal and it gets reboots pretty often it drives me nuts. Always happens when i listen to music too
Sent from my GT-I9000 using XDA App

trekie86 said:
The reason you may not be having any sleep death is if the governor is set not to go into Deep Sleep. The Talon kernel supports OC/UV and that may be the culprit. However, my experience with voltage regulation kernels has not been nearly as stable as with ones that don't. I had to just replace my phone when I had the sleep death issues...good luck though.
Click to expand...
Click to collapse
I'm sure that is going to Deep Sleep, I've Cpu Spy installed in my phone.

pexo74 said:
I'm sure that is going to Deep Sleep, I've Cpu Spy installed in my phone.
Click to expand...
Click to collapse
Same here
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.

Anyone have anymore feedback?
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.

Day 7 NO sleep death
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.

1 week without shutdown. O'be tried the new release of talon, and works too.

[Q] Fix for G2X sleep of death?

The main problem with my G2X is the sleep of death, which happens a lot. I get occasional reboots too, but not too often. I tried flashing EaglesBlood 1.05 and then CM7 nightly (7/6), which I'm on now, and I still get sleeps of death and reboots, with perhaps reduced frequency but still bad. Maybe it's the battery, though I don't have overheating/charging/battery drain issues, so I'm not sure what the problem is and if it's hardware or software. Any advice on what I should do would be appreciated - thanks!

I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.

regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Wouldn't that drain your battery much faster?
Also, I only seem to get the SOD when the phone is charging overnight, and I have a damn screen off profile set to underclock too, not even the lowest frequencies either so it cant be the freeze that that causes sometimes. Tho when it does and I figure out it is frozen asleep, it is usually hot. Might have to either get new battery or replacement. Tho what seems to heat up the most is the area around the camera, so I don't know if the battery or CPU are to blame.

No. Stay Awake only takes effect when your phone is plugged into a power source. Give it a try. I used to get 1 SOD per day. Since i made those changes I've had none in over a month. I posted the same thing in other SOD related threads but no one seems to care.

Thanks regP - I enabled Stay Awake and it seems to help. I've only had one SoD since. My new theory is that it relates to heat (leaving phone in the sun, running too many apps etc.). I've also noticed I don't get an SoD at work, where I get no reception and it's air-conditioned...might be related.

You also need to flash Faux's OC kernel. Even if you dont OC it gets rid of the faulty 300hz frequency that is believed to be part of the problem. Do that along with stay awake and you should not see any more SOD or reboots.

I've noticed I only ever got SOD when using any different kernel than what's in the original ROM. I have been on CM7 since RC1 and have been updating each nightly since and not touched the kernel and have not had a single SOD since, even when charging overnight. Only when I would try Faux kernel or Trinity kernel I would get SOD's.

I dunno then. completely stock for mean means sod and reboots. gingerbreak leak means sod and reboots. stocks + days kernel and stay awake means no sod or reboots. buddy of mine also cured his problems the same way.

For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.

viraj071 said:
For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.
Click to expand...
Click to collapse
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.

I guess I got lucky... never encounter the SOD or Reboot. Running cm nightly 163... I only update nightly when I notice major change only from change log.
Sent from my LG-P999 using XDA App

regP said:
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.
Click to expand...
Click to collapse
So can you suggest any other kernel I should try to stop the sleep of death ?

I have two G2x - Stock Froyo and kernel, manually restart once per day - no SOD or async reboots. Both G2x did suffer from SOD (with or without heat) and reboots. Manual restarts are not as sexy as 3rd party kernels and roms, but it works.
My wife uses her G2x as an alarm clock - she gets in beds, manually shutsdown the G2x, restarts it, plugs into the charger, and it wakes her up in the morning. EVERY DAY.

viraj071 said:
So can you suggest any other kernel I should try to stop the sleep of death ?
Click to expand...
Click to collapse
my sod issues stopped when I enables "stay awake". never used anything but the included kernel of whatever Tom I decide to use.

What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk

noodles2224 said:
What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Our phone at 1 ghz has surpassed the gs2 and 1.2 ghz
Sent from my LG-P999 using XDA App

If missing with software and settings dont work you may just have a bad phone.

regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Thanks for this. I'll be sure to use the "Thanks" button when i have enough posts. I'd been leaving the phone screen on in my pocket (using an alarm clock app) because it would SOD anytime i used the lock button. Working better already.

I keep on getting SODs ONLY when there is a call waiting in the background and this happens only with CM7,MIUI.When I flash the stock gingerbread or even weapons G2x,EaglesBlood ROM the sods that occur during call waiting vanish. Can anyone help me here ? I tried fauxs kernel along with Stay awake and increasing the minimum CPU frequency but failed. Any help will be appreciated.

For the people that SOD occurs on the charger, try another charger (instead of stock LG charger). I tried the Motorola micro USB charger which put out only 550mA (which came with the H730 bluetooth) and the SOD vanished.
Probably over heating with the LG charger which puts out 1000mA

Which kernel am I running?

Hey all, quick question hopefully you all can help me out with. I am currently having terrible battery issues ever since I flashed my phone initially. Terrible as in 6 hours stand-by my phone would be dead.
Anyhow, I am just trying to figure out who's (which) kernel I am running. The kernel version is 2.6.35.7-I997RUXKG3-CL366622 . I have done searches but biggest problem is, threads usually do not post the version number for me to check what I am running.
I am on Infused 2.1.0 (thx GTG!), but battery life has been garbage on all ROMs so I am certain that is not the issue. Can anyone let me know, me love you long time.

iConformed said:
Hey all, quick question hopefully you all can help me out with. I am currently having terrible battery issues ever since I flashed my phone initially. Terrible as in 6 hours stand-by my phone would be dead.
Anyhow, I am just trying to figure out who's (which) kernel I am running. The kernel version is 2.6.35.7-I997RUXKG3-CL366622 . I have done searches but biggest problem is, threads usually do not post the version number for me to check what I am running.
I am on Infused 2.1.0 (thx GTG!), but battery life has been garbage on all ROMs so I am certain that is not the issue. Can anyone let me know, me love you long time.
Click to expand...
Click to collapse
Just the community kernel you can download CPU spy to help with that as well.
Sent from my SAMSUNG-SGH-I997 using xda premium

Maybe u just have a bad battery 6 hours is horrible off stand by.
unless you have some other things running thats eating it up. when you check your battery stats whats eating the most power. Display? Android Proccess?
check that out.

tyshemi said:
Just the community kernel you can download CPU spy to help with that as well.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Thanks for suggesting CPU Spy, looks like I am running Infusion-GB which is what I wanted. So something else is killing my battery

the2rrell said:
Maybe u just have a bad battery 6 hours is horrible off stand by.
unless you have some other things running thats eating it up. when you check your battery stats whats eating the most power. Display? Android Proccess?
check that out.
Click to expand...
Click to collapse
Problem is I bought 2 extra batteries and get exact same life. When I initially bought the phone I would get a days use surprisingly. After that, I have had nothing but god awful drain. I have had almost a dozen android phones and have never encountered such terrible battery life.
I do not have fetch data enabled/gps/widget updates or anything that would normally keep the processor/data churning while in my pocket. Battery use is usually around 40-80% on display, all other categories being minimal (which seems correct).
I'm banging my head on this one, I appreciate you guys replying to my thread

iConformed said:
Thanks for suggesting CPU Spy, looks like I am running Infusion-GB which is what I wanted. So something else is killing my battery
Click to expand...
Click to collapse
I'm running GB 1.0 Kernel and I loose 1% every 3 hrs. on standby.

iConformed said:
Problem is I bought 2 extra batteries and get exact same life. When I initially bought the phone I would get a days use surprisingly. After that, I have had nothing but god awful drain. I have had almost a dozen android phones and have never encountered such terrible battery life.
I do not have fetch data enabled/gps/widget updates or anything that would normally keep the processor/data churning while in my pocket. Battery use is usually around 40-80% on display, all other categories being minimal (which seems correct).
I'm banging my head on this one, I appreciate you guys replying to my thread
Click to expand...
Click to collapse
Send me a pic of your battery screen I settings
Sent from my SAMSUNG-SGH-I997 using xda premium

Ltilt2 said:
I'm running GB 1.0 Kernel and I loose 1% every 3 hrs. on standby.
Click to expand...
Click to collapse
That's solid! I'll try flashing 1.0 then instead of the 1.1 I'm currently on. Are you using this with Infused 2.1.0?

iConformed said:
That's solid! I'll try flashing 1.0 then instead of the 1.1 I'm currently on. Are you using this with Infused 2.1.0?
Click to expand...
Click to collapse
No, I'm running this with Apex 9.2 JVR

tyshemi said:
Send me a pic of your battery screen I settings
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Can't post outside links since I'm newer, sent PM with screen capture

1% per 3 hours standby is FREAKING AWESOME..!!!!
Maybe u have some stray app in the background that's using CPU/whatever it is that's eating up ur battery.
Some subtle things u cud try since u said display is taking up 40-80% of battery:
1. Turning off screen auto rotation, turning it on when needed
2. Turning off auto brightness, turning it on to auto when needed
Use SetCPU like people above pointed out and this would let u see what processor states ur phone is spending most time in.

It sounds like for some people, Infusion 1.1 really flakes out. No clue why. I don't overclock so I don't run it.
It's either Infusion 1.1 flaked out, or if you continue having problems with other kernels, you have a rogue app.
Kernels rarely make any significant difference in battery life unless they're broken.

Entropy512 said:
It sounds like for some people, Infusion 1.1 really flakes out. No clue why. I don't overclock so I don't run it.
It's either Infusion 1.1 flaked out, or if you continue having problems with other kernels, you have a rogue app.
Kernels rarely make any significant difference in battery life unless they're broken.
Click to expand...
Click to collapse
Are there any apps I could get that could monitor packets in/out from what I have installed? I have a lot of apps but most are from trusted sources

Running Infusion-GB 1.1 and Infused 2.1.0: I get 1% drain every 3 hours on standby with radio on (reasonable H+ reception) and 1% every 6 hours on flight mode.
It's most likely a defect in your phone or a configuration issue. You really have to be using your phone for at least 4 or 5 hours (screen-on time) over those 6 hours to cut through battery that fast.

superweapons said:
Running Infusion-GB 1.1 and Infused 2.1.0: I get 1% drain every 3 hours on standby with radio on (reasonable H+ reception) and 1% every 6 hours on flight mode.
It's most likely a defect in your phone or a configuration issue. You really have to be using your phone for at least 4 or 5 hours (screen-on time) over those 6 hours to cut through battery that fast.
Click to expand...
Click to collapse
Dang, I'd think it's a defective unit too except for when I first got it battery was fantastic. But I'm definitely not a heavy user, most my time is at work and I only occassionaly turn it on to check time/sms
Sent from my SAMSUNG-SGH-I997 using xda premium

iConformed said:
Dang, I'd think it's a defective unit too except for when I first got it battery was fantastic. But I'm definitely not a heavy user, most my time is at work and I only occassionaly turn it on to check time/sms
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
when you go to settings > applications > running services - is there anything there that looks like it shouldn't be there?
i know that there is a process that starts with an "o" that is tied into media hub's protected content (DRM) - eats a ton of battery, and isn't really necessary.
it's also possible that you have the SNS service going, but constantly in a restarting state. this seemed to eat a lot of battery also.
otherwise, i'd do what others have suggested and monitor with CPU spy, and i'd also suggest an app called Better Battery Stats (not available in the market - find it here on XDA by a developer named chamonix). this will let you know if you have any wakelocks that are preventing your phone from reaching deep sleep when it is idle.
definitely sounds like you could have a wakelock or 2 interfering with your phone trying to get into those lower frequencies.

wipe battery stats?
Did you try wiping battery stats?

iConformed said:
Are there any apps I could get that could monitor packets in/out from what I have installed? I have a lot of apps but most are from trusted sources
Click to expand...
Click to collapse
Packets in/out isn't what you want unless you also have unusual data usage too. It's wakelock stats you want - look at the BetterBatteryStats app. It used to be only on XDA but apparently it's on the market now.
iphone4 said:
Did you try wiping battery stats?
Click to expand...
Click to collapse
I've said it before, and I'll say it again - Wiping battery stats does NOTHING on our phone. Don't go blindly telling people to do something on our devices just because it worked on another device. The fuel gauge chip on GalaxyS series phones works in a very different way than HTC phones. (Exception: I think the GSII has a more traditional fuel gauge.)

Charging animation issue!!!

Hello, I've been with this problem almost a month and I hope that I can find a solution here. In fact, when my phone is off and I want to charge it by plunging it to a charger, normally, the phone will turn on (but not boot into a ROM) and a charging animation (a big battery with green "juice" in it) will appear. However, when I do the same with by GT-N7100 running JellyBam version jellybam_n7100_jb-PAOKP10-4.1.0-20130116 and kernel 3.0.31-CM-g9d7654c [email protected]#1 Wed Jan 16 08:48:47 CET 2013, it stuck at the screen where there's a loading circle "forever". I do not think it is the ROM problem since at that state the phone is not even booting into the ROM. Also, couple of people on this forum advice me to flash another kernel since that seems to be a kernel problem (but I couldn't see why since the kernel that I am currently using comes with the ROM itself, so I think it should work with the hardware itself). Also, I couldn't find a compatible kernel with the version of the ROM as most of theme included RedPill are out of date. I can upgrade the ROM but it has problem with the newest version. So, I just don't feel comfortable to do the flash right now. Any idea? Do you think it's the ROM problem, the kernel problem or just simply the charging animation that doesn't work properly? I been asking this question multiple times and many researches have been made but nothing and no one can give me a satisfactory answer and here's a link: http://forum.xda-developers.com/showpost.php?p=37923172&postcount=706

Dan Law 001 said:
Hello, I've been with this problem almost a month and I hope that I can find a solution here. In fact, when my phone is off and I want to charge it by plunging it to a charger, normally, the phone will turn on (but not boot into a ROM) and a charging animation (a big battery with green "juice" in it) will appear. However, when I do the same with by GT-N7100 running JellyBam version jellybam_n7100_jb-PAOKP10-4.1.0-20130116 and kernel 3.0.31-CM-g9d7654c [email protected]#1 Wed Jan 16 08:48:47 CET 2013, it stuck at the screen where there's a loading circle "forever". I do not think it is the ROM problem since at that state the phone is not even booting into the ROM. Also, couple of people on this forum advice me to flash another kernel since that seems to be a kernel problem (but I couldn't see why since the kernel that I am currently using comes with the ROM itself, so I think it should work with the hardware itself). Also, I couldn't find a compatible kernel with the version of the ROM as most of theme included RedPill are out of date. I can upgrade the ROM but it has problem with the newest version. So, I just don't feel comfortable to do the flash right now. Any idea? Do you think it's the ROM problem, the kernel problem or just simply the charging animation that doesn't work properly? I been asking this question multiple times and many researches have been made but nothing and no one can give me a satisfactory answer and here's a link: http://forum.xda-developers.com/showpost.php?p=37923172&postcount=706
Click to expand...
Click to collapse
Why are you powering off your phone to charge your battery anyway lol and does it really matter asking as its charging anyway its a kernel issue so its not the ROM its the kernel your on
Sent from my SCH-I500 using Tapatalk 2

It does make a difference between charging your phone when your phone is actually on and charging when it's off. In fact, when it's on and even it's set to low CPU level ( let say 200Mhz), when you connect to your charger, there's still activities in the CPU. Imagine if you leave your phone on and charge it overnight, CPU will work for nothing and leaving the phone off and charge it is a good way to charge your battery in the way that give the CPU some rest. You can not stay awake overnight, your phone can't neither...
Sent from my GT-N7100 using xda premium

Dan Law 001 said:
It does make a difference between charging your phone when your phone is actually on and charging when it's off. In fact, when it's on and even it's set to low CPU level ( let say 200Mhz), when you connect to your charger, there's still activities in the CPU. Imagine if you leave your phone on and charge it overnight, CPU will work for nothing and leaving the phone off and charge it is a good way to charge your battery in the way that give the CPU some rest. You can not stay awake overnight, your phone can't neither...
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Ive never turned my phone off and its been 3yrs I've had this phone (galaxy s1) lol I can only imagine what my CPU is thinking lol
Sent from my SCH-I500 using Tapatalk 2

reply
hope you resolve that problem perfectly

Please help
Dan Law 001 said:
Hello, I've been with this problem almost a month and I hope that I can find a solution here. In fact, when my phone is off and I want to charge it by plunging it to a charger, normally, the phone will turn on (but not boot into a ROM) and a charging animation (a big battery with green "juice" in it) will appear. However, when I do the same with by GT-N7100 running JellyBam version jellybam_n7100_jb-PAOKP10-4.1.0-20130116 and kernel 3.0.31-CM-g9d7654c [email protected]#1 Wed Jan 16 08:48:47 CET 2013, it stuck at the screen where there's a loading circle "forever". I do not think it is the ROM problem since at that state the phone is not even booting into the ROM. Also, couple of people on this forum advice me to flash another kernel since that seems to be a kernel problem (but I couldn't see why since the kernel that I am currently using comes with the ROM itself, so I think it should work with the hardware itself). Also, I couldn't find a compatible kernel with the version of the ROM as most of theme included RedPill are out of date. I can upgrade the ROM but it has problem with the newest version. So, I just don't feel comfortable to do the flash right now. Any idea? Do you think it's the ROM problem, the kernel problem or just simply the charging animation that doesn't work properly? I been asking this question multiple times and many researches have been made but nothing and no one can give me a satisfactory answer and here's a link: http://forum.xda-developers.com/showpost.php?p=37923172&postcount=706
Click to expand...
Click to collapse
My friend. I have ten mtk6575 tablet works good but all of them hanging during powered off charge!!! I need a solution.... please help

+1
:good:
rain_vich said:
My friend. I have ten mtk6575 tablet works good but all of them hanging during powered off charge!!! I need a solution.... please help
Click to expand...
Click to collapse
yes guys im too looking for the solution im on note 2 n7100 but some morons are fine with sayn they do not shut there phones how lame it is .... seriously its bug of kernel and ramdisk ...which already been solved by one of dev at s3 CM bases or AOKP on rom liquidsmooth rom ....
SO STOP TELLING PEOPLE NOT SWITCH OFF MOBILE OR IT DOES NOT MATTER ALL USERS ARE DIFFERENT .....:laugh:
respect

Updates
Was a solution to this ever found?

Found the fix here: https://forum.xda-developers.com/showthread.php?t=2293095&page=3