yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] @rbiter:
Bumped 350 mhz to 750mv from 735. Woke up to a crashed phone. Other crashes have rebooted so it might've been the charger bug.
[Samsung Galaxy Nexus] rabug:
1.4Ghz running fine on my SC04D device... still testing lower voltages.
[Samsung Galaxy Nexus] dnlsmy:
I don't know if anyone has asked this yet, but for those who are able to get the 1.4GHz Kernel to boot and work successfully, was your device originally a yakju or yakjuwx or other?
[Samsung Galaxy Nexus] aron7awol:
I would expect a screen off cap to lower efficiency as well, since the CPU has the highest speed to voltage ratio at the highest level. Let it clock up and get the work done at its most efficient state, and then clock back down to save power while it's idle.

Edit: Of course, if you don't care about performance while the screen is off, which is certainly a reasonable stance to take, having a screen off cap will certainly at least save some battery life.
[Samsung Galaxy Nexus] pukemon:
yes. i actually think bumping up my profile for screen off in setcpu from 350/350 to 350/700 helped standby a little bit. for a small bump in voltage you get twice the performance when phone is standing by. i haven't seen a noticeable improvement, but it makes a lot of sense, especially since this chipset has 4 stepping frequencies.
[Samsung Galaxy Nexus] michaelearth:
Since we cant yet overclock the CPU very much, has there been any work on trying to push the GPU past 380mhz?
[Samsung Galaxy Nexus] steveeJ:
first of all, THANKS for the work!

i'm currently running your kernel but haven't flashed it yet.

i seem to be lucky since i don't have any problems so far.

can you tell me where you got the config for the kernel?

i wanted to grab /proc/config.gz but it's not there :-/

thanks again!

greets

stefan
[Samsung Galaxy Nexus] dario3040:
Coolbho stated that he ran it up to 512 mhz, and did some benchmarks.
[Samsung Galaxy Nexus] michaelearth:
Are you serious? Maybe I know nothing but that seems like a huge overclock for a GPU on a phone! Am I wrong? Plus since most of the stock rom's GUI is done on the GPU (plus rooted roms are putting full GUI actions on the GPU) this will yeild amazing performance results in the GUI and Games.

im ecstatic right now!
[Samsung Galaxy Nexus] darrendm:
I would imagine that a 512mhz overclock would make heat a (major) issue?
[Samsung Galaxy Nexus] pukemon:
it's only a 128mhz overclock. it does seem unusually high for a mobile phone gpu, but mobile gpu's have come a long way the last 3 years or so. i wonder how much performance it adds since the 540 is no slouch even though people write it off as so because it's ~2 years old.
[Samsung Galaxy Nexus] steveeJ:
has anyone seen a difference between the different cpu governors regarding stability?

i have a feeling with "hotplug" it's not as stable as with ondemand or interactive.
[Samsung Galaxy Nexus] sluflyer06:
Go one stepping at a time, lower it 25mV at a time, stress test it, benchmark it, game on it, sometimes i lock it to each stepping and use the phone a bunch on it. Its really just trial and error.

What I have found and nobody has mentioned that I've seen is that before it gets unstable the scores in benchmarks will start falling off when the voltage gets to low even though the phone is seeming to run fine.
[Samsung Galaxy Nexus] schriss:
This is when CPU is handling increased number of errors. This is why when overclocking or undervolting desktop CPUs we use Prime95, it will report these errors before you even see any app crashing. Its possible because Prime95 is expecting a number in certain range and notifies when CPU starts to misbehave due to too low voltage. I think its not ported to android yet.
[Samsung Galaxy Nexus] b15love:
could you be so kind to post up the kernel with the GPU @ 512MHz
[Samsung Galaxy Nexus] Shodney:
That's interesting. I don't know any real way to test the undervolt properly, so I just run a few stress tests and test it in normal usage over a week or so. If the phone doesn't hang or reboot during that time, I assume the undervolt is fine.

Presumably though, from what you and schriss are saying, even though the phone seems to be running fine it may potentially be struggling with additional CPU errors which could actually have a negative effect on battery? (through reduced performance)
[Samsung Galaxy Nexus] schriss:
Real way to test undervolt would be to use an application similar to desktop PC application called Prime95, which calculates prime numbers. By doing this, it knows what to expect and when cpu returns value out of expected range, it throws an error. Prime95 has been used by overclockers for years.

See this thread: http://xdaforums.com/showthread.php?t=1389827

which I created asking if someone could port this tool or create one (it might be fairly simple app). That app would need to run calculations and warn when values are out of range. You might have heard about stress testing graphics cards, you stress it and software is looking for artefacts on the screen, when you find 1 or more - you found your limit. Healthy card could be stressed indefinitely without producing a single artefact. That's having a "rock stable" card or cpu.
[Samsung Galaxy Nexus] Luxferro:
There's a SuperPI add in the market (free) that will calculate PI (3.14) out to like 512,000 decimals if you want to check it (i've only tried up to 64,000 decimals):p
[Samsung Galaxy Nexus] schriss:
Prime95 was designed to highlight computing errors, this app I'm not sure. It might always produce correct result as cou will deal with errors to some extent and eventually when pushed too hard the app might simply crash. Not sure if it would display invalid result when undervolted too much, that's what I mean.
[Samsung Galaxy Nexus] dnlsmy:
Any luck getting the Kernel to work on devices that slow down at 1.4GHz? I still can't reach it yet on my phone.
[Samsung Galaxy Nexus] Riztnack:
Will this kernel support verizon LTE?
[Samsung Galaxy Nexus] Natolx:
Neither of these kernels booted past the Google logo for me on my LTE Galaxy Nexus
[Samsung Galaxy Nexus] rabug:
ICL53F won't boot neither... stuck at google logo.
[Samsung Galaxy Nexus] VoicesX:
Wait update for ICL53F YAKJU (Android 4.0.2) (3.0.8 kernel)
[Samsung Galaxy Nexus] jopherr:
hey guys. i have a question. does temperature influence how much voltage is required for the processor? I ask this because in my room, ~70 F all parts of my Gnex function fine at

1200 MHz : 1150

920 MHz : 1000

700 MHz : 925

350 MHz : 850

however, when i went outside where it was ~40, my phone would constantly freeze and reboot a minute later. at the lock screen, messaging app, setcpu start screen, setcpu voltage changing screen, pretty much random freezes.

I had to change it to:

1200 MHz : 1300

920 MHz : 1175

700 MHz : 1000

350 MHz : 900

to make it stable for usage.

now that I am back in my room, 1150 works just fine @ 1.2 GHz

its so strange yet frustrating :C

anyone have thoughts?
[Samsung Galaxy Nexus] pukemon:
no but everything else on the SOC and fluctuations can influence it. especially radio signal, games, anything else sucking up voltage and i'm thinking screen brightness now. i was running my screen at 10% for 2 days stable and i had to bump it up yesterday evening because i was outside and my phone crashed twice, once when i received a call on bluetooth and it crashed. so i had to bump it back up. if you don't need absolute stability, go with the lower voltages and bump them up 5mv or so after a crash. if stability is high priority start with the higher voltages and bump down 10mv or so every 12-24hours.
[Samsung Galaxy Nexus] :
Temperature will have an effect on the voltage required to keep your processor stable. When hotter, semiconductors will usually experience a decrease in resistivity. Since:

Power supplied to processor = Voltage² / Resistance

You can see an increase in resistance, caused by the phone running cooler outside, will reduce the supplied power to the processor. Assuming that the voltage is constant. To maintain the same power supplied to the CPU, an increase in voltage would be required.

Correct me if I'm wrong someone, only applying some of my own logic here, not something I've read in a book and know for sure.
[Samsung Galaxy Nexus] KiNG OMaR:
I've been using these voltages for well over a week now without any hiccups. Took a lot of fine tuning on each frequency step, but this is what I am happy with now. No crashes/reboots for well over a week. Posting these for anyone else who would like to try and doesn't know where to begin ;)

1200 Mhz - 1125 mV

920 Mhz - 1000 mV

700 Mhz - 925 mV

350 Mhz - 800 mV
[Samsung Galaxy Nexus] jopherr:
xD do u think its possible to make a script or what not for tasker/llama so that at certain times of the day (night time which is cold vs day time which is warm), the undervoltages would change?
[Samsung Galaxy Nexus] sluflyer06:
I can't say I agree with that at all. Coming from personal experience back in college I used to be into the competitive overclocking scene for computers. I was running processors down to -74C with a custom blended refrigerant system and the colder you get a semiconductor the more stable and faster speeds it will be able to run given other variables remain constant.

I really couldn't hypothesize why his phone is getting unstable when its colder out other than at some point the voltage in the battery is going to start dropping as battery temperature drops, so if the undervolt is right at the limits of stability ANY small change somewhere is going to cause problems.

I keep posting in threads that people should run benchmarks at stock voltage and record the values and then keep running them at different undervolts, I discovered that performance starts to drop before any stability problems crop up which means the hardware is not happy even though its not crashing or causing FC yet.
[Samsung Galaxy Nexus] dario3040:
You could always try Tasker.
[Samsung Galaxy Nexus] psouza4:
Erm -- you didn't read his question, did you. He's asking if Tasker is capable of touching clock speeds. :P
[Samsung Galaxy Nexus] KiNG OMaR:
Am I missing something or does this just not boot on ICL53F?
[Samsung Galaxy Nexus] Joe92T:
I dont understand why 1.4ghz is a barrier I thought it was my understanding that the CPU in our phones native clockspeed was 1.5ghz n Google just UNDERclocked it... u think we should atleast get the stock 1.5ghz up to like 1.8... freezing at 1.4 is weaksauce
[Samsung Galaxy Nexus] mortzz:
Read the thread. The reasons are clearly explained.
[Samsung Galaxy Nexus] dbum:
Same for me.
[Samsung Galaxy Nexus] nosympathy:
thread OP hasn't been touched since december 8th, so this kernel is not set to run on the new update.
[Samsung Galaxy Nexus] dario3040:
I seem to miss the small details lately...

Either that or he Ninja'd me
[Samsung Galaxy Nexus] dwallersv:
Sorry to break it to you, but you're wrong.

Electrical resistance increases with temperature.

The physical phenomena is complex, but a simplified way to think about it is this: Heat in a solid is simply the vibration of atoms. As a conductor gets hotter, the constituent atoms in the crystal lattice vibrate more vigorously, banging in to electrons and impeding their flow.

Like I said, it's not truly that simplistic (the complete explanation involves quantum mechanics and the behavior of electron wave functions interacting with the wave functions of "phonons" and nuclei), but the above gives a fair picture.
[Samsung Galaxy Nexus] fatsix:
You are correct. I deal with this daily on a much larger scale. If it gets hot enough it will start effecting the voltage because of the increased resistance.
[Samsung Galaxy Nexus] slackwaresupport:
is this for GSM or LTE?
[Samsung Galaxy Nexus] slackwaresupport:
hello?? is this thing on??
[Samsung Galaxy Nexus] kerms:
its for GSM
[Samsung Galaxy Nexus] :
I'm aware that I simplified the problem, but was only attempting to realise a logical deduction to the problem.

While it is true that electrical resistance increases with temperature for almost everything, this is not always true for a semiconductor. Over a small temperature range (usually the operating temperature) resistance can decrease with temperature in semiconductors.

I'm supposing on a near quantum scale of processors, the extra kinetic energy of atoms going around a chip when hotter can lower resistance. Like I said, I'm no electrical engineer, but resistance decreasing with temperature is certainly possible in a silicon chip.
[Samsung Galaxy Nexus] Audionut11:
Got my CPU to run at 900mv @ 1200mhz and instant crash at 850mv. Going to settle for 925mv (for now).

Currently testing 920mhz with 675mv.

Looks like lowest I can go is 600mv which I reckon the CPU will happily run with at 700mhz.

Crazy voltage drops from stock.

Be interesting to test battery consumption after I confirm voltages.

Can't wait for franciscofranco to add OC to his kernel. See what this puppy can do.
[Samsung Galaxy Nexus] @rbiter:
Way too low. Instability.
[Samsung Galaxy Nexus] Audionut11:
Indeed. Would benchmark fine at very low voltages on the performance governor. But once I went back to ondemand it would cause a crash.

Currently running these voltages for 12+hrs with no problems.

975mv @ 1200mhz

800mv @ 920mhz

700mv @ 700mhz

650mv @ 350mhz
[Samsung Galaxy Nexus] pukemon:
probably way too low still. trust me. i thought i was good twice on two 48 hour runs and i still got booted. you will probably have to come up at least 50 on those. -300mv+ did fine on stress tests but the daily grind got me in a bind. i'm running 1141, 978, 877 and 759 atm. i think i could run my 1200mhz, 700mhz and 350mhz voltages back down. my 920 voltage has been hurting me. i bumped it up 15mv today after the 3rd crash and my others 2 or 3mv twice today. 33%+ uv's just don't happen. and if they did, that would piss a lot of people off at the high stock voltages. i don't think anybody is running 1200 @ less than 1000mv stable, much less 1100mv. and we're running with 45nm chipsets, not 32nm.
[Samsung Galaxy Nexus] Audionut11:
I must be imagining things then :p

All CPU's are different. ;)
[Samsung Galaxy Nexus] T6D16C84:
I can't even get the kernel to boot, when I run a test boot all I get is the hang on the google logo.....
[Samsung Galaxy Nexus] RieGo:
edit: sry wrong post :D
[Samsung Galaxy Nexus] mikeacela:
What might be some of u guy's set cpu profiles? I don't have much experience with voltages but really want to scale back battery life, so i was just curious as to what set cpu profiles you might be using? thanks
[Samsung Galaxy Nexus] @rbiter:
If you want to be conservative, start out about 100-150mv. If stability isnt a big concern and you want to be agressive start about 300mv uv'ed. Then work your way down or up5-10 mv at a time. Setting your min max on one frequency amd doing a stress test will also help some.
[Samsung Galaxy Nexus] Azdian:
I stuck at the Google Logo at the start up after flashing the file .. and ideas?

Im runing android revolution hd 2.1.2
[Samsung Galaxy Nexus] mikeacela:
Is this compatible with CDMA? or is it GSM only?
[Samsung Galaxy Nexus] @rbiter:
Probably gsm only. I think it is just a patch so it might work cdma version but definitely dont quote me on that.
[Samsung Galaxy Nexus] _Dejan_:
Im try it(fastboot boot gnex_oc_uv.img) on STOCK rooted GSM Nexus with ICL53F but do not work(Stuck on google logo)...
[Samsung Galaxy Nexus] ratson:
Are there any progress made on devices which have the stuttering issue? Or do you need anything like dmesg or other debug info?

Btw how can we check the gpu clock?

Thanks in advance
[Samsung Galaxy Nexus] ymr0211:
can i use this kernel with "Android Revolution HD™ 2.1.2"

I'm using Android Revolution HD™ 2.1.2 which is based on ICS 4.0.2.

Can i use your kernel for overclocking?
[Samsung Galaxy Nexus] skyhigh2004:
Well I've been running

1200:1100

920:975

700:875

350:750

For a week or so now. If I basically go any lower on any of the steps I get reboots. These setting have gotten me through any and all activities on my phone. Also these UV have been consistent across all the roms and kernels I've used.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Marco Schaap:
I tried to test this kernel on my IML74K AOPK build 9 ROM, if I execute fastboot boot gnex_oc_uv.img my screen is stuck on Google logo.. I'm now running Matrix 1.5 kernel and want to try this one but it will not succeed. Any ideas on this one?
[Samsung Galaxy Nexus] @rbiter:
Are they good with your profiles? I could go lower, but then i had issues with profiles so i started bumping up a couple mv on the 2 low frequencies. Been stable about 72 hrs now.

Crazy world, ay?
[Samsung Galaxy Nexus] stoneyfordni:
once i DL this kernal what do I do with it.

Reboot to recovery and flash Zip from SD?

I am using EAGLEBLOOD rom atm.
[Samsung Galaxy Nexus] ogdobber:
this kernel is for 4.0.1

fastboot install only

it hasn't been updated, nor do I believe it will be. I think the main purpose was to get the patch out for the devs;)

hence the name [DEVS/KERNEL]
[Samsung Galaxy Nexus] stoneyfordni:
Thanks for your reply
[Samsung Galaxy Nexus] ratson:
??? was this a reply?
[Samsung Galaxy Nexus] kyota:
Where is the next step of this kernel ? maybe we can try to skip 1.5Ghz and go to 1.6Ghz ? I don't know... maybe ?
[Samsung Galaxy Nexus] lollinope:
sorry guys, is this kernel working with Revolution HD 2.1.2 ROM?
[Samsung Galaxy Nexus] Marco Schaap:
Tanks for the reply! I'm an idiot ;-)
[Samsung Galaxy Nexus] reav:
uhm.... i dont think to use this mod... now 1.2ghz its enought
[Samsung Galaxy Nexus] dario3040:
Ok, if 1.2 is enough then don't flash it, your choice.
[Samsung Galaxy Nexus] AndyCr15:
I tried booting from the UV only and it stuck on the Google screen and didn't boot :(

Anyone else?
[Samsung Galaxy Nexus] jopherr:
This is for 4.0.1 I believe
[Samsung Galaxy Nexus] sblantipodi:
1.5GHz version will be out from Sprint soon.

no news on hitting 1.5GHz in a stable way?
[Samsung Galaxy Nexus] ogdobber:
either TI came up with a fix or they are running a different processor...I'm kinda thinking the fix came because of the "disable it for now" commit
[Samsung Galaxy Nexus] combatmedic870:
Google wouldnt do us like that would they?!?!?:confused:

Well we know its not a exynos processor....that wont run on 4g...i think i would be a little pissed is it had an omap5.:mad:
[Samsung Galaxy Nexus] jopherr:
Its higher clocked probably because TI was finally able to successfully bin the 4460 consistantly. Sorry to say it, but we early adopters got the crappier set of 4460s
[Samsung Galaxy Nexus] @rbiter:
Premature statement.

My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
[Samsung Galaxy Nexus] sblantipodi:
OMAP 4460S does not exist. where did you see the OMAP4460S?

is there anything official in this S version?
[Samsung Galaxy Nexus] dario3040:
He meant, 4460's.

Just a spelling mistake.

---------- Post added at 11:23 PM ---------- Previous post was at 11:22 PM ----------

I highly doubt it, Google wouldn't do that.

I bet it's a mistake on Sprints part, because TI have been trying to do this for more than a year, and now suddenly it works?
[Samsung Galaxy Nexus] sblantipodi:
What are you talking about? What are trying to do TI?
[Samsung Galaxy Nexus] jopherr:
Sprints LTE network won't be live until 2Q. Assuming this phone will be launched with a compliant LTE network available, the phone won't be available at least until early summer. That gives TI approximately 6+ months since it created our batch of 4460's and sent them to samsung's manufacturing plants. I think it is very possible TI will be able to make 1.5 Ghz 4460's by then. Sorry if this is confusing but I hope u get what I mean
[Samsung Galaxy Nexus] combatmedic870:
Hmmmm....I dont think TI would put out sub par 4460's.....They would just make them 4430's and be done with it. They are the same processor, just lower binned.

Either its a mistake, or they found a work around.

If they did find a work around, this is a good thing for us. Then we can begin to get the true power of the 4460 unleashed! I know this processor can get 1.8ghz!!!
[Samsung Galaxy Nexus] jopherr:
There are 2 differences between a 4460 and a 4430. The first is that the 4460 is supposed to be clocked higher. 1.5 ghz vs 1.2 ghz. The second is that the sgx540 in the 4460 is clocked higher @ 384 vs 300. HOWEVER. Google underclocked the sgx540 in the GN to 300 anyways to save battery. So we pretty much have a 4430 in our GN. That said. There are many kernels in this forum that OC it back to 384 MHz.
[Samsung Galaxy Nexus] combatmedic870:
I thought the 4430 was clocked at 1ghz...
[Samsung Galaxy Nexus] jopherr:
Ah yes. My bad. I was forgetting the 4430 was also in the Playbook and the bionic, not just the razr
[Samsung Galaxy Nexus] dario3040:
That's not my point, if they already made this advertisement saying 1.5 Ghz, then it has to be either:

#1. A typo

or

#2. TI made it work like it should.

I put my bet on #1

---------- Post added at 05:25 PM ---------- Previous post was at 05:23 PM ----------

TI (Texas Intruments) have been trying to make the OMAP 4460 run on 1.5 Ghz for a long time it seems.
[Samsung Galaxy Nexus] sblantipodi:
Can't understand how TI can try to run on 1.5GHz a 1.5GHz CPU. :rolleyes:
[Samsung Galaxy Nexus] Lox_Dev:
The sprint version will be clocked at 1.5Ghz ...
[Samsung Galaxy Nexus] itsjusttim:
That 1.8 is what I want.
[Samsung Galaxy Nexus] pukemon:
to do what? shave 300ms off a task? bigger benchmark numbers?
[Samsung Galaxy Nexus] itsjusttim:
To be honest, for fun. I don't care about bragging, benchmarks, or how much faster other things are. I like to push everything I have to the limit.
[Samsung Galaxy Nexus] pukemon:
they make racecars for that. or motorcycles. skydiving is more exhilirating. i need my phone for the long haul so i don' think i'll be shortening it's life span so i can tell everybody my phone can do 1,954,000,000 cycles a second. it just doesn't do it for me. nor do i need any nerds approval. i'll just stick to thanking the devs for getting us there.
[HTC Sensation] Wanderer_Zero:
*stands up*

Um.... My name is Wanderer_Zero and

i'm a ROM-a-holic.
[HTC Sensation] SuperSwaggtastic:
My name is SuperSwaggtastic and i too... Am a rom-o-holic...

*gasps all around*

[Rom: Alpha 10][Kernel: Faux 0.2.5b2]
[HTC Sensation] stonew5082:
Keep commin back.
[HTC Sensation] arzbhatia:
*Claps*

Welcome.. Welcome my friends.
[HTC Sensation] Dope Ex:
another ROM-o-holic says: WELCOME! :)
[HTC Sensation] vitusdoom:
welcome dude. rom-a-holic means, you devour roms? :D
[HTC Sensation] redbullcat:
Hello new people! Hope you enjoy your time at XDA :)
[HTC Sensation] Wanderer_Zero:
Well of course we devour roms!

Om nom rom nom!
[HTC Sensation] stroobach:
I'm stroobach.. and I'm a alcoholic ehm.. no wait.. what?.. I'm a flash a holic

:3

sent from my Nokia 3310
[HTC Sensation] unfnknblvbl:
What would I do without my sweet, sweet romahol and flashahol?
[Galaxy Ace S5830 General] droidtwoseven:
What's the SanGingerAce default font name?
[Galaxy Ace S5830 General] adeklipse:
You're gonna have more luck posting in the related thread rather than making a new one. :)
[Galaxy Ace S5830 General] droidtwoseven:
This is I think the fastest way to get the answer. LOL :D

Do you know?
[Galaxy Ace S5830 General] adeklipse:
Sorry, nope.

I haven't used a stock-based custom ROM in then last month ever since Behrad ported CM7 and other builds started popping up.

Sent from my GT-S5830
[Galaxy Ace S5830 General] sdotmouse:
SonySketch. You can get it from one of the font changer apps in the market. I think its the one made by jrummy.

Sent from a phone with an app.
[Xperia Arc Q&A, Help & Troubleshooting] BinaryXeroMedia:
Hi has anyone got the greenglow theme. I really want it but he has not got it on his thread anymore. If someone has it. Please please please pm me it or share here. I LOVE that theme. I always wanted it but never had the arc but now I have it I still can't taste that's sweet apple green on my phone. I want my phone to be alienated with the green alien glow.

Regards

Blackwatch