Related
Hi, as the topic states, does anyone know where i can download one and flash? my setup on my sig is current.
thanks
So you're trying to run the official kernel with a custom ROM? Why?
why not? and what prevents me from running an official kernel? to OC and drain my batteries? other than that, what else?
edit/
what may keep me from using an official kernel is the 15MB additional ram. however i was under the impression that if I had radio 2.22.27.08, and H-Boot 1.33.0013(d), it doesnt limit me from using any of the froyo kernels floating around. if im incorrect with my assumptions, can someone enlighten me?
nomadman said:
why not? and what prevents me from running an official kernel? to OC and drain my batteries? other than that, what else?
Click to expand...
Click to collapse
Because you can't OC is probably the main reason. The only other one I can think of is the random battery drain that some kernels experience.
On the plus side I can think of stability and battery life. Knock yourself out, I'm sure someone can post it for you.
I have the zip file for the 2.2 OTA but I have no idea where to find the kernel.
Here's a link. - http://www.filedropper.com/update3-e3671133717dsigned-opal-frg83-from-dmd64e3671133
Phateless said:
Because you can't OC is probably the main reason. The only other one I can think of is the random battery drain that some kernels experience.
On the plus side I can think of stability and battery life. Knock yourself out, I'm sure someone can post it for you.
I have the zip file for the 2.2 OTA but I have no idea where to find the kernel.
Here's a link to my dropbox. - http://db.tt/XHrvInZ
Click to expand...
Click to collapse
IMO, the current ROm im using (TheOfficial) is working wonderfully. I care less about overclocking since I don't play games and dont find the need for the applications I use to be overclocked. Also the UI response on the ROM is incredible.
You are right, until the other ROMs iron out the random battery drain, which I have experiences in both CM7 and pershoot kernels, i wont be using them because i do not like having to restart the phone every time after i charge. ezterry's current kernel always gives me the green screen. however, ez's older kernel doesn't, but I prefer running the latest unmodified kernel.
I'm satisfied using a non-oc kernel and would rather set the mim clock freq. to ~177.
Makes sense. If you can figure out how to extract the kernel from that zip I linked you to, you should have your kernel.
Phateless said:
Makes sense. If you can figure out how to extract the kernel from that zip I linked you to, you should have your kernel.
Click to expand...
Click to collapse
lol, thats my problem. I don't. I also have athe official OTA Froyo image for mt3g. but i have no idea how to extract and apply it to the current OS. Thanks for the offer though. i'll try to find a way to do it. was just hoping someone had a flashable official kernel laying around they'de like to share.
I hit a brick wall. I guess i'll just stick with ezBiffTestKernel20101106-2708_S based on kernel 2.6.34.7. It's a bit old but it will suffice until i figure it out. At least I don't have to reboot every time I pull from the USB charger.
/edit
Btw, can anyhone remember that the OTA kernel version was?
nomadman said:
I hit a brick wall. I guess i'll just stick with ezBiffTestKernel20101106-2708_S based on kernel 2.6.34.7. It's a bit old but it will suffice until i figure it out. At least I don't have to reboot every time I pull from the USB charger.
/edit
Btw, can anyhone remember that the OTA kernel version was?
Click to expand...
Click to collapse
Naw but you could always nandroid back to stock and look. If I could figure out how to delete my google account info from my nandroids I'd email one to you. I still have a few from my mt3g.
Phateless said:
Naw but you could always nandroid back to stock and look. If I could figure out how to delete my google account info from my nandroids I'd email one to you. I still have a few from my mt3g.
Click to expand...
Click to collapse
thats ok dude. too much trouble on your part. gonna try out koush-AnyKernel-a09a6f1 or dsixda_Android_Kitchen_0.113 and see what i come up with. (fish'in). and im sure there's a ROM out there that doesnt have a modified kernel i can extract from. Just cant figure out how to get it from the offical OTA archive
nomadman said:
thats ok dude. too much trouble on your part. gonna try out koush-AnyKernel-a09a6f1 or dsixda_Android_Kitchen_0.113 and see what i come up with. (fish'in). and im sure there's a ROM out there that doesnt have a modified kernel i can extract from. Just cant figure out how to get it from the offical OTA archive
Click to expand...
Click to collapse
Actually there might be a legal copyright issue with distributing oem kernels in custom ROMs. I don't know for sure though.
Shouldn't been since the kernel code is open source, but I'm not sure either. I did find a guide to extracting kernel's from ROM's but it requires that you are either running Linux or are running Linux in a virtual environment.
Phateless said:
Actually there might be a legal copyright issue with distributing oem kernels in custom ROMs. I don't know for sure though.
Click to expand...
Click to collapse
The kernel is open source. I dont think i have a problem there. Its gapps that we can not redistribute. i read that from CM forum.
DonJuan692006 said:
...I did find a guide to extracting kernel's from ROM's but it requires that you are either running Linux or are running Linux in a virtual environment.
Click to expand...
Click to collapse
thanks! if u can find the link again, i'd be grateful. im on a unix (Mac) environment, so i might be able to do it. if not on Mac, I already have vmware fusion installed and its not a problem slapping on the latest Ubuntu.
I did find a how-to on CM wiki that required a boot.img and fastboot to flash. also found one requiring zimage from a rom. but i could not find the zimage file from the TMO Froyo OTA. lol.
Here's what I was reading. Which is doing the boot.img method.
DonJuan692006 said:
Here's what I was reading. Which is doing the boot.img method.
Click to expand...
Click to collapse
nice! androidcentral was down for maintenance the whole time i was researching yesterday. thanks for the link!
nomadman said:
edit/
what may keep me from using an official kernel is the 15MB additional ram. however i was under the impression that if I had radio 2.22.27.08, and H-Boot 1.33.0013(d), it doesnt limit me from using any of the froyo kernels floating around. if im incorrect with my assumptions, can someone enlighten me?
Click to expand...
Click to collapse
Glad I happened to go back a page...
The official kernel is meant to go with 0013 and 28.25 so yes, you should still have the additional RAM, which this phone desperately needs.
2.6.32.9-g94b855e
[email protected]#1 is what my phone says and I just received the OTA update a few days ago. Hope this is what you were looking for!
I've been trying to figure this out all day. I actually have a linux installation already but none of the download links for the perl files work. If you have them please upload them somewhere and I'll make us a flashable AnyKernel update.zip.
I've been trying to follow this guide: http://forum.xda-developers.com/showthread.php?t=667923 but none of the android-dls.com links work
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.
Hello all,
i have been an owner of a nexus s gsm s-lcd since August 2011 and i have been experimenting mostly with cyanogenmod and cyanogenmod based roms such as nscollab.
Using my phone mainly for my jobs, since the beginning of the usage of non official roms, i am always having stability problems ending up not trusting my phone for everyday use.
I have tried cyanogenmod stable, rc, lots of nightly builds and various nscollab versions from 1.0.39.
From my experience so far, except when using matr1x 5.5 cfs i always have some of the following problems, some times some of them and sometimes all of them:
1. reboots
2. reboots with no ability to load the os, with only solution the removal of battery
3. crashes with the result of the pin needed to be given again
4. never waking up after deep sleep
The kernels i have used so far are all the matr1x cfs(sorry, i do not trust con Kolivas and his bfs, being a linux user for 10 years), various netarchy and the stock cyanogenmod .
The only kernel that has been stable for me until now is matr1x 5.5 cfs.
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
The first thing I though having all these problems is that the main cause of them would be the undervolting that all most of the kernels have. After some tests i realized that with the voltages that proton suggests or even with the stock voltages, the problems do not disappear.
Although, i have found my stable kernel and i always flash matr1x 5.5 cfs in all the roms i use, i would really like to know what is the usual suspect of all these problems. Is there any possibility that some of them are not kernel related and the cause is in the source code of cyanogenmod?
To sum up, i really believe that we should try an effort to create a kernel that is very close to the stock one, and be very careful with the extra modules that we add. Although i do not have the experience of making a kernel package for android, i will try for sure to make a flashable kernel for my needs, and if it's stable i will upload it and share with all of you.
I believe that every mobile has to be bug-free(as possible), and reliable for everyday use and at least i should be reboot-free.
I would really like to read other users experience and opinions.
Regards,
Michael
it was the same for me. nscollab was unusable since it was always freezing in two minutes after boot. changing the kernel did not help. so I decided to change the rom to Nexus MV 10.05. it works very stable (not a single reboot or freeze) and faster than nscollab.
mikkkg said:
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
Click to expand...
Click to collapse
Well, I found that custom kernels can work with stock ROM's. I'm using stock Google 2.3.6 on my 9023 + pete's kernel with Voodoo sound and BLN. Stable as ****, practically no issues, I'm happy with my NS as never before just because of the lack of constant flashing the **** around to "optimize". It just works flawlessly.
Here's the link to the kernel : http://www.peteralfonso.com/2011/08/download-nexus-s-263514-kernel.html
Had the no wake issue with cm7 216 and nscol 1.4.5. On nscol 1.4.6 and no problems yet. If it happens again it would seem to be a cm7 issue. While annoying devs are constantly hunting down and correcting problems, just the way it is and doesn't bother me.
Sent from my Nexus S using xda premium
Jeez loueeeeze
Just use nscollab .46 because that has stock voltages and you should be fine
Sent from my Nexus S using XDA App
The hole point for me is not using any other kernel but the stock one.. compile yourself a nexus s kernel (google it for how to) and be happy without any reboot, crash..
baterry? normally 1.5 days @ 1.0ghz..
You could do that as well
Sent from my HTC Sensation 4G using XDA App
mathkid95 said:
Jeez loueeeeze
Just use nscollab .46 because that has stock voltages and you should be fine
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
.45 with stock voltages caused the "pin asking" issue even with stock voltages(even with 5.5 cfs - maybe a cyanogen problem?), so that's why i am stuck at .42 with 5.5 cfs and did not even try .46.
Try .46 and lemme know
Sent from my HTC Sensation 4G using XDA App
mathkid95 said:
Try .46 and lemme know
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
If you see, in the thread of nscollab, there are also problems with the phone dying etc, even with the new stable cyanogenmod + matr1x kernel.
I only do tests in my mobile during the weekend, because i use it all week for my job. So stuck with matr1x 5.5 until i see a really stable matr1x kernel coming after 8.
madd0g said:
Here's the link to the kernel :
Click to expand...
Click to collapse
Thank you very much for posting this link. I did not know that kernel. I just found some time to flash nscollab .50 with this kernel and i only changed interactive governor with ondemand to be even closer to stock kernel.
I hope that it is as stable as it is for you.
After some hours with this new kernel, i am not sure about stability(although it seems stable) but nexus is running smoothier than ever.
I've used ondemand from the beginning I started using this kernel, then I tried interactive (default) just to try it out. Not really a difference, same stability/speed and I could get rid of NoFrillsCPU app setting the default governor at startup. So to wrap up, kernel runs beautiful from the start, no extra fiddling necessary.
I do not believe the issues described in the OP are kernel related. They persist in all custom kernels. I think it is from Dalvik VM crash but I have no proof.
Sent from my Nexus S using XDA App
http://forum.xda-developers.com/showthread.php?t=959282&page=309
As I read here I am not alone in the problems described, and after lots and lots of tests i am sure that this is a matr1x specific issue.
So, as i do not have permission to write in a development thread yet, I suggest the following:
1. if the developer of nscollab wants to continue with Matr1x kernels, makes a new release with the last well known stable kernel, which is Matr1x 5.5 until Matr1x developer finds out what is the problem with the new kernels.
2. Matr1x is replaced with another kernel, such as Peter Alfonso's kernel(running FINE for 24 hours. In the same period with Matr1x kernels i would have at least 2-3 problems- 5.5 cfs excluded).
EDIT:
I just got the first "dead phone" issue with alfonso kernel. I should be more patient about stability results of this kernel, or this issue is not kernel related.
After many days of testing with nscollab and different kernels, i am sure that the major problem of "dead phone" is not kernel related but a cyanogenmod issue.
The most stable kernel i tried was Peter Alfonso, but after 4 days of use the issue appeared.
As i need a really stable rom, before going back to stock, i am testing Oxygen 2.3.1, which i do not know yet if it's stable(i hope) but until now is the fastest and smoothest experience.
Id say if you want stability, stay on stock, extra features like BLN and Voodoo sound are added via kernel anyway.
Sent from my Nexus S using Tapatalk
mikkkg said:
After many days of testing with nscollab and different kernels, i am sure that the major problem of "dead phone" is not kernel related but a cyanogenmod issue.
The most stable kernel i tried was Peter Alfonso, but after 4 days of use the issue appeared.
As i need a really stable rom, before going back to stock, i am testing Oxygen 2.3.1, which i do not know yet if it's stable(i hope) but until now is the fastest and smoothest experience.
Click to expand...
Click to collapse
Kalimocho found a kernel error and a missing vendor file in the CM kernel. It will be fixed in the next nightly. The hope is that this was the cause of the freezes/reboots/bootloops/dimscreen bootloops that people were seeing.
mikkkg said:
Hello all,
i have been an owner of a nexus s gsm s-lcd since August 2011 and i have been experimenting mostly with cyanogenmod and cyanogenmod based roms such as nscollab.
Using my phone mainly for my jobs, since the beginning of the usage of non official roms, i am always having stability problems ending up not trusting my phone for everyday use.
I have tried cyanogenmod stable, rc, lots of nightly builds and various nscollab versions from 1.0.39.
From my experience so far, except when using matr1x 5.5 cfs i always have some of the following problems, some times some of them and sometimes all of them:
1. reboots
2. reboots with no ability to load the os, with only solution the removal of battery
3. crashes with the result of the pin needed to be given again
4. never waking up after deep sleep
The kernels i have used so far are all the matr1x cfs(sorry, i do not trust con Kolivas and his bfs, being a linux user for 10 years), various netarchy and the stock cyanogenmod .
The only kernel that has been stable for me until now is matr1x 5.5 cfs.
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
The first thing I though having all these problems is that the main cause of them would be the undervolting that all most of the kernels have. After some tests i realized that with the voltages that proton suggests or even with the stock voltages, the problems do not disappear.
Although, i have found my stable kernel and i always flash matr1x 5.5 cfs in all the roms i use, i would really like to know what is the usual suspect of all these problems. Is there any possibility that some of them are not kernel related and the cause is in the source code of cyanogenmod?
To sum up, i really believe that we should try an effort to create a kernel that is very close to the stock one, and be very careful with the extra modules that we add. Although i do not have the experience of making a kernel package for android, i will try for sure to make a flashable kernel for my needs, and if it's stable i will upload it and share with all of you.
I believe that every mobile has to be bug-free(as possible), and reliable for everyday use and at least i should be reboot-free.
I would really like to read other users experience and opinions.
Regards,
Michael
Click to expand...
Click to collapse
I use this, if it helps you.
Thread here.
mikkkg said:
http://forum.xda-developers.com/showthread.php?t=959282&page=309
As I read here I am not alone in the problems described, and after lots and lots of tests i am sure that this is a matr1x specific issue.
So, as i do not have permission to write in a development thread yet, I suggest the following:
1. if the developer of nscollab wants to continue with Matr1x kernels, makes a new release with the last well known stable kernel, which is Matr1x 5.5 until Matr1x developer finds out what is the problem with the new kernels.
2. Matr1x is replaced with another kernel, such as Peter Alfonso's kernel(running FINE for 24 hours. In the same period with Matr1x kernels i would have at least 2-3 problems- 5.5 cfs excluded).
EDIT:
I just got the first "dead phone" issue with alfonso kernel. I should be more patient about stability results of this kernel, or this issue is not kernel related.
Click to expand...
Click to collapse
lol i keep looking but i dont find anything
ahhhh
can someone list which kernels work with the 0.014 ICS update for the a500? im sick of the stock kernel that came with cm9, i believe and want to flash another one.
my tabs unlocked, cm9 installed, but is laggy so i think OC'ing it may help a tad.
ty in advanced as im new to the world of flashing kernels
ztotherad said:
can someone list which kernels work with the 0.014 ICS update for the a500? im sick of the stock kernel that came with cm9, i believe and want to flash another one.
my tabs unlocked, cm9 installed, but is laggy so i think OC'ing it may help a tad.
ty in advanced as im new to the world of flashing kernels
Click to expand...
Click to collapse
Currently, there are no known OC/UV kernels for the 500/501 running ICS. With the exception of TegraOwners, however it only works with the Tegraowner rom as best I know.
Moscow Desire said:
Currently, there are no known OC/UV kernels for the 500/501 running ICS. With the exception of TegraOwners, however it only works with the Tegraowner rom as best I know.
Click to expand...
Click to collapse
damn, i was hoping there was a kernel out there.. is it possible to take a kernel from another tegra2 device & flash it to the a500?
thank you btw for all your answers to my possible ridiculous questions!
ztotherad said:
damn, i was hoping there was a kernel out there.. is it possible to take a kernel from another tegra2 device & flash it to the a500?
thank you btw for all your answers to my possible ridiculous questions!
Click to expand...
Click to collapse
Look in my thread , they are not OC kernels , the tweaked ones but they improve smoothness big time.
One thing they are build for 1.031.00 based rom , they will work on older versions but it is possible that camera fails.
I want to know if I need to install a custom rom or a custom kernel or a combination of both so that I can overclock my phone(1ghz single core). Please help. Why is everybody so silent here, so unwilling to answer a simple question as this. My fourth post of the same question.
todopertin said:
I want to know if I need to install a custom rom or a custom kernel or a combination of both so that I can overclock my phone(1ghz single core). Please help. Why is everybody so silent here, so unwilling to answer a simple question as this. My fourth post of the same question.
Click to expand...
Click to collapse
Any custom ROM that comes packaged with an included kernel should allow you to overclock. AFAIK the oveclocking capability lies within the kernel (at least with Xperias this is the case) . At the least, a stock ROM with a custom kernel and a CPU/Performance app will give you overclocking options.
My suggestion though is to get a ROM like PAC, that comes with a kernel and the needed app to manage your CPU settings.
Langes said:
Any custom ROM that comes packaged with an included kernel should allow you to overclock. AFAIK the oveclocking capability lies within the kernel (at least with Xperias this is the case) . At the least, a stock ROM with a custom kernel and a CPU/Performance app will give you overclocking options.
My suggestion though is to get a ROM like PAC, that comes with a kernel and the needed app to manage your CPU settings.
Click to expand...
Click to collapse
That is not fully correct.
Most PAC builds use the stock CM kernel. Our ROM offers performance settings to manage that, but they generally do not allow overclocking.
Some of us have additional builds with performance kernels built in. Not all of us though.
Your best approach would be to install PAC for your device then check your devices XDA thread for a popular performance kernel and flash that afterwords. The performance control will see the new CPU settings and you will then be able to configure it as you need.
DL an oc app, like CPU tuner or whatever..
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
todopertin said:
I want to know if I need to install a custom rom or a custom kernel or a combination of both so that I can overclock my phone(1ghz single core). Please help. Why is everybody so silent here, so unwilling to answer a simple question as this. My fourth post of the same question.
Click to expand...
Click to collapse
Yes, you need a kernel with overclock support .
On Gs2 I use PAC and dorimanx kernel
On your phone you need to search for kernels and roms for your model
Sent from my GT-I9100 using Tapatalk