Under-volting question - T-Mobile LG G2x

Ok I'm sure I'm going to get flamed and *****ed at for making a thread on this, but I cant find a guide on this anywhere.. lol.
I'm running Bionix 2 RC1 with Trinity15. I have plenty of experience with rooting and flashing roms, modems and kernels, and also over clocking. The only thing I haven't dabbled in is under-volting.
My question is, its there a thread on this that I have missed or is there someone that can explain the basics of what I need to know to properly under-volt using pimp my cpu?
Thank you very much in advance.
Sent from my G2x running Bionix 2 with the power of Trinity.

+1 for me also

Make a backup, trial and error

chillwill11 said:
Make a backup, trial and error
Click to expand...
Click to collapse
yea pretty much...
the safest process, or at least the one I would use is start with a base back, meaning stock voltages, no overclock or unvervolts... DO NOT DELETE THIS
now on your next boot up, set your overclock and take all of your voltages down 50mV. Run a stress test for 15 to 20 minutes, the longer the more accurate feedback you will get. Basically if your phone doesnt freeze or reboot you have a good undervolt. Now reboot into recovery and make a backup.
Rinse, repeat... make a new backup with your new voltages and from there I would go down in -25mV segments to be a little more accurate and basically just check for stability, if your phone is unstable then programs will freeze up or better yet your phone will just give you the old **** you and restart on its own haha
Typically I think stability at the top end speeds is best measured in the stress test and stability at the bottom speeds is best measured by the phone making it through the day without freezes or reboots... so the best way in my opinion would be to lower your voltages a bit each day until you find that breaking point where your phone becomes unstable...
cheers!

Good advice, thanks very much, I'll give it a go.
Sent from my G2x running Bionix 2 with the power of Trinity.

JHaste said:
yea pretty much...
the safest process, or at least the one I would use is start with a base back, meaning stock voltages, no overclock or unvervolts... DO NOT DELETE THIS
now on your next boot up, set your overclock and take all of your voltages down 50mV. Run a stress test for 15 to 20 minutes, the longer the more accurate feedback you will get. Basically if your phone doesnt freeze or reboot you have a good undervolt. Now reboot into recovery and make a backup.
Rinse, repeat... make a new backup with your new voltages and from there I would go down in -25mV segments to be a little more accurate and basically just check for stability, if your phone is unstable then programs will freeze up or better yet your phone will just give you the old **** you and restart on its own haha
Typically I think stability at the top end speeds is best measured in the stress test and stability at the bottom speeds is best measured by the phone making it through the day without freezes or reboots... so the best way in my opinion would be to lower your voltages a bit each day until you find that breaking point where your phone becomes unstable...
cheers!
Click to expand...
Click to collapse
Agree with this mostly. However, I actually recommend focusing your UV tweaks on the lower clock speeds. Since the goal is to conserve battery power, modifying your idle speeds will give you more benefit then the higher ones. Also, by not changing a ton of different voltage levels at once, you can fine tune a bit easier. I'm not saying to completely ignore the higher clocks, but you'll probably find them to be less tolerant of UVing anyway.
As a side note, never be afraid to make a new thread in Q&A. The rule of "search before you post" applies much more to development threads then to the Q&A section. Those who browse this section generally want to help regardless of whether or not the question has already been answered 100 times before.

MWBehr said:
Agree with this mostly. However, I actually recommend focusing your UV tweaks on the lower clock speeds. Since the goal is to conserve battery power, modifying your idle speeds will give you more benefit then the higher ones. Also, by not changing a ton of different voltage levels at once, you can fine tune a bit easier. I'm not saying to completely ignore the higher clocks, but you'll probably find them to be less tolerant of UVing anyway.
As a side note, never be afraid to make a new thread in Q&A. The rule of "search before you post" applies much more to development threads then to the Q&A section. Those who browse this section generally want to help regardless of whether or not the question has already been answered 100 times before.
Click to expand...
Click to collapse
totally agree! I am a nice helpful guy in the Q&A section but I will rip you a new one in the general section or dev section
on a side note... i really wish pimp my cpu would let me do custom undervolts D:

JHaste said:
totally agree! I am a nice helpful guy in the Q&A section but I will rip you a new one in the general section or dev section
on a side note... i really wish pimp my cpu would let me do custom undervolts D:
Click to expand...
Click to collapse
What do you mean by custom? Like more precise than 25mv increments?

Related

Ben's SuperD 1.8--"TwEaKeD"-by KNK (whoa)

first and foremost, if I've posted in the wrong place, I ask that a MOD kindly move it for me please...and you have my sincerest apology now, if its in the right place then disregard these words. Notice I said MOD, i don't need a bunch of people posting all the known comments like "this is in the wrong place" .."somebody ban this waste of space"..."learn how to read the forum rules"..."I'm tired of people posting here"...etc, etc. All that is not necessary, when a MOD can simply come right along and move it. If you insist on being a MOD "wanna be"..or a "tattle tell" (some refer to as snitch) Then just PM the CEO of XDA that Klyentel posted in the wrong place, who cares...as long as it gets corrected
EDITDONT WORRY ABOUT YOUR SWAP PARTITIONS,COMPCACHE,3RD PARTY SWAP APPS, AND YOUR FANCY LITTLE USER CONFIG'S.....THEY WON'T WORK ON THIS ROM--AND YOU DON'T NEED EM-
I highly recommend anyone who hasn't played with the overclocking hack recently brought to everyones attention, credit and thanks to Eugene, or anyone who has tried it and didn't like it, to make their first time experience or redeem their failed experience with KnK's version of the super-d 1.8 rom, seriously, it will shut down any doubts in mind that the hack makes a difference, trust me.
(Some of you may or may have not already tried this, if so feel free to comment your experience, as it will give others a better idea what to expect, similar settings don't count, you can sit here & argue this forum a thousand pages long about how you already tried this and that...how you turned swap on and off got the same results....benchmarked this, benchmarked that....well Daproy said this and Shadowich said that....[those are just random names of high posting users by the way, I'm not pointing anyone out, by all means those are two well respected, knowledgeable senior members for those who don't know] but I will not engage into a paragraph after paragraph argument with you, nothing stands as a valid opinion until you flashed this rom, not your own tweaked version, with your own tweaked settings, THIS ROM>FOLLOWING THESE STEPS are the only valid comments that will be made redeemable to any type of response from me, period. If another random member wants to post back and forth with ya than fine, but I will continue to ignore irrelevance)
And it would be greatly appreciated if off topic, sarcastic humor, LOL buddy chat, and pointless picture posting be taken over to a PM for private conversation...as it has nothing to do with this thread
BY THE WAY THIS IS NOT MY ROM, I AM NOT A DEV. I'M A HAPPY SUPER D USER WHO STUMBLED ACROSS A PIECE OF GREATNESS AND DECIDED TO SHARE. IF YOU HAVE PROBLEMS, ISSUES, CONCERNS, OR QUESTIONS...I SUGGEST YOU CONTACT THE PERSON RESPONSIBLE FOR THIS TWEAKED VERSION OF SUPER D, HERE IS HIS INFO-- [email protected], XDA MEMBER NAME-KNK, TWITTER-DIGITALKNK
THANK YOU
Backup what ya got, Do a clean full wipe, download this zip:
http://www.megaupload.com/?d=3J6RP7GN
extract it to ya pc, grab the setcpu.txt file and the setcpu apk- he forgot to put it back in the rom, so you will need this unless you have a copy of the apk on your sdcard already, place it on the root of ya sd,
transfer the KnK's custom Super D rom to your sdcard,
boot into recovery and flash,
after it fully loads, don't do anything, reboot again,
when it loads back up, go to your setcpu app and choose Custom settings
tweak your high/min the way ya want, I recommend 628/245
after setting it, reboot again,
when it loads back up, you will be completely amazed, I promise you.
Whats special about his version? Theres no swap/compcache, a few system apps are removed (so if you like the stock email, calculator, IM and all that, you'll have to port it back yourself)
Maps Nexus Multi-Touch enhancement already applied, cpu hack boot img already compiled and packaged
and probably more but IDK, maybe he tweaked the kernel or something, needless to say this is still Super D-1.8, and you all know how great that is anyway, credit due to the Dev-Ben Buchacher
but truth be told this is the fastest I've seen guys, really, It defeats the purpose of swap and compcache
just try it on ya spare time, and if ya follow the steps above I promise you wont be disappointed
I welcome all your opinions, negative, positive, flame me, blame me, hate me and be angry, I don't care....this is worth my time to post for others to try because my experience was that good, call it crazy, "placebo", imaginative, whatever....bet ya can't call me a lie flash and you'll see why.
Downloading this now can't wait to try it out
Thanks, I'll try this out too
The different fonts and colors hurt my eyes. I'll download it though...
And someone had to say something negative:
"The rom cooker app isn't even out yet and it's already happening."
That should rid the negative for a few posts
Wooo downloading now. Thank you for sharing.
i feel u on that some ppl just plain out rude lol!!! applying this now i will update as i go!!!! good look on this !!!
JAguirre1231 said:
The different fonts and colors hurt my eyes. I'll download it though...
And someone had to say something negative:
"The rom cooker app isn't even out yet and it's already happening."
That should rid the negative for a few posts
Click to expand...
Click to collapse
LOL, agreed, but I'm not and will not be one of the "Rom Cooking" posters, this is someone elses.
fail...lol
please read eugenes official statement on the overclock not actually working. Any speed increase you see is fictional.
http://forum.xda-developers.com/showpost.php?p=5584571&postcount=164
d33dvb said:
fail...lol
please read eugenes official statement on the overclock not actually working. Any speed increase you see is fictional.
http://forum.xda-developers.com/showpost.php?p=5584571&postcount=164
Click to expand...
Click to collapse
Please flash this rom, and follow these steps, then post your fiction theory along with its link again. that is my one and only reply to you. Thanks.
Whether or not the overclocking really works, this is pretty much the ROM combo I've been after for awhile
What are the required partitions and SPL?
I installed setCPU, but I'm not getting the option to increase the clockspeed beyond 528 ...
Where exactly do I copy the setcpu.txt file to get the additional clock rates?
Do I choose a different hardware platform (g1, magic, nexus, etc.) for the setCPU app?
chilln73 said:
I installed setCPU, but I'm not getting the option to increase the clockspeed beyond 528 ...
Where exactly do I copy the setcpu.txt file to get the additional clock rates?
Do I choose a different hardware platform (g1, magic, nexus, etc.) for the setCPU app?
Click to expand...
Click to collapse
put the file on the root of your sd---meaning just drop it on the card, not inside a folder
you will not choose a handset- such as g1, magic,nexus,etc...
you will choose the very last option which is Custom settings
please do not forget two reboots are required!! Follow all steps carefully.
I spent some time with the ROM and I wasn't noticing a huge difference in performance... Went back to Super D.
Johnny5401 said:
What are the required partitions and SPL?
Click to expand...
Click to collapse
Same as the original rom (Ben) stated...please see the main thread labeled (rom) SuperD1.8-"Fried Donut" for any change logs or special install requirements.
CaptainShanks said:
I spent some time with the ROM and I wasn't noticing a huge difference in performance... Went back to Super D.
Click to expand...
Click to collapse
please do tell in detail....did you reboot after first flash? and again after setting overclock? How long did you play? Were there any decreases in performance? Such as lags, freeze ups? what did you clock? high/min?
People, dont get carried away, you cant just flash, boot up, spin clock speed up to highest your heart feels, then turn off and nandroid back to your old set-up, you have to do the steps above exactly as stated, and if you did indeed do so...i want to know more about what your experience and clock tweaks were, because one minor adjustment can make a difference.
CaptainShanks said:
I spent some time with the ROM and I wasn't noticing a huge difference in performance... Went back to Super D.
Click to expand...
Click to collapse
Couldn't really tell either. I replaced Home++ with Advanced Launcher to make a better judgement, but as far as I can tell it's just the typical Super D speeds... which is of course, amazingly fast.
Tried at your rec setting of 628.
bigdbag said:
Couldn't really tell either. I replaced Home++ with Advanced Launcher to make a better judgement, but as far as I can tell it's just the typical Super D speeds... which is of course, amazingly fast.
Tried at your rec setting of 628.
Click to expand...
Click to collapse
cool,
alright thanks for the input!
Here's an idea, if you're up for it...wipe and go back to the stock super D 1.8 with no cpu hack, and see if the speed feels the same....it'll be fast, cus like you said super d is fast, but I can almost guarantee it wont be the same
Umm wow ... I didn't think Klyentel would have made a post about this hahaha. In any case thanks .
I don't run it at 780 in fact My max is 580mhz since overclocking it to anything above that is a battery eater and doesn't jump much in performance.
Be sure to use profiles on setcpu that is the most useful feature on there.
I have these settings.
Charging
- 780max
- 384min
Sleep/Standby
- 245max
- 128min
Power < 90%
- 580max
- 245min
Battery Temp > 37.9
- 245max
- 245min
I have the profile set @ 780 when charging because I have the failsafe enabled which drops the cpu down if the battery is to heat up. So that's the only time I have it enabled at 780mhz.
Well I hope you enjoy the rom I didn't do much but just tweak it a bit like Klyentel said Ben did most of the work with SuperD which is an awesome rom all I did was tweak it to my liking
For those not seeing a difference you won't really at standard tasks, I have setcpu to on demand on the normal Super D 1.8 and set at 384 or 528 max you see no real difference... that is until you start multi tasking. Having 10 browsers windows open, snes emulator, last fm and documents to go the speed increase is greatly noticed as its at its heaviest usage that the cpu finally decideds to crank up due to workload.
If your gonna test then do so properly rather than a quick look and deciding nothing has changed. Gonna flash this myself later and do some proper more constructive testing and report back.

[Q] Options to Undervolt CPU

I've been searching around for a way to undervolt my captivate to save on battery life. Ideally I'd like to just use a program but it seems SetCPU doesn't adjust the vsel and you either need to edit some kind of dbdata table or use the Unhelpful kernel. Can anyone tell me more about this? I'm not sure if I'd want to flash to unhelpful just so I can undervolt
Im pretty sure flashing unhelpfuls kernel is your best option for undervolting. I ran that kernel for quite a bit on a few different roms and it worked amazingly to preserve battery life. I went from about a 12 hour life to about 30 depending on usage. The biggest problem is finding a table that works for your phone. It seems as though everyone had to customize tables based on their phone. I was lucky enough to find one in the unhelpful thread that worked flawlessly
Is flashing a kernel different than flashing a rom? All I've done so far is root so I'm unsure of the differences.
Is there a sticky on how to flash the unhelpful kernel? I've browsed through the thread with little luck unless something is buried very deep within its 40+ pages
Its fairly simple...all the instructions are in the open f the thread. Download the file. Place it on the root of your SD card. Use rom manager to flash the kernel. Changing the table on the other hand is a little tricky. By default its undervolted at a very safe level... I fulound I could get much lower and still have my phone stable with no issues.
Sent from my SAMSUNG-SGH-I897 using XDA App

[Kernel]Experimental 2.6.35 with Automatic Voltage Scaling (AVS)

This kernel is based on Thalamus's Oxygen Kernel but with AVS and he's given me permission to post it here for testing.
I implemented AVS from scratch (based on the Code Aurora kernel) and it seems to work well for me.
AVS uses some hardware to emulate the longest gate delays through the CPU datapath. If the delay is longer than expected, the CPU voltage can be decreased, if shorter then it can be increased. This means that the CPU is always running near the minimum voltage it requires and because power consumption rises with the square of voltage this is a good thing.
Here are the results of some initial tests (full load, no idle):
Clock Speed, Without AVS, With AVS
1113600,234mA,223mA
998400,207mA,190mA
768000,158mA,138mA
499200,111mA,93mA
384000,90mA,79mA
245000,70mA,64mA
So there are power savings of about 8-15%
All patches are initially pushed here:
https://github.com/dzo/kernel/tree/2.6.35-bravo-exp
and should end up here:
https://github.com/thalamus/kernel/tree/2.6.35-bravo-exp
You can see the current status of AVS by doing:
Code:
cat /sys/module/avs/parameters/status
Doing:
Code:
echo 1 > /sys/module/avs/parameters/debug
will put lots of debugging info in the kernel log.
To disable AVS do:
Code:
echo 0 > /sys/module/avs/parameters/enabled
The minimum voltage is set to 900mV but you can change this using e.g.:
Code:
echo 850 > /sys/module/avs/parameters/vdd_min
Putting too low a value in here will crash your phone because AVS seems to have trouble with low frequencies.
I also added some extra frequency steps, 76.8MHz and 192MHz.
Don't expect huge power savings, the CPU is only one of the things using power on our devices.
I think AVS is a nice idea and I'd like to know how stable it is on other people's phones.
To install, flash the attached update zip from recovery.
Please don't use this kernel unless you are fairly well informed about what you are doing.
15/4/12: Updated kernel with higher vdd_min
Going to give this a test now, I'll report back later.
How did you produce those mA readings btw?
have you tried using other kernels like Eviolets one? does it really save much more battery than EVs?
is it 100% stable??
with the kernel using some hardware to calculate the voltages needed wouldnt it take some more power to get the calculations done?
cez10 said:
have you tried using other kernels like Eviolets one? does it really save much more battery than EVs?
Click to expand...
Click to collapse
Why don't you try it and find out instead of asking questions.
is it 100% stable??
Click to expand...
Click to collapse
I think the words '[Kernel]Experimental' in the thread title are a clue.
with the kernel using some hardware to calculate the voltages needed wouldnt it take some more power to get the calculations done?
Click to expand...
Click to collapse
The overhead of the calculations is negligible.
So this is only for gingerbread AOSP ROMs or works on Sense as well?
lvnatic said:
So this is only for gingerbread AOSP ROMs or works on Sense as well?
Click to expand...
Click to collapse
Oh my...people just want to be spoonfed on XDA these days.
This kernel is based on Thalamus's Oxygen Kernel
Click to expand...
Click to collapse
As Oxygen is an AOSP ROM it's fairly clear that it's not going to be a sense kernel isn't it?
Thanks for sharing this.
What are the available governors? I can't find this information on github.
Will switching between governors (depending on phone state) cause any issues with the voltage change, that aren't advised?
_thalamus said:
Oh my...people just want to be spoonfed on XDA these days.
As Oxygen is an AOSP ROM it's fairly clear that it's not going to be a sense kernel isn't it?
Click to expand...
Click to collapse
He never mentioned it is specifically for AOSP or Sense ROMs. I was wondering if this is just a separate script, not kernel dependent. But if I give it a 2nd read then yes, it seems indeed it is an entire kernel, my bad, no need for a spoon...or w/e it means.
lvnatic said:
He never mentioned it is specifically for AOSP or Sense ROMs. I was wondering if this is just a separate script, not kernel dependent. But if I give it a 2nd read then yes, it seems indeed it is an entire kernel, my bad, no need for a spoon...or w/e it means.
Click to expand...
Click to collapse
Don't listen to Thalamus. He has no time for people less "knowledgeable" than him. There was a time where I thought a kernel was a kernel.
I thought I had escaped his unhelpful comments when I left Oxygen thanks to his attitude (if you don't like his attitude, then tough is the general gist of it). If he was a shop owner he would go bankrupt, quickly, as he has no people skills whatsoever.
If he wasn't a dev, he would be labeled a troll, yet he is allowed to get away with being nasty to people. When will XDA introduce a -thanks button?
I think the saying goes, if you don't have anything nice to say, then don't say anything at all.
Thanks, this one looks like a good project
As to stability: i've been using this kernel for a couple hours without issues, with very small draining btw; anyway a few minutes ago the phone became unresponsive: i was just typing a message with whatsapp, clocked 192x806, and a freeze occurred. A soft reset did the trick.
Keep up the good job
Edit: i'm on beta 2 fyi...
chronicfathead said:
Don't listen to Thalamus. He has no time for people less "knowledgeable" than him. There was a time where I thought a kernel was a kernel.
I thought I had escaped his unhelpful comments when I left Oxygen thanks to his attitude (if you don't like his attitude, then tough is the general gist of it). If he was a shop owner he would go bankrupt, quickly, as he has no people skills whatsoever.
If he wasn't a dev, he would be labeled a troll, yet he is allowed to get away with being nasty to people. When will XDA introduce a -thanks button?
I think the saying goes, if you don't have anything nice to say, then don't say anything at all.
Click to expand...
Click to collapse
Hahahahahaha.
That cheered me up, I'm having a crap day.
Happy to be of assistance.
Edit: You prove how little you know about me by saying that I have no time for people less knowledgeable than me. That is totally untrue. I spend a lot of time helping people who are less knowledgeable than me. What I have no time for is laziness, people who won't help themselves or idiots. There is a big difference.
_thalamus said:
Hahahahahaha.
That cheered me up, I'm having a crap day.
Happy to be of assistance.
Edit: You prove how little you know about me by saying that I have no time for people less knowledgeable than me. That is totally untrue. I spend a lot of time helping people who are less knowledgeable than me. What I have no time for is laziness, people who won't help themselves or idiots. There is a big difference.
Click to expand...
Click to collapse
I only base my observation on posts of yours that I have read. Rather than shooting people down, advise them so they can improve their knowledge.
sent by touching my Desire
In Airplane mode i had 2mA battery usage all night without AVS and 5mA usage with AVS. This is via Battery monitor widget.
Xinot said:
In Airplane mode i had 2mA battery usage all night without AVS and 5mA usage with AVS. This is via Battery monitor widget.
Click to expand...
Click to collapse
AVS has nothing to do with power consumption while the device is asleep. When the phone sleeps, the CPU is power collapsed, i.e. is completely powered down. AVS only changes the voltage while the CPU is awake.
The Kernel work great on Miui 1.4.8 since 2 days! No reboot or freeze... and in idle with JiuceDefender, 652Mhz max ondemand over 3h the device lost only 2% accu
Thanks for your work
Sent from my HTC Desire using XDA App
I've just updated the kernel in the first post to increase the minimum voltage and remove some possibly unstable frequencies.
Should be more stable now.
dzo said:
AVS has nothing to do with power consumption while the device is asleep. When the phone sleeps, the CPU is power collapsed, i.e. is completely powered down. AVS only changes the voltage while the CPU is awake.
Click to expand...
Click to collapse
OukkiDoukki! So i have something else going on here...
Thanks running sweet keep up the great work using on GV 2.0
Sent from my HTC Desire using XDA Premium App
cez10 said:
have you tried using other kernels like Eviolets one? does it really save much more battery than EVs?
is it 100% stable??
Click to expand...
Click to collapse
Just a quick post to say that I've been testing this kernel for 2/3 days (actually the version that Thalamus has in his experimental github) and find the battery usage to be the same. But the AVS code seems much cleaner than the implementation I have.
As for stability, I haven't had a single crash yet. And overall speed seems better than on my kernel.
Quadrant also confirms this.
Regards,
EViollet said:
Just a quick post to say that I've been testing this kernel for 2/3 days (actually the version that Thalamus has in his experimental github) and find the battery usage to be the same. But the AVS code seems much cleaner than the implementation I have.
As for stability, I haven't had a single crash yet. And overall speed seems better than on my kernel.
Quadrant also confirms this.
Regards,
Click to expand...
Click to collapse
Do you think you will be compiling ManU 1.5 from this source then?

Overclocking - pros & cons?

Yes, I FINALLY did it!!! I overclocked my G2X. I would appreciate if anyone could share their experiences with o.c. pros and cons... Should I retreat or stay where I am? Please some feed back!
Over 1300 seems to cause trouble on mine.
i dont think oc'ing is really that necessary with a phone this fast but if u must i wouldn't go above 1.3 (just seems unstable above that). I think the "Pros" come from being able to underclock. Setting up profiles for uc'ing when screen is off or as battery level drops etc really prolongs the life of the battery (at least in my case)
On my OG droid that came limited at 550 mhz, ya, oc'ing was def necessary but I cant really think of any "Pros" for oc'ing this phone.
each phone is different though so play around and you'll find a combination that works great for your phone, good luck
Well... you can get some serious bench scores... This thing rocks the Mandelbrot multithread test in smartbench 2011 at 1.5 ghz. Other than that it helps with games.
Sent from my LG-P999 using XDA App
wu_wei_lion said:
Well... you can get some serious bench scores... This thing rocks the Mandelbrot multithread test in smartbench 2011 at 1.5 ghz. Other than that it helps with games.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
What about the CPU not having enough cooling and frying the CPU over time. I presume its just like Desktop overclocking but without all the extra cooling you can add to make it safe for the hardware.
tombaker1 said:
What about the CPU not having enough cooling and frying the CPU over time. I presume its just like Desktop overclocking but without all the extra cooling you can add to make it safe for the hardware.
Click to expand...
Click to collapse
But what i really want to know is if oc could damage the phone. After all if there is that danger it's noy worth it...
In all honesty I used to be really into benchmark scores and OCing the heck out of my phone and under volting it in the process but that led to many battery pulls ect. What I've noticed is just keep it at stock and mild uving seems to be the best for me its stable decently fast just 2 cents though
Overclocking a cpu is the same as on a pc, only a bit more dangerous on a phone. (This phone already has overheating problems running at stock speeds ) On a computer, people pay a premium for parts that are easily overclocked, and have either very good fans/heatsinks or a liquid cooling rig.
Overclocking is dangerous, especially because not all chips are going to be made equal, even if they come off the same production line. These chips are designed to run at a certain voltage, and certain clock speed. As far as real world use, (NOT benchmarks. Sure, they look pretty and all, but benchmarks are never very accurate.)
Sure, you might get 2-3 more fps on your games, but is that worth the risk of shortening the life of your chip/phone?
(And just so you know, I've been building/overclocking pc's for years, but I also understand what you need to do to keep it stable, and it's *all about cooling*.)
If you're not convinced, try this. Don't overclock your phone, and use it for a few days. Tell me honestly that you really notice a real-usable difference with the chip overclocked or not. (Games set aside, but like I said, getting a couple extra fps on a game to me isn't worth the risk without a proper cooling setup)
For those of you that really don't understand what you're doing to your chips when you overclock, I'd suggest doing some reading about it. A good place to start would be here: http://en.wikipedia.org/wiki/Overclocking
So you think using fauxs kernel is not safe or reduces the life of the chip? I just flashed it and didnt oc or uv further then fauxs default settings...
Sent from my LG-P999 using XDA App
I'm not saying it's for sure, I'm saying there's a chance.
Plus keep in mind that these kernels have other really nice additions besides overclocking and undervolting. I'm using faux's stock voltage kernel ext4, and leaving it at stock settings, and it really works great.
I just posted this up because I see a lot of people more interested in quadrant scores (which to me are pretty useless) than stability of their phones. If you do overclock, and it works for you, more power to you. I just want to inform people. I'd HIGHLY suggest if you aren't sure, read that wiki article, it's a great place to start. (not all information is there, but it gives a very good general idea on how and what overclocking is.)
Thanks! i always like reading knowledgeable and informative posts!
Sent from my LG-P999 using XDA App
mstrk242 said:
I'm not saying it's for sure, I'm saying there's a chance.
Plus keep in mind that these kernels have other really nice additions besides overclocking and undervolting. I'm using faux's stock voltage kernel ext4, and leaving it at stock settings, and it really works great.
I just posted this up because I see a lot of people more interested in quadrant scores (which to me are pretty useless) than stability of their phones. If you do overclock, and it works for you, more power to you. I just want to inform people. I'd HIGHLY suggest if you aren't sure, read that wiki article, it's a great place to start. (not all information is there, but it gives a very good general idea on how and what overclocking is.)
Click to expand...
Click to collapse
OK, you definitely convinced me.... I have also faux (let me tell you exactly - Kernel Version 2.6.32.9 FR Faux 123-v0.03) on EagleBlood 1.05. Could you please tell me what I need to do set up in order to be safe? Thanks!
I'd just go to faux's thread in the development section (his froyo thread, not the cm7 one, since you're using eagleblood), and download his stock voltage kernel. (It's in the first post.) He's on .04 now, by the way.
Then reboot into recovery, and flash the file you downloaded. It'll overwrite your current kernel and modules with the new one, then reboot.
mstrk242 said:
I'd just go to faux's thread in the development section (his froyo thread, not the cm7 one, since you're using eagleblood), and download his stock voltage kernel. (It's in the first post.) He's on .04 now, by the way.
Then reboot into recovery, and flash the file you downloaded. It'll overwrite your current kernel and modules with the new one, then reboot.
Click to expand...
Click to collapse
I could not find this thread under G2X Android Development Section... I found threads Kernel Trinity, Kernel CM7, Kernel LGE Stock Froyo, Kernel Morphine... Which one is it...? Please do have some patience, at least I learn fast!
krekabl said:
I could not find this thread under G2X Android Development Section... I found threads Kernel Trinity, Kernel CM7, Kernel LGE Stock Froyo, Kernel Morphine... Which one is it...? Please do have some patience, at least I learn fast!
Click to expand...
Click to collapse
You passed right by it. LGE stock froyo. (That doesn't mean it's a stock froyo rom, it means it's *based* on one )
http://forum.xda-developers.com/showthread.php?t=1102720
Choose the stock voltage one. (ext3 or 4, depending on your preference.)
mstrk242 said:
You passed right by it. LGE stock froyo. (That doesn't mean it's a stock froyo rom, it means it's *based* on one )
http://forum.xda-developers.com/showthread.php?t=1102720
Choose the stock voltage one. (ext3 or 4, depending on your preference.)
Click to expand...
Click to collapse
Thanks you've been very helpful. That's why I made this post I hope this can help other people as well as it's helped me! )
krekabl said:
I could not find this thread under G2X Android Development Section... I found threads Kernel Trinity, Kernel CM7, Kernel LGE Stock Froyo, Kernel Morphine... Which one is it...? Please do have some patience, at least I learn fast!
Click to expand...
Click to collapse
And a lot of times the kernel will be credited to the developer. So if you see "faux's kernel" people are referring to kernels by faux123. Trinity kernels were developed by morfic. If you are having a hard time finding a specific one, look at the top left to see who started the thread and sometimes that will help find it. Does that make sense? I had to pull an overnight at work so I am a little loopy....
Sent from my butt using XDA Premium App

[Q] Freezing after flashing kernel

hi...I have bigxie apex ics rom on my nexus s and when i flash matr1x kernel 19.5cfs it starts to freeze. Works just fine with the stock kernel. Also when i was using the cm9 it worked fine with the stock but when i flashed matr1x kernel it started to freeze and reboot. Please help!
His kernel is undervolted by default. The phone might not be able to handle the voltages. I have no idea how to fix it though since you can't even get past the full boot. Better off going with something else.
had the same issue, just use another kernel or raise voltages. i've got no idea why everyone recommends matr1x, UV by default just doesn't make sense since every cpu behaves differently. it's like selling "one size fits all" t-shirts. i recommend simple kernel or trinity, they are the most stable ones on my phone apart from stock obviously.
Aktifit said:
had the same issue, just use another kernel or raise voltages. i've got no idea why everyone recommends matr1x, UV by default just doesn't make sense since every cpu behaves differently. it's like selling "one size fits all" t-shirts. i recommend simple kernel or trinity, they are the most stable ones on my phone apart from stock obviously.
Click to expand...
Click to collapse
The most known product doesn't mean it's the more fitting for everyone. It just means it's popular. *shrugs*
I'd be willing to bet that a lot of the people using it don't even know it's undervolted, sadly.
thankyou for the replies...i will try the trinity kernel
You all argue about matrix yeah its undervolted so?? You need to raise your voltage to to make it stable because not all phones can handle undervolted values. It's been address millions times and you all still argue.? Goddamit!! (Bunch of noobs) try to solve the problem first before suggesting another kernel. It so irritating you all. I'm sure matrix dev despise you all because of your.ignorance.
Sent from my Nexus S®
chronophase1 said:
I'd be willing to bet that a lot of the people using it don't even know it's undervolted, sadly.
Click to expand...
Click to collapse
I am guessing most people do know that it is undervolted. If they don't, I wouldn't understand why. He plainly states that if you have freezing issues to raise your voltages right in the FAQ. I have been running the Matr1x since gb and have never had issues with the undervoting. Perhaps your phone can't take it.
If people aren't smart enough to read what the developer has to say, why would he set it to the higher voltages and expect users to move the voltages down themselves. You imply the common user is not smart enough to do it themselves. So what does that leave the developer to do? He can make it like he thinks it should be or make it for the idiots that can't or won't read the op comments.
People need to understand kernels run differently on every phone. So instead of whining they should just move on.
________________
Just Flash It !!!
did u wipe dalvik cache...
Skunk Ape1 said:
I am guessing most people do know that it is undervolted. If they don't, I wouldn't understand why. He plainly states that if you have freezing issues to raise your voltages right in the FAQ. I have been running the Matr1x since gb and have never had issues with the undervoting. Perhaps your phone can't take it.
If people aren't smart enough to read what the developer has to say, why would he set it to the higher voltages and expect users to move the voltages down themselves. You imply the common user is not smart enough to do it themselves. So what does that leave the developer to do? He can make it like he thinks it should be or make it for the idiots that can't or won't read the op comments.
People need to understand kernels run differently on every phone. So instead of whining they should just move on.
________________
Just Flash It !!!
Click to expand...
Click to collapse
Or that the common user is prone to not reading and just going ahead and flashing.
Seriously, coffees have "CAUTION: HOT!" written on them. I pretty much lost faith in "common users" a long time ago.
Skunk Ape1 said:
I am guessing most people do know that it is undervolted. If they don't, I wouldn't understand why. He plainly states that if you have freezing issues to raise your voltages right in the FAQ!
Click to expand...
Click to collapse
Exactly! Read everything first. Educate your self before attempting anything. Just because you can flash doesn't mean you should without understanding anything about what it does or will do to your phone. FAQ is there for you to become familiar with what issues have happened and might happen to you. Yes the Matrix thread is long but I read a lot of it to understand what it was, issues and what others are saying. Just like any ROM, Kernel or mod you plan on trying, read the thread first. :thumbup:
Hope I don't sound like I'm complaining but most threads are started or answered wrong because of this. Good luck :thumbup:
Sent from my Nexus S using xda premium
This is what I was getting at and it somehow got interpreted wrong. It wasn't a dig at mathkid and any of the regular users on here. There are a lot of new users on here and many flash stuff excitedly and don't fully read stuff. I've been there before. Its still a common mistake.
Sent by pocket technology.

Categories

Resources