Database Info

Ondemand vs Lazy Governor

Guys, can you help me out?
Something odd has been happening on my phone. I run Matrix kernel 9.5 on Lazy Governor and everything's fine, but when i turn it to Ondemand the phone starts to reboot randomly.
Does anybody know what can it be?
Thanks!

Try running different min and Max frequencies and see if that helps.
Sent from my Nexus S using Tapatalk

have you fiddled with the voltages

I tried different min and max frequencies and I also played a little bit with voltages. What i realized is that if the voltage is too low for a particular frequency my phone reboots. Do you know how can i teste how far i can get with OC?? If i OC to 1.2GHz for instance, and my phone reboots... Can i put a higher voltage to 1.2 frequency in order to get it working?
Thanks in advance!

Try to increase the voltage as small as possible until it not reboot
But be carefull! Increased voltage can damaged your cpu.
I prefer dont do OC, this device is fast enough on default freq.
Sent from my Nexus S using XDA App

[Q] Massive reboots while charging.

Hi i have never encountered such a problem before, been using my phone for about a year now.
When i updated my ROM to CyberGR-MOD|NS.NGN ICS v.8 HYBRID+ICUP Speedy7|CM9-AOKP|MODS++|STORMY 3 and switched to Matrix 17.5 kernel i get massive reboots while my phone is charging.
the thing is the phone works flawlessly while on battery but once i plug in the charger i'll get random reboots. i am running at stock kernel settings. ondemand, cfq scheduler. no OC no Undervolt. any idea whats the cause of this??
thanks!!

Matr1x is undervolted by default, so try setting them to default values in NSTools or something. I believe INT is undervolted too. Defaults are:
ARM:
Freq (MHz) Voltage (mV)
100 950
200 950
400 1050
800 1200
1000 1250
INT:
Freq (Mhz) Voltage (mV)
100 900
200 950
400 1000
800 1050
1000 1100

Sorry I forgot to mention that I have raised the voltages to original stock voltages as well. Double checked and my phone is running at those voltages when I get the reboots. Would you suggest raising them even more?

No, the phone should run perfectly well at stock voltages (as long as you raised arm AND int). Any higher is wasteful. Did you do a dalvik cache wipe before installing matr1x? And if you did, did you do a thorough wipe before flashing the new ROM? That would mean doing a data/factory reset and formatting /system at least (formatting /boot too, preferrably). If you can't find any other reason, i'd probably start with reflashing the kernel and then the ROM too, as many weird and wonderful things can happen if there are remnants of old system files.

Yupp that's what I usually do every time I update my ROM. I even did it once to try and fix this problem. I'm beginning to suspect that it's an issue with my ROM and the kernel. Though nobody on the thread seems to have the same issue. Eagerly waiting for an update. Anyways thanks for the advice.

Not sure what else it could be aside from the typical try a different kernel/rom/governor/whatever. Hopefully an update or something clears it up for you, but until then i'd definitely try to find something that doesn't go ape**** when you start charging

[Q]i9023 once reboot during boot (Matr1x 20, stock rom)

Hy guys!
I own an i9023, and I'm a frequent reader of XDA's Nexus S section. A week ago I've decided to change the stock kernel. I choose the newest Matr1x kernel, i found this the most sympathetic, after reading through several [kernel] threads. So i tried the 19.5 BFS/CFS, and now my device is on 20.0 CFS with stock rom 4.0.4. I've installed NSTools too. And using smartassV2/noop 100/1000 DIDLE, and no OC, and default voltages too.
I am absolutely statisfied with the kernel, it is much smoother than stock, and has a great battery life, and gets better with every update. At least in case 19.5 to 20
But here is my problem:
Almost in every boot, my phone reboots once during boot. After it is rebooted, works like a charm, no freezes, nor reboots. Fast, reliable, anything you want.
I noticed the device boots without any problem after flashing kernel, before applying any NSTools settings, or if I use resetnstools.zip.
So i am thinking, maybe NSTools can be the source of this reboot.
Here is my NSTools settings:
All tewaks off, 97%, noop.
CPU: smartassV2, 100/1000
liveOC: 100%, 800, 1000
DIDLE: ON
SmartassV2: awake ideal 1000, sleep ideal 100, sleep wakeup 600, min load 70, max 85, ramp down 200, up 200, down rate 49000, up 48000
volt: default
Settings: set on boot
So any idea what is causing this reboot? Or this is normal? I think it is not, but it even could be
Thanks the answer.

Matr1x is undervolted by default. Try upping them a bit or reverting to stock voltages.

Harbb said:
Matr1x is undervolted by default. Try upping them a bit or reverting to stock voltages.
Click to expand...
Click to collapse
This. My phone hates undevolting and I had to return all the voltage settings to the stock Nexus settings if I want to use his kernel. Since I changed them, I've had no reboots or freezes.

Thanks the fast answer Harbb and chronophase1!
Looks like mine hates the UV too Raised the voltages a bit (didn't changed the INT, and that ARM, what was already on Nexus S default), look like good at first look. But requires further testing, to say the problem is gone. Thanks again.

Yeah. All phones aren't the same sadly. If it makes you feel any better, I've been running the kernel for almost 100 hours straight and no issues. Before, every time I hit about 95 hours up time the damn thing would freeze with the UV settings. So I'm still running the test but so far so good on my end.

Looks like the problem is solved. After several voltage settings, I had to return to default Nexus S voltages, even on 1Ghz. The reboot during boot disappeared.
I lost the UV, but I gained OC, now stable on 1.2GHz/1350mv/1150mv. And battery is still good, hope it will remain that way.

Did you change the INT VOLT settings first? Or did you revert all to the stock levels.
I suspect reverting only INT VOLT to the Stock levels will fix those problems. If anybody is willing to try that would be nice ) (I only experienced reboot once with default Matr1x values so no point in my trying)

[Q] CPU Maxed Out?

Hello. I am having an issue. My mother was talking to me today, and she was complaining about how her phone was so hot. I checked it out, and it was definitely was. So I loaded up CPU Spy, and it is showing that it is running at 1200 MHz for over 10 hours. It is not lowering its frequency at all. I tried rebooting and it is doing the same thing. I am not sure how to handle this. I have never had this happen when I had it (this was my old phone before I upgraded to the Galaxy Nexus). Does anyone know what I should do?

stompysan said:
Hello. I am having an issue. My mother was talking to me today, and she was complaining about how her phone was so hot. I checked it out, and it was definitely was. So I loaded up CPU Spy, and it is showing that it is running at 1200 MHz for over 10 hours. It is not lowering its frequency at all. I tried rebooting and it is doing the same thing. I am not sure how to handle this. I have never had this happen when I had it (this was my old phone before I upgraded to the Galaxy Nexus). Does anyone know what I should do?
Click to expand...
Click to collapse
First off, try to check wich governor are u using. Something such as performance or interactive give the permission to the cpu to rank up faster even if the task is light weight.
Then try to install another kernel but before juast wipe dalvik cache

Cascabreu said:
First off, try to check wich governor are u using. Something such as performance or interactive give the permission to the cpu to rank up faster even if the task is light weight.
Then try to install another kernel but before juast wipe dalvik cache
Click to expand...
Click to collapse
Tried changing governors to everything, including conservative, and it still jumps up. I will try and flash a different kernel and see what happens.

stompysan said:
Tried changing governors to everything, including conservative, and it still jumps up. I will try and flash a different kernel and see what happens.
Click to expand...
Click to collapse
Try matrix or bedalus

I flashed the latest Trinity and it seems to have fixed everything. Thanks for the help!

pros and cons OC/UV

about time for me to change roms again. i know there are many with this option, but have never chose to pursue that option due to lack of understanding benefits. always seemed to get satisfactory battery life out of phone, but could it be better? i have noticed different speeds on my phone with different roms but is this something that can speed up and keep the smooooth in my phone?
just thought i would get some feedback of the advantages and disadvantages of overclocking and undervolting.
will it harm my infuse?
what are good settings?
what exactly would the OC or UV each do?
if i run a search on this, i know i am going to get the phone book and just figured i would get a more specific answer directly as opposed to piecing little bits together and still not being confident in what my interpretation would be.
everyone in the infuse community always seems to have the answers and dont steer the dullards such as myself in the wrong direction.
you guys are the MAN, and well, you women.....your the woman i reckon

captemo said:
will it harm my infuse?
Click to expand...
Click to collapse
No, so significant damage can be done with overclocking. Alhought if you set your ghz too high your phone might become unresponsive, overheat and/or auto reboot your device. This is normal if your on GB and some ICS roms. Don't see it much on JB becuase the some kernels dont support it. Just be sure to play with your settings and MAKE SURE SET ON BOOT IS DISABLED or else your phone will be stuck in a bootloop when overclocked beyond stable settings.
captemo said:
what are good settings?
Click to expand...
Click to collapse
I usually stick with 1400 ghz because 1600 ghz[max] drains battery too quickly for not much of performance boost and 1600 is considered unstable on most GB and ICS roms. As for CPU governor Id stick with ONDEMAND.
captemo said:
what exactly would the OC or UV each do?
Click to expand...
Click to collapse
OC is over clocking your processor to a higher ghz for better perofmance and under volting is drawing less energy

Is there like a guide saying what each CPU governor does? Because some of them are pretty confusing with their terminology, like smartassv2

Garen21 said:
Is there like a guide saying what each CPU governor does? Because some of them are pretty confusing with their terminology, like smartassv2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1420742

I used to under volt a lot to get better battery life. But it seemed to make a couple apps hang now and then.
I am now on Scotts PA JellyBean ROM. Battery life is very good for me stock with this. So I have left under volt to stock settings.
Normally I'll run on smartassV2 governer. With NOOP i/o. And 100mhz - 1400mhz.. just for a little extra boost.
When I know I'll be playing a game or multitasking, I'll boost it to 1600mhz.
Overall stock settings run amazing, both battery life and performance, on Scott's PA JB and CM10.
After doing some reading, I believe I can get better results from using the above settings. It all depends on what your personal goal is.
The biggest concern you should have when overclocking is mentioned above. Boot loop, just make sure you test it for a while with set on boot un checked.
Undervolting you can go to low and also boot loop, so same applies here... leave set on boot un checked. All phones are different on what settings they run best at. Just gotta play around and see what works for you.
A good rule of thumb for under voting... go down 25mv at a time and test it out... keep going down 25mv until you get a problem or boot loop and then go back.. then you'll know your max.
You can safely under volt more on the lower frequencies than you can the higher ones. Personally I never undervolted more than 100mv across the board. And when I did, I usually kept it around -50mv.
Sent from my SGH-I997 using xda app-developers app

not for infuse but a good reference for ocuv. explains what they do
http://forum.xda-developers.com/showthread.php?t=1827635
Sent from my GT-I9300 using xda premium

This is the best guide I've found covering kernel and system tuning - CPU parameters, governors, schedulers, init.d, loadable modules, etc. It's for the SGS2 (i9000) and some of the governors/schedulers are not available on the Infuse, but much of this is applicable to our phone:
http://forum.xda-developers.com/showthread.php?t=1369817
As for OC/UV, as long as you stay away from the "Performance" governor (this runs the phone at max freq all the time), and undervolting below -75 to -100 you generally will be safe. As phones are different, it is important to test in gradual steps to ensure your phone will be reliable. Use a good CPU manager, like SetCPU, Antutu, or Voltage Control. Make sure you enable the "revert to stock" feature so that you can boot recovery and turn off any bad OC/UV. As noted above, do not check the enable on boot setting until you are certain you have a good config.
The decision to OC should take into account how you use the phone. If your phone is asleep more than 80% of the time on average, you can probably run an OC config and still have overall good battery life (i.e. lasting an entire day with nightly recharges). If you use your phone for music playback or something else that prevents it from sleeping, OC may not be for you. If you run CPU intensive games, it is better to disable UV settings while OCed.
Use CPU Spy to keep an eye on your time at each freq state (and sleep). Use the default battery stats and graph to monitor which apps are consuming the most battery. Use apps like Better Battery Stats, Android Assistant and Watchdog for more detailed monitoring of what is keeping the phone awake and which apps/processes are top cpu resource consumers. With this information you can identify problem apps and decide whether you should remove them from your phone.
From the "unintended functionality" side of the house, there are certain tweaks that will cause your phone to run at max freq ... mucking around with phone properties in build.prop can lead to runaway rild process problems (usually shows up as unusually high "Dialer" in the standard battery stats list and a phone that is warm or hot to the touch). Some of the tweak scripts in adrenaline and tbolt can cause similar problems. There is a known bug in the infuse network drivers that shows up as much higher than normal Android OS battery usage. This can usually be corrected (short term fix) by toggling Flight/Airplane mode off/on. Running the stock UCLB3 GB kernel also seems to minimize this issue (assuming you are running a GB ROM), but flash with caution as you will need to disable voodoo lagfix first. (You will also lose CWM recovery, OC/UV capability, and be on the slower stock file system setup).

I have done a fair amount of experimenting including lots of time on conservative governor with Fmax=1600 and never had any problem that I attributed to OC'ing.
In contrast I did find a limit on UVing. I just updated my thread with my experience on uv here:
http://forum.xda-developers.com/showthread.php?p=32552571#post32552571
The bottom line is that for MY phone, the following works fine:
100 Mhz: 950mv max – 50mv = 900 millivolts
200 Mhz: 950mv max – 25= 925 millivolts
400 Mhz: 1050mv max – 50mv = 1000 millivolts
800 Mhz: 1200mv max – 75 mv = 1125 millivolts
1200 Mhz: 1275mv max – 50mv = 1225 millivolts
1600 Mhz: 1400mv max – 75mv = 1325 millivolts
Some other links with others' experience suggestions about UV'ing for Infuse:
Hozw low is your undervolt?
http://forum.xda-developers.com/showthread.php?t=1693689&highlight=kernel
[Q] Recommended SetCPU settings?
http://forum.xda-developers.com/showthread.php?t=1292836&highlight=setcpu
You’ll note the last thread has comments from Entropy’s settings.
Also Zen and qkster gave advice in the first thread (my thread).
All three guys very well respected and worth listening to.
Entropy mentioned you can uv the higher frequencies more than the lower (different than what was posted earlier in this thread). I don’t know for sure but I’d lean toward Entropy’s advice on that matter.
I think all in all somewhere between 50 and 100 is the max you can expect to undervolt.
What can be achieved varies with phone as stated by many.
You are welcome to experiment with slowly decreasing. That's what I did.
But in the benefit of hindsight, the process of slowly decreasing is tedious. And going beyond the limit was a little scarey for me. Could've been worse if the phone crapped out at a critical time during "experimenting". Like almost everything related to battery life, the results (how much benefit) seem y subjective (difficult to measure quantitatively). Most people say they don’t notice a dramatic difference with UV. If you want to get the low hanging fruit without a lot effort, you might just try 50 down. That's what I'd do if I had to do it all over again.
By the way, setcpu can be set up to provide a failsafe escape route even if you go overboard. There is a zip file that will toggle the setcpu settings off when launched from CWM. You just have to put the zip file on your sd card before you start tweaking. See "safe mode" in the setcpu documentation.

started to wonder at first whether i would get any responses after 218 views and nothing, but i knew the community would come through as they always do. all the regulars as usual regulars ( Zen, Quickster and others) are always eager to help. i think you have all provided me with the valuable info i requested.
thank you much party people