Related
Based off of htc-kernel-espresso repository from CyanogenMod github and a modified version of toastcfh's overclock patch.
espresso source based is for
espresso devices only
legend source based is for
espresso, legend, or aria devices
No support will be given, use at your own risk, DON'T FLASH unless you know what you are doing .
Version 3.5:
updated source to include interactive governor
added darchstar's patch to fix idle status being set NULL
added a 787 for those that can't do 806
incorporated changes into legend code base
http://www.mediafire.com/?9ziqlmh6vy26x
V4.0: (Requires setting scaling_max_freq in order to boot)
all frequencies included in one kernel.
added 480 back.
864 max
available frequencies: 245760, 400000, 480000, 600000, 768000, 787200, 806400, 825600, 844800, 864000
NOTE:
Since all frequencies are now playing nicely together, I am only going to be releasing one kernel version per source base.
It is up to you to set your maximum speed in your init.d files or you might not boot (since the maximum is 864).
For Those of you who have used my G1 kernels, this will not be an issue since you should know how to do it. For the others, good luck .
Essentially, you need to put something like...
Code:
echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
somewhere in your init.d files. Personally I like to use 00banner since it's first to execute on cyanogenmod.
Don't forget that if you swap out an init.d file you need to make the new one executable. For example...
Code:
chmod 0750 /system/etc/init.d/00banner
http://www.mediafire.com/?7jyeovzuo8lx9
archive:
http://www.mediafire.com/?v6cdcjyf04ebd
These are koush's anykernel.zip's that change your boot and system images. To return to your original state just do a nandroid advanced restore of the boot and system partitions (of course you have to of backed them up first).
github (master branch is legend base, oc-espresso-2.6.29 branch is espresso base. Default is set to espresso)
sweet, he's doing an overclock kernel?? thats awesome!
posted a v2 to fix a problem with minimum frequency.
This version is set to 691/691 when screen is on and 245/245 when screen is off.
edit: this broke it.
dumfuq said:
posted a v2 to fix a problem with minimum frequency.
This version is set to 691/691 when screen is on and 245/245 when screen is off.
edit: this broke it.
Click to expand...
Click to collapse
Lol I was gonna post to not try and set it to a performance profile as it breaks the overclock.
Great work though I'm finally so glad to see this. I flashed it and boot was quite a bit faster as well. A 91mhz gain seemed to make quite a difference. If this arm cpu will hit 800 then this phones gonna fly.
Ok noticing some lag here and there. I just did a quadrant bench and only scored 333. I have not did a reboot since I flashed it. Will try and report back.
Sent from my T-Mobile myTouch 3G Slide using XDA App
v3. fixed for the night.
screen on 480/691
screen off 245/480
sultan.of.swing said:
Lol I was gonna post to not try and set it to a performance profile as it breaks the overclock.
Great work though I'm finally so glad to see this. I flashed it and boot was quite a bit faster as well. A 91mhz gain seemed to make quite a difference. If this arm cpu will hit 800 then this phones gonna fly.
Ok noticing some lag here and there. I just did a quadrant bench and only scored 333. I have not did a reboot since I flashed it. Will try and report back.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
was the lag on v1? if so the minimum frequency was dropping to 19mhz, that's why i had to do the next one.
never tried quadrant before...i kinda like
on test 1, i exerienced a TON of lag... i set min / max at 691 and got lag like a mofo >.> hopefully t3 doesnt lag so bad this time
quick question... if i do this kernel, and i dont like it, can i go back to the old one just by flashing the old one or would that break something??
you could easily make a backup boot image zip
thomas.nelson4 said:
quick question... if i do this kernel, and i dont like it, can i go back to the old one just by flashing the old one or would that break something??
Click to expand...
Click to collapse
This kernel is just for testing purposes. You don't want it for daily use. If you are not comfortable flashing random broken things, don't even bother with it. Currently it takes a big performance hit for 3d graphics and has no wifi.
dumfuq said:
This is a test, this is ONLY a TEST.
Based off of htc-kernel-espresso repository from CyanogenMod github
Wifi is broken.
Performance is LOCKED at 691 mhz.
This is an update.zip that replaces your boot.img. To return to the stock boot.img just do a nandroid advanced restore of the boot partition (of course you have to of backed it up first).
No support will be given, use at your own risk, DON'T FLASH unless you know what you are doing .
oc691-kernel-test-v1-signed.zip
oc691-kernel-test-v3-signed.zip
Click to expand...
Click to collapse
hey do you have the patch for this?
wesgarner said:
hey do you have the patch for this?
Click to expand...
Click to collapse
here is the diff
slide_oc.diff
fyi I ended up hardcoding the 691 instead of using the old technique because the divisor was giving me issues with anything over 652 and I was just trying to do a proof of concept anyway.
Any reason it might go to black on boot-up...for minutes? Confict with new radio maybe?
My slide's looking very brickalicious at the moment so I'm gonna volume down and power into recovery; Just not booting. Was running Slidemeroot5r1.
Dumfuq, I love you.
Oakley44 said:
Any reason it might go to black on boot-up...for minutes? Confict with new radio maybe?
My slide's looking very brickalicious at the moment so I'm gonna volume down and power into recovery; Just not booting. Was running Slidemeroot5r1.
Click to expand...
Click to collapse
guess what, ive got a GREAT answer for ya... that boot image is ONLY FOR froyo roms at this point. sorry bud :/
Oakley44 said:
Any reason it might go to black on boot-up...for minutes? Confict with new radio maybe?
My slide's looking very brickalicious at the moment so I'm gonna volume down and power into recovery; Just not booting. Was running Slidemeroot5r1.
Click to expand...
Click to collapse
Is SlideMeRoot5r1 a CyanogenMod-6.0.0? I think not.
dumfuq said:
Is SlideMeRoot5r1 a CyanogenMod-6.0.0? I think not.
Click to expand...
Click to collapse
Ahh, what douchey lord of noobs I am.
Ok well, needless to say I did a full restore and rebooted. Still goes to black. Any change you have a zip for the stock kernel?
breaks WIFI on SuperFly 1.2 ... me only???
dumb... i can't read
UM BUT maybe pushing some wlan.ko file....?
Oakley44 said:
Ahh, what douchey lord of noobs I am.
Ok well, needless to say I did a full restore and rebooted. Still goes to black. Any change you have a zip for the stock kernel?
Click to expand...
Click to collapse
just flash Slidemeroot5r1 rom without wipe and reboot
Sxyman815 said:
just flash Slidemeroot5r1 rom without wipe and reboot
Click to expand...
Click to collapse
Already wiped system/cache to go back to last restore. In the middle of restore as I type this... . Next time I'll read the thread title a bit better..........ok, yeah it worked .
Right guy's,
I was asked to start this thread by Doomlord to see how many others are having problems flashing cm7 roms that contain the custom kernel.
When i flash the recent cm7 roms with k006 as soon as my screen times out or i switch it off with the power button(quick press)the phone goes into re-boot, it does not do it with the usb connected and my phone does not do it on any other rom even the cm7 that uses stock kernel.
I have tried everything i can think off to fix this issue from flashing repair with seus to using a brand new sdcard with just the cm7 update on to flash, i have run out of ideas, Doolord seems to think it is hardware related, please post if you are experiencing this problem, i am not concerned about wlod, this is a seperate problem.
When you post can you say which rom you have flashed and also which kernel, thanks in advance for your help, hopefully we can get this sorted.:
UPDATE..... THE LINK IS FOR THE BEST SOLUTION FOUND BY 9LUKAS5, HE HAS MADE A FLASHABLE ZIP TO SORT MINILOADER ISSUES OUT, SEE POST 28, PLEASE READ HIS OP AND GIVE THANKS.
http://forum.xda-developers.com/showthread.php?t=1046609
running J's latest CM7 v018 k006 on an X10a and never had this problem
I have had this problem to , on an erlier custom kernel with cm7, i dont use cm7 anymore so cant say if i should have this problem now but i know a bunch of People have reported the same issue in the Swedish forum www.swedroid.se that the phone reboots when you put the phone to sleep. With cm7 kernel 006.
Xperia™
Nothing is True, Everything is Permitted!
Xperia84 said:
I have had this problem to , on an erlier custom kernel with cm7, i dont use cm7 anymore so cant say if i should have this problem now but i know a bunch of People have reported the same issue in the Swedish forum www.swedroid.se that the phone reboots when you put the phone to sleep. With cm7 kernel 006.
Xperia™
Nothing is True, Everything is Permitted!
Click to expand...
Click to collapse
Thanks for the info xperia, i think it may be down to k006, the thing is why do some have the problem and others don't?
Sent from my X10 using XDA App
Hey smartgardens iv just had an idea cant beleive i didnt think of this before! Have tried messing with settings on set cpu? I might be worth creating a screen off profile and have 384 as maximum scaling and 245 as the lowest or even perhaps raise the maximum up some more. Perhaps your processor just isnt getting enough juice!
Sent from my Full Android on x10 using XDA Premium App
The Gingerbread Man said:
Hey smartgardens iv just had an idea cant beleive i didnt think of this before! Have tried messing with settings on set cpu? I might be worth creating a screen off profile and have 384 as maximum scaling and 245 as the lowest or even perhaps raise the maximum up some more. Perhaps your processor just isnt getting enough juice!
Sent from my Full Android on x10 using XDA Premium App
Click to expand...
Click to collapse
Hi Steve,
That's a great idea buddy,I will try that later when i get home from work, what you describe is just what may be happening, thanks for the help.
Sent from my X10 using XDA App
i havent even time to install an app before i get wlod, so cant be setcpu
and i had the same with k005 cm7 rom, and with k006 on miui-formels 2.2,
thanks for thread, i read your pm just few min's ago
tremendouz said:
i havent even time to install an app before i get wlod, so cant be setcpu
and i had the same with k005 cm7 rom, and with k006 on miui-formels 2.2,
thanks for thread, i read your pm just few min's ago
Click to expand...
Click to collapse
Just a thought, it could be that your CPU can't handle the OC/UV of K006. Try doing a clean install with one of J's stock builds and then install set cpu on that. Configure set cpu to "On Demand", Max cpu to 998 and then enable "On Boot"
Boot into XRecovery, backup the ROM then flash J018. If you then do an advanced restore of the Data only from the backup you should end up with Set CPU installed and set to run on boot.
Iv tried doing data restores from v17 to v18 and get md5 mismatch even though iv not touched the file name.
Sent from my Full Android on x10 using XDA Premium App
The Gingerbread Man said:
Iv tried doing data restores from v17 to v18 and get md5 mismatch even though iv not touched the file name.
Sent from my Full Android on x10 using XDA Premium App
Click to expand...
Click to collapse
Once before I've had a backup that had the same problem, I couldn't even do a complete restore from that backup. There is probably something wrong with the backup that's causing the problem.
I managed to do a Data restore from J013 to J018.
GreatBigDog said:
Just a thought, it could be that your CPU can't handle the OC/UV of K006. Try doing a clean install with one of J's stock builds and then install set cpu on that. Configure set cpu to "On Demand", Max cpu to 998 and then enable "On Boot"
Boot into XRecovery, backup the ROM then flash J018. If you then do an advanced restore of the Data only from the backup you should end up with Set CPU installed and set to run on boot.
Click to expand...
Click to collapse
sounds promising, ill give it a shot now, even if i was about to install it with stock right now
edit: i cant install the stock one, cause when i flash stock kernel chargemon doomlord provided for me i stuck on se logo
what strange is, that when i leave my phone alone it doesnt reboot, but till i use it a few seconds "reboot" 2-3 times, then im in system again and if i leave it "no reboot",
maybe someone can post how i can delete the following from system/bin/chargemon via pc, adb
Code:
umount /cache
umount /sdcard
umount /cdrom
umount /data/DxDrm/fuse
killall -9 DxDrmServerIpc
insmod /system/kernel/splboot.ko
sync
cat /system/kernel/miniloader > /proc/splboot/image
cat /system/kernel/boot.img > /proc/splboot/boot_img
echo > /proc/splboot/boot
tremendouz said:
i havent even time to install an app before i get wlod, so cant be setcpu
and i had the same with k005 cm7 rom, and with k006 on miui-formels 2.2,
thanks for thread, i read your pm just few min's ago
Click to expand...
Click to collapse
@tremedouz
Hi Bro,
Doomlord said you was having the same problems, i felt like giving up, no matter what i did the same outcome, anyway hopefully we can sort it out, let us know how you get on with set cpu.
GreatBigDog said:
Just a thought, it could be that your CPU can't handle the OC/UV of K006. Try doing a clean install with one of J's stock builds and then install set cpu on that. Configure set cpu to "On Demand", Max cpu to 998 and then enable "On Boot"
Boot into XRecovery, backup the ROM then flash J018. If you then do an advanced restore of the Data only from the backup you should end up with Set CPU installed and set to run on boot.
Click to expand...
Click to collapse
@Greatbigdog
Thanks for your advice, i have had a try of putting the setting to performence in cyanogen settings but it gave me cyanogen setting error message flashing up once the phone re-booted.
The thing is with vo17 stock my phone runs nice, i have flashed over that but got the same result, i have never tried setcpu, i will try your way later though and post back, thanks buddy.
guys some custom kernels (especially the ones ment for CM7) come with RAMDISKs integrated into the custom kernel and there is no seperate ramdisk available in /system...
so when u skip custom kernel booting the intended ramdisk is not executed and the necessary init scripts are never run... that could be the reason why some users (with CM7) are getting stuck when not using custom kernel for booting...
though the CM7 releases marked STOCK kernel should work... but even if those one are having the same issue then we need to search for another probable cause of the problem...
DooMLoRD said:
guys some custom kernels (especially the ones ment for CM7) come with RAMDISKs integrated into the custom kernel and there is no seperate ramdisk available in /system...
so when u skip custom kernel booting the intended ramdisk is not executed and the necessary init scripts are never run... that could be the reason why some users (with CM7) are getting stuck when not using custom kernel for booting...
though the CM7 releases marked STOCK kernel should work... but even if those one are having the same issue then we need to search for another probable cause of the problem...
Click to expand...
Click to collapse
Hi Doomlord,
I have ran both zips that either provided boot with custom kernal/boot with stock kernal, the last time i used the latter my phone never booted, could this have done something in my partition on my phone?, other than that is the ram disk you are talking about in system/bin ramdisk tar, if so i will have a look.
What about the solution using setcpu, i thought the idea was right thats why the screen switches off and does not when usb is connected.
EDIT... Ok just started testing with setcpu settings/add profile, still the same issue, will activating perflock disabler do any harm?
EDIT... maybe you are right about ramdisk as i have not got one showing in system/bin
EDIT... I have now stopped the phone re-booting by flashing the 2 zips below, custom kernal is now showing in my about phone the only thing is i have wifi error, at least i have got somewhere with cm7 v018, the thing is what has this added to my phone to stop the re-boots?
To get wifi working i have tried the following with no luck, using root explorer copy and pasted from update v018 the kernal,module folder and the chargemon, the phone is still stable though and no re-boots, hope somebody now can work out what is the problem.
Had this problem once when I had the v018 stable and Gapps installed.The phone reboot and the problem didn't come back afterwards
Ok Guys i have finally fixed my phone, i have just flashed j's v19 with custom kernel k007, as soon as the screen went off it went into re-boot mode, this time i flashed j's provided bb52 using the latest flash tool, you have to create a bundle first, i flashed this bb 4 times in a row without turning on the phone, just pull the battery out, i turned the phone on and 30 minutes now without 1 reboot, hope this helps those who have been having the same trouble.
I have the same problem. Created a flash file with Js baseband in the flash tool.
Flashed it, had this problem. Smartgardens says we should flash this several times, but i cant see how that has any effect tbh?!
superleeds27 said:
I have the same problem. Created a flash file with Js baseband in the flash tool.
Flashed it, had this problem. Smartgardens says we should flash this several times, but i cant see how that has any effect tbh?![/Q
Well why don't you try it and post back, whats the point in starting a thread to help if you don't help yourself, i could not use the custum kernal either, as soon as i fladhed v019 k007this morning i had the same problem as you, doing what i posted sorted it.
Click to expand...
Click to collapse
smartgardens said:
Right guy's,
I was asked to start this thread by Doomlord to see how many others are having problems flashing cm7 roms that contain the custom kernel.
When i flash the recent cm7 roms with k006 as soon as my screen times out or i switch it off with the power button(quick press)the phone goes into re-boot, it does not do it with the usb connected and my phone does not do it on any other rom even the cm7 that uses stock kernel.
I have tried everything i can think off to fix this issue from flashing repair with seus to using a brand new sdcard with just the cm7 update on to flash, i have run out of ideas, Doolord seems to think it is hardware related, please post if you are experiencing this problem, i am not concerned about wlod, this is a seperate problem.
When you post can you say which rom you have flashed and also which kernel, thanks in advance for your help, hopefully we can get this sorted.
Click to expand...
Click to collapse
you have to use the miniloader and the splboot.ko from z's incall volume fix kernel to fix that problem
How do we use it, where do we put it etc?
Hi, i have simple questions:
1 - How to change permanent cpu freq, if somebody reflash firmware, or kernel me need freq what i set.
2 - Can i change button combination to enter in download mode.
3 - Can i deny reflash my device?
1). I can't think of any sane reason for doing this, but just set the governor to have min and max frequency the same, also see 3).
2). No
3). No
TheSooth said:
Hi, i have simple questions:
1 - How to change permanent cpu freq, if somebody reflash firmware, or kernel me need freq what i set.
2 - Can i change button combination to enter in download mode.
3 - Can i deny reflash my device?
Click to expand...
Click to collapse
You can use Extweaks for siyah kernel, and xxtweaker for fluxi. When you set the cpu click the "set on boot" button. There's no way to permanently set the cpu after every flash though
Sent from my GT-I9100 using xda premium
But if somebody flash sammy, then the kernel will be overwritten by stock.
So I was playing with voltages, and by accident checked "set at boot",the pone froze, and had to restart it, but it freezes again at pin entry, before I can set them back to default.
How can I solve this? I would post on slim ics thread , but I dont have enough posts.
Ok,managed to fix by installing another kernel (I was using Siyah), but the problem persist once I go back to Siyah.
Where does it saves the undervolt configuration?
mierdaseca said:
Ok,managed to fix by installing another kernel (I was using Siyah), but the problem persist once I go back to Siyah.
Where does it saves the undervolt configuration?
Click to expand...
Click to collapse
If you used extweaks, go into Recovery Mode, there is an specially area for siyah kernel configuration. There you can erase the exTweaks configuration.
oz_90 said:
If you used extweaks, go into Recovery Mode, there is an specially area for siyah kernel configuration. There you can erase the exTweaks configuration.
Click to expand...
Click to collapse
Thanks,tried that,but didnt work.I changed the voltages from "ASS" (the Slim ICS configuration menu) ,not from Extweaks.
Using any kernel that supports voltage controls freezes
mierdaseca said:
Thanks,tried that,but didnt work.I changed the voltages from "ASS" (the Slim ICS configuration menu) ,not from Extweaks.
Using any kernel that supports voltage controls freezes
Click to expand...
Click to collapse
Try to enter recovery, wipe data, chache and dalvik. Then install another ROM. If you can't, maybe reinstalling the same rom can solve it.
Edit: the wipe data will erase all your apps and other stuff, but not photos or music.
Managed to fix it.
With a kernel that doesnt let you change voltages, I set the fovernor to performance.Then flashed Siyah again, and didnt freeze, so I could untick the "set at boot" voltages and fixed it.
mierdaseca said:
Managed to fix it.
With a kernel that doesnt let you change voltages, I set the fovernor to performance.Then flashed Siyah again, and didnt freeze, so I could untick the "set at boot" voltages and fixed it.
Click to expand...
Click to collapse
Thats good. Maybe right now you don't want to mess with voltages anymore jaja, but if you want it later you should visit this thread http://forum.xda-developers.com/showthread.php?t=1610044.
Remember to use the applications that are specially made for every kernel, and have an "emergency exit" if you mess up with something again.
Cheers.
Hey guys i think i ****ed up my cpu but i hope it isnt like that i installed agni pure stock kernel and kernel tuner app from play store. and i just miss clicked +12 volt for every mhz steps instead of -12 at cpu voltage. And now my phone complates the booting and i enter the sim code and drawing to model for unlock and ops it freeze and restarts after a while. i am using and ver. 4.3.3 and usin xxbugnl1 the lastest release for sgs3. Is there any way to recover my phone guys i really need your help
EDIT: i just used the zip file for reset voltages in here
and removed kernel tuner before it gains root rights it seems everythink ok now
Flash full stock firmware then factory reset, if still the same then yes you have fried the hardware.
boomboomer said:
Flash full stock firmware then factory reset, if still the same then yes you have fried the hardware.
Click to expand...
Click to collapse
Thanks bro i think it was too close to burn out my CPU but i was just lucky i guess I used the link that i mentioned on my edit. It really helped me. Thanks anyway