Downloads here: http://www.neopeek.com/viewtopic.php?f=14&t=6507
Pretty much as stock as you can get it, if you want to create your own line of roms based off this.. Doesn't seem like that google supports these old roms anymore for the sake of server space (the sources seem to be deleted)
e334 said:
-Wipe everything (except dalvik-cache), data, rotate-settings, cache, and battery-stats! Wipe is very important! Superwipe V1 & V2 is fine to use.
Click to expand...
Click to collapse
since dalvik-cache is stored on /data , how do you go about not wiping dalvik-cache but still wiping data ?
wiping data will wipe
dalvik-cache
rotate-settings
battery-stats
since they are all stored on data
See: http://forum.xda-developers.com/showthread.php?t=637419
I understand what you mean, but the recovery "wipe dalvik-cache" function wipes more than it needs to (the dex files), and causes the rom to crash. This often occurs on 1.6 roms, but not in 2.1+.
can it be run on 2708? just no 3d?
For use with 2708 RADIO
See this post: http://forum.xda-developers.com/show...3&postcount=43
the link can not be opened
yes, it can run 2708, just flash kernel after install and it will work.
Link here: http://droidbasement.com/db-blog/?p=1563
e334 said:
See: http://forum.xda-developers.com/showthread.php?t=637419
I understand what you mean, but the recovery "wipe dalvik-cache" function wipes more than it needs to (the dex files), and causes the rom to crash. This often occurs on 1.6 roms, but not in 2.1+.
Click to expand...
Click to collapse
ahh I see
it is not a problem at install time, and is only a problem if lame symlink hacks have been used to redirect the dalvik-cache from cache to some other place, instead of using the dex to data only prop
you don't link any of your source as per http://forum.xda-developers.com/showthread.php?t=755506
well, dex never goes to /cache, so symlink hacks are not required, so wiping dalvik-cache with RA will not be an issue
problem doesn't exist
e334 said:
3D and/or camera WILL NOT WORK WITH 10 MB RAM HACK KERNELS!!!
Click to expand...
Click to collapse
Why is hw3d broken I know not.. least if you use a 2708 kernel.. you can use the original 10mb hack on the 2708 kernel with broken 3d but working camera but that seems silly.
You can go back to my 2708+ kernel thread and look up the old builds kernel.. in theory hw3d+camera will work unless you are having other issues with newer kernels and hw3d on the older rom.
FYI the old builds kernel has an alternative memory map that correctly maps hw3d for 2708, and maps 8mb for camera rather than the 5mb in froyo. (This is needed for the older libcamera's.. if you are re-building from source you may want to see if you can shim in the froyo libcamera)
ezterry said:
Why is hw3d broken I know not.. least if you use a 2708 kernel.. you can use the original 10mb hack on the 2708 kernel with broken 3d but working camera but that seems silly.
You can go back to my 2708+ kernel thread and look up the old builds kernel.. in theory hw3d+camera will work unless you are having other issues with newer kernels and hw3d on the older rom.
FYI the old builds kernel has an alternative memory map that correctly maps hw3d for 2708, and maps 8mb for camera rather than the 5mb in froyo. (This is needed for the older libcamera's.. if you are re-building from source you may want to see if you can shim in the froyo libcamera)
Click to expand...
Click to collapse
I think he is just getting things confused, like with the dalvik-cache wipe thing.
saying that problems exist when they don't
to clarify I'm reffering to this
Bugs so far:
-no 3d with 2708+ kernels because of the 10mb hack
Click to expand...
Click to collapse
unless I missed something and there are 2708 kernels which give extra 21mb ram?
from what I understood your 2708 kernels for older 1.6 builds gains 11mb instead of 14 with 2.2+ ( due to the required cam mem,as explained above )
and the 10 mb ramhack is completely different where memory allocated to the gpu is mapped to system instead, so it makes sense that 3d would not function (the gpu has no memory )
Effdee said:
unless I missed something and there are 2708 kernels which give extra 21mb ram?
Click to expand...
Click to collapse
I've been a bit too lazy to create/release it .. but in theory I could make a build with
15 + 5 + 8 =28mb on top of a regular 1.6 stock kernel by breaking both hw3d and camera
15 = 2708 ram changes (I say 14 elsewhere because newer froyo kernels have another ram hack to regain 1mb on all ebi0 radios/spls..
5 = camera ram
8 = EBI video region (hw3d)
This may need 1.6 but be interesting for the ram.. or those wanting more of just a embeded linux device
ezterry said:
5 = camera ram
Click to expand...
Click to collapse
the camera is interesting, the cam on the g1 is awful anyway so this ram might be put to better use as system ram.
I'm just wondering how much ram the cam would need for barcode (QR) scanning, as I would miss that ability.
might have a poke around myself and see what I find
ezterry said:
I've been a bit too lazy to create/release it .. but in theory I could make a build with
15 + 5 + 8 =28mb on top of a regular 1.6 stock kernel by breaking both hw3d and camera
15 = 2708 ram changes (I say 14 elsewhere because newer froyo kernels have another ram hack to regain 1mb on all ebi0 radios/spls..
5 = camera ram
8 = EBI video region (hw3d)
This may need 1.6 but be interesting for the ram.. or those wanting more of just a embeded linux device
Click to expand...
Click to collapse
omg ive been asking for this for a while now.. but nobody answered... would love to see this get done ) i wish i know how though.. :/
A good think would be 15 + 8 = 23mb with camera working and 3D broken
apps2ext seems to be broken in R1. Update soon.
Effdee said:
ahh I see
it is not a problem at install time, and is only a problem if lame symlink hacks have been used to redirect the dalvik-cache from cache to some other place, instead of using the dex to data only prop
you don't link any of your source as per http://forum.xda-developers.com/showthread.php?t=755506
well, dex never goes to /cache, so symlink hacks are not required, so wiping dalvik-cache with RA will not be an issue
problem doesn't exist
Click to expand...
Click to collapse
Hmm.. I see, although it has proved problematic for me to wipe dalvik-cache via recovery, so let's just leave it at that..
The source is obviously from google, as it is "AOSP" Android Open Source Project, which is from google.
e334 said:
Hmm.. I see, although it has proved problematic for me to wipe dalvik-cache via recovery, so let's just leave it at that..
The source is obviously from google, as it is "AOSP" Android Open Source Project, which is from google.
Click to expand...
Click to collapse
so you made no changes?
guess we are better off using an established 1.6 in the rom bible then
Some people prefer "pure" AOSP.
Sent from my HTC Stallion using XDA App
when it comes to donut it seems most prefer cm4 or superd
Whats great about this is that it gives users more options to choose from when selecting a ROM.
Sent from my HTC Stallion using XDA App
Effdee said:
when it comes to donut it seems most prefer cm4 or superd
Click to expand...
Click to collapse
Its the community's choice, I won't get butt-hurt if no one downloads my rom. I *know* that there are CM4 or SuperD roms out there, and I have tried them all, and they are good and fast, and I'm not ashamed to say that my rom is rather basic/buggy. If you want to continue trolling this thread to make yourself feel better, and make me look like an idiot, you are more than welcome to...
e334 said:
Its the community's choice, I won't get butt-hurt if no one downloads my rom. I *know* that there are CM4 or SuperD roms out there, and I have tried them all, and they are good and fast, and I'm not ashamed to say that my rom is rather basic/buggy. If you want to continue trolling this thread to make yourself feel better, and make me look like an idiot, you are more than welcome to...
Click to expand...
Click to collapse
trolling?
I just pointed out that your advice on not wiping dalvik-cache was contradictory as you said you *must* wipe data which will also wipe dalvik-cache.
I wasn't trying to make you look like an idiot. That would be a waste of time as you are doing that all on your own.
and if I *really* wanted to troll I would sign up to the competing forum you advertise in the op
I note you have asked for the thread to be deleted, which is probably a good idea as you violated the rules regarding source code and gpl
but would be a little unfair as the thread evolved, as a result of more miss information from yourself, into a think tank regards memory in the different kernels.
Related
READ FIRST - I am no longer updating my ROMs - details.
If you're following the Hero scene, you'll know that I have published a custom ROM based on the 1.73.405.5 shipping ROM. I have a Vodafone Magic (32B) and a T-Mobile G1 kicking around (and HTC want my PR review unit Hero back!), so figured it would be cool to firstly build a really simple way for me to package my ROMs for all 3 devices, and secondly try and produce an update.zip that runs on all 3!
Well, the first step is here, I have the MoDaCo Custom ROM ready to install on your Sapphire 32B device (if anyone can point me at a boot.img / kernel that runs this on 32A, i'll include that in the package (I can't test 32A)).
Things you should know...
- Contents are IDENTICAL to the MoDaCo Custom ROM core version detailed here.
- I have used cyanogen's kernel from 4.0.4 (big respect to cyanogen, he's doing awesome work!)
- Now compcache ready - use this script for a big performance boost!
It has room for improvement, and given the serious lack of ROM on the G1, I think optimising is a priority. Hopefully it will also provide a useful base for some other chefs. All that said and done tho, I don't think in it's current state it's unusable!
The download link (in update.zip format for flashing in the usual way via recovery image) is at: http://android.modaco.com/content/h...-09-2-1-modaco-custom-rom-hero-to-dream-port/
I've packaged Cyanogen's 4.1.6 BFS enabled Kernel and wlan.ko as an update.zip too (see above thread) - nandroid backup before applying!
I've quoted some of my original Hero post here, so you know what you're getting. Enjoy!
P
Changelog
2.2
Fixed SU and SD card bugs.
2.1.2
Updated busybox
Now compcache ready - use this script for a big performance boost!
2.1.1
Switch to Cyanogen's kernel
Fixed G-Sensor / Compass
Fixed sound
Unified Dream / Sapphire 32B download
2.1
Initial Release
me said:
This ROM is based on the Generic 2.73.405.5 release version of the 'new update' (together with my own optimisations) for the best possible performance! The ROM is now available in 2 versions - 'core' and 'enhanced' by popular request.
Included in both 'core' and 'enhanced' versions
- Rooted with 'adb remount' permission and superuser APK
- A2SD included (fully automatic - thanks cyanogen!) - create a EXT3 partition as your second partition to use. dalvik-cache remains on device. EXT4 is NOT supported.
- Added Jbed Java
- Added Spare Parts (run it and switch the 2 animation types to 'fast' for an even better experience!)
- Added Custom Locale for setting non english Locales
- Added android-wifi-tether 1.52 (props to the developer, this is a great app!)
- Added WMSM
- Added busybox 1.15 - tweaked such that 'get information' in Swapper now works as desired
- Added nano 2.09 - text editor for use in shell mode
- Added terminfo and settings to boot.img to allow nano etc. use
- Added tun.ko file (untested, please report on whether this is useful)
- Added files required for Debian linux
- Moved Quickoffice to data partition to allow easy uninstall
- Deleted 'Learn More' application
- Deleted Maps application - install from the Android Market to always stay up to date
- ROM now includes touch focus in Camera app
- ROM now supports shortcuts using BetterCut (and therefore I assume anycut!) in Rosie
- Silenced boot sound (it's still there and can be reactivated with a file edit)
- You can now check your MoDaCo Custom ROM (MCR) version from the about menu. It will display MCR2.0 (core) or MCR2.0e (enhanced).
- Fix for HTC Peep on Vodafone now available here!
Click to expand...
Click to collapse
Yes
Fire up the stoves chefs and let the cook-off begin!!! lol
Awesomeness Just out of interest then, is this the same build as in this thread
http://forum.xda-developers.com/showthread.php?t=555624
or newer/older?
Jonno12345 said:
Awesomeness Just out of interest then, is this the same build as in this thread
http://forum.xda-developers.com/showthread.php?t=555624
or newer/older?
Click to expand...
Click to collapse
It is based on a newer build of Hero. So it should technically be better. May need some optimization for the G1 though.
I'm running CM v4.1.4 right now, I can just flash this without any other modification? Would a wipe be advisable?
modaco said:
If you're following the Hero scene, you'll know that I have published a custom ROM based on the 1.73.405.5 shipping ROM. I have a Vodafone Magic (32B) and a T-Mobile G1 kicking around (and HTC want my PR review unit Hero back!), so figured it would be cool to firstly build a really simple way for me to package my ROMs for all 3 devices, and secondly try and produce an update.zip that runs on all 3!
Well, the first step is here, I have the MoDaCo Custom ROM ready to install on your Sapphire 32B device (if anyone can point me at a boot.img / kernel that runs this on 32A, i'll include that in the package (I can't test 32A)).
Things you should know...
- Contents are IDENTICAL to the MoDaCo Custom ROM core version detailed here.
- I have used the awesome 2.6.29 jac kernel (serious respect - these guys are the real heroes (pun intended)!)
- None of the 2.6.29 kernel tricks are used (yet)
- No real optimisation has been done (yet)
So, it has room for improvement, and given the serious lack of ROM on the G1, I think optimising is a priority. Hopefully it will also provide a useful base for some other chefs. All that said and done tho, I don't think in it's current state it's unusable!
The download link (in update.zip format for flashing in the usual way via recovery image) is at: http://android.modaco.com/content/h...-09-2-1-modaco-custom-rom-hero-to-dream-port/
I've quoted some of my original Hero post here, so you know what you're getting. Enjoy!
P
Click to expand...
Click to collapse
thanks!!! 10 chars
B3astofthe3ast said:
I'm running CM v4.1.4 right now, I can just flash this without any other modification? Would a wipe be advisable?
Click to expand...
Click to collapse
just make sure u have the latest Radio and SPL and make a nand backup Just In Case
Anyone else having trouble flashing? Get an error, going to redownload incase it's just a bad download.
Redownloaded, still can't flash, get
Code:
E:failure at line 361:
copy_dir PACKAGE:data DATA:
Installation aborted.
EDIT: Wiped dalvik-cache and it flashed .
Jonno12345 said:
Redownloaded, still can't flash, get
Code:
E:failure at line 361:
copy_dir PACKAGE:data DATA:
Installation aborted.
Click to expand...
Click to collapse
You have to wipe your ext 3 and do a alt+w
Yeeeahhh.
The blaze is about to be set!
Got a question....
Are there any devs out there that can build a ROM from the ground up? Maybe a Hero clone that doesn't require so much space and resource? I've noticed (not being anything close to a dev) that you guys take a ROM developed by some techie at HTC and cook it to bring the rest of us enjoyment and peace with our phones, but does any dev have the know-how to develope a "Hero" ROM designed for the G1?
If this is retarded, just ignore the post and tell me to go brick my G1. Word...
jugg2000 said:
Yeeeahhh.
The blaze is about to be set!
Got a question....
Are there any devs out there that can build a ROM from the ground up? Maybe a Hero clone that doesn't require so much space and resource? I've noticed (not being anything close to a dev) that you guys take a ROM developed by some techie at HTC and cook it to bring the rest of us enjoyment and peace with our phones, but does any dev have the know-how to develope a "Hero" ROM designed for the G1?
If this is retarded, just ignore the post and tell me to go brick my G1. Word...
Click to expand...
Click to collapse
Um first off that would be painstainkinly annoying to do and second if it was possible someone probably would have done it and third these roms are a HERO rom designed for a g1 they were once for hero now there for a g1
r_dub said:
You have to wipe your ext 3 and do a alt+w
Click to expand...
Click to collapse
Ahh okay, didn't wipe my ext 3 Hoped I'd get away with it Will try again.
Jonno12345 said:
Ahh okay, didn't wipe my ext 3 Hoped I'd get away with it Will try again.
Click to expand...
Click to collapse
Yeah for 1.5.1 its an absolute must
jugg2000 said:
Yeeeahhh.
The blaze is about to be set!
Got a question....
Are there any devs out there that can build a ROM from the ground up? Maybe a Hero clone that doesn't require so much space and resource? I've noticed (not being anything close to a dev) that you guys take a ROM developed by some techie at HTC and cook it to bring the rest of us enjoyment and peace with our phones, but does any dev have the know-how to develope a "Hero" ROM designed for the G1?
If this is retarded, just ignore the post and tell me to go brick my G1. Word...
Click to expand...
Click to collapse
if you have the money to pay my bills whilst I quit my day job and can wait several months. Then yes.
It takes TEAMS of people that get paid a **** ton of money MONTHS to develop a ROM from the ground up.
ccyrowski said:
if you have the money to pay my bills whilst I quit my day job and can wait several months. Then yes.
It takes TEAMS of people that get paid a **** ton of money MONTHS to develop a ROM from the ground up.
Click to expand...
Click to collapse
Scratch that. If you have the money to pay every cooker here for several months then yes it could be done.
EDIT: I'm only talking for myself and JAC, but a lot of the stuff JAC or I include in our builds we built from the source at http://android.git.kernel.org/
ccyrowski said:
Scratch that. If you have the money to pay every cooker here for several months then yes it could be done.
Click to expand...
Click to collapse
Not a bad idea we could all pitch in and have all the hero devs work togeather on a fully functional G1 Hero build LOL just kidding
im gonna nandroid backup and flash... will post results
It looks like we have some known issues for me to fix tomorrow... no G-Sensor, Compass or (worringly) sound! biggrin.gif
If any chefs have come across these before and have any hints, let me know! wink.gif
P
hey i have bricked my phone i trieed to update my radio to install this rom after completing it when i rebooted my phone now i onli see a photo of a box and a arrrow cuming out of it indicating to phone i cant even power on my phone cant even go to recovery mode..............please help...
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.
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.
The credits for this rom should ALL go to SebastianFM from his original thread: http://forum.xda-developers.com/showthread.php?t=1025330
He has made numerous changes and compiled modified libs to get this port running...
Features Sense 2.1 and GB 2.3.3...
Code:
Working:
-Wifi
-Bluetooth
-GPS
-GSensor
Code:
Changes Made:
-Modified EZTerry 26364-s3 kernel (Added "turbo" mode for msm7201a, htc usb enable)
-Zram 48mb
-SDEXT for htc dream...
Code:
Requirements:
HTC Magic: "MTD 180 2" (sd-ext not used)
HTC Dream: "MTD 75 2" + 512mb ext4 sd-ext
I will be releasing a stripped version later.. This may be too slow for hTC dream but it runs fine on my htc sapphire. Let me note that the speed is not stellar but it is decent enough for daily usage. To be frank, I would rather use an AOSP/CM rom than this but here it is for you to mess with.
Download:
http://uniteddev.com/wordpress/files/DS_SFM_3.0.2_FULL.zip
FIX UPDATER-SCRIPT ERROR:
http://w261678.open.ge.tt/1/files/798xb0G/0/blob?download
Click to expand...
Click to collapse
Also, I am working on porting SFM's HTC Salsa based kernel from 32A to 32B but I am having trouble getting it to boot. If you are seriously interested in helping, just send me a pm and I will give you the link to the source.. Currently I am using ezterry's 2.6.36.4 aosp based kernel with a few changes I made myself, but it is not completely compatible with our needs as camera does not work and HW acceleration isn't fully working.
e334 said:
The credits for this rom should ALL go to SebastianFM from his original thread: http://forum.xda-developers.com/showthread.php?t=1025330
He has made numerous changes and compiled modified libs to get this port running...
Features Sense 2.1 and GB 2.3.3...
Code:
Working:
-Wifi
-Bluetooth
-GPS
-GSensor
Code:
Changes Made:
-Modified EZTerry 26364-s3 kernel (Added "turbo" mode for msm7201a, htc usb enable)
-Zram 48mb
-SDEXT for htc dream...
Code:
Requirements:
HTC Magic: "MTD 180 2" (sd-ext not used)
HTC Dream: "MTD 75 2" + 512mb ext4 sd-ext
I will be releasing a stripped version later.. This may be too slow for hTC dream but it runs fine on my htc sapphire. Let me note that the speed is not stellar but it is decent enough for daily usage. To be frank, I would rather use an AOSP/CM rom than this but here it is for you to mess with.
Also, I am working on porting SFM's HTC Salsa based kernel from 32A to 32B but I am having trouble getting it to boot. If you are seriously interested in helping, just send me a pm and I will give you the link to the source.. Currently I am using ezterry's 2.6.36.4 aosp based kernel with a few changes I made myself, but it is not completely compatible with our needs as camera does not work and HW acceleration isn't fully working.
Click to expand...
Click to collapse
What would you describe as "decent enough for daily usage"?^^ Because if i would define that, it's like no laggs and stuff and not force closing and beeing stable.
If you want you can take some stuff from my thread design or whatever.
Well it's stable for sure.. No hanging on 32B sapphire.
ill test it on the dream soon
Please keep in mind that I will not be giving any support... You are on your own
i was run rom but slow....
vuvantuan59 said:
i was run rom but slow....
Click to expand...
Click to collapse
It should be quicker on Sapphire than G1/Dream, due to the ROM being stored in internal memory(ROM). On G1, the Rom is stored partially on SD and uses various links. And I think the magic has 288MB RAM vs 192 in G1.
I am on 32B sapphire with 192 ram.. it runs *decently* but I wouldn't recommend this for daily use right now. It should be after I strip it of its widgets and sense apps.. (which by then would be pointless build other than the HTC Launcher lol)
It *does* run faster than previous builds because it uses zram (compcache) instead of swapping which makes it even slower.
I understand. that's my personal opinion. and I want to comments with you....
Thanks
Sent from my HTC Dream using XDA
Go figure I talked so much smack to get this re-released, and my dumb a$$ can't even get this bad boy to boot. Im somewhat sure i have to re partition my card. It just wont even install. OHHH THE IRONY!!
yeah it shows an error while installing...tried a couple of times with amon ra,cwm2&4..but no luck...
Khizzer said:
yeah it shows an error while installing...tried a couple of times with amon ra,cwm2&4..but no luck...
Click to expand...
Click to collapse
Oh thank the Devs ( lol see what I did there) I thought it was just me. Are you getting error at SD/... status (0). That's what I'm getting. I thought maybe I have to repartition my SD but my SD is petitioned with everything maxed out to the highest settings. It installed once but I stuck at the g1 screen. I guess I just keep trying
let me see..
The error is because of updater-script. I added a fixed updater-script, just replace it in the zip. (META-INF/com/google/android/updater-script)
e334 said:
The error is because of updater-script. I added a fixed updater-script, just replace it in the zip. (META-INF/com/google/android/updater-script)
Click to expand...
Click to collapse
Awesome, thanks. Gonna try it right away. Ill just edit this post withthe results so I don't clutter up the thread.
Edit: I'm getting no love from this rom. It just wont install, and I tried every different way. With cMTD, firerats mtd regular mtd but it just wont boot. I have to be doing something wrong.
should i flash a kernel over it...
it doesnt boot...
any flashing instructions would be good...
Mine does not boot too. It seems that /sd-ext can't be mounted
ThauExodus said:
Mine does not boot too. It seems that /sd-ext can't be mounted
Click to expand...
Click to collapse
I've tried it on a T-Mobile myTouch 3G (GSM) PVT32B with latest Radio combo and booted!
Here's what i've done, following the BananaBread thread method of flashing:
Flashed using: CWM 2.5.0.7 (only version i found to support SD-Ext!) in this order:
1) recovery-v1.5.9-Alpha3-CustomMTD_S.zip
2) mtdpartmap.txt (i put 230 for OS and 6 for Swap, which left me with 230 for apps)
3) ohsaka-super-wipe.zip
4) Flashed DS_SFM_3.0.2_FULL.zip (after implementing the fix mentioned of updater)
5) Booted!
Works:
- WiFi
- Bluetooth (Turns on and Paired with my PC)
- Widgets
- Market
- GPS (tested with iGO)
- SetCPU (autodetect works!)
- Restart / Power Off
Doesn't Work:
- Camera (kept crashing)
Can't Test:
- Calls (i don't have a spare SIM card for this phone)
I've attached LogCat of all the operations i've done, including trying to open the Camera.
All-in-All, pretty good rom, not the fastest of the bunch but still works really nice for such an old device (this IS the very 2nd Phone that came out with Android!).
I do wish they could fix the camera
doesnt work for me....and i didnt get the sd-ext thing...should i mount it manually...
Khizzer said:
doesnt work for me....and i didnt get the sd-ext thing...should i mount it manually...
Click to expand...
Click to collapse
Which version of CWM are you using ?