Is there a Kernel that is not OC for CM7?
it does not come oc'd at stock.
912MHZ is the default max scaling clock.
kernel does not OC unless set by user after install. Correct?
Correct.
1ghz max is default with latest kernel.
i am getting piss poor result on my tablet. after nvflash then cm7 is getting 13xx and 15xx and most of the other time it would give me "service called failed" even tho it is connected. is it possible nvflash did not remove the kernel? what would i need to flash to bring it back to "normal"?
Flash the latest kernel. This corrects a bug with cpu1 not hotplugging properly. Not contained in the latest nightly as of yet.
Related
I was running dag 0.2 and was overclocking fine, and decided to install saurom.
wiped caches-->factory reset-->install saurom+fixes-->restore TB backup-->setcpu has 1.5ghz as max, with no higher options as before. cpuspy reports that it's dag0.2 loaded, but I can't overclock.
I tried CWM installing the dag 0.2 kernel but it didn't help. am I missing a step?? i assumed that dag 0.2 overclock was included in the ROM.
Strange..so I installed System Tuner to try and it had higher Ghz options, and I overclocked to 1.83. Went back to setCPU and it was able to overclock! I just uninstalled systemtuner and can now use setCPU properly. Any ideas as to why it thought 1.5ghz was the max before??
Ok I tried some new roms and started noticing a pattern in that BLN was behaving erratic.
By erratic I mean this.
If I set the LED's to stay on, they will turn on but then raondomly go off for a second or so and then come back on again, there was no pattern except it took longer to happen after a phone reboot and when the usb plugged in from pc.
If I set them to blink and I set the off period for longer than 4 seconds, then after they go off for the first or send time then after just 1 second they come back on again but only if I set the off to more than 4 seconds, weird.
In these cases was testing on freshly installed roms with wiped user data.
One of the roms was based on stock which made this even stranger as BLN works 100% perfect on stock rom with cf-root, the rom was based on cf-root b84 so I chanced it to downgrade it to cf-root b82 and bam BLN fixed.
So the issue is down to a fubar kernel.
Now CM's stock rom doesnt support BLN, so on the CM roms I was using the blackhawk rom which has the exact same symptons as cf-root b84, seems only cf-root b82 works properly.
Here is the changelog for cf-root b83 and b84.
CF-Root-S5830-v3.7-b84.zip (12.55 MB)
BUGFIX: Invisible boot animation.
Install CF-Root-S5830-v3.7-b84.zip via "CWM recovery" first and then install b84-fixed.zip via "CWM Manager - Flash kernel"!
CF-Root-S5830-v3.7-b83.zip (12.38 MB)
- Untested since on CyanogenMod 7.2 firmware for now
- Using b82 recovery image
- CPU and system bus overclock enabled
- GPU driver backported from 2.6.35-11 kernel source
- interactive, interactiveX, smart*ss, and smart*ssV2 governor
- Samsung on the fly governor setting disabled
- WiFi driver taken from DXKPD
Click to expand...
Click to collapse
I dont have b83 but am about to flash mythICS which is based on b83, my gut guess is the bug was introduced in b83 as b84 only has a tiny changelog.
What I am asking is if someone can either do me a kernel for CM based on the above information (so dont include new GP driver, dont disable on the fly governor, dnt add new wifi driver) and see if the result is a fixed kernel, or if anyone has instructions on how to build my own kernel based on CM's sources.
I dont really need a new kernel for stock based roms as I can just downgrade to b82 cf-root to fix them.
Also is this better in dev section or here?
confirmed b83 is indeed borked and b82 also fixed on mythICS.
So I need a b82 for CM
I am on hellybean 12/24 my CPU gets stock at 1000 when I use an app for a while is there a fix. I am on stock kernel with ondemand
As title suggests, there is a wierd (and Very annoying, since it forces me to use a while loop in a script to stick back to interactive) function in my kernel, which forces the CPU governor into ondemand every time screen-on/off occurs
Phone: Acer Liquid Glow E330
Kernel: all, this thing applies to stock, vache's, and lupohirp's kernel
PrintK says something about a str_governor variable (set to ondemand) which by circumstances gotta be the default governor
Any clues? Ideas?
Sent from my scytheaxe
SuicideFlasher said:
As title suggests, there is a wierd (and Very annoying, since it forces me to use a while loop in a script to stick back to interactive) function in my kernel, which forces the CPU governor into ondemand every time screen-on/off occurs
Phone: Acer Liquid Glow E330
Kernel: all, this thing applies to stock, vache's, and lupohirp's kernel
PrintK says something about a str_governor variable (set to ondemand) which by circumstances gotta be the default governor
Any clues? Ideas?
Sent from my scytheaxe
Click to expand...
Click to collapse
I never encounter such issue before, maybe you can change the kernal.
angelamar90 said:
I never encounter such issue before, maybe you can change the kernal.
Click to expand...
Click to collapse
Already tried vache's kernel and lupo's kernel, also tried to mod the stock boot.img to no avail. The issue is not in the ramdisk
Sent from my scytheaxe
Hello. I instal Asgard v1.5 Kernels on Fulmics ROM 1.0.
All stock, no other mod, clear cache and art, but all core stay on max value and vpu temp its 80C.
This is on all gov, only poversave work normal. Anyone's have this problem? Any sugest?
Aha, when restore stock boot in twrp its work normal.
Sorry for my bsd en.