Random shutdowns? - Vibrant General

Anyone else having issues with the phone shutting itself off at random intervals? It is happening on mine and I have to pull the battery in order to power it back on.
So far have rooted, installed su file browser, and system panel. Only other thing I have done is removed Amazon mp3.
Thanks in advanced, just want to know if I need to exchange my phone or not.
Sent from my SGH-T959 using XDA App

kopykatkiller said:
Anyone else having issues with the phone shutting itself off at random intervals? It is happening on mine and I have to pull the battery in order to power it back on.
So far have rooted, installed su file browser, and system panel. Only other thing I have done is removed Amazon mp3.
Thanks in advanced, just want to know if I need to exchange my phone or not.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
This happen to me yesterday 3 times after the phone's screen was off for more than 10 min
I uninstalled setcpu and it never happened again so far.

Ok maybe it is a setcpu setting that is defaulting wrong. Anyone with setcpu installed that is not experiencing this? If so, what are your settings?
Sent from my SGH-T959 using XDA App

i also had this happen to me w/ setcpu active, i have yet to have it happen w/o setcpu

Happened with setcpu to me to. Removed it no problem since.

Same as everyone else. W/ SetCPU it happens. W/o SetCPU it doesn't.
Just sent the dev a message to let him know of the situation. http://twitter.com/MINUS_Stl/status/18719463969

Are you guys changing the scaling governor? From early reports, the Galaxy S phones can't take ondemand, you have to stick it to conservative.
You can "simulate" ondemand by changing freq step in Advanced to 100%.

Ya know. I did actually change it to ondemand seeing as that's what I always used on my G1. Gonna reinstall and see how we do. Will definitely report back. Thanks.
UPDATE: 1 hour in on 'conservative' and all is good.

I probably have to put a warning or something for Galaxy S for ondemand. It's probably a kernel flaw for that.
For now, it looks like conservative is 100% stable, haven't had reports of crashes on it.

Yeah, I'd say conservative is it. Thanks, bro.

Yes, before the reply about the conservative setting I had messed with it and set to that. Wanted to verify before posting, but as stated that appears that is the key. Thanks guys.
Loving this phone by the way.
Sent from my SGH-T959 using XDA App

coolbho3000 said:
Are you guys changing the scaling governor? From early reports, the Galaxy S phones can't take ondemand, you have to stick it to conservative.
You can "simulate" ondemand by changing freq step in Advanced to 100%.
Click to expand...
Click to collapse
I had SetCPU set to Conservative since I installed it. Yesterday it randomly powered off 6 times. I found this post and deleted SetCPU and am currently using Overclock widget. So far I haven't had it power off.
Has anyone else had this issue while having it set to conservative?

Yes! I changed my charger and it hasn't happened ever since.
Sent from my SGH-T959 using XDA App

i have also noticed that if i set a profile so that the cpu has a max of 400mhz while screen is off it will crash on me randomly. i have to keep it at at least 800mhz. It has just started doing this.
also does anybody know if it is dangerous to run in performance mode at a constant 1000mhz? it makes my phone super fast(obviously) but sounds dangerous making it run at maximum power constantly while the screen is on.

I've never used or installed SetCPU and my phone was shutting down by itself as well and had to do the battery pull to get it back on. I found it to be the "Power saving mode" in the display setting. Ever since I turned it off it has not shut down.

I also experienced this once when I try to install setcpu on my vibrant running bionix-v 1.2. Uninstalled it and it never happend again. =)

Just use the stock kernel.
Sent from my SGH-T959 using XDA App

this used to happen to me all the time so I got a replacement from tmobile but it continued to happen. It finally stopped when i rooted and flashed my phone

This thread is quite old, and while I do appreciate the contributions, it was long ago when this was posted and was dealing with a very early version of the over-clocked kernel. Please let this thread die, so that current ones maintain priority.
Sent from my SGH-T959 using XDA App

at least you guys are getting something. My phone shuts down 1-3 times a day. it is whether its rooted or not, customized rom or not. It just like to go to deep sleep really bad. Hopefully I can exchange it. But i just get my gps fixed, i dont know if i will get a new one with crappy gps.

Related

Hit unlock - screen blinks one and off

So recently here I've been having an issue with my G2. After hitting the unlock button to wake the G2 up, the screen struggles to light up and sometimes it doesn't at all!
When this happens I have to hit the unlock button multiple times just to get the screen to wake itself up, is this happening to anyone else?
Thank god my 3rd G2 is on its way, I should have it tomorrow.
I'm having the same issue also. I think the issue is from setting the CPU down while the screen is off.
Could this be because we've got out G2 oc to 1.42ghz+?
Sent from my T-Mobile G2 using XDA App
My G2 is stock and has this problem.....
Sent from my T-Mobile G2 using XDA App
EdTeach1680 said:
My G2 is stock and has this problem.....
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Well that answers that question lol
Sent from my T-Mobile G2 using XDA App
also have this problem, i usually just open the keyboard.
My stock phone did this...I was under the impression it was some issue with the unlock button. Tmo sent a new one and my replacement hasn't had any issues.
Sent from my T-Mobile G2 using XDA App
This started happening to me when I ran that app that blinked the notification lights when you got a text/voicemail/whatever. (sorry, can't remember what it was called...) When I uninstalled it, it went back to working properly.
[edit - NoLED is the app that was causing it for me.]
Having this same problem, and its extremely frustrating. Sometimes it goes away for a few mins, but most of the time I have to keep pressing the power button till the screen stays on. For some reason, it registers almost every press of the power button as 2. As someone said in one of the above posts, it might have to do with setcpu's screen off profile, but turning that off doesn't solve it for me =(
Sent from my HTC Vision using XDA App
I have this same problem. I was wondering if it was maybe baconbits or setcpu. It never really happened before I got perma root and installed baconbits. Sometimes flipping out the keyboard doesnt even unlock the phone.
I don't know about stock. But this def happened with baconbits for me. I flashed the 2 different sense roms and whenever i applied the baconbits kernel for those roms i had the issues, once i flashed a different kernels I was fine again. So I'll have to pass on bb for now. I hope they can fix this issue because the setcpu settings were great with it.
It happened with my first stock G2. At first I just dealt with it, but then I checked out my wife's G2 (purchased together) and her's worked perfectly. I eventually decided to go though the hassle of getting a replacement from Wirelfy. The replacement's been working fine after perm root & OC.
Install ota and you won't have this problem.
[G2/HTC Vision]
Try removing the setcpu widget from your screen, it seems to have fixed it for me
This was happening to me too. If you have baconbits and setcpu installed, do not use the on demand governor. I changed mine to interactive and my problem went completely away. Conservative works fine as well. On demand was giving me problems though. Even before baconbits on demand was not working properly.
xeduran said:
This was happening to me too. If you have baconbits and setcpu installed, do not use the on demand governor. I changed mine to interactive and my problem went completely away. Conservative works fine as well. On demand was giving me problems though. Even before baconbits on demand was not working properly.
Click to expand...
Click to collapse
Going to give this a try. Do you happen to know what the difference between interactive and on demand are?
Phawkes said:
Going to give this a try. Do you happen to know what the difference between interactive and on demand are?
Click to expand...
Click to collapse
trying this too. The problem seemed to start when I overclocked the cpu. very annoying
Phawkes said:
Going to give this a try. Do you happen to know what the difference between interactive and on demand are?
Click to expand...
Click to collapse
Interactive ramps up to your max speed faster and ramps down from the max slower. So you basically get a little faster performance than ondemand, but at the cost of a little more battery usage. I do not think the battery usage is very significant though.

[Q] Fascinate Won't Wake from Sleep/Screen Off

My brother and I both got Fascinates this month. Both are rooted, but only mine is upgraded to DJ05. We are both loving the phone except, both of us have a problem where the screen/phone will not wake up from sleep sometimes. It will just show a black screen, it even happened while talking on the phone today, the screen didn't wake when I got off the phone. I've done a few searches and on some other phones people suggested setting SetCP to at least one higher then the minimum when it's in screen off mode, but I just tried that and had the same issue 5 minutes later. With all the development going on, I'm hoping that someone may have found a fix for it. Does anyone else have this problem or know of a solution? I apologize if there is another thread in the fascinate forum about this, I did a few searches, but didn't see anything.
Thanks,
Ryan
You could help yourself by stating what rom version and what specific kernel you are using. And if you are using a task killer and or power managment app.
good day.
Sorry if I wasn't clear enough. We are both rooted, but my brother is otherwise running stock. No task manager, just Setcpu. I upgraded to DJ05 and installed JTs Superclean w/non voodoo and rom. But I wouldn't think that'd be the problem considering he's running stock. Maybe it's setcpu? If so is their another comparable manager for battery life that someone might suggest, I can see if that fixes it?
Setcpu offers no benefit to devices using a stock kernel only good for over clocked kernels. If the problem at hand didn't start until installing setcpu, then you have your answer. I myself do not use any power management apps so I can't speak for them.
good day.
Did you by any chance install something that adjusts the brightness of your screen?
If your running Setcpu and your having problems waking up the phone, are you running a profile for the screen off? You can't run profiles on Sammy phones, they don't like it.
No, no brightness apps.
Yes, I was running a profile for screen off and stuff. That was the whole point of Setcpu, I thought, so you could reduce it when the battery started getting low and the phone wasn't being used. Thanks for the info, I uninstalled it. I guess that's the problem. Only time will tell though. Do you know of any other reputable apps that would be similar to Setcpu?
Why not try geeks last kernel? I believe it was uv and should help battery life if that's what you're going for.
I would, but people have had some issues with them from what I hear, besides he's no longer developing them or supporting them, so sooner or later I'd be changing anyway. Maybe I'll check out juice defender.
You can keep setcpu, just don't use any profiles lol and keep it on conservative
Sent from my SCH-I500 using XDA App
Does it actually do anything for you though to help save battery life without the profiles?
Just because he isn't deving for the sf doesnt mean that his kernels are worse than the stock one...I use adryn's 12/17 test 2 and get amazing battery life..14 hrs at like 60-65% but it's voodoo and you will prob not want that.
setcpu will change the ramp up/ramp down speed...more time at max when you need it more time at min when you dont...i don't think it will help nearly as much as proper kernel

Epic help needed!!

So i have been going crazy! I started with ACS Frozen 1.1.0 and it was suffering from the "not waking up" problem. I assumed it was the overclocking so i went through all the crap with playing with the volts and settings. Well i never got the problem to go away so i switched roms to 1.1.1 (I think) and i got the same thing! So i wend to Bonsai v4.1.1 then to Emerald envy. Now im on SRF 1.2 final. All do the same thing!! The phone will go to sleep and not wake up with out a battery pull. Some roms make it take longer than others but at the most i get like 5-6hours before the lock screen (on 1.1.0). On this 1.2final i am getting almost immediate shut down!!! Non of them work!! I thought because the 1.2 final was pretty much a stock kernel i would not have a problem... i was wrong. The phone other wise runs great! So should i go back to stock? any suggestions??
Does it start doing it right after you flash a rom? Or does happen after you've installed all your favorite apps?
Sent from my SPH-D700 using Tapatalk
Either stop using SetCPU's ondemand setting and switch it to conservative, or just don't use the application at all.
The minimum for your phone seems to be higher than 100mhz, so adjust accordingly. Just remember, the ondemand setting doesn't maintain the minimum you set, so that's why you have to use conservative.
Or switch kernels and that might do it for you as well. Genocide kernel is a popular choice, but even that dev suggests using conservative, not ondemand, even though it does maintain the minimum when you set it on his newest kernel.
Hope that made sense.
I dont know if it happens before or after.. i always set it up... ill try flashing it now and not setting anything up. But if i cant use my apps then what the point?
I stooped over clocking it about 4 flashes ago. The last few times i did not even let voltage control get root access to see if that was the problem and is still freeze's! Also i read up and tried every configuration i could for overclocking before giving up on it.
Maybe its my apps? Or awd launcher? But that seems doubtful to me.
Anybody point me in the direction for returning it back to complete stock? If running it for some time with non of my apps does not work then i am going back to stock.
This will get you back to stock.
http://forum.xda-developers.com/showthread.php?t=1052813
I would try flashing a rom again without apps then as things look good start installing stuff. For me there was a battery widget that would lock up my nook color and on my Epic I had music stutters.
Sent from my SPH-D700 using Tapatalk
I flashed the 1.2final rom and have been adding 1 app every 4 hours. I have not has any freezing. Hard to believe a app would crash my phone... I will let you guys know what app ends up crashing it.
But now that I know its a app I will try over clocking again... and recommendations for a kernel for this frozen 1.2final rom?
Sent from my SPH-D700 using XDA App
Using setcpu?
Sent from my Epic 4G via Tapatalk
Some phones can't handle certain clock speeds. Sounds like your CPU may be biting the dust, or just got the bad end of the silicon.
Sent from my SPH-D700 using XDA Premium App
Well the phone has worked all night! I loaded youmail and that seems to be what crashed it. But now i am thinking it was not a app at all... it was my backup. When it crashed after loading youmail i reinstalled the rom and just loaded app.. I did not use Mybackup pro to load my data. The phone seems fine as of right now. I have not overclocked it once yet. I hope it was my backed up data because at this point i just want a phone that does not need to be reloaded every few hours.
hayzooos said:
Either stop using SetCPU's ondemand setting and switch it to conservative, or just don't use the application at all.
The minimum for your phone seems to be higher than 100mhz, so adjust accordingly. Just remember, the ondemand setting doesn't maintain the minimum you set, so that's why you have to use conservative.
Or switch kernels and that might do it for you as well. Genocide kernel is a popular choice, but even that dev suggests using conservative, not ondemand, even though it does maintain the minimum when you set it on his newest kernel.
Hope that made sense.
Click to expand...
Click to collapse
NissanNick said:
Well the phone has worked all night! I loaded youmail and that seems to be what crashed it. But now i am thinking it was not a app at all... it was my backup. When it crashed after loading youmail i reinstalled the rom and just loaded app.. I did not use Mybackup pro to load my data. The phone seems fine as of right now. I have not overclocked it once yet. I hope it was my backed up data because at this point i just want a phone that does not need to be reloaded every few hours.
Click to expand...
Click to collapse
I wasn't saying don't use any apps, I was saying not to use SetCPU with ondemand. Maybe it was youmail, maybe you just had some corrupt data. Who really knows.
Google doesn't go through the verification/testing process like Apple does, so you'll get some rogue apps out there that just plain suck, and can cause issues with your phone. Maybe that was the case.
Either way, it sounds like you got it pretty much figured out. If I ever restore a backup (not a nandroid), I usually only put data back to games, not any other apps, as there's no real need. Maybe for an email app to keep the settings, but even that's not hard to set back up.

Gingerbread - high CPU utlization by "System"

On my Bell Atrix, I've found that in every build of Gingerbread I've tried (both the AT&T and Orange France versions), my CPU never cycles down from 1 GHz. On Froyo, it would change depending on usage, but with Gingerbread, it's always pegged on max. According to SystemPanel app, approximately 40% of the CPU is constantly utilized by "System" non-stop. This was not the case with Froyo.
I wonder if this ties in with the entry in the battery usage list which shows X as being among the top two users of battery. The CPU total for X is almost the same as the time the phone has been awake.
Has anyone else experienced this? I know there have been a lot of people complaining about the poor battery life on Gingerbread (and I'm one of them), but now I'm wondering if it has to do with "Service" and the mysterious X constantly using the CPU in the background.
Do u have any OC kernels in there or just stock GB?
Sent from my MB860 using XDA Premium App
I've used the stock kernels, the original ones with the RAM fix, and edgen's overclocked kernel and they all behave exactly the same.
frelnik said:
I've used the stock kernels, the original ones with the RAM fix, and edgen's overclocked kernel and they all behave exactly the same.
Click to expand...
Click to collapse
I had the same problem, when you delete all data from fastboot (fastboot-w), install 2.3.4 gingerbread returned and the battery lasts me about the same as the stock 2.1.1 FR. (taking into account that spends more battery 2.3.4). now I have the Orange Radio 2.3.4 with kernel faux123 0.100.00R. sorry for my English
I've run fastboot -w, and used CWM to clear data/cache both before installing ROMs and after installing ROMs, and none of that made a difference. BUT last night I installed kennethpenn's Beta 4, and for the first time, my CPU frequencies were properly scaling, and System was not taking up 40%. Since then, I've wiped data/cache and tried different kernels and different ROMs, and all of them are working. It's almost as though kennethpenn's ROM installed something that wasn't there previously and is persisting through wipes, and ROM/kernel installations. Is that even possible?
freeze your bloat.
use setcpu for system profiles.
problem solved.
For me it was X server running in background and taking 40-50% of cpu. I had to move it because there was no other solution.
Magnetox said:
freeze your bloat.
use setcpu for system profiles.
problem solved.
Click to expand...
Click to collapse
No.
I didn't have to do this with the Froyo builds and I still had excellent battery life (2-3 days). if I go back to 1.8.3 I still have excellent battery life. And that's with Corporate Sync, Gmail push, and Twitter and Facebook in Blur's Social Networking.
There is something in the leaked Gingerbread roms that eats batteries for lunch.
stewartsoda said:
No.
I didn't have to do this with the Froyo builds and I still had excellent battery life (2-3 days). if I go back to 1.8.3 I still have excellent battery life. And that's with Corporate Sync, Gmail push, and Twitter and Facebook in Blur's Social Networking.
There is something in the leaked Gingerbread roms that eats batteries for lunch.
Click to expand...
Click to collapse
You're right. This wasn't in 1.83. But if you freeze your bloat and use setcpu profiles, you will get 2 days of use from your phone.
Sent from my MB860 using Tapatalk
frelnik said:
On my Bell Atrix, I've found that in every build of Gingerbread I've tried (both the AT&T and Orange France versions), my CPU never cycles down from 1 GHz. On Froyo, it would change depending on usage, but with Gingerbread, it's always pegged on max. According to SystemPanel app, approximately 40% of the CPU is constantly utilized by "System" non-stop. This was not the case with Froyo.
I wonder if this ties in with the entry in the battery usage list which shows X as being among the top two users of battery. The CPU total for X is almost the same as the time the phone has been awake.
Has anyone else experienced this? I know there have been a lot of people complaining about the poor battery life on Gingerbread (and I'm one of them), but now I'm wondering if it has to do with "Service" and the mysterious X constantly using the CPU in the background.
Click to expand...
Click to collapse
I'm also on a bell Atrix with 2.3.4 Orange. I've actually never seen this X process that some people talk about? I don't see it anywhere in my battery usage. My top 2 are almost always display and phone idle. I wonder whether you guys are using a setting or app that I'm not. That said, I'm not getting great battery life either. 10 hours and my phone dies.
I'm also using setcpu with a screen off profile. Haven't decided yet whether it helps or not.
Sent from my MB860 using XDA Premium App
maledyris said:
I'm also on a bell Atrix with 2.3.4 Orange. I've actually never seen this X process that some people talk about? I don't see it anywhere in my battery usage. My top 2 are almost always display and phone idle. I wonder whether you guys are using a setting or app that I'm not. That said, I'm not getting great battery life either. 10 hours and my phone dies.
I'm also using setcpu with a screen off profile. Haven't decided yet whether it helps or not.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Freeze the bloat on your phone and use edgan's international kernel. I'm getting 24-30 hours on my bell atrix on 2.3.4 orange.
jaysonsantos said:
For me it was X server running in background and taking 40-50% of cpu. I had to move it because there was no other solution.
Click to expand...
Click to collapse
That's pretty much what I was getting as well. X was always second to display in terms of battery usage, and it seemed to be using the CPU constantly whenever the phone was awake. I'm not sure what to make of it, what with some people seeing it and some people not. All I know is that after I tried kennethpenn's ROM, X disappeared, and my CPU seems not to be occupied nonstop. Since then I've wiped my phone and installed the Ninja ROM and faux's stock international kernel, and my phone continues to function without X eating up the CPU. This was the exactly same setup that, prior to kennethpenn's ROM, was suffering from constant high CPU usage. No idea what changed it, but now things *seem* to be operating normally and my battery is much improved.
I solved it renaming "/etc/X11" to "/etc/X11.bkp". So... X process magically disappeared!!!
Anyone notice that if you throttle CPU down, to 1mhz then run your finger back and forth on the screen it will still throttle to 1.3mhz? Or is it just me?
Edit: using setcpu
Sent from my MB860 using XDA App
Sass86 said:
Anyone notice that if you throttle CPU down, to 1mhz then run your finger back and forth on the screen it will still throttle to 1.3mhz? Or is it just me?
Edit: using setcpu
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Open setcpu. Go to profiles. Then quit and go back in to setcpu and it should stick. Don't know why. I'm going to try a profile to keep it at 1100 like temp over 0. Who knows.
Sent from my MB860 using Tapatalk
Funny. I opened setcpu and it was back at 1300, so my solution is moot. I did just set a profile if battery is below 101% then scale to 1100 low priority (40)
Sent from my MB860 using Tapatalk
I don't know what the deal is. Set cpu tells me the clock is set to 1100. Which matches cm7 settings which also matches system panel. But watching the cpu speed in setcpu it will go to 1300. So yeah. Back to the drawing board.
Sent from my MB860 using Tapatalk
Bear with me. Not spamming. Here's my deal. Most people's governors are greyed out. Mine is not. Tasker, system monitor show it which then allows setcpu to show it. If I'm on powersave the clock will not stick to my setting of 1100. If I set it to performance. It sticks. Any one confirm or deny?
Sent from my MB860 using Tapatalk
I was seeing the same thing until I made a profile for Battery < 101 max at 1000 and a priority of 80%. Now every time I open setcpu he cpu maxes as 1000.
Indeed.. atrix with stock kernel runs all the time at high freqs..
with faux kernel, is at lowest value, so we save battery.
does it have a governor enabled by default or something?
whatever he did, its pretty good!
Imagine that with undervolt..

note on steriods???

i just noticed this morning after unplugging my note that even though my note is going into deep sleep the battery drain is still way too much as compared to the previous day...
i checked cpuspy and at first didn't register anything odd except that it goes into deep sleep.. after a second glance only then i realized that instead of running at 200mhz my note was running at 1000mhz during charge..
has anyone here experienced this before?? although i noticed that it seems to be a lot snappier now
i just can't help but worry what lasting damage it may be doing to the processor... and the fact that even though it goes into deep sleep i'm losing about 5% of juice for every 15-20 mins.
see screenshots below. the first was when i unplugged it from the charger and the second... after going to deep sleep
see screenshots
sorry forgot to attach screenshots
scarlet_sg said:
i just noticed this morning after unplugging my note that even though my note is going into deep sleep the battery drain is still way too much as compared to the previous day...
i checked cpuspy and at first didn't register anything odd except that it goes into deep sleep.. after a second glance only then i realized that instead of running at 200mhz my note was running at 1000mhz during charge..
has anyone here experienced this before?? although i noticed that it seems to be a lot snappier now
i just can't help but worry what lasting damage it may be doing to the processor... and the fact that even though it goes into deep sleep i'm losing about 5% of juice for every 15-20 mins.
see screenshots below. the first was when i unplugged it from the charger and the second... after going to deep sleep
Click to expand...
Click to collapse
Try restarting and see it is softens up
Sent from my GT-N7000 using xda premium
tried it... even did a hard reset by pulling battery out... still the same...
now clueless on what next...
See what processes are running. And kill some unneccessary ones?
Sent from my GT-N7000 using XDA
scarlet_sg said:
tried it... even did a hard reset by pulling battery out... still the same...
now clueless on what next...
Click to expand...
Click to collapse
ANy new apps that u installed recently ?
Normally , rogue process is going to call an abnormal battery drain ,,,download some sort of process,app moniter and see which process is running and taking most of the CPU time......My guess is that it has to be one of the apps that you have installed or started which is causing this
That was what I thought initially but I don't remember installing anything these past few days as I just froze a few bloatware and was monitoring the device for any issues.
The last thing I remember changing was some setting under the development concerning background process.
Hmmmn. Maybe I'll put it back and see.
Really appreciate the help guys. I'll keep you updated.
Sent from my GT-N7000 using XDA
Kernel and rom version pleeez
Sent from my GT-N7000 using Tapatalk 2
scarlet_sg said:
The last thing I remember changing was some setting under the development concerning background process.
Hmmmn. Maybe I'll put it back and see.
Click to expand...
Click to collapse
this may be the reason - afair this setting kills each process after you leave it, so in readily you might have ended with a constant loop of processes being closed and then restarted by system
Sent from my GT-N7000 using xda premium
i unchecked the limiting of background process but still the same... cpu is still running at 1000mhz most of the time
i did a hard reset by turning off and pulling the battery for a few minutes... still the same although the note still goes into deep sleep but hardly uses other cpu speeds except for 1000mhz...
i tried freezing some of my apps and games, those which i suspect might have required 1000mhz to run but still the same...
i guess i'll just have to wait and see for a little while if this changes...
i'm now thinking of reverting back to GB... since the battery drain for ICS is such a let down and with this problem... i'll give it a couple more days
what ROM are you running?
anyway something in the governor seems to have changed ,your case seems to be a performance governor.
try installing set cpu and set minimum to 200 ,max to 1400 ,and the governor to "on demand"
should fix things for you
IM on stock Ics lp9. I haven't root yet after I upgraded ota.
Set CPU requires root ain't it?
Sent from my GT-N7000 using XDA
scarlet_sg said:
IM on stock Ics lp9. I haven't root yet after I upgraded ota.
Set CPU requires root ain't it?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
yes it does ,but if you're not rooted then the governor couldn't possibly have changed by you !!
could it be a bug in lp9? I heard that ICS have some battery issues
how long were you running LP9 before noticing this issue?
Well, havent heard it from that rom. Bring it back
Sent from my GT-N7000 using Tapatalk 2
it might be the fault of some rogue app running in background, did you check with betterbatterystats?
Sent from my GT-N7000 using xda premium
I was using lp9 for about 2 Weeks after I started noticing the CPU usage
Couldn't find a fix so I reverted back to rooted lc2 GB
With all the issues with Ics - battery drain, fc's and mmc bug and now this CPU overclocking felt it wasn't worth it.
Now the note is sleeping like a baby. Battery is back to its efficient self. I'm getting 3 days on one full charge.
Will just wait for an update on official Ics.
Appreciate all the help guys.
Sent from my GT-N7000 using XDA

Categories

Resources