First of all, I'll try to explain the situation:
I was using my X10a with the stock 2.1 2.0.2.A.0.24 firmware with root and JIT enabled (yeah, I like to use my Sony Ericsson with Sony Ericsson's software). And everything was fine, I had the software mod to enable dual touch, so far, so good.
Then, I heard about this new 2.1.A.0.435 build with some improvements on Mediascape and overall performance, not to mention the official dual touch support (that is a bit better than the unofficial). So, as my X10 is Global Generic, I decided to update my software with SEUS. After updating, I rooted my phone and did the same things that I did on the other build (enable JIT and install Sysctl), but this time, my battery was draining like more than 10 percent an hour no matter if it was idle or in use! So i started investigating what was draining my battery and by monitoring the CPU use with SetCPU, I noticed that the CPU was always working at 998Mhz and before, it usually went up to 998Mhz, but when idle, it stayed on 245Mhz. With .24 build, it usually stayed on 245Mhz when idle, but with .435 build, it ALWAYS is on 998Mhz, even when idle! Sometimes, for less than a second, it goes down to 245Mhz and immediately up back to 998Mhz. I've tried many things, but the processor clock is always on top. SetCPU can underclock it (I can set both sliders to 245 and it will show that the CPU is on 245), but I don't want to use a slow phone to get the same battery life I got with the other build! And I checked with SeePU the CPU load doesn't change the clock. Even with low cpu usage, it keeps the 998Mhz clock.
Anyone has got any suggestions of what should I try now? I already updated with SEUS, repaired with SEUS, flashed the Stock .435 ROM downloaded from this forum but the problem persists. Any suggestion to solve this battery drain problem is welcome.
Thanks in advance.
Now I see how useful it is to post a question in this section of the forum.
Use Set cpu profiles, I.e. when The screen Is off the cpu should be at the minimum settings, with the highest priority.
Sent from my X10i using XDA App
Yeah, this is a fix. But then, to have the regular battery life, I just have to let my phone idle at all times and not use it as before? And by the way, by the time I said "how useful..." I already found that an app was draining my battery life. The app was Turn Silent. It kept my CPU at highest clock at all times, making even charging the phone a hard task. I just went back to Flip4Silence. Now my CPU stays at 245Mhz at most times.
Still I see that posting in the right section of the forum is useless. If I posted this thread at Android Development, people who get to understand what makes Android bump up the CPU clock would certainly at least investigate what might be happening. Well, it seems that build .435 is better, but it allows the CPU to stay at full clock more than needed. And the SetCPU fix really meant a great deal, but to get longer battery life, I have to "avoid" using my handset. I hope someone join me in this thread and help me investigating what's wrong. I'll try this new firmware released by Rogers, since it has a new baseband and possibly a fix for that CPU management issue.
moacyrfilho said:
Now I see how useful it is to post a question in this section of the forum.
Click to expand...
Click to collapse
There was no need for this useless and demeening comment.
Sent from my X10i using XDA App
Stating true situations is demeening? What about bringing up solutions in the correct place? Is that too much to ask? Oh, well... Anyway sorry for the ones who got offended.
Related
OK, so I'm on GSB 3.4 (though this issue began with 3.3), and I'm having a problem with my phone rebooting (screen cuts off after about a second, and the phone immediately reboots to the skateboard screen) at the following times:
1. Whenever I attempt to wake the phone from sleep.
2. Whenever I hang up a phone call.
3. Whenever I get a phone call while the phone is asleep.
4. Whenever I plug the phone in to charge while the phone is asleep (be it a wall socket or PC) [see below].
These problems only occur when the phone is NOT plugged into a charging source; the problem appears to be nonexistent in this scenario. But as soon as I unplug, all 4 become auto-crash scenarios.
I tried going back to GSB 3.2, but no dice. I then resorted to the stock-ish XTRsense ROM, which fixed the issue, but going back to Froyo just was too big a downgrade for me.
Throughout this process, I full-wiped multiple times, hoping to track the issue to an app or setting, but even before restoring anything through TBU (I think I may have just let the phone go to sleep at the "Touch the Android" initial setup screen once), the problem persisted, eliminating apps, settings, or CM7 CPU modifications as possible culprits.
I've continued to play with CM7 CPU settings even up till now, but I'm not getting much of anywhere. I've now resorted to the "Caffeine" app, which just never lets the phone go to sleep, and I just turn the brightness down or activate the "Desk Clock" mode in the default Clock app to save battery.
HELP?
Have you tried Tazz's ROM or CondemnedSoul's ROM, just to see what happens with those? CS's ROM uses ADW as the default launcher (not sure about Tazz's) - perhaps it's something with LauncherPro?
Had this happen once
Sent from my Aosp Gin-Tazz using XDA App
My phones use to freeze on the unlock screen, it happened in multiple roms. i switched back to the "ondemand" governor and it hasn't happened since. not sure if it the same issue but it might help.
My last name is also Schultz ....
Sent from my Aosp-Gin-Tazz using XDA Premium App
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
scary alien said:
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
Click to expand...
Click to collapse
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
I'll try the changing the max, but I know I've tried as low as 604 max (19 min) with the problem persisting, and as high as 710 or 768 before GSB 3.3 (when the problem started) with no major issues. And I had already been using Ondemand when the problem started, having stopped using Smartass when I thought it slowing the performance down a bit. Any other governors I should try?
And does the overclocking issue not apply when a phone is charging?
doogald said:
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
Click to expand...
Click to collapse
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
natemup said:
And does the overclocking issue not apply when a phone is charging?
Click to expand...
Click to collapse
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
scary alien said:
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
Click to expand...
Click to collapse
You would have only seen that if you had seen the post in the GSB thread, of course.
I am still going to suggest trying Tazz or Condemned. From what the OP says, he should be able to see that it's having the same issue pretty quickly.
But, just to rule out the OC issue, you could try setting the max to stock 528 and see if it still happens.
doogald said:
You would have only seen that if you had seen the post in the GSB thread, of course.
Click to expand...
Click to collapse
lol...that post was on the 519th page of (currently) 530 pages! (I read the first page, does that count? )
Still crashing on 528 max / 19 min...
natemup said:
Still crashing on 528 max / 19 min...
Click to expand...
Click to collapse
How about on Tazz or Condemned? And, 19.2 is too slow for a minimum for this kernel. 245 should be the minimum.
scary alien said:
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
Click to expand...
Click to collapse
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
One more thing: if, right after the phone reboots itself, I unlock it before the screen goes off and manually put it to sleep and quickly wake it back up, the issue usually doesn't occur (and I can keep doing this, putting it to sleep and waking it back up again, with no issue). But if I unlock it and let it sit and reach the screen timeout itself (or never unlock it after it reboots, then let it sit for a while), the problem reoccurs.
natemup said:
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
Click to expand...
Click to collapse
I have used both GSB and Condemned and you will not be missing anything. I stopped using GSB because I could not get market updates to stick reliably. I do not have that issue at all with Condemned.
Right now the only issue with the latest Condemned is apparently a GPS issue, so I would go with V6 or V7 rather than V8 for now until CondemnedSoul gets an update. Or, if you don't navigate, go ahead with V8. It's just fine.
You're obviously having a stability issue with GSB now, so you have nothing to lose but about 45 minutes of time and a Nandroid Restore to go back to GSB if you don't like it.
So, I had a minor issue that was fixed by switching to a different ROM. It's worth a try.
I wish you luck finding a solution.
natemup said:
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
Click to expand...
Click to collapse
Nate,
Sorry about that ...I was confused from where you asked in post #8 about whether or not overclocking was in effect while charging (it can/could be, depending on the overclocking monitor/govenor I suppose) and I had lost that point from your original post.
I would say take doogald's advice and switch to at least some other ROM since that would help indicate if it is indeed a software issue or a hardware issue. Its sounding like its not clock-speed related given the things you've already tried. If you've still got issues on other ROMs, that would tend to point to some hardware issue (our Erii are getting a little long in the tooth at this point, after all).
You could even flash back to stock and see if the phone is still stable there since you can always re-root and re-restore your Nandroid backups.
Good luck...I hope you figure something out.
Problem is alive and well on Condemned GB. *sigh*
XTRsense was fine and flawless, but going back to Froyo after months on gingerbread was just too depressing for me...
Sent from my ERIS using XDA App
I'm going to make one more suggestion - not sure if you have tried this yet, but try flashing GSB from a full wipe. When you go through the setup, DO NOT LOG IN TO YOUR GOOGLE ACCOUNT. After the launcher starts, go into the market, let it log you in to your Google account then, and then install all of your apps and change all of your settings from scratch.
When you log in with your Google account when installing a CM ROM, it tries to restore your apps and settings from your last CM ROM install. It may be that you have some weird setting or app that is causing this that you just keep reinstalling when you flash the ROM and log in with your account.
If you've already tried this, then try running xtrSENSE or xtrROM instead. They are both excellent ROMs and clearly your phone likes them better.
[edit] Oh, and try leaving your min at 245 MHz for a while. See if that helps your phone run better. It should, and it should have the exact same battery life as 19.2, as nonsensical as that sounds.
It is literally happening as soon as I boot the phone after a fresh GB install. I four-corner the Android setup screen, let the screen time out, and boom I'm screwed.
i'VE BEEN RUNNING CM7 for a month (about)
I update to the latest version and right now im on the KANGED version thats not OFFICIAL release but it is made by the dev.
Anyways...
Every day i wake up in the morning, from 100% my battery goes to about 90- 85% from using it then i go to school, phone in my pocket for about 7-8 hours.
It usually goes to 70% or 75% when i check soon as school is over.... but today.. it was at 32%!!?
My battery has been draining FAST this past week. IDK what's causing it, but i think its a app, but watchdog lite doesn't show anything at all.
Any tips at all guys?
- PLEASE DO NOT REPLY TELLING ME TO PUT IT ON AIRPLANE MODE WHILE IN MY POCKET- I GET TEXTS FROM MY BROTHER/MOM TELLING ME IF I HAVE TO WALK OR IF THEIR GOING TO PICK ME UP AND OTHER IMPORTANT INFO LIKE THAT-
Please help me out here.
I love CM7, and it's NEVER been this bad, but if it is because of CM7 then i have no choice but to go back to 2.2.1
EXTRA INFO:
I don't have a data plan so... my phone can't communicate with other servers and crap.
I keep wifi off, bluetooth off GPS off.
Maybe i'll have auto brightness on but thats it.
Check what profile are you using on setcpu? Also you might wanna check the signal while in you school.
Sent from my SGH-T959 using Tapatalk
Check battery stats it will tell you what is using your battery the most.
Sent from my SGH-T959 using XDA App
Abu-7abash said:
Check what profile are you using on setcpu? Also you might wanna check the signal while in you school.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
I suspected it was SetCPU doing this, so i uninstalled that.
the signal is... okay? When in my pocket it sometimes goes to NO Signal, but is usually at 2-3 bars.
rom fiend said:
Check battery stats it will tell you what is using your battery the most.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It says Android OS is using the most.
Then Display
then Cell Standby
then Phone Idle.
Honestly, my phone isn't even turned on during the whole thing..............
I maybe check the time once in the while, but besides that its always idle.
I just slept for a hour. I lost 10% in that hour. WTF is this lol
try recalibrating the batter by using either root explorer or the terminal to delete /data/system/battstats.bin as sometimes CWM on cm7 for galaxy s doesn't delete it.
i have the same issues and tried everything..i dnt even have data plan to use internet and i keep my 2g on and my battery still drains like pipes in the sewers
geoffcorey said:
try recalibrating the batter by using either root explorer or the terminal to delete /data/system/battstats.bin as sometimes CWM on cm7 for galaxy s doesn't delete it.
Click to expand...
Click to collapse
I use battery calibrator app and used it alot and battery left app shows, my readings are accurate but not from 0% because I never reach 0%.
Time to go to 0.
Thanks.
More tips would be nice as well
xriderx66 said:
I use battery calibrator app and used it alot and battery left app shows, my readings are accurate but not from 0% because I never reach 0%.
Time to go to 0.
Thanks.
More tips would be nice as well
Click to expand...
Click to collapse
try not using the battery claibrator app, and removing it from your phone and manually deleting the batterystats.bin file from /data/system and see if that helps your phone at all.
I also suggest getting CPUSpy from the market, and track what states your phone is in and for how long it is in certain states. if it's not going into the sleep state, then something is keeping the cpu active (possibly a governor setting).
xriderx66 said:
I suspected it was SetCPU doing this, so i uninstalled that.
the signal is... okay? When in my pocket it sometimes goes to NO Signal, but is usually at 2-3 bars.
It says Android OS is using the most.
Then Display
then Cell Standby
then Phone Idle.
Honestly, my phone isn't even turned on during the whole thing..............
I maybe check the time once in the while, but besides that its always idle.
I just slept for a hour. I lost 10% in that hour. WTF is this lol
Click to expand...
Click to collapse
That aint normal my friend, you should jump into another modem, regardless of what you're on. Maybe that helps and by all means, what kernel are you on?
I'm on the stock kernel... Should I visage and can you link me to more cm7 modems or atleast a good one that works good?
geoffcorey said:
try not using the battery claibrator app, and removing it from your phone and manually deleting the batterystats.bin file from /data/system and see if that helps your phone at all.
I also suggest getting CPUSpy from the market, and track what states your phone is in and for how long it is in certain states. if it's not going into the sleep state, then something is keeping the cpu active (possibly a governor setting).
Click to expand...
Click to collapse
During the whole night its been at 800ghz for 71%
WTFFF
Also how do I know its a governor setting? I don't usually use those at all
Where can I check if it was that?
xriderx66 said:
I'm on the stock kernel... Should I visage and can you link me to more cm7 modems or atleast a good one that works good?
Click to expand...
Click to collapse
The stock one should be battery efficient but I honestly haven't really tried it out. Give r12 or r25 a shot from here. They've been great in every aspect to me. Just make sure you're not on kang 7.1 when flashing, it doesn't support that.
As for modems I'd suggest either KB5 or KB1. If you're on either one switch to the other, may help.
don't run phone on "performance" -- it's silly to run the cpu at top speed when the phone is just sitting doing nothing. Run it at "on demand" or "conservative" especially if it is OCed. Also set screen timeout at a minute or less. If you got the phone used, it's possible the battery is old. If you reboot it a lot and install roms and stuff you'll run the battery down fast.
Well..
Yesterday I did a cleaning of apps i never use and some i installed recently.
I guess that did the trick? I have no more problems came back from school and my battery's at 76%
@Abu, thanks for the tips. i don't want to get a different kernel and modem.. im on kanged 7.1 lol.
@Nazcalito
Fearing it was that i uninstalled SetCPU.
Should i re-get it and make it OnDemand?
xriderx66 said:
Fearing it was that i uninstalled SetCPU.
Should i re-get it and make it OnDemand?
Click to expand...
Click to collapse
don't use setcpu if you don't have to. the built int scaler for the kernel is actually much better than letting setcpu run in the background polling the cpu and system for changes.
if you're running a custom kernel, get voltage control, and with it you can UV, OC, under clock, and change scheduler.
And in Settings -> CM Settings -> Performance -> CPU Settings, you can control min frequency, max frequency, and governors.
geoffcorey said:
don't use setcpu if you don't have to. the built int scaler for the kernel is actually much better than letting setcpu run in the background polling the cpu and system for changes.
if you're running a custom kernel, get voltage control, and with it you can UV, OC, under clock, and change scheduler.
And in Settings -> CM Settings -> Performance -> CPU Settings, you can control min frequency, max frequency, and governors.
Click to expand...
Click to collapse
I went there, and its already on "ondemand" so.. nothing should be touched?
Anything else i can do?
The only time i use internet is at home with WIFI
Hi,
I followed qbking77's video to install the alpha build of ICS on photon 4G. I then used Antutu CPU Master (Free) to underclock the phone. After the twaeking I used the app CPU Spy to check the distribution of CPU frequencies used over a period of time. I observed that the phone has not been able to get into the deep sleep mode. With stock ROM, the phone always spent over 80% of the time in deep sleep (averaged over a day). But the ICS build is not allowing the phone to get into deep sleep state.
Its either this or the CPU Spy app is broken by the ICS build. I am not sure what it is and I wanted to ask the forum members if they have seen anything similar. Due to permission issues I am being forced to post it here rather than the development thread. I apologize if this causes any confusion.
I am interested in this as this might help improve the battery life.
- Harakiri
Harakiri1298 said:
Hi,
I followed qbking77's video to install the alpha build of ICS on photon 4G. I then used Antutu CPU Master (Free) to underclock the phone. After the twaeking I used the app CPU Spy to check the distribution of CPU frequencies used over a period of time. I observed that the phone has not been able to get into the deep sleep mode. With stock ROM, the phone always spent over 80% of the time in deep sleep (averaged over a day). But the ICS build is not allowing the phone to get into deep sleep state.
Its either this or the CPU Spy app is broken by the ICS build. I am not sure what it is and I wanted to ask the forum members if they have seen anything similar. Due to permission issues I am being forced to post it here rather than the development thread. I apologize if this causes any confusion.
I am interested in this as this might help improve the battery life.
- Harakiri
Click to expand...
Click to collapse
Have you posted any of this info in Joker's ICS Forum? I think he would appreciate the feedback.
I cant post in dev forum unless I have 10 posts. If someone could post in on my behalf it would be great. I think this is something that will greatly improve battery life if it gets fixed.
- Harakiri
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
Hey Guys,
i have to ask a new Question again.. (And because i'm not allowed to ask it in the X10 Mini Pro MiniCm10 Thread i have to aks here..):
Since yesterday i'm trying MiniCm10 on my X10 mini Pro, and for the moment everything is good except off the battery.. The Battery is going low very quick.. Even if i don't use the phone..
Is there something i can do to make it last for a longer time?
Thanks for you help
have you enabled undervolt an governor "on demand" in the cpu settings?
btw, one of the problem of this phone is the very little battery, and the new version of android are more heavy on the battery...
_cheh_ said:
Hey Guys,
i have to ask a new Question again.. (And because i'm not allowed to ask it in the X10 Mini Pro MiniCm10 Thread i have to aks here..):
Since yesterday i'm trying MiniCm10 on my X10 mini Pro, and for the moment everything is good except off the battery.. The Battery is going low very quick.. Even if i don't use the phone..
Is there something i can do to make it last for a longer time?
Thanks for you help
Click to expand...
Click to collapse
First I would check if the phone is sleeping properly, which is not always the case with MiniCM10. If you turn off the screen it should go to sleep in about 10 seconds, and if you press the back-button when it's asleep it won't turn on the screen. If the menu- or back-buttons do turn on the screen then it's a sleep problem. Try disabling running services (everything apart from settings and keyboard should have no adverse effect on the running of the phone). If that doesn't help maybe wiping everything and re-installing the ROM could fix it.
Slash90[ITA] said:
have you enabled undervolt an governor "on demand" in the cpu settings?
btw, one of the problem of this phone is the very little battery, and the new version of android are more heavy on the battery...
Click to expand...
Click to collapse
No, i didn't tried.. But if i understand the wikipedia-article concerning undervolting correct, it can force errors? I'm not sure if i want my handy to make calculating-errors...
@SmG67, I'll check this tomorrow, when i have to leave my phone without the possibility to charge it again for the whole day..
@both of you: Thanks for the quick answers
_cheh_ said:
No, i didn't tried.. But if i understand the wikipedia-article concerning undervolting correct, it can force errors? I'm not sure if i want my handy to make calculating-errors...
@SmG67, I'll check this tomorrow, when i have to leave my phone without the possibility to charge it again for the whole day..
@both of you: Thanks for the quick answers
Click to expand...
Click to collapse
No error, maybe reboots if you use undervolt with overclocked cpu frequencies
Slash90[ITA] said:
No error, maybe reboots if you use undervolt with overclocked cpu frequencies
Click to expand...
Click to collapse
The processor won't be undervolted on anything above 604 Mhz, only on frequences lower than that. The undervolt module doesn't use unstable voltages anymore, the only trade-off is that stepping up through the frequencies takes a bit longer because the voltage needs to be ramped up too, making the phone slightly slower. So there is not really any harm in enabling it.