Database Info

[KERNEL] [GPL] MixUp - Overclock/Undervolt (11/10/2010 - Taco Madness!)

This is based off the latest Samsung kernel source (DI18) with some of my tweaks. Overclock to 1.2Ghz @ 1.25V is maximum. That is 50mV LESS than the voltage given in a stock kernel for 1Ghz!
This kernel is UNBELIEVABLY fast! Average Linpack scores of 9.5+ mflops & Quadrant scores of ~950-1050.
Battery life is great on this beast. Yesterday I ran it all day starting around 8AM, and I didn't hit low battery until 10PM. Thats the furthest I've ever gone, and almost double stock.
Just flash the zip in recovery. I have had no issues with this kernel, nor have any of my testers. This kernel is already included in AOSP Magic & Tha Boss ROM v.2 or above (it was actually made special for Tha Boss at the request of it's maker @KyleCole90). If you're running one of those ROMs you don't need to flash this, unless I release a new version here.
Use SetCPU to set the clock. You'll have to re-do the autodetect (press Menu, Choose Device, Autodetect) for it to decide the new speeds, and you may have to do it a few times. Also, if you flash a different kernel, or update then you'll have to re-detect as well.
Props to @Decad3nce for the BFQ patch from his Hero kernel, @Supercurio for his Voodoo Color mod for the i9000 I just ported it to Epic, Skeeterslint for helping me solve a problem with my ramdisk, @KingKlick92 for a baseline of safe values for voltages from his Vibrant kernel, @Herver for the conservative tweaks, and to Unhelpful on the Captivate forum for his helpful (*rimshot*) source for his Captivate overclock kernel.
If you have any questions or problems (shouldn't be any ) then Twitter me or email me. Also, I don't ask for donations, but if you're feeling generous and you like my work please check out my apps on the Market or send me a donation via the Paypal Donate link in my signature.
-------------------------------------------------------------------------------
Root Issues On Some ROMs:
There are some root issues on some ROMs due to the fact that they still use the old JoeyKrim root. It was never intended to be a permanent root method. Once we got kernel root it became moot. I recommend you ask your ROM dev to fix this, instead of complaining to me
Here's how to fix it if your ROM dev doesn't (just run this from a shell/command prompt, you must have ADB set up):
Code:
adb shell
remountrw
rm /system/bin/playlogo
rm /system/bin/jk-su
mv /system/bin/playlogo-orig /system/bin/playlogo
-------------------------------------------------------------------------------
Changelog:
MixUp-20101110-1036 -- Released 11/10/2010 10:37PM CST:
Added Smartass governor. Still beta. Not default, but available. Similar to interactive, but more responsive & better battery supposedly. Thanks to a dev in the Hero forums whose name I can't remember.
CIFS support
VooDoo Sound support. Still beta.
1.3Ghz & 1.6Ghz OC!
Light & CPU tweaks from Devin
Several more small tweaks I can't remember
This version is beta! I have NOT tested this one at all! I'm running FroYo atm, and I can't test this kernel since it isn't .32. Let me know of any (probably a few) bugs.
MixUp-20101024-847 -- Released 10/24/2010 8:47PM CST:
Switched back to conservative scheduler by default. Interactive is still there, but not default. It'll get set to default when someone fixes interactive.
Patched up to 2.6.29.6 (thanks @Nullghost)
Various scheduler tweaks, backported from newer versions
New BusyBox version
Back camera tweaks, sharpness & saturation upped a notch. I think its better, but if you disagree then take them down a notch in camera settings.
Front cam tweaks. Samsung -- People != blobbish vampires. Sharpness & color upped. No more pale blobs of Play-Doh.
RNDIS! Finally! DevinXTreme got this one goin.
Speaking of Devin, this is now a collab between him & I, with some (credited) kanging from @Nullghost
Optical sensor tweaks. I know, I know, they keep coming. It's good, I promise. I think I FINALLY fixed it.
IMPORTANT! Calibrate your battery after flashing this kernel, else it will decrease! To calibrate, charge your phone all the way (or insert a full battery), wipe battery stats in Clockwork, let it drain to ZERO, plug it in and charge to FULL! Do NOT put in a full battery after the discharge. Your battery should really improve after this.
MixUp-20101017-855 -- Released 10/17/2010 10:05PM CST:
New CPU tables again. Alleviate radio sleep issues. Anything left is just DI18's fault
Actually capped at 1Ghz at boot now, just change with the OC program of your choice
No more no-voodoo version. Voodoo is brightness issue free now, and its too much hassle to maintain two kernels. It may return eventually if I get around to integrating it to my config
Interactive CPU governor added & set as default. Ondemand still available as are the rest.
Fixed lots of config errors, depriving you of EXT4 & BFQ
More optimization for Cortex-A8
MixUp-20101005-809 -- Released 10/5/2010 8:09PM CST:
New CPU Tables (MOAR BATTERYZ!!11!)
More conservative tweaks from Herver (BATTERYZ!!!)
Updated to DI18 sources
New ramdisk
Limited to 1Ghz until changed in setcpu now, better battery by default & more stable for some users. Just up it in SetCPU if you want OCing
Tweaked minimum brightness levels
Screen doesn't fall to minimum brightness automatically until 1% battery now. Used to be 5%. You're welcome
I left up the old DG27 kernel for people who haven't yet upgraded to DI18, just in case the DI18 one causes issues for them
MixUp-20100926-323 -- Released 9/26/2010 3:55PM CST:
Switched to BFQ scheduler. See here for details.
Tweaks to the default Conservative governor. Scales up sooner to avoid hangups and scales down sooner to save battery
Added the Voodoo Color option (thanks @Supercurio for creating it, I just ported it to Epic). There are some issues with it as described at the link. If you don't like it, use the one without it instead of complaining, kthx
Fixed root issues finally, if you experience them you still have the JoeyKrim exploit installed. Bad user.
Undervolted 50 more mV across the board, battery life on this beast is amazing
Added Superuser Permissions app (thanks for the help, Skeeterslint)
adbd now runs as root by default. That means "adb shell" drops you straight to # instead of $
EXT3/EXT4 FS support included in kernel. Do with it what you will.
Changed to a different floating point emulation method that *may* yield better performance
NEON support in the kernel
MixUp-20100921-655 -- Released 9/21/2010 6:55PM CST:
Added Clockwork & ROM Manager support.
Judging from the reports I've heard and things I've seen, I'ma call this one Stoopid Fast. Just cuz it sounds cool
MixUp-20100920-630 -- Released 9/20/2010 6:30PM CST:
adbd now runs as root. This allows adb push to /system. It also enables adb remount to remount /system to RW or RO, but there is something missing from the ROMs that don't allow adb remount yet. I'm working on it.
Small tweaks to voltage table (I think) so possible better battery life on this one, but don't hold me to that. I'll be fine tuning them later on some more.
-------------------------------------------------------------------------------
Source:
My source is now on GitHub.
Stock DI18 Samsung kernel branch here. This is for beginning kernel devs. It's totally stock. Feel free to fork this or download the tree to start your own kernel base.
MixUp VooDoo is here. This has all my changes applied and I will push all my changes to it.
I did not have time to upload my source for the non VooDoo kernel today, I have the local repo done, but I only have access to a high speed connection when I go into town, and I didn't have time to upload this one while I had access. Really though, if you want the source for a non-Voodoo kernel its identical to this, just change the "drivers/video/samsung/s3cfb_tl2796.c" and "drivers/video/samsung/s3cfb_mdnie.c" files with the ones from the stock repo. Everything else is identical.
For devs wondering how I made ADBD run as root, I'm sure you already know how to do this, but if not do the following. Go to your ramdisk, open up default.prop, and then:
Change ro.secure=1 to ro.secure=0
Change ro.debuggable=0 to ro.debuggable=1
Change persist.service.adb.enable=0 to persist.service.adb.enable=1
Then recompile. That's it.
-------------------------------------------------------------------------------
And just to protect me:
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE!
Overclock kernels carry an inherent risk. You're pushing your hardware further than it's meant to go. Everything should be safe, and I've tested it myself and I trust it on my phone. But that doesn't mean it's perfect.
If *you* screw up and blame me, I will point at you and laugh. Deal with it.

i think i'll wait a bit to see if this is safe to flash

If I flash this kernel will I get those black screens like I did with Heros rom?
Sent from my SPH-D700 using Tapatalk

plmiller0905 said:
If I flash this kernel will I get those black screens like I did with Heros rom?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I don't notice them, but if you got them on his ROM you may well see them here too since its the same kernel. I recommend you set it on OnDemand scheduler with SetCPU instead of Conservative or whatever the default is

Geniusdog254 said:
I don't notice them, but if you got them on his ROM you may well see them here too since its the same kernel. I recommend you set it on OnDemand scheduler with SetCPU instead of Conservative or whatever the default is
Click to expand...
Click to collapse
Ok sounds good...what about having to hurry up and put the phone to sleep on the intial startup to stop the bootloops, do I have to do the same for this kernel as well?
Sent from my SPH-D700 using Tapatalk

plmiller0905 said:
Ok sounds good...what about having to hurry up and put the phone to sleep on the intial startup to stop the bootloops, do I have to do the same for this kernel as well?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Probably. I've gotten away without doing it, but the last couple boots I've had to. I'll build my own kernel later today and see if that fixes it. Just gotta download the Samsung source and set up a build environment for this instead of my Evo

Geniusdog254 said:
Probably. I've gotten away without doing it, but the last couple boots I've had to. I'll build my own kernel later today and see if that fixes it. Just gotta download the Samsung source and set up a build environment for this instead of my Evo
Click to expand...
Click to collapse
Ok I'll wait to flash this then cause trying to hurry up and put the phone into sleep mode at startup is hell. I'll be looking forward to your kernel and thanks for your hard work.
Sent from my SPH-D700 using Tapatalk

This kernel boot loops your phone. Even with a battery pull. I suggest flashing back to the stock kernel with Odin3.

casual864 said:
This kernel boot loops your phone. Even with a battery pull. I suggest flashing back to the stock kernel with Odin3.
Click to expand...
Click to collapse
are you putting it to sleep as soon as it boots??

Good so far thanx for posting it

BopChie said:
are you putting it to sleep as soon as it boots??
Click to expand...
Click to collapse
Even if I do that, whenever I put the phone to sleep it won't turn back on. Forcing me to do a battery pull.

casual864 said:
Even if I do that, whenever I put the phone to sleep it won't turn back on. Forcing me to do a battery pull.
Click to expand...
Click to collapse
Hmm did you put SetCPU at Set on Boot? I've seen that cause issues before. I know that it's working fine for me, although I occasionally have to do the instant-sleep trick on boot, but not always.
I know that it works for me, and it's reported working in the og. Grimey Goods thread as long as you do the instant-sleep. YMMV

so i dont set setcpu on boot or i do?

evoguyfhp said:
so i dont set setcpu on boot or i do?
Click to expand...
Click to collapse
You can give it a shot. I have it set on boot and it works for me but it's caused problems in the past if you set weird freqs. YMMV

Just posted a new version. Yes, I actually compiled this one
Let me know how it works. I'm going to bed. It's late here. I'll check feedback in the morning and respond to them tomorrow after class.
Enjoy

Geniusdog254 said:
Just posted a new version. Yes, I actually compiled this one
Let me know how it works. I'm going to bed. It's late here. I'll check feedback in the morning and respond to them tomorrow after class.
Enjoy
Click to expand...
Click to collapse
changelog?

[email protected] said:
changelog?
Click to expand...
Click to collapse
See OP. No more issues on boot (don't worry about locking and unlocking as soon as it boots anymore) and no wake issues. To make sure you have no wake issues, use the "ondemand" governor. That's the only one I've tested with. Can't guarantee that on conservative or powersave or any of the others. You can change them in SetCPU

Got It.. D'Oh..

PlankLongBeard said:
Only thing I ask for is a update.zip for returning to stock DI07 Kernal. After that all is well.. (BTW.. Thats for the Just In Case) Makes it Easier!
Click to expand...
Click to collapse
clockwork backup?

BopChie said:
clockwork backup?
Click to expand...
Click to collapse
Yeah, will be doing so, I forgot..

[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?

[SOLVED] Undervolting

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).

[KERNEL][FROYO][OC][08-08-11]PeanutButta Jelly Time - OTB Edition

For the people that want overclocking, here is your chance. I took my standard voodoo kernel, and put in the stuff needed to overclock it. Thanks to nemesis2all and his OTB kernel from the Fascinate for the code needed to get this to work. Also, use extreme caution when using the higher clock speeds. The stock "max" voltage for the CPU is 1300mv, and 1500MHz and 1600MHz are both at 1500mv, so it's heavily over-volted at the top end. By default, the system will boot to 1000MHz and you need to set the speeds you want in Voltage Control App. I don't personally use this because I think overclocking is useless, so any bug reports need as much information as possible, or they will be dismissed and not looked into at all. If you run into an issue with the system locking up, odds are that you have undervolted to much for a given clock speed. Other than that, you're on your own. Same FAQ applies as the regular PBJ kernel, so look there until I get a chance to post it here as well.
Installation Instructions:
1. Download zip
2. Transfer to SDCard
3. Reboot into recovery, you'll need to have CWM if you don't already
4. Install zip from SDCard and select the zip you downloaded.
5. Reboot and enjoy
0808
Make logcat an option that can be turned on/off
-From root shell, run "logcat-enable" to turn logcat on, "logcat-disable" to turn it off
Make /preinstall partition swap space
Fix problem with rooting phone on boot
Fix fix_permissions in recovery
Update to recovery
0731
Fix mount USB Storage in recovery
0730
Updated CWM binary
Custom boot animation support
0709
Voodoo Sound V10
0615
Overclocking - Use Voltage Control App to adjust clocks and voltages
0602
Voodoo Sound fixed - Thanks supercurio
Removed OnDemand
Added FIFO and BFQ IO Schedulers
Added tun.ko and cifs.ko
0531
Initial release, built from source
Undervolted
Voodoo lagfix available - Thanks supercurio
Updated compiler flags
Linaro Toolchain for cross-compiling
Battery hack to allow for non-OEM Batteries - courtesy of SirGatez
init.d support
SDCard speed tweak (via init.d script)
Upstream EXT4 Patches
VFAT Patch
TCP and CFS Tweaks to help data/performance
V(R) IO Scheduler
Auto-root on boot
Maybe missing some other stuff, check Github for full changes
TODO (somewhat in order of importance):
Smooth out boot animation
NOTES:
If you are experiencing problems, I need detailed info to be able to fix it or help you out. Failure to provide detailed info will mean I'm just going to ignore your problem as user error. Details would be something such as which kernel you are flashing (filename) and steps to reproduce the issue. Also, if you used any other kernels that had the same problem or didn't have the problem.
DISCLAIMER
By downloading and using the kernels, this signifies that you have read this full post and the FAQ before reporting an issue. You also take all responsibility if your phone breaks or your warranty becomes void (which, if you're flashing this, it already is). I offer no guarantees as to anything working, though I try not to release broken stuff, it happens sometimes.

FAQ Placeholder

2k+ on quadrant @ 1.4ghz... Niiiiice
Thanks imnuts

Undervolted and running ok so far.
Sent from my SCH-I510 using XDA App

Could you cuties advise on what sort of settings you're using for this?
I'm using the 'vr' setting with an Interactive governor at 1.1GHz and my phone is slowing to a crawl so it's hardly usable. I'm not looking for any crazy overclocking just something to keep my phone snappy whilst I keep in touch with my prostitutes and be sure they are working the proper street corners.
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!

ZeppelinJ0 said:
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!
Click to expand...
Click to collapse
Go into a Terminal Emulator on the device and type Mount. 3rd or 4th row on the list should show ext4. If it does then lagfix is enabled. If you do not see Ext4 and it says rfs still then it is not enabled.

will2live said:
Go into a Terminal Emulator on the device and type Mount. 3rd or 4th row on the list should show ext4. If it does then lagfix is enabled. If you do not see Ext4 and it says rfs still then it is not enabled.
Click to expand...
Click to collapse
Well it's definitely enabled. I just must have set the CPU settings poorly because this thing is crawling right now, I can't even scroll through the app drawer!
I've been trying to CWM back to the other PBJ kernels however my phone hangs on reboot, I'm guessing because those need to be flashed with Odin.

asenduk said:
2k+ on quadrant @ 1.4ghz... Niiiiice
Thanks imnuts
Click to expand...
Click to collapse
I wish I knew what I was doing wrong.. running at 1.4 and my quadrant scores are exactly the same.... not that it really matters but still...

imnuts said:
. I don't personally use this because I think overclocking is useless.
Click to expand...
Click to collapse
Just curious as to why you think it's useless. I am sure you know some thing that I don't so your opinion matters to me. I love the fact that I can overclock, but if it's not needed then I might not bother. I know it did make a difference for my DX.

das7771 said:
Just curious as to why you think it's useless. I am sure you know some thing that I don't so your opinion matters to me. I love the fact that I can overclock, but if it's not needed then I might not bother. I know it did make a difference for my DX.
Click to expand...
Click to collapse
Use a program like CPUSpy that shows you the clock speed stats of your phone. >75% of the time, it will likely be in 400MHz or less, this probably approaches >90% if you say 800MHz or less, especially if you are not a heavy user. At that point, why overclock your phone? To get the overclocking stable, you need increase voltages across the board, and despite undervolting, you'll never get the same power usage as you can with a non-overclocked kernel as some of the voltage changes you can't revert. My opinion is that while overclocking can smooth some stuff out, for most day-to-day usage, it has no practical benefits and only causes more battery drain than you would otherwise have. Given how precious battery life is these days, why knowing make your battery drain faster?

it's funny you say that becuase i noticed with ludeboy's kernel that when overclocking system panel very rarely showed my phone running over the stock speed. Usually it was as you stated some where around 800mhz..I understand what your saying...Thanks for the quick response.

So what if we run stock clock...but undervolt? Do you think we will see any batt savings?

Backup SD and app data b/c crashing/freezing can corrupt files.
Edit: Also keep Voltage Scheduler Remover on your phone just in case.
1600
1500
1400
1300 -0
1000 -25
800 -50
400 -75
200 -100
100 -150
"interactive" was unstable a couple kernels ago so I haven't tried it.

suzook said:
So what if we run stock clock...but undervolt? Do you think we will see any batt savings?
Click to expand...
Click to collapse
Potentially, yes, but you may lose stability.

Awesomeness
I love it. I can deal with a slightly shortened battery life. I wanted to OC because a lot of the more intense games don't run as smooth as I would like. With OC, its all butter. Thanks!! I have mine set at 1400, and it really didn't improve my quadrant scores, but there's a noticeable decrease in lag going from one app to another.

suzook said:
So what if we run stock clock...but undervolt? Do you think we will see any batt savings?
Click to expand...
Click to collapse
You would see better battery life at stock clock speeds if you just used the standard (ie. not overclocked) kernel I built.

Just wondering if you're going to branch off development of PBJT w/o overclocking separately - or if this is going to be built/rolled into future releases?
I'm on board with not thinking it's necessary - though I can see how the tinkerers and speed demons would love it. (And all the more power to them, literally)

I don't know imnuts, I always noticed when I forced the phone into a higher overclock it always seemed quite a bit snapier.

Keep it on conservative. Interactive is buggy.
ZeppelinJ0 said:
Could you cuties advise on what sort of settings you're using for this?
I'm using the 'vr' setting with an Interactive governor at 1.1GHz and my phone is slowing to a crawl so it's hardly usable. I'm not looking for any crazy overclocking just something to keep my phone snappy whilst I keep in touch with my prostitutes and be sure they are working the proper street corners.
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!
Click to expand...
Click to collapse

underscored said:
Just wondering if you're going to branch off development of PBJT w/o overclocking separately - or if this is going to be built/rolled into future releases?
Click to expand...
Click to collapse
This will remain separate from the standard kernel most likely. I will see if I can build off of this source without overclocking and have it work, though I don't know if it will. I want to keep them separate for stability and battery life reasons.

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