Edit: It was actually coded by phhusson, in conjunction with toastcfh and others. See thread here: http://forum.xda-developers.com/showthread.php?t=665515
This thread is about a new overclock kernel patch for the MSM7K, which includes the G1 and Magic.
Devs working on overclock kernels. If you want your overclock kernel in OP (here) send me a PM and I'll consider linking to it.
For devs, the original patch is here, and an updated commit to allow for scalable frequencies is here
There's also an autodetection patch for SetCPU by coolbho3000 himself here
pershoot's github for the lazy: http://github.com/pershoot/ds-kernel
Downloadable Kernels to Flash for the Rest of Us
These kernels are not officially endorsed by Cyanogen for his ROM, so use at your own risk and do not file any bug reports to the ROM owners. pershoot has done some good things to this for Cyanogenmod including some extra frequencies to choose from.
EBI0 version = 32B Magic or G1 on 1.x or 2.x radio
EBI1 version = 32A Magic or G1 on 3.x radio
2.6.33.3 for any rom EBI0/EBI1 by pershoot
Has lots of tweaks and goes up to 576 MHz
Verification:
This works. Read the thread.
Video proof of 614 MHz: http://www.youtube.com/watch?v=9Oaesb0OX8k
FAQ:
A) How do I try this without flashing this to my phone?
If you want to try this without flashing your phone, download the zip file for your phone. First turn OFF wifi. Then turn your phone off.
Now go into fastboot. Extract boot.img, probably in the same folder as your fastboot application. Then use:
Code:
fastboot boot boot.img
(replace boot.img with the name of the img file)
This will make the kernel run temporarily on your phone up till your phone is restarted again. Do NOT turn your wifi on at this time, because it will freeze your phone. If you want to keep it, flash the whole zip file from recovery. Otherwise just restart your phone and you will be back to whatever you had before.
B) Ramhack?
What is known as the ramhack is done by modifying the kernel source code with a patch and making a new kernel to flash. Hence you see a boot.img in the zip files you flash.
This overclock kernel patch modifies the source code of the kernel. If you want both ramhack together with the overclock, you need a kernel that contains both the ramhack AND the overclock patch. If not explicitly stated, you can assume that the overclock patched kernel does not contain the ramhack patch and thereby does not have ramhack.
C) What phones does this work on?
All HTC Dream/G1 and myTouch/Magic, not including Fender or 1.2 editions of the Magic for the precompiled kernels in this thread.
If you are applying the patch yourself it should work on any MSM7K device.
D) What are some prerequisites I need to flash this?
Custom recovery compatible with test keys, or root with working adb/fastboot.
And you need a compatible phone (see C)
E) My wifi doesn't work after I flashed x.img file!
YOU MUST FLASH THE CORRESPONDING WIFI MODULE WHENEVER YOU FLASH THE KERNEL.
The .img file contains the kernel, which requires a patching wifi module to be recompiled (wlan.ko located in your system volume) with that kernel.
If wlan.ko was not provided, wifi will simply not work. Ask whoever compiled that kernel to provide a wlan.ko file for you to flash.
F) Is this stable?
Stability seems to vary, but at the moment I do not recommend using 614 MHz for day-to-day use.
This kernel does not even run stable at 614 MHz right now for me, or at least when I try to just plug in my usb cable. Not sure what can be done there. I threw in the 653 MHz EBI1 kernel that wouldn't boot for me for kicks.
My gut feeling of being unable to boot at 653 MHz and being unstable at even 614 Mhz leads me to think that the G1 is a pretty hopeless overclock. The 32B Magic might have better luck. CDMA Heros are getting up to 700 MHz easily on the other forum. It is not surprising that HTC designed the phones to have higher clock tolerances than the G1 designed to run at 384 MHz.
(DEVS/COOKS) Original kernel patch to overclock from 528 MHz to 711 MHz, but that wouldn't boot. Boots fine at 614 MHz on my G1 with 3.x radio. Probably more stable at lower speeds.
For all MSM7K devices including the Hero, Dream, Magic
Credits:
phhusson for sharing
ToAsTcfh for coming up with it
Cyanogen because it's his kernel source
benbuchacher for Super D
farmatito for EBI0 compile
coolbho3000 for SetCPU
pershoot for some great compiled kernels
Notes:
I am not a dev!
This patch performs more changes the kernels source in acpuclock.c and involves the software modification of the way PLL is handled to allow for the overclock.
It is different than the previous OC patch that only modified the frequency table.
This patch adjusts the 528 MHz clock to 711 MHz, and can be modified by changing the patch file. Acceptable clocks are multipliers of TXCO (19.2MHz).
710.4 MHz = 19.2 * 37
Should work on 2.6.27 and 2.6.29, and maybe more.
Some devs have already added this to their CDMA Hero ROMs with reports of success.
xaueious said:
From Hero CDMA forums:
http://forum.xda-developers.com/showthread.php?t=665515
I am not a dev so my deductions may not be that correct.
This patch performs more changes the kernels source in acpuclock.c and involves the software modification of the PLL to allow for the overclock.
It is different than the previous OC patch that only modified the frequency table.
This patch adjusts the 528 MHz clock to 711 MHz, and can be modified by changing the patch file.
Should work on 2.6.27 and 2.6.29, and maybe more.
For everyone else who doesn't know this is, don't flame yet. I want someone to patch their kernel source and report back. If you don't know what that means try not to contribute.
I haven't tried this for myself because I don't have a lot of experience building kernels, and my source is way outdated such that it will take me the whole night to sync my repos.
Some devs have already added this to their CDMA Hero ROMs with reports of success.
I am withholding my judgement on this for now.
Click to expand...
Click to collapse
Sounds sweet, but is it real this time? however if it is, its going in my new kernel
It had already been established before that this won't work on Dream because the chip's PLL is set to a clock where the maximum stable speed you can get is 528 Mhz and the next, acceptable speed (not placebo like the one tried before) crashes the phone.
i thought the PLL was written in software?
I was doubting this too, but there's indication that it is different this time.
jad011 said:
i thought the PLL was written in software?
Click to expand...
Click to collapse
This is what this patch does differently.
Someone try this!
xaueious said:
This is what this patch does differently.
Someone try this!
Click to expand...
Click to collapse
not bricking my phone today
Dude you can't brick your phone with a patched kernel like this.
No devs willing to try it? The patch might be quick one. Just take a look.
The diff might not apply as is since it was made for CDMA Hero. In any case, I'm not worried because I'm sure that we will figure something out.
http://forum.xda-developers.com/showthread.php?t=557863
http://forum.xda-developers.com/showthread.php?t=631810
http://forum.xda-developers.com/showthread.php?t=630236
it's been tried, turned out to be duds
jubeh said:
http://forum.xda-developers.com/showthread.php?t=557863
Click to expand...
Click to collapse
I know. I asked the dev about the exact same thing with the exact same threads!!!
Here was his reply: http://forum.xda-developers.com/showpost.php?p=6234015&postcount=91
Do me and everyone else a favor and go to the thread in the OP and READ
If not just look at the diff file. You'll see what I mean. This HAS NOT been done before.
Better be for real. This'll defiently help the myTouch Slide ROMs run.
If this is real, I'm going to buy the slim extended battery for g1 and flog another 6 months or so out of this bad boy.
I really wish I knew how to use this patch. I would be very willing to flash this on my device Can someone who knows how to do it for the sake of our curiosity, instead of just ignoring it? Unless things are tested, every solution proposed is a possibility Thanks in advance guys!
If anyone wants to post up a build/boot.img with this hacked on, I'd be willing to risk my spare G1 to test the results.
this isnt going to brick your phone
The guys over ad cdma hero forum have a rom with 746mhz...
Who can tell if it works? not me...
for me the speed is fast enough already with 512 mhz fix... but clocking from 128 to 746 mhz on demand would be epic
and then the new mytouch slide rom... rocking it at the moment. love my phone like never before
Update can wait
AWESOME!
This is great! I was hoping someone would find a way to OC this processor! There's a Hero Rom with it confirmed working with benchmarks that look really promising. I can't wait for it to be built into a rom for us G1 users!
..so why doesn't someone just patch it in and give it a shot?
Well I am trying to boot it and my phone freezes with the stock patch after displaying the bootscreen. Trying one more time and lowering the multiplier from 37 to 34.
34 * 19.2 = 652.8 MHz -> FAILED
Didn't boot properly either. It stopped with the line "D/BT HSHFP( 706): Starting BluetoothHeadsetService" in logcat for me. Phone freezes after video goes on. The entire boot seems fine otherwise, even building dalvik-cache and everything.
Boots with what I think is 614.4 MHz, for a 16% overclock, CM-kernel patched:
My Linpack on Super D without JIT is about
2.04 seconds with 2.647 Mflops after multiple runs.
My Super D install is really choppy on CM-kernel though. Until I figure out how to build wg-kernel I wont be keeping this.
2.35 seconds with 2.308 Mflops after multiple runs
The improvement of 15% is inline with theoretical values!
Anyways I think this proves that this OC is doing something!
Proof of concept kernels for Super D 1.10.2 (should work on some other ROMs)
Based on cm-kernel
Should be running at 614 MHz. BogoMIPS wont report it, and the kernel is not going to report the frequency it is running at since the change is internal. But the benchmark shows an improvement so I'd say this works.
EBI1 version is for 32A or people on 3.x radios only! (aka me)
G1/32B version is coming.
(ramzswap.ko is in there but you might not even need it. I left it there because I was too lazy to take it out)
Notes
No point of building this unless this is done with wg-kernel with RAMHack for me. This is a proof of concept rather than something you should use as an everyday kernel. I found wg-kernel at 528MHz with RAMHACK to be smoother despite the higher benchmarks of the 614 MHz kernel.
Someone can try different frequencies...
Sounds great... I am a bit surprised why people are not more enthusiastic about this? Just because the previous OC was found to be wrong doesn't mean that we give up right?
Anyway, how do we apply this to our devices? Just flash it from recovery? Or ? Sorry, am a noob, but would like to test it out Btw, Thanks for the good news
xaueious said:
Well I am trying to boot it and my phone freezes with the stock patch after displaying the bootscreen. Trying one more time and lowering the multiplier from 37 to 34.
34 * 19.2 = 652.8 MHz -> FAILED
Didn't boot properly either. It stopped with the line "D/BT HSHFP( 706): Starting BluetoothHeadsetService" in logcat for me. Phone freezes after video goes on. The entire boot seems fine otherwise, even building dalvik-cache and everything.
Boots with what I think is 614.4 MHz, for a 16% overclock, CM-kernel patched:
My Linpack on Super D without JIT is about
2.04 seconds with 2.647 Mflops after multiple runs.
My Super D install is really choppy on CM-kernel though. Until I figure out how to build wg-kernel I wont be keeping this.
2.35 seconds with 2.308 Mflops after multiple runs
The improvement of 15% is inline with theoretical values!
Anyways I think this proves that this OC is doing something!
Proof of concept kernels for Super D 1.10.2 (should work on some other ROMs)
Based on cm-kernel
Should be running at 614 MHz. BogoMIPS wont report it, and the kernel is not going to report the frequency it is running at since the change is internal. But the benchmark shows an improvement so I'd say this works.
EBI1 version is for 32A or people on 3.x radios only! (aka me)
G1/32B version is coming.
(ramzswap.ko is in there but you might not even need it. I left it there because I was too lazy to take it out)
Notes
No point of building this unless this is done with wg-kernel with RAMHack for me. This is a proof of concept rather than something you should use as an everyday kernel. I found wg-kernel at 528MHz with RAMHACK to be smoother despite the higher benchmarks of the 614 MHz kernel.
Someone can try different frequencies...
Click to expand...
Click to collapse
To be honest it doesn't look that useful for the G1. But I would still like to see a dev pick this up for reaping the little benefits that this does promise.
I'm at least hopeful that we can get stable 576 MHz for all roms from now on.
Related
this is for 32A RADIO 6.35.* and SPL 1.76.2007 please do not try this on anything else as it could damage your phone!!
i am not responsible for any damage, brick, your phone exploding or radioactive batteries
this is new kernel for cursorsense, but it can also be used on any other 1.5 ROM for 6.35 radio
i have overclocked the kernel so it can run 1 GHz
but it is set to be between 660 MHz to 1 GHz so most of the time it will be on 800 MHz
this is still W.I.P. so mind before flashing! and always make a backup of your phone before
i will take any request for anything! so please reply with some info on what to clean up, work on or optimize
at last but not least i would like to thank
-eugene373: for the first script used for this and his idea
-charnsingh_online: for his support, testing, giving me the idea to this and working along my side in the whole progress
-Cursordroid: for the fantastic Rom, kernel and support
- everyone else that have helped just a little bit with this. especially you reporting and giving feedback!
the update zip contains: boot.img, wlan.ko and compache modules
to install simply flash on top of the ROM
version 0.2
min: 245 MHz
max: 998 MHz
cleaned up the script allowing the overclocking so its smaller and reacts better
this is not finished build so please comment what can be done!
should be more stable than V0.1
link to download
4shared: http://www.4shared.com/file/218371784/43a55720/CCR-06-RalleGade-V02.html
megaup: http://www.megaupload.com/?d=JQXVI9Q6
version 0.1
min: 660 MHZ
max: 1 GHz
i have cleaned out most debug options from the kernel so it's now booting even faster!
cleaned: ocfs2, jbd2 ext2, 3 and 4
a bit more responding overall
link to download:
4shared http://www.4shared.com/file/218319243/3d4b922b/CCR-06-RalleGade.html
megaup http://www.megaupload.com/?d=GA1WD1UZ
How dangerous is it to use this? Any overheating, freezes, battery leaks or similar issues? How would it affect the lifespan of the processor?
Plus im not sure if google thought that such things would be done and implemented any counter-measures...like BSOD in windows...
can you mirror the file on megaupload or rapidshare, reason being im in china atm and 4shared seems to be blocked
Has anyone tried this?
1ghz? That's kind of double the CPU speed, i fail to see how that's safe to do on a cellphone
i tried , my magic runs on this kernel @ 825mhz , and everything seems to be ok , of course device is hot
the overclocking is installed over the existing rom - so it can be undone by restoring a nand backup or re-applying the rom's update.zip?
@michaldepa: what is hot? a little bit more or really boiling hot?
hone2009 , device is a little bit more hot than stock , stable for one hour , with ~10 phone calls and 10minuts teeter.
It would be nice to stable the overclocking around 650/700Mhz, maybe the heat and the battery loss wouldn't hurt much.
I'll keep an eye on this thread, but i'm not trying it yet.
ralle.gade said:
i will take any request for anything! so please reply with some info on what to clean up, work on or optimize
at last but not least i would like to thank
eugene373: for the first script used for this and his idea
charnsingh_online: for his support and for giving me the idea to this
link to download: http://www.4shared.com/file/218170587/2c5c149a/CCR-06-RalleGade.html
the update zip contains: boot.img, wlan.ko and compache modules
to install simply flash on top of the ROM
Click to expand...
Click to collapse
I would just like to ask: can anyone work one for old radio??
As I'm still on 1.33.0009 spl with old radio, reluctant to flash to new spl or radio as it'll brick my phone easily
can it even work on old radio?
Of course it can, I'm also looking for a port for the old radio.. maybe something for super d
Great work!
Do you have plans to extend the patch to other ROM (e.g. Eclair)?
@ralle.gade Where are your modiffied kernel source or patch for overclock?
It's not here yet as I wanna make some finetuning tweeking and porting to other roms until then enjoy what you got
And BTW what roms do you want this for?
ralle.gade said:
It's not here yet as I wanna make some finetuning tweeking and porting to other roms until then enjoy what you got
And BTW what roms do you want this for?
Click to expand...
Click to collapse
Super D 1.8 - Ahmgsk port for old radio...
If you cant do that then make one for the new radio
Thanks in advance!
Your welcome!
working wifi
Hello, this kernel is great, but could You do something about wifi, i can't even run it please
That should be Fixed with the WLAN.ko included!
can you make something for MARSDROID SPL7 1.8 B, it on a new radio. but its donut, not cupkake.
Is this worth? I mean, are the benefits worth the risk? How's the battery doing? Is the phone noticeably faster?
Thanks
Update to the universal overclock. I've tested it working on several ROMS... seems to be better than my first one. Based off dumfuq's latest OC kernel for CM5 which is based off the latest cyanogenmod. Instructions are the same as below. Let's set some G1s on fire!
EDIT WIFI FIXED NOW
UNIVERSAL OVERCLOCK VERSION 2.01 WIFI FIXED
This can be flashed right over what you have now
EDIT IT DOES WORK ON 1.5-1.6 ROMS !!!!!
Below you'll find a link to an overclock update.zip ... all you have to do is flash it, regardless of your ROM and use set cpu to tweak your settings. It will allow you to clock the CPU up to 825mhz!!! Anything over 768mhz locks up the phone so you may want to set a max value via userinit.sh. 652mhz seems to be stable for me
WARNING: Overclocking can shorten battery life and kill the PROC on your phone. I'm in no way responsible for your phone getting hotter than the sun and exploding.
NANDROID BEFORE FLASHING THIS
I'm not a DEV... i just like to tinker. All I did was notice this and throw it all together--------CREDIT GOES TO Dumfuq, Koush and Pershoot for making this possible
Instructions:
----------------------
INSTRUCTIONS HAVE BEEN CHANGED
*Download and install setcpu.
*Select auto detect (ensure it is set at 528mhz) make sure "set on boot" and "ondemand" are selected
*Download and flash THIS update.zip up to 652mhz Stable or this stable 576mhz overclock from Pershoot from recovery and reboot
*Go back into setcpu... hit "menu" and select autodetect again ...you'll notice you now have frequencies for up to 825mhz
*Configure min and max frequency to your liking (652mhz seems to be best for me) (you may want to set a sleep profile of 245min/245max since you won't need OC while you aren't using the device)
*Enjoy
TESTED AND WORKING ON Cyangenmod 5.0.7 / KingKlick's ERIS2G1 / ZXHero 1.5 / ZXHero 2.1 / KingKlick's Legend2G1 / NoSense 1.5 / HTC CLay's Superfast / ALL CSDI ROMS !
ive been waiting on something like this thanxxxxxx
but installation aborted it said something like E: kernal
mccurt29 said:
ive been waiting on something like this thanxxxxxx
but installation aborted it said something like E: kernal
Click to expand...
Click to collapse
What ROM are you flashing this on top of?
Agreed, the zip isn't signed correctly. Here's a working version.
Might want to thank Koush and Pershoot for the kernel script too.
This sounds awesome, it could make many sense roms much more usable as a daily!! Will flash and test later tonight when I get home from work. Thanks!
carl2990 said:
i get
E: Wrong digest:
Kernal/zImage
E:Verification failed
using cannon v2.0
Click to expand...
Click to collapse
Sorry for the confusion I did not sign the zip properly. SHOULD BE WORKING NOW.
Would you be willing to talk about how this works and how it can work on any Rom. I would be interested in knowing that.
EDIT ... Actually I found some info in the overclock thread. Thanks.
billquinn1 said:
Would you be willing to talk about how this works and how it can work on any Rom. I would be interested in knowing that.
Click to expand...
Click to collapse
Uses Anykernel.zip created by Koush
updater-script runs and extract the boot.img from your current ROM.
It unpacks the boot.img into kernel and ramdisk.
It repacks newboot.img with the new kernel and the same ramdisk.
It flashes the newly created boot image.
I got the source HERE
infinitybiff said:
Uses Anykernel.zip created by Koush
updater-script runs and extract the boot.img from your current ROM.
It unpacks the boot.img into kernel and ramdisk.
It repacks newboot.img with the new kernel and the same ramdisk.
It flashes the newly created boot image.
I got the source HERE
Click to expand...
Click to collapse
This is very clever. Thanks.
0o koush's anykernel from github nice thinking
sunsean said:
This sounds awesome, it could make many sense roms much more usable as a daily!! Will flash and test later tonight when I get home from work. Thanks!
Click to expand...
Click to collapse
makes Eris2G1 fly!!!!!!!!!!
So if I'm reading this right, your using koush's anykernal method (which pershoot uses on his kernals) with dumfuq's patch. Good ****.
You might want to let people that dumfuqs kernal defaults to 8xx at boot, so a lot of people won't boot if they don't set default boot after flashing. This can be done with userinit.sh or in /system/banner or something like that if u don't have an ext partation w/userinit.sh. its explaind how to push the line in other theard. Id copy and paste here, but I'm driving right now, lol.
You also might want to give pershoot xtra kernal a shot also. It maxes at 576, but also has other optimasations included and if stable on all g1's.
fastludeh22 said:
So if I'm reading this right, your using koush's anykernal method (which pershoot uses on his kernals) with dumfuq's patch. Good ****.
You might want to let people that dumfuqs kernal defaults to 8xx at boot, so a lot of people won't boot if they don't set default boot after flashing. This can be done with userinit.sh or in /system/banner or something like that if u don't have an ext partation w/userinit.sh. its explaind how to push the line in other theard. Id copy and paste here, but I'm driving right now, lol.
You also might want to give pershoot xtra kernal a shot also. It maxes at 576, but also has other optimasations included and if stable on all g1's.
Click to expand...
Click to collapse
Thanks for the heads up. I've edited the instructions to install set cpu first so when they flash the update it will still boot up at 528 and they can change accordingly
Can we use an alternative other than SetCPU?
flexnix said:
Can we use an alternative other than SetCPU?
Click to expand...
Click to collapse
I'm pretty sure you can set the max speed via userinit.sh.... something like
"#!/system/bin/sh
echo 633600 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq"
in other news i just got this to work on a 1.5 sense ROM!!!!!!
Thanks, I'm about to test this out
Thanks bro!
Does anyone know if I can just flash this ota with just my phone? I downloaded the zip ota, and astro shows that it's on my sd card, but when I go to recovery to flash zip, it's not showing up...?
Just impatient to try this cuz it sounds sweet, lol, but I know if I can't do it ota I can do it later tonight at home...
sunsean said:
Does anyone know if I can just flash this ota with just my phone? I downloaded the zip ota, and astro shows that it's on my sd card, but when I go to recovery to flash zip, it's not showing up...?
Just impatient to try this cuz it sounds sweet, lol, but I know if I can't do it ota I can do it later tonight at home...
Click to expand...
Click to collapse
move the file to the root of your sdcard if you downloaded OTA its probably in sdcard/downloads or something
Please Read
This will not change anything on your phone that would prevent you from ever flashing a new rom or nandroiding back to a working one. Everything this update will do can completely be erased with a wipe or nandroid. Also flashing any rom, clean install or not, will preplace the boot.img this update.zip puts on your phone. So dont blame these downloads for your simple user errors of not being able to flash a new rom or nandroiding.
This is an overclocked kernel from toastcfh godmode .29 source. The kernel was actually pulled from Fresh Toast
This works on DamageControl and roms based off of his, it will not effect any of DC mods, including the Dconig app.
UPDATE
6/6/10- This should be working on the newest damagecontrol 2.09. Please report (if overclocking has worked in the past for you) if you have a problem on the newest release.
Click to expand...
Click to collapse
I made an attempt to get compcache to work, so it might or it might not. Someone with more experience might want to double check it.
Both include setcpu.txt for Setcpu OC app.. Select "custom" at the very bottom for device. Do not select hero. Or you can select "Auto Detect" at the top, this does not need the setcpu.txt.
*View attachment damage710v2.zip* THIS IS A TEST KERNEL FOR THE NEWEST DAMAGECONTROL 2.09.. It is the exact same as damage710 but with a newer ramdisk, this is in hope of fixing any problems anyone is having with 2.09 and OC kernel. There might not even be a difference in the new ramdisk between the old one. I didnt have time to check. Sooo ya.
*View attachment damage537.zip* 537mhz is the default.. scalable to 768 if you use an OC'ing app
*View attachment damage768.zip* 768mhz default clock speed -read below
*View attachment damage710.zip* 710mhz default clock speed -read below
Both can be scaled from 19.2 to 768mhz..
DAMAGE710--The damage710 will default 710mhz, you must use an OC app to scale it to 768. Use damage710 if your phone can not boot the 768mhz. And dont scale any higher then 710mhz or your phone might reboot.
DAMAGE768--If your phone can boot the 768mhz then either download will work. But if you dont want to use an OC'ing app then the damage768 will scale to 768mhz.
This IS a flashable update.zip.. This will only replace your boot.img of your phone. So it is not a full rom. This is applied on top of your rom.
ALWAYS MAKE A NANDROID BEFORE FLASHING.
You Do Not Need A Partition On Your Sdcard For Overclocking
THIS IS A MUST FOR SWAP/compcache
To get swap working, you must have an ext partition on your sdcard. This will format you sdcard erasing everything, so do the following. Back up everything from your sdcard to your computer(exp- In a folder on your desktop named Sdcard). In recovery, select partition sdcard, use all default values, 32mb swap, 512mb ext partition, the rest fat32. Then when its finished change ext2 to ext3. Then reboot the phone. And then move all the files you backed up to the computer back to your sdcard.
If thanking me for putting this together. You should also give an even bigger thanks to Toastcfh for this kernel.
Thanks also goes to flipzmode, cuz i pulled the kernel from his boot.img in fresh toast.
Also darchstar for the defaulting clock speed tip.
So does this mean we can get the real AOSP dialer on Damaged's ROM?
mattshaver said:
So does this mean we can get the real AOSP dialer on Damaged's ROM?
Click to expand...
Click to collapse
No.. this just adds overclocking and the few extra things that come along with it in the kernel. Has nothing to do with AOSP.
you rock
10 char
Excuse my ignorance on this topic.
But with Darchdroid, the issue was porting the Eris .29 Kernal to get a full hardware working AOSP Rom (I think) , so what is the difference?
My apologizes for taking up the space with my questions. Just a noob trying to get his facts straight.
If anyone wants to know how to do this, follow this guide starting at Step 8.
Essentially just extract the kernel you want from the right boot.img, extract the ramdisk from the other boot.img, then use mkbootfs and makebootimg to put them back together.
PM me if you need help.
mattshaver said:
Excuse my ignorance on this topic.
But with Darchdroid, the issue was porting the Eris .29 Kernal to get a full hardware working AOSP Rom (I think) , so what is the difference?
My apologizes for taking up the space with my questions. Just a noob trying to get his facts straight.
Click to expand...
Click to collapse
I dont mind, ask anything here. Its how we learn
But that was the issue with all 2.1 roms. Toastchf cracked the code (in a way, not literally). And was able to give us a working source for .29 kernel. That kernel can then be used to work on any cdma hero 2.1 rom. But there are different things you have to do to get it to work on Darchdroid AOSP rom, he has already done that and its in his newest release. This one I posted above is just to work with damagecontrol roms or ones based off of it.
To get the AOSP dialer working you would have to have a rom based on AOSP, which darchdroid is the only rom so far. All the other roms are based on htc framework or just something different then AOSP. But im pretty sure theres AOSP dialers for damagecontrol. Go check the apps and themes section.
EDIT: the dialers are also completely separate from the kernel. Its based on what the rom is.
i'm running ic3rom and in the process testing it out
jeremysterling said:
i'm running ic3rom and in the process testing it out
Click to expand...
Click to collapse
If you downloaded the compcache one, can you go into terminal and type
adb shell
free
Tell me if it says "swap" in what comes up and that it doesnt have all 0's.
ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help
I think I may be confused as to what exactly the kernel's role/job is, as well as to what the drivers role/function are.
a kernel is what tells the hardware how to interact with the software, and drivers are what tell the software how to interact with the hardware? Correct?
So, why would it take a different kernel to run a full AOSP ROM? Why not just write new drivers for the difference of hardware?
On another topic. The framework would be comparable to what CounterStike is to Half-Life. It still uses the underling software, but is modified and branded in its own way as to give such a "proprietary" feel?
I am so confused. (Google here I come)
schmooo said:
ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help
Click to expand...
Click to collapse
It doesnt effect jit at all. It only adds a few files and changes your boot.img.
schmooo said:
ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help
Click to expand...
Click to collapse
JIT is controlled by other variables, namely build.prop and the dalvikvm.so library; it won't hinder those settings at all.
Jus10o said:
If you downloaded the compcache one, can you go into terminal and type
adb shell
free
Tell me if it says "swap" in what comes up and that it doesnt have all 0's.
Click to expand...
Click to collapse
i used adb on my computer (not sure if that makes a difference):
C:\androidsdk\tools>adb shell
# free
free
total used free shared buffers
Mem: 195764 193404 2360 0 7384
Swap: 0 0 0
Total: 195764 193404 2360
#
Re: [KERNEL] Toast-godmode .29 source for DamageControl
So I can flash this and oc icerom? Etc....
-------------------------------------
Sent via the XDA Tapatalk App
mattshaver said:
I think I may be confused as to what exactly the kernel's role/job is, as well as to what the drivers role/function are.
a kernel is what tells the hardware how to interact with the software, and drivers are what tell the software how to interact with the hardware? Correct?
So, why would it take a different kernel to run a full AOSP ROM? Why not just write new drivers for the difference of hardware?
On another topic. The framework would be comparable to what CounterStike is to Half-Life. It still uses the underling software, but is modified and branded in its own way as to give such a "proprietary" feel?
I am so confused. (Google here I come)
Click to expand...
Click to collapse
Haha well you are right sorta on what the kernel does, but all cdma htc heros use the same kernels but it depends on what android version you are using. 1.5 uses .27 kernel, and 2.1 can use a edited .27 kernel but something things wont work, like camera. What toast did was made his own .29 kernel based on other sources and what we already have then we use for our 2.1 roms. The 2.1 roms that come from sprint use a .29 kernel that work, but we cant edited anything within the kernel until they release the source to the kernel. You must have source to the kernel to be able to change anything with in it. You cant download a rom from xda and take the kernel out and change the files and put them back. You have to already have the files to the kernel, change what you want, make your own kernel and then put it on the rom. Cuz once you compile the kernel its not able to be opened back up.
In a boot.img there are 2 parts, the kernel and a ramdisk. The ramdisk CAN be opened back up and changed. But if its trying to call something within the kernel it has to already be there, since you cant add anything to it. If you start with all the kernel files and compile your own like what toast did, then you can add the special things like overclocking frequencies.
I know I really suck at explaining things. I only know the basics of how it all works.
jeremysterling said:
i used adb on my computer (not sure if that makes a difference):
C:\androidsdk\tools>adb shell
# free
free
total used free shared buffers
Mem: 195764 193404 2360 0 7384
Swap: 0 0 0
Total: 195764 193404 2360
#
Click to expand...
Click to collapse
And you have the compcache.. or the newer one i posted?
Jus10o said:
It doesnt effect jit at all. It only adds a few files and changes your boot.img.
Click to expand...
Click to collapse
Decad3nce said:
JIT is controlled by other variables, namely build.prop and the dalvikvm.so library; it won't hinder those settings at all.
Click to expand...
Click to collapse
sweet im gonna give it a try
Jus10o said:
And you have the compcache.. or the newer one i posted?
Click to expand...
Click to collapse
i downloaded and flashed damage1.zip with compcache
jeremysterling said:
i downloaded and flashed damage1.zip with compcache
Click to expand...
Click to collapse
Ok thanks.. yea compcache and swap arent working. Ill work on it.
But overclocking and everything else is. So its not gunna make a noticeable difference.
11-24-2010 UPDATE
http://www.ziggy471.com/2010/11/24/ziggy471-kernels-incbravoevo-updated-24-nov/
11-14-2010 UPDATE
http://www.ziggy471.com/2010/11/14/ziggy471-kernels-incbravoevo-updated-14-nov/
11-13-2010 UPDATE
http://www.ziggy471.com/2010/11/13/ziggy471-kernels-incbravoevo-updated-13-nov/
11-05-2010 UPDATE - Sorry for the late update!
http://www.ziggy471.com/2010/11/05/ziggy471-evo-kernels-fps-fixed-updated-5-nov/
10-28-2010 UPDATE
http://www.ziggy471.com/2010/10/28/betaziggy471-evo-kernel-updated-28-oct/
10-26-2010 UPDATE!
ZIGGY updated the kernel. Here is the link. (It's the link that has evo in it)
http://www.ziggy471.com/2010/10/26/...credible-aospevobravo-kernels-updated-26-oct/
ZIGGY, thanks for visiting this thread and thanks for a great kernel.
10-25-2010
Hey Everyone, first of all I DO NOT take any credit for this kernel. I came across it in Myn's Rom thread and since it didn't have it's own thread, I just wanted to start one so people could find it easily. I also noticed it in VirusRom's thread. So whoever ziggy is, thanks a lot! I'm getting great battery life on this kernel and according to the threads, it looks like others are also. Here's the link to ziggy471 website with the download. Thanks again ziggy!
http://www.ziggy471.com/downloads/?did=31
source can be found here ~~~> https://github.com/ziggy471/linux-2.6.32.25/tree/evo
gotshores said:
Hey Everyone, first of all I DO NOT take any credit for this kernel. I came across it in Myn's Rom thread and since it didn't have it's own thread, I just wanted to start one so people could find it easily. I also noticed it in VirusRom's thread. So whoever ziggy is, thanks a lot! I'm getting great battery life on this kernel and according to the threads, it looks like others are also. Here's the link to ziggy471 website with the download. Thanks again ziggy!
http://www.ziggy471.com/downloads/?did=31
Click to expand...
Click to collapse
+1 on this bro! Found the kernel this morning while looking for bakes kernel lol. Awsome one got lil lags here n their but can b workable
Sent from my PC36100 using Tapatalk
ya man, i ran it the other day and had great battery, but i thought it had affected my 4g connection, so i flashed another kernel. i reflashed ziggy's today because i missed the battery effect and i haven't had any issues all day (4G connects just fine). I not too technical, so i don't know the in's and out's of this kernel, but i do notice my battery life at the end of the day.
you said that you came across it on Myn's ROM. Is that the ROM your currently running? Just want to see how it works on others
ya, i'm using myn's rom and have only used that so far. would be interesting to see how it run's on other roms
im using a htc evo 4g with ziggys Ziggy471Kernel-EVO-update_signed-10242010-1644
on the download page it says alot but doesnt really explain how to access anything.
http://www.ziggy471.com/2010/10/23/z...kernel-23-oct/
i cannot adb in, says device not found, but via terminal if i do lsmod i get this
bcm4329 210342 0 – live 0xbf000000
if i try init.d or /proc/undervolt i get permission denied.
i did enter SU before entering anything, i dont know whats going on.
if i do cat /proc/undervolt i get the list of undervolt values like shown a few pages ago...
can anyone help?
Ziggy471 HTC EVO Kernel 23 Oct
NOTICE: I am not responsible for anything that may or may not happen to your phone, except for maybe it running faster. You break it, you fix it.
23 Oct 2010:
Kernel version 2.6.32.24
Overclocked
1.28GHz, I don’t recommend this setting, it doesn’t appear to work on the newer Desire ports. I recommend 1.113 or 1.15.
BFS 357 CPU Scheduler
BFQ IO Scheduler
Swap enalbed
SLUB (Unqueued Allocator)
All CPU governors, Interactive is the default
CPU Undervolt control via /proc/undervolt – built in, not a module
http://forum.xda-developers.com/showthread.php?t=775997&highlight=voltage+module
Fix for slow SD card access
http://forum.xda-developers.com/showthread.php?t=815557
CIFS
EXT4
TUN
A few tweaks here and there.
etc…
Also included in the update:
1. For any ROM that has busybox’s run-parts enabled, I added a screen state frequency/governor switching script, located in /system/etc/init.d. This means you do not have to use setcpu to control the frequency or governor anymore. If you prefer not using this script, delete it
The defaults for the script:
AWAKE_GOVERNOR=”interactive”
AWAKE_GOVERNOR_FREQENCY_MAX=”1113600″
AWAKE_GOVERNOR_FREQENCY_MIN=”245000″
SLEEP_GOVERNOR=”powersave”
SLEEP_GOVERNOR_FREQENCY_MAX=”460800″
SLEEP_GOVERNOR_FREQENCY_MIN=”245000″
2. remount script that will be installed to /system/bin.
Valid input format:
remount [ro|rw|status]
ro = read only (default)
rw = read write (to make modifications)
status = current mount mode
3. hosts file that blocks most ads, if you find more, let me know
also new kernel released on the 24th...
http://virusrom.com/Kernels/Ziggy471/Ziggy471Kernel-EVO-update_signed-10242010-1644.zip
hmm might give this kernel a try...I'm willing to try anything to save battery life...
intheb0x said:
Ziggy471 HTC EVO Kernel 23 Oct
NOTICE: I am not responsible for anything that may or may not happen to your phone, except for maybe it running faster. You break it, you fix it.
23 Oct 2010:
Kernel version 2.6.32.24
Overclocked
1.28GHz, I don’t recommend this setting, it doesn’t appear to work on the newer Desire ports. I recommend 1.113 or 1.15.
BFS 357 CPU Scheduler
BFQ IO Scheduler
Swap enalbed
SLUB (Unqueued Allocator)
All CPU governors, Interactive is the default
CPU Undervolt control via /proc/undervolt – built in, not a module
http://forum.xda-developers.com/showthread.php?t=775997&highlight=voltage+module
Fix for slow SD card access
http://forum.xda-developers.com/showthread.php?t=815557
CIFS
EXT4
TUN
A few tweaks here and there.
etc…
Also included in the update:
1. For any ROM that has busybox’s run-parts enabled, I added a screen state frequency/governor switching script, located in /system/etc/init.d. This means you do not have to use setcpu to control the frequency or governor anymore. If you prefer not using this script, delete it
The defaults for the script:
AWAKE_GOVERNOR=”interactive”
AWAKE_GOVERNOR_FREQENCY_MAX=”1113600″
AWAKE_GOVERNOR_FREQENCY_MIN=”245000″
SLEEP_GOVERNOR=”powersave”
SLEEP_GOVERNOR_FREQENCY_MAX=”460800″
SLEEP_GOVERNOR_FREQENCY_MIN=”245000″
2. remount script that will be installed to /system/bin.
Valid input format:
remount [ro|rw|status]
ro = read only (default)
rw = read write (to make modifications)
status = current mount mode
3. hosts file that blocks most ads, if you find more, let me know
also new kernel released on the 24th...
http://virusrom.com/Kernels/Ziggy471/Ziggy471Kernel-EVO-update_signed-10242010-1644.zip
Click to expand...
Click to collapse
Is there a changelog for the latest?
Trying it now. I wonder why he left out 2 of the most popular frequencies 1119 and 1228. Goes from 1115 to 1280, thats a pretty big jump......
myn said on his thread that he can confirm that adb doesn't work on the kernel released on the 24th also. if ziggy gets adb to work, he's gonna recommend it. i don't use adb, i do use terminal emulator every now and then, but haven't check to see if that wouldn't work either.
phistyle said:
hmm might give this kernel a try...I'm willing to try anything to save battery life...
Click to expand...
Click to collapse
I just grabbed it and id say Im a heavy user and i took it off the charger at 4:30am and it just died on me at 11 something ... id say pretty good battery life... using Myn's Rom
Problem with the broken adb shell is that it's causing some users to have problems using Titanium Backup. I love the kernel, but won't use it as a daily driver until Ti works without issue.
gotshores said:
myn said on his thread that he can confirm that adb doesn't work on the kernel released on the 24th also. if ziggy gets adb to work, he's gonna recommend it. i don't use adb, i do use terminal emulator every now and then, but haven't check to see if that wouldn't work either.
Click to expand...
Click to collapse
Crazy, ADB works fine for me with the one from the 24th.
do i have to go into adb shell in order to change the clock speed?
sorry im a newb...
f10g44 said:
do i have to go into adb shell in order to change the clock speed?
sorry im a newb...
Click to expand...
Click to collapse
you can use setcpu or Overclock wideget
nugzo said:
Crazy, ADB works fine for me with the one from the 24th.
Click to expand...
Click to collapse
you lucky ****er lol,
i think your the ONLY one adb shell is working for!
ugh,
we need to get someone in here that knows how to run and tweak this kernel.
its got so much crap built in and its hard to access it all, i wish there was a write up for us evo owners...
someone get ziggy in here or someone that knows about this!
The kernel that was released on the 24th seems to be well put together, I'm oc to the fullest and stable as can be, will report back what the battery life is.
Funny thing my ADB has nvr been broken and the 24th works fine for me
Sent from my phone.. I think Tapatalk???
I'm trying to get a functional config for the 1.2 mytouch but I'm having trouble tracking down the exact source to the MT3G-Fender-1.2-2.6.35.12-10M-test4.zip kernel but it's proving rather tricky. I can't seem to determine what the source to this kernel is and where to pull it.
If anyone can point me in the correct direction i can start on some work.
I pulled some pre-packaged git repo from ezterry's github. ezterry-kernel-biff-testing-5fba47e
I pulled my config from the running kernel from the zip i mentioned above running on my phone.
I built the kernel produced from using that config and the wlan.ko module.
Using this guide : http://forum.androidcentral.com/htc...how-build-your-own-kernel-package-source.html
I just want to be sure the kernel source i'm starting out with doesn't need extra patches that weren't included in the github pull in order to get it to work on the 1.2.
thanks for any help.
I'm also looking at cyanogenmod's github and will probably build a kernel against that pull this week as well.
Still, would like to know what sets the kernel i mentioned above apart from just straight pulls of these repos. That's the only part really confusing me.
Hey I was wondering if you could make this kernel your building an OverClock kernel too. No one has built one for our MyTouchs 1.2 that is truly for this device.
The Max OC I've been able to pull of is 725 without the phone freezing and rebooting.
Idk just thought it would be a good idea for your kernel!
Sent from my Fender using XDA Premium App
overclocking stability is less about the kernel and more about your particular hardware. Some phones just by manufacturing luck can achieve faster clocks than stock to varying degrees. 710 is considered to be the average max i believe. Anything faster is in the far minority of units. People who hack the cpufreq table to get these higher clocks limit to what they consider safe to stop people from actually destroying their hardware (which is possible).
Though, these "oc kernels" should have their patches posted somewhere. It's difficult to track down where exactly these kernel zips are coming from and thus to find out what their source is. Legally they need to either be shipped with the source or shipped with files pointing to the source or have the source available from the same place the binary was downloaded from. thus far I'm just guessing as to what the actual source is to the kernel i'm currently using and hoping all the necessary changes and patches are committed to the github that I believe the kernel is ultimately based from.
cellsafemode said:
I'm trying to get a functional config for the 1.2 mytouch but I'm having trouble tracking down the exact source to the MT3G-Fender-1.2-2.6.35.12-10M-test4.zip kernel but it's proving rather tricky. I can't seem to determine what the source to this kernel is and where to pull it.
If anyone can point me in the correct direction i can start on some work.
Click to expand...
Click to collapse
Hi I built this kernel.. later versions have a SOURCES file with the url's to the source I used. I added that after I started seeing it posted outside of the rom thread I originally posted it to
This is a build off of Pershoots github source
https://github.com/pershoot/kernel-2635
including Ezterry's 10Meg patch to the 32a mem map (Fender/1.2 is 32a/b hi-bred)
https://github.com/ezterry/kernel-b...9fca2404a4fa24384d11f8422ced65920bf06#L0R1355
and Farmatito's usb drain patches 001 - 022 excluding bfs
http://forum.xda-developers.com/showthread.php?t=1010932
and wlan.ko from Cyanogen's sources
the .config can be obtained using kernel-sources/scripts/extract-ikconfig
or adb pull /proc/config.gz config.gz
and as for Overclocking have a look at Dumfuq's githib
https://github.com/dumfuq/cm-kernel/commit/9f113c9e0acf19f57a35acbb85bd6f5cc2e76bb2
I get reboots at anything over 595
edit: I build these kernels because usb mount does not work with 2.6.34 on Gingerbread roms and more recent Cyanogen kernels had the green tint issue. Since the green tint issue is fixed and I think 2.6.34.8 works better on Froyo I haven't been working with 2.6.35 at all lately
cellsafemode said:
I'm trying to get a functional config for the 1.2 mytouch but I'm having trouble tracking down the exact source to the MT3G-Fender-1.2-2.6.35.12-10M-test4.zip kernel but it's proving rather tricky. I can't seem to determine what the source to this kernel is and where to pull it.
....
I just want to be sure the kernel source i'm starting out with doesn't need extra patches that weren't included in the github pull in order to get it to work on the 1.2.
Click to expand...
Click to collapse
you need to ask the person that build 2.6.35.12 based kernels.. [see ratkings comment]
My github has sources for 2.6.34.7/8 and 2.6.36.4 tags match my public builds (I think they are all tagged if not check the notes with my release of the kernel for the correct commit)
I also had some 2.6.35.9-11 builds from cm-kernel sources (exact commits and patches if needed mentions on the posts with the kernels) but the last one off those was in January.. and besides the january one the builds were 32b/2708+ only since that was the reason to re-build cm. sources with little modification.
I too get issues over 595. Wifi will not work etc. at 595 everything is happy.
I pulled the .config, and you cleared everything up. I was just wondering if those extra patches or anything that made booting to the 1.2 correctly were missing from the standard github kernels that I've found.
I have two jobs so time is very limited but I'm hopeful to boot my own compiled kernel this weekend and then work on modifying the accelerometer driver, specifically the parts that handle determining orientation in order to create a sysfs file that controls orientation locking. Write a 1 to the file and it always reports the same orientation that it's currently in, tricking the entire android system into thinking you are never changing your orientation... write a 0 and it reports the real orientation.. and so on. Then write a little app that can be used as a widget or kept in notification bar so you can easily tap lock the orientation whenever needed. Allowing true landscape and portrait locking on any mytouch 3g.
Uhh yeah I trimmed that way down.. no debugging at all (I like to live dangerously)
later tests were less insane
http://www.mediafire.com/file/eqgv0sbb7t4c57s/config-test7
the only other thing to note is that kernel/mkbootimg.sh was edited to force the base address to 10000000 instead of copying the address of the previous kernel.. thats really why I posted it as for Fender/1.2 only. I didn't want anyone messing that up and blaming me when re-flashing Pershoots kernel didn't correct it
It looks like the 1.2 patch is something that basically changes the 32A so if you patch your kernel source to support 1.2, you break building 32A kernels (you have to then have two trees or continually apply and remove the patch between builds). Is that the case, does the patch make your tree a 1.2 only tree when building for the 32A ?
If so I can edit the patch to introduce a kernel config under the saphire board selection to choose if you want to build for the mytouch 1.2 or 32A or 32B directly. So there is no confusion. Then instead of replacing values in the source like the patch does, wrap them in IFdef macros based on the kernel config options.
Then it should be easy to roll out 3 kernel compiles and do something similar to an auto kernel package and utilize a little logic to determine which to use. A rev board with 2.22 radio == 1.2 (i forget if there is another locale where the radio is different for the 1.2). Others can be chosen based on board rev only.
cellsafemode said:
It looks like the 1.2 patch is something that basically changes the 32A so if you patch your kernel source to support 1.2, you break building 32A kernels (you have to then have two trees or continually apply and remove the patch between builds). Is that the case, does the patch make your tree a 1.2 only tree when building for the 32A ?
If so I can edit the patch to introduce a kernel config under the saphire board selection to choose if you want to build for the mytouch 1.2 or 32A or 32B directly. So there is no confusion. Then instead of replacing values in the source like the patch does, wrap them in IFdef macros based on the kernel config options.
Then it should be easy to roll out 3 kernel compiles and do something similar to an auto kernel package and utilize a little logic to determine which to use. A rev board with 2.22 radio == 1.2 (i forget if there is another locale where the radio is different for the 1.2). Others can be chosen based on board rev only.
Click to expand...
Click to collapse
Um... all my kernels to my knowledge work on 32a old radio, 1.2/32b old radio and 2708+ 32b new radios..
Just 3 config files and #ifs for the changes.. ebi1=3.22 radio, ebi0=2.22 radio, and 2708+ = 32b with 2.22.27.08+ radios. (And thus 3 binaries in the auto kernels)
Note the ebi1/ebi0 have both 32a and 32b versions that is what you see with the smi size logic in the kernel
ok. I read the description of the 10M patch above wrong and thought it was also enabling 1.2 support ...
Also, I'm wondering why exactly we use an initrd/initramfs setup. Our rootfs drivers are all compiled in so what's the real reason we bother with initrd ? Seems like we could speed up loading time if we avoid having to decompress and use an initramfs image and just get right into mounting root
OK, sweet. I have 2.6.36.4-s2 working 100% on my mytouch 1.2. Now i can move forward with some actual development.
cellsafemode said:
Also, I'm wondering why exactly we use an initrd/initramfs setup. Our rootfs drivers are all compiled in so what's the real reason we bother with initrd ? Seems like we could speed up loading time if we avoid having to decompress and use an initramfs image and just get right into mounting root
Click to expand...
Click to collapse
i might be wrong but i think android mounts the partitions directly to places in the initrd. never does a switch root out of it like most linux distros.
but im a noob and might be wrong lol
tvall said:
i might be wrong but i think android mounts the partitions directly to places in the initrd. never does a switch root out of it like most linux distros.
but im a noob and might be wrong lol
Click to expand...
Click to collapse
The normal configuration is:
/ = ramdisk and contains init and adbd on the rom (and all of recovery)
/system = system partition
/cache = cache partition
/data = is userdata partition or internal MMC card depending on the device's design
/data/data = userdata if the device has an internal MMC card
** dream/sapphire only has /data on the MTD partition .. no internal MMC card.. just the external one (sd-card)
Can it be changed .. well that is more of a rom design than a kernel question.. just set the bootimage's command line to match if needed... but the above is aosp's expectation.
OK,
2.6.36.4-s2 ezterry kernel for mytouch 1.2
http://signal-lost.homeip.net/files/2.6.36.4-s2-cellsafe.zip.torrent
Source code at
http://signal-lost.homeip.net/files/ezterry_2.6.36.4-s2.torrent
Seed if you download. tTorrent app is a full torrent app for your phone. Or you can just load it on your computer (ideal) and then move it over usb while in recovery.
This is basically rattking's kernel install package with some minor asthetic edits to the install script and layout. The kernel is based off an older rattking .config with necessary changes to match configuration changes in the newer kernel as well as changes to certain schedulers and included drivers and features.
edit:
If you have trouble connecting to the torrent, make sure encryption is on.
IF you still have problems.. the direct link is http://signal-lost.homeip.net/files/2.6.36.4-s2-cellsafe.zip But it would be nice if the torrent was used.
edit2:
Some info about the latest kernel for those who haven't checked it out...
the 10M patch is already applied in the upstream source, so you'll have that. I also turned on all the unsafe frequencies, but default you move around between 122 and 595. You can override that however with user apps.
NOTE: Swap is not enabled with this kernel. .. that's about all the important stuff for now. I just wanted to get a good stable starting point before i start diving in and breaking stuff.
New version with some bugfixes.
I forgot to add in scsi support so the mass storage feature can function... some other minor changes too.
http://signal-lost.homeip.net/files/2.6.36.4-s2-cellsafe2.zip.torrent
7 hours of constant audio playback with the regular music player, on and off texting and web browsing over 3g (3g enabled entire time) and still got 50% power. I gotta compare to other kernels but that sounds pretty decent considering by now i'd be plugging the phone in.
my next half day off when i'm not 2 jobbing it i'll patch up the sensors so that I can enable and disable updating the orientation sensor via sysfs. Should be trivial then to have real orientation locking that's application independent. Should be sweet !
Is your kernel mainly for gingerbread, or froyo? If I understand right, ezTerry's 2.6.36.4 kernels are for gingerbread...
I've only tested it against gingeryoshi so I would say gingerbread or newer