Overclocking Kernels for webOS Devices - WebOS Software and Hacking General

There are a number of overclocking kernels available for webOS devices:
1) UberKernel
This is the kernel that is recommended for most users. It has been comprehensively alpha and beta tested, and has predefined profiles available that have been proven to be functional and safe for all users.
Instructions on how to install and use the UberKernel, and the corresponding Govnah application which is used to set the overclocking and other kernel parameters, can be found in the Preware Homebrew Documentation app in the official Palm app catalog (yes, Palm allows instructions on how to overclock your device in the official app catalog).
The official wiki page for UberKernel is at:
http://www.webos-internals.org/wiki/Application:UberKernel
2) Other experimental kernels
In addition to the UberKernel, there are a number of other experimental kernels developed and released in separate alpha testing feeds. These experimental kernels are used for initial bleeding-edge alpha testing of new kernel development directions and new kernel features. Once these new features have been proven to be stable, they usually migrate into the next beta testing version of the UberKernel.
Instructions for how to install the experimental kernels and the conditions of use can be found at:
http://www.webos-internals.org/wiki/Testing_Feeds
The official wiki pages for these experimental kernels are at:
http://www.webos-internals.org/wiki/Application:PsychoKernel
http://www.webos-internals.org/wiki/Application:WarthogKernel
All of these kernels (both the stable versions and the experimental versions) can be installed on your webOS device using Preware. You do not need to wipe or reflash your device, nor do you need to wipe any of your data (although we do advise you to always have full backups of your data whenever you are using overclocking kernels).
Complete source code for all kernel modifications can be found in the WebOS Internals git repositories at
http://git.webos-internals.org/?p=kernels/patches.git;a=summary
and the build system for building these kernels from these patches can be found in the WebOS Internals autobuilder git repository at
http://git.webos-internals.org/?p=preware/build.git;a=summary
Any kernel hackers who wish to participate in custom kernel development for webOS devices should make themselves known in the #webos-internals IRC channel on Freenode.
-- Rod Whitby
-- WebOS Internals Founder and Project Lead

Hi,
I have my AT&T GSM Palm Pre Plus running WebOS 2.1
I installed Govnah but I can't get the Uber Kernel thru Pre Ware, it says that there are not available overclockable kernels for WebOS 2.1 , I thought HP already released the kernel source.
Best Regards.

MGA2009 said:
Hi,
I have my AT&T GSM Palm Pre Plus running WebOS 2.1
I installed Govnah but I can't get the Uber Kernel thru Pre Ware, it says that there are not available overclockable kernels for WebOS 2.1 , I thought HP already released the kernel source.
Best Regards.
Click to expand...
Click to collapse
It's available in the kernel testing feed. Details on the webos-internals Wiki:
http://www.webos-internals.org/wiki/Testing_Feeds
-- Rod

testing feed?... becareful with kernels that are still in beta.. never know
Sent from my HTC HD2 using XDA App

hakuchi18v said:
testing feed?... becareful with kernels that are still in beta.. never know
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
The thing with the Pre phone is that even if you flash a totally bad kernel, you simply do a recovery mode boot and use the webOS Doctor to flash back a good image.
http://www.webos-internals.org/wiki/How_To_Recover
Or you do a recovery mode initramfs boot, mount the filesystem, and move the backup kernel back into place.
http://www.webos-internals.org/wiki/Memboot
Even if you wipe the bootloader (but you would need to try *really* hard to do this, and no end-user ever has), you can still boot the OMAP over USB and flash a new bootloader.
http://www.webos-internals.org/wiki/Last_Resort_Emergency_BootLoader_Recovery
No real danger at all, since the device has been designed by Palm to be brick-proof.
There has never been a permanently bricked webOS device from homebrew or hacking. Period.
-- Rod

rwhitby said:
The thing with the Pre phone is that even if you flash a totally bad kernel, you simply do a recovery mode boot and use the webOS Doctor to flash back a good image.
Or you do a recovery mode initramfs boot, mount the filesystem, and move the backup kernel back into place.
Even if you wipe the bootloader (but you would need to try *really* hard to do this, and no end-user ever has), you can still boot the OMAP over USB and flash a new bootloader.
No real danger at all, since the device has been designed by Palm to be brick-proof.
There has never been a permanently bricked webOS device from homebrew or hacking. Period.
-- Rod
Click to expand...
Click to collapse
true..
Sent from my HTC HD2 using XDA App

I'm a bit confused. I've added the testing feed and I see a bunch of 1.4.x kernels. None of them have any indication in the description that htey are 2.1 kernels. The Uberkernel I have was released on 1/10, so I'm assuming that it is not the right one.
Sprint Pre running 2.1

drizek said:
I'm a bit confused. I've added the testing feed and I see a bunch of 1.4.x kernels. None of them have any indication in the description that htey are 2.1 kernels. The Uberkernel I have was released on 1/10, so I'm assuming that it is not the right one.
Sprint Pre running 2.1
Click to expand...
Click to collapse
If you're seeing 1.4.5 kernels, then you do not have the correct testing feed installed. This usually happens if you don't follow the wiki directions precisely and name the feed incorrectly. If you follow the wiki precisely and name the feed correctly, then Preware automatically updates the feed version on every boot.
-- Rod

I did follow the instructions, I think it has something to do with how the phone identifies its software. I manually added the 2.1.0 public kernel feed and tried to install Uber, but it errored out saying the kernel is not compatible.

drizek said:
I did follow the instructions, I think it has something to do with how the phone identifies its software. I manually added the 2.1.0 public kernel feed and tried to install Uber, but it errored out saying the kernel is not compatible.
Click to expand...
Click to collapse
What webOS version is reported by your Device Info application?
If it says anything other than HP webOS 2.1.0, then you don't have a correct 2.1.0 installation.
-- Rod

Thanks.
I'm running an alternate kernel at 1000mhz.
Hope it get on stable quickly.
Best Regards.

rwhitby said:
What webOS version is reported by your Device Info application?
If it says anything other than HP webOS 2.1.0, then you don't have a correct 2.1.0 installation.
-- Rod
Click to expand...
Click to collapse
1.4.5
I thought it was supposed to say that to get on the App Catalog. I'm definitely running 2.1.0 though and it works fine.
Edit: I looked at the instructions again and it seems like you modified the scripts, right(i metadoctored on the first day)? Is there a way to force installation of the new kernel or should I go back and rerun the whole thing with the new script?

drizek said:
1.4.5
I thought it was supposed to say that to get on the App Catalog. I'm definitely running 2.1.0 though and it works fine.
Edit: I looked at the instructions again and it seems like you modified the scripts, right(i metadoctored on the first day)? Is there a way to force installation of the new kernel or should I go back and rerun the whole thing with the new script?
Click to expand...
Click to collapse
You need to re-doctor.
-- Rod

Big fan of the AV8B Harrier II kernel here, and I'm glad to see it get on the 2.1 testing feed so quickly.
In my experience the best battery life I've experienced on any kernel, and it has been extremely stable for me as well.

How is the battery life when you have everything overclocked? I used to have a Pre -, but left cause of sprint before the plus even came out, and I am missing webos a lot. I am going to get a pre plus on verizon soon, and want to overclock it while I wait for the Pre 3 to come. I just want to know how much better the batter life is with a different kernal if at all.

card0124 said:
How is the battery life when you have everything overclocked? I used to have a Pre -, but left cause of sprint before the plus even came out, and I am missing webos a lot. I am going to get a pre plus on verizon soon, and want to overclock it while I wait for the Pre 3 to come. I just want to know how much better the batter life is with a different kernal if at all.
Click to expand...
Click to collapse
I believe the battery life should be worse, not better when overclocked. However, my pre- is overclocked and I haven't noticed any difference in battery life. Of course, how you use your phone plays a big role in the battery life so your experience may differ from mine. I recommend trying it for yourself.

Jive Turkey said:
I believe the battery life should be worse, not better when overclocked. However, my pre- is overclocked and I haven't noticed any difference in battery life. Of course, how you use your phone plays a big role in the battery life so your experience may differ from mine. I recommend trying it for yourself.
Click to expand...
Click to collapse
A lot depends on the voltage and governor of a kernel I have a nexus s clocked to 1.4 ghz with bit of undervolting and battery life is comparable to the stock kernel. Just depends on how the Dev builds it.
Sent from my Nexus S 4G using XDA Premium App

Related

[1.267GHz!!!] [Devs] Overclocking/undervolting patches (update 6/15)

I got an EVO myself and managed to overclock it to 1.267GHz. We could probably go even higher, but that requires more extensive changes. Here are the changed source files: http://dl.dropbox.com/u/36553/supersonic_oc-uv.tar.gz
It also includes an undervolt courtesy of pershoot (a whole 0.1V lower when idle, which should help battery drain a lot!). Here is a test update.zip: http://dl.dropbox.com/u/36553/supersonic_oc-uv_signed.zip (working WiFi). Make sure to do a nandroid backup first!
Sensors/camera do not currently work in this kernel because the source is not yet complete.
There is an overvolt on the highest frequencies. It should not cause any issues. Thanks to toastcfh for his source, Herver for creating the first booting overclocked kernel on the EVO, all the kernel devs in the N1 community, especially pershoot and kmobs, richardtrip from the Desire community, koush for anykernel updater, and all who helped to root the EVO. Enjoy!
Update 6/15: Fixed 950mV undervolt. Raised voltages from 1228800 above to improve stability. Source files updated and update.zip uploaded.
old said:
I posted these in an earlier thread, but I think I should bring this to everyone's attention. Here are some simple patches that will overclock the Evo up to 1.267GHz (though by any means it's not guaranteed to get that high!):
Edit: please don't flash the below update.zip, as it doesn't seem to boot. Devs, the patches are still below, and a zimage is in the anykernel update zip.
Update: I compiled it myself. Here is an update.zip: http://dl.dropbox.com/u/36553/update-oc_signed.zip. This uses toastcfh's sources, Koush's excellent anykernel updater and a config.gz pulled from a stock Supersonic. If this doesn't boot, no damage will be done to your phone. Just reboot into recovery and reinstall your ROM. You can test overclocking by grabbing SetCPU from my sig or changing the cpufreq values if you know how. Once we get this working, I will create an undervolted version for battery savings. I'd get an Evo, but it's sold out everywhere T_T
http://dl.dropbox.com/u/36553/supersonic_oc.zip
cpufreq.c and acpuclock-scorpion.c are in arch/arm/mach-msm, and supersonic_defconfig is just the config. I don't have an Evo, so I can't test these out, but these should work with the source files toastcfh posted earlier: http://forum.xda-developers.com/showthread.php?t=686240.
Undervolting can be achieved simply by adjusting the voltages (in mV) in the acpu_freq_tbl table in acpuclock-scorpoion.c. For those not familiar with his work, you can see pershoot's safe (but lower) voltages for the N1 here: http://github.com/pershoot/nexus-kernel/blob/master/acpuclock-scorpion.c. If you want to overvolt or go under 1000mV, you have to make one further adjustment to the voltage regulator in board-supersonic.c.
Note that the N1 and the Evo are completely different devices (with similar processors), so what may work for the N1 may not work for the Evo.
Click to expand...
Click to collapse
Awesome... until I am sure this is stable, I will wait, but I must have overclock
jigglywiggly said:
Awesome... until I am sure this is stable, I will wait, but I must have overclock
Click to expand...
Click to collapse
I don't recommend overclocking, the devices already can run warm at current settings.
But then again, you are entitled to do as you wish.
Options better than overclocking are to remove the Sprint bloatware and strip down parts of Sense, this speeds things up alot by removing excess background applications.
Well it ain't too bad, my Droid at 1 ghz(550 stock) runs great.
So this should be good too.
I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...
phinnaeus said:
I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...
Click to expand...
Click to collapse
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.
Well, I agree with the benchmarking comments but on the subject of Froyo... Froyo is designed to be even faster on equivalent hardware than 2.1... and 2.1 on my Evo is smooth as silk. And the Evo handles most Flash I can throw at it, so I'm not sure. I have however noticed a small performance difference with live wallpaper running, so maybe OCing will clear that up a bit.
Jus10o said:
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.
Click to expand...
Click to collapse
You know, this is an excellent point and I feel like I failed the developer community in some small way when you had to bring it up. You shouldn't have to provide a reason for wanting progress, it should happen for its own sake.
Proceed.
Jus10o said:
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.
Click to expand...
Click to collapse
Agree with everything you just said, and I am less than excited about the benchmarks with the EVO thus far
Roman G said:
Agree with everything you just said, and I am less than excited about the benchmarks with the EVO thus far
Click to expand...
Click to collapse
HAHAHA.. im sorry but i had to laugh at your sig.
Jus10o said:
HAHAHA.. im sorry but i had to laugh at your sig.
Click to expand...
Click to collapse
Ya I sold my hero a couple weeks before the EVO dropped, and had to use my wife's old phone.
phinnaeus said:
I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...
Click to expand...
Click to collapse
I'm not trying to start an argument at all but you have to think broader mathematically. If the processor runs at 1000Mhz or 999mhz (In the case of my N1) a .267 increase is 267mhz, a 26.7% increase in computational performance... That's pretty raw especially in cellphone terms, that have no way to vent or displace that kind of heat.
Has anyone noticed how much hotter the kickstand gets? I bet you that it's attached to something the cpu is connected to. $5 bucks says we will see KICKSTAND HEATSINK + FAN MOD 2GHZ OC! LOL
thebluecoat said:
I'm not trying to start an argument at all but you have to think broader mathematically. If the processor runs at 1000Mhz or 999mhz (In the case of my N1) a .267 increase is 267mhz, a 26.7% increase in computational performance... That's pretty raw especially in cellphone terms, that have no way to vent or displace that kind of heat.
Has anyone noticed how much hotter the kickstand gets? I bet you that it's attached to something the cpu is connected to. $5 bucks says we will see KICKSTAND HEATSINK + FAN MOD 2GHZ OC! LOL
Click to expand...
Click to collapse
This is a patch for developers, not a discussion thread for the merits (or lack thereof) of overclocking.
If you don't want to overclock your phone, nobody is making you.
It has worked out fine in the Desire and Nexus One community.
coolbho3000 said:
This is a patch for developers, not a discussion thread for the merits (or lack thereof) of overclocking.
If you don't want to overclock your phone, nobody is making you.
It has worked out fine in the Desire and Nexus One community.
Click to expand...
Click to collapse
how do i apply this ???????
can u make it flashable?
mccurt29 said:
how do i apply this ???????
can u make it flashable?
Click to expand...
Click to collapse
need to follow the directions in the first post. the .c files need to be loaded into the kernel source (right now just have toast's soruce) and the kernel has to be compiled with them.
if somebody wants to compile up a kernel with these, we could start testing. if i get some free time i'll help out here and compile a kernel but somebody else will prob beat me to it!
please someone let us know how this works out for your evo 4g... benchmark, test results... anything to show better/worse performance, whether your got ALOT warmer, or just a lil, etc.. ne information would be greatly appreciated it, i'm not a 100% noob, i just know how to follow instructions very well, doesn't mean i understand everything that's going on, just the basic concept of what i want. thank you in advance.
madunix said:
please someone let us know how this works out for your evo 4g... benchmark, test results... anything to show better/worse performance, whether your got ALOT warmer, or just a lil, etc.. ne information would be greatly appreciated it, i'm not a 100% noob, i just know how to follow instructions very well, doesn't mean i understand everything that's going on, just the basic concept of what i want. thank you in advance.
Click to expand...
Click to collapse
I'm waiting for someone to compile this first.
If nobody steps forward, I'll make my own attempt, but I'll be working blind with no test hardware.
I'm pretty sure most devs are waiting on the htc source kernal before playing with this. I can't wait but I understand them being hesitant to do too much with this for now. Still awesome of you to post it and have it rdy for when that time comes!
sounds good.
madunix said:
sounds good.
Click to expand...
Click to collapse
Your signature says you have a radio of 1.32.651.6, just to let you know that is not a radio, that is an HTC software OTA update. My radio is 1.39.00.05.31 for example

SetCPU for Android

I'm sure almost all (if not all) of you that have obtained root on your Incredible (which this app requires) know what this app is and possibly have even used it in the past. There doesn't appear to be any Incredible specific modifications made to the app yet, but I just wanted to throw this out there. As always, be VERY careful with overclocking, esp. with this CPU (I personally wouldn't try anything over 1.2ghz). If you feel your phone getting hot, don't keep running it! Also neither the author, XDA or I take any responsibility in the case that you toast your Incredible.
http://www.pokedev.com/setcpu/
I thought we'd need a modded kernel to run it over 1.2 Ghz? How can we do that with just rooting the phone and installing setcpu?
Or I'm way off and I have no idea what I'm thinking lol..
andrew53517 said:
I thought we'd need a modded kernel to run it over 1.2 Ghz? How can we do that with just rooting the phone and installing setcpu?
Or I'm way off and I have no idea what I'm thinking lol..
Click to expand...
Click to collapse
no, you are correct. i have built the kernel (HTC release) w/ the required changes. but have not been able to flash
Wow I wasn't aware of the kernel limits, or maybe I subconsciously read it somewhere since I threw 1.2ghz out there (over the last couple weeks I've been dealing with a cold I can't seem to shake so I blame a combination of insomnia+Nyquil... mmm Nyquil).
Id say its worth some green to get that kernel. I have been looking high and low to find one. seems that the demand is there but not the development. Let me know if you get it up and running and I'll donate to the cause.
Just wish I could develop it at this point, but getting the phone rooted was a task for me. Even with video instructions....

[Kernel] [Updated 22OCT] HeroC - 2.6.35.14

This can now be considered stable, after significant testing and use by the community. As always, the hero you save could be your own, so be safe.
This would not have been possible without the efforts of everyone in the community that played a part in moving the ball forward. In particular s0be and riemer for their initial efforts to get a working 2.6.35 build as a baseline, and the continuing efforts of riemer, erasmux, arco, et al; also thanks to toast, darch, decadence, pershoot, and cyanogen, as well as the Linux, CM, AOSP, and CAF teams that have provided the broad shoulders for tinkerers like myself to stand on. My sincere gratitude to all of these and the legion of others who I have not listed, who have contributed to making the open source community strong and productive.
This kernel is based on a combination of updated board files for HeroC, and efforts by arco, riemer, erasmux on new sources originally from the HTC marvel code release. After several weeks on the new base, everything appears to be working well. Initial sources have been posted to github.
New version (2.6.35.14) is at:
https://github.com/TeamHeroC/heroc-kernel-2.6.35
The sources for this Kernel and the AOSP flavored 2.3.5 ROM sources are posted to the TeamHeroC github. This organization github was created instead of using a personal github so that others could join in team development efforts if they are interested, and the organization could be more easily maintained after people move on to other devices. I am probably looking at somewhere between 2-5 months myself.
Flash from recovery, and remember nandroid is your friend.
UPDATE - KERN-2.6.35.14-10SEP-V1.0.zip
10SEP version has been updated with changes from various sources. Github has also been updated to be in sync with this update.
UPDATE - KERN-2.6.35.14-22OCT-V1.1.zip
22OCT version has been updated with changes from various sources. Github has also been updated to be in sync with this update.
Old version - No Longer in Development
This is very much a work in progress, so be safe.
This would not have been possible without the efforts of everyone in the community that played a part in moving the ball forward. In particular s0be and riemer for their efforts to get a working 2.6.35 build as a baseline; also thanks to toast, darch, decadence, pershoot, and cyanogen, as well as the Linux, CM, AOSP, and CAF teams that have provided the broad shoulders for tinkerers like myself to stand on. My sincere gratitude to all of these and the legion of others who I have not listed, who have contributed to making the open source community strong and productive.
This kernel is based on a combination of the s0be/riemer board files and other mods applied to the CyanogenMod cm-kernel android-msm-2.6.35-unified branch. It does not have smartass (not working yet), but the camera seems to work consistently for me on both interactive and ondemand (Note: setting min cpufreq to 352 is recommended to minimize camera problems). This is still very much an early effort, but thought I would post for anyone interested. Initial sources have been posted to github.
https://github.com/TeamHeroC/cm-kernel-heroc
New version (2.6.35.14) is at:
https://github.com/TeamHeroC/heroc-kernel-2.6.35
The approach to building this kernel was to go back to a build based on the last CM 2.6.35 source from the repo and add files from the s0be/riemer source tree to get a working kernel. My goal is to get this as close to standard source as possible, so the changes will just be the device specific board files, drivers, etc. The reason for this approach is to (hopefully) get a well defined set of files and updates that can be applied to other kernel releases (.37, .38, ...) with minimal conflicts and dependencies.
Lots of things that I will be working on as time permits. In no particular order this includes things like:
complete headset updates
update qdsp5_comp to align with latest sources
update smd files to align with latest sources
rework board files to current standards
check and complete i2c updates
complete USB updates
compare and update MSM frame buffer files
cpufreq updates and smartass governor
check and update device specific drivers
The sources for this Kernel and the AOSP flavored 2.3.4 ROM sources are posted to the TeamHeroC github. This organization github was created instead of using a personal github so that others could join in team development efforts if they are interested, and the organization could be more easily maintained after people move on to other devices. I am probably looking at somewhere between 2-5 months myself.
Flash from recovery, and remember nandroid is your friend.
Added No Headset version as suggested by s0be. This version has no headset drivers built in. In theory, this should improve the stability of your USB functions. This has had very little in the way of testing. YMMV.
Thank You,
Flashing now!
painter_ said:
Thank You,
Flashing now!
Click to expand...
Click to collapse
Thank you this great news!!!!!
Sent from my HERO200 using XDA Premium App
Awesome news.
Thanks JB for picking this up.
jaybob413 said:
Flash from recovery, and remember nandroid is your friend.
Click to expand...
Click to collapse
Thanks again Jaybob,
One question, Ive been running the kernel that you posted on s0be's thread a few days back, is this one updated or is it basically the same? So far no Camera bug for me (which is why I flashed to begin with).
chalan30 said:
Thanks again Jaybob,
One question, Ive been running the kernel that you posted on s0be's thread a few days back, is this one updated or is it basically the same? So far no Camera bug for me (which is why I flashed to begin with).
Click to expand...
Click to collapse
A few changes since then, but nothing major. I can't really say whether it is better or worse than the previous. Seems about the same to me. I will add the previous version to the OP later as well.
jaybob413 said:
A few changes since then, but nothing major. I can't really say whether it is better or worse than the previous. Seems about the same to me. I will add the previous version to the OP later as well.
Click to expand...
Click to collapse
Radical.
Thanks for your efforts. The previous version has been working well for me on your May 30th rom with FR 118_15 with some autokiller tweaks. Battery life seems a little worse but still very decent. All very smooth with ADW eX and LPPro . Had a couple of issues with the phone locking up (black screen) for about 20 30 seconds, then coming back on its own. Not sure if it was because my min was too low on setcpu (on demand). Not that it matters but my linpack scores have been consistently lower. but real world performance is great.
Lets see how this does.
so totally didnt see this thread until just now.. thanks a ton jaybob.. this kernel has some loyal followers, and i know i can say for most of them that i am glad to see someone who is capable pick this up.. i was trying my hand at it, but i dont have the time right now, and my knowledge base just isnt as broad as it needs to be for this.. so thanks man, you are the best..
3 Hours now and it seams stable. It took a little while after the first boot before my phone became stable. The ROM I am running the 5/25 version of Evervolv.
painter_ said:
3 Hours now and it seams stable. It took a little while after the first boot before my phone became stable. The ROM I am running the 5/25 version of Evervolv.
Click to expand...
Click to collapse
Yeah these .35 kernels usually take a few minutes to warm up. but they tend to get tremendously better with time..
sent from my... wait.. what..
This thing is running too smooth on the latest nightly. Someone pinch me!!
pstevep said:
Yeah these .35 kernels usually take a few minutes to warm up. but they tend to get tremendously better with time..
sent from my... wait.. what..
Click to expand...
Click to collapse
Its kinda weird how they do that... but they do go nice after a little while!
and jaybob this build is running a lot smoother than the last one.. on a whole, its smooth a silk, camera is working great.. kudos so far man..
jaybob413 said:
(Note: setting min cpufreq to 352 is recommended to minimize camera problems)
Click to expand...
Click to collapse
Isn't camera supposed to engage perflock?
jasonmaloney said:
Isn't camera supposed to engage perflock?
Click to expand...
Click to collapse
No perflock in this kernel (or s0be's or deca's). My recommendation is just based on an observation that when the min cpu freq was set to a very low value (19), I would see a lot of camera freezes. It may work fine at lower settings, I normally have mine set to 352 and don't have camera problems with ondemand or interactive, so this is just what has worked for me. It may also be fine at 264 or 176, but I haven't tried them.
Running this kernel with the latest CM7 nightly and I've never seen my Heroc run so smooth nor get this crazy good battery life.
Thanks JB.
Haven't checked to see if I get my regular reboot after 10 minutes of Google navigation.
I was using sobe's .35 kernel and the camera worked at first but lately wouldn't work at all and I saw that the camera was supposed to be working well with this. Flashed it a little while ago and haven't been able to take a single picture. My cpu is ondemand with a min/max 518/768.
braczkowski said:
I was using sobe's .35 kernel and the camera worked at first but lately wouldn't work at all and I saw that the camera was supposed to be working well with this. Flashed it a little while ago and haven't been able to take a single picture. My cpu is ondemand with a min/max 518/768.
Click to expand...
Click to collapse
i honestly think that right now some of the camera stuff is phone specific.. because i know some people have no issues, asome people have intermittent issues (me), and some people lose it all together.. but thats how it was with s0be's version as well, i think until most of the camera bugs are squashed we will continue to see random issues for random people..
BTW since you already cant use the camera, try switching to interactive for the governor, and try it then.. jaybob said that his works fine with interactive, so maybe your phone will respond better with it.. just a thought, no promises..
352 min cpu fixed my camera issue.

overclock area on cm9 greyed out

Why is the overclocking area on my Captivate greyed out after installing cm9 latest nightly???
I honestly do not have the time to read hundreds of pages of forums to see if someone has allready had this issue.
Of course i tried searches.
It happens on any cm9 nightly, not just the latest one.
I want to be back at 1.2ghz. being stuck at 1ghz. is rediculous to me after being so spoiled. (lots of google earth, gaming and other stuff that a higher clock speed helps with)
If I have to I will just go back to 2.3.7 and a swift 1.3ghz. MAX
BUT it seems like I should be able to overclock using CM9 on my captivate.
Please do not explain the system settings and performance yadda yadda yadda, anymore, i am obviously familiar enough with an android device to know how to use system settings etc. if i can root and install custom roms i can read and point and click as well.
Sorry for the frustruation but i seriously can not deal with anymore nonsense and 80 diff. pieces of broken info from people that only "heard from some guy" about how to do all this.
Thank you in advance... forever learning"!"
yellowfuse said:
Why is the overclocking area on my Captivate greyed out after installing cm9 latest nightly???
I honestly do not have the time to read hundreds of pages of forums to see if someone has allready had this issue.
Of course i tried searches.
It happens on any cm9 nightly, not just the latest one.
I want to be back at 1.2ghz. being stuck at 1ghz. is rediculous to me after being so spoiled. (lots of google earth, gaming and other stuff that a higher clock speed helps with)
If I have to I will just go back to 2.3.7 and a swift 1.3ghz. MAX
BUT it seems like I should be able to overclock using CM9 on my captivate.
Please do not explain the system settings and performance yadda yadda yadda, anymore, i am obviously familiar enough with an android device to know how to use system settings etc. if i can root and install custom roms i can read and point and click as well.
Sorry for the frustruation but i seriously can not deal with anymore nonsense and 80 diff. pieces of broken info from people that only "heard from some guy" about how to do all this.
Thank you in advance... forever learning"!"
Click to expand...
Click to collapse
Were you using Glitch before, or some other custom kernel? I didn't think cyanogen's stock kernel supported overclock. If you install a new nightly you have to reinstall your overclocking kernel.
I have been using cyanogenmod only. I never purposefully installed a custom kernel then the rom. Just used Odin to root/clockwork and so forth. Never heard of Glitch. Through out all of my custom rom experiences with the captivate I have been able to use the sys. settings or osmonitor to overclock to a max of 1.3ghz. I have tried miui or whatever its called for about five minutes. other than that just cm6/7, then updated to cm9. in the past whatever kernel i had, stayed in effect, i guess.
I will do a search for custom kernels for cm9 on captivate.
I havent seen any yet, but who knows. I am used to simply stunning roms and the moto droid one. That was great! SS/chevy~ would always have links to the latest kernels avail. for the current builds etc. Good job too.
SO... the search continues.
*Mystery: If I cant even change cpu settings in osmonitor (up or down), yet it lets me enable root mode, what does that mean? The greyed out overclocking area in perfomance settings (up or down)???
I need to learn more"!"
As mentioned, glitch kernel b6 is a great ics kernel. Flash over CM9 and install nstools from the market to control all the kernel settings such as oc/uv, voltages etc etc.
Sent from my glitched ICS Captivate using XDA App
The options are greyed out because the stock kernel currently doesn't support overclocking. Glitch is awesome, and Semaphore kernel is pretty nice too.
Sent from my CM9 ICS i897 Captivate
IcyGlitch for OC, and Semaphore for 400MB mem.
Well Glitch has 387 MB of free RAM
both kernels are good
I want my 13 MB! They are unused so occupying them is unforgivable. IcyGlitch is solid kernel, and I hope 400MB will be added.
b-eock said:
Well Glitch has 387 MB of free RAM
Click to expand...
Click to collapse

[Q] Need root/rom/etc recommendations for an odd Captivate setup.

I just picked up this OEM-condition ATT Captivate today and after playing around with it, installing apps on it, fixing the rear speaker, etc...I decided I want to root it and try out a good/reputable/reliable ROM.
Here's the tricky part...this phone doesn't have service, nor will it ever. That's right. Absolutely no cellular service for this device. I'm using it strictly as a home phone for incoming/outgoing calls on my WiFi using GrooveIP + my google voice number(and maybe some games/radio/etc) and as an emergency phone when I'm away from home and in other WiFi hotspots. Otherwise I've got this crappy little tracfone that I use almost exlusively for texting and the rare phone calls I need to make. Just can't justify wasting money on a contract or any other setup with the way I use phones anymore.
So considering how I use this phone is it worth rooting? If so, what ROM could I go with that will be significantly better than the OEM setup but not require j33t hax to mess around with? If this were my main cell I wouldn't mind going all out on it like I've done with every other phone I've owned, but since I use it this way I can't really justify dumping a ton of time and effort in to it. I just want something clean, cool, and reliable.
If it helps any here's the apps I have/use currently...
-Advanced Task Killer
-Play Store
-Zedge
-Firefox
-Youtube
-GrooveIP
-Gmail
-Facebook
-Words With Friends
-AdAway(Don't use it, but would like to)
Here are my software versions...
Firmware Version - 2.3.5
Baseband Version - I897UCKK4
Kernal Version - 2.6.35.7-I897UCKK4-CL614489
Build Number - GINGERBREAD.UCKK4
which stock os version are you running? eclair, froyo or gingerbread?
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Check the development forum. Someone created a ROM called captivate touch. I think it is what you're looking for.
Sent from my SAMSUNG-SGH-I897 using xda premium
laughingT said:
which stock os version are you running? eclair, froyo or gingerbread?
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
I'm brand-new to droid phones so I really have no idea what those names beyond being OS versions apparently.
Firmware Version - 2.3.5
Baseband Version - I897UCKK4
Kernal Version - 2.6.35.7-I897UCKK4-CL614489
Build Number - GINGERBREAD.UCKK4
Red_81 said:
Check the development forum. Someone created a ROM called captivate touch. I think it is what you're looking for.
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
Thanks for the recommendation. I'll check that one out.
Check out Legend 5. It's the best for KK4 Gingerbread (Tested by me).
The link is on my sig just click it. :good:
takeoutttt said:
Check out Legend 5. It's the best for KK4 Gingerbread (Tested by me).
The link is on my sig just click it. :good:
Click to expand...
Click to collapse
Thanks, checking that out now.
The ROM mentioned by a poster above doesn't look to be supported anymore and I don't think it's compatible with my KK4 GB.
Could someone explain to me real quick how this ROM stuff works? To my knowledge this phone has a Firmware and an OS, and if that's the case, does the ROM replace the OS and/or the Firmware? Or is it installed and ran separate from my Firmware and OS? If there's a thread that explains this, a link would be much appreciated.
Answered my own question. I'm going with the Legend 5 ROM + CORN kernel 7.06 using the Odin method. Installed the kernel first, now trying to figure out how to get the pop-up menu when I plug the USB cable in so I can go to mass storage mode in order to put that ROM.zip file on there. I guess it doesn't do that anymore with the new kernel?
Install went without a hitch. Noticing a lot of visual differences, but not much in the way of performance differences.
Does this CORN kernel lock my phone in at 1.60GHz or did I misread something?
Does having this kernel mean my phone is now "rooted?"
johnnyrichter said:
Install went without a hitch. Noticing a lot of visual differences, but not much in the way of performance differences.
Does this CORN kernel lock my phone in at 1.60GHz or did I misread something?
Does having this kernel mean my phone is now "rooted?"
Click to expand...
Click to collapse
Corn kernel gives you a ROOTED status, and enables you to use "schedulers and governors" and a 1.2Ghz CPU speed which is confirmed safe. Download CPU Spy and Voltage Control in play store so you can monitor your CPU usage and can adjust between schedulers and governors. I use Legend 5 ICS.
Not sure if I want to go as far as OCing anything. Just looking for a nice ROM that fits my needs.
Legend5 seems nice but it has some issues here and there and the way I use the phone doesn't really benefit from a majority of the changes it offers. I'll keep messing with it and see if I can like it a bit more.
takeoutttt, I got CPU Spy and Voltage control but what I'm seeing on my screen doesn't match any of the walkthroughs I found for VC.
On the main screen I have the Scheduler dropdown, Governor dropdown, and two slider bars...one for minimum speed and one for maximum speed. I see no other dropdowns, no other sliders, no advanced screen, no voltage controls, etc.
Options in scheduler dropdown; noop, deadline, cfq(default).
Options in governor dropdown; conservative, userspace, powersave, ondemand, performance.
Settings are default for now until I can figure this out.

Categories

Resources