Related
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?
When I undervolt my phone my reception is horrible like 1-2 bars when its normally full. Am i doing anything wrong? I just can't get the undervolting and the reception to work well together
King Askaba said:
When I undervolt my phone my reception is horrible like 1-2 bars when its normally full. Am i doing anything wrong? I just can't get the undervolting and the reception to work well together
Click to expand...
Click to collapse
If undervolting is impacting the performance of your phone (in your case, the signal strength) then it can be argued you're undervolting too much, even though your phone is stable otherwise. About the only thing you can do is try undervolting a little less. Every phone is different regarding this kind of stuff, so it's a trial and error situation.
Or I suppose you can try different radio/RIL combinations. But I haven't read of anyone testing radio/RIL performance at different voltage levels so there's no evidence to suggest this will fix your problem - just throwing ideas out there.
I tried the -25 undervolt and my signal is up to an acceptable area would be cool if i could get the -50 but oh well still going to get good battery
King Askaba said:
When I undervolt my phone my reception is horrible like 1-2 bars when its normally full. Am i doing anything wrong? I just can't get the undervolting and the reception to work well together
Click to expand...
Click to collapse
Well, I'm no electrical engineer, but common sense kind of makes me agree with Henry...
Radio needs juice/cpu time to operate.
Undervolting reduces the amount of voltage supplied to cpu, perhaps other components.
Reduced power to cpu/radio/etc. = reduced performance.
Especially if it worked fine before undervolting. Really doesn't seem that mysterious to me.
Keep in mind you're doing something to the phone it wasn't originally designed to do. Just because it can tolerate it, doesn't mean it's going to tolerate it AND behave as if everything is normal.
Is it possible just to install the undervolt zip or do have to have the kernel that goes along with it?
Is it possible to change the amount of undervolt simply and easily?
Sent from my Inspire 4G using XDA App
King Askaba said:
Is it possible just to install the undervolt zip or do have to have the kernel that goes along with it?
Click to expand...
Click to collapse
The kernel must support undervolting.
henrybravo said:
The kernel must support undervolting.
Click to expand...
Click to collapse
This I am aware of. I mean is there a way to change the amount of undervolt in MDJ Kernels to try to improve signal strength? or are there any comparable non undervolting kernels with all the features still there?
willwalk93 said:
Is it possible to change the amount of undervolt simply and easily?
Click to expand...
Click to collapse
Usually, yes. For example, some of the common kernels being used to undervolt the Inspire are LorDMoD kernels. He's got 4 undervolt scripts that will undervolt your phone to various levels, depending on how low you can go (every phone is different). Some users have created their own custom undervolting scripts as well.
-25mv script: safe for almost all phones
-50mv script: safe for many phones but not all
UUV (Ultimate Undervolt script): you're starting to get into some serious undervolting here. Doesn't work with a lot of phone
PUV ("Pinky" Undervolt script): crazy undervolting (LorD ClockaN calls it "heavenly undervolt"). The PUV script is stable on a fairly low number of phones.
These scripts are contained in separate downloadable .zip files that you simply flash in recovery mode. The .zip contains a script file called "99voltages" that is copied into your /system/etc/init.d folder. Any scripts placed into this folder are automatically executed upon bootup. Once this script runs, it sets the voltages for your CPU at various speed levels. The voltage of your CPU can be verified by viewing the vdd_levels file located in /sys/devices/system/cpu/cpu0/cpufreq. The voltage of the CPU changes as the frequency goes up and down. Typically the higher the frequency the more voltage is needed.
Sorry that was probably more info than you asked for.
henrybravo said:
Yes. Some of the common kernels being used to undervolt the Inspire are LorDMoD kernels. He's got 4 undervolt scripts that will undervolt your phone to various levels, depending on how low you can go (every phone is different). Some users have created their own custom undervolting scripts as well.
-25mv script: safe for almost all phones
-50mv script: safe for many phones but not all
UUV (Ultimate Undervolt script): you're starting to get into some serious undervolting here. Doesn't work with a lot of phone
PUV ("Pinky" Undervolt script): crazy undervolting (LorD ClockaN calls it "heavenly undervolt"). The PUV script is stable on a fairly low number of phones.
These scripts are contained in separate downloadable .zip files that you simply flash in recovery mode. The .zip contains a script file called "99voltages" that is copied into your /system/etc/init.d folder. Any scripts placed into this folder are automatically executed upon bootup. Once this script runs, it sets the voltages for your CPU at various speed levels.
Click to expand...
Click to collapse
So can one simply edit the scipts in the kernel packages to try to improve signal strength?
Also, is there any way to determine the current undervolt on my phone? I am on mdj v23 atm.
willwalk93 said:
Also, is there any way to determine the current undervolt on my phone? I am on mdj v23 atm.
Click to expand...
Click to collapse
I thought someone might ask this, so I edited my post a little bit ago to answer this. Check the bottom of my last post and I mentioned what file to check to see your voltages.
One thing I should mention is you probably shouldn't give too much credence to undervolting. It is not the big battery saver you might think it is. It does help somewhat, but even using the extreme PUV script, the net effect to the battery is about 10% improvement in standby mode, and the more conservative script settings are considerably less. If you want more detail, there is a discussion in the last few pages or so of the LorDModUE thread listed in my sig where we discuss the merits of undervolting. Of course on a phone like the Inspire with a measly 1230 mAH battery, every percent counts and is welcome, which is why I'm a fan of undervolting. As was pointed out in that thread, when your phone is being used with the screen on, the largest battery draining component is the display. When your phone is in standby mode, the largest draining component is the radio. A CPU voltage drop of 25mv is only 2.5% (which equates to ~5% power consumption drop by the CPU; see LorDModUE thread for the formula). Given the fact that the CPU is far from the biggest draining component in the phone, the total net effect with a 25mv drop is much less than a 5% improvement.
To answer your other question, yes you can edit the scripts yourself if you're willing to invest the time and effort. I don't know if it's worth the effort in most situations. For example, King Askaba's signal is fine at -25mv but starts to degrade at -50mv. Finding the sweet spot between such a close set of voltages (-25mv versus -50mv) isn't going to make a difference in your battery life.
Thanks for all the help but if i can't have good signal then I wont undervolt. Especially when it not that much of a battery saver.
Sent from my MIUI HTC Inspire 4G using XDA App.
King Askaba said:
Thanks for all the help but if i can't have good signal then I wont undervolt. Especially when it not that much of a battery saver.
Sent from my MIUI HTC Inspire 4G using XDA App.
Click to expand...
Click to collapse
I'm with you 100% Not worth the trade off.
I am using inspired ace with the mdj v23 kernel. There was no system/etc/init.d folder wasn't there. So how do I restore my voltage to its full power with this kernel? Also the method to check did not work as that file was not found in root explorer.
Sent from my Inspire 4G using XDA App
willwalk93 said:
I am using inspired ace with the mdj v23 kernel. There was no system/etc/init.d folder wasn't there. So how do I restore my voltage to its full power with this kernel? Also the method to check did not work as that file was not found in root explorer.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
My bad, I was referring to LorDMoD kernels which only work on AOSP ROMs, so those folders/files won't apply to your ROM. I'm not familiar your ROM/kernel (I think I got confused on who I was replying to since you and King Askaba were both chiming in, my mistake).
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
Hello,
FIRST OFF!
This thread is NOT for discussing whether or not benchmarking is useful. If you feel the need to flame me or anyone here for CARING about benchmarks, then go find another thread to piss in! I made this thread to clean up Faux's thread as it was taking over.
Ever since moving to any of the newer CM7 updates, I have noticed extremely low benchmark scores on CF Bench. When on CM7-1 with one of faux's kernels, everything is fine. (Cf Bench = 7000)
When I say low, Im talking 4000 on CF Bench despite OCing to 1.56Ghz. That is far below what the Sensation STOCK is measured at...
Notes:
1-Scores can be all over the place. At one point, I got a 6400. This would immediately become a 5000, and then back to 4000 range.
2-I have tried using three different methods of controlling the clock. (System tuner by 3c and fauxclock, both recommended by faux for his kernels, and then the CM7 performance settings). Fauxclock had the best outcome, but EXTREMELY unstable!
3-I have done NUMEROUS restarts along with cache clearing and dalvik clearing. I even pulled the A-Bomb out and used the superwipe script to start fresh. After the a-bomb, I DL only what I needed to test with...
4-My phone feels laggy, which goes along with the crappy scores.
At this point, I am restoring to my trusty Alpha 1 + faux kernel. While that works, I feel I will wind up getting left behind.
What could cause this? What are some things I may have overlooked? Others DONT have this problem, at all.
Matt
well i will say benchmarking isnt a totally conclusive. although there isnt any other method of tangible scoreing as of yet. However i will say that if your phone is laggy then your benchmarks are a good way to test why.
scoreing varies when you have active apps in the background unknowingly.
also if you flashed a new rom and kept your old kernel that will dramatically reduce your scores. check out some other kernels for your new rom and see if that makes a difference.
try flashing back to stock and deleting the kernel, then flash the CM7 rom without the kernel in your system and run a test.
theres a lot of things that will change your scoreing.
let me know what you get out of this.
rddocke said:
well i will say benchmarking isnt a totally conclusive. although there isnt any other method of tangible scoreing as of yet. However i will say that if your phone is laggy then your benchmarks are a good way to test why.
scoreing varies when you have active apps in the background unknowingly.
also if you flashed a new rom and kept your old kernel that will dramatically reduce your scores. check out some other kernels for your new rom and see if that makes a difference.
try flashing back to stock and deleting the kernel, then flash the CM7 rom without the kernel in your system and run a test.
theres a lot of things that will change your scoreing.
let me know what you get out of this.
Click to expand...
Click to collapse
I came from ARHD with fauxs kernel. I did a superwipe and then flashed cm7-1 and then flashed fauxs kernel. Everything was great until I tried any of the new CM7's...Just tried cm7-6 and got a WHOPPING 3000!!!!!!!!! YAY!!!!!!!!
I knew it would be low, just playing with the phone. I find it so weird that going back to cm7-1 fixes everything.
Either their new updates kill my performance for whatever reason, or going from one cm7 build to another is a no go. (I did a superwipe just to be sure when going from alpha1 to alpha 5).
Damnit.
If it werent for seeing others with good scores, I would blame cm7 or faux's kernel. Its got to be some little quirk with my phone. (And a few others).
Matt
I recently rooted my P999/G2x and installed CM7.1.0.1, and am extremely happy with it. Am looking to tinker just a *little* bit more, but have some questions... I have LOTS of answers on the forums, but am somewhat skeptical about the currency of some of the information out there (let's face it, stuff changes fast!). So, down to it:
Kernels:
- Did CM7 overwrite the stock kernel?
- I understand the benefits to changing the kernel; what about drawbacks?
- Does CWM back up your kernel with Backup and Restore? If not, how do you do this?
- Recommendations on a good, reliable kernel to use w/ CM7? I am looking at faux123's CM and morific's Trinity. Thoughts?
OC/UV:
- Can you OC on stock/CM7 kernel?
- What is the best app to manage OC/UV? I have my eye on setCPU, cpu Master, and Android Overclock (JRummy16)
- Any recommended settings for the G2x? Any settings to avoid? My plan is to incrementally adjust, but don't really have an idea as to where to start.
Thx in advance!
- Did CM7 overwrite the stock kernel?
Yes
- I understand the benefits to changing the kernel; what about drawbacks?
Since not all the chips are made in the same way, you could soft brick your phone if you try to flash an undervolted kernel. This is the way mine is, and it's somewhat irritating but not all that bad using the stock voltage and overclocking to around 1.4ghz rather than 1.5ghz+. Also, battery life should be expected to be less with an overclocked CPU. It's up to you to decide how you want to run your device.
- Does CWM back up your kernel with Backup and Restore? If not, how do you do this?
Yes, backup creates an image of the entire thing. Before you start making changes, always make a backup so you can revert to previous settings should you soft brick your device. Make a backup, clear cache/dalvik, flash the kernel and reboot the phone. First boot times will always be a little longer when flashing a kernel, so be patient and don't pull your battery right away. For me personally, if it hasn't done anything noticeable after about ten minutes, I pull my battery. Reboot into recovery and restore from the backup you made. If you started off trying an undervolted kernel, time to try the standard voltage now!
- Can you OC on stock/CM7 kernel?
No, and you'll be able to tell once you flash CM7 and use SetCPU (or whatever you use) and see the max is still at 1ghz.
- What is the best app to manage OC/UV? I have my eye on setCPU, cpu Master, and Android Overclock (JRummy16)
Personal preference. I think probably SetCPU is used by most people including myself.
- Any recommended settings for the G2x? Any settings to avoid? My plan is to incrementally adjust, but don't really have an idea as to where to start.
If you want to be safe just start out at 1ghz. If you have no random reboots with your kernel then move it up to 1.1 or 1.2 and see if it's stable there. Personally, I just went ahead and overclocked to 1.4ghz. For the most part people don't really have problems with this I guess. The problems usually lie in whether or not you are undervolted and by how much. If you find your device can run an undervolted kernel, I would just leave the undervolt settings the way they are. As I said, I can't run OC/UV and have to use SV, so I never touch any of the voltage settings.
Hope this helps!
Using eagle blood (cm7 based) with faux kernel.
I heard trinity kernels may have random reboot but don't quote me on that.
Try faux kernel with oc/uv. Its very good, latest is 0.48. But if you go with the ds version (debaouch?) The battery percentages are all over the place... Lol one minute its 50% the next it may be 34%...
Use set cpu. I've uv additional 25mv across the board with no I'll effects. Screen off profile at 503 mhz max and some other profiles will have you getting 24hours easily with normal usage.
Make sure test it out before you "set on boot"...
Sent from my LG-P999 using XDA App
I tired using DS OC/UV Kernel Version 0.4.8 kernel on my g2x running the latest stable release of CM7 1.0.1. Followed all the necessary step of wiping cache, and darvik but when I reboot, I get the blue lg sign after which the screen just black out and its stuck like that till i pull the battery out. Any one know what I may be going wrong here? ? ?
Trinity ELPmax with Phoenixblood is the best combo. Trinity batterylife is amazing. When i leave the house my phones battery is 100%. 11 hours later (I when i make it home) my battery is always under 60% but never less then 40%. I play music as soon I leave the house, and till I get in the house. I also turn of data when not using and have setscpu set to 900mhz max and screen off profile set to 432 max 216 min.
Just my personal results
e4e5nf3nc6 said:
- Did CM7 overwrite the stock kernel?
Yes
- I understand the benefits to changing the kernel; what about drawbacks?
Since not all the chips are made in the same way, you could soft brick your phone if you try to flash an undervolted kernel. This is the way mine is, and it's somewhat irritating but not all that bad using the stock voltage and overclocking to around 1.4ghz rather than 1.5ghz+. Also, battery life should be expected to be less with an overclocked CPU. It's up to you to decide how you want to run your device.
- Does CWM back up your kernel with Backup and Restore? If not, how do you do this?
Yes, backup creates an image of the entire thing. Before you start making changes, always make a backup so you can revert to previous settings should you soft brick your device. Make a backup, clear cache/dalvik, flash the kernel and reboot the phone. First boot times will always be a little longer when flashing a kernel, so be patient and don't pull your battery right away. For me personally, if it hasn't done anything noticeable after about ten minutes, I pull my battery. Reboot into recovery and restore from the backup you made. If you started off trying an undervolted kernel, time to try the standard voltage now!
- Can you OC on stock/CM7 kernel?
No, and you'll be able to tell once you flash CM7 and use SetCPU (or whatever you use) and see the max is still at 1ghz.
- What is the best app to manage OC/UV? I have my eye on setCPU, cpu Master, and Android Overclock (JRummy16)
Personal preference. I think probably SetCPU is used by most people including myself.
- Any recommended settings for the G2x? Any settings to avoid? My plan is to incrementally adjust, but don't really have an idea as to where to start.
If you want to be safe just start out at 1ghz. If you have no random reboots with your kernel then move it up to 1.1 or 1.2 and see if it's stable there. Personally, I just went ahead and overclocked to 1.4ghz. For the most part people don't really have problems with this I guess. The problems usually lie in whether or not you are undervolted and by how much. If you find your device can run an undervolted kernel, I would just leave the undervolt settings the way they are. As I said, I can't run OC/UV and have to use SV, so I never touch any of the voltage settings.
Hope this helps!
Click to expand...
Click to collapse
+1 to everything you said
just to add if you want to over clock then go with faux or trinity. the cm7 kernel is faster then both @1000mhz, if speed is what your looking for without the dangers of oc. The stock cm7 kernel also lacks the ability to under volt soo battery life might not be as good though
Rbern144 said:
I tired using DS OC/UV Kernel Version 0.4.8 kernel on my g2x running the latest stable release of CM7 1.0.1. Followed all the necessary step of wiping cache, and darvik but when I reboot, I get the blue lg sign after which the screen just black out and its stuck like that till i pull the battery out. Any one know what I may be going wrong here? ? ?
Click to expand...
Click to collapse
Format data/ factory reset.
Wipe all cache.
Format system. (don't forget)
Flash cm.
Flash kernel.
It may take a while for the system to boot, 5 min. Let it load, and reboot, enjoy.
Sent from my LG-P999 using XDA App