Related
Yeah, like topic states.
Im on CM6 on my nexus 1, with the korean radio and the stock kernel (haven't flashed any kernel at all since i got my N1). Now i feel like flashing a new kernel, but witch do you recommend?
Thanks guys!
I recommend IntersectRaven's cfs kernel. Best one for battery life I have found. Also the smoothest on my n1
Rellikzephyr
Sent from my Nexus One using Tapatalk
rooted using unrevoked, clockwork, cm6 RC2. terrrrrrible battery. anyone else have this issue? fixes?
sdnegus said:
rooted using unrevoked, clockwork, cm6 RC2. terrrrrrible battery. anyone else have this issue? fixes?
Click to expand...
Click to collapse
have you flashed any of the CM6 nightlies yet? the last 4 or 5 are using a new kernel that vastly improves battery life. there are also really awesome features that are not in the first iteration of RC2.
if you're not happy with kernel in the latest cm6 nightlies there are other options as well. go to the Android Development section and flash invisiblek's latest ASOP kernel (#17). it's gives wonderful battery life.
hope this helps.
chemical1der said:
have you flashed any of the CM6 nightlies yet? the last 4 or 5 are using a new kernel that vastly improves battery life. there are also really awesome features that are not in the first iteration of RC2.
if you're not happy with kernel in the latest cm6 nightlies there are other options as well. go to the Android Development section and flash invisiblek's latest ASOP kernel (#17). it's gives wonderful battery life.
hope this helps.
Click to expand...
Click to collapse
Download this kernal. Youre problems, soved. times 10.
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
Hey all,
This is my first thread so please be kind
I currently trying out a few ROMs, right now I'm loving Carbon Rom (nightly) but the battery life is not as good as PA, is this about right? When I'm not using it, the battery drops significantly, while using PA only drops a few percent. I'm using all the same apps btw on both (using titanium to backup and restore).
I used to have PAC on 4.2 (release version) and the battery life was great, but the 4.3 nightly battery life is even worse than Carbon.
I don't want to switch back to PAC 4.2 or PA for that matter since Carbon Rom have been stable and have great features
So what I'm trying to ask is, whether this so-so battery life is to be expected on a carbon Rom or am I missing some steps?
I did a clean wipe before installing carbon, currently running with semaphore 1.7.1 kernel.
Thx.
Alamien said:
Hey all,
This is my first thread so please be kind
I currently trying out a few ROMs, right now I'm loving Carbon Rom (nightly) but the battery life is not as good as PA, is this about right? When I'm not using it, the battery drops significantly, while using PA only drops a few percent. I'm using all the same apps btw on both (using titanium to backup and restore).
I used to have PAC on 4.2 (release version) and the battery life was great, but the 4.3 nightly battery life is even worse than Carbon.
I don't want to switch back to PAC 4.2 or PA for that matter since Carbon Rom have been stable and have great features
So what I'm trying to ask is, whether this so-so battery life is to be expected on a carbon Rom or am I missing some steps?
I did a clean wipe before installing carbon, currently running with semaphore 1.7.1 kernel.
Thx.
Click to expand...
Click to collapse
I just installed it. I agree so far. I am kinda disappointed. It might be my battery though. I just ordered a new one to test that out. I put the KitKat version instead of the Lollipop one expecting better battery life but it sucks. Obviously it takes some time to get used to it for proper readings. Have you figured out the problem (seeing its been 2+years)
So I was running stock for a very long time, and I had insane battery life. I usually got 5 and a half hours of screen on time with my usage which mostly included browsing and a bit of youtube-ing and maybe the 30-40 minutes of gaming. I never used it conservatively though, I just didn't need anything else. I had GPS and bluetooth off and I used WiFi only at home (2g, not 3g, when outside).
Anyway, a month ago I flashed PA 3.99 and my battery life has reduced. I only (relatively) get 4 and a half to 5 hours of screen on time. Is this normal? I thought I'll get better battery life with a custom ROM. I'm still running stock kernel BTW.
PA is giving me too many issues including random reboots so I've decided to flash either CM, PSX, Carbon or PACman (help me in deciding from these?). Should I flash a custom kernel too? I'm leaning towards Faux for the battery life but I'm scared it might reduce it!
PS : I just flashed the PA ROM, so I'm still running the stock kernel, right? The thing is, on my older phone, some devs bundled the ROM with a custom kernel. My kernel version says 3.4.0-perf-g04b6fae. Sorry for the noob-ness.
There are just too many factors, the coding, apps installed, kernel, optimization, the user usage pattern, signal quality. It wouldn't surprise me though, but if it work for you stick with it.
Kernel alone doesn't determine the whole picture. I don't use PA, but I don't think it use stock kernel since stock usually ends with "mtv.corp.google.com".
You can check these battery life benchmark for kernels if you want to try, however, I don't go by them: http://forum.xda-developers.com/showthread.php?t=2449982
Mohit12 said:
So I was running stock for a very long time, and I had insane battery life. I usually got 5 and a half hours of screen on time with my usage which mostly included browsing and a bit of youtube-ing and maybe the 30-40 minutes of gaming. I never used it conservatively though, I just didn't need anything else. I had GPS and bluetooth off and I used WiFi only at home (2g, not 3g, when outside).
Anyway, a month ago I flashed PA 3.99 and my battery life has reduced. I only (relatively) get 4 and a half to 5 hours of screen on time. Is this normal? I thought I'll get better battery life with a custom ROM. I'm still running stock kernel BTW.
PA is giving me too many issues including random reboots so I've decided to flash either CM, PSX, Carbon or PACman (help me in deciding from these?). Should I flash a custom kernel too? I'm leaning towards Faux for the battery life but I'm scared it might reduce it!
PS : I just flashed the PA ROM, so I'm still running the stock kernel, right? The thing is, on my older phone, some devs bundled the ROM with a custom kernel. My kernel version says 3.4.0-perf-g04b6fae. Sorry for the noob-ness.
Click to expand...
Click to collapse
I did exactly the same, and feel exactly the same... I have the same apps, same usage, and I feel like I have a few hours less with this ROM (and same Kernel). I'm planning to give Franco a try, I think, although according to that benchmark it won't give a great battery life either... Have you already tried anyone?
Just a noob question, I haven't yet completely understood that thing about builds. When I was completely stock I was in JWR66Y. Then I only flashed PA 3.99 RC2 (for that build) and now in settings it says JLS36G. It now means that I have to care that kernels get on well with JLS36G? I thought I would stay in JWR66Y.
jpl90 said:
I did exactly the same, and feel exactly the same... I have the same apps, same usage, and I feel like I have a few hours less with this ROM (and same Kernel). I'm planning to give Franco a try, I think, although according to that benchmark it won't give a great battery life either... Have you already tried anyone?
Just a noob question, I haven't yet completely understood that thing about builds. When I was completely stock I was in JWR66Y. Then I only flashed PA 3.99 RC2 (for that build) and now in settings it says JLS36G. It now means that I have to care that kernels get on well with JLS36G? I thought I would stay in JWR66Y.
Click to expand...
Click to collapse
there are two versions of 4.3..one is stock (JWR) and one is AOSP (JLS)
the AOSP build is more latest in a way..AOSP build has more speed but has random freezes for 2-3 seconds (should be fixed in most of the roms by now) while stock JWR build is not as speedy as AOSP but doesnt have those random freezes.
And yeah you would now have to flash a JLS kernel rather than JWR..and if you want a kernel with good battery life..try hells core kernel which IMO has the best battery life and performance
http://d-h.st/users/hellsgod/?fld_id=13048#files
Mohit12 said:
So I was running stock for a very long time, and I had insane battery life. I usually got 5 and a half hours of screen on time with my usage which mostly included browsing and a bit of youtube-ing and maybe the 30-40 minutes of gaming. I never used it conservatively though, I just didn't need anything else. I had GPS and bluetooth off and I used WiFi only at home (2g, not 3g, when outside).
Anyway, a month ago I flashed PA 3.99 and my battery life has reduced. I only (relatively) get 4 and a half to 5 hours of screen on time. Is this normal? I thought I'll get better battery life with a custom ROM. I'm still running stock kernel BTW.
PA is giving me too many issues including random reboots so I've decided to flash either CM, PSX, Carbon or PACman (help me in deciding from these?). Should I flash a custom kernel too? I'm leaning towards Faux for the battery life but I'm scared it might reduce it!
PS : I just flashed the PA ROM, so I'm still running the stock kernel, right? The thing is, on my older phone, some devs bundled the ROM with a custom kernel. My kernel version says 3.4.0-perf-g04b6fae. Sorry for the noob-ness.
Click to expand...
Click to collapse
after trying multiple different ROMs, kernels, etc.. I found that I wasted a lot of time getting geeked-out over nothing special. Sure, it's fun.. exciting... learning.. some minor features that are cool.. but, I do desire to have those hours of life back. Also, I experienced many more downsides than positives. Battery, lock-ups, random reboots, etc. A rooted stock device has served me very well..
acridity said:
there are two versions of 4.3..one is stock (JWR) and one is AOSP (JLS)
the AOSP build is more latest in a way..AOSP build has more speed but has random freezes for 2-3 seconds (should be fixed in most of the roms by now) while stock JWR build is not as speedy as AOSP but doesnt have those random freezes.
And yeah you would now have to flash a JLS kernel rather than JWR..and if you want a kernel with good battery life..try hells core kernel which IMO has the best battery life and performance
http://d-h.st/users/hellsgod/?fld_id=13048#files
Click to expand...
Click to collapse
Thanks! I had read about the difference between AOSP and stock, but didn't know/remember that JLS always AOSP. I think I felt this one better than stock. I've already been 4 days with it and I'm really comfortable being able to change dpi individually, custom it and use Pie, too, and stability is just as in stock, I think (I only got restarts in both of them while using Skype :S ). I didn't even worry to try CyanogenMod (in all my previous phones I had used it, always).
schmit said:
after trying multiple different ROMs, kernels, etc.. I found that I wasted a lot of time getting geeked-out over nothing special. Sure, it's fun.. exciting... learning.. some minor features that are cool.. but, I do desire to have those hours of life back. Also, I experienced many more downsides than positives. Battery, lock-ups, random reboots, etc. A rooted stock device has served me very well..
Click to expand...
Click to collapse
That's my concern in trying with new, custom kernels. Right now I'm just fine (although I'd like to have a little better battery life), so I'll keep reading and see if it's worth changing the kernel .
Thank you!
jpl90 said:
Thanks! I had read about the difference between AOSP and stock, but didn't know/remember that JLS always AOSP. I think I felt this one better than stock. I've already been 4 days with it and I'm really comfortable being able to change dpi individually, custom it and use Pie, too, and stability is just as in stock, I think (I only got restarts in both of them while using Skype :S ). I didn't even worry to try CyanogenMod (in all my previous phones I had used it, always).
That's my concern in trying with new, custom kernels. Right now I'm just fine (although I'd like to have a little better battery life), so I'll keep reading and see if it's worth changing the kernel .
Thank you!
Click to expand...
Click to collapse
the hassle come with flashing a new rom because you have to do a factory reset..with kernel though its pretty simple just wipe cache/dalvik cache flash kernel then reboot. So just try the kernels you think are interesting and if youre not comfortable with it then flash another one..i know its a hassle with rom but not much with kernel.
P.S you guys should really try hells god kernel. Ive been personally using it for 3 months and the battery life is just amazing
I'm getting good battery life with KitKat.
acridity said:
the hassle come with flashing a new rom because you have to do a factory reset..with kernel though its pretty simple just wipe cache/dalvik cache flash kernel then reboot. So just try the kernels you think are interesting and if youre not comfortable with it then flash another one..i know its a hassle with rom but not much with kernel.
P.S you guys should really try hells god kernel. Ive been personally using it for 3 months and the battery life is just amazing
Click to expand...
Click to collapse
Yeah, I've already flashed kernels in other phones, but never had this risk of compatibility issues due to different builds.
I've read that JSS kernels in JWR roms cause problems. Is the opposite not true? I mean, right now I have a stock JWR kernel running in a AOSP based ROM (JLS). Could this compatibility problems cause boot issues too? Of course, always with tested kernels. Or I'll always have the opportunity to boot into TWRP and flash a new kernel, until one works?
And one last question. When I look for AK's 4.3 kernel I only read JWR and JSS. Why doesn't it say JLS? Is it the same as JSS, then?
Thanks!
I can vouch for the above statements. I'm liking Hells core kernel. It's fast and has great battery life (as good as stock, maybe even slightly better). FWIW, I'm using Carbon ROM now and it's MUCH better than PA.
jpl90 said:
Yeah, I've already flashed kernels in other phones, but never had this risk of compatibility issues due to different builds.
I've read that JSS kernels in JWR roms cause problems. Is the opposite not true? I mean, right now I have a stock JWR kernel running in a AOSP based ROM (JLS). Could this compatibility problems cause boot issues too? Of course, always with tested kernels. Or I'll always have the opportunity to boot into TWRP and flash a new kernel, until one works?
And one last question. When I look for AK's 4.3 kernel I only read JWR and JSS. Why doesn't it say JLS? Is it the same as JSS, then?
Thanks!
Click to expand...
Click to collapse
Sorry i forgot to mention that JLS and JSS are the same build JLS being the latest one..so there is no difference in JSS or JLS. You can flash a JSS kernel on a JLS build no problem. But if youre build is jwr then your kernel build should also be jwr because yes it causes compatibility issues if you flash a jwr kernel on a jss/jls build or vice versa. In every ROM the stock kernel is matched with its build number. If its a jwr ROM then the stock kernel would also be jwr and vice versa.
Flashing a jwr on a jls/jss rom or a jls/jss kernel on a jwr rom might cause the phone to be in a bootloop (not going past the bootanimation) and even if you get it to boot up the performance would be lacking and it might cause random freezes, graphic glitches and or random reboots.
However there are some roms that are a hybrid which means its a combination of jwr build and jls/jss build. In that case you will flash a jwr kernel only nothing else.