Database Users

nscollab/cyanogenmod - the need of a stable kernel

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

[Q] Custom Kernel and updates

Heya, everybody.
I'd like to know if you guys could recommend a good kernel for undervolting and overclocking the Nexus 7. (I'm only looking into very mild overclocking, I don't want worse battery life)
But here's the main thing: I'm wondering about how you'd best go about updating your tablet after flashing a custom kernel. Will I be able to take OTA updates? Am I forced to flash new ROMs every update?
I'd just like the most simple way of updating my OS while being able to overclock and undervolt my Nexus 7. (OTA updates would be the most simple, right? If possible ofc)
I've got a Nexus 7 32GB. Android 4.2.1, IC 3568A-ME370T, Model ME370T, Build JOP40D

there aren't many kernels so quick search through android/original sections 1st pages you can find information about everything you need. i would suggest m-kernel or omega most stable (on my device) and with features you seek, although OC is kinda pointless IMHO if you are not going to benchmark it and given how scores/real world perfomance show well...it's pointless
i think you can't easily just update rom and keep kernel, but it's not much work, download newer version of the rom flash it, flash kernel, boot and resume... 5mins tops.

berkos said:
there aren't many kernels so quick search through android/original sections 1st pages you can find information about everything you need. i would suggest m-kernel or omega most stable (on my device) and with features you seek
Click to expand...
Click to collapse
Okay, I'll have a look at them. Thanks.
OC is kinda pointless IMHO if you are not going to benchmark it and given how scores/real world perfomance show well...it's pointless
Click to expand...
Click to collapse
Well, even if I'm only getting a 5% increase in performance or battery life I still consider it worth it. It's a rather simple upgrade that will last for years (I plan on taking good care of my device )
i think you can't easily just update rom and keep kernel, but it's not much work, download newer version of the rom flash it, flash kernel, boot and resume... 5mins tops.
Click to expand...
Click to collapse
Wait, so you can update Kernel and ROM separately?
Am I correct in assuming that most ROMs (including stock) come with a Kernel that will replace whatever Kernel I have?

I am using trinity kernel alpha 4 version along with cm 10.1 ROM. Can over clock to 1.7 GHz with this kernel. Downloaded trinity tool box also. You can under clock, over clock and set voltages along with some kernel tweaks. Has worked flawlessly so far. I also downloaded and installed cyan delta app. It will flash the delta file of each nightly you want and also flash kernel all in one shot. (Cyan Delta will only work with CyanogenMod ROMs.)
Sent from my Nexus 7 using Tapatalk HD

kevk60 said:
I am using trinity kernel alpha 4 version along with cm 10.1 ROM. Can over clock to 1.7 GHz with this kernel. Downloaded trinity tool box also. You can under clock, over clock and set voltages along with some kernel tweaks. Has worked flawlessly so far. I also downloaded and installed cyan delta app. It will flash the delta file of each nightly you want and also flash kernel all in one shot. (Cyan Delta will only work with CyanogenMod ROMs.)
Click to expand...
Click to collapse
I found this thread:
http://forum.xda-developers.com/showthread.php?t=1889571
I'll probably use Franco if possible, cuz amazing battery life. I noticed that my Nexus 7 only lasts like 5hours when gaming with it(stock clocks). That's not good enough for me! :S
If it doesn't work I'll probably go for Omega or M-Kernel. (or AOKP stock kernel)
I'll probably go for Paranoid Android 3.0 with the Franco kernel. I've read that they're compatible.
Updating to newer versions might be a bit of a pain, but the cool functions are probably worth it :3

You don't need to update every time a new version of a ROM or Kernel comes out, you know. If it's setup and working perfectly, the best thing to do would be to enjoy your tablet.

OTA updates do a lot of validation checks before they begin; in fact, they perform a checksum on every file targeted for a patch update.
It is quite common (not always, but common) for the kernel or ramdisk to be modified during an OTA update - so this means a high likelihood that an OTA update will not succeed on a device with a custom kernel.
There are lots of ways to do what you want, though; two basic strategies would be:
- From a backup, restore only the (stock) boot partition. Apply the OTA, and then restore a backup of your OC kernel/boot partition.
- Using Titanium Backup (or Carbon), back up your apps & data. Restore a pure stock backup, and take the OTA update on that. Make a Nandroid Backup of this. Flash the replacement kernel & a root kit. Boot and restore your apps. (This method is more labor intensive).
Note the frequent mention of full (nandroid) backups in the above. Backups are a good thing to have; make them early and often.
Anyway, there you go - two methods for the price of zero.

I prefer PA3.0 & Motley Kernel
Searz said:
I found this thread:
http://forum.xda-developers.com/showthread.php?t=1889571
...
I'll probably go for Paranoid Android 3.0 with the Franco kernel. I've read that they're compatible.
Updating to newer versions might be a bit of a pain, but the cool functions are probably worth it :3
Click to expand...
Click to collapse
I use PA3.0 with Motley Kernel and it works like a champ. There are stretches where I get 2-3 days of battery life (but I am paranoid and have everything disabled when I don't use it, and brightness down to ~15%). The link you provided though is a good resource.
--dchriste

Searz said:
I found this thread:
http://forum.xda-developers.com/showthread.php?t=1889571
I'll probably use Franco if possible, cuz amazing battery life. I noticed that my Nexus 7 only lasts like 5hours when gaming with it(stock clocks). That's not good enough for me! :S
If it doesn't work I'll probably go for Omega or M-Kernel. (or AOKP stock kernel)
I'll probably go for Paranoid Android 3.0 with the Franco kernel. I've read that they're compatible.
Updating to newer versions might be a bit of a pain, but the cool functions are probably worth it :3
Click to expand...
Click to collapse
Well don't expect major improvement in battery life while gaming, maybe if you down clock CPU for less demanding games, if you run demanding 3d games like Horn you will drain battery fast. Kernels change from version to version, performance and battery wise, so try different versions from same Dev. When it comes to games the way tegra 3 is designed you will not see much of benefit if any from oc cpu. Just look at the latest m36 kernel, your n7 will basically become dual core device with immeasurable performance loss. All I want to say don't expect wonders. If you are after battery life I would suggest you to look into other less bloated ROMs, like code fire, dirtybox, rasbean jelly. Paranoid is great in some aspects but I found less popular roms are easier on the battery, but not by a large margin.
Sent from my Nexus 7 using xda premium

I would have to agree. You do not have to update your rom with every nightly or your kernel with every version. If your tab is working fine, use it for what you got it for. Sorta like Murphy's law. If it ain't broke, don't fix it. (Read the changelogs)
Sent from my Xoom using Tapatalk HD

ynrozturk said:
You don't need to update every time a new version of a ROM or Kernel comes out, you know. If it's setup and working perfectly, the best thing to do would be to enjoy your tablet.
Click to expand...
Click to collapse
kevk60 said:
I would have to agree. You do not have to update your rom with every nightly or your kernel with every version. If your tab is working fine, use it for what you got it for. Sorta like Murphy's law. If it ain't broke, don't fix it. (Read the changelogs)
Click to expand...
Click to collapse
Yea, I won't be reflashing things unless there's new features that I really want.
dchriste90 said:
I use PA3.0 with Motley Kernel and it works like a champ. There are stretches where I get 2-3 days of battery life (but I am paranoid and have everything disabled when I don't use it, and brightness down to ~15%). The link you provided though is a good resource.
Click to expand...
Click to collapse
Motley is apparently one of the "worst" kernels when it comes to optimization and battery life. The best thing about it is probably the features, but I don't really need any of them, so I probably won't be using that one
bftb0 said:
OTA updates do a lot of validation checks before they begin; in fact, they perform a checksum on every file targeted for a patch update.
It is quite common (not always, but common) for the kernel or ramdisk to be modified during an OTA update - so this means a high likelihood that an OTA update will not succeed on a device with a custom kernel.
Click to expand...
Click to collapse
Yea, that seems to be the case from what I've read. But flashing the stock kernel would make it work fine, right?
bftb0 said:
- From a backup, restore only the (stock) boot partition. Apply the OTA, and then restore a backup of your OC kernel/boot partition.
Click to expand...
Click to collapse
This seems like it has a possibility of going wrong. I think I'll go with the second method.
bftb0 said:
- Using Titanium Backup (or Carbon), back up your apps & data. Restore a pure stock backup, and take the OTA update on that. Make a Nandroid Backup of this. Flash the replacement kernel & a root kit. Boot and restore your apps. (This method is more labor intensive).
Click to expand...
Click to collapse
This method is actually not that "labor intensive". As long as you've got Ti Backup Pro it's very easy to do this, you just gotta wait a while things backup/restore.
berkos said:
Well don't expect major improvement in battery life while gaming, maybe if you down clock CPU for less demanding games, if you run demanding 3d games like Horn you will drain battery fast.
If you are after battery life I would suggest you to look into other less bloated ROMs, like code fire, dirtybox, rasbean jelly. Paranoid is great in some aspects but I found less popular roms are easier on the battery, but not by a large margin.
Click to expand...
Click to collapse
Yea, I realize now that battery life when gaming probably won't change much.
Battery life is very important to me, but if it comes at the expense of features then the difference has to be noticeable.
How has your experience been? (compare the ROMs you've used)

[Q] What is the fastest stable ROM+kernel+libs?

So searching comes up with >1 year old threads and not really answering my question.
I got a used N4 recently for my daughter, and I want it to be as fast and stable as possible. I unlocked, then ADB flashed the currrent Google image and then rooted, made it ART runtime and applied the Z2 Bionic lib zip, applied current Franco kernel. Then I was halted in terms of is that the fastest?
Is that best combination which exists right now?
Is CM11 better?
I didn't really form a concluson of the Z2 Dalvik lib vs ART.

From what I know, this patch is currently faster than ART itself:
http://forum.xda-developers.com/nexus-4/general/4-4-4-4-x-qualcomm-optimized-dalvik-t2546120
Since ART is 'experimental' right now of course it lacks of improvements, but I am sure if Android L is released this October this wouldnt be the case anymore.
Also some Custom Roms like Cyanogenmod has its own optimized bionic libs, sometimes better than the stock ones or any patches. I highly recommend you to try this out, because than you dont have to search and compare no more.
In terms of kernel, I would not recommend you to use franco's kernel on a Custom Rom. Make sure to use any other kernel. This is just my personal experiences with franco's kernel and someone might call me too dumb to use this kernel, but why do I have so much trouble with franco and every other kernel runs fine like matr1x, ak or semaphore? Judge for yourself

CCody said:
From what I know, this patch is currently faster than ART itself:
http://forum.xda-developers.com/nexus-4/general/4-4-4-4-x-qualcomm-optimized-dalvik-t2546120
Since ART is 'experimental' right now of course it lacks of improvements, but I am sure if Android L is released this October this wouldnt be the case anymore.
Also some Custom Roms like Cyanogenmod has its own optimized bionic libs, sometimes better than the stock ones or any patches. I highly recommend you to try this out, because than you dont have to search and compare no more.
In terms of kernel, I would not recommend you to use franco's kernel on a Custom Rom. Make sure to use any other kernel. This is just my personal experiences with franco's kernel and someone might call me too dumb to use this kernel, but why do I have so much trouble with franco and every other kernel runs fine like matr1x, ak or semaphore? Judge for yourself
Click to expand...
Click to collapse
Right so I saw the claim that sticking with Dalvic and using the optimised Dalvik lib is faster but I gave up keeping track of it as too much "feels" and "benchmarks aren't representative" conclusion.
Noting to avoid Franco with custom ROMs. The custom one I did was CM and Franco warns to not use it!

nigelhealy said:
So searching comes up with >1 year old threads and not really answering my question.
I got a used N4 recently for my daughter, and I want it to be as fast and stable as possible. I unlocked, then ADB flashed the currrent Google image and then rooted, made it ART runtime and applied the Z2 Bionic lib zip, applied current Franco kernel. Then I was halted in terms of is that the fastest?
Is that best combination which exists right now?
Is CM11 better?
I didn't really form a concluson of the Z2 Dalvik lib vs ART.
Click to expand...
Click to collapse
the fastest.. whatever im using.
but really, these kinds of threads arent allowed on xda since you are asking us to compare roms. oh, ill clue you in a little, cm isnt even close to the fastest. and no, franco kernel isnt the fastest either.

Best ROM/kernel threads are not allowed on XDA
The best bet is to head over to the development sections and try some out for yourself and see which combination suits you best
Thread closed

smooth and fast in nexus 6p

Wich ROM, mod, kernel or combination of two of them give me the best experience in android?? I m looking for an Android system fast, smooth and best battery life. Thanks to all

If something was the best, nothing else would be used as there's no point in using something that's inferior when you can get something better.
There is no best, I suggest you read each thread and pick one that suits your needs. Saying X ROM and kernel is the best is like saying a specific vehicle is the best...One may say a Ferrari and another may say an F-350. But who's right?
Some people like roms and kernels bloated with 1000 customization options filled with placebo "optimization and enhancements". Others prefer a clean, minimal ROM without all the useless bling that they'll never use.
P.S. there's probably 10 threads like these, and possibly 11 by next week that you could've read through. I'll just copy and paste this same post on the next one.
Sent from my Nexus 6P using Tapatalk

Currently using PureNexus nougat with ElementalX kernel. The experience is pretty good.
Using the phone for SMS/MMS, YouTube and web browsing. I can get ~ 5/6h sot with a full charge on WiFi and ~ 3h30 sot on 3g/LTE which is enough for me.
Also using custom CPU governor profile in EXKernel Manager helped me with battery life without affecting performance (at least not that I noticed). You can find more infos here:
https://forum.xda-developers.com/nexus-6p/general/guide-advanced-interactive-governor-t3290605
Hope that helps

I am using the stock ROM with the ElementalX Kernel. Very happy with the performance of the phone. I arrive at the end of the day with 40% battery on average

yamilmanzur said:
I am using the stock ROM with the ElementalX Kernel. Very happy with the performance of the phone. I arrive at the end of the day with 40% battery on average
Click to expand...
Click to collapse
Wich version of stock are using?? I was use that option but I had some issue with stock.

5.1 said:
Currently using PureNexus nougat with ElementalX kernel. The experience is pretty good.
Using the phone for SMS/MMS, YouTube and web browsing. I can get ~ 5/6h sot with a full charge on WiFi and ~ 3h30 sot on 3g/LTE which is enough for me.
Also using custom CPU governor profile in EXKernel Manager helped me with battery life without affecting performance (at least not that I noticed). You can find more infos here:
https://forum.xda-developers.com/nexus-6p/general/guide-advanced-interactive-governor-t3290605
Hope that helps
Click to expand...
Click to collapse
Thanks for your answer. I had a boot loop when I install pure Nexus, Gapps, ElementalX and super su. But I like this option. Wich Gapps recommend?

hpagliettini said:
Wich version of stock are using?? I was use that option but I had some issue with stock.
Click to expand...
Click to collapse
7.1.1 ROM stock

hpagliettini said:
Thanks for your answer. I had a boot loop when I install pure Nexus, Gapps, ElementalX and super su. But I like this option. Wich Gapps recommend?
Click to expand...
Click to collapse
Hi. Gapps included in the OP of thePureNexus thread. OenGapps will work too.

Another "best rom" thread? Seriously ?
Pure

F2FS + Dark ROM + FLASH kernel ! That's the best combination and I am a serial flasher

These people that are saying there isn't a best ROM, I don't really understand the reasoning behind this. There most certainly is a best ROM kernel combination. Otherwise all these ROMs and kernels would be exactly the same right? Sorry to say, some are better than others. This is just a fact.
If you want speed, smoothness, glass, breakneck speeds, great battery life, there really is one only choice.
Uber rom by Chad and faster kernel by Chad.
Why?
On f2fs, (trust me, you want f2fs) I have yet to find kernel or ROM combination that beats this.
Its the only rom that's built with GCC 6.3.1, and the only rom built with clang 3.9.1. Coupled with f2fs, this rom FLIES.
I have flashed every single ROM on this forum and then some, and I'm telling you this is the best combination you can possibly hope for:
https://temp.bbqdroid.org

NOTilyass said:
F2FS + Dark ROM + FLASH kernel ! That's the best combination and I am a serial flasher
Click to expand...
Click to collapse
How much sot do you have with this combination?
You flash f2fs + dark ROM + Gapps + flash kernel in one time?

TrainNanpaMaster said:
These people that are saying there isn't a best ROM, I don't really understand the reasoning behind this. There most certainly is a best ROM kernel combination. Otherwise all these ROMs and kernels would be exactly the same right? Sorry to say, some are better than others. This is just a fact.
If you want speed, smoothness, glass, breakneck speeds, great battery life, there really is one only choice.
Uber rom by Chad and faster kernel by Chad.
Why?
On f2fs, (trust me, you want f2fs) I have yet to find kernel or ROM combination that beats this.
Its the only rom that's built with GCC 6.3.1, and the only rom built with clang 3.9.1. Coupled with f2fs, this rom FLIES.
I have flashed every single ROM on this forum and then some, and I'm telling you this is the best combination you can possibly hope for:
https://temp.bbqdroid.org
Click to expand...
Click to collapse
Uber rom by Chad I definitely agree is the best. I tried using his faster angler but it caused problems with mods like viper4arise so I am sticking with flash kernel. Uber by Chad is definitely the best rom though and I have tried so many roms like pure nexus, resurrection remix, dirty unicorns, sixRom, lineage, cyanogenmod, nitrogen, Cortex and so many more.

Is the stock camera working on either Uber or Dark ROM with f2fs file system?
Thanks

There's no such thing as a best rom fact, but only best rom opinions, which isn't a good idea to ever discuss here. [emoji14]
As for battery, that all depends on you as a user to manager your battery life your way. I get 4+ SOT easily and I listen to a lot of music and text a lot.
As for what I'm using, I'm running ABC Rom with franco.kernel, root, and V4A. ?
Sent from my Nexus 6P using Tapatalk

TrainNanpaMaster said:
These people that are saying there isn't a best ROM, I don't really understand the reasoning behind this. There most certainly is a best ROM kernel combination. Otherwise all these ROMs and kernels would be exactly the same right? Sorry to say, some are better than others. This is just a fact.
If you want speed, smoothness, glass, breakneck speeds, great battery life, there really is one only choice.
Uber rom by Chad and faster kernel by Chad.
Why?
On f2fs, (trust me, you want f2fs) I have yet to find kernel or ROM combination that beats this.
Its the only rom that's built with GCC 6.3.1, and the only rom built with clang 3.9.1. Coupled with f2fs, this rom FLIES.
I have flashed every single ROM on this forum and then some, and I'm telling you this is the best combination you can possibly hope for:
https://temp.bbqdroid.org
Click to expand...
Click to collapse
In this link I download the Uber ROM, right?
And other thing, you say me I have to flash to f2fs first before install this ROM and kernel?? Or I don't have to flash previous?

DEVILOPS 007 said:
Uber rom by Chad I definitely agree is the best. I tried using his faster angler but it caused problems with mods like viper4arise so I am sticking with flash kernel. Uber by Chad is definitely the best rom though and I have tried so many roms like pure nexus, resurrection remix, dirty unicorns, sixRom, lineage, cyanogenmod, nitrogen, Cortex and so many more.
Click to expand...
Click to collapse
I'm using faster kernel (r63) with Viper for arise with no problems at all bro. What's your steps for flashing?
I'm using 2.4 alpha B.

TrainNanpaMaster said:
I'm using faster kernel (r63) with Viper for arise with no problems at all bro. What's your steps for flashing?
I'm using 2.4 alpha B.
Click to expand...
Click to collapse
I basically just wiped cache and dalvik/art cache and flashed the rom and kernel and all my mods. I also made sure to do stuff like rename audio effects and everything I did to make it work with flash. I use stable 2.4 deutronomy aroma installer. I was talking to someone else on this rom and kernel and he said he had the same problem too so it might be hit and miss or maybe you flashed it different than us. Please tell.me what you did to get it to work. Thanks

What partitions do you guys convert to f2s besides cache? Data as well? Everything else remains ext4?

Running stock has been great for me lately. Downgraded to 6.0.1 running Xposed for pixel mods. Amplify and greenify. With exkernel has been a great experience so far. Near 7h SOT yesterday. Will be going back to 7.1.1 soon, as the February update is out.. I heard lineage OS has good battery life. Will be trying that out soon in a few days.
Read the threads on XDA and good luck!!:good:

[Discussion] Favourite Kernel and Why ?

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