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
Just got a Nexus 7 Tablet last night. I know everyone hates the "best ROM" question but I am clueless ass to the Nexus 7 scene. I have been an EVO/EVO 3D rom user forever.
What is the BEST Nexus 7 Rom for basic performance, battery and mostly added features / tools? If anyone has the time/desire to quickly (in a nutshell) compare and contrast a few top roms that would be awesome.
Your best results will be for you to read the various threads about each of the roms.
There the users of the roms will have posted what they like, have problems with experiences.
It would be hard to get a good comparison from anyone unless they actually have tried all the various rom.
I prefer clean ROM's that don't stray too far from AOSP, and don't include a lot of features. With that said, here's some of my favorites:
CleanROM
TeamEOS
Liquid Jellybean
Glazed Jellybean
And if you do choose a AOSP ROM, Here are some kernels:
motley kernel
faux kernel
Clemsyn's Elite Kernel
Trinity Seven
I'm currently about to give TeamEOS's latest nightly + Clemsyn's Elite Kernel (undervolted) a try
I've moved to Baked Grouper with motley's kernel and am wildly impressed. Liquid is also a very nice ROM.
goofball2k said:
I've moved to Baked Grouper with motley's kernel and am wildly impressed. Liquid is also a very nice ROM.
Click to expand...
Click to collapse
Thanks for the replies guys. I went ahead and tried Baked Grouper Blackbean by Team Baked.
What are some advantages of the motley kernel?
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
I unlocked, rooted, and flashed my nexus 10 only a few hours ago.
Now I have a question, about the Kernels, which are available for the Nexus 10.
Are they worth flashing, and which one is good concernig battery and performence.
I use PAcman Rom
I've had excellent luck with ktoonz manta kernel.
From my S-Off DNA
I second ktmanta, but would encourage you to try them all. Trinity is good for noobs, its stable, fast, and there's not much to mess up. Ktmanta with ktweaker is crazy customizable, but if not careful, you can make performance worse.I've readgood things about franco's kernel, but I've not personally tried it.
Here's a good link to learn: http://forum.xda-developers.com/showthread.php?t=1369817
thanks,
i think i´ll try ktmanta, because i have very much experience with kernels on my sgs2 so i´m not a noob
i also read that FRanco kernel is good, maybe i´ll try.
The one issue with Franco's kernel on the Nexus 10 is that it hasnt had much development so there isnt much to it. Basically a few little patches and adding boost pulse to OnDemand governor and that is it. If you are going to run a flash and forget kernel then Trinity is a much better choice right now.
I am running rooted stock 4.4, what custom kernel would go great for overclocking.
oxydo is quite simple, of that doesnt work out for you try m kernel, or the other way around, both are great
imo best oc kernel is DerKernel aka TrinitySeven.
I have flashed Franco Kernel, is that not very good
TotalMusic said:
I have flashed Franco Kernel, is that not very good
Click to expand...
Click to collapse
Hi, TotalMusic....
It's very good actually. I've used franco in the past, but not of recent. However, with the release of KitKat, I've just flashed the recently released franco version, r76. All seems OK so far. Nice and smooth.
Franco's kernels are known for their smoothness and speed, as well as being good for battery life.
But they don't support overclocking.
Rgrds,
Ged.