Hello all I just flashed new sense and I have questions. Which govenors and I/O schedulers are you running. My dalvik heap is 32 is there any benefit from changing the size? I am new at this any suggestions about my settings would be great.
http://bit.ly/MHiPOe
http://forum.xda-developers.com/showthread.php?t=1369817
Sent from my myTouch_4G_Slide using Tapatalk 2
If you notice any lag with the rom you can raise it slightly but be carefull not to raise it too high more than 40m. The more you raise it the more battery drain you'll get. Vm heap helps with memory.
Sent from my PG06100 using xda premium
Related
I was getting 10.5 but getting force closes so I wiped and reinstalled anyone know what caused this
You probably didn't reinstall SetCPU and overclock the CPU to 1.3. It defaults at 1.0.
Thx running 10.5 again
Sent from my SPH-D700 using XDA App
Sent from my SPH-D700 using XDA App
Cam3ron1 said:
Thx running 10.5 again
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Yup no problem.
Make sure you set it to minimum 200, maximum 1300 and scaling to conservative. Performance scaling should really only be used when you actually need the performance (Cause it takes more battery life), which isn't often with this phone.
Hey im just wondering what other peoples specs are for SetCpu?
12000-1000 is what I'm normally set at..
but as far as Voltage and Advance settings I don't know to much in these 2 area's...
so just curious in what people do with these options, and if it increases performance?
Kernal: Matr1x 11.5
Sent from my Nexus S 4G using XDA Premium App
I usually set mine to 1200 200 set it on lazy and its really smooth and very good battery life. I don't mess with the voltage.
Sent from my Nexus S 4G using xda premium
I usually undervolt and keep the stock 1000 / 100 (usually able to get about -75mV from each level w/ 100% stable. At -125mV I start to notice some instability.)
When I OC though I usually keep the voltage at stock and go 1200 / 250.
Anything over 1200 at stock and I find my phone starts getting unstable - everyone's is different though.
Interactive or Lazy Governors for both.
Currently running NexusBeam 4.1 and Glados 2.2.
Thinking about flashing back to ver. 3 though.
Thanks guys.. you guys dont touch options in advance?
Sent from my Nexus S 4G using XDA Premium App
Now that we have a new way to overclock in v14 there are near unlimited variables to overclocking with this kernel. I've found a good balance of performance with 1300ghz step and live OC value of 121%. Let us know what has worked for you. You may include voltages as well.
I'm using reborn90's settings
200-1000; 110% live oc arm volt; 800/950/1100/1175 int volt; 1000/1000/1000/1025
Seems rather steady, I also recommend turning save on boot in settings of nstools before applying these settings just in case xD
Sent from my SCH-I500 using xda premium
I am on 100-1300 with 116% Live OC, haven't played with voltage yet but everything runs great.
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
mleonm5 said:
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Do you UV first then live oc? Or is it just stock voltages?
Sent from my SCH-I500 using xda premium
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
mleonm5 said:
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
it depends on how far you phone can go, some can oc more then others but some less then others, I usually never go passed 1.2ghz ,I'd rather save battery.
Sent from my SCH-I500 using xda premium
Just my opinion, but since Android 4.0 relies so heavily on the hardware rendering capabilities of the phone you'd be better off to UNDERCLOCK the CPU to 800mHz, and apply the Live OC to say 125% and have an effective CPU speed of 1000mHz while increasing the GPU clock by the same amount. I've tried it and it works very well but I didn't stick with it long enough to see how it affected battery life. You will need to modify your voltages though. I was at 1250mV on the 800mHz step.
If anyone is interested in just using stock settings, i found this thread interesting:
http://forum.xda-developers.com/showthread.php?t=1424064
100-800 mhz, 125% live oc.
So how much of a change have you noticed from Stock kernel to Glitch. I tried OCing once.. and it froze.. and phone died.. and ended up having to wipe / re-flash. Probably user error though
Just wanted to say I accidentally OC'd to 1.4ghz with 110% LOC and man did this thing fly and didn't even crash.
Sent from my ICS Mesmerize
I noticed I'm able to achieve higher stable oc (over 1500) using low leakage voltage and live oc of 116 or less. Without low leakage i can barely acheive 1400 oc at anything over 110 live oc. Never noticed this much difference in internal voltage stability in previous kernel version. I wonder what's changed?
Hello guys,
I'm here to ask for all of your opinions about the cpu Profiles, frequencies and governor.
For screen on I'm currently using 1200mHz on performance, I would like to know if it would save more battery by using on demand governor.
Some months ago I had a discussion with few xda members about this subject. But that was on aurora v4. Now I'm currently on v5 u17. Let me know your opinion. Thanks
Sent from my U8800 using xda app-developers app
To be honest, I've never experienced any benefits of setting cpu profiles for screen on, screen off etc. Your phone will work much more smoothly if you stick as close to the defaults as possible.
I don't use profiles. My min is 245 and max 1200, using on demand governor.
For a while I experimented with profiles, and had bad lag when unlocking the phone, and terrible battery use when screen on.
Independent of profiles, your governor will put your phone into deep sleep when the screen is off anyway.
Do a search for "race to idle" this explains in more detail the benefits of using ondemand as opposed to other governors in terms of battery use etc.
IMHO, Android as a platform would be far better served if people stuck close to the default settings and cpu profiles. Most of the time, any negligible benefits are just placebo.
Sent from my U8800 using xda app-developers app
So according to the race to idle running with performance governor saves battery
Sent from my U8800 using xda app-developers app
In theory yes, but if your cpu is always running at max frequency, ie even when doing nothing, then no.
I have done tests, and my battery always lasts longer using ondemand as opposed to performance, or other governors.
Sent from my U8800 using xda app-developers app
Use interactive/bfq that's the best in my opinion
Sent from my U8800-51 using xda premium
Hi all, I have galaxy note 2 and I have flashed AOKP Rom a couple of weeks ago. I bought the Samsung 64 GB MicroSD Pro Class 10 Memory Card which has 70 read speed, 20 MB/s write speed but the music lags on any and every music app. In every 5 or so seconds, music stops for a split second and then resumes. I can't seem to figure out what the issue is.
Is the music lagging when you put the songs on internal storage?
Or maybe you can try to format the sd card.
Its because the kernel problem of some roms at pegasusq based go to the kernel settings and change cpu baseline ondemand or something else that not pegasusq
Sent from my GT-N7100 using XDA Free mobile app
drker said:
Its because the kernel problem of some roms at pegasusq based go to the kernel settings and change cpu baseline ondemand or something else that not pegasusq
Sent from my GT-N7100 using XDA Free mobile app
Click to expand...
Click to collapse
This seems about right. However, I've been through nearly all available governors on my current kernel with little improvement.
Raising the minimum cpu frequency to about 400 has helped but it's not an ideal solution.
Sent from my GT-N7105 using XDA Premium 4 mobile app
conantroutman said:
This seems about right. However, I've been through nearly all available governors on my current kernel with little improvement.
Raising the minimum cpu frequency to about 400 has helped but it's not an ideal solution.
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
maybe you have a lot of app that running in background or wakelock ? I have great at ondeman min cpu freq 200 and usin spotify.
I had this issue in both official and dn3 and tried raising min frequency to 400 mhz also 600 mhz still it does exist..
I didn't find this issue in OmniRom at all, and before that I had Samsung Touchwiz which also ran very smoothly, the lag is quite irritating during music. I have minimum amount of background apps (antivirus, facebook, gmail) as of now, still no improvement.
intl said:
Is the music lagging when you put the songs on internal storage?
Or maybe you can try to format the sd card.
Click to expand...
Click to collapse
Windows 7 allowed me to format the card in exFat format, I have tried that, I also tried fomatting the card via the phone itself, it still didn't get rid of the lag.
drker said:
maybe you have a lot of app that running in background or wakelock ? I have great at ondeman min cpu freq 200 and usin spotify.
Click to expand...
Click to collapse
Nope.
It's cpu related and when I used to use ondemand with my old 4.1.2 rom this was never a problem. Unfortunately the 4.2.2 kernel I'm on only has silly governors that cause more problems than they solve and ondemand is no longer an option for me.
Sent from my GT-N7105 using XDA Premium 4 mobile app
Thanks for the tips guys, I am using CPU Tuner now, I have kept the minimum frequency to 200 and music is playing nicely. I guess the default frequency was set even lower than that. Which would explain the unreal increase in the battery life that I was experiencing since I installed this rom on the phone.