Database Info

Overclocking your android msm7k device

Hi there,
Many of you heard of the awesome ToAsTcfh's sauce, and I guess pretty much everyone wonders what the secret is. ToAsTcfh left me the honor to announce it, so here it comes.
It's simply overclocking. (if you read the title of this post, it wouldn't surprise you )
Overclocking msm7k has been supported on wince devices' linux port for a long time now. (months for msm720xa, and maybe even more for 720x and 750x, I haven't see the details). So it's the same idea that has been implemented here.
Making it work was more difficult than for wince devices, because the radio software is way too clever on android. Still, we got past this difficulty, and it works.
It's actually even better than what ToAsTcfh actually got, he posted only older results which were bottlenecked at 620MHz, now this patch provide users with a 710MHz frequency.
And it should work for all msm7x0xa devices. (so that makes almost double speed for stock G1 ).
So, for the explanations, earlier overclocking tries failed, because people assumed that PLL have fixed frequencies, which is wrong, we can set those PLLs frequencies with both multipliers and divisors.
That's what the writel(......) line in the patch does, it changes the multiplier of PLL. The "origin" of the PLL is TCX0 which is running at 19.2MHz.
For people who wants even more overclocking, you can change the values:
the writel(0x25, ......) line,
This value is the multiplier from 19.2MHz to cpu frequency, 19.2MHz*0x25=710.4MHz
You can change it to whatever value you want, but the higher limit seems to be around 750MHz.
If you want to play with mem values, edit the line:
Code:
{ 528000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 160000, 0, 5, -1 },
Change the 3 after 132000, it's the divisor of memory compared to cpu frequency, -1 (with default settings, it's 132MHz=528MHz/(3+1)
The patch is attached, and also available at http://htcandroid.xland.cz/oc.diff.txt
Now the credits, thanks to bzo for the idea, and the implementation on wince devices, and thanks ToAsTcfh for the tests (it really needed a lot of time, even if the patch looks damn simple now, stupid radio software!), and for making me remember he exists.
PS: btw, I also helped getting 3D on eclair for your devices, and I still have no android device at all

is this for real?

.............
yep its not a day dream

wow!!! so where do I push this file to????
edit: Why do I feel like I am about to nut???

its not a file u push to the device. the kernel has to be built with the changes in the patch

toast.... There is nothing I can say but awesome! And you for mod!!

Aww man, i thought we would keep it as a surprise until i had put it in my darchdroid rom . Lol, great work toast

darchstar said:
Aww man, i thought we would keep it as a surprise until i had put it in my darchdroid rom . Lol, great work toast
Click to expand...
Click to collapse
phhusson deserves the credit for this. hes the man

darchstar said:
Aww man, i thought we would keep it as a surprise until i had put it in my darchdroid rom . Lol, great work toast
Click to expand...
Click to collapse
Is this still on schedule to be released this weekend?!
Toast..you're awesome!

as awesome as this seem, one question comes to mind. hows this affect battery life?

as awesome as this seem, one question comes to mind. hows this affect battery life?
Click to expand...
Click to collapse
True but who cares... Lol.
But seriously, its interesting to know.

ok so question is when do we get a stable Rom with this kernel. I suppose I can compile a new kernel my self tonight... source needed or just the changes in the first post?
if I need source who has a git address?
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

kashb91 said:
as awesome as this seem, one question comes to mind. hows this affect battery life?
Click to expand...
Click to collapse
The cpu is overclocked only when used at full load, so if you let it sleep all the time, it won't change much battery life.

2.6.27 or 2.6.29?
.27 I assume...?

can't wait for darch to get this on his legend ROM

obelisk79 said:
2.6.27 or 2.6.29?
.27 I assume...?
Click to expand...
Click to collapse
AFAIK there have been no change on acpuclock from .27 to .29, so .29 should work. You just need kernel's sources.

Awesome news. I thought all work on the overclocking front was pretty much done for . Can it be applied to the new 2.1 releases though without source?
Edit: Question was answered above.

???
where is the dl for the kernel?? can we flash it or was this just a heads up ??

Awesomeee id like a flashable zipp.lol.thanks y'all.**** waiting for the official sprint release lol

*wipes tear from eye*
I love you guys.

Ram Hack for Cyaonogen 5.0.7

Can anybody tell me how to get this? About 2 hours ago i flashed cyanogen 5.0.7 and ive been trying to get the Ram Hack but its just not working. So if you guys could tell me how that would be nice

AndroidKaboom said:
Can anybody tell me how to get this? About 2 hours ago i flashed cyanogen 5.0.7 and ive been trying to get the Ram Hack but its just not working. So if you guys could tell me how that would be nice
Click to expand...
Click to collapse
none so far. just an overclock hack.

since im a noob i dont know what overclock hack is. can you explain?

yes, i would like to know of this overclock hack as well, i have overclocking apps on my mytouch (rooted) but is this hack refering to something you flash, or an add-on specificly for Cyanogen¿
Thank you in advance
~Dark

AndroidKaboom said:
since im a noob i dont know what overclock hack is. can you explain?
Click to expand...
Click to collapse
It makes your phone run WAY faster (in most cases) at the whim of battery life though... never had an issue with the battery, my Mytouch (1.2) with CM 5.0.7 test 5 made it so my battery is like... uber good, very efficiant power management on that rom (once you tinker with it) my old stock Donut FW (1.6) was eating the crap out of my batt, had to recharge once or twice a day, now its every other day! even overclocked!
*** Should have probably said there is no HACK for this yet, only overclocking apps (if im wrong please... flame me lol)
~Dark

Im new to all of this. Can someone please send me step by step directions on how to root my, my touch 3g with the latest
-------------------------------------
Sent via the XDA Tapatalk App

just a word of advice i would google before you ask questions or post problems. there are lots of guides out there this is the one that i used.
I am new so i cant post links but just go to google and search "magic to cyanogen"
also i would recomend a non-test or experiemental rom first. you will save yourself a headache
welcome to mod-ville.... its like farm-ville only cool.

AndroidKaboom said:
Can anybody tell me how to get this? About 2 hours ago i flashed cyanogen 5.0.7 and ive been trying to get the Ram Hack but its just not working. So if you guys could tell me how that would be nice
Click to expand...
Click to collapse
I don't believe this is going to be a fruitful idea, if possible. Cyanogen himself has stated that Eclair is heavily dependent on the GPU and that it would hurt performance to take away GPU memory.

Jigga0o7 said:
I don't believe this is going to be a fruitful idea, if possible. Cyanogen himself has stated that Eclair is heavily dependent on the GPU and that it would hurt performance to take away GPU memory.
Click to expand...
Click to collapse
Yeah, RAM hack's a bad idea here.
I had the RAM hack working on an earlier test version of CM5 (Eclair). While I saw a huge difference and performance boost using it on CM4 (Donut), using it on 5 seemed to actually slow it down a hair.

[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 and overclocking

Since SetCPU was updated today to support the tegra II chip, I thought I would just give you all a heads up. Hope to see some kernels compiled with overclocking slots soon.

coolestmage said:
Since SetCPU was updated today to support the tegra II chip, I thought I would just give you all a heads up. Hope to see some kernels compiled with overclocking slots soon.
Click to expand...
Click to collapse
Cant you overclock by hand without that?

There are a few other apps and methods to overclock. The newest version of setcpu is able to see the slots in clemsyn's kernel, but they don't exceed 1ghz.
Sent from my Droid using XDA App

Looks like the xoom is already OCd to 1.5. Can't wait to see some kernels for us too

Wrong section.
At any rate, I'm sure once coolbho3000 puts his overclock code in github, the kernel devs around here may be able to get these puppies overclocked as well. The difference being that the Xoom as a .36 based kernel as where we are still running .32 based kernels, so there is just as much chance that it doesn't port.
When posting, think of the content and context. This thread is about an app. But this section is for Guides, Kernels, and ROMs to be released. I know this section is where most folks spend most or all of their timing reading/posting, but there are 4 sections for a reason, to keep content organized and relevant. Let's help the mods do that by posting in the appropriate section.

miphonematt said:
Wrong section.
At any rate, I'm sure once coolbho3000 puts his overclock code in github, the kernel devs around here may be able to get these puppies overclocked as well. The difference being that the Xoom as a .36 based kernel as where we are still running .32 based kernels, so there is just as much chance that it doesn't port.
When posting, think of the content and context. This thread is about an app. But this section is for Guides, Kernels, and ROMs to be released. I know this section is where most folks spend most or all of their timing reading/posting, but there are 4 sections for a reason, to keep content organized and relevant. Let's help the mods do that by posting in the appropriate section.
Click to expand...
Click to collapse
Am I missing something? Isn't this in the general section?
Why do there seem to be so many self imposed forum police these days? Seems like half the posts I see are people *****ing at the op

There is a big difference between 36 and 32. Honestly, I only assume this from looking at the latest 38 rc commits and comparing the two. But it seems to be significant, even in its comments and verbosity. What's missing is cpu-tegra.c or the cpufreq driver for tegra written by Colin Cross (android dev) - instead we have NVIDIA's cryptic cpufreq.c .. I can barely understand what's going on with most code.. but it seems like our kernel version is from a time where NVIDIA's code was still being sorted thru by the aforementioned Google dev.

I have setcpu installed however I cant change the governor

collindv said:
Am I missing something? Isn't this in the general section?
Why do there seem to be so many self imposed forum police these days? Seems like half the posts I see are people *****ing at the op
Click to expand...
Click to collapse
Because we are supposed to self police ourselves otherwise the mods just close our forum.

grinch247 said:
I have setcpu installed however I cant change the governor
Click to expand...
Click to collapse
Because your kernel isnt set up to be changed

thebadfrog said:
Because your kernel isnt set up to be changed
Click to expand...
Click to collapse
however I can alter the speed up or down...and check off set on boot..

grinch247 said:
however I can alter the speed up or down...and check off set on boot..
Click to expand...
Click to collapse
Yes and so can I. I can also set the governor with a script or manually. They kernel for the GTab has 2 settings....performance and powersave... and as far as I know setcpu doesnt support the .32 kernel that GTab has. It does support the .36 kernel that the xoom has.

collindv said:
Am I missing something? Isn't this in the general section?
Why do there seem to be so many self imposed forum police these days? Seems like half the posts I see are people *****ing at the op
Click to expand...
Click to collapse
I (one of the two mods) moved this into the General section where it should be. It had been in the Development section which wasn't the right place.
And thebadfrog is correct - we (as a community) benefit when everyone helps everyone out - including making sure posts are created in the right spot, and aren't just another variation on a question that might have been asked 15,245,332 times before.

I apologise for posting in development. I wasn't even paying attention. Thank your for moving the thread for me.

Originally Posted by coolestmage  
Since SetCPU was updated today to support the tegra II chip, I thought I would just give you all a heads up. Hope to see some kernels compiled with overclocking slots soon.
Cant you overclock by hand without that?
__________________
| chuong trinh thiet ke web | Dịch vụ Quản lý website | cty thiet ke web | thiet ke trang website | lÃ*m website giá rẻ

You need a kernel that supports overclocking and the GTab doesnt have one yet

thebadfrog said:
Yes and so can I. I can also set the governor with a script or manually. They kernel for the GTab has 2 settings....performance and powersave... and as far as I know setcpu doesnt support the .32 kernel that GTab has. It does support the .36 kernel that the xoom has.
Click to expand...
Click to collapse
wondering if the xoom setcpu profile would jive w/ our tablets?

The gtbalet's benchmark is around 2,500. The overclocked Xoom got 2850. Standard Xoom @ 1Ghz got 2,150.
Am I missing something???? If the gtablet could be OC'd that would be huge.

grinch247 said:
wondering if the xoom setcpu profile would jive w/ our tablets?
Click to expand...
Click to collapse
Kayak83 said:
The gtbalet's benchmark is around 2,500. The overclocked Xoom got 2850. Standard Xoom @ 1Ghz got 2,150.
Am I missing something???? If the gtablet could be OC'd that would be huge.
Click to expand...
Click to collapse
The profiles won't until the AOSP frequency scaling is imported into the kernel sources - and that's not an easy process. Then the kernel will have to be compiled, etc.
Yes - it'd be nice to be OC'd - but battery life would be affected. It's a tradeoff in many ways....

jerdog said:
The profiles won't until the AOSP frequency scaling is imported into the kernel sources - and that's not an easy process. Then the kernel will have to be compiled, etc.
Yes - it'd be nice to be OC'd - but battery life would be affected. It's a tradeoff in many ways....
Click to expand...
Click to collapse
On my OG Droid I like being able to drop the speed for battery savings when the screen is off if it's not in use. So there's more in it than just big numbers.

Overclocking Kernels for webOS Devices

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