this is for 32A RADIO 6.35.* and SPL 1.76.2007 please do not try this on anything else as it could damage your phone!!
i am not responsible for any damage, brick, your phone exploding or radioactive batteries
this is new kernel for cursorsense, but it can also be used on any other 1.5 ROM for 6.35 radio
i have overclocked the kernel so it can run 1 GHz
but it is set to be between 660 MHz to 1 GHz so most of the time it will be on 800 MHz
this is still W.I.P. so mind before flashing! and always make a backup of your phone before
i will take any request for anything! so please reply with some info on what to clean up, work on or optimize
at last but not least i would like to thank
-eugene373: for the first script used for this and his idea
-charnsingh_online: for his support, testing, giving me the idea to this and working along my side in the whole progress
-Cursordroid: for the fantastic Rom, kernel and support
- everyone else that have helped just a little bit with this. especially you reporting and giving feedback!
the update zip contains: boot.img, wlan.ko and compache modules
to install simply flash on top of the ROM
version 0.2
min: 245 MHz
max: 998 MHz
cleaned up the script allowing the overclocking so its smaller and reacts better
this is not finished build so please comment what can be done!
should be more stable than V0.1
link to download
4shared: http://www.4shared.com/file/218371784/43a55720/CCR-06-RalleGade-V02.html
megaup: http://www.megaupload.com/?d=JQXVI9Q6
version 0.1
min: 660 MHZ
max: 1 GHz
i have cleaned out most debug options from the kernel so it's now booting even faster!
cleaned: ocfs2, jbd2 ext2, 3 and 4
a bit more responding overall
link to download:
4shared http://www.4shared.com/file/218319243/3d4b922b/CCR-06-RalleGade.html
megaup http://www.megaupload.com/?d=GA1WD1UZ
How dangerous is it to use this? Any overheating, freezes, battery leaks or similar issues? How would it affect the lifespan of the processor?
Plus im not sure if google thought that such things would be done and implemented any counter-measures...like BSOD in windows...
can you mirror the file on megaupload or rapidshare, reason being im in china atm and 4shared seems to be blocked
Has anyone tried this?
1ghz? That's kind of double the CPU speed, i fail to see how that's safe to do on a cellphone
i tried , my magic runs on this kernel @ 825mhz , and everything seems to be ok , of course device is hot
the overclocking is installed over the existing rom - so it can be undone by restoring a nand backup or re-applying the rom's update.zip?
@michaldepa: what is hot? a little bit more or really boiling hot?
hone2009 , device is a little bit more hot than stock , stable for one hour , with ~10 phone calls and 10minuts teeter.
It would be nice to stable the overclocking around 650/700Mhz, maybe the heat and the battery loss wouldn't hurt much.
I'll keep an eye on this thread, but i'm not trying it yet.
ralle.gade said:
i will take any request for anything! so please reply with some info on what to clean up, work on or optimize
at last but not least i would like to thank
eugene373: for the first script used for this and his idea
charnsingh_online: for his support and for giving me the idea to this
link to download: http://www.4shared.com/file/218170587/2c5c149a/CCR-06-RalleGade.html
the update zip contains: boot.img, wlan.ko and compache modules
to install simply flash on top of the ROM
Click to expand...
Click to collapse
I would just like to ask: can anyone work one for old radio??
As I'm still on 1.33.0009 spl with old radio, reluctant to flash to new spl or radio as it'll brick my phone easily
can it even work on old radio?
Of course it can, I'm also looking for a port for the old radio.. maybe something for super d
Great work!
Do you have plans to extend the patch to other ROM (e.g. Eclair)?
@ralle.gade Where are your modiffied kernel source or patch for overclock?
It's not here yet as I wanna make some finetuning tweeking and porting to other roms until then enjoy what you got
And BTW what roms do you want this for?
ralle.gade said:
It's not here yet as I wanna make some finetuning tweeking and porting to other roms until then enjoy what you got
And BTW what roms do you want this for?
Click to expand...
Click to collapse
Super D 1.8 - Ahmgsk port for old radio...
If you cant do that then make one for the new radio
Thanks in advance!
Your welcome!
working wifi
Hello, this kernel is great, but could You do something about wifi, i can't even run it please
That should be Fixed with the WLAN.ko included!
can you make something for MARSDROID SPL7 1.8 B, it on a new radio. but its donut, not cupkake.
Is this worth? I mean, are the benefits worth the risk? How's the battery doing? Is the phone noticeably faster?
Thanks
Related
Thanks to chris-steenkamp's great find, it seems that we now can have fully working LEDs on any Hero ROM that can be made to run on Magic 32A (=means one that has a 32A kernel available or works with one of the supported kernels). The fix itself is amazingly simple and can be done like this:
1. Reboot phone into recovery (the recovery must have root and adb access - I recommend Amon_RA's great recovery)
2. Connect the phone to your PC
3. Switch to your Android SDK tools directory
4. adb shell mount -a (ignore warnings about /dev/mmcblk0p2 not mounting if you see them)
5. adb pull /system/build.prop .
6. Edit the build.prop file that you have just downloaded. Change ro.product.device from hero to sapphire. That's it!
7. adb push build.prop /system
8. adb shell sync
9. Reboot phone. You should now have working LEDs!
I've also repackaged most of the available 32A kernels with the modified build.prop file for some of the most popular Hero ROMs available. Please note that I take absolutely no credit for these kernels, I've just repackaged them to include the LED fix. All of the credit for making these kernels goes to hotweiss, modaco and redglasses.
Repackaged 32A kernels for specific ROMs with the LED fix incorporated:
TheOfficial Hofo 32A Kernel update by hotweiss for Drizzy's Hero ROM 1.5.5
TheOfficial Hofo 32A Kernel update by hotweiss for JACxHeroSki ROM 2.1
MoDaCo 2.2 32A Kernel update by modaco for MoDaCo 2.2 Hero ROM 1.5.5
MyHero 2.6.29 BFS 32A Kernel update by redglasses for MyHero 1.1.2 Hero ROM
MyHero 2.6.29 non-BFS 32A Kernel update by redglasses for MyHero 1.1.2 Hero ROM
Update for getting the trackball glow working in most likely any ROM on 32A Magic
Trackball glow fix for 32A
New! Experimental 32A kernel updates for specific ROMs with LED fix and other goodness compiled and packaged by me:
Note: Because of complaints about extreme bandwidth usage from my ISP, all files are now Rapidshare hosted only. Sorry.
Qteknology 1.6 2.6.29 BFS-303 32A 1.1 kernel update for Qteknology 1.6 and 1.7 by Qteknology
MyHero 1.1.3 2.6.29 BFS-303 32A v1.1 kernel update for MyHero 1.1.3 Hero ROM by redglasses
eViL ROM v3 2.6.29 BFS-304 32A v1.2.1 kernel update for eViL Hero v3 by eViL D:
eViL ROM v3 2.6.29 non-BFS 32A v1.2.1 kernel update for eViL Hero v3 by eViL D:
eViL ROM v3s 2.6.29 BFS-304 32A v1.2.1 kernel update for eViL Hero v3s by eViL D:
Blur Hero 1.5.7 2.6.29 BFS-303 32A v1.1 kernel update for Drizzy's Blur Hero 1.5.7 by Drizzy
T-mobile Pulse for G1 1.1c 2.6.29 BFS-303 32A v1.1 kernel update for T-mobile Pulse for G1 1.1c by diaztradeinc - VERY EXPERIMENTAL ROM, slow and many things don't work yet!
SenseHero 1.0 2.6.29 BFS-304 32A v1.2.1 kernel update for SenseHero 1.0 by ccyrowski
SenseHero 1.0 2.6.29 non-BFS 32A v1.2.1 kernel update for SenseHero 1.0 by ccyrowski
Drizzy's Final Hero 1.0 2.6.29 BFS-304 32A v1.2.1 kernel update for Drizzy's Final Hero 1.0 by kingclick
MotoBlur 1.1 2.6.29 BFS-304 32A v1.2.1 kernel update for MotoBlur 1.1 by twistedumbrella - WiFi doesn't seem to work, minimal testing, HIGHLY EXPERIMENTAL
eViL Sense 1.5 2.6.29 BFS-304 32A v1.3 kernel update for eViL Sense 1.5 by eViL D: - don't forget that this ROM doesn't have a bootscreen, it's just blank
Hero3G UnI Tattoo Donut 2.6.29 BFS-304 32A v1.3 kernel update for Hero3G UnI Tattoo Donut 1.6 by eugene373
Dwang Donut 2.6.29 BFS-310 32A v1.4D kernel update for Dwang Donut 1.12 and 1.13 by dwang
A word about "my" kernel update
Although I refer to that new kernel update as "mine", that's not really true. I'm not really a dev at all. I'm responsible for compiling the kernel, packaging the updates and for some minor tweaking and tinkering to get everything running, yes. But most of the credit for the creation of those kernel updates goes to the people who made it possible (mostly without even knowing): Cyanogen, TigerTael, hotweiss, modaco, bcrook, chris-steenkamp, Amon_RA, gboddina and countless others here at XDA. Thanks for doing the hard work and letting us go along for the ride!
The kernel in "my" updates is the latest Cyanogen 2.6.29 kernel with all the goodness that comes with it, most notably the latest BFS 304 code. As far as I can tell, there are no major problems with it and everything seems to be working fine, but please bear in mind that it's rather experimental and if you're going to try it, backup and be cautious. The kernel works just fine for me, but YMMV.
Unlike pretty much all the other G1/32B to 32A ROM ports I've seen so far, if you combine my new kernel updates with the original G1/32B ROMs, the kernel modules should be working. Which also means there's possibility for compcache, which I think is actually a first for 32A.
One more thing - those kernel packages MAY more or less work on other ROMs as well, but they're really made for the specific ROMs. If you insist on trying it with some other ROM, be sure to do nandroid backup before! The update script deletes/replaces some system files and there's no real guarantee it won't break your system on ROMs other than those they're supposed to be used with.
How to combine 32B/G1 Hero ROM with 32A kernel:
(0. Backup everything, but that should go without saying. I use Backup for Root and MyBackup Pro for user data and of course Nandroid)
1. Pick your preferred 32B/G1 Hero ROM and the corresponding kernel update from the above list, download them and place them in the root dir of your SD card
2. Start your favourite recovery (again, I use Amon_RA's) - it shouldn't matter if you have it flashed into phone or start it via fastboot.
3. Wipe (just in case) and if you use app2sd, format your ext3 partition as well
4. Flash your downloaded ROM file to the phone
5. Without restarting the phone (important!), flash your downloaded 32A kernel update
6. Restart the phone and hope that everything will work for you. Bear in mind that as usual, the first boot after flashing often takes a long time.
There's also another possibility to get LEDs working on 32A with ROMs that are not on the previous list. Some of the ROMs seem to already have the fix incorporated (that's how it was discovered). Those ROMs lack their kernel counterparts for 32A, but sometimes can be combined with other 32A kernel updates and work (for the most part).
LED-enabled ROMs that we know work on 32A when combined with one of the supported 32A kernels:
Qteknology 1.6 by Qteknology
eViL Hero v2.9.5 by eViL D:
Kernels that can be combined with LED-enabled ROMs:
TheOfficial HoFo for Drizzy's ROM by hotweiss. Known problems: multitouch doesn't work.
MyHero 2.6.29 (both BFS and non-BFS) by redglasses. Known problems: some problems with trackball glow notification.
MoDaCo 2.2 32A kernel by modaco. Known problems: compcache can't be enabled.
If you like my work, buy me a Pepsi
You mean you used QTek 32B ROM in you 32A device?
same question as pabbas, did you port the 32b rom to 32a, if so, just uplaod it, thx
What he did is flashing the 32b rom and then try to flash (one at a time) all the 32a kernels he mentioned..porting a 32b rom to 32a is all a matter of kernel substitution..
dBartoz said:
What he did is flashing the 32b rom and then try to flash (one at a time) all the 32a kernels he mentioned..porting a 32b rom to 32a is all a matter of kernel substitution..
Click to expand...
Click to collapse
So we can flash any 32B to 32A with the right kernel?
Yes, just as dBartoz says. Flashed the 32B ROM from the recovery and without leaving the recovery, flashed the 32A kernel update over it to overwrite the boot.img and wlan.ko with the 32A ones. That's pretty much all you need to do to run 32B ROM on a 32A device. Granted, you lose the ROMs customized kernel, but then again, there's still a lot to gain by doing this. I thought this is common knowledge here.
I can probably repackage the ROM and the kernel into one package and upload it, but honestly, I can't really see the point in doing that (and I would be pretty much distributing someone else's work without contributing anything).
Case_ said:
Yes, just as dBartoz says. Flashed the 32B ROM from the recovery and without leaving the recovery, flashed the 32A kernel update over it to overwrite the boot.img and wlan.ko with the 32A ones. That's pretty much all you need to do to run 32B ROM on a 32A device. Granted, you lose the ROMs customized kernel, but then again, there's still a lot to gain by doing this. I thought this is common knowledge here.
I can probably repackage the ROM and the kernel into one package and upload it, but honestly, I can't really see the point in doing that (and I would be pretty much distributing someone else's work without contributing anything).
Click to expand...
Click to collapse
thanks man,
I'm going to try it out
Case_, did you test if the bluetooth is working well with the "mix" rom for wich the led is working?
In that case this could be a (the first?) really full working hero rom for magic..
Let us know if you find any issues, as soon as I have some time I'll be checking it out too..
EDIT
Did you have to create three partitions (fat32, swap, ext) to make the rom work or is leaving only the fat32 partition ok?
You know, with 32A we don't have those lack-of-memory issues..
dBartoz said:
Case_, did you test if the bluetooth is working well with the "mix" rom for wich the led is working?
In that case this could be a (the first?) really full working hero rom for magic..
Let us know if you find any issues, as soon as I have some time I'll be checking it out too..
Click to expand...
Click to collapse
I did try camera, GPS and wifi and it all seems to be working just fine. I don't really care for bluetooth, so I did not try that just yet. I'm not even sure what the exact issues were. Will educate myself, try it (if I can) and report back ASAP.
Case_ said:
I did try camera, GPS and wifi and it all seems to be working just fine. I don't really care for bluetooth, so I did not try that just yet. I'm not even sure what the exact issues were. Will educate myself, try it (if I can) and report back ASAP.
Click to expand...
Click to collapse
Thank you very much..
It'd be great if you could report some information about battery life too..
P.S. I edited my previous post with one more question (about the partitions needed), what did you do under that POV?
Thanks again!
dBartoz said:
Thank you very much..
It'd be great if you could report some information about battery life too..
P.S. I edited my previous post with one more question (about the partitions needed), what did you do under that POV?
Thanks again!
Click to expand...
Click to collapse
So I tried the bluetooth and (unless I'm doing something wrong) it seems it's a no-go, sorry. I can pair with devices but that's pretty much it. When I tried using the headset to call, nothing really happened, the phone said the headset is connected, but the sound was still coming from the phone, not from the headset, and clicking on Bluetooth on in the call menu or pushing the headset call button didn't really do anything. That's with the HoFo Drizzy kernel. I'll try the other kernels soon (but I don't think it'll make much difference - then again who knows...)
Edit: With the MyHero kernel, the headset at least seems to work, but the only thing coming from when making a call is the white noise.
Considering the partitioning, I don't really like running app2SD on 32A (I think it actually slows the phone down quite a bit and doesn't help anything), but I also think Sense UI really needs more memory or swap to be usable in the long-term, even on 32A (and as reported by my friend with Hero, even he does have pretty much the same memory and performance issues I have with any Hero ROM without swap), so what I did was create (using parted via adb within the recovery) the usual three partition setup (only the ext2 partition was really small, like a few MB max) and then delete the ext2 partition, so there's no partition for app2SD and yet the swap partition is still identified as /dev/block/mmcblk0p3 , so the ROMs I'm trying pick it up and use it without the need to reconfigure anything. I'm currently using 64MB swap and as far as I'm concerned, the phone runs great, much better than without the swap partition, though I'll probably change the swap partition size to 32MB soon, as I think it should be sufficient.
As for the battery life, absolutely no complaints whatsoever - seems to me it's actually maybe even a bit better than with stock ROM (and that is with "always-on mobile" enabled), but I may be imagining it
Qteknology's rom use a shell script to making LEDs work. Now we have a app to do that.
Please look at this thread.
http://forum.xda-developers.com/showthread.php?t=565015
redglasses said:
Qteknology's rom use a shell script to making LEDs work. Now we have a app to do that.
Please look at this thread.
http://forum.xda-developers.com/showthread.php?t=565015
Click to expand...
Click to collapse
Yeah, I noticed some of the Hero ROMs contain the HeroLed application (and forgot to look up on it). Mainly because it's force closing at the phone startup
So, from the 32A point of view, the shell script is definitely a better alternative for now, as it's the only one working (but still only with some of the kernels). But it's great to know why this seems to be the only ROM that works, thanks for the info!
I just flashed Qteknology + HoFo for Drizzy's as you suggested.
Tried the led with handcent sms a second ago, and it works
You rock, Thanks for the helpful post
Finally a confirmation that it works for someone else as well, great! Just out of curiosity to see if it really is somehow related to SPL, what SPL do you use?
Oh, and don't thank me, I'm just "mixing" together someone else's hard work.
I'm thinking about the possibility of "splicing" this LED shell script from Qteknology ROM into other Hero ROMs, but so far I wasn't even able to locate it in the ROM or find some info about it :/
So far I have used only myhero rom's, and they worked very well. This rom works even better! Only thing I would love to see is transparent notification area (like in myhero rom).
Great work! Thanks!
Led notifications works with sms popup and missed call aplications.
The dafault one that came with the phone, which is an italian 32 by TIM.
Just got this infos from fastboot:
HBOOT-1.33.0008 (SAPP10000) | RADIO-3.22.20.17
II just noticed that multitouch aint working for me. I tried the browser and the album and it won't let me zoom that way.
Another issue is that I keep geting force close on com.HTC.core or something like that.
Ah, thehtc keyboard is pretty damn laggy on the browser.
Should i try another kernel? Which one should I try?
nubcake said:
II just noticed that multitouch aint working for me. I tried the browser and the album and it won't let me zoom that way.
Another issue is that I keep geting force close on com.HTC.core or something like that.
Ah, thehtc keyboard is pretty damn laggy on the browser.
Should i try another kernel? Which one should I try?
Click to expand...
Click to collapse
You're right, the DrizzyHoFo kernel seems to not support multitouch. Thanks, I'll mention it in the first post. Try either of the other two kernels, those work just fine here. I have no preference in them, really - the MyHero kernel has a BFS alternative available, whereas the MoDaCo kernel (which in its 32A alternative I think does NOT have BFS, though I can be wrong) should have the possibility of enabling compcache (although I need to try to work on that, there's some problems with modprobe I can perhaps work around).
No problems with force closes here, at all. Did you wipe before flashing the ROM, as you always should, and if you use ext3 for app2sd, did you format it as well? Other than that I'm afraid I can't really help you, sorry.
But there's now another ROM that has LED working on 32A - eViL Hero ROM v2.9.5. So if anyone doesn't like Qteknology for some reason, you can try this one. I'm updating the first post with my findings (I've changed it's structure a bit for now and altered the thread title as well). It's most likely that working LEDs will soon be common on most Hero ROMs even when running those on 32A - I'll try to keep updating the list in the first post for as long as I think it makes some sense.
Edit: It was actually coded by phhusson, in conjunction with toastcfh and others. See thread here: http://forum.xda-developers.com/showthread.php?t=665515
This thread is about a new overclock kernel patch for the MSM7K, which includes the G1 and Magic.
Devs working on overclock kernels. If you want your overclock kernel in OP (here) send me a PM and I'll consider linking to it.
For devs, the original patch is here, and an updated commit to allow for scalable frequencies is here
There's also an autodetection patch for SetCPU by coolbho3000 himself here
pershoot's github for the lazy: http://github.com/pershoot/ds-kernel
Downloadable Kernels to Flash for the Rest of Us
These kernels are not officially endorsed by Cyanogen for his ROM, so use at your own risk and do not file any bug reports to the ROM owners. pershoot has done some good things to this for Cyanogenmod including some extra frequencies to choose from.
EBI0 version = 32B Magic or G1 on 1.x or 2.x radio
EBI1 version = 32A Magic or G1 on 3.x radio
2.6.33.3 for any rom EBI0/EBI1 by pershoot
Has lots of tweaks and goes up to 576 MHz
Verification:
This works. Read the thread.
Video proof of 614 MHz: http://www.youtube.com/watch?v=9Oaesb0OX8k
FAQ:
A) How do I try this without flashing this to my phone?
If you want to try this without flashing your phone, download the zip file for your phone. First turn OFF wifi. Then turn your phone off.
Now go into fastboot. Extract boot.img, probably in the same folder as your fastboot application. Then use:
Code:
fastboot boot boot.img
(replace boot.img with the name of the img file)
This will make the kernel run temporarily on your phone up till your phone is restarted again. Do NOT turn your wifi on at this time, because it will freeze your phone. If you want to keep it, flash the whole zip file from recovery. Otherwise just restart your phone and you will be back to whatever you had before.
B) Ramhack?
What is known as the ramhack is done by modifying the kernel source code with a patch and making a new kernel to flash. Hence you see a boot.img in the zip files you flash.
This overclock kernel patch modifies the source code of the kernel. If you want both ramhack together with the overclock, you need a kernel that contains both the ramhack AND the overclock patch. If not explicitly stated, you can assume that the overclock patched kernel does not contain the ramhack patch and thereby does not have ramhack.
C) What phones does this work on?
All HTC Dream/G1 and myTouch/Magic, not including Fender or 1.2 editions of the Magic for the precompiled kernels in this thread.
If you are applying the patch yourself it should work on any MSM7K device.
D) What are some prerequisites I need to flash this?
Custom recovery compatible with test keys, or root with working adb/fastboot.
And you need a compatible phone (see C)
E) My wifi doesn't work after I flashed x.img file!
YOU MUST FLASH THE CORRESPONDING WIFI MODULE WHENEVER YOU FLASH THE KERNEL.
The .img file contains the kernel, which requires a patching wifi module to be recompiled (wlan.ko located in your system volume) with that kernel.
If wlan.ko was not provided, wifi will simply not work. Ask whoever compiled that kernel to provide a wlan.ko file for you to flash.
F) Is this stable?
Stability seems to vary, but at the moment I do not recommend using 614 MHz for day-to-day use.
This kernel does not even run stable at 614 MHz right now for me, or at least when I try to just plug in my usb cable. Not sure what can be done there. I threw in the 653 MHz EBI1 kernel that wouldn't boot for me for kicks.
My gut feeling of being unable to boot at 653 MHz and being unstable at even 614 Mhz leads me to think that the G1 is a pretty hopeless overclock. The 32B Magic might have better luck. CDMA Heros are getting up to 700 MHz easily on the other forum. It is not surprising that HTC designed the phones to have higher clock tolerances than the G1 designed to run at 384 MHz.
(DEVS/COOKS) Original kernel patch to overclock from 528 MHz to 711 MHz, but that wouldn't boot. Boots fine at 614 MHz on my G1 with 3.x radio. Probably more stable at lower speeds.
For all MSM7K devices including the Hero, Dream, Magic
Credits:
phhusson for sharing
ToAsTcfh for coming up with it
Cyanogen because it's his kernel source
benbuchacher for Super D
farmatito for EBI0 compile
coolbho3000 for SetCPU
pershoot for some great compiled kernels
Notes:
I am not a dev!
This patch performs more changes the kernels source in acpuclock.c and involves the software modification of the way PLL is handled to allow for the overclock.
It is different than the previous OC patch that only modified the frequency table.
This patch adjusts the 528 MHz clock to 711 MHz, and can be modified by changing the patch file. Acceptable clocks are multipliers of TXCO (19.2MHz).
710.4 MHz = 19.2 * 37
Should work on 2.6.27 and 2.6.29, and maybe more.
Some devs have already added this to their CDMA Hero ROMs with reports of success.
xaueious said:
From Hero CDMA forums:
http://forum.xda-developers.com/showthread.php?t=665515
I am not a dev so my deductions may not be that correct.
This patch performs more changes the kernels source in acpuclock.c and involves the software modification of the PLL to allow for the overclock.
It is different than the previous OC patch that only modified the frequency table.
This patch adjusts the 528 MHz clock to 711 MHz, and can be modified by changing the patch file.
Should work on 2.6.27 and 2.6.29, and maybe more.
For everyone else who doesn't know this is, don't flame yet. I want someone to patch their kernel source and report back. If you don't know what that means try not to contribute.
I haven't tried this for myself because I don't have a lot of experience building kernels, and my source is way outdated such that it will take me the whole night to sync my repos.
Some devs have already added this to their CDMA Hero ROMs with reports of success.
I am withholding my judgement on this for now.
Click to expand...
Click to collapse
Sounds sweet, but is it real this time? however if it is, its going in my new kernel
It had already been established before that this won't work on Dream because the chip's PLL is set to a clock where the maximum stable speed you can get is 528 Mhz and the next, acceptable speed (not placebo like the one tried before) crashes the phone.
i thought the PLL was written in software?
I was doubting this too, but there's indication that it is different this time.
jad011 said:
i thought the PLL was written in software?
Click to expand...
Click to collapse
This is what this patch does differently.
Someone try this!
xaueious said:
This is what this patch does differently.
Someone try this!
Click to expand...
Click to collapse
not bricking my phone today
Dude you can't brick your phone with a patched kernel like this.
No devs willing to try it? The patch might be quick one. Just take a look.
The diff might not apply as is since it was made for CDMA Hero. In any case, I'm not worried because I'm sure that we will figure something out.
http://forum.xda-developers.com/showthread.php?t=557863
http://forum.xda-developers.com/showthread.php?t=631810
http://forum.xda-developers.com/showthread.php?t=630236
it's been tried, turned out to be duds
jubeh said:
http://forum.xda-developers.com/showthread.php?t=557863
Click to expand...
Click to collapse
I know. I asked the dev about the exact same thing with the exact same threads!!!
Here was his reply: http://forum.xda-developers.com/showpost.php?p=6234015&postcount=91
Do me and everyone else a favor and go to the thread in the OP and READ
If not just look at the diff file. You'll see what I mean. This HAS NOT been done before.
Better be for real. This'll defiently help the myTouch Slide ROMs run.
If this is real, I'm going to buy the slim extended battery for g1 and flog another 6 months or so out of this bad boy.
I really wish I knew how to use this patch. I would be very willing to flash this on my device Can someone who knows how to do it for the sake of our curiosity, instead of just ignoring it? Unless things are tested, every solution proposed is a possibility Thanks in advance guys!
If anyone wants to post up a build/boot.img with this hacked on, I'd be willing to risk my spare G1 to test the results.
this isnt going to brick your phone
The guys over ad cdma hero forum have a rom with 746mhz...
Who can tell if it works? not me...
for me the speed is fast enough already with 512 mhz fix... but clocking from 128 to 746 mhz on demand would be epic
and then the new mytouch slide rom... rocking it at the moment. love my phone like never before
Update can wait
AWESOME!
This is great! I was hoping someone would find a way to OC this processor! There's a Hero Rom with it confirmed working with benchmarks that look really promising. I can't wait for it to be built into a rom for us G1 users!
..so why doesn't someone just patch it in and give it a shot?
Well I am trying to boot it and my phone freezes with the stock patch after displaying the bootscreen. Trying one more time and lowering the multiplier from 37 to 34.
34 * 19.2 = 652.8 MHz -> FAILED
Didn't boot properly either. It stopped with the line "D/BT HSHFP( 706): Starting BluetoothHeadsetService" in logcat for me. Phone freezes after video goes on. The entire boot seems fine otherwise, even building dalvik-cache and everything.
Boots with what I think is 614.4 MHz, for a 16% overclock, CM-kernel patched:
My Linpack on Super D without JIT is about
2.04 seconds with 2.647 Mflops after multiple runs.
My Super D install is really choppy on CM-kernel though. Until I figure out how to build wg-kernel I wont be keeping this.
2.35 seconds with 2.308 Mflops after multiple runs
The improvement of 15% is inline with theoretical values!
Anyways I think this proves that this OC is doing something!
Proof of concept kernels for Super D 1.10.2 (should work on some other ROMs)
Based on cm-kernel
Should be running at 614 MHz. BogoMIPS wont report it, and the kernel is not going to report the frequency it is running at since the change is internal. But the benchmark shows an improvement so I'd say this works.
EBI1 version is for 32A or people on 3.x radios only! (aka me)
G1/32B version is coming.
(ramzswap.ko is in there but you might not even need it. I left it there because I was too lazy to take it out)
Notes
No point of building this unless this is done with wg-kernel with RAMHack for me. This is a proof of concept rather than something you should use as an everyday kernel. I found wg-kernel at 528MHz with RAMHACK to be smoother despite the higher benchmarks of the 614 MHz kernel.
Someone can try different frequencies...
Sounds great... I am a bit surprised why people are not more enthusiastic about this? Just because the previous OC was found to be wrong doesn't mean that we give up right?
Anyway, how do we apply this to our devices? Just flash it from recovery? Or ? Sorry, am a noob, but would like to test it out Btw, Thanks for the good news
xaueious said:
Well I am trying to boot it and my phone freezes with the stock patch after displaying the bootscreen. Trying one more time and lowering the multiplier from 37 to 34.
34 * 19.2 = 652.8 MHz -> FAILED
Didn't boot properly either. It stopped with the line "D/BT HSHFP( 706): Starting BluetoothHeadsetService" in logcat for me. Phone freezes after video goes on. The entire boot seems fine otherwise, even building dalvik-cache and everything.
Boots with what I think is 614.4 MHz, for a 16% overclock, CM-kernel patched:
My Linpack on Super D without JIT is about
2.04 seconds with 2.647 Mflops after multiple runs.
My Super D install is really choppy on CM-kernel though. Until I figure out how to build wg-kernel I wont be keeping this.
2.35 seconds with 2.308 Mflops after multiple runs
The improvement of 15% is inline with theoretical values!
Anyways I think this proves that this OC is doing something!
Proof of concept kernels for Super D 1.10.2 (should work on some other ROMs)
Based on cm-kernel
Should be running at 614 MHz. BogoMIPS wont report it, and the kernel is not going to report the frequency it is running at since the change is internal. But the benchmark shows an improvement so I'd say this works.
EBI1 version is for 32A or people on 3.x radios only! (aka me)
G1/32B version is coming.
(ramzswap.ko is in there but you might not even need it. I left it there because I was too lazy to take it out)
Notes
No point of building this unless this is done with wg-kernel with RAMHack for me. This is a proof of concept rather than something you should use as an everyday kernel. I found wg-kernel at 528MHz with RAMHACK to be smoother despite the higher benchmarks of the 614 MHz kernel.
Someone can try different frequencies...
Click to expand...
Click to collapse
To be honest it doesn't look that useful for the G1. But I would still like to see a dev pick this up for reaping the little benefits that this does promise.
I'm at least hopeful that we can get stable 576 MHz for all roms from now on.
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
This is a fully functioning Froyo Rom based off CM6 Latest Nightly Build
please post any issues you may have here - not in cyanogen mod, as my changes may have been the cause
always recommend that you backup whatever you need - wipe and then install - as I am now using the data partition for some apps
to enable overclock greater than 576mhz see this thread for alternate kernels
note : let me know what frequencies you have problems at though so I can judge for future oc better if you choose to use these - NOTE: has not been updated lately and these OC kernels may or may not work - I just use 576 mhz
Dumfuqs Kernel Corner!
Using the 710mhz kernel I can get Mflops on linpack with JIT enabled of >= 4.8
Here are the Links! :
After Each Update I always recommend a wipe if any problems are experienced - though u may not have too
32A - 3.22 Radio ( Eg. - Rogers HTC Magic and Rogers HTC Dream)
If YOU DO NOT WANT BLACK CLOCK THEN MAKE SURE TO CHANGE THE SETTINGS IN CYANOGEN SETTINGS!!!
FroyoRedux-1.9.5-32a.zip - 64.4 Mb
32B - 2.XX Radio (Eg. - MT3G, G1, MT3G 1.2)
If YOU DO NOT WANT BLACK CLOCK THEN MAKE SURE TO CHANGE THE SETTINGS IN CYANOGEN SETTINGS!!!
FroyoRedux-1.9.5-32b.zip - 64.4 Mb
Optional Themes :
Sense Style Theme : 195-sense_theme.zip - 3.1 Mb
Galaxy S Style Theme : 195-Galaxy_theme.zip - 3.2 Mb
(if you are not using 6.35 radio then disregard this section!! for magic 6.35 radio only!)
32a - 6.35 Radio Patch
carz_6.35_v0.67-signed.zip - 3.3 Mb
camera does not work - please report issues to carz via his thread in this forum
You must be using cursors modified recovery for it to install proper - 6.35 recovery image download
Code:
fastboot flash recovery recovery-RA-Magic32A-6.35-v1.6.2.img
Flash the recovery on the new radio only!!
Droid Basement Blog - Pershoot Source
CM Source
Carz Source
Credits - Thanks to Cyanogen, Pershoot, Bcrook, anderweb, dumfuq,carz and everyone who helped make this possible!! thanks as it is your work that made this possible
First
Thank you for the rom . will check it out!
Second
Installing now
Hah! and I thought I was going to bed. lol
Thanks!
First thoughts, AWESOME
I haven't installed anything and this ROM has IMPRESSED me like no other.
Logging into Market now, will advise when getting my apps fully recovered.
This looks GREAT
Once they get apps2sd for EXT 2 working I will try this...
Awesome dude. Thanks alot. Been looking for CM 614mhz kernel for a while.
Does wifi work on this ROM?
Every other nightly i have flashed has had no wifi
ok iam trying this rom now.
i hope it havent got memory leak issues like i had with all cm roms.
will give feedback soon!
//Nick
my impressions:
i dont find this rom good man.. sorrym
wifi works.
but this thing got memoryleak issues too as the original cm rom.
when everything is killed i got 23 mb free ram !!!!
this is sooooo low.
so everytime i left an app the homescreen is restarting every time
if you fix the memory leak issues it would be great!!!!!
//Nick
EDIT: who wants to see the memory leak and everytime restarts homescreen ?
pm me for my msn and i will show you at cam..
nickislauw said:
my impressions:
i dont find this rom good man.. sorrym
wifi works.
but this thing got memoryleak issues too as the original cm rom.
when everything is killed i got 23 mb free ram !!!!
this is sooooo low.
so everytime i left an app the homescreen is restarting every time
if you fix the memory leak issues it would be great!!!!!
//Nick
EDIT: who wants to see the memory leak and everytime restarts homescreen ?
pm me for my msn and i will show you at cam..
Click to expand...
Click to collapse
its all in how you set the rom up...
personally, this rom flies...
using:
no jit (havent played with it yet)
- swap (swapper 2, partition option unchecked, 32mb w/ 30 swappiness)
- no compcache
the only problems i have soo far is...
- surface dithering cant be disabled,
- cant increase
other than the few apps i didnt like (deleted them with titanium)
everything else is golden, solid work sir
Michaelr219 said:
its all in how you set the rom up...
personally, this rom flies...
using:
no jit (havent played with it yet)
- swap (swapper 2, partition option unchecked, 32mb w/ 30 swappiness)
- no compcache
the only problems i have soo far is...
- surface dithering cant be disabled,
- cant increase
other than the few apps i didnt like (deleted them with titanium)
everything else is golden, solid work sir
Click to expand...
Click to collapse
ok i got 128 mb swap on my mem card but how do i enable it in CM???
Nice!
Best Froyo Rom i`ve had so far ... ! Thx
nickislauw said:
ok i got 128 mb swap on my mem card but how do i enable it in CM???
Click to expand...
Click to collapse
download swapper 2 from market
open it
hit menu
go to settings
pick your settings for size and swappiness
(recommended is 32mb and 30 swappiness, anything more = overkill)
reboot
after reboot
open terminal and type
Code:
su
free
it should show total mem + swap
hope that helps
How is the battery life?
The last 2 versions of CM have been killing me, i had to switch back to Dwang 1.7.1 for an every day ROM.
ekeefe41 said:
How is the battery life?
The last 2 versions of CM have been killing me, i had to switch back to Dwang 1.7.1 for an every day ROM.
Click to expand...
Click to collapse
i miss dwang... fastest most stable rom everrrrr
but, its too early to tell... im gonna let it run out of juice
wipe battery stats
full charge (phone off)
and wipe stats again
then report back tomorrow...
this rom is solid though, closest to dwang in speed and stability with loadssss more features...
i just need someone to help with the vm heap size and dithering issue i mentioned earlier (cant change them, even after reboot)
maybe swap has something to do with it... im gonna disable it and retry
ill report back
ps - for the titanium restore... make sure the new option in the menu for 2.2 users is checked or it WONT WORK!!!!
please add to the first post
hee michael,
i enabled swap with swapper 2 but can i now remove the program??
i setted the swap so theres no need for the program? can i remove it ?
//Nick
nickislauw said:
hee michael,
i enabled swap with swapper 2 but can i now remove the program??
i setted the swap so theres no need for the program? can i remove it ?
//Nick
Click to expand...
Click to collapse
you can try, and then run the terminal command again to see if the settings stick... i dont believe they will tho without running the firerat patch... but then at that point, it will default to whatever swap settings you have on a userinit or your partition... its funny you asked that, cause i was just looking at my free mem thinking the exact same thing
I just installed it and I like it. But I can't find flash sites working. Is there a way to enable this? Thanks!
Michaelr219 said:
you can try, and then run the terminal command again to see if the settings stick... i dont believe they will tho without running the firerat patch... but then at that point, it will default to whatever swap settings you have on a userinit or your partition... its funny you asked that, cause i was just looking at my free mem thinking the exact same thing
Click to expand...
Click to collapse
LOL ISNT THIS funny? after swap etc... i got like 38mb free ram!!!!!!!
this is great man!!!!!
PS: look at the 2 links for the pictures of ram and command line of swap.
is the swap still enabled now??? the screenshot was taken after i removed swapper 2
link 1:
http://img834.imageshack.us/i/afbeelding2.jpg/
link 2:
http://img51.imageshack.us/i/afbeelding3o.jpg/
//Nick
Hi all
I decided to give you an update for the apparently much-used 2.09 ROM
This is fully rooted, kept completely stock with the following small mods,
mostly for powersaving and ease-of-use.
The following additions were made:
- Busybox + Latest su and SuperUser.apk.
- Still has A2SD+, a bit cleaner implementation this time. (Fully depends on whether or not you create an EXT partition, which can be EXT2/3 or 4.)
- OpenVPN and TUN
- Wifi module edited to make sure it never goes into standby.
- Symlinked /data/local/bootanimation.zip for easy bootanimation replacements.
- Cpufreq_interactive governor as default. This is slightly better than ondemand.
- Default undervolting by 75mV-100mV -> Major powersaving.
- UnionFS-FUSE overlay filesystem for /system. This makes /system writeable, and therefore allows you to use stuff like MetaMorph.
Thanks to tgreer for hosting my stuff!
Make sure you pick the correct radio to go with these two ROMs. It's a bad idea to use an older ROM with a newer radio, or vice-versa, seeing as these ROMs have updated RILs.
*updated* HTC 2.10 ROM
32.44.00.32U_5.09.05.30_2 radio (recommended for 2.10 - new RIL)
Older HTC 2.09 ROM
32.43.00.32U_5.09.00.20 radio (recommended for 2.09)
is this de-odexed?
lol that was fast mate cheers will flash to ther halfs phone when she gets back lol
Santa, is that you????
Nekromantik said:
is this de-odexed?
Click to expand...
Click to collapse
Not atm.
It is kept close to stock. Custom ROMs later on will be deodexed, based on this.
Great job mate. No fuss. Straight in there.
surprised...
Nekromantik said:
is this de-odexed?
Click to expand...
Click to collapse
Most probably not I guess (since the OTA also is odexed). But f*ck that, dex files just waste space on your data partition anyway.
excellent misdirection...a majority of us were following 42turkeys little run around and here you were waiting for us.
How about some credit's in the OP to the right people.
nice nice nice downloading now
That's fantastic.
Can anyone OC this Rom pls
YAY
Awesome mate!
Will take the plunge as soon as my DL is finished.
You've added exactly the bits I need (especially the OpenVPN).
Anyone tested this yet?
Fantastic up thanks
Anyone tried it yet lol
Thanks a ton m8.... will try this one instead of the few others posted
Dlding now but speed down to 100kb/s, gone tast asap.
EDIT: thnx for adding the app2sd busybox and vpn settings ;-)
and now the whole thing without f**** SENSE please ...
Can't seem to install this. It only says (Bad)