When I load the latest cyanogenmod nightly and flash the ktmanta 4.4 kernel upon setup I get error android phone something has stopped responding in all the other ROMs such as omni it doesn't do that.
If anyone has a solution please tell
zachdees said:
When I load the latest cyanogenmod nightly and flash the ktmanta 4.4 kernel upon setup I get error android phone something has stopped responding in all the other ROMs such as omni it doesn't do that.
If anyone has a solution please tell
Click to expand...
Click to collapse
There have been some changes in the CM ramdisk, This is mostly the cause of your issues....
Thx Josh
lj50036 said:
There have been some changes in the CM ramdisk, This is mostly the cause of your issues....
Thx Josh
Click to expand...
Click to collapse
Is there a fix ktmanta is the only kernel that has undervolting I've tried every kernel and not one except this one has undervolting I'm on omni ROM currently which sucks because when I apply voltage or clock settings they don't stick they reset to default
zachdees said:
Is there a fix ktmanta is the only kernel that has undervolting I've tried every kernel and not one except this one has undervolting I'm on omni ROM currently which sucks because when I apply voltage or clock settings they don't stick they reset to default
Click to expand...
Click to collapse
The solution would be to repack the boot.img with the updated ramdisk from CM... To get a new boot.img and flash it and see what it does..
Just a FYI
Kernel + ramdisk = boot.img
If you get me this kernel you are flashing I could make you a new boot.img...
Let me know
Thx Josh
lj50036 said:
The solution would be to repack the boot.img with the updated ramdisk from CM... To get a new boot.img and flash it and see what it does..
Just a FYI
Kernel + ramdisk = boot.img
If you get me this kernel you are flashing I could make you a new boot.img...
Let me know
Thx Josh
Click to expand...
Click to collapse
It's the latest ktmantsn4.4.2 kernel over in mantas thread
Related
I was wondering about the overclocking kernal for cm7. just how do i put it in. Do I have to do that when I first install or can I add it later. also does it really help. I mean is the difference really noticeable or not at all. I am still deciding if I should do it or not.
Kernels are flashed through ClockworkMod and can be flash anytime after you flash a rom. If you use the search bar you can easily find what particular kernel works for your setup.
OK, I think I found the right one but I was also wondering if I could install it when I first installed cm7. When I installed it I saw that it was searching for the kernel and for gapps but didn't find the n and skipped it. Could I install it then
chad11 said:
OK, I think I found the right one but I was also wondering if I could install it when I first installed cm7. When I installed it I saw that it was searching for the kernel and for gapps but didn't find the n and skipped it. Could I install it then
Click to expand...
Click to collapse
CM7 has the ability to be overclocked as it sets.
settings > CM settings > performance > CPU settings.
just be extremely careful when Overclocking devices. it can takes it's toll in the long run.
and the g/apps are not kernel dependent they are ROM dependent.
OK but what do you mean by gapps are not kernal dependant
chad11 said:
OK but what do you mean by gapps are not kernal dependant
Click to expand...
Click to collapse
On *UNIX based devices. They have a section of the firmware called the "kernel". The kernel accepts the coding, binary and scripts from the RAM/ROM and tells the hardware how to act, what to do, and when to do it.
The g/apps have nothing to do with the kernel.
The g/apps are Google's property and cannot be included in AOSP based ROMs. Those ROMs are developed from Google's code. And developers do not have the ability to add those at will. So we must flash them after/prior (depending on he ROM) to get the Google Apps.
YES! DO IT!
for me its like day and night, it so much smoother with dals OC kernel. and yes you can flash the OC kernel any time. you can flash cm7 rc1 then OC kernel in the same boot. or you can first install cm7 to check it out for a while and then later flash the new kernel. if you planning to flash dal's 6/18 kernel, make sure to get his app NC Tweaks.
NC Tweaks here:
http://forum.xda-developers.com/showthread.php?t=1104039
Dal's Kernel here:
http://forum.xda-developers.com/showthread.php?t=925451
thanks. What I want to know is how to flash it. do I do it the same way as gapps( have wifi and reboot in recovery mode) or is there a different way?
chad11 said:
thanks. What I want to know is how to flash it. do I do it the same way as gapps( have wifi and reboot in recovery mode) or is there a different way?
Click to expand...
Click to collapse
You place the over clock zip file in the root of your sd card and flash it through cwm like you would a rom or gapps. So for example you would flash cm7 then gapps then the overclock kernel.
Not to Jack this thread, but I want to update from cm7 old kernel to New nightly build. Does the new kernel flash with the nightly?
Sent from my Optimized Shift using XDA App
JeramyEggs said:
Not to Jack this thread, but I want to update from cm7 old kernel to New nightly build. Does the new kernel flash with the nightly?
Sent from my Optimized Shift using XDA App
Click to expand...
Click to collapse
When you move from stable cm7 to cm7 nightly the new kernel is included. However the included kernel is overclockable only to 975mhz. If you want a higher clock speed you'll have to use dals 6182011 kernel, up to 1200mhz.
whats is cmw?
chad11 said:
whats is cmw?
Click to expand...
Click to collapse
it's actually CWM.
ClockWork Manager
basically boot into recovery then flash.
OK. but this may be a stupid question but will the cm7 kernal work with the stable version7.0.3 because that is what I have.
chad11 said:
OK. but this may be a stupid question but will the cm7 kernel work with the stable version7.0.3 because that is what I have.
Click to expand...
Click to collapse
I'm not following you cannot use just a Cyanogen(mod) kernel. They are built into their ROMs.
chad11 said:
OK. but this may be a stupid question but will the cm7 kernal work with the stable version7.0.3 because that is what I have.
Click to expand...
Click to collapse
sorry, but no. dal's 6/18 OC kernel will not work with 7.0.3....
...just flash n118 and you'll be fine
Ok thanks anyway. do you know when the kernal will work with a stable version
chad11 said:
Ok thanks anyway. do you know when the kernal will work with a stable version
Click to expand...
Click to collapse
The latest nightly should be considered stable. It is in release candidate stable for the next stable build. The next stable build should be released in the next couple of days.
neidlinger said:
it's actually CWM.
ClockWork Manager
basically boot into recovery then flash.
Click to expand...
Click to collapse
No--It's- Clock Work Mod Recovery
CWMR ;^}
Jimbo67 said:
No--It's- Clock Work Mod Recovery
CWMR ;^}
Click to expand...
Click to collapse
There is a Clockwork ROM Manager and a ClockworkMod Recovery image.
Together they are known as "CWM" Since one is a recovery and the other is a ROM manager.
Do you feel the CM10 917+ Builds are less buttery or more choppy... It is due to a change in the CM source that removes VSYNC and replaces it with IOCTL that is much more power efficient.! Anyway if you want the smoothness over power until CM fixes it...
Flash this pack to revert the changes to the VSYNC.! [works with 917&918]
PS: Make sure you flash Either CM10 914 Kernel or Semaphore 2.1.0/2.1.0s or Devil before 917 , else you will have a black screen, after flashing the pack as they require kernel change.!
PS: New NOMUTEX Patch by pawitp. Download.! [Flash in Recovery. No need for kernel changes.]
ok, good to know there is a workaround for when the latest flashed cm10 is lagging, thx for that!
one question though: you only write cm10kernel or semaphore, is it not possible to use this with devil-kernel?
EDIT: 1.4.1 of DerTeufel's jellybean-kernel should work, too, shouldn't it?
it was made before the vsync-change and it is a kernel for cm10.
or is there any specific reason why devil-kernel not works for this?
EDIT2: ok, i just saw your edit right now, thx!
so everybody that wants to use cm10 WITHOUT the new vsync-change WITH devil-kernel should flash version 1.4.1 of it after flashing this mod.
greetz n thx,
sUsH
Is hellybean using VSYNC or IOCTL (knowing that devil kernel is vsync)
exadeci said:
Is hellybean using VSYNC or IOCTL (knowing that devil kernel is vsync)
Click to expand...
Click to collapse
Yes the latest version is.
yeah i experience the same problem
after flashing back to 9/14
all problem gone
I think there's bug in 17and 18 version
I read from the thread that the 918 build solves the problem... Don't quote me on this though.
so for the NOMUTEX-patch-thing it is NOT necessary to flash an older kernel, is that right?
greetz,
sUsH
Thanks nice that someone works on it!
Sent from my GT-I9000 using xda premium
sUsH667 said:
so for the NOMUTEX-patch-thing it is NOT necessary to flash an older kernel, is that right?
Click to expand...
Click to collapse
Nope kernel mod not required.
sUsH667 said:
so for the NOMUTEX-patch-thing it is NOT necessary to flash an older kernel, is that right?
greetz,
sUsH
Click to expand...
Click to collapse
mnazim said:
Nope kernel mod not required.
Click to expand...
Click to collapse
ah, ok, i get it, no kernel mod required cause there is a kernel included that gets flashed when using this zip...
so i better ask again:
can this new patch be used with other kernels?
and since there is a kernel included, the way would be
1. flash rom
2. flash patch
3. flash wished kernel
is that right?
EDIT: any idea what the patch.diff in the flashable is good for?
thx for clarification!
greetz,
sUsH
mnazim said:
Yes the latest version is.
Click to expand...
Click to collapse
What is IOCTL ?
sUsH667 said:
EDIT: any idea what the patch.diff in the flashable is good for?
Click to expand...
Click to collapse
I believe IOCTL will hold a lock on the framebuffer that is released only during the next vsync. this is the reason for microlags.
Read more Here.
AlwaysDroid said:
What is IOCTL ?
Click to expand...
Click to collapse
IOCTL is Input Output Control. It is a specific system call/api that does i/o operations in the system.
Read More.!
Simple question... How can I overclock this device?
I am currently running latest cm10 from nightly and I cannot overclock it probably because of the kernel....
Any suggestions/ideas about this issue will be gladly appreciated
*bump* I need a solution for overclocking this, someone, please post something!
If there is no custom kernel available for your device you probably are not going to overclock it for now.
Berat1337 said:
*bump* I need a solution for overclocking this, someone, please post something!
Click to expand...
Click to collapse
The following kernel for overcl... should work with cm build 7 and also for latest cm build...:
purity kernel
Don´t forget to make a backup before installing the kernel ...remember ..everything at your own risk ...
phreephiber said:
The following kernel for overcl... should work with cm build 7 and also for latest cm build...:
purity kernel
Don´t forget to make a backup before installing the kernel ...remember ..everything at your own risk ...
Click to expand...
Click to collapse
yep, i know.... didn't want to create a custom kernel since i dont have much info about the tolerance of the actual clock value... so thanks for your info...
It seems on pretty much any rom with a custom kernel breaks my camera. When I focus it goes all screwy and crashes. Changing the GPU govenor dosent help. Any ideas how to stop this? Even on JWR with a JWR kernel it happens. Im stuck using stock 4.2.2 with stock kernel because it kills my camera.
bandit97 said:
It seems on pretty much any rom with a custom kernel breaks my camera. When I focus it goes all screwy and crashes. Changing the GPU govenor dosent help. Any ideas how to stop this? Even on JWR with a JWR kernel it happens. Im stuck using stock 4.2.2 with stock kernel because it kills my camera.
Click to expand...
Click to collapse
wait wait! are you using JWR or JSS on a 4.2.2 rom?
update to 4.3 and when you get it now flash a kernel JWR if you are in stock rom if not and you are using Carbon rom, Rasbeanjelly,Cyanogenmod use JSS (JLS now) if you are on Paranoid , PSX , Purity flash JWR kernel then.
this should be fix your problem on camera!
alvin182 said:
wait wait! are you using JWR or JSS on a 4.2.2 rom?
update to 4.3 and when you get it now flash a kernel JWR if you are in stock rom if not and you are using Carbon rom, Rasbeanjelly,Cyanogenmod use JSS (JLS now) if you are on Paranoid , PSX , Purity flash JWR kernel then.
this should be fix your problem on camera!
Click to expand...
Click to collapse
Lol. I know. I was just saying even if I use a kernel written for specifically JWR on JWR it still bug's. Basically any kernel with any rom other than stock breaks my camera. Im aware about the different kernel and rom types.
bandit97 said:
Lol. I know. I was just saying even if I use a kernel written for specifically JWR on JWR it still bug's. Basically any kernel with any rom other than stock breaks my camera. Im aware about the different kernel and rom types.
Click to expand...
Click to collapse
sorry man i understood you were on a 4.2.2 rom sorry.
have you ever made a full flash factory image? maybe you need reset all via userdata .
just try sometimes i do this!
I wanna run these two together but when I install Franco it messes up the screen color....
Plz help
robbieast said:
I wanna run these two together but when I install Franco it messes up the screen color....
Plz help
Click to expand...
Click to collapse
youre mistaken, its not franco kernel that messes up your screen color, its your cm10.2 nightly.
cm xhanged its sourse from aosp to qualcomm, so running any asop kernel in cm will give you that effect. only cm based custom kernels will be fine. theres a temporary flashable fix for this floating around, if it still works that is.
robbieast said:
I wanna run these two together but when I install Franco it messes up the screen color....
Plz help
Click to expand...
Click to collapse
Yes lately cm is causing some color problems.
Here is the colorfix zip file flash this in recovery and also use a JSS kernel AFAIK cm needs a JSS kernel'
COLORFIX zip : DOWNLOAD
Press thanks if I helped you.
how about CM11.. is there any colorfix available yet?
i flashed CM10 colorfix for the 4.4.X based CM11 variant but seems it'll restart the session after the boot animation