yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] ellesshoo:
One more question. Is it possible to increase the bus/clock at specific steppings? For example set it such that it runs 100, 200, 400, 800, then 1100.
[Nexus S Android Development] Ezekeel:
You mean increasing the frequency and bus selectively for a single state? No and this is not planned. For once I see no benefit in that and secondly this would put Morfic out of business - and he might send his muscle from Brooklyn to break my legs.
[Nexus S Android Development] simms22:
i only do fingers, legs are to obvious :eek:
[Nexus S Android Development] polobunny:
Wouldn't that help for power saving? Having 100MHz at a low voltage instead of having 110MHz and a bit more voltage.

You could have the highest (or higher frequencies) overclocked through the bus so in high load situations it would perform better than "stock" CPU only OC.

Not sure it's worth the effort, if do-able and I get the feeling it would be hell to debug and correct the bugs though. Switching the bus frequency around all the time like the CPU frequency doesn't sound like the best thing to do.
[Nexus S Android Development] morfic:
run 400/1000 on a kernel and oddly enough, it saves more power than 100/1000, needs more testing, but looks like Franky is right on that one. o_O
[Nexus S Android Development] Maximilian Mary:
If I understood correctly, I thought Ezekeel added a deepidle patch a while back that makes it idle at 100 MHz regardless of min_freq.

I'm still not convinced that skipping the 200 step is the best way to go (though I will defer to the experts). I think it just means the governor has room for improvement. If the governor is not scaling correctly for optimal performance and battery life, it's not doing it's job.
[Nexus S Android Development] got2best:
I am having a problem.. I set live oc to 105 and then Raised all voltages by 15 .. and set minimum at 105 and Max at 1050 .. still reboots within an 1/2 hr. Any ideas?

sent from my Nexus S i9023 from XDA premium
[Nexus S Android Development] thoth77:
Stock Voltage

Down the voltages to the stock value
[Nexus S Android Development] polobunny:
I might have misread (or my memory is doing me wrong) but I don't think that's the case.
[Nexus S Android Development] got2best:
Ok I will try that thanks.. I wanted to set the live oc value to 110 .. and i fallowed the voltages on the first page raised all by 30 but it doesn't work .. any ideas for that one?

sent from my Nexus S i9023 from XDA premium
[Nexus S Android Development] thoth77:
Stock, Enough

In my experience, to +10% Live OC, the stock voltages enough and ironically stable.... no reboot
[Nexus S Android Development] Zorrich:
I was having a similar experience until I tried streaming video. It froze my phone within 10 seconds 3 times in a row. I up'ed the voltages by 30 each and played fine.
[Nexus S Android Development] thoth77:
Set Voltages

In Live OC, Setting the voltages is delicate
[Nexus S Android Development] got2best:
Tried up 10% with stock voltages and it still froze :/ any more ideas?

sent from my Nexus S i9023 from XDA premium
[Nexus S Android Development] thoth77:
Kernel Dev

Finally, ask the kernel dev about the adequate voltages...:confused:
[Nexus S Android Development] Zorrich:
I up'ed the voltages by 30 each and it has been working great. I believe that is what Ezekeel also recommends in the very first post of this thread.
[Nexus S Android Development] thoth77:
I want to know

The first post

☞

raise each

or

raise the only for max freq
[Nexus S Android Development] got2best:
Yep I did that also and no go.. reboot after about 1/2 hr

sent from my Nexus S i9023 from XDA premium
[Nexus S Android Development] yaronyud:
i got rid of live_oc and you can do what i did and it work just great..

set.MIN->400 , set.Max->1300 and the phone just moves great....

yeah it wont raise your bus stuff but it still work great...

if you want i heard somewhere that formatting system and wiping data and than reinstalling ROM and Ker than try it... it should work
[Nexus S Android Development] got2best:
Just tried the new rom and kernal.. reboot! Lol.. stinks :/ .. I will try the 400-1300 and c how that works for me.. what governor are you using?

sent from my Nexus S i9023 from XDA premium
[Nexus S Android Development] got2best:
Would surface dithering cause problems with this? .. because I turned mine off and it seems to b fixed...

sent from my Nexus S i9023 from XDA premium
[Nexus S Android Development] morfic:
if you want people to push for higher bus speeds, you should include a progressive option to raise DVSINT1 as bus goes higher.

This would allow more phones to run a higher bus speed.

Raising the cpu voltage will not help them get 240MHz + Stable, some lucky ones might anyway, but only pushing cpu voltage is limiting the number of successes.
[Nexus S Android Development] franciscofranco:
Yes. My phone works at 250 bus speed, but causes some strange issues like Launcher 3D app drawer being ****ing slow and sluggish and some menu transition problems and I get one or two reboots in a while.
[Nexus S Android Development] simms22:
if youre running a cm based rom, try disabling surface dithering and enabling allow purging of assets in cm settings, performance.
[Nexus S Android Development] franciscofranco:
Nah, Oxygen all the way for me. I'm fine with live_oc = 110, just answered morfic's post to give Ezekeel more info about the 250 bus speed thingy.
[Nexus S Android Development] simms22:
ahhh.. cool :)
[Nexus S Android Development] mike216:
So allowing purging actually does a good job freeing up memory

I love nscollab and you know we need all the memory free we can get on these great cm based roms

I know disabling dithering allowed me to liveoc on stock voltages without a reboot on franco's 27th beast of a kernel! I'm actually very satisfied at 1000 because I'm able to undervolt 40 across the board

Sent from my G1
[Nexus S Android Development] kecinzer:
I know, that this is kind of OT, but can someone explain me, what this voltages means?

DVSARM1

DVSARM2

DVSARM3

DVSARM4

DVSINT1 - now I know, that this is bus voltage

DVSINT2

Thanks for explaining.
[Nexus S Android Development] yaachi:
DVSARM - cpu voltage

1,2,3,4 are for different cpu levels like 1000mhz 800mhz 400mhz 100mhz

see

http://morfic.euroskank.com/git/?p=linux-samsung.git;a=blob;f=arch/arm/mach-s5pv210/cpu-freq.c;h=cd89569212083f4462f320f988c47c41a980cfd2;hb=1d9844f3a13c02eeff077c341df5073897910cfe#l84

and they are defined here:

http://morfic.euroskank.com/git/?p=linux-samsung.git;a=blob;f=arch/arm/mach-s5pv210/include/mach/voltages.h;h=8a1400164e0e924633506d4180db6d6ff9d27a92;hb=1d9844f3a13c02eeff077c341df5073897910cfe
[Nexus S Android Development] Flying Fox:
Great job, have I mentioned yet?

The thing I don´t understand is, how to change the init.d file. I´m no dev and obviously didn´t quite understand what to do.

In the 92kernelconfig-file (/sys/etc/init.d) I changed the oc_value to 120 and in the 83aroc file the settings for min/max frequencies. But my device didn´t respond to the new settings.

Im running Miui KelLMSKing MIUI 2.4.1 and Franco.Kernel 11/2 and was using ES file explorer.

When writing "echo "120" > /sys/class/misc/liveoc/oc_value" into the Terminal Emulator everthing works fine - but of course only until the next reboot.....

Any idea why my changes had no effect to the bus-speed?

Anyway, many thanks for this mod!!!!!!!
[Nexus S Android Development] thoth77:
Exceed +20%, dangerous

Exceed +20%, dangerous

Many users of the Nexus S community exceeding +20% in Live OC,

lost their IMEI... data connection broken.

"only Emergency Call" sign

I must have my Nexus S repaired tomorrow (+25% LiveOC):(

Everyone, Let's efs backup before the accident

http://xdaforums.com/showthread.php?t=1138873
[Nexus S Android Development] Ezekeel:
Yeah. I did not think about that. Probably I should implement a proper custom UV interface that can also change the internal voltage.

Hmm. This is the first time I hear that LiveOC is suspected to have caused a serious problem like that. So, how many are 'many users'?

I guess it is possible that due to some OC the device cannot handle the efs partition got scrambled. The partition is mounted read-write and I once tried to remount it to read-only on boot for security reasons, but I got problems with the mobile connection. So something is writing to the efs partition and if the device crashes during that write operation this might lead to corrupt data. But this potential danger is not limited to OC with LiveOC, but can always happen if one operates the device outside of its specifications. So yeah, always backup your efs partition.
[Nexus S Android Development] polobunny:
I'm thinking like you that most people with issues like those probably got their data corrupted. That's the price you're ready to pay if you overclock any component, your data integrity might take a plunge if you get to the point where it's not stable...

Guess it's time for a word of warning to fend off the beginners. Something along the lines of "your dog might get hit by a car, your girlfriend might leave you, your boss might fire you and your father might disown you if you overclock your phone. Nobody's responsible but you". :P
[Nexus S Android Development] caleb1783:
too late for da warning... spending more time w my phone than my girlfriend...!

maybe it was good idea to have max limit set to 120...

Sent from Divinus Nexus S...
[Nexus S Android Development] thoth77:
5 members (all exceed +20%)

5 members (all exceed +20%)

These happened to some users of "bus speed up kernel of morfic" months ago

"But this potential danger is not limited to OC with LiveOC, but can always happen if one operates the device outside of its specifications. So yeah, always backup your efs partition"

That's XDA! :) We're the crackflashers!
[Nexus S Android Development] yaronyud:
say..

can anybody please explain why the maxfreq->on how it works..? and what are this advantage over not using this...???
[Nexus S Android Development] Maximilian Mary:
It pedals faster so it can coast more.
[Nexus S Android Development] psygbert:
This post deleted.
[Nexus S Android Development] matmat07:
I was on a 125% live OC, and I got artifact while doing a benchmark, then an SoD. Does it means I pushed it too far, or that voltage wasn't high enough? (was on 800mhz baze, so 1000mhz)
[Nexus S Android Development] seriouslyjeff:
I feel so dumb but how do I adjust the value?? What program are you using
[Nexus S Android Development] al_madd:
Go to market...download nstools..
[Nexus S Android Development] droidance:
I see many people are running Live OC = 110. How does it affect battery from 100? I having some lag when I try to unlock phone... sometimes I have to long press the power button to have the screen on, sometimes it doesn't work at all.. sometimes it works but there is lag when I hover the unlock button.

Will raising Live OC value to 110 help? I'm running CM7 latest KANG + TEUV 11/14 880 / 100 lazy
[Nexus S Android Development] Ezekeel:
That is not an issue with Live OC, but with the way Morfic has decided to implement DEEP IDLE in that version of his TEUV kernel.
[Nexus S Android Development] NicholasQ:
My phone doesn't seem to like anything above 112 % :(. In nstools I've seen a setting for 150%. People actually make it to that?
[Nexus S Android Development] Bradart:
Mine barfs at anything above 107
[Nexus S Android Development] NicholasQ:
Yea I've raised by voltages and been able to get 115 but it doesn't last long before I start getting force closes and reboots.
[Nexus S Android Development] polobunny:
Not that I'm aware. 125 seems the absolute highest some people were able to hit. Keep in mind not all phones are alike. I cannot seem to get anything past 110 to be entirely stable.
[Nexus S Android Development] NicholasQ:
Yea, I am aware of phones having different tolerances. I was just curious as to how below average mine is. Seems like my phone never ran reliably above 1.2 Ghz and anything about 112 ish in liveoc seems to cause problems. Damn. :mad:
[Nexus S Android Development] polobunny:
Do not confuse CPU overclock and LiveOC (which overclocks the bus, thus bus, GPU and CPU).

Your phone might be able to run a 1.2GHz overclock on the CPU but not the bus at 112%. Or not on the GPU.

You have to do trial and error to make sure you understand the limits of your phone on every setting to be able to find the "sweet spot".
[Nexus S Android Development] djjonastybe:
I was wondering if we could set values lower than 100 with liveOC. The values seem not to be working.
[Nexus S Android Development] NicholasQ:
I am not confusing them. That's why I said I could never go above 1.2 Ghz on an overclock AND (in a separate occasion) I could never go over 112% on liveoc. I can see where maybe I wasn't clear enough. Seems like my sweet spot is 1.1-1.2 ghz with no more than a 112% live oc.
[Nexus S Android Development] phone_user:
CPU, bus/GPU and DRAM! It is “innovation”.
[Nexus S Android Development] polobunny:
No you can't. Recent changes to NSTools reflect this, having a slider instead of values you can input.
[Nexus S Android Development] djjonastybe:
I currently use liveOC at 105

Well a great initiative would be to make a thread about liveoc, voltage values, clock speeds etc...

So we can have big big list and eventually make some kind of graph to calculate the safe zone, the average results people get, and so on.

Even we know all phones are different it is possible to calculate these results. So we can have a summary report for all nexus s based phones.

I can only recommend testing these without deep idle.
[Nexus S Android Development] jacobuscuracao:
a guy said he did that and it crashed his screen
[Nexus S Android Development] Ezekeel:
A friend of my cousin did this and his neighbour's cat exploded. True story.
[Nexus S Android Development] Realtyem:
I needed a good LOL, thanks man.:p
[Nexus S Android Development] OCedHrt:
I have been curious about the battery drain on ICS as well. I'm new on Nexus S so am not sure what the normal drain is, but it's so far pretty bad so I have been doing my own testing. I have rotation turned off and and CPU spy shows 80-90% deep sleep state but the drain is still about 10% an hour on idle. This is with matrix or glados credit kernels.

The point I'm trying to make is that it may not be all CPU related.
[Nexus S Android Development] BitteredBro:
Hi.

I've been messing around with liveOC for a while trying to get the most stable and battery friendly combination.

The goal was to find the lowest battery consumption and the higher overclocking while retaining a fully functional phone (games, browsing, video play, etc.)

The attachment shows my findings. As you can see, I achieved some battery consumption reduction which resulted on an extra hour of "Screen On" time. I got to say that I only changed the CPU voltages and let the Int voltages stock, so these results could be improved, but consider these results as the best my phone can do. Higher OC resulted on reboots and Lower voltages resulted on SOD.

While doing these tests, more questions came to my mind.

1.- More overclocking step are more battery efficient? The way I understand it, lower number of steps could force the system to work at speeds unecesary high sometimes, which in the long run would result on higher battery consumtion, but I dont' have enough knowledge and can't figure a way to test these asumption.

2.- At which point the LiveOC performance gain equals the normal OV performance gain? Lets say I LiveOC to 20% with max Speed of 1000 Mhz. It's equally fast as if I normally OC to 1200 MHz? Theoretically it sould be faster because of the Bus and GPU overcloking. But what happens when the speed achieved using normal OC is higher than the attainable with LiveOC?

3.- Take a look at the purple and red lines. It would seem the purple one is faster than the red one, but It uses smaller LiveOC value. Wich one is better performance wise?

4.- Why can I UV more with one group of settings than the other? The red line resulted of using 200 Mhz bus speed (Glitch kernel Beta 3), the others using 217 mhz (Glitch Kernel Beta 2). I think it got to do with the results of multiplying the bus steps with the LiveOC value. Sometimes the resultant number wasn't an integer and then the phone freezzed or the GUI stuttered. I think thats the reason but again, I don't know.

Maybe someone can elaborate on my findings and lend me a hand in understanding more about LiveOC.

Thanks in advance.
[Nexus S Android Development] :
Can you check my battery thread please?

kernels ; battery ; ROM ; gov/sched
[Nexus S Android Development] Enyo.:
Does Overclocking fry our Exynos 3110 (former Hummingbird) processor?

Is heat the only killer, or is it the higher frequencies too?
[Nexus S Android Development] byeonggonlee:
[MOD] Selective LiveOC

I like this MOD. Except one(applies to ALL frequency).

So I fixed it once. It works fine. So I want to show this MOD. :)

This MOD is based on LiveOC(Is it natural? :D)

This MOD applies 'LiveOC' 800MHz and above. If you want to change. You just change the value '800000'.

This MOD's source is here.
[Nexus S Android Development] android_nexus:
Wow, great! :)
[Nexus S Android Development] nexus_junkie:
Live OC above the selected freq?
[Nexus S Android Development] androidphone2012:
General users can change the oc target?
[Nexus S Android Development] byeonggonlee:
I've fixed more.

now you can change this value.

/sys/class/misc/liveoc/oc_target -> value is here

source is here

---------- Post added at 11:03 PM ---------- Previous post was at 11:02 PM ----------

yes. you can change value through "/sys/class/misc/liveoc/oc_target"

if you want to change 1000MHz. Change the value 1000000. then liveoc applies 1000MHz and above. Below frequencies are not applied.
[Nexus S Android Development] reference.phone:
sounds promising, cool! :)
[Nexus S Android Development] 93ae8074:
Sounds nice. What about bus frequency? How is it affected by your changes?
[Nexus S Android Development] morfic:
Nice fix to liveoc, even if i won't use it, the way you changed it in my opinion is "right".

Thanks for this.
[Nexus S Android Development] novic_dev:
Thanks!!!

Thanks!! Using your MOD in AniDroid Hardened Kernel
[Nexus S Android Development] byeonggonlee:
Thanks. It is feeling good to be praised by my favorite kernel's developer.

---------- Post added at 10:11 PM ---------- Previous post was at 10:07 PM ----------

I've modified 'a little'. So other features are same as LiveOC.

---------- Post added at 10:19 PM ---------- Previous post was at 10:11 PM ----------

Thanks :). I will look forward to your next version.
[Nexus S Android Development] 93ae8074:
Which means that even changing just one CPU frequency the bus frequency it's gonna be changed too. Innit?

So if I change 800 MHz. to 880 MHz. it implies a rise in bus speed from 200 MHz. to 220 MHz. What happens if at the same time I change 1000 MHz. frequency to 1050 Mhz. frequency? Is it gonna change bus frequency to 210 MHz?

Cheers.
[Nexus S Android Development] nexusphone:
This patch, not different percentage oc value at Each frequency but setting oc_target, only above frequencies applied live oc

Sent from my Nexus S
[Nexus S Android Development] 93ae8074:
I beg your pardon.
[Nexus S Android Development] Harbb:
It will apply liveoc to all frequencies at or above what you set in that file. All frequencies below are not OCed, all above are.
[Nexus S Android Development] 93ae8074:
So every different frequency is gonna have a different bus speed. Ok, nevermind, I'll check the freaking code myself.

Cheers.
[Nexus S Android Development] simms22:
yes. with live oc every percent you raise the cpu, you also raise the gpu.
[Nexus S Android Development] chalan30:
thanks for this mod! it seems like a great implementation. do you have any ideas as to having the mod apply to freq below the target, instead of freq above the target. this would give the ability to benefit from higher BUS at lower CPU freq without having to worry so much about stability issues at higher CPU frequencies ? so theoretically i could set the target at 800000 and live oc at 105 and my CPU freq would be overclocked up to 840 but then 1000 1200 1300 and 14** could stay the same. Or am I just missing the point :p
[Nexus S Android Development] byeonggonlee:
Sorry to late reply. It is not difficult. I'll do&upload later.
[Nexus S Android Development] byeonggonlee:
Hello. I was added lower/higher frequency limit on MODed LiveOC.

See this :)

(I was consulted https://github.com/DerTeufel/samsung-kernel-aries/commit/923fcd92cc40c1ba5e93c419f3edd9fcb7a69303)
[Nexus S Android Development] DerTeufel1980:
great :)

i have removed the limit for traget_low <= target_high and vice versa, and also added one more "if" to cpufreq.c, now the values can be "switched" and live_oc can be applied to all freq, which are NOT between the two limits. i'll send you the commit later. maybe you find this useful, too.
[Nexus S Android Development] byeonggonlee:
What a great idea! :)

Your commit is better than mine. I'll modify later.
[Nexus S Android Development] byeonggonlee:
I've SLIGHTLY fixed DerTeufel1980's commit.

Fixed commit is this

Great Thanks to DerTeufel1980.

====Previous commits====

[MOD]Selective LiveOC

[MOD]Selective LiveOC - Fixed it more - you can change this value now :)

[MOD] Add Lower/Higher Frequency Limit on LiveOC

[MOD] Modified some conditions of LiveOC
[Nexus S Android Development] Lalaca:
So, err... how does the end user make use of these new modifications?
[Nexus S Android Development] Harbb:
Ask your favourite kernel dev (nicely, of course) to implement these changes in their kernel - or alternatively build your own kernel from source with the above edits and possibly some other mods.
[Nexus S Android Development] ljordan2:
I believe that Air kernel has already incorporated it.
[Nexus S Android Development] androidphone2012:
"Selective LiveOC MOD" works well on Air Kernel v3.5 :)

echo "800000" > /sys/class/misc/liveoc/oc_target_high
echo "400000" > /sys/class/misc/liveoc/oc_target_low
echo "120" > /sys/class/misc/liveoc/oc_value
[Nexus S Android Development] Lalaca:
This was what I was after. I keep up with AIR kernel; I just needed to know what changes I needed for my init.d script.

Cool!
[Nexus S Android Development] DerTeufel1980:
based on the idea of stratosk, and the way ezekeel exports the live_oc freqencies for gpu_min_freq, i have fixed smartassV2 governor to use freq according to liveoc value.

i did not push the changes to git yet, but you can find the fixed smartassV2.c and the exported values from cpufreq.c here:

http://pastebin.com/P1VC62Mj

many thanks also to byeonggonlee, who pointed me to a commit for fixing the userinterface (this commit can be found here: https://github.com/abev66/linux_NS_ICS_vilta/commit/ad316c6049c6ce07b6bc01fd1778b8567efa9bc2)
[Nexus S Android Development] DerTeufel1980:
maybe some of you have noticed, that selective live_oc is causing some instablilties, and some freq are sometimes live_oc'ed, although, they should not.

i have found the issue with it now. the apll_value is not set correctly, when low freq are not live_oc'ed.

to avoid this, please take a look at my fix:

https://github.com/DerTeufel/samsung-kernel-aries/commit/1878f55599330eb5a39eee2280222c18fab4351f
[Nexus S Android Development] byeonggonlee:
Thanks. But I am busy preparing for the midterm exam. So I'll try that after my exam.
[Nexus S Android Development] drktigger:
Is there a maximum limit you should try to keep under for the arm voltage?
[Nexus S Android Development] RcrdBrt:
1500 mV for the arm voltage is a good limit for 1400 mhz

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] KOala888:
I have tried to add live oc to my kernel, my device has same cpu and gpu as nexus s.

Our community uses gingerbread kernel with initframs changed to be more cm9 cyanogenmod friendly.

I have done everything like there:

https://github.com/Ezekeel/GLaDOS-nexus-s/tree/liveoc

But my device bootloops on samsung logo, any idea? Had anybody gone through similar problem?
[Nexus S Android Development] :
Do you have a github?