Related
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
I recently saw the article for the ability to install cwm recovery to our phones system partition via the Xperia CWM Auto Installer app:
https://market.android.com/details?id=com.pvy.CWMinstaler
I am currently running the latest kernel from DoomLord, which I love but I wanted to know if there would be any advantages to using the above app over the custom kernel? And also if I use the app would it be safer to flash back to stock kernel, and alos wondering I thought I saw at one time a tweaked stock R800x kernel 2.3.3 that was modified to allow overclocking? Anyway if I do decide to give the above app a shot I was thinking of flashing the modified stock kernel (but I cannot find it anymore, unless I missed it somewhere on XDA) and then using the above app. Mostly just wanting people feedback and whether or not between the two which one would be better performance, and if someone can point me to the thread for the modified stock 2.3.3 kernel that would be fantastic.
Not to thread jack: Wasn't the app released just the same as the boot CWM with just touch support? Wasn't sure if there was a huge difference between the two programs.
As for your question regarding the stock kernel, highest the kernel itself will support is 1024Mhz; might have to throw on some racing stripe decals to make it go faster. I haven't seen any modified-stock kernels to be honest, just DoomLords.
= X™
n0_face said:
Not to thread jack: Wasn't the app released just the same as the boot CWM with just touch support? Wasn't sure if there was a huge difference between the two programs.
As for your question regarding the stock kernel, highest the kernel itself will support is 1024Mhz; might have to throw on some racing stripe decals to make it go faster. I haven't seen any modified-stock kernels to be honest, just DoomLords.
= X™
Click to expand...
Click to collapse
I thought I saw somewhere here on XDA for the xperia plays that there was a cdma modified kernel running 2.3.3 that had been modified to overclock. I am aware that the stock kernel is locked at the 1ghz. Thats 2 reasons why I am using DoomLords kernel, 1 for the overclock and 2 for the recovery. Just wonderinf if there would be any benefit to a stock modified kernel to allow overclock and teh xperia auto installer rather then the custom kernel?
I'm working on a modified stick kernel with kerianftw's help... Right now I'm working on adding cwm into it, and add soon as that's fine and I test it out (it'll probably take a week or so of testing)
Please don't ask for an ETA, because I am a busy man, as soon as I get it done & the bugs out, I'll post it.
I'm not sure if there will be that big of a difference because Doom v10 is pretty awesome...
Sent from my R800x using Tapatalk
Hey, I own the play r800x and I am using the 'Xperia CWM Auto-Instaler' with no problems at all. Backups and restores working like a dream, I just recently flashed "[ROM][CDMA] IT-ROM [r800x]" http://forum.xda-developers.com/showthread.php?t=1459456 (which is based of "COLA's" ROM and geared towards speed) and everything is working flawlessly.
If you're looking for speed (which I would love to be able to overclock too) then you should definitely consider using Cola's rom, or the one I'm using (IT-ROM [R800X]) ... I'm almost certain you will not be disappointed, my phone is now running much smoother/faster, no problems at all. Wifi, sms, 3g, phone, everything up and running without any hassle.
Good luck
Hi,
so, i'm looking for a good kernel for my N4, but... I can't really decide. I heard that franco and faux's kernel were good, but i can't see why. What's the difference between those kernels ? What's the features ? What's the difference between the stock one, and those one ?
Thanks for your answers !:good:
I'm running the matr1x kernel and I've liked it. I tried the others and this one provided the best battery life.
Sent from my Nexus 4 using xda premium
bricked kernel is the best!
look at this!
http://www.youtube.com/watch?feature=player_embedded&v=RtmxlnikTiQ
Sorry to bump this post, but i'm still looking for the pros and the cons of each kernel...
I didn't find any changelog or features for franco's kernel, and faux's kernel seems good... But i don't have my N4 for the moment... So i can't test them ! Thanks for your answer
Franco's kernel gets a changelog posted every time he does an update, it just isn't added to the first post. If you use his app (free version available) to download the newest kernel, the changelog is given through that as well.
I don't know how Franco compares to other kernels since i haven't tried them, but all the standard options seem to be there. Latest update added gamma control.
I believe every device reacts differently to kernels. I personally get the best battery life from Matr1x.
Sent from my Nexus 4 using xda premium
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.
We have another post for ROM. Why do we not have another post for Kernel ?
As we can see, we have more than 5 kernels that are from XDA developer or someone else. But which one is really good for your ROM and which one still keep updating ?
I have been using OP5T for 2 months. Have used so many kernels but i still got stuck in those and do not know which is more stable. I am planning to use the kernel from Blu_Spark. Is that good ?
Post your favourite kernel and tell everybody why you use that. It will help newbie to pick what they want.
I am using Flash kernel at the moment but I have already tried Blu, franko, arter, ElementalX etc, but honestly for me it's difficult to see any difference since this phone have already a great battery life and great speed. On my previous phone (S8) the custom kernel gives a big advantage since the phone have tons of bloat and and isn't running stock like Android.
vvt4994 said:
We have another post for ROM. Why do we not have another post for Kernel ?
As we can see, we have more than 5 kernels that are from XDA developer or someone else. But which one is really good for your ROM and which one still keep updating ?
I have been using OP5T for 2 months. Have used so many kernels but i still got stuck in those and do not know which is more stable. I am planning to use the kernel from Blu_Spark. Is that good ?
Post your favourite kernel and tell everybody why you use that. It will help newbie to pick what they want.
Click to expand...
Click to collapse
I have tried Blu and Franco for now and both have been very good. I really think kernel performance depends on the combo with the ROM as well as your device. I'm on Liquid Remix with Franco currently but I may give Resurrection Remix a try with Flash. If I had more time, I'd flash every ROM with every kernel to get a feel for all the possibilities LOL. :good:
For me Franco and flash kernel are the Best.... Now with ob3 with Franco kernel
Enviado desde mi ONEPLUS A5010 mediante Tapatalk
Did the Franco improve battery or performance? Someone Tried the Boeffla?
At the moment, both Flash Kernel and RenderKernel are great options in my opinion. I have tried most of the other kernels on xda and if you are looking specifically for smoothness/speed, these are the two you should test first. I do not run battery cycles; everyones daily use scenario really differs too much.
Flash Kernel currently has some kernel features I need (Kcal support & wakelock blocker) while RenderKernel does not have these features quite yet. While it lacks in some features, RenderKernel is undoubtedly the smoothest kernel for 5T right now.
I am on a 5T with OOS 5.0.3.
I like Franco but recently some custom ROMs have WIFI cannot turn on problem after I flash Franco kernel.
:fingers-crossed:
(Don't blame any devs here just sharing.)
crashazz33 said:
At the moment, both Flash Kernel and RenderKernel are great options in my opinion. I have tried most of the other kernels on xda and if you are looking specifically for smoothness/speed, these are the two you should test first. I do not run battery cycles; everyones daily use scenario really differs too much.
Flash Kernel currently has some kernel features I need (Kcal support & wakelock blocker) while RenderKernel does not have these features quite yet. While it lacks in some features, RenderKernel is undoubtedly the smoothest kernel for 5T right now.
I am on a 5T with OOS 5.0.3.
Click to expand...
Click to collapse
Where can I download flash kernel?
mo123456789 said:
Where can I download flash kernel?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-5t/development/op5t-flash-kernel-v2-15-1-t3729330/page34
I haven't really played around with Kernel choices much.
I use and appreciate the professionalism of ElementalX kernel.
With it's options to adjust for extreme brightness, it quickly became a favorite a couple years ago and I've just stuck with it since.
Now most devs are adding high brightness to their kernels.
I guess I can start checking other kernels out.
I do like that ElementalX stays very stockish, reliable.
I can pretty much flash it and feel confident nothing weird will pop up over the next few days.
CZ Eddie said:
I haven't really played around with Kernel choices much.
I use and appreciate the professionalism of ElementalX kernel.
With it's options to adjust for extreme brightness, it quickly became a favorite a couple years ago and I've just stuck with it since.
Now most devs are adding high brightness to their kernels.
I guess I can start checking other kernels out.
I do like that ElementalX stays very stockish, reliable.
I can pretty much flash it and feel confident nothing weird will pop up over the next few days.
Click to expand...
Click to collapse
ElementalX, Franco, and flash were all my go-to kernels back in the 6p days (just a few months ago, lol), so it's hard to pick, especially since they all ended up on the 5t. Right now I'm on exkernel though I am partial to flash. Battery life is amazing on all 3, but the overclock on ex just adds that extra bit of smoothness that I've never experienced before. Call it placebo but I just love this kernel (exkernel).
any more input?
im curious to know if fsync affects battery performance at all, can someone also test this out if you are on a kernel that enables disabling the fsync feature
virtyx said:
any more input?
im curious to know if fsync affects battery performance at all, can someone also test this out if you are on a kernel that enables disabling the fsync feature
Click to expand...
Click to collapse
Tried it but didn't notice any difference.
Technically it should improve performance when using the phone, but it won't be noticeable.
boeffla
simple and steady, close to stock for daily using.
blu_spark, always on the Fastlane. ?
Does flashing a custom kernel solves Google play services battery drain?
Do I need custom recovery and root to flash a custom kernel? I'm not willing to play with kernel adiutor so I'm not really interested in rooting
luws said:
Does flashing a custom kernel solves Google play services battery drain?
Do I need custom recovery and root to flash a custom kernel? I'm not willing to play with kernel adiutor so I'm not really interested in rooting
Click to expand...
Click to collapse
Custom kernel has nothing to do with google play services. You need custom recovery to flash a kernel, but most kernels for op5t are "flash & forget" which mean there is no reason to change the setting of the kernel.
Sent from my ONEPLUS 5T
vagkoun83 said:
Custom kernel has nothing to do with google play services. You need custom recovery to flash a kernel, but most kernels for op5t are "flash & forget" which mean there is no reason to change the setting of the kernel.
Sent from my ONEPLUS 5T
Click to expand...
Click to collapse
maybe not Google play services specifically, but with my latest phone (zuk z2), kernel was directly related to deep sleep
stock OOS/kernel has a serious issue with Google PS in terms of deep sleep. Besides that, I dont feel any need to flash a custom kernel. SOT is incredible already, and performance is really fluid.
luws said:
maybe not Google play services specifically, but with my latest phone (zuk z2), kernel was directly related to deep sleep
stock OOS/kernel has a serious issue with Google PS in terms of deep sleep. Besides that, I dont feel any need to flash a custom kernel. SOT is incredible already, and performance is really fluid.
Click to expand...
Click to collapse
If you are OK then there is no need to flash a kernel. If an app is crap (like Google services or facebook) the kernel can't do miracles and its not kernels job to control wakelocks of user apps
Sent from my ONEPLUS 5T
I keep changing between blu and new kernel
Not sure which to stick with but I think new kernel gives me a bit more battery