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

[POLL] SOD (sleep of death) issues/cases on ICS - Is it happening to you?

For ICS users only
I was just curious, since many users (including me), never got SOD on the phone, not even once..
And being a heavy user, I tried many GB and ICS builds (But I use Criskelo's stuff most of the time...)and so far no SOD..
Just give your vote, for the statistics (or curiosity? )
Thanks
.

When using the Rocket Rom, 1.5, I only ever got one and that was when sync was on and wifi was doing it's little glitch-out thing. Other than that, have never had one on 1.5.

It happened often when i flashed via Mobile ODIN. Re-flashing via full PC ODIN and then installing iMilka's AOSP has given me no problems.
I don't have any hard evidence that mobile odin is to blame, but flashing with full PC odin make a big difference for a friend and I.

Lots of SODs when running Chinese Repack, just a couple since switching to imilka's AOSP.
Repack flashed via Mobile Odin.

chasmodo said:
Lots of SODs when running Chinese Repack, just a couple since switching to imilka's AOSP.
Click to expand...
Click to collapse
Didnt try imilka's , started up (and staying) with Criskelo's and then tried a couple of other builds just to compare ...
Never got SOD on any of the other builds including ,when running CF repack with gapps 7.1
And always flashing with Mobile Odin with the necessary full wipes
.

I have not had a single SOD. Was on ROMOW ICS until imilka AOSP, have used imilka V1-V4 and been on V4 since release day with 0 SOD's. Mobile Odin CF Repack to imilka.

Have had several on Midnote.....matter of fact just had one 2 minutes ago...lol Otherwise this rom is perfect!

I just had one on the latest stock build of GB from India. I haven't rooted my phone or anything. Interesting. I will keep my eye on this thread. Thanks!

Feel free to mock me .... but what do you mean when you say SOD (screen of death)? Total system crash?

For some reason I get about 3 a day. I'm pretty sure its app installed. Once I raised the minimum CPU to 500 it got a lot better. When I get a chance I'll reinstall everything.
All in all I'm pretty sure its user error and not the rom. I'm using asop rom v4.
Sent from my GT-N7000 using xda premium

Yep same question here. (what do you mean by SOD?)
Many times I have the black screen when launching some app that sometimes work and sometimes don't (when I reboot the app is not accessible anymore).
I have an issue, it seems access to the external SD is not functioning well. Since I moved to ICS, I can't tell if it's Rom related or if its the SD that's faulty (it seems all OK when plugged to the computer).
I might have also to reboot when wifi toggled back on is not working well.
I'm using criskeloRom +15 toggles (but had more or less the same behavior with all the rom I used, Midnote or RocketRom).

Never on Criskelo's 1.5 ROM....in fact it is now 3 days without a reboot...I have had a couple of crashes without need for reboot, but its when Touchdown updates the stock contact list, which even happened on gingerbread...

Are you guys sure this is ROM related and not some other software?
I had SOD on GB

been using Team Rocket 1.5 since the first release, I totally had 4 times of SOD, not that much really.

i been using midnote repacked by me for atleast 6 days now NO SOD.
i give u guys a secret.
download midnote.dont download gapps from that thread.
download gapps from hptouchpad cm9 thread.its called gapps v11
youtube is tablet version.

@betoNL
Actually, it's not screen of death. It's sleep of death.

Using Chinese repacked ICS, flashed using Mobile Odin, got 4 SOD, once per day, going back to GB.

chasmodo said:
@betoNL
Actually, it's not screen of death. It's sleep of death.
Click to expand...
Click to collapse
Yep...just the other day I corrected somebody that wrote screen of death instead of sleep...
And I now I made the same mistake
Thanks for the observation though...
Just corrected it.
.

I am on criskelo v1 b3 with kernel Angelom, modem lb1, setcpu, but i have SOD yet
I love ICS and Chrome and i don't want return to GB

intruda119 said:
For some reason I get about 3 a day. I'm pretty sure its app installed. Once I raised the minimum CPU to 500 it got a lot better. When I get a chance I'll reinstall everything.
All in all I'm pretty sure its user error and not the rom. I'm using asop rom v4.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Yes, let's continue blaming the user despite how some have gotten SOD on a fresh flash on a stock Chinese ROM with no apps installed.

Which kernel is everyone using?

I successfully completed the conversion to dev mode and root my device. I have the multi-system kernel at this time but was wondering which kernel gives the best battery life and which are most people using?
The only 2 kernels I am aware of that are available are the emotion and multi-system ones. Is there something else?

My N4 performs well with this multi-system kernel Courtesy of @hsbadr

I've been using the Eceed Kernel by @kairi_zeroblade:
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742
there is a verizon version. I had no problems flashing this onto my jasmine rom 4.3 running android 5.1.1.
One user reported loosing data(4g) with this kernel but didnt give any info on what rom or firmware he was running.
the kernel works great so far, much better battery life. Scores 82,000+ consistently on antutu.
The kernel comes pre configured. The only things you can change if you wish is the cpu voltages, cpu currents, and a couple of read ahead tweaks in Synapse
the only thing I noticed was some camera lag (a bit slower to open and to switch from front to rear) that @kairi_zeroblade said could be due to the strict cpu settings. I believe hes working on a 6.0 MM kernel right now that should work for verizon.
Definitely worth a shot to check it out!!!! If you have any feedback just post in the original thread.

joemill said:
I've been using the Eceed Kernel by @kairi_zeroblade:
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742
there is a verizon version. I had no problems flashing this onto my jasmine rom 4.3 running android 5.1.1.
One user reported loosing data(4g) with this kernel but didnt give any info on what rom or firmware he was running.
the kernel works great so far, much better battery life. Scores 82,000+ consistently on antutu.
The kernel comes pre configured. The only things you can change if you wish is the cpu voltages, cpu currents, and a couple of read ahead tweaks in Synapse
the only thing I noticed was some camera lag (a bit slower to open and to switch from front to rear) that @kairi_zeroblade said could be due to the strict cpu settings. I believe hes working on a 6.0 MM kernel right now that should work for verizon.
Definitely worth a shot to check it out!!!! If you have any feedback just post in the original thread.
Click to expand...
Click to collapse
Got same results in antutu which is pretty awesome as fast as s6 but have no data on kyubi'so rom

This one: http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224

I use the screen mirroring option all the time. I would say test that out to determine which kernel is best for you. I know one of the kernels floating around doesn't support screen mirroring which is a big no no for me.
Sent from my SM-N910V using Tapatalk
---------- Post added at 05:13 PM ---------- Previous post was at 05:12 PM ----------
Not really big on Viper and over clocking so maybe someone else could shed some light on those features.
Sent from my SM-N910V using Tapatalk

axeldiks1 said:
Got same results in antutu which is pretty awesome as fast as s6 but have no data on kyubi'so rom
Click to expand...
Click to collapse
How are you guys getting over 82,000+. I'm only getting 72,000 with Jasmine

Dovanote said:
How are you guys getting over 82,000+. I'm only getting 72,000 with Jasmine
Click to expand...
Click to collapse
The Xceed kernel is over clocked to 2.8ghz and has various other tweaks

joemill said:
The Xceed kernel is over clocked to 2.8ghz and has various other tweaks
Click to expand...
Click to collapse
I haven't tweaked anything yet and this kernal is pretty nice. Battery life seems to last longer. Gotta test for a few more days.

Dovanote said:
I haven't tweaked anything yet and this kernal is pretty nice. Battery life seems to last longer. Gotta test for a few more days.
Click to expand...
Click to collapse
Xceed comes pre tweaked. The only thing that may give a little more speed is changing the internal and SD card read ahead from 512 to 2048mb and cfq as the scheduler. Most other adjustments are untouchable

any 6.0 roms working on the verizon note 4?

joemill said:
I've been using the Eceed Kernel by @kairi_zeroblade:
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742
there is a verizon version. I had no problems flashing this onto my jasmine rom 4.3 running android 5.1.1.
One user reported loosing data(4g) with this kernel but didnt give any info on what rom or firmware he was running.
the kernel works great so far, much better battery life. Scores 82,000+ consistently on antutu.
The kernel comes pre configured. The only things you can change if you wish is the cpu voltages, cpu currents, and a couple of read ahead tweaks in Synapse
the only thing I noticed was some camera lag (a bit slower to open and to switch from front to rear) that @kairi_zeroblade said could be due to the strict cpu settings. I believe hes working on a 6.0 MM kernel right now that should work for verizon.
Definitely worth a shot to check it out!!!! If you have any feedback just post in the original thread.
Click to expand...
Click to collapse
I lost my 4g also and I am on kubyi ultimate.I really want to try this kernel again, but I need the 4g..
Sent from my SM-N920F using Tapatalk

lolwatpear said:
any 6.0 roms working on the verizon note 4?
Click to expand...
Click to collapse
Hsbadr has a CM 13 port which is 6.0
CM 13 6.0.1 Unofficial

MatroxD said:
I lost my 4g also and I am on kubyi ultimate.I really want to try this kernel again, but I need the 4g..
Sent from my SM-N920F using Tapatalk
Click to expand...
Click to collapse
So looks like the kubyi rom will not work with this kernel. :/ I'm guessing the data fix will have to be patched into the Xceed kernel.
I haven't had the time to read through this:
http://forum.xda-developers.com/note-4-tmobile/general/running-international-roms-n910t-t3220738
Is it only for the n910t varient?
Does anyone have any info on the data fix for the verizon kernel so maybe @kairi_zeroblade can add it to the next build.?

joemill said:
So looks like the kubyi rom will not work with this kernel. :/ I'm guessing the data fix will have to be patched into the Xceed kernel.
I haven't had the time to read through this:
http://forum.xda-developers.com/note-4-tmobile/general/running-international-roms-n910t-t3220738
Is it only for the n910t varient?
Does anyone have any info on the data fix for the verizon kernel so maybe @kairi_zeroblade can add it to the next build.?
Click to expand...
Click to collapse
What info do you want to know about the datafix for Kyubi? It has multisystem kernel included. So far that is the only kernel that is compatible with Kyubi. No changes to the kernel were made to make it work with Kyubi. It just happened to work when I tried flashing Kyubi on our phone. So it became part of the datafix since it worked so well. I think if anything, @kairi_zeroblade should talk with @hsbadr the developer of multisystem kernel. We got lucky that hsbadr's kernel worked !

bostonsean said:
Hsbadr has a CM 13 port which is 6.0
CM 13 6.0.1 Unofficial
Click to expand...
Click to collapse
I meant stock mm roms. I noticed the snapdragon note 4 forums have them, but I'm not sure if they will work on the Verizon note 4.

jcip17 said:
What info do you want to know about the datafix for Kyubi? It has multisystem kernel included. So far that is the only kernel that is compatible with Kyubi. No changes to the kernel were made to make it work with Kyubi. It just happened to work when I tried flashing Kyubi on our phone. So it became part of the datafix since it worked so well. I think if anything, @kairi_zeroblade should talk with @hsbadr the developer of multisystem kernel. We got lucky that hsbadr's kernel worked !
Click to expand...
Click to collapse
I was thinking there was some type of patch or fix @hsbadr may have implemented into the multisystem kernel to get it to work. looks like @kairi_zeroblade is focusing on marshmallow though which should be awesome! Can't wait for us to get the update

I just re downloaded emotion kernel and am going to try it for a little bit.. Strange thing is, my battery percent jumped from 20 to 42 after reboot.. I will have to see how it goes..
Sent from my SM-N920F using Tapatalk

I second the Eceed kernel. Im on the jasmine rom and was using the emotion kernel but I noticed a fast drain on the battery. Switched over to Eceed a few days ago and have experienced a huge improvement on battery life, without the sacrifice in speed. Thanks Joemill for the suggestion.

Read about Exceed kernel so I gave it a try and thats the one Im sticking with. Runs great,using Jasmine Rom with it as well,battery life is great and my phone is very quick,highly recommend it.

N910F Best Rom?

Hi i'm still on stock rom Android 6.0.1 (updated by Odin). I wan't to install some custom rom to my N910F note 4 but there is so many roms i can't decide which one would be the best. I'm thinking of roms with note 7/s7 features. Can any of you that using decent rom give an advice which rom is most stable without bugs or only minor bugs? I don't want to lose fingerprint secure and i'm aware few roms had problems with that? Is it fixed now? If any of you have tested any roms and are happy can you make some recommendations for me for which rom i should go? I will really appreciate that

thenecu said:
Hi i'm still on stock rom Android 6.0.1 (updated by Odin). I wan't to install some custom rom to my N910F note 4 but there is so many roms i can't decide which one would be the best. I'm thinking of roms with note 7/s7 features. Can any of you that using decent rom give an advice which rom is most stable without bugs or only minor bugs? I don't want to lose fingerprint secure and i'm aware few roms had problems with that? Is it fixed now? If any of you have tested any roms and are happy can you make some recommendations for me for which rom i should go? I will really appreciate that
Click to expand...
Click to collapse
Noble rom v3 is best in my opinion and fingerprint works with workaround no bugs so far and AOD also works.i am using this for about 2 weeks and very satisfied.all the games runs butter smooth.only issue i had when i first installed this rom was over heating and i fixed with xceed kernel.all the other roms based on note7 or s7 i tried has lot of bugs IN MY OPINION

Trex888 said:
Noble rom v3 is best in my opinion and fingerprint works with workaround no bugs so far and AOD also works.i am using this for about 2 weeks and very satisfied.all the games runs butter smooth.only issue i had when i first installed this rom was over heating and i fixed with xceed kernel.all the other roms based on note7 or s7 i tried has lot of bugs IN MY OPINION
Click to expand...
Click to collapse
Sounds gud to me I am gonna give v3 a try what's the workaround for the fingerprint scanner?

vibealite said:
Sounds gud to me I am gonna give v3 a try what's the workaround for the fingerprint scanner?
Click to expand...
Click to collapse
You have to flash a zip file from twrp
it will give you original note 4 settings ui then register fingerprint after that flash another zip file to restore s7 settings ui.then you can use fingerprint with c locker app for lockscreen.and fingerprint srcurity app to lock apps both of this apps are free in playstore
Just search for fingerprint workaround inside noble v3 thread and there are lot of discussion and files there.

Thank you for opinion, have you also tried Dr Ketan or Norma rom before Noble v3?

thenecu said:
Thank you for opinion, have you also tried Dr Ketan or Norma rom before Noble v3?
Click to expand...
Click to collapse
Drketen rom is very good but i have over heating issues
And norma i tried all versions but still in beta and buggy in my opinion.there are lot of fix to do to make norma run stable.

Thank you Trex888 for your opinion, i think i will give it a try at evening i will try to install it however if anyone want to add something to this trade feel free to do so. More opinions only help (i guess not only for me but for other N910F users)

Trex888 said:
Noble rom v3 is best in my opinion and fingerprint works with workaround no bugs so far and AOD also works.i am using this for about 2 weeks and very satisfied.all the games runs butter smooth.only issue i had when i first installed this rom was over heating and i fixed with xceed kernel.all the other roms based on note7 or s7 i tried has lot of bugs IN MY OPINION
Click to expand...
Click to collapse
how does AOD work for you? Its buggy and you cant use the auto brightness

Motawa88 said:
how does AOD work for you? Its buggy and you cant use the auto brightness
Click to expand...
Click to collapse
It works great just when you unlock phone you have to press power button 2 or 3 times or you can cover the sensors with your finger and press once to restore brightness.make sure you update AOD from galaxy apps to latest version.

So basically i need to download the latest version of rom from:
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-noble-rom-t3392289
And for instalation process first i need to flash Bootloader & Modem, then rom and then kernel? If yes which kernel you recommend? and do i need to root my phone before?

thenecu said:
So basically i need to download the latest version of rom from:
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-noble-rom-t3392289
And for instalation process first i need to flash Bootloader & Modem, then rom and then kernel? If yes which kernel you recommend? and do i need to root my phone before?
Click to expand...
Click to collapse
Custom roms comes pre rooted you don't need to root
You have to be on any 6.0.1 bootloader doesn't matter
Best kernel for noble in my openion will be 1 of 3 kernels below.
1st . xceed kernel will give you performance & better battery and no over heating in my opinion
2nd. beastmode r56 will give you best speed & performance but sometimes has heating and auto sync issues with noble v3
3rd. Hvitamin kernel will give you best performance and speed but has heating issues
All of them will work with n910f
You can try every 1 couple of days dont judge in few hours kernel is good or bad
Dont forget to thanks or donate few bucks to kernels and rom developers if you can.they put lots of hours to do awesome job.
All kernels are awesome I am not saying that kernels are bad i am sharing my opinion and experience based on my usage

Custom roms comes pre rooted you don't need to root
You have to be on any 6.0.1 bootloader doesn't matter
Best kernel for noble in my openion will be 1 of 3 kernels below.
1st . xceed kernel will give you performance & better battery and no over heating in my opinion
2nd. beastmode r56 will give you best speed & performance but sometimes has heating and auto sync issues with noble v3
3rd. Hvitamin kernel will give you best performance and speed but has heating issues
All of them will work with n910f
You can try every 1 couple of days dont judge in few hours kernel is good or bad
Dont forget to thanks or donate few bucks to kernels and rom developers if you can.they put lots of hours to do awesome job.
All kernels are awesome I am not saying that kernels are bad i am sharing my opinion and experience based on my usage
Click to expand...
Click to collapse
I've installed the rom it was working fine. However fingerprint lock don't work for me? Do i need to use third party apk for that? Second thing later i've instaled xceed kernel, everygthing seems to work fine and smooth. However eveytime i restart phone or turn it off and on in left up corner is see text "kernel is not senandroid enforcing" - is that mean something is wrong? Phone is turning on normally, there is no boot loop or anything like that but it concerns me a little bit.

Custom kernels for g900V and CM13?

I have CM13 on the g900V and have some problems with CPU frequencies (posted on the ROM thread). It seems the only custom kernel for this phone and ROM is an unofficial boeffla kernel which was last updated in April and with which I had some problems too (random reboots).
Really aren't there any other kernels that work on g900V and CM13?
Thanks!

Some g900f kernels work on the g900v like try crazy super kernel
sent from my nexus 4 I also own a voyager tablet and an I-phone 4s

I want to report that I just installed the original Boeffla 3.3 for G900F and it's working just fine.
The issue with simple_ondemand for GPU governor seems fixed. The issue that I cannot set the lower CPU freq lower than 1881 MHz remains, though. (workaround in another post)
EDIT: Although almost everything runs smoothly, and I get amazing battery life with some CPU governors, camera doesn't work, it "does not connect"
Gonna try crazy super kernel as recommended

I used crazy sure kernel last time I used it 3 months or so ago the features I used worked including changing CPU MHz and fast charge and governors worked that is what I used
Sent from my Nexus 4 using Tapatalk

dronkit said:
I want to report that I just installed the original Boeffla 3.3 for G900F and it's working just fine.
The issue with simple_ondemand for GPU governor seems fixed. The issue that I cannot set the lower CPU freq lower than 1881 MHz remains, though.
Click to expand...
Click to collapse
You can install the 900F kernel on the 900V?

Yeah I used to do it back when I owned a g900v
sent from my nexus 4 using Tapatalk I also own a voyager tablet and I also own an I phone 4s

[email protected] said:
Yeah I used to do it back when I owned a g900v
sent from my nexus 4 using Tapatalk I also own a voyager tablet and I also own an I phone 4s
Click to expand...
Click to collapse
Huh, yeah it worked, crazy! Had no clue you could do that. Cool, now my SElinux is permissive.

ldeveraux said:
Huh, yeah it worked, crazy!
Click to expand...
Click to collapse
does your camera work? mine doesn't in g900f boeffla kernel

dronkit said:
does your camera work? mine doesn't in g900f boeffla kernel
Click to expand...
Click to collapse
Yes, I just tested and it's working fine.

[email protected] said:
I used crazy sure kernel last time I used it 3 months or so ago the features I used worked including changing CPU MHz and fast charge and governors worked that is what I used
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ldeveraux said:
Yes, I just tested and it's working fine.
Click to expand...
Click to collapse
Which one are you using? I tried to TWRP install this "anykernel crazy superkernel" and i get "this kernel is not compatible with your device" and does not install.

dronkit said:
Which one are you using? I tried to TWRP install this "anykernel crazy superkernel" and i get "this kernel is not compatible with your device" and does not install.
Click to expand...
Click to collapse
Boeffla's works fine:
http://forum.xda-developers.com/gal...ernel-boeffla-kernel-1-0-beta1-23-03-t3062073

ldeveraux said:
Boeffla's works fine:
http://forum.xda-developers.com/gal...ernel-boeffla-kernel-1-0-beta1-23-03-t3062073
Click to expand...
Click to collapse
I don't understand. The link you posted is a kernel for Touchwiz (stock samsung android), isn't it? We're talking CM13
Like I said, I tried Boeffla's kernel for CM13 but my camera doesn't work.
Still waiting for hauckk since he said he used crazy super kernel but I can't install it.

Edit the zip file for crazy super kernel and remove the asserts line guide here http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/182438-solved-assert-failed.html
Sent from my iPhone using Tapatalk

[email protected] said:
Edit the zip file for crazy super kernel and remove the asserts line guide here http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/182438-solved-assert-failed.html
Click to expand...
Click to collapse
Thanks, what I did was to edit out the check in the install script.
But, still, I get no camera ("cannot connect to camera"). Exactly what version of crazy super kernel do you have working? I tried the latest (16.0) and no camera. Gonna try some newer test versions now.

Finally!
I can report camera is working!
I had to install the latest CM13 nightly. The latest snapshot does not work. It's not on CM's site anymore so here's a link.
The kernel I used is the very latest test build. This link is the developer's folder which will hopefully contain the latest ones. Mine I pulled it from the folder "cm13-new test kernels".
If anyone wants, I can explain how to edit the script so the kernel doesn't refuse to install in g900v.