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.
Related
if you want a certain script added, chances are some1 else does too. if you have an idea, or find a script you want added, please either post or PM me. i take a look at this thread alot throughout the day, so i will be able to see your ideas quickly. YOUR IDEAS ARE IMPORTANT
first of all, i did not write this script, i took it from the thread HTC Hero Speedup v2.0 (http://forum.xda-developers.com/showthread.php?t=521421), which was put together by tehseano, who i must thank, however, it seems to only work for Haykuro's Hero ROM
THIS SCRIPT is made to speedup the HTC HERO rom on the g1's. my speedup script is made to work under JACman's. if tried on someone elses, you could brick your phone (although i doubt it), and i will not take responcibility for bricks
trying to use it under JACman 1.72, i couldn't get tehseano's script to work, so im going through a bunch of tweaking and editing for it to work under JACman roms (im guessing twistedumbrella's too).
currently, i'm about to release version 0.2. - released
i have fixed most of the directories and codes except for Battery fix, i have gotten the HTC camera to work, read the readme file
out of curiosity, does any1 have any preference on where i upload the files? want someplace easy and fast, so no rapidshare or anything like that. first working suggestion gets it
please do not use option #8 once it is up, it is not done yet
everything else should be good. this is made STRICTLY for JACman roms, not haykuro's, but twistedumbrella's should work, since it is based off of JACmans
____________________________________________________________________________________________
version 0.2 - http://www.4shared.com/file/113524687/c98398cd/AJZ_HeroSpeed_02.html
very minor changes
fixed the scripts
working on a battery fix
version 1.0 will be more compatible with JAChero 1.8, i expect to release that in the next few day, but this might not be possible because i'm going on vacation
_____________________________________________________________________
I ACCIDENTLY UPLOADED THE BAT AS A TXT FILE. im not gunna change it, so until the next release, just rename the file as a bat
0.1.5: http://www.4shared.com/file/113343120/6c89dd65/AJZ_HeroSpeed_015.html
i must thank dpgc213 for creating the original lockscreen change bat file
Changes:
deleted option to delete pc sync, causes bootloops and doesnt exist
added possibility to change the screen lock image (although doesnt have to do with speed)
added quick directions for changing the lock screen image
____________________________________________________________________________________________
version 0.1 - http://rapidshare.com/files/247165073/hero_speedup_2.0_AJZ_0.1.zip
here's a mirror of 0.1 http://www.4shared.com/file/113320662/7e513586/hero_speedup_20_AJZ_01.html
in version 0.2, expect to see support for the deletion of htc sync, and support for changing your lock screen
can you please include instructions for mac users? thanks good work
did you get it to work with JACman 1.72, you said you would try to tweak it, but did not say if you were successful?
I dont know how to apply the script cuz its made for windows, If some1 put instructions plz?
Franklees said:
did you get it to work with JACman 1.72, you said you would try to tweak it, but did not say if you were successful?
Click to expand...
Click to collapse
i got all the commands and everything working in 1.72 except for #2 to work. #2 will cause a boot loop.
#2 just deletes your htc sync, which idk what it does anyways.
in 0.2, i will try to fix this, as well as add support to change your lock screen
i got the change lockscreen part in, now just gatta see the problem with htc sync
juangil said:
I dont know how to apply the script cuz its made for windows, If some1 put instructions plz?
Click to expand...
Click to collapse
u could try renaming it to something that will work in leopard (er tiger). idk if that would work, im not a mac user. ubuntu and windows
alexjzim said:
u could try renaming it to something that will work in leopard (er tiger). idk if that would work, im not a mac user. ubuntu and windows
Click to expand...
Click to collapse
so if put the optimize.sh file in my sd how do I run it? or is the .bat file the ones that needs to be run? thx
juangil said:
I dont know how to apply the script cuz its made for windows, If some1 put instructions plz?
Click to expand...
Click to collapse
it cant be used for mac users, but basically a bat file just has a bunch of adb commands in it. i can post them for you if you like.
wwwhershcom said:
it cant be used for mac users, but basically a bat file just has a bunch of adb commands in it. i can post them for you if you like.
Click to expand...
Click to collapse
great! that will do it, I appreciate your help
anyone know if HTC pc sync is included in 1.72? if it is, anyone know where it is? once i find this out i can release 0.2.
Wow, this script really made a difference
Henchman said:
Wow, this script really made a difference
Click to expand...
Click to collapse
was aiming for that
juangil said:
can you please include instructions for mac users? thanks good work
Click to expand...
Click to collapse
...Buy a PC lol.
alexjzim said:
was aiming for that
Click to expand...
Click to collapse
When I ran option 3, 6 and 5 in that order without a reboot and then reboot after I did all those I got a bootloop, when I did #5 it was saying success on each one. If I installed dextop-wrapper awhile back like weeks ago do I have to install it again because I didn't install it. I figured I still had it.
jigdagod said:
When I ran option 3, 6 and 5 in that order without a reboot and then reboot after I did all those I got a bootloop, when I did #5 it was saying success on each one. If I installed dextop-wrapper awhile back like weeks ago do I have to install it again because I didn't install it. I figured I still had it.
Click to expand...
Click to collapse
my only suggestion is to wipe and reinstall your ROM, then do everything in order. i cant tell you exactly, because i cant actually see your phone
Okay, thanks I'll try that tomorrow when I get home.
Does this support 1.72 yet?
71CH said:
Does this support 1.72 yet?
Click to expand...
Click to collapse
first of all, i did not write this script, i took it from the thread HTC Hero Speedup v2.0 (http://forum.xda-developers.com/showthread.php?t=521421), which was put together by tehseano, who i must thank, however, it seems to only work for Haykuro's Hero ROM
THIS SCRIPT is made to speedup the HTC HERO rom on the g1's. my speedup script is made to work under JACman's. if tried on someone elses, you could brick your phone (although i doubt it), and i will not take responcibility for bricks
trying to use it under JACman 1.72, i couldn't get tehseano's script to work, so im going through a bunch of tweaking and editing for it to work under JACman roms (im guessing twistedumbrella's too).
currently, i'm about to release version 0.1. - released
i have fixed most of the directories and codes except for uninstalling HTC sync, and replacing the sapphire camera with the official HTC camera. i have gotten the HTC camera to work before, and just need to add in the right codes
out of curiosity, does any1 have any preference on where i upload the files? want someplace easy and fast, so no rapidshare or anything like that. first working suggestion gets it
please do not use option #2 once it is up, it will cause your phone to boot loop - option #2 is now used to change the lockscreen and is completely usable now
everything else should be good. this is made STRICTLY for JACman roms, not haykuro's, but twistedumbrella's should work, since it is based off of JACmans
PC sync is out of all JAChero builds... i spent hours trying to fix something not there . because of this, the next release will be 0.1.5 instead of 0.2
I ACCIDENTLY UPLOADED THE BAT AS A TXT FILE. im not gunna change it, so until the next release, just rename the file as a bat
0.1.5: http://www.4shared.com/file/11334312...Speed_015.html
i must thank dpgc213 for creating the original lockscreen change bat file
Changes:
deleted option to delete pc sync, causes bootloops and doesnt exist
added possibility to change the screen lock image (although doesnt have to do with speed)
added quick directions for changing the lock screen image
__________________________________________________ __________________________________________
71CH said:
Does this support 1.72 yet?
Click to expand...
Click to collapse
Yes.
That's what I'm using ti with. And it's made Rosie completely usable for the first time for me.
Has anyone had the experience where Rosie was really fast when first optimizing using whatever procedure but then lags down over time? That was what I experienced when using a different optimizer. Hopefully this one is consistent.
Hi guys,
Over at the HTC Hero forum I have been developing a kitchen to help ordinary people learn how to build their own ROM. It allows you to do basic things such as rooting a shipped ROM, adding apps2sd, modifying the task killer memory threshold, etc.
The appropriate settings are now in place to make it work for the Dream.
Here is the link to the kitchen:
http://forum.xda-developers.com/showthread.php?t=633246
Before you flash your new custom ROM made from this kitchen, please make a Nandroid backup first of your existing ROM!
Thank you, and enjoy!
Working so far on Ubuntu, figures I just learned how to use git and make my own EBI1 kernels 2 days ago, thanks for this. I'll let you know once I flash a rom how it goes.
carz12 said:
Working so far on Ubuntu, figures I just learned how to use git and make my own EBI1 kernels 2 days ago, thanks for this. I'll let you know once I flash a rom how it goes.
Click to expand...
Click to collapse
Cool, thanks. I am most concerned about how the wireless tethering option will work on the Dream because it requires a kernel fix for Android 1.5 and 1.6. The kitchen is supposed to do that automatically but it will replace your existing kernel.
BTW looks like you are from my home town of Edmonton!
It's not booting, I used my own nan sys and boot img's, set up a working directory and then rebuilt, long time at rogers screen and then boot animation for a minute then a blank back-lit screen, I'll logcat and post it later, time for work.
Is this compatible with the EBI1 dream?
dsixda said:
Cool, thanks. I am most concerned about how the wireless tethering option will work on the Dream because it requires a kernel fix for Android 1.5 and 1.6. The kitchen is supposed to do that automatically but it will replace your existing kernel.
BTW looks like you are from my home town of Edmonton!
Click to expand...
Click to collapse
I may need to go to EBI0 to test if it replaces the kernel?
carz12 said:
It's not booting, I used my own nan sys and boot img's, set up a working directory and then rebuilt, long time at rogers screen and then boot animation for a minute then a blank back-lit screen, I'll logcat and post it later, time for work.
Is this compatible with the EBI1 dream?
Click to expand...
Click to collapse
What is different about EBI1 from a kernel level? If all you did was extract the system and boot.img, and then build without modifying anything, then that should work.
EDIT: If this is a customized ROM (e.g. with custom kernel) then the update-script file under META-INF\.... may need some manual tweaking. The Option 1 in the menu is recommended only for stock ROMs, because this option creates a simple generic update-script file.
If you are indeed using a custom ROM then I'd try to get the original update.zip file of this ROM, which already has the correct update-script file. Just copy that update-script into your existing kitchen.
Or even simpler, just use the original update.zip file and run Option 11 instead of the Nandroid backup.
carz12 said:
I may need to go to EBI0 to test if it replaces the kernel?
Click to expand...
Click to collapse
I am not familiar with all the different Dreams, but it will replace the kernel if you have a 1.5 or 1.6 ROM.
It works on my rogers dream, I took the original rom for the g1, set up a working directory, replaced the launcher, took out a few apps, replaced the boot.img and wlan.ko with the ebi1 compatible versions I compiled and put in my own prop files, booted right up, thanks for this. Can't test the tethering thing as it'll change the kernel on me.
dsixda said:
I am not familiar with all the different Dreams, but it will replace the kernel if you have a 1.5 or 1.6 ROM.
Click to expand...
Click to collapse
What would happen if I just replaced the wlan.ko and boot.img-kernel in the dream_1_6_update folder with my ebi1 versions? could I test out the add wireless tether option?
carz12 said:
What would happen if I just replaced the wlan.ko and boot.img-kernel in the dream_1_6_update folder with my ebi1 versions? could I test out the add wireless tether option?
Click to expand...
Click to collapse
I'll try this tomorrow. Looks cool.
downloading now, ill let you know how things go tomorrow.
carz12 said:
What would happen if I just replaced the wlan.ko and boot.img-kernel in the dream_1_6_update folder with my ebi1 versions? could I test out the add wireless tether option?
Click to expand...
Click to collapse
I'm not sure exactly what the modified boot.img-kernel in the kitchen has, but I'm guessing it's a couple of networking-related variables that were changed. If your kernel has those modifications then maybe it will work. Doesn't hurt to try
Let me know if it works, then we can use your version for individuals who are cooking Rogers ROMs.
A question: Is it possible to tell that a ROM is for a Rogers Dream (ie. somewhere in the build.prop)? In that way, the script can automatically decide what action to take.
carz12 said:
It works on my rogers dream, I took the original rom for the g1, set up a working directory, replaced the launcher, took out a few apps, replaced the boot.img and wlan.ko with the ebi1 compatible versions I compiled and put in my own prop files, booted right up, thanks for this. Can't test the tethering thing as it'll change the kernel on me.
Click to expand...
Click to collapse
That's great news so far! Thank you
will ROMs created work with MyTouch 3G
nicknowsky said:
will ROMs created work with MyTouch 3G
Click to expand...
Click to collapse
Lets hope I am setting this up now to try it for my touch 3g
nicknowsky said:
will ROMs created work with MyTouch 3G
Click to expand...
Click to collapse
Since it's the HTC Magic, yes it should! Please try and let me know.
I'll create a thread for this in the Magic forum so that people can post their feedback there. Thank you
EDIT: Here's the thread where you can post Magic/myTouch 3G feedback:
http://forum.xda-developers.com/showthread.php?t=651470
Question...What section on the HTC site would I look for the shipped rom.exe...Specific device = Mytouch?
holmes901 said:
Question...What section on the HTC site would I look for the shipped rom.exe...Specific device = Mytouch?
Click to expand...
Click to collapse
Just do a search in XDA for Mytouch/Magic shipped ROMs. Usually there are links to the original ROMs in the Wiki page for your device.
dsixda said:
I'm not sure exactly what the modified boot.img-kernel in the kitchen has, but I'm guessing it's a couple of networking-related variables that were changed. If your kernel has those modifications then maybe it will work. Doesn't hurt to try
Let me know if it works, then we can use your version for individuals who are cooking Rogers ROMs.
A question: Is it possible to tell that a ROM is for a Rogers Dream (ie. somewhere in the build.prop)? In that way, the script can automatically decide what action to take.
Click to expand...
Click to collapse
I'll try it out tonight, the sources I used to compile were wes's and his kernel has tethering support unless I broke it, I've never used tethering before.
carz12 said:
I'll try it out tonight, the sources I used to compile were wes's and his kernel has tethering support unless I broke it, I've never used tethering before.
Click to expand...
Click to collapse
Tethering is actually useful even if you don't need it all the time, eg. if your desktop PC cannot access the internet or your wife is using an iPod touch to access the internet in a restaurant.
So do Rogers Dreams require a special kernel, due to the 911 fix? So I guess the stock ROM update has the proper kernel, but modifications like the wireless tether for a Rogers Dream would require a patched Rogers kernel.
Hey all, this is a patch that will change out the kernel for King's SenseHybrid 2.3. I use this rom pretty much daily. It is a cupcake based hero, just this update speeds up the performance a bit.
Instructions:
-Wipe everything!
-Install King's 2.3 SenseHybrid (Please follow his directions.)
http://forum.xda-developers.com/showthread.php?t=563294&highlight=SenseHybrid
- Flash this update immediately after flashing King's rom
- Reboot and enjoy!
ChangeLog:
Updates user.conf (if you don't like it, change it )
Virtual mem settings adjusted
proc_cpu_en=0 # to save battery life
Updates Kernel to CM 4.2.15.1
Removes:
Meebo
HeroLED
AKNotepad
teeter
Adds:
Free Advanced Task Manager (Useful)
****I just posted a 10MB ram hack version in the thread below. It uses CM 4.2.14.1 with CFS instead.****
If you like it, then great! I've been experimenting with using different kernels on different people's roms. I'm new to it, but if anyone has any tips, they are greatly appreciated.
Red.
PS. PLEASE DO NOT ASK ABOUT BT! IF YOU HAVE READ ANYTHING ON THIS SITE CONCERNING HERO ROMS ON A G1/DREAM THEN YOU WOULD KNOW BETTER AND WOULDN'T RISK BEING FLAMED.
Sounds good I was going to flash the sensehybrid soon anyways so this sounds perfect.
Wait a few minutes..
If you can hold off a bit, I am also making a 10MB ram hack version with CM 4.2.14.1 CFS. Just testing now.
Red.
CM 4.2.14.1 10MB Ram Hack with CFS
Here is another one that you can flash immediately after flashing king's 2.3. This uses the 4.2.14.1 CM kernel and the CFS 10MB ram hack. I absolutely hate BFS on G1/Dreams! Anyways, this one should run faster. I would also look into the thread that has been posted recently about speeding up hero roms and change the line in your init.rc to keep rosie in memory. just copy the init.rc onto your sdcard and edit it with notepad++ (windows program, it is great!) and then copy it back to your root over the existing init.rc and reboot. (if this is complicated, then don't try it.)
Otherwise, Enjoy!!
will this work without an ext/swap partition?
Without ext partition...
Honestly, if you are using the Death SPL and you are running this with my ram hack, you should be ok. Unfortunately, the compcache on King's earlier roms are usually broken. I tried pushing ramzswap from the CM kernel and still no luck, but then again, I'm not as savy as some of the other dev's out there. You will just have to edit the user.conf after you finish flashing the two, you want to do the following:
First, before flashing you want to pull the user.conf from the system/bin/ directory in king's zip file. edit the user.conf using notepad++ in windows and change the linuxswap=1 to 0 so that it turns it off. then copy that file to your sdcard.
immediately after flashing the two files,
-go to console from the recovery and type the following
mv /sdcard/user.conf /system/bin/
reboot
this will disable the linuxswap and then you will be able to run the rom. But again it would be better with a swap partition.
Hope this helps.
Red.
would prefer the WG kernel but okay thanks
protomanez said:
would prefer the WG kernel but okay thanks
Click to expand...
Click to collapse
Same here, WG is great. I tried the RH CFS patch, but I got an error while flashing it. Had to restore from switchrom.
where's the wg-kernel patch for 1.5 hero roms?
Also, does multitouch still work with THIS patch?
boot loop...
?
Chabsie, telling me u got a boot loop doesn't help me resolve the problem much. You must have DeathSPL for this rom, Must be full wipe, and EXT4 partition. If that doesn't help, please list the stats for your phone, which hack u are using and where your issue occurs.
Jcarrz, WG kernel version of this is released in another thread. It is on 2nd or third page, just search.
Thanks.
Red.
Just a question, since im not an expert. but how is this cupcake based hero, when CM 4.2.15.1 is donut based? Also thanks i will give it a try now.
Snacky-cakes
domex2k said:
Just a question, since im not an expert. but how is this cupcake based hero, when CM 4.2.15.1 is donut based? Also thanks i will give it a try now.
Click to expand...
Click to collapse
HTC developed the sense UI and this port is from the HTC Hero or the earlier Droid Eris (Prior to upcoming update from Verizon to 2.1.) Both of those phones use Cupcake as the base and then Sense UI is just a pretty cover for it. The kernel I used is from CM's Donut based roms, which is more than compatable, but again, the framework and ramdisk and everything else reflects a 1.5 environment. Enjoy the patch.
Red.
redd12345 said:
HTC developed the sense UI and this port is from the HTC Hero or the earlier Droid Eris (Prior to upcoming update from Verizon to 2.1.) Both of those phones use Cupcake as the base and then Sense UI is just a pretty cover for it. The kernel I used is from CM's Donut based roms, which is more than compatable, but again, the framework and ramdisk and everything else reflects a 1.5 environment. Enjoy the patch.
Red.
Click to expand...
Click to collapse
Got it. Thanks
Yeah it runs pretty smooth, the only thing was the contacts from Gmail did not sync, but im going to later on reflash and see what happens.
sync fix
domex2k said:
Got it. Thanks
Yeah it runs pretty smooth, the only thing was the contacts from Gmail did not sync, but im going to later on reflash and see what happens.
Click to expand...
Click to collapse
Just go back into system menu and re-sync manually and give it a minute. It will work fine. I had that happen on one of the trials.
Red.
redd12345 said:
Just go back into system menu and re-sync manually and give it a minute. It will work fine. I had that happen on one of the trials.
Red.
Click to expand...
Click to collapse
Great i will give that i try Thank you
Suggestion
domex2k said:
Great i will give that i try Thank you
Click to expand...
Click to collapse
You may like this one better.
http://forum.xda-developers.com/showthread.php?t=654789
This is the Wes Garner Ramhack. It should be slightly faster. I think that you still need to have a partition though because of the apps to sd. You would have to do complete wipe for this one again.
Red.
redd12345 said:
You may like this one better.
http://forum.xda-developers.com/showthread.php?t=654789
This is the Wes Garner Ramhack. It should be slightly faster. I think that you still need to have a partition though because of the apps to sd. You would have to do complete wipe for this one again.
Red.
Click to expand...
Click to collapse
Thanks for the link. I will give it a try, because some reason when used the other 2 cm patches the camera and camcorder will FC and so i then just flashed this rom solo and it did not fc
multitouch?
redd12345 said:
Chabsie, telling me u got a boot loop doesn't help me resolve the problem much. You must have DeathSPL for this rom, Must be full wipe, and EXT4 partition. If that doesn't help, please list the stats for your phone, which hack u are using and where your issue occurs.
Jcarrz, WG kernel version of this is released in another thread. It is on 2nd or third page, just search.
Thanks.
Red.
Click to expand...
Click to collapse
Sorry for being vague. I had everything right except ext3 instead of ext4. I'm looking for some directions on how to upgrade. If you have any please let me know, thanks.
Hey all, there were requests for Wes' Kernel and the 10MB ramhack, so I thought I would try to entertain them. This will change out king's kernel in SenseHybrid 2.3 for Wes' 10MB RamHack kernel. This will also run 32MB of compcache on boot up, Swap partition is still required for A2SD. If you want to run a swap partition, I recommend EXT4 and to use Notepad++ (windows program for editing linux files) to change your /system/bin/user.conf
Now the fun part.
Instructions:
-Wipe everything! (This ONLY works from a fresh install!!!)
-Install King's 2.3 SenseHybrid (Please follow his directions.)
http://forum.xda-developers.com/showthread.php?t=563294
- Flash this update immediately after flashing King's rom (Do NOT reboot before you flash this patch!)
- Reboot and enjoy!
NOTE: PLEASE GIVE THIS SOME TIME TO BOOT AND TO SYNC. ALSO, DO NOT START SWIPING RIGHT AWAY AS THE PROGRAMS TAKE TIME TO LOAD. JUST LET IT SIT FOR A BIT AND BE PATIENT... Then it's pretty quick.
ChangeLog:
Updates user.conf (if you don't like it, change it )
Virtual mem settings adjusted
proc_cpu_en=0 # to save battery life
Updates Kernel to WG RamHack from latest Donut rom
Removes LinuxSwap in exchange for 32MB Compcache
Removes:
Meebo
HeroLED
AKNotepad
teeter
Adds:
Free Advanced Task Manager (Useful)
If you like it, then great! I've been experimenting with using different kernels on different people's roms. I'm new to it, but if anyone has any tips, they are greatly appreciated.
Red. (Testing out FireRat's 30MB ideas next... I just don't have a PHD in "Freakin' Awesome," so it's gonna take some time.)
PS. PLEASE DO NOT ASK ABOUT BT! IF YOU HAVE READ ANYTHING ON THIS SITE CONCERNING HERO ROMS ON A G1/DREAM THEN YOU WOULD KNOW BETTER AND WOULDN'T RISK BEING FLAMED.
Saved for any updates.
Reserving space.
The link to the SenseHybrid thread doesn't work.
Also, you should try to work on hero 2.1 (new - DroidEris Legend ect) instead of hero 1.5 (old).
Correct Link
http://forum.xda-developers.com/showthread.php?t=563294&highlight=Sense
G1ForFun said:
The link to the SenseHybrid thread doesn't work.
Also, you should try to work on hero 2.1 (new - DroidEris Legend ect) instead of hero 1.5 (old).
Correct Link
http://forum.xda-developers.com/showthread.php?t=563294&highlight=Sense
Click to expand...
Click to collapse
Didn't vega make a WG kernel already though for eris/legend?
Thanks.
G1ForFun said:
The link to the SenseHybrid thread doesn't work.
Also, you should try to work on hero 2.1 (new - DroidEris Legend ect) instead of hero 1.5 (old).
Correct Link
http://forum.xda-developers.com/showthread.php?t=563294&highlight=Sense
Click to expand...
Click to collapse
I updated the link in the initial post. Thank you. Other than that, I think there are plenty of good Dev's that are working on the 2.1 field. I am really new to this and do not have anywhere near the experience that they do. This was a request from another post that I had earlier. I like the 1.5 hero because of the almost full functionality (minus BT.) 2.1 is a great platform, but until the drivers are released, it is frustrating. I was beside myself when they were reverse engineered for the Camera app to be enabled. People here work really hard on these roms. In any event, I hope people will make use of this.
Red.
redd12345 said:
I updated the link in the initial post. Thank you. Other than that, I think there are plenty of good Dev's that are working on the 2.1 field. I am really new to this and do not have anywhere near the experience that they do. This was a request from another post that I had earlier. I like the 1.5 hero because of the almost full functionality (minus BT.) 2.1 is a great platform, but until the drivers are released, it is frustrating. I was beside myself when they were reverse engineered for the Camera app to be enabled. People here work really hard on these roms. In any event, I hope people will make use of this.
Red.
Click to expand...
Click to collapse
Well props to you on your work, I know people still use 1.5 sense I was just making a suggestion.
Lol.
G1ForFun said:
Well props to you on your work, I know people still use 1.5 sense I was just making a suggestion.
Click to expand...
Click to collapse
I'll get there someday. Everyone might be on a different phone by then, but I'll be in the game for a while. Thanks again!
Red.
I just flash_image'd the boot.img on my installation... What are the differences in doing that over flashing the entire zip?
xjjjay said:
I just flash_image'd the boot.img on my installation... What are the differences in doing that over flashing the entire zip?
Click to expand...
Click to collapse
Wifi, Adv. Task manager, swap, compcache, and their modified user.conf so not much
JAguirre1231 said:
Wifi, Adv. Task manager, swap, compcache, and their modified user.conf so not much
Click to expand...
Click to collapse
crap didn't notice wifi was broken -_-
Too lazy to sift through all the other changes this patch makes in order to get wg kernel... 2.3 is fast enough
Now that im using this kernel, when ppl call me their name/picture doesnt show up... its as if i dont have their number, when i really do. it even asks me if i want to store their number after the call... so for whatever reason it isnt recognizing my contacts when they call. it does recognize them when i get a text.
Issue?
chabsie said:
Now that im using this kernel, when ppl call me their name/picture doesnt show up... its as if i dont have their number, when i really do. it even asks me if i want to store their number after the call... so for whatever reason it isnt recognizing my contacts when they call. it does recognize them when i get a text.
Click to expand...
Click to collapse
I didn't have this issue when I ran trials, but I will try to reload. Are you using EXT4 partition? You may also want to try to re-sync your information in Settings/Data Syncronization. Also, I just want to make sure that you installed this patch from a fresh wipe and didn't flash it over the other patches that I made (I noticed you tried the CM ones as well.)
Let me know if either of these work or help.
Red.
yes im using ext4 and yes i flashed it over a fresh wipe. when i make a call, the contact is recognized as it should, its just incoming calls that dont work.
i just resynced contacts and that didnt make a difference for me.
side question: ive seen it mentioned in other threads that you should wipe davlik cache, battery stats, and rotate settings in addition to the factory reset wipe and repartitioning. how do you wipe those first 3?
chabsie said:
yes im using ext4 and yes i flashed it over a fresh wipe. when i make a call, the contact is recognized as it should, its just incoming calls that dont work.
i just resynced contacts and that didnt make a difference for me.
side question: ive seen it mentioned in other threads that you should wipe davlik cache, battery stats, and rotate settings in addition to the factory reset wipe and repartitioning. how do you wipe those first 3?
Click to expand...
Click to collapse
If you download Amon_ra's recovery and flash it, when you are in recovery mode, there will be an option under wipe. Still looking into camera issue.
Red.
I have problem with cam after flashing kernel.
Am i the only one whit this?
feenty said:
I have problem with cam after flashing kernel.
Am i the only one whit this?
Click to expand...
Click to collapse
No, you are not the only one with this issue. I flashed it two times after wipe. But the camera still broken.
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