Hi. I'm using a rooted Samsung Galaxy S2 i9100G, running on stock Jelly Bean 4.1.2 with Blazing Kernel v10 by Ryuinferno.
Ever since i rooted my phone, my phone wont respond to any buttons, but it is definitely running because it is hot and the battery is drained at a fast rate. The screen remained off and i had to do a battery pull to restart the phone. But I have been pulling out the battery way too many times and i am getting tired of it. I have tried installing wakelock detector to see if i can find out the cause of the problem. But I had to do a battery pull to turn on my screen, and by doing that the stats are all gone. Is there any suggested solution that i can do? I dont want to do a factory reset on my device. I suspect that there is a problem with my Trickster MOD or SetCPU profiles. These are my profiles:-
1. Screen off
CPU 600 - 300, Governor lulzactive
Priority 70
2. Charging AC
CPU 1200 - 300, Governor smartassV2
Priority 60
3. Battery <= 20%
CPU 600 - 300, Governor lulzactive
Priority 50
4. Battery <= 40%
CPU 1008 - 300, Governor lulzactive
Priority 40
5. If all of these are true(Screen on and Screen unlocked)
CPU 1008 - 300, Governor smartassv2
Priority 30
Is there anybody out there who can help me?
thanks in advance
Turn off phone by pressing power button for 10 seconds . battery stats and wake locks stay in RAM and because they have battery RAM remains almost intact and nothing disappear so you can check them when phone is on
Sent from my GT-I9100 using xda premium
JssCheonGz said:
Hi. I'm using a rooted Samsung Galaxy S2 i9100G, running on stock Jelly Bean 4.1.2 with Blazing Kernel v10 by Ryuinferno.
Ever since i rooted my phone, my phone wont respond to any buttons, but it is definitely running because it is hot and the battery is drained at a fast rate. The screen remained off and i had to do a battery pull to restart the phone. But I have been pulling out the battery way too many times and i am getting tired of it. I have tried installing wakelock detector to see if i can find out the cause of the problem. But I had to do a battery pull to turn on my screen, and by doing that the stats are all gone. Is there any suggested solution that i can do? I dont want to do a factory reset on my device. I suspect that there is a problem with my Trickster MOD or SetCPU profiles. These are my profiles:-
1. Screen off
CPU 600 - 300, Governor lulzactive
Priority 70
2. Charging AC
CPU 1200 - 300, Governor smartassV2
Priority 60
3. Battery <= 20%
CPU 600 - 300, Governor lulzactive
Priority 50
4. Battery <= 40%
CPU 1008 - 300, Governor lulzactive
Priority 40
5. If all of these are true(Screen on and Screen unlocked)
CPU 1008 - 300, Governor smartassv2
Priority 30
Is there anybody out there who can help me?
thanks in advance
Click to expand...
Click to collapse
Yeah, your phone is experiencing SOD's (screen of death). It can happen for a couple of reasons. You could be looking down the right path for your profiles, if no one else is experiencing them with the same kernel as you. It can be a kernel bug, but if no one else is experiencing the same issues it'll be your setup. Start reading up on what causes a SOD in terms of governor profiles, there are certain do's and don'ts. As I don't use the same governors (or kernel) as you, I can't pinpoint your problem. Droidphile (xda user) has made a great post explaining 'kernel governors, i/o schedulers, CPU tweaks' or something to that effect. Good place to start reading
Hopper8 said:
Yeah, your phone is experiencing SOD's (screen of death). It can happen for a couple of reasons. You could be looking down the right path for your profiles, if no one else is experiencing them with the same kernel as you. It can be a kernel bug, but if no one else is experiencing the same issues it'll be your setup. Start reading up on what causes a SOD in terms of governor profiles, there are certain do's and don'ts. As I don't use the same governors (or kernel) as you, I can't pinpoint your problem. Droidphile (xda user) has made a great post explaining 'kernel governors, i/o schedulers, CPU tweaks' or something to that effect. Good place to start reading
Click to expand...
Click to collapse
thanks for pinpointing what problem i am having. i looked up to several problems and i thought my phone froze or some sort. thanks :victory:
Hopper8 said:
Yeah, your phone is experiencing SOD's (screen of death). It can happen for a couple of reasons. You could be looking down the right path for your profiles, if no one else is experiencing them with the same kernel as you. It can be a kernel bug, but if no one else is experiencing the same issues it'll be your setup. Start reading up on what causes a SOD in terms of governor profiles, there are certain do's and don'ts. As I don't use the same governors (or kernel) as you, I can't pinpoint your problem. Droidphile (xda user) has made a great post explaining 'kernel governors, i/o schedulers, CPU tweaks' or something to that effect. Good place to start reading
Click to expand...
Click to collapse
i think i found out the cause of the problem. Apparently stock rom do not provide some kind of code to prevent SOD. It seems that i have to use AOSP rom or revert back to stock kernel. Is there any kernel that supports stock rom that u can recommend to me??
Hum...stock ROMs shouldn't suffer from SOD, so wipe it all out (or even nuke it) and don't worry, it's not gonna happen again
Sent from the little guy
gastonw said:
Hum...stock ROMs shouldn't suffer from SOD, so wipe it all out (or even nuke it) and don't worry, it's not gonna happen again
Sent from the little guy
Click to expand...
Click to collapse
Hmm that's what I thought too. But before I rooted mine, after the update to 4.1.2, I was having a SOD on average once every two days over the course of a month after the update. No idea why, but it's part of the reason why I rooted it. Tried a factory reset and was still having problems. Didn't nuke it as that requires root and I figured I may as well run a custom ROM as well if I was rooting.
Were you on custom before the JB jump?
Nevermind, you weren't even rooted.
Dalvik might be the key here.
Sent from my GT-I9100 using xda app-developers app
gastonw said:
Were you on custom before the JB jump?
Nevermind, you weren't even rooted.
Dalvik might be the key here.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
i rooted my phone after the JB jump to get a custom kernel
Hopper8 said:
Hmm that's what I thought too. But before I rooted mine, after the update to 4.1.2, I was having a SOD on average once every two days over the course of a month after the update. No idea why, but it's part of the reason why I rooted it. Tried a factory reset and was still having problems. Didn't nuke it as that requires root and I figured I may as well run a custom ROM as well if I was rooting.
Click to expand...
Click to collapse
gastonw said:
Hum...stock ROMs shouldn't suffer from SOD, so wipe it all out (or even nuke it) and don't worry, it's not gonna happen again
Sent from the little guy
Click to expand...
Click to collapse
i think it might be caused by the kernel and the stock rom :/
JssCheonGz said:
i think it might be caused by the kernel and the stock rom :/
Click to expand...
Click to collapse
Theoretically, stock kernel and ROM is the most stable combination you could have. That's what Gaston was saying, and I agree. The only problem is that in your case (and mine previously), it wasn't. You can try tweaking your profiles, but you already have minimum frequency set to 300 MHz. You don't have 100MHz enabled do you?
Hopper8 said:
Theoretically, stock kernel and ROM is the most stable combination you could have. That's what Gaston was saying, and I agree. The only problem is that in your case (and mine previously), it wasn't. You can try tweaking your profiles, but you already have minimum frequency set to 300 MHz. You don't have 100MHz enabled do you?
Click to expand...
Click to collapse
i had to agree that stock kernel and rom is stable. but it is so laggy at times and it is frustrating. TT. my minimum frequency is 300MHz. i had 4 SOD today ._. so annoying
JssCheonGz said:
my minimum frequency is 300MHz. i had 4 SOD today ._. so annoying
Click to expand...
Click to collapse
Make a nandroid backup, then do a total wipe, flash the kernel and and see if it still occurs before setting your profiles. Then when you're done testing you can at least restore the backup, and you'll know if the SOD's are caused by your profiles or the kernel not playing nice.
Hopper8 said:
Make a nandroid backup, then do a total wipe, flash the kernel and and see if it still occurs before setting your profiles. Then when you're done testing you can at least restore the backup, and you'll know if the SOD's are caused by your profiles or the kernel not playing nice.
Click to expand...
Click to collapse
was doing backup for my phone last night, and i havent do any wipe. no SOD today. so weird ._.
JssCheonGz said:
was doing backup for my phone last night, and i havent do any wipe. no SOD today. so weird ._.
Click to expand...
Click to collapse
Hopper8 said:
Make a nandroid backup, then do a total wipe, flash the kernel and and see if it still occurs before setting your profiles. Then when you're done testing you can at least restore the backup, and you'll know if the SOD's are caused by your profiles or the kernel not playing nice.
Click to expand...
Click to collapse
I did a nandroid backup, full wipe, and tried using Stock Rom + Blazing Kernel without having SetCPU. Had 4 SOD. Then yesterday night I did a full wipe again, and this time using Stock Rom and Stock Kernel 4.1.2 without SetCPU and had 3 SOD. What to do T.T the warranty period ended too T.T
gastonw said:
Hum...stock ROMs shouldn't suffer from SOD, so wipe it all out (or even nuke it) and don't worry, it's not gonna happen again
Sent from the little guy
Click to expand...
Click to collapse
did a full wipe, and i am still suffering from SOD T.T with stock rom and stock kernel
Hopper8 said:
Make a nandroid backup, then do a total wipe, flash the kernel and and see if it still occurs before setting your profiles. Then when you're done testing you can at least restore the backup, and you'll know if the SOD's are caused by your profiles or the kernel not playing nice.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The battery stats from settings today :/
JssCheonGz said:
did a full wipe, and i am still suffering from SOD T.T with stock rom and stock kernel
Click to expand...
Click to collapse
That is unlucky indeed, although I have seen it once before. (It was my mum's brand new S2, second day since she'd bought it and got a SOD. Rather than let me troubleshoot it, she returned it for a new one.) Have you tried running a custom ROM with its stock kernel? Something that's stable, say RootBox 4.0. That was rock solid for me.
You're mucking around with non-standard CPU settings/profiles/etc & you're honestly wondering why you're getting SOD's ? Set everything back to stock frequencies/settings & start again, only make changes very slowly/incrementally (25MHz at a time, for example) until you find out what works with the CPU in your phone (this is often quite variable from device to device). Do this for every phone state given you've been running 5 different profiles. Don't try to work out what works with or set all profiles at once; start with screen on/unlocked, (I.E when you're using the phone) get that right, then do the others in turn.
There's been a bit of overthinking going on thus far methinks.
MistahBungle said:
You're mucking around with non-standard CPU settings/profiles/etc & you're honestly wondering why you're getting SOD's ? Set everything back to stock frequencies/settings & start again, only make changes very slowly/incrementally (25MHz at a time, for example) until you find out what works with the CPU in your phone (this is often quite variable from device to device). Do this for every phone state given you've been running 5 different profiles. Don't try to work out what works with or set all profiles at once; start with screen on/unlocked, (I.E when you're using the phone) get that right, then do the others in turn.
There's been a bit of overthinking going on thus far methinks.
Click to expand...
Click to collapse
At first I thought there might be an error in the way i set my CPU or the Kernel. I did a nandroid backup, and i did a fullwipe. At that time, my phone is running on stock rom 4.1.2 and Blazing Kernel. I did not install SetCPU so I dont think i tweaked the settings for the CPU settings, but Im still getting SODs. Then I tried doing a full wipe again, this time using stock rom stock kernel. and i am still getting it. Since it is all stock i dont think there is any way i adjusted the frequencies......
Related
I'm running prebeta 4 - and just wondering if anyone is having there phone heat up on them? It only takes about 5-10 minutes of use and it gets pretty warm? I have gone into the performance settings and lowered the cpu speed to 913mhz? That seemed to help a tad, but it could just be in my head.
Another thing i noticed is that copy and paste doesn't work. Is anyone else able to solve that issue?
Thanks!
jake.perkinsr said:
I'm running prebeta 4 - and just wondering if anyone is having there phone heat up on them? It only takes about 5-10 minutes of use and it gets pretty warm? I have gone into the performance settings and lowered the cpu speed to 913mhz? That seemed to help a tad, but it could just be in my head.
Another thing i noticed is that copy and paste doesn't work. Is anyone else able to solve that issue?
Thanks!
Click to expand...
Click to collapse
It does heat up a bit. You may want to try undervolting your phone. I've noticed that it doesn't get as warm. If you do a search there are a few threads on the topic. No C+P problems for me.
I installed CM7 yesterday too. Haven't had any issues with heating up yet. Idle is around 32C. Performance wise , this is the best ! as enomai said, you can under volt your phone by going to settings>cm settings>performance>"watch out for the dragons ahead! >CPU settings>change the min and max cpu frequency to your desire MHz.
You might need to reflash and wipe everything. Or find out what rogue app you got going.
I voided my warranty and your mum.
had a force close and notice that caused it to overheat, checked set cpu and noticed it sitting at 1300 constantly and not scaling or dropping at all.. had to reboot for it to cool down.
tonesy said:
had a force close and notice that caused it to overheat, checked set cpu and noticed it sitting at 1300 constantly and not scaling or dropping at all.. had to reboot for it to cool down.
Click to expand...
Click to collapse
AAhhh ok. Well in that case I would say if it's not a piece of software * like for example do you have TWO overclock softwares installed, like setcpu AND another?*, then it's probably a kernel problem. I would uninstall whatever software you have to overclock, reboot into fastboot, do a
fastboot erase boot
fastboot reboot
, and then reboot into recovery and try flashing the kernel again. wipe cache, see if this works.
Do I need to get Setcpu to undervolt my phone? I'm a bit nervous that the heat will damage my phone. I really love cm7, but I need it to not overheat. This never happened when I ran stock? What do you guys think?
Sent from my MB860 using XDA App
I havnt been running into any overheating issues at all, actually been running cooler on CM7. Im running Faux's 1.3 OC kernal instead of the kernal that came with it though. Try reflashing the kernal or flashing another one of Faux's kernals for CM7. I would definitely install Setcpu so u can moiter the battery and processer temps. Set up a few profiles and try undervolting some.
Hi, i have this problem with my phone that whenever it
is on deep sleep with charger off the screen will not turn on afterwards but the phone itself I think is still on
I am using the latest ics 4.0.3 lpq with the latest siyah kernel
lordemil said:
Hi, i have this problem with my phone that whenever it
is on deep sleep with charger off the screen will not turn on afterwards but the phone itself I think is still on
I am using the latest ics 4.0.3 lpq with the latest siyah kernel
Click to expand...
Click to collapse
Known as the "Sleep of Death" (SOD). I see you're on Siyah. Are you overclocking or undervolting? Common cause is using undervolt values that are too low. If you are undervolting, you may need to bump your voltages up a bit. You can also change your governer to see if that helps.
ctomgee said:
Known as the "Sleep of Death" (SOD). I see you're on Siyah. Are you overclocking or undervolting? Common cause is using undervolt values that are too low. If you are undervolting, you may need to bump your voltages up a bit. You can also change your governer to see if that helps.
Click to expand...
Click to collapse
i have not touch an voltage settings, i only changed the governor to "lulzactive" with SetCpu
but the problem only started to occur very frequently like at least twice a day since i updated to ICS (but the first few days were fine, only this 3 days it started). when i was using GB, i had this problem only 2 times.
lordemil said:
i have not touch an voltage settings, i only changed the governor to "lulzactive" with SetCpu
but the problem only started to occur very frequently like at least twice a day since i updated to ICS (but the first few days were fine, only this 3 days it started). when i was using GB, i had this problem only 2 times.
Click to expand...
Click to collapse
Hmm... try a different governor and see if the problem persists, or reduces in frequency.
ctomgee said:
Hmm... try a different governor and see if the problem persists, or reduces in frequency.
Click to expand...
Click to collapse
alright thanks, i will get back at you
lordemil said:
alright thanks, i will get back at you
Click to expand...
Click to collapse
Just post here. Not sure how much more help I can be though. If you haven't messed with clock speed or voltages, then governor is about the last idea I've got. If that doesn't fix it, try going back to a stock kernel.
Then I'm all out of ideas.
ctomgee said:
Just post here. Not sure how much more help I can be though. If you haven't messed with clock speed or voltages, then governor is about the last idea I've got. If that doesn't fix it, try going back to a stock kernel.
Then I'm all out of ideas.
Click to expand...
Click to collapse
thanks... i will post back in a few days
it looks like after i updated the kernel again, the problem went away
thanks for your help ctomgee
lordemil said:
it looks like after i updated the kernel again, the problem went away
thanks for your help ctomgee
Click to expand...
Click to collapse
No problem. Curious tho, when you updated to ICS, did you also update Siyah to 3.0 or higher? GokhanMoral compiled a v3 for ICS.
Happens sometimes on cm9 but pressing home key for 5 secs walked the phone up
ctomgee said:
No problem. Curious tho, when you updated to ICS, did you also update Siyah to 3.0 or higher? GokhanMoral compiled a v3 for ICS.
Click to expand...
Click to collapse
sorry for late reply... yea i did, it was probably just a bug in the kernel or something but it looks like the problem is gone now
sahibunlimited said:
Happens sometimes on cm9 but pressing home key for 5 secs walked the phone up
Click to expand...
Click to collapse
ahhh icic, well will try it out next time the SOD occurs to me again
when i was using setcpu on GB i got SOD with lulzactive too, i didnt under/over clock.
i just use on demand or conservative instead,i have not bothered to find out why it occurred
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Just try clearing app data rebooting and reinstalling the app. That problem has happened to me every once in a blue moon and that fixed it for me.
Sent from my SGH-I777 using Tapatalk 2
Thanks, I'll try reinstalling the kernel.
Which app are you referring to? because I had this problem no matter which app I used to change the governor (Extweaks, voltage control, setcpu).
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
bacon_n_icecream said:
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
Click to expand...
Click to collapse
It's the lulzkernel for some-reason :|
I have problem goto smartassv2 it's ok just steps heavy
Thanks for your suggestion. I just moved over to ondemand and its been ok for me. Too early to make any judgments but I'll try smartassv2 next.
Not that I'm glad to that you're having problems, but I'm glad I'm not the only one with this issue. Thanks for the response
Winklie said:
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Click to expand...
Click to collapse
DONT use kernel cleaning scripts. They cause more problems than good.
Sent from my AT&T I777 running AOKP build 3X
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
bacon_n_icecream said:
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
Click to expand...
Click to collapse
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
thanks, I generally do that any way along with the script cleaner
K Rich said:
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
CPU related as well...
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
kbulut said:
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
Click to expand...
Click to collapse
Lots of questions there. Phone overclocking is the same and at the same time different than PC overclocking. I too bought SetCPU and due to bugs and problems have completely abandoned it. Honestly with the exception of running an epeen benchmark there is little incentive to overclock. Find a newer Kernel (I use NEAK which has no overclocking ability) and install it, performance is stellar. You really have to ask yourself, is my phone slow enough that I need more CPU power to make it faster?
To see what time your CPU is spending at a given clock speed, download CPUSpyhttps://play.google.com/store/apps/details?id=com.bvalosek.cpuspy&feature=nav_result#?t=W251bGwsMSwyLDNd, you will be surprised to see your phone spend very little time at it's max clockspeed.
Due to the immaturity of the fab process for our CPU's (well SoC), what is a stable overclock for one person might not even load for another. These CPU's are not like an Intel Sandy Bridge, with 1Ghz of free overclocking, nearly guaranteed. You can certainly play with voltages to try and attain a higher overclock, but at the expense of CPU lifetime, as well as battery.
Additionally, it takes a new Kernel 3 or so full charge, discharge cycles on a phone to really 'settle in' and 'learn' a particular phones battery, while yours got hot, which to me indicates an endless loop of some kind running in the background.
My advice would be as follows: Choose a ROM you like, feel free to play with different Kernels, again, I use NEAK, which does not work for some folks, or crashes or whatever. Give it several days to 'settle in' and if your still not happy with performance or have stability problems, try a different governor/scheduler. You really need to establish a good, solid baseline of your phones performance and make small changes and give them long enough to establish any changes to your phones overall stability. Basically running cowboy through your phone and making changes will have a negative overall outcome. Make small, documented changes, test and see what overall effect this has to your phone's stability and battery life, and make another change.
bacon_n_icecream said:
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Click to expand...
Click to collapse
Lulz has known problem in 3.2b2-1
Gokhan has fixed it in 3.2b2 - 2
Wait for ktoonsez to update it for us
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Thank you so much for the information. Could I simply uninstall the setcpu and go back to normal? Simply reflash the rom and/or kernel? I really like shostock2 with the cherry picker kernel for now. I want to give them a week of try to make my mind. Before the setcpu I think.I was better off
Thanks for the help by the way. I appreciate it.
Thanks for the update about the new siyah kernel. Glad it wasn't just me with the issue. I was going to post this question in the siyah thread but am new to the site so didn't have permission so thanks for finding me all the way over here
Phalanx7621 said:
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I'm just going off what I've seen in the Siyah/NEAK threads. Most of the lock-ups/random reboots I've heard people having had used the cleaning script. Either that or its just coincidence.
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
bacon_n_icecream said:
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
Click to expand...
Click to collapse
Hmm, well I've just manually wiped cache and dalvik and have never had problems between roms/kernels.
Sent from my SGH-I777 using Tapatalk 2
What I'm running:
Latest NEAK kernel + AOKP build 36.
Issue also occurred in Phonebricker + NEAK (sammy version).
My issue:
Occasionally the OS will get extremely slow, like you would expect if the phone were running at 100mhz or something. Everything continues to work, just reeaaallly slow. For instance, music playback gets very electronic-y as sounds are stretched out, tapping one of the capacitive buttons takes 5-10 seconds before vibration/feedback, and another 5-10 seconds before a menu pops up. I managed to get the NEAK configurator open and scrolled to the CPU tab, and it claimed I was at 1200mhz - though the phone didn't even get warm so I'm skeptical.
I'm guessing since I've done a full wipe between phone bricker + NEAK and AOKP + NEAK, the only thing in common are my apps and the NEAK kernel, so it stands to reason it would be one or the other causing this. My wife's GS2 is running AOKP + NEAK as well though and we haven't experienced this problem on it yet (but it's intermittent so it might be there, just hasn't happened yet). I'm currently running conservative governor + SIO, but it has also happened on conservative + NOOP.
While I could just change a bunch of sh!t and hope it goes away, I'm more interested in figuring out what's causing it, and fixing it properly. How can I figure out what's going on? What will log this kind of thing? What do you guys recommend?
Thanks!
this is really easy/simple. flash a different kernel. all devices are not created equally so you need to just try everything that we have and see which best fits your device.
if you had this issue on 2 different roms with the same kernel then you've answered this question in your post for yourself. it wasnt even necessary to post this dude. change kernels. done.
some phone like neak kernel, some phones dont. some phones like siyah, some phones dont. you cant "fix" that unless you get a different phone and try neak again. but even then it my not "fix" this issue because nothing is broken.
Well, what if it's something as simple as the governor I'm using or an undervolt setting? I'll probably flash back to your kernel though, but again it'd be nice if I could figure out exactly what the phone is doing when it's "super-lagging".
Eckyx said:
Well, what if it's something as simple as the governor I'm using or an undervolt setting? I'll probably flash back to your kernel though, but again it'd be nice if I could figure out exactly what the phone is doing when it's "super-lagging".
Click to expand...
Click to collapse
If you're undervolting when this issue is happening, change it back to regular voltage.
I can attest to the slow downs and the screen lock ups. I have been using Tasks kernel for the past week and a half. Going back to try NEAK one last time. If it gives the same results I'll have to give up on it. I don't under volt hardly at all by the way. Like maybe -25 per step so it isn't that, and when I first experienced the issue I tried Evey possible io scheduler / governor combo under the sun. All yielded same darn results.
Sent from my SGH-I777 using xda premium
Phalanx7621 said:
I can attest to the slow downs and the screen lock ups. I have been using Tasks kernel for the past week and a half. Going back to try NEAK one last time. If it gives the same results I'll have to give up on it. I don't under volt hardly at all by the way. Like maybe -25 per step so it isn't that, and when I first experienced the issue I tried Evey possible io scheduler / governor combo under the sun. All yielded same darn results.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
+1, my problem was with typing as well. Stock voltages, several kernels.
Sent from my Galaxy S2
Simba501 said:
+1, my problem was with typing as well. Stock voltages, several kernels.
Sent from my Galaxy S2
Click to expand...
Click to collapse
I've only used Task's (CM9) kernel and NEAK, and I haven't yet experienced any slowdowns with Task's, but I really have no idea what kind of optimizations his has, haven't found any information on it published so I can't say what's different between his and the NEAK kernel.
What kernels have you had problems on?
Eckyx said:
I've only used Task's (CM9) kernel and NEAK, and I haven't yet experienced any slowdowns with Task's, but I really have no idea what kind of optimizations his has, haven't found any information on it published so I can't say what's different between his and the NEAK kernel.
What kernels have you had problems on?
Click to expand...
Click to collapse
Stock & Siyah. My issue with it wasn't major; it just isn't as polished as GB. The difference is noticeable.
Sent from my Galaxy S2
When mine gets laggy, I usually pull out the battery and put it back after 10 min or so. If you are leaving the phone on more than 2-3 days at a time, that could really hurt the memory and phone performance. The phone usually runs on 300 mb but it will run about 700mb ram after 3 days (even force closing everything).
It is not mentioned so I just wanted to cover all bases
After posting about giving NEAK another try, I did. And within 10 minutes got an extreme lag slow down while typing. Didn't touch any settings kernel side. So I flashed siyah kernel and so far no problems. Sux too. I liked NEAK.
Sent from my SGH-I777 using xda premium
I have been running Siyah with Task's AOKP and have had zero lag and great battery. No UV or OC.
Sent from my SGH-I777 using xda premium
Posted this in NEAK thread but also posting it here:
I just installed the new AOKP, used kernel clean script and installed NEAK 2.0.5x, then went into the NEAK Pro config and changed my governor to Conservative and sched to SIO. Rebooted, opened Scramble with Friends and immediately got superlag.
Turning off the screen and waiting 20-30 seconds fixes it (long enough for the phone to go to sleep), but nothing else short of a reboot will help. I can leave it like that for an hour (if I don't let it sleep) and it'll still be uberslow.
I have recently just hopped back onto ICS AGAIN. I have used ICS ever since its been out for my region and every single try i will revert due to the same issue. Either battery life or random freezes.
This time i am really lost hope. I was hoping samsung could release something that worked for me but it never came. I have to seek help from all the pros
The situation:
I have flashed afew ICS ROMs and kernel combo. I tried
DXLP9 w/ stock, siyah, NEAK
DXLPB w/ stock, siyah, NEAK
Sensation ROM 3.5 with siyah.
They all had the same issue whether i UV them or not. I tried factory resets, clear cache, kernel cleaning scripts, even SD format.
They all will have random freezes on load. Its random so sometimes i cant recreate the situation. Most common ones are updating or downloading from market, when its near or starts to install. But i can watch videos and everything fine. GMaps sometimes freezes it too.
As for governer i use smartassv2 for siyah and lulzactive for NEAK and SIO as scheduler. Did try ondemand on stock and sometimes noop and NEAK. Same responses.
I ran sensation rom fine ytd with 1 widget and downloaded whatsapp and extweaks and UV and everything was stable. Watched pps the whole night. Totally fine and this morning i wanted to load my normal apps from market and it started to freeze on me.
Im really lost someone pls help me. If not i really have to go back to GB again.
Sent from my GT-I9100 using xda app-developers app
sianzb0i said:
I have recently just hopped back onto ICS AGAIN. I have used ICS ever since its been out for my region and every single try i will revert due to the same issue. Either battery life or random freezes.
This time i am really lost hope. I was hoping samsung could release something that worked for me but it never came. I have to seek help from all the pros
The situation:
I have flashed afew ICS ROMs and kernel combo. I tried
DXLP9 w/ stock, siyah, NEAK
DXLPB w/ stock, siyah, NEAK
Sensation ROM 3.5 with siyah.
They all had the same issue whether i UV them or not. I tried factory resets, clear cache, kernel cleaning scripts, even SD format.
They all will have random freezes on load. Its random so sometimes i cant recreate the situation. Most common ones are updating or downloading from market, when its near or starts to install. But i can watch videos and everything fine. GMaps sometimes freezes it too.
As for governer i use smartassv2 for siyah and lulzactive for NEAK and SIO as scheduler. Did try ondemand on stock and sometimes noop and NEAK. Same responses.
I ran sensation rom fine ytd with 1 widget and downloaded whatsapp and extweaks and UV and everything was stable. Watched pps the whole night. Totally fine and this morning i wanted to load my normal apps from market and it started to freeze on me.
Im really lost someone pls help me. If not i really have to go back to GB again.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
try with less UV, and more bus freq
pelpa87 said:
try with less UV, and more bus freq
Click to expand...
Click to collapse
but i even tried no UV and with stock. ytd i tried no UV again. seems to be performing well but i cannot let my phone run without UV cos it will drain battery very fast
Btw im using the same 5 cpu states but i turned off the 1.2GHz state. So its 200 to 1000. What do you mean more bus freq? Up cpu speed?
sianzb0i said:
but i even tried no UV and with stock. ytd i tried no UV again. seems to be performing well but i cannot let my phone run without UV cos it will drain battery very fast
Btw im using the same 5 cpu states but i turned off the 1.2GHz state. So its 200 to 1000. What do you mean more bus freq? Up cpu speed?
Click to expand...
Click to collapse
dunno about siyah, i use fluxi, u can ov bus. I think in siyah too.
The thing is simple, not every phone reacts equal. My phone for example doesn't handle strongs uv. I have to slightly uv it. Same as bus.
I even saw some phones that couldn't handle aokp without over volting. Ir getting higher bus.
In the other hand, uv is overrated. It doesnt saves as battery as everyone thinks. The screen is battety's worst enemy
Sent from my GT-I9100 using xda premium